Recent Posts

Pages: 1 ... 8 9 [10]
91
Users / Re: IMPORTANT NOTICE: 1204 debs from svn version 29240
« Last post by mkbrown69 on August 16, 2014, 04:21:38 pm »
Pos,

Any particular things we should be watching for?  The referenced commit was changes to GenDevices and committing Radu's JSON plugin, but the knock-on effects are not as obvious.  Is the area of concern around new dependencies being installed, or changes to existing installed packages/services?

Thanks!

/Mike
92
Users / Re: IMPORTANT NOTICE: 1204 debs from svn version 29240
« Last post by posde on August 16, 2014, 06:43:00 am »
The updated debs are in the repo.
93
Users / IMPORTANT NOTICE: 1204 debs from svn version 29240
« Last post by posde on August 15, 2014, 11:46:16 pm »
There has been a change in a central header file. This change effects all binary packages. The next set of upgrades will contain a lot of files, and you can expect some crazy postinst madness. Beware of when you do the upgrade.
94
Users / Re: What Android app to use
« Last post by posde on August 15, 2014, 06:07:46 pm »
golgoj4,

sometimes people need a push. Sometimes they need more. Eventually people will go over the initial hurdle and figure out that QML is no rocket science, and the results are very fulfilling.
95
Users / Re: thinking about new av receiver
« Last post by acald on August 15, 2014, 05:38:33 pm »
Just a side point toward the original post.

there are a few out there now that will handle multiple hdmi out with audio to match. it just depends on how much you want to spend.  The onkyo 838 has two video zones and a third audio zone.

If you want wired whole house audio inexpensively and relatively easy to install, the channel vision a-bus system works well to give you audio in each room hanging off one of the zones on the receiver or a stereo output from linuxmce.  then you have a local volume control in each room.  you can't control the volume with the orbiters but it is very simple for just background music or jamming cleaning music (WAF)
96
Users / Re: What Android app to use
« Last post by golgoj4 on August 15, 2014, 05:03:23 pm »
but possy, we've established nobody can be bothered to learn qml. It not like I engineered a new orbiter framework that make the ui dead simple to edit or anything...

-tired guy
97
Installation issues / Re: Fibaro Dimmer Module - FGD-211 - Dianemo
« Last post by mardibloke on August 15, 2014, 03:13:11 pm »
Now trying with an MK LRC14 remote....

Getting same issue, that switch does not function as expected once device added to z-wave network

Reset all zwave network,  and have added devices back in.

Anyone played with Fibaro and Dianemo/Linuxmce?
98
Developers / Re: O2 Joggler As full MD - Testing needed
« Last post by garagevibes on August 15, 2014, 02:59:09 pm »
Thanks Coley,

Sorry for the delays Ive just recently had a baby so thats taken most of my time at the moment.

I have tried to do it under chroot but I end up with a few errors as I need to download the kernel source patch it and then compile it and finally install it but it doesn't seem like it likes compiling over a chroot environment, I dont really know where next to go I would be so grateful if someone with more Linux knowledge could help, So if you have a joggler that you wouldn't mind sparing and fancy a challenge the guide to getting to where I am now is as so:

1 - Download the Joggler reflashing tool and updated openpeak firmware from this site:
http://birdslikewires.co.uk
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 following rom files from here http://www.tardistracker.com/roms.zip  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:
 coreboot.rom
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.

8. now we need to flash our EEPROM so we need a tool to do that and we need DOS to run it so first download a usb bootable freedos imaged from here: http://ftp.chtaube.eu/pub/FreeDOS/bootable-usb/FreeDOS-1.1-memstick-2-256M.img.bz2 and thne download the realtek EEPROM flash tool from here: http://www.biosrepair.com/bios/PG8168.rar.

9. now dd over the dos image to a memory stick (must be at least 256mb).

10. now mount your memory stick and extract the EEprom programing tool to the stick so you can access it once freedos is booted on the joggler.

11. browse to the extracted EEprom programming tool directory on the memory stick and find 3 .cfg files named like this "8168.CFG" each one is for a different version of the  network card to be safe I edited all of them so open each one in a text editor and then at the top of the file find the line "node id=" and edit this to whatever mac address you want, I would recommend just offsetting the last few digits and then save each amended .cfg file.
 
12. now attach a small usb hub to the usb port of your joggler and attached a keyboard and the memory stick you have just been using and apply power.

13. follow the options on screen to boot yourself in to freeDOS and browse to the EEprom programming tool folder.

14. now type the following and press enter to flash "PG8169 / W".

15. now type PG8169 / R to read the network card and check all is written correctly.

16. now power down the joggler.

17 - Go to www.rom-o-matic.com and create a usb based PXE image and flash to a usb stick.
18 - Place usb stick into the joggler and connect a network cable between the joggler and your internal LMCE network.
19 - power on the joggler and you should boot in to iPXE which will configure the network card and then TFTP from the core using your new mac address.

20. that should be it you should shortly see the announced ourselves to the router messaged and the Media Director should start to be created, once done your get a message saying rebooting but the joggler wont reboot just pull the power and turn it on again, you should now boot in to LMCE.

21. your now as far as me you should after a bit of loading be presented with errors relating to the graphics drivers this is where I need your help.

if you want to read more on the EEprom flashing tool use google to translate teh following site: http://www.biosrepair.com/bios/pg8168.htm.

Hope someone can follow this and possibly offer some assistance, Many thanks.
99
Users / Re: thinking about new av receiver
« Last post by Esperanto on August 15, 2014, 12:46:15 pm »
I can't see that working to be honest. But even if it could be made to work the only advantage I can see is that all the signals are transmitted down a single cable. It seems a lot of complexity for no real gain.

Personally I am even happy with a fixed volume on the device and relative software volumes. To me it seems like a huge gain; one utp cable is everywhere (and for people who do not care about wifi disadvantages they even don't need one at all) and pulling tons of cables and possibly introducing additional (sound) hardware and diminished quality (you probably know the requirements for audio cables when used on longer distances) seems like a lot of trouble if it can be done with a bit of software. Of course that first needs to be made ;-). To bad I don't have an IP receiver otherwise I could test it a bit.
100
Users / Re: zwave network lockups/delays
« Last post by sambuca on August 15, 2014, 09:27:35 am »
The delay are usually caused by two things - network problems or a device that does not respond to a command (firmware bug or incomplete OpenZWave configuration for that device).

Heal network will run for a long time if you have many devices, which it looks like you have, so that would be expected. I don't know how long, as I have never tried, and I don't have the same number of devices either. If it does not stop, I would reboot.

I would recommend using heal node instead, as this runs much faster, on just the nodes that are having problems.

br,
sambuca
Pages: 1 ... 8 9 [10]