No suspend after upgrade

[moteprime]

Hi again.
The guide did not work for me, and as Christopher on Launchpad sez, the hardware in our Ideapads are different. But thanks a lot for writing it.

Well, i had it with this crappy laptop. The hours i spend to get it to works in Ubuntu are a waste. It is only made for running windows, and that for somebody else than me.
I gave up, and went and got a e130 thinkpad. Everything works out of the box, except a couple of the function keys.
It's a bliss.

[ppq]

I wonder, is there a quicker way to achieve this? Windows must be manipulating the EFI boot entries somehow so could we use efibootmgr to replicate that without installing Windows?

Would it be possible for you to give us the result of "sudo efibootmgr -v" after Windows has "fixed" your EFI bios?

Then maybe we can just add the efi entry and make it work without needing to install Windows. From reading other forum posts we can see that the Ubuntu EFI entry must be moved down the boot order as booting with that instead of directly from the HDD device prevents the wifi from working (shows as hardware disabled) so perhaps the problems run deeper than just wifi. The ubuntu EFI boot entry would seem to be the root cause of a number of issues so suggest we look into that.

Thanks

Hi,
when my laptop was in CSM compatibility mode, I was able to get some output from efibootmgr, but I was unable to create new entries. The commands were executed without errors, but when I would run efibootmgr again, nothing would be different.

This is the output now, while in UEFI mode:

bene@s205:~$ sudo efibootmgr -v
[sudo] password for bene: 
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,0002,0004,0005,0006
Boot0000  Setup    
Boot0001  Boot Menu    
Boot0002* USB FDD:    030a2400d23878bc820f604d8316c068ee79d25b6ff015a28830b543a8b8641009461e49
Boot0003* ATA HDD0: SAMSUNG 470 Series SSD                      ACPI(a0341d0,0)PCI(11,0)ATAPI(0,0,0)..bYVD.A...O.*..
Boot0004* USB HDD: SanDisk Cruzer Blade    ACPI(a0341d0,0)PCI(13,2)USB(1,0)3.!..3.G..A.....
Boot0005* USB CD:    030a2400d23878bc820f604d8316c068ee79d25b86701296aa5a7848b66cd49dd3ba6a55
Boot0006* PCI LAN: Realtek PXE B02 D00    BIOS(6,0,5265616c74656b20505845204230322044303000)..................@.......@...@.............................................A.....................
bene@s205:~$ sudo efibootmgr ## this looks exactly the same as before
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,0002,0004,0005,0006
Boot0000  Setup
Boot0001  Boot Menu
Boot0002* USB FDD:
Boot0003* ATA HDD0: SAMSUNG 470 Series SSD                  
Boot0004* USB HDD: SanDisk Cruzer Blade
Boot0005* USB CD:
Boot0006* PCI LAN: Realtek PXE B02 D00

Summary by boot-repair: http://paste.ubuntu.com/1478637/

Edit: One could try to set the laptop in UEFI mode by wiping the disk completely (dd if=/dev/zero to get rid of GPT traces), resetting the laptop a few times (no power, no battery, holding the power button for 30 sec) and booting a Ubuntu Live CD and checking if waking up from suspend works.
Unfortunately I didn't try this before doing it my way (see previous post).
When it works one just needs to install Ubuntu while letting it create the vfat UEFI partition , and then use boot-repair to magically make it bootable.

[belrik]

I spent this evening trying to remove and then re-create the EFI partition. I started with using boot-repair with the EFI options enabled and then reformatted the EFI partition and re-created it from scratch. No difference. I have a single /EFI/ubuntu/grubx64.efi file there and for some reason although that boots it behaves strangely and seems to break wifi. Interestingly I noticed that I get different results if I choose "ubuntu" in the BIOS boot menu as opposed to setting it to default above the disk drive under boot options. For some reason doing that is invoking the boot in a different way and I see garbled text on the console but the wifi doesn't break. Suspend and shutdown are still broken whatever I do though, resulting in a hang.

I don't have a spare laptop so I can't wipe this to install Windows, will just have to wait until this is fixed upstream.