Sponsored Content
Full Discussion: Error F painit on bootup
Operating Systems SCO Error F painit on bootup Post 303015372 by jgt on Tuesday 3rd of April 2018 04:10:03 PM
Old 04-03-2018
I would suggest that you do one more thing since it appears that you will not be able to boot the system if the Axxon card fails.

Remove the driver, re-link the kernel and save it in /stand as unix.no_axxon, then re-install the driver.
If the card fails, or has to be removed, you can still get the system started by entering unix.no_axxon at the Boot: prompt.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Triple bootup

Hi guys, May I know how to install Solaris 8 in the way that I can triple boot it with my the other two OS: WIndows ME and Windows 2000 Pro. Can you all please kindly advise me on how to setup the triple boot process inorder to allow Windows ME to be the default OS when being ask to choose... (1 Reply)
Discussion started by: cia
1 Replies

2. Linux

Preventing a scan of the RAID during bootup

I have a RH 7.3 server that needs a restart today after putting a patch in place. The last time I rebooted this box was almost a year ago and when the uptime is quite long, Linux likes to check all the disks for errors, including the RAID. This adds almost 1.5Hrs to my bootup process:eek: . Does... (1 Reply)
Discussion started by: turbo90awd
1 Replies

3. UNIX for Advanced & Expert Users

bootup script

Hello there I need to run a script whenever i reboot or startup my HP-UX server. This script adds some routes to the route table, and it start third party aplications like "Star Manager". I thought i could do this simply putting the script in "/sbin/init.d, and a link to the script in... (7 Replies)
Discussion started by: vascobrito
7 Replies

4. UNIX for Dummies Questions & Answers

Bootup Error

Hi all The following error was displayed when a sco server (5.0.5) was booted. What should be done to overcome the problem. Replies appreciated. Bios 03.0 0130688 KB memory good 01 processor(s) in system remote console dialing on, please wait connect fail : modem off cpu clock... (6 Replies)
Discussion started by: raguramtgr
6 Replies

5. UNIX for Dummies Questions & Answers

Why not automatic bootup

Evry time I start up my mavhine ,have to type in unix at Boot : Is there a way unix should bootup automatically? Asif (2 Replies)
Discussion started by: asif iqbal
2 Replies

6. AIX

How to start ssh at bootup

Hi i installed ssh of version v 1.21 and my AIX is of 5.3. I want to start my ssh deamon at the startup can any one please help me out reg.. Thanks in advance.. (1 Reply)
Discussion started by: kmalla
1 Replies

7. AIX

File system not mounting at bootup

Hi, I've got a recent problem with 2 file systems on an AIX 5.3 server. The fs's are marked to auto mount at startup and do show as being mounted after a a restart however if you cd to the mount point and 'df -g .' it shows the fs hasn't actually mounted. $ mount |grep SQLT0001.0 ... (2 Replies)
Discussion started by: m223464
2 Replies

8. UNIX for Advanced & Expert Users

system slows after bootup for some time

Hi, I am using a Linux system running at run level 3. I am finding a wired problem, once the system boots, the system terminal slows down, I need to type the characters repeatedly to enter my login and password info. Also running any commands takes time, it stays in this condition for some... (1 Reply)
Discussion started by: cjjoy
1 Replies

9. UNIX for Dummies Questions & Answers

bootup sequence

What is the boot up sequence in UNIX? (2 Replies)
Discussion started by: karthi_g
2 Replies

10. Solaris

Sunfire X4600 Errors on Bootup

Hi Folks, Has anyone seen these errors on bootup. Mar 15 12:22:30 svc.startd: svc:/system/device/local:default: Method "/lib/svc/method/devices-local" failed due to signal SEGV.ht (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved. Configuring devices. ... (1 Reply)
Discussion started by: ESSTEAM
1 Replies
pcram(7D)							      Devices								 pcram(7D)

NAME
pcram - PCMCIA RAM memory card device driver SYNOPSIS
memory@<socket>/pcram@<technology>,0:c memory@<socket>/pcram@<technology>,0:c,raw DESCRIPTION
The PCMCIA RAM memory card device driver supports disk-like I/O access to any standard PCMCIA static random access memory (SRAM) card and dynamic random access memory (DRAM) card. The driver supports standard PCMCIA SRAM/DRAM cards that contain a Card Information Structure (CIS). RAM card densities in the 512Kilobytes to 64Mbyte range are supported. PRECONFIGURATION
If a PC card memory device is recognized, the pcram device driver is automatically loaded, the physical address allocated, and special files created (if they do not already exist). Known Problems and Limitations The Solaris pcmem driver is not capable of handling "combo" memory cards with multiple types of memory on them (for example, combined SRAM and nonvolatile FLASH). Inserting such a card into a system running the Solaris software may cause a system panic. Because the PC card memory device is designed as a pseudo-floppy diskette type, the only utility that can be used for formatting is fdfor- mat(1). CONFIGURATION
Configuration topics include initial installation and configuration, identifying an unrecognized device, special files, using PC card mem- ory devices, and hot-plugging. Initial Installation and Configuration 1. Install the Solaris software. 2. Boot the system. 3. Insert the card. Identifying an Unrecognized Device If you insert a memory device and it is not recognized (no special files created), use the prtconf command. 1. Become root. 2. Run the prtconf -D command to display the configuration recognized by the system. A recognized device will appear in the prtconf output. For example: # prtconf -D . . . pcic, instance #0 (driver name: pcic) . . . memory, instance #0 (driver name: pcmem) pcram, instance #0 (driver name: pcram) 3. If your memory device does not appear at the end of the prtconf output, it is not supported and cannot be used with the pcram driver. Special Files The special files created for PC card memory devices act like disks and have names in the form /dev/dsk/c#t#d#p# or /dev/dsk/c#t#d#s#. Abbreviations used in the names are: o c# Controller # o t# Card technology type #, defined as follows: 0 Null--no device 1 ROM 2 OTPROM (One Time PROM) 3 UV EPROM 4 EEPROM 5 Flash EPROM 6 SRAM 7 DRAM o d# Device region of type #, usually zero o p# fdisk partition # o s# Solaris slice # Note - A device name can be specified either by a partition name (p#) or a slice name (s#), but not both. Using PC Card Memory Devices Solaris recognizes a PC Card memory device automatically upon the card's insertion. If you do not want automatic handling of a PC card memory device, insert an entry for the device in /etc/vfstab and set the mount at boot field to no. See vfstab(4). PC Card memory devices do not need to have file systems on them, though typically, before using a new PC Card memory card, you will want to create a file system on it. DOS PCFS is the best format to use. (You can use virtually any file system format on a PC card memory card, but most other file system formats are platform-dependent, making them unsuitable for moving data between different types of machines. See "Using a PCMCIA Memory Card" in the OpenWindows Advanced User's Guide.) Note - If you want to redirect the output of a tar command (or dd or cpio) to a PC card memory device, first create a file system on the card, using the fdformat(1) command without arguments. The card must be reformatted before it can be written on again. Hot-Plugging If a memory card is removed while in use, the device driver returns errors until the memory card is inserted into the appropriate socket. Close and reopen the device with the card reinserted, and the memory card will work. o If you remove the card while in use as a file system, unmount the file system using the umount command. Then reinsert the card and remount the file system using the mount command. o If you remove the card and interrupt a tar or cpio process, stop the process, reinsert the card, and restart the process. FILES
/kernel/drv/pcram pcram driver /dev/dsk/cntndnsn block files /dev/rdsk/cntndnsn raw fileswhere: cn controller n tn technology type n 0x1ROM,0x2OTPROM,0x3EPROM, 0x4EEPROM,0x5FLASH,0x6SRAM, 0x7DRAM dn technology region in type n sn slice n SEE ALSO
fdformat(1), pcmcia(7D), dkio(7I), pcmem(7D) SunOS 5.11 2 Mar 2007 pcram(7D)
All times are GMT -4. The time now is 03:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy