11:09 a.m.
I've replaced my ageing Nvidia card with a more recent and much faster
AMD GPU. However when I boot the system, the default display still
shows as the built-in Intel chip, even though AMD modules are loaded:
$ sudo lsmod|grep -i amd
amdgpu 10153984 1
iommu_v2 24576 1 amdgpu
gpu_sched 49152 1 amdgpu
drm_ttm_helper 16384 1 amdgpu
drm_buddy 20480 2 amdgpu,i915
drm_display_helper 180224 2 amdgpu,i915
ttm 94208 3 amdgpu,drm_ttm_helper,i915
(Nvidia modules are not loaded).
Inxi shows:
$ inxi -G
Graphics:
Device-1: Intel IvyBridge GT2 [HD Graphics 4000] driver: i915 v: kernel
Device-2: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
driver: amdgpu v: kernel
Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.3 driver: X:
loaded: amdgpu,modesetting unloaded: fbdev,vesa dri: crocus gpu: i915
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa
22.1.7
Switcherooctl shows both GPUs:
$ switcherooctl list
Device: 0
Name: Intel® HD Graphics 4000
Default: yes
Environment: DRI_PRIME=pci-0000_00_02_0
Device: 1
Name: Advanced Micro Devices, Inc. [AMD®/ATI] Ellesmere
[Radeon RX 470/480/570/570X/580/580X/590] (Radeon RX 580)
Default: no
Environment: DRI_PRIME=pci-0000_01_00_0
I should mention that both GPUs are connected through an HDMI switch to
a single monitor. I've used this successfully in the past to get PCI
passthrough on Windows VMs for gaming.
I haven't touched anything else. I tried unplugging the i915 and
rebooting (after removing the HDMI switch and connecting the monitor
directly), but simply got a blank screen (in fact three dots at the top
left).
Is there some grub magic I need to do? I assumed this would be
automatic but it seems not.
poc
11:27 a.m.
Patrick O'Callaghan composed on 2022-11-09 17:09 (UTC):
$ inxi -G
That's not enough info. Show -GSaz please.
Proprietary NVidia driver removal is not a simple matter of uninstalling rpms.
Typically blacklisting and/or /etc/X11/xorg.con* files and/or kernel cmdline
options get left behind, and sometimes even a replacement library, or an initrd
rebuild is needed.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
1:25 p.m.
On Wed, 2022-11-09 at 12:27 -0500, Felix Miata wrote:
Patrick O'Callaghan composed on 2022-11-09 17:09 (UTC):
> $ inxi -G
That's not enough info. Show -GSaz please.
$ inxi -Gsaz
Graphics:
Device-1: Intel IvyBridge GT2 [HD Graphics 4000] vendor: Micro-Star MSI
driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13
ports: active: HDMI-A-1 empty: DP-1,VGA-1 bus-ID: 00:02.0
chip-ID: 8086:0162 class-ID: 0300
Device-2: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: Tul / PowerColor driver: amdgpu v: kernel arch: GCN-4
code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 1
speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
active: none empty: DP-2, DP-3, DP-4, DVI-D-1, HDMI-A-2 bus-ID: 01:00.0
chip-ID: 1002:67df class-ID: 0300 temp: 29.0 C
Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.3
compositor: kwin_x11 driver: X: loaded: amdgpu,modesetting
unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: HP 24f serial: <filter>
built: 2020 res: 1920x1080 hz: 60 dpi: 93 gamma: 1.2
size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
OpenGL: renderer: Mesa Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa
22.1.7 direct render: Yes
Sensors:
System Temperatures: cpu: 29.0 C mobo: N/A gpu: amdgpu temp: 28.0 C
Fan Speeds (RPM): N/A
Proprietary NVidia driver removal is not a simple matter of
uninstalling rpms.
Typically blacklisting and/or /etc/X11/xorg.con* files and/or kernel
cmdline
options get left behind, and sometimes even a replacement library, or
an initrd
rebuild is needed.
I thought as much but wasn't sure. The current boot line is:
$ cat /proc/cmdline
BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.0.5-200.fc36.x86_64
root=UUID=8e1f7af4-c0bf-434e-b1c4-a9af2c810d56 ro rootflags=subvol=root
modprobe.blacklist=nouveau rd.blacklist=nouveau vconsole.font=latarcyrheb-sun16 rhgb quiet
audit=0
It's blacklisting nouveau because I used to use the proprietary Nvidia
driver.
poc
2:07 p.m.
On Wed, 2022-11-09 at 19:25 +0000, Patrick O'Callaghan wrote:
On Wed, 2022-11-09 at 12:27 -0500, Felix Miata wrote:
> Patrick O'Callaghan composed on 2022-11-09 17:09 (UTC):
>
> > $ inxi -G
>
> That's not enough info. Show -GSaz please.
>
$ inxi -Gsaz
Graphics:
Device-1: Intel IvyBridge GT2 [HD Graphics 4000] vendor: Micro-Star
MSI
driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built:
2012-13
ports: active: HDMI-A-1 empty: DP-1,VGA-1 bus-ID: 00:02.0
chip-ID: 8086:0162 class-ID: 0300
Device-2: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: Tul / PowerColor driver: amdgpu v: kernel arch: GCN-4
code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 1
speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
active: none empty: DP-2, DP-3, DP-4, DVI-D-1, HDMI-A-2 bus-ID:
01:00.0
chip-ID: 1002:67df class-ID: 0300 temp: 29.0 C
Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.3
compositor: kwin_x11 driver: X: loaded: amdgpu,modesetting
unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm
(20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: HP 24f serial: <filter>
built: 2020 res: 1920x1080 hz: 60 dpi: 93 gamma: 1.2
size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9
modes:
max: 1920x1080 min: 720x400
OpenGL: renderer: Mesa Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa
22.1.7 direct render: Yes
Sensors:
System Temperatures: cpu: 29.0 C mobo: N/A gpu: amdgpu temp: 28.0 C
Fan Speeds (RPM): N/A
> Proprietary NVidia driver removal is not a simple matter of
> uninstalling rpms.
> Typically blacklisting and/or /etc/X11/xorg.con* files and/or
> kernel
> cmdline
> options get left behind, and sometimes even a replacement library,
> or
> an initrd
> rebuild is needed.
Sorry, wrong options. Once again:
$ inxi -GSaz
System:
Kernel: 6.0.5-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.37-36.fc36
parameters: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.0.5-200.fc36.x86_64
root=UUID=8e1f7af4-c0bf-434e-b1c4-a9af2c810d56 ro rootflags=subvol=root
modprobe.blacklist=nouveau rd.blacklist=nouveau
vconsole.font=latarcyrheb-sun16 rhgb quiet audit=0
Desktop: KDE Plasma v: 5.25.5 tk: Qt v: 5.15.6 wm: kwin_x11 vt: 2
dm: SDDM Distro: Fedora release 36 (Thirty Six)
Graphics:
Device-1: Intel IvyBridge GT2 [HD Graphics 4000] vendor: Micro-Star MSI
driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13
ports: active: HDMI-A-1 empty: DP-1,VGA-1 bus-ID: 00:02.0
chip-ID: 8086:0162 class-ID: 0300
Device-2: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: Tul / PowerColor driver: amdgpu v: kernel arch: GCN-4
code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 1
speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
active: none empty: DP-2, DP-3, DP-4, DVI-D-1, HDMI-A-2 bus-ID: 01:00.0
chip-ID: 1002:67df class-ID: 0300 temp: 29.0 C
Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.3
compositor: kwin_x11 driver: X: loaded: amdgpu,modesetting
unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: HP 24f serial: <filter>
built: 2020 res: 1920x1080 hz: 60 dpi: 93 gamma: 1.2
size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
OpenGL: renderer: Mesa Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa
22.1.7 direct render: Yes
There's nothing relevant in /etc/X11/xorg.conf.d
poc
2:36 p.m.
Patrick O'Callaghan composed on 2022-11-09 20:07 (UTC):
$ inxi -GSaz
System:
Kernel: 6.0.5-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.37-36.fc36
parameters: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.0.5-200.fc36.x86_64
root=UUID=8e1f7af4-c0bf-434e-b1c4-a9af2c810d56 ro rootflags=subvol=root
modprobe.blacklist=nouveau rd.blacklist=nouveau
Competent FOSS display drivers for NVidia GPUs require the KMS that those two
=nouveau parameters disable. Purging those two from /etc/default/grub & grub.cfg
followed by reboot should be all you need, but you can test by editing them away
via the E key at the Grub menu.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
3:38 p.m.
On 11/9/22 12:36, Felix Miata wrote:
Patrick O'Callaghan composed on 2022-11-09 20:07 (UTC):
> $ inxi -GSaz
> System:
> Kernel: 6.0.5-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
> v: 2.37-36.fc36
> parameters: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.0.5-200.fc36.x86_64
> root=UUID=8e1f7af4-c0bf-434e-b1c4-a9af2c810d56 ro rootflags=subvol=root
> modprobe.blacklist=nouveau rd.blacklist=nouveau
Competent FOSS display drivers for NVidia GPUs require the KMS that those two
=nouveau parameters disable. Purging those two from /etc/default/grub & grub.cfg
followed by reboot should be all you need, but you can test by editing them away
via the E key at the Grub menu.
How are those parameters relevant to the current situation? I agree
that they should be removed because they are no longer relevant, but
they shouldn't be affecting anything. The new graphics is AMD.
3:46 p.m.
Samuel Sieb composed on 2022-11-09 16:38 (UTC-0500):
Felix Miata wrote:
> Patrick O'Callaghan composed on 2022-11-09 20:07 (UTC):
>> $ inxi -GSaz
>> System:
>> Kernel: 6.0.5-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
>> v: 2.37-36.fc36
>> parameters: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.0.5-200.fc36.x86_64
>> root=UUID=8e1f7af4-c0bf-434e-b1c4-a9af2c810d56 ro rootflags=subvol=root
>> modprobe.blacklist=nouveau rd.blacklist=nouveau
> Competent FOSS display drivers for NVidia GPUs require the KMS
that those two
> =nouveau parameters disable. Purging those two from /etc/default/grub & grub.cfg
> followed by reboot should be all you need, but you can test by editing them away
> via the E key at the Grub menu.
How are those parameters relevant to the current situation? I agree
that they should be removed because they are no longer relevant, but
they shouldn't be affecting anything. The new graphics is AMD.
They aren't relevant, but I got sidetracked and when I came back I thought I was
done. Obviously I hadn't finished thinking through this before clicking send. :(
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
4:28 p.m.
On Wed, 2022-11-09 at 13:38 -0800, Samuel Sieb wrote:
On 11/9/22 12:36, Felix Miata wrote:
> Patrick O'Callaghan composed on 2022-11-09 20:07 (UTC):
>
> > $ inxi -GSaz
> > System:
> > Kernel: 6.0.5-200.fc36.x86_64 arch: x86_64 bits: 64 compiler:
> > gcc
> > v: 2.37-36.fc36
> > parameters: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.0.5-
> > 200.fc36.x86_64
> > root=UUID=8e1f7af4-c0bf-434e-b1c4-a9af2c810d56 ro
> > rootflags=subvol=root
> > modprobe.blacklist=nouveau rd.blacklist=nouveau
>
> Competent FOSS display drivers for NVidia GPUs require the KMS that
> those two
> =nouveau parameters disable. Purging those two from
> /etc/default/grub & grub.cfg
> followed by reboot should be all you need, but you can test by
> editing them away
> via the E key at the Grub menu.
How are those parameters relevant to the current situation? I agree
that they should be removed because they are no longer relevant, but
they shouldn't be affecting anything. The new graphics is AMD.
They may be relevant if they remove KMS, which apparently AMD requires.
I've removed them in any case and rebooted, but it doesn't seem to make
a lot of difference.
I'll read through the material Greg referenced, which suggests I need
to install some extra packages.
poc
12:16 a.m.
On 11/9/22 14:28, Patrick O'Callaghan wrote:
On Wed, 2022-11-09 at 13:38 -0800, Samuel Sieb wrote:
> On 11/9/22 12:36, Felix Miata wrote:
>> Patrick O'Callaghan composed on 2022-11-09 20:07 (UTC):
>>
>>> $ inxi -GSaz
>>> System:
>>> Kernel: 6.0.5-200.fc36.x86_64 arch: x86_64 bits: 64 compiler:
>>> gcc
>>> v: 2.37-36.fc36
>>> parameters: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.0.5-
>>> 200.fc36.x86_64
>>> root=UUID=8e1f7af4-c0bf-434e-b1c4-a9af2c810d56 ro
>>> rootflags=subvol=root
>>> modprobe.blacklist=nouveau rd.blacklist=nouveau
>>
>> Competent FOSS display drivers for NVidia GPUs require the KMS that
>> those two
>> =nouveau parameters disable. Purging those two from
>> /etc/default/grub & grub.cfg
>> followed by reboot should be all you need, but you can test by
>> editing them away
>> via the E key at the Grub menu.
>
> How are those parameters relevant to the current situation? I agree
> that they should be removed because they are no longer relevant, but
> they shouldn't be affecting anything. The new graphics is AMD.
They may be relevant if they remove KMS, which apparently AMD requires.
I've removed them in any case and rebooted, but it doesn't seem to make
a lot of difference.
KMS isn't really something you can remove, except maybe by recompiling
the kernel. It's an interface that the various graphics drivers use.
5:27 a.m.
On Wed, 2022-11-09 at 12:27 -0500, Felix Miata wrote:
Patrick O'Callaghan composed on 2022-11-09 17:09 (UTC):
> $ inxi -G
That's not enough info. Show -GSaz please.
Proprietary NVidia driver removal is not a simple matter of
uninstalling rpms.
Typically blacklisting and/or /etc/X11/xorg.con* files and/or kernel
cmdline
options get left behind, and sometimes even a replacement library, or
an initrd
rebuild is needed.
I did an initrd rebuild and rebooted. Still no change in behaviour.
$ inxi -GSaz
System:
Kernel: 6.0.5-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.37-36.fc36
parameters: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.0.5-200.fc36.x86_64
root=UUID=8e1f7af4-c0bf-434e-b1c4-a9af2c810d56 ro rootflags=subvol=root
vconsole.font=latarcyrheb-sun16 rhgb quiet audit=0
Desktop: KDE Plasma v: 5.25.5 tk: Qt v: 5.15.6 wm: kwin_x11 vt: 2
dm: SDDM Distro: Fedora release 36 (Thirty Six)
Graphics:
Device-1: Intel IvyBridge GT2 [HD Graphics 4000] vendor: Micro-Star MSI
driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13
ports: active: HDMI-A-1 empty: DP-1,VGA-1 bus-ID: 00:02.0
chip-ID: 8086:0162 class-ID: 0300
Device-2: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: Tul / PowerColor driver: amdgpu v: kernel arch: GCN-4
code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 1
speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
active: none empty: DP-2, DP-3, DP-4, DVI-D-1, HDMI-A-2 bus-ID: 01:00.0
chip-ID: 1002:67df class-ID: 0300 temp: 38.0 C
Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.5
compositor: kwin_x11 driver: X: loaded: amdgpu,modesetting
unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: HP 24f serial: <filter>
built: 2020 res: 1920x1080 hz: 60 dpi: 93 gamma: 1.2
size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
OpenGL: renderer: Mesa Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa
22.1.7 direct render: Yes
poc
3:55 p.m.
On Wed, Nov 9, 2022 at 6:09 PM Patrick O'Callaghan
<pocallaghan(a)gmail.com> wrote:
I've replaced my ageing Nvidia card with a more recent and much faster
AMD GPU. However when I boot the system, the default display still
shows as the built-in Intel chip, even though AMD modules are loaded:
$ sudo lsmod|grep -i amd
amdgpu 10153984 1
iommu_v2 24576 1 amdgpu
gpu_sched 49152 1 amdgpu
drm_ttm_helper 16384 1 amdgpu
drm_buddy 20480 2 amdgpu,i915
drm_display_helper 180224 2 amdgpu,i915
ttm 94208 3 amdgpu,drm_ttm_helper,i915
(Nvidia modules are not loaded).
Inxi shows:
$ inxi -G
Graphics:
Device-1: Intel IvyBridge GT2 [HD Graphics 4000] driver: i915 v: kernel
Device-2: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
driver: amdgpu v: kernel
Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.3 driver: X:
loaded: amdgpu,modesetting unloaded: fbdev,vesa dri: crocus gpu: i915
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa
22.1.7
Switcherooctl shows both GPUs:
$ switcherooctl list
Device: 0
Name: Intel® HD Graphics 4000
Default: yes
Environment: DRI_PRIME=pci-0000_00_02_0
Device: 1
Name: Advanced Micro Devices, Inc. [AMD®/ATI] Ellesmere
[Radeon RX 470/480/570/570X/580/580X/590] (Radeon RX 580)
Default: no
Environment: DRI_PRIME=pci-0000_01_00_0
I should mention that both GPUs are connected through an HDMI switch to
a single monitor. I've used this successfully in the past to get PCI
passthrough on Windows VMs for gaming.
I haven't touched anything else. I tried unplugging the i915 and
rebooting (after removing the HDMI switch and connecting the monitor
directly), but simply got a blank screen (in fact three dots at the top
left).
In order to disable i915 altogether, I used an option in bios/efi firmware.
(I have an NVIDIA card and want to use it always/for any application.)
Is there some grub magic I need to do? I assumed this would be
automatic but it seems not.
If the intention is to use either i915 or the AMD card depending on
the application
that is AMD Dynamic Switchable Graphics,
I would suggest looking at
https://wiki.archlinux.org/title/PRIME#Gnome_integration
https://wiki.archlinux.org/title/PRIME
https://wiki.archlinux.org/title/ATI
https://wiki.archlinux.org/title/AMDGPU
greg
4:17 p.m.
On Wed, 2022-11-09 at 22:55 +0100, greg wrote:
In order to disable i915 altogether, I used an option in bios/efi
firmware.
(I have an NVIDIA card and want to use it always/for any
application.)
That would certainly be an option, though I'd prefer to avoid BIOS
settings id possible.
> Is there some grub magic I need to do? I assumed this would be
> automatic but it seems not.
If the intention is to use either i915 or the AMD card depending on
the application
that is AMD Dynamic Switchable Graphics,
I would suggest looking at
https://wiki.archlinux.org/title/PRIME#Gnome_integration
https://wiki.archlinux.org/title/PRIME
https://wiki.archlinux.org/title/ATI
https://wiki.archlinux.org/title/AMDGPU
A lot of very detailed info there, thanks.
poc
7:20 a.m.
On Wed, 2022-11-09 at 22:17 +0000, Patrick O'Callaghan wrote:
On Wed, 2022-11-09 at 22:55 +0100, greg wrote:
> In order to disable i915 altogether, I used an option in bios/efi
> firmware.
> (I have an NVIDIA card and want to use it always/for any
> application.)
>
That would certainly be an option, though I'd prefer to avoid BIOS
settings id possible.
> > Is there some grub magic I need to do? I assumed this would be
> > automatic but it seems not.
>
> If the intention is to use either i915 or the AMD card depending on
> the application
> that is AMD Dynamic Switchable Graphics,
> I would suggest looking at
>
> https://wiki.archlinux.org/title/PRIME#Gnome_integration
> https://wiki.archlinux.org/title/PRIME
> https://wiki.archlinux.org/title/ATI
> https://wiki.archlinux.org/title/AMDGPU
Still poring over that material, but in the meantime I did at least
manage to get screen output by using "Run on discrete graphics card"
from Gnome.
However a) I want to use KDE, and b) I still haven't managed to get
anything graphically interesting to work, i.e. Windows games via Steam,
which I have been able to run before now on the IGP.
Rebooting with only the AMD card connected to the monitor doesn't work
either. I may have to disable the IGP from the BIOS, but I can't
believe this is the only solution.
poc
7:30 a.m.
On Thu, Nov 10, 2022 at 9:21 AM Patrick O'Callaghan <pocallaghan(a)gmail.com>
wrote:
[...]
I did at least
manage to get screen output by using "Run on discrete graphics
card"
from Gnome.
However a) I want to use KDE, and b) I still haven't managed to get
anything graphically interesting to work, i.e. Windows games via Steam,
which I have been able to run before now on the IGP.
Rebooting with only the AMD card connected to the monitor doesn't work
either. I may have to disable the IGP from the BIOS, but I can't
believe this is the only solution.
It may not be the only solution, but it is probably the least likely to give
problems in the long run across OS versions and driver updates.
Never trust cables and connectors -- you could try swapping HDMI cables.
My experience with switches has been that they work well if you find a
stable
configuration (order in which systems are powered on), but screw up if
something changes (new GPU, OS update, etc.)
--
George N. White III
7:37 a.m.
On Thu, 2022-11-10 at 09:30 -0400, George N. White III wrote:
On Thu, Nov 10, 2022 at 9:21 AM Patrick O'Callaghan
<pocallaghan(a)gmail.com>
wrote:
> [...]
>
I did at least
> manage to get screen output by using "Run on discrete graphics
> card"
> from Gnome.
>
> However a) I want to use KDE, and b) I still haven't managed to get
> anything graphically interesting to work, i.e. Windows games via
> Steam,
> which I have been able to run before now on the IGP.
>
> Rebooting with only the AMD card connected to the monitor doesn't
> work
> either. I may have to disable the IGP from the BIOS, but I can't
> believe this is the only solution.
>
It may not be the only solution, but it is probably the least likely
to give
problems in the long run across OS versions and driver updates.
Never trust cables and connectors -- you could try swapping HDMI
cables.
My experience with switches has been that they work well if you find
a
stable
configuration (order in which systems are powered on), but screw up
if
something changes (new GPU, OS update, etc.)
Thanks. I was hoping to be able to use both GPUs, which I've been doing
for years with a Windows VM and my old Nvidia card. I'd much prefer
this to dual booting. I haven't yet managed to set up the VM correctly
for the new card, but that's a separate issue.
poc
7:30 a.m.
On Thu, Nov 10, 2022 at 09:30:36AM -0400, George N. White III wrote:
On Thu, Nov 10, 2022 at 9:21 AM Patrick O'Callaghan
<pocallaghan(a)gmail.com>
wrote:
> [...]
> Rebooting with only the AMD card connected to the monitor doesn't work
> either. I may have to disable the IGP from the BIOS, but I can't
> believe this is the only solution.
>
It may not be the only solution, but it is probably the least likely to give
problems in the long run across OS versions and driver updates.
Never trust cables and connectors -- you could try swapping HDMI cables.
My experience with switches has been that they work well if you find a
stable
configuration (order in which systems are powered on), but screw up if
something changes (new GPU, OS update, etc.)
In such cases I'd certainly try to boot the computer with some Live
system (Fedora, Debian, whatever) - to come closer to know whether
it's actually a hardware problem or a problem with the installed
system ...
7:55 a.m.
On Sat, 2022-11-12 at 14:30 +0100, Wolfgang Pfeiffer wrote:
On Thu, Nov 10, 2022 at 09:30:36AM -0400, George N. White III wrote:
> On Thu, Nov 10, 2022 at 9:21 AM Patrick O'Callaghan
> <pocallaghan(a)gmail.com>
> wrote:
>
> > [...]
> > Rebooting with only the AMD card connected to the monitor doesn't
> > work
> > either. I may have to disable the IGP from the BIOS, but I can't
> > believe this is the only solution.
> >
>
> It may not be the only solution, but it is probably the least
> likely to give
> problems in the long run across OS versions and driver updates.
>
> Never trust cables and connectors -- you could try swapping HDMI
> cables.
> My experience with switches has been that they work well if you
> find a
> stable
> configuration (order in which systems are powered on), but screw up
> if
> something changes (new GPU, OS update, etc.)
In such cases I'd certainly try to boot the computer with some Live
system (Fedora, Debian, whatever) - to come closer to know whether
it's actually a hardware problem or a problem with the installed
system ...
As mentioned in another sub-thread, I got it working by disabling the
IGP via the BIOS. I'd still like to make this more dynamic by
blacklisting the IGP at boot, but haven't managed this yet. It doesn't
seem to be enough just to put i915 among the blacklisted modules.
poc
1:27 p.m.
Patrick O'Callaghan composed on 2022-11-12 13:55 (UTC):
As mentioned in another sub-thread, I got it working by disabling
the
IGP via the BIOS. I'd still like to make this more dynamic by
blacklisting the IGP at boot, but haven't managed this yet. It doesn't
seem to be enough just to put i915 among the blacklisted modules.
Is i915.modeset=0 one of the boot parameters you tried that didn't help?
Were you always able to use both NVidia and Intel at the same time, or only
offload from NVidia to Intel, thus only connecting physically to Intel outputs?
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
4:33 p.m.
On Sat, 2022-11-12 at 14:27 -0500, Felix Miata wrote:
Patrick O'Callaghan composed on 2022-11-12 13:55 (UTC):
> As mentioned in another sub-thread, I got it working by disabling
> the
> IGP via the BIOS. I'd still like to make this more dynamic by
> blacklisting the IGP at boot, but haven't managed this yet. It
> doesn't
> seem to be enough just to put i915 among the blacklisted modules.
Is i915.modeset=0 one of the boot parameters you tried that didn't
help?
No, I used i915 as the module name. Maybe that's the problem.
Were you always able to use both NVidia and Intel at the same time,
or only
offload from NVidia to Intel, thus only connecting physically to
Intel outputs?
I could reboot and mask the Nvidia card so Linux would leave it alone,
meaning my Windows VM could access it directly via PCI passthrough,
leaving the i915 for normal Linux operations. In operation, this
involved manually switching the monitor input back and forth (and the
kb and mouse, but I'm used to that).
I've so far not been able to reproduce this with the AMD card. I'm
pretty sure it's possible as it's a common configuration (though my CPU
is Intel and not AMD.)
If I can get this to work, I would then like to not to have to tweak
the BIOS settings to turn the i915 on or off again according to when I
wanted it. I would still need to flip the boot settings and reboot, but
I can live with that.
poc
5:07 p.m.
On Wed, 2022-11-09 at 22:55 +0100, greg wrote:
In order to disable i915 altogether, I used an option in bios/efi
firmware.
(I have an NVIDIA card and want to use it always/for any
application.)
That's what I ended up doing. I tried blacklisting the i915 but it was
still be there on booting. Turning it off in the BIOS is what got the
result.
I'd still like to enable both GPUs for VM PC passthrough, but haven't
got that working yet.
Thanks to everyone who replied.
poc
9:02 a.m.
On Wed, 09 Nov 2022 17:09:02 +0000
Patrick O'Callaghan <pocallaghan(a)gmail.com> wrote:
Is there some grub magic I need to do? I assumed this would be
automatic but it seems not.
When I switched from nvidia to amd, many years ago, it was seamless.
But that was older hardware, I didn't have two graphics cards (a builtin
and a discrete), and I am using the radeon driver with an amd cpu, not
an amd card with an intel cpu. Anyway I did a quick search and found
this link that mentions something called prime that seems to do
something like what you want.
https://www.unixmen.com/using-hybrid-graphic-card-intel-amd-arch-linux/
5:09 p.m.
On Thu, 2022-11-10 at 08:02 -0700, stan via users wrote:
On Wed, 09 Nov 2022 17:09:02 +0000
Patrick O'Callaghan <pocallaghan(a)gmail.com> wrote:
> Is there some grub magic I need to do? I assumed this would be
> automatic but it seems not.
When I switched from nvidia to amd, many years ago, it was seamless.
But that was older hardware, I didn't have two graphics cards (a
builtin
and a discrete), and I am using the radeon driver with an amd cpu,
not
an amd card with an intel cpu. Anyway I did a quick search and found
this link that mentions something called prime that seems to do
something like what you want.
https://www.unixmen.com/using-hybrid-graphic-card-intel-amd-arch-linux/
Thanks. I may get round to that later, though often the Arch package
structure is different enough from Fedora to make some decoding
necessary. For now I disabled the IGP in the BIOS, which gets me part
of the way.
poc
532
days inactive
535
days old
21 comments
7 participants
participants (7)
-
Felix Miata -
George N. White III -
greg -
Patrick O'Callaghan -
Samuel Sieb -
stan -
Wolfgang Pfeiffer