LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 11-17-2013, 01:30 AM   #1
san2ban
Member
 
Registered: May 2013
Location: Bengaluru / India
Distribution: Slackware14-64bit
Posts: 55

Rep: Reputation: Disabled
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
 
Old 11-17-2013, 01:46 AM   #2
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,288

Rep: Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802
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.
 
Old 11-17-2013, 01:54 AM   #3
san2ban
Member
 
Registered: May 2013
Location: Bengaluru / India
Distribution: Slackware14-64bit
Posts: 55

Original Poster
Rep: Reputation: Disabled
Thanks.
I will try and report back
 
Old 11-17-2013, 02:59 AM   #4
san2ban
Member
 
Registered: May 2013
Location: Bengaluru / India
Distribution: Slackware14-64bit
Posts: 55

Original Poster
Rep: Reputation: Disabled
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
 
Old 11-17-2013, 03:14 AM   #5
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.1 (multi-lib) KDE 4.11.4
Posts: 1,399

Rep: Reputation: 131Reputation: 131
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
 
Old 11-17-2013, 03:35 AM   #6
san2ban
Member
 
Registered: May 2013
Location: Bengaluru / India
Distribution: Slackware14-64bit
Posts: 55

Original Poster
Rep: Reputation: Disabled
Mine is a simple desktop, with 2 HDD, slackware, Xp one on each

Will try and report back
 
Old 11-17-2013, 03:50 AM   #7
san2ban
Member
 
Registered: May 2013
Location: Bengaluru / India
Distribution: Slackware14-64bit
Posts: 55

Original Poster
Rep: Reputation: Disabled
Negative. Same behaviour. Could not get a command prompt also. Blank Screen
 
Old 11-17-2013, 04:20 AM   #8
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.1 (multi-lib) KDE 4.11.4
Posts: 1,399

Rep: Reputation: 131Reputation: 131
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
 
Old 11-17-2013, 05:53 AM   #9
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,288

Rep: Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802
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.
 
Old 11-23-2013, 08:28 AM   #10
san2ban
Member
 
Registered: May 2013
Location: Bengaluru / India
Distribution: Slackware14-64bit
Posts: 55

Original Poster
Rep: Reputation: Disabled
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
 
Old 11-23-2013, 04:33 PM   #11
mlslk31
Member
 
Registered: Mar 2013
Location: Florida, USA
Distribution: Slackware, FreeBSD
Posts: 98

Rep: Reputation: 28
Quote:
Originally Posted by san2ban View Post
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.
 
Old 11-23-2013, 08:47 PM   #12
san2ban
Member
 
Registered: May 2013
Location: Bengaluru / India
Distribution: Slackware14-64bit
Posts: 55

Original Poster
Rep: Reputation: Disabled
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"

Last edited by san2ban; 11-23-2013 at 08:48 PM.
 
Old 11-23-2013, 09:23 PM   #13
mlslk31
Member
 
Registered: Mar 2013
Location: Florida, USA
Distribution: Slackware, FreeBSD
Posts: 98

Rep: Reputation: 28
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.
 
Old 11-23-2013, 09:50 PM   #14
san2ban
Member
 
Registered: May 2013
Location: Bengaluru / India
Distribution: Slackware14-64bit
Posts: 55

Original Poster
Rep: Reputation: Disabled
Mine does not blank for 3 seconds, permanently
 
Old 11-23-2013, 11:21 PM   #15
mlslk31
Member
 
Registered: Mar 2013
Location: Florida, USA
Distribution: Slackware, FreeBSD
Posts: 98

Rep: Reputation: 28
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Display disappears before login screen cdr_nitjsr@yahoo.com Linux - Newbie 2 10-26-2013 10:41 AM
[SOLVED] Display problem with screen when booting up Slackware 13.37 Kipkay211 Linux - Newbie 12 05-08-2012 05:12 PM
display disappears after splash - ubuntu/t40 laptop iansworld Linux - Laptop and Netbook 1 09-17-2008 07:06 PM
Only has half of display in GUI mrdensity Linux - General 5 01-09-2003 02:27 PM


All times are GMT -5. The time now is 09:03 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration