yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
1) that's why i get kind of surprise when i mounted ubuntu.img and found files in /dev, i guess you backed up that img

2) right, i know that, but again, you got it after or before install ubuntu? If i make bigger or smaller image and partition i guess i'll have to change it.

3) is this make by script of yours? or is this ubuntu feature? i haven't use ubuntu in so much time so i don't know. I am a (not official) debian mantainer and this is the first time i've hearded about oem-config, maybe i am missing something.

EDITED: nevermid, i found oem-config package in ubuntu, doesn't exits in debian, i'll see if i cand rebuild it for this purpose in orde to other people can use debian image.

4) sbkdeteck sais my device is sbk1 but i had to use a livecd to check it because y got segfault in my debian instalation, i think it's because a diferent version of

libthread.so

Thanks again.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
1) No, I did not "backup" that image, it is a modified live image from OMAP.

2) No, the UUID is generated with the filesystem.

3) oem-config is based off ubiquity, and it an ubuntu feature.

4) if it said sbkv1 then it will be :)
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
well, this is going to be harder than i thougth, anyway i am going to give it a try. Thanks for your help again.
[Eee Pad Transformer Q&A, Help & Troubleshooting] braernoch:
Kernel Source - SoC Audio

My most promising lead is one you're much better suited to try. I'm a coder, and I lack y'all's understanding of the architecture just yet. Perhaps we keep audio support included in the kernel and just modify the .c and .h files it uses to build its drivers from the get-go. I'm looking in particular at

1) "linux_kernel_TF101/sound/soc/tegra/tegra_soc_wm8903.c"

2) "linux_kernel_TF101/sound/soc/codecs/wm8903.h"

Theoretically, you can tweak the codec registers and define how the driver interacts with the card before compiling. Hopefully you can do something with that. I'll keep looking.

(Aside)

Have you tried adjusting sound card configuration through "/var/lib/alsa/asound.state"? Run "alsactl --help" to see that that's the default config file, adjust it, then run "alsactl restore 0" to load changes. I've had no luck there.

I thought "alsa-info.sh" from alsa-project.org might be helpful, but it looks for most of its info in lspci which is not supported on ARM devices. The closest tool I found was "lshw", but that doesn't really help.
[Eee Pad Transformer Q&A, Help & Troubleshooting] v0id_walker:
More questions

How is the speed of the device with ubuntu running on top of it? Is it comparable with Atom netbooks?

Will the update to ICS make it impossible to root the device?

As always, thank you for the answers.
[Eee Pad Transformer Q&A, Help & Troubleshooting] conizius:
I got some problems updating my android kernel.

I'm using a dualboot setup with ubuntu as recovery.

What I'm trying to do is flashing the oc kernel from roach (Prime 2.0.6).

I tried extracting the blob from the provided zip, renaming it and placing it into images/.

Then running OLiFE -> Update -> Android Kernel -> Turn on Device

Flashing finished, but afterwards neither system is booting.

Thought I could copy the missing kernel modules from Ubuntu or maybe even from Android, but there is no way.

Android is looping at the EeePad screen and Ubuntu reboots with a kernel panic.

When I turn around and flash the original boot.img everything is back to normal, Android as well as Ubuntu boots as if nothing has ever happened.

Is there any step I'm missing? Or am I just to tired to see the obvious mistake? Does I have to tell anything the size of the new kernel (it's a few bytes different).

Thanks for help :)

Btw. in frustration also tried with the kernel from Revolver Rom with the same result...

Well the speed is comparable in my opinion, but keep in mind that you have pretty limited ram ;) And you have an arm-architecture, so binary releases will never work for you unless they are released for arm. Beside that it's great! And we all love lilstevie for that! ;)

For ICS you could just wait for a Prime release with ICS. And if you have a skb1 device nobody can lock you out... maybe you just have to get down to honeycomb until a rooted rom is released (and pre alpha builds are already floating around).
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
if you are talking about tipical unknown symbol (see dmesg) when you try to load de module with modprobe try to execute depmod -a as root or with sudo.

