Docked laptop loses parallel port (Gusty - Not a hardware failure)

Bug #160746 reported by zeddock on 2007-11-07
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

Dell D800 laptop.
Clean CD Gusty 7.10 release installed
***Unsure if this has been problem in past as only tested parallel port with this printer under XP Pro OS. Did not try it under Feisty, either.
Checked BIOS to find current setting is for "Normal". Have tried different settings like ECP, etc. No change.

While undocked a parallel printer can be configured and used as expected.
Once docked the port does not seem to exist.

===
:~$ ls /dev/l*
/dev/log /dev/loop0
===
~$ lsmod | grep lp
lp 12580 0
parport 37448 3 ppdev,lp,parport_pc
===
(Removed ip addresses. Replaced with x's below.)
$ lpinfo -l -v
Device: uri = socket
        class = network
        info = AppSocket/HP JetDirect
        make-and-model = Unknown
        device-id =
Device: uri = beh
        class = network
        info = Backend Error Handler
        make-and-model = Unknown
        device-id =
Device: uri = hpfax
        class = direct
        info = HP Fax (HPLIP)
        make-and-model = Unknown
        device-id =
Device: uri = socket://xxx.xxx.xxx.xxx
        class = network
        info = HP LaserJet 2200 xxx.xxx.xxx.xxx
        make-and-model = HP LaserJet 2200
        device-id =
Device: uri = socket://xxx.xxx.xxx.xxx
        class = network
        info = HP LaserJet 4000 Series xxx.xxx.xxx.xxx
        make-and-model = HP LaserJet 4000 Series
        device-id =
Device: uri = socket://xxx.xxx.xxx.xxx
        class = network
        info = hp LaserJet 4300 xxx.xxx.xxx.xxx
        make-and-model = hp LaserJet 4300
        device-id =
Device: uri = socket://xxx.xxx.xxx.xxx
        class = network
        info = HP LaserJet 5000 Series xxx.xxx.xxx.xxx
        make-and-model = HP LaserJet 5000 Series
        device-id =
Device: uri = socket://xxx.xxx.xxx.xxx
        class = network
        info = HP LaserJet 5000 Series xxx.xxx.xxx.xxx
        make-and-model = HP LaserJet 5000 Series
        device-id =
Device: uri = hp
        class = direct
        info = HP Printer (HPLIP)
        make-and-model = Unknown
        device-id =
Device: uri = http
        class = network
        info = Internet Printing Protocol (http)
        make-and-model = Unknown
        device-id =
Device: uri = ipp
        class = network
        info = Internet Printing Protocol (ipp)
        make-and-model = Unknown
        device-id =
Device: uri = lpd
        class = network
        info = LPD/LPR Host or Printer
        make-and-model = Unknown
        device-id =
Device: uri = cups-pdf:/
        class = file
        info = Print into PDF file
        make-and-model = Generic PDF file generator
        device-id = MFG:Generic;MDL:PDF file generator;DES:Generic PDF file generator;CLS:PRINTER;CMD:POSTSCRIPT;
Device: uri = scsi
        class = direct
        info = SCSI Printer
        make-and-model = Unknown
        device-id =
Device: uri = smb
        class = network
        info = Windows Printer via SAMBA
        make-and-model = Unknown
        device-id =
Device: uri = socket://xxx.xxx.xxx.xxx
        class = network
        info = Xerox WorkCentre 5030 128.183.81.98
        make-and-model = Xerox WorkCentre 5030
        device-id =
Device: uri = socket://xxx.xxx.xxx.xxx
        class = network
        info = Xerox WorkCentre 5030 128.183.81.250
        make-and-model = Xerox WorkCentre 5030
        device-id =
===

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 cupsys. The following wiki will also help: https://wiki.ubuntu.com/DebuggingPrintingProblems . Please attach the additional infomation outlined under the 'Parallel port printer' section. Thanks!

Till Kamppeter (till-kamppeter) wrote :

This is not a CUPS problem but a kernel issue, as the /dev/lp* devices disappear, too, not only the entry in "lpinfo -v". Moving to the kernel ...

Changed in linux:
assignee: nobody → ubuntu-kernel-team

Thank you all for moving this forward.

zeddock

On Dec 6, 2007 8:28 AM, Till Kamppeter <email address hidden> wrote:

> This is not a CUPS problem but a kernel issue, as the /dev/lp* devices
> disappear, too, not only the entry in "lpinfo -v". Moving to the kernel
> ...
>
> ** Changed in: linux-meta (Ubuntu)
> Sourcepackagename: cupsys => linux-meta
>
> ** Changed in: linux (Ubuntu)
> Sourcepackagename: linux-meta => linux
>
> ** Changed in: linux (Ubuntu)
> Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
>
> --
> Docked laptop loses parallel port (Gusty - Not a hardware failure)
> https://bugs.launchpad.net/bugs/160746
> You received this bug notification because you are a direct subscriber
> of the bug.
>

The Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2 which is set to come out around Dec 20. However, here are the instructions to install if you choose to do so, otherwise just wait for Alpha2 to come out:

1) edit the file /etc/apt/sources.list and add the following line:

deb http://archive.ubuntu.com/ubuntu hardy main restricted

2) sudo apt-get update
3) sudo apt-get install linux-image-2.6.24-1-generic
4) reboot and select the new kernel from the grub menu

After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance!

Changed in linux:
status: New → Incomplete
Nick Ellery (nick.ellery) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
assignee: ubuntu-kernel-team → nobody
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers