Puppy Linux Discussion Forum forum

@wizard & @rcrsn51 It seems you both seek to establish if I already have a "native" WiFi module in the Pavilion. What follows is my attempt to provide the info to establish that point. I conclude "yes" - there is (or should be) the hardware present. (a) At first I believed that there was no WiFi hardware present. (b) I believe I was wrong . I believe there is a Broadcom device present. Everything below is on that point. Cobaka. First my reasons for believing "no native WiFi present". (1) After installing BWPup64 - no traffic seen on desktop (conky) display. . (I think the display is conky). . Using SNS (simple n/w setup) conky did NOT display traffic to/from the modem. . Prior to this, SNS always configured/connected to the net as expected. (2) After I connected USB "dongle" I saw traffic on conky. I could log onto this forum (sometimes), but the performance was abysmal. (3) The original owner told me he had to buy a SIM card to connect, and for that reason I thought, "strange". That's why I though I must add a dongle to get WiFi. Now - following @wizard and @rcrsn51 's suggestion (internal device exists) I started to look for confirmation. Where would I get confirmation? (Well, (dear собака) why not look in the user manual. Good idea, eh? (clever me!) (4) From the Pavilion manual, page 51. . WLAN module .Atheros 9485GN 802.11b/g/n 1×1 WiFi and 3012 Bluetooth 4.0 Combo Adapter -- p/n 655795-001 .Atheros WB225 802.11b/g/n 1×1 Bluetooth Combo Adapter. . . 675794-001 . Broadcom

I also tried the kernel change mechanism that worked fine for the most part. However, the pet with the broadcom-sta module for the 6.12.109 kernel that was working fine in 7.4.92, loaded but no wifi could be detected. Tried to unload reload and nothing changed without any kernel warnings or complains. Tried the broadcom-sta driver with the kernel role back and it appears that in that case the b43 module is also loaded and messes up the wifi Code: uname -r6.12.109lsmod | grep wlwl 6455296 0cfg80211 425984 3 wl,b43,mac80211#......uname -r7.2.12lsmod | grep wlwl 6459392 0cfg80211 479232 1 wl So I used the approach that fatdog is using, removing the conflicting modules and reinstalling broadcome-sta and associates, and worked Code: rmmod b43rmmod wlrmmod ssbrmmod bcmarmmod mac80211rmmod cfg80211modprobe lib80211modprobe cfg80211modprobe wl Not sure why this conflict is appearing only during the rollback to an older kernel but at least there is a work around till a better solution is implemented.

I've uploaded the new Rox-Filer2 2.14.0-6 release with the correct source code. Hi. Will you being updating the .debs ? https://sourceforge.net/projects/essora ... /packages/

Hi @peebee : Thanks a lot for your answer, but I need 6.18.56, Sorry - only the current version is available........

@davids45 - 6.12 will introduce a firmware issue - you'd need an updated fdrv (this pup's firmware is puppy .sfs) - kernel & fdrv from bookworm are usrmerge anyway, so can't use with this pup. Maybe try this later kernel (unzip it & replace zdrv / vmlinuz): https://www.mediafire.com/file/d1g75mjr ... s.zip/file

hi, I see that BookwormPup64 got in the past update versions every 4-6 months. But the last version 10.0.12 is 1 year "old". Should we expect new one?

G'day norgo & ozsouth, I've just tried the terminal commands in norgo's list in SLK as supplied (k-6.1.13): and with a 6.6.8 kernel from ozsouth (using its zrdv.sfs and vrmlinuz in place of the originals): The wifi modules were shown as present in both kernels but neither produced a wireless interface nor could either be activated. Do I need a newer new kernel - Bookworm has a 6.12.71 (being used now)? Heres the terminal list in this Bookworm Pup to show me what is expected when the wifi on my Cubi works: Thanks again for you time and trouble. David S.

Did my upgrade from 7.4.92 version to 7.5 version and so far all is well. Noticed the TV Panel is a new version all channels work. I'll go through the Chromium settings tomorrow and see if anything snuck in by the Chromium devs or any new changes. I like DuckDuckGo search engine. Any way the new version seems to be working good installed as a frugal on a 16 GB (2.0) PNY USB flash drive. Is there a terminal command to check for any old kernels from previous versions that are no longer need. If there is a command for that is there also a command to remove old no longer needed kernels. Thanks @BarryK

@rockedge @Sofiya @peebee @Duprate , I've uploaded the new Rox-Filer2 2.14.0-6 release with the correct source code. I've also improved the "Open With" menu. When there are more than three applications, they're now grouped into a submenu. Could you please give this version a try and let me know if everything works correctly on KLV? https://github.com/josejp2424/ROX-Filer ... /v2.14.0.6 You have the same version listed twice in your Tags (c . and c -) When updating a template, the latest one is always looked at You're right, @Sofiya . I accidentally created two tags for the same commit.

@rockedge @Sofiya @peebee @Duprate , I've uploaded the new Rox-Filer2 2.14.0-6 release with the correct source code. I've also improved the "Open With" menu. When there are more than three applications, they're now grouped into a submenu. Could you please give this version a try and let me know if everything works correctly on KLV? https://github.com/josejp2424/ROX-Filer ... /v2.14.0.6 You have the same version listed twice in your Tags (c . and c -) When updating a template, the latest one is always looked at

@rockedge @Sofiya @peebee @Duprate , I've uploaded the new Rox-Filer2 2.14.0-6 release with the correct source code. I've also improved the "Open With" menu. When there are more than three applications, they're now grouped into a submenu. Could you please give this version a try and let me know if everything works correctly on KLV? https://github.com/josejp2424/ROX-Filer ... /v2.14.0.6 Let's say first you decide whether you will have a version with ( . or - ), I'm tired of rewriting the update script back and forth

@rcrsn51 You: @cobaka Here is the reality of your situation. I love dealing with reality! 1. Your attempt to build the AX300 USB driver has failed again. That's me. Agree. First class loser (but what about the ant and the rubber tree plant?) 2. The install script you are using is intended for mainstream distros, not Puppy. That is definitely the case. See previous posting about "unable to locate vmlinuz". 3. All your subsequent testing continues to be on the original internal adapter, which you know to be defective. That isn't certain, and I will investigate that point. (but later). 4. No amount of pinging is going to fix it. Certainly true, but isn't pinging (and tracerouting) and all the other stuff fun? (The next part of this adventure will involve .... diving into code) собака