antiX will not set the native monitor resolution

[Member ant_222]

Helpful

Up

0

::

I have just reinstalled antiX, but forgot to activate the dbus service in the installer. Now I am stuck without internet connectivity. Statring it manually does not help. How do I configure dbus for autostart?

[Moderator Brian Masinick]

Helpful

Up

0

::

I don’t remember doing anything special but start over and watch each prompt.

--
Brian Masinick

[Moderator BobC]

Helpful

Up

0

::

Brian’s instructions copied from the Liquorix site were the ones I used originally. The one thing none of us can tell you is if this will solve the problem you are having. But its worth a try, I think.

PS: go copy and run the instructions from that site, not here.

Brian Masinick wrote:

https://liquorix.net/

Liquorix Kernel

Liquorix is a distro kernel replacement built using the best configuration and kernel sources for desktop, multimedia, and gaming workloads.

Install

Debian Prerequisites:

curl ‘https://liquorix.net/add-liquorix-repo.sh’ | sudo bash

sudo apt-get install linux-image-liquorix-amd64 linux-headers-liquorix-amd64

• This reply was modified 5 months ago by BobC.

[Member DaveW]

Helpful

Up

0

::

Hi to all,
This thread started because ant_222 has a system that won’t recognize his monitor resolution.
Somewhere along the line, it became focused on attempts to use a later kernel version. I missed the reason for that.

In any case, I had a similar resolution problem with antix21/22 on my eeepc 900. Although this may be a very different machine than the one in question, it might be worth a try. See my thread and eventual solution at:
https://www.antixforum.com/forums/topic/asus-eeepc-900-antix21-display-resoluton-problem/

[Moderator Brian Masinick]

Helpful

Up

0

::

Great suggestion. I hope this is applicable to ant_222.

--
Brian Masinick

[Member DaveW]

Helpful

Up

0

::

The solution for my eeepc is a bit cumbersome, because the OS only recognizes very low resolutions.
However, by adding the line with i915 instruction in Grub (post #91244), many other resolutions became available in xrandr. Perhaps that will be enough for ant_222.

[Moderator BobC]

Helpful

Up

0

::

Those are good suggestions, and you could try each of them separately and see if any of them works. FYI, I don’t have a JasperLake

Good guesses to try…

From davew post:
insmod i915 i915.modeset=1

My successes for skylake:

acpi_osi=!Windows 

and

older kernels i think under 5.13 try i915.preliminary_hw_support=1
newer kernels above 5.13 and under 5.18 try i915.alpha_support=1
newest kernels 5.18 and above try i915.force_probe=4e61

[Member ant_222]

Helpful

Up

0

::

Thanks you for the further suggestions. I will start trying them later today. In the mean time, I am somewhat stuck:

ant_222 wrote:

I have just reinstalled antiX, but forgot to activate the dbus service in the installer. Now I am stuck without internet connectivity. Starting it manually does not help. How do I configure dbus for autostart?

Can you please help me activate the dbus service, which is installed by not loaded at startup? If I fail to fix it quick, I will simply reinstall antiX again, setting the dbus checkbox on the Services tab in the installer. Update: reading runit docs.

[Moderator BobC]

Helpful

Up

0

::

Sorry, I would say start over with a fresh USB would be easiest. That should have nothing to do with the screen resolution.

PS: I don’t think I have needed to change that for internet to work that I recall.

• This reply was modified 5 months ago by BobC.

[Member ant_222]

Helpful

Up

0

::

OK, staring afresh, but stuck at the installation screen with Service Settings (advanced). During the previous installations, I have been able there to select severeal services, such as anacron and dbus, but now the list Common Serivices to Enable is empty (photo). How can I cause the installer to populate it and let me select the ones I need? I am running the installer from a USB stick written in dd mode from antiX-22-runit_x64-base.iso.

• This reply was modified 4 months, 4 weeks ago by ant_222.

[Moderator BobC]

Helpful

Up

0

::

I don’t think dd can make a good flashdrive to boot and run antiX live.

You should use antiX’s Live USB Maker to make the flashdrive

[Moderator Brian Masinick]

Helpful

Up

0

::

I would amend the statement above slightly. Both the Full-featured mode – writable Live USB and the Image mode – read-only Live USB (dd) write usable Live USBs.

As clearly stated in the description, the key difference is that the Full-featured mode is writable. If you want writable persistence to the Live USB, then you definitely want Full-featured mode. If you do not intend to use persistence, then either mode works fine, and image (dd) mode might be slightly faster to write. In any case, the dd command has a rich history that predates the Live USB Maker tool by well over a decade.

--
Brian Masinick

[Moderator BobC]

Helpful

Up

0

::

Something I have been forced to learn many times is that problems should be analyzed and solved one at a time with no additional permutations added between.

PS: What I mean by that is that you should just find a solution for your video without touching anything else not required. Once your video works reliably, then you can go on to tackling another issue.

• This reply was modified 4 months, 4 weeks ago by BobC.

[Moderator Brian Masinick]

Helpful

Up

1

::

Along that line, what happens if you take all of the default selections – ONLY deviating from the default choices if you have to select a different device, otherwise stick to the defaults.

--
Brian Masinick

[Member ant_222]

Helpful

Up

0

::

Now that I have purged Windows, I no longer can use Rufus to produce bootable USB sticks, so I used antiX Live USB maker in dd mode. No, I do not need USB persistence at all. You are absolutely right, BobC, in that troubles ought to be shot one a at a time (and preferably in the head rather than in the foot), but I did not intend to change my installation procedure and was surprised that the list of available services in the installer suddenly became empty: no cron, no dbus, no connman. All right, Brian—I will install tonight whatever the defaults are except selecting the desired partitions, and then try again to install the Liquorix kernel.

As to your trick of specifying the driver in GRUB, DaveW, it looks but a crutchy, temporary solution to me. randr still identifies your display as default, which means it fails properly to register it. Since Debian Dog Sid with kernel 6.0.0-2-amd64 works on my PC well, with your help we should be able to track down the exact component that needs to be upgraded, migrated, or reconfigured. If it helps, you can improve your own setup, too.

• This reply was modified 4 months, 4 weeks ago by ant_222.
• This reply was modified 4 months, 4 weeks ago by ant_222.

[Author]

Posts