Bug 62887
| Summary: | kickstart install fails with ks=hd:fd0/hostname.ks | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Public Beta | Reporter: | Alexandre Oliva <aoliva> | ||||
| Component: | anaconda | Assignee: | Jeremy Katz <katzj> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Brock Organ <borgan> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | skipjack-beta2 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2002-04-10 02:29:33 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 61901 | ||||||
| Attachments: |
|
||||||
|
Description
Alexandre Oliva
2002-04-07 05:07:21 UTC
This just worked for me with a kickstart config named ks.foo and booting with 'linux ks=hd:fd0/ks.foo'. Are there any error messages listed on tty3? Hmm... Perhaps there is only a problem in the case of the `dd'. This was booting off a bootnet.img floppy, btw. I didn't have virtual consoles at such an early stage to tell whether there were any messages there. Anyway, I'm confused as to why kickstart installation didn't work when I didn't use the driver disk. Perhaps it had trouble with network detection (it's an rtl8139 card, whose driver is not present in bootnet.img) and fell back to manual installation? 8139too is actually on bootnet, so you shouldn't need a driver disk. What did the kickstart config look like (mine didn't get to stage 2, but that's just because I specified a non-existent NFS path for it to mount :-) And you should have the different VCs at that point to look and get more information, tty3 just tends to scroll fast early :/ Hmm... I don't see it in modules.cgz in the initrd.img in bootnet.img. Curiously, mii.o is there, but 8139too depends on mii.o and, when the driver disk is loaded, is says it loads the mii module. Anyway, without the driver disk I could not get it to recognize the rtl8139 card and, as soon as I had the driver disk in, it worked fine. I'll attach the config file. Created attachment 52809 [details]
libero.ks
Oops, moved 8139too back to bootnet. Somehow had a couple of drivers migrate. I'll look into the other part shortly. Aha, I bet I know what's going on -- do you have the kickstart config on the boot floppy or the driver disk? The kickstart config is loaded after the driver disk, so it would need to be on the latter. Tried that too, it didn't help. But having the kickstart file in the boot floppy works, as long as it is named ks.cfg. There's probably some code supposed to save a copy of it in /tmp, but such code fails to take other names into account. I'd also guess it won't work if I try kickstart includes. %pre gets processed long after driver disks (it's not done until we get stage 2 loaded), so has very little effect for %include. I just did a test with the older tree where 8139too isn't on bootnet with 'linux dd ks=hd:fd0/ks.foo' and had it work properly loading the kickstart config off of the driver disk. Which, although a little odd, is correct as far as its always been. Were there any messages on tty3 about being unable to copy the file? Hmm... It worked this time. How odd... I was even more surprised because I couldn't find the kickstart file in the drivers disk. Perhaps I goofed and failed to unmount /mnt/floppy before removing it? I can't promise this didn't happen, unfortunately :-( Oh, well... At least I'm now happy cause I won't need the drivers disk for final :-) Sorry about the noise :-( |