[Lenovo b475e]: Precise 12.04.2 install fails

Bug #1125610 reported by Jeff Marcom
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
High
AceLan Kao
Precise
Fix Released
High
AceLan Kao
Quantal
Fix Released
High
AceLan Kao

Bug Description

Attempting an install of 12.04.2 precise results in a few major blocking issues.

B475e 1:
    Mainboard LB475B UMA MB SIT 11312-SB 1.0G DIP#1
    UEFI BIOS version: HPET18WW (1.03)
    UEFI BIOS Date 2012-05-29

    Problem encountered:
        Systems hangs while at Ubuntu Splash screen. Will not accept any keyboard activity
    Steps to reproduce:
       1.) Download and Install 12.04.2 to key, cd, or other boot media.
       2.) Choose "Install Ubuntu" Option

B475e 2:
    Mainboard LB475B UMA MB SIT 11312-SB 1.7G DIP#5
    UEFI BIOS version: HPET09WW (0.09)
    UEFI BIOS Date 2012-03-15

    Problem encountered:
        Systems hangs while at grub loader after installation:
        error: no suitable mode found
        error: no video mode available

        Also, to control boot menu options an external usb keyboard must be used. Cannot use onboard keyboard.
    Steps to reproduce:
       1.) Download and Install 12.04.2 to key, cd, or other boot media.
       2.) Choose "Install Ubuntu" Option
       3.) Go through installation process
       4.) Remove media
       5.) Reboot

These machines do not present a problem installing 12.04.1
       6.) Wait for machine to attempt to boot from HD.

Jeff Marcom (jeffmarcom)
tags: added: blocks-hwcert
tags: added: blocks-hwcert-enablement
tags: added: lexington-lab
tags: added: 201204-10857 201204-10862
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 1125610

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.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: precise
Revision history for this message
Jeff Marcom (jeffmarcom) wrote :

Setting this back to new, I can't get logs for this mister bot!

Changed in linux (Ubuntu):
status: Incomplete → New
tags: added: regression-release
Revision history for this message
Brad Figg (brad-figg) wrote :

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

apport-collect 1125610

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Do you happen to know if any newer versions of Ubuntu install on this same system?

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: bot-stop-nagging kernel-da-key
Changed in linux (Ubuntu Precise):
status: New → Incomplete
importance: Undecided → High
Revision history for this message
Jeff Marcom (jeffmarcom) wrote :

Trying quantal on the same set of systems fail in the exact same manner.

Changed in linux (Ubuntu):
status: Incomplete → New
Changed in linux (Ubuntu Precise):
status: Incomplete → New
Revision history for this message
Brad Figg (brad-figg) wrote :

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

apport-collect 1125610

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu Precise):
status: New → Incomplete
Revision history for this message
Jeff Marcom (jeffmarcom) wrote :

The failures do not occur in raring.

Changed in linux (Ubuntu):
status: Incomplete → New
Changed in linux (Ubuntu Precise):
status: Incomplete → New
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

One additional question, does this only happen when booting in UEFI mode? Does it also happen if you boot with normal BIOS mode?

tags: added: kernel-fixed-upstream
Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu Precise):
status: New → Confirmed
Changed in linux (Ubuntu Quantal):
status: New → Confirmed
Revision history for this message
Jeff Marcom (jeffmarcom) wrote :

I tried setting it to only boot legacy (default was UEFI) and machine #1 saw the same issue where it hangs at the Ubuntu splash screen, machine #2 hung after selecting option "Install Ubuntu" from the live iso.

Changed in linux (Ubuntu Quantal):
importance: Undecided → High
Revision history for this message
James M. Leddy (jm-leddy) wrote :

Sounds like a regression with the graphics driver. We have to figure out if it's loading the fglrx or radeon drivers by default. From there we can proceed to figure out what went wrong.

Interestingly, the pre-install project for these machines disable updating of the driver. I suppose they found too many regressions:

Package: disable-jockey-fglrx
Priority: extra
Section: admin
Installed-Size: 29
Maintainer: James Ferguson <email address hidden>
Architecture: amd64
Version: 1.2
Filename: pool/public/d/disable-jockey-fglrx/disable-jockey-fglrx_1.2_amd64.deb
Size: 3372
SHA256: 50aa60fcc3f9716331d28885b176a6453e9a09d3f0fc3da6342bb1ae2756e426
SHA1: 0f003bd70b6466e0a26b6c62e78ab71f3ac36e6d
MD5sum: 5977f04d45c6339d54d1ccae2aaca5e3
Description: Prevents loading of invalid fglrx drivers
 This package prevents Jockey (the "Additional Drivers" app) from
 suggesting the load of invalid versions of the fglrx (AMD/ATI
 graphics driver) package. Removal of this package may allow Jockey
 to replace a working driver with an invalid one.
Modaliases: hwe(pci:v00001002d*sv*sd*bc03sc*i*)

Changed in linux (Ubuntu):
assignee: nobody → AceLan Kao (acelankao)
Changed in linux (Ubuntu Precise):
assignee: nobody → AceLan Kao (acelankao)
Changed in linux (Ubuntu Quantal):
assignee: nobody → AceLan Kao (acelankao)
Revision history for this message
Yang Kun (YK) (dayangkuncn) wrote :

@AceLan, do you have any update ?

Revision history for this message
AceLan Kao (acelankao) wrote :

Since I don't have this machine and you can't provide more log on this issue,
could you try to pass those kernel command while booting up
   acpi=off pci=noacpi noapic nolapic

Changed in linux (Ubuntu Precise):
status: Confirmed → Incomplete
Changed in linux (Ubuntu Quantal):
status: Confirmed → Incomplete
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jeff Marcom (jeffmarcom) wrote :

that seemed to have worked an let me install and boot 12.04.2 successfully.

Changed in linux (Ubuntu):
status: Incomplete → New
Changed in linux (Ubuntu Precise):
status: Incomplete → New
Changed in linux (Ubuntu Quantal):
status: Incomplete → New
Revision history for this message
Jeff Marcom (jeffmarcom) wrote :

Problem is intermittent, sometimes I can boot from live media, other times there is no keyboard input to select "Install Ubuntu" or "Try Ubuntu without installing" from the menu.

Revision history for this message
Brad Figg (brad-figg) wrote :

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

apport-collect 1125610

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu Precise):
status: New → Incomplete
Changed in linux (Ubuntu Quantal):
status: New → Incomplete
Jeff Marcom (jeffmarcom)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu Precise):
status: Incomplete → Confirmed
Changed in linux (Ubuntu Quantal):
status: Incomplete → Confirmed
Revision history for this message
Yang Kun (YK) (dayangkuncn) wrote :

cert team confirmed the hardware is currently with Alberto.

AceLan Kao (acelankao)
Changed in linux (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
AceLan Kao (acelankao) wrote :

Using 12.04.3 to install and boot up the system, it works well.
It will use radeon driver and runs unity 3d without any problems.

So, I think the problem had been fixed by 12.04.3

Changed in linux (Ubuntu):
status: In Progress → Fix Released
Changed in linux (Ubuntu Precise):
status: Confirmed → Fix Released
Changed in linux (Ubuntu Quantal):
status: Confirmed → Fix Released
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.