|
augalex
|
 |
« on: December 19, 2007, 04:07:16 pm » |
|
Hy guys,
there's a big problem while trying to boot my first MD via PXE.
I got an Asus A7N8X-deluxe board, with two NICs onboard, when I connect one of them the md tries to boot via PXE, everything seems to go its way, until, the line: filename tftpboot/pxelinux.0 comes up, for about 20 seconds and after this.
After this, the last block written:
IP-Config eth0 complete (from 192.168.1.23)
adr: 192.168.80.255 broadcast: 192.168.80.255 netmask: 255.255.255.0
gateway: 192.168.80.1 dns0: 192.168.80.1 dns1: 0.0.0.0
rootserver: 192.168.80.1 rootpath: filename tftpboot/pxelinux.0
is repeated about hours in a really fast way.....
I already tried to setup a diskless client in the webadmin first, wich also causes no effect.
Changing the NIC = the same problem....
looking forward for some help.......
augalex
|
|
|
|
|
Logged
|
|
|
|
Zaerc
Alumni
LinuxMCE God
Posts: 2256
Department of Redundancy Department.
|
|
« Reply #1 on: December 19, 2007, 04:27:23 pm » |
|
You could try to disable the NIC you're not using.
|
|
|
|
|
Logged
|
"Change is inevitable. Progress is optional." -- Anonymous  |
|
|
|
tkmedia
|
|
« Reply #2 on: December 19, 2007, 04:29:42 pm » |
|
Had a similar problem at one point I think it is switching nics on you during the pxe boot. Try disabling one of the on-board nics.
Good luck
Warning - while you were typing a new reply has been posted. You may wish to review your post.
Zarec you beat me again.
|
|
|
|
|
Logged
|
|
|
|
|
augalex
|
|
« Reply #3 on: December 19, 2007, 04:36:27 pm » |
|
Wow, after hours and hours, thre different NICs, blood and tears.......
the solution was that easy.....
thanks a lot Zaerc
and of course, even if a little too late... *g* tkmedia.....
augalex
|
|
|
|
|
Logged
|
|
|
|
jca
Newbie
Posts: 11
|
|
« Reply #4 on: December 19, 2007, 09:20:07 pm » |
|
Wow, after hours and hours, thre different NICs, blood and tears.......
the solution was that easy.....
thanks a lot Zaerc
and of course, even if a little too late... *g* tkmedia.....
augalex
You should post that solution in the Wiki for the next person  |
|
|
|
|
Logged
|
|
|
|
spoolin1
First post!
Posts: 1
|
|
« Reply #5 on: April 25, 2008, 07:35:25 pm » |
|
can't wait to try this when I get home from work!
|
|
|
|
|
Logged
|
|
|
|
methodus
Newbie
Posts: 5
|
|
« Reply #6 on: June 19, 2008, 11:47:09 am » |
|
Hi,
I have a Jetway J9F2-Extreme. I deactivated the second NIC but it is still looping all day long. I also tryed to set up BIOS boot order and switching between both NICs....
How can I fix it?
Thanks...
Edit: actually I just deaktivated PXE. Is this all I have to do?
|
|
|
|
« Last Edit: June 19, 2008, 11:50:50 am by methodus »
|
Logged
|
|
|
|
|
totallymaxed
|
|
« Reply #7 on: June 19, 2008, 11:21:16 pm » |
|
Hi,
I have a Jetway J9F2-Extreme. I deactivated the second NIC but it is still looping all day long. I also tryed to set up BIOS boot order and switching between both NICs....
How can I fix it?
Thanks...
Edit: actually I just deaktivated PXE. Is this all I have to do?
Hmmm... you must have PXE boot enabled in BIOS otherwise your MD wont.... well PXE boot! Andrew |
|
|
|
|
Logged
|
|
|
|
|
Ritmo2k
|
|
« Reply #8 on: June 19, 2008, 11:55:46 pm » |
|
I am new to Linux MCE, but I know from PXE installs of Linux for servers which often have two nics the problem I think you are seeing is that possibly the nic that is plugged in and receives the pxe file starts, then the OS attempts to continue loading off the second nic. There are a few RH specific things to control this, but as I have no experience yet with Debian based Linux I wouldn't know what to add to the boot line.
Maybe someone familiar with this process in Debian based Linux can apply it here?
|
|
|
|
|
Logged
|
|
|
|
methodus
Newbie
Posts: 5
|
|
« Reply #9 on: June 20, 2008, 12:24:08 pm » |
|
Hi,
I have a Jetway J9F2-Extreme. I deactivated the second NIC but it is still looping all day long. I also tryed to set up BIOS boot order and switching between both NICs....
How can I fix it?
Thanks...
Edit: actually I just deaktivated PXE. Is this all I have to do?
Hmmm... you must have PXE boot enabled in BIOS otherwise your MD wont.... well PXE boot! Andrew Thank you Andrew, but actually this is not what I asked for. I have two nics and it keeps cycling as described in the first post. So I want to know how to deactivate one of the two devices, not both! |
|
|
|
|
Logged
|
|
|
|
|
Murdock
|
|
« Reply #10 on: November 29, 2008, 06:01:32 am » |
|
I just had the same problem. You just need to disable the on-board NIC via the BIOS menu. Hit [f2] or <del> upon first boot.
|
|
|
|
|
Logged
|
|
|
|
|
Domodude
Guest
|
|
« Reply #11 on: February 02, 2009, 11:55:02 am » |
|
Sorry to bring this up again. WIKI mentions a fix, but.... You could try to disable the NIC you're not using.
I have a retarded motherboard (albatron KI51PV-754) which does not allow turning off only one of the two integrated NICs. So either boot with two NICs or boot with none  Any way to adjust a config on the core, so it will pick the other NIC? |
|
|
|
|
Logged
|
|
|
|
Zaerc
Alumni
LinuxMCE God
Posts: 2256
Department of Redundancy Department.
|
|
« Reply #12 on: February 02, 2009, 12:23:07 pm » |
|
Sorry to bring this up again. WIKI mentions a fix, but.... You could try to disable the NIC you're not using.
I have a retarded motherboard (albatron KI51PV-754) which does not allow turning off only one of the two integrated NICs. So either boot with two NICs or boot with none Any way to adjust a config on the core, so it will pick the other NIC? Maybe try hooking both nics to the switch, desperate times call for desperate measures... |
|
|
|
|
Logged
|
"Change is inevitable. Progress is optional." -- Anonymous |
|
|
|
