1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
|
<?xml version="1.0" ?>
<system version="1.0">
<!-- summary: generic information about the submission -->
<summary>
<!-- live_cd: Was this submission made on a system running an Ubuntu Live
CD or on a regular Ubuntu/Linux installation?
-->
<live_cd value="False"/>
<!-- system_id: A hash of the "system identifier". This value is intended
to identify the tested computer model; the value should
be derived from the properties
system.product, system.vendor of the HAL UDI
/org/freedesktop/Hal/devices/computer.
-->
<system_id value="f982bb1ab536469cebfd6eaadcea0ffc"/>
<!-- distribution, distroseries: These values are retrieved from
/etc/lsb-release, parameters DISTRIB_ID and DISTRIB_RELEASE.
-->
<distribution value="Ubuntu"/>
<distroseries value="7.04"/>
<!-- architecture: The processor architecture of the operating system.
-->
<architecture value="amd64"/>
<!-- private: If False, this submission is publicly accessible from
Launchpad, else it is only accesible by the submitter, by
Launchpad administrators and by scripts running with
administrator rights. Submissions marked "private" should
only be used to gather statistical data.
-->
<private value="False"/>
<!-- contactable: If True, the owner agrees to be contacted by other
persons about devices which appear in his submission.
Example of a use case: Developers can ask device owners
to perform tests.
-->
<contactable value="False"/>
<!-- date_created: Date and time (UTC) of the submission.
-->
<date_created value="2007-09-28T16:09:20.126842"/>
<!-- client: The name and version of the program that created the
submission data.
-->
<client name="hwtest" version="0.9">
<!-- plugin: name and version of a plugin used by the client.
This tag may appear more than once.
-->
<plugin name="architecture_info" version="1.1"/>
<plugin name="find_network_controllers" version="2.34"/>
<plugin name="internet_ping" version="1.1"/>
<plugin name="harddisk_speed" version="0.7"/>
</client>
<!-- The kernel name and version, as shown by "uname -r"
-->
<kernel-release value="2.6.28-14-generic"/>
</summary>
<!-- hardware: data about the hardware the submission was made on.
-->
<hardware>
<!-- udev: The output of running "udevadm info - -export-db" -->
<udev>P: /devices/LNXSYSTM:00
E: UDEV_LOG=3
E: DEVPATH=/devices/LNXSYSTM:00
E: MODALIAS=acpi:LNXSYSTM:
P: /devices/pci0000:00/0000:00:1a.0
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:1a.0
E: DRIVER=uhci_hcd
E: PCI_CLASS=C0300
E: PCI_ID=8086:2834
E: PCI_SUBSYS_ID=17AA:20AA
E: PCI_SLOT_NAME=0000:00:1a.0
E: MODALIAS=pci:v00008086d00002834sv000017AAsd000020AAbc0Csc03i00
P: /devices/pci0000:00/0000:00:1a.0/usb3
N: bus/usb/003/001
S: char/189:256
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb3
E: MAJOR=189
E: MINOR=256
E: DEVTYPE=usb_device
E: DRIVER=usb
E: DEVICE=/proc/bus/usb/003/001
E: PRODUCT=1d6b/1/206
E: TYPE=9/0/0
E: BUSNUM=003
E: DEVNUM=001
E: DEVNAME=/dev/bus/usb/003/001
E: DEVLINKS=/dev/char/189:256
P: /devices/pci0000:00/0000:00:1a.0/usb3/3-0:1.0
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb3/3-0:1.0
E: DEVTYPE=usb_interface
E: DRIVER=hub
E: DEVICE=/proc/bus/usb/003/001
E: PRODUCT=1d6b/1/206
E: TYPE=9/0/0
E: INTERFACE=9/0/0
E: MODALIAS=usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
P: /devices/pci0000:00/0000:00:1a.0/usb3/3-0:1.0/usb_endpoint/usbdev3.1_ep81
N: usbdev3.1_ep81
S: char/252:4
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb3/3-0:1.0/usb_endpoint/usbdev3.1_ep81
E: MAJOR=252
E: MINOR=4
E: DEVNAME=/dev/usbdev3.1_ep81
E: DEVLINKS=/dev/char/252:4
P: /devices/pci0000:00/0000:00:1f.1
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:1f.1
E: DRIVER=ata_piix
E: PCI_CLASS=1018A
E: PCI_ID=8086:2850
E: PCI_SUBSYS_ID=17AA:20A6
E: PCI_SLOT_NAME=0000:00:1f.1
E: MODALIAS=pci:v00008086d00002850sv000017AAsd000020A6bc01sc01i8a
P: /devices/pci0000:00/0000:00:1f.1/host3
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:1f.1/host3
E: DEVTYPE=scsi_host
P: /devices/pci0000:00/0000:00:1f.1/host3/scsi_host/host3
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:1f.1/host3/scsi_host/host3
P: /devices/pci0000:00/0000:00:1f.1/host3/target3:0:0
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:1f.1/host3/target3:0:0
E: DEVTYPE=scsi_target
P: /devices/pci0000:00/0000:00:1f.1/host3/target3:0:0/3:0:0:0
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:1f.1/host3/target3:0:0/3:0:0:0
E: DEVTYPE=scsi_device
E: DRIVER=sr
E: MODALIAS=scsi:t-0x05
</udev>
<!-- The content of publicly accessible files in /sys/class/dmi/id/
format: filename:content
as for example generated by "grep -r . /sys/class/dmi/id/"
-->
<dmi>/sys/class/dmi/id/bios_vendor:LENOVO
/sys/class/dmi/id/bios_version:7LETB9WW (2.19 )
/sys/class/dmi/id/bios_date:06/06/2008
/sys/class/dmi/id/sys_vendor:LENOVO
/sys/class/dmi/id/product_name:6457BAG
/sys/class/dmi/id/product_version:ThinkPad T61
/sys/class/dmi/id/board_vendor:LENOVO
/sys/class/dmi/id/board_name:6457BAG
/sys/class/dmi/id/board_version:Not Available
/sys/class/dmi/id/chassis_vendor:LENOVO
/sys/class/dmi/id/chassis_type:10
/sys/class/dmi/id/chassis_version:Not Available
/sys/class/dmi/id/chassis_asset_tag:No Asset Information
/sys/class/dmi/id/modalias:dmi:bvnLENOVO:bvr7LETB9WW(2.19)
</dmi>
<!-- Additional data for SCSI devices: vendor, model, type
For each udev node which has DEVTYPE=scsi_device, we need
the content of the sysfs files vendor, model, type. The data
is stored in the same format as the DMI data:
/path/to/file:filecontent
-->
<sysfs-attributes>
P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
A: modalias=input:b0019v0000p0001e0000-e0,1,k74,ramlsfw
A: uniq=
A: phys=LNXPWRBN/button/input0
A: name=Power Button
P: /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:03/input/input8
A: modalias=input:b0019v0000p0006e0000-e0,1,kE0,E1,E3,F0,F1,F2,F3,F4,F5,ramlsfw
A: uniq=
A: phys=/video/input0
A: name=Video Bus
</sysfs-attributes>
<!-- processors: Data about processors installed in a system.
The data is retrieved from /proc/cpuinfo.
-->
<processors>
<!-- processor: Data from /proc/cpuinfo about a single processor.
-->
<processor id="123" name="0">
<!-- property: The data of one line of /proc/cpuinfo.
attribute name: The name of the property
(the text left of the ':' in a line of /proc/cpuinfo)
attribute type: A Python type appropriate for the value.
-->
<property name="wp" type="bool">
True
</property>
<property name="flags" type="list">
<value type="str">
fpu
</value>
<value type="str">
vme
</value>
<value type="str">
de
</value>
</property>
<property name="cpu_mhz" type="float">
1000.0
</property>
</processor>
</processors>
<!-- aliases: optional data provided by the user:
The name of a peripheral, PCI card etc as shown by a label on
the device. OEM devices are often sold under different names
by different vendors; having a set of alias names for a device
allows users of the HWDB to search for information by these
"marketing names".
-->
<aliases>
<!-- alias: The "label name" of a device or system.
attribute target: The sysfs path of a device as given
in <udev>.
-->
<alias target="/devices/pci0000:00/0000:00:1f.1/host3/target3:0:0/3:0:0:0">
<!-- vendor: The vendor name shown on the device label.
-->
<vendor>Medion</vendor>
<!-- model: The model name of shown on the label.
-->
<model>QuickPrint 9876</model>
</alias>
</aliases>
</hardware>
<!-- software: Data about the software installed on the system.
-->
<software>
<!-- lsbrelease: The data from /etc/lsb-release.
-->
<lsbrelease>
<!-- property: the data from one line of /etc/lsb-release.
attribute type: A Python type appropriate for this
property (str).
-->
<property name="release" type="str">
7.04
</property>
<property name="codename" type="str">
feisty
</property>
<property name="distributor-id" type="str">
Ubuntu
</property>
<property name="description" type="str">
Ubuntu 7.04
</property>
<property name="dict_example" type="dict">
<value name="a" type="str">value for key a</value>
<value name="b" type="int">1234</value>
</property>
</lsbrelease>
<!-- packages: Data about the installed software packages.
-->
<packages>
<!-- package: Data about a single package.
The <property> sub-tags contain the DEB properties
"name", "priority", "section", "source", "version",
"installed_size", "size", "summary".
XXX Abel Deuring 2007-12-12: What about submissions
from RPM-based Linux versions? (And "exotic" variants
like Gentoo?)
-->
<package name="metacity" id="200">
<property name="installed_size" type="int">
868352
</property>
<property name="section" type="str">
x11
</property>
<property name="summary" type="str">
A lightweight GTK2 based Window Manager
</property>
<property name="priority" type="str">
optional
</property>
<property name="source" type="str">
metacity
</property>
<property name="version" type="str">
1:2.18.2-0ubuntu1.1
</property>
<property name="size" type="int">
429128
</property>
</package>
</packages>
<!-- Information extracted from Xorg.0.log.
HAL does not provide any information about Xorg drivers, so
we retrieve that from the xserver's log file.
-->
<xorg version="1.3.0">
<!-- driver: Data about a driver.
(optional)
attribute name: The name of the driver.
attribute version: The version of the driver.
attribute class: The module class of the driver
attribute device: The ID of a device driven by this driver.
-->
<driver name="fglrx" version="1.23" class="X.Org Video Driver"
device="12"/>
</xorg>
</software>
<!-- questions: User's answers to questions asked by the client.
-->
<questions>
<!-- question: Data of a question.
attribute name: The unique name of the question.
attribute plugin: The name of the plugin which asked
the question.
attribute version: The version of the question.
attribute type: Allowed values are "manual" and "automatic".
A "manual" question requires user input for the answer;
an "automatic" question gets the answer automatically.
-->
<question name="detected_network_controllers"
plugin="find_network_controllers">
<!-- target: Information about a device or software package the
question is about. The attribute "id" is the sysfs path of
a device as given in <udev>, or the ID of a software package
node.
This node may appear multiple times.
-->
<target id="/devices/pci0000:00/0000:00:1a.0/usb3/3-0:1.0/usb_endpoint/usbdev3.1_ep81">
<!-- driver: The driver which controls the target device. This tag
may appear more than once.
While we are working on a project called "Hardware Database",
we are not that much interested in the question, if a device
works "as such", but if their Linux driver(s) work.
It is not in every case possible to identify the used driver
from HAL data, so we need another way to add this information.
(example: HAL does not know, which driver is used for the
graphics card.)
Example for multiple drivers: Some scanners have a SCSI _and_
a USB interface; if such a scanner is tested, we not only want
to know, which Sane backend is used, but also, which interface
is used.
Also, it might be interesting to know for many USB 2.0 devices,
if a USB 1 (uhci_hcd or ohci_hcd driver) or the USB 2 driver
(ehci_hcd) was used. A USB 1 driver might for example explain
latency problems.
-->
<driver>ipw3945</driver>
</target>
<!-- ID of the 88E8055 PCI-E Gigabit Ethernet Controller -->
<target id="/devices/pci0000:00/0000:00:1f.1"/>
<!-- command: The command line of an external command required to
ask this question.
-->
<command/>
<!-- answer: The answer to the question. Two types of answers are
defined, "multiple_choice" and "measurement". (See below
for an example of the latter.)
attribute type: Must be "multiple_choice" or "measurement".
-->
<answer type="multiple_choice">pass</answer>
<!-- answer_choices: The list of possible choices.
The data should only be used for consistency
checks and to detect variants of the question.
-->
<answer_choices>
<value type="str">fail</value>
<value type="str">pass</value>
<value type="str">skip</value>
</answer_choices>
<!-- A user comment about the device or about the test.
-->
<comment>
The WLAN adapter drops the connection very frequently.
</comment>
</question>
<question name="internet_ping"
plugin="internet_ping">
<target id="/devices/pci0000:00/0000:00:1f.1"/>
<command/>
<answer type="multiple_choice">pass</answer>
<answer_choices>
<value type="str">fail</value>
<value type="str">pass</value>
<value type="str">skip</value>
</answer_choices>
</question>
<!-- example for a "measurement question"
-->
<question name="harddisk_speed"
plugin="harddisk_speed">
<target id="/devices/pci0000:00/0000:00:1f.1/host3/target3:0:0/3:0:0:0"/>
<command>hdparm -t /dev/sda</command>
<!-- answer: The answer to a "measurement question".
attribute type: See above.
attribute unit: The unit of the result of the measurement.
XXX Abel Deuring 2007-12-12 bug=175978 We should
enumerate a list of allowed units, in order to avoid
multiple units for the same dimension. e.g., B/sec,
MB/sec or inch, cm, foot.
For dimensionless values, the attribute unit is omitted.
"Percentage" and similar "convenience pseudo-units" like
ppm are _not_ allowed; instead a dimensionless
value must be used, where 0 is equivalent 0% and 1.0 is
equivalent to 100%.
-->
<answer type="measurement" unit="MB/sec">38.4</answer>
</question>
</questions>
<!-- miscellaneous additional text data.
-->
</system>
|