Problems updating MX Linux - a Debian derivative.

Atheist

Active Member
Joined
Dec 12, 2021
Messages
105
Reaction score
33
Credits
929
I have a new machine: https://psref.lenovo.com/syspool/Sys/PDF/datasheet/Yoga Slim 7i Pro-14_datasheet_EN.pdf
I have installed MX Linux (AHS). In order to avoid terrible screen blanking on and off with cursor movement, I had to replace "quiet splash" with "nomodeset noacpi" in /etc/default/grub. That got me up and running more or less stably.
When I try to (sudo apt) update I get the following:
$ sudo apt update
Err:1 http://deb.debian.org/debian bullseye-updates InRelease
Could not resolve 'deb.debian.org'
Err:2 http://security.debian.org/debian-security bullseye-security InRelease
Could not resolve 'security.debian.org'
Err:3 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bullseye InRelease
Could not resolve 'mirrors.rit.edu'
Err:4 http://deb.debian.org/debian bullseye InRelease
Could not resolve 'deb.debian.org'
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye-updates/InRelease Could not resolve 'deb.debian.org'
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye/InRelease Could not resolve 'deb.debian.org'
W: Failed to fetch http://security.debian.org/debian-security/dists/bullseye-security/InRelease Could not resolve 'security.debian.org'
W: Failed to fetch http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/dists/bullseye/InRelease Could not resolve 'mirrors.rit.edu'
W: Some index files failed to download. They have been ignored, or old ones used instead.
apm@Linguist:~
Any help would be appreciated.
A

P.S. Graphics info:
$ inxi -G
Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: N/A
Display: x11 server: X.Org 1.20.13 driver: vesa unloaded: fbdev,modesetting
resolution: 2880x1800~91Hz
OpenGL: renderer: llvmpipe (LLVM 12.0.1 256 bits) v: 4.5 Mesa 21.2.5
apm@Linguist:~
 

Attachments

  • 1639619024000.gif
    1639619024000.gif
    42 bytes · Views: 309


Have you changed the mirrors that are being used?

I am not so familiar with mx linux, but changing the mirrors should produce some beneficial result.

I am led to believe you can switch mirrors with MX Repo manager.
 
Last edited:
It's an issue between the migration from Buster to Bullseye, I have faced it before. Give me an hour or 3 and I can come back with some ideas.

@Atheist let us know your timezone if you like and I'll work to that.

Cheers

Chris
 
It's an issue between the migration from Buster to Bullseye, I have faced it before. Give me an hour or 3 and I can come back with some ideas.

@Atheist let us know your timezone if you like and I'll work to that.

Cheers

Chris
Thanks very much, Chris. I am in New Orleans, i.e. Central time zone U.S.
 
You can try
Code:
ping -c 5 deb.debian.org
and see if you get a response
Are you able to connect to internet?
maybe something wrong with /etc/resolv.conf
 
Ta (Aussie for thank you, pronounced "tar") - 9:15 now and you may have hit the sack.

When you are bright-eyed and bushy-tailed, find your way to Terminal and give us the output for the following (my comments are prefaced by a hash)

Code:
cat /etc/apt/sources.list.d/debian.list

# and

cat /etc/apt/sources.list.d/debian-stable-updates.list

# and

cat /etc/apt/sources.list.d/mx.list

# if they exist

Wizard
 
You can try
Code:
ping -c 5 deb.debian.org
and see if you get a response
Are you able to connect to internet?
maybe something wrong with /etc/resolv.conf
Yes and yes. Pings are good. Cf:
$ ping -c 5 deb.debian.org
PING debian.map.fastlydns.net (151.101.50.132) 56(84) bytes of data.
64 bytes from 151.101.50.132 (151.101.50.132): icmp_seq=1 ttl=59 time=24.0 ms
64 bytes from 151.101.50.132 (151.101.50.132): icmp_seq=2 ttl=59 time=20.2 ms
64 bytes from 151.101.50.132 (151.101.50.132): icmp_seq=3 ttl=59 time=20.0 ms
64 bytes from 151.101.50.132 (151.101.50.132): icmp_seq=4 ttl=59 time=19.5 ms
64 bytes from 151.101.50.132 (151.101.50.132): icmp_seq=5 ttl=59 time=20.3 ms

--- debian.map.fastlydns.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 19.489/20.796/24.038/1.642 ms
thank you.
 
Ta (Aussie for thank you, pronounced "tar") - 9:15 now and you may have hit the sack.

When you are bright-eyed and bushy-tailed, find your way to Terminal and give us the output for the following (my comments are prefaced by a hash)

Wizard
Apparently I do not have those files:
cat: /etc/apt/sources.list.d/debian.list: No such file or directory
cat: /etc/apt/sources.list.d/debian-stable-updates.list: No such file or directory
cat: /etc/apt/sources.list.d/mx.list: No such file or directory
A
P.S. My eyes are still bright, but my tail is losing its bushiness fast. :-(
 
Last edited:
Apparently I do not have those files:
cat: /etc/apt/sources.list.d/debian.list: No such file or directory
cat: /etc/apt/sources.list.d/debian-stable-updates.list: No such file or directory
cat: /etc/apt/sources.list.d/mx.list: No such file or directory
A
P.S. My eyes are still bright, but my tail is losing its bushiness fast. :-(
Also check etc/apt/debian.list - for some silly reason they may have been installed there instead of sources.list.d
 
Last edited by a moderator:
Ta (Aussie for thank you, pronounced "tar") - 9:15 now and you may have hit the sack.

When you are bright-eyed and bushy-tailed, find your way to Terminal and give us the output for the following (my comments are prefaced by a hash)

Code:
cat /etc/apt/sources.list.d/debian.list

# and

cat /etc/apt/sources.list.d/debian-stable-updates.list

# and

cat /etc/apt/sources.list.d/mx.list

# if they exist

Wizard
WAIT!! I think I screwed up. Those files are there. Here:
$ cat /etc/apt/sources.list.d/debian.list
# Debian Stable.
deb http://deb.debian.org/debian bullseye main contrib non-free
deb http://security.debian.org/debian-security bullseye-security main contrib non-free
#deb-src http://deb.debian.org/debian bullseye main contrib non-free

#bullseye backports
#deb http://deb.debian.org/debian bullseye-backports main contrib non-free
 
$ cat /etc/apt/sources.list.d/debian-stable-updates.list
# Debian bullseye Updates
deb http://deb.debian.org/debian bullseye-updates main contrib non-free

SORRY about this. I hope it didn't cause you too much time.
A
 
SORRY TO JUMP IN (Wiz) - No to the below for now, see my next Post

Since the files are where they are suppose to be I am leaning toward a problem with - /etc/resolv.conf
Make a copy of /etc/resolv.conf
Code:
cp /etc/resolv.conf /etc/resolv.conf.old
.
Now run following commands.
Code:
echo 'nameserver 1.1.1.1\nnameserver 1.0.0.1' > /etc/resolv.conf
Code:
ping -c 4 deb.debian.org; echo 'Return code: ' $?
If last line is Return code: 0, apt update should now work
 
Last edited by a moderator:
No, Your Lordship - 1st a couple of errors.

1. Your 1st command AND your 2nd command needs to be prefaced with sudo
2. 2nd command has typo, nnameserver should be nameserver

I am not so certain that it is a DNS issue. As I said before

It's an issue between the migration from Buster to Bullseye, I have faced it before.

Give me some time and I will get back to you with a definitive answer.

@Atheist , in the meantime can you please give me output for (these a L for Lima, not capital I)

Code:
ls -l /etc/resolv.conf

Mine in a similar MX-21 (but not AHS) shows as

Code:
$ ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 65 Dec 16 13:47 /etc/resolv.conf

Thanks

Wizard

BTW by word of short explanation this deals with permissions set on the file, which we can change if need be. :)
 
This subject to your output from the above command being similar to mine.

The lines that say

deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/

are likely a problem.

I'd like to see you change all such references in the file /etc/apt/sources.list.d/mx.list

to read

deb http://mxrepo.com/mx/repo/ bullseye main non-free

The line with the hash does not matter, for now

You can do that either from Terminal with nano or from your File Manager, which should be Thunar, but as root.

If you can't wait, His Lordship can explain how, no doubt.

Save the changed file, run your updates again, and see how it goes.

Cheers

Wiz
 
No, Your Lordship - 1st a couple of errors.

1. Your 1st command AND your 2nd command needs to be prefaced with sudo
2. 2nd command has typo, nnameserver should be nameserver

I am not so certain that it is a DNS issue. As I said before



Give me some time and I will get back to you with a definitive answer.

@Atheist , in the meantime can you please give me output for (these a L for Lima, not capital I)

Code:
ls -l /etc/resolv.conf

Mine in a similar MX-21 (but not AHS) shows as

Code:
$ ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 65 Dec 16 13:47 /etc/resolv.conf

Thanks

Wizard

BTW by word of short explanation this deals with permissions set on the file, which we can change if need be. :)
Could catch on the typo - must have fat fingered that - brain thinks one thing and fingers do nother :eek:- should be
Code:
sudo echo 'nameserver 1.1.1.1\nameserver 1.0.0.1' > /etc/resolv.conf
and
Code:
sudo ping -c 4 deb.debian.org; echo 'Return code: ' $?
- basically two things DNS or Permissions
 
@Atheist , in the meantime can you please give me output for (these a L for Lima, not capital I)

Code:
ls -l /etc/resolv.conf

Mine in a similar MX-21 (but not AHS) shows as

Code:
$ ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 65 Dec 16 13:47 /etc/resolv.conf

BTW by word of short explanation this deals wit, permissions set on the file, which we can change if need be. :)
I am familiar with chmod, if needed
My directory entry looks the same as yours
$ ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 53 Dec 16 10:14 /etc/resolv.conf
 
Could catch on the typo - must have fat fingered that - brain thinks one thing and fingers do nother :eek:- should be
Code:
sudo echo 'nameserver 1.1.1.1\nameserver 1.0.0.1' > /etc/resolv.conf
and
Code:
sudo ping -c 4 deb.debian.org; echo 'Return code: ' $?
- basically two things DNS or Permissions
Thanks, Expirion:
________________________
sudo echo 'nameserver 1.1.1.1\nameserver 1.0.0.1' > /etc/resolv.conf

bash: /etc/resolv.conf: Permission denied
_______________________
apm@Linguist:~
$

sudo ping -c 4 deb.debian.org; echo 'Return code: ' $?

[sudo] password for apm:
PING debian.map.fastlydns.net (151.101.50.132) 56(84) bytes of data.
64 bytes from 151.101.50.132 (151.101.50.132): icmp_seq=1 ttl=59 time=21.8 ms
64 bytes from 151.101.50.132 (151.101.50.132): icmp_seq=2 ttl=59 time=22.7 ms
64 bytes from 151.101.50.132 (151.101.50.132): icmp_seq=3 ttl=59 time=21.9 ms
64 bytes from 151.101.50.132 (151.101.50.132): icmp_seq=4 ttl=59 time=40.3 ms

--- debian.map.fastlydns.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 21.813/26.696/40.309/7.866 ms
Return code: 0
apm@Linguist:~
 

Staff online


Top