On 06/12/12 12:11, Felix Miata wrote:
On 2012-12-06 11:38 (GMT++1100) Basil Chupin composed:
So my final plea re my hassle is: what do I need to do to get the UDMA correct when using grub2, please?
Grub does not determine how the kernel configures ATA.
I know that! But it is what you put into the parameters for the kernel in grub/grub2 which determines what the damn kernel will do regarding the configuration of the devices' UDMAs.
Progress is unlikely until this registers.
Ce`?
Kernel options are the same regardless which Grub is used to load the kernel.
And so, which parameter I put into ????: 'libata.force=5:80c' or 'force=5:80c'? But the bottom line is why *should* I even think about doing this fiddle in this day age and day? Why does the kernel crap out about the 40-wire thingie when such cables haven't been used for.....how many years?
Did you try moving the SATA cables among the various motherboard ports?
No. But why should I? I expect the kernel to know what the heck it is doing. I am not running any abnormal system which was imported from some planet in a galaxy yet to be discovered - it is a stock standard mobo and cpu, and openSUSE 12.2 which hundreds of other people would have installed (but obviously they just haven't paid attention to how their system is performing :-( ).
If you swap cables, does the problem stay with the HD, or move to the other?
No, haven't done this. But again, while it is an option to try, why should I do this?
Have you used the diagnostic software provided by the HD manufacturer to ensure absence of defects?
This is sounding like the list of mandatory questions any call-centre is given to ask when a customer complains about a service :-( . The HDDs haven't collapsed within the normal 3 months after purchase so there is nothing wrong with them.
Are you sure the external carrier isn't where the problem lies?
What "external carrier"? Surely I could not have "external carrier" problems on 2, or even 3, computers?
This latter is a problem I had: https://bugzilla.novell.com/show_bug.cgi?id=757426 Comments in the bug or its upstream may help you figure out which if any cmdline option will help.
OK, I have had a quick look (and I mean this :-) ) of that 'bug' report but simply cannot fathom why anybody has to go thru this rubbish of reporting such a "bug" when it is simply bad coding in the kernel! BC -- Using openSUSE 12.2 x86_64 KDE 4.9.4 & kernel 3.6.8-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org