OK, j said that his k3b worked fine after install and update.
So I moved my computer to a fast connection, reinstalled 9.1 Professional from CD (with HD format - to make sure it was clean) and did the online update.
No luck.
Tried the packman k3b V 0.11.14-0 that j suggested.
No luck. k3b just sits there looking and looking, the HD (it's a SCSI) shines its light brightly.
Both th CD and the CDRW are available to KDE as drives.
Any suggestions?
Conrad
SuSE's posted info in the db apply to 8.1, I am assuming they have no relevance to this problem that I am having with 9.1
__________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail
Have you tried something counterintuitive, such as downgrading to 9.0 and checking to see if k3b works then?
Reasoning?
When I upgraded to 9.0 the USB printer stopped working (could see it and print to it using one form of the shell command but not the other)
clean installing didn't work
upgrading to 9.1 didn't work
clean installing 9.1 did
From this I deduce that there are some malformed config files or mappings (i.e., some form of clerical error in the packaging process). Unfortunately I don't know enough to know whether I'm talking rubbish.
However...
I have a USB scanner that I can now no longer access through kooka/sane/xsane even though I can test it successfully in YaST. This feels like further supporting evidence
I've got no idea if this is helpful
On Sunday 29 August 2004 07:10, Conrad Schuler wrote:
OK, j said that his k3b worked fine after install and update.
So I moved my computer to a fast connection, reinstalled 9.1 Professional from CD (with HD format - to make sure it was clean) and did the online update.
No luck.
Tried the packman k3b V 0.11.14-0 that j suggested.
No luck. k3b just sits there looking and looking, the HD (it's a SCSI) shines its light brightly.
Both th CD and the CDRW are available to KDE as drives.
Any suggestions?
Conrad
SuSE's posted info in the db apply to 8.1, I am assuming they have no relevance to this problem that I am having with 9.1
Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail
* Gerry Gavigan gg@gerryg.uklinux.net [08-29-04 03:47]:
However...
I have a USB scanner that I can now no longer access through kooka/sane/xsane even though I can test it successfully in YaST.
Have you gone to http://www.xsane.org to see if xsane supports your scanner? XSane is just a graphical user interface for sane and the applications that you cited as not seeing your scanner are all graphical.
If your scanner is not supported by xsane, you can still scan from the command line, or there are other scanner gui's available, such as: vuescan http://www.hamrick.com/vsm.html
What brand/model of scanner do you have? Have you checked in /etc/scan.d/ for the config file and does it require modification?
On Sunday 29 August 2004 14:14, Patrick Shanahan wrote:
Have you gone to http://www.xsane.org to see if xsane supports your scanner? XSane is just a graphical user interface for sane and the applications that you cited as not seeing your scanner are all graphical. If your scanner is not supported by xsane, you can still scan from the command line, or there are other scanner gui's available, such as: vuescan http://www.hamrick.com/vsm.html
What brand/model of scanner do you have? Have you checked in /etc/scan.d/ for the config file and does it require modification?
(I know you realise) I was posting to indicate that between upgrades some devices that were working, stop working (it is my experience that they start working again one upgrade later).
The scanner is the canoscan 670u and is auto detected by YaST and assigned the plustek driver. It successfully acquired a test image during set up. The scanner used to work through kooka in 9.0. Until 9.1 I have not needed to touch xsane.
Currently Yast describes the device as "libusb"
However I cannot find that device in /dev/usb to test xsane [plustek:/dev/usb/libusb] [-s] from the command line (so kooka and indeed the gimp are irrelevant at this time)
The entries dev/usb/ contains are [scanner0] [scanner1] etc.
It reminds me of the printer problem that I couldn't solve when I upgraded from 8.2 to 9.0. Then
echo -en "\rHello\r\f" >/dev/usblp0
worked, but
echo -en "\rHello\r\f" >/dev/usb/lp0
did not work and CUPS seemed to be looking for the latter entry. I tried symbolic linking but could not solve the problem.
I cannot find libusb anywhere so even if I had confidence in my ability to correctly create a symbolic link, I am not sure that it would be any use.
TIA
* Gerry Gavigan gg@gerryg.uklinux.net [08-29-04 12:28]:
On Sunday 29 August 2004 14:14, Patrick Shanahan wrote:
Have you gone to http://www.xsane.org to see if xsane supports your scanner? XSane is just a graphical user interface for sane and the applications that you cited as not seeing your scanner are all graphical. If your scanner is not supported by xsane, you can still scan from the command line, or there are other scanner gui's available, such as: vuescan http://www.hamrick.com/vsm.html
What brand/model of scanner do you have? Have you checked in /etc/scan.d/ for the config file and does it require modification?
(I know you realise) I was posting to indicate that between upgrades some devices that were working, stop working (it is my experience that they start working again one upgrade later).
A scientific observation
The scanner is the canoscan 670u and is auto detected by YaST and assigned the plustek driver. It successfully acquired a test image during set up. The scanner used to work through kooka in 9.0. Until 9.1 I have not needed to touch xsane.
So you didn't look to see if it was supported, but you say it worked with 9.0, so it is/was supported. And you did not check to see if the config file was correct or even there.
Currently Yast describes the device as "libusb"
libusb is a library "that allows userspace access to USB devices", not a device. libusb provides access to the device, probably /dev/usb/scanner0 or /dev/usbscanner
btw, I did not know what libusb was, I looked it up. Some interest *is* required.
rpm -q libusb will tell you if you have libusb installed
Yast *may* be telling you that libusb *is* required. Yast2 -> Install Software -> libusb will do it.
However I cannot find that device in /dev/usb to test xsane [plustek:/dev/usb/libusb] [-s] from the command line (so kooka and indeed the gimp are irrelevant at this time)
http://www.sane-project.org/man/sane-plustek.5.html says (you should read as it is somewhat long):
To use your scanner with this backend, you need at least two entries in the configuration file (there are more you might want): /usr/local/etc/sane.d/plustek.conf [usb] vendor-id product-id device /dev/usbscanner so you should have at least: /etc/sane.d/plustek.conf usb 0x04a9 0x220d /dev/usb/scanner0
or /etc/sane.d/canonusb.conf or /etc/sane.d/canon670u.conf
with the same lines, usb... & /dev/usb/scanner0
the /dev/usb/scanner0 line might want to be /dev/usbscanner, you will need to experiment
The entries dev/usb/ contains are [scanner0] [scanner1] etc.
yes, there is also, /dev/usbscanner
It reminds me of the printer problem that I couldn't solve when I upgraded
not related.... and will confuse the issue
I cannot find libusb anywhere so even if I had confidence in my ability to correctly create a symbolic link, I am not sure that it would be any use.
Why would you want to 'create a symbolic link'? Use rpm to see if it is installed and/or look for it with 'locate'. From what you have told me here, it seems that it needs to be installed, if it is not. It will not hurt anything to have it installed anyway, except use a little disk space, so install it.
On Sunday 29 August 2004 22:54, Patrick Shanahan wrote:
So you didn't look to see if it was supported, but you say it worked with 9.0, so it is/was supported. And you did not check to see if the config file was correct or even there.
I am not trying to waste your time - however I now realise I was being elliptical. www.sane-project.org reported that the scanner was fully supported by the plustek driver (but this was something that I knew because it used to work under 9.0)
YaST correctly applied the driver and successfully performed a test scan
I had also tried this:
linux:/ # sane-find-scanner
found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan], chip=LM9832/3) at libusb:002:002
# Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage.
and this
linux:/ # scanimage -L device `plustek:libusb:002:002' is a Canon N670U/N676U/LiDE20 USB flatbed scanner
libusb is a library "that allows userspace access to USB devices", not a device. libusb provides access to the device, probably /dev/usb/scanner0 or /dev/usbscanner
btw, I did not know what libusb was, I looked it up. Some interest *is* required.
thank you for the information - I made an assumption based on ignorance, not laziness. I am running libusb 0.1.8-31
so you should have at least: /etc/sane.d/plustek.conf usb 0x04a9 0x220d /dev/usb/scanner0
These are the last few lines of plustek.conf (sic)
# # and of course the device-name # # device /dev/usbscanner device auto
# # to define a new device, start with a new section: # [usb] # usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d
the /dev/usb/scanner0 line might want to be /dev/usbscanner, you will need to experiment
If I understand correctly "device auto" picks up the device.
However I ran it from the console, it was not recognised and I cannot find another reference to "device" the command
yes, there is also, /dev/usbscanner
all devices lists start with devicetype0 rather than devicetype - do you think that is an issue here?
Although you suggest the printer comment was irrelevant I notice that plustek.conf seems to be looking for "usbscanner" rather than "scanner" in usb/ similar to the formats that did/didn't work for testing usb printers
Gerry
* Gerry Gavigan gg@gerryg.uklinux.net [08-30-04 07:33]:
On Sunday 29 August 2004 22:54, Patrick Shanahan wrote:
linux:/ # sane-find-scanner found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan], chip=LM9832/3) at libusb:002:002
linux:/ # scanimage -L device `plustek:libusb:002:002' is a Canon N670U/N676U/LiDE20 USB flatbed scanner
so you should have at least: /etc/sane.d/plustek.conf usb 0x04a9 0x220d /dev/usb/scanner0
These are the last few lines of plustek.conf (sic)
# # and of course the device-name # # device /dev/usbscanner device auto
I would change this to 'device /dev/usbscanner'
# # to define a new device, start with a new section: # [usb] # usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d
and delete all but one of these 'usb 0x4a9 0x220d'
the /dev/usb/scanner0 line might want to be /dev/usbscanner, you will need to experiment
If I understand correctly "device auto" picks up the device.
why leave it to chance?
yes, there is also, /dev/usbscanner
all devices lists start with devicetype0 rather than devicetype - do you think that is an issue here?
no, reference plustek.conf (sited above).
Although you suggest the printer comment was irrelevant I notice that plustek.conf seems to be looking for "usbscanner" rather than "scanner" in usb/ similar to the formats that did/didn't work for testing usb printers
usb is relevant, printer is not, just happens to be usb??
make the changes to the plustek.conf and try xsane report
On Monday 30 August 2004 17:29, Patrick Shanahan wrote:
- Gerry Gavigan gg@gerryg.uklinux.net [08-30-04 07:33]:
These are the last few lines of plustek.conf (sic)
# # and of course the device-name # # device /dev/usbscanner device auto
I would change this to 'device /dev/usbscanner'
and delete all but one of these 'usb 0x4a9 0x220d'
make the changes to the plustek.conf and try xsane report
I tried as you suggested.
xsane could not find the scanner I went back to YaST and reinstalled the scanner (so I could test it) - this time YaST could not find the scanner either (and this is where the multiple "usb 0x4a9 0x220d" entries are coming from)
I restored the line in plustek.conf to "device auto" and reinstalled the scanner - this time YaST could detect it and do a test scan
Gerry
* Gerry Gavigan gg@gerryg.uklinux.net [08-31-04 17:58]:
I restored the line in plustek.conf to "device auto" and reinstalled the scanner - this time YaST could detect it and do a test scan
and xsane ???
On Wednesday 01 September 2004 01:39, Patrick Shanahan wrote:
and xsane ???
restoring the line in plustek.conf
from: device dev/usbscanner to: device auto
restored plustek.conf to its original state.
xsane could not find the scanner
* Gerry Gavigan gg@gerryg.uklinux.net [08-31-04 17:58]:
xsane could not find the scanner I went back to YaST and reinstalled the scanner (so I could test it) - this time YaST could not find the scanner either (and this is where the multiple "usb 0x4a9 0x220d" entries are coming from)
I restored the line in plustek.conf to "device auto" and reinstalled the scanner - this time YaST could detect it and do a test scan
post the FULL output from: scanimage -L and from: sane-find-scanner
You only posted *one* line of output earlier, I get five. Also post the versions of sane and xsane, ie: rpm -q sane rpm -q xsane
I can find nothing applicable on google.com/linux
On Wednesday 01 September 2004 01:55, Patrick Shanahan wrote:
post the FULL output from: scanimage -L
linux:/ # scanimage -L device `plustek:libusb:002:002' is a Canon N670U/N676U/LiDE20 USB flatbed scanner linux:/ #
and from: sane-find-scanner
linux:/ # 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.
found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan], chip=LM9832/3) at libusb:002:002 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program.
rpm -q sane
linux:/ # rpm -q sane sane-1.0.14-0.pm.0 linux:/ #
rpm -q xsane
linux:/ # rpm -q xsane xsane-0.95-0.pm.0 linux:/ #
the pm indicates that theses are the latest packages from www.packman.links2linux.de
I can find nothing applicable on google.com/linux
I have not tried that particular search but I did read everything I could find on the SUSE database
* Gerry Gavigan gg@gerryg.uklinux.net [09-01-04 03:13]:
I have not tried that particular search but I did read everything I could find on the SUSE database
Sorry, I do not know where to go from here.
I would be interested in knowing how you do solve this, if you do.
gud luk,
On Sat, 28 Aug 2004, Conrad Schuler wrote:
OK, j said that his k3b worked fine after install and update.
So I moved my computer to a fast connection, reinstalled 9.1 Professional from CD (with HD format - to make sure it was clean) and did the online update.
No luck.
Tried the packman k3b V 0.11.14-0 that j suggested.
No luck. k3b just sits there looking and looking, the HD (it's a SCSI) shines its light brightly.
Both th CD and the CDRW are available to KDE as drives.
Any suggestions?
Well i have a SCSI HD too and i haven't had any problems at all! As far as i know, i think there is no need to mess with ide-scsi options during kernel boot since SuSE 9.1.
Can u please try the other alternative package for cd-writing, "XCDRoast"?
Can u also please give some detailed info about your cdroms hardware like manufacturer etc...? (u can view detailed info about your hardware with the 'hwinfo' command, as root). When u say that K3B just sits there looking and looking, after how many minutes does it displays its main window (or it doesnt at all?). Can u enter in the Configuration of K3B dialog ? Have u seen the logs of the kernel/system? Is there any error/warning about your CDRW ? Have u tried to disconnect any of your cd-rom drives and see if K3B starts?
Conrad
SuSE's posted info in the db apply to 8.1, I am assuming they have no relevance to this problem that I am having with 9.1
Hope i helped...;) Filip.
-
Conrad Schuler -
Filippos Papadopoulos -
Gerry Gavigan -
Patrick Shanahan