On Wed, 01 Jul 2015 14:05:57 -0400 (EDT), Ben Hutchings wrote:
>
> Please note that i2o will be going away entirely (disabled in 4.0,
> removed upstream in 4.2).
Thanks, Ben, I hadn't heard that; but it really doesn't have anything
to do with this bug, per se. I happened to discover it using an
Source: linux
Severity: wishlist
Dear Maintainer,
Please enable CONFIG_MMIOTRACE.
mmiotrace can provide very valuable information to the nouveau developers. But
to enable that, we currently need to rebuild the kernel, and rebuild the nvidia
blob against it.
>From ubuntu:
Enable MMIOTRACE to
On Wed, 2015-07-01 at 03:39 -0400, Stephen Powell wrote:
> Package: initramfs-tools
> Version: 0.120
> Severity: normal
>
> A recent upgrade of my stretch system via
>
>apt-get upgrade
>
> failed with
>
>mkinitramfs: failed to determine device for /
>
> I run with MODULES=dep in /etc/i
Package: initramfs-tools
Version: 0.120
Severity: normal
A recent upgrade of my stretch system via
apt-get upgrade
failed with
mkinitramfs: failed to determine device for /
I run with MODULES=dep in /etc/initramfs-tools/conf.d/driver-policy. My system
uses an i2o hardware RAID device, d
On Tue, Jun 30, 2015 at 06:25:42PM +0200, Bastian Blank wrote:
> You have several modules loaded that are not supported. You want to try
> it without first.
i've blacklisted those modules, even purged them -- still, when i
reboot, my kernel is tainted 4096 (O) after login; at that time, no
out-of
5 matches
Mail list logo
