1 |
Running 2.6.35-r8. I suspected hal, as well. |
2 |
|
3 |
If I look through my /var/log/dmesg output, the load messages are |
4 |
almost identical to yours before I emerge the set. |
5 |
|
6 |
Unfortunately unmerging and re-emerging hal didn't seem to do anything. |
7 |
|
8 |
Then again -- would hal really have anything to do with the kernel |
9 |
loading the firmware? Hal shouldn't even be started by that point. |
10 |
|
11 |
-j |
12 |
|
13 |
On Sun, Sep 26, 2010 at 4:23 AM, Adam Carter <adamcarter3@×××××.com> wrote: |
14 |
> For reference here's mine |
15 |
> iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree: |
16 |
> iwlagn: Copyright(c) 2003-2010 Intel Corporation |
17 |
> iwlagn 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 |
18 |
> iwlagn 0000:04:00.0: setting latency timer to 64 |
19 |
> iwlagn 0000:04:00.0: Detected Intel Wireless WiFi Link 5100AGN REV=0x54 |
20 |
> iwlagn 0000:04:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels |
21 |
> iwlagn 0000:04:00.0: irq 32 for MSI/MSI-X |
22 |
> iwlagn 0000:04:00.0: firmware: requesting iwlwifi-5000-2.ucode |
23 |
> iwlagn 0000:04:00.0: loaded firmware version 8.24.2.12 |
24 |
> |
25 |
> Side note - If your system is pcie then you should turn on the MSI kernel |
26 |
> options. |
27 |
> |
28 |
> I have no idea really - tho out of the software you installed before the |
29 |
> breakage, Hal would have to be the biggest suspect. Maybe stop it form |
30 |
> starting at boot and reboot to see what happens?? (FWIW im running hald) I |
31 |
> assume you've added the hal use flag and done an emerge with newuse? |
32 |
> |
33 |
> What kernel are you running? |
34 |
> |
35 |
> |
36 |
> |