Stuck after ISO install - LAN not working [Solved]

[j2mcgreg]

Could it be that my iso is somewhat corrupt????

That's a possibility, but, you have said that it works in an MX 23 live session. Does it also work in a live session of MX 21,3?

[monamtb]

Nope, there must be something else.

Code: Select all

echo 'nameserver 1.1.1.1' | sudo tee /etc/resolv.conf

Then try to open a web page right after that.

Hello Charlie,
after running the sudo tee command the websites now load and I can use my LAN connection.

Code: Select all

Snapshot created on: 20230823_1437
System:    Kernel: 5.10.0-25-amd64 [5.10.191-1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-25-amd64 root=UUID=<filter> ro quiet 
           splash, ipv6.disable=1 
           Desktop: KDE Plasma 5.20.5 info: latte-dock wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.3_x64 Wildflower August 23  2023 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: FUJITSU product: LIFEBOOK E546 v: 10601736746 serial: <filter> 
           Chassis: type: 10 v: LIFEBOOK E546 serial: <filter> 
           Mobo: FUJITSU model: FJNB290 v: F3 serial: <filter> UEFI: FUJITSU // Insyde 
           v: Version 1.28 date: 08/29/2022 
Battery:   ID-1: CMB1 charge: 52.0 Wh (93.0%) condition: 55.9/62.6 Wh (89.3%) volts: 11.8 
           min: 10.8 model: Fujitsu CP753171-01 type: Li-ion serial: <filter> status: Discharging 
CPU:       Info: Dual Core model: Intel Core i5-6300U bits: 64 type: MT MCP arch: Skylake 
           family: 6 model-id: 4E (78) stepping: 3 microcode: F0 cache: L2: 3 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19999 
           Speed: 400 MHz min/max: 400/3000 MHz Core speeds (MHz): 1: 400 2: 400 3: 400 4: 400 
           Vulnerabilities: Type: gather_data_sampling status: Not affected 
           Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable 
           Type: retbleed mitigation: IBRS 
           Type: spec_rstack_overflow status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional, RSB filling, 
           PBRSB-eIBRS: Not affected 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable 
Graphics:  Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Fujitsu Limited. driver: i915 
           v: kernel bus-ID: 00:02.0 chip-ID: 8086:1916 class-ID: 0300 
           Device-2: Chicony FJ Camera type: USB driver: uvcvideo bus-ID: 1-8:3 chip-ID: 04f2:b413 
           class-ID: 0e02 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: modesetting 
           unloaded: fbdev,vesa display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 158 size: 309x174mm (12.2x6.9") 
           diag: 355mm (14") 
           OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 22.0.5 
           direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Fujitsu Limited. 
           driver: snd_hda_intel v: kernel alternate: snd_soc_skl bus-ID: 00:1f.3 
           chip-ID: 8086:9d70 class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-25-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel Ethernet I219-LM vendor: Fujitsu Limited. driver: e1000e v: kernel 
           port: 3040 bus-ID: 00:1f.6 chip-ID: 8086:156f class-ID: 0200 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel modules: wl port: 3040 
           bus-ID: 02:00.0 chip-ID: 8086:24f3 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 
           bus-ID: 1-7:2 chip-ID: 8087:0a2b class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: N/A rfk-block: 
           hardware: no software: no address: <filter> 
           Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: slave accept 
Drives:    Local Storage: total: 931.51 GiB used: 342.34 GiB (36.8%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 1TB size: 931.51 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: 3B6Q scheme: GPT 
Partition: ID-1: / raw-size: 923.25 GiB size: 907.69 GiB (98.31%) used: 342.34 GiB (37.7%) 
           fs: ext4 dev: /dev/sda2 maj-min: 8:2 
           ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 282 KiB (0.1%) fs: vfat 
           dev: /dev/sda1 maj-min: 8:1 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3 
           maj-min: 8:3 
Sensors:   System Temperatures: cpu: 50.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 2584 lib: 1447 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bullseye main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/megasync.list 
           1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/Debian_11/ ./
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirror.easyname.ch/mxlinux-packages/mx/repo/ bullseye main non-free
           2: deb http://mirror.easyname.ch/mxlinux-packages/mx/repo/ bullseye ahs
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https://repo.skype.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/softmaker.list 
           1: deb https://shop.softmaker.com/repo/apt stable non-free
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb [signed-by=/usr/share/keyrings/teamviewer-keyring.gpg] https://linux.teamviewer.com/deb stable main
Info:      Processes: 250 Uptime: 15m wakeups: 2 Memory: 7.65 GiB used: 3.73 GiB (48.7%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

[Charlie Brown]

:D

I knew that, cause there was such an issue on MX-21 about the resolv.conf not being created.

On 21 there was not relvconf package (unlike 19) also on 23 same.. therefore it seems to be an issue sourcing from NM "that version" .. cause that one is responsible for creating the file..

Whatever.. the way you tried is temporary, so, we'll make it permanent:

Code: Select all

sudo tee /etc/resolv2.conf <<!
nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 8.8.8.8
!

Code: Select all

sudo rm /etc/resolv.conf ; sudo ln -s /etc/resolv2.conf /etc/resolv.conf

[monamtb]

Charlie Brown, you are the hero,
Thank you so much for solving this - may it help others also running into that issue.

The MX Linux community is just one awesome bunch :-)!!!!!!!!

[Charlie Brown]

[Charlie Brown]

In the meantime, the resolv2.conf above is also a trick, cause it keeps overwriting the one you ceate.. hence a link etc... to prevent overwriting ...

[CharlesV]

In the meantime, the resolv2.conf above is also a trick, cause it keeps overwriting the one you create.. hence a link etc... to prevent overwriting ...

@Charlie Brown Now THAT is slick!! Thank you for sharing that!!

[Charlie Brown]

My pleasure.