Sponsored Content
Homework and Emergencies Emergency UNIX and Linux Support Linux: passing parameters to kernel modules Post 302641419 by otheus on Wednesday 16th of May 2012 06:26:10 AM
Old 05-16-2012
FYI: the code snippet above is the Qlogic driver for Linux 2.6.x. Version 8.01.07, copyrighted 2007.
 

10 More Discussions You Might Find Interesting

1. HP-UX

Information about kernel modules

Hi all, what do kernel modules libaudit, klog and strlog do? Specifically I want to determine if it was possible for us to determine if kernel level auditing is enabled at all? regards (0 Replies)
Discussion started by: slash_blog
0 Replies

2. UNIX for Dummies Questions & Answers

Linux kernel module parameters

Hi, Does anyone know if it is possible to know the current value of a kernel module parameters after the module is loaded. Are the values of the parameters advertised at some /proc or /sys location ? The only thing I know is modinfo, that actually looks a the module .ko and gives a... (3 Replies)
Discussion started by: macL
3 Replies

3. Solaris

Which file is read by kernel to set its default system kernel parameters values?

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

4. UNIX for Advanced & Expert Users

Kernel Modules Not geting built

I installed in VM the Mandriva Linux with 2.6.27 kernel. But presently when I fire make the modules .ko does not get built. I get the following output on firing command in the kernel module folder. $ make Building first_driver.c ... make: Entering directory... (1 Reply)
Discussion started by: rupeshkp728
1 Replies

5. Programming

Debugging Linux Kernel Modules

I am aware of debugging linux applications using gdb and ddd. Now I have written a simple kernel module having init_module, exit _module and some functions for tasklets and workqueues. I want to debug these kernel modules like I used to debug applications setting breakpoints etc. How can I debug... (1 Reply)
Discussion started by: rupeshkp728
1 Replies

6. UNIX for Dummies Questions & Answers

Linux kernel modules makefiles doubts

This query is regarding the makefiles of linux kernel modules. I saw at some sites on net it is suggesting to include the following path: KERNEL_SOURCE := /usr/src/linux... while at some places it is askibg to include /lib/modules path: KERNEL_SOURCE := /lib/modules/2.6.27-7-generic/build... (0 Replies)
Discussion started by: rupeshkp728
0 Replies

7. Red Hat

Kernel parameters problem in Linux

please tell me the list of kernel parameters in RHEL 5.7 Because we've a requirement in one project. Also tell me the importance of eah kernel parameter if possible. ==Thanks in Advance==:):D (1 Reply)
Discussion started by: vamshigvk475
1 Replies

8. Hardware

Linux Kernel Modules

Hey everyone. I have a question, doing an lsmod gives me a list of all the loaded modules for my system. But how did they know to load? my /etc/modules files is empty, so how did these modules know to load themselves on boot time? If I were to take this hard drive to another computer with a... (6 Replies)
Discussion started by: Lost in Cyberia
6 Replies

9. Linux

Disable loading kernel modules

Hi, I am running CentOS 6.5 and I want to remove auto loading 8021q and garp modules, but there are no configure files in /etc/modprobe.d define bot modules. I even added both module names to /etc/modprobe.d/blacklist.conf, both of them are still loaded after the reboot. How can I disable... (2 Replies)
Discussion started by: hce
2 Replies

10. UNIX for Beginners Questions & Answers

Missing Modules After Compiling Kernel

I'm a little embarrassed after all these years I've never really successfully compiled my own kernel. I used this guide to make the following files: linux-headers-5.1.9_5.1.9-1_amd64.deb linux-image-5.1.9_5.1.9-1_amd64.deb linux-libc-dev_5.1.9-1_amd64.deb When I first booted into this... (4 Replies)
Discussion started by: Azrael
4 Replies
ISP(4)							   BSD Kernel Interfaces Manual 						    ISP(4)

NAME
isp -- Qlogic based SCSI and FibreChannel SCSI Host Adapters SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device scbus device isp Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): isp_load="YES" DESCRIPTION
This driver provides access to SCSI or FibreChannel devices. SCSI features include support for Ultra SCSI and wide mode transactions for SCSI, Ultra2 LVD (for the ISP1080 and ISP1280), and Ultra3 LVD (for the ISP12160). Fibre Channel support uses FCP SCSI profile for FibreChannel. and utilizes Class 3 and Class 2 connections (Qlogic 2100 is Class 3 only, minor patches to the Qlogic 2200 to force Class 2 mode). Support is available for Public and Private loops, and for point-to-point connec- tions (Qlogic 2200 only). The newer 2-Gigabit cards (2300, 2312, 2322) and 4-Gigabit (2422, 2432) are also supported. Command tagging is supported for all (in fact, FibreChannel requires tagging). Fabric support is enabled by default for other than 2100 cards. Fabric support for 2100 cards has been so problematic and these cards are so old now that it is just not worth your time to try it. FIRMWARE
Firmware is available if the ispfw(4) module is loaded during bootstrap (q.v.). It is strongly recommended that you use the firmware available from ispfw(4) as it is the most likely to have been tested with this driver. HARDWARE
Cards supported by the isp driver include: ISP1000 SBus Fast Wide, Ultra Fast Wide cards, Single Ended or Differential cards. ISP1020 Qlogic 1020 Fast Wide and Differential Fast Wide PCI cards. ISP1040 Qlogic 1040 Ultra Wide and Differential Ultra Wide PCI cards. Also known as the DEC KZPBA-CA (single ended) and KZPBA-CB (HVD differential). Qlogic 1240 Qlogic 1240 Dual Bus Ultra Wide and Differential Ultra Wide PCI cards. Qlogic 1020 Qlogic 1020 SCSI cards. Qlogic 1040 Qlogic 1040 Ultra SCSI cards. Qlogic 1080 Qlogic 1280 LVD Ultra2 Wide PCI cards. Qlogic 1280 Qlogic 1280 Dual Bus LVD Ultra2 Wide PCI cards. Qlogic 12160 Qlogic 12160 Dual Bus LVD Ultra3 Wide PCI cards. Qlogic 210X Qlogic 2100 and 2100A Copper and Optical Fibre Channel Arbitrated Loop (single, dual). Qlogic 220X Qlogic 2200 Copper and Optical Fibre Channel Arbitrated Loop PCI cards (single, dual, quad). Qlogic 2300 Qlogic 2300 Optical Fibre Channel PCI cards. Qlogic 2312 Qlogic 2312 Optical Fibre Channel PCI cards. Qlogic 234X Qlogic 234X Optical Fibre Channel PCI cards (2312 chipset, single and dual attach). Qlogic 2322 Qlogic 2322 Optical Fibre Channel PCIe cards. Qlogic 200 Dell Branded version of the QLogic 2312 Fibre Channel PCI cards. Qlogic 2422 Qlogic 2422 Optical Fibre Channel PCI cards (4 Gigabit) Qlogic 2432 Qlogic 2432 Optical Fibre Channel PCIe cards (4 Gigabit) CONFIGURATION OPTIONS
Target mode support may be enabled with the options ISP_TARGET_MODE option. BOOT OPTIONS
The following options are switchable by setting values in /boot/device.hints. They are: hint.isp.0.disable A hint value to disable driver in kernel. hint.isp.0.fwload_disable A hint value to disable loading of firmware ispfw(4). hint.isp.0.prefer_memmap A hint value to use PCI memory space instead of I/O space access for. hint.isp.0.prefer_iomap A hint value to use PCI I/O space instead of Memory space access for. hint.isp.0.ignore_nvram A hint value to ignore board NVRAM settings for. Otherwise use NVRAM settings. hint.isp.0.fullduplex A hint value to set full duplex mode. hint.isp.0.topology A hint value to select topology of connection. Supported values are: lport Prefer loopback and fallback to point to point. nport Prefer point to point and fallback to loopback. lport-only Loopback only. nport-only Point to point only. hint.isp.0.portwwn This should be the full 64 bit World Wide Port Name you would like to use, overriding the value in NVRAM for the card. hint.isp.0.nodewwn This should be the full 64 bit World Wide Node Name you would like to use, overriding the value in NVRAM for the card. hint.isp.0.iid A hint to override or set the Initiator ID or Loop ID. For Fibre Channel cards in Local Loop topologies it is strongly recommended that you set this value to non-zero. hint.isp.0.role A hint to define default role for isp instance (target, initiator, both). hint.isp.0.debug A hint value for a driver debug level (see the file /usr/src/sys/dev/isp/ispvar.h for the values. SYSCTL OPTIONS
dev.isp.N.loop_down_limit This value says how long to wait in seconds after loop has gone down before giving up and expiring all of the devices that were visi- ble. The default is 300 seconds (5 minutes). A separate (nonadjustable) timeout is used when booting to not stop booting on lack of FC connectivity. dev.isp.N.gone_device_time This value says how long to wait for devices to reappear if they (temporarily) disappear due to loop or fabric events. While this timeout is running, I/O to those devices will simply be held. dev.isp.N.wwnn This is the readonly World Wide Node Name value for this port. dev.isp.N.wwpn This is the readonly World Wide Port Name value for this port. SEE ALSO
da(4), intro(4), ispfw(4), sa(4), scsi(4), gmultipath(8) AUTHORS
The isp driver was written by Matthew Jacob originally for NetBSD at NASA/Ames Research Center. BUGS
The driver currently ignores some NVRAM settings. Target mode support is not completely reliable yet. It works reasonably well for Fibre Channel, somewhat well for Qlogic 1040 cards, but does not yet work for the other cards (due to last minute unannounced changes in firmware interfaces). BSD
February 28, 2007 BSD
All times are GMT -4. The time now is 05:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy