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 - pigdog

Pages: [1] 2 3 ... 69
Installation issues / Re: LMCE-1404 20150308181930157 reboot loop
« on: March 27, 2015, 07:22:32 pm »

Tried 20150326121930361 with same results.


Installation issues / Re: LMCE-1404 20150308181930157 reboot loop
« on: March 27, 2015, 04:44:14 pm »

Yes, each time.  Groundhog day all over again.

Am presently downloading 1404-20150326121930361 to try out.


Installation issues / Re: LMCE-1404 20150308181930157 reboot loop
« on: March 27, 2015, 02:57:23 pm »

On initial startup - [fail]

 * Starting SMB/CIFS File and Active Directory Server

All other processes [OK].

The Nvidia driver installation begins and ends and the requires a reboot.

(With the results from previous post).


Installation issues / Re: LMCE-1404 20150308181930157 reboot loop
« on: March 27, 2015, 02:30:04 pm »

If it helps at all...

Hitting <ESC> at "fancy" Ubuntu splash show our startup processes.

So the startup launches a bunch of processes and loads the Nvidia driver.

Then you'll get the please stand by while your system is rebooted message.

Then it attemps to stop   - Restart_Myth_Backend /usr/pluto/bin/
         - LinuxMCE linuxmce
         - discovery /usr/pluto/bin/
         - Orbiter /usr/pluto/bin/
         - LMCE launch Manager /user/pluto/bin/
         - DCERouter /usr/pluto/bin/
         - XWindowsSystem /usr/pluto/bin/
         - Gamepad Radar /usr/pluto/bin/
         - NFS Radar /usr/pluto/bin/
         - Samba Radar /usr/pluto/bin/
         - Storage Status Radar /usr/pluto/bin/
         - Voicemail Monitor /usr/pluto/bin/
         - PNP MD Plugin (interactor) /usr/pluto/bin/

who [fail]

         - Dhcpd Plugin /usr/pluto/bin/

who [OK]


* Enable Wake-on-LAN /usr/pluto/bin/
Stopping Asterisk PBX: asterisk.
Stopping Network Block Device server: nbd-server.
 * Stopping internet superserver inetd
 * Stopping Postfix Mail Transport Agent postfix
Stopping radvd: No /usr/sbin/radvd found running: none killed.
 * Stopping rsync daemon rsync
Stopping xl2tpd: xl2tpd.
 * Stopping MD monitoring service mdadm --monitor
 * Stopping NFS kernel daemon
 * Unexporting directories for NFS kernel daemon...
ipsec_setup: Stopping Openswan IPsec...
ipsec_setup: stop ordered, but IPsec appears to be already stopped!
ipsec_setup: doing cleanup anyway...
waiting for pid 1880 to die
 * Stopping domain name service... bind9
 * Asking all remaining processes to terminate...
 * All processes ended within 1 seconds...
rpcbind: rpcbind terminating on signal. Restart with "rcpbind -w"
ModemManager[1686]: <info>  Caught signal, shutting down...

ModemManager[1686]: <info> ModemManager is shut down
Deactivating swap
Unmounting local filesystems
mount: /is busy
* will now restart

We go though BIOS restart and then back to GNU GRUB screen to groundhog day all over again.


Installation issues / Re: LMCE-1404 20150308181930157 reboot loop
« on: March 26, 2015, 01:18:37 am »

Just got back from work and tried again.

Doesn't matter from the GNU GRUB version 2.02~beta2-9ubuntu1 menu screen if I select *Ubuntu or Advanced options for Ubuntu.

The "fancy" Kubuntu splash appears, not the LMCE Kubuntu 14.04 splash, and the system cold reboots (BIOS splash) and loads the GNU GRUB screen again.

MD5sum's checked out on the iso's.  Something seems borked.

If you'd like me to try anything, please advise.


Installation issues / Re: LMCE-1404 20150308181930157 reboot loop
« on: March 24, 2015, 10:56:49 pm »

Well something weird is going on.

Just tried 20150221002330069 and same,same.

Time to do some scratching... head, butt, (butthead a possibility).


Installation issues / LMCE-1404 20150308181930157 reboot loop
« on: March 24, 2015, 10:36:16 pm »

I downloaded and installed this snap.   

It loads and after restart provides the Ubuntu GRUB select screen.

After selecting Ubuntu it runs (for a bit), but then loops back to Ubuntu GRUB select screen.


Installation issues / Re: CuBox-i from SolidRun
« on: March 21, 2015, 10:27:23 pm »

I will take a peek at installing ubuntu trusty on a microSD.  I should be able to shoe-horn onto a 16gig card.  If not I'll pick up a 32.

I have Android running on one mSD.  Fedora 20 on another.

I am working nights this w/e so hopefully will have some news next week.


