Code: Select all
# modprobe wl
modprobe: FATAL: Module wl not found in directory /lib/modules/4.19.23
Code: Select all
# modprobe wl
modprobe: FATAL: Module wl not found in directory /lib/modules/4.19.23
Code: Select all
lspci -nn | grep Network
Code: Select all
dmesg | grep 'firmware'
HeheSemme wrote: Do I know you?
Kernel drivers are SPECIFIC. Skami I'm sure simply forgot to include the 64 bit after amd.https://archive.org/download/Puppy_Linu ... [b]k4.1.11[/b]_amd64-5.pet
Saturdays was Slacko. Yesterday, Bionic.
==Should I just remove the reference to broadcom_sta in /root/.packages/user-installed-packages?
I realize that issue is on me, as I used the cli, however a new user makes certain assumptions, based on past experience. For me, using a netbook is a bit fiddly as is, so I try to use the cli and an app launcher as much as possible so as not having to rotate through the app menu constantly.Semme wrote:You mean this original?Kernel drivers are SPECIFIC. Skami I'm sure simply forgot to include the 64 bit after amd.https://archive.org/download/Puppy_Linu ... [b]k4.1.11[/b]_amd64-5.petSaturdays was Slacko. Yesterday, Bionic.
Nowhere did I suggest using a cmdline.
That said, what's the output here:Winston Wolf: If I’m curt with you it’s because time is a factor. I think fast, I talk fast, and I need you to guys to act fast if you wanna get out of this. So pretty please, with sugar on top, install the bleepin' driver.
Code: Select all
lspci -nn | grep Network
Semme wrote:Hallelujah!
Wow.Semme wrote:I lost my reply. Forum soft BLOWS!
I have two, but I seem to be having difficulty getting one to load as default at boot. The profile has to be activated manually every boot and auto dhcp initiated manually.Semme wrote:Anyway, yeah -- gotta make a profile before using one.
The connection itself seems to be OK when I get it running, although the local internet really blows these days, so it is sometimes hard to tell...Semme wrote:In the event you find it unreliable, grab the 4.6 pkg here and follow the instructions.