wlan0 not found

[DirectFX]

Hi.
I'm new in this community and I have decided I want to give a Puppy Linux a try.
I have a problem connecting to wifi. It looks wifi adapter is not recognised since I only got to choose between eth and windows in "interfaces" tab.
I tried to load different modules (Network wizard -> load modules), also tried "auto-probe" in "more" tab with no luck.

I'm booting FossaPup from USB
Wireles device: MediaTek Wi-Fi 6 MT7921 (ifconfig gave: 14c3:7961)

I hope gave enough informations and I really hope someone can help me.

[rcrsn51]

The mt7921u driver came into the mainstream Linux kernel around k5.12, so you would need a much newer Puppy than Fossa. Even then, your adapter might not be detected.

You might be better off getting a cheap N-mode adapter.

Just to be clear, is your adapter internal or USB?

[mikeslr]

There may be other solutions. But the post here, https://askubuntu.com/questions/1357135 ... -card-7961 suggests that the 'stock' kernel --the one included in fossapup64's ISO-- may be too old; that you'll need the wifi-driver which, under Linux, only became available with kernel 5.12. That and any later kernel should do.

Fortunately, it's easy to change a Puppy's kernel. I'll explain how in a minute. But may I suggest that you try either (or both -- each only needs its own folder) S15Pup64, https://www.forum.puppylinux.com/viewto ... 125#p74125 or F96_4-radky5, https://www.smokey01.com/radky/Testing/ ... radky5.iso. Both have newer kernels. S15Pup64, binary-compatible with Slackware, is now the 'Official Puppy'. F96_4-radky5 is a newer version based on Ubuntu Focal Fossa. Both have recently been extensively tested. Any 'rough edges' that may later appear 'in the wild' should prove an easy fix.

Swapping kernels is at most 4-step process which can be done from a running Puppy. (1) Obtain the new kernel; (2) if obtained as a tar.bz2, extract it; (3) rename the two components; (4) Substitute the new from the old.

(1) Obtaining the new kernel: you can either use one you already have, for example by having deployed either S15Pup64 or F96_4-radky5; or you can download a 'hugh kernel' from a link on this Section, https://www.forum.puppylinux.com/viewforum.php?f=65. Without getting into specific reasons, I'll suggest the 5.19.11 from the link here, https://www.forum.puppylinux.com/viewto ... 585#p67585.

(2) Fossapup64 has a built in application for changing kernels when using a 'hugh kernel' package. Menu>Setup>QuickPet>Click Change Kernel. Read the help file. It may eliminate most of following.

(2a) A 'hugh kernel' is packaged as a 'tar.bz2'. Right-Click and extract it. That will produce two files, one named vmlinuz-xxxx, and the other kernel-modules.sfs-xxx. The 'xxx's' are so that humans can identify which is which.

(3) Rename vmlinuz-xxx to just vmlinuz. It is the kernel, itself. The 'kernel-modules' are the drivers compiled for that kernel. You'll notice that on storage Fossapup64 has a file named zdrv_fossapup64_9.5.sfs and another named initrd.gz. Initrd loads into ram first and then looks for files bearing a specific puppy's designation. Your fossapup's designation is 'fossapup64_9.5.sfs'. For historical reasons, Puppy identifies the drivers as zdrv. So You'd rename kernel-modules.sfs-xxx to zdrv_fossapup64_9.5.sfs.

(4) Substitute the new for the old. Just drag & drop from wherever you renamed the above next to fossapup64's initrd file. That will over-write the current files. But just to be safe, before dragging & dropping, I Right-Click an empty space, select New>folder, name it 'old-kernel' and drag and drop the old vmlinuz & zdrv into it. Then drag & drop the new. AND REBOOT.

[rcrsn51]

@mikeslr: Before sending this new user on a wild-goose-chase, have you confirmed that any of these alternate kernels actually support his particular 14c3:7961 device? Have you identified a source for the requisite firmware?

[DirectFX]

The mt7921u driver came into the mainstream Linux kernel around k5.12, so you would need a much newer Puppy than Fossa. Even then, your adapter might not be detected.

You might be better off getting a cheap N-mode adapter.

Just to be clear, is your adapter internal or USB?

It s internal adapter.

[DirectFX]

There may be other solutions. But the post here, https://askubuntu.com/questions/1357135 ... -card-7961 suggests that the 'stock' kernel --the one included in fossapup64's ISO-- may be too old; that you'll need the wifi-driver which, under Linux, only became available with kernel 5.12. That and any later kernel should do.

Fortunately, it's easy to change a Puppy's kernel. I'll explain how in a minute. But may I suggest that you try either (or both -- each only needs its own folder) S15Pup64, https://www.forum.puppylinux.com/viewto ... 125#p74125 or F96_4-radky5, https://www.smokey01.com/radky/Testing/ ... radky5.iso. Both have newer kernels. S15Pup64, binary-compatible with Slackware, is now the 'Official Puppy'. F96_4-radky5 is a newer version based on Ubuntu Focal Fossa. Both have recently been extensively tested. Any 'rough edges' that may later appear 'in the wild' should prove an easy fix.

Swapping kernels is at most 4-step process which can be done from a running Puppy. (1) Obtain the new kernel; (2) if obtained as a tar.bz2, extract it; (3) rename the two components; (4) Substitute the new from the old.

(1) Obtaining the new kernel: you can either use one you already have, for example by having deployed either S15Pup64 or F96_4-radky5; or you can download a 'hugh kernel' from a link on this Section, https://www.forum.puppylinux.com/viewforum.php?f=65. Without getting into specific reasons, I'll suggest the 5.19.11 from the link here, https://www.forum.puppylinux.com/viewto ... 585#p67585.

(2) Fossapup64 has a built in application for changing kernels when using a 'hugh kernel' package. Menu>Setup>QuickPet>Click Change Kernel. Read the help file. It may eliminate most of following.

(2a) A 'hugh kernel' is packaged as a 'tar.bz2'. Right-Click and extract it. That will produce two files, one named vmlinuz-xxxx, and the other kernel-modules.sfs-xxx. The 'xxx's' are so that humans can identify which is which.

(3) Rename vmlinuz-xxx to just vmlinuz. It is the kernel, itself. The 'kernel-modules' are the drivers compiled for that kernel. You'll notice that on storage Fossapup64 has a file named zdrv_fossapup64_9.5.sfs and another named initrd.gz. Initrd loads into ram first and then looks for files bearing a specific puppy's designation. Your fossapup's designation is 'fossapup64_9.5.sfs'. For historical reasons, Puppy identifies the drivers as zdrv. So You'd rename kernel-modules.sfs-xxx to zdrv_fossapup64_9.5.sfs.

(4) Substitute the new for the old. Just drag & drop from wherever you renamed the above next to fossapup64's initrd file. That will over-write the current files. But just to be safe, before dragging & dropping, I Right-Click an empty space, select New>folder, name it 'old-kernel' and drag and drop the old vmlinuz & zdrv into it. Then drag & drop the new. AND REBOOT.

Thanks actually It helps. I will try S15Pup64-22.12+1-T first. Maybe I will like the version itself If not Im gonna go with 4 step proces.

[rcrsn51]

It s internal adapter.

OK. So the correct driver name is mt7921e. I checked in another distro with k5.18 and your particular 14c3:7961 device is supported.

But it also requires the firmware files /lib/firmware/mediatek/WIFI_xxx, which are NOT in fossapup.

[DirectFX]

It s internal adapter.

OK. So the correct driver name is mt7921e. I checked in another distro with k5.18 and your particular 14c3:7961 device is supported.

But it also requires the firmware files /lib/firmware/mediatek/WIFI_xxx, which are NOT in fossapup.

Thank you this is important information. May I ask which distro also has the newer karnel? I already downloaded S15Pup64 for testing.

[rcrsn51]

Thank you this is important information. May I ask which distro also has the newer karnel? I already downloaded S15Pup64 for testing.

It's a kernel from Debian Bookworm. I downloaded the F96_4-CE_radky5.iso which has a k6.0 kernel, but I don't see your device in it.

[DirectFX]

Thank you this is important information. May I ask which distro also has the newer karnel? I already downloaded S15Pup64 for testing.

It's a kernel from Debian Bookworm. I downloaded the F96_4-CE_radky5.iso which has a k6.0 kernel, but I don't see your device in it.

You were right. In F96_4-CE_radky5 can't connect. I don't know about S15Pup64-22.12+1-T since It got stuck on "Waiting for modules to be loaded...". I flashed S15Pup64-22.12+1-T with BalenaEtcher. You maybe know the solution to this problem?

[rcrsn51]

You maybe know the solution to this problem?

You might be better off getting a cheap N-mode adapter.

[DirectFX]

You maybe know the solution to this problem?

You might be better off getting a cheap N-mode adapter.

I guess this is only solution.

[DirectFX]

Did you needed to use "LICK" program to boot "F96_4-CE_radky5.iso"? When I tried to flash iso in Balena It said there is no bootable file or something. With which program did u make ur bootable USB?

[rcrsn51]

Did you needed to use "LICK" program to boot "F96_4-CE_radky5.iso"? When I tried to flash iso in Balena It said there is no bootable file or something. With which program did u make ur bootable USB?

I didn't. I just mounted the ISO and looked inside for the Mediatek wifi drivers.

[mikeslr]

Balena does not properly flash Puppys to a USB-Key. If the operating system you are using to place a Puppy on a USB-Key is windows, see this post about using rufus, https://www.forum.puppylinux.com/postin ... it&p=40522. If a Linux operating system, see Bigpup's post about using Unetbootin, viewtopic.php?p=6801&sid=561bd9f430070f ... 2495#p6801. rcrsn51's ISObooter might also work, https://www.forum.puppylinux.com/viewto ... 211#p65211. But I'll leave it to him to explain how if that's at all possible from a different Linux Distro.
USB-Imager, https://gitlab.com/bztsrc/usbimager/#usbimager should also work, but will only create a READ-ONLY for-installation-to-another media USB-Key, see https://www.forum.puppylinux.com/viewto ... 376#p70376

Early on rcrsn51 accurately pointed out that I failed to mention that to use 5.19.11 Kernel you might need firmware. That's correct. But he didn't take the opportunity to explain what's going on or where to get the firmware. [Perhaps it was just easier to send you out to spend money on a cheap N-mode adapter which would, at best, always occupy one of your ports and at worst might not be fully functional].

80% of new computing devices are manufactured to run Windows. An operating system requires both drivers and firmware to communicate with hardware peripherals, such as wifi-adapters. Manufactures of such hardware peripherals take pains to provide both drivers and firmware for Windows. To a large extent, and especially with regard to the constantly evolving needs of web-facing hardware, the Linux community has to create its own drivers and firmware. Drivers are kernel-specific: they have to be compiled under and to function under specific kernels. Firmware is not. Once you have the correct firmware it will work with any kernel.

If I understand it correctly, the kernels used by Puppies are not 'compiled from scratch': rather Puppy Devs employ a kit to modify the kernels published by The Linux Kernel organization, https://www.kernel.org/ to include some capabilities --such as the employment of AUFS-- required by Puppys which the kernels direct from that organization lacks. New Kernels are frequently published. Each publication will try to include drivers for then current hardware; but --to reduce size and workload-- leave out drivers for 'older, less-likely to be needed, hardware. Puppy Devs do not intentionally leave out drivers which the Kernel Organization provides. However, neither do they include drivers for hardware not yet in existence, nor those for all the myriad hardware which has been manufactured and is somewhere out there.
The 5.12 kernel was identified as providing the needed driver. The 6 series kernels are new, involve substantial changes, and have not been identified as providing the driver you need. It should be included, but there's a difference between should be and is. As previously mentioned, Puppys require AUFS. The explanation I left out of my original post as to why a 5.19 kernel, is that "the only AUFS ACTIVE branches (for kernel develpment) are 5.x-rcN, 5.10.117, 5.10.140, 5.19. https://www.forum.puppylinux.com/viewto ... 490#p67490. Posts on the forum identified kernels of the 5.19 series as working under Puppies.

The ISOs of Puppys always provide what its Dev believes is the most likely needed drivers and firmware. As the specific files don't conflict with each other, some package both drivers and firmware in a zdrv.sfs. Others, locate only drivers in zdrv.sfs, placing firmware in a fdrv.sfs.

rcrsn51 correctly realized that if fossapup64-9.5's kernel didn't have the required drivers, it was also unlikely to have the required firmware. Some of our devs, such as gyrog, provide packages of firmware. His firmware packages tend to be all-encompassing, and consequently large. You can find them here, https://www.mediafire.com/folder/k2j223jzddy9x/firmware. His post on the forum provided a link to that.
As I previously explained with regard to drivers (zdrv.sfs) a firmware package would have to be renamed, using Fossapup64-9.5 as an example to fdrv_fossapup64-9.5.sfs.

