• Content Count

  • Joined

  • Last visited

About Fourdee

  • Rank

Recent Profile Visitors

1287 profile views
  1. Igor, Thank you for opening up and allowing me to understand you, and, the way in which your project is allowed to operate. We clearly have a different level of comprehension and expected professionalism, which unfortunately, can not be met in the middle. I believe there is nothing that can be gained from further discussion. In the interest of both our projects, I will remove all ARMbian based images from the DietPi lineup. You can view the status of this in the following link: My only hope, is that you can find a higher level of solac
  2. I completely understand, as I also experience this first hand with DietPi. Its not easy doing something for nothing, especially when the joy factor which drives everything, is destroyed by those frustrations. Although we don't do kernel work, our support software titles require constant maintenance and adjustments due to changes outside of our control. Because as well know too well, Linux is not a constant, its always evolving and one line of code changed can break everything that depended on it. I envy and appreciate what you guys have achieved for those devices, and, highly
  3. Sorry you feel that way Igor. It was never our intention to take over the work you guys do with ARMbian. It is our intention, to use your ARMbian opensource build tools, which allows us to generate an initial image, then optimize and configure it for DietPi. We then release it to our end users (with full credit to ARMbian in the DietPi login banner). Without which, we would need to revert to non-ARMbian based images. If anything, DietPi is promoting the work you are doing, in a different end-user experience and format. Our efforts and skills are not in kernel devolpment, its not what
  4. @zador.blood.stained Thank you for the info, much appreciated!
  5. Hi, Apologies for bringing up an old topic. Has anyone been successful obtaining a working HDMI audio output with BPi Pro + Mainline 4.9? I tried various mixer settings, 3.5mm works fine, but not HDMI. Thanks.
  6. Thomas, If you can clearly define an issue with DietPi and/or its security, please make a git ticket and we will look into it. In the mean time, I will continue to delete all "hear say" posts with no relevant proof of your claims. It would also be worth noting, that, only your posts have ever been deleted, in the history of DietPi project.
  7. We have a system in DietPi that allows users to pre-enter their wifi details in /boot/dietpi.txt before powering on. By default, all DietPi images have all networking disabled, then this code runs after resize: Config file, located on FAT partition: Default /etc/network/interfaces: So, ARMbian could have a similar system, config /boot/armbian.txt, loaded during 1st run. I
  8. Well, that answers that question then. Thanks for info Lightweight justice for your single-board computer. Optimized | Simplified | For everyone Kernel 4.x+: Tried a few months back with various boards using ARMbian build tools. Devices wouldn't boot. Haven't tried since. If I remember correctly. Your website used to list issues when using the "vanilla kernel", reduced support and features? Put me off trying further. ondemand is wrong for Allwinner BSP kernels: One could say, Allwinner H3 is wrong . On your experience, is interactive "right" for Allwinner?
  9. Hi all, I'am looking at creating a single unified H3 DietPi image (currently using ARMbian build tools), rather than one for each board. Would allow us to support all H3 devices, reduce work load and simplify DietPi source code. Basically I need to know if its possible, and which unique files/configurations would need changing to achieve it. The end goal: The user would download the H3 image, modify it for their board (eg: copy and paste job on /boot), prior to powering on. Some questions: Is script.bin the only unique configuration across all H3 boards? Aside from any additiona
  10. Just thought i'd share. SystemD service to automatically logon main screen (tty1) as user root, during boot:
  11. Thanks Tkaiser, Would be interesting to see the results, and, if needed, work on improving those results. I still havn't found a way of physically disabling the onboard BCM wifi/bt. The best we have at the moment is module blacklists, but the chip will still be drawing power i'd assume.
  12. Thanks guys, exactly the info I was after. Yep, so uboot settings can be unique to the device, rather than just the SoC type: So in theory, if I want to use an existing image for a device, I'd need to match the device I want to target, with another device that has the same uboot configuration. Q: Does the .fex (.bin) override the uboot clocks/power regulation etc, rendering the unique uboot settings void? edit: Thanks. I'am all for getting everything little thing out of the device, including power usage . Prime example is the Odroid C1/C2. The HK images ha
  13. Thanks zador.blood.stained, We don't install cpufreq on DietPi, gov and optional max freq is applied during boot to /sys/devices/system/cpu with script. Q: Is the .fex (script.bin) file responsible for these unique min/max clocks and vcore voltages (if i remember correctly)? Q: On a default and, what situations would render this unique to the device, if any? Ah yes, i see. modules available in /etc/modules are unique to the device. It appears compiled modules are the same across all sun8i compiled images. Q: Is it safe to say ARMbia
  14. Hi all, We are now using ARMbian build tools as our 1st choice for all future DietPi SBC images. Currently, we support these devices that use ARMbian at their base: BPI Pro BPI M2+ OPI PC NanoPi Neo I'd like to increase this so we can support more boards with the same ARM SoC (eg: H3). Unfortunately, like most, i do not have access to every SBC out there. As we do further manual optimizations to the ARMbian images, after compile (eg: DietPi-RAMlog, DietPi-RAMdisk, package removals, prep for DietPi scripts etc etc), having the SBC device is essential to creating our image. I'am c
  15. Fresh installation of Armbian_5.17_Bananapipro_Debian_jessie_3.4.112.img, built today. Scan now works, but it wont connect. Tried both DHCP (times out) and STATIC, with WiFi creds set in network interfaces: root@bananapipro:~# iwconfig wlan0 wlan0 IEEE 802.11 ESSID:"" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Bit Rate:65 Mb/s Tx-Power:32 dBm Retry min limit:7 RTS thr:off Fragment thr:off Power Management:off wlan0 Link encap:Ethernet HWaddr e0:76:d0:03:54:f4 inet addr: Bcast:192.168.