This driver install is annoying, and I'm not going to recompile a kernel simply to get even my onboard working. I can live without the Wireless onboard, but ffs, everything else detects fine except my Marvell.
What linux os' automatically setup Marvell Gig Eth0
- Thread starter krevo
- Start date
cmon...someone has to have experienced this problem...not even ubuntu recognizes my Marvell gig onboard.
modprobe -l sk98lin
If it really isn't there, find out who maintains the kernel packages for your distro, and fire off an email. He might say no, but I don't know why (unless you're an ass about it), especially if this is a 2.6 kernel, where I know the driver is already in the kernel, in which case, unless there is some kind of weird technical problem, it is likely an oversight.
In any case, if you have the config that was used to build the default kernel (it might be in /proc, it might be in /boot), recompiling is very easy.
If it really isn't there, find out who maintains the kernel packages for your distro, and fire off an email. He might say no, but I don't know why (unless you're an ass about it), especially if this is a 2.6 kernel, where I know the driver is already in the kernel, in which case, unless there is some kind of weird technical problem, it is likely an oversight.
In any case, if you have the config that was used to build the default kernel (it might be in /proc, it might be in /boot), recompiling is very easy.
No, I'm no newb to recompiling kernels. I was and have been running Slack on my k6 450 for almost 7 years now. However, I don't feel its necessary to bother with this driver. Modprobe does not show it. The install script is defunkt when it comes to auto installing, the manual install also doesn't work do to GCC compiler version error. This driver is just a general pain in the ass.
Why should I have to recompile a perfectly fine kernel just to test some x64 linux distros? I just want to fire up and boot so I can rationalize running a box at work under 64 bit kernel. This justifies itself in and that I want to find the easiest linux distro for us to distribute dual booted for some systems we're building at work. Mostly based upon Asus boards that have Marvell eth0.
Why should I have to recompile a perfectly fine kernel just to test some x64 linux distros? I just want to fire up and boot so I can rationalize running a box at work under 64 bit kernel. This justifies itself in and that I want to find the easiest linux distro for us to distribute dual booted for some systems we're building at work. Mostly based upon Asus boards that have Marvell eth0.
and just another note...
Why is it that there are so many people here who try and persuade people to not bump threads, to search meaninglessly through age-old threads, and act like web forums gurus? I just needed a simple answer, and yes, I might be a little impatient, but please understand that this forum will not go under do to a little bumpage and a couple measly double topics. Why can't everyone here be as friendly as many small tech related forums. My overall opinion of Anandtech as a whole is it's filled with overly stuck up tech snobs and smartasses. It shouldn't be this way here, of all places. I recommend many people to this forum as a means of having many brains come together to solve complicated tech issues, and it seems like they all come back to me about the jerks to shun them away. God, just chill out and be glad you have a place to come together with so many others who enjoy all things technological.
/end rant
*waits for nobody to respond because they're afraid they won't be accepted by the "community" *
Why is it that there are so many people here who try and persuade people to not bump threads, to search meaninglessly through age-old threads, and act like web forums gurus? I just needed a simple answer, and yes, I might be a little impatient, but please understand that this forum will not go under do to a little bumpage and a couple measly double topics. Why can't everyone here be as friendly as many small tech related forums. My overall opinion of Anandtech as a whole is it's filled with overly stuck up tech snobs and smartasses. It shouldn't be this way here, of all places. I recommend many people to this forum as a means of having many brains come together to solve complicated tech issues, and it seems like they all come back to me about the jerks to shun them away. God, just chill out and be glad you have a place to come together with so many others who enjoy all things technological.
/end rant
*waits for nobody to respond because they're afraid they won't be accepted by the "community" *
Beleive it ot not alot of linux distro have a default eth0 as disabled I
To be honest I am running fedora core 4 64-bit and I have gigabit lan in their and no problems at all everything went autodetected , but I am not sure about the marvell lan though , but whats the big deal with the marvell lan
if it gives you too much pain in the ass just use a regular NIC I suppose you are not using a 1000 mbps network so a 100Mbps ould just do.
To be honest I am running fedora core 4 64-bit and I have gigabit lan in their and no problems at all everything went autodetected , but I am not sure about the marvell lan though , but whats the big deal with the marvell lan
if it gives you too much pain in the ass just use a regular NIC I suppose you are not using a 1000 mbps network so a 100Mbps ould just do.
That's the problem many Linux users on this board. I don't want to have to use a bs workaround in order to just have my onboard work. Seems like all answers at Anandtech point to "if it doesn't want to work, use a standard 10/100 eth card. Why should I have to do that if there is a distro that supports my onboard eth.
sourceninja
Diamond Member
- Mar 8, 2005
- 8,805
- 65
- 91
ubuntu, gentoo live CD, fedora, and suse all recognize my onboard gigabyte lan from marvell and nvidia on my DFI nforce 4 ultra board. I know this is a stupid question, but are you sure the onboard nic is enabled in the bios? Unless its a different onboard nic then mine, i'm not sure why you dont have drivers for it. In fact, fedora didn't even see my nvida nic forcing me to move my cable to my marvell nic.
Fedora Core 2 and 3 detected my Marvell ethernet controller with the stock kernel. No problem there.
The Marvell sata controller on the other hand...
wow there buddy I am the one who is usually complaining about linux gurus lol you wanted it to work, well lets say in your case theres no way it can, then do you want to spend the rest of your life trying to make it work, no thank you I am way past that stage when I first started using linux.
When I had a DFI Lanparty Ultra-D motherboard it had a marvell NIC and an nvidia NIC I spent 3 days and 4 windows xp reinstallations , and yes I am more of a WIN guru than a LINUX guru and there was no way to get it to work so with all simplicity I said fck the NIC and fck the WINblows and switched to the marvell lan , fck this what kind of benefits did the nvidia NIC come with all it had is this firewall that you might already have if you own a basic router. bottom line don't start pointing fingers everywere as u like. All OS's suck , Linux and Windows both suck either one way or the other you just have to find the medium point between them and their usage.
I can't use windows xp pro alone and I can't use Fedora core 4 64bit alone I need both of them.
at least until ATI starts making some deacent drivers for linux and games start exploding on linux the way they r on windows right now , but untill then I need both. and maybe someday The BIG LINUX GUYS will decise to creat something SIMPLE called a FCKING SETUP FILE BY WHICH I DONT HAVE TO GO ON A TRIP AROUND THE NET TO FIND SOME FCKING PACKAGES AND LIBRARIES AND DEPENDENCIES sigh........
To be honest nothing feels anybetter than FC4 64-bit really I mean everytime I restart to play HL2 or CS: Source on WINXP PRO I feel like a caveman looking at that winxp system that I have tweaked from all angles inorder for it to become bareable. or runnable
Cross posting has generally been viewed as rude behaviour. Quick bumping has been enough reason for a warning from the moderating staff in the past. Lighten up.
If you want it, make it. There are simple packages out there, you just don't seem to be using them.
I have found ubuntu, and debian in general find my marvell nic. But I must have some guru powers that transfer through my keyboard during the install :disgust:
If you want help, ask nicely, and someone will help. OS is not the quickest forum, and a bump after 30 minutes is not warranted, especially since it was probably only a couple threads down the page. As a general rule, it is fine to bump your thread once every 4 hours, at least that is what it is limited to in the FS/FT forum.
A search that took me about 5 seconds brought this page up:
http://forums.anandtech.com/messageview...atid=34&threadid=1652109&enterthread=y
Have a nice day, and next time take a chill pill.
If you want help, ask nicely, and someone will help. OS is not the quickest forum, and a bump after 30 minutes is not warranted, especially since it was probably only a couple threads down the page. As a general rule, it is fine to bump your thread once every 4 hours, at least that is what it is limited to in the FS/FT forum.
A search that took me about 5 seconds brought this page up:
http://forums.anandtech.com/messageview...atid=34&threadid=1652109&enterthread=y
Have a nice day, and next time take a chill pill.
There are 2 types of 10/100/1000 marvell nics.
One is the Yukon series the other is called the Yukon-2 series.
One is PCI-based and is going to be included by default in 2.6.13 series kernels and probably have it's drivers already aviable by most modern distros.
The other is a PCI Express based card, that while it has a similar make and model name, is completely different from the PCI version. This is probably going to be more difficult to get going.
The thing is that a reseller of Marvell based nics released a GPL'd driver that included support for both nic cards. The bad part is that technically speaking it should of been in two seperate drivers for the two different cards. I beleive technically the cards are very different.
For the PCI version they've gotten a driver put together from the orginal GPL'd one that is compatable with the kernel coding style, but the PCI-E version is going to take a bit longer to get working.
Meanwhile the original drivers still should function perfectly well. If you have the PCI-e version then it's going to require you to use this package as far as I can tell.
You can get the driver from here:
http://www.syskonnect.de/syskonnect/support/driver/htm/sk9elin.htm
From the README webpage there are 2 ways to install the kernel.
One way is to do the normal compile module and install module and man page routine. I don't think that you'd need the entire kernel source to do that and you definately don't have to recompile your kernel from scratch to do that. Just install the kernel header package supplied by your distro.
If that doesn't work you can probably install the sources for your system kernel then copy the config over from your /boot directory (depending on how your distro is setup) to your linux sources directory (like /usr/src/linux/.config) and run a 'make oldconfig&& make' and that should be enough to get what you need to compile the module.
But I am pretty sure that all you'd need would be the header package.
The second method outlined in the readme is to use the install script to generate a kernel patch then you can use that patch to recompile the kernel using patched sources.
This would be handy in situations were you have lots of machines using the nic and you want them to be be supported by default from a kernel package of your own making. Or your using it in a embedded style or network boot situation and you want support for the card built into the kernel itself so you don't have to mess around with generating a initrd (which itself is generally not difficult).
Hell, depending on your OS it's likely that you've got a pre-compiled version of the drivers already aviable for you.
The reason that I recommended to a newbie in another thread to get a seperate nic card is because a person new to Linux is going to find the experiance of simply adjusting to a working desktop a difficult one. Making sure to have the kernel header package and be able to make install scripts executable is something that would be very frustrating at first.
besides having a spare nic card is very handy to have and they are dirt cheap anyways. (as is a spare harddrive, spare video card, etc etc) I have a couple cheapo cards that I bought for a "3 for price of two, with each card on sale for 8 bucks" a few years ago. I've used them for all sorts of different little things... Used them for Windows, used them for Linux, used them OpenBSD, it doesn't matter.
One is the Yukon series the other is called the Yukon-2 series.
One is PCI-based and is going to be included by default in 2.6.13 series kernels and probably have it's drivers already aviable by most modern distros.
The other is a PCI Express based card, that while it has a similar make and model name, is completely different from the PCI version. This is probably going to be more difficult to get going.
The thing is that a reseller of Marvell based nics released a GPL'd driver that included support for both nic cards. The bad part is that technically speaking it should of been in two seperate drivers for the two different cards. I beleive technically the cards are very different.
For the PCI version they've gotten a driver put together from the orginal GPL'd one that is compatable with the kernel coding style, but the PCI-E version is going to take a bit longer to get working.
Meanwhile the original drivers still should function perfectly well. If you have the PCI-e version then it's going to require you to use this package as far as I can tell.
You can get the driver from here:
http://www.syskonnect.de/syskonnect/support/driver/htm/sk9elin.htm
From the README webpage there are 2 ways to install the kernel.
One way is to do the normal compile module and install module and man page routine. I don't think that you'd need the entire kernel source to do that and you definately don't have to recompile your kernel from scratch to do that. Just install the kernel header package supplied by your distro.
If that doesn't work you can probably install the sources for your system kernel then copy the config over from your /boot directory (depending on how your distro is setup) to your linux sources directory (like /usr/src/linux/.config) and run a 'make oldconfig&& make' and that should be enough to get what you need to compile the module.
But I am pretty sure that all you'd need would be the header package.
The second method outlined in the readme is to use the install script to generate a kernel patch then you can use that patch to recompile the kernel using patched sources.
This would be handy in situations were you have lots of machines using the nic and you want them to be be supported by default from a kernel package of your own making. Or your using it in a embedded style or network boot situation and you want support for the card built into the kernel itself so you don't have to mess around with generating a initrd (which itself is generally not difficult).
Hell, depending on your OS it's likely that you've got a pre-compiled version of the drivers already aviable for you.
The reason that I recommended to a newbie in another thread to get a seperate nic card is because a person new to Linux is going to find the experiance of simply adjusting to a working desktop a difficult one. Making sure to have the kernel header package and be able to make install scripts executable is something that would be very frustrating at first.
besides having a spare nic card is very handy to have and they are dirt cheap anyways. (as is a spare harddrive, spare video card, etc etc) I have a couple cheapo cards that I bought for a "3 for price of two, with each card on sale for 8 bucks" a few years ago. I've used them for all sorts of different little things... Used them for Windows, used them for Linux, used them OpenBSD, it doesn't matter.
my bro has a msi k8n neo2 platinum and he has the marvell gigabit ethernet. he installed 64bit hoary and it worked just fine. he also installed gentoo and it was supported.
The Debian box I'm typing this on has the sk98lin driver, and I do seem to remember a Fedora install that found a Marvell/Syskonnect NIC on an Asus mobo a while back.
What distro are you running anyway?(Sorry if it's in there, but some of your posts are a bit...annoying to read, punctuations and paragraphs are your friends).
What distro are you running anyway?(Sorry if it's in there, but some of your posts are a bit...annoying to read, punctuations and paragraphs are your friends).
From the asus website:
http://usa.asus.com/prog/spec.asp?m=A8N-SLI%20Deluxe&langs=09
It appears that it's a regular PCI model and not PCI-e model marvell nic controller, so it should work with a distro with a relatively modern kernel like Ubuntu.. I beleive in future kernels the drivers may be called skge for the yukon pci and sky2 for the yukon-II pci-e adapters. see: http://lkml.org/lkml/2005/7/28/199
Unless of course the network adapter maintainers in the Linux kernel decide to change their mine and accept the skyconnect's sk89lin drivers with support for both types of cards.
That stuff may be a bit dated, I am not sure.
also something to watch out for on gcc errors, if they come up at random times during compile time (like sometimes it makes it, and other times it fails and when it fails it fails at different spots) then there is a good chance that it's due to a memory error. If it fails always in the same spot, then it's very likely a bug in the source code or compiler itself.
http://usa.asus.com/prog/spec.asp?m=A8N-SLI%20Deluxe&langs=09
It appears that it's a regular PCI model and not PCI-e model marvell nic controller, so it should work with a distro with a relatively modern kernel like Ubuntu.. I beleive in future kernels the drivers may be called skge for the yukon pci and sky2 for the yukon-II pci-e adapters. see: http://lkml.org/lkml/2005/7/28/199
Unless of course the network adapter maintainers in the Linux kernel decide to change their mine and accept the skyconnect's sk89lin drivers with support for both types of cards.
That stuff may be a bit dated, I am not sure.
also something to watch out for on gcc errors, if they come up at random times during compile time (like sometimes it makes it, and other times it fails and when it fails it fails at different spots) then there is a good chance that it's due to a memory error. If it fails always in the same spot, then it's very likely a bug in the source code or compiler itself.
well, I don't know. These system would be using the current available iso of 32bit Ubuntu Linux. They are also based upon a really cheap Asus mobo (A8V-E Deluxe) and for some reason not even Ubuntu find ANY network controllers during install. Even prompts you "Do you really wanna continue setup w/o network"
And, I apologize for my demeanor last night, however, I've just been hassled here so many times to search for older threads, not to bump quicker than a certain amount of time, and to keep my posts free of any details. Short, precise and too the point is good in some cases, but sometimes details are necessary. 
Strange, considering Ubuntu is based on Debian, and as I said, Debian includes the sk98lin module by default.
Did you try looking around in your dmesg for clues? I remember the NIC's on Asus mobos being a little touchy before.
Did you try looking around in your dmesg for clues? I remember the NIC's on Asus mobos being a little touchy before.
ya.. maybe it's unable to detect the nic card for some reason.
While booted up in the ubuntu (or debian) install cdrom you should be able to switch to console by going ctrl-alt-f2 (or similar) and get a command line.
from there you might be able to do things like 'lspci' to see listed pci devices and be able to modprobe or at least insmod the module.
I am not sure all of what is aviable on the install cdroms though.. but you should be able to get the networking going manually if you have to. I've had to do that a couple times in the past.
While booted up in the ubuntu (or debian) install cdrom you should be able to switch to console by going ctrl-alt-f2 (or similar) and get a command line.
from there you might be able to do things like 'lspci' to see listed pci devices and be able to modprobe or at least insmod the module.
I am not sure all of what is aviable on the install cdroms though.. but you should be able to get the networking going manually if you have to. I've had to do that a couple times in the past.
Originally posted by: krevo
And, I apologize for my demeanor last night, however, I've just been hassled here so many times to search for older threads, not to bump quicker than a certain amount of time, and to keep my posts free of any details. Short, precise and too the point is good in some cases, but sometimes details are necessary.
?Usually details are a plus. Too many irrelevant ones are annoying, but then again, how is the one asking the question supposed to know for sure what is irrelevant and what is not?
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 21K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter