Hi, I’ve been using the MrChromebox script to swap out the 128 GB eMMC that came with my my Idea Pad 5 Chrome 16IAU7 laptop to an NVME drive and set up the machine to dual boot into Ubuntu 23.
But I got things working. I have a few problems though I was hoping someone could tell me figure out:
Sometimes when booting I get the error “nvme nvme0: Device not ready; aborting installaition, CSTS=0x0”. Also sometimes when coming out of sleep I think the same error occurs and it causes the login screen to break. This also occurred during Ubuntu installation (install would sometimes only see the USB stick and not the NVME drive, other times it could). I think going to the boot menu and picking a boot device lowers rate of failure but doesn’t eliminate it.
I can’t get Fn keys to work. Pressing the search key before the fn key works in ChromeOS but not Ubuntu
I’m not sure if all these are firmware related but I think at least some ought to be (and if anyone has tips on the others I’d appreciate it). I searched the forum and didn’t see any relevant previous posts.
Oops the nvme error message is “nvme nvme0: Device not ready; aborting initalization, CSTS=0x0". And of course when it can’t find the hard drive boot fails.
I’m afraid I don’t know anything about replacing your Chromebook’s internal storage. As for identifying sound issues on your Chromebook, please run the debugging script and tag WeirdTreeThing.
Can you also share the .conf file in /etc/keyd here so I can take a look and see if I can help with the shortcut key issue you’re having?
Replacing the internal storage worked fine. I believe the error related to not finding the NVME is independent of that (but I mentioned it just in case it was somehow relevant) as this never happens when booting to ChromeOS, it only happens with edk2 booting to grub for Ubuntu. Once the boot partition is found there are never any errors accessing the disk from Ubuntu.
@sadlerm wrt to the Fn keys, to be clear, they do work as ‘back’ / ‘volume up’ etc… keys but I’m unable to find a key combination that actually sends F1, F2 etc… which is what I want. I’ve tried both search + F-key (which is what works in ChromeOS) as well as Ctrl+Alt+F-key (somewhere on the internet I think I read maybe that’s how it should be accessed). Am I just not using the right modifier key? Is the [meta] from the config file the Chrome ‘search’ key?
Ideally I’d be able to set them to send F1, F2 … by default and then have a modifier for sound up / mute / etc… but as long as I can use both modes somehow that’s good enough for me.
if you’re dual booting, you’re running the stock firmware, and there’s nothing one can do at the firmware level to fix any issues which might come out of running RW_LEGACY along side it – be they audio or keymapping related.
if your NVMe drive is failing to boot from edk2, it could be a coreboot issue, or it could be an edk2 issue, but there’s no way to debug it because there’s no debug output from the stock firmware. You’d have to flash the UEFI Full ROM firmware and hope the issue is reproducible there, and hope it’s in edk2 so it can be fixed there.
I tried xubuntu 23 and now hotkeys are working fine.
if your NVMe drive is failing to boot from edk2, it could be a coreboot issue, or it could be an edk2 issue, but there’s no way to debug it because there’s no debug output from the stock firmware
Will rerunning the MrChromebox script update coreboot/edk2? Assuming it is a bug in one of those I’d like to try newer versions of them as they’re available.
Used ‘mainline kernels’ to upgrade to 6.6.15 and then ran the ‘chromebook-linux-audio’ setup again and still only see the dummy output device. Anything else required?
> uname -a
Linux <hostname> 6.6.15-060615-generic #202402010035 SMP PREEMPT_DYNAMIC Thu Feb 1 01:23:26 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux