Search the Community

Showing results for tags 'legacy'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues
    • Peer to peer technical support
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Armada A388, A3700
    • Amlogic S905(x)
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
  • Development
    • Allwinner H6
    • Rockchip 3399
    • Development

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 8 results

  1. Hi, my rock64 (rev2) with the latest build of Armbian randomly looses its network connection. I couldn't use the armbianmonitor -u as it had no network connection, but when i use ifconfig, I can see it's still got it's settings and is the NIC lights are on. ifconfig showed 6 TX errors. My NIC is set to DHCP with static reserved IP address to an ASUS router. I leave it on 24/7 and check it once a while as it pretty much is used as a NAS with a single USB 3 drive. This morning I connected up via HDMI and a USB keyboard and logged in successfully. I don't have much Linux experience so wasn't sure how to capture the logs to SD card so i could copy them up here later. The NIC dropouts occur about once a week at random days and times. I have tried use ifup and ifdown to try and re-enable the NIC, but when I did this I got a stack dump and I couldn't enter any further commands into Ubuntu. Next time the NIC fails, what command(s) should I use? I've had this issue before on the later ayufun arm64 ubuntu builds too. I see the kernel has been updated to v5 over at ayufun's github, maybe there are some code changes that might help. I did read that dropping the MTU down from 1500 to 1492 might help, but don't really want to make random changes. Any suggestions much appreciated.
  2. The newest revision does not boot from current SD images. I'm working to debug why. If anyone else has a board and can test it out, let me know. The eMMC will boot, no problem, so it's just the SD itself. Model: Pine64 Rock64 DRAM: 1022 MiB MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1 SF: Detected w25q128bv with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Pine64 Rock64 misc_init_r cpuid=55524b50303930343200000000051f1a serial=f55c6806c317581 Net: eth0: ethernet@ff540000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! mmc_init: -95, time 9 switch to partitions #0, OK mmc1 is current device ** No partition table - mmc 1 ** starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: Core Release: 3.10a USB3: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 2 USB Device(s) found scanning bus 2 for devices... 2 USB Device(s) found scanning bus 3 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT Ideally getting old an new to boot would be ideal, @Igor this might mean a fragmentation for this board though, like having a V2 and older and a V3 and newer build if we can't make them all play nice with one bootloader.
  3. Hello, I recently installed Armbian 5.85 legacy on my new Orange Pi Lite in order to try out my new Orange Pi camera, but it's not being recognized at all, even after following the instructions in this topic: I already tried doing the following (as root) unsuccessfully (no errors returned, but still can't detect camera): sunxi-pio -m "PG11<1><0><1><1>" #DOVDD sunxi-pio -m "PE15<1><0><1><0>" #Power_Down sunxi-pio -m "PE14<1><0><1><1>" #reset modprobe gc2035 modprobe vfe_v4l2 Here's the output of lsusb: Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Unfortunately, Armbian 5.20 is no longer available, so I can't try that unless I can compile it from source.
  4. Hello everyone :-). I would like help, I checked on the Web and I found using the forum a script (that I modified) to trigger using DTS LEDs. I adapted the script found here at the end of the page: Topic 112-dtb-howto-add-leds I think that for the section "disk-activity" and "netdev" it misses options but I'm not a developer just a scheming. Can you please explain to me how to add options to the mentioned trigger? I searched a lot of time but did not find any information. Here is my script, everything works fine (compiled with armbian-add-overlay), but "disk-activity" and "netdev" do not work. I tested the write / read trigger on disk but did not work either. Can you explain to me how to add the (device) options for disk-activity (with usb-nand-sata on / dev / sda) and netdev (for eth0)? thank you for the one who can help me to understand or to work this script. My card is OrangePi PC2 H5 1GB Sorry for bad english, my mother language is french. (this message is translatted in english from french) here is my script: /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h5"; fragment@0 { target = <&pio>; __overlay__ { gpio_pin: gpio_pin { pins = "PA19","PA7","PA8","PA9","PA10","PD11","PA6","PA1","PA0","PA3"; function = "gpio_out"; }; }; }; fragment@1 { target-path = "/"; __overlay__ { gpiopull: gpiopull { compatible = "gpio-leds"; pinctrl-names = "default"; pinctrl-0 = <&gpio_pin>; status = "okay"; gpio_out_19 { label = "P19:orange:wifiRx"; gpios = <&pio 0 19 0>; linux,default-trigger = "phy0rx"; }; gpio_out_7 { label = "P7:red:wifiTX"; gpios = <&pio 0 7 0>; default-state = "om"; linux,default-trigger = "phy0tx"; }; gpio_out_8 { label = "P8:orange:wifiConnect"; gpios = <&pio 0 8 0>; linux,default-trigger = "phy0assoc"; }; gpio_out_9 { label = "P9:green:wifiDetectUSB"; gpios = <&pio 0 9 0>; linux,default-trigger = "phy0radio"; }; gpio_out_10 { label = "P10:blue:cpuOnline"; gpios = <&pio 0 10 0>; linux,default-trigger = "cpu"; }; gpio_out_11 { label = "P11:white:Act"; gpios = <&pio 3 11 0>; linux,default-trigger = "activity"; }; gpio_out_0 { label = "P0:mmc0"; gpios = <&pio 0 0 0>; linux,default-trigger = "mmc0"; }; gpio_out_1 { label = "P1:disk-activity"; gpios = <&pio 0 1 0>; linux,default-trigger = "disk-activity"; }; gpio_out_3 { label = "P3:etherLink1gbps"; gpios = <&pio 0 3 0>; linux,default-trigger = "0.2:01:1Gbps"; }; gpio_out_6 { label = "P6:cpuled"; gpios = <&pio 0 6 0>; linux,default-trigger = "netdev"; }; }; }; }; }; addDTBTest2.dts
  5. I am using legacy Armbian_5.14_Orangepi2_Ubuntu_xenial_3.4.112.7z and a Logitech C110 and I cannot set some params. However I can set this in my PC under x86_64 3.13.0-91-generic. Below is the output of v4l2-ctl in orangepi2. Any idea? $ v4l2-ctl -l --verbose VIDIOC_QUERYCAP: ok error 22 getting ctrl Brightness error 22 getting ctrl Contrast error 22 getting ctrl Saturation error 22 getting ctrl Hue error 22 getting ctrl White Balance Temperature, Auto error 22 getting ctrl Gamma error 22 getting ctrl Power Line Frequency error 22 getting ctrl White Balance Temperature error 22 getting ctrl Sharpness error 22 getting ctrl Backlight Compensation exposure_auto (menu) : min=0 max=3 default=3 value=3 exposure_absolute (int) : min=2 max=5000 step=1 default=312 value=312 exposure_auto_priority (bool) : default=0 value=1 pan_absolute (int) : min=-72000 max=72000 step=3600 default=0 value=0 tilt_absolute (int) : min=-54000 max=54000 step=3600 default=0 value=0 zoom_absolute (int) : min=1 max=2 step=1 default=1 value=1
  6. Hello, I've been using an OrangePi PC with legacy distribution for a long time as a mini-server, it worked Ok except for some seemingly random freeze. I'm using it with an unsupported monitor size (1600x1200), so I had a modded version, and I never updated the system files to avoid having to recompile. I'd like to update Armbian to the mainline kernel version, but I want to keep all my settings/additions/installed programs, so I'd prefer to NOT do a complete re-install. Is there a way to do an upgrade without losing everything?? If not, how can I keep track of all the modifications currently installed so I can re-install them? TIA
  7. I have a Renegade ROC-3328-CC board, and trying to get the touch to work on the touchscreen (Typical resistive Touch screen 3.5" HDMI HAT type screen). I'm using the Armbian_5.75_Renegade_Ubuntu_bionic_default_4.4.174_desktop.img, and everything is working except the touch on the screen. Does anyone have success with this combination? By reading through topics on the forum, it seems to me that I need to be on the mainline kernel (since it has fbtft and ads7846 drivers), but I'm not finding any packaged images using mainline that will support his board. Anyone have a mainline Image for the Renegade? I tried the Tinker images which are on Rockchip 3328, but they completely fail to boot. Only next step I'm seeing is to build a custom kernel, or try to backport the fbtft + ads7846.
  8. Hi. I want to run the desktop at a 800x600 resolution, to get better FPS at full screen gaming (HDMI screen). I fiddled with OpenGL, and it looks like I got a lot better FPS by just using glshim. Is there a known approach to getting 800x600 resolution? h3disp does not show 800x600 as an option. This is the Armbian Ubuntu Xenial image. Regards, Morten