It seems Dag-Erling Smørgrav wrote:
> Soren Schmidt <[EMAIL PROTECTED]> writes:
> > Well, the ATA driver has just grown more standard compliant :)
> > You *must* hang around for 31secs to wait for slow devices to come ready,
> > according to the ATA specs. Now I've gone to great length before to
>
Soren Schmidt <[EMAIL PROTECTED]> writes:
> Well, the ATA driver has just grown more standard compliant :)
> You *must* hang around for 31secs to wait for slow devices to come ready,
> according to the ATA specs. Now I've gone to great length before to
> get around this by using clever heuristics,
Aloha!
Terry Lambert wrote:
Joachim Strömbergson wrote:
So now the tousand dollar question becomes "What in the boot contains a
timeout around 30 seconds, a timout that lately has been
committed/ctivated in the kernel code?"
SCSI has one of these; are you compiling with ATAPICAM?
Nope. No ATAPICA
Joachim Strömbergson wrote:
> So now the tousand dollar question becomes "What in the boot contains a
> timeout around 30 seconds, a timout that lately has been
> committed/ctivated in the kernel code?"
SCSI has one of these; are you compiling with ATAPICAM?
-- Terry
_
It seems Joachim Strömbergson wrote:
> > Thanks! I guess I'm too impatient these days... Yes, it works after waiting
> > for about 30 seconds. So a correction, it doesn't hang, it's just slow when
> > detecting :).
>
> So now the tousand dollar question becomes "What in the boot contains a
> ti
--On Wednesday, September 17, 2003 00:24:06 +0200 Arjan van Leeuwen
<[EMAIL PROTECTED]> wrote:
On Tuesday 16 September 2003 23:33, Joachim Strömbergson wrote:
Aloha!
Arjan van Leeuwen wrote:
> If I start my kernel from september 15, my computer hangs after this
> message:
>
> atapci0: port 0x
Aloha!
Arjan van Leeuwen wrote:
On Tuesday 16 September 2003 23:33, Joachim Strömbergson wrote:
Try again and see if it is a real, solid hang, or if it just takes a while.
Thanks! I guess I'm too impatient these days... Yes, it works after waiting
for about 30 seconds. So a correction, it doesn't
On Tuesday 16 September 2003 23:33, Joachim Strömbergson wrote:
> Aloha!
>
> Arjan van Leeuwen wrote:
> > If I start my kernel from september 15, my computer hangs after this
> > message:
> >
> > atapci0: port 0xa400-0xa40f at device
> > 7.1 on pci0
> > ata0: at 0x1f0 irq 14 on atapci0
> > ata0: [
Aloha!
Arjan van Leeuwen wrote:
If I start my kernel from september 15, my computer hangs after this message:
atapci0: port 0xa400-0xa40f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
Did you wait a while? I just completed my system update (getting the
OpenSSH patch in
--On Tuesday, September 16, 2003 23:09:57 +0200 Arjan van Leeuwen
<[EMAIL PROTECTED]> wrote:
If I start my kernel from september 15, my computer hangs after this
message:
atapci0: port 0xa400-0xa40f at device
7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
A kernel from september
If I start my kernel from september 15, my computer hangs after this message:
atapci0: port 0xa400-0xa40f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
A kernel from september 7 works normally. A normal dmesg is attached. Anything
I can try?
Arjan
Copyright (c) 1992-20
11 matches
Mail list logo
