- This topic has 59 replies, 9 voices, and was last updated Dec 4-4:30 am by BobC.
-
Posts
-
andyprough
I built up from core tonight and built the git version of DWM window manager, these were the packages I added:
arandr xorg xserver-xorg-legacy xserver-xorg-video-intel xserver-xorg-video-vesa xinit roxterm-gtk2 acpi pmount git build-essential patch libx11-dev libxft-dev libxinerama-dev cmst
Worked great.
blur13
I’ve been wondering why there is a Sid iso for core but not base or full. From my understanding, taking the “stable” regular full iso and changing the repos to sid will get you a sid full iso. But if that is the case, wouldnt changing the repos in the stable core iso get you a sid install. So why have a specific sid iso for core?
Maybe we could feature request a sid full antix iso?
Sorry for the jumbled terminology but I hope you can sort of understand what I mean.
olsztyn
Did you do the thing that Christophe said? You have to do it for startx to work:
Edit your /etc/X11/Xwrapper.config.
Add at the bottom of the file:
needs_root_rights=yesYes. I did.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersAlso, if you have an Intel video card, install xserver-xorg-video-intel. See if that’s missing for some reason.
Intel it is. I did not have it. Installed and rebooted.
Still the same error.Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
christophe
I don’t know if this comes from using runit or sid, or not. I only used Sid and runit once for a very short time. So I don’t know if that’s the reason.
I use stable & SysV init. And it just works; as andyprough wrote, adding a few more packages, like listing xservers by name to make sure you have them regardless whether they are part of the xorg metapackage or not.
confirmed antiX frugaler, since 2019
arandr xorg xserver-xorg-legacy xserver-xorg-video-intel xserver-xorg-video-vesa xinit roxterm-gtk2 acpi pmount
At this point I have them. I did not install the rest on your list as they are related to building DWM from git source code.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersBobC
I’ve been wondering why there is a Sid iso for core but not base or full.
Maybe we could feature request a sid full antix iso?
.I could probably burn the antiX 22 sid base 64 runit I created to an .iso if everyone is looking to avoid redoing the process.
Also, I don’t think doing it for full would be that much more difficult.
The only antiX base application package missing was streamlight because of a dependency issue.
- This reply was modified 5 months ago by BobC.
christophe
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server errorWould you post your Xwrapper.config for us to look at? Also, double-check the graphics info. (That’s all I can think to check/re-check.)
confirmed antiX frugaler, since 2019
I don’t know if this comes from using runit or sid, or not. I only used Sid and runit once for a very short time. So I don’t know if that’s the reason.
Perhaps I will redo the same process using Sysvinit Core ISO, just to see if the issue is Runit related. I will use another X61 laptop, so I have both Runit (so far not working) and Sysvinit installs on the same model machines for comparison.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersWould you post your Xwrapper.config for us to look at?
Xwrapper.config has the following:
allowed_users=console
needs_root_rights=yesExactly as prescribed by anticapitalista in one of past posts…
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parametersandyprough
I’m assuming you created an ~/.xinitrc file with the “exec jwm” or whatever window manager line to instruct startx what to do.
One thing I didn’t note is that I did not use runit or Sid last night with my core installation. So it could be one of those like you said.
Brian Masinick
I’m assuming you created an ~/.xinitrc file with the “exec jwm” or whatever window manager line to instruct startx what to do.
One thing I didn’t note is that I did not use runit or Sid last night with my core installation. So it could be one of those like you said.
Yeah, I don’t know about that either. I’ve built antiX Core many times in the past, but with my current network availability, it’s difficult to find ANY wired network solutions around me anymore; therefore I generally need a setup with that built in; otherwise I’m forced to hack my solutions (which I’ve done too), but that takes too much time to do very often (unless I build tools to copy ALL of the stuff I need, and I haven’t done that).
I am, however, using a runit version of antiX 22 right now on my HP-14, and in fact, I had to hack in some firmware, a different kernel, and a few modules to get this one working too.
So yes, it CAN be done, but it takes work, and the specifics will VARY from system to system.In my case, I needed a newer kernel to support my hardware; brought that in, didn’t work. Found that my wireless firmware was missing one file, brought the missing file in; STILL no go. So I went to MX Linux, which I believe was one of the distros working here, looked at everything it had in place, and literally copied every /lib/module, kernel related config and module files, anything else I could spot that interacted or mentioned the kernel or the wireless firmware I was using, and finally got it working; that’s a LOT of work that required hours of research. On top of that, REGULAR MX Linux doesn’t work either; I have to have the AHS (Advanced Hardware Support) stuff for newer images in order to get it working. PCLinuxOS, MX Linux AHS, and openSUSE have these; I got siduction working too; don’t remember if it worked immediately or if I had to do the same prep; seems to me I had to do it to something else; anyway, once I did it on this hardware, it was easier to copy it from a working system, but these kinds of issues are not exactly “portable” to fix; they can differ slightly for each hardware platform in question; some may work out of the box, others need tweaks.
That’s one positive of my Dell Inspiron 5558; it has always worked with my hardware AND software!
--
Brian Masinickchristophe
Up
0
I’m assuming you created an ~/.xinitrc file with the “exec jwm” or whatever window manager line to instruct startx what to do.From my experience, if you only have one wm installed, startx will use it automatically (at least it works that way with jwm).
It’s probably a good way to do it (andyprough’s suggestion), so you can change it up in the future.
confirmed antiX frugaler, since 2019
If you had a matching antiX 22 (ie sysvinit or runit with same architecture 32/64) installed, you could try my packagecomp utility
Thank you BobC…
I am not yet at the point of being able to start X, using Runit SID ISO. About to redo the same process using Sysvinit to see what makes the difference…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersIf you had a matching antiX 22 (ie sysvinit or runit with same architecture 32/64) installed, you could try my packagecomp utility
Thank you BobC…
I am not yet at the point of being able to start X, using Runit SID ISO. About to redo the same process using Sysvinit to see what makes the difference…I converted antiX 22 sid runit core to antiX 22 sid runit base last night and have it completely running. I just wish I’d setup the core userid as demo 🙂
- You must be logged in to reply to this topic.
