After a few package upgrades LMDE boots to ER shell???

[este.el.paz]

So, had another recurrence of the booting to Leap 15.6 and ER shell . . . rebooted and selected Faye again and second time brought the LMDE system?? So there is this intermittent issue with not finding itself, but then finding it and the non-revival from suspend, which also might be intermittent?? No time to mess with it now, but posting the system info as per request:

Code: Select all

[code]
System:
  Kernel: 6.1.0-17-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Desktop: Cinnamon v: 6.0.4
    tk: GTK v: 3.24.38 wm: muffin vt: 7 dm: LightDM v: 1.26.0 Distro: LMDE 6 Faye
    base: Debian 12.1 bookworm
Machine:
  Type: Desktop System: Apple product: MacPro5,1 v: 0.0 serial: <superuser required> Chassis:
    type: 7 v: Mac-F221BEC8 serial: <superuser required>
  Mobo: Apple model: Mac-F221BEC8 serial: <superuser required> UEFI: Apple v: 138.0.0.0.0
    date: 07/30/2018
CPU:
  Info: quad core model: Intel Xeon W3565 bits: 64 type: MT MCP smt: enabled arch: Nehalem rev: 5
    cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 1596 min/max: 1596/3325 boost: enabled cores: 1: 1596 2: 1596 3: 1596 4: 1596
    5: 1596 6: 1596 7: 1596 8: 1596 bogomips: 51070
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA GK110 [GeForce GTX 780] vendor: eVga.com. driver: nouveau v: kernel arch: Kepler
    pcie: speed: 2.5 GT/s lanes: 16 ports: active: DVI-I-1 empty: DP-1,DVI-D-1,HDMI-A-1
    bus-ID: 05:00.0 chip-ID: 10de:1004 class-ID: 0300 temp: 34.0 C
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1280x1024 s-dpi: 96 s-size: 338x270mm (13.31x10.63") s-diag: 433mm (17.03")
  Monitor-1: DVI-I-1 model: ViewSonic VA951S serial: <filter> res: 1280x1024 hz: 60 dpi: 86
    size: 376x301mm (14.8x11.85") diag: 482mm (19") modes: max: 1280x1024 min: 720x400
  API: OpenGL v: 4.3 Mesa 22.3.6 renderer: NVF0 direct-render: Yes
Audio:
  Device-1: Intel 82801JI HD Audio driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:3a3e class-ID: 0403
  Device-2: NVIDIA GK110 High Definition Audio vendor: eVga.com. driver: snd_hda_intel v: kernel
    pcie: speed: 2.5 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 10de:0e1a class-ID: 0403
  API: ALSA v: k6.1.0-17-amd64 status: kernel-api
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Intel 82574L Gigabit Network driver: e1000e v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: 2000 bus-ID: 09:00.0 chip-ID: 8086:10f6 class-ID: 0200
  IF: enp9s0 state: down mac: <filter>
  Device-2: Intel 82574L Gigabit Network driver: e1000e v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: 1000 bus-ID: 0a:00.0 chip-ID: 8086:10f6 class-ID: 0200
  Device-3: Broadcom BCM4322 802.11a/b/g/n Wireless LAN vendor: Apple AirPort Extreme driver: wl
    v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 0d:00.0 chip-ID: 14e4:432b class-ID: 0280
  IF: wls5 state: dormant mac: <filter>
  IF-ID-1: enp10s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Apple Built-in Bluetooth 2.0+EDR HCI type: USB driver: btusb v: 0.8 bus-ID: 5-1.1:3
    chip-ID: 05ac:8215 class-ID: fe01 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: enabled,running rfk-block:
    hardware: no software: yes address: <filter>
Drives:
  Local Storage: total: 2.73 TiB used: 32.56 GiB (1.2%)
  ID-1: /dev/sda vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB speed: 3.0 Gb/s
    type: SSD serial: <filter> rev: 032 scheme: GPT
  ID-2: /dev/sdb vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB speed: 3.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: CC43 scheme: GPT
  ID-3: /dev/sdc vendor: Western Digital model: WD10EZEX-00BN5A0 size: 931.51 GiB speed: 3.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: 1A01 scheme: GPT
Partition:
  ID-1: / size: 47.76 GiB used: 8.12 GiB (17.0%) fs: ext4 dev: /dev/sdb8
  ID-2: /boot/efi size: 196.9 MiB used: 43.3 MiB (22.0%) fs: vfat dev: /dev/sdc1
  ID-3: /home size: 88.07 GiB used: 24.39 GiB (27.7%) fs: ext4 dev: /dev/sdb10
