[gentoo-ppc-user] Are there any Pegasos users?
Hi here, are there any Pegasos users using Gentoo? Especially the hardware platform Pegasos II? I am looking for experiences about building an own kernel for this architecture. I compile them by myself for some years, but I think I could be better if I find someone else who is building kernels for Pegasos II. I am interested to exchange/talk about config files and so on. Unfortunately Gentoo seems to have dropped kernel support for Pegasos for some years. No installation disk contains a kernel for this hardware. Bye Johannes -- --//-- //Johannes R. Geiss Zaurus, Pegasos, Amiga and C64 user \\ // PGP at https://pegasos.dnsalias.org/~jgeiss/pgpkey.txt --\X/- signature.asc Description: PGP signature
Re: [gentoo-user] the best filesystem for server: XFS or JFS (or?)
Thanks for replies. As I had expected, they brought even more uncertainty then I had before... :-) ext3/4: I excluded them because as I understand, they do not support snapshots (only with lvm, which I do not use, and I've hreard snapshots in lvm are not very effective, or something like that). Next minus-point, I tried resizing of ext3/lvm once in the past and remember it was a real pain in a**... reiserfs/reiser4: Future of these fs seems to be somehow vague, at least to me. And I do not know if it can handle snaphosts and resizing. xfs power-off: I have always thought, journaling is there to prevent data loss during unexpected power-off. And now I read I could loose data even with journaled fs...? jfs power-off: the same. How is it possible, I could loose data with such a mature journaled filesystem during power-off? btrfs: never heard of it. Is it stable enough to be used? I just checkt man-page of mount, and it does not show btrfs as supported filesystem... Jarry
Re: [gentoo-user] the best filesystem for server: XFS or JFS (or?)
On Tue, 22 Mar 2011 09:13:48 +0100, Mr. Jarry wrote: ext3/4: I excluded them because as I understand, they do not support snapshots (only with lvm, which I do not use, and I've hreard snapshots in lvm are not very effective, or something like that). Next minus-point, I tried resizing of ext3/lvm once in the past and remember it was a real pain in a**... Resizing LVM and ext3/4 is as easy as it gets lvresize -L+5G /dev/vg/lv resize2fs /dev/vg/lv No need to mess around with cfdisk/fdisk/parted. Also, letting LVM handle snapshots means you have a consistent way of doing things, independent of the filesystem. -- Neil Bothwick WinErr 103: Error buffer overflow - Too many errors encountered. Additional errors may not be displayed or recorded. signature.asc Description: PGP signature
Re: [gentoo-user] the best filesystem for server: XFS or JFS (or?)
On 03/21/2011 08:32:22 PM, Jarry wrote: Hi, I'm looking for the best filesystem for a small multi-purpose server with a couple of services running (ftp, web, mail, mysql). For me very important features are: snapshot (will be used for backup, must be native without lvm) journaling resizeable (if possible online) I'd like to suggest BTRFS. I know, there is a general warning because it's a new file system. But I haven't found any issues myself nor those being mentioned on the net. I have several machines running BTRFS for all partitions except / (root) since , AFAIK, BTRFS on the root partition needs a patched grub I had crashes (power down and hard reset due to X11 crashes) but my BTRFS files system recover fast and without any glitch. You might have a look at https://btrfs.wiki.kernel.org/index.php/Main_Page From that The main Btrfs features include: Extent based file storage (2^64 max file size) Space efficient packing of small files Space efficient indexed directories Dynamic inode allocation Writable snapshots Subvolumes (separate internal filesystem roots) Object level mirroring and striping Checksums on data and metadata (multiple algorithms available) Compression Integrated multiple device support, with several raid algorithms Online filesystem check (not yet implemented) Very fast offline filesystem check Efficient incremental backup and FS mirroring Online filesystem defragmentation BUT, you need a (very) recent kernel. The most recent bad bug when using coreutils-8.10 (http://bugs.gentoo.org/show_bug.cgi?id=353907) has been fixed in the 2.6.38 kernel but not for ext4, yet (AFAIK). Helmut.
[gentoo-user] Bash $VAR expansion escapes the dollar instead of expanding
I have an env var, WWW=/home/www/felix, which I have always used with tab completion without problems. cd $WWW/httabphtab20110318 would expand in steps cd /home/www/felix/htdocs/ cd /home/www/felix/htdocs/photos/ cd /home/www/felix/htdocs/photos/20110318 But some recent bash upgrade has scuppered this. tab no longer expands the $WWW; instead, it escapes the $, adds a space at the end, and thinks itself clever. cd \$WWW/ht ph which does me no good. I'll be danged if I can figure out any google-fu to search for this, and 'bash help' and 'info bash' have done me no good either. I do not know which specific bash upgrade changed this, since I don't have very many of these env vars I used similarly. The current bash --version is 4.2.8(2)-release, gentoo version is app-shells/bash-4.2_p8. -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman rocket surgeon / fe...@crowfix.com GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o
Re: [gentoo-user] the best filesystem for server: XFS or JFS (or?)
Mr. Jarry wrote: Thanks for replies. As I had expected, they brought even more uncertainty then I had before... :-) ext3/4: I excluded them because as I understand, they do not support snapshots (only with lvm, which I do not use, and I've hreard snapshots in lvm are not very effective, or something like that). Next minus-point, I tried resizing of ext3/lvm once in the past and remember it was a real pain in a**... reiserfs/reiser4: Future of these fs seems to be somehow vague, at least to me. And I do not know if it can handle snaphosts and resizing. xfs power-off: I have always thought, journaling is there to prevent data loss during unexpected power-off. And now I read I could loose data even with journaled fs...? jfs power-off: the same. How is it possible, I could loose data with such a mature journaled filesystem during power-off? btrfs: never heard of it. Is it stable enough to be used? I just checkt man-page of mount, and it does not show btrfs as supported filesystem... Jarry This is usually the case, more confusion. Every file system has its strengths and its weaknesses. Here is some info BTRFS: https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices#Current_Status This is what I suggest. Find out which file systems support the snapshot, since that is one thing that you have to have and a lot of file systems don't support it. Then research those to see which one matches your needs the closest. Keep in mind, none of them will be perfect. If you have large files, find out which one handles those best. If you have a lot of small files, which one handles those best. You will always have some trade offs tho. Example, XFS may be perfect but you may have to buy a really good UPS to work with your rig. It may be that EXT4 works best but still lacks something with regard to speed. Just another trade off. Just start with the must haves and work your way down the list until one file system is left. That will likely be your file system. I think the biggest thing, don't expect to find a file system that is perfect. None of them are really. Dale :-) :-)
[gentoo-user] color in terminals with white background
Hi, All, For quite a few years I've had a low level irritation with the font colors in my x11-terms/terminal. I like a white background and a black font in my terminals, and that satisfies me perfectly 99.44% of the time. The colors that appear by default with the ls command are perfect. But the colors that appear when I do an emerge -ptDuNv, and the colors that appear when interactively merging config files with dispatch-conf (configured to use vimdiff) are sometimes completely unreadable. In particular, the light yellow font on a white background that portage uses sometimes is almost invisible. I have tried now and then in the past to develop my own color scheme, but without notable success. I once tried making the yellow darker in various ways, and that helped, but then the (formerly yellow) text became unreadable if I highlighted it. I tried dark backgrounds for a while, but I guess I have too many years of reading black print on white pages; dark backgrounds are just wrong for me. And I haven't found any satisfactory answers with web searches. Is there anybody with a font color scheme they like for use on a white background? Thanks for any suggestions, John Blinka
Re: [gentoo-user] the best filesystem for server: XFS or JFS (or?)
Am 22.03.2011 09:13, schrieb Mr. Jarry: Thanks for replies. As I had expected, they brought even more uncertainty then I had before... :-) ext3/4: I excluded them because as I understand, they do not support snapshots (only with lvm, which I do not use, and I've hreard snapshots in lvm are not very effective, or something like that). Next minus-point, I tried resizing of ext3/lvm once in the past and remember it was a real pain in a**... Neil already pointed out that resizing is plain easy. Increasing the size online is a matter of seconds. Shrinking needs to be done offline after an `e2fsck -f` but is no problem, either. reiserfs/reiser4: Future of these fs seems to be somehow vague, at least to me. And I do not know if it can handle snaphosts and resizing. Reiserfs-3 supports increasing the size but not shrinking (AFAIK). Performance characteristics are similar to Ext3 in this regard. xfs power-off: I have always thought, journaling is there to prevent data loss during unexpected power-off. And now I read I could loose data even with journaled fs...? Journalling is better suited for system crashes than power failures. Things get especially ugly when you think about write caches in HDDs or RAID controllers. Additionally, the main purpose of journalling is to protect the file system, not the data. Normally, journals only contain metadata changes like space allocations to files but not the actual data written to it. Even good old Ext3 might put random junk at the end of your files when it is mounted with journal=writeback during a crash. This is basically a speed/security tradeoff. When you read up about the various journal options for Ext3, you will understand it better. jfs power-off: the same. How is it possible, I could loose data with such a mature journaled filesystem during power-off? btrfs: never heard of it. Is it stable enough to be used? I just checkt man-page of mount, and it does not show btrfs as supported filesystem... Wikipedia has information about it. Basically, it will be replacement of Ext4. Hope this helps, Florian Philipp signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] Re: Compositing too slow in KDE
On 03/20/2011 12:09 PM, Mick wrote: On Sunday 20 March 2011 18:38:00 Mick wrote: On Saturday 19 March 2011 23:02:11 Jorge Martínez López wrote: I also have an ATI card and I do suffer the slow compositing. I solved it by switching back to the classic Mesa (instead of Gallium). Thanks Jorge, I switched to classic too and now it does not crash - however: 1. When I start kde compositing is disabled. 2. If I click on Resume Compositing, then the first time I try it I get a notification saying: Compositing has been suspended by another application and it remains disabled. 3. The second time I try to resume compositing it works! 4. If at that stage I exit/restart KDE compositing is disabled again ... o_O Why is this happening? What other application is clashing or causing compositing not to take? BTW, I just tried this on an older Pentium 4 32bit box with an ATI Radeon X600 (RV380) and it is exhibiting similar symptoms, except that if I try to resume compositing a second time kwin crashes. I have an AMD Phenom II X4 940 with an Radeon 4870 that loves to crash when I turn on compositing. OpenGL works wonderfully until it crashes kwin. XRender chews up so much CPU I'd rather not have it. I have an AMD Athlon II X4 635 with an onboard Radeon 4200 that loves to crash when I turn on compositing. Both these boxes have SB700/SB800 chipsets. I use xdm on the former and manually run X on the other. Same problem on both. I did not have this problem in xorg-server 1.7 series.
Re: [gentoo-user] the best filesystem for server: XFS or JFS (or?)
On Tue, 22 Mar 2011 17:05:27 +0100, Florian Philipp wrote: reiserfs/reiser4: Future of these fs seems to be somehow vague, at least to me. And I do not know if it can handle snaphosts and resizing. Reiserfs-3 supports increasing the size but not shrinking (AFAIK). Performance characteristics are similar to Ext3 in this regard. Reiser3 does support shrinking, but not online. XFS doesn't support shrinking under any circumstances. -- Neil Bothwick The severity of the itch is inversely proportional to the reach. signature.asc Description: PGP signature
Re: [gentoo-user] color in terminals with white background
On Tue, 22 Mar 2011 11:43:54 -0400, John Blinka wrote: For quite a few years I've had a low level irritation with the font colors in my x11-terms/terminal. I like a white background and a black font in my terminals, and that satisfies me perfectly 99.44% of the time. The colors that appear by default with the ls command are perfect. But the colors that appear when I do an emerge -ptDuNv, and the colors that appear when interactively merging config files with dispatch-conf (configured to use vimdiff) are sometimes completely unreadable. In particular, the light yellow font on a white background that portage uses sometimes is almost invisible. You can remap the colours portage uses in /etc/portage/color.map. See man portage and man color.map for details. -- Neil Bothwick c:Press Enter to Exit signature.asc Description: PGP signature
Re: [gentoo-user] color in terminals with white background
On 03/22/2011 08:43 AM, John Blinka wrote: Hi, All, For quite a few years I've had a low level irritation with the font colors in my x11-terms/terminal. I like a white background and a black font in my terminals, and that satisfies me perfectly 99.44% of the time. The colors that appear by default with the ls command are perfect. But the colors that appear when I do an emerge -ptDuNv, and the colors that appear when interactively merging config files with dispatch-conf (configured to use vimdiff) are sometimes completely unreadable. In particular, the light yellow font on a white background that portage uses sometimes is almost invisible. I have tried now and then in the past to develop my own color scheme, but without notable success. I once tried making the yellow darker in various ways, and that helped, but then the (formerly yellow) text became unreadable if I highlighted it. I tried dark backgrounds for a while, but I guess I have too many years of reading black print on white pages; dark backgrounds are just wrong for me. And I haven't found any satisfactory answers with web searches. Is there anybody with a font color scheme they like for use on a white background? Thanks for any suggestions, Will someone please answer John so I can use it too? And for that matter, does anyone who uses a dark background AND uses vimdiff as their etc-update tool run up against the same issue: vimdiff mode and certain syntax highlighting rules combine to make some sections of documents completely illegible. My workarounds are to use vim's syntax off in *each* window (PITA) which solves the vimdiff problem. For poor color, I use xterm's Ctrl-Middle menu to go dark background. And most of root's vim sessions seem to think my background is dark, so I'm constantly have to do :set bg=light. I use xterm.
Re: [gentoo-user] Re: Compositing too slow in KDE
Bill Longman wrote: On 03/20/2011 12:09 PM, Mick wrote: On Sunday 20 March 2011 18:38:00 Mick wrote: On Saturday 19 March 2011 23:02:11 Jorge Martínez López wrote: I also have an ATI card and I do suffer the slow compositing. I solved it by switching back to the classic Mesa (instead of Gallium). Thanks Jorge, I switched to classic too and now it does not crash - however: 1. When I start kde compositing is disabled. 2. If I click on Resume Compositing, then the first time I try it I get a notification saying: Compositing has been suspended by another application and it remains disabled. 3. The second time I try to resume compositing it works! 4. If at that stage I exit/restart KDE compositing is disabled again ... o_O Why is this happening? What other application is clashing or causing compositing not to take? BTW, I just tried this on an older Pentium 4 32bit box with an ATI Radeon X600 (RV380) and it is exhibiting similar symptoms, except that if I try to resume compositing a second time kwin crashes. I have an AMD Phenom II X4 940 with an Radeon 4870 that loves to crash when I turn on compositing. OpenGL works wonderfully until it crashes kwin. XRender chews up so much CPU I'd rather not have it. I have an AMD Athlon II X4 635 with an onboard Radeon 4200 that loves to crash when I turn on compositing. Both these boxes have SB700/SB800 chipsets. I use xdm on the former and manually run X on the other. Same problem on both. I did not have this problem in xorg-server 1.7 series. I have a very similar setup and it works fine here, AMD Phenom II X4 955 Deneb 3.2GHz with a Nvidia GT-220 video card. I also have the SB700/SB800 chipset as well, Gigabyte mobo. The biggest difference I see is the video card as far as hardware is concerned. Software, I'm on xorg-server-1.9 here. I never tried the older series on this rig. I also still have a xorg.conf file too. May not matter but just upgraded to a 2.6.38 kernel. Also, no hal here either which is why I went with that xorg version during my install. I hope this little bit of info helps in some small way. If you need more info about my setup, let me know. Dale :-) :-)
Re: [gentoo-user] the best filesystem for server: XFS or JFS (or?)
On 3/22/2011 1:13 AM, Mr. Jarry wrote: Thanks for replies. As I had expected, they brought even more uncertainty then I had before... :-) ext3/4: I excluded them because as I understand, they do not support snapshots (only with lvm, which I do not use, and I've hreard snapshots in lvm are not very effective, or something like that). Next minus-point, I tried resizing of ext3/lvm once in the past and remember it was a real pain in a**... Any Mysql db smaller than 200GB is being backed up by a combination of LVM/Ext3 at a large Internet company with a big purple Y. It's mildly painful to setup, but RHEL uses LVM by default so it's just a matter of resizing to get the partitions you need. Once that's done you can kick off snapshots with very little effort. Not sure where you heard it was ineffective and I'd ignore further information from that source. kashani
Re: [gentoo-user] the best filesystem for server: XFS or JFS (or?)
On Monday 21 March 2011 20:32:22 Jarry wrote: Hi, I'm looking for the best filesystem for a small multi-purpose server with a couple of services running (ftp, web, mail, mysql). For me very important features are: snapshot (will be used for backup, must be native without lvm) journaling resizeable (if possible online) After a little research I have found two candidates: JFS (created by IBM) jfs = no barriers = not safe for your data. Use something different.
[gentoo-user] Problems starting OpenLDAP
Hi there, I try to start an LDAP-service for managing by eMail-Addresses centralised on my server. Unfortunately I constantly fail to start slapd. I tried a lot of documentations I've found on the web, including Gentoo's non-official doc at http://www.gentoo.org/doc/en/ldap-howto.xml as well as http://www.yolinux.com/TUTORIALS/LinuxTutorialLDAP.html but to no avail. The daemon slapd only starts as root and connecting to it via ldapadd -f stooges.ldif -xv -D cn=StoogeAdmin,o=stooges \ -h 127.0.0.1 -w secret1 always fails with ldap_initialize( ldap://127.0.0.1 ) ldap_bind: Invalid credentials (49) I suspect something is wrong with my backend database. Has anybody installed and started OpenLDAP successfully on Gentoo? I am interested in config files and which components/use flags are involved. I have installed cyrus-sasl-2.1.23-r1, openldap-2.4.24 Bye Johannes -- --//-- //Johannes R. Geiss Zaurus, Pegasos, Amiga and C64 user \\ // PGP at https://pegasos.dnsalias.org/~jgeiss/pgpkey.txt --\X/- signature.asc Description: PGP signature
Re: [gentoo-user] Re: Compositing too slow in KDE
On Tuesday 22 March 2011 16:45:54 Dale wrote: Bill Longman wrote: On 03/20/2011 12:09 PM, Mick wrote: On Sunday 20 March 2011 18:38:00 Mick wrote: On Saturday 19 March 2011 23:02:11 Jorge Martínez López wrote: I also have an ATI card and I do suffer the slow compositing. I solved it by switching back to the classic Mesa (instead of Gallium). Thanks Jorge, I switched to classic too and now it does not crash - however: 1. When I start kde compositing is disabled. 2. If I click on Resume Compositing, then the first time I try it I get a notification saying: Compositing has been suspended by another application and it remains disabled. 3. The second time I try to resume compositing it works! 4. If at that stage I exit/restart KDE compositing is disabled again ... o_O Why is this happening? What other application is clashing or causing compositing not to take? BTW, I just tried this on an older Pentium 4 32bit box with an ATI Radeon X600 (RV380) and it is exhibiting similar symptoms, except that if I try to resume compositing a second time kwin crashes. I have an AMD Phenom II X4 940 with an Radeon 4870 that loves to crash when I turn on compositing. OpenGL works wonderfully until it crashes kwin. XRender chews up so much CPU I'd rather not have it. I have an AMD Athlon II X4 635 with an onboard Radeon 4200 that loves to crash when I turn on compositing. Both these boxes have SB700/SB800 chipsets. I use xdm on the former and manually run X on the other. Same problem on both. I did not have this problem in xorg-server 1.7 series. I have a very similar setup and it works fine here, AMD Phenom II X4 955 Deneb 3.2GHz with a Nvidia GT-220 video card. I also have the SB700/SB800 chipset as well, Gigabyte mobo. The biggest difference I see is the video card as far as hardware is concerned. Software, I'm on xorg-server-1.9 here. I never tried the older series on this rig. I also still have a xorg.conf file too. May not matter but just upgraded to a 2.6.38 kernel. Also, no hal here either which is why I went with that xorg version during my install. I hope this little bit of info helps in some small way. If you need more info about my setup, let me know. So this seems like the xorg-1.9 driver won't play nicely with ATI video cards. FYI mesa classic seems to be better than gallium, although both crash. As already reported xrender works, but eats up resources. Will have to wait for later versions it seems. Thanks for your replies. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] color in terminals with white background
On Tuesday 22 March 2011 16:30:28 Bill Longman wrote: On 03/22/2011 08:43 AM, John Blinka wrote: Hi, All, For quite a few years I've had a low level irritation with the font colors in my x11-terms/terminal. I like a white background and a black font in my terminals, and that satisfies me perfectly 99.44% of the time. The colors that appear by default with the ls command are perfect. But the colors that appear when I do an emerge -ptDuNv, and the colors that appear when interactively merging config files with dispatch-conf (configured to use vimdiff) are sometimes completely unreadable. In particular, the light yellow font on a white background that portage uses sometimes is almost invisible. I have tried now and then in the past to develop my own color scheme, but without notable success. I once tried making the yellow darker in various ways, and that helped, but then the (formerly yellow) text became unreadable if I highlighted it. I tried dark backgrounds for a while, but I guess I have too many years of reading black print on white pages; dark backgrounds are just wrong for me. And I haven't found any satisfactory answers with web searches. Is there anybody with a font color scheme they like for use on a white background? Thanks for any suggestions, Will someone please answer John so I can use it too? And for that matter, does anyone who uses a dark background AND uses vimdiff as their etc-update tool run up against the same issue: vimdiff mode and certain syntax highlighting rules combine to make some sections of documents completely illegible. My workarounds are to use vim's syntax off in *each* window (PITA) which solves the vimdiff problem. For poor color, I use xterm's Ctrl-Middle menu to go dark background. And most of root's vim sessions seem to think my background is dark, so I'm constantly have to do :set bg=light. I use xterm. Sorry I don't have an answer to the OP, although Neil's suggestion should allow him to get rid of yellow fg colour. @Bill: Is colordiff any better/different than vimdiff? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Compositing too slow in KDE
Mick wrote: On Tuesday 22 March 2011 16:45:54 Dale wrote: I have a very similar setup and it works fine here, AMD Phenom II X4 955 Deneb 3.2GHz with a Nvidia GT-220 video card. I also have the SB700/SB800 chipset as well, Gigabyte mobo. The biggest difference I see is the video card as far as hardware is concerned. Software, I'm on xorg-server-1.9 here. I never tried the older series on this rig. I also still have a xorg.conf file too. May not matter but just upgraded to a 2.6.38 kernel. Also, no hal here either which is why I went with that xorg version during my install. I hope this little bit of info helps in some small way. If you need more info about my setup, let me know. So this seems like the xorg-1.9 driver won't play nicely with ATI video cards. FYI mesa classic seems to be better than gallium, although both crash. As already reported xrender works, but eats up resources. Will have to wait for later versions it seems. Thanks for your replies. That is what I was thinking but I have VERY little experience with ATI cards. I have one but only used it to install the basics of this new rig. No GUI, just a console. I did notice there is a xorg 1.9.5 in the tree. I'm not sure when it was added but if you are not already using it, it may be worth a try. It could fix the issue you are having. It seems you have a newer card and as usual, they can lag a little bit when it comes to fixes. That is true for ATI and Nvidia I guess. Glad the info help eliminate hardware problems at least. Dale :-) :-)
Re: [gentoo-user] Re: Compositing too slow in KDE
On 03/22/2011 03:32 PM, Mick wrote: On Tuesday 22 March 2011 16:45:54 Dale wrote: Bill Longman wrote: On 03/20/2011 12:09 PM, Mick wrote: On Sunday 20 March 2011 18:38:00 Mick wrote: On Saturday 19 March 2011 23:02:11 Jorge Martínez López wrote: I also have an ATI card and I do suffer the slow compositing. I solved it by switching back to the classic Mesa (instead of Gallium). Thanks Jorge, I switched to classic too and now it does not crash - however: 1. When I start kde compositing is disabled. 2. If I click on Resume Compositing, then the first time I try it I get a notification saying: Compositing has been suspended by another application and it remains disabled. 3. The second time I try to resume compositing it works! 4. If at that stage I exit/restart KDE compositing is disabled again ... o_O Why is this happening? What other application is clashing or causing compositing not to take? BTW, I just tried this on an older Pentium 4 32bit box with an ATI Radeon X600 (RV380) and it is exhibiting similar symptoms, except that if I try to resume compositing a second time kwin crashes. I have an AMD Phenom II X4 940 with an Radeon 4870 that loves to crash when I turn on compositing. OpenGL works wonderfully until it crashes kwin. XRender chews up so much CPU I'd rather not have it. I have an AMD Athlon II X4 635 with an onboard Radeon 4200 that loves to crash when I turn on compositing. Both these boxes have SB700/SB800 chipsets. I use xdm on the former and manually run X on the other. Same problem on both. I did not have this problem in xorg-server 1.7 series. I have a very similar setup and it works fine here, AMD Phenom II X4 955 Deneb 3.2GHz with a Nvidia GT-220 video card. I also have the SB700/SB800 chipset as well, Gigabyte mobo. The biggest difference I see is the video card as far as hardware is concerned. Software, I'm on xorg-server-1.9 here. I never tried the older series on this rig. I also still have a xorg.conf file too. May not matter but just upgraded to a 2.6.38 kernel. Also, no hal here either which is why I went with that xorg version during my install. I hope this little bit of info helps in some small way. If you need more info about my setup, let me know. So this seems like the xorg-1.9 driver won't play nicely with ATI video cards. FYI mesa classic seems to be better than gallium, although both crash. As already reported xrender works, but eats up resources. Will have to wait for later versions it seems. Well after fifteen minutes of no crashes, here are my settings: $ emerge -pv xorg-server mesa cairo $(qlist -IC x11-drivers) These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] x11-drivers/radeon-ucode-20110106 0 kB [ebuild R ] media-libs/mesa-7.9.1 USE=classic nptl -debug -gallium -gles -llvm -motif -pic (-selinux) VIDEO_CARDS=radeon -intel -mach64 -mga -nouveau -r128 -savage -sis -tdfx -via -vmware 0 kB [ebuild R ] x11-base/xorg-server-1.9.5 USE=ipv6 kdrive nptl udev xorg -dmx -doc -minimal -static-libs -tslib 0 kB [ebuild R ] x11-libs/cairo-1.10.2-r1 USE=X opengl qt4 svg xcb (-aqua) -debug -directfb -doc (-drm) (-gallium) (-openvg) -static-libs 0 kB [ebuild R ] x11-drivers/xf86-input-evdev-2.6.0 0 kB [ebuild R ] x11-drivers/xf86-input-keyboard-1.5.0 0 kB [ebuild R ] x11-drivers/xf86-input-mouse-1.6.0 0 kB [ebuild R ] x11-drivers/xf86-video-ati-6.14.0 0 kB My kernel is 2.6.36-r5 gentoo-sources running on the AMD Athlon II X4 machine: $ zgrep RADEON /proc/config.gz CONFIG_DRM_RADEON=m CONFIG_DRM_RADEON_KMS=y CONFIG_FB_RADEON=y CONFIG_FB_RADEON_I2C=y CONFIG_FB_RADEON_BACKLIGHT=y # CONFIG_FB_RADEON_DEBUG is not set Wonderfully wobbly windows once again, without widespread (and unwelcomed) untimely terminations.
Re: [gentoo-user] Re: terrible performance with btrfs on LVM2 using a WD 2TB green drive
On Wed, 2011-03-16 at 08:29 +0800, Bill Kenworthy wrote: On Tue, 2011-03-15 at 15:26 +, James wrote: Bill Kenworthy billk at iinet.net.au writes: I have recently added a WD 2TB green drive to two systems and am finding terrible performance with btrfs on an LVM using these drives. Just some feedback now Ive fixed it. Moved all the valuable data off the lv, dropped the rest and shrunk the vg off the disk. Recreated the partitions using fdisk and restored the lv and btrfs. Only the initial partitioning and the pv were set up specifically 4k aware. As a simple benchmark using dirvish to backup in the same fashion as I was previously, time went from 18-19 minutes down to just over 3 minutes - ~6 time speedup, same times as on older disks using reiserfs. I feel reiserfs is a little faster at this, but not by much and no solid figures as too much has changed. I'm happy! BillK
