Recognition of ipw2100 in network wizard

Message

#1 Post by **BÃ©Ã¨m** » Wed 16 May 2007, 12:23

I hoped my WiFi card would be recognized now with the 2.16rc in the network wizard and loaded.

This is still not the case and the ipw2200 is loaded instead.
I load the ipw2100 by hand in the NW wizard and push save.
Fortunately on next boot the ipw2100 is loaded (together with the not needed ipw2200) and configuration is preserved.

It would be nice to have only the ipw2100 recognized and loaded when installing afresh as I don't know if there could be an interaction between the ipw2200 and ipw2100, which prevents the WiFi adapter to work flawlessly.

jonyo · #2 Post by **jonyo** » Thu 17 May 2007, 00:05

Had a similar prob in 2.15 with a bcm43xx scenario & someone gave me these instructions
that I didn't try out.
-----------------------------------------------------
Hi Jonyo
In an earlier message I used this to stop the BCM43xx driver from loading:

Right now you will have to do it manually:
1. In a text editor open the following file : /etc/rc.d/rc.modules
2. In line 32 of that file, add the module you want to blacklist. Always leave a space before closing the quotes.

That line will look like the following:Code:
SKIPLIST=" arcfb cirrusfb cyber2000fb cyblafb hgafb neofb pm2fb s1d13xxxfb sstfb tdfxfb tridentfb vga16fb aty128fb atyfb radeonfb i810fb intelfb kyrofb nvidiafb rivafb savagefb sisfb bcm43xx "

3. Save your changes and close the file.

Hope this helps

#3 Post by **BÃ©Ã¨m** » Thu 17 May 2007, 00:22

Thanks Jonyo, this seems to work.

But it doesn't solve the base problem, that the ipw2100 adapter isn't detected as such and that it is considered as a ipw2200.

tempestuous · #4 Post by **tempestuous** » Thu 17 May 2007, 04:19

Béèm,
Your problem is caused by the way that Intel defines its pci id numbers.
All Intel PRO/Wireless 2100/2200/2915 adaptors have a "family" pci id of 8086 1043.
Then each individual model has a secondary pci id, which will be something like 8086 2701 for example.
If you open /lib/modules/2.6.18.1/modules.pcimap in a text editor you will see what I mean.
Because the family pci id is read first, the ipw2200 driver claims ALL of these devices. It's Intel's fault.

jonyo has a good point. You should blacklist the ipw2200 driver, then add this command to the end of /etc/rc.d/rc.local -

modprobe ipw2100

BarryK · #5 Post by **BarryK** » Thu 05 Jul 2007, 01:48

Beem and Jonyo, can you guys do something for me.
I can't simply blacklist the ipw2200 and bcm43xx drivers, but I can get the correct drivers to load if I know what your wifi chipset IDs are.

One way to find these is to run PupScan, that you will find in the System menu. Click the button in the "PCI interfaces" section -- the latest version of PupScan in 2.17exp1 only has one button in the this section, older PupScans have two buttons -- the right-most one will list all the PCI interfaces and show what modules are loaded for each.

Anyway, find the wifi interface, you will see something like this (this example is the wifi interface on my laptop):

DESCRIPTION: Atheros Communications, Inc. AR5005G 802.11abg NIC
VENDOR: 168c DEVICE: 001a KERNEL MODULE: ath_pci

...its those VENDOR, DEVICE numbers I need.

Note, I am informed that Dougal is working on something a bit more generic to handle the Intel vendor:device numbering, which is better long-term, but if you give me the IDs I can immediately patch-in the correct module loading for your chips.

HairyWill · #6 Post by **HairyWill** » Thu 05 Jul 2007, 07:24

I've got an ipw2200 and can't find any reference to 8086:1043

Code: Select all

#lspci -vb | grep 1043
#

lspci -vb shows the following for my nic

Code: Select all

01:02.0 Class 0280: 8086:4220 (rev 05)
        Subsystem: 8086:2702
        Flags: bus master, medium devsel, latency 64, IRQ 11
        Memory at d0200000 (32-bit, non-prefetchable)
        Capabilities: [dc] Power Management version 2

I presume it is the subsystem that is interesting.
Apologies if you knew all this already.

tempestuous · #7 Post by **tempestuous** » Thu 05 Jul 2007, 14:35

Here's the section of /lib/modules/modules.pcimap.2.6.18.1 that I was talking about.
Most drivers list their unique vendor-device numbers first in columns 1 and 2, but with the ipw series the common vendor-device number of 8086 1043 is listed first for 57 out of 62 variants. HairyWill just happens to have one of the 5 exceptions.

