• LM 21.3 fails to boot after updates

    From Axel@none@not.here to alt.os.linux.mint on Sun Nov 8 10:31:56 2026
    From Newsgroup: alt.os.linux.mint


    after doing the latest updates on a LM 21.3 machine it fails to boot-
    flashing cursor after initial bootup and the LM logo. I-a tried normal
    and recovery modes using an earlier kernel, but they didn't work, so I restored using timeshift. I tried the updates again, and got the same
    result, so it's presently in the 'flashing cursor' state. I can restore
    it again using Timeshift (hopefully), but then i wont be able to upgrade
    it. what to do?-a :(
    --
    Linux Mint 22.3

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.os.linux.mint on Sat Nov 7 23:59:59 2026
    From Newsgroup: alt.os.linux.mint

    On Sun, 8 Nov 2026 10:31:56 +1100, Axel wrote:

    after doing the latest updates on a LM 21.3 machine it fails to
    boot- flashing cursor after initial bootup and the LM logo.

    Any boot messages? Tried any recovery modes (e.g. single-user)?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Axel@none@not.here to alt.os.linux.mint on Sun Nov 8 11:19:04 2026
    From Newsgroup: alt.os.linux.mint

    Lawrence DrCOOliveiro wrote:
    On Sun, 8 Nov 2026 10:31:56 +1100, Axel wrote:

    after doing the latest updates on a LM 21.3 machine it fails to
    boot- flashing cursor after initial bootup and the LM logo.
    Any boot messages?

    nope

    Tried any recovery modes (e.g. single-user)?

    I don't know what that means. I-a tried normal and recovery modes using
    an earlier kernel (as I said) but they didn't work
    --
    Linux Mint 22.3

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.os.linux.mint on Sat Nov 7 19:30:41 2026
    From Newsgroup: alt.os.linux.mint

    On Sat, 11/7/2026 6:59 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 8 Nov 2026 10:31:56 +1100, Axel wrote:

    after doing the latest updates on a LM 21.3 machine it fails to
    boot- flashing cursor after initial bootup and the LM logo.

    Any boot messages? Tried any recovery modes (e.g. single-user)?


    If the boot options include "quiet splash" from the original
    install, you can edit these in the grub boot menu. You should
    have the menu turned on at all times. Why ? Because of days
    like this. *Never* let a computer obscure stuff... or else.

    And since the OP mentions

    "I tried normal and recovery modes using
    an earlier kernel, but they didn't work"

    We know the menu lines are available to be edited.
    Remove the quiet and splash and see where it is stuck.

    I had something get stuck just the other day on the Big Machine,
    but I neglected to take a picture of this with my camera.

    *******

    A web reference suggests:

    press e to edit commands before booting
    search & replace "quiet splash" with "nomodeset"
    Mint preview desktop starts
    Connect to internet
    Run driver manager > after it checks download nVidia drive

    Now, that doesn't always work, as Driver Manager now becomes
    confused by the available NVidia drivers versus kernel version
    and it will report that the best driver is already there or
    that no driver is needed.

    But at least if you get that far, you're not dead in the water,
    merely inconvenienced.

    I lose track of these things, but I think I got tempted to try a
    HWE kernel, and instead of making a small jump, it installed 7.0.0 kernel, which was never going to work with an old video card :-)

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Axel@none@not.here to alt.os.linux.mint on Sun Nov 8 12:59:51 2026
    From Newsgroup: alt.os.linux.mint

    Paul wrote:
    On Sat, 11/7/2026 6:59 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 8 Nov 2026 10:31:56 +1100, Axel wrote:

    after doing the latest updates on a LM 21.3 machine it fails to
    boot- flashing cursor after initial bootup and the LM logo.
    Any boot messages? Tried any recovery modes (e.g. single-user)?

    If the boot options include "quiet splash" from the original
    install, you can edit these in the grub boot menu. You should
    have the menu turned on at all times. Why ? Because of days
    like this. *Never* let a computer obscure stuff... or else.

    And since the OP mentions

    "I tried normal and recovery modes using
    an earlier kernel, but they didn't work"

    We know the menu lines are available to be edited.
    Remove the quiet and splash and see where it is stuck.

    I had something get stuck just the other day on the Big Machine,
    but I neglected to take a picture of this with my camera.

    *******

    A web reference suggests:

    press e to edit commands before booting
    search & replace "quiet splash" with "nomodeset"
    Mint preview desktop starts
    Connect to internet
    Run driver manager > after it checks download nVidia drive

    sorry, I forgot to mention I did this, but it still won't boot


    Now, that doesn't always work, as Driver Manager now becomes
    confused by the available NVidia drivers versus kernel version
    and it will report that the best driver is already there or
    that no driver is needed.

    But at least if you get that far, you're not dead in the water,
    merely inconvenienced.

    I lose track of these things, but I think I got tempted to try a
    HWE kernel, and instead of making a small jump, it installed 7.0.0 kernel, which was never going to work with an old video card :-)

    I'll try again with an older kernel still than I used


    Paul
    --
    Linux Mint 22.3

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Axel@none@not.here to alt.os.linux.mint on Sun Nov 8 13:02:02 2026
    From Newsgroup: alt.os.linux.mint

    Axel wrote:
    Paul wrote:
    On Sat, 11/7/2026 6:59 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 8 Nov 2026 10:31:56 +1100, Axel wrote:

    after doing the latest updates on a LM 21.3 machine it fails to
    boot- flashing cursor after initial bootup and the LM logo.
    Any boot messages? Tried any recovery modes (e.g. single-user)?

    If the boot options include "quiet splash" from the original
    install, you can edit these in the grub boot menu. You should
    have the menu turned on at all times. Why ? Because of days
    like this. *Never* let a computer obscure stuff... or else.

    And since the OP mentions

    -a-a-a "I tried normal and recovery modes using
    -a-a-a-a an earlier kernel, but they didn't work"

    We know the menu lines are available to be edited.
    Remove the quiet and splash and see where it is stuck.

    I had something get stuck just the other day on the Big Machine,
    but I neglected to take a picture of this with my camera.

    *******

    A web reference suggests:

    -a-a-a press e to edit commands before booting
    -a-a-a search & replace "quiet splash" with "nomodeset"
    -a-a-a Mint preview desktop starts
    -a-a-a Connect to internet
    -a-a-a Run driver manager > after it checks download nVidia drive

    sorry, I forgot to mention I did this, but it still won't boot


    Now, that doesn't always work, as Driver Manager now becomes
    confused by the available NVidia drivers versus kernel version
    and it will report that the best driver is already there or
    that no driver is needed.

    But at least if you get that far, you're not dead in the water,
    merely inconvenienced.

    I lose track of these things, but I think I got tempted to try a
    HWE kernel, and instead of making a small jump, it installed 7.0.0
    kernel,
    which was never going to work with an old video card :-)

    I'll try again with an older kernel still than I used

    but then.. how will that help. because after I do all the updates I'll
    be back to square one, won't I?



    -a-a-a Paul


    --
    Linux Mint 22.3

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Gordon@Gordon@leaf.net.nz to alt.os.linux.mint on Sun Nov 8 02:15:00 2026
    From Newsgroup: alt.os.linux.mint

    On 2026-11-07, Axel <none@not.here> wrote:

    after doing the latest updates on a LM 21.3 machine it fails to boot- flashing cursor after initial bootup and the LM logo. I-a tried normal
    and recovery modes using an earlier kernel, but they didn't work, so I restored using timeshift. I tried the updates again, and got the same result, so it's presently in the 'flashing cursor' state. I can restore
    it again using Timeshift (hopefully), but then i wont be able to upgrade
    it. what to do?-a :(


    Got a TimeShift back up? Yes? then fire it up and follow the instructions on the screen.

    You will need a live USB boot to TimeShift, as your machine does not boot
    up.

    Plenty of videos on You Tube.

    Timeshift has got me out of many a hole. Works a treat.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Axel@none@not.here to alt.os.linux.mint on Sun Nov 8 15:46:49 2026
    From Newsgroup: alt.os.linux.mint

    Gordon wrote:
    On 2026-11-07, Axel <none@not.here> wrote:
    after doing the latest updates on a LM 21.3 machine it fails to boot-
    flashing cursor after initial bootup and the LM logo. I-a tried normal
    and recovery modes using an earlier kernel, but they didn't work, so I
    restored using timeshift. I tried the updates again, and got the same
    result, so it's presently in the 'flashing cursor' state. I can restore
    it again using Timeshift (hopefully), but then i wont be able to upgrade
    it. what to do?-a :(

    Got a TimeShift back up?

    yes, used it as I said in my post above

    Yes? then fire it up and follow the instructions on
    the screen.

    You will need a live USB boot to TimeShift, as your machine does not boot
    up.

    I use a live DVD as some machines don't boot from USB sticks


    Plenty of videos on You Tube.

    Timeshift has got me out of many a hole. Works a treat.
    --
    Linux Mint 22.3

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.os.linux.mint on Sun Nov 8 00:33:27 2026
    From Newsgroup: alt.os.linux.mint

    On Sat, 11/7/2026 9:02 PM, Axel wrote:
    Axel wrote:
    Paul wrote:
    On Sat, 11/7/2026 6:59 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 8 Nov 2026 10:31:56 +1100, Axel wrote:

    after doing the latest updates on a LM 21.3 machine it fails to
    boot- flashing cursor after initial bootup and the LM logo.
    Any boot messages? Tried any recovery modes (e.g. single-user)?

    If the boot options include "quiet splash" from the original
    install, you can edit these in the grub boot menu. You should
    have the menu turned on at all times. Why ? Because of days
    like this. *Never* let a computer obscure stuff... or else.

    And since the OP mentions

    -a-a-a "I tried normal and recovery modes using
    -a-a-a-a an earlier kernel, but they didn't work"

    We know the menu lines are available to be edited.
    Remove the quiet and splash and see where it is stuck.

    I had something get stuck just the other day on the Big Machine,
    but I neglected to take a picture of this with my camera.

    *******

    A web reference suggests:

    -a-a-a press e to edit commands before booting
    -a-a-a search & replace "quiet splash" with "nomodeset"
    -a-a-a Mint preview desktop starts
    -a-a-a Connect to internet
    -a-a-a Run driver manager > after it checks download nVidia drive

    sorry, I forgot to mention I did this, but it still won't boot


    Now, that doesn't always work, as Driver Manager now becomes
    confused by the available NVidia drivers versus kernel version
    and it will report that the best driver is already there or
    that no driver is needed.

    But at least if you get that far, you're not dead in the water,
    merely inconvenienced.

    I lose track of these things, but I think I got tempted to try a
    HWE kernel, and instead of making a small jump, it installed 7.0.0 kernel, >>> which was never going to work with an old video card :-)

    I'll try again with an older kernel still than I used

    but then.. how will that help. because after I do all the updates I'll be back to square one, won't I?

    While broken, you want to do "something" so you can boot into the OS.
    It's much easier to work on an OS, if you can boot into it,
    and nicer still if the GUI comes up. While you can chroot in with
    a Live media, the question then would be what exactly could you
    do at that point, which is clever enough to fix it. When you use Live media, you don't have to chroot in, but chroot is used for things like boot repair.

    You've got:

    1) A distro with an original kernel version.
    2) At some point, the kernel version jumped, and for some people
    that was enough to cause DKMS preparation of the selected NVidia
    driver to fail. If the folks had stayed on Nouveau, that might not
    have happened, but that isn't the most pleasant choice on older machines
    (slower). I've probably been in the bind you're in now, several times
    thanks to NVidia. In one case, I had to delete a bunch of packages in
    Synaptic, so that the Driver Manager could offer some "sane choices".
    3) If you further issue the command to enable the HWE kernel, that
    makes a further kernel version jump (7.0.0), which pretty well guarantees an NVidia
    card using the Nvidia driver is going to break.

    You can try nomodeset to get around where you are at now.

    The Nouveau driver has likely been blacklisted. There will
    be a blacklist file, in a directory ending in ".d" that
    will have a single line in it listing "nouveau" to be blacklisted.
    If nouveau was not blacklisted, it could take over as a driver
    in place of the (now nonexistent) DKMS Nvidia driver.

    You could hunt for that file, while booted from Live media.
    But I don't know if that is sufficient to do the job or not,
    as I don't know exactly what the Driver Manager does during
    a boot (if anything).

    When the Driver Manager no longer shows any entries,
    it's "no longer your friend". Whether Clem is supposed to
    fix this, or Ubuntu is supposed to fix this, I can't guess.

    *******

    I could try simulating this, but I don't know if I can match where you
    are right now, close enough to do the job. I would not do that in
    a VM, as the situation requires an NVidia video card as a physical thing.
    I would do an install with the network cable disconnected, then allow
    the updater to see the possibility of updates.

    You could help by listing:

    1) (New) kernel version that is broken. 6.14 maybe ?
    2) (Previous) kernel or two. Was it 6.8.xxx ?
    3) Model of Nvidia card.

    You probably don't have an AMD card right now, as that
    would use AMDGPU which is apparently in the kernel (so it
    is not a candidate for DKMS breakage). I have a machine
    with an AMD card (RX 9060 XT) and the older machine with
    NVidia GTX1080 in it.

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Axel@none@not.here to alt.os.linux.mint on Sun Nov 8 20:02:38 2026
    From Newsgroup: alt.os.linux.mint

    Paul wrote:
    On Sat, 11/7/2026 9:02 PM, Axel wrote:
    Axel wrote:
    Paul wrote:
    On Sat, 11/7/2026 6:59 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 8 Nov 2026 10:31:56 +1100, Axel wrote:

    after doing the latest updates on a LM 21.3 machine it fails to
    boot- flashing cursor after initial bootup and the LM logo.
    Any boot messages? Tried any recovery modes (e.g. single-user)?

    If the boot options include "quiet splash" from the original
    install, you can edit these in the grub boot menu. You should
    have the menu turned on at all times. Why ? Because of days
    like this. *Never* let a computer obscure stuff... or else.

    And since the OP mentions

    -a-a-a "I tried normal and recovery modes using
    -a-a-a-a an earlier kernel, but they didn't work"

    We know the menu lines are available to be edited.
    Remove the quiet and splash and see where it is stuck.

    I had something get stuck just the other day on the Big Machine,
    but I neglected to take a picture of this with my camera.

    *******

    A web reference suggests:

    -a-a-a press e to edit commands before booting
    -a-a-a search & replace "quiet splash" with "nomodeset"
    -a-a-a Mint preview desktop starts
    -a-a-a Connect to internet
    -a-a-a Run driver manager > after it checks download nVidia drive
    sorry, I forgot to mention I did this, but it still won't boot

    Now, that doesn't always work, as Driver Manager now becomes
    confused by the available NVidia drivers versus kernel version
    and it will report that the best driver is already there or
    that no driver is needed.

    But at least if you get that far, you're not dead in the water,
    merely inconvenienced.

    I lose track of these things, but I think I got tempted to try a
    HWE kernel, and instead of making a small jump, it installed 7.0.0 kernel, >>>> which was never going to work with an old video card :-)
    I'll try again with an older kernel still than I used
    but then.. how will that help. because after I do all the updates I'll be back to square one, won't I?
    While broken, you want to do "something" so you can boot into the OS.
    It's much easier to work on an OS, if you can boot into it,
    and nicer still if the GUI comes up. While you can chroot in with
    a Live media, the question then would be what exactly could you
    do at that point, which is clever enough to fix it. When you use Live media, you don't have to chroot in, but chroot is used for things like boot repair.

    You've got:

    1) A distro with an original kernel version.
    2) At some point, the kernel version jumped, and for some people
    that was enough to cause DKMS preparation of the selected NVidia
    driver to fail. If the folks had stayed on Nouveau, that might not
    have happened, but that isn't the most pleasant choice on older machines
    (slower). I've probably been in the bind you're in now, several times
    thanks to NVidia. In one case, I had to delete a bunch of packages in
    Synaptic, so that the Driver Manager could offer some "sane choices".
    3) If you further issue the command to enable the HWE kernel, that
    makes a further kernel version jump (7.0.0), which pretty well guarantees an NVidia
    card using the Nvidia driver is going to break.

    You can try nomodeset to get around where you are at now.

    The Nouveau driver has likely been blacklisted. There will
    be a blacklist file, in a directory ending in ".d" that
    will have a single line in it listing "nouveau" to be blacklisted.
    If nouveau was not blacklisted, it could take over as a driver
    in place of the (now nonexistent) DKMS Nvidia driver.

    You could hunt for that file, while booted from Live media.
    But I don't know if that is sufficient to do the job or not,
    as I don't know exactly what the Driver Manager does during
    a boot (if anything).

    When the Driver Manager no longer shows any entries,
    it's "no longer your friend". Whether Clem is supposed to
    fix this, or Ubuntu is supposed to fix this, I can't guess.

    *******

    I could try simulating this, but I don't know if I can match where you
    are right now, close enough to do the job. I would not do that in
    a VM, as the situation requires an NVidia video card as a physical thing.
    I would do an install with the network cable disconnected, then allow
    the updater to see the possibility of updates.

    You could help by listing:

    1) (New) kernel version that is broken. 6.14 maybe ?
    2) (Previous) kernel or two. Was it 6.8.xxx ?
    3) Model of Nvidia card.

    the current kernel listed in Grub is 5.15.0-203
    I've also tried booting with 5.15.0-198, 157 and 151, without success

    this is the hardware (from System Info)

    -a Kernel: 5.15.0-91-generic x86_64 bits: 64 compiler: gcc v: 11.4.0
    Desktop: Cinnamon 6.0.4
    -a-a-a tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux
    Mint 21.3 Virginia
    -a-a-a base: Ubuntu 22.04 jammy
    Machine:
    -a Type: Desktop Mobo: ASRock model: 980DE3/U3S3 serial: <superuser
    required>
    -a-a-a BIOS: American Megatrends v: P2.00 date: 09/04/2015
    CPU:
    -a Info: 6-core model: AMD FX-6100 bits: 64 type: MT MCP smt: enabled
    arch: Bulldozer rev: 2 cache:
    -a-a-a L1: 288 KiB L2: 6 MiB L3: 8 MiB
    -a Speed (MHz): avg: 1109178 high: 1110599 min/max: 1400/3300 boost:
    enabled cores: 1: 1108953
    -a-a-a 2: 1110599 3: 1110557 4: 1108221 5: 1108475 6: 1108265 bogomips: 31318379
    -a Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics:
    -a Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: ASUSTeK driver:
    nouveau v: kernel pcie:
    -a-a-a speed: 2.5 GT/s lanes: 4 ports: active: HDMI-A-1 empty: DVI-D-1 bus-ID: 01:00.0
    -a-a-a chip-ID: 10de:1d01 class-ID: 0300
    -a Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa
    -a-a-a gpu: nouveau display-ID: :0 screens: 1
    -a Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9")
    -a Monitor-1: HDMI-1 mapped: HDMI-A-1 model: Asus VP247 serial: <filter>
    res: 1920x1080 hz: 60
    -a-a-a dpi: 94 size: 521x293mm (20.5x11.5") diag: 598mm (23.5") modes:
    max: 1920x1080 min: 720x400
    -a OpenGL: renderer: NV138 v: 4.3 Mesa 23.0.4-0ubuntu1~22.04.1 direct
    render: Yes
    Audio:
    -a Device-1: AMD SBx00 Azalia driver: snd_hda_intel v: kernel bus-ID:
    00:14.2 chip-ID: 1002:4383
    -a-a-a class-ID: 0403
    -a Device-2: NVIDIA GP108 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
    -a-a-a pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 01:00.1 chip-ID: 10de:0fb8 class-ID: 0403
    -a Sound Server-1: ALSA v: k5.15.0-91-generic running: yes
    -a Sound Server-2: PulseAudio v: 15.99.1 running: yes
    -a Sound Server-3: PipeWire v: 0.3.48 running: yes
    Network:
    -a Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8169
    -a-a-a v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e800 bus-ID: 04:00.0 chip-ID: 10ec:8168
    -a-a-a class-ID: 0200
    -a IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
    Drives:
    -a Local Storage: total: 931.52 GiB used: 265.16 GiB (28.5%)
    -a ID-1: /dev/sda vendor: Western Digital model: WD5000AZLX-60K2TA0
    size: 465.76 GiB
    -a-a-a speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 1A01
    scheme: GPT
    -a ID-2: /dev/sdb type: USB vendor: LITE-ON model: UITRA1 size: 465.76
    GiB type: N/A
    -a-a-a serial: <filter> rev: 0108 scheme: MBR
    Partition:
    -a ID-1: / size: 7.8 GiB used: 793 MiB (9.9%) fs: overlay source: ERR-102 Swap:
    -a Alert: No swap data was found.
    USB:
    -a Hub-1: 1-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed:
    480 Mb/s chip-ID: 1d6b:0002
    -a-a-a class-ID: 0900
    -a Hub-2: 1-3:10 info: Terminus Hub ports: 4 rev: 2.0 speed: 480 Mb/s
    power: 100mA
    -a-a-a chip-ID: 1a40:0101 class-ID: 0900
    -a Device-1: 1-3.1:11 info: UGREEN Receiver type: Keyboard,Mouse,HID
    driver: hid-generic,usbhid
    -a-a-a interfaces: 3 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID:
    2b89:0043 class-ID: 0300
    -a-a-a serial: <filter>
    -a Device-2: 1-3.2:12 info: PCPlay Barcode PCP-BCG4209 type: Keyboard,Mouse
    -a-a-a driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s power: 400mA
    -a-a-a chip-ID: 13ba:0018 class-ID: 0301
    -a Device-3: 1-3.3:13 info: Canon PC-D300/FAX-L400/ICD300 type: Printer driver: usblp
    -a-a-a interfaces: 1 rev: 1.1 speed: 12 Mb/s power: 2mA chip-ID: 04a9:2634 class-ID: 0701
    -a-a-a serial: <filter>
    -a Hub-3: 2-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed:
    480 Mb/s chip-ID: 1d6b:0002
    -a-a-a class-ID: 0900
    -a Hub-4: 3-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12
    Mb/s chip-ID: 1d6b:0001
    -a-a-a class-ID: 0900
    -a Hub-5: 4-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12
    Mb/s chip-ID: 1d6b:0001
    -a-a-a class-ID: 0900
    -a Hub-6: 5-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12
    Mb/s chip-ID: 1d6b:0001
    -a-a-a class-ID: 0900
    -a Hub-7: 6-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12
    Mb/s chip-ID: 1d6b:0001
    -a-a-a class-ID: 0900
    -a Hub-8: 7-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12
    Mb/s chip-ID: 1d6b:0001
    -a-a-a class-ID: 0900
    -a Hub-9: 8-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s
    -a-a-a chip-ID: 1d6b:0002 class-ID: 0900
    -a Hub-10: 9-0:1 info: Super-speed hub ports: 4 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003
    -a-a-a class-ID: 0900
    -a Device-1: 9-3:2 info: JMicron / USA JMS578 SATA 6Gb/s type: Mass
    Storage driver: uas
    -a-a-a interfaces: 1 rev: 3.0 speed: 5 Gb/s power: 8mA chip-ID: 152d:0578 class-ID: 0806
    -a-a-a serial: <filter>
    Sensors:
    -a System Temperatures: cpu: 34.5 C mobo: N/A gpu: nouveau temp: 41.0 C
    -a Fan Speeds (RPM): N/A
    Repos:
    -a Packages: apt: 2120
    -a Active apt repos in: /etc/apt/sources.list
    -a-a-a 1: deb cdrom:[Linux Mint 21.3 _Virginia_ - Release amd64 20240109]/ jammy contrib main
    -a Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    -a-a-a 1: deb http: //packages.linuxmint.com virginia main upstream import backport
    -a-a-a 2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    -a-a-a 3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main
    restricted universe multiverse
    -a-a-a 4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    -a-a-a 5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
    Info:
    -a Processes: 230 Uptime: 38m wakeups: 0 Memory: 15.6 GiB used: 2.22 GiB (14.3%) Init: systemd
    -a v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Cinnamon
    v: 6.0.4 inxi: 3.3.13

    I've booted it with a live DVD. can you suggest anything?

    note; my knowledge of LM is limited


    You probably don't have an AMD card right now, as that
    would use AMDGPU which is apparently in the kernel (so it
    is not a candidate for DKMS breakage). I have a machine
    with an AMD card (RX 9060 XT) and the older machine with
    NVidia GTX1080 in it.

    Paul
    --
    Linux Mint 22.3

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Heinz Schmitz@sch@example.invalid to alt.os.linux.mint on Sun Nov 8 11:38:00 2026
    From Newsgroup: alt.os.linux.mint

    Axel wrote:
    I've booted it with a live DVD. can you suggest anything?
    I had a similar problem on ubuntu. After a short circuit in the power
    supply I was only presented a tty login screen that never accepted
    my password, and after a while only a blinking white line in the left
    upper corner of the screen.
    I suspected that the PC was not shut down correctly after the flash
    from the power supply. Live CD booted alright and the system seemed
    without other problems.
    I pulled all connections to hard disks and checked them one by one
    with gparted. Found a problem, corrected it, and everything ok again.
    He who heals is right. :-).
    Regards,
    H.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mike Easter@MikeE@ster.invalid to alt.os.linux.mint on Sun Nov 8 07:17:59 2026
    From Newsgroup: alt.os.linux.mint

    Axel wrote:
    I use a live DVD as some machines don't boot from USB sticks

    Apologies for this being off-topic to your thread issue; but I just
    wanted to remark on the above line.

    I have a machine that is 'contrary' or limited in its abilities to boot
    in a number of ways that I want it to.

    So, I put a Plop boot manager on a CD, I'm currently using his PBM6, and
    it allows me to boot from devices that the native bios won't, such as an
    added SSD, or of course USBs.

    I've been using Plop variants for years. Here's his table of managers: https://www.plop.at/en/bootmanagers.html
    --
    Mike Easter
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.os.linux.mint on Sun Nov 8 11:35:28 2026
    From Newsgroup: alt.os.linux.mint

    On Sun, 11/8/2026 4:02 AM, Axel wrote:
    Paul wrote:
    On Sat, 11/7/2026 9:02 PM, Axel wrote:
    Axel wrote:
    Paul wrote:
    On Sat, 11/7/2026 6:59 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 8 Nov 2026 10:31:56 +1100, Axel wrote:

    after doing the latest updates on a LM 21.3 machine it fails to
    boot- flashing cursor after initial bootup and the LM logo.
    Any boot messages? Tried any recovery modes (e.g. single-user)?

    If the boot options include "quiet splash" from the original
    install, you can edit these in the grub boot menu. You should
    have the menu turned on at all times. Why ? Because of days
    like this. *Never* let a computer obscure stuff... or else.

    And since the OP mentions

    -a-a-a-a "I tried normal and recovery modes using
    -a-a-a-a-a an earlier kernel, but they didn't work"

    We know the menu lines are available to be edited.
    Remove the quiet and splash and see where it is stuck.

    I had something get stuck just the other day on the Big Machine,
    but I neglected to take a picture of this with my camera.

    *******

    A web reference suggests:

    -a-a-a-a press e to edit commands before booting
    -a-a-a-a search & replace "quiet splash" with "nomodeset"
    -a-a-a-a Mint preview desktop starts
    -a-a-a-a Connect to internet
    -a-a-a-a Run driver manager > after it checks download nVidia drive
    sorry, I forgot to mention I did this, but it still won't boot

    Now, that doesn't always work, as Driver Manager now becomes
    confused by the available NVidia drivers versus kernel version
    and it will report that the best driver is already there or
    that no driver is needed.

    But at least if you get that far, you're not dead in the water,
    merely inconvenienced.

    I lose track of these things, but I think I got tempted to try a
    HWE kernel, and instead of making a small jump, it installed 7.0.0 kernel,
    which was never going to work with an old video card :-)
    I'll try again with an older kernel still than I used
    but then.. how will that help. because after I do all the updates I'll be back to square one, won't I?
    While broken, you want to do "something" so you can boot into the OS.
    It's much easier to work on an OS, if you can boot into it,
    and nicer still if the GUI comes up. While you can chroot in with
    a Live media, the question then would be what exactly could you
    do at that point, which is clever enough to fix it. When you use Live media, >> you don't have to chroot in, but chroot is used for things like boot repair. >>
    You've got:

    1) A distro with an original kernel version.
    2) At some point, the kernel version jumped, and for some people
    -a-a-a that was enough to cause DKMS preparation of the selected NVidia
    -a-a-a driver to fail. If the folks had stayed on Nouveau, that might not
    -a-a-a have happened, but that isn't the most pleasant choice on older machines
    -a-a-a (slower). I've probably been in the bind you're in now, several times >> -a-a-a thanks to NVidia. In one case, I had to delete a bunch of packages in >> -a-a-a Synaptic, so that the Driver Manager could offer some "sane choices". >> 3) If you further issue the command to enable the HWE kernel, that
    -a-a-a makes a further kernel version jump (7.0.0), which pretty well guarantees an NVidia
    -a-a-a card using the Nvidia driver is going to break.

    You can try nomodeset to get around where you are at now.

    The Nouveau driver has likely been blacklisted. There will
    be a blacklist file, in a directory ending in ".d" that
    will have a single line in it listing "nouveau" to be blacklisted.
    If nouveau was not blacklisted, it could take over as a driver
    in place of the (now nonexistent) DKMS Nvidia driver.

    You could hunt for that file, while booted from Live media.
    But I don't know if that is sufficient to do the job or not,
    as I don't know exactly what the Driver Manager does during
    a boot (if anything).

    When the Driver Manager no longer shows any entries,
    it's "no longer your friend". Whether Clem is supposed to
    fix this, or Ubuntu is supposed to fix this, I can't guess.

    *******

    I could try simulating this, but I don't know if I can match where you
    are right now, close enough to do the job. I would not do that in
    a VM, as the situation requires an NVidia video card as a physical thing.
    I would do an install with the network cable disconnected, then allow
    the updater to see the possibility of updates.

    You could help by listing:

    1) (New) kernel version that is broken.-a 6.14 maybe ?
    2) (Previous) kernel or two.-a-a-a-a-a-a-a-a-a-a-a-a Was it 6.8.xxx ?
    3) Model of Nvidia card.

    the current kernel listed in Grub is 5.15.0-203
    I've also tried booting with 5.15.0-198, 157 and 151, without success

    this is the hardware (from System Info)

    -a Kernel: 5.15.0-91-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
    -a-a-a tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
    -a-a-a base: Ubuntu 22.04 jammy
    Machine:
    -a Type: Desktop Mobo: ASRock model: 980DE3/U3S3 serial: <superuser required> -a-a-a BIOS: American Megatrends v: P2.00 date: 09/04/2015
    CPU:
    -a Info: 6-core model: AMD FX-6100 bits: 64 type: MT MCP smt: enabled arch: Bulldozer rev: 2 cache:
    -a-a-a L1: 288 KiB L2: 6 MiB L3: 8 MiB
    -a Speed (MHz): avg: 1109178 high: 1110599 min/max: 1400/3300 boost: enabled cores: 1: 1108953
    -a-a-a 2: 1110599 3: 1110557 4: 1108221 5: 1108475 6: 1108265 bogomips: 31318379
    -a Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics:
    -a Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: ASUSTeK driver: nouveau v: kernel pcie:
    -a-a-a speed: 2.5 GT/s lanes: 4 ports: active: HDMI-A-1 empty: DVI-D-1 bus-ID: 01:00.0
    -a-a-a chip-ID: 10de:1d01 class-ID: 0300
    -a Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa
    -a-a-a gpu: nouveau display-ID: :0 screens: 1
    -a Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9")
    -a Monitor-1: HDMI-1 mapped: HDMI-A-1 model: Asus VP247 serial: <filter> res: 1920x1080 hz: 60
    -a-a-a dpi: 94 size: 521x293mm (20.5x11.5") diag: 598mm (23.5") modes: max: 1920x1080 min: 720x400
    -a OpenGL: renderer: NV138 v: 4.3 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes
    Audio:
    -a Device-1: AMD SBx00 Azalia driver: snd_hda_intel v: kernel bus-ID: 00:14.2 chip-ID: 1002:4383
    -a-a-a class-ID: 0403
    -a Device-2: NVIDIA GP108 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
    -a-a-a pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 01:00.1 chip-ID: 10de:0fb8 class-ID: 0403
    -a Sound Server-1: ALSA v: k5.15.0-91-generic running: yes
    -a Sound Server-2: PulseAudio v: 15.99.1 running: yes
    -a Sound Server-3: PipeWire v: 0.3.48 running: yes
    Network:
    -a Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169
    -a-a-a v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e800 bus-ID: 04:00.0 chip-ID: 10ec:8168
    -a-a-a class-ID: 0200
    -a IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
    Drives:
    -a Local Storage: total: 931.52 GiB used: 265.16 GiB (28.5%)
    -a ID-1: /dev/sda vendor: Western Digital model: WD5000AZLX-60K2TA0 size: 465.76 GiB
    -a-a-a speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 1A01 scheme: GPT
    -a ID-2: /dev/sdb type: USB vendor: LITE-ON model: UITRA1 size: 465.76 GiB type: N/A
    -a-a-a serial: <filter> rev: 0108 scheme: MBR
    Partition:
    -a ID-1: / size: 7.8 GiB used: 793 MiB (9.9%) fs: overlay source: ERR-102 Swap:
    -a Alert: No swap data was found.
    USB:
    -a Hub-1: 1-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
    -a-a-a class-ID: 0900
    -a Hub-2: 1-3:10 info: Terminus Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
    -a-a-a chip-ID: 1a40:0101 class-ID: 0900
    -a Device-1: 1-3.1:11 info: UGREEN Receiver type: Keyboard,Mouse,HID driver: hid-generic,usbhid
    -a-a-a interfaces: 3 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 2b89:0043 class-ID: 0300
    -a-a-a serial: <filter>
    -a Device-2: 1-3.2:12 info: PCPlay Barcode PCP-BCG4209 type: Keyboard,Mouse -a-a-a driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s power: 400mA
    -a-a-a chip-ID: 13ba:0018 class-ID: 0301
    -a Device-3: 1-3.3:13 info: Canon PC-D300/FAX-L400/ICD300 type: Printer driver: usblp
    -a-a-a interfaces: 1 rev: 1.1 speed: 12 Mb/s power: 2mA chip-ID: 04a9:2634 class-ID: 0701
    -a-a-a serial: <filter>
    -a Hub-3: 2-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
    -a-a-a class-ID: 0900
    -a Hub-4: 3-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    -a-a-a class-ID: 0900
    -a Hub-5: 4-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    -a-a-a class-ID: 0900
    -a Hub-6: 5-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    -a-a-a class-ID: 0900
    -a Hub-7: 6-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    -a-a-a class-ID: 0900
    -a Hub-8: 7-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    -a-a-a class-ID: 0900
    -a Hub-9: 8-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
    -a-a-a chip-ID: 1d6b:0002 class-ID: 0900
    -a Hub-10: 9-0:1 info: Super-speed hub ports: 4 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003
    -a-a-a class-ID: 0900
    -a Device-1: 9-3:2 info: JMicron / USA JMS578 SATA 6Gb/s type: Mass Storage driver: uas
    -a-a-a interfaces: 1 rev: 3.0 speed: 5 Gb/s power: 8mA chip-ID: 152d:0578 class-ID: 0806
    -a-a-a serial: <filter>
    Sensors:
    -a System Temperatures: cpu: 34.5 C mobo: N/A gpu: nouveau temp: 41.0 C
    -a Fan Speeds (RPM): N/A
    Repos:
    -a Packages: apt: 2120
    -a Active apt repos in: /etc/apt/sources.list
    -a-a-a 1: deb cdrom:[Linux Mint 21.3 _Virginia_ - Release amd64 20240109]/ jammy contrib main
    -a Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    -a-a-a 1: deb http: //packages.linuxmint.com virginia main upstream import backport
    -a-a-a 2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    -a-a-a 3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    -a-a-a 4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    -a-a-a 5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
    Info:
    -a Processes: 230 Uptime: 38m wakeups: 0 Memory: 15.6 GiB used: 2.22 GiB (14.3%) Init: systemd
    -a v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Cinnamon v: 6.0.4 inxi: 3.3.13

    I've booted it with a live DVD. can you suggest anything?

    note; my knowledge of LM is limited

    The GT1030, there should still be a driver in Driver Manager for it.

    *******

    LM213 Fresh Install (Nouveau)

    System:
    Host: TUBASOLO Kernel: 5.15.0-91-generic x86_64 bits: 64
    Desktop: Cinnamon 6.0.4 Distro: Linux Mint 21.3 Virginia
    Graphics:
    Device-1: NVIDIA GP108 [GeForce GT 1030] driver: nouveau v: kernel
    Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting
    unloaded: fbdev,vesa gpu: nouveau resolution: 1920x1080~75Hz
    OpenGL: renderer: NV138 v: 4.3 Mesa 23.0.4-0ubuntu1~22.04.1

    ************************************************************************

    LM213 Want NVidia. No 535 in updated repo, use 545 as nearest to it. OK.

    System:
    Host: TUBASOLO Kernel: 5.15.0-91-generic x86_64 bits: 64
    Desktop: Cinnamon 6.0.4 Distro: Linux Mint 21.3 Virginia
    Graphics:
    Device-1: NVIDIA GP108 [GeForce GT 1030] driver: nvidia v: 545.29.06
    Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia
    resolution: 1920x1080~75Hz
    OpenGL: renderer: NVIDIA GeForce GT 1030/PCIe/SSE2
    v: 4.6.0 NVIDIA 545.29.06

    ************************************************************************

    LM213 Update Manager 1GB updates, new kernel, DKMS must be broken.
    When the kernel updates, it is still set up for 545.

    System:
    Host: TUBASOLO Kernel: 5.15.0-203-generic x86_64 bits: 64
    Desktop: Cinnamon 6.0.5 Distro: Linux Mint 21.3 Virginia
    Graphics:
    Device-1: NVIDIA GP108 [GeForce GT 1030] driver: N/A
    Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nouveau,vesa
    unloaded: fbdev,modesetting gpu: N/A resolution: 1920x1080~77Hz
    OpenGL: renderer: llvmpipe (LLVM 15.0.7 256 bits)
    v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.4

    /etc/modprobe.d/blacklist.conf <=== nothing relevant at the moment, nouveau not mentioned

    $ cat /etc/modprobe.d/nvidia-graphics-drivers-kms.conf
    # This file was generated by nvidia-driver-545
    # Set value to 0 to disable modesetting
    options nvidia-drm modeset=1

    Driver Manager has the following text.

    NVIDIA Corporation: GP108 [GeForce GT 1030]
    This device is using an alternative driver.

    nvidia-driver-470 (recommended) <===
    Version 470.256.02-Oubuntu0.22.04.6
    NVIDIA driver metapackage

    nvidia-driver-580
    Version 580.178.04-Oubuntu0.22.04.1
    NVIDIA driver metapackage

    nvidia-driver-545
    X Version 545.29.06-Oubuntu0.22.04.2
    NVIDIA driver metapackage <=== "was selected"

    nvidia-driver-390
    Version 390.157-Oubuntu0.22.04.2
    NVIDIA driver metapackage

    xserver-xorg-video-nouveau (open-source)
    Version 1:1.0.17-2build1
    X.Org X server - Nouveau display driver <=== "now using"

    I can find a reddit

    I'm aware I can boot in single-user (rescue) mode and e.g.

    apt uninstall nvidia-driver-515-open <=== not a binary blob
    apt install nvidia-driver-515 <=== binary blob, uses DMKS

    but I'd like to understand if there is specifically a "Mint way" of doing this.
    ...
    to remove the nvidia driver. try

    sudo apt purge nvidia* <=== assumes not many of total Nvidia packages are loaded
    looks reasonable, when I checked the list

    sudo apt install xserver-xorg-video-nouveau <=== (which is loaded on mine, already)

    # and additionally...

    sudo apt install nvidia-driver-470 <=== metapackage, includes xserver-xorg-video-nvidia-470

    You would probably have to blacklist nouveau, but
    as long as xserver-xorg-video-nouveau is still there,
    the GUI should come up, and when the blacklist nouveau
    is added, that should facilitate the 470 that was installed
    to take over. It's also possible the metapackage would do
    this anyway.

    To do that, you'd have to find the systemd recipe for
    changing boot mode. It's either that, or the "rescue mode"
    in the GRUB menu is going to do that. Before systemd,
    the run levels were numbers. Whereas systemd uses the
    name of the level, single user or multiuser. The single
    user is conceptually similar to how Windows has a Safe Mode
    (and a normal mode). Single-user mode is sometimes used
    for repairs. Assuming you can even get that far, and
    that should work, as like Safe Mode there is less baggage.

    https://askubuntu.com/questions/788323/how-do-i-change-the-runlevel-on-systemd

    "Mapping between runlevels and systemd targets
    roiroCroCroCroCroCroCroCroCroCroCroCroCro4roCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroE
    roeRunlevel roe Target roe
    roLroCroCroCroCroCroCroCroCroCroCroCroCro+roCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCron
    roe0 roe poweroff.target roe
    roLroCroCroCroCroCroCroCroCroCroCroCroCro+roCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCron
    roe1 roe rescue.target roe <=== single-user
    roLroCroCroCroCroCroCroCroCroCroCroCroCro+roCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCron
    roe2, 3, 4 roe multi-user.target roe
    roLroCroCroCroCroCroCroCroCroCroCroCroCro+roCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCron
    roe5 roe graphical.target roe <=== (normal usage ???)
    roLroCroCroCroCroCroCroCroCroCroCroCroCro+roCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCron
    roe6 roe reboot.target roe
    rooroCroCroCroCroCroCroCroCroCroCroCroCro|roCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroy

    Now, to just change the "runlevels" in 16.04, you can use for eg:

    sudo systemctl isolate multi-user.target

    To make this the default "runlevel", you can use:

    sudo systemctl enable multi-user.target
    sudo systemctl set-default multi-user.target <=== likely enough itself
    ...

    sudo systemctl start graphical.target
    sudo systemctl start multi-user.target
    "

    And here, it shows how to do it from the boot line.

    https://www.tecmint.com/boot-ubuntu-in-rescue-mode/

    quiet splash systemd.unit=rescue.target

    Not doing that on the next boot, would then likely run
    you at graphical.target (as it is likely the set-default right now).

    Paul

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.os.linux.mint on Sun Nov 8 18:56:54 2026
    From Newsgroup: alt.os.linux.mint

    On Sun, 11/8/2026 10:17 AM, Mike Easter wrote:
    Axel wrote:
    I use a live DVD as some machines don't boot from USB sticks

    Apologies for this being off-topic to your thread issue; but I just wanted to remark on the above line.

    I have a machine that is 'contrary' or limited in its abilities to boot in a number of ways that I want it to.

    So, I put a Plop boot manager on a CD, I'm currently using his PBM6, and it allows me to boot from devices that the native bios won't, such as an added SSD, or of course USBs.

    I've been using Plop variants for years.-a Here's his table of managers: https://www.plop.at/en/bootmanagers.html


    I can add some color commentary.

    Some machines had strange quirks, because the BIOS
    was written by the mobo/OEM company, and not by one of the Big BIOS companies. My Dell Optiplex 780 for example, it has USB boot capability,
    but only one USB stick should be connected, as the BIOS has
    no "steering capability". It's basically "boot from USB"
    but not *which* USB.

    The other trend, started like this. The Big BIOS company ensures
    anything on the Southbridge, has boot capability (will be in
    popup boot menu). Before USB2 was in the Southbridge, an outboard
    chip was used. And the outboard chip didn't have the required
    BIOS module (that really could have been in there, if they
    gave a rats ass).

    CPU
    |
    NB
    |
    SB ------------- PCI bus --- NEC 72xxxx (USB2 hub)
    | USB1.1 | USB2.0
    (boots) (does not boot)

    The motherboard company, the BIOS is "modular" and has a "file system".
    If you add a NEC 72xxxx BIOS level module to the BIOS image, there is
    a standard for reading storage devices that helps with the glue for booting.

    The pattern repeats later.

    CPU+NB --- mem sticks
    |
    |
    |
    PCH ------------- PCIe bus --- NEC or Asmedia (USB3 or maybe USB4)
    | USB2.0 | USB3.0
    (boots) (may or may not boot)

    Thus, when an individual claims their machine does not boot
    from USB, there are some steps you can take, to check.
    If it's a Dell, it could be the "Dell-ism" behavior.

    If the design uses an outboard chip (not in the PCH), then
    it may or may not boot. The BIOS companies are getting
    better at adding the BIOS module.

    One reason the BIOS companies do not like adding the module,
    is because of things like SIL3112. Silicon Image provided
    a number of BIOS and runtime modules for its silicon. But,
    when the BIOS boot module has a bug, now what do you do ?
    The SIL3112 had some problem with 1TB hard drives or so.
    This required re-issuing the BIOS file (and likely this was
    after the support period was past). Motherboard companies
    have issued a lot more BIOS files than normal, since the UEFI/PCA2011/BlackLotus era came along. They are, in a sense
    now "used to it", patching up shit. They definitely do not
    like doing this, but they seem to have discovered production
    line techniques for repairing a hundred BIOS at the same time.

    And even when you have given up on a motherboard company
    (late with their update), don't worry, it might take them
    an extra *nine months* to get around to it, but they eventually
    will release one. As a user though, you have no idea what
    is going on, with regard to those.

    Summary: Attempt to boot off the "slowest" USB port, as an
    attempt to see if the BIOS is new enough for USB boot
    from SB/PCH chip.

    Paul


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Len Murphy@invalid@invalid.invalid to alt.os.linux.mint on Mon Nov 9 06:45:23 2026
    From Newsgroup: alt.os.linux.mint

    On 08/11/2026 15:17, Mike Easter wrote:
    So, I put a Plop boot manager on a CD, I'm currently using his PBM6,
    and it allows me to boot from devices that the native bios won't, such
    as an added SSD, or of course USBs.


    My machines can boot from USB flash drives, but they don't have DVD
    drives. Would it be possible to create a custom flash drive that I could
    use to create a bootable drive with your boot image? I know Rufus can do
    this with Linux distributions, but I want to try the small image to see
    if it can create various utilities for both Linux and Windows. It's just
    a hobby of mine.




    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.os.linux.mint on Mon Nov 9 03:57:52 2026
    From Newsgroup: alt.os.linux.mint

    On Mon, 11/9/2026 1:45 AM, Len Murphy wrote:
    On 08/11/2026 15:17, Mike Easter wrote:
    So, I put a Plop boot manager on a CD, I'm currently using his PBM6, and it allows me to boot from devices that the native bios won't, such as an added SSD, or of course USBs.


    My machines can boot from USB flash drives, but they don't have DVD drives. Would it be possible to create a custom flash drive that I could use to create a bootable drive with your boot image? I know Rufus can do this with Linux distributions, but I want to try the small image to see if it can create various utilities for both Linux and Windows. It's just a hobby of mine.





    $ disktype pbm6.iso

    Regular file, size 1.010 MiB (1058816 bytes)
    ISO9660 file system
    Volume name "PBM6"
    Application "GENISOIMAGE ISO 9660/HFS FILESYSTEM CREATOR (C) 1993 E.YOUNGDALE (C) 1997-2006 J.PEARSON/J.SCHILLING (C) 2006-2007 CDRKIT TEAM"
    Data size 1.010 MiB (1058816 bytes, 517 blocks of 2 KiB)
    El Torito boot record, catalog at 32
    Bootable non-emulated image, starts at 33, preloads 2 KiB
    Platform 0x00 (x86), System Type 0x00 (Empty)
    Joliet extension, volume name "PBM6"

    That should boot on a legacy BIOS machine.

    You can use disktype, to judge whether a thing is legacy or hybrid.

    There is also SuperGRUB, available as an ISO, but with
    the same sort of limitation that it might not be a hybrid
    and boots in either legacy BIOS (CSM) or in UEFI mode,
    but not both. In SuperGRUB is scans the machine for bootable
    partitions and makes a menu entry for each one it thinks it
    can boot. I believe I have even chainloaded balky Windows where
    the boot is broken (like the EFI directory stuff isn't right).

    These are things, you just play with them and see what you can get.

    I may have tried more than one SuperGRUB before I got one that
    fit the situation.

    supergrub2-classic-2.06s4-multiarch-CD.iso

    Name: supergrub2-classic-2.06s4-multiarch-CD.iso
    Size: 24,905,728 bytes (23 MiB)
    SHA256: D26EE9CDA990051FBE4C2B367659DF5156A130A7ADA29F0B4FB0E65928D8EBAB

    # It might be this one

    https://sourceforge.net/projects/supergrub2/files/2.06s4/super_grub2_disk_2.06s4/supergrub2-classic-2.06s4-multiarch-CD.iso/download

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Axel@none@not.here to alt.os.linux.mint on Mon Nov 9 20:56:46 2026
    From Newsgroup: alt.os.linux.mint

    Paul wrote:
    On Sun, 11/8/2026 4:02 AM, Axel wrote:
    Paul wrote:
    On Sat, 11/7/2026 9:02 PM, Axel wrote:
    Axel wrote:
    Paul wrote:
    On Sat, 11/7/2026 6:59 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 8 Nov 2026 10:31:56 +1100, Axel wrote:

    after doing the latest updates on a LM 21.3 machine it fails to >>>>>>>> boot- flashing cursor after initial bootup and the LM logo.
    Any boot messages? Tried any recovery modes (e.g. single-user)?

    If the boot options include "quiet splash" from the original
    install, you can edit these in the grub boot menu. You should
    have the menu turned on at all times. Why ? Because of days
    like this. *Never* let a computer obscure stuff... or else.

    And since the OP mentions

    -a-a-a-a "I tried normal and recovery modes using
    -a-a-a-a-a an earlier kernel, but they didn't work"

    We know the menu lines are available to be edited.
    Remove the quiet and splash and see where it is stuck.

    I had something get stuck just the other day on the Big Machine,
    but I neglected to take a picture of this with my camera.

    *******

    A web reference suggests:

    -a-a-a-a press e to edit commands before booting
    -a-a-a-a search & replace "quiet splash" with "nomodeset"
    -a-a-a-a Mint preview desktop starts
    -a-a-a-a Connect to internet
    -a-a-a-a Run driver manager > after it checks download nVidia drive >>>>> sorry, I forgot to mention I did this, but it still won't boot

    Now, that doesn't always work, as Driver Manager now becomes
    confused by the available NVidia drivers versus kernel version
    and it will report that the best driver is already there or
    that no driver is needed.

    But at least if you get that far, you're not dead in the water,
    merely inconvenienced.

    I lose track of these things, but I think I got tempted to try a
    HWE kernel, and instead of making a small jump, it installed 7.0.0 kernel,
    which was never going to work with an old video card :-)
    I'll try again with an older kernel still than I used
    but then.. how will that help. because after I do all the updates I'll be back to square one, won't I?
    While broken, you want to do "something" so you can boot into the OS.
    It's much easier to work on an OS, if you can boot into it,
    and nicer still if the GUI comes up. While you can chroot in with
    a Live media, the question then would be what exactly could you
    do at that point, which is clever enough to fix it. When you use Live media,
    you don't have to chroot in, but chroot is used for things like boot repair.

    You've got:

    1) A distro with an original kernel version.
    2) At some point, the kernel version jumped, and for some people
    -a-a-a that was enough to cause DKMS preparation of the selected NVidia >>> -a-a-a driver to fail. If the folks had stayed on Nouveau, that might not >>> -a-a-a have happened, but that isn't the most pleasant choice on older machines
    -a-a-a (slower). I've probably been in the bind you're in now, several times
    -a-a-a thanks to NVidia. In one case, I had to delete a bunch of packages in
    -a-a-a Synaptic, so that the Driver Manager could offer some "sane choices".
    3) If you further issue the command to enable the HWE kernel, that
    -a-a-a makes a further kernel version jump (7.0.0), which pretty well guarantees an NVidia
    -a-a-a card using the Nvidia driver is going to break.

    You can try nomodeset to get around where you are at now.

    The Nouveau driver has likely been blacklisted. There will
    be a blacklist file, in a directory ending in ".d" that
    will have a single line in it listing "nouveau" to be blacklisted.
    If nouveau was not blacklisted, it could take over as a driver
    in place of the (now nonexistent) DKMS Nvidia driver.

    You could hunt for that file, while booted from Live media.
    But I don't know if that is sufficient to do the job or not,
    as I don't know exactly what the Driver Manager does during
    a boot (if anything).

    When the Driver Manager no longer shows any entries,
    it's "no longer your friend". Whether Clem is supposed to
    fix this, or Ubuntu is supposed to fix this, I can't guess.

    *******

    I could try simulating this, but I don't know if I can match where you
    are right now, close enough to do the job. I would not do that in
    a VM, as the situation requires an NVidia video card as a physical thing. >>> I would do an install with the network cable disconnected, then allow
    the updater to see the possibility of updates.

    You could help by listing:

    1) (New) kernel version that is broken.-a 6.14 maybe ?
    2) (Previous) kernel or two.-a-a-a-a-a-a-a-a-a-a-a-a Was it 6.8.xxx ?
    3) Model of Nvidia card.
    the current kernel listed in Grub is 5.15.0-203
    I've also tried booting with 5.15.0-198, 157 and 151, without success

    this is the hardware (from System Info)

    -a Kernel: 5.15.0-91-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
    -a-a-a tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
    -a-a-a base: Ubuntu 22.04 jammy
    Machine:
    -a Type: Desktop Mobo: ASRock model: 980DE3/U3S3 serial: <superuser required>
    -a-a-a BIOS: American Megatrends v: P2.00 date: 09/04/2015
    CPU:
    -a Info: 6-core model: AMD FX-6100 bits: 64 type: MT MCP smt: enabled arch: Bulldozer rev: 2 cache:
    -a-a-a L1: 288 KiB L2: 6 MiB L3: 8 MiB
    -a Speed (MHz): avg: 1109178 high: 1110599 min/max: 1400/3300 boost: enabled cores: 1: 1108953
    -a-a-a 2: 1110599 3: 1110557 4: 1108221 5: 1108475 6: 1108265 bogomips: 31318379
    -a Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    Graphics:
    -a Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: ASUSTeK driver: nouveau v: kernel pcie:
    -a-a-a speed: 2.5 GT/s lanes: 4 ports: active: HDMI-A-1 empty: DVI-D-1 bus-ID: 01:00.0
    -a-a-a chip-ID: 10de:1d01 class-ID: 0300
    -a Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa
    -a-a-a gpu: nouveau display-ID: :0 screens: 1
    -a Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9")
    -a Monitor-1: HDMI-1 mapped: HDMI-A-1 model: Asus VP247 serial: <filter> res: 1920x1080 hz: 60
    -a-a-a dpi: 94 size: 521x293mm (20.5x11.5") diag: 598mm (23.5") modes: max: 1920x1080 min: 720x400
    -a OpenGL: renderer: NV138 v: 4.3 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes
    Audio:
    -a Device-1: AMD SBx00 Azalia driver: snd_hda_intel v: kernel bus-ID: 00:14.2 chip-ID: 1002:4383
    -a-a-a class-ID: 0403
    -a Device-2: NVIDIA GP108 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
    -a-a-a pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 01:00.1 chip-ID: 10de:0fb8 class-ID: 0403
    -a Sound Server-1: ALSA v: k5.15.0-91-generic running: yes
    -a Sound Server-2: PulseAudio v: 15.99.1 running: yes
    -a Sound Server-3: PipeWire v: 0.3.48 running: yes
    Network:
    -a Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169
    -a-a-a v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e800 bus-ID: 04:00.0 chip-ID: 10ec:8168
    -a-a-a class-ID: 0200
    -a IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
    Drives:
    -a Local Storage: total: 931.52 GiB used: 265.16 GiB (28.5%)
    -a ID-1: /dev/sda vendor: Western Digital model: WD5000AZLX-60K2TA0 size: 465.76 GiB
    -a-a-a speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 1A01 scheme: GPT
    -a ID-2: /dev/sdb type: USB vendor: LITE-ON model: UITRA1 size: 465.76 GiB type: N/A
    -a-a-a serial: <filter> rev: 0108 scheme: MBR
    Partition:
    -a ID-1: / size: 7.8 GiB used: 793 MiB (9.9%) fs: overlay source: ERR-102 >> Swap:
    -a Alert: No swap data was found.
    USB:
    -a Hub-1: 1-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
    -a-a-a class-ID: 0900
    -a Hub-2: 1-3:10 info: Terminus Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
    -a-a-a chip-ID: 1a40:0101 class-ID: 0900
    -a Device-1: 1-3.1:11 info: UGREEN Receiver type: Keyboard,Mouse,HID driver: hid-generic,usbhid
    -a-a-a interfaces: 3 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 2b89:0043 class-ID: 0300
    -a-a-a serial: <filter>
    -a Device-2: 1-3.2:12 info: PCPlay Barcode PCP-BCG4209 type: Keyboard,Mouse >> -a-a-a driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s power: 400mA
    -a-a-a chip-ID: 13ba:0018 class-ID: 0301
    -a Device-3: 1-3.3:13 info: Canon PC-D300/FAX-L400/ICD300 type: Printer driver: usblp
    -a-a-a interfaces: 1 rev: 1.1 speed: 12 Mb/s power: 2mA chip-ID: 04a9:2634 class-ID: 0701
    -a-a-a serial: <filter>
    -a Hub-3: 2-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
    -a-a-a class-ID: 0900
    -a Hub-4: 3-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    -a-a-a class-ID: 0900
    -a Hub-5: 4-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    -a-a-a class-ID: 0900
    -a Hub-6: 5-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    -a-a-a class-ID: 0900
    -a Hub-7: 6-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    -a-a-a class-ID: 0900
    -a Hub-8: 7-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    -a-a-a class-ID: 0900
    -a Hub-9: 8-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
    -a-a-a chip-ID: 1d6b:0002 class-ID: 0900
    -a Hub-10: 9-0:1 info: Super-speed hub ports: 4 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003
    -a-a-a class-ID: 0900
    -a Device-1: 9-3:2 info: JMicron / USA JMS578 SATA 6Gb/s type: Mass Storage driver: uas
    -a-a-a interfaces: 1 rev: 3.0 speed: 5 Gb/s power: 8mA chip-ID: 152d:0578 class-ID: 0806
    -a-a-a serial: <filter>
    Sensors:
    -a System Temperatures: cpu: 34.5 C mobo: N/A gpu: nouveau temp: 41.0 C
    -a Fan Speeds (RPM): N/A
    Repos:
    -a Packages: apt: 2120
    -a Active apt repos in: /etc/apt/sources.list
    -a-a-a 1: deb cdrom:[Linux Mint 21.3 _Virginia_ - Release amd64 20240109]/ jammy contrib main
    -a Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    -a-a-a 1: deb http: //packages.linuxmint.com virginia main upstream import backport
    -a-a-a 2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    -a-a-a 3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    -a-a-a 4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    -a-a-a 5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
    Info:
    -a Processes: 230 Uptime: 38m wakeups: 0 Memory: 15.6 GiB used: 2.22 GiB (14.3%) Init: systemd
    -a v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Cinnamon v: 6.0.4 inxi: 3.3.13

    I've booted it with a live DVD. can you suggest anything?

    note; my knowledge of LM is limited

    Thanks for your interest and detailed reply. I am working thru it.

    The GT1030, there should still be a driver in Driver Manager for it.

    yes there is. see here..


    *******

    LM213 Fresh Install (Nouveau)

    System:
    Host: TUBASOLO Kernel: 5.15.0-91-generic x86_64 bits: 64
    Desktop: Cinnamon 6.0.4 Distro: Linux Mint 21.3 Virginia
    Graphics:
    Device-1: NVIDIA GP108 [GeForce GT 1030] driver: nouveau v: kernel
    Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting
    unloaded: fbdev,vesa gpu: nouveau resolution: 1920x1080~75Hz
    OpenGL: renderer: NV138 v: 4.3 Mesa 23.0.4-0ubuntu1~22.04.1

    ************************************************************************

    LM213 Want NVidia. No 535 in updated repo, use 545 as nearest to it. OK.

    first roadblock. :( I tried to change the driver to 545 but got this..

    what should I do? can I maybe remove all nvidia drivers and use the open source one?


    System:
    Host: TUBASOLO Kernel: 5.15.0-91-generic x86_64 bits: 64
    Desktop: Cinnamon 6.0.4 Distro: Linux Mint 21.3 Virginia
    Graphics:
    Device-1: NVIDIA GP108 [GeForce GT 1030] driver: nvidia v: 545.29.06
    Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia
    resolution: 1920x1080~75Hz
    OpenGL: renderer: NVIDIA GeForce GT 1030/PCIe/SSE2
    v: 4.6.0 NVIDIA 545.29.06

    ************************************************************************

    LM213 Update Manager 1GB updates, new kernel, DKMS must be broken.
    When the kernel updates, it is still set up for 545.

    System:
    Host: TUBASOLO Kernel: 5.15.0-203-generic x86_64 bits: 64
    Desktop: Cinnamon 6.0.5 Distro: Linux Mint 21.3 Virginia
    Graphics:
    Device-1: NVIDIA GP108 [GeForce GT 1030] driver: N/A
    Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nouveau,vesa
    unloaded: fbdev,modesetting gpu: N/A resolution: 1920x1080~77Hz
    OpenGL: renderer: llvmpipe (LLVM 15.0.7 256 bits)
    v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.4

    /etc/modprobe.d/blacklist.conf <=== nothing relevant at the moment, nouveau not mentioned

    $ cat /etc/modprobe.d/nvidia-graphics-drivers-kms.conf
    # This file was generated by nvidia-driver-545
    # Set value to 0 to disable modesetting
    options nvidia-drm modeset=1

    Driver Manager has the following text.

    NVIDIA Corporation: GP108 [GeForce GT 1030]
    This device is using an alternative driver.

    nvidia-driver-470 (recommended) <===
    Version 470.256.02-Oubuntu0.22.04.6
    NVIDIA driver metapackage

    nvidia-driver-580
    Version 580.178.04-Oubuntu0.22.04.1
    NVIDIA driver metapackage

    nvidia-driver-545
    X Version 545.29.06-Oubuntu0.22.04.2
    NVIDIA driver metapackage <=== "was selected"

    nvidia-driver-390
    Version 390.157-Oubuntu0.22.04.2
    NVIDIA driver metapackage

    xserver-xorg-video-nouveau (open-source)
    Version 1:1.0.17-2build1
    X.Org X server - Nouveau display driver <=== "now using"

    I can find a reddit

    I'm aware I can boot in single-user (rescue) mode and e.g.

    apt uninstall nvidia-driver-515-open <=== not a binary blob
    apt install nvidia-driver-515 <=== binary blob, uses DMKS

    but I'd like to understand if there is specifically a "Mint way" of doing this.
    ...
    to remove the nvidia driver. try

    sudo apt purge nvidia* <=== assumes not many of total Nvidia packages are loaded
    looks reasonable, when I checked the list

    sudo apt install xserver-xorg-video-nouveau <=== (which is loaded on mine, already)

    # and additionally...

    sudo apt install nvidia-driver-470 <=== metapackage, includes xserver-xorg-video-nvidia-470

    You would probably have to blacklist nouveau, but
    as long as xserver-xorg-video-nouveau is still there,
    the GUI should come up, and when the blacklist nouveau
    is added, that should facilitate the 470 that was installed
    to take over. It's also possible the metapackage would do
    this anyway.

    To do that, you'd have to find the systemd recipe for
    changing boot mode. It's either that, or the "rescue mode"
    in the GRUB menu is going to do that. Before systemd,
    the run levels were numbers. Whereas systemd uses the
    name of the level, single user or multiuser. The single
    user is conceptually similar to how Windows has a Safe Mode
    (and a normal mode). Single-user mode is sometimes used
    for repairs. Assuming you can even get that far, and
    that should work, as like Safe Mode there is less baggage.

    https://askubuntu.com/questions/788323/how-do-i-change-the-runlevel-on-systemd

    "Mapping between runlevels and systemd targets
    roiroCroCroCroCroCroCroCroCroCroCroCroCro4roCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroE
    roeRunlevel roe Target roe
    roLroCroCroCroCroCroCroCroCroCroCroCroCro+roCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCron
    roe0 roe poweroff.target roe
    roLroCroCroCroCroCroCroCroCroCroCroCroCro+roCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCron
    roe1 roe rescue.target roe <=== single-user
    roLroCroCroCroCroCroCroCroCroCroCroCroCro+roCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCron
    roe2, 3, 4 roe multi-user.target roe
    roLroCroCroCroCroCroCroCroCroCroCroCroCro+roCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCron
    roe5 roe graphical.target roe <=== (normal usage ???)
    roLroCroCroCroCroCroCroCroCroCroCroCroCro+roCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCron
    roe6 roe reboot.target roe
    rooroCroCroCroCroCroCroCroCroCroCroCroCro|roCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroy

    Now, to just change the "runlevels" in 16.04, you can use for eg:

    sudo systemctl isolate multi-user.target

    To make this the default "runlevel", you can use:

    sudo systemctl enable multi-user.target
    sudo systemctl set-default multi-user.target <=== likely enough itself
    ...

    sudo systemctl start graphical.target
    sudo systemctl start multi-user.target
    "

    And here, it shows how to do it from the boot line.

    https://www.tecmint.com/boot-ubuntu-in-rescue-mode/

    quiet splash systemd.unit=rescue.target

    Not doing that on the next boot, would then likely run
    you at graphical.target (as it is likely the set-default right now).

    Thank you very much for this detailed info, which enabled me to fix the problem. so I did "sudo apt purge nvidia*" and then clicked on the 470
    driver, and LM rebuilt the nvidia drivers list, with 470 as the
    installed driver. I then did the Update Manager updates, and rebooted
    all looks fine. so it was a nvidia driver issue. thanks again. :)


    Paul

    --
    Linux Mint 22.3

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Axel@none@not.here to alt.os.linux.mint on Mon Nov 9 20:58:44 2026
    From Newsgroup: alt.os.linux.mint

    Heinz Schmitz wrote:
    Axel wrote:

    I've booted it with a live DVD. can you suggest anything?
    I had a similar problem on ubuntu. After a short circuit in the power
    supply I was only presented a tty login screen that never accepted
    my password, and after a while only a blinking white line in the left
    upper corner of the screen.
    I suspected that the PC was not shut down correctly after the flash
    from the power supply. Live CD booted alright and the system seemed
    without other problems.
    I pulled all connections to hard disks and checked them one by one
    with gparted. Found a problem, corrected it, and everything ok again.
    He who heals is right. :-).

    I loaded gparted but couldn't see what to do with it

    Regards,
    H.


    --
    Linux Mint 22.3

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.os.linux.mint on Mon Nov 9 05:15:54 2026
    From Newsgroup: alt.os.linux.mint

    On Mon, 11/9/2026 4:56 AM, Axel wrote:


    Thank you very much for this detailed info, which enabled me to fix the problem.
    so I did "sudo apt purge nvidia*" and then clicked on the 470 driver, and LM rebuilt
    the nvidia drivers list, with 470 as the installed driver. I then did the Update Manager
    updates, and rebooted all looks fine. so it was a nvidia driver issue. thanks again. :)

    Excellent. Thanks for followup.

    And I wouldn't have known that, without setting it up and trying it.
    As quite frequently I get more "optimistic" suggestions that don't work.
    The 470 then, that's old enough it's bound to work.

    *******

    I've just been over, looking at Debian instructions for NVidia install,
    and their instructions are "banana crackers". They sure know how
    to make things seem complicated.

    The Devuan tree-herder, he promised a solution for NVidia, and
    the text provided had one step only, which was acquiring an
    NVidia .run file and running it as root (sudo). And I could
    not believe that worked, but it did. That's considered naughty, because
    it's outside the tree in a way, and you might not be able to easily
    reverse it. But I was happy that the solution was a one-liner.

    You never know what these instructions will look like...

    Paul


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From pinnerite@pinnerite@gmail.com to alt.os.linux.mint on Tue Nov 10 21:25:41 2026
    From Newsgroup: alt.os.linux.mint

    On Mon, 9 Nov 2026 20:58:44 +1100
    Axel <none@not.here> wrote:

    Heinz Schmitz wrote:
    Axel wrote:

    I've booted it with a live DVD. can you suggest anything?
    I had a similar problem on ubuntu. After a short circuit in the power supply I was only presented a tty login screen that never accepted
    my password, and after a while only a blinking white line in the left
    upper corner of the screen.
    I suspected that the PC was not shut down correctly after the flash
    from the power supply. Live CD booted alright and the system seemed
    without other problems.
    I pulled all connections to hard disks and checked them one by one
    with gparted. Found a problem, corrected it, and everything ok again.
    He who heals is right. :-).

    I loaded gparted but couldn't see what to do with it

    Regards,
    H.




    --
    Linux Mint 22.3


    gparted.
    At top right opposite the icons is a field showing the path of a drive.
    If you have more than one there is a dropdown arrow that will enable
    you to choose the one that you wish to examine.

    The lowest items show partitions of the selected drive.
    The menu at the top helps you choose which operation you wish to execute.

    Or more easily, Google "How to use gparted"

    Good luck,
    Alan
    --
    Linux Mint 22.1 kernel version 6.8.0-84-generic Cinnamon 6.4.8
    AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 2TB SSD, 2TB Barracuda
    --- Synchronet 3.22a-Linux NewsLink 1.2