Hi, Same issue here with Tumbleweed, updated to 4.4 kernel and LUKS crypted partition (but not root fortunately) Symptoms are similar but not exactly the same. I was able to boot when insisting... but protected partition is not mounted. Looking at systemd journal I could see that plymouth related issues : Feb 12 09:30:25 systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV Feb 12 09:30:25 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termi Feb 12 09:30:25 systemd[1]: plymouth-start.service: Unit entered failed state. Feb 12 09:30:25 systemd[1]: plymouth-start.service: Failed with result 'core-dump'. I have had issues with plymouth and luks for dome time actually https://bugzilla.opensuse.org/show_bug.cgi?id=948975 rgds Paul On Fri, Feb 12, 2016 at 3:41 PM, Robert Schweikert wrote:

On 02/12/2016 09:09 AM, Fabian Vogt wrote:

...

Hi,

I've got a similiar issue (starting from kernel 4.4 IIRC) I haven't got around to debug yet. My lenovo ThinkPad X250 (Broadwell Graphics) hangs at the same point (doesn't display that message though) and just nothing happens. What works for me is to append "plymouth.enable=0" to the kernel cmdline. I'm using an encrypted LVM setup as well, maybe it's related.

Appears to be related, adding "plymouth.enable=0" does the trick.

With plymouth disabled the passphrase is requested right after the the initial message.

Thanks :) :) made my day Robert

P.S. Yes, I updated the bug report with the information.

-- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo

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

I think an update on "Tumbleweed – Review of the week xx" from DimStar would makes sense. Myself I read carefully every week and I think a warning coming from Dominique would be the best channel. Message could be: Warning: Tumbleweed users using LUKS encrypted devices reported plymouth related issues. Current workaround identified is to disable plymouth at boot time with "plymouth.enable=0" on kernel command line. rgds Paul On Mon, Feb 15, 2016 at 1:31 PM, Ludwig Nussel wrote:

Robert Schweikert wrote:

...

On 02/12/2016 09:09 AM, Fabian Vogt wrote:

...

I've got a similiar issue (starting from kernel 4.4 IIRC) I haven't got around to debug yet. My lenovo ThinkPad X250 (Broadwell Graphics) hangs at the same point (doesn't display that message though) and just nothing happens. What works for me is to append "plymouth.enable=0" to the kernel cmdline. I'm using an encrypted LVM setup as well, maybe it's related.

Appears to be related, adding "plymouth.enable=0" does the trick.

With plymouth disabled the passphrase is requested right after the the initial message.

How can we communicate such issues so the next one who gets hit knows where to look for first?

cu Ludwig

-- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ 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

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

On vendredi, 12 février 2016 21.13:01 h CET Stefan Seyfried wrote:

Am 12.02.2016 um 14:54 schrieb Robert Schweikert:

...

Hi,

Could use some help....

I know don't reboot a running system.... but kidding aside, yesterday I did reboot TW system Lenovo X1 Carbon, all Intel HW, and well that was it. When the system attempts to boot I end up with

Ignoring BGRT: Invalid version 0 (expected 1)

on the screen after the initial messages about initrd and kernel loading, (boo#966255).

The symptom is that the message shows up, then the screen goes blank and then the message is redisplayed. Thus I think this is the point where I would under regular circumstances enter the passphrase for my encrypted partition.

I had to remove "splash=silent" from the kernel command line to get it to ask for the password. I would think plymouth is borked.

To be able to boot my newer skylake hidpi on nvme I finally opted to this kind of command line BOOT_IMAGE=/vmlinuz-4.4.0-3-default root=/dev/mapper/vg0-lvtwroot root=LABEL=TWROOT elevator=cfq crashkernel=512M-:256M rd.vconsole.keymap=ch-fr rd.vconsole.font=ter-v32b.psfu rd.locale.LANG=en_US.UTF-8 rd.luks.allow-discard showopts nosplash quiet luks=yes GPU is driven by nvidia 352.79 for the moment (nouveau xorg is lacking GF117 chipset actually) I've giving up to try to make the optimus working, support for newer intel gpu was even worst (read not ready yet ;-) and no plymouth installed .... Also as plymouth is related could it be http://bugzilla.opensuse.org/show_bug.cgi?id=959986 changes done ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

sorry need coffee... I meant reported the bug in bugzilla. On Mon, Feb 15, 2016 at 9:41 AM, Paul Gonin wrote:

Hi,

Anyone reported the issue already ? On my side, I can't access my luks based device and a consequence is that I lost my vpn configuration.

thanks Paul

On Fri, Feb 12, 2016 at 10:03 PM, Bruno Friedmann wrote:

...

On vendredi, 12 février 2016 21.13:01 h CET Stefan Seyfried wrote:

...

Am 12.02.2016 um 14:54 schrieb Robert Schweikert:

...

Hi,

Could use some help....

I know don't reboot a running system.... but kidding aside, yesterday I did reboot TW system Lenovo X1 Carbon, all Intel HW, and well that was it. When the system attempts to boot I end up with

Ignoring BGRT: Invalid version 0 (expected 1)

on the screen after the initial messages about initrd and kernel loading, (boo#966255).

The symptom is that the message shows up, then the screen goes blank and then the message is redisplayed. Thus I think this is the point where I would under regular circumstances enter the passphrase for my encrypted partition.

I had to remove "splash=silent" from the kernel command line to get it to ask for the password. I would think plymouth is borked.

To be able to boot my newer skylake hidpi on nvme I finally opted to this kind of command line BOOT_IMAGE=/vmlinuz-4.4.0-3-default root=/dev/mapper/vg0-lvtwroot root=LABEL=TWROOT elevator=cfq crashkernel=512M-:256M rd.vconsole.keymap=ch-fr rd.vconsole.font=ter-v32b.psfu rd.locale.LANG=en_US.UTF-8 rd.luks.allow-discard showopts nosplash quiet luks=yes

GPU is driven by nvidia 352.79 for the moment (nouveau xorg is lacking GF117 chipset actually) I've giving up to try to make the optimus working, support for newer intel gpu was even worst (read not ready yet ;-)

and no plymouth installed ....

Also as plymouth is related could it be http://bugzilla.opensuse.org/show_bug.cgi?id=959986 changes done ?

--

Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch

openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot

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

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

On Mon, Feb 15, 2016 at 12:45 AM, Paul Gonin wrote:

...

To be able to boot my newer skylake hidpi on nvme I finally opted to this kind of command line BOOT_IMAGE=/vmlinuz-4.4.0-3-default root=/dev/mapper/vg0-lvtwroot root=LABEL=TWROOT elevator=cfq crashkernel=512M-:256M rd.vconsole.keymap=ch-fr rd.vconsole.font=ter-v32b.psfu rd.locale.LANG=en_US.UTF-8 rd.luks.allow-discard showopts nosplash quiet luks=yes Anyone reported the issue already ? On my side, I can't access my luks based device and a consequence is

I don't know if this is relevant, but... I have a fresh load of TW on a Dell server, and, within that, a fresh load of TW as a Xen DomU guest. Following the most recent update, I am still able to boot my physical host, but pygrub can no longer boot my DomU. In fact, pygrub -l aborts with no output, suggesting it can't even understand the DomU. I had to extract the kernel and initrd from the DomU manually to the Dom0 host, and use that in similar fashion (specifying kernel and initrd manually) to get my DomU to boot. (And my dom0 has 34 instances of [bioset] running, but that may be orthogonal.)

sorry need coffee... I meant reported the bug in bugzilla.

I may well have the same issue... Glen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Mon, Feb 15, 2016 at 8:36 AM, Olaf Hering wrote:

...

Following the most recent update pygrub can no longer boot my DomU

As a workaround, try grub2-x86_64-xen.rpm. Remove "boot=pygrub" and use 'kernel="/usr/lib/grub2/x86_64-xen/grub.xen"' Olaf

Dear Olaf - You, sir, are a genius! Thank you! In the movie, "Back to the Future," Doc Brown is excited to learn that he finally built something that works, and shouts, "IT WORKS!!!!!" Please hear that voice as I shout the same! THANK YOU! THANK YOU! Glen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org