OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Debian => Topic started by: gojira on May 19, 2008, 04:26:16 am
-
There are some cheap Canon K30225 CF wifi cards on ebay at the moment. Anyone using one with debian? Thanks.
-
There are some cheap Canon K30225 CF wifi cards on ebay at the moment. Anyone using one with debian? Thanks.
I'm currently based in South Africa and cf WIFI cards are impossible to find
-
There are some cheap Canon K30225 CF wifi cards on ebay at the moment. Anyone using one with debian? Thanks.
Has anyone tried the SparkLAN WL-672 Wireless Compact Flash? Does it work?
-
Bought one last month for a 2200 series Ipaq. Came with no driver which auction said included. note that their auctions now say does NOT include CD.They did not respond to requests for drivers instead sent me to a site that had drivers for downloading which could not be uploaded into XP or Vista.
Nice card though. My 5 year old loves it for her dollhouse. Get an SDIO and pay.
-
I'm using exactly the same Canon on pdaXrom beta 3 without any problem. Worked out of the box, so I doubt you will have any problem with debian.
-
I'm using exactly the same Canon on pdaXrom beta 3 without any problem. Worked out of the box, so I doubt you will have any problem with debian.
I'm using exactly the same Canon too, on Sharp Zaurus C1000 with "Andromeda" filesystem and kernel 2.6.24-4yonggun. Work perfectly and when connect it to my Z. it's autoconfigure as eth1 interface.
-
I'm using exactly the same Canon on pdaXrom beta 3 without any problem. Worked out of the box, so I doubt you will have any problem with debian.
I'm using exactly the same Canon too, on Sharp Zaurus C1000 with "Andromeda" filesystem and kernel 2.6.24-4yonggun. Work perfectly and when connect it to my Z. it's autoconfigure as eth1 interface.
I also installed debian-andromeda, but the canon k30225 can't be detected. I see there's no hostap_cs.conf file in /etc/pcmcia (planex gw-cf11h working with andromeda and hostap)
It's being detected and working under pdaxrom
Any ideas? thanks
-
I also installed debian-andromeda, but the canon k30225 can't be detected. I see there's no hostap_cs.conf file in /etc/pcmcia (planex gw-cf11h working with andromeda
do the usual thing... "pccardctl ident" and status and inquiry etc etc, and let us know what you see. might need to do pccardctl resume before hand. (cardctl and pccardctl are equivalent commands depending on age of distro)
-
hello,
yonggun:~# pccardctl info 1
PRODID_1="Canon"
PRODID_2="Wireless LAN CF Card K30225"
PRODID_3="Version 01.00"
PRODID_4=""
MANFID=0004,2003
FUNCID=6
yonggun:~# pccardctl status 1
3.3V 16-bit PC Card
Subdevice 0 (function 0) [unbound]
yonggun:~# pccardctl ident 1
product info: "Canon", "Wireless LAN CF Card K30225", "Version 01.00", ""
manfid: 0x0004, 0x2003
function: 6 (network)
yonggun:~# dmesg | tail -n 2
pccard: PCMCIA card inserted into slot 1
pcmcia: registering new device pcmcia1.0
tried loads of things for days with no success, maybe I googled with wrong keywords for this issue, but no doc related or working for me. planex card is failing and need to replace it
thanks for your attention
-
it looks like this is a prism2 card with alternative ident... you should be able to modify your /etc/pcmcia/wlan-ng.conf (or equivalent file) to add lines like this:
card "Canon Wireless LAN CF Card K30225"
manfid 0x0004,0x2003
bind "prism2_cs"
-
added
card "Canon Wireless LAN CF Card K30225"
manfid 0x0004,0x2003
bind "prism2_cs"but main problem is that cant build prims2_cs with module-assistant as there's no linux headers
added
card "Canon Wireless LAN CF Card K30225"
manfid 0x0004,0x2003
bind "hostap_cs"to /etc/pcmcia/config
added SYSFS{manf_id} and SYSFS{card_id} in /etc/udev/rules.../70-persistent-net.rules with mac and all
tried also creating a rules file in same folder with
ACTION=="add", SYSFS{manf_id}=="0x0004", SYSFS{card_id}=="0x2003", SYSFS{func_id}=="0x06", \
RUN+="/sbin/modprobe hostap_cs ignore_cis_vcc=1"
ACTION=="add", SYSFS{manf_id}=="0x0004", SYSFS{card_id}=="0x2003", SYSFS{func_id}=="0x04", \
OPTIONS="last_rule"
edited the udev rules generation for net disabling all ignore conditions.
added options hostap_cs ignore_cis_vcc=1 to /etc/modules and modules.conf
nothing has any minimal effect, always get the:
pccard: PCMCIA card inserted into slot 1
pcmcia: registering new device pcmcia1.0
i can't even get a debug message that shows me the next step, always the same reply no matter what i do
-
http://lists.infradead.org/pipermail/linux...ary/005305.html (http://lists.infradead.org/pipermail/linux-pcmcia/2008-January/005305.html)
after reading this i don't know if it's possible to bring that card up using the custom yonggun kernel
[size=]
but seing the previous post from AltairTK
I'm using exactly the same Canon too, on Sharp Zaurus C1000 with "Andromeda" filesystem and kernel 2.6.24-4yonggun. Work perfectly and when connect it to my Z. it's autoconfigure as eth1 interface.
it's confusing, did a fresh andromeda install and nothing configured as eth1, as expected
i would like to see a lspcmcia -vvv of AltairTK's card just to check that it's not a different card[/size]
edit: i see in /hostap-driver-0.4.9/driver/modules/hostap_cs.c L:935
#if (LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,13))
static struct pcmcia_device_id hostap_cs_ids[] = {
PCMCIA_DEVICE_MANF_CARD(0x000b, 0x7100),
PCMCIA_DEVICE_MANF_CARD(0x000b, 0x7300),
...seems manfids are hardcoded in hostap driver?! 2or0 please
thanks
-
SOLVED, hexedited hostap_cs.ko, always backup the original file first!
finally, after some time forgeting it as planex card was (half)working it forced me to start checking this ebay-Canon card again.
1) i found that the same Canon K30225 might have two different manfid:
I guess AltairTK K30225 card is
Identification: manf_id: 0x0156 card_id: 0x0002
function: 6 (network)
prod_id(1): "Wireless LAN" (0x4b8870ff)
prod_id(2): "11Mbps PC Card" (0x70e946d1)
prod_id(3): "Version 01.02" (0x4b74baa0)
prod_id(4): --- (---)
as seing in http://article.gmane.org/gmane.linux.distr...93/match=k30225 (http://article.gmane.org/gmane.linux.distributions.angstrom.user/1993/match=k30225)
while my K30225 card is
product info: "Canon", "Wireless LAN CF Card K30225", "Version 01.00", ""
manfid: 0x0004, 0x2003
function: 6 (network)
hostap_cs.ko (.c with source) has
PCMCIA_DEVICE_MANF_CARD_PROD_ID1(0x0156, 0x0002, "INTERSIL",
0x74c5e40d),
PCMCIA_DEVICE_MANF_CARD_PROD_ID1(0x0156, 0x0002, "Intersil",
0x4b801a17),and might detect AltairTK's card, but hasn't 0x0004, 0x2003 (my K30225) anywhere in source file
2) forcing the detection of my card hexediting /lib/modules/(...)/wireles/hostap/hostap_cs.ko
[blockquote]* i first searched for the (text) string "m000Bc7100" and changed it to "m0004c2003"
* then searched for the hex string "0B 00 00 71" and changed it to "04 00 03 20".[/blockquote]
got the idea from here: http://sin613.blogspot.com/2007/02/i-win.html (http://sin613.blogspot.com/2007/02/i-win.html)
modified hostap_cs.ko attached: dload and untar it in the /lib/modules/(...)/net/wireles/hostap/ folder
-
well done, your persistence has paid off
I am reminded of how people discovered that the original (cheaper) Orinoco silver cards (40 bit wep) were identical to the more expensive Orinoco gold cards (full 128 bit wep), with only a different ident, so that the driver refused to use a larger key. People were able to hack the windows driver, and then someone hacked the firmware updater which allowed you to turn a silver into a gold!
-
Hi,
my wireless-cfcard work perfectly if i used a no-protected wifi connection (i have not tested with WEP encryption) because when i plugged in automatically load the orinoco driver.
If i insert Orinoco in blacklist and manually modprobe hostap my card is recognised as pcmcia but no network adapter is added (eth1, wlan0 ecc...)
-- For Same --
this is my output of dmesg when i plugged the card:
pccard: PCMCIA card inserted into slot 0
pcmcia: registering new device pcmcia0.0
pcmcia: request for exclusive IRQ could not be fulfilled.
pcmcia: the driver needs updating to supported shared IRQ lines.
eth0: Hardware identity 801b:0000:0001:0000
eth0: Station identity 001f:0004:0001:0008
eth0: Firmware determined as Intersil 1.8.4
eth0: Ad-hoc demo mode supported
eth0: IEEE standard IBSS ad-hoc mode supported
eth0: WEP supported, 104-bit key
eth0: MAC address 00:00:85:31:e2:33
eth0: Station name "Prism I"
eth0: ready
eth0: orinoco_cs at 0.0, irq 169, io 0xc4820000-0xc482003f
udev: renamed network interface eth0 to eth1
and the output of lspcmcia & pccardctl:
yonggun:/sbin# pccardctl ls
Socket 0 Bridge: [pxa2xx-pcmcia] (bus ID: pxa2xx-pcmcia)
Socket 0 Device 0: [orinoco_cs] (bus ID: 0.0)
yonggun:/sbin# pccardctl info
PRODID_1="Wireless LAN"
PRODID_2="11Mbps PC Card"
PRODID_3="Version 01.02"
PRODID_4=""
MANFID=0156,0002
FUNCID=6
yonggun:/sbin# pccardctl ident
Socket 0:
product info: "Wireless LAN", "11Mbps PC Card", "Version 01.02", ""
manfid: 0x0156, 0x0002
function: 6 (network)
-------
With orinoco drivers i have some problems with my Router and wpa encryption. I think it's not supported ( eth0: WEP supported, 104-bit key );
when i launch wpa_supplicant, iwlist, wpa_gui and wifi-radar detect my network but the led of connection is not fixed and wpa_supplicant enter in a continuous scan loop (i try wext and wired drivers).
Now I try to make the change, suggested by Same, in the configuration file of pcmcia card and to udev for (i hope) use HostAP instead of Orinoco.
-
well done, your persistence has paid off
I am reminded of how people discovered that the original (cheaper) Orinoco silver cards (40 bit wep) were identical to the more expensive Orinoco gold cards (full 128 bit wep), with only a different ident, so that the driver refused to use a larger key. People were able to hack the windows driver, and then someone hacked the firmware updater which allowed you to turn a silver into a gold!
thanks, k30225 card is quite good (range and all) and for $14 in ebay is the best option, i had to give a second try [img]http://img.alibaba.com/photo/203529069/Wireless_LAN_CF_Card_Type_II_for_PDA_K30225_.summ.jpg\" border=\"0\" class=\"linked-image\" /]
AltairTK, it seems that is loading orinoco drivers, try "apt-get install hostap-utils" it will blacklist all orinoco and other drivers that could interfere in the process
if you can'T apt-get cause no connection try to add the following lines in
/etc/modprobe.d/blacklist
blacklist orinoco_cs
blacklist orinocoalso i would check what is inside /etc/udev/rules.d/70-persistent-net.rules (or something which has the name *persistent*net.rules in that folder *NOT* the generator' file). what i did is deleting the file (backup it) and let the udev regenerate it again inserting a clean setup for your card when hostap_cs is properly "linked" to the card
if it doesn't autoload just add at the end of the /etc/modules the line "hostap_cs" without quotes, it should be wlan0 in ifconfig and iwconfig, not eth*
-
checked the wpa thing with this card:
I just did the following:
in /etc/network/interfaces I have this lines for the wlan0 card
allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-ssid MyAP
wpa-psk MyAsciiPASS
then ifdown wlan0 && ifup wlan0 and works
-
I think when I got stuck with orinoco/hermes drivers being loaded, I ended up renaming in the file system so that they couldn't be loaded, as for some reason blacklisting didn't work... but that was a while ago!
-
Well done Same, all work perfectly.
But i must to use the trick of Hex-edit the hostap_cs driver.
In teory the original driver should recognize my card (0x0156 - 0x0002), but when i plug, nothing happens. So i edit your hostap_cs.ko replacing your "m0004c2003" with my "m0156c0002" and "04 00 03 20" with "56 01 02 00".
Now, when i plug the card, the driver automatically create wlan0 interface, which is autoconfigure as written in /etc/network/interfaces and when i launch the command "wpa_supplicant" with driver wext and interface wlan0
wpa_supplicant -c /etc/wpa_supplicant.conf -D wext -i wlan0
in 1/100 of second my Z. is connected in Internet through my router :-)
Thank you very very much !
-
speculatrix: yeah that was my second choice, i did that in the past as blacklisting didn't work for me either. good point.
AltairTK: nice to see you got it working
on the other hand i think you shouldn't need to launch the wpa cmd manually.
have you tried that /etc/network/interfaces configuration with wpa-psk and wpa-ssid?
it launches the wpa_supp... cmd automatically. try to append wpa-driver wext in the iface wlan0 inet dhcp section.