Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The em8300 is the device name for a hollywood+ or creative dxr3 dvd decoder, nothing to do with the webcam.
Your video devices are there and the permissions look ok, what type of motherboard do you have?
I'm thinking that maybe the wrong usb controller module may be loaded.
Like Aussie said it might be the wrong usb module. It varies greatly which usb module works. On my computer both the uhci and the usb-uhci module work. I do however need to also load the ehci-hcd module for USB 2.0 support. If I don't then the webcam light never even turns on and it never gets registered with the USB driver.
But like I said before you really need to be reading through the output of dmesg (also found in /var/log/messages usually). It tells you whether the device has been registered and if the webcam driver detected the camera properly. It should give you a few clues where to go from there. So run the command dmesg and post the part relating to the usb and the webcam.
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 09:45:46 Feb 24 2003
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: USB UHCI at I/O 0xe400, IRQ 12
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: USB UHCI at I/O 0xe800, IRQ 12
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
hub.c: USB new device connect on bus1/1, assigned device number 2
usb.c: USB device 2 (vend/prod 0x46d/0x8b3) is not claimed by any active driver.
hub.c: USB new device connect on bus1/2, assigned device number 3
input0: USB HID v1.10 Mouse [Logitech USB Mouse] on usb1:3.0
usb.c: registered new driver snd-usb-audio
ALSA ../alsa-kernel/usb/usbaudio.c:1980: 2:2:0 : AS_GENERAL descriptor not found
usb-uhci.c: interrupt, status 3, frame# 100
usb.c: registered new driver audio
audio.c: v1.0.0:USB Audio Class driver
EXT3 FS 2.4-0.9.18, 14 May 2002 on ide0(3,2), internal journal
Adding Swap: 522104k swap-space (priority -1)
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.18, 14 May 2002 on ide0(3,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SCSI subsystem driver Revision: 1.00
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: HL-DT-ST Model: CD-RW GCE-8320B Rev: 1.04
Type: CD-ROM ANSI SCSI revision: 02
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
ohci1394: pci_module_init failed
ip_tables: (C) 2000-2002 Netfilter core team
8139too Fast Ethernet driver 0.9.25
divert: allocating divert_blk for eth0
eth0: RealTek RTL8139 Fast Ethernet at 0xd092bf00, 00:20:ed:3a:85:b1, IRQ 10
eth0: Identified 8139 chip type 'RTL-8139C'
eth0: Setting half-duplex based on auto-negotiated partner ability 0000.
es1371: version v0.30 time 09:46:21 Feb 24 2003
es1371: found chip, vendor id 0x1274 device id 0x5880 revision 0x02
es1371: found es1371 rev 2 at io 0xec00 irq 10
es1371: features: joystick 0x0
ac97_codec: AC97 Audio codec, id: 0x4352:0x5914 (Cirrus Logic CS4297A rev B)
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
usb-uhci.c: interrupt, status 3, frame# 2020
usb-uhci.c: interrupt, status 3, frame# 20
You didn't add the part about the pwc modules being loaded. But anyways here is some more information.
The usb driver detects two devices. The first it claims to be unknown and the second is your mouse. It gives the following information about the unknown device (vend/prod 0x46d/0x8b3)
The first being the vendor number for Logitech and the second being the product number for the QuickCam Zoom. I checked in my own kernel sources (2.4.20) and it is not supported yet. So I went to the site to check on the latest version and apparently the QuickCam Zoom is only supported from driver version 8.9 and upwards and will only be included in the 2.4.21 kernel which isn't out yet. So you will have to download the latest version and compile it yourself. It would probably be easier if you compile for a kernel from www.kernel.org instead of adding it to the redhat kernel you already have.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.