Linux for RK3188 based TV boxes

[linuxium]

Ok I understand you can't sleep until you figure it out , so there is clarification:
File you see in /lib/modules came from rootfs pakage e.g Linuxium's ubuntu or whatever you use as rootfs
the file in /lib/modules/3.0.36+/kernel/drivers/net/wireless/rtl8188eu comes from my package. These might be same maybe not. I recommend using one in /lib/modules/3.0.36+/kernel/drivers/net/wireless/rtl8188eu, as it is for sure comes from same kernel source as kernel.

FYI the files in /lib/modules in my RFS are the Android modules - they are there for compatibility with some of my earlier work however they are not required in your circumstances. The Linux modules should be used in preference to the Android ones as mmm123 says.

[no_spam_for_me]

FYI the files in /lib/modules in my RFS are the Android modules - they are there for compatibility with some of my earlier work however they are not required in your circumstances. The Linux modules should be used in preference to the Android ones as mmm123 says.

THX
I figure it out by my self
I test the 'sudo insmod /lib/modules/8188eu.ko' and I see it at lsmod as wlan or wifi but not as 8188eu and it don't work ...

[no_spam_for_me]

partitions

Ok, perhaps I'm on the wrong way, but your kernel at recovery is able to boot
- /dev/sda
- /dev/mmcblk0
If I use partitions it did not work???

And I don't understand why?
I unpack your recovery.img with 'Android Image Kitchen v1.8' so I get the kernel and the ramdisk.

If I have a look at the '\init' I find out that you
1.) looking at '/proc/cmdline' for 'root' and set the ROOT=/dev/disk/by-label/${value#LABEL=} (after you set it with LABEL and after you have a look at '\')
2.)
maybe_break mount
log_begin_msg "Mounting root file system"
. /scripts/${BOOT}
parse_numeric ${ROOT}
maybe_break mountroot
mountroot
log_end_msg
(and BOOT is only set if '/dev/nfs' in the '/proc/cmdline')

and at 'scripts\local-premount\fixrtc' you also look for 'root'...

with an extract at shell both variables seems to be good, so I don't understand way it only work at sda and mmcblk0 instead of partitions (and I thought that I have run it at one of my beginning test at mmcblk0p1 too, but it seems so that this is a mistake...)

for x in $(cat /proc/cmdline); do
echo "x: "$x""
        case $x in
        init=*)
                init=${x#init=}
                ;;
        root=*)
                ROOT=${x#root=}
echo "ROOT: "$ROOT""
                case $ROOT in
                LABEL=*)
                        ROOT="${ROOT#LABEL=}"
echo "ROOT: "$ROOT""
                        # support any / in LABEL= path (escape to \x2f)
                        case "${ROOT}" in
                        */*)
echo "case at /"
                        if command -v sed >/dev/null 2>&1; then
                                ROOT="$(echo ${ROOT} | sed 's,/,\\x2f,g')"
                        else
                                if [ "${ROOT}" != "${ROOT#/}" ]; then
                                        ROOT="\x2f${ROOT#/}"
                                fi
                                if [ "${ROOT}" != "${ROOT%/}" ]; then
                                        ROOT="${ROOT%/}\x2f"
                                fi
                                IFS='/'
                                newroot=
                                for s in $ROOT; do
                                        newroot="${newroot:+${newroot}\\x2f}${s}"
                                done
                                unset IFS
                                ROOT="${newroot}"
                        fi
                        esac
                        ROOT="/dev/disk/by-label/${ROOT}"
echo "ROOT: "$ROOT""
                        ;;
                esac
        esac
done
echo "ROOT: "$ROOT""
 
 
for x in $(cat /proc/cmdline); do
        case ${x} in
        root=*)
                value=${x#*=}
 
                # Find the device node path depending on the form of root= :
 
                case ${value} in
                UUID=*)
                        ROOTDEV=/dev/disk/by-uuid/${value#UUID=}
                        ;;
                LABEL=*)
                        ROOTDEV=/dev/disk/by-label/${value#LABEL=}
                        ;;
                *)
                        ROOTDEV=${value}
                        ;;
                esac
        ;;
        fixrtc)
                BROKEN_CLOCK=1
        ;;
        esac
done
echo "ROOTDEV: "$ROOTDEV""

x: initrd=0x62000000,0x00800000
x: root=LABEL=linuxroot
ROOT: LABEL=linuxroot
ROOT: linuxroot
ROOT: /dev/disk/by-label/linuxroot
x: init=/sbin/init
ROOT: /dev/disk/by-label/linuxroot
ROOTDEV: /dev/disk/by-label/linuxroot

ls -al /dev/disk/by-label
total 0
drwxr-xr-x 2 root root  60 Jan  3 21:38 .
drwxr-xr-x 6 root root 120 Jan  3 21:02 ..
lrwxrwxrwx 1 root root   9 Jan  3 21:38 linuxroot -> ../../sda

If I put in the SD

ls -al /dev/mmc*
brw-rw---- 1 root disk 179, 0 Jan  3 21:36 /dev/mmcblk0
brw-rw---- 1 root disk 179, 1 Jan  3 21:36 /dev/mmcblk0p1

ls -al /dev/disk/by-label
total 0
drwxr-xr-x 2 root root  60 Jan  3 21:36 .
drwxr-xr-x 6 root root 120 Jan  3 21:02 ..
lrwxrwxrwx 1 root root  15 Jan  3 21:36 linuxroot -> ../../mmcblk0p1

Startup the device with this SD at {initramfs}
ls /dev/disk/by-label
lrwxrwxrwx 1 15 linuxroot -> ../../mmcblk0p1
drwxr-xr-x 5 100 ..
drwxr-xr-x 2 60 .

If I start up the device without a RFS and I plug sda and type 'init' at {initramfs} only errors...


PS: --------
Generally I identify the problem:
My first tries I do with a 4GB SD instead of the now used 32GB.
With 'sudo fdisk -l /dev/mmcblk0' at the 4GB I get

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1              63     7882751     3941344+   c  W95 FAT32 (LBA)

and actually it works with mmcblk0p1

=> ls -al /dev/mmc*
brw-rw---- 1 root disk 179, 0 Jan  4 00:22 /dev/mmcblk0
brw-rw---- 1 root disk 179, 1 Jan  4 00:22 /dev/mmcblk0p1
=> ls -al /dev/disk/by-label
total 0
drwxr-xr-x 2 root root  60 Jan  4 00:22 .
drwxr-xr-x 6 root root 120 Jan  4 00:22 ..
lrwxrwxrwx 1 root root  15 Jan  4 00:22 linuxroot -> ../../mmcblk0p1

At the 32GB first I try it with ext2 (System = LINUX) and then with FAT32 too, but if I remember correct, the System was W95 FAT32 without (LBA)...

I will figure it out tomorrow, but for to day, I can sleep

PPS:--------
No, the 4GB SD also starts with 'W95 FAT32' ... ???
No idea, what kind of problem it is at the 32GB...

[no_spam_for_me]

PPPS:
WinXP SP3
Generally writing the img with WinHex:

With CreateMini for >=1 partitions:
Everything is fine, if SD / USB is <=8GB (1,2,3 Partitions)
System (at 'sudo fdisk -l')
W95 FAT32
or
Linux (ext2 at CreateMini)
BUT with SD / USB >=16GB it doesn't work...

To reset the partition to 1 at <=8GB with e.g. 'HP USB Disk Storage Format Tool 2.2.3' or 'Rufus'
=> only boot to linux if e.g. Ext2Fsd is running (and detach, attach, detach USB/SD)

USB-16GB / SD-32GB no chance to boot up with a partition (only "hole" device with 'Win32 Disk Imager 0.9 binary')
(ok, I get it at the sd with 1 partition, but I can not remember what and how I made it and now because of the test it is away...)

MiniTool Partition Wizard 8.1.1 Server
SD-32GB
- (primary, fat32 (with ext no drive-letter possible))
- WinHex restore image...
- same procedure

USB-16GB "hole" device with 'Win32 Disk Imager 0.9 binary' and an existing backup
- sudo resize2fs /dev/sda
- copy image-file to it (FTP)
- sudo apt-get install gparted
- insert SD-32GB
- dash Gparted (5GB, primary, ext4, linuxroot)
- sudo dd bs=4M if=linuxium-ubuntu1204-desktop-rfs-BASIS.img of=/dev/mmcblk0p1
- sudo reboot
- detach USB
- same procedure ... fu** offffff

=> ls -al /dev/mmc*
brw-rw---- 1 179, 1 /dev/mmcblk0p1
brw-rw---- 1 179, 0 /dev/mmcblk0
=> ls -al /dev/disk/by-label
lrwxrwxrwx 1 15 linuxroot -> ../../mmcblk0p1
drwxr-xr-x 5 100 ..
drwxr-xr-x 2 60 .

[no_spam_for_me]

dmesg

Perhaps someone can have a look at it (and find helping information)...

What I'm wondering in is that first:

[    1.493087] msdos_partition..461... ==== Begin to parse sdcard-partition.  [mmc0]
[    1.493280] msdos_partition..530... ==== The sdcard has MBR. [mmc0]
[    1.493411] msdos_partition..543... ==== partition-1, size=30930944KB  [mmc0]
[    1.493552] msdos_partition..571... ==== main partition-1....[mmc0]
[    1.493683]  mmcblk0: p1

but later then:

[    1.942692] EXT4-fs (mmcblk0): error loading journal

Of course, because it is partitiontable !?!
This is my mount for the dmesg > ...

[   48.578371] EXT4-fs (mmcblk0p1): recovery complete
[   48.620529] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)

[mmm123]

Perhaps someone can have a look at it (and find helping information)...

What I'm wondering in is that first:

[    1.493087] msdos_partition..461... ==== Begin to parse sdcard-partition.  [mmc0]
[    1.493280] msdos_partition..530... ==== The sdcard has MBR. [mmc0]
[    1.493411] msdos_partition..543... ==== partition-1, size=30930944KB  [mmc0]
[    1.493552] msdos_partition..571... ==== main partition-1....[mmc0]
[    1.493683]  mmcblk0: p1

but later then:

[    1.942692] EXT4-fs (mmcblk0): error loading journal

Of course, because it is partitiontable !?!
This is my mount for the dmesg > ...

[   48.578371] EXT4-fs (mmcblk0p1): recovery complete
[   48.620529] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)

if you have running linux, use linux fdisk/cfdisk to partition USB drive, then use linux tools to format as ext4, and copy files there
btw missing journal should not be a problem since it is automatically fixed on boot.

[no_spam_for_me]

btw missing journal should not be a problem since it is automatically fixed on boot.

Yes of course, but not at mmcblk0 because that's the device and not a partition and because of that it is normal that the system could not find a journal at mbr but it is not normal, that the system seem to try to mount the mbr ...

I try it with GpartEd and

mkdir ~/img
sudo mount -o loop linuxium-ubuntu1204-desktop-rfs-BASIS.img ~/img
mkdir ~/sd
sudo mount -t ext4 /dev/sdb1 ~/sd
sudo cp -r -a ~/img/* ~/sd
sudo umount ~/sd
sudo umount ~/img
sudo tune2fs -L linuxroot /dev/sdb1

The dmesg was with GpartEd and

sudo dd bs=4M if=linuxium-ubuntu1204-desktop-rfs-BASIS.img of=/dev/sdb1

But I will give your suggestion a chance...

[mmm123]

mkdir ~/img
sudo mount -o loop linuxium-ubuntu1204-desktop-rfs-BASIS.img ~/img
mkdir ~/sd
sudo mount -t ext4 /dev/sdb1 ~/sd
sudo cp -r ~/img/* ~/sd
sudo umount ~/sd
sudo umount ~/img
sudo tune2fs -L linuxroot /dev/sdb1

sudo bash -login
mkdir ~/img
mkdir ~/sd
mount -o loop linuxium-ubuntu1204-desktop-rfs-BASIS.img ~/img
mkfs.ext4 /dev/sdb1
tune2fs -L "linuxroot" /dev/sdb1
mount /dev/sdb1 ~/sd
cd ~/img
tar -cfps - . | ( cd ~/sd ; tar -xpvf - )
cd ~
umount sd
umount img

[no_spam_for_me]

if you have running linux, use linux fdisk/cfdisk to partition USB drive, then use linux tools to format as ext4

sudo cfdisk /dev/mmcblk0
=> 3 x 10GB
sudo mkfs.ext4 /dev/mmcblk0p2
sudo tune2fs -L linuxroot /dev/mmcblk0p2

same procedure

 :
[    1.472707] mmc_attach_sd..1219..  ===== Begin to identify card as SD-card. [mmc0]
[    1.488462] gp_rknand_info = : 0xee61c100
[    1.488622] request IRQ_NANDC irq , ret=0.........
[    1.488764] FTL INFO:Version = 438,Date = 20130516
[    1.488923] FlashCopyProgBuf1=0xc1483000
[    1.489091] ATime: 40 ns AHB: 150 timming: 1082
[    1.489191] No.1 FLASH INFO:ad de 94 eb 74
[    1.489281] No.2 FLASH INFO:ff ff ff ff ff
[    1.489365] No.3 FLASH INFO:ff ff ff ff ff
[    1.489457] No.4 FLASH INFO:ff ff ff ff ff
[    1.489971] ATime: 32 ns AHB: 150 timming: 1061
[    1.490237] ATime: 32 ns AHB: 150 timming: 1061
[    1.490326] randomizer = 2 , EccBits = 28 pSpec->pReadRetrial = bf026360
[    1.500154] rk29_sdmmc_change_clk_div..1935..  newDiv=0, newCLK=37500Khz [sd_mmc]
[    1.500415] mmc0: new high speed SDHC card at address 59b4
[    1.500911] mmcblk0: mmc0:59b4       29.4 GiB
[    1.502659]
[    1.502665] msdos_partition..461... ==== Begin to parse sdcard-partition.  [mmc0]
[    1.502876] msdos_partition..530... ==== The sdcard has MBR. [mmc0]
[    1.503011] msdos_partition..543... ==== partition-1, size=9765624KB  [mmc0]
[    1.503165] msdos_partition..571... ==== main partition-1....[mmc0]
[    1.503311] msdos_partition..543... ==== partition-2, size=9765632KB  [mmc0]
[    1.503465] msdos_partition..571... ==== main partition-2....[mmc0]
[    1.503596] msdos_partition..543... ==== partition-3, size=11400704KB  [mmc0]
[    1.503752] msdos_partition..571... ==== main partition-3....[mmc0]
[    1.503887]  mmcblk0: p1 p2 p3
[    1.504575] mmc_rescan_try_freq..1718..  ===== Initialize SD-card successfully. [mmc0]
 :
[    1.873850] EXT4-fs ([U]mmcblk0[/U]): error loading journal
 :
ls -al /dev/disk/by-label
lrwxrwxrwx 1 15 linuxroot -> ../../mmcblk0p[B]1[/B]
drwxr-xr-x 5 100 ..
drwxr-xr-x 2 60 .

mmcblk0 instead of mmcblk0p2
and mmcblk0p1 instead of mmcblk0p2


I don't know, is it a problem of *.ko, *.so or kernel...???

[no_spam_for_me]

delete because bullshit

[mmm123]

sudo cfdisk /dev/mmcblk0
=> 3 x 10GB
sudo mkfs.ext4 /dev/mmcblk0p2
sudo tune2fs -L linuxroot /dev/mmcblk0p2

It is possible, that SD card reader into your device doesn't support 32G SD cards.

[no_spam_for_me]

I don't know, I don't think so, because if I remember correctly it is the same with USB 16GB (sda, also a USB-microSD-reader with the 32GB) and SD without partition(s) at 32GB (mmcblk0) work...

[mmm123]

I don't know, I don't think so, because if I remember correctly it is the same with USB 16GB (sda, also a USB-microSD-reader with the 32GB) and SD without partition(s) at 32GB (mmcblk0) work...

I just checked my device, it has similar SD card - 32G and it works perfectly
Of course I use 1st partition for linux

root@rk3188:~# fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 31.6 GB, 31611420672 bytes
255 heads, 63 sectors/track, 3843 cylinders, total 61741056 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 * 63 60548984 30274461 83 Linux
/dev/mmcblk0p2 60548985 61741055 596035+ 82 Linux swap / Solari
---
[ 1.464320] mmc_attach_sd..1219.. ===== Begin to identify card as SD-card. [mmc0]
[ 1.489094] gp_rknand_info = : 0xee21c100
[ 1.489270] request IRQ_NANDC irq , ret=0.........
[ 1.489415] FTL INFO:Version = 438,Date = 20130516
[ 1.489863] FlashCopyProgBuf1=0xc1483000
[ 1.490044] ATime: 40 ns AHB: 150 timming: 1082
[ 1.490150] No.1 FLASH INFO:98 de 84 93 72
[ 1.490245] No.2 FLASH INFO:ff ff ff ff ff
[ 1.490337] No.3 FLASH INFO:ff ff ff ff ff
[ 1.490428] No.4 FLASH INFO:ff ff ff ff ff
[ 1.490922] ATime: 32 ns AHB: 150 timming: 1061
[ 1.491203] ATime: 32 ns AHB: 150 timming: 1061
[ 1.491302] randomizer = 2 , EccBits = 28 pSpec->pReadRetrial = bf025c34
[ 1.491359] rk29_sdmmc_change_clk_div..1935.. newDiv=0, newCLK=37500Khz [sd_mmc]
[ 1.491487] mmc0: new high speed SDHC card at address 59b4
[ 1.492021] mmcblk0: mmc0:59b4 SD 29.4 GiB
[ 1.493623]
[ 1.493628] msdos_partition..461... ==== Begin to parse sdcard-partition. [mmc0]
[ 1.493836] msdos_partition..530... ==== The sdcard has MBR. [mmc0]
[ 1.494026] msdos_partition..543... ==== partition-1, size=30274461KB [mmc0]
[ 1.494243] msdos_partition..571... ==== main partition-1....[mmc0]
[ 1.494399] msdos_partition..543... ==== partition-2, size=596035KB [mmc0]
[ 1.494547] msdos_partition..571... ==== main partition-2....[mmc0]
[ 1.494680] mmcblk0: p1 p2
[ 1.495269] mmc_rescan_try_freq..1718.. ===== Initialize SD-card successfully. [mmc0]

---
[ 2.067658] EXT4-fs (mmcblk0p1): INFO: recovery required on readonly filesystem
[ 2.075333] EXT4-fs (mmcblk0p1): write access will be enabled during recovery
---
[ 3.688115] EXT4-fs (mmcblk0p1): recovery complete
[ 3.714215] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
---
[ 11.013019] Adding 596028k swap on /dev/mmcblk0p2. Priority:-1 extents:1 across:596028k SS
[ 11.341133] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)

----



root@rk3188:~# cat /proc/partitions
major minor #blocks name

179 0 30870528 mmcblk0
179 1 30274461 mmcblk0p1
179 2 596035 mmcblk0p2
---

root@rk3188:~# ls -l /dev/disk/by-label/
total 0
lrwxrwxrwx 1 root root 15 Jan 1 2000 linuxroot -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jan 1 2000 swap -> ../../mmcblk0p2

[no_spam_for_me]

Boot by boot.img & kernel.img OR by recovery.img (that's what i use)?

[mmm123]

Boot by boot.img & kernel.img OR by recovery.img (that's what i use)?

It is booting with kernel.img/boot.img (not recovery). There is no big difference in kernels (e.g recovery kernel has buit-in command line while kernel/boot ombo gets command line from bootloader. Initrd is probably identical.
Unless android is screwing card, which is not very likely.