antiX will not set the native monitor resolution

[Moderator BobC]

Helpful

Up

0

::

1. Use Live-USB-Maker from the antiX you have and take all default settings to burn the iso to the USB. Reboot from that with the settings I gave for the kernel you will be booting with and try it to see if it fixes the video resolution.

2. If video is fixed, next get internet working. If problems, sudo dmesg and use grep to search for firmware. Maybe something newer is needed.

3. If video not fixed get internet working and try updating the USB to boot with stable liquorix kernel and use my settings to boot from that.

[Moderator BobC]

Helpful

Up

0

::

Do you really need to use base and runit?

If you dont get this working immediately with the settings above you should consider running antiX 64 full sysvinit since it is the one most people run. Just my opinion but you have too many permutations that nobody else has, so you should minimize them until you know what settings will fix your problems.

[Moderator BobC]

Helpful

Up

0

::

Lastly, if you have problems burning the USB, use the advanced panel to turn off automount.

Tell us exactly what iso you are booting from and what kernel and what additional boot parameters you give it.

[Moderator Brian Masinick]

Helpful

Up

0

::

Since Sid works, now the exercise is to determine where the necessary files reside, then copy them from Sid to the system you’re using.
I don’t know whether you have enough physical space to install BOTH of these systems on your equipment.

If your hard drive (or whatever you are using) is 40 GB, for instance, you COULD divide it into at least two or more partitions and then install each distro.
Once you do that, you can take as long as you need to locate the files that work on Sid and are either missing or incomplete on our setup.

I often don’t know exactly where things are when I start, so I begin by searching the most likely directories to find what I’m looking for.

For instance, I’ll run an information report to find out the names of the device or devices in question, then search for those strings. There may end up being multiple locations where things have to be copied, but at least that provides a start. I also use searches on the Internet to find out more about whatever devices or features I’m learning about. So you can see that I don’t necessarily know 100% percent how to solve an issue when I begin; I do, however, have a general idea what to do, a general idea about locations and directories; that gives me a head start. But like everyone else, I started from zero and learned; the more each person does their own version of this, the more satisfying it is, and the better we become at problem solving and resolution.

So to summarize, though it’s not the only way, I’d start by attempting to install both systems on the same hardware, then I’d start looking for the information that identifies each device, and proceed from there, using both the installed images and Internet searches to find as many clues as possible. If you provide some information, I might be able to help a little more.

--
Brian Masinick

[Member ant_222]

Helpful

Up

0

::

Brian,
I have already made special provisions for installing two OSes side-by-side. I have a separate ESP partition, two 48 Gb OS partitions, and a data partition to store whatever should should OS (re)intallations. If Debian Dog does not destroy my boot configuration but accurately adds itself to the GRUB menu, all should be well.

[Moderator Brian Masinick]

Helpful

Up

0

::

ant_222 wrote:

Brian,
I have already made special provisions for installing two OSes side-by-side. I have a separate ESP partition, two 48 Gb OS partitions, and a data partition to store whatever should should OS (re)intallations. If Debian Dog does not destroy my boot configuration but accurately adds itself to the GRUB menu, all should be well.

Excellent! Step one to “comparison” learning; this will eventually lead to being able to get ideas from other systems, and sometimes it will allow physically copying files, programs, and data – when they are compatible across the systems – they should be compatible in the antiX – Debian Sid scenario since we’re considering the definition and configuration of peripheral devices.

--
Brian Masinick

[Member ant_222]

Helpful

Up

0

::

So—I have installed antix-22-runit_x64-base.iso—the exact version I want, with defaluts. Immediagtely after the new system booted, and fired up the terminal and typed entered the command for the installation of prerequisites:
curl 'https://liquorix.net/add-liquorix-repo.sh' | sudo bash
which this time went without errors and printed:
[INFO ] Liquorix kernel intalled successfully
which surprised me as I was intalling only the prerequisites and not the kernel itself. On second thought, I suggested that the script above had indeed installed the entire kernel with Debian prerequisites, and rebooted. This proved correct, as the GRUB menu now showed an additional option for: 6.0.0-12.1-liquorix-amd64, and uname -r after boot confirmed this.

The new kernel, however, did not resolved my problem, and my display is still unrecognised by X and named default, with 1024×768 remaining the only available resolution. Yet the graphical driver seems loaded correctly:

$ inxi -G
Graphics:
  Device-1: Intel JasperLake [UHD Graphics] driver: i915 v: kernel
  Display: server: X.Org v: 1.20.11 driver: X: loaded: fbdev gpu: i915
    resolution: 1024x768
  OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.5

I then added the i915 driver to the GRUB config file as per DaveW:
GRUB_CMDLINE_LINUX_DEFAULT="quiet insmod i915 i915.modeset=1 selinux=0"
and, although Dave did not indicate it, ran
sudo update-grub.
After reboot, the resolution was the same. Here are my dmesg and Xort.0.log. Observe in the former the same errors as I had with other non-antiX kernels:

[    0.000000] x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
[    0.021360] Unknown kernel command line parameters "insmod i915 BOOT_IMAGE=/boot/vmlinuz-6.0.0-12.1-liquorix-amd64", will be passed to user space.

Observe in the latter lots of invalid argument errors and the following:

[     4.346] (==) Using config file: "/etc/X11/xorg.conf"
[     4.347] (==) Using config directory: "/etc/X11/xorg.conf.d"
[     4.347] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     4.348] (==) No Layout section.  Using the first Screen section.
[     4.348] (==) No screen section available. Using defaults.
[     4.348] (**) |-->Screen "Default Screen Section" (0)
[     4.348] (**) |   |-->Monitor "<default monitor>"
[     4.348] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[     4.348] (**) |   |-->Device "Device0"
[     4.348] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
.................
[     4.379] (II) FBDEV(0): hardware: i915drmfb (video memory: 9216kB)
[     4.379] (II) FBDEV(0): checking modes against framebuffer device...
[     4.379] (II) FBDEV(0): checking modes against monitor...
[     4.379] (II) FBDEV(0): Virtual size is 1024x768 (pitch 1024)

I have not installed Debian Dog yet, but will do so as time permits. Thanks again for your help.

[Moderator Brian Masinick]

Helpful

Up

0

::

I’m wondering if, in this case, it is necessary to construct a specific Xorg.conf file that contains the necessary parameters.

In the EARLY days of the X11 Window System project, it was always necessary to create a graphics configuration file; the early programs had no automatic detection.
In most cases today it is unnecessary; however, occasionally it still needs to be done; otherwise you encounter what you are seeing.

See

https://www.fedoraproject.org/wiki/How_to_create_xorg.conf
https://askubuntu.com/questions/217758/how-to-make-an-xorg-conf-file
https://www.cyberciti.biz/tips/create-a-xorgconf-file.html
https://www.x.org/releases/current/doc/man/man5/xorg.conf.5.xhtml

to learn more about it; some of these references are OLD and are not necessarily perfect or ideal, but they should help in understanding what this file is and what it does.
I hope these references are helpful; I’m afraid you may have to do some manual configuration unless you are successful in figuring out why the Debian Sid instance works and the antiX instance does not work; looking at both side by side may also provide clues.

--
Brian Masinick

[Member ant_222]

Helpful

Up

0

::

Must I not resolve the kernel errors first: #AC crash and unrecognised command-line parameters from GRUB—both quoted in my previous post? If the kernel cannot load correctly, are we really entitield to solve later problems, which may be caused by the earler kernel-level ones?

I have no idea how to install Debian Dog in normal mode as a second OS. Its graphical installer offers only frugal mode, and cannot seem to detect and use an existing ESP partition. Will you tell me to consult the Debian guys about it?

[Moderator Brian Masinick]

Helpful

Up

0

::

I can tell you why it’s not working properly: the graphical configuration is not set up properly (if at all).
Suggestion is to install the other system side se by side and compare them.

I believe you said that you have two separate 48 GB partitions; put antiX on one of them and Debian Sid on the other one. They both offer boot loaders so it makes little difference which one you use as long as you are able to boot into either system. So to me the next step is to get both systems installed; once that is done you can compare them and see, side by side the way each one is configured; the antiX one seems to be missing stuff that the Debian Sid one has. Find those differences and you’re one or two steps closer to a solution.

--
Brian Masinick

[Moderator BobC]

Helpful

Up

0

::

We have been trying to help, but you never even tried my solution. I went to the trouble of figuring it out for you, but you didn’t even try it. You only tried DaveW’s solution.

BTW, if anyone gives you parameters to add, add them at the end of the linux boot line, not beginning.

If you are going to install Debian Dog and know it works, install it first.

antiX will install itself nicely on the open partition you left for it and configure a dual boot for both. All you need to do is tell it which partition to make the antiX root. As to where to put grub, if its EFI, click ESP, if not, click MBR.

[Moderator BobC]

Helpful

Up

0

::

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

The last one is specifically configured for that device in your machine if you are running a kernel 5.18 or above.

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

[Moderator BobC]

Helpful

Up

0

::

Do it at boot. Type it in at the end of the line.

I added this to the end of my boot line. It complains a bit depending on which kernel is used on the i915.xxxxxxxx parameter but I’m sure it will find one of them:
acpi_osi=!Windows i915.preliminary_hw_support=1 i915.alpha_support=1 i915.force_probe=191b

You could add:
acpi_osi=!Windows i915.preliminary_hw_support=1 i915.alpha_support=1 i915.force_probe=4e61

Do not update grub with new settings until it they work when you boot it. Then you will know what actually works.

[Moderator BobC]

Helpful

Up

0

::

If you don’t know how to install debian dog, and can’t find instructions, I’m sorry, I don’t know offhand, and yes, people that wrote it and run it would be best to ask.

antiX will automatically add a boot entry to its grub setup for debian dog if it finds a partition with /boot and other things needed. If not, you can add it manually with a custom entry later.

[Moderator BobC]

Helpful

Up

0

::

Debian dog was not intuitive to install, but it can be done. I didn’t figure out how to do a frugal install, but was able to get the full install to work. I didn’t find any instructions to do that, and had trouble getting grub to boot it because I don’t think the built in grub was setup to handle EFI. I ended up creating a custom.cfg for it to make it work driven by antiX’s grub boot system. I also suspect some antiX packages might work with it if/where lucky.

PS: I didn’t install that on my main system… Test machine only…

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

[Author]

Posts