Configuring Boot with Off-board ISA Intel Pro/100
-
@wanderbread (warning: relying on a very old memory here) If there is no chip socket for the Pro/100 it should have the pxe firmware built in, it just needs to be enabled with the utility I mentioned.
As for the usb boot. Depending on how old the motherboard is, it may support booting off usb, or you can go the bootable cd-rom route. Either way we can get the pxe boot media to work. Finding ISA network cards may be a bit challenging. (ok let me correct what I said above) ISA == Computers before the PC2000 standard came out. So they will not/support usb booting, even if there is a usb spot to plug in to.)
The Rom-o-matic site does support creating an iso (cdrom) boot image if needed.
-
@george1421 Yeah, there’s no USB port on the board to speak of, I was insinuating I’d need to buy a (non-existent) card to go that route.
Also, this network card appears to have a socket with no chip.
However, I’m inclined to believe what you said about the firmware being built in if the socket isn’t present because the links you provided to the Intel boot utility specifies it’s compatible with Pro/100… but I don’t think I have one it’s compatible with, per the empty socket. I’ll have to try, unfortunately that will have to wait until the machine isn’t being used. -
@wanderbread Will you tell me the IP address of your fog server?
-
@george1421 Unfortunately no, because it’s on a hidden sub-net, kept in the dark from the outside world.
Prior to having FOG set up ransom-ware got to the current machine in question, along with 2 other identical machines. Put our production team down for two days thanks to one of our electrical eng’s downloading some printer drivers from a shady website. Crawled nearly our entire network.
-
@wanderbread OK fair enough we can still work with that. I should have time in a bit to recreate the iso you need to burn to a cdrom.
(But if the fog server is on a private IP address, it would do little good for me to know its at 192.168.1.50 since that isn’t a routable IP address. There is no way I can reach it from here. Now if your fog server is using a public address [internet based] then you have more issues than me knowing it.)
-
@george1421 Oh sorry, (duhhh moment), 192.168.30.11 is the IP address I use internally.
-
@wanderbread Lets start with the simple iso image format. If this doesn’t work then I’ll go through the advanced route to create the iso.
We’ll use the ipxe rom-o-matic site to create the iso image you will burn onto a cdrom (dvd is not needed since the ipxe kernel is so small).
You will download that and burn it to a cdrom. To aid in your comfort scan it for viruses if you need. Then when you have time cdrom boot your computer and it should connect you to the fog ipxe menu. If not we’ll go the advanced route which will give me a bit more control on the drivers used.
-
@george1421 Thanks. This is greatly appreciated, I’ve got it on a disk. I’ll have to wait until our production hours are over to test, but I’ll get back to you.
-
@george1421 I’m not seeing where the IP is applicable on rom-o-matic. I’m probably overlooking something, attempting to create a different boot image. I didn’t have any luck with the image you provided.
-
@wanderbread Well that is a bit disappointing, but somewhat expected. Did it have an issue with detecting a dhcp IP address? Or was there a different error?
We’ll have to go through the advanced route and take some of the guesswork out of what is in the image. The IP address is the address of your fog server and we are chain loading to the fog server.
-
@george1421 Well I wasn’t actually able to boot from the image… or at least it seems that way. I set my boot order accordingly; on startup it went through the normal stuff, then "Boot from CD: " was displayed, the cursor blinked for 20 to 30 seconds, and it proceeded to boot from the HDD.
-
@wanderbread Interesting… You should have seen at least an iPXE splash screen.
-
@george1421 Upon further inspection, I don’t think the disk-drive is capable of reading from the disk I used, or something. I attempted to browse the disk in Explorer and I get an error saying the disk may be corrupt.
-
-
@wanderbread Well the disk may not be readable from windows since the disk format may be a linux variant.
-
@george1421 Burned to CD-R, it’s booting from it now, but it seems like it’s only seeing the onboard (non-functioning) network card.
EDIT:
I disabled both ports via BIOS configuration, and it still fails.I take back my previous statement, I think that it’s at least recognizing the ISA card. If I have a cable plugged in the MAC shows up as 94:94:94:… but if it’s not plugged in, it’s all 0’s
-
@wanderbread The initial image I sent you only knows about the first ethernet adapter, which it may be the built in broken one. That whole mess-of url I just posted is more advanced and contains all known ipxe drivers. I have not tested it yet to say its any better, worse or same as the first image.
-
@george1421 The image file created with that second URL I just posted pxe boots via virtual box with 2 network adapters and the first one unplugged. Does that mean it will work for you, ??
-
This post is deleted! -
@george1421 I’ll attempt to. Not sure if this is coincidence, or not, but for some reason the (ISA) network card isn’t working on my Windows install now. Like it doesn’t even show in my network adapters list anymore. Attempted to go through the “Add New Hardware” prompts, won’t recognize on hardware scan. When I try to add it manually by selecting from list, it’s present but there is an error message next to it, saying the device failed to start. Tried ignoring it and re-installing the drivers anyways, but was unsuccessful.
