LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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
 
Search this Thread
Old 08-08-2013, 03:02 PM   #1
fsauer
Member
 
Registered: Jul 2012
Posts: 38

Rep: Reputation: Disabled
upgrade to latest current (kernel 3.10.5): black screen


I happily upgraded from 3.9.10 to the new kernel plus related upgrades, via slackpkg.

The machine is an asus zenbook, efi, i915... no troubles prior to the upgrade

All looked nice, the boot process whisked by, and then, suddenly there only was a black screen. Being in runmode 4, I switched to Console 1 (Ctrl-Alt-F1) which did not change this. All is black....

Rebooted from a setup usb, boots from the root at the hard disk, X is black also. But the console is readable. So I could change the runlevel to 3. Which worked only for the setup usb. The new kernel configuration went black again, this time without X...

/var/log/messages:
Code:
[    0.000000] Console: colour dummy device 80x25
[    0.000000] console [tty0] enabled
...
[    0.389454] efifb: probing for efifb
[    0.397610] efifb: framebuffer at 0xe0000000, mapped to 0xffffc90009780000, using 16200k, total 65536k
[    0.397614] efifb: mode is 1920x1080x32, linelength=7680, pages=1
[    0.397616] efifb: scrolling: redraw
[    0.397619] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[    0.403992] Console: switching to colour frame buffer device 240x67
[    0.409856] fb0: EFI VGA frame buffer device
This seems to show me the console text during the boot process, small letters....

continuing:
Code:
[    4.134164] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing generic driver
[    4.135943] Console: switching to colour dummy device 80x25
[    4.225918] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    4.225921] [drm] Driver supports precise vblank timestamp query.
[    4.225966] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    4.272584] fbcon: inteldrmfb (fb0) is primary device

....
[    5.732026] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[    6.258481] Console: switching to colour frame buffer device 240x67
[    6.266437] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    6.266476] i915 0000:00:02.0: registered panic notifier
[    6.276051] acpi device:28: registered as cooling_device5
[    6.280574] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    6.280646] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input10
[    6.280748] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
This seems to be the stuff I cannot see.... and I don't know what of this is relevant.

I don't know how to move on from here. Way out of my depth

Thank you for any pointers in the right direction!
 
Old 08-08-2013, 04:22 PM   #2
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,239

Rep: Reputation: 1041Reputation: 1041Reputation: 1041Reputation: 1041Reputation: 1041Reputation: 1041Reputation: 1041Reputation: 1041
Two things you could try:
(1) append "nomodeset" (without the quotes) to your command line at boot time. This should prevent loading a framebuffer driver so handover won't occur and at least at run level 3 you shouldn't have a black screen. if that works you could set "vga = normal" (again, without the quotes) in /etc/lilo.conf.
(2) If that prevents X to start, fall back to a VESA X driver.
For that, just do this:
Code:
mv /etc/X11/xorg.conf-vesa /etc/X11/xorg.conf
Of course these suggestions are only temporary workarounds.

Last edited by Didier Spaier; 08-08-2013 at 04:24 PM.
 
Old 08-08-2013, 04:51 PM   #3
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 867

Rep: Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749
64-bit or 32-bit?
 
1 members found this post helpful.
Old 08-08-2013, 09:41 PM   #4
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,188
Blog Entries: 15

Rep: Reputation: 826Reputation: 826Reputation: 826Reputation: 826Reputation: 826Reputation: 826Reputation: 826
Also, to supplement what Patrick asked, but which config file did you load with the kernel make config utility?

The config-3.10.1 should work for the majority of the 3.10.x series of kernels, but you should always double check the configuration for errors and warnings before proceeding to compile.
 
Old 08-09-2013, 02:46 AM   #5
fsauer
Member
 
Registered: Jul 2012
Posts: 38

Original Poster
Rep: Reputation: Disabled
Thank you all for your comments.

First: forgotten data: 64bit, huge kernel

in my elilo.conf I got
Code:
append="add_efi_map i915.i915_enable_rc6=1 pcie_aspm=force drm.blankoffdelay=1 i915.semaphores=1"
from the archlinux wiki, if I remember correctly.

Adding nomodeset or leaving all of them away allows a visible console, which is seen in messages:
Code:
colour dummy device 80x25
but no X, also when leaving the original line away, starting with nomodeset only. elilo chokes on vga=normal

Thank you for any further pointers!
And have a nice day
Franz


Here is my Xorg.0.log, I think it contains most info:
Code:
X.Org X Server 1.13.4
Release Date: 2013-04-17
[     9.659] X Protocol Version 11, Revision 0
[     9.659] Build Operating System: Slackware 14.1 Slackware Linux Project
[     9.659] Current Operating System: Linux franzlaptop 3.10.5 #2 SMP Sun Aug 4 15:38:19 CDT 2013 x86_64
[     9.659] Kernel command line: BOOT_IMAGE=dev000:\EFI\BOOT\vmlinuz-huge-3.10.5 root=/dev/sda2  nomodeset add_efi_mmap i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 ro
[     9.659] Build Date: 18 April 2013  01:47:25AM
[     9.659]  
[     9.659] Current version of pixman: 0.30.0
[     9.659] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[     9.659] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     9.659] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Aug  9 09:20:47 2013
[     9.662] (==) Using config directory: "/etc/X11/xorg.conf.d"
[     9.662] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     9.664] (==) No Layout section.  Using the first Screen section.
[     9.664] (==) No screen section available. Using defaults.
[     9.664] (**) |-->Screen "Default Screen Section" (0)
[     9.664] (**) |   |-->Monitor "<default monitor>"
[     9.664] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[     9.664] (==) Automatically adding devices
[     9.664] (==) Automatically enabling devices
[     9.664] (==) Automatically adding GPU devices
[     9.664] (WW) The directory "/usr/share/fonts/local" does not exist.
[     9.664] 	Entry deleted from font path.
[     9.664] (WW) The directory "/usr/share/fonts/CID" does not exist.
[     9.664] 	Entry deleted from font path.
[     9.666] (==) FontPath set to:
	/usr/share/fonts/TTF,
	/usr/share/fonts/OTF,
	/usr/share/fonts/Type1,
	/usr/share/fonts/misc,
	/usr/share/fonts/75dpi/:unscaled,
	/usr/share/fonts/100dpi/:unscaled,
	/usr/share/fonts/75dpi,
	/usr/share/fonts/100dpi,
	/usr/share/fonts/cyrillic
