after a long download it stopped at each 100MB, got it flashed to a SD card and it works,
has some gnome tools and has some benchmarks tools
I have the new Debian on another card it works well too
Anyone managed to get NTFS HDD mounted on this image yet? The moment I connect an NTFS HDD the screen goes blank and unresponsive. Need to power cycle at that point. Also launching apps like Synaptic or the browser seems to put the FS into read-only mode after which most other operations seem to fail. Anything that I am missing here?
@shades_aus
In response to your query - "> Anyone have ideas on how to get the HDD activity light working again for this image?"
Have a look in /sys/classes/leds
There should be a couple of symlinks;
firefly:blue:power
firefly:yellow:user
Note: Don't get too hung up on the file names of those symlinks. The led color in the filename is inconsequential.
'cd' to the one named 'firefly:yellow:user'
ls -l output should show the following list of files; firefly@renegade:/sys/class/leds/firefly:yellow:user$ ls -l total 0 -rw-r--r-- 1 root root 4096 Jun 21 07:48 brightness lrwxrwxrwx 1 root root 0 Jun 21 07:48 device -> ../../../leds -r--r--r-- 1 root root 4096 Jun 21 07:48 max_brightness drwxr-xr-x 2 root root 0 Jun 21 07:48 power lrwxrwxrwx 1 root root 0 Jun 21 07:48 subsystem -> ../../../../../class/leds -rw-r--r-- 1 root root 4096 Jun 21 16:25 trigger -rw-r--r-- 1 root root 4096 Jun 21 07:48 uevent
Have a look at the trigger file (eg. cat trigger)
You should see a list of the names of valid triggers that can be used. The one surrounded by square brackets is the current trigger (probably [none] at the moment).
Now echo "xxxxx" > trigger Where xxxxx is one of those trigger names you saw when you cat'd the file.
In my case, since I'm using eMMC (rather than SD card), I did echo "mmc1" > trigger
And voila, now the led flickers whenever there is a file operation that causes access of the eMMC drive.
I can't find any config.text file however, there is a binary rk3328-roc-cc.dtb in /boot that has links to the LED links. I know of no way to edit this currently if this is even correct.
Ok. I have no idea how to make it run at boot however, I edited /etc/rc.local and added in :
cd /sys/class/leds/firefly:yellow:user
echo "mmc0" > trigger
cd /
That at least makes it work after booting, just not during the load stages itelf.
Comments
where did they post it? Didn't find it on their news site or ftp folder?
Its in the download ubuntu popup from http://en.t-firefly.com/doc/download/index/id/34.html
There is also a new debian image too.
after a long download it stopped at each 100MB, got it flashed to a SD card and it works,
has some gnome tools and has some benchmarks tools
I have the new Debian on another card it works well too
That is one slow server, be ready to pause and resume the download 15 times in 2 hours.
Anyone interested in creating a Torrent for it? I cant download anything from those links, it cuts out at ~300 megs for any of the files.
I put it on google drive
https://drive.google.com/file/d/18vuBiR8_bD2pbk5vG38CDkYZu2NHNF-h/view?usp=sharing
let me know if link doesn't work
Can someone tell me how to flash it to emmc?
EDIT: Nevermind, somehow shorting emmc data and grnd didn't put my device into maskrom mode so I had to be a little more creative.
how do you connect to wifi in this OS?
@jeepthing - Much appreciated. Server kept 503-ing throughout the weekend. Was able to download from your Google drive in less than a minute!
Awesome! Thanks! Let me know if you hit a bandwidth limit and i can share the file on my drive.
Anyone have ideas on how to get the HDD activity light working again for this image?
Anyone managed to get NTFS HDD mounted on this image yet? The moment I connect an NTFS HDD the screen goes blank and unresponsive. Need to power cycle at that point. Also launching apps like Synaptic or the browser seems to put the FS into read-only mode after which most other operations seem to fail. Anything that I am missing here?
my WD usb drive works run thru a powered usb 3.0 hub
@shades_aus
In response to your query - "> Anyone have ideas on how to get the HDD activity light working again for this image?"
Have a look in /sys/classes/leds
There should be a couple of symlinks;
Note: Don't get too hung up on the file names of those symlinks. The led color in the filename is inconsequential.
'cd' to the one named 'firefly:yellow:user'
ls -l output should show the following list of files;
firefly@renegade:/sys/class/leds/firefly:yellow:user$ ls -ltotal 0-rw-r--r-- 1 root root 4096 Jun 21 07:48 brightnesslrwxrwxrwx 1 root root 0 Jun 21 07:48 device -> ../../../leds-r--r--r-- 1 root root 4096 Jun 21 07:48 max_brightnessdrwxr-xr-x 2 root root 0 Jun 21 07:48 powerlrwxrwxrwx 1 root root 0 Jun 21 07:48 subsystem -> ../../../../../class/leds-rw-r--r-- 1 root root 4096 Jun 21 16:25 trigger-rw-r--r-- 1 root root 4096 Jun 21 07:48 ueventHave a look at the trigger file (eg. cat trigger)
You should see a list of the names of valid triggers that can be used. The one surrounded by square brackets is the current trigger (probably [none] at the moment).
Now
echo "xxxxx" > triggerWhere xxxxx is one of those trigger names you saw when you cat'd the file.In my case, since I'm using eMMC (rather than SD card), I did
echo "mmc1" > triggerAnd voila, now the led flickers whenever there is a file operation that causes access of the eMMC drive.
Thanks pdf !!
I shall have a look!
:-) Works like a charm. Thank you. Is there a way to make it stick on re-boot? It seems to default back to none.
I can't find any config.text file however, there is a binary rk3328-roc-cc.dtb in /boot that has links to the LED links. I know of no way to edit this currently if this is even correct.
Ok. I have no idea how to make it run at boot however, I edited /etc/rc.local and added in :
cd /sys/class/leds/firefly:yellow:user
echo "mmc0" > trigger
cd /
That at least makes it work after booting, just not during the load stages itelf.