Re: squeeze kernel upgrade fixes r8169 network driver?

2012-01-17 Thread Jon Dowland
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

Re: squeeze kernel upgrade fixes r8169 network driver?

2012-01-16 Thread Curt
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

Re: squeeze kernel upgrade fixes r8169 network driver?

2012-01-16 Thread Sven Joachim
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

Re: squeeze kernel upgrade fixes r8169 network driver?

2012-01-16 Thread Curt
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

Re: squeeze kernel upgrade fixes r8169 network driver?

2012-01-16 Thread Sven Joachim
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

Re: squeeze kernel upgrade fixes r8169 network driver?

2012-01-16 Thread Curt
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

Re: squeeze kernel upgrade fixes r8169 network driver?

2012-01-16 Thread Sven Joachim
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

Re: squeeze kernel upgrade fixes r8169 network driver?

2012-01-16 Thread Curt
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

Re: squeeze kernel upgrade fixes r8169 network driver?

2012-01-16 Thread Sven Joachim
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 nothing about the matter). > > I thin

Re: squeeze kernel upgrade fixes r8169 network driver?

2012-01-16 Thread Jon Dowland
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 it, not this sec

squeeze kernel upgrade fixes r8169 network driver?

2012-01-16 Thread Curt
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 eins