From owner-freebsd-mobile Wed Mar 26 01:56:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA00295 for mobile-outgoing; Wed, 26 Mar 1997 01:56:16 -0800 (PST) Received: from f30.hotmail.com (F30.hotmail.com [207.82.250.41]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA00289 for ; Wed, 26 Mar 1997 01:56:13 -0800 (PST) Received: (from root@localhost) by f30.hotmail.com (8.7.5/8.7.3) id BAA17764; Wed, 26 Mar 1997 01:55:39 -0800 (PST) Date: Wed, 26 Mar 1997 01:55:39 -0800 (PST) Message-Id: <199703260955.BAA17764@f30.hotmail.com> Received: from 206.231.1.163 by www.hotmail.com with HTTP; Wed, 26 Mar 1997 01:55:39 PST X-Originating-IP: [206.231.1.163] From: " Patrick Killourhy" To: freebsd-mobile@freebsd.org Subject: XFree86 on hitachi w/ neomagic 128 SVGA controller Content-Type: text/plain Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone out there had any luck running X on a Hitachi notebook (the E133T, specifically) that uses the NeoMagic 128 PCI SVGA controller? This is the same controller as use in the new Dell latitude 133s, i believe, but i haven't seen anything on that one, either. thanks for your help! -p. --------------------------------------------------------- Get Your *Web-Based* Free Email at http://www.hotmail.com --------------------------------------------------------- From owner-freebsd-mobile Wed Mar 26 01:56:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA00316 for mobile-outgoing; Wed, 26 Mar 1997 01:56:29 -0800 (PST) Received: from f21.hotmail.com (F21.hotmail.com [207.82.250.32]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA00311 for ; Wed, 26 Mar 1997 01:56:26 -0800 (PST) Received: (from root@localhost) by f21.hotmail.com (8.7.5/8.7.3) id BAA13992; Wed, 26 Mar 1997 01:55:53 -0800 (PST) Date: Wed, 26 Mar 1997 01:55:53 -0800 (PST) Message-Id: <199703260955.BAA13992@f21.hotmail.com> Received: from 206.231.1.163 by www.hotmail.com with HTTP; Wed, 26 Mar 1997 01:55:52 PST X-Originating-IP: [206.231.1.163] From: " Patrick Killourhy" To: freebsd-mobile@freebsd.org Subject: XFree86 on hitachi w/ neomagic 128 SVGA controller Content-Type: text/plain Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone out there had any luck running X on a Hitachi notebook (the E133T, specifically) that uses the NeoMagic 128 PCI SVGA controller? This is the same controller as use in the new Dell latitude 133s, i believe, but i haven't seen anything on that one, either. thanks for your help! -p. --------------------------------------------------------- Get Your *Web-Based* Free Email at http://www.hotmail.com --------------------------------------------------------- From owner-freebsd-mobile Wed Mar 26 02:39:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA01993 for mobile-outgoing; Wed, 26 Mar 1997 02:39:13 -0800 (PST) Received: from critter.dk.tfs.com (phk.cybercity.dk [195.8.133.247]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA01988; Wed, 26 Mar 1997 02:39:08 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id LAA12019; Wed, 26 Mar 1997 11:38:07 +0100 (CET) To: " Patrick Killourhy" cc: freebsd-mobile@FreeBSD.ORG Subject: Re: XFree86 on hitachi w/ neomagic 128 SVGA controller In-reply-to: Your message of "Wed, 26 Mar 1997 01:55:53 PST." <199703260955.BAA13992@f21.hotmail.com> Date: Wed, 26 Mar 1997 11:38:07 +0100 Message-ID: <12017.859372687@critter> From: Poul-Henning Kamp Sender: owner-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199703260955.BAA13992@f21.hotmail.com>, " Patrick Killourhy" writes : >Has anyone out there had any luck running X on a Hitachi notebook >(the E133T, specifically) that uses the NeoMagic 128 PCI SVGA >controller? This is the same controller as use in the new Dell latitude >133s, i believe, but i haven't seen anything on that one, either. >thanks for your help! Check out the demo from www.xgi.com -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-mobile Wed Mar 26 12:13:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA19036 for mobile-outgoing; Wed, 26 Mar 1997 12:13:18 -0800 (PST) Received: from cise.ufl.edu (root@fireant.cise.ufl.edu [128.227.205.210]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA19016 for ; Wed, 26 Mar 1997 12:13:08 -0800 (PST) Received: from cise.ufl.edu (tick.cise.ufl.edu [128.227.224.30]) by cise.ufl.edu (8.8.5/8.7.1) with ESMTP id PAA21581; Wed, 26 Mar 1997 15:12:40 -0500 (EST) Message-Id: <199703262012.PAA21581@cise.ufl.edu> To: Poul-Henning Kamp cc: mobile@freebsd.org Subject: Re: XFree86 on hitachi w/ neomagic 128 SVGA controller In-reply-to: Your message of "Wed, 26 Mar 1997 11:38:07 EST." <12017.859372687@critter> Date: Wed, 26 Mar 1997 15:12:40 -0500 From: "James F. Hranicky" Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp wrote: > >(the E133T, specifically) that uses the NeoMagic 128 PCI SVGA > >controller? This is the same controller as use in the new Dell latitude > >133s, i believe, but i haven't seen anything on that one, either. > > Check out the demo from www.xgi.com I can't seem to find this address: [jfh@tick:/usr/catman] 83 % nslookup www.xgi.com Server: hail.cise.ufl.edu Address: 128.227.205.72 *** hail.cise.ufl.edu can't find www.xgi.com: Server failed ---------------------------------------------------------------------- | Jim Hranicky, Senior SysAdmin UF/CISE Department | | E314E CSE Building Phone (904) 392-1057 | | jfh@cise.ufl.edu http://www.cis.ufl.edu/~jfh | ---------------------------------------------------------------------- From owner-freebsd-mobile Wed Mar 26 12:37:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA22140 for mobile-outgoing; Wed, 26 Mar 1997 12:37:42 -0800 (PST) Received: from critter.dk.tfs.com (phk.cybercity.dk [195.8.133.247]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA22121; Wed, 26 Mar 1997 12:37:32 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id VAA12873; Wed, 26 Mar 1997 21:36:35 +0100 (CET) To: "James F. Hranicky" cc: mobile@freebsd.org Subject: Re: XFree86 on hitachi w/ neomagic 128 SVGA controller In-reply-to: Your message of "Wed, 26 Mar 1997 15:12:40 EST." <199703262012.PAA21581@cise.ufl.edu> Date: Wed, 26 Mar 1997 21:36:35 +0100 Message-ID: <12871.859408595@critter> From: Poul-Henning Kamp Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199703262012.PAA21581@cise.ufl.edu>, "James F. Hranicky" writes: >Poul-Henning Kamp wrote: > >> >(the E133T, specifically) that uses the NeoMagic 128 PCI SVGA >> >controller? This is the same controller as use in the new Dell latitude >> >133s, i believe, but i haven't seen anything on that one, either. >> >> Check out the demo from www.xgi.com > >I can't seem to find this address: > > [jfh@tick:/usr/catman] 83 % nslookup www.xgi.com > Server: hail.cise.ufl.edu > Address: 128.227.205.72 > > *** hail.cise.ufl.edu can't find www.xgi.com: Server failed Sorry, www.xig.com ^^^ www.xig.com has address 199.164.187.35 -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-mobile Thu Mar 27 09:46:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA00787 for mobile-outgoing; Thu, 27 Mar 1997 09:46:25 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA00759 for ; Thu, 27 Mar 1997 09:46:17 -0800 (PST) Received: from tfd.com (tfd.com [206.205.61.2]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id IAA04889 for ; Thu, 27 Mar 1997 08:57:51 -0800 (PST) Received: from sneezy (sneezy.tfd.com [10.9.200.10]) by tfd.com (8.7.4/8.7.3) with SMTP id LAA16482 for ; Thu, 27 Mar 1997 11:58:01 -0500 (EST) Received: by sneezy id AA13189 (5.65b/IDA-1.4.3 for freebsd-mobile@freebsd.org); Thu, 27 Mar 97 11:56:33 -0500 Date: Thu, 27 Mar 97 11:56:33 -0500 From: Kent Hauser Message-Id: <9703271656.AA13189@sneezy> To: freebsd-mobile@freebsd.org Subject: sendmail & the roving laptop Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk How does one go about setting up sendmail to work with a travelling laptop? What I want is to be able to send mail to `foo@x.org' & have it queued for uucp transmission. I also want mail to `kent@tfd.com' and `kent' to be locally delivered. For extra credit I would like mail to `co-worker@tfd.com' and/or `co-worker' to be queued for uucp transmission. I have run into two main classes of problems: 1) sendmail refuses to *not* do a dns lookup even when the "no dns" option is specified. While my laptop nameserver has all of the local records, it can't do a real lookup while travelling. This causes sendmail to hang & not send the mail. 2) all mail is either locally delivered or queued. If mail to a co-worker is queued for uucp xmission, then my mail is also queued. If mail to me is locally delivered, then co-worker mail is also & bounces. [[ I experimented with the above while connected to the local ethernet to get around problem number 1. ]] As this must be a common problem, I hope someone can help me out. Thanks, Kent ======== For what it's worth, it's a piece of cake to get the mail server to forward a copy of all mail to the laptop via uucp. All you need is this entry in the `.forward' file & the following shell script. .forward: \kent, "|rsh uucp-host rmail-kent" rmail-kent: #!/bin/sh exec uux -p -n 'kent!rmail kent' From owner-freebsd-mobile Thu Mar 27 09:49:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA01647 for mobile-outgoing; Thu, 27 Mar 1997 09:49:48 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA01619; Thu, 27 Mar 1997 09:49:43 -0800 (PST) Received: from smtp.well.com (smtp.well.com [206.80.6.147]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id HAA04589 ; Thu, 27 Mar 1997 07:54:39 -0800 (PST) Received: from well.com (spidaman@well.com [206.15.64.10]) by smtp.well.com (8.8.5/8.8.4) with SMTP id HAA08249; Thu, 27 Mar 1997 07:53:27 -0800 (PST) Date: Thu, 27 Mar 1997 07:53:23 -0800 (PST) From: Ian Kallen Reply-To: Ian Kallen To: freebsd-mobile@freebsd.org cc: freebsd-hackers@freebsd.org Subject: (Dell Latitude) psm0/sc0 conflicts killing X? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I don't know what else changed when I went from 2.2-GAMMA w/o PAO (Used the zp drivers from the 3c589) to 2.2.1-RELEASE... I'm on a Dell XPi p100 and Xinside's X server was doing fine w/ 800X600 @256 but since I ran the upgrade and applied the PAO patches, I've had to explicitly re-enable psm0 by booting w/ -c (other X won't start at all) but the keyboard is dead once I'm in X. I tried reinstalling Xinside but that made no differnce. Any comments or suggestions (if a look @ my kernel config is needed to comment on it, I'll send that along as well) appreciated! The next interface will not be another desktop metaphor.... Ian Kallen .... http://www.well.com/user/spidaman/ ....the revolution will not be televised. ===== TO RECEIVE MY PGP KEY, SEND MAIL TO spidey-pgp-info@well.com ======= From owner-freebsd-mobile Thu Mar 27 11:17:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA11447 for mobile-outgoing; Thu, 27 Mar 1997 11:17:04 -0800 (PST) Received: from mailbag.jf.intel.com (mailbag.jf.intel.com [134.134.248.4]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA11442 for ; Thu, 27 Mar 1997 11:17:01 -0800 (PST) Received: from aahz.jf.intel.com (aahz.jf.intel.com [192.198.161.2]) by mailbag.jf.intel.com (8.8.5/8.7.3) with SMTP id LAA14018 for ; Thu, 27 Mar 1997 11:19:18 -0800 (PST) Received: by aahz.jf.intel.com (Smail3.1.28.1 #13) id m0wAKec-000hxlC; Thu, 27 Mar 97 11:16 PST Message-Id: From: batie@aahz.jf.intel.com (Alan Batie) To: mobile@freebsd.org Date: Thu, 27 Mar 1997 11:16:06 -0800 (PST) X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk subscribe -- Alan Batie ------ What goes up, must come down. batie@aahz.jf.intel.com \ / Ask any system administrator. +1 503-264-8844 (voice) \ / --unknown D0 D2 39 0E 02 34 D6 B4 \/ 5A 41 21 8F 23 5F 08 9D From owner-freebsd-mobile Thu Mar 27 12:24:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA18496 for mobile-outgoing; Thu, 27 Mar 1997 12:24:57 -0800 (PST) Received: from mailbag.jf.intel.com (mailbag.jf.intel.com [134.134.248.4]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA18491 for ; Thu, 27 Mar 1997 12:24:51 -0800 (PST) Received: from aahz.jf.intel.com (aahz.jf.intel.com [192.198.161.2]) by mailbag.jf.intel.com (8.8.5/8.7.3) with SMTP id MAA17716 for ; Thu, 27 Mar 1997 12:27:10 -0800 (PST) Received: by aahz.jf.intel.com (Smail3.1.28.1 #13) id m0wALiI-000hxlC; Thu, 27 Mar 97 12:23 PST Message-Id: From: batie@aahz.jf.intel.com (Alan Batie) Subject: pao install To: mobile@freebsd.org Date: Thu, 27 Mar 1997 12:23:58 -0800 (PST) X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm installing 2.2-RELEASE on a Toshiba 420CDS using the PAO boot floppy and a Linksys EC2T (NE2000 compat) pcmcia card. I tried before with the 3c589C and got the same results, namely 0.5KB/sec transfer rates. I suspect lost interrupts somewhere; here's the tcpdump of it; .2 is my local workstation, from which I'm ftping the release, and .202 is the laptop doing the install: 12:20:36.136822 192.198.161.2.20 > 192.198.161.202.1026: . 66608:68056(1448) ack 1 win 8760 [tos 0x8] 12:20:36.139360 192.198.161.202.1026 > 192.198.161.2.20: . ack 70952 win 13032 (DF) 12:20:36.139636 192.198.161.2.20 > 192.198.161.202.1026: . 70952:72400(1448) ack 1 win 8760 [tos 0x8] 12:20:36.139688 192.198.161.202.1026 > 192.198.161.2.20: . ack 70952 win 17376 (DF) 12:20:36.139811 192.198.161.2.20 > 192.198.161.202.1026: P 72400:73832(1432) ack 1 win 8760 [tos 0x8] 12:20:38.139060 192.198.161.2.20 > 192.198.161.202.1026: . 70952:72400(1448) ack 1 win 8760 [tos 0x8] 12:20:38.202006 192.198.161.202.1026 > 192.198.161.2.20: . ack 72400 win 17376 (DF) 12:20:38.202254 192.198.161.2.20 > 192.198.161.202.1026: . 72400:73848(1448) ack 1 win 8760 [tos 0x8] 12:20:38.202399 192.198.161.2.20 > 192.198.161.202.1026: . 73848:75296(1448) ack 1 win 8760 [tos 0x8] 12:20:38.206557 192.198.161.202.1026 > 192.198.161.2.20: . ack 75296 win 17376 (DF) 12:20:38.206801 192.198.161.2.20 > 192.198.161.202.1026: . 75296:76744(1448) ack 1 win 8760 [tos 0x8] 12:20:38.206926 192.198.161.2.20 > 192.198.161.202.1026: . 76744:78192(1448) ack 1 win 8760 [tos 0x8] 12:20:38.207054 192.198.161.2.20 > 192.198.161.202.1026: . 78192:79640(1448) ack 1 win 8760 [tos 0x8] 12:20:38.210833 192.198.161.202.1026 > 192.198.161.2.20: . ack 78192 win 17376 (DF) 12:20:38.211050 192.198.161.2.20 > 192.198.161.202.1026: . 79640:81088(1448) ack 1 win 8760 [tos 0x8] 12:20:38.211401 192.198.161.2.20 > 192.198.161.202.1026: . 81088:82536(1448) ack 1 win 8760 [tos 0x8] 12:20:40.646887 192.198.161.2.20 > 192.198.161.202.1026: . 78192:79640(1448) ack 1 win 8760 [tos 0x8] 12:20:45.647017 192.198.161.2.20 > 192.198.161.202.1026: . 78192:79640(1448) ack 1 win 8760 [tos 0x8] 12:20:45.802665 192.198.161.202.1026 > 192.198.161.2.20: . ack 79640 win 17376 (DF) -- Alan Batie ------ What goes up, must come down. batie@aahz.jf.intel.com \ / Ask any system administrator. +1 503-264-8844 (voice) \ / --unknown D0 D2 39 0E 02 34 D6 B4 \/ 5A 41 21 8F 23 5F 08 9D From owner-freebsd-mobile Thu Mar 27 13:12:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA22608 for mobile-outgoing; Thu, 27 Mar 1997 13:12:29 -0800 (PST) Received: from mailbag.jf.intel.com (mailbag.jf.intel.com [134.134.248.4]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA22603 for ; Thu, 27 Mar 1997 13:12:25 -0800 (PST) Received: from aahz.jf.intel.com (aahz.jf.intel.com [192.198.161.2]) by mailbag.jf.intel.com (8.8.5/8.7.3) with SMTP id NAA19839 for ; Thu, 27 Mar 1997 13:14:44 -0800 (PST) Received: by aahz.jf.intel.com (Smail3.1.28.1 #13) id m0wAMSK-000hxlC; Thu, 27 Mar 97 13:11 PST Message-Id: From: batie@aahz.jf.intel.com (Alan Batie) Subject: never mind To: mobile@freebsd.org Date: Thu, 27 Mar 1997 13:11:31 -0800 (PST) X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The performance problem with the pao stuff turned out to be a hub gone bad and corrupting packets... -- Alan Batie ------ What goes up, must come down. batie@aahz.jf.intel.com \ / Ask any system administrator. +1 503-264-8844 (voice) \ / --unknown D0 D2 39 0E 02 34 D6 B4 \/ 5A 41 21 8F 23 5F 08 9D From owner-freebsd-mobile Thu Mar 27 14:51:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA00450 for mobile-outgoing; Thu, 27 Mar 1997 14:51:10 -0800 (PST) Received: from perki0.connect.com.au (perki0.connect.com.au [192.189.54.85]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA00444 for ; Thu, 27 Mar 1997 14:51:07 -0800 (PST) Received: from nemeton.UUCP (uucp@localhost) by perki0.connect.com.au with UUCP id JAA04053 (8.8.5/IDA-1.6); Fri, 28 Mar 1997 09:51:01 +1100 (EST) Received: from topaz.nemeton.com.au (topaz.nemeton.com.au [203.8.3.18]) by nemeton.com.au (8.8.5/8.8.5) with ESMTP id JAA16096; Fri, 28 Mar 1997 09:22:40 +1100 (EST) Received: from localhost.nemeton.com.au (localhost.nemeton.com.au [127.0.0.1]) by topaz.nemeton.com.au (8.8.5/8.8.5) with SMTP id JAA01384; Fri, 28 Mar 1997 09:23:10 +1100 (EST) Message-Id: <199703272223.JAA01384@topaz.nemeton.com.au> X-Authentication-Warning: topaz.nemeton.com.au: localhost.nemeton.com.au [127.0.0.1] didn't use HELO protocol To: Kent Hauser cc: freebsd-mobile@freebsd.org Subject: Re: sendmail & the roving laptop In-reply-to: <9703271656.AA13189@sneezy> Date: Fri, 28 Mar 1997 09:23:10 +1100 From: Giles Lean Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 27 Mar 97 11:56:33 -0500 Kent Hauser wrote: > 1) sendmail refuses to *not* do a dns lookup even when the "no dns" > option Check out 'nocanonify'. > 2) all mail is either locally delivered or queued. Yes; it is unusual to try to get sendmail to do per-user routing. If I *had* to do this (I'd find an alternative) I would think about: - aliasing all co-workers to 'co-worker@domain' - aliasing myself to 'myself@myhost.domain' - making sure mail to @domain is sent via UUCP - making sure mail to @myhost.domain is delivered locally (i.e. give up on having your mail be 'myself@domain'.) > As this must be a common problem, I hope someone can help me out. I'm not sure that it is ... Regards, Giles From owner-freebsd-mobile Thu Mar 27 19:29:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA15696 for mobile-outgoing; Thu, 27 Mar 1997 19:29:56 -0800 (PST) Received: from mailsrv.cc.utsunomiya-u.ac.jp (mailsrv.cc.utsunomiya-u.ac.jp [160.12.200.20]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA15684; Thu, 27 Mar 1997 19:29:52 -0800 (PST) Received: from zodiac.mech.utsunomiya-u.ac.jp (M1jR7d7E0xeCyWCQiNBE44y3k3CXQsBa@zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by mailsrv.cc.utsunomiya-u.ac.jp (8.8.5+2.7Wbeta5/3.5Wpl4) with ESMTP id MAA16977; Fri, 28 Mar 1997 12:29:16 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zenith.mech.utsunomiya-u.ac.jp [160.12.33.60]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id MAA26251; Fri, 28 Mar 1997 12:33:40 +0900 (JST) Message-Id: <199703280333.MAA26251@zodiac.mech.utsunomiya-u.ac.jp> To: Ian Kallen cc: freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: (Dell Latitude) psm0/sc0 conflicts killing X? In-reply-to: Your message of "Thu, 27 Mar 1997 07:53:23 PST." References: Date: Fri, 28 Mar 1997 12:33:39 +0900 From: Kazutaka YOKOTA Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I don't know what else changed when I went from 2.2-GAMMA w/o PAO (Used >the zp drivers from the 3c589) to 2.2.1-RELEASE... I'm on a Dell XPi p100 >and Xinside's X server was doing fine w/ 800X600 @256 but since I ran the >upgrade and applied the PAO patches, I've had to explicitly re-enable psm0 >by booting w/ -c (other X won't start at all) I think this is normal. The psm driver is disabled in GENERIC kernel, with or without PAO, by default, isn't it? >but the keyboard is dead >once I'm in X. I tried reinstalling Xinside but that made no >differnce. Any comments or suggestions (if a look @ my kernel config >is needed to comment on it, I'll send that along as well) appreciated! I had a report from another Dell Latitude XPi owner stating that if he tries to change the keyboard repeat rate by kbdcontrol, his keyboard freezes. He and I are now chasing the problem. It appears that the keyboard controller of his Latitude behaves in an unusual way. I wonder the cause of your problem is similar to his. I would be very grateful if you could try the following patch to /sys/i386/isa/syscons.c, rebuild the kernel, and try `kbdcontrol -r fast' or try starting X. Please send me debug messages you see. You may see something like: sc0: enabling tty intr. (set_keyboard) sc0: about to send command and data (set_keyboard) sc0: command:xx data:yy ret:zz (set_keybard) in the console (vty0). If you see: sc0: kbdc is LOCKED!! (scintr) your problem is the same as his. Kazu --- syscons.c-1.205 Mon Mar 3 10:09:00 1997 +++ syscons.c Mon Mar 24 12:04:57 1997 @@ -647,6 +651,12 @@ mark_all(cur_console); } + if (!kbdc_lock(sc_kbdc, TRUE)) { + log(LOG_DEBUG, "sc0: kbdc is LOCKED!! (scintr)\n"); + return; + } else { + kbdc_lock(sc_kbdc, FALSE); + } /* * Loop while there is still input to get from the keyboard. * I don't think this is nessesary, and it doesn't fix @@ -3114,7 +3131,7 @@ if ((c == -1) || !set_controller_command_byte(sc_kbdc, kbdc_get_device_mask(sc_kbdc), - KBD_ENABLE_KBD_PORT | KBD_DISABLE_KBD_INT + KBD_DISABLE_KBD_PORT | KBD_DISABLE_KBD_INT | KBD_DISABLE_AUX_PORT | KBD_DISABLE_AUX_INT)) { /* CONTROLLER ERROR */ kbdc_lock(sc_kbdc, FALSE); @@ -3128,9 +3145,14 @@ * but the timeout routine (`scrn_timer()') will be blocked * by the lock flag set via `kbdc_lock()' */ + log(LOG_DEBUG, "sc0: enabling tty intr. (set_keyboard)\n"); splx(s); + log(LOG_DEBUG, "sc0: about to send command and data (set_keyboard)\n"); - send_kbd_command_and_data(sc_kbdc, command, data); + log(LOG_DEBUG, "sc0: command:%x data:%x ret:%x (set_keybard)\n", + command, data, + send_kbd_command_and_data(sc_kbdc, command, data)); + send_kbd_command(sc_kbdc, KBDC_ENABLE_KBD); /* restore the interrupts */ if (!set_controller_command_byte(sc_kbdc, From owner-freebsd-mobile Thu Mar 27 21:15:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA19995 for mobile-outgoing; Thu, 27 Mar 1997 21:15:52 -0800 (PST) Received: from smtp.well.com (smtp.well.com [206.80.6.147]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA19977; Thu, 27 Mar 1997 21:15:49 -0800 (PST) Received: from well.com (spidaman@well.com [206.15.64.10]) by smtp.well.com (8.8.5/8.8.4) with SMTP id VAA28333; Thu, 27 Mar 1997 21:14:54 -0800 (PST) Date: Thu, 27 Mar 1997 21:14:55 -0800 (PST) From: Ian Kallen To: Kazutaka YOKOTA cc: freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: (Dell Latitude) psm0/sc0 conflicts killing X? In-Reply-To: <199703280333.MAA26251@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yes, I got almost the exact same messages, including sc0: kbdc is LOCKED!! (scintr) well, if you have a fix, I'd be happy to test it for you :) Shall I revert to the original syscons.c or will patching it with the debugging stuff be OK? Thank You Very Much! On Fri, 28 Mar 1997, Kazutaka YOKOTA wrote: > > >I don't know what else changed when I went from 2.2-GAMMA w/o PAO (Used > >the zp drivers from the 3c589) to 2.2.1-RELEASE... I'm on a Dell XPi p100 > >and Xinside's X server was doing fine w/ 800X600 @256 but since I ran the > >upgrade and applied the PAO patches, I've had to explicitly re-enable psm0 > >by booting w/ -c (other X won't start at all) > > I think this is normal. The psm driver is disabled in GENERIC kernel, > with or without PAO, by default, isn't it? > > >but the keyboard is dead > >once I'm in X. I tried reinstalling Xinside but that made no > >differnce. Any comments or suggestions (if a look @ my kernel config > >is needed to comment on it, I'll send that along as well) appreciated! > > I had a report from another Dell Latitude XPi owner stating that if he > tries to change the keyboard repeat rate by kbdcontrol, his keyboard > freezes. He and I are now chasing the problem. It appears that the > keyboard controller of his Latitude behaves in an unusual way. I wonder > the cause of your problem is similar to his. > > I would be very grateful if you could try the following patch to > /sys/i386/isa/syscons.c, rebuild the kernel, and try `kbdcontrol -r > fast' or try starting X. Please send me debug messages you see. > You may see something like: > > sc0: enabling tty intr. (set_keyboard) > sc0: about to send command and data (set_keyboard) > sc0: command:xx data:yy ret:zz (set_keybard) > > in the console (vty0). If you see: > > sc0: kbdc is LOCKED!! (scintr) > > your problem is the same as his. > > Kazu > > --- syscons.c-1.205 Mon Mar 3 10:09:00 1997 > +++ syscons.c Mon Mar 24 12:04:57 1997 > @@ -647,6 +651,12 @@ > mark_all(cur_console); > } > > + if (!kbdc_lock(sc_kbdc, TRUE)) { > + log(LOG_DEBUG, "sc0: kbdc is LOCKED!! (scintr)\n"); > + return; > + } else { > + kbdc_lock(sc_kbdc, FALSE); > + } > /* > * Loop while there is still input to get from the keyboard. > * I don't think this is nessesary, and it doesn't fix > @@ -3114,7 +3131,7 @@ > if ((c == -1) > || !set_controller_command_byte(sc_kbdc, > kbdc_get_device_mask(sc_kbdc), > - KBD_ENABLE_KBD_PORT | KBD_DISABLE_KBD_INT > + KBD_DISABLE_KBD_PORT | KBD_DISABLE_KBD_INT > | KBD_DISABLE_AUX_PORT | KBD_DISABLE_AUX_INT)) { > /* CONTROLLER ERROR */ > kbdc_lock(sc_kbdc, FALSE); > @@ -3128,9 +3145,14 @@ > * but the timeout routine (`scrn_timer()') will be blocked > * by the lock flag set via `kbdc_lock()' > */ > + log(LOG_DEBUG, "sc0: enabling tty intr. (set_keyboard)\n"); > splx(s); > + log(LOG_DEBUG, "sc0: about to send command and data (set_keyboard)\n"); > > - send_kbd_command_and_data(sc_kbdc, command, data); > + log(LOG_DEBUG, "sc0: command:%x data:%x ret:%x (set_keybard)\n", > + command, data, > + send_kbd_command_and_data(sc_kbdc, command, data)); > + send_kbd_command(sc_kbdc, KBDC_ENABLE_KBD); > > /* restore the interrupts */ > if (!set_controller_command_byte(sc_kbdc, > > > The next interface will not be another desktop metaphor.... Ian Kallen .... http://www.well.com/user/spidaman/ ....the revolution will not be televised. ===== TO RECEIVE MY PGP KEY, SEND MAIL TO spidey-pgp-info@well.com ======= From owner-freebsd-mobile Thu Mar 27 22:54:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA24129 for mobile-outgoing; Thu, 27 Mar 1997 22:54:18 -0800 (PST) Received: from mailsrv.cc.utsunomiya-u.ac.jp (mailsrv.cc.utsunomiya-u.ac.jp [160.12.200.20]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA24121; Thu, 27 Mar 1997 22:54:15 -0800 (PST) Received: from zodiac.mech.utsunomiya-u.ac.jp (kcQ8k77UcVrWIoO69OOTadZgLAfwRSFo@zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by mailsrv.cc.utsunomiya-u.ac.jp (8.8.5+2.7Wbeta5/3.5Wpl4) with ESMTP id PAA17757; Fri, 28 Mar 1997 15:53:18 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zenith.mech.utsunomiya-u.ac.jp [160.12.33.60]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id PAA29688; Fri, 28 Mar 1997 15:57:36 +0900 (JST) Message-Id: <199703280657.PAA29688@zodiac.mech.utsunomiya-u.ac.jp> To: Ian Kallen cc: freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: (Dell Latitude) psm0/sc0 conflicts killing X? In-reply-to: Your message of "Thu, 27 Mar 1997 21:14:55 PST." References: Date: Fri, 28 Mar 1997 15:57:30 +0900 From: Kazutaka YOKOTA Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Yes, I got almost the exact same messages, including > sc0: kbdc is LOCKED!! (scintr) Now, may I assume you got the messages in the following order, the return code was "fa" ("zz" in the fifth line) and the keyboard did NOT freeze? sc0: enabling tty intr. (set_keyboard) sc0: about to send command and data (set_keyboard) sc0: kbdc is LOCKED!! (scintr) sc0: kbdc is LOCKED!! (scintr) sc0: command:xx data:yy ret:zz (set_keybard) ~~ sc0: kbdc is LOCKED!! (scintr) >well, if you have a fix, I'd be happy to test it for you :) Shall I >revert to the original syscons.c or will patching it with the debugging >stuff be OK? Please revert to the original syscons.c and apply the following patch. It is known to work, that is, kbdcontrol can change key repeat rate and the X server doesn't lock up the keyboard. This patch doesn't generate debug messages, so it will be more suitable for daily use than the previous one. Kazu --- syscons.c-dist Mon Mar 3 10:09:00 1997 +++ syscons.c Mon Mar 17 08:02:35 1997 @@ -3110,11 +3111,12 @@ /* disable the keyboard and mouse interrupt */ s = spltty(); +#if 0 c = get_controller_command_byte(sc_kbdc); if ((c == -1) || !set_controller_command_byte(sc_kbdc, kbdc_get_device_mask(sc_kbdc), - KBD_ENABLE_KBD_PORT | KBD_DISABLE_KBD_INT + KBD_DISABLE_KBD_PORT | KBD_DISABLE_KBD_INT | KBD_DISABLE_AUX_PORT | KBD_DISABLE_AUX_INT)) { /* CONTROLLER ERROR */ kbdc_lock(sc_kbdc, FALSE); @@ -3129,15 +3131,21 @@ * by the lock flag set via `kbdc_lock()' */ splx(s); +#endif - send_kbd_command_and_data(sc_kbdc, command, data); + if (send_kbd_command_and_data(sc_kbdc, command, data) != KBD_ACK) + send_kbd_command(sc_kbdc, KBDC_ENABLE_KBD); +#if 0 /* restore the interrupts */ if (!set_controller_command_byte(sc_kbdc, kbdc_get_device_mask(sc_kbdc), c & (KBD_KBD_CONTROL_BITS | KBD_AUX_CONTROL_BITS))) { /* CONTROLLER ERROR */ } +#else + splx(s); +#endif kbdc_lock(sc_kbdc, FALSE); } From owner-freebsd-mobile Thu Mar 27 23:42:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA25777 for mobile-outgoing; Thu, 27 Mar 1997 23:42:20 -0800 (PST) Received: from smtp.well.com (smtp.well.com [206.80.6.147]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA25752; Thu, 27 Mar 1997 23:42:15 -0800 (PST) Received: from well.com (spidaman@well.com [206.15.64.10]) by smtp.well.com (8.8.5/8.8.4) with SMTP id XAA14067; Thu, 27 Mar 1997 23:41:53 -0800 (PST) Date: Thu, 27 Mar 1997 23:41:54 -0800 (PST) From: Ian Kallen To: Kazutaka YOKOTA cc: freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: (Dell Latitude) psm0/sc0 conflicts killing X? In-Reply-To: <199703280657.PAA29688@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sir, you are very correct: /kernel: sc0: enabling tty intr. (set_keyboard) /kernel: sc0: about to send command and data (set_keyboard) /kernel: sc0: kbdc is LOCKED!! (scintr) /kernel: sc0: kbdc is LOCKED!! (scintr) /kernel: sc0: command:f3 data:0 ret:fa (set_keybard) /kernel: sc0: kbdc is LOCKED!! (scintr) and, most importantly: your patch appears to have worked - I'm happily running X again w/o difficulty for the past few minutes, it looks fine. Please remind me to buy you dinner should you be traveling to San Francisco ;) Thanks again and best regards, Ian On Fri, 28 Mar 1997, Kazutaka YOKOTA wrote: > > >Yes, I got almost the exact same messages, including > > sc0: kbdc is LOCKED!! (scintr) > > Now, may I assume you got the messages in the following order, the > return code was "fa" ("zz" in the fifth line) and the keyboard did NOT > freeze? > > sc0: enabling tty intr. (set_keyboard) > sc0: about to send command and data (set_keyboard) > sc0: kbdc is LOCKED!! (scintr) > sc0: kbdc is LOCKED!! (scintr) > sc0: command:xx data:yy ret:zz (set_keybard) > ~~ > sc0: kbdc is LOCKED!! (scintr) > > >well, if you have a fix, I'd be happy to test it for you :) Shall I > >revert to the original syscons.c or will patching it with the debugging > >stuff be OK? > > Please revert to the original syscons.c and apply the following patch. > It is known to work, that is, kbdcontrol can change key repeat rate > and the X server doesn't lock up the keyboard. > > This patch doesn't generate debug messages, so it will be more > suitable for daily use than the previous one. > > Kazu > > --- syscons.c-dist Mon Mar 3 10:09:00 1997 > +++ syscons.c Mon Mar 17 08:02:35 1997 > @@ -3110,11 +3111,12 @@ > > /* disable the keyboard and mouse interrupt */ > s = spltty(); > +#if 0 > c = get_controller_command_byte(sc_kbdc); > if ((c == -1) > || !set_controller_command_byte(sc_kbdc, > kbdc_get_device_mask(sc_kbdc), > - KBD_ENABLE_KBD_PORT | KBD_DISABLE_KBD_INT > + KBD_DISABLE_KBD_PORT | KBD_DISABLE_KBD_INT > | KBD_DISABLE_AUX_PORT | KBD_DISABLE_AUX_INT)) { > /* CONTROLLER ERROR */ > kbdc_lock(sc_kbdc, FALSE); > @@ -3129,15 +3131,21 @@ > * by the lock flag set via `kbdc_lock()' > */ > splx(s); > +#endif > > - send_kbd_command_and_data(sc_kbdc, command, data); > + if (send_kbd_command_and_data(sc_kbdc, command, data) != KBD_ACK) > + send_kbd_command(sc_kbdc, KBDC_ENABLE_KBD); > > +#if 0 > /* restore the interrupts */ > if (!set_controller_command_byte(sc_kbdc, > kbdc_get_device_mask(sc_kbdc), > c & (KBD_KBD_CONTROL_BITS | KBD_AUX_CONTROL_BITS))) { > /* CONTROLLER ERROR */ > } > +#else > + splx(s); > +#endif > kbdc_lock(sc_kbdc, FALSE); > } > > > > > > > The next interface will not be another desktop metaphor.... Ian Kallen .... http://www.well.com/user/spidaman/ ....the revolution will not be televised. ===== TO RECEIVE MY PGP KEY, SEND MAIL TO spidey-pgp-info@well.com ======= From owner-freebsd-mobile Fri Mar 28 08:40:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA19446 for mobile-outgoing; Fri, 28 Mar 1997 08:40:53 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA19441; Fri, 28 Mar 1997 08:40:48 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA16977; Fri, 28 Mar 1997 09:40:36 -0700 (MST) Date: Fri, 28 Mar 1997 09:40:36 -0700 (MST) Message-Id: <199703281640.JAA16977@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ian Kallen Cc: freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: (Dell Latitude) psm0/sc0 conflicts killing X? In-Reply-To: References: X-Mailer: VM 6.22 under 19.14 XEmacs Lucid Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I don't know what else changed when I went from 2.2-GAMMA w/o PAO (Used > the zp drivers from the 3c589) to 2.2.1-RELEASE... The queing patches were added to the console driver. And, it works fine on my 2.2 desktop box and on my laptop, both running Xig's package. The queing patches were necessary to avoid lockups on my desktop using Xig's server, hence the reason I pushed for them in the release. > I'm on a Dell XPi p100 > and Xinside's X server was doing fine w/ 800X600 @256 but since I ran the > upgrade and applied the PAO patches, I've had to explicitly re-enable psm0 > by booting w/ -c (other X won't start at all) but the keyboard is dead > once I'm in X. It works fine out of X? > I tried reinstalling Xinside but that made no > differnce. Any comments or suggestions (if a look @ my kernel config > is needed to comment on it, I'll send that along as well) appreciated! Hmm, can you send me your config file in private email, and I'll compare it to mine at work? Nate From owner-freebsd-mobile Fri Mar 28 08:52:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA20239 for mobile-outgoing; Fri, 28 Mar 1997 08:52:33 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA20231 for ; Fri, 28 Mar 1997 08:52:30 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA17030; Fri, 28 Mar 1997 09:48:27 -0700 (MST) Date: Fri, 28 Mar 1997 09:48:27 -0700 (MST) Message-Id: <199703281648.JAA17030@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: batie@aahz.jf.intel.com (Alan Batie) Cc: mobile@freebsd.org Subject: Re: never mind In-Reply-To: References: X-Mailer: VM 6.22 under 19.14 XEmacs Lucid Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The performance problem with the pao stuff turned out to be a hub gone > bad and corrupting packets... Cool! I was fretting over this, and nothing came to mind why it wouldn't work. Thanks for the update! Nate