| View previous topic :: View next topic |
| Author |
Message |
Maedhros
Bodhisattva
Joined: 14 Apr 2004
Posts: 5511
Location: Durham, UK
|
|
| Back to top |
|
 |
Finswimmer
Bodhisattva
Joined: 02 Sep 2004
Posts: 5467
Location: Langen (Hessen), Germany
|
 Posted: Sat Mar 04, 2006 2:00 pm Post subject: xf86-video-nv-1.0.1.5: undefined symbol: xf86CreateCursorInf |
 |
|
Hi!
Everytime I run xorg-7 I get this with my (old) GeForce 2 Ti:
xf86-video-nv-1.0.1.5: undefined symbol: xf86CreateCursorInfoRec
For more infos: https://bugs.gentoo.org/show_bug.cgi?id=116702
But they couldn't help me either.
Maybe you can?
Thank you
Tobi
_________________
Bitte auf Rechtschreibung, korrekte Formatierung und Höflichkeit achten!
Danke |
|
| Back to top |
|
|
data
n00b
Joined: 15 Jan 2004
Posts: 17
Location: France
|
| Posted: Sat Mar 04, 2006 3:31 pm Post subject: xkeyboard-config fails |
|
|
Previously I mentioned my trouble with xkeyboard-config not working and xorg falling back to the console layout. Well here's an error message that I hadn't seen before (it wasn't in the logs, just on the console). I get the same thing if I try to setxkbmap plus the "Error loading new keyboard description" message.
| Code: | syntax error: line 1 of pc
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error: Error interpreting include file "pc"
> Exiting
> Abandoning symbols file "default"
Errors from xkbcomp are not fatal to the X server |
I can't see any obvious problems with files named pc in /etc/X11/xkb. Maybe I should file a bugreport.
Anyone else had this problem ?
EDIT: problem solved by manually deleting /usr/X11R6/lib/X11/xkb and /usr/share/X11/xkb and then reemerging xkeyboard-config.
However I'd still like to know why my dvorak deadkeys aren't working 
EDIT2: deadkeys work after adding include "level3(ralt_switch)" to the dvorak section of /usr/share/X11/xkb/symbols/us  .
Last edited by data on Sat Mar 04, 2006 6:56 pm; edited 2 times in total |
|
| Back to top |
|
|
compbatant
n00b
Joined: 03 Oct 2005
Posts: 21
|
| Posted: Sat Mar 04, 2006 4:40 pm Post subject: |
|
|
nvidia drivers 1.0.8178
i try this configuration in xorg.conf:
Section "Monitor"
Identifier "mag"
Option "dpms"
EndSection
and this:
Section "Monitor"
Identifier "mag"
HorizSync 30-83
VertRefresh 56-75
EndSection
and this:
Section "Monitor"
Identifier "mag"
Modeline "1280x1024" 109.62 1280 1336 1472 1720 1024 1024 1026 1062
EndSection
and i've got this during startx:
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(--) NVIDIA(0): Linear framebuffer at 0xD0000000
(--) NVIDIA(0): MMIO registers at 0xE4000000
(II) NVIDIA(0): NVIDIA GPU detected as: GeForce4 MX 440
(--) NVIDIA(0): VideoBIOS: 04.17.00.45.91
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(II) NVIDIA(0): Detected AGP rate: 4X
(--) NVIDIA(0): VideoRAM: 65536 kBytes
(II) NVIDIA(0): Connected display device(s): CRT-0
(--) NVIDIA(0): CRT-0: maximum pixel clock: 350 MHz
(II) NVIDIA(0): Frequency information for CRT-0:
(II) NVIDIA(0): HorizSync : 4294967.000-0.000 kHz
(II) NVIDIA(0): VertRefresh : 4294967296.000-0.000 Hz
(II) NVIDIA(0): (HorizSync from EDID)
(II) NVIDIA(0): (VertRefresh from EDID)
(II) NVIDIA(0): mag: Using hsync range of 4294967.00-0.00 kHz
(II) NVIDIA(0): mag: Using vrefresh range of 4294967296.00-0.00 Hz
(II) NVIDIA(0): Clock range: 12.00 to 350.00 MHz
(II) NVIDIA(0): Not using mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x350" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x175" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x400" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "720x400" (hsync out of range)
(II) NVIDIA(0): Not using default mode "360x200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x240" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x240" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x240" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x240" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "400x300" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "400x300" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "400x300" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "400x300" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "400x300" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1152x864" (hsync out of range)
(II) NVIDIA(0): Not using default mode "576x432" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x960" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x960" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (hsync out of range)
(II) NVIDIA(0): Not using default mode "896x672" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (hsync out of range)
(II) NVIDIA(0): Not using default mode "896x672" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (hsync out of range)
(II) NVIDIA(0): Not using default mode "928x696" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (hsync out of range)
(II) NVIDIA(0): Not using default mode "928x696" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "832x624" (hsync out of range)
(II) NVIDIA(0): Not using default mode "416x312" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1152x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "576x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "700x525" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "700x525" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(WW) NVIDIA(0): Mode pool is empty
(EE) NVIDIA(0): No modes remaining for display device CRT-0
(EE) NVIDIA(0): *** Aborting ***
(EE) NVIDIA(0): Failed to unmap registers.
(EE) NVIDIA(0): Failed to unmap registers.
(EE) NVIDIA(0): Failed to free registers.
(II) UnloadModule: "nvidia"
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found |
|
| Back to top |
|
|
Finswimmer
Bodhisattva
Joined: 02 Sep 2004
Posts: 5467
Location: Langen (Hessen), Germany
|
| Posted: Sat Mar 04, 2006 6:24 pm Post subject: |
|
|
Try X -configure
Tobi
_________________
Bitte auf Rechtschreibung, korrekte Formatierung und Höflichkeit achten!
Danke |
|
| Back to top |
|
|
compbatant
n00b
Joined: 03 Oct 2005
Posts: 21
|
|
| Back to top |
|
|
compbatant
n00b
Joined: 03 Oct 2005
Posts: 21
|
| Posted: Sat Mar 04, 2006 8:09 pm Post subject: |
|
|
i added this:
Option "DPI" "85 x 86"
and now it is ok :] |
|
| Back to top |
|
|
MorLipf
Apprentice
Joined: 09 Nov 2004
Posts: 226
Location: Solingen, Germany
|
| Posted: Sun Mar 05, 2006 9:37 am Post subject: |
|
|
A second time:
I unmerged the old Xorg 6.8.2, removed all old config files and installed Xorg 7.0-r1 with evdev, keyboard, mouse and the ati-module (not fglrx).
Then I created a config with Xorgconfig with the ati-module, a display resolution of 1280x1024 etc.
My problem is that every time I start X with startx or kdm the resolution is only 640x480 and I can't switch it.
The Xorg logfiles don't show errors and my config seems to be fine. |
|
| Back to top |
|
|
RaZoR1394
Guru
Joined: 09 Jan 2005
Posts: 356
|
| Posted: Sun Mar 05, 2006 10:24 am Post subject: |
|
|
| MorLipf wrote: | A second time:
I unmerged the old Xorg 6.8.2, removed all old config files and installed Xorg 7.0-r1 with evdev, keyboard, mouse and the ati-module (not fglrx).
Then I created a config with Xorgconfig with the ati-module, a display resolution of 1280x1024 etc.
My problem is that every time I start X with startx or kdm the resolution is only 640x480 and I can't switch it.
The Xorg logfiles don't show errors and my config seems to be fine. |
I had the same problem. Try this under Section "Device":
If you have tft/lcd screen.
| Quote: |
Option "MonitorLayout" "TMDS, NONE"
|
If you have a crt screen.
| Quote: |
Option "MonitorLayout" "CRT, NONE"
|
_________________
http://en.wikipedia.org/wiki/Cell_(microprocessor) |
|
| Back to top |
|
|
MorLipf
Apprentice
Joined: 09 Nov 2004
Posts: 226
Location: Solingen, Germany
|
| Posted: Sun Mar 05, 2006 10:46 am Post subject: |
|
|
| Thx, it works now! |
|
| Back to top |
|
|
nesl247
Veteran
Joined: 15 Jun 2004
Posts: 1614
Location: Florida
|
| Posted: Sun Mar 05, 2006 2:47 pm Post subject: |
|
|
| Has anyone else experienced hardlocks upon exiting X? It doesn't matter if I am root or a user. |
|
| Back to top |
|
|
Pithlit
l33t
Joined: 27 Dec 2003
Posts: 887
Location: fuhen
|
| Posted: Sun Mar 05, 2006 11:52 pm Post subject: |
|
|
Just switched to modular... Is there some fix for the synaptics driver? My cursor behaves erratically (jumps all over the screen), touchpad lost its scroll area and the fourway button (acer laptops) does nothing (well... behaves as the left/right buttons instead of doing its job and scrolling horizontaly/verticaly).
*edit* just noticed (wtf?!?):
| Code: | | [ebuild R ] x11-base/xorg-x11-7.0-r1 USE="-3dfx" INPUT_DEVICES="evdev keyboard mouse synaptics wacom -acecad -aiptek -calcomp -citron -digitaledge -dmc -dynapro -elo2300 -elographics -fpit -hyperpen -jamstudio -joystick -magellan -magictouch -microtouch -mutouch -palmax -penmount -spaceorb -summa -tek4957 -ur98 -vmmouse -void" VIDEO_CARDS="fbdev sis vesa -apm -ark -ati -chips -cirrus -cyrix -dummy -fglrx -glint -i128 -i740 -i810 -imstt -mga -neomagic -newport -nsc -nv -nvidia -rendition -s3 -s3virge -savage -siliconmotion -sisusb -tdfx -tga -trident -tseng -v4l -vga -via -vmware -voodoo" 0 kB |
| Xorg.0.log wrote: | (EE) No Input driver matching `synaptics'
(EE) No Input driver matching `wacom'
(EE) No Input driver matching `wacom'
(EE) No Input driver matching `wacom'
|
*edit2* ...O...K... I guess I should reemerge synaptics && linuxwacom ... should've thought of that first 
*edit3* Figures... that fixed it.
_________________
If someone solves a problem for you say thanks... and put [SOLVED] in the title! |
|
| Back to top |
|
|
Zr40
Tux's lil' helper
Joined: 19 Sep 2002
Posts: 76
|
| Posted: Mon Mar 06, 2006 10:24 am Post subject: |
|
|
I'm having trouble getting the dvorak keyboard layout to work in X. whatever I specify in xorg.conf, it only uses qwerty.
| Code: | Section "InputDevice"
Identifier "Keyboard1"
Driver "evdev"
Option "Device" "/dev/input/event0"
Option "AutoRepeat" "500 30"
Option "XkbRules" "xorg"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
Option "XkbVariant" "dvorak"
EndSection |
When I try 'setxkbmap -layout us -variant dvorak', I get the following:
| Code: | Couldn't interpret _XKB_RULES_NAMES property
Use defaults: rules - 'xorg' model - 'pc101' layout - 'us'
*** glibc detected *** free(): invalid pointer: 0xb7ff5ca0 ***
Aborted |
|
|
| Back to top |
|
|
data
n00b
Joined: 15 Jan 2004
Posts: 17
Location: France
|
| Posted: Mon Mar 06, 2006 4:50 pm Post subject: |
|
|
| Zr40 wrote: | | I'm having trouble getting the dvorak keyboard layout to work in X. whatever I specify in xorg.conf, it only uses qwerty. |
I had a similar problem but no crash. Just out of interest, you could try to "loadkeys dvorak" before starting X. You may find that X is using your console layout.
Anyway the following solved my problem.
| Code: | emerge -av unmerge xkbdata xkeyboard-config
rm -rf /usr/X11R6/lib/X11/xkb /usr/share/X11/xkb
emerge -av xkeyboard-config |
|
|
| Back to top |
|
|
agaffney
Retired Dev
Joined: 28 May 2003
Posts: 104
Location: St. Charles, MO
|
| Posted: Mon Mar 06, 2006 5:42 pm Post subject: composite extension |
|
|
I can't seem to get the composite extension to work right with modular X. I've got the following in my xorg.conf:
| Code: | Section "Extensions"
Option "Composite" "Enable"
Option "RENDER" "Enable"
EndSection |
I see the following in my Xorg.0.log:
| Code: | | (II) Initializing built-in extension COMPOSITE |
and yet when I run xcompmgr, I get:
| Code: | agaffney@kirara ~ $ xcompmgr -c
No composite extension |
Running xdpyinfo does not show the composite extension loaded:
| Code: | name of display: :0.0
version number: 11.0
vendor string: The X.Org Foundation
vendor release number: 70000000
X.Org version: 7.0.0
maximum request size: 16777212 bytes
motion buffer size: 256
bitmap unit, bit order, padding: 32, LSBFirst, 32
image byte order: LSBFirst
number of supported pixmap formats: 7
supported pixmap formats:
depth 1, bits_per_pixel 1, scanline_pad 32
depth 4, bits_per_pixel 8, scanline_pad 32
depth 8, bits_per_pixel 8, scanline_pad 32
depth 15, bits_per_pixel 16, scanline_pad 32
depth 16, bits_per_pixel 16, scanline_pad 32
depth 24, bits_per_pixel 32, scanline_pad 32
depth 32, bits_per_pixel 32, scanline_pad 32
keycode range: minimum 8, maximum 255
focus: window 0xa00006, revert to PointerRoot
number of extensions: 31
BIG-REQUESTS
DAMAGE
DEC-XTRAP
DOUBLE-BUFFER
DPMS
Extended-Visual-Information
GLX
LBX
MIT-SCREEN-SAVER
MIT-SHM
MIT-SUNDRY-NONSTANDARD
RANDR
RECORD
RENDER
SECURITY
SGI-GLX
SHAPE
SYNC
TOG-CUP
X-Resource
XC-APPGROUP
XC-MISC
XFIXES
XFree86-Bigfont
XFree86-DGA
XFree86-Misc
XFree86-VidModeExtension
XInputExtension
XKEYBOARD
XTEST
XVideo
default screen number: 0
number of screens: 1
screen #0:
print screen: no
dimensions: 1280x1024 pixels (382x302 millimeters)
resolution: 85x86 dots per inch
depths (7): 24, 1, 4, 8, 15, 16, 32
root window id: 0x44
depth of root window: 24 planes
number of colormaps: minimum 1, maximum 1
default colormap: 0x20
default number of colormap cells: 256
preallocated pixels: black 0, white 16777215
options: backing-store NO, save-unders NO
largest cursor: 64x64
current input event mask: 0xda001f
KeyPressMask KeyReleaseMask ButtonPressMask
ButtonReleaseMask EnterWindowMask StructureNotifyMask
SubstructureNotifyMask SubstructureRedirectMask PropertyChangeMask
ColormapChangeMask
number of visuals: 8
default visual id: 0x23
visual:
visual id: 0x23
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x24
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x25
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x26
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x27
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x28
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x29
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x2a
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
|
Anyone have any ideas? |
|
| Back to top |
|
|
Zr40
Tux's lil' helper
Joined: 19 Sep 2002
Posts: 76
|
| Posted: Mon Mar 06, 2006 10:33 pm Post subject: |
|
|
| data wrote: | | Zr40 wrote: | | I'm having trouble getting the dvorak keyboard layout to work in X. whatever I specify in xorg.conf, it only uses qwerty. |
I had a similar problem but no crash. Just out of interest, you could try to "loadkeys dvorak" before starting X. You may find that X is using your console layout.
|
Actually, I've got the dvorak console layout loaded at boot, in /etc/conf.d/keymaps.
| Quote: |
Anyway the following solved my problem.
| Code: | emerge -av unmerge xkbdata xkeyboard-config
rm -rf /usr/X11R6/lib/X11/xkb /usr/share/X11/xkb
emerge -av xkeyboard-config |
|
Doesn't solve the problem here 
Edit: Solved it! I was using evdev for keyboard input. Changing back to 'keyboard' applied the keymap  |
|
| Back to top |
|
|
Xake
Guru
Joined: 11 Feb 2004
Posts: 588
Location: Göteborg, the rainy part of scandinavia
|
| Posted: Tue Mar 07, 2006 11:42 am Post subject: |
|
|
| Zr40 wrote: | | Edit: Solved it! I was using evdev for keyboard input. Changing back to 'keyboard' applied the keymap |
I can hardly wait for an updated package of evdev since it is rewritten in cvs to support keyboards and layouts better. |
|
| Back to top |
|
|
nesl247
Veteran
Joined: 15 Jun 2004
Posts: 1614
Location: Florida
|
| Posted: Tue Mar 07, 2006 11:52 am Post subject: |
|
|
| agaffney: can you please post your xorg.conf? Also before you do, please try without: Option "RENDER" "Enable" As that is no longer needed (since way back) |
|
| Back to top |
|
|
agaffney
Retired Dev
Joined: 28 May 2003
Posts: 104
Location: St. Charles, MO
|
| Posted: Tue Mar 07, 2006 3:03 pm Post subject: |
|
|
Commenting out the RENDER line didn't have any effect. Here's my xorg.conf:
| Code: | Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/corefonts"
FontPath "/usr/share/fonts/freefont"
FontPath "/usr/share/fonts/sharefonts"
FontPath "/usr/share/fonts/terminus"
FontPath "/usr/share/fonts/ttf-bitstream-vera"
FontPath "/usr/share/fonts/unifont"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/artwiz"
EndSection
Section "Module"
Load "extmod"
Load "dri"
Load "dbe"
Load "record"
Load "xtrap"
Load "glx"
Load "type1"
Load "freetype"
EndSection
Section "Extensions"
Option "Composite" "Enable"
# Option "RENDER" "Enable"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
EndSection
Section "Monitor"
DisplaySize 380 300 # mm
Identifier "Monitor0"
VendorName "SAM"
ModelName "SyncMaster"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "ColorKey" # <i>
#Option "CacheLines" # <i>
#Option "Dac6Bit" # [<bool>]
#Option "DRI" # [<bool>]
#Option "NoDDC" # [<bool>]
#Option "ShowCache" # [<bool>]
#Option "XvMCSurfaces" # <i>
#Option "PageFlip" # [<bool>]
Identifier "Card0"
Driver "i810"
VendorName "Intel Corp."
BoardName "82865G Integrated Graphics Device"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024" "1024x768"
# Modes "1024x768"
EndSubSection
EndSection
|
|
|
| Back to top |
|
|
firephoto
Veteran
Joined: 29 Oct 2003
Posts: 1612
Location: +48° 5' 23.40", -119° 48' 30.00"
|
| Posted: Tue Mar 07, 2006 5:41 pm Post subject: |
|
|
| Xake wrote: | | Zr40 wrote: | | Edit: Solved it! I was using evdev for keyboard input. Changing back to 'keyboard' applied the keymap |
I can hardly wait for an updated package of evdev since it is rewritten in cvs to support keyboards and layouts better. |
Hopefully it works good, it's pretty much useless unless maybe the model keyboard the dev who created it works. Nothing I've tried works as expected, there's always a few keys doing double duty at random functions. (arrow keys tied to print screen randomly is one)
_________________
#gentoo-kde on freenode |
|
| Back to top |
|
|
nesl247
Veteran
Joined: 15 Jun 2004
Posts: 1614
Location: Florida
|
| Posted: Tue Mar 07, 2006 7:59 pm Post subject: |
|
|
| agaffney: I have no idea then. Have you read the wiki entry for Xorg and Transparency carefully? It might contain a fix. |
|
| Back to top |
|
|
Xake
Guru
Joined: 11 Feb 2004
Posts: 588
Location: Göteborg, the rainy part of scandinavia
|
| Posted: Tue Mar 07, 2006 9:43 pm Post subject: |
|
|
| firephoto wrote: | | Hopefully it works good, it's pretty much useless unless maybe the model keyboard the dev who created it works. Nothing I've tried works as expected, there's always a few keys doing double duty at random functions. (arrow keys tied to print screen randomly is one) |
Have you tried the version in CVS or? I have not had the time fully to compile and play.....
EDIT::
Doh, I have time now. going to try it.... |
|
| Back to top |
|
|
Kaste
Guru
Joined: 21 Dec 2005
Posts: 546
Location: /home Sweet /home
|
| Posted: Sun Mar 12, 2006 8:08 pm Post subject: |
|
|
I did a reinstall because i borked my system with an improper compiler transition :/.
Now i can't get my xorg 7 to run anymore. What happens is it compiles fine and is finished with everything, but when i type startx it won't find it. At first i thought i had some path issues but a find / -iname startx reveals that it is not present on my system at all.
How is that possible?
BTW that exact same thing happend to a friend of mine as well. |
|
| Back to top |
|
|
Gremo
Guru
Joined: 27 Feb 2006
Posts: 450
|
| Posted: Mon Mar 13, 2006 2:22 am Post subject: |
|
|
hi,
i emerged just few minutes ago modular X.
i'm getting some warnings, i cannot understand:
1)rgbpath not found
and:
| Code: |
(WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found
|
any help? |
|
| Back to top |
|
|
me22
n00b
Joined: 30 Jun 2002
Posts: 45
Location: Canada
|
| Posted: Mon Mar 13, 2006 4:31 am Post subject: |
|
|
I just finished installing xorg 7, and it's working fine.
The only annoyance I've found is that the "Terminal" font has changed. I was using 6.8's version for all sorts of things, and the version in 7 is about twice as tall as all my other fonts in size 10, and is much thicker than the old one.
Is it possible to get the old version of the terminal font back?
( I've tried searching, but "terminal font" give tons of irrelevant results. ) |
|
| Back to top |
|
|
|
Desktop Environments
