According to Harry L. Styron: While burning my CPU.
>
> Uwe Schmidtmann wrote:
> >
> > Luis Yanes wrote:
> > >
> > > Sure, I login as root and executed sccinit at the command line from
> > > /sbin/sccinit and also from the ones built in the source tree, but
> > > nothing happens.
> > >
> > > 73's de Luis
> >
>
> I haven't been following this. But sccinit appears to need to be
> executed from the rc.d scripts during the network startup. I have never
> been able to get it to execute as a command after the kernel boot has
> completed.
I have not followed this disscussion either but what Luis describes sounds
normal to me, if sccinit returns with no errors then it found the card,
dmesg will show something like the following just after issuing sccinit.
Z8530 SCC driver version 2.4c.dl1bke (experimental) by DL1BKE
Copyright 1993,1996 Joerg Reuter DL1BKE ([EMAIL PROTECTED])
scc0: data port = 0x153 control port = 0x152 -- found
scc1: data port = 0x151 control port = 0x150 -- found
scc2: data port = 0x157 control port = 0x156 -- found
scc3: data port = 0x155 control port = 0x154 -- found
Init Z8530 driver: 4 channels, IRQ 7
If you try a second time after the card has been found sccinit will return,
TIOSCCINI: : Invalid argument
sccinit writes to your log file also;
Z8530 SCC driver version 2.4c.dl1bke (experimental) by DL1BKE
--------------
Uwe,
You can only use sccinit once when you have the scc driver compiled into the
kernel, if it is compiled as a module you can rmmod ax25, (netrom) and any
other dependancies, then rmmod scc, after that you can reissue 'sccinit'.
All the above regards to z8530drv-2.4c as to 3.0 i would imagen the details
are the same.
> > Hi again,
> >
> > ok. Sorry, then I have no further idea.
> >
> > regards,
> >
> > Uwe
>
> --
> ######################################
> # Harry L. Styron, Attorney at Law #
> # 1-925-932-4300 Fax 1-925-944-0591 #
> # "The devil is in the details." #
> ######################################
>
--
Regards Richard.
[EMAIL PROTECTED]
