Antonio,
Re: This brings up a question regarding the new /etc/modprobe.d/ directory
that is now become depracated?
----------
/etc/modprobe.d/ is not itself deprecated, to my understanding.
Rather there is being implemented a requirement that all files within
/etc/modprobe.d/ have an ending .conf
For example, here are the contents of my Ubuntu folder:
$ ls /etc/modprobe.d/
agrsm.conf blacklist.conf
blacklist-modem.conf dkms.conf
alsa-base.conf blacklist-firewire.conf blacklist-oss.conf
libpisock9.conf
blacklist-ath_pci.conf blacklist-framebuffer.conf blacklist-watchdog.conf
wherein agrsm.conf is just the rename of my older agrsm, facilitating
port creation and loading of agrmodem + agrserial upon:
$ modprobe agrserial.
MarvS
On Thu, Sep 24, 2009 at 7:28 PM, Antonio Olivares
<olivares14031@xxxxxxxxx> wrote:
> Marv & Manish,
>
> The output from scanModem reports that the agrsm-tools package does
> provide for autoloading?
>
> The agrsm-tools package supports driver autoloading, but does not itself
> contain drivers.
>
> This brings up a question regarding the new /etc/modprobe.d/ directory
> that is now become depracated? How is the driver to be loaded if not
> put directly in the /etc/modprobe.d/ directory?
>
> The only thing that I can come up with is a modified script for
> /etc/init.d/ and use of chkconfig and add it as a service with it.
> Something like
>
> #!/bin/sh
> #
> # agrsmd: Starts the agrsm-11c11040 Modem Daemon
> #
> # chkconfig: 345 90 10
> # description: This is the user space part of the
> 11c11040 agrsm Modem driver
>
> modprobe agrmodem
> modprobe agrserial
>
> if ! [[ -e /dev/modem ]] &> /dev/null; then
> {
> echo "Linking /dev/ttyAGS3 to /dev/modem to let kppp access modem"
> ln -s /dev/ttyAGS3 /dev/ttySAGR
> ln -s /dev/ttyAGS3 /dev/modem
> }
> fi
>
> # See how we were called.
> case "$1" in
> start)
> echo -n "Starting agrsm . . ."
> modprobe agrmodem
> modprobe agrserial
> echo "done"
> ;;
> stop)
> echo -n "Shutting down agrsm . . ."
> modprobe -r agrserial
> modprobe -r agrmodem
> echo "done"
> ;;
> status)
> ;;
> restart)
> $0 stop
> $0 start
> ;;
> *)
> echo "Usage: agrsm {start|stop|restart|status}"
> exit 1
> esac
>
> exit 0
>
> save it to agrsmd. Then copy this file over to /etc/rc.d/init.d or
> /etc/init.d/ folder and add it with chkconfig as superuser
> $ su -
> passwd:
> # cp agrsmd /etc/init.d/ or /etc/rc.d/init.d/
> # chkconfig agrsm --add
> then check to see if the links are created or not?
>
> [root@localhost init.d]# chkconfig agrsmd on
> [root@localhost init.d]# cd ..
> [root@localhost rc.d]# for i in 0 1 2 3 4 5 6
>
> and you should see some K00? and S00? stuff created with agrsmd.
>
> Modified a bit to match agrsm from slmodemd startup script found here.
>
> http://www20.brinkster.com/olivares/slmodemd-setup-1.html
>
> I do not know if this will actually work, but I did have some success
> with modified pctel scripts with chkconfig in Fedora. I hope that the
> script works but it comes with no warranty :( I know the script
> somehow works in Slax, but only Hugo confirmed that it works since I
> could not get the agrsm 11c1:0620 modem to work for me.
>
> Regards,
>
> Antonio
>
> On 9/24/09, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote:
>> Antonio,
>>
>> Would you provide Manish with instructions for driver loading on
>> RPM systems, using a /etc/init.d/ script.
>>
>> Manish
>>
>> Autoloading a bootup loading of winmodem drivers is NOT recommended.
>> While they may be working well now, after some future kernel update,
>> they could contribute to a crash during bootup. You would then need
>> to work with a Rescue Disk to recover functionality.
>>
>> If you have installed the agrsm-tools package, then
>> # modprobe agrserial
>> will setup all needed for subsequent dialout.
>>
>> If you want to take the RISKs of having them autoload,
>> then add lines to the file /etc/module
>> agrmodem
>> agrserial
>>
>> or somewhat more conservatively, write a loading script for /etc/init.d/
>>
>> Marvin
>>
>>
>> On Thu, Sep 24, 2009 at 12:19 AM, Manish Kalonia
>> <manishkalonia85@xxxxxxxxx> wrote:
>>> Hi Marvin,
>>>
>>> Thanks a lot for the help. The sound is working fine. I had to search
>>> for the dkms package from the suse webpage. But still I have to load the
>>> drivers after every restart. Is there any way that these drivers get
>>> loaded automatically instead of regular drivers.
>>>
>>> Anyways, thanks again for the help.
>>>
>>> Regards,
>>> Manish Kalonia
>>>
>>> On Tue, 2009-09-22 at 21:24 -0400, Marvin Stodolsky wrote:
>>>> Manish,
>>>>
>>>> For openSUSE 11.1 - Kernel Linux version 2.6.27.29-0.1-default and modem
>>>> Codec: LSI ID 1040
>>>> Vendor Id: 0x11c11040
>>>>
>>>> from http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ you
>>>> should first install SuSE's dkms package, then from
>>>> http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ , the
>>>> agrsm-tools-0.0.1-2.noarch.rpm , just a diagnostic helper
>>>> >From http://linux.zsolttech.com/linmodem/agrsm/Testing/ the code
>>>> package
>>>> dkms-agrsm-2.1.80-9mdv2009.0.i586.rpm
>>>>
>>>> These should be installed in order dkms,
>>>> dkms-agrsm-2.1.80-9mdv2009.0.i586.rpm, agrsm-tools-0.0.1-2.noarch.rpm
>>>>
>>>> Loss of sound is expected.
>>>> Bjorn is most experienced to help you.
>>>>
>>>> Service of 11c11040 under 2.6.28 kernels has not yet been accomplished.
>>>>
>>>> MarvS
>>>>
>>>>
>>>> On Tue, Sep 22, 2009 at 9:04 AM, Manish Kalonia
>>>> <manishkalonia85@xxxxxxxxx> wrote:
>>>> > Hi,
>>>> >
>>>> > I am using opensuse 11.1 on a CQ45-137TX compaq machine. I followed the
>>>> > necessary steps described in making modules HOWTO section. But after
>>>> > making the modules from the kernel source and rebooting my sound system
>>>> > stopped working. Also, i could not make any modules from the agrsm
>>>> > files. I am attaching the ModemData file.
>>>> >
>>>> > Thanks in advance
>>>> >
>>>> > Thanks and Reply,
>>>> > Manish Kalonia
>>>> >
>>>
>>>
>>
>
