[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#696244: marked as done (kms problems when using plymouth on sandy-bridge)

Your message dated Sat, 24 Apr 2021 07:26:47 -0700 (PDT)
with message-id <60842aa7.1c69fb81.620c4.375d@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #696244,
regarding kms problems when using plymouth on sandy-bridge
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
696244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696244
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: plymouth-drm
Version: 0.8.8-3
Severity: normal

Hi,

this is a bug that I suspect is in plymouth, but could as well be in
the kernel or in X. I describe the issue here, please reassign to
kernel or X if appropriate.

Steps to reproduce:

(1) boot Debian sid with Debian kernel and "quiet splash" on the
command line

(2) See Debian boot with plymouth solar theme

(3) Wait until display manager comes up

(4) Switch to tty1 using Ctrl-Alt-F1

(5) See a working KMS "text" console

(6) Switch to tty7 using Ctrl-F7

(7) See cursor vanishing and tty1 still displayed

>From this point, the console is unuseable. Even Magic SysRq does not
work any more. However, the machine remains on the network and can be
shutdown over ssh without problems.

Repeating the same without "splash" on the kernel command line,
therefore not using the plymouth splash screen, makes switching back
to X successful.

The hardware is a ThinkPad T520 with a Core i7 processor, using the
Core Processor Family IGC:

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd
Generation Core Processor Family Integrated Graphics Controller
[8086:0126] (rev 09)

The machine is equipped with nVidia Optimus as well, but this is not
being used, and neither the proprietary nVidia driver nor any open
source alternative such as bumblebee are installed.

I can also reproduce this with a vanilla 3.7.1 kernel and I suspect
that this applies to all other kernel versions between 3.2 and 3.7 as
well.

If additional information is necessary, I'll try to deliver it.

Greetings
Marc


-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages plymouth-drm depends on:
ii  fontconfig-config  2.9.0-7.1
ii  libc6              2.13-37
ii  libcairo2          1.12.2-2
ii  libdrm2            2.4.33-3
ii  libglib2.0-0       2.33.12+really2.32.4-3
ii  libkms1            2.4.33-3
ii  libpango1.0-0      1.30.0-1
ii  libpng12-0         1.2.49-3
ii  multiarch-support  2.13-37
ii  plymouth           0.8.8-3
ii  ttf-dejavu-core    2.33-3

Versions of packages plymouth-drm recommends:
pn  plymouth-themes-all  <none>

plymouth-drm suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: