Old Dell Latitude D610 Wireless missing

[jssouza]

Maybe better to remaster the ISO - add the 3.0.1 vmlinuz and 000-kernel into the 4.0 one and recreate the iso.

[Ed_P]

I tried that earlier with a different ISO and had problems. I couldn't make the ISO on the 586 system, it kept hanging I believe. And creating the x586 ISO on the x86_64 system had an error when booting on the x586 system. That's why neko stepping in helped.

I'm looking into boot options.

[donald]

Ed
what i would do:
take a spare usb thumbdrive > make a normal install
(msdos partition table, ext2 filesystem, stock porteus-4)
no grub/iso booting trickery.
You do not need the EFI folder if you want the Thumbdrive to start a 32-bit non-UEFI machine.
only boot and porteus are needed.
Use the from= cheatcode to avoid confusion with existing files on the hard disk.
Example:
APPEND from=UUID:your_string_here changes=UUID:your_string_here/porteus
You get the string with the blkid command.

Start the maschine with this thumbdrive > check if there are firmware files
ipw2200-bss.fw
ipw2200-ibss.fw
ipw2200-sniffer.fw

Test all the firmware files you have, place them into /lib/firmware/
(only one set at a time)
and use as root
modprobe -r ipw2200
modprobe ipw2200

Check all the firmware files you have -- i would start with the 3.0.1 files
because this version worked (?)
[extract the files from the modules]

If no combination works, I would try another live distro e.g. salix,slackel,ubuntu
If any of them work, check what firmware files they have and try them out as well.
------------------------------------------------------------------------------------------

a command to determine the version of the ipw2200 driver (the *.ko file) is (as root)
modinfo ipw2200

[donald]

Small problem here, if ipw2200 is not loaded the first command fails and hence the second command of actual modprobe wont work....

That's right, but based on the previous posts, you can almost certainly say
that ipw2200 was always loaded.

If you were certain, then just the second command would've sufficed woudn't it? Why then type in modprobe -r ipw2200 if it was certain ipw2200 was not loaded? And if not certain.. the 2nd command fails

Here you have another one

Code: Select all

#!/bin/bash
if lsmod | grep -q "ipw2200"
then
modprobe -r ipw2200 && modprobe ipw2200

else
modprobe ipw2200

fi

You know the goal is to un-/reload the driver after changes have been made (firmware),do you?

[jssouza]

You know the goal is to un-/reload the driver after changes have been made (firmware),do you?

Kinda pointless question, seeing who suspected and confirmed the firmware was missing and suggested the un/reloading of the driver in the first place

Here you have another one

Code: Select all

#!/bin/bash
if lsmod | grep -q "ipw2200"
then
modprobe -r ipw2200
fi
modprobe ipw2200

[Ed_P]

Thank you guys for being patient. In addition to working on the Dell system I'm working on getting my wife's replacement working for her. Her old Windows 10 HP notebook died last week and while the new HP is Windows 10 also its an "S" version which has some idiosyncracies.

Ok, here's what I have from the 3 systems, all running with the vmlinuz and 001-kernel files from the 3.0.1 ISO system and all run as booted ISOs. I got the grub4dos menu problem fixed.

Porteus 3.0.1

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# modinfo ipw2200
filename:       /lib/modules/3.14.15-porteus/kernel/drivers/net/wireless/ipw2x00/ipw2200.ko
firmware:       ipw2200-bss.fw
firmware:       ipw2200-sniffer.fw
firmware:       ipw2200-ibss.fw
license:        GPL
author:         Copyright(c) 2003-2006 Intel Corporation
version:        1.2.2kmpr
description:    Intel(R) PRO/Wireless 2200/2915 Network Driver
srcversion:     743C1D496825C286F776DCB
alias:          pci:v00008086d00004224sv*sd*bc*sc*i*
alias:          pci:v00008086d00004223sv*sd*bc*sc*i*
alias:          pci:v00008086d00004221sv*sd*bc*sc*i*
alias:          pci:v00008086d00004220sv*sd*bc*sc*i*
alias:          pci:v00008086d0000104Fsv*sd*bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002762bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002761bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002754bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002753bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002752bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002751bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002742bc*sc*i*
alias:          pci:v00008086d00001043sv0000103Csd00002741bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002741bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002732bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002731bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002722bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002721bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002712bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002711bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002702bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002701bc*sc*i*
depends:        cfg80211,libipw,lib80211
intree:         Y
vermagic:       3.14.15-porteus SMP preempt mod_unload 486 
parm:           disable:manually disable the radio (default 0 [radio on]) (int)
parm:           associate:auto associate when scanning (default off) (int)
parm:           auto_create:auto create adhoc network (default on) (int)
parm:           led:enable led control on some systems (default 1 on) (int)
parm:           debug:debug output mask (int)
parm:           channel:channel to limit associate to (default 0 [ANY]) (int)
parm:           rtap_iface:create the rtap interface (1 - create, default 0) (int)
parm:           mode:network mode (0=BSS,1=IBSS,2=Monitor) (int)
parm:           bt_coexist:enable bluetooth coexistence (default off) (int)
parm:           hwcrypto:enable hardware crypto (default off) (int)
parm:           cmdlog:allocate a ring buffer for logging firmware commands (int)
parm:           roaming:enable roaming support (default on) (int)
parm:           antenna:select antenna 1=Main, 3=Aux, default 0 [both], 2=slow_diversity (choose the one with lower background noise) (int)
root@porteus:/home/guest# 

Porteus 3.2.2

Code: Select all

guest@porteus:/mnt/sda3/porteus322$ lsmod | grep ipw
ipw2200                97360  0
libipw                 15428  1 ipw2200
lib80211                1888  2 libipw,ipw2200
cfg80211              118972  3 wl,libipw,ipw2200
guest@porteus:/mnt/sda3/porteus322$ ./bootdev.sh
System Memory: 2016M
Boot device:   /mnt/sda3
Boot device format: "ntfs" 
Boot folder:   /porteus3.x/
Boot mode:     ISO /dev/sda3/ISOs/Porteus-CINNAMON-v3.2.2-i586.iso
OS:       Porteus-v3.2.2
ARCH:     i586
Kernel:   Linux porteus 3.14.15-porteus
Desktop:  cinnamon.xzm  Cinnamon 3.2.2
Cmdline:  quiet from=/dev/sda3/ISOs/Porteus-CINNAMON-v3.2.2-i586.iso    extramod=/porteus40/Modules   

Porteus-Livedbg log: 
# Recognized devices:
/dev/sda1: SEC_TYPE="msdos" LABEL="DELLUTILITY" UUID="07D2-0B17" TYPE="vfat" 
/dev/sda2: LABEL="Windows" UUID="3AA0D45AA0D41E67" TYPE="ntfs" 
/dev/sda3: LABEL="Data" UUID="BCD86E64D86E1CC0" TYPE="ntfs" 
/dev/sda4: LABEL="Backups" UUID="DE400D55400D3635" TYPE="ntfs" 

# Booting device:
/mnt/isoloop

# Porteus data found in:
/mnt/isoloop/porteus

# Changes are stored in:
memory

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/isoloop/porteus/base/000-kernel.xzm
/mnt/isoloop/porteus/base/001-core.xzm
/mnt/isoloop/porteus/base/002-xorg.xzm
/mnt/isoloop/porteus/base/003-cinnamon.xzm
/mnt/sda3//porteus40/Modules/000-kernel.xzm
/mnt/sda3//porteus40/Modules/firefox-63.0.3-i686-1.xzm
/mnt/sda3//porteus40/Modules/flashplayer-plugin-24.0.0.186-i386-2alien.xzm
/mnt/sda3//porteus40/Modules/iw-4.3-i586-1.xzm

ISO=/mnt/sda3/ISOs/Porteus-CINNAMON-v3.2.2-i586.iso

Devices: 

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

Password: 
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 01)
03:01.0 CardBus bridge: Texas Instruments PCI6515 Cardbus Controller
03:01.5 Communication controller: Texas Instruments PCI6515 SmartCard Controller
03:03.0 Network controller: Intel Corporation PRO/Wireless 2915ABG [Calexico2] Network Connection (rev 05)
guest@porteus:/mnt/sda3/porteus322$ 

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

Porteus 4.0

Code: Select all

guest@porteus:/mnt/sda3/porteus40$ lsmod | grep ipw
ipw2200                97360  0
libipw                 15428  1 ipw2200
lib80211                1888  2 libipw,ipw2200
cfg80211              118972  3 wl,libipw,ipw2200

