• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Configuring Boot with Off-board ISA Intel Pro/100

    Scheduled Pinned Locked Moved
    General Problems
    2
    26
    6.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • george1421G
      george1421 Moderator
      last edited by george1421

      This must be a really old (ancient) network card. Does this card have a ROM slot in it?

      Some of the pro/100s had a utility that you needed to use to enable pxe booting.

      ref: http://www.intel.com/content/www/us/en/support/network-and-i-o/ethernet-products/000005992.html
      ref: http://www.intel.com/content/www/us/en/support/network-and-i-o/ethernet-products/000005626.html

      It appears you need the bootutil.exe utility to interact with the network card. I remember that the 3com cards had a similar configuration utility for their isa cards.

      <edit> found another site with instructions for enabling the pxe boot agent on the intel cards: http://www.urtech.ca/2010/08/how-to-make-an-intel-network-card-pxe-boot/

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

      1 Reply Last reply Reply Quote 0
      • W
        wanderbread
        last edited by wanderbread

        Yes, indeed it is!
        The intel links provided look familiar, I may have attempted this already some time ago. I seem to remember lack of support for the ISA cards. However, I could be mistaken, I’ll give it a shot.

        <edit> First stop: Find a boot rom or a new card, I guess.

        george1421G 1 Reply Last reply Reply Quote 0
        • george1421G
          george1421 Moderator @wanderbread
          last edited by george1421

          @wanderbread Is the boot rom socket filled?

          If you have no success with the onboard boot rom, you can always boot from a USB stick into the fog ipxe menu. In this case you will use an alternate pxe boot rom called ipxe which fog uses to supplement the pxe boot rom.

          This is a somewhat older info, but should get you started. https://forums.fogproject.org/topic/6347/usb-boot-bios-client-into-fog-menu If you need help I can help build this boot kernel for you.

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

          W 1 Reply Last reply Reply Quote 1
          • W
            wanderbread @george1421
            last edited by wanderbread

            @george1421 No, there’s nothing in the socket, that coupled with the fact that I don’t think ISA-to-USB cards even exist is why I was thinking I needed to find a new wireless card, unless there is a way I could use that boot image on a CD or floppy disk. Plan on diving into all that today to see where I can get.

            george1421G 1 Reply Last reply Reply Quote 0
            • george1421G
              george1421 Moderator @wanderbread
              last edited by

              @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.

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

              W 1 Reply Last reply Reply Quote 0
              • W
                wanderbread @george1421
                last edited by

                @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.

                george1421G 1 Reply Last reply Reply Quote 0
                • george1421G
                  george1421 Moderator @wanderbread
                  last edited by

                  @wanderbread Will you tell me the IP address of your fog server?

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                  W 1 Reply Last reply Reply Quote 0
                  • W
                    wanderbread @george1421
                    last edited by wanderbread

                    @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.

                    george1421G 1 Reply Last reply Reply Quote 0
                    • george1421G
                      george1421 Moderator @wanderbread
                      last edited by

                      @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.)

                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                      W 1 Reply Last reply Reply Quote 0
                      • W
                        wanderbread @george1421
                        last edited by

                        @george1421 Oh sorry, (duhhh moment), 192.168.30.11 is the IP address I use internally.

                        george1421G 1 Reply Last reply Reply Quote 0
                        • george1421G
                          george1421 Moderator @wanderbread
                          last edited by

                          @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).

                          https://www.rom-o-matic.eu/build.fcgi?BINARY=ipxe.iso&BINDIR=bin&REVISION=master&DEBUG=&EMBED.00script.ipxe=%23!ipxe dhcp set next-server 192.168.30.11 set filename undionly.kpxe chain tftp%3A//%24{next-server}/%24{filename}&

                          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.

                          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                          W 2 Replies Last reply Reply Quote 0
                          • W
                            wanderbread @george1421
                            last edited by wanderbread

                            @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.

                            1 Reply Last reply Reply Quote 0
                            • W
                              wanderbread @george1421
                              last edited by wanderbread

                              @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.

                              george1421G 1 Reply Last reply Reply Quote 0
                              • george1421G
                                george1421 Moderator @wanderbread
                                last edited by

                                @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.

                                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                                W 1 Reply Last reply Reply Quote 0
                                • W
                                  wanderbread @george1421
                                  last edited by

                                  @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.

                                  george1421G 1 Reply Last reply Reply Quote 0
                                  • george1421G
                                    george1421 Moderator @wanderbread
                                    last edited by

                                    @wanderbread Interesting… You should have seen at least an iPXE splash screen.

                                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                                    W 1 Reply Last reply Reply Quote 0
                                    • W
                                      wanderbread @george1421
                                      last edited by

                                      @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.

                                      george1421G 1 Reply Last reply Reply Quote 0
                                      • george1421G
                                        george1421 Moderator
                                        last edited by

                                        Saving a bit more complex boot file for later. Don’t worry about this for now. I will test in the lab to ensure it boots.

                                        https://rom-o-matic.eu/build.fcgi?BINARY=ipxe.iso&BINDIR=bin&REVISION=master&DEBUG=&EMBED.00script.ipxe=%23!ipxe ifopen isset %24{net0/mac} %26%26 dhcp net0 || goto dhcpnet1 echo Received DHCP answer on interface net0 %26%26 goto proxycheck %3Adhcpnet1 isset %24{net1/mac} %26%26 dhcp net1 || goto dhcperror echo Received DHCP answer on interface net1 %26%26 goto proxycheck %3Adhcperror dhcp || prompt --key s --timeout 10000 DHCP failed%2C hit 's' for the iPXE shell%3B reboot in 10 seconds %26%26 shell || reboot %3Aproxycheck isset %24{proxydhcp/next-server} %26%26 isset %24{next-server} %26%26 echo Duplicate option 66 (next server) from DHCP proxy and DHCP server %26%26 echo Using IP sent by DHCP proxy %24{proxydhcp/next-server} %26%26 prompt --timeout 5000 || goto nextservercheck %3Anextservercheck isset %24{proxydhcp/next-server} %26%26 set next-server %24{proxydhcp/next-server} || isset %24{next-server} %26%26 goto netboot || goto setserv %3Asetserv echo -n Please enter tftp server%3A %26%26 read next-server %26%26 goto netboot || goto setserv %3Anetboot chain tftp%3A//%24{next-server}/default.ipxe || prompt --key s --timeout 10000 Chainloading failed%2C hit 's' for the iPXE shell%3B reboot in 10 seconds %26%26 shell || reboot&general.h/DOWNLOAD_PROTO_HTTPS:=1&general.h/DOWNLOAD_PROTO_FTP:=1&general.h/DOWNLOAD_PROTO_NFS:=1&general.h/DOWNLOAD_PROTO_FILE:=1&general.h/SANBOOT_PROTO_ISCSI:=1&general.h/SANBOOT_PROTO_AOE:=1&general.h/SANBOOT_PROTO_IB_SRP:=1&general.h/SANBOOT_PROTO_FCP:=1&general.h/SANBOOT_PROTO_HTTP:=1&general.h/IMAGE_PXE:=1&general.h/IMAGE_SCRIPT:=1&general.h/IMAGE_BZIMAGE:=1&general.h/IMAGE_PNM:=1&general.h/NSLOOKUP_CMD:=1&general.h/TIME_CMD:=1&general.h/DIGEST_CMD:=1&general.h/LOTEST_CMD:=1&general.h/VLAN_CMD:=1&general.h/PXE_CMD:=1&general.h/REBOOT_CMD:=1&general.h/POWEROFF_CMD:=1&general.h/IMAGE_TRUST_CMD:=1&general.h/PCI_CMD:=1&general.h/PARAM_CMD:=1&general.h/NEIGHBOUR_CMD:=1&general.h/PING_CMD:=1&general.h/CONSOLE_CMD:=1&general.h/IPSTAT_CMD:=1&general.h/CERT_CMD:=1&usb.h/USB_HCD_XHCI:=1&usb.h/USB_HCD_EHCI:=1&usb.h/USB_HCD_UHCI:=1&usb.h/USB_KEYBOARD:=1&console.h/CONSOLE_FRAMEBUFFER:=1&console.h/CONSOLE_VMWARE:=1&general.h/ROM_BANNER_TIMEOUT=40&

                                        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                                        1 Reply Last reply Reply Quote 0
                                        • george1421G
                                          george1421 Moderator @wanderbread
                                          last edited by

                                          @wanderbread Well the disk may not be readable from windows since the disk format may be a linux variant.

                                          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                                          W 1 Reply Last reply Reply Quote 0
                                          • W
                                            wanderbread @george1421
                                            last edited by wanderbread

                                            @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

                                            george1421G 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 1 / 2
                                            • First post
                                              Last post

                                            154

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project