You are not logged in.
Pages: 1
thanks for your help and attention
the bootloaders work fine ( tested systemd-boot and grub and window's )
the bios works fine ( it is graphical )
the uefi shell works fine but I ve never used it before so if something wasnt i couldnt tell
I thought it was caused by an arch update at first but no OS will boot ( tried arch debian windows and arch-based distro )
each time the screen displays the last image from the bootloader and gets stuck until I press the power button
tried emptying the battery completely and then pressing the power button for 15 secs as advised on the manufacturer's website
tried using speak up ( stays silent )
tried using a single ram stick ( exact same issue )
tried using no ram stick ( stuck on black screen )
the integrated keyboard rgb works
the device worked fine for a month
it is still under warranty ( I m probably gonna have to use it )
it is a medion erazer e40 ( 12th gen intel i5 and 4050 laptop nvidia GPU )
do you have any idea what is the problem and how to fix it
i m suffering right now
thanks in advance
Offline
What OSes you have installed?
How your boot was setup (what boot loader)?
When it last worked?
What did you do (or maybe it stopped working itself)?
And what error you actually see - post it here.
Offline
The only OS I have ever install on this computer was arch but I tried using other .isos to see if it was an arch only problem
It used systemd bootloader
It last worked tuesday
I did an arch update ( through paru -Syu for AUR and repos then through discover for flatpaks and kde addons )
The update from discover did complain about failing to update something called uefi- dash - something I can't remember maybe settings but I simply ignored it
I don't see any error, the screen is just freezed black or on the last imaged displayed by the boot loader when trying to boot an OS or memtest
Offline
If you have available systemd boot menu you can press "e" to edit kernel boot parameters (h, ?, F1 for list of available keys) and remove "quiet" and eventually change "loglevel" to 5 or 6 to see boot error.
Booting from live cd you can mount your system partition and see and post contents of file "/var/log/pacman.log" which contains your update log by command "curl -F 'f:1=<-' ix.io < /var/log/pacman.log" .
Offline
There were no quiet parameter in the kernel boot parameters and adding loglevel=6 didn't change anything
the boot parameters were root=PARTUUID=long string of dash seperated hexadecimal numbers zswap.enabled=0 rw rootfstype=f2fs to which I appended under your advise loglevel=6
Booting from a live usb stick doesn't work, like with the installed OS, the screen gets stuck on the last image displayed by the bootloader or on a blackscreen
The only thing a live usb has allowed me to do is access the uefi shell and a bootloader other than systemd
I am therefore unable to run that command or see the content of that file unless there is a way to do so from uefi interactive shell or bios or a bootloader
I unfortunately don't own any other computer with a compatible ssd slot to check the contents of pacman.log
since no operating system I tried wants to boot from anything I don't think it s an issue with arch
Offline
Do you have 'secure boot' enabled in uefi bios? Disable it for now and try to boot something.
When you power on laptop does it display something; at least manufacturer logo? Does controls blinking? Do you hear/see if it is working?
Last edited by xerxes_ (2023-09-01 11:44:43)
Offline
it is disabled and has always been since I took my hands on this computer
when it is enabled instead of crashing it doesn't even allow the bootloader to launch, displays Linux Boot Manager has been blocked by the current security policy and sends me to the bios
I just tried turning it on and booting into windows, instead of getting stuck on the last image from the bootloader it gets stuck on the manufacturer logo, PROGRESS! I guess
Offline
Add "systemd.unit=multi-user.target nomodeset" to the https://wiki.archlinux.org/title/Kernel_parameters
If that doesn't work, try "systemd.unit=rescue.target nomodeset"
And because of
it is a medion erazer e40 ( 12th gen intel i5 and 4050 laptop nvidia GPU )make sure to also add "nvidia_drm.modeset=1", https://wiki.archlinux.org/title/NVIDIA … de_setting
Offline
tried both parameters twice ( once with and once without nvidia argument )
exact same problem, right after I press enter it gets stuck on a black screen. the fans are also louder than they ought to be for the workload I forgot to precise earlier
Offline
So Arch doesn't boot the rescue target w/o modesetting, windows doesn't boot, some live distro from USB doesn't boot - you might wanna try an UEFi update, but that's proabably also hard to do unless the UEFI can self-udpate from a prepared usb key (and succeeds with this)
Offline
Since I now believe everything originated from a failed automatic uefi update from kde discover could you tell me the source it uses to update the firmware. Is it the manufacturer? if so they would be responsible for the problem and the warranty could apply otherwise they could argue that I caused the issue through bad software and have me pay for diagnostic + motherboard replacement potentially. also how do I know if UEFI can self update and if so how to update it?
Offline
Discover seems to FE https://wiki.archlinux.org/title/Fwupd
I don't find anything Medion in https://fwupd.org/lvfs/devices/ - apparently they merged w/ lenovo, but I've no idea whether you'd get FW updates this way at all.
Offline
Pages: 1