2014-02-12, 22:21
does anyone have bootproblems with openelec installed on SSD too or does it concern only USB 3.0 Stick?
(2014-02-12, 21:14)micoba Wrote: There's a first reaction from Intel regarding the new update...
https://communities.intel.com/thread/48842
(2014-02-12, 22:21)Aquila Wrote: does anyone have bootproblems with openelec installed on SSD too or does it concern only USB 3.0 Stick?
(2014-02-12, 23:01)micoba Wrote: @frarev
The Akasa looks huge on the photos - now, that's bad advertising! First I found it ugly... But now that I took a second look, and learnt, that it's only 150 mm looking from the front, I will consider buying it!
(2014-02-12, 17:03)bustamelon Wrote:(2014-02-12, 13:28)chongwho Wrote: Hello all,
Some great info in these forums. Thanks for everything so far.
I am looking to SSH in to my Openelec NUC to create the remote command, however putty is saying "network error: connection refused".
I have researched a bit and found that I needed to create the ssh_enable blank file in configfiles, which I have done, but I am still unable to SSH.
This is stopping me from getting the remote working (and also the colors issue form post 1 of the thread)
Any help would be much appreciated
Not to overlook the obvious, but did you enable the SSH server in the OpenElec settings?
This depends on what version you are running. I don't think there is any need for the blank file in v2+... although I could be wrong about that. I have never had to do that. Just tick the box in the GUI settings menu.
(2014-02-13, 04:06)chongwho Wrote:(2014-02-12, 17:03)bustamelon Wrote:(2014-02-12, 13:28)chongwho Wrote: Hello all,
Some great info in these forums. Thanks for everything so far.
I am looking to SSH in to my Openelec NUC to create the remote command, however putty is saying "network error: connection refused".
I have researched a bit and found that I needed to create the ssh_enable blank file in configfiles, which I have done, but I am still unable to SSH.
This is stopping me from getting the remote working (and also the colors issue form post 1 of the thread)
Any help would be much appreciated
Not to overlook the obvious, but did you enable the SSH server in the OpenElec settings?
This depends on what version you are running. I don't think there is any need for the blank file in v2+... although I could be wrong about that. I have never had to do that. Just tick the box in the GUI settings menu.
Wow. Don't I feel stupid. SSH was turned off in OpenElec settings.
(2014-02-12, 23:30)bukhlef Wrote: Ok this is noobish i know, but i really don't know how to execute these two commands, i already connected to my NUC via SSH but what shall i do to execute these commands after i pasted them in SSH window >.> i even tried ExtraPutty still same thing nothing happens
cd /storage/.config
touch autostart.sh
chmod +x autostart.sh
nano autostart.sh
# IR fix
modprobe -r nuvoton-cir
echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
modprobe nuvoton-cir
(2014-02-12, 22:50)frarev Wrote:(2014-02-12, 21:14)micoba Wrote: There's a first reaction from Intel regarding the new update...
https://communities.intel.com/thread/48842
Not good :-( They consider Linux is not an official supported OS for our NUC.
(2014-02-12, 20:46)Crssi Wrote: Then I could only speculate that your remote does not send the right power on sequence.
If you know anyone with MCE/RC6 compliant remote to try with it?
(2014-02-13, 11:06)OllieB Wrote:(2014-02-12, 20:46)Crssi Wrote: Then I could only speculate that your remote does not send the right power on sequence.
If you know anyone with MCE/RC6 compliant remote to try with it?
Last night I played with some of the BIOS settings and guess what....I have managed to brick my NUC completely
The power button does not work anymore (green light on, but no response), wake on lan does not work and neither does the remote. A BIOS recovery (USB stick and jumper) does not work because the power button does not function so I cannot start the NUC anymore.
Have e-mailed the vendor whether they want to replace the unit, or if they insist on trying to or send for repairs, I will try to remove the motherboard from the case (apparently not that easy) to disconnect/connect the CMOS battery.
Strange that the box is designed in such a way that the power button stops functioning when the BIOS is corrupted.