Bug#858849: installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64
Hi, On Wed, Mar 29, 2017 at 09:27:42AM -0700, Jose R R wrote: >On Wed, Mar 29, 2017 at 8:48 AM, Cyril Bruleboiswrote: >> Jose R R (2017-03-29): >> >>> "We also encourage installation reports to be sent even if the >>> installation is successful, so that we can get as much information as >>> possible on the largest number of hardware configurations." < >>> https://www.debian.org/releases/stable/amd64/ch05s04.html.en#submit-bug >>> > >> >> Sure, with official images. >> >>> If you are still 'bothered' with my sporadic submissions, I encourage >>> you to modify the documentation to specifically exclude the glaring >>> omission. >> >> I could be adding a specific “we don't need reiser4-specific reports” > >Please do add that phrase; thus removing any ambiguities and cover the >glaring omission in the Debian documentation. It's hardly a "glaring omission" that we don't list *explicitly*: * we don't want reiser4-specific reports * we don't want Ubuntu installation reports * we don't want installation reports about other modified images You're reading the "Installation Guide for Debian", not the "Installation Guide for every unofficial user-modified version of Debian". The docs are meant to describe how to install Debian using Debian's installer - is that not obvious? >That clarification will prevent other individuals -- who have >downloaded the netboot installer from SourceForge -- from potentially >reporting via the debian mechanism -- once the installation completes. > >Additionally, appending “we don't need reiser4-specific reports” will >be a welcome *explicit* change in policy from other FOSS projects, >like GNU Parted, where the unspoken censorship on reiser4 bites anyone >who submits patches in support of the >'Batman Machine': Reiser4 >< https://metztli.it/readOnlyEphemeral/Batman_Machine-Reiser4.pdf > I understand that you're working on reiser4 stuff and you'd like to publicise it - that's cool and I hope it's working well for you! But spamming us here is *not* helping. OK? -- Steve McIntyre, Cambridge, UK.st...@einval.com "When C++ is your hammer, everything looks like a thumb." -- Steven M. Haflich
Bug#858849: installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64
Niltze, On Wed, Mar 29, 2017 at 8:48 AM, Cyril Bruleboiswrote: > Hi, > > Jose R R (2017-03-29): >> With all due respect, 99% of the build code for the debian-installer >> is yours. As well as the build pulls 99% UDEBs from official debian >> repositories. > > That doesn't mean that everything built on top of it has to be reported > on Debian mailing lists and bug tracker. See derivative distributions, > they have their own issue tracker, and only forward specific issues. > >> i.e., this is a Debian issue, not mine -- as I did not even touch that >> code and/or modules -- which 1 month ago actually did work smooth: >> >> Netboot debian-installer was unable to load firmware from second USB >> for wifi connection; accordingly, in another virtual screen, I mounted >> the 2nd USB and manually copied the firmware directory onto the >> installer environment /lib. d-i then detected the wifi signal, etc. >> >> >> Second, report on this unofficial jessie-backports kernel >> 4.9.16-1+reiser4.0.1 sheds light on the fact I experienced *no issue* >> with module i915, as had been reported by (maintainer?): < >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858078 > thus, in a >> collateral manner, I am contributing to official debian development. > > If you want to reply to submitters/maintainers, reply to specific bug > reports/threads, instead of sending lengthy mails to other people? > >> Finally, I am not requesting *any* support. I am simply reporting that >> your d-i pulling official UDEBs actually have been successful, with >> minor modifications and a few extra UDEBs of mine, in my installation >> experience, following Debian documentation guidelines: > > I haven't put words in your mouth and suggested you were requesting some > support. I'm just not convinced such reports are useful. If you > encounter specific issues, report specific bug reports against the > relevant component. > > debian-boot@ isn't and shouldn't be the destination of each and every > thing connected to, or merely using, Debian Installer. > >> "We also encourage installation reports to be sent even if the >> installation is successful, so that we can get as much information as >> possible on the largest number of hardware configurations." < >> https://www.debian.org/releases/stable/amd64/ch05s04.html.en#submit-bug >> > > > Sure, with official images. > >> If you are still 'bothered' with my sporadic submissions, I encourage >> you to modify the documentation to specifically exclude the glaring >> omission. > > I could be adding a specific “we don't need reiser4-specific reports” Please do add that phrase; thus removing any ambiguities and cover the glaring omission in the Debian documentation. That clarification will prevent other individuals -- who have downloaded the netboot installer from SourceForge -- from potentially reporting via the debian mechanism -- once the installation completes. Additionally, appending “we don't need reiser4-specific reports” will be a welcome *explicit* change in policy from other FOSS projects, like GNU Parted, where the unspoken censorship on reiser4 bites anyone who submits patches in support of the 'Batman Machine': Reiser4 < https://metztli.it/readOnlyEphemeral/Batman_Machine-Reiser4.pdf > Again, thank you. Best Professional Regards. -- Jose R R http://metztli.it - Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/ - Try at no charge http://b2evolution.net for http://OpenShift.com PaaS - from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
Bug#858849: installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64
Hi, Jose R R(2017-03-29): > With all due respect, 99% of the build code for the debian-installer > is yours. As well as the build pulls 99% UDEBs from official debian > repositories. That doesn't mean that everything built on top of it has to be reported on Debian mailing lists and bug tracker. See derivative distributions, they have their own issue tracker, and only forward specific issues. > i.e., this is a Debian issue, not mine -- as I did not even touch that > code and/or modules -- which 1 month ago actually did work smooth: > > Netboot debian-installer was unable to load firmware from second USB > for wifi connection; accordingly, in another virtual screen, I mounted > the 2nd USB and manually copied the firmware directory onto the > installer environment /lib. d-i then detected the wifi signal, etc. > > > Second, report on this unofficial jessie-backports kernel > 4.9.16-1+reiser4.0.1 sheds light on the fact I experienced *no issue* > with module i915, as had been reported by (maintainer?): < > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858078 > thus, in a > collateral manner, I am contributing to official debian development. If you want to reply to submitters/maintainers, reply to specific bug reports/threads, instead of sending lengthy mails to other people? > Finally, I am not requesting *any* support. I am simply reporting that > your d-i pulling official UDEBs actually have been successful, with > minor modifications and a few extra UDEBs of mine, in my installation > experience, following Debian documentation guidelines: I haven't put words in your mouth and suggested you were requesting some support. I'm just not convinced such reports are useful. If you encounter specific issues, report specific bug reports against the relevant component. debian-boot@ isn't and shouldn't be the destination of each and every thing connected to, or merely using, Debian Installer. > "We also encourage installation reports to be sent even if the > installation is successful, so that we can get as much information as > possible on the largest number of hardware configurations." < > https://www.debian.org/releases/stable/amd64/ch05s04.html.en#submit-bug > > Sure, with official images. > If you are still 'bothered' with my sporadic submissions, I encourage > you to modify the documentation to specifically exclude the glaring > omission. I could be adding a specific “we don't need reiser4-specific reports” there, but I would hope this isn't needed, since the only submitter of such reports against images we don't build, publish, or support, seems to be you. Thanks for your cooperation. KiBi. signature.asc Description: Digital signature
Bug#858849: installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64
Niltze, On Mon, Mar 27, 2017 at 8:00 PM, Cyril Bruleboiswrote: > Hi, > > Metztli Information Technology (2017-03-27): >> Boot method: CD/USB >> Image version: https://metztli.it/readOnlyEphemeral/xiuhcohuatl.iso built on >> Mar 25 08:35 (2017) >> Date: Mar 26, 2017, 01:49 > > A couple of months ago, I asked: > | Do we need to get installation reports for non-Debian installers? > | This isn't something we produce, publish, or support, so… > > It would be nice if those installation reports could be sent elsewhere; > thanks already. > > > KiBi. With all due respect, 99% of the build code for the debian-installer is yours. As well as the build pulls 99% UDEBs from official debian repositories. i.e., this is a Debian issue, not mine -- as I did not even touch that code and/or modules -- which 1 month ago actually did work smooth: Netboot debian-installer was unable to load firmware from second USB for wifi connection; accordingly, in another virtual screen, I mounted the 2nd USB and manually copied the firmware directory onto the installer environment /lib. d-i then detected the wifi signal, etc. Second, report on this unofficial jessie-backports kernel 4.9.16-1+reiser4.0.1 sheds light on the fact I experienced *no issue* with module i915, as had been reported by (maintainer?): < https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858078 > thus, in a collateral manner, I am contributing to official debian development. Finally, I am not requesting *any* support. I am simply reporting that your d-i pulling official UDEBs actually have been successful, with minor modifications and a few extra UDEBs of mine, in my installation experience, following Debian documentation guidelines: "We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations." < https://www.debian.org/releases/stable/amd64/ch05s04.html.en#submit-bug > If you are still 'bothered' with my sporadic submissions, I encourage you to modify the documentation to specifically exclude the glaring omission. Best Professional Regards. -- Jose R R http://metztli.it - Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/ - Try at no charge http://b2evolution.net for http://OpenShift.com PaaS - from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
Bug#858849: installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64
Hi, Metztli Information Technology(2017-03-27): > Boot method: CD/USB > Image version: https://metztli.it/readOnlyEphemeral/xiuhcohuatl.iso built on > Mar 25 08:35 (2017) > Date: Mar 26, 2017, 01:49 A couple of months ago, I asked: | Do we need to get installation reports for non-Debian installers? | This isn't something we produce, publish, or support, so… It would be nice if those installation reports could be sent elsewhere; thanks already. KiBi. signature.asc Description: Digital signature
Bug#858849: installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64
Package: installation-reports Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: Boot method: CD/USB Image version: https://metztli.it/readOnlyEphemeral/xiuhcohuatl.iso built on Mar 25 08:35 (2017) Date: Mar 26, 2017, 01:49 Machine: HP Pavilion Notebook PC 2x8192MB RAM Partitions: udev devtmpfs 102400 10240 0% /dev tmpfs tmpfs 3276596 9488 3267108 1% /run /dev/sda6 reiser4 92791120 5182708 87608412 6% / tmpfs tmpfs 8191484 7048 8184436 1% /dev/shm tmpfs tmpfs 51204 5116 1% /run/lock tmpfs tmpfs 81914840 8191484 0% /sys/fs/cgroup /dev/sda9 ext213626980061 48938 63% /boot tmpfs tmpfs 16383008 1638292 1% /run/user/118 tmpfs tmpfs 1638300 20 1638280 1% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Netboot debian-installer was unable to load firmware from second USB for wifi connection; accordingly, in another virtual screen, I mounted the 2nd USB and manually copied the firmware directory onto the installer environment /lib. d-i then detected the wifi signal, etc. I selected a non-expert installation & d-i proceeded normally, by downloading via SSL from metztli.it jessie-packport 4.9.16-1+reiser4.0.1 (2017-03-24), reiser4progs 1.1.x, as well as bp replacements of: nfs-common_1.3.4-2.1_amd64.deb libgssapi-krb5-2_1.15-1.1_amd64.deb libk5crypto3_1.15-1.1_amd64.deb libkrb5-3_1.15-1.1_amd64.deb libkrb5support0_1.15-1.1_amd64.deb In this installer I noticed a lot of debugging verbosity (F4), but overall installation was successfull. In this Reiser4 'retrofitted' d-i, a non-expert install will leave the regular kernel in addition to the Reiser4-enabled bp kernel. < https://metztli.it/readOnlyEphemeral/xiuhcohuatl_0.png > notwithstanding a netstat will show same services available as in a non-reiser4 install. Regular kernel may be purged by user -- who, if having selected option 'Debian Desktop Environment' will see: < https://metztli.it/readOnlyEphemeral/xiuhcohuatl_01.png > Again, as in the last installation, dmesg shows segmentation faults as user operates her/his new jessie, as shown in snapshot: < https://metztli.it/readOnlyEphemeral/xiuhcohuatl_02.png > which introduce latency in the operation of the newly installed jessie. These issues will go away by doing: apt-get -t jessie-backports update apt-get -t jessie-backports dist-upgrade Except that non-expert install does not provide jessie-backports option or by default. The user thus has to add directive: deb http://ftp.debian.org/debian jessie-backports main (at least) to her/his /etc/apt/sources.list Finally, unlike user who reported bug 858078 with i915, < https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858078 > this system booted normally into a GUI without modification on my part: lsmod | grep i915 i915 1241088 5 drm_kms_helper155648 1 i915 drm 360448 6 i915,drm_kms_helper i2c_algo_bit 16384 1 i915 video 40960 1 i915 button 16384 1 i915 -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="8 (jessie) - installer build 20170325-15:09" X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux xiuhcohuatl 4.9.0-2+reiser4.0.1-amd64 #1 SMP Debian 4.9.16-1+reiser4.0.1 (2017-03-24) x86_64 Xonecuiltzin lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658] lspci -knn: 00:02.0