Swap:
  ID-1: swap-1 type: partition size: 14.9 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdc9
  ID-2: swap-2 type: partition size: 14.9 GiB used: 0 KiB (0.0%) priority: -3 dev: /dev/sda9
  ID-3: swap-3 type: partition size: 13.06 GiB used: 0 KiB (0.0%) priority: -4 dev: /dev/sdb11
USB:
  Hub-1: 1-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 2-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-3: 3-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 3-3:2 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 3-3.1:3 info: Apple Aluminium Keyboard (ANSI) type: Keyboard,HID driver: apple,usbhid
    interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 05ac:024f class-ID: 0301
    serial: <filter>
  Device-2: 3-3.2:4 info: Sunplus Innovation Gaming mouse [Philips SPK9304] type: Mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s power: 98mA chip-ID: 1bcf:08a0
    class-ID: 0301
  Hub-5: 4-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-6: 5-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-7: 5-1:2 info: Broadcom BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) ports: 3 rev: 2.0
    speed: 12 Mb/s chip-ID: 0a5c:4500 class-ID: 0900
  Device-1: 5-1.1:3 info: Apple Built-in Bluetooth 2.0+EDR HCI type: Bluetooth driver: btusb
    interfaces: 4 rev: 2.0 speed: 12 Mb/s chip-ID: 05ac:8215 class-ID: fe01 serial: <filter>
  Hub-8: 6-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-9: 7-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-10: 8-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A gpu: nouveau temp: 34.0 C
  Fan Speeds (RPM): N/A gpu: nouveau fan: 960
Repos:
  Packages: pm: dpkg pkgs: 2125
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com faye main upstream import backport
    2: deb https: //deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    3: deb https: //deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
    4: deb http: //security.debian.org bookworm-security main contrib non-free non-free-firmware
    5: deb https: //deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware
Info:
  Processes: 264 Uptime: 2m wakeups: 0 Memory: 15.6 GiB used: 2.01 GiB (12.9%) Init: systemd v: 252
  target: graphical (5) default: graphical Compilers: gcc: 12.2.0 alt: 12 Client: Unknown
  python3.11 client inxi: 3.3.26

[/code]

[SMG]

No time to mess with it now, but posting the system info as per request:

Apple hardware (especially some of the older models) can sometimes be finicky about resuming from suspend. It really depends on the GPU.

We'd probably have to check and see what errors you are getting to know if something can be done. Here are the nouveau bug reports that mention suspend.

[este.el.paz]

No time to mess with it now, but posting the system info as per request:

Apple hardware (especially some of the older models) can sometimes be finicky about resuming from suspend. It really depends on the GPU.

We'd probably have to check and see what errors you are getting to know if something can be done. Here are the nouveau bug reports that mention suspend.

@SMG:

Well, the problem comes and goes with changes in kernels . . . it would be better if the problem could be solved and left behind, instead of tagging along, appearing and disappearing, etc.

Thanks for that link to the nouveau forum . . . might be handy to be able to post "upstream" on the problems . . . .

[este.el.paz]

Today is Faye day . . . booted up fine, to the proper system . . . I did see something in the dmesg that said "Failed: failed to start console.service"??? but that didn't seem to interfere with getting to the GUI. Suspended and revived a couple of times, then ran the 6.1.xx -18 kernel upgrade through and updated-bootloader to click the 18 kernel into top choice for grub.

And, cold booted back into Faye . . . and again suspended and revived . . . .

Perhaps Faye is starting to figure out who she is in this machine and is growing more confident, believing in herself such that "revival" is now more enthusiastically accomplished, focusing on herself grounded into her proper UUID instead of shopping for other identities found in other locations???

I'll monitor Faye for a bit more to see if this is consistent behavior or . . . a hypomanic spike . . . .

[EDIT] Following up on the life of Faye, I wanted to be able to mark this as "solved" but so far seems like each time Faye is selected in grub menu, the first time goes to ER or in today's case an "initramfs"?? shell, showing the correct sdb8 location in the dmesg, but not logging into /home . . . .

Have to shut down, then second boot the dmesg runs through, showing one "fail" on "console setup service" but rolling through to GUI. Typing this in Faye, on the second attempt. So Faye is a "50/50" system?? Second times a charm kind of a deal???[/EDIT]

[este.el.paz]

