Bug#865120: release-notes: document i386/amd64 kernel changes for jessie->stretch
On Sat, 2018-05-05 at 09:44 +0900, Masanori Goto wrote: > Recently I encountered this amd64 kernel issue on my i386 architecture > machine. I think this is useful to be mentioned. Why don't we want to > apply this proposed text? > > > You're quite right, this should have been documented. It might be > > worth mentioning linux-headers-amd64 as well. Also, module-assistant > > doesn't support foreign architectures but DKMS is fine. > > +1 to linux-headers-amd64. One tricky thing is, this is not officially > supported so module-assistant doesn't work, so that should be clearly > mentioned. I also had some issues to install some kernel related > packages (e.g. virtualbox-dkms) so I'm not sure DKMS is fine or not - > I rather think DMKS also doesn't work but I'd like to hear your > feedback. Should we also mention that? [...] Some module packages do their own architecture detection and may fail when the primary architecture is i386 and the kernel flavour is amd64. This can happen regardless of what architecture the kernel package is labelled as! DKMS itself doesn't seem to have a problem with it. At some point I tested the available DKMS-based packages with this configuration and reported bugs, but there may have been regressions since then. Where module-assistant goes wrong is that it always sets the package architecture to be the primary architecture. I looked at fixing this, but there's no one place to fix it as every dependent package duplicates logic and templates. DKMS doesn't normally build or install packages, so it doesn't have this problem. Ben. -- Ben Hutchings If more than one person is responsible for a bug, no one is at fault. signature.asc Description: This is a digitally signed message part
Bug#865120: release-notes: document i386/amd64 kernel changes for jessie->stretch
Masanori Goto wrote: > Recently I encountered this amd64 kernel issue on my i386 architecture > machine. I think this is useful to be mentioned. Why don't we want to > apply this proposed text? I don't know anything about how widespread or critical or worthy of documentation this bug might be, but I notice a couple of lines that have English language problems sneaking back in. > > Users are advised that the -amd64 flavor of kernel > is no longer provided for the i386 architecture. > Instead, these kernels are available and installed directly from amd64 "Available and installed" makes it sound as if the kernels are already automatically installed (and if they can be installed then it's obvious that they're available). My draft had These kernels should instead be installed directly from the amd64 (With definite article) > architecture, using multiarch, the mechanism allowing the > installation of foreign-architecture packages. > > > > > >To check if you are running i386 user space with >amd64 kernel, run: >dpkg --print-architecture; uname -r (would give >i386 and a flavor ending in >-amd64). > > > > > >To add amd64 as a foreign architecture, run: >dpkg --add-architecture amd64; apt-get update > > > > >(Install the appropriate kernel metapackage as described above.) > > > > > > Note that installing kernel modules are not officially supported > through module-assistant. > Number agreement fix: Note that installing kernel modules is not officially supported through module-assistant. But hang on, surely that's not true - handling kernel modules is the one and only thing module-assistant *does* officially support! Don't you mean something more like this? Note that module-assistant does not officially support foreign-architecture kernel modules. (So maybe it should add "but DKMS does"?) -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Bug#865120: release-notes: document i386/amd64 kernel changes for jessie->stretch
Recently I encountered this amd64 kernel issue on my i386 architecture machine. I think this is useful to be mentioned. Why don't we want to apply this proposed text? > You're quite right, this should have been documented. It might be > worth mentioning linux-headers-amd64 as well. Also, module-assistant > doesn't support foreign architectures but DKMS is fine. +1 to linux-headers-amd64. One tricky thing is, this is not officially supported so module-assistant doesn't work, so that should be clearly mentioned. I also had some issues to install some kernel related packages (e.g. virtualbox-dkms) so I'm not sure DKMS is fine or not - I rather think DMKS also doesn't work but I'd like to hear your feedback. Should we also mention that? Based on Justin's feedback, here's the change - who can pick up this documentation updates? Users are advised that the -amd64 flavor of kernel is no longer provided for the i386 architecture. Instead, these kernels are available and installed directly from amd64 architecture, using multiarch, the mechanism allowing the installation of foreign-architecture packages. To check if you are running i386 user space with amd64 kernel, run: dpkg --print-architecture; uname -r (would give i386 and a flavor ending in -amd64). To add amd64 as a foreign architecture, run: dpkg --add-architecture amd64; apt-get update (Install the appropriate kernel metapackage as described above.) Note that installing kernel modules are not officially supported through module-assistant.
Bug#865120: release-notes: document i386/amd64 kernel changes for jessie->stretch
Stuart Prescott wrote: > With Stretch, amd64 flavour kernels are no longer supplied within the i386 > Debian architecture (i.e. for a 64 bit kernel with a 32 bit userspace). The > release notes should document that these kernel packages are no longer > offered so that users don't accidentally run unsupported kernels indefinitely > (hence severity:important). > > The upgrade path is to enable amd64 as a foreign architecture and then install > the relevant amd64 kernel image. > > A 0th draft at some wording for §4.6/4.6.1: Ben has pointed out a couple of extra things that ought to be mentioned; I'm basically just nitpicking the spelling and so on. > Users of the i386 port are advised that the amd64 flavour of kernel We're standardising to en_US, so it's a kernel "flavor" (but no, not "advized"). > is no longer included within the i386 port but that these kernels i386 isn't exactly a "port"; I'd suggest sticking to "the i386 architecture". However, since the text varies from arch to arch, the version that's shown to i386 users can afford to be slightly less wordy about it. I'd suggest: Users are advised that the -amd64 flavor of kernel is no longer provided for the i386 architecture. These kernels > should instead be installed directly from the amd64 port using the > ability for apt and dpkg to install foreign architecture packages > (known as multiarch). (Perhaps phrase this as "using multiarch, the mechanism allowing the installation of foreign-architecture packages"?) > - check if running i386 userspace with amd64 kernel: > `dpkg --print-architure` is i386, and > `uname -r` ends in amd64 > Typo: --print-archiTECture. Here's a version bringing it slightly closer to full sentences: To check if you are running i386 userspace with amd64 kernel, run: dpkg --print-architecture; uname -r (would give i386 and a flavor ending in -amd64). > - add amd64 as foreign architecture > `dpkg --add-architecture amd64; apt-get update` > > - (install the appropriate kernel metapackage as described already) To add amd64 as a foreign architecture, run: dpkg --add-architecture amd64; apt-get update (Install the appropriate kernel metapackage as described above.) -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Bug#865120: release-notes: document i386/amd64 kernel changes for jessie->stretch
On Mon, 2017-06-19 at 23:37 +1000, Stuart Prescott wrote: > Package: release-notes > Severity: important > > With Stretch, amd64 flavour kernels are no longer supplied within the i386 > Debian architecture (i.e. for a 64 bit kernel with a 32 bit userspace). The > release notes should document that these kernel packages are no longer > offered so that users don't accidentally run unsupported kernels indefinitely > (hence severity:important). [...] You're quite right, this should have been documented. It might be worth mentioning linux-headers-amd64 as well. Also, module-assistant doesn't support foreign architectures but DKMS is fine. Ben. -- Ben Hutchings Experience is directly proportional to the value of equipment destroyed. - Carolyn Scheppner signature.asc Description: This is a digitally signed message part
Bug#865120: release-notes: document i386/amd64 kernel changes for jessie->stretch
Package: release-notes Severity: important With Stretch, amd64 flavour kernels are no longer supplied within the i386 Debian architecture (i.e. for a 64 bit kernel with a 32 bit userspace). The release notes should document that these kernel packages are no longer offered so that users don't accidentally run unsupported kernels indefinitely (hence severity:important). The upgrade path is to enable amd64 as a foreign architecture and then install the relevant amd64 kernel image. A 0th draft at some wording for §4.6/4.6.1: Users of the i386 port are advised that the amd64 flavour of kernel is no longer included within the i386 port but that these kernels should instead be installed directly from the amd64 port using the ability for apt and dpkg to install foreign architecture packages (known as multiarch). - check if running i386 userspace with amd64 kernel: `dpkg --print-architure` is i386, and `uname -r` ends in amd64 - add amd64 as foreign architecture `dpkg --add-architecture amd64; apt-get update` - (install the appropriate kernel metapackage as described already) cheers Stuart
