Re: problem on mandrake 10.0
<[email protected]> Wed, 17 Nov 2004 20:42:47 +0100 (CET)
| Newsgroups | gmane.linux.drivers.modem.hcf |
|---|---|
| Message-ID | <[email protected]> |
I had the same problem some time ago also with my mandrake 10 comunity edition and my supraexpress modem(I remember, now I dont use a telephone modem). I tried to change the country code (even to a diferent to my country) and sometimes it worked. Also, someone suggest me using a initialization command I cant remember right now, to turn off the busy line test before dialing (perphaps something like atxN with N a number 0,1,2,3). Look for AT commands and try. This last solution worked better for me. Sorry I cant remember exactly how it was. --- "Linuxant support (Jonathan)" <[email protected]> escribió: > Hi, > > it is possible that all these problems are related to 'udev' which is > > present on Mandrakelinux 10. Please try with the latest version of > the > HCF PCI driver, this new version adds improved support for 'udev'. > You > can download this new release of the HCF driver download page at : > > http://www.linuxant.com/drivers/hcf/full/downloads.php > > Regards, > > > Jonathan > Technical specialist / Linuxant > www.linuxant.com > [email protected] > > > [email protected] wrote: > > Hello, > > > > After a fresh installation of Mandrake 10.0 Official (plus > updates), I have > > discovered that my old Rockwell/Conexant internal modem would work > with a > > linuxant HCF driver. After installing the following, > > hcfpcimodem-1.01lnxt04111200full_k2.6.3_7mdk-1mdk.i586. > > > <http://www.linuxant.com/drivers/hcf/full/archive/hcfpcimodem-1.01lnxt04111200full/hcfpcimodem-1.01lnxt04111200full_k2.6.3_7mdk-1mdk.i586.rpm.zip?PHPSESSID=0b1d275682bd5b98ec46fd04e0e72b8e>rpm > > > > <http://www.linuxant.com/drivers/hcf/full/archive/hcfpcimodem-1.01lnxt04111200full/hcfpcimodem-1.01lnxt04111200full_k2.6.3_7mdk-1mdk.i586.rpm.zip?PHPSESSID=0b1d275682bd5b98ec46fd04e0e72b8e> > > I was able to go online without any problem. However, after my next > system > > bootup, the modem was no longer accessible. Yet the command > > % rchcfpci restart > > made the module again active. Now the problem is that the modem > _always_ returns > > the signal BUSY after dialling. I have made all possible efforts to > solve this > > issue (reinstalling, compiling, disabling acpi and apic, etc), all > to no avail. > > Internet searches likewise did not yield any useful hint. > > > > Does anyone have any idea? I hope I could avoid buying a > non-winmodem, since I > > need to use dialup access only for a few months. > > > > Thanks in advance > > > > François C > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > hcflinux mailing list > > [email protected] > > https://www.linuxant.com/mailman/listinfo/hcflinux > _______________________________________________ > hcflinux mailing list > [email protected] > https://www.linuxant.com/mailman/listinfo/hcflinux > ______________________________________________ Renovamos el Correo Yahoo!: ¡100 MB GRATIS! Nuevos servicios, más seguridad http://correo.yahoo.es