kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1184165

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

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions