You are installing via floppy, I'm installing via CD. You can easily change your boot image, I can't unless I were using RW, but I'm using R right now. :) Right now CD is easier than floppy for me. Kickstart does not work according to the docs for getting the ks.cfg file via HTTP. On try #1 I had accidentally put "ks=http://x.x.x.x/ks.cfg"; and that resulted in "GET /./ks.cfg HTTP/1.1". I re-read the docs and it says to use "ks=http:server.example.com:/mydir/ks.cfg" so I tried that and instead got nothing at the http server. In the 3rd console I see ks location: http:/192.168.1.2:/ks.cfg transferring http://192.168.1.2://.ks.cfg to a fd failed to retrieve http://192.168.1.2:/ks.cfg Any ideas? Seems like both the code and the docs are wrong in this case. -Chad- On Fri, 2002-04-26 at 17:26, secroft wrote: > This is a copy of my syslinux.cfg in which I don't have to type anything, > and my ks.cfg follows that. Obviously the xxx.xxx.xxx.xxx would be an IP, > but I don't think our info security people would like me to post that > information, even with a firewall. :) > > > default ks > prompt 1 > timeout 10 > display boot.msg > F1 boot.msg > F2 general.msg > F3 expert.msg > F4 param.msg > F5 rescue.msg > label linux > kernel vmlinuz > append initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 vga=788 > label text > kernel vmlinuz > append initrd=initrd.img lang= text devfs=nomount ramdisk_size=7168 > label expert > kernel vmlinuz > append expert initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 > label ks > kernel vmlinuz > append ks=floppy initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 > label nofb > kernel vmlinuz > append initrd=initrd.img lang= devfs=nomount nofb ramdisk_size=7168 > label lowres > kernel vmlinuz > append initrd=initrd.img lang= lowres devfs=nomount ramdisk_size=7168 > > > ks.cfg: > > lang en_US > langsupport en_US > keyboard us > mouse msintellips/2 > timezone --utc America/Boise > rootpw --iscrypted $1$7XÝÿ3Nîe$cER1a8pbhvG1dYpjlMW93/ > reboot > text > bootloader --useLilo > install > nfs --server kick-pin.micron.com --dir /kickstart > network --bootproto static --ip xxx.xxx.xxx.xxx --netmask xxx.xxx.xxx.xxx > --gateway xxx.xxx.xxx.xxx --nameserver xxx.xxx.xxx.xxx > auth --useshadow --enablemd5 > firewall --disabled > clearpart --linux > part /boot --fstype ext2 --size=51 > part /usr --fstype ext2 --size=3072 > part /var --fstype ext2 --size=3048 > part /opt --fstype ext2 --size=2048 > part / --fstype ext2 --size=1024 > part swap --size=2048 > part /tmp --fstype ext2 --size=2048 > > #Do not configure the X Window System > skipx > %packages > @Printing Support > @Network Support > @NFS File Server > @Anonymous FTP Server > @Network Managed Workstation > @Emacs > @Utilities > @Legacy Application Support > @Software Development > @Kernel Development > libcap > ntp > %post > /bin/mkdir /mnt/tmp > /bin/mount -o nolock xxx.xxx.xxx.xxx:/export/local-lnx/install /mnt/tmp > /bin/rpm -i /mnt/tmp/nis-utils-1.4.1-0.i386.rpm > /bin/rpm -i /mnt/tmp/pam_unix2-1.7-0.i386.rpm > /bin/rpm -Uvh --force /mnt/tmp/e1000-3.1.23-1.src.rpm > /bin/mkdir /root/download > /bin/cp /mnt/tmp/system-auth /etc/pam.d/. > /bin/cp /mnt/tmp/login /etc/pam.d/. > /bin/cp /mnt/tmp/ssh_config /etc/ssh/. > /bin/cp /mnt/tmp/sshd_config /etc/ssh/. > /bin/cp /mnt/tmp/sendmail.cf /etc/. > /bin/cp /mnt/tmp/nsswitch.conf /etc/. > /bin/cp /mnt/tmp/resolv.conf /etc/. > /bin/cp /mnt/tmp/syslog.conf /etc/. > /bin/cp /mnt/tmp/nisplus /etc/init.d/. > /bin/cp /mnt/tmp/ntp.conf /etc/. > /bin/cp /mnt/tmp/defaultdomain /etc/. > /bin/cp /mnt/tmp/motd /etc/. > /bin/cp /mnt/tmp/securetty /etc/. > echo "NISDOMAIN=micron.com" >> /etc/sysconfig/network > /bin/rm -rf /dev/cosole > /bin/rm -rf /dev/tty0 > /bin/mknod -m 622 /dev/console c 5 1 > /bin/mknod -m 622 /dev/tty0 c 4 0 > /bin/cp /mnt/tmp/lilo.conf /etc/. > /sbin/lilo > /bin/cp /mnt/tmp/inittab /etc/. > /sbin/chkconfig --level 2345 ntpd on > /bin/ln -s /etc/init.d/nisplus /etc/rc2.d/S99nisplus > /bin/ln -s /etc/init.d/nisplus /etc/rc3.d/S99nisplus > /bin/ln -s /etc/init.d/nisplus /etc/rc4.d/S99nisplus > > -----Original Message----- > From: Chad M. Stewart [mailto:cms@xxxxxxxxxx] > Sent: Friday, April 26, 2002 3:14 PM > To: kickstart-list@xxxxxxxxxx > Subject: Re: insmod (path is null) > > > > Thank you Scott, putting the module in /tmp of the ram disk worked, the > module can be loaded. Though I was still prompted to select this from a > list. Anyone know how to make the installer automatically load the > right module? I'm trying for a completely automatic installation, no > humans, no keyboard, this is a must! > > > > -Chad- > > > On Thu, 2002-04-25 at 23:23, Scott Croft wrote: > > There was a hint about the e1000.o module in another thread that you > > might try. > > Take the module and place it in the /tmp directory within the initrd.img > > file. I did the same as mentioned in the other thread and it solved my > > issues. If you run into a space issue on the disk after re-building the > > initrd.img then remove unneeded files, create another img filesystem > > that is smaller with dd, and put the data in that image file. > > > > As a side note, I have edited the ks.cfg file on a non-linux, non-pc > > system, and a pc. Once I touched the file with something non-linux, it > > ceased to function. I intentionally tried it with both after noticing > > issues and asking Jeremy about it. > > > > Scott > > > > > > On Thu, 2002-04-25 at 19:58, Chad M. Stewart wrote: > > > > > > I'm moving one step at time to my fully automatic install. > > > > > > I added the 8139too.o module from the 2.4.7-10BOOT kernel. I then > > > edited module-info. I did not add anything to pcitable. I looked but > > > did not see anything that looked similar for say a 3c5x9 ethernet card. > > > > > > I then created a bootable cdrom using this new image. It boots, > > > /sbin/loader gets run, and then I get a screen asking for me to chose a > > > ethernet interface, I can see the text I added, I select that and then > > > get "Failed to insert 8139too module." If I switch to virtual console > > > 3 I see "going to insmod 8139too.o (path is null)" > > > > > > I double checked the ISO image to be sure that the 8139too.o file is > > > actually in modules.cgz and it is. > > > > > > Two questions > > > > > > Any idea how to fix the path is null problem? > > > > > > If the above is solved will I still be prompted to select my NIC? My > > > goal is to have a NO KEYBOARD required install. While selecting a NIC is > > > trival it does require human intervention and I'm trying very hard to > > > avoid that. :) Once the above is solved, if I'm still prompted to > > > select a NIC is there anyway to get around that? > > > > > > btw - Linux on the desktop ROCKS!! :) > > > > > > > > > Thanks, > > > Chad > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Kickstart-list mailing list > > > Kickstart-list@xxxxxxxxxx > > > https://listman.redhat.com/mailman/listinfo/kickstart-list > > > > > > > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list@xxxxxxxxxx > > https://listman.redhat.com/mailman/listinfo/kickstart-list > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list