Yep. Today was supposed to be "Faye Day" . . . first boot, selecting Faye from grub goes to ER shell, rebooted and tried again and it went to initramfs shell?? Shut down via power button. Third time it showed (as before) "Leap 15.6" in the dmesg and went to ER. Shut down.

On cold boot I again selected Faye from grub and then "advanced options" . . . from the list of ten or so kernel options I picked the 5th line down . . . booted to initramfs again . . . "can't find init" or something like that.

5th time I selected tomorrow's system, Debian Trixie/12 . . . booted up fine, I'm typing this post in Trixie. Trixie seems to know who she is and where she resides.

Any ideas would be appreciated, hard to work with a system that won't even get to a functional TTY. I'll monitor it for another bit . . . doesn't seem like Faye is snapping out of the init funk???

[este.el.paz]

Today is again the day of Faye . . . this time she booted right up, on the first attempt. Still the same single error in the dmesg on "failed to start console.service . . ." but moved on to the GUI.

Ran an apt that brought 6 packages . . . one of them Firefox, but didn't seem to be any major items that would hopefully move Faye past this intermittency of success and failure . . . ???

Today was a "good day" in the life of Faye in this machine . . . no clues about how to diagnose or move through any potential causes . . . .

[SMG]

no clues about how to diagnose or move through any potential causes . . . .

Me neither. Intermittent issues are often more challenging and I do not normally help with boot issues to know of a good troubleshooting plan for this.

[este.el.paz]

no clues about how to diagnose or move through any potential causes . . . .

Me neither. Intermittent issues are often more challenging and I do not normally help with boot issues to know of a good troubleshooting plan for this.

@SMG:

Well, thanks for playing along on it. It is a bit odd, in that I have both debian and ubuntu systems installed on the same machine, generally running and booting w/o error . . . . Years back when I first checked Mint out I had troubles keeping LMDE running, possibly on my '09 MacBookPro . . . of some type, and switched over to main channel Mint for a number of years . . . .

And, now trying LMDE again . . . finger's crossed that we are in the clear on the boot mis-identification problem . . . .

[este.el.paz]

Another attempts to boot Faye fails to prevail . . . 1st cold boot goes to initramfs shell . . . "reboot" was not accepted as a command; second cold boot goes to the Leap 15.6 ER shell; third cold boot goes again to Leap ER shell; 4th time selected "advanced options" second kernel down in the grub list . . . again goes to Leap 15.6.

It shows "we will run fsck" . . . but question is, is that running in the Leap partition??? Last week I think after a few reboots I got into Faye, there were a few package upgrades, nothing that seemed to clear the problems with self-identification or self-location skills . . . .

Don't know if there have been any changes to the LMDE live iso since 1/6/24 that would warrant a fresh download and reinstall of / . . . haven't had time to mess with reinstalling or chrooting over into the system . . . .

Basic function seems to be eluding this install of LMDE/cinnamon . . . .

[SMG]

Don't know if there have been any changes to the LMDE live iso since 1/6/24 that would warrant a fresh download and reinstall of / . . . haven't had time to mess with reinstalling or chrooting over into the system . . . .

ISOs are frozen in time at the time they are made. They are never updated. Only if there is an issue with what you downloaded or burned to usb might there be any difference.

[este.el.paz]

Don't know if there have been any changes to the LMDE live iso since 1/6/24 that would warrant a fresh download and reinstall of / . . . haven't had time to mess with reinstalling or chrooting over into the system . . . .

ISOs are frozen in time at the time they are made. They are never updated. Only if there is an issue with what you downloaded or burned to usb might there be any difference.

Understood. The question is on the frequency of when LMDE updates their isos?? I recall from years back they would stay the same for quote awhile??

[SMG]

The question is on the frequency of when LMDE updates their isos??

Which part of "They are never updated." did you want me to explain in more detail?

The LMDE 6 ISO which came out last fall will never be updated. What came out the day of release is the only ISO which will ever be released for LMDE 6.

There will be a new LMDE ISO when LMDE 7 is released some time in the future, but that ISO will be for LMDE 7.

[este.el.paz]

OK, that is what I thought, i.e., no point in downloading another one. Over in TW they are changed perhaps daily.

OK, so for kicks I got out my SuperGrub2 ext flash drive, figured out which line would be for LMDE and it booted right up.

I then ran an apt dist-upgrade and the only thing it did was to remove kernel 6.1.0-17-amd64 . . . and it now wants to boot vmlinuz-6.1.0-12-amd64.

I'll have to update-bootloader and see whether this "regression" of kernels will now allow Faye to find herself in the short list of installs?