[     9.666] (==) ModulePath set to "/usr/lib64/xorg/modules"
[     9.666] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[     9.666] (II) Loader magic: 0x7f5540
[     9.666] (II) Module ABI versions:
[     9.666] 	X.Org ANSI C Emulation: 0.4
[     9.666] 	X.Org Video Driver: 13.1
[     9.666] 	X.Org XInput driver : 18.0
[     9.666] 	X.Org Server Extension : 7.0
[     9.667] (--) PCI:*(0:0:2:0) 8086:0166:1043:1517 rev 9, Mem @ 0xf7800000/4194304, 0xe0000000/268435456, I/O @ 0x0000f000/64
[     9.667] (II) Open ACPI successful (/var/run/acpid.socket)
[     9.669] Initializing built-in extension Generic Event Extension
[     9.669] Initializing built-in extension SHAPE
[     9.669] Initializing built-in extension MIT-SHM
[     9.669] Initializing built-in extension XInputExtension
[     9.669] Initializing built-in extension XTEST
[     9.669] Initializing built-in extension BIG-REQUESTS
[     9.669] Initializing built-in extension SYNC
[     9.669] Initializing built-in extension XKEYBOARD
[     9.669] Initializing built-in extension XC-MISC
[     9.669] Initializing built-in extension XINERAMA
[     9.669] Initializing built-in extension XFIXES
[     9.669] Initializing built-in extension RENDER
[     9.669] Initializing built-in extension RANDR
[     9.669] Initializing built-in extension COMPOSITE
[     9.669] Initializing built-in extension DAMAGE
[     9.669] Initializing built-in extension MIT-SCREEN-SAVER
[     9.669] Initializing built-in extension DOUBLE-BUFFER
[     9.669] Initializing built-in extension RECORD
[     9.669] Initializing built-in extension DPMS
[     9.669] Initializing built-in extension X-Resource
[     9.669] Initializing built-in extension XVideo
[     9.669] Initializing built-in extension XVideo-MotionCompensation
[     9.669] Initializing built-in extension XFree86-VidModeExtension
[     9.669] Initializing built-in extension XFree86-DGA
[     9.669] Initializing built-in extension XFree86-DRI
[     9.669] Initializing built-in extension DRI2
[     9.669] (II) LoadModule: "glx"
[     9.722] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[     9.752] (II) Module glx: vendor="X.Org Foundation"
[     9.752] 	compiled for 1.13.4, module version = 1.0.0
[     9.752] 	ABI class: X.Org Server Extension, version 7.0
[     9.752] (==) AIGLX enabled
[     9.761] Loading extension GLX
[     9.761] (==) Matched intel as autoconfigured driver 0
[     9.761] (==) Matched vesa as autoconfigured driver 1
[     9.761] (==) Matched modesetting as autoconfigured driver 2
[     9.761] (==) Matched fbdev as autoconfigured driver 3
[     9.761] (==) Assigned the driver to the xf86ConfigLayout
[     9.761] (II) LoadModule: "intel"
[     9.761] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[     9.822] (II) Module intel: vendor="X.Org Foundation"
[     9.822] 	compiled for 1.13.4, module version = 2.21.13
[     9.822] 	Module class: X.Org Video Driver
[     9.822] 	ABI class: X.Org Video Driver, version 13.1
[     9.822] (II) LoadModule: "vesa"
[     9.822] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[     9.841] (II) Module vesa: vendor="X.Org Foundation"
[     9.841] 	compiled for 1.13.4, module version = 2.3.2
[     9.841] 	Module class: X.Org Video Driver
[     9.841] 	ABI class: X.Org Video Driver, version 13.1
[     9.841] (II) LoadModule: "modesetting"
[     9.841] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[     9.861] (II) Module modesetting: vendor="X.Org Foundation"
[     9.861] 	compiled for 1.13.4, module version = 0.8.0
[     9.861] 	Module class: X.Org Video Driver
[     9.861] 	ABI class: X.Org Video Driver, version 13.1
[     9.861] (II) LoadModule: "fbdev"
[     9.922] (WW) Warning, couldn't open module fbdev
[     9.922] (II) UnloadModule: "fbdev"
[     9.922] (II) Unloading fbdev
[     9.922] (EE) Failed to load module "fbdev" (module does not exist, 0)
[     9.922] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
	i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
	E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
	965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
	4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
	Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
	Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
	Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
	Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
	Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
	Ivybridge Server (GT2), HD Graphics, HD Graphics 4600,
	Haswell Desktop (GT3), HD Graphics, HD Graphics 4600,
	Haswell Mobile (GT3), HD Graphics, HD Graphics P4600/P4700,
	Haswell Server (GT3), Haswell (GT1), Haswell (GT2), Haswell (GT3),
	HD Graphics, Haswell (GT2), Haswell (GT3), Haswell SDV Desktop (GT1),
	Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT3),
	Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
	Haswell SDV Mobile (GT3), Haswell SDV Server (GT1),
	Haswell SDV Server (GT2), Haswell SDV Server (GT3),
	Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
	Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
	Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
	Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4400,
	HD Graphics 5000, Haswell ULT Server (GT1), Haswell ULT Server (GT2),
	Iris(TM) Graphics 5100, Haswell ULT (GT1), Haswell ULT (GT2),
	Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4200,
	Iris(TM) Graphics 5100, Haswell CRW Desktop (GT1), HD Graphics 4600,
	Iris(TM) Pro Graphics 5200, Haswell CRW Mobile (GT1),
	HD Graphics 4600, Iris(TM) Pro Graphics 5200,
	Haswell CRW Server (GT1), Haswell CRW Server (GT2),
	Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
	Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
	Iris(TM) Pro Graphics 5200, ValleyView PO board
[     9.923] (II) VESA: driver for VESA chipsets: vesa
[     9.923] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     9.923] (++) using VT number 7

[     9.934] (WW) Falling back to old probe method for modesetting
[     9.934] (EE) open /dev/dri/card0: No such file or directory
[     9.934] (II) Loading sub module "vbe"
[     9.934] (II) LoadModule: "vbe"
[     9.934] (II) Loading /usr/lib64/xorg/modules/libvbe.so
[     9.941] (II) Module vbe: vendor="X.Org Foundation"
[     9.941] 	compiled for 1.13.4, module version = 1.1.0
[     9.941] 	ABI class: X.Org Video Driver, version 13.1
[     9.941] (II) Loading sub module "int10"
[     9.941] (II) LoadModule: "int10"
[     9.941] (II) Loading /usr/lib64/xorg/modules/libint10.so
[     9.942] (II) Module int10: vendor="X.Org Foundation"
[     9.942] 	compiled for 1.13.4, module version = 1.0.0
[     9.942] 	ABI class: X.Org Video Driver, version 13.1
[     9.942] (II) VESA(0): initializing int10
[     9.943] (EE) VESA(0): V_BIOS address 0x43420 out of range
[     9.943] (II) UnloadModule: "vesa"
[     9.943] (II) UnloadSubModule: "int10"
[     9.943] (II) Unloading int10
[     9.943] (II) UnloadSubModule: "vbe"
[     9.943] (II) Unloading vbe
[     9.943] (EE) Screen(s) found, but none have a usable configuration.
[     9.943] 
Fatal server error:
[     9.943] no screens found
[     9.943] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[     9.943] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[     9.943] (EE) 
[     9.955] Server terminated with error (1). Closing log file.
 
