Ubuntu doesn't work on HP Elitebook 8560w

Bug #864739 reported by Simon
120
This bug affects 18 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Well, the headline says it all - have been trying for the last couple of days to get Ubuntu running on my new HP Elitebook 8560w (core i7, nVidia Quadro 1000m).
I tried
- several USB sticks
- a SD card
- a CD
- 11.04
- 11.10
- 10.10
- SATA modes AHCI and IDE
- "fan always on while on A/C power" in the BIOS (read somewhere that that might cause an error)
in several combinations... none of this worked.

I know that at laptops with two graphics cards (e.g. i7 / nVidia Quadro) you have to disable the switchable graphics. However, from what I read the Elitebook always uses the nVidia, and there is no BIOS switch for that, so I can't try and solve the problem that way.

Sometimes (using the USB stick) I got to a kind of "messed-up" menu (the "try linux", "install linux" and so on, but very weird looking); using the CD, I got the normal pink background without any menu.
Either way, the boot process failed; using the USB-sticks, it just froze saying "sdb: attached SCSI removable disk" or something about "USB HID interface" (though only once, I think). The same thing happened booting from the CD when any USB device was attached; after I removed them all I get "/sbin/modprobe pci -bv -long number- unexpected exit with status 0x0009".

So, no matter what I do, I can't even get the Live CD running...
Tried the CD on another Laptop, btw (Acer Aspire 5810TG); got the same errors at first, but playing around in the BIOS a little solved the problem eventually... so the CD/USB stick should be alright.

tsg1zzn (tsg1zzn)
affects: ubuntu → linux (Ubuntu)
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 864739

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
Simon (simon-baar) wrote :

Can't get Linux to run, so I can't create any log files...
bug still persists.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
aquCHAOS (aquchaos) wrote :

Same issue on my HP 8560w. Hoping there is a good solution. Thanks!

Revision history for this message
Simon (simon-baar) wrote :

Bug is still there with Ubuntu 11.10.... also, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/870071, I would guess that's the same one?

Revision history for this message
Jordan Weaver (i-jordanweaver) wrote :

I am having the same issue on my HP 8560w. I always get to the same point once I boot into the USB drive. If I don't make a selection soon, it just jumps right into it and then stalls on the same part mentioned above. Even if I do make a point to select the Run from USB option I always get to the same stalling point:

....
sd 6:0:0:0: [sdb] Write Protect is off
sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
sd 6:0:0:0: [sdb] No Caching mode page present
sd 6:0:0:0: [sdb] Assuming drive cache: write through
sd 6:0:0:0: [sdb] No Caching mode page present
sd 6:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1
sd 6:0:0:0: [sdb] No Caching mode page present
sd 6:0:0:0: [sdb] Assuming drive cache: write through
sd 6:0:0:0: [sdb] Attached SCSI removable disk
(blinking cursor hang)

I've tried it with and without the "Fan Always On..." setting and it makes no difference. Any help? I'm trying to get this into a dual-boot system because my office requires me to use XP at work (bleh) and I want to have something interesting to use at home. XP can't even make use of all the great hardware that comes with this laptop.

Revision history for this message
Simon (simon-baar) wrote :

Precisely the error I get; only difference w/11.10 is that it says "Attached SCSI disk", without the removable.

This is starting to get annoying... I mean, Win7 is nice and all, but this Laptop is supposedly certified for SuSe 11, so I think it's kind of poor that Ubuntu doesn't run on it.

Revision history for this message
jgu (jens-guenther) wrote :

Here's the same, try to install 11.10 on HP 8560w. Configures usb & sata and then hangs.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the release candidate kernel versus the daily build. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Actually, I don't think you will be able to try the mainline kernel since you can't get Ubuntu installed at all. Are you able to install any version of Ubuntu on the system?

tags: added: maverick natty oneiric
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.0.0-12.20)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.20
Revision history for this message
rsc (rsc-x) wrote :

I had the same issue. However I was able to start the live-cd/usb by adding the following grub boot parameter (using F6):
nouveau.modeset=0

After that I was able to install Ubuntu 11.10, and the installed kernel boots without problem. However I did select to upgrade during installation, so maybe the installed kernel version is newer than the one of the live-cd.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
jgu (jens-guenther) wrote :

THX rsc! Your tip did it for me!

Revision history for this message
Simon (simon-baar) wrote :

Yep, same here... nomodeset for booting the live CD, no problems after installation w/updates...

Seems like everything is working now! (Except for the touchpad on/off button...)

Still a quite annoying bug for people who don't know about the workaround...

Revision history for this message
Kenrick Bingham (loxo) wrote :

Works for me, too. Thank you, rsc!

I agree: it would be good to get this machine booting out of the box.

I also tried 10.04 LTS, and it has similar problems. However, the following works:
- install 10.04 amd64 from CD
- install linux-image-2.6.38-11-generic from http://packages.ubuntu.com/fi/lucid/linux-image-2.6.38-11-generic (transfer it to the laptop using an USB stick)
- add GRUB_CMDLINE_LINUX="nouveau.modeset=0" to /etc/default/grub
- run sudo update-grub
- reboot

Slightly OT: To get the Nvidia display working properly, add the PPA from https://launchpad.net/~ubuntu-x-swat/+archive/x-updates and enable the nvidia driver by running jockey-gtk.

Revision history for this message
subxaero (subxaero) wrote :

What is your BIOS version?

I had similar problem after updating BIOS to F.03. Then decided downgrade it to F.02 and that fixed my case.

Revision history for this message
Simon (simon-baar) wrote :

That would make sense...
I have F.03 as well, and since it appears to be an error with some part of the ACPI, maybe it's broken/incompatible in the new BIOS version?

Revision history for this message
Ingo Gerth (igerth) wrote :

This is very interesting. I am posting here as a person that installed Ubuntu 11.10 flawlessly, out of the box, without any further configuration. Never had any problems and the sole thing that does not work is the finger print reader... If I can help in any way, let me know.

Revision history for this message
Kenrick Bingham (loxo) wrote :

@subxaero: My BIOS version is indeed F.03. It is the one that shipped with the computer.

(Sorry this took a while, I had already given the laptop to the end user.)

Revision history for this message
Neal (ntrischi-deactivatedaccount) wrote :

Hi... after reading/following the instructions on this thread, i'm still have a problems with installing Ubuntu on my HP elitebook 8560w.My bio version is F.03 and every time i try to install Ubuntu i receive these errors..
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
ata5: SATA link down (SStatus 0 SControl 300)

Any help would be appreciated....

Revision history for this message
Kenrick Bingham (loxo) wrote :

