On Sat, 21 May 2011 00:36:01 +1000
Basil Chupin
I see no requirement to provide any "technical details" about my system because what my system is all about I have already described, and it matters not a pinch of horse manure as to what it is because it has been identified that the kernel has a problem and this problem has not been resolved since some 3 years ago.
What "my system" has or not in common "with similar stories [I] found on the web" has absolutely nothing to do with the price of fish.
Yes it has something to do with it. Because it is not like it is broken on all the systems out there. It is something about your system. Probably the specific IDE chip your system is using. Either the chip, the board design or the driver has an issue. It might simply be the chip not being able to detect an 80 pin cable and the kernel thus defaulting to a safe value. It might be the board design, that disallows the chip, even though it would be able to detect an 80 pin cable if hooked up correctly, to detect the cable. It might be the driver, simply not having implemented the function to detect the cable. Believe me: I still have ~8 machines with IDE drives. All of them run with UDMA >=66 and none of them needs such a kernel parameter.
pants" when it comes to being "with it". I now know different - and to make this knowledge worse is that contrary to what the "geek" people claim that it takes M$ months or longer to get right is takes Linux KERNEL people YEARS to get resolved. Rather sad I would think.
That's unrelated. For a Microsoft OS you probably have to install the "Vendor drivers" from your motherboard vendor anyway, and they have probably just hardwired that value. At least they could have solved it that way. Would be interesting if a plain Windows installation with stock drivers does work as well.
I'm not the one doing the google search, because _you_ are the one asking for help. So you are the one who should be summarizing your findings, and giving enough details for us to help you.
100% agree with Jean
In this specific case, what you should have told us was: what your hardware (IDE controller) is, and what your system has in common with the many similar reports you found by googling. I guess that the common point is the IDE controller chip, but to properly help you, it's better to start with facts rather than guesses. And maybe there are other factors, such as the hard disk drives you're using, or some kernel configuration option, or the brand of the motherboard.
You claim that there is a bug in the kernel for over 3 years. You can't expect it to get fixed if people affected by it just pass the proper module parameter and don't make proper bug reports.
My guess if that what you have is faulty hardware, and the kernel can't work around this, and that's why the "bug" was never fixed - because it's not a kernel bug. But again, this is just a guess, by lack of technical details.
<Sigh>
I am not going to get into a pointless discussion with you about the above.
It's not pointless. It's like taking your car to a mechanic and telling him "it does not drive nicely". When he asks in which way it does "not drive nicely", you tell "search for other stories of not nicely driving cars on google". Not helpful.
Read my original post, read your response, read my response (above), do a search on the search parameter(s) I already gave you, read what is contained in those search results.
If 3 People on 3 places on the world place the same search terms into google, they will get three different sets of results. This is only one of the problems with your approach.
(I have counted to 20 so far.....am holding on to my temper....and so I shall now finish this post :-) .)
Wow, if this is how you write a polite post, I don't want to see an impolite one. Just for the record: I found your mails to be pretty impolite and normally I probably would have just mumbled "What an a..." to myself and have hit Shift-Delete. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org