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 - alge

Pages: [1]
1
Debian / Htc Universal
« on: January 04, 2009, 05:11:46 pm »
Hi,

after a while a tried today to start again with my titchy installation from scratch, as in my first try half a year ago the phone applications did not work.

I was wondering a little bit that the initial installation using /sbin/titchybootstrap2 and /etc/rcS.d/S99titchybootstrap3 did not work. I fixed the calls to dpkg there, added some missing debs (net-utils, sed, module-init-tools if I remember all) and mainly installed everything manually. Afterwards I recognized that this may be due to the fact, that the jigdo file and apt/sources.list refer to debian testing, which was something different last year.

Well, I managed to setup a basic Debian testing now, with usb networking and ssh.

But now I cannot find any titchy-* package. The Packages file from debian.neilandtheresa.co.uk is empty. Has anyone mirrors of these packages or even the source packages to rebuild them?

Some posts above contain already some questions regarding the repository not beeing accessible, is this still the same?

Thanks

Albrecht

2
Security and Networking / Wifi Oddness
« on: January 09, 2005, 06:56:58 pm »
I have the same trouble with my linksys wrt54g AP at home. I think it is due to interacion with other networks nearby ..... For me it helps when I execute the following script as root before connecting:
Code: [Select]
#!/bin/sh
usbctl on 1
sleep 2
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
# following stuff on single line
wlanctl-ng wlan0 dot11req_scan bsstype=any bssid=ff:ff:ff:ff:ff:ff ssid="" scantype=both channellist="01:02:03:04:05:06:07:08:09:0a:0b:00:00:00" minchanneltime=200 maxchanneltime=250

albrecht

3
6000 - Tosa / Vpn Client For Sl6000l
« on: January 09, 2005, 06:32:16 pm »
just finished a tun.o module see my post in a different thread.

albrecht

4
6000 - Tosa / Looking for tun.o built for SL-6000
« on: January 09, 2005, 06:22:45 pm »
maybe a little bit too late :-)  ... but i needed it now too (for openvpn).

compiled with 2.4.18 from jp 1.11 rom sources, works with 1.12 rom

Code: [Select]
mkdir /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/net/
cp tun.o /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/net/
depmod -a
mknod /dev/net/tun c 10 200
modprobe tun

albrecht

5
6000 - Tosa / Dial-up Connection With Aircable Adapter
« on: January 09, 2005, 01:38:33 pm »
Hi all,

the AirCable Bluetooth adapter works with the SL-6000L, it blocks the keyboard (you can connect it either with closed keyboard or with open keyboard, once connected you cannot change the keyboard state), the blue LED points downwards.

[img]http://www.math.uni-klu.ac.at/~agebhard/aircable-sl6000-1.jpg\" border=\"0\" class=\"linked-image\" /]
[img]http://www.math.uni-klu.ac.at/~agebhard/aircable-sl6000-2.jpg\" border=\"0\" class=\"linked-image\" /]

I created a Serial Dial-Up connection with Settings/Network.

This connection works when I call it manually
Code: [Select]
pppd call DIALUPXXXXX nodetach /dev/ttyS0(nodetach for debugging purposes or to be able to  simply end the connection with ctrl-C)

With the network applet only my Wireless and Irda(irda doesnt work, other story) connections show up
[img]http://www.math.uni-klu.ac.at/~agebhard/aircable-sl6000-dial.png\" border=\"0\" class=\"linked-image\" /]
so I can not select it for starting.

I guess Qtopia doesn't recognize the internal /dev/ttyS0 as modem, any hints?

6
Security and Networking / Sl-6000l Wireless Setup
« on: January 05, 2005, 07:56:19 am »
this didn't work:

Internet--->Firewall==wrt54g/svea------WDS----->wrt54g/svea----->Zaurus SL6000

after changing to

Internet--->Firewall==wrt54g/svea------WDS----->wrt54g/svea--cable->wrt54gs/linksys/otherESSID--->Zaurus SL6000

it worked.

but meanwhile I recognized that it wasn't related to the firmware, it also stopped working with linksys firmware on the last wrt54gs after changing channels.

It turned out it only works for me with channel 10, 11 or 12. before I recognized this I had channel=auto (it switched to 1 or 2), this didn't work.

I think it's related to my neighbour networks (on 801.11g on channel 6), maybe the antenna in the Z is not as good as that one in my SMC card.

It can also be partly related to WDS: now I'm back at a two wrt54 setup with sveasoft and WDS.  sometimes it doesn't connect, maybe because both APs with same ESSID are visible? But if I execute before tapping the connect icon:

Code: [Select]
usbctl on 1
sleep 2
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
wlanctl-ng wlan0 dot11req_scan bsstype=any bssid=ff:ff:ff:ff:ff:ff ssid="" \
 scantype=both channellist="00:01:02:03:04:05:06:07:08:09:0a:0b:00:00" \
 minchanneltime=200 maxchanneltime=250

it works. I'll have a look for the wlan scripts where I can add this permanently...

Albrecht

7
6000 - Tosa / SL-6000 carry cases
« on: January 05, 2005, 06:49:48 am »
as promised the HOWTO:

PDF (large! 2MB)

gzipped Postscript (very large! 20MB,  ~ 40 MB unpacked)

DXF file (for e.g. QCad)

EPS file with layout only

8
6000 - Tosa / SL-6000 carry cases
« on: January 03, 2005, 06:40:16 pm »
Quote
alge,

looks really nice, a couple q's:

- how is it working out for the 6K?   do you think a velcro fastener would work better for easy closing?
- how long to put together?
- source of leather? cobbler, craft store, other?

J
I'll prepare a short HOWTO for this doityourself case, with some more pictures ...

It took me about three evenings. I got the leather from a local cobbler store, it is about 3mm thick.
You only need some rather strong yarn, a leather needle, a swiss army knife or similar and four! tapestry needles.

velcro fastener: dont know, may be better, but the simple loop works well.

I'm using the smaller 5000D case for almost two years now (everyday), I had only to replace the yarn one time (from cotton to synthetics).

9
6000 - Tosa / SL-6000 carry cases
« on: December 30, 2004, 06:03:01 pm »
I use a selfmade belt attachable carying case. no room for additional stuff, no holes for cables etc. only for carrying the Z around.
[img]http://www.math.uni-klu.ac.at/~agebhard/zaurus-case.jpg\" border=\"0\" class=\"linked-image\" /]
I already used a slightly smaller but similar case for my SL-5000 (visible in the background of the image).

10
Security and Networking / Sl-6000l Wireless Setup
« on: December 24, 2004, 07:25:14 am »
I also tried connecting via GUI, but when this fails, you have not many debugging options, thats why I used these manual wlan startup commands.

Currently I'm using a third WRT54GS with original firmware (there is no connection problem) behind my WDS bridge for the 6000L.

I thought that I also tried sveasoft firmware without WDS, but I have to repeat those tests to be sure.

Albrecht

11
Security and Networking / Sl-6000l Wireless Setup
« on: December 21, 2004, 02:49:37 am »
just for completeness: I also figured out (using this forum) how to start the internal wlan device manually

Code: [Select]
usbctl on 1
sleep 2
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable

A scan for an AP can be done by
Code: [Select]
wlanctl-ng wlan0 dot11req_scan bsstype=any bssid=ff:ff:ff:ff:ff:ff ssid="" \
 scantype=both channellist="00:01:02:03:04:05:06:07:08:09:0a:0b:00:00" \
 minchanneltime=200 maxchanneltime=250

and if the return value contains a "numbss" value >=1 you can get the scan results by
Code: [Select]
wlanctl-ng wlan0 dot11req_scan_results bssindex=0where you can iterate bssindex from 0 to numbss-1.

12
Security and Networking / Sl-6000l Wireless Setup
« on: December 21, 2004, 02:41:51 am »
slapout: maybe the problem is that I don't use the original firmware on the WRT54G but a modified version from sveasoft.com. And I also enabled WDS between my two access points (both running in mixed 11/54 Mbit mode).

I'll soon get another WRT54G and will try with original firmware.

Meanwhile I found a public hotsot near university where I could connect to the login portal immediately, so now I'm sure that my SL6000's wifi card is not damaged at least.

Tehas: Yes i forgot about this in my first try , but i already had disabled HWA matching before.
Maybe I'should try enabling it and put the new HWA in the accepted HWA list...

I also tested the WLAN parameters (WEP ...) by using the same setup with my SMC CF card and it works there.

The problem with the internal USB Prism2 even occurs before any DHCP packets have to be send, this can only happen after you are authenticated and associated to the accesspoint (that means you can see the APs harware adress listed when you call iwconfig wlan0).

Meanwile i also tried a Cisco AP (Airo-AP1231) with the same result. The log output on this AP shows my HWA with th error code: Auth_not_Assoc

I'll kkep trying, I guess I have to create a systematic experimental plan with enabling/disabling several AP features (mixed mode, WDS bridging or not and so on)

Meanwhile I also learned some of the wlanctl-ng subcommands. in any case I  can scan successfully for APs with "wlanctl-ng dot11req_scan ...." and "wlanctl-ng dot11req_scan_results ...." which shows me the SSID and BSSID (HWA) of the AP.
I compared these results with results from the SMC CF card and they only differ in the ibssatimwindow parameter (=0 for working SMC card, =65105 for SL6000 internal card). I still don't know what this means and if it has any meaning to my problem.

Thanks

Albrecht

13
Security and Networking / Sl-6000l Wireless Setup
« on: December 16, 2004, 06:11:47 pm »
Hi,

I just got my new SL 6000L and I'm trying to connect to my WRT54G access point
(SHARP ROM version 1.12)

I'm sure that I got all setup entries right, because I can use the same setup successfully (ESSID, WEP keys) when I plug my SMC 2642W CF card in (which I normally use in my SL-5000D). MAC address filtering is turned of at the AP.

I even tried to disable WEP on the WRT54G but I could not connect at all.

When I look at ifconfig ouput during the connection trial, I see only 3 or 4 dropped packets in the TX/RX statistics.

After the connection trial (tapping the network icon in status bar)  the wlan0 device is removed, can anybody tell me how to start the connection manually from a terminal? It would help debugging my setup a lot.

I already tried
Code: [Select]
/etc/wlan/wlan-setup start wlan0 qpewlan0which is running after the click on the network icon, but this seems only to be the second part of scripts which have to be run, it already expects a wlan0 device to be present. How can I create this manually, reloading prism2_usb module is not enough. I guess some hotplug script has to be run, but which one?

I tried also at work with some Cisco access point (forgot model name), also no connection there.

By enabling lots of debug options we could at least see some packets which came from the hardware address of the SL6000.

Below is my dmesg output of a connection attempt, I'm a bit unsure if the hex-0 serial number is ok, because with my WDC card I can see some integer there, could anybody look at his dmesg output if it looks similar?
Code: [Select]
ub.c: USB new device connect on bus1/2, assigned device number 2
usb.c: USB device 2 (vend/prod 0xbb2/0x302) is not claimed by any active driver.
init_module: prism2_usb.o: 0.2.0 Loaded
init_module: dev_info is: prism2_usb
usb.c: registered new driver prism2_usb
ident: nic h/w: id=0x8026 1.0.0
ident: pri f/w: id=0x15 1.1.3
ident: sta f/w: id=0x1f 1.7.4
MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1
PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=1/4
STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/12
PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Prism2 card SN: \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
p80211knetdev_hard_start_xmit: Tx attempt prior to association, frame dropped.
p80211knetdev_hard_start_xmit: Tx attempt prior to association, frame dropped.
p80211knetdev_hard_start_xmit: Tx attempt prior to association, frame dropped.
usb.c: USB disconnect on device 2

thanks

Pages: [1]