Package: linux-headers-amd64
Severity: normal
Dear Maintainer,
I've been using a i386 install running on an amd64 kernel for many
years, and recently a new problem showed up: to build kernel modules
`dkms` needs `linux-headers-amd64(:amd64)` and this package conflicts
with the 32bit GCC
> since the wrong package: linux-compiler-gcc-13-x86
> is isntalled.
Thanks... so this prompted me to dig again into the problem and this
time I found a workaround which consist in installing
`gcc-13-x86-64-linux-gnu` (which I found simply via `apt-file search
/usr/bin/x86_64-linux-gnu-gcc-13`.
>> I can answer this part: yes, you can definitely put an Intel wifi card
>> in the mini-pcie slot of an ARM box.
> This means that, in principle, we should enable many modules more to get
> as full support as desired in Debian on each and every arch...
My point wasn't just that it's technically
so the point is: if anyone wishes me to propose to allwinner that
they convert over to devicetree, or any other proposal which involves
significant low-level changes to their working practices that could
potentially have a massive knock-on effect onto their
multi-million-dollar clients, it
We believe that the bug you reported is fixed in the latest version of
Linux, which is due to be installed in the Debian FTP archive.
Indeed, I confirm that this problem is fixed in the linux-image-3.2.0-4
package that's now in `testing'. Thank you very much,
Stefan
--
To
In case you haven't followed https://bugs.freedesktop.org/show_bug.cgi?id=54615
I got a patch there which seems to fix this problem.
Stefan
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
reopen 686284
thanks
Version: 3.2.29-1
[...]
Patch applied; closing optimistically. An update about how recent
kernels behave would still be very welcome.
I just tested the 3.2.0-4-686-pae image (v3.2.30-1) and got pretty much
the same result. But check
Patch applied; closing optimistically. An update about how recent
kernels behave would still be very welcome.
I'm hoping to be able to test a new kernel within a week or two, thank
you,
Stefan
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of
forwarded 686284 https://bugs.freedesktop.org/show_bug.cgi?id=54615
thanks
- it also appears with experimental's 3.5.0-trunk
Good to hear. Please report this upstream following instructions
from [1], and let us know the bug number so we can track it.
Done,
Stefan
--
To
severity 686284 important
thanks
After further experimentation, I'm bumping this bug's severity:
- it also appears with experimental's 3.5.0-trunk (so sitting here,
waiting for a stream to trickle from upstream might not be a good plan).
- while blacklisting i915 lets me boot, it prevents s2ram
Package: src:linux
Version: 3.2.23-1
Severity: normal
Dear Maintainer,
The KMS code for the 82830 graphics chip has been problematic evr since its
introduction. Sometimes, booting works and Xorg's `intel' driver works as
well, but resume (from suspend or hibernate) typically doesn't and just
I can enable it right now,
That would be very welcome, yes.
but the next stable release (Debian 7.0, 'wheezy') will use Linux 3.2.
Yes, I know.
Do you want it added to that as well?
That would be super awesome, but the synaptics-usb module was only added
to the 3.4 kernel.
It looks like
Package: linux-2.6
Version: 3.4.1-1~experimental.1
Severity: normal
Dear Maintainer,
I'm looking forward to Debian's 3.4 kernel, mostly because it should
finally free me from manually compiling the synaptics-usb kernel
module I've been using for years now (pretty much the last such module,
Update: it turns out the problem is partly due to my graphics card
officially being unable to use my monitor's favorite modeline
(unofficially, it's worked fine for years, but nouveau installed
a bugfix that makes it obey the official limits).
Stefan
--
To UNSUBSCRIBE, email to
Please report this at
https://bugs.freedesktop.org/enter_bug.cgi?product=xorgcomponent=Driver/nouveau
I've just done that; in https://bugs.freedesktop.org/show_bug.cgi?id=40747
Stefan
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe.
Package: linux-2.6
Version: 2.6.39-2
Severity: normal
With linux-image-2.6.39-2-686-pae, my kernel's console does not use my
monitor's native resolution (1600x1200) and instead uses 1280x1024.
On the other hand linux-image-2.6.32-5-686-bigmem used 1600x1200 just fine.
My hardware is recognized by
Package: linux-image-2.6-686
Version: 2.6.32+28
Severity: important
As the subject explains, ever since my last reboot yesterday, I can't suspend
nor hibernate my T60, which is very inconvenient.
More specifically, when I try to suspend, the machine goes to sleep OK, but the
resume fails (the
Package: linux-kbuild-2.6.34
Version: 2.6.34-1~experimental.1
Severity: normal
linux-image-2.6.36 packges have been on experimental for a while now,
but there's still no trace of any accompagnying linux-kbuild.
This is apparently the usual way things work w.r.t experimental
kernel packages.
I
Package: linux-2.6
Version: 2.6.33-1~experimental.4
Severity: normal
I recently switched to the new 2.6.33 kernel because of its support
for the TRIM command for my SSD disk, but it turns out that it has one
very serious regression: its iwl3945 driver seems not to provide any
power-saving any
While I'm not convinced that there is still a need for a patch like
drivers-ata-ata_piix-postpone-pata.patch (whose name seems misleading
BTW), seeing how most/all other distributions don't bother with such
a thing, I'm willing to believe that there might still be occasional
situations where the
Package: ipw3945-modules-2.6.21-2-686
Version: 1.2.2-1+2.6.21-6
Severity: normal
The versioning info of the prebuilt packages seems to be different from
the versioning used by module-assistant, so that after auto-install'ing
the ipw3945-1.2.2-1 kernel module, aptitude wants to upgrade it to
Package: linux-image-2.6.20-1-686-bigmem
Version: 2.6.20-3
Severity: normal
When upgrading the package used by the currently running kernel,
the package installer give a big warning about how it's dangerous
and requires a prompt reboot.
In my case I'd much rather that such things simply *never*
22 matches
Mail list logo
