Fedora 8 installs okay, won't boot.

[psyvision]

Hi,

I have had problems on my machine with both the 32 and 64 bit versions of the DVD. I have managed to get both to install (although not installing them at the same time...) except neither will boot.

At the moment I have the 32bit version on my computer (specs coming...) and it will install fine, I can then boot onto the DVD and go into rescue mode and chroot to my installation. However, if i attempt to use grub to boot the installation normally I have no luck.

The screen will display Red Hat nash etc... and then (i believe) do the Starting udev stage, at this point I get what looks to be a stack dump output with calls relating to emu_10k, which after some reading seems to be related to soundcards. The next printout is firewire related and then the machine hangs. Note I have an EMU1616 Pro audio soundcard (which the drivers are developed by creative).

I have tried specifying the kernel parameters when booting with grub (apm=off etc etc) and have also tried specifying run level 3, when doing this i still get the "stack dump" but it carries on a little further and hangs after setting the hostname...

The machine is a dual booting Windows XP box with an Asus M2N32-SLI nForce 590 motherboard, its an AMD64 dual core CPU with two NVIDIA 7600GS in SLI, the system then has two dual monitor screens attached.

I've got Fedora 8 installed on my laptop (dual boot again) and would rather use it on my main PC as opposed to say Ubuntu which I will try next to see if it is Fedora related.

I had an attempt at viewing messages from past boots by using dmesg but didnt have much luck in finding an error. Removing "quiet" from the boot command yeilds no luck either. Can someone give me some pointers as to what/where I should be looking? The installation is not on a RAID drive (but it is sata).

Is it worth trying a different runlevel? It seems to get further in runlevel 3 but i don't know what is meant to come after setting the hostname.

[FriedChips]

just for an experiment, try removing the emu and then try booting it up just to see what happens. At least if we can for sure pin it on that we can also update your system and try some newer/different kernels and look at some other options.

[psyvision]

You were right!

I have removed the EMU and udev starts with no issues, the only boot issue is eth1 which i need to deactivate on boot.

What are my next steps then considering that EMU do not do official drivers? I am not really fussed about having sound and so is there a way to stop the detection of the card? (Which is normal PCI based, not PCI-E).

[FriedChips]

First things first, now that you are into your new install do a full system update.

yum update

then shutdown and reinsert the card and see if you can boot. This may work because you will be running a new kernel. If not we need to figure out what kernel module is loaded by that emu card and blacklist it to keep it from loading up and brining your system to it's knees.

[FriedChips]

http://www.alsa-project.org/main/ind...5#EMU_Firmware
it appears that alsa has just added support for your card!! So if we can get it to boot with that puppy you may even have sound too after you get done updating post:

rpm -qa | grep "alsa"

[psyvision]

I saw a few posts relating to 1212 but not 1616, lets see if we can get it going... saves me removing the card for linux work..

I have the following installed:

alsa-utils-1.0.15-1.fc8
alsa-plugins-pulseaudio-1.0.14-5.fc8
alsa-lib-1.0.15-1.fc8
alsa-lib-devel-1.0.15-1.fc8
bluez-utils-alsa-3.20-4.fc8

[FriedChips]

welp that is the version of alsa you need what happens if you put the card back in now? I assume you have updated everything though right?

[psyvision]

Ah, I didnt see your first post, I did a full update from the console when it wasnt booting originally. My kernel (uname -r) is:

2.6.23.8-63.fc8

[FriedChips]

you may want to try a newer kernel yet.

yum update kernel --enablerepo=updates-testing

if that doesn't work we'll have to figure out something else... Maybe a 24 series kernel....

[psyvision]

I've put the card back in and same error...

[FriedChips]

Here is a link to the 24 series kernel. Download the rpm for your architecture and give it a shot if that other one doesn't work for you.
http://koji.fedoraproject.org/koji/b...?buildID=27444

Download it to you desktop and run:

su
rpm -ivh /home/*/Desktop/kernel*

then reboot and choose it from the menu.

[psyvision]

yum update kernel --enablerepo=updates-testing

Resulted in "Could not find update match for kernel"

So i tried the following after downloading the i686

su
rpm -ivh /home/*/Desktop/kernel*

Yielded the same results of udev failing and Fedora not booting...

[FriedChips]

Okay try this:

su -
echo "blacklist emu_10k" >> /etc/modprobe.d/blacklist
shutdown -h now

then reinsert your card and fire it up. You most likely won't have sound but hopefully you will be able to boot up. At least then you will not have to remove your card to run linux and it will give us some time to figure out the issue.

[psyvision]

I carried out the commands you gave and put the card back in, rebooted with the 23 series kernel and it crashes on boot as per before.

snd_emu10k1_free [snd_emu10k1]
snd_emu10k1_create [snd_emu10k1]
snd_card_new [snd]
iput
snd_card_emu10k1_probe [snd_emu10k1]
pci_device_probe

Is the stack trace for the crash, is emu_10k the right thing to blacklist? or can you see if from above i need to blacklist something different?

[FriedChips]

hmmm. okay try:

su -
echo "blacklist snd_emu10k1" >> /etc/modprobe.d/blacklist