Re: modload
- From: "Kalyan Manchikanti" <kalyan.manchikanti@xxxxxxxxx>
- Date: 25 Mar 2007 09:53:09 -0700
On Mar 24, 11:56 pm, Mikail Dellovich <f...@xxxxxxx> wrote:
Andrew Gabriel wrote:
In article <130at888dcf2...@xxxxxxxxxxxxxxxxxx>,
Mikail Dellovich <f...@xxxxxxx> writes:
I pkgadd installed a couple of drivers in the /kernel/drv/sparcv9
directory. But I noticed that they seem to autoload only on the first
reboot. Any subsequent reboot necessitates that you manually call
modload ... to load said drivers. Why did it load automatically on the
first reboot and not on subsequent ones. Where can I tell the kernel to
load them automatically if they are sitting in the /kernel/drv/sparcv9
directory?
Solaris only loads drivers when they are first used. After driver
installation, a flag is set (/reconfigure) to force all drivers
to load to enumerate their hardware, which results in /devices
and /dev being updated. In more recent Solaris versions (can't
recall if that includes Solaris 9), all unused drivers are
unloaded after the hardware enumeration. So this would explain
why your driver was loaded on the next reboot, although it might
have been unloaded (providing it was correctly written to be
unloadable) immediately afterwards. In the absence of reconfiguration
at boot time, drivers are not loaded until they are first used.
Why do you want the driver loaded when you are using it?
The kernel will also unload all drivers which are not being used
when it gets low on memory.
The funny thing is that if I do a touch /reconfigure before reboot the
drivers will load fine all the time after reboot and work with the
asterisk application!
The drivers were taken fromhttp://www.solarisvoip.com/.. Zaptel and
Ztdummy drivers.
They were built on Solaris 10.
I am tying to load them on Solaris 9. On solaris 10 is works fine in
terms of loading when called by the application.
In Solaris 9
But if I just issue:
modload /kernel/drv/sparcv9/zaptel
modload /kernel/drv/sparcv9/ztdummy
add_drv zaptel
add_drv ztdummy
in a script in /etc/rc2.d/
it will not work properly.
Modinfo shows them to be loaded but asterisk the application doesn't
seem to work as follows:
Mar 24 23:54:35 WARNING[287]: chan_zap.c:1064 zt_open: Unable to open
'/dev/zap/pseudo': No such device or address
Mar 24 23:54:35 ERROR[287]: chan_zap.c:7551 chandup: Unable to dup
channel: No such device or address
Mar 24 23:54:35 WARNING[287]: app_meetme.c:464 build_conf: Unable to
open pseudo channel - trying device
Mar 24 23:54:35 WARNING[287]: app_meetme.c:467 build_conf: Unable to
open pseudo device
xxnew-host:0:05:/> file /kernel/drv/sparcv9/zaptel
/kernel/drv/sparcv9/zaptel: ELF 64-bit MSB relocatable SPARCV9 Version 1
xxnew-host:0:05:/> file /kernel/drv/sparcv9/ztdummy
/kernel/drv/sparcv9/ztdummy: ELF 64-bit MSB relocatable SPARCV9 Version 1
Is there some other way to force load them even though touch
/reconfigure will pre-load them in a way that will work?
Thanks
Try putting a line like this in in your /etc/system ( make a backup
before the change) and reboot..
forceload: drv/sparcv9/<youdrivername>
.
- Follow-Ups:
- Re: modload
- From: Mikail Dellovich
- Re: modload
- References:
- modload
- From: Mikail Dellovich
- Re: modload
- From: Andrew Gabriel
- Re: modload
- From: Mikail Dellovich
- modload
- Prev by Date: Re: Best way to modify SMF service script?
- Next by Date: disks mountable under both Solaris9 and Solaris10?
- Previous by thread: Re: modload
- Next by thread: Re: modload
- Index(es):
Relevant Pages
|
