Unable to create wireless device

Phishfry said:
So somehow you need to get a temporary connection to bring the machine up to date with patches and the upgrade. Do you have any other method like USB-Ethernet dongle?


The first thing to look at is pciconf -lv. Near the bottom should be some sort of information about an Intel wireless adapter. Model number is important in this case.
That will direct you to which driver on FreeBSD-15.0-RELEASE you should be loading. It may have changed from the previous version.
www.freebsd.org

FreeBSD 15.0 Hardware Notes

FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.
www.freebsd.org www.freebsd.org
Click to expand...
Hi Phishfry

The model number of my wireless adapter is known to me, it’s Intel Dual Band Wireless AC 7265, iwm driver supports it.

Somehow this time wireless interface is not created. BTW not sure whether it’s related or not facing issue with su command as well “bad system call” is the output therein.

Thanks
rraj
 
rraj said:
BTW not sure whether it’s related or not facing issue with su command as well “bad system call” is the output therein.
Click to expand...
What does freebsd-version -urk output? Because this sounds like you're running a new userland on an old kernel.
 
In /etc/rc.conf, kern_securelevel_enable and kern_securelevel, if you have any remove them.
 
Then there's no reason why pciconf(8) would fail with an "Operation not permitted" error.

Starting to grasp at straws here, but what's the output of ls -l /dev/pci
 
SirDice said:
Then there's no reason why pciconf(8) would fail with an "Operation not permitted" error.

Starting to grasp at straws here, but what's the output of ls -l /dev/pci
Click to expand...
Hi SirDice

The output is:
Code: 
crw-r—r— 1 root wheel 0x16 Jan 27 15:22 /dev/pci
.

Facing issues with su - also, outputs “ bad system call “ & fails.

Thanks
rraj
 
Then I'm lost. Your system is seriously borked. If it was my system I'd wipe the whole lot and do a fresh, clean, install.
 
Can you display your /boot/loader.conf.

Maybe you are loading a firmware that is distraught....

I would also remove all /etc/rc.conf settings for wireless to see if you can get pciconf to show status.

I feel you may have a wrong wireless settings somewhere.
 
rraj said:
Probably did the update rollback as it did not go correctly!
Click to expand...
Something got messed up with the rollback and I fear you now have a mix of 14.3 and 15.0 executables and libraries (which certainly would explain the weird errors and "bad system call" issues).

Phishfry said:
I would also remove all /etc/rc.conf settings for wireless to see if you can get pciconf to show status.
Click to expand...
pciconf(8) doesn't depend on any driver. It queries the hardware directly through ACPI.
 
Phishfry said:
Can you display your /boot/loader.conf.

Maybe you are loading a firmware that is distraught....

I would also remove all /etc/rc.conf settings for wireless to see if you can get pciconf to show status.

I feel you may have a wrong wireless settings somewhere.
Click to expand...
Hi Phishfry

loader.conf contains iwm related entries from past.

I believe rc.conf does not contain any setting related to wireless.

Thanks
rraj
 
As SirDice advises this system sounds really fouled. Version mismatches probably have the system beyond repair.
I have not seen a machine that cannot run pciconf in a long time. I did it once doing a major version upgrade. It was a learning experience.

Without internet your only resource fix is a source tree based one. Do you have the source tree installed?

Wouldn't it be easier to copy your settings files to a USB stick and start over?

Trying to run a source based upgrade on a fouled system could be a huge waste of time.

rraj said:
loader.conf contains iwm related entries from past.
Click to expand...
I would have the system torn to parade rest. Anything else is fodder.
 
Phishfry said:
As SirDice advises this system sounds really fouled. Version mismatches probably have the system beyond repair.
I have not seen a machine that cannot run pciconf in a long time. I did it once doing a major version upgrade. It was a learning experience.

Without internet your only resource fix is a source tree based one. Do you have the source tree installed?

Wouldn't it be easier to copy your settings files to a USB stick and start over?

Trying to run a source based upgrade on a fouled system could be a huge waste of time.


I would have the system torn to parade rest. Anything else is fodder.
Click to expand...
Hi Phishfry

I think I have the source tree installed. How to proceed further? Can you list the steps?

Thanks
rraj
 
Step One: Copy all your current settings file to USB stick.

You should have started here from the manual:
freebsd-update IDS >> outfile.ids
Looking at your system state after a failed upgrade.
docs.freebsd.org

Chapter 26. Updating and Upgrading FreeBSD

Information about how to keep a FreeBSD system up-to-date with freebsd-update or Git, how to rebuild and reinstall the entire base system, etc
docs.freebsd.org docs.freebsd.org
For this you will need internet.

After review and remediation move to Ch. 26.6 for source based upgrade.
 
You must log in or register to reply here.
Back
Top