Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 13124 - ls120: unconfigured
ls120: unconfigured
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Erik Troan
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2000-06-27 13:00 EDT by giulioo
Modified: 2007-04-18 12:27 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-07-13 12:54:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description giulioo 2000-06-27 13:00:04 EDT
This is a spin-off of #12188, which I've closed because I used a too 
generic summary, and it is now obsolete with beta2.

expert text install, because GUI just keeps rebooting my system.

During install:

probing for ide floppies
no ide floppy devices found

hda: IDE disk...
hdc: LS-120 VER5 00 UHD ...
hdd: cdrom.
ide0 ...
ide1 ...
hda: IDE disk
hdd: CDROM

that is, the ls120 is detected but the driver is not installed.

Normal boot:
1) there isn't any entry for ls120 in  /etc/fstab
2) module ide-floppy is not loaded
3) it works if I load manually ide-floppy
4) ugly messages when mounting the ls-120 (after having mke2fs on it):
hdc: unknown partition table
hdc: unknown partition table
it would be nice it those messages could go away :-)

class: FLOPPY
bus: IDE
detached: 0
device: hdc
driver: ignore
desc: "LS-120 VER5 00 UHD Floppy"
Comment 1 giulioo 2000-07-11 08:08:00 EDT
ls120 is still unconfigured in beta3.

Bugzilla is forcing me to change the component ("installer" seems gone).
So I'm choosing anaconda, even because this time I used the GUI install.
Comment 2 Michael Fulbright 2000-07-13 12:54:02 EDT
Fixed for next beta.

Note You need to log in before you can comment on or make changes to this bug.