Old 08-09-2013, 06:08 AM   #6
dunric
Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 450

Rep: Reputation: 56
First would suggest to (temporarily) remove all settings concerning the dreaded i915 module from kernel params as there were many changes in last releases. Guess you didn't forget to rerun lilo after a kernel update
 
Old 08-09-2013, 08:30 AM   #7
fsauer
Member
 
Registered: Jul 2012
Posts: 38

Original Poster
Rep: Reputation: Disabled
Hmmmm, with or without the i915-related options, the kernel option "nomodeset" creates a console, X does not come up (no screens), and without nomodeset the console is black also. Various logs as seen above.


From inspecting /var/log/messages, the nomodeset option comes up with the dummy console. The efifb creates the unreadable console (I suppose).

Thank you!
Franz


PS. elilo does not have to be rerun. Only elilo.conf has to contain the correct kernel information.
 
Old 08-09-2013, 03:19 PM   #8
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 867

Rep: Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749Reputation: 1749
I wonder if removing CONFIG_EFI_FB from the kernel configuration would help? To be honest, I'm not sure under what circumstances (if any) that is actually needed. I'm still experimenting with UEFI through emulation here, but even when I do get UEFI hardware I'll have limited configurations to be able to test with. Anyone know how important having the EFI FB enabled actually is?
 
Old 08-09-2013, 04:03 PM   #9
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,840

Rep: Reputation: 846Reputation: 846Reputation: 846Reputation: 846Reputation: 846Reputation: 846Reputation: 846
IIRC VirtualBox in EFI-mode needs CONFIG_FB_EFI=y or you boot to a black screen. I found this comment that seems to suggest it (rwebber is commenting back when 13.37 was the latest stable, which did not have CONFIG_FB_EFI on):

Quote:
Originally Posted by rwebber View Post
It seems that an EFI system does not have normal VGA, or text mode or VESA framebuffer support, but requires the new EFI frame buffer support. It's even worse on VirtualBox because its video mode is not supported by Linux until you load the guest additions from a virtual CD. I suppose that someone with a real EFI system with a real video card that is supported in the kernel might have an easier time of it, though your screen may be black until the kernel finished loading.
 
Old 08-10-2013, 04:23 AM   #10
fsauer
Member
 
Registered: Jul 2012
Posts: 38

Original Poster
Rep: Reputation: Disabled
Let me give some additional information. I seem to have given a wrong pointer to the efifb. This provides the working console. I did a thorough comparison between the black screen and the nomodeset version of /var/log/messages. A diff of video related stuff plus some log lines present in both versions will hopefully clear that up.

Code:
< kernel: [] Linux version 3.10.5 (root@hive64) (gcc version 4.8.1 (GCC) ) #2 SMP Sun Aug 4 15:38:19 Ckernel: [] Command line: BOOT_IMAGE=dev000:\EFI\BOOT\vmlinuz-huge-3.10.5 root=/dev/sda2  add_efi_mem
< kernel: [] e820: BIOS-provided physical RAM map:
---
> kernel: [] Linux version 3.10.5 (root@hive64) (gcc version 4.8.1 (GCC) ) #2 SMP Sun Aug 4 15:38:19 Ckernel: [] Command line: BOOT_IMAGE=dev000:\EFI\BOOT\vmlinuz-huge-3.10.5 root=/dev/sda2  nomodeset akernel: [] e820: BIOS-provided physical RAM map:

< kernel: [] Kernel command line: BOOT_IMAGE=dev000:\EFI\BOOT\vmlinuz-huge-3.10.5 root=/dev/sda2  add_
kernel: [] PCIe ASPM is forcibly enabled
---
> kernel: [] Kernel command line: BOOT_IMAGE=dev000:\EFI\BOOT\vmlinuz-huge-3.10.5 root=/dev/sda2  nomo
kernel: [] PCIe ASPM is forcibly enabled



************************************
in both versions fail and nomodeset:

kernel: [] Console: colour dummy device 80x25
kernel: [] console [tty0] enabled

kernel: [] efifb: probing for efifb
kernel: [] efifb: framebuffer at 0xe0000000, mapped to 0xffffc90009780000, using 16200k, total 65536kernel: [] efifb: mode is 1920x1080x32, linelength=7680, pages=1
kernel: [] efifb: scrolling: redraw
kernel: [] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
kernel: [] Console: switching to colour frame buffer device 240x67
kernel: [] fb0: EFI VGA frame buffer device
kernel: [] GHES: HEST is not enabled!

