Page 1 of 1

Failed to connect to wired network eth0 (solved)

Posted: Thu Jan 12, 2023 2:39 pm
by szept

Hi guys,

I'm using linux from time to time or going back to windows if I get too annoyed that some apps/games work better on windows. Right now I'm in a phase of 95% linux again, but because Ubuntu got heavier than I could expect I started to seek other options. Lubuntu was very nice, but still heavy/slow for my old laptop. Later I found out there are live-usb distros and I picked AntiX and Puppy as the most attractive options from comparisions I have read. Well, to be honest I was more for Puppy (fossapup64_9.5), until I tried it on my work PC - it failed to connect to the WIRED internet... Ubuntu had no problems, Lubuntu had no problems, AntiX had no problems, but Puppy gave me this ;(

Image

Any ideas how to fix it? AntiX live-USB connected automatically straight away (below).

Image

Thanks,
Damian


Re: Failed to connect to wired network eth0

Posted: Thu Jan 12, 2023 2:56 pm
by rockedge

@szept Good question! and :welcome:

I have not seen the No DHCP negotiation error before. If in fact this is Fossapuo64-0.5 there should be other network management tools to connect with.

This sounds like a firmware driver is missing. What is the ethernet card model? With the other network tools there is one that will let you try out other firmware drivers by loading and unloading them.

Where does this version of Fossapup come from? What are the options in Menu->Setup->Network ?


Re: Failed to connect to wired network eth0

Posted: Thu Jan 12, 2023 3:18 pm
by mikewalsh

@rockedge / @szept :-

Mm. Yes, I'd try out Network Wizard before you condemn Puppy. As Erik says, with that you get the ability to load other drivers and then re-try again.

To keep Puppy's size down to a minimum, not every available item of firmware and/or networking driver is included OOTB. It's usually easy enough to locate and add the required items; as has been stated, this does indeed sound more like missing firmware than anything else.

We do need more info, though; the make/model of the Ethernet card would be a start. Menu->System->PupSysInfo system information should help. Try the 'Device' tab->Network.....and let us have a readout of what it says.

Copy/paste into your next reply, please, and put it between code tags, if you would (the "</>" button above the editor). Makes it easier to read! Thanks.

(It's mostly wireless devices we get this sort of issue with, but.....hell; there's a first time for everything, y'know? Let us have that info, please, and we'll see what can be done. OK?)

Mike. ;)


Re: Failed to connect to wired network eth0

Posted: Thu Jan 12, 2023 4:56 pm
by szept

Thanks guys, I'll get the info you're asking for. It happened on both PC's at my work, but neither Ubuntu, Lubuntu nor AntiX asked for any action - they connected automatically. It's probably something very silly :)

Damian


Re: Failed to connect to wired network eth0

Posted: Thu Jan 12, 2023 8:05 pm
by williwaw

can you copy and paste the log? the code display </> button above will help format the paste in the forum editor


Re: Failed to connect to wired network eth0

Posted: Fri Jan 13, 2023 1:21 am
by 8Geee

I would also like to add this...

Check the router in the browser's address bar (usually 192.168.x.y) and see if the IP needs a reset. I get a "Secure Negotiation Fail" warning whenever my ISP's copper wire connection goes wonky.

8Geee


Re: Failed to connect to wired network eth0

Posted: Tue Jan 17, 2023 4:37 pm
by szept

Got the following.

Computer A:

Code: Select all

▶—— Network Devices ——◀

Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme BCM5761 Gigabit Ethernet PCIe [14e4:1681] (rev 10)
• Kernel Driver: tg3
• Memory Used: 156.00 KB
• Path: /lib/modules/5.4.53/kernel/drivers/net/ethernet/broadcom/tg3.ko
• Driver Version: 3.137
• Description: Broadcom Tigon3 ethernet driver

Computer B:

Code: Select all

▶—— Network Devices ——◀

Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme BCM5761 Gigabit Ethernet PCIe [14e4:1681] (rev 10)
• Kernel Driver: tg3
• Memory Used: 156.00 KB
• Path: /lib/modules/5.4.53/kernel/drivers/net/ethernet/broadcom/tg3.ko
• Driver Version: 3.137
• Description: Broadcom Tigon3 ethernet driver

On the second PC I also run some other stuff:

Code: Select all

▶—— Network Report ——◀

Firewall: On (ip_tables active)
Network Interface: No active interface 
Wireless Network: No wireless connection

▶TCP/IP Network Interfaces:

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:88 errors:0 dropped:0 overruns:0 frame:0
          TX packets:88 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:7048 (6.8 KiB)  TX bytes:7048 (6.8 KiB)


▶Kernel IP Routing Table:

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo


▶Active Internet Connections: (servers and established)

Proto Recv-Q Send-Q Local Address           Foreign Address         State      

tcp        0      0 0.0.0.0:6566            0.0.0.0:*               LISTEN     
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN     


▶Network Protocol Statistics:

Ip:
    Forwarding: 2
    88 total packets received
    0 forwarded
    0 incoming packets discarded
    88 incoming packets delivered
    88 requests sent out
    22 outgoing packets dropped

Icmp:
    44 ICMP messages received
    0 input ICMP message failed
    ICMP input histogram:
        destination unreachable: 44
    44 ICMP messages sent
    0 ICMP messages failed
    ICMP output histogram:
        destination unreachable: 44

IcmpMsg:
        InType3: 44
        OutType3: 44

Tcp:
    0 active connection openings
    0 passive connection openings
    0 failed connection attempts
    0 connection resets received
    0 connections established
    0 segments received
    0 segments sent out
    0 segments retransmitted
    0 bad segments received
    0 resets sent

Udp:
    0 packets received
    44 packets to unknown port received
    0 packet receive errors
    44 packets sent
    0 receive buffer errors
    0 send buffer errors

UdpLite:

TcpExt:
    0 packet headers predicted

IpExt:
    InOctets: 7048
    OutOctets: 7048
    InNoECTPkts: 88

Code: Select all

▶—— 68 Loaded Kernel Modules (lsmod) ——◀

Total Memory Used: 4208.00 KB

MODULE:                BYTES  USED BY
dcdbas                 16384  1 dell_smbios
dell_smbios            16384  1 dell_wmi
dell_wmi               16384  0
dell_wmi_descriptor    16384  2 dell_wmi,dell_smbios
drm                   368640  7 drm_kms_helper,ttm,nouveau
drm_kms_helper        139264  1 nouveau
fb_sys_fops            16384  1 drm_kms_helper
gpio_ich               16384  0
hwmon                  16384  2 tg3,nouveau
i2c_algo_bit           16384  1 nouveau
i2c_i801               28672  0
input_leds             16384  0
iptable_filter         16384  1
iptable_mangle         16384  0
iptable_nat            16384  0
ip_tables              28672  5 iptable_filter,iptable_nat,iptable_mangle
ledtrig_audio          16384  1 snd_hda_codec_generic
libphy                 57344  1 tg3
lpc_ich                24576  0
mxm_wmi                16384  1 nouveau
nf_conntrack           86016  5 xt_conntrack,nf_nat,nf_nat_ftp,nf_conntrack_irc,nf_conntrack_ftp
nf_conntrack_ftp       16384  1 nf_nat_ftp
nf_conntrack_irc       16384  0
nf_defrag_ipv4         16384  1 nf_conntrack
nf_defrag_ipv6         16384  1 nf_conntrack
nf_nat                 36864  2 nf_nat_ftp,iptable_nat
nf_nat_ftp             16384  0
nls_cp852              20480  0
nls_iso8859_2          16384  0
nouveau              1761280  4
parport                40960  2 parport_pc,ppdev
parport_pc             28672  0
pcspkr                 16384  0
ppdev                  20480  0
pps_core               16384  1 ptp
psmouse               122880  0
ptp                    20480  1 tg3
rfkill                 20480  0
snd                    65536  13 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_seq_oss,snd_hda_intel,snd_hda_codec_analog,snd_hda_codec,snd_timer,snd_pcm_oss,snd_pcm,snd_rawmidi,snd_mixer_oss
snd_hda_codec          90112  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_analog
snd_hda_codec_analog    16384  1
snd_hda_codec_generic    65536  1 snd_hda_codec_analog
snd_hda_codec_hdmi     49152  4
snd_hda_core           53248  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_analog,snd_hda_codec
snd_hda_intel          28672  0
snd_intel_nhlt         16384  1 snd_hda_intel
snd_mixer_oss          24576  1 snd_pcm_oss
snd_pcm                81920  5 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_hda_core
snd_pcm_oss            49152  0
snd_rawmidi            28672  1 snd_seq_midi
snd_seq                53248  6 snd_seq_midi,snd_seq_oss,snd_seq_midi_event,snd_seq_dummy
snd_seq_device         16384  4 snd_seq,snd_seq_midi,snd_seq_oss,snd_rawmidi
snd_seq_dummy          16384  0
snd_seq_midi           16384  0
snd_seq_midi_event     16384  2 snd_seq_midi,snd_seq_oss
snd_seq_oss            36864  0
snd_timer              28672  2 snd_seq,snd_pcm
soundcore              16384  1 snd
sparse_keymap          16384  1 dell_wmi
syscopyarea            16384  1 drm_kms_helper
sysfillrect            16384  1 drm_kms_helper
sysimgblt              16384  1 drm_kms_helper
tg3                   159744  0
ttm                    77824  1 nouveau
wmi                    20480  6 dell_wmi,wmi_bmof,dell_smbios,dell_wmi_descriptor,mxm_wmi,nouveau
wmi_bmof               16384  0
xt_conntrack           16384  4
xt_pkttype             16384  1

Code: Select all

Pup-SysInfo System Report (Summary), pon 16 sty 2023

Current Time: 15:07:57
System Uptime: 0d 0h 7m
Load Average: 0.02 0.11 0.08
Processes: 194 total, 3 running

====> BASE STATUS <====

Linux Kernel: 5.4.53 (x86_64)
Version: #1 SMP PREEMPT Sun Jul 26 12:11:02 BST 2020
Build GCC: 9.3.0

Kernel Command Line:
pfix=fsck pmedia=cd

Username: root
Language: pl_PL.UTF-8
Keyboard: pl
Timezone: Europe/Warsaw

Distro: fossapup64 9.5
Window Manager: JWM v2.4.0
Desktop Start: xwin jwm

Development:
 Bash: 5.0.17
 Geany: 1.35
 Gtkdialog: 0.8.4
 Perl: 5.30.0
 Python: 
 Yad: 0.42.1 (GTK+ 2.24.32)
 --
 busybox: 1.31.0
 dhcpcd: 6.6.2
 Glibc: 2.31
 OpenSSL: 1.1.1f  31 Mar 2020, built on: Mon Apr 20 11:53:50 2020 UTC
 wpa_supplicant: 2.9

Firewall: On (ip_tables active)
Network Interface: No active interface 
Wireless Network: No wireless connection

Boot Partition: sdb1 (Size 58G, Free 52G)
Boot File System: vfat
Boot Media: cd

PUPMODE=12
PUPSFS=sdb1,vfat,/puppy_fossapup64_9.5.sfs
PUPSAVE=sdb1,vfat,/fossapup64save-szczyt.4fs

====> COMMAND-LINE HISTORY (/root/.history) <====

No command history is detected in /root/.history.

====> ENVIRONMENT VARIABLES (env) <====

BASH_FUNC_pupsysinfo_help%%=() {  export PUPSYSINFO_HELP="
BATTERY0=BAT0
BATTERY1=
BROWSER=/usr/local/bin/defaultbrowser
...

Code: Select all

Information about this interface:
 Interface: eth0  Driver: tg3  Bus: pci  MacAddress: BC:30:5B:D2:04:EF
 Description: Broadcom Tigon3 ethernet driver 
 
dhcpcd[19720]: version 6.6.2 starting
dhcpcd[19720]: all: IPv6 kernel autoconf disabled
dhcpcd[19720]: eth0: adding address fe80::7b37:44a3:dd78:5658
dhcpcd[19720]: if_addaddress6: Operation not supported
dhcpcd[19720]: script_runreason: /lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 1
dhcpcd[19720]: DUID 00:01:00:01:2b:4a:ec:11:cc:af:78:5b:8a:0b
dhcpcd[19720]: eth0: IAID 5b:d2:04:ef
dhcpcd[19720]: eth0: soliciting a DHCP lease
dhcpcd[19720]: eth0: probing for an IPv4LL address
dhcpcd[19720]: eth0: using IPv4LL address 169.254.123.46
dhcpcd[19720]: eth0: adding route to 169.254.0.0/16
dhcpcd[19720]: script_runreason: /lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 1
dhcpcd[19720]: forked to background, child pid 19930
dhcpcd[19940]: version 6.6.2 starting
dhcpcd[19940]: all: IPv6 kernel autoconf disabled
dhcpcd[19940]: eth0: adding address fe80::7b37:44a3:dd78:5658
dhcpcd[19940]: if_addaddress6: Operation not supported
dhcpcd[19940]: script_runreason: /lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 1
dhcpcd[19940]: DUID 00:01:00:01:2b:4a:ec:11:cc:af:78:5b:8a:0b
dhcpcd[19940]: eth0: IAID 5b:d2:04:ef
dhcpcd[19940]: eth0: soliciting a DHCP lease
dhcpcd[19940]: eth0: probing for an IPv4LL address
dhcpcd[19940]: eth0: using IPv4LL address 169.254.123.46
dhcpcd[19940]: eth0: adding route to 169.254.0.0/16
dhcpcd[19940]: script_runreason: /lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 1
dhcpcd[19940]: forked to background, child pid 20106

And this is from my laptop, where wi-fi is working fine:

Code: Select all

▶—— Network Devices ——◀

Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller [10ec:8136] (rev 05)
• Kernel Driver: r8169
• Memory Used: 72.00 KB
• Path: /lib/modules/5.4.53/kernel/drivers/net/ethernet/realtek/r8169.ko
• Description: RealTek RTL-8169 Gigabit Ethernet driver

Network controller [0280]: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01)
• Kernel Driver: ath9k
• Memory Used: 92.00 KB
• Path: /lib/modules/5.4.53/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko
• Description: Support for Atheros 802.11n wireless LAN cards.

Re: Failed to connect to wired network eth0

Posted: Tue Jan 17, 2023 8:07 pm
by bigpup

When doing a wired connection to the network providing service.

Does it use a set IP address and configurations or are they usually provided by DHCP?

Have you tried to make a connection using the Network Wizard program?
It requires you to select what is done and when. Gives you better control.

Check the Firewall and make sure it is off, when you try to make the first connection.
just to make sure it is not blocking something.
Usually the very first boot will have the Firewall off.

After connection is working, you can turn the Firewall on and keep it on.


Re: Failed to connect to wired network eth0

Posted: Wed Jan 18, 2023 1:42 pm
by rcrsn51

Tg3 is a standard Ethernet driver and should be working. This may be a timing problem.

Open a terminal.
Run: ifconfig eth0 up
Run: dhcpcd eth0
Wait a bit.

As was suggested above, check for missing firmware.

Run: dmesg | grep -i firmware


Re: Failed to connect to wired network eth0

Posted: Fri Jan 20, 2023 6:06 pm
by szept

It worked out eventually! ;D

First I did the terminal commands, so:

ifconfig eth0

Code: Select all

eth0      Link encap:Ethernet  HWaddr B8:AC:6F:97:2F:5A  
          inet addr:192.168.1.249  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:47 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:8859 (8.6 KiB)  TX bytes:2612 (2.5 KiB)
          Interrupt:17

dhcpcd eth0

Code: Select all

dhcpcd[22705]: version 6.6.2 starting
dhcpcd[22705]: all: IPv6 kernel autoconf disabled
dhcpcd[22705]: eth0: adding address fe80::c5a9:5f57:3977:efb2
dhcpcd[22705]: if_addaddress6: Operation not supported
dhcpcd[22705]: script_runreason: /lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 1
dhcpcd[22705]: DUID 00:01:00:01:2b:4a:ec:11:cc:af:78:5b:8a:0b
dhcpcd[22705]: eth0: IAID 6f:97:2f:5a
dhcpcd[22705]: eth0: soliciting a DHCP lease
dhcpcd[22705]: eth0: probing for an IPv4LL address
dhcpcd[22705]: eth0: using IPv4LL address 169.254.182.229
dhcpcd[22705]: eth0: adding route to 169.254.0.0/16
dhcpcd[22705]: script_runreason: /lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 1
dhcpcd[22705]: forked to background, child pid 22906

dmesg | grep -i firmware

Code: Select all

[    1.206197] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    1.325929] acpi PNP0A03:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge

I haven't pay attention, so no idea when the internet connection started working, but after all of them the internet was running! However when I restarted the PC it wasn't working again, so I decided to try internet wizard.

Image

Image

Image

Image

Image

Image

This also fix the connection and at the end it asked if I wanted to save settings, so it will work after reboot. I did and it's working all fine. I did the same thing for the other PC. When I returned to my laptop when wi-fi was working straight form the beggining, it wasn't now, but I clicked on the internet icon with "x" on the taskbar, I scanned for available wifi networks, picked the one I wanted, I tried few options for password and eventually it's working again.

Image

Thanks a lot for help guys. Well, I should try the internet connection wizard first, because eventually it turned out to be quite straight forward, but I guess I thought it will be more complicated, so I started with forum :)

3 final questions (for now!):
1. I'm not sure is it doing it everytime, but it happened twice already - it changes my keyboard layout language to English (US) while I set Polish at the beginning. Main language and time zone remain as set - only keyboard changes.
2. Alt+Tab switches windows in order, but what if I want to swap only between 2 windows - can I do that?
3. Where does the download/upgrade kiloBytes are stored, where do they go - to RAM? Because I downloaded a game (Medivia) and I run update, but none of the store areas seemed to be increasing...


Re: Failed to connect to wired network eth0

Posted: Fri Jan 20, 2023 11:23 pm
by williams2

swap only between 2 windows - can I do that?

If you are using jwm, you can switch desktop workspaces
by pressing alt+1 and alt+2 (and alt+3)

If you have 2 windows in your workspace,
alt+tab will switch between those 2 windows.
You can move windows to other workspaces
so that just the 2 windows are in one workspace.

You can configure your keymmaps in the menu.

You can select keymaps like this:

setxkbmap us

or like this:

setxkbmap 'us(alt-intl),pl(phonetic)' -option grp:lctrl_lshift_toggle

Where does the download/upgrade kiloBytes are stored, where do they go - to RAM?

It depends what software you are using, and how you configure it.

For example, the Mega add-on for Firefox downloads all of the file that you are downloadlng
to the ram that is assigned to Firefox, then it pops up the Save File window.

Where a game saves data, depends on the game.
Sometimes you can configure that.
Sometimes the data is stored in /root/, for exampe, in /root/.config/


Re: Failed to connect to wired network eth0

Posted: Sat Jan 21, 2023 3:13 am
by bigpup

This is info about adding software that you need to know about.
https://forum.puppylinux.com/viewtopic.php?t=1819

How save works
https://forum.puppylinux.com/viewtopic.php?t=6526

pupmode 13 operation applies to how you are using a Puppy Linux install.


Re: Failed to connect to wired network eth0

Posted: Mon Jan 23, 2023 6:32 am
by szept
williams2 wrote: Fri Jan 20, 2023 11:23 pm

If you have 2 windows in your workspace,
alt+tab will switch between those 2 windows.

Ok, but what if I have 3 or more windows in a single workspace and I would like to switch ONLY between 2 of them? Alt+tab switches between all of them, it's going one after another through every window.

You can move windows to other workspaces (...)

How do I move window to another workspace?

You can configure your keymmaps in the menu.

In SETUP => mouse/keyboard?

You can select keymaps like this:
setxkbmap us
or like this:
setxkbmap 'us(alt-intl),pl(phonetic)' -option grp:lctrl_lshift_toggle

Is that a command for terminal?

Where a game saves data, depends on the game.
Sometimes you can configure that.
Sometimes the data is stored in /root/, for exampe, in /root/.config/

I was thinking what if the app I want to download or its' update is bigger than my RAM or my save file? Will Puppy display a warning or get an error? I was updating the game called Medivia, the update size was almost 1GB, but when it was downloading it I haven't notice any increase of space on that nice display on the right hand side of my desktop. Btw - can I configure its' font colour, because I cannot really see titles with the yellow Puppy wallpaper.

bigpup wrote: Sat Jan 21, 2023 3:13 am

This is info about adding software that you need to know about.
https://forum.puppylinux.com/viewtopic.php?t=1819

How save works
https://forum.puppylinux.com/viewtopic.php?t=6526

pupmode 13 operation applies to how you are using a Puppy Linux install.

Rite, I'm gonna read that!
Thanks guys!


Re: Failed to connect to wired network eth0 (solved)

Posted: Mon Jan 23, 2023 7:13 am
by bigpup

Asking a bunch of different questions in one topic is just confusing and hard to follow for everyone.

Stop posting questions in this topic.

Start a new topic for each question and get specific answer to only it.

One question or issue per topic.

No limit on number of topics you can make.


Re: Failed to connect to wired network eth0 (solved)

Posted: Sat Feb 04, 2023 9:54 pm
by szept

I was thinking that new topic are the proper way for more questions, but was too lazy for that. It took me a while, but I finally posted new question in new topics. Check them out guys and thanks for help on this one!

Damian


Re: Failed to connect to wired network eth0

Posted: Mon Feb 06, 2023 5:56 pm
by szept
williams2 wrote: Fri Jan 20, 2023 11:23 pm

You can configure your keymmaps in the menu.

You can select keymaps like this:

setxkbmap us

or like this:

setxkbmap 'us(alt-intl),pl(phonetic)' -option grp:lctrl_lshift_toggle

Can you explain what did you mean by this keymmaps config?
I created separate post.
https://www.forum.puppylinux.com/viewtopic.php?t=7961