> 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 li
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
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
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 filesyst
> 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 initi
