Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I attempted to post the xorg log here however it did not post probably due to size.
Large files should not be pasted into any web forum message. They should either be attached to a forum post, or uploaded to a pastebin site where they can either be opened as plain text without necessity to login or have JS enabled, or be downloaded as-is without embellishment, editing or markup. Pastebinning is facilitated in Debian via the command pastebinit.
Quote:
The verbage I'm referring to is,"Note the kernel cmdline parameters I have in Grub, which I have bolded". I thought GRUB is where it came from because it was mentioned.
The bolded "parameters" in comment #7 were brought into inxi output via the content of file /proc/cmdline. They appear in /proc/cmdline because when the selected Grub boot stanza was executed they were included on the linu line as may have been modified in real time. Parameter presence happens either because they were part /etc/default/grub when /boot/grub/grub.cfg was last generated, or, because they were added at boot time in the Grub selection menu via striking the "E" key and adding them to or editing the selected linu line, which applies such change only on the imminent boot.
The output from the integrated graphics via the VGA port is 1440 x 900.
The output from the card is limited to 1024 x 768.
In desktop systems with both integrated and discrete graphics installed, behavior is influenced by BIOS settings. BIOS come in too many flavors to make any specific suggestions what to enable or disable or how these settings are there described. Making appropriate selection of settings depends on the particular BIOS and hardware capabilities, and on your desire. The simplest way forward in most cases is to not attempt to use onboard graphics output(s) when a discrete GPU is installed, as discrete GPU preferred is the default setup with most BIOS. With some BIOS, mostly older ones, installation of a discrete GPU makes impossible use of the integrated GPU or onboard output(s). Until the BIOS can be set to support your desired use of available graphics ports, or your desire can be conformed to whatever the hardware and firmware can support, it won't make much difference what you do with Debian configuration or packaging.
I suggest utilizing only the Oland card's outputs, configuring the BIOS to prefer the discrete GPU, and if necessary, blocking loading of the i915 kernel driver. Switching to using only radeon or amdgpu kernel modules from i915 may require regenerating your initrd. With both displays connected to the Oland, radeon or amdgpu kernel module loaded, and i915 kernel module unloaded, 1024x768 should no longer be a limitation on either display.
What does the following report when booted using the Oland GPU?
I set it to use the discrete gpu. How can I disable the i915 driver?
Including i915.modeset=0 on Grub's linu line ought to work well enough for testing. Once you know for sure it's really necessary, blacklisting and excluding from initrds may be preferred. With the BIOS set to prefer discrete, it shouldn't be necessary.
You really don't want both radeon and amdgpu loaded. That's why I referred to the bolded options in comment #7. It's the method of selecting one to the exclusion of the other with any GCN #1 generation of Radeon GPU.
I suppose your root problem could be the presence of amdgpu and i915 and radeon all loaded at once. For your intended use, one of the three exclusively should be perfect. My GCN #1 is using only amdgpu, as comment #7 shows.
I used Synaptic to remove xserver-xorg-video-intel and xserver-xorg-video-amdgpu since xserver-xorg-video-radeon is the one that runs the card.
How do I block the i915 driver from loading? Detailed instructions please.
I used Synaptic to remove xserver-xorg-video-intel and xserver-xorg-video-amdgpu since xserver-xorg-video-radeon is the one that runs the card.
How do I block the i915 driver from loading? Detailed instructions please.
You don't. Your machine has an intel card and uses the i915 driver for that card.
The issue seems to be that you have both the amdgpu driver and the radeon driver loading and that will present a problem since both are trying to use the same hardware. The AMD card should work with one or the other but you should never use both drivers for the same card.
I used Synaptic to remove xserver-xorg-video-intel and xserver-xorg-video-amdgpu since xserver-xorg-video-radeon is the one that runs the card.
What else did you do?
Quote:
How do I block the i915 driver from loading?
How do you know it's necessary? Was the simpler i915.modeset=0 process not helpful? It's intended to disable the functions that the i915 module provides, primarily KMS. Without KMS available, X will prefer any alternative that provides it, such as the discrete GPU and radeon module. If i915.modeset=0 wasn't helpful, blacklisting i915 isn't likely to help either.
You don't. Your machine has an intel card and uses the i915 driver for that card.
It has two GPUs, an Intel HD 530, and a possibly more capable yet 2 year older Radeon HD Oland. The kernel will only load the i915 for use with an Intel GPU, just like it will only load the amdgpu and/or radeon module for use with an AMD/ATI GPU it supports, such as OP's Oland. Blacklisting is a valid method of prohibiting use of one GPU in favor of using an alternate that depends on a different module.
Quote:
The issue seems to be that you have both the amdgpu driver and the radeon driver loading and that will present a problem since both are trying to use the same hardware. The AMD card should work with one or the other but you should never use both drivers for the same card.
This is the reason for the instructions previously given to OP here about using the bolded command line parameters in comment #7 or their converse, to limit loading to only one or the other, because the GCN #1 series of Radeons is supported by either/both kernel module(s).
The only other thing I can think is the DVI-1 24+5 to VGA adapter is somehow limiting the screen resolution.
Today, my DVI-24+5 cable arrived. That fixed the resolution problem.
In the meantime, I want to thank all who have responded to my question. MRMAZDA in particular (have you considered being an instructor?, your knowledge is really up there!) and I learned a lot from your post!
My reasonable new to me Lenovo Think Pad X1 Carbon 8th generation laptop came from the factory with an Intel UHD graphics adapter, I also have an Hp Chrome Book which is a custom order with a similar UHD Intel graphics adapter. My main HP Z420 work Station has a ATI?AMD Redeon 7500 or similar GPU.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.