Lenovo UEFI issues

[tanstaaflwdm]

Well, I've managed to brick my new laptop and am hoping someone can help me.

Brand new Lenovo Ideapad. Decided I couldn't handle Windows 8 and so try to set up a dual boot to 12.10, 64-bit.

Installed as a separate partition and everything seemed to go well, but when I rebooted I got "Image failed to verify with *ACCESS DENIED*" From there it proceeded to boot into Windows.

OK, so I ran boot-repair. Boot-repair says it ran successfully but now nothing works. I get the grub menu but selecting ubuntu gives me a blank screen and nothing else and selecting anything else gives me an invalid image error. So right now I have nothing.

The url it gave me is http://paste.ubuntu.com/1679821

Please tell me I haven't given myself an expensive doorstop. Any suggestions?

[oldfred]

Welcome to the forums.

Moved to your own thread as in the mega-tread it gets confusing on who is getting what instructions.

Did you turn off secure boot and fast boot in Windows first. And can you still get into UEFI/BIOS?

You may be having video issue or other boot parameter is required with Ubuntu. At grub menu press e and replace quiet splash with nomodeset. Screens shown:
How to set NOMODESET and other kernel boot options in grub2 - both liveCD & first boot, but different
http://ubuntuforums.org/showthread.php?t=1613132
https://help.ubuntu.com/community/BootOptions


Or from Boot-Repair:
Boot-Repair --> Advanced options --> GRUB options tab --> tick "Add kernel option: nomodeset" --> Apply

It looks like Boot-Repair added the correct entries to boot. This is the correct one even though it says recovery.
"Windows UEFI recovery bootmgfw.efi"

These are incorrect as grub still has a bug.
'Windows 8 (loader) (on /dev/sda5)'

[tanstaaflwdm]

Thanks for the move. Was just following the link from the boot-repair page.

Did you turn off secure boot and fast boot in Windows first. And can you still get into UEFI/BIOS?

Uh-oh. Might have shot myself in the foot then. I thought the secure boot/fast boot options were in the BIOS, not in Windows. I didn't see them so didn't change anything.

Since it's a brand-new machine if I could get to the recovery partition I would just reset the thing and start over; there's no data to lose. But I can't seem to get it to boot either. On this Lenovo there is a smaller button next to the power button that is used to access the BIOS/recovery partition, but boot-repair has apparently grabbed it too.

[oldfred]

Secure Boot is definitely in UEFI/BIOS.
But fast boot may be a Windows setting or in UEFI. It seems that it bypasses UEFI booting like with BIOS we had the BIOS loading before grub. But it may be a Windows setting that changes UEFI?
And on some systems then you cannot get into UEFI at all unless Windows is working. Grub has added a new entry to get into UEFI, it should be the last on the grub menu.

Some have totally reset system by reinstalling UEFI/BIOS, but I do not know how to do that unless you can get into UEFI?
And some systems with UEFI have just totally reset (the key you are talking about?) and then it boots Windows again. But this varies by Vendor as each has implemented UEFI differently.

UEFI/BIOS Boot keys - about halfway down on this Microsoft page
http://social.technet.microsoft.com/...ows-to-go.aspx


Two that have worked: lenovo may have similar UEFI but only minor differences for each version?
Lenovo Z580 laptop
http://ubuntuforums.org/showthread.php?t=2112271
Lenovo Ideapad Y500 LiveUSB Problem
http://ubuntuforums.org/showthread.php?t=2095063


But some have reported issues.

The current state of UEFI and Linux = Feb 1, 2013 - Matthew Garrett
Samsung, Lenovo & Toshiba UEFI issues
http://mjg59.dreamwidth.org/22028.html
Matthew Garrett's Blog
http://mjg59.dreamwidth.org/

[tanstaaflwdm]

OK, I have the z580 too but I didn't see an option to turn off secure boot in the bios. I'll check again.

[tanstaaflwdm]

OK, I haven't made too much progress, but my system is partially useful.

Normally I get the Grub menu. Selecting "ubuntu" gives me a blank, grey screen and selecting anything else gives me a variety of errors.

But if I power off and on a few times it will eventually let me into ubuntu. At this point it seems to work fine until I shut down again. Then I have to try a few more times before it will work again.

The power cycle sounds like something is getting caught in cache somewhere or something, if that makes any sense at all, but I can't imagine what it could be. Or maybe hardware related. I'm not sure.

I'm going to avoid doing anything else to the system right at the moment. The reason this became an issue is that I'm in a training class the next few days (mongo db), needed the laptop for it, and my old laptop was a 6 year old Celeron with a bad power switch. So if I can get through the class I'll have time to sort things out.

Our company is moving towards Linux in general and are trying to get us developers migrated over, hence the class, so I'm not exactly bleeding edge when it comes to setting this stuff up. I did perl development on hp-ux for a while, but apparently it's easier to use a server that someone else set up than to do it myself.

I'm tempted just to blow Windows completely away and do a full ubuntu install but I'm afraid it may make this worse at this point. Cthulhu knows that what little I saw of Windows 8 before everything went west did nothing to make me want to use it, but I guess I still need my security blanket.

Anyway, thanks for the help so far. It's given me something to investigate at least. I'll be back in a few days probably asking a lot of dumb questions.

[tanstaaflwdm]

Didn't mean to leave this hanging for so long but I haven't made any progress so haven't had anything to add.

The system is still behaving erratically. Sometimes I can get it to display a status as it boots, sometimes it doesn't. I've actually managed to get into ubuntu twice in the past two weeks but that's it. Usually I give up after four or five tries.

My latest discovery is this repeating message.

https://www.sugarsync.com/pf/D8551579_760_800143722

The "blocked for 120 seconds" message led me to this thread where it seems other people are having the same problem.

https://bugs.launchpad.net/ubuntu/+s...x/+bug/1093217

The thread implies that the system will eventually boot but I haven't seen that happen myself. Maybe I just haven't let it sit long enough. It also says that some people have had success by booting with the battery removed but my system won't work at all without the battery.

Anyway, just didn't want to leave the thread hanging and wanted to give what little new info I have.

Edit: Immediately after posting this I tried booting with the battery out again. Turns out I had to flip the battery lock switch back into position.

It booted into ubuntu immediately...

[tanstaaflwdm]

And the last piece of the puzzle turned out to be nomodeset. I took that back out of my grub options and my system now boots on demand. As long as the battery is removed.

This makes using the laptop as a laptop a bit problematic but in the meantime I suppose I can use the Windows partition if I absolutely have to use it someplace without power. It looks like the problem is in the official bug list so I am presuming that at some point it will get fixed. Until then I think I'm working.

Here's the various bits of solution

For the Lenovo Z580 laptop...
1) To get into the bios (to turn off secure boot) hold down the F2 key while powering on to get access to the bios menu. To turn off secure boot you have to set a bios password. Once that is set, turn off secure boot. There is also a setting to optimize the bios for Windows. Change that to "other os".

2) Install ubuntu

3) To get ubuntu to actually boot, remove the battery. There are two release buttons for the battery. One is spring loaded and the other is not (and will show a red mark when "open"). Close the non-spring loaded button after removing the battery, otherwise the laptop will not power up. You have to be plugged in, obviously.

4) I have disabled bluetooth (bt in the bios). I am not positive that this has an effect anymore but have not tested with it re-enabled yet.

5) Based on what I have found (link in last post) the problem with the battery check was introduced in a relatively recent build. That is why the install disc I was using worked; it was an older version. It was only after I had used the system for a bit and it downloaded and installed an automatic update that the problem appeared.

So that's it. I'm going to call this one closed and keep an eye out for an update that fixes the battery issue.

And that was an annoying couple of weeks. Hope this short-circuits the puzzle for someone.

[nozyczek]

My Lenovo Z580 is finally behaving as expected. Here is the workaround you can use to fix the problem. Also don't forget to thank Tom for finding and documenting this DSDT workaround.

[viperstrike2]

I am somewhat convinced this workaround (http://askubuntu.com/questions/23970.../353999#353999) isn't working anymore (or maybe it's just me). Can anyone verify this works with 12.04 LTS with 3.5.0-35-generic kernel?

Following the above instructions, here is my "sudo update-grub2" output:

Generating grub.cfg ...
Found custom ACPI table: /boot/dsdt.aml
Found linux image: /boot/vmlinuz-3.8.0-35-generic
Found initrd image: /boot/initrd.img-3.8.0-35-generic
Found linux image: /boot/vmlinuz-3.8.0-29-generic
Found initrd image: /boot/initrd.img-3.8.0-29-generic
Found memtest86+ image: /memtest86+.bin
done

However, after rebooting it still hangs with the battery installed.
I rebooted without the battery and ran "dmesg | grep DSDT" and it shows "20061109" (which according to the original Comment #63 means it isn't running the updated dsdt) :

[    0.000000] ACPI: DSDT 00000000daff1000 0AD3E (v02 LENOVO  IVB-CPT 00000000 INTL 20061109)
[    0.097625] ACPI: EC: Look up EC in DSDT

But my dsdt is there...here's the output from "ls -l /boot/dsdt.aml" :

-rw-r--r-- 1 root root 44354 Feb  3 20:21 /boot/dsdt.aml

Furthermore, 01_apci is executable...here's the output from "ls -l /etc/grub.d/01_apci" :

-rwxr-xr-x 1 root root 640 Feb  3 18:43 /etc/grub.d/01_acpi

Does anybody have a clue as to why grub isn't loading the modified dsdt??