Member

andyprough
I’m wondering if seatd will resolve one thing for me. I removed slim/slimski, and have been logging into my window manager with a tty login script. That was giving me a frozon Xorg, but I read anti’s post about startx, and once I added ‘needs_root_rights=yes’ to /etc/X11/Xwrapper.conf then my xorg was working.
However, I think it’s supposed to be ideal to run xorg as a normal user instead of as root. I read that seatd will
Seat management takes care of mediating access to shared devices (graphics, input), without requiring the applications needing access to be root.
Does this mean that with seatd I will no longer need the ‘needs_root_rights=yes’ line?
Just curious.
Member

rad
While this solution may seem obvious to the people who’ve dealt with X before, I know it’s frustrating to those who haven’t, and ideally prevention is needed. Also, it might be useful to add this to the nvidia driver install recovery wiki page, which amounts to ‘clear the config, then just give up’.
Issue: on my fresh live-usb, I used persistence to install Nvidia drivers (either via the Control Center button or ‘sudo apt install nvidia-driver’, same outcome). Next boot, the init with the circles stalled on the last step, starting X.
Using Alt+F1 to drop into text mode, it asks for the username/password, and running ‘startx’ gives an error about not finding any screens. I also noticed that resolution was low (where on original boot it recognized the 1920×1080 screen).
Solution: The solution was to go into the X config (‘sudo nano /etc/X11/xorg.conf’). Mine showed the driver as being ‘vesa’, so I changed it to ‘nvidia’, saved and started the GUI with ‘startx’, although maybe a persist&reboot is more appropriate once that is confirmed to work.
I’m using antix-21_x64, with a somewhat recent nvidia card (installing driver version 460->).
-
This topic was modified 10 months, 3 weeks ago by rad.
-
This topic was modified 10 months, 3 weeks ago by rad.
Member

stevesr0
Hi Severin,
Perhaps an unhelpful thought…
Can you launch a graphic environment from the login terminal using the startx command?
stevesr0
Forum Admin

Dave
Log into a terminal as root and run the service management tool sysv-rc-conf to disable slimski (remove all x marks).
alternatively if you are always going to run from console… you can remove slimski and run startx /usr/local/bin/desktop-session rox-icewm where rox-icewm is the desktop code. (could also be space-icewm, icewm, rox-fluxbox, etc).
Depending how minimal you want an X session you could also get rid of desktop-session and build your session manually in ~/.xinitrc and run just startx with no arguments
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
Forum Admin

anticapitalista
Try not using failsafe boot
About setting up xserver-xorg-legacy. If you have a login manager you shouldn’t need it.
https://www.antixforum.com/forums/topic/startx-on-antix-base-and-full/
Do you have dbus-x11 installed?
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Member

stevesr0
Hi,
For Sid users with laptops that have wacom digitizers, today’s update broke X on my system. When I started X (startx), the screen turned black and stayed that way.
I removed that package (which was an update from version 0.34 to 1.0) and X worked normally again.
stevesr0
-
This topic was modified 1 year, 1 month ago by caprea.
-
This topic was modified 1 year, 1 month ago by caprea.
Forum Admin

rokytnji
From what I have read. One needs TDM login manager installed if the F1 key in slimski don’t pick it up.
10.3.
How do I replace the standard text login screen with the TDE login screen?
https://www.trinitydesktop.org/faq/configure.php#idm140487997800880
Starting
Manually
To start Trinity from the Linux console:
$ startx /opt/trinity/bin/starttde
See xinit for more.
Graphically
tde-tdebase comes with TDE Display Manager. To start it at boot, enable the tdm.service.
https://wiki.archlinux.org/title/trinity#Graphically
That is all I have to say as I have no interest in running trinity myself.
Member

