LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-04-2018, 01:24 AM   #1
narke
Member
 
Registered: Apr 2010
Posts: 197

Rep: Reputation: 4
-current Kernel: have to use modeset=0 to make X work


When running the new -current kernel (4.14.47) on my laptop, my console automatically switched to high resolution mode (very small fonts) during boot. This is understandable because I think the KMS was taking effect, which was introduced after 2.6.xx. But I found I cannot start X by default. The startx command just halt forever. Then I tried to pass modeset=0 to my kernel as a parameter: nouveau.modeset=0, and, after that, startx began to work.

Could anyone know a reason for this? If the reason is that my display card does not support mode-setting, why, after passed modeset=0 to it, the console (before the startx) still switches to high resolution anyway? If the modeset=0 not taking effect, why startx begins to work after I set it? Head spins ...

Thanks in advance.
-woody
 
Old 06-04-2018, 02:45 AM   #2
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235
You should use either
Code:
nomodeset
OR
Code:
nouveau.modeset=0
 
Old 06-04-2018, 06:02 AM   #3
narke
Member
 
Registered: Apr 2010
Posts: 197

Original Poster
Rep: Reputation: 4
Quote:
Originally Posted by Darth Vader View Post
You should use either
Code:
nomodeset
OR
Code:
nouveau.modeset=0
I know this, but I am curious to know why it is needed in this new kernel but not in an old one like 4.4.x. And, I also donít understand while modeset disabled by this parameter, why the linux console still can switch to high resolution mode (1920x1024).
 
Old 06-04-2018, 08:38 AM   #4
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,498

Rep: Reputation: Disabled
Does this command work from any empty tty?

Code:
xinit /usr/bin/xterm -- :1
If it does you can check if GL works from the opened xterm.

Code:
glxgears
 
Old 06-05-2018, 01:38 AM   #5
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 573

Rep: Reputation: 63
Is this the same problem that I've seen at

https://www.linuxquestions.org/quest...en-4175631078/
 
Old 06-05-2018, 09:52 AM   #6
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,498

Rep: Reputation: Disabled
I think there might be a few similar issues. I personally have issues with the modesetting ddx (Part of xorg-server) and DRI3. The default xf86-video-nouveau and DRI2 work fine though even if they feel a bit sluggish after have been using modestting and DRI3 for a while...
 
Old 06-06-2018, 12:08 AM   #7
narke
Member
 
Registered: Apr 2010
Posts: 197

Original Poster
Rep: Reputation: 4
Quote:
Originally Posted by aikempshall View Post
Is this the same problem that I've seen at

https://www.linuxquestions.org/quest...en-4175631078/
Seems the thread was talking virtualbox? Dont understand what's the relevant ...
 
Old 06-06-2018, 04:04 AM   #8
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 573

Rep: Reputation: 63
Quote:
Originally Posted by narke View Post
Seems the thread was talking virtualbox? Dont understand what's the relevant ...
It seemed to me that the problem -
  1. was described similarly
  2. raised after on or after June 3rd
  3. work around was the same i.e. applying nomodeset

In my case I have bisected the Mesa Code and found an update to their code base which caused the problem I'm seeing on my system.

My system, running in VirtualBox, was perfectly happy until I applied the update mesa-18.1.1-x86_64-1
 
Old 06-06-2018, 08:26 AM   #9
narke
Member
 
Registered: Apr 2010
Posts: 197

Original Poster
Rep: Reputation: 4
Quote:
Originally Posted by aikempshall View Post
It seemed to me that the problem -
  1. was described similarly
  2. raised after on or after June 3rd
  3. work around was the same i.e. applying nomodeset

In my case I have bisected the Mesa Code and found an update to their code base which caused the problem I'm seeing on my system.

My system, running in VirtualBox, was perfectly happy until I applied the update mesa-18.1.1-x86_64-1
I understand, thanks!
 
  


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 Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Updated -current, cannot install NVidia driver (nvidia-modeset.ko) dugan Slackware 4 01-07-2018 05:17 PM
Debugging kernel issue (Kernel modeset to be particular) yuchankit Linux - Kernel 3 02-05-2015 07:30 AM
[SOLVED] Cannot make kernel 3.2.x work on my old laptop, stuck at 2.6.38.7 -current dc_eros Slackware 11 08-07-2012 07:21 AM
--current, radeon r300 segfault glxgears, glxinfo with radeon.modeset=0 on dual head Old_Fogie Slackware 1 11-29-2010 02:20 PM
How do I make a change to a current kernel? Would 'make oldconfig' work... jtp51 Slackware 11 11-01-2004 11:02 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:17 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