Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - phenigma

Pages: [1] 2 3 ... 108
I'm aware of that but the rumors agree already flying of potential consumer devices built the same.  Time will tell.  ;)

Sent from my Nexus 5 using Tapatalk


Looks like neat stuff that could interface with lmce.  Time will tell.

Users / Re: Keep Web page in forefront while watching a movie
« on: October 03, 2016, 01:33:20 am »
This is the definitive answer:

Code needs to be added.  The other option is to disable the screen saver completely.

Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 25, 2016, 07:43:02 pm »
Interesting, you've provided pretty much all the info I need.  I'll look into it a bit more from this end. 

I'm not experiencing any media playback issues really, besides files that are incompatible... But that is actually very very few.  I've also not experienced slow nfs speeds like you are describing.  If you figure anything out please share.

Sent from my Nexus 5 using Tapatalk

Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 25, 2016, 05:18:09 pm »
The Mac warning is normal.  1404 i386 should have the updates in the repo.  Others have the updated file.  'apt-cache policy lmce-bootscripts'

Sent from my Nexus 5 using Tapatalk

Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 24, 2016, 04:48:12 pm »
good morning!

this is /etc/dhcp/dhcpd.conf

and this is the output of tcpdump:

Code: [Select]
dcerouter_1047514:/home/linuxmce# tcpdump -i eth1 -vv | grep "tftp"
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0" > [no cksum]  35 RRQ "71638953/start.elf" octet tsize 0 > [no cksum]  29 RRQ "autoboot.txt" octet tsize 0 > [no cksum]  27 RRQ "config.txt" octet tsize 0 > [no cksum]  29 RRQ "recovery.elf" octet tsize 0 > [no cksum]  26 RRQ "start.elf" octet tsize 0 > [no cksum]  26 RRQ "fixup.dat" octet tsize 0
          file "/tftpboot/pxelinux.0"

sorry, need to figure out howto use pastebinit with tcpdump...
dhcpd.conf doesn't contain the magic text.  Please upgrade your packages and re-run

Sent from my Nexus 5 using Tapatalk

Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 23, 2016, 11:41:45 pm »
It's now working for others that were having similar problems.  You aren't using the command I gave for tcpdump so I cannot compare what you are providing to what I know it should look like.  Installing the default netboot package will put all the files in the correct location within tftpboot.

Just to cover another base can you pastebin the file /etc/dhcp/dhcpd.conf.


Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 23, 2016, 08:39:50 pm »
I've put up a new default netboot image for the rpis.  This is working on my RPi3 without an sdcard again.  I highly recommend leaving the sdcard in as the RPi3 SOC has some bugs that make netbooting very unreliable without the sdcard.  So grab the two files from the wiki page (default image and sdcard image) and try again with these fresh files.

* phenigma crosses fingers.

Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 22, 2016, 11:50:33 pm »
Well, good news is that I am able to re-create the issue you are having with one of my RPi3s.  I'm booting without an sdcard and it looks like a conflict between the gpu's bootcode.bin on the version of start.elf in the default package.  This is my theory atm.  When I use my sdcard and an RPi2 it is working.  I'll try to figure out what is conflicting.

If I boot with my sdcard from the wiki, the RPi3 boots fully.  Don't remove the card.

Use this on the core to track tftpbooting (change eth1 to whatever your internal nic is):  tcpdump -i eth1 -vv | grep "tftp"

A full boot first boot will look like this:


Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 22, 2016, 02:15:47 pm »
I wonder if you have an old diskless image for the rpi.  I added the bits to bring in the experimental kernel just a week ago or so.  You might try creating a new diskless image.

Edit: it's the default image that's not booting.  I know I suggested not doing it but perhaps try re-downloading the default image and re-install it.

Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 22, 2016, 02:02:59 pm »
Well, it looks like the RPi is network booting but stopping after tftp of fixup.dat.  Can you confirm that you see the square rainbow box on your RPi screen a few moments after turning it on (this indicates that start.elf transferred)?  I'm at a little bit of a loss at the moment as to why it's stopping.


Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 22, 2016, 01:31:01 am »
If it still doesn't boot we need to check the dhcp config.  I'm thinking that even with the upgraded packages the dhcp config may not have been rewritten to provide the proper magic text to the rpi to permit it to network boot.

In that case you can run '/usr/pluto/bin/' to rewrite the dhcp config, then run 'service isc-dhcp-server restart'.

Let me know what works out and I can make any required changes to package installs.

Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 21, 2016, 09:15:12 pm »
I would definitely try with my sdcard, in case there is some version mismatch between your bootcode.bin and start.elf in the default network boot directory.  Your files all look good.

The link should be removed, it is not created properly as it doesn't contain the rpi serial number.

Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 21, 2016, 05:28:45 pm »
While I and one other have been successful I've heard of a couple issues more recently.  I've heard of some issues with the diskless filesystem being created but the device itself should be creating.

Prepared the raspberry for network/usb booting (it is showing 0x3020000a).
I have not used the sdcard mentioned in the wiki. I used the way it was described there:
Should be the same result?

I assume you're booting without an sdcard.  The RPi foundation has found a couple of bugs in that method.  Try booting with an sdcard that has just bootcode.bin on it (or use the new one I just posted on the wiki, it'll set the OTP bit, rewrite the sdcard contents and reboot automatically).

Installed the default netboot kernel package.

Changed the TARGET_TYPE. (Do i need to change it back after i have created the tarball?)

No, it simply needs to be set for the target type you want the image created for prior to running the script.  You could create a tarball for both i386 and rpi, for example.

The raspberry didn`t get recognized. So i even tried to add the template manually, providing a mac address and an ip address.

it won`t boot.

I really, really, really do not recommend adding the DT manually, it will not contain the serial number of the RPi, which is a requirement to netboot.  The automatic process will pass the serial number to the core when it is discovered.

I made a tcpdump on the core/hybrid and all i could find is this:

Code: [Select]
13:48:52.061106 IP moon142.49154 > 29 RRQ "autoboot.txt" octet tsize 0
13:48:53.061145 IP moon142.49155 > 27 RRQ "config.txt" octet tsize 0
13:48:54.061306 IP moon142.49156 > 29 RRQ "recovery.elf" octet tsize 0
13:48:55.061453 IP moon142.49157 > 26 RRQ "start.elf" octet tsize 0
13:48:56.061562 IP moon142.49158 > 26 RRQ "fixup.dat" octet tsize 0

That doesn't seem like it's passing the files.  Can you run 'ls -lah /tftpboot/ | pastebinit' so I can see if all of the tftp files are setup properly.

I don`t know what i can do. Maybe reinstall everything? Did the netboot kernel package changed since last week? Is it a good idea to reinstall that?

Shouldn't have to re-install.  The default kernel package has not changed since last week, the only change is that I've provided an sdcard to setup the OTP bit and rewrite the card automatically.

I would really like to have a noiseless raspberry as md.
And i really would be very thankfull for any idea/suggestion/hint!

The rpi is pretty nice as a lightweight MD, I've been running 3 permanent and 2 testing units for many years now.

I'll be checking into the issues that you, and others, have been reporting over the next few days.  Thanks for testing!

Users / 'Diskless' Raspberry Pis are out in the wild!
« on: September 21, 2016, 01:43:15 am »
Hey everyone!  I wanted to pass on some of the recent work I've been doing in relation to the Raspberry Pis.

It's been a long slog bringing the system to the RPi line of systems.  In the original LMCE release for the RPi I had spent 2 months hacking u-boot to provide a really robust 'PXE like' boot process for the RPi in LMCE.  It was intense and required understanding and programing u-boot for low-level memory access to pass boot parameters (ATAGS) properly to the linux kernel.  When the RPi2 was released the hardware had changed significantly and the broadcom SOC was upgraded to a multi-core cpu and armv7 rather than the older armv6 architecture.  Due to the architecture changes in the SOC u-boot failed to work with the new Raspberries.  So I revived the old, old concept of disked Media Directors for the RPi2.  This worked well as long as the power didn't go out (which meant you would have to re-write the sdcard and let the system re-install all the software packages again.)  With the RPi foundation's recent announcement of netboot capability ( we have a new way to boot all Raspberry Pi B's (1, 2 and 3).

Head on over to to read about how to setup a network booting RPi Media Director.

Keep in mind that the RPi foundation (and myself) still consider this to be very experimental.

Have fun!

Pages: [1] 2 3 ... 108