| View previous topic :: View next topic |
| Author |
Message |
SysGhost
n00b
Joined: 24 Apr 2007
Posts: 48
Location: Stockholm
|
 Posted: Mon Sep 08, 2008 7:26 am Post subject: Kde won't work when I use vesa driver in xorg.conf. |
 |
|
Hey.
Just like the subject says:
Kde won't work when I use vesa driver in xorg.conf.
But if I use a native driver such as nv (or something else depending on the hardware) kde works just fine.
You see, the trick is, this installation is going to move between different setups of hardware, and so far I managed to make most working.
I want the vesa driver because it can be used with different graphic cards and with that I don't have to reconfigure xorg.conf each time I put the movable harddisk in a different machine.
Everything works fine so far, but not kde, which refuses to start when I try the vesa driver.
What could possibly be wrong? I'm out of options...
kded seems to be the problem:
--cut-start-----------------------------------------------------------
user@host ~$ /usr/kde/3.5/bin/startkde
startkde: Starting up...
/usr/bin/iceauth: creating new authority file /home/mno/.ICEauthority
DCOP aborting call from 'anonymous-7981' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
startkde: Shutting down...
klauncher: Exiting on signal 1
startkde: Running shutdown scripts...
startkde: Done.
user@host ~$
user@host ~$ /usr/kde/3.5/bin/kded
FATAL: DCOP communication problem!
Avbruten (SIGABRT)
user@host ~$
--cut-end------------------------------------------------------------- |
|
| Back to top |
|
 |
