THANKS THANKS THANKS !Re: [hsflinux] uart and irq settings for /dev/ttySHSF0

[Kaushik Ghose]

Hi Marc and all you linmodem-ers,
can't thank you enough ! I got the modem to work !
Currently on my linux high for this week.

Ok Marc here's how I got your hsf driver working on my HP6630.

I have SuSE linux 7.3 (2.4.10-4GB kernel)
The machine is a HP 6630 pavilion desktop i810 chipset bought in 1999
Modem : HSF Connexant SoftK56 (vendor: 14f1, device : 2013)

I downloaded your rpm for SuSE for this kernel
The file name is hsflinmodem-5.03.03.L2mbsibeta02052600-1_suse73.i386.rpm
and installed it.

Then I added "pci=biosirq" to my /etc/lilo.conf file.
ran /sbin/lilo

Then I went into the BIOS during POST (by hitting F1) , went into
"advanced" and there is this funny OS TYPE setting, which I set to
"other" (was WIN98)

My modem init string turns out to be AT&FE, and the hangup string is ATH
(I think). The rest of the stuff is unchanged from the kppp defaults.
(You can get this from <your dos partition>/windows/inf/CNX2013.inf or
from the modem log on windows)

Now, only after I changd the BIOS OS option to "other" did all this work
(and ofcourse I didn't discover all of this in a linear fashion, rather a
random walk!). The only reason why I fiddled with this setting is that I
ran across a page where a post said doing this solved some other problem
with a PCI device. 
Methinks I smell a windows conspiracy here... :)

I don't know if removing the "pci=biosirq" from lilo.conf will still let
the driver work, but I'll try that tomorrow.

Anyway, thanks a lot, now I have internet on my linux box and don't have
to reboot into windows everytime.

cheers !
-kaushik


On Wed, 12 Jun 2002, Marc Boucher wrote:

> Hi Kaushik,
> 
> Seems that you have an IRQ assignment problem which isn't the HSF
> driver's fault. Try upgrading to the latest SuSE kernel, adding the
> pci=biosirq parameter when booting, playing with ACPI BIOS settings,
> and if everything fails you might have to compile the newest kernel
> from ftp.kernel.org with the latest ACPI patches.
> 
> Let us know what worked..
> 
> Marc
> 
> On Wed, Jun 12, 2002 at 10:04:27AM -0400, Kaushik Ghose wrote:
> > Hi marc,
> > thanks for your reply.
> > The hsf modules do load up after I run kppp. However there is a problem.
> > here is the relevant part of the output of dmesg
> > 
> > PCI: Enabling device 01:0e.0 (0304 -> 0307)
> > PCI: No IRQ known for interrupt pin A of device 01:0e.0. Pleas e try using
> > pci=biosirq.
> > LinuxHookInterrupt: request for IRQ 0 failed
> > Trying to free free IRQ0
> > hsf_request_port: ComCtrlOpen failed, r=1!
> > 
> > 
> > any suggestions ?
> > thanks
> > -kaushik
> > 
> > 
> > On Wed, 12 Jun 2002, Marc Boucher wrote:
> > 
> > > ttySHSF0 is a completely virtual uart, there is no point to use setserial
> > > on it.  The type, irq, and i/o values reported are indeed dummy placeholders.
> > > The real values are assigned automatically to the low-level hardware driver.
> > > 
> > > You should see hsf modules loaded after trying to access the device.
> > > 
> > > If not, then try "modprobe hsfserial" manually to see if any error
> > > messages occur. Afterwards run "dmesg" to check for additional kernel
> > > error messages..
> > > 
> > > Marc
> > > 
> > > On Wed, Jun 12, 2002 at 12:21:20AM -0400, Kaushik Ghose wrote:
> > > > Hi,
> > > > This refers to how the hsflinmodem works.
> > > > 
> > > > Basically I oculdn't get it to work on my system
> > > > HP 6630 Pavilion, connexant soft56K modem, SuSE 7.3, kernel 2.14.10-4GB
> > > > and want to understand the system a bit better
> > > > 
> > > > I'm guessing that by installing
> > > > the rpm for my kernel and linux distro I load certain modules (namely the
> > > > hsf modules) into the kernel and they work just like the winmodem software
> > > > does.
> > > > 
> > > > So in order for this to be transparent to the rest of the system
> > > > /dev/modem links to this "virtual device" so all info that would go to the
> > > > serial port connected to the physical modem goes to this "fake" device.
> > > > 
> > > > Now my question is how does the fake device know how to send on the
> > > > information to the physical modem ? DOn't we have to do any settings, or
> > > > does hsfconfig take care of all that ?
> > > > 
> > > > Also when I do setserial -G /dev/modem I get the reply uart: unknown
> > > > 
> > > > is this ok ?
> > > > 
> > > > The irq is set to 0, should I fiddle with this or is it a "dummy"
> > > > 
> > > > If I do lsmod, I can't see anything with hsf, should I ?
> > > > 
> > > > thanks
> > > > -kaushik
> > > > 
> > > > 
> > > > 
> > > > _______________________________________________
> > > > hsflinux mailing list
> > > > hsflinux at lists.mbsi.ca
> > > > http://www.mbsi.ca/mailman/listinfo/hsflinux
> > > > 
> > > 
> > 
>