Skip to main content

No network on Fedora 9 x86_64

Using a x86_64 DVD version of Fedora 9, I have installed the system and noticed an issue: the network is not active when trying to use third-party repository. For some unknown reason, the network is not using Ethernet despite manually setting the IP. I had submitted a bug report and followed suggestion: still no online access even with NetworkManager disabled. The same issues also occured on... Fedora 8. The Ethernet adapter is a integrated Marvell Yukon on the motherboard, it ran fine on Fedora 7 and i386 version of Fedora 9 using network install. Hopefully this issue will be resolved soon.

Comments

Anonymous said…
I think my system had a different issue, with a different name. Maybe related?

I didn't file a bug report.

I installed the Pre-Release of x86_64 from a USB drive, started some updates, killed it... went to the terminal, did a yum update, then killed that in the middle.

Now... my machine still connects to the Internet, but I get a message that there's no network connection... and my machine won't update at all... something about not having repos or something.

Don't really have time to diagnose further at the moment, but maybe this little tidbit will help. I'll probably end up re-installing from the release, and see how that goes. I figured I did some stuff I "shouldn't" do.
I have reinstalled the final release of x86_64 from DVD, got the right gateway. NetworkManager finally accept the connection but no access to the Internet.
Unknown said…
Yeah I've got the same problem. I've installed 3 machines using fedora. I have done an i386 and 2x 64 bit systems. The i386 seems to work perfectly but under the 64bit install, both machines are having Network Manager problems. I've edited the settings a number of times and no matter what I do, the system won't boot with the Ethernet adaptor coming up. I am able to edit and put in the settings correctly, command line 'ifup eth0' works fine and gives me a pingable network but not on boot. I tried by-passing it but it seems the Network manager is ingrained into Fedora and such things as Firefox then tell me that it can't see the Network settings. Seems to be a 64bit problem? Just thought I'd relay my experiences. Anyone got any ideas?
Definitively a x86_64 issue. Matt, as workaround try to boot to the BIOS PC to disable 4GB RAM support. It looks like a bug related to the Ethernet driver that don't support 4GB RAM (skge in my case with Marvell Yukon Gigabit). Could you post what you got on bug and #446428 and #447489?
Anonymous said…
I had problems with a non 64 bit install and finally did this:
Click on System and then Administration. Select 'Network', add your network devices here (if not already in) and activate them. I had to have my ISP's DNS servers in the configuration for mine to work. Make sure when you set them up that you do not check the box that says Controlled by network manager.
Next go back to System and Administration and select Network Device Control. Make sure your device shows here and is active. After this is done, check the icon on the toolbar and see if it becomes active and allows internet access. Mine gave me fits but I now have internet and am moving on to the next problem.....updates won't install and cannot install from root as it says I don't have authority to do so. Go figure.
Anonymous said…
From Mauriat Miranda website::

Summary-
If you are using wired only networks, this will solve your problem. If you use wireless and wired devices you will need to investigate this further, but you can keep NetworkManager enabled and enable the original network service to see if the problem is resolved.


WIRED ONLY NETWORK:
First disable NetworkManager and prevent it from automatically loading:

"sudo /etc/init.d/NetworkManager stop"
"sudo /sbin/chkconfig --level 35 NetworkManager off"

Next, configure your network settings:
"sudo system-config-network"

Next, enable the service and make sure it loads at next boot:
"sudo /etc/init.d/network start"
"sudo /sbin/chkconfig --level 35 network on"

Finished! Reboot.

WIRED & WIRELESS
First leave NetworkManager enabled

Next, configure your network settings:
"sudo system-config-network"

Next, enable the service and make sure it loads at next boot:
"sudo /etc/init.d/network start"
"sudo /sbin/chkconfig --level 35 network on"

Finished! Reboot.

See
http://www.mjmwired.net/resources/mjm-fedora-f9.html for more tips. He is a knowledgeable person.

-e
Jeff Moss said…
Thanks for the last anonymous comment pointing at Mauriat Miranda website...worked a treat for me on my AMD x86_64 Opteron box running fedora 9.

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