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
VGA(4)							   BSD Kernel Interfaces Manual 						    VGA(4)

NAME
vga -- generic video card interface SYNOPSIS
options VESA options VESA_DEBUG=N options VGA_ALT_SEQACCESS options VGA_NO_FONT_LOADING options VGA_NO_MODE_CHANGE options VGA_SLOW_IOACCESS options VGA_WIDTH90 device vga In /boot/device.hints: hint.vga.0.at="isa" DESCRIPTION
The vga driver is a generic video card driver which provides access to video cards. This driver is required for the console driver syscons(4). The console driver will call the vga driver to manipulate video hardware (changing video modes, loading font, etc). The vga driver supports the standard video cards: MDA, CGA, EGA and VGA. In addition, the driver can utilize VESA BIOS extensions if the video card supports them. VESA support can either be statically included in the kernel or can be loaded as a separate module. In order to statically link the VESA support to the kernel, the VESA option (see below) must be defined in the kernel configuration file. The vesa module can be dynamically loaded into the kernel using kldload(8). DRIVER CONFIGURATION
Kernel Configuration Options The following kernel configuration options (see config(8)) can be used to control the vga driver. These options provide compatibility with certain VGA cards. VGA_ALT_SEQACCESS You may want to try this option if the mouse pointer is not drawn correctly or the font does not seem to be loaded properly on the VGA card. However, it may cause flicker on some systems. VGA_SLOW_IOACCESS Older VGA cards may require this option for proper operation. It makes the driver perform byte-wide I/O to VGA registers and slow down a little. VGA_WIDTH90 This option enables 90 column modes: 90x25, 90x30, 90x43, 90x50, 90x60. These modes are not always supported by the video card and the display. It is highly likely that LCD display cannot work with these modes. The following options add optional features to the driver. VESA Add VESA BIOS support to the driver. If the VGA card has the VESA BIOS extension 1.2 or later, this option will utilize the VESA BIOS service to switch to high resolution modes. VESA_DEBUG=N Set the VESA support debug level to N. The default value is zero, which suppresses all debugging output. The following options will remove some features from the vga driver and save kernel memory. VGA_NO_FONT_LOADING The vga driver can load software font to EGA and VGA cards. This option removes this feature. Note that if you use this option and still wish to use the mouse on the console then you must also use the SC_ALT_MOUSE_IMAGE option. See syscons(4). VGA_NO_MODE_CHANGE This option prevents the driver from changing video modes. EXAMPLES
Your kernel configuration should normally have: device vga And you need the following line in /boot/device.hints. hint.vga.0.at="isa" The following lines should be included in the kernel configuration file in order to enable the VESA BIOS Extension support. options VESA device vga If you do not want VESA support included in the kernel, but want to use occasionally, do not add the VESA option. And load the vesa module as desired: kldload vesa SEE ALSO
vgl(3), syscons(4), config(8), kldload(8), kldunload(8) STANDARDS
Video Electronics Standards Association, VESA BIOS Extension (VBE). HISTORY
The vga driver first appeared in FreeBSD 3.1. AUTHORS
The vga driver was written by Soren Schmidt <sos@FreeBSD.org> and Kazutaka Yokota <yokota@FreeBSD.org>. This manual page was written by Kazutaka Yokota. BSD
June 30, 1999 BSD
All times are GMT -4. The time now is 12:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy