Cannot connect eth0 {SOLVED}

[PeteAir]

This is a DELL™ OPTIPLEX™ 790 with intel onboard nic e1000e, I tried all 3 connection managers. SMS says it does not exist. Frisbee says eth0 is active but no connect. Wizzard Identifies it and says connection, but no connect. When I run dmesg | grep -i firmware iget ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored.
All sfs files are in the correct place and show Loading Done in green at boot up,
This is on fossa64/ and win10 this adapter works fine.
What next to try? THanks pete

[mikeslr]

"What can I try next?"

rerwin --the creator of most of Puppys network applications-- could better answer this. But there is a* newer version of Simple_network_setup than Fossapup64 has as a built-in; and a recent and a Network_connect_update-20220407. https://www.forum.puppylinux.com/viewto ... 2241#p2241. I didn't check whether the frisbee whose download is linked from that post is also newer than Fossapup64's builtin version.
I think stemsee's Simpler Network App is also supposed to b able to handle ethernet. The latest version can be obtained from this post. viewtopic.php?p=59427#p59427
If you have to download packages using Windows, do not use Windows to move them. Rather boot into Puppy and file-browse to their download location. Linux is case sensitive. And AFAIK, Windows still screws up a file's name when copying/moving it.

-=-=-=-=-
* The post actually has links to two Simple_network_setups, versions 2.4.2 and 3.3. I think both are newer than Fossapup's builtin. A couple of post from here, https://www.forum.puppylinux.com/viewto ... 433#p46433 down explain their differences.

[ozsouth]

@PeteAir - An updated driver is available here: viewtopic.php?p=51112&sid=395c860c12400 ... 5b4#p51112

[PeteAir]

Thanks ozsouth, I just installed the new driver and the updated sns and connector but no change, no eth0,

[ozsouth]

@PeteAir - I can't find later source code & assume you used the fossapup64 specific .pet, so if no ethernet device showing in any of the 3 connection tools, I would usually query adaptor type. What does terminal command lspci -nn (that starts with lowercase L)
reveal, regarding network items? The output code [xxxx:xxxx] would be useful.

EDIT: I confirm e1000e is the correct driver. My updated driver (which reports 'taints kernel') should work, so obviously there is some other problem.

[PeteAir]

ozsouth,
lspci -nn Gives 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) [8086:1502] (rev 04)
Thanks so much for the help\
pete

[xenial]

@PeteAir2
Please don't take this as patronising but did you actually "load" the module for the ethernet.?.I know when i first started with fossapup i had to first load my broadcom driver for the interface to be "seen" by the network manager and initially like yourself i incorrectly assumed fossapup was not going to connect because silly me had overlooked actually loading the module rather than it being done automatically.

I used the 3rd option "network wizard" at the bottom of the list and then i performed a "scan" to scan for available interfaces.
Sorry if this is not much help to you but i hope (prays) that it points you in the right direction.
best of luck.

[PeteAir]

Xenial, I did use the 3rd option and selected scan and it said it did not find a new adapter.
thanks pete

[xenial]

@PeteAir
Are the modules loaded.?

[oldaolgeezer]

Hi PeteAir:

While you are waiting for more detailed help, I'll report this:

Puppy's Hardinfo utility reports that I have a DELL OPTIPLEX 9010 desktop with Intel e1000e ethernet
on an "Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)"

On my fossapup64_9.5, if I run the command:

dmesg|grep e1000e

I see:

e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) xx:xx:xx:xx:xx:xx
e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: 1011FF-0FF
e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

and if I run rcrsn51's "standard diagnostic test for wifi":

dmesg | grep -i firmware

I see nothing, perhaps indicating there is no firmware or maybe none is needed.

My e1000e (on my DELL OPTIPLEX 9010) seems to work fine
in fossapup64_9.5 or slacko64-8.2 or bionicpup64-8.0

What I have running in my fossapup64_9.5 Linux 5.4.53 (note the date and size):

ls -la /lib/modules/5.4.53/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
277304 Jul 26 2020 /lib/modules/5.4.53/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko

What is in the e1000e-3.8.4-k5453.pet (For fossapup64-9.5 with original 5.4.53 kernel only):

288904 2022-02-27 20:17 ./e1000e-3.8.4-k5453/lib/modules/5.4.53/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko

Maybe this will help somehow....

[rerwin]

@PeteAir,
As the maintainer (not creator) of the Puppy network managers and default ethernet starter, I would like to see some logs so I can look for clues. We should be able to depend on the default starting of wired ethernet and avoid complicating things with the network managers.

The simplest way to do this is to boot with pfix=ram or "option 0" if you already have multiple pupsave files or folders for FossaPup, then in a terminal enter:
pdiag
and have it save a collection of diagnostic data. (The "default" will not work in an existing Puppy environment if you have ever used the other managers in it, so start "fresh".)

The result is a zipped "pdiag..." file that you can attach to either a post here a PM to me (after saving it somewhere and getting on the internet somehow).

I would be looking in the /tmp/bootsysinit.log and /var/log/messages files. If you prefer, you can post/send just those files, although the pdiag is easier and more thorough.

Richard

[PeteAir]

Xenial, At boot the screen says loading each of the sfs files done in green.

[bigpup]

This is my Fossapup64 9.5 install using the same driver you say you need to use.
So it works for me.

▶—— Network Devices ——◀

Onboard - Ethernet
• Kernel Driver: e1000e
• Memory Used: 168.00 KB
• Path: /lib/modules/5.4.53/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
• Driver Version: 3.2.6-k
• Description: Intel(R) PRO/1000 Network Driver

I use the Network Wizard to setup the connection.
Select the listed ethO
.

Screenshot.jpg (51.87 KiB) Viewed 1290 times

.
Select AUTO DHCP
.

Screenshot(1).jpg (60.87 KiB) Viewed 1290 times

.
After is gets a DHCP connection it should report successful.
Say yes to keep this configuration.
.

Screenshot(2).jpg (22.03 KiB) Viewed 1290 times

.
Back at main window select done.

At next window select set as default.

[PeteAir]

oldaolgeezer, Your Dell specs are the same as my 790 and here is what I get
root# dmesg | grep e1000e
[ 6.436395] e1000e: loading out-of-tree module taints kernel.
[ 6.437038] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.4-NAPI
[ 6.437039] e1000e: Copyright(c) 1999 - 2020 Intel Corporation.
What the heck is out-of-tree module taints kernel.???

[PeteAir]

Hey bigpup, I have done exactly as you put it and it states sucessful but it is not

[bigpup]

What is telling you it is not successful?
You cannot access the internet with a browser?

[oldaolgeezer]

Hi PeteAir:

I noticed there seem to be a number of hits from Googling the string:

"loading out-of-tree module taints kernel e1000e"

[PeteAir]

rerwin » Tue Jun 14, 2022 10:39 am I just saw this reply and I will work on it
Thanks Pete

[PeteAir]

bigpup, the taskbar icon states Active interface: None
and browser no go.
I have fossa on 3 laptops with no probs, and it was on this dell until last week when Ms/Win10 stated that it detected disk errors abd I needed to reboot so it could FIX them. I did and MS fixed it with NO BOOT to the drive. I loaded my backup drive win10 is fine but fossa boots fine but no network, I loaded the Live CD and it boots fine but no net.
The only reason I am trying to save this fossa is I have it configured so that I can see it. My eyes have cataracts,
I put the live bionicdog in and it works fine with net.
Thanks pete

[Clarity]

Hi @PeteAir
After you get 'success', Can you post the output of this
root# ethtool eth0

P.S. On the Wizard that @bigpup shows above, did you also click the "Test button' to see its result?
And, can you "ping" any home LAN devices from this 'bad' PC?

Curious

[PeteAir]

clarity I can get success in wizzard only, and not the taskbar icon, yes abd test did nothing. but here iseth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: on (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected:

[PeteAir]

Clarity right now it shows axtive interface eth0 but the ip is 169.254;231.230 no pings

[rerwin]

it shows active interface eth0 but the ip is 169.254;231.230

That's the problem! The router or DNS is not returning a valid IP address. It may be a timing issue.

I have that problem on my 2006 PC and have been adjusting things to accommodate that, by inserting waits and retrying later.

The network_connect_update .pet package does a retry, which works sometimes. But it waits about 20 seconds, so be patient.

Install that package in the "fresh" Puppy I suggested and reboot, saving that environment in a pupsave. Skip the "pdiag" for now. I may have you make some edits to one of the files from the package, so, you can keep that new pupsave awhile.

[PeteAir]

Richard, this is a strange setup. I pull eth thru a linksys switch thats connected to a router/wifi bridge that gets wifi from a 4g Hotspot. This is the only system to have probs with the setup. I will change routers tonight and try that.
thanks. pete

[mikewalsh]

Richard, this is a strange setup. I pull eth thru a linksys switch thats connected to a router/wifi bridge that gets wifi from a 4g Hotspot. This is the only system to have probs with the setup. I will change routers tonight and try that.
thanks. pete

.....and you wonder WHY you're having issues? Jeezus H. f**kin' Christ alive, what a convoluted setup..!

Yeah, I occasionally get that issue as well. I get round it by setting consecutive 'static IPs' across the entire kennels....and also set CloudFlare as my DNS resolver while I'm at it. (Well; it works for me, anyroad.)

Richard's right, though. Ethernet should be dependable, and just "work".

-----------------------------------

Interesting you say ethernet works straight off for you in Bionic64. The Realtek ethernet adapter in this new-ish HP desktop rig point blank refuses to connect. Doesn't want to know......and we must have tried just about everything we could think of (and then some..!) Luckily, it also has a combo wireless/Bluetooth chip (which can only do one thing at a time. I never use Bluetooth, so it does duty as a wireless adapter to give me an internet connection.....though as I've remarked on here before, I still can't get my head round the whole concept of desktop PCs with wireless adapters!)

Seems like some weird Frankenstein 'hybrid'! Yet Bionic64 is the only one out of the entire kennels to be 'ultra-picky' like that. The rest of 'em are perfectly happy for the same Ethernet adapter to 'do its thing'.

Sod's law, huh?

Luckily, ozsouth took pity on me, and whipped together a .pet for a suitable wireless driver. Which - cross fingers! - to date is working fine. (Cheers, Oz! )

Mike.

[Clarity]

Hi @PeteAir and thanks for your description.

I understand you wired configuration: What you are saying is that all the other machines get their IP personality from the router including those connected via the LAN switch, and that this PC does not. Correct?

I have a couple question as I'm sure @rerwin does too:

• Has this PC connected via other Operating system(s)/distros using the current ethernet wire before?

  • If so, I have a simple checklist to check.

  • If not, I also have Aa checklist.

Which?

[williams2]

[ 6.437038] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.4-NAPI
[ 6.437039] e1000e: Copyright(c) 1999 - 2020 Intel Corporation.
What the heck is out-of-tree module taints kernel.???

It just means that using the Intel(R) PRO/1000 Network Driver- 3.8.4-NAPI e1000e: Copyright(c) 1999 - 2020 Intel Corporation
which does not have a GPL open source license
makes the kernel also not 100% GPL open source

So using that propriety Intel(R) PRO/1000 Network Driver
makes your Puppy OS not 100% GPL
because the Linux kernel is not 100% GPL.

So, "taints" refers to the GPL open source license.

If this driver module is not working,
but the other Pups do work,
maybe you need to blacklist this Intel driver?

[PeteAir]

Thanks wizzard, ozsouth, richard, bigpup. williams2. clarity, Mike Walsh and the entire Puppy Forum for the great help that has been noted numerous times around the world. I went to my network spares box and dug out a realtek wireless pci card, stuck it in, booted fossa bang installed and setup with sns in 59 secs. And I worked for 2 days on the intel eth. Goes to show everything does not work with everything, ya gotta adapt.
Thanks pete

[mikewalsh]

@PeteAir :-

Just as a postscript - and to confirm what Richard said about an invalid IP addy above - here ya go:-

https://askleo.com/why_cant_i_connect_w ... p_address/

It's explained a few things for me as well..! ("AskLeo" actually looks like quite a good "problem-solver" site, if you like things explained in plain, easy-to-understand English...)

Mike.

[PeteAir]

Yes mike, I read a lot of your posts because you state things in "easy for old guys to understand". Even though I have used Puppy since version 4 came out my retention and thought process is not the same as it once was.
thanks, pete