You are not logged in.
- Topics: Active | Unanswered
#1051 Re: Hardware & System Configuration » [SOLVED] Problem with shutdown script » 2021-11-29 14:48:22
Hello:
... instead of using sleep use the wait command.
Hmm ...
"... wait is a command that waits for the given jobs to complete ..."
Think that may be it?
I'll try it out and report back here.
But if it the command works from an open terminal ...
vboxmanage controlvm "madmax ascii" poweroff && sleep 5s && sudo /usr/bin/shutdown.sh
... shouldn't it also work in the launcher command line?
xfce4-terminal -x vboxmanage controlvm "madmax ascii" poweroff && sleep 5s && sudo /usr/bin/shutdown.sh
My guess is that there's something in the syntax I'm using, just cannot find out what it is.
Thanks for your input.
Best,
A.
#1052 Re: Hardware & System Configuration » Attention Dual/Multi-booters: Latest GRUB (2.06-2) disables os-prober » 2021-11-29 11:13:07
Hello:
... received an update to grub ...
... os-prober would no longer run.
... people with dual-boot or multi-boot computers will no longer be able to...update-grub...in order to get their other systems to show in the grub menu.
Any idea as to what led to that?
Is it some systemd related thing?
That will probably break the grub-customizer application.
C'mon devs, you can do better than that!
Indeed ...
+100
... open and edit the following file...
/etc/default/grub
...and add the following line...GRUB_DISABLE_OS_PROBER=falseSave and close the file, then open a terminal and run an...
update-grub
Thank you very much for the heads-up.
Best,
A.
#1053 Hardware & System Configuration » [SOLVED] Problem with shutdown script » 2021-11-28 21:46:08
- Altoid
- Replies: 8
Hello:
I shut down my Devuan Beowulf system with a script called from a launcher which I set up within the panel of my Xfce desktop:
This is the script:
#!/bin/sh
# added to shutdown directly - no shutdown helper
PATH=/sbin:/bin:/usr/sbin:/usr/bin:
#
sync && sudo ethtool -s eth0 wol d && sudo rmmod -s -v e1000e && sudo shutdown -h nowThis is the launcher command line:
xfce4-terminal -x sudo /usr/bin/shutdown.shThis has been working perfectly well for the longest time.
Some time ago I set up Pihole in an autostarted Vbox virtual machine but although it seems to start up properly it does not shutdown gracefully.
ie: sudo shutdown -h now takes effect before the virtual machine has completely shut down.
The idea is to send the virtual machine the shutdown command, wait 5s and then execute the shutdown script.
Simple if not elegant.
As VBox gives members of the vboxusers group permission to start and shutdown a virtual machine, I cannot add the shutdown command to the shutdown script called from the launcher because this script needs sudo. ie: root privileges and the vms belong to vmusers and not to root.
So I add the virtual machine shutdown script + a 5s sleep to the launcher command line.
But it does not work with the launcher.
vboxmanage controlvm "madmax ascii" poweroff && sleep 5s && sudo /usr/bin/shutdown.sh works properly if I execute it from a terminal.
But not when I run it from the launcher:
xfce4-terminal -x vboxmanage controlvm "madmax ascii" poweroff && sleep 5s && /usr/bin/shutdown.sh
It only shuts down the virtual machine, the rest of the command does not have effect.
Cannot figure out what I'm doing wrong.
Any ideas?
Thanks in advance.
A.
#1054 Hardware & System Configuration » Hibernation nosave memory in dmsg » 2021-11-27 00:59:30
- Altoid
- Replies: 0
Hello:
I don't have hibernation enabled in my Devuan Beowulf installation.
Why do I have this in my dmsg printout?
~$ sudo dmesg
--- snip ---
[ 0.039017] PM: hibernation: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
[ 0.039019] PM: hibernation: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
[ 0.039020] PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000e1fff]
[ 0.039021] PM: hibernation: Registered nosave memory: [mem 0x000e2000-0x000fffff]
[ 0.039023] PM: hibernation: Registered nosave memory: [mem 0xbfe40000-0xbfe4dfff]
[ 0.039024] PM: hibernation: Registered nosave memory: [mem 0xbfe4e000-0xbfecffff]
[ 0.039026] PM: hibernation: Registered nosave memory: [mem 0xbfed0000-0xbfeddfff]
[ 0.039027] PM: hibernation: Registered nosave memory: [mem 0xbfede000-0xbfeebfff]
[ 0.039028] PM: hibernation: Registered nosave memory: [mem 0xbfeec000-0xbfffffff]
[ 0.039029] PM: hibernation: Registered nosave memory: [mem 0xc0000000-0xdfffffff]
[ 0.039031] PM: hibernation: Registered nosave memory: [mem 0xe0000000-0xefffffff]
[ 0.039032] PM: hibernation: Registered nosave memory: [mem 0xf0000000-0xfedfffff]
[ 0.039033] PM: hibernation: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
[ 0.039034] PM: hibernation: Registered nosave memory: [mem 0xfee01000-0xffafffff]
[ 0.039036] PM: hibernation: Registered nosave memory: [mem 0xffb00000-0xffffffff]
--- snip ---
~$
As far as I know, I have disabled any and all power management.
Thanks in advance,
A.
#1055 Re: Hardware & System Configuration » acpi errors on each kernel update » 2021-11-26 15:51:56
Hello:
Thanks
You're welcome.
I can/could 'iasl -c' a new DSDT ...
Yes.
Provided you were able enough and found your way around the obscure maze of DSDT stanzas.
Now, if the kernel you are using was compiled with ACPI_TABLE_UPGRADE=y you can still load an alternate DSDT table using the acpi_override method.
Here's the list of links I have kept, some may be dead by now.
There are one or two that have the recipe to load an alternate DSDT via acpi_override in one of these groups.
I used it and was able to load a new table successfully.
Override: <---- here
https://delta-xi.net/#056
https://wiki.archlinux.org/index.php/DSDT
https://cgc.com.kw/tag/dsdt-override/
Patches:
https://github.com/RehabMan/Laptop-DSDT … estart.txt
https://github.com/RehabMan/Intel-NUC-D … DT-PTS.dsl
https://www.tonymacx86.com/threads/shut … dt.229418/
GRUB:
https://github.com/tsgates/arch-wiki-ma … ki/DSDT.md
Then there's all these, some of which may have been worthwhile, but I can't recall which:
https://github.com/hirschmann/nbfc/wiki … k%27s-DSDT
https://cannibalcandy.wordpress.com/201 … acpi-woes/
https://sit1way.wordpress.com/2013/04/1 … uggy-dsdt/
http://blog.michael.kuron-germany.de/20 … compiling/
https://lists.gnu.org/archive/html/bug- … 00008.html
https://github.com/torvalds/linux/blob/ … pi/osi.txt
https://patchwork.kernel.org/patch/2831128/
https://www.kernel.org/doc/Documentatio … erride.txt
https://www.tldp.org/HOWTO/SCSI-2.4-HOWTO/kconfig.html
https://01.org/linux-acpi/documentation/overriding-dsdt
https://www.insanelymac.com/forum/topic … dt-editor/
http://wiki.osx86project.org/wiki/index.php/DSDT
http://acpi.sourceforge.net/dsdt/
https://gaugusch.at/kernel.shtml
https://init-6.bitbucket.io/content/201 … r-central/
https://gist.github.com/rschmukler/1101770
Unfortunately DSDT editing is the almost exclusive realm of Mac boxes/laptop owners who want to run Linux on them.
This means that most if not all the information to be found is for that hardware, albeit with quite a bit of overlapping with Wintel stuff.
A fortunate thing because help is not available (or offered) to non-Mac people.
Long story short: I was eventually able to fix most of the BIOS errors/warnings detected with the MS based tools I found on line and came up with a new DSDT.
Much to my chagrin and after a great many hours hard work, the new DSDT did not solve the problems the crap BIOS my Sun Ultra 24 has.
Save getting rid of most of the errors/warnings (not all), did nothing else for me, at least nothing noticeable.
Which meant that the Linux kernel was doing its workaround properly. 8^)
But I had to do it all over again when the kernel got upgraded and after I forgot to do it for a second time, I decided it was not worth the hassle.
It did not solve my Ultra 24 issues so that was it.
HTH.
Best,
A.
#1056 Re: Hardware & System Configuration » acpi errors on each kernel update » 2021-11-26 12:16:12
Hello:
... an old piece from Intel atoms time.
D945GCLF2D ...
All these warning are like/similar to the ones I get in dmesg when booting my Sun Ultra 24 WS:
groucho@devuan:~$ sudo dmesg | grep -i "acpi bios"
[ 0.018306] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 128/64 (20200925/tbfadt-569)
[ 1.272873] ACPI BIOS Error (bug): Could not resolve symbol [\_SB._OSC.SUPP], AE_NOT_FOUND (20200925/psargs-330)groucho@devuan:~$ sudo dmesg | grep -i "acpi error"
[ 1.272882] ACPI Error: Aborting method \_SB._OSC due to previous error (AE_NOT_FOUND) (20200925/psparse-531)
groucho@devuan:~$ I run Devuan Beowulf on my Asus EEE 1000HE which has an Atom 280 processor and also get a number of ACPI warnings but it works properly.
Or so it seems. 8^/
groucho@eee-dev3:~$ sudo dmesg | grep -i "acpi warning"
[ 14.086823] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x0000000000000800-0x000000000000087F (\PMIO) (20180810/utaddress-213)
[ 14.157275] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x0000000000000800-0x000000000000087F (\_SB.PCI0.SBRG.PMS0) (20180810/utaddress-213)
[ 14.226890] ACPI Warning: SystemIO range 0x00000000000004B0-0x00000000000004BF conflicts with OpRegion 0x0000000000000480-0x00000000000004BF (\_SB.PCI0.SBRG.GPBX) (20180810/utaddress-213)
[ 14.290513] ACPI Warning: SystemIO range 0x0000000000000480-0x00000000000004AF conflicts with OpRegion 0x0000000000000480-0x00000000000004BF (\_SB.PCI0.SBRG.GPBX) (20180810/utaddress-213)
groucho@eee-dev3:~$ I understand that these ACPI errors/warnings are caused by badly written BIOSes.
ie: The result of a blatant lack of adherence to ACPI standards by BIOS writers, OEMs and their permanent bowing to the very lax ACPI compliance by Microsoft.
Many years ago this was labelled the "Wintel" way of doing things and the main reason most motherboards support MS OSs (from XP home to Vista) but not Linux.
From what I have read, the Linux kernel is supposed to be able to 'work around' these problems but this does not happen on all motherboards/BIOSes.
And as time passes by, a lot of this hardware, which would work properly with a correctly written BIOS, ends up falling by the wayside.
You may want to try booting a plain/basic Beowulf Devuan net install installation from a USB sick with ACPI disabled in the kernel command line ie; ACPI=off and see what (if any) errors/warnings you get from that via the install logs and dmesg.
Maybe your server can do well enough without ACPI?
Sorry but that's all I can come up with.
Best,
A.
#1057 Re: ARM Builds » [Raspberry Pi 400] Why is wifi interface named wlan1 on the Pi400? » 2021-11-25 21:47:15
Hello:
... Devuan on both Pi4b and Pi400, in aarch64 mode.
... WIFI interface is named WLAN0 on the Pi4b ...
... named WLAN1 on the Pi400 ...
Any clues?
Can't imagine why.
But check this and see if there's something there: https://wiki.debian.org/NetworkInterfaceNames
eg: the /etc/udev/rules.d/70-persistent-net.rules file in each one of the installations and compare them.
Best,
A.
#1058 Re: Other Issues » [SOLVED] serial terminal login stopped working » 2021-11-25 13:25:09
Hello:
I have been following this thread because I have never used serial input and was interested to see how it worked.
... other thing that is very odd is that I can enter in text at the log in prompt from the same SATA SSD drive
when a graphics card and keyboard is installed using the original install inittab that was saved before I modified it ...
So ...
What is the difference between the original install inittab and the modified one which then did not work?
And then, what is the difference between that original one and the one in the updated Devuan Chimaera?
Looking at the eventual differences between them will give us a way to diagnose the problem.
Thanks in advance,
A.
#1059 Re: Other Issues » [SOLVED] Problems with a Seagate portable drive » 2021-11-24 12:48:49
Hello:
Do smartctl -h to get a complete usage summary.
You may want to read the summary again. <----
Look for the -T modifier to see what it does ...
~$ sudo smartctl -h
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-5.10.0-0.bpo.3-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
Usage: smartctl [options] device
--- snip ---
===== SMARTCTL RUN-TIME BEHAVIOR OPTIONS =====
--- snip ---
-T TYPE, --tolerance=TYPE (ATA)
Tolerance: normal, conservative, permissive, verypermissive
--- snip ---
~$... and use it as required by the application so it can continue:
--- snip --- Read Device Identity failed: Invalid argument A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
External drives running through USB are sometimes tricky, some brands more than others.
Previous (limited) experience has shown me that this is many times due to problematic access to the USB controller chip inside the external drive's case.
While you can use other ie: -d modifiers, I expect that using -T will allow the application to decide the device's type and act accordingly.
For example, a run on an old 40Gb (!) USB drive I have:
groucho@devuan:~$ sudo smartctl -i -a -T verypermissive /dev/sdg1
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-5.10.0-0.bpo.3-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: SAMSUNG
Product: MP0402H
Revision: 0811
User Capacity: 40,060,403,712 bytes [40.0 GB]
Logical block size: 512 bytes
Device type: disk
Local Time is: Wed Nov 24 09:33:25 2021 -03
SMART support is: Unavailable - device lacks SMART capability.
=== START OF READ SMART DATA SECTION ===
Current Drive Temperature: 0 C
Drive Trip Temperature: 0 C
Error Counter logging not supported
Device does not support Self Test logging
~$ Running this ...
~$ sudo smartctl -i -a -T verypermissive /dev/sdx... should get you some results.
Best,
A.
#1060 Re: Other Issues » [SOLVED] Error message after update » 2021-11-23 15:09:54
Hello:
... why I got that error message ...
Could be a temp glitch in the script, caused by [ whatever could be ].
Periodically, I'll run updates and they don't complete.
I've experienced it in my boxes a couple of times.
I just retried and that would be it.
This is Linux, not MS. ;^ )
As long as the glitches are not a constant ...
Thanks to all, especially ...
You're welcome but it's nothing special.
Just trying to give back a bit of the much I have received here at Dev1.
Best,
A.
#1061 Re: Other Issues » [SOLVED] Problems with a Seagate portable drive » 2021-11-23 14:08:29
Hello:
... strongly recommend a SMART test on that device.
+1
See https://linoxide.com/how-to-test-ssd-hd … -in-linux/
or
Do smartctl -h to get a complete usage summary.
You don't want a drive with issues if you are using it for backups.
Best,
A.
#1062 Re: Other Issues » [SOLVED] Error message after update » 2021-11-23 13:01:16
Hello:
ron@ron:~$ sudo apt update && sudo apt upgrade --- snip --- 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
You're good to go. 8^D
Best,
A.
#1063 Re: Other Issues » [SOLVED] Error message after update » 2021-11-23 12:41:45
Hello:
Did all three ...
Doing as suggested by MiyoLinux included the next step I would have suggested to check the state your system was in:
$ sudo apt update && sudo apt upgradeAs you can see, the terminal printout when reinstalling linux-image-amd64 reads:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.You may want to try it and see if it comes up clean ie:
~$ sudo apt update && sudo apt upgrade
--- snip ---
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. # <- this
~$ If it does, we're done.
Unless you have any other issues, I think now you're good to go. 8^D
That said, in my opinion it is not by any means necessary to run a system on the latest kernel/bleeding edge.
Unless you have the latest hardware or are testing new things.
But then Debian most probably won't have native drivers ready and you will have to depend on the OEMs for that.
Until systemd and wayland reared their heads, it was all about stability and previsibility.
ie: the tried and true way of doing things in Debian.
Things have changed quite a bit, which is why we're here now.
Best,
A.
#1064 Re: Other Issues » [SOLVED] Error message after update » 2021-11-22 22:18:55
Hello:
sudo apt-get install --fix-broken returned ...
Right ...
apt says those packages are no longer required.
Now you do this:
sudo apt autoremove && sudo apt install -f The first part (before &&) will remove the packages no longer required and the second part will look for and try to fix any missing dependencies you may have in the system.
Let's see what you get from that.
Best,
A.
#1065 Re: Hardware & System Configuration » VBox virtual machine error in dmesg » 2021-11-22 20:34:14
Hello:
No, not yet. I am reluctant ...
I went ahead and tried installing the latest avaiable from their repository.
groucho@devuan:~$ vboxmanage --version
6.1.28r147628
groucho@devuan:~$ After all the vm only runs Pie-hole and Unbound.
The line in dmesg for the guest is still there:
groucho@dev-pihole:~$ sudo dmesg | grep -i error
--- snip ---
[ 16.458606] 00:00:00.178288 vminfo Error: Unable to connect to system D-Bus (1/3): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
--- snip ---
groucho@dev-pihole:~$ I now get the kernel traps for vboxsvc and vboxheadless but can see no problem/effects.
That said, it seems that a newer version for Buster/Beowulf has been released after we last wrote:
https://download.virtualbox.org/virtual … _amd64.deb
I'll try it and see if things improve.
Thanks for your input.
Best,
A.
#1066 Re: Other Issues » [SOLVED] Error message after update » 2021-11-22 14:05:16
Hello:
Did something really go wrong?
Seems some part of the installation process may have not been fully completed.
eg: something not completely removed, dependencies not completed for some reason.
--- snip ---
linux-image-5.15.0-1-amd64 is not configured yet
--- snip ---No idea why.
But you may want to try giving apt-get a chance to fix it:
sudo apt-get install --fix-brokenHopefully, the output you get will either mark success or say what's going on or missing.
Best,
A.
#1067 Re: Hardware & System Configuration » VBox virtual machine error in dmesg » 2021-11-22 04:44:51
Hello:
... VirtualBox 6.1 is messed up and doesn't work right on Beowulf.
I have not had any of the problems you mention.
Only the ones mentioned (kernel error in host at shutdown and guest's dmesg) but they don't seem to cause any malfunction, at least one that I can see or notice.
But then I am not doing anything to tax the installation, my guest just runs a recursive DNA server (unbound) and Pi-hole on the host.
It seems from what I have read in the Virtualbox support forum that they balk at use of Linux distribution versions of VBox.
They insist on their version being used, not targeted at any specific distribution, just at any version that is not theirs.
If not their version, admin says no to any support.
Like I mentioned I am running 6.1.18-142142 but the virtualbox version for Debian Buster/Devuan Beowulf available at download.virtualbox.org is 6.1.28-147628.
... version that has been working reliably for me is 6.1.22 r144080 (Qt5.6.1).
Have you tried the latest one from the virtual box repository or was that the one that locked up?
Thanks for your input.
A.
#1068 Re: Hardware & System Configuration » VBox virtual machine error in dmesg » 2021-11-20 22:56:55
Hello:
... looks fine ...
Good to know.
Thanks.
... leads to the question whether the dbus daemon(s?), which is supposed to be the server end of that socket, is running at the time during bootup when something is expecting it.
The daemon(s) run in the guest, yes?
Lets see:
I boot the host and it autostarts the guest (headless) at some point in the boot process.
I can eventually login to the guest's desktop via the VirtualBox manager, but I am slowly getting used to doing most things via cmd line. =^)
I log in to the host as soon as I get SLiM on screen and right upon getting the desktop, I load Pegasus Mail and Pale Moon.
But unless I wait a few seconds, I cannot get anything from either because there is no net connection available at that point.
I expect this is because Unbound and Pi-hole are not up and running yet.
Not because of the guest machine not being up yet.
Sound plausible?
Thanks for your input.
Best,
A.
#1069 Re: Hardware & System Configuration » VBox virtual machine error in dmesg » 2021-11-20 21:12:46
Hello:
... looking for a pathname ...
... useful to review that with namei ...
I added the -o to the command to show the owner and group data:
groucho@dev-pihole:~$ sudo namei -l -o /var/run/dbus/system_bus_socket
f: /var/run/dbus/system_bus_socket
drwxr-xr-x root root /
drwxr-xr-x root root var
lrwxrwxrwx root root run -> /run
drwxr-xr-x root root /
drwxr-xr-x root root run
drwxr-xr-x messagebus messagebus dbus
srwxrwxrwx root root system_bus_socketI'm afraid this is rather out of my depth. 8^|
Have to read the manfile a few more times to interpret this properly.
Does it look right to you?
The only thing that seems strange (to me) is that everything is owned by root.
Thanks for your input.
Best,
A.
#1070 Re: Hardware & System Configuration » VBox virtual machine error in dmesg » 2021-11-20 20:22:22
Hello:
There does not seem to be a vboxusers group available in the guest machine.
On a whim, I added the vboxusers group to the guest machine and my userid to the group:
groucho@dev-pihole:~$ groups
groucho adm disk mail cdrom tape sudo backup plugdev users vboxsf vboxusers
groucho@dev-pihole:~$ groucho@dev-pihole:~$ cat /etc/group | grep vbox
vboxsf:x:999:groucho
vboxusers:x:1001:groucho
groucho@dev-pihole:~$ Unfortunately, the error in dmesg persists:
groucho@dev-pihole:~$ sudo dmesg | grep -i error
[ 17.507723] 00:00:00.118675 vminfo Error: Unable to connect to system D-Bus (1/3): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
groucho@dev-pihole:~$There are two instances of system_bus_socket.
1. In /var/run/dbus
groucho@dev-pihole:~$ ls /var/run/dbus
pid system_bus_socket
groucho@dev-pihole:~$ 2. In /run/dbus
groucho@dev-pihole:/run/dbus$ ls
pid system_bus_socket
groucho@dev-pihole:/run/dbus$ This would be correct as they are linked:
groucho@dev-pihole:~$ ls -ald /run /var/run /var/lock /run/lock
drwxr-xr-x 21 root root 920 Nov 20 16:26 /run
drwxrwxrwt 2 root root 80 Nov 20 16:27 /run/lock
lrwxrwxrwx 1 root root 9 Jun 6 2018 /var/lock -> /run/lock
lrwxrwxrwx 1 root root 4 Jun 6 2018 /var/run -> /run
groucho@dev-pihole:~$ So ...
Why doesn't vm find it?
I wonder where it is you have to tell it where to find it ...
Some *.conf file?
Best,
A.
#1071 Re: Hardware & System Configuration » VBox virtual machine error in dmesg » 2021-11-20 18:57:07
Hello:
Bist Du Mitglied der Gruppe vboxusers?
Ja bin ich =^)
My userid is the same in both the host and the guest.
In the host:
groucho@devuan:~$ groups
groucho adm lp mail dialout fax cdrom floppy tape sudo audio dip www-data backup video plugdev staff users crontab netdev lpadmin scanner saned vboxusers fuse powerdev debian-exim
debian-eximgroucho@devuan:~$groucho@devuan:~$ cat /etc/group | grep vbox
vboxusers:x:124:groucho
groucho@devuan:~$ In the guest, my user is a member of vboxsf:
groucho@dev-pihole:~$ groups
groucho adm disk mail cdrom tape sudo backup plugdev users vboxsf
groucho@dev-pihole:~$ groucho@dev-pihole:~$ cat /etc/group | grep vbox
vboxsf:x:999:groucho
groucho@dev-pihole:~$ There does not seem to be a vboxusers group available in the guest machine.
Danke schön,
A.
#1072 Re: Hardware & System Configuration » VBox virtual machine error in dmesg » 2021-11-20 12:19:30
Hello:
... your host ...
Sorry, I neglected to mention it. 8^/
My host runs on Beowulf:
groucho@devuan:~$ uname -a
Linux devuan 5.10.0-0.bpo.3-amd64 #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11) x86_64 GNU/Linux
groucho@devuan:~$ It runs VBox 6.1:
groucho@devuan:~$ vboxmanage --version
6.1.18r142142
groucho@devuan:~$ The guest runs on ascii:
groucho@dev-pihole:~$ uname -a
Linux dev-pihole 4.9.0-16-amd64 #1 SMP Debian 4.9.272-2 (2021-07-19) x86_64 GNU/Linux
groucho@dev-pihole:~$ ... Ceres' dbus-system-bus-common for VBox will break dbus ...
I thought something like that would happen.
Mix & Match is usually not a good idea.
Unless backports?
So, I get this error in my guest's dmesg:
ie: when booting.
groucho@dev-pihole:/var/log$ sudo dmesg | grep -i error
[ 18.005937] 00:00:00.181397 vminfo Error: Unable to connect to system D-Bus (1/3): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
groucho@dev-pihole:/var/log$ This seems to be related to VBox and dbus.
But ...
I also get this on the screen when I shutdown the host, found it in /var/log/messages:
groucho@devuan:/var/log$ cat messages | grep -i error
--- snip ---
Nov 19 22:38:23 localhost kernel: [21254.843754] traps: VBoxSVC[2451] trap int3 ip:7fa545efcddc sp:7ffe92195e50 error:0 in VBoxXPCOMIPCC.so[7fa545ef8000+f000]
--- snip ---
groucho@devuan:/var/log$It seems to be related to VBox, just like the error in the guest.
Could these be related? Dumb question. 8^|
... don't know what to suggest.
No problem.
It's the effort that counts. 8^)
Thanks for your input.
Best,
A.
#1073 Re: Hardware & System Configuration » VBox virtual machine error in dmesg » 2021-11-19 23:39:54
Hello:
... dbus's new dependencies in Unstable is dbus-system-bus-common.
My VBox Devuan machine is ascii:
groucho@dev-pihole:~$ uname -a
Linux dev-pihole 4.9.0-16-amd64 #1 SMP Debian 4.9.272-2 (2021-07-19) x86_64 GNU/Linux
groucho@dev-pihole:~$ And these are the dependencies listed for dbus:
groucho@dev-pihole:~$ apt-cache depends dbus
dbus
Depends: adduser
Depends: init-system-helpers
Depends: lsb-base
Depends: libapparmor1
Depends: libaudit1
Depends: libc6
Depends: libcap-ng0
Depends: libdbus-1-3
Depends: libexpat1
Depends: libselinux1
| Suggests: <default-dbus-session-bus>
Suggests: <dbus-session-bus>
dbus-x11
groucho@dev-pihole:~$ default-dbus-session-bus and dbus-session-bus are not installed. (see OP)
But dbus-system-bus-common is not listed.
In any case, default-dbus-session-bus and dbus-session-bus can't be installed.
Apt selects dbus-x11 but it is already installed.
Can dbus-system-bus-common from experimental be installed in ascii?
Thanks for your input.
Best,
A.
#1074 Hardware & System Configuration » VBox virtual machine error in dmesg » 2021-11-19 14:18:03
- Altoid
- Replies: 16
Hello:
I'm getting this error message at /var/log/dmesg in my Devuan Beowulf VBox machine:
groucho@dev-pihole:~$ sudo dmesg | grep -i error
[ 20.422388] 00:00:00.601196 vminfo Error: Unable to connect to system D-Bus (1/3): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
groucho@dev-pihole:~$But dbus is installed:
groucho@dev-pihole:~$ apt list | grep installed | grep -i dbus
--- snip ---
dbus/oldoldstable-security,now 1.10.28-0+deb9u1+devuan2 amd64 [installed,automatic]
dbus-x11/oldoldstable-security,now 1.10.28-0+deb9u1+devuan2 amd64 [installed,automatic]
libdbus-1-3/oldoldstable-security,now 1.10.28-0+deb9u1+devuan2 amd64 [installed,automatic]
libdbus-glib-1-2/oldoldstable,now 0.108-2 amd64 [installed,automatic]
libnet-dbus-perl/oldoldstable,now 1.1.0-4+b1 amd64 [installed,automatic]
libqt5dbus5/oldoldstable-security,now 5.7.1+dfsg-3+deb9u3 amd64 [installed,automatic]
groucho@dev-pihole:~$ And the socket exists:
groucho@dev-pihole:/var/run/dbus$ ls system_bus_socket
system_bus_socket
groucho@dev-pihole:/var/run/dbus$ system_bus_socket permissions are only for root:
groucho@dev-pihole:/var/run/dbus$ ls -l system_bus_socket
srwxrwxrwx 1 root root 0 Nov 19 09:56 system_bus_socket
groucho@dev-pihole:/var/run/dbus$ So ...
Could it be that something here is not configured correctly?
eg: a permissions issue?
Thanks in advance.
Best,
A.
#1075 Re: Other Issues » [SOLVED] Problems with a Seagate portable drive » 2021-11-19 01:51:19
Hello:
... deleted the partition, created a new one, and then formatted it. Still can't write to it.
... taking a hammer to it ...
Hmm ...
What's the hurry? 8^D
Don't let an opportunity to experiment (and learn something new) pass you by.
You'll have time to dissect it later on.
One of the things you can do is try to clear the drive completely.
With gparted:
1. select the drive - make sure it is the one you want to nuke.
2. do: partition -> format to -> cleared
That should leave the drive in a 'virgin state' so to speak.
Exit gparted, unplug the drive, plug it in again, restart gparted and select the drive again, making sure it is the one you want to nuke:
1. do: device -> create partition table and then create a single partition, format it to FAT32 and then run a check to see what's up.
Try a couple of cycles of clear -> format -> clear.
There's also a command line tool called TestDisk which I have used only a couple of times to recover a partition but it worked.
I believe there's a command to completely clear a drive.
Thanks ...
You're welcome.
Best,
A.
Board footer
