Closed PaulRobert1 closed 5 years ago
hello, do you have a LAN cable connected to the RPi 1 and does your RPi 1 got an IP address from that network?
can you please download/clone tha project again... at least the file p2-include-var.sh ... i added some code to gather the name of the networkadapter for RPi1, i didn't tested my scripts on an RPi1 before. hope it will work for you now.
Thank you for the fast response, i am going to test it now, yes i have cable connected to lan, ifconfig shows valid ip, and can navigate internet
tested it, now when I run part 2 I just get a > and i can type after it, nothing else happens
do you mean part2 script was running without errors, but and after the script exited, your RPi installation is broken?
No, when i ran part 2 the 1st time i downloaded the project, it said no ip found, and incomplete command error, the second time i dowloaded it when i run part 2 , i get a new line in the terminal with > No installation of part 2 whatsoever.
On Fri, Mar 15, 2019, 20:30 beta-tester notifications@github.com wrote:
do you mean part2 script was running without errors, but and after the script exited, your RPi installation is broken?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beta-tester/RPi-PXE-Server/issues/14#issuecomment-473396518, or mute the thread https://github.com/notifications/unsubscribe-auth/ApjNDehy39jG1MsELBlTDIaARJUDkZI6ks5vW-a9gaJpZM4b2Auh .
A screenshot of the error is in the attachment above
I get the same error when trying to install with bash
thats strange...
i just tested the script on a RPi1B rev2 (512MB) and RPi1B+ and it executed successfully. i used the actual Raspbian version Raspbian Stretch with desktop the Desktop version is maybe too heavy for an RPi1, it run extremly slow to finish. what version are you using?
the script should not do any interaction with the user.
and at the moment, i do not see, where that >
could come from.
EDIT: eh... saw your screenshot...
i see you are running the script as root. please run the script without root (su).
bash install-pxe-server_pass2.sh
I tried with root, without root, with bash, with ./ I have raspbian stretch the basic, not the full one, downloaded today
On Fri, Mar 15, 2019, 20:54 beta-tester notifications@github.com wrote:
thats strange...
i just tested the script on a RPi1B rev2 (512MB) and RPi1B+ and it executed successfully. i used the actual Raspbian version Raspbian Stretch with desktop https://www.raspberrypi.org/downloads/raspbian/ the Desktop version is maybe too heavy for an RPi1, it run extremly slow to finish. what version are you using?
the script should not do any interaction with the user. and at the moment, i do not see, where that > could come from.
EDIT: eh... saw your screenshow... i see you are running the script as root. please run the script without root (su). bash install-pxe-server_pass2.sh
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beta-tester/RPi-PXE-Server/issues/14#issuecomment-473404154, or mute the thread https://github.com/notifications/unsubscribe-auth/ApjNDU2oAHL3u17zXloXtBho0WoR4sQfks5vW-xxgaJpZM4b2Auh .
this is the same version i used. what version of RPi1 do you have RPi1B rev.1 with 256MB (short GPIO header), a RPi1B rev2 with 512MB (short GPIO header) or a RPi1B+ with 512MB and long GPIO header?
if nothing will help, try to edit the p2-include-var.sh
file and add the correct interface nam at line 33.
e.g.:
INTERFACE_ETH0=eth0
in case eth0
is not your network interface name, please use the right name.
Rpi 1 short gpio header, model b 512mb
On Fri, Mar 15, 2019, 21:05 beta-tester notifications@github.com wrote:
this is the same version i used. what version of RPi1 do you have RPi1B rev.1 with 256MB (short GPIO header), a RPi1B rev2 with 512MB (short GPIO header) or a RPi1B+ with 512MB and long GPIO header?
if nothing will help, try to edit the p2-include-var.sh file and put the correct interface nam at line 33:
INTERFACE_ETH0=eth0
in case eth0 is not your network interface name, please use the right name.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beta-tester/RPi-PXE-Server/issues/14#issuecomment-473407480, or mute the thread https://github.com/notifications/unsubscribe-auth/ApjNDSZ4GHQBGC45BUZWO2_ztOiMFvTJks5vW-8JgaJpZM4b2Auh .
Thank you for your help, i will check and see.
On Fri, Mar 15, 2019, 21:05 beta-tester notifications@github.com wrote:
this is the same version i used. what version of RPi1 do you have RPi1B rev.1 with 256MB (short GPIO header), a RPi1B rev2 with 512MB (short GPIO header) or a RPi1B+ with 512MB and long GPIO header?
if nothing will help, try to edit the p2-include-var.sh file and put the correct interface nam at line 33:
INTERFACE_ETH0=eth0
in case eth0 is not your network interface name, please use the right name.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beta-tester/RPi-PXE-Server/issues/14#issuecomment-473407480, or mute the thread https://github.com/notifications/unsubscribe-auth/ApjNDSZ4GHQBGC45BUZWO2_ztOiMFvTJks5vW-8JgaJpZM4b2Auh .
i will test the script again... this will take a while.
in the meantime please modify the p2-include-var.sh file and add eth0
as shown above.
Ok
On Fri, Mar 15, 2019, 21:11 beta-tester notifications@github.com wrote:
i will test the script again... this will take a wile. in the meantime please modify the p2-include-var.sh file and add eth0 as shown above.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beta-tester/RPi-PXE-Server/issues/14#issuecomment-473408986, or mute the thread https://github.com/notifications/unsubscribe-auth/ApjNDVyR9U6ed_VV5dTiUssD1VqrMFwHks5vW_BPgaJpZM4b2Auh .
i am out of ideas.
i added a "fallback" to the script to use eth0
in case it could not gather name of the interface from the system.
but normally it should have worked already with the first version of the fix.
if it is still not working for you.
p2-include-var.sh
is the newest version (should have the # fallback
included).p2-include-var.sh
is in the same folder as the install-pxe-server_pass2.sh
file.su
, no sudo
).find /sys/devices/ -type d | grep "1:1.0/net/"
giving you on the console?your fix worked, thank you very much! i am now downloading the os list selected, if say i want to add a windows 10 iso what is the procedure? I put the iso in the iso folder, add the name of the iso in handle.sh and re run part 2?
thank you for your report and good to hear, that it works.
for the windows 10 iso, do you mean a windows 10 PE iso that is around 500MByte big, or do you mean a whole windows 10 installation iso that is about 3GByte big?
if you have a Windows PE iso it is easy to integrate to the PXE boot process. you can add it as memdisk - it is not the most elegant way and eats twice the RAM as necessary, but it is easy. from within the Win PE, you can mount a (samba) network share to a windows 10 installation media and install windows via that share.
to PXE boot the full Windows 10 installation iso will be complicated, because of its size. it can't be loaded as a memdisk anmore. and because of you have to tell windows where to find the installation files on the network.
see also: Download and install the Windows ADK to create you own Windows PE iso. Windows PE (WinPE) Configure a PXE server to load Windows PE
a template for Windows PE (ISO) is already in the script. you have to provide a windows PE iso that must have the name win-pe-x86.iso
and an empty win-pe-x86.url
file. copy both to the destination folder, where all the ISOs were stored and re-run the pass2 script. it should see the win-pe-x86.iso and integrate it to the PXE-menu.
note, that the architecture (x86 or amd64) of Windows PE and Windows 10 installation must be the same, when you try to install Windows from within Windows PE. if you only want to get access to an already installed Windows system, you can use either windows x86 or amd64 architecture. then it doesn't matter. i use the x86 version, because there are more applications available that runs on x86 and are not aveilable for amd64.
maybe you open a new issue with a request to windows PE. then i will try to explain it there for the public or will add a wiki.
Hello, when I try to install pass2.sh i get ip adress not found error, i have lan setup and tested on it. It also displays commandline incomplete. Please help Kind Regards.