Hi,
On Fri, 2 Jul 1999, Phil Fraser wrote:
> Thank you for the reply Franck, but still no joy.
>
> > I had the same problem. No bc0 when I did ifconfig. Thats what you have
> isn't
> > it ?
>
> Yes, no /dev/bc*.
an network device has nog /dev/*, check eth0 , and btw the netword devaice
is called bcsf* (full duplex,new driver) and and bcsh*(half duplex, old
driver)
I used to have :
alias bcsf0 baycom_ser_fdx
alias bcsf1 baycom_ser_fdx
alias bcsf2 baycom_ser_fdx
alias bcsf3 baycom_ser_fdx
alias bcsh0 baycom_ser_hdx
alias bcsh1 baycom_ser_hdx
alias bcsh2 baycom_ser_hdx
alias bcsh3 baycom_ser_hdx
in my /etc/conf.modules for module use.
>
> > Do netstat -v and you will see if your kernel is well configured with
> AX25.
>
> This tells me that there is no Ax.25 support in the kernel which is why I
> posted the original message. I thought that I must have overlooked something
> when I compiled the kernel. I've recompiled the kernel a dozen times
> including different option without any obvious effect.
Sure you have ax25 support compiled in, or loaded as module ?
>
> Also, any attempt to use sethdlc does nothing except display a help screen.
> This may be an indication of the problem.
Trying with the correct device name would help i supose.
>
> I'm sure that I have overlooked something that should be obvious, any ideas?
> I've included my original e-mail in case it helps.
>
> > Hello,
> >
> > I have been attempting to configure Linux to use a serial Baycom modem for
> > some time, without success. The problem, as I see it, is the kernel has
> not
> > created a Baycom interface device.
> >
> > My most recent kernel compilation has amateur radio ax.25 level 2 protocol
> > and the Baycom ser12 full duplex driver, and no other amateur radio
> options,
> > built into the kernel. I have also tried a modularised kernel with amateur
> > radio support.
> >
> > I am currently using Red Hat 6.0 and kernel version 2.2.5-15. I also have
> > Craig Small's ax.25 tools installed.
> >
> > Things were a little more promising under Red Hat 5.2 and kernel version
> > 2.0.36. It still didn't work, but a boot message said something about the
> > creation of bc0-3 being deferred. Deferred until when wasn't made clear.
Yes in 2.0.xx the baycom simulates s kiss device on /dev/bc*, but in
2.2.xx it has changed to a netwerk interface, with the named modules
bcs[fh]*, and no related /dev/*
> >
> > I have searched the list archives for an answer, what have I overlooked?
/usr/src/linux/Documentation/networking/(baycom.txt|ax25.txt) ?
>
> Regards,
> Phil Fraser
> <[EMAIL PROTECTED]>
>
>
>
Arjan Filius
mailto:[EMAIL PROTECTED]
--------------------------------------------------------------
Argh! All right, so how am I supposed to work with Linux when
everything's already been done?! Can't these people leave some
broken MSDOS like parts so there's problems left to solve!?....
