Hello... Praveen Kallakuri: [...] > i finally > removed everything xfree-, gnome-, etc and started afresh. How did you do that ? dselect or manually ? > i had the /etc/X11 dir almost empty. i know a lot of that is linked to > in /usr/X11R6/libs but not sure how much. what i want to say is, i did > not empty the latter. but i purged all x-related packages from dselect > in order to start off afresh. to continue, i still have the same problem > i had before. > anwyays now, i have gnome2.2 (the woody backport created by James > Strandboge). i have xfree86 4.2.1 backport for woody, again from > people.debian.org/~blade/woody/i386. > 3. gnome2 starts, i see gnome2 try to start but it immediately aborts My experience with upgrading to gnome2 was, that some configuration was incompatible, and i should better have purged old gnome before .... but i am not sure to what extension (all ~/.gnome-* also ?). since dpkg won't remove non empty directories it's even better to remove user's ~/.gnome and his /tmp/orbit-xyz also. afaikc there was something like recommendet on their homepage....
Praveen Kallakuri: > well i guess that was something i dint try after installing the new X. > but i tried it now, and i get the same behavior. note that i got twm to > work. so i think its a gnome specific problem, but not having anything > to do with userlevel or /etc/ config files. just a hunch. i am > providing links to some files someone may find useful. > thanks > http://csce.unl.edu/~pkallaku/pub/general/XF86Config-4 > http://csce.unl.edu/~pkallaku/pub/general/XFree86.0.log > http://csce.unl.edu/~pkallaku/pub/general/startx.err Since X is starting up (so you can see gnome starting) it's probably ok. So some details i wonder about, wouldn't help you, unfortunateley. Anyway. Mixed of /etc/X11/XF86Config-4 and the X-Log: SubSection "Display" Depth 16 Modes "1152x864" "1024x768" "800x600" "640x480" EndSubSection <-> (--) VESA(0): Virtual size is 1024x768 (pitch 1024) (**) VESA(0): Default mode "1024x768" I'm used to have the first mode by default... maybe the ati-RamSize or your screen doesn't support this resolution ? Section "Device" Identifier "ATI Technologies, Inc. Radeon Mobility M6 [LY]" Driver "vesa" BusID "PCI:1:0:0" VideoRam 8 Option "UseFBDev" "true" EndSection <-> (WW) VESA(0): Option "UseFBDev" is not used Vesa is a framebuffer driver ? So why. (man XF86Config fbdev) (WW) Open APM failed (/dev/apm_bios) (No such file or directory) .... Do you use acpi instead ? Section "InputDevice" Identifier "Generic Mouse" Driver "mouse" Option "SendCoreEvents" "true" Option "Device" "/dev/input/mice" Option "Protocol" "ImPS/2" Perhaps you better make mice a link to psaux...or just it to /dev/psaux here .... but, ok, it's log-osmetic ;-) afaicr the ati raedon is supported from a 2.4.x kernel module, but that's not the mobility then.... here's a link, but maybe no more actual. http://www.ati.com/na/pages/products/pc/radeon32/index.html -- micha.
