- This topic has 11 replies, 6 voices, and was last updated Oct 17-11:06 am by Robin.
-
Posts
-
Robin
Hello, need urgently some help:
After my athlon XP (32bit) mainboard running long time rock stable on antiX 19 died from dried out capacitors I’ve got an old Sempron board (64bit) from ModdIt (many thanks again!). Installing antiX 21 on it was quite easy, as usual, it runs like a charm, tested with an uptime of some months already.But the aftermath is a bit tricky and I actually need some help.
Most pressing issue is: I can’t print. Main reason for this is: There is no printing driver for Linux available for this printer (Canon LBP 8 Mark IV), the existing driver for LBP8 Mark III comes up with unusable poor results (way to low resolution).
So my workaround on the old Athlon System was to start a virtualised Windows 2000 system in virtualbox and print everything needed from within this virtual environment.
After updating the system to antiX 21 I can’t any longer start the virtual machine from the virtualbox installed, it wouldn’t allow me to set the required settings and comes up with an error message:
Ungültige Einstellungen erkannt: Seite: System: Beschleunigung Die Hardware-Virtualisierung ist in den Systemeinstellungen aktiviert, obwohl dies vom Host-System nicht unterstützt wird. Deshalb sollte diese deaktiviert werden, um ein virtuelles System starten zu könnenEven when on the settings page the message points to the selection for “Paravirtualisierung” is set to “keinen (none)” it wouldn’t allow me to store the settings, the error message stays active.
Searching the web for this problem it turned out this issue is possibly caused by a modification of virtualbox made starting after Ver 6.0.24:
Die VirtualBox-Versionen bis einschließlich 6.0.24 können VMs sowohl mit als auch ohne VT-x ausführen. VirtualBox 6.1.x und neuer können VMs nur noch mit VT-x ausführen. Der Code für die Ausführung von VMs ohne VT-x wurde entfernt…
They have removed the code for CPUs without hardware virtualisation after this version.
I tried to verify whether my Sempron CPU has or not has this feature, but couldn’t find out definitively. The BIOS also doesn’t tell anything about this. Here are my specs taken from antiX Control center:System: Kernel: 5.10.104-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc v: 10.2.1 parameters: BOOT_IMAGE=/vmlinuz-5.10.104-antix.1-amd64-smp root=UUID=5bc6e23a-7c3d-4830-983c-4fe01bac800d ro quiet Desktop: IceWM v: 2.9.9 vt: 7 dm: slimski v: 1.5.0 Distro: antiX-21_x64-full Grup Yorum 31 October 2021 base: Debian GNU/Linux 11 (bullseye) Machine: Type: Desktop Mobo: FOXCONN model: M61PMV v: FAB 1.1 serial: <superuser required> BIOS: Phoenix v: P07 date: 07/28/2009 Battery: Message: No system battery data found. Is one present? Memory: RAM: total: 1.94 GiB used: 979.9 MiB (49.4%) RAM Report: permissions: Unable to run dmidecode. Root privileges required. PCI Slots: Permissions: Unable to run dmidecode. Root privileges required. CPU: Info: model: AMD Sempron LE-1250 bits: 64 type: UP arch: K8 built: 2005-06 process: AMD 65nm family: 0xF (15) model-id: 0x7F (127) stepping: 2 microcode: N/A Topology: cpus: 1x cores: 1 smt: <unsupported> cache: L1: 128 KiB desc: d-1x64 KiB; i-1x64 KiB L2: 512 KiB desc: 1x512 KiB Speed (MHz): 2200 min/max: 1000/2200 scaling: driver: powernow-k8 governor: performance core: 1: 2200 bogomips: 4420 Flags: 3dnow 3dnowext 3dnowprefetch apic clflush cmov cpuid cr8_legacy cx16 cx8 de extapic extd_apicid fpu fxsr fxsr_opt lahf_lm lm mca mce mmx mmxext msr mtrr nopl nx pae pat pge pni pse pse36 rdtscp rep_good sep sse sse2 syscall tsc vme vmmcall Vulnerabilities: Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: spec_store_bypass status: Not affected Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: ASUSTeK driver: radeon v: kernel arch: TeraScale 2 code: Evergreen process: TSMC 32-40nm built: 2009-15 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports: active: VGA-1 empty: DVI-I-1,HDMI-A-1 bus-ID: 02:00.0 chip-ID: 1002:68f9 class-ID: 0300 Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: radeon unloaded: fbdev,modesetting,vesa gpu: radeon display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 1152x864 s-dpi: 96 s-size: 304x228mm (11.97x8.98") s-diag: 380mm (14.96") Monitor-1: VGA-1 mapped: VGA-0 model: Belinea/Maxdata 0x1b6c serial: <filter> built: 1998 res: 1152x864 hz: 75 dpi: 91 gamma: 1.83 chroma: red: x: 0.643 y: 0.329 green: x: 0.271 y: 0.604 blue: x: 0.141 y: 0.063 white: x: 0.278 y: 0.310 size: 320x240mm (12.6x9.45") diag: 400mm (15.7") ratio: 4:3 modes: 1280x1024, 1152x864, 1024x768, 800x600, 640x480, 640x400 OpenGL: renderer: AMD CEDAR (DRM 2.50.0 / 5.10.104-antix.1-amd64-smp LLVM 11.0.1) v: 3.3 Mesa 20.3.5 compat-v: 3.1 direct render: Yes Audio: Device-1: NVIDIA MCP61 High Definition Audio vendor: Foxconn driver: snd_hda_intel v: kernel bus-ID: 00:05.0 chip-ID: 10de:03f0 class-ID: 0403 Device-2: AMD Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 bus-ID: 02:00.1 chip-ID: 1002:aa68 class-ID: 0403 Sound Server-1: ALSA v: k5.10.104-antix.1-amd64-smp running: yes Network: Device-1: NVIDIA MCP61 Ethernet vendor: Foxconn type: network bridge driver: forcedeth v: kernel port: ec00 bus-ID: 00:07.0 chip-ID: 10de:03ef class-ID: 0680 IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> IP v4: <filter> scope: global broadcast: <filter> IP v6: <filter> scope: link WAN IP: <filter> Bluetooth: Message: No bluetooth data found. Logical: Message: No logical block device data found. RAID: Message: No RAID data found. Drives: Local Storage: total: 55.94 GiB used: 12.92 GiB (23.1%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SV6004H size: 55.94 GiB block-size: physical: 512 B logical: 512 B speed: <unknown> type: N/A serial: <filter> rev: 0-11 scheme: GPT Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVD-RAM GSA-H55L rev: 1.03 dev-links: cdrom,cdrw,dvd,dvdrw Features: speed: 48 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running Partition: ID-1: / raw-size: 20 GiB size: 19.52 GiB (97.59%) used: 7.38 GiB (37.8%) fs: ext4 dev: /dev/sda2 maj-min: 8:2 label: root uuid: 5bc6e23a-7c3d-4830-983c-4fe01bac800d ID-2: /boot raw-size: 500 MiB size: 474 MiB (94.79%) used: 154 MiB (32.5%) fs: ext4 dev: /dev/sda1 maj-min: 8:1 label: boot uuid: 4e8cb7b3-d37f-4533-92c1-315d6a79cc3a ID-3: /home raw-size: 30 GiB size: 29.36 GiB (97.87%) used: 5.39 GiB (18.4%) fs: ext4 dev: /dev/sda3 maj-min: 8:3 label: home uuid: f15441e2-5cbf-4b88-b63d-a91f232ebf7a Swap: Kernel: swappiness: 10 (default 60) cache-pressure: 50 (default 100) ID-1: swap-1 type: partition size: 5.45 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda4 maj-min: 8:4 label: swap uuid: ffd30430-ec4d-472a-8d7d-a49e515dc5f2 Unmounted: Message: No unmounted partitions found. USB: Hub-1: 1-0:1 info: Full speed or root hub ports: 10 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 Hub-2: 2-0:1 info: Full speed or root hub ports: 10 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900 Sensors: System Temperatures: cpu: 4294939.3 C mobo: N/A gpu: radeon temp: 57.0 C Fan Speeds (RPM): N/A Repos: Packages: apt: 1855 lib: 846 Active apt repos in: /etc/apt/sources.list.d/antix.list 1: deb http: //ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/bullseye bullseye main nosystemd nonfree Active apt repos in: /etc/apt/sources.list.d/bullseye-backports.list 1: deb http: //deb.debian.org/debian bullseye-backports main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 1: deb http: //ftp.de.debian.org/debian/ bullseye-updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http: //ftp.de.debian.org/debian/ bullseye main contrib non-free 2: deb http: //security.debian.org/ bullseye-security main contrib non-free No active apt repos in: /etc/apt/sources.list.d/various.list Processes: CPU top: 5 of 138 1: cpu: 17.6% command: firefox-esr pid: 2352 mem: 241.7 MiB (12.1%) 2: cpu: 12.3% command: firefox-esr pid: 2219 mem: 462.6 MiB (23.3%) 3: cpu: 11.0% command: yad pid: 12849 mem: 27.2 MiB (1.3%) 4: cpu: 3.0% command: gtkdialog pid: 12806 mem: 27.6 MiB (1.3%) 5: cpu: 2.5% command: xorg pid: 1546 mem: 76.9 MiB (3.8%) Memory top: 5 of 138 1: mem: 462.6 MiB (23.3%) command: firefox-esr pid: 2219 cpu: 12.3% 2: mem: 241.7 MiB (12.1%) command: firefox-esr pid: 2352 cpu: 17.6% 3: mem: 211.0 MiB (10.6%) command: virtualbox pid: 10776 cpu: 0.8% 4: mem: 123.5 MiB (6.2%) command: firefox-esr pid: 2439 cpu: 0.4% 5: mem: 76.9 MiB (3.8%) command: xorg pid: 1546 cpu: 2.5% Info: Processes: 138 Uptime: 1h 17m wakeups: 1 Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: service Compilers: gcc: 10.2.1 alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.19Anyway, I wanted to give the virtualbox version 6.0.24 a try, but it seems to be impossible to install it in antiX21, there exist only versions above 6.1, requiring the vt-x capability of the host CPU:
$ apt-cache policy virtualbox virtualbox: Installiert: 6.1.22-dfsg-2~mx21+1 Installationskandidat: 6.1.22-dfsg-2~mx21+1 Versionstabelle: *** 6.1.22-dfsg-2~mx21+1 500 500 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/bullseye bullseye/main amd64 Packages 100 /var/lib/dpkg/status 6.1.14-dfsg-2~mx19+1 500 500 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/bullseye bullseye/nosystemd amd64 PackagesAlso on the virtualbox download site there doesn’t seem to be a deb package available for bullseye: Virtualbox 6.0.24 download page Last one present is for buster. Moreover the packages available on this site will contain dependencies to systemd I believe. But antiX 21 is bullseye, and no systemd.
I also can’t switch to a different virtualisation program, since all my hdd images containing the complete virtualised windows are specifically from virtualbox. They were created before Microsoft had shut down their update servers for Win2000 and WinXP, and they contain all the service packs. I’ve used them on antiX 17 and antiX 19 already, they ran fine always. Now, when switching to another virtualisation program I’d need starting from scratch with the original Win install medium and the original serial and verification code, but there is no microsoft server anymore to authenticate the genuine microsoft thing the installation process asks for. Moreover this will not restore all the service packs needed for proper functioning.
So it looks I’m stuck in compatibility issues with this new antiX 21 install I can’t solve on my own.
Any help appreciated.Robin
Attachments:
Windows is like a submarine. Open a window and serious problems will start.
techore
No AMD-V on the CPU which you probably figured out. I don’t read Deutsch(?), sorry.
I found older VirtualBox builds at: https://www.virtualbox.org/wiki/Download_Old_Builds
Another option, is build from source but that is a bit of a rabbit hole.
* https://www.virtualbox.org/wiki/Linux%20build%20instructions
* https://www.virtualbox.org/browser/vbox/trunkI wish that I could be more help, but I’ve moved to qemu/kvm using virt-manager. I, believe, kvm is going to require Intel VTx or AMD-V.
christophe
What about this: antiX-17.5 live-usb or frugal from hdd – using virtualbox 5.x to run your old Windows VM. Using this live antiX only for printing.
Not ideal to switch between antiX versions, to be sure. But it should work.- This reply was modified 8 months, 3 weeks ago by christophe.
- This reply was modified 8 months, 3 weeks ago by christophe.
confirmed antiX frugaler, since 2019
andyprough
I’ve installed packages from the VBox site on lots of non-systemd systems, I don’t recall ever having a problem. Maybe I’m just not remembering correctly
Many thanks for all your suggestions.
Actually this CPU probably lacks of the VT-x thing the virtualbox versions available in antiX 21 expect to be present:
lscpu | grep -A 2 -E "(VT-x)"
This command doesn’t come up with an result.Using a separate live antiX explicitely for printing is no choice: Foe each sheet needed to be printed I’d need to shut down the system, restart with an outdated antiX 17 OS, starting a virtualised outdated Windows on it, print the page and shut down the virtualised windows and the antiX 17 afterwards and reboot the true recent antiX 21 OS to proceed work. Not exactly what I’d call a convenient and fast workflow.
Printing directly from within the virtualised windows running directly on the default OS is different, there you can transfer everything to be printed directly via clipboard or via a common transfer folder in no time, while the virtualised windows is waiting paused until needed. This way you can print anything you need in no time. whenever you want.
Great to read there are no systemd dependencies when installing the packages from the original virtualbox download page. So I’ll give this a try.
Main problem: The needed package of virtualbox Version 6.0.24 is only available up to buster, while antiX 21 is based on bullseye. Anyway, I’ve learned you can sometimes force install older packages successfully, maybe some specific features will not work properly.
I tried the following:
sudo apt-get install './virtualbox-6.0_6.0.24-139119~Debian~buster_amd64.deb'
This comes up with missing dependency: libvpx5
Checking this libvpx package shows, this was renamed to libvpx6 in bullseye, and is already installed. Moreover this package contatins some multimedia codecs only, not needed for printing at all. So possibly it is enough to create a dummy package to make things work:sudo apt-get install equivs equivs-build libvpx5.controlWithin the control file I replaced the package-name to libvpx5 and the version to 1.6.0
Then:equivs-build libvpx5.control sudo apt-get install './libvpx5/libvpx5_1.6.0_all.deb'Now again I tried to install the virtualbox 6.0.24 package from buster:
$ sudo apt-get install './virtualbox-6.0_6.0.24-139119~Debian~buster_amd64.deb' Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Hinweis: »virtualbox-6.0« wird an Stelle von »./virtualbox-6.0_6.0.24-139119~Debian~buster_amd64.deb« gewählt. Die folgenden zusätzlichen Pakete werden installiert: libpython2-stdlib libpython2.7-minimal libpython2.7-stdlib python-is-python2 python2 python2-minimal python2.7 python2.7-minimal Vorgeschlagene Pakete: python2-doc python-tk python2.7-doc binfmt-support Die folgenden Pakete werden ENTFERNT: droopy-antix python-is-python3 Die folgenden NEUEN Pakete werden installiert: libpython2-stdlib libpython2.7-minimal libpython2.7-stdlib python-is-python2 python2 python2-minimal python2.7 python2.7-minimal virtualbox-6.0 0 aktualisiert, 9 neu installiert, 2 zu entfernen und 3 nicht aktualisiert. Es müssen noch 3.977 kB von 107 MB an Archiven heruntergeladen werden. Nach dieser Operation werden 243 MB Plattenplatz zusätzlich benutzt. Möchten Sie fortfahren? [J/n] j Holen:1 http://ftp.de.debian.org/debian bullseye/main amd64 libpython2.7-minimal amd64 2.7.18-8 [396 kB] Holen:2 http://ftp.de.debian.org/debian bullseye/main amd64 python2.7-minimal amd64 2.7.18-8 [1.322 kB] Holen:3 http://ftp.de.debian.org/debian bullseye/main amd64 python2-minimal amd64 2.7.18-3 [34,2 kB] Holen:4 http://ftp.de.debian.org/debian bullseye/main amd64 libpython2.7-stdlib amd64 2.7.18-8 [1.865 kB] Holen:5 http://ftp.de.debian.org/debian bullseye/main amd64 python2.7 amd64 2.7.18-8 [311 kB] Holen:6 http://ftp.de.debian.org/debian bullseye/main amd64 libpython2-stdlib amd64 2.7.18-3 [21,2 kB] Holen:7 http://ftp.de.debian.org/debian bullseye/main amd64 python2 amd64 2.7.18-3 [24,5 kB] Holen:8 http://ftp.de.debian.org/debian bullseye/main amd64 python-is-python2 all 2.7.18-9 [2.940 B] Holen:9 ./virtualbox-6.0_6.0.24-139119~Debian~buster_amd64.deb virtualbox-6.0 amd64 6.0.24-139119~Debian~buster [103 MB] Es wurden 3.977 kB in 6 s geholt (682 kB/s). Vorkonfiguration der Pakete ... (Lese Datenbank ... 233204 Dateien und Verzeichnisse sind derzeit installiert.) Entfernen von droopy-antix (0.1.8) ... Entfernen von python-is-python3 (3.9.2-1) ... Vormals nicht ausgewähltes Paket libpython2.7-minimal:amd64 wird gewählt. (Lese Datenbank ... 233192 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../0-libpython2.7-minimal_2.7.18-8_amd64.deb ... Entpacken von libpython2.7-minimal:amd64 (2.7.18-8) ... Vormals nicht ausgewähltes Paket python2.7-minimal wird gewählt. Vorbereitung zum Entpacken von .../1-python2.7-minimal_2.7.18-8_amd64.deb ... Entpacken von python2.7-minimal (2.7.18-8) ... Vormals nicht ausgewähltes Paket python2-minimal wird gewählt. Vorbereitung zum Entpacken von .../2-python2-minimal_2.7.18-3_amd64.deb ... Entpacken von python2-minimal (2.7.18-3) ... Vormals nicht ausgewähltes Paket libpython2.7-stdlib:amd64 wird gewählt. Vorbereitung zum Entpacken von .../3-libpython2.7-stdlib_2.7.18-8_amd64.deb ... Entpacken von libpython2.7-stdlib:amd64 (2.7.18-8) ... Vormals nicht ausgewähltes Paket python2.7 wird gewählt. Vorbereitung zum Entpacken von .../4-python2.7_2.7.18-8_amd64.deb ... Entpacken von python2.7 (2.7.18-8) ... Vormals nicht ausgewähltes Paket libpython2-stdlib:amd64 wird gewählt. Vorbereitung zum Entpacken von .../5-libpython2-stdlib_2.7.18-3_amd64.deb ... Entpacken von libpython2-stdlib:amd64 (2.7.18-3) ... libpython2.7-minimal:amd64 (2.7.18-8) wird eingerichtet ... python2.7-minimal (2.7.18-8) wird eingerichtet ... Linking and byte-compiling packages for runtime python2.7... python2-minimal (2.7.18-3) wird eingerichtet ... Vormals nicht ausgewähltes Paket python2 wird gewählt. (Lese Datenbank ... 233936 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../python2_2.7.18-3_amd64.deb ... Entpacken von python2 (2.7.18-3) ... Vormals nicht ausgewähltes Paket python-is-python2 wird gewählt. Vorbereitung zum Entpacken von .../python-is-python2_2.7.18-9_all.deb ... Entpacken von python-is-python2 (2.7.18-9) ... Vormals nicht ausgewähltes Paket virtualbox-6.0 wird gewählt. Vorbereitung zum Entpacken von .../virtualbox-6.0_6.0.24-139119~Debian~buster_amd64.deb ... Entpacken von virtualbox-6.0 (6.0.24-139119~Debian~buster) ... libpython2.7-stdlib:amd64 (2.7.18-8) wird eingerichtet ... python2.7 (2.7.18-8) wird eingerichtet ... libpython2-stdlib:amd64 (2.7.18-3) wird eingerichtet ... python2 (2.7.18-3) wird eingerichtet ... python-is-python2 (2.7.18-9) wird eingerichtet ... virtualbox-6.0 (6.0.24-139119~Debian~buster) wird eingerichtet ... Lege Gruppe »vboxusers« (GID 119) an ... Fertig. Trigger für hicolor-icon-theme (0.17-2) werden verarbeitet ... Trigger für man-db (2.9.4-2) werden verarbeitet ... Trigger für shared-mime-info (2.0-1) werden verarbeitet ... Trigger für mailcap (3.69) werden verarbeitet ... Trigger für desktop-file-utils (0.26-1) werden verarbeitet ... Writing Menu: jwm Writing Menu: fluxbox Writing Menu: icewmOk, this removes droopy-antix, which shouldn’t happen, since droopy-antiX shouldn’t depend on the convenience package python-is-python3., but anyway, I can live with this.
The installer created a new user group “vboxusers”, so I had to add my user to this group (can be done in antiX control center or alternatively simply on console)
So the package installed fine on antiX 21, and I’ll report soon whether the virtualbox program itself starts and works flawlessly.
Windows is like a submarine. Open a window and serious problems will start.
marcelocripe
lscpu | grep -A 2 -E “(VT-x)”
This command doesn’t come up with an result.
Please try these commands Matheus taught:
lscpu | grep -A 2 -E AMD-V
or
lscpu | grep -A 2 -E VT-x
Still heavy trouble with virtualbox.
The issues are way more heavy I’d have expected. There actually seems to exist no way to get virtualbox working on any of my machines anymore, after having used this program for many years without any issues. Since I have many containers in use, there it is no option to switch to another virtualisation program.
On antiX 21, 64 bit:
In the antiX 21 repos are only versions above 6.1.x available which require machines with either amd-v or vt-x. The last version running on machines without this special feature was 6.0.24, but this is not available neither from the antix, mx or debian repos. It can be only installed on buster, not on bullseye. I tried to force install the buster package on antiX 21 as described some postings above, but after installing fine the virtualbox UI won’t come up, while the vboxdrv is loaded at system start properly. The message is:Das COM-Objekt für VirtualBox konnte nicht erzeugt werden. Die Anwendung wird nun beendet. Details: Callee RC: NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154)Also compiling the package from source on antiX 21 stops with errors at some point:
fatal error: linux/smp_lock.h: Datei oder Verzeichnis nicht gefunden 141 | # include <linux/smp_lock.h> | ^~~~~~~~~~~~~~~~~~ compilation terminated.So I thought I’d have better success when running it on the 32bit notebook with antiX 19 32bit based on buster, since apt reported a virtualbox version to be avialable:
$ apt-cache policy virtualbox virtualbox: Installiert: (keine) Installationskandidat: 5.2.4-dfsg-1~mx17+1 Versionstabelle: 5.2.4-dfsg-1~mx17+1 500 500 https://mirror.eu.oneandone.net/linux/distributions/mx/packages/antix/buster buster/main i386 PackagesOK, but nevertheless it won’t install:
$ sudo apt-get install virtualbox Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass Sie eine unmögliche Situation angefordert haben oder, wenn Sie die Unstable-Distribution verwenden, dass einige erforderliche Pakete noch nicht erstellt wurden oder Incoming noch nicht verlassen haben. Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen: Die folgenden Pakete haben unerfüllte Abhängigkeiten: virtualbox : Hängt ab von: python3 (< 3.6) aber 3.7.3-1 soll installiert werden Hängt ab von: python3.5 ist aber nicht installierbar Hängt ab von: libgsoap10 ist aber nicht installierbar Hängt ab von: libpython3.5 (>= 3.5.0~b1) ist aber nicht installierbar Hängt ab von: virtualbox-qt (= 5.2.4-dfsg-1~mx17+1) soll aber nicht installiert werden E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete.And on the virtualbox download site there are the very last 32bit packages available for “stretch” only while “buster” is missing. All packages for buster are 64bit only.
So, how can I boot into all my virtualbox containers I’m using for so many years now?
It’s a no-go I can’t access them anymore. What’s going on here?Would it be possible to have packages of the last version running on machines without amd-v or vt-x (which is 6.0.24) present in the 64 bit repos of antiX 21 (and antiX 22) so they can be installed by apt again simply? That would be great.
Or do I actually have to downgrade back to antiX 17 both machines now? (No Idea whether this would help, but it would cause a lot of trouble with other programs like Internet browsers probably)
Windows is like a submarine. Open a window and serious problems will start.
anticapitalista
There are some older Virtualbox debs here (6.0.12):
http://repo.antixlinux.com/archive/virtualbox-5/virtualbox/
They *might* work
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Many thanks, anticapitalista! I’ll check them out immediately. You are right, 6.0.12 looks promising, maybe it installs and runs on either the 32 ore 64 bit machine.
Windows is like a submarine. Open a window and serious problems will start.
christophe
Check this out, if nothing else works:
https://shallowsky.com/blog/linux/migrate-virtualbox-to-qemu.htmlconfirmed antiX frugaler, since 2019
Check this out…
Many thanks for your hint. Unfortunately this requires to have a running instance of virtualbox at hand, since the needed raw images are to be created from the vdi files from within virtualbox beforehand. The other issue which will be very difficult to handle is the different type of hardware quemu emulates. All the images of different operating systems expect the hardware emulated by virtualbox and won’t be able to boot anymore on qemu, even after conversion of the hdd image files to the proper qemu format.
Right now I’m still trying to force install the 6.0.12 version of virtualbox on antiX 21 on the 64 bit machine as anticapitalista suggested above. Apt installation comes up with some complaints about python version mismatch (expects 3.7 but can get only 3.9 on antiX 21).
apt-get install './virtualbox-dkms_6.0.12-dfsg-1~mx19+1_all.de' './virtualbox-qt_6.0.12-dfsg-1~mx19+1_amd64.deb' './virtualbox_6.0.12-dfsg-1~mx19+1_amd64.deb' ... Die folgenden Pakete haben unerfüllte Abhängigkeiten: virtualbox : Hängt ab von: python3 (< 3.8) aber 3.9.2-3 soll installiert werden Hängt ab von: python3.7 ist aber nicht installierbar Hängt ab von: libgsoap-2.8.75 ist aber nicht installierbar Hängt ab von: libpython3.7 (>= 3.7.0) ist aber nicht installierbar E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete.I believe the differences between these python versions are not that big, it could be enough already to change the respective version numbers in the control file while manually repacking the original package. When looking into its changelog the same goes probably also for libgsoap-2.8.104 which is available on antiX 21 instead of 2.0.75. So let’s see whether this works now finally.
Windows is like a submarine. Open a window and serious problems will start.
OK, after walking endless pathways and climbing some hills and valleys up and down, all in vain, I finally had to stop trying to install Virtualbox on antiX 21 on this machine. After it looked promising first while trying to compile from the sources, applying successfully a first patch, it ran into heavy issues due to code removal in sources later. I had to backport patches not meant for this version, and finally ran into kernel incompatibilities I can’t resolve, since I’m not experienced in compiling at all. Don’t even understand most of the cryptic error messages it shows to me. Main issue is: There is a gap between the maximum virtualbox version running on this CPU and the minimum available source versions for the antiX 21 system base bullseye. Something like this must be compiled and patched by an experienced programmer.
So next I tried to use qemu instead and convert one of the smaller 2.5G containers (conversion of the big 10G and 25G containers would have been another issue due to limited disk space). But poor result: Existing windows guest living in the container would come up in emegrency mode only, and not recognising the CD/DVD drive, so no way to update its drivers to the switched virtual environment from original Windows CD. Tried to reinstall Windows from scratch. Qemu needed more than 5 hours for this Windows installation, this was the slowest install I’ve seen ever, even on oldschool i386 66MHz bords it was faster than on this more modern powerful 64bit CPU running 2GHz. And after a couple of the windows typical needed reboots during setup, finally the success message of completed installation and configuration came up, asking me for a last time to reboot. Well, now this fresh installed Win would boot into bsod only. Repeated the procedure using another type of virtual CPU, all in vain. So I dropped this quemu thing also. Simply doesn’t work here.
I ended up downgrading to antiX 19.5 full 64bit.
Then all of a sudden everything went smoothly. Had to apt upgrade and kernel update the system again, reinstall all software needed, a process which takes hours always.
Then I installed virtualbox simply from apt, and now it came up properly, and accepted all my existing guest containers. Had to set up the parallel port properly using VBoxManage modifyvm …, add my user to vboxusers, rmmod the lp service, and viola! Finally I can print again and access the silly old windows-only software.So Christophe, you were right from the beginning:
What about this: antiX-17.5 live-usb or frugal from hdd – using virtualbox 5.x to run your old Windows VM
Not a downgrade as far as to 17, but still downgrading was the single solution.
Many thanks to all here having been lending a helping hand, giving advice!
Drawback of this story is: I won’t have a running antiX 21 system anymore now for testing purposes.
Even when it works for now, I need to fix this issue on antiX 21 at latest before antiX 19 will be EOL, maybe earlier, if some other programs stop security upgrading on buster based systems some day.Windows is like a submarine. Open a window and serious problems will start.
- You must be logged in to reply to this topic.
