hbern
November 14, 2022, 9:04pm
#1
I am attempting to install openSUSE Tumbleweed on my computer. I have tried this on the 20221111 and 20221113 ISOs, as well as multiple boot makers, so I don’t believe either of those is the issue. I am using the offline install ISO. Each time it progresses smoothly down (excepting 2 times where it hung on network autosetup) until it reaches System Analysis > System Probing > Probe USB devices where it freezes on 0%. The most recent time I left it running for over 6 minutes without any sign of progress, during which time my laptop continued to heat up.
System Details:
Dell XPS 15 9520
One USB 3.2 Gen 2 (Type-C) port with DisplayPort
Two Thunderbolt 4 (USB4) Type-C ports with Power Delivery
Plugged in devices:
Power adapter from manufacturer (this also occurs with power adapter removed)
Samsung USB-C Flash Drive (boot media)
Any help is appreciated
mrmazda
November 14, 2022, 10:35pm
#2
XPS 15 9520 is a Dell series or class, not a specific model, so we can’t know what hardware you have. Please tell us at least which model(s) of GPU(s) and CPU it has, and whether it features Optane.
Did you try the failsafe menu selection, or to see more messages, try appending nomodeset to the end of the linu line or removing splash=silent and quiet, after striking the E key at the openSUSE boot menu?
hbern
November 14, 2022, 11:54pm
#3
mrmazda:
XPS 15 9520 is a Dell series or class, not a specific model, so we can’t know what hardware you have. Please tell us at least which model(s) of GPU(s) and CPU it has, and whether it features Optane.
Did you try the failsafe menu selection, or to see more messages, try appending nomodeset to the end of the linu line or removing splash=silent and quiet, after striking the E key at the openSUSE boot menu?
Adding nomodeset to the command made everything work perfectly, thanks!
mrmazda
November 15, 2022, 1:42am
#4
That’s impossible. Work, obviously, but not perfectly. Perfect graphics performance depends on kernel mode setting, which nomodeset disables, causing fallback to a crude and slow graphics driver. It is intended as a troubleshooting parameter and workaround, not for normal use. If the installer left it in place in Grub in the installed system, it needs to be removed - if and when it is determined to no longer be needed. It’s possible your hardware is too new to be properly supported, thus making it a necessary workaround until proper hardware support is available. To the end of so determining, please provide here, using code tags , output run from a terminal window such as Xterm or Konsole:
inxi -CGMSaz
You might need to install inxi and xdpyinfo first.
hbern
November 15, 2022, 11:24pm
#5
mrmazda:
That’s impossible. Work, obviously, but not perfectly. Perfect graphics performance depends on kernel mode setting, which nomodeset disables, causing fallback to a crude and slow graphics driver. It is intended as a troubleshooting parameter and workaround, not for normal use. If the installer left it in place in Grub in the installed system, it needs to be removed - if and when it is determined to no longer be needed. It’s possible your hardware is too new to be properly supported, thus making it a necessary workaround until proper hardware support is available. To the end of so determining, please provide here, using code tags , output run from a terminal window such as Xterm or Konsole:
inxi -CGMSaz
You might need to install inxi and xdpyinfo first.
Sorry for the delayed response. You are correct, when I said that it had worked “perfectly” I meant that the installation had worked perfectly. I had some graphical issues (cannot change screen brightness, locked to an aspect ratio different from my screen) but I did not connect the dots. Here is the information you requested:
System:
Kernel: 6.0.8-1-default arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-6.0.8-1-default
root=UUID=4768938c-c624-42b2-80e9-9e74308cf2a2 splash=silent nomodeset
mitigations=auto quiet security=apparmor
Desktop: KDE Plasma v: 5.26.3 tk: Qt v: 5.15.7 wm: kwin_x11 vt: 7
dm: SDDM Distro: openSUSE Tumbleweed 20221113
Machine:
Type: Laptop System: Dell product: XPS 15 9520 v: N/A
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: Dell model: 0MWGD4 v: A00 serial: <superuser required> UEFI: Dell
v: 1.8.1 date: 10/13/2022
CPU:
Info: model: 12th Gen Intel Core i7-12700H bits: 64 type: MST AMCP
arch: Alder Lake gen: core 12 level: v3 built: 2021+ process: Intel 7 (10nm
ESF) family: 6 model-id: 0x9A (154) stepping: 3 microcode: 0x423
Topology: cpus: 1x cores: 14 mt: 6 tpc: 2 st: 8 threads: 20 smt: enabled
cache: L1: 1.2 MiB desc: d-8x32 KiB, 6x48 KiB; i-6x32 KiB, 8x64 KiB
L2: 11.5 MiB desc: 6x1.2 MiB, 2x2 MiB L3: 24 MiB desc: 1x24 MiB
Speed (MHz): avg: 2700 min/max: 400/4600:4700:3500 scaling:
driver: intel_pstate governor: powersave cores: 1: 2700 2: 2700 3: 2700
4: 2700 5: 2700 6: 2700 7: 2700 8: 2700 9: 2700 10: 2700 11: 2700
12: 2700 13: 2700 14: 2700 15: 2700 16: 2700 17: 2700 18: 2700 19: 2700
20: 2700 bogomips: 107520
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB
filling, PBRSB-eIBRS: SW sequence
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel Alder Lake-P Integrated Graphics vendor: Dell driver: N/A
alternate: i915 arch: Gen-12.2 process: Intel 10nm built: 2021-22+
bus-ID: 0000:00:02.0 chip-ID: 8086:46a6 class-ID: 0300
Device-2: NVIDIA GA107M [GeForce RTX 3050 Mobile] vendor: Dell
driver: N/A alternate: nouveau non-free: 515.xx+ status: current (as of
2022-08) arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-22
bus-ID: 0000:01:00.0 chip-ID: 10de:25a2 class-ID: 0302
Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
bus-ID: 3-6:2 chip-ID: 0c45:6a15 class-ID: 0e02
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.5
compositor: kwin_x11 driver: X: loaded: modesetting,vesa unloaded: fbdev
alternate: intel gpu: N/A 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: Unknown-1 mapped: None-1 res: 1920x1080 hz: 60 size: N/A
modes: 1920x1080
OpenGL: renderer: llvmpipe (LLVM 15.0.3 256 bits) v: 4.5 Mesa 22.2.3
direct render: Yes
hbern
November 15, 2022, 11:33pm
#6
mrmazda:
That’s impossible. Work, obviously, but not perfectly. Perfect graphics performance depends on kernel mode setting, which nomodeset disables, causing fallback to a crude and slow graphics driver. It is intended as a troubleshooting parameter and workaround, not for normal use. If the installer left it in place in Grub in the installed system, it needs to be removed - if and when it is determined to no longer be needed. It’s possible your hardware is too new to be properly supported, thus making it a necessary workaround until proper hardware support is available. To the end of so determining, please provide here, using code tags , output run from a terminal window such as Xterm or Konsole:
inxi -CGMSaz
You might need to install inxi and xdpyinfo first.
Seems I managed to delete the post on accident so let’s try this again. You are correct, I posted that it was done “perfectly” when I completed installation. I have some graphics issues (cannot change brightness, locked to 1920x1080 when my screen is actually 1920x1200, etc), but did not connect the dots. Here is the information you requested:
System:
Kernel: 6.0.8-1-default arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-6.0.8-1-default
root=UUID=4768938c-c624-42b2-80e9-9e74308cf2a2 splash=silent nomodeset
mitigations=auto quiet security=apparmor
Desktop: KDE Plasma v: 5.26.3 tk: Qt v: 5.15.7 wm: kwin_x11 vt: 7
dm: SDDM Distro: openSUSE Tumbleweed 20221113
Machine:
Type: Laptop System: Dell product: XPS 15 9520 v: N/A
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: Dell model: 0MWGD4 v: A00 serial: <superuser required> UEFI: Dell
v: 1.8.1 date: 10/13/2022
CPU:
Info: model: 12th Gen Intel Core i7-12700H bits: 64 type: MST AMCP
arch: Alder Lake gen: core 12 level: v3 built: 2021+ process: Intel 7 (10nm
ESF) family: 6 model-id: 0x9A (154) stepping: 3 microcode: 0x423
Topology: cpus: 1x cores: 14 mt: 6 tpc: 2 st: 8 threads: 20 smt: enabled
cache: L1: 1.2 MiB desc: d-8x32 KiB, 6x48 KiB; i-6x32 KiB, 8x64 KiB
L2: 11.5 MiB desc: 6x1.2 MiB, 2x2 MiB L3: 24 MiB desc: 1x24 MiB
Speed (MHz): avg: 2590 high: 2700 min/max: 400/4600:4700:3500 scaling:
driver: intel_pstate governor: powersave cores: 1: 2700 2: 2700 3: 2700
4: 2700 5: 2700 6: 2700 7: 2700 8: 2700 9: 2700 10: 2700 11: 517 12: 2700
13: 2700 14: 2700 15: 2700 16: 2700 17: 2700 18: 2700 19: 2700 20: 2700
bogomips: 107520
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB
filling, PBRSB-eIBRS: SW sequence
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel Alder Lake-P Integrated Graphics vendor: Dell driver: N/A
alternate: i915 arch: Gen-12.2 process: Intel 10nm built: 2021-22+
bus-ID: 0000:00:02.0 chip-ID: 8086:46a6 class-ID: 0300
Device-2: NVIDIA GA107M [GeForce RTX 3050 Mobile] vendor: Dell
driver: N/A alternate: nouveau non-free: 515.xx+ status: current (as of
2022-08) arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-22
bus-ID: 0000:01:00.0 chip-ID: 10de:25a2 class-ID: 0302
Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
bus-ID: 3-6:2 chip-ID: 0c45:6a15 class-ID: 0e02
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.5
compositor: kwin_x11 driver: X: loaded: modesetting,vesa unloaded: fbdev
alternate: intel gpu: N/A 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: Unknown-1 mapped: None-1 res: 1920x1080 hz: 60 size: N/A
modes: 1920x1080
OpenGL: renderer: llvmpipe (LLVM 15.0.3 256 bits) v: 4.5 Mesa 22.2.3
direct render: Yes
(It marks my screen as 1920x1080 on this but it is in fact 1920x1200)
mrmazda
November 16, 2022, 7:57am
#7
As inxi was run while booted using nomodeset, its output is misleading in some respects, and in others incomplete, but to start with, you’re using a laptop categorically classified as having Optimus graphics, meaning both an Intel IGPU, and a discrete NVidia GPU. I can’t provide any detailed help with this configuration. It does look like your hardware should be old enough for full graphics support, your CPU/IGPU having been introduced in Q1’22, and thus should only need some special configuration due to the Optimus configuration. Next installation step, if you haven’t already, should be to follow the suse prime instructions here , then let us know how it goes.
The current use of 1920x1080 mode instead of 1920x1200 is because the crude fallback VESA display driver in use due to modeset on your kernel command line in Grub doesn’t support very many modes, and 1920x1200 is not one of those it does.
Before jumping into following the prime instructions I suggest as a diagnostic aid to try a boot into the installed system without using nomodeset. At some point it will be required, and knowing before disturbing anything else may save trouble later. To test, at the Grub menu, with the normal default selection highlighted, strike the E key, navigate to the end of the line that begins linu (which usually wraps onto at least one more line), delete or backspace away nomodeset, quiet & splash=silent (the latter two to cause verbose boot messages), then append a space and plymouth=0 , and finally proceed with boot. Are you able to complete a boot this way? Instead of a GUI login screen, do you get a shell prompt instead? If you get an all black screen, does Ctrl-Alt-F3 bring up a shell login prompt? Does the boot hang similar to what happened to cause you to start this thread?
hbern
November 17, 2022, 10:47pm
#8
mrmazda:
As inxi was run while booted using nomodeset, its output is misleading in some respects, and in others incomplete, but to start with, you’re using a laptop categorically classified as having Optimus graphics, meaning both an Intel IGPU, and a discrete NVidia GPU. I can’t provide any detailed help with this configuration. It does look like your hardware should be old enough for full graphics support, your CPU/IGPU having been introduced in Q1’22, and thus should only need some special configuration due to the Optimus configuration. Next installation step, if you haven’t already, should be to follow the suse prime instructions here , then let us know how it goes.
The current use of 1920x1080 mode instead of 1920x1200 is because the crude fallback VESA display driver in use due to modeset on your kernel command line in Grub doesn’t support very many modes, and 1920x1200 is not one of those it does.
Before jumping into following the prime instructions I suggest as a diagnostic aid to try a boot into the installed system without using nomodeset. At some point it will be required, and knowing before disturbing anything else may save trouble later. To test, at the Grub menu, with the normal default selection highlighted, strike the E key, navigate to the end of the line that begins linu (which usually wraps onto at least one more line), delete or backspace away nomodeset, quiet & splash=silent (the latter two to cause verbose boot messages), then append a space and plymouth=0 , and finally proceed with boot. Are you able to complete a boot this way? Instead of a GUI login screen, do you get a shell prompt instead? If you get an all black screen, does Ctrl-Alt-F3 bring up a shell login prompt? Does the boot hang similar to what happened to cause you to start this thread?
For unrelated reasons, I have decided that openSUSE is not for me. But thank you for offering your help!
Same issue here, OpenSuSE Tumbleweed 20221120 hangs at “Probe USB devices”. A brand new Dell XPS 15 9520, I am waiting on an additional harddisk, that should be here tomorrow, at that moment I will run the suggested steps and attach the output here.
From my system
**System:**
**Kernel:** 6.0.8-1-default **arch:** x86_64 **bits:** 64 **compiler:** gcc **v:** 12.2.1
**parameters:** BOOT_IMAGE=/boot/vmlinuz-6.0.8-1-default
root=UUID=7dd9193e-6062-4b8e-9e6a-5101f048ab74 nomodeset
resume=/dev/disk/by-uuid/f35ad53c-d442-4906-9827-2e4298a3fec4
mitigations=auto quiet security=apparmor
**Desktop:** KDE Plasma **v:** 5.26.3 **tk:** Qt **v:** 5.15.7 **wm:** kwin_x11 **vt:** 7
**dm:** SDDM **Distro:** openSUSE Tumbleweed 20221123
**Machine:**
**Type:** Laptop **System:** Dell **product:** XPS 15 9520 **v:** N/A
**serial:** <superuser required> **Chassis:****type:** 10 **serial:** <superuser required>
**Mobo:** Dell **model:** 0YD3W1 **v:** A00 **serial:** <superuser required> **UEFI:** Dell
**v:** 1.8.1 **date:** 10/13/2022
**CPU:**
**Info:****model:** 12th Gen Intel Core i7-12700H **bits:** 64 **type:** MST AMCP
**arch:** Alder Lake **gen:** core 12 **level:** v3 **built:** 2021+ **process:** Intel 7 (10nm
ESF) **family:** 6 **model-id:** 0x9A (154) **stepping:** 3 **microcode:** 0x424
**Topology:****cpus:** 1x **cores:** 14 **mt:** 6 **tpc:** 2 **st:** 8 **threads:** 20 **smt:** enabled
**cache:****L1:** 1.2 MiB **desc:** d-8x32 KiB, 6x48 KiB; i-6x32 KiB, 8x64 KiB
**L2:** 11.5 MiB **desc:** 6x1.2 MiB, 2x2 MiB **L3:** 24 MiB **desc:** 1x24 MiB
**Speed (MHz):****avg:** 2490 **high:** 2700 **min/max:** 400/4600:4700:3500 **scaling:**
**driver:** intel_pstate **governor:** powersave **cores:****1:** 2700 **2:** 2700 **3:** 2700
**4:** 2700 **5:** 565 **6:** 2700 **7:** 2700 **8:** 2700 **9:** 2700 **10:** 2700 **11:** 2700 **12:** 2700
**13:** 2700 **14:** 2700 **15:** 2700 **16:** 2700 **17:** 2700 **18:** 2700 **19:** 647 **20:** 2700
**bogomips:** 107520
**Flags:** avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
**Vulnerabilities:**
**Type:** itlb_multihit **status:** Not affected
**Type:** l1tf **status:** Not affected
**Type:** mds **status:** Not affected
**Type:** meltdown **status:** Not affected
**Type:** mmio_stale_data **status:** Not affected
**Type:** retbleed **status:** Not affected
**Type:** spec_store_bypass **mitigation:** Speculative Store Bypass disabled via
prctl
**Type:** spectre_v1 **mitigation:** usercopy/swapgs barriers and __user pointer
sanitization
**Type:** spectre_v2 **mitigation:** Enhanced IBRS, IBPB: conditional, RSB
filling, PBRSB-eIBRS: SW sequence
**Type:** srbds **status:** Not affected
**Type:** tsx_async_abort **status:** Not affected
**Graphics:**
**Device-1:** Intel Alder Lake-P Integrated Graphics **vendor:** Dell **driver:** N/A
**alternate:** i915 **arch:** Gen-12.2 **process:** Intel 10nm **built:** 2021-22+
**bus-ID:** 0000:00:02.0 **chip-ID:** 8086:46a6 **class-ID:** 0300
**Device-2:** NVIDIA GA107M [GeForce RTX 3050 Ti Mobile] **vendor:** Dell
**driver:** N/A **alternate:** nouveau **non-free:** 515.xx+ **status:** current (as of
2022-08) **arch:** Ampere **code:** GAxxx **process:** TSMC n7 (7nm) **built:** 2020-22
**bus-ID:** 0000:01:00.0 **chip-ID:** 10de:25a0 **class-ID:** 0302
**Device-3:** Microdia Integrated_Webcam_HD **type:** USB **driver:** uvcvideo
**bus-ID:** 3-6:3 **chip-ID:** 0c45:6d1f **class-ID:** 0e02
**Display:** x11 **server:** X.Org **v:** 21.1.4 **with:** Xwayland **v:** 22.1.5
**compositor:** kwin_x11 **driver:****X:****loaded:** modesetting,vesa **unloaded:** fbdev
**alternate:** intel **gpu:** N/A **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:** Unknown-1 **mapped:** None-1 **res:** 1920x1080 **hz:** 60 **size:** N/A
**modes:** 1920x1080
**OpenGL:****renderer:** llvmpipe (LLVM 15.0.5 256 bits) **v:** 4.5 Mesa 22.2.4
**direct render:** Yes
With nomodeset removed the system boots normally in graphics mode, highest resolution which gives very small letters because this is a 4k screen. The result of inxi
**System:**
**Kernel:** 6.0.8-1-default **arch:** x86_64 **bits:** 64 **compiler:** gcc **v:** 12.2.1
**parameters:** BOOT_IMAGE=/boot/vmlinuz-6.0.8-1-default
root=UUID=7dd9193e-6062-4b8e-9e6a-5101f048ab74
resume=/dev/disk/by-uuid/f35ad53c-d442-4906-9827-2e4298a3fec4
mitigations=auto security=apparmor plymouth=0
**Desktop:** KDE Plasma **v:** 5.26.3 **tk:** Qt **v:** 5.15.7 **wm:** kwin_x11 **vt:** 7
**dm:** SDDM **Distro:** openSUSE Tumbleweed 20221123
**Machine:**
**Type:** Laptop **System:** Dell **product:** XPS 15 9520 **v:** N/A
**serial:** <superuser required> **Chassis:** **type:** 10 **serial:** <superuser required>
**Mobo:** Dell **model:** 0YD3W1 **v:** A00 **serial:** <superuser required> **UEFI:** Dell
**v:** 1.8.1 **date:** 10/13/2022
**CPU:**
**Info:** **model:** 12th Gen Intel Core i7-12700H **bits:** 64 **type:** MST AMCP
**arch:** Alder Lake **gen:** core 12 **level:** v3 **built:** 2021+ **process:** Intel 7 (10nm
ESF) **family:** 6 **model-id:** 0x9A (154) **stepping:** 3 **microcode:** 0x424
**Topology:** **cpus:** 1x **cores:** 14 **mt:** 6 **tpc:** 2 **st:** 8 **threads:** 20 **smt:** enabled
**cache:** **L1:** 1.2 MiB **desc:** d-8x32 KiB, 6x48 KiB; i-6x32 KiB, 8x64 KiB
**L2:** 11.5 MiB **desc:** 6x1.2 MiB, 2x2 MiB **L3:** 24 MiB **desc:** 1x24 MiB
**Speed (MHz):** **avg:** 2512 **high:** 2700 **min/max:** 400/4600:4700:3500 **scaling:**
**driver:** intel_pstate **governor:** powersave **cores:** **1:** 2700 **2:** 2700 **3:** 2700
**4:** 2700 **5:** 883 **6:** 2700 **7:** 2700 **8:** 2700 **9:** 2700 **10:** 2700 **11:** 2700 **12:** 2700
**13:** 2700 **14:** 771 **15:** 2700 **16:** 2700 **17:** 2700 **18:** 2700 **19:** 2700 **20:** 2700
**bogomips:** 107520
**Flags:** avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
**Vulnerabilities:**
**Type:** itlb_multihit **status:** Not affected
**Type:** l1tf **status:** Not affected
**Type:** mds **status:** Not affected
**Type:** meltdown **status:** Not affected
**Type:** mmio_stale_data **status:** Not affected
**Type:** retbleed **status:** Not affected
**Type:** spec_store_bypass **mitigation:** Speculative Store Bypass disabled via
prctl
**Type:** spectre_v1 **mitigation:** usercopy/swapgs barriers and __user pointer
sanitization
**Type:** spectre_v2 **mitigation:** Enhanced IBRS, IBPB: conditional, RSB
filling, PBRSB-eIBRS: SW sequence
**Type:** srbds **status:** Not affected
**Type:** tsx_async_abort **status:** Not affected
**Graphics:**
**Device-1:** Intel Alder Lake-P Integrated Graphics **vendor:** Dell **driver:** i915
**v:** kernel **arch:** Gen-12.2 **process:** Intel 10nm **built:** 2021-22+ **ports:**
**active:** eDP-1 **empty:** DP-1, DP-2, DP-3, DP-4, HDMI-A-1
**bus-ID:** 0000:00:02.0 **chip-ID:** 8086:46a6 **class-ID:** 0300
**Device-2:** NVIDIA GA107M [GeForce RTX 3050 Ti Mobile] **vendor:** Dell
**driver:** nouveau **v:** kernel **non-free:** 515.xx+ **status:** current (as of 2022-08)
**arch:** Ampere **code:** GAxxx **process:** TSMC n7 (7nm) **built:** 2020-22
**bus-ID:** 0000:01:00.0 **chip-ID:** 10de:25a0 **class-ID:** 0302
**Device-3:** Microdia Integrated_Webcam_HD **type:** USB **driver:** uvcvideo
**bus-ID:** 3-6:3 **chip-ID:** 0c45:6d1f **class-ID:** 0e02
**Display:** x11 **server:** X.Org **v:** 21.1.4 **with:** Xwayland **v:** 22.1.5
**compositor:** kwin_x11 **driver:** **X:** **loaded:** modesetting **unloaded:** fbdev,vesa
**alternate:** intel,nouveau,nv,nvidia **gpu:** i915 **display-ID:** :0 **screens:** 1
**Screen-1:** 0 **s-res:** 3840x2400 **s-dpi:** 96 **s-size:** 1016x635mm (40.00x25.00")
**s-diag:** 1198mm (47.17")
**Monitor-1:** eDP-1 **model:** Sharp 0x1516 **built:** 2021 **res:** 3840x2400 **hz:** 60
**dpi:** 290 **gamma:** 1.2 **size:** 336x210mm (13.23x8.27") **diag:** 396mm (15.6")
**ratio:** 16:10 **modes:** 3840x2400
**OpenGL:** **renderer:** Mesa Intel Graphics (ADL GT2) **v:** 4.6 Mesa 22.2.4
**direct render:** Yes
I installed the nvidia driver and used prime-select nvidia
to select the nvidia driver, this all worked. When I now attach my docking station with 2 additional screens my desktop is expanded correctly. Any information that I can provide to help to analyze why the install hangs on Probe USB devices?
mrmazda
November 24, 2022, 7:18pm
#13
You seem to have reported a properly working installation. If you wish to take the installation issue further, report a bug pointing to this thread, and let the developers instruct what information they need.
In the future, when pasting the output from any command, please include the command that caused the output as part of the paste. Also, C and M from inxi, unlike S and G, are only needed the first time in a given thread. Nothing about C or M output will subsequently change unless you change CPUs or PCs.
mrmazda
November 25, 2022, 3:11pm
#14