e...
Please consider upgrading your kernel! I hope you can imagine that
almost none of the "guru's" is interested in hacking a several
generations old kernel.
73 Thorsten
--
| Thorsten KranzkowskiInternet: [EMAIL PROTECTED]|
| Mobile: ++49 170 1876134 Snail: Niemannsweg 30, 49201 Dissen, Germany |
| Ampr: dl8bcu@db0lj.#rpl.deu.eu, [EMAIL PROTECTED] [44.130.8.19] |
or & maintainer of setserial.
Ok, I noted some /dev/cua occurrences in the setserial manpage, I'll send
Ted a note about that.
BTW. I've 14 serial ports running in my system, 2 onboard, 4 on a dumb
ISA card and 8 on a fourport compativle card. I've reprogrammed the
address de
used an
interrupt. (As opposed to polling each port individually). Linux
can use that register if available. In fact it's the default for some ports
ttyS5 onwards. So one can switch it off.
'^fourport' not needed on ttyS0..3 (because it's the default) but it won't
hurt
x27;t work with differently named devices.
You should not be surprised if someday suddenly all cua* prots are gone :-)
> and so on.
Brians real problem seams he want to adjust the base address to 0x3f8 (he says
so in his text) but infact uses 0x3f0 (typo!) in his rc-script
73 Thorsten
--
Brian: maybe you should change the '0' at the end of your port addresses
to '8' and doublecheck that the address is correct then.
> > 03f6-03f6 : ide0
> > ec80-ecff : eth1
> > ef80-ef9f : Intel Speedo3 Ethernet
> > ffa0-ffa7 : ide0
> > ffa8-ffaf :
On Thu, Feb 03, 2000 at 12:55:51PM +1100, Craig Small wrote:
> Thorsten Kranzkowski said:
> > distribution. They will get a new Kernel _along_ with matching application
> > software.
>
> As someone who used to maintain the ax25-tools and the ax25-kernel for
> one dist
: no
BUT: I think this has nothing to do with that error-message. Can you post
'cat /proc/ioports' output?
> these serial ports ??
>
>
> Brian McCarthy
> N7TUQ
>
Thorsten
--
| Thorsten Kranzkowski Internet: [EMAIL PROTECTED]|
| Mobile
mount of time to work out what needs to be done to upgrade, with the
Well, that's true somehow. But as I understand from the discussion there
are some 'mutually exclusive' changes to be done.
> option of falling back to something that works in the interim.
It see
g toward being as consistent with the rest of the
> Linux networking standards as possible.
Absolutely. What I personally wish is that the ax25-Interfaces are referenced
with their kernel-net-device-name (e.g. bcsf0, ax1 ...) instead by means
of those /etc/ax25/{ax,nr,rs}ports files.
>
targetting for 2.4 or later, to intentionally
cut support for older kernels.
Look at the new ax25-tools: they _require_ glibc 2.1.x - because supporting
older libs is ugly and older libs don't provide funcionality the tools need.
If you already have glibc, then a new kernel is no
s somewhat tricky though. (because micro$soft insists on trashing
the mbr and thus deleting LILO)
73 Thorsten
--
| Thorsten Kranzkowski Internet: [EMAIL PROTECTED]|
| Mobile: ++49 161 7210230Snail: Niemannsweg 30, 49201 Dissen, Germany |
| Ampr: dl8bcu@db0lj.#rpl.deu.eu, [EMAIL PROTECTED] [44.130.8.19] |
Date: Tue, 20 Jul 1999 13:13:47 +
From: Thorsten Kranzkowski <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Linux boot messages
Reply-To: [EMAIL PROTECTED]
Mail-Followup-To: [EMAIL PROTECTED]
X-Mailer: Mutt 0.95.6i
In-Reply-To: <[EMAIL PROTECTED]>; from Gerd on Tue,
Jul
ibution'
I can also reproduce this bug on my main pc (alpha AXPpci33) but the
debugging message is much less descriptive :-(
It seems to me that the 'heartbeat timer' doesn't get removed when downing
the interface. It tics once per 5 seconds
> 73 de Jeff
>
> --
fore that my primary PC was an cyrix486DX/4 with a similar setup.
Hmm - I still didn't test the Baycom on a shared interrupt
(it's on irq 3 now)
>
> Until I get a newer mainboard and cards, I would like to be able
> to squeeze the most out of my old, and still functiona
wn. Maybe the 'heartbeat' timer?
If there is demand for more detailed info I will investigate this again.
>
> Max, IK0XKP (Rome, Italy)
>
73 Thorsten
--
| Thorsten KranzkowskiSnail: Niemannsweg 30, 49201 Dissen, Germany |
| Mobile: ++49 161 7210230 Inet:
lcome.
When you intend to use tcp/ip, you will have to use the interface name anyway,
right? (route, ipchains ...)
> You missed only the whole idea of [ax|nr|rs]ports files...
hihi - at least I now have a clue what the motivation for it really is,
although I still don't like it.
> -
testing purposes etc.
I don't know about netrom or rose but guessing from the manpages the same
arguments apply. You can use nr0 or rose0 to access these interfaces.
By the way - one should drop "-i inetaddr" and "-m mtu" from nrattach and
rsattach - that's ifcon
17 matches
Mail list logo
