Fossapup won't go online

[redandwhitestripes]

Hi there, running from a USB stick on a desktop PC.I have an ethernet connection that is working fine on windows 10 and on Bionicpup also running from a USB stick boot.

None of the network wizards work. Running the advanced wizard with auto DHCP shows a successful connection but no page will load. This is a new challenge I have never faced before and other pups on the same desktop will connect.Here is the output from SNS, I have no idea if it helps or not

Information about this interface:
Interface: eth0 Driver: r8169 Bus: pci MacAddress: D0:50:99:67:91:FC
Description: RealTek RTL-8169 Gigabit Ethernet driver

dhcpcd[12685]: version 6.6.2 starting
dhcpcd[12685]: all: IPv6 kernel autoconf disabled
dhcpcd[12685]: eth0: adding address fe80::613a:f0e4:1afd:11d6
dhcpcd[12685]: if_addaddress6: Operation not supported
dhcpcd[12685]: script_runreason: /lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 1
dhcpcd[12685]: DUID 00:01:00:01:28:98:24:41:d0:50:99:67:91:fc
dhcpcd[12685]: eth0: IAID 99:67:91:fc
dhcpcd[12685]: eth0: soliciting a DHCP lease
dhcpcd[12685]: eth0: using IPv4LL address 169.254.1.197
dhcpcd[12685]: eth0: adding route to 169.254.0.0/16
dhcpcd[12685]: script_runreason: /lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 1
dhcpcd[12685]: forked to background, child pid 12816
dhcpcd[12826]: version 6.6.2 starting
dhcpcd[12826]: all: IPv6 kernel autoconf disabled
dhcpcd[12826]: eth0: adding address fe80::613a:f0e4:1afd:11d6
dhcpcd[12826]: if_addaddress6: Operation not supported
dhcpcd[12826]: script_runreason: /lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 1
dhcpcd[12826]: DUID 00:01:00:01:28:98:24:41:d0:50:99:67:91:fc
dhcpcd[12826]: eth0: IAID 99:67:91:fc
dhcpcd[12826]: eth0: soliciting a DHCP lease
dhcpcd[12826]: eth0: probing for an IPv4LL address
dhcpcd[12826]: eth0: using IPv4LL address 169.254.1.197
dhcpcd[12826]: eth0: adding route to 169.254.0.0/16
dhcpcd[12826]: script_runreason: /lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 1
dhcpcd[12826]: forked to background, child pid 12959


[norgo]

please post vendor and device ID of your network interface chip

[bigpup]

Here is the output from SNS

Is this info being provided by Fossapup64 9.5 or from one of the other Puppy versions that is working?

[ozsouth]

@redandwhitestripes - I assume you also tried frisbee. Even though mainly for wireless, works for ethernet too (untick wireless options, then change interface). I find it works best all round.

[rcrsn51]

dhcpcd[12826]: eth0: using IPv4LL address 169.254.1.197

The bogus 169.254.x.y number indicates that something went wrong when your machine tried to acquire an IP address via DHCP.

The usual culprit is a faulty driver, but you are using the standard ethernet r8169 driver. It might be a timing problem.

When it fails, open a terminal and type: dhcpcd eth0

[redandwhitestripes]

please post vendor and device ID of your network interface chip

Windows 10 says "Realtek PCIe GBE Family Controller #4"

Here is the output from SNS

Is this info being provided by Fossapup64 9.5 or from one of the other Puppy versions that is working?

From Fossa

@redandwhitestripes - I assume you also tried frisbee. Even though mainly for wireless, works for ethernet too (untick wireless options, then change interface). I find it works best all round.

I tried them all. I'm also a fan of frisbee when I set up a static IP I find it easiest. (I haven't tried static ip in this case though)

dhcpcd[12826]: eth0: using IPv4LL address 169.254.1.197

The bogus 169.254.x.y number indicates that something went wrong when your machine tried to acquire an IP address via DHCP.

The usual culprit is a faulty driver, but you are using the standard ethernet r8169 driver. It might be a timing problem.

When it fails, open a terminal and type: dhcpcd eth0

Thank you, that's interesting. I will report back.

[bigpup]

You may think, asking if that info is from Fossapup, is a dumb question.
But you talk about other Puppy versions, that work, and you do not specifically say the info is from what.
How do we know it is not from one that works?
I have had issues like this, where the info provided by the bad OS, is little to none. Not as complete as what you posted.
I do not assume anything.
This is proven every day.
What you do not tell us, is usually the clue to fix it.

If this is a fresh new install of Fossapup.

If you find nothing that seems to help.

I would do a fresh new download of the Fossapup64 9.5 iso.
A new format of the partition the Fossapup install is going to go.
Do a new install from this new downloaded iso.

Strange things like this have been fixed by doing this.
Bad downloads and bad installs do happen.

If you download the iso to any location that is a Windows format and has been used by Windows OS.
There is a good chance the iso is fragmented.
This can cause issues when trying to use this iso.
Defrag the location before storing a Puppy iso on it.
Same applies to installing on a Windows format.

If nothing else, this eliminates one possible cause.

Because Fossapup64 9.5 can be installed as minimum or complete.
Is this a complete install?
Everything in the iso is in the install?

[ozsouth]

@redandwhitestripes - would please run the following in a terminal & post output here (first letter is lower case L):
lspci -nn | grep thernet

NOTE: It is the 9 character code in square brackets I'm looking for.

Also, as @rcrsn51 says, 169.x.x.x range indicates an error, so static ip worth trying.

[Clarity]

@redandwhitestripes hummm??? Works before with other PUPs but not now... ??? Not getting an IP address ???

1. Check the PC's LAN cable to see if it is plugged in securely on both ends

2. Restart your LAN's router-modem

3. Rerun PUP's Menu>Internet Connection Wizard (P.S. I would use its "Network Wizard" and its
   'Test Interface' feature to insure the PC sees your LAN.)

[bigpup]

One thing to try to eliminate one possible cause.

Have the firewall disabled, when you try to make the connection setup.
Turn it back on after the setup is configured and working.

The firewall active, can cause first time connection setup problems.

[bigpup]

Here is the output from SNS from Fossapup.

How about posting this output, from one of the connections in a Puppy version, where it works.

Maybe comparing the two, will identify something.

Pup-Sysinfo->Devices->Network
Post what that provides for info.

[redandwhitestripes]

You may think, asking if that info is from Fossapup, is a dumb question.
But you talk about other Puppy versions, that work, and you do not specifically say the info is from what.
How do we know it is not from one that works?
I have had issues like this, where the info provided by the bad OS, is little to none. Not as complete as what you posted.

I completely understand and I agree, never assume anything, especially with desktops. I managed to get it online yesterday and I will check and report back on the repeat attempt. Thank you for your help.

[redandwhitestripes]

So I may have discovered the root of the problem, after experiencing the same issue with Linux Mint. It seems that when dual booting with Windows and Linux, Windows can alter settings on the ethernet driver that Linux cannot reset. This happens when rebooting into Linux rather than starting from a full power off cycle, which explains why the problem could seem random to unaware users like me.

Other forums have suggested changing the power management settings on the ethernet driver in windows (basically, unchecking all options), unchecking fast boot options in windows or BIOS and auto resetting the ethernet on boot for Linux.

Hope this helps someone.

[Clarity]

Thanks for your finding @redandwhitestripes

I have a PC platform, too, where it, too, requires a power-cycle for all features to report-in correctly for a boot.

MY PC is too old and its firmware solely need an update which the manufacturer no longer provides.

You might check to see if you have firmware updates available for your PC. If so, the updates "MAY" resolve the experience.