[SOLVED] Cannot replace AntiX with other distro

bodge99 · 08-09-2019, 08:43 AM

Hi,

Klaas:
Systemd errors:

Code:

Failed to dissect: Input/output error

This one appears to be involved with GPT partition identification. SystemD is having problems with the detected partition table.. It looks like your "phantom" ms partitions might be involved here..

Code:

wpa_supplicant[682]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
wpa_supplicant[682]: dbus: Failed to construct signal

Looks like systemd wifi hardware support is either misconfigured or the hardware is incorrectly identified.

Code:

pulseaudio[1115]: [pulseaudio] backend-ofono.c: Failed to register ...

This may be Bluetooth related. Have you tried pairing with an audio device?

I'll look further..

Bodge99

bodge99 · 08-09-2019, 09:06 AM

Hi,

Klaas:
Systemd

Quote:

Systemd provides a standard process for controlling what programs run when a Linux system boots up. While systemd is compatible with SysV and Linux Standard Base (LSB) init scripts, systemd is meant to be a drop-in replacement for these older ways of getting a Linux system running.

Systemd, which was created by Red Hat's Lennart Poettering and Kay Sievers, does more than start the core programs running. It also starts a journal of system activity, the network stack, a cron-style job scheduler, user logins, and many other jobs. That may sound good to you, but some developers hate it.

Quote:

In Unix-based computer operating systems, init (short for initialization) is the first process started during booting of the computer system. Init is a daemon process that continues running until the system is shut down. It is the direct or indirect ancestor of all other processes and automatically adopts all orphaned processes. Init is started by the kernel during the booting process; a kernel panic will occur if the kernel is unable to start it. Init is typically assigned process identifier 1.

SysV init is still used in Slackware and Devuan. Other distro's have adopted systemd as their init mechanism. I personally really detest it.
The only OS that I run with systemd is Mint. As I've said before, I run Mint as other family members use it and I recommend it to new starters as Mint is very easy to use.

I view systemd as a "necessary evil" in Mint. Most of the time it runs reasonably O.K. on my systems but I've seen the occasional problem that could only be solved by reinstalling major parts of the system. Sometimes, I've just said ****** it!, I'm reinstalling..

I think that you need to address your "phantom" ms partitions..

Bodge99

bodge99 · 08-09-2019, 09:55 AM

Klaas:

One other thing to consider.. As Mint 19.2 is out now, you could try booting the Leonovo from a Mint 19.2 flashdrive. As 19.2 has a slightly newer kernel you could try this and see if the installer can see your eMMC.

If it does, you could just "bite the bullet" and install 19.2 "fresh". This would solve any potential missing packages problem as well as eliminating the "phantom" ms partitions if you let the installer wipe everything.

I would personally back up the existing installation to flashdrive as per the first part of post #290. Just in case... but that's just me..

Your call, obviously..

Bodge99

Klaas Vaak · 08-09-2019, 10:15 AM

Quote:

Originally Posted by bodge99

Hi,

Klaas:
Systemd errors:

Code:

Failed to dissect: Input/output error

This one appears to be involved with GPT partition identification. SystemD is having problems with the detected partition table.. It looks like your "phantom" ms partitions might be involved here..

The "systemd-analyze" command was fixed following SystemD reinstallation as per your instruction. The phantom ms partitions, hmm..

Quote:

Code:

wpa_supplicant[682]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
wpa_supplicant[682]: dbus: Failed to construct signal

Looks like systemd wifi hardware support is either misconfigured or the hardware is incorrectly identified.

Yet, Wifi works.

Quote:

Code:

pulseaudio[1115]: [pulseaudio] backend-ofono.c: Failed to register ...

This may be Bluetooth related. Have you tried pairing with an audio device?

1. Bluetooth related? Isn't pulseaudio to do with PulseAudio Volume Control? The volume keys on the keyboard work, unlike with AntiX.
2. Pairing with an audio device: the computer won't be used for that.

Klaas Vaak · 08-09-2019, 10:26 AM

Quote:

Originally Posted by bodge99

Klaas:

One other thing to consider.. As Mint 19.2 is out now, you could try booting the Leonovo from a Mint 19.2 flashdrive. As 19.2 has a slightly newer kernel you could try this and see if the installer can see your eMMC.

If it does, you could just "bite the bullet" and install 19.2 "fresh". This would solve any potential missing packages problem as well as eliminating the "phantom" ms partitions if you let the installer wipe everything.

I would personally back up the existing installation to flashdrive as per the first part of post #290. Just in case... but that's just me..

Your call, obviously..

Bodge99

