On Fri, 10 Jan 1997, Fundamental wrote:
>
> Yop, i picked the wrong network driver doh! Now my new dual-processor
> kernel mounts the right drives, and finds the network but just hangs on
>
> Configuring serial devices
>
> The lists esteemed wisdom is sort:)
>
You probably have serial c
On Fri, 10 Jan 1997, Fundamental wrote:
>
> Configuring serial devices
>
I had/have the same problem. The way I got around it was to comment out
the "automatic" configuration stuff in /etc/rc.boot/0setserial and
uncommented the appropriate "manual" configuration stuff.
This took care of
On 8 Jan 1997, Manoj Srivastava wrote:
srivasta >Hmm,
srivasta >
srivasta > /dev/sda1. Well, I wonder if the scsi modules have been
srivasta > compiled in the new kernel? You may have a problem otherwise.
srivasta >
well, this is odd. The machine im compiling on has two scsi drives, when
i
On Wed, 8 Jan 1997, Fundamental wrote:
>
> Okay ive compiled my new kernel, made it bootable from a kickstart disk
> and tried booting - problem, i get a kernel panic. So i just stuck in my
> old 2.0.0 kickstart and she booted up fine.
>
> Im pretty sure the problem is that the new kernel doesn
Fundamental wrote:
>
> On Tue, 7 Jan 1997, Ryan Shaw wrote:
>
> ryans >before writing the new kernel to disk or running lilo on it go into
> ryans >/usr/src/linux/arch/i386/boot or some similar path (can't remember
> exactly
> ryans >what it is at the moment) and find the zImage file. then do a
Hmm,
/dev/sda1. Well, I wonder if the scsi modules have been
compiled in the new kernel? You may have a problem otherwise.
manoj
--
"Oh God ... I'm *shot* ... Hey ... *wait* a second ... I'm *okay*
... Wow! This is *cool! Bullets don't hurt me!" Superboy, #2 of
SUPERBOY THE
On Tue, 7 Jan 1997, Ryan Shaw wrote:
ryans >before writing the new kernel to disk or running lilo on it go into
ryans >/usr/src/linux/arch/i386/boot or some similar path (can't remember
exactly
ryans >what it is at the moment) and find the zImage file. then do a `rdev
ryans >zImage' to see which
On Wed, 8 Jan 1997, Fundamental wrote:
> I know i can fix this by running rdev, but how do i run an rdev on a
> kernel that wont boot?
before writing the new kernel to disk or running lilo on it go into
/usr/src/linux/arch/i386/boot or some similar path (can't remember exactly
what it is at the
8 matches
Mail list logo