| Autor | 
    Nachricht | 
  
  
    | 
      
     | 
    
      
        
          
             
           | 
					
            Titel: Kriege meinen DVB-T USB Empfänger nicht zum laufen 
             Verfasst am: 22.11.2006, 14:17 Uhr
           | 
				 
       
     | 
  
  
    
      
        
          
             
            
  
            Anmeldung: 13. Mai 2004 
            Beiträge: 24 
             
            
            
           | 
         
       
     | 
    
      
        
          Hallo ich hoffe es kann mir jemand helfen, meine DVD-T Karte von Artec (Artec T1 USB TV Box) zum laufen zu kriegen. Ich schaffe es einfach nicht. Das Forum/Wiki konnte mir leider da auch nicht wirklich weiterhelfen (wird wohl eher an mir liegen).
 
 
hier ein dmsg Auszug:
 
Zitat: 
dmesg
 
nput/input1
 
i2c_adapter i2c-0: nForce2 SMBus adapter at 0x4c00
 
i2c_adapter i2c-1: nForce2 SMBus adapter at 0x4c40
 
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.56.
 
ACPI: PCI Interrupt Link [APCH] enabled at IRQ 21
 
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [APCH] -> GSI 21 (level, low) -> IRQ 233
 
PCI: Setting latency timer of device 0000:00:0a.0 to 64
 
forcedeth: using HIGHDMA
 
usbcore: registered new driver usbfs
 
usbcore: registered new driver hub
 
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
 
parport: PnPBIOS parport detected.
 
parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
 
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
 
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
 
00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
 
eth0: forcedeth.c: subsystem: 01043:8141 bound to 0000:00:0a.0
 
ACPI: PCI Interrupt Link [APCF] enabled at IRQ 20
 
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 20 (level, low) -> IRQ 50
 
PCI: Setting latency timer of device 0000:00:02.0 to 64
 
ohci_hcd 0000:00:02.0: OHCI Host Controller
 
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1
 
ohci_hcd 0000:00:02.0: irq 50, io mem 0xda004000
 
usb usb1: configuration #1 chosen from 1 choice
 
hub 1-0:1.0: USB hub found
 
hub 1-0:1.0: 10 ports detected
 
ACPI: PCI Interrupt Link [APCL] enabled at IRQ 23
 
ACPI: PCI Interrupt 0000:00:02.1 -> Link [APCL] -> GSI 23 (level, low) -> IRQ 217
 
PCI: Setting latency timer of device 0000:00:02.1 to 64
 
ehci_hcd 0000:00:02.1: EHCI Host Controller
 
ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 2
 
ehci_hcd 0000:00:02.1: debug port 1
 
PCI: cache line size of 64 is not supported by device 0000:00:02.1
 
ehci_hcd 0000:00:02.1: irq 217, io mem 0xfeb00000
 
ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
 
usb usb2: configuration #1 chosen from 1 choice
 
hub 2-0:1.0: USB hub found
 
hub 2-0:1.0: 10 ports detected
 
ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 22
 
ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCJ] -> GSI 22 (level, low) -> IRQ 225
 
PCI: Setting latency timer of device 0000:00:04.0 to 64
 
intel8x0_measure_ac97_clock: measured 58646 usecs
 
intel8x0: clocking to 47048
 
usb 2-1: new high speed USB device using ehci_hcd and address 2
 
usb 2-1: configuration #1 chosen from 1 choice
 
Adding 1542204k swap on /dev/hda1.  Priority:-1 extents:1 across:1542204k
 
usb 2-4: new high speed USB device using ehci_hcd and address 5
 
usb 2-4: configuration #1 chosen from 1 choice
 
ohci_hcd 0000:00:02.0: wakeup
 
usbcore: registered new driver libusual
 
Initializing USB Mass Storage driver...
 
scsi4 : SCSI emulation for USB Mass Storage devices
 
usb-storage: device found at 2
 
usb-storage: waiting for device to settle before scanning
 
scsi5 : SCSI emulation for USB Mass Storage devices
 
usb-storage: device found at 5
 
usb-storage: waiting for device to settle before scanning
 
usbcore: registered new driver usb-storage
 
USB Mass Storage support registered.
 
usb 1-2: new low speed USB device using ohci_hcd and address 2
 
usb 1-2: configuration #1 chosen from 1 choice
 
usb 1-3: new full speed USB device using ohci_hcd and address 3
 
usb 1-3: configuration #1 chosen from 1 choice
 
usbcore: registered new driver hiddev
 
input: Logitech Optical USB Mouse as /class/input/input2
 
input: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on usb-0000:00:02.0-2
 
usbcore: registered new driver usbhid
 
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
 
ts: Compaq touchscreen protocol output
 
dvb-usb: found a 'Artec T1 USB1.1 TVBOX with AN2235 (faulty USB IDs)' in cold state, will try to load a firmware
 
dvb-usb: downloading firmware from file 'dvb-usb-dibusb-an2235-01.fw'
 
usbcore: registered new driver dvb_usb_dibusb_mb
 
usbcore: registered new driver usbtest
 
usb 1-3: USB disconnect, address 3
 
dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
 
usb 1-3: new full speed USB device using ohci_hcd and address 4
 
usb 1-3: configuration #1 chosen from 1 choice
 
dvb-usb: found a 'DiBcom USB1.1 DVB-T reference design (MOD3000)' in warm state.
 
dvb-usb: will use the device's hardware PID filter (table count: 16).
 
DVB: registering new adapter (DiBcom USB1.1 DVB-T reference design (MOD3000)).
 
  Vendor: ST332062  Model: 0A                Rev: 0811
 
  Type:   Direct-Access                      ANSI SCSI revision: 00
 
SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)
 
  Vendor: Maxtor 6  Model: V300F0            Rev:
 
  Type:   Direct-Access                      ANSI SCSI revision: 02
 
sda: test WP failed, assume Write Enabled
 
sda: assuming drive cache: write through
 
DVB: registering frontend 0 (DiBcom 3000M-B DVB-T)...
 
SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)
 
sda: test WP failed, assume Write Enabled
 
sda: assuming drive cache: write through
 
 sda:<6>dibusb: This device has the Panasonic ENV77H11D5 onboard.
 
input: IR-receiver inside an USB DVB receiver as /class/input/input3
 
dvb-usb: schedule remote query interval to 150 msecs.
 
 sda1
 
sd 4:0:0:0: Attached scsi disk sda
 
sd 4:0:0:0: Attached scsi generic sg0 type 0
 
usb-storage: device scan complete
 
SCSI device sdb: 586114704 512-byte hdwr sectors (300091 MB)
 
sdb: Write Protect is off
 
sdb: Mode Sense: 38 00 00 00
 
sdb: assuming drive cache: write through
 
dvb-usb: DiBcom USB1.1 DVB-T reference design (MOD3000) successfully initialized and connected.
 
SCSI device sdb: 586114704 512-byte hdwr sectors (300091 MB)
 
sdb: Write Protect is off
 
sdb: Mode Sense: 38 00 00 00
 
sdb: assuming drive cache: write through
 
 sdb: sdb1 sdb2 < sdb5 sdb6 >
 
sd 5:0:0:0: Attached scsi disk sdb
 
sd 5:0:0:0: Attached scsi generic sg1 type 0
 
usb-storage: device scan complete
 
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707]
 
ACPI: Getting cpuindex for acpiid 0x1
 
Capability LSM initialized
 
fuse init (API version 7.7)
 
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
 
NTFS driver 2.1.27 [Flags: R/W MODULE].
 
NTFS volume version 3.1.
 
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
 
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
 
eth0: no link during initialization.
 
ACPI: Power Button (FF) [PWRF]
 
ACPI: Power Button (CM) [PWRB]
 
ACPI: Fan [FAN] (on)
 
ACPI: Thermal Zone [THRM] (40 C)
 
lp0: using parport0 (interrupt-driven).
 
lp0: console ready
 
ppdev: user-space parallel port driver
 
vmmon: module license 'unspecified' taints kernel.
 
/dev/vmmon[2303]: Module vmmon: registered with major=10 minor=165
 
/dev/vmmon[2303]: Module vmmon: initialized
 
/dev/vmnet: open called by PID 2325 (vmnet-bridge)
 
/dev/vmnet: hub 0 does not exist, allocating memory.
 
/dev/vmnet: port on hub 0 successfully opened
 
bridge-eth0: enabling the bridge
 
bridge-eth0: up
 
bridge-eth0: already up
 
bridge-eth0: attached
 
/dev/vmnet: open called by PID 2339 (vmnet-natd)
 
/dev/vmnet: hub 8 does not exist, allocating memory.
 
/dev/vmnet: port on hub 8 successfully opened
 
Linux agpgart interface v0.101 (c) Dave Jones
 
[drm] Initialized drm 1.0.1 20051102
 
ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
 
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4] -> GSI 19 (level, low) -> IRQ 58
 
[drm] Initialized radeon 1.25.0 20060524 on minor 0
 
/dev/vmnet: open called by PID 2432 (vmnet-netifup)
 
/dev/vmnet: hub 1 does not exist, allocating memory.
 
/dev/vmnet: port on hub 1 successfully opened
 
/dev/vmnet: open called by PID 2433 (vmnet-netifup)
 
/dev/vmnet: port on hub 8 successfully opened
 
/dev/vmnet: open called by PID 2453 (vmnet-dhcpd)
 
/dev/vmnet: port on hub 8 successfully opened
 
/dev/vmnet: open called by PID 2467 (vmnet-dhcpd)
 
/dev/vmnet: port on hub 1 successfully opened
 
[drm] Setting GART location based on new memory map
 
[drm] Loading R300 Microcode
 
[drm] writeback test succeeded in 1 usecs
 
usb 1-3: USB disconnect, address 4
 
dvb-usb: DiBcom USB1.1 DVB-T reference design (MOD3000) successfully deinitialized and disconnected.
 
/dev/vmnet: open called by PID 2724 (vmware-vmx)
 
eth0: Promiscuous mode enabled.
 
device eth0 entered promiscuous mode
 
bridge-eth0: enabled promiscuous mode
 
/dev/vmnet: port on hub 0 successfully opened
 
/dev/vmmon[2736]: host clock rate change request 0 -> 19
 
/dev/vmmon[2736]: host clock rate change request 19 -> 83
 
device eth0 left promiscuous mode
 
bridge-eth0: disabled promiscuous mode
 
/dev/vmnet: open called by PID 2736 (vmware-vmx)
 
eth0: Promiscuous mode enabled.
 
device eth0 entered promiscuous mode
 
bridge-eth0: enabled promiscuous mode
 
/dev/vmnet: port on hub 0 successfully opened
 
usb 1-3: new full speed USB device using ohci_hcd and address 5
 
usb 1-3: configuration #1 chosen from 1 choice
 
dvb-usb: found a 'Artec T1 USB1.1 TVBOX with AN2235 (faulty USB IDs)' in cold state, will try to load a firmware
 
dvb-usb: downloading firmware from file 'dvb-usb-dibusb-an2235-01.fw'
 
dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
 
usb 1-3: USB disconnect, address 5
 
usb 1-3: new full speed USB device using ohci_hcd and address 6
 
usb 1-3: configuration #1 chosen from 1 choice
 
dvb-usb: found a 'DiBcom USB1.1 DVB-T reference design (MOD3000)' in warm state.
 
dvb-usb: will use the device's hardware PID filter (table count: 16).
 
DVB: registering new adapter (DiBcom USB1.1 DVB-T reference design (MOD3000)).
 
DVB: registering frontend 0 (DiBcom 3000M-B DVB-T)...
 
dibusb: This device has the Panasonic ENV77H11D5 onboard.
 
input: IR-receiver inside an USB DVB receiver as /class/input/input4
 
dvb-usb: schedule remote query interval to 150 msecs.
 
dvb-usb: DiBcom USB1.1 DVB-T reference design (MOD3000) successfully initialized and connected.
 
dvb-usb: DiBcom USB1.1 DVB-T reference design (MOD3000) successfully deinitialized and disconnected.
 
usb 1-3: usbfs: interface 0 claimed by usbfs while 'vmware-vmx' sets config #1
 
/dev/vmmon[2736]: host clock rate change request 83 -> 1043
 
/dev/vmmon[2736]: host clock rate change request 1043 -> 83
 
/dev/vmmon[2736]: host clock rate change request 83 -> 1043
 
/dev/vmmon[2736]: host clock rate change request 1043 -> 83
 
/dev/vmmon[2736]: host clock rate change request 83 -> 1043
 
/dev/vmmon[2736]: host clock rate change request 1043 -> 83
 
/dev/vmmon[2736]: host clock rate change request 83 -> 1043
 
/dev/vmmon[2736]: host clock rate change request 1043 -> 83
 
/dev/vmmon[2736]: host clock rate change request 83 -> 1043
 
/dev/vmmon[2736]: host clock rate change request 1043 -> 83
 
/dev/vmmon[2736]: host clock rate change request 83 -> 1043
 
/dev/vmmon[2736]: host clock rate change request 1043 -> 83
 
device eth0 left promiscuous mode
 
bridge-eth0: disabled promiscuous mode
 
/dev/vmnet: open called by PID 2736 (vmware-vmx)
 
eth0: Promiscuous mode enabled.
 
device eth0 entered promiscuous mode
 
bridge-eth0: enabled promiscuous mode
 
/dev/vmnet: port on hub 0 successfully opened
 
/dev/vmmon[2736]: host clock rate change request 83 -> 19
 
/dev/vmmon[2736]: host clock rate change request 19 -> 1
 
/dev/vmmon[2736]: host clock rate change request 1 -> 19
 
/dev/vmmon[2736]: host clock rate change request 19 -> 83
 
device eth0 left promiscuous mode
 
bridge-eth0: disabled promiscuous mode
 
/dev/vmnet: open called by PID 2736 (vmware-vmx)
 
eth0: Promiscuous mode enabled.
 
device eth0 entered promiscuous mode
 
bridge-eth0: enabled promiscuous mode
 
/dev/vmnet: port on hub 0 successfully opened
 
loop: loaded (max 8 devices)
 
FAT: bogus number of FAT structure
 
VFS: Can't find a valid FAT filesystem on dev loop0.
 
FAT: bogus number of FAT structure
 
VFS: Can't find a valid FAT filesystem on dev loop0.
 
FAT: bogus number of FAT structure
 
VFS: Can't find a valid FAT filesystem on dev loop0.
 
usb 1-3: USB disconnect, address 6
 
usb 1-3: new full speed USB device using ohci_hcd and address 7
 
usb 1-3: configuration #1 chosen from 1 choice
 
dvb-usb: found a 'Artec T1 USB1.1 TVBOX with AN2235 (faulty USB IDs)' in cold state, will try to load a firmware
 
dvb-usb: downloading firmware from file 'dvb-usb-dibusb-an2235-01.fw'
 
dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
 
usb 1-3: USB disconnect, address 7
 
usb 1-3: new full speed USB device using ohci_hcd and address 8
 
usb 1-3: configuration #1 chosen from 1 choice
 
dvb-usb: found a 'DiBcom USB1.1 DVB-T reference design (MOD3000)' in warm state.
 
dvb-usb: will use the device's hardware PID filter (table count: 16).
 
DVB: registering new adapter (DiBcom USB1.1 DVB-T reference design (MOD3000)).
 
DVB: registering frontend 0 (DiBcom 3000M-B DVB-T)...
 
dibusb: This device has the Panasonic ENV77H11D5 onboard.
 
input: IR-receiver inside an USB DVB receiver as /class/input/input5
 
dvb-usb: schedule remote query interval to 150 msecs.
 
dvb-usb: DiBcom USB1.1 DVB-T reference design (MOD3000) successfully initialized and connected.
 
dvb-usb: DiBcom USB1.1 DVB-T reference design (MOD3000) successfully deinitialized and disconnected.
 
/dev/vmmon[2736]: host clock rate change request 83 -> 1043
 
/dev/vmmon[2736]: host clock rate change request 1043 -> 83
 
/dev/vmmon[2736]: host clock rate change request 83 -> 1043
 
sd 4:0:0:0: SCSI error: return code = 0x08000002
 
sda: Current: sense key=0x4
 
    ASC=0x4b ASCQ=0x0
 
end_request: I/O error, dev sda, sector 55491693
 
usb 2-10: new high speed USB device using ehci_hcd and address 11
 
usb 2-10: configuration #1 chosen from 1 choice
 
scsi6 : SCSI emulation for USB Mass Storage devices
 
usb-storage: device found at 11
 
usb-storage: waiting for device to settle before scanning
 
  Vendor:           Model: Flash Disk        Rev: 2.00
 
  Type:   Direct-Access                      ANSI SCSI revision: 02
 
ready
 
SCSI device sdc: 512000 512-byte hdwr sectors (262 MB)
 
sdc: Write Protect is off
 
sdc: Mode Sense: 03 00 00 00
 
sdc: assuming drive cache: write through
 
SCSI device sdc: 512000 512-byte hdwr sectors (262 MB)
 
sdc: Write Protect is off
 
sdc: Mode Sense: 03 00 00 00
 
sdc: assuming drive cache: write through
 
 sdc: sdc1
 
sd 6:0:0:0: Attached scsi removable disk sdc
 
sd 6:0:0:0: Attached scsi generic sg2 type 0
 
usb-storage: device scan complete
 
/dev/vmmon[2736]: host clock rate change request 1043 -> 83
 
device eth0 left promiscuous mode
 
bridge-eth0: disabled promiscuous mode
 
/dev/vmmon[2724]: host clock rate change request 83 -> 0
 
vmmon: Had to deallocate locked 33212 pages from vm driver f4c20000
 
vmmon: Had to deallocate AWE 3835 pages from vm driver f4c20000
 
usb 1-3: USB disconnect, address 8
 
usb 1-3: new full speed USB device using ohci_hcd and address 9
 
usb 1-3: configuration #1 chosen from 1 choice
 
dvb-usb: found a 'Artec T1 USB1.1 TVBOX with AN2235 (faulty USB IDs)' in cold state, will try to load a firmware
 
dvb-usb: downloading firmware from file 'dvb-usb-dibusb-an2235-01.fw'
 
usb 1-3: USB disconnect, address 9
 
dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
 
usb 1-3: new full speed USB device using ohci_hcd and address 10
 
usb 1-3: configuration #1 chosen from 1 choice
 
dvb-usb: found a 'DiBcom USB1.1 DVB-T reference design (MOD3000)' in warm state.
 
dvb-usb: will use the device's hardware PID filter (table count: 16).
 
DVB: registering new adapter (DiBcom USB1.1 DVB-T reference design (MOD3000)).
 
DVB: registering frontend 0 (DiBcom 3000M-B DVB-T)...
 
dibusb: This device has the Panasonic ENV77H11D5 onboard.
 
input: IR-receiver inside an USB DVB receiver as /class/input/input6
 
dvb-usb: schedule remote query interval to 150 msecs.
 
dvb-usb: DiBcom USB1.1 DVB-T reference design (MOD3000) successfully initialized and connected.
 
 
 
 
Es scheint ja, als ob die DVB_t Karte erkannt worden ist, aber leider kann ich weder mit kaffeine, xine oder mplayer zum laufen. Ich hoffe ihr könnt mir weiterhelfen.
 
 
MfG
 
Saladin | 
         
        
          | 
          
            
          
            
            
           | 
         
         
	        |     | 
	       
       
     | 
  
  
    | 
      
      
     | 
  
  
      | 
  
  
    | 
      
     | 
    
      
        
					
            Titel: Re: Kriege meinen DVB-T USB Empfänger nicht zum laufen 
             Verfasst am: 22.11.2006, 14:58 Uhr
           | 
				 
       
     | 
  
  
    
      
        
          
             
            
  
            Anmeldung: 06. Feb 2005 
            Beiträge: 1194 
            Wohnort: Mecklenburg 
            
            
           | 
         
       
     | 
    
      
        
          Ich habe eigentlich keine Ahnung von PC+TV, aber ich würde es einfach mal mit VDR versuchen.
 
 
MfG T. | 
         
        
          
          
            
          
             _________________ Notebook: Kanotix2006-1-rc1, Kernel 2.6.17.13-kanotix-2, ECS A531,Transmeta-Crusoe 1GHz,256MB, IceWM,
 
PC: Kanotix2006-1-rc1, Kernel 2.6.17.13-kanotix-2, VIA-Ezra 933MHz, 256MB, XFCE4
            
           | 
         
         
	        |     | 
	       
       
     | 
  
  
    | 
      
      
     | 
  
  
      | 
  
  
    | 
      
     | 
    
      
        
					
            Titel: RE: Re: Kriege meinen DVB-T USB Empfänger nicht zum laufen 
             Verfasst am: 22.11.2006, 16:07 Uhr
           | 
				 
       
     | 
  
  
    
      
        
          
             
            
  
            Anmeldung: 13. Mai 2004 
            Beiträge: 24 
             
            
            
           | 
         
       
     | 
    
      
        
          | Ich habe auch den VDR kurz mal ausprobiert, aber keine positiven Ergebnise damit erziehlt, wobei ich jetzt natürlich nicht weiss, ob es an VDR oder an der DVB-T Karten Installation lag. | 
         
        
          | 
          
            
          
            
            
           | 
         
         
	        |     | 
	       
       
     | 
  
  
    | 
      
      
     | 
  
  
      | 
  
  
    | 
      
     | 
    
      
        
					
            Titel: RE: Re: Kriege meinen DVB-T USB Empfänger nicht zum laufen 
             Verfasst am: 22.11.2006, 16:16 Uhr
           | 
				 
       
     | 
  
  
    
      
        
          
            Team Member 
             
  
  
            Anmeldung: 06. Mai 2005 
            Beiträge: 3087 
            Wohnort: berlin 
            
            
           | 
         
       
     | 
    
      
        
          wenn du mit kaffeine keinen dvb-tab nach start bekommst, brauchst du andere nicht versuchen.
 
anscheinend gibt es probleme mit der firmware deines sticks uns es wird ne andere genommen:
 
DiBcom USB1.1 DVB-T reference design (MOD3000)
 
ich würde mal mit : 'Artec T1 USB TV Box+debian' googeln.
 
 
greetz
 
devil | 
         
        
          
          
            
          
             _________________ <<We are  Xorg - resistance is futile - you will be axximilated>>
 
 
Host/Kernel/OS  "devilsbox" running[2.6.19-rc1-git5-kanotix-1KANOTIX-2006-01-RC4 ]
 
CPU Info        AMD Athlon 64 3000+ clocked at [ 803.744 MHz ]
            
           | 
         
         
	        |     | 
	       
       
     | 
  
  
    | 
      
      
     | 
  
  
      | 
  
  
    | 
      
     | 
    
      
        
					
            Titel:  
             Verfasst am: 22.11.2006, 16:48 Uhr
           | 
				 
       
     | 
  
  
    
      
        
          
             
            
  
            Anmeldung: 13. Mai 2004 
            Beiträge: 24 
             
            
            
           | 
         
       
     | 
    
      
        
          kaffeine zeigt mir ja einen "DVB-T Button" (wie auch immer beschrieftet) an.
 
Nur eine Kanalsuche ergibt keine Resultate. Liste bleibt immer leer.
 
Das die DVB-T Empfänger läuft, weis ich, da auf dem selben Rechner mittels VmWare Kanäle hereinkommen.
 
 
Das Netz hilft auch nicht weiter, da die informationen ziemlich spärlich gesät sind. | 
         
        
          | 
          
            
          
            
            
           | 
         
         
	        |     | 
	       
       
     | 
  
  
    | 
      
      
     | 
  
  
      | 
  
  
    | 
      
     | 
    
      
        
					
            Titel:  
             Verfasst am: 22.11.2006, 17:05 Uhr
           | 
				 
       
     | 
  
  
    
      
        
          
            Team Member 
             
  
  
            Anmeldung: 06. Mai 2005 
            Beiträge: 3087 
            Wohnort: berlin 
            
            
           | 
         
       
     | 
    
      
        
          dann versuch halt mal vdr, menuepunkt 7: kanalliste ändern.
 
 
greetz
 
devil | 
         
        
          
          
            
          
             _________________ <<We are  Xorg - resistance is futile - you will be axximilated>>
 
 
Host/Kernel/OS  "devilsbox" running[2.6.19-rc1-git5-kanotix-1KANOTIX-2006-01-RC4 ]
 
CPU Info        AMD Athlon 64 3000+ clocked at [ 803.744 MHz ]
            
           | 
         
         
	        |     | 
	       
       
     | 
  
  
    | 
      
      
     | 
  
  
      | 
  
  
    | 
      
     | 
    
      
        
					
            Titel:  
             Verfasst am: 22.11.2006, 18:13 Uhr
           | 
				 
       
     | 
  
  
    
      
        
          
             
             
  
            Anmeldung: 19. Jun 2005 
            Beiträge: 398 
            Wohnort: Hessen/Geinsheim 
            
            
           | 
         
       
     | 
    
      
        
          haste das mal probiert  um überhaupt ne Kanalliste zu bekommen ?
 
http://kanotix.com/FAQ-id_cat-114.html
 
 
Bei mir hats geholfen, allerdings benutze ich eine DVB-S Karte | 
         
        
          
          
            
          
             _________________ Samsung R510 4GB Ram GF9200GS M 1280x800 Win7 32bit
 
HP Mini 311 3 GB Ram Nvidia ION 1368x768 Linux Mint 10 KDE
            
           | 
         
         
	        |     | 
	       
       
     | 
  
  
    | 
      
      
     | 
  
  
      | 
  
  
    | 
      
     | 
    
      
        
					
            Titel:  
             Verfasst am: 22.11.2006, 19:36 Uhr
           | 
				 
       
     | 
  
  
    
      
        
          
             
            
  
            Anmeldung: 13. Mai 2004 
            Beiträge: 24 
             
            
            
           | 
         
       
     | 
    
      
        
          Deppsche: Danke hilft mir aber nicht weiter.
 
 
@devil:bringt leider auch keine Besserung ->no signal
 
 
ich schätze ich kriege keine ordentliche verbindung zum gerät.
 
wie/wo kann ich den sonst sehen, ob der treiber richtig installiert ist, und ob daten auf der usb schnittstelle fliessen und mir diese ansehen.
 
 
eine frage hätte ich auch noch, ob ich die firmware die ich in /usr/lib/hotplug kopiert habe irgendwie noch regitrieren muss. wenn ja wo/wie | 
         
        
          | 
          
            
          
            
            
           | 
         
         
	        |     | 
	       
       
     | 
  
  
    | 
      
      
     | 
  
  
      | 
  
  
    | 
      
     | 
    
      
        
					
            Titel:  
             Verfasst am: 22.11.2006, 20:39 Uhr
           | 
				 
       
     | 
  
  
    
      
        
          
            Team Member 
             
  
  
            Anmeldung: 06. Mai 2005 
            Beiträge: 3087 
            Wohnort: berlin 
            
            
           | 
         
       
     | 
    
      
        
          no signal kommt immer beim xine start.
 
drück einfach mal 1 oder 2 oder was immer oder öffne mit m das menue.
 
 
greetz
 
devil | 
         
        
          
          
            
          
             _________________ <<We are  Xorg - resistance is futile - you will be axximilated>>
 
 
Host/Kernel/OS  "devilsbox" running[2.6.19-rc1-git5-kanotix-1KANOTIX-2006-01-RC4 ]
 
CPU Info        AMD Athlon 64 3000+ clocked at [ 803.744 MHz ]
            
           | 
         
         
	        |     | 
	       
       
     | 
  
  
    | 
      
      
     | 
  
  
      | 
  
  
    | 
      
     | 
    
      
        
					
            Titel:  
             Verfasst am: 23.11.2006, 09:49 Uhr
           | 
				 
       
     | 
  
  
    
      
        
          
             
            
  
            Anmeldung: 13. Mai 2004 
            Beiträge: 24 
             
            
            
           | 
         
       
     | 
    
      
        
          | Leider auch nichts. Ich sehe zwar, den neuen Kanalnamen beim umschalten, aber kann leider kein Bild/Ton empfangen. | 
         
        
          | 
          
            
          
            
            
           | 
         
         
	        |     | 
	       
       
     | 
  
  
    | 
      
      
     | 
  
  
      | 
  
  
    | 
      
     | 
    
      
        
					
            Titel:  
             Verfasst am: 23.11.2006, 09:56 Uhr
           | 
				 
       
     | 
  
  
    
      
        
          
            Team Member 
             
  
  
            Anmeldung: 06. Mai 2005 
            Beiträge: 3087 
            Wohnort: berlin 
            
            
           | 
         
       
     | 
    
      
        
          vielleicht hilft das hier weiter:
 
http://www.kanotix.com/FAQ-id_cat-114.html
 
 
greetz
 
devil | 
         
        
          
          
            
          
             _________________ <<We are  Xorg - resistance is futile - you will be axximilated>>
 
 
Host/Kernel/OS  "devilsbox" running[2.6.19-rc1-git5-kanotix-1KANOTIX-2006-01-RC4 ]
 
CPU Info        AMD Athlon 64 3000+ clocked at [ 803.744 MHz ]
            
           | 
         
         
	        |     | 
	       
       
     | 
  
  
    | 
      
      
     | 
  
  
      | 
  
  
    | 
      
     | 
    
      
        
					
            Titel:  
             Verfasst am: 23.11.2006, 13:26 Uhr
           | 
				 
       
     | 
  
  
    
      
        
          
             
             
  
            Anmeldung: 17. Dez 2004 
            Beiträge: 290 
            Wohnort: Detmold 
            
            
           | 
         
       
     | 
    
      
        
          Deine Fehlerbeschreibung deutet darauf hin, dass Du das gleiche Problem wie ich hast.
 
Mit Kernel 2.6.18 funktioniert meine DVB-Karte nicht, bis 2.6.17 hat sie funktioniert, und mit 2.6.19 scheint sie auch wieder zu funktionieren. | 
         
        
          
          
            
          
             _________________ albatros
 
_________
            
           | 
         
         
	        |     | 
	       
       
     | 
  
  
    | 
      
      
     | 
  
  
      | 
  
  
    | 
      
     | 
    
      
        
					
            Titel:  
             Verfasst am: 23.11.2006, 14:19 Uhr
           | 
				 
       
     | 
  
  
    
      
        
          
             
            
  
            Anmeldung: 13. Mai 2004 
            Beiträge: 24 
             
            
            
           | 
         
       
     | 
    
      
        
          Ich werde mal heute abend eine frühere Kanotix Version mit einem Kernel kleiner 2.6.17 in einem VMWare Container installieren.
 
Mal sehen, ob die dann funktioniert.
 
 
Sonst muss wohl ein neuer Kernel her, obwohl ich keinen Schimmer habe, wie ich den installieren muss. | 
         
        
          | 
          
            
          
            
            
           | 
         
         
	        |     | 
	       
       
     | 
  
  
    | 
      
      
     | 
  
  
      | 
  
  
  
    | 
      
     |