public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* usb ov511 problem (kernel crash)
@ 2001-10-03  9:30 Pasi Kärkkäinen
  2001-10-03 15:30 ` André Dahlqvist
  2001-10-03 16:04 ` Greg KH
  0 siblings, 2 replies; 5+ messages in thread
From: Pasi Kärkkäinen @ 2001-10-03  9:30 UTC (permalink / raw)
  To: linux-kernel


Hello!

I have an HP Omnibook 6000 laptop. When I plug in the D-LINK DRU-100C
(Ver. B2) usb-camera, and load the ov511 driver, the camera is detected
just fine. But, when I try to use the /dev/video0, the whole kernel
crashes! The same happens when I do "cat /dev/video0". There's nothing in
the syslog. Sysrq wont work.

I'm using Linux 2.4.10 and driver that comes with the kernel. I've also
tried the 1.42 ov511 driver from linux-usb.org. I use Debian GNU/Linux
(sid).

Any ideas?


usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.268 $ time 14:27:13 Oct  2 2001
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 10 for device 00:07.2
usb-uhci.c: USB UHCI at I/O 0x1880, IRQ 10
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: v1.268:USB Universal Host Controller Interface driver



Linux video capture interface: v1.00
usb.c: registered new driver ov511
ov511.c: OV511 USB Camera Driver v1.42
hub.c: USB new device connect on bus1/1, assigned device number 2
ov511.c: USB OV511+ camera found
ov511.c: camera: Generic OV511 Camera (no ID)
ov511.c: i2c write retries exhausted
ov511.c: i2c write: error -1
ov511.c: Sensor is an OV6620


Thanks for your help.


- Pasi Kärkkäinen

                                   ^
                                .     .
                                 Linux
                              /    -    \
                             Choice.of.the
                           .Next.Generation.



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: usb ov511 problem (kernel crash)
  2001-10-03  9:30 usb ov511 problem (kernel crash) Pasi Kärkkäinen
@ 2001-10-03 15:30 ` André Dahlqvist
  2001-10-03 16:04 ` Greg KH
  1 sibling, 0 replies; 5+ messages in thread
From: André Dahlqvist @ 2001-10-03 15:30 UTC (permalink / raw)
  To: linux-kernel

Pasi Kärkkäinen <pasik@iki.fi> wrote:

> I have an HP Omnibook 6000 laptop. When I plug in the D-LINK DRU-100C
> (Ver. B2) usb-camera, and load the ov511 driver, the camera is detected
> just fine. But, when I try to use the /dev/video0, the whole kernel
> crashes!

Try 2.4.11-pre2. The changelog says "Greg KH: USB updates", and I think
that includes a fix for a crasher that a few people have run into. I
think it was in usb-uhci.

Hope this helps,
-- 

André Dahlqvist <andre.dahlqvist@telia.com>

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: usb ov511 problem (kernel crash)
  2001-10-03  9:30 usb ov511 problem (kernel crash) Pasi Kärkkäinen
  2001-10-03 15:30 ` André Dahlqvist
@ 2001-10-03 16:04 ` Greg KH
  2001-10-16  1:08   ` Which USB hsot controller to use? Dr. Kelsey Hudson
  1 sibling, 1 reply; 5+ messages in thread
From: Greg KH @ 2001-10-03 16:04 UTC (permalink / raw)
  To: Pasi Kärkkäinen; +Cc: linux-kernel

On Wed, Oct 03, 2001 at 12:30:06PM +0300, Pasi Kärkkäinen wrote:
> 
> Hello!
> 
> I have an HP Omnibook 6000 laptop. When I plug in the D-LINK DRU-100C
> (Ver. B2) usb-camera, and load the ov511 driver, the camera is detected
> just fine. But, when I try to use the /dev/video0, the whole kernel
> crashes! The same happens when I do "cat /dev/video0". There's nothing in
> the syslog. Sysrq wont work.
> 
> I'm using Linux 2.4.10 and driver that comes with the kernel. I've also
> tried the 1.42 ov511 driver from linux-usb.org. I use Debian GNU/Linux
> (sid).

Fixed in 2.4.11-pre1, or use the uhci.o host controller instead of
usb-uhci.o.

thanks,

greg k-h

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Which USB hsot controller to use?
  2001-10-03 16:04 ` Greg KH
@ 2001-10-16  1:08   ` Dr. Kelsey Hudson
  2001-10-16 17:20     ` Greg KH
  0 siblings, 1 reply; 5+ messages in thread
From: Dr. Kelsey Hudson @ 2001-10-16  1:08 UTC (permalink / raw)
  To: linux-kernel

I noticed in the kernel configuration that there are two UHCI drivers for
UHCI-based motherboards/add-in option boards. Which one is better?

Thanks,

 Kelsey Hudson                                           khudson@ctica.com
 Software Engineer
 Compendium Technologies, Inc                               (619) 725-0771
---------------------------------------------------------------------------


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Which USB hsot controller to use?
  2001-10-16  1:08   ` Which USB hsot controller to use? Dr. Kelsey Hudson
@ 2001-10-16 17:20     ` Greg KH
  0 siblings, 0 replies; 5+ messages in thread
From: Greg KH @ 2001-10-16 17:20 UTC (permalink / raw)
  To: Dr. Kelsey Hudson; +Cc: linux-kernel

On Mon, Oct 15, 2001 at 06:08:09PM -0700, Dr. Kelsey Hudson wrote:
> I noticed in the kernel configuration that there are two UHCI drivers for
> UHCI-based motherboards/add-in option boards. Which one is better?

Depends on the drivers/devices you are using.  Currently the uhci.o
driver doesn't work properly for some devices that use bulk queuing
(visor, empeg, bluetooth, etc.) while the usb-uhci driver does.
On the other hand, the usb-uhci driver doesn't work for some people with
other kinds of hardware.

Try both out, and see which one works for you :)

(hopefully this problem goes away soon...)

thanks,

greg k-h

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2001-10-16 17:29 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-10-03  9:30 usb ov511 problem (kernel crash) Pasi Kärkkäinen
2001-10-03 15:30 ` André Dahlqvist
2001-10-03 16:04 ` Greg KH
2001-10-16  1:08   ` Which USB hsot controller to use? Dr. Kelsey Hudson
2001-10-16 17:20     ` Greg KH

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox