03f0:1205 [Asus A7N266VM] Scanner does not work: Simple scan gives a device busy error

[Janos G. Komaromi]

This is a virgin installation of 13.04.

Scanner is not found - reported by Simple scan. I tried Ask Ubuntu, but got no answer.

I have a parallel installation of 12.xx on the same computer, and scanner does work. So what is specific about 13.04?

I have also an old FC-3 installation and the scanner works, using sane with xinetd. I notice that 13.04 does not use xinetd. So how is the scanner accessed? Whatever it is, it works on 12.xx and does not on 13.04.

In terminal mode:

sane-find-scanner
   found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1205 [hp scanjet scanner]) at libusb:002:002

scanimage -L
   [hp5590] hp5590_get_status: USB-in-USB: got non-zero device status (status 12)
   [hp5590] hp5590_init_scanner: scanner reports non-zero status: Device busy

lsusb
   Bus 002 Device 002: ID 03f0:1205 Hewlett-Packard ScanJet 4500C/5550C
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-generic.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3396 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'nForce'/'NVidia nForce with ALC650E at irq 20'
   Mixer name : 'Realtek ALC650E'
   Components : 'AC97a:414c4722'
   Controls : 50
   Simple ctrls : 33
CasperVersion: 1.315.1
DistroRelease: Ubuntu 12.04
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
LiveMediaBuild: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1)
Lsusb:
 Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Transcend JetFlash Flash Drive
 Bus 002 Device 002: ID 03f0:1205 Hewlett-Packard ScanJet 4500C/5550C
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System Manufacturer System Name
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-29-generic N/A
 linux-backports-modules-3.8.0-29-generic N/A
 linux-firmware 1.79.6
RfKill:

