Re: [H] Marvell network stuff
I've used the Marvell Yukon gigabit controllers before. I had them on some boards from Gigabyte a couple of years ago. I'd just whichever one Asus has on their site. I have not heard of Alaska. Once I had one onboard a motherboard was whose Device ID did not match the device ids in the drivers (*.inf). I had to force install the driver and it worked fine after that. I think somehow the device id changed because this was a production system at a local Copy Center that suddenly went offline. I quickly saw that it's ethernet controller had become an unknown/other device in the Windows Device Manager. After checking the vendor and device id of the ethernet controller I found that the vendor code matched but the device id didn't. Neither the drivers from the motherboard manufacturer nor Marvell's reference driver had a matching id. It was very odd. ::shrug:: -Tharin O. --- DHSinclair [EMAIL PROTECTED] wrote: Thanks Al, Have not found a change log yet. I've exploded all the zippers I have. No info/log files yet.. V10 is the plan, as soon as I find out just which Marvell chip is on the board. Could now be Alaska. Thought it was Yukon. Stupid codewords. Got to the Marvell site, but, as usual, it is not a clear path to what I'd like to know. I do not know the proper lingo and buzz/codewords. The search is fun anyway. Best, Duncan At 17:56 01/31/2008 -0500, you wrote: DHSinclair [EMAIL PROTECTED] wrote: I now have drivers at V7, V8, V9, and V10. Am I correct to use the V10 drivers? Or, should I just use the default V6.27 that came with the m/b to start with? There should be a change log telling what each version corrected. I would just go with the newest driver... Best, Al
Re: [H] Marvell network stuff
Tharin O., OK. The last Marvell driver I could find on the Asus site, (which works very badly here), was a v6.28. One level higher than the CD that came with the m/b. No matter, did my research. So far, I am fairly impressed with the Marvell nic chip. It does work and have seen no events in the event log. The Marvell site was down the night I went to look. It turns out that Alaska is the 'new' nic chip Marvell makes. I do know that I do have Yukon (88E8001-LKJ) chips. With the Marvell site down, I surfed and found drivers from v7-v10. This chip has either had lots of bugs, or lots of updates. Hmm. Whatever. Stuff happens. Next day, I was able to get to the Marvell site and got the latest drivers and utilities for the Yukon chip. The driver I loaded was v10.51.3.3. It is running hot, straight, normal ATM. All good here. And, the utilitites even work also. So far, so good. Expect the Intel GBit nics to arrive in the next hour or so. By midnight my LAN will be running GBit (except for the server). Newegg goofed up the server nic order :) I ran into the device ID/Vendor ID problem once many years ago. I was never able to get the device installed. I finally binned the device and bought another (more expensive) device to replace it. If a device passes bios and then will not answer it's driver dot-inf file, I toss it and get a replacement. I do not know how to re-write (edit) the dot-inf file. Why should I? Thank you for your share. So far, so good with the two on-board G-Bit nics. Best, Duncan At 06:39 02/05/2008 -0800, you wrote: I've used the Marvell Yukon gigabit controllers before. I had them on some boards from Gigabyte a couple of years ago. I'd just whichever one Asus has on their site. I have not heard of Alaska. Once I had one onboard a motherboard was whose Device ID did not match the device ids in the drivers (*.inf). I had to force install the driver and it worked fine after that. I think somehow the device id changed because this was a production system at a local Copy Center that suddenly went offline. I quickly saw that it's ethernet controller had become an unknown/other device in the Windows Device Manager. After checking the vendor and device id of the ethernet controller I found that the vendor code matched but the device id didn't. Neither the drivers from the motherboard manufacturer nor Marvell's reference driver had a matching id. It was very odd. ::shrug:: -Tharin O. --- DHSinclair [EMAIL PROTECTED] wrote: Thanks Al, Have not found a change log yet. I've exploded all the zippers I have. No info/log files yet.. V10 is the plan, as soon as I find out just which Marvell chip is on the board. Could now be Alaska. Thought it was Yukon. Stupid codewords. Got to the Marvell site, but, as usual, it is not a clear path to what I'd like to know. I do not know the proper lingo and buzz/codewords. The search is fun anyway. Best, Duncan At 17:56 01/31/2008 -0500, you wrote: DHSinclair [EMAIL PROTECTED] wrote: I now have drivers at V7, V8, V9, and V10. Am I correct to use the V10 drivers? Or, should I just use the default V6.27 that came with the m/b to start with? There should be a change log telling what each version corrected. I would just go with the newest driver... Best, Al
[H] Marvell network stuff
Does anyone have any experience with Marvell network stuff? The corp website seems to be down to me ATM. I will go back to it in due time. Never heard of Marvell. :( It seems that the GBit chip (on-board) on 2 of my Asus m/bs is by Marvell. No, I do not know the device number yet. But, my research today leads me to think it may be of the internal brand 'Yukon.' Confirm to come.. :) My m/b CD comes with drivers for the GBit chip at version 6.27. I spent the afternoon downloading any/all drivers for w2K. I now have drivers at V7, V8, V9, and V10. Am I correct to use the V10 drivers? Or, should I just use the default V6.27 that came with the m/b to start with? Thanks. Best, Duncan
Re: [H] Marvell network stuff
DHSinclair [EMAIL PROTECTED] wrote: I now have drivers at V7, V8, V9, and V10. Am I correct to use the V10 drivers? Or, should I just use the default V6.27 that came with the m/b to start with? There should be a change log telling what each version corrected. I would just go with the newest driver... Best, Al
Re: [H] Marvell network stuff
Thanks Al, Have not found a change log yet. I've exploded all the zippers I have. No info/log files yet.. V10 is the plan, as soon as I find out just which Marvell chip is on the board. Could now be Alaska. Thought it was Yukon. Stupid codewords. Got to the Marvell site, but, as usual, it is not a clear path to what I'd like to know. I do not know the proper lingo and buzz/codewords. The search is fun anyway. Best, Duncan At 17:56 01/31/2008 -0500, you wrote: DHSinclair [EMAIL PROTECTED] wrote: I now have drivers at V7, V8, V9, and V10. Am I correct to use the V10 drivers? Or, should I just use the default V6.27 that came with the m/b to start with? There should be a change log telling what each version corrected. I would just go with the newest driver... Best, Al
