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.

Topics - garagevibes

Pages: [1]
Developers / O2 Joggler As full MD - Testing needed
« on: March 13, 2014, 04:05:15 pm »
Hi all,

First I'm not to sure where this topic could really lie so please move if needed be,

Basically I haven't invented anything I have just pulled various things together to try and get my Joggler to PXE boot as a full MD, however I have had some issues with my core lately and I don't currently have any other MD's to test so I wonder if anyone with a Joggler wants to try these instructions out and see if they get further than me :)

Ok so where to start first the joggler uses an EFI boot rom which is a stumbling point, however someone far clever than me has created a coreboot/seabios rom replacement for this which in essence will convert your Joggler from an almost atom based pc in to a full atom based pc, I have attached a copy of this but I take no credit its from the forum its just here to help people locate it.

So here are the steps to get you to this point, you should note that you will be flashing your boot rom and wont be able to boot to the old software after this although if all goes well flashing back to the EFI boot rom is quite easy and if you have a second Joggler and you do happen to somehow completely brick one you can hot swap the boot rom from a working joggler to fix so this isn't as risky as it initially looks honest :)

so steps:
1 - Download the Joggler reflashing tool and updated openpeak firmware from this site:
2 - Follow instructions on the site to install the updated openpeak firmware.
3 - After doing this you are left with a Joggler that is up to date and that you can easily SSH to.
4 - Download the attached rom files on this post unzip and add to a newly formated FAT32 usb stick, there are 2 folders in this zip file one is a backup of the normal EFI boot rom the other is the new coreboot rom, copy the .rom file out of the coreboot folder and place on the root of the usb stick.
5 - Now place the usb stick into the Joggler and reboot.
6 - Check the DHCP address on the Joggler and SSH to the Joggler; username is joggler and password is joggler
7 - Now issue the following commands:

# cd /mnt
This will enter the USB stick
# ls
This will list the files on the stick and should show this:
Now the next two lines will flash the boot rom:
# modprobe fh
# dd if=/mnt/coreboot.rom of=/dev/fh count=1 bs=1024k
Now finally reboot:
# reboot

after reboot you should now see a different boot splash with an icon of a shark, this is now your bios.

So now you have more of a standard PC than a Joggler you should be able to flash a standard disc image now to a usb stick and the Joggler will boot it even windows seems to work sort of but we want to PXE boot so next steps:

1 - Go to and create a usb based PXE image and flash to a usb stick.
2 - Place usb stick into the joggler and connect a network cable between the joggler and your internal LMCE network.
3 - Restart joggler and you should boot in to iPXE which will configure the network card and then TFTP from the core.

Now this is as far as I have got, I then get a kernel panic at the point it seems that the initial PXE boot image passes over control to LMCE very much like an issue you would see with an incompatible network card.

Now there are 2 types of Joggler 1 has the r8168 network card the other has a r8169 network card I have the r8168 type and this known to have issues with LMCE so i followed the wiki to recreate the diskless image with the r8168 driver but without success.

As stated before though I have had issues with my core and I get the same error trying to PXE boot VMfusion on my Mac so I would be grateful if others could test this and see if they get the same results and also if anyone has any ideas of what the issue could be it would be great, I think it has something to do with drivers I just cant pin down what ones.

If after this you want to go back to the original EFI rom just place the back up .rom file in the zip attached on the root of a usb stick, place in the joggler, reboot and at the shark logo press the F7 key this will re flash the old EFI rom back and you will be back to a normal Joggler again.

Many thanks

PS seems I cant upload file attachments larger than 192KB so please download the roms from this link:

Installation issues / Issues running on 1004
« on: February 24, 2014, 08:59:38 pm »
Hi I gave 1204 a go last week but I've dropped back to 1004 for a moment till some of the issues I had get ironed out, however I have installed 1004 fine but whenever I run I get the errors below, does anyone have any ideas?

Code: [Select]
dcerouter_1039715:/home/daniel# sh /usr/pluto/bin/
Mon Feb 24 19:50:52 GMT 2014 - Logging initiatilized to /var/log/pluto/Diskless_MD_Creation_20140224_195052.log
Mon Feb 24 19:50:52 GMT 2014 - BEGIN: Target: ubuntu - lucid - i386
Mon Feb 24 19:50:52 GMT 2014 - BEGIN: Host: ubuntu - lucid - i386
Mon Feb 24 19:50:52 GMT 2014 - Creating chroot for MD creation at: /tmp/Diskless_CreateTBZ.pNbBudatP
Mon Feb 24 19:50:52 GMT 2014 - Untarring /usr/pluto/install/PlutoMD_Debootstraped.tar.bz2
Mon Feb 24 19:51:05 GMT 2014 - Preparing the diskless system
Mon Feb 24 19:51:06 GMT 2014 - Setting up /etc/sources.list for HOST_DISTRO: ubuntu
Mon Feb 24 19:51:06 GMT 2014 - Setting up SSH
Mon Feb 24 19:51:06 GMT 2014 - Setting up Foxconn NT330i compatability
Mon Feb 24 19:51:06 GMT 2014 - PreSeeding package installation preferences
Reading package lists...
Building dependency tree...
Package debconf-utils is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
E: Package debconf-utils has no installation candidate
An error (Exit code 100) occured during the last action
install of debconf-utils

