LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > antiX / MX Linux
User Name
Password
antiX / MX Linux This forum is for the discussion of antiX and MX Linux.

Notices


Reply
  Search this Thread
Old 08-17-2019, 04:03 PM   #1
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 3,378
Blog Entries: 9

Rep: Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884
Installed kernel 4.9.189 in AntiX-17 as advised. Now I have two problems!


The first one is trivial. This kernel is not the default boot kernel, probably because it has a lower version number than the old one (4.18.7). I can only boot it by going into GRUB's advanced options sub-menu. A fix for this would be nice.

The second problem is more serious. I cannot run Xorg. I checked the Xorg log and the problem seems to be here:
Code:
[    33.414] (--) CHROME(0): Mapping the frame buffer at address 0xF0000000 with size 131072 KB.
[    33.415] (EE) CHROME(0): Unable to map the frame buffer.
Error: Invalid argument (22)
[    33.415] (II) CHROME(0): Exiting viaMapMMIO.
[    33.415] (II) CHROME(0): VIAFreeRec
[    33.415] (II) CHROME(0): VIAFreeScreen
[    33.415] (II) CHROME(0): VIAFreeRec
[    33.415] (II) UnloadModule: "openchrome"
[    33.415] (II) UnloadSubModule: "vgahw"
[    33.415] (II) Unloading vgahw
[    33.415] (EE) Screen(s) found, but none have a usable configuration.
[    33.415] (EE) 
Fatal server error:
Under the old kernel, the frame buffer mapping is successful, CHROME continues to initialise and X comes up normally. Openchrome is an unusual driver (they don't make these Via Chrome chips any more) but it would be a pity if it really won't work with this more secure kernel.
 
Old 08-17-2019, 08:18 PM   #2
mrmazda
Senior Member
 
Registered: Aug 2016
Location: USA
Distribution: openSUSE, Debian, Knoppix, Mageia, Fedora, others
Posts: 1,757

Rep: Reputation: 541Reputation: 541Reputation: 541Reputation: 541Reputation: 541Reputation: 541
modprobe.blacklist=viafb might be something to try.

You may need an iomem or iommu option. I have yet to find any discussion or doc about how to determine which if any may or may not be indicated, but they seem to be indicated for older hardware and/or drivers to be able to cope with tighter restrictions on memory access while running newer kernels.
 
1 members found this post helpful.
Old 08-18-2019, 09:58 AM   #3
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 3,378

Original Poster
Blog Entries: 9

Rep: Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884
viafb doesn't seem to exist any more, though I remember it causing problems with older kernels. These kernels have a (presumably equivalent) module set with the flag FB_VIA. I don't know its precise name because it hasn't been set in either the working kernel or the bad one. So this is unlikely to be the source of the problem.

I'll try out the memory mapping options later.
 
1 members found this post helpful.
Old 08-18-2019, 11:34 AM   #4
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 3,378

Original Poster
Blog Entries: 9

Rep: Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884
"iomem=relaxed" does it. I shall need to find a way of putting this permanently into GRUB. I'm not very knowledgeable about GRUB because I hate it and have always used LILO.

Thank you Mr Mazda. You are indeed very illuminating!

Now how do I get my new kernel to be the first one on the list? Do I have to uninstall the older (but higher numbered) kernel or is there a simpler way? And while we're at it, why doesn't the kernel installation script understand about LTS kernels?

PS: Looks like all I have to do for relaxed iomem is to put it into the GRUB_CMDLINE_LINUX_DEFAULT string, then update GRUB.

Last edited by hazel; 08-18-2019 at 11:58 AM. Reason: Added postscript
 
1 members found this post helpful.
Old 08-18-2019, 12:52 PM   #5
fatmac
Senior Member
 
Registered: Sep 2011
Location: Upper Hale, Surrey/Hants Border, UK
Posts: 3,119

Rep: Reputation: Disabled
Probably easiest to apt-get remove the unwanted kernel, grub should automatically use the 'new' one the next time you boot, if I remember right, (I normally only upgrade to later kernels).
 
Old 08-18-2019, 12:56 PM   #6
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 3,378

Original Poster
Blog Entries: 9

Rep: Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884
Quote:
Originally Posted by fatmac View Post
Probably easiest to apt-get remove the unwanted kernel, grub should automatically use the 'new' one the next time you boot, if I remember right, (I normally only upgrade to later kernels).
Well, so do I. So does everyone. But because of the kernel's LTS system, a later kernel in an LTS series can have a lower version number than an earlier non-LTS kernel. So an upgrade (for meltdown mitigation in this case) can look like a downgrade. Apparently GRUB is too stupid to understand this.

Obviously I couldn't remove the old kernel until I got the new one to boot properly all the way to the X display manager. But now that I know the correct command line parameters to use, it should be safe to get rid of it.

Last edited by hazel; 08-18-2019 at 12:59 PM.
 
1 members found this post helpful.
Old 08-18-2019, 01:18 PM   #7
mrmazda
Senior Member
 
Registered: Aug 2016
Location: USA
Distribution: openSUSE, Debian, Knoppix, Mageia, Fedora, others
Posts: 1,757

Rep: Reputation: 541Reputation: 541Reputation: 541Reputation: 541Reputation: 541Reputation: 541
Quote:
Originally Posted by hazel View Post
"iomem=relaxed" does it.

Quote:
I shall need to find a way of putting this permanently into GRUB.
Add it to one of GRUB_CMDLINE_LINUX_DEFAULT= and/or GRUB_CMDLINE_LINUX= in /etc/default/grub and the next update of grub.cfg should include it.
 
Old 08-19-2019, 08:26 AM   #8
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 3,378

Original Poster
Blog Entries: 9

Rep: Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884Reputation: 1884
All done now. I updated GRUB and the new kernel boots successfully. Then I got rid of the old ones and now the new kernel is my default. Thanks, guys!
 
Old 08-19-2019, 08:47 AM   #9
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: AntiX 17
Posts: 5,840
Blog Entries: 21

Rep: Reputation: 2921Reputation: 2921Reputation: 2921Reputation: 2921Reputation: 2921Reputation: 2921Reputation: 2921Reputation: 2921Reputation: 2921Reputation: 2921Reputation: 2921
Quote:
Originally Posted by hazel View Post
All done now. I updated GRUB and the new kernel boots successfully. Then I got rid of the old ones and now the new kernel is my default. Thanks, guys!
Yeah. Was procrastinating on my chromebook.

Code:
$ uname -a
Linux biker 5.2.3-antix.1-amd64-smp #1 SMP PREEMPT Fri Jul 26 19:41:50 BST 2019 x86_64 GNU/Linux
For me, If the sd card slot works. I keep it.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Error (md5sum) while slackpkg was running kernel update to 4.4.189 on Slackware64 14.2 TheTKS Slackware 3 08-21-2019 08:25 PM
Need help troubleshooting boot fail of new 4.4.189 kernel ljb643 Slackware 20 08-19-2019 08:43 PM
[SOLVED] Removal of the hplip package causes system crash when using kde? (huge kernel 4.4.189) sxy Slackware 3 08-18-2019 04:34 AM
[SOLVED] Conky display gets corrupted since updating Antix-16 to Antix-17 hazel Linux - Distributions 3 12-18-2017 08:55 AM
is high mem support in a 2.6 kernel advised against for 1GB of memory? hedpe Linux - General 2 09-06-2005 09:35 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > antiX / MX Linux

All times are GMT -5. The time now is 11:40 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration