Bionicpup64 8.0 CE

[rerwin]

The connection time was halved, it was just under 40 seconds after desktop is loaded.

Wow! And that is with the fix in the wrong place in the code.

The trace tells me that 30 network entries were skipped but that 5 unnecessary entries were processed. Forty seconds saved and 30 records skipped means each entry takes about 1.3 seconds. So, skipping 5 more should reduce the time by 7 seconds.

The timing can be seen by a grep command, which shows the following for Terry H:

Code: Select all

# grep '^DEBUG:' bootsysinit.log 
DEBUG: 18:55:58 Starting iwlist scan for wlan0 networks.
DEBUG: 18:56:01 Completed iwlist scan for wlan0 networks.
DEBUG: 18:56:04 Completed wpa_supplicant for wlan0 network.
DEBUG: 18:56:39 Completed wpa_supplicant for wlan0 network.
DEBUG: 18:56:45 Completed connection processing for wlan0.
DEBUG: 18:56:45 Completed connection processing for wlan0.
#

I have now corrected the fix and replaced the file, at:
http://www.murga-linux.com/puppy/viewto ... 61#1009361

For my system which sees only one network, I get:

Code: Select all

root# grep '^DEBUG:' bootsysinit.log
DEBUG: 06:57:16 Started rc.network processing for wifi networks.
DEBUG: 11:57:20 Started iwlist scan for wlan0 networks.
DEBUG: 11:57:21 Completed iwlist scan for wlan0 networks.
DEBUG: 11:57:24 Started wpa_supplicant for wlan0 network.
DEBUG: 11:57:25 Completed wpa_supplicant for wlan0 network.
DEBUG: 11:57:25 Started dhcpcd for wlan0 networks.
DEBUG: 11:57:33 Completed dhcpcd for wlan0 networks.
DEBUG: 11:57:33 Completed connection processing for wlan0.
DEBUG: 11:57:33 Completed connection processing for wlan0.

So, the minimum time to expect is about 17 seconds, total. That seems to result in my network icon showing "no connection" for less than 1 second.
Richard

[Terry H]

Richard,

FAN...TAS...TIC. Wifi up 8 seconds after desktop. Rebooted to check and confirm. Great job. Thank you.

Do you need the bootsysinit.log?

Code: Select all

root# grep '^DEBUG:' bootsysinit.log
DEBUG: 11:17:36 Started rc.network processing for wifi networks.
DEBUG: 16:17:40 Started iwlist scan for wlan0 networks.
DEBUG: 16:17:44 Completed iwlist scan for wlan0 networks.
DEBUG: 16:17:47 Started wpa_supplicant for wlan0 network.
DEBUG: 16:17:48 Completed wpa_supplicant for wlan0 network.
DEBUG: 16:17:48 Started dhcpcd for wlan0 networks.
DEBUG: 16:17:54 Completed dhcpcd for wlan0 networks.
DEBUG: 16:17:54 Completed connection processing for wlan0.
DEBUG: 16:17:54 Completed connection processing for wlan0.

Edit: Checked in upupbb 18.05 also, it was equally as quick to have wifi active.

[rerwin]

Do you need the bootsysinit.log?

Yes, please. I need to confirm that we got the right answer the right way. I am working up the next version of SNS -- 2.1 -- for woofCE. I may post it for testing.

Edit 11/15/18: simple_network_setup-2.1 is now available here:

http://www.murga-linux.com/puppy/viewto ... 876#952876

[Mike Walsh]

WeX screencaster 0.8.18 'patched' for Bionicpup64

Morning, all.

New 'all-in-one' version of Will McEwan's WeX screencaster now available for Bionicpup64 (with Weav & scrox built-in). This has been patched by means of the 'audio_in.plug' plugin having been modified; the problem with ffmpeg's 'asyncts_filter' option has now been eliminated.

Make sure to update the PPM, and install all the 'ffmpeg' stuff first. Also check to see if the system has libgiblib1 installed, as this is required. If not, just plug 'giblib' into the PPM search box, and install the result.

http://www.murga-linux.com/puppy/viewto ... 99#1009799

Enjoy.


Mike.

[belham2]

Hi Phil and all,

Just curious....as Bionic obsoleted my Sony Vaio laptop's SDCard slot, I just tried on another laptop (an HP with an Intel chip and brcm wireless) to install Bionic and it will not recognize the built-in wireless (Brcm4311 802.11bg WLAN) card.

When this HP laptop is running Xenialpup and the wireless is recognized and working fine & dandy, I see that both of these modules are loaded (4.9.15) kernel:

module name: wl
path: /lib/modules/4.9.15/kernel/drivers/net/wireless/wl.ko

module name: cfg80211
path: /lib/modules/4.9.15/kernel/net/wireless/cfg80211.ko


When I load and boot Bionic, and it goes to desktop with no recognition of the built-in brcm4311 wireless (even punching the manual wireless on-off button does nothing and trying to copy over firmware from Xenial to Bionic---nada, nothing works), the cfg80211 module was loaded from 4.18.15, but there is no "wl.ko" to be found anywhere in Bionicpup. Where's the "wl.ko" in Bionic, Phil???

Anyone run into this problem? Or have a wireless problem with Bionicpup64 install?


Lol, I am starting to hate updated pup distro(s)....keeps obsoleting stuff left and right, stuff that is not even 5-6 yrs old. This is 2 laptops now that Bionicpup has coughed up the obsoleting problem. Ugh.....

[perdido]

module name: wl
path: /lib/modules/4.9.15/kernel/drivers/net/wireless/wl.ko

A related broadcom wireless issue of missing wl.ko was recently discovered and
fixed in bionic beaver by pemasu, may be some useful info for bionicpup.
http://www.murga-linux.com/puppy/viewto ... 50#1009650

.

[sheldonisaac]

belham2, best wishes; probably my report won't help, but FWIW, see below.

Bionic obsoleted my Sony Vaio laptop's SDCard slot, I just tried on another laptop (an HP with an Intel chip and brcm wireless) to install Bionic and it will not recognize the built-in wireless (Brcm4311 802.11bg WLAN) card.

Bionic seems to recognize the SD card slot in my primary computer, this Dell E6410, and also the Atheros built-in wireless.
Re the modules, thanks: I looked in this Bionicpup64, and found

-rw-r--r-- 1 root root 619454 Nov 9 00:58 /lib/modules/4.14.79-u64oz/kernel/net/wireless/cfg80211.ko

and

-rw-r--r-- 1 root root 44342 Nov 9 00:57 /lib/modules/4.14.79-u64oz/kernel/drivers/net/wireless/wl3501_cs.ko

Among lots of things, lsmod shows

cfg80211 319488 4 ath9k_common,ath9k,ath,mac80211

[belham2]

module name: wl
path: /lib/modules/4.9.15/kernel/drivers/net/wireless/wl.ko

A related broadcom wireless issue of missing wl.ko was recently discovered and
fixed in bionic beaver by pemasu, may be some useful info for bionicpup.
http://www.murga-linux.com/puppy/viewto ... 50#1009650

.

Gracias, Perdido....that should do it! Should have known Pemasu or Peebee and/or one of you gurus would see it immediately. It seems the older I get, the more I "for"-get how to fix things in Puppy. It makes me get mad at myself that I can't remember how to do some things in puppy that I just did 4-5 years ago. Haha.....getting lazy and modern-day puppies have been spoiling me

Thanks again!

[belham2]

belham2, best wishes; probably my report won't help, but FWIW, see below.

Bionic obsoleted my Sony Vaio laptop's SDCard slot, I just tried on another laptop (an HP with an Intel chip and brcm wireless) to install Bionic and it will not recognize the built-in wireless (Brcm4311 802.11bg WLAN) card.

Bionic seems to recognize the SD card slot in my primary computer, this Dell E6410, and also the Atheros built-in wireless. Re the modules, thanks: I looked in this Bionicpup64, and found

-rw-r--r-- 1 root root 619454 Nov 9 00:58 /lib/modules/4.14.79-u64oz/kernel/net/wireless/cfg80211.ko

and

-rw-r--r-- 1 root root 44342 Nov 9 00:57 /lib/modules/4.14.79-u64oz/kernel/drivers/net/wireless/wl3501_cs.ko

Among lots of things, lsmod shows

cfg80211 319488 4 ath9k_common,ath9k,ath,mac80211

Thanks, Sheldon....Peebee did (a few days ago) come to the rescue, it's just that I've been too lazy to get at it. So I was making the cardinal sin of complaining and whining, which I am ashamed of. Well, that is, still in my imitation of Trumpian defense, it's partly Phil's & Peebee's fault in the first place! Why? They've coddled me so long now (especially Peebee) by never expecting a problem when I do a new install and/or upgrade with their OSes, that when something actually does go wrong, I can't find my way out of a wet paper bag anymore. It's embarrassing

[peebee]

module name: wl
path: /lib/modules/4.9.15/kernel/drivers/net/wireless/wl.ko

Broadcom wl is another proprietary driver that is NOT included in the kernel.
And it is kernel dependent
and builds take time and effort to produce
so its only worth building for system builds and kernels that are going to be around for a llllllllloooooooonnnnnnnnnnnggggggggggggg time......

Beta does not fit this model......so don't expect to get any proprietary drivers in beta releases.....

[sheldonisaac]

Broadcom wl is another proprietary driver that is NOT included in the kernel.
And it is kernel dependent
and builds take time and effort to produce
so its only worth building for system builds and kernels that are going to be around for a llllllllloooooooonnnnnnnnnnnggggggggggggg time......

Beta does not fit this model......so don't expect to get any proprietary drivers in beta releases.....

Thanks, peebee, good points! And thanks to you all for a bit of education to my old brain.

Funny (maybe) story: a few years ago, I tried a librepup, whose author wanted to use only public domain (or whatever that's called nowadays) components.
Well, it did not see the Broadcom wireless card in the Dell E6410. So I bought an Intel card. Still didn't work. My friend gave me the Atheros card from his son's broken laptop. This seems to work with all the Puppys; at least the ones currently in menu.lst: this Bionic64, Xenial32, and Tahr32.

Sheldon

[bigpup]

Beta refers to the phase in software development between the alpha phase and the release candidate phase.

Beta software is generally considered "complete" by the developer but still not ready for general use due to a lack of testing "in the wild." Websites, operating systems, and programs alike are often said to be in beta at some point during development.

Beta software is either released to everyone (called an open beta) or a controlled group (called a closed beta) for testing.
The Purpose of Beta Software

Beta software serves one main purpose: to test performance and identify issues, sometimes called bugs.

Allowing beta testers to try out software and provide feedback to the developer is a great way for the program to get some real-world experience and to identify how it will work when it's out of beta.

In Puppy Land we the users are the beta testers.

So, you found a problem and reported it.
Others offered possible fixes.
If the fix works. Report it so the developer of Bionicpup64 can add it to the OS.

[Terry H]

Hi Phil and all,

Just curious....as Bionic obsoleted my Sony Vaio laptop's SDCard slot, ...

I don't think this is quite true, Dell were using realtek pcie card readers as recent as last year and probably still are in current laptops. I believe it was an oversight / bug that the kernel parameter is not being set for rtsx_pci in newer kernels.

[ozsouth]

@belham2 - I've made Broadcomm wireless drivers for my 2 newest kernels - can't test them though.
See http://murga-linux.com/puppy/viewtopic. ... 05#1009905

[Mike Walsh]

@ sheldonisaac:-

Funny (maybe) story: a few years ago, I tried a librepup, whose author wanted to use only public domain (or whatever that's called nowadays) components.
Well, it did not see the Broadcom wireless card in the Dell E6410. So I bought an Intel card. Still didn't work. My friend gave me the Atheros card from his son's broken laptop. This seems to work with all the Puppys; at least the ones currently in menu.lst: this Bionic64, Xenial32, and Tahr32.

That's not hard to understand, Sheldon. The Broadcom and Intel card drivers use 'blobs'; small chunks of proprietary, closed-source code. The Atheros drivers don't; it's all 'open-source'.

Which just happens to be one of the primary requirements for any fully 'libre' distro...and it's also why folks have gone to a great deal of trouble to also develop a fully 'libre' BIOS (and boot-loaders, too).


Mike.

[belham2]

@belham2 - I've made Broadcomm wireless drivers for my 2 newest kernels - can't test them though.
See http://murga-linux.com/puppy/viewtopic. ... 05#1009905

Hi Ozsouth!

I saw (your post in the other thread) early this morning and am going to download the 64bit & give it a go tonight on that HP laptop. Not sure if it matters though, as Peebee said the main wl.ko module or something is not included in this Bionic edition because it is beta. Need that wl,ko to load first, I think, so that wireless is recognized as being a option with any/all broadcom wifi chipsets. Once that wl.ko is loaded, maybe then yours kicks in? I don't know. Anyhow---BIG THANK YOU for making the two .pets for broadcom-STA.

I might be misunderstanding things, but either way when I get off work, going to download it and give it a go on the laptop.

Thanks again!


[Update, Tuesday, 13 Nov: I installed your 64-bit ubuntu broadcom-STA.pet into phil's Bionic64, but no luck. I also navigated to the /lib/modules/4.18.15/kernel/drivers/net/wireless/ to make sure the .pet installed the "wl.ko" correctly, and it did. One thing to note is that when I did boot with your .pet installed, at least for the first time bionicpup64 recognized there was a wireless there in the laptop. But it was hopeless in determining what kind or even if it was broadcom, yet Puppy Network Wizard gave an option (for the first time) that there is a pci wireless on the laptop. I don't know if we need more drivers, or different drivers. When going through Puppy Network Wizard, everything I tried kept throwing back this:

Error!
Failed to raise interface wlan0 (despite Puppy Wizard seeing a PCI wireless interface)
Failed command was: ifconfig wlan0 up
Error returned was: ifconfig SCIOCSIFFLAGS: No error information

Thanks again, ozsouth for giving this a go....looks like I'll have to wait for whenever the bionic-Beta edition becomes the "not" beta edition anymore & then hope to get it working with the gurus help. Otherwise, back to the the older pups and stay away from these new kernels & pups of the past 12 months, or go with Slackware which weirdly has no problems with the HP broadcom laptop

[Billtoo]

New install to a 64gb usb-3.0 flash drive:

System: Host: puppypc25219 Kernel: 4.19.1 x86_64 (64 bit) Desktop: JWM 2.3.7 Distro: bionicpup64 7.9.6
Machine: Device: desktop System: HP product: 260-p029 serial: CNV6240BWP
Mobo: HP model: 81B4 v: 01 serial: PFPSK0BWJ301LW UEFI [Legacy]: AMI v: F.04 date: 05/10/2016
CPU: Dual core Intel Core i3-6100T (-HT-MCP-) speed/max: 1103/3101 MHz
Graphics: Card: Intel HD Graphics 530
Display Server: X.org 1.19.6 driver: intel tty size: 171x23 Advanced Data: N/A for root
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Card-2: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be
Drives: HDD Total Size: 1061.7GB (2.2% used)
Weather: Conditions: 32 F (0 C) - Mostly Cloudy Time: November 13, 3:28 PM EST
Info: Processes: 143 Uptime: 22 min Memory: 207.3/3809.9MB Client: Shell (bash) inxi: 2.3.8

I'm using the fatdog kernel, it doesn't see the sdhc card reader.
It connected to the wireless adapter from the network wizard.
Streaming video is good with this kernel, not even a ripple.

Thanks.

[ozsouth]

@belham2 - wl drivers are kernel-specific & I used what I had - kernel 4.14.79 (ubuntu derivatives) - .pet won't work in other kernels.

[Billtoo]

I updated this install:

System: Host: puppypc28882 Kernel: 4.14.81 x86_64 (64 bit) Desktop: JWM 2.3.7 Distro: bionicpup64 7.9.6
Machine: Device: desktop System: Compaq-Presario product: AU194AA-A2L CQ5123F serial: MXX9300M0F
Mobo: MSI model: Boston v: 1.0 BIOS: Phoenix v: 5.24 date: 06/19/2009
CPU: Dual core Pentium E5200 (-MCP-) speed/max: 1866/2500 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] RV530 [Radeon X1600 PRO]
Display Server: X.org 1.19.6 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
tty size: 167x26 Advanced Data: N/A for root
Network: Card: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169
Drives: HDD Total Size: 626.4GB (4.5% used)
Weather: Conditions: 28 F (-2 C) - Overcast Time: November 15, 12:04 PM EST
Info: Processes: 87 Uptime: 29 min Memory: 160.6/3952.0MB Client: Shell (bash) inxi: 2.3.8

Changed from dual monitor setup to one larger monitor.
Changed kernel + added Firefox.

Works well.

[666philb]

Test 7.9.6 on Lenovo yoga 530
AMD Ryzen 5 2500u
Pristine frugal install

Thanks for the included Realtek RTL8821CE wifi kernel module. Sorry to say, the device was not detected. Is there anything I can test/do?

I thought the newer kernel would have positive effect on the graphical experience... But it hasn't... It sometimes loads into X, sometimes not. When reaching X, the system freezes after minutes (sometimes seconds).
It uses the ati driver, and I wonder if I should try the AMD proprietary driver? The problem is that I can't connect to the web, so I have to somehow include it into my usb-pendrive that I boot from. Secondly, I have to force Puppy to use it during boot. Can I do that in xorgwizard?

Neither the touchpad nor the touchscreen works.

Thanks for any help

hi zigbert,

can you PM me your /var/log/messages & /var/log/Xorg.0.log

also in a terminal try depmod -a and see if that gets your wifi seen