Bionicpup64 8.0 CE

[artsown]

7.9.7 with bugfixes looks good here. Can't say about bluetooth though
since I have never used it.

Art

[petihar]

Hello 666philb

Terry H wrote :

Several attempts to pair phone to laptop. I could see (scan on) phone from laptop, I attempted to pair, got pair message on phone, clicked 'Allow', phone was connected for a few seconds then disconnected.
Once again totally frustrated with bluetooth.

It's the same for me. Then I tried after installing blueman which offers an easier graphical interface. The result is of course the same!

[rerwin]

I found a problem with selecting a pupsave file that seems unique to bionic64 pup. It is the only puppy whose name makes it so that its pupsave files occur first in the puppy directory, ahead of the puppy SFS files.

In that case, the prompt for selection of a pupsave file appears but does not accept the keyboard input of the number! It does not respond to the key-press and requires pressing the power switch to shut down the PC.

I am sure this is a woofCE issue, but mention it here to see if others see the same behavior.

[666philb]

Hello 666philb

Terry H wrote :

Several attempts to pair phone to laptop. I could see (scan on) phone from laptop, I attempted to pair, got pair message on phone, clicked 'Allow', phone was connected for a few seconds then disconnected.
Once again totally frustrated with bluetooth.

It's the same for me. Then I tried after installing blueman which offers an easier graphical interface. The result is of course the same!

EDIT: aaarg ... i missed something in janky_bt, for a phone edit /usr/local/janky_bt/startnetwork and add your phones device number here ......
dev_DC_F0_90_2F_01_C5 (<your device)

i think that you are both good up to this point, once paired it's normal to say connected for a few seconds then disconnected. At this point with a phone, turn on bluetooth tethering in the phones settings (it won't connect unless this is on), then click 'tether to phone' in janky_bt. it may then connect automatically, if not then try connecting in 'bluetoothctl' connect DC:F0:90:2F:01:C5 (<your device)
if this fails try 'repeating the above
Once connected 'bnep0' interface should be available in frisbee & network
wizard.

for the speaker once paired , you need to 'add speaker' in janky_bt (make sure to save) and then 'connect to speaker' in janky_bt. you should then be able to connect in bluetoothctl connect 00:12:6F:AD:14:7C (<your device)
once connected run programs with

Code: Select all

ALSAPCM=pcm.puppybt palemoon
ALSAPCM=pcm.puppybt deadbeef
ALSAPCM=pcm.puppybt kodi

if it still won't connect .. double check /etc/asound.conf has your device, and repeat the above.
another thing to try is in bluetoothctl remove 00:12:6F:AD:14:7C (<your device) and re pair it
BTW blueman may have messed up your bluetooth installation i would uninstall it and click on updates again in quickpet.
whilst i finally got blueman to be able to connect to a phone, connecting to a speaker was impossible as it requires pulseaudio

[666philb]

I found a problem with selecting a pupsave file that seems unique to bionic64 pup. It is the only puppy whose name makes it so that its pupsave files occur first in the puppy directory, ahead of the puppy SFS files.

In that case, the prompt for selection of a pupsave file appears but does not accept the keyboard input of the number! It does not respond to the key-press and requires pressing the power switch to shut down the PC.

I am sure this is a woofCE issue, but mention it here to see if others see the same behavior.

hi rerwin,

this happens because of a missing builtin keyboard module in the kernel.
it'l hopefully be added in the next build

[666philb]

double post

[rerwin]

this happens because of a missing builtin keyboard module in the kernel.
it'l hopefully be added in the next build

Thanks for the explanation. My workaround for this is to add another type of file before the first pupsave in the directory. Then pupsave selection works normally.

[Billtoo]

I changed kernels, (compiled 4.14.86 with woof-ce kernel kit, from my
bionicpup64 7.9.6 install)

root# sh VulnChecker
l1tf Mitigation: PTE Inversion
meltdown Mitigation: PTI
spec_store_bypass Vulnerable
spectre_v1 Mitigation: __user pointer sanitization
spectre_v2 Mitigation: Full generic retpoline, STIBP: disabled, RSB filling
root#

The WM-Switcher still doesn't work, but CTRL-Backspace to get to the
commandline then doing "xwin xfce4-session" no quotes get me there
after doing a couple of other steps.

I've forgotten all that I tried to get xfce4 working but it's useable now

Thanks.

[Billtoo]

After hammering on my previous bionicpup64 7.9.7 install I decided to
do a fresh install:

System: Host: puppypc25869 Kernel: 4.14.86 x86_64 (64 bit) Desktop: JWM 2.3.7 Distro: bionicpup64 7.9.7
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: 1350/2500 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] RV530 [Radeon X1600 PRO]
Display Server: X.org 1.19.6 driver: radeon tty size: 147x28 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 (1.1% used)
Weather: Conditions: 21 F (-6 C) - Scattered Clouds Time: December 7, 1:03 PM EST
Info: Processes: 97 Uptime: 14 min Memory: 172.8/3952.0MB Client: Shell (bash) inxi: 2.3.8

I added all the same applications including xfce4, changed the kernel
first.
Still have problems getting xfce4 to run, it will but the first mouse
click gives a screen with jwm background and nothing else.

Thanks.

EDIT: I left it for a few hours, booted up again to JWM, used the WM switcher to xfce4, rebooted 4 times and xfce4 comes up each time, it healed itself yippee

[gyro]

this happens because of a missing builtin keyboard module in the kernel.
it'l hopefully be added in the next build

Thanks for the explanation. My workaround for this is to add another type of file before the first pupsave in the directory. Then pupsave selection works normally.

This doesn't make sense.
If the problem is a missing module, it can't be fixed by adding an extra file.
And if there is a missing module, it should be fixed by "initmodules" during first-boot, so the keyboard should work on second boot.

