LinHES Forums http://forum.linhes.org/ |
|
Setup impressions Knoppmyth and Mythdora http://forum.linhes.org/viewtopic.php?f=14&t=14189 |
Page 1 of 1 |
Author: | moloth [ Thu Feb 15, 2007 9:16 am ] |
Post subject: | Setup impressions Knoppmyth and Mythdora |
Every now and again I try to setup a myth tv box just to see how it is progressing and lately I have been really surprised. I am a big fan of both knoppmyth and mythdora for making such an easy way to get your mythbox up and going. I still have a few minor issues but I am happy to say that yes most thing are working. I downloaded both from files.bigpond which made life easy! Here is my setup on my old hardware: System Setup System: AMD 2800 (2083MHz) runing on an Asus Motherboard (Piece of crap MB! Lan and Sound Dead) TV Card: DVICO FusionHDTV Dual DVB-T Remote: Fusion MCE Remote that came with the card. This remotes ir receiver is plugged into the card via what looks like a sound jack. The card was a little expensive at the time ($300) but i wanted two tuners so i could record while watching. Anyway i tried this setup using both distros: MythDora 3.2 http://g-ding.tv I tried this first as i very familiar with fedora having used it since version 3. Again I am still a linux newbie but can find my way around and I like using gnome. I had very similar problems in both knoppmyth and mythdora. Install was straight forward. After the initial setup i was greeted with a familiar desktop. Linux detected 1 of my 2 tuners and the remote didn't work. Time to poke around in linux. I headed over to /dev/ and found that yes dvb was there. so: cd /dev/dvb unfortunatly only /dev/dvb/adapter0 was there. So I had a look around on the forums to see what i was supposed to see. Looks like the second tuner is a usb one (this is why you have to plug the usb loop back into your card). Maybe it was some usb device... /dev/hiddev0 not there /dev/usb not there There was a /dev/bus/usb/001/003 that would disapear and reapear each time i removed the usb loop back thingy. A site suggested that i type in dmesg and look for anything interesting: Code: cx88[0]/0: found at 0000:00:0b.0, rev: 5, irq: 18, latency: 32, mmio: 0xbd000000 cx88[0]/0: registered device video0 [v4l2] cx88[0]/0: registered device vbi0 ACPI: PCI Interrupt 0000:00:0b.2[A] -> GSI 19 (level, low) -> IRQ 18 cx88[0]/2: found at 0000:00:0b.2, rev: 5, irq: 18, latency: 32, mmio: 0xbc000000 cx88[0]/2: cx2388x based dvb card DVB: registering new adapter (cx88[0]). DVB: registering frontend 0 (Zarlink MT352 DVB-T)... does the /2 mean that it can see the second reciever? Personally i think it is detecting the composite (aerial) and svideo in. dmesg should show it detecting the second reciever each time i plug it in right? So here goes. I unplug the usb cord and plaug it back in... and this appears at the bottom of my dmesg: Code: usb 1-2: USB disconnect, address 2
usb 1-2: new high speed USB device using ehci_hcd and address 3 usb 1-2: config 1 has an invalid descriptor of length 1, skipping remainder of the config usb 1-2: config 1 has 0 interfaces, different from the descriptor's value: 1 usb 1-2: configuration #1 chosen from 1 choice Oh crap.. this kernel or the modules don't know about my second tuner?!? This also doesn't bode well for my remote because under windows if i unplug my usb loopback the remote stops working. Checking the kernel version they are running 2.6.18... 2.6.20 is out but i wont be installing that and making a mess of things. At least i have 1 tuner working and I set up using the following: #mythtv-setup Capture Card Setup - Works This setup found my channels. Although the name of my card was incorrect. Card Type: DVB DTV capture card (v3.x) Dvb Card Number: 0 Frontend: Zarlink MT352 DVB-T Capure Card Setup - Mis-configurations These configs didn't work. Firstly trying to find the second tuner: Card Type: DVB DTV capture card (v3.x) Dvb Card Number: 1 Frontend: Could not open card number 1 --- Try different drivers, This detected the name of my card correctly but failed to find any channels. Card Type: pcHDTV DTV capture card (w/V4L drivers) video devcice: /dev/video0 (yes /dev/video0 exists) Name: DViCO FusionHDTV DVB-T Dual Dig [cx8800] Live TV Woohoo at least my channels were detected. And it found all of them! Up pops mythfrontend so i hit live tv. What a disapointment the tv was coming through choppy. Looks like about 2-3 fps (dunno how to check exactly what this is - any ideas?) Okies lets check to see if my video card was working properly. I have in an elcheapo ATI card and checked out how to install it at: http://news.softpedia.com/news/How-to-I ... 8740.shtml one of the lines to determine if it is working properly is: #glxinfo | grep direct direct rendering: Yes Cool it is working properly....but unfortunatly this is the last straw. I am not watching choppy tv. Time to see if knoppmyth is any better KnoppMyth R5E50 http://www.mysettopbox.tv/knoppmyth.html This is a smaller distro. It can fit onto 1CD. Not that it really matters cause i burn everything to dvd now anyway to get better read times. Installation was good except it looked like a few things failed in the setup. Like when it asked for an american zip code for weather or something. Again only 1 tuner was detected and the remote didnt work. same dmesg saying it dint know what was plugged in. /dev/dvb/adapter0 was the only 1 there. Same myth-setup. All the chanels were detected so there was only 1 thing left to do. check out live tv. Live TV OMG! The tv was coming through crystal clear at full frame rate! Well im going to have a play with this one now but there are still a few annoyances: #1 No browser except for lynx (yuck) and mythbrowser. I will work out how to get firefox on there hopefully. Or need to work out mythbrowser better. Doesnt work like I think it should. How do you type in an address... shouldn't the arrow keys allow you to edit the url? #2 my remote and second tuner still dont work. -- On a side note i disable the au_tv_grabber and use the following HOWTO to update my tv listings: SITE: http://tvguide.org.au HOWTO at http://minnie.tuhs.org/twiki/bi...w/TVGuide/MythTV -- My Questions are: 1. Is it possible for me to setup the second tuner? 2. Is it possible to get the remote working? |
Author: | moloth [ Thu Feb 15, 2007 10:50 am ] |
Post subject: | Checking round on the forums |
After reading this thread http://mysettopbox.tv/phpBB2/viewtopic.php?t=12397 I found this: http://www.linuxtv.org/download/dvb/fir ... bird-01.fw but still gives the same usb error from dmesg: Code: usb 1-2: USB disconnect, address 2
usb 1-2: new high speed USB device using ehci_hcd and address 3 usb 1-2: config 1 has an invalid descriptor of length 1, skipping remainder of the config usb 1-2: config 1 has 0 interfaces, different from the descriptor's value: 1 usb 1-2: configuration #1 chosen from 1 choice Checked the remote was working in windows and it is. Still cant fire this baby up in knoppmyth?? |
Author: | cecil [ Thu Feb 15, 2007 1:51 pm ] |
Post subject: | |
So, does KnoppMyth win hands down over MythDora?! ![]() |
Author: | moloth [ Thu Feb 15, 2007 8:39 pm ] |
Post subject: | |
Found this over at linuxtv... perhaps i am putting the firmware in at the wrong place? Dont know: http://linuxtv.org/wiki/index.php/DVICO http://linuxtv.org/wiki/index.php/DVB_U ... onHDTV_USB --- DViCO FusionHDTV USB This class of usb devices is codenamed, Bluebird. All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices: - lgdt330x.ko - mt352.ko - zl10353.ko - dvb-usb.ko - dvb-usb-cxusb.ko These frontend(s)/demodulator(s) can be found in various revisions of this device: - LG Electronics DT3303 - Zarlink MT352 - Zarlink ZL10353 device/model type firmware name comments/quirks URL/pictures DViCO FusionHDTV 5 USB Gold USB2.0 dvb-usb-bluebird-01.fw [90] DViCO FusionHDTV USB DVB-T USB2.0 dvb-usb-bluebird-01.fw There is a working Mac driver written by John Dalgliesh. http://www.defyne.org [91] DViCO FusionHDTV DVB-T Dual USB USB2.0 dvb-usb-bluebird-01.fw [92] --- Also here is a picture of my card: http://www.fusionhdtv.co.kr/ENG/Product ... gital.aspx |
Author: | moloth [ Thu Feb 15, 2007 9:22 pm ] |
Post subject: | |
Here is the output from lsusb Code: #lsusb
Bus 005 Device 002: ID 0fe9:db50 DVICO Bus 005 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 #lsusb -v Bus 005 Device 002: ID 0fe9:db50 DVICO Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize0 64 idVendor 0x0fe9 DVICO idProduct 0xdb50 bcdDevice 1.00 iManufacturer 0 iProduct 0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 171 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 100mA Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize0 64 bNumConfigurations 1 Device Status: 0x0000 (Bus Powered) *snip |
Author: | moloth [ Fri Feb 16, 2007 8:58 am ] |
Post subject: | |
when i ran lsmod I noticed that these last two drivers werent loaded.. is the usb driver supposed to load them when it is plugged in? moloth wrote: All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:
- lgdt330x.ko - mt352.ko - zl10353.ko - dvb-usb.ko - dvb-usb-cxusb.ko I loaded them manually using: Code: insmod /lib/modules/2.6.18-chw-13/kernel/drivers/media/dvb/dvb-usb/dvb-usb.ko
insmod /lib/modules/2.6.18-chw-13/kernel/drivers/media/dvb/dvb-usb/dvb-usb-cxusb.ko Is there anyway to make this permanent? Not that it seemed to make a difference when i plugged the usb back in. |
Author: | moloth [ Fri Feb 16, 2007 10:23 am ] |
Post subject: | |
At the top of this page: http://linuxtv.org/wiki/index.php/DVB_U ... onHDTV_USB it says that i need to make sure that these modules are loaded: Quote: For all devices shown below you need to load (if not compiled into the kernel):
- i2c-core --already loaded - crc32 -- Not Loaded - firmware_class --already loaded - dvb-core.ko --already loaded - dvb-pll.ko --already loaded and maybe others too. If the loading fails for any particular module you'll get a "unkown symbol"-message. Then take a look at dmesg to find out, which symbols (functions) are missing. After you've found out which module was absent, please come back here and add it to the list/device-entry. I can find modules crc16 and libcrc32c but not crc32. perhaps I need a newer kernel? oh and instead of the insmod lines you can just use: Code: modprobe dvb_usb
modprobe dvb_usb_cxusb . |
Author: | moloth [ Fri Feb 16, 2007 11:24 am ] |
Post subject: | IT Works!!!!!!!!!!!!!!!!!!! |
Woohooo! Finally found my problem.. and it is so simple: edit /etc/modprobe.d/aliases change the line Code: alias char-major-81-* videodev
to alias char-major-81-* cx8800 /dev/dvb now shows adapter0 and adapter1 cat /dev/input/event2 now shows data when the remote is used only took me 4 days ![]() oh yea... you don't have to do those modprobe lines either! |
Author: | moloth [ Fri Feb 16, 2007 9:49 pm ] |
Post subject: | Oh Smeg...then Success! |
Booted the thing up this morning and it was failing to work again... piece of *^%^. So again when i unplugged the usb and plugged it back in I had the dmesg: Code: usb 5-4: USB disconnect, address 2 usb 5-4: new high speed USB device using ehci_hcd and address 3 usb 5-4: config 1 has an invalid descriptor of length 1, skipping remainder of the config usb 5-4: config 1 has 0 interfaces, different from the descriptor's value: 1 usb 5-4: configuration #1 chosen from 1 choice So I reset my /etc/modprobe.d/aliases back to normal because this was now not the fix... it was more likely some fluke... but now I know it can detect the damn hardware. Looking at the error I noticed ehci_hcd which i think is the usb2.0 driver. So I did this: rmmod ehci_hcd then the dmesg said this: Code: ehci_hcd 0000:00:10.4: remove, state 1 usb usb5: USB disconnect, address 1 usb 5-4: USB disconnect, address 3 ehci_hcd 0000:00:10.4: USB bus 5 deregistered ACPI: PCI interrupt for device 0000:00:10.4 disabled usb 2-2: new full speed USB device using uhci_hcd and address 2 usb 2-2: configuration #1 chosen from 1 choice dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual USB' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-bluebird-01.fw' usbcore: registered new driver dvb_usb_cxusb usb 2-2: USB disconnect, address 2 dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. usb 2-2: new full speed USB device using uhci_hcd and address 3 usb 2-2: configuration #1 chosen from 1 choice dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual USB' in warm state. dvb-usb: This USB2.0 device cannot be run on a USB1.1 port. (it lacks a hardware PID filter) dvb-usb: DViCO FusionHDTV DVB-T Dual USB error while loading driver (-19) dvb_usb_cxusb: probe of 2-2:1.0 failed with error -22 OOh that looks promising! but it is still having errors... uhci_hcd looks like the usb1.1 driver?? and this is a usb2.0 device. Ok we will put the ehci_hcd driver back in. modprobe ehci_hcd then dmesg: Code: PCI: Enabling device 0000:00:10.4 (0010 -> 0012)
ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI 21 (level, low) -> IRQ 19 ehci_hcd 0000:00:10.4: EHCI Host Controller ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 5 ehci_hcd 0000:00:10.4: irq 19, io mem 0xbb000000 ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb5: configuration #1 chosen from 1 choice hub 5-0:1.0: USB hub found hub 5-0:1.0: 8 ports detected usb 5-4: new high speed USB device using ehci_hcd and address 2 usb 5-4: configuration #1 chosen from 1 choice dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual USB' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (DViCO FusionHDTV DVB-T Dual USB). DVB: registering frontend 1 (Zarlink MT352 DVB-T)... input: IR-receiver inside an USB DVB receiver as /class/input/input2 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: DViCO FusionHDTV DVB-T Dual USB successfully initialized and connected. usb 2-2: USB disconnect, address 3 Woohoo! now the question is why does this work? Do the drivers have to be loaded in a certain order? and how do you do this? |
Page 1 of 1 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |