Jump to content

petrmaje

Members
  • Posts

    69
  • Joined

  • Last visited

Posts posted by petrmaje

  1. On 6/30/2017 at 9:40 AM, zador.blood.stained said:

    Support for this board is marked as "phased out", but the build target was not removed and upgrading the kernel will be possible too (at your own risk).

     

    Please check this thread, it appears that there is at least some progress. I will move messages related to R1 to this thread later.

    Hi,

    the situation with Lamobo is very bad. I understand reasons, why you drop support for the board, but you should provide last working configuration for possible upgrades. All devices with next kernel will die after apt-get upgrade. This happened to me today. In archive is nothing working with kernel 4.x, which I need. So is it possible remove R1 from build target and in download section offer last 4.x kernel with switch support? And block kernel upgrade using apt?

    Thanks,

    Petr

  2. I have one OrangePiPc with an ip camera, resolution 1280 * 720 and 5fps. The processor load is 5%. Only problem zoneminder not updated to version 1.30, and I'm not going to do it manually because the system is fully functioning for months without any problem.

    1.29 is good and stable, it was big step forward from previous version.

  3. Everything depends on what do you need. I required two 1280x720 cameras at 10FPS, three 640x480. The reason was, that our old dual core xenon server was overloaded, so I tried to move the system to ARM. But generally, if you dont need so high framerate, one board should be enough for several cameras.

    For zoneminder is one important rule - more cores are better :) Other things you can tune up by software. Thats my experience.

    But finally I replaced dual core xenon by quad core xenon and the system load drops down to 10%.

    PM

  4. i have the same error.tvheadend shows in :

     

    cat /etc/apt/sources.list.d/tvheadend.list 

     

    but fails when trying to install (with both apt-get or script) : Unable to locate package :(

    Try to compile it from source. It is easy with armbian, everything is preinstalled and you don't need to wait for somebody to fix it. Or, did you find another solution?

  5.  

    Are you using latest script?

     

    I just tested - working normally.

    cat /etc/apt/sources.list.d/tvheadend.list 

    must result in:

    deb https://dl.bintray.com/tvheadend/deb wheezy release

    It seems to be ok:

    root@TVheadend:~# cat /etc/apt/sources.list.d/tvheadend.list
    deb https://dl.bintray.com/tvheadend/deb wheezy release
    root@TVheadend:~#
    

    In the meantime I compiled tvheadend from source, but I have another issue with uploading firmware to USB dongle:

    [    8.725304] dvb-usb: found a 'Leadtek WinFast DTV Dongle Gold' in warm state.
    [    8.733722] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
    [    8.744609] ERROR: 256 KiB atomic DMA coherent pool is too small!
    [    8.744618] Please increase it with coherent_pool= kernel parameter!
    [    8.751888] dvb-usb: Leadtek WinFast DTV Dongle Gold error while loading driver (-12)
    [    8.757347] dvb_usb_af9015: probe of 1-1.2:1.0 failed with error -12
    [    8.762924] usbcore: registered new interface driver dvb_usb_af9015
    
    

    I am googling about it ...

     

    Kernel 4.4.1-sunxi has no problem with uploading firmware ....

  6. Apart from the many issues we had with the R1 (vendor 'forgot' to define SATA power definition, faulty power design, crappy OS support in the beginning and so on), there's one thing most people interested into this device always overlook: It's not suitable to be used as a router without an additional USB-to-Ethernet dongle.

     

     

    Hi Tkaiser,

     

    USB-to-Ethernet dongle is not the only solution. People with PPPoE are without problems, as the people with tagged wan. If you have a switch at home with two unused ports, you can tag your wan and everything should be ok.

     

    PM

  7. Hi Petr, 3 devices at the moment, multicasting a movie to the Apple TV while I made the measurements, and 2 simultaneous devices in the last couple of days without any hitches. For me it is far much better, I never had a wifi connection with stalling to a halt on the client side for more than 2-3 minutes. I will do more extensive tests next week.

     

    It looks like big step forward :) I will try it on my lamobo during weekend ;)

  8. My SSID is "rui"

    Hi Rui,

     

    it looks impresive, but I had similar results with some drivers a time before. How many devices do you have connected to the AP? Try to connect for example 3 or 4 wifi devices, some of the far from the AP and generate network traffic simultaneously.

    If your driver will handle it without speed drop to minimum, congatulations!!!! :)

     

    Petr

  9. The question is, if the device will overlive till evening. System is running on SD card and HD is only for data. Is the linux log so clever, that when there is no space for logging will flush logfiles?

     

    BTW.

     

    There is a temporal solution by switching to alternative A20 kernel.

     

    apt-get install linux-image-banana

     

    ...  but that kernel will not update anymore in the future so you will need later to come back to

     

    linux-image-sun7i

  10. Hi,

     

    after pure installation Armbian_4.5_Lamobo-r1_Debian_wheezy_3.4.109.zip, the log is full of GMAC messages:

    [43099.518189] GMAC TX status: VLAN frame
    [43099.521192] GMAC TX status: VLAN frame
    [43099.524646] GMAC TX status: VLAN frame
    [43111.775611] GMAC TX status: VLAN frame
    [43112.963963] GMAC TX status: VLAN frame
    [43112.980989] GMAC TX status: VLAN frame
    [43112.986370] GMAC TX status: VLAN frame
    [43112.989681] GMAC TX status: VLAN frame
    [43112.992410] GMAC TX status: VLAN frame
    [43112.996184] GMAC TX status: VLAN frame
    [43113.002038] GMAC TX status: VLAN frame
    [43113.973308] GMAC TX status: VLAN frame
    [43113.976078] GMAC TX status: VLAN frame
    [43114.143583] GMAC TX status: VLAN frame
    [43114.487643] GMAC TX status: VLAN frame
    [43114.700444] GMAC TX status: VLAN frame
    [43115.015755] GMAC TX status: VLAN frame
    [43115.188027] GMAC TX status: VLAN frame
    
    

    Bug? Or I configured something wrong?

     

    PM

     

  11. Kann mir jemand helfen!

    ich habe schon alles ausprobiert von Tido, usw.

    ich habe das img Armbian_4.2_Lamobo-r1_Debian_wheezy_4.1.6

    Mein vorhaben den wan port (3) als internet Eingang, die anderen Ports sind für meine Clienten  die au den Board zugreifen können.

    Gibt es ein img. was funktioniert oder mir sharen kann.

    Sorry ich kann nicht gut Englisch  

    Ich Danke in voraus

    You need probably the same configuration as cfi700. So follow his steps in this forum and everything should work.

  12. Hi,

     

    there is more cases, how the interface can be down. It can be physicaly unpluged, it can be can be up, but without connection to the internet etc.

    If you want real failover connection, you have to write some script, which will check connection availability. Something like this:

     

    if ping -I eth0 8.8.8.8 then ip route change default via eth0 gateway

    else  ip route change default via ppp0 gateway

     

    I did this for my friend a time ago and it works fine.

  13. Nothing to add, just a breadboard a 4.7K res on a base of a transistor (picture TKasier) and that  petrmaje didn't give up on the R1, makes me smile. :rolleyes:

    I geuss Goethe is right again : "In the realm of ideas everything depends on enthusiasm... in the real world all rests on perseverance.

     

    Currently i´am on a D.V.R. with R1 and zoneminder (ipcamera) project, no problems, and damn the A20 still keeps surprising me.

     

    Caio from Holland

    :-) the board is so bad and so good... Goethe is right :)

  14. :-) I was in the same situation several months before. Lamobo can work perfectly, as both of my lamobo does, but you must: (thanks to Igor, Patcher, Tkaiser etc...)

     

    - Operate Lamobo verticaly

    - put high profile heatsink to BCM switch (under the harddisk)

    - put heatsink to A20

     

    If you use ordinary HDD with consumption 500mA, no USB, no WiFi, no HDMI and you have good USB power cable, you don´t need secondary power via battery connector.

     

    20150915_193939.jpg

     

    :-) It works :))))

     

    PM

     

     

    Hello everybody.

    before exposing my actual problem a little summary so that others who faced the same situation might benefit.

     

    I got my buggy Lamobo-R1 and tried every possible image with sata before finding armbian.

    I didn't expect so many problems and I tried to mount my sata hd for the first time when the unit shut off.

     

    The armbian image file stopped booting when a SATA hd was connected to the unit!

    I spent 5 days writing to Sinovoip and reading their nonsense replies until they sent me a link on the bananapi

    forums full of complaints about how poorly this unit was designed.

     

    No improvement. My unit does not boot with 5v 4A power injected through battery connector (even pushing pwr on button).

     

    Finally I tried the only other option I've read on the same forum here , injecting power to J12 connector, and couldn't boot either but - unexpectedly - after removing J12 power the Lamobo-R1 booted again with armbian sd image and the sata worked.

     

    Summarizing no boot possible injecting powering the unit other than from the micro USB port

    With micro USB + battery connector I can boot and use SATA (just tested mounting and accessing files though)

    BUT if I use the HD drive continuously reading it for more than 22/25 minutes then the unit shuts down unexpectedly.

     

    For the heat issues I read on forums I put silicon nuts to give 5mm space between the pcb and the hard disk but even with that the unit shuts down,

    but honestly after 25 minutes the heat didn't seem that much.

     

    Do you have hints/suggestions on how to proceed? I'll put a fan now to test if this behaviour is due to heat but I'm skeptical.

     

    Thanks for any help you might give,

    V.

  15. thanks for your lightspeed reply  :)

     

    I feel a bit stupid but I can't find any .fex file in my system

     

    edit :

    tried Vanilla and Legacy kernel and I can't find any .fex file anywhere that is maybe part of the problem

    You must convert /boot/script.bin to fex by bin2fex tool, edit and convert back by fex2bin tool.

    What device do you want to connect? I have piface with LCD display, which is also connected by SPI (MCP23s17 expander), I tried it some time before with my R1, but without success. If you will make SPI working, post your experiences here, please :)

  16. I found some documents on the net, but they did not help ... :( So I did it my way :D :D

     

    Wooww !! Great !

     

    Thank you for your great recipe, it is working great !

    So the only way to work with device tree is to reverse engineer the code ?

     

    It was really hard to find the right info on the net ! I hope it is going to be a little bit easier for battery management, not sure :s 

  17. Hello,

     

    I used to work with script.bin to configure LED and Battery management on my Olimex A20 Lime2. It was pretty easy. 

    Since I switched to kernel 4.1 I had to deal with device tree which is terrible to understand.

     

    I would like to do a simple thing : change my Led conf. @petrmaje I fallowed your indication but I can't find a way to adapt it on my board.

     

    Below is what I have :

                            led_pins@0 {
                                    allwinner,pins = "PH2";
                                    allwinner,function = "gpio_out";
                                    allwinner,drive = <0x1>;
                                    allwinner,pull = <0x0>;
                                    linux,phandle = <0x35>;
                                    phandle = <0x35>;
                            };

    and

            leds {
                    compatible = "gpio-leds";
                    pinctrl-names = "default";
                    pinctrl-0 = <0x35>;
    
                    green {
                            label = "a20-olinuxino-lime2:green:usr";
                            gpios = <0x1a 0x7 0x2 0x0>;
                            default-state = "on";
                    };
            };
    

    The gpio declaration is not clear at all

    gpios = <0x1a 0x7 0x2 0x0>;
    

    I don't know how to modify it to GPIO 3 PIN 33 (PH20)

     

     

    Sometime on the web, I find this

    gpios = <&gpio3 20 0>;

    But same, it does not work.

     

    Any clue ?

    The key is to reverse compile dtb to dts, then you get easy readable format of the file. So when you want to change this led to PH20, try this:

     

    in first section: allwinner,pins = "PH20"

     

    in second section:

     

    gpios = <0x1a 0x7 0x14 0x0>;

     

    This should work.

    I found this way by reverse engineering, but once more gpios parameters:

     

    0x1a - I dont konow

    0x7 - port group, group is "H"=7 (A=0 etc)

    0x14 - port number is 20 (PH20) and when you convert 20 to hexadecimal = 0x14.

     

    PM

  18. @petrmaje:

    You are the best!

     

    Now, the BPi R1 working as expected.

     

    But... i have two more little problems:

    First is there a easy way to disable the WLAN? (not so tragic if not)

     

    Second, maybe more complicated - For some of my IOT-Clients I need a static IP-Address (connect to MAC). Could I do this as well in one of the configuration files and could you give me some hints?

     

    service hostapd stop

    update-rc.d hostapd disable

     

    For static DHCP leseases simply add line like this to dnsmasq.conf :

    dhcp-host=02:05:05:02:d3:84,10.0.0.220
    
  19. Many thanks for your quick reply.

    Could you please show me more details on how to set lan is br0 in the interface config.

     

    The changes in dnsmasq you suggested are done.

    auto lo
    iface lo inet loopback
    
    auto eth0.101
    iface eth0.101 inet dhcp
        pre-up swconfig dev eth0 set reset 1
        pre-up swconfig dev eth0 set enable_vlan 1
        pre-up swconfig dev eth0 vlan 101 set ports '3 8t'
        pre-up swconfig dev eth0 set apply 1
    
    auto eth0.102
    iface eth0.102 inet manual
        pre-up swconfig dev eth0 vlan 102 set ports '0 1 2 4 8t'
        pre-up swconfig dev eth0 set apply 1
    
    auto br0
    iface br0 inet static
        address 192.168.2.1
        netmask 255.255.255.0
        network 192.168.2.0
        broadcast 192.168.2.255
    bridge_ports eth0.102
    
    
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines