Re: Bug#139043: [ARM] Please mention conflict with "noinitrd" boot option

2002-03-24 Thread Ralph Siemsen
On Sat, Mar 23, 2002 at 08:14:36PM -0500, Rod Stewart wrote: > > Yup, you want your /etc/dhcpd.conf to look similar to the following. > Although the domain-name is ignored, and you most likely do not want > the routers part. The format for 'root-path' is NeTTrom specific. > > filename "vml

Re: Bug#139043: [ARM] Please mention conflict with "noinitrd" boot option

2002-03-23 Thread Rod Stewart
On Fri, 22 Mar 2002, Adam C Powell IV wrote: > >You probably do not want the 'netconfig_eth0 flash' set in the firmware > >with save-all. > > > Really? I haven't had it interfere with my setup with save-all. What > kinds of problems can it cause? Is it just that the network gets > configured t

Re: Bug#139043: [ARM] Please mention conflict with "noinitrd" boot option

2002-03-22 Thread Adam C Powell IV
Rod Stewart wrote: On Thu, 21 Mar 2002, Adam C Powell IV wrote: NeTTrom command-> setenv netconfig_eth0 flash NeTTrom command-> setenv kerntftpserver 192.168.0.1 NeTTrom command-> setenv kerntftpfile tftpboot.img NeTTrom command-> save-all NeTTrom command-> setenv kernconfig tftp Onl

Re: Bug#139043: [ARM] Please mention conflict with "noinitrd" boot option

2002-03-21 Thread Philip Blundell
On Thu, 2002-03-21 at 13:26, Adam C Powell IV wrote: > command to review your environment settings. Finally, if your > "cmdappend" NeTTrom variable has the "noinitrd" option (which is > necessary to boot 2.4 kernels), Is this actually still necessary with the latest 2.4 kernels? I thought it wa

Re: Bug#139043: [ARM] Please mention conflict with "noinitrd" boot option

2002-03-21 Thread Ralph Siemsen
On Thu, Mar 21, 2002 at 08:26:54AM -0500, Adam C Powell IV wrote: > > Only the last of these interferes with normal disk booting, so it is > safe to save-all right before it, which will store the network settings > in case you need to boot from the network again. Use the "printenv" > command to

Re: Bug#139043: [ARM] Please mention conflict with "noinitrd" boot option

2002-03-21 Thread Philip Blundell
On Thu, 2002-03-21 at 14:42, Rod Stewart wrote: > I thought you built the tulip as a module? Which would make it at least > fun if not impossible to boot off of, wouldn't it? Oh, wait, I was > thinking about also booting with and NFS root. Yes, you are right for the > Debian install it 'should'

Re: Bug#139043: [ARM] Please mention conflict with "noinitrd" boot option

2002-03-21 Thread Rod Stewart
On 21 Mar 2002, Philip Blundell wrote: > On Thu, 2002-03-21 at 14:21, Rod Stewart wrote: > > You must use eth0 (10-baseT) ne2k(piece of crap) for the tftpboot. > > Yes, it is possible to boot off eth1, but the Debian kernels do not > > support it, and you have to pass lots of parameters with c

Re: Bug#139043: [ARM] Please mention conflict with "noinitrd" boot option

2002-03-21 Thread Philip Blundell
On Thu, 2002-03-21 at 14:21, Rod Stewart wrote: > You must use eth0 (10-baseT) ne2k(piece of crap) for the tftpboot. > Yes, it is possible to boot off eth1, but the Debian kernels do not > support it, and you have to pass lots of parameters with cmdappend, it is > ugly. Eh? The kernel shoul

Re: Bug#139043: [ARM] Please mention conflict with "noinitrd" boot option

2002-03-21 Thread Rod Stewart
On Thu, 21 Mar 2002, Adam C Powell IV wrote: > Let's start with section 5.4, "Booting from TFTP," here's my suggestion: > > Booting from the network requires that you have a network connection > supported by the boot floppies, including either a static network > address or a DHCP server, and also

Re: Bug#139043: [ARM] Please mention conflict with "noinitrd" boot option

2002-03-21 Thread Adam C Powell IV
Chris Tillman wrote: On Tue, Mar 19, 2002 at 07:06:14AM -0500, Adam C Powell IV wrote: Package: boot-floppies Version: 3.0.10-2002-03-14 Greetings, Users of current netwinder 2.4 kernels must boot with option "noinitrd" in the cmdappend NeTTRom firmware variable. Unfortunately, this disables the