Puppy Linux Discussion Forum

.

Thanks, jrb for publishing Another Jammy64pup. And thanks, jasper for continuing to update its applications.

Another Jammy64pup is the only Pup on my computers which fully support my long-time favorites --such as Osmo and pWidgets-- as well as current versions of my most commonly used applications.

I may have to master pkg-cli(2) to add some oddballs only available as flatpaks.

.

.

.

.

Computer in sig below....

Just tried Jammy64 this evening and was pleased to find that the touchpad worked OOTB on this very new computer. Great! One of the only puppies that this has happened with.

Unfortunately wifi doesn't work. The card is an Intel Wifi 6e ax211. Generally seems to require iwlwifi firmware iwlwifi-so-a0-gf-a0-71.ucode and iwlwifi-so-a0-gf-a0-72.ucode to work I believe. I did try installing Gyrog's linux_firmware_usr_20240201.sfs but still couldn't get it going.

.

Thanks Jasper, but I already had those drivers and had tested them out when I first posted here.

I did however download your .pet just to make sure, then install it, then save and reboot. But no change. No wifi is shown at all. Just bluetooth.

One possible explanation is that sometimes I need to use a different one of Puppy"s network managers to initiate using this card. Unfortunately, the only network manager in Jammypup64 is the simple one, and that one has no information and won't allow you to choose a different interface (in this case iwlwifi).

Frisbee seems the most thorough in recognizing a new hardware interface. It seems to work for me when others fail.

@vtpup

I had similar issues myself before I got it working properly.

I removed my default FDRV.SFS and then booted up the device to see which hardware would function without the need of additional drivers.

Then I had to switch kernels until I found which one was the most suitable for me.

Then I used the "WiFi" only drivers.

@ozsouth , was kind enough to work it through with me.

In the end I had to downgrade my Linux kernel (ZDRV.SFS & Vmlinuz) to ensure that I had it stable.

It is a bit of trial and error, however it will work

Also, @rerwin , has provided updates to his networking applications here:

viewtopic.php?p=2241#p2241

Hi Jasper, thanks. I had already tried other kernels and fdrv, as well as other "huge" firmware sfs. Something seems wrong with the distro re. wifi in general. I haven't had these problems with doing the same with F95, F96CE, Bookworm64, even Bionic64.

There is no network wizard in Menu>Setup or a network manager switcher. SNS/conman seems to be the only included network manager, and as I said it provides no useful info or options. It just shows nothing.

This is a basic problem, the other network managers are necessary to try any other solutions. I have downloaded the Frisbee and old Network Manager links from Rerwin's thread that you referenced above. But neither of them is functional to see the firmware. I'm not sure if this is a usr-merge problem or what. Essential to get Intel wifi cards working is iwlwifi. It would normally be very standard in an installation, but seems not to be loaded by default in Jammy. Network manager can't find it:

And modprobing it in seems to have no effect on Network Manager. It still looks for it in that kernel module directory. Frisbee also seems confused about loading interfaces.

Intel wifi kernel support should be simple as Intel is a total standard and their drivers modules and firmware are all open source AX211 wifi has been around for a few years.

Anyway, I'm going to look in on this thread when I canand a network wizard with additional network managers, in case it gets a changed and/or updated kernel, but unfortunately I can't keep testing suggestions to fix this myself -- I have to do taxes this week! Yuck...

Jasper wrote: Tue May 21, 2024 6:25 am

Small internal updates

croc-9.6.17 - Simple, and secure file transfer between any two computers

Or via terminal for a quick 'n dirty' install or update:

wget -qO- https://getcroc.schollz.com | bash

@sonny

Thanks for sharing the script

The only issue is that it places the binary in the wrong location. A quick check shows me it hasn't been stripped either ........ what's a few extra kb's

The binary should be installed in

/usr/bin

not

/usr/local/bin

a possible solution would be to add

bash -s /usr/bin

this would download the binary to the correct location.

Unfortunately, it does not work for this application

.

.

.

SPAM message ............ advertising a product/service not included in my original message

@Jasper :-

Edited to remove the "spam info" that was added. See above.

I can't really ban the poster for this because it WAS their first infraction.....and it wasn't even an actual link. Not yet, anyway....!

Mike.

.

.

.

.

.

.

.

.

.

.

.

.