Webcams again (trust spacecam 120) Microdia TwinkleCam USB camera

dasy2k1 · 07-15-2009, 09:15 AM

I have a new webcam that i would like to get working

lsusb reports it as

Code:

Bus 002 Device 009: ID 0c45:600d Microdia TwinkleCam USB camera

and the dmesg when i plug it in is

Code:

[120321.219896] evbug.c: Event. Dev: input4, Type: 1, Code: 28, Value: 1
[120321.219901] evbug.c: Event. Dev: input4, Type: 0, Code: 0, Value: 0
[120321.259886] evbug.c: Event. Dev: input4, Type: 4, Code: 4, Value: 458792
[120321.259895] evbug.c: Event. Dev: input4, Type: 1, Code: 28, Value: 0
[120321.259899] evbug.c: Event. Dev: input4, Type: 0, Code: 0, Value: 0
[120336.669025] usb 2-6: new full speed USB device using ohci_hcd and address 10
[120336.879654] usb 2-6: configuration #1 chosen from 1 choice
[120337.875893] evbug.c: Event. Dev: input4, Type: 4, Code: 4, Value: 458834
[120337.875903] evbug.c: Event. Dev: input4, Type: 1, Code: 103, Value: 1
[120337.875908] evbug.c: Event. Dev: input4, Type: 0, Code: 0, Value: 0
[120337.947896] evbug.c: Event. Dev: input4, Type: 4, Code: 4, Value: 458834
[120337.947905] evbug.c: Event. Dev: input4, Type: 1, Code: 103, Value: 0
[120337.947909] evbug.c: Event. Dev: input4, Type: 0, Code: 0, Value: 0
[120338.755900] evbug.c: Event. Dev: input4, Type: 4, Code: 4, Value: 458792
[120338.755912] evbug.c: Event. Dev: input4, Type: 1, Code: 28, Value: 1
[120338.755917] evbug.c: Event. Dev: input4, Type: 0, Code: 0, Value: 0
mchi8ds2@mchi8ds2-desktop:~$

(not sure what the other crap that keeps spooling is)

after this i get

Code:

mchi8ds2@mchi8ds2-desktop:~$ lsmod | grep vid
video                  29204  0 
output                 11648  1 video
nvidia               8123768  38 
mchi8ds2@mchi8ds2-desktop:~$

google tells me that i should be using the gspca driver for this so i tried

sudo modprobe gspca_main

this now gives in lsmod

Code:

mchi8ds2@mchi8ds2-desktop:~$ lsmod | grep vid
videodev               45184  2 gspca_main,compat_ioctl32
v4l1_compat            23940  1 videodev
video                  29204  0 
output                 11648  1 video
nvidia               8123768  38 
mchi8ds2@mchi8ds2-desktop:~$

but still no life

previposly i had found a site that recomended blacklisting sn9c102
after deblacklisting it and repluging the webcam i get

Code:

mchi8ds2@mchi8ds2-desktop:~$ lsmod | grep vid
videodev               45184  3 sn9c102,gspca_main,compat_ioctl32
v4l1_compat            23940  1 videodev
video                  29204  0 
output                 11648  1 video
nvidia               8123768  38 
mchi8ds2@mchi8ds2-desktop:~$

but cheese still gives no camera found

jdkaye · 07-15-2009, 09:58 AM

Hi,
I have the identical webcam, Trust Spacecam 120. It works on pretty well everything (skype, kopete, amsn, xawtv...) except ekiga and cheese. My results are a bit different than yours which may be of help. You're using ubuntu so it shouldn't be too different from debian. Here's my data.

Code:

$ lsusb | grep Microdia
Bus 002 Device 002: ID 0c45:600d Microdia TwinkleCam USB camera

Pretty much like yours.
dmesg is a bit less wordy:

Code:

$ dmesg | grep cam
[    8.988395] usb 2-2: Product: USB camera
[   31.334030] gspca: USB GSPCA camera found. SONIX sn9c10[1 2]

Nothing like the stuff you're getting.

Code:

$ lsmod | grep vid
videodev               27520  1 gspca
v4l1_compat            12260  1 videodev

I'm using a different module. I build mine from the gspca-source package using module-assistant. I don't know how you did yours. You might try it with other apps besides cheese and see if any of them work.
Cheers,
jdk

dasy2k1 · 07-15-2009, 10:32 AM

nothing is detected in anything else and m-a wont build the debian module from souce as i can only seem to get the kernel headers in the repo or a souce tarball with a slightly differnt name,
im working on compiling that and will see what happens eventually

jdkaye · 07-15-2009, 01:45 PM

Quote:

Originally Posted by dasy2k1

nothing is detected in anything else and m-a wont build the debian module from souce as i can only seem to get the kernel headers in the repo or a souce tarball with a slightly differnt name,
im working on compiling that and will see what happens eventually

I don't really understand what you're saying here but as long as you do I guess that's ok. Surely Ubuntu gives you a way of building modules, doesn't it? In Debian it's all pretty automatic. You just fire up m-a and go through the steps. It downloads what it needs and then goes about building your module. I guess it's different in Ubuntu.
Good luck
jdk