On Wed, Nov 14, 2007 at 11:26:06AM -0500, Mark Lord wrote:
> Another way to the same thing is with "hdparm -E",
> which contrary to my earlier posting actually does
> seem to work already with libata.
Hi!
There are DVD-ROM drives that don't react to hdparm -E but do react to
SET_STREAMING, for
Hi Mark!
On Wed, Nov 14, 2007 at 11:41:37AM -0500, Mark Lord wrote:
> Ahh.. got it. The host_status returned (not checked by that code) was 7,
> which means "host error".
>
> In this case, that's because the cmd_len is (16), which is too large for
> ATAPI.
> It needs to be changed to (12)
On Wed, Nov 14, 2007 at 10:09:22AM -0500, Mark Lord wrote:
> I think the problem here might be that libata doesn't actually support
> SG_IO
> for ATAPI drives prior to 2.6.24 (ugh).
>
> Try it with a 2.6.24-rc* kernel from kernel.org, or back-patch the ATA_16
> SG_IO support into your older
On Wed, Nov 14, 2007 at 12:28:59AM +0100, Sebastian Kemper wrote:
> http://svn.mplayerhq.hu/mplayer/trunk/stream/stream_dvd.c?view=markup
>
> See dvd_set_speed(). The drive I'm using is an Optiarc DVD RW AD-7170A.
> With the "old" ATA driver dvd_set_speed() works, with lib
On Wed, Nov 14, 2007 at 12:28:59AM +0100, Sebastian Kemper wrote:
http://svn.mplayerhq.hu/mplayer/trunk/stream/stream_dvd.c?view=markup
See dvd_set_speed(). The drive I'm using is an Optiarc DVD RW AD-7170A.
With the old ATA driver dvd_set_speed() works, with libata it doesn't.
Hello Alan
On Wed, Nov 14, 2007 at 10:09:22AM -0500, Mark Lord wrote:
I think the problem here might be that libata doesn't actually support
SG_IO
for ATAPI drives prior to 2.6.24 (ugh).
Try it with a 2.6.24-rc* kernel from kernel.org, or back-patch the ATA_16
SG_IO support into your older kernel.
Hi
Hi Mark!
On Wed, Nov 14, 2007 at 11:41:37AM -0500, Mark Lord wrote:
Ahh.. got it. The host_status returned (not checked by that code) was 7,
which means host error.
In this case, that's because the cmd_len is (16), which is too large for
ATAPI.
It needs to be changed to (12) instead.
I
On Wed, Nov 14, 2007 at 11:26:06AM -0500, Mark Lord wrote:
Another way to the same thing is with hdparm -E,
which contrary to my earlier posting actually does
seem to work already with libata.
Hi!
There are DVD-ROM drives that don't react to hdparm -E but do react to
SET_STREAMING, for
Hi Alan!
On Tue, Nov 13, 2007 at 09:22:30PM +, Alan Cox wrote:
> It isn't a known issue, and it suprises me as SG_IO basically passes
> commands through to the drive. We don't support speed change via xfermode
> setting but GPCMD_SET_STREAMING sohuld behave.
>
> Do you have a simple code
Hi all,
while trying to limit the speed of DVD drives during DVD playback I've
come under the impression that GPCMD_SET_STREAMING via SG_IO doesn't yet
work with libata/PATA (AMD/NVIDIA PATA support). I tested on an NForce2
board (all IDE, no SATA) and kernel 2.6.22.12. When I use the "old" ATA
Hi all,
while trying to limit the speed of DVD drives during DVD playback I've
come under the impression that GPCMD_SET_STREAMING via SG_IO doesn't yet
work with libata/PATA (AMD/NVIDIA PATA support). I tested on an NForce2
board (all IDE, no SATA) and kernel 2.6.22.12. When I use the old ATA
Hi Alan!
On Tue, Nov 13, 2007 at 09:22:30PM +, Alan Cox wrote:
It isn't a known issue, and it suprises me as SG_IO basically passes
commands through to the drive. We don't support speed change via xfermode
setting but GPCMD_SET_STREAMING sohuld behave.
Do you have a simple code example
Am Mittwoch, 15. August 2007 18:49:07 schrieben Sie:
> Linux kernel version 2.6.22.3 has been released. It is available from:
> ...
> The following files were changed in this release:
>
> Makefile |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Obviously something went wrong.
-
To
Am Mittwoch, 15. August 2007 18:49:07 schrieben Sie:
Linux kernel version 2.6.22.3 has been released. It is available from:
...
The following files were changed in this release:
Makefile |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Obviously something went wrong.
-
To
Hello all,
I get these warnings compiling rc4 (see attached out.log file). I'm used
to warnings compiling my (vanilla) kernels, but these look more
suspicious than usual to me.
If this is nothing to worry about, please disregard. Otherwise please
CC.
Regards
Sebastian
--
"When the going
Hello all,
I get these warnings compiling rc4 (see attached out.log file). I'm used
to warnings compiling my (vanilla) kernels, but these look more
suspicious than usual to me.
If this is nothing to worry about, please disregard. Otherwise please
CC.
Regards
Sebastian
--
When the going
On Mon, Apr 30, 2007 at 03:34:29PM +0200, Michal Piotrowski wrote:
> Sebastian, please test both patches.
> http://bugzilla.kernel.org/attachment.cgi?id=11331=view
> http://bugzilla.kernel.org/attachment.cgi?id=11332=view
Hello,
I applied both patches and the kernel panic doesn't happen anymore.
On Mon, Apr 30, 2007 at 03:34:29PM +0200, Michal Piotrowski wrote:
Sebastian, please test both patches.
http://bugzilla.kernel.org/attachment.cgi?id=11331action=view
http://bugzilla.kernel.org/attachment.cgi?id=11332action=view
Hello,
I applied both patches and the kernel panic doesn't happen
Hello list,
this is an old issue, I reported it to
http://bugzilla.kernel.org/show_bug.cgi?id=5410 in 2005, but it still
bothers me. My mouse light (simple Logitech USB mouse) still stays on
after shutdown with 2.6.21-rc7.
But, headway has been made (a little). It turned out that I don't have
Hello list,
this is an old issue, I reported it to
http://bugzilla.kernel.org/show_bug.cgi?id=5410 in 2005, but it still
bothers me. My mouse light (simple Logitech USB mouse) still stays on
after shutdown with 2.6.21-rc7.
But, headway has been made (a little). It turned out that I don't have
On Thursday 01 February 2007 07:13, you wrote:
> Sebastian Kemper wrote:
> > But now /proc/mtrr shows 256MB of video ram, same as lspci, whereas
> > the real amount of video ram (as properly detected by X) is only
> > 128MB.
>
> The size of the aperture doesn't have
Hello list,
I read about the changes regarding the mtrr code in the upcoming 2.6.20
kernel and so today I tried rc7.
Since quite some time I had warning messages like
mtrr... overlaps existing...
whenever I started up Xorg with DRI enabled. This doesn't happen anymore
with 2.6.20-rc7.
But
Hello list,
I read about the changes regarding the mtrr code in the upcoming 2.6.20
kernel and so today I tried rc7.
Since quite some time I had warning messages like
mtrr... overlaps existing...
whenever I started up Xorg with DRI enabled. This doesn't happen anymore
with 2.6.20-rc7.
But
On Thursday 01 February 2007 07:13, you wrote:
Sebastian Kemper wrote:
But now /proc/mtrr shows 256MB of video ram, same as lspci, whereas
the real amount of video ram (as properly detected by X) is only
128MB.
The size of the aperture doesn't have to match the actual amount of
memory
On Fri, Dec 01, 2006 at 03:32:47PM -0800, [EMAIL PROTECTED] wrote:
> On Fri, Dec 01, 2006 at 03:29:22PM -0800, Pete Zaitcev wrote:
> > On Fri, 1 Dec 2006 15:23:39 -0800, [EMAIL PROTECTED] wrote:
> >
> > > BIOS handoff assumes an SMI, right? Could SMI be masked?
> >
> > That might be a bad idea,
On Fri, Dec 01, 2006 at 02:03:59PM +0100, Sebastian Kemper wrote:
> Hello all,
>
> I sometimes get this message when I boot kernel 2.6.19. Could this be
> related to the BIOS option "USB keyboard support"? When I turn it off I
> never get the "handoff fai
Hello all,
I sometimes get this message when I boot kernel 2.6.19. Could this be
related to the BIOS option "USB keyboard support"? When I turn it off I
never get the "handoff failed" message afaik. But I need it to access
lilo. Now I use an USB->PS2 adapter and turn "USB keyboard support" off.
Hello all,
I sometimes get this message when I boot kernel 2.6.19. Could this be
related to the BIOS option USB keyboard support? When I turn it off I
never get the handoff failed message afaik. But I need it to access
lilo. Now I use an USB-PS2 adapter and turn USB keyboard support off.
If
On Fri, Dec 01, 2006 at 02:03:59PM +0100, Sebastian Kemper wrote:
Hello all,
I sometimes get this message when I boot kernel 2.6.19. Could this be
related to the BIOS option USB keyboard support? When I turn it off I
never get the handoff failed message afaik. But I need it to access
lilo
On Fri, Dec 01, 2006 at 03:32:47PM -0800, [EMAIL PROTECTED] wrote:
On Fri, Dec 01, 2006 at 03:29:22PM -0800, Pete Zaitcev wrote:
On Fri, 1 Dec 2006 15:23:39 -0800, [EMAIL PROTECTED] wrote:
BIOS handoff assumes an SMI, right? Could SMI be masked?
That might be a bad idea, because
30 matches
Mail list logo
