- This topic has 81 replies, 7 voices, and was last updated Dec 31-3:11 pm by ant_222.
-
AuthorPosts
-
December 11, 2022 at 11:40 am #95383Member
ant_222
::I did not find that message in dmesg or dmesg logs, but here what grep -i kernel returned for the last dmesg log (the forum did not let me post it). There is a crash at 0.000000 and unknown kernel commandline parameters at 0.021001.
V6 kernels available: I enable xanmod1 and liquorix from repos I found in a Linux V6 search:
Did you configure some other repositories in apt in addtition to those for antiX? Do you recommend that I do the same in order to install a V6 kernel? apt already shows me
linux-image-6.0.0-0.deb11.2-amd64/bullseye-backports 6.0.3-1~pbo11+1 Linux 6.0 for 64-bit PCs (signed)- This reply was modified 4 months, 4 weeks ago by ant_222.
December 11, 2022 at 2:12 pm #95387Memberant_222
::My /boot/ directory now contains the following vmlinuz files:
vmlinuz-4.9.0-326-antix.1-amd64-smp vmlinuz-5.10.142-antix.1-amd64-smp vmlinuz-5.18.0-0.deb11.4-amd64The last file is deb11 rather than antix.
Can it explain the dmesg errors for 5.18?The same errors are present in dmesg with linux-image-6.0.0-0.deb11.2-amd64, installed from the antiX repository via apt.
- This reply was modified 4 months, 4 weeks ago by ant_222.
December 11, 2022 at 4:22 pm #95397Moderator
Brian Masinick
::I did not find that message in dmesg or dmesg logs, but here what grep -i kernel returned for the last dmesg log (the forum did not let me post it). There is a crash at 0.000000 and unknown kernel commandline parameters at 0.021001.
V6 kernels available: I enable xanmod1 and liquorix from repos I found in a Linux V6 search:
Did you configure some other repositories in apt in addtition to those for antiX? Do you recommend that I do the same in order to install a V6 kernel? apt already shows me
linux-image-6.0.0-0.deb11.2-amd64/bullseye-backports 6.0.3-1~pbo11+1 Linux 6.0 for 64-bit PCs (signed)Yes, I recommend both xanmod1 and Liquorix kernels; I did a few quick checks on the modules and priorities they emphasize, and both of these kernels favor interactive workloads, so they are very good for routine use, and in fact, I’ve had very good experience with both of them. I am not certain that these kernels are certain to resolve the video issue; I hoped they would, but if the Debian 5.18 kernel doesn’t help, I’m not sure. Perhaps at this stage a better place to devote research is into determining which distributions (if any) support this graphics card. If we can find some systems that DO support the card, it is then possible to snag files from those systems to include them in the libraries so that the X server properly detects and displays as expected. At that point, the newer kernels will provide appropriate support for your system; I suppose you can do BOTH.
Also, yes, I add the xanmod1 and Liquorix repos in the /etc/apt/sources.list.d directory.
--
Brian MasinickDecember 11, 2022 at 5:23 pm #95398Memberant_222
::Thank you for the clarification, Brian. I am not sure we can say 5.18 did not help because, although I installed and booted it, it showed two errors in dmesg. I will quote them from above in case you missed it:
x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.18.0-0.deb11.4-amd64 root=UUID=f84c3aca-a563-421c-b016-525793ef87f1 ro quiet Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-5.18.0-0.deb11.4-amd64", will be passed to user space.The same happens with kernel 6.0.
You ask if another distribution could set the correct resoluion. My very first post in this thread answers your question. I repeat that Debain Dog Sid fails to autodetect the correct resolution, but lets me set it manually, so we can say we have a working configuration there. If you will help me extract the relevant files from that and install them into antiX, I will prepare a bootable USB stick with that distribution.
The antiX FAQ says: “A further feature of antiX is that you can install kernels from a variety of sources including Debian, siduction, aptosid and liquorix,” yet in my tests only the kernels listed in the Package Manager boot without those dmesg errors. Perhaps those errors should be invesigated as well?
My /etc/apt/sources.list.d/antix.list lists the Bullseye repository and two commented ones: Testing and Sid. I have found the liquorix repo in various.list and enabled it. apt udpate complained:
E: The repository 'http://liquorix.net/debian sid InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) for repository creation and user configuration detail.Shall I override this check by marking the repository as trusted?
Update:
uname -r on Debian Dog reports: 6.0.0-2-amd64.
xrandr lists about twenty resoltuions, including those below (720×400) and above (1920×1080) the native resolution of my display (1280×1024).December 11, 2022 at 6:43 pm #95400Moderator
Brian Masinick
::I’d be happy to help. It may be a day or two if you are able to wait…
--
Brian MasinickDecember 11, 2022 at 6:51 pm #95401ModeratorBobC
::I don’t understand why the last post you are trying to load a Liquorix Sid kernel, but above trying to use a Bullseye kernel.
Also, if possible its better to compare with Debian itself rather than distro that uses things from Debian. Ie: Can you get it to work with Debian stable?
Did the Liquorix Bullseye 6 kernel not work? Here are the settings I’m using…
Kernel: 6.0.0-9.1-liquorix-amd64 arch: x86_64 bits: 64 compiler: gcc v: 10.2.1 parameters: audit=0 intel_pstate=disable hpet=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/boot/vmlinuz-6.0.0-9.1-liquorix-amd64 Active apt repos in: /etc/apt/sources.list.d/liquorix.list 1: deb [arch=amd64] https: //liquorix.net/debian bullseye main 2: deb-src [arch=amd64] https: //liquorix.net/debian bullseye main- This reply was modified 4 months, 4 weeks ago by BobC.
December 11, 2022 at 6:51 pm #95402Memberant_222
::Thank you very much, Brian
I certainly can wait. In the mean time, and in addition to fixing my specific problem, shall I report the dmesg errors with 5.18 and 6.0 Debian kernels, and the error of the liquorix repo being unsigned, as formal issues somewhere?December 11, 2022 at 7:30 pm #95404ModeratorBobC
::So the answer to get what I have above installed was to go to the Liquorix.net site and follow their instructions to download and install their kernel.
December 11, 2022 at 8:56 pm #95407Moderator
Brian Masinick
::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
--
Brian MasinickDecember 11, 2022 at 9:17 pm #95409Memberant_222
::Brian,
Installation of prerequisites fails:Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-headers-6.0.0-12.1-liquorix-amd64 : Depends: libc6 (>= 2.34) but 2.31-13+deb11u5 is to be installed Depends: libpci3 (>= 1:3.8.0) but 1:3.7.0-5 is to be installed Depends: libperl5.36 (>= 5.36.0) but it is not installable Depends: libpython3.10 (>= 3.10.0) but it is not installable Depends: libssl3 (>= 3.0.0) but it is not installable E: Unable to correct problems, you have held broken packages.Perhaps instead of installing liquorix, some can help me install the 5.18 or 6.0 kernel from on of the official antiX repositories?
December 11, 2022 at 9:23 pm #95410Moderator
Brian Masinick
::OK, based on what your error messages report, some package or package group has installed other packages or package groups that interfere with Liquorix dependencies.
Not sure what those are, but if I even have the liquorix headers installed, I have NOT encountered these dependency issues on any of my distributions including antiX, so it does represent an issue. Figuring out exactly WHERE that problem started is not an easy one to start without a close look; however, if anyone has seen or encountered this one and knows an obvious solution, I defer to that expert help!
--
Brian MasinickDecember 11, 2022 at 9:25 pm #95411Memberant_222
December 11, 2022 at 9:30 pm #95412Moderator
Brian Masinick
::— Steven Barrett
is the person who maintains the Liquorix kernel. I don’t know if he would know why you have that unresolved dependency, but sure, if you start over with a fresh installation, you can add the Liquorix repo right away and install the latest Liquorix kernel and hopefully that will solve your problem; if you are willing, it’s worth a try! --
Brian MasinickDecember 11, 2022 at 9:34 pm #95413Memberant_222
::BobC,
in message #95401 you specify liquorix repo, as if you installed you kernel from there, but in message
#95404 you write that you followed the instruction from their site, which do not seem to access the repo. Anyway, I added the repo you quoted:
deb [arch=amd64] https: //liquorix.net/debian bullseye main
and tried:
sudo apt install linux-image-5.18.0-17.1-liquorix-amd64
It installed the kernel, but then wrote:
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
Update: That was a USB stick inserted. Strage that it should break kernel installation…December 11, 2022 at 9:53 pm #95414Moderator
Brian Masinick
::Mine looks different; try this instead:
more /etc/apt/sources.list.d/liquorix.list
deb https://liquorix.net/debian bullseye main
deb-src https://liquorix.net/debian bullseye mainThen, as I suggested above, run this command and it ought to work:
sudo apt-get install linux-image-liquorix-amd64 linux-headers-liquorix-amd64
I suspect it’ll install the V6 Liquorix kernel as long as it’s a clean system.
--
Brian Masinick -
AuthorPosts
- You must be logged in to reply to this topic.