This will generate /lib/modules/modules.* files needed to be able to load that modules.

---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------

I've been making my own tests with a custom debian image with lxde and it's fast as hell, much faster than ubuntu with gnome (obviusly) but it's still pretty unsable because i haven't been able yet to make work wifi or other important drivers, but i guess if you customize that image with another lighter enviroment it will be quite fast.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
you cant just flash an nvblob, that is its own format and needs to be unpacked first
[Eee Pad Transformer Q&A, Help & Troubleshooting] braernoch:
At first, "make modules" from the kernel source wouldn't even compile the modules. I think I just needed a good "make mrproper". Now that I have my modules, yes, I'm getting that error, but I already tried depmod as root. I get:

root@braer-tf101:/# depmod -a
WARNING: Loop detected: /lib/modules/2.6.36.4-1210+/kernel/sound/soc/codecs/snd-soc-wm8903.ko needs headset.ko which needs snd-soc-wm8903.ko again!
WARNING: Module /lib/modules/2.6.36.4-1210+/kernel/sound/soc/codecs/snd-soc-wm8903.ko ignored, due to loop
WARNING: Module /lib/modules/2.6.36.4-1210+/kernel/sound/soc/tegra/tegra_soc_controls.ko ignored, due to loop
WARNING: Module /lib/modules/2.6.36.4-1210+/kernel/sound/soc/tegra/tegra_soc_wm8903.ko ignored, due to loop
WARNING: Module /lib/modules/2.6.36.4-1210+/kernel/sound/soc/tegra/headset.ko ignored, due to loop

Trying to see if I can edit manually. Grr...
[Eee Pad Transformer Q&A, Help & Troubleshooting] v0id_walker:
If there is such an issue with missing binaries for arm in ubuntu, why dont we use ArchARM, netbsd or debian? Its not like o want to whine, i am just asking why did we choose the ubuntu (i am perfectly happy with arch, so i will try to use that :) )

I am not going to buy the prime (i dont have enought money for that) :P I will be perfectly happy with the first transformer, with working gps, etc
[Eee Pad Transformer Q&A, Help & Troubleshooting] Jazztrmpter:
OLiFE Script Read Error

Hello everybody,

My excitement of dual booting my Transformer B60K was recently halted when trying to do a full backup. I downloaded both the plain OLiFE tar and the Prime edition, but I am using the regular script with no additions for the backup. I plan to use the Prime edition to do the dual boot.

Anyways, I'm running BackTrack 5 from a 16 gb flash drive. All works well, except for the 16gb size limitation when trying to do these sorts of operations involving large file sizes. I read the guide here to dual boot my transformer, and I'm on step 7 of the Backup section. Within number 7, it mentions "If you get a read error it might be because you don't have enough space to store the backups". This is what I'm stuck on.

Put your device in APX mode then press any key
Device detected in APX mode
Putting device into Nv3P Phone Update mode
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x033c11c741601417
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0

sending file: ./images/transformer.bct
- 4080/4080 bytes sent
./images/transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: ./images/bootloader.bin
| 976013/976013 bytes sent
./images/bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Backing up partitions now
userdata.img
Nvflash started
[resume mode]
receiving file: ./backups/2012-01-17-userdata.img, expected size: 29249503232 bytes
file create failed NvError 0x30013
command failure: read failed
Press any key to continue...

I extracted OLiFE.tar.gz (tar -zxvf) to my external 1tb hard drive, and ran the script in the directory on my external. If the read error is truly from lack of space, then how can I make the script use my 1tb external hard drive, and not my 16gb filesystem on my flash drive? I will not continue the process without a backup of at least my user data, but I'd really like a full backup of the stock Android system + my user data. Any suggestions?

If nothing comes up, my backup plan is to partition 150gb or so out of my 2tb internal drive and boot BT5 from that.
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
You have two options, the first one and the easiest one is forgetting about backuping, i did a backup and never used it, i found here in XDA a nvflashable stock rom and that's what i use, in fact, i'v used that rom instead of prime in order to have dual boot with stock rom and ubuntu/debian just changing system.img from olifes package with system.img from stock rom

