aRTee

I do not have a "DisplaySize" entry in my XF86Config-4. This use to be determined/ or rather could be controlled in /etc/X11/XftConfig but that (as you know) has been done away with, so, other than the XF86Config-4, where would X get this value? I'm just wondering if your "DisplaySize" from XF86Config-4 is being overwritten somewhere else. xdpyinfo reveals the same as above for me. On my machine I get: and xdpyinfo confirmed this. If I don't put this DisplaySize line in the xfconfig, I get something like 97 dpi or so, it reads the info from the monitor. If I leave the monitor off without the DisplaySize line, it defaults to 75dpi. Well, no, not under kde, since then a session is already running. Also, if I log in with gnome as a de, evolution (and the gimp and some other apps, like video-dvdrip) still look bad, no matter what I set in the font stuff.... I'm trying to think of what I could get from that mdk9.1rc1 install that is on another partition,.... maybe I should just move /usr/share to something else and then link that old one...? [edit] nope that last thing didn't help either (did a mv /usr/share/themes /usr/share/themes.old and then ln -s /alt/usr/share/themes /usr/share/themes)

Just to take back what I said on the first page in this thread about Canon.... last week I installed a system with a Canon S630 and it was autodetected and worked like a charm. Note that I only printed out a standard (colour) testpage, but it did look ok. Don't know about the high res quality though. I'll let you know if I have the chance to print a picture on that machine (father in law's machine, normally uses win)..

Almost forgot to mention, I booted into mdk9.1rc1 which I still have on another partition and with other usernames... There everything was ok. So I created a new user (in 9.1 final), copied all data from the mdk9.1rc1 useraccount that was good, then started X + startkde,.. and I found it was not ok. So the difference must be in some config files of the system, not the user.... Now as to how to find this difference... ? (note that as that olduser I was using keramic, but also with galaxy the problem arises)

Yes, apologies for hijacking your thread..... Did you manage to solve things and if yes, how? No! I taught her well. Actually, not so long ago I asked if she'd prefer to autologon, and her response was: but that's not good for security, then everyone can start my computer and get to my files.... Anyway, I think I might enlighten you about the font size: this happens when you turn on your monitor AFTER having booted into X; check /var/log/XFree86.0.log and search for the string 'DPI', which you will find after the virtual resolution setting,.... it could be that the DPI value is set according to info from the display, and with a lack of that, it's set to 75 dpi hor and vert.. You can set this with a line like DisplaySize 403 302 in the monitor section of your /etc/X11/XF86Config-4 (this one makes my dpi setting 100), so that it doesn't matter whether the screen is on or off when X is started. Back to my gf's computer and mine, I just booted hers and checked, DPI is 75, so made mine the same, without effect... Tried this in a konsole, does nothing for me; the first doesn't do much, the second gives an error: WARNING **: Could not connect to gnome-session. is for gtk2 themes, and is for gtk1.2 themes. If the theme doesn't have a font entry you can put one in there. Thanks for your comment btw Gregor, did try that, without success.. I also did mv /usr/share/themes/Crux/gtk/gtkrc /usr/share/themes/Galaxy/gtk/gtkrc since the Crux theme has a font definition... didn't help either... From error messages I got when playing with /usr/share/themes/Galaxy/gtk/gtkrc and then starting evolution from the cli I know it is reading that file..... This is getting frustrating....

bvc, thanks for the link to that other thread, .. unfortunately, it didn't help me out... It seems a lot has changed since that thread (October, November last year)... Anyway, I played with the .gtk files in my homedir, and elsewhere, couldn't find anything. Weird thing is, I logged on as a testuser, so clean environment, started a gnome session and played with the font and other settings,... evolution seems to follow a different scheme, it never budged... What really bugs me, is that on my girlfriends computer everything looks fine.. or maybe it's because she has a much lower resolution that I can't tell it's not better..?

Very impressive!! Thanks a lot! About the improvement for kde or gnome, how did that thing end where they were confused about Mdk 9.0 kde being faster than Gentoo kde? At the time I didn't care to much to follow it,... did they figure out why this was? Or was it just a subjective false observation?

Hey great Motts, nice to find someone willing to try this! Also, you don't have to rip a whole dvd, you could just rip some part that takes, say, 10 minutes. At least then you could tell the difference.. (If you try with something that just takes a few secs you'd never be sure that it was a fair comparison..)

I have no idea about evolution being gtk or not (think so though), but in any case, the bad fonts were like that in bluefish, until I changed them (in bluefish), couldn't change them in evolution though (can change the font of the mailcontents, not of the drop down menus etc). Tried gnome-theme-manager, doesn't help... Also tried: gnome-default-applications-properties (something else), gnome-font-properties (close, but this helps to get things ok in gnome, not under kde..), gnome-ui-properties..... none helped out here. So if anyone has an idea, please let me know.

If you look at the bottom of each message, you find some buttons: profile, pm (personal message), and in my case you also see WWW.... try clicking that. From the looks of it, you have already followed DOlsons info (from that other website) in which case you now have OSS instead of ALSA. The control you want is IGain or OGain (forgot which one), make sure it's not muted (green ledlike light) and pump up the volume... Let me know if that works.

Apart from the fact that it can be good fun and very rewarding to completely build your own system, not to mention the great learning experience, I don’t really see why you should recompile your system to get a few seconds here and there if it costs 4 days to compile and set things up.... ;) If I ever have time left, I will definitely try gentoo, or lfs, but for now, I still want to install SuSE to try out (someone gave me a cd to try it), never used that, also on the agenda is check out more stuff on mdk9.1 (my remote is not working yet). And of course, work on my website. Question: could anyone with such an optimised system compile something for i586 and compare the speed with athlon optimised code? Sort of, benchmark the system? Try it with something like, divx encoding, ogg encoding etc. Those are tasks that are normally long and there it would help if you can speed things up, even if it’s only a few % (just encoded a movie to divx for the first time, 2 pass: 5:30 + 6:20 hrs..)

Be aware that in case of a diskcrash, or just exchange, your system will not have a swap.... Also, I have not seen any swap used since I put in my second 512MB stick... :) Another thing to keep in mind is that with 2 drives, you also have 2 cashes on the drives, normal size is 2MB nowadays, so you double that to 4MB...

Just try it, and if you manage to post after installing, it can work If we don’t hear from you anymore, it’s a nice warning for all. ;) Seriously, I think it should be no problem, I have all msoffice and wpoffice fonts, that’s a couple of hundred... Maybe you can just add a part of those fonts and see if it’s still ok?

Look on the configuration page of my site,... all you have to do (which is not logical, but not hard) is open kmix, and go to the last controls. One is called: analog rear or so, MUTE this one (yeah weird). Then you will have sound from the rear speakers, fiddle to find out which mixer controls let you adjust the volume. You do not need the stuff from that other mdkxp site, it can work with alsa (DOlsons site explains how to do it with OSS, I used that in mdk9.0 with success, now it’s no longer necessary).

I have the same problem, didn’t post about it yet (other things to do)... But: on my mdk9.1 machine, I use kde. Evolution shows this problem. I changed the gnome font, so under gnome no problem. Under kde, evolution still looks like crap. Bluefish allowed me to change the font, now looks fine... No idea why under kde evolution looks like in your screenshot, but under gnome it’s fine... Also, I made a new user, to make sure it wasn’t some old setting. No good. On the other hand, on my girlfriends machine, all is fine since I installed 9.1, evolution under kde looks great...... weird.

I just put the old fstab entry into my new mdk9.0 and later mdk9.1 /etc/fstab and they mount on boot without any problem. You should not have to resort to editing /etc/rc.local or anything else, just /etc/fstab At the time (mdk8.2) I set things up with linuxconf, later just copied the right entries to the new /etc/fstab.

The point is, it has to be possible to use in a presentation for instance, so using latex would give me a pdf, not what I need.... I give ImageMagick a go, see how far it gets.. I just hope it can read .ps/.eps

