[linux-dvb] Fwd: Artec T1 confusion - DVB Frage

.cyn cyn.mosh at gmail.com
Sun Jul 3 23:18:27 CEST 2005


After booting, lsusb gives:

Bus 003 Device 002: ID 054c:0069 Sony Corp. Memorystick MSC-U03 Reader
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 002: ID 0547:2235 Anchor Chips, Inc. AN2235 EZUSB-FX 
Microcontroller
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 046d:c00e Logitech, Inc. Optical Mouse
Bus 001 Device 001: ID 0000:0000
 
Indeed I had to remove the usbtest module to get past identifying it as 
EZ-USB device.
I have tried disconnecting and waiting without luck.

The syslog before the successful load was:

Jul 2 18:39:26 moshfc4 kernel: ACPI: PCI Interrupt Link [LNKA] enabled at 
IRQ 9
Jul 2 18:39:26 moshfc4 kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link 
[LNKA] -> GSI 9 (level, low) -> IRQ 9
Jul 2 18:39:26 moshfc4 kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
Jul 2 18:39:26 moshfc4 kernel: uhci_hcd 0000:00:1d.0: new USB bus 
registered, assigned bus number 1
Jul 2 18:39:26 moshfc4 kernel: uhci_hcd 0000:00:1d.0: irq 9, io base 
0x00001800
Jul 2 18:39:26 moshfc4 kernel: hub 1-0:1.0: USB hub found
Jul 2 18:39:26 moshfc4 kernel: hub 1-0:1.0: 2 ports detected
Jul 2 18:39:26 moshfc4 kernel: ACPI: PCI Interrupt Link [LNKD] enabled at 
IRQ 9
Jul 2 18:39:26 moshfc4 kernel: ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link 
[LNKD] -> GSI 9 (level, low) -> IRQ 9
Jul 2 18:39:26 moshfc4 kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
Jul 2 18:39:26 moshfc4 kernel: uhci_hcd 0000:00:1d.1: new USB bus 
registered, assigned bus number 2
Jul 2 18:39:26 moshfc4 kernel: uhci_hcd 0000:00:1d.1: irq 9, io base 
0x00001820
Jul 2 18:39:26 moshfc4 kernel: hub 2-0:1.0: USB hub found
Jul 2 18:39:26 moshfc4 kernel: hub 2-0:1.0: 2 ports detected
Jul 2 18:39:26 moshfc4 kernel: ACPI: PCI Interrupt Link [LNKC] enabled at 
IRQ 9
Jul 2 18:39:26 moshfc4 kernel: ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link 
[LNKC] -> GSI 9 (level, low) -> IRQ 9
Jul 2 18:39:26 moshfc4 kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
 Jul 2 18:39:26 moshfc4 kernel: usb 1-1: new low speed USB device using 
