[gentoo-user] Re: xorg-server without suid still runs as root?
On 25/06/2020 17:24, inasprecali wrote: How are you starting X in the first place? Are you using a display manager? Are you running startx? In the former case, this is perfectly normal for many display managers, including SDDM. GDM, if I'm not mistaken, can and does run X as a regular user if possible. Upstream has been talking about adding this functionality to SDDM for a while, but so far it still hasn't been merged. Ah, that explains it them. I'm indeed using SDDM (due to its native support in Plasma.)
Re: [gentoo-user] Re: xorg-server
On Thu, Apr 16, 2020 at 1:07 AM Ian Zimmerman wrote: > > On 2020-04-14 21:36, Jorge Almeida wrote: > > > Yes, that seems right. I just added "-elogind" to make.conf and that's > > it. But I'm really curious about the framebuffer stuff. As for other > > stuff (mounting USB, etc), doing it by hand it's fine. > > One possible implication is that without one of these mystery packages, > you need the Xorg binary to be setuid root, and with them, you don't. > Just a hypothesis: I don't use either elogind or ConsoleKit, and my Xorg > is setuid root. :-( > > This also links back to my last question about firefox. It turned out > that the rare and random crashes stopped when I shifted from allowing X > to start on the first unused tty (which is the default) to starting it > on the tty where I'm already logged in. I'm thinking this is somehow > related to my user id and permissions on the tty. Possibly with one of > the login managers it is not an issue. I start Xorg via xinit, on a forced VT. It works fine for me. But yes, I do have it suid root... Jorge
[gentoo-user] Re: xorg-server
On 2020-04-14 21:36, Jorge Almeida wrote: > Yes, that seems right. I just added "-elogind" to make.conf and that's > it. But I'm really curious about the framebuffer stuff. As for other > stuff (mounting USB, etc), doing it by hand it's fine. One possible implication is that without one of these mystery packages, you need the Xorg binary to be setuid root, and with them, you don't. Just a hypothesis: I don't use either elogind or ConsoleKit, and my Xorg is setuid root. :-( This also links back to my last question about firefox. It turned out that the rare and random crashes stopped when I shifted from allowing X to start on the first unused tty (which is the default) to starting it on the tty where I'm already logged in. I'm thinking this is somehow related to my user id and permissions on the tty. Possibly with one of the login managers it is not an issue. -- Ian
[gentoo-user] Re: xorg-server crashing, back to log-in screen
On 01/29/2014 04:20 PM, Joseph wrote: After recent upgrade I've noticed my xorg-server is crashing, and sending me back to log-in screen on two of my computers. It happens mostly when when I click a tab in firefox or try to log-out. I'm using firefox-24.1.1 Sometimes /var/log/Xorg.0.log contains valuable hints about X crashes.
[gentoo-user] Re: xorg-server-1.11.4 runs havoc
On 01/31/2012 02:53 AM, Helmut Jarausch wrote: Hi, having updated xorg-server from 1.11.3 to 1.11.4 my machine runs havoc. xdm or slim start as usual, but having entered my password I get a blank screen or some colored strips and the only escape is via the famous SysRq sequence. But, disabling xdm, logging in via a console and using startx, Xorg is coming up normally and runs normally. Of course, I've re-emerged everything in x11-drivers. Has anybody made a similar experience and has somebody an explanation for this? Does xdm leave log files in /var/log? (I don't know) Maybe there is something old/invalid in /etc/X11 directing xdm to do something stupid. Did you try re-emerging xdm? And revdep-rebuild, naturally.
Re: [gentoo-user] Re: xorg-server-1.11.4 runs havoc
On Tue, Jan 31, 2012 at 2:28 PM, walt w41...@gmail.com wrote: On 01/31/2012 02:53 AM, Helmut Jarausch wrote: Hi, having updated xorg-server from 1.11.3 to 1.11.4 my machine runs havoc. xdm or slim start as usual, but having entered my password I get a blank screen or some colored strips and the only escape is via the famous SysRq sequence. But, disabling xdm, logging in via a console and using startx, Xorg is coming up normally and runs normally. Of course, I've re-emerged everything in x11-drivers. Has anybody made a similar experience and has somebody an explanation for this? Does xdm leave log files in /var/log? (I don't know) Maybe there is something old/invalid in /etc/X11 directing xdm to do something stupid. Did you try re-emerging xdm? And revdep-rebuild, naturally. kdm was crashing on my box after: eselect qtgraphicssystem set 2 (setting opengl) After changing it to native, and without rebuilding anything, kdm is running fine. -- Andrés Becerra Sandoval
Re: [gentoo-user] Re: xorg-server-1.10 breaks nvidia-drivers
On Sunday 03 April 2011 01:30:24 Elaine C. Sharpe wrote: On Sat, Apr 02, 2011 at 10:30:02PM +0200, Nikos Chantziaras wrote: On 04/02/2011 06:25 PM, Peter Humphrey wrote: On Saturday 02 April 2011 12:32:32 walt wrote: I had the same problem with slow bug-fixes for the older chipsets like mine. Is this the moment to upgrade your video card? They seem to be cheap enough, even here in UK. On the other hand, xorg-server 1.9.5 is perfectly fine! ;-) A lot cheaper than upgrading my video card, too -- they only sell the video card I need when you buy the whole laptop! Oh, well. It was just a thought. -- Rgds Peter
[gentoo-user] Re: xorg-server-1.10 breaks nvidia-drivers
On 04/01/2011 01:23 PM, Yohan Pereira wrote: On Friday 01 Apr 2011 08:39:04 PM walt wrote: The good old nv driver still works with 1.10, happily. have you tried nouveau? works well here. Yes, a few months ago, but I had the same problem with slow bug-fixes for the older chipsets like mine. The drivers worked well about 90% of the time and were unusable the other 10%. I reverted to xorg 1.95 and all is good again :)
Re: [gentoo-user] Re: xorg-server-1.10 breaks nvidia-drivers
On Saturday 02 April 2011 12:32:32 walt wrote: I had the same problem with slow bug-fixes for the older chipsets like mine. Is this the moment to upgrade your video card? They seem to be cheap enough, even here in UK. -- Rgds Peter
[gentoo-user] Re: xorg-server-1.10 breaks nvidia-drivers
On 04/02/2011 06:25 PM, Peter Humphrey wrote: On Saturday 02 April 2011 12:32:32 walt wrote: I had the same problem with slow bug-fixes for the older chipsets like mine. Is this the moment to upgrade your video card? They seem to be cheap enough, even here in UK. On the other hand, xorg-server 1.9.5 is perfectly fine! ;-)
Re: [gentoo-user] Re: xorg-server-1.10 breaks nvidia-drivers
On Sat, Apr 02, 2011 at 10:30:02PM +0200, Nikos Chantziaras wrote: On 04/02/2011 06:25 PM, Peter Humphrey wrote: On Saturday 02 April 2011 12:32:32 walt wrote: I had the same problem with slow bug-fixes for the older chipsets like mine. Is this the moment to upgrade your video card? They seem to be cheap enough, even here in UK. On the other hand, xorg-server 1.9.5 is perfectly fine! ;-) A lot cheaper than upgrading my video card, too -- they only sell the video card I need when you buy the whole laptop! -- caveat utilitor
[gentoo-user] Re: xorg-server 1.7.6 without mouse and keyboard (solved)
On 07/13/2010 08:14 PM, Mark Knecht wrote: On Tue, Jul 13, 2010 at 10:01 AM, Tamer Higazith9...@googlemail.com wrote: Hi Mark! you were entirely right, the problem were the input drivers. There three packages I remerged: xf86-input-mouse xf86-input-keyboard xf86-input-evdev and the problem was gone. Tamer Glad it worked. Investigate modules-rebuild as it keeps track of these things and does it for you pretty easily. Here's what's in my list: c2stable ~ # module-rebuild list ** Packages which I will emerge are: =x11-base/xorg-drivers-1.7 =x11-drivers/xf86-input-evdev-2.3.2 =x11-drivers/xf86-video-ati-6.13.0 =x11-drivers/xf86-video-fbdev-0.4.2 =x11-drivers/xf86-input-keyboard-1.4.0 =x11-drivers/xf86-input-mouse-1.5.0 =x11-drivers/xf86-video-vmware-11.0.1 =media-libs/mesa-7.8.1 All of the above are not kernel modules. Kernel updates don't affect them, only xorg-server updates do. =app-emulation/vmware-modules-1.0.0.26 Only this is affected by kernel updates.
[gentoo-user] Re: xorg-server 1.7.6 without mouse and keyboard (solved)
On 07/13/2010 08:01 PM, Tamer Higazi wrote: Hi Mark! you were entirely right, the problem were the input drivers. There three packages I remerged: xf86-input-mouse xf86-input-keyboard xf86-input-evdev and the problem was gone. Portage tells you to do exactly that after updating xorg-server. It might be a good idea to check the messages so that you can read whether you are required to do something after emerging/updating something. You can use elogv (pp-portage/elogv) for that.
Re: [gentoo-user] Re: xorg-server 1.7.6 without mouse and keyboard (solved)
On Tue, Jul 13, 2010 at 10:53 AM, Nikos Chantziaras rea...@arcor.de wrote: On 07/13/2010 08:14 PM, Mark Knecht wrote: On Tue, Jul 13, 2010 at 10:01 AM, Tamer Higazith9...@googlemail.com wrote: Hi Mark! you were entirely right, the problem were the input drivers. There three packages I remerged: xf86-input-mouse xf86-input-keyboard xf86-input-evdev and the problem was gone. Tamer Glad it worked. Investigate modules-rebuild as it keeps track of these things and does it for you pretty easily. Here's what's in my list: c2stable ~ # module-rebuild list ** Packages which I will emerge are: =x11-base/xorg-drivers-1.7 =x11-drivers/xf86-input-evdev-2.3.2 =x11-drivers/xf86-video-ati-6.13.0 =x11-drivers/xf86-video-fbdev-0.4.2 =x11-drivers/xf86-input-keyboard-1.4.0 =x11-drivers/xf86-input-mouse-1.5.0 =x11-drivers/xf86-video-vmware-11.0.1 =media-libs/mesa-7.8.1 All of the above are not kernel modules. Kernel updates don't affect them, only xorg-server updates do. =app-emulation/vmware-modules-1.0.0.26 Only this is affected by kernel updates. No disagreement on that, but frankly it doesn't matter to me. It works. Takes about 1 minute to rebuild these files. I don't care (as a user type) why I have to do it. I do it and my machine works. It covers kernel and xorg updates. That's OK with me. Or maybe you're just pointing this out to the OP? I suspect I might have failed with the same problem as the OP myself this morning had I used not it. There was an xorg-driver update that didn't update all the input devices in my make.conf file. (evdev specifically) This command did. Maybe I didn't need to rebuild evdev after an sorg-driver update but I suspect you'd agree it's safer if I do. Sometimes the tools take care of things that are just oversights. Matters not that I shouldn't have to do it. Matters more that the machine works. Cheers, Mark
Re: [gentoo-user] Re: xorg-server 1.7.6 without mouse and keyboard (solved)
Nikos Chantziaras wrote: On 07/13/2010 08:01 PM, Tamer Higazi wrote: Hi Mark! you were entirely right, the problem were the input drivers. There three packages I remerged: xf86-input-mouse xf86-input-keyboard xf86-input-evdev and the problem was gone. Portage tells you to do exactly that after updating xorg-server. It might be a good idea to check the messages so that you can read whether you are required to do something after emerging/updating something. You can use elogv (pp-portage/elogv) for that. And if you have a GUI installed, elogviewer is pretty nice too. I have both, just in case the GUI don't start. ;-) It happens. Dale :-) :-)
[gentoo-user] Re: xorg-server 1.8.1 random segfaults
On 05/16/2010 12:32 AM, Nikos Chantziaras wrote: Does anyone else get random segfaults all the time with xorg-server-1.8.1? xorg-server-1.8.0 is working just fine. I'm on ~amd64 with x11-drivers/xf86-video-ati-6.13.0 (also tried live ebuild from x11 overlay.) I just upgraded today to 1.8.1 so I have only a few hours of testing, but no crashes yet. My video card is nvidia with a different driver, of course, but my guess would be the ati driver. I've seen a lot of people complaining about ati drivers on the Xorg mailing list lately.
[gentoo-user] Re: xorg-server: Pressing 'down'/'right ctrl' keys yields newline
On 05/12/2010 05:25 AM, Amit Dor-Shifer wrote: Hi all. After updating world, xorg-1.5.3-r6 to 1.7.6 among others, I'm now faced with a/m issue. 1. left ctrl key works fine, so does the down arrow key on the numpad. 2. Seems like the down key generates a double sequence: both the down event and a newline. This doesn't happen in terminal mode, nor in firefox (3.6.3) or amarok, but does occur in konsole, thunderbird-bin, kwrite, oowriter eclipse-3.5. Attached is xorg log. amit0 ~ # qlist -Iv hal app-misc/hal-info-20090716 sys-apps/hal-0.5.13-r2 I've no idea how to proceed w/this. Any clues would be appreciated. With every version of X11, the amount of stuff in xorg.conf gets less, as part of the xorg design. I can see from your xorg.log that you have things in xorg.conf that shouldn't be there any longer. Specifically, you seem to be using the keyboard and mouse drivers *and* evdev at the same time, which is wrong -- evdev has replaced the mouse and keyboard drivers, and you don't need an Input device section for either of them now. I suggest you generate a new xorg.conf by running X -configure and use the result as a good place to add a few custom things like these: (**) Option xkb_layout en_US,ru (**) Option xkb_variant ,winkeys (**) Option xkb_options grp:shift_toggle,grp_led:scroll
[gentoo-user] Re: xorg-server/nvidia/x86-driver updated: No kbd, no mouse
On 04/25/2010 06:28 AM, meino.cra...@gmx.de wrote: [ 2806.923] (II) LoadModule: evdev [ 2806.923] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [ 2806.973] (II) Module evdev: vendor=X.Org Foundation [ 2806.973]compiled for 1.8.0, module version = 2.4.0 [ 2806.973]Module class: X.Org XInput Driver [ 2806.973]ABI class: X.Org XInput driver, version 9.0 [ 2806.973] (**) Logitech N48: always reports core events [ 2806.973] (**) Logitech N48: Device: /dev/input/mouse0 [ 2806.984] (EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device [ 2807.016] (II) UnloadModule: evdev Inappropiate ioctl looks like some version mismatch between kernel interface and ... what? Notice that the error message appeared between loading evdev and unloading evdev, so I read that as meaning you need to recompile evdev. I'm not entirely clear yet about how 1.8 handles input devices, but I think it uses evdev automatically even if you don't have it in your xorg.conf.
Re: [gentoo-user] Re: xorg-server/nvidia/x86-driver updated: No kbd, no mouse
walt w41...@gmail.com [10-04-25 17:56]: On 04/25/2010 06:28 AM, meino.cra...@gmx.de wrote: [ 2806.923] (II) LoadModule: evdev [ 2806.923] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [ 2806.973] (II) Module evdev: vendor=X.Org Foundation [ 2806.973] compiled for 1.8.0, module version = 2.4.0 [ 2806.973] Module class: X.Org XInput Driver [ 2806.973] ABI class: X.Org XInput driver, version 9.0 [ 2806.973] (**) Logitech N48: always reports core events [ 2806.973] (**) Logitech N48: Device: /dev/input/mouse0 [ 2806.984] (EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device [ 2807.016] (II) UnloadModule: evdev Inappropiate ioctl looks like some version mismatch between kernel interface and ... what? Notice that the error message appeared between loading evdev and unloading evdev, so I read that as meaning you need to recompile evdev. I'm not entirely clear yet about how 1.8 handles input devices, but I think it uses evdev automatically even if you don't have it in your xorg.conf. That was also my first thought, but evdev was recompiled -- as I wrote in my initial mail... What next? -- Please don't send me any Word- or Powerpoint-Attachments unless it's absolutely neccessary. - Send simply Text. See http://www.gnu.org/philosophy/no-word-attachments.html In a world without fences and walls nobody needs gates and windows.
Re: [gentoo-user] Re: xorg-server/nvidia/x86-driver updated: No kbd, no mouse
meino.cra...@gmx.de writes: That was also my first thought, but evdev was recompiled -- as I wrote in my initial mail... What next? Do you have an InputClass section in your xorg.conf? This is needed for xorg to use udev to detect input devices.
Re: [gentoo-user] Re: xorg-server/nvidia/x86-driver updated: No kbd, no mouse
Graham Murray gra...@gmurray.org.uk [10-04-25 18:28]: meino.cra...@gmx.de writes: That was also my first thought, but evdev was recompiled -- as I wrote in my initial mail... What next? Do you have an InputClass section in your xorg.conf? This is needed for xorg to use udev to detect input devices. yes: Section InputClass Identifier keyboard-all Driver evdev Option XkbLayout de Option XkbVariant ,qwertz Option XkbOptions grp:alt_shift_toggle,grp:switch,compose:rwin,terminate:ctrl_alt_bksp Option XkbVariant nodeadkeys MatchIsKeyboard on EndSection -- Please don't send me any Word- or Powerpoint-Attachments unless it's absolutely neccessary. - Send simply Text. See http://www.gnu.org/philosophy/no-word-attachments.html In a world without fences and walls nobody needs gates and windows.
[gentoo-user] Re: xorg-server/nvidia/x86-driver updated: No kbd, no mouse
On 04/25/2010 10:05 AM, meino.cra...@gmx.de wrote: Graham Murraygra...@gmurray.org.uk [10-04-25 18:28]: meino.cra...@gmx.de writes: That was also my first thought, but evdev was recompiled -- as I wrote in my initial mail... What next? Do you have an InputClass section in your xorg.conf? This is needed for xorg to use udev to detect input devices. yes: Section InputClass Identifier keyboard-all Driver evdev Option XkbLayout de Option XkbVariant ,qwertz Option XkbOptions grp:alt_shift_toggle,grp:switch,compose:rwin,terminate:ctrl_alt_bksp Option XkbVariant nodeadkeys MatchIsKeyboard on EndSection I have no InputClass section at all, but I don't need all the options you use. Might be worth commenting the whole section out just as a test. I built xorg-server with the hal useflag disabled, and udev flag enabled.
Re: [gentoo-user] Re: xorg-server/nvidia/x86-driver updated: No kbd, no mouse
walt w41...@gmail.com [10-04-26 03:00]: On 04/25/2010 10:05 AM, meino.cra...@gmx.de wrote: Graham Murraygra...@gmurray.org.uk [10-04-25 18:28]: meino.cra...@gmx.de writes: That was also my first thought, but evdev was recompiled -- as I wrote in my initial mail... What next? Do you have an InputClass section in your xorg.conf? This is needed for xorg to use udev to detect input devices. yes: Section InputClass Identifier keyboard-all Driver evdev Option XkbLayout de Option XkbVariant ,qwertz Option XkbOptions grp:alt_shift_toggle,grp:switch,compose:rwin,terminate:ctrl_alt_bksp Option XkbVariant nodeadkeys MatchIsKeyboard on EndSection I have no InputClass section at all, but I don't need all the options you use. Might be worth commenting the whole section out just as a test. I built xorg-server with the hal useflag disabled, and udev flag enabled. Sorry guys for not understanding this anymore. First question after posting my problem was: Did you read the guides??? Now I included exactly what the guides say and compiled as the ebuild has configured it (hal off, udev on) and now I am told to remove the stuff again... I am going back to xorg-server 1.7.6 and wait until this becomes more consistent. -- Please don't send me any Word- or Powerpoint-Attachments unless it's absolutely neccessary. - Send simply Text. See http://www.gnu.org/philosophy/no-word-attachments.html In a world without fences and walls nobody needs gates and windows.
Re: [gentoo-user] Re: xorg-server upgrade
On 4/21/2010 1:41 AM, Graham Murray wrote: walt w41...@gmail.com writes: That was true in the past, but no longer. The recent release of xorg 1.8 specifically says that hal will not be supported in any future xorg versions, so we should all start looking beyond hal. Don't spend a lot of effort now learning about hal because it's on the way out. (Not many people mourning it's impending demise, apparently.) And if you use udev then you need an (at least minimal) xorg.conf. With the new modular xorg.conf.d setup, you really don't. I have no xorg.conf and the only thing I'm missing is the mouse wheel emulation on my touchpad. The xorg-server package includes configuration segments that handle the basic input devices for you, and the server itself is pretty good as figuring out your output devices. --Mike
[gentoo-user] Re: xorg-server upgrade
On 04/20/2010 04:05 PM, john wrote: Linux/Gentoo appaers to be moving away from xorg.conf and towards hal/policices... That was true in the past, but no longer. The recent release of xorg 1.8 specifically says that hal will not be supported in any future xorg versions, so we should all start looking beyond hal. Don't spend a lot of effort now learning about hal because it's on the way out. (Not many people mourning it's impending demise, apparently.)
Re: [gentoo-user] Re: xorg-server upgrade
walt w41...@gmail.com writes: That was true in the past, but no longer. The recent release of xorg 1.8 specifically says that hal will not be supported in any future xorg versions, so we should all start looking beyond hal. Don't spend a lot of effort now learning about hal because it's on the way out. (Not many people mourning it's impending demise, apparently.) And if you use udev then you need an (at least minimal) xorg.conf.
[gentoo-user] Re: xorg-server 1.7.
On 04/09/2010 10:41 PM, Dale wrote: I searched the logs in /var/log and found this: (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X (EE) NVIDIA(0): log file that the GLX module has been loaded in your X (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If #eselect opengl list Available OpenGL implementations: [1] nvidia * -- Are you using this one? [2] xorg-x11
Re: [gentoo-user] Re: xorg-server 1.7.
walt wrote: On 04/09/2010 10:41 PM, Dale wrote: I searched the logs in /var/log and found this: (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X (EE) NVIDIA(0): log file that the GLX module has been loaded in your X (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If #eselect opengl list Available OpenGL implementations: [1] nvidia * -- Are you using this one? [2] xorg-x11 Yep. I saw it switch to that during the emerge but I typed it in to make sure. I downgraded back to the old versions and things are working now. I did have to recompile all the input stuff again but at least it works. According to the forums, this is a known problem since xorg is updated but apparently nvidia is not yet. Dale :-) :-)
[gentoo-user] Re: xorg-server 1.7.
On 04/10/2010 11:19 AM, Dale wrote: walt wrote: On 04/09/2010 10:41 PM, Dale wrote: I searched the logs in /var/log and found this: (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X (EE) NVIDIA(0): log file that the GLX module has been loaded in your X (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If #eselect opengl list Available OpenGL implementations: [1] nvidia * -- Are you using this one? [2] xorg-x11 Yep. I saw it switch to that during the emerge but I typed it in to make sure. I downgraded back to the old versions and things are working now. I did have to recompile all the input stuff again but at least it works. According to the forums, this is a known problem since xorg is updated but apparently nvidia is not yet. Yes, I see now. It works for me because I have the ~ version of the nvidia driver unmasked. I run the most recent kernel from Linus and the stable driver won't compile against his newer kernels.
Re: [gentoo-user] Re: xorg-server 1.7.
walt wrote: On 04/10/2010 11:19 AM, Dale wrote: walt wrote: On 04/09/2010 10:41 PM, Dale wrote: I searched the logs in /var/log and found this: (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X (EE) NVIDIA(0): log file that the GLX module has been loaded in your X (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If #eselect opengl list Available OpenGL implementations: [1] nvidia * -- Are you using this one? [2] xorg-x11 Yep. I saw it switch to that during the emerge but I typed it in to make sure. I downgraded back to the old versions and things are working now. I did have to recompile all the input stuff again but at least it works. According to the forums, this is a known problem since xorg is updated but apparently nvidia is not yet. Yes, I see now. It works for me because I have the ~ version of the nvidia driver unmasked. I run the most recent kernel from Linus and the stable driver won't compile against his newer kernels. I think this is a version mismatch thing. Xorg, nvidia and maybe something else just don't like the currently available versions at the moment. I did try that keyworded nvidia driver for my card but it wasn't happy with it either. I think that was why I had a black screen. I dunno. At least it is working for now and maybe when the next version is released all this will be fixed. Dale :-) :-)
Re: [gentoo-user] Re: Xorg-server fails to compile
On Mon, 2009-12-14 at 04:27 +0100, meino.cra...@gmx.de wrote: but interestingly portageq owners / xextproto reports None of the installed packages claim the file(s). Yes, since you have given it the name of an ebuild, not a file. You can do what you want by equery files [packagename]
Re: [gentoo-user] Re: Xorg-server fails to compile
Boy Hartsuiker bm.hartsui...@gmx.com [09-12-14 16:56]: On Mon, 2009-12-14 at 04:27 +0100, meino.cra...@gmx.de wrote: but interestingly portageq owners / xextproto reports None of the installed packages claim the file(s). Yes, since you have given it the name of an ebuild, not a file. You can do what you want by equery files [packagename] I did a emerge -C libXext xextproto; emerge -1 libXext xextproto; emerge -1 xorg-server but the error remains the same. Now? -- Please don't send me any Word- or Powerpoint-Attachments unless it's absolutely neccessary. - Send simply Text. See http://www.gnu.org/philosophy/no-word-attachments.html In a world without fences and walls nobody needs gates and windows.
Re: [gentoo-user] Re: Xorg-server fails to compile
On Mon, 2009-12-14 at 17:43 +0100, meino.cra...@gmx.de wrote: I did a emerge -C libXext xextproto; emerge -1 libXext xextproto; emerge -1 xorg-server but the error remains the same. Now? Seems like the versions are incompatible with each other. Do you have anything X related masked/unmasked or key worded? You can also try unmerging them both and then emerging xorg-server and let portage handle the dependencies. If this is a first install you should emerge x11-base/xorg-x11. I made the mistake of just emerging the X server once, and that doesn't work. Maybe run revdep-rebuild two times to be sure everything is in order.
Re: [gentoo-user] Re: Xorg-server fails to compile
On Mon, 2009-12-14 at 17:43 +0100, meino.cra...@gmx.de wrote: I did a emerge -C libXext xextproto; emerge -1 libXext xextproto; emerge -1 xorg-server but the error remains the same. Now? Seems like the versions are incompatible with each other. Do you have anything X related masked/unmasked or key worded? You can also try unmerging them both and then emerging xorg-server and let portage handle the dependencies. If this is a first install you should emerge x11-base/xorg-x11. I made the mistake of just emerging the X server once, and that doesn't work. Maybe run revdep-rebuild two times to be sure everything is in order.
[gentoo-user] Re: Xorg-server fails to compile
On 12/13/2009 07:27 PM, meino.cra...@gmx.de wrote: * * x11-libs/libXtst-1.1.0== UNSTABLE version * Package 'x11-proto/xextproto-7.0.5' = STABLE version Your portage is trying to mix stable and unstable packages on the same machine. You need to figure out why that's happening.
Re: [gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
2009/12/13 walt w41...@gmail.com: On 12/12/2009 04:20 PM, Mick wrote: ... I tried the startx trick. I recall that this would launch my WM (fluxbox), but now all I get is an X session with twm! Has something changed with /etc/rc.conf? Where should I specify fluxbox? That twm session is the default (see end of /etc/X11/xinit/xinitrc) if you don't specify what you really want. The xdm display manager checks in ~/.xsession for the stuff you want to run (i.e. fluxbox), but startx uses the file ~/.xinitrc for the same purpose. You could probably just copy .xsession to .xinitrc for starters. OK, but I never had set up ~/.xsession or ~/.xinitrc files. This is a single user machine. As far as I can recall I had only set up in /etc/rc.conf the parameter XSESSION=fluxbox, which looked in /etc/X11/Sessions/ and ran the fluxbox configuration file that I had in there. Looking at /etc/conf.d/xdm I see this: = # What display manager do you use ? [ xdm | gdm | kdm | kdm-4.3 | gpe | entrance ] # NOTE: If this is set in /etc/rc.conf, that setting will override this one. = In that file I have specified DISPLAYMANAGER=xdm. Again as far as I recall this is how I had set things up, so I am not sure what has changed recently. Setting a ~/.xinitrc file with 'exec startfluxbox' in it starts fluxbox nicely if I run startx from the console - but this is not the same session that I would get which would also include xconsole. I found these messages now, but no significant errors: = Setting CPU scaling governor performance for CPU 1... could not open file /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor for writing! failed setting 'performance' CPUfreq governor! Failed to read: session.screen0.maxIgnoreIncrement Setting default value Failed to read: session.screen0.maxDisableMove Setting default value Failed to read: session.screen0.maxDisableResize Setting default value Failed to read: session.screen0.noFocusWhileTypingDelay Setting default value Failed to read: session.screen0.tooltipDelay Setting default value Failed to read: session.screen0.clientMenu.usePixmap Setting default value Failed to read: session.screen0.maxIgnoreIncrement Setting default value Failed to read: session.screen0.maxDisableMove Setting default value Failed to read: session.screen0.maxDisableResize Setting default value Failed to read: session.screen0.noFocusWhileTypingDelay Setting default value Failed to read: session.screen0.tooltipDelay Setting default value Failed to read: session.screen0.clientMenu.usePixmap Setting default value Failed to read: session.screen0.maxIgnoreIncrement Setting default value Failed to read: session.screen0.maxDisableMove Setting default value Failed to read: session.screen0.maxDisableResize Setting default value Failed to read: session.screen0.noFocusWhileTypingDelay Setting default value Failed to read: session.screen0.tooltipDelay Setting default value Failed to read: session.screen0.clientMenu.usePixmap Setting default value Failed to read: session.screen0.slit.acceptKdeDockapps Setting default value = So, what would be the way to start xdm and have xdm starting fluxbox? -- Regards, Mick
[gentoo-user] Re: Xorg-server fails to compile
On 12/13/2009 10:03 AM, meino.cra...@gmx.de wrote: Hi, emerge of xorg-server-1.6.5-r1 fails while in the build process. Logfile's contents is: /usr/include/X11/extensions/dpms.h:40: error: expected ')' before '*' token /usr/include/X11/extensions/dpms.h:41: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSGetVersion' /usr/include/X11/extensions/dpms.h:42: error: expected ')' before '*' token /usr/include/X11/extensions/dpms.h:43: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSSetTimeouts' /usr/include/X11/extensions/dpms.h:44: error: expected ')' before '*' token /usr/include/X11/extensions/dpms.h:45: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSEnable' /usr/include/X11/extensions/dpms.h:46: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSDisable' /usr/include/X11/extensions/dpms.h:47: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSForceLevel' /usr/include/X11/extensions/dpms.h:48: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSInfo' That file (dpms.h) is installed by x11-proto/xextproto-7.0.5. Do you have that version? I would re-emerge that package even if it look correct.
Re: [gentoo-user] Re: Xorg-server fails to compile
walt w41...@gmail.com [09-12-14 01:08]: On 12/13/2009 10:03 AM, meino.cra...@gmx.de wrote: Hi, emerge of xorg-server-1.6.5-r1 fails while in the build process. Logfile's contents is: /usr/include/X11/extensions/dpms.h:40: error: expected ')' before '*' token /usr/include/X11/extensions/dpms.h:41: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSGetVersion' /usr/include/X11/extensions/dpms.h:42: error: expected ')' before '*' token /usr/include/X11/extensions/dpms.h:43: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSSetTimeouts' /usr/include/X11/extensions/dpms.h:44: error: expected ')' before '*' token /usr/include/X11/extensions/dpms.h:45: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSEnable' /usr/include/X11/extensions/dpms.h:46: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSDisable' /usr/include/X11/extensions/dpms.h:47: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSForceLevel' /usr/include/X11/extensions/dpms.h:48: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSInfo' That file (dpms.h) is installed by x11-proto/xextproto-7.0.5. Do you have that version? I would re-emerge that package even if it look correct. Emerge refuses to merge that: * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / filename` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). Once again, please do NOT file * a bug report unless you have completely understood the above message. * * Detected file collision(s): * * /usr/include/X11/extensions/XTest.h * /usr/include/X11/extensions/lbxbuf.h * /usr/include/X11/extensions/Xag.h * /usr/include/X11/extensions/Xge.h * /usr/include/X11/extensions/lbxbufstr.h * /usr/include/X11/extensions/XEVI.h * /usr/include/X11/extensions/multibuf.h * /usr/include/X11/extensions/shape.h * /usr/include/X11/extensions/XLbx.h * /usr/include/X11/extensions/XShm.h * /usr/include/X11/extensions/Xdbe.h * /usr/include/X11/extensions/Xcup.h * /usr/include/X11/extensions/Xext.h * /usr/include/X11/extensions/dpms.h * /usr/include/X11/extensions/MITMisc.h * /usr/include/X11/extensions/security.h * /usr/include/X11/extensions/xtestext1.h * /usr/include/X11/extensions/sync.h * /usr/include/X11/extensions/lbximage.h * /usr/include/X11/extensions/extutil.h * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * x11-libs/libXext-1.1.1 * /usr/include/X11/extensions/MITMisc.h * /usr/include/X11/extensions/XEVI.h * /usr/include/X11/extensions/XLbx.h * /usr/include/X11/extensions/XShm.h * /usr/include/X11/extensions/Xag.h * /usr/include/X11/extensions/Xcup.h * /usr/include/X11/extensions/Xdbe.h * /usr/include/X11/extensions/Xext.h * /usr/include/X11/extensions/Xge.h * /usr/include/X11/extensions/dpms.h * /usr/include/X11/extensions/extutil.h * /usr/include/X11/extensions/lbxbuf.h * /usr/include/X11/extensions/lbxbufstr.h * /usr/include/X11/extensions/lbximage.h * /usr/include/X11/extensions/multibuf.h * /usr/include/X11/extensions/security.h * /usr/include/X11/extensions/shape.h * /usr/include/X11/extensions/sync.h * /usr/include/X11/extensions/xtestext1.h * * x11-libs/libXtst-1.1.0 * /usr/include/X11/extensions/XTest.h * * Package 'x11-proto/xextproto-7.0.5' NOT merged due to file collisions. * If necessary, refer to your elog messages for the whole content of the * above message. but interestingly portageq owners / xextproto reports None of the installed packages claim the file(s). How can I proceed ? -- Please don't send me any Word- or Powerpoint-Attachments unless it's absolutely neccessary. - Send simply Text. See http://www.gnu.org/philosophy/no-word-attachments.html In a world without fences and walls nobody needs gates and windows.
Re: [gentoo-user] Re: Xorg-server fails to compile
On my system I have libXtst-1.1.0 installed but I'm running with xextproto-7.1.1 try unmasking xextproto and see if that helps. On Mon, 14 Dec 2009 04:27:11 +0100, meino.cra...@gmx.de wrote: walt w41...@gmail.com [09-12-14 01:08]: On 12/13/2009 10:03 AM, meino.cra...@gmx.de wrote: Hi, emerge of xorg-server-1.6.5-r1 fails while in the build process. Logfile's contents is: /usr/include/X11/extensions/dpms.h:40: error: expected ')' before '*' token /usr/include/X11/extensions/dpms.h:41: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSGetVersion' /usr/include/X11/extensions/dpms.h:42: error: expected ')' before '*' token /usr/include/X11/extensions/dpms.h:43: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSSetTimeouts' /usr/include/X11/extensions/dpms.h:44: error: expected ')' before '*' token /usr/include/X11/extensions/dpms.h:45: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSEnable' /usr/include/X11/extensions/dpms.h:46: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSDisable' /usr/include/X11/extensions/dpms.h:47: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSForceLevel' /usr/include/X11/extensions/dpms.h:48: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'DPMSInfo' That file (dpms.h) is installed by x11-proto/xextproto-7.0.5. Do you have that version? I would re-emerge that package even if it look correct. Emerge refuses to merge that: * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / filename` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). Once again, please do NOT file * a bug report unless you have completely understood the above message. * * Detected file collision(s): * * /usr/include/X11/extensions/XTest.h * /usr/include/X11/extensions/lbxbuf.h * /usr/include/X11/extensions/Xag.h * /usr/include/X11/extensions/Xge.h * /usr/include/X11/extensions/lbxbufstr.h * /usr/include/X11/extensions/XEVI.h * /usr/include/X11/extensions/multibuf.h * /usr/include/X11/extensions/shape.h * /usr/include/X11/extensions/XLbx.h * /usr/include/X11/extensions/XShm.h * /usr/include/X11/extensions/Xdbe.h * /usr/include/X11/extensions/Xcup.h * /usr/include/X11/extensions/Xext.h * /usr/include/X11/extensions/dpms.h * /usr/include/X11/extensions/MITMisc.h * /usr/include/X11/extensions/security.h * /usr/include/X11/extensions/xtestext1.h * /usr/include/X11/extensions/sync.h * /usr/include/X11/extensions/lbximage.h * /usr/include/X11/extensions/extutil.h * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * x11-libs/libXext-1.1.1 * /usr/include/X11/extensions/MITMisc.h * /usr/include/X11/extensions/XEVI.h * /usr/include/X11/extensions/XLbx.h * /usr/include/X11/extensions/XShm.h * /usr/include/X11/extensions/Xag.h * /usr/include/X11/extensions/Xcup.h * /usr/include/X11/extensions/Xdbe.h * /usr/include/X11/extensions/Xext.h * /usr/include/X11/extensions/Xge.h * /usr/include/X11/extensions/dpms.h * /usr/include/X11/extensions/extutil.h * /usr/include/X11/extensions/lbxbuf.h * /usr/include/X11/extensions/lbxbufstr.h * /usr/include/X11/extensions/lbximage.h * /usr/include/X11/extensions/multibuf.h * /usr/include/X11/extensions/security.h * /usr/include/X11/extensions/shape.h * /usr/include/X11/extensions/sync.h * /usr/include/X11/extensions/xtestext1.h * * x11-libs/libXtst-1.1.0 * /usr/include/X11/extensions/XTest.h * * Package 'x11-proto/xextproto-7.0.5' NOT merged due to file collisions. * If necessary, refer to your elog messages for the whole content of the * above message. but interestingly portageq owners / xextproto reports None of the installed packages claim the file(s). How can I proceed ? -- Zeerak
Re: [gentoo-user] Re: Xorg-server fails to compile
Just unmerge libXext and xextproto and then emerge them again. It looks like some files have been moved from one to the other.
[gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
2009/12/11 Mick michaelkintz...@gmail.com: Hi All, I emerged xorg-server-1.6.5-r1, as well as x11-drivers/xf86-input-synaptics-1.2.0, xf86-input-keyboard-1.4.0, xf86-input-mouse-1.5.0 and xf86-input-evdev-2.3.1 and now I can't get past the xdm login screen. It is worth noting that I also emerged a load of apps including xkbcomp-1.1.1 and xinit-1.2.0-r3. When I enter my passwd at the xdm login it takes a couple of seconds and it drops me back into the login screen. The xdm.log mentions: === X.Org X Server 1.6.5 Release Date: 2009-10-11 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.31-gentoo-r6 i686 Current Operating System: Linux lappy 2.6.31-gentoo-r6 #1 Fri Nov 27 07:32:41 GMT 2009 i686 Build Date: 11 December 2009 11:36:44AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Dec 11 20:10:50 2009 (==) Using default built-in configuration (30 lines) (EE) Failed to load module vesa (module does not exist, 0) (EE) Failed to load module fbdev (module does not exist, 0) NTSC PAL PAL-M XRANDR name: VGA-0 Connector: VGA CRT1: INTERNAL_DAC1 DDC reg: 0x60 XRANDR name: LVDS Connector: LVDS LCD1: INTERNAL_LVDS DDC reg: 0x1a0 XRANDR name: S-video Connector: S-video TV1: INTERNAL_DAC2 DDC reg: 0x0 finished output detect: 0 finished output detect: 1 finished output detect: 2 finished all detect before xf86InitialConfiguration after xf86InitialConfiguration Entering TV Save Save TV timing tables saveTimingTables: reading timing tables TV Save done disable LVDS disable primary dac disable LVDS disable TV disable LVDS init memmap init common init crtc1 init pll1 restore memmap restore common restore crtc1 restore pll1 set RMX set LVDS enable LVDS disable primary dac disable TV expected keysym, got XF86TouchpadToggle: line 122 of inet The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server /etc/X11/xdm/Xresources:31:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:32:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:33:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:34:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:35:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:36:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:37:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:38:2: error: invalid preprocessing directive #xlogin XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0.0 after 117 requests (109 known processed) with 0 events remaining. disable LVDS finished PLL2 Entering Restore TV Restore TV PLL Restore TVHV Restore TV Restarts Restore Timing Tables Restore TV standard Leaving Restore TV error setting MTRR (base = 0x4800, size = 0x0100, type = 1) Invalid argument (22) Entering TV Save Save TV timing tables saveTimingTables: reading timing tables TV Save done disable LVDS disable primary dac disable LVDS disable TV disable LVDS init memmap init common init crtc1 init pll1 restore memmap restore common restore crtc1 restore pll1 set RMX set LVDS enable LVDS disable primary dac disable TV (EE) XKB: No components provided for device Virtual core keyboard The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from
[gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
2009/12/12 Mick michaelkintz...@gmail.com: 2009/12/11 Mick michaelkintz...@gmail.com: Hi All, I emerged xorg-server-1.6.5-r1, as well as x11-drivers/xf86-input-synaptics-1.2.0, xf86-input-keyboard-1.4.0, xf86-input-mouse-1.5.0 and xf86-input-evdev-2.3.1 and now I can't get past the xdm login screen. It is worth noting that I also emerged a load of apps including xkbcomp-1.1.1 and xinit-1.2.0-r3. When I enter my passwd at the xdm login it takes a couple of seconds and it drops me back into the login screen. The xdm.log mentions: === X.Org X Server 1.6.5 Release Date: 2009-10-11 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.31-gentoo-r6 i686 Current Operating System: Linux lappy 2.6.31-gentoo-r6 #1 Fri Nov 27 07:32:41 GMT 2009 i686 Build Date: 11 December 2009 11:36:44AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Dec 11 20:10:50 2009 (==) Using default built-in configuration (30 lines) (EE) Failed to load module vesa (module does not exist, 0) (EE) Failed to load module fbdev (module does not exist, 0) NTSC PAL PAL-M XRANDR name: VGA-0 Connector: VGA CRT1: INTERNAL_DAC1 DDC reg: 0x60 XRANDR name: LVDS Connector: LVDS LCD1: INTERNAL_LVDS DDC reg: 0x1a0 XRANDR name: S-video Connector: S-video TV1: INTERNAL_DAC2 DDC reg: 0x0 finished output detect: 0 finished output detect: 1 finished output detect: 2 finished all detect before xf86InitialConfiguration after xf86InitialConfiguration Entering TV Save Save TV timing tables saveTimingTables: reading timing tables TV Save done disable LVDS disable primary dac disable LVDS disable TV disable LVDS init memmap init common init crtc1 init pll1 restore memmap restore common restore crtc1 restore pll1 set RMX set LVDS enable LVDS disable primary dac disable TV expected keysym, got XF86TouchpadToggle: line 122 of inet The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server /etc/X11/xdm/Xresources:31:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:32:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:33:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:34:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:35:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:36:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:37:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:38:2: error: invalid preprocessing directive #xlogin XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0.0 after 117 requests (109 known processed) with 0 events remaining. disable LVDS finished PLL2 Entering Restore TV Restore TV PLL Restore TVHV Restore TV Restarts Restore Timing Tables Restore TV standard Leaving Restore TV error setting MTRR (base = 0x4800, size = 0x0100, type = 1) Invalid argument (22) Entering TV Save Save TV timing tables saveTimingTables: reading timing tables TV Save done disable LVDS disable primary dac disable LVDS disable TV disable LVDS init memmap init common init crtc1 init pll1 restore memmap restore common restore crtc1 restore pll1 set RMX set LVDS enable LVDS disable primary dac disable TV (EE) XKB: No components provided for device Virtual core keyboard The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got
[gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
On 12/12/2009 12:55 AM, Mick wrote: ... Not sure if it is related but I am getting this: Regenerating /etc/ld.so.cache... /sbin/ldconfig: /usr/lib/libltdl.so.3 is not a symbolic link What does this mean? revdep-rebuild does not show anything needing to be rebuilt. That must be a very old file. Here's what I have: -rw-r--r-- 1 root root 41652 2009-12-08 06:30 /usr/lib/libltdl.a -rw-r--r-- 1 root root 919 2009-12-08 06:30 /usr/lib/libltdl.la lrwxrwxrwx 1 root root16 2009-12-08 06:31 /usr/lib/libltdl.so - libltdl.so.7.2.1* lrwxrwxrwx 1 root root16 2009-12-08 06:31 /usr/lib/libltdl.so.7 - libltdl.so.7.2.1* -rwxr-xr-x 1 root root 34252 2009-12-08 06:30 /usr/lib/libltdl.so.7.2.1* If you also have these files then just delete the so.3 version. Otherwise, I've downgraded xkbcomp with no joy and now I am downgrading xorg-server to see if this has any effect. I'm struggling to understand all the keyboard stuff too. Do you still use an xorg.conf file? If you are using evdev then you should not be using the xf86-input-mouse or xf86-input-keyboard drivers, just the xf86-input-evdev driver. I have the entire input section of xorg.conf commented out and evdev seems to be the default input driver now. I'll bet xdm is hiding the really helpful error messages, so I would shut off xdm and use startx to see if you get any better information.
Re: [gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
On 12/12/2009, walt w41...@gmail.com wrote: On 12/12/2009 12:55 AM, Mick wrote: ... Not sure if it is related but I am getting this: Regenerating /etc/ld.so.cache... /sbin/ldconfig: /usr/lib/libltdl.so.3 is not a symbolic link What does this mean? revdep-rebuild does not show anything needing to be rebuilt. That must be a very old file. Here's what I have: -rw-r--r-- 1 root root 41652 2009-12-08 06:30 /usr/lib/libltdl.a -rw-r--r-- 1 root root 919 2009-12-08 06:30 /usr/lib/libltdl.la lrwxrwxrwx 1 root root16 2009-12-08 06:31 /usr/lib/libltdl.so - libltdl.so.7.2.1* lrwxrwxrwx 1 root root16 2009-12-08 06:31 /usr/lib/libltdl.so.7 - libltdl.so.7.2.1* -rwxr-xr-x 1 root root 34252 2009-12-08 06:30 /usr/lib/libltdl.so.7.2.1* Mine are slightly different. I also have /usr/lib/lbltdl.so.0 - libltdl.so.0.1.2 and also have libltdl.so.0.1.2 libltdl.so.3 libltdl.so.3.1.0 If you also have these files then just delete the so.3 version. Thanks, I'll check for dependencies and then remove them. Otherwise, I've downgraded xkbcomp with no joy and now I am downgrading xorg-server to see if this has any effect. I'm struggling to understand all the keyboard stuff too. Do you still use an xorg.conf file? If you are using evdev then you should not be using the xf86-input-mouse or xf86-input-keyboard drivers, just the xf86-input-evdev driver. I have the entire input section of xorg.conf commented out and evdev seems to be the default input driver now. I have had mouse, keyboard and synaptics along with evdev in my INPUT_DEVICES and have emerged relative drivers. I am now going to remove them and see what gives. I am not clear which /etc/hal/fdi/policy/* files I should have in there ... any ideas? I'll bet xdm is hiding the really helpful error messages, so I would shut off xdm and use startx to see if you get any better information. Thanks, will try that too. -- Regards, Mick
[gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
On 12/12/2009 03:14 PM, Mick wrote: ... I have had mouse, keyboard and synaptics along with evdev in my INPUT_DEVICES and have emerged relative drivers. I am now going to remove them and see what gives. I know nothing about the synaptics driver, so be careful about deleting it. Maybe rename it instead of deleting it? I am not clear which /etc/hal/fdi/policy/* files I should have in there ... any ideas? That depends on what hardware you have -- a lot of the stuff that once went into xorg.conf can be put in an fdi file now. Here is an example: I have an unusual mouse with four buttons and no wheel, and I use one extra button to simulate a mouse wheel: $cat /etc/hal/fdi/policy/10-x11-logitech.fdi ?xml version=1.0 encoding=ISO-8859-1? deviceinfo version=0.2 device match key=info.product contains=ImExPS/2 merge key=input.x11_options.EmulateWheel type=stringtrue/merge merge key=input.x11_options.EmulateWheelButton type=string8/merge /match /device /deviceinfo The two lines with input.x11_options used to be in my xorg.conf in the Input section. Those lines do the same thing now that I've moved them into an fdi file.
Re: [gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
On 12/12/2009, walt w41...@gmail.com wrote: On 12/12/2009 03:14 PM, Mick wrote: ... I have had mouse, keyboard and synaptics along with evdev in my INPUT_DEVICES and have emerged relative drivers. I am now going to remove them and see what gives. I know nothing about the synaptics driver, so be careful about deleting it. Maybe rename it instead of deleting it? Nope, unmerged it and deleted it from make.conf, then when I emerged xf86-video-ati and evdev all other drivers (mouse, keyboard, synaptics) were brought in as well. I am not clear which /etc/hal/fdi/policy/* files I should have in there ... any ideas? That depends on what hardware you have -- a lot of the stuff that once went into xorg.conf can be put in an fdi file now. Here is an example: Thanks for that. I tried the startx trick. I recall that this would launch my WM (fluxbox), but now all I get is an X session with twm! Has something changed with /etc/rc.conf? Where should I specify fluxbox? No /var/log/xdm.log or other errors were there this time. Trying to start xdm and I keep getting the same old errors: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server (:0.0) and (EE) XKB: No components provided for device Virtual core keyboard. I am running out of things to try now. I don't have a recent enough back up otherwise I would roll back this bad experience. -- Regards, Mick
[gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
On 12/12/2009 04:20 PM, Mick wrote: ... I tried the startx trick. I recall that this would launch my WM (fluxbox), but now all I get is an X session with twm! Has something changed with /etc/rc.conf? Where should I specify fluxbox? That twm session is the default (see end of /etc/X11/xinit/xinitrc) if you don't specify what you really want. The xdm display manager checks in ~/.xsession for the stuff you want to run (i.e. fluxbox), but startx uses the file ~/.xinitrc for the same purpose. You could probably just copy .xsession to .xinitrc for starters. No /var/log/xdm.log or other errors were there this time. Trying to start xdm and I keep getting the same old errors: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server (:0.0) and (EE) XKB: No components provided for device Virtual core keyboard. I am running out of things to try now. I don't have a recent enough back up otherwise I would roll back this bad experience. I have these lines in my xorg.conf but I can't remember when or why I put them there. I believe it had something to do with evdev, though. Section ServerFlags Option AllowEmptyInput true Option AutoAddDevices true EndSection
Re: [gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
Mick wrote: On 12/12/2009, walt w41...@gmail.com wrote: On 12/12/2009 03:14 PM, Mick wrote: ... I have had mouse, keyboard and synaptics along with evdev in my INPUT_DEVICES and have emerged relative drivers. I am now going to remove them and see what gives. I know nothing about the synaptics driver, so be careful about deleting it. Maybe rename it instead of deleting it? Nope, unmerged it and deleted it from make.conf, then when I emerged xf86-video-ati and evdev all other drivers (mouse, keyboard, synaptics) were brought in as well. I am not clear which /etc/hal/fdi/policy/* files I should have in there ... any ideas? That depends on what hardware you have -- a lot of the stuff that once went into xorg.conf can be put in an fdi file now. Here is an example: Thanks for that. I tried the startx trick. I recall that this would launch my WM (fluxbox), but now all I get is an X session with twm! Has something changed with /etc/rc.conf? Where should I specify fluxbox? No /var/log/xdm.log or other errors were there this time. Trying to start xdm and I keep getting the same old errors: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server (:0.0) and (EE) XKB: No components provided for device Virtual core keyboard. I am running out of things to try now. I don't have a recent enough back up otherwise I would roll back this bad experience. I haven't been following this thread a whole lot but this may help. Do a emerge -epv world and see if you see any changes there. It may be a USE flag change or it may be something else that you notice. It's just a pretend so it shouldn't take but a few minutes. May need to use 'less' or 'more' to scroll through the output easier. I hope that shows something that will help. Dale :-) :-)
Re: [gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
walt wrote: I have these lines in my xorg.conf but I can't remember when or why I put them there. I believe it had something to do with evdev, though. Section ServerFlags Option AllowEmptyInput true Option AutoAddDevices true EndSection If I recall correctly, that disables evdev. I think the first Option disables it. I'm not real sure about the second one. I remember because I did that when I couldn't get evdev to work. Dale :-) :-)
Re: [gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
091213 Mick wrote: I tried the startx trick. It's not a trick ! -- it's the normal sensible way to start X (smile). I recall that this would launch Fluxbox, but now all I get is an X session with twm ! Where should I specify fluxbox? You need a file ~/.xinitrc . Mine is # PP 091002 : for Fluxbox-1.1.1 + KDE 4 xscreensaver kdeinit4 startfluxbox It also starts Xscreensaver the KDE 4 libs, which I want. I just upgraded to Xorg-server 1.6.5-r1 without any problem beyond the need to update 82 pkgs in my own labor-intensive fashion. There was also an update to Hal Lvm2 Util-linux from my weekly 'eix-sync', which I made sure to get done before tackling X. HTH. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] Re: xorg-server upgrading problem
Nikos Chantziaras rea...@arcor.de wrote: I already posted how do downgrade to 1.6.5 correctly :P I have a slightly different case, but related -- I tried the upgrade because I saw a message that the new nvidia drivers would actually work, but xorg-server 1.7.1 would not compile and so I followed the instructions in the bug 290739 comments 3 and 6 and xorg-server 1.6.5 and 1.6.4 which is the one I still have -- neither one will compile. In the 1.6.5 case I get errors in rensize.c. Thanks in advance for any ideas on how to fix. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
[gentoo-user] Re: xorg-server upgrading problem
On 11/09/2009 11:18 PM, Roy Wright wrote: On Nov 9, 2009, at 1:04 AM, Johannes Kimmel wrote: Try to resync and emerge the new eselect-opengl and run eselect opengl set nvidia again. This could fix it, as I had a similar problem. The old eselect did something wrong, but I can't remember exactly because it went somehow long yesterday :) Good catch, but unfortunately it didn't help. I've downgraded the nvidia drivers to 185.18.36-r1 which then loaded glx, but still not dri or dri2. Maybe I need to upgrade the kernel from 2.6.29... BTW, xorg-server-1.6.5 does work with nv drivers, but I need opengl. I'm currently trying to downgrade server to 1.6.3, but that's not compiling. Let's say I'm not very impressed with the xorg ebuild technique of specifying dependencies using =. xorg ebuilds should be holistic based on the xorg-server version. Instead I have to figure out the version masks for each of the dependencies. PITA! I already posted how do downgrade to 1.6.5 correctly :P
Re: [gentoo-user] Re: xorg-server upgrading problem
On Nov 9, 2009, at 3:36 PM, Nikos Chantziaras wrote: On 11/09/2009 11:18 PM, Roy Wright wrote: On Nov 9, 2009, at 1:04 AM, Johannes Kimmel wrote: Try to resync and emerge the new eselect-opengl and run eselect opengl set nvidia again. This could fix it, as I had a similar problem. The old eselect did something wrong, but I can't remember exactly because it went somehow long yesterday :) Good catch, but unfortunately it didn't help. I've downgraded the nvidia drivers to 185.18.36-r1 which then loaded glx, but still not dri or dri2. Maybe I need to upgrade the kernel from 2.6.29... BTW, xorg-server-1.6.5 does work with nv drivers, but I need opengl. I'm currently trying to downgrade server to 1.6.3, but that's not compiling. Let's say I'm not very impressed with the xorg ebuild technique of specifying dependencies using =. xorg ebuilds should be holistic based on the xorg-server version. Instead I have to figure out the version masks for each of the dependencies. PITA! I already posted how do downgrade to 1.6.5 correctly :P Sorry, forgot to mention that I did try those instructions. Didn't help. I'm currently punting, removing all of X from my system, then will start over... Thank you, Roy
[gentoo-user] Re: xorg-server upgrading problem
On 11/09/2009 02:46 AM, Roy Wright wrote: Howdy, I have a home server/htpc (~x86) that I'm finally updating after a few months and I hit an issue with xorg-server. Here's the background: Was at xorg-server-1.6.3 and current sync tried to upgrade to 1.7.1, which failed to compile. In researching on b.g.o., discovered that nvidia has not released a driver yet that will work with 1.7.1, so followed the bug report directions and masked out several packages to prevent 1.7.1 upgrading. I think the bug about ati-drivers should help: http://bugs.gentoo.org/show_bug.cgi?id=290739 From that bug, follow those two comments *exactly*: http://bugs.gentoo.org/show_bug.cgi?id=290739#c3 http://bugs.gentoo.org/show_bug.cgi?id=290739#c6 This should get you to a correctly installed 1.6.5 again.
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
On Fri, 10 Jul 2009 13:47:09 -0500 Dale rdalek1...@gmail.com wrote: What gets me is this, I even did a fresh install on another hard drive, it don't work there either. hal and friends were included from the very start of the install too. Either I am missing something that is not in the guide or it just don't like my hardware. My mouse is a old P/S2 type mouse. It's not even as complicated as a USB thingy. Did you add the acpid, hald and dbus to the default runlevel? -- -- Keith Dart ke...@dartworks.biz ===
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
Keith Dart wrote: On Fri, 10 Jul 2009 13:47:09 -0500 Dale rdalek1...@gmail.com wrote: What gets me is this, I even did a fresh install on another hard drive, it don't work there either. hal and friends were included from the very start of the install too. Either I am missing something that is not in the guide or it just don't like my hardware. My mouse is a old P/S2 type mouse. It's not even as complicated as a USB thingy. Did you add the acpid, hald and dbus to the default runlevel? acpid, nope. The rest, yes. I have never used acpid before either. It seems that I tried that a long time ago and it didn't work. Maybe something else close to that tho. It's been a while. Dale :-) :-)
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
On Fri, Jul 10, 2009 at 10:46 PM, Keith Dartke...@dartworks.biz wrote: On Fri, 10 Jul 2009 20:53:22 -0700 Kevin O'Gorman kogor...@gmail.com wrote: This is NOT the way for Linux to make progress in the desktop wars, folks. Works for me. ;-) But its true that Xorg is making some rapid progress. There's some growing pains. If you are running Gentoo unstable mask (~X) then you are on the bleeding edge of open source development. Therefore occasional breakage is to be expected. File a bug, make it better. If you want stable, then use Ubuntu LTS release, or CentOS. Stable, but boring. ;-) Thanks for the sermon, pastor. I guess. Why did you jump to the conclusion that I am running unstable? I'm not. I never have, though I occasionally (like twice in the 7 years I've been using gentoo) marked a particular package for unstable. So by elimination, the term for what I have should be stable. Why then try to exile me to a distro I don't want? I do, however, pretty much need working. A black screen, dead input devices, and impossibly esoteric config files just don't cut it. (The HAL learning curve is a danger in itself, and is just not worth it to me. I don't expect to touch it for years, which means that when it eventually gets broken I'll have forgotten it completely and have no idea how to proceed safely). I got a solution by disabling HAL in gentoo. And for my broken ubuntu systems, I did indeed go back to LTS, but not so much because of the LT, it's just that 8.04 is the last one that worked. That's the upside of a binary distro -- my November backup was good enough (i.e. it worked), and an overnight update brought everything up to speed and up to snuff. The things that change a lot are all in /home, which was not affected. Hopefully, I can now get on with my summer projects. I'm done with HAL and X. Until next time. ++ kevin -- Kevin O'Gorman, PhD
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
On Friday 10 July 2009, Kevin O'Gorman wrote: On Thu, Jul 9, 2009 at 9:52 PM, Kevin O'Gormankogor...@gmail.com wrote: Okay, I'm re-emerging hal. I was already using gcc-4.1.2. I still have mouse and keyboard emerged, but not mentioned in the xorg.conf. I am coming late to the party here but I not so long ago did this on an old ATI R300 card and and an NVidia FX-5200. All I had to do was to make sure to emerge evdev by: INPUT_DEVICES=keyboard mouse evdev in /etc/make.conf and then comment out the mouse/keyboard stanzas in my existing xorg.conf. And then it worked. If you really feel you need a new video card, I recently got a GeForce 9400 GT. It has 512MB of RAM, is inexpensive and KDE 4.2 performance is very acceptable. HTH -Robin -- -- Robin Atwood. Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst from Mandalay by Rudyard Kipling --
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
090709 Kevin O'Gorman wrote: On Thu, Jul 9, 2009 at 8:51 PM, Dalerdalek1...@gmail.com wrote: If all else fails: x11-base/xorg-server -hal Is there any other advice? A new HAL made no difference. Sigh. I ran into this twice, first on my frontline machine, then on the stand-by. The solution was 'USE=-hal emerge xorg-server', then remerge all drivers. There was a Gentoo help doc re it, which gave this as the simplest option. 'evdev' is a separate matter: you need to include it in your kernel, than you can simplify your drivers. HTH -- ,, SUPPORT ___//___, Philip Webb : purs...@chass.utoronto.ca ELECTRIC /] [] [] [] [] []| Centre for Urban Community Studies TRANSIT`-O--O---' University of Toronto
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
On Fri, Jul 10, 2009 at 4:55 AM, Philip Webbpurs...@ca.inter.net wrote: 090709 Kevin O'Gorman wrote: On Thu, Jul 9, 2009 at 8:51 PM, Dalerdalek1...@gmail.com wrote: If all else fails: x11-base/xorg-server -hal Is there any other advice? A new HAL made no difference. Sigh. I ran into this twice, first on my frontline machine, then on the stand-by. The solution was 'USE=-hal emerge xorg-server', then remerge all drivers. There was a Gentoo help doc re it, which gave this as the simplest option. 'evdev' is a separate matter: you need to include it in your kernel, than you can simplify your drivers. HTH Evdev has been included in my kernels throughout this mess. It hasn't helped. The Gentoo doc on the upgrade was a bit scetchy about configuring HAL; now that I find that disabling HAL in xorg is the solution, I suspect that the underlying problem is HAL configuration. After all, there's nothing at all special about my mouse or keyboard. Why should we have to configure HAL manually? Since the stone ages, Linux installations have determined what keyboard we have and have set things up for us. How different can PS/2 or USB mice be? SO: if anyone succeeded with xorg and HAL, with a USA keyboard and a wheel mouse, would please tell me about their HAL config, I'd sure love to see it. ++ kevin -- Kevin O'Gorman, PhD
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
Kevin O'Gorman wrote: On Fri, Jul 10, 2009 at 4:55 AM, Philip Webbpurs...@ca.inter.net wrote: 090709 Kevin O'Gorman wrote: On Thu, Jul 9, 2009 at 8:51 PM, Dalerdalek1...@gmail.com wrote: If all else fails: x11-base/xorg-server -hal Is there any other advice? A new HAL made no difference. Sigh. I ran into this twice, first on my frontline machine, then on the stand-by. The solution was 'USE=-hal emerge xorg-server', then remerge all drivers. There was a Gentoo help doc re it, which gave this as the simplest option. 'evdev' is a separate matter: you need to include it in your kernel, than you can simplify your drivers. HTH Evdev has been included in my kernels throughout this mess. It hasn't helped. The Gentoo doc on the upgrade was a bit scetchy about configuring HAL; now that I find that disabling HAL in xorg is the solution, I suspect that the underlying problem is HAL configuration. After all, there's nothing at all special about my mouse or keyboard. Why should we have to configure HAL manually? Since the stone ages, Linux installations have determined what keyboard we have and have set things up for us. How different can PS/2 or USB mice be? SO: if anyone succeeded with xorg and HAL, with a USA keyboard and a wheel mouse, would please tell me about their HAL config, I'd sure love to see it. ++ kevin Same here. I have a old keyboard that has been around for a lng time. It's a Dell Quietkey. My mouse is a decent Logitech that cost about $20.00 or so a few years ago. It worked with Mandrake and Gentoo all this time then someone comes up with a mouse trap that don't like it. I'm with you. Dale :-) :-)
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
On Friday 10 July 2009 17:43:44 Kevin O'Gorman wrote: On Fri, Jul 10, 2009 at 4:55 AM, Philip Webbpurs...@ca.inter.net wrote: 090709 Kevin O'Gorman wrote: On Thu, Jul 9, 2009 at 8:51 PM, Dalerdalek1...@gmail.com wrote: If all else fails: x11-base/xorg-server -hal Is there any other advice? A new HAL made no difference. Sigh. I ran into this twice, first on my frontline machine, then on the stand-by. The solution was 'USE=-hal emerge xorg-server', then remerge all drivers. There was a Gentoo help doc re it, which gave this as the simplest option. 'evdev' is a separate matter: you need to include it in your kernel, than you can simplify your drivers. HTH Evdev has been included in my kernels throughout this mess. It hasn't helped. The Gentoo doc on the upgrade was a bit scetchy about configuring HAL; now that I find that disabling HAL in xorg is the solution, I suspect that the underlying problem is HAL configuration. After all, there's nothing at all special about my mouse or keyboard. Why should we have to configure HAL manually? Since the stone ages, Linux installations have determined what keyboard we have and have set things up for us. How different can PS/2 or USB mice be? SO: if anyone succeeded with xorg and HAL, with a USA keyboard and a wheel mouse, would please tell me about their HAL config, I'd sure love to see it. I run latest unstable here with a regular USA layout on a Dell XPS M1530 with nvidia driver, hal and evdev. The HAL config is empty apart from a policy file for a touch pad, and it's a dual-screen setup. Here's my xorg.conf: # egrep -v '^$|^#' /etc/X11/xorg.conf Section ServerLayout Identifier Layout0 Screen 0 Screen0 0 0 EndSection Section Files EndSection Section Module Load dbe Load extmod Load glx EndSection Section ServerFlags Option Xinerama 0 EndSection Section Monitor # HorizSync source: edid, VertRefresh source: edid Identifier Monitor0 VendorName Unknown ModelName Samsung SyncMaster HorizSync 30.0 - 81.0 VertRefresh 56.0 - 75.0 Option DPMS EndSection Section Device Identifier Device0 Driver nvidia VendorName NVIDIA Corporation BoardName GeForce 8600M GT EndSection Section Screen Identifier Screen0 Device Device0 MonitorMonitor0 DefaultDepth24 Option NoLogo True Option TwinView 1 Option TwinViewXineramaInfoOrder DFP-0 Option metamodes CRT: nvidia-auto-select @1440x900 +1920+0, DFP: nvidia-auto-select +0+0 SubSection Display Depth 24 EndSubSection EndSection It all JustWorks for me, I assume in my case at least it's working as designed. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
Alan McKinnon wrote: On Friday 10 July 2009 17:43:44 Kevin O'Gorman wrote: On Fri, Jul 10, 2009 at 4:55 AM, Philip Webbpurs...@ca.inter.net wrote: 090709 Kevin O'Gorman wrote: On Thu, Jul 9, 2009 at 8:51 PM, Dalerdalek1...@gmail.com wrote: If all else fails: x11-base/xorg-server -hal Is there any other advice? A new HAL made no difference. Sigh. I ran into this twice, first on my frontline machine, then on the stand-by. The solution was 'USE=-hal emerge xorg-server', then remerge all drivers. There was a Gentoo help doc re it, which gave this as the simplest option. 'evdev' is a separate matter: you need to include it in your kernel, than you can simplify your drivers. HTH Evdev has been included in my kernels throughout this mess. It hasn't helped. The Gentoo doc on the upgrade was a bit scetchy about configuring HAL; now that I find that disabling HAL in xorg is the solution, I suspect that the underlying problem is HAL configuration. After all, there's nothing at all special about my mouse or keyboard. Why should we have to configure HAL manually? Since the stone ages, Linux installations have determined what keyboard we have and have set things up for us. How different can PS/2 or USB mice be? SO: if anyone succeeded with xorg and HAL, with a USA keyboard and a wheel mouse, would please tell me about their HAL config, I'd sure love to see it. I run latest unstable here with a regular USA layout on a Dell XPS M1530 with nvidia driver, hal and evdev. The HAL config is empty apart from a policy file for a touch pad, and it's a dual-screen setup. Here's my xorg.conf: # egrep -v '^$|^#' /etc/X11/xorg.conf Section ServerLayout Identifier Layout0 Screen 0 Screen0 0 0 EndSection Section Files EndSection Section Module Load dbe Load extmod Load glx EndSection Section ServerFlags Option Xinerama 0 EndSection Section Monitor # HorizSync source: edid, VertRefresh source: edid Identifier Monitor0 VendorName Unknown ModelName Samsung SyncMaster HorizSync 30.0 - 81.0 VertRefresh 56.0 - 75.0 Option DPMS EndSection Section Device Identifier Device0 Driver nvidia VendorName NVIDIA Corporation BoardName GeForce 8600M GT EndSection Section Screen Identifier Screen0 Device Device0 MonitorMonitor0 DefaultDepth24 Option NoLogo True Option TwinView 1 Option TwinViewXineramaInfoOrder DFP-0 Option metamodes CRT: nvidia-auto-select @1440x900 +1920+0, DFP: nvidia-auto-select +0+0 SubSection Display Depth 24 EndSubSection EndSection It all JustWorks for me, I assume in my case at least it's working as designed. What gets me is this, I even did a fresh install on another hard drive, it don't work there either. hal and friends were included from the very start of the install too. Either I am missing something that is not in the guide or it just don't like my hardware. My mouse is a old P/S2 type mouse. It's not even as complicated as a USB thingy. Dale :-) :-)
[gentoo-user] Re: xorg-server mouse and keyboard woes
On 07/10/2009 01:29 AM, Helmut Jarausch wrote: On 9 Jul, Kevin O'Gorman wrote: I had tried holding back on xorg-server 1.5, but somewhere in May at least one package got past my version limits and X broke. Rather than to try to revert, I thought surely by now, X would be fixed. Sigh. In another thread, after spending 2 months without a working X server, I got KDM to start. But without the mouse and keyboard. The nice folks who got me that far warned and comisserated thus: I had a similar problem. Finally I added hald to boot Was hald in 'default' before that? rc-update add hald boot and rebooted. From now on Xorg 1.5 and now 1.6 work just fine with hal. I wonder why this hasn't been done/checked by the xorg-server ebuild. Interesting, I never noticed until now that I have hald in 'default' like Kevin and yet I have no problems with input devices. I'm using only USB mice but PS/2 keyboard with X+hal and only evdev, not keyboard or mouse drivers. No InputDevice sections at all in xorg.conf. I'm wondering if this could be related to APCI or BIOS somehow, which seems to be a major source of different bugs from machine-to-machine. Dunno, but it's frustrating to watch you guys have so much trouble with this problem. Kevin, I have two mice, one very non-standard and the other bog-standard as the Brits like to say. The Microsoft Basic Optical Mouse has two buttons and a wheel, and it works well under evdev except that I like to use Emulate3Buttons. My InputDevice sections are gone completely, as I mentioned, so I wrote a new conf file /etc/hal/fdi/policy/10-emulate3buttons.fdi: ?xml version=1.0 encoding=ISO-8859-1? deviceinfo version=0.2 device match key=info.capabilities contains=input.mouse merge key=input.x11_options.Emulate3Buttons type=stringtrue/merge /match /device /deviceinfo I just edited the system input file from /usr/share/hal/fdi/policy after studying the sytax for awhile, and it worked :o) Basically, anything you'd put in an InputDevice section of xorg.conf is transformed into the input.x11_options syntax above. I made another file for my non-standard mouse adding things like EmulateWheel but the syntax was identical to above.
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
Mine is working fine also, I did have to rebuild all the drivers after every update, using 1.6.1.901-r5 currently; This is a desktop, I have nothing in /etc/hal/fdi/policy/ david [02:54 PM] opteron ~ $ ls /usr/lib64/xorg/modules/input/ evdev_drv.so kbd_drv.so mouse_drv.so Here is xorg.conf and Xorg.0.log http://dwabbott.com/xorg/ I use a wireless usb keyboard/mouse Both dbus and hald are in runlevel default I read this over plus the 1.5 guide; http://dberkholz.wordpress.com/2009/02/26/xorg-server-16-preview-in-x11-overlay/ I feel your pain. hope something can help. -- Powered by Gentoo GNU/Linux http://linuxcrazy.com
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
On Fri, Jul 10, 2009 at 11:50 AM, waltw41...@gmail.com wrote: On 07/10/2009 01:29 AM, Helmut Jarausch wrote: On 9 Jul, Kevin O'Gorman wrote: I had tried holding back on xorg-server 1.5, but somewhere in May at least one package got past my version limits and X broke. Rather than to try to revert, I thought surely by now, X would be fixed. Sigh. In another thread, after spending 2 months without a working X server, I got KDM to start. But without the mouse and keyboard. The nice folks who got me that far warned and comisserated thus: I had a similar problem. Finally I added hald to boot Was hald in 'default' before that? rc-update add hald boot and rebooted. From now on Xorg 1.5 and now 1.6 work just fine with hal. I wonder why this hasn't been done/checked by the xorg-server ebuild. Interesting, I never noticed until now that I have hald in 'default' like Kevin and yet I have no problems with input devices. I'm using only USB mice but PS/2 keyboard with X+hal and only evdev, not keyboard or mouse drivers. No InputDevice sections at all in xorg.conf. I'm wondering if this could be related to APCI or BIOS somehow, which seems to be a major source of different bugs from machine-to-machine. Dunno, but it's frustrating to watch you guys have so much trouble with this problem. Kevin, I have two mice, one very non-standard and the other bog-standard as the Brits like to say. The Microsoft Basic Optical Mouse has two buttons and a wheel, and it works well under evdev except that I like to use Emulate3Buttons. My InputDevice sections are gone completely, as I mentioned, so I wrote a new conf file /etc/hal/fdi/policy/10-emulate3buttons.fdi: ?xml version=1.0 encoding=ISO-8859-1? deviceinfo version=0.2 device match key=info.capabilities contains=input.mouse merge key=input.x11_options.Emulate3Buttons type=stringtrue/merge /match /device /deviceinfo I just edited the system input file from /usr/share/hal/fdi/policy after studying the sytax for awhile, and it worked :o) Basically, anything you'd put in an InputDevice section of xorg.conf is transformed into the input.x11_options syntax above. I made another file for my non-standard mouse adding things like EmulateWheel but the syntax was identical to above. Well, thanks for the commisseration. I put -hal on xorg-xerver in packages.use, and all is well. There's little chance I'm going to throw more time into this particular hole. I have to spend it on my Ubuntu system, which was also hosed by an xorg upgrade: I'm reverting that one to a year-old LTS install that I can rely on for at least another year. This is NOT the way for Linux to make progress in the desktop wars, folks. ++ kevin -- Kevin O'Gorman, PhD
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
On Fri, 10 Jul 2009 20:53:22 -0700 Kevin O'Gorman kogor...@gmail.com wrote: This is NOT the way for Linux to make progress in the desktop wars, folks. Works for me. ;-) But its true that Xorg is making some rapid progress. There's some growing pains. If you are running Gentoo unstable mask (~X) then you are on the bleeding edge of open source development. Therefore occasional breakage is to be expected. File a bug, make it better. If you want stable, then use Ubuntu LTS release, or CentOS. Stable, but boring. ;-) -- -- Keith Dart ke...@dartworks.biz ===
[gentoo-user] Re: xorg-server mouse and keyboard woes
Kevin O'Gorman kogorman at gmail.com writes: 'emerge -e1 world' did the trick Okay, I was hoping for variable mileage, but maybe no dice. Have you rebuilt HAL? It might help I have rebuilt version hal-0.5.11-r9 try to get back to what you had before your last (broken) upgrade. Make sure you are using gcc-4.1.2, as 4.3.2 is borked (many folks have different issues) hth, James
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
James wrote: Kevin O'Gorman kogorman at gmail.com writes: 'emerge -e1 world' did the trick Okay, I was hoping for variable mileage, but maybe no dice. Have you rebuilt HAL? It might help I have rebuilt version hal-0.5.11-r9 try to get back to what you had before your last (broken) upgrade. Make sure you are using gcc-4.1.2, as 4.3.2 is borked (many folks have different issues) hth, James If all else fails: x11-base/xorg-server -hal Put that in package.use and re-emerge xorg-server. You may have to re-emerge mouse and keyboard too. Dale :-) :-)
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
On Thu, Jul 9, 2009 at 8:51 PM, Dalerdalek1...@gmail.com wrote: James wrote: Kevin O'Gorman kogorman at gmail.com writes: 'emerge -e1 world' did the trick Okay, I was hoping for variable mileage, but maybe no dice. Have you rebuilt HAL? It might help I have rebuilt version hal-0.5.11-r9 try to get back to what you had before your last (broken) upgrade. Make sure you are using gcc-4.1.2, as 4.3.2 is borked (many folks have different issues) hth, James If all else fails: x11-base/xorg-server -hal Put that in package.use and re-emerge xorg-server. You may have to re-emerge mouse and keyboard too. Dale Okay, I'm re-emerging hal. I was already using gcc-4.1.2. I still have mouse and keyboard emerged, but not mentioned in the xorg.conf. Crossing my fingers. Is there any other advice? Is there any hope? ++ kevin -- Kevin O'Gorman, PhD
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
Kevin O'Gorman wrote: On Thu, Jul 9, 2009 at 8:51 PM, Dalerdalek1...@gmail.com wrote: James wrote: Kevin O'Gorman kogorman at gmail.com writes: 'emerge -e1 world' did the trick Okay, I was hoping for variable mileage, but maybe no dice. Have you rebuilt HAL? It might help I have rebuilt version hal-0.5.11-r9 try to get back to what you had before your last (broken) upgrade. Make sure you are using gcc-4.1.2, as 4.3.2 is borked (many folks have different issues) hth, James If all else fails: x11-base/xorg-server -hal Put that in package.use and re-emerge xorg-server. You may have to re-emerge mouse and keyboard too. Dale Okay, I'm re-emerging hal. I was already using gcc-4.1.2. I still have mouse and keyboard emerged, but not mentioned in the xorg.conf. Crossing my fingers. Is there any other advice? Is there any hope? ++ kevin If you find yourself without a keyboard or mouse and can't get back to a console, press and hold alt + sysreq then hit R and E. I did this the other day and it took me back to a console. Since I have yet to get xorg and hal to work, good luck. Dale :-) :-)
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
On Thu, Jul 9, 2009 at 9:52 PM, Kevin O'Gormankogor...@gmail.com wrote: On Thu, Jul 9, 2009 at 8:51 PM, Dalerdalek1...@gmail.com wrote: James wrote: Kevin O'Gorman kogorman at gmail.com writes: 'emerge -e1 world' did the trick Okay, I was hoping for variable mileage, but maybe no dice. Have you rebuilt HAL? It might help I have rebuilt version hal-0.5.11-r9 try to get back to what you had before your last (broken) upgrade. Make sure you are using gcc-4.1.2, as 4.3.2 is borked (many folks have different issues) hth, James If all else fails: x11-base/xorg-server -hal Put that in package.use and re-emerge xorg-server. You may have to re-emerge mouse and keyboard too. Dale Okay, I'm re-emerging hal. I was already using gcc-4.1.2. I still have mouse and keyboard emerged, but not mentioned in the xorg.conf. Crossing my fingers. Is there any other advice? Is there any hope? A new HAL made no difference. Sigh. Another option occurs to me: get a new video card and stop using the onboard one. I've barely paid any attention to the threads about ATI vs NVIDIA, and don't know if there are any others worth considering. Care to make a suggestion for someone who rarely (read: almost never) plays games or does other work that stress a video card, and just wants the stuff to work? In current machines, it would be a PCI-X (not PCI-E) card. ++ kevin -- Kevin O'Gorman, PhD
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
On Thu, Jul 9, 2009 at 10:02 PM, Dalerdalek1...@gmail.com wrote: Kevin O'Gorman wrote: On Thu, Jul 9, 2009 at 8:51 PM, Dalerdalek1...@gmail.com wrote: James wrote: Kevin O'Gorman kogorman at gmail.com writes: 'emerge -e1 world' did the trick Okay, I was hoping for variable mileage, but maybe no dice. Have you rebuilt HAL? It might help I have rebuilt version hal-0.5.11-r9 try to get back to what you had before your last (broken) upgrade. Make sure you are using gcc-4.1.2, as 4.3.2 is borked (many folks have different issues) hth, James If all else fails: x11-base/xorg-server -hal Put that in package.use and re-emerge xorg-server. You may have to re-emerge mouse and keyboard too. Dale Okay, I'm re-emerging hal. I was already using gcc-4.1.2. I still have mouse and keyboard emerged, but not mentioned in the xorg.conf. Crossing my fingers. Is there any other advice? Is there any hope? ++ kevin If you find yourself without a keyboard or mouse and can't get back to a console, press and hold alt + sysreq then hit R and E. I did this the other day and it took me back to a console. Since I have yet to get xorg and hal to work, good luck. Dale Thanks. Ctl-Alt-BS is still working for me. I'm now rebuilding xorg-server, xf86-input-mouse and xf86-input-keyboard with -hal. ++ kevin -- Kevin O'Gorman, PhD
Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
Kevin O'Gorman wrote: A new HAL made no difference. Sigh. Another option occurs to me: get a new video card and stop using the onboard one. I've barely paid any attention to the threads about ATI vs NVIDIA, and don't know if there are any others worth considering. Care to make a suggestion for someone who rarely (read: almost never) plays games or does other work that stress a video card, and just wants the stuff to work? In current machines, it would be a PCI-X (not PCI-E) card. ++ kevin I have a old FX-5200 and it does all right. I tested KDE 4 the other day, it is not the fastest thing on that. I'm not sure if it is a setting on my part or just needs a better card. I'm on the old PCI stuff too. Dale :-) :-)
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
Mark Knecht ha scritto: No, I need a new kernel also. The kernel on this machine is 2 years old. Also, I have about a dozen packages masked so I've unmasked those and will need to get the whole machine up to date. There is something I didn't understand at all in this thread. Why did you need to update the machine at all? Did you badly need some support for new video formats or performance improvement? Otherwise I really don't see the point of upgrading it. I see the point of upgrading a desktop or server system (yet my desktop kernel is 1.5 years old and I'm fine), but a MythTV box looks like an appliance that once working , you touch no more. m.
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On Thu, Jun 25, 2009 at 1:47 AM, bnbrullonu...@gmail.com wrote: Mark Knecht ha scritto: No, I need a new kernel also. The kernel on this machine is 2 years old. Also, I have about a dozen packages masked so I've unmasked those and will need to get the whole machine up to date. There is something I didn't understand at all in this thread. Why did you need to update the machine at all? Did you badly need some support for new video formats or performance improvement? Otherwise I really don't see the point of upgrading it. I see the point of upgrading a desktop or server system (yet my desktop kernel is 1.5 years old and I'm fine), but a MythTV box looks like an appliance that once working , you touch no more. m. With the switch to digital TV I had to buy new hardware to record. Even though this machine is only a frontend it started having trouble that my other Gentoo desktop PCs were not. I updated everything I could on this machine without updating the video driver, the kernel and xorg-x11. Since I couldn't change the kernel or the video driver I chose to update xorg-x11 and hit the wall. I don't do these things for fun. It's OK with me if a machine never gets updated but with MythTV they change data formats, database formats, communication protocols and break things along the way WRT remote frontends that haven't been updated, or that's my experience. I figured that is what happened here. Anyway, that's all done. The machine is updated and close to clean. Still have to do a grub update but that can wait. I'm having a few problems with things like eselect opengl set 1 complaining about libraries and things so I'll have to work on that before I push forward. Hope that explains a bit anyway. Cheers, Mark
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On Tue, 23 Jun 2009 18:42:11 -0700, Mark Knecht wrote: You can tell before you perform the update that the old version is no longer in portage, How? I run eix-sync and at that point it's no longer in /usr/portage/distfiles. AFAIK, eix-sync doesn't touch $DISTDIR. If it does, that's a very good reason to not use it. Am I supposed to study what eix-sync is going to do before it does it for the 800 or so packages that are on my system? Fat chance anyone does that on a regular and thorough basis. Or do you mean let eix-sync happen, then study emerge -pvDuN and somehow determine that it's going to delete one out of 100 packages that it's going to update? How often do you update? I have myth front and backends, running mostly stable and I doubt they get that many updates a year. Gentoo gives you responsibility for maintaining your machines. You don't get to hand that back. emerge -avuDN does exactlky what you tell it to do, whether that's what you wanted or not, it is your responsibility to ensure that the two match. then you can copy the ebuild from /var/db/pkg to your overlay (and run quickpkg for speed) before updating. Remember that nothing is ever truly removed from portage, it is still in the CVS attic, What would be handy would be a script that you run after you sync. If a package you have installed is no longer in the tree, it copies the ebuild to an overlay. Ebuild and the source code package also? The source code is still in $DISTDIR, still on the upstream server and probably still on the mirrors for a while. (Sarcastically) What's an 'personal' overlay? You don't need one to install Gentoo. You don't seem to need one until it's too late and you have to somehow create it and deal with this after it's become a problem. Creating and setting up your own overlay is as complex as copying one line from make.conf.example to make.conf. My problem was I'm already toast at the dinner table tonight. I told the family that the machine doesn't work anymore and now it's not clear I'm allowed to sleep here anymore. Hard to build an overlay if I'm locked out. What, no SSH? ;-) A different short-term solution might be to find another old junker machine that is supported, building it out of junker parts. This would be good if I had any certainty that when the work was completed portage wouldn't immediately create the same havok. Your real problem is that you are using outdated and unsupported hardware. Not unsupported by Gentoo but unsupported by ATI. Incidentally, have you filed a bug report about this, if the only available driver for your hardware has been removed from portage, you should post a bug asking it to be reinstated. -- Neil Bothwick I laugh in the face of danger, then I hide until it goes away signature.asc Description: PGP signature
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On Wednesday 24 June 2009 02:28:50 Neil Bothwick wrote: Those who can, do. Those who cannot, teach. Those who cannot teach, HACK! No, no - those who can't teach teach teachers. Or so my father used to say, from what he said had been bitter experience. -- Rgds Peter
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On Tue, Jun 23, 2009 at 7:06 PM, Mark Knechtmarkkne...@gmail.com wrote: Is xorg-server-1.1.1 completely gone and I'm hosed? I'm not finding it on my my machine. The only variations on that theme seem to be in /var/db/pkg. No tar files, just other programming junk. http://sources.gentoo.org/ is your friend :) Specifically: http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo-x86/x11-base/xorg-server/xorg-server-1.1.1-r5.ebuild Every ebuild that has ever been in portage is available on CVS or via the web viewcvs interface above. You'll probably need the patches for this version from http://sources.gentoo.org/viewcvs.py/gentoo-x86/x11-base/xorg-server/files/?hideattic=0 as well as whatever other split-ebuilds may be required to support this version. It looks like it was obsoleted and deleted from the main portage tree almost 2 years ago. Download them, put them in your local overlay, mask newer-than-1.1 versions in your /etc/portage/* and hopefully your problem will be solved. :)
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On Wed, Jun 24, 2009 at 12:46 AM, Neil Bothwickn...@digimed.co.uk wrote: On Tue, 23 Jun 2009 18:42:11 -0700, Mark Knecht wrote: SNIP A different short-term solution might be to find another old junker machine that is supported, building it out of junker parts. This would be good if I had any certainty that when the work was completed portage wouldn't immediately create the same havok. Your real problem is that you are using outdated and unsupported hardware. Not unsupported by Gentoo but unsupported by ATI. Incidentally, have you filed a bug report about this, if the only available driver for your hardware has been removed from portage, you should post a bug asking it to be reinstated. -- Neil Bothwick I laugh in the face of danger, then I hide until it goes away Unfortunately for me: 1) It absolutely isn't that the hardware is unsupported, it's that a *feature* of the hardware (TV Out S-Video) became unsupported. The machine works (AFAIK) with Gentoo. It boots, it probably runs X just fine using the VGA output. It's that the S-Video output feature (TV Out) has become unsupported by ati-driver. Who would have ever guessed when you purchased a machine that uses and ATI chipset with a built-in ATI graphics controller that it would be ATI that chose to obsolete it? Amazing... 2) Following your Bugzilla suggestion about asking that it be put back into portage to it's logical conclusion and it gets scary. Here's the paraphrased request: a) I need ati-driver-8.28.8 put back into portage because it's the last driver that supports TV out for the 9100 IGP chipset. b) Unfortunately I need 2.6.19 added back into portage because it's the last kernel that ati-driver-8.28.8 runs on. c) Because all this old stuff doesn't work on the new xorg-server I need xorg-server-1.1.1 to remain in portage. Multiply this sort of requirement up by whatever additional packages are required to get the stuff above actually working and it looks unlikely, 'eh? Granted, I don't need the kernel because I can just get that and manage it myself. (I.e. - I don't need gentoo-sources) I really think this is what a personal overlay is for, but as I've said for years, it's hard to build an overlay when you don't know what needs to be in it until it's been removed. And yes, *something* has removed these files, at least from my distfiles directory and I'm pretty confident it wasn't me by hand because the machines all have disk space which is the only reason I ever remove packages from there by hand. There are still things lurking around in /var/db/pkgs or whatever it's called so maybe I can learn how to create a personal overlay form what's left and then go look elsewhere for other things required. Anyway, thanks for the inputs. I'm not sure what I'm going to do next other than take some time and figure things out. As always I appreciate your help. Cheers, Mark
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On Wed, 24 Jun 2009 13:17:12 -0700, Mark Knecht wrote: 1) It absolutely isn't that the hardware is unsupported, it's that a *feature* of the hardware (TV Out S-Video) became unsupported. And the S-Video output is part of the hardware, so you do have unsupported hardware. 2) Following your Bugzilla suggestion about asking that it be put back into portage to it's logical conclusion and it gets scary. Here's the paraphrased request: a) I need ati-driver-8.28.8 put back into portage because it's the last driver that supports TV out for the 9100 IGP chipset. b) Unfortunately I need 2.6.19 added back into portage because it's the last kernel that ati-driver-8.28.8 runs on. c) Because all this old stuff doesn't work on the new xorg-server I need xorg-server-1.1.1 to remain in portage. When you put it like that... but there's no harm in asking. I really think this is what a personal overlay is for, but as I've said for years, it's hard to build an overlay when you don't know what needs to be in it until it's been removed. I think that whenever you start masking newer versions of a package to force portage to stay with the older ones, you should consider copying them to an overlay. Everything is removed eventually and if you can't keep up with updates, you preferred version will disappear at some time. It's not the end of the world as you can still get the files from the CVS attic, it's just that copying them in advance saves some work. And yes, *something* has removed these files, at least from my distfiles directory and I'm pretty confident it wasn't me by hand because the machines all have disk space which is the only reason I ever remove packages from there by hand. eix-sync makes no mention of cleaning $DISTDIR, either in its man page or --help output, so I reckon you're running something else to do this. Maybe eclean in a postsync script. What do you have in /etc/portage/postsync.d? You could put a script in here that runs rsync -a /usr/portage/ /usr/portage.bak/ which would mean you have your own portage attic and could retrieve any deleted ebuild whenever you want. -- Neil Bothwick Anything is possible if you don't know what you are talking about. signature.asc Description: PGP signature
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On Wednesday 24 June 2009 22:17:12 Mark Knecht wrote: I really think this is what a personal overlay is for, but as I've said for years, it's hard to build an overlay when you don't know what needs to be in it until it's been removed. And yes, something has removed these files, at least from my distfiles directory and I'm pretty confident it wasn't me by hand because the machines all have disk space which is the only reason I ever remove packages from there by hand. There are still things lurking around in /var/db/pkgs or whatever it's called so maybe I can learn how to create a personal overlay form what's left and then go look elsewhere for other things required. So why don't you do exactly that? I can't help but think when reading this thread that you are going round in circles, wondering if you should create a personal overlay, when you already know that the only possible solution IS a personal overlay. It's documented in the gentoo docs. Briefly: Create a directory somewhere for your stuff and include it in PORTDIR_OVERLAY in /etc/make.conf. If the current versions of ebuilds you need are currently installed, the ebuilds will be in /var/db/pkg so copy them to your overlay directory retaining the category/package structure. If not currently installed, get them from gentoo's cvs. Look inside each ebuild, see what it's DEPENDS are, make sure you have suitable ebuilds in your overlay. Rinse, repeat. It's fiddly, but not hard to do. Mask stuff using normal portage methods to make sure you don't upgrade to something incompatible. emerge world and let rip. Stop playing dixie with the idea and just do it, man! -- alan dot mckinnon at gmail dot com
RE: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
I havent been following this thread but have you checked the open source drivers? New features are always being ported in. The two options are; - Radeon driver (module is named ati) - Radeonhd driver (module is named radeon) Check out the current features here http://www.x.org/wiki/RadeonFeature all boxes are for the radeon/ati driver unless the box contains (RHD, in which case it's the radeonhd/radeon driver). In particular TV out should work on R100/R200/R300 based cards.
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On Wed, Jun 24, 2009 at 5:08 PM, Adam Carteradam.car...@optus.com.au wrote: I havent been following this thread but have you checked the open source drivers? New features are always being ported in. The two options are; - Radeon driver (module is named ati) - Radeonhd driver (module is named radeon) Check out the current features here http://www.x.org/wiki/RadeonFeature all boxes are for the radeon/ati driver unless the box contains (RHD, in which case it's the radeonhd/radeon driver). In particular TV out should work on R100/R200/R300 based cards. It's a great question and one I'd like to answer. Someone else suggested this yesterday I think. Thanks for suggesting I get back to it. I am scanning the /var/log/Xorg.0.log looking for info on what chip this is. I'm not finding anything that says what Radeon family it's part of. lspci tells me what I posted here already - that it's part of the IGP 9100 family. I found this page at the AMD/ATI site but I suspect it's for a newer version of the chipset: http://ati.amd.com/products/radeon9100igp/features.html I'm going to pursue this with more dedication as it is really the only current path I've heard of so far that gives me a chance to stay current with Gentoo. What VIDEO_DEVICES setting might one use to get this driver called up? Either ati or radeon and check that it installs Open Source? It is a bunch of work, but it would be great if I can use it. Thanks, Mark DesertFlower ~ # lspci -vv SNIP 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon 9100 IGP (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 8107 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 (2000ns min), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 11 Region 0: Memory at e800 (32-bit, prefetchable) [size=128M] Region 1: I/O ports at d000 [size=256] Region 2: Memory at fde0 (32-bit, non-prefetchable) [size=64K] Expansion ROM at fdd0 [disabled] [size=128K] Capabilities: [58] AGP version 3.0 Status: RQ=256 Iso- ArqSz=0 Cal=7 SBA+ ITACoh- GART64- HTrans- 64bit+ FW+ AGP3+ Rate=x4,x8 Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=none Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
[gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On 06/25/2009 03:46 AM, Mark Knecht wrote: On Wed, Jun 24, 2009 at 5:08 PM, Adam Carteradam.car...@optus.com.au wrote: I havent been following this thread but have you checked the open source drivers? New features are always being ported in. The two options are; - Radeon driver (module is named ati) - Radeonhd driver (module is named radeon) Check out the current features here http://www.x.org/wiki/RadeonFeature all boxes are for the radeon/ati driver unless the box contains (RHD, in which case it's the radeonhd/radeon driver). In particular TV out should work on R100/R200/R300 based cards. [...] I am scanning the /var/log/Xorg.0.log looking for info on what chip this is. I'm not finding anything that says what Radeon family it's part of. lspci tells me what I posted here already - that it's part of the IGP 9100 family. I found this page at the AMD/ATI site but I suspect it's for a newer version of the chipset: http://ati.amd.com/products/radeon9100igp/features.html That's an R200 chip. http://en.wikipedia.org/wiki/Radeon_R200
RE: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
I am scanning the /var/log/Xorg.0.log looking for info on what chip this is. I'm not finding anything that says what Radeon family it's part of. lspci tells me what I posted here already - that it's part of the IGP 9100 family. http://en.wikipedia.org/wiki/Comparison_of_ATI_Graphics_Processing_Units says its an R200. I found this page at the AMD/ATI site but I suspect it's for a newer version of the chipset: http://ati.amd.com/products/radeon9100igp/features.html I'm going to pursue this with more dedication as it is really the only current path I've heard of so far that gives me a chance to stay current with Gentoo. What VIDEO_DEVICES setting might one use to get this driver called up? Either ati or radeon and check that it installs Open Source? So you want the radeon/ati driver, the package name is xf86-video-ati, so I guess that means you want ati in VIDEO_DEVICES. It is a bunch of work, but it would be great if I can use it. I thought emerge xf86-video-ati, then swapping Driver flgrx to Driver radeon in xorg.conf was all that is required??
[gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On 06/25/2009 04:04 AM, Adam Carter wrote: What VIDEO_DEVICES setting might one use to get this driver called up? Either ati or radeon and check that it installs Open Source? So you want the radeon/ati driver, the package name is xf86-video-ati, so I guess that means you want ati in VIDEO_DEVICES. It's radeon in recent X.Org, not ati. Not sure when that changed. Probably with xorg-server 1.5.
RE: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
So you want the radeon/ati driver, the package name is xf86-video-ati, so I guess that means you want ati in VIDEO_DEVICES. It's radeon in recent X.Org, not ati. Not sure when that changed. Probably with xorg-server 1.5. Damn - I had checked the /usr/portage/x11-drivers directory and the packages are called -ati and -radeonhd, so I assumed that's what would be passed via the variable, but of course it's the modules name, so flgrx installs ati-drivers radeon installs xf86-video-ati radeonhd installs xf86-video-radeonhd
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On Wed, Jun 24, 2009 at 5:59 PM, Nikos Chantziarasrea...@arcor.de wrote: On 06/25/2009 03:46 AM, Mark Knecht wrote: On Wed, Jun 24, 2009 at 5:08 PM, Adam Carteradam.car...@optus.com.au wrote: I havent been following this thread but have you checked the open source drivers? New features are always being ported in. The two options are; - Radeon driver (module is named ati) - Radeonhd driver (module is named radeon) Check out the current features here http://www.x.org/wiki/RadeonFeature all boxes are for the radeon/ati driver unless the box contains (RHD, in which case it's the radeonhd/radeon driver). In particular TV out should work on R100/R200/R300 based cards. [...] I am scanning the /var/log/Xorg.0.log looking for info on what chip this is. I'm not finding anything that says what Radeon family it's part of. lspci tells me what I posted here already - that it's part of the IGP 9100 family. I found this page at the AMD/ATI site but I suspect it's for a newer version of the chipset: http://ati.amd.com/products/radeon9100igp/features.html That's an R200 chip. http://en.wikipedia.org/wiki/Radeon_R200 Thanks. That would be good news as the new ATI driver says TV Out is supported. Building a new kernel now. cheers, Mark
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On Wed, Jun 24, 2009 at 6:04 PM, Adam Carteradam.car...@optus.com.au wrote: I am scanning the /var/log/Xorg.0.log looking for info on what chip this is. I'm not finding anything that says what Radeon family it's part of. lspci tells me what I posted here already - that it's part of the IGP 9100 family. http://en.wikipedia.org/wiki/Comparison_of_ATI_Graphics_Processing_Units says its an R200. I found this page at the AMD/ATI site but I suspect it's for a newer version of the chipset: http://ati.amd.com/products/radeon9100igp/features.html I'm going to pursue this with more dedication as it is really the only current path I've heard of so far that gives me a chance to stay current with Gentoo. What VIDEO_DEVICES setting might one use to get this driver called up? Either ati or radeon and check that it installs Open Source? So you want the radeon/ati driver, the package name is xf86-video-ati, so I guess that means you want ati in VIDEO_DEVICES. It is a bunch of work, but it would be great if I can use it. I thought emerge xf86-video-ati, then swapping Driver flgrx to Driver radeon in xorg.conf was all that is required?? No, I need a new kernel also. The kernel on this machine is 2 years old. Also, I have about a dozen packages masked so I've unmasked those and will need to get the whole machine up to date. None the less I'm happy to do it if there's any chance it will work. Thanks, Mark
[gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On 06/25/2009 04:27 AM, Mark Knecht wrote: I thought emerge xf86-video-ati, then swapping Driver flgrx to Driver radeon in xorg.conf was all that is required?? No, I need a new kernel also. The kernel on this machine is 2 years old. Also, I have about a dozen packages masked so I've unmasked those and will need to get the whole machine up to date. None the less I'm happy to do it if there's any chance it will work. If it works, better make sure you keep the system up to date. Gentoo will bark and bite you at some point if you don't; I'm sure you figured that out by now :P
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On Wed, Jun 24, 2009 at 6:51 PM, Nikos Chantziarasrea...@arcor.de wrote: On 06/25/2009 04:27 AM, Mark Knecht wrote: I thought emerge xf86-video-ati, then swapping Driver flgrx to Driver radeon in xorg.conf was all that is required?? No, I need a new kernel also. The kernel on this machine is 2 years old. Also, I have about a dozen packages masked so I've unmasked those and will need to get the whole machine up to date. None the less I'm happy to do it if there's any chance it will work. If it works, better make sure you keep the system up to date. Gentoo will bark and bite you at some point if you don't; I'm sure you figured that out by now :P Except for being forced into all these old kernel and video packages the machine has been kept up to date. Now it will be completely up to date. :-) The new kernel booted the first time and except for me forgetting to enable the correct NIC things looked good. I added the 3c590 and now can get to it over ssh. emerge -DuN @world will take a few hours as there are a number of packages to update. Tomorrow I will delve into the newer Open Source ATI driver and see how things go. Wish me luck. cheers, Mark
[gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On 06/24/2009 02:20 AM, Mark Knecht wrote: Hi all, Main question is whether there is any change in the way I select the fglrx driver with xorg-server-1.5? I have a big emerge running on one of my MythTV frontends that uses an old 2.6.19 kernel with an old 8.28 ati-driver package. The machine does not use a keyboard or mouse. I cannot update either the kernel or the ati-driver for hardware support reasons. When the emerge is finished in a couple of hours do I need to change the xorg.conf file at all to use the server with the fglrx driver or will it just work? There's a pretty big chance that 8.28 is so old that it does not support xorg-server 1.5 at all. That means you can't use xorg-server 1.5. And if you're not prepared to update your kernel, then the xorg native driver (xf86-video-ati) is out of the question too. It looks to me you'll have to keep using the older xorg-server.
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On Tue, Jun 23, 2009 at 4:27 PM, Nikos Chantziarasrea...@arcor.de wrote: On 06/24/2009 02:20 AM, Mark Knecht wrote: Hi all, Main question is whether there is any change in the way I select the fglrx driver with xorg-server-1.5? I have a big emerge running on one of my MythTV frontends that uses an old 2.6.19 kernel with an old 8.28 ati-driver package. The machine does not use a keyboard or mouse. I cannot update either the kernel or the ati-driver for hardware support reasons. When the emerge is finished in a couple of hours do I need to change the xorg.conf file at all to use the server with the fglrx driver or will it just work? There's a pretty big chance that 8.28 is so old that it does not support xorg-server 1.5 at all. That means you can't use xorg-server 1.5. And if you're not prepared to update your kernel, then the xorg native driver (xf86-video-ati) is out of the question too. It looks to me you'll have to keep using the older xorg-server. Thanks Nikos. I hope that's not the case or I've waster a couple of hours because emerge didn't stop me from doing this. No messages at all about anything like too old a kernel or vidieo driver. It's almost done so I guess I'll just wait and then see how it goes. There is no way to update the kernel as far as I know. The ATI chip that's in the computer has an S-video output that I need to drive the TV. After 8.28 ATI stopped supporting S-Video for this chip meaning I cannot update ati-drivers. To use the 8.28 ati-driver package I'm forced to use the 2.6.19 kernel. Believe me, I'd like to update but don't know how to unless I buy a new video card. I haven't looked in the box in a LONG time but I think it's possibly PCI only, and then it's also low form factor so it will probably be pretty hard to find ANY video card to fit it, but maybe I'll look around in case I have to go that way. Cheers, Mark
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On Tue, Jun 23, 2009 at 4:40 PM, Mark Knechtmarkkne...@gmail.com wrote: On Tue, Jun 23, 2009 at 4:27 PM, Nikos Chantziarasrea...@arcor.de wrote: On 06/24/2009 02:20 AM, Mark Knecht wrote: Hi all, Main question is whether there is any change in the way I select the fglrx driver with xorg-server-1.5? I have a big emerge running on one of my MythTV frontends that uses an old 2.6.19 kernel with an old 8.28 ati-driver package. The machine does not use a keyboard or mouse. I cannot update either the kernel or the ati-driver for hardware support reasons. When the emerge is finished in a couple of hours do I need to change the xorg.conf file at all to use the server with the fglrx driver or will it just work? There's a pretty big chance that 8.28 is so old that it does not support xorg-server 1.5 at all. That means you can't use xorg-server 1.5. And if you're not prepared to update your kernel, then the xorg native driver (xf86-video-ati) is out of the question too. It looks to me you'll have to keep using the older xorg-server. Thanks Nikos. I hope that's not the case or I've waster a couple of hours because emerge didn't stop me from doing this. No messages at all about anything like too old a kernel or vidieo driver. It's almost done so I guess I'll just wait and then see how it goes. There is no way to update the kernel as far as I know. The ATI chip that's in the computer has an S-video output that I need to drive the TV. After 8.28 ATI stopped supporting S-Video for this chip meaning I cannot update ati-drivers. To use the 8.28 ati-driver package I'm forced to use the 2.6.19 kernel. Believe me, I'd like to update but don't know how to unless I buy a new video card. I haven't looked in the box in a LONG time but I think it's possibly PCI only, and then it's also low form factor so it will probably be pretty hard to find ANY video card to fit it, but maybe I'll look around in case I have to go that way. Cheers, Mark OK, after the reboot fglrx is in memory but Xorg.0.log is complaining about missing symbols: myth12 ~ # uname -a Linux myth12 2.6.19-gentoo-r5 #2 PREEMPT Sat May 19 17:55:30 PDT 2007 i686 Intel(R) Celeron(R) CPU 2.26GHz GenuineIntel GNU/Linux myth12 ~ # lsmod | grep fglrx fglrx 390828 0 agpgart24240 2 fglrx,ati_agp myth12 ~ # (II) LoadModule: fglrx (II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so dlopen: /usr/lib/xorg/modules/drivers//fglrx_drv.so: undefined symbol: miZeroLineScreenIndex (EE) Failed to load /usr/lib/xorg/modules/drivers//fglrx_drv.so (II) UnloadModule: fglrx (EE) Failed to load module fglrx (loader failed, 7) (EE) No drivers available. Fatal server error: no screens found Am I completely hosed here? Looking on NewEgg I'm not finding any AGP fanless, low-profile cards yet and I'm not sure the machine supported AGP anyway. I'll have to open the box or find some old docs online. There is one fanless ATI Radeon 9250-based PCI-based card but it's expensive for this application at $90. Looks like it's back to the older xorg-server. - Mark
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On Tue, Jun 23, 2009 at 4:53 PM, Mark Knechtmarkkne...@gmail.com wrote: On Tue, Jun 23, 2009 at 4:40 PM, Mark Knechtmarkkne...@gmail.com wrote: On Tue, Jun 23, 2009 at 4:27 PM, Nikos Chantziarasrea...@arcor.de wrote: On 06/24/2009 02:20 AM, Mark Knecht wrote: Hi all, Main question is whether there is any change in the way I select the fglrx driver with xorg-server-1.5? I have a big emerge running on one of my MythTV frontends that uses an old 2.6.19 kernel with an old 8.28 ati-driver package. The machine does not use a keyboard or mouse. I cannot update either the kernel or the ati-driver for hardware support reasons. When the emerge is finished in a couple of hours do I need to change the xorg.conf file at all to use the server with the fglrx driver or will it just work? There's a pretty big chance that 8.28 is so old that it does not support xorg-server 1.5 at all. That means you can't use xorg-server 1.5. And if you're not prepared to update your kernel, then the xorg native driver (xf86-video-ati) is out of the question too. It looks to me you'll have to keep using the older xorg-server. Thanks Nikos. I hope that's not the case or I've waster a couple of hours because emerge didn't stop me from doing this. No messages at all about anything like too old a kernel or vidieo driver. It's almost done so I guess I'll just wait and then see how it goes. There is no way to update the kernel as far as I know. The ATI chip that's in the computer has an S-video output that I need to drive the TV. After 8.28 ATI stopped supporting S-Video for this chip meaning I cannot update ati-drivers. To use the 8.28 ati-driver package I'm forced to use the 2.6.19 kernel. Believe me, I'd like to update but don't know how to unless I buy a new video card. I haven't looked in the box in a LONG time but I think it's possibly PCI only, and then it's also low form factor so it will probably be pretty hard to find ANY video card to fit it, but maybe I'll look around in case I have to go that way. Cheers, Mark OK, after the reboot fglrx is in memory but Xorg.0.log is complaining about missing symbols: myth12 ~ # uname -a Linux myth12 2.6.19-gentoo-r5 #2 PREEMPT Sat May 19 17:55:30 PDT 2007 i686 Intel(R) Celeron(R) CPU 2.26GHz GenuineIntel GNU/Linux myth12 ~ # lsmod | grep fglrx fglrx 390828 0 agpgart 24240 2 fglrx,ati_agp myth12 ~ # (II) LoadModule: fglrx (II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so dlopen: /usr/lib/xorg/modules/drivers//fglrx_drv.so: undefined symbol: miZeroLineScreenIndex (EE) Failed to load /usr/lib/xorg/modules/drivers//fglrx_drv.so (II) UnloadModule: fglrx (EE) Failed to load module fglrx (loader failed, 7) (EE) No drivers available. Fatal server error: no screens found Am I completely hosed here? Looking on NewEgg I'm not finding any AGP fanless, low-profile cards yet and I'm not sure the machine supported AGP anyway. I'll have to open the box or find some old docs online. There is one fanless ATI Radeon 9250-based PCI-based card but it's expensive for this application at $90. Looks like it's back to the older xorg-server. - Mark Am I hosed again? Did updating portage break my machine by removing what I was just using: 1245799356: === Unmerging... (x11-base/xorg-server-1.1.1-r5) 1245799361: unmerge success: x11-base/xorg-server-1.1.1-r5 1245799361: emerge (62 of 64) x11-base/xorg-server-1.5.3-r6 to / 1245799363: === (62 of 64) Cleaning (x11-base/xorg-server-1.5.3-r6::/usr/portage/x11-base/xorg-server/xorg-server-1.5.3-r6.ebuild) 1245799363: === (62 of 64) Compiling/Merging (x11-base/xorg-server-1.5.3-r6::/usr/portage/x11-base/xorg-server/xorg-server-1.5.3-r6.ebuild) 1245800519: === (62 of 64) Merging (x11-base/xorg-server-1.5.3-r6::/usr/portage/x11-base/xorg-server/xorg-server-1.5.3-r6.ebuild) 1245800527: AUTOCLEAN: x11-base/xorg-server:0 myth12 ~ # ls -a /usr/portage/distfiles/xorg-server-* /usr/portage/distfiles/xorg-server-1.5.3-gentoo-patches-08.tar.bz2 /usr/portage/distfiles/xorg-server-1.5.3.tar.bz2 myth12 ~ # Is xorg-server-1.1.1 completely gone and I'm hosed? I'm not finding it on my my machine. The only variations on that theme seem to be in /var/db/pkg. No tar files, just other programming junk. I absolutely HATE this about portage. Update your machine just thinking about trying a new piece of software and then find you cannot immediately go back. Gentoo was supposed to be about choice. Seems it's not about my choice anymore. Bummer. Maybe I can find this on another machine somewhere. Don't know what to do though. Family gets no MythTV for a few days, or maybe forever? I'm trying to mask things to check this and emerge is really mad at me. - Mark
[gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On 06/24/2009 03:06 AM, Mark Knecht wrote: [...] Am I hosed again? Did updating portage break my machine by removing what I was just using: [...] Is xorg-server-1.1.1 completely gone and I'm hosed? I'm not finding it on my my machine. The only variations on that theme seem to be in /var/db/pkg. No tar files, just other programming junk. I absolutely HATE this about portage. Update your machine just thinking about trying a new piece of software and then find you cannot immediately go back. Gentoo was supposed to be about choice. Seems it's not about my choice anymore. Bummer. I hate to say this, but if you have a machine that you don't keep up to date by doing full updates at least each month or two, then Gentoo is *not* for you because Gentoo simply lacks the notion of stable. Stable refers to package versions, not system stability. Gentoo is never stable in that sense like other distros that offer stable releases. Something like Debian stable should be more appropriate and far more easier to keep operational for machines like that.
Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On Tue, Jun 23, 2009 at 5:16 PM, Nikos Chantziarasrea...@arcor.de wrote: On 06/24/2009 03:06 AM, Mark Knecht wrote: [...] Am I hosed again? Did updating portage break my machine by removing what I was just using: [...] Is xorg-server-1.1.1 completely gone and I'm hosed? I'm not finding it on my my machine. The only variations on that theme seem to be in /var/db/pkg. No tar files, just other programming junk. I absolutely HATE this about portage. Update your machine just thinking about trying a new piece of software and then find you cannot immediately go back. Gentoo was supposed to be about choice. Seems it's not about my choice anymore. Bummer. I hate to say this, but if you have a machine that you don't keep up to date by doing full updates at least each month or two, then Gentoo is *not* for you because Gentoo simply lacks the notion of stable. Stable refers to package versions, not system stability. Gentoo is never stable in that sense like other distros that offer stable releases. Something like Debian stable should be more appropriate and far more easier to keep operational for machines like that. Gentoo is for me. Gentoo is the only distro I run and the only one I've run for at least 6 years. Gentoo has run on THIS VERY MACHINE for over 4 years and it is the ONLY distro that has EVER run on this machine. Today I run eix-sync and emerge xorg-x11 and the machine breaks and I cannot go back. It is not my choice that Gentoo maintainers decided to drop something from portage required to make this machine run and not give me a way to get it back. Portage chose to erase files on MY machine - files that are required to make the machine work. Gentoo package maintainers decided to obsolete my machine, not me. I'm sure there's some way to get things back working again but I don't know what they are. I've got two identical machines but looking around on the other machine it doesn't seem much happier, even though it's currently functional. Well, I guess you can chuckle at my problems and say tough luck. Better if you can offer some guidance about what to read to go find these files. Again, I'd LOVE to keep the machine COMPLETELY up to date. It's not my fault the folks who run portage decided to remove what this machine requires to work. It's not my fault that ATI stopped supporting the hardware. It's not my fault that the only driver that works with the hardware only works with an old kernel. And there is probably NO distro that would support this box anymore off the install CD. - Mark
[gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On 06/24/2009 03:06 AM, Mark Knecht wrote: [...] Family gets no MythTV for a few days, or maybe forever? I'm trying to mask things to check this and emerge is really mad at me. As a last attempt at damage control, try the full update anyway. Remove fglrx from VIDEO_CARDS and replace it with radeon (I assume you have a Radeon card?) Delete /etc/X11/xorg.conf and see what happens. Maybe the recent xorg driver for Radeons supports the S-Video port of your card correctly. At least that's what I'm seeing while googling for xf86-video-ati S-Video.
[gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
On 06/24/2009 03:27 AM, Mark Knecht wrote: Gentoo is for me. Gentoo is the only distro I run and the only one I've run for at least 6 years. Gentoo has run on THIS VERY MACHINE for over 4 years and it is the ONLY distro that has EVER run on this machine. Today I run eix-sync and emerge xorg-x11 and the machine breaks and I cannot go back. It is not my choice that Gentoo maintainers decided to drop something from portage required to make this machine run and not give me a way to get it back. Portage chose to erase files on MY machine - files that are required to make the machine work. Gentoo package maintainers decided to obsolete my machine, not me. You should have taken a backup of /usr/portage and created binary packages using quickpgk before the update. Portage can't contain every ancient version of every package out there. It would grow to infinity. Old stuff has to go. That's the very nature of Gentoo's rolling release nature (or on other words, its lack of a stable notion.) Anyway, see my other post, maybe you can go on with the update and have it working in the end. I'm sure there's some way to get things back working again but I don't know what they are. The rule is simple. If a fresh installation of Gentoo wouldn't work, you're out of luck. Gentoo lacks releases. Either you change hardware or distribution.