So, the "good" news is that SG2 will find and boot Faye . . . we'll have to see whether Faye can do it on her own . . . ?? Next week.

[SMG]

OK, so for kicks I got out my SuperGrub2 ext flash drive, figured out which line would be for LMDE and it booted right up.

I then ran an apt dist-upgrade and the only thing it did was to remove kernel 6.1.0-17-amd64 . . . and it now wants to boot vmlinuz-6.1.0-12-amd64.

I believe the latest kernel for LMDE is 6.1.0-18 so I have no idea what is happening on your flash drive.

[este.el.paz]

OK, so for kicks I got out my SuperGrub2 ext flash drive, figured out which line would be for LMDE and it booted right up.

I then ran an apt dist-upgrade and the only thing it did was to remove kernel 6.1.0-17-amd64 . . . and it now wants to boot vmlinuz-6.1.0-12-amd64.

I believe the latest kernel for LMDE is 6.1.0-18 so I have no idea what is happening on your flash drive.

The flash drive is where I have Super Grub2 installed, for an "external" grub function . . . that got me into LMDE install in "sdb8" internal partition; and I ran an apt and that, rather than installing 6.1.0-18 as you suggest might be available . . . removed 6.1.0-17 . . . leaving -12 as the kernel of choice.

I thought that was expressed fairly clearly . . . . Not holding my breath on LMDE finding its way to "health" and clean booting . . . .

Other fish to fry right now.

[SMG]

OK, so for kicks I got out my SuperGrub2 ext flash drive, figured out which line would be for LMDE and it booted right up.

I then ran an apt dist-upgrade and the only thing it did was to remove kernel 6.1.0-17-amd64 . . . and it now wants to boot vmlinuz-6.1.0-12-amd64.

I believe the latest kernel for LMDE is 6.1.0-18 so I have no idea what is happening on your flash drive.

The flash drive is where I have Super Grub2 installed, for an "external" grub function . . . that got me into LMDE install in "sdb8" internal partition; and I ran an apt and that, rather than installing 6.1.0-18 as you suggest might be available . . . removed 6.1.0-17 . . . leaving -12 as the kernel of choice.

I thought that was expressed fairly clearly . . . .

My point was I have no idea why running an upgrade would remove a kernel dropping you back into an even older kernel. That makes no sense to me.

I will have no further comments in this topic. You have a one-off situation that others are not experiencing.

[este.el.paz]

OK, thanks kindly for your assistance. Doesn't seem like any other offerings on the issue . . . I guess no point to posting updates on it . . . . If LMDE can't repair itself soon it'll prolly go the way of nuke n pave.

[xenopeek]

Maybe try updating the initramfs with sudo update-initramfs -u if you haven't tried yet. But because it sometimes boots, sometimes doesn't, that's a very wild guess. A kernel update would have done this already.

[este.el.paz]

Maybe try updating the initramfs with sudo update-initramfs -u if you haven't tried yet. But because it sometimes boots, sometimes doesn't, that's a very wild guess. A kernel update would have done this already.

@xenopeek:

Thanks for the suggestion over here . . . when I get back to LMDE I'll give it a try. I was, as mentioned in the other thread, hoping to mark this as "solved," but booting LMDE still seems to "work" and then "not work."

Somewhere in the recent mix apt appears to have installed the xx -18 kernel, so it must have then run the command??

Still seems like intermittent behavior on LMDE function; on to other stuff to do today. I'll check back to fiddling with LMDE when I get some spare time.

[axisofevil]

[edit:] Based upon the possible chroot data showing the UUIDs were correct I rebooted, selected LMDE in the grub menu and . . . it booted up, as "itself"!!!??? So, the question is will this be an intermittent thing, sometimes booting, sometimes not??? But now in LMDE, ran an apt and it showed the 6.1. xxx -18 kernel packages, which seemed to cause problems for another poster in the forum, also having Nvidia card. So, for now I'm in LMDE, but declined to upgrade to the newer kernel that apt is offering . . . . Possibly there might be a newer on available in the "Kernel" app??

My read of the bug report and the fix in the other topic is that the problem is with the proprietary Nvidia driver packages which you said you are not using. The fix is going to be to change the proprietary Nvidia driver packages and not a change to the kernel.

I don't know if people who are not using the proprietary Nvidia driver are having problems with that kernel.

I am using the 6.1.0-18 kernel with a low-end nvidia card in LMDE6 but with "standard" nouveau drivers, without any problems.