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 :(
On 14/05/11 19:35, Jean Delvare wrote:
I had no idea if that would work, I never
needed these parameters and did not go read the documentation either
before suggesting it. Simply, it is what _I_ would have tried next. And
I'm glad it worked.
Sorry to ask: but aren't you somehow connected with the kernel development?
I am. But that doesn't mean I am fully familiar with each of the
13174877 lines of code the sources of the openSUSE 11.4 kernel are
made of. In particular, storage is not my area.
No, I don't. I think (and, in fact, I am eve certain) that you did not
provide enough technical details about your system, and what it as in
common with the similar stories you found on the web.
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.
It is actually very needed.
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.
It is actually totally relevant, and I shall prove it.
I've just booted and connected to 2 of the 4 machines I own that still
have an IDE or PATA drive in them (the other two have no power at the
moment, otherwise I would have checked them too.) I've looked at the
kernel logs for both of them. Here's what I found:
[First system, laptop with Intel ICH3 controller]
hda: ST96812A, ATA DISK drive
hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hda: UDMA/100 mode selected
[Second system, desktop board with Intel ICH5 controller]
ata2.00: ATAPI: PLEXTOR CD-ROM PX-54TA, 1.00, max UDMA/33
ata1.00: ATA-7: Maxtor 6Y080L0, YAR41BW0, max UDMA/133
ata2.00: configured for UDMA/33
ata1.00: configured for UDMA/100
As you can see, both of them get UDMA/100 working, and I did not
have to pass any kernel parameter for this.
So, all my systems work, all yours fail. Either you are cursed, or
your systems have something in common which mine don't.
It doesn't matter which Linux distro I install on
my system, or my
Not surprising as they are all based on the same upstream kernel
project. OTOH, if you acknowledge that the problem is not specific
to openSUSE, then why are you reporting it on an opensuse list
rather than to upstream kernel developers?
wife's, I get the same message showing that the
UDMA has been
incorrectly set because of this "40-wire cable" BS identification by the
Again, I presume your system and your wife's system have something
in common which causes the problem.
You ask me why I didn't notice this before,
No, I don't.
Simple answer is that
I never bothered to look before, and accepted that Linux was "the ants
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.
Maybe this has to do with the fact that M$ engineers don't spend time
answering user questions for free? ;)
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
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.
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
I am not going to get into a pointless discussion with you about the above.
Actually you have just done that :p
You are giving the typical "support desk"
response for which you have
been trained to give.
I have not even been trained. I actually do support for a living, but
not as a support desk agent. I _do_ a lot of user support on
open-source projects though, for free. But thankfully, most of the
time users trust my expertise and provide the information I ask for.
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
Again (as you either did not read or did not understand): you are the
one asking for help, you are the one doing the homework. When you get
help from professionals for free, you have to make things as easy as
possible for them.
contained in those search results. Then after you have
done so, then
come back and tell me that "...what you have is faulty hardware".
This would indeed be my preliminary and unreliable conclusion, based
on the very succinct information you provided.
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org