Old Dell Latitude D610 Wireless missing

[beny]

hi, Ed_P this is my kernel config,as you can see the intel kernel module is a module so you have to load it with modprobe,you have also the firmware when you load the module kernel the device is ready to go.. maybe, the lsmod show if you have it,i think you have to have the whole kernel,but you can try if module is loaded withtout it.

/lib/modules/5.4.6-zen/build/drivers/net/wireless/intel/ipw2x00/

CONFIG_WLAN_VENDOR_INTEL=y
CONFIG_IPW2100=m
CONFIG_IPW2100_MONITOR=y
# CONFIG_IPW2100_DEBUG is not set
CONFIG_IPW2200=m
CONFIG_IPW2200_MONITOR=y
CONFIG_IPW2200_RADIOTAP=y
CONFIG_IPW2200_PROMISCUOUS=y
CONFIG_IPW2200_QOS=y
# CONFIG_IPW2200_DEBUG is not set

[Ed_P]

beny ipw2200 is present in two systems that see wifi connections. But no drivers folders.

Porteus 3.2.2

Code: Select all

guest@porteus:~$ lsmod | grep ipw
ipw2200                93972  0
libipw                 15487  1 ipw2200
lib80211                1764  1 libipw
cfg80211              139900  3 wl,ipw2200,libipw
firmware_class          4112  4 ipw2200,pcmcia,tg3,i915
guest@porteus:~$ ls /lib/modules/4.9.0-porteus
build@             modules.builtin      modules.devname  modules.symbols.bin
kernel/            modules.builtin.bin  modules.order    source@
modules.alias      modules.dep          modules.softdep
modules.alias.bin  modules.dep.bin      modules.symbols
guest@porteus:~$ ls /lib/modules/4.9.0-porteus/build
/lib/modules/4.9.0-porteus/build@
guest@porteus:~$ ls /lib/modules/4.9.0-porteus/build/drivers
/bin/ls: cannot access '/lib/modules/4.9.0-porteus/build/drivers': No such file or directory
guest@porteus:~$ su
Password: 
root@porteus:/home/guest# ls /lib/modules/4.9.0-porteus/build/drivers
/bin/ls: cannot access '/lib/modules/4.9.0-porteus/build/drivers': No such file or directory
root@porteus:/home/guest# 

Porteus 4.0

Code: Select all

guest@porteus:~$ lsmod | grep ipw
ipw2200               102400  0
libipw                 24576  1 ipw2200
lib80211               12288  1 libipw
cfg80211              176128  2 ipw2200,libipw
guest@porteus:~$ ls /lib/modules/4.19.113-porteus
build@             modules.builtin.alias.bin  modules.order
kernel/            modules.builtin.bin        modules.softdep
modules.alias      modules.dep                modules.symbols
modules.alias.bin  modules.dep.bin            modules.symbols.bin
modules.builtin    modules.devname            source@
guest@porteus:~$ ls /lib/modules/4.19.113-porteus/build
/lib/modules/4.19.113-porteus/build@
guest@porteus:~$ ls /lib/modules/4.19.113-porteus/build/drivers
/bin/ls: cannot access '/lib/modules/4.19.113-porteus/build/drivers': No such file or directory
guest@porteus:~$ su
Password: 
root@porteus:/home/guest# ls /lib/modules/4.19.113-porteus/build/drivers
/bin/ls: cannot access '/lib/modules/4.19.113-porteus/build/drivers': No such file or directory
root@porteus:/home/guest# 

[donald]

/lib/modules/4.9.0-porteus/kernel/drivers/net/wireless/intel/ipw2x00/ipw2200.ko

[Ed_P]

Thank you donald.

Porteus 3.2.2

Code: Select all

guest@porteus:~$ ls /lib/modules/4.9.0-porteus/kernel/
arch/   crypto/   extra/  kernel/  net/    virt/
block/  drivers/  fs/     lib/     sound/
guest@porteus:~$ ls /lib/modules/4.9.0-porteus/kernel/drivers
acpi/       connector/  gpu/    md/       pci/       ptp/      thunderbolt/
ata/        cpufreq/    hid/    media/    pcmcia/    pwm/      tty/
base/       crypto/     hwmon/  mfd/      phy/       rtc/      uio/
bcma/       dma/        i2c/    misc/     platform/  scsi/     usb/
block/      extcon/     input/  mmc/      power/     ssb/      vhost/
bluetooth/  firewire/   isdn/   net/      powercap/  staging/  video/
char/       firmware/   leds/   parport/  pps/       thermal/  virtio/
guest@porteus:~$ ls /lib/modules/4.9.0-porteus/kernel/drivers/net
bonding/   geneve.ko  macsec.ko  phy/   tun.ko   virtio_net.ko  wireless/
ethernet/  gtp.ko     mdio.ko    ppp/   usb/     vmxnet3/
fjes/      irda/      mii.ko     slip/  veth.ko  wimax/
guest@porteus:~$ ls /lib/modules/4.9.0-porteus/kernel/drivers/net/wireless
admtek/  broadcom/  intersil/  ralink/    rndis_wlan.ko  ti/
ath/     cisco/     marvell/   ray_cs.ko  rsi/           wl3501_cs.ko
atmel/   intel/     mediatek/  realtek/   st/            zydas/
guest@porteus:~$ ls /lib/modules/4.9.0-porteus/kernel/drivers/net/wireless/intel/ipw2x00
ipw2100.ko  ipw2200.ko  libipw.ko
guest@porteus:~$ modprobe /lib/modules/4.9.0-porteus/kernel/drivers/net/wireless/intel/ipw2x00/ipw2200.ko
bash: modprobe: command not found
guest@porteus:~$ 

Porteus 4.0

Code: Select all

guest@porteus:~$ ls /lib/modules
4.16.3-porteus/  4.19.111-porteus/  4.19.113-porteus/
guest@porteus:~$ ls /lib/modules/4.19.113-porteus/kernel/drivers/net/wireless/intel
ipw2x00/  iwlegacy/  iwlwifi/
guest@porteus:~$ ls /lib/modules/4.19.113-porteus/kernel/drivers/net/wireless/intel/ipw2x00/
ipw2100.ko  ipw2200.ko  libipw.ko
guest@porteus:~$ modprobe /lib/modules/4.19.113-porteus/kernel/drivers/net/wireless/intel/ipw2x00/ipw2200.ko
bash: modprobe: command not found 

So where does one get modprobe?

And how is this driver effecting Porteus's not being able to sign on to a wifi network connection it shows?

[donald]

So where does one get modprobe?

You have already used this command. -- see page 1.

However,
as root

Code: Select all

modprobe -r ipw2200 && modprobe ipw2200

[beny]

and lsmod show you if this module is loaded,without module and firmware you can't do anything...

[Ed_P]

Good grief!!

Porteus 3.2.2

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# modprobe /lib/modules/4.9.0-porteus/kernel/drivers/net/wireless/intel/ipw2x00/ipw2200.ko
modprobe: FATAL: Module /lib/modules/4.9.0-porteus/kernel/drivers/net/wireless/intel/ipw2x00/ipw2200.ko not found in directory /lib/modules/4.9.0-porteus
root@porteus:/home/guest# ls       /lib/modules/4.9.0-porteus/kernel/drivers/net/wireless/intel/ipw2x00/
ipw2100.ko  ipw2200.ko  libipw.ko
root@porteus:/home/guest# 

guest@porteus:~$ lsmod | grep ipw
ipw2200                93972  0
libipw                 15487  1 ipw2200
lib80211                1764  1 libipw
cfg80211              139900  3 wl,ipw2200,libipw
firmware_class          4112  4 ipw2200,pcmcia,tg3,i915

Porteus 4.0

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# modprobe /lib/modules/4.19.113-porteus/kernel/drivers/net/wireless/intel/ipw2x00/ipw2200.ko
modprobe: FATAL: Module /lib/modules/4.19.113-porteus/kernel/drivers/net/wireless/intel/ipw2x00/ipw2200.ko not found in directory /lib/modules/4.19.113-porteus
root@porteus:/home/guest# ls      /lib/modules/4.19.113-porteus/kernel/drivers/net/wireless/intel/ipw2x00/
ipw2100.ko  ipw2200.ko  libipw.ko
root@porteus:/home/guest# 

guest@porteus:~$ lsmod | grep ipw
ipw2200               102400  0
libipw                 24576  1 ipw2200
lib80211               12288  1 libipw
cfg80211              176128  2 ipw2200,libipw

[donald]

Ed, use

Code: Select all

root@porteus:/home/guest# modprobe -r ipw2200 && modprobe ipw2200

(without any path) while 3.2.2 is running.
This should un-/reload the driver.It may or may not help.
[There will be no output > when done check the wifi.]

I see 4.19.113 in the port-4 output, where does this come from?
Please use (try) an unmodified/stock porteus-4 -- 4.16.3 i think.

And put the firmware files into /lib/firmware/ if they are missing.
ipw2200-bss.fw
ipw2200-ibss.fw
ipw2200-sniffer.fw
When you have the firmware files in place, execute the modprobe command as described above
and check the wifi.

[Ed_P]

Thank you Donald.

No change in connecting to the selected wifi connection in 3.2.2 or 4.0 after executing the modprobe commands. The network sees the wireless connections and repeatedly asks for authorization when the home one is selected. The password is present and correct.

4.0 is an iso made for me by neko and /lib/firmware includes the 3 ipw2200 files you said to check for.

[jssouza]

Ed, use

Code: Select all

root@porteus:/home/guest# modprobe -r ipw2200 && modprobe ipw2200

(without any path) while 3.2.2 is running.
This should un-/reload the driver.It may or may not help.
[There will be no output > when done check the wifi.]

I see 4.19.113 in the port-4 output, where does this come from?
Please use (try) an unmodified/stock porteus-4 -- 4.16.3 i think.

And put the firmware files into /lib/firmware/ if they are missing.
ipw2200-bss.fw
ipw2200-ibss.fw
ipw2200-sniffer.fw
When you have the firmware files in place, execute the modprobe command as described above
and check the wifi.

Small problem here, if ipw2200 is not loaded the first command fails and hence the second command of actual modprobe wont work. The original suggestion had a ';' in between.

Anyway, another option: Replace the vmlinuz and 000-kernel of the 4.0 system with the 3.0.1 ones.

[beny]

Ed_P would you please show the ip link result and you have to use iw that is a low level software first or use wicd that scan for wifi automatically,if you have a password prompt what software use for...

[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.

[Ed_P]

The original suggestion had a ';' in between.

Anyway, another option: Replace the vmlinuz and 000-kernel of the 4.0 system with the 3.0.1 ones.

Thank you jssouza. I only saw the suggestion with the && between the commands. As for vmlinuz and the 000-kernel from 3.0.1 I'm not sure the connection problem is in them. I think it's in the Porteus Network code, where ever that may be, not responding to the ipw's code properly.

Ed_P would you please show the ip link result and you have to use iw that is a low level software first or use wicd that scan for wifi automatically,if you have a password prompt what software use for...

I would love to get iw to work beny but the last time I tried iw it didn't work.

Code: Select all

root@porteus:/home/guest# iw dev 
phy#0
	Interface eth1
		ifindex 3
		wdev 0x1
		addr e6:b3:08:d1:62:23
		type managed
root@porteus:/home/guest# iw dev interface scan
command failed: No such device (-19)
root@porteus:/home/guest# iw dev interface 
Usage:	iw [options] command
Options:
	--debug		enable netlink debugging
	--version	show version (4.3)
.....

root@porteus:/home/guest# iw dev interface connect "SlickMoose"
command failed: No such device (-19)

Are you saying

Code: Select all

iw dev interface connect "192.168.200.130"

would work better?

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

I agree.

[jssouza]

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

another option: Replace the vmlinuz and 000-kernel of the 4.0 system with the 3.0.1 ones.

As for vmlinuz and the 000-kernel from 3.0.1 I'm not sure the connection problem is in them.

Something about having tried and lost instead of not trying at all comes to mind

[Ed_P]

Something about having tried and lost instead of not trying at all comes to mind

True enough, true enough.

Unfortunately overriding vmlinuz doesn't work well with grub4dos.

Code: Select all

set ISO4=Porteus-CINNAMON-v4.0-k4.19.113-i586.iso


title Porteus 4.0   changes=EXIT\n 330MB\n %ISO4%\n Run 'blkid' as root to find all info about drives and partitions.
# http://www.911cd.net/forums/index.php?s=&showtopic=25876&view=findpost&p=176070
find --set-root /ISOs/%ISO4%
map --heads=0 --sectors-per-track=0  /ISOs/%ISO4% (0xff) 
map --hook
root (0xff)
#kernel (0xff)/boot/syslinux/vmlinuz
kernel /mnt/sda3/porteus40/vmlinuz from=/ISOs/%ISO4%  changes=EXIT:/porteus40/changes/porteussave.dat extramod=/porteus40/Modules volume=20 
initrd (0xff)/boot/syslinux/initrd.xz

No matter how I code it it comes back as Not Found. The 000-kernel module I can put in the Modules folder. But if you think it's worth trying...