Hello,
maximilian attems <m...@stro.at> wrote:
> oh sorry got confused by all that.
> could you post the content of the initramfs in question?
>
> lsinitramfs /boot/initramfs-2.6.32-5-486 | grep modules
t...@debian:~/Desktop/571035$ lsinitramfs initrd-in-question | grep modules
conf/modules
lib/modules
lib/modules/2.6.32-5-486
lib/modules/2.6.32-5-486/kernel
lib/modules/2.6.32-5-486/kernel/fs
lib/modules/2.6.32-5-486/kernel/fs/mbcache.ko
lib/modules/2.6.32-5-486/kernel/fs/ext2
lib/modules/2.6.32-5-486/kernel/fs/ext2/ext2.ko
lib/modules/2.6.32-5-486/kernel/drivers
lib/modules/2.6.32-5-486/kernel/drivers/ide
lib/modules/2.6.32-5-486/kernel/drivers/ide/ide-core.ko
lib/modules/2.6.32-5-486/kernel/drivers/ide/ide-gd_mod.ko
lib/modules/2.6.32-5-486/kernel/drivers/ide/ide-cd_mod.ko
lib/modules/2.6.32-5-486/kernel/drivers/cdrom
lib/modules/2.6.32-5-486/kernel/drivers/cdrom/cdrom.ko
lib/modules/2.6.32-5-486/kernel/drivers/scsi
lib/modules/2.6.32-5-486/kernel/drivers/scsi/scsi_mod.ko
lib/modules/2.6.32-5-486/kernel/drivers/scsi/sd_mod.ko
lib/modules/2.6.32-5-486/kernel/drivers/virtio
lib/modules/2.6.32-5-486/kernel/drivers/virtio/virtio_pci.ko
lib/modules/2.6.32-5-486/kernel/drivers/thermal
lib/modules/2.6.32-5-486/kernel/drivers/thermal/thermal_sys.ko
lib/modules/2.6.32-5-486/kernel/drivers/acpi
lib/modules/2.6.32-5-486/kernel/drivers/acpi/fan.ko
lib/modules/2.6.32-5-486/kernel/drivers/acpi/thermal.ko
lib/modules/2.6.32-5-486/kernel/drivers/md
lib/modules/2.6.32-5-486/kernel/drivers/md/dm-mod.ko
lib/modules/2.6.32-5-486/kernel/lib
lib/modules/2.6.32-5-486/kernel/lib/crc-t10dif.ko
lib/modules/2.6.32-5-486/modules.dep.bin
lib/modules/2.6.32-5-486/modules.dep
lib/modules/2.6.32-5-486/modules.alias.bin
lib/modules/2.6.32-5-486/modules.alias
lib/modules/2.6.32-5-486/modules.symbols.bin
lib/modules/2.6.32-5-486/modules.softdep
lib/modules/2.6.32-5-486/modules.symbols
lib/modules/2.6.32-5-486/modules.devname
I know, that in the past, the module ide_generic was needed for
this machine to access the harddisc.
> also the run of mkinitramfs might be interesting
> sh -x /usr/sbin/mkinitramfs -k 2.6.32-5-486 -o /tmp/foo
I'm a bit puzzled about this one.
I have a laptop here, where the 2.6.32-5-486 kernel is installed,
included the initrd in question.
But that laptop is unable to boot (this is the basic problem of this
bugreport :-))
Where should I execute this command?
On that laptop within a chroot? (I'm afraid, this will not work because
of not enough ram)
Or on another machine?
> which devices do exist on boot in that initramfs
> ls /dev/[hs]da*
> ls /dev/disk/by-uuid/
(initramfs) ls /dev/[hs]da*
ls: /dev/[hs]da*: No such file or directory
(initramfs) ls /dev/disk/by-uuid/
ls: /dev/disk/by-uuid/: No such file or directory
Thanks
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-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
