openSUSE Factory April 2009

factory@lists.opensuse.org

86 participants
67 discussions

[opensuse-factory] Plans and Issues for ATI fglrx Driver for 11.2?

by David C. Rankin

Listmates, There are 2 issues that need to be addressed regarding the fglrx driver and the upcoming 11.2 release. Currently in 11.1, there are many laptop cards supposedly "supported" by the ATI driver that crash or hardlock when the driver is installed. Currently my X1200 is one, the 200 is another from the list (I'm not sure what the technical card architecture is for the "200"). Suffice it to say, this is a significant problem for all affected users. The issues that need to be addressed pre-11.2 are: (1) Performance issues and crashes caused by the ATI driver. Recent driver problems: The 9-2 driver release caused my Toshiba 205d laptop to reboot on xdm start and the 9-3 driver caused my laptop to hardlock if glxgears was started. All fglrx drivers 8-10 through 8-12 had performance of less than 60% of the 8-9 driver. Compounding the problem is the fact that nothing prior to the 8-12 driver will even compile or run on 11.1 or later (presuming 11.2 as well) Thankfully, there are some cards that seem to do OK with the recent 9-3 driver on 11.1, but it is hit or miss ...and... the fact that it works on "some" does nothing to address and help the users where it "does not" work. Before the 11.2 release, Novell needs to get a handle on what cards will and will not run with the ATI driver and at least incorporate a warning or release note for those with affected hardware. (2) Confirm - ATI driver support will be dropped for all R300-R500 ATI cards post 9-3 driver release (per phoronix.com ATI forum). This is another *biggie* Novell needs to get its arms around, to again, either incorporate into the installer a way to not install the driver on non-supported hardware or identify and warn about the lack of support for all R300-R500 cards. That means no (nada) fglrx driver support for the R300-R500 series cards which include the: 9500, 9600, 9700, 9800, X300, X550, X600, X700, X800, X850 AllInWonder, and X1050 cards affecting all laptops bought before Q3 2005 (or January 2007 in the case of the X1050). All of which are still *very* prevalent in the group of laptops that make up the installed user base today and will continue to do so through 11.2 release. This issue of dropping support is separate and apart from issue (1) above because the group of cards in (1) are supposedly still supported. Other Thoughts: After Stefan Dirsch handed over the reins of driver maintainer to Bob Walmsley <bob(a)walmsley.com.au> I guess he is now the guy that this should be coordinated through. I am glad to try and help, and to run test cases, etc. since I drew the black bean in laptop selection so let me know if/when there are new cases to test. I follow the ATI driver releases and test each one so I have a good handle on where things stand today. The problem is that Novell needs to use its resources to get a working partner in ATI to address some of these issues. Luugi Marsan <atilinuxnovellbugs(a)ati.com> was in the past the ATI contact, but at present, I haven't a clue who the ATI contact is or even if there is one. Without a good contact, we are dead-in-the-water getting any of these issues addressed and we are guaranteed a significant number of stranded users if these issues are not addressed. Right now the 8-9 driver works fine for 10.3 and 11.0, but unfortunately it is incompatible with 11.1. The ATI issues prevent me, and all others affected, from being able to move to 11.1. Hopefully, if Novell will start now to address some of these driver issues with ATI, then by 11.2 release they have a good chance of ironed out. With a desktop, you can always rip the ATI card out and replace it. With a laptop ... you are kind-of stuck. -- 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 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years, 10 months

[opensuse-factory] Question about beagle

by Daniel Fuhrmann

There are many complains about beagle. Does anybody use this dog? My first step with a new system is to deinstall beagle. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years, 12 months

[opensuse-factory] gcc miscompilation on Factory i586?

by Wolfgang Rosenauer

Hi, I've got a real weird issue by trying to update mozilla-nss for Factory what I can only interpret as compiler issue or very weird coding issue. mozilla-nss is running a comprehensive test suite during build which currently only seems to fail on openSUSE_Factory i586. It apparently works on x86_64, all older distributions and also in Factory_staging. https://build.opensuse.org/package/show?package=mozilla-nss&project=mozilla… In the failing buildlog one can see that it's crashing on a tool called signtool with free() on an invalid pointer. (search for "- FAILED"). When I build locally I also get those cores dumped and looked into two of them which show the following stack: (gdb) bt #0 0xb7be39d6 in raise () from /lib/libc.so.6 #1 0xb7be52d8 in abort () from /lib/libc.so.6 #2 0xb7c1fa25 in ?? () from /lib/libc.so.6 #3 0xb7c259c5 in ?? () from /lib/libc.so.6 #4 0xb7c2727b in free () from /lib/libc.so.6 #5 0xb7d45ab7 in PR_Free () from /usr/lib/libnspr4.so #6 0xb7d89f41 in PORT_Free_Util (ptr=0x0) at secport.c:152 #7 0x0805b146 in jar_extract_mf (jar=0x8091f90, format=<value optimized out>, fp=0x8092048, ext=0x806a210 "sf") at jarfile.c:737 #8 0x0805b5b2 in jar_extract_manifests (fp=<value optimized out>, format=<value optimized out>, jar=<value optimized out>) at jarfile.c:611 #9 JAR_pass_archive (jar=0x8091f90, format=jarArchZip, filename=0x80795c8 "nojs.jar", url=0x806c5f1 "some-url") at jarfile.c:134 #10 0x08057c32 in VerifyJar (filename=0x80795c8 "nojs.jar") at verify.c:74 #11 0x0804e7fe in main (argc=9, argv=0xbfa54424) at signtool.c:1007 Looking at secport.c:152 I find: void PORT_Free(void *ptr) { if (ptr) { PR_Free(ptr); } } I'm really confused how the above stack can happen at all if ptr=0x0. That's the reason why I'm actually thinking about some weird toolchain thing. That's a _bit_ important to me as I need to update NSS for different reasons and I don't want to disable the testsuite. Any pointers for me on that? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years

[opensuse-factory] Why separate dirs for: /etc/apache2/ssl.crl ssl.crt ssl.csr ssl.key ssl.prm?

by David C. Rankin

Devs, Posted to user list but Per and I are still scratching our heads. (well, I don't know if he's scratching, but I am...) Why does opensuse use separate directories under /etc/apache2 for ssl.crl ssl.crt ssl.csr ssl.key ssl.prm? Why is that any better than say putting all the certs in /etc/apache2/sslcerts? After all, the dirs are just option in /etc/apache2/vhosts.d/vhost-ssl.conf, example: SSLCertificateFile /etc/apache2/ssl.crt/server.crt SSLCertificateKeyFile /etc/apache2/ssl.key/server.key so why have 5 directories if 1 will do? -- 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 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years

[opensuse-factory] hplip problems

by Sid Boyce

Bug #487060 (Critical) refers - one in-house Novell user has seen the problem where jobs are queued but won't print on a network printer . The printer, in my case a USB attached HP Photosmart C4180 All-in-one does the same with the factory hplip and hplip-hpijs at ver. 2.8.7. The problem started with a zypper dup just before the M1 release and affects all the boxes I have. I tried 2.8.7 on 3 boxes and attaching the printer I get the same problem. So I downloaded hplip-3.9.4 source and installed it after using zypper to remove hplip and hplip-hpijs. The scanner function works perfectly. The print comes out as a page of solid black and the job remains on the queue. Propbably a mismatch between cups and the new hplip. I've suggested a new 3.9.4 package be added to factory - no further response so far. Sounds like my standard complaint? You're right. Is anyone having printing problems with HP printers? Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years

Re: [opensuse-factory] hplip problems

by Raymond Wooninck

On 30/04/09 04:23, Sid Boyce wrote: > I've suggested a new 3.9.4 package be added to factory - no further > response so far. Sounds like my standard complaint? You're right. Hi Sid, 3.9.4 packages for Factory are available from my Home repository. Just use the following URL: http://software.opensuse.org/search?baseproject=openSUSE%3AFactory&p=1&q=hp… I will create a submitreq again to the devel-project of hplip, so that we can expect this version to be in Factory. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years

[opensuse-factory] Automatic bug reporting tool

by Rastislav Krupanský

Hi all. I just want to ask, why isn´t Apport (http://en.opensuse.org/Apport), or any automatic bug reporting tool, enabled by default? I think, it would by useful for you (as developers) to have it enabled, at least in development versions. Or wouldn´t? Reports via this tool could be more accurate, than obtaining info from users in some cases. If i´m right, Gnome uses bug-budy, but what is for KDE? -- S pozdravom / Best regards, Rasto -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years

[opensuse-factory] Radeon HD4870 a Sound Card ?

by Günther J. Niederwimmer

Hello, on a Intel Board DX58SO and a Radeon HD4870 PCIe, YaST2 tell me the Radeon HD4870 is a Soundcard ? Now I have two Soundcards a Intel and a Radeon ? Is this correct ? -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years

[opensuse-factory] /usr/include asm, linux problem

by Donn Washburn

I have over the years compiled from soutce about everything out there. However, recently I have noticed the /usr/include/asm and /usr/include/linux are the source of headaches. In the early days they were links to the /usr/src/linux kernel source. However in an effort to setup more CPU types there has been a change. /usr/include/asm seems to lack headers that are in /usr/include/asm-x86. I heard at some point that the real clean headers were in /usr/include/asm and linux. My question is based on this x86 machine would it be better to link asm to asm-x86? And what is the file /usr/include/linuxls" (no .h) doing there. It is a v4l2 file -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)windstream.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years

[opensuse-factory] /usr/include asm, linux problem

by Donn Washburn

I have over the years compiled from soutce about everything out there. However, recently I have noticed the /usr/include/asm and /usr/include/linux are the source of headaches. In the early days they were links to the /usr/src/linux kernel source. However in an effort to setup more CPU types there has been a change. /usr/include/asm seems to lack headerss that are in /usr/include/asm-x86. I heard at some point that the real clean headers were in /usr/include/asm and linux. My question is based on this x86 machine would it be better to link asm to asm-x86? And what is the file /usr/include/linuxls" (no .h) doing there. It is a v4l2 file -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)windstream.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

13 years

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory April 2009