Welcome to MilkyWay@home

Posts by Siran d'Vel'nahr

1) Message boards : Number crunching : I gotta remember... (Message 75060)
Posted 17 Feb 2023 by Profile Siran d'Vel'nahr
Post:
Greetings,

Just over 4 days ago I was finally able to get my dual boot system working properly. I did a lot of searching of the Internet and tried many different approaches. I was able to find something that showed me the location of the Grub boot loader. Are you sitting down? It showed me that it was located /sdb1/cdrom or something like that. The only time I have a CD/DVD machine hooked up is if I decide to watch a DVD movie. It is connected through a USB port.

I found something (cannot remember what it was that I found) that got rid of that entry. I had all SSDs and my one HDD disconnected and had only the Windows M.2 NVME drive installed. Windows was completely installed, finally.

I re-connected my other drives and booted into Linux Mint. I did the sudo os-prober and updated Grub. I rebooted and Windows showed up in the Grub menu. I selected it and booted into Windows. I then rebooted and selected Linux Mint and booted into it. Problem fixed!

@Keith:
I believe that what I fixed this thing with was one or more of these that I saw on the Internet:
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
But if memory serves, I fixed it by booting into my Live USB Linux drive. Memory is really bad any more at my age (71), mostly short term. Using GParted was how I found the /cdrom crap and I could do nothing with the partition since it didn't exist anywhere. Maybe I didn't use the above commands, but I do remember something about them. I don't know, I just don't remember clearly. All I remember was being very elated when I got it fixed!

Thanks Keith for the help you gave.

Have a great day!

Siran
2) Message boards : Number crunching : I gotta remember... (Message 75032)
Posted 7 Feb 2023 by Profile Siran d'Vel'nahr
Post:
Hi Keith,

I found something different about setting up Linux Mint and Windows as dual boot on 2 SSDs.

When I partitioned my Linux SSD I used "Partition type: Primary" for the EFI and /boot partitions, the / and /home partitions, per instructions I used, are set to "Partition type: Logical". I found another set of instructions that set all partitions as "Partition type: Primary". Also it says to select the /EFI partition before hitting the "Install Now" button, for loading the bootloader. I selected the / partition I believe. It is looking to me as though I must, once again, install Linux Mint using the new instructions I just found.

What do you think? I won't do anything until I get your opinion.

Have a great day!

Siran
3) Message boards : Number crunching : I gotta remember... (Message 75031)
Posted 7 Feb 2023 by Profile Siran d'Vel'nahr
Post:
Hi Keith,
Go back to the /boot/grub/grub.cfg file and see what the -- set root= statement has for the UUID for the Linux OS set root= statements.
The -- set root= statements are set to the UUID of my Linux partitions.

I think you will find either one of your Windows1 chain or Windows chain UUID's match one of the Linux OS set root= values.
That is why you are getting the Linux OS booting when you select the Windows grub choice.
I don't understand how setting the Linux -- set root= statement to a Windows UUID will cause the PC to boot into Linux.

I don't think you should have TWO chain statements. One of them is incorrect and its entry should be removed from the grub.cfg file.
I think maybe the second entry which probably is identified as chain1 is the extraneous one. But verify first which one has the same set root= value as one of your Linux entries.
Both have the Windows partitions UUIDs.

Then it is as simple as removing the entry from the file. If it is the second statement, just cut everything within the curly braces.

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
I don't feel comfortable messing with that file.

I used the Disks function in Accessories to verify the UUIDs for both M.2 NVME drives. The UUIDs for the Windows partitions M.2 match that which is in the grub.cfg file. The UUIDs for the Linux partitions M.2 match that which is in the grub.cfg file.

I'm thinking about joining the Linux Mint forum and posting everything there to see if someone may have any ideas to fix this. So, until then I won't be messing with the grub.cfg file. Like I mentioned, I don't feel comfortable about that. If I need to go into Windows for any reason I will just use the BIOS Boot Override method.

