yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] :
brick? explain me what's happened ;)
[Eee Pad Transformer Android Development] ramoncio:
Hi guys, great work bringing linux to TF101!!

I have been trying to run ubuntu on my tf101 with no success, tried all different kernels and images, but none of them boots.

I have been been using linux for years, even compiled a couple of android and linux kernels for my rk3188 device, and made a bash script to crosscompile kernels and create minimal systems with fakeroot, so I'm not afraid of linux console.

I have TWRP and latest 4.4 katkiss.

I installed bigwheelie memory modification script (bash version), so now I have 25Gb of internal storage available, maybe this is the problem?

I get errors like: cant find /lib/modules/3.XXXXX/modules.dep but if I boot from android i can see the file is there in /data/linuxroot/lib/modules/3.XXXXX/modules.dep.

Any pointers?

Thanks in advance!
[Eee Pad Transformer Android Development] Kingzak34:
This error is OK.

What did you do exactly, and what happened ?
[Eee Pad Transformer Android Development] ramoncio:
Oh great! I wasn't expecting such a fast answer :)

Did a small script to run it on the tablet on a ssh shell, and have been modifying it for different images and kernels:

# run this as root

busybox mount -o remount,rw /

rm -rf /data/linuxroot

mkdir -p /data/linuxroot

chmod 755 /data/linuxroot

cd /data/linuxroot

#tar -pxvjf /storage/emulated/0/Download/kubuntu-14.04.tar.bz2

tar -pxvzf /storage/emulated/0/Download/tf101-14.04-Lubuntu-Tegra-armaf.tar.gz

cp -R /storage/emulated/0/Download/3.1* /data/linuxroot/lib/modules/

busybox mount -o remount,ro /

reboot recovery

I think with 1.2 kernel screen was black, and with one of the combinations I can't recall now I even got an ubuntu logo appeared, and some error wanting me to ignore or continue, but just for once.
[Eee Pad Transformer Android Development] Kingzak34:
For now kernel that should be used is the 15 one. ( The last one too )

You may have to fix error on your android partition, check in this thread to correct filesystem errors method is somewhere not far.
[Eee Pad Transformer Android Development] ramoncio:
After the script, it boots into recovery, and I flash kernel. I usually get some errors about files in /dev/ when flashing kernel, but it reboots with penguins most of the times.

---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------

Ok thanks!! I'll look into checking filesystem, stick with 1,5 and report back, maybe with screenshots.

Any recommended image? I'd like to try that ubuntu base with tegra drivers included, and I'll try different desktops.

---------- Post added at 09:12 PM ---------- Previous post was at 09:05 PM ----------

One more thing, when I got this device, it had no serial number, so I don't know for sure if this is a SBK1 or SBK2 device.

When running bigwheelie script, I got asked for device type and selected SBK1, it all worked well without errors, and all android apps seem to run just fine, but I'm not fully confident everything is fine, and more since I don't seem to be able to run linux.
[Eee Pad Transformer Android Development] Kingzak34:
I don't know for skb version. But at least if it worked it think it's good.

You can use the image you want there is no problem about that. The one you chose is good.

Tapatalké depuis mon OnePlus One MIUI !
[Eee Pad Transformer Android Development] ramoncio:
I can't find how to fix internal filesystem.

From Terminal? ADB? TWRP?

In TWRP i can fix all partitions but internal memory.

Tried again the script with 14.04-base.tar.gz and 3.1.10-15-gabaf62d kernel.

Attached you can find the first and second boot captures.

First boot freezes there.

I restart and second boot ends on a loop with second capture.

Will keep searching to see if I can fix filesystem. I can reformat it if needed.

But after installing bigwheelie I haven't done much, it shouldn't be broken.

Just played a couple of games, installed a few apps and played with ubuntu images and kernels.
[Eee Pad Transformer Android Development] Kingzak34:
Don't connect dock until you get to login screen. It avoid errors and lags from 2nd screen.

For first screen I don't know.

To fix files stem I don't remember check on image thread too. I remember seeing it but I don't remember where. I'm sure it's in this thread or image thread.

Tapatalké depuis mon OnePlus One MIUI !
[Eee Pad Transformer Android Development] ramoncio:
Without dock it hangs here
[Eee Pad Transformer Android Development] ramoncio:
after 5-10 mins i get more messages:

INFO: task kiteractiveup:66 bloqued for more than 120 secs

"echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this message

INFO: task kiteractiveup:66 bloqued for more than 120 secs

"echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this message

INFO: task kiteractiveup:66 bloqued for more than 120 secs

and loops there
[Eee Pad Transformer Android Development] Kingzak34:
I think there is something wrong with installation. Try to do every step by hand and check if every step is working right

Tapatalké depuis mon OnePlus One MIUI !
[Eee Pad Transformer Android Development] ramoncio:
Ok, I found the post explaining how to fix filesystem by jrowler, linking a e2fsck.static.gz file.

From what I see my TWRP already has a e2fsck included, maybe that file was needed for previous twrp or cwm versions with no e2fsck.

Tried with both and I get the same error:

# e2fsck -p /dev/block/mmcblk0p7

Superblock

Blocks_per_group=16368, should have been 16384 # e2fsck -p /dev/block/mmcblk0p7:

the superblock could not be read or does not describe a correct ext2 filesystem.

If the device is valid and really contains an ext2 filesystem (and not swap or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fs -b 16368 <device>

I notice my parttion is /dev/block/mmcblk0p7 and not /dev/block/mmcblk0p6
[Eee Pad Transformer Android Development] Kingzak34:
And when you do mount in terminal what files stem do you have for Internal memory?

Tapatalké depuis mon OnePlus One MIUI !
[Eee Pad Transformer Android Development] ramoncio:
/dev/block/mmcblk0p7 on /data type ext4

/dev/block/mmcblk0p7 on /sdcard type ext4
[Eee Pad Transformer Android Development] Kingzak34:
So I don't know. Try to make a new installation manually step by step with su permission.

Tapatalké depuis mon OnePlus One MIUI !
[Eee Pad Transformer Android Development] ramoncio:
I will try manually, but installation only extracts a tar.gz file and copies a few files, not much where it can fail :)

Files are in the correct place after running the script, and system gets mounted rw properly or files wouldn't be in /data/linuxroot

Something is going on with partitions I think.

I'll dig deeper on bigwheelie script to see what exactly does, and if it was really installed successfuly on my device.

Maybe linux doesn't work with bigwheelie??
[Eee Pad Transformer Android Development] Kingzak34:
Yes I know. I'd don't know too what can fail. Be sure to use last 15 kernel. Older than 12 may not work on 14.04

Tapatalké depuis mon OnePlus One MIUI !
[Eee Pad Transformer Android Development] ramoncio:
Also noticed that when I flash linux kernel I get these errors attached, is this normal?
[Eee Pad Transformer Android Development] Kingzak34:
Never seen this before. I'm on 2.8.1.1 TWRP. Maybe it's part of the problem.
[Eee Pad Transformer Android Development] ramoncio:
Ok, problem seems to be with partitioning, as i can see

root@tf101:/ # fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 32.0 GB, 32006733824 bytes

4 heads, 16 sectors/track, 976768 cylinders

Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0 doesn't contain a valid partition table

Ot maybe fdisk can't read gpt partitions, and that's why that error, not sure.

I'll ask in bigwheelie thread, and come back when I got my partitioning right for sure.

Thanks for your fast and valuable help!!!

---------- Post added at 07:34 PM ---------- Previous post was at 07:29 PM ----------

bigwheelie script installed TWRP 2.8.1.4, and that's why I was using it.

I just downgraded to TWRP 2.8.1.1, so I use your same working version.
[Eee Pad Transformer Android Development] steveeJ:
[MENTION=3753391]jrohwer[/MENTION]

I've seen the new-bcmdhd branch is more recent than master.

Which branch in your repository should be used for compilation?

Which firmware files will be needed for a new RootFS?
[Eee Pad Transformer Android Development] netr0pa:
Hi, it seems like I also got the same problem with "cannot read /lib/modules/1.XXXX.modules.dep" - issue.

I have already extracted the modules into that folder of linuxroot and the file "modules-dep" is there. I don't know why it didn't work?

Versions I used:

Kernel: 1.5 (newest one from John)

Ubuntu version is also from John

TWRP version 2.8.1.4 (flashed with Nvflash).

Could it be something to do with partition? This is wierd because I managed to install the Lubuntu 12.04.4 With Tegra drivers - no problem so why would it be a problem now with this version of Ubuntu?

When I read this thread, it seems I was not the only one who got this problem with "cannot find /lib/modules" so there must be something in it. Any possible solutions?
[Eee Pad Transformer Android Development] Kingzak34:
It's not an issue if I remember well. I mean it doesn't affect the installation. You can just not care about those

Tapatalké depuis mon MEGA Mate 8 !
[Eee Pad Transformer Android Development] netr0pa:
The problem is that I cannot ignore those messages because the screen is stucking when I boot with those messages. I was waiting and waiting and couldn't get past the boot.

So basically I had to install 9-kernel instead of 10 or 12 or 15-kernel. I'm using right now 9-kernel which all of you guys used in the past.

There is something wrong with the 10 and 12 kernel (from what I read in the thread, you guys discussed about something to do with partition). Even 15-kernel didn't work either but it might just be something to do with my tf101's partition.

Edit: This is a great linux version for tf101 - I would even say probably the best one I have tried so far! I'm very impressed and grateful for all the work all of you guys here put down on this project! I see that multiple forum members have been engaged, thank you all for that!

It took me few weeks to battle with the installation of this specific linux version (coming from a guy who had never had any experience with Linux at all in the past) but it was all worth it, I might actually need some more help later once I checked through the OS a bit more. For now, I just wanted to share my opinion and gratitude about this project :) I know I'm a bit late to the party but hey, it's better to be late than never ;)
[Eee Pad Transformer Android Development] Kingzak34:
If it doesnt boot, it doesnt come from those error. With some kernel it may just hang and not boot, try to boot 4 or 5 times and should work if installation is correct.
[Eee Pad Transformer Android Development] netr0pa:
So now guys, I'm getting stuck again at this phase where I tried out DJDill's "ubuntu.img" image.

I don't know how to install this one (I'm sorry Im a beginner in a world of Linux so I got stuck here at this stage).

What I have done so far was to follow the guide from Kingzak34 where I already installed jrohwer's Ubuntu 14.04.

After that I have already extracted the bcm3249.tar.gz into lib/firmware.

After this step, I guess it's time to use DJDill's image in order to get proper wifi and USB, right? But how do I run this command or how do I flash it? I couldn't do it through TWRP since it's not a zip file.

After DJDill's image installation, I should go ahead and use "Ubuntu-3.1.10-9-rootbind kernel" ? And then go ahead and type "sudo depmod –a" in terminal once I have logged into the new linux OS?

Is that correct? But how do install DJDill's image file then?

[MENTION=3447252]Kingzak34[/MENTION], do you still remember how you guys did this? Please help me as a beginner out if you can, thank you in advance! :) Maybe you could please tell me it in ABC-steps, step by step and I will do everything I can in order to learn
[Eee Pad Transformer Android Development] prog19:
Same here... don't know where to go from where i am...

waiting for some advice
[Eee Pad Transformer Android Development] vietchinh:
So. I was able to boot up in RW in arch linux, but i wasnt able to boot into image again.. Heh system fail to mount? well idk. Testing other images.
[Eee Pad Transformer Android Development] maq0007:
Boot stops with:

plymouthd: ply-terminal.c:611: ply_terminal_open: Assertion 'terminal != ((void *)0)' failed.

Any clue what's wrong?

[edit]

this is with tubuntu1.1 and 1.2.
[Eee Pad Transformer Android Development] prog19:
when I try to boot in the latest tubuntu i get the same message
[Eee Pad Transformer Android Development] hlavicka82:
So I have been playing with this for four days and I was not successful to finalize a linux instalation.

I tried Tubuntu 1.1 and 1.2 - did not boot. I had the same error as previously mentioned.

I tried netinstaller 0.7 - like 10 times from scratch. It booted to the gui where you can run a script to setup desktop and display manager however after rebooting it was stuck.

I tried also Ubuntu 11.10 and Lubuntu 12.04 which i found in transformador's thread and they did not boot

I also tried Arch linux which booted fine however it needs a more experienced user to get everything setup

If someone finds an image that will work well please share.

I am on TeamEOS 4.2.2
[Eee Pad Transformer Android Development] vietchinh:
And how did you boot up ach linux?

It didnt work for me D:
[Eee Pad Transformer Android Development] 4512jth:
It also didn't work for me. I got a stack trace on boot.

EDIT: I rebooted and it worked fine?
[Eee Pad Transformer Android Development] vietchinh:
Can you tell me how to install? Just extract that tar in to linuxroot?

The first time i booted i got some sort of terminal. When i login and depmod -a and reboot i got still same screen.
[Eee Pad Transformer Android Development] hlavicka82:
For arch linux you need to setup everything on your own....the desktop and dispay manager...

Odoslané z môjho Transformer TF101 pomocou Tapatalk 4 Beta
[Eee Pad Transformer Android Development] zachf714:
Yep but that is the great thing about arch
[Eee Pad Transformer Android Development] vietchinh:
My god... I am Such a idiot... Well google is my friend lol

though wifi still doesnt work.
[Eee Pad Transformer Android Development] jrohwer:
This won't work directly with Tubuntu as the linux root file system is not put into the correct place. I haven't used Tubuntu myself as I can't (have a TF101G and no nvflash/wheelie), but IIRC Tubuntu repartitions your tab to install linux into /dev/block/mmcblk0p8. You have to get a linux root file system (Ubuntu, Debian, Arch or whatever) and manually put it in the correct place as described in the OP. The stuck on reboot with netinstaller is also due to the fact that after the reboot it's running the rootbind kernel which then can't find the root filesystem. The images from transformador's thread should work but note that you FIRST have to copy the linux rootfs to /data/linuxroot as described in detail in the OP.
[Eee Pad Transformer Android Development] jrohwer:
Re. wifi, did you check this:

http://xdaforums.com/showthread.php?p=43315235

Make sure your bcm4329 module is loaded.
[Eee Pad Transformer Android Development] maq0007:
I used tubuntu image as per OP's instructions. Ie copied files from it to /data/linuxroot. It's not tubuntu that repartitions anything, any image can be installed on separate partition.
[Eee Pad Transformer Android Development] vietchinh:
I did and i didnt had /etc/modules?

So i couldnt test. + i need to make desktop etc.
[Eee Pad Transformer Android Development] 4512jth:
How can I get the touchpad working on an Arch installation? The screen works fine but the mouse on the dock does not work.
[Eee Pad Transformer Android Development] shanegru:
twrp is a custom recovery.. some use clockworkmod some use twrp

---------- Post added at 09:38 PM ---------- Previous post was at 09:25 PM ----------

twrp is a custom recovery.. simular to clockworkmod
[Eee Pad Transformer Android Development] jrohwer:
Arch linux uses /etc/modules-load.d/<program>.conf for loading modules and

/etc/modprobe.d/myfilename.conf for passing module options.

See https://wiki.archlinux.org/index.php/Kernel_modules

Note that I have never used Arch linux but found this after 2 mins of googling :)
[Eee Pad Transformer Android Development] jrohwer:
Install the mtrack driver. The Ubuntu package is xserver-xorg-input-mtrack but I'm not sure what the Arch package is called.

Then add the following lines to /etc/X11/xorg.conf

Section "InputClass"
Identifier "elantech_touchscreen"
MatchDevicePath "/dev/input/event5"
Driver "mtrack"
EndSection

Logout and into your X-server again, and it should work.
[Eee Pad Transformer Android Development] jrohwer:
Update: Sni kernel

So I've been trying to compile the kernel from [MENTION=1801056]Sni[/MENTION] sources (http://xdaforums.com/showpost.php?p=43203818&postcount=569) to see if I can use it with my rootbind method, seeing that it has the latest L4T sources from nvidia merged. I've had mixed success.

I can compile the kernel from his sources and can also boot it with rootbind. :good:

USB hotplug and framebuffer now work great. :good:

However, I can't get wifi to work with his bcmdhd driver.

Mounting of FAT formatted USB disks also not working (I think it has to do with UTF-8 vs iso8859-1 encoding).

I think the latter two issues can be fixed by trying to compile with the old bcm4329 driver (which is also used in the kernel in the OP), and by recompiling FAT with iso8859-1 support. However, I haven't spent any time on it.

My main issue is that I can't get overclocking to work on Sni's sources. The default max is 1.0GHz and the kernel in the OP is overclocked to 1.6GHz. This really is a huge issue. With the oc'ed kernel Ubuntu runs reasonably fast and is usable. At the stock 1.0GHz it's slow and painful. I actually use my tab for work when travelling :) So I'd rather have a snappy tab with half-working USB and no framebuffer than a slow one with everything working.

So if I can't get overclocking to work I won't spend time fixing the other issues. I've tried patching Sni's sources with the same overclock code as for Jhinta's, there were no merge conflicts. The kernel also compiles without error (both gcc4.4 and 4.6). However the TF does not boot (just black screen).

Both complete diffs for the OC code are attached. The only thing I can find is that the source in tegra2_dvfs.c has changed upstream by NVIDIA in about line 165 (compare the 2 diffs):

