Sponsored Content
Operating Systems SCO SCO 5.0.7 driver for HP SmartArray P410i Controller on Proliant DL380 G7? Post 303037257 by hicksd8 on Saturday 27th of July 2019 11:46:27 AM
Old 07-27-2019
This is where a USB floppy drive comes in really handy both to write the BTLD floppies on the Linux box and read them (as BTLD driver(s)) on installation.

Perhaps try to acquire, beg, borrow or steal one of those.
This User Gave Thanks to hicksd8 For This Post:
 

10 More Discussions You Might Find Interesting

1. SCO

ultra 320 scsi raid controller driver for sco 5.0.6

I am facing a problem to install sco 5.0.6 in Dell Power Edge SC1420 which raid controller is ultra 320 scsi raid controller . how/from where to download the ultra 320 scsi raid controller driver for sco 5.0.6. Plz help with any idea karzon (1 Reply)
Discussion started by: karzon
1 Replies

2. SCO

driver needed for hp smartarry p200i sas raid controller

recently we have purchased hp proliant ml350 g5 server and configured raid 5 with hp smartarray p200i sas controller.but i could not found any sas raid controller hp smartarry p200i driver for sco unix 5.0.7 :(.i searched on hp support site,but no use.any one can help. (3 Replies)
Discussion started by: prakrithi
3 Replies

3. UNIX for Dummies Questions & Answers

SCO Openserver 6.0 Insall on HP DL380 serverl

Trying to install Openserver 6.0 on this server which has an integrated Smart Array P400. Install halts with the message ....... "Incorrect Disk Partitioning .........................." I havent yet got to the "divvy" and disk partitioning section of the install section so I am... (2 Replies)
Discussion started by: farmacy
2 Replies

4. SCO

SCO 5.0.7 no root disk controller found error during install

I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd. I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies

5. SCO

Loading SCO 507 on HP ProLiant ML350 G6

This is my first load of SCO OpenServer v5.0.7 on a HP ProLiant ML350 G6. When it asks me to identify the source media it can't find it no matter how I respond. The SCO compatible page says it used the on board SATA DVD-ROM on Port 2 of the embedded SATA controller with "Legacy IDE emulation (as... (8 Replies)
Discussion started by: farmboy
8 Replies

6. SCO

Change Disk controller in SCO 6.0.0

So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller. First, I downloaded the megasas driver from SCO and installed it on the old system. Then I created a new Microlite Edge emergency boot cd with the new driver on it. I... (2 Replies)
Discussion started by: jgt
2 Replies

7. Debian

HP ProLiant DL380 G4 w/ Debian... If your familiar with this machine please help.

Hello, I have a few questions about this server. It has two CPU's 3.20 ghz / 800 mhz / 1MB L2 5120 MB RAM 6 hard disks on HP Smart Array 6i controller (36.4 GB Ultra320 SCSI HD each) RAID set to RAID 5 (5 discs) with one spare (6th disk) USB, 2 Ethernet ports, 1 ILO port, 1 SCSI port ... (2 Replies)
Discussion started by: Marcus Aurelius
2 Replies

8. SCO

Getting error sco unix 507 from cdrom:no controller for device you chosen

Installing SCO UNIX 507 on Dell Poweredge T610. It has no floppy so I downloaded the BTLD onto CD from SCO site to load without floppy drive. BTLD loads ok. when i get to the Media to be used, no matter what option i chose i get the error: No controller for device you have chosen. During bootup you... (9 Replies)
Discussion started by: romanglad112
9 Replies

9. SCO

How to change raid controller driver ? (hardware change)

Hello I'm trying to virtualize an instance of Sco Unix 5.0.5 in VirtualBox (called VM-A) , but sco I have problems set to launch with the new raid controller . The physical machine has a raid controller adaptec (alad driver) but VirtualBox uses buslogic (blc driver) What ... (3 Replies)
Discussion started by: flako
3 Replies

10. SCO

SCO OS 6 Driver for LSIL SAS1064E Raid Controller

Hi all, A client has an SCO OpenServer Server 6.0, that is running on an HP ProLiant Box and they lost the root password. Its equipped with a Doal-Core Intel Pentium Processor. They don't have any media or emergency disk anymore. I tried to boot with the CD Rom, then "Tools", then exit to... (7 Replies)
Discussion started by: thm2222
7 Replies
FD(4)							     Linux Programmer's Manual							     FD(4)

NAME
fd - floppy disk device CONFIGURATION
Floppy drives are block devices with major number 2. Typically they are owned by root.floppy (i.e., user root, group floppy) and have either mode 0660 (access checking via group membership) or mode 0666 (everybody has access). The minor numbers encode the device type, drive number, and controller number. For each device type (that is, combination of density and track count) there is a base minor number. To this base number, add the drive's number on its controller and 128 if the drive is on the secondary controller. In the following device tables, n represents the drive number. Warning: If you use formats with more tracks than supported by your drive, you may cause it mechanical damage. Trying once if more tracks than the usual 40/80 are supported should not damage it, but no warranty is given for that. If you are not sure, don't create device entries for those formats, so as to prevent their usage. Drive-independent device files which automatically detect the media format and capacity: Name Base minor # -------------------- fdn 0 5.25 inch double density device files: Name Capac. Cyl. Sect. Heads Base minor # ---------------------------------------------------------- fdnd360 360K 40 9 2 4 5.25 inch high density device files: Name Capac. Cyl. Sect. Heads Base minor # ---------------------------------------------------------- fdnh360 360K 40 9 2 20 fdnh410 410K 41 10 2 48 fdnh420 420K 42 10 2 64 fdnh720 720K 80 9 2 24 fdnh880 880K 80 11 2 80 fdnh1200 1200K 80 15 2 8 fdnh1440 1440K 80 18 2 40 fdnh1476 1476K 82 18 2 56 fdnh1494 1494K 83 18 2 72 fdnh1600 1600K 80 20 2 92 3.5 inch double density device files: Name Capac. Cyl. Sect. Heads Base minor # ---------------------------------------------------------- fdnD360 360K 80 9 1 12 fdnD720 720K 80 9 2 16 fdnD800 800K 80 10 2 120 fdnD1040 1040K 80 13 2 84 fdnD1120 1120K 80 14 2 88 3.5 inch high density device files: Name Capac. Cyl. Sect. Heads Base minor # ---------------------------------------------------------- fdnH360 360K 40 9 2 12 fdnH720 720K 80 9 2 16 fdnH820 820K 82 10 2 52 fdnH830 830K 83 10 2 68 fdnH1440 1440K 80 18 2 28 fdnH1600 1600K 80 20 2 124 fdnH1680 1680K 80 21 2 44 fdnH1722 1722K 82 21 2 60 fdnH1743 1743K 83 21 2 76 fdnH1760 1760K 80 22 2 96 fdnH1840 1840K 80 23 2 116 fdnH1920 1920K 80 24 2 100 3.5 inch extra density device files: Name Capac. Cyl. Sect. Heads Base minor # ---------------------------------------------------------- fdnE2880 2880K 80 36 2 32 fdnCompaQ 2880K 80 36 2 36 fdnE3200 3200K 80 40 2 104 fdnE3520 3520K 80 44 2 108 fdnE3840 3840K 80 48 2 112 DESCRIPTION
fd special files access the floppy disk drives in raw mode. The following ioctl(2) calls are supported by fd devices: FDCLRPRM clears the media information of a drive (geometry of disk in drive). FDSETPRM sets the media information of a drive. The media information will be lost when the media is changed. FDDEFPRM sets the media information of a drive (geometry of disk in drive). The media information will not be lost when the media is changed. This will disable autodetection. In order to reenable autodetection, you have to issue an FDCLRPRM. FDGETDRVTYP returns the type of a drive (name parameter). For formats which work in several drive types, FDGETDRVTYP returns a name which is appropriate for the oldest drive type which supports this format. FDFLUSH invalidates the buffer cache for the given drive. FDSETMAXERRS sets the error thresholds for reporting errors, aborting the operation, recalibrating, resetting, and reading sector by sector. FDSETMAXERRS gets the current error thresholds. FDGETDRVTYP gets the internal name of the drive. FDWERRORCLR clears the write error statistics. FDWERRORGET reads the write error statistics. These include the total number of write errors, the location and disk of the first write error, and the location and disk of the last write error. Disks are identified by a generation number which is incremented at (almost) each disk change. FDTWADDLE Switch the drive motor off for a few microseconds. This might be needed in order to access a disk whose sectors are too close together. FDSETDRVPRM sets various drive parameters. FDGETDRVPRM reads these parameters back. FDGETDRVSTAT gets the cached drive state (disk changed, write protected et al.) FDPOLLDRVSTAT polls the drive and return its state. FDGETFDCSTAT gets the floppy controller state. FDRESET resets the floppy controller under certain conditions. FDRAWCMD sends a raw command to the floppy controller. For more precise information, consult also the <linux/fd.h> and <linux/fdreg.h> include files, as well as the floppycontrol(1) manual page. FILES
/dev/fd* NOTES
The various formats permit reading and writing many types of disks. However, if a floppy is formatted with an inter-sector gap that is too small, performance may drop, to the point of needing a few seconds to access an entire track. To prevent this, use interleaved formats. It is not possible to read floppies which are formatted using GCR (group code recording), which is used by Apple II and Macintosh computers (800k disks). Reading floppies which are hard sectored (one hole per sector, with the index hole being a little skewed) is not supported. This used to be common with older 8-inch floppies. SEE ALSO
chown(1), floppycontrol(1), getfdprm(1), mknod(1), superformat(1), mount(8), setfdprm(8) COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2010-08-29 FD(4)
All times are GMT -4. The time now is 02:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy