On 11/13/2015 10:26 AM, Sven Joachim wrote:
I see two notable things here:
- There is no sign of the i915 module being loaded, I guess the on-board
graphics is disabled in the BIOS/UEFI?
These are the only things I see in CMOS setup that seem to be related to
graphics:
Settings ->
General ->
System Information ->
Processor Information ->
shows nothing about graphics
Device Information ->
Video Controller = NVIDIA N12P-NS2
Video BIOS Version = 75.19.6A.01.02
Video Memory = 512 MB
Panel Type = 15.6" FHD
Native Resolution = 1920 by 1080
Video ->
Optimus ->
Enable Optimus = disabled
- The boot seems to stall for 27 seconds. That is probably unrelated to
this bug, but if you want to find out why, systemd-analyze(1) is your
friend.
Let me try again, using a stopwatch:
0:00 push power button
0:07 POST displayed
0:12 GRUB menu displayed
0:17 GRUB runs
0:23 LUKS prompt displayed
1:00 LUKS passphrase entered
1:08 login screen displayed
2:00 login as toor
2:02 desktop displayed
It looks repeatable:
[ 4.966532] sda: sda1 sda2 sda3
[ 4.967006] sd 0:0:0:0: [sda] Attached SCSI disk
[ 4.974416] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw
xa/form2 cdda tray
[ 4.974419] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 4.974609] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 4.975611] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 4.975702] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 5.067157] device-mapper: uevent: version 1.0.3
[ 5.067287] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30)
initialised: dm-de...@redhat.com
[ 32.778218] random: nonblocking pool is initialized
[ 34.848447] NET: Registered protocol family 38
[ 35.074219] raid6: sse2x1 4711 MB/s
[ 35.142138] raid6: sse2x2 7738 MB/s
[ 35.210066] raid6: sse2x4 11132 MB/s
[ 35.210067] raid6: using algorithm sse2x4 (11132 MB/s)
[ 35.210068] raid6: using ssse3x2 recovery algorithm
[ 35.210364] xor: automatically using best checksumming function:
[ 35.250018] avx : 22887.000 MB/sec
[ 35.252889] Btrfs loaded
Perhaps it is related to LUKS (?).
I don't think I'll be able to solve the problem, but at least you
have an easy workaround.
You solved the original problem -- the graphical login manager now
works. Thank you.
David