CPU_DVFS("cpu", 2, 0, MHZ, 0, 0, 503, 503, 655, 760, 798, 798, 950, 970, 1015, 1040, 1100, 1178, 1200),
CPU_DVFS("cpu", 2, 1, MHZ, 0, 0, 503, 503, 655, 760, 798, 798, 950, 970, 1015, 1040, 1100, 1200),

vs.

CPU_DVFS("cpu", 2, 0, MHZ, 0, 0, 0, 0, 655, 655, 798, 798, 902, 902, 960, 1000, 1100, 1100, 1200),
CPU_DVFS("cpu", 2, 1, MHZ, 0, 0, 0, 0, 655, 760, 798, 798, 950, 950, 1015, 1015, 1100, 1200),

I don't have C programming skills and am not able to hack kernel code. I've just applied various patches and compiled kernel sources. So if anyone want's to chip in you are more than welcome :)
[Eee Pad Transformer Android Development] Sni:
I think its because this driver need newer firmware. Did you extract firmwares i've attached to /lib/firmware ?

Can you post output of dmesg

Oh, yes. I thought it is universal way to use utf8. Changing it back must solve problems.

Charset can also be specified directly:

mount -o iocharset=iso8859-1

Yeah, it was really slow. Are you using Unity?

I will try to play with frequencies. Was 1.6GHz stable for you? no random crashs/ hangups/ blackscreens?
[Eee Pad Transformer Android Development] jrohwer:
Yes I did and the driver finds the firmware. But it still gives an error. I sent you a detailed kernel log by PM. Did you receive it?

OK thanks for the command line mount tip :)

I never had a reboot/crash with 1.6, but for my own sanity and safety I set the max to 1.5 using cpufreq-utils and have been running this for months without a single problem. I use interactive governor. I am not using Unity but run kubuntu (I run KDE on my main desktop as well and run a lot of KDE apps for my daily work). On the tab it is really nice, I can get hw accelleration to work with kwin_gles, and I run kubuntu low-fat-settings to disable the akonadi and nepomuk semantic desktop stuff.
[Eee Pad Transformer Android Development] prog19:
I can't get any ubutuntu image to work with thist... what a shame. Someone could point aubuntu image that works ?
[Eee Pad Transformer Android Development] Sni:
Yes, now i think the problem is that bcm4329 is WEXT driver, while bcmdhd is nl80211.

Then the solution is to configure userspace (wpa_supplicant/networkmanager...) to use nl80211 stack.
[Eee Pad Transformer Android Development] jrohwer:
OK I've sorted this one out. The problem was the nvram.txt. The version you sent me by PM works just fine and after copying it to /lib/firmware/nvram_4329.txt and rebooting, network-manager connects to the wifi without any further configuration. I attach the nvram.txt below in case someone else wants to test it.

BTW I see that the Android ROMS (both stock ASUS and custom such as EOS or KatKiss) contain four files in /system/etc:

The nvram.txt in /data/misc/wifi on my Android is identical to nvram_murata.txt, and this is also the version I used for the bcm4329 driver in the Linux kernel. The nvram.txt you send and which works with the bcmdhd driver is identical to nvram.txt in the Android ROMS. It seems the bcmdhd driver needs a different nvram.txt from the bcm4329.

I also got the MicroSD vfat to mount with iso8859-1 charset, using the command line. So I guess recompiling the kernel with the correct config will fix that.

So this kernel is really now perfect :) except for the overclock. Have you had any progress with that?
[Eee Pad Transformer Android Development] Kingzak34:
Nice to hear that thanks both of you for your work ! I'm waiting next kernel version :)

Tapatalké depuis mon Nexus 4 MIUI !
[Eee Pad Transformer Android Development] steveeJ:
great idea you had here!

i'm playing this through in my head right now, and i have a question regarding kernel flashing.

you say:

and i have just tried to backup my current kernelblock from that partition using cat, then dd. first i noticed that the partition is way bigger than the kernel. but what really surprised me is that the kernel blob i was reading with dd from that partition(/dev/block/mmcblk0p4 ?!) , and looked and compared it to the original blob i flashed using TWRP: the dd blob has all zeroes until address 0x400, the original blob doesn't?!

now why i'm asking all this is, because i want to be able to flash to kernel blob's from android and native linux, so that i can use scripts to reboot into the other one without using the recovery for flashing

i searched the forums but didn't find answers to my question.

i would appreciate a small lesson here :)

this includes pointing to threads/sites covering this topic on tf101 of course!

thanks in advance!

steveeJ