Installation issues / Re: CuBox-i from SolidRun
« on: March 18, 2015, 02:03:19 am »

I just cut and pasted part of my notes as what I had kinda done to date.

Tftpboot and other junk not included.

This is based on the installation of the 12.04 variant of LMCE.

My notes (so far) for investigation of Cubox ARM support on LMCE.

Log in as root.

apt-get update
apt-get upgrade
apt-get dist-upgrade

Preparing to build from sources.

We need to have gcc-arm-linux-gnueabi installed.

apt-get install gcc-arm-linux-gnueabi

We also need to have u-boot-tools installed (for mkimage).

apt-get install u-boot-tools

Plus, we need to have lzop installed (for "make zImage").

apt-get install lzop

Finally, we need git installed

apt-get install git

If logged in as root when we check our directory tree...


... we have 'Desktop' and 'new-installer' as directories.

Step 1. - u-boot for cu-box with pxe patches

To build the bootloader...

git clone

Now when we check our directory tree...


... we now have 'Desktop', 'new-installer' and 'u-boot-imx6' as directories.


cd u-boot-imx6

Set up our environment variables.

export ARCH=arm
export CROSS_COMPILE=/usr/bin/arm-linux-gnueabi-

Then we build the bootloader.

make mx6_cubox-i_config


A successful build will create u-boot-* files (including u-boot-img) plus a SPL file.

The SPL file is used for the actual machine detection and initialization. 
This file must be flashed on offset 1KByte of the boot micro SD.

The  u-boot.img is the second stage bootloader.
It can be flashed at offset 42KByte from the start of the boot micro SD. 
Or it can alternatively be put as-is on the first partition of the micro SD.

The general bootloader flashing procedure is...

dd if=SPL of=/dev/sdX bs=1K seek=1

...where /dev/sdX is the location of your microSD card.

For flashing u-boot.img as raw to the micro SD -

dd if=u-boot.img of=/dev/sdX bs=1K seek=42

WARNING: Make sure you are flashing u-boot to the proper target device.  Putting the wrong device identifier could wipe your hard drive.

You can boot from the microSD at this point without booting a Linux system (only the u-boot).

Step 2. - Kernel build (with appropriate patches)

Compiling the kernel.

Change directory to /u-boot-imx6/arch/arm in order to edit the file

modify the line

CROSS_COMPILE ?= arm-linux-


CROSS_COMPILE ?= arm-linux-gnueabi-

cd back to the 'Desktop', 'new-installer' and 'u-boot-imx6' directories

The 3.10 LTS kernel is the main kernel to be used for end users and general availability.

It is based on Linaro kernel 3.10 LTS, i.MX6 Freescale patches and patches from Russell King, Jon Nettleton and various other developers.

The kernel can be built using the following commands.

git clone

Upon completion when we now check our directory tree...


... we now have 'Desktop', 'new-installer', 'u-boot-imx6' and 'linux-linaro-stable-mx6' as directories.

cd linux-linaro-stable-mx6
Set up our environment variables.

export ARCH=arm
export CROSS_COMPILE=/usr/bin/arm-linux-gnueabi-

make imx_v7_cbi_hb_defconfig

make zImage imx6q-cubox-i.dtb imx6dl-cubox-i.dtb imx6dl-hummingboard.dtb
make modules

The generated files are -


The first file is the actual kernel. The other three are device tree files loaded by the boot loader.

So from what I looked at in DisklessCreate - yeah this approach was 'different'.

Don't know if I can use "trusty image" because of the patches.

I was going to create a menuconfig for pxelinux.cfg and chose the package I wanted to install something like...

DISPLAY message
DEFAULT cubox blah blah
LABEL cubox blah blah
   kernel /where the heck my vmlinux is
   append root=/dev/nfs boot=casper netboot=nfs nfsroot=IP.OF.YOUR.SERVER:/srv/tftpboot/cubox blah blah initrd= cubox/blah blah/initrd.lz --

kinda thing.  You know. HACKABILLY.

I also need those .dtb files to support the different variants of the cubox-hummimgboard I believe.  (I don't know for sure.  Suppose to automatically load the proper .dtb depending upon hardware).

Anyway I'll poke around at this end.


Installation issues / Re: CuBox-i from SolidRun
« on: March 15, 2015, 06:56:54 pm »


I shouldn't have looked at TBZ.  My HACKABILLY approach wasn't the way to go.

I always had a concern re: CreateDiskless.  Oh well, up to my waist now!


Installation issues / Re: CuBox-i from SolidRun
« on: March 15, 2015, 12:13:03 am »

I'm at a point where I figure the way to boot the Cubox is to create a pxelinux menu in-order to chose between Pluto x86 default and Cubox ARM.

If anyone has a different approach, please advise.

I am going to look at TBZ shell to see if I'm missing something as well.

I'm up to my knees but not drowning yet!


Installation issues / Re: NAS recognized and added but no meddia addded
« on: February 12, 2015, 10:08:58 pm »

I had a whole lot of weirdness going on.

Two hard drives with Ubuntu and (awk!) Win10.  Both corrupted. 

The ASRock B75M-DGS motherboard constantly making clicking noises - like a mechanical relay being operated

I have an old 430W power supply in that system, but, there may have been an issue with an IDE to SATA power adapter.

Once swapped the clicking stopped.  I've rebuilt both drives and so far no major issues.

Still have a couple of minor issues to resolve.

Hopefully soon I can get back to pursuing the Cubox.


Installation issues / Re: NAS recognized and added but no meddia addded
« on: February 10, 2015, 04:30:09 pm »

HDD got corrupted and now boots into initramfs.

Ran diag tool from WD and HDD was reported as physically OK.

Before crash NAS volume 2 was not being unlocked and reported too many symbolic links.  Volume 1 was fine.

Will reload software and try again.


Installation issues / Re: NAS recognized and added but no meddia addded
« on: February 09, 2015, 10:35:15 pm »

So I have reloaded from scratch, did not do an update, upgrade, dist-upgrade (yet) and my media was picked up.

When all is done I will do an update, upgrade and dist-upgrade - then I will add some new media and see if it is picked up.


Installation issues / NAS recognized and added but no meddia addded
« on: February 09, 2015, 04:25:40 pm »

I have finally got the pieces together to rebuild my dev box (to try to get cu-box working - haven't managed to do ANYTHING since October/14).  I loaded on 12041002114429514, which is my bullet load, running on my main system.  I did update, upgrade, dist-upgrade.  Everything fine.  Fired up my NAS, it was discovered, added username/password.  No media discovered.  I rebooted, nothing. I tried a resync from webadmin Media Files Sync  and received the following.

sudo -u root /usr/pluto/bin/UpdateMedia -d \"/home/public/data/videos\"

21   02/09/15 10:05:02.390      lock(0x9151a8c) (>2) alarm: AlarmManager.cpp:102  <0xb7713b40>
21   02/09/15 10:05:02.390      acquired(0x9151a8c) #0 (>2) alarm AlarmManager.cpp:102  <0xb7713b40>
21   02/09/15 10:05:02.390      start cond wait AlarmManager.cpp:102 (0x9151a8c)  <0xb7713b40>
10   02/09/15 10:05:02.394      Activating Pluto Media Identifier... <0xb7715700>
10   02/09/15 10:05:02.395      Pluto Media Identifier activated. Extensions 74 <0xb7715700>
10   02/09/15 10:05:02.395      MediaState::LoadDbInfo ready to run big query <0xb7715700>
10   02/09/15 10:05:02.398      MediaState::LoadDbInfo got 1 rows <0xb7715700>
10   02/09/15 10:05:02.398      UpdateMedia::ReadDirectory /home/public/data/videos <0xb7715700>
10   02/09/15 10:05:02.399      Sync'ing db with directory... <0xb7715700>
10   02/09/15 10:05:02.399      DB sync'd with directory! <0xb7715700>
10   02/09/15 10:05:02.399      AlarmManager::~AlarmManager start 0x9151a48 <0xb7715700>
21   02/09/15 10:05:02.399      lock(0x9151a8c) (>3) alarm: AlarmManager.cpp:87  <0xb7715700>
21   02/09/15 10:05:02.399      acquired(0x9151a8c) #0 (>3) alarm AlarmManager.cpp:87  <0xb7715700>
21   02/09/15 10:05:02.399      unlock(0x9151a8c) #0 (>3) alarm: AlarmManager.cpp:87  <0xb7715700>
21   02/09/15 10:05:02.399      end cond wait AlarmManager.cpp:102 (0x9151a8c)  <0xb7713b40>
21   02/09/15 10:05:02.399      unlock(0x9151a8c) #0 (>2) alarm: AlarmManager.cpp:102  <0xb7713b40>
21   02/09/15 10:05:02.399      removed from map (0x9151a8c) #0 (>2) alarm: AlarmManager.cpp:102  was: 2 size, now 1 Rel: Y Got: Y <0xb7713b40>
21   02/09/15 10:05:02.399      removed from map (0x9151a8c) #0 (>3) alarm: AlarmManager.cpp:87  was: 1 size, now 0 Rel: Y Got: Y <0xb7715700>
10   02/09/15 10:05:02.399      AlarmManager::~AlarmManager done 0x9151a48 <0xb7715700>


When NAS was added as a Windows file share I received QT4 and QT5 download error messages when the file server software was beiing asdded and installed.


Pages: [1] 2 3 ... 69