Results 1 to 10 of 13
I found this link about modem drivers
Linuxant - Linux drivers for Conexant chipsets - HSF driver downloads
I didn't knew what I have to choose
because I don't know ...
- 02-06-2009 #1Just Joined!
- Join Date
- Sep 2008
- Posts
- 42
problem with modem driver
I found this link about modem drivers
Linuxant - Linux drivers for Conexant chipsets - HSF driver downloads
I didn't knew what I have to choose
because I don't know about this note
what's HDA modem?Note to Ubuntu Hardy (8.04) and SUSE (11.0, 11.1) users with HDA modems: Installing the alsa-driver-linuxant package is necessary before installing this driver.
is it win modem ?what's defference if it's?
and the most important think what I choose
my info :
opensuse11
Intel(R) 536EP V.92 Modem
amd 32bit
thanks
- 02-06-2009 #2Linux Guru
- Join Date
- Jan 2009
- Location
- Dover, NH
- Posts
- 1,633
Hmm, I remember you. Did the driver ever build?
Anyway, to answer your question, "HDA" means "High Definition Audio."
This means the modem is (same as an HSF modem) little more than a cheap sound card; all signals, commands, and data are processed by the CPU. Even the serial port interface is a virtual emulation. Yes, that kind of modem is a softmodem (aka winmodem).
Check this page for more information:
Modem-HOWTO: Modems for a Linux PC
The Intel 536EP is as far as I can tell a real modem, just needs a kernel module to link the modem on the PCI bus to a device interface the rest of the system can use. I don't know if you're talking about this one or if you ran into a Conexant modem you're inquiring about, so I'll leave that here for now.
- 02-07-2009 #3Just Joined!
- Join Date
- Sep 2008
- Posts
- 42
thanks for remember
hello
thanks for clear answer
now my kernal 2.6.25.5-1.1
and other information exist in last post
what I have to do for configuration my modem????
and connect with dial up ????
- 02-07-2009 #4Linux Guru
- Join Date
- Jan 2009
- Location
- Dover, NH
- Posts
- 1,633
First, I need to know if you followed the instructions in the Intel-Readme from the previous thread and if the build (make 536) and install (make install) was sucessful, as in no fatal errors.
After that, we can check for the presence of the module and if it's loaded. Once that's done, Yast should be able to take care of the rest of the configuration.
- 02-09-2009 #5Just Joined!
- Join Date
- Sep 2008
- Posts
- 42
oh noif the build (make 536)
the problem is here
wasn't built
I don't know why!!!!!!!!!
- 02-09-2009 #6
You need to show the error messages.
- 03-03-2009 #7Just Joined!
- Join Date
- Sep 2008
- Posts
- 42
Failed to build driver
OK....You need to show the error messages.
PHP Code:linux-ftyd:/windows/D/Linux/modem/intel-536EP-2.56.76.0-suse91-UP # make clean
cd coredrv; make clean
make[1]: Entering directory `/windows/D/Linux/modem/intel-536EP-2.56.76.0-suse91-UP/coredrv'
rm -f *.ko *.o *~ core
make[1]: Leaving directory `/windows/D/Linux/modem/intel-536EP-2.56.76.0-suse91-UP/coredrv'
rm -f *.o *.ko
linux-ftyd:/windows/D/Linux/modem/intel-536EP-2.56.76.0-suse91-UP # make 536
Module precompile check
Current running kernel is: 2.6.25.5-1.1-pae
/lib/modules... autoconf.h exists
diff: /boot/vmlinuz.autoconf.h: No such file or directory
autoconf.h matches running kernel
diff: /boot/vmlinuz.version.h: No such file or directory
version.h matches running kernel
uname -r|grep "2.6" && \
cd coredrv && make 536core_26 && \
cp Intel536.ko .. && cd .. && \
strip --strip-debug Intel536.ko && \
exit; \
ls Intel536.ko >/dev/null 2>&1 || uname -r | grep "2.6" && echo "Failed to build driver" && exit; \
if [ ]; then \
cd coredrv; make TARGET=TARGET_SELAH KERNEL_SOURCE_PATH= "PSTN_DEF=-DTARGET_SELAH -DTARGET_LINUX -DLINUX" 536core; \
else \
cd coredrv; make TARGET=TARGET_SELAH KERNEL_INCLUDES=/lib/modules/`uname -r`/build/include \
"PSTN_DEF=-DTARGET_SELAH -DTARGET_LINUX -DLINUX" 536core; \
fi ; \
cp Intel536.o .. ; \
if [ -a /boot/vmlinuz.version.h ]; then \
cp /boot/vmlinuz.version.h /lib/modules/`uname -r`/build/include/linux/version.h;\
fi
2.6.25.5-1.1-pae
make[1]: Entering directory `/windows/D/Linux/modem/intel-536EP-2.56.76.0-suse91-UP/coredrv'
make -C /lib/modules/2.6.25.5-1.1-pae/build SUBDIRS=/windows/D/Linux/modem/intel-536EP-2.56.76.0-suse91-UP/coredrv modules
make[2]: Entering directory `/usr/src/linux-2.6.25.5-1.1-obj/i386/pae'
make -C /usr/src/linux-2.6.25.5-1.1 O=/usr/src/linux-2.6.25.5-1.1-obj/i386/pae/. modules
/usr/src/linux-2.6.25.5-1.1/scripts/Makefile.build:46: *** CFLAGS was changed in "/windows/D/Linux/modem/intel-536EP-2.56.76.0-suse91-UP/coredrv/Makefile". Fix it to use EXTRA_CFLAGS. Stop.
make[4]: *** [_module_/windows/D/Linux/modem/intel-536EP-2.56.76.0-suse91-UP/coredrv] Error 2
make[3]: *** [sub-make] Error 2
make[2]: *** [all] Error 2
make[2]: Leaving directory `/usr/src/linux-2.6.25.5-1.1-obj/i386/pae'
make[1]: *** [536core_26] Error 2
make[1]: Leaving directory `/windows/D/Linux/modem/intel-536EP-2.56.76.0-suse91-UP/coredrv'
2.6.25.5-1.1-pae
Failed to build driver
- 03-03-2009 #8
Looks like you do not have the kernel source installed.
- 03-06-2009 #9Just Joined!
- Join Date
- Sep 2008
- Posts
- 42
oh..
I know..
I installed it before this
but
thanks
- 03-07-2009 #10Just Joined!
- Join Date
- Sep 2008
- Posts
- 42
oh..
what can I do know
Is it problem without solution ?


Reply With Quote