Jump to content

TRS-80

Moderators
  • Posts

    760
  • Joined

  • Last visited

Reputation Activity

  1. Like
    TRS-80 reacted to AB-Stromer in Armbian 22.08 booting from emmc   
    I see this has been solved but maybe it is helpful for others if I share my experience of the last days....

    - had Manjaro KDE first and then later Manjaro Gnome running on my PBP, wanted to change desktop due to bad performance with Gnome and somewhat weird booting behaviour

    - ran into a lot, really lot of trouble with these U-Boot hassle (u-boot, idbloader, trust) and repeatedly not working, at last not even booting and needed Reset directly on the the board

    - was so close to kick the PBP into the trash bin

    - but then wanted to give Armbian a chance 

    - downloaded the version for PBP, version current, with Cinnamon. Unpacked, flashed to a SD card (with dd, no etcher ..), inserted into PBP, start: success!! System on SD booted at first step, ran into initial config, set up wifi: amazing!

    - after half an hour enjoying this rescue of my PBP, I wanted to try to flash onto the emmc...

    - after quickly finding out, that - other than the armbian doc tells - it's not via "armbian-install" on the command line, but via "armbian-config" in the menu. Chose "System on eMMC, Boot from eMMC"option. Started, it worked through and

    - voila! Booting and running from emmc on first shot!!

    - So easy can life be! I am really happy and thankful to Armbian, I am an Armbian fan now    😀
  2. Like
    TRS-80 reacted to willmore in dedicated subforums for boards   
    Igor, yes, I think the issue is the 'how to communicate this better' problem.  I understand your situation and I appreciate all of your work.  Let me add my perspective and the motivation that lead me to ask my question.
     
    In this thread we see that there is a desire to have a working Linux distro for the Opi Zero 3.  Armbian is a great starting point--plain Debian would work as well, but Armbian has some SBC specific customizations that make it more appropriate--so that's what people tend to use.  Someone pointed out there was a mostly working version available.  They and others have been working for months to try to improve it.  I think all of this is a simple distillation of facts and it's in dispute.
     
    Where there seems to be some issue is motivations.  I don't know the person who made the original port--"leeboby" on github.  I don't know what their long term intention is.  Maybe they are interested in their port becoming official and taking over an official Armbian maintainer role.  Maybe it's just a 'fire and forget' effort they did for some reason.  I don't know.  But the people here would clearly like to move towards some kind of more official board support under the Armbian umbrella.
     
    To that end, the question was asked if there could be a board specific sub-forum created for this clearly unsupported board so that conversations about an unsupported board wouldn't 1) pollute the general unsupported board forum 2) make it clear that it was unsupported (to manage peoples expectations) 3) make it easier for people to find information on the effort to get this board supported by Armbian.  Having a sub-forum would help provide a sense of community and help develop interest in the effort.  *with hope* a maintainer would be attracted to or developed by this community.  As you point out, this is a completely volunteer effort.  I see people in this thread (before the split) who are showing interest in doing volunteer work.  I though I reasonably could expect a community manager to encourage the development of a community--in this case by creating a sub-forum for the board under the unmaintained board/sun-xi forum.

    So, the question I though was being asked is "can this effort find a space to work?"  What you heard was "support this board!"  Your reply was "we aren't going to support that board without a maintainer".  What I heard was "we have no interest in assisting in your effort to support this board".  So, let me ask a better question now that I hope we all have a better shared understanding of the context of the question.

    Is there a place in these forums for efforts to create support for currently unsupported boards to work?  It would need to be such that it's very clear to anyone participating that *the board is not supported and might never be supported by Armbian and that it's simply a community effort to try to reach that goal*.  I hope that addresses your concerns with people trying to abuse Armbian for support of other peoples ports.

    If the answer is no, that's fine, this is your forum and it's up to you to decide how you wish it to be used.  I simply wanted the proper question to be asked so that we all knew what was being asked.
     
    I just hope there's a way to collect community base interest and effort and channel it into something that makes Armbian better.  Thank you for all of your work and specifically the time you've taken to address this question of mine.
  3. Like
    TRS-80 reacted to Carmella Benton in Big thank you to the Armbian developers / "success story"   
    Hi
     
    I had bought a NanoPi R4S with the goal of installing IPfire.
    Unfortunately that was too complicated for me https://wiki.ipfire.org/hardware/arm/friendlyelec/nanopi-r4s
     
    I had now installed Armbian and NextCloud and I am very satisfied. In about 10 hours I had "my own cloud". Therefore a very warm and big thank you to the Armbian developers.
    Only thanks to the Armbian, I can look over the Raspberry horizon.
     
    I wish you a very pleasant week
    Best regards
  4. Like
    TRS-80 reacted to Dantes in media players not playing files over smb, is ffmpeg compiled without networking support?   
    Yay! I have it working
     
    But I'm not an expert in compiling so ymmv
    Feel free to comment or point out any mistakes
     
    # when libshaderc-dev is installed the build succeeds, but has a run-time failure
    sudo apt remove \ libshaderc-dev  
    # install compiling tools
    sudo apt install \ autogen automake cmake libtool meson pkg-config  
    # install development libraries
    sudo apt install \ libalsaplayer-dev libaom-dev libarchive-dev libass-dev libavcodec-dev libavfilter-dev \ libcaca-dev libd3dadapter9-mesa-dev libegl1-mesa-dev libfdk-aac-dev libfontconfig-dev \ libfreetype-dev libfribidi-dev libharfbuzz-dev libjack-dev libjpeg-dev libmp3lame-dev \ libmujs-dev libopenal-dev libopus-dev libpipewire-0.3-dev libplacebo-dev libsdl2-dev \ libsixel-dev libsoxr-dev libunwind-dev libva-dev libvdpau-dev libvkd3d-dev libvorbis-dev \ libvpx-dev libx264-dev libx265-dev libxpresent-dev libxxhash-dev libzimg-dev  
    # clone mpv build script repository
    git clone https://github.com/mpv-player/mpv-build  
    # configure ffmpeg options by creating a file called mpv-build/ffmpeg_options with content:
    --enable-static
    --disable-shared
    --enable-gpl
    --enable-libaom
    --enable-libfdk-aac
    --enable-libfribidi
    --enable-libmp3lame
    --enable-libopus
    --enable-libsmbclient
    --enable-libsoxr
    --enable-libvorbis
    --enable-libvpx
    --enable-libx264
    --enable-libx265
    --enable-nonfree
    --enable-version3  
    # configure mpv options by creating a file called mpv-build/mpv_options with content:
    -Dlibmpv=true  
    # start building
    cd mpv-build ./rebuild -j$(nproc)
    # strip executable
    cp -p mpv/build/mpv /tmp/mpv strip --strip-unneeded /tmp/mpv touch -r mpv/build/mpv /tmp/mpv  
    # test mpv
    /tmp/mpv smb://myserver/myshare/myfile.mkv  
    Yay!
     
  5. Like
    TRS-80 got a reaction from Tearran in Video : How to install OMV on Armbian Buster and set up a SMB share with it   
    I could be wrong, but I would suspect that the armbian-config script should actually install it.  But maybe it's broken?
     
    So, if anyone does figure it out, please do submit a patch!
  6. Like
    TRS-80 got a reaction from freezr in Armbian Devuan Based?   
    That's not the problem, the problem is the extra workload in modifying (and then maintaining) whatever parts of Armbian to support the 2 different init systems (as c0rnelius already went into some detail about).
     
    And we barely have the resources to do what we do already...
     
    Having said that, if it is something you feel strongly enough about, have at it.  But as c0rnelius pointed out, you would probably have your work cut out for you.
  7. Like
    TRS-80 reacted to NicoD in Video : How to build your own Armbian images   
    Hi all.
    I made a new video on how to build Armbian images.
    These days you can use your ARM64 SBC to do this.

    For Windows users there's WSL2 you can use. Here my video about that.

    Greetings, NicoD
  8. Like
    TRS-80 got a reaction from Werner in Armbian crashing when trying to compile code?   
    Personally I like Mean Well, they are decent brand who tend to deliver the advertised voltage (which is a whole another problem with no-name supplies, not just in SBC world but also PC and others) and last a good long while.  And pretty affordable, usually.
     
    Lately I have even been switching to DIN rail mounted power supplies for my SBCs (and other devices, even monitors, as I had too many power bricks piling up around my desktop/workbench area).
  9. Like
    TRS-80 reacted to greenknight in Popular Intrusion Detection Systems for Linux?   
    I recommend looking at Snort and Zeek. Most IDSs are just a rip off of Snort especially the commercially available ones. Zeek is kinda a packet analyzer but I have seen cool things done with it to make and IDS.
  10. Like
    TRS-80 reacted to gene1934 in bpi-m5 cinamon contains core dump in the xz, hdmi screen goes away when gui starts monitor goes off, stays off   
    There was a time, 45 years ago when I was carving code for an rca 1802 with nothing but the rca programmers manual and a hex editor in a cosmac super elf, when I would have been in hog heaven at the prospect of such an offer But now I'm 88 and have mechanical things in my heart to keep my diabetic ticker running & keeping me going.  So the info traded would likely be from you to me, which doesn't pay your net bills However, there one law no one can break, TANSTAAFL. And I don't do business with paypal since their delays in approving an ebay purchase 20 years ago cost the owner of the tv station I was at, playing consulting engineer ar the time, about $50,000  in lost revenue, Rig your donation page to take my mastercard and you will see a donation as soon as I discover I can use one of my cards to pay w/o having to move it thru paypal.
     
    In the meantime Igor, take care and stay well.
    Cheers, <gheskett@shentel.net>
  11. Like
    TRS-80 reacted to TijuanaKez in Anyone here have a stable Helios64 running OMV6?   
    Interesting that yours doesn't freeze up on Segmentation fault etc.
    I also have a suspicion that the amount and kind of drives installed as this has an effect on power drawer and possibly integrity of the 12V and 5V rails.
    Grounds for the suspicion:
    Suggestion to raise VDD to 0.95V to improve stability as done with other Rockhip RK3399 boards Preventing the higher CPU frequencies makes it more stable. High CPU freqs are more demanding on power. The fact they shipped the unit with big electrolytic capacitors soldered to the end of wires on the Sata loom. Seems like a way to help smooth power rails without having to redesign the board. Various other hints here on the subject of VRMs, cpu governor settings, ramp time, latency etc in relation to the  RK3399. https://forum.odroid.com/viewtopic.php?t=30303
    https://github.com/u-boot/u-boot/commit/f210cbc1f3d4f84baa595d83933369b4d6a529ea
    https://github.com/u-boot/u-boot/commit/5a6d960b222203e60ab57e19b3eb7b41c24b564b
    https://wiki.t-firefly.com/en/Firefly-RK3399/driver_pwm.html
    http://patchwork.ozlabs.org/project/uboot/patch/20191128061433.1952869-2-anarsoul@gmail.com/
     
    So, @mrjpaxton interested to know how many drives you have installed, and what type (5400, 7200, or SSD)?
    Also a possibility is running fewer tasks on the unit means the CPU has less demand and the governor may by rarely, if at all, trying to switch into the higher problematic frequencies.
     
    update: my unit still hasn't frozen again since last post with the 4000-14000 omdemand so things are looking pretty stable. so far so good anyway.
     
     
     
     
     
     
  12. Like
    TRS-80 reacted to TijuanaKez in Anyone here have a stable Helios64 running OMV6?   
    @mrjpaxtonI defintely bulit the unit corretly. As I said in the post, I had a %100 stable unit on OMV5 with the image listed in the wiki for years.
    Paying attention to this forum though, it's clear stability issues have been long running for many users and from what I can gather, the root problem is to do with cpu and power management. Quite a complex subject, something that PC overclockers would know more about than me.
    @snakekick thanks for chiming in too. Good info.
    Collecting info as I find it, it does seem like preventing the CPU from hitting the high end is the best way to go (contrary to other posts here).
    Still running on-demand 400-14000 now on @bunducafe's info, and it's more or less stable. As it's only happened once so far since changing to that setting, I can't even confirm it wasn't some other insult to the system
     
  13. Like
    TRS-80 reacted to c0rnelius in Armbian Devuan Based?   
    Although this is doable. It would be a fairly large undertaking.  Any services and custom services currently used, would need a sysvinit equivalent. Then there is the question, would this also need to be integrated into armbian-config?  Probably, yes. Would all features in armbian-config even be supported in Devuan? I seriously doubt it. Also depending on how debs specific to Armbian are currently put together and the depends they may or may not have, those would also need to be modified.
     
    Plus it would need to be extensively tested. I have found some scripts I run that are linked to services sometimes need modification when using them on Devuan. 
     
    For a lot of boards though, on a basic level. It could be done.
  14. Like
    TRS-80 reacted to ct100 in Increased idle power consumption when booting from eMMC vs microSD   
    I found the reason this happens. Its not the eMMC itself, the boot from eMMC or booting from FAT vs EXT4. It's the much faster system boot speed from eMMC and the network configuration that leads to this bug.
     
    The device that consumes the additional idle power is the Realtek RTL8125 2.5GbE NIC when left in an bugged unmanaged/unconfigured/off state.
     
    When using stock Armbian with Network-Manager it seems to depend on the image, software distribution and the system boot speed with how often the Realtek NIC gets into this bugged state. Properly configuring the NIC in Network-Manager prevents this from happening.
     
     
    When using Armbian Bullseye with OpenMediaVault installed with the OMVExtras InstallScript this can be reproduced 100%. The InstallScript (without using the option -n to skip network configuration) removes Network-Manager and lets systemd-networkd and OpenMediaVault/Netplan manage the network.
     
    Since the MAC of the Realtek RTL8125 2.5GbE NIC is not fixed and changes every boot systemd-networkd with the policy "MACAddressPolicy=persistent" (default in /usr/lib/systemd/network/99-default.link) automatically adds a persistent MAC address to the Adapter. At the same time OpenMediaVault creates netplan files that assign network configuration based on this added MAC address.
     
    This leads to a race condition in systemd-networkd. If systemd-networkd adds the persistent MAC to the adapter before it tries to assign the configuration matched to this persistent MAC everything works as expected. When the system boots faster systemd-networkd tries to match the configuration to a MAC that is not added yet to the adapter and that leaves the adapter off, unmanaged and bugged.
     
    (In these code parts eth0 = GMAC & Realtek RTL8211F 1GbE and Realtek RTL8125 2.5GbE NIC = enP3p49s0)
     
    Random MAC adresses:
    Aug 28 09:53:57 nanopi-r6s kernel: r8125 0003:31:00.0 (unnamed net_device) (uninitialized): Invalid ether addr 00:00:00:00:00:00 Aug 28 09:53:57 nanopi-r6s kernel: r8125 0003:31:00.0 (unnamed net_device) (uninitialized): Random ether addr 4e:54:94:b5:ad:c7  
    OMV Netplan file (matching with mac!):
    root@nanopi-r6s:~# cat /etc/netplan/20-openmediavault-enP3p49s0.yaml network: ethernets: enP3p49s0: match: macaddress: de:d1:aa:55:c9:bf accept-ra: true dhcp4: yes dhcp4-overrides: use-dns: true use-domains: true dhcp6: yes dhcp6-overrides: use-dns: true use-domains: true  
    Netplan auto generated systemd-networkd .network:
    root@nanopi-r6s:~# cat /run/systemd/network/10-netplan-enP3p49s0.network [Match] MACAddress=de:d1:aa:55:c9:bf [Network] DHCP=yes LinkLocalAddressing=ipv6 IPv6AcceptRA=yes [DHCP] RouteMetric=100 UseMTU=true UseDomains=true  
    When booting from slow microSD status of enP3p49s0 is ok:
    root@nanopi-r6s:~# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 ether routable configured 3 enP3p49s0 ether no-carrier configuring 3 links listed. root@nanopi-r6s:~# networkctl status enP3p49s0 ● 3: enP3p49s0 Link File: /usr/lib/systemd/network/99-default.link Network File: /run/systemd/network/10-netplan-enP3p49s0.network Type: ether State: no-carrier (configuring) Path: platform-fe180000.pcie-pci-0003:31:00.0 Driver: r8125 Vendor: Realtek Semiconductor Co., Ltd. Model: RTL8125 2.5GbE Controller HW Address: de:d1:aa:55:c9:bf HW Permanent Address: 4e:54:94:b5:ad:c7 MTU: 1500 (min: 68, max: 9194) QDisc: mq IPv6 Address Generation Mode: eui64 Queue Length (Tx/Rx): 4/4 Auto negotiation: yes Speed: n/a Port: tp DHCP6 Client DUID: DUID-EN/Vendor:0000ab1166a0671791d79f890000  
    When booting from much faster eMMC enP3p49s0 is left in a bugged state:
    root@nanopi-r6s:~# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 ether routable configured 3 enP3p49s0 ether off unmanaged 3 links listed. root@nanopi-r6s:~# networkctl status enP3p49s0 ● 3: enP3p49s0 Link File: /usr/lib/systemd/network/99-default.link Network File: n/a Type: ether State: off (unmanaged) Path: platform-fe180000.pcie-pci-0003:31:00.0 Driver: r8125 Vendor: Realtek Semiconductor Co., Ltd. Model: RTL8125 2.5GbE Controller HW Address: de:d1:aa:55:c9:bf HW Permanent Address: 92:f6:18:f3:59:af MTU: 1500 (min: 68, max: 9194) QDisc: noop IPv6 Address Generation Mode: eui64 Queue Length (Tx/Rx): 4/4 Auto negotiation: yes Speed: n/a Port: tp  
    The fix is to install OpenMediaVault without re configuring the network with InstallScript option -n. That keeps Network-Manger and doesn't add the ethernet adapters to the OMV database.
     
    Another option is to remove Network-Manager and also remove the matching by MAC address from OMV netplan files by editing "/srv/salt/omv/deploy/systemd-networkd/netplan/files/ethernet.j2" and deleting:
    match: macaddress: {{ mac_address }} After saving and applying the new network configuration in OMV webgui the MAC address matching is gone and adapters get only matched by name.
     
  15. Like
    TRS-80 reacted to yam1 in Armbian Desktop Wallpaper Contest   
    I am submitting my **original artwork** for the Armbian Wallpaper Contest.
    **Artwork Details:**

    - **Title:**Penguin Planets in Armbian Universe
    - **Description:**I wrote a little program to create this image. The background, the penguins and the icons can be customized by making small changes to this program. A wall paper generator web page could be made available for this purpose as well.  To encourage vendor support for this project, the penguins (icon, penguin size and location) can be customized per vendor needs. Linux penguins as planets is my original idea (I did not find or copy anything from google). Since the image can be easily recomputed, they are not important any more only the idea remains. The background image is found by searching google images for royalty free universe images. Another background image can be substituted easily if need be.

    I hereby confirm and certify that this artwork is an original piece created solely by me. By submitting this artwork to the Armbian Wallpaper Contest, I agree to release it under the [Creative Commons Zero (CC0) license](https://creativecommons.org/publicdomain/zero/1.0/legalcode) (CC0 1.0).
     

     
     
     

  16. Like
    TRS-80 reacted to fabiobassa in CSC Armbian for RK322x TV box boards   
    dear friends
    i remark that we continue to give help to someone that is not willing to listen and perhaps THIS IS FRUSTRATING and not the fact that the box is not booting

    After discovered that IF ONLY HE had followed all the instructions that very kindly the users of this 3ad suggested instead of trying other magic combinations, and after we  already said thet we need uart logs and so now I  would like remember  we said to him to stay on legacy kenel that is 4.4.xxx

    And guess !!

    He flahsed Armbian_22.11.1_Rk322x-box_jammy_current_5.15.80_xfce_desktop.img.xz
    in other words a 5.15.80 kernel

    Do we need other words?

     
  17. Like
    TRS-80 reacted to occams razor in CSC Armbian for RK322x TV box boards   
    @n3o  The members trying to help you are highly experienced. The important point here is for you not to treat their specific instructions as merely "suggestions" after which you go off and do your own thing.   That is where the frustration lies. 
     
    Based on the energy other users and you have spent on this, I would just buy some other TV box or SBC that is already known to run Armbian without any issues instead of trying to resurrect an old tired piece of hardware.   Unless you are really short on cash,  this is what I would do.  However, if you really are so short on cash that you cannot afford another $20USD on something else, then I believe your priorities are all wrong.
     
    I have an H20 RK3228A tv box that is in transit that has some documented booting issues with Armbian.  In a way, I am happy to see how this whole episode has progressed.  I'm happy because now I know what NOT to do.
  18. Like
    TRS-80 reacted to dalyer in s905x question   
    In my experience (T95X/AmLogic s905x) it's best to re-flash the stock Android using the AmLogic USB Burning Tool first before trying to boot Armbian from SD card.
    You need to explain in more detail exactly what you're doing, how you're preparing the SD card, how you are trying to boot it, what if any output/errors you get on trying to boot it etc.
  19. Like
    TRS-80 reacted to NicoD in Tips for choosing my first cheap TV box?   
    Why not buy an Armbian supported SBC? Most TV-Boxes are crap. Overheating and low-quality. For better quality you also pay a lot more. So then why not buy a good SBC?

    RK3399 ain't that expensive and has great IO. RK3588 is high end so cost more, but it's future proof.
    OrangePi5+ should be best value. I don't have it, so can't say much about it. 
    NanoPi R6S/R6C isn't that expensive. The C has NVMe and USB3, and very fast CPU.
     
    If you want to use full sized HDD's then look at the Odroid HC4. It has the S905X3. As powerful as RPi4(when not OC) and 2 SATA for full sized HDDs. But no USB3 or other IO. It does have HDMI.
     
    RK3568 is also a SoC that has great IO and not too expensive. Not sure if there are Armbian supported boards with it.
    RK3566 less IO but still better than any RPi.

    I only had one ok TV-Box from a bunch. The Mecool KM6 with S905X4, but that doesn't have Armbian support. S905X3 should have better support. But you are never certain all hardware will work.
    TV-box manufactures ofter use different components for the same model TV box. So some people might have wifi working, but others don't.
  20. Like
    TRS-80 reacted to ahoneybun in Armbian 23.05 (Suni) Testings   
    # Pinebook Pro testing
     
    ## Armbian_23.5.0-trunk.219_Pinebook-pro_jammy_current_6.1.29_gnome_desktop
    - Boots live disk [x]
    - Installs to eMMC - ext4 [x]
       - Fn keys works [] : NOTE F9 and F10 are swapped
          - Fn1 [x]
          - Fn2 [x]
          - Fn3 []
          - Fn4 [x]
          - Fn5 [x]
          - Fn6 [x]
          - Fn7 [x]
          - Fn8 []
          - Fn9 []
          - Fn10 []
          - Fn11 []
          - Fn12 []
       - Wi-Fi works [x]
       - Bluetooth works []
       - Touchpad works [x]
          - Ports
          - USB-C - data [x]
          - USB-C - power [x]
          - USB-A - data [x]
    BUG: Screen locking does not work without GDM.
    ## Armbian_23.5.0-trunk.219_Pinebook-pro_jammy_current_6.1.29_xfce_desktop
    - Boots live disk [x]
    - Installs to eMMC - ext4 [x]
       - Fn keys works [] : NOTE F9 and F10 are swapped
          - ESC []
          - Fn1 [x]
          - Fn2 [x]
          - Fn3 [x]
          - Fn4 []
          - Fn5 []
          - Fn6 []
          - Fn7 [x]
          - Fn8 []
          - Fn9 []
          - Fn10 []
          - Fn11 []
          - Fn12 []
       - Wi-Fi works [x]
       - Bluetooth works []
       - Touchpad works [x]
          - Ports
          - USB-C - data [x]
          - USB-C - power [x]
          - USB-A - data [x]
     
    BUG1: Ubuntu artwork is being used instead of Armbian during live disk boot once in the desktop. Shows the Ubuntu artwork during boot once installed to eMMC, it does show Armbian artwork at login screen/desktop.
    BUG2: Touchpad is very jumpy.
     
    ## Armbian_23.5.0-trunk.219_Pinebook-pro_jammy_current_6.1.29_i3-wm_desktop
    - Boots live disk [x]
    - Installs to eMMC - ext4 [x]
       - Fn keys works [] : NOTE F9 and F10 are swapped
          - Fn1 [x]
          - Fn2 [x]
          - Fn3 [x]
          - Fn4 []
          - Fn5 []
          - Fn6 []
          - Fn7 [x]
          - Fn8 []
          - Fn9 []
          - Fn10 []
          - Fn11 []
          - Fn12 []
       - Wi-Fi works [x]
       - Bluetooth works []
       - Touchpad works [x]
       - Ports
          - USB-C - data [x]
          - USB-C - power [x]
          - USB-A - data [x]
     
    BUG1: Battery indicator says no battery, I have opened a report of it here: https://armbian.atlassian.net/browse/AR-1756
    BUG2: Touchpad is very jumpy.
     
    # Not tested yet
    ## Armbian_23.5.0-trunk.219_Pinebook-pro_jammy_current_6.1.29_minimal
    - Boots live disk []
    - Installs to eMMC []
       - Fn keys works []
          - Fn1 []
          - Fn2 []
          - Fn3 []
          - Fn4 []
          - Fn5 []
          - Fn6 []
          - Fn7 []
          - Fn8 []
          - Fn9 []
          - Fn10 []
          - Fn11 []
          - Fn12 []
       - Wi-Fi works []
       - Bluetooth works []
       - Touchpad works []
          - Ports
          - USB-C - data []
          - USB-C - power []
          - USB-A - data []
  21. Like
    TRS-80 reacted to Werner in A newly designed multi-port hardware based on S905x3 chip   
    With free samples nobody can pay for their living.
    https://www.armbian.com/partner-contact-form/
    https://forum.armbian.com/subscriptions/
  22. Like
    TRS-80 reacted to maximumsettings in We are ready to offer a Bountysource donation to Armbian   
    Although I have not yet tested the Moonlight-QT build on the Orange Pi 5, I plan to do so tonight.  I will be contacting amazingfate regarding the bounty. I consider this to be the best $1000 I have ever spent, and I hope it marks the beginning of a long-term relationship between Maximumsettings and the Orange Pi 5 Armbian community. The Pi 5 will provide us with  one the most affordable and superior streaming device available in the market.

    Just so you know, our organization has many ideas, but we lack the internal resources to implement them. I am optimistic that we can create a situation where everyone benefits, a win-win scenario.  I am hopeful  that the approach of offering bounties for adding new features and fixing bugs will be successful within the Armbian community.
  23. Like
    TRS-80 got a reaction from d_m in Armbian 22.08 booting from emmc   
    In the following thread I essentially did all the steps I had mentioned above.  Proceeding slowly and carefully, I felt confident to flash the SPI, once I had determined that indeed it was empty.
     
    In the end you were right, the key is putting tow-boot on the SPI.  I mean, that is certainly the easiest way I think.  And the way I did it, I did not even have to open the case (which I was getting very tired of doing by this point, LOL).  I have got Armbian working now both via SD card (the other day) and/or eMMC (just tonight).  Detailed instructions can be found here:
     
    https://forum.armbian.com/topic/27598-getting-armbian-working-on-second-batch-mid-2022-pinebook-pro/
  24. Like
    TRS-80 reacted to morganwahl in Pinebook Pro working with generic arm64 UEFI image   
    Hello!
     
    I don't really have a question, but just wanted to report I tried out the generic UEFI arm64 image on a Pinebook Pro, and it installed emmc and booted just fine!
     
    This was possible because I had installed Tow-Boot to the SPI flash, which supports UEFI booting.
     
    I had tried using the Pinebook Pro build of armbian, which worked fine when booting off the sdcard, but installing it to the emmc wasn't working.
     
    I'm using Tow-Boot 2021.10 then arbmian image Armbian_22.08.7_Uefi-arm64_jammy_current_5.15.74 .
     
    There's a few rough edges in the grub menu, but it boots the OS off the emmc just fine.
     
    Should the be mentioned on the Pinebook Pro page? Personally, having Tow-Boot installed to SPI is all around a much more "normal" laptop experience, so it seems like a good idea in general.
     
     
  25. Like
    TRS-80 reacted to d_m in Armbian 22.08 booting from emmc   
    Honestly I would not have flashed Tow-Boot into the SPI except that at some point a U-boot update made my PBP unbootable. So I had no choice.

    I had to actually open the case to do this (and it took a few tries to get everything working) so it's certainly not for the faint of heart.
     
    I really wish Pine64 had shipped these things with a more reasonable boot loader from the start.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines