Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Complete Linux Newbie.
Running Mandrake 9.
Using kppp (but same problem in the gnome thingi)
Got a Conexant chipset internal PCI modem.
Installed and configged the HSF drivers.
kppp speaks with the modem and everything seems OK, _but_;
ATDT# doesnt actually send the tones for #. Iv listened on the line and when I commandeer ATDT# it starts some kind of a very rapid flicker....
I thought it might be sending pulse, but I tried this on the connection Im on now (same box, same modem, WinXP) and I couldnt hear anything on the line then. And I/kppp explicitly asks for D_T_, so....
The modem got /dev/ttySHSF0 and /dev/cuaHSF0. In the instructions to the driver it says that the cua is the 'call-out device'. Neither show up in kppp, but ttySHSF0 has the /dev/modem link which does show up. The problem is the same if I change the link (ln -s) to cuaHSF0.
1. Whats happening??
2. How can I fix it?? Obviously I _need_ to get online..
3. How do I get /dev/ttySHSF0 and /dev/cuaHSF0 to show up in kppp
Did you check your modem type with the utility at the hcfpcimodem site ?
Also - setserial or kpp has options to show something akin to a log which is fairly straight-forward. Listening in wont help you too much.
Setserial at the command-line is easier
Hope this helps
Originally posted by fancypiper I had no problems with Mandrake 9.0 and a Conexant/Rockwell modem. Did you correctly identify your modem and get the correct driver?
Thanx for all those links, hope someone will find them useful.
Yeah, I did correctly identify and the driver was the correct one. Problem is now solved, as I got a prompt answer from the Linuxant Support guys [1].
The problem was APIC and its wrong handeling of PCI. I put the variable 'noapic' in my bootloader (LILO), and everything now workes.
[1]:
I think you might have an IRQ problem or a FLAGS/RELAYS problem. Both
problems require some work to get around.
If it is an IRQ problem, you can try playing with the kernel options
"noapic", "acpi=off" and/or "apm=off".
If that doesn't work, you can try to configure and install a generic kernel
with the ACPI patches found on this web site: http://sf.net/projects/acpi
You will then need to use the generic HSF driver and compile the modules
with "hsfconfig".
For FLAGS/RELAYS problems, if your modem work correctly under Windows, you
can usually import the settings from the Windows driver. I will give you the
procedure.
Please find a ".cty" or ".inf" file included with your Windows modem driver
(you might have both) and then look for the lines starting with:
"XXXX" has to be replaced with your specific country code (the code is shown
when you run "hsfconfig --info").
Once you found the settings, you need to import them in the INF file under
Linux (replace the existing settings). To find out which file to edit, again
run "hsfconfig --info".
After saving the changes to the file, make sure you unload the driver with
"hsfstop" and then run "hsfconfig --nvram" to update the "nvram.bin" file
that is used by the modem.
Excuse me! I'm a beginner of Linux.. I think I have a same problem with u.. Can u explain how did u solve this problem in detail?? ( I'm not good at speaking English)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.