The officially official Devuan Forum!

You are not logged in.

#1 Re: Devuan » Debian has fallen. What now? » 2020-01-19 15:31:25

Hello:

Altoid wrote:

Hello:
The writing has been on the wall for a long time now.
And it's well past the time to heed the warning.

Just to reinforce what I wrote previously / further illustrate just what is going on Linux/MS wise, I invite members to check out this YouTube chat from almost two years ago by a chap called Lunduke.
https://www.youtube.com/watch?v=TVHcdgrqbHE

... and this other one.

https://www.youtube.com/watch?v=9MflUrykPaY

I think they are worth watching.
Of course, YMMV.

Cheers (?),

A.

#2 Re: Installation » installing nvidia drivers on ascii 2.1 » 2020-01-09 11:43:36

Hello:

steve wrote:

... edited my sources.list file ...

For those (more knowledgeable than I) able to opine, it would probably be important to see the contents/output of cat /etc/apt/sources.list.

Edit:

The output of cat /var/log/Xorg.0.log would be useful also.

Cheers,

A.

#3 Re: Installation » "Warning": Failed to connect to lvmetad » 2019-12-31 10:45:47

Hello:

turbo wrote:

Any suggestions ?

I have not come across this and from what I have read, if the system boots without issues, it is just a harmless warning.
Maybe someone else knows better.

Cheers,

A.

#4 Re: Devuan » Debian has fallen. What now? » 2019-12-29 13:52:44

Hello:

fsmithred wrote:

It could have been worse.

Indeed ...
But I fear that (eventually) it will get worse.
To me it's just a question of time.

Why?
Because not enough people are paying attention to what is going on.

I've clocked roughly 20+ years of MS software use, ~5 years as a regular -> advanced user, the rest as first -> second tier support and on-site hardware service when needed, all at the different places where I made a living and from home when out of a job.

So my background is not that of a coder/developer or packager but someone who started late but who has seen all this first hand as a privileged/advanced user, like many others here.

IMO, there is a striking parallel between systemd in Linux and the registry in Windows OSs.

Systemd in Linux brings back memories of my difficult transition from W3.11 to W95, with the end of the familiar and usually well documented *.ini files I understood (and could tweak when things went foul) to the obscure workings of *the registry*, which took me a few years to get a minimal hold of, basically through unending trial and error grief.

After a few years (W95 to XPSP3) I understood what it was all about: a developer sanctioned virus running inside the OS, constantly changing and going deeper and deeper into the OS with every iteration and as a result, progressively putting an end to the possibility of knowing/controlling what was going on inside your box/the OS as it became more and more obscure.

When systemd appeared in Debian (I was already running Ubuntu) and saw what and how it did it, I realised that systemd was nothing more than a registry class virus which was infecting the Linux ecosystem at the behest of the developers involved and the complicity or indifference of most of the others.

So I moved from Ubuntu to PCLinuxOS and then on to Devuan.

Paranoid?

No. Just strongly convinced that there are people both inside and outside IT that actually want this systemd takeover to happen and are quite willing to pay shitloads of money to push that agenda, Poettering being a prime suspect but surely not the only recipient.

I don't see this MS cozying up to / barging into Linux and areas of influence (GitHub acquisition, WSLinux (!), etc.) in various ways as a coincidence: these things do not happen just because or on a senior manager's whim.

What I do see (YMMV) is systemd being a sort of a putsch to generate a convergence Windows with or into Linux, which is not good for Linux and will be its undoing.

But there's really nothing new here: it's just the well known MSbrace at work.
It's been going on for more than 30 years.

And no, I don't have an answer to this problem.

But I do think that it would probably be a good thing that the awesome manpower behind all the Linux projects scattered out there team up to find common ground instead of everyone of them wanting to do their own thing while mindlessly waving the flag of choice, a flag which they are set to lose if they do not react fast enough.

The writing has been on the wall for a long time now.
And it's well past the time to heed the warning.

Of course, nothing but my $0.02 and as always, YMMV.

To all Dev1  members/guests: Have a Happy New Year 2020.

Cheers,

A.

#5 Re: Installation » Keyboard configuration issue » 2019-12-28 14:37:23

