Sadly I will always show errors since I have many tasks that were stranded by the database crash a while back. Unless they scrub the database completely clean and start fresh, I will always have task errors.

Hi Keith,

I don't remember a database crash. The only outages I show are the one in May when the network hack happened and one back in late January/early February which I don't remember a cause for. The database crash you speak of must have happened before I came back to Milkyway on December 28, 2020. Is that when?

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Sadly I will always show errors since I have many tasks that were stranded by the database crash a while back. Unless they scrub the database completely clean and start fresh, I will always have task errors.

Hi Keith,

I don't remember a database crash. The only outages I show are the one in May when the network hack happened and one back in late January/early February which I don't remember a cause for. The database crash you speak of must have happened before I came back to Milkyway on December 28, 2020. Is that when?

Have a great day! :)

Siran

Mine are like this one, I have 4 of these:
1886911 2138086335 830321 1 Feb 2021, 20:32:56 UTC 2 Feb 2021, 5:34:58 UTC Completed, waiting for validation 562.79 210.18 pending Milkyway@home Separation v1.46 (opencl_nvidia_101)
windows_x86_64

or this one, I have 2 of these:
178592 2139699024 827464 21 Jan 2021, 21:14:26 UTC 22 Jan 2021, 5:36:40 UTC Validate error 2,848.52 560.24 --- Milkyway@home Separation v1.46 (opencl_nvidia_101)
x86_64-pc-linux-gnu

I have not crunched MW for months and still have over 800 work units mostly from January showing
all the more recent ones have cleared out
they don't get in the way so I wont bother about it
if this is repeated across the project they could shrink the database a good bit if the have a clean out

I don't remember a database crash. The only outages I show are the one in May when the network hack happened and one back in late January/early February which I don't remember a cause for. The database crash you speak of must have happened before I came back to Milkyway on December 28, 2020. Is that when?

Have a great day! :)

Siran

Nope the crash in February that orphaned a lot of tasks after the database rebuild.

https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4698&postid=70508

Caused by the work unit generator running out of 2^32 counts for task ID's
Same issue that SETI had to deal with back in 2015 and needed to increase the number generator limits.

---

Nope the crash in February that orphaned a lot of tasks after the database rebuild.

Hi Keith,

Ok, that's the one that shows on my BM Statistics tab. Got it! :-)

Now I have a BUNCH of erred tasks again. Total was 364, but it's going down. I think something happened weirdly that day for some strange reason with the PC. I don't know what it was. I'm kinda thinkin' it had something to do with my keyboard swap the other day. I was installing some Linux software that controls the current board. The installations were done through the terminal. I think that was when the errors happened. Oh well, things are back to "normal" now. ;-)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

erroring out tasks isn't a big deal to a wingman unless they are returned way late, but before the server releases a new one. On this particular project, it's hard to actually hurt your wingman. I mean you can but the WUs are so quick and numerous your wingman is going to move onto tons of other work and won't flinch.

erroring out tasks isn't a big deal to a wingman unless they are returned way late, but before the server releases a new one. On this particular project, it's hard to actually hurt your wingman. I mean you can but the WUs are so quick and numerous your wingman is going to move onto tons of other work and won't flinch.

Hi MC,

The only harm to a wingman is that they will have to wait longer for credit as someone else has to work on the task and finish without any errors.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

Well, guys and gals, I decided to throw in the towel, so-to-speak.

Just over 21 years ago I got into this because of SETI@Home. Since SETI shut down I decided to come back here.

Today I decided to take the stress off of my CPU and GPU and went NNT here. I'll finish what tasks I currently have and stop distributed computing. If SETI should come back I shall return there. If not, my PC will have a major sigh of relief.

It has been a wonderful time donating my PC(s) time to science.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

Well, guys and gals, I decided to throw in the towel, so-to-speak.

Just over 21 years ago I got into this because of SETI@Home. Since SETI shut down I decided to come back here.

Today I decided to take the stress off of my CPU and GPU and went NNT here. I'll finish what tasks I currently have and stop distributed computing. If SETI should come back I shall return there. If not, my PC will have a major sigh of relief.

It has been a wonderful time donating my PC(s) time to science.

Have a great day! :)

Siran

I am very sorry to hear that!!! We will miss you and your wit!!!

Greetings,

Of all the mean and nasty things to do to a person running Linux!

I had a Linux kernel and firmware update yesterday. Did them, among 2 or 3 other updates, and of course the update program said to reboot for the new kernel to be loaded at boot time. Ok, done this before, and instead of booting back into Linux Mint, I booted into Winders 10 to play Final Fantasy XIV. Got done playing and went to boot into Linux and BOOM!

Resolution is lower than 1024 x 768 and the login screen freezes! Cannot type and mouse will not work! I tried the trick of holding down the "shift" key while booting and Grub does NOT show up; It goes right into loading and freezing at the login screen. I have used my USB drive to log into Linux Mint 18 point something or other. As a matter of fact, I'm typing this in Firefox on this Mint version.

I have been all over the Internet trying to find SOMETHING that will get my Mint 20.2 back; reinstalling Grub, changing the default whatever it was from 0 to 1 so that it would load the previous version of the Kernel, looking into adding to the fstab file so that I can mount to the NVMe drive. Funny thing is, GParted, fdisk, lsblk and blkid all see all drives, but the file manager does not.

I can go into Winders 10 and copy folders/files over to my HDD and do a complete reinstall of Linux Mint, but I was hoping that there is perhaps something else I can do to fix this that I have not found on the Internet. By the way, I'm kicking myself for not doing a, what's it called, snapshot of the current, before I did the updates. I should probably look into that for when I have Kernel updates from now on. ;-)

If anyone has any ideas and/or tricks that I have yet to find, PLEASE let me know. Except for the folder/file copying, I'm gonna hold off on a reinstall of Linux Mint 20.2 for a day or 2.

Sorry for this post being so long, but I figured more information was better. ;-)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Keep trying to get to the grub menu with the SHIFT key at boot. Try to catch it a second before the BIOS splash screen disappears.
Use the grub recovery menu.
Or . . . just edit the /etc/default/grub file from your Live USB stick, add nomodeset to the kernel command line and mount your Ubuntu partition so you can do the update-grub.

---

Keep trying to get to the grub menu with the SHIFT key at boot. Try to catch it a second before the BIOS splash screen disappears.
Use the grub recovery menu.
Or . . . just edit the /etc/default/grub file from your Live USB stick, add nomodeset to the kernel command line and mount your Ubuntu partition so you can do the update-grub.

Hi Keith,

I keep trying the SHIFT key approach and nothing; Grub just won't come up. As for editing anything, I cannot mount any of the drives for editing. I use Nano in terminal and terminal keeps saying that it cannot find the drive(s) in fstab. I looked into adding and it is one long drawn out process. Anything edited on the USB drive is not maintained either.

So, I have decided that I'll just do a clean install of Mint 20.2. I've already copied folders with files for Mint over to my data drive. I've downloaded Mint 20.2 and will have to log into Winders to put it on my USB drive, if I cannot find a way to do it here in... No, I don't think that would be a good idea, I'll just do it in Winders. I have a utility (cannot remember it's name off hand) for this purpose. I've used it for putting both Winders and Linux Mint on USB drives. I just cannot remember it's name, but will know it when I see it. I think it's something like Lucas or Rufus or something like that. Oh well... :-)

It would be good to only maintain 2 or 3 older working Kernels, right? I was sitting for a long time waiting for whatever the new Kernel update was doing to my 26 or so old Kernels. Speaking of Kernels, what would be the likeliness of me getting that Kernel that screwed something up?

Have a great day! :-)

Siran

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Hi Keith,

Well I'll be dipped in honey!

My last install of Linux Mint did not have the Grub OS selector show up. Now I have one which means IT'S WORKING!!! :-)

I'm now busy making the settings changes I had before. Woohoo!!!

Have a great day! :-)

Siran

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

If I read your next to last post correctly, you are keeping 26 older kernels in your grub file. Why?????
That would lead to an extremely bloated grub menu.
Normal practice is to let grub manage itself and the apt update process prune the backup kernels to only around 3 deep.
No reason to keep more.

---

