Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #78314 > unrolled thread

Bug#1031564: linux-image-cloud-amd64: Please include e1000 and e1000e modules in cloud kernel.

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1031564: linux-image-cloud-amd64: Please include e1000 and e1000e modules in cloud kernel. Witold Baryluk <witold.baryluk@gmail.com> - 2023-02-18 19:00 +0100
    Processed: Re: Bug#1031564: linux-image-cloud-amd64: Please  include e1000 and e1000e modules in cloud kernel. "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-02-20 09:10 +0100
    Bug#1031564: linux-image-cloud-amd64: Please include e1000 and e1000e modules in cloud kernel. Bastian Blank <waldi@debian.org> - 2023-02-20 09:10 +0100
    Bug#1031564: marked as done (linux-image-cloud-amd64: Please  include e1000 and e1000e modules in cloud kernel.) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-02-20 09:50 +0100

#78314 — Bug#1031564: linux-image-cloud-amd64: Please include e1000 and e1000e modules in cloud kernel.

Package: linux-image-cloud-amd64
Severity: normal
X-Debbugs-Cc: witold.baryluk@gmail.com

e1000 emulation is a default in qemu. It would be nice to have available
in a cloud kernel. While most of the time one will use virtio, or some
other cloud specific driver, for troubleshooting images, booting system
images in recovery mode, manually, etc, it is good to have e1000 as it is
easy to run in qemu.

For completeness this is how it presents in lspci:

00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 03)

This is with default qemu settings. (i440fx chipset).

With -M q35 (which is also very commonly used), qemu defaults to using:

00:02.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

This is handled by e1000e module.

As far as I know neither of these modules require any firmware files. And
qemu emulated device would not use it anyway.

So please include e1000 and e1000e in default cloud kernel image buld.

While at it, it would be nice to have ptp module probably. And ptp_kvm (I
actually use that on real cloud instances, not just in qemu).

As of the file size, for rather unknown reasons the e1000.ko and
e1000e.ko files are rather large, 300KB and 616KB on my system. Plus
another 49K for ptp. It is a little more than expected. My guess this is
due to inclusion of debug symbols. One way or another, it should be
included in the cloud image.


Regards,
Witold

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.2.0-rc5 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-cloud-amd64 depends on:
pn  linux-image-6.1.0-5-cloud-amd64  <none>

linux-image-cloud-amd64 recommends no packages.

linux-image-cloud-amd64 suggests no packages.

[toc] | [next] | [standalone]

#78320 — Processed: Re: Bug#1031564: linux-image-cloud-amd64: Please include e1000 and e1000e modules in cloud kernel.

Processing control commands:

> tag -1 wontfix
Bug #1031564 [linux-image-cloud-amd64] linux-image-cloud-amd64: Please include e1000 and e1000e modules in cloud kernel.
Added tag(s) wontfix.

-- 
1031564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031564
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#78321

Control: tag -1 wontfix

On Sat, Feb 18, 2023 at 05:54:31PM +0000, Witold Baryluk wrote:
> e1000 emulation is a default in qemu. It would be nice to have available
> in a cloud kernel. While most of the time one will use virtio, or some
> other cloud specific driver, for troubleshooting images, booting system
> images in recovery mode, manually, etc, it is good to have e1000 as it is
> easy to run in qemu.

qemu is not in scope for the cloud kernel.  You can read about the scope
in the packages description.

And you can easily select virtio network while running qemu, which will
work.

Bastian

-- 
If I can have honesty, it's easier to overlook mistakes.
		-- Kirk, "Space Seed", stardate 3141.9

[toc] | [prev] | [next] | [standalone]

#78322 — Bug#1031564: marked as done (linux-image-cloud-amd64: Please include e1000 and e1000e modules in cloud kernel.)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Mon, 20 Feb 2023 09:43:44 +0100
with message-id <Y/MywFDvavpgO1vg@shell.thinkmo.de>
and subject line Re: Bug#1031564: linux-image-cloud-amd64: Please include e1000 and e1000e modules in cloud kernel.
has caused the Debian Bug report #1031564,
regarding linux-image-cloud-amd64: Please include e1000 and e1000e modules in cloud kernel.
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 owner@bugs.debian.org
immediately.)


-- 
1031564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031564
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web