Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add documentation about netbooting LibreELEC on Raspberry Pis #18

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

wklaebe
Copy link

@wklaebe wklaebe commented Jun 22, 2021

No description provided.

@lrusak lrusak requested a review from HiassofT June 25, 2021 21:50
@bam80
Copy link
Contributor

bam80 commented Jan 30, 2022

@HiassofT ?

@wklaebe wklaebe force-pushed the feature/document-raspi-netboot branch from ef8fb12 to b2ff412 Compare October 9, 2022 13:12
@HiassofT HiassofT removed their request for review October 9, 2022 14:57
@HiassofT
Copy link
Member

HiassofT commented Oct 9, 2022

First of all, thanks a lot for your contribution!

I'd prefer if you structure the wiki page a bit and focus on the LE specific bits:

Start with the general LE setup, i.e. boot/flash must be made available both via TFTP and NFS and disk/storage via NFS, and how to populate the boot/flash directory.

You can give short examples how eg /etc/exports or a TFTP config file look like, but oherwise drop the RPiOS specific bits like how to install specific TFTP server (there are several different ones available). Just add links to RPiOS forum threads or wiki pages where these bits are already discussed in detail.

As for kernel ip config: in general it's recommended to use kernel ip autoconfiguration, so ip=dhcp is enough - manual configuration is only needed in rare cases.

As RPi4 doesn't suffer from many of the limitations that RPi2/3 had it's best to add the few RPi2/3 specific bits in a separate section at the end. Eg mention here that TFTP server must be on the same server as DHCP - and better link to existing docs which describe how to setup a (proxy) DHCP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants