Dhcpclient folder empty

Help with setting up network cards, including WiFi cards.
Hagg
Posts: 17
Joined: Sat Mar 05, 2022 6:26 pm

Re: Dhcpclient folder empty

Post by Hagg »

RodMyers wrote: Sat Mar 12, 2022 6:22 am it is, and you probably overlooked that line, like I did numerous times.

Start at the top of the page, and read each line, and sentence carefully.
Okay, this is maddening. I just had my wife and our neighbor look at the problem phrase you gave me:

kld_list="linux linux64 cuse fusefs /boot/modules/i915kms.ko if_iwlwifi"

and try to find it in this thread:

https://forums.ghostbsd.org/viewtopic.php?f=64&t=2315

None of us can find it. Not even some elements of it, such as "linux64 fusefs."

So, obviously we're all looking at the wrong thread. So, I did a search for that phrase in the GhostBSD forum search field up there on the right corner of this page and it is nowhere other than here where you and I have posted it. Something is wrong... I know I am not being pranked.. so l am in the crazy position of having to ask you for a link to the page where that phrase "kld_list="linux linux64 cuse fusefs /boot/modules/i915kms.ko if_iwlwifi"" occurs. Please.. I know this whole thing must be a misunderstanding of some sort.. but I can't find that which you tell me is where you made a correction to solve this issue of not being able to get networking/wifi to work on our machines.

???

*Hagg*
RodMyers
Posts: 67
Joined: Sat Nov 27, 2021 8:16 pm

Re: Dhcpclient folder empty

Post by RodMyers »

A sysctl net.wlan.devices should now list iwlwifi0.

Do not load it from /boot/loader.conf but form kld_list in /etc/rc.conf .
CODE: SELECT ALL

sudo sysrc kld_list+="if_iwlwifi"
Hagg
Posts: 17
Joined: Sat Mar 05, 2022 6:26 pm

Re: Dhcpclient folder empty

Post by Hagg »

Progress! But not quite working.

Now I still have "network card not enabled," but I do see the list of available networks including mine when I click the network manager icon in the tray. However when I click my network nothing happens so I cannot enter password and join. On "service netif start" I see "warning wpa_supplicant.conf is unreadable." So, I see you had to set that up, how do I go about doing that as there is no wpa_supplicant.conf file in the /etc folder.

By the way you have been amazing with your help and patience! Thank you very much, I think I am just inches from resolving this network issue now.
RodMyers
Posts: 67
Joined: Sat Nov 27, 2021 8:16 pm

Re: Dhcpclient folder empty

Post by RodMyers »

what do you have in the /etc/wpa_supplicant? didn't fully read your message

should be something like;

network={
ssid="network name"
psk="passphrase"
id_str="0"
priority=1
}
Hagg
Posts: 17
Joined: Sat Mar 05, 2022 6:26 pm

Re: Dhcpclient folder empty

Post by Hagg »

RodMyers wrote: Sun Mar 13, 2022 2:35 pm what do you have in the /etc/wpa_supplicant? didn't fully read your message

should be something like;

network={
ssid="network name"
psk="passphrase"
id_str="0"
priority=1
}
Actually it was empty as I just created the wpa_supplicant folder and created a wpa_supplicant.conf file inside. I’ll try inserting your example with my network name and pass phrase.
Hagg
Posts: 17
Joined: Sat Mar 05, 2022 6:26 pm

Re: Dhcpclient folder empty

Post by Hagg »

Okay, when running sudo service netif restart I get a long string of info but it all starts with "warning /etc/wpa_supplicant.conf is not readable" and another warning "failed precedent routine for wpa_supplicant"
RodMyers
Posts: 67
Joined: Sat Nov 27, 2021 8:16 pm

Re: Dhcpclient folder empty

Post by RodMyers »

that is my wpa_spplicant, minus my info, straight from the ghostbsd machine

web search "create wpa_supplicant" for tips
Hagg
Posts: 17
Joined: Sat Mar 05, 2022 6:26 pm

Re: Dhcpclient folder empty

Post by Hagg »

RodMyers wrote: Mon Mar 14, 2022 7:02 am that is my wpa_spplicant, minus my info, straight from the ghostbsd machine

web search "create wpa_supplicant" for tips
Yes, I know. As I mentioned in the post following that I inserted my info.. but still no joy as it brought up the warning messages. I am stuck again.

I followed the instructions at the BSD wpa_supplicant wiki page but cannot get any farther than I have.

