I have uploaded fixes that should fix FDE unlocking, please let me know if things are still broken after updating your packages.
1 Like
FDE unlocking all working again 
1 Like
With the latest update I now have 4K 60Hz using USB-C DP on my Dell XPS! (Up from 30hz on previous kernels/DTBs) So I actually now can use my external monitor properly! Great to see the progress.
I do have weird blue screens on my laptop screen sometimes when I disconnect the USB-C. Only a hard reset of the laptop works then. Maybe if I have time I’ll lookup some logs to see if the driver is reporting some issue, and report it upstream.
Also, the only way to get my wanted setup (only external monitor, and laptop screen off) is by booting laptop to Gnome, then select ‘Suspend’ in the power menu, immediately close the laptop screen, then immediately connect the USB-C monitor, and then 50% of the time I do get my monitor running, and the laptop screen is then not active anymore, so I don’t go ‘offscreen’ from my monitor to my laptop area. Can’t find a way to just disable it in Gnome or auto disable the laptop screen when closing lid. But hey, this is progress, cause now I can at least start setup my workflow instead of using my desktop Ubuntu machine!
1 Like
Did anyone managed to boot on the Surface Pro 11? If so, can you tell me which changes to do in order to boot? I really need it, thank you!
1 Like
How did you guys actually get the installer images working? I finally got this booted on my brand new Yoga Slim 7x… after a few attempts to boot I finally got into the desktop, fixed the display settings issue, but after maybe 20 or so attempts, I’ve never had the installer actually let me install anything. It always crashes at a random step. Sometimes it’s step 3 when it goes to detect the keyboard, sometimes it’s after I’ve selected my timezone, sometimes it’s on launch. But the installer app itself seems to be totally broken.
Edit:
Popping open the terminal and using “sudo ubuntu-bug ubuntu-desktop-bootstrap” and digging through the logs that were displaying… I noticed there were a lot of socket-related issues, even though all of the connections being made were pointing at localhost. I completely disabled wifi and bluetooth (put the device in airplane mode), and I was able to get all of the way through setup the first try.
@ryaninbinary this is definitely unexpected and not something I have heard of before. It might make sense to try different USB ports and drives just in case. Feel free to also open a bug at Bugs : ubuntu-concept with your logs attached.
Hello, did you manage to get around with this?
I’m having the same problem in an Archlinux install
I have upgraded the system, and I can confirm that I get the regular Ubuntu loading screen after grub and subsequently also the disk-decryption works. Since I set up a key file that is stored in the initrd (as a temporary thing), this works even without user input.
AND in about 10% of my boots, the system actually boots up normally into the gnome login-screen.
However, in the other 90%, it shows a blue screen after decryption and then reboots. I could not yet figure out a pattern, of when/why it passes and when/why not. Anything I can do to help debug this?
edit: booting in safe mode never leads to a regular loading screen (not even with text) and also not blue screen; safe mode always results in the old behaviour (black screen and then reboot).
1 Like
Thanks for confirming the prompt works!
However, in the other 90%, it shows a blue screen after decryption and then reboots. I could not yet figure out a pattern, of when/why it passes and when/why not. Anything I can do to help debug this?
Is this a 64GB RAM machine? Could you try adding GRUB_BADRAM=0x8800000000,0xf800000000 to /etc/default/grub and then run update-grub and see if that fixes the blue screen?
edit: booting in safe mode never leads to a regular loading screen (not even with text) and also not blue screen; safe mode always results in the old behaviour (black screen and then reboot).
Haven’t ever tried that. I’ll have to check what safe mode does differently.
1 Like
It is indeed!
Adding that to the file (but with quotes like the file suggested) and running update-grub instantly blue-screened the device 
However, I managed to boot into the system again, and run it successfully, and now my boot-success-rate went from 10% to around 50%, so I think we are onto something 
Does this blacklist some regions of my RAM? Maybe we need to blacklist more?
Does this blacklist some regions of my RAM? Maybe we need to blacklist more?
Yes, there is a firmware bug on 64GB devices causing those blue screens and removing the upper 32GB of RAM is the only known working fix of at this point. Maybe I got the mask wrong, try adding cutmem 0x8800000000 0x8fffffffff at the start of your /boot/grub/grub.cfg manually, that is what we do in our installer to make things work.
1 Like
Thank you so much for taking the time, really appreciated!
Oh, boy, I hope this gets fixed at some point.
cutmem seems to let the system boot reliably! Thank you!
This will get overwritten on the next grub-update, correct? What’s the difference between cutmem and badram? Would badram work the hex values you provided for cutmem?
Anyway, really happy to be able to boot the system properly for the first time 
This will get overwritten on the next grub-update, correct? What’s the difference between
cutmemandbadram? Would badram work the hex values you provided for cutmem?
So in theory they should do the same thing as I understand it, only one takes a range and the other takes an address + mask. I’ll have to check why that didn’t work as expected.
I installed Ubuntu successfully on my Omnibook. I did however completely overwrite the preinstalled Windows installation. Is there really no other way than reinstalling Windows, extracting the firmware files and copying them in place under Linux? Anyone willing to share their files with me? Can’t see why copyright would be a problem since the files are delivered with the computer and since they surely eventually will be made downloadable for Linux users as well.
BTW the Swedish keyboard layout is wrong (unless that also would be solved with the right firmware files in place).
1 Like
I did however completely overwrite the preinstalled Windows installation
That should depend on which option you chose in the installer. There is a dual boot and a replace Windows with Ubuntu option.
Is there really no other way than reinstalling Windows, extracting the firmware files and copying them in place under Linux
It looks like you might be lucky and HP actually distributes them on the homepage. It might be possible to extract the firmware using innoextract or similar. See: https://support.hp.com/se-sv/drivers/hp-omnibook-x-14-inch-laptop-ai-pc-14-fe0000/2102217282
Can’t see why copyright would be a problem since the files are delivered with the computer and since they surely eventually will be made downloadable for Linux users as well.
Because things being Shipped with the computer doesn’t mean we are allowed to redistribute them. Windows is delivered preinstalled on the Computer, that doesn’t make it legal for us to redistribute it.
EDIT: So I took a quick look, sp155535.exe should contain everything you need and can be unpacked with 7z e sp155535.exe. qcom-firmware-extract - ~ubuntu-concept/ubuntu/+source/qcom-firmware-extract - [no description] tells you which files you need and where they go. We could update qcom-firmware-extract to download the exe and unpack it automatically in case no local windows installation exists.
So, first of all, I am really happy that FDE now works, thanks for fixing it!
I have been playing around with the system and a lot of day-to-day things work correctly, more than I expected (zoom in browser, airpods…). There are some app-specific hick-ups, but nothing critical, yet.
These are the “major” things I still have:
- I am still not getting dtb files automatically. I have copied the one from the install image to
/bootand always create symlinks for the kernels manually. But this is not a great solution. - Refreshrate of the external monitor is still 30hz, even though someone here suggested this was fixed.
- There is no GL or video acceleration in Firefox (from ppa / not the snap).
- I don’t think any suspend happens on closing the lid, but I still need to investigate.
2 Likes
I am still not getting dtb files automatically. I have copied the one from the install image to
/bootand always create symlinks for the kernels manually. But this is not a great solution.
I still don’t understand what is happening there since I know it works on other machines. Can you please show use the output from apt list --installed | grep flash-kernel, apt-list --installed | grep linux-image and cat /sys/firmware/devicetree/base/model.
flash-kernel (from our ppa) should detect the device based on the model and install the correct dtb, so one of those must be broken or we are missing something.
1 Like
this will be fixed as soon as the firefox snap switches to a core24 base (and the mesa-2404 drivers provided for it through the shared content snap, all my core24 snaps have full HW acceleration already) … i doubt anyone cares for the PPA version though …
1 Like
I was looking at updating the SSD for my Yoga 7x. Can I leave my Windows install on the current drive, and do an ubuntu-only install on the new one? Will I still be able to pull firmware files to the system from my original drive (over USB-C) using the qcom-firmware script?
1 Like
you might have to adapt to modify the script a bit but I think it is simple enough to do that manually. Basically just copy a bunch of files from one disk to the other.
1 Like