Pap
Hello antiX community!
I was aware of antiX a long time ago, I even gave it a try in a virtualbox in the past, but since I am not a “distro-hopper” this is the first time I do have real antiX installations. I must say I am quite impressed.
I was always for lightweight distributions and desktops, but antiX brings the term “lightweight” to a another level. After setting up everything to my liking, antiX with a fully functional (and pretty) desktop starts by using ~90 Mb of memory, while the best I have seen so far using other lightweight distributions was around 140 Mb. The difference may seem small, but it’s not if you consider old machines with barely 1 Gb of memory… then every byte counts. Of course a bloated distribution would happily take over 500-1000 Mb of memory (or even more) before even running any application.
Not only that, but antiX was the only distribution that managed to deal with an old eee-PC equipped with the awful Intel GMA500 (“Poulsbo”) GPU. Literally every other distro I tried in that machine was “crawling” to the point of being unusable (and I tried many non-bloated distros). Even moving a window was dead slow, probably because of the lack of drivers for that GPU and/or incompatible kernel. Nevertheless antiX runs decently on that oldie, making it useful again. The only issue I had was startx failed after the first system update (I don’t use display managers so I uninstalled slimski). It didn’t take long to find a solution in antiX forums.
Furthermore, in other distributions I had to get rid of the crappy pulseaudio, which is used by default in most cases – and it is not always easy to get rid of it. With antiX, I didn’t have to bother.
All in all, a great distribution, full of features and yet easy on resources. I am surprised it is not more popular.
Last but not least, a humble (probably stupid) question: In the past, I used Debian “testing” for several years – until they introduced systemd. Back then “testing” was in fact quite stable (with rare, and never serious, issues). I’m not sure what is the situation nowadays, since I didn’t touch a Debian-based distro for more than 10 years. So I kept the default antiX repo configuration intact. Is this the “right”, official antiX way to go? I am asking because antiX gives me the option to add “testing” repos as well. There are some packages I would want up-to-date, and including “testing” repos will do that (nothing serious, no sid or controversial repos). I am ok with occasional issues caused by testing packages, but I also value stability, plus I don’t know how antiX behaves with testing repos in general. If issues are rather frequent, or outright dangerous with antiX, I’ll just stay on the default repos and compile/install the few packages I want up-to-date manually.
Official, dedicated, determined, fanatic systemd HATER since... its release.
Member

stevesr0
Hi Igj100,
So, you can use the laptop as long as suspending is blocked? If so, at the moment the system is usable (except if you are running on battery and need more time than the battery allows without using suspend).
I am not an expert. I just searched a bit and noted many similar complaints of failure to resume after laptop suspend. No single fix works most of the time.
Three other things to try:
1. I had a problem with X after an update that did not include the xserver-xorg-legacy package. Your system is a dual core and might be old enough to require that. Although my system would only go into a black screen when I invoked X using startx, which is different from yours. Installing xserver-xorg-legacy fixed that problem.
2. If #1 doesn’t (magically) work, try the newest available kernel in the antiX/Debian repositories. (as long as you can block suspending, you should have enough time to download and install a new kernel. On reboot, the newest kernel will be used by default.
3. If neither # 1 or 2 work, try live usb distros (antix and another “brand”) to see if this is only an issue with installed distros or with antiX.
stevesr0
Member

techore
I’ve never built xorg without a display manager and hoping someone has done it and can assist.
Using antix-core 21, I have installed xorg (cli-aptiX), xinit, and twm. No display manager. root works fine, but normal user account doesn’t–account has video and the default group memberships from the installer. Farted around with xserver-xorg-legacy as well.
It’s a big ask, but after a week of experimentation, I am not sure that I am even on the right path or that it can be done with the current state of Debian.
-
This topic was modified 1 year, 3 months ago by techore.
-
This topic was modified 1 year, 3 months ago by techore. Reason: solved
Member

scruffyeagle
I was working with this yesterday, trying to figure out what’s wrong. I think the problem is that the Xorg directory is simply missing. Gone, with all its contents too.
——————————-
Here was vital output, when I entered the startx command as root:
Using config directory “/etc/share/x11/xorg.conf.d”
Using system config directory “/usr/share/x11/xorg.conf.d”
) AIGLX: Suspending AIGLX clients for VT switch (EE) Server terminated with error(1).
Closing log file.ornation. (EE) (II
Xinit: giving up
Xinit: Unable to connect to X server: connection refused
Xinit: Server error
————————————–
Here was some output when I entered the startx command as a regular user:
Fatal server error:
(EE) Cannot open log file “/home/spirit/.local/share/xorg/Xorg.0.log”
———————————
Changing directories & doing ls at the command prompt, I found that the /home/spirit/.local/share/Xorg/ directory simply doesnt’ exist – and I suspect based on the error message, that it should.
-
This reply was modified 1 year, 4 months ago by scruffyeagle. Reason: typos
Moderator

caprea
The nouveau driver is already installed and used per default on antiX for nvidia cards, this is normal.It will get blacklisted after installation of nvidia.
If the driver installer from control-centre does not work for you and you want to install the nvidia-driver manually,
first download your matching driver from nvidia side
Then you have to go out of X with Ctrl + Alt + F2from your desktop
or with the method typing letter e on boot screen and adding a 3 to the line beginning with “linux” before booting.
When out of x type
sudo service slim stop
sudo sh NVIDIA-Linux-x86_64_your matching driver.run
You can ignore the “pre-install script failed” warning and choose “Continue anyway”
Answer the questions with yes and after installation do
startx
You might have to blacklist the nouveau manally
echo "blacklist nouveau" | sudo tee -a /etc/modprobe.d/blacklist.conf
reboot and do the procedure second time.
Another way to install the nvidia is to use the sgfxi script, which is also installed per default on antiX,
heres a manual, important point begins at “Running sgfxi directly”
https://smxi.org/docs/sgfxi-manual.htm
This method also might has to be runned twice.
Is there a reason why you are not using the current antiX21, because there for sure the baked in nvidia installer is working fine.
Please let us know more about your hardware for better helping, post
inxi -zv6
or
inxi -Gxx
Member

scruffyeagle
I had a major crash of Antix v19.3 (upgraded). It’s being run on a Dell Precision M6300 laptop, 4GB RAM, 10 GB swap, 27 GB ext4 partition.
I’d been online, reading a long document. When I was done, I tried to update my diary – and, it couldn’t save. The error message box said it couldn’t write to the file. I eventually shut down LibreOffice w/o saving it. I tried opening files on other partitions, but couldn’t close them. The error message said no space on the disk. I tried to reboot, but it couldn’t shut down properly. I shut it down via press-and-hold of the power button. Trying to reboot into Antix 19.3 (up’d), it stalled out at a terminal prompt, unable to start up the X windowing w/ desktop.
There were 2 error lines visible on the screen, which were both the same:
rsyslogd: file ‘4’ write error: No space left on device [v8.1904.0 try https://www.rsyslog.com/e/2027 ]
I tried using “startx”, and it didn’t work. Here’s the output it printed to the screen:
———————————–
Xauth: Unable to write authority file /home/spirit/.Xauthority-n
(EE)
fatal server error
(EE) Cannot open log file /home/spirit/.local/share/xorg.0.log
(EE)
(EE)
Please consult the Xorg Foundation support at http://wiki.x.org for help
(EE)
Xinit: giving up
Xinit: Unable to connect to X server
: connection refused
Xinit: server error
——————————–
I painstakingly copied by hand, the vital info from the screen onto paper. Luckily, I had a second laptop set up with Antix v19.4 – and that’s what I’m using for posting here. Note, that I was under the impression that I still had around 9 GB unused in the partition.
-
This topic was modified 1 year, 4 months ago by scruffyeagle.
Member

stevesr0
Hi male,
Thanks for comments.
I installed isenkram-cli (thanks for the suggestion). It said no firmware was missing.
stevesr0
System:
Host: stevesFujitsu Kernel: 5.15.0-2-amd64 x86_64 bits: 64 compiler: gcc
v: 11.2.0 Desktop: Openbox 3.6.1 dm: startx
Distro: antiX-19.1-sid_x64-net Marielle Franco 18 December 2019
base: Debian GNU/Linux bookworm/sid
Network:
Device-1: Marvell 88E8055 PCI-E Gigabit Ethernet vendor: Fujitsu Limited.
driver: sky2 v: 1.30 port: 2000 bus-ID: 04:00.0 chip-ID: 11ab:4363
Device-2: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network
driver: iwl4965 v: in-tree: bus-ID: 0c:00.0 chip-ID: 8086:4229
rfkill
ID TYPE DEVICE SOFT HARD
0 wlan phy0 unblocked blocked
-
This reply was modified 1 year, 4 months ago by stevesr0.
-
This reply was modified 1 year, 4 months ago by stevesr0.
-
This reply was modified 1 year, 4 months ago by stevesr0.
Forum Admin

anticapitalista
I’m a bit confused.
Is it only fluxbox that you cannot use? What about IceWM, jwm?
Are you using slim or slimski or startx to login?
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.