Dpup Stretch 7.5 CE (RC-5)

[WiZard]

I have customized rc3 with wallpapers, documents, themes, directories, symlinks, programs and changed the wm to openbox/fbpanel.

This is the procedure I've used with other puppies

Remaster as follows:
-run standard remaster from menu
-at /tmp/root message (this section insures all my changes are included)
delete the contents of /tmp/root
copy contents of /root to tmp/root

-at /etc message (this section insures openbox/fbpael is used)
copy /etc/windowmanager to tmp/etc

The remaster boots fine with the changes, but when you right click the desktop it generates a "root-menu" not found message.

This was fixed as follows:
-at /etc message
copy /etc/xdg/menus to /tmp/etc/xdg/menus
copy /etc/xdg/openbox to /tmp/etc/xdg/openbox

Also found that a save file created by the remastered puppy does not load on reboot.

[sc0ttman]

How do I get Virtualbox working?

I'd really like to make VirtualBox work in RC3...

I am assuming the repo packages don't work, cos I couldn't make them work, and Puppy runs a different kernel than Debian...

(Currently I am running RC1 (IIRC) ... But I booted RC3 today, with devx and kernel sources SFS loaded..)

In RC3, I downloaded the i386 virtualbox .deb package from the homepage (about 63mb), and installed it..

I ran it, and it said I should run `vboxsetup` (or something), to build the kernel modules..

So I did ... but it couldn't build the kernel modules... It said the Linux headers files were not present...

I don't actually know what I am doing, so any guidance would be appreciated!

[radky]

I have customized rc3 with wallpapers, documents, themes, directories, symlinks, programs and changed the wm to openbox/fbpanel.

This is the procedure I've used with other puppies

Remaster as follows:
-run standard remaster from menu
-at /tmp/root message (this section insures all my changes are included)
delete the contents of /tmp/root
copy contents of /root to tmp/root

-at /etc message (this section insures openbox/fbpael is used)
copy /etc/windowmanager to tmp/etc

The remaster boots fine with the changes, but when you right click the desktop it generates a "root-menu" not found message.

This was fixed as follows:
-at /etc message
copy /etc/xdg/menus to /tmp/etc/xdg/menus
copy /etc/xdg/openbox to /tmp/etc/xdg/openbox

Also found that a save file created by the remastered puppy does not load on reboot.

Hi WiZard,

Thanks for testing rc3.

Today I remastered rc4 which is the upcoming release that includes multiple additional Woof-CE fixes to Puppy infrastructure.

Before the remaster, I followed your approach and switched to fbpanel/openbox.

Then during the remaster, at /etc message, I copied
1 - /etc/xdg/menus to /tmp/etc/xdg/menus
2 - /etc/xdg/openbox to /tmp/etc/xdg/openbox

After the remaster and subsequent manual frugal installation of the corresponding puppy_stretch_7.5.sfs, I booted the remastered rc4 without difficulty.

After making cosmetic changes to the desktop I created a non-encrypted savefile and rebooted. The savefile loaded correctly and all is well.

So, while testing the upcoming Dpup Stretch rc4, the /usr/sbin/remasterpup2 script is working OK for me.

[radky]

How do I get Virtualbox working?

I'd really like to make VirtualBox work in RC3...

I am assuming the repo packages don't work, cos I couldn't make them work, and Puppy runs a different kernel than Debian...

(Currently I am running RC1 (IIRC) ... But I booted RC3 today, with devx and kernel sources SFS loaded..)

In RC3, I downloaded the i386 virtualbox .deb package from the homepage (about 63mb), and installed it..

I ran it, and it said I should run `vboxsetup` (or something), to build the kernel modules..

So I did ... but it couldn't build the kernel modules... It said the Linux headers files were not present...

I don't actually know what I am doing, so any guidance would be appreciated!

Hi sc0ttman,

I have no experience with virtualbox, but after installing the i386 virtualbox .deb package you could try the following in a terminal to build the VirtualBox kernel modules.

