Realtek 8111\8168 & undionly.kpxe -> hangs on Initialising Devices...


  • Developer

    This dirty hack in my default.ipxe file seemed to do the trick:

    #!ipxe
    cpuid --ext 29 && set arch x86_64 || set arch i386
    isset ${net1/mac} && chain [url]http://10.0.0.50/fog/service/ipxe/boot.php?mac=${net1/mac}[/url] ||
    params
    param mac ${net0/mac}
    param arch ${arch}
    chain [url]http://10.0.0.50/fog/service/ipxe/boot.php##params[/url]


  • Developer

    undionly.kpxe is used by fog because it is compatible with more network cards. .pxe versions dump the UNDI and require recompiling with additional drivers to support new cards


  • Developer

    I’m trying to get more familiar with iPXE. Am I OK to assume that I can (attempt to) build an all-drivers ipxe.kpxe file and use it with FOG as long as the script to chainload to default.ipxe happens? I’m trying to figure out why undionly.kpxe is being used by default in FOG. Thanks for any feedback.

    Andy


  • Developer

    Just to add some more notes to the thread - my test machines include a Biostar A880GB+ motherboard with the Realtek NIC I referenced earlier. The other is an Asus laptop - a K60IJ with an Atheros AR8121/AR8113/AR8114 pci-e NIC along with an Atheros wireless card. Again, the “stock” FOG undionly.kpxe file didn’t work with the AR8121. I got a “insert boot media” error.

    I decided to try using the undionly.kpxe file that I compiled for the Realtek NIC. Full host registration seemed to go fine but if I told FOG to image the computer upon reboot, undionly.kpxe would see the wireless NIC (identified as net0) and bypass that with an error. It would then identify the AR8121 (as net1) and boot into the FOG menu with a “Not a registered host” error. On a hunch, I yanked the wireless card and then imaging could take place properly if the AR8121 was identified as net0. I’m sure what this all means yet, but I wanted to note my experience.

    These two hosts worked fine in 0.32 from start to finish, including snapins & multicasting.

    Andy


  • Senior Developer

    Again, I’m not aware of anything wrong with the undionly.kpxe file. The kernel however is a different beast. The kernel is simply trying to load the drivers. The only way to remove something is to remove the related item from the kernel in its entirety. This i2c-parport-light adapter isn’t necessarily the thing taking a period of time but rather the last message you see while the rest of the drivers are loading.


  • Developer

    Tom,

    I recompiled a new undionly.kpxe using this site: rom-o-matic.eu and with help from these forums on chainloading default.ipxe, I was able to upload an image into FOG 1.0.0.

    Is there a way to remove (or reduce) the 60 second wait time on the “i2c-parport-light adapter type unspecified” message before the kernel is finally loaded?

    Embedded script:#!ipxe
    dhcp
    chain default.ipxe

    Thanks again,

    Andy


  • Developer

    I apologize - this was a different undionly.kpxe file in the picture. BUT my results were exactly the same for iPXE.


  • Developer

    Tom,

    Thanks much for the reply.

    FOG 1.0.0 (I believe revision 1650), Ubuntu 13.10 server

    I have checked the wiki and forums and don’t see my exact issue anywhere. Updating the kernel seems one step ahead as the kernel never loads. It hangs and doesn’t reboot. Same behavior whether I restart or start cold. Picture attached.

    Here’s what I see in apache error log today repeatedly (not much help IMO):
    PHP Warning: date_default_timezone_get(): It is not safe to rely on the system’s timezone settings. You are required to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone ‘UTC’ for now, but please set date.timezone to select your timezone. in /var/www/fog/commons/system.php on line 11, referer: [url]http://10.0.0.51/fog/management/index.php?node=home[/url]

    Andy[ATTACH=full]725[/ATTACH]

    [url="/_imported_xf_attachments/0/725_realtekhangs.jpg?:"]realtekhangs.jpg[/url]


  • Senior Developer

    TO my knowledge, this driver does already exist within the kernel. I don’t know of any issues with this device and undionly.kpxe though. How does it hang? Everytime you start the dive, or everytime the device is restarted? By start, I mean from a powered off state, where restart is still powered the ntire time.


Log in to reply
 

381
Online

6.4k
Users

13.8k
Topics

130.0k
Posts