Changing network connections.

Sector11 · 2019-09-12 22:01:28

Had a strange occurrence today.

I had /etc/network/interfaces configured thus:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

## https://forums.bunsenlabs.org/viewtopic.php?pid=88338#p88338

#source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

#allow-hotplug enp2s0
auto enp2s0
iface enp2s0 inet dhcp

All conkys configured correctly and all was good with Sector11.

Today I took my computer to a shop I know and swapped a 4BG RAM stick for an (GB RAM stick and bought a graphics card. An: Advanced Micro Devices [AMD/ATI] Juniper PRO [Radeon HD 6750] Do not know if I need a driver to run it but it's in my computer.

Side question: Do I need some sort of driver for that to use the 1GB memory it has?

Of course they fired it up in the shop to see if is did anything, it booted to the screen but no further, - no keyboard - no mouse - no net connection.

I get it home, plug everything in and NO INTERNET! Fooled around for a while than finally thought install BL on another partition ... I saw it was setting up DCHP to enp3s0 <<-- WHAT!!!!

Backed out of the install went to my /etc/network/interfaces file and made some changes.

Now it looks like this:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

## https://forums.bunsenlabs.org/viewtopic.php?pid=88338#p88338

#source /etc/network/interfaces.d/*

# changed enp2s0 to enp3s0  12/09/19
# The loopback network interface
auto lo
iface lo inet loopback

#allow-hotplug enp3s0
auto enp3s0
iface enp3s0 inet dhcp

Why would that change?

PackRat · 2019-09-12 22:31:53

Predictable Network Interface Names

Did they move your network card to make head space for the new graphics card? That will change the name since the ethernet card will be in a different pci bus. I don't think just adding a graphics card will change the ethernet name, but maybe it did in this case.

Of course they fired it up in the shop to see if is did anything, it booted to the screen but no further, - no keyboard - no mouse - no net connection.

Is that because the keyboard, mouse and ethernet weren't connected; kind of leaving that hanging out there like they borked your computer.

PackRat · 2019-09-12 22:34:00

Side question: Do I need some sort of driver for that to use the 1GB memory it has?

What graphics card was replaced? You'll need AMD/ATI firmware for the new one.

Sector11 · 2019-09-12 22:40:22

PackRat wrote:

Predictable Network Interface Names
Did they move your network card to make head space for the new graphics card? That will change the name since the ethernet card will be in a different pci bus. I don't think just adding a graphics card will change the ethernet name, but maybe it did in this case.
Of course they fired it up in the shop to see if is did anything, it booted to the screen but no further, - no keyboard - no mouse - no net connection.
Is that because the keyboard, mouse and ethernet weren't connected; kind of leaving that hanging out there like they borked your computer.

On-board Ethernet card ... no special card. So no they did not move it.
Which means:

Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)

SHOULD still apply!

Hmmmmm maybe because there was NO internet connection?

Sector11 · 2019-09-12 22:56:44

PackRat wrote:

Side question: Do I need some sort of driver for that to use the 1GB memory it has?
What graphics card was replaced? You'll need AMD/ATI firmware for the new one.

   $ gra
Graphics:  Card-1: Intel Device 5912 bus-ID: 00:02.0 chip-ID: 8086:5912
           Card-2: Advanced Micro Devices [AMD/ATI] Juniper PRO [Radeon HD 6750]
           bus-ID: 01:00.0 chip-ID: 1002:68bf
           Display Server: X.Org 1.19.2 drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           GLX Renderer: Gallium 0.4 on AMD JUNIPER (DRM 2.49.0 / 4.9.0-11-amd64, LLVM 3.9.1)
           GLX Version: 3.0 Mesa 13.0.6 Direct Rendering: Yes

Card-1 - Onboard graphics card. Can't remove - just not using.

Card-2 - the new one

Looks like firmware installed by default:

 12 Sep 19 @ 19:44:40 ~
   $ ser radeon
