Bump -- just wondering if anyone else has any thoughts or has seen this in recent system updates.
-james On Sun, Sep 26, 2010 at 1:50 PM, James <j...@nc.rr.com> wrote: > Running 2.6.35-r8. I suspected hal, as well. > > If I look through my /var/log/dmesg output, the load messages are > almost identical to yours before I emerge the set. > > Unfortunately unmerging and re-emerging hal didn't seem to do anything. > > Then again -- would hal really have anything to do with the kernel > loading the firmware? Hal shouldn't even be started by that point. > > -j > > On Sun, Sep 26, 2010 at 4:23 AM, Adam Carter <adamcart...@gmail.com> wrote: >> For reference here's mine >> iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree: >> iwlagn: Copyright(c) 2003-2010 Intel Corporation >> iwlagn 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 >> iwlagn 0000:04:00.0: setting latency timer to 64 >> iwlagn 0000:04:00.0: Detected Intel Wireless WiFi Link 5100AGN REV=0x54 >> iwlagn 0000:04:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels >> iwlagn 0000:04:00.0: irq 32 for MSI/MSI-X >> iwlagn 0000:04:00.0: firmware: requesting iwlwifi-5000-2.ucode >> iwlagn 0000:04:00.0: loaded firmware version 8.24.2.12 >> >> Side note - If your system is pcie then you should turn on the MSI kernel >> options. >> >> I have no idea really - tho out of the software you installed before the >> breakage, Hal would have to be the biggest suspect. Maybe stop it form >> starting at boot and reboot to see what happens?? (FWIW im running hald) I >> assume you've added the hal use flag and done an emerge with newuse? >> >> What kernel are you running? >> >> >> >