muhsinzubeir
l33t
Joined: 29 Sep 2007
Posts: 948
Location: /home/muhsin
|
| Posted: Mon Sep 08, 2008 8:20 am Post subject: |
|
|
I think you can comment VIDEO_CARDS on make.conf...and recompile X and you can move around btwn machines with the expense of building all drivers.
P:S
Notice commenting VIDEO_CARDS in make.conf means building you X with all drivers, some of them are masked...you will need to unmask them.I think its a great solution then using vesa only...but if you wanna be that economic by building only vesa, you can still specify vesa or only those few video cards that you have...en you should be able to move freely btwn machines
Notice:
Any change on make.conf takes effect after you have recompiled!
cheers
_________________
~x86
p5k-se
Intel Core 2 Duo
Nvidia GT200
http://www.zanbytes.com |
|
| Back to top |
|
|
SysGhost
n00b
Joined: 24 Apr 2007
Posts: 48
Location: Stockholm
|
| Posted: Mon Sep 08, 2008 10:06 am Post subject: |
|
|
| muhsinzubeir wrote: | | I think you can comment VIDEO_CARDS on make.conf...and recompile X and you can move around btwn machines with the expense of building all drivers. |
I thought about that, yet I still wonder if there is any way to make xorg to autodetect and load the correct driver without the need to define the particular driver in xorg.conf each time I change machine.
| muhsinzubeir wrote: |
P:S
Notice commenting VIDEO_CARDS in make.conf means building you X with all drivers, some of them are masked...you will need to unmask them.I think its a great solution then using vesa only...but if you wanna be that economic by building only vesa, you can still specify vesa or only those few video cards that you have...en you should be able to move freely btwn machines
Notice:
Any change on make.conf takes effect after you have recompiled!
|
That problem is already solved, able to use the vesa and most window managers such as windowmaker for example, works great with both the native drivers awell as the vesa one.
My problem is: KDE refuse to start if I use the vesa driver. However, kde works just fine if used with a native driver. see previously posted errors.
"FATAL: DCOP communication problem!" error from kded ONLY occurs when I use the vesa driver.
That is strange in my opinion. KDE shouldn't care about what driver is being used, or am I wrong? |
|
| Back to top |
|
|
muhsinzubeir
l33t
Joined: 29 Sep 2007
Posts: 948
Location: /home/muhsin
|
| Posted: Mon Sep 08, 2008 10:17 am Post subject: |
|
|
u are right kde shouldnt care bout driver layer...im curious how do u switch btwn one driver to another one?recompile X?
_________________
~x86
p5k-se
Intel Core 2 Duo
Nvidia GT200
http://www.zanbytes.com |
|
| Back to top |
|
|
SysGhost
n00b
Joined: 24 Apr 2007
Posts: 48
Location: Stockholm
|
| Posted: Tue Sep 09, 2008 5:14 am Post subject: Simple... |
|
|
Thats simple, I just change the Driver option under the Device section in xorg.xonf:
Driver "vesa"
is changed to
Driver "nv"
...and back, in the case I use an nVidia card
I have already compiled most of the drivers avaliable for X by including most of them in the VIDEO_CARDS variable in make.conf (not those masked thou, I don't need them... yet)
I hoped I could use vesa one only not needing to switch between them all |
|
| Back to top |
|
|
muhsinzubeir
l33t
Joined: 29 Sep 2007
Posts: 948
Location: /home/muhsin
|
| Posted: Tue Sep 09, 2008 7:52 am Post subject: |
|
|
understood, but changing by editing that way i doubt if its the nicest way {im just doubting if the names of the drivers would be the same and other parameters when you move to another machine}...
what about auto-generating xorg.conf every time you plug it to another machine,would that be an option?...its probably 2 commands you can just create script to simplify the process...
goodluck...
_________________
~x86
p5k-se
Intel Core 2 Duo
Nvidia GT200
http://www.zanbytes.com |
|
| Back to top |
|
|
d2_racing
Bodhisattva
Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada
|
| Posted: Tue Sep 09, 2008 11:48 am Post subject: |
|
|
Hi, can you post your emerge --info
Also, when you change something inside the video_cards in /etc/make.conf, you need at least to run this command :
| Code: |
# emerge -uDNv world
|
|
|
| Back to top |
|
|
SysGhost
n00b
Joined: 24 Apr 2007
Posts: 48
Location: Stockholm
|
| Posted: Tue Sep 09, 2008 7:56 pm Post subject: |
|
|
...well... let's not slip away from the original topic:
KDE wont start when using vesa drivers.
I want to use vesa just for that particular reason NOT to reconfigure the machine each time
btw... doing an "emerge -uDNv world " each time I put the harddrive in a different machine seems a bit... *erh*... drastic?
PS: (edit) This is a total new installation with all settings made already, when I emerged kde-meta everything went just fine, but refuse to start, I got a tip from someone that vesa driver from xorg wont work with kde, I thought it was just silly, but I tested and... heck... he was right, so far...
Will give the "emerge --info" output as soon as I can get to it...
Last edited by SysGhost on Tue Sep 09, 2008 8:06 pm; edited 1 time in total |
|
| Back to top |
|
|
szczerb
Veteran
Joined: 24 Feb 2007
Posts: 1709
Location: Poland => Lodz
|
| Posted: Tue Sep 09, 2008 8:01 pm Post subject: |
|
|
| You just have to do it once so xorg-server builds all the drivers. Then you only have to change the configuration in xorg.conf |
|
| Back to top |
|
|
SysGhost
n00b
Joined: 24 Apr 2007
Posts: 48
Location: Stockholm
|
| Posted: Tue Sep 09, 2008 8:09 pm Post subject: |
|
|
| szczerb wrote: | | You just have to do it once so xorg-server builds all the drivers. Then you only have to change the configuration in xorg.conf |
That, I already have done, redone and retried, even with unmerge at some point, no success. Also tried re-emerge kdebase and the whole kde-install (tedious work to unmerge everything, but done aswell) |
|
| Back to top |
|
|
cabbagewalker
n00b
Joined: 09 Feb 2004
Posts: 61
Location: Nottingham, UK
|
| Posted: Tue Sep 09, 2008 10:27 pm Post subject: |
|
|
No real answer to your problem I know but it works on this computer using KDE 4.1.1 (from Gentoo's overlay) and xorg-x11-7.2. Normally I use the nvidia driver, but a quick edit in xorg.conf showed that it works with vesa.
D |
|
| Back to top |
|
|
SysGhost
n00b
Joined: 24 Apr 2007
Posts: 48
Location: Stockholm
|
| Posted: Wed Sep 10, 2008 10:06 am Post subject: |
|
|
I find it kinda weird that kde (kded) wont start because of vesa, or something missing when I compiled x86-video-vesa.
Do I have to reemerge kdebase just because of reemerging x86-video-vesa ? ...wait... already tried that.
What could it be then, that causes kded having a "FATAL: DCOP communication problem! " with vesa driver.
Posting the info from "emerge --info" (I've put some extra newlines in to ease up reading it)
| Code: | Portage 2.1.4.4 (default/linux/x86/2008.0, gcc-4.1.2, glibc-2.6.1-r0, 2.6.25-gentoo-r7 i686)
=================================================================
System uname: 2.6.25-gentoo-r7 i686 Intel(R) Pentium(R) 4 CPU 1.70GHz
Timestamp of tree: Thu, 14 Aug 2008 01:45:03 +0000
ccache version 2.4 [enabled]
app-shells/bash: 3.2_p33
dev-java/java-config: 1.3.7, 2.1.6
dev-lang/python: 2.4.4-r13
dev-python/pycrypto: 2.0.1-r6
dev-util/ccache: 2.4-r7
sys-apps/baselayout: 1.12.11.1
sys-apps/sandbox: 1.2.18.1-r2
sys-devel/autoconf: 2.13, 2.61-r1
sys-devel/automake: 1.5, 1.7.9-r1, 1.9.6-r2, 1.10.1
sys-devel/binutils: 2.18-r1
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool: 1.5.24
virtual/os-headers: 2.6.23-r3
ACCEPT_KEYWORDS="x86"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=i686 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-O2 -march=i686 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache distlocks metadata-transfer sandbox sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="http://mirror.mdfnet.se/mirror/gentoo/ http://ftp.ds.karen.hj.se/gentoo/ http://ftp.ing.umu.se/linux/gentoo/"
LANG="sv_SE.UTF-8"
LDFLAGS="-Wl,-O1"
LINGUAS="sv_SE sv se en en_GB"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="7zip X accessibility acl alsa berkdb bzip2 cli cracklib crypt cups dbus dri fortran gcj gdbm gif gnustep gpm gtk hal iconv ipv6 isdnlog java jpeg kde midi mmx mp3 mudflap ncurses nls nptl nptlonly objc objc++ objc-gc opengl openmp pam pcre perl png pppd python qt qt3 readline reflection session spl ssl sysfs tcpd tiff truetype unicode x86 xinerama xorg xscreensaver xulrunner zlib"
ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci"
ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol"
APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias"
ELIBC="glibc"
INPUT_DEVICES="keyboard mouse"
KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text"
LINGUAS="sv_SE sv se en en_GB"
USERLAND="GNU"
VIDEO_CARDS="apm ark chips cirrus cyrix dummy epson fbdev fglrx glint i128 i740 i810 imstt mach64 mga neomagic nsc nv nvidia r128 radeon rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via vmware voodoo"
Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, MAKEOPTS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY |
|
|
| Back to top |
|
|
muhsinzubeir
l33t
Joined: 29 Sep 2007
Posts: 948
Location: /home/muhsin
|
| Posted: Wed Sep 10, 2008 10:20 am Post subject: |
|
|
dont forget vesa is a kind of light weight ....the best shot i can think of is auto-generating the xorg.conf everytime you move to another machine.This only 2 commands!
| Quote: | #!/bin/bash
Xorg -configure
cp /root/xorg.conf.new /etc/X11/xorg.conf |
_________________
~x86
p5k-se
Intel Core 2 Duo
Nvidia GT200
http://www.zanbytes.com |
|
| Back to top |
|
|
szczerb
Veteran
Joined: 24 Feb 2007
Posts: 1709
Location: Poland => Lodz
|
| Posted: Wed Sep 10, 2008 10:25 am Post subject: |
|
|
| How about going without an xorg.conf? |
|
| Back to top |
|
|
d2_racing
Bodhisattva
Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada
|
| Posted: Wed Sep 10, 2008 11:03 am Post subject: |
|
|
| In fact, since X.ORG 7.2 you don't need at all a /etc/X11/xorg.conf to have a working 2d environment. |
|
| Back to top |
|
|
SysGhost
n00b
Joined: 24 Apr 2007
Posts: 48
Location: Stockholm
|
| Posted: Wed Sep 10, 2008 12:08 pm Post subject: |
|
|
No xorg.conf seems to work, and having only a vesa driver installed (unmerged the others since it wanted to load nv or vga drivers before trying vesa)
Works so far, it fires up and I get a 640x480. but the problem is still there:
using vesa = kde fails to load
using nv = kde loads!
using vga = kde loads!
using svga = xorg fails. (seems svga driver aren't compartible with a geforce card)
And again: I want to use vesa only, nothing else, that way I dont need to change any configuration at all.
My temporary solution: using windowmaker, since that one works with vesa
Fluxbox also seems to have trouble with the vesa driver, but works fine with other drivers
So once again:
* I don't want to reconfigure the system each time I switch machine (I'm not the only one using this portable harddisc)
* I simply want to use VESA ONLY! (actually works, but KDE wont accept it)
* Resolution at 1024x768, so vga driver is out of the question, svga driver wont work at all.
So my question is, What possible reason makes KDE not working on a VESA driven screen? and what could I have forgot since it seems that KDE lost it rights to connect to the dcop server when using VESA? |
|
| Back to top |
|
|
widremann
Veteran
Joined: 14 Mar 2005
Posts: 1314
|
| Posted: Wed Sep 10, 2008 12:56 pm Post subject: |
|
|
| SysGhost wrote: | No xorg.conf seems to work, and having only a vesa driver installed (unmerged the others since it wanted to load nv or vga drivers before trying vesa)
Works so far, it fires up and I get a 640x480. but the problem is still there:
using vesa = kde fails to load
using nv = kde loads!
using vga = kde loads!
using svga = xorg fails. (seems svga driver aren't compartible with a geforce card)
And again: I want to use vesa only, nothing else, that way I dont need to change any configuration at all.
My temporary solution: using windowmaker, since that one works with vesa
Fluxbox also seems to have trouble with the vesa driver, but works fine with other drivers
So once again:
* I don't want to reconfigure the system each time I switch machine (I'm not the only one using this portable harddisc)
* I simply want to use VESA ONLY! (actually works, but KDE wont accept it)
* Resolution at 1024x768, so vga driver is out of the question, svga driver wont work at all.
So my question is, What possible reason makes KDE not working on a VESA driven screen? and what could I have forgot since it seems that KDE lost it rights to connect to the dcop server when using VESA? |
If you don't have an xorg.conf, then you don't need to reconfigure each time. Just don't use the xorg.conf and you are done. It will JUST WORK each time you go to a new machine. And do make sure to have your other drivers installed so X can use them when appropriate. |
|
| Back to top |
|
|
SysGhost
n00b
Joined: 24 Apr 2007
Posts: 48
Location: Stockholm
|
| Posted: Wed Sep 10, 2008 1:07 pm Post subject: |
|
|
Well... thanks for trying, but let's get this down to the problem I have:
Xorg and vesa IS working just fine, KDE refuse to use it thou.
I have a working configuration with VESA and at 1024x768-24@60Hz
IT WORKS!!!!
But try to understand my problem:
So far so good, X is workling, VESA is working, windowmaker works on it. That works!
not trying to use KDE:
startkde
Wont work!
Why? It refuses to work with a VESA driven screen.
If i use a native driver such as nv, ati, mach64 ... etc, kde works, so it has to be something with VESA and KDE.
and please, before answering: read previous posts! |
|
| Back to top |
|
|
SysGhost
n00b
Joined: 24 Apr 2007
Posts: 48
Location: Stockholm
|
| Posted: Wed Sep 10, 2008 1:10 pm Post subject: |
|
|
| ... have to add: some cards this installation is going to be used with, are so odd, they seems to ONLY work with vesa, they have no whatsoever drivers available with Xorg-server |
|
| Back to top |
|
|
|
Desktop Environments
