[sane-devel] Re: scanner not recognised part II

2004-03-02 Thread m. allan noah
On Tue, 2 Mar 2004, Paul Frisson wrote: > Checked /var/log/messages in which I found no clue about the unloading the > driver. (can't paste the lines here because apparently I need to be logged as > root to read that file, is ther something like 'su' in graphical mode ? - I > don't feel it yet

[sane-devel] Re: scanner not recognised part II

2004-03-01 Thread m. allan noah
when the driver is unloaded, it may say something. so you could go back=20 thru your /var/log/messages, and see where this happens. there may be some= =20 clue on the preceding lines about why this happened. if the kernel is automatically booting the module (because it believes it= =20 is unused)

[sane-devel] Re: scanner not recognised part II

2004-03-01 Thread Paul Frisson
Yes, I already checked, and the line is there indeed, so the driver must be= =20 unloaded. Meanwhile I rebooted the machine and of course, the driver was gone, so I'm= =20 now looking for a way to load - or reload - it automatically.=20 Le Lundi 1 Mars 2004 00:41, Karl Heinz Kremer a =E9crit : >

[sane-devel] Re: scanner not recognised part II

2004-03-01 Thread Paul Frisson
Whf ! It worked :-) Many many thanks, and one last stupid question, where and what must be chan= ged=20 in order to load the driver at boot, not to have to retype the load command= ? Thank you again, I feel much better ! PF Le Dimanche 29 F=E9vrier 2004 23:48, Karl Heinz Kremer a

[sane-devel] Re: scanner not recognised part II

2004-02-29 Thread Paul Frisson
I suppose it must be a software/configuration problem since, as I said, it= =20 worked in RH9. Cabling supposed to be OK, the scanner works under windows (I have a dual=20 boot). The adapter is an adaptec AHA-2920, must be supported according to t= he=20 linux documentation. So, here comes my 'st

[sane-devel] Re: scanner not recognised part II

2004-02-29 Thread Karl Heinz Kremer
According to your boot messages, it was loaded at boot time. Something=20= must have unloaded it. I have no idea why this happens. Usually, the driver=20 should not get unloaded automatically. Check to see if you have this entry in your /etc/modules.conf file: alias scsi_hostadapter fdomain If n

[sane-devel] Re: scanner not recognised part II

2004-02-29 Thread Karl Heinz Kremer
The CD-R shows up as SCSI device because the CD burning software can=20 only work with SCSI devices. You are using the ide2scsi pseudo SCSI adapter=20= for this. As you can see, it does not see the scanner. THis means that it's=20= not a Sane problem, but a problem with the SCSI system (cabling,

[sane-devel] Re: scanner not recognised part II

2004-02-29 Thread Paul Frisson
No file neither directory names /dev/scanner (but there are /dev/scanner0 = and=20 scanner1 ... in /dev/usb) The cat /proc/scsi/scsi command provided the answer : Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: PLEXTOR Model: CD-R PX-W1210A Rev: 1.10 Type: CD-ROM

[sane-devel] Re: scanner not recognised part II

2004-02-29 Thread Paul Frisson
--Boundary-00=_rqbQAdZX4mcREmO Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Seems we have a problem here, even if I don't understand exactly what's goi= ng=20 on : output text-file is joined. Le Dimanche 29 F=E9vrier 2004

[sane-devel] Re: scanner not recognised part II

