Jens Krehbiel-Gräther schrieb: > Dominik Kuhlen schrieb: > >> Hi >> <snip> >> >> >>> dev:/usr/src/multiproto# patch -p1 < pctv452e.patch >>> patching file linux/drivers/media/Kconfig >>> patching file linux/drivers/media/dvb/dvb-usb/Kconfig >>> Hunk #1 succeeded at 239 (offset 2 lines). >>> patching file linux/drivers/media/dvb/dvb-usb/Makefile >>> Hunk #1 succeeded at 61 with fuzz 2. >>> patching file linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h >>> Hunk #1 FAILED at 139. >>> 1 out of 1 hunk FAILED -- saving rejects to file >>> linux/drivers/media/dvb/dvb-usb >>> /dvb-usb-ids.h.rej >>> patching file linux/drivers/media/dvb/dvb-usb/pctv452e.c >>> patching file linux/drivers/media/dvb/frontends/Kconfig >>> Hunk #1 succeeded at 405 (offset 47 lines). >>> patching file linux/drivers/media/dvb/frontends/Makefile >>> Hunk #1 succeeded at 42 (offset 3 lines). >>> patching file linux/drivers/media/dvb/frontends/lnbp21.c >>> Hunk #1 succeeded at 117 (offset -1 lines). >>> patching file linux/drivers/media/dvb/frontends/lnbp22.c >>> patching file linux/drivers/media/dvb/frontends/lnbp22.h >>> patching file linux/drivers/media/dvb/frontends/stb0899_algo.c >>> Hunk #1 succeeded at 495 (offset -27 lines). >>> patching file linux/drivers/media/dvb/frontends/stb0899_drv.c >>> patching file linux/drivers/media/dvb/frontends/stb0899_drv.h >>> patching file linux/drivers/media/dvb/frontends/stb6100.c >>> patching file linux/include/linux/dvb/frontend.h >>> patching file linux/include/linux/dvb/video.h >>> Hunk #1 succeeded at 32 with fuzz 1 (offset 1 line). >>> dev:/usr/src/multiproto# >>> </snip> >>> >>> So I inserted the line into >>> linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h by hand >>> #define USB_PID_PCTV_452E 0x021f >>> >>> >> ok. this might happen if the file has been changed in repository since i have diff'ed. >> >> >>> I type make and all compiles with only a few warnings but now without >>> any error. >>> >>> When I install the modules and load them I get the following output from >>> dmesg: >>> >>> </snip> >>> usb 3-2: new high speed USB device using ehci_hcd and address 4 >>> usb 3-2: configuration #1 chosen from 1 choice >>> dvb-usb: found a 'PCTV HDTV USB' in warm state. >>> pctv452e_power_ctrl: 1 >>> dvb-usb: will pass the complete MPEG2 transport stream to the software >>> demuxer. >>> DVB: registering new adapter (PCTV HDTV USB) >>> pctv452e_frontend_attach Enter >>> stb0899_attach: Exiting .. ! >>> >>> >> Hmm. i wonder why this happens: the stb0899 did not attach properly: >> could you please load the stb0899 without verbose= parameter. >> it will print more info what's going on. >> >> > > > Hi! > > Well perhaps it is a hardware error in my device?? > Loading the module without "verbose" parameter prints the following in > the syslog: > > Jan 30 19:37:21 dev kernel: usb 3-6: new high speed USB device using > ehci_hcd and address 2 > Jan 30 19:37:21 dev kernel: usb 3-6: device descriptor read/64, error -71 > Jan 30 19:37:22 dev kernel: usb 3-6: device descriptor read/64, error -71 > Jan 30 19:37:22 dev kernel: usb 3-6: new high speed USB device using > ehci_hcd and address 3 > Jan 30 19:37:22 dev kernel: usb 3-6: configuration #1 chosen from 1 choice > Jan 30 19:37:22 dev kernel: dvb-usb: found a 'PCTV HDTV USB' in warm state. > Jan 30 19:37:22 dev kernel: pctv452e_power_ctrl: 1 > Jan 30 19:37:22 dev kernel: dvb-usb: will pass the complete MPEG2 > transport stream to the software demuxer. > Jan 30 19:37:22 dev kernel: DVB: registering new adapter (PCTV HDTV USB) > Jan 30 19:37:22 dev kernel: pctv452e_frontend_attach Enter > Jan 30 19:37:22 dev kernel: stb0899_write_regs [0xf1b6]: 02 > Jan 30 19:37:22 dev kernel: stb0899_write_regs [0xf1c2]: 00 > Jan 30 19:37:22 dev kernel: stb0899_write_regs [0xf1c3]: 00 > Jan 30 19:37:22 dev kernel: stb0899_write_regs [0xf141]: 02 > Jan 30 19:37:22 dev kernel: _stb0899_read_reg: Reg=[0xf000], data=05 > Jan 30 19:37:22 dev kernel: stb0899_get_dev_id: ID reg=[0x05] > Jan 30 19:37:22 dev kernel: stb0899_get_dev_id: Device ID=[0], Release=[5] > Jan 30 19:37:22 dev kernel: _stb0899_read_s2reg Device=[0xf3fc], Base > address=[0x00000400], Offset=[0xf334], Data=[0xb7fffe05] > Jan 30 19:37:22 dev kernel: _stb0899_read_s2reg Device=[0xf3fc], Base > address=[0x00000400], Offset=[0xf33c], Data=[0xb7fffe05] > Jan 30 19:37:22 dev kernel: stb0899_get_dev_id: Demodulator Core > ID=[<B7><FF><FE>^E], Version=[-1207960059] > Jan 30 19:37:22 dev kernel: _stb0899_read_s2reg Device=[0xfafc], Base > address=[0x00000800], Offset=[0xfa2c], Data=[0xb7fffe05] > Jan 30 19:37:22 dev kernel: _stb0899_read_s2reg Device=[0xfafc], Base > address=[0x00000800], Offset=[0xfa34], Data=[0xb7fffe05] > Jan 30 19:37:22 dev kernel: stb0899_get_dev_id: couldn't find a STB 0899 > Jan 30 19:37:22 dev kernel: stb0899_attach: Exiting .. ! > Jan 30 19:37:22 dev kernel: dvb-usb: no frontend was attached by 'PCTV > HDTV USB' > Jan 30 19:37:22 dev kernel: input: IR-receiver inside an USB DVB > receiver as /class/input/input4 > Jan 30 19:37:22 dev kernel: dvb-usb: schedule remote query interval to > 100 msecs. > Jan 30 19:37:22 dev kernel: pctv452e_power_ctrl: 0 > Jan 30 19:37:22 dev kernel: dvb-usb: PCTV HDTV USB successfully > initialized and connected. > Jan 30 19:37:22 dev kernel: usbcore: registered new interface driver > pctv452e > > > > Because of this line I think there is an error in the hardware: > Jan 30 19:37:22 dev kernel: stb0899_get_dev_id: Demodulator Core > ID=[<B7><FF><FE>^E], Version=[-1207960059] > > Also the light is always showing green (even if it is not connected with > a pc). > I will test the device under windows this evening to see wheter it is > working or not. > OK, I really think its a hardware problem. In Windows I get a bluescreen when I start the TV-Application (on 3 different PCs, so I think it must be something wrong with the hardware). I will try again when I get a new device from pinnacle support. Jens _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
