You are not logged in.
Hi,
I tried to install Archlinux on two different machine. (Dell Latitude E4300 and a Dell Optiplex 755)
After making of the proper pxe+dhcp setup,.... I downloaded the https://releng.archlinux.org/pxeboot/ipxe.pxe
file and tried to boot via lan. It stopped after selecting mirror.... I said ok. Let's try with different way.
I tried boot via installer CD and..... network not worked.
The big surprises were come when I tried to start the original (untouched) linux system...
On both PC the network connection gone died. Cannot send or receive any packets through the
network card that I used in the pxe bootup process.
I tried to use the network card via sysrescue cd ant it's nothing.
The only way I could make the card working is to install windows and use it.
Both machine has Intel network card in it.
Laptop: 82567LM
Optiplex 755: 82566DM-2
What I tried:
- force/set speed, duplex, tso, advertise parameters on both => not a solution
- setup fixip instead of using dhcp => not a solution
- different distributions => not a solution
My guess:
The pxe file made some changes in my network card's firmware, state variables
that made both of them unsuable under linux and windows can revert them via driver settings.
Offline
If you mess up anywhere along the way, you have to reload the whole image over the internet for each machine. If you have another machine running Arch (which you probably don't), you can make it a PXE server, and you could further test the problem from there. But you have PXE server somewhere serving the ipxe.pxe file. All you would need is the base installation with a tweak to mkinitcpio.conf and tftp, dhcp, nfs, etc. from the diskless nfs root wiki. Remember to install the mkinitcpio-nfs-utils package. It's better if you have the local PXE server, because you can actually set up thin clients, not just an install image root. You can also use packages in the cache from the main machine and distribute them to install your PXE server, as well as the clients (of course, watch architectures).
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
I think we have some misunderstanding. The problem is not with installing (I am installed it on both device). I could solve it by many way.
The main problem is that I have 1 notebook and 1 PC with a half killed ethernet card and I could not make it working under any linux distributions.
The fun is that under windows the cards still works well but somehow under linux I could not make them work again.
That's why I think there is some mode hack inside that ipxe.pxe file which killed my cards half.
Offline
I think a pxe file just needs a little text editing.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Hi,
I have the same problem with my lenovo X200s, since I tried to install archlinux via IPXE the Ethernet NIC does not not work anymore under Linux but under Windows.
Arch linux installation hanged after login the initial ramdisk and after that the Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network Connection is unusable under Windows.
tftpboot]# file ipxe.pxe
ipxe.pxe: pxelinux loader (version 3.70 or newer)
The file mentioned in the post is not just a little text file and the problem started after the initrd was downloaded.
Perhaps 'nomorewindows' should read what the other list members instead of 'the stupid windows' pharsing! The hint to download the whole image, if the network is dead is nonsens.
Whould be nice to get a qualified help, if anyone find a solution. No I have to use a USB adapter under Linux.
ramuller
P.S.
Last edited by ramuller (2015-02-05 19:00:41)
Offline
Are you UEFI? You'll need the uefi pxe file instead of the BIOS pxe file from syslinux.
OH wait you're using IPXE to download the kernel and initramfs. And from that, the driver state for the network card is unknown. Is it even loading the module for your card?
OP didn't say what his NIC was.
Other guy tells me what it is, but the connection between network card, IPXE and the Linux doesn't work with my card isn't exactly clear.
Last edited by nomorewindows (2015-02-05 19:34:41)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Hi again,
the problem is that the NIC is dead after I and goshawk tried to install arch linux via pxe, that means that even the initial dhcp request during pxe boot fails.
I'm using a lenovo X200s.
Again the facts for a non mouse user:
Start condition:
NIC (intel 82567LM) works fine
- Fedora 20
- Windows 7
Installation attempt
Attempt to install arch Linux with the ipxe.pxe from arch web site
- initial ramdisk loaded
- some other file loaded (sorry no logs)
- loading hangs in acquire network address
- reboot after 20min.
Result:
NIC is dead
- dhcp during pxe boot does not work -> so not any ipxe or anything else can be loaded over Ethernet
- Ethernet is not working anymore under Fedora
- Ethernet is working under Windows 7
I rebooted both OS' several times but no change, so since goshawk has the same problem I assume that the network driver from arch linux made something really bad to the NIC e.g. changing some non-volatile memory, which is bricking the unit.
If I don't find a nice tool to fix the problem, perhaps I'll install ARCH from disk and try to figure out what the module does, even it's a few years ago I wrote Linux kernel modules.
goshawk: If you found a solution, please let me know!
BR
Ralf (Mouse user)
Offline
DHCP without PXE directives doesn't get a dhcp address? Not sure if mii-tool or ethtool in the install image. I don't think your module needs firmware, Can you tell which kernel module it is? Tell us what you can gather from fedora.
Last edited by nomorewindows (2015-02-06 12:07:44)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Hi nomorewindows,
have you ever made a PXE installation? PXE boot is invited for thin clients without any disk, so means it should start without ant shell just from cold start at the moment when the device starts. No kernel, no tools no shell no tools. Take a breath and a look here http://ipxe.org .
You talk about modules and tools?!?!?
ramuller
Offline
I was able to solve it.
Solution (for my problem) first:
install arch linux from disk/usb e.g. I used the dual iso + unet... to the device without network connection
Step by step after booting :
- fire up the network with ifconfig ... and it worked
- boot from USB/CD (IPXE does not work:(
- # it's anyway a live system 32 bit-
- : I used ifconfig to bring the interface up
- suddenly my eth0 was back working (no systemd like if renaming)
- boot FED20 -64(didn't work)
- boot Windows 7-64, everything was OK
- boot FED20-64 Everything OK
NIC works again;)
Analysis:.
I suppose there is a mix with x86-32 and x86-64 microcode ending up in the NIC's volatile memory .
thanks to goshawk
to high light the problem
ramuller
Last edited by ramuller (2015-02-06 18:50:16)
Offline
Hi nomorewindows,
have you ever made a PXE installation? PXE boot is invited for thin clients without any disk, so means it should start without ant shell just from cold start at the moment when the device starts. No kernel, no tools no shell no tools. Take a breath and a look here http://ipxe.org .
You talk about modules and tools?!?!?ramuller
Post #2 describes such an encounter from nfs diskless arch wiki.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline