Re: Mouse frozen in X when returning from text console
Something I noticed today: switch to text console from X using C-A-F1; upon return, the mouse cursor is frozen. moused appears to still work because I can cut/paste text in the text console. Restarting moused doesn't help. Yes, I can confirm it. Going back to Xfree 3.3.6 fixes it. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: [EMAIL PROTECTED], Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problem after recent commits to dev/aic7xxx (aic7880)
Hi, after recent commits to dev/aic7 I get timeouts from my hardware at the SCSI-Bus (a CD-ROM an a CDR) and it needs very long to boot. An old kernel boots just fine. The (stripped down) output of a verbose boot: ---snip--- ahc0: Adaptec aic7880 Ultra SCSI adapter port 0xb000-0xb0ff mem 0xd980-0xd9800fff irq 9 at device 6.0 on pci0 ahc0: Reading SEEPROM...done. ahc0: Low byte termination Enabled ahc0: High byte termination Enabled ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 423 instructions downloaded BIOS Geometries: 0:03ffda3f 0..1023=1024 cylinders, 0..218=219 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Waiting 5 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ahc0: target 1 synchronous at 10.0MHz, offset = 0xf (probe2:ahc0:0:2:0): SCB 0x7 - timed out while idle, SEQADDR == 0x195 (probe2:ahc0:0:2:0): Queuing a BDR SCB (probe2:ahc0:0:2:0): SCB 0x7 - timed out while idle, SEQADDR == 0x195 (probe2:ahc0:0:2:0): no longer in timeout, status = 34b ahc0: target 1 using asynchronous transfers ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe2:ahc0:0:2:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe2:ahc0:0:2:0): ILLEGAL REQUEST asc:24,0 (probe2:ahc0:0:2:0): Invalid field in CDB ahc0: target 2 synchronous at 20.0MHz, offset = 0xf ahc0: target 1 synchronous at 10.0MHz, offset = 0xf Creating DISK cd0 Creating DISK cd1 pass0 at ahc0 bus 0 target 1 lun 0 pass0: TEAC CD-R55S 1.0Q Removable CD-ROM SCSI-2 device pass0: Serial Number 8Y24511C pass0: 10.000MB/s transfers (10.000MHz, offset 15) pass1 at ahc0 bus 0 target 2 lun 0 pass1: PIONEER CD-ROM DR-U16S 1.01 Removable CD-ROM SCSI-2 device pass1: 20.000MB/s transfers (20.000MHz, offset 15) Mounting root from ufs:/dev/ad0s2a ad0s1: type 0xc, start 63, end = 6277634, size 6277572 : OK ad0s2: type 0xa5, start 6290928, end = 40031711, size 33740784 ad0s2: C/H/S end 1023/104/63 (14120945) != end 40031711: invalid (cd1:ahc0:0:2:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd1:ahc0:0:2:0): NOT READY asc:3a,0 (cd1:ahc0:0:2:0): Medium not present cd1 at ahc0 bus 0 target 2 lun 0 cd1: PIONEER CD-ROM DR-U16S 1.01 Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present start_init: trying /sbin/init (cd0:ahc0:0:1:0): SCB 0x7 - timed out in Message-in phase, SEQADDR == 0x195 (cd0:ahc0:0:1:0): BDR message in message buffer (cd0:ahc0:0:1:0): SCB 0x7 - timed out in Message-in phase, SEQADDR == 0x195 (cd0:ahc0:0:1:0): no longer in timeout, status = 34b ahc0: target 1 using asynchronous transfers ahc0: target 2 using asynchronous transfers ahc0: Issued Channel A Bus Reset. 1 SCBs aborted ahc0: target 1 synchronous at 10.0MHz, offset = 0xf (cd0:ahc0:0:1:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ahc0:0:1:0): NOT READY asc:4,1 (cd0:ahc0:0:1:0): Logical unit is in process of becoming ready cd0 at ahc0 bus 0 target 1 lun 0 cd0: TEAC CD-R55S 1.0Q Removable CD-ROM SCSI-2 device cd0: Serial Number 8Y24511C cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Logical unit is in process of becoming ready ---snip--- And the output of "ident /usr/src/sys/dev/aic7/* | grep FreeBSD": ---snip--- $FreeBSD: src/sys/dev/aic7xxx/93cx6.c,v 1.6 2000/07/18 20:12:12 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/93cx6.h,v 1.5 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/Makefile,v 1.7 2000/05/27 21:35:47 obrien Exp $ $FreeBSD: src/sys/dev/aic7xxx/ahc_eisa.c,v 1.16 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/ahc_pci.c,v 1.32 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx.c,v 1.47 2000/07/25 20:40:34 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx.h,v 1.21 2000/07/24 22:27:40 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx.reg,v 1.22 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx.seq,v 1.97 2000/07/24 22:27:40 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aicasm.c,v 1.26 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aicasm.h,v 1.9 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aicasm_gram.y,v 1.9 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aicasm_insformat.h,v 1.1 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aicasm_scan.l,v 1.11 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aicasm_symbol.c,v 1.9 2000/07/18 20:12:13 gibbs Exp $ $FreeBSD: src/sys/dev/aic7xxx/aicasm_symbol.h,v 1.9 2000/07/18 20:12:14 gibbs Exp $ ---snip--- Bye, Alexander. -- Press every key to continue. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body
Re: if_tun.ko seems broken
On Wed, 26 Jul 2000 16:26:48 +0100, Ben Smithurst wrote: I think the device needs to be opened before you can do anything with it. PPP of course does this for you, but if you want to ifconfig it yourself you might try something like ``dd if=/dev/tun0 of=/dev/null count=0'' first. Ah, okay. Having said this to the person who swore that ifconfig tun0 worked for him, he now remembers that he doesn, in fact, use ppp(8). :-) Thanks, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: if_tun.ko seems broken
In message [EMAIL PROTECTED], Sheldon Hearn writes: On Wed, 26 Jul 2000 12:33:07 +0200, Sheldon Hearn wrote: Does this have anything to do with your recent change to if_tun.c? Nope. I've reverted rev 1.75 of if_tun.c and the behaviour persists. Someone locally insists that the ifconfig line ifconfig tun0 inet 10.0.0.1 should work. Any ideas? I think you are seing the "interesting" side effect of the BSD concept of "POINT2POINT" lines. I think we should loose that concept in favour of interfaces using a netmask of 255.255.255.255 and let programs like ppp install a hostroute to the other end when it is reachable. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: if_tun.ko seems broken
On Thu, 27 Jul 2000 09:37:11 +0200, Poul-Henning Kamp wrote: ifconfig tun0 inet 10.0.0.1 I think you are seing the "interesting" side effect of the BSD concept of "POINT2POINT" lines. I think that's anotehr issue. Once I'd read 0 bytes from /dev/tun0 with dd(1), I was able to do ifconfig tun0 inet 10.0.0.1 10.0.0.1 which is actually what I wanted. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Broadcast address with DHCP
dhclient seems to be broken, it's giving me the all zeroes broadcast
address instead of all ones:
inet 192.168.91.35 netmask 0xfff0 broadcast 192.168.91.32
(should be broadcast 192.168.91.47)
Index: dhclient.c
===
RCS file: /usr/cvs/src/contrib/isc-dhcp/client/dhclient.c,v
retrieving revision 1.16
diff -u -r1.16 dhclient.c
--- dhclient.c 2000/07/20 19:51:37 1.16
+++ dhclient.c 2000/07/27 12:21:38
@@ -1972,7 +1972,7 @@
if (broadcast.len) {
client_envadd (ip - client,
prefix, "broadcast_address",
- "%s", piaddr (subnet));
+ "%s", piaddr (broadcast));
}
}
}
I think this needs fixing.
--
Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D
FreeBSD Documentation Project /
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
test.
how can i unsubscribe from freebsd-current and subcribe to freebsd-stable, Thanks, Vincent
Re: Mouse frozen in X when returning from text console
On Wed, 26 Jul 2000, Jos Backus wrote: :[This is with yesterdays' -current and today's kernel, and Xfree86 4.0.1 using :the ati driver module.] : :Something I noticed today: switch to text console from X using C-A-F1; upon :return, the mouse cursor is frozen. moused appears to still work because I :can cut/paste text in the text console. Restarting moused doesn't help. : I don't have this problem, using XFree86 4.0.1, the ati module, /dev/psm0, and a current from early june. I do have a problem that some Solaris applications die horrible deaths trying to display on the FreeBSD box. That's probably neither FreeBSD nor XFree's fault though. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mouse frozen in X when returning from text console
On Thu, 27 Jul 2000, David Scheidt wrote: On Wed, 26 Jul 2000, Jos Backus wrote: :[This is with yesterdays' -current and today's kernel, and Xfree86 4.0.1 using :the ati driver module.] : :Something I noticed today: switch to text console from X using C-A-F1; upon :return, the mouse cursor is frozen. moused appears to still work because I :can cut/paste text in the text console. Restarting moused doesn't help. : I don't have this problem, using XFree86 4.0.1, the ati module, /dev/psm0, and a current from early june. I do have a problem that some Solaris One suggestion was made that I might have been the result of the recent changes to the syscons driver ... something about entropy? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mouse frozen in X when returning from text console
Benedikt Schmidt wrote: Same problem here on current (make world + kernel last week) with Xfree86 4.0.1 using a V3000 and and ps2 mouse. I tried using "Device" "/dev/mouse" with moused and "Device" "/dev/psm0" without moused. With both settings the mouse is frozen after switching back to X. I didn't have this problem with Xfree 4.0. It just appeared when I updated to the new 4.0.1 port. I don't have this problem on Linux using Xfree86 4.0.1 on the same computer. This problem is not specifically related to -CURRENT; it happens with XFree86 4.0.1 when the configured mouse protocol is "Auto". Another glitch: "Protocol SysMouse" does not work with moused; however, "Protocol Mousesystems" does. -- JMA ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: test.
On Thu, 27 Jul 2000 16:34:58 +0200, "Vincent Bruijnes" wrote: How can i unsubscribe from freebsd-current and subcribe to freebsd-stable, Thanks, Vincent Send a mail to [EMAIL PROTECTED] (not to this list) with unsubscribe freebsd-current subscribe freebsd-stable in the message body. Further information can be found at http://www.freebsd.org/handbook/eresources.html#ERESOURCES-MAIL -- Robert Drehmel [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mouse frozen in X when returning from text console
On Thu, 27 Jul 2000, Jose M. Alcaide wrote: Benedikt Schmidt wrote: Same problem here on current (make world + kernel last week) with Xfree86 4.0.1 using a V3000 and and ps2 mouse. I tried using "Device" "/dev/mouse" with moused and "Device" "/dev/psm0" without moused. With both settings the mouse is frozen after switching back to X. I didn't have this problem with Xfree 4.0. It just appeared when I updated to the new 4.0.1 port. I don't have this problem on Linux using Xfree86 4.0.1 on the same computer. This problem is not specifically related to -CURRENT; it happens with XFree86 4.0.1 when the configured mouse protocol is "Auto". Another glitch: "Protocol SysMouse" does not work with moused; however, "Protocol Mousesystems" does. Mine is set to (5.0-CURRENT): Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol""MouseMan" Option "Device" "/dev/ttyd1" EndSection And (4.1RC): Section "Pointer" Protocol"MouseMan" Device "/dev/psm0" BaudRate1200 Resolution 100 Buttons 3 EndSection To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Mouse behaving funny since 5.0-CURRENT upgrade
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 been responding slowly and erratically, jumping as it moves, et al. The mouse daemon seems to be consuming more CPU time than I would hope: 389 root 2 0 880K 504K select 0:02 16.28% 5.37% moused (it has been as high as 9%) I'm using the default arguments to moused, with moused enabled in /etc/rc.conf. I'm not sure what changed, but it would be nice if it hadn't :-). Robert N M Watson [EMAIL PROTECTED] http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CFR: apm debug print cleanup and display on/off improvement
Hi, I worked apm debug print cleanup to avoid re-build kernel with APM_DEUG (this kernel option seems unavailable for now) for obtaining debug messages on apm. http://people.freebsd.org/~iwasaki/apm/apm-debug.diff The debug flag can be controlled by sysctl interface and loader setting "debug.apm_debug=1" with this. This patch also includes some enhancements from linux on display control by apm -d. I'm expecting that we can see some improvements on some laptops where apm -d doesn't work correctly so far. I'll commit this comming week end if no objections. Thanks # Yes, I just want to finish apm related work before we concentrate # on ACPI stuff :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Mouse frozen in X when returning from text console
This patch does indeed fix the problem here. Thanks! This should really make it into 4.0.2... ---Jos -Original Message- From: Alexander N. Kabaev [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 26, 2000 8:13 PM To: The Hermit Hacker Cc: [EMAIL PROTECTED]; Jos Backus; Benedikt Schmidt Subject: Re: Mouse frozen in X when returning from text console There was a patch floating around which fixed these mouse problems for me. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mouse behaving funny since 5.0-CURRENT upgrade
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 been responding slowly and erratically, jumping as it moves, et al. I'm using the default arguments to moused, with moused enabled in /etc/rc.conf. I'm not sure what changed, but it would be nice if it hadn't :-). Yep. It's been that way in 5.0-current for about 2-3 weeks now. When I use /dev/sysmouse in X, my mouse is really jumpy. It's so bad that I don't use moused anymore in X. When I use my mouse normally, i.e. without moused (/dev/mouse), in X, mouse movements are OK. Also, cursor motion is jumpy as well. Must be the recent commits to syscons. -- - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mouse behaving funny since 5.0-CURRENT upgrade
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 been responding slowly and
erratically, jumping as it moves, et al.
I'm using the default arguments to moused, with moused enabled in
/etc/rc.conf. I'm not sure what changed, but it would be nice if it
hadn't :-).
Yep. It's been that way in 5.0-current for about 2-3 weeks now. When
I use /dev/sysmouse in X, my mouse is really jumpy. It's so bad that
I don't use moused anymore in X. When I use my mouse normally, i.e.
without moused (/dev/mouse), in X, mouse movements are OK. Also,
cursor motion is jumpy as well. Must be the recent commits to
syscons.
--
- Donn
Index: psm.c
===
RCS file: /src/CVS/src/sys/isa/psm.c,v
retrieving revision 1.27
diff -u -r1.27 psm.c
--- psm.c 2000/07/22 04:08:12 1.27
+++ psm.c 2000/07/27 06:53:24
@@ -1827,9 +1827,11 @@
{
struct psm_softc *sc;
int unit;
+int s;
unit = (int)arg;
sc = devclass_get_softc(psm_devclass, unit);
+s = spltty();
if (sc-watchdog kbdc_lock(sc-kbdc, TRUE)) {
if (verbose = 4)
log(LOG_DEBUG, "psm%d: lost interrupt?\n", unit);
@@ -1837,6 +1839,7 @@
kbdc_lock(sc-kbdc, FALSE);
}
sc-watchdog = TRUE;
+splx(s);
sc-callout = timeout(psmtimeout, (void *)unit, hz);
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
/bin/sh dumps core with here-document of 8bit text
I don't know you are the right person to ask, but I found you committed some of 8bit cleaning in src/bin/sh. Shell script which contains here-document of 8bit text sometimes dumps core. For example, please test this script in 4.1 or -current. #!/bin/sh cat EOF [8bit text which contains 0x82 character] EOF And, if I use 'EOF' instead of EOF, it works fine. Do you have any idea about this behavior? After at a glance of sources, 0x82 is used as CTLVAR control character. I think this should be escaped as CTLESC CTLVAR before examining variable substitution whether here-docuement is quoted or not. -- Jun Kuriyama [EMAIL PROTECTED] // FreeBSD Project 8bit.sh.gz