***********************************



< kernel: [] [drm] Memory usable by graphics device = 2048M
< kernel: [] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing generic driver
< kernel: [] Console: switching to colour dummy device 80x25
< kernel: [] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
< kernel: [] [drm] Driver supports precise vblank timestamp query.
< kernel: [] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=iokernel: [] fbcon: inteldrmfb (fb0) is primary device

< kernel: [] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
< kernel: [] Console: switching to colour frame buffer device 240x67
< kernel: [] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
< kernel: [] i915 0000:00:02.0: registered panic notifier
< kernel: [] acpi device:28: registered as cooling_device5
< kernel: [] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
< kernel: [] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input10
< kernel: [] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0


< kernel: [] [drm] GMBUS [i915 gmbus dpd] timed out, falling back to bit banging on pin 6
< kernel: [] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5
< kernel: [] [drm] GMBUS [i915 gmbus panel] timed out, falling back to bit banging on pin 3
I hope someone will see this who can make sense of it....

Thank you!

Franz
 
Old 08-14-2013, 09:14 AM   #11
fsauer
Member
 
Registered: Jul 2012
Posts: 38

Original Poster
Rep: Reputation: Disabled
Seems to be an upstream bug, also observed in arch and fedora....

eg: https://bbs.archlinux.org/viewtopic.php?id=167314

Will have to roll back kernel...

Thank you all!
 
Old 08-15-2013, 01:48 AM   #12
Kallaste
Member
 
Registered: Nov 2011
Distribution: Slackware
Posts: 344

Rep: Reputation: 84
Did the old kernel work? If all else fails, you could always disable your efi, unless of course you need it for something else. I have a Zenbook myself, and I set it in Legacy BIOS mode and have none of these complications. It's running 3.10.5 right now with no issues.

Incidentally, you do not need the i915_enable_rc6 kernel parameter anymore. That option is now enabled by default.
 
Old 08-15-2013, 02:18 AM   #13
fsauer
Member
 
Registered: Jul 2012
Posts: 38

Original Poster
Rep: Reputation: Disabled
Thank you for asking, BN. Went back to 3.9.10 and it works nicely. Just used the -huge- config from 3.10.5

I haven't checked the details. I think there is some tweaking possible with newer kernels. While reading i saw some drivers to replace the usual generic ones. But I'm not sure if they apply to my machine ....

I think I'm quite happy with the efi stuff. After getting used to it, it is working nicely. Actually, I don't think it is connected to the present troubles. (efifb worked all the time)

I'll keep you updated if something new comes up...

Good luck!

Franz
 
Old 09-10-2013, 04:19 AM   #14
fsauer
Member
 
Registered: Jul 2012
Posts: 38

Original Poster
Rep: Reputation: Disabled
Still black screen on asus zenbook - current, kernel 3.10.11

Hi all! Just an update to the thread http://www.linuxquestions.org/questi...en-4175472685/

Installing the new upgrade to kernel 3.10.11 still left me with a black screen. 3.9.10 works.
System is a ux31a, i7, 15", ivy bridge

After the kernel switches to the intel driver the screen goes black. backlight seems to work. I am able to log in blind, and get the dmesg added below, and then reboot

Does someone have an idea who i could contact upstream?

Thanks and good luck
Franz


dmesg output
 
Old 09-10-2013, 06:44 AM   #15
jostber
Member
 
Registered: Jul 2001
Location: Skien, Norway
Distribution: Slackware 14.0 64-bit
Posts: 228

Rep: Reputation: 41
Could you see if this could give a clue?

http://lkml.org/lkml/2013/2/20/183
 
  


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


Similar Threads
Thread Thread Starter Forum Replies Last Post
After kernel upgrade I experience black screen when I logout mlpa Slackware 11 05-29-2013 01:34 PM
[SOLVED] X broken after latest x86_64 -current upgrade the_penguinator Slackware 3 02-24-2013 05:45 PM
[SOLVED] wicd broken after latest -current upgrade the_penguinator Slackware 2 06-29-2012 01:29 PM
[SOLVED] Xorg segfault after latest upgrade -current yenn Slackware 14 05-14-2012 05:41 PM
HP nx9105 With Latest Nvidia = Black Screen c3nturion Linux - Laptop and Netbook 6 02-03-2005 02:06 PM


All times are GMT -5. The time now is 12:55 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