![]() The reason for my warning earlier was possibly due to an order of operations issue, I think the kernel update came before the firmware package set update, thus causing a problem somehow. Make sure that you're on the latest firmware, as every other document mentions. Then take the rest of the updates with a "dist-upgrade". UPDATE I have been able to get everything working "smoothly", before doing any updates, update the linux-firmware package first. I will be trying an upgrade to the latest 6.3(or whatever shows) to see what happens. But it seems that after updating 6.2, firmware is missing, or it just gets stuck. I am still playing around with things, I may change my statement with additional actions to take. To be clear, do not install kernel 6.2!!! It seems that avoiding the 6.2 kernel is a good thing to do at the moment. I did my initial install with all updates, and it didn’t end well. Right now I have found that a basic install with no updates works the best so far. There is an unstable “concept” build of Ubuntu that will install a version of Lunar Lobster. And a few updates to jhohisel's scripts in my fork as I've modded it heavily for my own testing, and have found some needed additions to make it as close to a "stock" ubuntu iso as possible. ![]() I'm pushing out an iso in a day or two with this patch included. For some reason my auto UUID script doesn't pull the systemd UUID reliably. ![]() BUT, It requires physically adding the UUID. For the time being, I've gotten a script that nicely patches the grub bootloader that you save in the esp directory and can be run anytime anything goes wrong to repair it. And grub apparently needs it to find the kernel I'm assuming? I'm still experimenting and I've found reports of success with grub as the only means. But I have learned that you need something to load up a device tree, to be passed to a kernel. I don't know a whole ton about arm systems, I'm learning allot as I go. Using this method is quite effective though, as it doesn't do an "overlay" so to speak its put into terms that it "replaces it entirely". Why is it later? Why doesn't grub use the dtb itself, AND pass it to the kernel. Grub itself does support dtbs, but in their quote "a device tree can be specified for later use by the kernel". If you use the normal kernel source, then youll have to remember to install a dtbloader or use systemd to pass the device tree to grub. I believe they use the mainline kernel now that it has support. Lenovo Photo Library (including lots of wallpapers)īy the way, arch has a really good support group that made it relatively trivial to install it on the x13s. Mirror of Hardware Maintenance Manuals for discontinued models ![]() Lenovo Windows Digital Download Recovery Images Lenovo Parts Removal and Replacement Videos (select ThinkPad tab) Specification guides for discontinued models When reinstalling Windows, try the Lenovo disc images, as longer battery times have been reported, probably due to custom drivers. A can of compressed air may be useful too, and a bottle of isopropyl alcohol and cotton buds are good for cleaning, but not on the screen. The only tools you need for servicing a ThinkPad are a set of small screwdrivers and a nylon spudger (for taking the screen and keyboard bezels off), and possibly a pair of tweezers. Corporate bulk purchasers don't usually go for it. Not only will it have better brightness, colour, contrast and viewing angles - you will most probably more than make up the investment when selling it. When buying a new ThinkPad, consider taking the IPS screen option if possible, as it doesn't cost much. When buying a used ThinkPad, remember to check that the BIOS is not locked with a supervisor's password and that Computrace is not enabled and activated. For IBM/Lenovo ThinkPad laptop enthusiasts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |