Search Results for 'startx'

[Member schnabel]

Ok, there was a typo in Xwrapper.conf. I had needs_root_right, not needs_root_rights.

Why is there a need for all that at all? I never had any problems running startx without such?

[Member schnabel]

Anonymous wrote:

search box on antixforum main page
query: startx

the likely solution is described within a post (#66806) by anticapitalista, dated Sept 9, 2021

That is what i did, and if i didn’t miss something, it is exactly what i described in my question. And it doesn’t work.

[Anonymous]

search box on antixforum main page
query: startx

the likely solution is described within a post (#66806) by anticapitalista, dated Sept 9, 2021

I installed xorg-server-xorg-legacy, startx still fails
I edited /etc/X11/Xwrapper.config,
both

needs_root_rights = yes
needs_root_rights=yes

give an error (key not available.

the part from ~/.local/share/xorg/Xorg.0.log

[    21.387] (EE) modeset(0): drmSetMaster failed: Permission denied
[    21.387] (EE)
Fatal server error:
[    21.387] (EE) AddScreen/ScreenInit failed for driver 0
[    21.387] (EE)
[    21.387] (EE)

startx as root works fine.

thanks in advance

Almost done with tests with live CD/DVD (optical media), before proceeding to try testing with live USB.

However there’s one last issue I saw:
If booting *without* the “toram” boot option, X always fails to load. When finishing booting system starts in command line, and typing “startx” results in error that “failed to connect to server”, or something like that.
With the “toram” option, there have been no problems until now.

Current rig:

demo@antix1:~
$ inxi -Fxz
System:
  Host: antix1 Kernel: 4.9.0-264-antix.1-amd64-smp x86_64 bits: 64 
  compiler: gcc v: 8.3.0 Desktop: IceWM 2.3.4 
  Distro: antiX-19.4_x64-base Grup Yorum 20 May 2021 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Laptop System: Gateway product: NE-522 v: V2.02 serial: <filter> 
  Mobo: Gateway model: NE-522 v: V2.02 serial: <filter> UEFI: Insyde v: 2.02 
  date: 05/03/2013 
Battery:
  ID-1: BAT0 charge: 1.6 Wh condition: 23.4/37.0 Wh (63%) 
  model: SANYO AL12A32 status: Charging 
CPU:
  Topology: Dual Core model: AMD E1-2500 APU with Radeon HD Graphics 
  bits: 64 type: MCP arch: Jaguar rev: 1 L2 cache: 1024 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 5589 
  Speed: 1200 MHz min/max: 800/1400 MHz Core speeds (MHz): 1: 800 2: 1000 
Graphics:
  Device-1: AMD Kabini [Radeon HD 8240 / R3 Series] 
  vendor: Acer Incorporated ALI driver: radeon v: kernel bus ID: 00:01.0 
  Display: server: X.Org 1.20.4 driver: ati,radeon 
  unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz 
  OpenGL: 
  renderer: AMD KABINI (DRM 2.49.0 4.9.0-264-antix.1-amd64-smp LLVM 7.0.1) 
  v: 4.5 Mesa 18.3.6 direct render: Yes 
Audio:
  Device-1: AMD Kabini HDMI/DP Audio vendor: Acer Incorporated ALI 
  driver: snd_hda_intel v: kernel bus ID: 00:01.1 
  Device-2: AMD FCH Azalia vendor: Acer Incorporated ALI 
  driver: snd_hda_intel v: kernel bus ID: 00:14.2 
  Sound Server: ALSA v: k4.9.0-264-antix.1-amd64-smp 
Network:
  Device-1: Qualcomm Atheros QCA8171 Gigabit Ethernet 
  vendor: Acer Incorporated ALI driver: alx v: kernel port: 2000 
  bus ID: 01:00.0 
  IF: eth0 state: down mac: <filter> 
  Device-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter 
  vendor: Lite-On driver: ath9k v: kernel port: 2000 bus ID: 05:00.0 
  IF: wlan0 state: up mac: <filter> 
  Device-3: Lite-On Atheros AR3012 Bluetooth type: USB driver: btusb 
  bus ID: 4-2:5 
Drives:
  Local Storage: total: 223.57 GiB used: 591.6 MiB (0.3%) 
  ID-1: /dev/sda vendor: A-Data model: SU650 size: 223.57 GiB 
Partition:
  ID-1: / size: 3.63 GiB used: 591.6 MiB (15.9%) fs: overlay source: ERR-102 
Sensors:
  System Temperatures: cpu: 53.5 C mobo: 37.0 C gpu: radeon temp: 53 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 125 Uptime: 3h 19m Memory: 5.28 GiB used: 336.0 MiB (6.2%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 
  inxi: 3.0.36 
demo@antix1:~
$

In other few tested rigs this issue doesn’t happen.

Oh, and on a brief side note, independently of this issue, I tried @Xecure’s past advise regarding usage of the “toram” option. Supposedly one needs to add the “menus=s” boot option in conjunction with it.
However, this did absolutely nothing, and not using the option still boots the system seemingly fine.
Also, this boot option is not mentioned at all in the Antix wiki, and only barely mentioned in the FAQ website. And there, it mentions nothing about “menus” boot option accepting any kind of value…
Was there a reason behind it?

Thanks again.

Some users don’t want to use any login manager and prefer startx after logging in at the console (as user).
For this to work, install xserver-xorg-legacy
Then you should be able to startx as user.
If not, edit /etc/X11/Xwrapper file to include these lines:

allowed_users = console
needs_root_rights = yes

Apparently, you will not need to edit that file if you first login as user, su to root then

apt install --reinstall xserver-xorg-legacy

However, this will not give you the same desktop as default antiX with login manager. It will give you the min or minimal options listed below.

Instead of typing startx, you should type something like this:

startx /usr/local/bin/desktop-session icewm

Available options:

rox-icewm
icewm
zzz-icewm
min-icewm
minimal-icewm
rox-fluxbox
fluxbox
zzz-fluxbox
min-fluxbox
minimal-fluxbox
rox-jwm
jwm
zzz-jwm
min-jwm
minimal-jwm
herbstluftwm

• This topic was modified 1 year, 8 months ago by anticapitalista. Reason: Extra options added
• This topic was modified 1 year, 8 months ago by anticapitalista.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Forum Admin anticapitalista]

@fungalnet – this thread is about sysVinit beta2 version.
Are you testing that version?
If so, those runit files come from upstream Debian ssh and acpid packages (particularly acpid as it depends on runit-helper)

Install xserver-xorg-legacy for startx to work without a login manager

Also see this post: https://www.antixforum.com/forums/topic/startx-on-antix-base-and-full/
Running live, I was able to boot to init 3 (just add 3 to the boot menu line and remove the splasht ‘cheat’).
Then I logged in as user, su to root and installed xserver-xorg-legacy (I didn’t need to edit Xwrapper file).
startx gives what we call our min/minimal-wm option.
I then removed slimski, elogind and the desktop still works ok.
Can’t get rid of dbus I’m afraid.

• This reply was modified 1 year, 8 months ago by anticapitalista. Reason: Added more info

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Forum Admin Dave]

What are the group assignments on the normal user under the net install?
Maybe that user is not part of a group that it should be; perhaps video?

Aside from that there may be a permissions issue elsewhere.
Best to try startx as regular user and check / post the output of the X log here.
cat /var/log/Xorg.0.lo

• This reply was modified 1 year, 8 months ago by Dave.

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

I downloaded both antiX-19.4_x64-core.iso and antiX-19.4_386-net.iso .
Then boot them live without persistence, install xorg and fluxbox using cli-aptiX.
Immediately after installation, I login as demo and run startx.
x64-core works fine but 386-net does not, is this a known problem?
If I login as root, both work fine.
Tried install recommended xorg-legacy-suid-wrapper (can’t recall exact package name) but it still fail.
What do I need to get startx to work in 386-net as non-root?

Setting up Linux on my “Chromebox”

In a previous document I wondered if I should purchase a Chromebook since I was curious if it would be a good fit for me and they are not very expensive in general. My conclusion in that document was that I would put off buying a Chromebook since I was more likely to use Linux and I didn’t want to be limited by the Google way of computing in “the cloud”.

(Here’s my thread with that document: https://www.antixforum.com/forums/topic/should-i-get-a-chromebook/)

Since I have spent several years experimenting with Linux I was comfortable with experimenting with the Chromium OS, the open source portion of the Google Chrome OS that comes installed on Chromebooks. Chromium OS is not exactly the same as Chrome OS but it is close enough for me to get a good feel for what is possible with a Chromebook. I have several old computers in my collection and I chose one to be my stand in for what I may have purchased had I decided to buy a used Chromebook off of Ebay.

I chose to install CloudReady on my old HP All-in-One desktop, with an AMD Dual Core processor at up to 3.6Ghz and 8GB of RAM. This is now my “Chromebox” in my lab and takes its place alongside several other old computers running various operating systems, mostly Linux and Windows.

When I first started with this experiment I was hoping I could install antiX linux on this same box and have both operating systems dual booting, just like I have done with several other machines that dual boot multiple operating systems. My favorite Linux OS is antiX and I had already installed both antiX and MX on this old box successfully. Now, can I add Chromium OS to the line up?

I quickly found out that ChromiumOS/CloudReady does not support dual booting. In fact, Chrome OS wants to take over the entire hard drive at time of installation. For my first attempt I chose to remove the hard drive and replace it with another hard drive so that I could go back to my antiX/MX dual boot system if this Chrome OS install didn’t work. I booted with the CloudReady USB and ran the installer to the hard drive. It worked. I now had a fully operational ChromeOS/ChromiumOS “Chromebox”. I played around with it and I ended up at the conclusion I mentioned above, that I preferred Linux to ChromeOS.

But now, what about installing Linux as a kind of virtual machine inside ChromiumOS? I had read that the current ChromeOS Chromebooks do support running Linux by using a virtual machine instance. But after some research I found out that this is not a feature of ChromiumOS, it only works on real ChromeOS Chromebooks. However, I did find an alternative called “Crouton” that installs multiple Linux instances using chroots. The results would be similar to what is offered on actual Chromebooks. So, I tried it.

I installed Crouton on my ChromiumOS Chromebox and then installed an instance of Ubuntu linux with the XFCE desktop. It worked. I had a full version of Linux running on the Chromebox. But it was Ubuntu. I had already decided that Xubuntu was my best Ubuntu option for these old machines but Crouton did not offer to install Xubuntu. Crouton is a collection of scripts and it only supports a small number of Linux distros by default, basically only three -Ubuntu, Debian, and Kali. But it does work. I had Ubuntu Linux running and it was not a bad experience. I could switch back and forth between CloudReady and Ubuntu by using a hot-key combination.

But what about antiX or MX? Could I get these installed with crouton and get the same experience as with Ubuntu? No. Crouton is not made to install just any linux distro. And while it may be technically possible for the crouton scripts to be modified to support alternate distros it was well beyond my skill level. I needed something that was already setup and working. I decided that I would be better served by a dual boot installation of ChromiumOS so that I could choose to boot into antiX instead of ChromeOS.

After more research I was able to learn how to dual boot CloudReady with another OS. There are also other alternatives for installing ChromiumOS besides CloudReady that have been reported to work for dual booting. But I decided to stay with CloudReady. The trick to dual booting with CloudReady is to use a separate hard drive for CloudReady and keep the other OS’s on another hard drive. CloudReady will take over one complete hard drive but it will not touch your other hard drive if you enter the commands correctly. I added a removable USB 3.0 hard drive I had available and installed CloudReady to that removable drive and kept the other hard drive with my multi-boot setup of Windows/antiX/MX/Xubuntu.

After installing CloudReady I rebooted the machine and it came up with CloudReady and I continued with my setup of ChromiumOS/CloudReady. But what happened to my Grub boot menu for antiX? I restarted and used the ESC key to get a boot menu and then selected the internal hard drive instead of the external USB hard drive. I was able to get back to my Grub menu. Now I can run antiX instead of CloudReady when I want to. My “Chromebox” is now dual boot. It’s a little clunky at boot time but it works.

Now, back to CloudReady and Crouton to see what I can do with Linux from inside the ChromeOS. I was able to install several versions of Linux as chroots. I also was able to install one instance that allows me to run Linux applications inside a ChromeOS window or tab. It all integrates pretty well. The only problem is that it has to be either Ubuntu, Debian, or Kali.

I managed to modify one of the Ubuntu chroots to simulate Xubuntu. It is not the Xubuntu distribution but it is close and gives me a familiar interface. I started with Ubuntu 16.04 with XFCE. Then I upgraded within the chroot to version 18.04 and then updated the instance using the crouton scripts. Then I modified the theme and added the Whisker Menu. The result is a version of Ubuntu Bionic that approximates Xubuntu Bionic. I will further attempt to update to the 20.04 LTS version. But I think I will leave this Ubuntu 18.04 chroot as is and setup another chroot for the current 20.04 version.

Since I cannot get antiX installed I attempted to install Debian with IceWM and try to approximate the antiX setup. I installed a Debian Sid chroot with only the Xorg/Xiwi target and no desktop environment. Once it was installed I tested running a Linux app from this Debian chroot inside of a ChromeOS window. It worked! This is proof of concept that I can run both ChromeOS apps and Linux apps at the same time in this Chromebox.

Now I continued to try and setup the IceWM windows manager and some other packages that I regularly use in antiX. I installed the icewm package and then read up on how to set up the configuration scripts to launch IceWM using startx. I had trouble at first since I didn’t understand that this Debian chroot had been setup to run inside of ChromeOS but did not yet support a full X server by itself. When I tried to launch IceWM all I got was a long wait followed by error messages. Eventually I figured out that I could launch IceWM from within ChromeOS and it worked to start an instance of Debian in a window inside ChromeOS. Fascinating!

Now I have two types of Linux installed in my Chromebox. The first type is running in a separate full screen instance and I can switch between Linux and ChromeOS using hot-keys. The second type is running inside of a ChromeOS Window/Tab as if it were just another app inside Chrome. In both cases I have to use the Logout/Shutdown options from within the chroot to stop the Linux instance from running.

So, have I changed my mind about Chromebooks? I mean, I can now run both Linux and ChromeOS at the same time on the same machine. That’s pretty cool, right? Yes, it’s cool. And it is a fun experiment. But I have not changed my mind about Chromebooks/Chromeboxes. For me, they are still not necessary. I can do most of the same things using ChromiumOS on one of my old machines. And Linux is a far superior platform for my own computing needs. And the fact that I can’t install just any Linux distro I choose is a deal breaker for me. And I have learned that Crostini has the same limits. The Linux instances inside ChromeOS are limited and restricted to what is supported by these add-ons. But I want antiX dammit! I will stay with my machines that allow dual booting. I will keep ChromiumOS so I can stay in touch with what is happening in the Chromebook universe. But until I can install antiX on a Chromebook I will not be buying a Chromebook – at least not for the Linux features.

Seaken64

P.S. One more thing that annoys me about Chromebooks. No secure local files. ChromeOS really wants us to use cloud storage. The OS is designed to sacrifice local storage. In fact, until recently you could not keep local files on your Chromebook without the threat of losing them to an OS system reset. I prefer to have the choice to store files locally without the threat of the OS deleting them according to their own rules. I’ll set the rules for my own files thank you.

• This topic was modified 1 year, 8 months ago by rokytnji.

I have a problem in live usb in uefi mode: startx don’t launch.

I have tested the boot entry x64-full Failsafe in advanced option menu. Works fine!

So, i have modified my customized entry to keep the persistance:

Key e
Add failsafe and bootsave:
linux /antix/vmlinuz quiet splasht disable=lxF failsafe bootsave …
and F10.
solved.

But I have not tested the upgrade of the kernel …

Linux on line
Windows off line

[Member Laurent]

I have a little problem i don’t understand:
When I launch a live usb in UEFi mode in my computers, startx don’t launch. Tested on a Eeepc 1015BX and a MSI Z370M.
Usb key made vith Live-usb-maker on Debian.
No reproductible in Virtualbox or vmware workstation.

In attachement, the log of xorg.O.log.

Thanks for a lead to investigate.

• This reply was modified 1 year, 9 months ago by Laurent.

Attachments:

1. Xorg.0.txt

Linux on line
Windows off line

[Member Xecure]

I will explain things so you understand what your are doing, and not only trying bootcodes.

For a graphic card to work it needs 2 things:
1. The kernel module related to that graphic device (kernel driver).
2. The Xorg module to render graphics to the Xorg/X11 graphic server (xorg video driver).

When running inxi -G, you are asking inxi to display all information it can find related to the graphic devices (hardware), the related kernel module that were loaded (and are being use) for this hardware to communicate with the kernel, and the module(s) xorg is using to draw to your screen.
For your example in OpenSUSE:

Graphics:
  Device-1: Matrox Systems MGA G200EV vendor: IBM driver: mgag200 v: kernel 
  bus ID: 07:00.0 chip ID: 102b:0530 
  Device-2: AMD Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] 
  vendor: PC Partner Limited driver: radeon v: kernel bus ID: 15:00.0 
  chip ID: 1002:6779 
  Display: x11 server: X.org 1.20.3 compositor: kwin_x11 
  driver: ati,modesetting,radeon FAILED: mga unloaded: fbdev,vesa 
  resolution: <xdpyinfo missing> 
  OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.2.4 compat-v: 3.1 
  direct render: Yes 

This is the desired result you want to emulate in antiX, but for some reason it cannot do this automatically. The reason for the problem detecting and configuring the correct drivers out of the box can be many things (different kernel version: opensuse uses 5.13, antiX uses 4.9; different detection on the live USB, etc.).

From the above output, the device 2 is the one that is being used to output video:

Device-2: AMD Caicos [Radeon HD 6450/7450/8450)[…] driver: radeon

You can see that the kernel driver used for this device is called radeon. You can see if it is loaded in any linux system with
lsmod | grep radeon
If there is NO output, it is not loaded. You will need to load it with
sudo modprobe radeon

The next part is the module used for Xorg server:

Display: x11 server: X.org 1.20.3 […] driver: ati,modesetting,radeon

You can see that there are 3 xorg video modules loaded: ati, modesetting and radeon
modesetting refers to the ability of the kernel to manage the display resolution and other video related properties. It works much better in newer kernels and also on newer hardware. For some devices, it is recommended to disable it at boot. You can do this using the boot parameter nomodeset, to instead use the xorg modules and not let the kernel try to intervene too much.
nomodeset
You can also force the kernel mode setting to load the correct radeon xorg video driver with the boot parameter
radeon.modeset=1
but probably the thing that is failing in your case is the kernel modesetting feature, so this will probably not work, and it is better to use both nomodeset and disable radeon modesetting
nomodeset radeon.modeset=0

Normally, the radeon module will also load the ati driver, so lets concentrate on the radeon driver.
If you see that the xorg radeon driver isn’t being used by xorg after booting to antiX, you can force it to use it in one of two ways:
A. Using a boot parameter (only works on antiX live system, and before booting):
xorg=radeon
B. Disable X server, (if it is running, meaning you have a graphical interface), create a xorg.conf file specifying that the radeon xorg module must be enabled when starting X server, and then start the xserver again. You can do this from terminal
sudo make-xorg-conf -f radeon -o /etc/X11/xorg.conf
stop slim and xorg server
sudo service slim stop
start it again with
sudo service slim start
or
sudo startx slim

You could try combining both methodes, of disabling the kernel modesetting and also forcing xorg to load the radeon driver
nomodeset xorg=radeon

As you see, there are too many possibilities that may have caused the failure.

If nothing above worked, it is very possible that the older 4.9 linux kernel in the antiX 19.4 ISO doesn’t support so well the video card as the newer 5.X linux kernels. If this was the case, you would need to:
A. Use a different antiX edition, for example with kernel version 4.19, or a community release with kernel 5.10, or the newer antiX-21-beta1, which lets you select in the boot menus the kernel 5.10.
B. (last resort) Install in fail-safe mode, update the kernel to a newer one and then remove the /etc/X11/xorg.conf to let it sart detect on the next boot the correct driver.

The information is here. I hope this can help you understand how to read the inxi output for the graphics cards, and also how to find one of the multiple paths (or try them all) that might help you boot to a working antiX system.

Let me know if there is something I didn’t explain properly, or need clarification.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member stevesr0]

Hi BobC,

You are 100% correct in surmising that I am not a “heavy duty” coder.

I am just a curious (permanent) noobie <g>. I really was puzzled that openbox launches just fine with no entries in init or initrc.

I posted partly to satisfy that curiosity and partly because I saw posts on the AntiX forum from folks who had difficulty getting openbox to launch.

I am pretty satisfied with the system that I have cobbled together. It boots fast and openbox starts “instantaneously” from startx.

How would a respin enable me to learn more about coding than this current system?

Thanks.

stevesr0

• This reply was modified 1 year, 10 months ago by stevesr0.

[Anonymous]

I just looked at man startx and man xinit – I don’t have entries where it says I should.

Okay, now revisit the manpage(s) and take note of the FILES section of doc.
In the absence of per-user config files, it will fallback to loading default init files located under /etc
.
Also, installation of the openbox package(s) may place additional config files and/or XDG -related files.
https://packages.debian.org/bullseye/amd64/openbox/filelist
Yes, just checked ~~ “/etc/X11/openbox” and “/etc/xdg/openbox/autostart”

If you REALLY want x-ray vision into what’s calling what…

sudo apt install strace (if it is not already installed)
man strace

Instead of directly launching startx, you can use a commandline like this (untested)
strace -e trace=process,open,read -o /tmp/startx_tracem.txt startx

then, from within the openbox session, inspect the content of /tmp/startx_tracem.txt

^— If you do, thanks in advance if you will publish the logfile content to pastebin.com and link the URL in a followup post here.