4.{8,9,10} Install ad0 READ command error

2004-05-21 Thread Richard Caley

I can't install 4.X on a couple of identical new machines. They both
exhibit the same problem, and it's consistant, so it's probably not
bad hardware, though perhaps weird hardware. Also, 5.2 does install,
but these are to be production machines at a remote location so I'd
really rather be running something long in the tooth.

I've googled and looked at the FBDS mailing lists and here and have
found some similar sounding reports, but no fix.

I need to make a decision on these machines for next week, and if I
can't bring myself to go with 5.X I may have to try linux, so if
anyone can come up with a way forward with 4.X in the next day or two
it would be a really Good Thing:-).

OK, details:

The disk is there, visible and will boot (to DOS in one case, to FBSD
5.2 in the other).

I boot from CD and it goes through the normal sequence to boot the
install kernel until it looks at the hard disk (copied from a screen
on
the other end of the room, so excuse typoes/brainoes):

ad0 sucess setting WDMA2 on SIS chip
Creating disk ad0
ad0 READ command timeout tag=0 serv=0 resetting ...
ata0 resetting devices

And then nothing for as close to forever as I have been prepared to
wait.

The motherboard is an ASRock KS41

Chipset:SIS 741 + SIS 963L

Athalon 2400+


Can't think of anything else relevent.


-- 
[EMAIL PROTECTED]   _O_
 |

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 4.{8,9,10} Install ad0 READ command error

2004-05-21 Thread Ion-Mihai Tetcu
On Fri, 21 May 2004 11:57:07 +0100 (BST)
Richard Caley [EMAIL PROTECTED] wrote:

 And then nothing for as close to forever as I have been prepared to
 wait.
 
 The motherboard is an ASRock KS41
 
 Chipset:SIS 741 + SIS 963L
 
 Athalon 2400+
 
 
 Can't think of anything else relevent.

HDD model and firmware version would be useful.

-- 
IOnut
Unregistered ;) FreeBSD user

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 4.{8,9,10} Install ad0 READ command error

2004-05-21 Thread Richard Caley
  The motherboard is an ASRock KS41
  Chipset:SIS 741 + SIS 963L
  Athalon 2400+

 HDD model and firmware version would be useful.

The HDD is a maxtor 6Y080P0 The BIOS is AMI and identifies itself as
K7S41 P1.10.

As a matter of interest, I have had a very similar problem on a
mini-PC which I had put down to a hardware fault, but maybe there is a
new(ish) motherboard chipset out there which 4.X can't cope with but
5.X can?

If it is of any relevance/use, 4.5-RELEASE does manage to boot as far
as the installer, and locks up on Probing Devices.

The only symptom under 5.2 is the disk geometry warning at the start
of partitioning which I have recieded in more or less every FBSD
installation for the past couple of years. Someone really should
rewrite that, since it seems impossible not to get it, and doesn't
actually seem to indicate a problem.

-- 
[EMAIL PROTECTED]   _O_
 |

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 4.{8,9,10} Install ad0 READ command error

2004-05-21 Thread Ion-Mihai Tetcu
On Fri, 21 May 2004 14:20:42 +0100 (BST)
Richard Caley [EMAIL PROTECTED] wrote:

   The motherboard is an ASRock KS41
   Chipset:SIS 741 + SIS 963L
   Athalon 2400+
 
  HDD model and firmware version would be useful.
 
 The HDD is a maxtor 6Y080P0 The BIOS is AMI and identifies itself as
 K7S41 P1.10.

FYI on a VIA 8237 this Maxtor woks
 ad0: Maxtor 6Y120L0/YAR41BW0 ATA-7 disk at ata0-master

But of course this means nothing ;-/ I've had problems with identical
HDD but different firmware versions.

Did you tried with another HDD ? Does the HDD work on another mobo ?

  As a matter of interest, I have had a very similar problem on a
 mini-PC which I had put down to a hardware fault, but maybe there is a
 new(ish) motherboard chipset out there which 4.X can't cope with but
 5.X can?

This could be possible due to acpi support in 5.x; but of course it can
happen also the other way. Did you tried to boot with acpi disable ?



-- 
IOnut
Unregistered ;) FreeBSD user

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 4.{8,9,10} Install ad0 READ command error

2004-05-21 Thread Richard Caley
 Did you tried with another HDD ? Does the HDD work on another mobo ?

Don't really want to mess with the hardware too much. These are
supposed to be identical machines to deliver quickly to a customer as
a stop-gap. I'll try with a spare HD this evening, but basicly I just
want to get something going on these machines as is as soon as
possible, so unless someonone somewhere has a brilliant idea I'll flip
a coin between the pain fo Linux and the worry of 5.2.

 This could be possible due to acpi support in 5.x; but of course it can
 happen also the other way. Did you tried to boot with acpi disable ?

Can I do that from the 4.X install CD? Everything seems to be disabled
in the BIOS, not that there is much.

-- 
[EMAIL PROTECTED]   _O_
 |

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 4.{8,9,10} Install ad0 READ command error

2004-05-21 Thread Ion-Mihai Tetcu
On Fri, 21 May 2004 15:16:56 +0100 (BST)
Richard Caley [EMAIL PROTECTED] wrote:

  Did you tried with another HDD ? Does the HDD work on another mobo ?
 
 Don't really want to mess with the hardware too much. These are
 supposed to be identical machines to deliver quickly to a customer as
 a stop-gap. I'll try with a spare HD this evening, but basicly I just
 want to get something going on these machines as is as soon as
 possible, so unless someonone somewhere has a brilliant idea I'll flip
 a coin between the pain fo Linux and the worry of 5.2.

Hmm, that is a way to go; if you do it, get a dmesg from it and post it
on current@ it might help.

 
  This could be possible due to acpi support in 5.x; but of course it can
  happen also the other way. Did you tried to boot with acpi disable ?
 
 Can I do that from the 4.X install CD? Everything seems to be disabled
 in the BIOS, not that there is much.

Nop, I was speaking about 5.x.


-- 
IOnut
Unregistered ;) FreeBSD user

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]