From: ronb02NOSPAM@gmail.com   
      
   On 2026-02-13, CrudeSausage  wrote:   
   > On Fri, 13 Feb 2026 09:12:28 -0000 (UTC), RonB wrote:   
   >   
   >> On 2026-02-12, CrudeSausage  wrote:   
   >>> On Thu, 12 Feb 2026 03:49:40 -0000 (UTC), RonB wrote:   
   >>>   
   >>>> On 2026-02-12, CrudeSausage  wrote:   
   >>>>> On 11 Feb 2026 20:30:44 GMT, rbowman wrote:   
   >>>>>   
   >>>>>> On Wed, 11 Feb 2026 10:39:19 -0000 (UTC), RonB wrote:   
   >>>>>>   
   >>>>>>   
   >>>>>>> In Linux Mint, you can do this is in Update Manager. When you see   
   >>>>>>> the kernel that is going to be updated, you right-click on the   
   >>>>>>> square beside it and choose either "Ignore the current update for   
   >>>>>>> this package." Or "Ignore all future updates for this package."   
   >>>>>>   
   >>>>>> I seldom use the GUI in any distro. In this case 'sudo apt upgrade'   
   >>>>>> failed trying to install the 6.17 kernel. I id open Update Manager   
   >>>>>> but the kernel packages had been downloaded and didn't show.   
   >>>>>>>   
   >>>>>>> apt-mark is supposed to allow you to hold and showhold, etc., but   
   >>>>>>> so far I can't get "sudo apt-mark showhold" to return anything,   
   >>>>>>> even though I've specifically held back a kernel to test it in   
   >>>>>>> Update Manager. (Probably have to hold the file in apt-mark to see   
   >>>>>>> it in apt-mark showhold.)   
   >>>>>>   
   >>>>>> showhold shows the four kernel packages. Again it doesn't seem to   
   >>>>>> work if the packages are already on the machine. I've used the   
   >>>>>> equivalent on Fedora to block VS Code updates. The update site is   
   >>>>>> very slow and often times out. Most of the Code updates have been AI   
   >>>>>> slop I don't want anyway.   
   >>>>>>   
   >>>>>> Similarly that works for 'sudo dnf update'. However Discover, the   
   >>>>>> Fedora version of Update Manager still shows an update available on   
   >>>>>> the taskbar. Minor annoyance since I don't use Discover.   
   >>>>>>   
   >>>>>>> Agree on Broadcom. Whenever I rebuild a laptop that has a Broadcom   
   >>>>>>> WiFi card, I look on eBay for a cheap Intel one. I don't even want   
   >>>>>>> to mess with Broadcom.   
   >>>>>>   
   >>>>>> I probably should have when I replaced the HDD with a SSD but It was   
   >>>>>> working after the initial installation. There's a limit on what I'll   
   >>>>>> spend on a 15 year old netbook that wasn't a ball of fire to begin   
   >>>>>> with.   
   >>>>>>   
   >>>>>>   
   >>>>>>> So these kernel issues are all related to Broadcom WiFi cards? My   
   >>>>>>> Firefox locked up twice on me using this computer (21.3, 5.15   
   >>>>>>> kernel)   
   >>>>>>> so I dropped back to an earlier 5.15 kernel. It hasn't locked up   
   >>>>>>> since,   
   >>>>>>> but Firefox was also updated so it could have been a Firefox issue.   
   >>>>>>>   
   >>>>>>>   
   >>>>>> The post I saw on Reddit all seemed to be the Broadcom module in   
   >>>>>> this case. Overall Nvidia seems to be the major PITA when the kernel   
   >>>>>> updates.   
   >>>>>> Fortunately I am Nvidia free.   
   >>>>>   
   >>>>> I can confirm that NVIDIA seems to have been behind the problem which   
   >>>>> led to corruption and a need to repair my Pop_OS! installation. I am   
   >>>>> shocked at how simple it was to fix though.   
   >>>>   
   >>>> Maybe both then. Nvidia is like a constant issue. When I had a Nvidia   
   >>>> card I just ran the generic Nouveau driver. Worked for what I needed.   
   >>>   
   >>> I would use Nouveau, but it's only okay for cards which don't have a   
   >>> locked firmware. That means that you need a chip older than the 9xx   
   >>> series from 2014.   
   >>   
   >> I didn't know that. The computer I had Nouveau on was probably made   
   >> around 2010 (if not earlier).   
   >   
   > Then Nouveau probably offered excellent or perfect support for the GPU   
   > there and you were better off using it over proprietary drivers. I am   
   > actually looking forward for the inevitable day when NVIDIA stops locking   
   > its GPU firmware so that open-source developers can improve their drivers   
   > the way that they did with AMD's. It is truly pointless for people to use   
   > Windows if they have an AMD GPU for gaming because the experience is   
   > almost always superior in Linux.   
      
   I stay away from trying to help people with gaming in Linux because I have   
   no clue. Some people it works okay in Linux, but I'm pretty that's   
   completely true.   
      
   --   
   "Not just insane... Trump insane."   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)