Framebuffer, i915, and Slackware current and Asus eeepc
Got an Asus eeepc 900a. Runs Intel 915 graphics. Upgraded to slackware current last week. X would not start. Based on info here, I reverted back to earlier libdrm and xf86-video-intel. That got it working again.
Updated Slackware current again today. I think I got a new kernel. Now, halfway through boot time, the screen goes blank, then comes back and the font is tiny. Gone into framebuffer mode. If I start X, it just freezes. Nothing but a reboot will get out of it. I have vga=normal in lilo.conf, but I read that this is no longer used. I can find no way to turn off framebuffer mode. From other threads here, I have tried append="i915.modeset=1" in lilo.conf. Has no effect. I could revert Slackware to 13.0 from current, and that would make the eeepc useful again. Is there anything else I should try? |
i915.modeset=1 *enables* kernel modesetting (ie. the high resolution framebuffer). You could use the 'nomodeset' kernel option to disable KMS. Having said that, the Xorg intel driver on -current will not work if KMS is disabled, from what I've read.
Adam |
i915.modeset=1 *enables* kernel modesetting (ie. the high resolution framebuffer). You could use the 'nomodeset' kernel option to disable KMS. Having said that, the Xorg intel driver on -current will not work if KMS is disabled, from what I've read.
Adam |
Quote:
|
Quote:
A look in /var/log/Xorg.0.log shows it getting ready to "Setting up VESA Mode 0x115 (800x600) and then kablooie, that's the end. Xorg.0.log shows "VESA VBA OEM: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS". Does this still come under Intel 915 Graphics? Near the start of Xorg.0.log, I see this: (EE) module ABI major version (5) doesn't match the server's version (6) (II) UnloadModule: "intel" (II) Unloading /usr/lib/xorg/modules/drivers/intel_drv.so (EE) Failed to load module "intel" (module requirement mismatch, 0) (II) LoadModule: "vesa" Is this significant? |
Sounds like you are mixing and matching Xserver and X driver packages of different versions.
Adam |
The only other option I can think to try - following the theory that kms is now enabled by default - is to eliminate my first bullet (rc.local). So basically you have no "modeset" mumbo-jumbo anywhere - not in rc.local and not in lilo.conf and also you have no vga= line in lilo.conf either.
|
Oh - another question: Are you using your own xorg.conf? If so, try without it.
|
Quote:
I will try your other suggestions tomorrow when I have access to the machine again, and I'll report back. I'll also check the versions of everything and make sure I have no mismatches. Thanks for all the help guys. |
Quote:
I have no vga= line in lilo.conf. I have no append with modeset in lilo.conf. I have no modprobe and modeset in rc.local. I downgraded libdrm and xf86-video-intel packages (previously mucked with to get it work after last upgrade), and forced an upgrade so I have current versions of both. It now works. X starts and my netbook is useful again. Thanks for the help. I sure learned a lot of stuff from this process. I have one more question relating to my reading in the forums. If someone says "blacklist nouveau" and I think this relates to modules, what is this blacklist thing, and how do you do it? I don't need to to do anything more on my netbook, I just want to know what this means. |
Blacklist means /etc/slackpkg/blacklist. It's where you put packages you don't want slackpkg to ever upgrade or to ever install-new. For instance, I did not install the kde packages on my 900a originally, so I put /slackware/kde in my blacklist file so that slackpkg doesn't keep trying to install them.
|
I think in this case blacklist actually means adding a module name to /etc/modprobe.d/blacklist.conf to keep it from getting loaded when the kernel boots.
|
Quote:
|
If on booting Slackware 13.1 screen font becoms tiny next can be tried:
In lilo.conf delete any 'vga = XXX'. Then:
{{{ append=" vt.default_utf8=1 " image = /boot/vmlinuz-huge-smp-2.6.33.4-smp root = /dev/sdaP label = aP # As it comes with KMS enabled read-only image = /boot/vmlinuz-huge-smp-2.6.33.4-smp root = /dev/sdaP label = aP_640x480 # LatArCyrHeb-16.psfu.gz COLUMNS=80 LINES=30 read-only addappend=" video=VGA-1:640x480 " # Seems KMS is off image = /boot/vmlinuz-huge-smp-2.6.33.4-smp root = /dev/sdaP label = aP_800x600 # LatArCyrHeb-19.psfu.gz COLUMNS=100 LINES=31 read-only addappend=" video=VGA-1:800x600 " # Seems KMS is off }}} For VGA-DIGIT check /sys/class/drm/card0/card0-XXX-DIGIT and try 'video=XXX-DIGIT:...' or dig dmesg ( LatArCyrHeb is for ru_RU.UTF-8 ) helpfull: http://wiki.archlinux.org/index.php/KMS http://bbs.archlinux.org/viewtopic.php?pid=755266 http://unixforum.org/index.php?showtopic=99485 https://wiki.ubuntu.com/X/KernelModeSetting http://www.insidesocal.com/click/201...rnel-mode.html http://www.linuxquestions.org/questi...urrent-736017/ With thanks Vit |
Some of the other responses may be giving better advice, but here is my two cents:
In your lilo.conf: 1: hash out any line that says "vga=xxx", your penguin should re-appear. If it worked, you would want an append that might included "video=intelfb ...", but current kernels are not up to this yet. Intel graphics automatically detect and use the highest resolution available for their framebuffers. 2: to enlarge the text on your boot console, add an append that forces one of the built-in kernel fonts. eg: append="fbcon=font:SUN12x22" Your choices will be whatever was built with your kernel, check "/proc/config.gz" In your xorg.conf: In the Graphics Device Section: Change the "Driver" line to ' Driver "Intel" ' Remove reference to specific Intel drivers. eg:change ' Driver "Intel..." ' to ' Driver "Intel" ' If that doesn't work, revert to the vesa framebuffer drivers: ' Driver "vesa" ' You will probably not notice any lack of performance with vesa framebuffers in X overall, but may have trouble with DVDs due to the lack of acceleration. |
All times are GMT -5. The time now is 03:08 PM. |