Re: [XFree86] Keyboard not working with latest CVS
On Thu, 2003-02-27 at 03:51, David Dawes wrote: It sounds like your Xlib has the wrong path for XKeysymDB. Did you install it in the same ProjectRoot as it was built for (lots of things can break if you don't)? I just did a make install, and there's a XKeysymDB under the ProjectRoot I built for. The original one is still in its old location, this is the one it's being read when X starts. strings .../lib/libX11.so | grep XKeysymDB [EMAIL PROTECTED]:~/cvs/X-install/lib strings libX11.so | grep XKeysymDB /home/garetxe/cvs/X-install/lib/X11/XKeysymDB [EMAIL PROTECTED]:~/cvs/X-install/lib ls -l $(strings libX11.so | grep XKeysymDB) -r--r--r--1 garetxe users8298 feb 26 12:29 /home/garetxe/cvs/X-install/lib/X11/XKeysymDB But it might be just that my system isn't properly configured and the wrong libX11 (the one under /usr/X11R6/lib/) is loaded instead for some reason. Looking to the relevant code in libX11 I agree it should work. Honestly, I don't think you should waste any more time on this unless someone else with a sane install of everything else sees the same, it might just as well be a bug somewhere else (in the computer chair interface probably :-)), and my system works just fine anyway. Thanks for your patience, Iaki PD: Not everything is complaints btw :-), the new X rocks, finally XVideo for my card and things such as the translucent cursors and easy font management are very nice, I had been wanting to have them for a long time. Thanks a lot for the superb work. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Keyboard not working with latest CVS
Hi again, I just upgraded to CVS and my keyboard stopped working. I dug a little deeper, now I have the keyboard (mostly) working. I didn't realize at first, but the Xserver was printing to the console this (*), which I include at the end of the email. I edited lib/X11/xkb/compat/xfree86 and lib/X11/xkb/symbols/pc/pc appropiately and the error messages are gone now. There's still a bug somewhere though. The only problem remaining is that the Alt Gr characters in the spanish keyboard don't work. For those who don't know, there are some keys with three characters on them (2 for example), and the third character is usually accessed by pressing a key labelled 'Alt Gr' and hitting the key. But doing that gives: KeyPress event, serial 20, synthetic NO, window 0x3c1, root 0x3f, subw 0x0, time 2314601, (37,72), root:(41,648), state 0x0, keycode 113 (keysym 0xffea, Alt_R), same_screen YES, XLookupString gives 0 bytes: KeyPress event, serial 25, synthetic NO, window 0x3c1, root 0x3f, subw 0x0, time 2314848, (37,72), root:(41,648), state 0x8, keycode 11 (keysym 0x32, 2), same_screen YES, XLookupString gives 1 bytes: 2 KeyRelease event, serial 25, synthetic NO, window 0x3c1, root 0x3f, subw 0x0, time 2314910, (37,72), root:(41,648), state 0x8, keycode 11 (keysym 0x32, 2), same_screen YES, XLookupString gives 1 bytes: 2 KeyRelease event, serial 25, synthetic NO, window 0x3c1, root 0x3f, subw 0x0, time 2315210, (37,72), root:(41,648), state 0x8, keycode 113 (keysym 0xffea, Alt_R), same_screen YES, XLookupString gives 0 bytes: Any ideas? TIA, Iaki (*) expected keysym, got XF86_Switch_VT_1: line 8 of xfree86 expected keysym, got XF86_Switch_VT_2: line 11 of xfree86 expected keysym, got XF86_Switch_VT_3: line 14 of xfree86 expected keysym, got XF86_Switch_VT_4: line 17 of xfree86 expected keysym, got XF86_Switch_VT_5: line 20 of xfree86 expected keysym, got XF86_Switch_VT_6: line 23 of xfree86 expected keysym, got XF86_Switch_VT_7: line 26 of xfree86 expected keysym, got XF86_Switch_VT_8: line 29 of xfree86 expected keysym, got XF86_Switch_VT_9: line 32 of xfree86 expected keysym, got XF86_Switch_VT_10: line 35 of xfree86 expected keysym, got XF86_Switch_VT_11: line 38 of xfree86 expected keysym, got XF86_Switch_VT_12: line 41 of xfree86 expected keysym, got XF86_Ungrab: line 45 of xfree86 expected keysym, got XF86_ClearGrab: line 48 of xfree86 expected keysym, got XF86_Next_VMode: line 51 of xfree86 expected keysym, got XF86_Prev_VMode: line 54 of xfree86 The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields expected keysym, got XF86_Switch_VT_1: line 51 of pc/pc expected keysym, got XF86_Switch_VT_2: line 55 of pc/pc expected keysym, got XF86_Switch_VT_3: line 59 of pc/pc expected keysym, got XF86_Switch_VT_4: line 63 of pc/pc expected keysym, got XF86_Switch_VT_5: line 67 of pc/pc expected keysym, got XF86_Switch_VT_6: line 71 of pc/pc expected keysym,
Re: [XFree86] Keyboard not working with latest CVS
On Wed, 2003-02-26 at 19:42, David Dawes wrote: I just upgraded to CVS and my keyboard stopped working. I dug a little deeper, now I have the keyboard (mostly) working. I didn't realize at first, but the Xserver was printing to the console this (*), which I include at the end of the email. I edited lib/X11/xkb/compat/xfree86 and lib/X11/xkb/symbols/pc/pc appropiately and the error messages are gone now. There's still a bug somewhere though. Those problems are caused by your installation not being complete. The defintions for the unrecognised keysyms are in lib/X11/XKeysymDB, so you need to update that file. It's as complete as make install makes it, just under a different ProjectRoot. Dunno why is it still looking under /usr/X11 in this case, but linking /usr/X11R6/lib/X11 to the new version does fix the problems. Thanks for the advice, Iaki ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Keyboard not working with latest CVS
Hi list, I just upgraded to CVS and my keyboard stopped working. If I start the server with -xkb (or the XkbDisable option in XF86Config) things appear to work just fine. Attached goes my XF86Config, X log (when things don't work) and the host.def file used for compiling. I installed X under a different prefix as you can see from host.def, but that used to work. Any clues? Iaki Section ServerFlags #Option XkbDisable true EndSection Section ServerLayout Identifier XFree86 Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer # For two mouses # InputDeviceMouse1 AlwaysCore InputDeviceKeyboard0 CoreKeyboard EndSection Section Files # RgbPath /usr/X11R6/lib/X11/rgb # ModulePath /usr/X11R6/lib/modules RgbPath /home/garetxe/cvs/X-install/lib/X11/rgb ModulePath /home/garetxe/cvs/X-install/lib/modules FontPath /usr/X11R6/lib/X11/fonts/misc:unscaled FontPath /usr/X11R6/lib/X11/fonts/local FontPath /usr/X11R6/lib/X11/fonts/75dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/100dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/Type1 FontPath /usr/X11R6/lib/X11/fonts/URW FontPath /usr/X11R6/lib/X11/fonts/Speedo FontPath /usr/X11R6/lib/X11/fonts/PEX FontPath /usr/X11R6/lib/X11/fonts/cyrillic:unscaled FontPath /usr/X11R6/lib/X11/fonts/latin2/misc:unscaled FontPath /usr/X11R6/lib/X11/fonts/latin2/75dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/latin2/100dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/latin2/Type1 FontPath /usr/X11R6/lib/X11/fonts/latin7/75dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/baekmuk:unscaled FontPath /usr/X11R6/lib/X11/fonts/japanese:unscaled FontPath /usr/X11R6/lib/X11/fonts/kwintv:unscaled FontPath /usr/X11R6/lib/X11/fonts/truetype FontPath /usr/X11R6/lib/X11/fonts/uni:unscaled FontPath /usr/X11R6/lib/X11/fonts/CID FontPath /usr/X11R6/lib/X11/fonts/ucs/misc:unscaled FontPath /usr/X11R6/lib/X11/fonts/ucs/75dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/ucs/100dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/hellas/misc:unscaled FontPath /usr/X11R6/lib/X11/fonts/hellas/75dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/hellas/100dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/hellas/Type1 FontPath /usr/X11R6/lib/X11/fonts/misc/sgi:unscaled FontPath /usr/X11R6/lib/X11/fonts/xtest FontPath /usr/X11R6/lib/X11/fonts/freefont FontPath /usr/X11R6/lib/X11/fonts/sharefont FontPath /usr/X11R6/lib/X11/fonts/tolkien EndSection Section Module Load record Load extmod Load dbe Load dri Load glx Load xie Load xtrap Load type1 Load speedo EndSection Section InputDevice Identifier Keyboard0 Driver keyboard # Driver kbd Option Protocol Standard Option XkbKeyCodes xfree86 Option XkbLayout es Option XkbModel pc104 Option XkbRules xfree86 # Option CustomKeycodes on EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol PS/2 Option Device /dev/mouse Option Emulate3Buttons on EndSection #Section InputDevice #Identifier Mouse1 #Driver mouse #Option Device /dev/input/mice #Option Protocol IMPS/2 #Option Emulate3Buttons off #Option ZAxisMapping 4 5 #EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model # HorizSync 31.5-48.5 # VertRefresh 55-90 # ModeLine 640x480 25.175 640 664 760 800 480 491 493 525 # Modeline 800x600 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync 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 ShowCache # [bool] #Option Dac6Bit # [bool] #Option DRI # [bool] #Option NoDDC # [bool] #Option XvMCSurfaces # i Option Stretch True Identifier Card0 Driver i810 VendorName Intel BoardName i830M BusID PCI:0:2:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 16 SubSection Display Depth 1 EndSubSection
[XFree86] i830m and stretching
Hi Xperts, I wrote a few days ago about a problem with i830m and mode switching. No solution was given, but Hans Öfverbeck said something interesting about stretching. The relevant mail is labelled: Mode incorrectly set with i830m in a toshiba 3000 x4 laptop Further investigations show that in the CVS version of i830_driver.c there's a Stretch option, although it appears to be not implemented (just glanzing through the code, I cannot run X cvs now). There's a 'Center' option too, i guess they will set the appropiate registers in the i830 (btw, are there any public specs for this card? I could only find for i810 in the intel site). I tried setting/unsetting the bits 31 and 29 of the 0x60018 register with pcitweak [pcitweak -w 00:02:00 0x60018 number, i hope this makes some sense] to no avail. The program succeeds but the register doesn't change. I would appreciate some help with this. I don't mind working on it but I need an starting point: - Is anyone working on the implementation of Stretch and Center? Could they be related to my problem? (i will be glad to provide more info about my problem as needed) - Are there any publicly available specs for the i830m? - Can I use pcitweak to change registers of the graphics card instead of modifying the xf86 module? (less painful for q'n'd testing) TIA, Iñaki ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Mode incorrectly set with i830m in a toshiba 3000 x4laptop
Hi, I'm trying to get XFree 4.2.1 working in a toshiba 3000 x4 laptop. I guess that you are trying to use the built in lcd. Yep. There's no fun in buying a laptop and needing to carry a CRT around with it, is it? ;-) What happens if you start X in 800x600 ? Same error, the image is streched. I boot in graphics mode from lilo (vga=788 - 800x600, what suse selected by default, this works until X changes the mode, it won't be restored correctly later on). Or if you use 1024x768 (vga=791) in console AND in X ? (Quake=slow) If I pass vga=791 to lilo i cannot see anything when i boot: the screen goes off, the system responds but i have to reboot in 800x600 to see anything. Looks like _something_ happened, though: when i restart and run X it usually shows in the bottom part of the screen the contents of the video memory (until it gets overwritten with the X default background), and I can see there the console status of the last reboot, so apparently the framebuffer console knew it was in 1024x768. Dunno, perhaps someone finds it interesting. Thanks, Iñaki ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
