[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#369363: marked as done (linux-image-2.6.15-1-486: "Sweex USB Webcam 300K" is recognised but doesn't work)

Your message dated Sat, 18 Jul 2009 00:26:29 +0200
with message-id <20090717222629.GA7573@galadriel.inutil.org>
and subject line Re: sn9c102: more info (posible solution)
has caused the Debian Bug report #369363,
regarding linux-image-2.6.15-1-486: "Sweex USB Webcam 300K" is recognised but doesn't work
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
369363: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=369363
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.15-1-486
Version: 2.6.15-8
Severity: normal

The "Sweex USB Webcam 300K" with bus ID "0c45:608f Microdia" is recognised but the video device that is set up doesn't work.

Xawtv:

aa@debian:~$ xawtv
This is xawtv-3.94, running on Linux/i686 (2.6.15-1-486)
can't open /dev/video0: Message too long
v4l-conf had some trouble, trying to continue anyway
v4l2: open /dev/video0: Message too long
v4l2: open /dev/video0: Message too long
v4l: open /dev/video0: Message too long
no video grabber device available
aa@debian:~$

cat:

debian:/home/aa# cat /dev/video0
cat: /dev/video0: Message too long
debian:/home/aa#

lsusb:

Bus 002 Device 005: ID 0c45:608f Microdia

/var/log/messages on connection:

May 29 11:42:48 debian kernel: ohci_hcd 0000:00:02.1: wakeup
May 29 11:42:49 debian kernel: usb 2-3: new full speed USB device using ohci_hcd and address 4
May 29 11:42:49 debian kernel: usb 2-3: SN9C103 PC Camera Controller detected (vid/pid 0x0C45/0x608F)
May 29 11:42:49 debian kernel: usb 2-3: OV7630 image sensor detected
May 29 11:42:50 debian kernel: usb 2-3: Initialization succeeded
May 29 11:42:50 debian kernel: usb 2-3: V4L2 device registered as /dev/video0
May 29 11:42:50 debian kernel: usb 2-3: Optional device control through 'sysfs' interface ready

/var/log/messages on disconnection:

May 29 11:43:32 debian kernel: usb 2-3: USB disconnect, address 4
May 29 11:43:32 debian kernel: usb 2-3: Disconnecting SN9C10x PC Camera...
May 29 11:43:32 debian kernel: usb 2-3: V4L2 device /dev/video0 deregistered


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-486
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.15-1-486 depends on:
ii  initramfs-tools [linux-initra 0.60       tools for generating an initramfs
ii  module-init-tools             3.2.2-2    tools for managing Linux kernel mo

linux-image-2.6.15-1-486 recommends no packages.

-- debconf information:
  linux-image-2.6.15-1-486/postinst/kimage-is-a-directory:
  linux-image-2.6.15-1-486/preinst/initrd-2.6.15-1-486:
  linux-image-2.6.15-1-486/preinst/overwriting-modules-2.6.15-1-486: true
  linux-image-2.6.15-1-486/postinst/create-kimage-link-2.6.15-1-486: true
  linux-image-2.6.15-1-486/preinst/lilo-has-ramdisk:
  linux-image-2.6.15-1-486/preinst/lilo-initrd-2.6.15-1-486: true
  linux-image-2.6.15-1-486/postinst/bootloader-error-2.6.15-1-486:
  linux-image-2.6.15-1-486/prerm/removing-running-kernel-2.6.15-1-486: true
  linux-image-2.6.15-1-486/preinst/elilo-initrd-2.6.15-1-486: true
  linux-image-2.6.15-1-486/postinst/depmod-error-2.6.15-1-486: false
  linux-image-2.6.15-1-486/preinst/abort-install-2.6.15-1-486:
  linux-image-2.6.15-1-486/postinst/old-initrd-link-2.6.15-1-486: true
  linux-image-2.6.15-1-486/prerm/would-invalidate-boot-loader-2.6.15-1-486: true
  linux-image-2.6.15-1-486/preinst/abort-overwrite-2.6.15-1-486:
  linux-image-2.6.15-1-486/postinst/old-dir-initrd-link-2.6.15-1-486: true
  linux-image-2.6.15-1-486/postinst/bootloader-test-error-2.6.15-1-486:
  linux-image-2.6.15-1-486/preinst/bootloader-initrd-2.6.15-1-486: true
  linux-image-2.6.15-1-486/postinst/old-system-map-link-2.6.15-1-486: true
  linux-image-2.6.15-1-486/preinst/already-running-this-2.6.15-1-486:
  linux-image-2.6.15-1-486/preinst/failed-to-move-modules-2.6.15-1-486:
  linux-image-2.6.15-1-486/postinst/depmod-error-initrd-2.6.15-1-486: false

--- End Message ---
--- Begin Message --- 
On Wed, Nov 12, 2008 at 12:54:42AM +0100, Moritz Muehlenhoff wrote:
> On Mon, Jan 07, 2008 at 11:14:27AM -0600, Niko Cavallini Araya wrote:
> > Package: linux-image-2.6.23-1-amd64
> > Version: 2.6.23-2
> > Followup-For: Bug #369363
> > 
> > Hi I own a Genius videoCam messenger webcam.
> > 
> > #lsusb
> > Bus 003 Device 002: ID 0c45:602e Microdia
> > 
> > same chipset as in this bug report.
> > 
> > 
> > The kernel image tries to use sn9c102 built in. This driver dos not work. I get some sort of green input from the cam.
> > Yet there is a Gspca-souce package in debian containing driver which does a much better job at supporting the cam. It is still limited but it gives a 
> > much
> > better image.
> > 
> > The problem is that to use gspca module the sn9c102 module must be black listed in etc/modprobe.d/blacklist so that gspca takes control of the webcam.
> > 
> > I have the feeling that sn9c102 is the old form of the gspca driver.
> > 
> > The sn9c102 driver could be left out of the linux image so not to conflict with gspca (user would have to install the module to get webcam support).
> 
> Does this behaviour still occur with the Lenny kernel?
> 
> (gspca has been merged in the mainline kernel as of 2.6.27 and there are
> commits, which resolve conflicts between the various drivers, so this is
> likely fixed upstream already.

No further feedback, closing the bug.

If anyone reencounters the problem, please reopen this bug.

Cheers,
        Moritz

--- End Message ---
Reply to: