Intel 82865g 2.6.33-smp kernel xorgserver 1.8, 2.11 driver version problem
Hi all! Im having a battle for quite some time now with lastest intel driver now and wondering if someone has solution.
Ive checked : http://intellinuxgraphics.org/2010Q1.html and i decided to have exact same version of everything listed in there installed on the system. I have few questions since i manually builded xorg-server 1.8 im wondering what packages are dependent for x11 to be upgraded so everything run smoothly for xserver 1.8. are those xf86-input* and xf86-video* the only one or there are other packages that i have to get rebuilded? the second question: im wondering if im the only one for that having a problem of that lastest driver dosent work for me, for the purpose i rebuilded the driver and libdrm 2.4.20 with kms enabled once i installed xorg-xserver 1.8.0 heres log problem: Code:
214.704] (II) LoadModule: "intel" thanks |
That chipset works fine with the x11 packages in the stock -current tree.
|
ive removed xorg-server 1.8, and then ive tried, again slackware current: executing commands in this order :
Code:
slackpkg update heres log: Code:
(II) Module dri2: vendor="X.Org Foundation" for me everything worked smoothly when in current stock was xorg-server 1.7.3 and ive builded from source libdrm and xf86-video-intel 2.10 kms enabled, after that i have this problem, im wondering what this error cause: Code:
/usr/lib/xorg/modules/intel_drv.so: undefined symbol: resVgaShared also what packages depends on xorg-server behaviour? |
I'm not sure where that symbol is coming from, but it means that some of your packages are not in sync with what's in our tree (or perhaps you have other stuff in /usr/local that's being seen).
|
how can i locate where the symbol is coming from ?
ive done also Code:
slackpkg clean-system its really interesting. ive also downloaded stock current tree and done Code:
upgradepkg --reinstall */*.txz |
if you don't have anything you need in /usr/local, you can try "resetting" it: maybe, as robby hinted above, something you build yourself has ended up installing there and it's loaded instead of the stuff in /usr.
so you can temporary move away the folders, create some pristine ones and see if it helps Code:
cd /usr/local but, in general and in particular with a complex package like X, it's very difficult to repair a situation where you don't know where your "make install"s have copied stuff... |
Quote:
we will see what kind of idea rworkman has im wondering how i can trace from where undefined symbol is coming from? thanks guys for helping me out |
i don't know robby's idea, but if I were you I would do this (it's not a rude answer, just what I would do):
- backup personal data - reinstall pristine -current from iso - use packages/slackbuilds only that will fix your problem faster than losing time trying to fix the symbol thing ;) |
Quote:
and 2.11 was in /usr/lib/xorg/modules/drivers/intel_drv.so so i had just to remove intel_drv.so from /usr/lib/xorg/modules and problem solved :) im just wondering when you guys incorporate new xserver 1.8.0 version into stock-current tree is it really necessary to rebuild from scratch all x11 packages aswell? |
I think yes, but someone more into building X than me (and maybe involved in the slackware team, but maybe you are referring to robby) can answer surely better.
also, if you search in the forum, there are some old threads about X building. |
its pointed to everyone, surely would like to know rworkman and other opinion about it,(although my opinion is just like yours, but want to check to make sure :)) but im very glad that i got the solution to the problem :)
|
Possibly you could be having issues with something that will be fixed in 2.6.33.5:
Code:
------------------ |
Oh, I see that it's solved now :/
Re xorg-server-1.8.x, at least some of the video drivers will need a rebuild, and probably some of them won't build against it, and we'll have to work out the documentation side of "how do I do $x" with regards to setting keymaps using udev instead of hal, and while we're at it, we'll look into using udisks and upower for removable devices and power management, and then nothing will be left using hal, I don't think, but that will require testing, and if I'm right, we can remove hal, but then that will require lots of testing to make sure, so that's why we didn't shoot for the newer 1.8.x branch for 13.1. Long sentence, anyone? ;-) |
Quote:
Yes thats why i was thinking if everything has to be rebuilded. Everything else clear, although its a bit long sentence. |
All times are GMT -5. The time now is 11:02 PM. |