First boot x64_86 error - kernel panic

[Jongi]

After running the install process and rebooting, this error immediately comes up:


insmod: error inserting '/lib/ext3.ko' :-1 Unknown symbol in module
insmod: error inserting '/lib/pata_via.ko' :-1 Unknown symbol in module
stabilized: open /proc/scsi/scsi : No such file or directory
insmod: error inserting '/lib/libata.ko' :-1 Unknown symbol in module
insmod: error inserting '/lib/libsata_via.ko' :-1 Unknown symbol in module

it would seem to me it's got something to do with sata?

[clay247]

You know how to fix things when the boot goes bad i guess? Usually you can use the grub init line to get things working again. When the machine boots and then the first Linux screen appears stop it by hitting "e" i think.

I'm seeing a lot of other forums complaining about this driver removed from standard kernel. This might have happened, so you might need a good Live CD to test things out. Did you change anything disk wise? Is it possible your disk went bad or isn't properly attached?

I have a similar board but I didn't go with the VIA chipsets for fear of this type of thing. I got the ATI chipset and it is great so far. One more thing, F8 was too bleeding edge for me, so I went back to FC7 for now.

If you have trouble let me know.

Cheers,

C

[Jongi]

thing is I installed fc7 32bit and upgraded to fc8 without issue.

my sidux and debian lenny (32bit) installs work.

no hardware changes since fc7 installed

[clay247]

Forgot to ask, did this happen after the latest kernel ( other ) updates, recently?

[clay247]

Just happened on to this too.

http://forums.fedoraforum.org/showpost.php?p=962770&postcount=2

In BIOS set the Sata Discs to AHCI and reboot. Wild guess here probably no help. Perhaps a similar BIOS setting?

[Jongi]

not sure what you mean by did this happen after an update? the error occurs the first time I boot after installing.

something I wonder now is whether this is a respin. but i'm fairly sure I would have labelled the dvd as such so I guess not.

[clay247]

I was talking about a $>yum -y update, sorry I forgot you are talking about a boot issue after a fresh install. Have you ever tried a network install? I usually do a totally minimal network install. Using this method you won't have as much yum'in to do later, and you know that you will get the standard install media. I think I usually use the boot.iso, which can be a pain to find sometimes. Good luck.

[Jongi]

ok. so i ran a new freshinstall but this time installed on a reiserfs parttion. posting from f8 x86_64. Used


expert reiserfs

after pressing Tab when the first install option was highlighted.

[clay247]

Yeah, there ya go. I've stayed away from reiser. There is a grub parameter for that, probably synonymous.

[Jongi]

just to clarify it was installing on a reiserfs partition that solved the issue.