Bionicpup64 8.0 CE

[Revolverve]

phil,666,d,hi,
restarting x, start ppm=
gtkdialog: ../../src/xcb_io.c:165: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed.
/usr/local/petget/pkg_chooser.sh: line 743: 32008 Aborted gtkdialog -p PPM_GUI
geany: Warning: ignoring null tag in /initrd/mnt/tmpfs/tmp/gtkdialog-splash_gtkrc
----nothing serious,killing /tmp/yaf-splash..bla..bla. and next call to ppm get the gui,until next X restart.

[ally]

I've set up 7.9.6 to run as my daily driver for a while to test

I was running google_chrome-57.0.2987.98-amd64-tahr.sfs on my xenialpup64-7.5 but on bionic this had artefacts within the text, moving to Google_Chrome-60.0.3112.101-amd64-tahr.sfs solved the issue (due to heavy download/uplosds to the archive the spot system gets in the way)

I have just discovered that the UP arrow launches print-screen, awkward in terminal! ** edit ** GB map



edit: I've installed on a second laptop and the UP arrow print screen launch is not happening, will do a fresh savefile and see if it still happens

[Terry H]

@rerwin

Richard,

I sent below details yesterday as a PM, but just noticed it stuck in outbox:

I am unable to get Bionicpup64 to auto connect using the provided rc.network script.

To test I changed from frisbee back to SNS as default. I changed to revised script and rebooted. It did not auto connect, so I manually connected from SNS > Intefaces. Attempting to connect from the Saved Profile list just hangs with "Please wait..." message on the screen. I did this several times, as well as deleting profiles and retrying. On the retries, I did not get confirmation of setting up SNS as default. I switched back to the original script and set up wifi again and rebooted twice to check auto connect. On both of these boots it took about 1:15 on the stop watch from desktop launch. I then swapped in the revised script again and once again failed to auto connect. Attempts to set up connection using the revised script does not give cofiirmation of setup.

So it appears that the password is not being saved when using the revisedscript. Line from bootsysinit.log:

/usr/sbin/network_default_connect: line 74: /usr/local/simple_network_setup/rc.network: Permission denied

[peebee]

