Hi!
I have problems with VIA and UHCI also. I don't know if the alpha stage of
the mustek driver or my USB drivers.
I can scan 3 images in a row. After 10-20 seconds my computer freeze. No
sysrq just power button.
Maybe this help...
Kernel 2.4.3. Via 686b (Epox 8kta2 mb)
Thanks!
---
Hi!
I have problems with VIA and UHCI also. I don't know if the alpha stage of
the mustek driver or my USB drivers.
I can scan 3 images in a row. After 10-20 seconds my computer freeze. No
sysrq just power button.
Maybe this help...
Kernel 2.4.3. Via 686b (Epox 8kta2 mb)
Thanks!
---
Johannes Erdfelt wrote:
> > I think this may be a problem in the dc2xx.o then, since uhci didn't reveal
> > any new messages.
>
> It's possible. Many cameras are touchy wrt to the commands it receives.
> If one is slightly wrong, some of them will just stop talking.
Yeah, looks like I get to
On Tue, Jun 19, 2001, Dylan Griffiths <[EMAIL PROTECTED]> wrote:
> Johannes Erdfelt wrote:
> > Could you load uhci with the debug=1 option?
>
> I did an 'insmod uhci.o debug=1' but the dmesg output did not alter.
>
> My easy steps to reproduce it is to 'delete selected images' in gphoto such
>
On Tue, Jun 19, 2001, Dylan Griffiths [EMAIL PROTECTED] wrote:
Johannes Erdfelt wrote:
Could you load uhci with the debug=1 option?
I did an 'insmod uhci.o debug=1' but the dmesg output did not alter.
My easy steps to reproduce it is to 'delete selected images' in gphoto such
that there
Johannes Erdfelt wrote:
I think this may be a problem in the dc2xx.o then, since uhci didn't reveal
any new messages.
It's possible. Many cameras are touchy wrt to the commands it receives.
If one is slightly wrong, some of them will just stop talking.
Yeah, looks like I get to see if I
Johannes Erdfelt wrote:
> Could you load uhci with the debug=1 option?
I did an 'insmod uhci.o debug=1' but the dmesg output did not alter.
My easy steps to reproduce it is to 'delete selected images' in gphoto such
that there will be no images in the camera left when the operation is done.
At
Johannes Erdfelt wrote:
Could you load uhci with the debug=1 option?
I did an 'insmod uhci.o debug=1' but the dmesg output did not alter.
My easy steps to reproduce it is to 'delete selected images' in gphoto such
that there will be no images in the camera left when the operation is done.
At
On Sun, Jun 17, 2001, Dylan Griffiths <[EMAIL PROTECTED]> wrote:
> dmesg log:
> usb.c: registered new driver dc2xx
> dc2xx.c: v1.0.0 David Brownell, <[EMAIL PROTECTED]>
> dc2xx.c: USB Camera Driver for Kodak DC-2xx series cameras
> PCI: Found IRQ 5 for device 00:04.2
> PCI: The same IRQ used for
Another thing I was happy to find working better in 2.4.5, was USB. I had
just dumped off ~70 high res pics (which would've taken forever via the
usual RS232 method), and was deleting the last pics when gphoto froze. The
dmesg log has the same messages it had before when I experimented with
Another thing I was happy to find working better in 2.4.5, was USB. I had
just dumped off ~70 high res pics (which would've taken forever via the
usual RS232 method), and was deleting the last pics when gphoto froze. The
dmesg log has the same messages it had before when I experimented with
On Sun, Jun 17, 2001, Dylan Griffiths [EMAIL PROTECTED] wrote:
dmesg log:
usb.c: registered new driver dc2xx
dc2xx.c: v1.0.0 David Brownell, [EMAIL PROTECTED]
dc2xx.c: USB Camera Driver for Kodak DC-2xx series cameras
PCI: Found IRQ 5 for device 00:04.2
PCI: The same IRQ used for device
12 matches
Mail list logo
