Jump to content

GeorgeP

Members
  • Posts

    33
  • Joined

  • Last visited

Posts posted by GeorgeP

  1. 2 hours ago, DanielRuf said:

    That was also my plan originally ;)
    The original Ubuntu image should work (but OMV does not work on Ubuntu, in case you want to use that) and also the Debian image in the Odroid forum should work, which uses the stock Odroid Kernel.

     

    In the Odroid Board we found that apparently the 4.9-Kernel-Version of the Armbian image should also work, which I will try this evening.

     

    For reference, see https://forum.odroid.com/viewtopic.php?f=207&t=41019

     

    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. 15 hours ago, belfastraven said:

    Hmmm  if your Ctrl-Alt-F2 prints a #,  I believe it is somehow using the us (or perhaps ANSI) keyboard layout.  That is what all of my other keyboards show  by default--the PBP is my only ISO keyboard device. 

     

    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 :-)

     

    Quote

    If you want to build groovy,  I believe you need to used EXPERT=yes on the ./compile.sh command.  I have done a dev build,  which builds kernel 5.9(.1 right now)  .  I did a console rather than a desktop build so I could play with installing a different desktop.   Groovy runs very well so far for me.

     

    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?

     

    Quote

     I am booting the NVME from SPI flash.   I installed an armbian uboot myself on  on SPI flash ,,  but I can see that armbian-config is being enabled to do that, too. 

     

    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 :-)

     

  3. 2 hours ago, belfastraven said:

    When you speak about opening a terminal window,  do you mean on the desktop?  or do you mean opening a terminal console with  CNTL-ALT-F(some-number).  The mechanisms are different.  For the  CNTL-ALT-F(some-number) ,  if I set  the /etc/default/keyboard file so that 

    XDBMODEL="pc105"

    XDBLAYOUT="gb"

    XDBVARIANT="intl"

     

    I get the pound sign at shift-3.

     

    For the desktop console, it is controlled by whatever desktop manager you are using, I believe.   So if in the desktop  settings you have the pc105 UK keyboard selected,  that should be working.   If it works elsewhere on the desktop,  but not in the desktop terminal--could it have something to do with the particular font or character set used for the terminal?  

     

    just FYI I am using groovy with a cinnamon desktop,  I have an ISO keyboard,  and I can indeed display the GBP 

     

     

    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?

     

  4. 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 

     

  5. 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!!

     

  6. 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.

     

     

  7. 32 minutes ago, Flole said:

    In order to solve my issues with the lockup I tried to enable the watchdog but I found the board locked up again this morning. Either the reboot is not working cleanly or the watchdog is not resetting the board correctly or my USB HDD is not initialized properly.

     

    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

     

  8. 2 hours ago, AZ8 said:

    1. how far Armbian on Opi3 from stable point?

    2. did someone compare performance Kodi on Armbian over LibreELEC? Is LibreELEC significantly faster?

     

    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 :D

  9. 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, .....

     

    image.png.cf97b1b2565efe2a6763e577d4e1cb95.png

  10. 8 hours ago, wureka said:

    I tried to boot it with ......

    However it was all in vain.

    ...

    Any suggestion?

     

     

    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?

  11. 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.

  12. On 8/29/2019 at 4:24 PM, Igor said:

    There is a mess with this firmware ... perhaps we only need to adjust this patch: https://github.com/armbian/build/blob/master/patch/kernel/rk3399-default/adjust_wireless_firmware_path.patch

    ... or rather make a copy/link from ap6212 -> rkwifi because it is highly possible we have different chips on the same board model.

     

    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

     

     

     

  13. 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

     

     

  14. 37 minutes ago, maxlinux2000 said:

    Now we are at 5.93 with kernel 5.2.6 but I would like to be able to compile builds with kernel of the 5.0.x series, because although sometimes they were hung and the audio does not work, at least they can be used.
    Right now I'm using an old build to write to you, but I don't dare to update it in case something breaks.

    This is working very well for me (only 5 days uptime due to local power outage - otherwise it "just works" :-)

    Screenshot_2019-08-09_12-39-38.png

     

    Screenshot_2019-08-09_12-42-51.png

  15. 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.

     

     

  16. 15 hours ago, dziobak said:
    
    apt-mark hold linux-dtb-dev-sunxi64

    and do full apt update/upgrade

    Works perfectly for me - thank you @dziobak :thumbup:

      ___  ____  _   _____
     / _ \|  _ \(_) |___ /
    | | | | |_) | |   |_ \
    | |_| |  __/| |  ___) |
     \___/|_|   |_| |____/
                           
    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       

           

     

  17. 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

     

  18. 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...

Important Information

Terms of Use - Privacy Policy - Guidelines