Hi,
I'm setting up a reasonably old PC with FC5 to use primarily as a test server for web development. A few days ago i installed FC5 and spent 2 days trying to configure a wireless network card. Having finally compiled the kernel with the additional drivers for the wireless card i got it up and running and everything was fine. The box was hidden away in a corner (where my partner couldn't see it) and all was good. This morning however the hard disk went in the machine, so i had to purchase a new disk and start all over again.
So my present situation: Not wanting to go through the pane of setting up a wireless card again, i thought I'd save myself a great deal of hassle and put a standard wired ethernet card in. So i did, a Netgear GA311 which i believe uses the Realtek 8169 chip set. I'd already checked online and everyone reported this card as working hassle free under fedora. But not for me. On boot I see the message:
r8169 device eth0 does not seem to be present, delaying initialisation
I get the same message if i do ifup eth0. ifconfig -a does not list eth0.
Using the GUI tool Network Manager the device can be seen under hardware.
So the network card not working is the first problem, any thoughts gratefully received.
In order to try and fix this i have downloaded linux drivers from the Realtek site. To install i need the kernel source, so i also downloaded kernel-devel-2.6.15-1.2054_FC5.i686.rpm. When i try to install this rpm i get:
-> rpm -Uvh kernel-devel-2.6.15-1.2054_FC5.i686.rpm error: cannot create %sourcedir /usr/src/redhat/SOURCES.
Any thoughts?
Many thanks, Greg.
On Thu, 2006-09-28 at 16:49 +0100, Greg Frith wrote:
Hi,
I'm setting up a reasonably old PC with FC5 to use primarily as a test server for web development. A few days ago i installed FC5 and spent 2 days trying to configure a wireless network card. Having finally compiled the kernel with the additional drivers for the wireless card i got it up and running and everything was fine. The box was hidden away in a corner (where my partner couldn't see it) and all was good. This morning however the hard disk went in the machine, so i had to purchase a new disk and start all over again.
So my present situation: Not wanting to go through the pane of setting up a wireless card again, i thought I'd save myself a great deal of hassle and put a standard wired ethernet card in. So i did, a Netgear GA311 which i believe uses the Realtek 8169 chip set. I'd already checked online and everyone reported this card as working hassle free under fedora. But not for me. On boot I see the message:
r8169 device eth0 does not seem to be present, delaying initialisation
I get the same message if i do ifup eth0. ifconfig -a does not list eth0.
Using the GUI tool Network Manager the device can be seen under hardware.
So the network card not working is the first problem, any thoughts gratefully received.
In order to try and fix this i have downloaded linux drivers from the Realtek site. To install i need the kernel source, so i also downloaded kernel-devel-2.6.15-1.2054_FC5.i686.rpm. When i try to install this rpm i get:
-> rpm -Uvh kernel-devel-2.6.15-1.2054_FC5.i686.rpm error: cannot create %sourcedir /usr/src/redhat/SOURCES.
You must be root to do the "rpm -Uvh" (I'd recommend "rpm -ivh"). Also note that the "kernel-devel" RPM is NOT the kernel source RPM. It is only the kernel headers..and is usually enough to build most 3rd party drivers.
---------------------------------------------------------------------- - Rick Stevens, Senior Systems Engineer rstevens@vitalstream.com - - VitalStream, Inc. http://www.vitalstream.com - - - - Beware of programmers who carry screwdrivers - ----------------------------------------------------------------------
On 28 Sep 2006, at 18:25, Rick Stevens wrote:
On Thu, 2006-09-28 at 16:49 +0100, Greg Frith wrote:
Hi,
I'm setting up a reasonably old PC with FC5 to use primarily as a test server for web development. A few days ago i installed FC5 and spent 2 days trying to configure a wireless network card. Having finally compiled the kernel with the additional drivers for the wireless card i got it up and running and everything was fine. The box was hidden away in a corner (where my partner couldn't see it) and all was good. This morning however the hard disk went in the machine, so i had to purchase a new disk and start all over again.
So my present situation: Not wanting to go through the pane of setting up a wireless card again, i thought I'd save myself a great deal of hassle and put a standard wired ethernet card in. So i did, a Netgear GA311 which i believe uses the Realtek 8169 chip set. I'd already checked online and everyone reported this card as working hassle free under fedora. But not for me. On boot I see the message:
r8169 device eth0 does not seem to be present, delaying initialisation
I get the same message if i do ifup eth0. ifconfig -a does not list eth0.
Using the GUI tool Network Manager the device can be seen under hardware.
So the network card not working is the first problem, any thoughts gratefully received.
In order to try and fix this i have downloaded linux drivers from the Realtek site. To install i need the kernel source, so i also downloaded kernel-devel-2.6.15-1.2054_FC5.i686.rpm. When i try to install this rpm i get:
-> rpm -Uvh kernel-devel-2.6.15-1.2054_FC5.i686.rpm error: cannot create %sourcedir /usr/src/redhat/SOURCES.
You must be root to do the "rpm -Uvh" (I'd recommend "rpm -ivh"). Also note that the "kernel-devel" RPM is NOT the kernel source RPM. It is only the kernel headers..and is usually enough to build most 3rd party drivers.
Thank Rick,
My apologies, I have installed the kernel-devel package, i get the error when trying to install kernel-2.6.15-1.2054_FC5.src.rpm. I am also doing this as root. So,
[root@wharfe]: rpm -ivh kernel-2.6.15-1.2054_FC5.src.rpm error: cannot create %sourcedir /usr/src/redhat/SOURCES.
- Rick Stevens, Senior Systems Engineer rstevens@vitalstream.com -
- VitalStream, Inc. http://www.vitalstream.com -
-Beware of programmers who carry screwdrivers -
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
On Thu, 28 Sep 2006 18:32:04 +0100 Greg Frith gfrith@gmail.com wrote:
On 28 Sep 2006, at 18:25, Rick Stevens wrote:
On Thu, 2006-09-28 at 16:49 +0100, Greg Frith wrote:
Hi,
I'm setting up a reasonably old PC with FC5 to use primarily as a test server for web development. A few days ago i installed FC5 and spent 2 days trying to configure a wireless network card. Having finally compiled the kernel with the additional drivers for the wireless card i got it up and running and everything was fine. The box was hidden away in a corner (where my partner couldn't see it) and all was good. This morning however the hard disk went in the machine, so i had to purchase a new disk and start all over again.
So my present situation: Not wanting to go through the pane of setting up a wireless card again, i thought I'd save myself a great deal of hassle and put a standard wired ethernet card in. So i did, a Netgear GA311 which i believe uses the Realtek 8169 chip set. I'd already checked online and everyone reported this card as working hassle free under fedora. But not for me. On boot I see the message:
r8169 device eth0 does not seem to be present, delaying initialisation
I get the same message if i do ifup eth0. ifconfig -a does not list eth0.
Using the GUI tool Network Manager the device can be seen under hardware.
So the network card not working is the first problem, any thoughts gratefully received.
In order to try and fix this i have downloaded linux drivers from the Realtek site. To install i need the kernel source, so i also downloaded kernel-devel-2.6.15-1.2054_FC5.i686.rpm. When i try to install this rpm i get:
-> rpm -Uvh kernel-devel-2.6.15-1.2054_FC5.i686.rpm error: cannot create %sourcedir /usr/src/redhat/SOURCES.
You must be root to do the "rpm -Uvh" (I'd recommend "rpm -ivh"). Also note that the "kernel-devel" RPM is NOT the kernel source RPM. It is only the kernel headers..and is usually enough to build most 3rd party drivers.
Thank Rick,
My apologies, I have installed the kernel-devel package, i get the error when trying to install kernel-2.6.15-1.2054_FC5.src.rpm. I am also doing this as root. So,
[root@wharfe]: rpm -ivh kernel-2.6.15-1.2054_FC5.src.rpm error: cannot create %sourcedir /usr/src/redhat/SOURCES.
- Rick Stevens, Senior Systems Engineer
rstevens@vitalstream.com -
- VitalStream, Inc.
Ran into a problem setting up an ether net bridge in an old computer. My guess in the end is the problem was actually a problem associated with the mother board chipset or bios rather than any of the cards I was using or the method. I might have been able to beat the problem by going into the kernel but decided it was simpler to just not do it. My main point is your challenge may be more an issue related to the age of the computer rather than the kernel/bios or the cards being used. If you can try to find a "less old" computer to run things on Norm
On 28 Sep 2006, at 18:53, Norm wrote:
On Thu, 28 Sep 2006 18:32:04 +0100 Greg Frith gfrith@gmail.com wrote:
On 28 Sep 2006, at 18:25, Rick Stevens wrote:
On Thu, 2006-09-28 at 16:49 +0100, Greg Frith wrote:
[snip]
You must be root to do the "rpm -Uvh" (I'd recommend "rpm -ivh"). Also note that the "kernel-devel" RPM is NOT the kernel source RPM. It is only the kernel headers..and is usually enough to build most 3rd party drivers.
Thank Rick,
My apologies, I have installed the kernel-devel package, i get the error when trying to install kernel-2.6.15-1.2054_FC5.src.rpm. I am also doing this as root. So,
[root@wharfe]: rpm -ivh kernel-2.6.15-1.2054_FC5.src.rpm error: cannot create %sourcedir /usr/src/redhat/SOURCES.
--
- Rick Stevens, Senior Systems Engineer
rstevens@vitalstream.com -
- VitalStream, Inc.
Ran into a problem setting up an ether net bridge in an old computer. My guess in the end is the problem was actually a problem associated with the mother board chipset or bios rather than any of the cards I was using or the method. I might have been able to beat the problem by going into the kernel but decided it was simpler to just not do it. My main point is your challenge may be more an issue related to the age of the computer rather than the kernel/bios or the cards being used. If you can try to find a "less old" computer to run things on Norm
Thanks for your comments Norm. Unfortunately (for me) i think there may be a lot of sense in what you say. I did however get the wireless cad working in the end, after compiling ndiswrapper and then using this to load a Win32 driver. There was i thinking that any old box would be able to cope with an ethernet card. BTW, the card is identified correctly in an 'lspci', and modprobe gives no errors when loading the r8169 driver.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
-- Greg Frith gfrith@gmail.com
How do,
On Thu, 2006-09-28 at 19:10 +0100, Greg Frith wrote:
Thanks for your comments Norm. Unfortunately (for me) i think there may be a lot of sense in what you say. I did however get the wireless cad working in the end, after compiling ndiswrapper and then using this to load a Win32 driver. There was i thinking that any old box would be able to cope with an ethernet card. BTW, the card is identified correctly in an 'lspci', and modprobe gives no errors when loading the r8169 driver.
Also, keep in mind, the majority of RealTek nics are the nic equivalent of a win modem :-( Try replacing with an Intel or 3Com & see if that makes a difference.
-- Greg Frith gfrith@gmail.com
taharka
Lexington, Kentucky U.S.A.
On Thu, Sep 28, 2006 at 03:10:20PM -0400, taharka wrote:
How do,
On Thu, 2006-09-28 at 19:10 +0100, Greg Frith wrote:
Thanks for your comments Norm. Unfortunately (for me) i think there may be a lot of sense in what you say. I did however get the wireless cad working in the end, after compiling ndiswrapper and then using this to load a Win32 driver. There was i thinking that any old box would be able to cope with an ethernet card. BTW, the card is identified correctly in an 'lspci', and modprobe gives no errors when loading the r8169 driver.
Also, keep in mind, the majority of RealTek nics are the nic equivalent of a win modem :-( Try replacing with an Intel or 3Com & see if that makes a difference.
All I know is that I've never had any trouble with Realtek chipset NICs. But I must admit I've not used any of 'em with FC5, either.
I'm currently running two of them in the old Smoothwall firewall box (8139 cards) and it had no trouble at all.
my desktop, which is running Centos 4.4 has a builtin 8169 (not a separate card) and it also works perfectly.
So, either FC5 has some oddity in how it recognizes/enables realtek chipsets, or the particular card you have has done something that breaks the otherwise easy-to-use chipset. No clue what.
Howdy,
On Thu, 2006-09-28 at 18:37 -0400, fredex wrote:
All I know is that I've never had any trouble with Realtek chipset NICs. But I must admit I've not used any of 'em with FC5, either.
Ever try using em with FreeBSD 5.x/6.x/7.x?
I'm currently running two of them in the old Smoothwall firewall box (8139 cards) and it had no trouble at all.
My current Firewall/Router box is an ex Smoothie with three 8139C nics. Switched it over to IPCop & suddenly discovered m0n0wall which is FreeBSD based & running as we speak. Bet yours are 8139Cs also. I once built a Smoothie for a customer with two 8139D nics. Nothing but problems. Exchanged them for two 8139Cs & all was well. IIRC correctly, there was some discussion about RealTek nics, a few years back, on the Smoothwall list. Bottom line is, these nics use CPU processing power the same way a win modem does. The m0n0wall box, is accessible via a web browser that's SVG enabled & I can see real time performance of the CPU. If I shut down m0n0wall, switch out the RealTek nics with either Intel/3Com, CPU usage goes way down compared to the RealTeks. BTW, did you know the founder of Smoothwall (I assume you know who I mean ;-) ) is one of the backers/funders of m0n0wall?
my desktop, which is running Centos 4.4 has a builtin 8169 (not a separate card) and it also works perfectly.
Not much you can do about a builtin, short of disabling it in the BIOS & installing a pci Intel/3Com nic. Should give you a performance boost though.
So, either FC5 has some oddity in how it recognizes/enables realtek chipsets, or the particular card you have has done something that breaks the otherwise easy-to-use chipset. No clue what.
My theory is this, ya save a ton of money by not paying $Microshaft prices. Why not splurge a little on some top quality nics?
taharka
Lexington, Kentucky U.S.A.
On Thursday 28 September 2006 23:37, fredex wrote:
All I know is that I've never had any trouble with Realtek chipset NICs. But I must admit I've not used any of 'em with FC5, either.
I'm currently running two of them in the old Smoothwall firewall box (8139 cards) and it had no trouble at all.
my desktop, which is running Centos 4.4 has a builtin 8169 (not a separate card) and it also works perfectly.
So, either FC5 has some oddity in how it recognizes/enables realtek chipsets, or the particular card you have has done something that breaks the otherwise easy-to-use chipset. No clue what.
Note that two other people have reported big problems with realtek 8139 cards and FC5 in the last week.
Anne
On Thu, 2006-09-28 at 19:10 +0100, Greg Frith wrote:
On 28 Sep 2006, at 18:53, Norm wrote:
On Thu, 28 Sep 2006 18:32:04 +0100 Greg Frith gfrith@gmail.com wrote:
On 28 Sep 2006, at 18:25, Rick Stevens wrote:
On Thu, 2006-09-28 at 16:49 +0100, Greg Frith wrote:
[snip]
You must be root to do the "rpm -Uvh" (I'd recommend "rpm -ivh"). Also note that the "kernel-devel" RPM is NOT the kernel source RPM. It is only the kernel headers..and is usually enough to build most 3rd party drivers.
Thank Rick,
My apologies, I have installed the kernel-devel package, i get the error when trying to install kernel-2.6.15-1.2054_FC5.src.rpm. I am also doing this as root. So,
[root@wharfe]: rpm -ivh kernel-2.6.15-1.2054_FC5.src.rpm error: cannot create %sourcedir /usr/src/redhat/SOURCES.
- Rick Stevens, Senior Systems Engineer
rstevens@vitalstream.com -
- VitalStream, Inc.
Ran into a problem setting up an ether net bridge in an old computer. My guess in the end is the problem was actually a problem associated with the mother board chipset or bios rather than any of the cards I was using or the method. I might have been able to beat the problem by going into the kernel but decided it was simpler to just not do it. My main point is your challenge may be more an issue related to the age of the computer rather than the kernel/bios or the cards being used. If you can try to find a "less old" computer to run things on Norm
Thanks for your comments Norm. Unfortunately (for me) i think there may be a lot of sense in what you say. I did however get the wireless cad working in the end, after compiling ndiswrapper and then using this to load a Win32 driver. There was i thinking that any old box would be able to cope with an ethernet card. BTW, the card is identified correctly in an 'lspci', and modprobe gives no errors when loading the r8169 driver.
I noted that you are using the 2.6.15-2054 kernel. Is there a reason that you have not updated to take advantage of the newer and better drivers in the later kernels?
For me, installing a wireless adapter in a fully updated FC5 system caused me a lot of stress because I had previously used ndiswrapper with that exact same adapter on the 2.6.15 and 2.6.16 kernels. The updated 2.6.17 kernel broke ndiswrapper because it was loading the drivers for the adapter.
I simply had to identify how to get the firmware for the adapter to load and remove ndiswrapper entirely. But the real problem was getting it through my thick skull that the open source driver would actually work and I no longer needed ndiswrapper. ;-))
I think the 8169 card may require updates that are newer than the 2.6.15 kernel as well.
On 28 Sep 2006, at 16:49, Greg Frith wrote:
Hi,
I'm setting up a reasonably old PC with FC5 to use primarily as a test server for web development. A few days ago i installed FC5 and spent 2 days trying to configure a wireless network card. Having finally compiled the kernel with the additional drivers for the wireless card i got it up and running and everything was fine. The box was hidden away in a corner (where my partner couldn't see it) and all was good. This morning however the hard disk went in the machine, so i had to purchase a new disk and start all over again.
So my present situation: Not wanting to go through the pane of setting up a wireless card again, i thought I'd save myself a great deal of hassle and put a standard wired ethernet card in. So i did, a Netgear GA311 which i believe uses the Realtek 8169 chip set. I'd already checked online and everyone reported this card as working hassle free under fedora. But not for me. On boot I see the message:
r8169 device eth0 does not seem to be present, delaying initialisation
I get the same message if i do ifup eth0. ifconfig -a does not list eth0.
Using the GUI tool Network Manager the device can be seen under hardware.
So the network card not working is the first problem, any thoughts gratefully received.
In order to try and fix this i have downloaded linux drivers from the Realtek site. To install i need the kernel source, so i also downloaded kernel-devel-2.6.15-1.2054_FC5.i686.rpm. When i try to install this rpm i get:
-> rpm -Uvh kernel-devel-2.6.15-1.2054_FC5.i686.rpm error: cannot create %sourcedir /usr/src/redhat/SOURCES.
Any thoughts?
Many thanks, Greg.
Hi all,
A reply to my own message with my final 'solution' in case this is of benefit to anyone else searching the archive with a similar issue.
I borrowed another basic (unbranded) network card with the same RealTek chipset and tried this, it gave me exactly the same error and i was unable to bring up a network connection with it. Therefore I concluded that there was nothing wrong with the network hardware.
I finally gave in and purchased a new motherboard, processor, memory and PSU. Having installed these components and booted up on the same hard disk which had the FC5 install from the previous machine the system immediately recognised the network hardware built into the motherboard (again a RealTek chipset) and the network was up. Being a glutton for punishment, I then installed the original Netgear GA311 card and re-booted. Again the machine immediately saw the card and had access to the network.
So, an incompatibility either between the network hardware and old motherboard/BIOS or Linux and the old motherboard/BIOS. Whichever i just wish i hadn't tried to save myself a few £££ in the first place and bought a new machine straight away. The old motherboard by the way was a Gigabyte GA-7IXE4 with an AMD 751/756 chipset.
HTH. Greg.
-
Anne Wilson -
Fred Smith -
Greg Frith -
Jeff Vian -
Norm -
Rick Stevens -
taharka