Maybe Peebee and/or Phil will see our posts here (and what I've found, that the Realtek RTS-versions worked in Xenial & LxpupSC64-18.04 versions, but the latest stuff of Bionic & Lpupsc64-18.06 killed them off.

Looks to me like a kernel config change has occurred from k16....see:
https://cateee.net/lkddb/web-lkddb/MISC_RTSX_PCI.html

CONFIG_MISC_RTSX_PCI=m
is now maybe needed in kernel config??
Would be good if somebody could confirm - please.

Even if this is what is needed, old kernels are unlikely to be rebuilt with this config - but new kernels could be.

[ozsouth]

I've made a 4.14.79 64bit ubuntu derivative kernel: http://murga-linux.com/puppy/viewtopic. ... 17#1009517
@peebee - I have CONFIG_MFD_RTSX_PCI=m in mine, but not MISC.

[peebee]

I've made a 4.14.79 64bit ubuntu derivative kernel: http://murga-linux.com/puppy/viewtopic. ... 17#1009517
@peebee - I have CONFIG_MFD_RTSX_PCI=m in mine, but not MISC.

Yes - thats the old config up to k15:
https://cateee.net/lkddb/web-lkddb/MFD_RTSX_PCI.html

I think??

[peebee]

As often Fatdog/JamesBond has the answer.....

Fatdog Kernel 19.1 is correctly configured and has the rtsx modules:
http://distro.ibiblio.org/fatdog/kernels/800/

The config is attached (remove -false.gz)

[belham2]

As often Fatdog/JamesBond has the answer.....

Fatdog Kernel 19.1 is correctly configured and has the rtsx modules:
http://distro.ibiblio.org/fatdog/kernels/800/

The config is attached (remove -false.gz)

Thanks, Peebee! It never even occurred to me to look in Fatdog.

Will give this a go and see what happens.........

[Billtoo]

This install was done a few days ago, have since updated the kernel:

System: Host: puppypc29722 Kernel: 4.14.79-x86_64 x86_64 (64 bit) Desktop: JWM 2.3.7
Distro: bionicpup64 7.9.6
Machine: Device: desktop Mobo: Acer model: Aspire X3950 serial: U02C120500059
BIOS: American Megatrends v: P01-A3 date: 05/05/2010
CPU: Dual core Intel Core i3 540 (-HT-MCP-) speed/max: 1628/3067 MHz
Graphics: Card: Intel Core Processor Integrated Graphics Controller
Display Server: X.org 1.19.6 driver: intel tty size: 172x28 Advanced Data: N/A for root
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Drives: HDD Total Size: 532.2GB (2.3% used)
Weather: Conditions: 36 F (2 C) - light showers rain mist Time: November 9, 12:08 PM EST
Info: Processes: 115 Uptime: 41 min Memory: 153.9/5896.3MB Client: Shell (bash) inxi: 2.3.8

This is installed to and boots from a sdhc card.

The hard drive has Manjaro installed with the newest kernel 4.19.1, Manjaro
can't run Nexuiz 242 but bionicpup64 7.9.6 can

[rerwin]

Terry H,
Thank you for sending me the bootsysinit log. I see that your network ID is seventh in a list of 34. There seems to be a lot of unnecessary processing going on just to find the connection information for your network (ESS) ID.

I have updated the trace version of rc.network to include what could be a fix to find the ID more quickly:

http://www.murga-linux.com/puppy/viewto ... 63#1009363

Please try it and send me the resultant bootsysinit.log file, again.

And anyone else in an area of an extreme number of available wifi networks, please try the newer rc.network.
Richard

[Terry H]

Terry H,
Thank you for sending me the bootsysinit log. I see that your network ID is seventh in a list of 34. There seems to be a lot of unnecessary processing going on just to find the connection information for your network (ESS) ID.

I have updated the trace version of rc.network to include what could be a fix to find the ID more quickly:

http://www.murga-linux.com/puppy/viewto ... 63#1009363

Please try it and send me the resultant bootsysinit.log file, again.

And anyone else in an area of an extreme number of available wifi networks, please try the newer rc.network.
Richard

I live in a condominium building, there are lots of wifi networks here. Will be testing shortly.

[sheldonisaac]

To set up a test run, copy the rc.network.gz file into /usr/local/simple_network_setup/, rename the original rc.network to something else (like rc.network.bak), then click on rc.network.gz to unzip it. Give the resultant rc.network file execute permissions, if it does not already have them.

The test is to now reboot to the same pupsave, note how long it takes to connect, then save a copy of /tmp/bootsysinit.log somewhere. Please post or PM me that bootsysinit.log as an gzipped attachment.

Richard, I downloaded the rc.network which says

EDIT 11/9/18: Added potential fix for slow connection where the desired wifi network is later in the list of available networksFor tracing SNS boot-up.
Includes experimental fix for slow connection at boot-up with
many available wifi networks.

even though I had no problem with the one that was there already,

Code: Select all

-rwxr-xr-x 1 root root 17710 Oct 23 12:27 orig-rc.network
-rwxr-xr-x 1 root root 18326 Nov  9 20:28 rc.network

Oh, this is in Bionicpup64 7.9.6

I rebooted; it worked fine, and I've PMed the bootsysinit.log.gz

[sheldonisaac]

Help, please. The up-arrow key on this Dell E6410 laptop starts mtpaint, rather than the expected actions: eg, command history in terminal, go up a line in text editng, .. Thanks for any help.
---------------
EDIT: Apologies. As has happened many times, I guess I saved something that caused the problem.

I "solved" it by starting over, made a new save folder. Don't know what was wrong with the previous one.

Linux puppypc5281 4.14.79-u64oz #1 SMP PREEMPT Fri Nov 9 16:39:26 AEDT 2018 x86_64 x86_64 x86_64 GNU/Linux

Sheldon

[Revolverve]

sheldonisaac

Thought up-arrow key starts mtpain problem was solved,
look at jwm-hotkeys keyboard shortcut ;exe:defaultscreenshot ...says print command here on .6

[sheldonisaac]

sheldonisaac

Thought up-arrow key starts mtpain problem was solved,
look at jwm-hotkeys keyboard shortcut ;exe:defaultscreenshot ...says print command here on .6

Thank you. See my edited post, above.

[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.....