Johannes, I managed to get my Yellow Dog kernel up from 2.6.10 to 2.6.14.3 (clean download, not patched). The Freecom USB stick is now detected but I get the same problems as Michael Hanke recently reported (thread subject "dnt Euro Stick DVB-T -- FATAL: FE_GET_INFO failed: 22") where the device won't tune. The Freecom works fine with EyeTV under MacOS X, no tuning problems or issues associated with input signal saturation as reported by Mike Choy (thread subject "freecom dvb-t usb firmware coldstate") so there's nothing wrong with the stick or the aerial feed. But I get the same "recv bulk message failed: -110" as everyone else under Linux. Here are the logs: Freecom dmesg output: usb 1-1: new high speed USB device using ehci_hcd and address 3 dvb-usb: found a 'WideView WT-220U PenType Receiver (Typhoon/ Freecom)' in warm state. dvb-usb: will use the device's hardware PID filter (table count: 15). DVB: registering new adapter (WideView WT-220U PenType Receiver (Typhoon/Freecom)). DVB: registering frontend 0 (WideView USB DVB-T)... dvb-usb: schedule remote query interval to 300 msecs. dvb-usb: WideView WT-220U PenType Receiver (Typhoon/Freecom) successfully initialized and connected. dvb-usb: recv bulk message failed: -110 Freecom tzap output: [root@yellowdog build-2.6]# tzap -r -a 0 -x BBCNews24 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 778000000 Hz freq: 778000000, inversion: 0, bw: 0, crHP: 3, crLP: 0, mod: 1, mode: 0, guard: 0, hier: 0 video pid 0x0280, audio pid 0x0281 status 1f | signal 3434 | snr e9e9 | ber 00000000 | unc 00000000 | FE_HAS_LOCK[root@yellowdog build-2.6]# Freecom scan output: [root@yellowdog build-2.6]# scan -c using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x0000 dumping lists (0 services) Done. [root@yellowdog build-2.6]# I tried the DEC2000-t with the new kernel, same problem as before, here are the logs for that: DEC2000-t dmesg output: usb 4-1: new full speed USB device using ohci_hcd and address 2 ttusb_dec: Firmware 1.05de Oops: kernel access of bad area, sig: 11 [#1] NIP: C0012168 LR: C01609EC SP: EFF2BC60 REGS: eff2bbb0 TRAP: 0300 Not tainted MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 DAR: 00000000, DSISR: 40000000 TASK = c0608bd0[31] 'khubd' THREAD: eff2a000 Last syscall: -1 GPR00: C01EC704 EFF2BC60 C0608BD0 00000000 FFFFFFFF 0000001E 00000000 000001A4 GPR08: 00000000 00000000 C01ECDDC C01ECC20 00000000 00000000 C18D6418 C18B4890 GPR16: 00000004 C18B48E2 C18A7E30 C03D0000 C0290000 C0380000 F22E0000 00000001 GPR24: 00000000 EFF2BD7C EDC1C860 00000000 0000001E 00000000 C0684120 C0684120 NIP [c0012168] strlen+0x4/0x18 LR [c01609ec] strlcpy+0x24/0x70 Call trace: [c01ec704] _request_firmware+0xc8/0x37c [f22dbe6c] ttusb_dec_probe+0x2ac/0xc58 [ttusb_dec] [c028336c] usb_probe_interface+0x78/0xa8 [c01e7540] driver_probe_device+0x50/0xf4 [c01e6ae0] bus_for_each_drv+0x60/0xb4 [c01e74ac] device_attach+0x98/0xdc [c01e696c] bus_add_device+0x40/0x154 [c01e529c] device_add+0x114/0x174 [c028b880] usb_set_configuration+0x2d0/0x488 [c02862c0] usb_new_device+0x15c/0x214 [c0287464] hub_thread+0x960/0xd18 [c0036604] kthread+0xf0/0x12c [c000756c] kernel_thread+0x44/0x60 [root@yellowdog build-2.6]# Regards, Tim. On 7 Dec 2005, at 14:53, Johannes Stezenbach wrote: > On Mon, Dec 05, 2005, Tim Hewett wrote: >> I'm trying to get the current CVS of Linux DVB working on an Apple >> iBook >> running Yellow Dog using either a Hauppauge DEC2000-t (which works >> fine on a Pentium III with Mandrake 9.1) and also a Freecom DVB-T USB >> stick. Neither work. The drivers build ok once the makefile is setup >> to find >> the source and the kernel config file in the right places, and they >> load but >> every time the Hauppauge device is connected the kernel hits an >> exception >> and the Freecom isn't recognised at all (though maybe the latter is >> because >> the kernel is only 2.6.10). >> >> I am wondering if the DVB drivers are only for the Intel >> architecture, >> or does the byte endian issue sort itself out automatically? Has >> anyone >> had any DVB devices working at all on PowerPC? > > They obviously don't get as many testers on non-x86 architectures. > > If you care about getting the DEC2000-t driver fixed you need to post > some useful info like the Oops message. Maybe someone can figure out > what's wrong then. > > Johannes > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.linuxtv.org/pipermail/linux-dvb/attachments/20051210/7644184e/attachment-0001.htm
