Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-12etch2
Severity: normal
After upgrading my notebook from sarge to etch special touchpad
features like scrolling with fingers didn't work any longer. I was
able to track down the problem to the psmouse module, which is not
able to detect
Julien Puydt escreveu:
I can confirm the same issue with 2.6.22-1 too, now it is out.
The ide-generic in /etc/initramfs-tools/modules trick also allows me to
boot, but without DMA. My BIOS doesn't have any ide legacy, and is as up
to date as possible (box is soon 3 years old).
It was
Duplicate of #432650
--
Marco de Freitas,
NBR para a Internet já! Porque meu navegador não é penico.
http://www.softwarelivre.org/news/2472
http://www.w3.org/2003/03/Translations/byLanguage?language=pt-br
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.6
tags 433768 sid lenny
Bug#433768: getdent(3) broken on hppa
Tags were: patch
Bug#427398: scandir syscall broken on hppa
Bug#431773: libqt4-dev: Missing mkspec files on hppa
Tags added:
Hi Maximilian,
thank you for your quick answer.
maximilian attems [EMAIL PROTECTED]:
On Thu, Jul 26, 2007 at 08:38:32PM +0200, Erik Schanze wrote:
Now kernel 2.6.22 is in Debian and the kernel team has disabled
CONFIG_IEEE1394, thus rendering dvgrab utterly useless with that
kernel. It
Hi Debian Kernel Maintainers,
I'm the Debain Maintainer for dvgrab.
I have received a bugreport (#432614) for it. Running dvgrab on
kernel 2.6.21 works with this warning in syslog:
kernel: raw1394: WARNING - Program dvgrab uses unsupported
isochronous request types which will be removed in
On Thu, Jul 26, 2007 at 07:42:20PM +0200, Bastian Blank wrote:
On Thu, Jul 26, 2007 at 10:47:00AM -0600, dann frazier wrote:
We need to decide which arches needs this rewrite now and which value
should be filed in.
And also, how should we re-write them? Should we just provide
On Thu, Jul 26, 2007 at 10:47:00AM -0600, dann frazier wrote:
We need to decide which arches needs this rewrite now and which value
should be filed in.
And also, how should we re-write them? Should we just provide
documentation, or also provide a utility to do it?
You don't want to do
On Thu, Jul 26, 2007 at 11:40:19AM +0200, Bastian Blank wrote:
Hi folks
For the libata-pata support we need to change fstab on several arches to
not break all systems which uses them.
Not to mention bootloader configs and other things that may handle
dump partitions.
We need to decide
One workaround found: use vanilla 2.6.22.1 which defaults to
libata. I also unset EFI_PARTITION with 2.6.22.1, but I don't think that
solved it.
In my case, when disk content was already under lvm, only grub option for
root filesystem needed a change from /dev/hda2 to /dev/sda2.
Are pata and
Bastian Blank [EMAIL PROTECTED] writes:
On Thu, Jul 26, 2007 at 01:23:51PM +0200, Goswin von Brederlow wrote:
Which of those change and why?
None.
I don't see how an libata update would change the serial number of the
disk, the filesystem label,
/dev/hd* is gone.
Bastian
Ok, THAT
Hi,
I've the same problem but my disks are scsi ones. So I can't change in fstab
hda to sda since I've already sda...
--
+---+
| gpe92 |
+---+
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Thu, Jul 26, 2007 at 08:38:32PM +0200, Erik Schanze wrote:
Hi Debian Kernel Maintainers,
I'm the Debain Maintainer for dvgrab.
I have received a bugreport (#432614) for it. Running dvgrab on
kernel 2.6.21 works with this warning in syslog:
kernel: raw1394: WARNING - Program dvgrab uses
Package: linux-2.6
Version: 2.6.22-2
Severity: normal
Hi,
Summary: echo 0 /proc/sys/vm/vdso_enabled hangs my kernel.
Since some months, I get unusable backtraces from gdb; I was pointed at
an OpenSuse bug at:
https://bugzilla.novell.com/show_bug.cgi?id=258433
which suggests
Your message dated Thu, 26 Jul 2007 11:57:43 +0200
with message-id [EMAIL PROTECTED]
and subject line Fixed
has caused the attached Bug report 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
On Thu, Jul 26, 2007 at 01:23:51PM +0200, Goswin von Brederlow wrote:
Which of those change and why?
None.
I don't see how an libata update would change the serial number of the
disk, the filesystem label,
/dev/hd* is gone.
Bastian
--
Respect is a rational process
--
FYI: The status of the firmware-nonfree source package
in Debian's testing distribution has changed.
Previous version: 0.4
Current version: 0.6
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more information.
On Thu, Jul 26, 2007 at 03:59:17PM +0200, Goswin von Brederlow wrote:
At a minimum you could fail in preinst if /dev/hd* is in fstab and
recommend to use one of the alternatives and explain how to look up
the right value.
This does not scale.
Bastian
--
Conquest is easy. Control is not.
* Date: Thu, 26 Jul 2007 15:21:49 +0200
Package: linux-2.6
Version: 2.6.22-2
Severity: normal
[--]
Summary: echo 0 /proc/sys/vm/vdso_enabled hangs my kernel.
Since some months, I get unusable backtraces from gdb; I was pointed at
an OpenSuse bug at:
19 matches
Mail list logo
