You are not logged in.
Pages: 1
Hello:
I have recently installed Devuan 32 bit ASCII on my (old but trusty) Asus 1000HE, in preparation for (eventually) ridding myself of the present XP installation which I still use for some things like tax returns and coffee roasting software.
groucho@devuan:~$ uname -a
Linux devuan 4.9.0-9-686-pae #1 SMP Debian 4.9.168-1 (2019-04-12) i686 GNU/Linux
groucho@devuan:~$
For the moment Devuan boots from an SD Card holding grub while the rest of the installaton is on the HD.
This allows me to boot into XD when I need to and at the same time not have to mess with the drive's mbr.
The rig works (quite) well and the hardware is holding up almost as well as my Palm IIIxe's. (!)
Unfortunately, one of the USB ports has a broken tab so there's some surgery ahead.
---
I am really very thankful for having a 32bit systemd free installation such as Devuan available, hopefully 32bit support will continue for a few years.
---
I've been going though the logs to see what needs tuning/unloading/fixing as this Atom N280@166/2Gb RAM system needs not be unduly taxed.
eg: there are no serial, parallel or PS/2 ports, among other things which are loading modules.
There are also some things that I use every so often but are not working properly, eg: Asus hot keys.
One thing I have found in dmesg is this:
groucho@devuan:~$ sudo dmesg | grep -i eee
[ 8.043608] eeepc_wmi: Found legacy ATKD device (ASUS010)
[ 8.043690] eeepc_wmi: WMI device present, but legacy ATKD device is also present and enabled
[ 8.043784] eeepc_wmi: You probably booted with acpi_osi="Linux" or acpi_osi="!Windows 2009" <---- ???
[ 8.043877] eeepc_wmi: Can't load eeepc-wmi, use default acpi_osi (preferred) or eeepc-laptop
[ 8.043977] eeepc-wmi: probe of eeepc-wmi failed with error -16
groucho@devuan:~$
The thing is that my kernel command line does not have acpi_osi="Linux" or acpi_osi="!Windows 2009".
groucho@devuan:~$ sudo dmesg
--- snip ---
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-9-686-pae root=UUID=24b98eaa-bf67-4746-a866-473cac307016 ro ipv6.disable=1 enable_mtrr_cleanup
--- /snip ---
So ...
What is to be done with this?
I have not been able to find out just what a legacy ATKD device is.
Combing through lshw I did find an unclaimed device:
*-display:1 UNCLAIMED
description: Display controller
product: Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2.1
bus info: pci@0000:00:02.1
version: 03
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: latency=0
resources: memory:f7f80000-f7ffffff
Any ideas?
Thanks in advance.
A.
Offline
my kernel command line does not have acpi_osi="Linux" or acpi_osi="!Windows 2009".
You could try clearing the string by using
acpi_osi=
Reference: https://github.com/torvalds/linux/blob/ … s.txt#L153
I did find an unclaimed device
I'm not really familiar with lshw(1) but could that be for an unused display output?
Can you post
lspci -knn | grep -iA2 'vga\|3d\|display'
Brianna Ghey — Rest In Power
Offline
Hello:
You could try clearing the string by using
acpi_osi=
This is what I get using acpi_osi= in the kernel line.
groucho@devuan:~$ sudo dmesg | grep eeepc
[ 6.284913] eeepc_laptop: Eee PC Hotkey Driver
[ 6.285177] eeepc_laptop: Hotkey init flags 0x41
[ 6.286378] eeepc_laptop: TYPE (2000000) not reported by BIOS, enabling anyway
[ 6.292166] eeepc_laptop: PANELPOWER (4000000) not reported by BIOS, enabling anyway
[ 6.292281] eeepc_laptop: Get control methods supported: 0x6101713
[ 6.293219] input: Asus EeePC extra buttons as /devices/platform/eeepc/input/input7
--- from here down were already there ---
[ 7.878347] eeepc_wmi: Found legacy ATKD device (ASUS010)
[ 7.884493] eeepc_wmi: WMI device present, but legacy ATKD device is also present and enabled
[ 7.890126] eeepc_wmi: You probably booted with acpi_osi="Linux" or acpi_osi="!Windows 2009"
[ 7.895852] eeepc_wmi: Can't load eeepc-wmi, use default acpi_osi (preferred) or eeepc-laptop
[ 7.901709] eeepc-wmi: probe of eeepc-wmi failed with error -16
[ 8.559056] eeepc_laptop: Unable to find port
groucho@devuan:~$
Just FYI, the options I got from disassembling dsdt.dat are these:
groucho@devuan:~/dsdt$ cat dsdt.dsl | grep -i _OS
If (CondRefOf (_OSI, Local1))
If (_OSI ("Windows 2000"))
If (_OSI ("Windows 2001"))
If (_OSI ("Windows 2001 SP1"))
If (_OSI ("Windows 2001 SP2"))
If (_OSI ("Windows 2001.1"))
If (_OSI ("Windows 2001.1 SP1"))
If (_OSI ("Windows 2006"))
ElseIf (MCTH (_OS, "Microsoft Windows NT"))
If (MCTH (_OS, "Microsoft WindowsME: Millennium Edition"))
If (MCTH (_OS, "Linux"))
If (CondRefOf (_OSI, Local0))
If (_OSI ("Windows 2001"))
If (_OSI ("Windows 2001 SP1"))
If (_OSI ("Windows 2001 SP2"))
If (_OSI ("Windows 2006"))
If (_OSI ("Windows 2009"))
If (_OSI ("Linux"))
ElseIf (MCTH (_OS, "Microsoft Windows"))
ElseIf (MCTH (_OS, "Microsoft WindowsME: Millennium Edition"))
ElseIf (MCTH (_OS, "Microsoft Windows NT"))
groucho@devuan:~/dsdt$
The kernel is evidently seeing something somewhere that is indicating acpi_osi="Linux" or acpi_osi="!Windows 2009".
That said, the default acpi_osi (preferred) or eeepc-laptop entires are not in the dsdt file.
I'll have to run some tests and see what happens.
Can you post
lspci -knn | grep -iA2 'vga\|3d\|display'
It returns nothing.
I seem to recall having seen something about ASUS010 somewhere once ...
I'll have a look and see what I can find.
Thanks for your input.
A.
Last edited by Altoid (2019-05-04 20:08:13)
Offline
Can you post
lspci -knn | grep -iA2 'vga\|3d\|display'
It returns nothing.
How about without my silly grep? What does the plain lspci -knn report about your graphics card?
Oh, and leave that poor cat(1) alone:
grep -i _OS dsdt.dsl
Last edited by Head_on_a_Stick (2019-05-04 20:34:34)
Brianna Ghey — Rest In Power
Offline
Hello:
What does the plain lspci -knn report about your graphics card?
Much more.
And about the other hardware too.
Here you go ...
groucho@devuan:~$ lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GSE Express Memory Controller Hub [8086:27ac] (rev 03)
Subsystem: ASUSTeK Computer Inc. Mobile 945GSE Express Memory Controller Hub [1043:8340]
--->
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03)
Subsystem: ASUSTeK Computer Inc. Mobile 945GSE Express Integrated Graphics Controller [1043:8340]
Kernel driver in use: i915
Kernel modules: i915
00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
Subsystem: ASUSTeK Computer Inc. Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1043:8340]
<---
00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 02)
Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family High Definition Audio Controller [1043:834a]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 1 [8086:27d0] (rev 02)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 2 [8086:27d2] (rev 02)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.3 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 4 [8086:27d6] (rev 02)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 [8086:27c8] (rev 02)
Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family USB UHCI Controller [1043:830f]
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 [8086:27c9] (rev 02)
Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family USB UHCI Controller [1043:830f]
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 [8086:27ca] (rev 02)
Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family USB UHCI Controller [1043:830f]
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 [8086:27cb] (rev 02)
Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family USB UHCI Controller [1043:830f]
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller [8086:27cc] (rev 02)
Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family USB2 EHCI Controller [1043:830f]
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e2)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 02)
Subsystem: ASUSTeK Computer Inc. 82801GBM (ICH7-M) LPC Interface Bridge [1043:830f]
Kernel driver in use: lpc_ich
Kernel modules: intel_rng, lpc_ich, leds_ss4200
00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 02)
Subsystem: ASUSTeK Computer Inc. 82801G (ICH7 Family) IDE Controller [1043:830f]
Kernel driver in use: ata_piix
Kernel modules: ata_piix, ata_generic
00:1f.2 IDE interface [0101]: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] [8086:27c4] (rev 02)
Subsystem: ASUSTeK Computer Inc. 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] [1043:830f]
Kernel driver in use: ata_piix
Kernel modules: ata_piix, ata_generic
01:00.0 Network controller [0280]: Ralink corp. RT2790 Wireless 802.11n 1T/2R PCIe [1814:0781]
Subsystem: AzureWave RT2790 Wireless 802.11n 1T/2R PCIe [1a3b:1059]
Kernel driver in use: rt2800pci
Kernel modules: rt2800pci
03:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet [1969:1026] (rev b0)
Subsystem: ASUSTeK Computer Inc. AR8121/AR8113/AR8114 Gigabit or Fast Ethernet [1043:8324]
Kernel driver in use: ATL1E
Kernel modules: atl1e
groucho@devuan:~$
Oh, and leave that poor cat(1) alone:
grep -i _OS dsdt.dsl
There's more than one way to skin a cat. =-)
I still have to polish my command line.
Thanks for the tip.
Cheers,
A.
Offline
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) Subsystem: ASUSTeK Computer Inc. Mobile 945GSE Express Integrated Graphics Controller [1043:8340] Kernel driver in use: i915 Kernel modules: i915 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) Subsystem: ASUSTeK Computer Inc. Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1043:8340]
That's interesting, you have two entries for the same device, no idea why
The i915 kernel driver is loaded though so you should be fine.
Brianna Ghey — Rest In Power
Offline
Hello:
That's interesting, you have two entries for the same device, no idea why
The display appears to be working fine, so that would be something to look at later on.
Maybe it has to do with the 1000HE's vga port?
In any case, the issue in this post was mainly related to eeepc_wmi.
I have searched the web and traced the problem to a bug in linux-source-4.9 kernel due to a regression apparently caused by this patch:
https://git.kernel.org/pub/scm/linux/ke … ?h=v4.9.51
It seems that it is the same as this, but [sort of] explained:
https://git.amelchem.com/amel/linux/com … 573777c6ac
If legacy device (SB.ATKD - ASUS010) used by eeepc-laptop
is enabled, don't allow eeepc-wmi to load because:
- eeepc-laptop may be loaded, and can conflict with
eeepc-wmi (they both try to register eeepc::touchpad
led for example).
- the WMI interface is inteded to be used when the OS is
not detected as Win 7. And when this is the case, the
ASUS010 device is disabled.
Edit
Apparently the ASUS010 device is the EEEPC Hotkey set.
See
https://github.com/torvalds/linux/blob/ … c-laptop.c
#define EEEPC_LAPTOP_VERSION "0.1"
#define EEEPC_LAPTOP_NAME "Eee PC Hotkey Driver"
#define EEEPC_LAPTOP_FILE "eeepc"#define EEEPC_ACPI_CLASS "hotkey"
#define EEEPC_ACPI_DEVICE_NAME "Hotkey"
#define EEEPC_ACPI_HID "ASUS010"
/Edit
Here's the original bug report from 20170920:
https://bugs.debian.org/cgi-bin/bugrepo … bug=876303
Here's what apparently needs to be done, no idea though.
"So I removed the 'use acpi_dev_found' patch from my kernel source, and without
this patch eeepc_wmi is loaded successfully, and all fn+ buttons working with
this netbook without acpi_os=Linux extra boot parameter"
And this is the last post in the bug report darted 20180301:
https://bugs.debian.org/cgi-bin/bugrepo … =876303#28
I've written to the author of the last post and apparently the bug is still there.
I have to get some live 32bit distro with a 5.0 kernel to see if it has been fixed but I am not holding my breath.
Looks like a bug originated in what was probably (?) a hastily applied patch.
It would be nice if the same haste would be applied to rolling it back. No?
Any ideas welcome (blacklisting something, etc.).
Cheers,
A.
Last edited by Altoid (2019-05-05 19:59:58)
Offline
Pages: 1