Jump to content

Search the Community

Showing results for tags 'lime2'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK Pi 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP


Skype


Github


Discord


Location


Interests

  1. I’ve recently ran into this where whenever I power up my Olimex Lime 2 eMMC with Armbian, it powers down before it propretly starts. Here’s what I managed to observe so far. Armbian version …em, latest at this stage, I guess, it’s a bit hard to check exactly right now press power on button, it powers on via HDMI I see the Armbian boot logo some early boot messages pop up and ends with “Starting kernel ....” (Loading init Ramdisk seems OK, loading of device tree also OK) it goes back to black screen with Armbian logo and the _ blinking for a very short time I see an error with a long number and saying something about ”rebooting again” it powers down by itself I tried to reboot with and without the external SATA disk attached as well as other with the battery plugged in or not, and everything leads to the same result.
  2. Greetings from USA, my name is Freddy Love and i'm new to Armbian and this forum. Currently i'm using a Lime2 no internal storage with Bullseye CLI on the SD. My pau06 works great, but want to use for small server and would obvi prefer to be hardwired in. Any help would be much appreciated. I'm still going thru everything I can read. My email is freddylovesart@protonmail.com and @freddylove@fosstodon.org // thx in advance. Sincerely, -fl
  3. Hello, I've a olimex lime2 rev.K board and i installed Armbian 20.08.0-trunk (Bionic-minimal) which is having ... Kernel Version : 5.4.51-sunxi (branch -> next ) u-boot : v2020.04 I've serial console on which I can see that board boot correctly. I want the board to show information and login prompt on HDMI output...but HDMI losses on boot when kernel loads, Part way through Kernel load looses monitor sync signal and monitor goes blank. Can sometimes get back for short period (5-10 seconds) if unplug/plug HDMI cable but still looses sync and monitor doesn’t detect that anything is connected. I spent a lot of time on forums, my board is powered with power adapter and My monitor is a TV. Board is booted via emmc memory. I've also seen on posts that resolution could be the problem, I've change in /boot/armbianEnv.txt: console=display disp_mode=1920*1080p60 to 1280*1024p60 save it and reboot not working... Sorry for my question if it has already been solved or if it is a silly question too. May me some one point me to the related docs or some pointer to move further. I appreciate any support here ! Regards. Suvhm
  4. Hi All, I'm trying to enable SPI2 on Olinuxino LIME2 board following the instruction of Armbian doc, and the README.sun7i... in the /boot/dtb/overlay directory. It seems I have to enable an spi2 device, but the overlay for SPI2 of sun7i is not present. The related section of armbianEnv.txt is the following: overlays=i2c1 spi-spidev uart2 uart3 uart4 uart5 uart6 uart7 param_spidev_spi_bus=2 param_spidev_max_freq=10000000 What I'm doing of wrong? Thanks in advance PaoloC
  5. Hello, I have a design with old but cheap Allwinner A20 processor. At the boot time, u-boot keeps rebooting just after reaching the below line (just after DRAM: 1GiB): U-Boot SPL 2019.07 (Oct 13 2020 - 17:36:08 +0300) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2019.07 (Oct 13 2020 - 17:36:08 +0300) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Olimex A20-OLinuXino-LIME2-eMMC I2C: ready DRAM: 1 GiB I even tried ready images from internet, alghtough some did not reboot countinlusly, but they stuck at the same place (line: DRAM: 1 GiB). BTW, in our PCB, we did not use "SD card detect" mechanical pin, so I already changed the U-boot CONFIG_MMC0_CD_PIN="PH1" to ="" before compile (otherwise it stuck in u-boot SPL and even did not go to u-boot). I treid to play with U-boot settings to have debugging message, but nothing changed. Can anyone give a clue? can the problem be a hardware issue? On internet I saw that I should see something like this, after DRAM line: ..... I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 In: serial .... Thank you
  6. Hello, Earlier on this week I decided to upgrade the kernel and the DTBs on my Armbian cluster (quite a few different boards but all of them based on Allwinner A20) from buster-next-5.92 to buster-current-20.08.2. Having successfully completed the upgrade on several other servers, I moved on to the lime2 one - which promptly failed to come back up after the reboot. Connecting the serial console shows u-boot doing its thing without issues and the kernel beginning to boot, producing normal messages - only to suddenly freeze. When exactly the freeze occurs varies, sometimes it even happens halfway through outputting a message line - but it is definitely before the handover to init and I think it's also before initramfs kicks in. Having poked around a bit, I have narrowed the problem down to the DTB update. If I have /boot/dtb point to dtb-4.19.62-sunxi, the system comes up fine - even with the new kernel. On the other hand, as soon as I symlink it back to dtb-5.8.6-sunxi the kernel hangs. BTW. I do not use any overlays and apart from the verbosity increase I do not think I have changed anything in armbianEnv.txt since system installation. In fact, let me just post it here: verbosity=7 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun7i-a20 rootdev=UUID=REDACTED rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Any ideas how I can debug this further? If you need any more information, let me know.
  7. Hi everyone, I am trying to setup a new armbian buster system on a lime2 eMMC board. Not currently using the eMMC. Wanted to have a regular armbian install on the sd card, and then an encrypted root partition on an SSD attached with SATA. I've done this before by loosely following this post If I setup a system without using dropbear to unlock the root partition and boot, and use a keyboard to enter the password to unlock it instead, that works fine. However, if I install the `dropbear-initramfs` package, copy my ssh keys to /etc/dropbear-initramfs/authorized_keys and then do `update-initramfs -u` the bootloader doesn't seem to get past the initial stages. Here is some of the output from the bootup leading me to believe something went wrong in updating the kernel image and the bootloader on the SD card: Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3789 bytes read in 2 ms (1.0 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 250 bytes read in 2 ms (122.1 KiB/s) 142269496 bytes read in 704 ms (17.3 MiB/s) 7163856 bytes read in 396 ms (17.3 MiB/s) Found mainline kernel configuration 42254 bytes read in 7 ms (5.0 MiB/s) 5532 bytes read in 5 ms (1.1 MiB/s) Applying kernel provided DT fixup script (sun7i-a20-fixup.scr) ## Executing script at 44000000 ## Loading init Ramdisk from Legacy Image at 43300000 Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 14226432 Bytes = 13.6 MiB Load Address: 0000000 Entry Point: 0000000 Verifying Checksum ... Bad Data CRC Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... A bunch of messages flash by which I couldn't get on camera, and then it hangs with something along the lines of `autload with TFTPGET...` From what I understand, the ramdisk image is corrupted and u-boot falls back to trying to download it from the network somehow. Is this ramdisk the `boot.scr` file? The interesting thing is if I downgrade the kernel, by downgrading the packages `linux-image-current-sunxi` and `linux-dtb-current-sunxi` to version 20.05.0-trunk instead of 20.05.3 then I can successfully install `dropbear-initramfs` and unlock the system via ssh. Does anyone have any ideas of how this can be fixed? I can provide more info if need be. Like how I setup the encrypted system. Or I can find my serial to usb cable to try and get more output Thanks
  8. Hello Team, I am worked on Olimex Lime2 rev.G2 board but now olimex start delivering Rev.K board. I used the same Armbian Rev 5.35 image which is having kernel version (4.13.16-sunxi) & u-boot version v2017.09. On Rev.G2 Ethernet speed was as expected but in rev.K it is not working. By default board booted and comes with ethernet speed 100Mbps, but in this case Ethernet is not working (DHCP server unable to assign ipv4 address to eth0). Later i reduce the eth0 speed to 10Mbps it start working as expected but spped is 10Mbps Some more info about the ethernet issue which will help to understand the issue more clearly - Any help is really appreciated. Thank You ! Suvhm
  9. I have had similar issues what somebody had on this forum but I cannot post reply because the topic is closed. But I found solution. You need to downgrade u-boot with following commands. For Olimex Micro: apt-get install linux-u-boot-next-micro=5.60 Tested on ARMBIAN 5.60 stable Ubuntu 18.04.3 LTS 4.19.84-sunxi For Olimex Lime2: apt-get install linux-u-boot-lime2-emmc-next=5.30 Tested on Ubuntu Bionic with Armbian Linux 4.19.81-sunxi
  10. Hello community, I'm looking to build an internet cube (https://internetcu.be/). Basically, the project uses an A20-OLinuXino-LIME2 but I'm looking to see if a better armbian could do the job. Prerequisites are quite similar to a NAS : quality, stability, performance, minus 80$, Gibabit LAN, SATA, USB. So I have 4 models in mind: - Banana pro - Banana pi - A20-OLinuXino-LIME2 - Espressobin Which one is best suited and/or do you have other models in mind?
  11. I am trying to enable Winstar TFT display on Olimex Lime2 board under the kernel 5.4. Display spec is here: https://www.winstar.com.tw/products/tft-lcd/ips-tft/lvds-tft.html Up to the day we've been using the legacy kernel 3.4 and the display worked fine -- the u-boot was compiled with the settings (CONFIG_VIDEO_LCD_MODE, CONFIG_VIDEO_LCD_POWER etc) suggested here: When I try to use the same settings in the mainline sources of armbian, the display does not work. I've enabled backlight with a DTS overlay and the backlight works but the display stays blank. Here is the output of dmesg: [ 2.846134] printk: console [ttyS0] enabled [ 2.851759] sun4i-drm display-engine: bound 1e00000.display-frontend (ops 0xc0a8c028) [ 2.851861] sun4i-drm display-engine: bound 1e20000.display-frontend (ops 0xc0a8c028) [ 2.852303] sun4i-drm display-engine: bound 1e60000.display-backend (ops 0xc0a8b868) [ 2.852610] sun4i-drm display-engine: bound 1e40000.display-backend (ops 0xc0a8b868) [ 2.853113] sun4i-drm display-engine: No panel or bridge found... RGB output disabled [ 2.853130] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 0xc0a8a590) [ 2.853543] sun4i-drm display-engine: No panel or bridge found... RGB output disabled [ 2.853559] sun4i-drm display-engine: bound 1c0d000.lcd-controller (ops 0xc0a8a590) ... [ 2.892843] fb0: switching to sun4i-drm-fb from simple And these are u-boot settings: CONFIG_LCD_IF_LVDS=y CONFIG_VIDEO_LCD_PANEL_LVDS=y CONFIG_VIDEO_LCD_MODE="x:1280,y:800,depth:24,pclk_khz:71000,le:70,ri:90,up:10,lo:13,hs:1,vs:1,sync:3,vmode:0" CONFIG_VIDEO_LCD_POWER="PH8" CONFIG_VIDEO_LCD_BL_EN="PH7" CONFIG_VIDEO_LCD_BL_PWM="PB2" I am at loss and any suggestions will be hightly appreciated. Thank you!
  12. Hello all, If i detach battery all works ok. With attached battery system reboots instead of shutting down. Anyone experiencing this issue again with 5.4.21 kernel? Is there a workaround to solve it, maybe in u-boot or somewhere else? Armbian 20.05.0-trunk built from source Thank you
  13. hi all, I've been running into an issue where the kernel starts throwing error messages (https://pastebin.com/bmPJPeq0), the board becomes very slow and the cpu load goes to 11 and stays there. This seems to happen when I change the CPU freq using armbian-config to anything lower than 528MHz. Any ideas how I could resolve this?
  14. Hello guys and gals Can anyone help me what information to add in boot.cmd file to make it bootable from SSD on SATA port? I found some examples but they are from 2014 and the information in my boot.cmd file looks slightly different from what is posted in the past. I'm using the latest Buster Server image with 4.19 kernel. By the way is it a good idea to enable TRIM for the SSD? I saw some options in YouTube how to enable TRIM, but just want to ask for opinion of people with SSD drives, who already managed to boot from SATA with SSD. setenv load_addr "0x44000000" setenv overlay_error "false" # default values setenv verbosity "1" setenv console "both" setenv disp_mem_reserves "off" setenv disp_mode "1920x1080p60" setenv rootfstype "ext4" setenv docker_optimizations "on" setenv rootdev "UUID=356XXXX-XXX-XXXX-XXXX-XXXXXXXXXX" # Print boot source itest.b *0x28 == 0x00 && echo "U-boot loaded from SD" itest.b *0x28 == 0x02 && echo "U-boot loaded from eMMC or secondary SD" itest.b *0x28 == 0x03 && echo "U-boot loaded from SPI" # get PARTUUID of first partition on SD/eMMC it was loaded from # mmc 0 is always mapped to device u-boot (2016.09+) was loaded from if test "${devtype}" = "mmc"; then part uuid mmc ${devnum}:1 partuuid; setenv devnum ${mmc_bootdev} setenv rootdev "/dev/sda${mmc_bootdev}p1" fi echo "Boot script loaded from ${devtype}" if test -e ${devtype} ${devnum} ${prefix}armbianEnv.txt; then load ${devtype} ${devnum} ${load_addr} ${prefix}armbianEnv.txt env import -t ${load_addr} ${filesize} fi if test "${logo}" = "disabled"; then setenv logo "logo.nologo"; fi if test "${console}" = "display" || test "${console}" = "both"; then setenv consoleargs "console=ttyS0,115200 console=tty1"; fi if test "${console}" = "serial"; then setenv consoleargs "console=ttyS0,115200"; fi setenv bootargs "root=${rootdev} rootwait rootfstype=${rootfstype} ${consoleargs} hdmi.audio=EDID:0 disp.screen0_output_mode=${disp_mode} panic=10 consoleblank=0 loglevel=${verbosity} ubootpart=${partuuid} ubootsource=${devtype} usb-storage.quirks=${usbstoragequirks} ${extraargs} ${extraboardargs}" if test "${disp_mem_reserves}" = "off"; then setenv bootargs "${bootargs} sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16"; fi if test "${docker_optimizations}" = "on"; then setenv bootargs "${bootargs} cgroup_enable=memory swapaccount=1"; fi load ${devtype} ${devnum} ${ramdisk_addr_r} ${prefix}uInitrd load ${devtype} ${devnum} ${kernel_addr_r} ${prefix}zImage if test -e ${devtype} ${devnum} "${prefix}.next"; then echo "Found mainline kernel configuration" load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile} fdt addr ${fdt_addr_r} fdt resize 65536 for overlay_file in ${overlays}; do if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/overlay/${overlay_prefix}-${overlay_file}.dtbo; then echo "Applying kernel provided DT overlay ${overlay_prefix}-${overlay_file}.dtbo" fdt apply ${load_addr} || setenv overlay_error "true" fi done for overlay_file in ${user_overlays}; do if load ${devtype} ${devnum} ${load_addr} ${prefix}overlay-user/${overlay_file}.dtbo; then echo "Applying user provided DT overlay ${overlay_file}.dtbo" fdt apply ${load_addr} || setenv overlay_error "true" fi done if test "${overlay_error}" = "true"; then echo "Error applying DT overlays, restoring original DT" load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile} else if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/overlay/${overlay_prefix}-fixup.scr; then echo "Applying kernel provided DT fixup script (${overlay_prefix}-fixup.scr)" source ${load_addr} fi if test -e ${devtype} ${devnum} ${prefix}fixup.scr; then load ${devtype} ${devnum} ${load_addr} ${prefix}fixup.scr echo "Applying user provided fixup script (fixup.scr)" source ${load_addr} fi fi bootz ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r} else echo "Found legacy kernel configuration" load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}script.bin bootz ${kernel_addr_r} ${ramdisk_addr_r} fi
  15. Hi I' am trying to use the SPI device on the Olimex Lime 2 board but i am having a lot of trouble. Basicaly i do not see the spidev on the device three. i am using the last image (Armbian_5.91_Lime2_Debian_buster_next_4.19.59), i have activated the overlays and that is the my armbianEnv.txt file verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun7i-a20 rootdev=UUID=3563b9df-bd15-4366-b897-da0963dfd5a0 rootfstype=ext4 overlays=spi-spidev usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Where am i wrong? Thanks in advance for any kind of help
  16. Hi Guys, After a long time after the release Linux kernel 4.x I want use the I2S on Lime2 (Armbian Stretch kernel 4.14.14), but I2S interface did not work. I was add activation of overlays i2s0 and i2s1 into/boot/armbianEnv.txt root@lime2:~# cat /boot/armbianEnv.txt verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun7i-a20 rootdev=UUID=dcf7af80-8026-4e99-870f-f0d35f926063 rootfstype=ext4 overlays=i2s0 i2s1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u After reboot I can't see I2S interfaces... root@lime2:~# aplay -l aplay: device_list:270: no soundcards found... root@lime2:~# lsmod | grep snd snd_soc_core 118784 1 sun4i_i2s snd_pcm_dmaengine 16384 1 snd_soc_core snd_pcm 65536 3 sun4i_i2s,snd_pcm_dmaengine,snd_soc_core snd_timer 24576 1 snd_pcm snd 45056 3 snd_timer,snd_soc_core,snd_pcm soundcore 16384 1 snd I2S really supported in Mainline on A20?
  17. Hardware setup :: Olimex Lime 2 Rev.k + 7" LCD + 5V power supply through the power jack. No battery is connected to the lime 2 board. Problem :: when the board boots up, the xfce power manager shows that the Battery is connected and it's in charging mode. The current charge value of the battery changes randomly like 92%, 56% and etc. When it reaches 0% the board will shut down. It completes the shut down procedure. The following is the terminal output, to find the battery status. Even though the battery is not connected you can observe that it returns the Voltage and reports that the battery is present root@olinuxino:~# cat /sys/class/power_supply/axp20x-battery/voltage_now 2865000 root@olinuxino:~# cat /sys/class/power_supply/axp20x-battery/present 1 root@olinuxino:~# cat /sys/class/power_supply/axp20x-battery/online 1 root@olinuxino:~# cat /sys/class/power_supply/axp20x-battery/capacity 0 root@olinuxino:~# cat /sys/class/power_supply/axp20x-battery/capacity 0 root@olinuxino:~# cat /sys/class/power_supply/axp20x-battery/online 1 root@olinuxino:~# cat /sys/class/power_supply/axp20x-battery/voltage_now 2879000 root@olinuxino:~# [ OK ] Stopped Unattended Upgrades Shutdown. [ OK ] Stopped target Timers. [ OK ] Stopped target Sound Card. ..... ..... ..... The board shut down as soon as the capacity reached 0%. I have three Lime 2 Rev.K boards, the behaviour is seen in all. What could be the reason for this behavior? Should I disable xfce power manager? What are the other problems with disabling xfce power manager? Can you please tell me the steps to disable the xfce4-power-manager. Note : I am using the Armbian_Ubuntu_bionic_5.1.12 OS with Lime 2 rev.K. It doesn't happen with Armbian_5.72.1 Debian_stretch. Attachments:: AXP209 Charging LED is ON - Even though the battery is not connected to the board, the charging LED is ON. The LED is not continuously ON, it blinks in random order. xfce4 Power manger - Image of xfce4 Power manger which shows that battery is connected even though its not physically connected.
  18. I am using Olimex Lime 2 Emmc Rev.k for a project. One of the Boards shuts down randomly. Its not a freeze or a sudden power down of the board. The board undergoes a complete shut down procedure. I checked the log entries in /var/log/syslog log file. There is a entry of board going to shut down but I couldn't find the reason for shut down. Is there a way to find out if the board got shut down because of the Power-button press, shutdown command from a SSH client, shutdown because of temperature or shutdown because of under voltage ? Is there a log file i can check to find the reason for shutdown?
  19. I flashed a fresh card with the LIME2 image. On boot, the bootloader loads. Once the kernel starts to load, I lose the display on HDMI. It is being powered over mini-usb, from a powered hub. No additional peripherals. It looks like the system is running (based on the Ethernet), but HDMI isn't displaying (the monitor says no signal). I'm able to connect over ssh.
  20. Hi, Lime2 A20 not even detecting mini usb ethernet, which was working perfectly fine on 3.xx. Manfu: Netgear USB: USB 2.0 Ethernet Adapter P/N: 322-10167-01 dmesg doesn't even list the device. Could board's port be damaged? I tired usb port with usb ethernet, it lists as: I'm using arbmian Ubuntu 18.04 with beta packages. Thanks
  21. hey guys, Using legacy kernel I have trouble having dual output on LCD and HDMI. I tried to have a cloned dual output (same framebuffer for both) : [disp_init] disp_init_enable = 1 disp_mode = 4 screen0_output_type = 1 screen0_output_mode = 6 screen1_output_type = 3 screen1_output_mode = 4 fb0_width = 0 fb0_height = 0 fb0_framebuffer_num = 2 fb0_format = 10 fb0_pixel_sequence = 0 fb0_scaler_mode_enable = 0 fb1_width = 1024 fb1_height = 600 fb1_framebuffer_num = 2 fb1_format = 10 fb1_pixel_sequence = 0 fb1_scaler_mode_enable = 0 ... Also tried with 2 framebuffers : [disp_init] disp_init_enable = 1 disp_mode = 2 screen0_output_type = 1 screen0_output_mode = 6 screen1_output_type = 3 screen1_output_mode = 4 fb0_width = 0 fb0_height = 0 fb0_framebuffer_num = 2 fb0_format = 10 fb0_pixel_sequence = 0 fb0_scaler_mode_enable = 0 fb1_width = 0 fb1_height = 0 fb1_framebuffer_num = 2 fb1_format = 10 fb1_pixel_sequence = 0 fb1_scaler_mode_enable = 0 ... On both case when booting the signal is first on HDMI until kernel starts. Then the signal goes to LCD and HDMI turns off. Any hint? Full fex below :
  22. Hi there, I am trying to download the lime2 legacy image : https://www.armbian.com/olimex-lime-2/#kernels-archive But the link is dead (error 404). Any chance to get this back up? Or can I use another legacy image and just change the script.bin or is there other things to modify? Thanks Edit : I just found the image on olimex website : ftp://staging.olimex.com/Allwinner_Images/A20-OLinuXino/2.legacy_images_kernel_3.4.x/
  23. Hello, I configured 2 armbian on sd card and the configuration of the i2c is the same in armbianEnv.txt. Plattform Olimex-Lime2 A20 verbosity=1 logo=disabled console=both disp_mode=1280x1024p50 overlay_prefix=sun7i-a20 rootdev=UUID=194e9f9a-826b-4644-9f2f-4ef388277816 rootfstype=ext4 overlays=i2c1 i2c2 uart3 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u as you see, I confiugred the overlays. But on one image I get: #image with desktop sudo i2cdetect -l i2c-3 i2c mv64xxx_i2c adapter I2C adapter i2c-1 i2c mv64xxx_i2c adapter I2C adapter i2c-2 i2c mv64xxx_i2c adapter I2C adapter and booting the other image I get # headless image sudo i2cdetect -l i2c-3 i2c mv64xxx_i2c adapter I2C adapter i2c-1 i2c mv64xxx_i2c adapter I2C adapter i2c-2 i2c mv64xxx_i2c adapter I2C adapter i2c-0 i2c sun4i_hdmi_i2c adapter I2C adapter so I get an aditional device for i2c-0. I don't understand what's happening. What could cause this effect? Or better: What must happen, that the i2c-0 does not appear in the list. One more info: The first image has a runing desktop and the second one in headless. Maybe this has something to do with the issue? Can someone give me a pointer to understand this. Btw. both versions work perfekt: i2cdetect -y 2 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: 20 21 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- i2cdetect -y 3 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: 20 21 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- The 0x68 is a RTC which is configured. So everything is OK, but I drives me crazy not to understand what I've done "wrong". Can someone give me a pointer? Thanks for all help.
  24. Hi all! I have an Olimex Olinuxino-Lime2-4GB A10 cpu based dev board and I have installed Armbian on an SD card. Everything works fine, except when trying to compile some drivers for the wifi dongle that I want to use. The dongle has an RTL8188CUS chip, and I also have another dongle with an RTL8192CU chip, and when following the instructions found here the compilation fails, because of the kernel headers missing. The instructions work fine on other distributions. Could someone help me figure out how to successfully compile the drivers? Where can I get the kernel headers? I really need these drivers for my project.
  25. Hi! I've been using Armbian on my a20 olinuxino lime2 board without issues for over a year now. Yesterday i decided to reflash the installation image onto the SD board. I've tried to flash it to different SD cards using the same method (SD card formatter + etcher), all of them booted but the SSH server always refuses the connection. Are there any workarounds to this?
×
×
  • Create New...