If I read your next to last post correctly, you are keeping 26 older kernels in your grub file. Why?????
That would lead to an extremely bloated grub menu.
Normal practice is to let grub manage itself and the apt update process prune the backup kernels to only around 3 deep.
No reason to keep more.

Hi Keith,

Yeah, I haven't figured out how to get them deleted and only keep 3. I'm gonna check the Internet on that to find out.

I also forgot to mention in my last post that I have 5.4.0-88.99 Kernel again. I did a bunch of updates but did NOT update the Kernel. I also have the Timeshift set up with a current Snapshot. Do you think I would have the same problem doing the Kernel update again?

Have a great day! :-)

Siran

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

The standard method of removing old updates is via the apt mechanism. Run these commands after you do the apt update
sudo apt autoremove
sudo apt autoclean

You can also remove old package configuration files for the kernel updates via the Synaptic Manager menu. I would certainly do that to remove all the old cruft you have accumulated and might be the cause for your latest kernel update stumble.

I would try again as long as you have a Live USB recovery plan.

---

The standard method of removing old updates is via the apt mechanism. Run these commands after you do the apt update
sudo apt autoremove
sudo apt autoclean

You can also remove old package configuration files for the kernel updates via the Synaptic Manager menu. I would certainly do that to remove all the old cruft you have accumulated and might be the cause for your latest kernel update stumble.

I would try again as long as you have a Live USB recovery plan.

Hi Keith,

This is weird! Everything was just fine and dandy, when I rebooted in Winders. When I was done I booted into Linux and I get the message in the upper right corner that tells me that I have no hardware acceleration and to load the Driver Manager so I did. It was running on NVIDIA v470 when I first switched from the novue or whatever it is called. So I switched to the NVIDIA v460 driver and I get the same thing. I tried to load the NVIDIA settings (for both versions) and all I get is the "Quit" box. Go figure!

The system is now running like I was running BOINC on the Intel video. Real herky jerky!

When it boots into Linux, I see a message that there was an error with the PCIe something but says it was corrected. The message goes by really fast. I'm wondering now if my video card is taking a dump on me or perhaps something blew on the PCIe lane(s). :-( I did run BOINC on the card for both SETI and Milkyway. I even think I ran it on a couple other projects too.

I'm gonna hold off on the Kernel update until I get this PC figured out. Thing is, everything was just fine when I was in Winders and playing Final Fantasy XIV. When I first switched to NVIDIA v470 and rebooted, I didn't get the message about the lack of hardware acceleration. Any ideas? Maybe build a new PC? lol :-)

Have a great day! :-)

Siran

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Sounds like the PC is straddling both the Nouveau and Nvidia drivers at the same time.
You can see what the error with the PCIE was with:

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

I would purge the Nvidia drivers and revert to Nouveau drivers to establish a baseline.
If there is still the same issue with the Nouveau drivers then I would start suspecting hardware issues.
If the Nouveau drivers behave themselves and your Desktop loads and runs correctly with the expected response, then try the Nvidia drivers again.

How are you getting the Nvidia drivers? Through the distro or through Nvidia or through the graphics-drivers PPA?

---

Sounds like the PC is straddling both the Nouveau and Nvidia drivers at the same time.

Hi Keith,

Funny you should mention that... Last night I got the idea to go back to the Nouveau driver and then go back to the NVIDIA v460 driver after the reboot. Voila! I did it this morning and it worked. I went into the display settings before I did this and saw that the display was set to Laptop and no other choices. That is what I kept getting with NVIDIA v470. The display setting is now showing my Acer monitor. NVIDIA settings come up now too. Do you think I should try going to the v470 driver again? I'm a bit reluctant to do that since even with my last Mint install I had problems with it.

I'm using the driver from the Distro.

Now, back to the Kernel problem. I gotta do a new Snapshot first before I do ANYTHING. Don't want the video problem again if things go wonky again. I tried those 2 commands you posted and all those Kernel files still exist. More Internet searches me thinks. ;-)

Thanks for the help and suggestions, Keith! :-)

Have a great day! :-)

Siran

---

CAPT Siran d'Vel'nahr XO - L L & P _\\//
USS Vre'kasht NCC-33187
Winders 10 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

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.

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.

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

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

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.

---