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.

Comments

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.
Jiggy 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.
Anonymous 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.


Pete

Popular posts from this blog

Drawing hair with Inkscape

My very first online tutorial is an adaption from Chris Design Drawing Hairs article using both Path and Path Editor tools which requires Inkscape 0.47 or newer. Start-up Inkscape application which should open a new blank page and set the document into landscape.  Create a path Select the bezier tool or press either Shift+F6 or B on the keyboard. Draw a line to approximately 800px or more. You can also use rectangle tool ( R or F4 as shortcut key) as a thin line illustrated in grey. While the line is selected, convert into path from the menu Path -> Stroke to Path or press Ctrl+Alt+C on the keyboard. For the rectangle, Path -> Object to Path or Ctrl+Shift+C . The result will show grey diamonds on each corner. Create a pattern On the menu, Extensions -> Modify Paths -> Add Nodes . Set the Max Segments Length to 5px. On the menu Extension -> Modify Paths -> Jitter Nodes . Leave the default settings and apply effects.

HP, Linux and ACPI

 Majority of HP hardware running on Linux and even Microsoft reported an issue related to a non-standard compliant ACPI. Notable message below repeats at least three times on the boot: 4.876549] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190215/dsopcode-198)  [ 4.876555] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190215/psparse-529)  [ 4.876562] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190215/psparse-529) The bug is a known for years from which Linux kernel team are unable to fix without the help of vendor i.e. HP. Here is a compilation of reports: BIOS error: The BIOS in this system is not fully ACPI compliant. ACPI BIOS ERROR (blue screen) on startup   ACPI bad works with Linux    The good news is some errors seems harmless. Unfortunately, such errors displayed the quirks approach used by

Detailing the installation of AMD OpenCL rpm for Fedora

Revisiting the previous blog and freshly reinstalling Fedora Design Suite due to a busted boot, I look at the official guideline from AMD Driver for Red Hat Enterprise Linux 7.2 and write a way to improve the process of installing on Fedora 29 in this example. Extracting the tarball contains the following: amdgpu-install amdgpu-pro-install symlink to amdgpu doc folder repodata folder RPMS folder containing rpm package Executing the command ./amdgpu-install -opencl=pal --headless sadly failed on Fedora on that line: ./amdgpu-install -y --opencl=pal --headless Last metadata expiration check: 0:30:51 ago on Mon 19 Nov 2018 07:13:43 PM PST. No match for argument: amdgpu Upon closer look, the script failed to created a temporary repository on /var/opt/amdgpu-pro-local probably explaining why amdgpu metapackage name failed to display. Someone should investigate and provide a fix. At least, we find out Fedora support is available but unofficial. Due to its design, Gnome