Change History (9)
comment:1 by , 20 years ago
Status: | new → assigned |
---|
comment:2 by , 20 years ago
Owner: | changed from | to
---|---|
Status: | assigned → new |
Summary: | MPlayer 1.0pre6 → MPlayer 1.0pre6 RTC Issues |
comment:3 by , 20 years ago
Just in case you do not know already: MPlayer needs the RTC to run at 1024 Hz to be able to use it, and the message is only a warning - it will cost a bit of performance if it can't use it, nothing more. Three known solutions: disable RTC via configure (bad idea IMHO) or add echo 1024 > /proc/sys/dev/rtc/max-user-freq to the startup script or ignore those messages ;-)
comment:4 by , 20 years ago
Cc: | added |
---|
comment:5 by , 20 years ago
Just a reminder for after 6.0, this should be fixed correctly by the sysctl script. 'echo "dev.rtc.max-user-freq=1024" >> /etc/sysctl.conf' echo is good when only changing one value.
comment:6 by , 20 years ago
Owner: | changed from | to
---|
comment:7 by , 20 years ago
Status: | new → assigned |
---|
comment:8 by , 20 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Updated BLFS to MPlayer-1.0pre6, however there is an issue with MPlayer wanting regular users to have access to /dev/rtc and then after giving that access, MPlayer complains that the value of /proc/sys/dev/rtc/max-user-freq is too low (needs to be 1024).
These issues are currently being discussed in blfs.dev