Master Kernel Thread

[ibuclaw]

Here is my dmesg output in colour.

:~$ dmesg | grep ath
[   18.530756] ath5k_pci 0000:00:09.0: registered as 'phy0'
[   18.956571] ath5k phy0: Atheros AR5213A chip found (MAC: 0x79, PHY: 0x45)
[   18.956576] ath5k phy0: RF2112A 2GHz radio found (0x56)
[   18.989253] ath_hal: module license 'Proprietary' taints kernel.
[   18.998284] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
[   19.064016] ath_pci: 0.9.4
[   19.134157] udev: renamed network interface wlan0 to ath0 

My card is the ath_pci...
I'm not sure why the ath5k_phy0 is showing though (does it need blacklisting?)

Read my last post on the previous page to know what I'm going on about.

[EDIT]
Yes, I think that it's the confliction of those two modules.
Here's my grepped dmesg in the 2.6.24 kernel

:~$ dmesg | grep ath
[   41.316301] ath_hal: module license 'Proprietary' taints kernel.
[   41.368469] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
[   41.635675] ath_pci: 0.9.4
[   45.303364] ath_rate_sample: 1.2 (0.9.4) 

So which file do I write in to blacklist the module then?

Regards
Iain

[ibuclaw]

Nevermind... found it.

[Gumper]

When you next boot up and see the splash screen. Hit Ctrl+Alt+F1 to see what your PC is doing.
It is most likely just hanging when it tries to load one module. So you should have plenty of time to write down the process it stops on.

I did as you suggested and the message that I have when it hangs is the following:

"Buffer I/O error on device FD0, Sector 0"
"End request : I/O error on FD0"

I assume from the FD0 part that it's referring to an issue with the floppy drive. The problem with that is I don't have one installed on my system. There is an entry for one in FSTAB though.

Here's that entry:

/dev/fd0 /media/floppy0 auto user,utf8,atime,noauto,rw,dev,exec,suid 0 0

Any ideas what this could mean?

[ptero]

I did as you suggested and the message that I have when it hangs is the following:

"Buffer I/O error on device FD0, Sector 0"
"End request : I/O error on FD0"

I assume from the FD0 part that it's referring to an issue with the floppy drive. The problem with that is I don't have one installed on my system. There is an entry for one in FSTAB though.

well, comment it out, maybe it will help...

[hyperair]

You can always blacklist the floppy module in /etc/modprobe.d/blacklist. I think that should help as well.

[Gumper]

well, comment it out, maybe it will help...

I thought about that but I remember doing it once before on a prior version on Ubuntu and then my system wouldn't boot. I'm a little hesitant to do it again.

[Gumper]

You can always blacklist the floppy module in /etc/modprobe.d/blacklist. I think that should help as well.

Thanks. I tried that but I get the same results.

[hyperair]

Did you run depmod?

sudo depmod -a

[ptero]

I thought about that but I remember doing it once before on a prior version on Ubuntu and then my system wouldn't boot. I'm a little hesitant to do it again.

hmmh, that's strange... are you sure that you didn't change anything else as well back then?
however, it shouldn't be a big enough reason to hesitate. just have a good live-cd near you (i prefer gentoo minimal cd ) and change the configuration file back if a problem like that appears.
and before applying major changes in configuration, i prefer to make a backup (stage4), because you can always get some minor troubles, which you won't discover instantly.

[Radomir]

For the usplash issue, please check out:
http://ubuntuforums.org/showpost.php?p=4356890

Uff, it's not that kind of the problem - I have splash on startup - 1280x1024 in 24-bit colour, but it fails when I'm shutting down or restarting. I get a bunch of messages from network manager - means a screen with text, and then some garbled image with lov resoluton and 8-bit color on the end. The bug is probably somwhere else... If anyone has an idea...
I allready tweaked my usplash with start-up manager.