markjeronimus

Had another encounter with the ssh problem after burning a year-old image that worked for 100% sure. This is a 'cleaned' image, with bash history and logs purged before ripping. I thought of comparing the 'good' & 'bad' SD card. Found *unattended* upgrade logs that didn't exist before, which happened around 6am when I was asleep. Apparently systemd upgraded and broke the stuff: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580 (search Failed to validate path /var/run/sshd: Bad file descriptor)

I ran updates, it indeed fixed by sshd at boot, but I don't understand how it broke in the first place. It was always working and without provocation it stopped working (I didn't update). If this happened on my OPi Zero (has no display outputs) instead of my OPi One, it would have bricked. And of course the update broke other stuff and my 800x480 display stopped working. Time to inspect the fex-bin files. [edit] somehow scripts.bin got completely replaced by one that looks like its for another board. One thing I noticed is that instead of the OPi One's 19 GPIOs it lists 88 GPIOs.

I think 'charger adapter' means wall wart or just 'adapter' in some regions. The vocabulary shifts because we use them for charging more than powering stuff, which used to be the other way around before the 2005's. For USB chargers there's also the issue of counterfeit chargers. Ken Shirriff did a thorough review of two seemingly identical chargers, one from China: http://www.righto.com/2014/05/a-look-inside-ipad-chargers-pricey.html Never had an issue with audible switching noise, in small or big PSUs. I've only heard laptops and motherboards 'whizz'. Some chargers give a nice smooth signal, others give a dirty signal full of HF spikes. Depending on your application this might make a difference. If you're regulating the voltage some way after the power plug (like most one-board PCs do), it's generally fine. I think it's hard to tell which you'll get unless have them tested with an oscilloscope (or happen to find such a review online). MeanWell is a good brand. Dunno about the DX one. A Li-ion charger I once bought from DX suddenly shorted after a year of normal use and blew it's (resistor-type) fuse with a small light show. Others still work. I think it's hit-or-miss.

I had a TI-83 even before my very first laptop, which makes it the first mobile programmable device I've owned. And I remember in those days I longed for a laptop for a long time, ever since my dad brought home an industrial 286 vga color laptop for a weekend.

Are there any plans to add support for the MCP7940 real-time clock? It's much cheaper than the DS1307 and mostly compatible. The biggest difference is Reg0b7 which is "Clock-Halt" in the 1307 but "STart" in the 7940. The 7940 also has some extra register bits like OSCEN which are default 0 in the 1307. I tried naively enabling the rtc-ds1307 module and it didn't work. An actual DS1307 chip worked immediately (just hot-plugging the break-out boards while executing "hwclock -rf /dev/rtc1"). The actual error I get is: "Timed out while waiting for the time to change", "The Hardware Clock registers contain values that are either invalid (e.g. 50th day of the month) or beyond the range we can handle (e.g. Year 2095)". I tried setting the time to a known good value and got just "Timed out while waiting for the time to change".

Confirmed that ADS7846-X11-daemon is working on OPI ONE for exactly the display mentioned (which has the TSC2046, which is just "a next-generation version to the ADS7846" according to the data sheet).

Bought a new OPi One and it works instantly. On all my LCD screens (Adafruit, Waveshare, Chinese)... HDMI port was fubar. Topic can be closed.

Bump, because we're really struggling at my company because it's practically decided long ago that we're going to use an Orange PI in our OEM product and now find out that it doesn't want to talk with any LCD screen we tried.

I have a 5" 800x480 TFP401 display which the current armbian can't drive, and I have no idea how to fix that. My EDID is identical to his. I'm a total armbian noob and half linux noob and have no idea where to start or what all the used terms mean (u-boot, dpms, ...) or they come with random patches or links to github changesets that I have no idea what to begin with. All I know is how to compile Igor's kernel, change existing patches in his repo, and burn it (as image, not u-boot) to an SD card, all because there is a nice tutorial for it. When people start talking about anything else I have no idea what to do with that information. I tried to modify the patch starting with 0026_ and edited video_timing[] with the parameters I got from EDID, but this doesn't work. I suspect I also have to edit video_timing[] but don't have enough information. (WereCatf's question about this was never answered). I've already plowed through these resources without results (or with more questions than results, see my first rant above) https://forum.armbian.com/index.php?/topic/752-tutorial-h3disp-change-display-settings-on-h3-devices/&page=2 https://forum.armbian.com/index.php?/topic/2874-adding-display-manager-in-armbian-and-attaching-hdmi-monitor/ https://github.com/igorpecovnik/lib/issues/594 https://github.com/igorpecovnik/lib/issues/443 https://forum.armbian.com/index.php?/topic/3671-adafruit-tfp401-hdmidvi-converter-doesnt-scale-screen800x480/