ISDN 4 linux and Demon and AsusCom PCI cards ..
Robin
Its busy on here again isn;t it ;)
anyway ...
anyone got any experience running the AsusCom ISDN cards under
ISDN4Linux (IPPP?) or indeed under any other ISDN protocol manager for
linux (if that the correct term)
i read the readme and was just as confused when I finished as when well
.. err I started out
Also .. I've bunged the card in and the PCI pnp thing in the bios seems
to have seen it .. so how do I get to view the settings so assigned ? ..
(irq, base etc) as Lothar (the Linux Mandrake hardware nazi) doesnl;t
appear to see it ... its Linux Mandrake btw .. but its 100% dedrat 6.2
compatible (so it says on the box) so redhat answers will do .
presumably there is some way of persuading redhat to display PCI config
setting ?? is there??
robin
Andrew Laurence Bryant
I expect you are trying too hard, just like I did.
I'm using an Asus ISDNLink 128 (but only one channel at the moment) on
SuSE 6.3 with I4L.
After lots of aggravation I contacted Werner Cornelius
(wer...@isdn4linux.de).
He replied that Asuscom PCI cards are either type=35 (HFC-PCI) or
type=36 (Winbond). You must not specify IRQ, I/O etc: just let the
system use auto-detection.
Karsten Keil at SuSE responded that the Asuscom driver is only for ISA
cards: for PCI cards use either HFC-S PCI for type 35, or W6692 for type
36.
The following info comes from Yast, the SuSE set-up tool, on my working
system:
Start I4L [X] (That means yes)
ISDN protocol [Euro-isdn (EDSS1)]
Type of isdn card [HFC 2BDSO PCI]
Card identification :HiSax :
Everything else is left blank: IRQ, I/O, Mem Base Add etc.
Hope this helps.
Andrew
p.s. Do you know anything about SCSI scanners & Adaptec cards? That's
my current bugbear.
Robin wrote:
>
> Hi ...
>
> Its busy on here again isn;t it ;)
>SNIP
>.......
> robin
Robin
> Robin,
>
> I expect you are trying too hard, just like I did.
>
<snip>
ooh thanks for that .. thats jus the info I need (i hope!) I'll let youknow
.. the line goes in monday ..
>
> p.s. Do you know anything about SCSI scanners & Adaptec cards? That's
> my current bugbear.
>
I run a Microtek X6 (636A4 in a newer box) into an Adaptec 2940 (ithink its
a 2940) and sometimes a NCR summink 817?? .. works s treat .. xscanimage
configure it just like it says on the tin and away it goes .. (the trick
seems to be to make sure you get a tier1 scsi card and a scanner on the
list of 'known workers' some of the cheaper crappier SCSI cards just won't
do it .. they aren;t 'real'scsi cards but special scannering scsi cards
with a limited scsi command set etc .. get a decent tier 1 card and you're
in with more of a chance
hth
Robin
>
> Andrew Laurence Bryant wrote:
>
> > Robin,
> >
> > I expect you are trying too hard, just like I did.
> >
>
> <snip>
>
> ooh thanks for that .. thats jus the info I need (i hope!) I'll let youknow
> .. the line goes in monday ..
here we go again .. replying to my own messages ;-)
right ho ..
having tracked down the gremlin that was preventing isdn4linux working
(kernel had type=35 HFC.PCI support .. but the init.d script didn't
think
so .. ) I now have my isdn4linux working a treat and autodialling into
demon Smurtime G5 just luvverley
now .. ;-) .. onto more deeper things ... your starter for 10:
has anyone got STAC (or indeed what is the best comp method) working
with
isdn4linux ..?? whenever I add -lzs 1 comp=7 to my (i)pppd init string
I
get:
Oct 20 22:43:14 workstation ipppd: unrecognized option 'comp=7'
sooo ..
Oct 20 22:53:45 workstation ipppd[21139]: Connect[0]: /dev/ippp0, fd: 7
Oct 20 22:53:49 workstation ipppd[21139]: Local number: xxxxxxxxx,
Remote number: 08440416672, Type: outgoing
Oct 20 22:53:49 workstation ipppd[21139]: PHASE_WAIT ->
PHASE_ESTABLISHED, ifunit: 0, linkunit: 0, fd: 7
Oct 20 22:53:53 workstation ipppd[21139]: ioctl(SIOCSIFMTU): Invalid
argument, 6 ippp0 1524.
Oct 20 22:53:53 workstation ipppd[21139]: Remote message: rszemeti: IP
Address: 158.152.98.107 Running PPP on 1053DNS
problem resolved. Possible problems with bonded NDU routing.Finger
sta...@gate.demon.co.uk for more info. Last change:
16:15 Oct 20HELLO^M
Oct 20 22:53:53 workstation ipppd[21139]: MPPP negotiation, He: No We:
No
Oct 20 22:53:53 workstation ipppd[21139]: CCP enabled! Trying CCP.
Oct 20 22:53:53 workstation ipppd[21139]: CCP: got ccp-unit 0 for link 0
(protocol: 0x80fd)
Oct 20 22:53:53 workstation ipppd[21139]: ccp_resetci!
Oct 20 22:53:53 workstation last message repeated 2 times
Oct 20 22:53:53 workstation ipppd[21139]: local IP address
158.152.98.107
Oct 20 22:53:53 workstation ipppd[21139]: remote IP address
158.152.1.222
in this bit .. does this mean I don't have MPPP enabled or even built
into
the kernel? .. and the line:
Oct 20 22:53:53 workstation ipppd[21139]: CCP enabled! Trying CCP.
does that mean I have compression available but the two ccp_resetci!
messages mean
it never establishes ...
and are the purple ROMP not-modems ASCEND_MAX's?
and what happened to Al Bundy?? ;-))
sorry .. so many questions..
r.
Jon Plews
Robin wrote in message <39F0C2AA...@rszemeti.demon.co.uk>...
[ snip ]
>
>now .. ;-) .. onto more deeper things ... your starter for 10:
>
>has anyone got STAC (or indeed what is the best comp method) working
>with
>isdn4linux ..?? whenever I add -lzs 1 comp=7 to my (i)pppd init string
>I
>get:
>
>Oct 20 22:43:14 workstation ipppd: unrecognized option 'comp=7'
>
'-lzs' *disables* LZS compression -- you want 'lzs 1:4' or 'lzs 1:3'
depending on the compression settings at Demon.
'comp=7' belongs in /etc/modules.conf, not in the options you
pass to ipppd. Don't use that level of outgoing compression
until you've checked the link works with no outgoing compression.
[ snip ]
>Oct 20 22:53:53 workstation ipppd[21139]: MPPP negotiation, He: No We:
>No
[ snip ]
>
>in this bit .. does this mean I don't have MPPP enabled or even built
>into the kernel?
That's a PPP negotiation message, nothing to do with the kernel.
MPPP is not available on surftime numbers on an SDU account (and
is current broken on NDU accounts I think).
You can use MPPP on the BLUE ROMP.
Jon Plews.