Messages

1

Angstrom & OpenZaurus / collie and kernel from 3.5.3 upgrades

« on: September 09, 2005, 02:03:50 pm »

1. it's not APM problem but usbnet related modules  "sa1100_bi net_fd usbdcore" are loaded in wrong order - blame Sharp/Lineo
[div align=\"right\"][a href=\"index.php?act=findpost&pid=95165\"][{POST_SNAPBACK}][/a][/div]

What is the correct order?
Can I insmod them in the correct order?
Here is the current order:

Code: [Select]

root@collie:/media/card/Documents/text# lsmod
Module                  Size  Used by    Tainted: PF
sa1100_bi              22924   0 (unused)
net_fd                 16636   1
usbdcore               22504   0 [sa1100_bi net_fd]
usbdmonitor             5448   0 (autoclean)
kbdsim                  1216   0
sharp_mmcsd_m          25792   2
rfcomm                 33512   0
l2cap                  17316   2 [rfcomm]
bluez                  32632   1 [rfcomm l2cap]
ipv6                  152344  -1
ipsec                 280008   0 (unused)

2. rm /etc/timestamp IIRC - collie has RTC, PXA based zauruses does not
[div align=\"right\"][a href=\"index.php?act=findpost&pid=95165\"][{POST_SNAPBACK}][/a][/div]

Thanks

Ajay

2

Angstrom & OpenZaurus / collie and kernel from 3.5.3 upgrades

« on: September 08, 2005, 12:21:57 pm »

Thanks for the reply hrw. Appreciated.

Look again into upgrades/collie directory and show WHEN I build r21 kernel. Then look again into /proc/version and compare both dates.

umm... not sure if I understand what you mean. What to look for in upgrades/collie? I can see the new kernel modules and other packages. These got upgraded when with ipkg upgrade.

I do see that the date /proc/version shows, and the timestamp on the r21 kernel at upgrades/collie are the same (june 30, 05). Is that what you meant for me to check?

Do the timestamps being same indicate that the upgrade was sucessful?

And next time use proper thread - I will move both posts to correct one.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=94891\"][{POST_SNAPBACK}][/a][/div]

In my defense... I did read this thread before posting, but didn't really find much discussion about r21 kernel, so I posted a new post.

Anyway, coming back to the topic...

If the timestamps show that the kernel was infact upgraded, what should I do about the suspend issues that I am facing (relisted below) ? Any pointers would be greatly appreciated.

Trying to fix:
1. Sometimes, Z resumes, but keyboard freezes. Am not able to suspend / shutdown Z. An attempt to do so freezes the PDA.
2. Upon semi-hard reboot (Change battery / Normal Operation), Z comes up, but loses date information. Everything gets reset to Aug 8th 2005, 8 am (or something like that)

Thanks

Ajay

3

Angstrom & OpenZaurus / collie and kernel from 3.5.3 upgrades

« on: September 07, 2005, 11:35:24 am »

I am trying to get rid of suspend issues that have started to occur after installing OZ 3.5.3 on my SL-5500. Using 64-0 config, with /home and /opt pointing to /media/card/home and /media/card/opt respectively.

Trying to fix:
1. Sometimes, Z resumes, but keyboard freezes. Am not able to suspend / shutdown Z. An attempt to do so freezes the PDA.
2. Upon semi-hard reboot (Change battery / Normal Operation), Z comes up, but loses date information. Everything gets reset to Aug 8th 2005, 8 am (or something like that)

Issue Synopsis: Flashing seems to do nothing. The kernel version still remains the same.

Details:
Following instructions from http://openzaurus.org/wordpress/2005/07/27...rnel-on-collie/ Here is the exact set of steps I followed:

add upgrades/collie into ipkg.conf
run ipkg update;ipkg upgrade to get r21 kernel modules installed

Code: [Select]

root@collie:/media/card/home/root# cat /etc/ipkg.conf
(.... comments sniped ....)
src/gz kernel http://www.openzaurus.org/official/unstable/3.5.3/upgrades/collie/
src/gz machine http://www.openzaurus.org/official/unstable/3.5.3/feed/machine/collie
src/gz upgrades http://openzaurus.org/official/unstable/3.5.3/upgrades/
src/gz base http://openzaurus.org/official/unstable/3.5.3/feed/base/
src/gz libs http://openzaurus.org/official/unstable/3.5.3/feed/libs/
src/gz console http://openzaurus.org/official/unstable/3.5.3/feed/console
src/gz devel http://openzaurus.org/official/unstable/3.5.3/feed/devel
src/gz opie http://openzaurus.org/official/unstable/3.5.3/feed/opie

dest root /
dest cf /media/cf/packages/
dest sd /media/card/packages/
dest ram /media/ram/packages/
root@collie:/media/card/home/root# ipkg update
(.... snip ....)
root@collie:/media/card/home/root# ipkg upgrade
(.... snip ....)
copy r21 kernel from “upgrades/collie” into CF card and flash it (ONLY kernel)

Code: [Select]

agautam@GentooDesktop ~/OZ/3.5.3 $ wget http://www.openzaurus.org/official/unstable/3.5.3/upgrades/collie/zImage-collie-64-0-r21.bin
(.... snip ....)
11:13:59 (242.50 KB/s) - `zImage-collie-64-0-r21.bin' saved [911,468/911,468]

agautam@GentooDesktop ~/OZ/3.5.3 $ wget http://www.openzaurus.org/official/unstable/3.5.3/upgrades/collie/zImage-collie-64-0-r21.bin.md5
(.... snip ....)
11:14:05 (595.70 KB/s) - `zImage-collie-64-0-r21.bin.md5' saved [61/61]

agautam@GentooDesktop ~/OZ/3.5.3 $ cp zImage-collie-64-0-r21.bin zImage
agautam@GentooDesktop ~/OZ/3.5.3 $ md5sum zImage
e179cc1991729d931f47d8031843aa0a  zImage
agautam@GentooDesktop ~/OZ/3.5.3 $ cat zImage-collie-64-0-r21.bin.md5
e179cc1991729d931f47d8031843aa0a  zImage-collie-64-0-r21.bin
agautam@GentooDesktop ~/OZ/3.5.3 $ scp zImage root@collie:/media/cf
Heres my flashing procedure:
1. Make sure that the only file I have on CF card is zImage
2. Make sure the CF card is FAT
3. shutdown collie
4. Switch mode to "Change Battery"
5. Remove battery cover.
6. Make sure power is connected
7. Press C D and the internal battery reset button.
.... Both the mail and battery lights light up
.... After approx 10 seconds (I timed it), they both switch off
8. Press the internal battery reset button.
9. Place battery cover back
10. Switch to "Normal Operation"
11. Press and hold Cancel button for a second and release
.... observe collie start ...

After collie starts up, I try to verify the kernel version:

Code: [Select]

root@collie:/media/card/home/root# cat /proc/version
Linux version 2.4.18-rmk7-pxa3-embedix-3.5.3 (hrw@home) (gcc version 2.95.3 20010315 (release)) #1 Thu, 30 Jun 2005 11:18:23 +0200
root@collie:/media/card/home/root# uname -a
Linux collie 2.4.18-rmk7-pxa3-embedix #1 Thu, 30 Jun 2005 11:18:23 +0200 armv4l unknown
boot Zaurus and be happy user of OZ 3.5.3 with r21 kernel

Code: [Select]

Would love to be one :)
Any ideas / tips to get the kernel upgraded would be greatly appreciated.

Thanks

Ajay

4

Angstrom & OpenZaurus / Vnc With Oz

« on: September 07, 2005, 11:04:34 am »

rename/symlink zaurus-kbdsim.o to kbdsim.o. that should get the keyboard working again.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=92549\"][{POST_SNAPBACK}][/a][/div]

That worked . Here is what I did:

Code: [Select]

cd /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/misc/
cp zaurus_kbdsim.o kbdsim.o
depmod -ae
shutdown -r now
upon reboot, kbdsim showed up in lsmod

Thanks very much.

Ajay

5

Angstrom & OpenZaurus / Vnc With Oz

« on: August 19, 2005, 11:16:09 am »

Ok. I got fbvncserver to work. in 3.5.3. With the exception that keyboard inputs don;t reach the application. Any suggestions on getting keyboard woking would be really appreciated.

Another minor issue: an application start icon does not show up in the GUI. Any suggestions ? I think this is just a matter of creating a valid .desktop file...

Executed command:

Code: [Select]

ipkg install fbvncserver
This installed:

Code: [Select]

root@collie:/media/card/home/root# ipkg list_installed | grep vnc
fbvncserver - 0.9.4-r1 - framebuffer VNC server
fbvncserver-kmodule - 0.9.4-r0 - framebuffer VNC server keyboard events module
libvncserver-javaapplet - 0.6-r0 - library for easy implementation of a RDP/VNC server
libvncserver-storepasswd - 0.6-r0 - library for easy implementation of a RDP/VNC server
here is what ipkg.conf looks like:

Code: [Select]

root@collie:/media/card/home/root# cat /etc/ipkg.conf
# Must have one or more source entries of the form:
#
#   src
#
# and one or more destination entries of the form:
#
#   dest
#
# where and are identifiers that
# should match [a-zA-Z0-9._-]+, should be a
# URL that points to a directory containing a Familiar
# Packages file, and should be a directory
# that exists on the target system.

# Proxy Support
#option http_proxy http://proxy.tld:3128
#option ftp_proxy http://proxy.tld:3128
#option proxy_username
#option proxy_password

# Offline mode (for use in constructing flash images offline)
#option offline_root target

src/gz kernel http://www.openzaurus.org/official/unstable/3.5.3/upgrades/collie/
src/gz machine http://www.openzaurus.org/official/unstable/3.5.3/feed/machine/collie
src/gz upgrades http://openzaurus.org/official/unstable/3.5.3/upgrades/
src/gz base http://openzaurus.org/official/unstable/3.5.3/feed/base/
src/gz libs http://openzaurus.org/official/unstable/3.5.3/feed/libs/
src/gz console http://openzaurus.org/official/unstable/3.5.3/feed/console
src/gz devel http://openzaurus.org/official/unstable/3.5.3/feed/devel
src/gz opie http://openzaurus.org/official/unstable/3.5.3/feed/opie

dest root /
dest cf /media/cf/packages/
dest sd /media/card/packages/
dest ram /media/ram/packages/
Any help / info on getting keyboard to work would be highly apreciated.

Thanks

Ajay

6

Angstrom & OpenZaurus / Configuring Lirc-modules For Ever! (ipkg-issue)

« on: August 19, 2005, 10:48:48 am »

The same has started to bug me too. removing lirc-modules seem to solve the annoying messages. reinstall did not help either.

A better solution would be really appreciated.

Thanks

Ajay

7

Angstrom & OpenZaurus / Usb Connection Howto

« on: August 11, 2005, 02:47:51 pm »

Z: SL5500, OZ 3.5.3,2.4.18-rmk7-pxa3-embedix
PC: Gentoo Linux / x86, 2.6.12-gentoo-r6

Just got IP forwarding / NAT working, so that I can access internet from my Zaurus via the USB connection. Here is the script that worked for me:

Code: [Select]

# make sure you have iptables stuff / modules compiled
# needs to be run on PC
modprobe ip_tables
modprobe iptable_nat

echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4/ip_dynaddr

EXTIF="eth0"
INTIF="usb0"

iptables -P INPUT ACCEPT
iptables -F INPUT
iptables -P OUTPUT ACCEPT
iptables -F OUTPUT
iptables -P FORWARD DROP
iptables -F FORWARD
iptables -t nat -F

iptables -A FORWARD -i $EXTIF -o $INTIF -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -i $INTIF -o $EXTIF -j ACCEPT
iptables -A FORWARD -j LOG

iptables -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE
echo "Make sure Zaurus's /etc/resolv.conf points to correct entries"
Ajay