Vasileios,
I’ve about come to my wits end on protonvpn. I’ve been working with the help desk at proton and got a lot of help, but all unsuccessful. I’ve uninstalled nordvpn and protonvpn and reinstalled protonvpn. Here is the log of my latest attempt. It runs until it “thinks” it sees 10 devices connected and then fails. I only have one instance running. If you see anything I’m missing I’d really appreciate it. Thanks
Konsole Record of protonvpn-cli c.txt (44.3 KB)
Hey @Mike19!
I would recommend logging into protonvpn.com and changing your password. Also, if you have an app on your phone for 2-factor authentication, I would recommend you utilize it as well. Once you change the password, any device logged into your VPN will be logged out - sooner or later. Remember to note down and use a complex password (10-12 characters, at least one capital letter, a few numbers and a few symbols will do the trick).
Thanks, that’s a good idea. One other question came to mind: since I am dual booting with Mint and have nordvpn on the mint side, is there any leakage or cross over between the two distros on the same computer?
PS: And another question for my ASUS laptop - dual booting ubuntu and mint. Tried to log into the mint side and only got a blinking cursor right after a line that read “invalid acp audio mode.” Went to the advanced mode and backed down on the kernel a couple of notches, still got the warning about the invalid acp audio mode, but it did boot up. Went to System Reports and it recommended I install multi-media codex. This is my first experience with linux having a boot problem and I don’t know how to generate, or find, a crash log. Any advice would be helpful. No rush, it’s just for nickle knowledge since I’m about to install the LMDE-5 version on here to check out. Thanks for all you do.
Hey @Mike19!
The short answer is no, there is zero leakage between two different Operating Systems. If you mount the other partition, then you can access it, but its root still requires elevated privileges - but no functionalities leak.
On your ACP (or was it ACPI?) issue, if it indeed requires codecs, then there’s a way to install a full pack of them in one go. However, first issue a system-wide update so that you avoid any type of library version mis-matches. Open up a terminal and execute:
sudo apt update && sudo apt upgrade -y
Once that is done, then execute:
sudo apt install ubuntu-restricted-extras
This will install every commonly used codec out there, including some basic Microsoft fonts. Some of them have EULAs (End User License Agreements), which will appear to you as text. You can use the TAB key and then the arrows on your keyboard to highlight the options and press Enter to accept. After that, I believe things should start working as intended.
Also, on the Mint side, it’s worthwhile to know that a new LTS (Long Term Support) version is coming out by the end of this month with a lot of extra hardware support. I believe this will be quite helpful. 
Thanks Vasileios, I think I’ll wait for the new version to come out before wrecking the whole thing. In the meantime, I’ll add the restricted extra package and see how that works. It’s a good learning experience for me to learn how to deal with these things, although I hope it doesn’t happen too often in Linux.
PS: I tried to install the ubuntu restricted extras in linux. It worked fine on my VAIO desktop, but when I tried it on the ASUS laptop, it hung up at the Microsoft EULA. I tried it three times with the same result. There was no way to agree to the EULA other than an button at the bottom of the page. Hitting enter did not help. On the ASUS, it won’t boot up in Mint unless I select the oldest kernel in recovery mode. Running the updates does not seem to help that problem either. Interesting???
Hey @Mike19!
When it asks for the EULA, just keep on tapping the TAB key until it highlights the selection you want or next to it. Then you can use the arrow keys to select the “OK” or the “Accept” one, where you can press the Enter.
On the ASUS not booting, perhaps there is an issue in the boot-loader not being properly updated with the new kernels. Let’s see if the following will help. Open up the terminal and execute:
sudo apt update
sudo apt install -f
sudo update-grub
And then reboot and see if that helped.
Thanks Vasileios, that worked (sorta). Got the update done, but it would not upgrade unless I ran a dpkg configure -a command. Then it upgraded, surprisingly even included the restricted extra package and the tab key worked to accept the EULA. Good Lesson!!! I learned something else new. When I did the shutdown now command, it keep reading lines that said something about stopping to write to the kernel crash log??? Then on restart, I tried using the latest version of the kernel and it wouldn’t start saying that I needed to load the kernel first. Got a successful restart using the oldest kernel in the grub menu. Lot’s to learn here. I think that I may need to spend hours and hours in a college computer class just to begin understanding what’s going on here. What a great hobby! The temps here today are a high of 99 F. That’s the coolest day of the week ahead with forecasts of over 100 F each day for the next week and with no rain in the forecast. That’s north Texas for you. Freezing in the winter and burning up in the summer with about a week of springtime in the middle. So there’s no gardening or yardwork in the near future to interfere with my new found hobby.
Hey @Mike19!
I’m officially jealous of your weather over there! Oregon keeps on shooting us back to Winter at first opportunity. As a Greek, I’m used to your kind of weather. 
Per the dpkg configure -a it would seem that an update wasn’t completed properly.
There might be a way to restore the Kernel images that are obviously not present. Locate and install dracut:
sudo apt install dracut
And then execute it via:
sudo dracut --force
This will generate all the kernel images you have installed to the boot sector. Once that is done, then you can inform the boot loader that the new files are there via:
sudo update-grub
And perhaps give it another shot?
Thanks Vasileios, unfortunately that didn’t work. I still had to go to the oldest kernel version in recovery mode to get it to boot. There was a long list of items that scrolled by during the boot process and some of them were red, but of course they went by so fast that I didn’t get to spot them. Is there a log file for the last boot that I don’t know about? Maybe I could go there and find out what the errors were.
OK, I found this.
talon65@MikesASUS:~$ sudo dmesg -T --color=always --level=err,warn | more
[Wed Jun 22 13:46:43 2022] You have booted with nomodeset. This means your GPU drivers are DISABLE
D
[Wed Jun 22 13:46:43 2022] Any video related functionality will be severely degraded, and you may
not even be able to suspend the system properly
[Wed Jun 22 13:46:43 2022] Unless you actually understand what nomodeset does, you should reboot w
ithout enabling it
[Wed Jun 22 13:46:43 2022] #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14 #15
[Wed Jun 22 13:46:43 2022] pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf co
unter.
[Wed Jun 22 13:46:43 2022] pci 0000:00:00.2: can’t derive routing for PCI INT A
[Wed Jun 22 13:46:43 2022] pci 0000:00:00.2: PCI INT A: not connected
[Wed Jun 22 13:46:43 2022] PPR X2APIC NX GT IA GA PC GA_vAPIC
[Wed Jun 22 13:46:43 2022] ACPI: Invalid passive threshold
[Wed Jun 22 13:46:43 2022] i8042: PNP: PS/2 appears to have AUX port disabled, if this is i
ncorrect please boot with i8042.nopnp
[Wed Jun 22 13:46:44 2022] platform eisa.0: EISA: Cannot allocate resource for mainboard
[Wed Jun 22 13:46:44 2022] platform eisa.0: Cannot allocate resource for EISA slot 1
[Wed Jun 22 13:46:44 2022] platform eisa.0: Cannot allocate resource for EISA slot 2
[Wed Jun 22 13:46:44 2022] platform eisa.0: Cannot allocate resource for EISA slot 3
[Wed Jun 22 13:46:44 2022] platform eisa.0: Cannot allocate resource for EISA slot 4
[Wed Jun 22 13:46:44 2022] platform eisa.0: Cannot allocate resource for EISA slot 5
[Wed Jun 22 13:46:44 2022] platform eisa.0: Cannot allocate resource for EISA slot 6
[Wed Jun 22 13:46:44 2022] platform eisa.0: Cannot allocate resource for EISA slot 7
[Wed Jun 22 13:46:44 2022] platform eisa.0: Cannot allocate resource for EISA slot 8
[Wed Jun 22 13:46:44 2022] systemd[1]: /lib/systemd/system/systemd-ask-password-console.se
rvice:20: Executable “systemd-tty-ask-password-agent” not found in path “/usr/local/sbin:/usr/local/bin:/usr
/sbin:/usr/bin:/sbin:/bin”
[Wed Jun 22 13:46:44 2022] systemd[1]: systemd-ask-password-console.path: Refusing to star
t, unit systemd-ask-password-console.service to trigger not loaded.
[Wed Jun 22 13:46:44 2022] systemd[1]: Failed to start Dispatch Password Requests to Conso
le Directory Watch.
[Wed Jun 22 13:46:45 2022] i2c_hid i2c-ASUE120B:00: i2c-ASUE120B:00 supply vdd not found, u
sing dummy regulator
[Wed Jun 22 13:46:45 2022] i2c_hid i2c-ASUE120B:00: i2c-ASUE120B:00 supply vddl not found,
using dummy regulator
[Wed Jun 22 13:46:45 2022] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0
C9062910 (first instance was on PNP0C14:00)
[Wed Jun 22 13:46:47 2022] snd_pci_acp3x 0000:04:00.5: Invalid ACP audio mode : 0
[Wed Jun 22 13:46:47 2022] thermal thermal_zone1: failed to read out thermal zone (-61)
[Wed Jun 22 13:46:51 2022] Started bpfilter
[Wed Jun 22 13:46:51 2022] kauditd_printk_skb: 13 callbacks suppressed
[Wed Jun 22 13:46:52 2022] iwlwifi 0000:02:00.0: FW already configured (0) - re-configuring
[Wed Jun 22 13:47:03 2022] debugfs: File ‘le_min_key_size’ in directory ‘hci0’ already pre
sent!e–
[Wed Jun 22 13:47:03 2022] debugfs: File ‘le_max_key_size’ in directory ‘hci0’ already pre
sent!e–
[Wed Jun 22 13:52:47 2022] [UFW BLOCK] IN=wlp2s0 OUT= MAC=1c:99:57:aa:1f:63:98:ed:7e:20:80:92:08:0
0 SRC=54.200.212.21 DST=192.168.4.56 LEN=40 TOS=0x0A PREC=0x40 TTL=223 ID=3578 PROTO=TCP SPT=443 DPT=36538 W
INDOW=34356 RES=0x00 ACK FIN URGP=0
[Wed Jun 22 13:53:19 2022] [UFW BLOCK] IN=wlp2s0 OUT= MAC=1c:99:57:aa:1f:63:98:ed:7e:20:80:92:08:0
0 SRC=65.8.243.40 DST=192.168.4.56 LEN=40 TOS=0x08 PREC=0x40 TTL=242 ID=32683 PROTO=TCP SPT=443 DPT=57216 WI
NDOW=34356 RES=0x00 ACK URGP=0
[Wed Jun 22 13:53:19 2022] [UFW BLOCK] IN=wlp2s0 OUT= MAC=1c:99:57:aa:1f:63:98:ed:7e:20:80:92:08:0
0 SRC=65.8.243.40 DST=192.168.4.56 LEN=40 TOS=0x08 PREC=0x40 TTL=242 ID=32674 PROTO=TCP SPT=443 DPT=57212 WI
NDOW=34356 RES=0x00 ACK URGP=0
[Wed Jun 22 13:53:19 2022] [UFW BLOCK] IN=wlp2s0 OUT= MAC=1c:99:57:aa:1f:63:98:ed:7e:20:80:92:08:0
0 SRC=65.8.243.40 DST=192.168.4.56 LEN=40 TOS=0x0A PREC=0x40 TTL=242 ID=32675 PROTO=TCP SPT=443 DPT=57212 WI
NDOW=34356 RES=0x00 ACK FIN URGP=0
[Wed Jun 22 13:53:19 2022] [UFW BLOCK] IN=wlp2s0 OUT= MAC=1c:99:57:aa:1f:63:98:ed:7e:20:80:92:08:0
0 SRC=65.8.243.40 DST=192.168.4.56 LEN=40 TOS=0x0A PREC=0x40 TTL=242 ID=32685 PROTO=TCP SPT=443 DPT=57216 WI
NDOW=34356 RES=0x00 ACK FIN URGP=0
[Wed Jun 22 13:53:20 2022] [UFW BLOCK] IN=wlp2s0 OUT= MAC=1c:99:57:aa:1f:63:98:ed:7e:20:80:92:08:0
0 SRC=65.8.243.79 DST=192.168.4.56 LEN=276 TOS=0x0A PREC=0x40 TTL=242 ID=4224 PROTO=TCP SPT=443 DPT=39938 WI
NDOW=34335 RES=0x00 ACK PSH URGP=0
[Wed Jun 22 13:53:20 2022] [UFW BLOCK] IN=wlp2s0 OUT= MAC=1c:99:57:aa:1f:63:98:ed:7e:20:80:92:08:0
0 SRC=65.8.243.79 DST=192.168.4.56 LEN=40 TOS=0x08 PREC=0x40 TTL=242 ID=60962 PROTO=TCP SPT=443 DPT=39940 WI
NDOW=34335 RES=0x00 ACK URGP=0
[Wed Jun 22 13:53:20 2022] [UFW BLOCK] IN=wlp2s0 OUT= MAC=1c:99:57:aa:1f:63:98:ed:7e:20:80:92:08:0
0 SRC=65.8.243.79 DST=192.168.4.56 LEN=40 TOS=0x08 PREC=0x40 TTL=242 ID=60938 PROTO=TCP SPT=443 DPT=39936 WI
NDOW=34335 RES=0x00 ACK URGP=0
[Wed Jun 22 13:53:20 2022] [UFW BLOCK] IN=wlp2s0 OUT= MAC=1c:99:57:aa:1f:63:98:ed:7e:20:80:92:08:0
0 SRC=65.8.243.79 DST=192.168.4.56 LEN=40 TOS=0x0A PREC=0x40 TTL=242 ID=60940 PROTO=TCP SPT=443 DPT=39936 WI
NDOW=34335 RES=0x00 ACK FIN URGP=0
[Wed Jun 22 13:53:20 2022] [UFW BLOCK] IN=wlp2s0 OUT= MAC=1c:99:57:aa:1f:63:98:ed:7e:20:80:92:08:0
0 SRC=65.8.243.79 DST=192.168.4.56 LEN=40 TOS=0x0A PREC=0x40 TTL=242 ID=60963 PROTO=TCP SPT=443 DPT=39940 WI
NDOW=34335 RES=0x00 ACK FIN URGP=0
[Wed Jun 22 13:53:20 2022] [UFW BLOCK] IN=wlp2s0 OUT= MAC=1c:99:57:aa:1f:63:98:ed:7e:20:80:92:08:0
0 SRC=65.8.243.79 DST=192.168.4.56 LEN=40 TOS=0x08 PREC=0x40 TTL=242 ID=61240 PROTO=TCP SPT=443 DPT=39938 WI
NDOW=34335 RES=0x00 ACK URGP=0
Hey @Mike19!
I finally decided to take a break from the NextCloud Hub editing and come here.
The dmesg command outputs information on the last boot, so it contains only information on the kernel that booted up. At this point, I am curious to see if by removing the “nomodeset” option from the boot operation - if it will help with the newer kernel.
I had a similar issue when I was setting up Debian for NextCloud. The distro did not have an available driver or firmware for the AMD GPU (which on my server was part of the CPU), so the desktop environment would not work. I switched to software mode on another DE and fixed that before I was able to go into the intended environment.
Let’s see if that will help.
When you enter the boot menu for Mint, select the first option (the newest kernel) and hit the letter E on your keyboard. Then, navigate to the nomodeset word with the arrow keys and delete it. Don’t worry, this process only alters the commands for a single boot. Once you delete it, press F10 and see if that does anything.
If it doesn’t, can you copy the contents of the following file and paste it here, please?
/etc/default/grub
Thank you!
Vasileios,
The newest kernel went straight to a flashing dash and hung. Hitting the letter E didn’t do it. Here’s the contents of the grub file:
Thanks
GNU nano 4.8 grub
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=lsb_release -i -s 2> /dev/null || echo Debian
GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash”
GRUB_CMDLINE_LINUX=""
#GRUB_BADRAM=“0x01234567,0xfefefefe,0x89abcdef,0xefefefef”
#GRUB_TERMINAL=console
^G Get Help ^O Write Out ^W Where Is ^K Cut Text ^J Justify ^C Cur Pos
^X Exit ^R Read File ^\ Replace ^U Paste Text^T To Spell ^_ Go To Line
Hey @Mike19!
This is bizarre! The output you’re getting says that you are booting with the nomodeset functionality, but the GRUB configuration does not show it anywhere.
Let’s look into getting an even newer kernel for your Linux Mint.
Open up a terminal and execute the following lines, one at a time:
sudo apt update && sudo apt upgrade -y
sudo add-apt-repository ppa:canonical-kernel-team/proposed -y
sudo apt update
sudo apt install linux-headers-5.15.*-*-generic linux-image-5.15.*-*-generic
sudo update-grub
reboot
And let it go boot normally, which should be the latest, 5.15 kernel, instead of the initial 5.4.
Please let me know how it goes.
Well, this is bizarre! I see it install the 5.15 kernel and I see it when I update grub, but the only kernel listed on reboot is the 5,4 and only the recovery version will successfully boot up.
Have a happy fourth, spend time with your family and take a break from this. I think we can wait for the new release and go from there.
Thanks!!
Happy 4th of July, @Mike19!
If you haven’t seen the 5.15 kernel, then the answer is that Ubuntu is controlling the grub boot-loader. Yes, this happens on systems that have more than one Linux installation. You can boot into Ubuntu and open up the terminal to do the following:
sudo apt update && sudo apt upgrade -y
sudo apt install dracut
sudo dracut --force
sudo update-grub
I hope this helps!