A10-OlinXino-LIME Custom Debian Image: See only cursor

[NoreSoft]

Hi together,

i have a problem. I use the A10-OlinXino-LIME with an A13-LCD4.3. At first I simply downloaded the Debian Image with kernel 3.4.90+ from here, run the change_display_a10_lime.sh and it worked.
But I had to compile a new kernel. I just exchanged the subfolders /lib/modules/ and /lib/firmware/ and the uImage file with my new compiled kernel and modules and everything worked fine.

Now I wanted to make a fresh install on a new SD-card. Because I allready changed the kernel and modules and the script.bin file (via the change_display-script), I found it easier to build everything as described in  these instructions and just use my own script.bin file and kernel config.

But unfortunately that does not work. (Which is quite strange, because it should be basically the same thing as before.) When I boot the board, I only see the cursor (as a big X) on the screen. The touch screen is btw working, i am able to move the cursor. I can change to a terminal via CTRL+ALT+F1 and normally login. But I don't have a clue, what is actually going wrong.

When I connect the UART with my computer, I see some errors in the boot process, but I am not able to understand them. Here is the last few lines with most of the errors:

Code Select Expand

[[36minfo[39;49m] Loading kernel module sw_ahci_platform.
ERROR: could not insert 'sw_ahci_platform': Unknown symbol in module, or unknown parameter (see dmesg)
[[36minfo[39;49m] Loading kernel module lcd.
[[36minfo[39;49m] Loading kernel module hdmi.
[[36minfo[39;49m] Loading kernel module ump.
ERROR: could not insert 'ump': Unknown symbol in module, or unknown parameter (see dmesg)
[[36minfo[39;49m] Loading kernel module disp.
[[36minfo[39;49m] Loading kernel module 8192cu.
ERROR: could not insert '8192cu': Unknown symbol in module, or unknown parameter (see dmesg)
[[36minfo[39;49m] Loading kernel module gpio-sunxi.
ERROR: could not insert 'gpio_sunxi': Unknown symbol in module, or unknown parameter (see dmesg)
[[36minfo[39;49m] Loading kernel module sunxi_cedar_mod.
ERROR: could not insert 'sunxi_cedar_mod': Unknown symbol in module, or unknown parameter (see dmesg)
[[36minfo[39;49m] Loading kernel module leds-sunxi.
libkmod: ERROR ../libkmod/libkmod-module.c:174 kmod_module_parse_depline: ctx=0xb7bbe008 path=/lib/modules/3.4.90+/kernel/drivers/leds/led-class.ko error=No such file or directory
libkmod: ERROR ../libkmod/libkmod-module.c:174 kmod_module_parse_depline: ctx=0xb7bbe008 path=/lib/modules/3.4.90+/kernel/drivers/leds/led-class.ko error=No such file or directory
ERROR: could not insert 'leds_sunxi': Unknown symbol in module, or unknown parameter (see dmesg)
[[36minfo[39;49m] Loading kernel module ledtrig-heartbeat.
ERROR: could not insert 'ledtrig_heartbeat': Unknown symbol in module, or unknown parameter (see dmesg)
[[36minfo[39;49m] Loading kernel module nand.
ERROR: could not insert 'nand': Unknown symbol in module, or unknown parameter (see dmesg)
[....] Activating lvm and md swap...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Checking file systems...fsck from util-linux 2.20.1
[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Mounting local filesystems...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Activating swapfile swap...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Cleaning up temporary files...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Setting kernel variables ...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Configuring network interfaces...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Cleaning up temporary files...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Setting up ALSA...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.

INIT: Entering runlevel: 2

[[36minfo[39;49m] Using makefile-style concurrent boot in runlevel 2.
[....] Starting enhanced syslogd: rsyslogd[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
Starting X display manager: slim.
[....] /etc/environment has been deprecated for locale information; use /etc/default/locale for LC_ALL="en_US.utf8" instead ...[?25l[?1c7[1G[[33mwarn[39;49m8[?25h[?0c [33m(warning).[39;49m
[....] Starting periodic command scheduler: cron[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c<4>Warning: this sunxi disp driver will see significant redesign.

[   16.271624] Warning: this sunxi disp driver will see significant redesign.
<4>Applications using /dev/disp directly will break.

[   16.293518] Applications using /dev/disp directly will break.
<4>For more information visit: http://linux-sunxi.org/Sunxi_disp_driver

[   16.313287] For more information visit: http://linux-sunxi.org/Sunxi_disp_driver
.
<4>[DISP] layer allocated: 0,101

[   16.327056] [DISP] layer allocated: 0,101
[....] Starting system message bus: dbus[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Loading cpufreq kernel modules...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone (none).
[....] CPUFreq Utilities: Setting performance CPUFreq governor...CPU0...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Starting network connection manager: NetworkManager[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Starting NTP server: ntpd[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
<4>[DISP] layer released: 0,101

[   18.444867] [DISP] layer released: 0,101
[....] <4>[DISP] layer allocated: 0,101

[   18.484696] [DISP] layer allocated: 0,101
Starting OpenBSD Secure Shell server: sshd[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
chmod: cannot access `/dev/cedar_dev': No such file or directory
chmod: cannot access `/dev/ump': No such file or directory
chmod: cannot access `/dev/mali': No such file or directory
[....] startpar: service(s) returned failure: rc.local ...[?25l[?1c7[1G[[31mFAIL[39;49m8[?25h[?0c [31mfailed![39;49m



Anyone has an idea what I could do?

Regards,
  David

[medarz]

The only thing I can think of, since there are several errors related to kernel modules, was if you erased the ones that came with the file system and replaced them with the ones generated during the creation of the SD.

These are the steps:

Code Select Expand

# rm -rf /mnt/sd/lib/modules/*
# cp -rfv linux-sunxi/out/lib/modules/3.4.90+/ /mnt/sd/lib/modules/

replace /lib/firmware folder with the generated /linux-sunxi/out/firmware
#rm -rf /mnt/sd/lib/firmware/
#cp -rfv linux-sunxi/out/lib/firmware/ /mnt/sd/lib/

Regards,

[NoreSoft]

Hi medarz,

thank you for your post.

I compared the uImage files and indeed they were different. I don't actually understand that. I did obtain the .conf file from the old system (the working one) by zcat /proc/config.gz > my_defconfig . And than build kernel and modules with that config. I don't know how this can go wrong.

But exchanging the kernel and the /lib/modules and /lib/firmware folder again did not help. I think the posted error messages went away though. I also recognized that the file uEnv.txt was missing and copied it, but still no success.

The fex-file is missing too but it is not neccessary, right?


Very mysterious... ;-)

[JohnS]

Isn't the fex still used with the kernel you're using?

John

[NoreSoft]

I think only the script.bin is used in any case.

The chip does not parse a textual version of a fex file, it gets cleaned and compiled by a fex-compiler.

from https://linux-sunxi.org/Fex_Guide#FEX_Description

To be sure I just tried it out. It did not help.

[NoreSoft]

Hi again,

found the time to look at this problem again.

I just compared the rootfs from the complete image to the rootfs from the "build your own"-image instructions. Unfortunately they differ. The first thing I see: The rootfs from the instructions does not contain a /bin folder. There is a lot more differences, which I don't understand.

What I ask myself:
1) Why are two different rootfs used?
2) Has anyone built an image with the rootfs from the instructions?

Hopefully I'll have some more time for this in the next days. I'll keep you up to date.

Regards,
  David