>
> Latest discovery: the mouse will work fine if you choose "/dev/pms0"
> and "auto" as mouse device and protocol type. But you have to kill
> "moused".
>
> Looks like XFree-4 does not like moused for some reason...
It sounds then like some weird moused interaction. Not using moused
is probab
On Thu, Jan 18, 2001 at 09:03:39AM -0500, Louis A. Mamakos scribbled:
| > Latest discovery: the mouse will work fine if you choose "/dev/pms0"
| > and "auto" as mouse device and protocol type. But you have to kill
| > "moused".
| >
| > Looks like XFree-4 does not like moused for some reason...
O
Drew Sanford <[EMAIL PROTECTED]> writes:
> I strongly suspect its an IRQ conflict. Every problem of this sort
> that I've seen with the A7V has been an IRQ conflict, including the
> problem I had with my own. Specificly I had to hard set the IRQ on my
> NIC through the PCI management section of t
> On Thu, Jan 18, 2001 at 09:03:39AM -0500, Louis A. Mamakos scribbled:
> | > Latest discovery: the mouse will work fine if you choose "/dev/pms0"
> | > and "auto" as mouse device and protocol type. But you have to kill
> | > "moused".
> | >
> | > Looks like XFree-4 does not like moused for some
On Thu, Jan 18, 2001 at 02:23:30PM +0100, Jimmy Olgeni wrote:
>
> Latest discovery: the mouse will work fine if you choose "/dev/pms0"
> and "auto" as mouse device and protocol type. But you have to kill
> "moused".
>
> Looks like XFree-4 does not like moused for some reason...
>
> --
Sure n
"Michel Talon" <[EMAIL PROTECTED]> wrote:
> On Thu, Jan 18, 2001 at 02:23:30PM +0100, Jimmy Olgeni wrote:
> >
> > Latest discovery: the mouse will work fine if you choose "/dev/pms0"
> > and "auto" as mouse device and protocol type. But you have to kill
> > "moused".
> >
> > Looks like XFree-4 do
We brought up a new box on a January 9th build of 4.2 stable.
Everything seemed fine until we fired up gated 3.6 public (current
port). gated comes up properly but it won't talk OSPF at all (other
OSPF routers never see any OSPF packets and gated_dump shows no
OSPF activity). The config file is
At 11:31 AM 1/18/01 -0500, Michael R. Wayne wrote:
>I did not notice anything on freebsd-stable regarding this lately but
>it's possible that it was buried under something else and I missed it.
I have gated running OSPF on a bunch of 4.x boxes. Are you sure you have
all the correct kernel params
> "WD" == William Denton <[EMAIL PROTECTED]> writes:
WD> Hi,
WD> I saw someone ask about this last year, but I don't think there was a
WD> reply, and the situation hasn't changed. Are there any plans to upgrade
WD> the version of Perl's CGI.pm in the source tree?
I don't think it should b
Hi guys,
I updated my ports, and wheni try installing pine i get an error.
===> Extracting for pine-4.31
>>Checksum OK for pine4.31.tar.gz.
===> pine-4.31 depends on shared library: c-client4.8 - not found
===>Verifying install for c-client4.8 in /usr/ports/mail/cclient
===> Extracting f
I hate that when that happens. It has happened with a lot of ports lately
(i.e. unixODBC). I usually figure the port was upgraded but the patches
weren't removed - so I remove them. It usually works :(
Tom Veldhouse
[EMAIL PROTECTED]
- Original Message -
From: "Nader Turki" <[EMAIL PR
> > I strongly suspect its an IRQ conflict. Every problem of this sort
> > that I've seen with the A7V has been an IRQ conflict, including the
> > problem I had with my own. Specificly I had to hard set the IRQ on my
> > NIC through the PCI management section of the bios.
...
> It certainly is an
Jamil Taylor wrote:
> > Do you still have that kernel config file handy? Maybe I'll try it on our
> > 620s.
>
> I will send my kernel config under separate email.
Now we're getting somewhere!
Running a kernel compiled from your config file, the system runs stable
with both CPUs turned on. I'm
13 matches
Mail list logo
