Hi all,
After using the bullseye-backports kernel, my vps ran out of memory
after a period of time.

. After this
upgrade I needed to prepare an external HDD (WD Elements 2TB) for
encryption and so I used the "write zeroes to a plain crypto container"
approach:
# cryptsetup open --type plain -d /dev/urandom
On Lu, 23 sep 19, 07:23:05, Karolis Pabijanskas wrote:
> Hey Everyone!
>
> `stretch-backports` kernel seems to have broken dependencies since a
> few days ago. In particular this package:
> https://packages.debian.org/stretch-backports/linux-image-amd64 seems
> to have a bro
On 9/23/19, Karolis Pabijanskas wrote:
> Hey Everyone!
>
> `stretch-backports` kernel seems to have broken dependencies since a few
> days ago. In particular this package:
> https://packages.debian.org/stretch-backports/linux-image-amd64 seems to
> have a broken dependency for
Hey Everyone!
`stretch-backports` kernel seems to have broken dependencies since a few days
ago. In particular this package:
https://packages.debian.org/stretch-backports/linux-image-amd64 seems to have a
broken dependency for linux-image-4.19.0-0.bpo.6-amd64, which does not seem to
exist in
Hi Jens,
On Wed, Oct 17, 2018 at 01:41:56PM +0200, Jens Holzkämper wrote:
> We get the following results (with a variance within a few seconds)
>
> 4.9 ext4:
> real 2m13.303s
[…]
> 4.18 ext4:
> real 4m3.276s
Absent anyone being able to make a suggestion of exactly what broke
here, perhaps yo
Hi.
On Wed, Oct 17, 2018 at 04:44:25PM +0200, Support (Jens) wrote:
> Hi,
>
> >> we have a NAS system acting as a place to store our server's backups
> >> (via rsync with link-dest). On that NAS we switched from the stable
> >> kernel (4.9) to the one provided by backports (4.18) because
Hi,
>> we have a NAS system acting as a place to store our server's backups
>> (via rsync with link-dest). On that NAS we switched from the stable
>> kernel (4.9) to the one provided by backports (4.18) because of an
>> unrelated problem. When we do that, we see a slowdown of our backup
>> process
Hi.
On Wed, Oct 17, 2018 at 01:41:56PM +0200, Jens Holzkämper wrote:
> Hi,
>
> we have a NAS system acting as a place to store our server's backups
> (via rsync with link-dest). On that NAS we switched from the stable
> kernel (4.9) to the one provided by backports (4.18) because of an
>
Hi,
we have a NAS system acting as a place to store our server's backups
(via rsync with link-dest). On that NAS we switched from the stable
kernel (4.9) to the one provided by backports (4.18) because of an
unrelated problem. When we do that, we see a slowdown of our backup
process, from the back
Hi -
Am using debian9, just upgraded my system to a gigabyte Z370 + intel
core-i7-8700k, bootup is EFI.
System works fine, but bootup is really slowed down because of the
following ACPI errors.
In digging around, looks like the issue is gigabyte needs to fix their
bios, have put in a support req
On 12/28/2014 05:03 AM, Andrei POPESCU wrote:
On Du, 28 dec 14, 15:02:02, Andrei POPESCU wrote:
You would need the package linux-headers-3.16-0.bpo.2-amd64, however,
backports is currently at 3.16.0-0.bpo.4-amd64 so you should probably
install linux-image-3.16.0-0.bpo.4-amd64 and
linux-headers-3
On Du, 28 dec 14, 15:02:02, Andrei POPESCU wrote:
>
> You would need the package linux-headers-3.16-0.bpo.2-amd64, however,
> backports is currently at 3.16.0-0.bpo.4-amd64 so you should probably
> install linux-image-3.16.0-0.bpo.4-amd64 and
> linux-headers-3.16.0-0.bpo.4-amd64, reboot, and th
On Sb, 27 dec 14, 21:27:40, Marc Shapiro wrote:
> dpkg: warning: unable to delete old directory
> '/usr/src/virtualbox-4.1.18/vboxdrv': Directory not empty
> dpkg: warning: unable to delete old directory '/usr/src/virtualbox-4.1.18':
> Directory not empty
You might want to clean this up.
> Buildi
On Sb, 27 dec 14, 20:29:38, Marc Shapiro wrote:
> I am trying to test ReactOS in Virtualbox. When I fired up virtualbox I
> received errors saying:
> -
>
> One or more virtual hard disks, CD/DVD or floppy media are not currently
> accessible. As a result, you will not be able
rience dkms for VirtualBox has never worked in Wheezy. I
have to
manually compile the module every time I upgrade the kernel.
According to the Debian Wiki, you have to install VirtualBox from
backports
if you use a backports kernel:
https://wiki.debian.org/VirtualBox#Debian_7_.22Wheezy.22_Backports
H
ever worked in Wheezy. I
have to
manually compile the module every time I upgrade the kernel.
According to the Debian Wiki, you have to install VirtualBox from
backports
if you use a backports kernel:
https://wiki.debian.org/VirtualBox#Debian_7_.22Wheezy.22_Backports
Hmmm ... that's t
e I missed a step somewhere in installing virtualbox? How do
> I get vboxdrv installed?
What version of virtualbox does the above represent?
In my experience dkms for VirtualBox has never worked in Wheezy. I have to
manually compile the module every time I upgrade the kernel.
Accordi
I am trying to test ReactOS in Virtualbox. When I fired up virtualbox I
received errors saying:
-
One or more virtual hard disks, CD/DVD or floppy media are not currently
accessible. As a result, you will not be able to operate virtual
machines that use these media until t
Gary Dale writes:
> On 25/11/14 02:14 PM, lee wrote:
>> Hi,
>>
>> what could be the problem with the backport kernels? They never finish
>> booting when the root fs is on an LVM volume.
>>
>> Do I need to take special precautions with the backports
On 25/11/14 02:14 PM, lee wrote:
Hi,
what could be the problem with the backport kernels? They never finish
booting when the root fs is on an LVM volume.
Do I need to take special precautions with the backports kernel to get
it to boot? I have a separate /boot partition not on LVM and a
Hi,
what could be the problem with the backport kernels? They never finish
booting when the root fs is on an LVM volume.
Do I need to take special precautions with the backports kernel to get
it to boot? I have a separate /boot partition not on LVM and a biosgrub
partition with the root fs on
Hi.
On Mon, 03 Nov 2014 19:34:05 +0100
Dennis Birkholz wrote:
> My /etc/fstab-file does not contain an entry for /sys at all.
>
> Mounts says:
> sysfs on /sys type sysfs (ro,nosuid,nodev,noexec,relatime)
>
> If I unmount /sys and mount it new with:
> mount -t sysfs -o rw,relatime,noexec,nodev
My /etc/fstab-file does not contain an entry for /sys at all.
Mounts says:
sysfs on /sys type sysfs (ro,nosuid,nodev,noexec,relatime)
If I unmount /sys and mount it new with:
mount -t sysfs -o rw,relatime,noexec,nodev,nosuid sysfs /sys/
I get:
mount: warning: /sys/ seems to be mounted read-only.
Hi.
On Sun, 02 Nov 2014 19:13:50 +0100
Dennis Birkholz wrote:
> Hi together,
>
> I switched from the Wheezy stable kernel to the latest kernel in
> backports (3.16.3-2~bpo70+1).
> Now I can not write-mount /sys any more, thus I can not trigger RAID
> check actions, etc.
>
> I tried remounting
Hi together,
I switched from the Wheezy stable kernel to the latest kernel in
backports (3.16.3-2~bpo70+1).
Now I can not write-mount /sys any more, thus I can not trigger RAID
check actions, etc.
I tried remounting it (mount -o remount -w /sys), but I can not get it
to be writable. Is this inten
On Sun, 29 Jan 2012 11:58:22 +0200, Andrei Popescu wrote:
> On Du, 29 ian 12, 09:37:36, Ramon Hofer wrote:
>> >
>> > Hmm, you must be running amd64, 3.1.0 is not available on i386. But
>> > anyway, if I understand correctly, it's too much effort to support
>> > more than one kernel version in bac
On Du, 29 ian 12, 09:37:36, Ramon Hofer wrote:
> >
> > Hmm, you must be running amd64, 3.1.0 is not available on i386. But
> > anyway, if I understand correctly, it's too much effort to support more
> > than one kernel version in backports, so it is likely to disappear soon.
> >
> > For nvidia-gl
On Sun, 29 Jan 2012 01:28:19 +0200, Andrei Popescu wrote:
> On Sb, 28 ian 12, 10:20:58, Ramon Hofer wrote:
>>
>> If I get you right I should install linux-image-3.2.0-0.bpo.1-amd64?
>> But there are other packages too like linux-image-amd64 which installs
>> the extra package linux-image-3.1.0-0.
On Sat, 28 Jan 2012 22:16:04 +0100, didier gaumet wrote:
> Le Sat, 28 Jan 2012 10:20:58 + (UTC), Ramon Hofer
> a écrit :
>
> [...]
>> I have added "deb http://backports.debian.org/debian-backports squeeze-
>> backports main" to my /etc/apt/sources.list
>
> "deb http://backports.debian.org/d
On Sb, 28 ian 12, 10:20:58, Ramon Hofer wrote:
>
> If I get you right I should install linux-image-3.2.0-0.bpo.1-amd64?
> But there are other packages too like linux-image-amd64 which installs
> the extra package linux-image-3.1.0-0.bpo.1-amd64. Here are all the
> possibilies I have:
Hmm, you m
Le Sat, 28 Jan 2012 10:20:58 + (UTC),
Ramon Hofer a écrit :
[...]
> I have added "deb http://backports.debian.org/debian-backports
> squeeze- backports main" to my /etc/apt/sources.list
"deb http://backports.debian.org/debian-backports squeeze- backports
main non-free" would be better
[...]
On Fri, 27 Jan 2012 23:00:49 +0200, Andrei Popescu wrote:
> On Vi, 27 ian 12, 20:39:06, Ramon Hofer wrote:
>>
>> The linux-image-amd64 package from squeeze backports installs linux-
>> image-3.1.0-0.bpo.1-amd64.
>> Is 2.6.29 the better choice than 3.1?
>
> I don't know, I can only tell you that
On Fri, 27 Jan 2012 23:14:43 +0200, Andrei Popescu wrote:
> On Vi, 27 ian 12, 23:00:49, Andrei Popescu wrote:
>>
>> I don't know, I can only tell you that 2.6.29 from squeeze-backports
>> doesn't work with nvidia-glx from squeeze, you need both from
>> backports, but in the meantime 2.6.29 got re
On Vi, 27 ian 12, 23:00:49, Andrei Popescu wrote:
>
> I don't know, I can only tell you that 2.6.29 from squeeze-backports
> doesn't work with nvidia-glx from squeeze, you need both from backports,
> but in the meantime 2.6.29 got replaced with 3.2 I didn't get the chance
> to test it (3.1 is n
On Vi, 27 ian 12, 20:39:06, Ramon Hofer wrote:
>
> The linux-image-amd64 package from squeeze backports installs linux-
> image-3.1.0-0.bpo.1-amd64.
> Is 2.6.29 the better choice than 3.1?
I don't know, I can only tell you that 2.6.29 from squeeze-backports
doesn't work with nvidia-glx from sque
On Fri, 27 Jan 2012 20:50:25 +0200, Andrei Popescu wrote:
> On Vi, 27 ian 12, 15:21:47, Ramon Hofer wrote:
>> Hi all
>>
>> I have some problems with the ir-remote of my htpc. That's why I want
>> to install a newer kernel.
>>
>> Can I install the linu
On Vi, 27 ian 12, 15:21:47, Ramon Hofer wrote:
> Hi all
>
> I have some problems with the ir-remote of my htpc.
> That's why I want to install a newer kernel.
>
> Can I install the linux-image-amd64 package from squeeze-backports kernel
> without changing nvidi
Hi all
I have some problems with the ir-remote of my htpc.
That's why I want to install a newer kernel.
Can I install the linux-image-amd64 package from squeeze-backports kernel
without changing nvidia-glx (version 195.36.31-6)?
Or will I have to compile the nvidia driver?
Best regards
obviously refusing to start.
On the plus side, I did get the Backports kernel and the proprietary
drivers running. Would still like to look at the Nouveau drivers though.
--
Ashton Fagg (ash...@fagg.id.au)
Web: http://www.fagg.id.au/~ashton/
Keep calm and call Batman.
--
To UNSUBSCRIBE, email to d
On Tue, Dec 27, 2011 at 06:50:42PM +1000, Ashton Fagg wrote:
> I've spent a few hours this afternoon mucking about with Nouveau
> trying to get it working (temporarily at least, just to check). I've
> had limited success in some areas and absolutely none in others.
>
> I firstly checked to make su
Hi Rob. Thanks for your reply.
On 26/12/11 23:59, Rob Owens wrote:
I believe that is true.
I've been experimenting with trying to work out how this all works, and
I've come across this for sticking with the proprietary nVidia drivers
(more on that in a moment).
http://www.vultaire.net/blog
On Mon, Dec 26, 2011 at 12:20:36PM +1000, Ashton Fagg wrote:
> Hi all,
>
> I have a Dell Latitude E6410 with nVidia graphics, and I would like
> to upgrade to a backports kernel. I currently run the proprietary
> nVidia drivers on the stock Squeeze kernel, because they seem to
>
Hi all,
I have a Dell Latitude E6410 with nVidia graphics, and I would like to
upgrade to a backports kernel. I currently run the proprietary nVidia
drivers on the stock Squeeze kernel, because they seem to "just work".
It's my understanding that I will not be able to ins
Proskurin Kirill wrote:
One question:
It is safe to use backported kernel in production?
Officially, it is not, but the backporters community is supportive enough.
You should probably check this[1] out first, however.
1: http://www.linuxfoundation.org/collaborate/workgroups/driver-backport
On Tue June 1 2010 12:20:43 pm Proskurin Kirill wrote:
> Hello.
>
> One question:
> It is safe to use backported kernel in production?
>
> I seems to need to use 2.6.30+ kernel to have a fix in OCFS2.
I use the kernel from backports for ext4 support on one of my boxes, never had
a problem with it
Hello.
One question:
It is safe to use backported kernel in production?
I seems to need to use 2.6.30+ kernel to have a fix in OCFS2.
--
Best regards,
Proskurin Kirill
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas..
On Wed, Jun 21, 2006 at 06:19:59PM -0700, Jeff Jones wrote:
> Dears,
>
> I'm completely newbie to backports.org kernel image and I have some difficult
> using it with m-a.
>
> I've successfully installed linux-image-686 from backports (doing apt pinning)
> which could point to the latest availabl
Dears,I'm completely newbie to backports.org kernel image and I have some difficult using it with m-a. I've successfully installed linux-image-686 from backports (doing apt pinning) which could point to the latest available kernel image.Now I'd need to use module assistant to compile the nvidia mod
52 matches
Mail list logo