Forum › Forums › Official Releases › antiX-19 “Marielle Franco, Hannie Schaft, Manolis Glezos, Grup Yorum, Wobblies” › After today’s total update boot screens inconsistent
- This topic has 25 replies, 5 voices, and was last updated Dec 16-10:59 pm by olsztyn.
-
AuthorPosts
-
November 30, 2020 at 10:44 pm #46217Member
olsztyn
I have performed a full update of Live antiX using Synaptic and after reboot the first thing I noticed was the boot screens change from full screen to just top left corner (small font) and back as the booting process progresses with dots representing stage of boot, as apparently screen resolution was determined. This video happens to be 1440×900 Nuveau default driver. I will test on other laptops with different resolutions and screens as well.
This was happening in the past but eventually got fixed and the boot screen was uniform in showing boot progress.
I do not think this this catch much attention but if someone has any hints what to exclude from update so as to not cause this fault, such hint will be greatly appreciated.
My antiX was 19.2 Hannie Schaft fully updated about three weeks ago, which update was fine and without negative artifacts.
I am not at a loss as I have multiple backup copies of perfectly working antiX Live, as performing any updates entails for me extensive testing before I migrate to updated release.
Any hints greatly appreciated…
Thanks and Regards.Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersNovember 30, 2020 at 10:54 pm #46218Forum Admin
anticapitalista
::/var/log/apt/history.log (or term.log) might help us to see what caused this.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
November 30, 2020 at 11:11 pm #46219Memberolsztyn
::Thanks for reply at such late for you hour…
Both files (history.log and term.log) are empty.
Also, just to update, booted the same updated antiX Live on other laptops appear to result in the same behavior. The small Top-Left interim boot screen appears to be VGA size, if it matters. I will try to identify boot stage at that point and to identify suspect modules and exclude from update…
Thanks and regards…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersNovember 30, 2020 at 11:20 pm #46221Memberolsztyn
::Both files (history.log and term.log) are empty.
I am not sure but their being empty might have been cased by remaster following antiX update…
I can try to redo update and capture these logs before remaster.
Thanks and Regards.Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersDecember 1, 2020 at 1:38 am #46228Anonymous
::If the problematic update occurred after you had recently performed a remaster operation,
and your system had been using dynamic root persistence, a fallback recovery is possiblesudo mv /live/boot-dev/antiX/linuxfs /live/boot-dev/antiX/linuxfs.BAD sudo mv /live/boot-dev/antiX/linuxfs.old /live/boot-dev/antiX/linuxfs sudo mv /live/boot-dev/antiX/linuxfs.md5 /live/boot-dev/antiX/linuxfs.md5.BAD sudo mv /live/boot-dev/antiX/linuxfs.md5.old /live/boot-dev/antiX/linuxfs.md5 sudo mv /live/boot-dev/antiX/rootfs /live/boot-dev/antiX/rootfs.BAD sudo mv /live/boot-dev/antiX/rootfs.old /live/boot-dev/antiX/rootfs ### then shutdown and restart the systemDecember 1, 2020 at 2:19 am #46229Memberolsztyn
::If the problematic update occurred after you had recently performed a remaster operation,
and your system had been using dynamic root persistence, a fallback recovery is possibleThank you skidoo for this recovery method. However I do not need to go to that extent as I have multiple copies of perfectly working antiX. This was just to report that today’s full update appears to cause a minor imperfection during boot.
A closer examination and comparing to boot appearance of antiX before update using a backup copy for more detail of this artifact:
– The small VGA size screen appears after fourth step – Start Init and appears to proceed to desktop. Upon shutdown the same small screen in top left appears to show.
– In comparison, booting a copy of antiX version before update results (after Start Init of full size) in screen blanking out for a while, after which the screen ‘Udev Done’ or something to that effect appears and then proceeds to desktop, no interim small screen.
Just to emphasize, it is not critical to me as I have multiple copies of perfectly working antiX, taught by prior experience, so I will try to identify what elements I can update and what to leave at current level, instead of total update.
Thanks again and best regards…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersDecember 1, 2020 at 2:28 pm #46259Member
Xecure
::Before installing the updates, update the packagelist
sudo apt update
and save in a separate file the updates
apt list --upgradable > conflicting-upgrades.list
and share the file here or paste the content between code tags. It will be better for the dev team to figure out if you display the list of possible conflicting packages. No need for guessing.antiX Live system enthusiast.
General Live Boot Parameters for antiX.December 1, 2020 at 8:24 pm #46305Memberolsztyn
::share the file here or paste the content between code tags. It will be better for the dev team to figure out if you display the list of possible conflicting packages. No need for guessing.
Thanks Xecure. conflicting-upgrades.list attached…
Regards.Sorry. Forum rejected that attachment for security.
Trying to paste inline. I apologize if long:
Listing…antix-installer/buster 1.3.4 amd64 [upgradable from: 1.3.3] app-select-antix/buster,buster 0.1.5 all [upgradable from: 0.1.3] cli-installer-antix/buster,buster 4.10 all [upgradable from: 4.9] eudev/buster 246:3.2.9.1.0antix1 amd64 [upgradable from: 232:3.2.9.1] fonts-opensymbol/buster-backports,buster-backports 2:102.11+LibO7.0.3-3~bpo10+1 all [upgradable from: 2:102.11+LibO7.0.2-2~bpo10+1] gir1.2-polkit-1.0/buster 0.105-29+antix1 amd64 [upgradable from: 0.105-26+antix1] google-chrome-stable/stable 87.0.4280.66-1 amd64 [upgradable from: 86.0.4240.183-1] gparted-common/buster,buster 1.1.0-0.1.antix1 all [upgradable from: 1.0.0-0.antix1] gparted/buster 1.1.0-0.1.antix1 amd64 [upgradable from: 1.0.0-0.antix1] herbstluftwm/buster 0.9.0-1.0antix1 amd64 [upgradable from: 0.8.3-3.0antix1] icewm-common/buster 1.9.2-1.0antix1 amd64 [upgradable from: 1.8.3-1.0antix1] icewm-experimental/buster 1.9.2-1.0antix1 amd64 [upgradable from: 1.8.3-1.0antix1] icewm/buster 1.9.2-1.0antix1 amd64 [upgradable from: 1.8.3-1.0antix1] iso-snapshot-antix/buster 0.3.22 amd64 [upgradable from: 0.3.20] iso-template-antix/buster,buster 19.16 all [upgradable from: 19.14] libeudev-dev/buster 246:3.2.9.1.0antix1 amd64 [upgradable from: 232:3.2.9.1] libeudev1/buster 246:3.2.9.1.0antix1 amd64 [upgradable from: 232:3.2.9.1] libeudev1/buster 246:3.2.9.1.0antix1 i386 [upgradable from: 232:3.2.9.1] libexif12/stable 0.6.21-5.1+deb10u5 amd64 [upgradable from: 0.6.21-5.1+deb10u4] libexif12/stable 0.6.21-5.1+deb10u5 i386 [upgradable from: 0.6.21-5.1+deb10u4] libgssapi-krb5-2/stable 1.17-3+deb10u1 amd64 [upgradable from: 1.17-3] libgssapi-krb5-2/stable 1.17-3+deb10u1 i386 [upgradable from: 1.17-3] libk5crypto3/stable 1.17-3+deb10u1 amd64 [upgradable from: 1.17-3] libk5crypto3/stable 1.17-3+deb10u1 i386 [upgradable from: 1.17-3] libkrb5-3/stable 1.17-3+deb10u1 amd64 [upgradable from: 1.17-3] libkrb5-3/stable 1.17-3+deb10u1 i386 [upgradable from: 1.17-3] libkrb5support0/stable 1.17-3+deb10u1 amd64 [upgradable from: 1.17-3] libkrb5support0/stable 1.17-3+deb10u1 i386 [upgradable from: 1.17-3] libldap-2.4-2/stable 2.4.47+dfsg-3+deb10u4 amd64 [upgradable from: 2.4.47+dfsg-3+deb10u3] libldap-2.4-2/stable 2.4.47+dfsg-3+deb10u4 i386 [upgradable from: 2.4.47+dfsg-3+deb10u3] libldap-common/stable,stable 2.4.47+dfsg-3+deb10u4 all [upgradable from: 2.4.47+dfsg-3+deb10u3] libpolkit-agent-1-0/buster 0.105-29+antix1 amd64 [upgradable from: 0.105-26+antix1] libpolkit-gobject-1-0/buster,buster 0.105-29+antix1 all [upgradable from: 0.105-26+antix1] libpolkit-gobject-elogind-1-0/buster 0.105-29+antix1 amd64 [upgradable from: 0.105-26+antix1] libproxy1v5/stable 0.4.15-5+deb10u1 amd64 [upgradable from: 0.4.15-5] libuno-cppu3/buster-backports 1:7.0.3-3~bpo10+1 amd64 [upgradable from: 1:7.0.2-2~bpo10+1] libuno-cppuhelpergcc3-3/buster-backports 1:7.0.3-3~bpo10+1 amd64 [upgradable from: 1:7.0.2-2~bpo10+1] libuno-purpenvhelpergcc3-3/buster-backports 1:7.0.3-3~bpo10+1 amd64 [upgradable from: 1:7.0.2-2~bpo10+1] libuno-sal3/buster-backports 1:7.0.3-3~bpo10+1 amd64 [upgradable from: 1:7.0.2-2~bpo10+1] libuno-salhelpergcc3-3/buster-backports 1:7.0.3-3~bpo10+1 amd64 [upgradable from: 1:7.0.2-2~bpo10+1] megasync/unknown 4.3.8-1.1 amd64 [upgradable from: 4.3.5-4.1] ncdu/buster 1.15.1-1.0antix1 amd64 [upgradable from: 1.13-1+b1] policykit-1/buster 0.105-29+antix1 amd64 [upgradable from: 0.105-26+antix1] repo-list/buster,buster 0.1.22 all [upgradable from: 0.1.21] runit-helper/buster,buster 2.10.1+antix1 all [upgradable from: 2.8.6] synaptic/buster 0.90.2+antix1 amd64 [upgradable from: 0.90+antix3] tmux/buster 3.1c-1.0antix1 amd64 [upgradable from: 3.1b-2.0antix1] uno-libs-private/buster-backports 1:7.0.3-3~bpo10+1 amd64 [upgradable from: 1:7.0.2-2~bpo10+1] ure/buster-backports 1:7.0.3-3~bpo10+1 amd64 [upgradable from: 1:7.0.2-2~bpo10+1] xfburn/buster 0.6.2-1.0antix1 amd64 [upgradable from: 0.5.5-2] youtube-dl/buster,buster 2020.11.21.1-1.0antix1 all [upgradable from: 2020.09.20-1.0antix1]- This reply was modified 2 years, 5 months ago by olsztyn.
- This reply was modified 2 years, 4 months ago by rokytnji.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersDecember 2, 2020 at 9:16 pm #46374Member
Xecure
::Sorry. i didn’t have time to check them.
Most suspicious are the eudev related updates. I will try testing on a live USB when I have time.The good thing is that this is only a cosmetic flaw during the tsplash (fbcondecoder) boot, that at some point it detects the graphic device and changes the resolution and scales the boot text splash.
I will try testing from antiX 19.3 base + updates and see if I also experience the same boot graphic glitch. But that wont be today.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.December 2, 2020 at 10:05 pm #46380Memberolsztyn
::Thank you Xecure, no rush or any my ask to spend your time on this, as you must have more important things than cosmetic boot issues of antiX.
Most suspicious are the eudev related updates.
Thanks. This was my conjecture as well. I will try to exclude these and see it it gets better. Subsequently this affects following boot screens. I have not done yet extensive testing of the overall update, taken aback by this issue. I will after taking eudev out of equation.
Thanks and Regards…- This reply was modified 2 years, 5 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersDecember 2, 2020 at 11:44 pm #46386Memberolsztyn
::I will try testing from antiX 19.3 base + updates and see if I also experience the same boot graphic glitch. But that wont be today.
Also, just to mention, my upgrade process was antiX FULL 19.2 Hannie Schaft, total update for the day I reported
I do not know if your 19.3 base will behave the same way. Either way I trust that in the future it will be eventually fixed and current issue might be just cosmetic, not affecting actual functionality of the updated antiX, however such unexpected artifact does nor instill confidence or trust in update in general.
I suggest any update to antiX should be approached with utmost caution and ample testing, with lots of backups before migrating permanently to such updated version. This is what I do, taught by painful experience…
Thanks again and Regards…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersDecember 6, 2020 at 2:15 am #46642Memberolsztyn
::Most suspicious are the eudev related updates. I will try testing on a live USB when I have time.
My attempt to exclude eudev related updates have been somehow not successful to confirm this. Sorry for my failure to accomplish this so far.
My perfectly working version of antiX is Hannie Schaft 19.2 fully updated about a month ago and my attempts to bring up to current update as of today are failing so far for such seemingly unimportant fault. I trust that as in the past this will be eventually fixed as usual.
Just to clarify my uncertainty, it is not just the irratic size of screens during boot sequence but also that some screens appear to be missing from sequence, such as it appears ‘Start Init’ is the last one (reduced in size) and then desktop after some time. The screens in between, namely ‘Udev Done’ and ‘Start X’ do not seem to appear at all, which does not inspire confidence…
I am kind of giving up on this latest update, as being fully updated a month ago should be good for some time… Particularly that it is working perfectly…
Thanks again and best Regards…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersDecember 6, 2020 at 8:47 am #46651Member
Xecure
::Sorry. I totally forgot about this.
Did you experience the same thing from a new live USB with antiX 19.3 (be it full or base)? I will “burn” a new live USB with antiX 19.3 64 bits base and persistence and test it out.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.December 6, 2020 at 11:24 am #46662Member
Xecure
::I must say that I may be imagining things, but hasn’t the boot text and options improved a lot? Is this because of the initrd update? Maybe it has been a long time since I created a new persistence, but it looks cleaner on antiX 19.3 than before. The “terminal screen” is cleaned before asking persistence size and a “DANGER: Insecure password” appears before setting new passwords for root and demo. Colors highlight the options. 10/10. Or maybe I am imagining things.
Could we get something similar for the boot text menus? No longer cascading options, but “clearing” the terminal before each choice? Maybe I am asking for too much.Anyway, back to the issue. I can confirm after installing the eudev update and saving persist changes that there is a little bit of a problem re-scaling the text splash screen, just at the “start init” step (and seems to get stuck until “start X” step). Also, after shutdown/rebooting, the text splash screen also takes about 1/4th of the screen and text gets messed up (“reboot” and “start init” messages get mixed up and get superposed).
Deleted the rootfs and started again, this time holding the current eudev version (232:3.2.9.1) in antiX 19.3 and blocking the 246:3.2.9.1.0antix1 new version (eudev, libeudev-dev and libeudev1 did not update). After updating and saving persistence changes, the text splash screen keeps performing as well as before. SO we can confirm that the last eudev update has changed things enough to create incompatibilities with antiX text splash screen, creating some cosmetic glitches.
My attempt to exclude eudev related updates have been somehow not successful to confirm this.
You can try to do this in you live system before installing the updates:
sudo apt-mark hold eudev
and then, a normal sudo apt upgrade. Eudev should not upgrade on your live system.- This reply was modified 2 years, 5 months ago by Xecure. Reason: added eudev version numbers
antiX Live system enthusiast.
General Live Boot Parameters for antiX.December 6, 2020 at 2:23 pm #46674Memberolsztyn
::Sorry. I totally forgot about this.
Did you experience the same thing from a new live USB with antiX 19.3 (be it full or base)? I will “burn” a new live USB with antiX 19.3 64 bits base and persistence and test it out.
No fault of yours, just my failure to be able to exclude eudev from update. It seemed to me other components had this as dependency, which I was not able to track.
I will try this with 19.3 to see if this got fixed in 19.3, out of curiosity, however it would be a problematic path for me to migrate all settings and tweaks, some I did not keep notes on, to re-create my antiX to perfectly working condition. This is considering such as it took me a long time to figure out IceWM settings to make it work correctly, with the help in this forum, and many other tweaks such as high fidelity sound settings on Alsa, tuning of which can in no way to remembered without digging out from internet found somewhere, etc…
So as you can see it is not just my being lazy, not wanting to start from scratch with 19.3 fresh, there was lots of time invested in making antiX work really well, so my preference would be to update the existing 19.2. However when it comes to a significant difference then I will need to do it at some point if 19.2 is not supported anymore…You can try to do this in you live system before installing the updates:
sudo apt-mark hold eudev
and then, a normal sudo apt upgrade. Eudev should not upgrade on your live system.Thank you Xecure!
Great tip I did not know… Greatly appreciate. I am learning something new every day…
Thanks and Regards…- This reply was modified 2 years, 5 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters -
AuthorPosts
- You must be logged in to reply to this topic.