ethernet adapter problem in redhat enterprise linux WS (update 3)
Hi everyone, this is my first post in this forum.
Ok, here's the story, I just finished installing this Redhat Enterprise Linux WS (update 3) on my new machine. Strangely enough, during the installation, it didn't ask me for configuring my network settings, which according to Redhat documentions that, my ethernet adapter couldn't be detected. However, I do have a Marvell Yukon Gigabit Ethernet Adapter that is integrated on my mobo. So, after finishing the installtion, I decided to install the driver manually. and I downloaded the driver 'sk98lin' (I think it should be the driver name...), and first I tried 'user mode' in its installation, unfortunately, it didn't work out very well, actually failed at the end. The reason is: "An error has occurred during the check process...." "It's not possible to build a standalone sk98lin driver on this host. The kernel don't export a neccesay symbols for the device driver and we aren't able to load the driver." So, I tried to compile both the driver and the kernel manually, but the thing is, I really couldn't find 'Marvell Yukon/SysKonnect SK-98xx/Sk-95xx Gigabit Ethernet Adapter support' in 'Network Device Support' when I was doing the kernel compilation. However, I did find the folder 'sk98lin' in /usr/src/linux-2.4.xx/drivers/net directory. Now, I'm totally lost, what should I do next?! I'm sorry for posting such a exhaustedly long thread.... Thank you you guys in advance... |
|
Quote:
Thanks. but it doesn't seems that help me much... The main problem is the above highlighted in red color. Cheers |
Sorry, I should have read more carefully, that was a link to what you already have. I tried to find an RPM, no luck.
The aforementioned crimson clause assumes that your kernel source is on the hard drive. RedHat doesn't do this. Stupid (and potentially insulting) question: Did you untar the kernel source on your drive as in 6.1 of the install instructions. |
RedHat is definitely not enthralled with this driver.
|
REL More than a bug...
I purchased REL3.0 for My IBM Thinkpad R51 2888 CA4 model which was working fine until I thought of registering it where the real problem started my network adapter did not support and no support helped me in that regard the support which I got from web support was nothing but a junk mail which read "contact INDIA support" but globally there was no support or driver available for the machine so almost My machine is going to be a dumb one ... I when thought of Linux I went to REL assuming all the latest and reliable stuff will be available but now it is evident that fedora is better that the REL which is charging for no good reason |
RHEL is supposed to be the most reliable, something on which to bank the Enterprise, which is by its nature not going to be the latest. This will also limit your choices of supported hardware.
Fedora is the latest stuff, but with no testing. Which is the most useful for you depends entirely on your priorities. > when thought of Linux I went to REL assuming all the latest and >reliable stuff will be available >but now it is evident that fedora is better that the REL which is >charging for no good reason |
Ok man
Can u please locate me to a driver to ethernet adapter which suits my system ? I have R51 IBM thinkpad 2888 model "Integrated Intel PRO/1000 Gigabit Ethernet" regards |
Quote:
|
Burrough, did you make any headway compiling the driver?
|
right, now the I got the official patch for kernel 2.4.22, but the default kernel is 2.4.21.20-EL on my machine, so could I apply this patch to this kernel, or I have to compile the driver on my own?
|
The patch must match the kernel, unfortunately.
|
hey guys,
I have IBM r51 thinkpad which has Intel(R) PRO/1000 Mobile Connection ethernet card. i have to do a project ..and i have RHEL ES3 installed on it...i have to configure many..but please help me in finding out a driver and its location where can i get it...please also find me a driver for redhat 9 as well...please guys help me fast...thanks praveen. |
If you read the previous threadjack, you would know.
|
Quote:
Read man modprobe, man insmod. Cheers. Burrough: did you get the source to match your kernel? If not, why don't you take stock of all the modules currently loaded and match them against the output of lspci. Then you can compile a kernel and the proper driver for your adaptor all in one fell swoop. There is an excellent kernel compiling guide here on LQ (probably in the wiki as well by now). |
Solution
I had the exact error come up in RHEL4 WS. The kernel module compiled but would not install correctly even if I manually installed the module. I looked at the script (install.sh) that installs the module and found the problem. First of all, I su to root to build and install the module. By default, /sbin is not in the path. Because of this, when the script tries to do an lsmod it fails to find the lsmod executable and instead of giving a decent message about that, it dumps out the
'An error has occurred during the check process which prevented the installation from completing. It's not possible to build a standalone driver on this host. The kernel don't export a neccesary symbols for the device driver and we aren't able to load the driver. Please compile the kernel and the driver manually.' message. If you edit the line: insmod_count='lsmod | grep $drv_name -c' (it was line 1234 in the version I used) and change it to insmod_count='/sbin/lsmod | grep $drv_name -c' then the driver will properly install. |
All times are GMT -5. The time now is 01:40 AM. |