Code: Select all

/etc/init.d/vboxdrv setup

For me, the above code returns the following:

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.

At this point, the following kernel modules are created and loaded (go to Menu -> System -> Pup-Kview to view the loaded modules):

vboxdrv - Oracle VM VirtualBox Support Driver
vboxnetadp - Oracle VM VirtualBox Network Adapter Driver
vboxnetflt - Oracle VM VirtualBox Network Filter Driver
vboxpci - Oracle VM VirtualBox PCI access Driver

Also, you may have to add something like the following line to /etc/group:

vboxusers1001:

---

Now, when I run VirtualBox in a terminal, I see the following:

Code: Select all

VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: libQt5X11Extras.so.5: cannot open shared object file: No such file or directory

So, it seems VirtualBox requires Qt5.

At this point, you can go to ROX-Filer and right-click /usr/lib/virtualbox, then select ListDD to show the missing Qt5 libs (see screenshot below).

Hopefully, the above will be helpful as you add the requisite libraries for VirtualBox.

[norgo]

...it seems VirtualBox requires Qt5.

yes, qt5 is needed to run virtualbox ( but should be already included by default )
please note: built-in qt5 libs are not located in default search path

you should find them under /opt/VirtualBox/
( in case of default installation without user specific prefix )

update:

@sc0ttman
Hi scotty, I created a kernel-module-package K 4.9.101-PAE for usage of virtualbox-5.1.10-112026
please install the kmp before you load the virtualbox SFS. So Virtualbox detect the kernelmodules automatically.

@radky
I'm really very impressed of your Dpup Stretch 7.5 CE ( very good job)

A little note:
the name of the folder for kernel modules is not a good choice.
why ?
as example the kmp for virtualbox
where should I put the modules ?
other distributions with the same kernel version most probably doesn't own a 4.9.101-stretch folder
simply the kernel version would be better in my opinion

Nevertheless very good distro

[WiZard]

@radky

Thanks for the confirmation on remastering, I use a small script file to make all my adjustments. I'll test it again on rc4 and if it runs correctly I'll upload it with some instructions for anyone whose interested.

wiz

[s243a]

I noticed that the package manager says that util-linux is installed but it's not.

I wanted it for the lscpu command. Fortunately, it lets me install it even though it said it was installed.

I'm not sure whether the package manager saying that it was installed was intentional or not.

[radky]

s243a wrote:
I noticed that the package manager says that util-linux is installed but it's not.

Hi s243a,

While checking a pristine installation of Dpup Stretch 7.5 RC4 (not yet released), I see the util-linux package (/root/.packages/woof-installed-packages/util-linux_2.29.2-1+deb9u1) and associated lscpu binary (/usr/bin/lscpu) are already installed. I'm not sure why the /usr/bin/lscpu binary is missing in your installation of RC3

---

norgo wrote:
the name of the folder for kernel modules (such as /lib/modules/4.9.101-stretch) is not a good choice.

Hi norgo,

To simplify kernel nomenclature for 3rd-party pets such as VirtualBox, I could provide a basename link to the stretch kernel (see image below).

[norgo]

I could provide a basename link to the stretch kernel (see image below).

good idea, thanks

[perdido]

Hi,

Anyone know where to get the kernel headers for kernel 4.1.48?
Thanks!

.

[watchdog]

Anyone know where to get the kernel headers for kernel 4.1.48?

http://smokey01.com/radky/Woof/

[perdido]

Anyone know where to get the kernel headers for kernel 4.1.48?

http://smokey01.com/radky/Woof/

Hi watchdog

Got all those but can't find the headers is any of them???

Edit: ended not needing the kernel headers to compile a wifi driver.
I still don't see them in either the devx, kernel sources or the fdrv sfs files.

.

[watchdog]

