Re: Fwd: Re: arm64 images to boot raspberry pi's
Hi folks,
Seems I was able to debug this.
The problem was related to adjustments to the settings of isc-dhcp (ldap). The following settings worked for me. I have added the default settings which are the commented lines. The qemu arm64 server is connected using a network bridge and runs on 10.0.2.10.
81 cn=intern,cn=dhcp,cn=tjener,ou=servers,ou=systems,dc=skole,dc=skolelinux,dc=no
cn: intern
objectClass: top
objectClass: dhcpSharedNetwork
dhcpOption: broadcast-address 10.255.255.255
dhcpOption: domain-name "intern"
dhcpOption: domain-name-servers 10.0.2.2
dhcpOption: netbios-name-servers tjener
dhcpOption: netbios-node-type 8
dhcpOption: ntp-servers ntp
#dhcpOption: root-path "/opt/ltsp/i386"
dhcpOption: root-path "/srv/ltsp/raspios"
dhcpOption: routers gateway
dhcpOption: smtp-server postoffice
dhcpOption: subnet-mask 255.0.0.0
dhcpOption: wpad-url "http://wpad/wpad.dat";
dhcpStatements: allow booting
dhcpStatements: allow bootp
dhcpStatements: allow unknown-clients
dhcpStatements: authoritative
dhcpStatements: default-lease-time 1800
#dhcpStatements: filename "/var/lib/tftpboot/pxelinux.0"
dhcpStatements: filename "cmdline.txt"
dhcpStatements: max-lease-time 3600
#dhcpStatements: next-server tjener
dhcpStatements: next-server 10.0.2.10
Kind regards,
Roman
> On 12/22/2023 10:59 AM GMT roman.meier@gismap.ch wrote:
>
>
> Hi folks,
>
> I was able to make my rpi4 boot for the first time today.
>
> Anyway, I'm getting the following output, which is rather gibberish to me unfortunately.
>
> Any ideas what is happening?
>
> [ 124.894512] VFS: Unable to mount root fs via NFS.
> [ 124.910683] Kernel panic - not syncing: Requested init /usr/share/ltsp/client/inft/init failed (error -2).
> [ 124.910789] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 6.1.0-rpi7-rpi/v8 #1 Debian 1:6.1,63-1+rpt1
> [ 124.910873] Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT)
> [ 124.910929] Call trace:
> [ 124.910959] dump_backtrace.part.0+0xec/Ox100
> [ 124.911919] show_stack+0x20/0x30
> [ 124.911060] dump_stack_lvl+0x88/0xb4
> [ 124.911141] dump_stack+0x18/0x34
> [ 124.91115Z] panic+Ox1a0/0x370
> [ 124.911196] kernel_init+Oxec/Ox140
> [ 124,911242] ret_from_fork+Ox10/0x20
> [ 124.911290] SMP: stopping secondary CPUs
> [ 124.911338] Kernel Offset: Ox115a000000 from Oxffffffc008000000
> [ 124.911392] PHYS_OFFSET: 0x0
> [ 124.911426] CPU features: 0xB0000,2013c080,0000421b
> [ 124.911476] Memory Limit: none
> [ 124.9115163 ---[ end Kernel panic - not syncing: Requested init /usr/share/ltsp/client/init/init failed (error -2). ]---
>
> Kind regards,
> Roman
>
> > ---------- Original Message ----------
> > From: roman.meier@gismap.ch
> > To: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
> > Cc: Petter Reinholdtsen <pere@hungry.com>, debian-edu@lists.debian.org
> > Date: 12/14/2023 1:30 PM GMT
> > Subject: Re: arm64 images to boot raspberry pi's
> >
> >
> > Hi Mike,
> >
> > I was able to add the arm64 LTSP server in a qemu-arm64 VM and also created the raspberry pi client image.
> >
> > I basically followed the instructions on ltsp.org to do so.
> >
> > The challenge is now to adjust the configuration of Debian Edu and qemu-arm64 VM.
> >
> > Currently the original one on Debian Edu is working just fine and serving images to all i386 devices, both diskless and thin client.
> >
> > The new arm64-ltsp server is used to serve diskless images for the rpi4 but is still untested since adjustments to the configuration are needed.
> >
> > Is there a way to run both ltsp servers in parallel on the same subnet?
> >
> > Do I have to run each on its specific subnet, e.g. by adding a third network card?
> >
> > What adjustments in the configuration are needed to be able to switch from one ltsp server to the other.
> >
> > Kind regards,
> > Roman
> >
> > > On 12/04/2023 9:01 PM GMT Mike Gabriel <mike.gabriel@das-netzwerkteam.de> wrote:
> > >
> > >
> > > Hi Roman,
> > >
> > > On Mo 04 Dez 2023 11:53:46 CET, roman.meier wrote:
> > >
> > > > Hi Petter!
> > > >
> > > > Thanks for the link!
> > > >
> > > > I may not have been clear enough. Sorry for that.
> > > >
> > > > I want to build an image for arm64 to be able to run the raspberry
> > > > pi's as ltsp clients. Since newer raspberry pi's are bootnet capable
> > > > and raspberry os is based on debian I thought there might be a good
> > > > chance for this to work out just fine.
> > > >
> > > > Kind regards,
> > > > Roman
> > >
> > > We don't have a cross-build approach for LTSP images, yet. What you could do:
> > >
> > > * install an arm64 LTSP server in a qemu-arm64 VM and create your LTSP
> > > client image in there
> > > * same on a Rasberry Pi
> > > * provide a patch to debian-edu-ltsp-install so that
> > > qemu-debootstrap gets used
> > > to create that image (see:
> > > https://github.com/faiproject/fai/blob/master/bin/fai-make-nfsroot#L277)
> > >
> > > Greets,
> > > Mike
> > > --
> > >
> > > DAS-NETZWERKTEAM
> > > c\o Technik- und Ökologiezentrum Eckernförde
> > > Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
> > > mobile: +49 (1520) 1976 148
> > > landline: +49 (4351) 850 8940
> > >
> > > GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
> > > mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
Reply to: