Generating a Lenny Netinst CD with a newer kernel
Since the lenny netinst CD recognized neither the RAID controller, nor the networking card of our server (a dell poweredge r710), we decided to build ourselves a custom lenny installer cd using a newer installer kernel. We tried to follow these tutorials: https://lliurex.net/projects/valencia/lliurex-pool/browser/installer/trunk/debian-installer/doc/custom-kernel.txt?rev=3506 http://wiki.debian.org/DebianInstaller/Modify/CustomKernel We used the kernel from lenny_backports (2.6.29). After figuring out that kernel-wedge had to be upgraded to its unstable version, we managed to build the udebs, and moved them to build/localudebs. We than found out that we had to uncomment monolithic in build/config/amd64.cfg to make the build_monolithic target available. However, make build_monolithic fails with E: Konnte Paket acpi-modules-2.6.29-2-amd64-di nicht finden (Transl.: could not find packet acpi-modules-2.6.29-2-amd64-di) Furthermore, there is a lot of stuff like fat-modules-2.6.26-1-amd64-di in the package list, even though we have only build udebs for 2.6.29, and changed the KERNELVESION parameter in build/config/amd64.cfg accordingly. We tried copying the line deb copy:/usr/src/debian-installer-20090123lenny1/build/ localudebs/ from build/sources.list.udeb to /etc/apt/sources.list. Now we can download the module acpi-modules-2.6.29-2-amd64-di using normal apt-get. So the build script really _should_ find the packages, shouldn't it? What are we doing wrong? And what about the 2.6.26 packages?
Re: Generating a Lenny Netinst CD with a newer kernel
-installer Packages OK http://ftp.nl.debian.org lenny-proposed-updates/main/debian-installer Packages Paketlisten werden gelesen... Fertig Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut... Fertig Need to download: acpi-modules-2.6.29-2-amd64-di ai-choosers anna apt-mirror-setup apt-setup-udeb archdetect auto-install base-installer bogl-bterm-udeb bootstrap-base busybox-udeb cdebconf-newt-udeb cdebconf-priority cdebconf-udeb choose-mirror choose-mirror-bin clock-setup console-keymaps-at core-modules-2.6.26-1-amd64-di crypto-core-modules-2.6.26-1-amd64-di crypto-dm-modules-2.6.26-1-amd64-di crypto-modules-2.6.26-1-amd64-di cryptsetup-udeb debian-archive-keyring-udeb debootstrap-udeb dhcp3-client-udeb di-utils di-utils-mapdevfs di-utils-reboot di-utils-shell di-utils-terminfo disk-detect dmsetup-udeb e2fsprogs-udeb env-preseed ethdetect ext2-modules-2.6.26-1-amd64-di ext3-modules-2.6.26-1-amd64-di fat-modules-2.6.26-1-amd64-di fdisk-udeb file-preseed finish-install gpgv-udeb grub-installer hw-detect initrd-preseed installation-locale jfs-modules-2.6.26-1-amd64-di jfsutils-udeb kbd-chooser kernel-image-2.6.26-1-amd64-di kernel-image-2.6.29-2-amd64-di kickseed-common libblkid1-udeb libdebconfclient0-udeb libdebian-installer4-udeb libdevmapper1.02.1-udeb libfribidi0-udeb libiw29-udeb libnss-dns-udeb libparted1.8-udeb libpcre3-udeb libpopt0-udeb libsysfs2-udeb libtextwrap1-udeb libuuid1-udeb lilo-installer localechooser lowmemcheck lvm2-udeb main-menu md-modules-2.6.26-1-amd64-di mdadm-udeb mdcfg-utils mkreiserfs-udeb module-init-tools-udeb nano-udeb netcfg network-preseed nls-core-modules-2.6.26-1-amd64-di nobootloader ntfsprogs-udeb os-prober-udeb partconf-find-partitions partman-auto partman-auto-raid partman-base partman-basicfilesystems partman-basicmethods partman-efi partman-ext3 partman-jfs partman-md partman-partitioning partman-reiserfs partman-target partman-utils partman-xfs pciutils-udeb pcmciautils-udeb pkgsel preseed-common rdate-udeb reiserfs-modules-2.6.26-1-amd64-di rescue-check rescue-mode rootskel save-logs tzsetup-udeb udev-udeb udpkg user-setup-udeb xfs-modules-2.6.26-1-amd64-di xfsprogs-udeb zlib1g-udeb Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut... Fertig E: Konnte Paket acpi-modules-2.6.29-2-amd64-di nicht finden make[2]: *** [stamps/get_udebs-monolithic-stamp] Fehler 100 make[1]: *** [_build] Fehler 2 make: *** [build_monolithic] Fehler 2 2009/6/5 Martin Gerdes martin.gerde...@googlemail.com Since the lenny netinst CD recognized neither the RAID controller, nor the networking card of our server (a dell poweredge r710), we decided to build ourselves a custom lenny installer cd using a newer installer kernel. We tried to follow these tutorials: https://lliurex.net/projects/valencia/lliurex-pool/browser/installer/trunk/debian-installer/doc/custom-kernel.txt?rev=3506 http://wiki.debian.org/DebianInstaller/Modify/CustomKernel We used the kernel from lenny_backports (2.6.29). After figuring out that kernel-wedge had to be upgraded to its unstable version, we managed to build the udebs, and moved them to build/localudebs. We than found out that we had to uncomment monolithic in build/config/amd64.cfg to make the build_monolithic target available. However, make build_monolithic fails with E: Konnte Paket acpi-modules-2.6.29-2-amd64-di nicht finden (Transl.: could not find packet acpi-modules-2.6.29-2-amd64-di) Furthermore, there is a lot of stuff like fat-modules-2.6.26-1-amd64-di in the package list, even though we have only build udebs for 2.6.29, and changed the KERNELVESION parameter in build/config/amd64.cfg accordingly. We tried copying the line deb copy:/usr/src/debian-installer-20090123lenny1/build/ localudebs/ from build/sources.list.udeb to /etc/apt/sources.list. Now we can download the module acpi-modules-2.6.29-2-amd64-di using normal apt-get. So the build script really _should_ find the packages, shouldn't it? What are we doing wrong? And what about the 2.6.26 packages? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Generating a Lenny Netinst CD with a newer kernel
Found a solution for at least a part of the problem: The file sources.list.udeb.local did not have the correct entries. sources.list.udeb even contains the comment # This file is automatically generated, edit sources.list.udeb.local instead., so my bad. Must have been too late... Now all that is left is to resolve the dependencies: packages crypto-core-modules-2.6.29-2-amd64-di and efi-modules are missing. And I'm still wondering about the 2.6.26 stuff. 2009/6/5 Martin Gerdes martin.gerde...@googlemail.com: Since the lenny netinst CD recognized neither the RAID controller, nor the networking card of our server (a dell poweredge r710), we decided to build ourselves a custom lenny installer cd using a newer installer kernel. We tried to follow these tutorials: https://lliurex.net/projects/valencia/lliurex-pool/browser/installer/trunk/debian-installer/doc/custom-kernel.txt?rev=3506 http://wiki.debian.org/DebianInstaller/Modify/CustomKernel We used the kernel from lenny_backports (2.6.29). After figuring out that kernel-wedge had to be upgraded to its unstable version, we managed to build the udebs, and moved them to build/localudebs. We than found out that we had to uncomment monolithic in build/config/amd64.cfg to make the build_monolithic target available. However, make build_monolithic fails with E: Konnte Paket acpi-modules-2.6.29-2-amd64-di nicht finden (Transl.: could not find packet acpi-modules-2.6.29-2-amd64-di) Furthermore, there is a lot of stuff like fat-modules-2.6.26-1-amd64-di in the package list, even though we have only build udebs for 2.6.29, and changed the KERNELVESION parameter in build/config/amd64.cfg accordingly. We tried copying the line deb copy:/usr/src/debian-installer-20090123lenny1/build/ localudebs/ from build/sources.list.udeb to /etc/apt/sources.list. Now we can download the module acpi-modules-2.6.29-2-amd64-di using normal apt-get. So the build script really _should_ find the packages, shouldn't it? What are we doing wrong? And what about the 2.6.26 packages? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Generating a Lenny Netinst CD with a newer kernel
Prividing dummy packages for the two packages created an iso, which boots, and recognizes both the networking card (after adding the firmware from an usbstick to /lib/firmware), and the hard drive. :-) Now the only problem left to solve is to get a kernel form lenny_backports installed, so that the installed system will actually find it's root file system. Anyway, the problem of creating an iso is solved, sorry about the noise. 2009/6/5 Martin Gerdes martin.gerde...@googlemail.com: Found a solution for at least a part of the problem: The file sources.list.udeb.local did not have the correct entries. sources.list.udeb even contains the comment # This file is automatically generated, edit sources.list.udeb.local instead., so my bad. Must have been too late... Now all that is left is to resolve the dependencies: packages crypto-core-modules-2.6.29-2-amd64-di and efi-modules are missing. And I'm still wondering about the 2.6.26 stuff. 2009/6/5 Martin Gerdes martin.gerde...@googlemail.com: Since the lenny netinst CD recognized neither the RAID controller, nor the networking card of our server (a dell poweredge r710), we decided to build ourselves a custom lenny installer cd using a newer installer kernel. We tried to follow these tutorials: https://lliurex.net/projects/valencia/lliurex-pool/browser/installer/trunk/debian-installer/doc/custom-kernel.txt?rev=3506 http://wiki.debian.org/DebianInstaller/Modify/CustomKernel We used the kernel from lenny_backports (2.6.29). After figuring out that kernel-wedge had to be upgraded to its unstable version, we managed to build the udebs, and moved them to build/localudebs. We than found out that we had to uncomment monolithic in build/config/amd64.cfg to make the build_monolithic target available. However, make build_monolithic fails with E: Konnte Paket acpi-modules-2.6.29-2-amd64-di nicht finden (Transl.: could not find packet acpi-modules-2.6.29-2-amd64-di) Furthermore, there is a lot of stuff like fat-modules-2.6.26-1-amd64-di in the package list, even though we have only build udebs for 2.6.29, and changed the KERNELVESION parameter in build/config/amd64.cfg accordingly. We tried copying the line deb copy:/usr/src/debian-installer-20090123lenny1/build/ localudebs/ from build/sources.list.udeb to /etc/apt/sources.list. Now we can download the module acpi-modules-2.6.29-2-amd64-di using normal apt-get. So the build script really _should_ find the packages, shouldn't it? What are we doing wrong? And what about the 2.6.26 packages? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
