Thanks Tom. Editing wifi_regd.c seems pretty promising. I'll try that.
-Mike
On 2023-09-14 02:21, Tom Dial wrote:
On 9/13/23 17:07, M. Cuffaro wrote:
Hello all,
I have looked around for an answer but was unable to find one, and
was hoping that someone here could help me. *First, some back
Hi Marco,
thanks for the helpful reply. I'll consider this but as a last resort.
Best,
-Mike
On 2023-09-14 00:39, Marco wrote:
Am 13.09.2023 19:07 schrieb M. Cuffaro:
Consult /var/lib/dkms/rtl88x2bu/5.13.1/build/make.log for more
information.
That drivers is incompatible with the current k
On 9/13/23 17:07, M. Cuffaro wrote:
Hello all,
I have looked around for an answer but was unable to find one, and was hoping
that someone here could help me. *First, some background to my information
about my question*. I recently ran
apt full-upgrade
on my Debian bookworm system. Because
Am 13.09.2023 19:07 schrieb M. Cuffaro:
> Consult /var/lib/dkms/rtl88x2bu/5.13.1/build/make.log for more
> information.
That drivers is incompatible with the current kernel.
How did you install it?
Uninstall it, then run the kernel update again.
Run
dkms status
And try
sudo dkms remove rtl88x2bu
Hello all,
I have looked around for an answer but was unable to find one, and was
hoping that someone here could help me. *First, some background to my
information about my question*. I recently ran
apt full-upgrade
on my Debian bookworm system. Because of what seems like a bug in dkms,
the
Hi List,
I upgraded my Kernel and now after restarting my computer I have to go
into /proc/sys/user/max_*_namespaces and modify the value to something
other than 0 (zero). Where do I file a bug?
I'm on Debian Stable with Kernel version 6.1.0-11-amd64 if it helps
any.
Thanks!
--
Tim McConnell
note: DO NOT DO THIS ON A PRODUCTION SYSTEM.
last week i was running an unsigned kernel and went to upgrade it
to a signed version and it came back with asking me about removing
a running kernel. in recent times that hasn't been and issue so i
aborted the install and then downloaded the desi
On Du, 02 ian 22, 20:59:45, David Wright wrote:
> On Sat 18 Dec 2021 at 12:36:49 (+0100), Andrei POPESCU wrote:
> > On Jo, 16 dec 21, 09:53:33, David Wright wrote:
> > >
> > > Anyone think it ironic that a multinational IT company with a
> > > market capitalisation of $50 billion as of September 2
On Sat 18 Dec 2021 at 12:36:49 (+0100), Andrei POPESCU wrote:
> On Jo, 16 dec 21, 09:53:33, David Wright wrote:
> >
> > Anyone think it ironic that a multinational IT company with a
> > market capitalisation of $50 billion as of September 2021 comes
> > here for help on upgrading the kernel on an
On Sat, Dec 18, 2021, 04:37 Andrei POPESCU wrote:
> Free(dom) Software was never meant to exclude comercial use or
> developers earning a living (or a fortune) from it.
>
>
> Agreed,.Andrei!
>
>
On Jo, 16 dec 21, 09:53:33, David Wright wrote:
>
> Anyone think it ironic that a multinational IT company with a
> market capitalisation of $50 billion as of September 2021 comes
> here for help on upgrading the kernel on an old Debian system?
Many questions on this list originate from businesse
On Jo, 16 dec 21, 16:12:37, to...@tuxteam.de wrote:
> On Thu, Dec 16, 2021 at 12:28:17PM +, Balasubramanian Ravuthan wrote:
> > Hi Team,
> >
> > We are looking support from you on the Linux Kernel upgrade on Debian
> > 10. Please help on this.
>
> Thi
rise from
such a individual kernel upgrade.
Better first try with the source packages from backports.
> 3. In order to upgrade Linux Kernel to 5.10 means we have to install Debian
> 11 BullsEye. Please Confirm.
See 1.
> 5. What will be the impact for upgrading Debian 10 with Kernel
-user@lists.debian.org
Subject: Re: Need Support on Debian10 Linux Kernel Upgrade
[CAUTION: This Email is from outside the Organization. Unless you trust the
sender, Don’t click links or open attachments as it may be a Phishing email,
which can steal your Information and compromise your Computer
On 12/16/21, David Wright wrote:
> On Thu 16 Dec 2021 at 16:12:37 (+0100), to...@tuxteam.de wrote:
>> On Thu, Dec 16, 2021 at 12:28:17PM +, Balasubramanian Ravuthan wrote:
>> > Hi Team,
>> >
>> > We are looking support from you on the Linux Kernel upgrad
Balasubramanian Ravuthan wrote:
>
> We are looking support from you on the Linux Kernel upgrade on Debian 10.
>
> We are currently using Debian10 Buster Linux Kernel 4.19 version and trying
> to upgrade to Debian10 Buster Linux Kernel 5.10 version. Is there any impact
>
On Thu 16 Dec 2021 at 16:12:37 (+0100), to...@tuxteam.de wrote:
> On Thu, Dec 16, 2021 at 12:28:17PM +, Balasubramanian Ravuthan wrote:
> > Hi Team,
> >
> > We are looking support from you on the Linux Kernel upgrade on Debian
> > 10. Please help on this.
>
On 2021-12-16 16:04 UTC+0100, Balasubramanian Ravuthan wrote:
> We are looking support from you on the Linux Kernel upgrade on Debian 10.
>
> We are currently using Debian10 Buster Linux Kernel 4.19 version and
> trying to upgrade to Debian10 Buster Linux Kernel 5.10 version. Is
Hi Debian Team,
We are looking support from you on the Linux Kernel upgrade on Debian 10.
We are currently using Debian10 Buster Linux Kernel 4.19 version and trying to
upgrade to Debian10 Buster Linux Kernel 5.10 version. Is there any impact on
this upgrading.
In other words, what are
On Thu, Dec 16, 2021 at 12:28:17PM +, Balasubramanian Ravuthan wrote:
> Hi Team,
>
> We are looking support from you on the Linux Kernel upgrade on Debian 10.
> Please help on this.
This is a user's list, not a support channel.
If you have concrete questions, you c
Balasubramanian Ravuthan wrote:
> Hi Debian Team,
>
> We are looking support from you on the Linux Kernel upgrade on Debian 10.
> Please help on this.
>
sudo apt update && sudo apt upgrade
Consider a dist-upgrade to Debian 11.
-dsr-
On 2021-12-16 13:28 UTC+0100, Balasubramanian Ravuthan wrote:
> Hi Team,
>
> We are looking support from you on the Linux Kernel upgrade on Debian
> 10. Please help on this.
There is no "Team" who will support you, we are all users who support
each other. Pai
Hi Team,
We are looking support from you on the Linux Kernel upgrade on Debian 10.
Please help on this.
Regards,
Bala
::DISCLAIMER::
The contents of this e-mail and any attachment(s) are confidential and intended
for the named recipient(s) only. E-mail
Hi Debian Team,
We are looking support from you on the Linux Kernel upgrade on Debian 10.
Please help on this.
Regards,
Bala
::DISCLAIMER::
The contents of this e-mail and any attachment(s) are confidential and intended
for the named recipient(s) only. E
Total story not understood but it seems as if apt had got the new kernel
package before the notification if the security issues. It just needed
a reboot. I suppose I must have assumed it was a new issue
Thank you for the support which eventually led me to the solution.
==John ffitch
On Lu, 12 aug 19, 08:49:34, Jude DaShiell wrote:
> The other tip about kernel install selection is to install something
> like kernel-i386 or kernel-x86 without all of the long version numbers
> as suffixes in their names.
This is a good idea in general. For the amd64 architecture the package
nam
the choices. I expect one way or the other you have this
covered correctly, so it could be something between you and debian pool
is misconfigured.
On Mon, 12 Aug 2019, john wrote:
> Date: Mon, 12 Aug 2019 08:23:59
> From: john
> To: debian-user@lists.debian.org
> Subject: Re: Ke
@lists.debian.org
Subject: Re: Kernel upgrade ?
Resent-Date: Mon, 12 Aug 2019 11:13:13 + (UTC)
Resent-From: debian-user@lists.debian.org
No I did not; I checked that again kjust niw but sill no upgrade.
On Mon, 12 Aug 2019, Holger Skidzun wrote:
> Did you by chance forgot apt-get update?
>
&g
You have updated /etc/apt-get/sources.list and replaced testing with
buster in all locations too and this failure continues?
On Mon, 12 Aug 2019, john wrote:
Date: Mon, 12 Aug 2019 07:12:39
From: john
To: Holger Skidzun
Cc: debian-user@lists.debian.org
Subject: Re: Kernel upgrade ?
Resent
No I did not; I checked that again kjust niw but sill no upgrade.
On Mon, 12 Aug 2019, Holger Skidzun wrote:
Did you by chance forgot apt-get update?
Cheers, Holger
Mit freundlichem Gruß!
Le 12 août 2019 à 12:35, John a écrit :
I received a notification from the Debian security list sayin
Did you by chance forgot apt-get update?
Cheers, Holger
Mit freundlichem Gruß!
> Le 12 août 2019 à 12:35, John a écrit :
>
> I received a notification from the Debian security list saying that
> there were a number of fixes to the kernel and saying I should update
> my buster system; "For the
On Mon, Aug 12, 2019 at 11:35:34AM +0100, John wrote:
> I received a notification from the Debian security list saying that
> there were a number of fixes to the kernel and saying I should update
> my buster system; "For the stable distribution (buster), these
> problems have been fixed in version
I received a notification from the Debian security list saying that
there were a number of fixes to the kernel and saying I should update
my buster system; "For the stable distribution (buster), these
problems have been fixed in version 4.19.37-5+deb10u2."
However apt does not seem to know about t
On Thu, 05 Jul 2018 20:02:15 +0200
Guillaume Clercin wrote:
Hello Guillaume,
>I upgrade nvidia-driver to version 390.67-2 and I can boot without
>option "slab_common.usercopy_fallback".
Thanks for all your input on this, Guillaume. If you hadn't pointed out
the workaround, I'd have been well a
Le jeudi 5 juillet 2018, 08:25:15 CEST Ric Moore a écrit :
> On 07/04/2018 09:12 PM, Carl Fink wrote:
> > On 07/02/2018 04:49 AM, Guillaume Clercin wrote:
> >> You need to update "/etc/default/grub" and add parameter to boot with.
> >> In this
> >> file, you need to edit the line starting with GRUB
On 07/04/2018 09:12 PM, Carl Fink wrote:
On 07/02/2018 04:49 AM, Guillaume Clercin wrote:
You need to update "/etc/default/grub" and add parameter to boot with.
In this
file, you need to edit the line starting with GRUB_CMDLINE_LINUX and
append
option: "slab_common.usercopy_fallback=y". This wo
On 07/02/2018 04:49 AM, Guillaume Clercin wrote:
You need to update "/etc/default/grub" and add parameter to boot with. In this
file, you need to edit the line starting with GRUB_CMDLINE_LINUX and append
option: "slab_common.usercopy_fallback=y". This workaround was suggested by
nvidia maintainer
On Sun, 1 Jul 2018 19:06:10 -0400
Carl Fink wrote:
Hello Carl,
>Thoughts?
Apply the fix reported by Guillaume. I can confirm it works.
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
No, he's just a w*
You Married A Tort
Le lundi 2 juillet 2018, 01:06:10 CEST Carl Fink a écrit :
> So, on a Testing system, linux-image-4.16.0-2-amd64 came up in the apt
>
> queue. I installed it and rebooted.
> My system froze on reboot. Scrolled through the boot messages on the
> console, up to X starting, then this (warning, long e
On Sun, 1 Jul 2018 19:06:10 -0400
Carl Fink wrote:
Hello Carl,
>Multiple reboots give the same behavior, never
>giving me either a console or X prompt.
Same here. Discovered by my wife when she turned the computer on this
morning. I haven't removed .0.2, simply manually selected the .0.1
kern
So, on a Testing system, linux-image-4.16.0-2-amd64 came up in the apt
queue. I installed it and rebooted.
My system froze on reboot. Scrolled through the boot messages on the
console, up to X starting, then this (warning, long excerpt from syslog):
Jul 1 18:50:08 debian-nitpicking kernel: [ 6.86
Le 11/07/2016 à 08:21, Miroslav Zaťko a écrit :
Same error here. First boot after fresh installation of Debian 8.5.0
from netinst CD finished with:
-BEGIN
error: invalid arch-independent ELF magic.
Entering rescue mode...
grub rescue>
-
Same error here. First boot after fresh installation of Debian 8.5.0
from netinst CD finished with:
-BEGIN
error: invalid arch-independent ELF magic.
Entering rescue mode...
grub rescue>
---EN
Greetings everyone,
today I ran into a weird problem I can't get my head around.
I run a debian 8 jessie server which was last updated around 4 weeks
ago. I did an apt-get update/upgrade today which only involved
around 20 packages, one of which was an update to the
linux-image-3.16.0-4-amd64 pac
On Mi, 13 aug 14, 17:13:24, pe...@easthope.ca wrote:
> * From: Andrei POPESCU
> * Date: Wed, 13 Aug 2014 08:32:32 +0300
> > ... complete output from running apt-get ...
>
> root@armada:/home/peter# apt-get install linux-image-2.6-686-pae
...
> root@armada:/home/peter# apt-get install lin
have to do with the TP-Link in the subject?
The driver for the Atheros AR9170 chipset in the TP-Link isn't working
with the 2.6.32 kernel; upgrade seemed a reasonable approach. For the
subject, my train of thought went off the rails.
Thanks,... Peter
--
On 7/6/14, Weydson Lima wrote:
> On 7/5/14, B wrote:
>> Try to add a file in /etc/modprobe.d (eg: NAUGHTY_INTEL_SND.conf)
>> with a line in: options snd-hda-intel index=-2 (or whatever name
>> is your module's name, YMMV) and reboot.
>
>
> What should the file name be? These are the files I h
What should the file name be? These are the files I have under modprobe.d:
alsa-base-blacklist.conf
alsa-base.conf
dkms.conf
fbdev-blacklist.conf
fglrx-blacklists-radeon.conf
radeon-kms.conf
I checked the alsa-base.conf and it had those lines:
options bt87x index=-2
options cx88_alsa index=-2
op
On Sat, 5 Jul 2014 21:19:39 -0600
Weydson Lima wrote:
> I have just upgraded the kernel on my Debian box from 3.2 to 3.14
> for the first time and I have no sound on X anymore. How can I
> troubleshoot this issue?
>
> I do see the snd_hda_intel module being loaded, but I don't know
> what else I
I have just upgraded the kernel on my Debian box from 3.2 to 3.14 for the
first time and I have no sound on X anymore. How can I troubleshoot this
issue?
I do see the snd_hda_intel module being loaded, but I don't know what else
I can do to solve this.
Thank you
On Tue, Apr 01, 2014 at 11:38:54AM +0100, Brad Rogers wrote:
> On Mon, 31 Mar 2014 18:51:59 -0400
> Stephen Allen wrote:
>
> Hello Stephen,
>
> >better although slower. At one time it was the go to, but since I've
> >gathered that apt-get has been improved.
>
> Also, IIRC, mixing aptitude, apt-
On Mon, 31 Mar 2014 18:51:59 -0400
Stephen Allen wrote:
Hello Stephen,
>better although slower. At one time it was the go to, but since I've
>gathered that apt-get has been improved.
Also, IIRC, mixing aptitude, apt-get & Synaptic for upgrades and
package installation, was considered a bad idea
On Mon, Mar 31, 2014 at 09:37:28PM +0200, Nemeth Gyorgy wrote:
> 2014-03-31 20:07 keltezéssel, Brad Rogers írta:
> > For my set of circumstances, it is. However, I neglected to take proper
> > note of yours. You're using apt-get (etc.) and I tend to use Synaptic.
> > Clearly, behaviour is differe
On Mon, Mar 31, 2014 at 07:46:15PM +0200, Nemeth Gyorgy wrote:
> 2014-03-30 14:59 keltezéssel, Stephen Allen írta:
>
> >> Are you sure?
> >> When the kernel version number changes, the
> >> linux-image--amd64.deb will be a new package.
> >>
> >> Plain apt-get upgrade upgrades the installed package
2014-03-31 20:07 keltezéssel, Brad Rogers írta:
> For my set of circumstances, it is. However, I neglected to take proper
> note of yours. You're using apt-get (etc.) and I tend to use Synaptic.
> Clearly, behaviour is different in each case.
>
> Mea Culpa.
>
> With the meta-package installed o
On Mon, 31 Mar 2014 19:46:15 +0200
Nemeth Gyorgy wrote:
Hello Nemeth,
>... was not correct... :)
For my set of circumstances, it is. However, I neglected to take proper
note of yours. You're using apt-get (etc.) and I tend to use Synaptic.
Clearly, behaviour is different in each case.
Mea Cu
2014-03-30 14:59 keltezéssel, Stephen Allen írta:
>> Are you sure?
>> When the kernel version number changes, the
>> linux-image--amd64.deb will be a new package.
>>
>> Plain apt-get upgrade upgrades the installed packages only and does not
>> install new package. But in this case the linux-image-
On Du, 30 mar 14, 10:57:37, Brad Rogers wrote:
> On Sun, 30 Mar 2014 10:42:52 +0200
> Nemeth Gyorgy wrote:
>
> Hello Nemeth,
>
> >Are you sure?
> >When the kernel version number changes, the
> >linux-image--amd64.deb will be a new package.
>
> Yes. Stephen said "..assuming of course the meta p
On Sun, Mar 30, 2014 at 10:42:52AM +0200, Nemeth Gyorgy wrote:
> 2014-03-29 22:29 keltezéssel, Stephen Allen írta:
> >> Do you have linux-image-amd64 installed? If not, install it. It always
> >> depends on the latest kernel so if there is a newer kernel, it will be
> >> installed automatically (if
On Sun, 30 Mar 2014 10:42:52 +0200
Nemeth Gyorgy wrote:
Hello Nemeth,
>Are you sure?
>When the kernel version number changes, the
>linux-image--amd64.deb will be a new package.
Yes. Stephen said "..assuming of course the meta package is
installed." He didn't write that without reason.
--
R
2014-03-29 22:29 keltezéssel, Stephen Allen írta:
>> Do you have linux-image-amd64 installed? If not, install it. It always
>> depends on the latest kernel so if there is a newer kernel, it will be
>> installed automatically (if you do dist-upgrade).
>>
>
> Actually a 'dist-upgrade' isn't necessar
On Sun, 2014-03-30 at 16:35 +1300, Chris Bannister wrote:
> > >Do I have to upgrade to 3.13-1-amd64?
>
> Absolutely not! If your machine is working perfectly, why risk it?
Good point :D!
OT: We sometimes take a look to our crystal balls and we are unhappy,
when e.g. the RT patched kernels > 3.8
On Sat, Mar 29, 2014 at 02:05:57PM +, Brad Rogers wrote:
> On Sat, 29 Mar 2014 14:31:03 +0100
> François Patte wrote:
>
> Hello François,
>
> >Since I installed debian sid (august 2013), I regularly made upgrade,
> >but the kernel doesn't appear to be upgraded. Why? I am running
>
> Unless
On Sat, Mar 29, 2014 at 04:50:50PM +0100, Nemeth Gyorgy wrote:
> 2014-03-29 14:31 keltezéssel, François Patte írta:
>
> > Since I installed debian sid (august 2013), I regularly made upgrade,
> > but the kernel doesn't appear to be upgraded. Why? I am running
> > 3.2.0-4-amd64 kernel.
> >
> > Do
2014-03-29 14:31 keltezéssel, François Patte írta:
> Since I installed debian sid (august 2013), I regularly made upgrade,
> but the kernel doesn't appear to be upgraded. Why? I am running
> 3.2.0-4-amd64 kernel.
>
> Do I have to upgrade to 3.13-1-amd64? If yes how to proceed?
>
Do you have lin
On Sat, 2014-03-29 at 14:05 +, Brad Rogers wrote:
> Either install the latest kernel manually or, if you prefer to have
> kernels handled by your usual update routine, install
> linux-image-amd64, which depends on the latest kernel version.
IOW a meta package does handle upgrades. But as Brad
ng the upgrade process. This
is intentional. Once you're happy with the new kernel upgrade, you can
manually remove the old one.
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
Bet you think you're king but you&
On Sat, 2014-03-29 at 14:31 +0100, François Patte wrote:
> Bonjour,
>
>
> Since I installed debian sid (august 2013), I regularly made upgrade,
> but the kernel doesn't appear to be upgraded. Why? I am running
> 3.2.0-4-amd64 kernel.
>
> Do I have to upgrade to 3.13-1-amd64? If yes how to procee
Bonjour,
Since I installed debian sid (august 2013), I regularly made upgrade,
but the kernel doesn't appear to be upgraded. Why? I am running
3.2.0-4-amd64 kernel.
Do I have to upgrade to 3.13-1-amd64? If yes how to proceed?
Thanks.
--
François Patte
UFR de mathématiques et informatique
Labo
On Tue, Jul 30, 2013 at 11:46:54PM -0400, Doug wrote:
> I have already done this multiple times and nothing seems to have changed.
> Here is a copy of mdadm.conf for your inspection.
>
>
> Does this look right? Any other ideas? Thanks for the help!
I can't tell whether the copy of mdadm.conf yo
I have already done this multiple times and nothing seems to have changed. Here
is a copy of mdadm.conf for your inspection.
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for
On Tue, Jul 30, 2013 at 12:01:40AM -0400, d...@ubutton.com wrote:
> After upgrading to kernel 3.9-1 from 3.2, my system will no longer
> boot. My OS is located on a RAID array, but when the system boots it
> says something along the lines of "mdadm: no arrays in the
> configuration file were found"
After upgrading to kernel 3.9-1 from 3.2, my system will no longer
boot. My OS is located on a RAID array, but when the system boots it
says something along the lines of "mdadm: no arrays in the configuration
file were found" and "root not found". Then it enters busy box. Once in
busy box I fin
On 16/01/12 21:14, Curt wrote:
> Yes, I verified in the kernel logs (/var/log/kern.log--thanks for that
> tip) : I was using 2.6.32-39 before; after the upgrade I'm using
> 2.6.32-39squeeze1.
According to the changelog, there has indeed been no other changes
between those versions.
I'm *sure* I
On 2012-01-16, Sven Joachim wrote:
>
>> dpkg.log says :
>>
>> upgrade linux-image-2.6.32-5-amd64 2.6.32-39 2.6.32-39squeeze1
>>
>> So there has been no version upgrade, apparently, and therefore the mystery
>> remains as to why the r8169 kernel driver works correctly now when it wasn't
>> working
On 2012-01-16 20:27 +0100, Curt wrote:
> On 2012-01-16, Sven Joachim wrote:
>
/var/log/dpkg.log would be the best place.
>>>
>>> I don't have that file on my system.
>>
>> That's a bit unfortunate. Did you deliberately turn off logging in
>> /etc/dpkg/dpkg.cfg ?
>
> Nope. I do have /var/dpk
On 2012-01-16, Sven Joachim wrote:
>>> /var/log/dpkg.log would be the best place.
>>
>> I don't have that file on my system.
>
> That's a bit unfortunate. Did you deliberately turn off logging in
> /etc/dpkg/dpkg.cfg ?
Nope. I do have /var/dpkg.log, sorry. Brain fart.
> It's expected that the
On 2012-01-16 19:20 +0100, Curt wrote:
> On 2012-01-16, Sven Joachim wrote:
>
>>> I don't know where to look to find out what kernel version I was using
>>> before.
>>
>> /var/log/dpkg.log would be the best place.
>
> I don't have that file on my system.
That's a bit unfortunate. Did you delib
On 2012-01-16, Sven Joachim wrote:
>> I don't know where to look to find out what kernel version I was using
>> before.
>
> /var/log/dpkg.log would be the best place.
I don't have that file on my system.
>> In /var/lib/dpkg/status-old it says:
>>
>> Package: linux-image-2.6-amd64
>
> This is j
On 2012-01-16 18:46 +0100, Curt wrote:
> On 2012-01-16, Sven Joachim wrote:
>>>
>>> I think a (prior) point release upgrade fixed it, not this security upgrade,
>>> but the security upgrade is built on top of the point release.
>>
>> According to debian/changelog, 2.6.32-36 was the last version i
On 2012-01-16, Sven Joachim wrote:
>>
>> I think a (prior) point release upgrade fixed it, not this security upgrade,
>> but the security upgrade is built on top of the point release.
>
> According to debian/changelog, 2.6.32-36 was the last version in which
> major changes were made to r8169, and
On 2012-01-16 17:14 +0100, Jon Dowland wrote:
> On Mon, Jan 16, 2012 at 03:50:39PM +, Curt wrote:
>> Did they fix the r8169, or was it all a bad dream?
>>
>> (I looked at the debian security advisory for the kernel upgrade, dated
>> 15 January, but it says nothi
On Mon, Jan 16, 2012 at 03:50:39PM +, Curt wrote:
> Did they fix the r8169, or was it all a bad dream?
>
> (I looked at the debian security advisory for the kernel upgrade, dated
> 15 January, but it says nothing about the matter).
I think a (prior) point release upgrade fixed
Got a kernel upgrade today from the security repository. I had
previously installed the Realtek proprietary driver (r8168) for my
network card, because the kernel module in squeeze was very problematic
(frequent disconnections, diminished throughput, etc...)
(curty@einstein:~$ uname -a
Linux
On Sun, 22 May 2011 18:56:21 +0200
Sven Joachim wrote:
> On 2011-05-22 18:37 +0200, Frank McCormick wrote:
>
> > Rebuilt initramfs...rebooted and everything **seems** fine.
> > However in looking through syslog I saw this:
> > [...]
> >
> > May 22 12:25:21 sid kernel: [5.698554] BUG: unabl
On 2011-05-22 18:37 +0200, Frank McCormick wrote:
> Rebuilt initramfs...rebooted and everything **seems** fine.
> However in looking through syslog I saw this:
> [...]
>
> May 22 12:25:21 sid kernel: [5.698554] BUG: unable to handle kernel NULL
> pointer dereference at (null)
Ouch.
> Is
On Sun, 22 May 2011 12:18:25 -0400
Frank McCormick wrote:
> On Sun, 22 May 2011 17:43:17 +0200
> Sven Joachim wrote:
>
> > On 2011-05-22 17:34 +0200, Frank McCormick wrote:
> >
> > > Same situation here - the problem arose after yesterdays
> > > upgrades...which are:
> > >
> > >
> > > [UPGRA
On Sun, 22 May 2011 16:51:25 +0100
Wolodja Wentland wrote:
> On Sun, May 22, 2011 at 11:34 -0400, Frank McCormick wrote:
>
> > Same situation here - the problem arose after yesterdays
> > upgrades...which are:
>
> > [UPGRADE] libgudev-1.0-0 169-1 -> 170-1
> > [UPGRADE] libudev0 169-1 -> 170-1
On Sun, 22 May 2011 17:43:17 +0200
Sven Joachim wrote:
> On 2011-05-22 17:34 +0200, Frank McCormick wrote:
>
> > Same situation here - the problem arose after yesterdays
> > upgrades...which are:
> >
> >
> > [UPGRADE] libgudev-1.0-0 169-1 -> 170-1
> > [UPGRADE] libudev0 169-1 -> 170-1
> > [UPG
On Sun, May 22, 2011 at 11:34 -0400, Frank McCormick wrote:
> Same situation here - the problem arose after yesterdays
> upgrades...which are:
> [UPGRADE] libgudev-1.0-0 169-1 -> 170-1
> [UPGRADE] libudev0 169-1 -> 170-1
> [UPGRADE] net-tools 1.60-23 -> 1.60-24
> [UPGRADE] udev 169-1 -> 170-1
>
On 2011-05-22 17:34 +0200, Frank McCormick wrote:
> Same situation here - the problem arose after yesterdays
> upgrades...which are:
>
>
> [UPGRADE] libgudev-1.0-0 169-1 -> 170-1
> [UPGRADE] libudev0 169-1 -> 170-1
> [UPGRADE] net-tools 1.60-23 -> 1.60-24
> [UPGRADE] udev 169-1 -> 170-1
> ==
Wolodja Wentland wrote:
On Sun, May 22, 2011 at 15:08 +0100, Anthony Campbell wrote:
I can only suppose that some package which was also upgraded today
(there were various libraries) has affected both kernels. I would put in
a bug report but I have no idea where the problem could lie.
Any sugge
On Sun, May 22, 2011 at 16:24 +0100, Anthony Campbell wrote:
> On 22 May 2011, Wolodja Wentland wrote:
> > On Sun, May 22, 2011 at 15:08 +0100, Anthony Campbell wrote:
> > > I can only suppose that some package which was also upgraded today
> > > (there were various libraries) has affected both ker
On Sun, 22 May 2011 16:24:02 +0100
Anthony Campbell wrote:
> On 22 May 2011, Wolodja Wentland wrote:
> > On Sun, May 22, 2011 at 15:08 +0100, Anthony Campbell wrote:
> > > I can only suppose that some package which was also upgraded today
> > > (there were various libraries) has affected both ker
On 22 May 2011, Wolodja Wentland wrote:
> On Sun, May 22, 2011 at 15:08 +0100, Anthony Campbell wrote:
> > I can only suppose that some package which was also upgraded today
> > (there were various libraries) has affected both kernels. I would put in
> > a bug report but I have no idea where the pr
On Sun, May 22, 2011 at 15:08 +0100, Anthony Campbell wrote:
> I can only suppose that some package which was also upgraded today
> (there were various libraries) has affected both kernels. I would put in
> a bug report but I have no idea where the problem could lie.
>
> Any suggestions?
A list o
I've been using linux-image-2.6.38-2-686 for some time without preblems.
After a dist-upgrade in Sid today I acquired
linux-image-2.6.39-1-686-pae. On booting this I had no connection
(wired) to my router. Also, on starting X (startx) the screen locked up
and I had to do a hard reset.
I reverted
From: John Magolske
Date: Wed, 04 May 2011 20:17:56 -0700
> Which suggests using the sysfsutils package & editing /etc/sysfs.conf
> so that these settings are applied automatically on boot...I did that.
Any idea why this setting is in /etc/sysfs.conf rather than /etc/sysctl.conf?
Thanks,
Thanks everyone for the helpful suggestions!
* Darac Marjal [110504 10:26]:
> Has your CPU governor changed, perhaps, to something more 'twitchy'?
> Try:
>cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
>
> If this returns "ondemand", for example, the CPU will jump to a higher
> fre
What kind of processor is built into your Thinkpad?
What is the output of lsmod?
Maybe the kernel module used for frequency scaling is not optimal.
--
Best regards,
Jörg-Volker.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact l
1 - 100 of 749 matches
Mail list logo
