• Content Count

  • Joined

  • Last visited

About iamwithstupid

  • Rank

Recent Profile Visitors

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

  1. Original Article: https://www.bleepingcomputer.com/news/security/linux-kernel-prior-to-508-vulnerable-to-remote-code-execution/ Reddit: https://www.reddit.com/r/linux/comments/bo6n2j/linux_kernel_prior_to_508_vulnerable_to_remote/ What does it mean for Armbian? I was just going to build a custom image for btrfs rootfs since I failed to get my SBCs with U-Boot to boot with it with an existing install for some reason even after moving /boot to an seperate etx4 partition ... OT: I really hate U-Boot and it's documentation, especially on the EspressoBin.
  2. After frying 2 RasPi Zeros in my first venture to the RasPi foundation-world I'll gladly pay the small premium for an SBC that is properly designed to not kill itself with 2x MicroUSB-Ports that have no shortage protection, or any kind of power-protection, linking directly to the SoC in USB-Host-Mode ... it's like they designed the Pi Zero to kill itself OOB completely ignoring how flawky and non-standardized (Micro)-USB is for powering anything. The price isn't so bad when I look at the Nanopi Duo2 on the other hand.
  3. Just in case you're wondering the v5 revision supports USB Power Control with its internal Hubs - meaning you can turn off/on your external HDD if you want to use it for backups as well (I can only confirm that the USB3 port is working together with an external Seagate Expansion Desktop 8TB (3,5'), not sure about USB2 or other devices). https://github.com/mvp/uhubctl/issues/140
  4. I'd say if anything the evolution of WiFi should tell us that bigger != better and more power != better reception and longer support-time != better wifi. I've experimented with that topic A LOT with many different devices and routers - expensive and cheap ones. Almost all RTL8811au and RTL8812au dongles just work well (there are obviously some black sheeps that overheat, and some that have a random MAC-Adresses assigned, but they're in a minority and can be dealed with) - even if the drivers have hiccups and are all over the place. The biggest issue is a lack of official support (especially regarding upstream support) requiring all kind of user-patches - who would wonder. I found the driver-variant from aircrack-ng to be the most stable (I think that's the one Hardkernel also uses): https://github.com/aircrack-ng/rtl8812au. Realtek is at it again, telling us their own drivers to be a code-mess rewriting them ... supplying ... tadaaaa ... nothing as an replacement in the meanwhile ... https://github.com/torvalds/linux/tree/master/drivers/net/wireless/realtek/rtlwifi A year later ... we're still not there. Oh well! At least the RTL8812ae PCIe variant is already supported now. Hopefully it will get upstream support soon (tm). Btw. If you're seeking small, inexpensive 5GHZ AC-WAPs (or Routers) on the other hand I can only recommend the Xiaomi Wifi 3G 2018 (with GBe, not 2017!) with Padavan Firmware ... They're worth their money twofold over every other expensive Consumer-Routers I've owned before (Several Asus ACXXAU, TP-Link, Netgear Variants ...). The thing is they don't even offer MU-MIMO, but that's fine - the bottlenecks for a lot of the consumer routers above will be their horrendus power-design, airflow and software. They're overcramped with components that increase the heat and decrease performance, lifetime and reliability. If you really need MU-MIMO then get something like an UniFi UAP-AC-PRO (usually for a flat with 100 feets that's simply a waste of money). I'd say give it a few months / years and we might have upstream support (hopefully). ----- TLDR: RTL8811au and RTL8812au are the choice to go for SBCs if you need Wireless nowadays. You'll still benefit from 2 Antennas without MU-MIMO because one is being used to send and one to recieve. A single antenna can just do one thing at once. 2x MU-MIMO only means 2 users can simultaniously send/recieve on 2 Antennas at once.
  5. Now that would make some sense. I for sure hope so that the NEO3 will be an headless server like the original one ... The NEO4 is surely a nifty looking device especially in that form factor - but I'm torn apart what I should think about it. Additional parts = additional consumption (ok you can often disable it) = additional failure-possibilities = additional cost you can't avoid ... I'm a friend of devices tailored for specific purposes (e.g. Odroid HC1/2 or the NEO1/2). That HDMI Port could seem like an attempt to drive towards KIOSK / Mediaplayer ... but the Rockchip support for HW-Decoding so far is rudemimental when compared for example to the s905 driven Odroid C2 (even tought its still residing in their crappy Amlogic Kernel and not Mainline yet), not even speaking about the RasPi when it comes to Kiosk ... there are some things that are ultra hard to catch up and that's a mature software platform (including drivers and firmware, speaking about the VPU of the RasPi). That said Rockchip SOCs are for sure the future when looking at Mainline Kernel development-support from Rockchip compared to what Amlogic or AllWinner does (H6 I call you).
  6. Meh, am I the only one a little bit worried simply because they're calling it NEO4 (like trying to make use of its fame)? I'd have prefered if they've stayed true to the initial purpose of the NEO - an headless server. Now we have another hybrid doing everything and nothing. A little bit HDMI, a little bit of Wifi, two additional USB-Ports ... all a lot more factors that can fail (and increase cost). With the price of the NEO2 rising and the NEO supposedly getting shelved out soon then this looks a bit meh. I know that we have the NEO Duo(2) now but yea ... NEO1/2 was such a nice package because it had everything right from the go, including a case. Wouldn't that be more like a NEO Plus 32456262+ whatever version we're at now ?
  7. I'd say one could simplfy that all and recommend good power supply manufacturers like Meanwell and Sunny from the start which provide datasheets for their powersupplies (for example here) and properly messure their performances, efficiency and reliability. Also a simple hint that you should optimally run a power-supply at only up to 80% of their max range to ensure that they work properly (super simplification, but you know ... safe margins work best with starters) @tkaiser maybe a recommendation here (not only for Barrel-Plug connectors, but also for powering via Headers) like this could save you guys also a lot of headaches regarding power supply questions ? That said - bottomline - don't use USB-Powersupplies like mentioned in the thread above. You're just asking for troubles - especially those kind of detachable ones where you can use another USB-Cable. If you really want an recommendation I'd look at original ones from phone manufacturers like Oneplus or Xiaomi (certainly NOT Samsung, with their ultra crappy power supplies) ...
  8. Bad news, I contacted them via Mail and it seems like this was the last batch sold (at least that's what support told me). The next one will be most likely another product Why oh why can't this be sold regulary ??? I mean I could even live with preorder and wait a few months until produced - but this is almost like a guranteed death (imagine one of the Dev-Units getting destroyed -> Sajonara development*). *ok that's a bit overdramatized, but yea ... when there's no supply development will stall as soon as enough of the units are dead. I don't think anyone ordered 10+ on backorder just in case ... ???
  9. Oh, I do! I'm even eating Bierstangerl while reading your post trying to grasp up some straws of knowdlege (maybe some of them will stick). Just registered because I had to add that ... have been reading your posts for some months now. Haven't flashed armbian yet tough, hench why I didn't feel the need to register yet. But oh, well, now I'll just do both ... ---- Edit: So I've tried the DietPi and the Armbian Nightly build and the idle and load temps are up to 20° higher on DietPi even when I switch the governor / frequencies in DietPi (they're correctly applied). That is for my NanoPi Neo2 - DietPi 4.14.y kernel idle after about 10 hours in the stock 3D print case with heatsink attached has an idle temp of about 60° - compared to armbian nightly with 4.18.y kernel - 40°. Both running pi-hole only so far, all updates applied. Same config.