OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: Mongus on November 03, 2005, 07:43:25 pm
-
I got it working following the instructions for Rc 10 On C3000 With Dual Boot (https://www.oesf.org/forums/index.php?showtopic=13560) but using the Rc12 root-akita archive available here (http://212.10.30.205/rc12/Zaurus-C1000-C3100/root-akita.tar.bz2).
Make sure to read the instructions for bug fixes in the other thread. I did a "chown -R root:root /hdd3/*" because the ownership was not right. I also had to make changes to several files to update "cardctl suspend" and "cardctl resume" to "cardctl suspend 0" and "cardctl resume 0". I'm sure the following files were changed /etc/pcmcia/network /usr/bin/network.py. There may have been others but I'm not sure. If you don't change the files your hard drive will be suspended along with your WLAN card .
One thing that I haven't seen documented anywhere was copying /sbin/writerominfo from the Cacko ROM I have installed to /hdd3/sbin/writerominfo. This fixes /proc/deviceinfo/product. Before I copied writerominfo /proc/deviceinfo/product was set to "unknown" which caused several problems the most noticable being akita.xmodmap not being used in X. Not having a working Fn makes typing very tedious . Apparently, the C1000 and C3100 writerominfo works differently than the C3000. Took several hours to figure out that one.
I haven't gotten hostap (https://www.oesf.org/forums/index.php?showtopic=15608&st=15#entry101297) to work yet. I'm getting unresolved symbol errors. (iw_handler_set_thrspy, iw_handler_get_thrspy, wireless_spy_update, iw_handler_get_spy, iw_handler_set_spy) Anybody with ideas how to get hostap to work? The wireless network going down anytime I try to do anything significant is really annoying.
I highly recommend installing gcc and gcc-headers so you can download Vim 6.4 (http://ftp://ftp.vim.org/pub/vim/unix/vim-6.4.tar.bz2) to build and install it. It's much better than busybox's vi .
-
I haven't gotten hostap (https://www.oesf.org/forums/index.php?showtopic=15608&st=15#entry101297) to work yet. I'm getting unresolved symbol errors. (iw_handler_set_thrspy, iw_handler_get_thrspy, wireless_spy_update, iw_handler_get_spy, iw_handler_set_spy) Anybody with ideas how to get hostap to work? The wireless network going down anytime I try to do anything significant is really annoying.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=102167\"][{POST_SNAPBACK}][/a][/div]
The hostap binaries from that thread have been built for the RC12 C1000/C3100 kernel. If you're running a different kernel, you'll have to rebuild hostap-drivers against the sources of that kernel. (Even if it's also a 2.4.20 kernel, the config is probably different.)
-
The hostap binaries from that thread have been built for the RC12 C1000/C3100 kernel. If you're running a different kernel, you'll have to rebuild hostap-drivers against the sources of that kernel. (Even if it's also a 2.4.20 kernel, the config is probably different.)
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=102213\")
I tried installing the [a href=\"https://www.oesf.org/forums/index.php?showtopic=10599]c3000-bigkernel[/url] but my WLAN card still hangs under load .
I guess I'll be building my own kernel for the SL-C3000 to try to get hostap running. Kind of scary building a kernel for the 3000 because I can't just boot off of a CDROM if I screw it up.
I'll give a shot and post my results here.
-
I guess I'll be building my own kernel for the SL-C3000 to try to get hostap running. Kind of scary building a kernel for the 3000 because I can't just boot off of a CDROM if I screw it up.
There really isn't any thing to worry about trying new kernels on the c3000. Just keep a cf card with a good kernel on it and use that to flash back if your kernel won't boot for some reason.
This family of zaurus also has a diagnostic mode. if you pull the battery, hold D and B, and while holding them put the battery back in you will boot into a shell on the Z, so if you screw your rom up with a dumb change you can fix it like this.
Hope this helps some ppl.
Realm