[jaunty] lpia alternate install does not install linux-lpia

Bug #359174 reported by Brandon Williams
8
Affects Status Importance Assigned to Milestone
base-installer (Ubuntu)
Fix Released
High
Colin Watson
Jaunty
Fix Released
High
Colin Watson

Bug Description

Binary package hint: debian-installer

Yesterday (April 4, 2009), I installed Jaunty to my dell mini 910 from a USB stick using the latest alternate install ISO found here http://cdimage.ubuntu.com/ports/daily/current/.

I put the install media on the USB stick using usb-creator, booted into the installer, and followed the prompts. The installation appeared to complete without any errors.

Upon reboot, I discovered that the linux-lpia meta package had not been installed, only linux-image-lpia. As a result, linux-restricted-modules-lpia was not installed. Without the restricted modules, the driver for my Broadcom wireless card was not available.

I think that linux-lpia should be installed, not just linux-image-lpia.

Tags: jaunty
Revision history for this message
Brandon Williams (opensource-subakutty) wrote :

FWIW, linux-lpia and linux-restricted-modules-lpia are both present on the install media. The work-around to complete installation was to mount the USB stick on /media/cdrom0, enable the CD as a software source, and install linux-lpia.

tags: added: jaunty
Craig Huffstetler (xq)
summary: - lpia alternate install does not install linux-lpia
+ [jaunty] lpia alternate install does not install linux-lpia
Revision history for this message
JP Vossen (jp-jpsdomain) wrote :

Same for me, using 1 day newer daily...

I used the 2009-04-11 http://cdimage.ubuntu.com/ports/daily/current/jaunty-alternate-lpia.iso, "burned" to a DataTraveler 2G USB key, and everything mostly Just Worked.

I had no network (wired or wireless) during the install, but wired worked fine after reboot. I had to manually install linux-restricted-modules-lpia after which I got the new sta driver and then wireless worked (where "worked" is defined as, "at least as well as that crappy Broadcom card ever works).

I didn't know about the linux-lpia meta-package, but now that I do I agree with OP, load it...

Revision history for this message
Colin Watson (cjwatson) wrote :

Please attach /var/log/syslog so that I can see what's going on here.

affects: debian-installer (Ubuntu) → base-installer (Ubuntu)
Changed in base-installer (Ubuntu):
status: New → Incomplete
Revision history for this message
Brandon Williams (opensource-subakutty) wrote :

Are you looking for /var/log/syslog from the currently running system with linux-lpia (and the restricted modules) already installed? If not, please provide more detail about what you're looking for.

Revision history for this message
Craig Huffstetler (xq) wrote :

Brandon,

From the system (linux-lpia still) you are booting into using the Jaunty Release Candidate live media, daily build, if at all possible. This gives us more real-time information.

Craig

Revision history for this message
JP Vossen (jp-jpsdomain) wrote :

Craig, I may be especially dense today (likely), but I'm still not clear what you want.

Do you mean to boot from the USB key and copy /var/log/syslog someplace? If so, at waht stage of the boot process? I didn't use a "Live" anything, I used the daily build alternate installer, so the only choice is "install." Logs from that don't seem useful, but I guess I can do something. I also don't want to mess up my now working (great) system. I can reboot and do a dmseg, lshw, whatever if that's useful, but since I already loaded the module...

I also just ran and submitted a "System testing" report (under this same user account) if that does anything for you...

Revision history for this message
Brandon Williams (opensource-subakutty) wrote :

I went through the installation up to the partition tool, and then saved the debug logs to disk. Here are the resulting logs.

Revision history for this message
Craig Huffstetler (xq) wrote :

JP,

Sorry, I may have been unclear.

That is exactly what we what we wanted. A copy of /var/log/syslog from the USB key after boot BEFORE the restricted modules are installed AND another one AFTER.

We want to see the errors and the problems you are experiencing directly from the system's "point of view."

Brandon,

Thanks.

Revision history for this message
Brandon Williams (opensource-subakutty) wrote :

Craig,

Please let me know if you need any additional logs. The USB key is running the alternate installer, not a live ISO, so adding the restricted modules to it is not an option. However, I could get you the syslog from the running system that has the restricted modules installed if that would be helpful.

Revision history for this message
Brandon Williams (opensource-subakutty) wrote :

Here are logs from the installed system both with and without the restricted modules installed. I've also included 'lspci -nvvk' output for both cases, in case there are any important differences between the two.

Revision history for this message
Colin Watson (cjwatson) wrote :

Sorry I didn't see your questions before now. Unfortunately neither of these sets of logs actually contains what I need, and Craig is mistaken about what I'm asking for. What I actually need is the *installer* syslog. I should have been more clear, though; after a completed installation, the file I need is saved in /var/log/installer/syslog.

Revision history for this message
Colin Watson (cjwatson) wrote :

Also, since it's just one file, it would be best if you didn't tar it up - if you just attach it directly then I can see it in my web browser.

Revision history for this message
JP Vossen (jp-jpsdomain) wrote :

Sweet, never noticed that.

$ ll /var/log/installer/syslog
-rw------- 1 root root 508K 2009-04-11 16:45 /var/log/installer/syslog

You sure you want uncompressed?
$ ll syslog.gz
-rw------- 1 root root 71K 2009-04-15 21:26 syslog.gz

Revision history for this message
Brandon Williams (opensource-subakutty) wrote :

Ah-hah ... here you go. Please let me know if any of the other logs from that directory would be helpful so I can attach those, tool.

Revision history for this message
Colin Watson (cjwatson) wrote :

Thanks - I see the problem now and will fix it. I think we should fix this for Jaunty since it's an alternate vs. desktop inconsistency and results in the wrong set of packages being installed.

I don't think desktop installs are affected, since ubiquity doesn't use this bit of base-installer.

Changed in base-installer (Ubuntu Jaunty):
assignee: nobody → Colin Watson (cjwatson)
importance: Undecided → High
status: Incomplete → Fix Committed
Revision history for this message
Colin Watson (cjwatson) wrote :

JP Vossen: although I don't need it now, in general I'm going to spend less time downloading a half-megabyte file than I would messing about decompressing it :-)

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package base-installer - 1.98ubuntu7

---------------
base-installer (1.98ubuntu7) jaunty; urgency=low

  * Add linux-lpia to kernel_update_list metapackage ordering hack
    (LP: #359174).

 -- Colin Watson <email address hidden> Fri, 17 Apr 2009 12:22:12 +0100

Changed in base-installer (Ubuntu Jaunty):
status: Fix Committed → Fix Released
Revision history for this message
JP Vossen (jp-jpsdomain) wrote :

Colin: point taken. :-) Thanks for fixing this...

Revision history for this message
Brandon Williams (opensource-subakutty) wrote :

I recently reinstalled from the released lpia alternate install CD. I can now confirm that the alternate install CD can be used to install the lpia architecture build without any special tweaking to get the necessary kernel and/or modules installed.

Thanks for the fix!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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