2004-02-29 Thread Karl Heinz Kremer
If you have a file named /dev/scanner, please remove it. Do you have any other SCSI devices? Please run this command with your=20 scanner attached and turned on: cat /proc/scsi/scsi Edit the file dll.conf and disable all other entries but the one for=20 the scanners you have (in a first step, you

[sane-devel] Re: scanner not recognised part II

2004-02-28 Thread Karl Heinz Kremer
This looks more and more like a SCSI problem. Try the following: export SANE_DEBUG_SANEI_SCSI=3D3 scanimage -L Please provide the output. On Feb 28, 2004, at 9:23 AM, Paul Frisson wrote: > seems I have it loaded, this is the answer after the command : > > sg 36492 0 (auto

[sane-devel] Re: scanner not recognised part II

2004-02-28 Thread Paul Frisson
seems I have it loaded, this is the answer after the command : sg 36492 0 (autoclean) scsi_mod 108168 3 [sg sr_mod ide-scsi] Le Samedi 28 F=E9vrier 2004 14:51, Karl Heinz Kremer a =E9crit : > Do you have the sg module loaded? This is required for SCSI scanner

[sane-devel] Re: scanner not recognised part II

2004-02-28 Thread Paul Frisson
Still no scan possible, still 'no device available', even as root :-( PF Le Samedi 28 F=E9vrier 2004 14:15, Karl Heinz Kremer a =E9crit : > Now we are getting somewhere... Is it still not possible to scan as > root user? > > On Feb 28, 2004, at 8:04 AM, Paul Frisson wrote: > > here is the printed

[sane-devel] Re: scanner not recognised part II

2004-02-28 Thread Paul Frisson
--Boundary-00=_2HJQAGcNDnjQsX8 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline here is the printed text Le Samedi 28 F=E9vrier 2004 13:56, Karl Heinz Kremer a =E9crit : > The backend gets initialized correctly, so you should

[sane-devel] Re: scanner not recognised part II

2004-02-28 Thread Paul Frisson
--Boundary-00=_UyIQAhAIwUsM9y+ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Done, text in file-attach PF Le Samedi 28 F=E9vrier 2004 13:23, Karl Heinz Kremer a =E9crit : > Try to set the debug variable for the DLL backen

[sane-devel] Re: scanner not recognised part II

2004-02-28 Thread Paul Frisson
There wan no # before epson PF Le Samedi 28 F=E9vrier 2004 13:05, Karl Heinz Kremer a =E9crit : > Have you modified dll.conf as I suggested in one of my previous replies? > > Karl Heinz

[sane-devel] Re: scanner not recognised part II

2004-02-28 Thread Karl Heinz Kremer
Do you have the sg module loaded? This is required for SCSI scanners.=20 Please run this command: cat /proc/modules | grep sg Does this print a line that starts with "sg"? On Feb 28, 2004, at 8:22 AM, Paul Frisson wrote: > Still no scan possible, still 'no device available', even as root :-( >

[sane-devel] Re: scanner not recognised part II

2004-02-28 Thread Karl Heinz Kremer
Now we are getting somewhere... Is it still not possible to scan as=20 root user? On Feb 28, 2004, at 8:04 AM, Paul Frisson wrote: > here is the printed text > > Le Samedi 28 F=E9vrier 2004 13:56, Karl Heinz Kremer a =E9crit : >> The backend gets initialized correctly, so you should find debug=20

[sane-devel] Re: scanner not recognised part II

2004-02-28 Thread Karl Heinz Kremer
The backend gets initialized correctly, so you should find debug output from the EPSON backend when you set SANE_DEBUG_EPSON. Please try it=20 again: export SANE_DEBUG_EPSON=3D128 xsane Does this print anything? On Feb 28, 2004, at 7:41 AM, Paul Frisson wrote: > Done, text in file-attach > > P

[sane-devel] Re: scanner not recognised part II

2004-02-28 Thread Karl Heinz Kremer
Try to set the debug variable for the DLL backend: export SANE_DEBUG_DLL=3D3 Then run xsane again. What output do you get? On Feb 28, 2004, at 7:13 AM, Paul Frisson wrote: > There wan no # before epson > > PF > > Le Samedi 28 F=E9vrier 2004 13:05, Karl Heinz Kremer a =E9crit : >> Have you modif

[sane-devel] Re: scanner not recognised part II

2004-02-28 Thread Karl Heinz Kremer
Have you modified dll.conf as I suggested in one of my previous replies? Karl Heinz On Feb 28, 2004, at 6:28 AM, Paul Frisson wrote: > Hello, > > As I said in former message, I reinstalled the whole fedora, and yes ! > the > wireless is still working :-) > > Now that I am sure I have a 'virgin