Here is my lspci:
00:00.0 Host bridge [0600]: NVIDIA Corporation MCP89 HOST Bridge [10de:0d60] 
(rev a1)
00:00.1 RAM memory [0500]: NVIDIA Corporation MCP89 Memory Controller 
[10de:0d68] (rev a1)
00:01.0 RAM memory [0500]: NVIDIA Corporation Device [10de:0d6d] (rev a1)
00:01.1 RAM memory [0500]: NVIDIA Corporation Device [10de:0d6e] (rev a1)
00:01.2 RAM memory [0500]: NVIDIA Corporation Device [10de:0d6f] (rev a1)
00:01.3 RAM memory [0500]: NVIDIA Corporation Device [10de:0d70] (rev a1)
00:02.0 RAM memory [0500]: NVIDIA Corporation Device [10de:0d71] (rev a1)
00:02.1 RAM memory [0500]: NVIDIA Corporation Device [10de:0d72] (rev a1)
00:03.0 ISA bridge [0601]: NVIDIA Corporation MCP89 LPC Bridge [10de:0d80] (rev 
a2)
00:03.1 RAM memory [0500]: NVIDIA Corporation MCP89 Memory Controller 
[10de:0d7b] (rev a1)
00:03.2 SMBus [0c05]: NVIDIA Corporation MCP89 SMBus [10de:0d79] (rev a1)
00:03.3 RAM memory [0500]: NVIDIA Corporation MCP89 Memory Controller 
[10de:0d69] (rev a1)
00:03.4 Co-processor [0b40]: NVIDIA Corporation MCP89 Co-Processor [10de:0d7a] 
(rev a1)
00:04.0 USB controller [0c03]: NVIDIA Corporation MCP89 OHCI USB 1.1 Controller 
[10de:0d9c] (rev a1)
00:04.1 USB controller [0c03]: NVIDIA Corporation MCP89 EHCI USB 2.0 Controller 
[10de:0d9d] (rev a2)
00:06.0 USB controller [0c03]: NVIDIA Corporation MCP89 OHCI USB 1.1 Controller 
[10de:0d9c] (rev a1)
00:06.1 USB controller [0c03]: NVIDIA Corporation MCP89 EHCI USB 2.0 Controller 
[10de:0d9d] (rev a2)
00:08.0 Audio device [0403]: NVIDIA Corporation MCP89 High Definition Audio 
[10de:0d94] (rev a2)
00:0a.0 SATA controller [0106]: NVIDIA Corporation MCP89 SATA Controller (AHCI 
mode) [10de:0d88] (rev a2)
00:0b.0 RAM memory [0500]: NVIDIA Corporation Device [10de:0d75] (rev a1)
00:0e.0 PCI bridge [0604]: NVIDIA Corporation Device [10de:0d9a] (rev a1)
00:15.0 PCI bridge [0604]: NVIDIA Corporation Device [10de:0d9b] (rev a1)
00:16.0 PCI bridge [0604]: NVIDIA Corporation Device [10de:0d9b] (rev a1)
00:17.0 PCI bridge [0604]: NVIDIA Corporation MCP89 PCI Express Bridge 
[10de:0d76] (rev a1)
01:00.0 FireWire (IEEE 1394) [0c00]: LSI Corporation FW643 [TrueFire] PCIe 
1394b Controller [11c1:5901] (rev 08)
02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4322 
802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)
03:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5764M Gigabit Ethernet PCIe [14e4:1684] (rev 10)
04:00.0 VGA compatible controller [0300]: NVIDIA Corporation MCP89 [GeForce 
320M] [10de:08a0] (rev a2)

Additionally, my dmesg is available on anonfiles. I'm pretty sure I sent you a 
link before as well but it may be down by now. 

https://anonfiles.com/Y2Ad37n8z6

> As modern wireless is highly dependent on systemd, are you sure that 
> everything is setup correctly?
Ill try debian in the next few days.


On April 25, 2023 8:54:59 PM UTC, Larry Finger <larry.fin...@lwfinger.net> 
wrote:
>On 4/25/23 12:22, Pogprogrammer wrote:
>> Hello,
>> I contacted this forum earlier and I installed devuan. Initially it worked 
>> on kernel 5.10 when I installed b43-installer and just set it up. However 
>> after reinstalling due to unrelated inconveiniences, it is unable to scan 
>> for wifi networks. Dmesg contains no relevant information except DMA RX 
>> timeout and another timeout waiting for bitmask 01800000 on register 0F90 to 
>> clear. The logs then show that the driver was loaded with a feature called 
>> PNLS, qnd it loaded version 784.2.
>> 
>> Under uname it is debian 5.10.162-1 on 5.10.0-21-amd64 kernel.
>
>The list b43-dev used to be a good place to ask questions like this, but 
>linux-wirel...@vger.kernel.org is better now. I have sent this reply to that 
>list.
>
>I understand that devuan is Debian without systemd. As modern wireless is 
>highly dependent on systemd, are you sure that everything is setup correctly?
>
>The output about 783.2 implies that the firmware was loaded, but those error 
>messages are of concern.
>
>Please run the command 'lspci -nn' and post the output. That will tell us what 
>device you actually have,
>
>You say that dmesg has no relevant information, but I would like to see for 
>myself. Please run the command 'dmesg > dmesg.txt', post dmesg.txt to some 
>site like https://pastebin.com/, and post the link to the file in the next 
>E-mail here.
>
>Larry
>
>
>
>

_______________________________________________
b43-dev mailing list
b43-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/b43-dev

Reply via email to