dogshome

Members
  • Content Count

    32
  • Joined

  • Last visited

About dogshome

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. scdc set scrambling refers to HDMI 2.0. My new monitor is HDMI 2.0. The desktop obviously understands it, although not reporting full resolution and and sticking at 60Hz. my monitor is only 30Hz at 4K. It's the text based boot screen that can't handle it. My (almost vintage) Orange Plus sees it correctly when running on Armbian, as does a 6 month old version on the NanoPi, so someone knows how this works. Thank you @piter75 So a 'lost setting' or 'feature' for development or porting from another build Mr Igor and friends please?
  2. @piter75 Hi, yes it boots this way. lots of test as things starting up, error country setting failed -2, but more drivers started OK, then it pauses with error: drm:drm_scdc_set_scrambling failed to read tmds config, error 6 and 2 similar errors. Logged in on terminal as normal startup. Desktop appears! Subsequent reboot fails until HMDMI unplugged, then it boots to desktop. I have a new 4K monitor with HDMI V2.0. That is something that has changed on my setup Can you spill the beans????
  3. PS My somewhat older Orange Pi Plus works fine on the latest firmware!
  4. V2 firmware also doesn't work (despite only difference being RAM type DDR3 to DDR4). I'm not sure its getting a far as to start a UART. It's dead Jim!
  5. Yes for Arduino. What PC software would i use?
  6. Hi all, This has confused me! I have an old copy Armbian_20.02.7_Nanopim4_buster_current_5.4.28_desktop.7z which works fine. Any SD cards I put it on using Balena Etcher works. Any of the latest versions simply won't boot. The only difference appears to be the XZ file format. I extracted one of the later ones using 7Zip and then Etcher to flash and as expected it mad no difference at all. Has something been done to the V1 firmware from the V2 that doesn't work or firmwares containing the wrong naming etc? Help!
  7. Ditto. Friendly seem to have permanently broken the video acceleration even though Chromium reports it as there. They have also added lots of junk. Armbian with this script is my preference.
  8. I think that is the idea, but I don't have that hat. Armbian usually transfers very well. I have the SATA Hat. I'm running Friendly OS right now which doesn't transfer 100% and I'm booting from EMMC and using SSD for data e.g. Thunderbird. The boot time from EMMC vs SSD SATA is negligible and running apps seems the same.
  9. RE:Accelerated graphics not working. I've found that updating Friendly OS using the Linux tools loses both the setting and the acceleration. Simply putting the setting back on doesn't fix it. If you stick to the Friendly releases, it's fine. Apart from when they mangle a release and have to fix it in a hurry when the Beta testers (us) complain.
  10. Not sure exactly what tearing you are asking about? Does it show black and white bars moving across the screen, yes. Are the bars all vertical without sections moving independently, yes. Is it like a piece of paper in front of you, no. The edges have a couple pixels blur. Is it the same on my i7 laptop and external graphics card, don't know yet :-) Sorry for the subjective answer!
  11. I switched away from armbian as it only supported graphics acceleration in certain packages. Friendly OS is tweaked and chromium for example is supported. I never tried open gl though and someone more knowledgeable than me will know for sure exactly what armbian supports today.
  12. Hi Axel, watching this thread. Armbian has been pretty bulletproof on all SBCs I've tried. Interested to see how this turns out.