guest@porteus:/mnt/sda3/porteus40$ ./bootdev.sh
System Memory: 2016M
Boot device:   /mnt/sda3
Boot device format: "ntfs" 
Boot folder:   /porteus40/
Boot mode:     ISO /ISOs/Porteus-CINNAMON-v4.0-k4.19.113-i586.iso
OS:       Porteus-v4.0
ARCH:     i586
Kernel:   Linux porteus 3.14.15-porteus
Desktop:  cinnamon.xzm  Cinnamon 3.6.7
Cmdline:  quiet from=/ISOs/Porteus-CINNAMON-v4.0-k4.19.113-i586.iso  changes=EXIT:/porteus40/changes/porteussave.dat extramod=/porteus40/Modules volume=20 

Porteus-Livedbg log: 
# Recognized devices:
/dev/sda1: SEC_TYPE="msdos" LABEL="DELLUTILITY" UUID="07D2-0B17" TYPE="vfat" 
/dev/sda2: LABEL="Windows" UUID="3AA0D45AA0D41E67" TYPE="ntfs" 
/dev/sda3: LABEL="Data" UUID="BCD86E64D86E1CC0" TYPE="ntfs" 
/dev/sda4: LABEL="Backups" UUID="DE400D55400D3635" TYPE="ntfs" 
/mnt/sda3//porteus40/changes/porteussave.dat: UUID="1990a1b3-b91a-44c1-bb81-1344171325b1" TYPE="xfs" 

# Booting device:
/mnt/isoloop

# Porteus data found in:
/mnt/isoloop/porteus

# Changes are stored in:
memory

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/isoloop/porteus/base/000-kernel.xzm
/mnt/isoloop/porteus/base/001-core.xzm
/mnt/isoloop/porteus/base/002-xorg.xzm
/mnt/isoloop/porteus/base/003-cinnamon.xzm
/mnt/sda3//porteus40/Modules/000-kernel.xzm
/mnt/sda3//porteus40/Modules/firefox-63.0.3-i686-1.xzm
/mnt/sda3//porteus40/Modules/flashplayer-plugin-24.0.0.186-i386-2alien.xzm
/mnt/sda3//porteus40/Modules/iw-4.3-i586-1.xzm

ISO=/mnt/sda3//ISOs/Porteus-CINNAMON-v4.0-k4.19.113-i586.iso

Devices: 

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

Password: 
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 01)
03:01.0 CardBus bridge: Texas Instruments PCI6515 Cardbus Controller
03:01.5 Communication controller: Texas Instruments PCI6515 SmartCard Controller
03:03.0 Network controller: Intel Corporation PRO/Wireless 2915ABG [Calexico2] Network Connection (rev 05)

