On 5/31/24 10:04, Evgeny Kapun wrote:
After I upgraded my system, my integrated sound card (Intel HDA) stopped
working properly. The sound plays, but it is severely distorted.
If I boot the same system with an older kernel, it works. Currently, I am
using kernel 6.6.13+bpo-amd64, because newer v
After I upgraded my system, my integrated sound card (Intel HDA) stopped
working properly. The sound plays, but it is severely distorted.
If I boot the same system with an older kernel, it works. Currently, I
am using kernel 6.6.13+bpo-amd64, because newer versions that I tried
don't work (in
Hi,
I update my packages on Debian Bookworm, and one of them was the Linux kernel:
6.1.0-15 --> 6.1.66-1
I see that file /run/reboot-required exists, but I miss file
/run/reboot-required.pkgs
Has Debian removed in Bookworm naming the packages, which require a reboot, or
will the linux-image p
Hi Paul,
On Thu, Jun 29, 2023 at 06:27:02PM +0200, Paul Leiber wrote:
> Just to state the obvious, what's bothering me is that my setup was working
> with kernel 5.10.0-21 and that it stopped working with kernel 5.10.178-3. So
> it seems that somewhere inbetween, changes have been introduced that
Am 29.06.2023 um 01:45 schrieb Andy Smith:
On Wed, Jun 28, 2023 at 09:40:52PM +0200, Paul Leiber wrote:
In the meantime, I have upgraded Dom0 to Debian Bookworm with
linux-image-amd64 6.1.27-1 and Xen 4.17. The issue persists, seemingly
unchanged.
In DomU dmesg, there are several "swiotlb buff
Hi Paul,
On Wed, Jun 28, 2023 at 09:40:52PM +0200, Paul Leiber wrote:
> In the meantime, I have upgraded Dom0 to Debian Bookworm with
> linux-image-amd64 6.1.27-1 and Xen 4.17. The issue persists, seemingly
> unchanged.
>
> In DomU dmesg, there are several "swiotlb buffer is full" entries while
>
1 GB memory. I understand that 1 GB of memory for
Dom0 is not very much, but it was working well until the kernel update.
top in Dom0 shows that there is still free memory in Dom0 (although not
much).
What I tried:
-
1. Increasing the DomU memory to 384 MB didn't solve the issue.
On Wed 07 Jul 2021 at 23:43:57 (-0400), Polyna-Maude Racicot-Summerside wrote:
> On 2021-07-07 11:34 p.m., David Wright wrote:
> > If you want to be able to set and change the default entry to boot,
> > that's straightforward to do with GRUB_DEFAULT and GRUB_SAVEDEFAULT
> > in /etc/default/grub, as
On Mi, 07 iul 21, 20:11:20, Polyna-Maude Racicot-Summerside wrote:
> On 2021-07-07 5:55 p.m., Andrei POPESCU wrote:
> >
> > The default in the grub menu is typically the newest kernel installed,
> > regardless of when it was (re)installed.
> If this is true then all this talk is useless because h
On Wed, Jul 07, 2021 at 11:43:57PM -0400, Polyna-Maude Racicot-Summerside wrote:
[...]
> Wasn't it more simple when using Lilo or Syslinux (Keep It Simple for
> Stupid) ?
>
> Yes I know, grub have so much more but sometime you don't need that much
> and this just make it more complicated.
While
Hi,
On 2021-07-07 11:34 p.m., David Wright wrote:
> On Wed 07 Jul 2021 at 20:11:20 (-0400), Polyna-Maude Racicot-Summerside wrote:
>> On 2021-07-07 5:55 p.m., Andrei POPESCU wrote:
>>> On Mi, 07 iul 21, 16:05:13, Polyna-Maude Racicot-Summerside wrote:
On 2021-07-07 2:47 p.m., Andrei POPESCU w
On Wed 07 Jul 2021 at 20:11:20 (-0400), Polyna-Maude Racicot-Summerside wrote:
> On 2021-07-07 5:55 p.m., Andrei POPESCU wrote:
> > On Mi, 07 iul 21, 16:05:13, Polyna-Maude Racicot-Summerside wrote:
> >> On 2021-07-07 2:47 p.m., Andrei POPESCU wrote:
> >>> On Mi, 07 iul 21, 09:35:17, Polyna-Maude R
Hi,
On 2021-07-07 5:55 p.m., Andrei POPESCU wrote:
> On Mi, 07 iul 21, 16:05:13, Polyna-Maude Racicot-Summerside wrote:
>> Hi !
>>
>> On 2021-07-07 2:47 p.m., Andrei POPESCU wrote:
>>> On Mi, 07 iul 21, 09:35:17, Polyna-Maude Racicot-Summerside wrote:
Yes you can downgrand
apt-get d
On Wed 07 Jul 2021 at 16:05:13 (-0400), Polyna-Maude Racicot-Summerside wrote:
> On 2021-07-07 2:47 p.m., Andrei POPESCU wrote:
> > On Mi, 07 iul 21, 09:35:17, Polyna-Maude Racicot-Summerside wrote:
> >>
> >> Yes you can downgrand
> >> apt-get downlaod linux-image-4.19.0-16-amd64
> >> dpkg -i linux
On Mi, 07 iul 21, 16:05:13, Polyna-Maude Racicot-Summerside wrote:
> Hi !
>
> On 2021-07-07 2:47 p.m., Andrei POPESCU wrote:
> > On Mi, 07 iul 21, 09:35:17, Polyna-Maude Racicot-Summerside wrote:
> >>
> >> Yes you can downgrand
> >> apt-get downlaod linux-image-4.19.0-16-amd64
> >> dpkg -i linux-i
Hi !
On 2021-07-07 2:47 p.m., Andrei POPESCU wrote:
> On Mi, 07 iul 21, 09:35:17, Polyna-Maude Racicot-Summerside wrote:
>>
>> Yes you can downgrand
>> apt-get downlaod linux-image-4.19.0-16-amd64
>> dpkg -i linux-image-4.19.0.16-amd64.deb
>
> Why so complicated?
>
> If APT can download the pack
On Mi, 07 iul 21, 09:35:17, Polyna-Maude Racicot-Summerside wrote:
>
> Yes you can downgrand
> apt-get downlaod linux-image-4.19.0-16-amd64
> dpkg -i linux-image-4.19.0.16-amd64.deb
Why so complicated?
If APT can download the package it can also install it (by calling dpkg
itself, of course).
On Wed 07 Jul 2021 at 09:35:17 (-0400), Polyna-Maude Racicot-Summerside wrote:
> On 2021-07-07 7:59 a.m., Dan Ritter wrote:
> > w f wrote:
> >> I locally host and maintain some Minecraft (Java) servers for my kids and
> >> their friends. This morning, I kicked everyone off the servers while I did
Hi,
On 2021-07-07 7:59 a.m., Dan Ritter wrote:
> w f wrote:
>> I locally host and maintain some Minecraft (Java) servers for my kids and
>> their friends. This morning, I kicked everyone off the servers while I did
>> some routine maintenance. I finished with a standard sudo apt update && sudo
w f wrote:
> I locally host and maintain some Minecraft (Java) servers for my kids and
> their friends. This morning, I kicked everyone off the servers while I did
> some routine maintenance. I finished with a standard sudo apt update && sudo
> apt full-upgrade
> A few things were updated - PHP
The fcheck task take +45000 seconds to complete instead of +8500 after
latest kernel update. Server is running on ESX as VM.
Is somebody experiencing similar prolonging task execution on CPU
intensive tasks? May be related to L1TF "Spectre-family" patches.
What commands to run to inves
Paul Zimmerman composed on 2018-01-09 23:43 (UTC):
> After running "aptitude update" and "aptitude safe-upgrade" on my Wheezy
> boxes, I find I have TWO kernels installed. One of them, the new patch for
> this "Meltdown" problem, does not boot. It hangs. Fortunately, they were
> smart enough to ke
Hi,
On Tue, 9 Jan 2018 23:43:23 + (UTC)
Paul Zimmerman wrote:
> After running "aptitude update" and "aptitude safe-upgrade" on my
> Wheezy boxes, I find I have TWO kernels installed. One of them, the new
> patch for this "Meltdown" problem, does not boot. It hangs.
> Fortunately, they were s
Hi,
On 02/14/2017 12:58 AM, Daniel Bareiro wrote:
> Some time ago I read that Linux 4.x incorporates the feature to be
> updated without requiring a restart of the operating system.
They incorporated parts of that. There are still some unsolved issues.
See for example this article from last Nove
Hi, Sven.
On 14/02/17 10:19, Sven Hartge wrote:
> He thinks of mechanisms like ksplice or kpatch where you can
> alter/patch the running kernel without rebooting the system.
Yes, I had read some about this and that, for example, Ubuntu has it
available but as a paid service that one can hire. W
Hi, Darac.
On 14/02/17 10:01, Darac Marjal wrote:
>>> Some time ago I read that Linux 4.x incorporates the feature to be
>>> updated without requiring a restart of the operating system.
>> Some Linux Distributions have such a feature. Debian is not one of them.
> Actually, yes it is, you just n
Darac Marjal wrote:
> On Tue, Feb 14, 2017 at 01:46:08PM +0100, Sven Hartge wrote:
>> Daniel Bareiro wrote:
>>> Some time ago I read that Linux 4.x incorporates the feature to be
>>> updated without requiring a restart of the operating system.
>> Some Linux Distributions have such a feature. De
On Tue, Feb 14, 2017 at 01:46:08PM +0100, Sven Hartge wrote:
Daniel Bareiro wrote:
Some time ago I read that Linux 4.x incorporates the feature to be
updated without requiring a restart of the operating system.
Some Linux Distributions have such a feature. Debian is not one of them.
Actual
Daniel Bareiro wrote:
> Some time ago I read that Linux 4.x incorporates the feature to be
> updated without requiring a restart of the operating system.
Some Linux Distributions have such a feature. Debian is not one of them.
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
Hi all!
Some time ago I read that Linux 4.x incorporates the feature to be
updated without requiring a restart of the operating system.
Since stretch incorporates a kernel of the 4.x series, this would imply
that we can update the kernel package and avoid reboots?
Thanks in advance.
Kind regar
> Hi Bob,
> >
> > Any help is appreciated.
> >
> Try to downgrade initramfs-tools to version 0.116 or below.
> With version higher than 0.116 you might not be able decrypt a seperated
> /usr
> partition.
> Hope this helps.
> > Thanks,
> > Ben
> Good luck1
> Hans
According to /var/log/apt/history.
Hi Bob,
>
> Any help is appreciated.
>
Try to downgrade initramfs-tools to version 0.116 or below.
With version higher than 0.116 you might not be able decrypt a seperated /usr
partition.
Hope this helps.
> Thanks,
> Ben
Good luck1
Hans
I have been running Debian Jessie on my laptop for more than a year. The
laptop has a regular HDD as /dev/sda and a 32G SSD drive as /dev/sdb.
/dev/sda11 is LUKS1-encrypted as /dev/mapper/sda11-crypt. There are two LVM
VGs:
$ pvs
PV VGFmt Attr PSize PFree
/dev/ma
On 10/10/2015 09:33 PM, Piyavkin wrote:
Yeah, but if the issue becomes permanent in all the future versions
starting from 3.2.71-2? It's kind of scary.
Good news: After some time waiting, there came version 3.2.73-2 and I
tested it both with 686-rt and 486 flavors. Both work good. No proble
I can get around the mount problem by explicitly specifying the filesystem
type (e.g., mount -t ext2 /dev/vda1 somedir)--is that some limitation of
busybox mount?
I still don't know why the system is having trouble starting up.
The recent kernel update included a fix for a KVM vunerab
After the recent kernel updates one of my virtual machines won't start.
GRUB runs and messages indicate the kernel is loaded and the initial
ramdisk is loading. Then it says it can't find the root device (identified
by correct UUID, though it wouldn't be visible until the logical volumes
are activ
On 10/10/2015 09:33 PM, Piyavkin wrote:
Miroslav, by the way, what version of BIOS your laptop has?
Insyde F15
On 10.10.2015 22:06, Miroslav Skoric wrote:
On 10/09/2015 08:45 PM, Piyavkin wrote:
I have exactly the same issue with the same kernel-packages. See here:
https://lists.debian.org/debian-user/2015/10/msg00231.html
Yes, my symptom was identical to what you have described there.
Interestingl
On 10.10.2015 22:06, Miroslav Skoric wrote:
On 10/09/2015 08:45 PM, Piyavkin wrote:
I have exactly the same issue with the same kernel-packages. See here:
https://lists.debian.org/debian-user/2015/10/msg00231.html
Yes, my symptom was identical to what you have described there.
Interestingl
On 10/09/2015 08:45 PM, Piyavkin wrote:
I have exactly the same issue with the same kernel-packages. See here:
https://lists.debian.org/debian-user/2015/10/msg00231.html
Yes, my symptom was identical to what you have described there.
Interestingly you use GRUB and not LILO, but even your GR
On 10/09/2015 06:09 PM, Brad Rogers wrote:
If that's true, that's a *serious* bug. LILO (or Grub, come to that)
should never delete kernels. I know Grub doesn't but, as I said before,
I've not used LILO for some years. Even so, I'd be surprised if it could
actually _delete_ kernels like that
me 2.5
years ago, so I forgot the initial kernel setup.) Anyway, for a long
time now there have been only such two kernel options, so I could choose
in between them. As long as I remember, during every kernel update both
kernels were updated in the same time so I could test each one
instantly. I
Update:
I've reported the bug here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801467
#801467
See also discussion there (similar case and possible solutions):
https://lists.debian.org/debian-user/2015/10/msg00175.html
Best regards,
Dmitry Piyavkin
I've reported the bug here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801467
#801467
Thanks for help.
Best regards,
Dmitry Piyavkin
On 10/9/2015 9:09 AM, Brad Rogers wrote:
On Thu, 8 Oct 2015 23:09:36 +0200
Miroslav Skoric wrote:
Hello Miroslav,
In fact, (and in my case) LILO does delete old kernels during the
If that's true, that's a *serious* bug. LILO (or Grub, come to that)
should never delete kernels. I know Gru
On Fri, 09 Oct 2015 21:45:19 +0300
Piyavkin wrote:
> Hi there,
>
> I have exactly the same issue with the same kernel-packages. See here:
> https://lists.debian.org/debian-user/2015/10/msg00231.html
>
> I use Grub. But it hadn't saved old good kernel versions in the exactly
> same manner
> as
Hi there,
I have exactly the same issue with the same kernel-packages. See here:
https://lists.debian.org/debian-user/2015/10/msg00231.html
I use Grub. But it hadn't saved old good kernel versions in the exactly
same manner
as Miroslav's LILO does. I have no option «Advanced options for Debian
Hi there,
I'm using Debian 7 Wheezy for a long time. In 2015-10-07 I've applied
proposed upgrades:
libfreetype6:i386 2.4.9-1.1+deb7u1 2.4.9-1.1+deb7u2
linux-image-3.2.0-4-486:i386 3.2.68-1+deb7u4 3.2.71-2
linux-image-3.2.0-4-686-pae:i386 3.2.68-1+deb7u4 3.2.71-2
linux-headers-3.2.0-4-686-pae:i
On Thu, 8 Oct 2015 23:09:36 +0200
Miroslav Skoric wrote:
Hello Miroslav,
>In fact, (and in my case) LILO does delete old kernels during the
If that's true, that's a *serious* bug. LILO (or Grub, come to that)
should never delete kernels. I know Grub doesn't but, as I said before,
I've not us
On Thu, Oct 08, 2015 at 11:09:36PM +0200, Miroslav Skoric wrote:
> On 10/08/2015 12:37 AM, Brad Rogers wrote:
>
> >>Thanks. Well I do not have GRUB here but LILO, and there are no saved
> >>old kernels as long as I know.
> >
> >There should be; Debian doesn't delete old kernels as part of the
> >
> Furthermore, as mentioned in my other mail, I used to have 486 and
> 686-pae kernels, and was used to switch from one to another from time to
> time, to see the difference. In the past I noticed that 686-pae tend to
> make mouse cursor moving slowly for a while, then to recover as usual,
> th
On 10/08/2015 12:37 AM, Brad Rogers wrote:
Thanks. Well I do not have GRUB here but LILO, and there are no saved
old kernels as long as I know.
There should be; Debian doesn't delete old kernels as part of the
upgrade process. Even LILO should have an option to boot older
kernels. Older ker
On 10/08/2015 10:58 AM, Riley Baird wrote:
rescue CLI?
If dpkg is available during the rescue CLI, you can install the .deb file
using the command
$ dpkg -i /path/to/packagename.deb
Riley, that was the solution I looked for and dpkg did the job. I
reinstalled the previous kernel and remov
On Wed, 7 Oct 2015 23:23:54 +0200
Miroslav Skoric wrote:
> On 10/07/2015 08:56 AM, Riley Baird wrote:
>
> >> After the last kernel update and restart, a wheezy-based machine (laptop
> >> running 7.9) boots to some point, however it freezes just before opening
> >
On Wed, 7 Oct 2015 23:23:54 +0200
Miroslav Skoric wrote:
Hello Miroslav,
>Thanks. Well I do not have GRUB here but LILO, and there are no saved
>old kernels as long as I know.
There should be; Debian doesn't delete old kernels as part of the
upgrade process. Even LILO should have an option t
On 10/07/2015 08:56 AM, Riley Baird wrote:
After the last kernel update and restart, a wheezy-based machine (laptop
running 7.9) boots to some point, however it freezes just before opening
GUI. Access to CLI (Ctrl-Alt-F1 etc) is also not possible. What to do to
recover?
Debian saves your old
On Wed, 07 Oct 2015 06:44:37 +0200
Miroslav Skoric wrote:
> Hi,
>
> After the last kernel update and restart, a wheezy-based machine (laptop
> running 7.9) boots to some point, however it freezes just before opening
> GUI. Access to CLI (Ctrl-Alt-F1 etc) is also not possible
Hi,
After the last kernel update and restart, a wheezy-based machine (laptop
running 7.9) boots to some point, however it freezes just before opening
GUI. Access to CLI (Ctrl-Alt-F1 etc) is also not possible. What to do to
recover?
Regards,
M.
Quoting Louis Wust (louisw...@fastmail.fm):
> On Thu, Jul 16, 2015, at 13:19, Hans wrote:
> > "[***] An LSB job is running: Raise network interfaces"
>
> The "LSB job" portion means that the long-running service is a script in
> /etc/init.d. The "Raise network interfaces" description means that it
On Thu, Jul 16, 2015, at 13:19, Hans wrote:
> "[***] An LSB job is running: Raise network interfaces"
The "LSB job" portion means that the long-running service is a script in
/etc/init.d. The "Raise network interfaces" description means that it
must be /etc/init.d/networking because that script ha
Hey guys,
after the last kernel update (3.16 -> 4.0.0), I have the problem, that theg
boot hangs, when the network is started. With the former kernel the
delay was 1 - 2 seconds, now it is about 90 seconds and during this time I
get the message:
"[***] An LSB job is running: Raise
Here is the message:
make: *** No rule to make target `modules'. Stop.
Am 05.03.2014 11:53, schrieb ralf.mard...@alice-dsl.net:
> Please post the complete command and complete English messages you get.
>
> LANG=C command
> or
> LC_ALL=C command
> should cause English messages.
>
> Regards,
> R
Please post the complete command and complete English messages you get.
LANG=C command
or
LC_ALL=C command
should cause English messages.
Regards,
Ralf
--
My apologies if I should break threads.
I'm receiving emails with Evolution, use an editor to write mails and
temporarily sent mails using
Hi people!
I have updated the kernel, and removed the old one, sources,
kbuild,linux-header and modules from the old kernel.
I have installed the updated, kernel, modules,kbuild,headers with the
same version number from the current one.
Now I want to compile manually a module and I receive the er
On 05/03/14 21:14, Tamer Higazi wrote:
> Hi people!
>
> I have updated the kernel, and removed the old one, sources,
> kbuild,linux-header and modules from the old kernel.
> I have installed the updated, kernel, modules,kbuild,headers with the
> same version number from the current one.
>
> Now I
The latest kernel update seems to have fixed the panics and GPFs I was
experiencing.
I was experiencing nearly predictable crashes whenever RAM was filled with
cached disk blocks. At that point, it seemed that anything that addressed the
cache would cause a crash: use a program that needed RAM
Hello,
I'm running Debian Testing on a Thinkpad X60s. After my latest
kernel-update to linux-image-3.2.0-4-686-pae sound and trackpoint
stopped working. If I boot linux-image-2.6.32-5-686 it's working fine.
So here's what I figured out so far...
root@x60s:/home/iz
On Wed, 05 Sep 2012 12:15:28 +1200, Chris Bannister wrote:
> On Tue, Sep 04, 2012 at 04:11:04PM +, Camaleón wrote:
(...)
>> > You don't spell "Security support" as "p, a, t, c, h, e, s" more
>> > below.
>>
>> What the...? Patches encompass security fixes and more!
>
> yeah, but, security
On Tue, Sep 04, 2012 at 04:11:04PM +, Camaleón wrote:
> On Tue, 04 Sep 2012 23:34:43 +1200, Chris Bannister wrote:
>
> > On Mon, Sep 03, 2012 at 02:49:00PM +, Camaleón wrote:
> >> >> ¹http://lists.debian.org/debian-user/2012/08/msg01890.html
> >> >
> >> > No mention about security support
On Ma, 04 sep 12, 16:36:27, Camaleón wrote:
> On Tue, 04 Sep 2012 19:22:50 +0300, Andrei POPESCU wrote:
>
> > On Ma, 04 sep 12, 16:11:04, Camaleón wrote:
> >>
> >> 1/ Debian stable branches don't receive new kernel releases from the
> >> usual repositories but they can be obtained from backports.
On Tue, 04 Sep 2012 19:22:50 +0300, Andrei POPESCU wrote:
> On Ma, 04 sep 12, 16:11:04, Camaleón wrote:
>>
>> 1/ Debian stable branches don't receive new kernel releases from the
>> usual repositories but they can be obtained from backports.
>>
>> 2/ Debian stable branches do receive kernel upgr
On Ma, 04 sep 12, 16:11:04, Camaleón wrote:
>
> 1/ Debian stable branches don't receive new kernel releases from the
> usual repositories but they can be obtained from backports.
>
> 2/ Debian stable branches do receive kernel upgrades in form of security
> fixes and patches.
>
> 3/ That said,
On Tue, 04 Sep 2012 23:34:43 +1200, Chris Bannister wrote:
> On Mon, Sep 03, 2012 at 02:49:00PM +, Camaleón wrote:
>> >> ¹http://lists.debian.org/debian-user/2012/08/msg01890.html
>> >
>> > No mention about security support in that post either ..., or was it
>> > in another thread?
>>
>> Are
On Mon, Sep 03, 2012 at 02:49:00PM +, Camaleón wrote:
> >> ¹http://lists.debian.org/debian-user/2012/08/msg01890.html
> >
> > No mention about security support in that post either ..., or was it in
> > another thread?
>
> Are you wearing your glasses now?
Don't need them! You don't spell "S
On Lu, 03 sep 12, 17:02:59, Emiliano M. Rudenick wrote:
>
> contrib? non-free? I think that's not right :|
Why?
Kind regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
signature.asc
Description: Digit
El Mon, 3 Sep 2012 20:37:46 +1200
Chris Bannister escribió:
> On Wed, Aug 29, 2012 at 05:54:32PM +0300, Mika Suomalainen wrote:
> > On 29.08.2012 17:45, Lisi wrote:
> > > but I don't know what happened to Lenny backports when Lenny was
> > > archived.
> >
> > They were archived too.
> >
> > http
On Mon, 03 Sep 2012 20:58:17 +1200, Chris Bannister wrote:
> On Wed, Aug 29, 2012 at 05:24:53PM +, Camaleón wrote:
>> On Wed, 29 Aug 2012 18:08:58 +0100, Tony van der Hoff wrote:
>>
>> > On 29/08/12 17:28, Camaleón wrote:
>> >> It does not matter that Lenny is out of support (formerly codenam
On Monday 03 September 2012 10:03:12 Chris Bannister wrote:
> On Wed, Aug 29, 2012 at 06:49:31PM +0100, Lisi wrote:
> > On Wednesday 29 August 2012 18:08:58 Tony van der Hoff wrote:
> > > On 29/08/12 17:28, Camaleón wrote:
> > > > It does not matter that Lenny is out of support (formerly codenamed
On Wed, Aug 29, 2012 at 06:49:31PM +0100, Lisi wrote:
> On Wednesday 29 August 2012 18:08:58 Tony van der Hoff wrote:
> > On 29/08/12 17:28, Camaleón wrote:
> > > It does not matter that Lenny is out of support (formerly codenamed
> > > "oldstable") because even the current stable release (Squeeze)
On Wed, Aug 29, 2012 at 05:24:53PM +, Camaleón wrote:
> On Wed, 29 Aug 2012 18:08:58 +0100, Tony van der Hoff wrote:
>
> > On 29/08/12 17:28, Camaleón wrote:
> >> It does not matter that Lenny is out of support (formerly codenamed
> >> "oldstable") because even the current stable release (Sque
On Wed, Aug 29, 2012 at 05:54:32PM +0300, Mika Suomalainen wrote:
> On 29.08.2012 17:45, Lisi wrote:
> > but I don't know what happened to Lenny backports when Lenny was
> > archived.
>
> They were archived too.
>
> http://http.debian.net/debian-archive/debian-backports/
>
> has folder "dists",
On Wednesday 29 August 2012 18:08:58 Tony van der Hoff wrote:
> On 29/08/12 17:28, Camaleón wrote:
> > It does not matter that Lenny is out of support (formerly codenamed
> > "oldstable") because even the current stable release (Squeeze) neither
> > get kernel upgrades (for kernel upgrades I mean g
On Wed, 29 Aug 2012 18:08:58 +0100, Tony van der Hoff wrote:
> On 29/08/12 17:28, Camaleón wrote:
>> It does not matter that Lenny is out of support (formerly codenamed
>> "oldstable") because even the current stable release (Squeeze) neither
>> get kernel upgrades (for kernel upgrades I mean goin
On 29/08/12 17:28, Camaleón wrote:
> It does not matter that Lenny is out of support (formerly codenamed
> "oldstable") because even the current stable release (Squeeze) neither
> get kernel upgrades (for kernel upgrades I mean going from 2.6.26 to
> 2.6.32 or 3.x branch, for instance). Kernel u
On 08/29/2012 11:28 AM, Camaleón wrote:
On Wed, 29 Aug 2012 11:21:30 -0500, Conrad Nelson wrote:
(snip)
In the second link, someone told that the problem may solved in the
kernel 2.6.30.
I tried to upgrade to the latest kernel via:
deb http://ftp.de.debian.org/debian-archive/debian/ lenny ma
On Wed, 29 Aug 2012 11:21:30 -0500, Conrad Nelson wrote:
> (snip)
>>> In the second link, someone told that the problem may solved in the
>>> kernel 2.6.30.
>>>
>>> I tried to upgrade to the latest kernel via:
>>>
>>> deb http://ftp.de.debian.org/debian-archive/debian/ lenny main deb-src
>>> http:
(snip)
In the second link, someone told that the problem may solved in the
kernel 2.6.30.
I tried to upgrade to the latest kernel via:
deb http://ftp.de.debian.org/debian-archive/debian/ lenny main
deb-src http://ftp.de.debian.org/debian-archive/debian/ lenny main
and
aptitude update
aptitude
On Wed, 29 Aug 2012 14:33:49 +0200, Meike Stone wrote:
> I've running an Debian Lenny and can't upgrade to Squeeze for the moment
> because of special software ...
>
> Now the Server crashed two times.
> The error message is every time (taken from the console):
>
> "Filesystem "dm-2": XFS intern
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 29.08.2012 17:45, Lisi wrote:
> but I don't know what happened to Lenny backports when Lenny was
> archived.
They were archived too.
http://http.debian.net/debian-archive/debian-backports/
has folder "dists", which seems to contain lenny-backpo
On Wednesday 29 August 2012 13:33:49 Meike Stone wrote:
> Hello dear list,
>
> I've running an Debian Lenny and can't upgrade to Squeeze for the
> moment because of special software ...
>
> Now the Server crashed two times.
> The error message is every time (taken from the console):
>
> "Filesystem
On Wed, Aug 29, 2012 at 02:33:49PM +0200, Meike Stone wrote:
> Hello dear list,
>
> I've running an Debian Lenny and can't upgrade to Squeeze for the
> moment because of special software ...
>
[cut]
>
> The Server is going to migrate to new software (and Debian) in three
> month, but until then
Hello dear list,
I've running an Debian Lenny and can't upgrade to Squeeze for the
moment because of special software ...
Now the Server crashed two times.
The error message is every time (taken from the console):
"Filesystem "dm-2": XFS internal error xfs_trans_cancel at line 1163
of fs/xfs/xfs
El 2011-05-09 a las 09:30 -0400, Brad Alexander escribió:
(sorry Brad, I completely missed your e-mail)
> On Mon, May 9, 2011 at 7:59 AM, Camaleón wrote:
>
> > On Sun, 08 May 2011 14:29:12 -0500, Stan Hoeppner wrote:
(...)
> > > Last, why haven't you migrated that guest (and all such systems)
On Sun, 08 May 2011 14:29:12 -0500, Stan Hoeppner wrote:
> On 5/8/2011 7:44 AM, Camaleón wrote:
>> Yesterday I updated the kernel to 2.6.38-2 on wheezy and now I get (at
>> a random basis) a warning about the ReiserFS filesystem "is not clean"
>> when booting.
>>
>> Despite the boot message, ther
On 5/8/2011 7:44 AM, Camaleón wrote:
Hello,
Yesterday I updated the kernel to 2.6.38-2 on wheezy and now I get (at a
random basis) a warning about the ReiserFS filesystem "is not clean" when
booting.
Despite the boot message, there are no more indications of a filesystem
corruption and indeed,
Hello,
Yesterday I updated the kernel to 2.6.38-2 on wheezy and now I get (at a
random basis) a warning about the ReiserFS filesystem "is not clean" when
booting.
Despite the boot message, there are no more indications of a filesystem
corruption and indeed, the system has been always being shu
Hello!
I found out the kernel was too new for debian stable udev
system. Lenny's udev needs
CONFIG_DEPRECATED_SYSFS
CONFIG_DEPRECATED_SYSFS_V2
enabled and the most actual stable kernel package has this enabled
(2.6.26-2-686) so I could update, even completely remotely, to this
version. Sadly upd
Sorry, this is not a reply but in initial message to the list.
> Are you using the kernel to autodetect the LVM volumes (using type
0xfd). It
Well I use only the kernel modules (dm_mod) and let userspace do its
stuff,
mainly debian's /etc/init.d/lvm does the job well. It relies on pvscan
dete
On Monday 12 July 2010 17:53:56 Konstantin Kletschke wrote:
> Well the update itself did run very well, grub2 loads new kernel and
> ramdisk and iniiates to start userspace. There pvscan detects no
> physical volumes anymore all of a sudden. Booting the old kernel again
> runs well and the bos come
Hello,
I tried to do a Kernel update on an (mainly) lenny box after it had an
uptime of over 400 days. This means quite old Box with old kernel meets
bleeding edge modern stuff. Additionally I moved from lilo to grub2 (if
that is from concern).
Well the update itself did run very well, grub2
1 - 100 of 304 matches
Mail list logo
