yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
I will upload a photo of my screen as I can't get the output from transformer now.

on android, I use stock kernel.

for Ubuntu, as you suggested, I created a new root img with rootstock. so I have the kernel from that rootfs.
[Eee Pad Transformer Q&A, Help & Troubleshooting] depeha:
Does someone have working gpu drivers (best as deb) for ubuntu? I´ve tried some from launchpad (for toshiba ac100 I think), but ubuntu now get stuck while booting.
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
here is the output:

filename: /lib/modules/2.6.36.3-tegra-transformer-wifi/bcm4329.ko
license: GPL v2
alias: sdio:c*v02D0d4319*
alias: sdio:c*v02D0d4329*
alias: sdio:c*v02D0d0493*
alias: sdio:c*v02D0d0492*
alias: sdio:c*v02D0d0000*
depends:
vermagic: 2.6.36.3 SMP preempt mod_unload ARMv7
parm: clockoverride:SDIO card clock override (int)
parm: sd_msglevel:uint
parm: sd_power:uint
parm: sd_clock:uint
parm: sd_divisor:uint
parm: sd_sdmode:uint
parm: sd_hiok:uint
parm: sd_f2_blocksize:int
parm: firmware_path:string
parm: nvram_path:string
parm: dhd_msg_level:int
parm: dhd_sysioc:uint
parm: dhd_watchdog_ms:uint
parm: dhd_arp_mode:uint
parm: dhd_arp_enable:uint
parm: dhd_pkt_filter_enable:uint
parm: dhd_pkt_filter_init:uint
parm: dhd_master_mode:uint
parm: dhd_watchdog_prio:int
parm: dhd_dpc_prio:int
parm: dhd_dongle_memsize:int
parm: iface_name:string
parm: dhd_idletime:int
parm: dhd_poll:uint
parm: dhd_intr:uint
parm: dhd_sdiod_drive_strength:uint
parm: dhd_txbound:uint
parm: dhd_rxbound:uint
parm: dhd_deferred_tx:uint
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
Take some time and read something sometime, it has been discussed many many many many many times that the android kernel lacks the required parts for the L4T drivers
[Eee Pad Transformer Q&A, Help & Troubleshooting] jerdog:
First rule of XDA:
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
a) drivers are implemented in the kernel, which is much more complicated to install than a simple deb

b) There is currently no support for graphics acceleration. If you know enough to contribute to the kernel I think there's some work going on with that under the uboot fork, but if not just wait til they're done.

The kernel is independent of the rootfs, it's what gets flashed to LNX. Since you haven't done anything you'll still have the original Ubuntu kernel.

Odd, looks like the module is in the right place. Have you tried rebooting and running 'lsmod'?
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
reboot didn'tmake any change.

btw, the module was not there in the rootfs. I just copied it from Android partition.

Since you didn't tell me to do so, I thought it might be interesting info.

what can I do now ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] aldur999:
I understand, and it makes sense :)

Anyway, I'll try again, crossing my fingers.

EDIT:

There's nothing to do, I've done the same procedure after running make clean, deleting everything and doing it again. Are you sure that is necessary remove arm-linux-gnueabi string? Could it be something wrong whit modules?
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
ok; I managed to start bcm4329 module successfully (compiled kernel and modules and flashed the kernel to LNX part.)

now I can see the wlan0 interface but I can't configure it because I don't have iwconfig on the rootfs for Ubuntu.

How can I get iwconfig working ? (I tried copying the command from Android, but it does not run - says "no such file or directory")
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
finally !

I've found the following packages from ports.ubuntu.com:

libpcsclite1_1.7.2-2ubuntu2_armel

libnl3_3.0-1.1ubuntu1_armel

libiw30_30~pre9-5ubuntu1_armel

wireless-tools_30~pre9-5ubuntu1_armel

wpasupplicant_0.7.3-3.1_armel

after all installed, I followed the instructions here:

http://www.pantz.org/software/wpa_supplicant/wirelesswpa2andlinux.html

now, Ubunto on Transformer is connected to my WPA2 AP.

finally, I began installing Ubuntu desktop.

Now, I have 2 questions:

1. how can I automate wireless connection (including the autoload of bcm4329 module) ?

2. how can I create a kernel.zip file to use with ClockWorkRecovery (to boot into Ubuntu) ?

I'd appreciate if you could help me with that.
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Even if the modules are not there, it will still boot. The arm-linux-gnueabi string is needed on x86 to invoke the cross-compiler, but on ARM systems it won't work since there is no need for the cross compiler (and therefore one doesn't exist).

You can't just copy programs, you need to find the package. Copying files from Android is only necessary for the drivers listed in the firmware injection script.

Actually, I think I just realised what your problem was. You can copy the binaries from the Android image which go in /lib/firmware, but you need the kernel modules for that module, which were included in the original rootfs. Using the custom kernel installs its own set of modules, so that's why that worked.

1) Just add 'bcm4329 iface_name=wlan0' to /etc/modules to have it load on boot.

Then just save the other commands in a bash script (Google this if you don't know how to, they're pretty useful).

2) Make a copy of the existing Linux.zip, and swap out the kernelblob file in it for the working one you just created.
[Eee Pad Transformer Q&A, Help & Troubleshooting] aldur999:
Ok, I even tried to cross-compile the whole kernel on my desktop, building the blob and flashing, but, nothing again. Is there a way to see what error do I get?
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
thank you.

is there a better way to achieve this ?

for example, would it be possible to change the recovery partition (from recovery to linux and visa versa) from within Android ?

There are apps named "ROM manager"; would that work for this purpose ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Normally if there's a kernel panic, you'll get an error message. The fact that it's not loading at all suggests that there's something wrong with the way you're compiling the kernel. I've attached the blob I compiled, try using that and see what happens. (Don't use this blob with any modules, since it will become unstable and crash.)

The recovery partition contains CWM - you can overwrite it with one of the bootloaders, but then you lose CWM. If you're only switching infrequently, I'd just use CWM.

The ROM Manager app looks like it uses CWM-style files, so presumably it would work just as well as extracting the blob from the CWM zip and writing it to the partition with dd. I haven't tried it myself though.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
there is a reason for that :p ROM Manager and CWM are made by the same person, and are companion apps, ROM Manager gets the files, and CWM does the work,
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Yeah, the username kind of gave it away. I wouldn't have thought the ROM Manager needed to rely on CWM to do the heavy lifting though.
[Eee Pad Transformer Q&A, Help & Troubleshooting] aldur999:
Ok that's really weird. I tried to flash your blob using dd and I got again the asus eee screen stuck. So, I tried to put it in a CWM zip, and it worked! O.o I'll try again with my blob and keep you updated.
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
so, in theory, with a "ROM manager" I must be able to flash;

1- recovery image to SOS partition for recovery for recovery purposes

2- linux image to SOS partition in daily use to switch easily from Android to Ubuntu

But, how will I know if the "ROM manager" application is designed to flash the correct partition for Asus Transformer ?

Is the SOS partition, on same block for each Android device ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
and this is why CWM does the work for ROM Manager
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
so, do you recommend me to test it with ROM manager ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
That's odd, all CWM does is dd the blob to the partition (mmcblk0p4).

Yes.
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
how can I backup my current UBT partition to an img file ?

as I had to work on it for 3 nights, I'd like to keep it somewhere.

And if anyone requires to have a working Ubuntu 11.10 partition, I can share...
[Eee Pad Transformer Q&A, Help & Troubleshooting] aldur999:
Ok, after compiling once again kernel, I flashed it through CWM, and everything works fine :) I really thank you for your help, and I cannot believe to have the wireless scanning too :D
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
"ROM manager" doesn't support Transformer.

So I decided to write a dd script for swapping recovery partition.

I will use some command like:

dd if=/sdcard/linux.img of=/dev/block/mmcblk0p4 bs=409

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4 bs=409

but I am not sure which is the recovery partition. It seems it's not mmcblk0p4 anymore. Any ideas ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
mmcblk0p4 is the staging partition not the recovery partition, the kernel needs to be packed into an nvidia update blob
[Eee Pad Transformer Q&A, Help & Troubleshooting] Danzano:
Is this a re-work of lil stevvys ubuntu image but with fixes?

I read wireless scanning is working?

Is network manager working or still through terminal?
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Use dd (it's mmcblk0p8) under Android. I suggest piping it through gzip or something similar.

You're welcome. But you shouldn't have scanning - at least, I don't.

p4 is where the blobs are loaded from for installation.

p9 and 910 are SOS and LNX, and are inaccessible while the OS is running. To flash both, you'll need to create a blob (use blobpack) and write it to p4.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
I am interested in why you do not have scanning, the latest versions compiled from git should have scanning as that is what was merged in from VHDA
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Interesting. 'sudo iwlist wlan0 scan' produces no results, but the Gnome GUI detects them. I didn't notice until now because I'm using KDE. I'm still on natty, if it's relevant.

I also seem to be getting some errors from AppArmor, but I don't think that's relevant.
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
I didn't understand that. Why do I need gzip ? Just dd wouldn't be enough ?

I have wifi scanning as well. I compiled the kernel with your instructions on page 103.

I don't understand. Shall I use p8 ?

if so, what do I need p4 , p9 and p10 for ?

I'm really confused...
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
dd alone is enough, but the image will be massive. Because it's mostly empty space, compressing it with gzip will result in a much smaller image. The alternative is to run resize2fs before and after, but generally you want to avoid modifying the partition when making a backup.

I'm guessing you're using Gnome as well?

When you boot the transformer, the bootloader starts by checking if there's a blob in p4. If there is it executes it. The blob will then extract the images it contains to the relevant partitions.

p9 and p10 are (allegedly) the partitions corresponding to LNX and SOS, but we can't access these directly (with dd) so we have to use blobs. This means we can write to them, but not read.

p8 is your Ubuntu root partition, so don't write anything to it unless you want to lose your files.

*p4 = mmcblk0p4

Sorry if that caused any confusion.
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
so, you say I can't access p9 and p10 from Android and I should access p4.

p4 seems to be a big partition. what else does it hold except the blobs ?

now, if I dd all p4 partition it will backup all partition. I just want to change the recovery partition to "clockwork" when I need that. and after I finish with recovery, I want to put the Ubuntu loader back.

how can I achieve this ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] moseskim:
Webcam?

I've searched the two main threads and haven't been able to find anything about setting up the webcam. I've been able to upgrade to Ubuntu 11.10 with touchpad and wifi working on a Transformer with only an Ubuntu. Any ideas on where to start to set it up?

Also: I'd like to try to the CrOS kernel - do I need the custom uboot for it to work, or can I just compile the custom kernel from the github and have it work on my pure ubuntu setup?

Thanks!
[Eee Pad Transformer Q&A, Help & Troubleshooting] rickatnight11:
Thanks for the guide. I started building the kernel on the Transformer, but I ran out of space on my Ubuntu partition (mmcblk0p8 - 3.9G). I'd like to grab some space from the Android partition (mmcblk0p7 - 24G), but when I try and run:

sudo resize2fs -p /dev/mmcblk0p7 20G

...I get this output:

resize2fs 1.41.14 (22-Dec-2010)
resize2fs: /dev/mmcblk0p7: The combination of flex_bg and
!resize_inode features is not supported by resize2fs.

Tips?
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
Webcams I am not too sure about, all of mine are built into devices, and even then, I don't use them.

As of the latest commit you can run the CrOS kernel without needing u-boot, but be warned, it is nowhere near as friendly on the asus bootloader, the gained stability is at the cost of artifacting on the graphics, I am still working on solving all the problems with it
[Eee Pad Transformer Q&A, Help & Troubleshooting] rickatnight11:
To add onto this I went ahead and built the kernel on the Android partition without any issue. Running the script "blobbed" it up and flashed it, and sure enough upon restart the blue meter filled up.

Then the Transformer rebooted and sat at the Asus screen. Eventually I rebooted into CWM Recovery, flashed the ZIP attached to the instruction post, and booted back into Ubuntu just like before. Two questions:

Any ideas as to what I did wrong in the build process?

I'm still running Android, and I didn't realize that the ZIP you posted would load Ubuntu as the default OS. I assumed it was the ZIP that let you boot Ubuntu from CWM. How can I restore Android as the default OS (I'm assuming I can bundle this kernel I've built into an Ubuntu-booting ZIP once I fix whatever's wrong with it.)
[Eee Pad Transformer Q&A, Help & Troubleshooting] moseskim:
Actually that's what I meant - the built-in webcam wasn't working on mine (couldn't get it to detect in empathy). Is something wrong with my installation, or how do you suggest setting it up?

As for the new kernel, thank you for the heads-up. I really like what you've done so far and am looking forward to the stable release.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
it is one of the things on the list of non working devices
[Eee Pad Transformer Q&A, Help & Troubleshooting] moseskim:
Yes I understand that, thanks. I'm interested in trying to set it up, do you have any constructive advice?
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
fix the kernel driver
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
p4 only holds blobs, and once the blob is used the partition is formatted. You can't backup partitions with it - if you want to create a backup you have to use nvflash.

It will be a lot easier if you just keep CWM in the recovery (SOS) partition and use it to load the different bootloaders into the LNX partition. To restore CWM you can either use nvflash or a custom blob. blobpack is fairly easy to use compared to nvflash, the only limitation is you can't use it for partitioning.

You can't resize them like that. resize2fs only changes the size of the filesystem - it's still limited by the size of the actual partition, which can only be changed with nvflash (which formats the entire system in the process).

p7 is FAT32, so I'd suggest creating a 4GB file on it, formatting the file as ext2 and using that as a loop device.

I don't know how well compiling on FAT32 would go, since it doesn't support Unix permissions.

You may want to consider increasing p8 to 8 GB at some stage anyway, since 4 GB is really quite restrictive in terms of what you can do with it.

If it freezes on boot without any messages, then something is wrong with the kernel. There are too many things that could go wrong in the build process to specifically address all of them, all I can suggest is very carefully going over the instructions. A while ago I posted a copy of my kernel/blob, try with that and see if it makes a difference. One other poster found it only worked when using CWM to install the blob - maybe try that.

The zip I posted is one of the two CWM zips posted by Jhinta somewhere in this thread. If you search for them you should be able to find it.
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
Ok; I will use the CWM in the SOS partition. But I don't know what to put in the zip files for each bootloader.

I understand that one of the bootloaders should be Linux bootloader (for Ubuntu), and the other one should be Android ?

How can I create the correct zip files for each ?

And, with which option can I run the zip files throught recovery ?

(is that "install a zip file" ?)
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
Maybe stupid question, but it works on 32GB version?

Sry for my english.

E: soory for spam, I found answer for my question - yes
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Instructions for creating an Ubuntu bootloader are given in my post on building the latest kernel. There's no need to create your own bootloader for Android - that was posted by Jhinta on this thread somewhere, along with a bootloader for Ubuntu that uses the stock kernel.

And yes, you use the install zip file option.
[Eee Pad Transformer Q&A, Help & Troubleshooting] conizius:
Hey there,

I just wanted to grab the files to have a look before I get an transformer, but it only tells me that the server can't be reached :(

Is there a problem with the server or is it me? Or maybe the link to germany :(

"Firefox kann keine Verbindung zu dem Server unter lilstevie.geek.nz aufbauen."

See firefox can't establish a connection to the server...

Oh and well when I'm already posting:

Which version is the best for a dual boot setup? Is 16gb enought or should I rather grab 32gb? And is umts working with ubuntu?

Greetings,

Coni
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
As I understand that server is just a PC in lilstevie's house/room/etc., so it does go down from time to time. It'll probably be up in a while.

Android uses about 1 GB, and by default Ubuntu uses a 4 GB partition (I'd recommend 8 GB though). Whatever more is used depends on what files you need (music, video, etc.)

AFAIK, the 3G Transformer isn't out yet / none of us have one, so naturally no-one's been able to work on the drivers. I think a few people have got theirs working with 3G dongles though - you'd have to search the thread to find out.
[Eee Pad Transformer Q&A, Help & Troubleshooting] conizius:
Oh well thanks! I'll just keep on trying.

Uhm well I just saw the 3g version on Amazon for 499€... I didn't know it wasn't out right from the start.

http://www.amazon.de/EeePad-Transfo...R0MC/ref=sr_1_1?ie=UTF8&qid=1319746311&sr=8-1

Greetings, Coni
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
But I don't want to use stock android kernel.

So I should create my own Android bootloader from my kernel zip file , right ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
I think that CWM file used the Prime kernel, though I honestly don't know. I haven't really used Android that much myself.

If you do need to create your own Android bootloader, find a nvflash version of whatever ROM you're using and treat the file it flashes to LNX as the linux.img used in that script I posted for creating blobs and flashing them (back in the instruction post).
[Eee Pad Transformer Q&A, Help & Troubleshooting] vhda:
I was not able to make active scanning work correctly. From what I could see in my debug logs, whenever I issued an active scan with "iwlist scan" the driver would make two scans - the first returned 0 APs, but the second returned the correct number of APs. If you use "iwlist scan last" you should get the correct list of APs that the driver has in its memory.
[Eee Pad Transformer Q&A, Help & Troubleshooting] moseskim:
Missing blkid

I got stuck very early on with the following error while trying to complie abootimg:

moses@moses-tablet:/tmp/abootimg$ make -j2

if [ ! -f version.h ]; then \

if [ -d .git ]; then \

echo '#define VERSION_STR "v0.6"' > version.h; \

else \

echo '#define VERSION_STR ""' > version.h; \

fi \

fi

cc -O3 -Wall -DHAS_BLKID -c -o abootimg.o abootimg.c

abootimg.c:51:25: fatal error: blkid/blkid.h: No such file or directory

compilation terminated.

make: *** [abootimg.o] Error 1

I got the package installed from the step before and rechecked it. Cloning the git of abootimg was done successfully as well. Am I missing another package? I'm having trouble finding one for blkid if that's what I'm missing.

Thanks!

-Moses

UPDATE: Solved by installing the libblkid-dev library.
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Thanks, that helps a lot. So then my question becomes: what is it that KDE does differently to Gnome, and how do we go about getting it to work?

Thanks for pointing this out - I've added it to the guide.
[Eee Pad Transformer Q&A, Help & Troubleshooting] moseskim:
I can confirm this issue as well - followed the steps according to the guide to compile the latest kernel for lilstevie's github and on first boot it simply led to the eeePad screen. I packed the blob from the custom kernel into the CWM.zip and flashed it from CWM Recovery and it worked.

Would it make a difference if the original flash installation I used was for Android default with Linux (according the lilstevie's OP)?
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
It shouldn't, since the part which is different (the bootloader) is being overwritten. I honestly don't understand why this results in a different outcome, but I'll add it to the guide anyway.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Mazzstrikers:
Hi guys, I know it's a little off topic but do you think this will work on the Iconia Tab A500 and other honeycomb tegra tabs? For A500 we can still connect a keyboard to USB and worse come, bring up ADB. So do you think it will work?
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
yes, it will, but it has to be done different because of the lack of nvflash
[Eee Pad Transformer Q&A, Help & Troubleshooting] moseskim:
Partition Resizing

I think I misunderstood lilstevie's post about resizing the Ubuntu partition (UBT). I wanted an 8GB Ubuntu partition, so I added 4GB to the UDA and 4GB to the UBT. I'm running the flash-purelinux.sh file and edited the respective part of the purelinux.cfg file in an attempt to get an 8GB UBT partition:

[partition]

name=UDA

id=15

type=data

allocation_policy=sequential

filesystem_type=ext3

size=8212129792

file_system_attribute=0

partition_attribute=0

allocation_attribute=0x808

percent_reserved=0

[partition]

name=UBT

id=16

type=data

allocation_policy=sequential

filesystem_type=basic

size=8194304000

file_system_attribute=0

partition_attribute=0

allocation_attribute=8

percent_reserved=0

filename=./images/ubuntu.img

When I boot in Ubuntu, the disk manager says that my UBT is 8GB and that the root filesystem (/) is mounted to it. But when I check out my home and filesystem directories, it still says that I have only ~500mb free. I tested this by downloading a 600mb file and I ran out of space. Any suggestions?
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
I want to create my own Android bootloader but can't find your instruction post. On which page is it ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
you need to run resize2fs
[Eee Pad Transformer Q&A, Help & Troubleshooting] residentorca:
I think you're looking for post 1022.