(this is on 3.4-RC as of Dec. 11)
Here's the situation -- a lot of modems are brain-dead, and don't do a
full reset when you tell them to (by a DTR drop, with (usually) AT&D3)...
The DTE baud rate likes to stay where it was, instead of returning to the
115200 that (my) gettys are expecting. I w
On Thu, Dec 16, 1999 at 02:03:10 +, W.H.Scholten wrote:
> Kenneth D. Merry wrote:
>
> > In general, the stock NCR driver isn't being actively maintained, and your
> > problem could be the result of a bug in the driver, or some problem with
> > your MO drive. It's hard to say for sure. Gerar
Kenneth D. Merry wrote:
> In general, the stock NCR driver isn't being actively maintained, and your
> problem could be the result of a bug in the driver, or some problem with
> your MO drive. It's hard to say for sure. Gerard's driver is actively
> maintained, though, so if you still have prob
[redirected to -hackers]
On Sunday, 12 December 1999 at 8:34:51 -0500, David Bein wrote:
> Hi ...
>
> I have a PC with triple boot partitions setup, one of
> which is loaded with Solaris 2.7 (officially called version 7).
> I am wondering if anyone has any experience directly mounting ufs
> pa
In message <[EMAIL PROTECTED]> Michael Kennett writes:
: To confirm:
:
: The new pccard code contains the `controller pccard' config directive.
: - the source code is in sys/dev/pcic
: sys/dev/pccard
:
: The old pccard code contains the `controller card' con
On Thu, Dec 16, 1999 at 00:49:47 +, WHS wrote:
> Thomas David Rivers wrote:
> >
> > >
> > > The kernel hangs (rather an endless loop) with messages like:
> > >
> > > ncr0: timeout nccb=0xc0c38000
> > >
> > > if I attach a fujitsu M2513A2 640MB MO drive. From a quick glance in the
> >
Warner wrote:
> In message <[EMAIL PROTECTED]> Michael Kennett writes:
> : I've just scoured the archives, and found a thread from late October 1999
> : titled:
> : Massive pccard disruptions to continue
> :
> : So, have these disruptions continued? And what is the current status with
> : pcc
Thomas David Rivers wrote:
>
> >
> > The kernel hangs (rather an endless loop) with messages like:
> >
> > ncr0: timeout nccb=0xc0c38000
> >
> > if I attach a fujitsu M2513A2 640MB MO drive. From a quick glance in the
> > ncr source it seems there's a problem with the script stuff in case
> This message was sent from Geocrawler.com by "Alex" <[EMAIL PROTECTED]>
> Be sure to reply to that address.
>
> Hello,
> How can I choose major device number for our
> network adapter driver?
Network adapters don't have major/minor numbers, so you don't need to do
this.
--
\\ Give a man a
>
> The kernel hangs (rather an endless loop) with messages like:
>
> ncr0: timeout nccb=0xc0c38000
>
> if I attach a fujitsu M2513A2 640MB MO drive. From a quick glance in the
> ncr source it seems there's a problem with the script stuff in case of a
> timeout. Anyway, this doesn't hap
This message was sent from Geocrawler.com by "Alex" <[EMAIL PROTECTED]>
Be sure to reply to that address.
Hello,
How can I choose major device number for our
network adapter driver?
Thank you,
Alex
Geocrawler.com - The Knowledge Archive
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "u
This message was sent from Geocrawler.com by "Alex" <[EMAIL PROTECTED]>
Be sure to reply to that address.
Hello,
My driver support ISA/PCI network boards.
Can I use the same name for ISA and PCI devices
in kernel configuration file?
Like this:
device wanpipe0 at isa? ... # for ISA
device wan
L.S.
The kernel hangs (rather an endless loop) with messages like:
ncr0: timeout nccb=0xc0c38000
if I attach a fujitsu M2513A2 640MB MO drive. From a quick glance in the
ncr source it seems there's a problem with the script stuff in case of a
timeout. Anyway, this doesn't happen with ei
I have had similar problems (with 3.3-RELEASE), and yesterday I tried
the ncr.c from 4.x but unfortunately it didn't help. My system crashed
after 26 hours, with instruction pointer == random page fault address.
The machine is a Compaq Proliant 1850R with 640M RAM and a "ThunderLAN"
(tl) network
Warner Losh writes:
| In message <[EMAIL PROTECTED]> Michael Kennett writes:
| : I've just scoured the archives, and found a thread from late October 1999
| : titled:
| : Massive pccard disruptions to continue
| :
| : So, have these disruptions continued? And what is the current status with
|
Kris Kirby wrote:
>
> I am attempting to start a program on a impromptu cluster, one program
> per machine. I am using make, and seq from the cluster-it package in the
> ports collection. My problem is that make doesn't start the jobs
> parallel, it just goes from one to the other.
Have you expl
In message <[EMAIL PROTECTED]> Michael Kennett writes:
: I've just scoured the archives, and found a thread from late October 1999
: titled:
: Massive pccard disruptions to continue
:
: So, have these disruptions continued? And what is the current status with
: pccard support in the kernel?
Hello All,
I've just scoured the archives, and found a thread from late October 1999
titled:
Massive pccard disruptions to continue
So, have these disruptions continued? And what is the current status with
pccard support in the kernel?
I've noticed that a few files still contain the PCCARD_
Kris Kirby wrote:
> In my project root, I have the following makefile:
> SUBDIR = 1 2 3 4 5 6 7 8 9
> .include
Assuming you have an `encode' target that you want to run in parallel;
you need something like:
.for entry in ${SUBDIR}
${entry}.encode__D: .PHONY
@if test -d ${.CURDIR}/${ent
19 matches
Mail list logo
