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] 4 5 ... 110
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!

Developers / Re: Who can I help with the Mythtv 'install' package
« on: September 18, 2016, 11:31:57 pm »
Thanks!  As soon as I have a few minutes I'll take a look.

Installation issues / Re: no sound over hdmi
« on: September 17, 2016, 03:13:49 am »
As we've mentioned there is really no one maintaining mythtv.  Patches are welcome.  Otherwise it sounds like a mismatch in settings for xine.  You have not provided any information about your video card hardware or card id.  I'm aware of the xine config, but it is extremely variable depending on hardware.

Sent from my Nexus 5 using Tapatalk

Installation issues / Re: "PXE-E77: Bad or missing discovery server list".
« on: September 16, 2016, 02:22:08 pm »
As posde indicates there is a fix for this in the repository now.  I've tested this now with multiple PCs and PXE booting PCs and RPis should both be working.  Keep in mind that the rpi foundation considers PXE booting to be very much in beta stage.  All said it's working well here.

Developers / Re: Who can I help with the Mythtv 'install' package
« on: September 16, 2016, 03:49:57 am »

Sent from my Nexus 5 using Tapatalk

Developers / Re: Who can I help with the Mythtv 'install' package
« on: September 16, 2016, 03:42:50 am »
We don't use github.  Our repository is available at:

See the sticky in the developers forum about gaining access to it.

Developers / Re: Who can I help with the Mythtv 'install' package
« on: September 13, 2016, 01:16:31 am »
Just a comment from above about Host and DBHostname,  on the core I can understand local host as value, but on MDs it must be dcerouter ( or else on mythtv-setup one gets the recurring language screen, or the mythtv-backend refuses to start)

Ok, include that info in the ticket.  It's being set in mysql.txt to dcerouter but not currently in config.xml.  Thanks for looking into this!

Developers / Re: Who can I help with the Mythtv 'install' package
« on: September 12, 2016, 09:21:23 pm »
I can help with script changes (if required) but cannot test as I don't have anything setup to test with.  Let me see if I can respond to a couple of points:

On the CORE, everything works great..   the /etc/mythtv/config.xml file and the /etc/mythtv/mysql.txt work great.

Good to know, thanks for verifying that.

On the MD:  there are several things Ive noticed:
     1.    the user mythtv needs to have the same uid and gid as the CORE's mythtv user (because the home folder is a nfs mount from the core)

hmm, I thought that ypserv/ypclient would be taking care of this.  That may need to be looked at to see if it's working properly or not.  The MDs *should* have all the same users as the core, at the same UID/GID.  Something in NIS may not be working properly?
**EDIT: NIS only deals with additional users, not system created users it seems. 

     2.    Each MD gets a unique <Password> in the /etc/mythtv/config.xml (by default on mythtv install i am assuming)  This <Password> can stay
            what it is, but also needs to be the same as the DBPassword in the /etc/mythtv/mysql.txt file,   AND it needs to be the same password for
            the mysql user mythtv@192.168.1.xx (MD iP address).

When the pluto-mythtv-player package is installed it attempts to copy the core's config.xml and mysql.txt file, however the package is installed into a chroot and likely can't get the files initially.  We'll need to look at a way to trigger a package re-configure during firstboot of the MD or something.

     3.    On any MD, the <Host> in /etc/mythtv/config.xml  and DBHostname in /etc/mythtv/mysql.txt NEEDS to be dcerouter

That is should be as it should be a duplicate of the core's file when things work as they are currently designed.

Hope this helps.

Very much.  I would ask that you open a ticket/issue in our git system so that we can reference this and track any changes related to it.  Add the above information to the ticket please.  Check the sticky at the top of the developers section on getting access to


Installation issues / Re: media search error
« on: September 10, 2016, 10:15:09 pm »

Installation issues / Re: Denon Receiver Control over Ethernet
« on: September 10, 2016, 09:48:48 pm »
That's got it.  Thanks for checking into that posde!


Installation issues / Re: Denon Receiver Control over Ethernet
« on: September 09, 2016, 12:42:39 am »
Well, I tried adding the Pioneer kuro and I'm not getting any codes here.  Shit.

Sent from my Nexus 5 using Tapatalk

Installation issues / Re: Installation fails on ubuntu 16.04
« on: September 07, 2016, 06:01:59 pm »
1604 will be available for installation when critical bugs preventing installation are fixed.


Pages: 1 2 [3] 4 5 ... 110