That makes sense. The problem is that the reason folks created biosdevname was because systems with multiple NICs tend to enumerate those NICs in a different order every time the system reboots. Advising folks not to have second adapters doesn't seem like a long-term plan. I have a notebook that &qu...

OK, it looks like everything is working now. In the long term, it may be worth considering rewriting the install scripts to iterate through available interfaces rather than looking for eth0. With everyone starting to use biosdevname, things are going to continue to be interesting. I followed this li...

BTW, I tried your first suggestion right off the bat. The BIOS only allows me to disable both NICs at once or to configure them individually for "On", "On with PXE", or "On with iSCSI Boot Support." I think I saw a full CD installation page somewhere. I'll look. Full in...

No worries. I appreciate any help and am happy to provide any info I can to get this moving. My server's a few years old, but is by no means ancient: Dell PowerEdge T310 16GB RAM PERC 6/i RAID controller with 4 disks, configured as individual volumes. - the Amahi installer discovers the disks just f...

Sorry, I didn't answer your original question. Yes, I saw Network on the install screen, but I can't remember if it showed eth0. I'll try another reinstall and let you know.

Thanks for the quick response. I've had to shut down Amahi for now since that interface is serving up DHCP, but none of the clients can get to anything other than the HDA once they get an address from it... I've been looking into the problem on the Fedora forums and it seems to have something to do ...

Hi! I downloaded the Amahi 7 Express Install DVD and it installed just fine. Unfortunately, my HDA was never able to connect to Amahi.org to finish the install. When it finished rebooting, I could get to the HDA control panel, but couldn't install any apps. I tried reinstalling the HDA a couple of t...