On Tue, May 08, 2001 at 11:17:04AM -0500, Dimitri Maziuk wrote:
> On Tue, May 08, 2001 at 01:42:20PM +0200, Daniel Faller wrote:
> > Hi,
> >
> > I was using kernel 2.4.3 without any problems, but kernel 2.4.4 refuses to
> > boot.
>
> FWIW I have 2.4.4 booting like a charm here. I didn't change
On Wednesday 09 May 2001 15:49, David Wright wrote:
> This may or may not help. The message above looks exactly like what
> you'd expect if sda was an empty Zip drive. If inserting a disk and
> rebooting changes the message, then that's what's happened.
A very strange, but good idea, it did change.
Quoting Daniel Faller ([EMAIL PROTECTED]):
> I am constantly getting:
>
> sda: READ CAPACITY failed
> sda: status=0 message=00 host=0 driver=28
> sda: extended sense code = 2
> block size assumed to be 512 bytes disksize = 1GB
> sda: I/O error: dev 08:00, sector 0.
>
> This happens when I try to
Hi,
I am constantly getting:
sda: READ CAPACITY failed
sda: status=0 message=00 host=0 driver=28
sda: extended sense code = 2
block size assumed to be 512 bytes disksize = 1GB
sda: I/O error: dev 08:00, sector 0.
This happens when I try to boot kernel 2.4.4, kernel 2.4.1 works perfectly,
they a
On Tuesday 08 May 2001 18:17, Dimitri Maziuk wrote:
> On Tue, May 08, 2001 at 01:42:20PM +0200, Daniel Faller wrote:
> FWIW I have 2.4.4 booting like a charm here. I didn't change my
> lilo.conf either.
That's right, I tried it with a different PC at home, and it worked without
any problem with th
On Tue, May 08, 2001 at 01:42:20PM +0200, Daniel Faller wrote:
> Hi,
>
> I was using kernel 2.4.3 without any problems, but kernel 2.4.4 refuses to
> boot.
FWIW I have 2.4.4 booting like a charm here. I didn't change my
lilo.conf either.
> But no success, it refuses to boot and basically tells
On Tue, May 08, 2001 at 02:00:10PM +0200, Daniel Faller wrote:
> On Tuesday 08 May 2001 13:54, you wrote:
> > --- Daniel Faller <[EMAIL PROTECTED]> wrote:
> > Check the name you have for initrd in lilo.conf
> >
> > mkinitrd -o /boot/initrd-2.4.4-686 /lib/modules/2.4.4
> >
On Tuesday 08 May 2001 13:54, you wrote:
> --- Daniel Faller <[EMAIL PROTECTED]> wrote:
> Check the name you have for initrd in lilo.conf
>
> mkinitrd -o /boot/initrd-2.4.4-686 /lib/modules/2.4.4
>
> does not match below
>
> initrd=/boot/initrd-2.4.4 in "/etc/lil
--- Daniel Faller <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I was using kernel 2.4.3 without any problems, but kernel 2.4.4
> refuses to
> boot. I do not think that my kernel Configuration is wrong.
>
> There was a Thread "trouble booting 2.4.4" some
Hi,
I was using kernel 2.4.3 without any problems, but kernel 2.4.4 refuses to
boot. I do not think that my kernel Configuration is wrong.
There was a Thread "trouble booting 2.4.4" some days ago, which suggested to
put:
do_initrd = Yes in "/etc/kernel-img.conf"
and
initr
> "Michael" == Michael P Soulier <[EMAIL PROTECTED]> writes:
Michael> Note that it doesn't mention _how_ to modify your boot
Michael> loader. I guess there are a lot of them, but lilo is
Michael> pretty common...
I have sometimes felt it would be better, if there {lilo,grub} had
h
At 989287374s since epoch (05/07/01 07:02:54 -0400 UTC), Herbert Xu wrote:
> Jason Healy <[EMAIL PROTECTED]> wrote:
> >
> > flexible == good. Unfortunately, there wasn't much warning about it, so I
> > bet a lot of people (and their respective machines) are panicing.
>
> Hmm, I thought the messag
On Mon, May 07, 2001 at 09:02:54PM +1000, Herbert Xu wrote:
> Jason Healy <[EMAIL PROTECTED]> wrote:
> >
> > flexible == good. Unfortunately, there wasn't much warning about it, so I
> > bet a lot of people (and their respective machines) are panicing.
>
> Hmm, I thought the message in the preins
Jason Healy <[EMAIL PROTECTED]> wrote:
>
> flexible == good. Unfortunately, there wasn't much warning about it, so I
> bet a lot of people (and their respective machines) are panicing.
Hmm, I thought the message in the preinst was as prominent as it could be.
Any suggestions on how it can be impr
On Sun, May 06, 2001 at 10:28:37PM -0400, Jason Healy wrote:
>
> Just hit this myself. I'm not at work, so I'm not completely sure how I
> fixed it (and my box is back in windows, so I can't ssh in...)
>
> I do know that it has to do with the new kernel images using initrd to boot.
> This means
At 989201956s since epoch (05/06/01 21:19:16 -0400 UTC), Michael P. Soulier
wrote:
> Hi there. I just installed kernel-image-2.4.4-686 on my P-III.
> Unfortunately, it panics during the boot, saying that it can't find the root
> partition. I have the root option set to /dev/hda4 in my lilo.con
"Michael P. Soulier" wrote:
>
> Hi there. I just installed kernel-image-2.4.4-686 on my P-III.
> Unfortunately, it panics during the boot, saying that it can't find the root
> partition. I have the root option set to /dev/hda4 in my lilo.conf, and I
possible the kernel doesnt support the ide
Hi there. I just installed a binary kernel 2.4.4 on my P-III.
Unfortunately, it panics during the boot, saying that it can't find the root
partition. I have the root option set to /dev/hda4 in my lilo.conf, and I
tried passing that as a boot option, but I had the same problem.
Any idea w
Hi there. I just installed kernel-image-2.4.4-686 on my P-III.
Unfortunately, it panics during the boot, saying that it can't find the root
partition. I have the root option set to /dev/hda4 in my lilo.conf, and I
tried passing that as a boot option, but I had the same problem.
Any idea w
19 matches
Mail list logo