I wonder if there is going to be a release of a GhostBSD iso that has this wpa supplicant and driver issue taken care of.
Hagg
Posts: 17
Joined: Sat Mar 05, 2022 6:26 pm

Re: Dhcpclient folder empty

Post by Hagg »

I just had an tech at the local community college read and follow the directions given here for getting wifi going on my Acer laptop. It would not go and his take is that it is hardware specific, although the directions are a bit muddled and with a few contradictory explanatory messages in between he did it all several times.

I have to forget about it and check back after some time as I've noticed that BSD is quite behind with regard to hardware support and my favorite GhostBSD is no exception. Again I want to thank you (and eric) for trying. I'll always have GhostBSD to check on now and then but until thankfully I have MX Linux and Windows to do work with no issues.

Thanks again!
wb7odyfred
Posts: 203
Joined: Sat Nov 12, 2016 5:44 pm

Re: AX201 wifi chip

Post by wb7odyfred »

http://bsd-hardware.info/?id=pci:8086-a0f0-1a56-1651
contents of kldstat
http://bsd-hardware.info/?probe=7319560506&log=kldstat
ifconfig output:
http://bsd-hardware.info/?probe=7319560506&log=ifconfig

create wlan0 interface Check for exact device driver name please.

Code: Select all

ifconfig wlan0 create wlandev iwlwifi0
contents of /etc/rc.conf file:

Code: Select all

wlans_iwlwifi0="wlan0"
ifconfig_wlan0="WPA DHCP"
Leave off 'WPA' for open network ( non encrypted)

Code: Select all

ifconfig_wlan0=" DHCP"
contents of /boot/loader.conf file:


contents of /etc/wpa_supplicant.conf file:

Code: Select all

network={
   ssid="innflux"
   key_mgmt=NONE
}
network={
	#: my NetGear box
	ssid="NETGEAR59"
	psk="my_passkey_892"
	key_mgmt=WPA-PSK
}
network={
	#: my NetGear box
	ssid="NETGEAR59"
	priority=3
	bssid=c4:04:15:7d:53:80
	key_mgmt=WPA-PSK
	proto=RSN
	psk="my_passkey_892"
}
device:

iwlwifi0@pci0:0:20:3: class=0x028000 rev=0x20 hdr=0x00 vendor=0x8086 device=0xa0f0 subvendor=0x1a56 subdevice=0x1651
vendor = 'Intel Corporation'
device = 'Wi-Fi 6 AX201'
class = network
bar [10] = type Memory, range 64, base 0x60531dc000, size 16384, enabled
cap 01[c8] = powerspec 3 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit
cap 10[40] = PCI-Express 2 root endpoint max data 128(128) FLR RO NS
max read 128
cap 11[80] = MSI-X supports 16 messages, enabled
Table in map 0x10[0x2000], PBA in map 0x10[0x3000]
ecap 0018[100] = LTR 1
ecap 000b[164] = Vendor [1] ID 0010 Rev 0 Length 20

[...] iwlwifi0: <iwlwifi> mem 0x60531dc000-0x60531dffff at device 20.3 on pci0
[...] iwlwifi0: could not load firmware image 'iwlwifi-QuZ-a0-hr-b0-70.ucode'
[...] iwlwifi0: File size way too small!
[...] iwlwifi0: could not load firmware image 'iwlwifi-QuZ-a0-hr-b0-69.ucode'
[...] iwlwifi0: File size way too small!
[...] ig4iic0: <Intel Tiger Lake-LP I2C Controller-4> at device 21.0 on pci0
[...] ig4iic0: Using MSI
[...] iicbus0: <Philips I2C bus (ACPI-hinted)> on ig4iic0
[...] iwlwifi0: successfully loaded firmware image 'iwlwifi-QuZ-a0-hr-b0-68.ucode'
[...] iwlwifi0: api flags index 2 larger than supported by driver
[...] iwlwifi0: TLV_FW_FSEQ_VERSION: FSEQ Version: XXX.XXX.XXX.XXX
[...] iwlwifi0: loaded firmware version 68.01d30b0c.0 QuZ-a0-hr-b0-68.ucode op_mode iwlmvm
[...] iwlwifi0: Detected Intel(R) Wi-Fi 6 AX203, REV=0x351
Last edited by wb7odyfred on Wed Feb 01, 2023 11:52 am, edited 2 times in total.
Post Reply