Byzantium backports unofficial

My installation has been singularly difficult and abnormal from others. At the moment all byz-backports have installed without warnings but for some reason there is no sound (and as a bonus video isn’t working if unmuted). Journalctl has various errors and fails but it’s hard to tell which are relevant and relevant to this issue.

2 Likes

I also spend almost 3 weeks to make whole thing work(missing the kbd package). I got no sound issue too later after that, but I ran the second command that Galliley’s no soudn commands first

, then I re run the 3 commands. It worked.

2 Likes

Question, is the flickering issue in the backports the version issue or just the byzamtium not run the higher version well?

Also, is there anyway to only install Phosh-Osk-stub?

Thanks.

Really hard to understand your situation…
Could you check systemctl status and look for failed units like systemctl | grep failed. Next you can inspect the reasons of an each particular unit by systemctl status <unit-name>.

1 Like

Do you mean flickering when you scroll the list of applications? As far as I noticed it appears in Buzantium together with bakcports. So, it must be related to some libs like gtk-3… The same effect I observe in ALT Mobile. Purism could apply some patches to avoid it.
That is more interesting - Crimson backports do not affected yet and work smoothly!

It is hardly possible in Byzantium as far as a lot of core libs must be upgraded together. I think Crimson backports will be much more flexible.

2 Likes

i see. thanks.

1 Like

Nope. Again. And here’s the interesting part (after installing a couple of sound/audio related files that I’m not entirely sure had anything to do with anything), I noticed that sounds in sound setting testing do not work, nor from any media source, BUT, I can hear system sounds (like raising and lowering volume) and I noticed that microphone works too.

That systemctl returned nothing for failled.

1 Like

Well that was interesting. The solution was: there was sound - it just wanted to come out through the modem (apparently). I installed pavucontrol, which is a bit more comprehensive control of audio. Apparently, for some odd reason, all my apps (including the sound settings test sounds) were automatically trying to force sound out via the modem, instead of anywhere else (like speakers or handset or headphones). It shows up as an either/or setting in pavucontrol. Now I just had to select the other destination for sounds when trying to hear something. As I said before: annoying.

2 Likes

Oh! It is really interesting! There is some package that responsible for automatic output switches when you try to call someone, connect BT or just listen the music. callaudiod must be one of them… I will try to find exact name.

1 Like

According to apt info it’s only for routing audio during calls so I’m not convinced that it’s behind this. It could be just a happenstance. Now we know how to fix it, if not prevent it.

1 Like

wys.
In general, could you check that you have all deps in the list installed?

1 Like

Wys doesn’t seem to be the culprit. Checked, all there.

1 Like

Oi @galilley , new phosh 0.45 is a bout to come came out today, and then there’s that Megapixels 2 alpha… Any chance you’ll have time to update those to backports?

3 Likes

vvmd 1.1 and vvmplayer 2.6 for @nerd7473

3 Likes

Too much new dependencies… wlroots, feedbackd, gtk-4, phoc, etc… I will try, according to the description, this release is very nice (like all the previous ones).

2 Likes

unl0kr 2.0.3

Today I tried to run apt dist-upgrade on my daily driver Byzantium with applied backports and lost luks promt exactly as @JR-Fi reported before. A brief inspection of the problem showed that one of the shared library lost in initrd.img file. To be honestly I’ve wanted to try it for a long time another osk for the boot screen - unl0kr.

unl0kr be built without issues and to replace osk-sdl you just need to fix your /etc/crypttab file (replace osk-sdl-keyscript to unl0kr-keyscript) and rebuild initrd.img file (just run sudo dpkg-reconfigure linux-image-6.6.0-1-librem5). The side effect is that the size of initrd.img reduced down to 26Mb instead of almost 100Mb before (when you remove osk-sdl completely).

Finally, I believe if you replace osk-sdl to unl0kr before the first reboot after applying backports everything must be Ok!

1 Like

I did upgrade today and it seems I lost all audio - for some reason there are no audio output or input devices, nothing shown in settings. A bit baffling.

Edit: this is not the same problem as before. Now something is really missing.
Edit: journalctl | grep failed is loooong. It seems to have (alot of repeating) problems, at least…

`kernel: cdns-mhpd-imx 32c00000.hdmi: [drm:cdns_mhdp_audio_config [cdns_mhpd_drmcore]] *ERROR* audio config failed: -110`
(udev-worker)[415]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 2` failed with exit code 99.

(and others - but at least the phosh fractional scaling fail is getting fixed in the new version)

1 Like

Just to check… Did you change wireplumber startup parameters as described in the readme?

The first message looks like this for me:

$ sudo dmesg | grep cdns-mhdp-imx
[    3.739818] cdns-mhdp-imx 32c00000.hdmi: [drm:cdns_mhdp_read_fw_version [cdns_mhdp_drmcore]] firmware version: 50d385ac

The second one about alsa appears as well and I do not care about.

What about installed kernel version?

$ LANG=en apt list --installed | grep "linux-image"
linux-image-6.6.0-1-librem5/byzantium-updates,now 6.6.66pureos1~byz1 arm64 [installed]
linux-image-librem5/byzantium-updates,now 6.6.66pureos1~byz1 arm64 [installed]
1 Like

I happily had audio in every way, as earlier posted, and this change happened without warning(s) - hence the note about update, as that’s the only change since then. The wireplumber changes were done. Now it seems that video-only.service is not to be found.

The kernel check was interesting. I had an older 6.5.0 there also but even removing it had no effect.

1 Like

I’ve lost a little bit in your case… As far as I remember during the last update you was not able to input a luks password, right? Now you changed osk, boot successfully, but lost sound at all?

2 Likes