Ubuntu
linux-source-2.6.22 package

Find errors while installing linux-image-2.6.22-14-server package

Bug #153743 reported by Marc Tardif
6
Affects Status Importance Assigned to Milestone
initramfs-tools (Ubuntu)
Fix Released
Low
Amit Kucheria
Hardy
Fix Released
Low
Amit Kucheria
linux-source-2.6.22 (Ubuntu)
Invalid
Medium
Unassigned
Hardy
Invalid
Medium
Unassigned

Bug Description

When installing the linux-image-2.6.22-14-server package on a desktop installation, I get several errors from the find command about /lib/firmware/2.6.22-14/firmware: No such file or directory. I have attached the complete output of the apt-get command below.

Tags: hwct
Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Marc,

I've tagged this as 'hardy-kernel-candidate' so that it is retargetted toward the upcoming Hardy kernel release. Thanks!

Changed in linux-source-2.6.22:
importance: Undecided → Medium
milestone: none → hardy-alpha-1
status: New → Triaged
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Confirming issue still exists for linux-image-2.6.24-1-server

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Triaged
Steve Langasek (vorlon)
Changed in linux-source-2.6.22:
milestone: hardy-alpha-1 → none
Revision history for this message
Jackdaw28 (simoncsoka) wrote :

Hi Leann,
This was the cause of my netgear wg511 not working: https://bugs.launchpad.net/ubuntu/+bug/152477
I just manually created the directory /lib/firmware/2.6.24-1-generic and copied the firmware file over from 2.6.22. This fixed the wireless problem for me.

Revision history for this message
Ben Collins (ben-collins) wrote :

Jackdaw28: This bug is not the cause of your netgear not working. This isn't really a bug, other than it produces annoying output. However, you would have your firmware installed if you installed the other packages needed (either linux-ubuntu-modules or linux-restricted-modules).

Lowering priority of this bug report, since it is mainly superficial. Also, retargeting to initramfs-tools, since that's where the errors are being produced (during update-initramfs call).

Changed in linux:
assignee: ubuntu-kernel-team → amitk
importance: Medium → Low
Changed in linux-source-2.6.22:
status: Triaged → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package initramfs-tools - 0.85eubuntu35

---------------
initramfs-tools (0.85eubuntu35) hardy; urgency=low

  * hook-functions: Do not display find error messages if firmware directories
    cannot be found. (LP: #153743)
  * scripts/functions: Remove unneeded quotes. These were causing multiple
    mountroot fail hook entries to be run as one command.
  * scripts/local: Panic if the root device node cannot be found, or vol_id
    can't identify the volume on the device. This allows mdadm's mountroot fail
    hook to be reliably triggered, as the md device node exists even if the
    array cannot be brought up.
  * init: Add 2>&1 to the run-init line at the end of the file, to fix a long
    outstanding bug where init has no stderr.
  * scripts/local-premount/resume: Source /scripts/functions, thanks to
    Nikolaus Filus for the patch. (LP: #203429)

 -- Luke Yelavich <email address hidden> Thu, 10 Apr 2008 00:48:51 +1000

Changed in initramfs-tools:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.