Re: Bug#903122: debian-installer-9-netboot-amd64: Please add char/virtio_console module (paravirtualized serial) to netinst

On Tue, 2018-07-10 at 02:32 +0200, Cyril Brulebois wrote: > Control: reassign -1 src:linux > Control: tag -1 patch > > Ben Hutchings (2018-07-09): > > I would say virtio-modules. All the virtio class drivers depend on > > virtio and virtio_ring, which means that adding them to any other > >

Bug#903437: firmware-atheros: Ath10k/QCA9377 doesn't work

Package: firmware-atheros Version: 20170823-1 Severity: important # [3.885977] ath10k_pci :07:00.0: firmware: failed to load ath10k/pre- cal-pci-:07:00.0.bin (-2) [3.885978] ath10k_pci :07:00.0: Direct firmware load for ath10k/pre-

Processed: Re: Bug#903122: debian-installer-9-netboot-amd64: Please add char/virtio_console module (paravirtualized serial) to netinst

Processing control commands: > reassign -1 src:linux Bug #903122 [debian-installer-9-netboot-amd64] debian-installer-9-netboot-amd64: Please add char/virtio_console module (paravirtualized serial) to netinst Bug reassigned from package 'debian-installer-9-netboot-amd64' to 'src:linux'. Ignoring

Re: Bug#903122: debian-installer-9-netboot-amd64: Please add char/virtio_console module (paravirtualized serial) to netinst

Control: reassign -1 src:linux Control: tag -1 patch Ben Hutchings (2018-07-09): > I would say virtio-modules. All the virtio class drivers depend on > virtio and virtio_ring, which means that adding them to any other > package would require that package to depend on virtio-modules. > > (The

Re: Bug#903122: debian-installer-9-netboot-amd64: Please add char/virtio_console module (paravirtualized serial) to netinst

On Sun, 2018-07-08 at 06:37 +0200, Cyril Brulebois wrote: [...] > Vincent Caron (2018-07-06): [...] > > If this module makes it to netinst's initrd, one would use those kvm > > args: > > > > -chardev file,path=virtiocon0.log,id=virtiocon0 > > -device virtio-serial > > -device

Bug#720528: nvidia: driver fails kernel 3.10+ (GeForce 600M and 700M series)

> Control: tag -1 moreinfo > > On Sat, 23 Aug 2014 22:53:48 -0700 Ben Hutchings > wrote: > > On Sat, 2014-08-23 at 20:14 -0700, Andres Cimmarusti wrote: > > > Let me re-state: worked with debian 3.9, broke with debian 3.11 (but > > > works with Ubuntu vanilla LTS 3.11.10.x series), worked with

Re: dkms: Build with an alternative like compiler rather than gcc

On Mon, Jul 9, 2018 at 4:43 PM, wrote: >> -Original Message- >> From: Sedat Dilek [mailto:sedat.di...@gmail.com] >> Sent: Monday, July 9, 2018 9:41 AM >> To: Limonciello, Mario >> Cc: p...@hungry.com; da...@debian.org; a...@debian.org; >> iucul...@debian.org;

RE: dkms: Build with an alternative like compiler rather than gcc

> -Original Message- > From: Petter Reinholdtsen [mailto:p...@hungry.com] > Sent: Monday, July 9, 2018 9:32 AM > To: sedat.di...@gmail.com; David Paleino; Aron Xu; Limonciello, Mario; > Giuseppe > Iuculano > Cc: Dynamic Kernel Modules Support Team; debian-kernel@lists.debian.org >

RE: dkms: Build with an alternative like compiler rather than gcc

> -Original Message- > From: Sedat Dilek [mailto:sedat.di...@gmail.com] > Sent: Monday, July 9, 2018 9:41 AM > To: Limonciello, Mario > Cc: p...@hungry.com; da...@debian.org; a...@debian.org; > iucul...@debian.org; pkg-dkms-ma...@lists.alioth.debian.org; debian- > ker...@lists.debian.org >

Re: dkms: Build with an alternative like compiler rather than gcc

On Mon, Jul 9, 2018 at 4:37 PM, wrote: >> -Original Message- >> From: Petter Reinholdtsen [mailto:p...@hungry.com] >> Sent: Monday, July 9, 2018 9:32 AM >> To: sedat.di...@gmail.com; David Paleino; Aron Xu; Limonciello, Mario; >> Giuseppe >> Iuculano >> Cc: Dynamic Kernel Modules

Re: dkms: Build with an alternative like compiler rather than gcc

On Mon, Jul 9, 2018 at 4:31 PM, Petter Reinholdtsen wrote: > > [Sedat Dilek] >> As a workaround I have symlinked my mycompiler wrapper-script to >> /usr/bin/gcc. That works. >> >> What is the recommended way to do this correctly? > > Perhaps you should use dpkg-divert to ensure your replaced gcc

Re: dkms: Build with an alternative like compiler rather than gcc

[Sedat Dilek] > As a workaround I have symlinked my mycompiler wrapper-script to > /usr/bin/gcc. That works. > > What is the recommended way to do this correctly? Perhaps you should use dpkg-divert to ensure your replaced gcc is not lost in a future package upgrade? The DKMS team in Debian

dkms: Build with an alternative like compiler rather than gcc

Hi, I am experimenting with clang to compile an upstream Linux kernel v4.14.y (here: y=54). For this I use bindeb-pkg make-target from Linus upstream. After installing the generated linux-headers and linux-image amd64 packages, the dkms kernel-modules were built with gcc-7 which defaults to gcc.

Bug#903393: [initramfs-tools] update-initramfs -u warns: Unknown X keysym "dead_belowmacron"

Package: initramfs-tools Version: 0.130 Severity: normal I experienced this when apt triggered initramfs-tools: Trigger für initramfs-tools (0.130) werden verarbeitet ... update-initramfs: Generating /boot/initrd.img-4.16.0-2-686 WARNING: Unknown X keysym "dead_belowmacron" WARNING: Unknown X

Bug#720528: nvidia: driver fails kernel 3.10+ (GeForce 600M and 700M series)

Control: tag -1 moreinfo On Sat, 23 Aug 2014 22:53:48 -0700 Ben Hutchings wrote: > On Sat, 2014-08-23 at 20:14 -0700, Andres Cimmarusti wrote: > > Let me re-state: worked with debian 3.9, broke with debian 3.11 (but > > works with Ubuntu vanilla LTS 3.11.10.x series), worked with debian > >

Processed: Re: Bug#720528: nvidia: driver fails kernel 3.10+ (GeForce 600M and 700M series)

Processing control commands: > tag -1 moreinfo Bug #720528 [src:linux] nvidia: driver fails kernel 3.10+ (GeForce 600M and 700M series) Added tag(s) moreinfo. -- 720528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720528 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#883294: Bug 197769 - kernel panic IO-APIC + timer (AMD CPU) from 4.13 onwards

Have you noticed https://bugzilla.kernel.org/show_bug.cgi?id=197769 *Bug 197769* - kernel panic IO-APIC + timer (AMD CPU) from 4.13 onwards seems very similiar to this debian-bug. In this context: > > > - Instead of not using IO-APIC