Re: [gentoo-user] kdrive use flag quandary
On Sunday 16 May 2010 05:42:13 William Kenworthy wrote: I am trying to update a laptop after a break of a few months and have an ... anomaly! It suddenly wants the kdrive use flag enabled for xorg-server and sabayon - why? I think kdrive is a minimal xserver built on top of xorg so its not appropriate for a system I want full functionality on - is it? How can I find out whats bringing this use flag in as I cant find anything so far. euse -I kdrive will show which packages on your system are using this flag. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Gentoo decapitated
On Sunday 16 May 2010 02:24:10 Kevin O'Gorman wrote: On Wed, May 12, 2010 at 3:33 PM, Dale rdalek1...@gmail.com wrote: Mine has xf86-* drivers as well. OP, do you have your setting in make.conf correctly? Mine looks like this: INPUT_DEVICES=keyboard mouse evdev I do NOT use hal so your settings may need to be different but you do need the line tho. I have INPUT_DEVICES=evdev, and adding either of the others makes X go back to not starting at all. That's right, you will also then need to install the appropriate x86 driver; e.g. x11-drivers/xf86-input-mouse -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: libpng12 is missing [TEMP SOLN]
On 5/15/2010 11:06 AM, Roy Wright wrote: Argh. Just have to vent a little. Bring up a new install on a system whose system disk died and was replaced with an SSD. OS installed no problems. Recovered my RAID5 and LVM JBOD volume (a GIANT THANK YOU to the mdadm and lvm2 folks!). Then first weekly update hits the libpng12 issue. No complaints, it's what I expect being at ~amd64 and the price I willing pay for the benefits of gentoo. Another THANK YOU to the lafilefixer folks and system is up. So on to my list a applications to be installed. Firefox check, openoffice check, handbrake...crap. Handbrake is one of the non-standard packages that includes their own version of support libraries. You guessed it, libpng12 dependent. Argh! Have fun, Roy I had the same problem with a 'missing' libpng12. There are 2 slots for libpng: slot 0 and slot 1.2. You DON'T want anything in the 1.2 slot. What you DO want is the lonely ebuild in the 0 slot. Why? It will create the libpng12.la file that is needed for packages to find the library. So this is what I did: 1. Ran emerge -C libpng to remove ALL versions of libpng that were installed. 2. Ran emerge =libpng-1.2.43-r2. I believe that is the version of the slot 0 libpng. 3. Ran lafilefixer --justfixit -- just in case. 4. Re-emerged cairo to make sure it was linked to my newly installed libpng12 5. Belatedly realized that I should mask every version of libpng above the slot 0 one, and did so. 6. Ran equery d libpng from the 'gentoolkit' package. 7. Re-emerged everything on that list (even Open office - ugh). In step 7, everything compiled and installed just fine - no errors. From what I can see, this looks like an upstream bug, where their source is coded to look only for libpng12, and nothing else. For me it would stop with an error during the linking phase, or right at the beginning (at least those packages had checks). I hope this helps someone. Chris
[gentoo-user] xorg-server 1.8.1 random segfaults
Does anyone else get random segfaults all the time with xorg-server-1.8.1? Backtrace: 0: /usr/bin/X (xorg_backtrace+0x28) [0x45cc28] 1: /usr/bin/X (0x40+0x59899) [0x459899] 2: /lib/libpthread.so.0 (0x300100+0xf0d0) [0x300100f0d0] 3: /usr/bin/X (dixLookupPrivate+0xa) [0x42c5aa] 4: /usr/lib64/xorg/modules/extensions/libglx.so (0x7f39c8fb3000+0x3f18a) [0x7f39c8ff218a] 5: /usr/lib64/xorg/modules/extensions/libglx.so (0x7f39c8fb3000+0x3656f) [0x7f39c8fe956f] 6: /usr/bin/X (FreeResource+0x13f) [0x42a38f] 7: /usr/lib64/xorg/modules/extensions/libglx.so (0x7f39c8fb3000+0x336c9) [0x7f39c8fe66c9] 8: /usr/lib64/xorg/modules/extensions/libglx.so (0x7f39c8fb3000+0x363ae) [0x7f39c8fe93ae] 9: /usr/bin/X (0x40+0x44f1c) [0x444f1c] 10: /usr/bin/X (0x40+0x217e5) [0x4217e5] 11: /lib/libc.so.6 (__libc_start_main+0xfd) [0x300041ebbd] 12: /usr/bin/X (0x40+0x21399) [0x421399] Segmentation fault at address 0x290 Fatal server error: Caught signal 11 (Segmentation fault). Server aborting 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.)
Re: [gentoo-user] USB printer and new cups
On Sunday 16 May 2010 02:56:23 Alex Schuster wrote: Thanks, this made me install gutenprint which claims to support the printer directly. I thought I had to use the iP4200 driver and hope it would work. I think that gutenprint is the correct driver for your printer and this page also suggests the same: http://www.openprinting.org/printer/Canon/Canon-iP4000 However, this might have been the case before the latest cups version - so some further testing will be required (see below). But my main problem is another one: How do I tell CUPS which device my printer is? I tried usb:/dev/usb/lp0 (found this notation when googling 'usb printer device uri'), but nothing happens when I try to print. This is the cups driver (in kernel) which ought to pick up your usb printer and use it without problems. However, according to your logs ... there seems to be a clash: There is a message in syslog that is being repeated hundreds of times: May 15 22:25:55 [kernel] usb 1-2: usbfs: interface 0 claimed by usblp while 'usb' sets config #1 So, what happens if you build usblp as a module and you modprobe -rv ubslp? Does cups pick up your printer now? And now it gets really crazy: In the printer overview I see not only the 'iP5200' I just created, but also a 'iP52002' that has the device URI 'usb://Canon/iP5200'. What did create this?! But printing to that does not work either. I suspect that this was created by the gutenprint driver that you installed. I believe that if you resolve the usblp error first then you'll know if gutenprint is necessary or if it will work. Some manual tweaking of the ppd file may also be needed to print in higher resolutions, but let's get it to print first. Stop press! I just checked again your first post: You are using cups 1.4 which accesses raw usb devices! Definitely remove usblp (or blacklist it and reboot if you don't want to recompile your kernel, or can't modprobe -r) and see if the cups back end picks up your printer on its own. HTH -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] X hoggs CPU (xorg-server-1.7.6) (was: xorg-server: Pressing 'down'/'right ctrl' keys yields newline)
On 05/14/10 00:47, walt wrote: On 05/13/2010 03:22 AM, Amit Dor-Shifer wrote: On 05/13/10 00:54, walt wrote: 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. 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 should have said *I* don't need an Input device section any more :) Actually I moved some of my custom stuff from xorg.conf to the hal config files -- but hal is deprecated now and I should it back to xorg.conf again. Thanks for the reminder. 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 Thanks. X -configure solved it. As long as we're at the subject:Those options you're mentioning, would they go under the Keyboard0 device? I Added some options there: Section InputDevice Identifier Keyboard0 Driver kbd *** kbd driver is obsolete, use evdev or just delete this line Simply deleting this line causes X to fail startup: Xorg.0.log (==) Using config file: /etc/X11/xorg.conf Data incomplete in file /etc/X11/xorg.conf InputDevice section Keyboard0 must have a Driver line. (EE) Problem parsing the config file (EE) Error parsing the config file /Xorg.0.log Explicitly setting Driver to evdev (to both mouse and keyboard sections) doesn't fix the unexplained messages in Xorg.0.log. At least X manages to start, though. Depending on your configuration, there may be some font and/or keyboard stuff in your own home directory. You may need to search or grep some subdirectories to find it if it's not obvious. Found nothing so-far... I'm now noticing another problem: X's CPU usage sky-rockets when using input devices. Especially mouse: If I move my pointer around the screen, hovering over some windows in the process, I get 50% CPU in 'top'. Amit
Re: [gentoo-user] kdrive use flag quandary
On Sun, 2010-05-16 at 08:08 +0100, Mick wrote: On Sunday 16 May 2010 05:42:13 William Kenworthy wrote: I am trying to update a laptop after a break of a few months and have an ... anomaly! It suddenly wants the kdrive use flag enabled for xorg-server and sabayon - why? I think kdrive is a minimal xserver built on top of xorg so its not appropriate for a system I want full functionality on - is it? How can I find out whats bringing this use flag in as I cant find anything so far. euse -I kdrive will show which packages on your system are using this flag. Its not what packages use it - but what packages are causing it to be needed that I want: From the new sabayon ebuild stabilized for gnome 2.28 it seems to require xorg-server to be built with kdrive. So even though this system is using stable gnome, the newer sabayon now requires it ... COMMON_DEPEND==dev-lang/python-2.4 =x11-libs/gtk+-2.6.0 =dev-python/pygtk-2.5.3 =dev-python/pygobject-2.15 x11-libs/pango dev-python/python-ldap x11-base/xorg-server[kdrive] It appears its set by autounmask for gnome-2.28.2 on my other systems so guess its a requirement these days ... guess I'll unmask the newer gnome here as well - seems to work ok. BillK
Re: [gentoo-user] kdrive use flag quandary
Am 16.05.2010 12:22, schrieb William Kenworthy: On Sun, 2010-05-16 at 08:08 +0100, Mick wrote: On Sunday 16 May 2010 05:42:13 William Kenworthy wrote: I am trying to update a laptop after a break of a few months and have an ... anomaly! It suddenly wants the kdrive use flag enabled for xorg-server and sabayon - why? I think kdrive is a minimal xserver built on top of xorg so its not appropriate for a system I want full functionality on - is it? How can I find out whats bringing this use flag in as I cant find anything so far. euse -I kdrive will show which packages on your system are using this flag. Its not what packages use it - but what packages are causing it to be needed that I want: From the new sabayon ebuild stabilized for gnome 2.28 it seems to require xorg-server to be built with kdrive. So even though this system is using stable gnome, the newer sabayon now requires it ... COMMON_DEPEND==dev-lang/python-2.4 =x11-libs/gtk+-2.6.0 =dev-python/pygtk-2.5.3 =dev-python/pygobject-2.15 x11-libs/pango dev-python/python-ldap x11-base/xorg-server[kdrive] It appears its set by autounmask for gnome-2.28.2 on my other systems so guess its a requirement these days ... guess I'll unmask the newer gnome here as well - seems to work ok. BillK You need kdrive for Xephyr!
Re: [gentoo-user] kdrive use flag quandary
On Sun, 2010-05-16 at 13:03 +0200, ich bins wrote: Am 16.05.2010 12:22, schrieb William Kenworthy: On Sun, 2010-05-16 at 08:08 +0100, Mick wrote: On Sunday 16 May 2010 05:42:13 William Kenworthy wrote: I am trying to update a laptop after a break of a few months and have an ... anomaly! It suddenly wants the kdrive use flag enabled for xorg-server and sabayon - why? I think kdrive is a minimal xserver built on top of xorg so its not appropriate for a system I want full functionality on - is it? How can I find out whats bringing this use flag in as I cant find anything so far. euse -I kdrive will show which packages on your system are using this flag. Its not what packages use it - but what packages are causing it to be needed that I want: From the new sabayon ebuild stabilized for gnome 2.28 it seems to require xorg-server to be built with kdrive. So even though this system is using stable gnome, the newer sabayon now requires it ... COMMON_DEPEND==dev-lang/python-2.4 =x11-libs/gtk+-2.6.0 =dev-python/pygtk-2.5.3 =dev-python/pygobject-2.15 x11-libs/pango dev-python/python-ldap x11-base/xorg-server[kdrive] It appears its set by autounmask for gnome-2.28.2 on my other systems so guess its a requirement these days ... guess I'll unmask the newer gnome here as well - seems to work ok. BillK You need kdrive for Xephyr! Perhaps, but its not installed and doesnt even have an ebuild that I can see. BillK
[gentoo-user] Re: Kernel upgrade and now LUKS failure
[Replying to http://thread.gmane.org/gmane.linux.gentoo.user/229533/focus=229542 ] On 2010-05-05 08:00:43 GMT, Daniel Troeder wrote: On 05/05/2010 06:42 AM, Stefan G. Weichinger wrote: Am 04.05.2010 23:24, schrieb Daniel Troeder: I'm using sys-fs/cryptsetup-1.1.1_rc1 since 02.05.2010 and didn't have any issues. Please decrypt your partition from the command line, so we can see if it is a cryptsetup/luks/kernel problem or a pam_mount problem. Cmdline should something like: $ sudo cryptsetup -d /etc/security/verysekrit.key luksOpen /dev/mapper/VG01-crypthome myhome Which should create /dev/mapper/myhome. My user sgw is currently not allowed to sudo this (should it be? it never was). And for root it says Kein Schlüssel mit diesem Passsatz verfügbar. (german) which should be No key available with this passphrase. in english. That is a message from cryptsetup. As you are using openssl to get the key, I think the problem might be there. I followed the guide you linked here (website is down, but google-cache works: http://webcache.googleusercontent.com/search?q=cache:7eaSac72CoIJ:home.coming.dk/index.php/2009/05/20/encrypted_home_partition_using_luks_pam_+encrypted_home_partition_using_luks_pamcd=2hl=dect=clnkgl=declient=firefox-a) and it works for me (kernel is 2.6.33-zen2): lvcreate -n crypttest -L 100M vg0 KEY=`tr -cd [:graph:] /dev/urandom | head -c 79` echo $KEY | openssl aes-256-ecb verysekrit.key openssl aes-256-ecb -d -in verysekrit.key In my personal opinion, both the quality of shell commands and key generation is suboptimal. What makes it bad is that people follow it. First, it generates a key which does not exploit the entire space. People claim it's because they want an ASCII readout, but frankly, you get the same with `hexdump -C`. Second, it's using echo without the -n parameter, thus implicitly inserting a newline into the key -- which is the cause for yoru observed mounting problems. Third, because you are passing the key via stdin into cryptsetup, it only uses the first line of whatever you pipe into it; whereas pam_mount uses the entire keyfile as it is supposed to be. (Fourth, the howto suggests ECB, which, well, looks rather weak considering the ECB's Tux picture on Wikipedia.) All of that should be in doc/bugs.txt, and mount.crypt even warns about ECB. You really cannot ignore seeing that. Phew!
[gentoo-user] emerge portage error
Hi, Please help me to get rid of this error while emerging portage: # emerge portage Calculating dependencies... done! Verifying ebuild Manifests... starting parallel fetching pid 6030 Emerging (1 of 2) dev-lang/python-2.5.4-r4 to / * Python-2.5.4.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * python-gentoo-patches-2.5.4-r3.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking Python-2.5.4.tar.bz2 ;-) ... [ ok ] * checking python-gentoo-patches-2.5.4-r3.tar.bz2 ;-) ... [ ok ] * bsddb module is out-of-date and no longer maintained inside dev-lang/python. It has * been additionally removed in Python 3. You should use external, still maintained bsddb3 * module provided by dev-python/bsddb3 which supports both Python 2 and Python 3. * * ERROR: dev-lang/python-2.5.4-r4 failed. * Call stack: *ebuild.sh, line 49: Called pkg_setup * python-2.5.4-r4.ebuild, line 64: Called built_with_use 'pkg_setup' 'pkg_setup' *eutils.eclass, line 1862: Called die * The specific snippet of code: * die) die $PKG does not actually support the $1 USE flag!;; * The die message: * sys-devel/gcc-4.1.2 does not actually support the libffi USE flag! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-lang/python-2.5.4-r4/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-lang/python-2.5.4-r4/temp/die.env'. * * Messages for package dev-lang/python-2.5.4-r4: * * ERROR: dev-lang/python-2.5.4-r4 failed. * Call stack: *ebuild.sh, line 49: Called pkg_setup * python-2.5.4-r4.ebuild, line 64: Called built_with_use 'pkg_setup' 'pkg_setup' *eutils.eclass, line 1862: Called die * The specific snippet of code: * die) die $PKG does not actually support the $1 USE flag!;; * The die message: * sys-devel/gcc-4.1.2 does not actually support the libffi USE flag! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-lang/python-2.5.4-r4/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-lang/python-2.5.4-r4/temp/die.env'. * * bsddb module is out-of-date and no longer maintained inside dev-lang/python. It has * been additionally removed in Python 3. You should use external, still maintained bsddb3 * module provided by dev-python/bsddb3 which supports both Python 2 and Python 3.
Re: [gentoo-user] emerge portage error
On Sunday 16 May 2010 15:10:16 Simon wrote:
Hi,
Please help me to get rid of this error while emerging portage:
# emerge portage
[snip]
Yea gods, the youth of today. In my day, when I was a little whipper-snapper,
we actually read the ebuild. Why because? Because there was no-one else around
to do our looking by proxy for us!
So, in the interest of decomming the proxy in my head, herewith the magic
incantations to make your problem go Poof! and disappear:
Firstly, you have tools to help. equery, euse, and many more. Learn how to use
them, and use them.
Secondly, read the ebuild. portage does what the ebuild says so the master
reference to figure out why portage wants to do something is in the ebuild (or
eclasses that it inherits).
* bsddb module is out-of-date and no longer maintained inside
dev-lang/python. It has
* been additionally removed in Python 3. You should use external,
still maintained bsddb3
* module provided by dev-python/bsddb3 which supports both Python 2
and Python 3.
*
* ERROR: dev-lang/python-2.5.4-r4 failed.
* Call stack:
*ebuild.sh, line 49: Called pkg_setup
* python-2.5.4-r4.ebuild, line 64: Called built_with_use
'pkg_setup' 'pkg_setup'
*eutils.eclass, line 1862: Called die
* The specific snippet of code:
* die) die $PKG does not
actually support the $1 USE flag!;;
* The die message:
* sys-devel/gcc-4.1.2 does not actually support the libffi USE flag!
From the ebuild:
pkg_setup() {
if use berkdb; then
ewarn \bsddb\ module is out-of-date and no longer
maintained inside dev-lang/python. It has
ewarn been additionally removed in Python 3. You should use
external, still maintained \bsddb3\
ewarn module provided by dev-python/bsddb3 which supports
both Python 2 and Python 3.
fi
if built_with_use sys-devel/gcc libffi; then
die Reinstall sys-devel/gcc with \libffi\ USE flag
disabled
fi
}
So, to get rid of the bsddb ewarn, you need to remove that berkdb from USE.
And the build failure is staring you right there in the face. As we say here
at the tip of Africa, As dit 'n slang was, het dit jou gepik [If it were a
snake, it would have already bitten you].
You have USE=libffi which doesn't work. Remove it, sync the tree, rebuild
world. (your portage and gcc versions have updates available, even on stable)
--
alan dot mckinnon at gmail dot com
[gentoo-user] Stuttering DVB-T video output
Hi, for watching DVB-T broadcasts on my PC I am using vlc, which is fed with an appropiate channels.conf file from the commandline. Everything is fine so far...but... The video output stutters, especially when switching desktops or when scrolling html pages in firefox or... often this happens without any additional actions on the desktop. lspci reports: 00:00.0 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge Subsystem: ASUSTeK Computer Inc. A8V Deluxe Kernel driver in use: agpgart-amd64 00:00.1 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:00.7 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] 00:0a.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13) Subsystem: ASUSTeK Computer Inc. Marvell 88E8001 Gigabit Ethernet Controller (Asus) Kernel driver in use: skge 00:0d.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) Subsystem: Avermedia Technologies Inc AverMedia AVerTV DVB-T 771 Kernel driver in use: bttv Kernel modules: bttv 00:0d.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) Subsystem: Avermedia Technologies Inc AverMedia AVerTV DVB-T 771 Kernel driver in use: bt878 Kernel modules: bt878 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) Subsystem: ASUSTeK Computer Inc. A7V600/K8V Deluxe/K8V-X/A8V Deluxe motherboard Kernel driver in use: sata_via 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard Kernel driver in use: pata_via 00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:10.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard Kernel modules: i2c-viapro 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60) Subsystem: ASUSTeK Computer Inc. A8V Deluxe motherboard (Realtek ALC850 codec) Kernel driver in use: VIA 82xx Audio 00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control Kernel driver in use: k8temp Kernel modules: k8temp 01:00.0 VGA compatible controller: nVidia Corporation G73 [GeForce 7600 GT] (rev a2) Subsystem: Micro-Star International Co., Ltd. Device 0640 Kernel driver in use: nvidia Kernel modules: nvidia uname -a reports: Linux solfire 2.6.32.13 #1 SMP PREEMPT Sat May 15 10:14:09 CEST 2010 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ AuthenticAMD GNU/Linux (the kernel is the vanilla version from ftp.kernel.org) vlc is: VLC media player 1.0.6 Goldeneye VLC version 1.0.6 Goldeneye Compiled by r...@localhost. Compiler: gcc version 4.3.4 (Gentoo 4.3.4 p1.1, pie-10.1.5) vlc uses as output default and the rest of the configuration is on default as the installation process leaves it behind. What can I do to prevent or minimize the
Re: [gentoo-user] Stuttering DVB-T video output
Hi, I am using dvb-s with kaffeine and ati and don't have any stuttering. Do you have effects turned on? Turn them off. Are you using the nvidia driver? Or nv? nouveau? Use nvidia. Do you have any stupid governor turned on - like userspace? Use ondemand.
Re: [gentoo-user] Gentoo decapitated
On Sun, May 16, 2010 at 12:11 AM, Mick michaelkintz...@gmail.com wrote:
On Sunday 16 May 2010 02:24:10 Kevin O'Gorman wrote:
On Wed, May 12, 2010 at 3:33 PM, Dale rdalek1...@gmail.com wrote:
Mine has xf86-* drivers as well. OP, do you have your setting in
make.conf correctly? Mine looks like this:
INPUT_DEVICES=keyboard mouse evdev
I do NOT use hal so your settings may need to be different but you do
need the line tho.
I have INPUT_DEVICES=evdev, and adding either of the others makes X
go
back to not starting at all.
That's right, you will also then need to install the appropriate x86
driver;
e.g. x11-drivers/xf86-input-mouse
You mean like this, the way it's always been? Or is there something more
specific I have to do?
treat src # eix x11-drivers/xf86-input-mouse
[I] x11-drivers/xf86-input-mouse
Available versions: 1.5.0{tbz2} {debug}
Installed versions: 1.5.0{tbz2}(09:38:05 PM 05/11/2010)(-debug)
Homepage:http://xorg.freedesktop.org/
Description: X.Org driver for mouse input devices
treat src #
BTW, the most recent boot started X without the mouse working, but these two
lines appear in /var/log/Xorg.0.log
line 44-47: (==) |--Input Device evdev
(==) |--Input Device default keyboard
(==) The core pointer device wasn't specified explicitly in the
layout.
Using the first mouse device.
line 457: (==) MACH64(0): Silken mouse enabled
(MACH64 is my video card)
(My mouse is a Microsoft optical with a USB cord that I use with a PS/2
adapter and a KVM switch, which works with Live disks. I have no idea what
Silken is)
These are the only lines with the word mouse in them.
--
Kevin O'Gorman, PhD
Re: [gentoo-user] Gentoo decapitated
On Sunday 16 May 2010 16:43:48 Kevin O'Gorman wrote:
On Sun, May 16, 2010 at 12:11 AM, Mick michaelkintz...@gmail.com wrote:
On Sunday 16 May 2010 02:24:10 Kevin O'Gorman wrote:
On Wed, May 12, 2010 at 3:33 PM, Dale rdalek1...@gmail.com wrote:
Mine has xf86-* drivers as well. OP, do you have your setting in
make.conf correctly? Mine looks like this:
INPUT_DEVICES=keyboard mouse evdev
I do NOT use hal so your settings may need to be different but you do
need the line tho.
I have INPUT_DEVICES=evdev, and adding either of the others makes X
go
back to not starting at all.
That's right, you will also then need to install the appropriate x86
driver;
e.g. x11-drivers/xf86-input-mouse
You mean like this, the way it's always been? Or is there something more
specific I have to do?
treat src # eix x11-drivers/xf86-input-mouse
[I] x11-drivers/xf86-input-mouse
Available versions: 1.5.0{tbz2} {debug}
Installed versions: 1.5.0{tbz2}(09:38:05 PM 05/11/2010)(-debug)
Homepage:http://xorg.freedesktop.org/
Description: X.Org driver for mouse input devices
treat src #
BTW, the most recent boot started X without the mouse working, but these
two lines appear in /var/log/Xorg.0.log
line 44-47: (==) |--Input Device evdev
(==) |--Input Device default keyboard
(==) The core pointer device wasn't specified explicitly in the
layout.
Using the first mouse device.
line 457: (==) MACH64(0): Silken mouse enabled
(MACH64 is my video card)
(My mouse is a Microsoft optical with a USB cord that I use with a PS/2
adapter and a KVM switch, which works with Live disks. I have no idea what
Silken is)
These are the only lines with the word mouse in them.
Kevin, what I would try first is to set INPUT_DEVICES=evdev mouse in your
/etc/make.conf, then emerge x11-drivers/xf86-input-mouse and finally reboot.
Unless your mouse needs some special driver it will just work.
I've been down this road (with simpler hardware than yours it seems) and my
machine would not start xorg if I did not have INPUT_DEVICES=evdev mouse
keyboard. On my laptops I had to also add synaptics.
HTH
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] Stuttering DVB-T video output
Volker Armin Hemmann volkerar...@googlemail.com [10-05-16 17:40]: Hi, I am using dvb-s with kaffeine and ati and don't have any stuttering. Do you have effects turned on? Turn them off. Are you using the nvidia driver? Or nv? nouveau? Use nvidia. Do you have any stupid governor turned on - like userspace? Use ondemand. As said, I am using DVB-T. In the lspci listing, I appended to my previous mail, you can find the kind of nvidia-card I am using and that I am using the nvidia driver. I recompiled with the ondemand governor set and will see, what happens. Thanks for your infos. Best regards, mcc -- 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] Gentoo decapitated
On Sun, May 16, 2010 at 8:43 AM, Kevin O'Gorman kogor...@gmail.com wrote:
On Sun, May 16, 2010 at 12:11 AM, Mick michaelkintz...@gmail.com wrote:
On Sunday 16 May 2010 02:24:10 Kevin O'Gorman wrote:
On Wed, May 12, 2010 at 3:33 PM, Dale rdalek1...@gmail.com wrote:
Mine has xf86-* drivers as well. OP, do you have your setting in
make.conf correctly? Mine looks like this:
INPUT_DEVICES=keyboard mouse evdev
I do NOT use hal so your settings may need to be different but you do
need the line tho.
I have INPUT_DEVICES=evdev, and adding either of the others makes X
go
back to not starting at all.
That's right, you will also then need to install the appropriate x86
driver;
e.g. x11-drivers/xf86-input-mouse
You mean like this, the way it's always been? Or is there something more
specific I have to do?
treat src # eix x11-drivers/xf86-input-mouse
[I] x11-drivers/xf86-input-mouse
Available versions: 1.5.0{tbz2} {debug}
Installed versions: 1.5.0{tbz2}(09:38:05 PM 05/11/2010)(-debug)
Homepage:http://xorg.freedesktop.org/
Description: X.Org driver for mouse input devices
treat src #
BTW, the most recent boot started X without the mouse working, but these
two lines appear in /var/log/Xorg.0.log
line 44-47: (==) |--Input Device evdev
(==) |--Input Device default keyboard
(==) The core pointer device wasn't specified explicitly in the
layout.
Using the first mouse device.
line 457: (==) MACH64(0): Silken mouse enabled
(MACH64 is my video card)
(My mouse is a Microsoft optical with a USB cord that I use with a PS/2
adapter and a KVM switch, which works with Live disks. I have no idea what
Silken is)
These are the only lines with the word mouse in them.
Oh, and one more thing showed up last night. I reemerged udev, and noticed
that the ebuild printed a message to the effect that if it doesn't work, I
should try emerging hal first. Leaving aside the non-effective language, I
tried that and although hal is installed, I can no longer build it. This
may turn out to be the most important thing. It turns out I can't compile
the latest wireshark either. Maybe something is hosed deep down. It may be
time to go down the emptytree road again, but it took 2 weeks last time,
and was a major PITA.
--
Kevin O'Gorman, PhD
Re: [gentoo-user] Re: libpng12 is missing [TEMP SOLN]
On May 16, 2010, at 2:30 AM, Chris Walters wrote: On 5/15/2010 11:06 AM, Roy Wright wrote: Argh. Just have to vent a little. So on to my list a applications to be installed. Firefox check, openoffice check, handbrake...crap. Handbrake is one of the non-standard packages that includes their own version of support libraries. You guessed it, libpng12 dependent. Argh! Have fun, Roy I had the same problem with a 'missing' libpng12. There are 2 slots for libpng: slot 0 and slot 1.2. You DON'T want anything in the 1.2 slot. What you DO want is the lonely ebuild in the 0 slot. Why? It will create the libpng12.la file that is needed for packages to find the library. So this is what I did: 1. Ran emerge -C libpng to remove ALL versions of libpng that were installed. 2. Ran emerge =libpng-1.2.43-r2. I believe that is the version of the slot 0 libpng. 3. Ran lafilefixer --justfixit -- just in case. 4. Re-emerged cairo to make sure it was linked to my newly installed libpng12 5. Belatedly realized that I should mask every version of libpng above the slot 0 one, and did so. 6. Ran equery d libpng from the 'gentoolkit' package. 7. Re-emerged everything on that list (even Open office - ugh). In step 7, everything compiled and installed just fine - no errors. From what I can see, this looks like an upstream bug, where their source is coded to look only for libpng12, and nothing else. For me it would stop with an error during the linking phase, or right at the beginning (at least those packages had checks). I hope this helps someone. Chris Got handbrake installed. When initially going thru the mess I ended up with both slot 0 and slot 1.2 installed. So unmerged slot 1.2, did a revdep-rebuild, then handbrake built fine. So system is (for now at least) pure 1.4. Have fun, Roy
[gentoo-user] RAID problems - Is udev at fault here?
I have a newish high-end machine here that's causing me some problems with RAID, but looking at log files and dmesg I don't think the problem is actually RAID and more likely udev. I'm looking for some ideas on how to debug this. The hardware: Asus Rampage II Extreme Intel Core i7-980x 12GB DRAM 5 WD5002ABYS RAID Edition 500GB drives The drives are arranged as a 3-drive RAID1 and a 2-drive RAID0 using mdadm. The issue is that when booting gets to the point where it starts mdadm and then about 50% of the time mdadm fails to find some of the partitions and hence either starts the RAID1 with missing drives or in the case of RAID0 won't start the RAID. For instance, /dev/md5 might start with a failed partition, either /dev/sda5 or sdb5 or sdc5 isn't found and the RAID is started. Once the problem has occurred I don't seem to be able to fix it with anything other than a reboot so far. Investigating dmesg when there is a failure I actually don't see that the missing partition is ever identified and looking at the /dev directory the partition isn't there either. Personally I don't think the problem is with the drives as BIOS shows me a table of the drives attached before booting and the 5 drives are _always_ shown. If I drop into BIOS proper and use BIOS tools to look at the drives I can _always_ read smart data and all drives respond to DOS-based tools like SpinRite. It's only when I get into Linux that they aren't found. The problem hasn't changed much with different kernels from 2.6.32 through 2.6.34, nor do I see any difference running vanilla-sources or gentoo-sources. Currently I'm using udev-149 with devfs-compat and extra flags enabled. Where might I start looking for the root cause of a problem like this? Let me know what other info would be helpful. Thanks, Mark
Re: [gentoo-user] Gentoo decapitated
On Sunday 16 May 2010 18:18:09 Kevin O'Gorman wrote:
On Sun, May 16, 2010 at 8:43 AM, Kevin O'Gorman kogor...@gmail.com wrote:
On Sun, May 16, 2010 at 12:11 AM, Mick michaelkintz...@gmail.com wrote:
On Sunday 16 May 2010 02:24:10 Kevin O'Gorman wrote:
On Wed, May 12, 2010 at 3:33 PM, Dale rdalek1...@gmail.com wrote:
Mine has xf86-* drivers as well. OP, do you have your setting in
make.conf correctly? Mine looks like this:
INPUT_DEVICES=keyboard mouse evdev
I do NOT use hal so your settings may need to be different but you
do need the line tho.
I have INPUT_DEVICES=evdev, and adding either of the others makes
X
go
back to not starting at all.
That's right, you will also then need to install the appropriate x86
driver;
e.g. x11-drivers/xf86-input-mouse
You mean like this, the way it's always been? Or is there something more
specific I have to do?
treat src # eix x11-drivers/xf86-input-mouse
[I] x11-drivers/xf86-input-mouse
Available versions: 1.5.0{tbz2} {debug}
Installed versions: 1.5.0{tbz2}(09:38:05 PM 05/11/2010)(-debug)
Homepage:http://xorg.freedesktop.org/
Description: X.Org driver for mouse input devices
treat src #
BTW, the most recent boot started X without the mouse working, but these
two lines appear in /var/log/Xorg.0.log
line 44-47: (==) |--Input Device evdev
(==) |--Input Device default keyboard
(==) The core pointer device wasn't specified explicitly in
the layout.
Using the first mouse device.
line 457: (==) MACH64(0): Silken mouse enabled
(MACH64 is my video card)
(My mouse is a Microsoft optical with a USB cord that I use with a PS/2
adapter and a KVM switch, which works with Live disks. I have no idea
what Silken is)
These are the only lines with the word mouse in them.
Oh, and one more thing showed up last night. I reemerged udev, and noticed
that the ebuild printed a message to the effect that if it doesn't work, I
should try emerging hal first. Leaving aside the non-effective language, I
tried that and although hal is installed, I can no longer build it. This
may turn out to be the most important thing. It turns out I can't compile
the latest wireshark either. Maybe something is hosed deep down. It may
be time to go down the emptytree road again, but it took 2 weeks last
time, and was a major PITA.
I don't know if you have been following the libpng12 is missing thread, but
for good measure you may want to try lafilefixer --justfixit and revdep-
rebuild -p -v -i a number of times first. On two machines of mine (x86) there
was no problem. On another (amd64) I had to go through the pain of emerge -e
world.
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
[gentoo-user] Re: Gentoo decapitated
On 05/16/2010 08:43 AM, Kevin O'Gorman wrote:
On Sun, May 16, 2010 at 12:11 AM, Mick michaelkintz...@gmail.com
mailto:michaelkintz...@gmail.com wrote:
On Sunday 16 May 2010 02:24:10 Kevin O'Gorman wrote:
On Wed, May 12, 2010 at 3:33 PM, Dale rdalek1...@gmail.com
mailto:rdalek1...@gmail.com wrote:
Mine has xf86-* drivers as well. OP, do you have your setting in
make.conf correctly? Mine looks like this:
INPUT_DEVICES=keyboard mouse evdev
I do NOT use hal so your settings may need to be different but you do
need the line tho.
I have INPUT_DEVICES=evdev, and adding either of the others makes X
go
back to not starting at all.
That's right, you will also then need to install the appropriate x86 driver;
e.g. x11-drivers/xf86-input-mouse
You mean like this, the way it's always been? Or is there something more
specific I have to do?
treat src # eix x11-drivers/xf86-input-mouse
[I] x11-drivers/xf86-input-mouse
Available versions: 1.5.0{tbz2} {debug}
Installed versions: 1.5.0{tbz2}(09:38:05 PM 05/11/2010)(-debug)
Homepage: http://xorg.freedesktop.org/
Description: X.Org driver for mouse input devices
treat src #
BTW, the most recent boot started X without the mouse working, but these two
lines appear in /var/log/Xorg.0.log
line 44-47: (==) |--Input Device evdev
(==) |--Input Device default keyboard
(==) The core pointer device wasn't specified explicitly in the
layout.
Using the first mouse device.
line 457: (==) MACH64(0): Silken mouse enabled
(MACH64 is my video card)
(My mouse is a Microsoft optical with a USB cord that I use with a PS/2 adapter
and a KVM switch, which works with Live disks. I have no idea what Silken is)
These are the only lines with the word mouse in them.
I just did the experiment of building xorg-server with the hal useflag *off*,
and
found that neither keyboard nor mouse worked until I restored the two
InputDevice
sections that I commented out when I switched to evdev+hal:
Section ServerLayout
Identifier X.org Configured
Screen 0 Screen0 0 0
Option AIGLXfalse
InputDeviceMouse0 CorePointer -- restored these two lines
InputDeviceKeyboard0 CoreKeyboard ---
EndSection
Section InputDevice
Identifier Keyboard0
Driver evdev
Option Device /dev/input/event3
EndSection
Section InputDevice
Identifier Mouse0
Driver evdev
Option Protocol auto
Option Device /dev/input/event4
Option Emulate3Buttons True
EndSection
Note those Device entries. I found those devices in /dev/input/by-path/:
$ls -l /dev/input/by-path/
lrwxrwxrwx 1 root root 9 2010-05-16 10:40 platform-i8042-serio-0-event-kbd -
../event3
lrwxrwxrwx 1 root root 9 2010-05-16 10:40 platform-i8042-serio-1-event-mouse
- ../event4
lrwxrwxrwx 1 root root 9 2010-05-16 10:40 platform-i8042-serio-1-mouse -
../mouse0
evdev uses event-devices, hence the name. I don't use the mouse0 device at
all but I'm guessing I would if I used the mouse driver instead of evdev.
Starting with xorg-server-1.8 the mouse and keyboard Inputdevice sections are no
longer needed (not sure about synaptics, though), because the server uses evdev
automatically (no manual configuration like cited above) and ignores hal
completely.
Using the evdev driver alone, and xorg-server built without hal, I get this:
(**) Option CorePointer
(**) Mouse0: always reports core events
(**) Mouse0: Device: /dev/input/event4
(II) Mouse0: Found 9 mouse buttons
(II) Mouse0: Found scroll wheel(s)
(II) Mouse0: Found relative axes
(II) Mouse0: Found x and y relative axes
(II) Mouse0: Configuring as mouse
(**) Option Emulate3Buttons True
(II) Mouse0: Forcing middle mouse button emulation on.
(II) XINPUT: Adding extended input device Mouse0 (type: MOUSE)
(**) Mouse0: (accel) keeping acceleration scheme 1
(**) Mouse0: (accel) acceleration profile 0
(II) Mouse0: initialized for relative axes.
(**) Option CoreKeyboard
(**) Keyboard0: always reports core events
(**) Keyboard0: Device: /dev/input/event3
(II) Keyboard0: Found keys
(II) Keyboard0: Configuring as keyboard
(II) XINPUT: Adding extended input device Keyboard0 (type: KEYBOARD)
(**) Option xkb_rules evdev
(**) Option xkb_model evdev
(**) Option xkb_layout us
[gentoo-user] Re: X hoggs CPU (xorg-server-1.7.6)
On 05/16/2010 01:12 AM, Amit Dor-Shifer wrote: Explicitly setting Driver to evdev (to both mouse and keyboard sections) doesn't fix the unexplained messages in Xorg.0.log. At least X manages to start, though. I'm expecting that your newest Xorg log will be different from the earlier ones. Which messages do you mean? I'm now noticing another problem: X's CPU usage sky-rockets when using input devices. Especially mouse: If I move my pointer around the screen, hovering over some windows in the process, I get 50% CPU in 'top'. I've never seen that before. Does hovering over xev print any messages?
[gentoo-user] Re: kdrive use flag quandary
On 05/16/2010 04:14 AM, William Kenworthy wrote: On Sun, 2010-05-16 at 13:03 +0200, ich bins wrote: Am 16.05.2010 12:22, schrieb William Kenworthy: On Sun, 2010-05-16 at 08:08 +0100, Mick wrote: On Sunday 16 May 2010 05:42:13 William Kenworthy wrote: I am trying to update a laptop after a break of a few months and have an ... anomaly! It suddenly wants the kdrive use flag enabled for xorg-server and sabayon - why? I think kdrive is a minimal xserver built on top of xorg so its not appropriate for a system I want full functionality on - is it? How can I find out whats bringing this use flag in as I cant find anything so far. euse -I kdrive will show which packages on your system are using this flag. Its not what packages use it - but what packages are causing it to be needed that I want: From the new sabayon ebuild stabilized for gnome 2.28 it seems to require xorg-server to be built with kdrive. So even though this system is using stable gnome, the newer sabayon now requires it ... COMMON_DEPEND==dev-lang/python-2.4 =x11-libs/gtk+-2.6.0 =dev-python/pygtk-2.5.3 =dev-python/pygobject-2.15 x11-libs/pango dev-python/python-ldap x11-base/xorg-server[kdrive] It appears its set by autounmask for gnome-2.28.2 on my other systems so guess its a requirement these days ... guess I'll unmask the newer gnome here as well - seems to work ok. BillK You need kdrive for Xephyr! Perhaps, but its not installed and doesnt even have an ebuild that I can see. Xephyr is a driver installed by xorg-server-1.8 on my ~amd64 machine, but not on my x86 machine with xorg-server-1.7.6. Which version are you trying to install?
Re: [gentoo-user] Gentoo decapitated
On Sun, May 16, 2010 at 9:03 AM, Mick michaelkintz...@gmail.com wrote:
On Sunday 16 May 2010 16:43:48 Kevin O'Gorman wrote:
On Sun, May 16, 2010 at 12:11 AM, Mick michaelkintz...@gmail.com
wrote:
On Sunday 16 May 2010 02:24:10 Kevin O'Gorman wrote:
On Wed, May 12, 2010 at 3:33 PM, Dale rdalek1...@gmail.com wrote:
Mine has xf86-* drivers as well. OP, do you have your setting in
make.conf correctly? Mine looks like this:
INPUT_DEVICES=keyboard mouse evdev
I do NOT use hal so your settings may need to be different but you
do
need the line tho.
I have INPUT_DEVICES=evdev, and adding either of the others makes
X
go
back to not starting at all.
That's right, you will also then need to install the appropriate x86
driver;
e.g. x11-drivers/xf86-input-mouse
You mean like this, the way it's always been? Or is there something more
specific I have to do?
treat src # eix x11-drivers/xf86-input-mouse
[I] x11-drivers/xf86-input-mouse
Available versions: 1.5.0{tbz2} {debug}
Installed versions: 1.5.0{tbz2}(09:38:05 PM 05/11/2010)(-debug)
Homepage:http://xorg.freedesktop.org/
Description: X.Org driver for mouse input devices
treat src #
BTW, the most recent boot started X without the mouse working, but these
two lines appear in /var/log/Xorg.0.log
line 44-47: (==) |--Input Device evdev
(==) |--Input Device default keyboard
(==) The core pointer device wasn't specified explicitly in
the
layout.
Using the first mouse device.
line 457: (==) MACH64(0): Silken mouse enabled
(MACH64 is my video card)
(My mouse is a Microsoft optical with a USB cord that I use with a PS/2
adapter and a KVM switch, which works with Live disks. I have no idea
what
Silken is)
These are the only lines with the word mouse in them.
Kevin, what I would try first is to set INPUT_DEVICES=evdev mouse in your
/etc/make.conf, then emerge x11-drivers/xf86-input-mouse and finally
reboot.
Unless your mouse needs some special driver it will just work.
I've been down this road (with simpler hardware than yours it seems) and my
machine would not start xorg if I did not have INPUT_DEVICES=evdev mouse
keyboard. On my laptops I had to also add synaptics.
Well, that breaks kind of badly. X never even starts. But for a peculiar
reason... Here's what I find in the log file
(==) Using config file: /etc/X11/xorg.conf
Data incomplete in file /etc/X11/xorg.conf
Undefined InputDevice evdev mouse referenced by ServerLayout
X.org Configured.
(EE) Problem parsing the config file
(EE) Error parsing the config file
Fatal server error:
no screens found
So I tried the same thing with two statements
Section ServerLayout
Identifier X.org Configured
Screen 0 Screen0 0 0
#InputDeviceMouse0 CorePointer
#InputDeviceKeyboard0 CoreKeyboard
InputDevice evdev
InputDevice mouse
EndSection
And I got
(==) Using config file: /etc/X11/xorg.conf
Data incomplete in file /etc/X11/xorg.conf
Undefined InputDevice mouse referenced by ServerLayout X.org
Configured.
(EE) Problem parsing the config file
(EE) Error parsing the config file
Fatal server error:
no screens found
So I'm thinking it just doesn't like mouse all of a sudden. Say what?
--
Kevin O'Gorman, PhD
[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: RAID problems - Is udev at fault here?
On 05/16/2010 10:56 AM, Mark Knecht wrote: I have a newish high-end machine here that's causing me some problems with RAID, but looking at log files and dmesg I don't think the problem is actually RAID and more likely udev. I'm looking for some ideas on how to debug this. The hardware: Asus Rampage II Extreme Intel Core i7-980x 12GB DRAM 5 WD5002ABYS RAID Edition 500GB drives I had an asus mobo that turned out to be great in the long run, but a few of its newer hardware gadgets took months to be well-supported by linux. I'm thinking (completely guessing :) it sounds like a driver that's not setting some bit properly in a hardware register during boot. That turned out to be a problem with the network chip on my asus, which randomly didn't work after reboots. Finally the driver got fixed after I whined a thousand times to the driver maintainer at Broadcom :)
Re: [gentoo-user] Gentoo decapitated
On Sun, May 16, 2010 at 11:23 AM, Mick michaelkintz...@gmail.com wrote: On Sunday 16 May 2010 18:18:09 Kevin O'Gorman wrote: On Sun, May 16, 2010 at 8:43 AM, Kevin O'Gorman kogor...@gmail.com wrote: major snippage Oh, and one more thing showed up last night. I reemerged udev, and noticed that the ebuild printed a message to the effect that if it doesn't work, I should try emerging hal first. Leaving aside the non-effective language, I tried that and although hal is installed, I can no longer build it. This may turn out to be the most important thing. It turns out I can't compile the latest wireshark either. Maybe something is hosed deep down. It may be time to go down the emptytree road again, but it took 2 weeks last time, and was a major PITA. I don't know if you have been following the libpng12 is missing thread, but for good measure you may want to try lafilefixer --justfixit and revdep- rebuild -p -v -i a number of times first. On two machines of mine (x86) there was no problem. On another (amd64) I had to go through the pain of emerge -e world. I just did the lafixer thing and was astonished at how many .la files it said it was fixing. Seems like my system should have been dead outright Now I'm off to a bunch of revdep-rebuilds. Hope this works, because I really *do not* want to emerge -e world (again). -- Kevin O'Gorman, PhD
Re: [gentoo-user] Gentoo decapitated
On Sun, May 16, 2010 at 2:43 PM, Kevin O'Gorman kogor...@gmail.com wrote: On Sun, May 16, 2010 at 11:23 AM, Mick michaelkintz...@gmail.com wrote: On Sunday 16 May 2010 18:18:09 Kevin O'Gorman wrote: On Sun, May 16, 2010 at 8:43 AM, Kevin O'Gorman kogor...@gmail.com wrote: major snippage Oh, and one more thing showed up last night. I reemerged udev, and noticed that the ebuild printed a message to the effect that if it doesn't work, I should try emerging hal first. Leaving aside the non-effective language, I tried that and although hal is installed, I can no longer build it. This may turn out to be the most important thing. It turns out I can't compile the latest wireshark either. Maybe something is hosed deep down. It may be time to go down the emptytree road again, but it took 2 weeks last time, and was a major PITA. I don't know if you have been following the libpng12 is missing thread, but for good measure you may want to try lafilefixer --justfixit and revdep- rebuild -p -v -i a number of times first. On two machines of mine (x86) there was no problem. On another (amd64) I had to go through the pain of emerge -e world. I just did the lafixer thing and was astonished at how many .la files it said it was fixing. Seems like my system should have been dead outright Now I'm off to a bunch of revdep-rebuilds. Hope this works, because I really *do not* want to emerge -e world (again). I've got to ask, though, what good a revdep-rebuild does with the -p (pretend) flag. Am I missing something here? -- Kevin O'Gorman, PhD
Re: [gentoo-user] Re: RAID problems - Is udev at fault here?
On Sun, May 16, 2010 at 1:32 PM, walt w41...@gmail.com wrote: On 05/16/2010 10:56 AM, Mark Knecht wrote: I have a newish high-end machine here that's causing me some problems with RAID, but looking at log files and dmesg I don't think the problem is actually RAID and more likely udev. I'm looking for some ideas on how to debug this. The hardware: Asus Rampage II Extreme Intel Core i7-980x 12GB DRAM 5 WD5002ABYS RAID Edition 500GB drives I had an asus mobo that turned out to be great in the long run, but a few of its newer hardware gadgets took months to be well-supported by linux. I'm thinking (completely guessing :) it sounds like a driver that's not setting some bit properly in a hardware register during boot. That turned out to be a problem with the network chip on my asus, which randomly didn't work after reboots. Finally the driver got fixed after I whined a thousand times to the driver maintainer at Broadcom :) It very well could be something like that. I had a Compaq laptop a few years ago which had an ATI chipset in it and which took a long time to get DMA working on the hard drive controller to it was very slow for the first few months. The thing about this is that it's a single 6 port SATA controller in an Intel chipset, albeit because it's the newer chipsets with the newest processor (6 cores, 12 threads) it likely hasn't been seen by too many people yet. Let's assume you're right? I've been trying to determine how udev goes about finding the actual hard drives and assigning them device names. Is there a way that I can get udev to log what it's doing? Any sort of debug messages I can get it to print in a log file somewhere? It is a flaky problem and strangely it doesn't always miss every partition on a given drive. For instance /dev/md3, md5 and md11 3-drive RAID1 arrays. You'd think if it was the controller failing it would fail for all the partitions on a given drive, but it doesn't. It might find sda3 for md3 but miss sda5 for md5. Strange. Thanks for the ideas. - Mark
Re: [gentoo-user] Gentoo decapitated
On Sunday 16 May 2010 22:45:55 Kevin O'Gorman wrote: On Sun, May 16, 2010 at 2:43 PM, Kevin O'Gorman kogor...@gmail.com wrote: On Sun, May 16, 2010 at 11:23 AM, Mick michaelkintz...@gmail.com wrote: On Sunday 16 May 2010 18:18:09 Kevin O'Gorman wrote: On Sun, May 16, 2010 at 8:43 AM, Kevin O'Gorman kogor...@gmail.com wrote: major snippage Oh, and one more thing showed up last night. I reemerged udev, and noticed that the ebuild printed a message to the effect that if it doesn't work, I should try emerging hal first. Leaving aside the non-effective language, I tried that and although hal is installed, I can no longer build it. This may turn out to be the most important thing. It turns out I can't compile the latest wireshark either. Maybe something is hosed deep down. It may be time to go down the emptytree road again, but it took 2 weeks last time, and was a major PITA. I don't know if you have been following the libpng12 is missing thread, but for good measure you may want to try lafilefixer --justfixit and revdep- rebuild -p -v -i a number of times first. On two machines of mine (x86) there was no problem. On another (amd64) I had to go through the pain of emerge -e world. I just did the lafixer thing and was astonished at how many .la files it said it was fixing. Seems like my system should have been dead outright Now I'm off to a bunch of revdep-rebuilds. Hope this works, because I really *do not* want to emerge -e world (again). I've got to ask, though, what good a revdep-rebuild does with the -p (pretend) flag. Am I missing something here? You're not missing anything. It's a cautionary step only. If you are about to do something with the machine and remerging the whole universe would be inconvenient at this moment in time, or you may want to reconsider/change some of your settings, then --pretend will give you this chance. I've made the habit of using it almost without thinking, but you can of course not use it, or substitute it with -a. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Gentoo decapitated
On Sun, May 16, 2010 at 3:00 PM, Mick michaelkintz...@gmail.com wrote: On Sunday 16 May 2010 22:45:55 Kevin O'Gorman wrote: On Sun, May 16, 2010 at 2:43 PM, Kevin O'Gorman kogor...@gmail.com wrote: On Sun, May 16, 2010 at 11:23 AM, Mick michaelkintz...@gmail.com wrote: On Sunday 16 May 2010 18:18:09 Kevin O'Gorman wrote: On Sun, May 16, 2010 at 8:43 AM, Kevin O'Gorman kogor...@gmail.com wrote: major snippage Oh, and one more thing showed up last night. I reemerged udev, and noticed that the ebuild printed a message to the effect that if it doesn't work, I should try emerging hal first. Leaving aside the non-effective language, I tried that and although hal is installed, I can no longer build it. This may turn out to be the most important thing. It turns out I can't compile the latest wireshark either. Maybe something is hosed deep down. It may be time to go down the emptytree road again, but it took 2 weeks last time, and was a major PITA. I don't know if you have been following the libpng12 is missing thread, but for good measure you may want to try lafilefixer --justfixit and revdep- rebuild -p -v -i a number of times first. On two machines of mine (x86) there was no problem. On another (amd64) I had to go through the pain of emerge -e world. I just did the lafixer thing and was astonished at how many .la files it said it was fixing. Seems like my system should have been dead outright Now I'm off to a bunch of revdep-rebuilds. Hope this works, because I really *do not* want to emerge -e world (again). I've got to ask, though, what good a revdep-rebuild does with the -p (pretend) flag. Am I missing something here? You're not missing anything. It's a cautionary step only. If you are about to do something with the machine and remerging the whole universe would be inconvenient at this moment in time, or you may want to reconsider/change some of your settings, then --pretend will give you this chance. I've made the habit of using it almost without thinking, but you can of course not use it, or substitute it with -a. -- Regards, Mick Well, it just told me it will rebuild clisp and m4, neither of which strike me as essential to Xorg, but I'll give it a try. Thanks, ++ kevin -- Kevin O'Gorman, PhD
Re: [gentoo-user] Gentoo decapitated
On Sun, May 16, 2010 at 01:16:34PM -0700, Kevin O'Gorman wrote: These are the only lines with the word mouse in them. Kevin, what I would try first is to set INPUT_DEVICES=evdev mouse in your /etc/make.conf, then emerge x11-drivers/xf86-input-mouse and finally reboot. Unless your mouse needs some special driver it will just work. The advice is to set the appropriate flag in /etc/make.conf NOT what you are doing below to /etc/X11/xorg.conf So I tried the same thing with two statements Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 #InputDeviceMouse0 CorePointer #InputDeviceKeyboard0 CoreKeyboard InputDevice evdev InputDevice mouse EndSection That is not exactly the right syntax for Xorg.conf If you are using an xorg.conf and not just using evdev/hal, then you should probably have something more like this in your configuration file: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/input/mouse1 EndSection ...plus other things. In the InputDevice section for Mouse0, note the Option that sets the Device to /dev/input/mouse1. You will have to set that to the appropriate path to the pointer device. It will most likely by somewhere in /dev/input/ (often just mouse0 or mice, I have a separate touchscreen device so mine is at mouse1). If you do not have a mouse device listed in /dev/input, then you need to check either your kernel configurations or your udev configurations. For more about the proper syntax in xorg.conf, try man xorg.conf. If you are unsure about how to write your xorg.conf file, post its full contents to the list and we'll take a look at it. Cheers, W -- Willie W. Wong ww...@math.princeton.edu Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire et vice versa ~~~ I. Newton
[gentoo-user] Re: kdrive use flag quandary
On 05/15/2010 09:42 PM, William Kenworthy wrote: I am trying to update a laptop after a break of a few months and have an ... anomaly! It suddenly wants the kdrive use flag enabled for xorg-server and sabayon - why? I think kdrive is a minimal xserver built on top of xorg so its not appropriate for a system I want full functionality on - is it? How can I find out whats bringing this use flag in as I cant find anything so far. The method most often suggested is adding the 't' flag to your emerge: #emerge -auNDt world
Re: [gentoo-user] Stuttering DVB-T video output
On 16 May 2010, at 15:10, meino.cra...@gmx.de wrote: ... for watching DVB-T broadcasts on my PC I am using vlc, which is fed with an appropiate channels.conf file from the commandline. Everything is fine so far...but... The video output stutters, especially when switching desktops or when scrolling html pages in firefox or... often this happens without any additional actions on the desktop. You need to state that you've catted from the /dev/whatever to a file, or whatever the correct way is to directly make a recording, then played the resultant video back using vlc, mplayer on a different system. You also haven't stated the resolution of the video you're trying to play. Hi-def is demanding of system resources, standard def should be no problem on any PC made in the last 7 or 8 years. Stroller.
SOLVED: Re: [gentoo-user] Re: Gentoo decapitated
On Sun, May 16, 2010 at 11:25 AM, walt w41...@gmail.com wrote:
On 05/16/2010 08:43 AM, Kevin O'Gorman wrote:
On Sun, May 16, 2010 at 12:11 AM, Mick michaelkintz...@gmail.commailto:
michaelkintz...@gmail.com wrote:
On Sunday 16 May 2010 02:24:10 Kevin O'Gorman wrote:
On Wed, May 12, 2010 at 3:33 PM, Dale rdalek1...@gmail.commailto:
rdalek1...@gmail.com wrote:
Mine has xf86-* drivers as well. OP, do you have your setting in
make.conf correctly? Mine looks like this:
INPUT_DEVICES=keyboard mouse evdev
I do NOT use hal so your settings may need to be different but you
do
need the line tho.
I have INPUT_DEVICES=evdev, and adding either of the others
makes X go
back to not starting at all.
That's right, you will also then need to install the appropriate x86
driver;
e.g. x11-drivers/xf86-input-mouse
You mean like this, the way it's always been? Or is there something more
specific I have to do?
treat src # eix x11-drivers/xf86-input-mouse
[I] x11-drivers/xf86-input-mouse
Available versions: 1.5.0{tbz2} {debug}
Installed versions: 1.5.0{tbz2}(09:38:05 PM 05/11/2010)(-debug)
Homepage: http://xorg.freedesktop.org/
Description: X.Org driver for mouse input devices
treat src #
BTW, the most recent boot started X without the mouse working, but these
two lines appear in /var/log/Xorg.0.log
line 44-47: (==) |--Input Device evdev
(==) |--Input Device default keyboard
(==) The core pointer device wasn't specified explicitly in
the layout.
Using the first mouse device.
line 457: (==) MACH64(0): Silken mouse enabled
(MACH64 is my video card)
(My mouse is a Microsoft optical with a USB cord that I use with a PS/2
adapter and a KVM switch, which works with Live disks. I have no idea what
Silken is)
These are the only lines with the word mouse in them.
I just did the experiment of building xorg-server with the hal useflag
*off*, and
found that neither keyboard nor mouse worked until I restored the two
InputDevice
sections that I commented out when I switched to evdev+hal:
Section ServerLayout
Identifier X.org Configured
Screen 0 Screen0 0 0
Option AIGLXfalse
InputDeviceMouse0 CorePointer -- restored these two
lines
InputDeviceKeyboard0 CoreKeyboard ---
EndSection
Section InputDevice
Identifier Keyboard0
Driver evdev
Option Device /dev/input/event3
EndSection
Section InputDevice
Identifier Mouse0
Driver evdev
Option Protocol auto
Option Device /dev/input/event4
Option Emulate3Buttons True
EndSection
Note those Device entries. I found those devices in /dev/input/by-path/:
$ls -l /dev/input/by-path/
lrwxrwxrwx 1 root root 9 2010-05-16 10:40
platform-i8042-serio-0-event-kbd - ../event3
lrwxrwxrwx 1 root root 9 2010-05-16 10:40
platform-i8042-serio-1-event-mouse - ../event4
lrwxrwxrwx 1 root root 9 2010-05-16 10:40 platform-i8042-serio-1-mouse -
../mouse0
evdev uses event-devices, hence the name. I don't use the mouse0
device at
all but I'm guessing I would if I used the mouse driver instead of
evdev.
Starting with xorg-server-1.8 the mouse and keyboard Inputdevice sections
are no
longer needed (not sure about synaptics, though), because the server uses
evdev
automatically (no manual configuration like cited above) and ignores hal
completely.
Using the evdev driver alone, and xorg-server built without hal, I get
this:
(**) Option CorePointer
(**) Mouse0: always reports core events
(**) Mouse0: Device: /dev/input/event4
(II) Mouse0: Found 9 mouse buttons
(II) Mouse0: Found scroll wheel(s)
(II) Mouse0: Found relative axes
(II) Mouse0: Found x and y relative axes
(II) Mouse0: Configuring as mouse
(**) Option Emulate3Buttons True
(II) Mouse0: Forcing middle mouse button emulation on.
(II) XINPUT: Adding extended input device Mouse0 (type: MOUSE)
(**) Mouse0: (accel) keeping acceleration scheme 1
(**) Mouse0: (accel) acceleration profile 0
(II) Mouse0: initialized for relative axes.
(**) Option CoreKeyboard
(**) Keyboard0: always reports core events
(**) Keyboard0: Device: /dev/input/event3
(II) Keyboard0: Found keys
(II) Keyboard0: Configuring as keyboard
(II) XINPUT: Adding extended input device Keyboard0 (type: KEYBOARD)
(**) Option xkb_rules evdev
(**) Option xkb_model evdev
(**) Option xkb_layout us
GENIUS. It worked! That which has been dead for 2 weeks is risen!
Many thanks.
--
Kevin O'Gorman, PhD
Re: [gentoo-user] Gentoo decapitated
On Sun, May 16, 2010 at 2:43 PM, Kevin O'Gorman kogor...@gmail.com wrote: On Sun, May 16, 2010 at 11:23 AM, Mick michaelkintz...@gmail.com wrote: On Sunday 16 May 2010 18:18:09 Kevin O'Gorman wrote: On Sun, May 16, 2010 at 8:43 AM, Kevin O'Gorman kogor...@gmail.com wrote: major snippage Oh, and one more thing showed up last night. I reemerged udev, and noticed that the ebuild printed a message to the effect that if it doesn't work, I should try emerging hal first. Leaving aside the non-effective language, I tried that and although hal is installed, I can no longer build it. This may turn out to be the most important thing. It turns out I can't compile the latest wireshark either. Maybe something is hosed deep down. It may be time to go down the emptytree road again, but it took 2 weeks last time, and was a major PITA. I don't know if you have been following the libpng12 is missing thread, but for good measure you may want to try lafilefixer --justfixit and revdep- rebuild -p -v -i a number of times first. On two machines of mine (x86) there was no problem. On another (amd64) I had to go through the pain of emerge -e world. I just did the lafixer thing and was astonished at how many .la files it said it was fixing. Seems like my system should have been dead outright Now I'm off to a bunch of revdep-rebuilds. Hope this works, because I really *do not* want to emerge -e world (again). Well, it was an interesting excercise, but I'm no closer to a runnable Xorg (it won't start at all as long as I have InputDevice mouse in there. I think I'll start exploring the ideas around what happens when you have Xorg -hal, as I do. Actually, I did that, and problem SOLVED!. -- Kevin O'Gorman, PhD
[gentoo-user] Re: RAID problems - Is udev at fault here?
On 05/16/2010 02:56 PM, Mark Knecht wrote: On Sun, May 16, 2010 at 1:32 PM, waltw41...@gmail.com wrote: On 05/16/2010 10:56 AM, Mark Knecht wrote: I have a newish high-end machine here that's causing me some problems with RAID, but looking at log files and dmesg I don't think the problem is actually RAID and more likely udev. I'm looking for some ideas on how to debug this. The hardware: Asus Rampage II Extreme Intel Core i7-980x 12GB DRAM 5 WD5002ABYS RAID Edition 500GB drives I had an asus mobo that turned out to be great in the long run, but a few of its newer hardware gadgets took months to be well-supported by linux. I'm thinking (completely guessing :) it sounds like a driver that's not setting some bit properly in a hardware register during boot. That turned out to be a problem with the network chip on my asus, which randomly didn't work after reboots. Finally the driver got fixed after I whined a thousand times to the driver maintainer at Broadcom :) It very well could be something like that. I had a Compaq laptop a few years ago which had an ATI chipset in it and which took a long time to get DMA working on the hard drive controller to it was very slow for the first few months. The thing about this is that it's a single 6 port SATA controller in an Intel chipset, albeit because it's the newer chipsets with the newest processor (6 cores, 12 threads) it likely hasn't been seen by too many people yet. Let's assume you're right? I've been trying to determine how udev goes about finding the actual hard drives and assigning them device names. Is there a way that I can get udev to log what it's doing? Any sort of debug messages I can get it to print in a log file somewhere? It is a flaky problem and strangely it doesn't always miss every partition on a given drive. For instance /dev/md3, md5 and md11 3-drive RAID1 arrays. You'd think if it was the controller failing it would fail for all the partitions on a given drive, but it doesn't. It might find sda3 for md3 but miss sda5 for md5. Strange. Hm. Is this your motherboard?: http://usa.asus.com/product.aspx?P_ID=W7i5W4Pw4fH22Mih Being a geek of a certain age, I find that products with names that invoke mega-dose anabolic steroids usually don't fit my lifestyle very well. I do better with product names that contain more sedate character strings like VSOP or MOM. By grepping through /usr/src/linux*/MAINTAINERS I turned up quite a few email addresses at intel.com, none of which seem relevant to RAID or its device drivers, but a polite email asking for a link to the appropriate dev might bring a polite and useful reply. That's how I connected with the appropriate dev at Broadcom, who eventually fixed my ethernet driver.
Re: [gentoo-user] Re: RAID problems - Is udev at fault here?
On Sun, May 16, 2010 at 5:07 PM, walt w41...@gmail.com wrote: SNIP Hm. Is this your motherboard?: http://usa.asus.com/product.aspx?P_ID=W7i5W4Pw4fH22Mih Being a geek of a certain age, I find that products with names that invoke mega-dose anabolic steroids usually don't fit my lifestyle very well. I do better with product names that contain more sedate character strings like VSOP or MOM. By grepping through /usr/src/linux*/MAINTAINERS I turned up quite a few email addresses at intel.com, none of which seem relevant to RAID or its device drivers, but a polite email asking for a link to the appropriate dev might bring a polite and useful reply. That's how I connected with the appropriate dev at Broadcom, who eventually fixed my ethernet driver. Yes, that's the motherboard. I don't care much about the names of things myself. I had limited options for the new i7-980x processor at the time I was ordering the hardware, and I'd never done overclocking before (and technically still haven't) so I got it because it was an Asus board which I've generally had very good luck with. To be clear, the RAID I'm doing is mdadm Linux software RAID and nothing having to do with the on-board RAID controller. The machine uses the standard Linux SATA drivers, or so I think. I like the VSOP idea. :-) - Mark
[gentoo-user] Re: SOLVED: Re: Re: Gentoo decapitated
On 05/16/2010 04:39 PM, Kevin O'Gorman wrote: On Sun, May 16, 2010 at 11:25 AM, walt w41...@gmail.com wrote: I just did the experiment of building xorg-server with the hal useflag *off*, and found that neither keyboard nor mouse worked until I restored the two InputDevice sections that I commented out when I switched to evdev+hal: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 Option AIGLX false InputDevice Mouse0 CorePointer -- restored these two lines InputDevice Keyboard0 CoreKeyboard --- EndSection Section InputDevice Identifier Keyboard0 Driver evdev Option Device /dev/input/event3 EndSection Section InputDevice Identifier Mouse0 Driver evdev Option Protocol auto Option Device /dev/input/event4 Option Emulate3Buttons True EndSection GENIUS. It worked! That which has been dead for 2 weeks is risen! Bless you, my son ;) (I always thought the deadline is the third day.) I could give you that information only after hours of frustrating research and trial-and-error hacking, most of which I've already forgotten, so it's a good thing that I commented those lines out instead of deleting them. Happily for all of us, the xorg devs are well aware of the frustrating user experience with all of this configuration nonsense, and are making very good progress towards automating it.
Re: [gentoo-user] identical drives, different free space!
On Sat, 2010-05-15 at 01:35 -0700, scott n-h wrote:
Have you checked to see if it is following symlinks? Possibly add a -l
option to copy symlinks as symlinks
good idea, I didn't have the -l option. Now I run rsync like this:
sudo /usr/bin/ionice -c 3 /usr/bin/rsync -aAlx --exclude suspend_file
--delete --delete-excluded --delete-before --partial --human-readable /
${MOUNTPT} ${LOGFILE}
Note the -l AND --delete-before.
However I'm STILL filling up the second drive for some unknown reason.
I've added --exclude /usr/portage/distfiles to the rsync options,
since there's no need to back up my distfiles, but I'd like to know why
it's not working...
--
Iain Buchanan iain at pcorp dot com dot au
It doesn't matter whether you win or lose -- until you lose.
[gentoo-user] need more swap
I have a one-off number crunching job that needs a large amount of swap. It is apparently possible to have up to 16TB of swap with an AMD opteron but I cant find out how - anyone here done this? I have a 125GB scssi disk I would like as one large swap but after setup the kernel can only see 2G (normal i386 is up to 32 2G partitions - I found that 5G ram and 12G swap wasnt enough so I now want more! :) BillK
Re: [gentoo-user] need more swap
ah, figured it out - had to be the whole disk, not a partition. BillK On Mon, 2010-05-17 at 08:48 +0800, Bill Kenworthy wrote: I have a one-off number crunching job that needs a large amount of swap. It is apparently possible to have up to 16TB of swap with an AMD opteron but I cant find out how - anyone here done this? I have a 125GB scssi disk I would like as one large swap but after setup the kernel can only see 2G (normal i386 is up to 32 2G partitions - I found that 5G ram and 12G swap wasnt enough so I now want more! :) BillK
Re: [gentoo-user] Re: kdrive use flag quandary
-t doesnt work in this case as emerge wants xorg-server built with the kdrive flag before it will continue processing - which makes sense. BillK On Sun, 2010-05-16 at 15:55 -0700, walt wrote: On 05/15/2010 09:42 PM, William Kenworthy wrote: I am trying to update a laptop after a break of a few months and have an ... anomaly! It suddenly wants the kdrive use flag enabled for xorg-server and sabayon - why? I think kdrive is a minimal xserver built on top of xorg so its not appropriate for a system I want full functionality on - is it? How can I find out whats bringing this use flag in as I cant find anything so far. The method most often suggested is adding the 't' flag to your emerge: #emerge -auNDt world
Re: [gentoo-user] [SOLVED] identical drives, different free space!
So after I excluded distfiles from my rsync, I found that the two partitions had roughly the same free space... strange! How could excluding around 6G of distfiles make two copies of the same thing the same size? Well, it turns out I have the distfiles mounted with --bind to my ftp/pub directory. And looking in the rsync man page: -x, --one-file-system ... Also keep in mind that rsync treats a bind mount to the same device as being on the same filesystem. So my distfiles were being copied in /usr/portage as well as /home/ftp/pub! Unfortunately the only way to get around it seems to be another --exclude directive. At least I understand what's going on now :) thanks for all the suggestions, -- Iain Buchanan iaindb at netspace dot net dot au Mr. Cole's Axiom: The sum of the intelligence on the planet is a constant; the population is growing.
[gentoo-user] Re: kdrive use flag quandary
On 05/16/2010 06:26 PM, Bill Kenworthy wrote: -t doesnt work in this case as emerge wants xorg-server built with the kdrive flag before it will continue processing - which makes sense. AFAICT, the cost of enabling kdrive is trivial. It compiles one more server /usr/bin/Xephyr, so I'd say just enable kdrive and go for it! On Sun, 2010-05-16 at 15:55 -0700, walt wrote: On 05/15/2010 09:42 PM, William Kenworthy wrote: I am trying to update a laptop after a break of a few months and have an ... anomaly! It suddenly wants the kdrive use flag enabled for xorg-server and sabayon - why? I think kdrive is a minimal xserver built on top of xorg so its not appropriate for a system I want full functionality on - is it? How can I find out whats bringing this use flag in as I cant find anything so far. The method most often suggested is adding the 't' flag to your emerge: #emerge -auNDt world
Re: [gentoo-user] Re: kdrive use flag quandary
On Sun, 2010-05-16 at 18:55 -0700, walt wrote: On 05/16/2010 06:26 PM, Bill Kenworthy wrote: -t doesnt work in this case as emerge wants xorg-server built with the kdrive flag before it will continue processing - which makes sense. AFAICT, the cost of enabling kdrive is trivial. It compiles one more server /usr/bin/Xephyr, so I'd say just enable kdrive and go for it! Thanks Walt, thats interesting that gnome-2.28 includes Xephyr via kdrive - bonus :) The system was moved to gnome-2.28 and updated/upgraded overnight and I just have half a dozen pkgs to sort out - after trying 217!) and its done. BillK On Sun, 2010-05-16 at 15:55 -0700, walt wrote: On 05/15/2010 09:42 PM, William Kenworthy wrote: I am trying to update a laptop after a break of a few months and have an ... anomaly! It suddenly wants the kdrive use flag enabled for xorg-server and sabayon - why? I think kdrive is a minimal xserver built on top of xorg so its not appropriate for a system I want full functionality on - is it? How can I find out whats bringing this use flag in as I cant find anything so far. The method most often suggested is adding the 't' flag to your emerge: #emerge -auNDt world
Re: [gentoo-user] need more swap
On Monday 17 May 2010 01:55:23 Bill Kenworthy wrote: ah, figured it out - had to be the whole disk, not a partition. As far as I know you can define a partition, or even a file as swap space. You'll need to set a swap fs on them first before you can use them and then it is a matter of swapon /dev/what_ever. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
