Jump to content

succo

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. well, it could be that 'm with ubuntu, or maybe that i don't need anything more than plain ext4, samba and nfs, but i have _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 21.02.2 Groovy with Linux 5.10.16-rockchip64 No end-user support: work in progress & unsupported (groovy) userspace! System load: 2% Up time: 9 days 13:21 Memory usage: 34% of 3.71G Zram usage: 6% of 1.85G IP: 192.168.1.150 CPU temp: 44°C Usage of /: 56% of 15G [ 0 security updates available, 26 updates total: apt upgrade ] Last check: 2021-02-27 00:00 [ General system configuration (beta): armbian-config ] and it has been stable for more than 3 weeks before last reboot, which was required after an update
  2. succo

    audio output

    it's Armbian 21.02.0-trunk.54 Groovy with Linux 5.9.16-rockchip64 right now i used a daily build with sources.list for devel, so I am running hirsute (rolling) and no audio device is created with usb-c hdmi dongle inserted btw, sorry for the late reply, but i'm an armbian forum beginner, so can't post more than once a day
  3. succo

    audio output

    ok, for now i solved the errors using the snd_dummy driver, but, afaik, audio over usb-c works for the nanopi (which is rk3399 as the helios) so maybe it could work here too
  4. succo

    audio output

    is there any way to send audio through displayport? i installed kodi, just as a database updater, but it fills the log with errors related to the audio system, and i see that aplay doesn't show any audio device, so another question is, is there any way to emulate an audio device? thanks
  5. well, it worked perfectly, even if it lacks hardware acceleration (i tried a 1080p mkv and it was slow as hell, don't know the cpu level but it was completely unusable, but i guess sd stuff will play ok, and i really didn't need kodi to output anything, just to update the db) i know NAS is not intended for this use, but if we can play music on a vacuum cleaner... btw, the fan trouble was depending on a too tight screw, disassembled it and found the culprit right now, webmin works for the remote administration part, apache works (even if i really don't need it yet), mariadb does its job, i put in 5 disks (for a total of 31T right now) and the helios runs stable, the only disappointment has been that i can't insert my FANTEC MR-25D Rack for 2 2,5 drives as the screw holes don't fit with the guides, so i can only fix the far screws and it doesn't stay straight enough to make contacts with the sata port, and iven if it would i couldn't access the 2,5 slots because ot the plastic guide in front of the slots
  6. ok, so my flaming new helios finally arrived (after Christmas, what a pity) and, after spending some time assembling it (it's not the easiest thing in the world, expecially if you want to attach the mainboard BEFORE connecting all the cables, as specified within the instructions) I started configuring it. As i don't like the easy way (I'd have bought something else, if i would have) I went for a daily build with Groovy (i don't need OMV for my purpose and am quite accostumed to the ubuntu way), and the first thing i did was to make it a rolling release, putting devel in the place of groovy in sources.list, so that now i run hirsute (even if with a groovy userspace, as armbian has no hirsute userspace yet). Here comes a question... could it be possible to have a devel channel, replicating the 'latest' channel, so that once hirsute overcomes groovy i don't have to edit armbian.list to reflect the change? OK, back to the testing... i come from many years with a dns-340l from d-link with fun_plug, not exactly the most user friendly situation and not exactly the top on the hardware side, so i can say i know how to make things work, so i migrated some config files, moved the disks and guess what? my shares came back to life in not more than a couple of hours, and now with a mariadb server (instead of an old mysql 4.something), and i can say i see the difference. I use kodi with a central db and (maybe the db server, maybe the ram, maybe who knows) everything is faster now... before every database read was a pity, now it's quite instantaneous. BTW, i had an usb-c to hdmi cable hanging around and it seems to be working (at least, after enabling the correct dtbo,, it shows the login on screen) so i tried to build kodi (i reached 80° C while building, is that normal? that's why i said 'flaming' in the start) and now have to try it as a service... i used to have an headless kodi installed on a rpi4 to update my library, but i guess i could have an instance running directly on the NAS, headless or not (i'd like to try how is kodi rendered on the helios) Now, another question... until now I saw only the upper fan spin (and you can see i reached quite high temperatures), what could have gone wrong? Anyway, the Helios64 is a real beast, it didn't freeze on me yet and is really over my expectations, thanks Helios team
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines