Sponsored Content
Full Discussion: Booting T5 from USB
Operating Systems Solaris Booting T5 from USB Post 302937151 by danish2012 on Wednesday 4th of March 2015 02:11:54 AM
Old 03-04-2015
did you used it on any other version of Solaris
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Booting

Hi all, I've managed to get Mandrake 9 installed by disconnecting my 2 windows' drives. When I reconnect them Mandrake wants to take over. I figure it's time for the BootManager, or should I use a Linux specific one like Lilo? Or have I already stuffed up by not running Lilo at time of... (2 Replies)
Discussion started by: onestepto
2 Replies

2. Linux

Booting Linux from an USB stick

I got Puppy linux and installed it on a usb stick. In the BIOS i selected to boot from USB-FDD but it goes to my HD and ignores the USB stick, What going on ?? (2 Replies)
Discussion started by: perleo
2 Replies

3. AIX

AIX not booting

ok so i have recently aquired an old Apple network server 700, its running AIX 4.1.4, i have virtually no experience in unix, it come up with "Can't open disk lebel package can't OPEN: /bandit/53c825@2,0:aix" i tried the maintinance mode with the AIX CD and i guess reinstalled, at least it... (1 Reply)
Discussion started by: Apo11o
1 Replies

4. UNIX for Dummies Questions & Answers

KNOPPIX CD not Booting

I have downloaded KNOPIIX and burned it on a CD, it niether boots from CD nor could I open the file, it seems the extension is .iso, would you mind sending me your comment,please. Thank you very much (2 Replies)
Discussion started by: amir
2 Replies

5. Linux

Problems booting RH 8

I installed RH8 on Thinkpad R51. The install went smooth, but when I tried to boot, it hanged at: PCI_IDE: unknown IDE controller on Pci bus 00 device f9, VID=8086, ID=24ca PCI: Device 00:1f.1 not available because of resource collisions. PCI_IDE: (ide_setup_pci_device:) could not enable... (0 Replies)
Discussion started by: etc
0 Replies

6. Solaris

booting from CD

Hello.. I am Still Learing Solaris .. when i try to Install Solaris 8 from its CD...i pressed STOP + A and i get a OK prompt screen. I then typed, "boot cdrom" and i am getting this error message. " FATAL: system is not bootable, boot command is disabled." How do we enable the boot... (5 Replies)
Discussion started by: vr76413
5 Replies

7. UNIX for Dummies Questions & Answers

Dual Booting

I first had windows xp 64-bit installed on my system, and then installed fedora 10 on a partition (partition was created while installing fedora). When installation was completed, I could not boot on Windows or Fedora, I keep on getting this disc error and system asking to press ctrl+alt+del to... (0 Replies)
Discussion started by: lucianvibz
0 Replies

8. UNIX for Dummies Questions & Answers

Booting different partitions on a usb drive with syslinux

Hello, I have an 8gb usb flash drive that I had high aspirations of using for a recovery/install/messing around multipurpose drive. fdisk shows: $ sudo fdisk -l /dev/sdb password for woodnt: Disk /dev/sdb: 8036 MB, 8036285952 bytes 255 heads, 63 sectors/track, 977 cylinders Units =... (0 Replies)
Discussion started by: Narnie
0 Replies

9. UNIX for Dummies Questions & Answers

USB-USB cable between linux and windows computers

Is there an easy way to setup a cross-over cable (USB-USB) between a linux box and a windows PC? My 2 machines are next to each other but I really do not want to keep transfering my files using my USB drive. Thanks! (4 Replies)
Discussion started by: Xterra
4 Replies
sane-find-scanner(1)					   SANE Scanner Access Now Easy 				      sane-find-scanner(1)

NAME
sane-find-scanner - find SCSI and USB scanners and their device files SYNOPSIS
sane-find-scanner [-h|-?] [-v] [-q] [-p] [-f] [-F filename] [devname] DESCRIPTION
sane-find-scanner is a command-line tool to find SCSI and USB scanners and determine their Unix device files. Its primary aim is to make sure that scanners can be detected by SANE backends. For SCSI scanners, it checks the default generic SCSI device files (e.g., /dev/sg0) and /dev/scanner. The test is done by sending a SCSI inquiry command and looking for a device type of "scanner" or "processor" (some old HP scanners seem to send "processor"). So sane-find-scanner will find any SCSI scanner connected to those default device files even if it isn't supported by any SANE backend. For USB scanners, first the USB kernel scanner device files (e.g. /dev/usb/scanner0), /dev/usb/scanner, and /dev/usbscanner) are tested. The files are opened and the vendor and device ids are determined, if the operating system supports this feature. Currently USB scanners are only found this way if they are supported by the Linux scanner module or the FreeBSD or OpenBSD uscanner driver. After that test, sane-find-scanner tries to scan for USB devices found by the USB library libusb (if available). There is no special USB class for scanners, so the heuristics used to distinguish scanners from other USB devices is not perfect. sane-find-scanner also tries to find out the type of USB chip used in the scanner. If detected, it will be printed after the vendor and product ids. sane-find-scanner will even find USB scan- ners, that are not supported by any SANE backend. sane-find-scanner won't find most parallel port scanners, or scanners connected to proprietary ports. Some parallel port scanners may be detected by sane-find-scanner -p. At the time of writing this will only detect Mustek parallel port scanners. OPTIONS
-h, -? Prints a short usage message. -v Verbose output. If used once, sane-find-scanner shows every device name and the test result. If used twice, SCSI inquiry informa- tion and the USB device descriptors are also printed. -q Be quiet. Print only the devices, no comments. -p Probe parallel port scanners. -f Force opening all explicitly given devices as SCSI and USB devices. That's useful if sane-find-scanner is wrong in determining the device type. -F filename filename is a file that contains USB descriptors in the format of /proc/bus/usb/devices as used by Linux. sane-find-scanner tries to identify the chipset(s) of all USB scanners found in such a file. This option is useful for developers when the output of "cat /proc/bus/usb/devices" is available but the scanner itself isn't. devname Test device file "devname". No other devices are checked if devname is given. EXAMPLE
sane-find-scanner -v Check all SCSI and USB devices for available scanners and print a line for every device file. sane-find-scanner /dev/scanner Look for a (SCSI) scanner only at /dev/scanner and print the result. sane-find-scanner -p Probe for parallel port scanners. SEE ALSO
sane(7), sane-scsi(5), sane-usb(5), scanimage(1), xscanimage(1), xsane(1), sane-"backendname"(5) AUTHOR
Oliver Rauch, Henning Meier-Geinitz and others SUPPORTED PLATFORMS
USB support is limited to Linux (kernel, libusb), FreeBSD (kernel, libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the vendor and device ids only works with Linux or libusb. SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris, FreeBSD, NetBSD, OpenBSD, and HP-UX. BUGS
No support for most parallel port scanners yet. Detection of USB chipsets is limited to a few chipsets. 13 Jul 2008 sane-find-scanner(1)
All times are GMT -4. The time now is 09:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy