Skip to main content

No network on Fedora 9 x86_64 follow up

Following my post related to NetworkManager. I have found out about the workaround. If you have x86_64 system with 4GB support enabled, you should disable it in order to make NetworkManager work. I am not sure if that bug affects other distributions so, possibly the bug may be related to the x86_64 kernel. Let see if my theory can be verified.


Eugene said…
That's strange. I am using Fedora 9 x86_64 with 4GB RAM, and I don't have any problem with NetworkManager.
Anonymous said…
same here.

Currently using x86_64 with 4gb + networkmanager. No such issues.

Its a Thinkpad T61 with Intel 3945ABG wireless
Further investigation, it appears the bug is more kernel related than NetworkManager with the use of skge module. My system uses Marvell Yukon Ethernet integrated in the Gigabyte GA-K8NSC-939. Maybe the skge module does not support 4GB so I have submitted the bug for that reason.
jar said…
I had the exact same problem with very similar hardware. Your post helped me get some ideas, I tried a bunch of different things. Did some packetsniffing etc.

Turns out it is something specific to the Marvell network card. I have two NICs on my motherboard and I tried the other one (Nvidia) and network seems to work perfectly! So maybe your problem could be fixed/worked around by trying a different network card.
I took an old Dlink Ethernet card, enabled 4GB RAM support on the motherboard and now runs Fedora 9. The issue related to Marvell network card about the 4GB RAM is confirmed thus definitely a kernel bug.
Jake_H said…
Fedora 9 x86_64 - The network icon next to my name and date always shows that there is no network available, and I usually have to manually restart networking a few times, click on the icon and enable and disable networking a few times, as well as fiddle with "work offline" back and forth in my Firefox browser. Sometimes it starts working quickly, other times I have to play with it for 10 minutes before I can reach the internet. Regardless, the icon always shows up as disconnected even if I am able to access the network. A search of the internet has not assisted me in my quest to resolve the issue. Can anyone help?
Could you provide your Ethernet card specification?
Anonymous said…
Good work people. I have a GA-K8NSC-939 + Athlon 3200+ and 4GB. I'm running Ubuntu 8.04 wuth an updated 2.6.24-17 64-bit kernel. I see the same problem.
When I upgraded from 2GB to 4GB, I went into the BIOS, Ctrl-F1 to get to the advanced chipset features, then enabled 4G RAM support. After that, when I booted I couldn't access the network. Interestingly, there was a boot-time message from the kernel
skge eth1: enabling interface
, so I didn't look there for the problem.

After reading the posts here I went back, disabled 4G support and got my network back - at the cost of a few hundred MB of RAM. The kernel now only sees 3584MB instead of the 4096MB it saw before.


Popular posts from this blog

Running Sapphire Radeon RX 560 on Fedora 27 beta (follow up)

Following the previous blog and some investigation, it turned out the kernel package from Mystro256 COPR repository based on agd5f kernel branch (one of AMD developers) resolves the blank screen issue. That could trigger a problem for users having a new AMD graphic hardware so perhaps a warning should be written on the release. Perhaps having one of contributors be part of kernel team bringing these improvement until those patches arrive to the mainline kernel for a better user experience.

Past the issue, the desktop experience with Radeon RX 560 was tremendously improved compared to the retired GTX 460 v2. Gnome on Wayland on Fedora runs smooth showing how far the open source amdgpu driver went through compared to previous years. That was also the opportunity to run a vulkan based smoke test demo on RADV, which is a counterpart of glxgears.

Overall the card is excellent once missing software are installed.

Running Sapphire Pulse Radeon RX 560 4GB on Fedora 27 Beta

I bought a Sapphire PulseRadeon RX 560 4GB to replace the broken Nvidia GTX 460 v2 after a long years of service. It is then my first ever dedicated AMD based video-card for a desktop.

The boot sequence on Fedora 27 hit a problem: a plain blank screen suggesting the card is not yet supported. Looking at Phoronix website revealed one of possible requirement missed: LLVM 5.0 which is currently not available to Fedora repository save a failed built. I filed a bug report to address the issue. Hopefully that will land on time for the official release of Fedora 27.

Vulkan now fully functional on ASUS X550ZE

Running Fedora 28 Design Suite post beta shows a nice surprise: Vulkan with RADV is fully functional on both South Island (Hainan) and Sea Island (Kaveri) cards on ASUS X550ZE laptop. amdgpu driver is needed to enable the feat in combination of boot parameter (cik.amdgpu_support=1 cik.radeon_support=0 si.amdgpu_support=1 si.radeon_support=0)

Some minor issues need be to addressed like occasional glitches. Otherwise the performance is stable enough for dail use.