Hi all,

I'm currently pulling my hair out trying to get my Acer Revo to net boot as a MD and I really hope someone can help.

I will give you a quick overview of recent changes then explain the issue as it maybe related.  :)

So I had 0810 all working fine for about a year or two but recently my motherboard on my core just died so I got a new Asus board with an AMD phoneme which unlocked to 4 cores whooho.

Unfortunately the board has an ATI graphics card which I know isn't great plus it has the annoying r8168 gigabit ethernet chip as well so not really the best but it did get 4 cores up from a 2 core chip so its worth the extra work I thought and actually it does work quite well, I install the latest repo version of LinuxMCE 0810, then run a script to blacklist and recompile the correct ethernet driver and downloaded and installed the ATI driver from AMD's site and then LinuxMCE installed with ease and as far as I can see everything works fine and as expected on the hybrid.

So the issue I have given that the new core should have been the real pain in the arse and wasn't is with my Acer Revo, which is widely regarded as supported and every other time I have needed to reinstall my core on the old motherboard has never had an issue.
However now it PXE boots fine and the core runs the or something like that, then it reboots installs the Nvidia 195 drivers, reboots again then beeps and I press Q or 1 to get to the AV wizard as I'm connected through HDMI and its great and thus far all works as expected but then when I get to the select audio connection and I press on anything other than no sound it just freezes on the wizard and I never see the screen with the speaker to adjust the volume.

I did manually run the AV wizard from the terminal to get a bit more information and it shows when I select an audio connection that Xine plays an audio file but I never hear it and I can see any errors.

Also if I do select no sound in the wizard I get past the AV wizard and all the white text shows up but after it says starting onscreen orbiter I see a flicker of a window opening and then just a black screen with an operational mouse pointer.

As a result I first thought it must have something to do with the ALSA version so I tried first to install the alsa modules but that didn't help, so then I downloaded a script to manually download and compile ALSA to 1.0.24 but this also didnt help, so then I tried to download the latest Nvida driver from there site but this also hasn't fixed the issue.

The final steps I have now taken are reinstalling the whole system first with the latest snapshot and then with the currently recommended snapshot, then one I had from 2010 and another that I found from 2009 which I knew worked back then but had issues with the sources.list obviously

All installed fine on the core/hybrid but have the same issue with the MD, its driving me mad Please Please can someone offer some suggestions, the only thing I can think of is that the ATI driver is somehow affecting things on the core and that this then moves down to the diskless MD image, if thats the case I'm happy to disable the core's graphics card and buy an Nvida one to add in but would this really help?

Many thanks and sorry its a little long winded just thought the background my help.



Installation issues / PXE Booting a MAC How to
« on: June 03, 2011, 01:06:02 pm »
Hi all,

I have been using LinuxMCE for a few years now but this is my first post so hello all.

I have had an old Mini Mac connected to my main TV for a while and find I really dont use it to much so decided it would make a great media director, of course theres the old issue of PXE booting the Mac but after a few months of searching I think I have found the answer and since I couldn't find it on here I thought I would share.

If like me you have been looking forever how to do this you will like me kick yourself with how easy it is.

First go here: h**p:// and select the output format to "ISO bootable image", the NIC to "all-drivers" and then leave the rest all blank as is.
Then select the "Get image" button to download the iso file.

Once downloaded burn the iso to a blank disk and put it into your mac, then either reboot the mac and hold the control key or alt key (if you have a standard keyboard) during boot and select the cd, or in OSX go to system pref -> startup disk -> then select the cd and reboot (this will then always boot from the cd until you press the control key as above and select the hardrive).

As the cd loads it will start a small linux distro and create a pxe enviroment and then pxe to the core as normal, once your on linuxmce you can of course eject the disk until you need to reboot.

I have tested this process many times and it works great.

I do have an issue at the moment though which some of you maybe able to help with it seems that the av wizard freezes on the audio connection option unless I select no sound and even then when Sarah should pop up i get a black screen with a mouse, I think I know the reason and its to do with the intel drivers and alsa version however when I try to download the toolchains to compile the alsa module the apt-get freezes at about 46%, I thought this maybe due to the sources list but they are identical to the ones on my core and my acer revo which compliled the new alsa drivers fine, Im tempted to do a complete restore of the system with the current snapshot anyway unless anyone has an idea what this could be.

Many thanks


Pages: [1]