| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 73438 | 2006-10-19 01:44:00 | BIOS & Missing Onboard LAN | Erayd (23) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 492568 | 2006-10-19 01:44:00 | Well this is quite a saga. It all started when I got a new motherboard (secondhand) for my PC. The motherboard is a Soltek SL-75FRN2 (nForce2 based), and it was having this problem before I got it: * Every 10 bootups or so it required a CMOS reset Recently it got a lot worse, and needed the reset jumper shorted for ~10 minutes on nearly every bootup - this morning I finally got pissed off with it and decided to fix it properly once and for all. So: Step 1: Find the BIOS file and flash utility (awdflash and 75frn220.bin) Step 2: Create a bootable CD with DRDOS and the flash stuff - this machine has no floppy drive Step 3: Flash BIOS with /sn/py Finds that nothing has changed, oh bugger Step 4: Flash BIOS again, but this time with the /cc clear CMOS switch as well Finds that nothing has changed, oh bugger Step 5: Try to hotflash another BIOS chip from some random old mobo, but awdflash refuses to write to it Step 6: Try to hotflash yet another old BIOS chip, same result Step 7: Do some research, discover that BIOS chips come in different sizes, and I need a 2MB BIOS - which I don't have (other than the stuffed one) Step 8: Continue trying to salvage the busted one, and flash it again, with the /cc flag set Finds that nothing has changed, getting quite pissed off by this stage Step 9: Reflash with /cc and /wb to overwrite the BIOS boot block Finds that nothing has changed, gets really, really pissed off, and does the BIOS equivalent of hitting it with a sledgehammer (i.e. step 10) Step 10: Flash AGAIN, with /cc (clear CMOS), /wb (overwrite bootblock), /cd (wipe DMI data), and /wp (wipe EHCD plug & play data) Finds that it seemes to have worked, but the onboard network has vanished Step 11: Spend a frustrating 30 minutes trying to find where the network has gone Step 12: Conclude that the flash has somehow disabled the network (as it still seems to be running, but the BIOS simply can't see it) and repeat step 11 with the /NVMAC:xxxxxxxxxxxx flag. Twice. Runs out of options, as the network still seems to be disabled, and puts in a PCI card So the end result of all that is a motherboard that now works properly, but has no onboard network. Any ideas how to get the BIOS to see the network again? |
Erayd (23) | ||
| 492569 | 2006-10-19 02:36:00 | Buy a new motherboard. Not a used one. | pctek (84) | ||
| 492570 | 2006-10-19 02:59:00 | Buy a new motherboard.But why would I do that? I got the existing one for free anyway, and all it's taken on my part is some time, swearing, and a spare network card. I'd just like to get the onboard LAN running again, so I can use WOL properly. | Erayd (23) | ||
| 492571 | 2006-10-19 03:03:00 | The SL-75FRN2 doesnt have onboard LAN but the SL-75FRN2-L does, perhaps you flashed with the incorrect BIOS? Check out this (www.soltek.com.tw) or this (www.imagef1.net.nz) |
Pete O'Neil (6584) | ||
| 492572 | 2006-10-19 03:08:00 | Nice post Pete!, I was going to suggest checking the BIOS, does it have LAN option at all, greyed out, not there etc. I reckon Pete's post to be the winner.............. |
SolMiester (139) | ||
| 492573 | 2006-10-19 03:13:00 | Nice one, I bet that's it - I was going by the model number on the instruction book, as I couldn't find it anywhere on the mobo. I'll try reflashing with the -L image and see what happens. If you don't hear back, assume I killed it... | Erayd (23) | ||
| 492574 | 2006-10-19 03:48:00 | I nearly brought a SL-75FRN2-L back in the day, ended up spending a bit more money and getting the EPOX 8RDA+. Can remember spending a bit of time getting my head around model numbers, the Soltek website doesnt mention that the SL-75FRN2 doesnt have lan, you have to read the manual to find out. | Pete O'Neil (6584) | ||
| 492575 | 2006-10-19 04:04:00 | Yeehah! Pete, you're an utter legend - that was the problem. Now it's all sorted, and I have a motherboard in perfect condition :D Also took the opportunity to change the mac address during the reflash - it now officially has the mac address aa:bb:cc:dd:ee:ff - much easier to remember :p |
Erayd (23) | ||
| 492576 | 2006-10-19 05:21:00 | You shouldn't change the MAC address arbitrarily, although it "probably" won't cause any problems. The MAC address is supposed to be absolutely unique. The computer gets packets from the nearest router using the MAC address, not the IP address. But as long as you don't give another card the same MAC address in your LAN it won't matter. | Graham L (2) | ||
| 492577 | 2006-10-19 06:05:00 | You shouldn't change the MAC address arbitrarily, although it "probably" won't cause any problems. The MAC address is supposed to be absolutely unique. The computer gets packets from the nearest router using the MAC address, not the IP address. But as long as you don't give another card the same MAC address in your LAN it won't matter. Absolutely right. Usually, there is a sticker (sometimes on the floppy connector) on the motherboard with the MAC Address. I once got some new PCs at work and the supplierhad done a bios upgrade (with a bad version) and the MAC addresses were all the same (although they looked "normal"). It was fun figuring out what was going on... |
gibler (49) | ||
| 1 2 | |||||