LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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 07-08-2017, 05:42 AM   #31
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 37

Original Poster
Rep: Reputation: Disabled

Quote:
Originally Posted by business_kid View Post
You have the Intel card singing; the Nvidia card comes once the module is loaded, or when you start X?

Either way, it seems you're down to boot options. You have a couple of ways to go
1. Fix your Nvidia boot arrangement. Those lilo or grub video parameters may matter to you.
2. Boot on the Intel card and switch over to nvidia later.
3. Load the Nvidia module in an initrd and see if that improves things.
The notebook display only comes on-line when X is started. There is nothing visible before that, only the messages about loading the kernel image and the initrd.
When I switch back from graphics mode to the console, there is still nothing visible.

1. Okay, I may try checking out the documentation for module parameters for nvidia.ko, or dropping vga=normal, or anything
2. Unfortunately it's either this or that. I can choose only Intel or NVidia in the UEFI setup. I can also enable Optimus, which would kind of be like a hybrid mode.
3. The nvidia.ko is already in the initrd image. I would assume that it gets loaded when the initrd is loaded.

Thank you for your help!
 
Old 07-09-2017, 04:03 AM   #32
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 8,035

Rep: Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802
If you're booting the intel card, you hardly want nvidia.ko in the initrd but the intel one. I personally don't use an initrd, as if you have the hard disk & motherboard chipset drivers compiled in, the thing boots and loads what it needs.

Look at your video options in grub/lilo. Lilo has the option of specifying
vga=<some_mode>
e.g. vga=791. You could also compile the intel module into the kernel if it's in the source. But every video card has 16 basic modes that should work on any machine, and you should be able to raise those. Every nvidia & intel card has them AFAIK. The only one I know of that didn't was the SiS 6326 back in the 1990s - a POS if ever there was one.
I managed to land myself a 'great bargain' of a motherboard back then sporting the famous Via MPV3 hardware fault (a disk copying thing), a lesser known usb fault on the same chipset (they disabled 2 usb ports on later models), and the SiS 6326 graphics:-//. If I was looking for worse, I couldn't have bought it. I still managed to run linux on it.
 
Old 07-09-2017, 10:44 AM   #33
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 37

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by business_kid View Post
If you're booting the intel card, you hardly want nvidia.ko in the initrd but the intel one. I personally don't use an initrd, as if you have the hard disk & motherboard chipset drivers compiled in, the thing boots and loads what it needs.

Look at your video options in grub/lilo. Lilo has the option of specifying
vga=<some_mode>
e.g. vga=791. You could also compile the intel module into the kernel if it's in the source. But every video card has 16 basic modes that should work on any machine, and you should be able to raise those. Every nvidia & intel card has them AFAIK.
ATM I intend to create an environment which supports both the both the Intel and the NVidia cards, so that it does not matter whick one is selected in the UEFI setup, either one will work.

Currently the Intel driver is built into the kernel image, the nvidia.ko is present in the initrd image.
The UEFI firmware works in a way, that the disabled GPU is not even listen in lspci, so if the NVidia card is disabled, the nvidia driver won't even load, because the module refuses to load, if there is not a compatible card present.
Therefore, the bootup console works just fine if the Intel card is selected.
(If the NVidia card is left enabled, the built-in Intel driver does not matter either, as the code is not initialized if there is no matching hardware. Just like in the case of the huge kernel.)

I will try this vga=something setting with the NVidia card.

Quote:
Originally Posted by business_kid View Post
The only one I know of that didn't was the SiS 6326 back in the 1990s - a POS if ever there was one.
I managed to land myself a 'great bargain' of a motherboard back then sporting the famous Via MPV3 hardware fault (a disk copying thing), a lesser known usb fault on the same chipset (they disabled 2 usb ports on later models), and the SiS 6326 graphics:-//. If I was looking for worse, I couldn't have bought it. I still managed to run linux on it.
Fortunately I managed to avoid that era, as I only started to work with Linux at the beginning of the 2000s.
Those must have been tougher times for Linux users, but as it seems there are still some leftovers for us to chew at even these days.
 
Old 07-09-2017, 11:12 AM   #34
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 8,035

Rep: Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802
Quote:
Those must have been tougher times for Linux users, but as it seems there are still some leftovers for us to chew at even these days.
It was actually getting easier. The 2.2 kernel started finding your interrupts for you (Think ISA bus, where no modern ideas worked) but you still needed /etc/interrupts. The 2.0 & previous kernels needed you to know what interrupt your device used. PCMCIA is still a royal PITA last time I looked.
Plug and play hardware standards took a lot of work out of it. Installs take an hour, not days.
 
Old 07-09-2017, 02:10 PM   #35
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 37

Original Poster
Rep: Reputation: Disabled
Kernel parameters, line vga=791 did not help at all. The screen is still blank util X starts up.
I'm attaching a dmesg output. Perhaps that may provide some hints.
Attached Files
File Type: txt dmesg.txt (58.1 KB, 5 views)
 
Old 07-10-2017, 03:34 AM   #36
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 8,035

Rep: Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802
Code:
  0.359843] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
That looks funny from your dmesg, so I'd try an understand what it's telling you. You have a thinkpad; there's plenty of them out there, and they're a bit weird in places. So a search like
"linux thinkpad video options nvidia" throws up loads of thinkpad related video issues with nvidia. I'd go for that as a quick option. Refine the search a bit more - perhaps add the word 'boot' and even your model number and see what you get.
 
Old 07-11-2017, 03:38 PM   #37
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware has beern Main OpSys for decades while testing others to keep up
Posts: 1,375

Rep: Reputation: 1259Reputation: 1259Reputation: 1259Reputation: 1259Reputation: 1259Reputation: 1259Reputation: 1259Reputation: 1259Reputation: 1259
I'm not certain I understand exactly what you're shooting for but if it is just text output of boot messages, that seems easiest with "vga = normal" in /etc/lilo.conf". My Thinkpad is much older than yours ( a T60) but does have a decent nVidia graphics system and I could see immediately if it was working properly right after install as I had "prompt" enabled and also the "slack.bmp" lines so my system paused at the boot options page with a nice Slackware logo. Have you tried that?

Here's my lilo.conf from 14.2

Code:
# LILO configuration file
# Start LILO global section
boot = /dev/sda
lba32
bitmap = /boot/slack.bmp
bmp-colors = 255,0,255,0,255,0
bmp-table = 60,6,1,16
bmp-timer = 65,27,0,255
# Append any additional kernel parameters:
append = "video=640x480"
#append="vt.default_utf8=0"
prompt
###
timeout = 60
# Normal VGA console
vga = normal
#####
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz-4.7.5
  root = /dev/sda8
  label = Slack64-14.2
  read-only  # Partitions should be mounted read-only for checking
###
image = /boot/vmlinuz-custom-3.12
  root = /dev/sda7
  label = Slack1432
  read-only
###
other = /dev/sda6
label = Porteus
###
other = /dev/sda11
label = Stububtu-16
# Linux bootable partition config ends

Last edited by enorbet; 07-12-2017 at 01:09 AM.
 
Old 07-12-2017, 02:02 AM   #38
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 37

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by enorbet View Post
I'm not certain I understand exactly what you're shooting for but if it is just text output of boot messages, that seems easiest with "vga = normal" in /etc/lilo.conf". My Thinkpad is much older than yours ( a T60) but does have a decent nVidia graphics system and I could see immediately if it was working properly right after install as I had "prompt" enabled and also the "slack.bmp" lines so my system paused at the boot options page with a nice Slackware logo. Have you tried that?
Thank you. My goal is being able to see the boot-up console messages, because there is nothing displayed currently.
I tried
Code:
vga=normal
but unfortunately it did not work for me.

Unfortunately elilo does not offer all the features lilo does, and having a more sophisticated chooser UI requires more extensive configuring, so I currently only have a text propmt configured.

Tonight I will try something different though. Until now, I only put nvidia.ko into the initrd image, but for some reason nvidia-modeset.ko and nvidia-drm.ko were not included automatically. So now I made sure that they are included as well, and will see whether that improves anything...
 
Old 07-12-2017, 01:41 PM   #39
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 37

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by wowbaggerHU View Post
Tonight I will try something different though. Until now, I only put nvidia.ko into the initrd image, but for some reason nvidia-modeset.ko and nvidia-drm.ko were not included automatically. So now I made sure that they are included as well, and will see whether that improves anything...
As mentioned, I've put the nvidia-modeset.ko and nvidia-drm.ko modules along the nvidia.ko module to the initrd image, but unfortunately that did not improve the situation either.
 
Old 07-13-2017, 03:38 AM   #40
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 8,035

Rep: Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802
Can you replace elilo? You've done just about everything else.
 
Old 07-13-2017, 03:48 AM   #41
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,527

Rep: Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480
Quote:
Originally Posted by business_kid View Post
Can you replace elilo? You've done just about everything else.
No, the OP didn't try to just install a kernel and associated modules from Slackware current (4.9.37 at time of writing). But that would not satisfy his curiosity.

However, making a diff between a config file provided in Slackware current and his custom one could give some clues.
 
Old 07-17-2017, 06:25 AM   #42
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 37

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Didier Spaier View Post
No, the OP didn't try to just install a kernel and associated modules from Slackware current (4.9.37 at time of writing). But that would not satisfy his curiosity.

However, making a diff between a config file provided in Slackware current and his custom one could give some clues.
During the weekend I had some time and have upgraded my 14.2 installation to -current.
Then I went on and recompiled my kernel config with the latest 4.9.38 version.
The next step was taking the version 4.9.37 kernel-generic kernel, disabling nouveau with modprobe.conf, and adding the NVidia kernel driver.
I have packaged it to initrd, and the result is the following:
At boot, efifb is activated, and stays active, until X starts. Then the NVidia driver seems to become active, and the text consoles become invisible. When hitting Ctrl+Alt+F1, I only see a blank black screen without anything on it.

So this behavior is not related to my config, as I haven't changed the config of the OS-shipped -generic kernel image.

Last edited by wowbaggerHU; 07-17-2017 at 06:27 AM.
 
Old 07-17-2017, 08:53 AM   #43
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 8,035

Rep: Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802
Code:
At boot, efifb is activated, and stays active, until X starts. Then the NVidia driver seems to become active, and the text consoles become invisible. When hitting Ctrl+Alt+F1, I only see a blank black screen without anything on it.
That would indicate issues with the nvidia kernel module. It's been a while, but that seemed to control the consoles while the driver under /usr/lib64/xorg/modules handles X. Maybe the handover goes poorly. Is there options/help to control that?
 
  


Reply

Tags
kernel compile, slackware 14.2, thinkpad


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
Make errors when building from kernel source 3.10.7 in seperate output directory duffman Slackware 12 10-14-2014 09:50 PM
Dual display on older LCD Projector and notebook screen surahyo Linux - Laptop and Netbook 2 08-24-2011 09:17 AM
Installing Linux into Notebook with Broken LCD pigsa Linux - Hardware 10 04-15-2011 02:41 AM
VAIO notebook: no HDD light, no LCD display gentoojedi Linux - Laptop and Netbook 2 12-20-2005 11:41 PM
Debian VideoCard/LCD drivers Sony Notebook cwainright Linux - Newbie 1 10-06-2005 09:30 AM


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