Jump to content

GeorgeP

Members
  • Posts

    33
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Applications

Everything posted by GeorgeP

  1. Thanks for the reply. I don't need OMV and I have no real need for a 'bleeding edge' kernel. so I think I will probably get one of the boards and go for Armbian with the 4.9 kernel. What's the stuff about "getting rid of petitboot"? - Don't the Odroid boards boot direct from SD?
  2. @DanielRuf I was thinking about getting one of these boards to put together a simple NAS for a friend but I would really need it to 'just work' - sadly I don't have the free time to tinker as much as I used to :-/ Do you know if the OEM supplied firmware (Ubuntu?) works OK? Thanks!
  3. GeorgeP

    Pinebook Pro

    Yeah - I'll look at this again when I get chance but it's not a big issue for me now - I don't often need to type '£' in a text console :-) I may give that a go - I have a build environment set up in a VM (somewhere! ;-) ) Although I've done loads of headless/server stuff this is my first real venture into Armbian desktops. If you build a console image can you then install a choice of desktops from armbian-config or do you have to do it all manually? I saw the armbian-config option to boot from SPI flash but was a bit scared of trying it in case I screwed the SPI if it went wrong, leaving me having to learn how to fix a 'brick'. If I can boot from SPI to NVME I can then use the EMMC for something else :-) Thanks for all your input :-)
  4. GeorgeP

    Pinebook Pro

    Thanks for the input. I was originally referring to a terminal window on the desktop. When I read your message I looked at /etc/default/keyboard and found all kinds of weirdness originated from I've no idea where!! I rebooted, ran armbian-config and re-entered all of my usual settings, rebooted again and it's now behaving (well - sort of!). My /etc/default/keyboard now looks like yours and a terminal window opened on the desktop now behaves correctly. If I open a console terminal (Ctrl-Alt-F2 say) then shift-3 still does something weird - it appears like it prints a hash and then a CR - but for now that's not an issue I can afford time to look at. So it looks like I had some corruption in the keyboard settings file - and as I remember I did have the system shut down on me (flat battery) half-way through some configuration :-) Interesting that you say you are running 'groovy' - presumably that is now an option in the armbian build system? I've not built by own versions for some time. How does it run on the PBP?
  5. I built a system very similar to this one: https://cgomesu.com/blog/Nanopi-m4-mini-nas/ The heatsink on the SATA hat does run hot but using the fan driver on the 'hat' and the code in the article (which drives the fan according to the SoC temperature) keeps everything running nicely. Welcome to Armbian 20.08.9 Buster with Linux 5.8.13-rockchip64 System load: 2% Up time: 8 days 2:59 Memory usage: 22% of 3.71G IP: 192.168.x.x CPU temp: 40'C Usage of /: 33% of 15G
  6. GeorgeP

    Pinebook Pro

    UK (ISO) Keyboard problem - terminal won't display a 'pound' As a long-time user of various flavours of Armbian on headless sytems (OrangePi, NanoPi ...) I couldn't resist installing it on my new Pinebook Pro. Well it works like a dream and I am just sooo impressed by all the work that has clearly been done - audio works fine, armbian-config had me set up booting from emmc with my rootfs on nvme SSD in no time at all. BUT - one weird problem that has me baffled... I'm so used to headless Armbian boards that setting up keyboard and localisation is almost automatic to me - but can I get the PBPro keyboard to generate a 'pound' (GBP, '£') in a terminal window- no I cant!! I've set everything up as I think it should be - and every other key on the (ISO) keyboard is correct - but open a terminal window and shift-3 (which should be '£') displays nothing at all. Other applications (Firefox, LibreOffice ...) will display the £ just fine. Can anyone give me any clues??? Thanks!!
  7. I've no specific postgresql experience but I have found that the way Armbian handles logging to zram can mean that the log files either don't exist or can't be written. Generally the answer to situations like this is to try running the binary from a command prompt with the 'verbose' switch set, if it then runs OK, try to modify the sysctl files to enable logging.
  8. I can't help thinking that something isn't right with your hardware. Have you tried booting the bare board "normally" from an SD card? I'm running my OPi3 on what is quite an old build but it seems rock solid. If it ain't broke..... ___ ____ _ _____ / _ \| _ \(_) |___ / | | | | |_) | | |_ \ | |_| | __/| | ___) | \___/|_| |_| |____/ Welcome to Ubuntu Bionic with Armbian Linux 5.3.0-sunxi64 System load: 0.15 0.16 0.14 Up time: 69 days Memory usage: 38 % of 1993MB Zram usage: 5 % of 996Mb IP: 192.168.0.5 CPU temp: 51°C Usage of /: 50% of 7.1G
  9. 1: I'm running an OPi3 as a headless server and I have no issues whatsoever.... Welcome to Ubuntu Bionic with Armbian Linux 5.3.0-sunxi64 System load: 0.02 0.07 0.03 Up time: 55 days Memory usage: 36 % of 1993MB Zram usage: 5 % of 996Mb IP: 192.168.x.x CPU temp: 54°C Usage of /: 52% of 7.1G 2: I have no idea. If I wanted a media centre I'd just buy a TV-box
  10. Maybe people looking to run a stable system should just stop chasing the very latest of everything! This uptime of 42 days is only because of a local power outage, otherwise it's absolutely rock solid running snapd, nextcloud, mosquitto, node-red, grafana, .....
  11. Without any information on what error messages you see it is almost impossible to suggest what may be wrong. Are you using a good power supply? Have you tried a different supply? Have you tried a different SD card?
  12. Remember that the H6 boards are still very much in development stage. If you aren't prepared to lose some data then IMHO you should choose a more stable platform.
  13. What is your power supply? You say "if the light comes back....." so are you using some kind of solar power? Why do you not want the systems to run continuously? You will struggle to get any board to start reliably if the power supply voltage increases slowly and a poor power supply is the cause of most reliability issues with any sbc. If you do have a solar supply you need to use a controller which switches the supply off and on according to the battery voltage. I strongly suspect that this could be your problem rather than the OS. You can try Armbian which I have always found to be 100% solid as long as you choose a stable version.
  14. I have a NanoPi Neo4 running "Debian Buster with Armbian Linux 4.4.190-rk3399" and I don't see this problem. I see this in htop:
  15. I've just come across this same problem. I copied the two files 'fw_bcm43438a1.bin' and 'fw_bcm43438a1_apsta.bin' (I'm not sure if that second one is needed) from /lib/firmware/ap6212/ to /lib/firmware/rkwifi/ and rebooted and the wifi now works OK. My board is very much a 'test bed' at the moment so I'm happy to test any possible fixes. George
  16. I just bought a FriendlyElec NanoPi Neo4 having had loads of experience with Armbian on Allwinner (OrangePi) boards. My preferred method for getting boards "up and running" is simply to connect a serial terminal to the debug port and power on. I tried this with several Armbian Buster images and found that I couldn't log in as root on any of them. Checking the SD card on my laptop, the debug port (ttyFIQ0) was missing from /etc/securetty. Editing /etc/securetty and adding ttyFIQ0 on a new line at the bottom of the file and all is well and I now have Buster up and running on the Neo4 :-) root@nanopineo4:/etc# diff securetty~ securetty 413a414,415 > > ttyFIQ0 root@nanopineo4:/etc# Can I suggest that this be added into the build? Thanks! George
  17. This is working very well for me (only 5 days uptime due to local power outage - otherwise it "just works" :-)
  18. Thanks MaX, but now I already have what I need - thanks to some others' comments on my post :-)
  19. Now that the OPi3 has been moved into the Armbian downloads section there needs to be be a set of 'known-to-be-working' images made available while development on newer kernels and features continues. There will be a number of people buying the OPi3 as their first SoC board, trying the 'factory' images (as we have all done in the past ) and then coming here where they will currently find images labelled "Suitable for Testing" that will not boot. This is not a great first impression of Armbian for these people, who won't yet have the knowledge or experience to hold back upgrade packages or to replace dtb files, etc. and just want to be able to boot a [mostly] working system.
  20. Works perfectly for me - thank you @dziobak ___ ____ _ _____ / _ \| _ \(_) |___ / | | | | |_) | | |_ \ | |_| | __/| | ___) | \___/|_| |_| |____/ Welcome to Ubuntu Bionic with Armbian Linux 5.1.7-sunxi64 System load: 0.22 0.16 0.14 Up time: 44 min Memory usage: 17 % of 1997MB IP: 192.168.xxx.xxx CPU temp: 36°C Usage of /: 24% of 7.1G
  21. Aaarrrgghh!! How did I not find that Thank you!
  22. Thanks for the suggestion but I need to use Ubuntu for the things I want to test, and I don't have *ANY* earlier Ubuntu images, only Debian :-/
  23. Hi guys, I'm aware of the current issues with the OPi3 images not booting and for me I can't find any of the currently downloadable images that will boot. I just need to urgently test a couple of things - can anyone point me to a reasonably recent Ubuntu Bionic dev server image for the OPi3 that will boot/run? I have an "old" Armbian_5.78_Orangepi3_Debian_stretch_dev_5.0.7.img that runs just fine (as long as I don't upgrade it!) but I don't have any similar Ubuntu versions. Does anyone happen to know of an archive of old versions, or maybe have something that I could download direct? Many thanks! George
  24. Seeing the current issues I'm happy that I'm running an earlier build :-) Welcome to ARMBIAN 5.83 user-built Debian GNU/Linux 10 (buster) 5.0.9-sunxi64 System load: 2.14 2.11 2.06 Up time: 23 days Memory usage: 60 % of 1997MB Zram usage: 1 % of 998Mb IP: 192.168.0.5 CPU temp: 56°C Usage of /: 27% of 7.1G Currently running PiHole, MQTT and SETI@Home :-D
×
×
  • Create New...