mythbuntu-bugs team mailing list archive
-
mythbuntu-bugs team
-
Mailing list archive
-
Message #01806
[Bug 211594] Re: pcHDTV HD3000 is not detected properly during setup
I've tried 10.04 RC server. cx88 modules seem to load, and dmesg shows
the cards (I have 2), but after configuring under DVB in mythtv-setup,
it says it can't get card info and scanning gives an error that it can't
open the card.
I haven't tried the workaround from the original bug report, but the
same hardware configuration worked a couple weeks ago with Mythbuntu
9.04.
I'm using 10.04 RC server with mythtv-backend and mythtv-database
installed and firmware copied to /lib/firmware.
I've also tried 9.10 server with the same configuration, and 10.04 RC
server as an upgrade from 9.10 (rather than a clean install). All gave
the same results.
--
pcHDTV HD3000 is not detected properly during setup
https://bugs.launchpad.net/bugs/211594
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Triaged
Bug description:
First, let's start with my hardware:
- Asus K8N-E motherboard
- nVidia 6200 video card
- pcHDTV HD3000 tuner
I have installed the Mythbuntu 8.04 Beta at least half a dozen times and have observed:
When I get into the Myth configuration process, Step 2 (Capture Card setup), if I take the default settings (V4L) then the HD3000 is properly detected and works. If I change the selection to DVB (to use the HD3000 in ATSC mode) the HD3000 is not detected; for 'Frontend ID' I get 'Could not get card info for card #0 Subty'. (The message is clipped by the dialog box frame, not by the screen edge.)
If I:
1) take the default V4L
2) complete all of the setup (through Step 4)
3) reboot
4) launch setup again
then I can edit the Capture Card, change it to DVB, and the HD3000 will be correctly detected and will work. If I edit the Capture Card during the initial setup (without rebooting) then it still isn't detected.
I don't know whether this is a Mythbuntu bug or a MythTV bug.