On Mon, 2017-05-29 at 09:48 +0300, Robert Munteanu wrote:

Hi,

On Mon, May 29, 2017 at 1:54 AM, Juan Erbes wrote:

...

Many ACPI errors: May 28 22:36:15 linux-lj8d kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363) May 28 22:36:15 linux-lj8d kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff957abfcd00a0), AE_NOT_FOUND (20170119/psparse-543)

(snip)

I am getting a number of these at boot as well after a MB firmware update, with no side effects. They are probably not the cause of your problems.

AE_NOT_FOUND always indicates a BIOS error. It's the equivalent of using an undefined variable in a sane programming language. Martin -- Dr. Martin Wilck , Tel. +49 (0)911 74053 2107 SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Sudhir Anand [05-28-17 19:06]:

On Sunday, 28 May 2017 22:54:53 BST Michael Born wrote: [...]

...

PS: I had a very similar problem with Suse 42.2 last week which made me change to TW. I suspect that it has to do with my rx480 graphics card and the amdgpu driver. In addition, I use the openCL part of the amdgpu-PRO binary driver.

Have you installed Nvidia driver?

surely not to run an amd card... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Thank you all for your comments. I did not install any Nvidia stuff for my AMD card. The ACPI/BIOS errors of my MSI Z77 mainboard are there for many years - I don't know why it is so hard for them to write a BIOS that has no wrong parameters in it... But, I don't think that is my problem. The messages have been there forever. I think your Nvidia comments are helpful. Although, I use the open source amdgpu+MESA drivers, I installed the OpenCL driver from the binary amdgpu-PRO package with: ./amdgpu-pro-install --compute Maybe that messed with my initrd. I will check that tonight when I'm back home. But, what could prevent the VESA fall-back driver to kick in? Cheers, Michael -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Monday, 29 May 2017 08:35:21 BST Michael Born wrote:

Thank you all for your comments.

I did not install any Nvidia stuff for my AMD card. The ACPI/BIOS errors of my MSI Z77 mainboard are there for many years - I don't know why it is so hard for them to write a BIOS that has no wrong parameters in it... But, I don't think that is my problem. The messages have been there forever.

I think your Nvidia comments are helpful. Although, I use the open source amdgpu+MESA drivers, I installed the OpenCL driver from the binary amdgpu-PRO package with: ./amdgpu-pro-install --compute

Maybe that messed with my initrd. I will check that tonight when I'm back home.

But, what could prevent the VESA fall-back driver to kick in?

Cheers, Michael

I am not an expert and will give my workaround and thoughts. During the boot process, a graphical driver has been registered to load. For a number of reasons, the driver is not loading successfully, resulting in the blank screen you are experiencing and possibly preventing the loading of vesa or any other driver. One solution is to uninstall all AMD or any other third party drivers by booting into runlevel 3, which is the level before graphical login and start of xserver. Once the terminal screen appears, uninstall the third party drivers. As I have no experience of AMD, I cannot advise on the exact steps to do this. Perhaps other members of this list can advise. Then run mkinitrd and reboot. If no other graphical drivers are available, xserver should start with vesa or framebuffer driver. If all else fails, a re-install might be an easier solution. On my computers there are two installations of Opensuse and both are available on grub boot manager. The home directory is on a separate partition and accessible to both. On my laptop, one partition has TW, one Leap 42.2 and the third one is the dark side (windows). I can reboot into the previous working version to carry on working and repair the version which is not working. If there are issues with graphical login (and there have been recently) or anything else and a broken system cannot be rectified, I find a re-install is an easier solution. Regards. -- Sudhir Anand -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

02.06.2017 18:58, Frank Kunz пишет:

Am 28.05.2017 um 23:54 schrieb Michael Born:

...

I installed TW from iso/usb stick a few days ago and also ran zypper dup --no-allow-vendor-change So, I'm on the latest snapshot. The pc was rebooted several times without a problem (default boot entry).

Today, after rebooting the pc I no longer get to the graphical login screen. After entering the LUKS password for my /home I get some more messages and then a blinking cursor. The keyboard LEDs stay dark (when pressing num-lock, caps-lock) and alt+ctrl+F1 doesn't work. Only the power button tells the system to shut down.

Unfortunately I have the same problem but different hardware: HP EliteBook 2760p with i915 graphics. It freezes when it should start the graphical login, only power button and magic sysrq is working then.

Output of journal: http://susepaste.org/44594523

How and when this output was taken if you say you cannot access system? Try booting with plymouth.enable=0, it show where it hangs. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

04.06.2017 14:53, Frank Kunz пишет:

Am 04.06.2017 um 08:17 schrieb Andrei Borzenkov:

...

...

Unfortunately I have the same problem but different hardware: HP EliteBook 2760p with i915 graphics. It freezes when it should start the graphical login, only power button and magic sysrq is working then.

Output of journal: http://susepaste.org/44594523

How and when this output was taken if you say you cannot access system?

I started the machine with "systemd.unit=multi-user.target". This comes up and then i got the journal by "journalctl -b -1".

...

Try booting with plymouth.enable=0, it show where it hangs.

I tried that, but then I get just a blank screen with a cursor. Without plymouth.enable=0 the boot text output is printed on the screen, the plymouth screen is not started before the system freezes.

The boot stalls at that point (tested multiple times, the order of the printed lines may differ):

Started Modem Manager Started Network Manager Script Dispatcher Service Started Login and scanning if iSCSI devices

During the collection of further info I found out that the system freeze is only temporary. It continues boot after about 5 minutes. Here is the "systemctl -b" output after the startup:

http://susepaste.org/24964207

Try booting with systemd.log_level=debug. It may show what exactly it waits for.

The first time gap in the log:

Jun 04 13:20:32 goofy kernel: usb 2-1.6: Manufacturer: Broadcom Corp Jun 04 13:27:11 goofy systemd-cryptsetup[374]: Set cipher aes, mode xts-plain64, key size 256 bits for device /dev/disk/by-id/ata-OCZ-ARC100_A22L1061528004319-part2.

is when the system waits for the luks passphrase. The second one is at 13:27:18, where ModemManager started.

Br, Frank

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org