Thanks Keith and have a great day!

Siran
4) Message boards : Number crunching : I gotta remember... (Message 75024)
Posted 5 Feb 2023 by Profile Siran d'Vel'nahr
Post:
Hi Keith,

OS-PROBER Output:
 sudo os-prober
[sudo] password for rick:                 
/dev/nvme0n1p1:Windows 10:Windows:chain
/dev/nvme0n1p2:Windows 10:Windows1:chain

I looked at /boot/grub/grub.cfg and this is the section pertaining to Windows:
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 10 (on /dev/nvme0n1p1)' --class windows --class os $menuentry_id_option 'osprober-chain-FAD4518FD4514F4F' {
	insmod part_msdos
	insmod ntfs
	search --no-floppy --fs-uuid --set=root FAD4518FD4514F4F
	parttool ${root} hidden-
	drivemap -s (hd0) ${root}
	chainloader +1
}
menuentry 'Windows 10 (on /dev/nvme0n1p2)' --class windows --class os $menuentry_id_option 'osprober-chain-320452170451DF03' {
	insmod part_msdos
	insmod ntfs
	search --no-floppy --fs-uuid --set=root 320452170451DF03
	parttool ${root} hidden-
	drivemap -s (hd0) ${root}
	chainloader +1
}
set timeout_style=menu
if [ "${timeout}" = 0 ]; then
  set timeout=10
fi
### END /etc/grub.d/30_os-prober ###

I hope this sheds a little more light on this issue. :-) By the way, my M.2 NVME drives are correct: /dev/nvme0n1pX. The sda and sdb storage devices are my NTFS drives: data drive for storage and a SSD for installed games.

Thanks Keith and have a great day!

Siran
5) Message boards : Number crunching : I gotta remember... (Message 75020)
Posted 5 Feb 2023 by Profile Siran d'Vel'nahr
Post:
Hi Keith,

... Now you say you can boot Windows from the grub menu with no issues.
I can only get booted into Windows if I use the boot option in Boot Override in the BIOS and select the Windows drive in Grub that displays. In a normal boot, without going into the BIOS, if I select the Windows drive to boot from in Grub, it boots into Linux.

You must have a scrambled grub in boot. Probably the Windows UUID is pointing at the Linux drive.

I looked in Grub and the only line that is uncommented is the OS_PROBER line you had me add, plus these lines near the top of the file:
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

In the fstab file, there is no reference to Windows, a Windows drive or UUID at all. All it shows are my partitions on the Linux NVME drive.

I shall keep looking on the Internet too to see if I can find a solution.

Thanks Keith and have a great day!

Siran
6) Message boards : Number crunching : I gotta remember... (Message 75013)
Posted 4 Feb 2023 by Profile Siran d'Vel'nahr
Post:
Hi Keith,

Well, I'm back into Winders, but...

First things first: I was not installing drivers for my Razer keyboard and headset. I was installing the setup software which controls the LED back lighting on the keyboard and shows battery level and other things for the headset. This software is in the software manager. I don't remember exactly what happened after the installation was complete. I do remember looking for the software in the menu and could not find it for some reason. That was when I decided that perhaps a reboot was in order and when I discovered the problem.

Now for the Winders "but..." above: I went into BIOS as you suggested.

The Boot Option Priorities has 2 selections:
#1 Ubuntu (1 TB NVME SSD)
#2 1 TB NVME SSD

I went into Boot Override which included my 250 GB NVME SSD with Winders installed. If I were to boot normally to go into Linux, the Grub menu is in lower resolution (1024 x 768). If I go into BIOS and select my Winders drive, the Grub menu is displayed in the higher resolution and I can boot into Windows by selecting it in the menu. If I select the Winders drive in the low resolution Grub menu, the machine boots into Linux Mint. Go figure! I'm stumped.

Can I do this:
So you need to boot the Windows install medium and drop to a command window then issue these commands:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

Then reboot and using the grub menu for Windows, see if you can get into it.

by booting into Winders via the BIOS method? Winders does not have a "LiveCD/USB" like Linux does, at least not that I remember. I don't go into Winders very much anymore, maybe once every few months or so, so booting Winders through the BIOS method is Ok with me. But if the above fixes can get me into Winders in a normal manner, so much the better. I will wait for any response you may have. :-)

Thanks Keith and have a great day!

Siran
7) Message boards : Number crunching : I gotta remember... (Message 75004)
Posted 3 Feb 2023 by Profile Siran d'Vel'nahr
Post:
Hi Keith,

Everything went well with the Grub file. The line was not there and I added it. After the grub update, it showed that it saw the Windows installation drive. Now...

I rebooted and went into Linux just fine. I rebooted again to go into Windows and get this on the screen for several seconds then re-displays the Grub menu:

Secure Boot forbids loading module from (HD3, GPT2) /grub/x86_64-EFI/parttool.mod.
Can't find command 'drivemap'.
Bad shim signature.

Uh, Ok, I just looked on the Internet and found a few things that have me thinking. I believe I have Secure Boot [Disabled]. I'm going to reboot and set it to [Enabled] to see if that fixes this new problem. Be back in a flash...

[edit]Well, I was wrong; Secure Boot was [Enabled].

I did make a change to the OS type; I changed it to [Other OS]. This is what I got:

Setting partition type to 0x7.
Error: can't find command 'drivemap'.
Error: invalid EFI file path.

I switched back to what was original and am back to the error messages above about "Secure Boot forbids...".

I will look some more on the Internet.
[/edit]

Thanks Keith,

Siran
8) Message boards : Number crunching : I gotta remember... (Message 75001)
Posted 3 Feb 2023 by Profile Siran d'Vel'nahr
Post:
Hi Keith,

Ok...

I reinstalled Linux Mint with CSM enabled and the EFI partition at the beginning of the drive. Believe it or not, I'm still getting those ACPI Error messages yet I'm now booting into Linux "properly". Everything is now configured the way I had it. I'm still not getting a Grub menu and the Windows M.2 NVME drive does not show up when I use F8 to bring up the boot menu.

I went to that page you linked to for installing Grub2 from the USB install drive. I booted from the USB drive and proceeded to use the second section since this is still a supported version of Linux Mint. I used the commands in the terminal window and listed the drives. I'm confused here. The (*) is shown at the boot partition of my Windows M.2 NVME drive. Is that where Grub gets installed? I had no problem with Grub until the fiasco which happened when installing the control software for my keyboard and headset. Everything worked just fine until that point.

I will hold off on the Grub issue until I find out if indeed that is where Grub is installed. Perhaps I shall check the Internet again... ;-)

Thanks and have a great day!

Siran
9) Message boards : Number crunching : I gotta remember... (Message 74997)
Posted 3 Feb 2023 by Profile Siran d'Vel'nahr
Post:
Hi Keith,

Well, something weird happened to this system when I was sleeping, of all things. I can no longer mount the drives: 2 M.2 NVME drives, one 1 TB SSD and my 500 GB spinning HDD. My Update Manager can no longer refresh the list. I'm not sure what else can be/go wrong. :-\

I do have Linux and Windows 10 on separate M.2 drives. My EFI partition is not first, but last. My mistake; did not know that the position was relevant. Not only that, this was the first time installing Linux Mint that while doing the partitioning even mentioned the EFI partition. Must be a new thing in this new version of Mint.

I will re-enable CSM and do a reinstall of Linux Mint... again, this time putting the EFI partition first. I'll let you know what I come up with.

Thanks Keith. Have a great day!

Siran
10) Message boards : Number crunching : I gotta remember... (Message 74992)
Posted 2 Feb 2023 by Profile Siran d'Vel'nahr
Post:
Greetings everyone! Been a long time. No, I'm not back to crunching for MW. I have come across a major problem however, and I happen to be acquainted with a few here that are running Linux in whatever flavor.

I'm still running my 8th gen Intel system; all the specs are in my profile. I had to get a new keyboard because of keys no longer working 100% or keys that would continue to post without a further key press. I had decided to install the Razer control software for my new keyboard and my headset. And here is where the major problem reared its ugly head:

Upon reboot, after installation, I received a mass quantity of errors and the machine would not boot. I cannot do a copy/paste so I will attempt to type 2 lines without any mistakes:

ACPI Error: Aborting method \_PR.PR11._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
ACPI BIOS Error (bug): Could not resolve symbol [PR.PR00._CPC, AE_NOT_FOUND (20210730/psargs-530)


Those 2 lines would repeat 10 more times before the system would go into "maintenance mode". Also I could not boot into Winders 10 on my second M.2 drive. So I figured that I would have to reinstall Linux Mint v21.1. I would see the same errors listed above yet Linux would boot from the USB flash drive. After installation I would reboot and the same thing would happen; the system would go into "maintenance mode" after listing the above errors. I did reinstall twice more with the same results. I decided to see what I could find on the Internet using my laptop...

On one forum I found that there a 3 causes for this: A change in the BIOS, a Kernel modification or a hardware problem. I figured that it was a hardware problem. I found another forum where someone had the same problem and he went into the BIOS and disabled CSM and still sees the errors yet is able to boot into Linux. I decided to check into new hardware but thought about the CSM item and in the next morning decided to disable CSM and reinstall Linux MInt. Voila, it worked. I'm back into Linux, but...

I no longer have a Grub menu and cannot boot into Winders. Using F8 does not find the other M.2 drive. Plus I still see the errors in the logs and on screen before booting into Linux.

Does anyone have any ideas on this?

Have a great day!

Siran
11) Message boards : Number crunching : I gotta remember... (Message 71218)
Posted 6 Oct 2021 by Profile Siran d'Vel'nahr
Post:
The next LTS kernel is going to be 5.10. https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.10-LTS-EOL-EOY-2026
Your guess is as good as mine. I am not familiar with the tools in Mint. You will have to discover that for yourself.


Hi Keith,

I just tested the "Remove Kernels..." button. All it wants to do is remove "installed" Kernels (not the active one of course) which makes me come to a conclusion of more confusing Kernel stuff:

The only Kernels installed are the last used and the currently active. The other Kernels listed in the different series are just the version numbers of all the Kernels. When installing the Kernel the appropriate files and dependencies are first downloaded then installed. I'm thinking that I have only 2 Kernels installed on this PC. Which begs the question: Why do I have version 5.8 list which are labeled "End-of-Life"? That truly makes no sense. :-|

And another question: Why, when updating a Kernel, would something have to be done with ALL the other listed versions? I don't get it. Or, is the updater making sure that all the others, save for the most recent, are uninstalled? It sits on each version number for a good 30 seconds. But then, if the previous update did that, why would new updates need to go through those hoops again? I think I'm thinking too much, me thinks. ;-)

Have a great day! :-)

Siran
12) Message boards : Number crunching : I gotta remember... (Message 71217)
Posted 6 Oct 2021 by Profile Siran d'Vel'nahr
Post:
Because the only way to get things tested and ready for the LTS setting is to send it out to be tested, and you are one of those people. They now want you to provide feedback on any problems you are seeing so they can address them before they come out, or get redone or even dropped, before the next LTS release. That's often why you will see a long list of changes before the next release, people are providing feedback and the developers are working on things.

Hi Mikey,

When I installed and did the re-install I saw nothing that would opt me into testing and sending feedback. I don't want to be a tester of Kernels. :-( Why would the maintainers want obsolete, end-of-life or older versions of a current series tested? To me that would be like trying to get DOS 6.2 to run on modern PCs. I don't believe it would work and I don't see the point of testing old Kernels.

Have a great day! :-)

Siran
13) Message boards : Number crunching : I gotta remember... (Message 71215)
Posted 6 Oct 2021 by Profile Siran d'Vel'nahr
Post:
The next LTS kernel is going to be 5.10. https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.10-LTS-EOL-EOY-2026
Your guess is as good as mine. I am not familiar with the tools in Mint. You will have to discover that for yourself.

Hi Keith,

Ok then, I'll spend a little more time stomping on the Internet to see what I can find and if I don't find anything specific, I'll just cross my fingers and hope for the best. I'm sure the Update Manager won't just remove Kernels willy nilly. I'll first try it on the Kernel series the system is NOT using to see what happens. ;-) I'll let you know what happens.

Have a great day! :-)

Siran
14) Message boards : Number crunching : I gotta remember... (Message 71212)
Posted 5 Oct 2021 by Profile Siran d'Vel'nahr
Post:
Because distros choose a long-term release for the stable platform version. Kernel 5.4 is the LTS kernel for your distro. Corporate IT managers like having all computers on the LTS package because they have commonality for support.

But the latest kernels are often pushed into HWE (HardWareEnablement) releases that offer the latest support for new hardware, latest bugfixes and latest feature sets.

The 5.11 kernel is one in the HWE series.

Distro maintainers declare which kernel series gets LTS denomination about every 4-5 years in 5 year leapfrogs typically. The next LTS kernel is the 5.10 series I believe.

https://www.kernel.org/

Hi Keith,

Ok, that makes sense. I understand LTS. But...

If the distributors are not using the 5.11 or 5.8, why even bloat the install with them? In the next iteration of Linux are we gonna have 5.11, 5.10, 5.8 and 5.4? Or will they get rid of one or both of the Kernels not active in an install and make the active obsolete after an update?

I went ahead and did the Kernel update and everything is just fine. I had my fingers crossed this time. ;-) So I guess that when you set the updater to automatically delete obsolete Kernels, it only deletes those marked "Obsolete", which I had done several days ago by hand. There weren't that many.

OH BOY!!! I just looked at my Kernel list in the updater and the "Remove Kernels..." button is now live. If I click that will it ONLY remove the ones not active or installed in each series and allow me to keep 1 or 2 older working ones? All the other times I looked the button was greyed out. If I remember correctly, when I was tramping the Internet trying to find out how to get rid of them it was always to go into the Kernel list and click the "Remove Kernels..." button. Mine was always greyed out.

I just watched a couple videos on Kernels and if you click on a kernel that says "Installed" you get a button to remove it. The others have an "Install" button. I'm thinking that with the "Remove Kernels..." button I should get a selector in each series of Kernels to select what to remove or remove all. Or is that just me dreaming? ;-)

Have a great day! :-)

Siran
15) Message boards : Number crunching : I gotta remember... (Message 71208)
Posted 5 Oct 2021 by Profile Siran d'Vel'nahr
Post:
No, I would not worry about it. It would take a vendor specific quirk added to the Linux-firmware package by the distro maintainers to fix the issue which is really benign, except for the growth of the logfiles I mentioned.

Hi Keith,

Ok, I won't worry about it then. :-)

I'm thinking of going ahead with the current Kernel update, but there is something that is confusing. Why is the most current and the currently active lower in version numbers than all the Kernels shown in Update Manager? Here's what I mean:
5.11... -- 1 supported until February 2022
        -- all the rest "Superseded"

5.8...  -- all "End Of Life"

5.4...  -- 0-88 supported until April 2025 (currently in line for update)
        -- all others "Superseded"
        -- currently active is 7th down the list from 0-88

Why would we not be using the higher version numbered Kernel 5.11... instead of 5.4...? I don't understand this. :-\

Have a great day! :-)

Siran
16) Message boards : Number crunching : I gotta remember... (Message 71206)
Posted 3 Oct 2021 by Profile Siran d'Vel'nahr
Post:
Hi Keith,

Did as you mentioned and I no longer see the error when the PC is booting. I did this:
dmesg --level=emerg,alert,crit,err,warn

and it no longer appears in the report.

Is that a problem with the motherboard? I went to the websites of the 2 urls at the top of that report and that kinda bothers me. Since it is 8th generation, would it behoove me to upgrade the PC MB and CPU at my age, (knockin' on the door of 70)?

Thanks and have a great day! :-)

Siran
17) Message boards : Number crunching : I gotta remember... (Message 71204)
Posted 2 Oct 2021 by Profile Siran d'Vel'nahr
Post:
You can see what the error with the PCIE was with:

dmesg --level=emerg,alert,crit,err,warn

Hi Keith,

I was so wrapped up in the other issues that I forgot about this. This is what is shown:
[    0.161935] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.161935] TAA CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/tsx_async_abort.html for more details.
[    0.161935]   #7  #8  #9 #10 #11
[    0.172499] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.462731] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[    0.462737] pcieport 0000:00:1c.4: AER:   device [8086:a294] error status/mask=00000001/00002000
[    0.462739] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
[    0.518956] platform eisa.0: EISA: Cannot allocate resource for mainboard
[    0.518957] platform eisa.0: Cannot allocate resource for EISA slot 1
[    0.518957] platform eisa.0: Cannot allocate resource for EISA slot 2
[    0.518957] platform eisa.0: Cannot allocate resource for EISA slot 3
[    0.518958] platform eisa.0: Cannot allocate resource for EISA slot 4
[    0.518958] platform eisa.0: Cannot allocate resource for EISA slot 5
[    0.518959] platform eisa.0: Cannot allocate resource for EISA slot 6
[    0.518959] platform eisa.0: Cannot allocate resource for EISA slot 7
[    0.518960] platform eisa.0: Cannot allocate resource for EISA slot 8
[    0.573535] resource sanity check: requesting [mem 0xfdffe800-0xfe0007ff], which spans more than pnp 00:07 [mem 0xfdb00000-0xfdffffff]
[    0.573537] caller pmc_core_probe+0x7f/0x180 mapping multiple BARs
[    0.957333] nvme nvme1: missing or invalid SUBNQN field.
[    1.111279] ata4.00: supports DRM functions and may not be fully accessible
[    1.115867] ata4.00: supports DRM functions and may not be fully accessible
[    4.647659] nvidia: loading out-of-tree module taints kernel.
[    4.647667] nvidia: module license 'NVIDIA' taints kernel.
[    4.647667] Disabling lock debugging due to kernel taint
[    4.703413] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  460.91.03  Fri Jul  2 06:04:10 UTC 2021
[    4.915877] kvm: disabled by bios
[    5.103310] kvm: disabled by bios
[    5.498284] kvm: disabled by bios
[    5.540589] kvm: disabled by bios
[    5.554915] kauditd_printk_skb: 13 callbacks suppressed
[    5.662174] kvm: disabled by bios
[    5.742727] kvm: disabled by bios
[    5.818308] kvm: disabled by bios
[    5.898109] kvm: disabled by bios
[    5.913839] nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
[    5.913841] ucsi_ccg 0-0008: i2c_transfer failed -110
[    5.913843] ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
[    5.913847] ucsi_ccg: probe of 0-0008 failed with error -110
[    6.113314] kvm: disabled by bios
[    6.322535] kvm: disabled by bios
[    6.730415] kvm: disabled by bios
[    6.971035] kvm: disabled by bios

Anything stand out?

Have a great day! :-)

Siran
18) Message boards : Number crunching : I gotta remember... (Message 71203)
Posted 2 Oct 2021 by Profile Siran d'Vel'nahr
Post:
https://forums.linuxmint.com/viewtopic.php?f=59&t=331611&p=1898849#p1898849

Hi John,

Thank you, that seems to have done the trick. After doing the edit and rebooting, I changed to v460 NVIDIA and rebooted. I checked my display and it showed my monitor. Just to be sure, I rebooted a second time, to simulate booting into Linux after running Winders, and no message in the upper right hand corner about "no hardware acceleration". I checked the display and it showed my monitor and also went into NVIDIA settings and everything seems good. Oh yeah, by the way, I had my fingers crossed both times. lol ;-)

Next step is to do the Kernel update and see about getting rid of the obsolete versions automagically. I'll do that in a day or 2 or 3 just to make sure my video problem is a thing of the past. :-)

Thanks again and have a great day! :-)

Siran
19) Message boards : Number crunching : I gotta remember... (Message 71201)
Posted 2 Oct 2021 by Profile Siran d'Vel'nahr
Post:
A kernel comprises only 5 files. Two header files, an image, module and module-extra file.
There are of course dozens and dozens of kernel versions available in the distro.
You are only interested in either the latest stable standard or HWE versions.
I'm thinking you are being confused by Synaptic. You aren't looking for all the kernels available to be installed from the distro, just the ones you have installed in the host.
You just click on the Status button in the left hand panel and then use the Installed - Auto Removeable button.
Then use the Not Installed - (residual configurations) button and check all the older kernels to be removed. That may take a while if as you stated you have 128 older kernel configuration files hanging around.

Hi Keith,

First off, I set up Update Manager so that it will dispose of older Kernels automagically, all but the most recent working or 2.

You're correct in that Synaptic is confusing. So I am just gonna let Update Manager do its thing.

This is getting just too ridiculous! Going to v460 did not fix my video problem. I switch to the Nouveau driver and then to v460 and now on the v460 reboot I get the message about no hardware acceleration. So I have stuck to Nouveau for now. At least the display settings utility shows my monitor and not "laptop" and the video is not herky jerky. When all them obsolete Kernels are gotten rid of I will try v460 again. Any ideas on when Update Manager will purge the obsolete? Will it happen when I try to update the Kernel again? I believe that on a clean install that ONLY the 2 or 3 most recent Kernels be packaged for the install. Why the heck do they put obsolete Kernels in the install package? Makes not sense to me.

Have a great day! :-)

Siran
20) Message boards : Number crunching : I gotta remember... (Message 71191)
Posted 30 Sep 2021 by Profile Siran d'Vel'nahr
Post:
If the r460 drivers are currently working and you don't have any projects that require the r470 drivers like GPUGrid, then I would stay pat now and first fix the issue you have with the kernel.

Hi Keith,

I had a problem with 470 on my last install of Mint. The display was said to be a Laptop. This time when I installed Mint I was hoping that 470 was "fixed". I'm thinking that it is not broken, just that it sees my machine differently than 460 does. I will be sticking with 460. :-)

Are you saying that running apt autoremove and autoclean did not work? Autoremove needs an acknowledgement "y" to remove the old programs. Autoclean does not.

Yes, they did nothing that I could see. I don't remember if autoremove asked for confirmation or not. I'll have to check again and let you know. Ok, just checked and it does not ask for confirmation.

You can also remove old programs with the Synaptic Package Manager. Did you try that method?

I went into Synaptic and holey moley, there are about a million files for the Kernels, well maybe not a million, but hundreds anyway. I haven't figured out how to remove ALL the files for all but 3 of the most current Kernels yet. By the way, the /boot partition is where the Kernel is stored, correct? I'm pretty sure I sized it 1 GB. I have / at 100 GB and /home takes up the remainder of the 1T NVMe drive.

I would not attempt to update the kernel until you can straighten out all the old kernels still hanging around in the apt-cache.

Hadn't plan on it. ;-)

Remember, the video drivers are compiled into each kernel. So if you have kernel issues which you seem to have, that leads to the likelihood of having issues upgrading the video driver.

Is it a general notion to only keep 2 or 3 working Kernels? If so, why would the install put all those Kernels on; why not only the 3 most recent? I don't get it. :-\

Have a great day! :-)

Siran


Next 20

©2025 Astroinformatics Group