LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Grafpup (https://www.linuxquestions.org/questions/grafpup-77/)
-   -   GRAFPUP 2 RC2 - WI-FI, intel ipw3945 wireless card works in Puppy but not in Grafpup. (https://www.linuxquestions.org/questions/grafpup-77/grafpup-2-rc2-wi-fi-intel-ipw3945-wireless-card-works-in-puppy-but-not-in-grafpup-558248/)

mike sumner 06-01-2007 05:01 AM

GRAFPUP 2 RC2 - WI-FI, intel ipw3945 wireless card problem - SOLVED****
 
Hi guys, hope someone can help me out. I have been using Puppy since January, starting with 2.13, and one of the things that made it so attractive was that it was the first distro I tried that supported my wifi. I really like the way Grafpup 2 is put together, but for some reason, even though it is similar to puppy, I have never been able to get the wifi to work. Going back a couple of releases, before the new kernel was introduced, the driver was there and the os could see the router but I could not get online. Since moving to the new kernel, there is no driver and modprobe does not work. I dont know whether the module will not compile, or what. I don't know if the module has to be included in the kernel when the kernel is compiled or whether it can be added after? I do not understand compiling and modules etc. so I am a bit out of my depth,:confused: and Nathan seems to be having problems with getting it working, so I was hoping that some of you old hands out there might be able to help.
Thanks in anticipation!
Cheers, Mike

Dell inspiron 6400 laptop

Nathan F 06-01-2007 03:36 PM

Correction Mike, the driver has been there for some time but apparently there were a few bugs related to using it with the 2.6.20 kernel. I just compiled a slightly newer version I'd like for you to try, located here. This is a PET package so you should be able to just click on it to install. I need to know asap whether or not this is working, as I want to get the final out in the next couple days at the latest. Truthfully today would be even better.

Nathan

mike sumner 06-01-2007 06:11 PM

Hi Nathan, Thanks for that, no joy though.

modprobed:

sh-3.00# modprobe ipw3945
FATAL: Error inserting ipw3945 (/lib/modules/2.6.20.2/kernel/drivers/net/wireless/ipw3945.ko): Unknown symbol in module, or unknown parameter (see dmesg)
sh-3.00#

This appears to be the relevent dmsg output:

ipw3945: Unknown symbol ieee80211_wx_get_encodeext
ipw3945: Unknown symbol release_firmware
ipw3945: Unknown symbol ieee80211_wx_set_encode
ipw3945: Unknown symbol ieee80211_wx_get_encode
ipw3945: Unknown symbol ieee80211_txb_free
ipw3945: Unknown symbol ieee80211_wx_set_encodeext
ipw3945: Unknown symbol request_firmware
ipw3945: Unknown symbol ieee80211_wx_get_scan
ipw3945: Unknown symbol escape_essid
ipw3945: Unknown symbol ieee80211_freq_to_channel
ipw3945: Unknown symbol ieee80211_set_geo
ipw3945: Unknown symbol ieee80211_rx
ipw3945: Unknown symbol ieee80211_get_channel
ipw3945: Unknown symbol ieee80211_channel_to_index
ipw3945: Unknown symbol ieee80211_rx_mgt
ipw3945: Unknown symbol ieee80211_get_geo
ipw3945: Unknown symbol free_ieee80211
ipw3945: Unknown symbol ieee80211_tx_frame
ipw3945: Unknown symbol ieee80211_is_valid_channel
ipw3945: Unknown symbol ieee80211_get_channel_flags
ipw3945: Unknown symbol alloc_ieee80211
ipw3945: Unknown symbol ieee80211_wx_get_encodeext
ipw3945: Unknown symbol release_firmware
ipw3945: Unknown symbol ieee80211_wx_set_encode
ipw3945: Unknown symbol ieee80211_wx_get_encode
ipw3945: Unknown symbol ieee80211_txb_free
ipw3945: Unknown symbol ieee80211_wx_set_encodeext
ipw3945: Unknown symbol request_firmware
ipw3945: Unknown symbol ieee80211_wx_get_scan
ipw3945: Unknown symbol escape_essid
ipw3945: Unknown symbol ieee80211_freq_to_channel
ipw3945: Unknown symbol ieee80211_set_geo
ipw3945: Unknown symbol ieee80211_rx
ipw3945: Unknown symbol ieee80211_get_channel
ipw3945: Unknown symbol ieee80211_channel_to_index
ipw3945: Unknown symbol ieee80211_rx_mgt
ipw3945: Unknown symbol ieee80211_get_geo
ipw3945: Unknown symbol free_ieee80211
ipw3945: Unknown symbol ieee80211_tx_frame
ipw3945: Unknown symbol ieee80211_is_valid_channel
ipw3945: Unknown symbol ieee80211_get_channel_flags
ipw3945: Unknown symbol alloc_ieee80211
sh-3.00#

Nathan F 06-01-2007 06:52 PM

The dmesg output found it for me. I have the iee80211 subsystem installed on my computer, but somehow it got left out of the zdrv file. Try the same download again, but this time it will be a little bigger because it has some extra modules in it. Then just click and install again.

Nathan

mike sumner 06-02-2007 02:12 AM

Still no go, new dmesg:

ipw3945: Unknown symbol ieee80211_wx_get_encodeext
ipw3945: Unknown symbol release_firmware
ipw3945: Unknown symbol ieee80211_wx_set_encode
ipw3945: Unknown symbol ieee80211_wx_get_encode
ipw3945: Unknown symbol ieee80211_txb_free
ipw3945: Unknown symbol ieee80211_wx_set_encodeext
ipw3945: Unknown symbol request_firmware
ipw3945: Unknown symbol ieee80211_wx_get_scan
ipw3945: Unknown symbol escape_essid
ipw3945: Unknown symbol ieee80211_freq_to_channel
ipw3945: Unknown symbol ieee80211_set_geo
ipw3945: Unknown symbol ieee80211_rx
ipw3945: Unknown symbol ieee80211_get_channel
ipw3945: Unknown symbol ieee80211_channel_to_index
ipw3945: Unknown symbol ieee80211_rx_mgt
ipw3945: Unknown symbol ieee80211_get_geo
ipw3945: Unknown symbol free_ieee80211
ipw3945: Unknown symbol ieee80211_tx_frame
ipw3945: Unknown symbol ieee80211_is_valid_channel
ipw3945: Unknown symbol ieee80211_get_channel_flags
ipw3945: Unknown symbol alloc_ieee80211
ipw3945: Unknown symbol ieee80211_wx_get_encodeext
ipw3945: Unknown symbol release_firmware
ipw3945: Unknown symbol ieee80211_wx_set_encode
ipw3945: Unknown symbol ieee80211_wx_get_encode
ipw3945: Unknown symbol ieee80211_txb_free
ipw3945: Unknown symbol ieee80211_wx_set_encodeext
ipw3945: Unknown symbol request_firmware
ipw3945: Unknown symbol ieee80211_wx_get_scan
ipw3945: Unknown symbol escape_essid
ipw3945: Unknown symbol ieee80211_freq_to_channel
ipw3945: Unknown symbol ieee80211_set_geo
ipw3945: Unknown symbol ieee80211_rx
ipw3945: Unknown symbol ieee80211_get_channel
ipw3945: Unknown symbol ieee80211_channel_to_index
ipw3945: Unknown symbol ieee80211_rx_mgt
ipw3945: Unknown symbol ieee80211_get_geo
ipw3945: Unknown symbol free_ieee80211
ipw3945: Unknown symbol ieee80211_tx_frame
ipw3945: Unknown symbol ieee80211_is_valid_channel
ipw3945: Unknown symbol ieee80211_get_channel_flags
ipw3945: Unknown symbol alloc_ieee80211
ipw3945: Unknown symbol ieee80211_wx_get_encodeext
ipw3945: Unknown symbol release_firmware
ipw3945: Unknown symbol ieee80211_wx_set_encode
ipw3945: Unknown symbol ieee80211_wx_get_encode
ipw3945: Unknown symbol ieee80211_txb_free
ipw3945: Unknown symbol ieee80211_wx_set_encodeext
ipw3945: Unknown symbol request_firmware
ipw3945: Unknown symbol ieee80211_wx_get_scan
ipw3945: Unknown symbol escape_essid
ipw3945: Unknown symbol ieee80211_freq_to_channel
ipw3945: Unknown symbol ieee80211_set_geo
ipw3945: Unknown symbol ieee80211_rx
ipw3945: Unknown symbol ieee80211_get_channel
ipw3945: Unknown symbol ieee80211_channel_to_index
ipw3945: Unknown symbol ieee80211_rx_mgt
ipw3945: Unknown symbol ieee80211_get_geo
ipw3945: Unknown symbol free_ieee80211
ipw3945: Unknown symbol ieee80211_tx_frame
ipw3945: Unknown symbol ieee80211_is_valid_channel
ipw3945: Unknown symbol ieee80211_get_channel_flags
ipw3945: Unknown symbol alloc_ieee80211
ipw3945: Unknown symbol ieee80211_wx_get_encodeext
ipw3945: Unknown symbol release_firmware
ipw3945: Unknown symbol ieee80211_wx_set_encode
ipw3945: Unknown symbol ieee80211_wx_get_encode
ipw3945: Unknown symbol ieee80211_txb_free
ipw3945: Unknown symbol ieee80211_wx_set_encodeext
ipw3945: Unknown symbol request_firmware
ipw3945: Unknown symbol ieee80211_wx_get_scan
ipw3945: Unknown symbol escape_essid
ipw3945: Unknown symbol ieee80211_freq_to_channel
ipw3945: Unknown symbol ieee80211_set_geo
ipw3945: Unknown symbol ieee80211_rx
ipw3945: Unknown symbol ieee80211_get_channel
ipw3945: Unknown symbol ieee80211_channel_to_index
ipw3945: Unknown symbol ieee80211_rx_mgt
ipw3945: Unknown symbol ieee80211_get_geo
ipw3945: Unknown symbol free_ieee80211
ipw3945: Unknown symbol ieee80211_tx_frame
ipw3945: Unknown symbol ieee80211_is_valid_channel
ipw3945: Unknown symbol ieee80211_get_channel_flags
ipw3945: Unknown symbol alloc_ieee80211
sh-3.00#

Nathan F 06-02-2007 08:09 PM

Mike -

Make sure you load the iee80211 module first. You may have to run depmod to make sure the system knows it's there. There are also some other modules in the same directory (/lib/modules/net/iee80211) which you may need for encrypted networks.

Ideally, it should all be automatic with the final iso, since it has the updated ipw3945 module and the missing iee80211 subsystem. I'm sorry we never verified that before the release, but for personal reasons yesterday was the latest that I could do the release, or else it would have had to be delayed for quite some time.

Nathan

mike sumner 06-03-2007 05:07 AM

Quote:

Originally Posted by Nathan F
Mike -

Make sure you load the iee80211 module first. You may have to run depmod to make sure the system knows it's there. There are also some other modules in the same directory (/lib/modules/net/iee80211) which you may need for encrypted networks.


Nathan

Hi Nathan, sorry but i'm struggling a bit here.
Do not know if it is relevant but the path quoted above is different in my file system. No /net in /lib/modules?
Anyway:
Downloaded and booted 2.00 final.
Downloaded pet package to /root.
Clicked, then picked the install option.

Something must have changed because the relevant dmesg output is much shorter. And there are 3 e's in ieee80211. Could this extra "e" be missing somewhere, or am I clutching at straws! Can you check out what I did in the terminal to see if it is right:

sh-3.00# modprobe iee80211
FATAL: Module iee80211 not found.
sh-3.00# modprobe ieee80211
sh-3.00# depmod
sh-3.00# modprobe ipw3945
FATAL: Error inserting ipw3945 (/lib/modules/2.6.20.2/kernel/drivers/net/wireless/ipw3945.ko): Unknown symbol in module, or unknown parameter (see dmesg)
sh-3.00# dmesg

ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, 1.2.17
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
ipw3945: Unknown symbol release_firmware
ipw3945: Unknown symbol request_firmware
ipw3945: Unknown symbol release_firmware
ipw3945: Unknown symbol request_firmware
sh-3.00#

If I am getting something wrong here, you may have to walk me through it.
Cheers, Mike
EDIT Is this relevant? http://ipw3945.sourceforge.net/

mike sumner 06-07-2007 04:45 AM

Hi Nathan, just bumping the thread to see if you've made any more progress on the driver. See my last post for error msgs.

mike sumner 06-08-2007 03:54 AM

Nathan, I would really appreciate it if you would just let me know if I am doing something wrong here or whether there is still a bug in the package.

Nathan F 06-08-2007 11:19 AM

My apologies Mike, I've been incredibly tied up for a while and missed your last couple posts. You are correct about my typo, it should be ieee80211. Also, the directory I mentioned should be /lib/modules/2.6.20.2/net I think.

The link you posted is the project page for the driver, and that is where I obtained all the sources. So yes, it is relevent.

I found another problem after some serious digging. I should have built hotplug firmware loading support into the kernel, but apparently it was built as a module instead. That is where the last missing symbol is coming from. In addition to loading the ieee80211 module you will also need to load the firmware_class module before loading ipw3945. I've tested (but still without having the card) and that allows the ipw3945 module to load fine. After that the firmware will need initialised and then hopefully it should be up and running. I'll check back with you later, probably tonight.

Nathan

mike sumner 06-08-2007 06:20 PM

Hi Nathan, the modprobes all seemed to work with no error messages:

sh-3.00# modprobe ieee80211

sh-3.00# modprobe firmware_class

sh-3.00# modprobe ipw3945

sh-3.00#

Should the driver appear as loaded in the network wizard? It is not there, so I do not know how to proceed:scratch: It does not appear in the list either.

I presume you want to put it in the upgrade package? Should I wait for that or do you need me to get it working first?
Mike

Nathan F 06-09-2007 08:39 AM

Well I think it's important to get through all the steps that ight be required to get a working interface before putting it in a patch. I think we've come a long way but there is still probably a good bit more to go. We need to get the firmware running now, which is in the zdrv squashfile. Do you know how to mount a squashfile from the command line?
Code:

mount -o loop -t squashfs (location of squashfile) (mountpoint)
Once you have it mounted you can grab the needed files out of it. There should only be two, /lib/firmware/ipw3945.ucode and /sbin/ipw3945d. Once they are in the correct place then make sure you have the modules loaded and then run the regulatory daemon ipw3945d.
Code:

/sbin/ipw3945d &
I'm not 100% sure you will need the & but it won't hurt. At that point we need to see if your interface is recognized, because it should be. From what I understand it should shw up as an eth interface, so if you have one normal wired connection it would show up as eth1. If you get nothing in the network wizard check it like this:
Code:

iwconfig eth1
That should return a bunch of information about the interface, if everything worked out ok. You could even set it up manually at this point, using iwconfig.
Code:

iwconfig eth1 essid Whatever
iwconfig eth1 key DEADBEEF00
iwconfig eth1

Of course replace Whatever and DEADBEEFOO with you correct essid and key. Or, if your network is not encrypted you won't have a key.

This should have all been manual, of course, but apparently some files relating to your interface got either dropped or the relevent sections weren't updated right when I switched to the new kernel. That is all totally my fault, now that I look back on it with a little more understanding. I'd like to put things right and have it working without any fuss for 2.01.

Nathan

mike sumner 06-09-2007 11:56 AM

Sorry Nathan, but I am being rather dense here. Fallen at the first hurdle.
It is a type 2 install and the zdrf_200.sfs is in /
Am I correct that the mountpoint is /zdrf_200.sfs?
But if this is the mountpoint, what is the location? My faulty logic tells me it would be the same but I guess it isn't.
Help!:confused:

Nathan F 06-09-2007 04:25 PM

Code:

mount -o loop -t squashfs /zdrv_200.sfs /mnt/data
That would mount it on /mnt/data. Then you need to copy /mnt/data/lib/firmware/ipw3945.ucode to /lib/firmware/ipw3945.ucode and /mnt/data/sbin/ipw3945d to /sbin/ipw3945d. Let me know how it comes out for you.

Nathan

mike sumner 06-09-2007 06:00 PM

managed to do that but modprobes dont work:

FATAL: Module ipw3945.ucode not found.
also, tried this:
sh-3.00# /sbin/ipw3945d &
ipw3945d - regulatory daemon
Copyright (C) 2005-2006 Intel Corporation. All rights reserved.
version: 1.7.22
2007-06-09 23:12:06: ERROR: Could not find Intel PRO/Wireless 3945ABG Network Connection
[1] 8271
[1] Done /sbin/ipw3945d
sh-3.00#


All times are GMT -5. The time now is 01:20 AM.