Linux for RK3188 based TV boxes

[stlava]

Just heard from the developer, the WiFi chipset is the RK903. From the quick research I have done, it looks like it is equivalent to the Broadcom 40183 chipset. Now off to complete my troubleshooting.

Were you ever able to get wifi working? I'm struggling with it right now.

[6stringplayer]

Were you ever able to get wifi working? I'm struggling with it right now.

Unfortunately no. This problem is a bit outside of my skill level yet.

[sevo1984]

hdmi settings

I've been using 1.1.1 recovery config succesfully for quite some time. Apart from wifi, everything is working just fine. Then tried a bit of experimenting to optimize it for my device and get wifi working - without success so far. In this process, I encountered an interesting issue. The only way to boot up linux is with hmdi mirroring on (that is to use original hdmi settings from mmm123's config). Tried all other combinations, won't boot. To add to the puzzle, linux dmesg indicates that lcdc1 is used as primary display and lcdc0 as external. Judging by device specification (“mk908” clone) it should be other way round. Indeed, Anroid dmesg shows that lcdc0 is used as primary display and lcdc1 not used at all! Any ideas? Many thanks! G

[no_spam_for_me]

static IP at ethernet

@mmm123
Do your kernel 1.1.1 e.g. from "dx05_nand_debian_1.1.1" works with static IP (instead of dhcp because of problem) at ethernet at K-R42 old rev (1332)?

[mmm123]

@mmm123
Do your kernel 1.1.1 e.g. from "dx05_nand_debian_1.1.1" works with static IP (instead of dhcp because of problem) at ethernet at K-R42 old rev (1332)?

Kernel has nothing to do with IP, but if you ask it like this - yes - you can configure static IP. It is done in /etc/network/interfaces
Replace
iface eth0 inet dhcp
with something like this:
iface eth0 inet static
address 192.168.1.10
netmask 255.255.255.0
gateway 192.168.1.1

eventually you can add:
pre-up ifconfig eth0 hw ether 00:00:00:12:34:56

[no_spam_for_me]

OK, THX and the important point is "Ethernet" because of the fu**ing RTL8201F
and if your kernel support it, it seems so, it is at the moment the only working kernel for that...

[no_spam_for_me]

From the "Picuntu on T-R42 - support for LAN/WiFi" thread

It is not likey alligment problem, because same driver works perfectly on older hardware (e.g K-R42 V1 and dx05).

Means K-R42 V1 the PCB TN-BX09_V2.0 (1321)?
For the Jesurun DX05 I can't find a pcb-picture
Because I have a TN-BX09_V2.1(1332) with the "IMG M1206IG 1330" instead of the "IMG M1201IG 1246"...

[mmm123]

From the "Picuntu on T-R42 - support for LAN/WiFi" thread


Means K-R42 V1 the PCB TN-BX09_V2.0 (1321)?
For the Jesurun DX05 I can't find a pcb-picture
Because I have a TN-BX09_V2.1(1332) with the "IMG M1206IG 1330" instead of the "IMG M1201IG 1246"...

These "IMG M1206IG 1330" and "IMG M1201IG 1246" should be passive elements. I doubt they cause any problem (unless they are broken, but you say it works with android)

BTW my DX05 is TN-BX09_V2.1 and it uses IMG M1201IG 1246

[enrique66_35]

OK, THX and the important point is "Ethernet" because of the fu**ing RTL8201F
and if your kernel support it, it seems so, it is at the moment the only working kernel for that...

Please report back if you get working ethernet with mmm123's image.

I tried it on a t-r42 (same ethernet chip) and could not get internet connection to download desktop packages so gave up on it.
Thanks.

[no_spam_for_me]

parameter for "Recovery image"

Recovery image:

http://data.a41z.net/X9fG54/dx05_boot_from_sd_recovery_1.1.1.7z

Just install it to recovery partition and reboot into recovery mode, it will boot from SD/USB with label linuxroot

@mmm123
To use this solution do I have to modify my actually parameter?

Generally for my actually flashed android (flash organisation) I've to use this part from my actually parameter at CMDLINE:

mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x00008000@0x00004000(kernel),0x00008000@0x0000C000(boot),0x00008000@0x00014000(recovery),0x000C0000@0x0001C000(backup),0x00040000@0x000DC000(cache),0x00400000@0x0011C000(userdata),0x00002000@0x0051C000(kpanic),0x00100000@0x0051E000(system),-@0x0063E000(user)

But what's about this part at CMDLINE:

console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000

Because for "Full installation in internal nand flash" and "Running linux from SD card or USB device"you use at CMDLINE:

initrd=0x62000000,0x00800000 root=LABEL=linuxroot init=/sbin/init

Do I have to delete
console=ttyFIQ0
and add
root=LABEL=linuxroot
and what's about the different init ("init=/sbin/init" instead off "init=/init") ???

[mmm123]

Because for "Full installation in internal nand flash" and "Running linux from SD card or USB device"you use at CMDLINE:

initrd=0x62000000,0x00800000 root=LABEL=linuxroot init=/sbin/init

Do I have to delete
console=ttyFIQ0
and add
root=LABEL=linuxroot
and what's about the different init ("init=/sbin/init" instead off "init=/init") ???

root=LABEL=linuxtoot tells initrd image (boot.img or buit into recovery.img) where to look for root filesystem - in this case it looks in localy attached storages - like SD cards, USB flash or USB HDD for partition with label "linuxroot" and boots system from there.
For "run from nand" version, this is not necessary, as initrd(boot.img) knows that root partition is in specific part in NAND (e.g 3rd NAND partition if I remember correctly) - and NAND is formatted and partitioned while installing system.
about "console=ttyFIQ0" if you know how to connect this type of console to your board - leave it - it will be usefull, if you don't (most likely) then remove it.
init=/init or init=/sbin/init - it tells kernel where to look for "init" into initrd (boot.img).
Sometimes it is shell script located into root directory (/), sometimes it is binary located into /sbin/

[no_spam_for_me]

I think we get the next little misunderstanding
1.) I generally know what the "root=LABEL=linuxroot" means. Do your solution need it at CMDLINE?
2.) I generally know what the "init=..." means. But I think the android needs "init=/init". But what do you need, or do you handle it fix in your "recovery.img" instead of reading it from the parameter CMDLINE (perhaps because of your own including "boot.img" inside the "recovery.img") so I can leave the "init=/init" at the parameter CMDLINE?
3.) "about "console=ttyFIQ0" if you know how to connect this type of console to your board - leave it - it will be usefull, if you don't (most likely) then remove it." does this type means UART (Serial-to-TTL converter)?
If yes: I don't use it, but if it doesn't matter to your booting, I will leave it at CMDLINE (perhaps for future use )...

greetings

[no_spam_for_me]

Ok, I've unpack your recovery.img and find the init-file at / (and a softlink at /sbin/)...
In the init-file I find

for x in $(cat /proc/cmdline); do
            case $x in
            init=*)
                        init=${x#init=}
                        ;;
            root=*)
                        ROOT=${x#root=}
                        case $ROOT in
                        LABEL=*)
                                   ROOT="${ROOT#LABEL=}"

1.)
So, at CMDLINE, I think
"init=/init" is ok and
"root=LABEL=linuxroot" is a must to have (if the volume-label is "linuxroot")...
Correct???

2.) And it seems so, you handle the device viy UUID, correct?

Greetings

[mmm123]

this initrd (into recovery.img) is what initramfs-tools (debian/ubuntu package) generates.
It has just few modifications to insert several modules (like framebuffer console)

about kernel command line
when you use kernel.img+initrd.img to boot - android or linux, kernel command line is provided by bootloader
when you use recovery.img, kernel command line is not provided by bootloader, so it has to be built into kernel.

In both cases you need kernel command line. Of course if you modify initrd to ignore command line or use static parameters, then you can go without kernel command line, except first part (initrd=0x62000000,0x00210000), which tells kernel where initrd imaneg is (this is memory address where bootloader loads initrd from flash, and auto-discovery option into kernel is bugged so parameter must be provided manually)

[no_spam_for_me]

when you use recovery.img, kernel command line is not provided by bootloader, so it has to be built into kernel.

too late

Step 1
parameter with "root=LABEL=linuxroot" at CMDLINE
and "dx05_sd_linux_1.1.1_recovery.img" flashed...
a) android start up correctly...
b) adb shell cat /proc/cmdline -> "... root=LABEL=linuxroot ..."
c) adb reboot recovery -> linux kernel start up till {initramfs} (and detects my wireless keyboard)



Next step will be a file-system at USB...



PS: -------------------

Step 2
Linuxium's Linux root file system (Ubuntu)

Fine-tuning like Ethernet and static IP follows...