Sorry I haven't gotten back to you until now.
On Tue, Apr 01, 2008 at 07:53:44AM EST, maximilian attems wrote:
> On Wed, 27 Feb 2008, Luke Yelavich wrote:
>
> > Attached is a patch to improve the way update-initramfs handles the
> > generating of new or updated initramfs images for kernels. It pu
Totally weird. Today /dev/disk/by-id/ata* in fstab couldn't be dealt with
upon boot, but I still could login as root (with only the root
partition mounted), whereupon I did reboot(8), and miraculously this
time the boot went smoothly!
So one does not need to rerun lilo, nor change /etc/fstab at al
FYI: The status of the linux-2.6 source package
in Debian's testing distribution has changed.
Previous version: 2.6.24-4
Current version: 2.6.24-5
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more information.
Hi,
I had a problem similar to yours, but today I finally got iwlwifi to
work! Have you tried different values for wpa-scan-ssid and
wpa-ap-scan? 0 and 1 respectively were the winning combination for
me...
There was one other thing that screwed me big time when switching from
ipw3945 to iwlwifi: I
On Mon, Apr 07, 2008 at 08:20:52PM +0200, Thomas Zander wrote:
> > The versions includes (2.14.1.5 and 4.44.1.20) are the newest.
> Not sure how they number; but .4 seems higher than .1.5 to me...
> http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-3945-ucode-2.14.4.tgz
> I used this link and
On Friday 4. April 2008 12:19:54 Bastian Blank wrote:
> > I went to the intel website and downloaded the newest firmware. A week
> > later I have not seen any of the above problems anymore.
> > Please consider upgrading the firmware in debian to the latest released.
>
> The versions includes (2.14.
There's a discussion of this bug and patches at:
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1209
Probably this should be reassigned to the kernel.
Dave
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, 07 Apr 2008, Alan Jenkins wrote:
> To resume from a swap file within a partition using the original swsusp,
> you find the block offset of the swap file header using e.g. swap-offset
> from the uswsusp package, and add "resume=" and
> "resume_offset=" parameters to the kernel command
tags 474691 pending
stop
On Mon, 07 Apr 2008, Alan Jenkins wrote:
> To resume from a swap file within a partition using the original swsusp,
> you find the block offset of the swap file header using e.g. swap-offset
> from the uswsusp package, and add "resume=" and
> "resume_offset=" parame
On Mon, Apr 07, 2008, maximilian attems wrote:
> On Mon, Apr 07, 2008 at 11:21:24AM +0200, Sam Hocevar wrote:
> >Okay, but I'm not asking for CONFIG_SECCOMP_DISABLE_TSC, just
> > CONFIG_SECCOMP, which is completely harmless (unless you can tell me
> > where the harm is).
>
> it adds useless bl
On Mon, Apr 07, 2008 at 11:21:24AM +0200, Sam Hocevar wrote:
>Okay, but I'm not asking for CONFIG_SECCOMP_DISABLE_TSC, just
> CONFIG_SECCOMP, which is completely harmless (unless you can tell me
> where the harm is).
it adds useless bloat.
the SECCOMP_DISABLE_TSC is crazy, that is adding a co
Processing commands for [EMAIL PROTECTED]:
> tags 474691 pending
Bug#474691: Can't resume from swap file hibernation (as opposed to partition)
Tags were: patch
Tags added: pending
> stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
On Mon, Apr 07, 2008, maximilian attems wrote:
> On Mon, Apr 07, 2008 at 12:47:56AM +0200, Sam Hocevar wrote:
> >
> > CONFIG_SECCOMP was disabled for performance reasons, but it has always
> > been harmless. Quoting the author:
> >
> > | On x86-64 SECCOMP generates absoutely zero performance hit
On Mon, Apr 07, 2008 at 10:08:47AM +0200, [EMAIL PROTECTED] wrote:
> Hello,
>
> As there is a new upgrade on package linux-image-2.6
> I'm wondering if I can apply this upgrade without risk of hanging one more
> time my production server ?
you never provided any error message, so your bug repor
On Mon, Apr 07, 2008 at 07:51:41AM +, maximilian attems wrote:
> that is a commercial entity, no need to push that.
>
> unless something substantial comes up that bug can be close right away.
It seems that you're not really forced to use the commercial side. CPUShare
may be use freely if you
Package: initramfs-tools
Version: 0.91e
Severity: wishlist
Tags: patch
To resume from a swap file within a partition using the original swsusp,
you find the block offset of the swap file header using e.g. swap-offset
from the uswsusp package, and add "resume=" and
"resume_offset=" parameters t
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.26
> severity 457044 important
Bug#457044: My box doesn't reboot after each upgrade of linux-image
Severity set to `important' from `important'
>
End of message, stopping processing here.
Hello,
As there is a new upgrade on package linux-image-2.6
I'm wondering if I can apply this upgrade without risk of hanging one more
time my production server ?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.20
> severity 457044 important
Bug#457044: My box doesn't reboot after each upgrade of linux-image
Severity set to `important' from `critical'
>
End of message, stopping processing here.
On Mon, Apr 07, 2008 at 12:47:56AM +0200, Sam Hocevar wrote:
>
> CONFIG_SECCOMP was disabled for performance reasons, but it has always
> been harmless. Quoting the author:
>
> | On x86-64 SECCOMP generates absoutely zero performance hit.
> |
> | The original seccomp patch for x86 also genera
Processing commands for [EMAIL PROTECTED]:
> severity 457044 critical
Bug#457044: My box doesn't reboot after each upgrade of linux-image
Severity set to `critical' from `important'
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Processing commands for [EMAIL PROTECTED]:
> retitle 457044 My box doesn't reboot after each upgrade of linux-image
Bug#457044: My box didn't reboot after upgrading linux-image-2.6.18-4-686
Changed Bug title to `My box doesn't reboot after each upgrade of linux-image'
from `My box didn't reboot a
22 matches
Mail list logo