Very Computer

Can you please help me with this one?

I have just downloaded the Kernel 2.4.16 (SuSe certified).
It is the first time that I tried to upgrade the kernel (config-compile
etc).
The version I had was the one included in SuSe 7.3 (2.4.10-4GB).
I did some changes to the .config file (via xconfig) but I didn't change
anything on the
filesystems section.

The result is that during xconfig, dep, clean, bzImage, modules, lilo, and
modules_install I HAD NO PROBLEMS what so ever.
When I tried to reboot the machine, it started loading and then stopped
(halted).
The last 5 messages are:

FAT: bogus logical sector size 65422
FAT: bogus logical sector size 65422
UDF-fs: No partitions found (1)
Kernel Panic: VFS: Unable to mount root fs on 03:43
    spurious 8259A interrupt: IRQ7

and then stops....

I tried to reconfigure the filesystems section (on xconfig) but I didn't
find anything related to VFS (unless it is there with another name OR if I
am blind! :o   )

I am a newbie with Linux and SuSe in particular.

Can you please tell me what is the problem and how can I fix it?
I have NO IDEA what these messages mean (apart from UDF).
....and what is the last message about the IRQ?!?!? It' sounds worrying!

NOTE: When I installed 7.3 in the first place I had NO problems and no error
messages about IRQs etc.
I just wanted to upgrade the kernel in order to install my SoundBlaster
Audigy!

PLEASE help!

Many thanks!
Chris

On Wednesday 29 May 2002 16:12, Chris, purporting to be

Quote:> Can you please help me with this one?

> I have just downloaded the Kernel 2.4.16 (SuSe certified).
> It is the first time that I tried to upgrade the kernel (config-compile
> etc).
> The version I had was the one included in SuSe 7.3 (2.4.10-4GB).
> I did some changes to the .config file (via xconfig) but I didn't change
> anything on the
> filesystems section.

> The result is that during xconfig, dep, clean, bzImage, modules, lilo, and
> modules_install I HAD NO PROBLEMS what so ever.
> When I tried to reboot the machine, it started loading and then stopped
> (halted).
> The last 5 messages are:

> FAT: bogus logical sector size 65422
> FAT: bogus logical sector size 65422
> UDF-fs: No partitions found (1)
> Kernel Panic: VFS: Unable to mount root fs on 03:43
>     spurious 8259A interrupt: IRQ7

> and then stops....

> I tried to reconfigure the filesystems section (on xconfig) but I didn't
> find anything related to VFS (unless it is there with another name OR if I
> am blind! :o   )

> I am a newbie with Linux and SuSe in particular.

> Can you please tell me what is the problem and how can I fix it?
> I have NO IDEA what these messages mean (apart from UDF).
> ....and what is the last message about the IRQ?!?!? It' sounds worrying!

> NOTE: When I installed 7.3 in the first place I had NO problems and no
> error messages about IRQs etc.
> I just wanted to upgrade the kernel in order to install my SoundBlaster
> Audigy!

> PLEASE help!

> Many thanks!
> Chris

Probably you did not run /sbin/lilo after editing /etc/lilo.conf.

GRUB does not need the stuff.

 I did !
But in order to be SURE I will do it again and I will let you know.

Thanks for the advice anyway!
What is VFS?

Quote:> Can you please help me with this one?

> I have just downloaded the Kernel 2.4.16 (SuSe certified).
> It is the first time that I tried to upgrade the kernel (config-compile
> etc).
> The version I had was the one included in SuSe 7.3 (2.4.10-4GB).
> I did some changes to the .config file (via xconfig) but I didn't change
> anything on the
> filesystems section.

> The result is that during xconfig, dep, clean, bzImage, modules, lilo, and
> modules_install I HAD NO PROBLEMS what so ever.
> When I tried to reboot the machine, it started loading and then stopped
> (halted).
> The last 5 messages are:

> FAT: bogus logical sector size 65422
> FAT: bogus logical sector size 65422
> UDF-fs: No partitions found (1)
> Kernel Panic: VFS: Unable to mount root fs on 03:43

This looks a bit weird...

How is your disk partitioned?

The FAT (MS-DOS) file system tries to look at a partition, and gets sick
parameters from it.

The kernel tries to mount the file system root at a /dev/hdx partition which
obviously does not exist.

Quote:>     spurious 8259A interrupt: IRQ7

This is usually a sign of a mis-behaving hardware interrupt: it chickens out
before the processor has had an opportunity to see what interrupt it was.
The behaviour can be created by a grossly wrong device driver.

Quote:> I tried to reconfigure the filesystems section (on xconfig) but I didn't
> find anything related to VFS (unless it is there with another name OR if I
> am blind! :o   )

VFS stands for Virtual File System - it is the master of all file systems in
Linux. The real file systems, e.g. ext2, vfat, iso9600 etc, are driven by
the VFS.

Boot the computer with the old kernel and show what fdisk says about your
hard disk. Also, the contents of the file system table or the output of an
empty mount command will help.

HTH

Tauno Voipio

Is the filesystem supported in the kernel? Not as a module, but built
in? I had this problem when I upgraded to reiserfs.

Liz

On Wed, 29 May 2002 17:35:06 +0100

Virtual File System. This is an interface between the kernel and the
filesystem drivers.

It would be good if you posted your lilo.conf or grub.conf file.

Vilmos

I concentrate on the next-to-last line.
Somehow, your kernel is unable to mount your root
partition on /dev/hdb3 (which is the "translation"
of the hex major and minor numbers).

Well, is /dev/hdb3 your root partition, or is it
somewhere else? (Should be found automatically during
the kernel compile, but who knows?). You didn't compile
your kernel on a different system (with a different root
part.) than the one you try to boot?

More possibilities follow: If /dev/hdb3 _is_ your true
root partition, and it fails mounting nevertheless,
then you must be missing either some HW drivers for
your HDD partition - i.e. IDE/ATA general driver and
IDE/ATA block device driver. I consider that very unlikely;
or did you really forget to include both drivers?

If your kernel does support IDE and IDE hard disks,
the next step: Which file system is used on /dev/hdb3?
Please post your /etc/fstab to us.
If the fs is something other than the default ext2,
you must also include the driver for that fs, either
statically, or in the initrd.
Check your /usr/src/linux/.config for the relevant
fs driver (ext3? reiserfs? xfs?).
If you load the resp. driver from initrd, you must
configure a new initrd, according to the setting
of the variable "INITRD_MODULES=..." in
/etc/sysconfig/kernel. What is your actual value?
Does it match your fstab? And, probably most
important, did you run 'mk_initrd' after the
kernel compilation? If you didn't, this might be the
core of your problem.

Regards,

Juergen