Re: G3 iBook LCD brightness in X under kernel 2.4.25 and 2.6.8
On Saturday 27 November 2004 2:02, Benjamin Herrenschmidt wrote: > On Fri, 2004-11-26 at 11:28 +0100, Christof Petig wrote: > > > I'm running pbbuttonsd 0.6.6-2 with gtkpbbuttons 0.6.4-3 (which are > > > tools that enable the LCD to be dimmed and brightened with keyboard > > > pressed). When I'm running the Debian kernel-image 2.4.25-8 and I press > > > the brightness up or down keys, I get the on-screen indication from > > > gtkpbbuttons and the LCD dims or brightens as expected in both X and on > > > the console. However, when I boot into kernel-image 2.6.8-6 or 2.6.9-1 > > > and press the brightness keys, I get the on-screen indication in X, but > > > the LCD doesn't change brightness. However, if I switch to a VT with a > > > console, the brightness changes to what I tried to change it to. Also, > > > pressing the brightness buttons works fine when I press them while in > > > the console. > > What machine model precisely ? If it's an iBook, only the very first one > had a mach64 based chip and indeed used atyfb-based brightness control, > that might have been broken... It's a first generation iBook SE (Special Edition). The SE means that it came with a 6GB HD, more RAM, and a slightly faster CPU (366MHz), but it does have a Mach64. > > > My video card is a Mach64, and I'm using the 'ati' driver for X. One > > > guess I have is that in 2.6, lots more things are built as kernel > > > modules. I'd like to try build any needed video stuff in, but I don't > > > know what it could be. Does anyone here have an idea what controls > > > screen brightness in X? > > Some earlier models have PMU-controlled brightness, independently on the > video card... So I don't think it's an "early model" because it came out later than the fruit-colored iBooks (it's grey and white, not -berry like the real first gen iBooks). > > Your mouse pointer might get some noisy spots on brightness change, ever > > noticed? I would blame the kernel first (since 2.4 works well). > > Ah ? Haven't noticed that ? what machine ? > > > > The reason this is important for me is that the LCD is not dimmed when > > > I close the lid for sleep, which kind of ruins the point of sleep. > > > > > > Does anyone have an idea of what else I need to do to get screen > > > dimming to work under X with Linux 2.6? > > You may be missing the atyfb kernel driver. So I've tried this using the stock Debian 2.6.8 and 2.6.9 PPC kernels with the same results. $ grep ATY /boot/config-2.6.9-powerpc CONFIG_FB_ATY128=y CONFIG_FB_ATY=y CONFIG_FB_ATY_CT=y CONFIG_FB_ATY_GX=y # CONFIG_FB_ATY_XL_INIT is not set It seems that the atyfb module is compiled in. Is there another way to check? Frank
Bug#283210: Jumping mouse in glx-mode
-BEGIN PGP SIGNED MESSAGE- Package: xlibmesa-glu Version: 4.3.0.dfsg.1-8 Severity: important Maybe this bug is upstream. But I did not find any information about this problem in the net. The problem is that in any application using glx-mode (and only in gls-mode) like tuxracer or unreal or other games the mouse is randomely jumping in random (short) timeintervals to a fix position on the screen. While in tuxracer this is just annoying in unreal for example it makes the game unplayable as you need the mouse to play. I have the problem now for long time and allways waiting if it will be fixed with update of X or kernel or so as I do not exactely know where the bug is located. It dosn't matter which kind of mouse using (usb, ps2, serial) and dosn't mather which graphics board (Matrox, nVidia, ATI Radeon) installed. I have no clue if I'm the only who have this problem. But it is reproducable on all computers I tested (with debian sarge and sid). To reproduce the bug, start tuxracer, move the mouse a bit and wait 10-20 seconds... Ah, yes, the seems only in the hardware glx mode, not when only software rendering is unsed. - -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (800, 'unstable'), (700, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.28 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE) Versions of packages xlibmesa-glu depends on: ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an ii libgcc1 1:3.4.3-1 GCC support library ii libstdc++51:3.3.5-2 The GNU Standard C++ Library v3 ii xlibmesa-gl [libgl1] 4.3.0.dfsg.1-8 Mesa 3D graphics library [XFree86] - -- no debconf information - -- Klaus Ethgenhttp://www.ethgen.de/ pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <[EMAIL PROTECTED]> Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iQEVAwUBQahIB5+OKpjRpO3lAQG/Sgf/Ro4eTA4TE1X2QhRmrIpI/ib6ioUwOtsR zkJd3N3CLTU7q+SrcI262lpq/Tt9jHf6pOKsoWvVH01kwLfbW5ZZPi7nl539Gpwl lhvIeiw+Ja1x4lcDmu0feN8o3QJwnGDHsMYpJeakit5HPG1+RcQc5zJJtV/Hu2vh SuLSYh3SXdRr+MthBSNDAe18b1LYxNSTN5nMYhuR17ReFh4Qp0HfGYvQQIoTzICp snxlePfiM9k4rWyFZv79MhopK4CC+/EOt4FvG16BHpe1qPLWxdTmHShDwT9y/n5+ zd8CXVBHPSG1gg+7hgzNrw1V533Nb4cxc+CgMRUbDegEymW284fEQw== =ZeQu -END PGP SIGNATURE-
Bug#280384: XFree not starting any more
On Fri, Nov 26, 2004 at 06:40:25PM -0500, Ron Murray wrote: >From your logs, this looks like the same problem I'm getting with > an E250 on 2.6 kernels (see the thread on this list a few days ago > titled "Re: E250, Raptor gfx, kernel 2.6: questions...". I believe > that http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=280384 also > refers to the same problem. This looks like the same problem I have. I found out that a work around for me was to install xserver-xfree86-dbg and use that server. Admar
Bug#230832: xserver-xfree86: XkbVariant was fi, kb not working in X
Subject: xserver-xfree86: XkbVariant was fi, kb not working in X Followup-For: Bug #230832 Package: xserver-xfree86 Version: 4.3.0.dfsg.1-8 *** Please type your report below this line *** I installed Debian GNU/Linux sarge from rc2 netinst cd, not choosing Desktop in the tasksel. After installing, I used aptitude to install Gnome et al. Then when gdm did not start, I noticed xserver-xfree86 was not installed and used aptitude to install also that. Now gdm worked but I could not type some characters. Middle of the keyboard did not work (and it worked OK in console). I saw in /etc/X11/XF86Config-4 that XkbVariant was fi. I had not typed that there, the file was as is from installing xserver. I was not asked during install about keyboard variant. I ran dpkg-reconfigure xserver-xfree86, chose empty to XkbVariant and keyboard started working even in X. -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xfree86 /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 20 Nov 27 11:39 /etc/X11/X -> /usr/bin/X11/XFree86 -rwxr-xr-x 1 root root 1745484 Sep 28 15:09 /usr/bin/X11/XFree86 Contents of /var/lib/xfree86/XF86Config-4.roster: xserver-xfree86 VGA-compatible devices on PCI bus: :00:0e.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) /etc/X11/XF86Config-4 unchanged from checksum in /var/lib/xfree86/XF86Config-4.md5sum. XFree86 X server configuration file status: -rw-r--r-- 1 root root 2989 Nov 27 11:46 /etc/X11/XF86Config-4 Contents of /etc/X11/XF86Config-4: # XF86Config-4 (XFree86 X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # This file is automatically updated on xserver-xfree86 package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xfree86 # package. # # If you have edited this file but would like it to be automatically updated # again, run the following commands as root: # # cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom # md5sum /etc/X11/XF86Config-4 >/var/lib/xfree86/XF86Config-4.md5sum # dpkg-reconfigure xserver-xfree86 Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/CID" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" EndSection Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "fi" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/gpmdata" Option "Protocol" "IntelliMouse" EndSection Section "Device" Identifier "ATI Technologies, Inc. Rage XL" Driver "ati" EndSection Section "Monitor" Identifier "Philips Brilliance 109P" HorizSync 30-110 VertRefresh 50-160 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "ATI Technologies, Inc. Rage XL" Monitor "Philips Brilliance 109P" DefaultDepth16 SubSection "Display" Depth 1 Modes "1280x960" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1280x960" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1280x960" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "12
Bug#283257: xfree86 config bug
Package: XFree86 Version: 4.1.0-16woody4 ( from notes on xfree-common) subject:XFree86 -configure gave Fatal server error: XFree86 has found a valid card configuration. Unfortunately the appropriate data has not been added to xf86PciInfo.h. Please forward 'scanpci -v' output to XFree86 support team. I have a new geforce MX4000 board by chaintech The complete /var/XFree86.0.log text is attached to this message along with the scanpci -v output. This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to XFree86@XFree86.Org and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.1.0.1 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 21 December 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Build Operating System: Linux 2.6.9-rc1 i686 [ELF] Module Loader present (==) Log file: "/var/log/XFree86.0.log", Time: Fri Nov 26 02:29:33 2004 (--) using VT number 7 (WW) Cannot open APM (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.4 XFree86 XInput driver : 0.2 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.2 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.1.0.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.1.0.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x80002144, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7190 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,7191 card , rev 03 class 06,04,00 hdr 01 (II) PCI: 00:04:0: chip 8086,7110 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:04:1: chip 8086,7111 card , rev 01 class 01,01,80 hdr 00 (II) PCI: 00:04:2: chip 8086,7112 card , rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:04:3: chip 8086,7113 card , rev 02 class 06,80,00 hdr 00 (II) PCI: 00:0a:0: chip 10ec,8139 card 10ec,8139 rev 10 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 10de,0185 card , rev c1 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: "scanpci" (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor="The XFree86 Project" compiled for 4.1.0.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (II) UnloadModule: "scanpci" (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 00x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 00x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 00x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x88 (VGA_EN is set) (II) Bus 1 I/O range: (II) Bus 1 non-prefetchable memory range: [0] -1 00xd600 - 0xd7ef (0x1f0) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 00xd7f0 - 0xe3ff (0xc10) MX[B] (II) Bus -1: bridge is at (0:4:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (--) PCI:*(1:0:0) NVidia unknown chipset (0x0185) rev 193, Mem @ 0xd600/24, 0xd800/27, BIOS @ 0xd7fe/17 List of video drivers: atimisc r128 radeon mga glint nv tga s3virge sis rendition neomagic i740 tdfx savage cirrus vmware tseng trident chips apm glide fbdev i128 ati i810 imstt ark cyrix siliconmotion vesa vga v4l (II) LoadModule: "atimisc" (II) Loading /usr/X11R6/lib/modules/drivers/atimisc_drv.o (II) Module atimisc: vendor="The XFree86 Project" compiled for 4.1.0.1, module version = 6.3.6 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.4 (II) Load
Re: G3 iBook LCD brightness in X under kernel 2.4.25 and 2.6.8
> r. > > So I've tried this using the stock Debian 2.6.8 and 2.6.9 PPC kernels with > the > same results. > > $ grep ATY /boot/config-2.6.9-powerpc > CONFIG_FB_ATY128=y > CONFIG_FB_ATY=y > CONFIG_FB_ATY_CT=y > CONFIG_FB_ATY_GX=y > # CONFIG_FB_ATY_XL_INIT is not set > > It seems that the atyfb module is compiled in. Is there another way to check? Check the bits in CONFIG_PMAC_BACKLIGHT in atyfb (like, add some printk's to see if they are reached etc..) Ben
Bug#279252: Please fix x-terminal-emulator for Sarge
Hello X hackers, please, please fix this bug before Sarge gets released. Steinar H. Gunderson wrote: > uxterm is now the default alternative for x-terminal-emulator; however, > debian-installer does not set an UTF-8 locale for my language (nb_NO). I just ran into this bug with my fresh Sarge install, too. :-( > Thus, I'd expect uxterm to behave like Branden thought it did; quote > Branden on IRC: "uxterm doesn't start a UTF-8 xterm if no UTF-8 locale > is set". > > However, uxterm does. If no UTF-8 locale is set (in LC_ALL, LC_CTYPE or > LANG), uxterm forcibly adds .UTF-8 to one of those ands starts an xterm > with -u8. From my point of view, this is broken; IMO this behaviour is not broken, but a special feature. Though this might be a matter of debate. However, as long as uxterm overrides the current locale, it _clearly_ should not be given a higher priority than the plain xterm in the Debian alternatives system. > I am using a non-UTF-8 > locale (and don't even have any UTF-8 locales generated), yet > x-terminal-emulator (which is the default in almost all window managers > in Debian) starts up using UTF-8. This means that my xterms suddenly use > a different character set from my aterms or eterms or whatnot, and even > more important, they use a different character set from my ssh sessions > and Linux consoles. They use a different character set and thus, with no UTF locale available, a broken keymap. I think this will break x-terminal-emulator for _many_ new installed Sarge systems. To make it worse, the x-terminal-emulator alternative was bound to plain xterm in Woody, and the change is hidden deep in the changelog. So I strongly second Steinar's proposal (of which I prefer the first solution): > My proposed solution is to do one or more of the following (in no > particular order): > > 1. Make xterm the default x-terminal-emulator again. > 2. Make uxterm not mess with the locale if it isn't UTF-8. > 3. Make debian-installer set UTF-8 locales by default for _all_ > languages. Please do not let Sarge ship with this bug. All the best, Nikolaus
