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

Summary of echo-icon-theme report on Virtual FUDCon

It was my first even conference on Virtual FUDCon which greatly saved time and money. In summary, echo-icon-theme will not be ready for Fedora 8 given the time constrains. Its guideline needs a rewrite started by Martin Sourada. The icons are now residing on echo-icon-theme repository which facilitates the access for contributors looking to add/update the icons. It also means the wiki page for EchoDevelopment will no longer upload icons and will serve as reference. The mouse cursors are not in the repository yet but will be available shortly. Mairin, Fedora Artwork team leader, suggested to use Tango guideline for icons smaller or equal than 24x24 while keeping the isometric view for 32x32 and above. Demitri Glezos thanked the team for the use of icons on his Transifex project . The set of icons is roughly 40 percent complete and users of other desktop environment like KDE are encouraged to test them and provide ticket to track issues. Be in mind the echo-icon-theme division tea...

Using AMD RX Vega driver OpenCL on Fedora 29

The Raven Ridge APU is very capable processor to handle OpenCL inside some applications like Blender, Darktable and Gimp. Unfortunately, the current implementation from Mesa, clover, stuck to 1.3, is not supported. AMD released their driver 18.40 with OpenCL2.0+ targeting only Red Hat Enterprise Linux/Cent OS 6.10 and 7.5 in addition of Ubuntu LTS. The good new is the former rpm format can be used on Fedora. The graphical part of Raven Ridge is Vega 8, basically a cut-down of Vega56 or Vega64 meaning choosing either driver for RX Vega . The instruction is provided for extracting the rpm files but here is  some requirements for OpenCL: kernel-devel (provided by Fedora repository) amdgpu-dkms dkms libopencl-amdgpu-pro opencl-amdgpu-pro-icd Once done, applications needing OpenCL will automatically detect the driver located on /opt/amdgpu/lib64 . Blender will list as unknown AMD GPU and Darktable will enable it. OpenCL from official AMD driver enabled on Darktable ...

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