LinuxQuestions.org - [SOLVED] Slackware 14.1, display disappears half way through while booting

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Slackware 14.1, display disappears half way through while booting (https://www.linuxquestions.org/questions/slackware-14/slackware-14-1-display-disappears-half-way-through-while-booting-4175484875/)

Slackware 14.1, display disappears half way through while booting

Dear Slackers
Upgraded from 14.0 to 14.1, through slackpkg command. Did everything as per instruction on slackdocs. Created initrd, lilo etc.

Now, when the kernel 3.10.17 is booting, half way through, the display disappears. My dell monitor says "Auto adjustment in progress', but no display

Pl. suggest a remedy

At the lilo prompt when booting, hit TAB and enter ' video=1024x768' or some other suitable video mode to test appending a kernel boot parameter.
If this works, you can make the change permanent by adding it to the 'append =' line in /etc/lilo.conf and rerunning lilo.

Thanks.
I will try and report back

Posting from system rescue CD

Code:



root@sysresccd /root % chroot /mnt /bin/bash

bash-4.2# nano /etc/lilo.conf

bash-4.2# lilo 

Warning: LBA32 addressing assumed

Warning: /dev/sdb is not on the first disk

Warning: Unable to determine video adapter in use in the present system.

Warning: Video adapter does not support VESA BIOS extensions needed for

  display of 256 colors.  Boot loader will fall back to TEXT only operation.

Added 3.10.17  +  *

Added WindowsXP

4 warnings were issued.

bash-4.2# lilo -v

LILO version 24.0 (released 07-Juni-2013)

  * Copyright (C) 1992-1998 Werner Almesberger  (until v20)

  * Copyright (C) 1999-2007 John Coffman  (until v22)

  * Copyright (C) 2009-2013 Joachim Wiedorn  (since v23)

This program comes with ABSOLUTELY NO WARRANTY. This is free software 

distributed under the BSD License (3-clause). Details can be found in 

the file COPYING, which is distributed with this software.

Compiled at 17:40:54 on Oct 27 2013



Warning: LBA32 addressing assumed

Reading boot sector from /dev/sdb

Warning: /dev/sdb is not on the first disk

Warning: Unable to determine video adapter in use in the present system.

Using BITMAP secondary loader

Calling map_insert_data

Mapping bitmap file /boot/slack.bmp

Warning: Video adapter does not support VESA BIOS extensions needed for

  display of 256 colors.  Boot loader will fall back to TEXT only operation.

Calling map_insert_file



Boot image: /boot/vmlinuz-generic-3.10.17

Mapping RAM disk /boot/initrd.gz

The initial RAM disk will be loaded in the high memory above 16M.

Added 3.10.17  +  *



Boot other: /dev/sda1, on /dev/sda, loader CHAIN

Added WindowsXP



Writing boot sector.

/boot/boot.0810 exists - no boot sector backup copy made.

4 warnings were issued.

bash-4.2# nano /etc/lilo.conf

bash-4.2# nano /etc/lilo.conf

bash-4.2# lilo

Warning: LBA32 addressing assumed

Warning: /dev/sdb is not on the first disk

Warning: Unable to determine video adapter in use in the present system.

Warning: Video adapter does not support VESA BIOS extensions needed for

  display of 256 colors.  Boot loader will fall back to TEXT only operation.

Added 3.10.17  +  *

Added WindowsXP

4 warnings were issued.

bash-4.2# nano /etc/lilo.conf

bash-4.2# lilo

Warning: LBA32 addressing assumed

Warning: /dev/sdb is not on the first disk

Warning: Unable to determine video adapter in use in the present system.

Warning: Video adapter does not support VESA BIOS extensions needed for

  display of 256 colors.  Boot loader will fall back to TEXT only operation.

Added 3.10.17  +  *

Added WindowsXP

4 warnings were issued.

bash-4.2# lilo -v

LILO version 24.0 (released 07-Juni-2013)

  * Copyright (C) 1992-1998 Werner Almesberger  (until v20)

  * Copyright (C) 1999-2007 John Coffman  (until v22)

  * Copyright (C) 2009-2013 Joachim Wiedorn  (since v23)

This program comes with ABSOLUTELY NO WARRANTY. This is free software 

distributed under the BSD License (3-clause). Details can be found in 

the file COPYING, which is distributed with this software.

Compiled at 17:40:54 on Oct 27 2013



Warning: LBA32 addressing assumed

Reading boot sector from /dev/sdb

Warning: /dev/sdb is not on the first disk

Warning: Unable to determine video adapter in use in the present system.

Using BITMAP secondary loader

Calling map_insert_data

Mapping bitmap file /boot/slack.bmp

Warning: Video adapter does not support VESA BIOS extensions needed for

  display of 256 colors.  Boot loader will fall back to TEXT only operation.

Calling map_insert_file



Boot image: /boot/vmlinuz-generic-3.10.17

Mapping RAM disk /boot/initrd.gz

The initial RAM disk will be loaded in the high memory above 16M.

Added 3.10.17  +  *



Boot other: /dev/sda1, on /dev/sda, loader CHAIN

Added WindowsXP



Writing boot sector.

/boot/boot.0810 exists - no boot sector backup copy made.

4 warnings were issued.

bash-4.2#

Still, display disappears halfway through

I had this problem with 14.0, it was, in my case, to do with the nvidia driver.

Wait until the disk activity stops, type your user name, then hit return/enter, type your password, then hit return/enter. With any luck you will now be at a command prompt. If not try typing startx.

Once you can see what you're doing then you will be able to find and fix the problem. I had to remove nouveau and install nvidia.

samac

Mine is a simple desktop, with 2 HDD, slackware, Xp one on each

Will try and report back

Negative. Same behaviour. Could not get a command prompt also. Blank Screen

Yes, you have to let it boot to a blank screen and then when all the disk activity is finished type the commands into the blank screen. It is possible that your system has booted but the graphic card is causing the problem, which X might be able to work around.

samac

Quote:

At the lilo prompt when booting, hit TAB and enter ' video=1024x768' or some other suitable video mode to test appending a kernel boot parameter.

Perhaps I should have pointed out the space character at the start of the ' video=1024x768' string.

Tried everything. No use.

Think I will download a fresh 14.1 ISO and re-install

Cannot upgrade 14.0 to 14.1, via slackpkg, by me

Quote:

Originally Posted by san2ban (Post 5069390)

Tried everything. No use.

Think I will download a fresh 14.1 ISO and re-install

Cannot upgrade 14.0 to 14.1, via slackpkg, by me

OK, that might solve the problem. On Intel--at least for the 845G chipset--the KMS driver simply stopped using 8bpp mode for the framebuffer console, if only for a very short time in the kernel 3.7-3.8 timeframe. I had to work around it with a line more like "video=1024x768-16@60" until it got fixed. I have a Dell monitor as well, and it went crazy until it could settle down on a set of timings. You might find that "video=640x480-16" will cause less distress for your monitor, at least until you get one of the newer kernels that's nicer about all of this. Even 3.10 wasn't all that good at first, but it's been fine for a few versions.

If you're not using the Intel driver, then please find the name of your video chipset and mention it.

Chrooted using system rescue CD

Code:



video                  16669  1 i915

bash-4.2# lspci -k

00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)

        Subsystem: Gigabyte Technology Co., Ltd Device 5000

        Kernel driver in use: agpgart-intel

lspci: Unable to load libkmod resources: error -12

00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)

        Subsystem: Gigabyte Technology Co., Ltd Device d000

        Kernel driver in use: i915

00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 01)

        Subsystem: Gigabyte Technology Co., Ltd GA-D525TUD (Realtek ALC887)

00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 01)

        Kernel driver in use: pcieport

00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 01)

        Kernel driver in use: pcieport

00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 01)

        Subsystem: Gigabyte Technology Co., Ltd GA-D525TUD

        Kernel driver in use: uhci_hcd

00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 01)

        Subsystem: Gigabyte Technology Co., Ltd GA-D525TUD

        Kernel driver in use: uhci_hcd

00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 01)

        Subsystem: Gigabyte Technology Co., Ltd GA-D525TUD

        Kernel driver in use: uhci_hcd

00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 01)

        Subsystem: Gigabyte Technology Co., Ltd GA-D525TUD

        Kernel driver in use: uhci_hcd

00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 01)

        Subsystem: Gigabyte Technology Co., Ltd GA-D525TUD

        Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)

00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)

        Subsystem: Gigabyte Technology Co., Ltd Device 5001

00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)

        Subsystem: Gigabyte Technology Co., Ltd Device b001

        Kernel driver in use: ata_piix

00:1f.2 IDE interface: Intel Corporation NM10/ICH7 Family SATA Controller [IDE mode] (rev 01)

        Subsystem: Gigabyte Technology Co., Ltd Device b002

        Kernel driver in use: ata_piix

00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 01)

        Subsystem: Gigabyte Technology Co., Ltd GA-8I945PG-RH/GA-D525TUD Mainboard

        Kernel driver in use: i801_smbus

02:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet (rev c0)

        Subsystem: Gigabyte Technology Co., Ltd Device e000

        Kernel driver in use: atl1c

bash-4.2#

says "unable to load libkmod resources, error-12"

Quote:

Code:

Kernel driver in use: i915

Looking back at the kernel 3.10 Changelogs, there are i915 fixes in 3.10.{3,5,6,7,10,11,14,15,17}. [Kernel fixes for the Intel graphics chipsets at or later than the 830 (10 years old?) are listed in the Changelogs as "drm/i915".] The 3-second blank screen while booting might have been fixed in one of those middle fixes. I don't know how far back these fixes were backported, though.

Mine does not blank for 3 seconds, permanently

Hmm, yes, and I'll readjust my line of thinking, and defer to the experts here. I don't do initrd at all. Maybe the Intel fixes that helped my hardware has broken something on your hardware. No telling. There are lots of ways to go from here.

A more full list of kernel command-line options for the framebuffer console are here:

https://www.kernel.org/doc/Documentation/fb/modedb.txt

Also, if you think that the software is at fault, you can go to https://bugs.freedesktop.org/ and see if an issue has been fixed. It's in the DRI section, and the section for kernel-related Intel display issues is called "DRM/Intel". The search term "blank screen" gives too many results for me to really narrow it down, though :(

Should you be able to get the output of `dmesg` somehow--ssh, serial, start X11 blind, etc.--know that there's a kernel boot parameter called "drm.debug" that you might used to get more info. I've used only the "drm.debug=0xe" setting, which is a bit much and will even announce when it's adjusting to change of VTs.