Bug#245012: installation-reports: d-i permit to create file systems not mountable when rebooted
On Thu, Apr 22, 2004 at 06:15:41AM +0200, Giuseppe Sacco wrote: Il gio, 2004-04-22 alle 04:25, Steve Langasek ha scritto: On Thu, Apr 22, 2004 at 12:00:10AM +0200, Giuseppe Sacco wrote: Il mer, 2004-04-21 alle 23:08, Per Olofsson ha scritto: On Wed, Apr 21, 2004 at 22:34 +0200, Giuseppe Sacco wrote: I just found that initrd exists also for powerpc, but I think that no debian package provides and initrd kernel for powerpc. I think the kernel packages provide the initrd as well. That's what they do on i386, at least. Er, kernel-image-2.4.25-powerpc-pmac depends on kernel-modules-2.4.25-powerpc, which contains all of these modules; and the initrd is not included in the kernel package in any case -- it's built at package install time. It would be inordinately silly to go to all the trouble of shipping a kernel that's built for initrd support, and then only ship a static initrd with fixed contents! You might be right: I don't know how the initrd is built, but that kernel (and all powerpc kernels) does not create the initrd image. Maybe the installation procedure is to be changed and the initrd created, since actually the result is that I cannot mount the root XFS file system. I'm sorry, but I don't believe this is the case. You specifically said you had difficulties with the yaboot installation, and that after rebooting you had to construct your kernel commandline *by hand*, and that commandline did not reference your initrd -- so of course it was not used, whether or not the initrd existed on disk. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#245012: installation-reports: d-i permit to create file systems not mountable when rebooted
Il Thu, Apr 22, 2004 at 08:30:38AM -0500, Steve Langasek ha scritto: On Thu, Apr 22, 2004 at 06:15:41AM +0200, Giuseppe Sacco wrote: [...] Maybe the installation procedure is to be changed and the initrd created, since actually the result is that I cannot mount the root XFS file system. I'm sorry, but I don't believe this is the case. You specifically said you had difficulties with the yaboot installation, and that after rebooting you had to construct your kernel commandline *by hand*, and that commandline did not reference your initrd -- so of course it was not used, whether or not the initrd existed on disk. No, this is wrong: the initrd image wasn't built. I knew, because I did a previous installation and filed a different bug, that yaboot wasn't working. So I selected to do not install a boot loader from d-i menu (there is a specific menuitem). I did not receive any error. The installation was completed right. The kernel installation (that I might repeat even now) does not create the initrd file. Bye, Giuseppe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#245012: installation-reports: d-i permit to create file systems not mountable when rebooted
On Wed, Apr 21, 2004 at 02:46 +0200, Giuseppe Sacco wrote: hd:4 root=/dev/hda4 rw but the kernel was unable to mount the root partition probably because XFS isn't compiled into the default kernel (2.4.25-powerpc-pmac). I reinstalled everthing using ext3 and the new system mounted the root partition correctly. I believe that all filesystems offered during the installation need to be compiled *into* the kernel. They are provided as modules in an initrd. You must boot with the initrd. When rebooting (with ext3) I found that /etc/fstab contained only one line: # UNCONFIGURED FSTAB FOR BASE SYSTEM I think this is because you didn't complete the installation process. After rebooting I kept the installation process until prompted for APT sources. The system found the installation CD inserted so it indexed it, but then I was unable to specify a different CD I have because I couldn't eject the first CD. I had to switch to the second console, login as root, execute eject, read the error message, find out the device name for the cdrom, execute 'eject /dev/hdc', switch back to the first console. Then I selected to do not use aptitude, dselect or apt-get and I still got a message about installing popularity-context but APT stopped asking for a cdrom but it couldn't mount it because of the wrong /etc/fstab After creating /etc/fstab, APT worked correctly. And probably this too, then. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#245012: installation-reports: d-i permit to create file systems not mountable when rebooted
Il mer, 2004-04-21 alle 22:26, Per Olofsson ha scritto: On Wed, Apr 21, 2004 at 02:46 +0200, Giuseppe Sacco wrote: hd:4 root=/dev/hda4 rw but the kernel was unable to mount the root partition probably because XFS isn't compiled into the default kernel (2.4.25-powerpc-pmac). I reinstalled everthing using ext3 and the new system mounted the root partition correctly. I believe that all filesystems offered during the installation need to be compiled *into* the kernel. They are provided as modules in an initrd. You must boot with the initrd. I just found that initrd exists also for powerpc, but I think that no debian package provides and initrd kernel for powerpc. When rebooting (with ext3) I found that /etc/fstab contained only one line: # UNCONFIGURED FSTAB FOR BASE SYSTEM I think this is because you didn't complete the installation process. I think not, since I completed the installation and I was missing the file after the reboot. The installation was normal and I just missed to install the boot loader (that wasn't working) Thanks, Giuseppe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#245012: installation-reports: d-i permit to create file systems not mountable when rebooted
On Wed, Apr 21, 2004 at 22:34 +0200, Giuseppe Sacco wrote: I just found that initrd exists also for powerpc, but I think that no debian package provides and initrd kernel for powerpc. I think the kernel packages provide the initrd as well. That's what they do on i386, at least. I think not, since I completed the installation and I was missing the file after the reboot. The installation was normal and I just missed to install the boot loader (that wasn't working) Uhm, okay. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#245012: installation-reports: d-i permit to create file systems not mountable when rebooted
Il mer, 2004-04-21 alle 23:08, Per Olofsson ha scritto: On Wed, Apr 21, 2004 at 22:34 +0200, Giuseppe Sacco wrote: I just found that initrd exists also for powerpc, but I think that no debian package provides and initrd kernel for powerpc. I think the kernel packages provide the initrd as well. That's what they do on i386, at least. This is different for powerpc. Maybe Sven Luther should change the kernel he upload? ~$ cat /var/lib/dpkg/info/kernel-image-2.4.25-powerpc-pmac.list /. /boot /boot/config-2.4.25-powerpc /boot/vmlinux-2.4.25-powerpc /boot/vmlinux.coff-2.4.25-powerpc /boot/patches-2.4.25-powerpc /boot/System.map-2.4.25-powerpc /usr /usr/share /usr/share/doc /usr/share/doc/kernel-image-2.4.25-powerpc-pmac /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/Changes.gz /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/copyright /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/changelog.gz /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/QuikDefault.gz /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/Buildinfo /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/debian.README.gz /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/conf.vars.gz /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/buildinfo.gz /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/README.Debian.1st.gz /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/changelog.Debian.gz ~$ Bye, Giuseppe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#245012: installation-reports: d-i permit to create file systems not mountable when rebooted
On Thu, Apr 22, 2004 at 12:00:10AM +0200, Giuseppe Sacco wrote: Il mer, 2004-04-21 alle 23:08, Per Olofsson ha scritto: On Wed, Apr 21, 2004 at 22:34 +0200, Giuseppe Sacco wrote: I just found that initrd exists also for powerpc, but I think that no debian package provides and initrd kernel for powerpc. I think the kernel packages provide the initrd as well. That's what they do on i386, at least. This is different for powerpc. Maybe Sven Luther should change the kernel he upload? ~$ cat /var/lib/dpkg/info/kernel-image-2.4.25-powerpc-pmac.list /. /boot /boot/config-2.4.25-powerpc /boot/vmlinux-2.4.25-powerpc /boot/vmlinux.coff-2.4.25-powerpc /boot/patches-2.4.25-powerpc /boot/System.map-2.4.25-powerpc /usr /usr/share /usr/share/doc /usr/share/doc/kernel-image-2.4.25-powerpc-pmac /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/Changes.gz /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/copyright /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/changelog.gz /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/QuikDefault.gz /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/Buildinfo /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/debian.README.gz /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/conf.vars.gz /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/buildinfo.gz /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/README.Debian.1st.gz /usr/share/doc/kernel-image-2.4.25-powerpc-pmac/changelog.Debian.gz ~$ Er, kernel-image-2.4.25-powerpc-pmac depends on kernel-modules-2.4.25-powerpc, which contains all of these modules; and the initrd is not included in the kernel package in any case -- it's built at package install time. It would be inordinately silly to go to all the trouble of shipping a kernel that's built for initrd support, and then only ship a static initrd with fixed contents! -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#245012: installation-reports: d-i permit to create file systems not mountable when rebooted
Il gio, 2004-04-22 alle 04:25, Steve Langasek ha scritto: On Thu, Apr 22, 2004 at 12:00:10AM +0200, Giuseppe Sacco wrote: Il mer, 2004-04-21 alle 23:08, Per Olofsson ha scritto: On Wed, Apr 21, 2004 at 22:34 +0200, Giuseppe Sacco wrote: I just found that initrd exists also for powerpc, but I think that no debian package provides and initrd kernel for powerpc. I think the kernel packages provide the initrd as well. That's what they do on i386, at least. [...] Er, kernel-image-2.4.25-powerpc-pmac depends on kernel-modules-2.4.25-powerpc, which contains all of these modules; and the initrd is not included in the kernel package in any case -- it's built at package install time. It would be inordinately silly to go to all the trouble of shipping a kernel that's built for initrd support, and then only ship a static initrd with fixed contents! You might be right: I don't know how the initrd is built, but that kernel (and all powerpc kernels) does not create the initrd image. Maybe the installation procedure is to be changed and the initrd created, since actually the result is that I cannot mount the root XFS file system. Bye, Giuseppe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#245012: installation-reports: d-i permit to create file systems not mountable when rebooted
Package: installation-reports Version: daily 20040419 Severity: important INSTALL REPORT Debian-installer-version: daily 20040419 uname -a: Date: 2004-apr-21 02:00 CET Method: netinst CD image Machine: Apple PowerBook G4 15 Processor: 1 PowerPC @ 867Mhz Memory: 512Mb Root Device: Root Size/partition table: Output of lspci: Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[E] Reboot: [O] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: I installed the complete system on a new XFS partition but was unable of install yaboot because of #244957. So I rebooted the system using the installation disk and typed, at the boot prompt: hd:4 root=/dev/hda4 rw but the kernel was unable to mount the root partition probably because XFS isn't compiled into the default kernel (2.4.25-powerpc-pmac). I reinstalled everthing using ext3 and the new system mounted the root partition correctly. I believe that all filesystems offered during the installation need to be compiled *into* the kernel. When rebooting (with ext3) I found that /etc/fstab contained only one line: # UNCONFIGURED FSTAB FOR BASE SYSTEM After rebooting I kept the installation process until prompted for APT sources. The system found the installation CD inserted so it indexed it, but then I was unable to specify a different CD I have because I couldn't eject the first CD. I had to switch to the second console, login as root, execute eject, read the error message, find out the device name for the cdrom, execute 'eject /dev/hdc', switch back to the first console. Then I selected to do not use aptitude, dselect or apt-get and I still got a message about installing popularity-context but APT stopped asking for a cdrom but it couldn't mount it because of the wrong /etc/fstab After creating /etc/fstab, APT worked correctly. Bye, Giuseppe -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.3-1-k7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
