Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Rep:
ogle & mplayer intermitternt freezing frames
Has anybody had any trouble with frames getting frozen every 1-2 seconds for a fraction of a second while playing DVDs? I have a 2.0G processor, 512M of RAM and 16x DVD drive. Since both players have the same problem, I was checking to see it was the CPU not being capable of decoding the frames, but the load never exceeded 50% at any point of time.
When I look at the dvd drive LED, it lights up exactly at the instant the frame freezes ( audio does not break at this point ) and it keeps on doing it every couple of seconds. What looks like the reason is a disk-read-wait here. Can I increase the 'read-buffer-size' or 'read-block-size' or something of the sort, so the software doesnt have to wait to get some more data from the drive before it can decode & render it?
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Original Poster
Rep:
Thanks NSKL. DMA did it!!
Could you run hdparm -tT on your dvd drive and post it? My buffered disk reads seem to be on the slow side, so I want to compare it with someone else's to see if there's some tuning left to be done. Are you using UltraDMA?
/dev/dvd:
Timing buffer-cache reads: 128 MB in 0.54 seconds =237.04 MB/sec
Timing buffered disk reads: 64 MB in 17.72 seconds = 3.61 MB/sec
Originally posted by nxny Adding the -k1 option to hdparm preserves state over 'soft' boots.
For Redhat, add
hdparm -d1 -k1 /dev/cdrom
line in /etc/rc.d/rc.local to preserve state over 'hard' boots.
well setting k in rc.local seems a bit bizarre seeing as the whole point of the k flag means you don't need to load them in rc.local.... the k flag stores it's settings in /etc/sysconfig/harddisks which is read by rc.sysinit on each boot, hard or soft.
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Original Poster
Rep:
Quote:
Originally posted by acid_kewpie well setting k in rc.local seems a bit bizarre seeing as the whole point of the k flag means you don't need to load them in rc.local.... the k flag stores it's settings in /etc/sysconfig/harddisks which is read by rc.sysinit on each boot, hard or soft.
I would like to see them stored somewhere, but dont know where. BTW, the following in an except from the hdparm man page
-k Get/set the keep_settings_over_reset flag for the drive. When this flag is set, the driver will preserve the -dmu options over a soft reset, (as done during the error recovery sequence). This flag defaults to off, to prevent drive reset loops which could be caused by combinations of -dmu settings. The -k flag should therefore only be set after one has achieved confidence in correct system operation with a chosen set of configuration settings. In practice, all that is typically necessary to test a configuration (prior to using -k) is to verify that the drive can be read/written, and that no error logs (kernel messages) are generated in the process (look in /var/adm/messages on most systems).
-K Set the drive's keep_features_over_reset flag. Setting this enables the drive to retain the settings for -APSWXZ over a soft reset (as done during the error recovery sequence). Not all drives support this feature.
And my /etc/sysconfig/hardisks ( Redhat Stock ) is practically empty - all lines commented out. No trace of the changes I made to the DVD drive. Which makes me wonder if hdparm identifies my DVD drive as a non-fixed disk and treats in differently. Do you think?
whenever I run hdparm I get command not found. I have the man pages for it so I assume that I have it. What is the command in RH 8.0?
thanks for the help
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Original Poster
Rep:
Quote:
Originally posted by acid_kewpie look for /sbin/hdparm you're presuambly screwing up your path when you su to root. that's assuming you are root of course.
yeah, try
su -
That should execute /etc/profile inside the su shell and change the path to root's.
Nevermind. I talked to some guy at Red Hat. He gave me a line to enter into etc/modules.conf. It's what you have to do to assign DMA in RH 8.0. The line for anyone curious is: options ide-cdrom dma=1
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.