Tags: precise running-unity
Uname: Linux 3.8.0-29-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/26/2004
dmi.bios.vendor: Award Software, Inc.
dmi.bios.version: ASUS A7N266-VM ACPI BIOS Rev 1008 beta 002
dmi.board.name: A7N266VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: REV 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 7
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSA7N266-VMACPIBIOSRev1008beta002:bd07/26/2004:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA7N266VM:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion:
dmi.product.name: System Name
dmi.product.version: System Version
dmi.sys.vendor: System Manufacturer

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1184165/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[papukaija (papukaija)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1184165

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc3-saucy/

[Janos G. Komaromi (jankom)]

Commenting on Brad Figg

tried "apport-collect 1184165"
  wanted me to "sudo apt-get install python-apport"

which I did, and then ran "apport-collect 1184165" again
   error: "ERROR: The launchpadlib Python module is not installed. This functionality is not available."

so I'll change status "Confirmed"

Janos

[Janos G. Komaromi (jankom)]

Re Joseph:

Installed 3.8.13 kernel and same problem.

Upstream kernel tested, same bug.

Thank you both (Brad and Joseph(

Janos

[Janos G. Komaromi (jankom)]

New idea regarding why scanner does not work:

It may not have anything to do with kernel. Just a thought:

I tried to access cups through its built-in web interface (http://localhost:631), and it is not accessible in 13.04. If I go to my 12.04 installation (same machine, same hard drive, different boot) http://localhost:631 comes up without any problem. As I mentioned before, the scanner works on 12.04 and it does not work on 13.04.

So my thinking is that 13.04 has some sort of security installed which is not on 12.04. The security prevents accessing ports on "localhost" (127.0.0.1). Even though the scanner is connected to the usb interface "sane" accesses it though the network as 127.0.1:6566.

The reason I came to this idea is because (1) tried cups on 127.0.0.1:631, and (2) my custom print driver was prevented from executing by apparmor. So I put these two things together and concluded that ubuntu (or debian) has some sort of protection scheme preventing idiots like me to mess up the system. I have been playing with linux long enough to be dangerous. Unfortunately, I'm new to ubuntu and therefore do not know the internal workings of it.

CONCLUSION: Normally scanner works through "saned", and the "xinetd" settings would allow it to use port 63566 on localhost. I do not see "xinetd" in ubuntu. What replaces its functionality? Apparently, the BUG is in the implementation of the alternate method and related other security schemes (apparmor??).

Thank you for your understanding and help,

Janos

[Janos G. Komaromi (jankom)]

Christopher: I'm away from home till mid-September. Will execute commands you suggested when I come back, and report on results. Thanks for picking up the ball - Janos

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

Christopher: I'm back and executed commands as per your instructions (broke-up the && sections to make sure I don't confuse the computer and myself).

Everything went well, I suppose, but there are two isuues I cannot explain - see attached file also.

(1) a warning window popped uo saying I'm not using official ubuntu kernel. This was a virgin installation and regularly updated. I did not mess with kernel (not on this installation; I do compile my own kernel for my FC3 original installation on a different partition, where both the scanner and lexmark printer do work).

I copied the warning message to the attached file, top section. So how come I'm not using an official kernel?

(2) see copy of terminal window output in attached file, below the xxxx separator. Is this relevant to the bug?

Thank you and all others who read this and try with me to solve this problem.

Janos

[Janos G. Komaromi (jankom)]

Christopher, sorry, how can I get an "Ubuntu reporsitory kernel"?

This was a virgin installation from an Ubuntu downloaded DVD. I have not touched anything, just let itself update. Did the installation DVD not install the "Ubuntu repository kernel"? Is this a bug of the installation DVD?

Here is the output of uname:

janos@Andraslinux:~$ uname -a
Linux Andraslinux 3.8.13-030813-generic #201305111843 SMP Sat May 11 22:52:24 UTC 2013 i686 athlon i686 GNU/Linux

At any rate, please help me to obtain an "Ubuntu repository kernel".

[penalvch (penalvch)]

Janos G. Komaromi, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Janos G. Komaromi (jankom)]

Christopher M. Penalver, OK, we are getting somewhere.

Before I do anything, please humor me, and allow me to understand what exactly I'm supposed to do. Let's go step by step.

(One) - should I download the ISO image from link http://cdimage.ubuntu.com/daily-live/current/ and create a virgin installation? I can do that, I have plenty of hard disk place. Please, confirm this step ONE. After that we can go to my understanding of the next step.

I'm more than happy to participate in this work. I do have the time and interest.

Janos

[penalvch (penalvch)]

Janos G. Komaromi, a live environment, or fresh installation fully updated (no PPAs, third party add-ons, etc.) would be fine.

[Janos G. Komaromi (jankom)]

Christopher M. Penalver, problem!

I clicked on the link. It took me to a site to download images. I chose the 13.10 Desktop Image, PC (Intel x86).

Created DVD from ISO image and rebooted to the DVD.

It did not give me a chance to test it as live DVD, so I went ahead and chose "comtinue", but without checking "install 3rd party software" as instructed by you.

Minor issue: explanations under choices were not readeable, just blank squares in place of characters. Apparently the display driver could not render the font.

Created new secondary partition but without separate /boot partition and proceeded with installation.

Minor issue: I got confused by "Ubuntu One" (what is it, why email, what register?), but went ahead as a good soldier.

Instalaltion proceeded, but got stuck at the end: "copying installation logs..."

I finally gave up and pulled the plug.

When I rebooted grub was messed up, lost entry for my trusted old FC3 installation on the other hard disk. But I hope I can fix that.

Booted into 13.10, but to a completely unfamiliar desktop and an extremely slow system. Finally I found the way to shut down the system normally, without pulling the plug.

After that I rebooted into 13.04 whose grub entry was not lost. Now I can write this report.

So we are still at STEP ONE.

Can you please help?

btw, what is PPA?

[Janos G. Komaromi (jankom)]

Christopher M. Penalver, problem update, a day later:

(a) I was able to get back to the boot capability to boot into my trusted old FC3 installation. I had to do a "sudo update-grub" from the new installation (13.10). The only way I could do it by Ctr-Alt-F1 switching into terminal. The gui desktop was useless. Apparently the aborted installation changed but not finished MBR. Grub now looks at the new installation. When I did the sudo grub-update from the 13.04 boot it did recognize the FC3 installation, but it looks like grub from MBR now reads the cfg from the 13.10 installation. Anyway, I'm glad that at least I'm back to square one.

(b) Also, from 13.10 terminal mode I did a "uname -a", see attached. This is to tell what kernel was installed.

Let me know how to proceed, and thanks.

Janos

[penalvch (penalvch)]

Janos G. Komaromi, would you be able to boot into a live or installed environment of a prior version of Ubuntu (ex. Raring) and simply run the apport-collect?

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

Christopher M. Penalver, testing update

(1) Booted into live DVD of Raring. Same problem, scanner does not work. Apport collect did not work even after installing python - see attached file of terminal dialogue

(2) Booted into live DVD of Saucy. Could not even find simple scan or any menu. I correct my previous message, the Saucy install DVD does give the option to try it, i.e. run a live DVD environment. I just could not read it, because as I mentioned in my previous message, the explanations were not readeable, just plane character squares. This is a bug in the ISO image. Somebody selected the wrong font.

(3) I also trried to follow your instruction (quote: ...Please do not test the daily kernel folder, but the one all the way at the bottom...), and tested kernel 3.12 - see attached file. Saccer does not work.

Problems:

(A) Presently I can boot into three environments: Raring and Saucy on sda, of which Saucy is extremely slow and useless. The third environment is FC3 on sdb. The problem is that since I installed Saucy it looks like grub only looks at the Sacy environment for cfg file. Can you please tell me how to get rid of Saucy and make sure grub reads the Raring cfg file at boot?

(B) After I installed kernel 3.12 for testing my Raring environment has an error indicator on the update gizmo on top of the right hand corner of my screen telling me to run the Package Manager from the right click menu. The right click menu of that gizmo (sorry, I don't know the official name panel? aplet? etc.) only gives me choices of More or Remove. So can you please help me how to fix this condition.

Please, understand that I'm new to Ubuntu and am not familiar with Ubuntu lingo, shortcuts, etc.

One final note: are you sure it is a kernel problem that scanner does not work? Please, read my first message on top of this thread. lsusb recognizes the scanner, sane-find-scanner finds it, but scanimage cannot access it because it is "busy".

[Janos G. Komaromi (jankom)]

Christopher M. Penalver, - attachment #2
apparently I can only attach one file, so here is the other one referenced in my previous message, testing item (3)

[penalvch (penalvch)]

Janos G. Komaromi, following up on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/comments/19 , would you be able to boot into a live or installed environment of a prior version of Ubuntu (ex. Raring), boot into a Ubuntu kernel (not a mainline/upstream one) and simply run the apport-collect?

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

Christopher M. Penalver, Sorry, I'm confused again. I thought comments 20 and 21 answered comment 19.

As far as comment 23: i'm booted now, and all the time for this bug report, into my 13.04 (or Raring) installation. So I have run aggain the apport command, see attached file of the screen dialogue. You'll notice that I ran it both ways, with -p linux and without. I don't quite understand the errors, but it's OK.

Again, what do you mean by "boot into a Ubuntu kernel (not a mainline/upstream one)"? How do I do that? Where do I get an "Ubuntu kernel"? See comment 17.

I'm sorry, I'm not trying to be difficult.

Janos

[penalvch (penalvch)]

Janos G. Komaromi, could you please boot into a Precise live environment, and then run the apport-collect?

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

Christopher M. Penalver, I'm in live DVD (did not fit on CD) boot ("try Ubuntu"). Looks good, if you allow me the opinion, it is much better than the other version I tried, see comments #17 and #21.

Scanner does work, but I think I stated that in my initial bug report.

I was not sure exactly what you wanted, so I ran apport-collect three ways. See attached file of terminal window transcript.

Hope this helps.

Janos

[penalvch (penalvch)]

Janos G. Komaromi, the next step is to bisect this issue between Precise and Raring, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Janos G. Komaromi (jankom)]

Christopher M. Penalver, thank you. I'll do that. Give me some time to study the article and get down to work. This will be my first bisection. Will keep you posted if any problem.

[Janos G. Komaromi (jankom)]

Christopher M. Penalver, I think we have a major confusion here, and it is mainly my fault. This is due to my lack of experience with Ubuntu community and with bug reporting.

The bug I reported is for Xubuntu, not for Ubuntu. "X" is the key word here.

When I studied the bisect notes and my previous tests I found out that

Precise (a.k.a. 12.04) kernel for Ununtu on live CD (or DVD) is 3.8.0-29
but for xubuntu it is 3.2.0-52

Scanner works on both live CD.

Raring (a.k.a. 13.04) kernel for xubuntu is 3.8.0-19, and scanner is not recognized, i.e. this bug.

Both Ubuntu and Xubuntu CDs have kernels marked "generic".

It looks like Xubuntu uses different kernels than Ubuntu. Why is that? Why should desktop user spoace software affect kernel? But these questions are only due to my "ask stupid questions" mentality.

As far as bisecting is concerned, I don't know where to find the relevant Xubuntu kernel releases. The bisecting instructions refer only to Ubuntu releases, not to Xubuntu. It looks like Xubuntu is an .org and Ubuntu is a .com. Am I in the wrong place reporting the bug?

The bottom line is: I need more help and directions how to proceed.

Thanks,

Janos

[penalvch (penalvch)]

Janos, the fact you are using Xubuntu doesn't change anything regarding bisections. The reason Ubuntu Precise and Xubuntu Precise differ in kernel versions is b/c the Ubuntu Kernel Team decided to backport the Quantal enablement stack to Ubuntu Precise. Hence, as documented in https://wiki.ubuntu.com/Kernel/KernelBisection , if one is looking to bisect Ubuntu (or Xubuntu) kernel version for Precise, they would go to https://launchpad.net/ubuntu/precise/+source/linux and do this.

[Janos G. Komaromi (jankom)]

Christopher, ok. I start to see the logic. However, I fail to understand why kernel 3.2 works on Xubuntu, but 3.8.0-19 does not, even though 3.8.0-29 works again in Ubuntu. Apparently something went bad going from 3.2.0-52 to 3.8.0-19 in Xubuntu, but going from 3.8.0-19 to 3.8.0-29 things became good again (I mean scanner recognition in Xubuntu).

So before I bisect anything would you agree that I should first install 3.8.0-29 on my Xubuntu, and test the scanner. If it works then we can decide if we need to bisect 3.8.0-19 and -29 if we really want to find out what is the offending code.

Let me know.

[penalvch (penalvch)]

Janos G. Komaromi, placing a hold on the bisect for now, could you please test for this in Saucy Xubuntu via http://cdimage.ubuntu.com/xubuntu/releases/saucy/beta-2/ and advise if this is reproducible?

[Janos G. Komaromi (jankom)]

Christopher: yes, reproducible. Installation DVD is fine, no problem with fonts . I did a live DVD test, and scanner is not recognized. Looks like kernel is 3.11.0-8.

Just to recap: Ubuntu or Xubuntu in Precise version do recognize scanner. Ubuntu Precise kernel is 3.8.0-29 amd Xubuntu Precise kernel is 3.2.0-52. They both work with my scanner.

[Janos G. Komaromi (jankom)]

Christopher, OK. Forgive me for a stupid question: bisect what? If it is the kernel that to blame, and if kervel versions are sequential, how come 3.2 0-52 works, 3.8.0-19 does not, then 3.8.0-29 works again, then 3.11.0-8 does not? What does Precise, Raring or Saucy has to do with kernel working or not? My understanding is that the various flavors (Precis, Saucy, Raring) have different features and packaging, supposedly better user experience, but they are built around some kernels, such as 3.2, 3.8 or 3.11. I would like to fully understand what I'm doing before starting.

Please, understand that I'm not trying to be difficult, but I'm confused about the fact that one kernel works, the next doesn't, the next works again, and so on. So should I simply bysect kernels in Xubuntu Precise and Raring? Raring already does not work, so why go to Saucy? Please, explain.

Maybe I totally miss the point. I studied the "bysect" link you sent me and this is why I have these questions.

Thanks, Janos

[penalvch (penalvch)]

Janos G. Komaromi, you are experiencing a not too uncommon regression-fix-regression phenomenon. It would be best to bisect the newest bisection point (3.8.0.29 works, 3.11.0-8 doesn't).

[Janos G. Komaromi (jankom)]

Christopher, OK. I'll start working on it.

[Janos G. Komaromi (jankom)]

Christopher, here is another question before I start digging into it. I would like to try 3.8.0-29 on my installed xubuntu. Yes, it worked on Ubuntu (not xubuntu) live CD, but just to make sure it is the kernel and not the distro around it I would like to test this idea.

Specifically, how can I simply download and activate kernel 3.8.0-29? The "Ubuntu Software Center" application does not have such a choice.

Thanks,

Janos

[Janos G. Komaromi (jankom)]

Christopher, one more thing: I have installed the same 13.04 xubuntu (Raring) on my Acer 64 bit laptop, using a USB stick as the root filesystem. When I connect the laptop to the same scanner it works. I checked the kernel and it is 3.8.0.31.

Well, this is a mystery, since my PC on which the scanner does not work is fully updated and yet the kernel is 3.8.0-19, as previously noted in this bug comment thread. So how come it was not updated to .31?

OK, let that be a separate problem.

So I was encouraged and wiped out my installation on the PC, repartitionad the hard drive and installed again 13.04 using the same DVD as I used before or used for the laptop. Installation. This new virgin installation, went well, and updated itself completely. Checked kernel, now it is the same as on laptop, that is .31.

Fine, so I tried to scan, and it is the same problem, scanner not recognized.

I guess, this test suggest that the problem is with kernel configuration. Apparently, because of the two different hardwares (laptop and my PC) some of the modules are not included in the kernel configuration. My Acer laptop can run the scanner without those modules, but my PC cannot.

This, to me, makes it even more important to test .29 kernel on my PC which worked on Ubuntu live CD (not xubuntu). If I have to bisect I would only have to bisect between 29 and 31. Better yet, if I can run a diff between 29 and 31 kernel configurations I may be able to discover what is the problem with accessing the scanner.

Summary:

I still need to know how to load .29 kernel in my xubuntu so that I can test it before further research or bisect.

Thank you or anybody else reading this.

Janos

[Janos G. Komaromi (jankom)]

New information from Janos

I did a diff on kernel configurations between 3.8.0-29 and -31 and found minimal, non-essential differences. Scanner works on -29 in ubuntu environment, but does not work on -31 in xubuntu environment. Scanner also works on different hardware (my Acer laptop) even on -31 xubuntu.

My conclusion is that scanner problem is not related to kernel but to distribution itself (xubuntu going from 12.04 to 13.04). I suggest to go back to my initial report where sane finds the scanner, but scanimage thinks it is busy.

I'm ready to give up on this bug.

xubuntu is a good compliment to my linux experience. I can continue to play with my old, hacked and mangled FC3 installation where the scanner works and my color lexmark printer also works. On the other hand, xubuntu could make my new HP P 1102W printer work that I was unable to accomplish so far in FC3. But xubuntu cannot make the lexmark printer and the scanner work. That's OK, I'll use both linux installations, depending on what I need.

[penalvch (penalvch)]

Janos G. Komaromi, remaining focused on the hardware you originally reported this against (Asus A7N266VM), you may find the desired kernels to bisect via:
https://launchpad.net/ubuntu/raring/+source/linux

[Janos G. Komaromi (jankom)]

Christopher M. Penalver, I'm again away from home till early February, so I do not have access to the home desktop coputer with Asus mother board. If it helps Ubuntu developers I'm willing to do the bisect project using the link you provided. Nevertheless, I would like to know and understand the following:

(1) If the kernel configuration is the same for a kernel that scanner works and for another kernel that the scanner does not work what is the point of bisecting kernels? Please, explain.

(2) Apparently the kernel recognizes the scanner devices, but something takes it over and causes it to report as being busy. Shouldn't we direct our investigation towards that?

Note: before I left home I wiped out the hard drive again (you know, the dd stuff) and installed 12.04 flawlessly. Everything works on the Asus computer, and I do not have 13.04 installation anymore. But again, if it helps I can create an install and do the bisect.

Also, I installed 12.04 on my Acer laptop, abandoned my W7 boot and use only my Xubuntu on it, completely happy. I'm writing this on my Acer laptop, from Xubuntu 12.04.

Janos

[penalvch (penalvch)]

Janos G. Komaromi, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/comments/62 :
>"1) If the kernel configuration is the same for a kernel that scanner works and for another kernel that the scanner does not work what is the point of bisecting kernels? Please, explain."

This question doesn't make any sense. At this time, this report is focused on the kernel version you are testing when it does and doesn't work, only for the hardware you originally reported against, not anything else. Bisection will allow a developer to know precisely what commit caused the problem. Then it can be best judged if reverting the commit, or improving upon it is the best way to go. Unless this is done, at best, it is onerous to address this issue.

>"(2) Apparently the kernel recognizes the scanner devices, but something takes it over and causes it to report as being busy. Shouldn't we direct our investigation towards that?"

That's what a bisection is, an investigation directed at exactly that.

>"Also, I installed 12.04 on my Acer laptop, abandoned my W7 boot and use only my Xubuntu on it, completely happy." If you are happy to use Precise, as it's EOL date is after Raring and Saucy, you are welcome to mark the Status Invalid.

[Janos G. Komaromi (jankom)]

Christopher M. Penalver, sorry for not expressing myself clearly: what I meant is that if two kernel versions have the same configurations then I would expect that they would work the same way. But maybe that is not the case. What made me suspicious is that a kernel version did work, then a later version did not, and yet an even later version worked again. I guess, everything is possible, so it would still make sense to do a bisect.

Nevertheless, the execise would be academic, since 12.04 works well on the ASUS desktop as well, including scanner. So even if there were some obscure kernel reason for the 13.04 scanner busy malfunction it would not be an improvement benefitting the entire Ubuntu community. Therefore I'll mark this bug as Status Invalid.

Again, thank you for your attention to this matter.

Janos