alias ser = aptitude search
i A libdrm-radeon1                       - Userspace interface to radeon-specific kernel DRM services 
p   libdrm-radeon1-dbg                   - Userspace interface to radeon-specific kernel DRM services 
p   radeontool                           - utility to control ATI Radeon backlight functions on laptop
p   radeontop                            - Utility to show Radeon GPU utilization                     
i A xserver-xorg-video-radeon            - X.Org X server -- AMD/ATI Radeon display driver            
p   xserver-xorg-video-radeon-dbg        - X.Org X server -- AMD/ATI Radeon display driver (debugging

PackRat · 2019-09-12 23:48:27

Card-1 - Onboard graphics card. Can't remove - just not using.
Card-2 - the new one

That probably answers your first question - you added a graphics card without removing the existing card, so your ethernet card was bumped from enp2s0 to enp3s0.

Yes, looks like your firmware is installed. You getting the graphics you need; no tearing that sort of thing?

Last edited by PackRat (2019-09-12 23:50:12)

DeepDayze · 2019-09-12 23:56:32

Usually the built in graphics chip needs to be disabled...that can be done in the BIOS. Try disabling the builtin GPU.

Sector11 · 2019-09-13 00:10:47

PackRat wrote:

Card-1 - Onboard graphics card. Can't remove - just not using.
Card-2 - the new one
That probably answers your first question - you added a graphics card without removing the existing card, so your ethernet card was bumped from enp2s0 to enp3s0.
Yes, looks like your firmware is installed. You getting the graphics you need; no tearing that sort of thing?

Ummm: Predictable Network Interface Names had nothing to do with "graphics" cards - "Network"

And as I just went through this, this part is just so much foofoo:

Come again, what good does this do?
With this new scheme you now get:
Stable interface names across reboots
Stable interface names even when hardware is added or removed, i.e. no re-enumeration takes place (to the level the firmware permits this)
↑↑ YEA RIIIGHT ↑↑
Stable interface names when kernels or drivers are updated/changed
Stable interface names even if you have to replace broken ethernet cards by new ones
The names are automatically determined without user configuration, they just work
The interface names are fully predictable, i.e. just by looking at lspci you can figure out what the interface is going to be called
Fully stateless operation, changing the hardware configuration will not result in changes in /etc
↑↑ YEA RIIIGHT ↑↑
Compatibility with read-only root
The network interface naming now follows more closely the scheme used for aliasing block device nodes and other device nodes in /dev via symlinks
Applicability to both x86 and non-x86 machines
The same on all distributions that adopted systemd/udev
It's easy to opt out of the scheme (see below)

Nope, seem just fine. And since the Montior is not plugged into the Mobo Graphics card I guess I'm good

DeepDayze wrote:

Usually the built in graphics chip needs to be disabled...that can be done in the BIOS. Try disabling the builtin GPU.

OH Great, I hate playing with the BIOS. But will take a look.

Sector11 · 2019-09-13 00:22:07

DeepDayze wrote:

Usually the built in graphics chip needs to be disabled...that can be done in the BIOS. Try disabling the builtin GPU.

OK, Internal Graphics card "Disabled"

Nothing blew up ... guess I am good to go.

DeepDayze · 2019-09-13 00:28:07

Sector11 wrote:

DeepDayze wrote:
Usually the built in graphics chip needs to be disabled...that can be done in the BIOS. Try disabling the builtin GPU.
OK, Internal Graphics card "Disabled"
Nothing blew up ... guess I am good to go.

Did your network connection go back to the original devicename after that change?

Sector11 · 2019-09-13 00:39:15

DeepDayze wrote:

Sector11 wrote:
DeepDayze wrote:
Usually the built in graphics chip needs to be disabled...that can be done in the BIOS. Try disabling the builtin GPU.
OK, Internal Graphics card "Disabled"
Nothing blew up ... guess I am good to go.
Did your network connection go back to the original devicename after that change?

No I would have said so.

I think it had to do something with turning the computer on while not connected to the Internet.

deleted0 · 2019-09-13 00:49:47

Sector11 wrote:

OK, Internal Graphics card "Disabled"
Nothing blew up ... guess I am good to go.

And you freed up some resources.

8bit

"You miss 100% of the shots you don't take." -Wayne Gretzky

PackRat · 2019-09-13 00:57:23

Ummm: Predictable Network Interface Names had nothing to do with "graphics" cards - "Network"

But the name is derived from the pci bus occupied. You're correct though, it's not supposed to change when adding hardware, but I've seen plenty of posts like yours where the ethernet designation changes for some reason.

Your network card didn't go back to the enp2s0 though; so something else going on.

Sector11 · 2019-09-13 02:24:12

Wayne Gretzky - so true - so true!

@ eight.bit.al - Yupe, did that - happy.

@ PackRat - Yea, someday I'll look into just why it happened.

#1 2019-09-12 22:01:28

Changing network connections.

#2 2019-09-12 22:31:53

Re: Changing network connections.

#3 2019-09-12 22:34:00

Re: Changing network connections.

#4 2019-09-12 22:40:22

Re: Changing network connections.

#5 2019-09-12 22:56:44

Re: Changing network connections.

#6 2019-09-12 23:48:27

Re: Changing network connections.

#7 2019-09-12 23:56:32

Re: Changing network connections.

#8 2019-09-13 00:10:47

Re: Changing network connections.

#9 2019-09-13 00:22:07

Re: Changing network connections.

#10 2019-09-13 00:28:07

Re: Changing network connections.

#11 2019-09-13 00:39:15

Re: Changing network connections.

#12 2019-09-13 00:49:47

Re: Changing network connections.

#13 2019-09-13 00:57:23

Re: Changing network connections.

#14 2019-09-13 02:24:12

Re: Changing network connections.

Board footer