MX Linux Forum

ludolph wrote: Fri Jun 21, 2019 2:57 amI just broke my system by the above mentioned kernel upgrade, just because I did not read this message on MX Forum.

BitJam wrote: Fri Jun 21, 2019 3:10 am

ludolph wrote: Fri Jun 21, 2019 2:57 amI just broke my system by the above mentioned kernel upgrade, just because I did not read this message on MX Forum.

Is your system live or installed? IIUC the installed system is easy to fix.

JayM wrote: Fri Jun 21, 2019 3:16 am If people don't read the Important Alert at the top of every forum page in bright red letters what makes you think that they'll read their email messages?

ludolph wrote: Fri Jun 21, 2019 3:19 am

JayM wrote: Fri Jun 21, 2019 3:16 am If people don't read the Important Alert at the top of every forum page in bright red letters what makes you think that they'll read their email messages?

I do not read MX Forum every day ... but I read all the emails I get!!!

JayM wrote: Fri Jun 21, 2019 3:25 am i would run kmathern's. May as well fix everything at once rather than piecemeal.

#!/bin/bash

#force rebuild of dkms packages (virtualbox, nvidia, fglrx, broadcom, ndiswrapper)
#part of mx-packageinstaller


[[ $(dpkg-query --show $1 2>/dev/null && echo $?) ]] || exit 0


for i in $(dpkg-query -l |grep "\-dkms" |awk '{print $2'}); do
 dpkg-reconfigure $i |tee -a /var/log/rebuild-dkms.log
done

exit 0

JayM wrote: Fri Jun 21, 2019 3:30 am

ludolph wrote: Fri Jun 21, 2019 3:19 am

JayM wrote: Fri Jun 21, 2019 3:16 am If people don't read the Important Alert at the top of every forum page in bright red letters what makes you think that they'll read their email messages?

I do not read MX Forum every day ... but I read all the emails I get!!!

I'm just the opposite. I visit the forum every day and only check my email when I happen to remember, usually once or twice a week,

One thing I've learned to do is to keep a USB stick set aside that has a recent personal snapshot of my MX system burned to it, so if something happens it's just a minor annoyance causing me to spend a few minutes reinstalling rather than being a major disaster causing me hours of work, reinstalling from scratch then reconfiguring everything the same way I had it.

AK-47 wrote: Fri Jun 21, 2019 3:36 am

JayM wrote: Fri Jun 21, 2019 3:25 am i would run kmathern's. May as well fix everything at once rather than piecemeal.

The /usr/share/mx-packageinstaller-pkglist/rebuild_dkms_packages.sh script actually does everything kmathern's fix does, and also writes its activity to a log file.
Here's what it looks like:

Code: Select all

#!/bin/bash

#force rebuild of dkms packages (virtualbox, nvidia, fglrx, broadcom, ndiswrapper)
#part of mx-packageinstaller


[[ $(dpkg-query --show $1 2>/dev/null && echo $?) ]] || exit 0


for i in $(dpkg-query -l |grep "\-dkms" |awk '{print $2'}); do
 dpkg-reconfigure $i |tee -a /var/log/rebuild-dkms.log
done

exit 0

./fixmx.sh

shutdown -r now

ludolph wrote: Fri Jun 21, 2019 3:40 amOK, but I still thinking, that the email alert could be very useful. I have no idea how many users were affected by this problem, but I am sure that email alert to all MX forum members could prevents serious troubles of many people.

JayM wrote: Fri Jun 21, 2019 3:48 am
So to clarify, just for the sake of Linux newbies, how would ludolph or others use this script on a system that boots to a blinking cursor? I would guess the procedure would be something like
1. Mount the root file system on the hard drive by clicking on it in Thunar
~ snip

JmaCWQ wrote: Fri Jun 21, 2019 4:17 am I think if a forum member has "Administrators can email me information:" set to "Yes" in their board preferences, then by all means send them an email.
This issue is a good example of when Admins could email users with relevant information.
The more ways this info gets out there then hopefully the greater number of people can be saved from having this problem.

Pierre wrote: Fri Jun 21, 2019 4:14 am

JayM wrote: Fri Jun 21, 2019 3:48 am
So to clarify, just for the sake of Linux newbies, how would ludolph or others use this script on a system that boots to a blinking cursor? I would guess the procedure would be something like
1. Mount the root file system on the hard drive by clicking on it in Thunar
~ snip

if you've got an blinking cursor you won't be able to Click on it in Thunar .. ..
- - you would probably have to use Ctrl-F1 to get into an Terminal .. maybe.

Pierre wrote: Fri Jun 21, 2019 4:14 am
if you've got an blinking cursor you won't be able to Click on it in Thunar .. ..
- - you would probably have to use Ctrl-F1 to get into an Terminal .. maybe.

... for those of you who are at the blank screen with a blinking cursor, you can try pressing <Alt><F2> to get to the login console. If that works then it should save you from having to reboot or edit the bootloader entry.

press 'e' in the bootloader and edit the line that starts with "linux" by added a "3" at the end. the press F10 to boot. This should get you to a console where you can can log in. Then run the command....

BitJam wrote: Fri Jun 21, 2019 4:00 amI'm hoping that if we had a screen like this:tty7.png
instead of the blank screen then it would be a little less frightening. It would also make it much easier for people to report to us what is going on and what failed so it is easier for us to help them.

JayM wrote: Fri Jun 21, 2019 3:48 amSo to clarify, just for the sake of Linux newbies, how would ludolph or others use this script on a system that boots to a blinking cursor? I would guess the procedure would be something like
1. Boot to your MX installation medium: DVD or USB stick
2. Mount the root file system on the hard drive by clicking on it in Thunar
3. Open a root Thunar and go to /root on that hard disk partition
4. Right-click there and Create Document of type Empty File and name it something like fixmx.sh
5. Open it in Featherpad and paste the conents of the script there and save it
6. Right-click on it, choose Properties, and check the box to make it executable
7. Boot to the installed system and at the blank screen press alt F2, log on as root, then type

Code: Select all

./fixmx.sh

(enter) then

Code: Select all

shutdown -r now

(enter) to reboot.
Is that about right?

/usr/share/mx-packageinstaller-pkglist/rebuild_dkms_packages.sh
reboot

sunrat wrote: Fri Jun 21, 2019 5:46 am siduction has an Upgrade Warnings subforum which all users are advised to read before upgrading. In over 10 years of using that distro, I've only struck trouble a couple of times which wasn't forewarned there, and several times have waited weeks before getting the all clear because of some major transition. This is to be expected in a distro based on Debian unstable, but maybe MX could do similar.
That said, in 5 years of using MX, this is the very first time a problem like this has occurred. MX is generally very reliable including with upgrades.

Jerry3904 wrote: Fri Jun 21, 2019 12:34 pm That kernel update has been removed, and will disappear as soon as the repo being used syncs up.

sudo apt-get update
sudo apt-get install antix-archive-keyring
sudo apt-get update

KBD wrote: Fri Jun 21, 2019 1:14 pm I'm just thinking out loud, but if we run into a serious update problem in the future couldn't a new keyring be issued to prevent updates? That would pretty much automatically bring users to the forum and they would then see the warning. A new key could be issued with instructions when it's safe to update again. Just a thought, maybe there is a better way to do it, but stopping updates before something breaks in that situation seems better than users breaking things then having to fix it.

antiX-Dave wrote: Fri Jun 21, 2019 10:01 pm So are we suggesting a message system something like this? ...