[SOLVED] What happened to Xorg in Slackware 13.0? (Intel chipset)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Could you try it with 2.6.29.6? One important issue with changing intel video driver is they require machine reboot. Killing and restarting X is not enough.
About 2.6.29.6, will do. Didn't realise I needed to reboot between trying the different intel video drivers. Will try that as well, thanks.
This is not Slackware to blame but developers of xorg and intel driver. I have very unstable X on my i810 intel video. Anyway latest intel driver seems to be best, grab it from here: http://advamacs.com/pub/xf86-video-i...9.0-i486-1.tgz
I'm not part of the X11 team or anything, but I have chased this dragon for a while on other issues.
As all of our hardware moves to dynamic detection and module or driver loading -- I plug a usb drive, the crank turns, the media gets mounted, the music plays -- X11 is running to catch-up on that approach. If you connect keyboards, mice, trackballs, tablets, displays and such, the hardware will mostly autodetect and modules load, but X11 does not absorb the details and integrate the parts.
The result is that the X-folks are busy making changes to how X11 gets its device and configuration details in the dynamic connection world. For a while, X11 vs. "your hardware" will be a bit dicey. I understand that for a while, you can always use xorg.conf to force things, but that you do not get one by default any longer. I'm not even sure what the dividing line is between the olde ways and the new ways as everything "depends" on so many other things.
ENCOURAGEMENT: As you discover things that work or work-around, please bring answers and solutions to LQ.
I'm so used to testing X servers by running the command 'X' that I never thought to actually launch with 'startx' until I had a working server. After reading through the posts again, and seeing agentdcooper mention a window manager, I realised perhaps things now depend on which WM you use, so I ran 'startx' and everything worked fine.
I now feel a complete idiot, and apologise for wasting everyone's time!
FYI, i solved my problem with intel graphics on slackware64 (kde freeze with custom kernel over stock 2.6.29.6) upgrading kernel to latests vanilla version with zen kernel patches (that include also some drm fixes - and selectable bfs/cfs schedulers). 2.6.32-rc5 and 2.6.32-rc5-zen1 patch - apply when in kernel sources with
FYI, i solved my problem with intel graphics on slackware64 (kde freeze with custom kernel over stock 2.6.29.6) upgrading kernel to latests vanilla version with zen kernel patches (that include also some drm fixes - and selectable bfs/cfs schedulers). 2.6.32-rc5 and 2.6.32-rc5-zen1 patch - apply when in kernel sources with
with this kernel stock intel drivers (2.8.0) works ok for me (without KMS).
that is EXCELLENT news! soo good, I gonna give this a shot = 2.6.32-rc5, and while I am at it I gonna give the zen patch a go... I never used a "zen" patch before, but it sounds intriguing ;;
Quote:
Zen Notes ... 2.6.32-rc5-zen1 "Quadrupulus Humulus Lupulus"
- Zen-Sched, compile-time selection CFS or latest BFS scheduler
* BFS is now the default scheduler via Kconfig - as of 10/5/2009
* If you encounter a BFS bug in this kernel, ONLY report it to zen developers please, as there is no official bfs 2.6.32 patch -- this one is zen-specific (to test bfs problems, compare it to 2.6.31-bfs)
- BFS 304
- Updates from linux-2.6.git
- BFQ is default i/o scheduler now, please test!
- tuxonice updated
- updated wireless-testing
- updated alsa
the brainfuck scheduler, eh??! hahah - curious how that works out
the difference in my case, I will be trying this on my slackware 13.0 x86 box (32bit)...
+++++++++++++++++++++++++++++++++++++++++
oh, bifferos - glad to hear u got it! wondering though, did u get it working with KDE4?? (if u ARE on a different window manager, would u mind giving it a try? sure u know this, but use xwmconfig to change window managers in slackware ) and another question, which version of intel drivers got things going for you? thanks!
Last edited by agentdcooper; 10-18-2009 at 12:32 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.