Related
Hello,
I followed this manual:
http://handhelds.org/moin/moin.cgi/BlueAngelHowtoInstallLinux
I partitioned my SD card (FAT; ext3 but even tried it with ext2) and copied these files to FAT:
http://htc.gnulinux.biz/files/blueangel/sd/linux/
and this OPIE image to ext3/s:
http://hands.com/~lkcl/blueangel/
Haret starts, but when the penguin gets the "big eyes" it freezes and I have to take out the battery.
I have an MDA III with Windows Mobile 6 (perhaps that's the problem?)
Thank you,
Alex
No that's not your problem. Try with a GPE image.
And, you have to tell us what's on the screen when it freezes.
There's only the penguin and a red-filled thermometer column on the screen.
I'll try it with the GPE image, thanks.
I tried it again with the GPE image, but still no luck.
Oh excuse me. I thought you had a problem with the linux image.
Your problem I think is the startup.txt. You should modify it to match the files you imported in the FAT partition.
Follow the link I give you bellow to download the newest files.
http://htc.gnulinux.biz/files/blueangel/sd/linux/
That worked for me.
I took exactly these files, and the files in startup.txt are correct. Now I did this: I changed one file in startup.txt to a non-existant file. Now I could get into the Haret application (otherwise it tries to boot correctly) and made it listen to port 9999. On my computer I started HyperTrm on 9999 (and got a console). Then I corrected startup.txt again. Using the command "bootlinux", it started the bootprocess. This is what I got:
-----------------
Welcome, this is HaRET running on WindowsCE v5.2
Minimal virtual address: 00010000, maximal virtual address: 7fffffff
CPU is Intel XScale ARM arch 5TE revision 3 product 16 stepping 6 running in sys
tem mode
Enter 'HELP' for a short command summary.
HaRET(1)# set KERNEL "zImage-2.6.12"
HaRET(2)# set MTYPE 766
HaRET(3)# set INITRD "initrd-2.6.12-hh2.gz"
HaRET(4)# set CMDLINE "root=/dev/ram0 init=/linuxrc ramdisk_size=14336 keepinitr
d console=tty0 boot_mmc=y"
HaRET(5)# bootlinux
Physical kernel address: a0008000
Preloader physical/virtual address: a55ad000
Physical initrd address: a0408000
Goodbye cruel world ...
have you put initrd-*wh.atev.er*-hh2.gz on the sd card in the same directory as HaREt? that was my problem.
and, as a tip, once you get it going, use the GPE image from here:
http://htc.gnulinux.biz/files/blueangel/sd/linux/
GPE will not be your booting problem, this is an inintialisation issue before it ven starts to boot GPE. but it will help if you use that image.
I was wondering how to start gpe from the command line, when I boot up linux, I get the login, but don't know how to start GPE. Does anyone here know?
Thanks,
Tim
GPE should start automatically. If not, it seems as if it doesn't find the image.
Perhaps you have no configuration file / a wrong file name of the GPE image is written in there?
My MDA III not booting with linux, i use:
haret-20071216.exe
startup.txt:
set KERNEL "zImage-2.6.12-hh2"
set MTYPE 766
set INITRD "initrd-2.6.12-hh2"
set CMDLINE "root=/dev/ram0 init=/linuxrc ramdisk_size=14336 keepinitrd console=ttyS2,115200 console=tty0"
bootlinux
initrd-2.6.12-hh2 (without GZ )
zImage-2.6.12-hh2
My MDA III booting, and stoping on :
Starting portmap daemon: portmap
where use board-id? In instruction write:
5. get your board id
dmesg | grep -i "board id"
6. write it down.
I'm waiting long time, my mda is freeze
i not use crandel...
use gpe image on linux partition...
me help, only hard reset
OS: WM6.0
Radio:1.15
help please... i love linux...
I've gotten Android installed (and updated) on my HTC Tilt Device. My current hang up is that when I let it boot it hangs with the message
Code:
A N D R O I D [ ] init: cannot find'/system/bin/logwrapper', disabling 'sysinit'
Did I do something wrong/what can I do to resolve this issue?
Regards,
~Jeff
Onward, upward, backward. forward, I tried installing the "Warm Donut" version instead of the "Eclair" and the system hangs with this different message are startup on this one:
Code:
init: Unable to open persistent property directory /data/property errno: 2
I think Android dislikes me (Maybe it knows my other phone runs Maemo LOL)... Suggestions?
~Jeff
So I found a thread (which I can't link to because of the forum rules) that describes my second issue but the alternate data.img file provided does not resolve the issue for me as it says it should... As always waiting patiently and open to suggestions.
~Jeff
Since you mention data.img i'll assume you are using Haret rather then Nand install.
The 'init: Unable to open persistent property directory /data/property errno: 2' means that android cannot find the data folder, usually happens if you miss the installer stage.
Even when running from haret we have to run the installer in order to unpack the 'androidinstall.tgz' and set up the data image.
To access the installer menu you must press the d-pad centre button when booting.
Note that once it is installed you do not need to enter the installer again, unless you are updating.
Sorry for my English.
I tried all the rom, all, and no work for me either. Use two ext2 partitions for data and system. Using the latest zimage, haret and initrd 2.6.32, tested all options with default.txt
When I install, the first time, everything is right, but the second time I boot android, everything goes wrong. After installing, wait 15 minutes before touching anything.
What else I can try?
WM 6.1
radio 1.70.19.09
SD 8GB class6 with fat32, ext2, ext2, linuxswap
Thanks.
Go to NAND ?
vellowax said:
Go to NAND ?
Click to expand...
Click to collapse
Now prefer haret.
My bootlog.txt
** /dev/block/mmcblk0p1
** Phase 1 - Read FAT (compare skipped)
Attempting to allocate 7032 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Free space in FSInfo block (1093801) not correct (1078495)
Fix? yes
Next free cluster in FSInfo block (640022) not free
Fix? yes
1961 files, 119676 free (1078495 clusters)
sh: 2: unknown operand
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop1 is mounted
/dev/block/loop1: clean, 710/65536 files, 97021/262144 blocks
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop0 is mounted
/dev/block/loop0 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/loop0: 625/65536 files (12.8% non-contiguous), 19711/262144 blocks
My default.txt
#alloctest 0x2000
set RAMSIZE 0x08000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd initrd.lzma
#
# The following kernel parameters are useful
# ppp.nostart - Set ppp.nostart=1 to disable starting the ppp connection on boot
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htckaiser.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
# lcd.density - Defaults to 160, 128 shows more on screen
#
set cmdline "ppp.nostart=0 pm.sleep_mode=0 lcd.density=120 mddi.width=240 mddi.height=320 no_console_suspend board-kaiser-keypad.atttilt=0 board-htckaiser.panel_type=2 hw3d.version=1 board-kaiser-battery.battery_capacity=2160 board-kaiser-battery.haret_divisor=2200 board_htckaiser.pmem_size=4 board_htckaiser.pmem_adsp_size=1 clock-7x00.a11=400"
boot
Please explain what goes wrong on the second boot.
What is showing on the screen at the end?
Everything you posted looks right, as far as I can see.
n2rjt said:
Please explain what goes wrong on the second boot.
What is showing on the screen at the end?
Everything you posted looks right, as far as I can see.
Click to expand...
Click to collapse
Thanks for your help.
On the second boot every few minutes installation screen appears (the rays forming X) and finally the screen turns white and kaiser does not respond and I have to go back to WM.
Can be the problem have installed this WM rom?
I can install android in NAND if that solve my problems, I like it android.
Sorry for my English.
Maybe when you turned off after the first boot, the filesystem was not cleanly dismounted. It might help to clear the dalvik cache during the boot, using the boot menu. To open the boot menu, push the middle of the screen when Linux starts to boot. Choose the option to clear the dalvik cache. When that finishes, choose the "Exit" option. I don't know, but it might help.
NAND will give fewer problems, but still has problems dismounting the filesystem cleanly when shutting down.
n2rjt said:
Maybe when you turned off after the first boot, the filesystem was not cleanly dismounted. It might help to clear the dalvik cache during the boot, using the boot menu. To open the boot menu, push the middle of the screen when Linux starts to boot. Choose the option to clear the dalvik cache. When that finishes, choose the "Exit" option. I don't know, but it might help.
NAND will give fewer problems, but still has problems dismounting the filesystem cleanly when shutting down.
Click to expand...
Click to collapse
Thanks, I'll do it again (clear dalvik cache), I tried it once after reading a lot, but did not help.
Clear dalvik cache but problems persist, now the kaiser after working a few hours, as before, the screen stays black and does not respond, back to WM.
At least now do not see the X and white screen. If everything is like most people, why do not I have the same results?
THIS POST IS OUTDATED, FOLLOW THE GUIDE IN THE STICKY INTRODUCTION TO ANDROID - THIS BUG HAS BEEN FIXED
DISREGARD THE POSTS UNTIL PAGE 5, THEY WERE POSTED BEFORE THIS ORIGINAL POST WAS EDITED WITH THIS FIX.
The problem some users are experiencing is that their phones freeze soon after their first boot until APN (access point name) is changed, this is somewhat difficult to do due to the freezes.
Note: this is for GSM users. I have no idea if this will work with CDMA, or even if they receive freezes.
Highlandsun and I have stumbled upon a fix that worked for me RHOD110 - this has been tested on GSM only (Froyo).
Using this fix, there should no longer be a need to manually select APN.
There are two files you need:
Highlandsun's RIL
and
Customized ROOTFS (F22's keymap rootfs (Mar 1st) edited - it WILL work with all his custom key bindings)
You will probably want to use this kernel if you are not already, it has great battery life and most failed wakes and SoDs are fixed. It is also what I used when testing this fix.
Firstly, extract put the downloaded RIL onto your SD card, I put mine in a folder named Android in the root of my SD, I recommend you do this also.
now edit conf/froyo.user.conf contained wherever you keep your HaRET.exe on your SD. If you are using Linux or a UNIX based operating system, use any editor you wish. If you are running windows, use notepad ++ to edit this file.
Add the following within the { } after custom_shells at the bottom of this file.
Code:
mount --bind /sdcard/Android/libhtcgeneric-ril.so /lib/froyo/libhtcgeneric-ril.so
so that your file should look something like this, I have highlighted the added line. You could even copy and paste the below to replace your whole file.
Code:
# General parameters
general{
renice=1 # Run the renice script to inprove call answering
}
#compcache related parameters
compcache{
compcache_en=1 # enable(1) or disable(0)20 compcache
cc_disksize=100 # Ram swap disksize - any number between 1 to 98 should work; default is 1/4 of the RAM (24)
cc_memlimit=64 # Limit the memory usage for backing swap (cc .5x known issue-defaults to 15% of total RAM)
cc_backingswap_en=0 # enable(1) or disable(0) backing swap
cc_backingswap=/dev/block/mmcblk0p4 # pointing to the backingswap partition device, swap
}
#create swap file for compcache or linux swap
swap_file{
swap_file_en=0 # set to 1 to create swap file
# set to 0 to del the swap file
linux_swap_file_size=32 # swap file size in MB
linux_swap_file=/sdcard/swapfile # pointing to the swap file location ( must be /system/sd/)
}
#Linux swap parameters
#
# linux swap can only be enabled if cc_backingswap_en is set to "0"
#
linux_swap{
linux_swap_en=0 # enable(1) or disable(0) linux swap
linux_swap_partition=/dev/block/mmcblk0p4 # swap partition device
}
#virtual memory
sys_vm{
sys_vm_en=1 # enable(1) or disable(0) virtual memory configurations
swappiness=0 # default 60
page_cluster=0 # default 3, (0 since CM3.9.6+)
laptop_mode=5 # default 0
dirty_expire_centisecs=3000 # default 3000
dirty_writeback_centisecs=1500 # default 500
dirty_background_ratio=3 # default 5
dirty_ratio=5 # default 10
vfs_cache_pressure=200 # default 100 (tendency of the kernel to reclaim cache memory)
overcommit_memory=1 # default 0 (0=Heuristic 1=Always overcommit 2=Don't overcommit)
overcommit_ratio=80 # default 50 (% of Physical+Virtual memory to allow allocation)
}
# custom shell commands, these commands run last
custom_shells{
chmod 777 /etc/dbus.conf
echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
rm -f /sdcard/*.rec
mount --bind /sdcard/Android/libhtcgeneric-ril.so /lib/froyo/libhtcgeneric-ril.so
modprobe ipv6
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
}
Once you have done that, save it and make sure it is saved. You may have to copy it to your pc, edit it, delete the one on your sd, copy it back across - if using droidexplorer to manage files. You could also edit this file from within Android using ASTRO to browse to it.
Now extract that rootfs.img mentioned above and replace your current one.
You will now have improved reliably and hopefully no freezes on boot. The device may also seem faster now.
This fix was suggested to me by Highlandsun (hyc) on #xdandroid irc. He deserves all the credit.
---------For Developers-----------
The modified rootfs has /init.etc/ppp/options.smd edited to the following with changes bolded:
Code:
debug
defaultroute
updetach
[B]#persist[/B]
local
usepeerdns
noipdefault
unit 0
linkname gprs
novj
novjccomp
[B]lcp-restart 1
lcp-max-configure 3
ipcp-restart 1
ipcp-max-configure 3[/B]
highlandsun said:
The hang is because the ril is stuck, it launches pppd and waits for a success status from it. But in this particular case, the connection used the wrong APN so pppd cannot succeed. With the "persist" setting in the ppp options file, pppd also never returns on failure, so ril waits forever, and everything grinds to a halt.
Commenting out the persist setting is the main fix for this. The additional ipcp/lcp lines are to decrease the time pppd spends retrying the connection setup, so that it will quit in less than 60 seconds, which allows ril to recover from the error sooner. I have some more patches for ril which will hopefully make the recovery even faster, coming up.
Click to expand...
Click to collapse
Well you really need to break it down better.
What kernel/modules combo have you tried? How far back did you go? What rootfs have you tried? What builds? System images? Have you looked at your startup.txt? What is in it?
I don't have a 110, but on my 400 most everything "works" flawlessly - assuming you have it configured correctly, yours should be the same.
arrrghhh said:
Well you really need to break it down better.
What kernel/modules combo have you tried? How far back did you go? What rootfs have you tried? What builds? System images? Have you looked at your startup.txt? What is in it?
I don't have a 110, but on my 400 most everything "works" flawlessly - assuming you have it configured correctly, yours should be the same.
Click to expand...
Click to collapse
Okay, firstly my startup.txt
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 clock_7x00.grp=0xa99 hw3d.force=1 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod110"
boot
Full Packages I have tried:
FROYO X RED 2011.02.06
ProjectAndroid2.2Froyo.012311
RhodiumXDAndroid23.01.10
XDAndroid2.2Froyo.012211
SENSE x 2011.02.10
Along with these Modules:
htc-msm-linux-20101204_010857-package
htc-msm-linux-20110210_213850-package
modules-2.6.27.46-01253-gd53ddf6-dirty
initrd:
initrd-20100813-b11116a
Rootfs:
rootfs-20110210-2cb7ec0
(and many others i have just deleted)
ryannathans said:
Okay, firstly my startup.txt
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 [color=red][B]msmts_calib=0x9f.0x39a.0x35c.0x78 clock_7x00.grp=0xa99[/B][/color] hw3d.force=1 msmvkeyb_toggle=off [color=red][b]pmem.extra=1[/color][/b] gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod110"
boot
Full Packages I have tried:
FROYO X RED 2011.02.06
ProjectAndroid2.2Froyo.012311
RhodiumXDAndroid23.01.10
XDAndroid2.2Froyo.012211
SENSE x 2011.02.10
[ 175.542358] hw3d: current 1343 ppid 1 file d5bb27c0 count 2
[ 175.580810] binder: 1329:1342 transaction failed 29189, size 564-0
[ 175.730926] hw3d: closing
[ 175.730987] hw3d_release: in release for pid=1338 tid=1343
[ 175.731018] hw3d: releasing 1338
Along with these Modules:
htc-msm-linux-20101204_010857-package
htc-msm-linux-20110210_213850-package
modules-2.6.27.46-01253-gd53ddf6-dirty
initrd:
initrd-20100813-b11116a
Rootfs:
rootfs-20110210-2cb7ec0
(and many others i have just deleted)
Click to expand...
Click to collapse
Ok, first the rhod110 physkeyboard option only exists in F22's rootfs.
Have you tried with FRX04?
Have you tried with a "regular" rootfs from the autobuild service?
You also have deprecated commands in your startup.txt, I highlighted them in red.
I'm assuming when you try different kernel/modules you're removing the old zImage/modules-xxx.tar.gz and replace with the new zImage/modules-xxx.tar.gz...
I don't see any other issues. You might need to go way back in the kernel archives, start around the beginning of November and work your way backwards.
If you can get any logs that would be helpful, as I'm just grabbing at straws since I don't actually know what the problem is. Could be your SD card, have you tried a different SD?
arrrghhh said:
Ok, first the rhod110 physkeyboard option only exists in F22's rootfs.
Have you tried with FRX04?
Have you tried with a "regular" rootfs from the autobuild service?
You also have deprecated commands in your startup.txt, I highlighted them in red.
I'm assuming when you try different kernel/modules you're removing the old zImage/modules-xxx.tar.gz and replace with the new zImage/modules-xxx.tar.gz...
I don't see any other issues. You might need to go way back in the kernel archives, start around the beginning of November and work your way backwards.
If you can get any logs that would be helpful, as I'm just grabbing at straws since I don't actually know what the problem is. Could be your SD card, have you tried a different SD?
Click to expand...
Click to collapse
Tried multiple SD cards, my current card is 16GB (could there be a problem here?)
where could I grab logs from?
Tried FRX04 too.
Just making sure im doing it right
Dowloaded RAR - Android v2.2.1 Froyo: Reference
unrar to 'andboot' on sd card.
edit startup.txt
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 hw3d.force=1 rel_path=andboot"
boot
Downloaded and put modules-2.6.27.46-01212-ge59fdaf.tar and its zImage in andboot
(deleted old ones first)
replaced rootfs with rootfs-20110210-2cb7ec0 (renamed of couse to rootfs.img)
.....
run haret.exe
past all the booting
past the xdandroid logo loop
screen is horizontal
slow and laggy android
screen flips to verticle
seems to be more stable
set up my wifi, connected.
so looks like the modules-2.6.27.46-01212-ge59fdaf has stopped it freezing seconds after booting into android.
what do you need now? Am I forever stuck with this old module?
ryannathans said:
Tried multiple SD cards, my current card is 16GB (could there be a problem here?)
where could I grab logs from?
so looks like the modules-2.6.27.46-01212-ge59fdaf has stopped it freezing seconds after booting into android.
what do you need now? Am I forever stuck with this old module?
Click to expand...
Click to collapse
Well at least an old kernel/modules boots. You sound like you're doing it correctly - just to be clear the modules ends in .tar.gz - you shouldn't be uncompressing this file whatsoever.
Now, on to logs. Since you never really boot adb is the only option. If you have Windows, Droid Explorer does most of the hard work for you. Once you get it setup, do a pull
Code:
adb pull /data/system/dropbox/ /path/to/folder/on/your/pc
It will dump all the files in that folder on your phone, onto that folder on your PC. Look at the last SYSTEM_LAST_KMSG file, attach it here.
Hell, attach a few of them.
arrrghhh said:
Well at least an old kernel/modules boots. You sound like you're doing it correctly - just to be clear the modules ends in .tar.gz - you shouldn't be uncompressing this file whatsoever.
Now, on to logs. Since you never really boot adb is the only option. If you have Windows, Droid Explorer does most of the hard work for you. Once you get it setup, do a pull
Code:
adb pull /data/system/dropbox/ /path/to/folder/on/your/pc
It will dump all the files in that folder on your phone, onto that folder on your PC. Look at the last SYSTEM_LAST_KMSG file, attach it here.
Hell, attach a few of them.
Click to expand...
Click to collapse
Just to clear it up, logs from module that dont boot or the one that does?
ryannathans said:
Just to clear it up, logs from module that dont boot or the one that does?
Click to expand...
Click to collapse
The dropbox will have logs from failed boots hopefully.
If you can get a log when it's failing to boot, that would be ideal. Might want to rename your data.img, grab the newest 1253 kernel from GIT and boot. See if you can grab a dmesg from adb,
Code:
adb shell dmesg > dmesg.txt
Will dump the dmesg.txt file to where ever you're running that command from. You can change the path on the right side of that command if you want to direct the output to a different folder.
i cant get droid explorer to find me device =/
scratch that, it picked up a "00000" that seems to be it.
new data.img, kernel and module from 1253. loads home screen with the google search bar and the android and it just froze up, performing soft reset, putting on the working modules and retrieving the logs for you.
done!
see attachment
is that all you need?
What should I do next?
ryannathans said:
is that all you need?
What should I do next?
Click to expand...
Click to collapse
The only log in there is from Sat Oct 23 02:21:48 CEST 2010. Can you get any adb interface running while it's booting...? Have you traced it down to which kernel is the one that fails to boot?
arrrghhh said:
The only log in there is from Sat Oct 23 02:21:48 CEST 2010. Can you get any adb interface running while it's booting...? Have you traced it down to which kernel is the one that fails to boot?
Click to expand...
Click to collapse
any kernel after november 2010 just freezes after booting (something to do with the panel?)
Trying a different 'package' and hopefully I can get the logs.
this time im using: http://forum.xda-developers.com/showthread.php?t=933177
okay is seems to be working -.- its modules-2.6.27.46-01232-gb7033df
ill try and load 1253
Ok, so start at 1232 and work your way towards 1253 - which kernel stops booting? I can't troubleshoot this as 1253 works fine on mine and most devices .
arrrghhh said:
The only log in there is from Sat Oct 23 02:21:48 CEST 2010. Can you get any adb interface running while it's booting...? Have you traced it down to which kernel is the one that fails to boot?
Click to expand...
Click to collapse
arrrghhh said:
Ok, so start at 1232 and work your way towards 1253 - which kernel stops booting? I can't troubleshoot this as 1253 works fine on mine and most devices .
Click to expand...
Click to collapse
can you point me to where I can download 1232 - 1253? appreciate the help so far
EDIT: I think i found them.
Trying now.
EDIT:
01245 - PASS
01246 - PASS
01250 - PASS
perhaps it was my 'noobiness' previously causing it to crash, I cant seem to reproduce it anymore -.-' I think i was using a different zImage to the Modules version
using FRX04, latest rootfs, my FN button on the keyboard is an @ and there is no other button that works as FN.
keyboard layout in startup.txt is set to rhod110
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ryannathans said:
perhaps it was my 'noobiness' previously causing it to crash, I cant seem to reproduce it anymore -.-' I think i was using a different zImage to the Modules version
using FRX04, latest rootfs, my FN button on the keyboard is an @ and there is no other button that works as FN.
keyboard layout in startup.txt is set to rhod110
Click to expand...
Click to collapse
Heh, it happens.
Have you tried F22's new rootfs? Adds all sorts of interesting keys, read thru his thread. I don't think the RHOD110 layout is in any other rootfs TBH...
arrrghhh said:
Heh, it happens.
Have you tried F22's new rootfs? Adds all sorts of interesting keys, read thru his thread. I don't think the RHOD110 layout is in any other rootfs TBH...
Click to expand...
Click to collapse
ahh noo. still same problem with it
thanks anyway
EDIT: everything's working sweet now that I had a chat with F22 and we got rhod110 support now
I faced same issue, it froze while installing, or so it seems. then one fine day, i accidently clicked on screen for 2-3 secs with stylus and then ... the screen moved one line up showing some message related to 'point 2' or in other words caliberation. My guess was it was waiting for caliberation and i thought it froze. Not sure of this is the same case with yours, but you can try it once. I clicked for 2-3 seconds on top-left corner first, then top-right, bottom-left, bottom-right, and lastly center of screen. After that everything worked properly.
*** ABOUT ***
This is an attempt to build a completely clean installation of xubuntu for the tf300tg (and probably tf300t). Most notably it does not reuse the ac100 ubuntu package.
I also want it to be as completely documented as possible starting from an official ubuntu repository and kernel source, until everything is working. Which does not mean it is for a complete beginner to reproduce...
It's not (yet) packaged : you at least need to be able to install a blob for the kernel, and a rootfs to a dedicated partition.
It's also not yet as cleaned up and documented as I would for the kernel side of things.
Everything is done on device on (and for) a tf300tg but as been reported to work on tf300t.
Most of the hard work was done by others. I mostly started from rabit's tf700 ubuntu, and added some insight from cb22 work on arch to get something working.
*** STATUS ***
What works :
- it boots into a clean xubuntu dm/desktop, with wifi (improved), 3g
- it also boots into android (stock, didn't try cm)
- 3g also works under android (new)
- touchpad / touchscreen
- 3d acceleration (version 16.3 of nvidia drivers)
- cpu and gpu overclock (respectively to 1,5 GHz and 446 MHz)
What I know doesn't work, isn't there yet :
- sound
- bluetooth
- some key remapping (esc, alt, ...)
Many other things I didn't check (sensors ?).
*** HOWTO install ***
0. of course you can break many things doing that ; you should have access to nvflash (never had to use it though) and with a recovery installed (I'm on twrp 2.4.3.0)
1. unpack xubuntu_tf300tg_rootfs-0.1.2.img.lzma to the internal storage and move / rename to linux/rootfs.img (/data/media/linux/rootfs.img)
1bis. you can change your keyboard layout in /etc/default/keyboard (replace "us" by whatever is your locale)
2. install the kernel blob using fastboot or "dd if=xubuntu_tf300tg_kernel-0.1.2oc.blob of=/dev/block/mmcblk0p4"
You should be able to reboot into xubunfu (or android).
3. log in as guest, from "user and groups" in the "settings manager", add one user, set password, change account type to administrator, add to sudo group (root password wil be asked : root)
4. logout, then login into your newly created user
5. open "language support" from the settings manager, and when it says missing locales, either choose install if you want "en" or "ask me later" if you want something else (in which case you can chose to install your own language, and configure them on the "regional format" page ; don't forget to apply system wide on both pages
6. change root password
Your second reboot should be more satisfying
*** HOWTO improve ***
1. find out what does not work and tell in the thread
2. understand what is documented bellow and propose correction / evolutions in the thread
3. don't hope for frequent updates : I do that alongside a more than full time job and tending to a two years old child. Still I will update.
*** DOWNLOAD ***
rootfs : http://d-h.st/vYf
kernel : http://d-h.st/UAy
misc config files : http://d-h.st/TEZ
nvidia drivers : http://d-h.st/pwQ
md5sum :
4f572c110c3f06f54699c826fed692f4 src-0.1.2.tar.lzma
249826271f4fadff4352217467e4ed2e xubuntu_tf300tg_kernel-0.1.2oc.blob
3263de707c2586d1e2177367f067361a xubuntu_tf300tg_rootfs-0.1.2.img.lzma
cf20b01281be3ef4b6d4631ae5cea67b R16.3.tar.lzma
*** HOW is it done / rootfs ***
I did it from ubuntu (rabits') on my tf300tg. Should be doable from another platform. Definitly doable from self.
As root.
# unset languages / locales
export LANG=C
unset LC_ADDRESS
unset LC_IDENTIFICATION
unset LC_MEASUREMENT
unset LC_MONETARY
unset LC_NAME
unset LC_NUMERIC
unset LC_PAPER
unset LC_TELEPHONE
unset LC_TIME
# mount a cleanly ext4 formated partition (futur root partition)
mount /dev/mmcblk1p2 /media/p1
# install initial minimal system
apt-get install debootstrap
debootstrap quantal /media/p1 http://ports.ubuntu.com/
# prepare to chroot
mv /media/p1/etc/apt/sources.list /media/p1/etc/apt/sources.list.orig
cp src/sources.list /media/p1/etc/apt/sources.list
mv /media/p1/etc/fstab /media/p1/etc/fstab.orig
cp src/fstab_chroot /media/p1/etc/fstab
mkdir /media/p1/run/user
# chroot into the new system and mount all special filesystems
chroot /media/p1
mount -a
# download xubuntu (avoiding unity which is recommended by lightdm)
apt-get update
apt-get upgrade
apt-get install xserver-xorg
apt-get --no-install-recommends install lightdm
apt-get install lightdm-gtk-greeter
apt-get install xubuntu-desktop
# install nvidia drivers and tuned nv.conf
tar xf R16.3.tar
update-alternatives --force \
--install /etc/ld.so.conf.d/arm-linux-gnueabihf_EGL.conf arm-linux-gnueabihf_egl_conf /usr/lib/nvidia-tegra/ld.so.conf 9000 \
--slave /usr/lib/xorg/modules/drivers/tegra_drv.so nvidia_drv /usr/lib/nvidia-tegra/xorg/modules/drivers/tegra_drv.abi13.so
ldconfig -v
update-rc.d ondemand disable
# change root password to something of your chosing and exit chroot
passwd root
# configure touchscreen and touchpad
apt-get install xserver-xorg-input-multitouch
exit
cp src/mtev.so /media/p1/usr/lib/xorg/modules/input
mkdir /media/p1/etc/X11/xorg.conf.d
cp src/50-elan* /media/p1/etc/X11/xorg.conf.d
# change hostname
# edit /media/p1/etc/hostname and replace tf300tg with your chosen hostname
# edit /media/p1/etc/hosts and insert a line (second one) with "127.0.0.1 yourhostname"
# hide the partitions from mmcblk0 (thanks cb22)
echo 'ENV{ID_PATH}=="platform-sdhci-tegra.3", ENV{UDISKS_IGNORE}="1"' > /media/p1/etc/udev/rules.d/80-hide_tf300tg_partitions.rules
# change keyboard defaults
# edit /media/p1/etc/default/keyboard ; replace "pc105" by "asus_laptop" ; you can also change "us" to your locale
# create mountpoints for system and data
mkdir /media/p1/system /media/p1/data
# configure for loading wifi module
echo bcm4329 >> /media/p1/etc/modules
#
cp /media/p1/etc/fstab.orig /media/p1/etc/fstab
*** HOW is it done / kernel ***
The kernel source is default asus 10.4.3.9 from asus' website download section. Patched to add cpu overclock from faux's kernel and gpu overclock from motley's kernel (diff file in src.tar.lzma).
Initial kernel config file is taken from stock 10.4.3.9 android, with options added to support ubuntu and oc. path to the nvram for bcm4329 modified.
Ramdisk is mostly that from rabbits 0.8.0, with some modificaitons to enable modem support under android.
*** Todo ****
- modify config / kernel to use nvidia's R16.3 tool to patch wifi ;
- build initramfs anew from tf300t/tg stock android initramfs (currently rabbits modified tf700) ;
- bluetooth and sound ;
- key remapping.
reserved 2
Sounds promising! Keep it up, hopefully other devs see this and help you out :good:
Re: [DEV][WIP] xubuntu on tf300tg 0.1.0
Good job, I will tray luck to night when I back from work.
P.S. I heave no dock - that means no keabord and mouse
Sent from my GT-I9100 using xda app-developers app
Keshukas said:
Good job, I will tray luck to night when I back from work.
P.S. I heave no dock - that means no keabord and mouse
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your interest.
Although I would be happy to have some feedback, it may be a bit early if you don't have a dock : it's completely functionnal with a dock and mouse (I've been using it for work - and build - for a few days), without a keyboard and mouse, you will not go farther than xubuntu' login screen.
Anyway if you still wan't to try it, tell me if you reach xubuntu blue login screen.
Re: [DEV][WIP] xubuntu on tf300tg 0.1.0
On the rabbit Ubuntu for tf700 are virtual keabord (beside clock switch ) witch I use to login to Ubuntu
Sent from my GT-I9100 using xda app-developers app
Assuming this is a dual boot kernel, how does the kernel know where ubuntu is installed if not installed on internal sdcard? Also what's the minimum size partition that can be used?
Moved the thread for ya...
Yes!!! ) Thanks I wait for it )) Xubuntu is my lovely linux, I have it on PC, Notebook, installed on fathers PC and now for tablet!! :good::good::good:
Keshukas said:
On the rabbit Ubuntu for tf700 are virtual keabord (beside clock switch ) witch I use to login to Ubuntu
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I know that and it can be reproduced (look at rabits' /etc/X11/xorg.conf ; and needs packages xserver-xorg-input-multitouch and mtev).
But I have not yet abandonned all hope of doing it the ubuntu way (ie. with evdev).
TechyNut said:
Assuming this is a dual boot kernel, how does the kernel know where ubuntu is installed if not installed on internal sdcard? Also what's the minimum size partition that can be used?
Click to expand...
Click to collapse
Rabits modified the boot image so that it checks /dev/sda*, then /dev/mmcblk1p*, then an img file on /dev/mmcblk0p8. The first which looks to be an ubuntu partition is used as root. He also activated vt (having a console during boot) in is kernel configuration. I reproduced both.
NRGZ28 said:
Moved the thread for ya...
Click to expand...
Click to collapse
Thanks. Induced some noise on other threads
Ramdisk initrd.img in your kernel blob file is not a gzip !!!
Ok starting test
1. Yours kernel most start android if no Linux in /dev/sda1 or /dev/mmcblk1p* or on /dev/mmcblk0p8. Some I understand ?
Now making backup of me tablet ( TF300t ) and flashing kernel to test it.
2. I planing Make Linux on me ExtSDcard (MiniSD 8 gb) and plug sdcard in tablet and then reboot tablet. i hope to start Xubuntu
akurpiel said:
Ramdisk initrd.img in your kernel blob file is not a gzip !!!
Click to expand...
Click to collapse
No. It's lzma.
You can check rabits' git for details : https://github.com/rabits/tf700
Keshukas said:
Ok starting test
...
i hope to start Xubuntu
Click to expand...
Click to collapse
I hope too. Thanks for testing.
Can't mount linux
So I thought I'd give this a try. These are the steps I took to install this:
1. Formated 8gig SD card as ext4
2. Extracted rootfs to SD card.
3. Inserted SD in base
4. copy /system/vendor and /system/etc from your tf into /system on that partition ; copy /data/misc from your tf into /data on that partition
5. fastboot -i 0x0b05 flash staging xubuntu_tf300tg_kernel-0.1.0.blob
6. reboot
6. Kernel boots prompting option, select 1 (linux) and fails to mount partition and boots into android with no other problem.
What am I missing?
ColMustard said:
So I thought I'd give this a try. These are the steps I took to install this:
1. Formated 8gig SD card as ext4
2. Extracted rootfs to SD card.
3. Inserted SD in base
4. copy /system/vendor and /system/etc from your tf into /system on that partition ; copy /data/misc from your tf into /data on that partition
5. fastboot -i 0x0b05 flash staging xubuntu_tf300tg_kernel-0.1.0.blob
6. reboot
6. Kernel boots prompting option, select 1 (linux) and fails to mount partition and boots into android with no other problem.
What am I missing?
Click to expand...
Click to collapse
I have had some occurences of hitting return to fast at the prompt and init not detecting correctly the SD card. So maybe let it timeout into trying to boot linux.
If that does not work, you can choose "s" at the prompt, then from there check into /dev/ which disks / partitions are recognized. Provided that your linux partition is the first and only one on the SD card, you should have a /dev/sda and /dev/sda1. What do you see ?
Also remove any usb drive, which could appear as /dev/sda (and make the sd card appear as /dev/sdb).
Some RABIT write "In-device microSD really bad works." :crying:
I heave problems to boot from sd now i think extract xubuntu in /data/media/linux/rootfs.img
-- Update --
MicroSD - /dev/block/mmcblk1p1
schrdlu said:
I have had some occurences of hitting return to fast at the prompt and init not detecting correctly the SD card. So maybe let it timeout into trying to boot linux.
If that does not work, you can choose "s" at the prompt, then from there check into /dev/ which disks / partitions are recognized. Provided that your linux partition is the first and only one on the SD card, you should have a /dev/sda and /dev/sda1. What do you see ?
Also remove any usb drive, which could appear as /dev/sda (and make the sd card appear as /dev/sdb).
Click to expand...
Click to collapse
Well it looks like it's a no go for me. it could be that I used Minitool Partition Wizard to format because I could not get to my linux machine at the time.
I also tried flashing the kernel over 3 different ROM:
1. CROMI 3.4.4 - Keep failing with Encryption error after boot animation prompting me to reset the device.
2. Hydro 7 - Keep failing with Encryption error after boot animation prompting me to reset the device.
3. CM 10.1 - Failed to get pass boot animation.
I'll have to re-flash Asus stock ROM (10.4.2.20) in order to fully test this, I might have to reformat the sd on linux also.
ColMustard said:
Well it looks like it's a no go for me. it could be that I used Minitool Partition Wizard to format because I could not get to my linux machine at the time.
I also tried flashing the kernel over 3 different ROM:
1. CROMI 3.4.4 - Keep failing with Encryption error after boot animation prompting me to reset the device.
2. Hydro 7 - Keep failing with Encryption error after boot animation prompting me to reset the device.
3. CM 10.1 - Failed to get pass boot animation.
I'll have to re-flash Asus stock ROM (10.4.2.20) in order to fully test this, I might have to reformat the sd on linux also.
Click to expand...
Click to collapse
Me to. I can't boot to android at all
I still tray boot to xubuntu with this kernel and I make img on the internal card
Keshukas said:
Me to. I can't boot to android at all
I still tray boot to xubuntu with this kernel and I make img on the internal card
Click to expand...
Click to collapse
Yeah, I did notice that the kernel looks for the /data/media/linux/.img for a last effort. I was thinking on doing the same.