VectorLinux
October 21, 2014, 11:42:36 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to http://vectorlinux.com/forum1. The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
 
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: [1]
  Print  
Author Topic: hsfmodem driver  (Read 2900 times)
overthere
Vectorian
****
Posts: 1281



« on: March 31, 2009, 07:52:26 pm »

I installed the hsfmodem-7.80.02.03full driver to see if it would install as another poster was haveing trouble.

http://www.linuxant.com/drivers/hsf/index.php

the modem installed well for me as per the install note and worked and I rebooted and it worked..I used it today and it worked but when I attempted a second use the connect script failed.
I ran in a terminal after reboot then opened again...below is the terminal and /var/log/message plus lspci & lsmod

the driver does not seem to load the second time?..curious if this is fixable or a one trick pony

it is the same from root or user

any thoughts would be appreciated...thanks

chestnut via terminal

user1:$ chestnut-dialer
/usr/share/chestnut-dialer/chestnut_dialer/connection.py:190: RuntimeWarning: tempnam is a potential security risk to your program
  file_name = os.tempnam()
chestnut-dialer: warning: cannot open '/etc/resolv.conf' for appending
chestnut-dialer: warning: cannot open '/etc/resolv.conf' for reading and writing
vector:/~

user1:$ chestnut-dialer
/usr/share/chestnut-dialer/chestnut_dialer/connection.py:190: RuntimeWarning: tempnam is a potential security risk to your program
  file_name = os.tempnam()
vector:/~
user1:$

/var/log/messages

Mar 31 21:24:12 vector pppd[4129]: Plugin passwordfd.so loaded.
Mar 31 21:24:13 vector kernel: PPP generic driver version 2.4.2
                -----------------------------------------------
Mar 31 21:24:13 vector pppd[4129]: pppd 2.4.4 started by user1, uid 1000
Mar 31 21:24:29 vector pppd[4129]: Serial connection established.
Mar 31 21:24:29 vector pppd[4129]: Using interface ppp0
Mar 31 21:24:29 vector pppd[4129]: Connect: ppp0 <--> /dev/modem
Mar 31 21:24:30 vector pppd[4129]: PAP authentication succeeded
Mar 31 21:24:31 vector kernel: PPP BSD Compression module registered
Mar 31 21:24:31 vector kernel: PPP Deflate Compression module registered
Mar 31 21:24:31 vector pppd[4129]: local  IP address
Mar 31 21:24:31 vector pppd[4129]: remote IP address
Mar 31 21:24:31 vector pppd[4129]: primary   DNS address
Mar 31 21:24:31 vector pppd[4129]: secondary DNS address
Mar 31 21:35:16 vector pppd[4129]: Terminating on signal 15
Mar 31 21:35:16 vector pppd[4129]: Connect time 10.8 minutes.
Mar 31 21:35:16 vector pppd[4129]: Sent 120214 bytes, received 269689 bytes.
Mar 31 21:35:16 vector pppd[4129]: Connection terminated.
Mar 31 21:35:17 vector pppd[4129]: Exit.

Mar 31 21:36:00 vector pppd[4535]: Plugin passwordfd.so loaded.

                -----------------------------------------------
Mar 31 21:36:00 vector pppd[4535]: pppd 2.4.4 started by user1, uid 1000
Mar 31 21:36:40 vector pppd[4540]: Plugin passwordfd.so loaded.
Mar 31 21:36:40 vector pppd[4540]: pppd 2.4.4 started by user1, uid 1000
Mar 31 21:36:40 vector pppd[4540]: Removed stale lock on modem (pid 4535)

Mar 31 21:40:43 vector gconfd (user1-4564): starting (version 2.22.0), pid 4564 user 'user1'
Mar 31 21:40:43 vector gconfd (user1-4564): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Mar 31 21:40:43 vector gconfd (user1-4564): Resolved address "xml:readwrite:/home/user1/.gconf" to a writable configuration source at position 1
Mar 31 21:40:43 vector gconfd (user1-4564): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Mar 31 21:40:43 vector gnome-keyring-daemon[4571]: Scheduling hal init retry

lspci lists modem
02:07.0 Communication controller: Conexant HSF 56k HSFi Modem (rev 01)
not sure how to get the id as per the link list

lsmod

snd_mixer_oss          15104  1 snd_pcm_oss
speedstep_lib           4740  0
freq_table              4352  0
hsfpcibasic2           64048  0
hsfserial              21284  1 hsfpcibasic2
hsfengine            1298400  2 hsfpcibasic2,hsfserial
hsfosspec              86252  6 hsfpcibasic2,hsfserial,hsfengine
hsfsoar                94296  1 hsfpcibasic2

sorry..not sure how to get the content into the window with the scroll for smaller post.
thanks for any
cheers
« Last Edit: April 09, 2009, 08:24:48 pm by overthere » Logged

Everything Is Relative
overthere
Vectorian
****
Posts: 1281



« Reply #1 on: April 03, 2009, 03:23:19 am »

Ok...since no one know if it is even possible to toggle off the gnome keyring daemon I decided to just delete everything related to gconfig and keyring to see what happened

I removed /home/.gconf & .gconfd--/etc/gconf--/usr/libexec/keyring ask & gconfig-2---/usr/include/gnome keyring & gconfig--and /usr/bin gnome-keyring

after reboot modem dials a connection once only but the /var/log/message no longer notes any gconfd or gnome-keyring messages

Apr  3 03:51:35 vector pppd[4195]: Plugin passwordfd.so loaded.
Apr  3 03:51:35 vector pppd[4195]: pppd 2.4.4 started by bootstrap, uid 1000
Apr  3 03:51:35 vector pppd[4195]: Removed stale lock on modem (pid 4140)

I changed the init string to AT &F thinking maby the modem was not being reset...still once

I looked in the bios for any mention of acpi and found one-acpi s3-disabled ...still once

linuxant suggests that if the modem dials irregularly 

This problem might be ACPI-related or caused by a timing issue related to the APIC timer module in some Linux kernels (usually SMP kernels).
You can verify if your kernel is using APIC by looking for the line "ENABLING IO-APIC IRQs" when you run the "dmesg" command.

If you experience this problem, try disabling ACPI and/or the APIC by booting your kernel with the option "acpi=off" and/or the option "noapic"

ok dmesg suggests that acpi is enabled for irq19 [lnkd] which is used by the hsf modem

ACPI: Using IOAPIC for interrupt routing

ACPI: PCI Interrupt Link [LNKC] (IRQs 16 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 16 18 19) *3

ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 19
hsfpcibasic2 0000:02:07.0: PCI INT A -> Link[LNKD] -> GSI 19 (level, high) -> IRQ 19
ttySHSF0 at I/O 0x1000 (irq = 19) is a Conexant HSF softmodem (PCI-14f1:2f00-13e0:8d8c)

how does one turn off acpi and /or acpi for irq19?

I typed acpi=off in a terminal ond also rebooted with it in rc.local
 and also with acpi_use_timer_override but to no effect

it seems to work consistantly once per boot with vl6 on compaq 6010

if anyone knows anything they are not talkin so I give up....bizarre

cheers
Logged

Everything Is Relative
uelsk8s
Administrator
Vectorian
*****
Posts: 2504



« Reply #2 on: April 03, 2009, 01:32:01 pm »

Quote
If you experience this problem, try disabling ACPI and/or the APIC by booting your kernel with the option "acpi=off" and/or the option "noapic"
that means you have to add those to the kernel command line (lilo or grub)
if you use lilo you can press the tab key and type them to see if they work.

Logged
overthere
Vectorian
****
Posts: 1281



« Reply #3 on: April 03, 2009, 08:49:01 pm »

Thanks uelsk8s
I did try it with linux acpi=off and with added acpi_use_timer_override

the system still boots and dmesg shows that acpi is disabled but I still get the connect script failed after one or two connections...this is always followed by the gconfigd and gnome keyring deamon thing which is why I was wanting to turn that off..

I do not think I moved all related files for gconf and keyring and do not know the ramifications of doing that. so it may still be part of the issue

I put them back in place before turning off acpi.

perhaps I need to switch to hal as the message says scheduleing hal init retry? I use vlhot..but could not find the dialog in vasm..I thought in vasm you could switch from one to the other

anyway thanks

cheers
« Last Edit: April 04, 2009, 01:05:14 am by overthere » Logged

Everything Is Relative
uelsk8s
Administrator
Vectorian
*****
Posts: 2504



« Reply #4 on: April 09, 2009, 09:30:58 am »

you want vasm -> hardware -> mounter IIRC
Logged
overthere
Vectorian
****
Posts: 1281



« Reply #5 on: April 09, 2009, 03:04:06 pm »

Thanks uelsk8s...Ill try it...for some reason I passed that thinking it was for hd mounts..anyway

cheers
Logged

Everything Is Relative
overthere
Vectorian
****
Posts: 1281



« Reply #6 on: April 10, 2009, 07:14:01 pm »

Ok..that naturally made no differance

the solution to the connect script failing seems to be in /etc/ppp/options

remove # from disconnect..this apperas to allow the modem to disconnect so a reconnection is possible.

cheers
Logged

Everything Is Relative
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!