9 More Discussions You Might Find Interesting
1. Linux
Hi everyone,
I am trying to prevent the ehci_hcd kernel module to load at boot time.
Here's what I've tried so far:
1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here):
2) Blacklisted the module by adding the following string to
3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
2. Solaris
Hi gurus
Could anybody tell me which file is read by kernel to set its default system kernal parameters values in solaris. Here I am not taking about /etc/system file which is used to load kernal modules or to change any default system kernal parameter value
Is it /dev/kmem file or something... (1 Reply)
Discussion started by: girish.batra
1 Replies
3. Linux
supermicro(dual core) server getting rebooted after "decompressing the kernel;booting the kernel" message comes.
I tried giving acpi=off to the kernel command line but same problem.It shows everything ok and no problem with memory and processors and power supplies.Wt could be the reason?
It has... (1 Reply)
Discussion started by: pankajd
1 Replies
4. AIX
Hello there:
I know that exist a procedure to convert an OS using 32bits kernel to 64 bits kernel. But, exist a procedure to convert an OS using 64bits to 32 bits kernel?
Please help me.
Regards. (2 Replies)
Discussion started by: GEIER
2 Replies
5. AIX
Hi,
I've got a IBM RS6000 with AIX 4.43 running with several networkcards. During a system restore somehow one of the networkcards doesn't connect.
I've been trying to troubleshoot the problem but I have no idea where to start. Am I right that the ENT# devices are the physicle NIC's? What are... (3 Replies)
Discussion started by: eRJe
3 Replies
6. SuSE
Hi All,
Is there a max number of slabs that can be used per kernel module? I'm having a tough time finding out that kind of information, but the array 'node_zonelists' (mmzone.h) has a size of 5. I just want to avoid buffer overruns and other bad stuff.
Cheers,
Brendan (4 Replies)
Discussion started by: Brendan Kennedy
4 Replies
7. Programming
hi all!
i have developed a mechanism in system.c to count how many times each kernel call is called. The results are held in an array in system.c . What i want to do is to create a new kernel call which will print this array. I need help in passing the array from system.c to the new kernel call. ... (5 Replies)
Discussion started by: aureliano
5 Replies
8. Linux
ok so I just installed fedora core 6 on my dell inspiron 700m and I go to boot into linux and I get this error. Has anyone seen this before?
I also had XP Pro and Vista installed on this pc prior to putting fedora core 6 on the machine. I'm trying to setup a triple boot system.
Please Help... (2 Replies)
Discussion started by: dave043
2 Replies
9. Solaris
Hi,
I am a beginner to Solaris. I installed it on a AMD Athlon 2000+, dual booting with XP. When I installed it, I didn't setup the network section and went on to install it without the n/w config. Now I have ethernet access at my school, and wanted to be able to connect to the internet through... (1 Reply)
Discussion started by: init-5
1 Replies
LEARN ABOUT SUSE
sg_map26
SG_MAP26(8) SG3_UTILS SG_MAP26(8)
NAME
sg_map26 - maps a special file to a SCSI generic (sg) device (or vice versa)
SYNOPSIS
sg_map26 [--dev_dir=DIR] [--given_is=0|1] [--help] [--result=0|1|2|3] [--symlink] [--verbose] [--version] DEVICE
DESCRIPTION
Maps a special file (block or char) associated with a SCSI device to the corresponding SCSI generic (sg) device, or vice versa. Can also
be given a sysfs file, for example '/sys/block/sda' or '/sys/block/sda/dev'.
Rather than map to or from a sg device, the sysfs file name matching a given device special file (or vice versa) can be requested. This is
done with '--result=2' and '--result=3'. This feature works on ATA devices (e.g. 'dev/hdc') as well as SCSI devices.
In this utility, "mapped" refers to finding the relationship between a SCSI generic (sg) node and the higher level SCSI device name; or
vice versa. For example '/dev/sg0' may "map" to '/dev/sda'. Mappings may not exist, if a relevant module is not loaded, for example. Also
there are SCSI devices that can only be accessed via a sg node (e.g. SAF-TE and some SES devices).
In this utility, "matching" refers to different representations of the same device accessed via the same driver. For example, '/dev/hdc'
and '/sys/block/hdc' usually refer to the same device and thus would be considered matching. A related example is that '/dev/cdrom' and
'/dev/hdc' are also considered matching if '/dev/cdrom' is a symlink to '/dev/hdc'.
OPTIONS
Arguments to long options are mandatory for short options as well.
-d, --dev_dir=DIR
where DIR is the directory to search for resultant device special files in (or symlinks to same). Only active when '--result=0' (the
default) or '--result=2'. If this option is not given and DEVICE is a device special file then the directory part of DEVICE is
assumed. If this option is not given and DEVICE is a sysfs name, then if necessary '/dev' is assumed as the directory.
-g, --given_is=0 | 1
specifies the DEVICE is either a device special file (when the argument is 0), or a sysfs 'dev' file (when the argument is 1). The
parent directory of a sysfs 'dev' file is also accepted (e.g. either '/sys/block/sda/dev' or '/sys/block/sda' are accepted). Usu-
ally there is no need to give this option since this utility first checks for special files (or symlinks to special files) and if
not, assumes it has been given a sysfs 'dev' file (or its parent). Generates an error if given and disagrees with variety of DEVICE.
-h, --help
output the usage message then exit.
-r, --result=0 | 1 | 2 | 3
specifies what variety of file (or files) that this utility tries to find. The default is a "mapped" device special file, when the
argument is 0. When the argument is 1, this utility tries to find the "mapped" sysfs node name. When the argument is 2, this util-
ity tries to find the "matching" device special file. When the argument is 3, this utility tries to find the "matching" sysfs node
name.
-s, --symlink
when a device special file is being sought (i.e. when '--result=0' (the default) or '--result=2') then also look for symlinks to
that device special file in the same directory.
-v, --verbose
increase the level of verbosity, (i.e. debug output).
-V, --version
print the version string and then exit.
NOTES
This utility is designed for the linux 2.6 kernel series. It uses special file major and minor numbers (and whether the special is block or
character) together with sysfs to do its mapping or matching. In the absence of any other information, device special files are assumed to
be in the '/dev' directory while sysfs is assumed to be mounted at '/sys'. Device names in sysfs are predictable, given the corresponding
major and minor number of the device. However, due to udev rules, the name of device special files can be anything the user desires (e.g.
'/dev/sda' could be named '/dev/my_boot_disk'). When trying to find a resultant device special file, this utility uses the major and minor
numbers (and whether a block or char device is sought) to search the device directory.
This utility only shows one relationship at a time. To get an overview of all SCSI devices, with special file names and optionally the
"mapped" sg device name, see the lsscsi utility.
EXAMPLES
Assume sg2 maps to sdb while dvd, cdrom and hdc are all matching.
# sg_map26 /dev/sg2
/dev/sdb
# sg_map26 /dev/sdb
/dev/sg2
# sg_map26 --result=0 /dev/sdb
/dev/sg2
# sg_map26 --result=3 /dev/sdb
/sys/block/sda
# sg_map26 --result=1 /dev/sdb
/sys/class/scsi_generic/sg0
Now look at '/dev/hdc' and friends
# sg_map26 /dev/hdc
<error: a hd device does not map to a sg device>
# sg_map26 --result=3 /dev/hdc
/sys/block/hdc
# sg_map26 --result=2 /dev/hdc
/dev/hdc
# sg_map26 --result=2 --symlink /dev/hdc
/dev/cdrom
/dev/dvd
/dev/hdc
# sg_map26 --result=2 --symlink /sys/block/hdc
/dev/cdrom
/dev/dvd
/dev/hdc
EXIT STATUS
The exit status of sg_map26 is 0 when it is successful. Otherwise see the sg3_utils(8) man page.
AUTHORS
Written by Douglas Gilbert.
REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>.
COPYRIGHT
Copyright (C) 2005-2007 Douglas Gilbert
This software is distributed under a FreeBSD license. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR-
POSE.
SEE ALSO
udev(8), udevinfo(8), lsscsi(lsscsi)
sg3_utils-1.23 January 2007 SG_MAP26(8)
