Bug#756183: Realtek RTL8111/8168/8411 module (r8168 or r8169) not loaded at boot
On Sun, Jul 27, 2014 at 10:09:14AM +0200, Ryan Kavanagh wrote: > The module for my "Ethernet controller [0200]: Realtek Semiconductor > Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller > [10ec:8168] (rev 09)" does not get loaded at boot under 3.14-2-amd64, > but does on previous kernel versions. This device works with both the > r8168 and the r8169 modules, but previous kernels loaded r8168. I did some more investigating, and it turns out that I had r8168-dkms installed, and in its long description: Installation of the r8168-dkms package will disable the in-kernel r8169 module. To re-enable r8169, the r8168-dkms package must be purged. My hypothesis is that either r8168-dkms failed to compile the DKMS module locally on my end for 3.14-2 (most likely), and since the r8168-dkms package was installed, the kernel didn't load r8169 either; or that r8168 managed to compile it and 3.14-2 refused to load it, and since the r8168-dkms package was installed, the kernel didn't load r8169 either. After purging r8168-dkms, r8169 started getting loaded properly by 3.14-2 at boot. Thus, this is likely a non-bug. Sorry for the noise. Best wishes, Ryan signature.asc Description: Digital signature
Bug#756183: Realtek RTL8111/8168/8411 module (r8168 or r8169) not loaded at boot
Control: reassign -1 r8168-dkms On Sun, 2014-07-27 at 10:52 +0200, Ryan Kavanagh wrote: > On Sun, Jul 27, 2014 at 10:09:14AM +0200, Ryan Kavanagh wrote: > > The module for my "Ethernet controller [0200]: Realtek Semiconductor > > Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller > > [10ec:8168] (rev 09)" does not get loaded at boot under 3.14-2-amd64, > > but does on previous kernel versions. This device works with both the > > r8168 and the r8169 modules, but previous kernels loaded r8168. > > I did some more investigating, and it turns out that I had r8168-dkms > installed, and in its long description: > > Installation of the r8168-dkms package will disable the in-kernel r8169 > module. To re-enable r8169, the r8168-dkms package must be purged. > > My hypothesis is that either r8168-dkms failed to compile the DKMS > module locally on my end for 3.14-2 (most likely), and since the > r8168-dkms package was installed, the kernel didn't load r8169 either; > or that r8168 managed to compile it and 3.14-2 refused to load it, and > since the r8168-dkms package was installed, the kernel didn't load r8169 > either. After purging r8168-dkms, r8169 started getting loaded properly > by 3.14-2 at boot. > > Thus, this is likely a non-bug. Sorry for the noise. It's a bug in r8168 that it failed to compile. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#756183: Realtek RTL8111/8168/8411 module (r8168 or r8169) not loaded at boot
Processing control commands: > reassign -1 r8168-dkms Bug #756183 [src:linux] Realtek RTL8111/8168/8411 module (r8168 or r8169) not loaded at boot Bug reassigned from package 'src:linux' to 'r8168-dkms'. No longer marked as found in versions linux/3.14.13-2. Ignoring request to alter fixed versions of bug #756183 to the same values previously set -- 756183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b756183.140646168015388.transcr...@bugs.debian.org
Re: Kernel version for jessie
On Fri, 2014-07-18 at 17:43 +0100, Ben Hutchings wrote: [...] > So we have a choice between: > > Linux 3.14-stable > - Supported by Greg for about 2 years after release (March 2014) > - As an official kernel.org branch, it is likely to get some more > testing and review, and more backports from upstream maintainers > > Linux 3.16-stable > - Supported by Ubuntu kernel team for about 15-18 months after distro > release (October 2014) > - Will support more current hardware and need fewer driver backports > > Both of these will be supported until about the same time that wheezy > reaches EOL, which is when I intend to stop maintaining 3.2-stable. At > that point, I would be prepared to take over maintainership of either of > the newer branches. > > There's not an obvious winner out of these two options, but we should > choose fairly soon. Please speak up with arguments either way. Based on the replies to this, I think 3.16 is now the clear winner. To avoid disruption to the installer, I think we should keep 3.14 in unstable until the next installer alpha/beta is out, and then move straight to 3.16. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
Bug#756207: postinst requires perl-modules but doesn't depend on it
Package: src:linux Version: 3.14.13-2 Severity: normal linux-image-$KVER's postinst requires perl-modules (use File::stat;), but only perl-base is essential, accordingly the postinst fails in a minimal environment: # cdebootstrap --arch=amd64 --flavour=minimal sid /mnt/ http://ftp.debian.org/debian/ # chroot /mnt/ /bin/bash # apt update # apt install linux-image-3.14-2-amd64 Setting up linux-image-3.14-2-amd64 (3.14.13-2) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.) debconf: falling back to frontend: Teletype Can't locate File/stat.pm in @INC (you may need to install the File::stat module) (@INC contains: /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at /var/lib/dpkg/info/linux-image-3.14-2-amd64.postinst line 8. BEGIN failed--compilation aborted at /var/lib/dpkg/info/linux-image-3.14-2-amd64.postinst line 8. dpkg: error processing package linux-image-3.14-2-amd64 (--configure): subprocess installed post-installation script returned error exit status 2 Regards Stefan Lippers-Hollmann signature.asc Description: This is a digitally signed message part.
Bug#756147: marked as done (scsi-common-modules-3.2.0-4-amd64-di: cannot PXE install on VMware)
Your message dated Sun, 27 Jul 2014 15:31:20 +0100 with message-id <1406471480.29010.173.ca...@deadeye.wl.decadent.org.uk> and subject line Re: Bug#756147: scsi-common-modules-3.2.0-4-amd64-di: cannot PXE install on VMware has caused the Debian Bug report #756147, regarding scsi-common-modules-3.2.0-4-amd64-di: cannot PXE install on VMware to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 756147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: scsi-common-modules-3.2.0-4-amd64-di Severity: important Tags: d-i Dear Maintainer, * What led up to the situation? installing on vmware by way of PXE using netboot initrd * What exactly did you do (or not do) that was effective (or ineffective)? creating a local repo cloning the ISO, with the addition of the scsi-common-modules * What was the outcome of this action? installation was successful * What outcome did you expect instead? -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- On Sat, 2014-07-26 at 13:46 -0500, Scott Coil wrote: > Package: scsi-common-modules-3.2.0-4-amd64-di > Severity: important > Tags: d-i > > Dear Maintainer, > >* What led up to the situation? >installing on vmware by way of PXE using netboot initrd >* What exactly did you do (or not do) that was effective (or > ineffective)? >creating a local repo cloning the ISO, with the addition of the >scsi-common-modules >* What was the outcome of this action? >installation was successful >* What outcome did you expect instead? This is not a bug in this package. I also don't understand how it's a bug in the netboot image - it is not supposed to include most storage drivers, but will download them as needed. Bear in mind that the netboot kernel and initrd need to exactly match the kernel version in the archive, so the netboot files for 7.4 and earlier will no longer work. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#756147: closed by Ben Hutchings (Re: Bug#756147: scsi-common-modules-3.2.0-4-amd64-di: cannot PXE install on VMware)
Perhaps this bug is filed under the incorrect package, however, I still believe this to be a bug as it is impossible to install in a detached environment using the distributed ISO. Neither the udeb's provided by the ISO or the netboot initrd provide the scsi_transport_spi module which is needed to install in an ESX environment. Mirroring the upstream repo is undesirable as I need a static set of package versions. I should be able to serve the mounted ISO to PXE install, but due to this missing module I am unable to do so. As far as I see, the answer is to either add the module to the initrd or add the udeb to the ISO. Adding to the ISO seems more ideal to me as it keeps the size of the initrd down. Scott On Sun, 27 Jul 2014 14:33:11 + Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the scsi-common-modules-3.2.0-4-amd64-di > package: > > #756147: scsi-common-modules-3.2.0-4-amd64-di: cannot PXE install on > VMware > > It has been closed by Ben Hutchings . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Ben Hutchings > by replying to this email. > > -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140727095832.2726c92d@scott-desktop
Processed: tagging 756207
Processing commands for cont...@bugs.debian.org: > tags 756207 + pending Bug #756207 [src:linux] postinst requires perl-modules but doesn't depend on it Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 756207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.140648417616348.transcr...@bugs.debian.org
Processed: tagging 756134
Processing commands for cont...@bugs.debian.org: > tags 756134 + pending Bug #756134 [src:linux] linux: French debconf templates translation Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 756134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.140648418716479.transcr...@bugs.debian.org
Processed: tagging 756049
Processing commands for cont...@bugs.debian.org: > tags 756049 + pending Bug #756049 [linux] [L10N,DE] linux: updated german debconf translation Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 756049: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.140648418216402.transcr...@bugs.debian.org
Bug#756147: closed by Ben Hutchings (Re: Bug#756147: scsi-common-modules-3.2.0-4-amd64-di: cannot PXE install on VMware)
On Sun, 2014-07-27 at 09:58 -0500, Scott Coil wrote: > Perhaps this bug is filed under the incorrect package, however, I still > believe this to be a bug as it is impossible to install in a detached > environment using the distributed ISO. Neither the udeb's provided by > the ISO or the netboot initrd provide the scsi_transport_spi module > which is needed to install in an ESX environment. > > Mirroring the upstream repo is undesirable as I need a static set of > package versions. I should be able to serve the mounted ISO to PXE > install, but due to this missing module I am unable to do so. I don't think this is a supported installation method. You should either use the netboot image and provide access to a mirror (not an ISO image), or use one of the CD/DVD images. > As far as I see, the answer is to either add the module to the initrd > or add the udeb to the ISO. Adding to the ISO seems more ideal to me as > it keeps the size of the initrd down. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
Bug#747922: kernel hang during boot on s390x in a virtual machine under z/VM when logged on to a terminal
Control: tag -1 patch On Sat, 2014-07-26 at 13:46 -0400, Stephen Powell wrote: > I have been working with upstream on this. Upstream has sent me > a patch, which I have applied and tested, and it seems to fix the > problem. Here is a link to the patch: > >http://users.wowway.com/~zlinuxman/119-3215-hangs.diff > > This patch is not yet official, but an official patch should be > submitted to kernel.org soon, if it hasn't been already. Thanks. This looks like a sensible change so far as I can understand it, but since I know nothing of s390 drivers I would like to see it go through upstream review before applying it. Please let us know when that has happened. Ben. -- Ben Hutchings Always try to do things in chronological order; it's less confusing that way. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#747922: kernel hang during boot on s390x in a virtual machine under z/VM when logged on to a terminal
Processing control commands: > tag -1 patch Bug #747922 [linux] kernel hang during boot on s390x in a virtual machine under z/VM when logged on to a terminal Added tag(s) patch. -- 747922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b747922.140650303023572.transcr...@bugs.debian.org
Bug#686636: Please backport virtio-scsi to wheezy
On Fri, 2014-07-25 at 23:17 +0200, Cyril Brulebois wrote: > Control: tag -1 patch > > Ron (2014-07-26): > > Hi, > > > > The virtio_scsi module got backported to the 3.2.39-1 kernel, > > but it appears it didn't get added to the virtio-modules udeb > > for the wheezy kernels -- which means you can switch to using > > it for an already installed wheezy guest in a VM, but you can't > > install a new VM configured to use it with the wheezy installer. > > > > Please consider adding this to virtio-modules for the wheezy > > branch to complete this (very welcome!) backport. > > Looking at the sid package, this module was added to the virtio-modules > package unconditionally (doesn't depend on the arch, as opposed to the > pci one); that happened in r20402, in preparation for 3.10.1-1. > > I've just looked at all linux-image-* binaries built from linux > 3.2.60-1+deb7u1, and all contain that module but two[*], so I'm not > entirely sure about its arch-independence. The attached patch (against > the wheezy svn branch) might do the work, or might need an extra '?'. > > [*] The two packages are the s390* -tape variants, which were dropped in > the meanwhile: > linux-image-3.2.0-4-s390x-tape_3.2.60-1+deb7u1_s390.deb > linux-image-3.2.0-4-s390x-tape_3.2.60-1+deb7u1_s390x.deb Those packages don't have *any* modules! I forget how they work - possibly they have the same release string as the regular package and can share their modules? Anyway, I think your patch will work. Ben. -- Ben Hutchings Always try to do things in chronological order; it's less confusing that way. signature.asc Description: This is a digitally signed message part
Processed: closing 686636, cloning 686636, submitter -1, retitle -1 to virtio-scsi is not included in installer ...
Processing commands for cont...@bugs.debian.org:
> close 686636 3.2.39-1
Bug #686636 [linux] Please backport virtio-scsi to wheezy
There is no source info for the package 'linux' at version '3.2.39-1' with
architecture ''
Unable to make a source version for version '3.2.39-1'
Marked as fixed in versions 3.2.39-1.
Bug #686636 [linux] Please backport virtio-scsi to wheezy
Marked Bug as done
> clone 686636 -1
Bug #686636 {Done: Ben Hutchings } [linux] Please
backport virtio-scsi to wheezy
Bug 686636 cloned as bug 756249
> submitter -1 Ron
Bug #756249 {Done: Ben Hutchings } [linux] Please
backport virtio-scsi to wheezy
Changed Bug submitter to 'Ron ' from 'Faidon Liambotis
'
> retitle -1 virtio-scsi is not included in installer
Bug #756249 {Done: Ben Hutchings } [linux] Please
backport virtio-scsi to wheezy
Changed Bug title to 'virtio-scsi is not included in installer' from 'Please
backport virtio-scsi to wheezy'
> found -1 3.2.39-1
Bug #756249 {Done: Ben Hutchings } [linux] virtio-scsi is
not included in installer
There is no source info for the package 'linux' at version '3.2.39-1' with
architecture ''
Unable to make a source version for version '3.2.39-1'
Marked as found in versions 3.2.39-1; no longer marked as fixed in versions
3.2.39-1 and reopened.
> fixed -1 3.10.1-1
Bug #756249 [linux] virtio-scsi is not included in installer
There is no source info for the package 'linux' at version '3.10.1-1' with
architecture ''
Unable to make a source version for version '3.10.1-1'
Marked as fixed in versions 3.10.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
686636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686636
756249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/handler.s.c.140650406328690.transcr...@bugs.debian.org
Processed: notfound 756249 in 3.2.23-1, severity of 756249 is important
Processing commands for cont...@bugs.debian.org: > notfound 756249 3.2.23-1 Bug #756249 [linux] virtio-scsi is not included in installer There is no source info for the package 'linux' at version '3.2.23-1' with architecture '' Unable to make a source version for version '3.2.23-1' No longer marked as found in versions 3.2.23-1. > severity 756249 important Bug #756249 [linux] virtio-scsi is not included in installer Severity set to 'important' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 756249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756249 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.140650439630154.transcr...@bugs.debian.org