@Neal trischitta: Did you try using the "nouveau.modeset=0" boot parameter (#11)?
Which Ubuntu version are you using?

Revision history for this message
Ted Johnson (tedj) wrote :

When should users expect this to be assigned as it's still a problem in the new PP12.04 LTS nightly images.

Revision history for this message
Ingo Gerth (igerth) wrote :

I want to point out, again, it works absolutely fine on my computer. Even with 12.04 images.

My hardware:
Intel® Core™ i7-2630QM CPU @ 2.00GHz × 8
Quadro 1000M/PCI/SSE2

This bug suggests this is a general problem with all Elitebooks 8560w, but *it is not*.

Revision history for this message
Luca Maranzano (liuk001) wrote :

Please note that the 8560w may have the NVidia Quadro 1000 (with the Optimus feature...) or the AMD M5950 graphic card (no optimus).

I think that the nouveau.modeset=0 patch is strictly NVidia related.

So may be that the different behaviours reported may be related to a different hardware configuration.

It should be better to report the exact graphic card used.

Cheers,
Luca

Revision history for this message
Kenrick Bingham (loxo) wrote :

Mine (comment #14) has an NVIDIA Quadro 2000M Graphics Card, and BIOS version F.03. It does not boot out of the box with maverick and later.

I realise that it has not been mentioned yet in this bug that with the 10.04 LTS default kernel on this computer, the network adapters do not work (even the ethernet one) and the display runs at low resolution.

The 2.6.38 kernel (linux-image-generic-lts-backport-natty) makes the network adapters work, but requires the nouveau.modeset=0 boot parameter. The ubuntu-x-swat/x-updates PPA adds proper support for the graphics card. These upgrades are of course a little incovenient to perform with no working network connection (see comment #14).

Revision history for this message
Michael Hüttemann (michael-huettemann) wrote :

I have a 8760w which came with an NVIDIA Quadro 4000M and hat BIOS F.01. This configuration booted okay, just like Ingo Gerth pointed out. After upgrading the BIOS to the currently most recent F.21 version, this bug occured. The "nouveau.modeset=0" workaround works as advertised.

This leads me to believe the problem starts to occur with more recent BIOS revision. I cannot be 100% sure though because I tried hard, but failed to downgrade the BIOS back to F.01 (or F.02 for that matter, which is also available on hp.com).

Revision history for this message
Dave Dennis (atomiclint) wrote :

Its been awhile since the last post, how are people doing with the 8560w with the Nvidia Quadro 1000 doing now?

Has it been stable at all?

I am looking at purchasing one and wish to run ubuntu on it, i just want to make sure that it will work properly without crashes and with 3d before i pull the trigger on buying one.

thanks for your help all

Revision history for this message
Alexey Brodkin (alexey-brodkin) wrote :

Hi Dave,

I'm enjoying my laptop of this type without any major issues.
I may list only few inconveniences with it:
1) To install Ubunto (be it 11.10 or 12.04 daily iso) you need to set "nomodeset" in GRUB to get installer working and install proprietary nVidia drivers. As you get it (nVidia drivers installed) you'll get system up and running generally without issues.
2) There're known issues with Unity in pair with nVidia proprietar drivers:
"Unity launcher corruption on resume from suspend "
https://bugs.launchpad.net/oem-priority/+bug/915265
"Resume from suspend takes much more time when nvidia-current driver is installed."
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/828761
3) If you need fingerprint reader - it won't work. No support in "libfprint"
"Fingerprint reader Validity Sensors not recognized"
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/790183

All other HW devices working properly if I didn't miss something.
Hope it helps.

Revision history for this message
Luca Maranzano (liuk001) wrote :

Hello all,

just to report that I'm currently using Ubuntu 11.10 64 bit on a 8760W (model number LG760ET) with the ATI M5950 graphic card and I'm quite happy with no particular issues after 3 days of heavy usage.

I'had only a really strange issue after the first installation. From the Live CD all was working fine and installation went really really smooth, but at the first reboot the screen was shifted like the attached photo! I was able to enable the ATI fglrx proprietary driver and after the reboot all was ok.

All is working fine so far, temperatures are quite cool and acpi reports this:

$ acpi -t
Thermal 0: ok, 0.0 degrees C
Thermal 1: ok, 0.0 degrees C
Thermal 2: ok, 0.0 degrees C
Thermal 3: ok, 0.0 degrees C
Thermal 4: ok, 0.0 degrees C
Thermal 5: ok, 25.0 degrees C
Thermal 6: ok, 36.0 degrees C
Thermal 7: ok, 35.0 degrees C
Thermal 8: ok, 43.0 degrees C
Thermal 9: ok, 46.0 degrees C

If you need power and big screen with Full HD resolution I'd suggest this model which is a little cheaper than the NVidia ones.
The 8560W with the ATI card is actually the same exact hardware a part the LCD size.

HTH
Cheers,
Luca

Revision history for this message
Josef Andersson (northar) wrote :

Can confirm it worked fine for me with the nouveau.modeset=0 boot parameter (x64 Ubuntu 11.10) as mentioned in the thread. Was a bit worried that Ubuntu wouldn't run on new hp 8560w at first..

