About working devices or not

[ArchangeGabriel]

I’m wondering what qualifies as a unsupported device and how you detect them.

For instance, I have this in my dmesg:

[   14.217147] lis3lv02d: unknown sensor type 0x0
[   14.217178] hp_accel: probe of HPQ6007:00 failed with error -22

This is an embedded accelerometer, that just doesn’t work under Linux currently. Of course, this is not really important because I don’t know what it could be used for, but it does count as an unsupported device to me. But not sure that you would count it, especially because dmesg is the only place where this is mentioned.

BTW, I think it would be interesting to list separately of dmesg the reported errors (mostly ACPI in general). For instance, this laptop spites:

[   14.301400] ACPI Error: Needed [Buffer/String/Package], found [Integer] 00000000c10b46a6 (20180313/exresop-560)
[   14.301404] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20180313/dswexec-427)
[   14.301410] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, AE_AML_OPERAND_TYPE (20180313/psparse-516)
[   14.301416] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_TYPE (20180313/psparse-516)
[   14.303022] ACPI Error: Needed [Buffer/String/Package], found [Integer] 00000000140c426d (20180313/exresop-560)
[   14.303026] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20180313/dswexec-427)
[   14.303030] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, AE_AML_OPERAND_TYPE (20180313/psparse-516)
[   14.303035] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_TYPE (20180313/psparse-516)
[   14.304256] ACPI Error: Needed [Buffer/String/Package], found [Integer] 00000000638aa933 (20180313/exresop-560)
[   14.304259] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20180313/dswexec-427)
[   14.304265] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, AE_AML_OPERAND_TYPE (20180313/psparse-516)
[   14.304270] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_TYPE (20180313/psparse-516)
[   14.310268] ACPI Error: Attempt to CreateField of length zero (20180313/dsopcode-134)
[   14.310308] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPI, AE_AML_OPERAND_VALUE (20180313/psparse-516)
[   14.310362] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_VALUE (20180313/psparse-516)

on every boot. The consequences are not clear to me, but being able to check rapidly whether this laptop model has some kinds of ACPI issues would be interesting.

Also, I would be interested to know how many laptops boot with acpi_osi=! acpi_osi='Windows 2009' or pcie_port_pm=off. Those are used to workaround some very important issues of hardware support under Linux regarding Nvidia GPU in laptops. I wouldn’t really count those devices as perfectly supported, since generally those options have a lot of consequences (non-working hotkeys, increased power consumption…). Yet you do not report this as an issue, because you do not detect it.

[linuxhw]

1. Status of each device kind is determined differently. For example, status of the graphics card is determined by driver availability in the system by lspci/hwinfo, driver usage by lsmod and absence of driver loading errors in xorg.log. Status of network cards is determined by successfully transmitted packages counted in ifconfig/ip logs and so on.

2. Accelerometers are usually mentioned in hwinfo, but not checked currently by hw-probe. We need to somehow link this hwinfo entry with dmesg error messages (by driver name?) to get both name and status of the device.:

    57: None 00.0: 10d00 Joystick
    [Created at input.312]
    Unique ID: 2oHd.lCw1nasASu4
    Hardware Class: joystick
    Model: "ST LIS3LV02DL Accelerometer"
    Device: "ST LIS3LV02DL Accelerometer"
    Device File: /dev/input/event14 (/dev/input/js0)
    Device Files: /dev/input/event14, /dev/input/js0, /dev/input/by-path/platform-lis3lv02d-event
    Device Number: char 13:78
    Buttons: 0
    Axes: 3
    Config Status: cfg=new, avail=yes, need=no, active=unknown
   

3. Just highlighted both ACPI Error and acpi_osi in dmesg for quick search. Need to parse this info and display on the site properly.

Thanks!