On August 8, 2021, peebee --the author or S15Pup64-- published a much smaller collection (only 47.4 Mbs) here, https://sourceforge.net/projects/lxpup/ ... e-kernels/. It might be adequate. And if you already downloaded the S15Pup64 ISO, it contains a file named fdrv_s15pup64_22.12.sfs you could rename to fdrv_fossapup64-9.6.sfs and use with F96_4-radky5 if it has the needed driver but not the firmware.

[Indeed, if S15pup64 functions but you like F96_4-radky5 better, you can swap into F96_4-radky5 S15pup64's vmlinuz, zdrv.sfs and fdrv.sfs, renaming the latter two.

Ozsouth also publishes a smaller firmware package. It was last updated 2022-12-16. (By following links on the forum) you'll find it here https://www.mediafire.com/file/2fpl93zd ... 2.sfs/file. Considering its currency, and that it is about 400 Mbs smaller than gyrog's all incompassing package, I'd try that first.

[Firmware is copied into RAM-Cache, with only the actually required files being swapped into and out of usable RAM as and when needed. Still, a 400 Mb file will have some impact on the RAM available to perform work. There used to be an application which could 'cut' out and repackage just the firmware needed by a specific computer. I can't locate it. And despite my request no one with either the memory to do so has done so, or the programming skills to re-create it has come forward.]

@ rcrsn51: Those of us who answer questions posed on the forum, yourself included, do so having incomplete knowledge of all the facts. Your avatar suggests your learning and experience. I appreciate that. When it comes to understanding Linux, it far exceeds mine. And as I written many times, I have a sometimes flaky memory. But, until posts suggest otherwise, I find it advisable to treat the inquirer as having even less knowledge than I. So, while I may forget to mention some aspect, what I do write has been researched rather than 'remembered'; and presented so that even a newby can understand the why, the wherefore, and how to proceed from there.

They are not short and cryptic for the purpose of always seeming to be right.

Neither of us has the time, money, nor inclination to acquire and test every computer, every operating system and every peripheral which is the subject of an inquiry. I do the best I can. I'll be happy to stop posting at all if I have your word that you will start taking the drugs which will be necessary for you to devote the time necessary to answer all the posts which will go unanswered by my absence, and the absences of others whom you similarly think --lacking your expertise-- should remain silent.

Failing that, I've taken the liberty providing you with a more fitting avatar. Edit, graphic removed, Thanks, rcrsn51 for reminding me.

[ozsouth]

@mikeslr - unfortunately, none of my kernels (including 5.19.11) have mt7921 e/s/u set. I will add that to my next one. Then we can talk about firmware. Meanwhile, a simple usb wifi adaptor (tp-link wn725n is a good cheap one) is the best solution for @DirectFX now.

[mikeslr]

Thanks, Oz. Reality is always superior to theory. And specific knowledge to generalizations. Sorry, rcrsn51 if I was overly offended by your condemnation which lacked specifics or an alternate course of action which could be easily be implemented. You can keep using your preferred avatar.

@ rockedge, we really do need a Forum Section for making recommendations about computers and hardware which work or should be avoided. My objection to rcrsn51's generalization is that I am the disgruntled owner of a wifi-adapter my Puppys don't recognize. But it was cheap and is fully functional under Windows 7.

[ozsouth]

@DirectFX - even though the wifi adaptor suggested above is a good idea, IF you reinstall S15Pup64 successfully to a usb stick, your wifi driver mt7921e is in the kernel (5.15.80). Once booted into it, the attached firmware .pet should then make your wifi work. Use at own risk.
After downloading, to install, click on .pet in ROX-Filer, wait about 5 sec, then try to connect, choosing frisbee option.

I've also updated my firmware fdrv on 17dec22, to include more mediatek fw. See: https://www.mediafire.com/file/02r8zh7s ... 2.sfs/file

[bigpup]

@mikeslr

My objection to rcrsn51's generalization is that I am the disgruntled owner of a wifi-adapter my Puppys don't recognize. But it was cheap and is fully functional under Windows 7.

Did you ever post a topic about your WIFI adapter issue?

From recently getting WIFI hardware working on a very new laptop.

I think what ozsouth posted is exactly what this person needs for his adapter.
A Puppy version whose kernel has the driver, but the firmware is missing.
So here is the firmware it needs.

In my case the Puppy versions did not have the WIFI hardware driver in the kernel they are using, but did have the firmware. (Fossapup64 9.5 and S15pup64 22.12)
I compiled the needed driver for each Puppy version kernel and installed it. (Drivers are kernel specific)
WIFI is now working.

For WIFI hardware you need two things:
kernel driver
Specific Hardware firmware
Well three if it is a laptop computer that has airplane switch to turn internal WIFI on/off. Make sure it is turned on. (I think I actually did turn off the WIFI at one point, trying to get it working, by accidentally hitting this switch)

Only thing needed is to figure out what is missing and provide it.

[mikeslr]

Thanks, bigpup, for the concern. My router broadcasts two signals, one being 5G. I have an old USB wifi-adapter which under Puppys picks up the other, but not the 5G. So I searched for and found one touted as working with Linux for about $10. It does: with LinuxMint and Manjaro. But not Puppys. It is possible that one of Puppys kernels might support it. But investigating which without any assurance of success takes time.

Although I have a lot of time to spare, I still consider it valuable. I also think the time of those, like ozsouth --who compile applications for others that they, themselves, don't need-- is also valuable.

Under the circumstances, obtaining 5G is a luxury --worth a $10 gamble-- but not worth spending my time or the time of others to obtain.

P.S. Happy that ozsouth has a possible solution. Having learned rcrsn51 exploratory technique --examine .../lib/firmware for the specific file, assume if absent so will be the related driver-- I checked recent Puppys and KLV-Airedale. None sport the MT7921. Neither do my versions of weedog'd Manjaro and Pop_OS.

[rcrsn51]

Having learned rcrsn51 exploratory technique --examine .../lib/firmware for the specific file, assume if absent so will be the related driver-- I

The definitive method would be to look in /lib/modules/xxx/kernel/drivers/net/wireless/mediatek for the file mt7921e.ko

I notice that you have still posted that insulting avatar. If you were genuinely apologetic, you would remove it.

[DirectFX]

Thank you all for your help. You really gave me a lot of informations to help. I'm going to try the solution without wifi adapter even though I have probably one siting somewhere in the corner covered in dust. I just like challenge sometimes and It would really help me with learning more about this distro and linux itself (kernels, firmwares, drivers etc.) as I want to install "puppy" on USB and make as flexible as It could get so I could stick the USB in almost "any" computer and use it for backup data from example: HDD or SSD when other OS crash or maybe just watch or browse,...

For now I need to figure It out how to get past "waiting for modules to complete loading" in S15Pup64 since It gets stuck there. Boots well in VirtualBox but not when I flash it on USB even not when I use FrugalPup for It.

[bigpup]

get past "waiting for modules to complete loading" in S15Pup64 since It gets stuck there

S15pup64 was being bug fixed to get released.
It has been reissued several times over the last few weeks.

Are you using this version of it:
S15Pup64-22.12+1-T.iso

Even if it looks like it is stuck at this point in the boot process.
If booting from a USB stick install.
The speed of the drive and the speed of the USB port, could make it look like it is stuck.

How much time have you given it to get past this point in the boot process?

[mikeslr]

Having learned rcrsn51 exploratory technique --examine .../lib/firmware for the specific file, assume if absent so will be the related driver-- I

The definitive method would be to look in /lib/modules/xxx/kernel/drivers/net/wireless/mediatek for the file mt7921e.ko

I notice that you have still posted that insulting avatar. If you were genuinely apologetic, you would remove it.

I've removed the avatar. Unfortunately, I didn't keep a copy which I considered using as my own for a while to remind me that the conduct I accused you of engaging in was what I, myself, had done.

I knew the designation of the firmware but not that mt7921e.ko was the name of driver. Kind of reminds me of the story about the drunk crawling around under a street lamp. Asked what he was doing he responded, "I'm looking for my keys." Asked "Is this where you lost them?", he responded, "No, but this is where the light is."

Well, the logic is a little better. A system lacking the firmware is also not likely to have the corresponding driver.