[sane-devel] usb_submit_urb return ENOMEM?
Hello everyone: I have some problem in developing usb scanner.who can help me? when call usb_submit_urb() in probe_scanner() (scanner.c of kernel 2.4.19), return is ENOMEM. why and how to resolve that? My scanner has three endpoints (1 is bulk in, 2 is bulk out, 3 is bulk interrupt). Then I marked usb_submit_urb, scanner is probed, and ioctl system call can be called. But when write_scanner, usb_bulk_msg return ENOMEM too. Why and how to?? Thanks a lot Dan _ ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£ http://www.hotmail.com
[sane-devel] IRQ conflict between Fujitsu fi-4120c and NIC
This is a multi-part message in MIME format. --=_NextPart_000_0005_01C2FC84.E57025D0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Hi, I added 'usb /dev/usb/scanner0' to fujitsu.conf, and it works now. I = could use scanimage to scan, but I could not use xsane, it prompted 'no = device', and did not show the select device dialog, I guess that might be xsane's configuration problem? Another problem is there is a IRQ conflict between fi-4120c and my NIC, here is the error log: eth0: transmit timed out, tx_status 00 status e601 diagnostics:net 0cd8 media 8880 dma 003a. eth0: Interrupt posted but not delivered -- IRQ blocked by another = device? This is the error log when I tried to ping another Windows machine I = used to be able to ping. Then I reboot the Linux machine, Redhat automatically removed the NIC configuration, so I lost the network connection to my Windows machine.=20 What should I do now? Thanks a lot, Peter --=_NextPart_000_0005_01C2FC84.E57025D0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable Hi,I added 'usb /dev/usb/scanner0' to=20 fujitsu.conf, and it works now. I coulduse scanimage to scan, but I = could=20 not use xsane, it prompted 'no device',and did not show the select = device=20 dialog, I guess that might be xsane'sconfiguration = problem?Another=20 problem is there is a IRQ conflict between fi-4120c and my NIC,here = is the=20 error log:eth0: transmit timed out, tx_status 00 status=20 e601diagnostics:net 0cd8 media 8880 dma 003a.eth0: Interrupt = posted=20 but not delivered -- IRQ blocked by another device?This is the = error log=20 when I tried to ping another Windows machine I usedto be able to=20 ping.Then I reboot the Linux machine, Redhat automatically = removed the=20 NICconfiguration, so I lost the network connection to my Windows = machine.=20 What should I do now?Thanks a=20 lot,Peter --=_NextPart_000_0005_01C2FC84.E57025D0--
[sane-devel] Could not locate Fujitsu fi-410c (untested?)
i have just recently gotten a 4120 myself. i am using the scsi port, not=20 the usb. i added some basic support to the fujitsu driver, and it was=20 placed in the cvs copy just a few days ago. so, you must use the latest=20 cvs source of sane to use this scanner. ( i was fortunate enough to follow= =20 behind ron cemer, who did most of the hard work) the different device numbers should not matter, since the fujitsu driver=20 uses the inquiry command (iirc) and string compairison to determine the=20 model, and both numbers you listed are associated with the 4x20 pair of=20 scanners, which are similar enough to make no difference. it is possible that you may see some color inversion using this scanner,=20 expect a patch in the next few days to address that. btw, i HIGHLY, HIGHLY recommend that you upgrade your os to at least=20 redhat 7.3 and apply every errata patch from updates.redhat.com, if you=20 are going to put the machine in question on the net. 7.1 contains many=20 security issues. allan On Sun, 6 Apr 2003, peter chen wrote: > Hi, > =A0 > In order to use Fujitsu fi-4120c, I=A0did the following: > =A0 > 1. Re-install Redhat 7.1 > =A0 > 2. add 'options scanner vendor=3D0x04c5 product=3D0x1041' to > /etc/modules.conf (to my surprise, when I powered fi-4120c on, and cat > 'proc/bus/usb/devices', the product id was 0x1041 instead of 0x0142 > for fi-4120c) > =A0 > 3. modprobe usb-uhci > =A0 > 4. modprobe scanner > then the scanner can be detected, 'Driver=3Dusbscanner'. > =A0 > Then I went to 'http://sane.informatik.uni-freiburg.de/anoncvs' and > downloaded sane-cvs-20030406.tar.gz, decompressed it and went into > frontend and backend and did the following: > =A0 > 1. ./configure > 2. make uninstall > 3. make > 4. make install > =A0 > then I ran sane-find-scanner, it reported it found usb scanner at > /dev/usb/scanner0, then I ran scanimage -L, scanimage --list-devices, > but they could not locate the scanner. > =A0 > I read from an article saying that the Linux kernel should be at least > 2.4.8 to work with the latest SANE (my Redhat 7.1 is 2.4.2-2), is this > the reason? > =A0 > And the product id is different (0x1041 instead of 0x1042) for > fi-4120c, could this be the reason? > =A0 > Or did I do anything wrong? > =A0 > I am considering re-installing Redhat Linux 9 and try again. > Is an error log necessary? > =A0 > Thanks, > =A0 > Peter >=20 > _= ___ > Add photos to your messages with MSN 8. Get 2 months FREE*. > ___ Sane-devel mailing list > sane-de...@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel >=20 --=20 "so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls" - Max Cavalera
[sane-devel] usb_submit_urb return ENOMEM?
Hi, On Sun, Apr 06, 2003 at 10:22:28PM +0800, Fan Dan wrote: >I have some problem in developing usb scanner.who can help me? You are talking about Linux kernel, not SANE? I guess linux-usb-devel is the right mailing list, see http://www.linux-usb.org. I'll cc that list. >when call usb_submit_urb() in probe_scanner() (scanner.c of kernel > 2.4.19), You'd better use the current code in 2.4.21-pre7. However, I don't think I have changed the interrupt code. > return is ENOMEM. why and how to resolve that? Check the code. Look where the ENOMEM comes from. I guess from somewhere in the host controller driver code. > My scanner has three endpoints (1 is bulk in, 2 is bulk out, 3 is > bulk interrupt). You know that the interrupt endpoint isn't really supported by the kernel scanner driver? The code is just a dummy currently. >Then I marked usb_submit_urb, scanner is probed, and ioctl system call > can be called. But when write_scanner, usb_bulk_msg return ENOMEM too. Why > and how to?? Please provide all details. Which scanner? Which host controller? Any other USB hardware used? Enable USB debugging in the kernel config and show us a complete log. Bye, Henning
[sane-devel] Microtek Slimscan C3 USB
Hi Josh, Henning is guessing right so please follow his advice. The C3's were buil= t in=20 different variations so I haven' yet a report if your particular model wo= rks=20 out of the box. But I think the chances are good because other C3's work=20 well. Please do your setup in these steps: -make the microtek kernel module recognize your scanner like Henning said= =2E -run sane-find-scanner; your scanner has to be reported, otherwise there = is=20 something wrong with your USB- or SCSI generic configuration -try your favourite scan program (most people prefer xsane) -in any case please make a logfile as described in the manpage sane-micro= tek2=20 and send it to me. If you have problems I can see some details in the=20 logfile. Bye Karsten On Friday 04 April 2003 10:37, Henning Meier-Geinitz wrote: > Hi, > > On Fri, Apr 04, 2003 at 12:02:08AM -0500, Josh Gladden wrote: > > I'm new to the list and have recently installed Linux on my system. = I > > have a Slimscan C3 USB scanner. I see that SANE supports the C3 > > PARPORT, but nothing about USB. Is there a way to redirect to the US= B > > port? > > The microtek2 maintainer may have more details for that issue. Anyway > I'm guessing a bit: > > Have a look at the manpage (sane-microtek2). The USB scanners are > supported by the microtec kernel module. So if that scanner uses a > SCSI-over-USB protocol it may work if you get it detected by the > microtek driver. You'll need to add the vendor & product ids to > drivers/usb/microtek.c. At least your scanner doesn't seem to be > mentioned there. > > Please show us the output of cat /proc/bus/usb/devices when your > scanner is plugged in. You may need to run "mount -t usbdevfs > /proc/bus/usb /proc/bus/usb" if that file isn't there. > > Bye, > Henning > ___ > Sane-devel mailing list > sane-de...@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] sanei_usb_init with 1.0.10: relocation error
Following is the ouputs I got. I am using Linux 2.4.18, Slackware 8.1, Scanjet 5300C, USB. How do I solve this problem (see last two lines of output)? I have not recompiled my kernel, so I think "sg" is built-in. bash-2.05a# sane-find-scanner # No SCSI scanners found. If you expected something different, make sure that # you have loaded a SCSI driver for your SCSI adapter. # Also you need support for SCSI Generic (sg) in your operating system. # If using Linux, try "modprobe sg". found USB scanner (vendor=0x03f0, product=0x0701) at /dev/usb/scanner0 # Your USB scanner was detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Scanners connected to the parallel port or other proprietary ports can't be # detected by this program. bash-2.05a# lsmod Module Size Used byNot tainted scanner 8480 0 uhci 23336 0 (unused) usbcore48000 0 [scanner uhci] parport_pc 14404 1 (autoclean) lp 6368 0 parport21664 1 [parport_pc lp] cs46xx 55080 0 (unused) ac97_codec 9568 0 [cs46xx] soundcore 3236 3 (autoclean) [cs46xx] pcmcia_core40896 0 ide-scsi7456 0 3c59x 24648 1 bash-2.05a# scanimage -L scanimage: relocation error: /usr/local/lib/sane/libsane-avision.so.1: undefined symbol: sanei_usb_init _ Download Norah Jones, Eminem and more! http://www.msn.com.sg/ringtones/
[sane-devel] Could not locate Fujitsu fi-410c (untested?)
Hi,
I had to reformat your message because it's HTML again. That's the
last time I respond to a HTML-only email.
On Sun, Apr 06, 2003 at 02:28:02AM +, peter chen wrote:
> In order to use Fujitsu fi-4120c, I did the following:
> 2. add 'options scanner vendor=0x04c5 product=0x1041' to
> /etc/modules.conf (to my surprise, when I powered fi-4120c on, and cat
> 'proc/bus/usb/devices', the product id was 0x1041 instead of 0x0142
> for fi-4120c)
Maybe I got the ids mixed when adding them to the kernel scanner
driver. What I have is:
| /* Fujitsu */
| { USB_DEVICE(0x04c5, 0x1041) }, /* fi-4220c USB/SCSI info:m...@mu-tec.de
| { USB_DEVICE(0x04c5,0x1042) }, /* fi-4120c USB/SCSI info:m...@mu-tec.de
| { USB_DEVICE(0x04c5, 0x1029) }, /* fi-4010c USB AVision info:mza@mu-tec.
The "41" and "42" may be a coincidence but it may also be an
indication for a mixup.
All the following is just guessed, I'm not the fujitsu maintainer:
> then I ran sane-find-scanner, it reported it found usb scanner at
> /dev/usb/scanner0, then I ran scanimage -L, scanimage --list-devices,
> but they could not locate the scanner.
fujitu.conf is set up correctly? I guess you need to add something like
"usb /dev/usb/scanner0".
> I read from an article saying that the Linux kernel should be at least
> 2.4.8 to work with the latest SANE (my Redhat 7.1 is 2.4.2-2), is this
> the reason?
I don't think so in this case. You need the newer versions if you want
to do autodetection using the vendor and product ids. For manually
setting the device file name it should work.
> And the product id is different (0x1041 instead of 0x1042) for
> fi-4120c, could this be the reason?
I don't think so, either. Looks like the backend soen't check the ids
at all.
> I am considering re-installing Redhat Linux 9 and try again.
Ususally it doesn't help to reinstall anything. Setting up software
may help :-)
> Is an error log necessary?
If setting up fujitsu.conf doesn't help, show us the output of
SANE_DEBUG_FUJITSU=255 scanimage -L
Bye,
Henning
[sane-devel] sanei_usb_init with 1.0.10: relocation error
Hi,
On Sun, Apr 06, 2003 at 01:18:47PM +0800, Daniel Sim wrote:
> Following is the ouputs I got. I am using Linux 2.4.18, Slackware 8.1,
> Scanjet 5300C, USB. How do I solve this problem (see last two lines of
> output)? I have not recompiled my kernel, so I think "sg" is built-in.
You only need sg for SCSI scanners or USB scanners that use a
SCSI-over-USB kernel driver. In current avision backends that doesn't
seem to be the case. That's why you can use the generic USB kernel
scanner driver ("scanner.o") at all.
> scanimage: relocation error: /usr/local/lib/sane/libsane-avision.so.1:
> undefined symbol: sanei_usb_init
In SANE 1.0.10 the avision backend doesn't use "sanei_usb_init". So am
I right that you just used sane 1.0.10 and copied the latest avision
backend into the source code? That doesn't seem to work. Get a
CVS snapshot that includes the backend (see SANE homepage, download
section). I haven't checked the backend code but I guess in addition
to the backend itsself you need updates to the sanei code and
backend/Makefile.in. All of those are included in the CVS snapshot.
If the avision maintainer reads this: the avision manpage still talks
about the hpusbscsi modules and is otherwise pretty SCSI-centric :-)
Bye,
Henning
[sane-devel] Could not locate Fujitsu fi-410c (untested?)
Hi, In order to use Fujitsu fi-4120c, I did the following: 1. Re-install Redhat 7.1 2. add 'options scanner vendor=0x04c5 product=0x1041' to /etc/modules.conf (to my surprise, when I powered fi-4120c on, and cat 'proc/bus/usb/devices', the product id was 0x1041 instead of 0x0142 for fi-4120c) 3. modprobe usb-uhci 4. modprobe scanner then the scanner can be detected, 'Driver=usbscanner'. Then I went to 'http://sane.informatik.uni-freiburg.de/anoncvs' and downloaded sane-cvs-20030406.tar.gz, decompressed it and went into frontend and backend and did the following: 1. ./configure2. make uninstall3. make4. make install then I ran sane-find-scanner, it reported it found usb scanner at /dev/usb/scanner0, then I ran scanimage -L, scanimage --list-devices, but they could not locate the scanner. I read from an article saying that the Linux kernel should be at least 2.4.8 to work with the latest SANE (my Redhat 7.1 is 2.4.2-2), is this the reason? And the product id is different (0x1041 instead of 0x1042) for fi-4120c, could this be the reason? Or did I do anything wrong? I am considering re-installing Redhat Linux 9 and try again. Is an error log necessary? Thanks, PeterAdd photos to your messages with http://g.msn.com/8HMLENUS/2749";>MSN 8. Get 2 months FREE*.
[sane-devel] Mustek Scanmagic 9636S not works
>Hi, > >please respond to the list, not to me. Maybe other people have more >ideas about your problem. > >System: > >Debian Woody 3.0 > >Kernel compiled: 2.4.14 > >Module: g_NCR5380 > > > >Scanner: Mustek Scanmagic 9636S > >Chip: DTC3181LE(DOMEX 436P) > > > >Command modprobe g_NCR5380 ncr_addr=0x280 dtc_3181e=1 Fail > >Why??? > > >On Sat, Apr 05, 2003 at 01:58:48PM +, José López Ruiz wrote: > > init_module: No such device. >> Hint: insmod errors can be caused by incorrect module parameters, >>including invalid IO or IRQ parameters. >> insmod /lib/modules/2.4.14/kernel/drivers/scsi/g_NCR5380.o failed. >> insmod g_NCR5380 failed. >> >> >> >>>Well, I don't have clairvoyance :-) What are the error messages on the >>>command line and in /var/log/syslog? >>> >>> > >Looks like wrong parameters. All my cards worked with the default >settings but some people reported that they had to change i/o >settings. Maybe a different card uses the same i/o range? > > > >> With other I/O not works. The same error. >> >> > >Card defective or not plugged in correctly? Try a different ISA slot. > > > >>Apr 5 13:35:23 kernel: SCSI subsystem driver Revision: 1.00 >>Apr 5 13:35:23 kernel: scsi0 : SCSI host adapter emulation for IDE ATAPI >>devices >>Apr 5 13:35:23 kernel: Vendor: RICOH Model: CD-R/RW MP7083A Rev: 1.10 >>Apr 5 13:35:23 kernel: Type: CD-ROM ANSI >>SCSI revision: 02 >>Apr 5 13:35:23 kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, >>lun 0 >>Apr 5 13:35:23 kernel: sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 >>cdda tray >>Apr 5 13:35:23 kernel: Uniform CD-ROM driver Revision: 3.12 >> >> > >I'm not sure if this is a problem here but there were reports about >the SCSI emultation for CDROMS making trouble with detection of real >SCSI devices. I would be surprised if it stops the detection of SCSI >controllers but you'd better try without idescsi. > > > > > > > >
