"if your kernel version and system tools don't match, things could be messed up." I think you're right about that.
Let me recap. Gutsy was having a hibernation problem with my new hardware (see http://ubuntuforums.org/showthread.php?t=760026) so it was suggested by several gurus I trust to give the Hardy kernel a try on Gutsy as per this thread - http://ubuntuforums.org/showthread.php?t=646755 This was before Hardy was released. It fixed the hibernation issue and hasn't affected anything else that I am aware of. Wine, Compiz, XAMPP etc all run as before. Just to confirm, I booted an old machine that has a Hardy install. xsane launched and lsusb worked properly too. (Should have thought to try that myself before posting.) Is there any way to get this working with my current kernel/OS mismatch? Or will I have to go to Virtual Box or another machine when I need to scan something until I upgrade? Thanks for zeroing in on the root of the problem. Till now, I have been blown away with how easy to use and reliable xsane has been. It handles the legacy scanner better than the funky drivers XP offered way back when . . . LOL! Quoting "m. allan noah" <kitno455 at gmail.com>: > On Wed, Jun 18, 2008 at 11:12 AM, <earther at eartherdesigns.com> wrote: >> NOTHING! Even though I have an external USB drive and USB thumb drive >> mounted!! What's up with that?? > > dont know. obviously you have some sort of system problem lower than > sane. what were you saying about running the wrong kernel or some > such? if your kernel version and system tools dont match, things could > be messed up. > > allan > >> >> Sorry I didn't catch that reply didn't go to the list. >> >> Quoting "m. allan noah" <kitno455 at gmail.com>: >> >>> please- always include the list on your responses, as others might >>> have more ideas. >>> >>> lets see the output of running lsusb >>> >>> allan >>> >>> On Wed, Jun 18, 2008 at 10:53 AM, <earther at eartherdesigns.com> wrote: >>>> >>>> Thanks for responding. Here's the ouput. What next? >>>> >>>> ~# SANE_DEBUG_NIASH=255 scanimage -L >>>> [sanei_debug] Setting debug level of niash to 255. >>>> [niash] sane_init >>>> [niash] Looking for ScanJet 3300C... >>>> [niash] Looking for ScanJet 3400C... >>>> [niash] Looking for ScanJet 4300C... >>>> [niash] Looking for HP ScanJet 4300c... >>>> [niash] Looking for Snapscan Touch... >>>> [niash] Looking for Office Scanner USB 19200... >>>> [niash] sane_get_devices >>>> >>>> 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). >>>> [niash] sane_exit >>>> >>>> >>>> >>>> Quoting "m. allan noah" <kitno455 at gmail.com>: >>>> >>>>> xsane is not the problem, but sane probably is. run this at the >>>>> command line as root: >>>>> >>>>> SANE_DEBUG_NIASH=255 scanimage -L >>>>> >>>>> and post the output to this list. >>>>> >>>>> allan >>>>> >>>>> On Wed, Jun 18, 2008 at 10:10 AM, <earther at eartherdesigns.com> wrote: >>>>>> >>>>>> Thought I would post a screenie of the device manager info for the >>>>>> ScanJet. Why can't xsane find it? >>>>>> >>>>>> http://www.eartherdesigns.com/ss/scanjet.jpg >>>>>> >>>>>> >>>>>> -- >>>>>> sane-devel mailing list: sane-devel at lists.alioth.debian.org >>>>>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel >>>>>> Unsubscribe: Send mail with subject "unsubscribe your_password" >>>>>> to sane-devel-request at lists.alioth.debian.org >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> "The truth is an offense, but not a sin" >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> -- >>> "The truth is an offense, but not a sin" >>> >> >> >> >> > > > > -- > "The truth is an offense, but not a sin" >
