Page 2 of 3

Re: Failure at kernel-update...

Posted: Wed Jun 19, 2019 10:05 am
by BV206
Eadwine Rose wrote:
Wed Jun 19, 2019 7:17 am
Are you guys perhaps running nvidia?
No. Here is the same machine with my main installation:

Code: Select all

        .+yddddddddddddddddddy+.           ------- 
      :yddddddddddddddddddddddddy:         OS: Ubuntu 18.04.2 LTS x86_64 
    -yddddddddddddddddddddhdddddddy-       Host: HP Pavilion g7 Notebook PC 06901300002046100006201 
   odddddddddddyshdddddddh`dddd+ydddo      Kernel: 4.18.0-22-generic 
 `yddddddhshdd-   ydddddd+`ddh.:dddddy`    Uptime: 7 mins 
 sddddddy   /d.   :dddddd-:dy`-ddddddds    Packages: 1927 
:ddddddds    /+   .dddddd`yy`:ddddddddd:   Shell: bash 4.4.19 
sdddddddd`    .    .-:/+ssdyodddddddddds   Resolution: 1600x900 
ddddddddy                  `:ohddddddddd   DE: Xfce 
dddddddd.                      +dddddddd   WM: Xfwm4 
sddddddy                        ydddddds   WM Theme: NumixBlue 
:dddddd+                      .oddddddd:   Theme: Greybird [GTK2/3] 
 sdddddo                   ./ydddddddds    Icons: Elementary-xfce-darker [GTK2/3] 
 `yddddd.              `:ohddddddddddy`    Terminal: xfce4-terminal 
   oddddh/`      `.:+shdddddddddddddo      Terminal Font: Liberation Mono 10 
    -ydddddhyssyhdddddddddddddddddy-       CPU: AMD A4-3305M APU (2) @ 1.900GHz 
      :yddddddddddddddddddddddddy:         GPU: AMD Radeon HD 6480G 
        .+yddddddddddddddddddy+.           Memory: 560MiB / 3418MiB 
           `-/osyhddddhyso/-`                                      
I should add that the persistent USB was encrypted and (while running Xubuntu) I can still see the file system and the Live-usb-storage directory doesn't appear to be affected.

Re: Failure at kernel-update...

Posted: Wed Jun 19, 2019 10:13 am
by Eadwine Rose
Hrmph.. here I was hoping it was just limited to those with nvidia drivers...


There are a few topics very recently on the kernel issues.. *scratches head* At times like these I wish I knew what I was talking about really so I could help. Hopefully soon someone with more knowledge will drop by.

Re: Failure at kernel-update...

Posted: Wed Jun 19, 2019 3:12 pm
by MX-Addict
Eadwine Rose wrote:
Wed Jun 19, 2019 7:17 am
Are you guys perhaps running nvidia?
I'm not running nvidia either, but I'm damn sure not going to update my main USB until I figure out what's happening! If this happened on my main hard-drive I don't know what I'd do, as I don't really know what tools I need to access root from another device in order to roll the kernel back. Holding back on installing MX on my new hard drive until I figure this out.
Only those willing to surmount obstacles can experience the wondrousness of the heights.

Re: Failure at kernel-update...

Posted: Wed Jun 19, 2019 3:16 pm
by Eadwine Rose
I believe in grub, advanced (going by memory here of what I read in another thread) there is a way to select the previous kernel as it would still be there.

Re: Failure at kernel-update...

Posted: Wed Jun 19, 2019 5:29 pm
by MX-Addict
Eadwine Rose wrote:
Wed Jun 19, 2019 3:16 pm
I believe in grub, advanced (going by memory here of what I read in another thread) there is a way to select the previous kernel as it would still be there.
I feel like even more of a noob than I actually am now! I cannot for the life of me find any real kernel options in grub.
(Not running systemd like peter_li, but having the same problem with being unable to use the mouse, or keyboard once it boots up, so no terminal.)
Won't be updating my main USB that I'm using now until I figure this out.
Here's the info for the one I'm using now that I can't afford to lose, and have no time to backup and remaster right now.

Code: Select all

System:    Host: mx1 Kernel: 4.19.0-5-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-18.3_x64 Continuum May 26  2019 
Machine:   Type: Laptop System: TOSHIBA product: Satellite C55t-B v: PSCMQU-00U006 
           serial: <root required> 
           Mobo: TOSHIBA model: ZBWAA v: 1.00 serial: <root required> UEFI [Legacy]: TOSHIBA 
           v: 5.00 date: 07/23/2015 
CPU:       Topology: Dual Core model: Intel Celeron N2830 bits: 64 type: MCP L2 cache: 1024 KiB 
           Speed: 1223 MHz min/max: 500/2416 MHz Core speeds (MHz): 1: 511 2: 502 
Graphics:  Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display driver: i915 
           v: kernel 
           Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel Bay Trail v: 4.2 Mesa 18.2.6 
Audio:     Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio 
           driver: snd_hda_intel 
           Sound Server: ALSA v: k4.19.0-5-amd64 
Network:   Device-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet driver: r8169 
           ID-1: /dev/sda vendor: Toshiba model: MQ01ABF050 size: 465.76 GiB 
           ID-2: /dev/sdb type: USB vendor: SanDisk model: Ultra Fit size: 57.30 GiB 
Partition: ID-1: / size: 19.56 GiB used: 2.60 GiB (13.3%) fs: overlay source: ERR-102  
Info:      Memory: 7.68 GiB used: 1.14 GiB (14.9%) 

Re: Failure at kernel-update...

Posted: Wed Jun 19, 2019 7:54 pm
by BV206
BV206 wrote:
Tue Jun 18, 2019 11:00 pm
This might be related. I had a perfectly good MX 18.3 persistent USB.
Today there were 10 updates including a kernel, firefox and other stuff that I didn't pay attention to.
After I did the updates the USB boots to the desktop but I now have no mouse, no keyboard, and no terminal so I can't tell what else was destroyed and I can't post any other information about it.
Tonight I made a new fresh USB and the same thing happened after I updated it. It boots to the desktop but can't use keyboard or mouse.

Re: Failure at kernel-update...

Posted: Wed Jun 19, 2019 8:04 pm
by fehlix
MX-Addict wrote:
Wed Jun 19, 2019 5:29 pm
Won't be updating my main USB that I'm using now until I figure this out.
Do you have another PC where you can try to check whether the "broken" USB stick boots into the system.
That's just to check thats not hardware / module specific.
Could you also check whether you can boot into the console, by adding a the number 3 into the option field space separated,
which goes to runlevel 3 console and also do try some F6-failsafe options.

Re: Failure at kernel-update...

Posted: Wed Jun 19, 2019 9:01 pm
by BitJam
BV206 wrote:
Tue Jun 18, 2019 11:00 pm
This might be related. I had a perfectly good MX 18.3 persistent USB.
Today there were 10 updates including a kernel, firefox and other stuff that I didn't pay attention to.
After I did the updates the USB boots to the desktop but I now have no mouse, no keyboard, and no terminal so I can't tell what else was destroyed and I can't post any other information about it.
Another user, CaputAlista, just reported the same problem after a live-remaster. I *think* they said a rollback didn't fix it but that would happen if they also had root persistence enabled. They would have to do a rollback and disable persistence.

But I think fehlix's suggestion is better. You should be able to boot into runlevel 3. Once the problem gets fixed in the repos, you should be able to update your system from the command line. We also have a command line package manager, cli-aptiX which makes updating and installing packages from the command line very easy.

Re: Failure at kernel-update...

Posted: Thu Jun 20, 2019 4:16 am
by peter_li
I don't really understand whats the relationship of the other failure descriptions in this thread with my first post. From my point of view the problem is with update-grub which only works on my system when not using systemd, it seems. Is there a way to explore this more in depth and send you better bug reports?

Re: Failure at kernel-update...

Posted: Tue Aug 13, 2019 8:04 pm
by jabeavers
Has this been solved? I have the same problem that just started today. It was working fine for several days, but started not detecting the other OSes on my system. Update-grub says the following:

sudo update-grub
Generating grub configuration file ...
using custom appearance settings
Found background image: /usr/share/backgrounds/MX Wall_1080P.png
Found linux image: /boot/vmlinuz-4.19.0-5-amd64
Found initrd image: /boot/initrd.img-4.19.0-5-amd64
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
Found memtest86+ image: /boot/memtest86+.bin
Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efi
Adding boot menu entry for EFI firmware configuration
done

Any help?