It’s almost a day when I reinstall tumbleweed on my system and my second monitor is not working cuz of tumbleweed unable to detect it. I tried many workaround, ask many people (on telegram), using kernel parameters, etc. Yet no success. My gpu is amd one and my cpu is amd as well. My usual fix on this is just put amdgpu.dc=0 on kernel parameters and my second monitor will work. But now with grub2 + bls this ain’t working. And when I try grub2 and successfully installed when grub ask for my password (since I add password on my / directory) grub will said invalid password. It does not matter if my password is correct or not and that will happened in instant as if my keystroke is not being registered and only the Enter key. Now I tried Fedora and see if it’s my second is the problem and after I installed fedora edit the grub, add the amdgpu.dc=0, update grub, reboot, and there it is my second monitor is working fine. It’s just opensuse is the one who has the problem. But my last install is just fine. Is there a bug going on core display or on grub2+bls right now? Or anyone can help me on my problem?
WRT 2nd monitor, it might help us to help you if we know more than just computer, AMD GPU and TW. Show I/O from running in a GUI terminal inxi -GSaz -za.
Grub2-bls isn’t mandatory, just new default.
Sorry for late reply was very busy today.
WRT 2nd monitor, it might help us to help you if we know more than just computer, AMD GPU and TW. Show I/O from running in a GUI terminal
inxi -GSaz -za.
I’m sorry I just switched on Fedora for now since I have a work to do immediately and right now I just can’t reinstall opensuse tumbleweed if that bug is still there. But I can sure that even I put amdgpu.dc=0 on my grub/kernel parameters my second monitor will not be recognize. Unlike before and my previous and recently reinstall of TW.
Grub2-bls isn’t mandatory, just new default.
Yup I see that. That’s why on my third attempt of installing TW I use grub+efi and it was installed no problem. But the problem arise when the grub ask for my password and grub won’t (seemingly) register my keystroke. It doesn’t matter if my password was wrong or not it will said my password is wrong. And before grub will take a pause to see if my password was wrong or not and it will unlock the / directory or if my password was wrong. But now the moment I hit Enter key it will just said my password is wrong or invalid.
I think there’s a bug on grub itself and right now I’m just gonna wait for weeks till and hopefully this bug will be crashed hard. Because I can’t leave opensuse I really love openSUSE Tumbleweed. That’s even though this happened to me I’ll try to comeback (THIS WEEK)!
If you provide inxi I/O from Fedora now, then if openSUSE again produces same problem, you can provide it again from TW so the two can be compared.
Here on my fedora
System:
Kernel: 6.17.7-300.fc43.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=(hd3,gpt2)/vmlinuz-6.17.7-300.fc43.x86_64
root=UUID=ca56083f-178f-447e-b0b9-c9e178d1d9d7 ro
rd.luks.uuid=luks-f771258d-ddce-41aa-bf81-6169714b3faf rhgb quiet
amdgpu.dc=0
Desktop: Xfce v: 4.20.1 tk: Gtk v: 3.24.49 wm: xfwm4 v: 4.20.0
with: xfce4-panel tools: xfce4-screensaver vt: 1 dm: LightDM v: 1.32.0
Distro: Fedora Linux 43 (Xfce)
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX
470/480/570/570X/580/580X/590] vendor: Sapphire Nitro+ driver: amdgpu
v: kernel arch: GCN-4 code: Arctic Islands process: GF 14nm built: 2016-20
pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: DVI-D-1,HDMI-A-1
empty: DP-1,DP-2,HDMI-A-2 bus-ID: 06:00.0 chip-ID: 1002:67df
class-ID: 0300 temp: 47.0 C
Display: x11 server: X.Org v: 21.1.20 with: Xwayland v: 24.1.9
compositor: xfwm4 v: 4.20.0 driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0
screens: 1
Screen-1: 0 s-res: 3520x1080 s-dpi: 96 s-size: 932x286mm (36.69x11.26")
s-diag: 975mm (38.38")
Monitor-1: DVI-D-1 mapped: DVI-D-0 pos: bottom-l model: BenQ GL2070
serial: <filter> built: 2017 res: mode: 1600x900 hz: 60 scale: 100% (1)
dpi: 94 gamma: 1.2 size: 432x240mm (17.01x9.45") diag: 494mm (19.5")
ratio: 16:9 modes: max: 1600x900 min: 720x400
Monitor-2: HDMI-A-1 mapped: HDMI-A-0 pos: primary,top-right
model: AOC 27B1H2 serial: <filter> built: 2023 res: mode: 1920x1080 hz: 60
scale: 100% (1) dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23")
diag: 686mm (27") ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 vendor: amd mesa v: 25.2.6 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: AMD Radeon RX 580 Series (radeonsi polaris10
ACO DRM 3.64 6.17.7-300.fc43.x86_64) device-ID: 1002:67df memory: 7.81 GiB
unified: no
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: glxinfo de: xfce4-display-settings x11: xdriinfo,
xdpyinfo, xprop, xrandr
I might wait for week or 2 before I try TW again (even though I’m already itchy to install TW again). And if (hopefully not) the problem still show up I’ll show my TW inxi.
Update on installing tumbleweed again. Aften fews days I now tried installing tumbleweed again with grub+efi and the result show up. Typing my password on my / partition meet me with invalid passphrase (again just like before). Anyone could help me? This issue of mine is here for almost a week now
Using grub2-bls is no good since i can’t get my second monitor to work. Even with updating my grub config. So I tried other opensuse user suggest use grub2+efi and I did and now i can’t seem to boot on my system since grub won’t register my keyboard keystroke. And just instantly prompt me with “invalid passphrase” whether my password is right or wrong.
Check if the Capslock key may be turned on. Is the Numlock key on or off?
Did you update bootloader from grub-bls to grub+efi how? Did you update the bootloader settings by passing update-bootloader after doing this? How did you update/change the bootloader? You do this via YaST2 boot loader, or another method?
You may need to perform a chroot by implementing the openSUSE Rescue system. Can you possibly take a photo of the halted machine and post here? Hopefully more advanced user/s will comment on this also.
Where are your thoughts oninxi -GSaz -za ? I thought inxi -GSaz --za was to be passed instead? Probably a typing error is my first guess.
Thanks
This was a typing error I didn’t catch. --za was intended.
I did check all of it.
Did an reinstall today because I thought this bug might been gone by now.
I did this command on fedora. Since I need to install a distro immediately since i have work that needs to be done immediately.
Here’s the photo:
Quick note: On grub2+bls my system is working flawlessly. I could type my password etc. But my only problem is I can’t seem to make my system to recognised/detect my second monitor. Even though I edited the kernel parameters and updated my grub config.
I feel like the “amdgpu.dc=0” is alright it just I think the command to update grub on grub+bls is wrong. That’s why my edit on grub config is not being read/updated.
It seems as the passphrase must not be entered correctly, for what I know I do not think it is a bug with LUKS?
You know about the ability of to change bootloader types at the installers summary screen right?
Maybe this is a deeper problem and you are somehow being prevented from opening / at all. Are you sharing partitions or something with the Fedora installation? You are able to boot Fedora on the same machine successfully at this time?
FYI, I have dual monitor desktop here and use the amdgpu.dc=1 kernel parameter with the Radeon 540X/550X/630.
No. I’m confidently 100% correct on my password since my password ain’t that long nor have special character.
Yes that’s why I change to from grub2+bls to grub2+efi on my reinstall again.
This my thought that’s why I wait for a week to reinstalled opensuse again.
Nope I completely remove Fedora.
Yes. Completely boot on fedora and successfully make my second monitor to work on fedora as well. By configuring/adding command on kernel parameters and update it.
I did that as well and the same result show up.
When you fire up the installer are you wiping everything or reusing partitions?
Yes I’m wiping everything.
Might be good to start a new thread and explain about the problem that is occurring with LUKS passphrase.