[Eee Pad Transformer Android Development] Aminpro:
Hi guys, finally got my old account back. I've been reading this whole thread and messaging back and fourth with jrohwer with a new account.

Thank you to him for this kernel :) It is certainly easier to manage and now possible to restore only a part of the linux system incase if something goes wrong with the original image as opposed to re flashing the whole partition.

I am currently stuck at making my wifi work at the newest kernel.

At first I inspected the log and found out that I've renamed nvram_4329 and not nvram_4329.txt. I thought that's the problem but now it is giving me a different error.

[ 13.144305] ## wifi_probe
[ 13.144343] wifi_set_power = 1
[ 13.154705] asusec: [asusec_reset_dock] send EC_Request
[ 13.248260] mmc2: new high speed SDIO card at address 0001
[ 13.360586] wifi_set_carddetect = 1
[ 13.362470] bcmdhd: fw_path: /lib/firmware//bcm4329/fw_bcmdhd.bin nvram_path: /lib/firmware//nvram_4329.txt
[ 13.362910] F1 signature read @0x18000000=0x9934329
[ 13.371744] DHD: dongle ram size is set to 294912(orig 294912)
[ 13.374184] wl_create_event_handler thr:52 started
[ 13.375134] dhd_attach thr:53 started
[ 13.375442] dhd_attach thr:54 started
[ 13.375704] dhd_attach thr:55 started
[ 13.378005] Broadcom Dongle Host Driver: register interface [wlan0] MAC: 00:90:4c:11:22:33
[ 13.378403]
[ 13.378415] Dongle Host Driver, version 5.90.125.94
[ 13.378432] Compiled in drivers/net/wireless/bcmdhd on Nov 7 2013 at 15:17:55
[ 13.378477] wifi_set_power = 0
[ 13.451689] asusec: [asusec_chip_init] Model Name: ASUS-EP101-DOCK
[ 13.457002] asusec: [asusec_chip_init] EC-FW Version: EP101-0213
[ 13.470909] input: asusec as /devices/platform/tegra-i2c.1/i2c-2/2-0019/input/input3
[ 13.579107] =========== WLAN placed in RESET ========
[ 13.579418] input: gpio-keys as /devices/platform/gpio-keys.0/input/input4
[ 13.579951] tps6586x-rtc tps6586x-rtc.0: setting system clock to 2014-01-24 19:18:25 UTC (1390591105)
[ 13.632782] udevd[111]: starting version 175
[ 14.304632] fm34 0-0060: Performing initialization
[ 15.246684] input: elantech_touchscreen as /devices/virtual/input/input5
[ 15.246900] asusec: [asusec_chip_init] touchpad and keyboard init
[ 15.301591] EXT4-fs (mmcblk0p7): mounting ext3 file system using the ext4 subsystem
[ 15.307815] EXT4-fs (mmcblk0p7): INFO: recovery required on readonly filesystem
[ 15.307824] EXT4-fs (mmcblk0p7): write access will be enabled during recovery
[ 17.099489] EXT4-fs (mmcblk0p7): recovery complete
[ 17.107850] EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: (null)
[ 18.029213] init: ureadahead main process (320) terminated with status 5
[ 19.262651] udevd[385]: starting version 175
[ 19.538934] tun: Universal TUN/TAP device driver, 1.6
[ 19.538942] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 20.559890]
[ 20.559894] Dongle Host Driver, version 5.90.125.94
[ 20.559897] Compiled in drivers/net/wireless/bcmdhd on Nov 7 2013 at 15:17:55
[ 20.559906] wl_android_wifi_on in
[ 20.559912] wifi_set_power = 1
[ 20.762499] =========== WLAN going back to live ========
[ 20.762509] sdio_reset_comm():
[ 20.818874] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
[ 20.899261] Firmware up: fw_path=/lib/firmware//bcm4329/fw_bcmdhd.bin op_mode=1, Broadcom Dongle Host Driver mac=94:db:c9:55:61:e5
[ 21.027480] Firmware version = wl0: Dec 12 2011 16:44:46 version 4.220.55
[ 21.028440] CFGP2P-ERROR) wl_cfgp2p_supported : wl p2p error -23
[ 21.030625] wlan0: set promisc 0 failed
[ 21.031594] wlan0: set promisc 0 failed
[ 21.032891] wlan0: set promisc 0 failed
[ 21.208121] wlan0: set promisc 0 failed
[ 22.674189] EXT4-fs (mmcblk0p7): warning: maximal mount count reached, running e2fsck is recommended
[ 22.679090] EXT4-fs (mmcblk0p7): re-mounted. Opts: (null)
[ 22.923625] wl_bss_connect_done succeeded status=(0x9)
[ 22.929969] Unable to handle kernel NULL pointer dereference at virtual address 00000094
[ 22.931643] pgd = c0004000
[ 22.932223] [00000094] *pgd=00000000
[ 22.933047] Internal error: Oops: 5 [#1] PREEMPT SMP
[ 22.934057] Modules linked in: tun scsi_wait_scan
[ 22.935150] CPU: 0 Not tainted (3.1.10-12-gf6ea477 #86)
[ 22.936331] PC is at wl_inform_single_bss+0xb8/0x328
[ 22.937365] LR is at 0x0
[ 22.937910] pc : [<c02bce4c>] lr : [<00000000>] psr: 800f0113
[ 22.937931] sp : dc583de8 ip : 00000000 fp : 000001a4
[ 22.940132] r10: dc562804 r9 : 00000000 r8 : dc540340
[ 22.941168] r7 : dc562804 r6 : dc0ab000 r5 : 00000000 r4 : dc0ab000
[ 22.942463] r3 : 00000001 r2 : 00000000 r1 : dc51d864 r0 : dc0ab000
[ 22.943745] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
[ 22.945193] Control: 10c5387d Table: 1b8b404a DAC: 00000015
[ 22.946273]

and the second problem is fixing the partition.

tried to fix it but I can't/don't know what to do.

/tmp # ./e2fsck.static -p /dev/block/mmcblk0p7
/dev/block/mmcblk0p7: Superblock blocks_per_group = 16368, should have been 16384
/dev/block/mmcblk0p7:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 16368 <device>

/tmp # ./e2fsck.static -b 16368 /dev/block/mmcblk0p7
e2fsck 1.41.14 (22-Dec-2010)
./e2fsck.static: Bad magic number in super-block while trying to open /dev/block/mmcblk0p7

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

/tmp # ./e2fsck.static -b 8193 /dev/block/mmcblk0p7
e2fsck 1.41.14 (22-Dec-2010)
./e2fsck.static: Bad magic number in super-block while trying to open /dev/block/mmcblk0p7

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

/tmp # ./e2fsck.static -b 8193 /dev/block/mmcblk0p7
e2fsck 1.41.14 (22-Dec-2010)
./e2fsck.static: Bad magic number in super-block while trying to open /dev/block/mmcblk0p7

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

I was hoping to use the newest kernel since the USB hotplugging was fixed otherwise I would be stuck at the old kernel.