Revision history for this message
Fabian Schäfer (fabians) wrote :

In addition to Lucas comment and for EliteBooks with AMD FirePro M5950:

I got rid of the shifted screen by 1) changing to a login-shell 2) installing fglrx with
$ sudo apt-get install fglrx
and 3) rebooting.

Thanks Luca.

Revision history for this message
Patrick G (alsole44) wrote :

As being a rookie in Linux,

I'm having the same error : attached scsi removable disk
On a asus 5750G with Nvidia Gforce 520M

It is running Windows 7 and I have Ubuntu 11.10 booting from an USB device

I see a solution changing "nouveau.modeset=0"

How/where do I add it
I cant get into Ubuntu at all so I guess I should do this either during boot (when ?) or changing something in the files on the USB drive.
the file: to /etc/default/grub is not on the usb drive.

I'm really new to all of this so step by step help would be appreciated.

Revision history for this message
Kenrick Bingham (loxo) wrote :
Revision history for this message
Juan (ecejuan-z) wrote :

Hi

I have HP 8560w, Intel core i5, NVIDIA Quadro 1000M Graphics Card, and BIOS version F.22 (latest) with Vista Enterprise 32 bits.

I have moved several VBOX virtual machines (Ubuntu 10.04.4 LTS 64 bits // Solaris 10 64 bits) from old laptop to this one and when I start them, after some seconds, minutes sometimes (random), the laptop restarts.

I've just installed a new VM using Ubuntu 10.4 (32 bits) and works, no problem.

I don't know if the problem might be related to graphics card or 64 bits (VT).

I tried to install new VM (64 bits) and I had the problem related above about SATA.

If you need more info or any test please advise.

Thanks

Revision history for this message
penalvch (penalvch) wrote :

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, boot using the nomodeset workaround, and run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote :

That is probably due to workaround with "nouveau.modeset=0"
If so, without that flag system won't even boot to allow to collect detailed information about the bug. Although, I'll try to reproduce this bug by running latest available Ubuntu from USB stick later today.

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote :

Bug is still there on todays daily build of 12.04. Attached foto is last what I see on the screen, after that nothing will happen for hours.

Revision history for this message
penalvch (penalvch) wrote :

Alexey Pelykh, could you use the workaround to boot into Precise and file a new report via the Terminal:
ubuntu-bug linux

Thanks!

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote :

Simply boot into Live Precise and after boot simply execute that line in terminal? Nothing more?

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : apport information

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CasperVersion: 1.312
DistroRelease: Ubuntu 12.04
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120324)
MachineType: Hewlett-Packard HP EliteBook 8560w
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname.seed boot=casper persistent initrd=/casper/initrd.lz splash nouveau.modeset=0 -- BOOT_IMAGE=/casper/vmlinuz
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12
StagingDrivers: mei
Tags: precise staging
Uname: Linux 3.2.0-20-generic-pae i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 01/05/2012
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SVD Ver. F.22
dmi.board.name: 1631
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 01.39
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.22:bd01/05/2012:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.39:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8560w
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard

tags: added: apport-collected precise staging
Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : AcpiTables.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : AlsaDevices.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : AplayDevices.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : ArecordDevices.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : AudioDevicesInUse.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : BootDmesg.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : CRDA.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : Card0.Amixer.info.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : Card0.Codecs.codec.1.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : Card1.Amixer.info.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : Card1.Amixer.values.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : Card1.Codecs.codec.0.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : Card1.Codecs.codec.1.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : Card1.Codecs.codec.2.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : Card1.Codecs.codec.3.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : IwConfig.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : Lspci.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : Lsusb.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : PciMultimedia.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : ProcModules.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : PulseList.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : RfKill.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : UdevDb.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : UdevLog.txt

apport information

Revision history for this message
Alexey Pelykh (alexey-pelykh) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Jens (jens-launchpad-net) wrote :

Same bug appears here (HP 8560w). If I enable "nomodeset" as boot parameter, I can boot into the 12.04 live system (beta2 as of 2012-04-24), but the display is locked to 80x600 and I cannot set any higher resolution.

Will run "ubuntu-bug linux" ASAP and report back.

penalvch (penalvch)
tags: removed: apport-collected precise staging
Revision history for this message
Jens (jens-launchpad-net) wrote :

I fixed this by removing all "nvidia-*" packages, adding the nvidia PPA (http://ppa.launchpad.net/nvidia-vdpau/ppa/ubuntu), and reinstalling linux-headers package that match the running kernel (in my case, Ubuntu 10.04, 2.6.38-10-generic) and _afterwards_ the nvidia-current package (280.13-0ubuntu1-lucid-xup2) (which triggers recompilation of the kernel module), then rebooting.

I guess the problem is that the "nvidia.ko" or "nvidia-current.ko" module is simply not being built and shipped with the package, probably due to license issues. This file was nowhere on my system before I reinstalled the drivers.

Revision history for this message
penalvch (penalvch) wrote :

Jens, please execute the following via the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

Revision history for this message
Jens (jens-launchpad-net) wrote :

Christopher, please see Bug #988974.

Revision history for this message
TH Tan (tanth7) wrote :

Dear Sir/Madam,

                 After downloading ISO file
 ubuntu-12.04-server-amd64.iso obtained from
 http://www.ubuntu.com/download/server, the installation was successful
 and complete on HP8560w computer. Upon boot-up, I noticed that the
 graphics device driver has a failed error message after which I cannot
 see the usual Ubuntu login screen. The sound generated upon bootup is correct for the login
 screen. Appreciate if you can check the graphics device driver file
 to see if it is correct. Please help to forward to the relevant
 person for him/her to attend if you are not the correct person. Hope
 to hear from you soon. If you do need further information, please do let me know.

CPU: Intel(R)Core(TM) i7-2720QM CPU@2.2GHz
System Type:64bit
Display Adapters: Nvidia Quadro 1000M
BIOS version:F.26 released on 7June2012 Please advice

Revision history for this message
TH Tan (tanth7) wrote :

Dear Sir/Madam,
                For your information in support of Alpha 3 ISO Testing on Hewlett Packard HP8560w notebook.

Computer HP8560w used for testing:
CPU: Intel(R)Core(TM) i7-2720QM CPU@2.2GHz
System Type:64bit
Display Adapters: Nvidia Quadro 1000M
BIOS Revision:68SVD Ver.F.26
BIOS Date:06/07/2012 7June2012
Video BIOS Revision:nVidia 04/28/11 28April2011

Tested quantal-server-amd64.iso
Problem [1]: Missing firmware files are:iwlwifi-6000g2a-6.ucode during installation.
Problem [2]: After installation and upon reboot, there is only a command line prompt no Unity screen or usual Ubuntu GUI(Graphical User Interface)

Tested quantal-desktop-amd64.iso
Problem [1]: During booting up of installation disk with quantal-desktop-amd64.iso, the following error log was observed but was able to proceed to installation screen. Installation was completed and able to boot into ubuntu os with unity.
[72.994176] tpm_tis 00:04: A TPM error [7] occurred attempting to read a pcr value
[75.803158] kvm:disabled by bios

                Looks like the bugs fixed is not uniform across all iso image. Hope you can fix the above bugs soon and released the next Alpha 4 iso for testing soon so I can redownload and reinstall the above 2 ISO images again. Thanks and hope to hear from you soon. If you need me to log in additional log file, please provide the steps for me to assist in this ISO Alpha 3 testing and reporting.

Regards,TH Tan
<email address hidden>

Revision history for this message
Mattias Walström (lazzer) wrote :

After a kernel upgrade (to 3.5.3) the nouveau problems disapperad. No longer require the "nomodeset" to boot the system.

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

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
penalvch (penalvch) wrote :

TH Tan, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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