12-24-2015
Sounds like a GRUB2 problem. Some sort of hardware initialization or incompatibility problem. Might be worth trying a later version of SLES.
10 More Discussions You Might Find Interesting
1. Solaris
Hey all,
I'm a newbie to iso files and I just downloaded
the 2 iso files for *cough* ms2003 R2 *cough*
trial software. After I downloaded the iso files
I just dragged them to my burn software gui
and sure enough it burned to dvd 2 iso files.
When I attempted to boot the image using VMware... (0 Replies)
Discussion started by: bdsffl
0 Replies
2. Filesystems, Disks and Memory
In our HP/Unix system, our master scsi drive was bootable and our mirrored drive was non-bootable. Are any of these alternatives possible:
1) Make the non-bootable scsi drive bootable? How?
2) Create a bootable scsi drive, then copy the mirrored data to the newly created scsi drive?
I seek... (1 Reply)
Discussion started by: bfisk
1 Replies
3. Linux
Hi everyone,
I want to run on VMWare the Linux XP 2010 Desktop 4.0.31 distro, Iīve downloaded the latest realese from its website (Trustverse Desktop 4.0 RC1 -build 31)-->http://www.linux-xp.com/desktop/download/.
Itīs 4.47 GB in size, but when I mount on an ISO software, the size is 2.75GB... (0 Replies)
Discussion started by: cgkmal
0 Replies
4. Linux
I just tried to run the command
kexec memtest86-4.0.iso
To boot into memtest86 using kexec.
This is the output:
Cannot determine the file type of memtest86-4.0.iso
How am I supposed to do this? (2 Replies)
Discussion started by: locoroco
2 Replies
5. Fedora
I need to boot the ultimate boot cd from an usb stick. Do I just copy the iso image to the usb key?
How do I make the usb stick bootable? (4 Replies)
Discussion started by: locoroco
4 Replies
6. Red Hat
Hi All,
I want to create kick start bootable ISO file. I have Centos 5.4 ISO and customized ks.cfg file. Now I need to recreate ISO with ks.cfg and content of existing ISO.
During installation, it automatically should pick the kick start file and need to proceed with the installation.
... (0 Replies)
Discussion started by: kalpeer
0 Replies
7. Red Hat
Hello Everyone,
Can anyone let me know how to make minimal boot.iso from rhl6 installation dvd iso image. I have a dvd image with me but i want to make just a minimal boot media. Somehow it is not shipped with dvd iso. I know we can download boot.iso from redhat site but is there any anyway we... (5 Replies)
Discussion started by: Rohit Bhanot
5 Replies
8. Red Hat
Hi All,
I have one query on creating bootable ISO.
I have installed Centos 5.6 and done few configuration changes which is needed for deploying my App. Later I have deployed my app. Now Centos is up and running in a dedicated box along with my app.
Now I want to create the... (3 Replies)
Discussion started by: kalpeer
3 Replies
9. Red Hat
Hi All
On one of my sandbox machine, I want to replace RHEL 6.2 to RHEL 7.3.
I am using both developer editions.
rhel-server-7.3-x86_64-dvd.iso ... This is what I have downloaded from
Red Hat Enterprise Linux Download | Red Hat Developers
My understanding is this file would work as a... (1 Reply)
Discussion started by: videsh77
1 Replies
10. UNIX for Beginners Questions & Answers
I have a .dmg file which was created from a disk consisting of two partitions. When I mount the dmg both partitions pop up, so I know the imaging worked properly. One partition is HFS+ and the other is FAT32.
So far, I've been unable to find a way to restore the dmg to a flash drive where both... (17 Replies)
Discussion started by: paulcristo
17 Replies
ACC(4) Kernel Interfaces Manual ACC(4)
NAME
acc - ACC LH/DH IMP interface
SYNOPSIS
/sys/conf/SYSTEM:
NACC 0 # ACC LH/DH ARPAnet IMP interface
PLI YES # LH/DH is connected to a PLI
DESCRIPTION
The acc device provides a Local Host/Distant Host interface to an IMP. It is normally used when participating in the DARPA Internet. The
controller itself is not accessible to users, but instead provides the hardware support to the IMP interface described in imp(4). When
configuring, the imp(NIMP) pseudo-device must also be included.
DIAGNOSTICS
acc%d: not alive. The initialization routine was entered even though the device did not autoconfigure. This indicates a system problem.
acc%d: can't initialize. Insufficient UNIBUS resources existed to initialize the device. This is likely to occur when the device is run
on a buffered data path on an 11/750 and other network interfaces are also configured to use buffered data paths, or when it is configured
to use buffered data paths on an 11/730 (which has none).
acc%d: imp doesn't respond, icsr=%b. The driver attempted to initialize the device, but the IMP failed to respond after 500 tries. Check
the cabling.
acc%d: stray xmit interrupt, csr=%b. An interrupt occurred when no output had previously been started.
acc%d: output error, ocsr=%b, icsr=%b. The device indicated a problem sending data on output.
acc%d: input error, csr=%b. The device indicated a problem receiving data on input.
acc%d: bad length=%d. An input operation resulted in a data transfer of less than 0 or more than 1008 bytes of data into memory (according
to the word count register). This should never happen as the maximum size of a host-IMP message is 1008 bytes.
3rd Berkeley Distribution July 26, 1987 ACC(4)