From benjamin.widawsky at intel.com Fri Apr 1 18:16:00 2016 From: benjamin.widawsky at intel.com (Ben Widawsky) Date: Fri, 1 Apr 2016 11:16:00 -0700 Subject: Skylake Iris 540 renderer string in i965 (the same as HD 520) In-Reply-To: <20160331202656.GA6634@intel.com> References: <56FAD0BE.7030606@gmail.com> <20160331202656.GA6634@intel.com> Message-ID: <20160401181556.GA32143@intel.com> On Thu, Mar 31, 2016 at 01:26:57PM -0700, Ben Widawsky wrote: > On Tue, Mar 29, 2016 at 09:00:14PM +0200, Michal Powalko wrote: > > Dear Ben and Michal, > > dear Ubuntu-bugsquad, > > > > I have recently bought a new Skylake based NUC with Intel® Core(TM) i5-6260U > > processor and Intel® Iris(TM) graphics 540. I am working on Ubunut 14.04.3 > > LTS (kernel 4.2) and waiting for 16.04 (kernel 4.4) to take advantage of > > both CPU (from Linux kernels > 4.3) and GPU full support. The 16.04 beta 2 > > is quite "unstable" in terms of Skylake GPU (see e.g. the archlinux source), > > so I tried to find out the walk-around to make it work more stable... > > > > I have found out Mesa commit "i965/skl: Update Skylake renderer strings" > > describing the device ID's of different GPU's. In case of my NUC, according > > the ARK' info Iris 540 has the ID of 0x1916, which in Mesa 11.x file has > > associated with HD 520 :( I did some research and found out, that the ID of > > 0x1916 can be used for HD 520 and Iris 540 (see attached screen-shots and > > links below) depending on the CPU :/ > > > > 1. Would it be possible for You to find out the solution to assign the > > proper GPU name base on ID (Iris 540 in case of i5-6260U) - maybe > > using CPU info ? > > 2. Can the wrong name / feature assessment between HD 520 and Iris 540 > > be the source of unstable operation / freeze / crash of the system > > (system working well but slow with Gallium3Ddriver)? > > > > I would be really happy to help You providing more information if necessary. > > > > Sources: > > > > * Mesa commit > > https://cgit.freedesktop.org/mesa/mesa/commit/?h=11.2&id=20e8ee36627f87414440650dcff89990eb70c688 > > > > * Wiki is saying: Iris Graphics 540, *GT3e* - 48 execution units with > > 64 MB of eDRAM, up to 806.4 GFLOPS at 1.05 GHz > > https://en.wikipedia.org/wiki/Intel_HD_and_Iris_Graphics > > https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units > > > > * Intel graphics on linux > > https://wiki.archlinux.org/index.php/intel_graphics > > > > * NUC specification > > http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc6i5syh.html > > > > * Intel Gen9 HD Graphics > > http://www.anandtech.com/show/9582/intel-skylake-mobile-desktop-launch-architecture-analysis/6 > > > > > > Best regards from Denmark > > Michal Powalko > > > > > > > Thank you for bringing this to my attention. Summing up there are two products > with the same devid, but different branding. > 520: http://ark.intel.com/products/88192/Intel-Core-i7-6600U-Processor-4M-Cache-up-to-3_40-GHz > 540: http://ark.intel.com/products/91160/Intel-Core-i5-6260U-Processor-4M-Cache-up-to-2_90-GHz > > Let me look into this further, and I will see what we can do. Meanwhile, I would > advise filing a bug upstream on freedesktop.org. > Hi. Ark has been updated to reflect the correct PCI device ID. I don't have an actual device, so I can't confirm this. -- Ben Widawsky, Intel Open Source Technology Center From alarconj at gmail.com Tue Apr 26 14:43:10 2016 From: alarconj at gmail.com (Julian Alarcon) Date: Tue, 26 Apr 2016 09:43:10 -0500 Subject: Problems with docummentation reporting bugs Message-ID: Hi! I tried multiple times to upload a .crash report to an existing bug with no success. Cheking the official documentation, I see that maybe there is an error in some of the steps to upload existing reports to existing bugs. https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_when_offline_or_using_a_headless_setup When I tried this: - ubuntu-bug -c ** -u ** I got this error: test at CO1WDJ39M6V1U:/var/crash$ ubuntu-bug -c /var/crash/_usr_bin_remmina.1001.crash -u 1515240 /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before import to ensure that the right version gets loaded. from gi.repository import GLib, Wnck, GdkX11, Gdk Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash file] ubuntu-bug: error: -u/--update-bug option cannot be used together with options for a new report Can you confirm if this is a real problem in the documentation? Thank you! -- Julian Alarcon -------------- next part -------------- An HTML attachment was scrubbed... URL: From dev at otq.za.net Tue Apr 26 15:22:03 2016 From: dev at otq.za.net (Bruce Pieterse) Date: Tue, 26 Apr 2016 17:22:03 +0200 Subject: Problems with docummentation reporting bugs In-Reply-To: References: Message-ID: <571F879B.7000008@otq.za.net> On 26/04/2016 16:43, Julian Alarcon wrote: > Hi! > > I tried multiple times to upload a .crash report to an existing bug with > no success. Cheking the official documentation, I see that maybe there > is an error in some of the steps to upload existing reports to existing > bugs. > > https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_when_offline_or_using_a_headless_setup > > When I tried this: > > * > > ubuntu-bug -c // -u // > > I got this error: > > test at CO1WDJ39M6V1U:/var/crash$ ubuntu-bug -c > /var/crash/_usr_bin_remmina.1001.crash -u 1515240 > /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without > specifying a version first. Use gi.require_version('Wnck', '3.0') before > import to ensure that the right version gets loaded. > from gi.repository import GLib, Wnck, GdkX11, Gdk > Usage: ubuntu-bug [options] [symptom|pid|package|program > path|.apport/.crash file] > > ubuntu-bug: error: -u/--update-bug option cannot be used together with > options for a new report > > Can you confirm if this is a real problem in the documentation? > > Thank you! > -- > Julian Alarcon > > Hi Julian, If it is a new bug report, you can omit the -u option. If you are adding more information to an existing bug report then you can use -u . It mentions this in the link you provided: "If this is to be added to an existing bug report, also use the -u option: ubuntu-bug -c -u " But what you want is: "When the file is ready, copy it to the system you intend to use for filing the report. There you can then file the report: ubuntu-bug -c " Another way of doing it, as mentioned in the docs is just run: ubuntu-bug /var/crash/application-name.crash Hope that helps. -- All the best, Bruce From dev at otq.za.net Tue Apr 26 15:28:22 2016 From: dev at otq.za.net (Bruce Pieterse) Date: Tue, 26 Apr 2016 17:28:22 +0200 Subject: Problems with docummentation reporting bugs In-Reply-To: <571F879B.7000008@otq.za.net> References: <571F879B.7000008@otq.za.net> Message-ID: <571F8916.5010508@otq.za.net> On 26/04/2016 17:22, Bruce Pieterse wrote: > > > On 26/04/2016 16:43, Julian Alarcon wrote: >> Hi! >> >> I tried multiple times to upload a .crash report to an existing bug with >> no success. Cheking the official documentation, I see that maybe there >> is an error in some of the steps to upload existing reports to existing >> bugs. >> >> https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_when_offline_or_using_a_headless_setup >> >> >> When I tried this: >> >> * >> >> ubuntu-bug -c // -u // >> >> I got this error: >> >> test at CO1WDJ39M6V1U:/var/crash$ ubuntu-bug -c >> /var/crash/_usr_bin_remmina.1001.crash -u 1515240 >> /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without >> specifying a version first. Use gi.require_version('Wnck', '3.0') before >> import to ensure that the right version gets loaded. >> from gi.repository import GLib, Wnck, GdkX11, Gdk >> Usage: ubuntu-bug [options] [symptom|pid|package|program >> path|.apport/.crash file] >> >> ubuntu-bug: error: -u/--update-bug option cannot be used together with >> options for a new report >> >> Can you confirm if this is a real problem in the documentation? >> >> Thank you! >> -- >> Julian Alarcon >> >> > > Hi Julian, > > If it is a new bug report, you can omit the -u option. If > you are adding more information to an existing bug report then you can > use -u . > > It mentions this in the link you provided: > > "If this is to be added to an existing bug report, also use the -u option: > > ubuntu-bug -c -u > " > > But what you want is: > > "When the file is ready, copy it to the system you intend to use for > filing the report. There you can then file the report: > > ubuntu-bug -c > " > > Another way of doing it, as mentioned in the docs is just run: > > ubuntu-bug /var/crash/application-name.crash > > Hope that helps. > Julian, My apologies, I misread your first sentence! That bug report is a duplicate of another bug report, but it has no reference to the other bug report. Perhaps the documentation is correct but due to the bug being marked as a duplicate of another bug, it can't be uploaded. Perhaps try tracking down the new bug version and try to submit the crash file against the new bug number. I'm assuming this is the reason, but hopefully some one with more experience with apport can comment. -- All the best, Bruce From alarconj at gmail.com Wed Apr 27 22:19:33 2016 From: alarconj at gmail.com (Julian Alarcon) Date: Wed, 27 Apr 2016 17:19:33 -0500 Subject: Problems with docummentation reporting bugs In-Reply-To: <571F8916.5010508@otq.za.net> References: <571F879B.7000008@otq.za.net> <571F8916.5010508@otq.za.net> Message-ID: Hi Bruce I marked as duplicated after I tried multiple times to add the crash information to the existing (duplicated) bug. As I couldn't make that I prefer to report a new bug and mark the old bug (with less information and old) as a duplicated bug of the new (both reported by me). The documentation is wrong, i guess. On Tue, Apr 26, 2016 at 10:28 AM, Bruce Pieterse wrote: > > > On 26/04/2016 17:22, Bruce Pieterse wrote: > >> >> >> On 26/04/2016 16:43, Julian Alarcon wrote: >> >>> Hi! >>> >>> I tried multiple times to upload a .crash report to an existing bug with >>> no success. Cheking the official documentation, I see that maybe there >>> is an error in some of the steps to upload existing reports to existing >>> bugs. >>> >>> >>> https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_when_offline_or_using_a_headless_setup >>> >>> >>> When I tried this: >>> >>> * >>> >>> ubuntu-bug -c // -u // >>> >>> I got this error: >>> >>> test at CO1WDJ39M6V1U:/var/crash$ ubuntu-bug -c >>> /var/crash/_usr_bin_remmina.1001.crash -u 1515240 >>> /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without >>> specifying a version first. Use gi.require_version('Wnck', '3.0') before >>> import to ensure that the right version gets loaded. >>> from gi.repository import GLib, Wnck, GdkX11, Gdk >>> Usage: ubuntu-bug [options] [symptom|pid|package|program >>> path|.apport/.crash file] >>> >>> ubuntu-bug: error: -u/--update-bug option cannot be used together with >>> options for a new report >>> >>> Can you confirm if this is a real problem in the documentation? >>> >>> Thank you! >>> -- >>> Julian Alarcon >>> >>> >>> >> Hi Julian, >> >> If it is a new bug report, you can omit the -u option. If >> you are adding more information to an existing bug report then you can >> use -u . >> >> It mentions this in the link you provided: >> >> "If this is to be added to an existing bug report, also use the -u option: >> >> ubuntu-bug -c -u >> " >> >> But what you want is: >> >> "When the file is ready, copy it to the system you intend to use for >> filing the report. There you can then file the report: >> >> ubuntu-bug -c >> " >> >> Another way of doing it, as mentioned in the docs is just run: >> >> ubuntu-bug /var/crash/application-name.crash >> >> Hope that helps. >> >> > Julian, > > My apologies, I misread your first sentence! That bug report is a > duplicate of another bug report, but it has no reference to the other bug > report. > > Perhaps the documentation is correct but due to the bug being marked as a > duplicate of another bug, it can't be uploaded. Perhaps try tracking down > the new bug version and try to submit the crash file against the new bug > number. > > I'm assuming this is the reason, but hopefully some one with more > experience with apport can comment. > > > -- > All the best, > > Bruce > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -- Julian Alarcon -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Thu Apr 28 09:52:11 2016 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 28 Apr 2016 09:52:11 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?knome?= Message-ID: <20160428095211.3691.38195@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingPrintingProblems" page has been changed by knome: http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=96&rev2=97 6. Check whether the printer gets correctly detected by the USB subsystem and determine its USB vendor/product IDs and the USB bus and device addresses: <
> {{{$ lsusb}}} <
> Note: The USB bus and device addresses change if you turn off or unplug the printer. Please re-run this command if needed. 7. Check whether the device files for the printer get created and the ownerships ("root lp") and permissions (non-HP: "crw-rw-r--", HP: "crw-rw-r--+") correctly set: <
> {{{$ ls -l /dev/usb/lp* /dev/bus/usb/*/*}}} 8. Determine the printer's device ID strings: <
> {{{$ sudo usb_printerid /dev/usb/lp0}}} <
> {{{$ sudo usb_printerid /dev/usb/lp1}}} <
> {{{...}}} <
> For HP printers also use <
> {{{$ hp-info -i}}} <
> and choose the printer with the problem from the text menu, then copy the "deviceid" entry from the output (can be several lines). - 9. For HP printers: Check whether HPLIP connects to them: <
> {{{$ hp-makeuri :}}} <
> Replace "" and "" by the bus and device numbers from the "lsusb" output (not vendor and product ID). The numbers must be supplied with three digits, zero-padded from the left, like "008:015". + 9. For HP printers: Check that you have the latest version of HPLIP and whether HPLIP connects to them: <
> {{{$ hp-makeuri :}}} <
> Replace "" and "" by the bus and device numbers from the "lsusb" output (not vendor and product ID). The numbers must be supplied with three digits, zero-padded from the left, like "008:015". (More information from [[http://hplipopensource.com/]].) 10. Find out if your printer gets detected by CUPS: <
> {{{$ lpinfo -v}}} 11. Attach the output of the above commands to the bug report.