Related
Hi I am currently running debian on my phone using the method outlines here
http://www.myhangoutonline.com/2009/11/22/install-linux-on-your-g1/
Ive gotta say it quite slow and the method of installation is strange.
Here is a video of someone dual booting NATIVE debian on a G1. Read descrip in video for more info.
http://www.youtube.com/watch?v=tX1BOGl8Fnw
I would really want an option where you boot into recovery (Holding Home) and there is a menu where you can choose to boot into a normal recovery (Amon_Ra's) and the other options would let you choose between what OS you want to boot into like Gnome,OpenMoko,Debian. A normal boot would take you back to android.
Speeking of OpenMoko
there is a tut here
http://wiki.openmoko.org/wiki/OpenMoko_on_HTC-Dream
and i was wonderin weather anyone had tried this because it seems very interesting and would make it possible to bood gnome,debian etc
any opinions are highly appreciated
let me know what you think.
i dunno if im allowed to but bump
donut = 1.6 right?
yes
cupcake = 1.5
donut = 1.6
eclair = 2.0/2.1
Hi!
I've got OpenMoko dual-booting natively on my G1.
When I first looked into the problem, I saw that:
1) OpenMoko option involved boot flashing that would disable booting into Android.
2) Debian option had no ready-to-use rootfs. You had to bring on the usbnet and install debian packages through netinstall. But Debian was able to dual boot, thanks to FukTheRegister's excellent recovery image.
I surely needed something in the middle
I had contacted the OpenMoko port developer, leviathan (a nice guy btw). He's doing some great job of hacking the forked Android kernel to work on HTC Dream together with some other guys. He told me that he was continuing his work on OpenMoko for HTC Dream and that made me want to try it instead of Debian. By the way, FukTheRegister's Debian and Ubuntu ports are based on leviathan's OpenMoko kernel.
What I did to install and dual-boot OpenMoko was:
1) I partitioned my microSD card into three partitions: FAT, ext3, ext3
2) I extracted the OpenMoko rootfs to the third partition (ext3)
3) I made myself a recovery image that would consist of the most recent OpenMoko kernel from gitorious AND FukTheRegister's ramdisk (I just glued them together and threw away some modules to make it fit into 5Mb - maximum for recovery partition images)
4) I copied the recent kernel modules to /lib/modules/ on the 3rd partition of the sd card
5) I copied my recovery image to the sd card and flashed it with flash_image recovery /sdcard/openmoko-recovery-partition3.img right on the phone (under root).
After that I was able to boot OpenMoko with holding HOME + END during the bootup or Android (holding nothing).
See http://vaskas.ru/om-g1/ for all the relevant files.
If you want to try it yourself:
- repeat stage 1) after me
- take the openmoko-rootfs-20091128.tar.gz and repeat stage 2) after me
- copy the openmoko-modules-20100128.tar.gz to /lib/modules/ on the 3rd partition and extract it there
- take the openmoko-recovery-partition3.img and repeat stage 5) after me
P.S. I am not 100% sure that it's going to work for you, because I experimented a lot. It's pretty likely to work though.
hi again vaskas!
thx for work. Tried your setup, it worked for me.
Now it would be nice to have a recovery with an option to boot the second ext3.
Openmoko on Dream ----> nice!
Seems to get a usb connection:
http://wiki.openmoko.org/wiki/Usb_networking
Is a ssh/dropbear server already running on boot?
vaskas thx so much for the huge leap forward ecept im a little confused. so when i hold home + power using ur method it will boot into openmoko, butif i boot normally it wouild go into android, but what if i wanted to boot into normal recovery like amon_ra's?
if i boot into android normally and then run quickboot app and select recovery will it boot opoenmoko or amon_ra's recovery. also with your method does keeping apps on the first ext3 still work? while the second ext3 is for openmoko?
also when making second ext3 partition what size should i make it?
p.s this is sooooooo sick with open moko the possibilities are endless aswell as for people who prefer they can turn openmoko into debian and some time in the future android
so future = openmoko installed instead of android and then being able to boot debian/android or stay in openmoko environment.
also if it's not to much trouble vaskas can u please make a vid and put on you tube or here thx in advance andthx for ur hard work
olvap377 said:
vaskas thx so much for the huge leap forward ecept im a little confused. so when i hold home + power using ur method it will boot into openmoko, butif i boot normally it wouild go into android, but what if i wanted to boot into normal recovery like amon_ra's?
Click to expand...
Click to collapse
No, normal recovery won't be there, since my image replaces it. As far as I know, it's the only way to dual-boot now. If you wish to use your normal recovery image (amon_ra's or cyanogen's), just flash it with flash_image recovery my.img. When you're done with it, flash it back to openmoko's.
olvap377 said:
if i boot into android normally and then run quickboot app and select recovery will it boot opoenmoko or amon_ra's recovery. also with your method does keeping apps on the first ext3 still work? while the second ext3 is for openmoko?
also when making second ext3 partition what size should i make it?
Click to expand...
Click to collapse
I haven't tried quickboot yet.
Yes, Apps2SD still works perfectly with the first of ext3 partitions. I suggest that you make the second one at least 700Mb in size. I've got 500Mb taken by OpenMoko, for instance.
olvap377 said:
also if it's not to much trouble vaskas can u please make a vid and put on you tube or here thx in advance andthx for ur hard work
Click to expand...
Click to collapse
Well, you shouldn't really thank me since I only built a recovery image It's the kernel and ramdisk hackers who rock.
I'll make a vid when I have some free time, but I really suggest that you try it yourself
scheich said:
hi again vaskas!
thx for work. Tried your setup, it worked for me.
Now it would be nice to have a recovery with an option to boot the second ext3.
Openmoko on Dream ----> nice!
Seems to get a usb connection:
http://wiki.openmoko.org/wiki/Usb_networking
Is a ssh/dropbear server already running on boot?
Click to expand...
Click to collapse
FukTheRegister's ramdisk has such an option. I can try to make such a recovery if you need it.
Yes, dropbear is started automatically.
I'd love to see a solid and stable distro that would provide all the things that Android doesn't have, with:
- A compact desktop environment, supposedly e17 or LXDE
- Midori or Google Chrome
- Pidgin
- Sylpheed or Claws for GPG-secured e-mail
- MPlayer or VLC
- FBReader
- evince
- AbiWord
- Gnumeric
- Conky
- Gpodder for podcasts
- Some music player like Sonata
- Cron, sshd, gcc, scripting languages like Python and Ruby
- Zhone for making calls, texting, storing the address book
See, I'm not advocating touch-oriented software. I think we still need touch-capable apps for calling, texting and the address book. The others can be easily manipulated with the trackball and keyboard on G1.
That's what we should aim for IMHO: http://wiki.openmoko.org/wiki/Image:Debian_lxde_zhone.png
OpenMoko project has all this stuff. And that's really awesome. The question is if such an OS should be based on Angstrom (like OpenMoko SHR) or Debian (see http://wiki.openmoko.org/wiki/Debian). My preference is Debian since I'm a long-time Debian/Ubuntu user.
i prefer debian too and i will try this when i get home
i'm sorry for my really dumb question.
but how can i copy something from windows (7) to a ext2 partition?
and if you are creating those partitions, do both ext2 have to be primary or
one primary and one secondary?
thx in advance
lolmensch said:
i'm sorry for my really dumb question.
but how can i copy something from windows (7) to a ext2 partition?
and if you are creating those partitions, do both ext2 have to be primary or
one primary and one secondary?
thx in advance
Click to expand...
Click to collapse
They both have to be primary. I also recommend you to upgrade them to ext3 which is more stable thanks to journaling.
As far as I know, it's not possible to write to extX partitions from Windows. You can copy the files you need to the FAT partition and move them within the phone using Astro or other file manager.
You can mount the second ext3 partition from Terminal Emulator in Android like this:
$ su
# cd /sdcard
# mkdir SD2
# mount /dev/block/mmcblk0p3 /sdcard/SD2
Then it will be accessible from Astro in /sdcard/SD2.
i followed all the steps correctly but it just gets stuch at boot screen if i try to boot into recovery
any advice
maybe this has something to do with the fact that i have ebi1 phone?
pls help i really want this
EDIT:
wow im dumb i figured it out if u look at my sig ull see the way my partitions are setup
i followed all ur steps except each time i changed instructions from p3 to p4 becasue i also have a linux swap so when i installed this recovery it tried to boot from part3 which is my swap and obviously didn;t work
so vaskas can u please for everyone who has a linux swap release another recovery except that boots from part4?
Have also a swap as the fourth partition.. That doesn't matter, I think. Its only important, that the second ext3 is the third partition.
Heres my partition table:
fdisk -l /dev/mmcblk0
Code:
Disk /dev/mmcblk0: 1977 MB, 1977614336 bytes
255 heads, 63 sectors/track, 240 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000ac1bc
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 64 514048+ b W95 FAT32
/dev/mmcblk0p2 65 131 538177+ 83 Linux
/dev/mmcblk0p3 132 223 738990 83 Linux
/dev/mmcblk0p4 224 240 136552+ 82 Linux swap / Solaris
olvap377 said:
i followed all the steps correctly but it just gets stuch at boot screen if i try to boot into recovery
any advice
maybe this has something to do with the fact that i have ebi1 phone?
pls help i really want this
EDIT:
wow im dumb i figured it out if u look at my sig ull see the way my partitions are setup
i followed all ur steps except each time i changed instructions from p3 to p4 becasue i also have a linux swap so when i installed this recovery it tried to boot from part3 which is my swap and obviously didn;t work
so vaskas can u please for everyone who has a linux swap release another recovery except that boots from part4?
Click to expand...
Click to collapse
Ok, try http://vaskas.ru/om-g1/openmoko-recovery-partition4.img - it should work.
I'll try to make a multiple-choice one soon.
thx alot il try when i get home from school
EDIT: still dosent work just freezes at boot screen
plzzzz help any advice
olvap377 said:
thx alot il try when i get home from school
EDIT: still dosent work just freezes at boot screen
plzzzz help any advice
Click to expand...
Click to collapse
Do you mean you're stuck into the "G1" screen? If so, it's a recovery/kernel problem, not really connected with partitioning and stuff. I'm not sure if this openmoko kernel supports EBI1/32A, may be it's the problem
Well I have a dream which is 32b but with ebi1 radio I think this is the problem because amon_ra has a special recovery just for rogers dreams meaning something is different between them
If u could compare amon's rogers to normal recovery and find the differences could u chabge yours to make the latest part 4 file ebi1 compatible?
olvap377 said:
Well I have a dream which is 32b but with ebi1 radio I think this is the problem because amon_ra has a special recovery just for rogers dreams meaning something is different between them
If u could compare amon's rogers to normal recovery and find the differences could u chabge yours to make the latest part 4 file ebi1 compatible?
Click to expand...
Click to collapse
Frankly speaking, I don't think I'm going to have much time for this Since my radio is different, I won't be able to test it properly too.
Actually, I hope that more people join the thread so that we'll be able to solve much more problems together. I wonder where the guys from "Installing Debian on G1" are gone, I saw 2-3 people really interested in native Linux there.
Can you still rename the thread? If so, what do you think about appending something like " - Native OpenMoko and Debian" to it?
EDIT: compared Amon_Ra's recoveries in hex editor, they seem quite different
Hi, I'm new here and I have successfully installed Android 1.5 to my HTC Vogue with HaRET but I would like to have either FroYo or Eclair. How would I go about doing this?
I do not want to flash my rom quite yet. I want to have it dual booting WM6.1 and Android until I'm brave enough to flash it.
Playgr0und said:
Hi, I'm new here and I have successfully installed Android 1.5 to my HTC Vogue with HaRET but I would like to have either FroYo or Eclair. How would I go about doing this?
I do not want to flash my rom quite yet. I want to have it dual booting WM6.1 and Android until I'm brave enough to flash it.
Click to expand...
Click to collapse
First, you need to delete all the android system that already installed, or you could make a backup of your andboot folder - just in case, maybe you want to go back to 1.5 without starting all over again.
Download any Eclair or Froyo build by the dev here in the forum, and place it together with your base file - some build may include these file in their package, then run Haret again.
The process is the same as 1.5 except with the newer files. You will not be able to "update" to a 2.x OS, you have to start from a clean slate, so be aware of that. Make note of all your programs so you know what to install again.
So would I just replace the ZImage file to a newer build or is there other files I require aside from the basefiles?
Eg. If I want Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS12] [7/26/10] version of FroYo do I just download the ZImage file or also the NBH file. From my knowledge, I think the NBH is for installing on NAND and ZImage for SD cards.
I didn't understand my own wording so here is what I mean. Do I need the ZImage or NBH or both?
you'll need a newer ZImage and his androidinstall.tar (or .tgz). You are correct in that the NBH is only for NAND while the ZImage is for SD Card installs.
Thanks a ton! Just downloading the files and I'm ready to test it out
I've tried SDCard load and NAND load for Droid
NAND is much faster and much more stable
Some people have reported issues when running off SDCard that disappear when flashed to NAND
Once you start using Froyo 2.2 and get it sync'ed with google - you won't want to go back to WinMo
Running Froyo RLS 12 @ 320x480 / 160DPI / 500mhz OC
Playgr0und said:
Thanks a ton! Just downloading the files and I'm ready to test it out
Click to expand...
Click to collapse
did you ever get this to work, because I cannot.
I did get it to work and it runs pretty good off the SD card and I am just about to flash it to the NAND after reading the comment above yours from Does_It_Matter.
I used DZO's basefiles for installation.
Does_It_Matter said:
I've tried SDCard load and NAND load for Droid
NAND is much faster and much more stable
Some people have reported issues when running off SDCard that disappear when flashed to NAND
Once you start using Froyo 2.2 and get it sync'ed with google - you won't want to go back to WinMo
Running Froyo RLS 12 @ 320x480 / 160DPI / 500mhz OC
Click to expand...
Click to collapse
I am wanting to flash FroYo to the NAND now but where can I find detailed instructions on how to do so?
Playgr0und said:
I am wanting to flash FroYo to the NAND now but where can I find detailed instructions on how to do so?
Click to expand...
Click to collapse
Actually, there's a FAQ thread for android-vogue,
here.. http://forum.xda-developers.com/showthread.php?t=628353
Anyway, i think incubus super eclair is the perfect one if you wanna try..
Flash Android 2.2
Hello i need help! i Want to flash my HTC touch with Froyo 2.2 or Eclair 2.1.... right now i have daulbooting Android 1.5 and WM 6.1 useing harit....
Links please
link please for nand file n ZImage n process to installl both
Go look in the Vogue Android dev forum, everything is in there.
ok...actually I did go to htc cdma android forum. tried many different android files. can anyone please help me understand how to choose the right file in which the cdma 1x data voice and data would work.
so far all the packages I've tried, I've had 2 problems:
1. after the first normal outgoing/incoming call, the 2nd call will not make the phone ring though the caller can hear the ringback tone.
2. all packages I tried had gsm apn settings instead of a place where you configure the cdma 1x data account.
can someone explain what Im doing wrong? thanks so much.
Hi.
I was checking each build today and noticed that the file structures between builds are different. Example, Matt's or Darkstone's has a rootfs.img and system.ext2 while shubcraft has htcleo_update.tar.gz and root folder, but no system.ext2 nor rootfs.img.
How come the structures are different? Hopefully one or some of the devs can chime in on this.
Oh and how come the initrd.gz cannot be extracted? I tried extracting one and when I opened it I saw a bunch of garbled syntax....
Thanks
i'm not a dev so i can't be 100% sure on this. i can tell you that when i load shubcraft's build up for the first time... the first screen says it is a htc hd2 on the setup screen. the other 2 say n1 or desire i think.
so my guess would be that shubcraft's build is more modified and the others is more image based from the other phones.
1 reason i loved shubcraft's build was that it kept my phone named correctly. i don't like going into my phone's about screen and seeing it named n1 or desire... cause it's not... heh, i have a HD2 and i'm proud of it dangit! =)
w0LfNiNja said:
i'm not a dev so i can't be 100% sure on this. i can tell you that when i load shubcraft's build up for the first time... the first screen says it is a htc hd2 on the setup screen. the other 2 say n1 or desire i think.
so my guess would be that shubcraft's build is more modified and the others is more image based from the other phones.
1 reason i loved shubcraft's build was that it kept my phone named correctly. i don't like going into my phone's about screen and seeing it named n1 or desire... cause it's not... heh, i have a HD2 and i'm proud of it dangit! =)
Click to expand...
Click to collapse
Actually, ita very easy to change the phones name on Android, im on Darkstones Froyo v1 and i changed it from saying" HTC Desire" to "HTC Leo" going to switch it back to HD2 tho. But the filesystems im not to sure about.
Sent from my HTC HD2 running DarkStone HD2Froyo v1
It's just because Shu8i do not supply system and userdata images with it's build, instead he relay on creating that files on first start of Android, that is the main reason Shu8i's build take so much more time to start up at first.
It's just a trade-off, less file size you download, more time to wait for first boot.
bangsters said:
Hi.
Oh and how come the initrd.gz cannot be extracted? I tried extracting one and when I opened it I saw a bunch of garbled syntax....
Thanks
Click to expand...
Click to collapse
It can just use
gunzip initrd.gz
cpio -d -i < initrd
Its a gzipped cpio file
mr_billionaire said:
Actually, ita very easy to change the phones name on Android, im on Darkstones Froyo v1 and i changed it from saying" HTC Desire" to "HTC Leo" going to switch it back to HD2 tho. But the filesystems im not to sure about.
Sent from my HTC HD2 running DarkStone HD2Froyo v1
Click to expand...
Click to collapse
guess i'm not that smart just yet. heh.
There are currently (from the files I've checked) two ways of packaging Android builds; the "Zego" way and the "XDAndroid" way.
Inside both builds, you'll find a haret (kernel loader), clrcad (enables audio in android), initrd.gz (initial root filesystem), zImage (kernel), and startup (the script haret uses to set up linux).
The XDAndroid-based builds have, additionally, a rootfs which is a big package intended to allow the same XDAndroid build to run on a wide variety of devices.
IMHO, the Zego initrd is much better because: 1. it allows for "otapackage" updates, 2. It's for HD2 only, 3. It's much cleaner and can run AOSP builds straight from a make (as long as you specify that the build images use ext2).
The disadvantage, though, is that it uses a regular init.rc instead of a hero one (only difference is that hero core jars aren't loaded into the classpath), so it takes a slight modification to get sense builds running.
The XDAndroid initrd, instead, just loads the rootfs and then from the rootfs several scripts run to determine the kind of device that's being used and then when the device is detected, the files used for that device (included in the rootfs) are "pushed" to the system image to allow all hardware to work correctly.
I tried to run an android build (froystone). i see some people have android up and running in 5 minutes. It looks like my system is booting up after 5 minutes. the screen is black with white text. How long should this go on? how will i know android is running?
charles1874 said:
I tried to run an android build (froystone). i see some people have android up and running in 5 minutes. It looks like my system is booting up after 5 minutes. the screen is black with white text. How long should this go on? how will i know android is running?
Click to expand...
Click to collapse
dude just leave it alone and let android do what it do
charles1874 said:
I tried to run an android build (froystone). i see some people have android up and running in 5 minutes. It looks like my system is booting up after 5 minutes. the screen is black with white text. How long should this go on? how will i know android is running?
Click to expand...
Click to collapse
for a faster booting from the phone off to android fully up, run a plain version of WM, then any choice of android
It would really help us if you let us know what windows mobile rom,android rom, and radio software.
The size of the winmo rom shouldnt have any effect on how fast android boots. I will say the faster the sd card the faster android boots because its booting from the sdcard.
windows mobile rom is:2.13.531.1*90953) wwe
radio: 2.10.50.26
android rom: [BUILD][02.09.2010][FroyoStone Sense - V2][Kernel: darkstone 2.6.32.9 #3]
i let it run thru the night, and it was still loading after about 6 or 7 hours
charles1874 said:
windows mobile rom is:2.13.531.1*90953) wwe
radio: 2.10.50.26
android rom: [BUILD][02.09.2010][FroyoStone Sense - V2][Kernel: darkstone 2.6.32.9 #3]
i let it run thru the night, and it was still loading after about 6 or 7 hours
Click to expand...
Click to collapse
You can either delete the data.img or you can format the sd card and try again.
ive been able to run every build without problems.
using energy's latest titanium build and radio 2.11
ok, i will format the card again. But should it take that long to load?
Not unless its the desirehd build
charles1874 said:
ok, i will format the card again. But should it take that long to load?
Click to expand...
Click to collapse
No. it shouldn't take more than 10-30 minute depending on how big you want your system storage to be (512, 1024, 2048). if android hangs during setting up (black screen with text), please report back to tell us exactly what it says when progress stall. This way we can at least have some idea of what's causing the stall. Formatting the sd card usually fix your issue. Having the latest radio is also recommended. If you don't know what radio version you have, look in the wmo hd2 section for more info on this. Good luck.
Currently, i am working on Slackware, but i just discovered that Fedora and Arch Linux can put on HTC HD2, too, anyone want more systems?
Please, finish your work first, then think of other distros, OK?
This is just a poll, i will still go on with my slackware, i just want to hear more suggestions
well none of already existing distros are functional or even WORKING
so please, finish work if you can first
well none of already existing distros are functional or even WORKING
Click to expand...
Click to collapse
What do you mean?
Do you mean no camera, no sound, no gps?
Almost every linux distro on MAGLDR is not working properly. Either touchscreen fails or other components. VNC version is hard to use and cannot into USB-Host
No magldr support, no easy way to change the kernel, no usb host, no wifi, no touchscreen... That's the basic stuff.
I've got a fedora 12 (or 13, can't remember which) that I was working with for a while in conjunction with the back track I was working with.
I was successful in getting it started up, but gnome for it is tricky to get going through vnc. Command line works fine though, as well as it having a lot of the needed packages for things to work.
At one point in time I had it booting through wm6 using the v0.3 kernel from dcordes Ubuntu version, but I ran out of time before getting touch working properly and such.
I can get a copy of it up sometime today or to morrow if you guys are interested
A few notes...
The fedora 12 and 13 were easier to setup and configure, but 14 and on has a lot of package dependancies that HAVE to be filled by hand. There's almost 300+ you need to track down manually, not to mention THIER dependencies too.
At the time I was working on it, f15 was in alpha and 16 and 17 were near nonexistent, so I was working with 12 and 13.
The good news is that 12 and 13 will basically work for ANY device (it targets arm V5, so our arm V7s can use it with out changes. When working with 15 or higher, they may not work properly (or at all) as many of the packages are not compiled as "no_arch" so there's a lot of packages that need manual installation as well.
Hit me up if you have any questions!! I'll have fedora up in its own post sometime over the next day or two
Sent from my HTC Sensation Z710e using xda premium
Both of you don't remember that, i am not using MAGLDR, and the option in the MAGLDR is "BOOT ANDROID" NOT "BOOT LINUX".
Moreover, i am producing linux on hd2 with HaRET, not MAGLDR.
"Everything"(exclude, gps, etc) are working on HaRET's version.
z3nful said:
I've got a fedora 12 (or 13, can't remember which) that I was working with for a while in conjunction with the back track I was working with.
I was successful in getting it started up, but gnome for it is tricky to get going through vnc. Command line works fine though, as well as it having a lot of the needed packages for things to work.
At one point in time I had it booting through wm6 using the v0.3 kernel from dcordes Ubuntu version, but I ran out of time before getting touch working properly and such.
I can get a copy of it up sometime today or to morrow if you guys are interested
A few notes...
The fedora 12 and 13 were easier to setup and configure, but 14 and on has a lot of package dependancies that HAVE to be filled by hand. There's almost 300+ you need to track down manually, not to mention THIER dependencies too.
At the time I was working on it, f15 was in alpha and 16 and 17 were near nonexistent, so I was working with 12 and 13.
The good news is that 12 and 13 will basically work for ANY device (it targets arm V5, so our arm V7s can use it with out changes. When working with 15 or higher, they may not work properly (or at all) as many of the packages are not compiled as "no_arch" so there's a lot of packages that need manual installation as well.
Hit me up if you have any questions!! I'll have fedora up in its own post sometime over the next day or two
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
I just downloaded the rootfs, haha, but i will start on archlinux later first when i finish my slackware...
http://fedoraproject.org/wiki/Architectures/ARM
I think you can try that Alpha
The fedora 12 and 13 were easier to setup and configure, but 14 and on has a lot of package dependancies that HAVE to be filled by hand. There's almost 300+ you need to track down manually, not to mention THIER dependencies too.
Click to expand...
Click to collapse
Dependencies... I hate this things, i used whole month to deal with dependencies on my slackware, slackpkg don't care about it!
dependancies are NOT fun lol
That a what I like about the vnc way of loading it, easy to diagnose the problems and find the packages
Sent from my HTC Sensation Z710e using xda premium
hopkinskong said:
i am not using MAGLDR, and the option in the MAGLDR is "BOOT ANDROID" NOT "BOOT LINUX".
Click to expand...
Click to collapse
You might want to notice that this option is called that because it has been used to boot only Android ROMs, since no linux distros were available for magldr.
hopkinskong said:
Moreover, i am producing linux on hd2 with HaRET, not MAGLDR.
"Everything"(exclude, gps, etc) are working on HaRET's version.
Click to expand...
Click to collapse
Also, the majority of HD2 users here use magldr because they use Windows Phone 7 or Android on NAND as a daily driver. If I were you, I would consider making a magldr-compatible version as well.
Haret is great, but WinMo days are over
MAGLDR is great thing, as allows for many different OS'es on one system without much trouble. Not having working linux distros on MAGLDR is a shame.
Thats what i get for not re reading ny post lol
I ment mmcblk1p3, not mmcblk0p3
If you can provide me with a kernel that has a ramfs that loads the system from mmckblk1p3 I can help a bit with the magldr boot, just don't have time to go through the ramfs changes (and I forgot how to do it again lol)
The reason I use that partition is it is SO much easier to modify across systems
Sent from my HTC Sensation Z710e using xda premium
Don't remember that, i am just a system(os) developer, i am not a bootloader developer, if you want linux boot on MAGLDR, ask DFT team!
Any hope for Slackware ETA?
New magldr news http://forum.xda-developers.com/showpost.php?p=24609524&postcount=1032. It seems that hopkinskong's decision not to concentrate on magldr booting for Slackware may pay off.
Also what price a 1024 HD2 now
hopkinskong said:
Don't remember that, i am just a system(os) developer, i am not a bootloader developer, if you want linux boot on MAGLDR, ask DFT team!
Click to expand...
Click to collapse
But there is no need to do anything bootloader-related... Check out MAGLDR topic at development section - Ubuntu 10.04 boots on MAGLDR/CLK with just only changing the kernel to a newer one. Wifi and touchscreen work (after copying wifi firmware and changing xorg.conf). The only thing that may be bootloader-dependent is probably USB host, but that's going to be fixed in new MAGLDR as I heard. And I think people would be still happy to have a nice MAGLDR version even without USB host. Please think about that, I can't understand how not a one dev cares about MAGLDR when it looks like it's easy to fix that. I'd love to have some Slack (or even better, Arch) on HD2
I think we should wait for new MAGLDR. It could revolutionize the way we use systems now.
I can't see how these MAGLDR changes would affect desktop Linux (ubuntu/slackware/arch etc.) on HD2. It's booted from SD anyway, it won't be installed to NAND. Simply because uncompressed Linux distribution needs more than 1GB of space, and we have either 0,5 or 1 GB. So why wait?
OK, new MAGLDR will release?
Yes, the new kernel's USBHOST is not working, and its hard to fix it, the USBHOST crashed with the battery driver(linux_on_wince_htc kernel). To use linux in MAGLDR, we need to fix that first.
For Slackware ETA:
I need to find another SD card, i was building my rootfs few days ago, but my SD card "crashed" for some reason, my computer even don't recognize my card anymore, i have a half-built rootfs backup-ed on my computer, when i have another 8G SD card available, i can start work again. (I remembered that my card has a 5-year warranty, but i need to find it out first)