Hello,
Ben Hutchings <b...@decadent.org.uk> wrote:
> On Mon, 2010-09-06 at 22:04 +0200, Holger Wansing wrote:
> > Hello,
> >
> > Ben Hutchings <b...@decadent.org.uk> wrote:
> > > On Sun, 2010-09-05 at 23:15 +0200, Holger Wansing wrote:
> > > > 2. the second is a debian-installer kernel.
> > > > I copied the kernel and initrd from a debian-installer netinst cd
> > > > (the same cd which was used to perform the test installation, leading
> > > > to this bugreport #571035, an debian-testing daily build from
> > > > 23. Aug 2010.
> > > > That kernel boots fine!!!
> > >
> > > So what's the version of that kernel (from /proc/version)?
> >
> > ~ # cat /proc/version
> > Linux version 2.6.32-5-486 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc
> > version 4.3.5 (Debian 4.3.5-1) ) #1 Tue Jun 1 04:27:25 UTC 2010
> >
> > Be aware, that this is a debian-installer kernel (booting that kernel brings
> > up the debian installation process). That might have another config?
>
> d-i uses the kernel and modules from a regular kernel package, only
> divided between multiple packages to reduce memory and network usage.
>
> So this seems to be a regression between 2.6.32-15 (used in the
> installer) and 2.6.32-20 (current version in testing on 25th August, and
> presumably what it installed). Unfortunately I can't see any changes
> between these versions which might be responsible.
>
> Could you try testing the intermediate versions, which should still be
> available from
> <http://snapshot.debian.org/binary/linux-image-2.6.32-5-486/>?
Sorry for the delay!
I tried the kernel versions 2.6.32-15 to -19 and found them all booting
so far.
2.6.32-21 also boots.
But I should have to mention, what I'm doing:
The system in question is an low memory system, an old Toshiba
Satellite laptop, that I only use for here.
The laptop has only 32MB of RAM, and because of that I am unable to
use the rescue mode of the debian-installer (rescue mode consumes to
much RAM since squeeze, this was already reported as #571715).
As a result of this, I use the following szenario to test the kernels
mentioned above:
On my main system, I download the kernel-image.deb Ben pointed me to,
and execute "dpkg -x kernel-image-xxxx.deb unpacked" to unpack the
deb-package.
Then I copy the files in "unpacked/boot" to an usbstick (that's the files
vmlinuz-2.6.32-xxxxx, config2.6.32-xxxxx and System.map-2.6.32-xxxxxx).
Then I boot the low-memory machine with a debian-installer cd, go through
the installation process so far, until I have the possibility to access
the harddisc and the usbstick.
Then I copy the three files to /boot on the machine and edit the grub
config file, to be able to boot the kernel from the grub-menu.
Summary: I have a kernel, but no initrd. And with this constellation,
the kernel boots, until he comes to the point where the root filesystem
is to be found, what fails:
"Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)"
But this is not a problem in this case, important is, that the kernel itself
boots, right?
So, maybe there is a problem with the initrd?
Maybe with the size of it? (remember that this is a lowmem machine)
Holger
--
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 2.5.0
under DEBIAN GNU/LINUX 5.0.0 - L e n n y
Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100911231856.69935138.li...@wansing-online.de
