|Summary:||ugly behaviour of the installer|
|Product:||[Retired] Red Hat Linux||Reporter:||duzhin|
|Component:||installer||Assignee:||Jay Turner <jturner>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||1999-11-02 16:24:45 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description duzhin 1999-11-01 23:52:04 UTC
I boot Linux from the diskette with boot.img. When I begin the installation, at a certain moment I see an ugly message appearing behind the menu window across two lines. It looks something like: ************** **************p/ncr53c8xx.o init_ module: D************** ************** where the stars are for the menu window. The installation process can be continued, however, but then the installer does not give me the chance to override the default swap file size (I have a machine with 768M memory, and I am not satisfied with 64M swap). I tried the installer in different modes with the same result. The machine is a new (off the box) Compaq Deskpro with Corega FastetherII PCI-TX network card. I was installing from its hard drive, Win98 partition. P.S. I never had any problems of this kind with the previous version of RedHat (6.0). Then, the installation took about 1 hour, including copying the RPMS and base files from the Internet. The RedHat 6.0 PC works perfectly since then.
Comment 1 Jay Turner 1999-11-02 16:24:59 UTC
The only install methods which default a swap partition size are the Server and the two Workstation installations, but both of these can be overridden with the manual partition selection. The custom installation does not default any partition sizes, but rather will just list the existing partitions. If you do not like the size of the partitions which already exist on the drive, then you must remove those partitions and create new ones which are of the appropriate size. As for the message which is appearing on the screen, it looks like the installer is trying to load the NCR SCSI module when there is not actually one in your system. You are right that it should really not affect anything, but it is pretty ugly. The only way around it is to install the machine in custom mode, which will allow you to specify the modules which get loaded. Reopen this bug if you are still seeing problems with the installation.