[Bug 892931] New: No Video/Audio Support From Native Installation and No Auto Updates from Nvidia
https://bugzilla.novell.com/show_bug.cgi?id=892931 https://bugzilla.novell.com/show_bug.cgi?id=892931#c0 Summary: No Video/Audio Support From Native Installation and No Auto Updates from Nvidia Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs@forge.provo.novell.com ReportedBy: secure@aphofis.com QAContact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Perfect and Seamless Video/Audio Support was available in 12.3! After Installation and Online Updates and adding Nvidia Reop there is no monitor identified in KDE>System Stetting>Monitor>Display Configuration There is Identifiable Information in both Screen Locker and Gamma correction of this Module. Yast can clearly identify the Video Card detection as a Nvidia GT200 [GeForce 210] and complete Hardware List. Video is connected via HDMI as normal however both Video/Audio this was perfect in 12.3 All support comes from Native Suse.de drivers Installed latest rebuild of change log support was 04 Jul 20014 EST: sndirsch@suse.de I am tempted to resign to kernel, however there are various files I know you'll need for this and other Installation and Storage and NFS Bugs etc. etc. before I trash this PC and revert back to 12.3 There are so many files I could attach in respect to this bug but I don’t know where to begin so I'll leave it to you to ask. Yast HW list will be one etc. etc. etc...Tell me how I can help with files and logs please as I want to trash this install and revert as soon as possible Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: No Video/Audio Support From Native Installation and No Auto Updates from Nvidia Expected Results: Exactly what is did in 12.3 There are so many files I could attach in respect to this bug but I don’t know where to begin so I'll leave it to you to ask. Yast HW list will be one etc. etc. etc...Tell me how I can help with files and logs please as I want to trash this install and revert as soon as possible -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=892931
https://bugzilla.novell.com/show_bug.cgi?id=892931#c1
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=892931
https://bugzilla.novell.com/show_bug.cgi?id=892931#c2
Scott Couston
Yes! Nvida has been a part of the perfect seamless integration as are all other valuable reps I add immediately the first few big online updates are done. The auto selection of the drivers, whether it be native or from Nvida continues to function perfectly, and once established, is just part of either Online Update or Apper. I'm not sure why everything stopped working in 13.1. All my current Nvida support is auto selected to native suse support driver files mainly with only a few files auto inserted from Nvida itself. I did note that on ALL the change logs file notes they were massively all altered and support added on 04 Jul 20014 EST: sndirsch@suse.de I'm not sure where the author may be over there, its a big place and upside down from where I sit here in OZ :-) Users just need to trust the logic of both. I've attached an image of today’s 12.3 example of Apper changes to Video driver and others. Why we default install 2 x Online Update vehicles I leave with you, however the logic of Yast Online Update requiring root auth and Apper requires nothing but user auth is a bit beyond my logic. Although the Online Update selection screen is often blank on the left hand side with no listings of file, Yast>Online update will update the best candidate update without interference. You only get into trouble, IF you start to 'self select/demand updates by overriding auto update selection and this will always leave a legacy of dependency and non performance of major components to the point of requiring a format and restart. This has been seamlessly working well before KDE4 and the disaster of V11.x I believe, when we got all stuffed up with IFUP/Network Manager conflicts and began the first of our plasma desktops that fell over all the time. I can recall V9.x and at that stage every Lizard got a boxed set of every open release, all over the world. It was a nice but expensive to maintain but the hard-copy user guide was unreal. In my Install bug report with 13.1 we still do NOT auto select the package groups help/documentation where local hard disk knowledge can be obtained. When your in trouble the net isn’t always there. The KDE Help module WAS to be able to be user indexed and re-indexed as more help topics or man pages got added with additional software installer brought their associated help or man pages were done. Let me know what files you require in support of this 13.1 install bottom of the line it use to work in 12.3 and now doesn’t and I not all currently selected file support are ALL subject to a file change as in the above. In respect to the X.org Nvida control Panel, well that app just hasn’t ever worked on two levels. Firstly you need root authority to save the file as I don't permit any install to also carry root authority and secondly where do I save the file? I am of the belief the config is an additional change to the current con-fig file and there is no ability, root or otherwise to merge the new config file. The is no mention of anything much in help and I have absolutely no idea where the config file is in the upper reaches of the directory structure. I've just found it far easier to add the repo and let what automation do what it does well. Both apper and Online update WILL auto install what files are required in the first instance and subsequent changes without interference or change required by X.org Nvida app which as I've said; provides no functional assistance what-so-ever. How can I best help you with information on this 13.1 Install I will have to trash as there are so so so many large issues with it, it kinda got the look and feel of alpha software and no where near a RC. The very same install/storage problem with X_64 and UEFI support that came crashing down on all of our X_64 are still very much the same yet were beautifully summed up be an internal bug report done over there. If install had its way none of my X_64 PC's would not even reboot as the bootloader is still full of assumptions and rubbish. Not being able to simply see standard BIOS ctrl+F, that is on everything for any RAID LV, lest my RAID5 config is a show stopper in my books. I just want to supply you with all the file log support of about my 4 Bugs on 13.1 and format and revert to perfectly stable, always work 12.3 that my production LAN sits on very nicely. I cant even start to test anything on 13.x Cheers and let me know what log file support I can provide. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=892931
https://bugzilla.novell.com/show_bug.cgi?id=892931#c3
--- Comment #3 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=892931
https://bugzilla.novell.com/show_bug.cgi?id=892931#c4
--- Comment #4 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=892931
https://bugzilla.novell.com/show_bug.cgi?id=892931#c5
--- Comment #5 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=892931
https://bugzilla.novell.com/show_bug.cgi?id=892931#c6
--- Comment #6 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=892931
https://bugzilla.novell.com/show_bug.cgi?id=892931#c7
--- Comment #7 from Scott Couston
participants (1)
-
bugzilla_noreply@novell.com