Bug#383807: Missing PCI IDs in the sata_via driver

2006-09-23 Thread Julien Louis
On Sat, Aug 19, 2006 at 08:26:33PM +0200, Martin Michlmayr wrote: > > The ubuntu dapper kernel include them and seems to work fine with the > > following > > line : > > { 0x1106, 0x0591, PCI_ANY_ID, PCI_ANY_ID, 0, 0, vt6420 }, > > Someone submitted a patch to the kernel folks to add this

Bug#387168: Missing SATA support for VIA VT8251 based boards

2006-09-23 Thread Marc 'HE' Brockschmidt
Heya, I just needed to download grml to install my new box, which is based on the VT8251 chipset. Please include the driver in the d-i kernel for etch, thanks. Marc, this is my PERSONAL needy self, not the release assistant one -- BOFH #335: the AA battery in the wallclock sends magnetic interfe

mkvmlinuz_24_powerpc.changes ACCEPTED

2006-09-23 Thread Debian Installer
Accepted: mkvmlinuz_24.dsc to pool/main/m/mkvmlinuz/mkvmlinuz_24.dsc mkvmlinuz_24.tar.gz to pool/main/m/mkvmlinuz/mkvmlinuz_24.tar.gz mkvmlinuz_24_powerpc.deb to pool/main/m/mkvmlinuz/mkvmlinuz_24_powerpc.deb Override entries for your package: mkvmlinuz_24.dsc - source devel mkvmlinuz_24_p

Re: Preparing linux-2.6 2.6.18-1

2006-09-23 Thread Sven Luther
On Sat, Sep 23, 2006 at 05:24:22PM +0200, Norbert Tretkowski wrote: > * Frederik Schueler wrote: > > Linux 2.6.18 has been released, and it looks like we can do a first > > upload today. > > Is there an .orig.tar.gz already? Sure, it was at http://kernel-archive.buildserver.net/debian-kernel sin

Bug#389064: linux-image-2.6.17-2-k7: Sporadic Keyboard Freezes for some applications

2006-09-23 Thread Edgar Ibsen
Package: linux-image-2.6.17-2-k7 Severity: important The only reason that I submitted this bug under this package is because upgrading from 2.6.15 to 2.6.17 seems to cause this bug; I don't remember any instances of it when I was using 2.6.15, but since I've upgraded to 2.6.17 two days ago I'v

Re: config change: old ptys

2006-09-23 Thread Bastian Blank
On Sat, Sep 23, 2006 at 05:28:09PM +0200, Bastian Blank wrote: > Will anyone object if I lower the count of old-style ptys to 16? Or > should we finaly disable it completely? Some arches already disabled it. Bastian -- Not one hundred percent efficient, of course ... but nothing ever is.

config change: old ptys

2006-09-23 Thread Bastian Blank
Hi folks Will anyone object if I lower the count of old-style ptys to 16? Or should we finaly disable it completely? Bastian -- The face of war has never changed. Surely it is more logical to heal than to kill. -- Surak of Vulcan, "The Savage Curtain", stardate 5906.5 signatu

Re: Preparing linux-2.6 2.6.18-1

2006-09-23 Thread Norbert Tretkowski
* Frederik Schueler wrote: > Linux 2.6.18 has been released, and it looks like we can do a first > upload today. Is there an .orig.tar.gz already? Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#361684: is unuseable on HP OmniBook 4150 on batteries

2006-09-23 Thread maximilian attems
please keep bugreport on cc :) On Sat, Sep 23, 2006 at 03:34:32PM +0200, Ronny Standtke wrote: > > not reading the previous part of your bug report, i have no idea > > what you mean by unusable, > > FYI here is the previous part of my bug report: > > If the notebook is booted when runnin

Bug#361684: is unuseable on HP OmniBook 4150 on batteries

2006-09-23 Thread maximilian attems
On Sat, Sep 23, 2006 at 01:56:33PM +0200, Ronny Standtke wrote: > I just want to add that I updated to the latest version of Debian testing > (linux-2.6.17) and the bug is still there: The notebook is unuseable when > running on batteries. not reading the previous part of your bug report, i have

Bug#361684: is unuseable on HP OmniBook 4150 on batteries

2006-09-23 Thread Ronny Standtke
I just want to add that I updated to the latest version of Debian testing (linux-2.6.17) and the bug is still there: The notebook is unuseable when running on batteries. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: found 378225 in 2.6.17-9

2006-09-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.21 > found 378225 2.6.17-9 Bug#378225: suspend to memory broken in 2.6.17 on Dell Latitude C610 Bug marked as found in version 2.6.17-9. > End of message, stopping processing here. Pleas

Re: Preparing linux-2.6 2.6.18-1

2006-09-23 Thread Steve Langasek
[Dropping -release from cc anyway; there's no possible reason this needs to be cross-posted to 4 lists] On Fri, Sep 22, 2006 at 07:12:53AM +0200, Sven Luther wrote: > On Thu, Sep 21, 2006 at 02:58:31AM -0500, Bill Allombert wrote: > > On Thu, Sep 21, 2006 at 08:52:15AM +0200, Sven Luther wrote: >

Re: Let's vote ...

2006-09-23 Thread Manoj Srivastava
Hi, On Fri, 22 Sep 2006 07:21:12 +0200, Sven Luther <[EMAIL PROTECTED]> said: > This issue remains, and it is still not solved. This has got the > approval of Steve Langasek (who said that his proposal and this > where orthogonal and a separate GR), of our DPL, who said he would > postpone his ow

Bug#387781: closed by Frans Pop <[EMAIL PROTECTED]> (Re: Bug#387781: Install failed on SATA drive)

2006-09-23 Thread Michael Burschik
I can confirm that 2.6.18 detects the SATA disk. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#375194: Can you test 2.6.18-rc7 ...

2006-09-23 Thread Sven Luther
On Tue, Sep 19, 2006 at 08:38:42PM +0200, maximilian attems wrote: > On Tue, Sep 19, 2006 at 08:26:11PM +0300, Yavor Doganov wrote: > > maximilian attems wrote: > > > > > > ppc builds modular input i8042, so we need to try to modprobe it. > > > > > > is your root device there when you are dropped

Re: proposal: kernel team IRC meeting on Saturday, 30th September 16:00 UTC

2006-09-23 Thread Sven Luther
On Fri, Sep 22, 2006 at 08:56:58PM -0700, Jurij Smakov wrote: > On Fri, Sep 22, 2006 at 01:37:18PM +0200, Frederik Schueler wrote: > > > I would like to propose an IRC meeting for all kernel team members, to > > discuss where we stand and what we want to do in the future, concerning > > kernel fir