In muc.lists.freebsd.questions, you wrote:
>
> Does anyone know of support for this PCMCIA card in FreeBSD? I have looked
> everywhere and can't seem to find it anywhere...not good. I also have a
> Linksys LANmodem 33.6 10Bast-T PCMCIA NIC. Anyone know if that one is
> supported?
For those inter
I upgraded my 4.0-release laptop to 5.0-current today and my xe0 was
recognized by the driver and everything was great.
There is a minor nit about the permissions on /dev. It was not readable
by others. So ps wouldn't work, because it could not open /dev/null.
-Arun
To Unsubscribe: se
"Jordan K. Hubbard" wrote:
>
> No, I don't mean rodents who've nibbled on chocolate-covered expresso
> beans, I mean PS/2 mice which fall victim to this new problem:
>
> May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
>
> I've seen it for the last few weeks and can only thin
On 22-May-00 Kazutaka YOKOTA wrote:
>
> Please, if you can avoid it, don't unplug and replug the mouse while
> the power is on. The PS/2 mouse interface is generally not capable
> of hot plugging/unplugging.
>
> As for sleep/wake-up problem on the laptop computers, you may
> be able to resolve
Kazutaka YOKOTA wrote:
>
> >> FWIW, those are all the symptoms of this problem too. The mouse
> >> doesn't just jump, it goes nuts with simulated button events. :)
> >
> >This can really suck with certain email clients, too.
> >
> >My hardware: Sony VAIO PCG-F160 w/integrated trackpad:
> >
> >
>> FWIW, those are all the symptoms of this problem too. The mouse
>> doesn't just jump, it goes nuts with simulated button events. :)
>
>This can really suck with certain email clients, too.
>
>My hardware: Sony VAIO PCG-F160 w/integrated trackpad:
>
> psm0: irq 12 on atkbdc0
> psm
>> > Um, if you don't see the above message but see erratic mouse
>> > behavior, then there may be a configuration problem (for moused or
>> > X), or a hardware problem.
>
>Well, the mouse is fairly new (less than 6 months) and otherwise works like
>a charm. I never saw this before 4.0, but that
"Jordan K. Hubbard" wrote:
>
> > I haven't seen this message, but I _have_ been seeing an off-and-on problem
> > where my PS/2 (Logitech Firstmouse) mouse will go insane. Just moving it
> > causes clicks, wild pointer motion, all sorts of stuff. I usually have to
>
> FWIW, those are all the sy
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> "David O'Brien" writes:
> : On Thu, May 11, 2000 at 12:48:40PM -0600, Warner Losh wrote:
> : > In the US, how do I get the same thing for C++?
> :
> : http://web.ansi.org/public/std_info.html
> :
> : Search for "C++":
> :
> : ISO/IEC 14882:199
Mike Smith wrote:
> > >I haven't seen this message, but I _have_ been seeing an off-and-on problem
> > >where my PS/2 (Logitech Firstmouse) mouse will go insane. Just moving it
> > >causes clicks, wild pointer motion, all sorts of stuff. I usually have to
> > >log in from another box and kill an
In message <[EMAIL PROTECTED]> Kazutaka YOKOTA
writes:
: But, there now are so many dumb KVMs which screw us, and we may have
: to accept that...
Yes. I've been cursed to use some of the dumb KVMs at work. It got
so bad that I've connected my mouse directly to the main machine and
not run X on
> >I haven't seen this message, but I _have_ been seeing an off-and-on problem
> >where my PS/2 (Logitech Firstmouse) mouse will go insane. Just moving it
> >causes clicks, wild pointer motion, all sorts of stuff. I usually have to
> >log in from another box and kill and restart moused; that fix
>> I've seen it for the last few weeks and can only think that something
>> must be stomping on the psm driver now (or the driver is missing
>> interrupts for reasons of its own). Anyone else seeing this?
>
>Yes, recently on 4.0-stable, though provoked by unplugging and
>replugging in the mouse.
>> May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
>>
>> I've seen it for the last few weeks and can only think that something
>> must be stomping on the psm driver now (or the driver is missing
>> interrupts for reasons of its own). Anyone else seeing this?
>
>I haven't see
>: May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
>:
>: I've seen it for the last few weeks and can only think that something
>: must be stomping on the psm driver now (or the driver is missing
>: interrupts for reasons of its own). Anyone else seeing this?
>
>I see this fr
>May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
>
>I've seen it for the last few weeks and can only think that something
>must be stomping on the psm driver now (or the driver is missing
>interrupts for reasons of its own). Anyone else seeing this?
Do you, by any chance, us
Jonathan Hanna drunkenly mumbled...
>
> > I've seen it for the last few weeks and can only think that something
> > must be stomping on the psm driver now (or the driver is missing
> > interrupts for reasons of its own). Anyone else seeing this?
>
> Yes, recently on 4.0-stable, though provoked
Jonathan Hanna wrote:
> Yes, recently on 4.0-stable, though provoked by unplugging and
> replugging in the mouse. It did not recover. This I thought
> sounded like a PR on the mouse being dead after a wakeup
> from sleep mode.
Come to think of it, I do use a KVM switch, but this usually happens a
On 22-May-00 Jordan K. Hubbard wrote:
> No, I don't mean rodents who've nibbled on chocolate-covered expresso
> beans, I mean PS/2 mice which fall victim to this new problem:
>
> May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
>
> I've seen it for the last few weeks and can
In message <3970.958963729@localhost> "Jordan K. Hubbard" writes:
: No, I don't mean rodents who've nibbled on chocolate-covered expresso
: beans, I mean PS/2 mice which fall victim to this new problem:
:
: May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
:
: I've seen it for
> I haven't seen this message, but I _have_ been seeing an off-and-on problem
> where my PS/2 (Logitech Firstmouse) mouse will go insane. Just moving it
> causes clicks, wild pointer motion, all sorts of stuff. I usually have to
FWIW, those are all the symptoms of this problem too. The mouse
d
Jordan K. Hubbard wrote:
> No, I don't mean rodents who've nibbled on chocolate-covered expresso
> beans, I mean PS/2 mice which fall victim to this new problem:
>
> May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
>
> I've seen it for the last few weeks and can only think tha
No, I don't mean rodents who've nibbled on chocolate-covered expresso
beans, I mean PS/2 mice which fall victim to this new problem:
May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
I've seen it for the last few weeks and can only think that something
must be stomping on the p
In message <[EMAIL PROTECTED]>, Mark Murray writes:
>> > I ask, as my RNG is a kld, and I want it to be as separate as possible
>> > without getting ridiculous.
>>
>> Yes. You could just cut/paste the existing mem.c driver, and remove
>> everything but the random hooks. In your init code regist
In message <[EMAIL PROTECTED]>, Mark Murray writes:
>> > > I want to commit a new /dev/random RSN, so I'll be needing a major
>> > > device; what is the procedure for getting one? I know how to steal one,
>> > > but ISTR that this is not how it is done.
>> >
>> > Just edit sys/conf/majors and cla
I was just wondering what the status on the static in the pcm driver on
the SoundBlaster ViBRA16X is... Just in case anyone forgot what I'm
talking about, almost half the time when I start playing an mp3 or an mpg
movie I get static out of the soundcard instead of music. If I keep
restarting the s
> Yes. Each instance of make_dev() takes a cdevsw argument for the minor numbe
r
> in question. So, you could have /dev/mem read/write/ioctl etc routines
> for major 2, minor 0 and 1, while have minors 3 and 4 being installed with
> their own open/close/read/write/etc routines.
>
> Devices are
> > I ask, as my RNG is a kld, and I want it to be as separate as possible
> > without getting ridiculous.
>
> Have a look at http://jeroen.vangelderen.org/FreeBSD/misc_device .
Thanks! You have some good ideas in there; I may just borg some of them.
:-)
M
--
Mark Murray
Join the anti-SPAM mov
Mark Murray wrote:
>
> > > > I want to commit a new /dev/random RSN, so I'll be needing a major
> > > > device; what is the procedure for getting one? I know how to steal one,
> > > > but ISTR that this is not how it is done.
> > >
> > > Just edit sys/conf/majors and claim the next available numb
> On Sun, May 21, 2000 at 09:53:18AM +0200, Mark Murray wrote:
> > I want to commit a new /dev/random RSN,
>
> Forgot to mention, please keep in mind this needs to be MI.
> sys/kern_random.c (which was sys/i386/isa/random_machdep.c) still is
> *very* ugly from a MI point of view. Any changes to
On Sun, May 21, 2000 at 09:53:18AM +0200, Mark Murray wrote:
> I want to commit a new /dev/random RSN,
Forgot to mention, please keep in mind this needs to be MI.
sys/kern_random.c (which was sys/i386/isa/random_machdep.c) still is
*very* ugly from a MI point of view. Any changes to kern_random.
On Sun, May 21, 2000 at 09:53:18AM +0200, Mark Murray wrote:
> I want to commit a new /dev/random RSN, so I'll be needing a major
> device;
Why can't you just rip out the existing random stuff and put in your new
stuff -- keeping the major and minor numbers the same?
--
-- David ([EMAIL PROTEC
> > I ask, as my RNG is a kld, and I want it to be as separate as possible
> > without getting ridiculous.
>
> Yes. You could just cut/paste the existing mem.c driver, and remove
> everything but the random hooks. In your init code register minors 3 and
> 4, and that's all you have to worry abo
Mark Murray wrote:
> > > > I want to commit a new /dev/random RSN, so I'll be needing a major
> > > > device; what is the procedure for getting one? I know how to steal one,
> > > > but ISTR that this is not how it is done.
> > >
> > > Just edit sys/conf/majors and claim the next available number
> > > I want to commit a new /dev/random RSN, so I'll be needing a major
> > > device; what is the procedure for getting one? I know how to steal one,
> > > but ISTR that this is not how it is done.
> >
> > Just edit sys/conf/majors and claim the next available number.
>
> You don't need one. Yo
Doug Rabson wrote:
> On Sun, 21 May 2000, Mark Murray wrote:
>
> > Hi
> >
> > I want to commit a new /dev/random RSN, so I'll be needing a major
> > device; what is the procedure for getting one? I know how to steal one,
> > but ISTR that this is not how it is done.
>
> Just edit sys/conf/major
On Sun, 21 May 2000, Mark Murray wrote:
> Hi
>
> I want to commit a new /dev/random RSN, so I'll be needing a major
> device; what is the procedure for getting one? I know how to steal one,
> but ISTR that this is not how it is done.
Just edit sys/conf/majors and claim the next available number
On 21 May, Hajimu UMEMOTO wrote:
[kris CCed, I think hi knows how to handle this]
> Alexander> after a new build{world,kernel} after the import of OpenSSH 2.1 to
> Alexander> internat (cvsupped 2517, around 14:00 CEST), xdm gets a signal
> Alexander> 11 if I use pam_ssh.so (after entering th
Hi
I want to commit a new /dev/random RSN, so I'll be needing a major
device; what is the procedure for getting one? I know how to steal one,
but ISTR that this is not how it is done.
Also - Peter said something about the "mem" device needing
to only contain the /dev/mem and /mem/kmem devices, a
39 matches
Mail list logo
