https://bugzilla.novell.com/show_bug.cgi?id=339679 Summary: Enhancement - Information on Install Issues & Pro-Active Support Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rob.opensuse.linux@googlemail.com QAContact: jsrain@novell.com Found By: Other Somewhere in Sax2 (& Xorg sever) there must be table defining supported adapters. After new cards come out, fixes to recognise them probably are frequently addition of Bus id's to classify a new card (plus some numbers in table entries). Similarly, digging around on net I discover things like : 1) pdc_202_old, hpt36x/37x IDE cards may have issues, due to reworking ATA code 2) Geforce 8x00 family cards having trouble recognising display etc Or even 3) Reiserfs uses BKL (Big Kernel Lock) - Do not enable BKL Pre-emption if build kernel (so some script could do, mount | grep reiserfs && zcat /proc/config.gz | grep PREMPT_BKL && yast-feedback-warn REISERFS-PREEMPT_BKL "ReiserFS/BKL Incompatible System Configuration"). OpenSuSE connects to repositories during installation, permitting download of patch rpm's, as well as extra packages. It may not be possible (or safe) directly to configure full capability automatically, but when YaST or SaX2 create a degraded configuration they should save a TAG plus HW ID. Then rather than simple release notes, YaST can build a static webpage with : 1) Link to current copy of i18n/L10n-ed release notes 2) Specific information, relating to machines HW or the OS configuration 3) Finally link to pages explaining 'HOWTO', for common use cases On the web link pages the administrator is guided to latest info on hardware issues, or post-installation steps like ATI/Nvidia 3D FAQ. As this becomes a dynamic process, this leverages the feedback from open user community, improving the initial install for confused refugee from Windows. All they would need to do, is wait a month or two for the 'Pros' to shake down the new release. When they do have a problem, they have a 1-Stop, 1-Click place to gain the latest information. So after a YOU update, perhaps new information becomes available and I could be informed of relevant addition to SuSE knoledge base, helping me sort a hardware/config problem I did not even know I had (yet!). Everyone's time would be saved, because support & developers setting up tags, cause YaST to inform via YOU (and URL in installation report) of known issue. The Support team, have an easy quick way to reduce duplicate bug reports & support requests, and also opportunity to recruit beta-testers for fixes. Those less technical, could simply ask to receive notification on problem resolution passing beta-testers. This would be far superior to current practice in closed OSes. This is pro-active, rather than reactive, the benefits would be : 1) Impress new user, that issue is known and worked on. 2) Reduce confused bug reports and support requests. 3) Improve OpenSuSE image, as PC Mags etc. would highlight such feature in review. 4) Leverage the benefit of OpenSource, so solutions found by the experienced, can be fed back quicker to the less technical. 5) Probably reduce Support work load, as more information will reduce bug duplicates and problems caused by user bungling (in desperate effort to crack problem). 6) May permit and encourage greater community involvement to produce the best OS product on the market. 7) Reduce number of catastrophic experiences. 8) Point user to useful and relevant community created content in Wiki for example. Whilst retaining overview by Novell/SuSE, to mitigate dangers of poor and outrightly bad advice being given. The perennially recurring issue for Linux of delayed release of graphics drivers, would be mitigated. Those effected less vocal on forums, letters to mags etc. ( By comparison with Vista, graphics work but support for legacy network cards etc is poorj. Yet it is emotionally easy (and cheap) to purchase a new supported card quickly disposing of perfectly good 'legacy' card; in comparison it would be emotionally very difficult to 'downgrade' to old card to run OS better, just after making purchase of the latest 3D Monster. ) This approach trickle down, to paying Enterprise customers, as their product will have been tested and improved by more extensive use in the field, which included good feedback for real-world usage. Use Scenario New Windows User sick of Vista decides to try Linux on a newish PC PC complete with recent 3D card, required to run latest MS Advertising^wNagware^wOS at acceptable speed, they install but display is horrid, and slow. Result they give up immediately and go back to the comfort of slick style over substance. They will never discover the benefits of software catalogue, freedom, and lack of obscene EULA's and demands for money, from stroppy and obnoxiously arrogant companies, pushing DRM and releasing noisy software to try and impress the user that it must therefore be important and an essential purchase item. However with the "degraded configuration" recorded by SaX2, post-install they are directed by YaST to a locally generated web-page, with an item linkin g them to website page explaining the issues. The site can provide the info say on 3D driver download from Nvidia, with the instructions how to use YOU (like the SaX2 developers currently issue). Furthermore they find, links to open Bugzilla report with, dialogue between another real user, testing problem resolution. Result, confidence and a feeling of being part of a community, running software made by ppl who share info and work together, in a truthful manner. Currently it stands, they would have to understand Sax2 and the driver possibilities, vesafb, oss or graphics vendor supplied binaries, to get an acceptable display post-installation. Whilst install tries to make a usable solution without user intervention, this is actually not sufficient, where the card is not recognised. Few are using 1028x760 16bit Win95 style display these days, and KDE/GNOME do not really run comfortably at that resolution (nevermind the slow screen updates of vesafb driver, causing artifacts when window moved for example (even compared to Vista Aero). It is time consuming finding out where to look, and also forum users get fed up of FAQs, by ppl who won't Google. Hope the kernel idea is clear, and though I've rambled, the benefits of encouraging feedback, improving the support DB would create a virtuous circle, improving future experience via growing and highly accessible knowledge base. In the enterprise, time saved plus avoidance of downtime will mean money, lowering Cost of Ownership, and increasing stability and uptime of SEL systems. For Novell/SuSE it would mean better publicity, reviews and a better used, and in long run more widely tested and understood product, that makes market leading industry standard solution look half baked, and expensive, with poor suport model. -- 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.