Re: bug in Sarge Debian Installer
On Sun, Dec 12, 2004 at 06:42:36PM +0100, Michael Rasmussen wrote: > Hi all > søn, 12 12 2004 kl. 13:53 +0100, skrev Frans Pop: > > One option for debugging this is looking at the packages sent over the > > network using a sniffer. > > > Inclosed you will find the log done with tcpdump -i eth0 port 69 or port > 67 -l | tee filename > > > > > > > > To me they seem identical so either it must be a bug i the PXE > implementation or in the kernel provided with debian-installer. And as the kernel provided with debian-installer works fine for the correct behaviour situation, that leaves the PXE implementation as culpritt. So you are completely right that you should use the onboard NIC. I can recomment http://www.etherboot.org for netbooting. See You under another Subject line Geert Stappers signature.asc Description: Digital signature
Re: bug in Sarge Debian Installer
Hi all søn, 12 12 2004 kl. 13:53 +0100, skrev Frans Pop: > One option for debugging this is looking at the packages sent over the > network using a sniffer. > Inclosed you will find the log done with tcpdump -i eth0 port 69 or port 67 -l | tee filename 18:37:08.153610 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xdd689837 secs:4 flags:0x8000 [|bootp] 18:37:09.002966 balder.datanom.net.bootps > 255.255.255.255.bootpc: xid:0xdd689837 secs:4 flags:0x8000 Y:192.168.2.85 S:balder.datanom.net ether 0:10:dc:68:98:37 [|bootp] [tos 0x10] 18:37:10.137043 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xdd689837 secs:4 flags:0x8000 [|bootp] 18:37:10.138957 balder.datanom.net.bootps > 255.255.255.255.bootpc: xid:0xdd689837 secs:4 flags:0x8000 Y:192.168.2.85 S:balder.datanom.net ether 0:10:dc:68:98:37 [|bootp] [tos 0x10] 18:37:10.144226 192.168.2.85.2070 > balder.datanom.net.tftp: 28 RRQ "/pxelinux.0" 18:37:10.146507 192.168.2.85.2071 > balder.datanom.net.tftp: 33 RRQ "/pxelinux.0" 18:37:10.179589 192.168.2.85.57089 > balder.datanom.net.tftp: 52 RRQ "/pxelinux.cfg/C0A80255" 18:37:10.182760 192.168.2.85.56834 > balder.datanom.net.tftp: 51 RRQ "/pxelinux.cfg/C0A8025" 18:37:10.185932 192.168.2.85.56579 > balder.datanom.net.tftp: 50 RRQ "/pxelinux.cfg/C0A802" 18:37:10.189162 192.168.2.85.56324 > balder.datanom.net.tftp: 49 RRQ "/pxelinux.cfg/C0A80" 18:37:10.192486 192.168.2.85.56069 > balder.datanom.net.tftp: 48 RRQ "/pxelinux.cfg/C0A8" 18:37:10.195774 192.168.2.85.55814 > balder.datanom.net.tftp: 47 RRQ "/pxelinux.cfg/C0A" 18:37:10.199038 192.168.2.85.9 > balder.datanom.net.tftp: 46 RRQ "/pxelinux.cfg/C0" 18:37:10.20 192.168.2.85.55304 > balder.datanom.net.tftp: 45 RRQ "/pxelinux.cfg/C" 18:37:10.205667 192.168.2.85.55049 > balder.datanom.net.tftp: 51 RRQ "/pxelinux.cfg/default" 18:37:10.207065 192.168.2.85.55050 > balder.datanom.net.tftp: 73 RRQ "/debian-installer/boot-screens/syslinux.txt" 18:37:10.208381 192.168.2.85.55051 > balder.datanom.net.tftp: 71 RRQ "/debian-installer/boot-screens/splash.rle" 18:37:15.176893 192.168.2.85.55052 > balder.datanom.net.tftp: 53 RRQ "/debian-installer/linux" 18:37:15.452834 192.168.2.85.55053 > balder.datanom.net.tftp: 57 RRQ "/debian-installer/initrd.gz" 18:34:16.660281 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xb4b8ddd7 secs:4 flags:0x8000 [|bootp] 18:34:17.006795 balder.datanom.net.bootps > 255.255.255.255.bootpc: xid:0xb4b8ddd7 secs:4 flags:0x8000 Y:192.168.2.50 S:balder.datanom.net ether 0:2:b3:b8:dd:d7 [|bootp] [tos 0x10] 18:34:17.632192 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xb4b8ddd7 secs:4 flags:0x8000 [|bootp] 18:34:17.635490 balder.datanom.net.bootps > 255.255.255.255.bootpc: xid:0xb4b8ddd7 secs:4 flags:0x8000 Y:192.168.2.50 S:balder.datanom.net ether 0:2:b3:b8:dd:d7 [|bootp] [tos 0x10] 18:34:17.640746 192.168.2.50.2070 > balder.datanom.net.tftp: 28 RRQ "/pxelinux.0" 18:34:17.643039 192.168.2.50.2071 > balder.datanom.net.tftp: 33 RRQ "/pxelinux.0" 18:34:17.686114 192.168.2.50.57089 > balder.datanom.net.tftp: 52 RRQ "/pxelinux.cfg/C0A80232" 18:34:17.689643 192.168.2.50.56834 > balder.datanom.net.tftp: 51 RRQ "/pxelinux.cfg/C0A8023" 18:34:17.693067 192.168.2.50.56579 > balder.datanom.net.tftp: 50 RRQ "/pxelinux.cfg/C0A802" 18:34:17.696419 192.168.2.50.56324 > balder.datanom.net.tftp: 49 RRQ "/pxelinux.cfg/C0A80" 18:34:17.699825 192.168.2.50.56069 > balder.datanom.net.tftp: 48 RRQ "/pxelinux.cfg/C0A8" 18:34:17.703137 192.168.2.50.55814 > balder.datanom.net.tftp: 47 RRQ "/pxelinux.cfg/C0A" 18:34:17.706405 192.168.2.50.9 > balder.datanom.net.tftp: 46 RRQ "/pxelinux.cfg/C0" 18:34:17.709576 192.168.2.50.55304 > balder.datanom.net.tftp: 45 RRQ "/pxelinux.cfg/C" 18:34:17.713049 192.168.2.50.55049 > balder.datanom.net.tftp: 51 RRQ "/pxelinux.cfg/default" 18:34:17.714497 192.168.2.50.55050 > balder.datanom.net.tftp: 73 RRQ "/debian-installer/boot-screens/syslinux.txt" 18:34:17.715895 192.168.2.50.55051 > balder.datanom.net.tftp: 71 RRQ "/debian-installer/boot-screens/splash.rle" 18:34:26.720787 192.168.2.50.55052 > balder.datanom.net.tftp: 53 RRQ "/debian-installer/linux" 18:34:27.047397 192.168.2.50.55053 > balder.datanom.net.tftp: 57 RRQ "/debian-installer/initrd.gz" To me they seem identical so either it must be a bug i the PXE implementation or in the kernel provided with debian-installer. Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xE3E80917 -- You two ought to be more careful--your love could drag on for years and years. signature.asc Description: Dette er en digitalt underskrevet brevdel
Re: [Fwd: Re: bug in Sarge Debian Installer]
On Sun, Dec 12, 2004 at 01:49:10PM +0100, Michael Rasmussen wrote: > Videresendt besked > > Fra: Michael Rasmussen <[EMAIL PROTECTED]> > > Til: Geert Stappers <[EMAIL PROTECTED]> A previous private send message forwarded to this list, allready answered to the list. > > Emne: Re: bug in Sarge Debian Installer > > Dato: Sun, 12 Dec 2004 13:26:25 +0100 > > søn, 12 12 2004 kl. 13:12 +0100, skrev Geert Stappers: > > > > > What is the color of the blank screen?(black? blue? other?) > > Black. Cheers Geert Stappers signature.asc Description: Digital signature
Re: bug in Sarge Debian Installer
søn, 12 12 2004 kl. 13:53 +0100, skrev Frans Pop: > I very much doubt this is an installer problem, as the installer is not > yet running at that time. > It could either be a problem in your bios with regard to PXE booting or > something in the way the files to be fetched are set up on the tftp > server (which would kind of make it an installation media problem). > If I use the PXE boot option from the onboard device all works as intended. To very I also have tried Ubuntu which uses the same installer and the same thing happend: Onboard all is fine, added device the same error > We do know that some architectures don't seem to like some tftp servers, > so you could try switching your tftp server. > atftpd and tftpd-hpa seem to work for i386. > My tftp is tftpd-hpa running on a Debian-Woody. This works well in any other situations. > I have not seen reports of this problem before. I guess your best bet is > try to solve it yourself and let us know if you find a solution. > Well one solution is obvious: use the onboard device:-) > One option for debugging this is looking at the packages sent over the > network using a sniffer. I will make a log from tcp-dump from both schenarios. Information is to follow. Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xE3E80917 -- You two ought to be more careful--your love could drag on for years and years. signature.asc Description: Dette er en digitalt underskrevet brevdel
Re: bug in Sarge Debian Installer
On Sun, Dec 12, 2004 at 01:26:25PM +0100, Michael Rasmussen wrote: > søn, 12 12 2004 kl. 13:12 +0100, skrev Geert Stappers: $ cd /usr/src/conglomerate [EMAIL PROTECTED]:/usr/src/conglomerate $ grep -R [EMAIL PROTECTED] . Binary file ./debian/conglomerate-common/usr/share/locale/da/LC_MESSAGES/conglomerate.mo matches ./po/da.po:"Last-Translator: Michael Rasmussen <[EMAIL PROTECTED]>\n" Binary file ./po/da.gmo matches [EMAIL PROTECTED]:/usr/src/conglomerate $ I knew the name was familiar to me :-) > > What is the color of the blank screen?(black? blue? other?) > Black. Acknowledge > > What is the last text you have seen? > > > The last text seen is PXE boot's notification that it loads initrd. When > changing the PXE boot to use the onboard net interface the kernel starts > loading after this message. My asumption is that for some reason the > kernel never starts loading. Acknowledge > > Hard to tell. > > You are very terse with your information. > > Provide us with more details. > What information is needed? Motherboard, net devices etc. The installer > never starts so it is hard to now what goes wrong. I agree on that, so the Subject of the thread is wrong. Networkbooting works for debian-installer, even on x86. It should also work for you. Make sure that the network boot setup on the install client and the kernel that you use can work together. Rereading: > The last text seen is PXE boot's notification that it loads initrd. When > changing the PXE boot to use the onboard net interface the kernel starts > loading after this message. My asumption is that for some reason the > kernel never starts loading. I think reading the fantastic manual will help, if not ask smart questions at the mailinglist. Cheers Geert Stappers signature.asc Description: Digital signature
Re: bug in Sarge Debian Installer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 12 December 2004 11:37, Michael Rasmussen wrote: > I have discovered a bug in the new Debian Installer. The bug is when > using PXE boot install and having an onboard network interface in the > computer and a second (pci-)network interface. When you want to install > via pxe boot on the added network interface, that is not the onboard, > all goes fine until the point where the fetch kernel should load. At > this point the computer simple hangs with a blank screen as a result. > Disabling the onboard controller does not solve the problem. I very much doubt this is an installer problem, as the installer is not yet running at that time. It could either be a problem in your bios with regard to PXE booting or something in the way the files to be fetched are set up on the tftp server (which would kind of make it an installation media problem). We do know that some architectures don't seem to like some tftp servers, so you could try switching your tftp server. atftpd and tftpd-hpa seem to work for i386. I have not seen reports of this problem before. I guess your best bet is try to solve it yourself and let us know if you find a solution. One option for debugging this is looking at the packages sent over the network using a sniffer. Cheers, FJP -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBvD9Xgm/Kwh6ICoQRAv8LAJ9YdknCB6pm+wsAZBdTyaOha8IXMQCgzARU O2+yte496c0+1reCT3xNit0= =Aiaf -END PGP SIGNATURE-
[Fwd: Re: bug in Sarge Debian Installer]
Videresendt besked > Fra: Michael Rasmussen <[EMAIL PROTECTED]> > Til: Geert Stappers <[EMAIL PROTECTED]> > Emne: Re: bug in Sarge Debian Installer > Dato: Sun, 12 Dec 2004 13:26:25 +0100 > søn, 12 12 2004 kl. 13:12 +0100, skrev Geert Stappers: > > > What is the color of the blank screen?(black? blue? other?) > Black. > > What is the last text you have seen? > > > The last text seen is PXE boot's notification that it loads initrd. When > changing the PXE boot to use the onboard net interface the kernel starts > loading after this message. My asumption is that for some reason the > kernel never starts loading. > > > Hard to tell. > > You are very terse with your information. > > Provide us with more details. > What information is needed? Motherboard, net devices etc. The installer > never starts so it is hard to now what goes wrong. > > Hilsen/Regards > Michael Rasmussen > > Get my public GnuPG keys: > michael rasmussen cc > http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xD3C9A00E > mir datanom net > http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xE501F51C > mir miras org > http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xE3E80917 > -- > You two ought to be more careful--your love could drag on for years and > years. > > Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xE3E80917 -- You two ought to be more careful--your love could drag on for years and years. signature.asc Description: Dette er en digitalt underskrevet brevdel
Re: bug in Sarge Debian Installer
On Sun, Dec 12, 2004 at 11:37:57AM +0100, Michael Rasmussen wrote: > Hi all, Hello Michael, > I have discovered a bug in the new Debian Installer. The bug is when > using PXE boot install and having an onboard network interface in the > computer and a second (pci-)network interface. When you want to install > via pxe boot on the added network interface, that is not the onboard, > all goes fine until the point where the fetch kernel should load. At > this point the computer simple hangs with a blank screen as a result. > Disabling the onboard controller does not solve the problem. What is the color of the blank screen?(black? blue? other?) What is the last text you have seen? > Has this problem been reported by others? Hard to tell. You are very terse with your information. Provide us with more details. And there is the Debian Bug Tracking System ( BTS ) See http://bugs.debian.org/ for more information. Cheers Geert Stappers signature.asc Description: Digital signature