Ok, added remarks to fix all things that were commented on here. Have a look, and tell me what you think. If anyone wants to exchange links, just post your link.

No I don't have one. I just copy pasted what my colleague mailed me in response.. Enjoy your portable linux device! (I'm waiting for the one with the vga resolution screen to become available... and affordable.. :) )

pmpatrick, I just fixed the problem you indicated; also: gregor, fixed the hp4200.conf into HP4200.conf (didn'tcatch that in your earlier comment). So now it detects the scanner fine with scanimage -L But it doesn't do any good, the result is still: cannot open device, operation not supported... Any more suggestions for me and gregor?

Ok, here's some info from this colleague: So there you go, you can take another OS and stick it on, control your pc if you have a wireless network etcetc... And I realise you're not going to pass it to me for 100$, but then again, too bad ;) edit: ps welcome as a new mdk user!

I have a colleague who has this device, he's linux only, and no problems. (Using mdk since I gave him the discs, not sure if he moved to 9.1 but with 9.0 all was fine) You don't get the linux software since it is normally already there. The darn thing can do anything,.... coolest thing: opened a prompt,... got a full command line interface: running bash. And I was directly root... ;) If you want, I can ask him what he uses or how. Or maybe I should shut up and offer you 100$ for the thing... ;)

I'm looking for a way to import .eps or .ps files into documents, in a way that will actually show the image in the document on the screen, before printing it (to a postscript file if need be). What is important is that the vector graphics information is not lost, so importing it into the Gimp, which can be done (I used that) is not the right approach for me. The imported image should show up on the screen (for instance, in a presentation), but also have the same quality as the original .ps when getting printed. I know .eps can have a preview, but that preview cannot scale nicely, and I know that I can use pstoepsi to convert from ps to eps, so from here on I will only write .ps but also mean .eps. There are some (non-free) programs that can convert .ps to wmf (windows vector graphics), which can be imported, viewed and altered in OOo. I have looked at convertPS, pstoedit and ps2vector. What other options are there? Are there any OSS programs that import ps (or pdf) and show a decent, scalable preview (that doesn't get blocky)? Are there any OSS programs that can do a conversion from .ps to a vector format which could then be imported into a document?

This probably happened since I also unplugged and replugged my scanner and webcam... I will try what you suggest tonight at home though, but I don't think that will help.... will see, you never know. (Actually, it is trying to talk to the scanner via /dev/usbscanner anyway...)

Hey, now we are really curious! Tell us! BTW I was just thinking you may have had the drive set to the wrong country code. So what was it really?

Ok, I've been at it a bit again,... Gregory, nice to know you're on my side; I was already thinking why you got that link so quickly to say it wasn't supported,... guess you had been looking for it too.. (btw I have to wonder if all this is worth it, 8-bit color and 600dpi seems to be the limit) I'm sorry if this post gets long, but I don't want to omit anything that might give a hint as to what could be a remedy for this situation. here we go (I'm posting the whole result for comparison reasons) : [root@zurich robert]# rmmod scanner [root@zurich robert]# SANE_CONFIG_DIR=/etc/sane.d SANE_DEBUG_HP4200=128 SANE_DEBUG_SANEI_USB=128 SANE_DEBUG_DLL=128 scanimage -d hp4200:/proc/bus/usb/001/003 [sanei_debug] Setting debug level of dll to 128. [dll] sane_init: SANE dll backend version 1.0.8 from sane-backends 1.0.11 [dll] add_backend: adding backend `hp4200' [dll] load: searching backend `hp4200' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-hp4200.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-hp4200.so.1' [dll] init: initializing backend `hp4200' [sanei_debug] Setting debug level of hp4200 to 128. [hp4200] sane_hp4200_init [sanei_debug] Setting debug level of sanei_usb to 128. [sanei_usb] sanei_usb_init: found kernel scanner device (0x03f0/0x0105) at /dev/usb/scanner0 usb_set_debug: Setting debugging level to 255 (on) usb_find_busses: Skipping non bus directory devices usb_find_busses: Skipping non bus directory drivers usb_find_busses: Found 005 usb_find_busses: Found 004 usb_find_busses: Found 003 usb_find_busses: Found 002 usb_find_busses: Found 001 usb_find_devices_on_bus: Found 001 on 001 usb_find_devices_on_bus: Found 002 on 001 skipped 1 class/vendor specific interface descriptors usb_find_devices_on_bus: Found 003 on 001 usb_find_devices_on_bus: Found 001 on 002 usb_find_devices_on_bus: Found 001 on 003 usb_find_devices_on_bus: Found 002 on 003 skipped 4 class/vendor specific interface descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors usb_find_devices_on_bus: Found 001 on 004 usb_find_devices_on_bus: Found 001 on 005 [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: device 0x046d/0xc506 doesn't look like a scanner (0/3) [sanei_usb] sanei_usb_init: found libusb device (0x03f0/0x0105) at libusb:001:003 [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: found libusb device (0x0471/0x0312) at libusb:003:002 [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: found 3 devices [hp4200] sane_hp4200_init: configuration file not found, defaulting to /dev/usbscanner. [hp4200] add_device(/dev/usbscanner) [hp4200] find_device [hp4200] add_device: open(/dev/usbscanner) failed: No such file or directory [hp4200] sane_hp4200_init: failed to add device "/dev/usbscanner" [dll] init: backend `hp4200' is version 1.0.0 [hp4200] sane_hp4200_open (/proc/bus/usb/001/003, 0xbffff074) [hp4200] find_device [hp4200] add_device(/proc/bus/usb/001/003) [hp4200] find_device [sanei_usb] kernel_get_vendor_product: ioctl (vendor) of device 0 failed: Invalid argument [sanei_usb] sanei_usb_get_vendor_product: ioctl (product) of device 0 failed: Invalid argument [sanei_usb] sanei_usb_get_vendor_product: device 5: Your OS doesn't seem to support detection of vendor+product ids [hp4200] : sanei_usb_get_vendor_product failed scanimage: open of device hp4200:/proc/bus/usb/001/003 failed: Operation not supported [dll] sane_exit: exiting [dll] sane_exit: calling backend `hp4200's exit function [hp4200] sane_hp4200_exit [hp4200] sane_hp4200_close (0x80625f8) [dll] sane_exit: finished Ok, so wrong syntax or so. Then I thought: let's try it the right way: [root@zurich robert]# SANE_CONFIG_DIR=/etc/sane.d SANE_DEBUG_HP4200=128 SANE_DEBUG_SANEI_USB=128 SANE_DEBUG_DLL=128 scanimage -L [sanei_debug] Setting debug level of dll to 128. [dll] sane_init: SANE dll backend version 1.0.8 from sane-backends 1.0.11 [dll] add_backend: adding backend `hp4200' [dll] load: searching backend `hp4200' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-hp4200.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-hp4200.so.1' [dll] init: initializing backend `hp4200' [sanei_debug] Setting debug level of hp4200 to 128. [hp4200] sane_hp4200_init [sanei_debug] Setting debug level of sanei_usb to 128. usb_set_debug: Setting debugging level to 255 (on) usb_find_busses: Skipping non bus directory devices usb_find_busses: Skipping non bus directory drivers usb_find_busses: Found 005 usb_find_busses: Found 004 usb_find_busses: Found 003 usb_find_busses: Found 002 usb_find_busses: Found 001 usb_find_devices_on_bus: Found 001 on 001 usb_find_devices_on_bus: Found 002 on 001 skipped 1 class/vendor specific interface descriptors usb_find_devices_on_bus: Found 003 on 001 usb_find_devices_on_bus: Found 001 on 002 usb_find_devices_on_bus: Found 001 on 003 usb_find_devices_on_bus: Found 002 on 003 skipped 4 class/vendor specific interface descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors usb_find_devices_on_bus: Found 001 on 004 usb_find_devices_on_bus: Found 001 on 005 [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: device 0x046d/0xc506 doesn't look like a scanner (0/3) [sanei_usb] sanei_usb_init: found libusb device (0x03f0/0x0105) at libusb:001:003 [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: found libusb device (0x0471/0x0312) at libusb:003:002 [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: found 2 devices [hp4200] sane_hp4200_init: configuration file not found, defaulting to /dev/usbscanner. [hp4200] add_device(/dev/usbscanner) [hp4200] find_device [hp4200] add_device: open(/dev/usbscanner) failed: No such file or directory [hp4200] sane_hp4200_init: failed to add device "/dev/usbscanner" [dll] init: backend `hp4200' is version 1.0.0 [hp4200] sane_hp4200_get_devices (0xbffff0a8, 0) No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). [dll] sane_exit: exiting [dll] sane_exit: calling backend `hp4200's exit function [hp4200] sane_hp4200_exit [dll] sane_exit: finished Hmm, did I read that correctly that it found a device but couldn't connect to it since /dev/usbscanner doesn't exist? (Which is the default since I commented out the line /dev/usb/scanner0 from /etc/sane.d/hp4200.conf ) Let's try again: [root@zurich robert]# ln -s /dev/usb/scanner0 /dev/usbscanner [root@zurich robert]# SANE_CONFIG_DIR=/etc/sane.d SANE_DEBUG_HP4200=128 SANE_DEBUG_SANEI_USB=128 SANE_DEBUG_DLL=128 scanimage -L [sanei_debug] Setting debug level of dll to 128. [dll] sane_init: SANE dll backend version 1.0.8 from sane-backends 1.0.11 [dll] add_backend: adding backend `hp4200' [dll] load: searching backend `hp4200' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-hp4200.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-hp4200.so.1' [dll] init: initializing backend `hp4200' [sanei_debug] Setting debug level of hp4200 to 128. [hp4200] sane_hp4200_init [sanei_debug] Setting debug level of sanei_usb to 128. [sanei_usb] sanei_usb_init: found kernel scanner device (0x03f0/0x0105) at /dev/usbscanner [sanei_usb] sanei_usb_init: found kernel scanner device (0x03f0/0x0105) at /dev/usb/scanner0 usb_set_debug: Setting debugging level to 255 (on) usb_find_busses: Skipping non bus directory devices usb_find_busses: Skipping non bus directory drivers usb_find_busses: Found 005 usb_find_busses: Found 004 usb_find_busses: Found 003 usb_find_busses: Found 002 usb_find_busses: Found 001 usb_find_devices_on_bus: Found 001 on 001 usb_find_devices_on_bus: Found 002 on 001 skipped 1 class/vendor specific interface descriptors usb_find_devices_on_bus: Found 003 on 001 usb_find_devices_on_bus: Found 001 on 002 usb_find_devices_on_bus: Found 001 on 003 usb_find_devices_on_bus: Found 002 on 003 skipped 4 class/vendor specific interface descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors usb_find_devices_on_bus: Found 001 on 004 usb_find_devices_on_bus: Found 001 on 005 [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: device 0x046d/0xc506 doesn't look like a scanner (0/3) [sanei_usb] sanei_usb_init: found libusb device (0x03f0/0x0105) at libusb:001:003 [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: found libusb device (0x0471/0x0312) at libusb:003:002 [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: found 4 devices [hp4200] sane_hp4200_init: configuration file not found, defaulting to /dev/usbscanner. [hp4200] add_device(/dev/usbscanner) [hp4200] find_device [dll] init: backend `hp4200' is version 1.0.0 [hp4200] sane_hp4200_get_devices (0xbffff0a8, 0) device `hp4200:/dev/usbscanner' is a Hewlett-Packard HP-4200 flatbed scanner [dll] sane_exit: exiting [dll] sane_exit: calling backend `hp4200's exit function [hp4200] sane_hp4200_exit [dll] sane_exit: finished Hello! It said my scanners name! ;) Unfortunately, at this point when I try (as user or as root): xsane -d hp4200:/dev/usbscanner I get a popup: Failed to open device 'hp4200:/dev/usbscanner': Operation not supported So then I put the path /dev/usb/scanner0 back into the hp4200.conf file and removed /dev/usbscanner (the link) but it still didn't see it, it really wants it at /dev/usbscanner: [root@zurich robert]# SANE_CONFIG_DIR=/etc/sane.d SANE_DEBUG_HP4200=128 SANE_DEBUG_SANEI_USB=128 SANE_DEBUG_DLL=128 scanimage -L [sanei_debug] Setting debug level of dll to 128. [dll] sane_init: SANE dll backend version 1.0.8 from sane-backends 1.0.11 [dll] add_backend: adding backend `hp4200' [dll] load: searching backend `hp4200' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-hp4200.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-hp4200.so.1' [dll] init: initializing backend `hp4200' [sanei_debug] Setting debug level of hp4200 to 128. [hp4200] sane_hp4200_init [sanei_debug] Setting debug level of sanei_usb to 128. [sanei_usb] sanei_usb_init: found kernel scanner device (0x03f0/0x0105) at /dev/usb/scanner0 usb_set_debug: Setting debugging level to 255 (on) usb_find_busses: Skipping non bus directory devices usb_find_busses: Skipping non bus directory drivers usb_find_busses: Found 005 usb_find_busses: Found 004 usb_find_busses: Found 003 usb_find_busses: Found 002 usb_find_busses: Found 001 usb_find_devices_on_bus: Found 001 on 001 usb_find_devices_on_bus: Found 002 on 001 skipped 1 class/vendor specific interface descriptors usb_find_devices_on_bus: Found 003 on 001 usb_find_devices_on_bus: Found 001 on 002 usb_find_devices_on_bus: Found 001 on 003 usb_find_devices_on_bus: Found 002 on 003 skipped 4 class/vendor specific interface descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 2 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors usb_find_devices_on_bus: Found 001 on 004 usb_find_devices_on_bus: Found 001 on 005 [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: device 0x046d/0xc506 doesn't look like a scanner (0/3) [sanei_usb] sanei_usb_init: found libusb device (0x03f0/0x0105) at libusb:001:003 [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: found libusb device (0x0471/0x0312) at libusb:003:002 [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: found 3 devices [hp4200] sane_hp4200_init: configuration file not found, defaulting to /dev/usbscanner. [hp4200] add_device(/dev/usbscanner) [hp4200] find_device [hp4200] add_device: open(/dev/usbscanner) failed: No such file or directory [hp4200] sane_hp4200_init: failed to add device "/dev/usbscanner" [dll] init: backend `hp4200' is version 1.0.0 [hp4200] sane_hp4200_get_devices (0xbffff0a8, 0) No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). [dll] sane_exit: exiting [dll] sane_exit: calling backend `hp4200's exit function [hp4200] sane_hp4200_exit [dll] sane_exit: finished Ok, no problem: [root@zurich robert]# mknod /dev/usbscanner c 180 48 made sure that running the scanimage -L would see the scanner again. I also did a chmod 777 /dev/usbscanner since it didn't have the same permissions as /dev/usb/scanner0 ... but the result is still the same: operation not supported... BTW the mknod wasn't too bad at all: [root@zurich robert]# 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=0x03f0, product=0x0105) at /dev/usb/scanner0 found USB scanner (vendor=0x03f0, product=0x0105) at /dev/usbscanner found USB scanner (vendor=0x03f0, product=0x0105) at libusb:001:003 found USB scanner (vendor=0x0471, product=0x0312) at libusb:003:002 # A USB device was detected. This program can't be sure if it's really # a scanner. If it is your scanner, 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. [root@zurich robert]# scanimage -L device `hp4200:/dev/usbscanner' is a Hewlett-Packard HP-4200 flatbed scanner [root@zurich robert]# But it keeps saying operation not supported... :( So what else is there to try?