Linuxium's Bootloader software to dualboot Android and Linux

[no_spam_for_me]

It is quite obvious:
crw--w---- 1 root tty 136, 2 Jan 1 22:28 2

strace of sudo is useless. capture strace of toolbox
e.g.:
1) sudo bash -login
2) strace ./toolbox reboot recovery 2>file
Still this is waste of time, i am sure this "toolbox" is available somewhere as source. Look for it and compile.

No, with "really mysteries" I mean is how you can identify the tty 136, 2 at first strace output...

root@LINUXIUMONE:~# strace ./toolbox reboot recovery
execve("./toolbox", ["./toolbox", "reboot", "recovery"], [/* 18 vars */]) = -1 ENOENT (No such file or directory)
dup(2)                                  = 3
fcntl64(3, F_GETFL)                     = 0x20002 (flags O_RDWR|O_LARGEFILE)
fstat64(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40086000
_llseek(3, 0, 0xbe860378, SEEK_CUR)     = -1 ESPIPE (Illegal seek)
write(3, "strace: exec: No such file or di"..., 40strace: exec: No such file or directory
) = 40
close(3)                                = 0
munmap(0x40086000, 4096)                = 0
exit_group(1)                           = ?
root@LINUXIUMONE:~# strace ./toolbox reboot recovery 2>str-file
root@LINUXIUMONE:~# cat str-file
execve("./toolbox", ["./toolbox", "reboot", "recovery"], [/* 18 vars */]) = -1 ENOENT (No such file or directory)
dup(2)                                  = 3
fcntl64(3, F_GETFL)                     = 0x20001 (flags O_WRONLY|O_LARGEFILE)
close(3)                                = 0
write(2, "strace: exec: No such file or di"..., 40strace: exec: No such file or directory
) = 40
exit_group(1)                           = ?

[enrique66_35]

I can't understand if it is possible for a real noob as I am, to make it work on a T-R42..
is this supported?
Do I have only to flash things and copy files or there is to insert command or compile something etc?
thank so much

As no_spam_for_me mentioned there is only direct support at present for the 3 devices Linuxium has specified. However I also own a T-R42 (v2) and I can confirm that flashing the ubuntu RFS does work although networking (ie internet connections) depend on your hardware -see below.

You'll need the flash tool, Loader, Parameter file, Boot image, Kernel(more on that in a second) and System image of either Ubuntu, Lubuntu or Xubuntu from

https://plus.google.com/+IanMORRISON/posts/765xvHJGWm6

TWO ISSUES TO CONSIDER
1. The kernel - depending on your version (V1.0,V2.0 and I've heard of V3.5) of T-R42 (it's printed on the PCB (circuit board) or the date of purchase might be a clue (but not guaranteed).
V1.0 has WLAN: AP6210 + LAN: asix ax88772 so will likely work right away with the Linuxium's kernels for wireless at least.
V2.0 has RTL8723AS + LAN: RTL8201F which is a bitch because there is no support that I can find for the wi-fi and even though I developed a kernel to detect the Lan it will not work properly to connect to the internet so your best option is a usb to lan adapter (ideally with the asix88772 chip - the Wii Lan Adapter works).

2. THIS PROCESS WIPES YOUR DEVICE!! I cannot stress this enough, if you chose to run the flash tool (Erase ISB ->flash the above files) you will lose EVERYTHING that's currently on it including android and any apps you had installed etc.

In Conclusion - without building a specific T-R42 recovery image the only option at the moment to get Linux is to flash it directly to nand, erasing android and with some very significant networking issues.

[mmm123]

Try this, but i can't guarantee if it works - no way to test it since my device doesn't have recovery partition:

rr.c:

#include <unistd.h>
#include <linux/reboot.h>
void main (){
reboot(LINUX_REBOOT_MAGIC1, LINUX_REBOOT_MAGIC2,
LINUX_REBOOT_CMD_RESTART2,"recovery");
}

---

gcc rr.c -o rr
./rr

[kayak1987]

thanks so much for the answers.
I have the T-R42 V2.0 so I think there's nothing to do..
I'm not interested in saving android cause actually I'm experimenting on this board, but the defection of WiFi and LAN is a big problem..

[enrique66_35]

thanks so much for the answers.
I have the T-R42 V2.0 so I think there's nothing to do..
I'm not interested in saving android cause actually I'm experimenting on this board, but the defection of WiFi and LAN is a big problem..

Then you're in the same boat as me In fairness to Ian/Linuxium his Linux images are very very good and I would recommend them with the proviso about networking. If you are going to use one please consider trying it with my kernel (http://www.freaktab.com/showthread.p...l=1#post153237). It enables the onboard Lan chip and Network Manager sets up a connection but I couldn't get it to function (unable to obtain IP by dhcp, setting it as static established a connection but no internet). Perhaps you can solve that issue although my feeling is the driver (rk29 vmac) is not working properly with Linux.

I would suggest you consider purchasing a 4 port usb hub and a usb to RJ45(lan) adapter with an asix88772 chip for internet. Unfortunately wi-fi is not possible until someone can find source code for the RTL8723as (wifi/bluetooth chip) for Linux.

As for android, the best rom I've seen is wasser's v1.2.4 which you'll find in the T-R42 forum.

[kayak1987]

Thanks so much!
Yes i'm Following the RK3188 forums and I've actually installed the new Wasser's 1.2.5 that on T-R42 V2.0 work perfectly!

I'll try to follow your suggestion as soon as I find the adapters! Thank you so much

Unfortunately I'm not in the knowledge conditions to program or compile anything..
so the only thing I can do is follow gently-well-explained step by step procedure

[enrique66_35]

I was daunted by the idea of re-compiling at first but after some research and experimenting I got a basic understanding. With a working source and config file you'd get the hang of it quick enough but as with most things, if someone else has already done it for you, why bother!

[ani1nonly]

I see what your problem is ... it was designed for using a micro SD card ... so I've modified it to accept an usb device and this should solve you problems and give some additional functionality to others ... see separate post (http://www.freaktab.com/showthread.p...298#post149298).

Dear Linuxium
thanks for your effort for making it to able to use external storage for linux rfs. i have successfully booted your ubuntu written on a 8gb pendrive(sandisk data travellar se9). i faced some problem to make pendrive in windows (xp) but succeeded by using your MAKE-LINUX-SDCARD.sh script and live ubuntu booted from 2gb sdcard on my netbook(lenovo s10).
The main problem I m facing now is that-
1-There is over scanning on my onida FHD LCD TV(approx 20 pixels from all four sides are going outside display area).
2-My screen filckers(displays goes blank every 2 to 3 seconds).
Problem no.1 solved by using script provided by jointherealms at http://www.freaktab.com/showthread.p...-Display-Scale.

but i m unable to find any solution for problem no. 2.
i tried kernels provided by 'rdavenpo' at https://github.com/rdavenpo/Linux3188

These kernels working well with "picuntu 4.5" because earlier when i was trying picuntu the flickering problem was there. but not working with your ubuntu setup.

any suggestion will be appreciated. Thanks

ani1nonly.

[enrique66_35]

If that kernel was meant for Picuntu 4.5 then it is booting OS from NAND where as your RFS is on a usb drive. You will need the kernel re-compiled for usb with the blink problem fix.

[ani1nonly]

If that kernel was meant for Picuntu 4.5 then it is booting OS from NAND where as your RFS is on a usb drive. You will need the kernel re-compiled for usb with the blink problem fix.

Dear brother
I think that the kernels are not meant for picuntu because there is no mension of picuntu in the post of the kernel here is the content of the post-
" Solution for RK3188-T FlashScreens
First of all this is not my patch is rdavenpo's patch from github, thanks man.

This is a kernel for RK3188-T without FlashScreens problems. and overclock.

https://github.com/rdavenpo/Linux3188

Just FYI - that kernel is undervolted and overclocked to 1.7GHz, sorry I forgot. I haven't had any issues on my 3188T @ 1.7GHz, but hardware can be different of course.

To turn off overclock:

echo 1416000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

To wake up wifi AP6210:

sudo insmod /lib/modules/rkwifi.ko

Thanks rdavenpo for all!

Kernel Working with:

802IV RK3188T and linuxium RFS, debian."

I just tried it on picuntu and it worked. But in the post it says working on linuxium rfs, debian.

[enrique66_35]

Dear brother
I think that the kernels are not meant for picuntu because there is no mension of picuntu in the post of the kernel here is the content of the post-
.....

I just tried it on picuntu and it worked. But in the post it says working on linuxium rfs, debian.

You missed my point. The kernel looks for the location of the RFS to boot and so unless it is specifically compiled to look to the usb device it will not boot an RFS from there.

The likelihood is that kernels taken from other sources (ie other than supplied by Linuxium for his bootloader or compiled with it in mind) are usually compiled to boot from NAND memory or possibly from SD card NOT usb.

If you had flashed the RFS to NAND then that linked kernel most likely would have worked. I assume that was where you had flashed picuntu to in order for that kernel to work previously?

[ani1nonly]

REQUEST FOR KERNEL

Dear linuxium
Can you compile your kernel used in your update.img with changes for preventing flickering of screen(solution for solving flickering in the post https://www.miniand.com/forums/forum...-solved?page=1)

Thanks
Ani1nonly

[ani1nonly]

You missed my point. The kernel looks for the location of the RFS to boot and so unless it is specifically compiled to look to the usb device it will not boot an RFS from there. The likelihood is that kernels taken from other sources (ie other than supplied by Linuxium for his bootloader or compiled with it in mind) are usually compiled to boot from NAND memory or possibly from SD card NOT usb. If you had flashed the RFS to NAND then that linked kernel most likely would have worked. I assume that was where you had flashed picuntu to in order for that kernel to work previously?

Thanks for such detailed info. I was not aware of that and one more thing I searched for the source thread of kernels without flickering issue and found that those kernel are specialy for picuntu on orignal thread.Dear can I replace picuntu rfs with linuxium rfs on picuntu 4.5 flash files(ie system.img(picuntu.rfs) with linuxium ubuntu desktop.img).?

[no_spam_for_me]

but not working with your ubuntu setup.

If you want to use the picuntu-rfs (system.img at SD/USB) with linuxium kernel, you have to label the rfs 'linuxroot' instead of 'picuntu', because the init look for this label

sudo tune2fs -L linuxroot /dev/[I]{device(-partition-number)}[/I]

[no_spam_for_me]

Dear can I replace picuntu rfs with linuxium rfs on picuntu 4.5 flash files(ie system.img(picuntu.rfs) with linuxium ubuntu desktop.img).?

I think so, at nand you only have to flash the img, because at nand normally works with addresses, if not, than you have to wirte the img to sd/usb, label it with 'picuntu' and make a backup (have a look at my sig) and then flash it to the nand