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

    Dell iPXE issues

    Scheduled Pinned Locked Moved
    FOG Problems
    5
    16
    7.6k
    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.
    • cmlC
      cml Moderator
      last edited by

      Hello all,

      Wondering if anyone could shed some lite on a strange issue we have been having since upgrading to 1.0+ where whenever we boot one of our Dell Inspiron 1121’s from undionly.kpxe it hangs on initializing devices.

      Things I have tried.
      [LIST]
      []Booting from all files and chainloading from pxelinux.0.old all hang at the exact same spot
      [      ]Booting with DEBUG=device,pci,undiload,undinet and booting from usb via ipxe.usb hang on the same three lines
      [*]Spinning up another Fog server - same issue
      [/LIST]

      [CODE]PCI02:00.0 (8086:0087) has driver “undipci”
      PCI02:00.0 has mem 90400000 io 0 irq 10
      PCI02:00.0 probe failed: No such device (http://ipxe.org/2c80603b)[/CODE]

      Any ideas 😄

      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by

        PCI ID ‘8086:0087’ seams to be an Intel Corporation Centrino Advanced-N + WiMAX 6250, correct? Are you sure you want to PXE-boot over the wireless adapter? Sounds a bit like iPXE does not detect your normal ethernet card, maybe?? Or it might the detect the wireless card as the first one?!?

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • W
          Wolfbane8653 Developer
          last edited by

          I have noticed this issue a few times with different revisions. Try using the undionly.kkpxe (yes thats an extra k) and let us know. If this does not work please try upgrading as I ran into my kernels being corrupted once.

          1 Reply Last reply Reply Quote 0
          • cmlC
            cml Moderator
            last edited by

            Thanks for the advise.

            It seems that it is detecting the nic, once I booted undionly.kkpxe I got more of the initial boot.

            [CODE]
            UNDI device is PCI 01:00.0, type DIX+802.3
            555kb free base memory after PXE unload
            iPXE initialising devices…Adding UNDI root bus
            UNDINIC 0x28c54 using UNDI 0x88af34d8
            UNDINIC 0x28c54 has MAC address d4:b3:d9:05:f4:49 and IRQ 7 (this is the wired mac address)
            UNDINIC 0x28c54 has type DIX+802.3, speed 10000000, flags 0000dc1b
            UNDINIC 0x28c54 using interrupt mode
            UNDINIC 0x28c54 added
            Adding PCI root bus
            PCI 00:00.0 … has no driver
            PCI 00:02.0 … has no driver
            etc.
            [/CODE]

            [SIZE=3]I have updated to kernel [/SIZE][FONT=Ubuntu][COLOR=#555555]3.18.5 and am still having the same issue.[/COLOR][/FONT]

            1 Reply Last reply Reply Quote 0
            • JunkhackerJ
              Junkhacker Developer
              last edited by

              the kernel won’t have anything to do with this, you need to update your ipxe files instead.

              signature:
              Junkhacker
              We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

              1 Reply Last reply Reply Quote 0
              • cmlC
                cml Moderator
                last edited by

                Still having the same issues with updated ipxe files.

                Booting from ipxe usb with debug gives me
                [CODE]iPXE initialising devices…Adding 3c509 root bus
                Adding EISA root bus
                Adding Hyper-V root bus
                Failed to add Hyper-V root bus: No such device (http://ipxe.org/2c83403b)
                Adding ISA root bus
                Adding ISAPnP root bus
                Adding MCA root bus
                Adding PCI root bus
                PCI 00:00.0 (8086:0044 CLASS 060000) has no driver
                PCI 00:02.0 (8086:0046 CLASS 030000) has no driver
                PCI 00:16.0 (8086:3b64 CLASS 078000) has no driver
                PCI 00:1a.0 (8086:3b3c CLASS 0c0320) has no driver
                PCI 00:1b.0 (8086:3b56 CLASS 040300) has no driver
                PCI 00:1c.0 (8086:3b42 CLASS 060400) has no driver
                PCI 00:1c.1 (8086:3b44 CLASS 060400) has no driver
                PCI 00:1d.0 (8086:3b34 CLASS 0c0320) has no driver
                PCI 00:1e.0 (8086:2448 CLASS 060401) has no driver
                PCI 00:1f.0 (8086:3b0b CLASS 060100) has no driver
                PCI 00:1f.2 (8086:3b2f CLASS 010601) has no driver
                PCI 00:1f.3 (8086:3b30 CLASS 0c0500) has no driver
                PCI 00:1f.6 (8086:3b32 CLASS 118000) has no driver
                PCI 01:00.0 (1969:1062) has driver “undipci”
                PCI 01:00.0 has mem 90500000 io 1000 irq 7
                UNDI 0xdbb04 loading UNDI ROM 0xdbb84 to CS 964b DS 9165 for PCI 01:00.0
                UNDI 0xdbb04 loaded PXENV+ 964b:00d0 !PXE 964b:0070 entry 964b:0106
                UNDI 0xdbb04 using [581,614) kB of base memory
                UNDINIC 0xdbb04 using UNDI 0xdbb04
                UNDINIC 0xdbb04 has MAC address d4:b3:d9:05:f4:49 and IRQ 7
                UNDINIC 0xdbb04 has type DIX+802.3, speed 1000000, flags 0000dc1b
                UNDINIC 0xdbb04 using interrupt mode
                UNDINIC 0xdbb04 added
                PCI 02:00.0 (8086:0087) has driver “undipci”
                PCI 02:00.0 has mem 90400000 io 0 irq 10
                PCI 02:00.0 probe failed: No such device (http://ipxe.org/2c80603b)[/CODE]

                I think this is going to end up being an iPXE issue, so I went ahead and posted the issue on the iPXE forums. I will let y’all know if a fix is found.

                Thanks everybody for the help.

                1 Reply Last reply Reply Quote 0
                • S
                  Sebastian Roth Moderator
                  last edited by

                  You seem to have more than one network adapter… This is the one you propably want to make work (the second one is a wireless adapter):
                  [CODE]PCI 01:00.0 (1969:1062) has driver “undipci”
                  PCI 01:00.0 has mem 90500000 io 1000 irq 7
                  UNDI 0xdbb04 loading UNDI ROM 0xdbb84 to CS 964b DS 9165 for PCI 01:00.0[/CODE]
                  Trying to find other people having used iPXE with 1969:1062 network card didn’t show up a lot of results when searching on the web. There is just an old post from 2011: [url]http://lists.ipxe.org/pipermail/ipxe-devel/2011-November/001024.html[/url] (see the ID there and read up a couple of post before that)…

                  iPXE mailinglist is definitely the better place to find out about this! Would be great if you’d report back on how things turned out…

                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                  1 Reply Last reply Reply Quote 0
                  • cmlC
                    cml Moderator
                    last edited by

                    Hey all figure I’d give an update.

                    Never heard anything back from the iPXE community but pressed on and almost got it solved.

                    I added [COLOR=#ff0000]PCI_ROM(0x1969, 0x1062, “atl1e_62”, “Attansic L1E 0x1062”, 0),[/COLOR] drivers/net/atl1e.c and rebuilt iPXE and the laptop now fully loads iPXE! <I ran around the library when this happened>

                    Unfortunately I get /default.ipxe…Connection times out after a few minutes.

                    From the iPXE shell running dhcp<fails>, ifconf<passes> i can then chain the file.

                    If i leave out dhcp ifconf fails, if I run ifconf first it fails but then if I run dhcp it passes which doesn’t make any since to me.

                    So in a confusing summary:
                    dhcp(fail)>ifconf>chain - works
                    ifconf(fail)>dhcp>chain - works
                    dhcp(fail)>dhcp>chain - works
                    ifconf(fail)>ifconf>chain - works

                    Set ipxescript to the following:
                    [CODE]#!ipxe
                    ifclose
                    ifopen && goto bootme || goto netstart
                    :netstart
                    dhcp
                    ifopen || reboot
                    isset ${next-server} && goto netboot || goto setserv
                    :setserv
                    echo -n Please enter tftp server: && read next-server && goto bootme
                    :bootme
                    isset ${next-server} && goto netboot ||
                    set next-server ${proxydhcp/next-server}
                    isset ${next-server} && goto netboot || goto netstart
                    :netboot
                    ifopen
                    dhcp || ifconf
                    chain tftp://${next-server}/default.ipxe || shell
                    [/CODE]

                    Which then gives:
                    Configuring (net0 d4:be:d9:05:f4:49)…Error 0x040ee19 ([url]http://ipxe.org/040ee119[/url])
                    Configuring (net0 d4:be:d9:05:f4:49)…Error 0x040ee19 ([url]http://ipxe.org/040ee119[/url])

                    And the boot process restarts. Any suggestions?

                    1 Reply Last reply Reply Quote 0
                    • Tom ElliottT
                      Tom Elliott
                      last edited by

                      Do you have STP enabled on your network (if so can you disable it temporarily or enable Rapid STP/Portfast?)

                      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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                      1 Reply Last reply Reply Quote 0
                      • cmlC
                        cml Moderator
                        last edited by

                        Same thing, the process only hangs on this particular model of laptop. I can get everything to load manually, but anything done through ipxescript fails.

                        1 Reply Last reply Reply Quote 0
                        • cmlC
                          cml Moderator
                          last edited by

                          More updates!

                          Enabled DEBUG=dhcp,tftp,http in the current ipxe build and this is the error that is thrown when running the dhcp command.

                          [CODE]DHCP 0x27f64 entering discovery state
                          DHCP 0x27f64 DHCPDISCOVER
                          DHCP 0x27f64 could not transmit UDP packet: Error 0x7f86216b (http://ipxe.org/7f86216b)
                          DHCP 0x27f64 DHCPDISCOVER
                          DHCP 0x27f64 could not transmit UDP packet: Error 0x7f86216b (http://ipxe.org/7f86216b)
                          DHCP 0x27f64 DHCPDISCOVER
                          DHCP 0x27f64 could not transmit UDP packet: Error 0x7f86216b (http://ipxe.org/7f86216b)
                          DHCP 0x27f64 DHCPDISCOVER
                          DHCP 0x27f64 could not transmit UDP packet: Error 0x7f86216b (http://ipxe.org/7f86216b)
                          Error 0x040ee19 (http://ipxe.org/040ee19)[/CODE]

                          Running dhcp again gives this.
                          [CODE]DHCP 0x27f64 entering discovery state
                          DHCP 0x27f64 DHCPDISCOVER
                          DHCP 0x27f64 DHCPOFFER from 10.1.1.1:67 (10.1.1.10) for 10.1.1.104
                          .DHCP 0x27f64 DHCPDISCOVER
                          DHCP 0x27f64 DHCPOFFER from 10.1.1.1:67 (10.1.1.10) for 10.1.1.104
                          .DHCP 0x27f64 entering request state
                          .DHCP 0x27f64 DHCPREQUEST to 10.1.1.10:67 for 10.1.1.104
                          DHCP 0x27f64 DHCPACK from 10.1.1.1:67 (10.1.1.10) for 10.1.1.104[/CODE]

                          10.1.1.1 - Gateway
                          10.1.1.10 - DHCP
                          10.1.1.104 - Client

                          I will solve this, I must.

                          1 Reply Last reply Reply Quote 0
                          • W
                            Wolfbane8653 Developer
                            last edited by

                            This post is deleted!
                            1 Reply Last reply Reply Quote 0
                            • W
                              Wolfbane8653 Developer
                              last edited by

                              [quote=“Tom Elliott, post: 43307, member: 7271”]Do you have STP enabled on your network (if so can you disable it temporarily or enable Rapid STP/Portfast?)[/quote]

                              HELLO Tom has a valid point here. If STP is enabled and you don’t have Portfast enabled it will cause iPXE not to work or work sporadically.
                              [url]http://fogproject.org/wiki/index.php/IPXE#What_do_I_enable_and_disable.3F[/url]

                              1 Reply Last reply Reply Quote 0
                              • cmlC
                                cml Moderator
                                last edited by

                                RSTP is enabled and here is the config for the interface on the switch:
                                [CODE]interface GigabitEthernet0/6
                                switchport access vlan 100
                                switchport mode access
                                switchport nonegotiate
                                switchport voice vlan 200
                                spanning-tree portfast
                                [/CODE]

                                1 Reply Last reply Reply Quote 0
                                • cmlC
                                  cml Moderator
                                  last edited by

                                  More modifications to the ipxescript and it works!!!

                                  I know this is a very specific use case and probably a horrible way to go about it, but if it helps here are the modifications I made.

                                  [CODE]#!ipxe
                                  ifclose
                                  ifopen && goto bootme || goto netstart
                                  :netstart
                                  dhcp && goto netboot || goto netstart
                                  :setserv
                                  echo -n Please enter tftp server: && read next-server && goto bootme
                                  :bootme
                                  isset ${next-server} && goto netboot ||
                                  set next-server ${proxydhcp/next-server}
                                  isset ${next-server} && goto netboot || goto netstart
                                  :netboot
                                  ping -c 1 FOG IP || goto netstart
                                  chain tftp://${next-server}/default.ipxe || shell
                                  [/CODE]

                                  Thank you guys for all of your help and thanks to all the devs for everything. Fog is a truly amazing imaging system.

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    Sebastian Roth Moderator
                                    last edited by

                                    Awsome that you got it running now!

                                    Have you talked to iPXE devs too?? Or do you mean FOG devs? I am just wondering because maybe iPXE devs would be able to help out fixing the driver itself. But if this is working for you, you might just leave it like that. Unfortunately I neither have the time nor the hardware to help with this any further although I’d love to help to get this properly fixed. 😉

                                    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

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

                                    178

                                    Online

                                    12.0k

                                    Users

                                    17.3k

                                    Topics

                                    155.2k

                                    Posts
                                    Copyright © 2012-2024 FOG Project