Meni je proradio na Fedori 3 kada sam pročitao email koji paste-ujem dole. Odeš na
www.linmodems.org, skineš utility 'scanModem', pogledaš rezultate i skineš driver koji ti treba. Ako imaš probleme prijaviš se na mailing listu i postaviš pitanje. Isto kao i ovom baji, i meni je proradio kada sam skinuo ovaj driver [url]http://linmodems.technion.ac.il/packages/Intel/537/intel-537-2.60.80.0.tgz[/url], driveri sa intelovog sajta mi nisu radili, imaju samo EP i SM). Nisam imao probleme koje je on imao pri kraju, moja "greška" je bila što sam skinuo driver sa Intela a ne nekog šklj sajta. Srećno!
***
Success With Intel 537 Modem In Fedora Core 3
I started by first downloading, unpacking, reading the directions, and while logged in as root, running the latest version of scanModem from the linmodem website.
The modemdata.txt generated by scanModem stated I had an Intel-537 modem and to download (for my particular Intel 537 modem) the Intel-537-2.60.80.0.tgz package available on the linmodem website.
Before I could compile the driver for my modem I needed to set up the kernel headers. According to the release notes with Fedora Core 3 you do not necessarily need to install the kernel source pkg. After consulting with Marv on how I could do this, I logged in as root, I moved into the following directory “ /lib/modules/KernelVersion/build/ “ and issued the following command,
“ make KERNEL_DIR=/lib/modules/KernelVersion/build/ “ , this set up the kernel header information that the compiler for the modem driver would need. Without this header information set up the driver will not compile. Now I was ready to begin compiling the modem driver.
I downloaded the proper Intel-537 version driver package for my modem (as there are several varieties of the Intel-537) from the linmodem.org website and unpacked in a temporary directory and proceeded to read the readme file and installation instructions for making the 537 driver.
I moved into the temporary directory where I had unpacked the 537 driver package.
As per the package instructions I issued the “ make clean” command. When that command was completed I Then issued the “make 537” command which compiles the drivers. When the compiling of the drivers was completed without errors (warnings are ok) I was ready for the next command. I issued the “make install” command which installs the drivers.
I then rebooted and verified that 537_boot (the modem driver module) was being loaded upon booting and it was.
The next phase is where I started to run into some difficulty.
I ran the Internet configuration wizard to set up my modem and ISP connection however the wizard was not picking up my modem correctly and I ended up installing it as a generic modem. Upon trying to activate the modem and my ISP connection I always got an “error 8” and my modem was not working at all. I deleted the generic modem from
the network configuration panel.
After some consulting with Marv he asked I find out where my outputs were by doing the following:
---------------------------------------------------------------------------------
[root@localhost ~]# ls -l /dev/modem /dev/537
[root@localhost ~]# lsmod | grep 537
If Intel537 is not shown
# modprobe Intel537
If there is a symbolic link
/dev/modem --> /dev/537
Try as a first function test:
[root@localhost ~]# wvdialconf wtest.txt
If successful, try the wizard again specifying /dev/modem as your port during the configuration.
-----------------------------------------------------------------------
My results were:
-----------------------------------------------------------------------
[root@localhost ~]# ls -l /dev/modem /dev/537
crw-rw-r-- 1 root root 240, 1 Jan 13 18:38 /dev/537
lrwxrwxrwx 1 root root 8 Jan 13 18:38 /dev/modem -> /dev/537
[root@localhost ~]# lsmod | grep 537
Intel537 4307172 0
----------------------------------------------------------------------
This showed I had the symbolic link.
Then I tried as a first function test:
----------------------------------------------------------------------
[root@localhost ~]# wvdialconf wtest.txt
my results were:
----------------------------------------------------------------------
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Port Scan<*1>: S2 S3 S4 S5 S6 S7
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
Please read the FAQ at
http://open.nit.ca/wvdial/
--------------------------------------------------------------------------------------
My modem wasn't being picked up on any ports.
After speaking with Marv again he suggested:
This is probably a trivia. Some wvdialconf releases don't follow the /dev/modem link, but only look at /dev/ttyS* port names, S14 and S15 are for experimental usage so just
[root@localhost dev]# rm /dev/ttyS15
[root@localhost dev]# ln -s /dev/537 /dev/ttyS15
and again
wvdialconf wtest.txt
If successful, then use the internet Configuration Wizard within the popup menus to configure a dialout. It will write a file /etc/wvdial.conf
------------------------------------------------------------------------
This created a symbolic link to ttyS15 for my modem driver, then I ran wvdialconf again and my results were:
[root@localhost /]# wvdialconf wtest.txt
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Port Scan<*1>: S2 S3 S4 S5 S6 S7
ttyS15<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS15<*1>: ATQ0 V1 E1 -- OK
ttyS15<*1>: ATQ0 V1 E1 Z -- OK
ttyS15<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyS15<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyS15<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyS15<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyS15<*1>: Modem Identifier: ATI -- OK
ttyS15<*1>: Speed 19200: AT -- OK
ttyS15<*1>: Speed 38400: AT -- OK
ttyS15<*1>: Speed 57600: AT -- OK
ttyS15<*1>: Speed 115200: AT -- OK
ttyS15<*1>: Speed 230400: AT -- OK
ttyS15<*1>: Speed 460800: AT -- OK
ttyS15<*1>: Max speed is 460800; that should be safe.
ttyS15<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found a modem on /dev/ttyS15.
Modem configuration written to wtest.txt.
ttyS15<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
----------------------------------------------------------
Wvdialconf found my modem finally !
I then ran the Internet configuration wizard again which didn't automatically pick up my modem so I installed it as a generic modem again and then I edited the settings for it in the Network Configuration Panel ,and made sure that in the Modem Configuration Panel the Modem Device was set to /dev/ttyS15 , and that on the Advanced tab on the Modem Dialup Configuration I entered the modem initialization string given by Wvdialconf.
I then clicked Activate and my modem worked fine. Finally.
All worked fine until I re-booted. My modem stopped working again. It seems that the symbolic link in my /dev directory would disappear on reboot and I had to remake the symbolic link every boot. This became frustrating. After still more consulting with Marv he directed me to an article on symbolic links. However , When shutting down the system for the night and clicking on Actions, then Log Out, I notice a little check box for “Save System Settings”, I checked this box and on all future re-boots my symbolic link and modem has continued to work flawlessly.
As an interesting aside, all the above was done while logged in as root. When I logged in as a user and I had to run the Internet Configuration Wizard again to set up the modem and ISP connection as a user, the modem would only work when it was set to /dev/modem in the Modem Device in the Modem Configuration Panel. Other than that everything worked the same.
Intel 537 i 537EP drajveri ponovo
Re: Intel 537 i 537EP drajveri ponovo
Re: Intel 537 i 537EP drajveri ponovo
Re: Intel 537 i 537EP drajveri ponovo
MD3200