On 05/25/2011 08:19 AM, Basil Chupin wrote:
-------- Original Message -------- Subject: Re: [opensuse-kernel] PATA devices being configured with wrong UDMA Date: Mon, 23 May 2011 17:47:48 +1000 From: Basil Chupin
To: opensuse-kernel@opensuse.org On 21/05/11 01:35, Jean Delvare wrote:
Hi Basil,
Le vendredi 20 mai 2011 16:36, Basil Chupin a écrit :
(Won't go into reasons, but it has to do with openSUSE and audio and pulseaudio and getting different results when installing the same copy of 11.4/KDE on the same system.......but let's not get into this one right now, OK? :-D .) Don't tell me about sound and pulseaudio :(
I won't ever again, I promise (until the next time) :-) .
More seriously, comparisons like this are very difficult to establish, and are often biased by personal experience.
Out of curiosity, did you try a different operating system on the same hardware, to see if it was doing any better with UDMA speed detection?
I had no intention of this going into some sort of a bun-fight over what seems to be a simple matter - and I still have no intention of this going into such a state.
I asked a simple question which was about what was the correct format to use in the "libata.force" statement to get both PATA channels working with an 80-wire cable; to show why I was asking the question I gave an extract from the boot.msg log file as well as making the comment that this hassle with the kernel incorrectly deciding that the machine was using a 40-wire cable has been known since at least 2008.
I received from you the answer as to what was the correct format to use for this over-riding kernel parameter. Wonderful! But then the (unintended) "fight" started :-D .
To save space and time what I deliberately omitted from my original post was that I had the following configuration a couple of weeks before I posted my question:
PATA #1 : WD HD with UDMA 133 LG CDROM with UDMA 33
PATA #2: Seagate with UDMA 100 Pioneer DVD-RW UDMA 100
and the kernel was giving me the correct UDMA settings for PATA #1 (UDMA 133/33) [NOTE: 133/33] *without* any "libata fix" but I had to use "libata.force=2:80c" to get the correct UDMA set for PATA #2.
This was all fine until I had to replace the LG CDROM (UDMA 33) with the new Pioneer DVD-RW which has UDMA 100.
(And this one is for Stefan: NOTE that the UDMA was set correctly on PATA #1 *without* any "libata" fiddles for #1 - so, the chip is working fine, right?)
When I did replace the LG CDROM on PATA #1 with a new Pioneer DVD-RW - so that I now had the Maxtor UDMA 133 with the DVD-RW UDMA 100 - the kernel decided that I had a 40-wire cable connected on PATA #1 and made both devices UDMA 33.
PATA #2 was still correctly set (to 100/100) by the entry of "libata.force=2:80c".)
This is when I posted my message of help for the correct format of the wording to get BOTH channels set to the correct UDMA by the kernel.
I would advise getting in touch with Tejun Heo