Date: Wed, 24 Sep 2008 19:20:03 GMT From: "Christophe Cap" <christophe.cap@gmail.com> To: freebsd-i386@FreeBSD.org Subject: Re: i386/122008: [ata] Fdisk fails. Cannot install 7.0 Release on P5VD2-MX with Maxtor PATA [regression] Message-ID: <200809241920.m8OJK3bE047602@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR i386/122008; it has been noted by GNATS. From: "Christophe Cap" <christophe.cap@gmail.com> To: bug-followup@freebsd.org, christophe.cap@gmail.com Cc: Subject: Re: i386/122008: [ata] Fdisk fails. Cannot install 7.0 Release on P5VD2-MX with Maxtor PATA [regression] Date: Wed, 24 Sep 2008 20:50:34 +0200 First of all sorry for the late reply. I did several 'test' install ranging from 4.7 tot 7-current and several Linux Indeed in the end it appeared to be a cable problem (40wire instead of 80 wire). So you can mark this as closed ! What confused me was that both OpenSuse and Ubuntu booted fine without errors nor warnings on that same drive. After severan installs, some googling en setting the loglevel to max (on Linux) I noticed this : ===BEGIN Linux dmesg snippet === ata4: PATA max UDMA/133 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001e408 irq 15 ata4.01: HPA unlocked: 66055248 -> 156301488, native 156301488 ata4.01: ATA-7: MAXTOR STM380215A, 3.AAD, max UDMA/100 ata4.01: 156301488 sectors, multi 16: LBA48 ata4.01: limited to UDMA/33 due to 40-wire cable ata4.01: configured for UDMA/33 ===END Linux dmesg snippet=== Notice how in Linux the cable is detected (somehow) and switches to UDMA/33 instead of UDMA100. So it's slow, but boots errorless. Maybe this cable detection is an idea for future FreeBSD releases ? Thanks for everyone looking into this problem. Best regards, Christophe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200809241920.m8OJK3bE047602>