Bionicpup64 8.0 CE

[amn87]

Brightness and Volume controls not working

If this is a laptop computer and you are talking about the buttons/keys on the laptop.
That is kind of normal, the option keys not working on laptops.
Bionicpup has programs for controlling those things.

I assume some operating system will boot and run OK on this computer.

This is the kind of issues you get if the install to the USB drive is just a bad install.
I would try it over fresh.

A clean new download of the Bionicpup64 8.0 iso

A fresh new format of the USB drive partition.
Rufus may do this for you.
If not, use a program that can format a partition.
Probably needs to be formatted fat 32 for Rufus to use it.

Using newly fresh Bionicpup iso, freshly formatted USB drive, and Rufus.
Install Bionicpup to the USB drive.

Any help?

Yes its a laptop specifically Acer Nitro 5. I totally forgot to mention it. Yes I use Rufus and Etcher. I have tried several times. Rufus reports everytime that there's no issue. I don't think its a bad download as in VMWare/Virtualbox it works well. Plus the MD5 checksums match.
Bionicpup32 while having the same issues with brightness and volume controls is a tad better as I can restart/shutdown reliably. Save files aren't an issue either. I would happily use it if it weren't for the 64-bit requirement for Chrome. I have attached a copy of the System Info from it.
Windows 10 is the main OS. I have tested Ubuntu 17.04,Lubuntu 19.04 and Bodhi Linux latest all of which work well.
TouchPad doesn't work in both x32/x64 flavors. The fn combo buttons don't work. UEFI with Secure Boot disabled.
My ancient Core 2 Duo laptop didn't have any problem with myriad Puppy versions. Of course I didn't get to test it with Bionicpup...

[bigpup]

I don't think its a bad download as in VMWare/Virtualbox it works well. Plus the MD5 checksums match

.
Are you saying that Bionicpup64 8.0, used in this way, on the exact same laptop, works with no problem?
Only if you boot from a install on a USB drive it has issues?

[amn87]

I don't think its a bad download as in VMWare/Virtualbox it works well. Plus the MD5 checksums match

.
Are you saying that Bionicpup64 8.0, used in this way, on the exact same laptop, works with no problem?
Only if you boot from a install on a USB drive it has issues?

Yes. In a VM the same iso works well. But if I boot from USB using the same iso all sorts of problems occur. Even more surprisingly Bionicpup32 has fewer issues.

[bigpup]

That seems to say something is wrong with the USB drive.

Have you tried to completely reformat the USB drive and do a fresh new install of Bionicpup?
Reformatting is the import part.
That should make sure fragmented file system is not causing this problem.

Just to try other possible causes.
Try plugging the USB drive into a different USB port.
Never know, check both the USB drive plug and the computers USB port for dirty or bent contacts.

[amn87]

That seems to say something is wrong with the USB drive.

Have you tried to completely reformat the USB drive and do a fresh new install of Bionicpup?
Reformatting is the import part.
That should make sure fragmented file system is not causing this problem.

Just to try other possible causes.
Try plugging the USB drive into a different USB port.
Never know, check both the USB drive plug and the computers USB port for dirty or bent contacts.

Other Linux ISOs work just fine. Rufus anyways formats the drive everytime. I will try with a fresh download with a different USB drive. Thanks for your inputs.

[linuxcbon]

Bionicpup64 8.0 CE with latest updates.
Some minor issues but worth to correct :
------------------------------------
Module 'pcspkr' is launched several times :
bootkernel.log
Error: Driver 'pcspkr' is already registered, aborting...
(...)
Error: Driver 'pcspkr' is already registered, aborting...
------------------------------------
bootsysinit.log
/etc/rc.d/rc.sysinit: /etc/rc.d/rc.local: line 11: can't create /sys/bus/usb/devices/usb7/power/wakeup: nonexistent directory
/etc/rc.d/rc.sysinit: /etc/rc.d/rc.local: line 12: can't create /sys/bus/usb/devices/usb8/power/wakeup: nonexistent directory
/etc/rc.d/rc.sysinit: /etc/rc.d/rc.local: line 13: can't create /sys/bus/usb/devices/usb9/power/wakeup: nonexistent directory
/etc/rc.d/rc.sysinit: /etc/rc.d/rc.local: line 14: can't create /sys/bus/usb/devices/usb10/power/wakeup: nonexistent directory
------------------------------------
Xorg.0.log
[ 48.219] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
------------------------------------
I have to start dhcpcd manually, even if it was already called before in the init.
------------------------------------
In folder /root/.cache/ , there are many files event-sound-cache.tdb.****
It seems that one new is created at each boot.
So why not delete the old ones at boot ?
------------------------------------
Same for folder /root/.dbus/session-bus/ , there are many files no more used. No cleanup at bootup ??

[bigpup]

666philb,

Are you sure that new Nvidia 430 driver in Quickpet is complete?
Does not work for me.
The 410 driver pet is 152M
The 430 driver pet is 94M

Never usually see a newer Nvidia driver package smaller than the older one????

[666philb]

666philb,

Are you sure that new Nvidia 430 driver in Quickpet is complete?
Does not work for me.
The 410 driver pet is 152M
The 430 driver pet is 94M

Never usually see a newer Nvidia driver package smaller than the older one????

hi bigpup
the pet is smaller as it's compressed using xz rather than gz. however, when i tried extracting it with uextract it showed an error (although it did extract).
i've re-uploaded the .pet now with gz compression http://distro.ibiblio.org/puppylinux/pe ... x86_64.pet

[bigpup]

Thanks for the quick response!

I will try the new upload pet.

That new pet of Nvidia 430 driver worked.

Wonder if something is wrong with xz compression in Bionicpup64 8.0
xz (XZ Utils) 5.2.2
liblzma 5.2.2

The latest stable is xz 5.2.4
https://tukaani.org/xz/

[666philb]

Bionicpup64 8.0 CE with latest updates.
Some minor issues but worth to correct :
------------------------------------
Module 'pcspkr' is launched several times :
bootkernel.log
Error: Driver 'pcspkr' is already registered, aborting...
(...)
Error: Driver 'pcspkr' is already registered, aborting...
------------------------------------
bootsysinit.log
/etc/rc.d/rc.sysinit: /etc/rc.d/rc.local: line 11: can't create /sys/bus/usb/devices/usb7/power/wakeup: nonexistent directory
/etc/rc.d/rc.sysinit: /etc/rc.d/rc.local: line 12: can't create /sys/bus/usb/devices/usb8/power/wakeup: nonexistent directory
/etc/rc.d/rc.sysinit: /etc/rc.d/rc.local: line 13: can't create /sys/bus/usb/devices/usb9/power/wakeup: nonexistent directory
/etc/rc.d/rc.sysinit: /etc/rc.d/rc.local: line 14: can't create /sys/bus/usb/devices/usb10/power/wakeup: nonexistent directory
------------------------------------
Xorg.0.log
[ 48.219] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
------------------------------------
I have to start dhcpcd manually, even if it was already called before in the init.
------------------------------------
In folder /root/.cache/ , there are many files event-sound-cache.tdb.****
It seems that one new is created at each boot.
So why not delete the old ones at boot ?
------------------------------------
Same for folder /root/.dbus/session-bus/ , there are many files no more used. No cleanup at bootup ??

hi linuxcbon,

the pcspkr thing is probably kernel related

the /etc/rc.d/rc.sysinit: /etc/rc.d/rc.local: line 11: can't create /sys/bus/usb/devices/usb7/power/wakeup: nonexistent directory errors are there as your machine doesn't have that many usb ports and is harmless. without the wakeup call to usbs they can sometimes not work after suspend

/var/run/dbus/system_bus_socket: No such file or directory) this is created after xorg initializes ... so just the single error. might be worth bringing up on woof

I have to start dhcpcd manually, even if it was already called before in the init. i have a similar problem on my desktop hardware. on all my other computers it's fine. i've ended up using frisbee, but i'll bring it up on woofce

same for the event-sound-cache.tdb.

cheers

[mouldy]

Same result. So maybe something wvdial depends on rather than wvdial itself? I guess nobody else uses wvdial for tethering or dialup for that matter, so I can live with PPP and pon/poff. That works fairly well and I created shortcut script for pon and link for poff on desktop so only have to click pon and wait until I get the little cell phone down in the tray.

hi mouldy,

maybe it's wvstreams that also needs changing ... try both wvdial & wvstreams from the ppm (make sure to get the ubuntu versions).

bionicpups wvdial & streams are old .pets, possibly from tahrpup

if still no luck, have a go with slackos ones again http://distro.ibiblio.org/puppylinux/pe ... cko6414.2/

Apparently PPM wont just overwrite existing package. Not really sure how other than hunting down and manually uninstalling individual files how you delete a builtin package on full install Puppy.

Today I was fooling around with frugal install and used "Remove builtin pkgs" tool in menu. This removed wvdial and wvdialstream though PPM wasnt aware they werent installed. But connected via PPP, I told PPM to install wvdial anyway. Didnt even bother updating first. It did install wvdial plus the wvstream dependencies. NOW I can connect via Pupdial or Wvdial.

May help somebody.

[linuxcbon]

hi linuxcbon,

the pcspkr thing is probably kernel related

the /etc/rc.d/rc.sysinit: /etc/rc.d/rc.local: line 11: can't create /sys/bus/usb/devices/usb7/power/wakeup: nonexistent directory errors are there as your machine doesn't have that many usb ports and is harmless. without the wakeup call to usbs they can sometimes not work after suspend

/var/run/dbus/system_bus_socket: No such file or directory) this is created after xorg initializes ... so just the single error. might be worth bringing up on woof

I have to start dhcpcd manually, even if it was already called before in the init. i have a similar problem on my desktop hardware. on all my other computers it's fine. i've ended up using frisbee, but i'll bring it up on woofce

same for the event-sound-cache.tdb.

cheers

hi 666philb,

can you bring up these issues in woofce too ?
- pcspkr is called how many times in init scripts or somewhere ?
- /etc/rc.d/rc.local can stop at usb6 ?
- can they add this cleanup in rc.sysinit to avoid the folders full of old files ?
rm /root/.cache/event-sound*
rm /root/.dbus/session-bus/*

cheers

[TiredPup]

I installed the RTL8821CE driver obtained from Quickpet. It works quite well on my HP laptop. Thank you very much.

[bigpup]

UExtract 3.38
http://www.murga-linux.com/puppy/viewtopic.php?t=87864
New updated version of UExtract with these changes:

- can extract BurpSuite auto-installer
- minor fixes and improvements
- new formats/extensions:

.apz (Autoplay Media Studio Exported Project) [unzip|7z]
.arduboy (Arduboy Game Package) [unzip|7z]
.asd (ASD Compressed Archive) [(un)asd]
.baklz4 (Compressed Firefox Recovery Backup File) [lz4jsoncat]
.bdoc (Binary DigiDoc Signature File) [unzip|7z]
.ctb (Cherrytree SQLite Document) [sqlite3|fossil]
.ctx (Cherrytree Password-protected SQLite) [7z]
.ctz (Cherrytree Password-protected XML) [7z]
.db & .db3 (same as .sqlite & .sqlite3) [sqlite3|fossil]
.dz (Dzip Compressed Archive) [dzip]
.ecsbx (Error-Correcting SeqBox Container File) [blkar]
.f3d (Fusion 3D Design) [unzip|7z]
.f3z (Fusion 360 Shared Project Archive) [unzip|7z]
.fb2k-component (Foobar2000 Component) [unzip|7z]
.fzbz (Fritzing Bundled Bin File) [unzip|7z]
.fzpz (Fritzing Bundled Part File) [unzip|7z]
.fzz (Fritzing Shareable Project File) [unzip|7z]
.gmz (Compressed GameMaker File) [7z]
.libzip (Camtasia Studio Zipped Library File) [unzip|7z]
.lpkg (Liferay Application) [unzip|7z]
.mbz (Moodle Backup File) [g(un)zip+tar]
.mpkg (Meta Package File) [xar|7z]
.opk (GCW Zero Open Package) [unsquashfs]
.pbi (PC BSD Installer Package) [7z+tar]
.pxz (Pixz XZ Compressed File) [(un)xz]
.qch (Qt Compressed Help File [sqlite3|fossil]
.rp9 (RetroPlatform Disk Image Archive) [unzip|7z]
.sbx (SeqBox Container File) [blkar]
.tpxz (Pixz XZ Compressed Tar Archive) [(un)xz+tar]
.tcx (TestComplete Script Extension Package) [unzip|7z]
.wa (Windows Addon Archive) [7z]
.xmcdz (Mathcad Compressed Worksheet File) [g(un)zip]
.xx & .xxe (XXEncoded File) [xxdecode]
.zi_ (Renamed ZIP) [unzip|7z]

[666philb]

quickpet updates

thanks mouldy ... updated wvdial & wvstreams
thanks bigpup & sfr ... updated uextract
fixed rpm install & extract ... needed ubuntus rpm2cpio and librpm

[666philb]

also added fsearch to the repo, this is a bit like 'everything' search that can be installed on windows. start typing and you get instant search results.

i'll add it to quickpet once it's synced with nluug

[escucha]

FSearch is a handy tool, thanks Phil.
It turns search work into rapid find when database is on.
Will use often.

[666philb]

added gatotray to the repo.
a handy tray app that shows cpu usage, memory usage, disc io and temperature.

[haywirepc]

Running bionicpup 64 8.0
I install and use xfce and compiz from repos.

When you use the pupshutdown menu from the xfce start menu, it starts, but when you press reboot or shutdown for example, the panels disappear then nothing happens. I thought it was just the computer I was on, but I copied my save file and same thing happens on every pc I tried.

Does anyone know a fix for this?

[666philb]

Running bionicpup 64 8.0
I install and use xfce and compiz from repos.

When you use the pupshutdown menu from the xfce start menu, it starts, but when you press reboot or shutdown for example, the panels disappear then nothing happens. I thought it was just the computer I was on, but I copied my save file and same thing happens on every pc I tried.

Does anyone know a fix for this?

hi haywirepc,

i think this is fixed now .... quickpet >>> bionicpup updates ... to test