Login
Username:

Password:


Lost Password?

Register now!
Main Menu
Linux Projects Forum Index
   Users - SN9C1xx
     Trust WB-3400T + kernel 2.6.21.1 + SN9C1xx v1.44 problem
Register To Post

Threaded | Newest First Previous Topic | Next Topic | Bottom
Poster Thread
peetr04
Posted on: 2007/5/4 22:47
Just popping in
Joined: 2007/5/4
From:
Posts: 3
Trust WB-3400T + kernel 2.6.21.1 + SN9C1xx v1.44 problem
Hello I have trouble with this config.

Any idea!?!? THANKS FOR ANSWER!!!!!

Dmesg say after webcam connect:

sn9c102: V4L2 driver for SN9C1xx PC Camera Controllers v1:1.44
usbcore: registered new interface driver sn9c102
usb 2-6: new full speed USB device using ohci_hcd and address 6
usb 2-6: configuration #1 chosen from 1 choice
usb 2-6: SN9C103 PC Camera Controller detected (vid:pid 0x0C45:0x60AF)
usb 2-6: [sn9c102_i2c_try_raw_read:404] I2C read failed for HV7131D image sensor
usb 2-6: [sn9c102_i2c_try_raw_read:404] I2C read failed for HV7131D image sensor
usb 2-6: [sn9c102_i2c_try_raw_read:404] I2C read failed for HV7131R image sensor
usb 2-6: [sn9c102_i2c_try_raw_read:404] I2C read failed for MI-0343 image sensor
usb 2-6: [sn9c102_i2c_try_raw_read:404] I2C read failed for MI-0360 image sensor
usb 2-6: PAS202BCB image sensor detected
usb 2-6: [sn9c102_usb_probe:3258] Support for PAS202BCB maintained by Luca Risolia <luca.risolia@studio.unibo.it>
usb 2-6: [sn9c102_init:1668] Uncompressed video format is active
usb 2-6: [sn9c102_init:1689] Image sensor supports 'exposure' control
usb 2-6: [sn9c102_init:1689] Image sensor supports 'global gain' control
usb 2-6: [sn9c102_init:1689] Image sensor supports 'red balance' control
usb 2-6: [sn9c102_init:1689] Image sensor supports 'blue balance' control
usb 2-6: [sn9c102_init:1689] Image sensor supports 'green balance' control
usb 2-6: [sn9c102_init:1689] Image sensor supports 'DAC magnitude' control
usb 2-6: Initialization succeeded
usb 2-6: V4L2 device registered as /dev/video1
BUG: unable to handle kernel paging request at virtual address 05100071
printing eip:
c046c739
*pde = 00000000
Oops: 0002 [#1]
SMP
Modules linked in: sn9c102 vmnet(P) vmmon(P) snd_usb_audio snd_usb_lib snd_seq_oss snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_seq_dummy bnep rfcomm l2cap bluetoot
h fuse hwmon_vid eeprom i2c_isa i2c_viapro coda snd_seq_midi snd_seq_midi_event snd_seq snd_rtctimer snd_pcm_oss snd_mixer_oss joydev bttv snd_emu10k1 video_buf snd_rawmidi firmware_class sn
d_ac97_codec k8temp ir_common nvidia(P) emu10k1_gp ac97_bus snd_seq_device snd_hda_intel snd_hda_codec btcx_risc tveeprom agpgart snd_util_mem gameport snd_hwdep forcedeth snd_pcm snd_timer
snd snd_page_alloc i2c_nforce2 usbhid ff_memless usbkbd usbmouse
CPU: 0
EIP: 0060:[<c046c739>] Tainted: P VLI
EFLAGS: 00010246 (2.6.21.1 #2)
EIP is at mutex_lock+0xd/0x1a
eax: 05100071 ebx: 05100071 ecx: 00000004 edx: c19c2000
esi: e817adf4 edi: ffffffef ebp: 00000000 esp: c19c3cdc
ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0068
Process khubd (pid: 204, ti=c19c2000 task=c19995b0 task.ti=c19c2000)
Stack: e817adb4 f935ec20 c01847f5 c03685e1 e817ae34 00000004 e07b01a4 00000001
00000000 d1398000 e817adbc 00000001 00000000 d1398000 f93485cf f935b4e9
c05339dc e07bfd10 00000001 00000cba d1398008 d1398028 cead7600 d139a258
Call Trace:
[<c01847f5>] sysfs_add_file+0x2a/0x70
[<c03685e1>] video_register_device+0x1ab/0x21c
[<f93485cf>] sn9c102_usb_probe+0x57e/0x741 [sn9c102]
[<c03cd201>] usb_probe_interface+0x5d/0x7f
[<c0320166>] really_probe+0xbd/0x14e
[<c032023b>] driver_probe_device+0x44/0xa5
[<c046b571>] klist_next+0x4b/0x71
[<c032029c>] __device_attach+0x0/0x5
[<c031f71b>] bus_for_each_drv+0x37/0x5e
[<c0320312>] device_attach+0x56/0x6a
[<c032029c>] __device_attach+0x0/0x5
[<c031f695>] bus_attach_device+0x1e/0x3e
[<c031e6e8>] device_add+0x3a0/0x618
[<c03cbc9e>] usb_set_configuration+0x389/0x3f9
[<c03d1eaa>] generic_probe+0x199/0x1e7
[<c03ccec1>] usb_probe_device+0x32/0x37
[<c0320166>] really_probe+0xbd/0x14e
[<c032023b>] driver_probe_device+0x44/0xa5
[<c046b571>] klist_next+0x4b/0x71
[<c032029c>] __device_attach+0x0/0x5
[<c031f71b>] bus_for_each_drv+0x37/0x5e
[<c0320312>] device_attach+0x56/0x6a
[<c032029c>] __device_attach+0x0/0x5
[<c031f695>] bus_attach_device+0x1e/0x3e
[<c031e6e8>] device_add+0x3a0/0x618
[<c03cb8fb>] usb_cache_string+0x76/0x90
[<c03c8000>] usb_new_device+0x82/0xbf
[<c03c907e>] hub_thread+0x668/0x9b7
[<c012bcf5>] autoremove_wake_function+0x0/0x35
[<c03c8a16>] hub_thread+0x0/0x9b7
[<c012bc2c>] kthread+0xb0/0xd8
[<c012bb7c>] kthread+0x0/0xd8
[<c0103cdb>] kernel_thread_helper+0x7/0x10
=======================
Code: 94 c0 c3 53 89 c3 e8 7d f7 ff ff 83 c8 ff f0 0f c1 03 48 79 05 89 d8 5b eb 1e 5b 31 c0 c3 53 89 c3 83 ec 04 e8 5f f7 ff ff 89 d8 <f0> ff 08 79 05 e8 c5 00 00 00 58 5b c3 57 56 89 c6 8d
40 04 53
EIP: [<c046c739>] mutex_lock+0xd/0x1a SS:ESP 0068:c19c3cdc
luca
Posted on: 2007/5/5 17:43
Webmaster
Joined: 2003/1/9
From:
Posts: 172
Re: Trust WB-3400T + kernel 2.6.21.1 + SN9C1xx v1.44 problem
Is /sysfs enabled in your kernel?
I suspect there's a bug in the kernel. Can you compile and load the driver against 2.6.20 and see?
peetr04
Posted on: 2007/5/5 21:41
Just popping in
Joined: 2007/5/4
From:
Posts: 3
Re: Trust WB-3400T + kernel 2.6.21.1 + SN9C1xx v1.44 problem
Hello!

I changed to kernel 2.6.20.11!

NO KERNEL OOPS NOW! :)

DMESG says:
usb 2-6: new full speed USB device using ohci_hcd and address 8
usb 2-6: configuration #1 chosen from 1 choice
usb 2-6: SN9C103 PC Camera Controller detected (vid:pid 0x0C45:0x60AF)
usb 2-6: PAS202BCB image sensor detected
usb 2-6: Initialization succeeded
usb 2-6: V4L2 device registered as /dev/video1
usb 2-6: Optional device control through 'sysfs' interface ready
usb 2-6: usb_submit_urb() failed, error -28
ohci_hcd 0000:00:02.0: leak ed f7d3c340 (#81) state 2
usb 2-6: usb_submit_urb() failed, error -28
ohci_hcd 0000:00:02.0: leak ed f7d3c380 (#81) state 2
usb 2-6: usb_submit_urb() failed, error -28

sn-webcam says:
--------------------------------------------------
SN-WEBCAM - v 0.8.0
--------------------------------------------------
Error: No space left on device
Is the webcam turned on and connected?
Is the module sn9c10xc loaded?

At course module is loaded, but on all app (tvtime, xawtv) or simple cat =dev/video1 says same:
No space left on device

What could the problem?

Thanks.
luca
Posted on: 2007/5/6 4:09
Webmaster
Joined: 2003/1/9
From:
Posts: 172
Re: Trust WB-3400T + kernel 2.6.21.1 + SN9C1xx v1.44 problem
You have too many devices connected to the same USB controller, so there's not enough bandwidth for the video streaming. Another problem is that you are trying to use bad applications, as neither tvtime nor xawtv have good and complete v4l2 support. One application to access the camera is videoview available in the download section.

peetr04
Posted on: 2007/5/8 7:15
Just popping in
Joined: 2007/5/4
From:
Posts: 3
Re: Trust WB-3400T + kernel 2.6.21.1 + SN9C1xx v1.44 problem
Yes could be, but i detached all other usb device and same problem. This messege: "no space left on device" is very intresting. It could be this camera is uncompatible with tis driver?

Ahh. :)

Threaded | Newest First Previous Topic | Next Topic | Top

Register To Post
 
Donations
Support Our Site!
Make donations with PayPal!
Donat-o-Meter Stats
May's Goal: $150.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Surplus: $-150.00

Donations