- This topic has 7 replies, 3 voices, and was last updated Oct 11-10:41 am by Hazardus.
-
Posts
-
Hazardus
I’m experimenting with some VM stuff and made the mistake of editing my /etc/X11/xorg.conf.in thinking I could just change it back if something went wrong.
Something went wrong.
Now I can’t load into antiX because the desktop manager is not loading. I see a lot of mentions of the wallpaper file not being available for IceWM (I use Rox-IceWM), but it’s there… I can load into console using ctr+alt+6 and type “startx” to get a session going… but it’s completely stock setting with a black background (and any time I try to change the desktop manager it sends me back to console).
FWIW it loads a very oversized version of auditorio-de-tenerife2.jpg wallpaper with nothing else on it (I use[d] lines.jpg). No cursor no icons nada until I switch to console and start the session like that.
Any quick fix? (+ I have images of my antiX partitions from before setting up for VMs.. I can restore individual files/directories from there but would rather not flash the whole partition.)
- This topic was modified 1 year, 6 months ago by Hazardus.
Xecure
Hi.
I can load into console using ctr+alt+6 and type “startx” to get a session going… but it’s completely stock setting with a black background (and any time I try to change the desktop manager it sends me back to console).
root account doesn’t have any desktop-session support.
Something went wrong.
If we can get a bit more info on what you were doing… Were you editing the window manager files?
You can restore the /etc/X11/xorg.conf.in file by reinstalling desktop-defaults-core-antix. Go back to the terminal and reinstall it with
sudo apt install --reinstall desktop-defaults-core-antix
Kill X and restart the slim service
sudo service slim stop
sudo service slim startantiX Live system enthusiast.
General Live Boot Parameters for antiX.No dice. I was trying to disable my dGPU to pass to a VM. I soon learned editing xorg.conf is an outdated practice, saw antiX had similar code in modular pieces, and found a grub option to disable on boot that I’m waiting to try (as soon as this is fixed).
When I run slim start it switches back to the oversized background environment where I can’t see/do anything in it. I edited the xorg.conf.in based on a solution I found online for nVidia cards (mine’s AMD, so I just swapped the ‘nvidia’s for ‘radeon’). I’m only a few months in to Linux and virtual machines. It’s taking a while to learn the ropes.
Please let me know what you need. I’m writing this on my antiX OS but in the ctrl+alt+F6 version (not sure what they’re called). If I do ctrl+alt+F7 it’s the same as slim start; giant wallpaper with nothing to do.
Here’s some random info that might possibly be helpful:
- It says slim started.
- In elogind I’m getting Unknown Option “nsdelegate” (problem with systemd?)
I installed systemd for systemctl to start services for the VM (but it seems antiX does not use this natively?). I can’t even be sure editing the xorg.conf is what started this (though I’m reasonably sure I restarted just before). Below are some outputs that may be of use.
I also sometimes get “Stopping X display manager: slim not running (/var/run/slim.lock not found)” — even though the file is indeed there (contains 4 digits).
Sometimes I get a message saying Slim failed to start <shrug>.
Here is a segment of the xorg log.
[ 164.588] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 164.592] (==) Log file: "/home/account/.local/share/xorg/Xorg.1.log", Time: Sun Oct 10 08:07:13 2021 [ 164.593] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 164.594] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 164.594] (==) No Layout section. Using the first Screen section. [ 164.594] (==) No screen section available. Using defaults. [ 164.594] (**) |-->Screen "Default Screen Section" (0) [ 164.594] (**) | |-->Monitor "<default monitor>" [ 164.594] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 164.594] (==) Automatically adding devices [ 164.594] (==) Automatically enabling devices [ 164.594] (==) Automatically adding GPU devices [ 164.594] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 164.594] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 164.594] Entry deleted from font path. [ 164.594] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 164.594] Entry deleted from font path. [ 164.594] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 164.594] Entry deleted from font path. [ 164.594] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, built-ins [ 164.594] (==) ModulePath set to "/usr/lib/xorg/modules" [ 164.594] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 164.594] (II) Loader magic: 0x564d10ba3e20 [ 164.594] (II) Module ABI versions: [ 164.594] X.Org ANSI C Emulation: 0.4 [ 164.594] X.Org Video Driver: 24.0 [ 164.594] X.Org XInput driver : 24.1 [ 164.594] X.Org Server Extension : 10.0 [ 164.595] (++) using VT number 6 [ 164.595] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31Xecure
For antiX to be stable, light and fast, it doesn’t support systemd at all.
After restoreing the xorg.conf.in, copy over the 10-amdgpu.conf (or 10-radeon.conf, depending on which is the better xorg module for your graphics card) file from /usr/share/X11/xorg.conf.d/ to /etc/X11/xorg.conf.d/ and edit this file to add the screen resolution. Then reboot and see if it works.
I have no idea on how passing a GPU to be used by a virtual machine, so I cannot give any advice there.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.I tried but it’s the same.
I loaded up the partition images I took before making the modifications. On the surface I can’t see anything wrong in any of the directories mentioned so far. I’ll look at it more closely tomorrow.
As much as I’d like to know what caused this problem, I’m about ready to just flash the partitions and reinstall the VM portions… at least that I know can solve it.
anticapitalista
In the future, don’t install systemd or libsystemd0 (or make sure some app doesn’t install it).
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
I can try. I’m having to reference multiple sources since there isn’t a uniform guide. I like antiX for it’s simplicity and high level of customization. Unfortunately most of the information requires searching the forums for posts about similar issues.
I flashed both partitions back to 5 days ago. Very glad I made those backups.
The problem was definitely in the root portion. I used a clone of root with the active /home partition (plus flashed /home first and checked again).
I’ll go slower this time reinstalling VMs. Hopefully I can use $ service <name> start to accomplish the same thing as systemctl.
Xecure was close. I technically have 3 monitors running 4 outputs — the large wallpaper I had was the result of SLiM stretching across all 3 (one of them is generally turned off). Once I reinstalled the VM portions the same thing happened again.. since my monitor settings were default (using all 3), I kept having windows appear on the one that was off so I unplugged it. THEN I could see the log in dialogue.
Previously slim logged in automatically. Something in the VM set changed that- still no idea what.
But by changing the slim configuration file I was able to restore the desired functionality and have the VM portions running.
- You must be logged in to reply to this topic.
