Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 119869 - mplayer-bin dvb can't detect tuner type
Summary: mplayer-bin dvb can't detect tuner type
Status: RESOLVED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: AMD64 Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-21 15:17 UTC by Ryan Olf
Modified: 2006-10-27 12:27 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Olf 2006-01-21 15:17:45 UTC
When trying to open a dvb stream, mplayer-bin gives the following error:
--------------------------------
MPlayer 1.0pre7try2-3.3.5-20050130 (C) 2000-2005 MPlayer Team
CPU: Advanced Micro Devices  (Family: 8, Stepping: 0)
Detected cache-line size is 64 bytes
CPUflags:  MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1
Compiled with runtime CPU detection - WARNING - this is not optimal!
To get best performance, recompile MPlayer with --disable-runtime-cpudetection.

85 audio & 196 video codecs
CommandLine: '-v' 'dvb://KRON-SD'

*snip*

Playing dvb://KRON-SD.
FE_GET_INFO error: 22, FD: 4

DVB_CONFIG, can't detect tuner type of card 0, skipping
DVB_CONFIG, can't open device /dev/dvb/adapter1/frontend0, skipping
DVB_CONFIG, can't open device /dev/dvb/adapter2/frontend0, skipping
DVB_CONFIG, can't open device /dev/dvb/adapter3/frontend0, skipping
DVB CONFIGURATION IS EMPTY, exit
Failed to open dvb://KRON-SD

*snip*
--------------------------------

mplayer (64 bit), has no problem detecting the tuner type (but has other problems that I'd like to see if mplayer-bin can help me get around):
--------------------------------
MPlayer 1.0pre7try2-3.4.4 (C) 2000-2005 MPlayer Team
CPU: Advanced Micro Devices  (Family: 8, Stepping: 0)
Detected cache-line size is 64 bytes
CPUflags:  MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1
Compiled for x86 CPU with extensions: MMX MMX2 3DNow 3DNowEx SSE SSE2

85 audio & 196 video codecs
CommandLine: '-v' 'dvb://KRON-SD'

*snip*

Playing dvb://KRON-SD.
TUNER TYPE SEEMS TO BE DVB-ATSC

*snip*
--------------------------

They seem to be the same version of mplayer, but compiled with different versions of gcc and maybe different USE flags?  My mplayer use flags are:
--------------------------
[ebuild   R   ] media-video/mplayer-1.0_pre7-r1  (-3dfx) (-3dnow) (-3dnowext) +X +aac -aalib +alsa (-altivec) +arts -bidi -bindist -bl -cdparanoia -cpudetection -custom-cflags -debug -dga +directfb -doc -dts -dv +dvb +dvd +dvdread -edl +encode -esd +fbcon -ggi +gif -gtk -i8x0 +ipv6 -jack -joystick +jpeg -libcaca -lirc -live -livecd -lzo +mad -matroska -matrox (-mmx) (-mmxext) +mythtv -nas -nls +nvidia +opengl +oss +png -real +rtc +samba +sdl (-sse) (-sse2) (-svga) -tga -theora +truetype -v4l -v4l2 +vorbis (-win32codecs) -xanim -xinerama -xmms +xv +xvid +xvmc 0 kB
---------------------------

The mplayer-bin ebuild version is media-video/mplayer-bin-1.0_pre7-r3
Comment 1 Ryan Olf 2006-02-28 20:53:41 UTC
Update:  still having the same problem with mplayer-bin.  But there's more, which may help explain the problem (though I still can't explain it.)

I tried installing mplayer in a 32bit chroot with exactly the same USE flags... same problem.  So I set up a bootable 32bit system with exactly the same USE flags.  I boot into it, recompile mplayer, and mplayer dvb runs fine.  If I mount that SAME SYSTEM as a chroot (making sure /proc /dev and my home are mounted in the chroot) I get the same "can't detect tuner type" error as in mplayer-bin.  Can anyone explain this?
Comment 2 Daniel Gryniewicz (RETIRED) gentoo-dev 2006-10-06 09:06:06 UTC
The kernel dvb drivers are apparently not cross-bit safe.  There's not a whole lot I can do about it, unfortunately.  I don't even have access to any dvb hardware.
Comment 3 Steve Dibb (RETIRED) gentoo-dev 2006-10-27 12:27:25 UTC
slightly old bug, please test w/newer versions and report back if same issue is still present.

thanks, Ryan