10 More Discussions You Might Find Interesting
1. Ubuntu
I cannot access or boot from my C drive. I'm running Zorin 9 and the drive is a Samsung SSD. The disk was encrypted on install, and that has not given me any problems before.
When I start the system it gets to the memory test page, and does not then load the password prompt, which it used to.... (1 Reply)
Discussion started by: David4321
1 Replies
2. Solaris
Hello Forum,
I'm really in a fix now,
I'm getting this error message now, seems like the boot block is damaged?
When I do probe-all the system freezes...
Can any one guide me as what to do next?
System is Solaris 8 running Open Boot PROM 4
System also does not have a cd/dvd rom drive...
... (17 Replies)
Discussion started by: br1an
17 Replies
3. Solaris
I installed a new hard drive completely blank.
sun blade 150
openboot 4.10.6
message:
Boot device: disk:a File and args:
Bad magic number in disk label
Can't open label package
Evaluating:
Can't open boot device (15 Replies)
Discussion started by: janiper
15 Replies
4. Solaris
Hello,
I am wondering which commend /file to check to find out what is the boot device?
regards
Ahmed
Egypt (1 Reply)
Discussion started by: ahmedamer12
1 Replies
5. Solaris
hi all:
I have a sun blade-1000 for labs only, with 73G hd loaded, which boot block installed on slice 0. I'm confused by setting "boot-device" value in obp, which my question as follow:
in ok mode, I got device alias like this:
disk0: /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@2,0
as I know the... (4 Replies)
Discussion started by: netshu
4 Replies
6. Solaris
I have a real emergency. I have a Sun Fire V240 UltraSparc server and am connected via the Serial Mgmnt Port with a Laptop. I have been building an Oracle database on it for the past couple months, not getting very far along with it , when suddenly, the system had a fatal crash. I've lost the... (2 Replies)
Discussion started by: mayewil
2 Replies
7. Solaris
Hi i need help pls ...
Server type sun fire 3800 I need to install solaris 9 .
When i boot the system i recieve the following :
System Controller 'sunfire3800':
Type 0 for Platform Shell
Type 1 for domain A console
Type 2 for domain B console
Type 3 for... (5 Replies)
Discussion started by: tt155
5 Replies
8. Solaris
I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies
9. UNIX for Dummies Questions & Answers
I watched this done a long time ago, but cannot find it anywhere. I need to alias the boot device "disk" to /sbus@7,0/QLGC,isp@0,10000/sd@c,0
I think I need to set "use-nvramrc?" to true, and then create an alias within the nvramrc to point disk to the boot disk, but this is the step I cannot... (3 Replies)
Discussion started by: 98_1LE
3 Replies
10. UNIX for Dummies Questions & Answers
I need to change the boot slice on a Sun box, more specifically the alias of "disk". When I do a printenv from the ok prompt, it lists "boot-device disk net", but when it boots, it is looking at the wrong slice on "disk" (3 Replies)
Discussion started by: 98_1LE
3 Replies
pcic(7D) pcic(7D)
NAME
pcic - Intel i82365SL PC Card Interface Controller
The Intel i82365SL PC Card interface controller provides one or more PCMCIA PC card sockets. The pcic driver implements a PCMCIA bus nexus
driver.
The driver provides basic support for the Intel 82365SL and compatible chips. The chips that have been tested are:
o Intel 82365SL
o Cirrus Logic PD6710/PD6720/PD6722
o Vadem VG365/VG465/VG468/VG469
o Toshiba PCIC and ToPIC
o Ricoh RF5C366
o Texas Instruments PCI1130/PCI1131/PCI1031
While most systems using one of the above chips will work, some systems will not be supported due to hardware designs options that may not
be software detectable. Note that systems with CardBus interfaces are only supported in the non-legacy mode. Systems that only initialize
the bridge to legacy mode and do not configure the PCI memory will not be supported.
Direct access to the PCMCIA hardware is not supported. All device access must be through the Card Services interface of the DDI.
PRECONFIGURE
o Install your add-in PC Card adapter prior to the Solaris installation.
o Some systems have their built-in PC Card adapter disabled by default. Enable it prior to Solaris installation.
o Requirements for a system depend on the combination of devices to be used. A typical two-socket system needs at least 8 Kbytes of
address space, 16 bytes of I/O space, and three free IRQs. Following are general guidelines:
+--------------+------------------------------------------------+
|Address space | At least 8 Kbytes are required with 4 Kbytes |
| | per socket in the 640K-1MB range (not neces- |
| | sarily contiguous); if there are three sock- |
| | ets, at least 12 Kbytes are needed. |
+--------------+------------------------------------------------+
|I/O space | At least 8 and preferably 16 bytes per socket. |
+--------------+------------------------------------------------+
|IRQs | One per socket, plus an IRQ for the pcic |
| | device driver itself. |
+--------------+------------------------------------------------+
CONFIGURATION
There is one driver configuration property defined in the pcic.conf file.
interrupt-priorities=11; This property must be defined and must not be modified from the default value.
Initial Installation and Configuration
To perform initial installation and configuration, do the following steps:
1. Consult the Configuration Assistant for address space, I/O space, and IRQs already used by system devices.
2. Insert the PC Card adapter.
3. Install the Solaris software.
4. Reboot the system.
Adding PC Card Support to a Previously Installed System
To add PC card support to a previously installed system, do the following:
1. Become root.
2. Do a reconfiguration reboot to reallocate resources:
# touch /reconfigure
# reboot
3. Insert the PC Card adapter and turn on the machine.
4. Boot the system so that the PC Card device driver begins running with the new resources allocated.
Allocating IRQs
To allocate the IRQs, do the following:
1. Boot with the Configuration Assistant so you can review the resource usage.
2. Select View/Edit Devices from the Device Tasks menu, and review the list of devices to see how many IRQs are being used. (There are 16
IRQs, from 0-15. Several IRQs are already assigned. For example, IRQ 3 is reserved for the second serial port, COM2, and IRQ 7 is
reserved for the parallel port.)
3. If your system has an unused COM2 or parallel port, delete the device to free the IRQ resource for a PC Card. To do this, select the
serial port device using IRQ 3 or the parallel port using IRQ 7, and choose Delete Device. Next, choose Continue to return to the
Device Tasks menu, then save the configuration.
4. Boot the Solaris software.
/kernel/drv/pcic pcic driver
/kernel/drv/pcic.conf pcic configuration file
pcmcia(7D), stp4020(7D)
20 Oct 2000 pcic(7D)