>>> = Stephen Clark
>> = Adam Richter
> = Patrick Ale
>> Do you know if these drives were advertising less capability
>> than they were spec-ed at? Do you recall if the IDE driver without
>> kernel arguments printed its rationale for reverting to the slower
>> setting?
[...]
>Then, afte
Do you know if these drives were advertising less capability
than they were spec-ed at? Do you recall if the IDE driver without
kernel arguments printed its rationale for reverting to the slower
setting?
I can only speak for myself of course.
On boot time the libsata driver detected my
On 2007-02-04 Stephen Clark wrote:
>I have had two different laptops that had to have boot time command line
>overrides to get the
>driver to allow the hardware work at what it was spec-ed at.
Do you know if these drives were advertising less capability
than they were spec-ed at? Do you
Bill Davidsen wrote:
Support for that ioctl could likely be added, but these days I don't
think there's much use for it. I can't see how anybody in their right
mind would want to disable DMA on a modern drive, and if libata turns
it off automatically then there's likely some serious hardware or
Bill Davidsen wrote:
I think deciding to turn off DMA which works fine in old kernels
qualifies as a "serious driver problem," which is why it should be under
user control.
For PATA, perhaps.
For SATA, turning off DMA can often -cause- additional problems.
Jeff
-
To unsubscribe fro
re: hdparm -d
Support for that ioctl could likely be added, but these days I don't
think there's much use for it. I can't see how anybody in their right
mind would want to disable DMA on a modern drive, and if libata turns
it off automatically then there's likely some serious hardware or
driv
Robert Hancock wrote:
Stephen Clark wrote:
Only some of the hdparm functionality is supported in libata, which
is partially by design. Presently there's no way to override the DMA
settings in libata, it starts out at the fastest supported settings
and falls back if it gets too many errors of c
Mark Lord wrote:
Robert Hancock wrote:
..
Only some of the hdparm functionality is supported in libata,
That's not true. MOST hdparm functionality is supported in libata.
Only a very few things are not supported, including -d and -X,
for reasons already pointed out.
Nearly everything else wo
Alan wrote:
Userspace PIO mode changes are NOT a good idea,
I would disagree there, but they are not high priority. We do need to
allow set_features/xfer but we need to snoop it and mode set properly
around it. There are cases you want to control this, more so admittedly
for DMA speeds.
*Bing
\
Userspace PIO mode changes are NOT a good idea,
and I doubt that libata would want to support that feature.
The "-d" flag (enable/disable DMA) is currently not implemented
by libata, though there may be a /sys/.. attribute for it (?).
Okay but... the driver itself does implement the calls, ma
> Userspace PIO mode changes are NOT a good idea,
I would disagree there, but they are not high priority. We do need to
allow set_features/xfer but we need to snoop it and mode set properly
around it. There are cases you want to control this, more so admittedly
for DMA speeds.
-
To unsubscribe fro
Robert Hancock wrote:
..
Only some of the hdparm functionality is supported in libata,
That's not true. MOST hdparm functionality is supported in libata.
Only a very few things are not supported, including -d and -X,
for reasons already pointed out.
Nearly everything else works.
-ml
-
To uns
Patrick Ale wrote:
Hi guys,
Me again, sorry.
Is it possible to make hdparm work with libata?
It already works fine with libata.
..
Anyway, I used to be able to force the drive back with using hdparm
-X68 -d 1 /dev/sdk
Userspace PIO mode changes are NOT a good idea,
and I doubt that libata
On 2/5/07, Robert Hancock <[EMAIL PROTECTED]> wrote:
Patrick Ale wrote:
The southbridge usually runs the PCI bus connected to the slots, so it's
possible that PCI bus issues were causing problems..
Explains a lot then yeah... okay, if the error occures again I will
let you know, I am booting up
Patrick Ale wrote:
Good morning all,
About the reason as of why it drops to PIO mode, I might have found
the reason for this, I am just not sure if what i found is related.
When I opened my Athlon XP machine, took the cables out and replaced
them for new cables, I found out that my southbridge
Good morning all,
About the reason as of why it drops to PIO mode, I might have found
the reason for this, I am just not sure if what i found is related.
When I opened my Athlon XP machine, took the cables out and replaced
them for new cables, I found out that my southbridge fan wasnt
spinning a
On 2/4/07, Stephen Clark <[EMAIL PROTECTED]> wrote:
I have had two different laptops that had to have boot time command line
overrides to get the
driver to allow the hardware work at what it was spec-ed at.
Well, I am sure that someone will at least take the problem I have
serious and will give
Patrick Ale wrote:
On 2/4/07, Stephen Clark <[EMAIL PROTECTED]> wrote:
Robert Hancock wrote:
But why are we taking away the users capability to control his/her own
hardware. Sounds like windows.
I wouldn't go as far as making that comparsion, most of all cause it's
totaly i
On 2/4/07, Stephen Clark <[EMAIL PROTECTED]> wrote:
Robert Hancock wrote:
But why are we taking away the users capability to control his/her own
hardware. Sounds like windows.
I wouldn't go as far as making that comparsion, most of all cause it's
totaly invalid, with all respect.
In my opin
Stephen Clark wrote:
Only some of the hdparm functionality is supported in libata, which is
partially by design. Presently there's no way to override the DMA
settings in libata, it starts out at the fastest supported settings
and falls back if it gets too many errors of certain types.
You sho
Robert Hancock wrote:
Hi guys,
Me again, sorry.
Is it possible to make hdparm work with libata?
I have some drives that for some reason fall back to lower UDMA
settings (like UDMA/44) while the drive is UDMA/100. I blame the way I
set-up my raid arrays for this and the bus not being able to ha
Hi guys,
Me again, sorry.
Is it possible to make hdparm work with libata?
I have some drives that for some reason fall back to lower UDMA
settings (like UDMA/44) while the drive is UDMA/100. I blame the way I
set-up my raid arrays for this and the bus not being able to handle
all the data that g
On Saturday 03 February 2007 09:55:52 Patrick Ale wrote:
> Hi,
>
> The problem is even worse, the drive falls back to PIO mode and there
> is no way I can get it back to dma mode (like I could by using
> hdparm). The only thing i can do is reboot the machine so it will see
> the drive is UDMA capa
Hi,
The problem is even worse, the drive falls back to PIO mode and there
is no way I can get it back to dma mode (like I could by using
hdparm). The only thing i can do is reboot the machine so it will see
the drive is UDMA capable.
If there is some beta/gamma software around or something you'd
24 matches
Mail list logo