I suppose a solution would be to hack this list to shift columns 3 and 4 to become columns 1 and 2. I then wonder what should go in colums 3 and 4,
"0xffffffff 0xffffffff" perhaps?

ipw2200 0x00008086 0x00001043 0x00008086 0x00002701 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x00008086 0x00002702 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x00008086 0x00002711 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x00008086 0x00002712 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x00008086 0x00002721 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x00008086 0x00002722 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x00008086 0x00002731 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x00008086 0x00002732 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x00008086 0x00002741 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x0000103c 0x00002741 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x00008086 0x00002742 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x00008086 0x00002751 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x00008086 0x00002752 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x00008086 0x00002753 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x00008086 0x00002754 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x00008086 0x00002761 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00001043 0x00008086 0x00002762 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x0000104f 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00004220 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00004221 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00004223 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
ipw2200 0x00008086 0x00004224 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002520 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002521 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002524 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002525 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002526 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002522 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002523 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002527 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002528 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002529 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x0000252b 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x0000252c 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x0000252d 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002550 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002551 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002553 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002554 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002555 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002560 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002562 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002563 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002561 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002565 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002566 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002567 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002570 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002580 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002582 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002583 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002581 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002585 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002586 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002587 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002590 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002592 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002591 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002593 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002596 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x00002598 0x00000000 0x00000000 0x0
ipw2100 0x00008086 0x00001043 0x00008086 0x000025a0 0x00000000 0x00000000 0x0

jonyo · #8 Post by **jonyo** » Thu 05 Jul 2007, 16:42

I use both cards on 2 diff laps & don't recall any probs with the onboard ipw card usin auto detect native drivers. I'll get on it first chance I get.
In regards to my bcm probs, I had a few posts when I was tryin to sort it out. Blacklisting the native driver that auto loaded on every boot (in 2.15) was the answer for me. The .inf file worked A-1 & was a piece of cake to set up

as in prior vers.
Might help explain a bit..
http://www.murga-linux.com/puppy/viewto ... 253#109659
http://www.murga-linux.com/puppy/viewto ... 253#109767
http://www.murga-linux.com/puppy/viewto ... 253#109932

jonyo · #9 Post by **jonyo** » Thu 05 Jul 2007, 21:23

Ok, booted up the acer 2420 travelmate with the ipw card in 2.15 (first time..prior vers before that) & net wiz shows ipw2200 which auto loads on boot & am on the net.