The other option is to mount external drive in the live cd, but this only would work if tha external drive is a linux filesystem like ext2, ext3, ext4...

If that external disk is formated in ntfs you can also create a virtual filessystem. For example:

asuming you have mounted and accesed that drive (i am going to supose it's call USB and mounted on media). Then you are in /media/USB folder in backtrack. wich means you are in that drive.

so create an enaugh large file to create the virtual filesystem:

dd if=/dev/zero of=filesystem.img seek=3000000000 bs=1 count=1

this comand will make a filessystem.img called file with 3 million bytes capacity, (2.7 gb ,more or less?) you will have to dedice how many bytes you need.

you have to format it

mkfs.ext4 filesystem.img

and then you have to mount it in some folder, first create the folder in your backtrack home

mkdir ~/filesystem

mount -o loop filesystem.img ~/filesystem

go to that folder, unpack there olife and try there your backup. should work

Remeber that your backup is going to be inside that file, and you only will be able to acees it if you mount that file in a linux system.

---------- Post added at 10:05 AM ---------- Previous post was at 09:57 AM ----------

The best option in my opinion would be the upcoming armhf architecture in debian, this is not ready yet but it's optimized for this kind off hardware but is not deboostrap-able yet in sid, it's quite new but i've been diggin in arm debian mailing list and they are making a hard work. In fact there is a proyect to fully support tf101

http: // www . cyber.com.au/~twb/doc/tf101 . html

you can google a bit about this new armhf architecture. In my personal opinion will be the best option. I now for sure that debian is the best distro giving good support for all the architectures you can imagine. :D
[Eee Pad Transformer Q&A, Help & Troubleshooting] conizius:
oh well... nVidia seams to have their own way for everything -.-

Okay, may I ask to be hinted where I can find how to pack anything for nvflash, so that I can take the kernel from the update.zip and repack it for nvflash?

Edit: Well never mind, I found the blob tools...

I did take a look at the update-script and it just dd's the blob to mmcblk0p4 (and copies some modules). But when I have a look at the partiton tables from the wiki, mmcblk0p4 has nothing to do with the android kernel, instead it would be p10.

Am I right? So theoreticaly I could just use dd from ubuntu, but I'm a little bit confused about the right partition now. Have those numbers changed because of the dualboot?

---------- Post added at 10:23 AM ---------- Previous post was at 10:08 AM ----------

Well, no I was not talking about ubuntu per se. It's just that not everything is in repositories (same goes for debian etc). And even not everything is released with source. And yet other projects are just to hard to compile for the average user.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
Just use blobtools to unpack the blob, the resultant files are ready for nvflash.

I chose ubuntu because they have quite strong support for arm vs other distributions, and also they have better touch support than the rest. ubuntus repo includes arm versions for MOST (probably around 90-95% of the total package count) are available, this is no less than the rest of the arm distributions, arm as a whole does not have the best support from the general community
[Eee Pad Transformer Q&A, Help & Troubleshooting] Danzano:
Hey guys sorry to ask but have not checked the thread in awhile how is the cross kernel going?

Last i heard lilstevie was trying to get hardware accell and some other things working has there been any progress on that front as of yet?

Thanks in advance wouldnt mind giving this another jam

Sent from my tf Enigmatic V2 beta 1.65Ghz Panda.test cust kernel settings
[Eee Pad Transformer Q&A, Help & Troubleshooting] Jazztrmpter:
I disabled/enabled my internal network card, now how do I assign a new interface?

First of all, thanks to Shaola for helping with my last question. I decided to backup individual apps using Titanium Backup, and have restored them in Prime.

For anyone that wants the ability to use a usb wireless adapter instead of the internal wireless card on the Transformer, here's how to disable the internal. I'm still working on getting the USB adapter assigned and recognized by the default network manager.

This is partly a guide in progress and partly my own question. When we figure the rest of this out, I'll make a new thread including a completed guide on this subject.

Note: I assume you have a USB adapter that you have already used with Linux before, and that you're not new to Linux.

Firstly, run lsusb after plugging in your adapter:

root@xxxxx:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc.
Bus 001 Device 004: ID 148f:2070 Ralink Technology, Corp. RT2070 Wireless Adapter

You should see it in the output. As you can see, Device 004 is my adapter. Now, you need to disable the internal card in the transformer. Gain root access and run these:

You should see the interface wlan0 and your network information, if connected to one. The wlan0 output is the one we want to look at.

wlan0 Link encap:Ethernet HWaddr 74:2f:68:20:b9:cb
inet addr:10.10.1.10 Bcast:10.10.1.123 Mask:255.255.252.0
inet6 addr: ab12::345c:67dd:ef89:b9cb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8434 errors:0 dropped:0 overruns:0 frame:0
TX packets:6557 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5134688 (5.1 MB) TX bytes:1056250 (1.0 MB)

Look in the first line at the HWaddr, otherwise known as your internal wireless card's MAC address. Take note of that, as we'll need it in the next step.

Now, gain root access and run:

Add these two lines to the end of the file, with your own MAC address of course, save, and exit.

[keyfile]
umanaged-devices=mac:74:2f:68:20:b9:cb

To re-enable the internal card, delete the lines.

You may also be able to change unmanaged to managed, or add # to the beginning of each line. (not tested)

Now, this is where I get stuck. I think I need to add a "managed-devces" line to the NetworkManager.conf file, but I cannot get the MAC address of my USB adapter. I also believe I can assign the USB adapter a new interface, such as wlan1, but I do not know how. Any ideas?
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
well, you shouldn't need to do anything to enable that device to be "managed" by network manager.

The thing is, the kernel detects it, loads automatically a module and makes de device (wlan1, eth0, eth1.... whatever) and should work automatically.

If it doesn't is almost sure because the kernel you are using has not support for that hardware, so you will have to compile it by your self.

First of all you have to assure that the device is not created.

Ifconfig command shows you active devices, but only active ones, ifconfig -a shows all of them, so if with ifconfig -a you can't see wlan1 that means there is no driver (or firmware) for that device.

see ifconfig -a, lsusb and dmesg to see what is realy happening

EDIT: if you see wlan1 when you type "ifconfig -a" but not when you type "ifconfig" just type

ifconfig wlan1 up

to launch the interface, netwok-manager should see it automatically
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
Or the simple solution is "sudo modprobe -r bcm4329" to permanently disable the internal wifi you can also remove the line that says "bcm4329" in /etc/modules
[Eee Pad Transformer Q&A, Help & Troubleshooting] Jazztrmpter:
Shaola, ifconfig -a does not show wlan1. It does however, give me usb0 and a new MAC address, but running ifconfig usb0 up doesn't do anything for network manager. It still only gives me one device to use.

I used this wifi adapter in Ubuntu 10.10 with no problems. It was even plug and play. No configuration needed. I wouldn't imagine that with an upgrade, device support was lowered for a brand new card.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
there is probably a kernel module for it in i386 or x86_64 kernels that doesn't exist in the arm tree
[Eee Pad Transformer Q&A, Help & Troubleshooting] Jazztrmpter:
Alright. What would be the next steps to getting this USB adapter to work?

I'm not new to Linux, but I am new to development. So if you point me in the right direction I may be able to figure it out on my own. :)
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
Well, usb0 also appears without pluggin that, so that's not the device you are looking for.

not true, linux-source is for all architectures, if the module for that is open source and not privative driver it will be in the kernel tree. ( I guess) The kernel you are using is not the "official one" i haven't digg so much yet in the kernel you are using, but the chrome one is addapted, it's not the official one (that's for sure) and the other one, did you take it from asus or another place instead of the official linux-tree?

well, it's not gonna be easy. you could compile it easyli if you had kernel-headers of the kernel you are using. In fact, i think it's the most important thing is lacking this proyect, an usable headers for compiling external drivers.

I've seen in my sheeva plug (arm architecture) the kernel is using is 2.6.32, (kirkwood build) and aparently those drivers are aviable:

sudo modprobe -l | grep rt2
kernel/drivers/net/wireless/rt2x00/rt2x00lib.ko
kernel/drivers/net/wireless/rt2x00/rt2x00pci.ko
kernel/drivers/net/wireless/rt2x00/rt2x00usb.ko
kernel/drivers/net/wireless/rt2x00/rt2400pci.ko
kernel/drivers/net/wireless/rt2x00/rt2500pci.ko
kernel/drivers/net/wireless/rt2x00/rt61pci.ko
kernel/drivers/net/wireless/rt2x00/rt2500usb.ko
kernel/drivers/net/wireless/rt2x00/rt73usb.ko
kernel/drivers/net/wireless/rt2x00/rt2800usb.ko

I've also downloaded from ralink the driver for your device and it's opensource you only need a firmware but i've seen it's already in ubuntu.img from lilstevie.

So, the question is, wich kernel are you using? where did that kernel came from? is it posible to build a headers package from that kernel? or at least bunch of headers files in order to find a way to compile external drivers? (you can also compile against linux source cause de headers are in there, but i've never gone in the kernel direction and my programming skills are close to zero, but i guess you would only need to set variables or modifie the Makefile)

As i see in ubuntu.img are two diferente kernels aviable 2.6.36.4 and 2.6.38.3 (in /lib/modules/ folder) i guess one of that is the crhome os kernel and the other one i don't know exactly wich one is or where does it come from.

Well, i am having so much fun with this proyect. I am learning so much. For now i am focused in building an armhf rootfs but there is a bug somewhere that doesn't let mi set up cron correctly, something related to perl and shortening names. But i will be looking for the kernel thing meanwhile.

@lilstevie: Is there a size limit for the kernel image to install with your script?
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
Okay I guess I should have been more specific, they don't exist in the module tree that I have in place for the transformer, I am not talking about source tree, although the kernel source is derived from the android source tree, which diverged from mainline quite a while ago.

Kernel headers will come when I start using a build kernel package, which should be with the next version or the one after, you can always "make linux-headers" from the cloned kernel source though.

2.6.38.3 is the ChromeOS kernel and is here

2.6.36.4 is based from the asus drop but is here.

@lilstevie: Is there a size limit for the kernel image to install with your script?[/QUOTE]

yes, look at the size of LNX and SOS in configs/*.config
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
All, clear, now, thanks for your work, let me now if you need something, i am not good at programming yet (and probably never) but i have some experience in debian packaging.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Jazztrmpter:
I too am having tons of fun with this project. My wireless card can use the RT 2800 driver, which, from your list posted, is at the end of the output. I didn't understand what that was from though. It's not from the ARM version on the transformer in the ubuntu.img?

As for me, I used the OLiFE Prime edition to flash both Ubuntu and Android. My kernel version:

uname -v:
2.6.36.4

So does that mean that the RT2800 driver is already on this kernel?
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
No, i have a sheeva plug, it's kind of miniserver that runs debian arm (originally ubuntu), so the output is from that kernel, not from lilstevie's one. You have to rty to compile the driver, either against linux-source (i think you can do that modifying Makefile to target the right include folder, take a look at it and see the errors if you try to) or mabye should be easier to make a package of headers to be able to compile any opensource driver you find later.

The thing is that you don't have the driver to run that device and you have to compile it.
[Eee Pad Transformer Q&A, Help & Troubleshooting] reali:
Hi!

Link to windows-flash-kit-v3.rar is closed (because of megaupload).

Please give us new link! Thanks =)
[Eee Pad Transformer Q&A, Help & Troubleshooting] Jazztrmpter:
Wireless

Where did you download the Ralink driver from? From what I have read, the rt2x00 driver has been included in all kernel releases since 2.6.24. So I am a bit confused because you said that "it's already in the ubuntu.img from lilstevie."

http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page#rt2x00_enters_mainline_kernel_-_January_2008

If the driver is already loaded into the kernel, what else is stopping the transformer from seeing my USB adapter as a usable wireless card?