OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: Capn_Fish on June 19, 2007, 09:04:32 pm
-
I would like to be able to compile modules for pdaXrom, but don't know how. Could somebody post a how-to? Unless I'm mistaken, the process is different on pdaX than on a normal box. Links to the stuff necessary would be great.
Hopefully this isn't horribly obvious.
Thanks in advance.
-
I would like to be able to compile modules for pdaXrom, but don't know how. Could somebody post a how-to? Unless I'm mistaken, the process is different on pdaX than on a normal box. Links to the stuff necessary would be great.
Hopefully this isn't horribly obvious.
Thanks in advance.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163415\"][{POST_SNAPBACK}][/a][/div]
for 2.6.x kernel you need to add the kernel headers to gcc 3.4.6
for 2.4.x kernel you need to use gcc 2.95.x (with fpa) and add the kernel headers for the appropriate model, ie Cxx00 use 2.4.20 kernel whereas cxx0 use 2.4.18 something kernel.
-
I feel like I've asked this before, but how do I get the kernel headers? And where exactly do I put them?
Thanks, and sorry for the (potentially) repeated question(s).
-
Could somebody please post the answers to the questions above? I'm fairly certain somebody here knows the answers...
-
I feel like I've asked this before, but how do I get the kernel headers? And where exactly do I put them?
Thanks, and sorry for the (potentially) repeated question(s).
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=163425\")
[a href=\"http://distro.ibiblio.org/pub/linux/distributions/pdaxrom/src/]http://distro.ibiblio.org/pub/linux/distri...ns/pdaxrom/src/[/url]
you need to configure the kernel but instead of compiling it, just copy the entire include subtree and whack it under the gcc include tree or symlink it....
-
After trying to configure the kernel, I have a few more questions:
-Can I do the configure part on a desktop?
-Does it matter what I configure it with?
Thanks.
-
1)install pdaxrom builder on a pc or virtual machine
2)follor the steps on note 101 upto when you start to actually build the romm (make all)
3)run make kernel_get
4)run make kernel_prepare
you now have the sources patched and ready to build in ~/<where you put your build>/build/linux-2.6.16.
with that you should be able tu build any modules.
Not sure if this is any easier that the other stuff ... but it's an alternative.
-
make kernel_prepare will perform make kernel_get
So you can skip step 3 :-)
Late
-
1)install pdaxrom builder on a pc or virtual machine
2)follor the steps on note 101 upto when you start to actually build the romm (make all)
3)run make kernel_get
4)run make kernel_prepare
you now have the sources patched and ready to build in ~/<where you put your build>/build/linux-2.6.16.
with that you should be able tu build any modules.
Not sure if this is any easier that the other stuff ... but it's an alternative.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163606\"][{POST_SNAPBACK}][/a][/div]
The sources at distro.ibiblio.../pdaxrom/src aren't patched? Does it matter? I'm trying to build the DM9601 module, and maybe packet-injection-patched hostap drivers, if it matters.
EDIT: Oh, and how hard is it to install the builder in a virtual machine and have networking support?
-
The sources at distro.ibiblio.../pdaxrom/src aren't patched? Does it matter?
No ... they get patched with make kernel_prepare from the stuf in ~/pdaxrom_builder/trunk/local_patches/linux-2.6.16/arm/....
I'm trying to build the DM9601 module, and maybe packet-injection-patched hostap drivers, if it matters.
Once you have the whole kernel sources patched with the arm and pdaxrom patches you can do whatever you like: add other patches, change kernel setup, build kernel or build just modules. If you have no experience with this stuff read the README in the kernel sources.
EDIT: Oh, and how hard is it to install the builder in a virtual machine and have networking support?
It's a simple. I use vmware because xen is teased with the slackware non xen friendly Thread Safe Library so I can give you a quick overview for vmware:
install the vmware software (in this step you must decide what type of networking you are going to give to the virtual machines: (*)bridged or nat),
create a new virtual machine and give it decent resources (disk ram and cpu),
put the pdaxrom-builder.iso somewhere where the vmware virtual machine can see it,
set up the properties on the virtual machine so that it uses the iso image as CD image (not the physical dryve),
boot the virtual machine and setup the pdaxrom-builder to HD in the virtual machine,
setup the builder following note 101 (if I remember correctly).
There you are: 15 minutes work and you have the pdaxrom-builder working (understanding how it works is a different beast ... but you can bug the hell out of Adrian for that as he did the same to Sash in turn ;-) )
* Bridged is good if you can give your VM's real addresses belonging to the same address space of the host machine, nat is godd when you aonly have one address avalible on the network where the host is attached so the VM's get another IP address and get automatically natted (like masquerade) to the address of your host.
-
The sources at distro.ibiblio.../pdaxrom/src aren't patched? Does it matter?
No ... they get patched with make kernel_prepare from the stuf in ~/pdaxrom_builder/trunk/local_patches/linux-2.6.16/arm/....
I'm trying to build the DM9601 module, and maybe packet-injection-patched hostap drivers, if it matters.
Once you have the whole kernel sources patched with the arm and pdaxrom patches you can do whatever you like: add other patches, change kernel setup, build kernel or build just modules. If you have no experience with this stuff read the README in the kernel sources.
EDIT: Oh, and how hard is it to install the builder in a virtual machine and have networking support?
It's a simple. I use vmware because xen is teased with the slackware non xen friendly Thread Safe Library so I can give you a quick overview for vmware:
install the vmware software (in this step you must decide what type of networking you are going to give to the virtual machines: (*)bridged or nat),
create a new virtual machine and give it decent resources (disk ram and cpu),
put the pdaxrom-builder.iso somewhere where the vmware virtual machine can see it,
set up the properties on the virtual machine so that it uses the iso image as CD image (not the physical dryve),
boot the virtual machine and setup the pdaxrom-builder to HD in the virtual machine,
setup the builder following note 101 (if I remember correctly).
There you are: 15 minutes work and you have the pdaxrom-builder working (understanding how it works is a different beast ... but you can bug the hell out of Adrian for that as he did the same to Sash in turn ;-) )
* Bridged is good if you can give your VM's real addresses belonging to the same address space of the host machine, nat is godd when you aonly have one address avalible on the network where the host is attached so the VM's get another IP address and get automatically natted (like masquerade) to the address of your host.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163624\"][{POST_SNAPBACK}][/a][/div]
What about doing this under Bochs or QEMU? I've had a little more experience with them (and they're more free).
EDIT: I'll just try it. If it fails, I can just try another and/or VMWarePlayer.
-
Now trying to follow the firections here (on a real HD):
http://www.pdaxrom.org/?q=node/93 (http://www.pdaxrom.org/?q=node/93)
But running setup does nothing. What's wrong? It's a SATA HD, if that matters.
Also, am I supposed to be able to boot from this partition? If so, what do I add to menu.lst?
Thanks.
-
Now trying to follow the firections here (on a real HD):
http://www.pdaxrom.org/?q=node/93 (http://www.pdaxrom.org/?q=node/93)
But running setup does nothing. What's wrong? It's a SATA HD, if that matters.
Maybe pdaxrom doesn't have the drivers for SATA disks? Try "fdisk -l" and see if the HDD you want to use is listed.
-
Now trying to follow the firections here (on a real HD):
http://www.pdaxrom.org/?q=node/93 (http://www.pdaxrom.org/?q=node/93)
But running setup does nothing. What's wrong? It's a SATA HD, if that matters.
Maybe pdaxrom doesn't have the drivers for SATA disks? Try "fdisk -l" and see if the HDD you want to use is listed.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163650\"][{POST_SNAPBACK}][/a][/div]
Yeah, it's there, and it shows up in /dev. The setup script implies that it supports SATA drives (it looks for sd* as well as hd* AFAICT).
EDIT: Rebooted and tried it without starting X, and it works. Stay tuned for the next problem!
-
OK, I finally got the setup to wrk, but now when I try to do the
make virtual-xchain_install
it fails to connect to the server. I used wget to DL the GCC source, but then it fails saying there is no room to decompress the source ("no space left on device").
Also, the partition that I specified in the "setup" isn't mounted, so I mounted it on /mnt/hd.
What am I doing wrong now?
-
Nobody has any thoughts on what could be going wrong?
-
OK, I managed to get the kernel configured and on my Z. I have the makefile set up to look for the stuff in the kernel dir and, after copying some stuff around, seem to have it so that me build should work.
But it doesn't. I get an error saying that CLOCK_TICK_RATE is not defined from the file jiffies.h. How can I fix this?
Thanks.
EDIT: I still want the pdaX86 dev environment set up, mostly because it seems like a better way to do stuff, but also because it seems I need to totally recompile the kernel to get patched hostap drivers.
Please help!
-
OK, I finally got the setup to wrk, but now when I try to do the
make virtual-xchain_install
it fails to connect to the server. I used wget to DL the GCC source, but then it fails saying there is no room to decompress the source ("no space left on device").
Also, the partition that I specified in the "setup" isn't mounted, so I mounted it on /mnt/hd.
What am I doing wrong now?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163673\"][{POST_SNAPBACK}][/a][/div]
That looks like the disk space you defined is too small ... or maybe your setup is not writing data to the HDU ?
In fact you added that some partition is not mounted .... I guess that's the snaze.
I've forgotten all the steps I did while setting up my virtual machine but this is what df says:
# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/loop0 232704 232704 0 100% /
none 452628 232912 219716 51% /boot/initrd/tmp
/dev/loop0 232704 232704 0 100% /
/dev/hda1 20806156 2197824 18398620 11% /dev/lazydisk
/dev/hda1 20806156 2197824 18398620 11% /var
/dev/hda1 20806156 2197824 18398620 11% /etc
/dev/hda1 20806156 2197824 18398620 11% /home
/dev/hda1 20806156 2197824 18398620 11% /lib/modules
/dev/hda1 20806156 2197824 18398620 11% /mnt
/dev/hda1 20806156 2197824 18398620 11% /tmp
none 452628 0 452628 0% /dev/shm
/dev/hda1 20806156 2197824 18398620 11% /opt/cross
#
And here is what mount says:
# mount
rootfs on / type rootfs (rw)
/dev/root on /boot/initrd type ext2 (rw,nogrpid)
none on /boot/initrd/proc type proc (rw,nodiratime)
none on /boot/initrd/tmp type tmpfs (rw)
/dev/loop0 on / type squashfs (ro)
none on /dev type ramfs (rw)
none on /proc type proc (rw,nodiratime)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw)
/dev/hda1 on /dev/lazydisk type ext3 (rw,data=ordered)
/dev/hda1 on /var type ext3 (rw,data=ordered)
/dev/hda1 on /etc type ext3 (rw,data=ordered)
/dev/hda1 on /home type ext3 (rw,data=ordered)
/dev/hda1 on /lib/modules type ext3 (rw,data=ordered)
/dev/hda1 on /mnt type ext3 (rw,data=ordered)
/dev/hda1 on /tmp type ext3 (rw,data=ordered)
none on /dev/shm type tmpfs (rw)
/dev/hda1 on /opt/cross type ext3 (rw,data=ordered)
#
-
OK, I managed to get the kernel configured and on my Z. I have the makefile set up to look for the stuff in the kernel dir and, after copying some stuff around, seem to have it so that me build should work.
But it doesn't. I get an error saying that CLOCK_TICK_RATE is not defined from the file jiffies.h. How can I fix this?
Thanks.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163805\"][{POST_SNAPBACK}][/a][/div]
Unless you know exactly what you're doing you should be using the pdaxrom builder to download and patch things for you (with the steps I gave you + Adrians suggestion.
Maybe the note 101 still referes to the old SVN ... use the new one on sourceforge and things should work again.
Once you have the things downloaded and patched remember that when you want to do custom things you most likely need to setup the cross toolchain environment (you should have a runsdk.sh script somewhere (in the opt tree) to do that for you).
Before you make changes to suit your needts try getting the standard pdaxrom kernel for your Z model built ... to check that what you have is working correctly.
The add whatever module you need and change the kernel setup if you need.
allways keep a copy of your .config file (make mrproper will wipe the .config file).
You might haveto do a make clean if you patch your kernel befor building anything.
You might haveto build the whole kernel before you can get some modules built (a lot depends on how the kernel configuration is setup).
-
I defined either 20 or 40 GB for that partition, which should be enough. Setup made a .pdax86 folder on the partition, so I think it worked. I'll reboot and see if it auto-detects the drive this time...
EDIT: Did I just need to run setup, or setup-hd as well?
EDIT3: Ran setup-hd, and after symlinking sda to hda and redoing lilo, I can ALMOST get it to boot. Now it gives some error about not being able to mount the rootfs on (8,1) or something like that. I'll get the exact error later.
EDIT2: If somebody would be willing to help out on IRC sometime (assuming I don't get it sorted out), that would be great.
I think I'll write up an updated how-to after this so others won't run into the same issues...
Thanks for the help.
-
I'm now hopefully solving the SATA issue by using my main computer for the pdaX86 install, so hopefully there won't be more issues, but I suspect that thre will be.
-
I think I'll write up an updated how-to after this so others won't run into the same issues...
That will be greatly appreciated.
-
I've now got the kernel source patched and stuff...I'll try to compile my module in a bit. But first, I want to patch the kernel hostap driver to support packet injection (hostap is now in the kernel), but one patch for hostap_cs.c won't apply. It fails at 872, if that helps.
The question is: Are there any patches applied to the kernel that could cause this patch not to work? The rest patches just fine.
Thanks.
-
I've now got the kernel source patched and stuff...I'll try to compile my module in a bit. But first, I want to patch the kernel hostap driver to support packet injection (hostap is now in the kernel), but one patch for hostap_cs.c won't apply. It fails at 872, if that helps.
The question is: Are there any patches applied to the kernel that could cause this patch not to work? The rest patches just fine.
Thanks.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163867\"][{POST_SNAPBACK}][/a][/div]
Maybe ... look in praxrom_builder/trunk/patches_local/linux-2.6.16/.... /arm/
the names should partially speak for themselves ...
If I remember right there is some hostap patches.
-
I see one patch that doesn't look essential to me...I'll try copying the unmodified source for hostap into the patched kernel source and see if the patch will work then.
-
Are there any specific settings I need to enable when I build the kernel? I'm rather paranoid after foobaring one when installing Gentoo. Also, how do I go about building/installing the kernel?
Thanks.
-
Are there any specific settings I need to enable when I build the kernel? I'm rather paranoid after foobaring one when installing Gentoo. Also, how do I go about building/installing the kernel?
Yes there are many ... I cannit recall them.
The best thing to do is let the pdaxrom builder build a kaenel for you (make kernel_compile) and then save the .config file in the kernel sources to somewhere safe.
Use the saved config as a starting point for whatever you want to add or remove to kernel configuration.
Keep in mind that for arm kernels you cannot carry the config across versions (ie from 2.6.16 to 2.6.17).
-
OK, I got the kernel compiled with packet injection support (I'll post it later), but I need to reflash my card's firmware to get it to work correctly. Is there package out there that works for downloading firmware to a card? I'm having issues compiling it into the kernel, and Beta 1's standard prism2_srec wouldn't work.
Thanks.
-
Hey capn_fish,
I once updated my firmware on my linksys wcf12 compact flash card. I used the guide found on this page:
http://www.aircrack-ng.org/doku.php?id=pri...b87e59b4b29c33b (http://www.aircrack-ng.org/doku.php?id=prism2_flashing&DokuWiki=927bc0525e32a7030b87e59b4b29c33b)
Maybe you can do the same with your card.
VirtusRex
-
Hey capn_fish,
I once updated my firmware on my linksys wcf12 compact flash card. I used the guide found on this page:
http://www.aircrack-ng.org/doku.php?id=pri...b87e59b4b29c33b (http://www.aircrack-ng.org/doku.php?id=prism2_flashing&DokuWiki=927bc0525e32a7030b87e59b4b29c33b)
Maybe you can do the same with your card.
VirtusRex
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163938\"][{POST_SNAPBACK}][/a][/div]
Did you do it on your Z? If so, what ROM? My issue is that pdaXrom apparently doesn't support flashing cards ATM.
-
Hey capn_fish,
I once updated my firmware on my linksys wcf12 compact flash card. I used the guide found on this page:
http://www.aircrack-ng.org/doku.php?id=pri...b87e59b4b29c33b (http://www.aircrack-ng.org/doku.php?id=prism2_flashing&DokuWiki=927bc0525e32a7030b87e59b4b29c33b)
Maybe you can do the same with your card.
VirtusRex
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163938\"][{POST_SNAPBACK}][/a][/div]
Did you do it on your Z? If so, what ROM? My issue is that pdaXrom apparently doesn't support flashing cards ATM.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163939\"][{POST_SNAPBACK}][/a][/div]
No, I did it on my laptop running windows xp using a pcmcia to CF adapter.
-
I now have a 2.6.16 Cxx00 kernel that supports packet injection and the flashing of Wi-Fi cards. I'll get links to info on how to install it as well as the actual files up later.
I assume there's interest?
-
Yeah, sounds good.
VirtusRex
-
Hey Capn_Fish,
I'm a little confuse about why your kernel needs to support packet injection?
I downloaded pdxaii13 5.4.5 and I've been using it with my C1000. So far I've managed to test packet injection on my home router and it works fine with my DWL-G122 usb wireless key. Does this mean pdaxii13 5.4.5 supports packet injection as well???
VirtusRex
-
Well, Meanie did tweak it, so I would guess that that is a yes. It wouldn't be strange for him to have added it in.
EDIT: Oh, r198 doesn't support injection out of the box. You need to patch andrecompile the kernel to get such support. I suspect Meanie patched the drivers for ii13, as they are separate from the kernel.
As to why I need packet injection, I just want to get WEP cracking to work. It has eluded me for some time, which irks me.
-
Here's the stuff (for Cxx00 r198; may work on other models/pdaXrom versions, but no guarentees). Just remove (or move to a safe place) /lib/modules/2.6.16, and untar the "lib" archive to /. Then, do a
nandlogical /dev/mtd1 WRITE 0x5a0000 0x160000 uImage
and reboot. You should have working packet injection, as well as support for flashing cards' firmware.
Remove the .txt extention from uImage.txt (so it becomes "uImage")
Sorry, I seem to not have the files other than the hostap-utils for flashing firmware. I'll get it soon (I don't want to retype this post).
EDIT: Added macchanger (only way I found to make my card work was changing its MAC)
EDIT2: I'm almost certain these are the right files (modules and uImage).
-
I've almost got a module compiled! It goes for a while, then complains about not being able to execute scrips/basic/fixdep. Is there a way around this?
EDIT: got around that be removing the file and recompiling it. Now it's complaining about scripts/mod/modpost. I removed it and tried to recompile it, but it doesn't work. Any workaround here?
EDIT2: OK the module is compiled! But no matter where I stick it, I can't modprobe it. I've been putting it in /lib/modules/2.6.16/<direcotry>, but it doesn't work. I'm probably missing somethig obvious...
EDIT3: OK, I figured it out...See the new packages thread for details and the module.
A dm9601.o file is created, but I thought it was supposed to be .ko? Or is that not a module?
Thanks.
-
How do you cross compile with pdaX86? When I try to build stuff, it builds it for x86. The kernel built fine for armv5tel, and I can't find a runsdk.sh equivalent.
If this is really obviously documented somewhere, please let me know.
Thanks.
-
I've made some notes as a reminder for myself (and for anyone who might find them usefull).
They are avalible on my home page in the "Zaurus" menu on the left and then "Issues" and "Documentation" submenus on the top.
In particular this (http://www.seicento.selfip.org/zaurus/issues/create_a_custom_kernel.html) and also this (http://www.seicento.selfip.org/zaurus/docs/pdaxrom-builder_kernel_only_build.txt) documents contain some usefull information.
The runsdk.sh should be in the /opt/cross tree somewhere .... I've made a copy of it in /usr/local/bin so that it's in the default path.
Just incase you cannot find it this is what it should be like (this is for the pdaxrom cross sdk current version) :
#!/bin/bash
. /etc/profile
export PATH=/opt/cross/arm/3.4.6-xscale-softvfp/bin:$PATH
export QTDIR=/opt/cross/arm/3.4.6-xscale-softvfp/armv5tel-cacko-linux/qt
export KDEDIR=/opt/cross/arm/3.4.6-xscale-softvfp/armv5tel-cacko-linux/qt
export X11INC=/opt/cross/arm/3.4.6-xscale-softvfp/armv5tel-cacko-linux/include
export X11LIB=/opt/cross/arm/3.4.6-xscale-softvfp/armv5tel-cacko-linux/lib
export PKG_CONFIG_PATH=/opt/cross/arm/3.4.6-xscale-softvfp/armv5tel-cacko-linux/lib/pkgconfig
export CROSS_COMPILE=armv5tel-cacko-linux-
export CROSS=$CROSS_COMPILE
export ARCH=arm
echo "Type exit for leave armv5tel-cacko-linux cross environment."
/bin/bash
Hope this helps.
-
New kernel and modules. Now with IPTables support and probably a bunch of extra junk. Includes the packet injection and firmware flashing (for the flashing, not tested but I' fairly sure I got it in there) support.
DL the junk.tar.gz file to somewhere and untar it. Follow the instrutions in the last post to flash the kernel, then remove your /lib/modules/2.6.16 folder, cd to /, and untar the lib.tar.gz file (which is in the junk.tar.gz file).
This is necessary to use the Firestarter package I just put up in the new packages thread.
-
How large is the demand for a fastfpe pdaX latest kernel with packet injection support? Post/PM me away if you want it.
-
@Capn Fish
Do you know whether ist works for Meanies pdaXii13v2. There is the kernel 2.4 available.
From where do I execute the command "nandlogical /dev/mtd1 WRITE 0x5a0000 0x160000 uImage" ?
Thanks
climber
SL-C3100 & pdaXii13v2
-
It probably will not work with pdaX11i3, but you never know. If nothing on the system (besides kernel modules) is kernel-specific, flashing it may be OK.
You can run the Nandlogical command from wherever (the example given was from the directory containing uImage).
-
Ok, I did a zbackup from my pdaXii13v2. I will try it on pdaXrom_r198 to get it working. These are the steps which I'm
planing to do. Please correct me if I'm wrong
1.) Flash my Zaurus SL-C3100 with pdaXrom_r198
2.) Reboot and do some settings
3.) Booted up off the pdaXrom installer and ran in a shell "nandlogical /dev/mtd1 WRITE 0x5a0000 0x160000 uImage" inside the directory containing
uImage
4.) Install the following apps: apps (http://zaurus.aircrack-ng.org/akita/)
a.) hostap-utils_0.4.7-r3_armv5te.ipk
b.) kernel-module-hostap-2.6_2.6.16-r41_akita.ipk
c.) aircrack-ng_0.9.1-r2_armv5te.ipk
???? I'm not sure if I need to install the kernel-module-hostap or if it's included in your file?
5.) Modify the script "airoscript.sh" to my settings as described in the readme.
6.) ?????????
Could this work or do I miss something? On which ROM did you get it successful working (pdaXrom; Angstrom; Cacko)?
Thanks
climber
-
You can flash the kernel from the normal OS. By installing the HostAP package, you got RID of the patched drivers (assuming it's unpatched) Try:
-Install r198
-flash kernel
-untar modules to /
-reboot
-install aircrack and stuff from my feed
That's what worked for me IIRC. The Aircrack packages on the site are for Angstrom/OZ.
-
What do you mean that I can flash the kernel form the nomal OS? The command nandlogical isn't available there or if you mean something different then please write some detailed instructions (please).
Which modules do you mean to untar to / ???
Thanks
climber
-
In post 36 of this thread, there are 4 attachments:
-HostAP utils (not necessary unless you want to flash firmware)
-macchanger (was the only way to make my card inject for some reason, works fine without it now, not necessary)
-uimage (not a text file, it's the kernel, necessary)
-lib.tar.gz (the modules, necessary)
Then flash the kernel (however you can) and untar the lib.tar.gz package to / (remove the old /lib/modules/2.6.16 directory first).
Or just get the junk.tar.gz file from post #40 and:
-untar to some location
-flash the kernel (however you can)
-rm -r /lib/modules/2.6.16
-cd /
-tar -xf /path/to/modules.tar.gz
Hope that's enough information.
H
-
No idea. I would guess so, but what's wrong with r198? It basically is r121, except with fixes.
-
One last questions before I start.
I never had installed r198 before so I read some entries in this forum. What I read look like that I first have to install U-boot
following these two links: Link1 (http://www.pdaxrom.org/?q=docs/installation/quickguide) Link2 (https://www.oesf.org/forum/index.php?showtopic=24857&hl=r198&st=0)
Inside this link Link3 (http://www.pdaxrom.org/?q=node/106) they talke about " .....NOTE: first release of emergency system for C1000/3x00 can't updating by this way...".
I have a SL-C3100 so which one of the 3 mentioned U-boot installation/upgrade versions should I take?
Thanks
climber
-
Put the files on a FAT-16 SD or CF (remove other card), remove all power from Z, hold C+D, insert AC. LEDs should come on for a bit, then go off. When they do, remove the power and flash r198*.
*Put the files on SD/CF, insert battery/power while holding OK, wait for it to boot and say "pdaX emergency system", answer 'y' to the question.
-
You told before that I can flash the kernel from the normal OS. Is it the
"nandlogical /dev/mtd1 WRITE 0x5a0000 0x160000 uImage" command. I only ask because this command isn't available
on pdaXii13v2.
Thanks
climber
-
It's available on r198, that's about all I know. I have never used pdaXii13, so I'm afraid I cannot be much help, or even come close to guaranteeing that this kernel will work.
What exactly are you trying to do here (eg, what setup)? I've been kind of getting mixed impressions.
-
I just realized I uploaded the kernel, instructions, and a flashing script to
http://www.techassassins.com/Zaurus/junk/aircrack/ (http://www.techassassins.com/Zaurus/junk/aircrack/)
-
Is it possible to get the packet injection working for pdaXii13v2 with 2.4.20 kernel?
Thanks
climber
-
Yes it is possible, maybe with the modules posted on some website (I believe there was a link in your other thread).
If it needs the drivers recompiled, I can't help you. I've tried twice in the past with no luck, and have no intention of trying again in the near future. Sorry.