Jump to content

scargill

Members
  • Posts

    34
  • Joined

  • Last visited

Posts posted by scargill

  1. Hi

     

    Brand new (stretch) setup - armbian-config does not seem to want to change keyboard or allow hardware setup for i2c etc. I recall in the past using this board with Armian and having no issues. grabbed latest armbian-config update - that didnt improve things. Under system and wireless options in armbian-config - toggle hardware configuration is empty - ie nothing on left or right. 

     

    Ideas anyone?

  2. [twi0_para]

    twi0_used = 1

    twi0_scl = port:PB00<2><default><default><default>

    twi0_sda = port:PB01<2><default><default><default>

     

    Also one for twi1_para  -  and a twi_para   -  I set all 3 to 1 - recompiled - rebooted - no difference whatsoever...  still - at least now i know how to manipulate that file...

     

    I don't think it has done anything though... the script.bin file has definitely been updated...

     

  3. 27 minutes ago, martinayotte said:

    Is the SSD1306 appear when doing "i2cdetect -y 0" ?

    For the other I2C buses, did you enabled them in the FEX ?

     

    Hi there - no it is not appearing - but usually I use I2c1  - and there you have hit my limit - I have NO idea how to use that FEX - indeed I found an editor in the config and now I can't find that  - but no I have not enabled them in FEX - it would be nice to enable i2c1 - ????

  4. Erm I wonder if I can push my luck - the Serial is all working now... but when I come to look at I2c - (i2cdetect) only I2c 0 is there... and that appears to be pins 3 and 5 on the 40 way connector - but taking my SSD1306 display (I put them on all my boards with a little Python driver) - and plugging it in - nothing is showing on port 3c....   unusual... any thoughts?

  5. Thank you...  Well I clicked on LEGACY for this board as that's the only one I could find on the Armbian site (Orange Pi Plus 2E) - please point me elsewhere if I picked the wrong one - however - your fixes worked.  I had already had a go with the FEL editor - not having a clue what I was doing - simply setting the current 0 setting for the 3 serial ports to 1 - but that didn't work (it did result in a WHOLE boatload of serial ports however, appearing in DEV)  But just adding in the setting you both provided - works a treat - all 3 ports work and I can forget about the debug port - though it really would be good to know how to turn that debug off on port 0 - utterly wasted for me, once I'm up and running.

  6. Hi


    Can someone help. I have the current "legacy" ubuntu for Orange Pi Plus 2E - installed this morning.

     

    Everything seems fine except - I cannot figure out how to enable the serial port ttyS0 for general use - the console keeps grabbing it - I tried altering the boot cmd from console=both to console=tty1 - and I recompiled that as per the instructions - no difference - I can see on boot up that it is setting up ttys0 for debugging - and when I try to enable and then use it in Node-Red - it works at first - then some debug info comes in - and Node-Red loses control of the serial port.

     

    Can anyone help - also - SURELY there is more than one serial port on this board? The connector suggests at least 3 - but only ttyS0 is showing up in /dev  - ideas?  (without recompiling the entire operating system)?

  7. So the board works happily. Better don't expect any HDMI output from A64 devices. HDMI driver in legacy images is a mess (and no one is going to fix it since some libs are blobs and sources aren't available) and mainline/vanilla is missing display output completely.

     

    Normally our Pine64 images should 'just work' but I haven't looked into settings yet and won't spend any time on this since A64 is basically boooooring as hell (for my use cases it's almost as crappy as Rasperries due to limited I/O bandwidth and for that what the average user wants A64 is simply the wrong SoC due to display situation. And who needs those 64-bit when we're talking about IoT stuff?)

     

    I also have not the slightest idea why other vendors start wasting ressources with A64 boards... maybe it's just marketing and product development madness from Allwinner's side (the specific business unit partners with Microsoft to bring stuff no one needs -- Win 10 IoT -- to A64 devices)

    Erm ho wants A64 for IOT? Don't underestimate people's ability to go further than you might imagine. I do a LOT of stuff with Node-Red and the Pi at times shows it's lack of power. I'm hoping the Odroid will prove to be better but simple benchmarks for that A64 unit suggest it will go further.

  8. Well, my A64 turned up today. There are no holes next to the fan - indeed I can't find a 2-way connector anywhere on the board...odd as they supplied a fan!

     

    I blindly thought that the Armbian for the Pin64 might work but with nothing to lose I tried it....  it doesn't do anything other than the little green indicator light - just a black screen. That leaves a stripped down operating system with god knows what's missing or Ubuntu mate, both off their site - as there is nothing on the DietPi site either.   Oh well, I wouldn't care but their downloads are very slow - the 896meg file is going to take 8 hours.. Time for an early night I guess.

  9. For clarity - I have just created a new SD - this time using the legacy JESSIE.

     

    sudo ifconfig shows this...

     

    wlan0     Link encap:Ethernet  HWaddr 98:a6:91:6c:5e:80
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
     
    After nmtui creation and seamless activation..
     
     
    wlan0     Link encap:Ethernet  HWaddr 98:a6:91:6c:5e:80
              inet addr:192.168.0.158  Bcast:192.168.0.255  Mask:255.255.255.0
              inet6 addr: fe80::9aa6:91ff:fe6c:5e80/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:87 errors:0 dropped:0 overruns:0 frame:0
              TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:10047 (9.8 KiB)  TX bytes:4057 (3.9 KiB)
     
     
    Disconnect power - disconnect ETHERNET - reconnect power - wait...and wait.....

     

    Nothing. A quick system scan shows nothing...  disconnect  - back to ETHERNET...

     

     
    wlan0     Link encap:Ethernet  HWaddr 98:a6:91:6c:5e:80
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
     
     
    sudo nmtui
     
    The WIFI is there - but needs activating - this time it wants a password!!?? Connection takes several seconds this time.
     
     
    wlan0     Link encap:Ethernet  HWaddr 98:a6:91:6c:5e:80
              inet addr:192.168.0.158  Bcast:192.168.0.255  Mask:255.255.255.0
              inet6 addr: fe80::9aa6:91ff:fe6c:5e80/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:83 errors:0 dropped:0 overruns:0 frame:0
              TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:9099 (8.8 KiB)  TX bytes:2956 (2.8 KiB)
     
     
    Clearly something there.  I figured I'd try a reboot and leave the ETHERNET connected (last time was actual power off)
    Sudo reboot.
     
    No Ethernet (correct as WIFI should take precidence).
     
    Sure enough  - WIFI working. Working but slow and stuttering - the very reason I went for the latest build in the first place (I'm 3ft from the access point in a small non-metal office).
     
    Power off - disconnect Ethernet - power on.
     
     
    This time it works - but slowly.
    At this point, from earlier advice from TKaiser - sudo h3consumption -w off
     
    Please be patient, external requirements are to be installed.
     
    Aborted
    fex2bin/bin2fex not found and unable to install. Exiting
    Aborted
    Writing script.bin went wrong. Nothing changed.
     
    Tried again - same thing.
     
    So - I tried the sudo armbianmonitor -u command..
     
     
    ICMP Host Unreachable from 192.168.0.130 for ICMP Echo sent to sprunge.us (216.2                                               39.36.21)
    ICMP Host Unreachable from 192.168.0.130 for ICMP Echo sent to sprunge.us (216.2                                               39.36.21)
    ICMP Host Unreachable from 192.168.0.130 for ICMP Echo sent to sprunge.us (216.2                                               39.36.21)
    ICMP Host Unreachable from 192.168.0.130 for ICMP Echo sent to sprunge.us (216.2                                               39.36.21)
    Network/firewall problem detected. Please fix this or upload /var/log/armhwinfo.                                               log manually.
    /var/log/armhwinfo.log has been uploaded to curl: (7) Failed to connect to sprun                                               ge.us port 80: Network is unreachable
    gzip: /var/log/armhwinfo.log.1.gz: No such file or directory
    Please post the URL in the Armbian forum where you've been asked for.
    pi@orangepizero:~$
     
    Before anyone says that sounds like a connection issue - that has been my constant complaint about earlier WIFI on the Pi Zero.
     
    pi@orangepizero:~$ ping www.bbc.co.uk
    PING www.bbc.net.uk (212.58.246.54) 56(84) bytes of data.
    From orangepizero (192.168.0.130) icmp_seq=1 Destination Host Unreachable
    From orangepizero (192.168.0.130) icmp_seq=2 Destination Host Unreachable
    From orangepizero (192.168.0.130) icmp_seq=3 Destination Host Unreachable
     
     
    Note that the first ping went through.
     
     
    I think it is fair to say that the hardware WORKS?
     
     
     
     
     
     
  10. This is normal

     

    Please provide output of "iwconfig" and please check if any wireless networks are displayed in nmtui - Activate a connection

     

    IWCONFIG says:

    eth0  no wireless extensions

    lo      nowireless  extensions..

     

    Thewireless network I put into nmtui is there - but nothing when you go to activate - just nothing there at all in the menu to activate.

  11. @scargill

    Looks like you are missing the firmware... If a directory /lib/firmware/xr819 doesn't exist, then please create it and put files from here inside it.

    Hi there

     

    The "firmware" subfolder did not exist at all - so I created it and put those files in.

     

    I then rebooted the board. I deleted the WIFI connection and recreated it. Still nothing - no Activate.

     

    I tried sudo modprobe and then nmtui again - no difference. I tried iwlist wlan0 scan - still - wlan0 interface doesn't support scanning.

     

    Here is the latest log output - http://sprunge.us/YFJF

     
    Somewhat different message now
     
    xradio_wlan: unknown parameter 'macaddr' ignored
     
    Anything I've missed?
  12. True. Pete, please provide output from 'sudo armbianmonitor -u' when connected via Ethernet (or at least dmesg output if you access the board through serial console).

     

    JFTR: WiFi on my OPi Zero stopped working some weeks ago after I did some hardware stuff so my assumption was that I managed to damage the board glueing a heatsink to the SoC or exchanging antennas. But maybe this was unrelated and WiFi is broken on some boards. At least logs would help to diagnose the problem (or let's better say they're necessary). Please see posts #155 and #158 here: https://forum.armbian.com/index.php/topic/2808-orange-pi-zero-went-to-the-market/?p=21561

     

    As per request - the log is here...  

     

    http://sprunge.us/VWZB

     

    This line stood out from the crowd...

     

    xradio_wlan mmc1:0001:1: Direct firmware load for xr819/sdd_xr819.bin failed with error -2

     

    As did these later on

     

    [ 12.031511] xradio_wlan mmc1:0001:1: Direct firmware load for xr819/sdd_xr819.bin failed with error -2

    [ 12.031532] xradio_wlan mmc1:0001:1: Falling back to user helper

     

    Standing out is one thing of course - I've no idea what to do about it.

  13. True. Pete, please provide output from 'sudo armbianmonitor -u' when connected via Ethernet (or at least dmesg output if you access the board through serial console).

     

    JFTR: WiFi on my OPi Zero stopped working some weeks ago after I did some hardware stuff so my assumption was that I managed to damage the board glueing a heatsink to the SoC or exchanging antennas. But maybe this was unrelated and WiFi is broken on some boards. At least logs would help to diagnose the problem (or let's better say they're necessary). Please see posts #155 and #158 here: https://forum.armbian.com/index.php/topic/2808-orange-pi-zero-went-to-the-market/?p=21561

     

    I've been experimenting and getting no-where - so to be safe I'll reload the operating system then send the logs. .(zador.blood.stained - I had no idea about this logging -not everyone has the same level of knowledge of Armbian)

  14. Just tested the wireless again with Xenial FEL booted system. Worked fine for me: nmtui - Activate a connection - (selected wireless network) - (input password) - connected.

    One time before my wireless network was not displaying in "Activate a connection" window, so I had to run "iwlist wlan0 scan" since there is no rescan option in nmtui network list.

    Hi there

     

    iwlist wlan0 scan

     

    wlan0     Interface doesn't support scanning

     

    What version operating system and release did you use? I used the latest nightly build as an earlier version was unreliable (but actually worked)

  15. sudo modprobe xradio_wlan   returns nothing... just back to the prompt

     

    sudo nmtui still shows the connection when you go to edit - but does not show anything in the ACTIVATE area - seems more like a bug in nmtui surely... after reboot the entry is still there under edit - but no sign of it in activate.

×
×
  • Create New...