I would like to avoid taking this path if possible. I know my computer won't be perfect, far from it, but it runs well enough to do the basic things my wife does on it, I'll be happy.
I don't know if you read the comments I posted in your absence today, but essentially inserting your and Colorpurple's kernel parameters was beneficial: a brief bit of text vomit, and booting into Mint happens. In other words, after getting Mint installed and sometimes booting into Mint, sometimes not, this for me is a big step forward.

The main issue now is suspend, which, like I said to Colorpurple (comment #315), seems to be video-related. Couldn't that be tweaked to work? You mentioned tweaking the video in 1 of your earlier comments, yesterday or the day before I think.

colorpurple21859 · 08-09-2019, 10:32 AM

could be the missing firmware

Klaas Vaak · 08-09-2019, 10:50 AM

Quote:

Originally Posted by colorpurple21859

could be the missing firmware

Are you referring to this - my comment #286?

Quote:

W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_8_2893.bin for module i915

When I 1st asked you about it you stated that I don't need to do anything - your comment #289. That stacks with what Bodge stated in comment #295 :

Quote:

This particular firmware file doesn't apply to your hardware.

So, installing it will not make a difference. What has made you change your mind?

Or are you referring to something else?

colorpurple21859 · 08-09-2019, 10:59 AM

I usually work on one problem at a time, now we got you booting okay, and the resume maybe a video problem and this firmware has to do with video. It is a shot in the dark, if it works great, if not at least you'll know that isn't the problem

bodge99 · 08-09-2019, 11:21 AM

Hi,

No, I think colorpurple21859 is raising the possibility that other firmware that might be missing. Depending on how the particular driver has been written, the kernel might not be aware of a particular firmware requirement.. The driver might just tell the kernel that it just cannot run, not the reason why.

Re: Pulseaudio & bluetooth. You can stream audio over Bluetooth.. Specific "hooks" are made between the Bluetooth software stack and the audio software.
BTW, Pulseaudio handles audio overall and was initially written by Lennart Poettering (the systemd guy.). Early versions were viewed poorly.. It was only when he left that others made significant improvements.

Your "text spew" appears to be systemd "barfing".. The "phantom" ms partitions seem to be part of the problem that is causing this.

As systemd controls key parts of your system it needs to be running correctly.

Code:

 systemd[378]: /lib/systemd/system-generators/systemd-gpt-auto-generator failed with exit status 1.

There was patch released in 2017 to allow systemd to ignore mmcblk0rpmb (one of the "phantom" partitions). I don't know when (or if) this was implemented. Poettering seems to reply with "won't fix" a lot to bugs being reported.

Try the kernel parameter:

Code:

systemd.gpt_auto=0

Bodge99

Klaas Vaak · 08-09-2019, 11:23 AM

Quote:

Originally Posted by colorpurple21859

I usually work on one problem at a time, now we got you booting okay, and the resume maybe a video problem and this firmware has to do with video. It is a shot in the dark, if it works great, if not at least you'll know that isn't the problem

OK, I copied that file to /lib/firmware/i915.
Do I need to do:

Code:

sudo update-initramfs -u

Klaas Vaak · 08-09-2019, 11:26 AM

Quote:

Originally Posted by bodge99

Hi,

Try the kernel parameter:

Code:

systemd.gpt_auto=0

Bodge99

So that goes in here, right?

Quote:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash atkbd.reset=1 i8042.nomux=1 i8042.reset=1 i8042.nopnp=1 i8042.dumbkbd=1 rootdelay=5 nomodeset"

bodge99 · 08-09-2019, 11:27 AM

Hi,

A good idea when adding certain types of firmware..

Doing this can't hurt anyway..

Bodge99

EDIT: Yes, add parameters there.

Klaas Vaak · 08-09-2019, 11:39 AM

Quote:

Originally Posted by bodge99

Hi,

A good idea when adding certain types of firmware..

Doing this can't hurt anyway..

Bodge99

EDIT: Yes, add parameters there.

Added it to the kernel parameters, AND did sudo update-grub ;-)
Result: no effect on "resume" - the black suspend screen stays :-(

bodge99 · 08-09-2019, 11:55 AM

Hi,

Re: bxt_huc_ver01_8_2893.bin firmware. This is specifically for the Broxton SOC.

However, Cherry Trail shares a common ancestry with Bay Trail so... perhaps it's worth adding it.

Quote:

Broxton (BXT) is the name of the core for Intel's generation of system on chip serving as a successor to Cherry Trail along with Willow Trail, and were primarily targeted towards smartphones. Broxton chips were designed to be manufactured with a 14 nm process and were part of Intel's Goldmont microarchitecture.

On April 29, 2016, Intel officially cancelled Broxton.

Bodge99

bodge99 · 08-09-2019, 12:02 PM

Hi,

I'll have a look at the systemd reporting and diagnostic tools..

Bodge99