I do not know much about this technical question. In puppy the kernel sources sfs is all I have ever used to compile drivers: I suppose it is intended to contain the headers of the kernel and all you need to compile drivers. I never installed headers of the kernel standing alone. Any puppy comes only with the base iso, the devx sfs to compile and the kernel sources sfs to compile drivers.

[sc0ttman]

Was just testing my Stretch 7.5 dotfiles in RC3...

The following package should probably be installed by default:

ncurses-term_6.0+20161126-1+deb9u2

Without it, when I set $TERM to a 256 color setting, like xterm-256color (or mlterm-256color in my case),
then it causes errors... Typing 'clear' and hitting enter might bring up the error msg...

Without being able to set a term to 256 colours, editors like Vim and Micro dont work as expected, and code
highlighting by programs like ranger, Pygments, bat (and others) dont work..


...Long story short, I installed ncurses-term_6.0, then set TERM=mlterm-256color ..
And now my terminal programs work OK again...

[Keef]

perdido

In the kernel source sfs, the headers are in :

/usr/src/linux/include/
/usr/src/linux/usr/include/

[perdido]

perdido

In the kernel source sfs, the headers are in :

/usr/src/linux/include/
/usr/src/linux/usr/include/

Thanks Keef !

.

[cthisbear]

radky:

Any chance of including drivers for

Simplecom NW601 Wireless USB in upcoming Stretch

http://murga-linux.com/puppy/viewtopic. ... 53#1008253

Solved twice in that link.

Chris.

[radky]

sc0ttman wrote:
The following package should probably be installed by default:

ncurses-term_6.0+20161126-1+deb9u2

http://murga-linux.com/puppy/viewtopic. ... 25#1008425

Hi sc0ttman,

I will add ncurses-term_6.0+20161126-1+deb9u2 to RC4.

---

cthisbear wrote:
Any chance of including drivers for

Simplecom NW601 Wireless USB in upcoming Stretch

http://murga-linux.com/puppy/viewtopic. ... 15#1008415

Hi cthisbear,

From perdido's rtl8812au-5.1.5_k4.1.48.pet I will include the following in the 4.1.48 iso of RC4:

/lib/modules/4.1.48/kernel/drivers/net/wireless/8812au.ko

Thanks

[cthisbear]

radky is a winner, as are all the Puppy helpers
here on Murga.

Cheers.....Chris.

[sc0ttman]

Hi radky,

Just a follow up on virtualbox... I booted a fresh RC3 and tried following your instructions as I understood them:

1. I used "SFS Load on-the-fly" to load the "kernel-sources-4.9.131-stretch.sfs" and the devx

2. I installed the VirtualBox .deb from their website for i386

3. I run the command you gave me ... But I got...

Code: Select all

# /etc/init.d/vboxdrv setup
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.

Not sure what I am doing wrong.. Probably something dumb..

Thanks for the ListDD tip... I hadn't seen that!

BTW, if Pkg is installed, you can also do this in the terminal:

pkg ldd <pkgname>

(where <pkgname> is an installed package:)

Code: Select all

# pkg ldd virtualbox
Searching for missing dependencies.. Please wait.
WARNING: virtualbox-5.2 has missing dependencies:
  /usr/lib/virtualbox/VBoxTestOGL:
    libQt5Core.so.5 => not found
  libQt5OpenGL.so.5 => not found
  libQt5Widgets.so.5 => not found
  /usr/lib/virtualbox/kchmviewer:
    libQt5Core.so.5 => not found
  libQt5Gui.so.5 => not found
  libQt5Widgets.so.5 => not found
  libQt5PrintSupport.so.5 => not found

... which is probably broken.. so I might steal your ListDD code for Pkg
----

norgo, thanks for the info, I will try your instructions and downloads next time round to see if that works..

-----

I really would like to know how to build the modules myself tho...
Just to know what I'm doing wrong and learn something..

Ideally I wanna build a headless-only Vbox package, and just use vbox,sh to manage the VMs ...
.. then re-build it on different pups..

Cheers