[later edit]
Sorry rerwin, I can't replicate the problem, with a fresh install.

gyro

[ITSMERSH]

Hi.

Just for your interest.

I have created a short 3m50s video showing BionicPup64 7.9.6, Qtractor 0.8.5 plus some u-he VST plugins in action.

The Video

[bigpup]

This is still a problem in v7.9.7
I know you said you reported this to Woof-CE, but!

Bionicpup64 7.9.7
Frugal using save folder.
HP 14 Chromebook

Menu>Setup>Mouse/Keyboard Wizard>Advanced Configuration>Keyboard Model

When I click on Keyboard Model
I get this error message
see attached image

I fixed this by editing xorg.conf.
/etc/X11/xorg.conf
In this section of xorg.conf several items are blocked by using # at start of entry line.
Remove the # and save changes.

This section of xorg.conf now looks like this:

Code: Select all

Section "InputClass"
	Identifier "keyboard-all"
	MatchIsKeyboard "on"
	MatchDevicePath "/dev/input/event*"
	Driver      "evdev"
	Option     "XkbRules" "evdev"
	Option     "XkbModel" "pc104" #xkbmodel0
	Option      "XkbLayout" "us"
	Option     "XkbVariant" "" #xkbvariant0
	Option      "XkbOptions" "terminate:ctrl_alt_bksp" #xkboptions0

[ITSMERSH]

Hi.

I'm still using 7.9.6 but I didn't download the 7.9.6 devx. Later I downloaded the 7.9.7 devx, but this has lots of dead symbolic links.

I tried to compile Xournal, but had to fix 3 of those dead symbolic links before my attempt of compiling Xournal was successful.

Is this caused by the devx itself or by the use of 7.9.6?

Thanks

[Billtoo]

I installed to the hard drive of my Acer laptop:

I changed the kernel and installed applications with PPM:

root# inxi -bw
System: Host: puppypc30856 Kernel: 4.14.87 x86_64 bits: 64 Desktop: Xfce 4.12.3 Distro: bionicpup64 7.9.7
Machine: Device: laptop System: Acer product: Aspire V5-571P v: V2.17 serial: NXM49AA03531512EC36600
Mobo: Acer model: Aspire V5-571P v: V2.17 serial: NBM491100831501E946600
UEFI [Legacy]: Phoenix v: V2.17 date: 02/27/2013
Battery BAT0: charge: 27.3 Wh 98.1% condition: 27.8/37.0 Wh (75%)
CPU: Dual core Intel Core i3-3227U (-MT-MCP-) speed/max: 1033/1901 MHz
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller
Display Server: X.Org 1.19.6 driver: intel Resolution: 1366x768@60.10hz
OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile version: 4.2 Mesa 18.0.5
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Card-2: Broadcom Limited BCM43228 802.11a/b/g/n driver: bcma-pci-bridge
Drives: HDD Total Size: 500.1GB (1.1% used)
Weather: Conditions: 34 F (1 C) - Partly Cloudy Time: December 9, 3:19 PM EST
Info: Processes: 142 Uptime: 35 min Memory: 622.3/5764.8MB Client: Shell (bash) inxi: 2.3.56
root#

The touchscreen is working.
I have another partition waiting for bionicpup64 final when it comes
out

Thanks.

[Revolverve]

An sfs of synthesizer-v-technical-preview for plain pure fun.

[ITSMERSH]

Hi.

Is there a working pngtopam package, so icon_switcher would work with pngoverlay.sh instead of pngoverlay (which needs X running)?

[torgo]

Great stuff as always, Phil.

Bionic64 is working great, even on a Socket AM1-based system (Asrock AM1H-ITX motherboard) where Xenial64 couldn't find a graphics driver.

(Tahr64 worked on that machine and chose the ati driver by default. Bionic64 chooses the radeon driver.)

I had been using Ubuntu rather than Puppy for the last couple of years but am migrating back to frugal installations of Puppy. This Bionic64 already looks like it's going to be an outstanding OS for many, many years to come.


One quirk I found: when using Quickpet to try to download the 32-bit compatibility SFS, it fails saying the link is broken and the file isn't found at any of the mirror sites. I downloaded it from ibiblio via the web, so it's there - just something odd with the link.



Other item that might be of interest to someone out there: the pet for Waterfox in the Xenial64 repository works fine in Bionic64. But it's an older version, and it won't quite update all the way to the most recent version (56.2.5). Instead it goes to a slightly earlier version (56.2.3) and then claims it's fully up to date. There were comments on the Waterfox blog from people having auto-update problems with 56.2.4, so it's a known issue. Seamonkey also tells you up front that older versions won't automatically update to the new one, so maybe it's a related (or intentional) thing.

But you can download the latest Waterfox tar.bz2 file and simply replace everything in /opt/waterfox with the contents of the downloaded archive file. It works just fine.

[ally]

I've reverted back to xenial64 as I cannot live with the font tearing when running chrome 57 (to avoid spot), chrome 70 does not exhibit this problem but the bulk downloading I do through the browser is a pain with spot enebaled

also, the mouse speed on my lenovo thinkpads goes berserk, hyper sensitive

the settings are the same as xenial and even with the values reduced to 1 in pupx it's almost unusable

[artsown]

@torgo
I'm glad you mentioned that waterfox sticks at 56.2.3
Since it's my default browser on six pups, I did a bit of work this morning
manually updating to 56.2.5 BTW, Basilisk is another very capable
alternative.

Art

[bigpup]

One quirk I found: when using Quickpet to try to download the 32-bit compatibility SFS, it fails saying the link is broken and the file isn't found at any of the mirror sites. I downloaded it from ibiblio via the web, so it's there - just something odd with the link.

Same for me.
Bionicpup64 7.9.7