Hello:

HevyDevy wrote:

... does many things well ...

Like all the other mainsream desktops out there these days.

HevyDevy wrote:

... fails in some areas ...

I'd say far too many, but as I suffer its shortcomings I cannot be objective enough.

HevyDevy wrote:

... has the multi monitor display working well ...

Just like Mate or Cinnamon or Gnome (which I have not tried).
But that is probably because X is working reasonably well and when it does not, some *.orx/layouts get it fixed quick enough.

For example: I've been waiting years for Xfce to be able to line up/organise/keep the desktop icons where I bloody put them.
It's the one thing I miss from XP.

I have been seriously thinking about getting rid of Xfce once and for all but never get around to doing so, probably for fear of breaking my Devuan ASCI .

Cheers,

A.

#6 Re: Installation » Keyboard configuration issue » 2019-12-28 13:27:28

Hello:

HevyDevy wrote:

... put the command in your autostart file ...

Done.

Applications -> Settings -> Session and Startup -> Application Autostart -> Add

Name: keyboardmap (or whatever)
Description: sets kb layout (or whatever)
setxkbmap latam

Thank you very much for your help.

That this issue is still a problem after so many years is not a good omen, not for Xfce and certainly not for the Linux ecosystem.

Cheers,

A.

#7 Re: Installation » Keyboard configuration issue » 2019-12-28 12:52:49

Hello:

HevyDevy wrote:

... tried setxbmap as a workaround ...

Yes, it works.
I can set the layout with setxkbmap.

But it does not survive a reboot.
Where can I set it to make it permanent?

Thanks for your input

Cheers,

A.

#8 Re: Installation » Keyboard configuration issue » 2019-12-28 11:21:07

Hello:

Altoid wrote:

rant
This is the type of thing that gets on Linux users' nerves: a straightforward configuration glitch in something that (at this stage in Linux time) should not be happening.
After all, how long has Xfce been a desktop option?
/rant

The issue I am having with the keyboard settings in Xfce seems to be related to a well known bug from back in 2010.
Nine (9) years ago and counting ....

https://askubuntu.com/questions/66096/h … er-reboots

Like someone else posted on that thread:

... u understand now why linux share in desktops is ~1%
A simple stupid language switcher applet is bugged for years...

I'll see if I can make one of the workarounds (evidently considered a permanent fix by the developers) work for me.

Cheers,

A.

#9 Re: Installation » Keyboard configuration issue » 2019-12-27 21:13:46

Hello:

HevyDevy wrote:

... configure the keyboard with setxbmap ?

Hmm ...
What I want is to be able to configure it via the desktop settings like it should be done.
ie: Applications -> Settings -> Keyboard -> Layout

rant
This is the type of thing that gets on Linux users' nerves: a straightforward configuration glitch in something that (at this stage in Linux time) should not be happening.
After all, how long has Xfce been a desktop option?
/rant

So if it wants to use the system defaults (the previous setting), I guess I'll have to try setting the system defaults to what I want.

Any other ideas?

Thanks for your input.

Cheers,

A.

#10 Re: Installation » Keyboard configuration issue » 2019-12-27 13:00:36

Hello:

Head_on_a_Stick wrote:

... Xfce?

Yes.

Head_on_a_Stick wrote:

... desktop is overriding your configuration.

Thought that could be the case, so tried Applications -> Settings -> Keyboard -> Layout, un-checked Use system defaults and chose Generic 105-key PC (intl.) with Spanish (Latin American) layout and Spanish (Latin American, no dead keys) variant.

But no, no cigar.

Thanks for your input.

A.

#11 Installation » Keyboard configuration issue » 2019-12-26 16:40:39

Altoid
Replies: 12

Hello:

My Sun 7 keyboard went south, the second one this year.
Nice but not so trusty after all.

So I pulled an old Lenovo backup from the closet: KU-0225 / P/N: 41A5312
It's a standard 105-key Latin American layout keyboard.

But something is not right and I cannot figure out what it is.

I have set the layout with dpkg-reconfigure keyboard-configuration and my /etc/default/keyboard file reads accordingly.

# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.

XKBMODEL="pc105"
XKBLAYOUT="latam"
XKBVARIANT="nodeadkeys"
XKBOPTIONS="lv3:ralt_switch,compose:menu,terminate:ctrl_alt_bksp"

BACKSPACE="guess"

It seems that the keyboard configuration setting is being ignored and the keyboard is working as if it were a Spanish layout (like if it had a ç / Ç at the end of the third row).

eg: The key that should give me an accent ` or two types of brackets { or } and [ or ] gives me a ç or a Ç.

Rather annoying.

Any idea what might be happening here?

Thanks in advance,

A.

#12 News & Announcements » Merry Christmas » 2019-12-24 21:43:46

Altoid
Replies: 9

Hello:

A hearty season's geeting (Merry Christmas / other celebrations, etc.)  to all here at Dev1, especially to those who keep the Devuan project moving forward.

Cheers,

A.

#13 Re: Other Issues » [SOLVED] Apt-get show one package per line? » 2019-12-17 02:29:19

Hello:

golinux wrote:

... always been overwhelmed by the blob of text too.

+1

Yes, it is a pity.
Keeps me from being more confident in using apt-get.

Maybe maintainers could find a way to make the output (more) readable by default, like dnf?

A.

#14 Re: Installation » Refracta Snapshot VM mount points question. » 2019-12-07 15:15:10

Hello:

fsmithred wrote:

I use optical media, too.
... directories under /media that are needed get created automatically. I think udev takes care of that.

OK

fsmithred wrote:

... directories you made under /media, take a look at the rsync excludes ...
... comment out one or more of the following lines, as needed.
Like this:

#- /cdrom/*
#- /media/*

Do the same with /usr/lib/refractainstaller/installer_exclude.list

Great ...  =-)

fsmithred wrote:

To add a line to fstab in the installer, you just need to add this line:

echo -e "/dev/sr0\t/media/cdrom\tauto\tnoauto,owner,ro,users\t0\t0" >> /target/etc/fstab

... right after the section that adds the swap line to fstab.
... starts around line 1430 in /usr/bin/refractainstaller and around line 1570 in /usr/bin/refractainstaller-yad.

The last two lines in the following code block are what you need to add.

# add entry for swap to fstab if needed
if [[ $use_existing_swap = "yes" ]] ; then
        if [[ $use_uuid = yes ]]; then
                swap_part="$(/sbin/blkid -s UUID $swap_dev | awk '{ print $2 }' | sed 's/\"//g')"
        else
                swap_part="$swap_dev"
        fi
        echo -e $"\n Adding swap entry to fstab...\n"
        echo -e "$swap_part\tswap\tswap\tdefaults\t0\t0" >> /target/etc/fstab
else
        echo -e "/swapfile\tswap\tswap\tdefaults\t0\t0" >> /target/etc/fstab
fi

# Make entry for cdrom in fstab
echo -e "/dev/sr0\t/media/cdrom\tauto\tnoauto,owner,ro,users\t0\t0" >> /target/etc/fstab

Thank you so much for taking the time to explain/write all this up.

I'll try it and see how it goes.
Just in case, this time I'll have a snapshot of the VM available.

Fortunately, I have backintime installled so I did not have to redo all my previous work after I went edit-happy with /ect/fstab.

With respect to seeing the devices in Xfe, I remembered gnome-disk-utility and decided to try it out on the VM and things got easier.
Not too heavy on the file system but certainly dangerous to use without the proper attention.

eg: that readily available delete selected partition button ...

Have a good week-end.
Cheers,

A.

#15 Re: Installation » Refracta Snapshot VM mount points question. » 2019-12-06 22:55:03

Hello:

fsmithred wrote:

fstab is excluded in the rsync copy ...
... gets created when you install with refractainstaller.

OK.
Sort of makes sense.
The live *.iso would take a large portion of boot time figuring out why it was not being able to mount what fastab said was there and may not be.

But what I am referring to is the fact that the mount points I generated in /media ie: /media/cdrom and /media/usb on the VM are not copied over to the *.iso.
ie: there are no files in /media on the live *.iso.

They survive a reboot of the VM and belong to root.
And I can mount a cdrom or usb to them as root.

If they do not get carried over to the live *.iso, I have to generate them everytime I boot the *.iso file.
Make sense?

fsmithred wrote:

There's no entry for cdrom.
I haven't needed that in years.

I still have a score or so of DVDs and CDs with data and need to access them every so often. 

fsmithred wrote:

... you'd need to add a line of code to refractasnapshot.

That's rather over my head.

Would it be possible to (eventually) add an option for that to refractasnapshot.conf?

--- ot ---
One of the very good things that TinyCore linux has is an application called mount tool.

A very simple desktop panel with a button for each of the drives in the system you are booting into.
Click on a drive and it gets mounted, click again, it gets unmounted.

I wonder if it was specially written for TCore or it has its origins in some linux application.
--- ot ---

Thanks in advance,

A.

#16 Re: Installation » Refracta Snapshot VM mount points question. » 2019-12-06 21:31:57

Hello:

ralph.ronnquist wrote:

... is that a typo in this post, or a typo in "fstab"?

It's a typo in fstab.
But the cdrom gets automatically mounted in the VM nevertheless.

[Changing it now]

Done.

groucho@devuan:~$ cat /etc/fstab
rootfs    / rootfs                              rw         0   0
/dev/sr0   /media/cdrom    auto    noauto,owner,ro,users   0   0
groucho@devuan:~$ 

Thanks for the heads up.

Best,

A.

#17 Installation » Refracta Snapshot VM mount points question. » 2019-12-06 16:41:42

Altoid
Replies: 6

Hello:

I have set up two mount points in my Devuan ascii 2.0.0 VM ...

/media/cdrom and /media/usb, the first one listed in /etc/fstab:

groucho@devuan:~$ cat /etc/fstab
rootfs    / rootfs                             rw         0   0
dev/sr0   /media/cdrom    auto    noauto,owner,ro,users   0   0
groucho@devuan:~$ 

... but when I boot the *.iso image made with RS, the mount points are not there.

Is this how it is supposed to be or am I missing something with respect to Refracta Snapshot's configuration or VMs in general?

Thanks in advance,

A.

#18 Re: Installation » Xfe + isomount question » 2019-12-05 21:25:55

Hello:

fsmithred wrote:

... you could make a hookscript that will run when you boot the live iso and inject the necessary lines into /etc/fstab.

No idea how to do that.

fsmithred wrote:

... won't work for a rescue usb that you're booting on some other box.

It's always the same box but as this *.iso (fortunately) is not used with any frequency, the disk configuration is likely to change so to all effects and purposes it is/could well be another box.

fsmithred wrote:

... better off doing it manually in a root terminal.
... fdisk, df and blkid to get information ...
... figure out which one you want to mount.

Yes, you might be right.
I have found that doing things in the terminal is helping me become, slowly albeit steadily, a bit more proficient with in use of the command line.

But it is hard to shed years point&click muscle memory and the apparent convenience it brought along.

I'll see what I can rig up.

Thanks for your input.

Best,

A.

#19 Re: Installation » Xfe + isomount question » 2019-12-04 22:54:55

Hello:

fsmithred wrote:

... can set up the boot menu before or when you make the snapshot.

OK

fsmithred wrote:

... set up the extra partitions in fstab with 'noauto,user' options, then you can mount/unmount by right-clicking on the mountpoint.

Yes, that should do it.

Excuse my ignorance, but how do I set that up in a live *.iso when I don't know what drives will be in the box when I use it?

fsmithred wrote:

If xfe won't do what you want ...

Xfe is really lean, quick and most importantly, desktop agnostic.
I'd rather stay with Xfe.

Thanks for your input, much appreciated.

Best,

A.

#20 Re: Installation » Xfe + isomount question » 2019-12-04 18:42:32

Hello:

fsmithred wrote:

... don't understand why you need to mount the isos.

To tell the truth, neither do I.

So I tried to recall how that came about and then it came back to me: I was trying out mounting (in general) with Xfe.
I was having the issues I have mentioned with USB drives and was also having problems mounting CD/DVDs.

So I then tried an *.iso I had at hand in /home/snapshot.
That is what happened and ho it came about.
Sorry ... 

fsmithred wrote:

... planning to do frequent editing of the iso's boot menu?

No, not really.
I can do that before generating it in refractasnapshot.conf, right?

You are (as usual) right and I stand corrected: the title of the post should have been different.
But the issue is common to mounting an *.iso, a USB drive or system drives are similar or the same.

fsmithred wrote:

According to the xfe docs ...

Yes, read them.

fsmithred wrote:

... mount filesystems with ctrl-M and unmount with ctrl-U.
What I can't figure out is how/where you find these unmounted filesystems.

Right.
That is exactly what I need to find out how to do.

fsmithred wrote:

... don't see anything in the preferences about volume management or devices.

Neither do I.

fsmithred wrote:

... adds custom mount / unmount commands ...

Yes, it was a feature someone asked for and the author implementes a couple of years later.
And that's what I want to use but I can only select to mount something Xfe can see/show as available.

Maybe it has to look in /etc/fstab?
I have two mount points /media/cdrom and /media/usb but my /etc/fstab only has rootfs / rootfs rw 0 0.

Thanks and sorry for the *.iso confusion.

Best,

A.

#21 Re: Installation » Xfe + isomount question » 2019-12-04 09:04:39

Hello:

bgstack15 wrote:

... Xfe is recognizing that the /home/groucho/Desktop/Example1 is a separate mount point.
... why it is giving you options (that don't work ...

Yes, if I mount the *.iso with the script as user and then open another instance of Xfe as root, I am able to unmount the *.iso with the icon from there.
I can also mount the *.iso with the script (mounts in /root/Desktop) but not with the the icon as it is also greyed out when as running as root.

Command line mounting of the iso on /media/cdrom is only possible as root.

groucho@devuan:/home/snapshot$ sudo mount snapshot-20191203_1428.iso /media/cdrom
mount: /dev/loop0 is write-protected, mounting read-only
groucho@devuan:/home/snapshot$
groucho@devuan:/home/snapshot$ sudo umount snapshot-20191203_1428.iso /media/cdrom
umount: snapshot-20191203_1428.iso: not mounted
groucho@devuan:/home/snapshot$ 
bgstack15 wrote:

Can you write a custom xfe function to fusermount -u the selected directory?

I'm sorry but my scripting abilities are non-existent so I'd need a more detailed explanation.
The isounmount script uses fusermount and is called from Xfe by selecting the *.iso file and right-click -> scripts -> isounmount

#fxe script iso-umount
 #!/bin/bash
 
 FILE=$(basename "$1")
 MOUNTPOINT="$HOME/Desktop/$FILE"
 
 fusermount -u "$MOUNTPOINT"

What I don't understand is why the mount icon does not go 'live' when I select the *.iso file with the pointer.
ie: Xfe is not identifying it as 'mountable' but then it does identify it as 'unmountable' once it is mounted.

Similar thing happens ith a USB stick:

I can mount it as root via command line and then the unmount icon is 'live' but the operation is not permitted.

Xfe is highly configurable, maybe this is all related to Edit -> Preferences -> Programs where Volume management is configured?

Mount: mount
Unmount: umount

Thanks for your input.

Cheers,

A.

#22 Re: Installation » Xfe + isomount question » 2019-12-04 00:44:13

Hello:

fsmithred wrote:

... commands are correct ...

Yes ...
I thought so too, because ...
... one thing I tried actually worked?  ;-D

fsmithred wrote:

Why do you want to mount the isos?

If you recall, this live Devuan ascii *.iso will live inside my box in a small capacity USB plugged into a motherboard USB port and will be used as a sort of rescue installation.
The drive will also have one or maybe two separate logical partitions inside an extended partition to hold a few *.iso files which I may need.

This is why I consider it important to be able to mount an *.iso image from within the live installation.
eg: imagine a rig with disabled boot drive and a failing CD/DVD unit with the backups/images in another drive in the box or on a portable external drive.

That said, why the difference in behaviour I mentioned earlier?

ie: Why can I mount and unmount an *.iso made with Refractasnapshot using the scripts I set up as the logged in user but cannot unmount it from Xfe?

On a related subject:

My Devuan ascii 2.0.0 installation works with four internal SAS drives, a DVD drive and four additional USB/FireWire ports, all of which I have to be to be available in Xfe to mount as needed via the live.iso.

It would have to be always there, to be awakened if I have a problem.
This means it has to be oblivious as to which drives are living inside the box when booted or to the ID any of the USB/FireWire drives that could be plugged in at any time.

ie:
When I boot the live.iso and start Xfe, I need to see the on-board drives present in the box at that time and any USB/FireWire drive I plug in so I can mount any of them.

Just like with my main Devuan ascii installation, where I can see all my drives in Thunar and mount/unmount them (w/pw) as needed.

How can I get that done?
With autofs?

Thanks in advance,

A.

#23 Installation » Xfe + isomount question » 2019-12-03 23:44:45

Altoid
Replies: 10

Hello:

Continuing with my ongoing tune up of a minimal Devuan ascii live *.iso, I am stuck ith the issue regarding automounting the drives.

While trying to see how to mount an *.iso image, I installed the isomount package as it had a much smaller footprint then other available options.

I found a couple of adequate scripts on the isomount project page which I set up in /home/groucho/.config/xfe/scripts:

#fxe script iso-mount
#!/bin/bash
 
FILE=$(basename "$1")
MOUNTPOINT="$HOME/Desktop/$FILE"
 
fuseiso -p "$1" "$MOUNTPOINT"

     
and

#fxe script iso-umount
 #!/bin/bash
 
 FILE=$(basename "$1")
 MOUNTPOINT="$HOME/Desktop/$FILE"
 
 fusermount -u "$MOUNTPOINT"

Now I can right-click on an *.iso file and do scripts -> mount or scripts -> unmount.

The surprise was that doing a right-click on the image mounted in /Desktop also showed me a greyed out Mount and an Unmount option, the latter bringing up a pop-up that said Permisison denied when clicked on.

So I can mount and unmount an *.iso made with Refractasnapshot using the scripts I set up as the logged in user but cannot unmount it from Xfe.
I cannot mount it either as the Mount and Unmount icons in the bar are greyed out and the Unmount icon appears only if I have previously mounted the *.iso file with the isomount script.

Same thing happens if I change the ownership of the *.iso file to the logged in user.

What am I missing here?

Thanks in advance.

A.

#24 Re: DIY » ascii VM to ascii live *.iso » 2019-11-30 12:49:06

Hello:

Altoid wrote:

Let me know if you need more information.

Problem solved.

Modified the settings.
Now the Details screen reads:

Display
Video Memory: 70MN
Remote Desktop Server: Disabled
Video Capture: Disabled

Machine -> Settings -> Display

Enable 3D Acceleration -> unticked
Enable 2D Acceleration -> unticked

Saved, remade the snapshot and burned to USB.

The error I reported earlier is not there anymore and both Synaptic and Pluma work as expected.

It seems that there is a bug in Vbox with 3D acceleration and it does not work properly.

https://forums.virtualbox.org/viewtopic.php?f=3&t=85589

Cheers,

A.

#25 Re: DIY » ascii VM to ascii live *.iso » 2019-11-30 11:32:47

Hello:

fsmithred wrote:

... don't understand the error ...
... shouldn't need 3D acceleration ...

Not that I understand much, but the same thought crossed my mind.

I mean, a permissions issue I can see but ...

fsmithred wrote:

... never gotten 3D to work in vbox.) How are you starting synaptic?

I can start it through the OB menu or through the terminal.
I can only see the error message via the terminal.

The OP command (from Obmenu) is lxterminal -e sudo synaptic.
Works perfectly well in the VM.

With respect to 3D in the VM ...

The Details screen reads:

Display
Video Memory: 70MN
Acceleration: 3D
Remote Desktop Server: Disabled
Video Capture: Disabled

Machine -> Settings -> Display

Enable 3D Acceleration -> ticked
Enable 2D Acceleration -> unticked

I can untick Enable 3D Acceleration but if I then tick save the setting and tick Enable 2D Acceleration, I get an error message at the bottom that reads Invalid settings.

This is the installed VBox version:

groucho@devuan:/$ vboxmanage --version
5.2.24_Debianr128122
groucho@devuan:/$ 
groucho@devuan:~$ sudo dmesg | grep -i video
[    0.758742] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[    1.505705] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    1.506254] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input3
[    6.221301] vboxvideo: loading out-of-tree module taints kernel.
[    6.525508] vboxvideo 0000:00:02.0: fb0: vboxdrmfb frame buffer device
[    6.540221] [drm] Initialized vboxvideo 1.0.0 20130823 for 0000:00:02.0 on minor 0
groucho@devuan:~$ 
groucho@devuan:~$ cat /proc/modules | grep -i video
vboxvideo 36864 2 - Live 0xffffffffc069f000 (O)
ttm 98304 1 vboxvideo, Live 0xffffffffc062d000
drm_kms_helper 155648 1 vboxvideo, Live 0xffffffffc0653000
drm 360448 5 vboxvideo,ttm,drm_kms_helper, Live 0xffffffffc05d4000
video 40960 0 - Live 0xffffffffc0220000
groucho@devuan:~$ 

More data that may be useful:

groucho@devuan:~$ glxinfo -i | grep render
OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW

direct rendering: Yes
OpenGL renderer string: Chromium
groucho@devuan:~$ 
groucho@devuan:~$ glxinfo -i | grep direct
OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW

direct rendering: Yes
groucho@devuan:~$ 
groucho@devuan:~$ glxinfo -i | grep openGL
OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW
groucho@devuan:~$ 

But GLX gears will run (I see it on the screen) albeit with the same OpenGL Warning:

groucho@devuan:~$ glxgears
OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW

XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 1669 requests (1669 known processed) with 0 events remaining.
groucho@devuan:~$ 
groucho@devuan:~$ glxgears -info
OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW

GL_RENDERER   = Chromium
GL_VERSION    = 2.1 Chromium 1.9
GL_VENDOR     = Humper
GL_EXTENSIONS = GL_EXT_texture_compression_s3tc GL_EXT_draw_range_elements GL_EXT_framebuffer_object GL_EXT_compiled_vertex_array GL_ARB_depth_texture GL_ARB_fragment_program GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_shadow GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_EXT_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_EXT_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_IBM_texture_mirrored_repeat GL_ATI_texture_mirror_once GL_ARB_texture_non_power_of_two GL_ARB_transpose_matrix GL_ARB_vertex_buffer_object GL_ARB_pixel_buffer_object GL_ARB_vertex_program GL_ARB_window_pos GL_EXT_blend_color GL_EXT_blend_minmax GL_EXT_blend_func_separate GL_EXT_blend_subtract GL_EXT_texture_env_add GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_secondary_color GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_EXT_texture_object GL_EXT_texture3D GL_IBM_rasterpos_clip GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_texgen_reflection GL_NV_texture_rectangle GL_ARB_texture_rectangle GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_SGIS_generate_mipmap GL_ARB_shading_language_100 GL_ARB_shader_objects GL_ARB_vertex_shader GL_ARB_fragment_shader GL_EXT_texture_sRGB GL_EXT_framebuffer_blit GL_EXT_blend_equation_separate GL_EXT_stencil_two_side GL_ARB_texture_float GL_ARB_draw_buffers GL_ARB_shader_texture_lod GL_CR_state_parameter GL_CR_cursor_position GL_CR_bounding_box GL_CR_print_string GL_CR_tilesort_info GL_CR_synchronization GL_CR_head_spu_name GL_CR_performance_info GL_CR_window_size GL_CR_tile_info GL_CR_saveframe GL_CR_readback_barrier_size GL_CR_server_id_sharing GL_CR_server_matrix  GL_EXT_stencil_two_side
VisualID 33, 0x21
302 frames in 5.0 seconds = 60.305 FPS
301 frames in 5.0 seconds = 60.014 FPS
301 frames in 5.0 seconds = 60.179 FPS
301 frames in 5.0 seconds = 60.045 FPS
288 frames in 5.0 seconds = 57.418 FPS
301 frames in 5.0 seconds = 60.013 FPS0
--- snip ---

Not much acceleration there, no?

groucho@devuan:~$ xvinfo        
X-Video Extension version 2.2
screen #0
 no adaptors present
groucho@devuan:~$ 

Let me know if you need more information.

Best,

A.

Board footer

Forum Software