Re: [arch-general] What happened to Powerpill?
On Tue, Apr 5, 2011 at 8:46 AM, Madhurya Kakati mkakati2...@gmail.com wrote: Please, someone restart powerpill development. It was awesome. I had to remove it in order to upgrade to pacman 3.5 but now I can't find it anywhere. The developer's post on the forums indicates that he's been working on a far better replacement, but doesn't have the free time right now to complete it. Perhaps his priorities could be changed if some cash was on the table, perhaps not.
Re: [arch-general] [signoff] kernel26-2.6.38-1
Hi guys, please signoff 2.6.38 series for both arches. Having issues here with ath9k, much slower than it was with 2.6.37. Found this bug re: Ubuntu on Launchpad, haven't checked the kernel tracker: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/735171
Re: [arch-general] [signoff] kernel26-2.6.38-1
On Sat, Mar 19, 2011 at 12:57 AM, Jeff Cook j...@deserettechnology.com wrote: Hi guys, please signoff 2.6.38 series for both arches. Having issues here with ath9k, much slower than it was with 2.6.37. Found this bug re: Ubuntu on Launchpad, haven't checked the kernel tracker: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/735171 Looks like I'm also getting bit by this on another machine that uses ath5k. Watching wireshark on two machines, almost all packets sent to the ath5k card never make it with 2.6.38. I also tested with a compat-wireless tarball from 2011-03-18 with the same results. Reverting to 2.6.37 makes the issue go away. Definitely seems like an unsafe upgrade at least for Atheros users.
Re: [arch-general] [signoff] kernel26-2.6.38-1
On Sat, Mar 19, 2011 at 7:21 AM, Richard Schütz r.sc...@t-online.de wrote: On Sat, Mar 19, 2011 at 12:57 AM, Jeff Cookj...@deserettechnology.com wrote: Having issues here with ath9k, much slower than it was with 2.6.37. Found this bug re: Ubuntu on Launchpad, haven't checked the kernel tracker: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/735171 Looks like I'm also getting bit by this on another machine that uses ath5k. Watching wireshark on two machines, almost all packets sent to the ath5k card never make it with 2.6.38. I also tested with a compat-wireless tarball from 2011-03-18 with the same results. Reverting to 2.6.37 makes the issue go away. Definitely seems like an unsafe upgrade at least for Atheros users. I can confirm that. When running 2.6.38 my downstream with ath9k is about 13 times slower compared to 2.6.37.4. -- Regards, Richard Schütz What kind of network are you using? A person in IRC suggested that these issues might only exist on certain (relatively rare) networks, like 802.11n or ad-hoc. I bisected and wound up with 8aec7af99b1e45 as the culprit, though that doesn't make much sense as that change was merged into 2.6.37. Here is my git bisect log: git bisect start '--' 'drivers/net/wireless/' # bad: [7d2c16befae67b901e6750b845661c1fdffd19f1] ath9k: fix aggregation related interoperability issues git bisect bad 7d2c16befae67b901e6750b845661c1fdffd19f1 # good: [3c0eee3fe6a3a1c745379547c7e7c904aa64f6d5] Linux 2.6.37 git bisect good 3c0eee3fe6a3a1c745379547c7e7c904aa64f6d5 # bad: [bfe3850b0cfca6ba64395e2705d9a51cd044f374] rndis_wlan: scanning, workaround device returning incorrect bssid-list item count. git bisect bad bfe3850b0cfca6ba64395e2705d9a51cd044f374 # good: [f7ec8fb4d6f8f3ecb8b11e9e46ece95aa66139cc] ath9k_hw: Fix eeprom offset for AR9287 devices (PCI/USB) git bisect good f7ec8fb4d6f8f3ecb8b11e9e46ece95aa66139cc # bad: [692d2c0fb36c02ad07d54641c26f48e644b27fbd] b43: rename config option for N-PHY, drop BROKEN git bisect bad 692d2c0fb36c02ad07d54641c26f48e644b27fbd # bad: [8efa5d7d6ad307ae2d220def37ca89594062c40d] ath5k: Check if pci pdev struct is initialized in common functions. git bisect bad 8efa5d7d6ad307ae2d220def37ca89594062c40d # good: [61cde037234c4b8e6497a23f5f236c64cbf9d41d] ath5k: Extend rate_duration git bisect good 61cde037234c4b8e6497a23f5f236c64cbf9d41d # bad: [61790c5f3c5f158821821a00797d94504531839f] iwlagn: fix microcode error on 4965 git bisect bad 61790c5f3c5f158821821a00797d94504531839f # bad: [8aec7af99b1e4594c4bb9e1c48005e6111f97e8e] ath5k: Support synth-only channel change for AR2413/AR5413 git bisect bad 8aec7af99b1e4594c4bb9e1c48005e6111f97e8e # good: [b2b4c69f682a2868411899a77842061dd745884f] ath5k: Tweak power detector delays on RF5111/RF5112 git bisect good b2b4c69f682a2868411899a77842061dd745884f # good: [f08fbf6cf4a31c8df52b21440c7a7e6fbe474b28] ath5k: Update PLL programming for turbo/half/quarter git bisect good f08fbf6cf4a31c8df52b21440c7a7e6fbe474b28 # good: [4c57581d939fd0f8f244b9730812069f4dac308a] ath5k: Skip powertable setting when we are on the same channel git bisect good 4c57581d939fd0f8f244b9730812069f4dac308a I may have done something wrong, I guess. I was testing with compat-wireless and not applying patches uniformly really, so they may have mucked things up, but I was getting some success with commits from Nov. 23, 2010 as well as some failures. I will try bisecting again soon and will probably just end up rebooting and testing each kernel individually that way, which is a seriously lame pain in the rear way to test just one driver.
Re: [arch-general] Python 3 Rationale?
Really please, please don't top post. http://www.river.com/users/share/etiquette/ Who cares! it takes too long to scroll down through the past fifteen generations to get to the relevant part of the message. Well, it takes me one keystroke. Get a better mail client. Whenever I try bottom-posting, my clients complain that I just sent them a blank email. As such, I am in the habit of top-posting because it is what most normal people expect; I suppose Outlook has established this trend. I try to remember to bottom-post when I write mailing lists (not too often), but it doesn't always work out. :( I don't really have a preference for where the post goes. I don't find either annoying. I understand the point in standards but I don't think we should be rude to those who forget/neglect/feel differently.
Re: [arch-general] Benchmarks (GUI)
I usually just run gtkperf. I haven't tried PTS yet but it's hard for me to trust anything that comes out of Phoronix.
Re: [arch-general] Benchmarks (GUI)
2010/10/11 Cédric Girard girard.ced...@gmail.com: On Mon, Oct 11, 2010 at 1:04 PM, Jeff Cook j...@deserettechnology.comwrote: I usually just run gtkperf. I haven't tried PTS yet but it's hard for me to trust anything that comes out of Phoronix. Please explain ? Phoronix is just really unprofessional and unreliable as a media outlet. They constantly post information that is first of all, absolutely atrociously, sometimes incomprehensibly written, and secondly often inaccurate and misrepresentative. They also use amateur reporting practices and lack standards, as we see with their Steam reporting and sending lots of traffic to Valve FTP servers not intended for public usage (for one example). Obviously this does not necessarily reflect directly on their software, but I think it's wise to take anything from Phoronix with a grain of salt. From Jeff -- Cédric Girard
Re: [arch-general] some notes on the radeon gallium driver
My understanding is that r300g is the new default in Mesa 7.9. See http://www.mail-archive.com/mesa-com...@lists.freedesktop.org/msg23390.html . Does this mean that Arch will automatically switch to it on release of Mesa or will extra steps be required?
Re: [arch-general] Xorg 1.9 - This traing is going to hell.
The only problem I've had is slow nvidia rendering with the stable drivers. Upgraded to nvidia-beta and all is better now. For those who might not know, you can upgrade to nvidia-beta by doing this: 1. Install a pacman wrapper that searches AUR too, I use clyde. 2. sudo clyde -Rd nvidia nvidia-utils 3. sudo clyde -S nvidia-beta --noconfirm You also go the old-fashioned way and just grab the PKGBUILD from AUR, in which case you remove the packages with pacman -Rd and then cd into the directory that contains the PKGBUILD and makepkg -i.
Re: [arch-general] What broke ctrl+c ??
On Sun, Jul 18, 2010 at 5:58 PM, David C. Rankin drankina...@suddenlinkmail.com wrote: On 07/17/2010 05:38 PM, Jeff Cook wrote: I had this problem a while back. In my case, I had compiled a random git checkout from awesomewm and that had a bug that was the cause of the failure. If you're using any beta or development branches of your window manager, you might want to try stable. Also, try removing any .xmodmap or other such configurations. Been through any config file I would have and I have no xmodmap or other custom x files. No beta apps at all. I am running (trying to run) kernel26-2.6.34.1-1-x86_64.pkg.tar.xz xf86-video-ati-6.13.1-1-x86_64.pkg.tar.xz and it is not going well... Are you sure? If this is restricted to gnome-terminal then you either probably have a gnome config file somewhere breaking it or there is some obscure bug in gnome-terminal and you should bring this up with them. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
Re: [arch-general] What broke ctrl+c ??
I had this problem a while back. In my case, I had compiled a random git checkout from awesomewm and that had a bug that was the cause of the failure. If you're using any beta or development branches of your window manager, you might want to try stable. Also, try removing any .xmodmap or other such configurations. On Sat, Jul 17, 2010 at 2:58 PM, Adriano Moura adriano.l...@gmail.comwrote: 2010/7/17 David C. Rankin drankina...@suddenlinkmail.com On 07/16/2010 09:52 PM, David C. Rankin wrote: Guys, I have a strange problem. ctrl+c is completely broken on my system. It won't cancel Jack Schit. It is the strangest thing I've seen. I apologize if there is some archain Arch notice on this I apologize, I've missed it. This is easy to test. Just to 'ping anywhere' and then try and kill it with ctrl+c. I have to open another terminal and either 'killall ping' or kill the pid to get the thing to stop. Same thing happens if I mistype a cli and need to cancel the execution (like if I mistype a ' instead of a and the script continues on a new line) What's up with this? OK I've narrowed it down to gnome-terminal. If I use konsole (kde3 or kde4) ctrl+c works just fine. Can anyone else try in gnome-terminal and see if ctrl+c is broken for you? Just type 'ping whatever' and then try to kill ping with crtl+c. I can't and that's a problem. I'm using using gnome-terminal 2.30.2-1 -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com Does Xterm and the VT's works? if so, it must be something with the gnome terminal :)
Re: [arch-general] Nouveau problem
Try following the nouveau page on ArchWiki and asking in some nouveau-specific support channels, like #nouveau on freenode. 2010/7/17 Lukáš Jirkovský l.jirkov...@gmail.com On 17 July 2010 17:01, Lars Tennstedt o...@larstennstedt.de wrote: Hello again, the graphics card on my old pc is a Nvidia GeForce 3 Ti 200. Before the release of the version 1.8 of X.org I used the proprietary driver. Because this is not possible anymore, I tried the nouveau driver and everything I can get is a blank screen. The vesa driver works correctly with the same configuration files. Thanks for your time! Bye Lars Today new nvidia legacy drivers were released, maybe you can try them.
Re: [arch-general] pidgin memory leak?
Perhaps you'll find more interest on the pidgin mailing lists. On Fri, May 29, 2009 at 6:22 PM, Jon Kristian Nilsen jokr.nil...@gmail.com wrote: Also try msn-pecan to see if maybe that one works better. -J On Sat, May 30, 2009 at 1:55 AM, ludovic coues cou...@gmail.com wrote: if pidgin is a problem, you can give a try to emesene. But I don't know if it have sound. And don't use msn dailly -- http://divineintervention.no
