Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ric

Pages: [1]
1
SIMpad forum / Atmelwlandriver On Simpad/familiar 0.8.4 ?
« on: September 18, 2006, 06:45:02 am »
Hi out there,

currently, I'm trying around with gpe/familiar 0.8.4 on my sinuspad.
Installation went fine but now, I'm having problems getting a stable wlan connection up and running.
I've been trying some time with a netgear ma401 with the orinoco driver which seems to work from time to time but not very stable: I need to insert the card a couple of times to get it running. So far, I didn't find a pattern behind this so I have to try and try which is very annoying. Once I get the card running, the network works and I can run things like ipkg.
Very unhappy with this situation, I got me another wlan card: Belkin F5D6020 ver.2 which uses an atmel chipset (got it very cheap...). Somewhere on the net, I found a feed that provides a compiled atmelwlandriver (atmelwlandriver.sourceforge.net) for the simpad, but for kernel version 2.4.25. Current kernel version in familiar 0.8.4 is 2.4.27.
I modified /etc/pcmcia/config so that the card is recognized by the cardmanager on insert but I have no success in binding the right driver to it.
Has anybody suceeded in getting an atmel based wlan card running on familiar 0.8.4?
If not, any idea why my ma401 doesn't seem to work stable? Maybe I should use hostap instead of orinoco?
One more question: ma401 should be able to handle WPA encryption after a firmware upgrade (which mine has). Can I use this feature on gpe/familiar/simpad?

Thanks for your help
Richard

2
SIMpad forum / Killed My Swisscom Cl4 Using Jtag.
« on: January 06, 2006, 05:46:39 pm »
Hi,

here are the last lines of the boot process with Sascha's image on my sinuspad:
/etc/rcS.d/S01version: 31: cannot create /dev/tty1: Permission denied
/etc/rcS.d/S01version: 31: cannot create /dev/tty1: Permission denied
/etc/rcS.d/S01version: 31: cannot create /dev/tty1: Permission denied
/etc/rcS.d/S01version: 31: cannot create /dev/tty1: Permission denied
/etc/rcS.d/S01version: 31: cannot create /dev/tty1: Permission denied
/etc/rcS.d/S01version: 31: cannot create /dev/tty1: Permission denied
/etc/rcS.d/S01version: 31: cannot create /dev/tty1: Permission denied
Setting up device links for devfs: done
Unable to handle kernel NULL pointer dereference at virtual address 00000008

After this, the machine hangs and must be reset.
BTW: with my own image, I also have the Permission denied-problem with /dev/tty1. While booting, I have to wait some time after all these messages until the boot continues. Any ideas?

Greetings
Richard

3
SIMpad forum / Killed My Swisscom Cl4 Using Jtag.
« on: January 06, 2006, 06:09:51 am »
before I forget it, you can find the latest opie Image I build on:
http://www-user.rhrk.uni-kl.de/~gerkhard/s...l4.rootfs.jffs2

Hi Sascha,

gave it a very short try last night on my tsinuspad. Unfortunately, it didn't even start correctly. Don't have the errormessage handy right now but I will tell you tonight when I'm back home.
I tried to build an opie-image myself. It started into the login-prompt on tty and showed some welcome image on the screen as well but the touchscreen didn't work at all. Had no time so far to dig deeper into this. My goal is an image for my sinuspad with a reasonable browser and a reasonable (i.e. imap-capable) email client.
so i'm keeping on trying.

Greetings
Richard

4
SIMpad forum / Opensimpad-0.9.0rc1 On T-sinuspad!
« on: December 01, 2005, 03:06:50 am »
Currently, I'm digging into bitbake/openembedded. Maybe eventually, I find some code to change partitions via the kernel which I indeed would prefer over manipulating the bootldr.
At the moment, I have problems building an opie-image from openembedded which I must understand at first.
But thanks for the hints.

Greetings
Richard

5
SIMpad forum / Opensimpad-0.9.0rc1 On T-sinuspad!
« on: November 30, 2005, 06:38:32 am »
Just a quick update:
gpe seems to run ok on the sinuspad with the mem=32M parameter. But still no idea how to have the bootloader start with usable partitions.
I'v contacted zecke to get the latest bootldr sources. Maybe this is the way to go.

Greetings
Richard

6
SIMpad forum / Simpad Bootloader 'load Root' Problem
« on: November 25, 2005, 07:28:32 am »
Me too...
I had WinCe 4.1 on my Simpad but was not able to get a reliable wireless connection with a netgear ma401. Tried all the drivers that were available but...
Next thing is, I would like to have an email client capable of imap so I can work with my home server from all workstations. I want the simpad mainly as surfpad and email client so that the 16MB should be sufficient.
Happily looking forward to things to come and eventually ready to do some things myself.

Greetings
Richard

7
SIMpad forum / Opensimpad-0.9.0rc1 On T-sinuspad!
« on: November 25, 2005, 07:11:27 am »
Hi Berend,

in the meantime, I gave the gpe-image a try, too with the same results.
I'm not really sure if there is a major problem with the bootldr itself leading to these problems or the images which maybe rely on an existing home partition or whatever.
Any idea if the issue about the reset partitions can be solved without touching the bootldr sourcecode? I'm not even close to compiling anything since I have no linux machine running (except my server) at this time - shame on me...
But I think there is a certain need to support 16MB Simpads after the recent flooding of sinuspads and the swisscom(?) pads.
Sooner or later, I will dig into the oe toolchain. But I must admit, I have a couple of priorities, first of all getting my new house ready :-)
Maybe it is worth waiting for Angström which I haven't very much info about right now.
I will keep trying the images I can find for now.
Anyone out there who can provide images suitable for 16MB simpads?

Greetings
Richard

8
SIMpad forum / Opensimpad-0.9.0rc1 On T-sinuspad!
« on: November 24, 2005, 06:50:33 am »
Hi all,

yesterday, I managed to run opensimpad-0.9.0rc1 on my stock T-Sinuspad!
Unfortunately, my solution is not permanent so far.

I take no responsibility for any damage that could happen when you try this out!

I'm running the hh.org bootldr that Chris had provided in combination with the RC1. This one seems to have a hardcoded partition table which needs 32MB of flash which the Sinuspad obviously doesn't have.
What I did is this:
After booting into the bootldr, I deleted the partitions home and root.
After that, I created a new root partition with the command
Code: [Select]
partition create root 0x40000 0xfc0000 16This is a partition that uses all the flash memory between the bootloader partition and the end of flash.
I erased this partition with
Code: [Select]
eflash rootNow, I loaded the jffs2-file with
Code: [Select]
load rootand uploaded the file http://opensimpad.org/bootldr-simpad/opens...0rc1_opie.jffs2 to the pad.
After the command
Code: [Select]
boot opie 1.2 started on my machine. I had not much time to try but most applications seemed to work. Some apps made the pad hang which was not so nice... but they were images for testing purposes, anyway.
Next time, I'm going to try one of the images of devernay.

Now to the problem: After suspend or reboot, the bootldr reconstructs the original partition table with the big root partition lasting to address 17c0000 and the home partition which I wouldn't need anyway. This leads to a kernel panic when rebooting into opie. After changing the partition table again and booting, it works again.

Is there a way to change the default partitions other than compiling a new bootldr? Maybe the params are the key. I need to dig deeper into this.
Maybe, I'm going to get the toolchain and build my own image, maybe someone could build an image after some patching of the bootldr.

Any help and hints are appreciated.

Greetings
Richard

Pages: [1]