guest@porteus:/mnt/sda3/porteus40$ su
Password: 
root@porteus:/mnt/sda3/porteus40# blkid
/dev/sda1: SEC_TYPE="msdos" LABEL="DELLUTILITY" UUID="07D2-0B17" TYPE="vfat" PARTUUID="1f9a1f99-01"
/dev/sda2: LABEL="Windows" UUID="3AA0D45AA0D41E67" TYPE="ntfs" PARTUUID="1f9a1f99-02"
/dev/sda3: LABEL="Data" UUID="BCD86E64D86E1CC0" TYPE="ntfs" PARTUUID="1f9a1f99-03"
/dev/sda4: LABEL="Backups" UUID="DE400D55400D3635" TYPE="ntfs" PARTUUID="1f9a1f99-04"
/mnt/sda3/porteus40/changes/porteussave.dat: UUID="1990a1b3-b91a-44c1-bb81-1344171325b1" TYPE="xfs"
/dev/loop0: UUID="2020-03-26-17-44-16-38" LABEL="Porteus" TYPE="iso9660"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/loop8: TYPE="squashfs"
root@porteus:/mnt/sda3/porteus40# 

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# modinfo ipw2200
filename:       /lib/modules/3.14.15-porteus/kernel/drivers/net/wireless/ipw2x00/ipw2200.ko
firmware:       ipw2200-bss.fw
firmware:       ipw2200-sniffer.fw
firmware:       ipw2200-ibss.fw
license:        GPL
author:         Copyright(c) 2003-2006 Intel Corporation
version:        1.2.2kmpr
description:    Intel(R) PRO/Wireless 2200/2915 Network Driver
srcversion:     743C1D496825C286F776DCB
alias:          pci:v00008086d00004224sv*sd*bc*sc*i*
alias:          pci:v00008086d00004223sv*sd*bc*sc*i*
alias:          pci:v00008086d00004221sv*sd*bc*sc*i*
alias:          pci:v00008086d00004220sv*sd*bc*sc*i*
alias:          pci:v00008086d0000104Fsv*sd*bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002762bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002761bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002754bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002753bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002752bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002751bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002742bc*sc*i*
alias:          pci:v00008086d00001043sv0000103Csd00002741bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002741bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002732bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002731bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002722bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002721bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002712bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002711bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002702bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002701bc*sc*i*
depends:        cfg80211,libipw,lib80211
intree:         Y
vermagic:       3.14.15-porteus SMP preempt mod_unload 486 
parm:           disable:manually disable the radio (default 0 [radio on]) (int)
parm:           associate:auto associate when scanning (default off) (int)
parm:           auto_create:auto create adhoc network (default on) (int)
parm:           led:enable led control on some systems (default 1 on) (int)
parm:           debug:debug output mask (int)
parm:           channel:channel to limit associate to (default 0 [ANY]) (int)
parm:           rtap_iface:create the rtap interface (1 - create, default 0) (int)
parm:           mode:network mode (0=BSS,1=IBSS,2=Monitor) (int)
parm:           bt_coexist:enable bluetooth coexistence (default off) (int)
parm:           hwcrypto:enable hardware crypto (default off) (int)
parm:           cmdlog:allocate a ring buffer for logging firmware commands (int)
parm:           roaming:enable roaming support (default on) (int)
parm:           antenna:select antenna 1=Main, 3=Aux, default 0 [both], 2=slow_diversity (choose the one with lower background noise) (int)
root@porteus:/home/guest#

My Porteus 4.0 ISO's iwp2200 module

Code: Select all

----------------------------------------------
root@porteus:/home/guest# modinfo ipw2200
filename:       /lib/modules/4.19.113-porteus/kernel/drivers/net/wireless/intel/ipw2x00/ipw2200.ko
firmware:       ipw2200-bss.fw
firmware:       ipw2200-sniffer.fw
firmware:       ipw2200-ibss.fw
license:        GPL
author:         Copyright(c) 2003-2006 Intel Corporation
version:        1.2.2kmpr
description:    Intel(R) PRO/Wireless 2200/2915 Network Driver
srcversion:     4B64A60566C85F7B215FF3B
alias:          pci:v00008086d00004224sv*sd*bc*sc*i*
alias:          pci:v00008086d00004223sv*sd*bc*sc*i*
alias:          pci:v00008086d00004221sv*sd*bc*sc*i*
alias:          pci:v00008086d00004220sv*sd*bc*sc*i*
alias:          pci:v00008086d0000104Fsv*sd*bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002762bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002761bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002754bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002753bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002752bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002751bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002742bc*sc*i*
alias:          pci:v00008086d00001043sv0000103Csd00002741bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002741bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002732bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002731bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002722bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002721bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002712bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002711bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002702bc*sc*i*
alias:          pci:v00008086d00001043sv00008086sd00002701bc*sc*i*
depends:        cfg80211,libipw
retpoline:      Y
intree:         Y
name:           ipw2200
vermagic:       4.19.113-porteus SMP preempt mod_unload 686 
parm:           disable:manually disable the radio (default 0 [radio on]) (int)
parm:           associate:auto associate when scanning (default off) (int)
parm:           auto_create:auto create adhoc network (default on) (int)
parm:           led:enable led control on some systems (default 1 on) (int)
parm:           debug:debug output mask (int)
parm:           channel:channel to limit associate to (default 0 [ANY]) (int)
parm:           rtap_iface:create the rtap interface (1 - create, default 0) (int)
parm:           mode:network mode (0=BSS,1=IBSS,2=Monitor) (int)
parm:           bt_coexist:enable bluetooth coexistence (default off) (int)
parm:           hwcrypto:enable hardware crypto (default off) (int)
parm:           cmdlog:allocate a ring buffer for logging firmware commands (int)
parm:           roaming:enable roaming support (default on) (int)
parm:           antenna:select antenna 1=Main, 3=Aux, default 0 [both], 2=slow_diversity (choose the one with lower background noise) (int)
root@porteus:/home/guest# 

With the 3.0.1 vmlinux & 001-kernel modules Porteus 3.2.2 and 4.0 each saw the wifi system and the connections available and attempts to connect to the home router resulted in repeated signon windows, the same as before.

FWIW While the 3.0.1 system has wifi access and I can use Google email on it I can't access the Porteus forum on it, with or without the "s" attached to http. So Terminal screens have to be saved then emailed to me so I can use them on my x86_64 system which can access the forum. I'm also not sure if the new Google rules that go into effect tomorrow will still work on the old Dell which will slow my testing results getting transfered.

[donald]

Ed
These outputs are confusing..
Example:
Why do you load 000-kernel.xzm (and others) from /porteus40/Modules when booting 3.2.2..?

browser issue:
Have you tried a version that is meant to work with the Porteus version you are actually booting?
e.g.
Pale Moon
or at "dl.porteus.org"

so 3.0.1 work, what about 3.1?

have you already prepared a usb thumb drive as suggested above?

[Ed_P]

Ed
These outputs are confusing..
Example:
Why do you load 000-kernel.xzm (and others) from /porteus40/Modules when booting 3.2.2..?

Ok, I can see why that could be confusing. I copied the 3.0.1's vmlinuz and 000-kernel files to the porteus40 folders and since they are on the same drive as the porteus322 folder I thought sharing the same files 3.0.1 files from the same folder would avoid the possibility of the ones being used were for 322 were different.

browser issue:
Have you tried a version that is meant to work with the Porteus version you are actually booting?
e.g.
Pale Moon
or at "dl.porteus.org"

Yes, mozilla-firefox-38.1.1esr-i486-1_slack14.1.xzm and it doesn't access the porteus forum either.

so 3.0.1 work, what about 3.1?

Just as obsolete as 3.0.1.

have you already prepared a usb thumb drive as suggested above?

No need, I got the grub4dos boot kernel override to work booting the ISO file.

At this point it has been proven that the 3.0.1 vmlinuz and 000-kernel files are not the fix to getting 3.2.2 or 4.0 to signon to the wifi connections. Any other suggestions?

[jssouza]

At this point it has been proven that the 3.0.1 vmlinuz and 000-kernel files are not the fix to getting 3.2.2 or 4.0 to signon to the wifi connections.

Not so sure, that be the case. The initrd loads the extramods much later in the boot process. By then the original kernel and its drivers would have been already loaded. Why would the boot process reload the drivers after finding another 000-kernel in extramod?

[Ed_P]

Well the boot process reloads 001-003 modules in extramods= folders over the top of modules already loaded so no reason to think it doesn't do the same with the 000 one. This feature has allowed me to test many mods to the ISO files without having to rebuild the ISOs over the years. And the modinfo outputs confirm what's been loaded in each case.

[jssouza]

There's a difference between what is over-written (overlayed) on the aufs mounts vs what has been already loaded onto the ram. For example, if you replace the kernel or the initrd on your file system, it does not automatically replace the running kernel, or the initrd that have been already loaded onto the ram.
What modinfo does is it gives the info of the module stored in your file system. That is why the output is a path to a file - not the driver that has been loaded.

Say you have an application (text editor) open. Assuming it is v1.0. Keeping the text editor still open, if you upgrade the text editor package to v1.1 (installpkg, activate a new module, whatever). Would the open text editor show version 1.1 or still v1.0 if you now go to its About? Shouldn't you need to close it and reopen?

Yes, driver was reloaded. Firmware was loaded, but what if some other drivers dependent on ipw2200 also need to reloaded?

lib80211 1888 2 libipw,ipw2200
cfg80211 118972 3 wl,libipw,ipw2200

Best bet would be for the kernel to load all these just once in the proper sequence wouldn't it?

So not guaranteeing it will work, but just saying that remastering the iso, or installing the 4.0 on a USB and replacing vmlinuz and 000-kernel on it with the 3.0.1 and then boot the USB, without the extramod method has a better chance, that's all.

[Ed_P]

I copied the 001-003 files from Porteus 4.0 to the 3.0.1 Modules folder, so the initrd and kernel files are not overlaid by newer files when booting. Unfortunately it didn't boot. I removed the 003 file and it still wouldn't boot. Both hung with a "/etc/rc.d/rc.S: line 59: /etc/profile.d/porteus.sh: No such file or directory".

Added in 12 hours 35 minutes 8 seconds:
Well, someplace along the line I thought someone suggested using a different Linux system so I tried slax-6.1.3. Wow!! The similarities with Porteus were quite a surprise for me. And like the other test systems it doesn't see the wifi either.

Added in 22 hours 57 minutes 21 seconds:
So I tried a different version of slax and it works!! I am posting this from it. And it has cheatcodes just like Porteus so I can save changes. Thank you donald for the suggestion.

[Ed_P]

No, I haven't given up on Porteus.

So I tried donald's ipw2200-fw-3.1-fw-1.txz suggestion described here with my Porteus-CINNAMON-v4.0-k4*.iso and a Porteus-CINNAMON-v4.0-i586.iso both as a xzm module and with the .fw modules added to the /lib/firmware folder and rebooted. None of my attempts worked.

I then tried the ipw2200 xzm module with a Porteus-LXQT-v4.0-i586.iso and I was able to connect to the Internet!!

I'm just not a fan of the LXQT DE. So I tried the ipw2200 xzm module with the Porteus-LXDE-v4.0-i586.iso and it failed with the repeated logon attempts. I didn't try the /lib/firmware folder approach because I'm not a fan of the LXDE DE either.

Added in 1 day 17 hours 18 minutes 54 seconds:
Absolutely amazing. I was going to write that the system works only to find when I returned from eating it doesn't connect again.

What I've done;

Booting LXQT iso - Porteus-LXQT-v4.0-i586.iso
ipw2200-fw-3.1-fw-1.xzm in the Modules folder
changes=EXIT active

System boots, able to connect to the Internet.

But not with the Auto connect to the Internet, saved from the boot of the Porteus-CINNAMON-v4.0-i586.iso file.
So I delete the Auto boot entry.

I reboot and I reconnect.

I put a 4.0 003-cinnamon.xzm in the Modules folder.
I reboot.
I have a desktop I prefer on top of a system that works
AND I AM CONNECTED to the Internet.

I leave to eat, close the lid, return, the connection tries to reconnect and I'm back in the password loop problem again. Apparently the network connection code Cinnamon uses is missing something.

I disabled the 003-Cinnamon module, reboot and I am online again with the LXQT DE.

[donald]

So if you restart and the hardware is reinitialized, the system can connect.
Can you now disconnect / reconnect?

--> I ...close the lid <--
What does it do? shutdown or suspend / hibernation?
Waking from suspend / hibernation may not initialize correctly.

--> changes=EXIT active <--
Does this save changes when the system uses suspend / hibernation?

Try without the EXIT cheatcode (just a test)
(or set to shutdown when closing the lid)

[Ed_P]

Hello donald.

Yes I can disconnect and reconnect. It takes 2 or 3 tries but it does work.

As for closing the lid it was config'ed to do Nothing but when opening it, when the notebook is plugged in, the system is dead; blank screen, no response from the keyboard and pushing the power button to activate it immediately shuts it down.

With the changes=EXIT option changes are only saved when the system is shutdown.

The notebook will boot to a default config which doesn't use the changes=EXIT cheatcode and the porteussave.dat file will be loaded as a module, so the changes will be there but the system won't change. And setting the lid close option to shutdown seems like a good approach.

Added in 11 hours 4 minutes 17 seconds:
And after I posted that the situation changed. I connect, the network symbol changes to indicate I'm connected, then 20-40 seconds later a message appears at the bottom of the screen saying I'm connected, and the network symbol at the top changes to no connection. And I am unable to connect to the 'net with Firefox or the Browser Update app.



Added in 2 hours 6 minutes 55 seconds:
Absolutely amazing.

So last night I changed the Lid options to Shutdown if on battery and to Hibernate if on ac power. I just opened the lid and the wifi network connected and I am posting this on the notebook.



Added in 10 hours 57 minutes 51 seconds:
So I booted to Windows thinking maybe defragging the drive with my Porteus ISO and run files might help. Surprise, surprise, Windows is connected but the connection shows a warning about being unstable or something!! Windows is the system that was installed on this machine when it was built so pretty sure the connection problem isn't driver related.

I rebooted the router and things have been connecting just fine on the notebook every since. Windows and Porteus. Plan on giving the notebook to my daughter for her kids this weekend.