Hi, Since upgrading to 7.1 with kernel 2.4.2 my scanner is inoperative. It is an SCSI Epson Perfection 1200. Xsane and Xscanimage cannot find a scanner: KDE control centre SCSI info shows it as a "processor". When I try to add the scanner through YAST 1 it tells me that the device i have selected does not appear to be a scanner. The Epson is connected through the advansys module which correctly id's my cdwriter Any clues would be most welcome:) -- Stu "The specification said Windows 95 or better, so I installed Linux"
Getting weirdness too... Try doing xsane -s, if that fails try doing it twice and check the message window. I was getting the same problem and noticed SCSI errors in the message window and had to try a few times before it saw the device. Also, try running it as root, there must be a setting somewhere that enables a user to use the scanner. Matt On Fri, 16 Mar 2001, Stewart Watson wrote:
Hi,
Since upgrading to 7.1 with kernel 2.4.2 my scanner is inoperative. It is an SCSI Epson Perfection 1200. Xsane and Xscanimage cannot find a scanner: KDE control centre SCSI info shows it as a "processor".
When I try to add the scanner through YAST 1 it tells me that the device i have selected does not appear to be a scanner.
The Epson is connected through the advansys module which correctly id's my cdwriter
Any clues would be most welcome:) -- Stu
"The specification said Windows 95 or better, so I installed Linux"
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On Friday 16 March 2001 21:46, Matthew Johnson wrote:
Getting weirdness too...
Try doing xsane -s, if that fails try doing it twice and check the message window. I was getting the same problem and noticed SCSI errors in the message window and had to try a few times before it saw the device.
Also, try running it as root, there must be a setting somewhere that enables a user to use the scanner.
Matt
Thanks for your quick response. The xsane -s didn't work. Su'd and still didn't work. logged in as root and bothe xsane and xscanimage no problem. did a chmod for /dev/sga logged back in as user and lo and behold--it all works. Its often the simple things that get you; I was being totally misled by the "processor" identification Happy now though Ta -- Stu "The specification said Windows 95 or better, so I installed Linux"
participants (2)
-
Matthew Johnson
-
Stewart Watson