Hello,
Anyone interested in porting linux to HTC Hermes? The Samsung processor is currently supported by vanilla 2.6 kernel
I tried running GNU HaRET 2006070419 version, here's the output of some commands:
Code:
# telnet 192.168.1.23 9999
Trying 192.168.1.23...
Connected to 192.168.1.23.
Escape character is '^]'.
Welcome, this is GNU/HaRET running on WindowsCE v5.1
PocketPC
HERM200
Minimal virtual address: 00010000, maximal virtual address: 7fffffff
CPU is ARM ARM arch 4T stepping 0 running in system mode
Enter 'HELP' for a short command summary.
-----------------
FB1: form=1 bpp=16 fbaddr=4E800000/10800000 x=240/2 y=320/480
FB0: form=160 bpp=16 fbaddr=4E800000/10800000 x=240/480 y=320/480
HaRET(1)# dump wince
Wince information
curr_perm: 00010001, memdiv: rdisk= 64 ram= 12493 pagesize= 4096
memdiv1: rdisk= 64 of 14612 ram= 12493 of 12493
memdiv2: 3 rdisk= 64 of 14612 ram= 12493 of 12493
OEMINFO: ncha=9
OEMINFO: HERM200
OEMINFO: HERM200
PLATFORMTYPE: PocketPC
PLATFORMTYPE: PocketPC
machine_id:0
audio_innum=1, audio_outnum=1
32snapshot failed
I don't think the Samsung SC32442A-400MHz processor is supported by this version of HaRET, but I found a page in russian where there is a version of HaRET for s3c2442 processors available!!
Here is some interesting output of this haret version:
Code:
# telnet 192.168.1.23 9999
Trying 192.168.1.23...
Connected to 192.168.1.23.
Escape character is '^]'.
Welcome, this is HaRET running on WindowsCE v5.1
Minimal virtual address: 00010000, maximal virtual address: 7fffffff
CPU is ARM ARM arch 4T stepping 0 running in system mode
Enter 'HELP' for a short command summary.
HaRET(1)# cpudetect
Warning: Detected CPU family: S3C24XX
HaRET(2)# cpuwgpio 1
Warning: Ready to watch s3c24xx GPIO
f0004 - GPA: 1
f0014 - GPB: 4e
f0024 - GPC: 3621
f0034 - GPD: 0
f0044 - GPE: f7e8
f0054 - GPF: d3
f0064 - GPG: 24be
f0074 - GPH: 7f
f00d4 - GPJ: 14b0
GPE changed to 0000f7e8
GPE changed to 0000f7c8
GPE changed to 0000f7e8
[...]
HaRET(3)# dump mmu mmu.txt
The MMU dump hungs the device
Samsung has also published manuals and datasheet of the processor, available here:
http://www.samsung.com/products/sem...ationProcessor/ARM9Series/SC32442/SC32442.htm
More information and kernel patches for Samsung SC32442A procesor can be found here:
http://www.fluff.org/ben/linux/
So, we have a lot of work to do... any developers able to help?
Wiki page
I've created a page on the wiki for the Hermes Linux port here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Linux
Forgive me for asking, but why would you want to put Linux on this device?
We've got enough issues getting support for the WM5 ROMs, don't you think?
If there's a good reason, I'd love to know what it is!
goestoeleven said:
Forgive me for asking, but why would you want to put Linux on this device?
We've got enough issues getting support for the WM5 ROMs, don't you think?
If there's a good reason, I'd love to know what it is!
Click to expand...
Click to collapse
If there's a mountain to be climbed... :wink:
That's what I figured... Good luck!
Well, may be climbing that mountain is the main reason. But here you have another, in my opinion, interesting reason:
http://www.linuxdevices.com/articles/AT7937511405.html
Re: Linux on HTC TyTN / Hermes
pof said:
The MMU dump hungs the device
Click to expand...
Click to collapse
What about running the "DUMP MMU" with gnuharet ? You can also try other commands
(POWERMON 10; NLED*)
They are ported from itsutils and should not depend on the CPU.
Hey cr2! Sorry for the late reply but I didn't see your post before
With gnuharet, powermon 10 works, shows this:
Code:
HaRET(4)# powermon 10
2146258 1 70 % 3792 359 0 410 0 0 -1 -1 0 255 255 0 -1 -1 0 0 0 4
2147264 1 70 % 3792 359 0 410 0 0 -1 -1 0 255 255 0 -1 -1 0 0 0 4
[...]
Also nled* commands work, I can make the device vibrate with "nled on 1" and stop it with "nledoff 1", etc..
The MMU DUMP was ok with gnuharet, see attached file!
I also updated the wiki page with some info about the Hermes hardware, as there are now pictures of the chipsets available, see this post:
http://forum.xda-developers.com/showthread.php?t=279151
yep.
got one. busy with htc sable. start when i'm done or bored.
Glad to see that lkcl and cr2 got an Hermes too
This sure means we'll see a linux kernel booting soon!
pof said:
Glad to see that lkcl and cr2 got an Hermes too
This sure means we'll see a linux kernel booting soon!
Click to expand...
Click to collapse
It sure would be damned sweet to get rid of M$'s OS on this device! By the way, how is Qtopia and other Linux PDA "stuff" doing these days? The last time I tried it was back on my IPAQ in... 2001 I think.
You have GPE and Opie as the main graphic environment used in handheld devices those days.
It seems that soon a new environment called OpenMoko will be released under a free license too, this one is more phone-focused than the others.
pof
thanks for the post , im glad i came across it,
somethings been on my mind for the last few days, a mate at work is always on about Linux so it got me thinking, id like to give it a try on my TyTN
Iv got 2 questions for you,
first is there a newbie guid to running Linux on PDA's il have a look on wiki next im sure il find something. is there any that you guys can recommand which you have found helpfull.
2nd Now this is the question thats bugging me,,,,,
Can we run 2 OS on a PDA????
is this poss? to have a dual boot option when the PDA starts so we can select either Linux or WM05, both on there own will run on the device, how about installing both at the same time, and then being able to boot with one,
just some thoughts>?
I might start another thread on this just incase this thread isnt getting anymore traffic
well time to get back to work and start doing the job im actually getting paid to do
N2h said:
first is there a newbie guid to running Linux on PDA's il have a look on wiki next im sure il find something. is there any that you guys can recommand which you have found helpfull.
Click to expand...
Click to collapse
Depends very much on which device you want to run linux, on the Hermes is not possible yet. But for the Universal or BlueAngel you have some guides here:
http://www.handhelds.org/moin/moin.cgi/Universal
http://www.handhelds.org/moin/moin.cgi/UniversalHowtoInstallLinux
http://www.handhelds.org/moin/moin.cgi/BlueAngel
N2h said:
Can we run 2 OS on a PDA????
is this poss? to have a dual boot option when the PDA starts so we can select either Linux or WM05, both on there own will run on the device, how about installing both at the same time, and then being able to boot with one,
Click to expand...
Click to collapse
You have WM5 on your flash, and Linux on the SD card. You start your pda with WinCE and then browse to storage card and run gnuharet.exe which will "destroy" WinCE and boot the Linux kernel and initrd found on FAT32 partition of SD card. Then from initrd, you mount the root filesystem on another partiton of the SD card...
pof thanks for the quick reply
il b ereading up on the guide links you have given,
also just to clarfy point 2
-----------------------
You have WM5 on your flash, and Linux on the SD card. You start your pda with WinCE and then browse to storage card and run gnuharet.exe which will "destroy" WinCE and boot the Linux kernel and initrd found on FAT32 partition of SD card. Then from initrd, you mount the root filesystem on another partiton of the SD card...
Today 02:05 PM
------------------------
by this means can we boot with WM and then run Linux from SD card once this is run would WM be completey wiped from device memory? so any data we had on the device for WM will be lost,
just so im explaing myself propley, i was wondering if you can keep both OS on the device and SD card boot from WM when you need that and when you want to use Linux boot with Linux but without losing you WM5 data etc.
same as some of the apple macs that can boot with windows and apple oc from the same machine and switch between the differnt OS's
thanks for the quick reply,
Iv got a collegue with universal I wonder if he will let me borrow his Universal??? lol
You can boot linux from SD card and you don't loose any data on WM5 when you shutdown linux and go back to WM5.
pof thanks mate,
il be hopefully running Linux on my Tytn,
you never know,,,,,,,,,,, by the time i learn and update myself on linux it may running on our devices
all the best to anyone else also trying!!!
I would love to try and help you guys, but i haven't got much experience in these kind of stuff. Where should i start looking for more info on the project?
The status of hermes linux port is always updated at this wiki page:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Linux
All development happens at #htc-linux in freenode irc server, but unfortunately as of now there's not a booting kernel yet for the Hermes, so you need some knowledge of low level programming to help at this stage.
i actually have studied low level programming with assembly and c, but i'm not that familiar with kernels :-/.
Related
I have been following the Android scene here pretty regularly but the os I have always really wanted is a full fledged Linux. I heard about, and wanted a N900 because of Maemo but I'm too poor to buy one . I then heard about the Mer project https://wiki.maemo.org/Mer to port Maemo to other devices and saw it booted on the kaiser http://forum.xda-developers.com/showthread.php?t=565480. On page two of that thread it is stated that someone (Mdrobnak) got it up and running pretty well on his Fuze with a couple tweaks to Xorg.conf, the kernel, and to the splash screen (resized to 640x480). I've been working over the past few days on getting it to start on my fuze but haret keeps giving errors about pc_clk_disable. I resized the splash, changed Xorg.conf to be 640x480 and did the rest of the directions on the Kaiser thread, but no luck. I would love to get a port of this going, as being able to use ~95% of Ubuntu packages working on my phone would be awesome. I wasn't quite sure how to patch the kernel; that would be the zImage, right? Any suggestions?
I'm going to be on #mer and #htc-linux irc on freenode quite a bit until we get this working well if anyone wants to discuss things, not that I can contribute much.
Would it be possible to create a rootfs.img file similar to how XDANDROID does it for people too lazy to partition their card or just plain suck like me?
Sounds interesting! Keep us updated!
Oh god! Ill be in 7th heaven if it's going to be done!
I think you can use the zImage of xdandroid, maybe it'll work
I tried the xdandroid zImage but it didn't work. This is really a call for help. I really don't know what I am doing, lol. I'm not even close to being a dev. Try out the steps on the Kaiser thread but use the stable 0.16 distribution as the testing links don't work. See if you can figure anything out.
Maemo on the Raph ? that would be great! maybe we could run it in dual boot with android and abandon WM for ever !
To get X working, use glemsom's kernel, and add msm_fb.fix_x=1 to cmdline.
For touchscreen, you might want to add msm_ts.raw=1 (but it can also work without it)
phhusson said:
To get X working, use glemsom's kernel, and add msm_fb.fix_x=1 to cmdline.
For touchscreen, you might want to add msm_ts.raw=1 (but it can also work without it)
Click to expand...
Click to collapse
Thanks, phh. Will try it when I get home.
that's the old and ugly msm_fb refresh hack.
I will update here once I have xorg working on kovsky and kaiser.
Man, I actually feel like this is getting places. Got Phhusson from XDANDROID and dcordes from the original Android on Diamond thread. Quite the star power.
@dcordes: What needs to be edited to use VGA; just the first screen resolution dimensions in Xorg.conf?
what image are you using?
I'm using the Smartq5 from here: http://wiki.maemo.org/Mer/Releases/0.16. My main problem is with the kernel though I think; haret hangs after about 15 seconds; I'm gonna create a log of it.
On my Raph300 I can login on the terminal using the Q5 image. I was using the latest zimage from gelmsom. But kernel is screaming some stuff a bout a clock not having an ena bit and something about an rpcrouter being blocked. When I try to start X, I get an error loading libpicacces.so.0
I get that same error, but Haret hangs when I get it. Please share what you did: e.g. editing xorg, exact zImage used, what you used to partition, your default.txt, whether you edited the splash screen image etc. I'd like to get a database of sorts of people's configurations. Good to know though. Did you add Phhusson's tip to default.txt?
"To get X working, use glemsom's kernel, and add msm_fb.fix_x=1 to cmdline.
For touchscreen, you might want to add msm_ts.raw=1 (but it can also work without it)"
Yes i added the msm_fb.fix_x=1 to the cmdline. Unfortunatly it is not the solution for this problem. We have got some trouble with the libraries. Maybe something is missing.
LordKiwi said:
Yes i added the msm_fb.fix_x=1 to the cmdline. Unfortunatly it is not the solution for this problem. We have got some trouble with the libraries. Maybe something is missing.
Click to expand...
Click to collapse
Last time I tried it worked automatically (I mean for X video output.) with msm_fb.fix_x=1
Sorry it works. JesusFreak and I extracted the tar file the wrong way.
I should have type tar -pxvf. I forgot the p which is very important.
Now it stops with a different error.
Code:
(**) FBDEV(0): using shadow framebuffer
(II) Loading sub module "shadow"
(II) LoadModule: "shadow"
(II) Loading /usr/lib/xorg/modules//libshadow.so
(II) Module shadow: vendor="X.Org Foundation"
compiled for 1.6.0, module version = 1.1.0
ABI class: X.Org ANSI C Emulation, version 0.4
(EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument
(EE) FBDEV(0): mode initialization failed
Fatal server error:
AddScreen/ScreenInit failed for driver 0
Dang it; I just can't get it to work. I'm the thread starter and I can't do it, lol. Here's what I did:
1. Downloaded 0.16 stable smartq5 rootfs.
2. Extracted the tar to my home folder. (Now that I think of it; I did it with archive manager not the command line, so no -p setting or anything. That could be the problem.)
3. Edited the xorg.conf file to change the resolution to 640x480.
4. Changed the splash screen size to 640x480.
5. Formatted my sd card to ext2 for 1.5 gb and fat32 for .5 gb using command line following these directions for ext2: http://wiki.maemo.org/Mer/Documentation/SmartQ_Installation_for_the_Windows_user and gparted for fat32.
6. I then used the directions on the same pagee as before to copy the file, except using cp instead of mv.
7. I copied haret, a zImage, and the startup.txt that I renamed to default.txt and edited to the fat32 partition.
8. I started Haret.
I attached my default.txt.
The formatting is done correct. You should try to use the tar command line wich you can find on the same page. It should solve the problem of loading the library.
•Type sudo tar -pxzvf *.gz and press return. This will now untar the entire 'rootfs' to the card. (Install Mer).
LordKiwi said:
Sorry it works. JesusFreak and I extracted the tar file the wrong way.
I should have type tar -pxvf. I forgot the p which is very important.
Now it stops with a different error.
Code:
(**) FBDEV(0): using shadow framebuffer
(II) Loading sub module "shadow"
(II) LoadModule: "shadow"
(II) Loading /usr/lib/xorg/modules//libshadow.so
(II) Module shadow: vendor="X.Org Foundation"
compiled for 1.6.0, module version = 1.1.0
ABI class: X.Org ANSI C Emulation, version 0.4
(EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument
(EE) FBDEV(0): mode initialization failed
Fatal server error:
AddScreen/ScreenInit failed for driver 0
Click to expand...
Click to collapse
I'm an idiot....... I saved my startup.txt as startup.doc. That's why X didn't start.
0.17 release
Is possible run the 0.17 realease in raphael more fast than in N810?
kaiser ubuntu port based on zubuntu by Omegamoon for Sharp Zaurus was successfully launched on HTC Nike!
Instructions:
1. download kernel
http://84.23.71.227/kerneloftheday/zImageUbuntu
2. download ubuntu basefiles and rootfs
3. place ubuntu.img, haret, initrd.gz and zImageUbuntu to Storage Card/ubuntu/
4. place this default.txt there too
Code:
set RAMADDR 0x10000000
set MTYPE 1724
set KERNEL zImageUbuntu
set initrd initrd.gz
set cmdline "pm.sleep_mode=1 mddi.width=320 mddi.height=480 lcd.density=160 board-htcnike-keypad.keypadlayout=1 board-htcnike-keypad.sticky_timer_time_ms=350 no_console_suspend"
boot
5. change board-htcnike-keypad.keypadlayout=1 to 0 if you have 20key nike.
6. run haret and press "Run", ubuntu & kernel will be loaded to login prompt, login with username root and no password, you will get root shell.
7. write
Code:
export TSLIB_TSDEVICE=/dev/input/event0
ts_calibrate
and calibrate your screen.
8. write startx and see LXDE running on your nike! you've got real linux box in pocket!
Note, rootfs for ubuntu needs 1GB of free space on your sdcard!
For now, you cannot work with screen, we have some difference from kaiser panel's, i.e. ubuntu gui is completely unusable, this thread were started to find out why.
based on this thread from kaiser forum.
Credits: dzo, Omegamoon, domy007, mblaster and guys from Rhodubuntu thread.
I dont get any response when i try to calibrate screen on niki 200
thats strange, it must work.
I will debug on touchscreen problems, but ubuntu running and that is great, now we have only input-devices problems, and this is more better than nothing.
Sounds great, but wouldn't it be better to try something smaller like puppylinux or Feather linux ?
zubuntu is only we have compiled for ARM and working with our hardware that starts X and tested on other htc's devices.
rzk333 said:
zubuntu is only we have compiled for ARM and working with our hardware that starts X and tested on other htc's devices.
Click to expand...
Click to collapse
Ok thanks for the information, did some reading before and was always wondering why they use ubuntu but this answer set things straight.
Greetz,
Great to see a full linux distro around for htc devices. I will fix the '_' tomorrow... Any other missing characters?
How is the speed of ubuntu? Is it very sluggish or usable?
'=' character maybe, for export line.
zImageUbuntu is updated (your link is still valid).
'=' and '-'are on '*'-button, '_' is Alt-
I have included the msm_fb_refresh and the keypad changes into my auto-updated-kernel, so you should be able to use the fresh kernels from my thread with ubuntu if you want recent updates (zImageUbuntu is not automatically updated).
got some progress,
1) msm refresh thread seems to disable sleep mode in android, thread polls framebuffer many times in second and drains battery.
2) linux logo on bootup must be disabled - logo gets over ts_calibrate's first crosshair point.
2) still trying to make touchscreen and tslib friends - i2c bus debug messages logs saying that touchscreen is connected and recieves data correctly.
found some data:
/dev/input/event0 - htcnike-kbd
/dev/input/event1 - htcnike-ts
but still no data from touchscreen...
rzk333 said:
got some progress,
1) msm refresh thread seems to disable sleep mode in android, thread polls framebuffer many times in second and drains battery.
2) linux logo on bootup must be disabled - logo gets over ts_calibrate's first crosshair point.
2) still trying to make touchscreen and tslib friends - i2c bus debug messages logs saying that touchscreen is connected and recieves data correctly.
found some data:
/dev/input/event0 - htcnike-kbd
/dev/input/event1 - htcnike-ts
but still no data from touchscreen...
Click to expand...
Click to collapse
Disabled msm refresh thread from the android kernels again. The kernel you linked in your first post is now automatically updated with anything new in the repository. Bootlogo is disabled, too. Good luck with tslib, let me know if when you need something else to be hacked into the kernel.
mblaster
I've just test the usb ether function in the zImage from the post
showthread.php?p=6675397
and it works just fine.
(Just when I had managed to make adbd works... but ssh is more reliable)
Thanks gTan64.
wow, that is good, now I can dump system state without hours of keyboard typing
I've managed to get internet by usb (cdc only) thanks to gTan64: just apply the patch from is post ("Debian on the vogue"), you can extract it from the download links.
And the TOUCHSCREEN WORK!!!!!!!
But you need to compile tslib from the tslib git (github.com/kergoth/tslib.git), the one in the rootfs from this post doesn't work.
Will make a more complete post later, I think.
Bye.
Ubuntu always shows me a black screen when I try to startup it!
What can I do make it work?
omg, I knew that something is wrong with tslib in this rootfs!
thanks for r&d, if you will make some packages & mans, I'll add them to first post.
Maybe you can upload some pics ?
But you need to compile tslib from the tslib git
Click to expand...
Click to collapse
I tried to compile - but no luck, autoconf fails to make configure...
I also uploaded debian rootfs and posted links in gTan's Debian on Vogue thread.
nothing happened last month?
Hello, every SD build users,
Savan told me a method about how to get the real WiFi MAC address from the kernel (i.e. the same MAC address you see on WM6.5).
However, we need to get the memory dump of HSPL running WM6.5 and your real MAC address, so Savan can find out the MAC offset and write it to kernel for getting the real WiFi MAC address.
I'm running NAND ROM now and I'm lazy (have no free time) to flash back to WM6.5 just for dumping HSPL and then flash back to MAGLDR later.
Thus, I would like to request helps from you, the SD build users running WM6.5.
If you can help, please use the following steps to dump the HSPL. Thanks.
Backup your original "startup.txt" in Android folder.
Place the following command in "startup.txt".
Code:
pwf hspl.dump 0x0 0x100000
Start HaRET and it will automatically run the above command.
Check if file hspl.dump exists in your SD card.
Send me hspl.dump and your real WiFi MAC address you see on WM6.5.
Reference: http://htc-linux.org/wiki/index.php?title=HaRET_Documentation#HaRET_commands
Update:
We can get the real WiFi MAC address from SPL/HSPL when using SD builds on WM. (Please use r12 kernel if you want to try it.)
However, we cannot get the real WiFi MAC when using MAGLDR and cLK bootloaders.
here you are:
MAC
00-23-76-8e-23-dc
let us know... thank
Marco
Real MAC:
38: E7: D8: 8E: 27: 6D
Thank you very much to marco.palumbi and kajos.
The correct command is 'pwf hspl.dump 0x0 0x100000'.
Hello marco.palumbi and kajos,
Thanks for your help.
Which version of HSPL do you use?
Is it SPL 2.08.HSPL?
I can find 0023768E23DC at 0xFC028 when HEX editing marco.palumbi's hspl.dump. (Nothing at 0x90028.)
But I can find 38E7D88E276D at 0x90028 and 0xFC028 when HEX editing kajos' hspl.dump.
These two memory dumps seem to be different in terms of format.
When I add 0x90028 or 0xFC028 to kernel source code, I still cannot read MAC address from kernel.
Maybe Savan and I miss something.
I'm trying different possible methods.
tytung said:
Hello marco.palumbi and kajos,
Thanks for your help.
Which version of HSPL do you use?
Is it SPL 2.08.HSPL?
Click to expand...
Click to collapse
My Bootloader shows SPL-3.03.0000
I don't use HSPL
R 2.15.50.14
G 15.42.50.11U
D 3.14.04666
is HSPL necessary for this?
Hi tytung,
I have the latest official HTC rom installed on my Italian EU device.
booting the device with vol- pressed I read:
PB81100 HX-BC
SPL-3.03.0000 XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x30
let me know if you need more information
Thanks to both of you.
I'm not sure whether SPL and HSPL have different format.
I changed my HD2 to HSPL 2.08 in order to install MAGLDR and flash NAND ROM.
And the new kernel with real MAC fix doesn't work for me on my NAND ROM.
WiFi MAC = ff:ff:ff:ff:ff:ff and bootloop.
Savan, the kernel developer of HTC Photon (HD Mini, another WM6.5 phone), told me that his real MAC fix may only work with SD build.
...but you've detected the realMAC at 0xFC028.
May be there a different way for implementing this?
Hi!
My MAC: 7C-61-93-33-F1-CF
With Power and Vol- i get:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x50
CotullaHSPL 0x50
hi
I am not expert on the HD2 device but I have some experience with embedded systems.
just to better understand and give some help.
the problem can be splitted in two steps:
1) find from somwhere in the device the assigned MAC addres. this seems to be at memory phisycal address 0xFC028 on kajos and mine device.
2) modify the kernel driver in order to use the address retrived from the prvious step.
tytung, which step is failing in your implementation?
to debug you can try
a) to printk() the phisical addres at 0xFC028 (so you can see it on dmesg)
b) modify the ETH kerrnel driver to use a string passed as kernel command line.
the last could be a easy solution for SD users becouse this way they can put the MAC on startup.txt...
zboq said:
Hi!
My MAC: 7C-61-93-33-F1-CF
With Power and Vol- i get:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x50
CotullaHSPL 0x50
Click to expand...
Click to collapse
Thank you.
I can find 7C619333F1CF at 0x90028 and 0xFC028 when HEX editing your hspl.dump.
marco.palumbi said:
hi
I am not expert on the HD2 device but I have some experience with embedded systems.
just to better understand and give some help.
the problem can be splitted in two steps:
1) find from somwhere in the device the assigned MAC addres. this seems to be at memory phisycal address 0xFC028 on kajos and mine device.
2) modify the kernel driver in order to use the address retrived from the prvious step.
tytung, which step is failing in your implementation?
to debug you can try
a) to printk() the phisical addres at 0xFC028 (so you can see it on dmesg)
b) modify the ETH kerrnel driver to use a string passed as kernel command line.
the last could be a easy solution for SD users becouse this way they can put the MAC on startup.txt...
Click to expand...
Click to collapse
I am not expert on the HD2 device either.
Here is my kernel diff. http://pastebin.com/HeSUAd5Y
What I cannot ensure is values of MSM_SPLHOOD_BASE and id_base.
According to your three spl.dump files, I think id_base = 0xFC028.
I don't know how to determine MSM_SPLHOOD_BASE.
Savan used IOMEM(0xF9500000) in his kernel, but he let me try IOMEM(0xF9200000).
I tried both and had the same result.
dmesg
Code:
<6>[ 3.489532] wifi_nvs_init
<4>[ 3.489562] id1 = 0xffffffff
<4>[ 3.489593] id2 = 0xffffffff
<4>[ 3.489593] id3 = 0xffffffff
<6>[ 3.489624] Device Wifi Mac Address by cardsharing-x: macaddr=ff:ff:ff:ff:ff:ff
I can boot into Android, but it reboots itself later. (I always enable WiFi.)
Update:
Doesn't the original kernel support set cmdline "rel_path=Android wifi.mac=00:11:22:33:44:55" in startup.txt?
kajos said:
...but you've detected the realMAC at 0xFC028.
May be there a different way for implementing this?
Click to expand...
Click to collapse
Maybe the real MAC patch only works for SD build because we get memory dump when running WinMo 6.5.
I tested new kernel on NAND with MAGLDR installed.
And the kernel cannot read SPL or have different address offset.
Here is my r12 beta2 kernel including the above real MAC patch.
You can try it on SD build.
I'm testing your new kernel and all i can say now is that i have my real mac address.
Edit:
I'm getting 60mA on standby so i'm going back to hastarin 8.6
No thanks left today
I'll do it tomorrow
I'm using MccMBoxmaX GS V9
http://forum.xda-developers.com/showthread.php?t=1038694
...and I'm getting no WIFI with r12beta2, but no wifi-error - it only can find no network
Is there a (universal) way, using this AutoMAC?
I can confirm that the MAC works for me too with r12beta2.
I get the correct one.
tytung,
I made some tests.
I am able to read the mac address from android in user space.
from the shell I issue this command:
devmem 0xFC028 64
the result for me is :
0x0000DC238E762300
that is my MAC.
devmem is part of busybox and read (and writes) phisycal memory using the /dev/mem device
can please try what is the results on your device?
regarding "wifi.mac=00:11:22:33:44:55" in startup.txt i think that it is not supported by the kernel itself.
in some android ROM this command line parameter is used by an userspace application somwhere during android boot to change values in /proc/calibration.
can you please point me to your latests kernel sources (the r11)?
i would like to give a look to them.
tytung said:
Maybe the real MAC patch only works for SD build because we get memory dump when running WinMo 6.5.
I tested new kernel on NAND with MAGLDR installed.
And the kernel cannot read SPL or have different address offset.
Here is my r12 beta2 kernel including the above real MAC patch.
You can try it on SD build.
Click to expand...
Click to collapse
Thank tytung for looking after the SD build user we need more stable kernel .. seems now u are the one that really focus on it !
Sent from my HD2 Bliss using XDA App
kajos said:
No thanks left today
I'll do it tomorrow
I'm using MccMBoxmaX GS V9
http://forum.xda-developers.com/showthread.php?t=1038694
...and I'm getting no WIFI with r12beta2, but no wifi-error - it only can find no network
Is there a (universal) way, using this AutoMAC?
Click to expand...
Click to collapse
My kernel needs a new /system/bin/wpa_supplicant.
You can get it from http://nexus-hd2.googlecode.com/files/kernel_tytung_r12_beta1_update.zip
And remember to set the permissions.
Code:
adb shell chown 0:2000 /system/bin/wpa_supplicant
adb shell chmod 755 /system/bin/wpa_supplicant
marco.palumbi said:
I can confirm that the MAC works for me too with r12beta2.
I get the correct one.
tytung,
I made some tests.
I am able to read the mac address from android in user space.
from the shell I issue this command:
devmem 0xFC028 64
the result for me is :
0x0000DC238E762300
that is my MAC.
devmem is part of busybox and read (and writes) phisycal memory using the /dev/mem device
can please try what is the results on your device?
regarding "wifi.mac=00:11:22:33:44:55" in startup.txt i think that it is not supported by the kernel itself.
in some android ROM this command line parameter is used by an userspace application somwhere during android boot to change values in /proc/calibration.
can you please point me to your latests kernel sources (the r11)?
i would like to give a look to them.
Click to expand...
Click to collapse
In r12 beta1:
# devmem 0xFC028 64
devmem 0xFC028 64
0xFFFF7FFFFFFFFFFF
Cotulla said "MAGLDR doesn't replace OSPL/HSPL. It runs in the chain after."
http://forum.xda-developers.com/showthread.php?t=893618
Not sure what he means exactly.
I think the kernel cannot access SPL when using MAGLDR and NAND ROM.
Maybe the memory space is overwritten by MAGLDR after HSPL's task is done.
My r11 kernel info: http://forum.xda-developers.com/showpost.php?p=10429937&postcount=3
Git: http://gitorious.org/~tytung/linux-on-wince-htc/tytungs-hastarins-linux_on_wince_htc
where could i found hping for android?
or where could i found busybox that contain hping?
What is the best forum for android busybox Q&A ?
Where can i tell my Android BusyBOX Question about HPING in busybox ?
Does anyone can help me ?!
busybox (busybox.net) does not include hping. You may find other multi-binaries including the hping, but it's not busybox and not very likely ported to Android. If it's hping you want, look for it (or port yourself) for Android - do not look for a "busybox". As long you don't need the tcl support in hping, I guess it's quite easy to compile it for Android.
Thanks For Reply ,
How can i compile hping for android ?
mbzadegan said:
Thanks For Reply ,
How can i compile hping for android ?
Click to expand...
Click to collapse
Using the SDK plus NDK would be the easiest way, I guess, but since you are asking, I guess you are not familiar with porting code to the Android, and in this case, I guess it may be a little to large task.
Or -- if Moses won’t go to the Mountain, bring the Mountain to Moses.
This is on my ASUS Transformer. I simply apt-get hping3.
Code:
[email protected]:~# apt-get install hping3
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
hping3
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 108 kB of archives.
After this operation, 324 kB of additional disk space will be used.
Get:1 http://ftp.se.debian.org/debian/ squeeze/main hping3 armel 3.a2.ds2-6 [108 kB]
Fetched 108 kB in 0s (339 kB/s)
Selecting previously deselected package hping3.
(Reading database ... 38945 files and directories currently installed.)
Unpacking hping3 (from .../hping3_3.a2.ds2-6_armel.deb) ...
Processing triggers for man-db ...
Setting up hping3 (3.a2.ds2-6) ...
[email protected]:~# hping3 --icmp localhost
HPING localhost (lo 127.0.0.1): icmp mode set, 28 headers + 0 data bytes
len=28 ip=127.0.0.1 ttl=64 id=61322 icmp_seq=0 rtt=0.3 ms
len=28 ip=127.0.0.1 ttl=64 id=61323 icmp_seq=1 rtt=0.7 ms
len=28 ip=127.0.0.1 ttl=64 id=61324 icmp_seq=2 rtt=0.8 ms
^C
--- localhost hping statistic ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.3/0.6/0.8 ms
This is possible because I'm running a complete GNU/Linux (Debian) on top of Android on it. You'll find a description with the how-to it in my signature, but it's not for the faint hearted and only for the GNU/Linux hackers, I guess. I don't know if this is easier than porting hping3 to Android, it's up to you to decide. But it really makes it easier running non-Android code, such as hping.
The XDA thread about it is here: http://forum.xda-developers.com/showthread.php?t=1780378
This is good idea but have 2 notes ! :
The virtual machines don't have a good packet throuput per secound !
And secound is i must install hping 3 whenever i run my VM !
I search for hping that i run it without in VM . ( because of low Packet Per Secound )
mbzadegan said:
This is good idea but have 2 notes ! :
The virtual machines don't have a good packet throuput per secound !
And secound is i must install hping 3 whenever i run my VM !
I search for hping that i run it without in VM . ( because of low Packet Per Secound )
Click to expand...
Click to collapse
I'm sorry, but I've must have made myself unclear here. No virtual machine is involved here at all, no performance loss and no need to install hping3 more than once. What I describes is a runtime environment, and involves no emulation or virtualization.
Still, I do agree with you, the best solution for you is probably a hping3 compiled for the native Android runtime environment. Running Debian may be overkill.
Hello,
I've got a strange problem:
-remix os works good when is install on usb (the alpha & the beta )
-remix os stuck at remix os boot screen when it's installed on ssd
What can i do (because on usb it's not very fast)?
atom n270 (32 bit)
gpu intel 945
Thank you
vlgyneco said:
Hello,
I've got a strange problem:
-remix os works good when is install on usb (the alpha & the beta )
-remix os stuck at remix os boot screen when it's installed on ssd
What can i do (because on usb it's not very fast)?
atom n270 (32 bit)
gpu intel 945
Thank you
Click to expand...
Click to collapse
Here too for resident mode guest mode worked after vga=791
Matam AlHaidariya said:
Here too for resident mode guest mode worked after vga=791
Click to expand...
Click to collapse
this could help both of you
http://forum.xda-developers.com/remix/remix-os/install-remix-os-parallels-vm-t3328973
Bombo1 said:
this could help both of you
http://forum.xda-developers.com/remix/remix-os/install-remix-os-parallels-vm-t3328973
Click to expand...
Click to collapse
Trying hope it work thanks
Bombo1 said:
this could help both of you
http://forum.xda-developers.com/remix/remix-os/install-remix-os-parallels-vm-t3328973
Click to expand...
Click to collapse
thank you, but your url it's about virtualisation and my problem concern install in ssd
vlgyneco said:
thank you, but your url it's about virtualisation and my problem concern install in ssd
Click to expand...
Click to collapse
Use steps 4 to 6 after you boot from USB with Remix OS, you will be able to reformat and install the OS again
Bombo1 said:
Use steps 4 to 6 after you boot from USB with Remix OS, you will be able to reformat and install the OS again
Click to expand...
Click to collapse
I whil try this today and will tel you
RE: Stuck at Remix OS boot screen
After much playing around and trial and error, I've managed to fix the flashing logo problem;
A lot of the scripts for the grub entry are needlessly complex, so I'll try and outline it as simply as I can. Make sure you use the grub customizer gui app (http://ubuntuhandbook.org/index.php/2016/04/install-grub-customizer-ubuntu-16-04-lts/) because it handles the different variations on the grub system from ubuntu-based distributions.
Since you will probably be at the stage of actually getting to the Remix OS flashing logo, I'll outline the details for the entry script in grub customizer that works and is fairly easy to follow;
The insmod entries may not all be needed, but including them all doesn't do any harm;
insmod gzio
insmod part_gpt
insmod ext2
The set root command tells grub where to find your RemixOs partition or folder, you can find your partition numbers by typing sudo fdisk -l in a terminal, it will list lots of /dev/sda[x] entries. eg (/dev/sda0, /dev/sda1 and so on) /dev/sda0 is your first partition on your first hard disk, which will be hd0 for grub. If you have more than one physical hard disk you will also have /dev/sdb entries here too, those will be hd1 for grub.
If you have RemixOS installed in your first hard disk hd0, and in the 3rd partition /dev/sda3 the line in the grub entry will be;
set root=(hd0,3)
The next few lines are telling grub which files to load up for RemixOS and are fairly simple by comparison;
linux /kernel /root=/dev/ram0
You will recall that 'kernel' is one of the files you extracted from the RemixOS ISO, this command basically tells the OS to load the kernel for Remix into ram. The next line is a bit more complicated, but it's the meat of the whole RemixOS system, after this command you can tell RemixOS which options you want to enable for your system. There are too many options to list here, so we'll keep it simple.
androidboot.hardware=RemixOS_x86_64 androidboot.selinux=permissive SRC=/system.img
This is also a fairly simple line, if you have an older x86 only machine, make sure you delete the '_64' at the end of the androidboot.hardware line. The next section androidboot.selinux=permissive is required. Lastly the SRC= line is the part I missed out when I was loading it for the first time. You have to make sure you point this SRC= to the system.img that you originally extracted from the ISO. The rest of the commands after this are the specific options you can configure, I'll leave that to your research
Finally, the last line initrd /initrd.img is required and also not terribly complicated.
The entry in grub customizer therefore should look a lot like this:
insmod gzio
insmod part_gpt
insmod part_msdos
insmod ext
set root='(hd0,3)'
linux /kernel root=/dev/ram0
androidboot.hardware=RemisOS_x86_64 androidboot.selinux=permissive SRC=/system.img
initrd /initrd.img
Bearing in mind to adjust where necessary for your own system, hope this helps!!!!
PSon't forget to SAVE entry in grub customizer!!!
Matam AlHaidariya said:
Here too for resident mode guest mode worked after vga=791
Click to expand...
Click to collapse
if your still having issues this worked for me www youtube com/ watch?v=3Vl25bJeGn8 just take out the spaces and insert periods