pci scan: (don't think the first part is required..)
(pci bus 0x0000 cardnum 0x1f function 0x03: vendor 0x8086 device 0x266a
Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller)

pci bus 0x0006 cardnum 0x05 function 0x00: vendor 0x8086 device 0x4220
Intel Corporation PRO/Wireless 2200BG

Gateway m-520 with BCM43xx
pci bus 0x0001 cardnum 0x09 function 0x00: venodor 0x14e4 device 0x4320
Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller

Thought i might add, that in regard to the info (below) in my 2.15 setup, it falls in line 36 & line 32 is blank.
------------------------------------------------------------------
"Right now you will have to do it manually:
1. In a text editor open the following file : /etc/rc.d/rc.modules
2. In line 32 of that file, add the module you want to blacklist. Always leave a space before closing the quotes.

That line will look like the following:Code:
SKIPLIST=" arcfb cirrusfb cyber2000fb cyblafb hgafb neofb pm2fb s1d13xxxfb sstfb tdfxfb tridentfb vga16fb aty128fb atyfb radeonfb i810fb intelfb kyrofb nvidiafb rivafb savagefb sisfb bcm43xx "
--------------------------------------------------------------
I do have another bcm43xx card that I might be able to get info on if it'd help.

#10 Post by **BÃ©Ã¨m** » Fri 06 Jul 2007, 23:51

BarryK wrote:Beem and Jonyo, can you guys do something for me.
I can't simply blacklist the ipw2200 and bcm43xx drivers, but I can get the correct drivers to load if I know what your wifi chipset IDs are.

One way to find these is to run PupScan, that you will find in the System menu. Click the button in the "PCI interfaces" section -- the latest version of PupScan in 2.17exp1 only has one button in the this section, older PupScans have two buttons -- the right-most one will list all the PCI interfaces and show what modules are loaded for each.

Anyway, find the wifi interface, you will see something like this (this example is the wifi interface on my laptop):

DESCRIPTION: Atheros Communications, Inc. AR5005G 802.11abg NIC
VENDOR: 168c DEVICE: 001a KERNEL MODULE: ath_pci

...its those VENDOR, DEVICE numbers I need.

Note, I am informed that Dougal is working on something a bit more generic to handle the Intel vendor:device numbering, which is better long-term, but if you give me the IDs I can immediately patch-in the correct module loading for your chips.

This is what is detected, but it's wrong.

DESCRIPTION: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter
VENDOR: 8086 DEVICE: 1043 KERNEL MODULE: ipw2200

From dmesg I extracted the ipw devices

ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.0k
ipw2200: Copyright(c) 2003-2006 Intel Corporation
ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
ipw2100: Copyright(c) 2003-2006 Intel Corporation

From puppyscan this is the info of ipw2100 loaded by hand.

filename: /lib/modules/2.6.21.5/kernel/drivers/net/wireless/ipw2100.ko
description: Intel(R) PRO/Wireless 2100 Network Driver
version: git-1.2.2
author: Copyright(c) 2003-2006 Intel Corporation
license: GPL
vermagic: 2.6.21.5 mod_unload 486
depends: firmware_class,ieee80211
alias: pci:v00008086d00001043sv00008086sd00002520bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002521bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002524bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002525bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002526bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002522bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002523bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002527bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002528bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002529bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd0000252Bbc*sc*i*
alias: pci:v00008086d00001043sv00008086sd0000252Cbc*sc*i*
alias: pci:v00008086d00001043sv00008086sd0000252Dbc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002550bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002551bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002553bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002554bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002555bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002560bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002562bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002563bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002561bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002565bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002566bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002567bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002570bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002580bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002582bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002583bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002581bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002585bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002586bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002587bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002590bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002592bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002591bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002593bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002596bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002598bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd000025A0bc*sc*i*
srcversion: E319E911F6ABD9F7735E244
parm: disable:manually disable the radio (default 0 [radio on]) (int)
parm: associate:auto associate when scanning (default on) (int)
parm: channel:channel (int)
parm: mode:network mode (0=BSS,1=IBSS,2=Monitor) (int)
parm: debug:debug level (int)

The same for the ipw2200 loaded automatically

filename: /lib/modules/2.6.21.5/kernel/drivers/net/wireless/ipw2200.ko
description: Intel(R) PRO/Wireless 2200/2915 Network Driver
version: 1.2.0k
author: Copyright(c) 2003-2006 Intel Corporation
license: GPL
vermagic: 2.6.21.5 mod_unload 486
depends: ieee80211,firmware_class
alias: pci:v00008086d00001043sv00008086sd00002701bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002702bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002711bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002712bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002721bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002722bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002731bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002732bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002741bc*sc*i*
alias: pci:v00008086d00001043sv0000103Csd00002741bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002742bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002751bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002752bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002753bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002754bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002761bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002762bc*sc*i*
alias: pci:v00008086d0000104Fsv*sd*bc*sc*i*
alias: pci:v00008086d00004220sv*sd*bc*sc*i*
alias: pci:v00008086d00004221sv*sd*bc*sc*i*
alias: pci:v00008086d00004223sv*sd*bc*sc*i*
alias: pci:v00008086d00004224sv*sd*bc*sc*i*
srcversion: D49A9EC8446976A876F5F04
parm: antenna:select antenna 1=Main, 3=Aux, default 0 [both], 2=slow_diversity (choose the one with lower background noise) (int)
parm: roaming:enable roaming support (default on) (int)
parm: cmdlog:allocate a ring buffer for logging firmware commands (int)
parm: hwcrypto:enable hardware crypto (default off) (int)
parm: bt_coexist:enable bluetooth coexistence (default off) (int)
parm: mode:network mode (0=BSS,1=IBSS) (int)
parm: channel:channel to limit associate to (default 0 [ANY]) (int)
parm: debug:debug output mask (int)
parm: led:enable led control on some systems (default 0 off)
(int)
parm: auto_create:auto create adhoc network (default on) (int)
parm: associate:auto associate when scanning (default on) (int)
parm: disable:manually disable the radio (default 0 [radio on]) (int)

In lspci -vb I find

02:02.0 Class 0280: 8086:1043 (rev 04)
Subsystem: 8086:2551
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at c0204000 (32-bit, non-prefetchable)
Capabilities: [dc] Power Management version 2

I hope this is what you are looking for, otherwise instruct me further.

jonyo · #11 Post by **jonyo** » Sat 07 Jul 2007, 01:36

jonyo wrote:Gateway m-520 with BCM43xx
pci bus 0x0001 cardnum 0x09 function 0x00: venodor 0x14e4 device 0x4320
Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller

It could be that the driver that comes with pup in 2.15, along with the firwware fix can be made to work (with the above) properly. I just had ltd success (& tons of hours & pia..

) basically fumbling about..with what little I know..if things don't go straightforward...

Turned out that nobody in the know chimed in (as far as fixin it) when I was tryin to sort it out but someone knew about how to blacklist & sent a PM.
Worked great in earlier vers pups with the .inf file so went that route.

Edit-ahhhhh.. just realized

i didn't provide the info requested with pupscan..will get back..once I get it.

BarryK · #12 Post by **BarryK** » Sat 07 Jul 2007, 02:42

Beem, thanks for all that information. I have a solution, but just to confirm something, could you run this:

# lspci -m -n -d 8086:1043

and post the repsonse.

jonyo · #13 Post by **jonyo** » Sat 07 Jul 2007, 03:04

DESCRIPTION: Intel Corporation PRO/Wireless 2200BG
VENDOR: 8086 DEVICE: 4220 KERNEL MODULE: ipw2200

DESCRIPTION: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller
VENDOR: 14e4 DEVICE: 4320 KERNEL MODULE: bcm43xx

#14 Post by **BÃ©Ã¨m** » Sat 07 Jul 2007, 21:46

BarryK wrote:Beem, thanks for all that information. I have a solution, but just to confirm something, could you run this:

# lspci -m -n -d 8086:1043

and post the repsonse.

This command gives:

02:02.0 "Class 0280" "8086" "1043" -r04 "1043" "2551"

Another problem I have is, that I can't get a working connection through the network wizard. My access point is found, the parameters given and when I select dhcp I get the message configuration unsuccessful (after 60 seconds)

But with RutilT I can configure and get a connection.

Linked to the detection issue?

jonyo · #15 Post by **jonyo** » Sat 07 Jul 2007, 22:23

Béèm wrote:Another problem I have is, that I can't get a working connection through the network wizard. My access point is found, the parameters given and when I select dhcp I get the message configuration unsuccessful (after 60 seconds)
But with RutilT I can configure and get a connection.

I have this issue with the ipw 2200 also in 2.15. In my other setups, (way) more often than not, I also have to use RutilT & even then, the wifi connection uisn RutilT is often diff for diff setups. What works on one doesn't work on another. Sometimes I have to add a profile, other times not. Sometimes a scan establishes a connection. Other times just clicking on a profile (don't have to hit connect) - then I usually have to hit auto dhcp, sometimes 2-3 times.

