John Reynolds~ <[EMAIL PROTECTED]> probably said:
> When you do this in 4.1.1, do you already have an 'ed0' device in
> your machine? The PAO example shows 'ed0' as the device while 4.1.1
> shows ed1. I'm currently having problems with any 4.1.1 kernel
> probing my two ed cards incorrectly (I get
[ On Tuesday, October 3, Thomas David Rivers wrote: ]
> Just to add to this thread a little.
>
> I put the card in a 3.4-RELEASE machine (which works.) It seems to
> acquire a different MAC address than the 4.1.1 code does.
>
> In 3.4 PAO I get:
>
>Card inserted, slot 0
>card0: assign
Dual 400MHz PII @128MB ram on a Asus P2B-D
I was hopeing only to have to build a kernel on this machine since that is
all I needed..
At 10:13 PM 10/2/00 -0600, Warner Losh wrote:
>In message <[EMAIL PROTECTED]> Darcy
Buskermolen writes:
>: ===> agp
>: @ -> /usr/src/sys
>: machine -> /usr/src/i3
Just to add to this thread a little.
I put the card in a 3.4-RELEASE machine (which works.) It seems to
acquire a different MAC address than the 4.1.1 code does.
In 3.4 PAO I get:
Card inserted, slot 0
card0: assign ed0 iobase 0x300 irq 9 flags 0x3
ed0: address 00:10:60:38:3b:b7,
On Wed, 27 Sep 2000, Alfred Perlstein wrote:
> I remeber coming across this problem with FreeBSD several years ago,
> someone told me to turn on or off the rfc extentions, try this:
The TCP Extensions are turned off yet.
Any other idea?
Paolo
To Unsubscribe: send mail to [EMAIL PROTECTED]
wi
Jordan, Cy and co.,
I'll admit my concept of time was taken from me during lectures on special
relativity, but for all observers on the list, I added fdesc after the
crashes began. I didn't see any problem with trying it.
I'll add the mfs mounts back later and poke the system by running
"periodi
Hi there,
I wanna download the FreeBSD iso file and i see FreeBSD 4.1-RELEASE and
FreeBSD 4.1.1-RELEASE. I think I bet get the 4.1.1-STABLE, but my
question is if i wanna get the latest 4.x-STABLE. Will it show
4.1-STABLE or 4.1.1-STABLE?
Thanks,
-Nader
To Unsubscribe: send mail to [EMAIL
> MFS will not cause you problems. It's safe to leave it in.
I think it might be a little premature to reach that conclusion right
now; I've had panics with MFS in the past and also took note of the
fact when Andrew said his usage of fdesc post-dated the crashes. But
for that, it would be my pr
In message <[EMAIL PROTECTED]>, John Baldwin writes:
>
> On 30-Sep-00 Cy Schubert - ITSD Open Systems Group wrote:
> > I've been working on a PGP 6.5.8 port, however I get the following:
> >
> > gcc -O -pipe -DPGP_UNIX=1 -DPGP_COMPILER_GCC=1 -DHAVE_CONFIG_H
> > -DPGP_DEBUG=1 -DUNFINISHED_CODE_
On Tue, 3 Oct 2000, FreeBSD wrote:
The problem wents away when changing Protocol from "PS/2" to "Auto".
Don't know as what the Logitech is now recohnized, but it works.
:>ng between virtual term and X11 problem. I can't verify right now
:>due to time constraints.
:>
:>My hardware is a Logitech Ma
Warner Losh <[EMAIL PROTECTED]> wrote:
>
> In message <[EMAIL PROTECTED]> Thomas David Rivers writes:
> : Nope - I have a "SmartLink" NE2000 clone card; that does to
> : 10/100 mbits/second... This is actually a re-labeled Archtek card.
>
> Ah. The light goes on. Does your config file look
I got the same error. After a few recompiles of XFree86 4.0.1_1 and still
no mouse, (something about ioctl and inappropriate device in
/var/log/XFree86.0.log), I only got it to work after setting the mouse
protocol to auto instead of ps/2.
/etc/X11/XF86Config:
Option "Protocol" "auto"
I think
12 matches
Mail list logo
