[linux-dvb] CX88 (HVR-3000) -- strange errors in dmesg
Hi, I've just noticed an absolute ton of these messages in dmesg, can anyone tell me what's going on, or what they mean? [ 123.404000] cx88[0]: irq pci [0x1000] brdg_err* [ 123.404000] cx88[0]: irq pci [0x1000] brdg_err* [ 123.412000] cx88[0]: irq pci [0x1000] brdg_err* [ 123.412000] cx88[0]: irq pci [0x1000] brdg_err* (repeat ad nauseum) Kernel 2.6.22-14-generic, Hg 11fdae6654e8 with HVR-3000 patches from dev.kewl.org/hauppauge merged in manually. Thanks, -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] CX88 (HVR-3000) -- strange errors in dmesg
hermann pitton wrote: looks like you need the last patches from Guennadi. http://marc.info/?l=linux-videor=1b=200803w=2 Most important is that one in the middle. [PATCH] Fix left-overs from the videobuf-dma-sg.c conversion to generic DMA Thanks - that seems to have fixed it. Thanks, -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Nicolas Will wrote: My Ubuntu-provided 2.6.22 works fine. And I am not losing any tuner. Not even with the Multirec of MythTV 0.21. Right, well I've had enough of Ubuntu 8.04a2 (and I've learned a valuable lesson about not using alpha OSes on production systems). This is mostly down to my own actions, though -- the kernel is utterly hosed, the nVidia driver won't load, and the HVR-3000 is refusing to talk (instead insisting that the demux chip isn't talking). I've backed the system off to 7.10 (Gutsy) and it seems stable -- I had to modify the patch from http://dev.kewl.org/hauppauge/ to apply on the latest Hg source... Much fun. It seems to work, so I'll probably publish the repository tomorrow some time (after the day I've had I don't feel like doing much of anything). Plus I'd rather like to see if it works before I go unleashing it on the masses at large. I'm just waiting for ScanDVB to finish making a channels.conf for ASTRA 28.2E, after that I'll see if I can crash the T500 :) -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Sid Boyce wrote: Regarding the NVidia module, NVidia themselves haven't yet conjured up a fix for the latest kernels. [snip] This was on 2.6.24 -- once I downgraded to 2.6.22, just about everything that could break, did. For bonus points, none of the packages would recompile either (but maybe I was being stupid). Like said, it was easier to just hose it down and start over. I've got the following kopts enabled for the DVB modules: == [EMAIL PROTECTED]:~$ cat /etc/modprobe.d/dvb-options # enable LNA for Hauppauge Nova-T-500 options dvb-usb-dib0700 force_lna_activation=1 # disable IR remote for Nova-T-500 (and other USB-DVB IRCs) options dvb-usb disable_rc_polling=1 # force card order -- DiB0700 (Nova-T-500) first, then CX88 (HVR-3000). # also creates virtual i/f 10 so Myth can see the Freeview hybrid install cx88-dvb /sbin/modprobe dvb-usb-dib0700; /sbin/modprobe --ignore-install cx88-dvb; mkdir -p /dev/dvb/adapter10; ln -sf /dev/dvb/adapter2/demux1 /dev/dvb/adapter10/demux0; ln -sf /dev/dvb/adapter2/dvr1 /dev/dvb/adapter10/dvr0; ln -sf /dev/dvb/adapter2/frontend1 /dev/dvb/adapter10/frontend0; ln -sf /dev/dvb/adapter2/net1 /dev/dvb/adapter10/net0 == At the moment both of the Nova-T-500's tuners are recording live TV, and the HVR-3000 is in DVT-T mode and recording too. No problems yet, but uptime is only 75 minutes. It's got a massive list of things to record overnight (think stress test), so fingers crossed. The only USB disconnect warning in dmesg is from when I unplugged the USB mouse after I got the R/C working. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] MT2266 I2C write failed, usb disconnet, WinTV Nova-TD stick, remote
Bernhard Albers wrote: [ 628.492000] hub 4-0:1.0: port 9 disabled by hub (EMI?), re-enabling... [ 628.492000] usb 4-9: USB disconnect, address 2 [ 628.50] MT2266 I2C write failed [ 628.50] MT2266 I2C write failed [ 650.208000] dvb-usb: error while stopping stream. Maybe it is a problem of the mainboard. It is an Asus m2a-vm hdmi (amd690g chipset and ati x1250 onboard graphics) with the latest Bios (1604). Interesting theory... I'm seeing the same thing on a Biostar TA690G mainboard, which uses the same chipset. It works fine on my desktop machine though (VIA K8T800PRO chipset; ASUS A8V Deluxe) and on my ASUS Eee (can't remember off-hand what chipset that uses, an Intel one of some description IIRC). Had some strange signal issues with the Nova-TD-Stick too - Tuner 0 worked fine, but Tuner 1 failed to lock onto the mux that carries FilmFour. Putting a 6dB attenuator inline fixed that nicely -- seems the low-noise amplifier in the Microtune chip sets its level based on an average of the whole band it's tuned to. Lots of strong signals = low amplification = not much signal strength going into the DiBcom decoder/demux chip. Weaken some of the strong signals, and it's fine. Most peculiar. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
[EMAIL PROTECTED] wrote: Not sure if this helps or adds that much to the discussion... (I think this was concluded before) But I finally switched back to kernel 2.6.22.19 on March 5th (with current v4l-dvb code) and haven't had any problems with the Nova-t 500 since. Running mythtv with EIT scanning enabled. Is this a distribution kernel, or one built from virgin (i.e. unmodified from www.kernel.org or one of the mirrors) source code? Is there any possibility of you uploading your .config file somewhere? I'm curious what kernel options you have set.. especially USB_SUSPEND (USB autosuspend -- not sure if this was added to 2.6.24 or if .22 had it as well; I don't have a .22 source tree at the moment). I'm building a kernel from the 2.6.24.2 virgin source on Ubuntu to do some testing; I'd like to prove that the problem exists in 2.6.24 proper before screaming kernel bug. But if 2.6.22 works, a bug is looking more and more likely. Thanks, -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Updated scan file for uk-EmleyMoor
Philip Pemberton wrote: rights Mux A (650MHz, C43) should be disappearing as it's the weakest... this UKFreeTV is wrong again.. Mux D should be disappearing first, because it most certainly IS the weakest at only 4kW ERP vs. the 10kW ERP of the other muxes... Grr.. My point still stands though - why should one tuner pick up a different set of muxes when both are fed from the same signal? -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Updated scan file for uk-EmleyMoor
Here's a scan file for Emley Moor with the correct frequencies and tuning parameters... Seems the one in the linux-dvb distribution has frequencies with a -133kHz or so offset, and without the correct QAM parameters. Probably my fault, because IIRC I submitted that tuning file... Data sourced from www.ukfree.tv, and works fine on my HVR-3000. # Emley Moor, West Yorkshire # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 62600 8MHz 2/3 3/4 QAM64 2k 1/32 NONE T 65000 8MHz 2/3 3/4 QAM64 2k 1/32 NONE T 67400 8MHz 3/4 3/4 QAM16 2k 1/32 NONE T 69800 8MHz 3/4 3/4 QAM16 2k 1/32 NONE T 70600 8MHz 3/4 3/4 QAM16 2k 1/32 NONE T 72200 8MHz 3/4 3/4 QAM16 2k 1/32 NONE -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Hauppauge Nova T-500 / Nova-TD Stick (DiBcom tuners/demods) - the plot thickens...
Henrik Beckman wrote: My TD stick never worked as it should in my Nforce 4, killed my USB controllers. Worked ok on my VIA controller. I've just tested it on an ASUS Eee PC (Intel chipset) and it seems to be fine, one tuner active and playing video, the other scanning for channels. What I did find interesting was that it really doesn't like strong signals. I rigged it up on our test bench at work (we have a UK terrestrial feed that's trimmed to the same signal power around the building, +/- a few dB). I clocked the signal at 70.1dBuV with a Promax DVB analyser, and the Nova-TD refused to lock on -- the tuner locked, but no data flowed (filter timeout pid... from scandvb). In fact, it only passed data along after I put 21dB worth of attenuators (three 3dBs and a pair of 6dBs) in line, bringing the signal strength down to 48dBuV. The maximum signal strength that allowed any signal was 60.8dBuV... Naturally, it's behaving itself with my aerial (pointed at Emley Moor) and doing a far better job than the Freecom USB stick I bought it to replace. This is with Fedora 8, kernel 2.6.23.15-137.fc8. I've got a 2.6.23 kernel building on the Ubuntu box, and I'm digging through the Fedora patches in the 2.6.23.15 kernel source RPM (and the kernel config) to see if there are any significant differences that might explain the issues with the T500 / TD. Not sure that stick is proved 100% stable. Seems stable here... Thanks, -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Hauppauge Nova T-500 / Nova-TD Stick (DiBcom tuners/demods) - the plot thickens...
Hi guys, I've just bought a Nova-TD stick to replace the Nova-T-500 (which really doesn't seem to want to play nice) and as soon as I enabled EIT scanning in MythTV, I got this in dmesg: [ 2780.827260] 02 81 01 f5 [ 2780.828753] ff ff [ 2780.828761] 02 81 01 fa [ 2780.830250] 00 00 [ 2780.830550] modifying (1) streaming state for 0 [ 2780.830555] data for streaming: 10 11 [ 2780.830557] 0f 10 11 00 [ 2780.831372] modifying (0) streaming state for 0 [ 2780.831377] data for streaming: 0 10 [ 2780.831378] 0f 00 10 00 [ 2780.836076] modifying (1) streaming state for 0 [ 2780.836086] data for streaming: 10 11 [ 2780.836087] 0f 10 11 00 [ 2780.842428] hub 6-0:1.0: port 1 disabled by hub (EMI?), re-enabling... [ 2780.842436] usb 6-1: USB disconnect, address 2 [ 2780.842721] 03 80 04 01 c0 00 [ 2780.842728] ep 0 write error (status = -19, len: 6) [ 2780.842730] MT2266 I2C write failed [ 2780.842732] 03 80 04 01 c0 00 [ 2780.842735] ep 0 write error (status = -19, len: 6) [ 2780.842737] MT2266 I2C write failed [ 2780.842739] 02 81 00 eb [ 2780.842743] ep 0 read error (status = -19) [ 2780.842744] e0 93 [ 2780.842746] I2C read failed on address 40 [ 2780.842748] 03 80 00 eb 00 32 [ 2780.842752] ep 0 write error (status = -19, len: 6) [ 2780.842753] 03 80 00 ec 07 00 [ 2780.842757] ep 0 write error (status = -19, len: 6) [ 2780.842758] 03 80 05 06 00 00 [ 2780.842762] ep 0 write error (status = -19, len: 6) [ 2780.842764] 02 81 05 00 [ 2780.842766] ep 0 read error (status = -19) [ 2780.842768] ac 1f [ 2780.842770] I2C read failed on address 40 [ 2780.842771] 03 80 03 06 ff ff [ 2780.842775] ep 0 write error (status = -19, len: 6) [ 2780.842776] 03 80 03 07 ff ff [ 2780.842780] ep 0 write error (status = -19, len: 6) [ 2780.842781] 03 80 03 08 00 07 [ 2780.842785] ep 0 write error (status = -19, len: 6) [ 2780.842786] 03 80 03 83 00 03 [ 2780.842790] ep 0 write error (status = -19, len: 6) [ 2780.842791] 03 80 05 00 8a 1f [ 2780.842795] ep 0 write error (status = -19, len: 6) [ 3097.541289] modifying (0) streaming state for 0 [ 3097.541294] data for streaming: 0 10 [ 3097.541295] 0f 00 10 00 [ 3097.541301] ep 0 write error (status = -19, len: 4) [ 3097.541302] dvb-usb: error while stopping stream. [ 3383.815796] wifi0: rx FIFO overrun; resetting First point: this is a DiB7000 based device, not a DiB3000 (which is what the Nova T-500 has on board -- that and a DiB0700 USB bridge). Now what caught my eye was the Now what I find interesting is the disabled by hub (EMI?) message -- the Nova-TD Stick is connected straight to the motherboard USB header via the short (6in) cable that came with the TD. A quick Google search suggests this might be down to heavy data transfer on the USB bus -- the controller can't handle the mass of data (buffer overflow?), so it shuts down the port. The Kernel notices that the controller has killed the port and restarts it. Most of what I've found seems to point to issues with older kernels (2.6.20 RCs mainly) and/or SMP... This suggests putting a hub in the way might help: http://forum.sparkfun.com/viewtopic.php?=p=25520 And this suggests issues surfacing under high I/O / Ethernet activity: http://www.mail-archive.com/[EMAIL PROTECTED]/msg18069.html Of course, the response was no it's not a kernel bug, it's a bug with your device (which is fair enough because 8/10 times it's NOT the kernel's fault, but in the other 2 times... :-/ ) The same thing was reported here with a DDR (Dance Dance Revolution?) pad... http://www.linuxquestions.org/questions/linux-hardware-18/usb-device-ddr-pad-keeps-disconnecting-596445/ The last one is interesting because if MythTV is grabbing the EIT, it'll be spooling the EIT data to RAM, then decoding it and saving it to the database. The database writes involve a good bit of disc access, and the data's going to be spooling in at ~20Mbit/sec from the DVB receiver. I wonder if the combination of lots of USB I/O, disc I/O, etc. is upsetting the kernel, or the USB controller (again - maybe the USB controller's buffer isn't getting flushed in time and is overflowing?) Though that said, 2x20Mbit=40Mbit, which is still well below USB2 High Speed's claimed 480Mbit transfer limit. The data is going to be packed into USB data frames/packets though, and I suspect the chip will be sending it in 188-byte blobs (i.e. full transport stream packets). I'm going to put my USB thumb-hub in the way (in unpowered mode) and see what happens. Given that I've never seen that bug in my syslog before today, and that the Fedora 7 / 8 stock kernels seem to be happy with it, I'd like to say kernel bug, but equally I don't want to place the blame on something that is rarely the cause of a problem. I'm also tempted to unplug the wireless card... that last rx FIFO overrun is making me somewhat suspicious. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your
Re: [linux-dvb] Hauppauge Nova T-500 / Nova-TD Stick (DiBcom tuners/demods) - the plot thickens...
Philip Pemberton wrote: [ 3097.541301] ep 0 write error (status = -19, len: 4) [ 3097.541302] dvb-usb: error while stopping stream. Forgot to mention -- after this mess, both tuners on the Nova-TD were dead. I restarted mythbackend and they woke up again, then as soon as I tuned to a channel both of them fell over again (USB disconnect). I think the EMI thing might have been a one-off -- the second disconnect was a standard one, not a hub has disabled the port. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Nicolas Will wrote: As much as I understand your position, where it's coming from, and the reasoning behind it (and I'm not necessarily against it, trust me on that), blaming it all on the closed parts is maybe just as bad as blaming a USB vendor or open source coders and giving up. It seems to be able to handle one or two recordings, then on the third it falls flat on its face. I told it to record Jurassic Park, and as soon as the recording was due to start, I got this in dmesg: Mar 3 21:00:03 dragon kernel: [51071.390905] mt2060 I2C write failed Mar 3 21:00:03 dragon kernel: [51071.390907] 03 14 04 07 ff ff Mar 3 21:00:03 dragon kernel: [51071.390910] ep 0 write error (status = -19, len: 6) Mar 3 21:00:03 dragon kernel: [51071.390912] 03 14 04 08 ff ff Mar 3 21:00:03 dragon kernel: [51071.390915] ep 0 write error (status = -19, len: 6) Mar 3 21:00:03 dragon kernel: [51071.390917] 03 14 04 09 ff f0 Mar 3 21:00:03 dragon kernel: [51071.390920] ep 0 write error (status = -19, len: 6) Mar 3 21:28:02 dragon -- MARK -- Mar 3 21:48:02 dragon -- MARK -- Mar 3 21:52:31 dragon kernel: [54213.772868] modifying (0) streaming state for 0 Mar 3 21:52:31 dragon kernel: [54213.772874] data for streaming: 0 10 Mar 3 21:52:31 dragon kernel: [54213.772876] 0f 00 10 00 Mar 3 21:52:31 dragon kernel: [54213.772881] ep 0 write error (status = -19, len: 4) Mar 3 21:52:31 dragon kernel: [54213.773463] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully deinitialized and disconnected. Mar 3 21:52:31 dragon kernel: [54214.011201] usb 2-1: new high speed USB device using ehci_hcd and address 3 Mar 3 21:52:31 dragon kernel: [54214.144020] usb 2-1: configuration #1 chosen from 1 choice Mar 3 21:52:31 dragon kernel: [54214.144429] FW GET_VERSION length: 16 Mar 3 21:52:31 dragon kernel: [54214.144431] cold: 0 Mar 3 21:52:31 dragon kernel: [54214.144433] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. Mar 3 21:52:31 dragon kernel: [54214.144457] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Mar 3 21:52:31 dragon kernel: [54214.144638] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) Mar 3 21:52:31 dragon kernel: [54214.144806] 0c 08 80 Mar 3 21:52:31 dragon kernel: [54214.158937] 0c 08 c0 Mar 3 21:52:31 dragon kernel: [54214.178924] 0c 0f 80 [.] I'm beginning to suspect a power supply or cooling issue; it seems to get worse the longer the machine is running... 15 hours uptime and the T500 is basically dead now, and a reboot only brings it back into the land of the living for a couple of hours at most... Now where did I put that 500W junker that came with the case... -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Nicolas Will wrote: You should really stick to the 1.10 firmware. 03-pre1 was an earlier test and has more issues. Well, I've figured out what was going on. Seems if you run 'make' against the source tree with one kernel, it will always build modules for said kernel until you run 'make distclean'. I started by building for 2.6.24-8-generic, then upgraded to -10-generic, then to -11-generic, and only did a 'make clean; make; sudo make install' when I rebuilt v4l-dvb, as this worked for Madwifi. So to summarise, if you're going to reuse the same source tree for multiple kernels, make distclean before making the drivers, or it'll build for the last kernel you built for... Not sure if it installs to the running kernel, but it certainly doesn't use the headers for the running kernel... But at least the card seems to be behaving now. Up 10 hours with: options dvb-usb-dib0700 debug=15 force_lna_activation=1 options dvb_usb disable_rc_polling=1 options usbcore autosuspend=-1 I've also blacklisted dvb-usb-dib0700 and modprobe'd it in an rc-script, so my HVR-3000 ends up as device 0 and the two T-500 tuners end up as devices 1 and 2; said shell script also sets up symlinks for the 1st and 2nd front-ends on the HVR to devices 10 and 11, because MythTV doesn't like the idea of a card having multiple front-ends... The clock is once again running... -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Patrik Hansson wrote: When i started using options usbcore autosuspend=-1 i deactivated debug=15 Will reactivate it again and reset my clock also. Just had a USB disconnect.. Switched MythTV to BBC HD, CPU load hit 100% and video jittered like mad. Switched back to Freeview via the Nova, both tuners down. USB disconnect and I2C errors in dmesg. Killed off mythbackend and the T500 re-attached, but wouldn't work (continuous disconnects whenever I loaded mythbackend) until I killed mythbackend, rmmod'ed dvb-usb-dib0700, then modprobed dvb-usb-dib0700 and restarted mythbackend. I've disabled EIT scanning on all but one of the Nova-T500 tuners, and set open on demand for both Nova-T500 tuners and both HVR-3000 tuners. If Myth isn't holding the tuner open, maybe it'll be a little more tolerant of this kind of glitch.. but it doesn't seem to switch to another tuner on the same source if one is dead, it just keeps hammering the same tuner over and over until it gives up... Urgh. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Patrik Hansson wrote: When i started using options usbcore autosuspend=-1 i deactivated debug=15 Will reactivate it again and reset my clock also. Well, changing channels on Myth seems to provoke it into failing... and it usually kills both tuners at the same time. Something is very badly wrong with this thing... I think I'm going to move the T500 into my Windows PC and buy a couple of cheap USB sticks for Freeview. This has gone on long enough. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Nicolas Will wrote: I am shocked by all your problems. I'm not. The blasted thing has a VIA USB controller on board - from experience it seems VIA are one of the few companies that still haven't managed to come up with a USB2 host-controller design that works properly without a filter driver sitting between the USB stack and the chip... I've got an uptime of 1 hour with the tuners idling (EIT scan on one of the tuners, other idle), but as soon as I start channel-hopping, the stupid thing falls over. So for what it's worth, here's the spec of my machine: - Biostar TA690G mainboard; AMD 690G chipset. Onboard VGA disabled. - AMD Athlon64 X2 4000+ AM2 CPU - 2GB RAM, dual channel mode - WD Caviar-GP (WD5000AACS) 500GB Quiet Drive - LiteOn LH-20A1P DVD writer - Hauppauge HVR-3000 DVB-S/T hybrid tuner - Hauppauge Nova-T 500 dual DVB-T And the OS: - Mythbuntu 8.04 alpha2 (Ubuntu Hardy) with latest updates - Kernel 2.6.24-11-generic - MythTV 0.21.0~fixes16259-0ubuntu1 I know a few folks are using 2.6.22 kernels.. just out of curiosity, has anyone got a Nova-T 500 working on 2.6.24? I'm just about to dig into the kernel changelog to see if anything's been changed relating to USB (especially anything to do with handling of VIA USB chipsets), though I doubt this is a kernel issue. IIRC there was something related to USB bandwidth handling that went into the kernel not long ago... hmm, I wonder... -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Nicolas Will wrote:
You do know that the cx24123 module has nothing to do with the
Nova-t-500, don't you?
I know. It's for the HVR-3000's satellite demux.
Would you have a DVB-S card in the system as well?
See above :)
Other than this issue, how's the stability of 0.21 in Hardy?
I'm itching... After al,l I ran Gutsy since alpha 2, for hardware
support reasons, but I have no real motivation apart from I want to try
the latest and greatest today.
Myth itself is quite stable, but Mythbuntu had some issues with the initial
8.04a2 release -- mostly with VNC and setting up the Myth transcoding daemon
('mkdir /var/lib/mythdvd/temp; chmod 777 /var/lib/mythdvd/temp' as root fixed
it for me). The LIRC config files for the Nova-T500's remote are a bit
mangled, and some buttons don't work by default.
Other than that, ripping DVDs to MPEG files and playing them back results in
issues with A/V sync; switching the player to default player in File Types
seems to have cured that.
Stability-wise, it puts MediaPortal to shame. Feature-wise, it's got
everything I need. Once I get the Nova-T500 to behave itself, and MythTV to
hibernate (or even shut down completely) and set an ACPI wakeup timer, I'll
consider the project 'done' :)
--
Phil. | (\_/) This is Bunny. Copy and paste Bunny
[EMAIL PROTECTED] | (='.'=) into your signature to help him gain
http://www.philpem.me.uk/ | ()_() world domination.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
And now the icing on the cake: [17296.754309] b5 7d [17296.754311] I2C read failed on address a [17298.643002] 02 15 81 fd [17298.643012] ep 0 read error (status = -19) [17298.643013] b5 7d [17298.643015] I2C read failed on address a [17300.535677] 02 15 81 fd [17300.535687] ep 0 read error (status = -19) [17300.535688] b5 7d [17300.535690] I2C read failed on address a [17302.193280] usbcore: deregistering interface driver dvb_usb_dib0700 [17302.314293] dib0700: loaded with support for 6 different device-types [17302.420405] BUG: unable to handle kernel paging request at virtual address fa23bda0 [17302.420412] printing eip: f89bd162 *pde = 374ac067 *pte = [17302.420417] Oops: [#1] SMP [17302.420420] Modules linked in: dvb_usb_dib0700 dib7000p dib7000m dvb_usb dib0070 isofs udf video output container sbs sbshc ac dock battery mt2060 dib3000mc dibx000_common iptable_filter ip_tables x_tables af_packet lp dvb_pll ipv6 cx22702 wlan_wep isl6421 cx24123 cx88_dvb cx88_vp3054_i2c wlan_scan_sta ath_rate_sample snd_hda_intel tuner tea5767 tda8290 snd_hwdep tda18271 tda827x tuner_xc2028 xc5000 snd_seq_dummy tda9887 cx88_alsa snd_pcm_oss snd_mixer_oss tuner_simple tuner_types snd_seq_oss mt20xx tea5761 ath_pci wlan ath_hal(P) sr_mod cdrom snd_pcm nvidia(P) snd_seq_midi cx8802 cx8800 snd_page_alloc cx88xx snd_rawmidi snd_seq_midi_event ir_common i2c_algo_bit videodev v4l1_compat compat_ioctl32 v4l2_common atiixp videobuf_dvb dvb_core snd_seq snd_timer snd_seq_device tveeprom videobuf_dma_sg videobuf_core btcx_risc snd i2c_piix4 button ati_agp agpgart ide_core i2c_core parport_pc parport soundcore shpchp pci_hotplug k8temp evdev pcspkr pata_atiixp ext3 jbd mbcache sg sd_mod ata_generic floppy uhci_hcd pata_acpi ahci ohci_hcd ehci_hcd libata usbcore scsi_mod ssb r8169 thermal processor fan fuse [17302.420479] [17302.420481] Pid: 9917, comm: kdvb-ad-1-fe-0 Tainted: P (2.6.24-11-generic #1) [17302.420484] EIP: 0060:[f89bd162] EFLAGS: 00010286 CPU: 0 [17302.420493] EIP is at i2c_transfer+0x22/0x60 [i2c_core] [17302.420496] EAX: fa23bda0 EBX: ffda ECX: 0003 EDX: dddebf00 [17302.420498] ESI: dddebf00 EDI: f77a255c EBP: 0003 ESP: dddebed8 [17302.420500] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 [17302.420503] Process kdvb-ad-1-fe-0 (pid: 9917, ti=dddea000 task=d8c59680 task.ti=dddea000) [17302.420505] Stack: dddebf00 f7515a28 dddebf00 dddebf54 dddebf68 f9c811bb [17302.420510]ddadb700 000a 0004 dddebf58 0074 0002 dddebf9a [17302.420515]000a 0004 dddebf54 0282 0282 0024 dddebf00 0001 [17302.420520] Call Trace: [17302.420529] [f9c811bb] dibx000_i2c_gated_tuner_xfer+0x10b/0x1b0 [dibx000_common] [17302.420563] [c0136f2e] del_timer_sync+0xe/0x20 [17302.420576] [f89bd17e] i2c_transfer+0x3e/0x60 [i2c_core] [17302.420590] [fa3800dc] mt2060_writereg+0x3c/0x60 [mt2060] [17302.420601] [f8a56a4e] dvb_frontend_thread+0x1ae/0x300 [dvb_core] [17302.420620] [c0141b80] autoremove_wake_function+0x0/0x40 [17302.420632] [f8a568a0] dvb_frontend_thread+0x0/0x300 [dvb_core] [17302.420644] [c01418c2] kthread+0x42/0x70 [17302.420647] [c0141880] kthread+0x0/0x70 [17302.420653] [c0106677] kernel_thread_helper+0x7/0x10 [17302.420665] === [17302.420666] Code: ff 83 c4 04 0f b6 c0 5b c3 83 ec 14 89 5c 24 04 bb da ff ff ff 89 7c 24 0c 89 c7 89 6c 24 10 89 cd 89 74 24 08 89 14 24 8b 40 0c 8b 00 85 c0 74 1f 8d 77 20 89 f0 e8 1e af 95 c7 8b 5f 0c 89 e9 [17302.420689] EIP: [f89bd162] i2c_transfer+0x22/0x60 [i2c_core] SS:ESP 0068:dddebed8 [17302.420697] ---[ end trace 8ec949325fb5108c ]--- I give up. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Darren Salt wrote: Which revision? Huh. Rev 62 UHCI and Rev 65 EHCI. Maybe it's not the USB HA then. I have a VIA-based USB card in one computer here; I've had no problems with it whatsoever. It shows up as: 00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 61) 00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 61) 00:10.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) There's a VIA southbridge in this machine; it actually works quite nicely with most things - exceptions being my Icybox IB380 hard drive enclosure and a Minolta film scanner. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Ben Firshman wrote: Mine has now been running for a couple of days now without problems, I will let you know if I lose a tuner. Strange, mine's still crashing out after a couple of hours. Just out of curiosity... - What kernel are you running? Distribution? Driver version? - If you're using MythTV, do you have Use this card for EIT scanning enabled for the T-500? - What firmware? Answers are 2.6.24-8-generic, Mythbuntu 8.04 alpha 2, Hg 615ce34, and yes (EIT scanning on) for me, and firmware is dvb-usb-dib0700-1.10.fw (in /lib/firmware/2.6.24-8-generic). I'm planning to try dvb-usb-dib0700-03-pre1.fw at some point -- is this older or newer than 1.10 (it's listed on the Wiki as a possible solution to the disconnect issue). I'm also staring daggers at the VIA USB controller chip on the T500... I've had nothing but trouble from VIA USB chips, with the possible exception of the K8T800 Pro on the motherboard in my desktop machine. FWIW, the PVR is based on a Biostar TA690G board, which uses the AMD/ATI 690G, but I've got a Gainward nVidia GeForce 8400GS PCIe-x16 card in there (because the 690G is a poor excuse for a graphics chip and only just works under Windows, let alone Linux!) Thanks, -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Patrik Hansson wrote: Just wanted to say that I´m experiencing the same. Using latest rev (the one with patches merged) + unknown remote key patch. Ubuntu 7.10 Also having a lot of prebuffer timeout 10 times i the middle of shows. I think I might have a workaround... On Mythbuntu or one of the many Ubuntu variants, this seems to work: 1) Run: lsmod |grep usbcore 2) If step 1 produced any output that started with 'usbcore', then usbcore is loaded as a module. Perform step 3a. Otherwise, step 3b. 3a) Create a text file called /etc/modprobe.d/local-dvb (the name is fairly irrelevant). Insert one line of text into it: options usbcore autosuspend=-1 Now go to step 4. 3b) Your kernel has usbcore built in. That means you have to modify the kernel command line... Edit /boot/grub/menu.lst (you'll need to sudo to do this). Search for this line: # defoptions=quiet splash Amend it to read: # defoptions=quiet splash usbcore.autosuspend=-1 It's meant to be commented out, so leave the hash at the beginning of the line alone... Save and exit, then run ... sudo update grub Ubuntu will regenerate grub.conf, using the new kernel command line. Off to step 4 you go! If you're using a non-Debian distro (e.g. Fedora), do the same thing but edit the 'kernel' line instead. It might read: kernel /boot/vmlinuz-2.6.24-8-generic root=LABEL=/ ro quiet splash Change it to: kernel /boot/vmlinuz-2.6.24-8-generic root=LABEL=/ ro quiet splash usbcore.autosuspend=-1 4) Reboot your PC. This is a bit long-winded, but saves a kernel recompile, and a ton of messing around recompiling kernels when Ubuntu do another release. I'm working on what I consider to be a better fix, which involves using the kernel's Quirks function to disable USB suspend just for the DiBcom controllers. That is, the kernel won't try and suspend them at all... Thanks, -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Christophe Boyanique wrote: options dvb-usb-dib0700 force_lna_activation=1 options dvb_usb disable_rc_polling=1 Did that last night and I'm still seeing MT2060 I2C timeouts... *sigh* This is on Mythbuntu 8.04 alpha-2, latest updates, running drivers from Hg TIP patched for the HVR-3000 (using the dev.kewl.org multi-frontend patch). Thanks, -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR-3000: fixed by downgrading kernel, any ~stoth/hvr3000 patches for 2.6.18 kernels?
Steven Toth wrote: Correct. I have no immediate plans to bring the multi-frontend patches beyond 2.6.18. If /When tuner refactoring and multiproto projects are accepted and merged then I'll think again. OK, well thanks for your work on the HVR3000 multi-frontend stuff anyway. I got it all working in the end (after rebuilding my own kernel RPM and a bunch of modules) but playback was awful (mainly because of the lack of Xvideo support in the current ATI driver - CPU usage on both cores hit 100% pretty quickly and the playback engine started dropping frames). No playback = no PVR... Oh well, I'll have another go towards the end of the year. Maybe then ATI will have sorted themselves out and fixed FGLRX... The kernel downgrade I can live with, the lousy video I can't. Emilio Castellano wrote: Analog works ok, DVB-T ok, DVB-S working with some troubles with diseq. I think I can live without DiSEqC - no switches, positioners or other doodads here, just a dish, an LNB and some satellite-grade co-ax cable :) Thanks. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR-3000: fixed by downgrading kernel, any ~stoth/hvr3000 patches for 2.6.18 kernels?
Darren Salt wrote: What lack of Xv? On the 690G, the chipset is an embedded Radeon X1250. The Fglrx driver doesn't support Xv on said chip. It's a known bug, and ATI are allegedly working on it... ... oh, the taintware? Drop it and use the open-source driver :-) (Well, unless you're using an R5xx or an Xpress.) Note facts mentioned above :) -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] HVR-3000: fixed by downgrading kernel, any ~stoth/hvr3000 patches for 2.6.18 kernels?
Well, it looks like either the kernel (stock FC6 2.6.20) or the driver itself is broken. Reverting to 2.6.18 (with minor patches to the r8169 Ethernet driver source) and installing Steve Toth's hvr3000 driver has enabled most of the card's features. The analogue TV tuner isn't working properly (but that might be a MythTV thing) but DVB-T works fine. I'm off to test DVB-S in a few minutes. To get this working, I've had to build a 2.6.18 kernel for Mythdora 4, reinstall the ATI Fglrx drivers (from the ATI package, not an RPM), rebuild LIRC, and rebuild IVTV. Actually, scrub that last part, I still haven't managed to rebuild the IVTV RPM from the AtRPMs source. But the rest of it seems to work... Does anyone know if any *working* patches exist to get Steve Toth's HVR-3000 driver (currently in hg under ~stoth/hvr3000) working on newer kernels? I got it to compile fairly well, it just didn't do much after it was compiled... Thanks. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] HVR-3000: DVB-T causes filter timeout / cx8802_timeout
Hi, I'm trying to get my Hauppauge HVR3000 working on Mythdora 4 (based on Fedora Core 6). This uses the 2.6.20 kernel, as supplied by Fedora (it's the same -fc6 RPM). I've tried with the drivers supplied with Mythdora, the latest Hg HEAD (http://linuxtv.org/hg/v4l-dvb/, 5a4448b56bc7), Steve Toth's HVR3000 branch (http://linuxtv.org/hg/v4l-dvb/~stoth/hvr3000) and Steve Toth's HVR4000 branch (http://linuxtv.org/hg/v4l-dvb/~stoth/hvr4000 with stoth-15.diff from http://dev.kewl.org/hvr4000/). On all of these, I get the same problem: (note: ~/uk-EmleyMoor is a modified version of /usr/share/dvb-apps/dvb-t/uk-EmleyMoor that includes ALL of the Emley Moor muxes) Here's what I did: - [EMAIL PROTECTED] v4l-dvb-5a4448b56bc7]# modprobe tuner [EMAIL PROTECTED] v4l-dvb-5a4448b56bc7]# modprobe cx88xx [EMAIL PROTECTED] v4l-dvb-5a4448b56bc7]# modprobe cx88_dvb [EMAIL PROTECTED] v4l-dvb-5a4448b56bc7]# scandvb ~/uk-EmleyMoor scanning /root/uk-EmleyMoor using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 62600 0 3 3 3 0 0 0 initial transponder 65000 0 3 3 3 0 0 0 initial transponder 67400 0 3 3 1 0 0 0 initial transponder 69800 0 3 3 1 0 0 0 initial transponder 70600 0 3 3 1 0 0 0 initial transponder 72200 0 3 3 1 0 0 0 initial transponder 67400 0 3 3 1 0 0 0 tune to: 62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 - And this turned up in dmesg: - Linux video capture interface: v2.00 cx2388x cx88-mpeg Driver Manager version 0.0.6 loaded CORE cx88[0]: subsystem: 0070:1402, board: Hauppauge WinTV-HVR3000 TriMode Analog/DVB-S/DVB-T [card=53,autodetected] TV tuner 63 at 0x1fe, Radio tuner -1 at 0x1fe tuner 0-0063: chip found @ 0xc6 (cx88[0]) tuner 0-0063: type set to 63 (Philips FMD1216ME MK3 Hybrid Tuner) tuner 0-0063: type set to 63 (Philips FMD1216ME MK3 Hybrid Tuner) cx88[0]: i2c scan: found device @ 0x10 [???] cx88[0]: i2c scan: found device @ 0xa0 [eeprom] cx88[0]: i2c scan: found device @ 0xaa [???] cx88[0]: i2c scan: found device @ 0xc2 [tuner (analog/dvb)] cx88[0]: i2c scan: found device @ 0xc6 [???] tveeprom 0-0050: Hauppauge model 14109, rev B3D3, serial# 1695398 tveeprom 0-0050: MAC address is 00-0D-FE-19-DE-A6 tveeprom 0-0050: tuner model is Philips FMD1216MEX (idx 133, type 4) tveeprom 0-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xf4) tveeprom 0-0050: audio processor is CX882 (idx 33) tveeprom 0-0050: decoder processor is CX882 (idx 25) tveeprom 0-0050: has radio, has IR receiver, has no IR transmitter cx88[0]: hauppauge eeprom: model=14109 input: cx88 IR (Hauppauge WinTV-HVR300 as /class/input/input11 cx88[0]/2: cx2388x 8802 Driver Manager ACPI: PCI Interrupt :03:05.2[A] - GSI 20 (level, low) - IRQ 21 cx88[0]/2: found at :03:05.2, rev: 5, irq: 21, latency: 64, mmio: 0xfa00 cx2388x dvb driver version 0.0.6 loaded cx8802_register_driver() -registering driver type=dvb access=shared CORE cx88[0]: subsystem: 0070:1402, board: Hauppauge WinTV-HVR3000 TriMode Analog/DVB-S/DVB-T [card=53] cx88[0]/2: cx2388x based dvb card DVB: registering new adapter (cx88[0]). DVB: registering frontend 0 (Conexant CX22702 DVB-T)... cx88[0]/2-mpeg: cx8802_timeout cx88[0]/2-mpeg: cx8802_timeout cx88[0]/2-mpeg: cx8802_timeout cx88[0]/2-mpeg: cx8802_timeout cx88[0]/2-mpeg: cx8802_timeout cx88[0]/2-mpeg: cx8802_timeout cx88[0]/2-mpeg: cx8802_timeout cx88[0]/2-mpeg: cx8802_timeout cx88[0]/2-mpeg: cx8802_timeout cx88[0]/2-mpeg: cx8802_timeout cx88[0]/2-mpeg: cx8802_timeout cx88[0]/2-mpeg: cx8802_timeout cx88[0]/2-mpeg: cx8802_timeout cx88[0]/2-mpeg: cx8802_timeout cx88[0]/2-mpeg: cx8802_timeout - Kernel is: [EMAIL PROTECTED] ~]# uname -a Linux dragon.homenet.philpem.me.uk 2.6.20-1.2944.fc6 #1 SMP Tue Apr 10 18:46:45 EDT 2007 i686 athlon i386 GNU/Linux CPU info: [EMAIL PROTECTED] ~]# cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 107 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ stepping: 1 cpu MHz : 1000.000 cache size : 512 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm cr8legacy ts fid vid ttp tm stc [6] bogomips: 2000.96 clflush size: 64 processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 107 model name : AMD Athlon(tm) 64 X2 Dual
[linux-dvb] Freecom DVB-T with scrambled vendor ID - possible to fix?
Hi, After a power cut this morning, my Freecom 25451-rev.3 (May 2006) DVB-T stick failed to restart - I've since found that this is because its USB ID has changed from 0x14aa:0x0225 to 0x1402:0x0225 - i.e. one byte of the VID has been changed. Does anyone know of a tool that can edit the contents of the EEPROM on the 25451, or any of the WideView USB sticks? Freecom are no help (take it back to where you bought it then) and the supplier doesn't want to know either (your warranty is with Freecom, not us - so much for the Sale of Goods Act), so I'm pretty much on my own... If I hack the Windows driver .INF files to reflect the new VID, they work fine. The Linux drivers also work insofar as the firmware gets uploaded, but the DVB entries in /dev never get created (I suspect this is an issue with the way I edited the VIDs). Thanks, -- Phil. http://www.philpem.me.uk/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
