* kernel compilation problem
@ 2003-12-23 10:46 joy
0 siblings, 0 replies; 6+ messages in thread
From: joy @ 2003-12-23 10:46 UTC (permalink / raw)
To: linux-newbie
Hi,
I was compiling the 2.4.18 kernel as a practice run and when I booted
thru it I recieved a message during boottime:
Kernel panic: VFS unable to mount root fs on 03:05.
any clues why?
I run the Debian woody release.
also when I boot thru my working kernel, I get a message during boottime:
spurious 8259A interrupt : IRQ7
any ideas?
thanx in advance,
Joy.M.M
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: kernel compilation problem
@ 2003-12-23 13:46 Pacheco Jason NPRI
0 siblings, 0 replies; 6+ messages in thread
From: Pacheco Jason NPRI @ 2003-12-23 13:46 UTC (permalink / raw)
To: Linux-Newbie (linux-newbie@vger.kernel.org)
> Hi,
> I was compiling the 2.4.18 kernel as a practice run and when I booted
> thru it I recieved a message during boottime:
> Kernel panic: VFS unable to mount root fs on 03:05.
> any clues why?
Did you copy over your /usr/src/linux/System.map file into /boot? Also,
did you build an initial ramdisk via mkinitrd? A lot of times that last
step is overlooked but is necessary because it loads the initial drivers
needed to mount the hard disk partitions.
> I run the Debian woody release.
> also when I boot thru my working kernel, I get a message
> during boottime:
> spurious 8259A interrupt : IRQ7
> any ideas?
I just recently built my first Debian system and I get the same error,
except I think the number is different. The system was a junk testbed, so
I figured it was my piece of garbage mobo, which his a Soyo K7ADA+. Anyway,
the error doesn't seem to cause a problem other than having that annoying
message popup here and there, but I would like to figure out how to solve
it as well.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: kernel compilation problem
[not found] <3BEEE23D31CAD2118D920008C75D8946059FF59E@NPRI54EXC21.NPT.N UWC.NAVY.MIL>
@ 2003-12-23 16:51 ` Ray Olszewski
2003-12-24 4:45 ` joy
0 siblings, 1 reply; 6+ messages in thread
From: Ray Olszewski @ 2003-12-23 16:51 UTC (permalink / raw)
To: linux-newbie
At 08:46 AM 12/23/2003 -0500, Pacheco Jason NPRI wrote:
> > Hi,
> > I was compiling the 2.4.18 kernel as a practice run and when I booted
> > thru it I recieved a message during boottime:
> > Kernel panic: VFS unable to mount root fs on 03:05.
> > any clues why?
Where is the host's actual root filesystem? 03:05 says the kernel is
looking for it on /dev/hda5 ... is that the right place or not? (It's not
typical for a Debian install, but not impossible either.)
If it is correct -- what filesystem type is it? (ext2, most likely). Make
sure your kernel has support for that filesystem type compiled in.
If it is incorrect -- what partition should it be? Are you compiling the
kernel on the same system you are trying to boot it on? What happens if you
specify the correct partition at the lilo (or grub or whatever you use for
a bootloader) prompt? Are you booting from hda?
>Did you copy over your /usr/src/linux/System.map file into /boot? Also,
>did you build an initial ramdisk via mkinitrd? A lot of times that last
>step is overlooked but is necessary because it loads the initial drivers
>needed to mount the hard disk partitions.
No it's not. It is only necessary if the kernel does not have ide support
compiled in (not usual) or dos not have support for your filesystem type
compiled in (again unusual, if the filesysystem is ext2). Typical,
"vanilla" systems do not need the initrd step to boot/init.
> > I run the Debian woody release.
[rest omitted]
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: kernel compilation problem
2003-12-23 16:51 ` Ray Olszewski
@ 2003-12-24 4:45 ` joy
2003-12-24 6:46 ` Beolach
0 siblings, 1 reply; 6+ messages in thread
From: joy @ 2003-12-24 4:45 UTC (permalink / raw)
To: Ray Olszewski; +Cc: linux-newbie, PachecoJ
Sorry to find a trivial answer to the Q. The settings were alright .
thanks a lot , Jason and Ray, All I needed to do was to to copy the
System.map as this Kernel does not use the other two System.map(s) in
/boot (they are for kernels compiled with diff options).
But still ,I would like to get rid of the irritating
spurious 8259A interrupt : IRQ7
message I get on Boottime.
I run an athlon 2400+ , with a biostar nforce2 mobo and the normal
peripherals, nothing out of the ordinary.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: kernel compilation problem
2003-12-24 4:45 ` joy
@ 2003-12-24 6:46 ` Beolach
0 siblings, 0 replies; 6+ messages in thread
From: Beolach @ 2003-12-24 6:46 UTC (permalink / raw)
To: gracecott; +Cc: linux-newbie
joy wrote:
> Sorry to find a trivial answer to the Q. The settings were alright .
> thanks a lot , Jason and Ray, All I needed to do was to to copy the
> System.map as this Kernel does not use the other two System.map(s) in
> /boot (they are for kernels compiled with diff options).
> But still ,I would like to get rid of the irritating
> spurious 8259A interrupt : IRQ7
> message I get on Boottime.
> I run an athlon 2400+ , with a biostar nforce2 mobo and the normal
> peripherals, nothing out of the ordinary.
>
The spurious 8259A interrupt error is an incredibly common and
non-dangerous error message. Most likely it is caused by the
uniprocessor APIC (Advanced Programmable Interupt Conrtoller) linux
code. It's really not dangerous or bad or anything. But if you really
do want to get rid of it, try recompiling the kernel without
uniprocessor APIC support ("Local APIC support on uniprocessors" in make
menuconfig). This should get rid of the message.
A couple good references for this issue are:
<http://www.linuxchix.org/pipermail/techtalk/2002-August/012697.html>
and this thread on the LKML (Linux Kernel Mailing List):
<http://www.cs.helsinki.fi/linux/linux-kernel/2001-47/0697.html>
HTH,
Conway S. Smith
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: kernel compilation problem
@ 2003-12-24 13:22 Pacheco Jason NPRI
0 siblings, 0 replies; 6+ messages in thread
From: Pacheco Jason NPRI @ 2003-12-24 13:22 UTC (permalink / raw)
To: Linux-Newbie (linux-newbie@vger.kernel.org)
> The spurious 8259A interrupt error is an incredibly common and
> non-dangerous error message. Most likely it is caused by the
> uniprocessor APIC (Advanced Programmable Interupt Conrtoller) linux
> code.
I blame the sunspots...
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2003-12-24 13:22 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-12-23 10:46 kernel compilation problem joy
-- strict thread matches above, loose matches on Subject: below --
2003-12-23 13:46 Pacheco Jason NPRI
[not found] <3BEEE23D31CAD2118D920008C75D8946059FF59E@NPRI54EXC21.NPT.N UWC.NAVY.MIL>
2003-12-23 16:51 ` Ray Olszewski
2003-12-24 4:45 ` joy
2003-12-24 6:46 ` Beolach
2003-12-24 13:22 Pacheco Jason NPRI
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox