Well, it’s Debian Stable, with the following changes:
Newer kernel from backports (2.6.38 and now 2.6.39)
Newer transmission-daemon from experimental (2.32)
sources.list
#
# deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official Snapshot amd64
LIVE/INSTALL Binary 20110324-07:27]/ squeeze mai
After making some backups, I tried to upgrade the kernel again.
Guess what? It just works now.
The term.log section looks nothing like the one above.
Also the old kernel has been retained.
term.log:
Log started: 2011-08-22 22:23:29
(Reading database ... M(Reading database ... 5%M(Reading database
I opened a new bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638896
It also questions Luke's questions.
Thanks so far.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: htt
ny other things I need to do (different) to be able to analyse things for
you guys?
-Original Message-
From: Luke Kenneth Casson Leighton
Sent: Monday, August 22, 2011 7:56 PM
To: Jonathan Nieder ; 636123-qu...@bugs.debian.org
Cc: Valentijn Scholten ; 636123-submit...@bugs.debian.org
Below is the snippet from term.log
As you can see I carefully ignored the warning about the kernel being removed.
I am used to having the old kernel still available as a boot option in grub.
After this I rebooted and ran into the kernel panic.
Log started: 2011-08-21 22:40:54
(Reading database .
I am running into a similar isue with 2.6.39.2. amd64.
Intel DH55TC with a Pentium G6950.
I was running a Debian Squeeze with 2.6.38.2 from backports. Was running
fine.
I decided to install 2.6.39.2 from backports (apt-get install ...)
It removed the old kernel and installed the new one.
I
6 matches
Mail list logo
