Bug 189723 - Default hdparm settings applied to DVD burner aren't optimal.
Summary: Default hdparm settings applied to DVD burner aren't optimal.
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 5
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2006-04-23 23:13 UTC by Philippe A
Modified: 2015-01-04 22:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-11-02 03:32:37 UTC

Attachments (Terms of Use)
Requested dmesg output. (13.92 KB, text/plain)
2006-05-30 00:27 UTC, Philippe A
no flags Details
hdparm -i /dev/hdc output (559 bytes, text/plain)
2006-08-01 02:03 UTC, Philippe A
no flags Details

Description Philippe A 2006-04-23 23:13:57 UTC
Description of problem:

Unless I tweak manually my DVD burner settings with hdparm, I get 1X burn speed
in K3B. Video playback from the DVD drive is choppy in mplayer or xine.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

1. Reset drive settings to defaults with hdparm -d0 -c0 -u0 -a256 -k0 /dev/hdc
2. Put an DVD+RW 4X in the drive. Choosing speed Auto or 4X won't change anything.
3. Open K3B and burn some stuff. 


1. Put a DVD movie in drive.
2. Playback with xine or mplayer.
Actual results:

- Burning crawls at 1X.
- DVD playback is choppy.

Expected results:

Burn speed should be 4X. DVD playback should be smooth. Both are obtained by
applying the following options: hdparm -c1 -d1 -u1 -a8 -k1 /dev/hdc

Additional info:

IMO having to play with hdparm to get DVD drive working at optimal performance
is a good example of something that would keep people away from using a Linux

Comment 1 Dave Jones 2006-05-29 04:36:02 UTC
please attach dmesg output (without any manual hdparm having been done).

Comment 2 Philippe A 2006-05-30 00:27:29 UTC
Created attachment 130210 [details]
Requested dmesg output.

Attached is the requested dmesg output.

Comment 3 Dave Jones 2006-07-29 05:56:11 UTC
This doesn't make a great deal of sense, as according to the dmesg, everything
was set up to use dma just fine.  What does hdparm -i /dev/hdc say ?

Comment 4 Philippe A 2006-08-01 02:03:29 UTC
Created attachment 133367 [details]
hdparm -i /dev/hdc output

Comment 5 Dave Jones 2006-09-17 03:25:25 UTC
[This comment added as part of a mass-update to all open FC4 kernel bugs]

FC4 has now transitioned to the Fedora legacy project, which will continue to
release security related updates for the kernel.  As this bug is not security
related, it is unlikely to be fixed in an update for FC4, and has been migrated
to FC5.

Please retest with Fedora Core 5.

Thank you.

Comment 6 Dave Jones 2006-10-17 00:47:17 UTC
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.

Comment 7 Philippe A 2006-11-02 03:32:37 UTC
Default hdparm settings work great in Fedora Core 6. Verified after deactivating
 my hdparm line in rc.local and rebooting.

Note You need to log in before you can comment on or make changes to this bug.