uhci_hcd and address 2
Jul 2 18:39:26 moshfc4 kernel: uhci_hcd 0000:00:1d.2: new USB bus 
registered, assigned bus number 3
Jul 2 18:39:26 moshfc4 kernel: uhci_hcd 0000:00:1d.2: irq 9, io base 
0x00001840
Jul 2 18:39:26 moshfc4 kernel: hub 3-0:1.0: USB hub found
Jul 2 18:39:26 moshfc4 kernel: hub 3-0:1.0: 2 ports detected
Jul 2 18:39:26 moshfc4 kernel: input: USB HID v1.10 Mouse [Logitech USB-PS/2 
Optical Mouse] on usb-0000:00:1d.0-1
Jul 2 18:39:26 moshfc4 kernel: usb 2-1: new full speed USB device using 
uhci_hcd and address 2
Jul 2 18:39:26 moshfc4 kernel: usb 3-1: new full speed USB device using 
uhci_hcd and address 2
Jul 2 18:39:26 moshfc4 kernel: ACPI: PCI Interrupt Link [LNKF] enabled at 
IRQ 9
Jul 2 18:39:26 moshfc4 kernel: ACPI: PCI Interrupt 0000:02:05.0[A] -> Link 
[LNKF] -> GSI 9 (level, low) -> IRQ 9
Jul 2 18:39:26 moshfc4 kernel: Yenta: CardBus bridge found at
0000:02:05.0[104d:80fa]
Jul 2 18:39:26 moshfc4 kernel: Yenta: ISA IRQ mask 0x08b8, PCI irq 9
Jul 2 18:39:26 moshfc4 kernel: Socket status: 30000006
Jul 2 18:39:26 moshfc4 kernel: ACPI: PCI Interrupt Link [LNKG] enabled at 
IRQ 9
Jul 2 18:39:26 moshfc4 kernel: ACPI: PCI Interrupt 0000:02:05.1[B] -> Link 
[LNKG] -> GSI 9 (level, low) -> IRQ 9
Jul 2 18:39:26 moshfc4 kernel: Yenta: CardBus bridge found at
0000:02:05.1[104d:80fa]
Jul 2 18:39:26 moshfc4 kernel: Yenta: ISA IRQ mask 0x0880, PCI irq 9
Jul 2 18:39:26 moshfc4 kernel: Socket status: 30000810
Jul 2 18:39:26 moshfc4 kernel: ohci1394: $Rev: 1250 $ Ben Collins <
bcollins at debian.org>
Jul 2 18:39:26 moshfc4 kernel: ACPI: PCI Interrupt Link [LNKH] enabled at 
IRQ 9
Jul 2 18:39:27 moshfc4 kernel: ACPI: PCI Interrupt 0000:02:05.2[C] -> Link 
[LNKH] -> GSI 9 (level, low) -> IRQ 9
Jul 2 18:39:27 moshfc4 kernel: ohci1394: fw-host0: OHCI-1394 1.0 (PCI): 
IRQ=[9] MMIO=[e8201000-e82017ff] Max Packet=[2048]
Jul 2 18:39:27 moshfc4 kernel: dvb-dibusb: found a 'DiBcom USB1.1 DVB-T 
reference design (MOD3000)' in warm state.
Jul 2 18:39:27 moshfc4 kernel: DVB: registering new adapter (DiBcom based 
USB Budget DVB-T device).
Jul 2 18:39:27 moshfc4 kernel: dvb-dibusb: found demodulator at i2c address 
0x8
Jul 2 18:39:27 moshfc4 kernel: dvb-dibusb: this device has the Thomson Cable 
onboard. Which is default.
Jul 2 18:39:27 moshfc4 kernel: DVB: registering frontend 0 (DiBcom 3000M-B 
DVB-T)...
Jul 2 18:39:27 moshfc4 kernel: dvb-dibusb: schedule remote query interval to 
100 msecs.
Jul 2 18:39:27 moshfc4 kernel: dvb-dibusb: DiBcom USB1.1 DVB-T reference 
design (MOD3000) successfully initialized and connected.
Jul 2 18:39:27 moshfc4 kernel: usbcore: registered new driver DiBcom based 
USB Budget DVB-T device
 
[even before that; all usb related events:
Jul 2 18:39:26 moshfc4 kernel: usbcore: registered new driver usbfs
Jul 2 18:39:26 moshfc4 kernel: usbcore: registered new driver hub
...
Jul 2 18:39:26 moshfc4 kernel: usbcore: registered new driver hiddev
Jul 2 18:39:26 moshfc4 kernel: usbcore: registered new driver usbhid
Jul 2 18:39:26 moshfc4 kernel: drivers/usb/input/hid-core.c: v2.01:USB HID 
core driver
...
Jul 2 18:39:26 moshfc4 kernel: USB Universal Host Controller Interface 
driver v2.2]


Danke Schoen
--
.Cyn

On 7/3/05, Patrick Boettcher <patrick.boettcher at desy.de> wrote:
> 
> Hi Cyn,
> 
> The Artec T1 is one of dibusb-clones which makes real headaches.
> 
> Artec delivers their USB boxes to endusers with the default USB ID of the
> USB microcontroller. In newer kernels this leads to autoloading the
> usbtest-module....
> 
> But I should not mention problems you don't have.
> 
> Did you try to disconnect your Box for 2 minutes from the USB bus and thus
> from the power?
> 
> The Artec boxes are known to have a good memory mixed with amnesia (yes,
> they only keep some information).
> 
> Some comments are in-line:
> 
> On Sun, 3 Jul 2005, .cyn wrote:
> > Ive got a *hopefully* quick question on geting my dvb box to play:
> >
> > the setup:
> >
> > - Fedora Core 4; 2.6.12-1.1387_FC4-i686 (latest)
> > - Artec T1 DVB
> >
> >
> > I got the drivers, modules and firmware necessary for the Artec to work, 
> but
> > it didn't.
> > Then suddenly, after some reboots, without having changed anything since
> > last time it wasn't working, it randomly worked fine.
> > Only till next reboot where it went back to not working.
> > So I have everything necessary to make it work but something isn't quite
> > right.
> > Digging the syslog to find the point it had worked (this is at somepoint
> > after startup before logging in)
> >
> > Jul 2 18:39:27 moshfc4 kernel: dvb-dibusb: found a 'DiBcom USB1.1 DVB-T
> > reference design (MOD3000)' in warm state.
> 
> Can you have a second look in that syslog to see which firmware it loaded
> to make that line.
> 
> What does lsusb show, after a cold boot and no driver loaded before?
> 
> best regards,
> Patrick.
> 
> --
> Mail: patrick.boettcher at desy.de
> WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.linuxtv.org/pipermail/linux-dvb/attachments/20050703/77fb4203/attachment.htm


More information about the linux-dvb mailing list