> > The problem springs, I think, from confusion between (Intellimouse) and
> > (!Intellimouse). The box pretends to be an Intellimouse even when you
> > don't have one [or this is what seems to happen in my case], and so
> > FreeBSD detects that you have an Intellimouse. However, then it all
>
>Is there any support for the wheel in FreeBSD/X, the moused man page seems
>to suggest there is but I've not managed to get it to do anything yet.
>
>Paul.
You will find the following URL useful to utilize the wheel in
the X environment.
http://www.inria.fr/koala/colas/mouse-wheel-scro
>On Tue, 20 Jul 1999, Warner Losh wrote:
>
>> I had problems with the my Kensignton mouse in a box, but some fixes
>> were made to -current that fixed the problems. A workaround is to set
>> flags 0x20 (the NOIDPROBE) which forces it to behave as if it were a
>> plain old 2 button (or in my cas
>Does this look right? Without this patch, my AXP was memory faulting
>every time it booted, in the dev2udev routine.
I am afraid this is not quite right.
Bruce, Doug and I are currently in discussion to fix this.
Kazu
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freeb
>> I am afraid this is not quite right.
>>
>> Bruce, Doug and I are currently in discussion to fix this.
>
>Hrm. Why does the AXP cons.c track udev_t while the x86 verson
>doesn't? As best as I can tell, the AXP doesn't seem to need it any
>more than the x86 does, unless I've missed something.
> For those of you who may not have seen this, and my apologies
>if I haven't seen it and everyone else has...
[...]
>===> en/handbook
>/usr/local/bin/jade -V html-manifest -ioutput.html -c /usr/doc/share/sgml/cat
>alog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/shar
>At this point we must still be in freebsd xinit, then XF86_VMware(linux
>server) get started. I'm running a linux X server under freebsd. Under
>3.2R all I had to do was change the symlink for X to point to XF86_VMware,
>under -current /dev/tty0 can't be found.
>
>Where was linux "/dev/tty0"
>> >At this point we must still be in freebsd xinit, then XF86_VMware(linux
>> >server) get started. I'm running a linux X server under freebsd. Under
>> >3.2R all I had to do was change the symlink for X to point to XF86_VMware,
>> >under -current /dev/tty0 can't be found.
>> >
>> >Where was
>There have been a few posts on -misc and on the XFree86 newsgroup
>reporting problems when using certain video adapters (The Voodoo 3 was
>one of them) w/ XFree86 3.3.4 on CURRENT. Symptoms varied from
>"pixelisation" when switching back to text mode, to "ghost" white lines
>when dragging window
>I have switched graphics card from S3Virge to ATI Mach64 RagePro rev 92
>with 8 MB RAM a I have noticed that VESA module doesn't work with this
>graphics card on my -current box - I can't use VESA_XXX console modes now.
>Command kldstat says there is loaded module vesa.ko. No errors are
>reporte
[...]
>I also get the keyboard problem periodically, and I've been
>trying to isolate just what I do to cause it. Generally, if I
>reboot and don't hit a key before FreeBSD boots, it never
>happens. If I tap enter to abort the countdown, the keyboard
>scrambles perhaps one time in five.
If you hi
>I second this. I'm not a linux user, but as a FreeBSD newbie
>I had a lot of trouble getting anywhere with console programs,
>esp. emacs and various IDE's that I tried to install. The key
>board mapping was difficult/impossible to figure out, and it
[...]
If the program in question is written
Oops, sorry. Apply the attached patch to /sys/modules/ukbd/Makefile.
Kazu
>A buildworld done in the last hour with a fresh cvsup fails with the
>following:
>
>touch opt_usb.h
>echo > ukbd.h
>echo '#define KBD_INSTALL_CDEV 1' > opt_kbd.h
>rm -f .depend
>mkdep -f .depend -a -nostdinc -D_KERNEL
Hi,
I am experiencing the same problem on the 4.0-CURRENT system
built from the source around Saturday. Another -CURRENT box,
for which 'make world' was done from the source about a week ago,
appears to have no problem.
I suspect `portmap' is somewhat broken. In addition to `rpc.statd',
`nfsd'
>i have uploaded a new bios (6btm0c23.bin, 1999/12/23) into Chaintech 6BTM
>motherboard and faced with a problem. my Genius NewScroll PS/2 mouse is
~
NetScroll?
>not functioning under FreeBS
>Hi, I've noticed a strange problem with vidcontrol and moused recently
>with current. I also had the same problem about 3 weeks back, and it
>doesn't seem to be occurring all that regularly.
What type of mouse is it, PS/2, serial, or USB? Is the power supply
in your system big enough? Is the
>It seems that recent kernels have problems initialising syscons in VESA pixel
>modes. Particularly "vidcontrol VESA_800x600" (actually "vidcontrol
>VESA_800x600 < /dev/ttyv1" to see what's going on ttyv0) command make my kerne
>l
>panicing with the following output:
[...]
>Looking into nm /kernel
for 4.0-CURRENT
24 January 2000
Kazutaka YOKOTA, [EMAIL PROTECTED]
This patch adds support for the following PS/2 mice to the psm driver.
- Microsoft IntelliMouse Explorer: 2 buttons on top, 2 side buttons
and a wheel which also acts as the middle button.
- Genius NetScroll Optical: 2 buttons
>Could someone with a recent (ie < 1 week) -CURRENT confirm whether they
>have problems booting their system when setting allscreens_flags to
>"VESA_800x600"? I have now verified the problem with two different
>systems -- Compaq Professional Workstation 5100 (UP, Matrox Millenium
>II) and Intel P
>Well, it's an ISA bus mouse. I bought this thing back in 1994. It's
>an IMSI mouse. I'll bet this stupid thing could last for 5 more
>years. :-)
>
>> I cannot immediately see why only the mouse suddenly died, while the
>> rest of the system was healthy,
>
>Yeah, I don't know. It happens extre
>>> 3. On the first reboot after installing, the keyboard was in a funny
>>> state.
>
>> Urk, can't reproduce it. I need a reproducible sequence of operations
>> before we'll have any hope of tackling this one.
>
>>> Control-alt-del definitely didn't work, so I had to power off and
>>> reboot. T
>I seem to have this problem occasionaly, the keyboard keymap gets all screwed
>up somehow, and the only way to get out is to hit the reset button. But I've
>been having the problem for a long time, and with different boxes. It happens
>about every 1 out of 15 reboots but randomly. I haven't been
>> In message <[EMAIL PROTECTED]> Mike Smith writes:
>> : It doesn't do anything to the keyboard, it just calls the BIOS to find
>> : out whether keys have been pressed.
>>
>> I've been seeing the hit twice fast problem for months.
>
>It's always been a problem; we don't understand the mechani
>Do you have specs on the Trackpoint PS/2 mice found on Thinkpads?
No.
>The version on my 770X has a double click by "pushing hard on the
>trackpoint" feature. It also has the ability to do the scroll
>thing if you hold the middle mouse button and move the trackpoint.
You mean, there feature
Ok, guys.
This is another patch for the atkbd driver. I expect this one is
better than my previous one. Remove the previous patch and try this
one instead. Stress the keyboard (like hitting the Return key twice
when booting the system), and see if it works.
Thank you.
Kazu
>> I have on a nu
Oops, my loopback (lo0) was down. It's a pilot error. Sorry for the
false alarm. `portmap' is OK in -CURRENT.
Jeffrey, your problem may be the same as mine. You had better check
`network_interfaces' in /etc/rc.conf. It should have `lo0' together
with all other network interfaces. Or, it sho
>On Tue, Feb 08, 2000 at 11:44:41PM +0900, Kazutaka YOKOTA wrote:
>> >On a recent -current (don't know if this is a known problem),
>> >when cursor is switched off on one virtual console, it is
>> >turned off on *all* virtual consoles. Any patch to try?
>
>On Wed, Feb 09, 2000 at 08:35:07PM +0200, Ruslan Ermilov wrote:
>> Hi!
>>
>> 1. Set cursor "blinking" or "destructive" (SC_BLINK_CURSOR)
>> 2. Press Scroll Lock (cursor will go away)
>> 3. Switch to another vtyX
>> 4. Switch to the original vty, where you pressed Scroll Lock
>> 5. Watch the curs
>Last cvs was a few hours ago and world was installed.
>A kernel built from this cvs hangs dead-hard when moused runs from
>rc.i386 and no mouse is plugged into the psm0 port
>
> device psm0at atkbdc? irq 12
>
>The moused config is:
>
>moused_enable="NO" # Run the mouse
>> o Is there a way to increase the number of lines of console output that are
>> "remembered" when you hit Scroll-Lock. Is this the MSGBUF_SIZE parameter?
>> What would be the consequences of increasing this slightly? e.
>
>The value compiled into the kenrnel is set with SC_HISTORY_SIZE; see
>> >moused_enable="NO" # Run the mouse daemon.
>> >moused_type="mousesystems" # See man page for rc.conf(5) for available
> se
>> >ttings.
>> >moused_port="/dev/cuaa0" # Set to your mouse port.
>> >moused_flags="" # Any additional flags to moused.
>>
>> Your configuration refer
file. (Please
examine README first when using the patches. It contains some more info
than extracted here.)
Kazu
=
Assorted patches for 4.0-CURRENT.
12 February 2000
Kazutaka YOKOTA
This archive contains assorted patches for 4.0
>The fact remains, however -- If moused_enable is set to YES, and the
>mouse is not present, the kernel crashes when trying to start moused,
>and it crashes VERY hard. It is a total freeze.
>This crash is the issue. I'm pursuing the fact that if this is
>reproducible elsewhere that it is unacc
>The following is, as indicated, a kernel built from Jan 24 cvs snap.
>Everything with this kernel is fine.
>
>ttyp1:--ROOT--@portley (2)# uname -a
>FreeBSD portley.mrynet.com 4.0-CURRENT FreeBSD 4.0-CURRENT #24: Mon Jan 24
> 17:36:27 PST 2000
>[EMAIL PROTECTED]:/usr/src/sys/compile/PO
>On -current my VGA card is being used as a CGA card. It is correctly
>recognized as a VGA:
>
>vga-pci0: mem 0xf800-0xfbff irq 11 at d
>evice 15.0 on pci0
The above message simply means that a PCI card classified as VGA is
found. This does not necessarily means that the card can be use
>> Possible Problem 3
>During setup, I configure my Intellimouse as an "Intellimouse" on port
>"ps/2". The mouse cursor works as it should but during boot I get the
>following diagnostic:
>
>rc.i386 configuring syscons: blank_time mousedmoused: mouse type mismatch
>(ps/2 != intellimouse), ps
>>>rc.i386 configuring syscons: blank_time mousedmoused: mouse type mismatch
>>>(ps/2 != intellimouse), ps/2 is assumed
>>
>> If you read the notice in the mouse configuration screen, you should
>> have understood that you should ALWAYS choose the type "Auto" for ANY
>> mouse connected to the PS
>1. The kernel compiled from GENERIC doesn't find my PS2 mouse.=20
>2. 'options XSERVER' renders the kernel incapable of booting. The
>config file is included below.
>3. Adding 'device pcm0' also makes the kernel unable to boot. The
>bootloader loads, tries to load the kernel and freezes up.=20
>I have 2 issues with 4.0-CURRENT. The first is the plethora of
>"microuptime() went backwards..." errors that scroll on my console.
>
>The second is that I have DDB compiled into my kernel (and a USB keyboard)
>either on vga or serial console, if I trip DDB (control-shift-esc), I will
>either g
In the last few days, I occasionally see the following message when I
boot the 4.0-CURRENT kernel.
AP #1 (PHY# 1) failed!
panic y/n [y]?
This doesn't always happen. But, roughly once in a few reboots. My MB
is Gigabyte GA-6BXD with two Celerons (400MHz).
Do I have a hardware problem? How shou
>Maybe there is a valid reason for this, but when I attempt to boot the 4.0
>kern.flp without a keyboard attached (I share one keyboard between four
>systems, here), it displays keyboard: no and the BTX loader message, and
>ceases to display ANY output on the attached monitor (though it does
>cont
>On my -current system, after rebooting, the keyboard was in a funny state
>(all 4 LEDs were turned on. My keyboard also has an internal click
>mechanism, which was no longer functional) I plugged the keyboard into
>another machine at that point, and it reset itself and worked fine on that
>mac
>> >And, if not, could
>> >the loader at least not display a message on the local monitor like
>> >"Switching output to serial console...", or better yet, "Switching output
>> >to serial console in 10 seconds.. press any key to abort"?
>>
>> Which key do you mean? The system has found no keyboa
>I don't make a habit of keyboard swapping, and I HAVE experienced some
>minor glitches before (such as weird scan codes being sent, or the state
>of caps lock changing).
You have been lucky that you didn't broke the motherboard when swapping
the keyboard.
The fact that you only had minor prob
>> It's indeed inconvenient that you cannot safely hot-plug the keyboard.
>> And the world is heading for the USB standard... :-)
>
>This actually opens another entire can of worms; detecting a USB keyboard
>at the bootstrap level is _not_ easy. It looks like at least some
>systems aren't sett
>> Why not just get a decent monitor/keyboard switch? Belkin makes a
>> nice 4-port in the $200 range that makes your motherboard think
>> there's a keyboard attached even if you are not currently switched
>> onto the system.
>
>I have something quite similar.. Still, seems like some individuals
>linking kernel.debug
>psm.o: In function `psmprobe':
>/sys/compile/RJK191/../../isa/psm.c(.text+0x9fe): undefined
>reference to `atkbdc
>_open'
>*** Error code 1
>
>I know psm.c was changed today, I'd suppose one reference here was
>missed in the process. Just figured I'd be the first to say so.
>After a cvsup today, building a kernel finishes with this:
>
>linking kernel.debug
>psm.o: In function `psmprobe':
>/sys/compile/RJK191/../../isa/psm.c(.text+0x9fe): undefined
>reference to `atkbdc
>_open'
>*** Error code 1
>
>I know psm.c was changed today, I'd suppose one reference here was
>m
>I'm trying to get VESA_800x600 mode to work on my notebook (Toshiba
>SatellitePro 445, CT65554 videocard, 2MB, 800x600 LCD), and
>unfortunately found that it is impossible. Any ideas of what is wrong?
You need to add
options SC_PIXEL_MODE
to your kernel configuration file.
There is
>> OK. Probably `slept 00:00:00 - 00:00:40' problem was caused by PS/2
>> mouse, I think. Do we need something to do with psm on suspending as
>> well as resuming?
>
>Im not sure anything needs to be done for PS/2.. check out these
>results..
The PS/2 mouse generates interrupt when /dev/psm0 is
>I've noticed some odd syscons keyboard behaviour over the past
>month or so. Sometimes I get a vty that outputs PC graphics characters
>for all of my input. This is always at a "login:" prompt. I think
>I can duplicate this by typing a bunch of garbage at a login prompt,
>but I don't feel lik
Becase of the following change in /sys/dev/syscons, you need to
recompile both the kernel, the vesa module and screen savers.
# Well, if you don't use the vesa module and the screen savers,
# you can forget about this :-)
Thank you for your cooperation.
Kazu
>yokota 1999/09/19 01:58:54 P
AFAIK, not all video cards generate the vertical retrace interrupt.
Even worse, some BIOSes have a configuration option which instract the
BIOS NOT to assign an IRQ to the PCI video card.
I fully agree that the vertical retrace interrupt will be of great
value, but I wonder if it is really worth
>> Well, I may be wrong :-)
>
>Well, sortof :)
>
>The delay caused by the system to process the interrupt and deliver
>the signal etc is unpredictable (well sortof) and is almost certainly
>too long so the window of opportunity will be missed ...
>
>This has been discussed to death many times in
>Today I noticed accidentally that either libvgl is broken, or the demo
>program does something wrong - the mouse cursor doesn't move.
Oops, sos and I have developed a new version of libsvgl which can
handle VESA modes in addition to the standard VGA graphics modes.
But I haven't committed it to
>Any docs for e.g.the fb device? I know,you can always UTSL, but it takes
>more time.
No docs yet, sorry.
>OBTW. there is an error in mouse(4) manpage. The ioctl is called
>MOUSE_GETSTATUS, not MOUSE_GETSTATE as the manpage claims.
Thank you for spotting the error! I will fix it.
Kazu
To
Four patches for review and test. They are for 4.0-CURRENT.
(moused patch should also work with -STABLE too.)
http://www.freebsd.org/~yokota/moused-991129.diff
http://www.freebsd.org/~yokota/kbdcontrol-991129.diff
http://www.freebsd.org/~yokota/panickey-991129.diff
http://www.freebsd.org/~yokota
I have been contemplating replacing our
/usr/src/share/termcap/termcap.src with the latest termcap file
maintained by Eric Raymond. His latest version seems 10.2.7 dated 10
March 1999.
While our termcap.src has been maintained well by ache and other
committers, Eric's version appears more compre
>I'm using non-standard 100x37 console mode on my notebook, because in 80x25
>text mode letters seems too big for my 12' panel, while other modes doesn't
>cover all panel size. So I've patched vidcontrol to switch to the VESA_800x600
>100x37 mode (instead of default 80x25) with 8x16 font, and in m
>Yes. I know about this problem too but I have no time to fix and test
>it. Is anybody interested in bug reports? ;-)
>
>* Left margin moving to the right is related to the screen width not
> divisible by 8 and an use of tabulators at the end of line after the
> last valid tab position. So the s
>Is there any way to use only the USB KLDs (i.e. remove all the USB
>options from the kernel config file) on a machine that has an USB
>keyboard?
Add "flags 0x100" to syscons. Note this is still an experimental
flag.
device sc0 at isa? flags 0x100
>I tried doing this (removed all the USB opti
Thank you for your detailed report.
>I added your recommendations above to the kernel config file
>(TWELVE). It didn't work. As can be seen from the dmesg below, when
>the USB options are present in the kernel, ukbd0 is found. When USB
>KLDs are used, uhid0 seems to grab the keyboard.
>
>[This is
>> I'm not yet 100% convinced that it would make sense to separate
>> the propellers code into a module. Is 5 Kbyte of kernel code
>> really that much of a problem? Please note that
>
>I certainly wouldn't argue this based on size, no. To understand the
>point I was arguing, consider what woul
>To Do list for the USB project:
>
>Let meknow if you would like to participate in any way, or you have
>done one of the items below!
[...]
>- USB Keyboards
>- Keyboard in DDB debugger does not work.
In what configuration does it not work? I can use my USB keyboard in
DDB without problems o
>To Do list for the USB project:
[...]
>- USB base stack and general items.
I am currently having trouble with Gigabyte GA-6BXD, dual Pentium III
motherboard. If I boot a UP kernel (5.0-CURRENT), the PIIX4 USB
controller works fine.
If I boot a SMP kernel (the only difference from the UP kerne
>What does it say before this info?
In dmesg.boot (after `boot -v' at the loader prompt):
uhci0: port 0xe000-0xe01f irq 15 at device
7.2 on pci0
uhci0: LegSup = 0x0010
uhci_run: setting run=0
uhci_run: done cmd=0x80 sts=0x20
uhci_run: setting run=1
uhci_run: done cmd=0x81 sts=0x0
usb0: on
>This has been fixed in both -STABLE and -CURRENT a week ago. The left
>button is working, the timeout is just to long. Read moused manpage
>and set the timeout to 200ms as a workaround (this is the default
>according to the manpage, but not according to the code in
>4.0-RELEASE).
>
> Sam
200 m
>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
>: 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?
>
>I haven't see
>> 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.
>> > 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
>> 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
>Try flags 0x04 on device psm.
>
>This undocumented option fixed my PS/2 IntelliMouse clone that has a
>wheel (which is also the center button).
As you have not given details on your problem and mouse,
I don't understand why this flag solved your problem...
That flag simply sets the mouse's reso
>> 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?
>
> FWIW, with -current from 5/8, I don't have any of those in
>/var/log/messages, goi
>I see those messages, however I do not have any problems mousing afterwards.
>I'm using a switchview, which at least resets the mouse when I switch.
Your Logitech 3-button mouse may be generic enough and is not affected
much by power cut when you use the KVM. Which model is it?
>On Sun, May 2
>I stopped using moused sometime during 4.0-current as a result of this.
When was it?
>It ocasionally froze, moved randomly around the screen, clicked without
>being touched, and yes, got extreamly jumpy. The hardware's rock solid,
>and once I ditched moused and read the device directly, life
>Yes. Just today, I was installing a Digital PC with 4.0-release. Before
>start using it, I upgraded to 4.0 Stable. Then I starded configuring X.
>
>FYI:
>
>FreeBSD 4.0-STABLE #0: Wed May 24 13:34:42 GMT 2000
>CPU: Pentium II/Pentium II Xeon/Celeron (265.75-MHz 686-class CPU)
>psm0: irq 12 on at
>I've tried to get a splash screen with two different 320x200x256
>bitmaps now, and all I get is a blank screen. Is there something else
>I'm missing?
Would you type 'boot -v' at the boot loader prompt and
send me /var/run/dmesg.boot? I also like to see the output
from 'vidcontrol -i mode' and '
Ok, folks. This is a test patch for the psm driver. I would like you
to do some test for me.
This is NOT the fix for the infamous "psmintr out of sync" message,
but is a test patch to see how things are on your machines. The patch
is for both CURRENT and STABLE.
Please apply the patch to /sys
>Okay, answering my own question for the sake of the archive, I believe it
>was an on combination of some of the options SC_something that
>vidcontrol -m on and my mouse and kernel didnt like. I was using some to
>save on kernel size and memory used but then decided to start using the
>compu
>After taking the patches for config and booting my box reboots
Which patch is it?
Kazu
>because I have:
>
>#allscreens_flags="-m on 80x50"
>#saver="logo"
>#font8x8="cp437-8x8"
>#font8x14="cp437-8x14"
>#font8x16="cp437-8x16"
>
>enabled in my rc.conf, a kernel from ~2 days ago is fine with this
>I already sent a mail about this problem a while ago, but it has not
>been solved yet. I mail again because I've made a mistake describing the
>problem. So, the problem was that when i type "vidcontrol VESA_800x600",
>it makes my box crash. I first thought that this was making my box
>reboot
Try the attached patch for /sys/isa/psm.c, and please report the
result.
Kazu
>Robert Watson wrote:
>>
>> I'm using a Micron P133 box with a PS/2 mouse. Up until this morning, I
>> was running 4.0-STABLE from a month or two back. I upgraded to
>> 5.0-CURRENT, and since that time, my mouse has
>Kazutaka YOKOTA wrote:
>>
>> Try the attached patch for /sys/isa/psm.c, and please report the
>> result.
>
>Actually, I use the mse0 device, because I have an isa bus mouse.
>
>--
>- Donn
Robert, I still want you to try my patch, as you are using the PS/
>I have a Logitech Trackball. I have tried it on the serial port
>and the PS/2 port and have the same problem in both places:
>
>5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Jul 27 06:00:20 EDT 2000
>XFree86-3.3.6 and
>TkDesk-1.2
>
>I right click on a directory or file in TkDesk, and a popup menu
>app
>Donn, would you please run moused at higher priority, (for example,
>"nice -5 moused..." or "nice -10 moused...",) in order to see if this
Oh, I meant "nice --5 mouse..." and "nice --10 moused..." :-)
Kazu
>is caused by moused somewhat not running in a timely manner.
>
>Kazu
To Unsubscribe:
>> Oh, I meant "nice --5 mouse..." and "nice --10 moused..." :-)
>
>Tried this. It doesn't fix the problem. The mouse is still jumpy no
>matter what the nice level. I believe it's a problem with syscons as
>a whole. For example, whenever I switch to a VC and do kbdcontrol -r
>240.34 to get a
>On Sun, 6 Aug 2000, Warner Losh wrote:
>
>>In message <[EMAIL PROTECTED]> Warner Losh writes:
>>: The reason you have a ISA to PCI bridge still is that the serial
>>: ports, parallel ports, floppy, keyboard and mouse devices still live
>>: on the ISA bus. They aren't full PCI nodes just yet in m
>Until yesterday, I was running -CURRENT from around July 4th on my
>notebook, given that I was travelling and unwilling to break my means of
>giving presentations on my trip :-). Yesterday, I decided to upgrade, and
>built kernel/world. The userland stuff appears to work fine, but
>interestingl
>The loader now detects ACPI in your system, and loads the ACPI
>module if it is present. This has major ramifications for the
>device probe and attach phases of system initialisation.
>
> - Root PCI bridges are detected using ACPI.
> - PCI interrupt routing is now performed using ACPI.
> - The
>So i can't use X server. The problem appeared right after i've compiled
>and installed freshly cvsuped kernel after new acpi first commit (31.08).
>I'm sending dmesg and kernel config files in attach, and waiting for
>help/comments. Thank you.
Please apply the attached patch in /sys/isa and see
>So i can't use X server. The problem appeared right after i've compiled
>and installed freshly cvsuped kernel after new acpi first commit (31.08).
>I'm sending dmesg and kernel config files in attach, and waiting for
>help/comments. Thank you.
Please apply the attached patch in /sys/isa and see
>> Please apply the attached patch in /sys/isa and see what it does.
>It does panic with a smiling face ;-)))
>
>panic message was "bad ivar read request"
Would try the following patch for /sys/isa/psm.c IN ADDITION TO
my previous patch?
(This is a test patch. It's not a final fix.)
Kazu
--- p
>> Would try the following patch for /sys/isa/psm.c IN ADDITION TO
>> my previous patch?
>>
>> (This is a test patch. It's not a final fix.)
>
>panic: nexus_setup_intr: NULL irq resource!
Ok, this is one last test patch. Please remove ALL my previous
patches and apply this one in /sys/isa.
Than
I just committed update to the PnP resource parser for the PnP
ISA and PnP BIOS devices. As this is a bug fix, there shouldn't
be any nasty surprises. But, if you have PnP ISA cards and
encounter any problems or suspicious behavior, please report.
Thanks.
Kazu
>yokota 2001/09/04 20:54:33 PD
>> > PS. I just removed and checkout sys/isa.
>> hope you did a "make clean" too...
>I tried this too - nothing changed. :(
>Where is my netscroll genius... I want it back
>;-)
What was the message? Is that the following?
panic: nexus_setup_intr: NULL irq resource!
Or, something else?
C
Thank you. I got the files.
Then, would you remove my previous small patch from psm.c, and put the
following line in /boot/device.hints instead and reboot?
debug.acpi.disable="sysresource"
Or, you may type
set debug.acpi.disable="sysresource"
at the loader prompt before "boot -v".
Kazu
>You
As I wrote in another mail to Harti Brandt and cc'ed to you, it now
appears that ACPI on your motherboard declares IRQ 12 BOTH in the PS/2
mouse resource descriptors and in the system reserved resource
descriptors.
The system reserved resources are sucked by the sysresource driver in
the acpi mo
As reported in this list by several people, you may be seeing that
your PS/2 mouse is not detected after the recent ACPI update.
This seems to be caused by ACPI in some BIOS assigns IRQ 12 (mouse
interrupt) to both the PS/2 mouse device node and the system reserved
resource node.
To see if this
1 - 100 of 180 matches
Mail list logo
