Re: Problems with d-i on self-made (debian-cd/easy-build.sh) Debian images
Hi Mario On Thu, 13 Oct 2011 11:45:36 +0200, Mario Fux debian...@unormal.org wrote: Non-text part: Multipart/Mixed Good morning And then trying to install I got the following error message in qemu and virtualbox: Error message: Error: Load installer components from CD: No kernel modules were found. This probably is due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive. As the error message says (unless there is a bug in d-i itself), the version of the kernel you are booting from your CD is not the same as in the archive. Which suite (stable, testing, unstable) are you tring to install? Did you somhow customize your installer kernel? These versions have to match exactly (including ABI version). The most likely cause is that the kernel got updated in between the moment you built your image and the installation. Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~ pgp60Gv62Wbnj.pgp Description: PGP signature
Bug#645308: tg3 broken for NetXtreme 5714S in squeeze 6.0.3 installer
Package: debian-installer Severity: important Tags: d-i squeeze Hi, this is a regression from 6.0.2.1 to 6.0.3. The IBM HS12 blade server has a Broadcom network chip: 04:04.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme 5714S Gigabit Ethernet [14e4:1669] (rev a3) 04:04.1 Ethernet controller [0200]: Broadcom Corporation NetXtreme 5714S Gigabit Ethernet [14e4:1669] (rev a3) when one tries to install squeeze 6.0.3 amd64 from the netinstall CD or via network boot, the network interface doesn't do DHCP in the installer (Network autoconfiguration failed). Via tcpdump, the DHCP server sees the DHCPDISCOVER sent out by the blade, responds with DHCPOFFER, but never sees a DHCPREQUEST. When I manually configure an IP address and ping the blade from the LAN, the pinging machine never sees the blade replying. When I ping from the blade to somewhere on the LAN, the remote machine sees the echo request, sends out an echo reply, but the blade does not see the reply. Manually running modprobe -r tg3, modprobe tg3 on a shell allows the installation to continue. The squeeze OS installed by the installer has working network immediaely. With a 6.0.2.1 amd64 netinstall CD, things are just fine. dmesg and syslog from the installer are attached. Greetings Marc installer-logs.txt.xz Description: application/xz
Re: About using static config with pxeboot/preseed
Julien Escario esca...@azylog.net writes: Hello, I'm trying to configure full automated install. The server is booting over pxe, get his dhcp lease and retrieve the preseed file over http. Preseeding is working well but not for the net config : ip address, hostname, ... After reboot, dhcp is still used and hostname is 'debian'. Is this a normal behaviour ? No way to use DHCP to get the address for d-i and install the server with a static address ? Probably not easily, but you can use preseed/late_command to overwrite /target/etc/network/interfaces if you wish. I use initrd preseeding with static network config during installation, and that works well. -- Regards, Feri. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ty7bu9e9@tac.ki.iif.hu
Re: Running cdebconf. Status and RFC
Hi guys, Just to let you know, I've done some work on it, had some real life stuff to deal with, and hit some technical issue, but I believe I just found what was my last blocking problem, so I'm now expecting to push a working version during the weekend. Regis On Thu, October 6, 2011 16:30, Regis Boudin wrote: Hi Joey, On Thu, October 6, 2011 16:07, Joey Hess wrote: Regis Boudin wrote: * debconf/frontend: debconf and cdebconf have different names for the frontends (Readline, Dialog, Gnome, versus text, newt, gtk), which causes all sorts of issues for the transition. Any objection to using cdebconf/frontend instead ? Not really, but the rest of d-i would need to be checked for uses of it. That part should be fine, I can keep the existing checks for both the old and new fields. * When switching from debconf to cdebconf, there is the problem of the database. One uses /var/cache/debconf, the other /var/lib/cdebconf by default, meaning either it has to be migrated, or cdebconf will have to use /var/cache/debconf. The main issue of migrating the database is in the case of a system wide upgrade where cdebconf would actually replace debconf. Between the package being unpacked and the postinst script being run, the database will be unconfigured ; so any other package trying to use debconf in this interval won't have access to the previously set values. This includes triggers, e.g. in the man-db postinst. Do you have any opinion in the long term ? In the short term, I could include the migration script for people willing to test, but I would like someone else's view on it before I do it. I can see no way around debconf and cdebconf using the same database, perhaps a preinst would need to move it and set up a symlink so debconf still sees it? That could actually be a solution. I'll try something along these lines, and make a new release with only the (c)debconf/frontend change in the meantime. Thanks for the answer and suggstion. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/a4fffc2104ca06df96068dd22ae0b44c.squir...@imalip.net
Re: About using static config with pxeboot/preseed
Hi, On 11.10.2011 17:17, Julien Escario wrote: I'm trying to configure full automated install. The server is booting over pxe, get his dhcp lease and retrieve the preseed file over http. Preseeding is working well but not for the net config : ip address, hostname, ... After reboot, dhcp is still used and hostname is 'debian'. Is this a normal behaviour ? No way to use DHCP to get the address for d-i and install the server with a static address ? Yeah, we noticed that as well. In our provisioning software (noc-ps) we simply work around that by not specifying the configuration in the preseed file, but feeding a static network configuration through kernel parameters: == netcfg/disable_dhcp=true netcfg/get_ipaddress=$ip netcfg/get_netmask=$netmask netcfg/get_gateway=$gateway == Regarding hostname: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606636 Yours sincerely, Floris Bos -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e36b997e4ed5237f50a929d256850...@to-the-max.net
Re: Problems with d-i on self-made (debian-cd/easy-build.sh) Debian images
Am Freitag 14 Oktober 2011, 10.07:27 schrieb Gaudenz Steinlin: Hi Mario Morning Gaudenz On Thu, 13 Oct 2011 11:45:36 +0200, Mario Fux debian...@unormal.org wrote: Non-text part: Multipart/Mixed Good morning And then trying to install I got the following error message in qemu and virtualbox: Error message: Error: Load installer components from CD: No kernel modules were found. This probably is due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive. As the error message says (unless there is a bug in d-i itself), the version of the kernel you are booting from your CD is not the same as in the archive. Which suite (stable, testing, unstable) are you tring to install? Did you somhow customize your installer kernel? These versions have to match exactly (including ABI version). No. In the first attempts I used the same version (suite) for the installer images as for the rest of the distribution. Afterwards I tried other combination: d-i from sid and rest from wheezy. Didn't really help. The most likely cause is that the kernel got updated in between the moment you built your image and the installation. Ok. Will try it again in the next days with an uptodate mirror and will come back if it doesn't help. thx Mario -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201110141940.55941.debian...@unormal.org
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * FAILED BUILD: kfreebsd-amd64 Oct 15 00:12 buildd@fano build_cdrom http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom.log * FAILED BUILD: kfreebsd-amd64 Oct 15 00:13 buildd@fano build_netboot http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log * FAILED BUILD: kfreebsd-amd64 Oct 15 00:15 buildd@fano build_netboot-gtk http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk.log * OLD BUILD:sparc Oct 12 00:13 buildd@zee build_cdrom http://d-i.debian.org/daily-images/sparc/daily/build_cdrom.log * OLD BUILD:sparc Oct 12 00:15 buildd@zee build_netboot http://d-i.debian.org/daily-images/sparc/daily/build_netboot.log * OLD BUILD:sparc Oct 12 00:18 buildd@zee build_miniiso http://d-i.debian.org/daily-images/sparc/daily/build_miniiso.log * FAILED BUILD: amd64 Oct 14 22:27 debian-cd@pettersson 1sidkfreebsd-amd64 http://cdbuilder.debian.org/cdimage-log/1sidkfreebsd-amd64 * FAILED BUILD: amd64 Oct 14 22:27 debian-cd@pettersson 2sidkfreebsd-amd64 http://cdbuilder.debian.org/cdimage-log/2sidkfreebsd-amd64 Totals: 109 builds (5 failed, 3 old) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1resbc-00040c...@ravel.debian.org