Very rare occasion i've had that I get a connection from the net wiz that then boots up clean into a wifi connection, all with the same wep settings from 2.12 to 5 - always seems to be a bit diff. Read about fixes here & there but can't say I tried any out. Don't mind having to take a few steps & never read any instructions on how to do it say.. in a proper way. All GUI so far also.

Workin out right now in my one 2.16 setup though.

BarryK · #16 Post by **BarryK** » Sun 08 Jul 2007, 01:20

Béèm wrote:02:02.0 "Class 0280" "8086" "1043" -r04 "1043" "2551"

Good. For 2.17alpha (to be released in a day or two probably), Puppy checks that last parameter. If it has '25' in the first two characters, then the ipw2100 has to be loaded. This fix is in the /etc/rc.d/rc.modules script.

#17 Post by **BÃ©Ã¨m** » Sun 08 Jul 2007, 09:16

BarryK wrote:
Béèm wrote:02:02.0 "Class 0280" "8086" "1043" -r04 "1043" "2551"
Good. For 2.17alpha (to be released in a day or two probably), Puppy checks that last parameter. If it has '25' in the first two characters, then the ipw2100 has to be loaded. This fix is in the /etc/rc.d/rc.modules script.

Thank you, I'll let you know here as soon as I can use the alpha. (will be without internet from Tuesday on)

#18 Post by **BÃ©Ã¨m** » Sun 26 Aug 2007, 22:29

Béèm wrote:
BarryK wrote:Beem, thanks for all that information. I have a solution, but just to confirm something, could you run this:

# lspci -m -n -d 8086:1043

and post the repsonse.
This command gives:
02:02.0 "Class 0280" "8086" "1043" -r04 "1043" "2551"
Another problem I have is, that I can't get a working connection through the network wizard. My access point is found, the parameters given and when I select dhcp I get the message configuration unsuccessful (after 60 seconds)

But with RutilT I can configure and get a connection.

Linked to the detection issue?

Sorry to respond only now, but I have been away for > 6 weeks.
In the meantime I use the 2.17.1 now.

There is good and bad news.
The good news: At first boot the ipw2100 is detected now and not the ipw2200 anymore.
So I configure and do a save of the network setup.
Then a poweroff and have choosen to save to pup_save
Now the bad news: When rebooting only the ipw2200 is recognized as before and not the ipw2100.
Once loaded by hand I can configure the ipw2100 for connection to internet.

So the ipw2100-2200 issue is still alive.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Recognition of ipw2100 in network wizard

Recognition of ipw2100 in network wizard