bus.dch wrote:I was going to guess that your keyboard was a USB keyboard. Maybe I'm wrong. If you're using a USB keyboard, can you try borrowing a PS/2 keyboard to see if that one will not die on you?
I have exactly the same problems with an dwl-g122 using the rt2570 driver. But I'm using the default notebook keyboard, i.e. no other usb device is connected.
bus.dch wrote:Can you post the output from /var/log/kernel/current when it freezes? That may be tricky without a keyboard, but maybe the files get synced to disk and the log is still there when you reboot? Especially using KDE you could reboot the system cleanly and get the logs that way.
Also, what does lsmod say? What does lspci say?
Plugging in the usb wlan stick will be logged as follows:
Code: Select all
Jan 18 12:10:49 [kernel] usb 4-3: new high speed USB device using ehci_hcd and address 2
Jan 18 12:10:50 [kernel] idVendor = 0x2001, idProduct = 0x3c00
Jan 18 12:10:50 [kernel] usbcore: registered new driver rtusb
Jan 18 12:10:51 [kernel] RT25usb Driver version 1.0.0
Jan 18 12:11:00 [dhcpcd] DHCP_NAK server response received_
Jan 18 12:11:47 [dhcpcd] timed out waiting for a valid DHCP server response_
The net is up and running. Here is the output from lsmod
Code: Select all
Module Size Used by
rt2570 184000 1
ehci_hcd 29192 0
uhci_hcd 29328 0
snd_intel8x0 29536 0
snd_ac97_codec 90748 1 snd_intel8x0
snd_ac97_bus 1920 1 snd_ac97_codec
usbcore 104320 4 rt2570,ehci_hcd,uhci_hcd
thinkpad 5508 0
radeon 103808 1
eepro100 26384 0
and lspci (it's an ibm Thinkpad R40):
Code: Select all
00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]
02:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller
02:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (MOB) Ethernet Controller (rev 81)
Now when unplugging the stick, this will be written into the log:
Code: Select all
Jan18 12:15:47 [kernel] usb 4-3: USB disconnect, address 2
Waiting a while, a cron-message will be appended. So the system still is running. The mouse on the console is usable (gpm is running) but I can't use the keyboard anyway.
I've compiled ACPI support into the kernel, so I'm able to shutdown by pressing the power button to shutdown the system. But the system shutdown freezes, too (Last message: Bringing down rausb0). After a restart I found the following in my logfile:
Code: Select all
Jan 18 12:20:01 [cron] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 18 12:24:19 [init] Switching to runlevel: 0
Jan 18 12:24:26 [xinetd] Exiting...
Jan 18 12:24:32 [rc-scripts] Error stopping kdm.
Jan 18 12:24:33 [sshd] Received signal 15; terminating.
Jan 18 12:24:34 [ivman] IVM stopped
Same messages, when trying to shutdown from KDE using the mouse. In that case Xorg seems to restart, i.e. the system dows not switch to the console while shutting down.
I've tried the same compiling APM support instead of ACPI support into the kernel. But the behaviour is the same. I will try it w/o any power management support soon. But I remember, that some days ago it was the same although no APM/ACPI support was compiled into the kernel either.