LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   kernel panic after fresh install of 10.2 (http://www.linuxquestions.org/questions/slackware-14/kernel-panic-after-fresh-install-of-10-2-a-366678/)

mosca 09-24-2005 04:52 PM

kernel panic after fresh install of 10.2
 
Hello friends!

I just did an install of 10.2 and receives the following kernel panic when rebooting. I chose the sata.i kernel and had to boot with sata.i noscanluns for the install to work (but I don't think it has to anything to do with the panic):

kmod: failed to exec /sbin/modprobe -s -k block-major-8, errno = 2
cannot open root device "807"
please append a correct root= boot option
Kernel panic unable to mount root fs on 08:07

I am able to boot using the install cd and mounting the /dev/sda7 gives me the / partition.

During the install, I only booted from cd, the files were installed from a 2nd hd.

I am dual booting with XP and it works as good as it can.

Uhm, what else could be of helpful...
In the lilo.conf, I have the following in the linux section:
image = /boot/vmlinuz
root = /dev/sda7 (as mentioned)
label = Linux
read-only

I'm not sure why the read-only line is there... The line has a comment saying "Non-UMSDOS filesystems should be mounted readonly for checking".

Any suggestions on what I should look into is very much appreciated!

Thanks in advance from a former debian user trying slack.

mosca 09-24-2005 05:44 PM

I guess I need an initrd, since the / is ext3.

gbonvehi 09-24-2005 06:58 PM

There's a step during installation that asks you for a kernel to install, did you choose the right one (sata.i) there?

mosca 09-24-2005 08:22 PM

Yes, there was an option to choose the same kernel as you were booting from.

Now I have some problems to create the initrd. It seems that the modules are zipped (e.g. jbd.o.gz) and therefore not ELF files (insmod complains about this). I must look into how to decompress these and then build a new initrd (I guess).

mosca 09-24-2005 08:49 PM

I did the following:
- gunzipped the modules I needed for ext3 (jbd and ext3) found in /boot/initrd-tree/lib/modules/2.4.31
- modified the little load_kernel_modules script to load the gunzipped files
- created a new initrd.gz by running mkinitrd in /boot.

Rebooting, the jbd.o seem to load fine (written nicely as Journalled Block Device driver loaded) but it is immediately followed by "kernel BUG at slab.c:815!" and some dump of system info. This is concluded by "Segmentation fault". Not that great. I guess this was not the right way to do this. :)

Any clues welcome!

btw, I got inspired by this:
http://www.linuxquestions.org/questi...5&pagenumber=1

Bruce Hill 09-24-2005 10:46 PM

If you started the install with the sata.i kernel, and you're using 2.4.31, you don't
need an initrd. What you need is when you come to that second part and it asks
you which kernel, don't say "skip and use the default one," but rather, you have
to once again select the sata.i kernel. At least that's been my experience.

You can check to see if you have the modules by issuing "lsmod" and they should
also issue "ls -al /lib/modules/2.4.31/kernel/fs/ext3/" to see if you have ext3.

Basel 09-25-2005 04:22 AM

Quote:

Originally posted by Chinaman
If you started the install with the sata.i kernel, and you're using 2.4.31, you don't
need an initrd. What you need is when you come to that second part and it asks
you which kernel, don't say "skip and use the default one," but rather, you have
to once again select the sata.i kernel. At least that's been my experience.

You have to do what Chinaman told you. Here is a thred that has the steps that you need to follow:
http://www.linuxquestions.org/questi...95#post1760995

mosca 09-25-2005 08:45 AM

Thank you! It works fine now when I installed the sata kernel.

Next step is to install a 2.6 kernel and to get the network working (I got the same network problem as
http://forums.us.dell.com/supportfor...essage.id=6627 )

Bruce Hill 09-25-2005 08:53 AM

In a terminal issue "/sbin/lspci" and post the entire line you get for Ethernet controller.

mosca 09-25-2005 09:22 AM

Here is lscpi -v:

05:08.0 Ethernet controller: Intel Corporation 82801G (ICH7 Family) LAN Controller (rev 01)
Subsystem: Dell: Unknown device 01a7
Flags: bus master, medium devsel, latency 64, IRQ 10
Memory at eceff000 (32-bit, non-prefetchable) [size=4K]
I/O ports at dcc0 [size=64]
Capabilities: [dc] Power Management version 2

Bruce Hill 09-25-2005 09:40 AM

As it says in that Dell forum, have you tried as root from a terminal to issue
"modprobe e100" yet? That module is in the 2.4.31 kernel that comes with
Slack-10.2, and you should be able to get it to work just fine.

After you modprobe it check the output of "lsmod" to see if it's there. Then
run as root "netconfig" and see if you can get it working. If not, post back what
commands you ran, and error messages you received.

Also, Google <Linux> for "Intel Corporation 82801G (ICH7 Family) LAN" and see
what you come up with.

mosca 09-25-2005 10:09 AM

Thank you for your reply.

modprobe e100 gives me:

init_module: no such device

and suggests me to look in the syslog or dmesg, but they do not contain anything about it. Maybe I could change the log level, but the default usually is ok...

Same result with ee100pro and similar modules (as suggested by google).

Bruce Hill 09-25-2005 10:39 AM

What is the output of "dmesg | grep eth0" ?
And of "lsmod" ?
And issue "less /usr/src/linux-2.4.31/.config" then you can just press the slash key
and enter Ethernet (/Ethernet ) which should take you to that section of your kernel
configuration file. You should have these (I think) for Intel chipsets:
Code:

CONFIG_EEXPRESS=m
CONFIG_EEXPRESS_PRO=m
<snip>
CONFIG_EEPRO100=m
# CONFIG_EEPRO100_PIO is not set
CONFIG_E100=m

We might also use something in /etc/rc.d/rc.modules, but first we need to know
for sure which chipset this NIC uses.

You might also try issuing "/sbin/lspic -vv" as root, to see if you get any more
information about that NIC. Perhaps you'll have to get that driver from Intel, but
I really don't think so ...

mosca 09-25-2005 10:54 AM

dmesg does not give anything on eth0.

lsmod shows that I've loaded soundcore, ntfs and ide-scsi.

my config file says all the intel ethernet options marked as modules.

In XP (aida32) I see that the NIC is a Intel PRO/100 VE, which should be covered by the e100 module.

mosca 09-25-2005 10:56 AM

lspci -vv does not say much to me:

05:08.0 Ethernet controller: Intel Corporation 82801G (ICH7 Family) LAN Controller (rev 01)
Subsystem: Dell: Unknown device 01a7
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (2000ns min, 14000ns max), cache line size 10
Interrupt: pin A routed to IRQ 10
Region 0: Memory at eceff000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at dcc0 [size=64]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-


All times are GMT -5. The time now is 05:58 PM.