KLV-vmhost_rc4 Works with Lenovo Ideapad With 32 bit EFI

[fredx181]

(say you delete that whiteout file (in upper_changes) and reboot, the file will be back again as it originally was with a pristine boot)

Just a little warning: I wrote above only to make clear how it technically works. I wouldn't recommend adding or deleting files to/from upper_changes, it depends on what and how, but weird things may happen if you'd do it as a day to day "regular" operation.

[rcrsn51]

@JusGellin : I'm not sure exactly what you did with your firmware files, but here is a good rule. Don't mess with the building blocks of your system while your system is running.

Boot off your USB drive. Go into your install on the emmc drive. Delete/rename the current firmware.sfs file. Copy in the new sfs file. Reboot.

[JusGellin]

@JusGellin : I'm not sure exactly what you did with your firmware files, but here is a good rule. Don't mess with the building blocks of your system while your system is running.

Boot off your USB drive. Go into your install on the emmc drive. Delete/rename the current firmware.sfs file. Copy in the new sfs file. Reboot.

You may have emphasized this to me before because I am always doing that.
I do use a usb drive to do any of that kind of thing and not directly on the system.

Plus I try doing this only on test systems and not a system I normally use.

Thanks for the good advice from you and @fredx181

[rcrsn51]

OTOH, if you had already determined that the only thing missing was a symlink to a firmware file, you could certainly fix that from within the running system.

As much as people like to promote frugal installs over full, these are situations that full users never have to worry about. There is no potential conflict between files that are inside sfs modules and files that are added later.

It's my gut feeling that frugal installs using overlayfs are more susceptible to strange behaviours than aufs systems.

[wiak]

@wiak and @rockedge
Too much easy talking IMO, how should a new KL user know that he/she has to add w_addmodule="sdhci_acpi" to the kernel boot line, ok, from this thread, yes, if lucky enough reading it.
Btw, if the initrd.gz that I provided to test didn't work for @JusGellin it's very unlikely that doing the above will work (but ok, you'll never know until tested of course).

edit:

Not criticism, just trying to help fixing a problem.

Listen Fred, ....

Well, I could criticize you now for the way you talk, but I'll shut up because there's no end in that. Criticizing criticism ... ... repeating ... ... not constructive and no fun either.

Whatever

[fredx181]

As much as people like to promote frugal installs over full, these are situations that full users never have to worry about. There is no potential conflict between files that are inside sfs modules and files that are added later.
...

That's why I'm starting to like very much the "Pseudo Full Install" concept: viewtopic.php?p=140394#p140394 (has the benefits of a frugal install but works the same as a full install)
No messing with whiteout files (they don't exist in the "pfull" directory), deleted files will be deleted directly there, not "masked".
Excuse me this time for the off-topic please.

[dancytron]

They are called "whiteout" files because they act like white out fluid we used to use with typewriters.

They cover up the file but it's still there underneath.

shopping.webp (20.23 KiB) Viewed 449 times