From owner-freebsd-current Sun Aug 8 2:52:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id BF80814C40 for ; Sun, 8 Aug 1999 02:52:12 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:uO3FcNTTyq4OvxANv7ceEYDZ66qvjN52@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id SAA06638; Sun, 8 Aug 1999 18:49:36 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id SAA09056; Sun, 8 Aug 1999 18:53:56 +0900 (JST) Message-Id: <199908080953.SAA09056@zodiac.mech.utsunomiya-u.ac.jp> To: "Pierre Y. Dampure" Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Problem using XFree86 3.3.4 w/ VESA kernel option In-reply-to: Your message of "Sun, 08 Aug 1999 01:13:06 +0100." <37ACCB92.E48E7852@k2c.co.uk> References: <37ACCB92.E48E7852@k2c.co.uk> Date: Sun, 08 Aug 1999 18:53:55 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >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 windows, etc... Would you give me the pointer to these posts? I seem to be unable to locate the posts you are referring to. Kazu >After a bit of digging, I found that removing the VESA kernel option >cured the problem on my Voodoo 3 2000 PCI adapter. I would be >interesting to know whether this is the case for all other hardware? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 5:28:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 9310E14FD4; Sun, 8 Aug 1999 05:28:33 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id OAA02945; Sun, 8 Aug 1999 14:27:23 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 352528711; Sun, 8 Aug 1999 13:03:38 +0200 (CEST) Date: Sun, 8 Aug 1999 13:03:38 +0200 From: Ollivier Robert To: current@freebsd.org, multimedia@freebsd.org Subject: Re: it's time... Message-ID: <19990808130338.A87329@keltia.freenix.fr> Mail-Followup-To: current@freebsd.org, multimedia@freebsd.org References: <000901bee13c$b1831dc0$0304020a@rings> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: <000901bee13c$b1831dc0$0304020a@rings>; from Cameron Grant on Sun, Aug 08, 1999 at 02:23:59AM +0100 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5543 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Cameron Grant: > the list of supported cards is as for luigi's driver, with the addition of a > couple more mss-clones, and trident 4dwave. there is a part done aureal Can someone with access to a Sony VAIO Z505S(X) laptop try this ? According to Sony it is supposed to be MSS compatible but it is not seen by the current sound code... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 7:12:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from esmeralda.xaa.iae.nl (esmeralda.xaa.iae.nl [194.151.75.9]) by hub.freebsd.org (Postfix) with ESMTP id 44EC214E9E for ; Sun, 8 Aug 1999 07:12:45 -0700 (PDT) (envelope-from freebsd@xaa.iae.nl) Received: from ariel.xaa.iae.nl (ariel.xaa.iae.nl [194.151.75.10]) by esmeralda.xaa.iae.nl (Postfix) with ESMTP id 94E86BA41; Sun, 8 Aug 1999 16:09:55 +0200 (MET DST) Received: by ariel.xaa.iae.nl (Postfix, from userid 1008) id 537265CF0; Sun, 8 Aug 1999 16:09:43 +0200 (CEST) Date: Sun, 8 Aug 1999 16:09:43 +0200 From: Mark Huizer To: Poul-Henning Kamp Cc: Andrzej Bialecki , freebsd-current@FreeBSD.ORG Subject: Re: Arg! MFS broken Message-ID: <19990808160943.A1286@ariel.xaa.iae.nl> References: <47364.932848590@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <47364.932848590@critter.freebsd.dk>; from Poul-Henning Kamp on Sat, Jul 24, 1999 at 10:36:30PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> > I'm sorry, I don't have either in my arsenal currently. > >> I found that trying to build a PicoBSD floppy was a sure way of crashing > >> my current box :-( Perhaps that is a nice testing environment? > > > >Then you should investigate this further, because it looks like some bug > >in vn(4) code - picobsd build doesn't do anything unusual except that... > > I built a release (which also uses vn(4)) yesterday, so to some extent > of the concept vn(4) works. I'm very interested in a traceback of > this panic... > I just redid the disk configuration here so I can get kernel dumps working again... I'll try it out this evening. -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 12:32:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 126E1151DD for ; Sun, 8 Aug 1999 12:31:58 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb58.imasy.or.jp [202.227.24.186]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id EAA00367; Mon, 9 Aug 1999 04:30:20 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199908081930.EAA00367@tasogare.imasy.or.jp> To: freebsd-current@FreeBSD.ORG Cc: imp@village.org, plm@xs4all.nl Subject: Re: recent apm changes X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 09 Aug 1999 04:34:06 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 19 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > In message <37A9FA33.426D35FC@seattleu.edu> Eric Hodel writes: > : I've got a -current machine (no cvsups in a few months) that wakes up > : immediately after suspending. (sleeps 0 seconds) > > Hmmm, some laptops will wakeup on a keyboard interrupt. The interrupt > that is waking you up may be the key up from the return you hit to > make the event happen. > > PAO has a small sleep in the apm driver, while -current didn't the > last time I looked. OK, I'll work on this. To Peter Mutsaers: Could you try following command to suspend and see any improvements? % sleep 3 && apm -z & To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 13:26: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp7.xs4all.nl (smtp7.xs4all.nl [194.109.127.50]) by hub.freebsd.org (Postfix) with ESMTP id C178B14FF2 for ; Sun, 8 Aug 1999 13:25:56 -0700 (PDT) (envelope-from plm@smtp7.xs4all.nl) Received: from localhost. (dc2-isdn98.dial.xs4all.nl [194.109.148.98]) by smtp7.xs4all.nl (8.9.3/8.9.3) with ESMTP id VAA18858; Sun, 8 Aug 1999 21:52:33 +0200 (CEST) Received: (from plm@localhost) by localhost. (8.9.3/8.8.7) id VAA00599; Sun, 8 Aug 1999 21:52:32 +0200 From: Peter Mutsaers MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14253.57344.873947.122158@muon.xs4all.nl> Date: Sun, 8 Aug 1999 21:52:32 +0200 (CEST) To: Mitsuru IWASAKI Cc: freebsd-current@FreeBSD.ORG, imp@village.org, plm@xs4all.nl Subject: Re: recent apm changes In-Reply-To: <199908081930.EAA00367@tasogare.imasy.or.jp> References: <199908081930.EAA00367@tasogare.imasy.or.jp> X-Mailer: VM 6.65 under Emacs 20.3.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> "MI" == Mitsuru IWASAKI writes: >> PAO has a small sleep in the apm driver, while -current didn't the >> last time I looked. MI> OK, I'll work on this. MI> To Peter Mutsaers: MI> Could you try following command to suspend and see any improvements? MI> % sleep 3 && apm -z & I have done this before, and it does bring the computer into suspend indeed (light flashes). But for my real problem, noise reduction, this doesn't help of course. The disks keep spinning, and so do all fans (CPU or whatever). In contract, if I suspend in Linux of Windows, the computer shuts up immediateley and is quiet. Only sometimes there is a (not too loud) little fan (I think it is the CPU fan) running for a few more minutes. regards, -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know plm@xs4all.nl | the Netherlands | what I'm doing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 13:30:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id 03BC814FF2 for ; Sun, 8 Aug 1999 13:30:15 -0700 (PDT) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.3/8.9.3) with ESMTP id WAA56965 for ; Sun, 8 Aug 1999 22:27:09 +0200 (CEST) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.9.3/8.9.3) id WAA21285 for freebsd-current@freebsd.org; Sun, 8 Aug 1999 22:27:08 +0200 (CEST) Date: Sun, 8 Aug 1999 22:27:08 +0200 From: Cejka Rudolf To: freebsd-current@freebsd.org Subject: VESA module doesn't work with ATI Mach64 RagePro Message-ID: <19990808222708.A21161@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 reported when I'm trying to unload/load vesa.ko module. Kernel reports during boot: VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc024f622 (1000022) VESA: ATI MACH64 Command "vidcontrol -i mode" reports lines below. It looks VESA module can't read mode table properly. But simple VESA utilities in DOS are capable to determine all VESA modes supported by ATI Mach64 card with VESA 2.0 BIOS. Is this known problem? Or should I invetigate this problem further? mode# flags type size font window linear buffer ------------------------------------------------------------------------------ 0 (0x000) 0x00000001 T 40x25 8x8 0xb8000 32k 32k 0x00000000 32k 1 (0x001) 0x00000001 T 40x25 8x8 0xb8000 32k 32k 0x00000000 32k 2 (0x002) 0x00000001 T 80x25 8x8 0xb8000 32k 32k 0x00000000 32k 3 (0x003) 0x00000001 T 80x25 8x8 0xb8000 32k 32k 0x00000000 32k 4 (0x004) 0x00000003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x00000000 32k 5 (0x005) 0x00000003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x00000000 32k 6 (0x006) 0x00000003 G 640x200x1 1 8x8 0xb8000 32k 32k 0x00000000 32k 13 (0x00d) 0x00000003 G 320x200x4 4 8x8 0xa0000 64k 64k 0x00000000 256k 14 (0x00e) 0x00000003 G 640x200x4 4 8x8 0xa0000 64k 64k 0x00000000 256k 16 (0x010) 0x00000003 G 640x350x2 2 8x14 0xa0000 64k 64k 0x00000000 128k 18 (0x012) 0x00000003 G 640x350x4 4 8x14 0xa0000 64k 64k 0x00000000 256k 19 (0x013) 0x00000001 T 40x25 8x14 0xb8000 32k 32k 0x00000000 32k 20 (0x014) 0x00000001 T 40x25 8x14 0xb8000 32k 32k 0x00000000 32k 21 (0x015) 0x00000001 T 80x25 8x14 0xb8000 32k 32k 0x00000000 32k 22 (0x016) 0x00000001 T 80x25 8x14 0xb8000 32k 32k 0x00000000 32k 23 (0x017) 0x00000001 T 40x25 8x16 0xb8000 32k 32k 0x00000000 32k 24 (0x018) 0x00000001 T 80x25 8x16 0xb8000 32k 32k 0x00000000 32k 26 (0x01a) 0x00000003 G 640x480x4 4 8x16 0xa0000 64k 64k 0x00000000 256k 27 (0x01b) 0x00000003 G 640x480x4 4 8x16 0xa0000 64k 64k 0x00000000 256k 28 (0x01c) 0x00000003 G 320x200x8 1 8x8 0xa0000 64k 64k 0x00000000 64k 30 (0x01e) 0x00000001 T 80x50 8x8 0xb8000 32k 32k 0x00000000 32k 32 (0x020) 0x00000001 T 80x30 8x16 0xb8000 32k 32k 0x00000000 32k 34 (0x022) 0x00000001 T 80x60 8x8 0xb8000 32k 32k 0x00000000 32k 37 (0x025) 0x00000003 G 320x240x8 1 8x8 0xa0000 64k 64k 0x00000000 64k 40 (0x028) 0x00000001 T 90x25 8x16 0xb8000 32k 32k 0x00000000 32k 42 (0x02a) 0x00000001 T 90x30 8x16 0xb8000 32k 32k 0x00000000 32k 44 (0x02c) 0x00000001 T 90x43 8x8 0xb8000 32k 32k 0x00000000 32k 45 (0x02d) 0x00000000 T 90x43 8x8 0xb8000 32k 32k 0x00000000 32k 46 (0x02e) 0x00000001 T 90x50 8x8 0xb8000 32k 32k 0x00000000 32k 48 (0x030) 0x00000001 T 90x60 8x8 0xb8000 32k 32k 0x00000000 32k 112 (0x070) 0x00000000 T 80x43 8x8 0xb8000 32k 32k 0x00000000 32k 113 (0x071) 0x00000001 T 80x43 8x8 0xb8000 32k 32k 0x00000000 32k -- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 13:43:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles523.castles.com [208.214.165.87]) by hub.freebsd.org (Postfix) with ESMTP id 775AF1502D for ; Sun, 8 Aug 1999 13:43:38 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id NAA13025; Sun, 8 Aug 1999 13:37:04 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908082037.NAA13025@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Cejka Rudolf Cc: freebsd-current@freebsd.org Subject: Re: VESA module doesn't work with ATI Mach64 RagePro In-reply-to: Your message of "Sun, 08 Aug 1999 22:27:08 +0200." <19990808222708.A21161@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Aug 1999 13:37:04 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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 > reported when I'm trying to unload/load vesa.ko module. Kernel reports > during boot: > > VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc024f622 (1000022) > VESA: ATI MACH64 > > Command "vidcontrol -i mode" reports lines below. It looks VESA module > can't read mode table properly. But simple VESA utilities in DOS are capable > to determine all VESA modes supported by ATI Mach64 card with VESA 2.0 BIOS. > Is this known problem? Or should I invetigate this problem further? Could you perhaps try to explain this a bit more? Are you saying that the card supports more modes than those listed below? What are they? How do these "simple VESA utilities" find these other modes? Are you sure that you're not also loading a VESA BIOS driver under DOS? I'm not aware of any deficiencies in our VESA modelist fetching code; I have, however, noticed that a lot of cards don't offer very good VESA support "out of the box" anymore. > mode# flags type size font window linear buffer > ------------------------------------------------------------------------------ > 0 (0x000) 0x00000001 T 40x25 8x8 0xb8000 32k 32k 0x00000000 32k > 1 (0x001) 0x00000001 T 40x25 8x8 0xb8000 32k 32k 0x00000000 32k > 2 (0x002) 0x00000001 T 80x25 8x8 0xb8000 32k 32k 0x00000000 32k > 3 (0x003) 0x00000001 T 80x25 8x8 0xb8000 32k 32k 0x00000000 32k > 4 (0x004) 0x00000003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x00000000 32k > 5 (0x005) 0x00000003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x00000000 32k > 6 (0x006) 0x00000003 G 640x200x1 1 8x8 0xb8000 32k 32k 0x00000000 32k > 13 (0x00d) 0x00000003 G 320x200x4 4 8x8 0xa0000 64k 64k 0x00000000 256k > 14 (0x00e) 0x00000003 G 640x200x4 4 8x8 0xa0000 64k 64k 0x00000000 256k > 16 (0x010) 0x00000003 G 640x350x2 2 8x14 0xa0000 64k 64k 0x00000000 128k > 18 (0x012) 0x00000003 G 640x350x4 4 8x14 0xa0000 64k 64k 0x00000000 256k > 19 (0x013) 0x00000001 T 40x25 8x14 0xb8000 32k 32k 0x00000000 32k > 20 (0x014) 0x00000001 T 40x25 8x14 0xb8000 32k 32k 0x00000000 32k > 21 (0x015) 0x00000001 T 80x25 8x14 0xb8000 32k 32k 0x00000000 32k > 22 (0x016) 0x00000001 T 80x25 8x14 0xb8000 32k 32k 0x00000000 32k > 23 (0x017) 0x00000001 T 40x25 8x16 0xb8000 32k 32k 0x00000000 32k > 24 (0x018) 0x00000001 T 80x25 8x16 0xb8000 32k 32k 0x00000000 32k > 26 (0x01a) 0x00000003 G 640x480x4 4 8x16 0xa0000 64k 64k 0x00000000 256k > 27 (0x01b) 0x00000003 G 640x480x4 4 8x16 0xa0000 64k 64k 0x00000000 256k > 28 (0x01c) 0x00000003 G 320x200x8 1 8x8 0xa0000 64k 64k 0x00000000 64k > 30 (0x01e) 0x00000001 T 80x50 8x8 0xb8000 32k 32k 0x00000000 32k > 32 (0x020) 0x00000001 T 80x30 8x16 0xb8000 32k 32k 0x00000000 32k > 34 (0x022) 0x00000001 T 80x60 8x8 0xb8000 32k 32k 0x00000000 32k > 37 (0x025) 0x00000003 G 320x240x8 1 8x8 0xa0000 64k 64k 0x00000000 64k > 40 (0x028) 0x00000001 T 90x25 8x16 0xb8000 32k 32k 0x00000000 32k > 42 (0x02a) 0x00000001 T 90x30 8x16 0xb8000 32k 32k 0x00000000 32k > 44 (0x02c) 0x00000001 T 90x43 8x8 0xb8000 32k 32k 0x00000000 32k > 45 (0x02d) 0x00000000 T 90x43 8x8 0xb8000 32k 32k 0x00000000 32k > 46 (0x02e) 0x00000001 T 90x50 8x8 0xb8000 32k 32k 0x00000000 32k > 48 (0x030) 0x00000001 T 90x60 8x8 0xb8000 32k 32k 0x00000000 32k > 112 (0x070) 0x00000000 T 80x43 8x8 0xb8000 32k 32k 0x00000000 32k > 113 (0x071) 0x00000001 T 80x43 8x8 0xb8000 32k 32k 0x00000000 32k > > -- > Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) > Brno University of Technology, Faculty of El. Engineering and Comp. Science > Bozetechova 2, 612 66 Brno, Czech Republic > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 16:26:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 1664014F75; Sun, 8 Aug 1999 16:26:39 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA13076; Sun, 8 Aug 1999 18:52:08 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id SAA18821; Sun, 8 Aug 1999 18:52:07 -0400 (EDT) Received: from localhost by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA18817; Sun, 8 Aug 1999 18:52:07 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Sun, 8 Aug 1999 18:52:07 -0400 (EDT) From: Kenneth Wayne Culver To: Cameron Grant Cc: multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: <000901bee13c$b1831dc0$0304020a@rings> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > to let newpcm out of the cage so you can all get your grubby little hands on > it. > > http://www.vilnya.demon.co.uk/newpcm+dfrpnp-19990807.diff.gz > > this is a patch against a recent -current. if you have a pci or isapnp > soundcard, you should have pnp0 and pcm0 in your kernel config as > appropriate. isapnp cards should not need any pnp lines in kernel.conf. > > the list of supported cards is as for luigi's driver, with the addition of a > couple more mss-clones, and trident 4dwave. there is a part done aureal > vortex driver which is as yet nonfunctional. mmap() is supported but not > well tested. format conversions are supported. the code seems to be > stable. > > please test it and email me success and failure reports. > > - cameron > It works ok for me, but one nice feature of the sound system would be if upon shutdown (I don't leave my machine on all the time right now) OS somehow looked at a config file (call it /etc/soundvol.conf) for mixer volumes, and set them to that as a default... Just an idea. KEnneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 18: 3:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 94F6E14D5D; Sun, 8 Aug 1999 18:03:45 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id UAA47932; Sun, 8 Aug 1999 20:59:37 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Sun, 8 Aug 1999 20:59:37 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Kenneth Wayne Culver Cc: Cameron Grant , multimedia@FreeBSD.org, current@FreeBSD.org Subject: Re: it's time... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Aug 1999, Kenneth Wayne Culver wrote: > It works ok for me, but one nice feature of the sound system would be if > upon shutdown (I don't leave my machine on all the time right now) OS > somehow looked at a config file (call it /etc/soundvol.conf) for mixer > volumes, and set them to that as a default... Just an idea. Don't you mean upon startup? If so, see my recent rc proposition for mixer settings. > > KEnneth Culver > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 18:18:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.prod.itd.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 9C9C514DCB; Sun, 8 Aug 1999 18:17:50 -0700 (PDT) (envelope-from cindy8520@britney.to) Received: from 154.5.137.195 (ip195.calgary5.dialup.canada.psi.net [154.5.137.195]) by swan.prod.itd.earthlink.net (8.9.3/8.9.3) with SMTP id SAA11178; Sun, 8 Aug 1999 18:13:53 -0700 (PDT) From: cindy8520@britney.to Message-Id: <199908090113.SAA11178@swan.prod.itd.earthlink.net> Date: Sun, 8 Aug 1999 15:39:02 Subject: Britney Spears Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiya!! My name is Cindy. I am teen female from FL. I made a Britney Spears Site, its callled Britney Power! If you want to know more about me you can visit it also. Check it out. http://Britney.to/power I will be waiting!! Please visit! Cindy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 18:39:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp4.erols.com (smtp4.erols.com [207.172.3.237]) by hub.freebsd.org (Postfix) with ESMTP id 32F6C150C6 for ; Sun, 8 Aug 1999 18:39:01 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (207-172-143-111.s48.as1.hgt.md.dialup.rcn.com [207.172.143.111]) by smtp4.erols.com (8.8.8/smtp-v1) with ESMTP id VAA25772; Sun, 8 Aug 1999 21:34:04 -0400 (EDT) Message-Id: <199908090134.VAA25772@smtp4.erols.com> X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990808222708.A21161@dcse.fee.vutbr.cz> Date: Sun, 08 Aug 1999 21:34:01 -0400 (EDT) From: John Baldwin To: Cejka Rudolf Subject: RE: VESA module doesn't work with ATI Mach64 RagePro Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Aug-99 Cejka Rudolf wrote: > > 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 > reported when I'm trying to unload/load vesa.ko module. Kernel reports > during boot: > > VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc024f622 (1000022) > VESA: ATI MACH64 These cards' VESA support sucks. It requires an extra software driver to be loaded, which they provide for DOS/Win9x, etc. I have a whole lab of 40 machines that use 320x200 splash screens as a result of this nonsense. :) --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 20:45:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id AC66F14EA4 for ; Sun, 8 Aug 1999 20:45:50 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:KFUDbgC/9QwTzPrGDvXvzkUsmWnNIxP+@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id MAA08410; Mon, 9 Aug 1999 12:43:57 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id MAA25802; Mon, 9 Aug 1999 12:48:16 +0900 (JST) Message-Id: <199908090348.MAA25802@zodiac.mech.utsunomiya-u.ac.jp> To: Cejka Rudolf Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: VESA module doesn't work with ATI Mach64 RagePro In-reply-to: Your message of "Sun, 08 Aug 1999 22:27:08 +0200." <19990808222708.A21161@dcse.fee.vutbr.cz> References: <19990808222708.A21161@dcse.fee.vutbr.cz> Date: Mon, 09 Aug 1999 12:48:15 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >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 >reported when I'm trying to unload/load vesa.ko module. Kernel reports >during boot: > >VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc024f622 (1000022) >VESA: ATI MACH64 > >Command "vidcontrol -i mode" reports lines below. It looks VESA module >can't read mode table properly. But simple VESA utilities in DOS are capable >to determine all VESA modes supported by ATI Mach64 card with VESA 2.0 BIOS. >Is this known problem? Or should I invetigate this problem further? There is a good possibility that the VESA BIOS extension for this card is provided in a DOS TSR program and the VESA BIOS entry in the ROM BIOS is just a stub. Such implementation is allowed in the VESA spec. Please examine the manual of the video card for information. Kazu > mode# flags type size font window linear buffer >------------------------------------------------------------------------------ > 0 (0x000) 0x00000001 T 40x25 8x8 0xb8000 32k 32k 0x00000000 32k [...] > 45 (0x02d) 0x00000000 T 90x43 8x8 0xb8000 32k 32k 0x00000000 32k > 46 (0x02e) 0x00000001 T 90x50 8x8 0xb8000 32k 32k 0x00000000 32k > 48 (0x030) 0x00000001 T 90x60 8x8 0xb8000 32k 32k 0x00000000 32k >112 (0x070) 0x00000000 T 80x43 8x8 0xb8000 32k 32k 0x00000000 32k >113 (0x071) 0x00000001 T 80x43 8x8 0xb8000 32k 32k 0x00000000 32k To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 22:32: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from mom.hooked.net (mom.hooked.net [206.80.6.10]) by hub.freebsd.org (Postfix) with ESMTP id A71B215132; Sun, 8 Aug 1999 22:32:05 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from fish.hooked.net (garbanzo@fish.hooked.net [206.80.6.48]) by mom.hooked.net (8.8.6/8.8.5) with SMTP id WAA24356; Sun, 8 Aug 1999 22:13:53 -0700 (PDT) Date: Sun, 8 Aug 1999 22:13:52 -0700 (PDT) From: Alex Zepeda To: "Brian F. Feldman" Cc: Kenneth Wayne Culver , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Aug 1999, Brian F. Feldman wrote: > > It works ok for me, but one nice feature of the sound system would be if > > upon shutdown (I don't leave my machine on all the time right now) OS > > somehow looked at a config file (call it /etc/soundvol.conf) for mixer > > volumes, and set them to that as a default... Just an idea. > > Don't you mean upon startup? If so, see my recent rc proposition for mixer > settings. Actually at shutdown would be cool. So it could save the current volumes, and restore them at startup. Altho, at suspend and resume time wouldn't be a bad idea either. - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 22:37: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles523.castles.com [208.214.165.87]) by hub.freebsd.org (Postfix) with ESMTP id 6D5B2150C9; Sun, 8 Aug 1999 22:37:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA15394; Sun, 8 Aug 1999 22:29:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908090529.WAA15394@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alex Zepeda Cc: "Brian F. Feldman" , Kenneth Wayne Culver , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: it's time... In-reply-to: Your message of "Sun, 08 Aug 1999 22:13:52 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Aug 1999 22:29:09 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 8 Aug 1999, Brian F. Feldman wrote: > > > > It works ok for me, but one nice feature of the sound system would be if > > > upon shutdown (I don't leave my machine on all the time right now) OS > > > somehow looked at a config file (call it /etc/soundvol.conf) for mixer > > > volumes, and set them to that as a default... Just an idea. > > > > Don't you mean upon startup? If so, see my recent rc proposition for mixer > > settings. > > Actually at shutdown would be cool. So it could save the current volumes, > and restore them at startup. Altho, at suspend and resume time wouldn't > be a bad idea either. Gosh, let's see; at shutdown it could edit /etc/rc.conf. Wouldn't that be handy? And so easy too. 8) -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 22:42:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 0DDF515139; Sun, 8 Aug 1999 22:42:03 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA00173; Mon, 9 Aug 1999 15:07:45 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990809150745:611=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: Date: Mon, 09 Aug 1999 15:07:45 +0930 (CST) From: "Daniel O'Connor" To: Alex Zepeda Subject: Re: it's time... Cc: current@FreeBSD.ORG, multimedia@FreeBSD.ORG, Cameron Grant , Kenneth Wayne Culver , "Brian F. Feldman" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990809150745:611=_ Content-Type: text/plain; charset=us-ascii On 09-Aug-99 Alex Zepeda wrote: > Actually at shutdown would be cool. So it could save the current volumes, > and restore them at startup. Altho, at suspend and resume time wouldn't > be a bad idea either. You could do it something like the way boot -c stuff or the splash screen is done, ie load a 'module' which is just a text file for the sound system to parse.. Don't know how you'd go unload'ing and load'ing the file though. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990809150745:611=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN65pKVbYW/HEoF9pAQGTlAP9GqvbAK4KEU8T5XRQqs3mLrjqBK6XWQvZ UU19005YRSIlG9ReksI2k+4nD8FY8tB2pltl0jykFT1JiLTjBN2x2A/OVg7Gsc1Y 2ctiIwqfgz6F4h/cHe9efFW/5SJUpm6R3TI6A5stfF5Q2qh0UMbsq6+L6vr3jzrz SeqYr4emMmg= =yGFP -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990809150745:611=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 22:42:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id D7348151B6; Sun, 8 Aug 1999 22:42:22 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA00187; Mon, 9 Aug 1999 15:08:19 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990809150819:611=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: <199908090529.WAA15394@dingo.cdrom.com> Date: Mon, 09 Aug 1999 15:08:19 +0930 (CST) From: "Daniel O'Connor" To: Mike Smith Subject: Re: it's time... Cc: current@FreeBSD.ORG, multimedia@FreeBSD.ORG, Cameron Grant , Kenneth Wayne Culver , "Brian F. Feldman" , Alex Zepeda Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990809150819:611=_ Content-Type: text/plain; charset=us-ascii On 09-Aug-99 Mike Smith wrote: > Gosh, let's see; at shutdown it could edit /etc/rc.conf. Wouldn't that > be handy? And so easy too. 8) Ahh but then you have to put up with the default sound levels until /etc/rc.conf is used :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990809150819:611=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN65pS1bYW/HEoF9pAQE8WgP/fiYM+/kE2c0iVlnPx72ISJUhh0xlhgkF x1mH3S39RKEb4Am/jxHlKWdmQJ0jC2QPhFABACLEqPCVv/CpbVlzupj53NvyNfMf bsj0Lc7kYMjfWKs4n1gI/6dW4+hY6/TOejQ0lWkgje5aGeVcN2zN+m1EAQpW1hVR T0i+UbkpCNQ= =ZWpQ -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990809150819:611=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 8 23:35:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 277F914EFD for ; Sun, 8 Aug 1999 23:35:32 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA51602; Mon, 9 Aug 1999 08:33:18 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199908090633.IAA51602@freebsd.dk> Subject: Re: VESA module doesn't work with ATI Mach64 RagePro In-Reply-To: <199908090348.MAA25802@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Aug 9, 1999 12:48:15 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Mon, 9 Aug 1999 08:33:18 +0200 (CEST) Cc: cejkar@dcse.fee.vutbr.cz, freebsd-current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kazutaka YOKOTA wrote: > > >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 > >reported when I'm trying to unload/load vesa.ko module. Kernel reports > >during boot: > > > >VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc024f622 (1000022) > >VESA: ATI MACH64 > > > >Command "vidcontrol -i mode" reports lines below. It looks VESA module > >can't read mode table properly. But simple VESA utilities in DOS are capable > >to determine all VESA modes supported by ATI Mach64 card with VESA 2.0 BIOS. > >Is this known problem? Or should I invetigate this problem further? > > There is a good possibility that the VESA BIOS extension for this card > is provided in a DOS TSR program and the VESA BIOS entry in the ROM > BIOS is just a stub. Such implementation is allowed in the VESA spec. Actually its because the ATI chip reports the modes as non-VGA modes, which is correct (sortof), and our VESA code rejects those modeentries. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 2:14:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from mom.hooked.net (mom.hooked.net [206.80.6.10]) by hub.freebsd.org (Postfix) with ESMTP id AA76D151F8; Mon, 9 Aug 1999 02:13:56 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from fish.hooked.net (garbanzo@fish.hooked.net [206.80.6.48]) by mom.hooked.net (8.8.6/8.8.5) with SMTP id CAA14070; Mon, 9 Aug 1999 02:11:52 -0700 (PDT) Date: Mon, 9 Aug 1999 02:11:51 -0700 (PDT) From: Alex Zepeda To: Mike Smith Cc: "Brian F. Feldman" , Kenneth Wayne Culver , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: <199908090529.WAA15394@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Aug 1999, Mike Smith wrote: > > On Sun, 8 Aug 1999, Brian F. Feldman wrote: > > > > > > It works ok for me, but one nice feature of the sound system would be if > > > > upon shutdown (I don't leave my machine on all the time right now) OS > > > > somehow looked at a config file (call it /etc/soundvol.conf) for mixer > > > > volumes, and set them to that as a default... Just an idea. > > > > > > Don't you mean upon startup? If so, see my recent rc proposition for mixer > > > settings. > > > > Actually at shutdown would be cool. So it could save the current volumes, > > and restore them at startup. Altho, at suspend and resume time wouldn't > > be a bad idea either. > > Gosh, let's see; at shutdown it could edit /etc/rc.conf. Wouldn't that > be handy? And so easy too. 8) Nah, it could store the values in, say, /etc/mixerX.vols, if the knob was enabled in rc.conf. Imagine for a moment one less thing to remember to tweak at boot time. Sure my AWE64 and 32PnP don't need tweaking upon startup if I don't mind waking everyone up when I play an mp3, but there are cards out there that default to a volume of zero. Sure it's nothing monumental, but it's a convience thing. I mean, if the FreeBSD project is opposed to convenience, why have /usr/local/etc/rc.d, or even rc.conf for that matter when one can enter this stuff in by hand each time at startup %) - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 2:19:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 7010714C28; Mon, 9 Aug 1999 02:19:38 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id SAA29884; Mon, 9 Aug 1999 18:46:34 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id SAA38283; Mon, 9 Aug 1999 18:46:33 +0930 (CST) Date: Mon, 9 Aug 1999 18:46:33 +0930 From: Greg Lehey To: FreeBSD current users , FreeBSD Committers Subject: Vinum RAID-5 broken Message-ID: <19990809184633.H31076@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to have broken something in Vinum's RAID-5 support while importing it to the source tree. It works fine when all disks are up, but things go to hell in degraded mode. I'll have it fixed in a day or two, but in the meantime don't try testing degraded mode: it don't work. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 2:25:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 49B4914BF9; Mon, 9 Aug 1999 02:25:06 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id SAA03125; Mon, 9 Aug 1999 18:52:10 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990809185210:611=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: Date: Mon, 09 Aug 1999 18:52:10 +0930 (CST) From: "Daniel O'Connor" To: Alex Zepeda Subject: Re: it's time... Cc: "Brian F. Feldman" Cc: "Brian F. Feldman" , Kenneth Wayne Culver , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990809185210:611=_ Content-Type: text/plain; charset=us-ascii On 09-Aug-99 Alex Zepeda wrote: > Why that complex? Couldn't I just drop in a small script using awk and > sh, to grab the mixer volumes, and drop it in rc.shutdown? Or even a > small C program would suffice if scripting isn't your cup of tea. Hmm.. true.. so have a shell script to write the file on shutdown, then load the file as a kernel mod on startup using the boot loader? That way you don't have that annoying window of time after the card has been initialised before /etc/rc is run :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990809185210:611=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN66dwlbYW/HEoF9pAQHcRQQAqCpfyKo5PpbWLy5TUksl44rrA0zbUSlm 9sQKNxRexWkWjIrxkdf/IR1tte0DzZlMXTLoScGkW83A+MLvy6IHhJG6SLy/a+By ThfUeW4S0u79bWcYBFjEalHJUafPiNO63iG0PHNHu0jpsld8AWYFcgjuRp8hKRCV ibSZ+5VoN+4= =tahN -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990809185210:611=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 2:32:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from mom.hooked.net (mom.hooked.net [206.80.6.10]) by hub.freebsd.org (Postfix) with ESMTP id 61B1A14EFD; Mon, 9 Aug 1999 02:32:36 -0700 (PDT) (envelope-from garbanzo@HOOKED.NET) Received: from fish.hooked.net (garbanzo@fish.hooked.net [206.80.6.48]) by mom.hooked.net (8.8.6/8.8.5) with SMTP id CAA14727; Mon, 9 Aug 1999 02:15:49 -0700 (PDT) Date: Mon, 9 Aug 1999 02:15:49 -0700 (PDT) From: Alex Zepeda To: "Daniel O'Connor" Cc: current@FreeBSD.ORG, multimedia@FreeBSD.ORG, Cameron Grant , Kenneth Wayne Culver , "Brian F. Feldman" Subject: Re: it's time... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Aug 1999, Daniel O'Connor wrote: > You could do it something like the way boot -c stuff or the splash screen is > done, ie load a 'module' which is just a text file for the sound system to > parse.. > > Don't know how you'd go unload'ing and load'ing the file though. Why that complex? Couldn't I just drop in a small script using awk and sh, to grab the mixer volumes, and drop it in rc.shutdown? Or even a small C program would suffice if scripting isn't your cup of tea. - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 2:33: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from mom.hooked.net (mom.hooked.net [206.80.6.10]) by hub.freebsd.org (Postfix) with ESMTP id 571B915226; Mon, 9 Aug 1999 02:32:55 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from fish.hooked.net (garbanzo@fish.hooked.net [206.80.6.48]) by mom.hooked.net (8.8.6/8.8.5) with SMTP id CAA17810; Mon, 9 Aug 1999 02:30:38 -0700 (PDT) Date: Mon, 9 Aug 1999 02:30:38 -0700 (PDT) From: Alex Zepeda To: "Daniel O'Connor" Cc: "Brian F. Feldman" , "Brian F. Feldman" , Kenneth Wayne Culver , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Aug 1999, Daniel O'Connor wrote: > > Why that complex? Couldn't I just drop in a small script using awk and > > sh, to grab the mixer volumes, and drop it in rc.shutdown? Or even a > > small C program would suffice if scripting isn't your cup of tea. > > Hmm.. true.. so have a shell script to write the file on shutdown, then load > the file as a kernel mod on startup using the boot loader? > > That way you don't have that annoying window of time after the card has been > initialised before /etc/rc is run :) Wha? Since neither the kernel nor the startup scripts really frob the sound devices much, another shell script could suffice for this too, no? I mean, I usually have to wait until after I've logged in to turn down the volume anyways. This could even be implemented (perhaps easier) thru the rc.d tree. Perhaps I'll do that tomorrow, and make a port out of it ;) Or am I just oversimplifying things? - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 2:59:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from arthur.caida.org (arthur.caida.org [204.212.46.6]) by hub.freebsd.org (Postfix) with ESMTP id AE286151A9; Mon, 9 Aug 1999 02:59:05 -0700 (PDT) (envelope-from dwm@arthur.caida.org) Received: from arthur.caida.org (localhost.caida.org [127.0.0.1]) by arthur.caida.org (8.9.0/8.9.0.Beta5) with ESMTP id FAA74200; Mon, 9 Aug 1999 05:56:58 -0400 (EDT) Message-Id: <199908090956.FAA74200@arthur.caida.org> Location: CAIDA Ann Arbor, MI To: Alex Zepeda Cc: "Daniel O'Connor" , current@FreeBSD.ORG, multimedia@FreeBSD.ORG, Cameron Grant , Kenneth Wayne Culver , "Brian F. Feldman" Subject: Re: it's time... In-reply-to: Message from of Mon Aug 9, 1999 2:15 PDT Date: Mon, 09 Aug 1999 05:56:58 -0400 From: Daniel McRobb Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 9 Aug 1999, Daniel O'Connor wrote: > > > You could do it something like the way boot -c stuff or the splash screen is > > done, ie load a 'module' which is just a text file for the sound system to > > parse.. > > > > Don't know how you'd go unload'ing and load'ing the file though. > > Why that complex? Couldn't I just drop in a small script using awk and > sh, to grab the mixer volumes, and drop it in rc.shutdown? Or even a > small C program would suffice if scripting isn't your cup of tea. > > - alex As far as I know, rc.shutdown doesn't get run unless you go to single user mode (for example, 'shutdown -h now' will not cause init to run rc.shutdown). Personally, I put my mixer settings in ~/.mixerrc, and load/save values there by running a script from ~/.xinitrc (load before starting window manager, save after window manager exits). But I never have a real need to use audio when I'm not running X (and no need to have any mixer settings before logon). Daniel ~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 7:34:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 9D5AF151EE for ; Mon, 9 Aug 1999 07:34:03 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn41.imasy.or.jp [202.227.24.233]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id XAA01774; Mon, 9 Aug 1999 23:31:26 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199908091431.XAA01774@tasogare.imasy.or.jp> To: plm@xs4all.nl Cc: iwasaki@jp.FreeBSD.org, freebsd-current@FreeBSD.ORG, imp@village.org Subject: Re: recent apm changes In-Reply-To: Your message of "Sun, 8 Aug 1999 21:52:32 +0200 (CEST)" <14253.57344.873947.122158@muon.xs4all.nl> References: <14253.57344.873947.122158@muon.xs4all.nl> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 09 Aug 1999 23:35:12 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 94 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG plm> In contract, if I suspend in Linux of Windows, the computer shuts up plm> immediateley and is quiet. Only sometimes there is a (not too loud) plm> little fan (I think it is the CPU fan) running for a few more minutes. I've read Linux code (v2.2.9) closely, noticed they put cli before APM BIOS call and save & restore segment registers. I suspect these two (or only cli?) affect the suspending state. To clarify, could you try attached patches (for sys/i386/i386/bioscall.s) one by one? # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # bioscall-1 # bioscall-2 # bioscall-3 # echo x - bioscall-1 sed 's/^X//' >bioscall-1 << 'END-of-bioscall-1' X--- i386/i386/bioscall.s.org Mon Aug 9 17:51:31 1999 X+++ i386/i386/bioscall.s Mon Aug 9 17:53:07 1999 X@@ -64,9 +64,16 @@ X movl 12(%ebp),%edx X movl 16(%ebp),%esi X movl 20(%ebp),%edi X+#if 1 /* cli hack */ X+ pushfl X+ cli X+#endif X pushl %ebp X lcall _bioscall_vector X popl %ebp X+#if 1 /* cli hack */ X+ popfl X+#endif X movl %eax,0(%ebp) X movl %ebx,4(%ebp) X movl %ecx,8(%ebp) END-of-bioscall-1 echo x - bioscall-2 sed 's/^X//' >bioscall-2 << 'END-of-bioscall-2' X--- i386/i386/bioscall.s.org Mon Aug 9 17:51:31 1999 X+++ i386/i386/bioscall.s Mon Aug 9 18:01:36 1999 X@@ -64,9 +64,17 @@ X movl 12(%ebp),%edx X movl 16(%ebp),%esi X movl 20(%ebp),%edi X+#if 1 /* segment regs hack */ X+ pushl %fs X+ pushl %gs X+#endif X pushl %ebp X lcall _bioscall_vector X popl %ebp X+#if 1 /* segment regs hack */ X+ popl %gs X+ popl %fs X+#endif X movl %eax,0(%ebp) X movl %ebx,4(%ebp) X movl %ecx,8(%ebp) END-of-bioscall-2 echo x - bioscall-3 sed 's/^X//' >bioscall-3 << 'END-of-bioscall-3' X--- i386/i386/bioscall.s.org Mon Aug 9 17:51:31 1999 X+++ i386/i386/bioscall.s Mon Aug 9 18:00:07 1999 X@@ -64,9 +64,20 @@ X movl 12(%ebp),%edx X movl 16(%ebp),%esi X movl 20(%ebp),%edi X+#if 1 /* cli + segment regs hack */ X+ pushfl X+ cli X+ pushl %fs X+ pushl %gs X+#endif X pushl %ebp X lcall _bioscall_vector X popl %ebp X+#if 1 /* cli + segment regs hack */ X+ popl %gs X+ popl %fs X+ popfl X+#endif X movl %eax,0(%ebp) X movl %ebx,4(%ebp) X movl %ecx,8(%ebp) END-of-bioscall-3 exit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 7:40:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from anch01.customcpu.com (anch01.customcpu.com [198.70.210.44]) by hub.freebsd.org (Postfix) with ESMTP id 61368150AF for ; Mon, 9 Aug 1999 07:40:36 -0700 (PDT) (envelope-from al7oj@customcpu.com) Received: from customcpu.com ([207.14.79.52]) by anch01.customcpu.com (Post.Office MTA v3.5.3 release 223 ID# 0-59598U2500L250S0V35) with ESMTP id com for ; Mon, 9 Aug 1999 06:37:44 -0800 Message-ID: <37AEE7F7.8EA393DD@customcpu.com> Date: Mon, 09 Aug 1999 06:38:47 -0800 From: "Michael A. Endsley" X-Mailer: Mozilla 4.61 [en] (OS/2; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: vty3 and 4.0 snap 080799 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just downloaded the latest snap (080799) and tried installing it. When getting to the media section and configuring ppp for a ftp install, I try going to vty3 (alt-f3). However, that vty is not available. I have tried this 3 times now. Is this broken? I did a search for this but have found nothing. Thanks, Mike al7oj@customcpu.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 8:11:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id EADF515216 for ; Mon, 9 Aug 1999 08:11:44 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA09774; Mon, 9 Aug 1999 09:09:42 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA19883; Mon, 9 Aug 1999 09:09:41 -0600 Date: Mon, 9 Aug 1999 09:09:41 -0600 Message-Id: <199908091509.JAA19883@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mitsuru IWASAKI Cc: plm@xs4all.nl, freebsd-current@FreeBSD.ORG, imp@village.org Subject: Re: recent apm changes In-Reply-To: <199908091431.XAA01774@tasogare.imasy.or.jp> References: <14253.57344.873947.122158@muon.xs4all.nl> <199908091431.XAA01774@tasogare.imasy.or.jp> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > plm> In contract, if I suspend in Linux of Windows, the computer shuts up > plm> immediateley and is quiet. Only sometimes there is a (not too loud) > plm> little fan (I think it is the CPU fan) running for a few more minutes. > > I've read Linux code (v2.2.9) closely, noticed they put cli > before APM BIOS call and save & restore segment registers. The CLI call is bogus. I note a commit I *just* made: ---------------------------- revision 1.49.2.4 date: 1999/07/10 18:36:59; author: nate; state: Exp; lines: +1 -2 - Remove un-necessary CLI statement from apm_int, which casues suspend/resume to fail on at least some IBM Thinkpads. [ FWIW, the cli call is also missing from -current ] Submitted by: "Kenton A. Hoover" ---------------------------- If the CLI is there, my box refuses to suspend. Apparently it was removed from linux a while back, and like many software projects that don't have usable history, the bug is now being re-introduced into Linux again. :( As far as the segment registers, we do an explicit save of them already when we switch into VM86 mode, so it should be necessary to save them twice. > I suspect these two (or only cli?) affect the suspending state. > To clarify, could you try attached patches (for sys/i386/i386/bioscall.s) > one by one? I'd be interested to know if either of the patches did anything... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 9:18:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 482501516C; Mon, 9 Aug 1999 09:18:50 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id MAA63368; Mon, 9 Aug 1999 12:14:57 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Mon, 9 Aug 1999 12:14:57 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Daniel McRobb Cc: Alex Zepeda , "Daniel O'Connor" , current@FreeBSD.org, multimedia@FreeBSD.org, Cameron Grant , Kenneth Wayne Culver Subject: Re: it's time... In-Reply-To: <199908090956.FAA74200@arthur.caida.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You guys don't see the point. The point is a single, simple place to put default mixer values for any number of devices, and fitting in with the current configuration file scenario. rc is the natural place for this, because _it_ gets run at startup. I just need to find somewhere to put this instead of rc.audio, because jkh vetoes it on that account... Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 9:19:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from maildns2.fsbdial.co.uk (s24.athenenet.co.uk [195.89.137.30]) by hub.freebsd.org (Postfix) with ESMTP id 1A8EF15256; Mon, 9 Aug 1999 09:19:24 -0700 (PDT) (envelope-from frankrj@netscape.net) Received: from [212.1.145.183] by maildns2.freenet.co.uk (NTMail 4.30.0012/NT0619.00.9914eb79) with ESMTP id lxzimaaa for ; Mon, 9 Aug 1999 17:15:36 +0100 Message-ID: <37AEFF63.1354B1C8@netscape.net> Date: Mon, 09 Aug 1999 17:18:43 +0100 From: Francis Jordan X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Cameron Grant Cc: multimedia@freebsd.org, current@freebsd.org Subject: Re: it's time... References: <000901bee13c$b1831dc0$0304020a@rings> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cameron Grant wrote: > > to let newpcm out of the cage so you can all get your grubby little hands on > it. > > http://www.vilnya.demon.co.uk/newpcm+dfrpnp-19990807.diff.gz > > this is a patch against a recent -current. if you have a pci or isapnp > soundcard, you should have pnp0 and pcm0 in your kernel config as > appropriate. isapnp cards should not need any pnp lines in kernel.conf. > > the list of supported cards is as for luigi's driver, with the addition of a > couple more mss-clones, and trident 4dwave. there is a part done aureal > vortex driver which is as yet nonfunctional. mmap() is supported but not > well tested. format conversions are supported. the code seems to be > stable. > > please test it and email me success and failure reports. > > - cameron Hi, First, I'd like to thank Cameron for his great work on the pcm driver. It builds and installs cleanly, and generally looks very impressive. I apologize in advance if the following message is a bit on the long side, but the problem I'm going to describe is very odd. I must also make clear that the sound card works fine under Windoze, and it also worked fine with the old pcm driver, until something got broken around 20 April this year (_after_ the integration of new bus). The sound card settings are changeable in the BIOS; this is what I have (the card is a non-PnP Yamaha): Sound: Enabled (other options are: Disabled and Auto) SB I/O address: 220-22F WSS I/O address: 530-538 Adlib I/O address: 388-38F MPU I/O address: 300-301 CTRL I/O address: 100 (OPL3 chip control) DMA A: DMA 1 (other options: 0,7) DMA B: DMA 0 (other options: 1,7) IRQ: IRQ 5 In accordance with these settings, I used the following line in the kernel: device pcm0 at isa? port 0x530 irq 5 drq 1 flags 0x10 (Note the order of the DMA channels - 1, then 0) Now this is what happens: the driver successfully detects the card, but fails to register an interrupt: /kernel: mss_detect - chip revision 0x0a /kernel: mss_detect() - Detected CS4231 /kernel: pcm0: at port 0x530-0x53f,0x310-0x311 irq 5 drq 1 flags 0xa210 on isa0 /kernel: pcm: setmap 30000, ff00; 0xc7bdd000 -> 30000 /kernel: pcm: setmap 40000, ff00; 0xc7bed000 -> 40000 /kernel: device combination doesn't support shared irq3 /kernel: intr_connect(irq3) failed, result=-1 /kernel: device combination doesn't support shared irq4 /kernel: intr_connect(irq4) failed, result=-1 /kernel: device combination doesn't support shared irq5 /kernel: intr_connect(irq5) failed, result=-1 /kernel: device combination doesn't support shared irq7 /kernel: intr_connect(irq7) failed, result=-1 /kernel: device combination doesn't support shared irq9 /kernel: intr_connect(irq9) failed, result=-1 /kernel: device combination doesn't support shared irq12 /kernel: intr_connect(irq12) failed, result=-1 /kernel: device combination doesn't support shared irq14 /kernel: intr_connect(irq14) failed, result=-1 /kernel: device combination doesn't support shared irq15 /kernel: intr_connect(irq15) failed, result=-1 IRQ 5 is definitely unused, and exactly the same setup worked fine with the old pcm driver. Another strange thing is that cat /dev/sndstat shows: FreeBSD Audio Driver (newpcm) Aug 8 1999 21:55:41 Installed devices: pcm0: at io 0x530 irq 5 drq 1:0 (1/1 channels duplex) as if everything were ok. It also seems that although intr_connect fails, IRQ 5 is marked as being in use, because pcic then chooses the next one available (10): /kernel: PC-Card VLSI 82C146 (5 mem & 2 I/O windows) /kernel: pcic: controller irq 10 Now the VERY odd thing: if I use DMA channels 0 and 1 (as opposed to 1 and 0), change the BIOS settings accordingly, and compile the kernel with device pcm0 at isa? port 0x530 irq 5 drq 0 flags 0x11 I get the following error: /kernel: mss_detect - chip revision 0x0a /kernel: mss_detect() - Detected CS4231 /kernel: pcm0: at port 0x530-0x53f,0x310-0x311 irq 5 flags 0xa211 on isa0 + /kernel: device_probe_and_attach: pcm0 attach returned 6 /kernel: device combination doesn't support shared irq3 /kernel: intr_connect(irq3) failed, result=-1 /kernel: device combination doesn't support shared irq4 /kernel: intr_connect(irq4) failed, result=-1 /kernel: device combination doesn't support shared irq7 /kernel: intr_connect(irq7) failed, result=-1 /kernel: device combination doesn't support shared irq9 /kernel: intr_connect(irq9) failed, result=-1 /kernel: device combination doesn't support shared irq12 /kernel: intr_connect(irq12) failed, result=-1 /kernel: device combination doesn't support shared irq14 /kernel: intr_connect(irq14) failed, result=-1 /kernel: device combination doesn't support shared irq15 /kernel: intr_connect(irq15) failed, result=-1 /kernel: PC-Card VLSI 82C146 (5 mem & 2 I/O windows) + /kernel: pcic: controller irq 5 and cat: /dev/sndstat: Device not configured As you can see, this time attach really failed, and pcic reused IRQ 5. (By the way, the problem is not specific to IRQ 5; e.g. I can disable the parallel port and give the sound card IRQ 7 - the results are the same.) Now what difference can the order of DMA channels possibly make? The error message about "shared" interrupts also looks suspect - why is the interrupt marked as shared? I guess the answer is somewhere in /sys/i386/isa/intr_machdep.c. Here's the relevant part from add_intrdesc(): if ((idesc->flags & INTR_EXCL) != 0 || (head->flags & INTR_EXCL) != 0) { /* * can't append new handler, if either list head or * new handler do not allow interrupts to be shared */ if (bootverbose) printf("\tdevice combination doesn't support " "shared irq%d\n", irq); return (-1); } The function add_intrdesc() is called from inthand_add(): idesc->handler = handler; idesc->argument = arg; idesc->maskptr = maskptr; idesc->intr = irq; idesc->flags = flags; /* block this irq */ oldspl = splq(1 << irq); /* add irq to class selected by maskptr */ errcode = add_intrdesc(idesc); splx(oldspl); if (errcode != 0) { if (bootverbose) printf("\tintr_connect(irq%d) failed, result=%d\n", irq, errcode); free(idesc->name, M_DEVBUF); free(idesc, M_DEVBUF); idesc = NULL; } return (idesc); inthand_add() is called from register_intr() as follows: flags |= INTR_EXCL; idesc = inthand_add("old", intr, isa_intr_wrap, irec, maskptr, flags); if (idesc == NULL) { free(irec, M_DEVBUF); return -1; } isareclist[intr] = irec; return 0; } (inthand_add is called from isa_setup_intr called from bus_setup_intr) Since inthand_add returns NULL, free() should free the interrupt. In the first case (DMA channels 1,0) it doesn't happen; in the second case (0,1) it does. Why? But the most important question is: why didn't it register the interrupt in the first place? Hope you multimedia gurus can explain what's going down. Thanks, Frank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 10:10:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles515.castles.com [208.214.165.79]) by hub.freebsd.org (Postfix) with ESMTP id 7ABAA15181 for ; Mon, 9 Aug 1999 10:10:35 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id KAA18706; Mon, 9 Aug 1999 10:01:28 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908091701.KAA18706@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: nate@mt.sri.com (Nate Williams) Cc: Mitsuru IWASAKI , plm@xs4all.nl, freebsd-current@FreeBSD.ORG, imp@village.org Subject: Re: recent apm changes In-reply-to: Your message of "Mon, 09 Aug 1999 09:09:41 MDT." <199908091509.JAA19883@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Aug 1999 10:01:28 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As far as the segment registers, we do an explicit save of them already > when we switch into VM86 mode, so it should be necessary to save them > twice. VM86 mode is only used to enable APM; after that we are using the 32-bit protected mode interface. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 10:15:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id E3953150D2 for ; Mon, 9 Aug 1999 10:15:50 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA10845; Mon, 9 Aug 1999 11:10:46 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA20764; Mon, 9 Aug 1999 11:10:45 -0600 Date: Mon, 9 Aug 1999 11:10:45 -0600 Message-Id: <199908091710.LAA20764@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: nate@mt.sri.com (Nate Williams), Mitsuru IWASAKI , plm@xs4all.nl, freebsd-current@FreeBSD.ORG, imp@village.org Subject: Re: recent apm changes In-Reply-To: <199908091701.KAA18706@dingo.cdrom.com> References: <199908091509.JAA19883@mt.sri.com> <199908091701.KAA18706@dingo.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > As far as the segment registers, we do an explicit save of them already > > when we switch into VM86 mode, so it should be necessary to save them > > twice. > > VM86 mode is only used to enable APM; after that we are using the > 32-bit protected mode interface. Ahh... In the old code, we used to explicitly push/pop all of the registers. Do we still do that? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 11: 5:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 5CD6214BEC for ; Mon, 9 Aug 1999 11:05:30 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA07745 for current@freebsd.org; Mon, 9 Aug 1999 13:42:47 -0400 From: Bill Paul Message-Id: <199908091742.NAA07745@skynet.ctr.columbia.edu> Subject: PCI bus on 486/66 no longer detected To: current@freebsd.org Date: Mon, 9 Aug 1999 13:42:46 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1798 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today I thought I would upgrade my 4.0 box from a July 15th snapshot to an August 9th snapshot. Only problem is I can't, because the August 9th snapshot's boot kernel refuses to locate my 486's PCI bus. Previously, the bus was detetected as follows: pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 tl0: irq 9 at device 13.0 on pci0 tl0: Ethernet address: 00:80:5f:9a:58:f1 xl0: <3Com 3cSOHO100-TX OfficeConnect> irq 12 at device 14.0 on pci0 xl0: Ethernet address: 00:10:5a:e3:60:9c xl0: autoneg complete, link status good (half-duplex, 100Mbps) pciconf -l shows the following: mcmillan# pciconf -l chip0@pci0:0:0: class=0x068000 card=0x00000000 chip=0x884910e0 rev=0x02 hdr=0x00 tl0@pci0:13:0: class=0x028000 card=0x00000000 chip=0xf1300e11 rev=0x10 hdr=0x00 xl0@pci0:14:0: class=0x020000 card=0x764610b7 chip=0x764610b7 rev=0x30 hdr=0x00 No, I didn't change any hardware setting anywhere. The older kernel still boots and works properly (I couldn't install the new snapshot because I need to do a network install, and my network cards are PCI). I have no idea where to look for the problem. Anybody have any bright ideas? -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 11:48: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from exegrnnts001.seattleu.edu (exegrnnts001.seattleu.edu [206.81.198.91]) by hub.freebsd.org (Postfix) with ESMTP id E333715152; Mon, 9 Aug 1999 11:47:50 -0700 (PDT) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu (ppp28.pm2a.wport.com [206.129.99.77]) by exegrnnts001.seattleu.edu with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id QS0G6DFJ; Mon, 9 Aug 1999 11:45:20 -0700 Message-ID: <37AF21B3.BDF4D6D6@seattleu.edu> Date: Mon, 09 Aug 1999 11:45:07 -0700 From: Eric Hodel Organization: Dis X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Daniel O'Connor Cc: current@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: it's time... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor wrote: > > On 09-Aug-99 Alex Zepeda wrote: > > Actually at shutdown would be cool. So it could save the current > volumes, > > and restore them at startup. Altho, at suspend and resume time > wouldn't > > be a bad idea either. > > You could do it something like the way boot -c stuff or the splash > screen is > done, ie load a 'module' which is just a text file for the sound system > to > parse.. > > Don't know how you'd go unload'ing and load'ing the file though. Wouldn't it be just like a splash screen? kldload volume.conf -t volume_data (or whatever) -- Eric Hodel hodeleri@seattleu.edu "They cook your gonies" -Terry Lambert's uncle on why he doesn't have a microwave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 13: 7:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id D9A0814FBE for ; Mon, 9 Aug 1999 13:07:49 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id NAA41806 for ; Mon, 9 Aug 1999 13:04:05 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Mon, 9 Aug 1999 13:04:04 -0700 (PDT) From: Doug X-Sender: doug@dt011n65.san.rr.com To: freebsd-current@freebsd.org Subject: wd0: interrupt timeout (status 58 error 1) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm starting to see the following errors more frequently on my 3 servers running current dated July 30. Aug 6 14:08:36 /kernel: wd0: interrupt timeout (status 58 error 1) Aug 6 14:08:38 /kernel: wd0: wdtimeout() DMA status 4 All 3 servers locked up over the weekend, although I have a feeling that the problem that locked them up was an nfs mount problem (more to come on that one when I get the details). However any insights into this wd problem are welcome. All 3 servers are custom boxes running intel N440BX mb's, dual PIII-500's, 512 megs of ram and (unfortunately) a mixture of quantum and western digital IDE hard disks. Here's a dmesg quote from one of them: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S Unless someone has something for me to check I'm going to try upgrading my -current today and see if that helps. These messages seem to be coming concurrent with time periods where the boxes enter heavy swapping, although it's tough to tell which one (or even if) is causing the other. Other tests indicate that the swapping problems are caused by some errant CGI scripts, which is what the boxes are set up to handle (cgi in general, not errant ones :). TIA, Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 13:28:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.keycomp.net (www.keycomp.net [207.44.1.33]) by hub.freebsd.org (Postfix) with ESMTP id 094DB14C2F for ; Mon, 9 Aug 1999 13:28:48 -0700 (PDT) (envelope-from billieakay@yahoo.com) Received: from bopper (kc-rmt03.keycomp.net [207.44.1.5]) by www.keycomp.net (8.8.5/SCO5) with SMTP id QAA04404 for ; Mon, 9 Aug 1999 16:32:52 -0400 (EDT) Message-ID: <000501bee2a4$64def5c0$01010101@bopper> From: "Bill A. K." To: Date: Mon, 9 Aug 1999 16:18:48 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 13:41:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from web1003.mail.yahoo.com (web1003.mail.yahoo.com [128.11.23.93]) by hub.freebsd.org (Postfix) with SMTP id DA4A8152C9 for ; Mon, 9 Aug 1999 13:41:50 -0700 (PDT) (envelope-from bvmcg@yahoo.com) Message-ID: <19990809203927.251.rocketmail@web1003.mail.yahoo.com> Received: from [24.29.199.43] by web1003.mail.yahoo.com; Mon, 09 Aug 1999 13:39:27 PDT Date: Mon, 9 Aug 1999 13:39:27 -0700 (PDT) From: Brian McGroarty Reply-To: brian@pobox.com Subject: Re: wd0: interrupt timeout (status 58 error 1) To: Doug , freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FWIW - I enabled APM over the weekend, configuring drives to spin down when not used for a good period of time. I get the message you list below, alternately with status 50 and 58, any time a drive needs to spin up. Myself, I'm curious about why the access light stays on on just one of the three hard drives once it's gone to sleep and come up again. The identical hard drive on the primary drive controller doesn't exhibit this behavior. --- Doug wrote: > I'm starting to see the following errors more frequently on > my 3 > servers running current dated July 30. > > Aug 6 14:08:36 /kernel: wd0: interrupt timeout > (status 58 error 1) > Aug 6 14:08:38 /kernel: wd0: wdtimeout() DMA > status 4 _____________________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 14: 7:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 9FCD115303 for ; Mon, 9 Aug 1999 14:07:29 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id OAA42097; Mon, 9 Aug 1999 14:05:17 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Mon, 9 Aug 1999 14:05:17 -0700 (PDT) From: Doug X-Sender: doug@dt011n65.san.rr.com To: brian@pobox.com Cc: Doug , freebsd-current@freebsd.org Subject: Re: wd0: interrupt timeout (status 58 error 1) In-Reply-To: <19990809203927.251.rocketmail@web1003.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Aug 1999, Brian McGroarty wrote: > FWIW - I enabled APM over the weekend, configuring drives to > spin down when not used for a good period of time. I get the > message you list below, alternately with status 50 and 58, any > time a drive needs to spin up. Thanks for the response. FWIW I have no apm enabled and these drives don't have a chance to spin down since they're always busy when under load. Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 14:15:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.49]) by hub.freebsd.org (Postfix) with ESMTP id 00DDE15187 for ; Mon, 9 Aug 1999 14:15:28 -0700 (PDT) (envelope-from plm@smtp3.xs4all.nl) Received: from localhost. (dc2-isdn59.dial.xs4all.nl [194.109.148.59]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id TAA10425; Mon, 9 Aug 1999 19:51:11 +0200 (CEST) Received: (from plm@localhost) by localhost. (8.9.3/8.9.1) id TAA00274; Mon, 9 Aug 1999 19:51:10 +0200 (MET DST) (envelope-from plm) From: Peter Mutsaers MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14255.5384.805557.274800@muon.xs4all.nl> Date: Mon, 9 Aug 1999 19:51:04 +0200 (MET DST) To: Mitsuru IWASAKI Cc: freebsd-current@FreeBSD.ORG, imp@village.org Subject: Re: recent apm changes In-Reply-To: <199908091431.XAA01774@tasogare.imasy.or.jp> References: <14253.57344.873947.122158@muon.xs4all.nl> <199908091431.XAA01774@tasogare.imasy.or.jp> X-Mailer: VM 6.65 under Emacs 20.3.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> "MI" == Mitsuru IWASAKI writes: plm> In contract, if I suspend in Linux of Windows, the computer shuts up plm> immediateley and is quiet. Only sometimes there is a (not too loud) plm> little fan (I think it is the CPU fan) running for a few more minutes. MI> I've read Linux code (v2.2.9) closely, noticed they put cli MI> before APM BIOS call and save & restore segment registers. I MI> suspect these two (or only cli?) affect the suspending state. MI> To clarify, could you try attached patches (for MI> sys/i386/i386/bioscall.s) one by one? I've tried them all. They don't make a difference alas. In doing so, to my surprise I found out that when I suspend my computer in FreeBSD, it isn't suspended at all! I have an ATX case with an Asus P2B motherboard. When I suspend my computer, the power led starts flashing (and keeps doing so). When I suspend my computer in Linux or Windows, as mentioned, the computer gets quiet (HDD spins down etc). The led flashes. Now I found out that when I suspend it in FreeBSD (either with sleep 1; zzz or with the suspend button or through the BIOS timer), the led starts flashing, but processes just keep running! I never paid attention to it, but I got suspicious because I'm running setiathome which accesses the harddrive occasionally, and even during suspend mode I heard the typical HDD sound sometimes. So the problem is not an incomplete suspend, but no suspend at all. It seems to suspend at first, the led starts flashing, the screen is blanked, but somehow the computer keeps running. -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know plm@xs4all.nl | the Netherlands | what I'm doing. ---------------+---------------------+------------------ Powered by FreeBSD (-current). See http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 14:26:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A1DA214D75 for ; Mon, 9 Aug 1999 14:26:06 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA14094; Mon, 9 Aug 1999 15:23:52 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA08002; Mon, 9 Aug 1999 15:23:55 -0600 (MDT) Message-Id: <199908092123.PAA08002@harmony.village.org> To: Peter Mutsaers Subject: Re: recent apm changes Cc: Mitsuru IWASAKI , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 09 Aug 1999 19:51:04 +0200." <14255.5384.805557.274800@muon.xs4all.nl> References: <14255.5384.805557.274800@muon.xs4all.nl> <14253.57344.873947.122158@muon.xs4all.nl> <199908091431.XAA01774@tasogare.imasy.or.jp> Date: Mon, 09 Aug 1999 15:23:55 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14255.5384.805557.274800@muon.xs4all.nl> Peter Mutsaers writes: : it, but I got suspicious because I'm running setiathome which accesses : the harddrive occasionally, and even during suspend mode I heard the : typical HDD sound sometimes. When I had my Libreto 50CT, I found that apm -Z (put into standby) would not work if there were any interrupts pending. These include any key releases that haven't happened by the time the suspend suspended, disk, serial I/O (I think, I only saw this once) and mouse I/O. If none of these things happened, it would standby correctly. I'm not sure what to do about this.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 16:35:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from wenet.net (pm3-23.ppp.wenet.net [206.15.85.23]) by hub.freebsd.org (Postfix) with ESMTP id 5D98E1532B; Mon, 9 Aug 1999 16:35:28 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by wenet.net (8.9.3/8.9.1) with ESMTP id QAA01099; Mon, 9 Aug 1999 16:31:00 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 9 Aug 1999 16:30:59 -0700 (PDT) From: Alex Zepeda To: "Brian F. Feldman" Cc: Daniel McRobb , "Daniel O'Connor" , current@FreeBSD.ORG, multimedia@FreeBSD.ORG, Cameron Grant , Kenneth Wayne Culver Subject: Re: it's time... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Aug 1999, Brian F. Feldman wrote: > You guys don't see the point. The point is a single, simple place to put > default mixer values for any number of devices, and fitting in with the > current configuration file scenario. rc is the natural place for this, > because _it_ gets run at startup. I just need to find somewhere to put > this instead of rc.audio, because jkh vetoes it on that account... One could stuff it into rc.conf, but this means it's harder to automagically save the state upon shutdown/reboot. But something like: deviceX_mixerdevice_vol = yy might work, and allow for multiple sound card. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 17:57:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id D027D14D75; Mon, 9 Aug 1999 17:57:32 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA14093; Tue, 10 Aug 1999 10:24:50 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990810102449:611=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: Date: Tue, 10 Aug 1999 10:24:49 +0930 (CST) From: "Daniel O'Connor" To: "Brian F. Feldman" Subject: Re: it's time... Cc: Kenneth Wayne Culver Cc: Kenneth Wayne Culver , Cameron Grant , multimedia@FreeBSD.org, current@FreeBSD.org, Alex Zepeda , Daniel McRobb Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990810102449:611=_ Content-Type: text/plain; charset=us-ascii On 09-Aug-99 Brian F. Feldman wrote: > You guys don't see the point. The point is a single, simple place to put > default mixer values for any number of devices, and fitting in with the > current configuration file scenario. rc is the natural place for this, > because _it_ gets run at startup. I just need to find somewhere to put > this instead of rc.audio, because jkh vetoes it on that account... Sure.. but you still have window of time where the audio is at its default level before the rc stuff is run.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990810102449:611=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN694WVbYW/HEoF9pAQG18QP/WH/288/KZwUlIYU/fs2a5ap9jRgFXqm2 woB8NxWlNIuvcvND6aHT75q2gyiWn7+KfK3STbqkzqDc/WIYBlvKAOHjD54rLRzu jhACXlxRuyIkjq3ZMXNYzh5T6KFs+N65mRPksFE0ynsFwl/rV3AORKDwnyVxhvsh R41nwoE2L8A= =TLce -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990810102449:611=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 18: 8:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id 1397B1511A; Mon, 9 Aug 1999 18:08:15 -0700 (PDT) (envelope-from sanpei@sanpei.org) Received: from oxygen.yy.ics.keio.ac.jp (oxygen.yy.ics.keio.ac.jp [131.113.47.3]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id KAA14889; Tue, 10 Aug 1999 10:03:51 +0900 (JST) Received: from lavender.yy.cs.keio.ac.jp (ppp121.dialup.st.keio.ac.jp [131.113.27.121]) by oxygen.yy.ics.keio.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id KAA01654; Tue, 10 Aug 1999 10:03:48 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id KAA02032; Tue, 10 Aug 1999 10:03:46 +0900 (JST) Date: Tue, 10 Aug 1999 10:03:46 +0900 (JST) Message-Id: <199908100103.KAA02032@lavender.yy.cs.keio.ac.jp> To: dwm@caida.org Cc: garbanzo@hooked.net, doconnor@gsoft.com.au, current@FreeBSD.ORG, multimedia@FreeBSD.ORG, gandalf@vilnya.demon.co.uk, culverk@wam.umd.edu, green@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: Your message of "Mon, 9 Aug 1999 18:56:58 JST". <199908090956.FAA74200@arthur.caida.org> From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dwm@caida.org wrote: >> >> As far as I know, rc.shutdown doesn't get run unless you go to single >> user mode (for example, 'shutdown -h now' will not cause init to run >> rc.shutdown). I think FreeBSD-current was fixed and everytime run rc.shutdown. SEE GNATS DB bin/12093. http://www.freebsd.org/cgi/query-pr.cgi?pr=12093 MIHIRA Sanpei Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 18: 8:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id EB13B15458 for ; Mon, 9 Aug 1999 18:08:45 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id DAA08856 for freebsd-current@FreeBSD.ORG; Tue, 10 Aug 1999 03:05:29 +0200 (CEST) (envelope-from olli) Date: Tue, 10 Aug 1999 03:05:29 +0200 (CEST) From: Oliver Fromme Message-Id: <199908100105.DAA08856@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: wd0: interrupt timeout (status 58 error 1) Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug wrote in list.freebsd-current: > On Mon, 9 Aug 1999, Brian McGroarty wrote: > > > FWIW - I enabled APM over the weekend, configuring drives to > > spin down when not used for a good period of time. I get the > > message you list below, alternately with status 50 and 58, any > > time a drive needs to spin up. > > Thanks for the response. FWIW I have no apm enabled and these > drives don't have a chance to spin down since they're always busy when > under load. Do those drives happen to be IBM DeskStar drives? They spin down automatically when they have not been turned off for about a week, in order to clean the heads. It's a feature. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 18:28:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 477F0152B2 for ; Mon, 9 Aug 1999 18:28:11 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn13.imasy.or.jp [202.227.24.205]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id KAA19675; Tue, 10 Aug 1999 10:25:47 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199908100125.KAA19675@tasogare.imasy.or.jp> To: plm@xs4all.nl Cc: iwasaki@jp.FreeBSD.org, freebsd-current@FreeBSD.ORG, imp@village.org, nate@mt.sri.com Subject: Re: recent apm changes In-Reply-To: Your message of "Mon, 9 Aug 1999 19:51:04 +0200 (MET DST)" <14255.5384.805557.274800@muon.xs4all.nl> References: <14255.5384.805557.274800@muon.xs4all.nl> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 10 Aug 1999 10:29:33 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 31 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > MI> I've read Linux code (v2.2.9) closely, noticed they put cli > MI> before APM BIOS call and save & restore segment registers. I > MI> suspect these two (or only cli?) affect the suspending state. > MI> To clarify, could you try attached patches (for > MI> sys/i386/i386/bioscall.s) one by one? > > I've tried them all. They don't make a difference alas. > > In doing so, to my surprise I found out that when I suspend my computer > in FreeBSD, it isn't suspended at all! > > I have an ATX case with an Asus P2B motherboard. When I suspend my > computer, the power led starts flashing (and keeps doing so). > > When I suspend my computer in Linux or Windows, as mentioned, the > computer gets quiet (HDD spins down etc). The led flashes. Hmmm, the CLI call is not useful in this case... I also had another kind of problem about CLI, my box froze sometimes when suspending. It shouldn't be put CLI in here as Nate mentioned. Segment regisers also wasn't related with the problem. I watched %fs before & after BIOS call using ddb, the value didn't change on my box. I guess Linux code only expects some BIOSes manipulate segment registers. Another possibility is *delay mechanism* on suspend (and standby). AFAIK, Linux, NetBSD and PAO has this but CURRENT. I'll make patch tonight based on PAO APM code. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 19:43:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 9F0631516E; Mon, 9 Aug 1999 19:43:40 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id WAA80119; Mon, 9 Aug 1999 22:41:17 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Mon, 9 Aug 1999 22:41:17 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: "Daniel O'Connor" Cc: Kenneth Wayne Culver , Kenneth Wayne Culver , Cameron Grant , multimedia@FreeBSD.org, current@FreeBSD.org, Alex Zepeda , Daniel McRobb Subject: Re: it's time... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Aug 1999, Daniel O'Connor wrote: > > On 09-Aug-99 Brian F. Feldman wrote: > > You guys don't see the point. The point is a single, simple place to put > > default mixer values for any number of devices, and fitting in with the > > current configuration file scenario. rc is the natural place for this, > > because _it_ gets run at startup. I just need to find somewhere to put > > this instead of rc.audio, because jkh vetoes it on that account... > > Sure.. but you still have window of time where the audio is at its default > level before the rc stuff is run.. Why... would audio be playing from rc? Bear in mind, it would be set even before rc.local... > > --- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 19:49:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 56A6A1516E; Mon, 9 Aug 1999 19:49:37 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id WAA80196; Mon, 9 Aug 1999 22:47:15 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Mon, 9 Aug 1999 22:47:15 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Alex Zepeda Cc: Daniel McRobb , "Daniel O'Connor" , current@FreeBSD.org, multimedia@FreeBSD.org, Cameron Grant , Kenneth Wayne Culver Subject: Re: it's time... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Aug 1999, Alex Zepeda wrote: > One could stuff it into rc.conf, but this means it's harder to > automagically save the state upon shutdown/reboot. But something like: Not really. You could do it with grep, awk, sed, or whatever you want, easily. The only possible problem would be... Getting it actually run at shutdown. > > deviceX_mixerdevice_vol = yy > > might work, and allow for multiple sound card. It's at http://janus.syracuse.net/~green/rc.audio.patch, not vapor :) > > - alex > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 20: 3:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 6D9641533B; Mon, 9 Aug 1999 20:03:33 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA20897; Mon, 9 Aug 1999 23:00:57 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id XAA05578; Mon, 9 Aug 1999 23:00:56 -0400 (EDT) Received: from localhost by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA05574; Mon, 9 Aug 1999 23:00:55 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Mon, 9 Aug 1999 23:00:55 -0400 (EDT) From: Kenneth Wayne Culver To: "Daniel O'Connor" Cc: "Brian F. Feldman" , Cameron Grant , multimedia@FreeBSD.org, current@FreeBSD.org, Alex Zepeda , Daniel McRobb Subject: Re: it's time... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 09-Aug-99 Brian F. Feldman wrote: > > You guys don't see the point. The point is a single, simple place to put > > default mixer values for any number of devices, and fitting in with the > > current configuration file scenario. rc is the natural place for this, > > because _it_ gets run at startup. I just need to find somewhere to put > > this instead of rc.audio, because jkh vetoes it on that account... > > Sure.. but you still have window of time where the audio is at its default > level before the rc stuff is run.. > > --- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > I didn't really mean to cause all this... I just wanted to have the mixer be at the levels I left it at when I shutdown the machine... I don't think we need all this argument about it. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 20:41:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 05C3A15338; Mon, 9 Aug 1999 20:41:28 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA16038; Tue, 10 Aug 1999 13:06:59 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990810130659:611=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: Date: Tue, 10 Aug 1999 13:06:59 +0930 (CST) From: "Daniel O'Connor" To: "Brian F. Feldman" Subject: Re: it's time... Cc: Daniel McRobb , Alex Zepeda , current@FreeBSD.org, multimedia@FreeBSD.org, Cameron Grant , Kenneth Wayne Culver Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990810130659:611=_ Content-Type: text/plain; charset=us-ascii On 10-Aug-99 Brian F. Feldman wrote: > > Sure.. but you still have window of time where the audio is at its default > > level before the rc stuff is run.. > Why... would audio be playing from rc? Bear in mind, it would be set > even before rc.local... I have a radio connected to line in on my sound card. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990810130659:611=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN6+eW1bYW/HEoF9pAQHf2gQApbbxxpDaEa/NXgzL9oVR1a3uTJzYJPGo EkB/+pznR6eY16xxl4SQp0GWhhc+n2TBbQtVxdZd2TjK+FiQGbo0YSiYhi1/uX82 FGQvvISEwmAdC7z/v55bgkffHMBGH4SwFvB7v+QHEufa9Udan9aMfRbiWdlFuAvA cIcyOVTVdPU= =krGW -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990810130659:611=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 20:43: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 885CE15338; Mon, 9 Aug 1999 20:43:02 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id XAA81003; Mon, 9 Aug 1999 23:40:38 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Mon, 9 Aug 1999 23:40:38 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: "Daniel O'Connor" Cc: Daniel McRobb , Alex Zepeda , current@FreeBSD.org, multimedia@FreeBSD.org, Cameron Grant , Kenneth Wayne Culver Subject: Re: it's time... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Aug 1999, Daniel O'Connor wrote: > > On 10-Aug-99 Brian F. Feldman wrote: > > > Sure.. but you still have window of time where the audio is at its default > > > level before the rc stuff is run.. > > Why... would audio be playing from rc? Bear in mind, it would be set > > even before rc.local... > > I have a radio connected to line in on my sound card. Then that would be playing during the entire bootup, wouldn't it? What, does it play only after the card has been detected? > > --- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 20:58: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id AD41214EB6; Mon, 9 Aug 1999 20:57:53 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA16315; Tue, 10 Aug 1999 13:22:17 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990810132217:611=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: Date: Tue, 10 Aug 1999 13:22:17 +0930 (CST) From: "Daniel O'Connor" To: "Brian F. Feldman" Subject: Re: it's time... Cc: Kenneth Wayne Culver Cc: Kenneth Wayne Culver , Cameron Grant , multimedia@FreeBSD.org, current@FreeBSD.org, Alex Zepeda , Daniel McRobb Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990810132217:611=_ Content-Type: text/plain; charset=us-ascii On 10-Aug-99 Brian F. Feldman wrote: > > I have a radio connected to line in on my sound card. > Then that would be playing during the entire bootup, wouldn't it? What, > does it play only after the card has been detected? The sound card shuts up after reset, and only starts outputing noise again after the sound card has been probed/attached. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990810132217:611=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN6+h8FbYW/HEoF9pAQElPAP+MVMxNOv0MgXiKLarI0/whxzdEHqrsBou lxqNRMt3/cSklHPmxUwqFuVh4Krpsh2Ge0Cm2OrXtZDb+sI7iaTy7YKFuRKvcu6w 7oWZQeU/0sj8yLmX1AilcmvT+fiHFThjPHjUhi094x0K7pHksM8e77DaN4CnDUQw FiJ93V1/jvk= =omz/ -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990810132217:611=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 9 23:38:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id C53F914D70 for ; Mon, 9 Aug 1999 23:38:25 -0700 (PDT) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.3/8.9.3) with ESMTP id IAA47610 for ; Tue, 10 Aug 1999 08:37:50 +0200 (CEST) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.9.3/8.9.3) id IAA55920 for freebsd-current@freebsd.org; Tue, 10 Aug 1999 08:37:49 +0200 (CEST) Date: Tue, 10 Aug 1999 08:37:49 +0200 From: Cejka Rudolf To: freebsd-current@freebsd.org Subject: Re: VESA module doesn't work with ATI Mach64 RagePro Message-ID: <19990810083749.A55581@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Soren Schmidt on Mon, Aug 09, 1999 at 08:33:18AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote (1999/08/09): > It seems Kazutaka YOKOTA wrote: > > There is a good possibility that the VESA BIOS extension for this card > > is provided in a DOS TSR program and the VESA BIOS entry in the ROM > > BIOS is just a stub. Such implementation is allowed in the VESA spec. > Actually its because the ATI chip reports the modes as non-VGA modes, > which is correct (sortof), and our VESA code rejects those modeentries. Yes, thanks. Information reported by 0x4F01 function about any video mode has set MODE_NON_VGA attribute indeed. And now I have found DOS TSR program for VESA support... I hate VESA 2.0/3.0 specification :-( I hate ATI :-( Is there any good AGP graphics card with full BIOS support in hardware? -- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 0: 7: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 72F5C14C22 for ; Tue, 10 Aug 1999 00:06:56 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA54482; Tue, 10 Aug 1999 09:04:55 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199908100704.JAA54482@freebsd.dk> Subject: Re: VESA module doesn't work with ATI Mach64 RagePro In-Reply-To: <19990810083749.A55581@dcse.fee.vutbr.cz> from Cejka Rudolf at "Aug 10, 1999 8:37:49 am" To: cejkar@dcse.fee.vutbr.cz (Cejka Rudolf) Date: Tue, 10 Aug 1999 09:04:55 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Cejka Rudolf wrote: > > Soren Schmidt wrote (1999/08/09): > > > It seems Kazutaka YOKOTA wrote: > > > There is a good possibility that the VESA BIOS extension for this card > > > is provided in a DOS TSR program and the VESA BIOS entry in the ROM > > > BIOS is just a stub. Such implementation is allowed in the VESA spec. > > > Actually its because the ATI chip reports the modes as non-VGA modes, > > which is correct (sortof), and our VESA code rejects those modeentries. > > Yes, thanks. Information reported by 0x4F01 function about any video > mode has set MODE_NON_VGA attribute indeed. And now I have found DOS TSR > program for VESA support... > > I hate VESA 2.0/3.0 specification :-( I hate ATI :-( Well well, no need to be that excited, if you hack out the test, the BIOS will willingly setup the modes that you get. And IIRC we can now support linear framebuffers in graphics modes, so support should be fairly easy to add.. > Is there any good AGP graphics card with full BIOS support in hardware? Dunno, but chances are getting smaller every day, most vendors relies on winblows drivers delivered with the cards nowadays.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 3:54:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from wenet.net (pm3-34.ppp.wenet.net [206.15.85.34]) by hub.freebsd.org (Postfix) with ESMTP id 9D15D15054; Tue, 10 Aug 1999 03:54:34 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by wenet.net (8.9.3/8.9.1) with ESMTP id DAA00859; Tue, 10 Aug 1999 03:52:48 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Tue, 10 Aug 1999 03:52:47 -0700 (PDT) From: Alex Zepeda To: "Daniel O'Connor" Cc: "Brian F. Feldman" , Kenneth Wayne Culver , Cameron Grant , multimedia@FreeBSD.org, current , Daniel McRobb Subject: Re: it's time... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Aug 1999, Daniel O'Connor wrote: > The sound card shuts up after reset, and only starts outputing noise again > after the sound card has been probed/attached. Perhaps the attach routine (or rc.something) should explicitly zero all the volumes, so that the card will remain silent until the knobs are called. - alex Experience something different With our new imported dolly She's lovely, warm, inflatable And we guarantee her joy - The Police To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 3:58: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from wenet.net (pm3-34.ppp.wenet.net [206.15.85.34]) by hub.freebsd.org (Postfix) with ESMTP id 5505B14A2E; Tue, 10 Aug 1999 03:58:00 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by wenet.net (8.9.3/8.9.1) with ESMTP id DAA00870; Tue, 10 Aug 1999 03:57:03 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Tue, 10 Aug 1999 03:57:02 -0700 (PDT) From: Alex Zepeda To: "Brian F. Feldman" Cc: current , multimedia@FreeBSD.org Subject: Re: it's time... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Aug 1999, Brian F. Feldman wrote: > On Mon, 9 Aug 1999, Alex Zepeda wrote: > > > One could stuff it into rc.conf, but this means it's harder to > > automagically save the state upon shutdown/reboot. But something like: > > Not really. You could do it with grep, awk, sed, or whatever you want, > easily. The only possible problem would be... Getting it actually run > at shutdown. I missed jkh's argument, but as far as I'm concerned, my first choice for this audio init stuff would be: * a SysV style script (and then having rc.shutdown call /usr/local/etc/rc.d/* w/ $1==stop; but that's another thread). * an rc.audio or rc.multimedia (this could perhaps contain some bt484 related things). But if it goes into "the" rc.conf, that would mean that whenever it runs at shutdown, it edits rc.conf; this isn't IMO a real great idea. Anything automated (even sysinstall) editing rc.conf in any way shape or form makes me leery because it's so much more error prone. > It's at http://janus.syracuse.net/~green/rc.audio.patch, not vapor :) When I wake up today, I'll check that out :^) - alex Experience something different With our new imported dolly She's lovely, warm, inflatable And we guarantee her joy - The Police To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 4: 4:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.erols.com (smtp2.erols.com [207.172.3.235]) by hub.freebsd.org (Postfix) with ESMTP id 2242714A2E for ; Tue, 10 Aug 1999 04:04:29 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (207-172-143-111.s48.as1.hgt.md.dialup.rcn.com [207.172.143.111]) by smtp2.erols.com (8.8.8/8.8.5) with ESMTP id HAA14356; Tue, 10 Aug 1999 07:05:28 -0400 (EDT) Message-Id: <199908101105.HAA14356@smtp2.erols.com> X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990810083749.A55581@dcse.fee.vutbr.cz> Date: Tue, 10 Aug 1999 07:04:15 -0400 (EDT) From: John Baldwin To: Cejka Rudolf Subject: Re: VESA module doesn't work with ATI Mach64 RagePro Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Aug-99 Cejka Rudolf wrote: > > Soren Schmidt wrote (1999/08/09): > >> It seems Kazutaka YOKOTA wrote: >> > There is a good possibility that the VESA BIOS extension for this card >> > is provided in a DOS TSR program and the VESA BIOS entry in the ROM >> > BIOS is just a stub. Such implementation is allowed in the VESA spec. > >> Actually its because the ATI chip reports the modes as non-VGA modes, >> which is correct (sortof), and our VESA code rejects those modeentries. > > Yes, thanks. Information reported by 0x4F01 function about any video > mode has set MODE_NON_VGA attribute indeed. And now I have found DOS TSR > program for VESA support... > > I hate VESA 2.0/3.0 specification :-( I hate ATI :-( > > Is there any good AGP graphics card with full BIOS support in hardware? Matrox G200 (and presumably G400). --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 5:15:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id B530B14D6C for ; Tue, 10 Aug 1999 05:15:29 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.9.3/8.9.3) with ESMTP id PAA09440; Tue, 10 Aug 1999 15:12:02 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 4A4F3CA; Tue, 10 Aug 1999 15:12:16 +0300 (EEST) Date: Tue, 10 Aug 1999 15:12:16 +0300 From: Vallo Kallaste To: John Baldwin Cc: Cejka Rudolf , freebsd-current@FreeBSD.ORG Subject: Re: VESA module doesn't work with ATI Mach64 RagePro Message-ID: <19990810151216.A4377@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <19990810083749.A55581@dcse.fee.vutbr.cz> <199908101105.HAA14356@smtp2.erols.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199908101105.HAA14356@smtp2.erols.com>; from John Baldwin on Tue, Aug 10, 1999 at 07:04:15AM -0400 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 10, 1999 at 07:04:15AM -0400, John Baldwin wrote: > > I hate VESA 2.0/3.0 specification :-( I hate ATI :-( > > > > Is there any good AGP graphics card with full BIOS support in hardware? > > Matrox G200 (and presumably G400). Now I'm set. I buy the G400, nothing else. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 5:35:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 999F3153C3; Tue, 10 Aug 1999 05:35:14 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 458CE1C1E; Tue, 10 Aug 1999 20:32:39 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "Cameron Grant" Cc: multimedia@freebsd.org, current@freebsd.org Subject: Re: it's time... In-reply-to: Your message of "Sun, 08 Aug 1999 02:23:59 +0100." <000901bee13c$b1831dc0$0304020a@rings> Date: Tue, 10 Aug 1999 20:32:39 +0800 From: Peter Wemm Message-Id: <19990810123239.458CE1C1E@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Cameron Grant" wrote: > to let newpcm out of the cage so you can all get your grubby little hands on > it. > > http://www.vilnya.demon.co.uk/newpcm+dfrpnp-19990807.diff.gz > > this is a patch against a recent -current. if you have a pci or isapnp > soundcard, you should have pnp0 and pcm0 in your kernel config as > appropriate. isapnp cards should not need any pnp lines in kernel.conf. > > the list of supported cards is as for luigi's driver, with the addition of a > couple more mss-clones, and trident 4dwave. there is a part done aureal > vortex driver which is as yet nonfunctional. mmap() is supported but not > well tested. format conversions are supported. the code seems to be > stable. > > please test it and email me success and failure reports. > > - cameron You're missing a bit of the patch I sent you to fix some resource problems caused by excessive cut/paste in Doug's code. Also, I implemented a proper (but still a hack) resource printer so you see all ranges. Before: pcm0: at port 0x220-0x22f,0x530-0x537 irq 5 drq 0,1 on isa0 After: pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,\ 0x370-0x371 irq 5 drq 0,1 on isa0 This still needs more work to handle line wraps etc. Matthew Dodd did some work in this area for the EISA code which should be able to be used. Patch appended. I don't think it's too critical since ISA_NPORT_IVARS is the largest range, but the lower layers might end up trying to allocate on rids that the upper layers can't handle. Cheers, -Peter diff -ru3 --exclude=CVS /home/peter/merge/isa/isa_common.c ./isa/isa_common.c --- /home/peter/merge/isa/isa_common.c Tue Aug 10 20:17:51 1999 +++ ./isa/isa_common.c Sat Aug 7 21:20:04 1999 @@ -270,12 +270,12 @@ { device_t dev = device_get_parent(child); int success, i; - struct resource *res[ISA_NPORT]; + struct resource *res[ISA_NIRQ]; /* * First clear out any existing resource definitions. */ - for (i = 0; i < ISA_NPORT; i++) { + for (i = 0; i < ISA_NIRQ; i++) { ISA_DELETE_RESOURCE(dev, child, SYS_RES_IRQ, i); res[i] = NULL; } @@ -300,7 +300,7 @@ } /* - * If we didn't find a place for port range i, then + * If we didn't find a place for irq range i, then * give up now. */ if (!res[i]) { @@ -309,7 +309,7 @@ } } - for (i = 0; i < ISA_NPORT; i++) { + for (i = 0; i < ISA_NIRQ; i++) { if (res[i]) bus_release_resource(child, SYS_RES_IRQ, i, res[i]); @@ -330,12 +330,12 @@ { device_t dev = device_get_parent(child); int success, i; - struct resource *res[ISA_NPORT]; + struct resource *res[ISA_NDRQ]; /* * First clear out any existing resource definitions. */ - for (i = 0; i < ISA_NPORT; i++) { + for (i = 0; i < ISA_NDRQ; i++) { ISA_DELETE_RESOURCE(dev, child, SYS_RES_DRQ, i); res[i] = NULL; } @@ -360,7 +360,7 @@ } /* - * If we didn't find a place for port range i, then + * If we didn't find a place for drq range i, then * give up now. */ if (!res[i]) { @@ -369,7 +369,7 @@ } } - for (i = 0; i < ISA_NPORT; i++) { + for (i = 0; i < ISA_NDRQ; i++) { if (res[i]) bus_release_resource(child, SYS_RES_DRQ, i, res[i]); @@ -507,26 +507,27 @@ isa_print_resources(struct resource_list *rl, const char *name, int type, const char *format) { - struct resource_list_entry *rle0 = resource_list_find(rl, type, 0); - struct resource_list_entry *rle1 = resource_list_find(rl, type, 1); + struct resource_list_entry *rle; + int printed; + int i; - if (rle0 || rle1) { - printf(" %s ", name); - if (rle0) { - printf(format, rle0->start); - if (rle0->count > 1) { - printf("-"); - printf(format, rle0->start + rle0->count - 1); - } - } - if (rle1) { - if (rle0) + printed = 0; + for (i = 0; i < 16; i++) { /* arbitary limit of 16 for now */ + rle = resource_list_find(rl, type, i); + if (rle) { + if (printed == 0) + printf(" %s ", name); + else if (printed > 0) printf(","); - printf(format, rle1->start); - if (rle1->count > 1) { + printed++; + printf(format, rle->start); + if (rle->count > 1) { printf("-"); - printf(format, rle1->start + rle1->count - 1); + printf(format, rle->start + rle->count - 1); } + } else if (i > 3) { + /* check the first few regardless */ + break; } } } @@ -772,7 +773,7 @@ if (type == SYS_RES_IRQ && rid >= ISA_NIRQ) return EINVAL; if (type == SYS_RES_DRQ && rid >= ISA_NDRQ) - return EINVAL; + return EINVAL; resource_list_add(rl, type, rid, start, start + count - 1, count); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 6:29:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from beelzebubba.sysabend.org (beelzebubba.sysabend.org [209.201.74.6]) by hub.freebsd.org (Postfix) with ESMTP id 67479153E2; Tue, 10 Aug 1999 06:29:19 -0700 (PDT) (envelope-from ragnar@sysabend.org) Received: by beelzebubba.sysabend.org (Postfix, from userid 1004) id BE3E341B7; Tue, 10 Aug 1999 09:26:15 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by beelzebubba.sysabend.org (Postfix) with SMTP id 6628D9BA6; Tue, 10 Aug 1999 09:26:15 -0400 (EDT) Date: Tue, 10 Aug 1999 09:26:15 -0400 (EDT) From: Jamie Bowden To: Alex Zepeda Cc: "Brian F. Feldman" , current , multimedia@FreeBSD.org Subject: Re: it's time... In-Reply-To: Message-ID: X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Aug 1999, Alex Zepeda wrote: :* an rc.audio or rc.multimedia (this could perhaps contain some bt484 :related things). : :But if it goes into "the" rc.conf, that would mean that whenever it runs :at shutdown, it edits rc.conf; this isn't IMO a real great idea. :Anything automated (even sysinstall) editing rc.conf in any way shape or :form makes me leery because it's so much more error prone. Why not create such a file, and update it whenever a change is made? The settings are always in whatever state you last set them to, no matter when it was, and you don't have to race shutdown. Jamie Bowden -- If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 8: 6:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 3D63F15013 for ; Tue, 10 Aug 1999 08:06:11 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn6.imasy.or.jp [202.227.24.198]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id AAA01219; Wed, 11 Aug 1999 00:04:44 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199908101504.AAA01219@tasogare.imasy.or.jp> To: iwasaki@jp.freebsd.org Cc: plm@xs4all.nl, freebsd-current@FreeBSD.ORG Subject: Re: recent apm changes In-Reply-To: Your message of "Tue, 10 Aug 1999 10:29:33 +0900" <199908100125.KAA19675@tasogare.imasy.or.jp> References: <199908100125.KAA19675@tasogare.imasy.or.jp> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 11 Aug 1999 00:08:29 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 189 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Another possibility is *delay mechanism* on suspend (and standby). > AFAIK, Linux, NetBSD and PAO has this but CURRENT. I'll make patch > tonight based on PAO APM code. Please try this patch. If it still fails, it's worth to try increasing APM_SUSPEND_DELAY, something like: #define APM_SUSPEND_DELAY 3 plm> or with the suspend button or through the BIOS timer), the led starts Oh, do you have suspend button on your box? Cool. On my poor experience, suspeding by hot-keys easier to success than by zzz(8). BTW, have you tried apmd too? Index: apm.c =================================================================== RCS file: /home/ncvs/src/sys/i386/apm/apm.c,v retrieving revision 1.98 diff -u -r1.98 apm.c --- apm.c 1999/08/02 18:46:34 1.98 +++ apm.c 1999/08/10 14:05:43 @@ -63,8 +63,10 @@ int initialized, active, bios_busy; int always_halt_cpu, slow_idle_cpu; int disabled, disengaged; + int standby_countdown, suspend_countdown; u_int minorversion, majorversion; u_int intversion, connectmode; + u_int standbys, suspends; struct bios_args bios; struct apmhook sc_suspend; struct apmhook sc_resume; @@ -431,7 +433,68 @@ static u_int apm_op_inprog = 0; +/* This is no good :( This should be SYSCTLized. */ +#ifndef APM_STANDBY_DELAY +#define APM_STANDBY_DELAY 1 +#endif + +#ifndef APM_SUSPEND_DELAY +#define APM_SUSPEND_DELAY 1 +#endif + static void +apm_do_suspend(void) +{ + struct apm_softc *sc = &apm_softc; + int error; + + if (!sc) + return; + + apm_op_inprog = 0; + sc->suspends = sc->suspend_countdown = 0; + + if (sc->initialized) { + error = DEVICE_SUSPEND(root_bus); + /* + * XXX Shouldn't ignore the error like this, but should + * instead fix the newbus code. Until that happens, + * I'm doing this to get suspend working again. + */ + if (error) + printf("DEVICE_SUSPEND error %d, ignored\n", error); + apm_execute_hook(hook[APM_HOOK_SUSPEND]); + if (apm_suspend_system(PMST_SUSPEND) == 0) + apm_processevent(); + else + /* Failure, 'resume' the system again */ + apm_execute_hook(hook[APM_HOOK_RESUME]); + } +} + +static void +apm_do_standby(void) +{ + struct apm_softc *sc = &apm_softc; + + if (!sc) + return; + + apm_op_inprog = 0; + sc->standbys = sc->standby_countdown = 0; + + if (sc->initialized) { + /* + * As far as standby, we don't need to execute + * all of suspend hooks. + */ + apm_default_suspend(&apm_softc); + if (apm_suspend_system(PMST_STANDBY) == 0) + apm_processevent(); + } +} + +static void apm_lastreq_notify(void) { struct apm_softc *sc = &apm_softc; @@ -478,29 +541,27 @@ apm_suspend(int state) { struct apm_softc *sc = &apm_softc; - int error; - if (!sc) + switch (state) { + case PMST_SUSPEND: + if (sc->suspends) + return; + sc->suspends++; + sc->suspend_countdown = APM_SUSPEND_DELAY; + break; + case PMST_STANDBY: + if (sc->standbys) + return; + sc->standbys++; + sc->standby_countdown = APM_STANDBY_DELAY; + break; + default: + printf("apm_suspend: Unknown Suspend state 0x%x\n", state); return; - - apm_op_inprog = 0; - - if (sc->initialized) { - error = DEVICE_SUSPEND(root_bus); - /* - * XXX Shouldn't ignore the error like this, but should - * instead fix the newbus code. Until that happens, - * I'm doing this to get suspend working again. - */ - if (error) - printf("DEVICE_SUSPEND error %d, ignored\n", error); - apm_execute_hook(hook[APM_HOOK_SUSPEND]); - if (apm_suspend_system(state) == 0) - apm_processevent(); - else - /* Failure, 'resume' the system again */ - apm_execute_hook(hook[APM_HOOK_RESUME]); } + + apm_op_inprog++; + apm_lastreq_notify(); } void @@ -625,6 +686,12 @@ if (apm_op_inprog) apm_lastreq_notify(); + if (sc->standbys && sc->standby_countdown-- <= 0) + apm_do_standby(); + + if (sc->suspends && sc->suspend_countdown-- <= 0) + apm_do_suspend(); + if (!sc->bios_busy) apm_processevent(); @@ -826,7 +893,7 @@ if (apm_op_inprog == 0) { apm_op_inprog++; if (apm_record_event(sc, apm_event)) { - apm_suspend(PMST_SUSPEND); + apm_do_suspend(); } } return; /* XXX skip the rest */ @@ -835,12 +902,12 @@ if (apm_op_inprog == 0) { apm_op_inprog++; if (apm_record_event(sc, apm_event)) { - apm_suspend(PMST_SUSPEND); + apm_do_suspend(); } } return; /* XXX skip the rest */ OPMEV_DEBUGMESSAGE(PMEV_CRITSUSPEND); - apm_suspend(PMST_SUSPEND); + apm_do_suspend(); break; OPMEV_DEBUGMESSAGE(PMEV_NORMRESUME); apm_record_event(sc, apm_event); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 8:16:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id 3457C15439 for ; Tue, 10 Aug 1999 08:16:45 -0700 (PDT) (envelope-from erik@habatech.no) Received: from bsdbox.habatech.no ([62.92.133.3]) by post.bgnett.no (8.8.8/8.8.8) with SMTP id RAA08228 for ; Tue, 10 Aug 1999 17:15:25 +0200 (CEST) (envelope-from erik@habatech.no) From: "Erik H. Bakke" To: freebsd-current@freebsd.org Subject: Improved support for NE2000 compatible ISA-PnP cards Date: Tue, 10 Aug 1999 17:16:30 +0200 X-Mailer: KMail [version 0.7.9] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99081017213200.00789@bsdbox.habatech.no> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following has also been submitted in the form of a PR. I am posting the information here because I think this will be of interest to others out there as well. If this is not the correct way to do it, or the correct place, please guide me to the correct path, as this is my first submission (But probably not the last) Here is the case: FreeBSD-current does not support all NE-2000 compatible network cards, nor will it probably ever do, but with the patch included below, at least some cards will be supported. The following will add support for a card, which under Windows platforms is recognized as a CNet NE2000 compatible. Quite simple patch... ****** START OF INCLUDED TEXT ****** *** if_ed.c Tue Jul 6 21:22:44 1999 --- if_ed.bak Tue Aug 10 16:36:03 1999 *************** *** 3443,3448 **** --- 3443,3449 ---- static pnpid_t edpnp_ids[] = { { 0xd680d041, "NE2000"}, + { 0x0090252a, "CNet NE2000 Compatible"}, { 0 } }; ****** END OF INCLUDED TEXT ****** --- Erik H. Bakke Habatech AS erik@habatech.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 8:45:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id DA600153F3 for ; Tue, 10 Aug 1999 08:45:23 -0700 (PDT) (envelope-from steveo@iol.ie) Received: from pooh.elsevier.nl (localhost [127.0.0.1]) by pooh.elsevier.nl (8.9.3/8.9.3) with ESMTP id QAA45756; Tue, 10 Aug 1999 16:32:38 +0100 (IST) (envelope-from steveo@iol.ie) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199908101504.AAA01219@tasogare.imasy.or.jp> Date: Tue, 10 Aug 1999 16:32:37 +0100 (IST) From: "Steve O'Hara-Smith" To: Mitsuru IWASAKI Subject: Re: recent apm changes Cc: freebsd-current@FreeBSD.ORG, plm@xs4all.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Aug-99 Mitsuru IWASAKI wrote: > Oh, do you have suspend button on your box? Cool. > On my poor experience, suspeding by hot-keys easier to > success than by zzz(8). On this point I can report the oppposite experience, on my machine (a no name special) the trackpad tends to lock up if touched between power on and resume finishing. The best indicator of safety is apm -z returning, if I use the button I have to guess. ---------------------------------- E-Mail: Steve O'Hara-Smith Date: 10-Aug-99 Time: 16:29:54 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 10:17:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.tucows.com (mail.tucows.com [208.229.216.23]) by hub.freebsd.org (Postfix) with ESMTP id 34E4514E87 for ; Tue, 10 Aug 1999 10:17:15 -0700 (PDT) (envelope-from arthur@tucows.com) Received: from Arthur.Linuxberg (starwars.linuxberg.org [208.229.216.41]) by mail.tucows.com (8.9.3/8.9.1) with ESMTP id NAA04613 for ; Tue, 10 Aug 1999 13:16:11 -0400 Received: from localhost (arthur@localhost) by Arthur.Linuxberg (8.9.3/8.9.3) with ESMTP id NAA00288 for ; Tue, 10 Aug 1999 13:15:49 -0400 (EDT) X-Authentication-Warning: Arthur.Linuxberg: arthur owned process doing -bs Date: Tue, 10 Aug 1999 13:15:49 -0400 (EDT) From: "Arthur H. Johnson II" X-Sender: arthur@arthur.linuxberg To: freebsd-current@FreeBSD.ORG Subject: Upgrading the system. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When you go into upgrade under /stand/sysinstall, and select ftp and use current.freebsd.org as the site, does it take the most recent snapshot? Arthur H. Johnson II arthur@tucows.com Linuxberg Manager Tucows.com Inc. http://www.linuxberg.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 10:21:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id A7E681542C for ; Tue, 10 Aug 1999 10:21:17 -0700 (PDT) (envelope-from jrs@enteract.com) Received: (qmail 84478 invoked from network); 10 Aug 1999 17:21:18 -0000 Received: from shell-1.enteract.com (jrs@207.229.143.40) by pop3-3.enteract.com with SMTP; 10 Aug 1999 17:21:18 -0000 Date: Tue, 10 Aug 1999 12:21:18 -0500 (CDT) From: John Sconiers To: "Arthur H. Johnson II" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Upgrading the system. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When you go into upgrade under /stand/sysinstall, and select ftp and use > current.freebsd.org as the site, does it take the most recent snapshot? no you have to set that option in the options screen. JOHN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 11:21: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id ACCE814E0A; Tue, 10 Aug 1999 11:21:02 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA17315; Tue, 10 Aug 1999 12:20:44 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA13330; Tue, 10 Aug 1999 12:20:50 -0600 (MDT) Message-Id: <199908101820.MAA13330@harmony.village.org> To: Peter Wemm Subject: Re: it's time... Cc: "Cameron Grant" , multimedia@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Tue, 10 Aug 1999 20:32:39 +0800." <19990810123239.458CE1C1E@overcee.netplex.com.au> References: <19990810123239.458CE1C1E@overcee.netplex.com.au> Date: Tue, 10 Aug 1999 12:20:50 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990810123239.458CE1C1E@overcee.netplex.com.au> Peter Wemm writes: : This still needs more work to handle line wraps etc. Matthew Dodd did some : work in this area for the EISA code which should be able to be used. I'd be very careful of line wrapping probe messages. I have scripts that rely on them being on one line to get a list of irqs, etc. However, the whole issue of how probe messages should print, and how much is a religious war that I try to steer clear of... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 11:22:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9B9061536D for ; Tue, 10 Aug 1999 11:22:30 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA17329; Tue, 10 Aug 1999 12:22:19 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA13357; Tue, 10 Aug 1999 12:22:33 -0600 (MDT) Message-Id: <199908101822.MAA13357@harmony.village.org> To: Mitsuru IWASAKI Subject: Re: recent apm changes Cc: plm@xs4all.nl, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 11 Aug 1999 00:08:29 +0900." <199908101504.AAA01219@tasogare.imasy.or.jp> References: <199908101504.AAA01219@tasogare.imasy.or.jp> <199908100125.KAA19675@tasogare.imasy.or.jp> Date: Tue, 10 Aug 1999 12:22:32 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908101504.AAA01219@tasogare.imasy.or.jp> Mitsuru IWASAKI writes: : + error = DEVICE_SUSPEND(root_bus); : + /* : + * XXX Shouldn't ignore the error like this, but should : + * instead fix the newbus code. Until that happens, : + * I'm doing this to get suspend working again. : + */ : + if (error) : + printf("DEVICE_SUSPEND error %d, ignored\n", error); I think that it is now safe to make this warning an error... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 11:25:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (Postfix) with ESMTP id E54851506F for ; Tue, 10 Aug 1999 11:25:44 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from localhost (localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id EAA56066 for ; Wed, 11 Aug 1999 04:24:55 +1000 (EST) (envelope-from andyf@speednet.com.au) Date: Wed, 11 Aug 1999 04:24:55 +1000 (EST) From: Andy Farkas X-Sender: andyf@localhost To: freebsd-current@FreeBSD.ORG Subject: installing hack(6) overwrites /var/games/hackdir/record file! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Perhaps this should be a PR... Seeing as how we are recently being amused by fortune(6) quotes, I thought I'd mention an acronymn that hasn't been used recently: POLA Can anyone explain why every time I upgrade world, my hard earned 'record' file whilst playing hack(6) gets overwritten by /dev/null, and also all the user 'bones' and 'save' files rm'd? If the interface to these files changes, surely the game should recognise it? I propose the following patch to src/games/hack: $ diff -u Makefile.orig Makefile --- Makefile.orig Wed Aug 11 04:16:06 1999 +++ Makefile Wed Aug 11 04:16:20 1999 @@ -31,14 +31,14 @@ beforeinstall: ${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m ${NOBINMODE} /dev/null \ ${DESTDIR}/var/games/hackdir/perm +.if !exists(${DESTDIR}/var/games/hackdir/record) ${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m 460 /dev/null \ ${DESTDIR}/var/games/hackdir/record +.endif ${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m 440 ${.CURDIR}/rumors \ ${DESTDIR}/var/games/hackdir/rumors ${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m ${NOBINMODE} \ ${.CURDIR}/help ${.CURDIR}/hh ${.CURDIR}/data \ ${DESTDIR}/var/games/hackdir - rm -f ${DESTDIR}/var/games/hackdir/bones* \ - ${DESTDIR}/var/games/hackdir/save/* .include -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 12:38:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 64EE515460 for ; Tue, 10 Aug 1999 12:38:25 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id MAA75060 for ; Tue, 10 Aug 1999 12:38:02 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 10 Aug 1999 12:38:02 -0700 (PDT) From: Doug White To: freebsd-current@FreeBSD.ORG Subject: Re: wd0: interrupt timeout (status 58 error 1) In-Reply-To: <199908100105.DAA08856@dorifer.heim3.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Aug 1999, Oliver Fromme wrote: > Doug wrote in list.freebsd-current: > > On Mon, 9 Aug 1999, Brian McGroarty wrote: > > > > > FWIW - I enabled APM over the weekend, configuring drives to > > > spin down when not used for a good period of time. I get the > > > message you list below, alternately with status 50 and 58, any > > > time a drive needs to spin up. > > > > Thanks for the response. FWIW I have no apm enabled and these > > drives don't have a chance to spin down since they're always busy when > > under load. > > Do those drives happen to be IBM DeskStar drives? > They spin down automatically when they have not been turned > off for about a week, in order to clean the heads. > It's a feature. You've got to be kidding. That makes them totally useless for server operation -- at some random time every week, down goes your server for a few minutes. :( Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 12:54: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 0D7571543B for ; Tue, 10 Aug 1999 12:53:55 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id PAA00866; Tue, 10 Aug 1999 15:52:06 -0400 (EDT) (envelope-from wollman) Date: Tue, 10 Aug 1999 15:52:06 -0400 (EDT) From: Garrett Wollman Message-Id: <199908101952.PAA00866@khavrinen.lcs.mit.edu> To: Doug White Cc: freebsd-current@FreeBSD.ORG Subject: Re: wd0: interrupt timeout (status 58 error 1) In-Reply-To: References: <199908100105.DAA08856@dorifer.heim3.tu-clausthal.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > You've got to be kidding. That makes them totally useless for server > operation -- at some random time every week, down goes your server for a > few minutes. :( Ye gets what ye pays for.... if you want a reliable server, use SCSI. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 13: 4:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 583D214EE5 for ; Tue, 10 Aug 1999 13:03:48 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA30178; Tue, 10 Aug 1999 22:01:16 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Garrett Wollman Cc: Doug White , freebsd-current@FreeBSD.ORG Subject: Re: wd0: interrupt timeout (status 58 error 1) In-reply-to: Your message of "Tue, 10 Aug 1999 15:52:06 EDT." <199908101952.PAA00866@khavrinen.lcs.mit.edu> Date: Tue, 10 Aug 1999 22:01:16 +0200 Message-ID: <30176.934315276@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908101952.PAA00866@khavrinen.lcs.mit.edu>, Garrett Wollman writes: >< said: > >> You've got to be kidding. That makes them totally useless for server >> operation -- at some random time every week, down goes your server for a >> few minutes. :( > >Ye gets what ye pays for.... if you want a reliable server, use SCSI. Fair to say in this case, IBM goes out of their way to explain that *DESK*star is NOT for servers. For a server you want ULTRAstar disks. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 14:28: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 1AE2A154B5 for ; Tue, 10 Aug 1999 14:28:03 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id XAA55824; Tue, 10 Aug 1999 23:27:42 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199908102127.XAA55824@freebsd.dk> Subject: Re: wd0: interrupt timeout (status 58 error 1) In-Reply-To: from Doug White at "Aug 10, 1999 12:38: 2 pm" To: dwhite@resnet.uoregon.edu (Doug White) Date: Tue, 10 Aug 1999 23:27:42 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Doug White wrote: > > > > > > > FWIW - I enabled APM over the weekend, configuring drives to > > > > spin down when not used for a good period of time. I get the > > > > message you list below, alternately with status 50 and 58, any > > > > time a drive needs to spin up. > > > > > > Thanks for the response. FWIW I have no apm enabled and these > > > drives don't have a chance to spin down since they're always busy when > > > under load. > > > > Do those drives happen to be IBM DeskStar drives? > > They spin down automatically when they have not been turned > > off for about a week, in order to clean the heads. > > It's a feature. > > You've got to be kidding. That makes them totally useless for server > operation -- at some random time every week, down goes your server for a > few minutes. :( That can't be true, at least not for the IBM DeskStars I own, I've NEVER EVER seen them do that, one proof should be: 11:22PM up 105 days, 4:18, 1 user, load averages: 1.06, 0.94, 0.91 dmesg snippet: wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S And none of the other machines I have with semilar or newer IBM's have ever done this, in fact I've yet to see one of them fail in any way.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 14:37:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from maildns2.fsbdial.co.uk (s24.athenenet.co.uk [195.89.137.30]) by hub.freebsd.org (Postfix) with ESMTP id DE24614D41 for ; Tue, 10 Aug 1999 14:37:21 -0700 (PDT) (envelope-from frankrj@netscape.net) Received: from [212.1.146.32] by maildns2.freenet.co.uk (NTMail 4.30.0012/NT0619.00.9914eb79) with ESMTP id nbommaaa for ; Tue, 10 Aug 1999 22:35:54 +0100 Message-ID: <37B09C02.658DA7F4@netscape.net> Date: Tue, 10 Aug 1999 22:39:14 +0100 From: Francis Jordan X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: wd0: interrupt timeout (status 58 error 1) References: <199908102127.XAA55824@freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG An unrelated question: I get the following in my dmesg: /kernel: ata0: master: setting up UDMA2 mode on PIIX4 chip OK /kernel: ad0: ATA-4 disk at ata0 as master /kernel: ad0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S /kernel: ad0: piomode=4, dmamode=2, udmamode=2 /kernel: ad0: 16 secs/int, 0 depth queue, DMA mode /kernel: acd0: CDROM drive at ata1 as master /kernel: acd0: drive speed 4134KB/sec, 128KB cache /kernel: acd0: supported read types: CD-R, CD-RW, CD-DA /kernel: acd0: Audio: play, 256 volume levels /kernel: acd0: Mechanism: ejectable tray /kernel: acd0: Medium: CD-ROM unknown medium, unlocked /kernel: ata_command: timeout waiting for interrupt ----------------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ It happens everytime I boot. What does the last line mean, and why does it appear? BTW, there's an audio CD in the CD-ROM drive, so it's not exactly "unknown" medium. What can I do to help fix this? Frank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 14:44:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3BE3714DD4 for ; Tue, 10 Aug 1999 14:44:55 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id XAA55868; Tue, 10 Aug 1999 23:44:35 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199908102144.XAA55868@freebsd.dk> Subject: Re: wd0: interrupt timeout (status 58 error 1) In-Reply-To: <37B09C02.658DA7F4@netscape.net> from Francis Jordan at "Aug 10, 1999 10:39:14 pm" To: frankrj@netscape.net (Francis Jordan) Date: Tue, 10 Aug 1999 23:44:35 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Francis Jordan wrote: > /kernel: acd0: CDROM drive at ata1 as master > /kernel: acd0: drive speed 4134KB/sec, 128KB cache > /kernel: acd0: supported read types: CD-R, CD-RW, CD-DA > /kernel: acd0: Audio: play, 256 volume levels > /kernel: acd0: Mechanism: ejectable tray > /kernel: acd0: Medium: CD-ROM unknown medium, unlocked > /kernel: ata_command: timeout waiting for interrupt > > ----------------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > It happens everytime I boot. What does the last line mean, and why does > it appear? BTW, there's an audio CD in the CD-ROM drive, so it's not > exactly "unknown" medium. What can I do to help fix this? I assume you only have those two devices on the ide channels right ?? Then the problem is that the CDROM drive doesn't respond proberly to a command, in fact it doesn't respond at all, there is no interrupt. Have you tried another CDROM drive ?? This smells alot like substandard hardware. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 14:57:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from bouvreuil.cybercable.fr (bouvreuil.cybercable.fr [212.198.3.12]) by hub.freebsd.org (Postfix) with SMTP id 489D914BE4 for ; Tue, 10 Aug 1999 14:57:11 -0700 (PDT) (envelope-from herbelot@cybercable.fr) Received: (qmail 5994 invoked from network); 10 Aug 1999 21:56:15 -0000 Received: from d022.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.22]) (envelope-sender ) by bouvreuil.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 10 Aug 1999 21:56:15 -0000 Message-ID: <37B09FFF.C6CC6BD5@cybercable.fr> Date: Tue, 10 Aug 1999 23:56:15 +0200 From: Thierry Herbelot Organization: Les barbus =?iso-8859-1?Q?associ=E9s?=, Paris, France X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: Doug White , freebsd-current@FreeBSD.ORG Subject: Re: wd0: interrupt timeout (status 58 error 1) References: <199908102127.XAA55824@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > [SNIP] > > That can't be true, at least not for the IBM DeskStars I own, I've > NEVER EVER seen them do that, one proof should be: same here wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , DMA, 32-bit, multi-block-16 wd1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-16 wd2: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S This is on my (very lightly loaded) home NFS server TfH (trying to upgrade one BP6 to 4.0) > > 11:22PM up 105 days, 4:18, 1 user, load averages: 1.06, 0.94, 0.91 > > dmesg snippet: > wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 > wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S > > And none of the other machines I have with semilar or newer IBM's > have ever done this, in fact I've yet to see one of them fail in > any way.. > > -Søren > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 14:58:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2A80514D4C for ; Tue, 10 Aug 1999 14:58:15 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id XAA55903; Tue, 10 Aug 1999 23:57:57 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199908102157.XAA55903@freebsd.dk> Subject: Re: wd0: interrupt timeout (status 58 error 1) In-Reply-To: <37B09FFF.C6CC6BD5@cybercable.fr> from Thierry Herbelot at "Aug 10, 1999 11:56:15 pm" To: herbelot@cybercable.fr (Thierry Herbelot) Date: Tue, 10 Aug 1999 23:57:57 +0200 (CEST) Cc: dwhite@resnet.uoregon.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Thierry Herbelot wrote: > Soren Schmidt wrote: > > > [SNIP] > > > > That can't be true, at least not for the IBM DeskStars I own, I've > > NEVER EVER seen them do that, one proof should be: > > same here > > wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 > wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S > wdc0: unit 1 (wd1): , DMA, 32-bit, multi-block-16 > wd1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S > wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa > wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-16 > wd2: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S > > TfH (trying to upgrade one BP6 to 4.0) Have you tried putting disks on the UDMA66 channel ?? I think it should work in upto WDMA mode now with the ata driver... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 16:22:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 106A514E35; Tue, 10 Aug 1999 16:18:17 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id AAA59247; Wed, 11 Aug 1999 00:14:44 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id PAA81171; Tue, 10 Aug 1999 15:53:01 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Date: Tue, 10 Aug 1999 15:53:01 +0100 From: Nik Clayton To: doc@freebsd.org, current@freebsd.org, committers@freebsd.org Cc: jdp@freebsd.org Subject: HEADS UP: doc/ tree breakage on Sunday 15th August Message-ID: <19990810155301.A77293@kilt.nothing-going-on.org> Reply-To: nik@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Heads up, [ cc: to -doc, -current, -committers, reply-to: nik ] On Sunday 15th August the doc/ tree will break. John Polstra will be performing surgery on the CVS repository[1], and when he's completed that I will be going in to fix up the build system infrastructure (all the Makefiles, primarily). If things go smoothly, the doc/ tree should be back and working by late Sunday evening (BST). If things go badly then it will be back and working by the end of Monday evening (BST). Prior to making these changes, John will announce a freeze on the doc/ repository. While this is going on, the doc/ tree will fail to build. This will impact on: * The web site, which uses the doc/ tree to build the FAQ, Handbook, and tutorials. On Thursday or Friday I will be altering the "webbuild" script so that it uses archived copies of the doc/ tree when rebuilding the web site. The site will therefore not be affected, however, any commits made to the FAQ, Handbook, or tutorials after I make the change will not show up on the site. The rest of the web site is unaffected. This will also affect our web site mirrors. I have been e-mailing the contacts for the mirrors to advise them, but a lot of the messages have been bouncing. Be prepared for some of the web site mirrors to either be out of date or broken for 24 hours or so. * "make release". Make sure you build with "NODOC=YES", otherwise the release build will fail. Jordan might want to make this the default -- although for what will hopefully amount to less than 24 hours of breakage it's probably not worthwhile. * Obviously, any -doc committers should get any commits they want in before the work by Saturday afternoon at the latest. So you know, there's a lot of work lined up in the queue ready to happen when this surgery is complete (I've been putting it off, because I didn't want to load the repository up with new files and then be moving them all over the place) including: * French translations of the FAQ and Handbook * The FAQ in DocBook * The beginnings of an infrastructure for http://docs.freebsd.org/ N [1] The nature of this surgery has been discussed extensively on the -doc mailing list, so I won't repeat that here. -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. - Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 17:37:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from maildns2.fsbdial.co.uk (s24.athenenet.co.uk [195.89.137.30]) by hub.freebsd.org (Postfix) with ESMTP id 1E2D5154EA for ; Tue, 10 Aug 1999 17:37:27 -0700 (PDT) (envelope-from frankrj@netscape.net) Received: from [212.1.145.161] by maildns2.freenet.co.uk (NTMail 4.30.0012/NT0619.00.9914eb79) with ESMTP id pkymmaaa for ; Wed, 11 Aug 1999 01:36:23 +0100 Message-ID: <37B0C652.BB7ABE6B@netscape.net> Date: Wed, 11 Aug 1999 01:39:46 +0100 From: Francis Jordan X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: wd0: interrupt timeout (status 58 error 1) References: <199908102144.XAA55868@freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > > It seems Francis Jordan wrote: > > /kernel: acd0: CDROM drive at ata1 as master > > /kernel: acd0: drive speed 4134KB/sec, 128KB cache > > /kernel: acd0: supported read types: CD-R, CD-RW, CD-DA > > /kernel: acd0: Audio: play, 256 volume levels > > /kernel: acd0: Mechanism: ejectable tray > > /kernel: acd0: Medium: CD-ROM unknown medium, unlocked > > /kernel: ata_command: timeout waiting for interrupt > > > > ----------------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > It happens everytime I boot. What does the last line mean, and why does > > it appear? BTW, there's an audio CD in the CD-ROM drive, so it's not > > exactly "unknown" medium. What can I do to help fix this? > > I assume you only have those two devices on the ide channels right ?? > Then the problem is that the CDROM drive doesn't respond proberly > to a command, in fact it doesn't respond at all, there is no interrupt. > Have you tried another CDROM drive ?? This smells alot like substandard > hardware. Yes, HDD on the primary, CD-ROM on the secondary controller. This is a notebook I'm talking about, so I haven't tried any other CD-ROM drives. If it doesn't respond at all, then how do you get all the other information, such as supported read types, speed, etc? Perhaps there is some other way of making this particular CD-ROM drive generate an interrupt? Of course, it's just a minor annoyance (and otherwise I'm very pleased with the driver's performance - many thanks to SOS), but if the new ATA driver were to eventually replace the old one, it's not a bad idea to try and get rid of as many silly error messages as possible. Is there just one standard that all ATAPI CD-ROM drives must comply with, or can there be variations? I apologize if this is a silly question. Frank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 18:12:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from web1001.mail.yahoo.com (web1001.mail.yahoo.com [128.11.23.91]) by hub.freebsd.org (Postfix) with SMTP id 2BFF0154D2 for ; Tue, 10 Aug 1999 18:12:20 -0700 (PDT) (envelope-from bvmcg@yahoo.com) Message-ID: <19990811010915.17486.rocketmail@web1001.mail.yahoo.com> Received: from [24.29.199.43] by web1001.mail.yahoo.com; Tue, 10 Aug 1999 18:09:15 PDT Date: Tue, 10 Aug 1999 18:09:15 -0700 (PDT) From: Brian McGroarty Reply-To: brian@pobox.com Subject: ATA - Trouble mounting secondary master To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In using the ATA driver, I'm unable to automatically mount a partition on a master drive on the secondary controller. fsck complains that device rwd2s1e isn't configured and exists. Immediately mounting by hand works perfectly. Compiling the kernel with wd instead of ata eliminates the problem. # ls -la /dev/*wd2s1e crw-r----- 1 root operator 3, 0x00020014 Aug 7 09:06 rwd2s1e brw-r----- 1 root operator 0, 0x00020014 Aug 7 09:06 wd2s1e # disklabel wd2 # /dev/rwd2c: type: ESDI disk: wd2s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 15 sectors/cylinder: 945 cylinders: 29872 sectors/unit: 28229040 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 28229040 0 unused 0 0 # (Cyl. 0 - 29871) e: 28229040 0 4.2BSD 0 0 0 # (Cyl. 0 - 29871) # grep wd2 /etc/fstab /dev/wd2s1e /home ufs rw 2 2 _____________________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 19:45:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc2.on.home.com (ha1.rdc2.on.home.com [24.9.0.15]) by hub.freebsd.org (Postfix) with ESMTP id 9B08314D06 for ; Tue, 10 Aug 1999 19:45:17 -0700 (PDT) (envelope-from street@iname.com) Received: from mired.eh.local ([24.66.100.55]) by mail.rdc2.on.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19990811024520.OZWZ12218.mail.rdc2.on.home.com@mired.eh.local>; Tue, 10 Aug 1999 19:45:20 -0700 Received: (from kws@localhost) by mired.eh.local (8.9.3/8.9.3) id WAA31436; Tue, 10 Aug 1999 22:45:20 -0400 (EDT) (envelope-from kws) To: freebsd-current@FreeBSD.ORG Cc: brian@pobox.com Subject: Re: ATA - Trouble mounting secondary master References: <19990811010915.17486.rocketmail@web1001.mail.yahoo.com> From: Kevin Street Date: 10 Aug 1999 22:45:19 -0400 In-Reply-To: Brian McGroarty's message of "Tue, 10 Aug 1999 18:09:15 -0700 (PDT)" Message-ID: <87wvv36nnk.fsf@mired.eh.local> Lines: 52 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "20 Minutes to Nikko" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian McGroarty writes: > In using the ATA driver, I'm unable to automatically mount a > partition on a master drive on the secondary controller. fsck > complains that device rwd2s1e isn't configured and exists. > Immediately mounting by hand works perfectly. Nice timing, I was about to send a message with a description of a similar (the same?) problem. The first access to any IDE disk (except the one I'm booting from - wd1) fails with 'device not configured'. This affects swapon for wd2s2b during the boot as well as the first mount for wd0 which happens to have only dos partitions on it. So the problem is not restricted to ufs partitions or to the secondary controller. Repeating the swapon or mount command works normally. I've been seeing this problem for about a month, but I've been away on vacation so am just beginning to look into it. I made changes to all my drives and put them in LBA mode at about the same time as I began seeing this, but I'm not sure if that is related. ata-pci0: at device 4.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ata0: master: setting up UDMA2 mode on PIIX4 chip OK ad0: ATA-4 disk at ata0 as master ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode ata0: slave: setting up UDMA2 mode on PIIX4 chip OK ad1: ATA-3 disk at ata0 as slave ad1: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 0 depth queue, DMA mode ata1: master: setting up UDMA2 mode on PIIX4 chip OK ad2: ATA-4 disk at ata1 as master ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=2 ad2: 16 secs/int, 0 depth queue, DMA mode acd0: CDROM drive at ata1 as slave acd0: drive speed 5515KB/sec, 256KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked -- Kevin Street street@iname.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 20: 5: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from web1002.mail.yahoo.com (web1002.mail.yahoo.com [128.11.23.92]) by hub.freebsd.org (Postfix) with SMTP id F360D14F3F for ; Tue, 10 Aug 1999 20:05:06 -0700 (PDT) (envelope-from bvmcg@yahoo.com) Message-ID: <19990811030509.3860.rocketmail@web1002.mail.yahoo.com> Received: from [24.29.199.43] by web1002.mail.yahoo.com; Tue, 10 Aug 1999 20:05:09 PDT Date: Tue, 10 Aug 1999 20:05:09 -0700 (PDT) From: Brian McGroarty Reply-To: brian@pobox.com Subject: Re: ATA - Trouble mounting secondary master To: Kevin Street , freebsd-current@FreeBSD.ORG Cc: brian@pobox.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Also of interest - I have a seperate access light for each of my drives, as they're in removable bays. I notice the access light for the secondary master remaining on after the kernel driver has done its scanning. The light goes off on this, the failed first access. I believe the light for the primary slave stays on as well, but goes off on the first access to the primary master (which does -not- fail). --- Kevin Street wrote: > Brian McGroarty writes: > > > In using the ATA driver, I'm unable to automatically mount a > > partition on a master drive on the secondary controller. > fsck > > complains that device rwd2s1e isn't configured and exists. > > Immediately mounting by hand works perfectly. > > Nice timing, I was about to send a message with a description > of a > similar (the same?) problem. The first access to any IDE disk > (except > the one I'm booting from - wd1) fails with 'device not > configured'. This > affects swapon for wd2s2b during the boot as well as the first > mount > for wd0 which happens to have only dos partitions on it. So > the > problem is not restricted to ufs partitions or to the > secondary > controller. > > Repeating the swapon or mount command works normally. > > I've been seeing this problem for about a month, but I've been > away on > vacation so am just beginning to look into it. I made changes > to all > my drives and put them in LBA mode at about the same time as I > began > seeing this, but I'm not sure if that is related. > > ata-pci0: at device 4.1 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > > ata0: master: setting up UDMA2 mode on PIIX4 chip OK > ad0: ATA-4 disk at ata0 as master > ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, > 512 B/S > ad0: piomode=4, dmamode=2, udmamode=2 > ad0: 16 secs/int, 0 depth queue, DMA mode > ata0: slave: setting up UDMA2 mode on PIIX4 chip OK > ad1: ATA-3 disk at ata0 as slave > ad1: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, > 512 B/S > ad1: piomode=4, dmamode=2, udmamode=2 > ad1: 16 secs/int, 0 depth queue, DMA mode > ata1: master: setting up UDMA2 mode on PIIX4 chip OK > ad2: ATA-4 disk at ata1 as master > ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, > 512 B/S > ad2: piomode=4, dmamode=2, udmamode=2 > ad2: 16 secs/int, 0 depth queue, DMA mode > acd0: CDROM drive at ata1 as slave > acd0: drive speed 5515KB/sec, 256KB cache > acd0: supported read types: CD-R, CD-RW, CD-DA > acd0: Audio: play, 256 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: CD-ROM 120mm data disc loaded, unlocked _____________________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 21:10:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 1C8D914DFE for ; Tue, 10 Aug 1999 21:10:06 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id GAA12393 for freebsd-current@FreeBSD.ORG; Wed, 11 Aug 1999 06:10:04 +0200 (CEST) (envelope-from olli) Date: Wed, 11 Aug 1999 06:10:04 +0200 (CEST) From: Oliver Fromme Message-Id: <199908110410.GAA12393@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: wd0: interrupt timeout (status 58 error 1) Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White wrote in list.freebsd-current: > On Tue, 10 Aug 1999, Oliver Fromme wrote: > > > > Do those drives happen to be IBM DeskStar drives? > > They spin down automatically when they have not been turned > > off for about a week, in order to clean the heads. > > It's a feature. > > You've got to be kidding. No, I'm serious, that behaviour is a fact, and it's documented. > That makes them totally useless for server > operation The IBM DeskStar series is for desktop use, not for Servers. (Apart from the fact that I wouldn't use IDE drives for real servers anyway.) > -- at some random time every week, down goes your server for a > few minutes. :( No, only a few seconds. If there doesn't happen to be a disk access in that time interval, you won't notice at all. Other- wise you'll get that log message from the driver. This is the background of that feature: The IBM DeskStar disks are specifically designed for at least one on/off cycle per day. The "landing zones" where the heads are parked consist of a special layer that cleans the heads. If the disk is not switched off for a long period, the disk enforces a short spin- down + spin-up to clean the disk heads periodically. All of this is explained in more detail in a white paper of IBM, I think it is available from IBM's site. IBM's server disks (UltraStar) are designed for much fewer on/off cycles (in fact IBM recommends that they should not be used in desktops that are switched off very often, e.g. for power-saving or noise-reduction). They don't have that cleaning layer (and they don't need it). That's one of the reasons why they're more expensive. Bottom line: For a server, buy server disks. If you use cheap IBM DeskStar disks in a server, you won't get 100% availability (rather 100% minus a few seconds per week). Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 22:33:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 37C2014D86 for ; Tue, 10 Aug 1999 22:33:15 -0700 (PDT) (envelope-from geoff@rucus.ru.ac.za) Received: (qmail 66419 invoked by uid 268); 11 Aug 1999 05:31:47 -0000 Message-ID: <19990811053147.66418.qmail@rucus.ru.ac.za> Subject: Re: ATA - Trouble mounting secondary master In-Reply-To: <19990811010915.17486.rocketmail@web1001.mail.yahoo.com> from Brian McGroarty at "Aug 10, 1999 06:09:15 pm" To: brian@pobox.com Date: Wed, 11 Aug 1999 07:31:47 +0200 (SAST) Cc: sos@freebsd.org, current@freebsd.org Reply-To: "Geoff Rehmet" From: "Geoff Rehmet" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian McGroarty writes : > In using the ATA driver, I'm unable to automatically mount a > partition on a master drive on the secondary controller. fsck > complains that device rwd2s1e isn't configured and exists. > Immediately mounting by hand works perfectly. > > Compiling the kernel with wd instead of ata eliminates the > problem. Hmm, I had exactly the same problem, although it manifested itself with a secondary master or slave. It went away a few weeks ago, and I was never able to make any sensible progress in tracking the problem down. It appears to occur when the partition table is read. Something times out, and the real partition table values are not read. The second time you read the disk, everything works. For a while, I had the line disklabel /dev/rad2s1a 2>&1 > /dev/null in my rc file :-). This was enough to kick the disk past the initial problem. (Not the right thing to do, but it allowed me to reboot without hitting single user mode.) Geoff. -- Geoff Rehmet, The Internet Solution geoffr@is.co.za; geoff@rucus.ru.ac.za; csgr@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 10 23:54:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7519014DE9; Tue, 10 Aug 1999 23:54:27 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA56765; Wed, 11 Aug 1999 08:53:24 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199908110653.IAA56765@freebsd.dk> Subject: Re: ATA - Trouble mounting secondary master In-Reply-To: <19990811053147.66418.qmail@rucus.ru.ac.za> from Geoff Rehmet at "Aug 11, 1999 7:31:47 am" To: geoffr@is.co.za Date: Wed, 11 Aug 1999 08:53:24 +0200 (CEST) Cc: brian@pobox.com, sos@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Geoff Rehmet wrote: > Brian McGroarty writes : > > In using the ATA driver, I'm unable to automatically mount a > > partition on a master drive on the secondary controller. fsck > > complains that device rwd2s1e isn't configured and exists. > > Immediately mounting by hand works perfectly. > > > > Compiling the kernel with wd instead of ata eliminates the > > problem. > Hmm, > > I had exactly the same problem, although it manifested itself with a > secondary master or slave. It went away a few weeks ago, and I > was never able to make any sensible progress in tracking the problem > down. Hmm, damn, after the problem went away for Geoff I thought it to be solved since I've never heard of it anywhere else, and I cant reproduce it here no matter what I try. Does it help eany if you only has the root partition use the wd dev and have the rest use the prober ad dev entries ?? It could be some artifact from this... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 0: 3: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D5A9A14FCC for ; Wed, 11 Aug 1999 00:02:55 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA56801; Wed, 11 Aug 1999 09:02:37 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199908110702.JAA56801@freebsd.dk> Subject: Re: wd0: interrupt timeout (status 58 error 1) In-Reply-To: <37B0C652.BB7ABE6B@netscape.net> from Francis Jordan at "Aug 11, 1999 1:39:46 am" To: frankrj@netscape.net (Francis Jordan) Date: Wed, 11 Aug 1999 09:02:37 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Francis Jordan wrote: > Yes, HDD on the primary, CD-ROM on the secondary controller. This is a > notebook I'm talking about, so I haven't tried any other CD-ROM drives. > If it doesn't respond at all, then how do you get all the other > information, such as supported read types, speed, etc? Perhaps there is > some other way of making this particular CD-ROM drive generate an > interrupt? Of course, it's just a minor annoyance (and otherwise I'm > very pleased with the driver's performance - many thanks to SOS), but if > the new ATA driver were to eventually replace the old one, it's not a > bad idea to try and get rid of as many silly error messages as possible. Hmm try the patch below so we can tell what command it is failing on.. > Is there just one standard that all ATAPI CD-ROM drives must comply > with, or can there be variations? I apologize if this is a silly > question. There is several versions of the ATAPI standard, but they are all pretty vague, there is LOTS of room for vendors to "improve" thier devices :( Index: ata-all.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v retrieving revision 1.16 diff -u -r1.16 ata-all.c --- ata-all.c 1999/08/06 17:39:37 1.16 +++ ata-all.c 1999/08/11 07:00:09 @@ -693,7 +693,8 @@ scp->active = ATA_WAIT_INTR; outb(scp->ioaddr + ATA_CMD, command); if (tsleep((caddr_t)scp, PRIBIO, "atacmd", 500)) { - printf("ata_command: timeout waiting for interrupt\n"); + printf("ata_command: timeout waiting for interrupt (cmd=0x%02x)\n, + command"); scp->active = ATA_IDLE; return -1; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 0: 3:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from mercury.is.co.za (mercury.is.co.za [196.4.160.222]) by hub.freebsd.org (Postfix) with ESMTP id 7BEE8154EC for ; Wed, 11 Aug 1999 00:03:03 -0700 (PDT) (envelope-from geoffr@is.co.za) Received: from ISJHBEX (isjhbexnode.is.co.za [196.26.1.2]) by mercury.is.co.za (8.9.3/8.9.3) with ESMTP id IAA07210; Wed, 11 Aug 1999 08:59:45 +0200 Received: by isjhbex.is.co.za with Internet Mail Service (5.5.2448.0) id ; Wed, 11 Aug 1999 09:06:12 +0200 Message-ID: From: Geoff Rehmet To: "'Soren Schmidt'" Cc: brian@pobox.com, current@FreeBSD.ORG Subject: RE: ATA - Trouble mounting secondary master Date: Wed, 11 Aug 1999 09:06:10 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm, My root device still lands up on "wd0" - even though my fstab has the root filesystem on ad0s1a. I haven't looked at getting it to use the ad dev entries for the root file system. (I'm assuming that is still WIP.) Geoff. > -----Original Message----- > From: Soren Schmidt [mailto:sos@freebsd.dk] > Sent: 11 August 1999 08:53 > To: geoffr@is.co.za > Cc: brian@pobox.com; sos@FreeBSD.ORG; current@FreeBSD.ORG > Subject: Re: ATA - Trouble mounting secondary master >=20 >=20 > It seems Geoff Rehmet wrote: > > Brian McGroarty writes : > > > In using the ATA driver, I'm unable to automatically mount a > > > partition on a master drive on the secondary controller. fsck > > > complains that device rwd2s1e isn't configured and exists. > > > Immediately mounting by hand works perfectly. > > >=20 > > > Compiling the kernel with wd instead of ata eliminates the > > > problem. > > Hmm, > >=20 > > I had exactly the same problem, although it manifested itself with = a > > secondary master or slave. It went away a few weeks ago, and I > > was never able to make any sensible progress in tracking the = problem > > down. >=20 > Hmm, damn, after the problem went away for Geoff I thought it to be > solved since I've never heard of it anywhere else, and I cant=20 > reproduce > it here no matter what I try. > Does it help eany if you only has the root partition use the wd dev > and have the rest use the prober ad dev entries ?? It could be some > artifact from this... >=20 > -S=F8ren >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 0:26:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 79C5A14E56 for ; Wed, 11 Aug 1999 00:26:45 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA56854; Wed, 11 Aug 1999 09:25:51 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199908110725.JAA56854@freebsd.dk> Subject: Re: ATA - Trouble mounting secondary master In-Reply-To: from Geoff Rehmet at "Aug 11, 1999 9: 6:10 am" To: geoffr@is.co.za (Geoff Rehmet) Date: Wed, 11 Aug 1999 09:25:51 +0200 (CEST) Cc: brian@pobox.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Geoff Rehmet wrote: > Hmm, > > My root device still lands up on "wd0" - even though my fstab has > the root filesystem on ad0s1a. I haven't looked at getting it to > use the ad dev entries for the root file system. (I'm assuming that > is still WIP.) Our boot blocks/loader dont have the needed computrons to use the "ad" device name. However I have some patches to boot2 that allows to boot off an ad root device, provided you dont use the loader, and put the rigth boot string in boot.config. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 1:56: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 461941508A for ; Wed, 11 Aug 1999 01:56:03 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Wed, 11 Aug 1999 09:54:36 +0100 Received: from voodoo.pandhm.co.uk (VOODOO [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id Q4XVHVV4; Wed, 11 Aug 1999 09:54:30 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 11EU9o-0000Jf-00; Wed, 11 Aug 1999 09:54:48 +0100 Date: Wed, 11 Aug 1999 09:54:48 +0100 To: Andy Farkas Cc: freebsd-current@freebsd.org Subject: Re: installing hack(6) overwrites /var/games/hackdir/record file! Message-Id: <19990811095448.B468@voodoo.pandhm.co.uk> References: MIME-Version: 1.0 X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Andy Farkas on Wed, Aug 11, 1999 at 04:24:55AM +1000 From: Dominic Mitchell Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 11, 1999 at 04:24:55AM +1000, Andy Farkas wrote: > Perhaps this should be a PR... > > Seeing as how we are recently being amused by fortune(6) quotes, I thought > I'd mention an acronymn that hasn't been used recently: POLA > > Can anyone explain why every time I upgrade world, my hard earned 'record' > file whilst playing hack(6) gets overwritten by /dev/null, and also all > the user 'bones' and 'save' files rm'd? Blimey! I wondered where all my rogue(6) scores were going. This is an excellent idea. I'll submit a PR, with your diffs and some for rogue. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Finally, when replying to messages only quote the parts of the message your will be discussing or that are relevant. Quoting whole messages and adding two lines at the top is not good etiquette." -- Elias Levy -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 2: 4:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from phluffy.fks.bt (usw1-1-42-ip42.pdx.nwnexus.net [206.63.5.42]) by hub.freebsd.org (Postfix) with ESMTP id 479F0150BC for ; Wed, 11 Aug 1999 02:04:21 -0700 (PDT) (envelope-from myke@ees.com) Received: from localhost (myke@localhost) by phluffy.fks.bt (8.8.8/8.8.8) with ESMTP id CAA15746; Wed, 11 Aug 1999 02:03:41 -0700 (PDT) (envelope-from myke@ees.com) Date: Wed, 11 Aug 1999 02:03:40 -0700 (PDT) From: Mike Holling X-Sender: myke@phluffy.fks.bt To: Thierry Herbelot Cc: Soren Schmidt , Doug White , freebsd-current@FreeBSD.ORG Subject: Re: wd0: interrupt timeout (status 58 error 1) In-Reply-To: <37B09FFF.C6CC6BD5@cybercable.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That can't be true, at least not for the IBM DeskStars I own, I've > > NEVER EVER seen them do that, one proof should be: > > same here > > wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 > wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S > wdc0: unit 1 (wd1): , DMA, 32-bit, multi-block-16 > wd1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S > wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa > wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-16 > wd2: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S I ran into this exact problem on a small LAN server with a single deskstar drive. Usually I would just see the error in the logs once or twice a month without incident, but one time it took down the server hard enough to munge quite a few files. The drive is now in a dualboot win98/freebsd multimedia box and I haven't seen the error again (the box isn't up for a week at a time). - Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 2:38:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from gidgate.gid.co.uk (gidgate.gid.co.uk [193.123.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 6FBD514C0E for ; Wed, 11 Aug 1999 02:38:19 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: (from rb@localhost) by gidgate.gid.co.uk (8.8.8/8.8.7) id KAA03966; Wed, 11 Aug 1999 10:37:32 +0100 (BST) (envelope-from rb) Message-Id: <3.0.6.32.19990811103730.007b8420@192.168.255.1> X-Sender: rbmail@192.168.255.1 X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 11 Aug 1999 10:37:30 +0100 To: Dominic Mitchell From: Bob Bishop Subject: Re: installing hack(6) overwrites /var/games/hackdir/record file! Cc: Andy Farkas , freebsd-current@FreeBSD.ORG In-Reply-To: <19990811095448.B468@voodoo.pandhm.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 09:54 11/08/99 +0100, Dominic Mitchell wrote: >On Wed, Aug 11, 1999 at 04:24:55AM +1000, Andy Farkas wrote: >> Perhaps this should be a PR... >> >> Seeing as how we are recently being amused by fortune(6) quotes, I thought >> I'd mention an acronymn that hasn't been used recently: POLA >> >> Can anyone explain why every time I upgrade world, my hard earned 'record' >> file whilst playing hack(6) gets overwritten by /dev/null, and also all >> the user 'bones' and 'save' files rm'd? > >Blimey! I wondered where all my rogue(6) scores were going. This is an >excellent idea. I'll submit a PR, with your diffs and some for rogue. I think you'll find that hack(6) itself silently removes save and bones files that are older than the binary, a precaution because it relies on data layout in the file. This is a PITA but nontrivial to fix. -- Bob Bishop +44 118 977 4017 rb@gid.co.uk fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 3:18:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (Postfix) with ESMTP id ECAFD14C23 for ; Wed, 11 Aug 1999 03:18:05 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from localhost (localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id UAA57598; Wed, 11 Aug 1999 20:16:19 +1000 (EST) (envelope-from andyf@speednet.com.au) Date: Wed, 11 Aug 1999 20:16:19 +1000 (EST) From: Andy Farkas X-Sender: andyf@localhost To: Bob Bishop Cc: freebsd-current@FreeBSD.ORG Subject: Re: installing hack(6) overwrites /var/games/hackdir/record file! In-Reply-To: <3.0.6.32.19990811103730.007b8420@192.168.255.1> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999, Bob Bishop wrote: > >> Can anyone explain why every time I upgrade world, my hard earned 'record' > >> file whilst playing hack(6) gets overwritten by /dev/null, and also all > >> the user 'bones' and 'save' files rm'd? > > > >Blimey! I wondered where all my rogue(6) scores were going. This is an > >excellent idea. I'll submit a PR, with your diffs and some for rogue. > > I think you'll find that hack(6) itself silently removes save and bones > files that are older than the binary, a precaution because it relies on > data layout in the file. This is a PITA but nontrivial to fix. Yes, hack will invalidate any save or bones file that is older than the mtime of (hard coded!) "/usr/games/hide/hack". And it tells you about it. But I can live with that. Its the trashing of the 'record' file that I'm most concerned about. If this file was untouched during upgrades, I'd be happy. The other point is that the data layout hasn't changed since the game was first brought into the tree (circa Sep '94). > > -- > Bob Bishop +44 118 977 4017 > rb@gid.co.uk fax +44 118 989 4254 (0800-1800 UK) > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 4:41:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from web1005.mail.yahoo.com (web1005.mail.yahoo.com [128.11.23.95]) by hub.freebsd.org (Postfix) with SMTP id 027FC15186 for ; Wed, 11 Aug 1999 04:41:14 -0700 (PDT) (envelope-from bvmcg@yahoo.com) Message-ID: <19990811114120.22915.rocketmail@web1005.mail.yahoo.com> Received: from [24.29.199.43] by web1005.mail.yahoo.com; Wed, 11 Aug 1999 04:41:20 PDT Date: Wed, 11 Aug 1999 04:41:20 -0700 (PDT) From: Brian McGroarty Reply-To: brian@pobox.com Subject: Re: ATA - Trouble mounting secondary master To: Soren Schmidt , geoffr@is.co.za Cc: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just tried and coming in via wd and ad produce the same problem. Note my previous comment - the access light is a steady on for this particular drive. It's left that way when devices are probed during startup. My configuration FWIW - (Note that the devclass_alloc_unit messages are new as of yesterday's cvsup and, presumably, unrelated.) Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #7: Tue Aug 10 22:13:10 CDT 1999 Timecounter "i8254" frequency 1193182 Hz CPU: Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 536870912 (524288K bytes) avail memory = 518422528 (506272K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc028f000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc028f09c. Pentium Pro MTRR support enabled Probing for PnP devices: devclass_alloc_unit: pcib0 already exists, using next available unit number devclass_alloc_unit: pcib0 already exists, using next available unit number devclass_alloc_unit: pcib0 already exists, using next available unit number devclass_alloc_unit: pcib0 already exists, using next available unit number devclass_alloc_unit: pcib0 already exists, using next available unit number npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 WARNING: "bktr" is usurping "bktr"'s cdevsw[] pcib6: at device 1.0 on pci0 pci1: on pcib6 vga-pci0: irq 16 at device 0.0 on pci1 isab0: at device 7.0 on pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 chip1: at device 7.2 on pci0 chip2: at device 7.3 on pci0 bktr0: irq 16 at device 16.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only smbus0: on bti2c0 Hauppauge Model 62471 A Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, dbx stereo. pci0: unknown card DD^0878 (vendor=0x109e, dev=0x0878) at 16.1 irq 16 pcm0: irq 18 at device 18.0 on pci0 pcm0: using I/O space register mapping at 0xef00 fxp0: irq 19 at device 19.0 on pci0fxp0: Ethernet address 00:90:27:18:a6:fa xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 16 at device 20.0 on pci0 xl0: Ethernet address: 00:50:04:01:77:7b xl0: autoneg complete, link status good (half-duplex, 100Mbps) devclass_alloc_unit: pci1 already exists, using next available unit number pcib1: on motherboard pci2: on pcib1 devclass_alloc_unit: pci2 already exists, using next available unit number pcib2: on motherboard pci3: on pcib2 devclass_alloc_unit: pci3 already exists, using next available unit number pcib3: on motherboard pci4: on pcib3 devclass_alloc_unit: pci4 already exists, using next available unit number pcib4: on motherboard pci5: on pcib4 devclass_alloc_unit: pci5 already exists, using next available unit number pcib5: on motherboard pci6: on pcib5 isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging disabled SMP: AP CPU #1 Launched! ata0: master: setting up UDMA2 mode on PIIX4 chip OK ad0: ATA-4 disk at ata0 as master ad0: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 31 depth queue, DMA mode ata0: slave: setting up UDMA2 mode on PIIX4 chip OK ad1: ATA-4 disk at ata0 as slave ad1: 21557MB (44150400 sectors), 43800 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 31 depth queue, DMA mode ata1: master: setting up UDMA2 mode on PIIX4 chip OK ad2: ATA-4 disk at ata1 as master ad2: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=2 ad2: 16 secs/int, 31 depth queue, DMA mode acd0: CDROM drive at ata1 as slave acd0: drive speed 344 - 1034KB/sec, 384KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: supported write types: CD-R, CD-RW, test write acd0: Audio: play, 128 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked, lock protected changing root device to wd0s1a changing root device to wd0a --- Soren Schmidt wrote: > It seems Geoff Rehmet wrote: > > Brian McGroarty writes : > > > In using the ATA driver, I'm unable to automatically mount > a > > > partition on a master drive on the secondary controller. > fsck > > > complains that device rwd2s1e isn't configured and exists. > > > Immediately mounting by hand works perfectly. > > > > > > Compiling the kernel with wd instead of ata eliminates the > > > problem. > > Hmm, > > > > I had exactly the same problem, although it manifested > itself with a > > secondary master or slave. It went away a few weeks ago, > and I > > was never able to make any sensible progress in tracking the > problem > > down. > > Hmm, damn, after the problem went away for Geoff I thought it > to be > solved since I've never heard of it anywhere else, and I cant > reproduce > it here no matter what I try. > Does it help eany if you only has the root partition use the > wd dev > and have the rest use the prober ad dev entries ?? It could be > some > artifact from this... > > -Søren > > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 4:47:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from mercury.is.co.za (mercury.is.co.za [196.4.160.222]) by hub.freebsd.org (Postfix) with ESMTP id 0DBFC150D9 for ; Wed, 11 Aug 1999 04:45:59 -0700 (PDT) (envelope-from geoffr@is.co.za) Received: from ISJHBEX (isjhbexnode.is.co.za [196.26.1.2]) by mercury.is.co.za (8.9.3/8.9.3) with ESMTP id NAA01846; Wed, 11 Aug 1999 13:40:56 +0200 Received: by isjhbex.is.co.za with Internet Mail Service (5.5.2448.0) id ; Wed, 11 Aug 1999 13:47:17 +0200 Message-ID: From: Geoff Rehmet To: "'brian@pobox.com'" , Soren Schmidt , Geoff Rehmet Cc: current@FreeBSD.ORG Subject: RE: ATA - Trouble mounting secondary master Date: Wed, 11 Aug 1999 13:47:15 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FWIW, I am running a July 30th kernel. let me see if the problem comes back with a new CVSup. > -----Original Message----- > From: Brian McGroarty [mailto:bvmcg@yahoo.com] > Sent: 11 August 1999 01:41 > To: Soren Schmidt; geoffr@is.co.za > Cc: current@FreeBSD.ORG > Subject: Re: ATA - Trouble mounting secondary master > > > I've just tried and coming in via wd and ad produce the same > problem. > > Note my previous comment - the access light is a steady on for > this particular drive. It's left that way when devices are > probed during startup. > > My configuration FWIW - > > (Note that the devclass_alloc_unit messages are new as of > yesterday's cvsup and, presumably, unrelated.) > > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights > reserved. > FreeBSD 4.0-CURRENT #7: Tue Aug 10 22:13:10 CDT 1999 > Timecounter "i8254" frequency 1193182 Hz > CPU: Celeron (686-class CPU) > Origin = "GenuineIntel" Id = 0x665 Stepping = 5 > > Features=0x183fbff ,MTRR,PGE,MCA,CM > OV,PAT,PSE36,MMX,FXSR> > real memory = 536870912 (524288K bytes) > avail memory = 518422528 (506272K bytes) > Programming 24 pins in IOAPIC #0 > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 > cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > Preloaded elf kernel "kernel" at 0xc028f000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc028f09c. > Pentium Pro MTRR support enabled > Probing for PnP devices: > devclass_alloc_unit: pcib0 already exists, using next available > unit number > devclass_alloc_unit: pcib0 already exists, using next available > unit number > devclass_alloc_unit: pcib0 already exists, using next available > unit number > devclass_alloc_unit: pcib0 already exists, using next available > unit number > devclass_alloc_unit: pcib0 already exists, using next available > unit number > npx0: on motherboard > npx0: INT 16 interface > pcib0: on > motherboard > pci0: on pcib0 > WARNING: "bktr" is usurping "bktr"'s cdevsw[] > pcib6: at device > 1.0 on pci0 > pci1: on pcib6 > vga-pci0: irq 16 at > device 0.0 on pci1 > isab0: at device 7.0 on pci0 > ata-pci0: at device 7.1 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > chip1: at device 7.2 on pci0 > chip2: at device 7.3 > on pci0 > bktr0: irq 16 at device 16.0 on pci0 > iicbb0: on bti2c0 > iicbus0: on iicbb0 master-only > smbus0: on bti2c0 > Hauppauge Model 62471 A > Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, dbx stereo. > pci0: unknown card DD^0878 (vendor=0x109e, dev=0x0878) at 16.1 > irq 16 > pcm0: irq 18 at device 18.0 on pci0 > pcm0: using I/O space register mapping at 0xef00 > fxp0: irq 19 at device > 19.0 on pci0fxp0: Ethernet address 00:90:27:18:a6:fa > xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 16 at device 20.0 on > pci0 > xl0: Ethernet address: 00:50:04:01:77:7b > xl0: autoneg complete, link status good (half-duplex, 100Mbps) > devclass_alloc_unit: pci1 already exists, using next available > unit number > pcib1: on motherboard > pci2: on pcib1 > devclass_alloc_unit: pci2 already exists, using next available > unit number > pcib2: on motherboard > pci3: on pcib2 > devclass_alloc_unit: pci3 already exists, using next available > unit number > pcib3: on motherboard > pci4: on pcib3 > devclass_alloc_unit: pci4 already exists, using next available > unit number > pcib4: on motherboard > pci5: on pcib4 > devclass_alloc_unit: pci5 already exists, using next available > unit number > pcib5: on motherboard > pci6: on pcib5 > isa0: on motherboard > fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on > isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > psm0: irq 12 on atkbdc0 > psm0: model IntelliMouse, device ID 3 > vga0: at port 0x3b0-0x3df iomem > 0xa0000-0xbffff on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: routing 8254 via pin 2 > IP packet filtering initialized, divert enabled, rule-based > forwarding disabled, > logging disabled > SMP: AP CPU #1 Launched! > ata0: master: setting up UDMA2 mode on PIIX4 chip OK > ad0: ATA-4 disk at ata0 as master > ad0: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, > 512 B/S > ad0: piomode=4, dmamode=2, udmamode=2 > ad0: 16 secs/int, 31 depth queue, DMA mode > ata0: slave: setting up UDMA2 mode on PIIX4 chip OK > ad1: ATA-4 disk at ata0 as slave > ad1: 21557MB (44150400 sectors), 43800 cyls, 16 heads, 63 S/T, > 512 B/S > ad1: piomode=4, dmamode=2, udmamode=2 > ad1: 16 secs/int, 31 depth queue, DMA mode > ata1: master: setting up UDMA2 mode on PIIX4 chip OK > ad2: ATA-4 disk at ata1 as master > ad2: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, > 512 B/S > ad2: piomode=4, dmamode=2, udmamode=2 > ad2: 16 secs/int, 31 depth queue, DMA mode > acd0: CDROM drive at ata1 as slave > acd0: drive speed 344 - 1034KB/sec, 384KB cache > acd0: supported read types: CD-R, CD-RW, CD-DA, packet track > acd0: supported write types: CD-R, CD-RW, test write > acd0: Audio: play, 128 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked, lock protected > changing root device to wd0s1a > changing root device to wd0a > > > > --- Soren Schmidt wrote: > > It seems Geoff Rehmet wrote: > > > Brian McGroarty writes : > > > > In using the ATA driver, I'm unable to automatically mount > > a > > > > partition on a master drive on the secondary controller. > > fsck > > > > complains that device rwd2s1e isn't configured and exists. > > > > Immediately mounting by hand works perfectly. > > > > > > > > Compiling the kernel with wd instead of ata eliminates the > > > > problem. > > > Hmm, > > > > > > I had exactly the same problem, although it manifested > > itself with a > > > secondary master or slave. It went away a few weeks ago, > > and I > > > was never able to make any sensible progress in tracking the > > problem > > > down. > > > > Hmm, damn, after the problem went away for Geoff I thought it > > to be > > solved since I've never heard of it anywhere else, and I cant > > reproduce > > it here no matter what I try. > > Does it help eany if you only has the root partition use the > > wd dev > > and have the rest use the prober ad dev entries ?? It could be > > some > > artifact from this... > > > > -Søren > > > > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 5: 9:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 8BFC015319 for ; Wed, 11 Aug 1999 05:09:21 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Wed, 11 Aug 1999 13:08:01 +0100 Received: from voodoo.pandhm.co.uk (VOODOO [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id Q4XVHV5W; Wed, 11 Aug 1999 13:07:54 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 11EXAz-0000YL-00; Wed, 11 Aug 1999 13:08:13 +0100 Date: Wed, 11 Aug 1999 13:08:13 +0100 To: Dominic Mitchell Cc: Andy Farkas , freebsd-current@freebsd.org Subject: Re: installing hack(6) overwrites /var/games/hackdir/record file! Message-Id: <19990811130812.A2117@voodoo.pandhm.co.uk> References: <19990811095448.B468@voodoo.pandhm.co.uk> MIME-Version: 1.0 X-Mailer: Mutt 0.95.6i In-Reply-To: <19990811095448.B468@voodoo.pandhm.co.uk>; from Dominic Mitchell on Wed, Aug 11, 1999 at 09:54:48AM +0100 From: Dominic Mitchell Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 11, 1999 at 09:54:48AM +0100, Dominic Mitchell wrote: > On Wed, Aug 11, 1999 at 04:24:55AM +1000, Andy Farkas wrote: > > Perhaps this should be a PR... > > > > Seeing as how we are recently being amused by fortune(6) quotes, I thought > > I'd mention an acronymn that hasn't been used recently: POLA > > > > Can anyone explain why every time I upgrade world, my hard earned 'record' > > file whilst playing hack(6) gets overwritten by /dev/null, and also all > > the user 'bones' and 'save' files rm'd? > > Blimey! I wondered where all my rogue(6) scores were going. This is an > excellent idea. I'll submit a PR, with your diffs and some for rogue. OK, if you'd like to have a look at PR bin/13068, and maybe somebody could commit if it's agreed to be a good thing. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Finally, when replying to messages only quote the parts of the message your will be discussing or that are relevant. Quoting whole messages and adding two lines at the top is not good etiquette." -- Elias Levy -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 5:46:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 42BAC154DE for ; Wed, 11 Aug 1999 05:46:12 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id OAA12086; Wed, 11 Aug 1999 14:45:23 +0200 (CEST) (envelope-from des) To: "Michael A. Endsley" Cc: freebsd-current@FreeBSD.ORG Subject: Re: vty3 and 4.0 snap 080799 References: <37AEE7F7.8EA393DD@customcpu.com> From: Dag-Erling Smorgrav Date: 11 Aug 1999 14:45:23 +0200 In-Reply-To: "Michael A. Endsley"'s message of "Mon, 09 Aug 1999 06:38:47 -0800" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Michael A. Endsley" writes: > I just downloaded the latest snap (080799) and tried installing it. > When getting to the media section and configuring ppp for a ftp install, > I try going to vty3 (alt-f3). However, that vty is not available. I have > tried this 3 times now. Is this broken? ttyv3 is on Alt-F4. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 7:22:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from maildns2.fsbdial.co.uk (s24.athenenet.co.uk [195.89.137.30]) by hub.freebsd.org (Postfix) with ESMTP id CAEDB14D1A for ; Wed, 11 Aug 1999 07:22:46 -0700 (PDT) (envelope-from frankrj@netscape.net) Received: from [212.1.146.19] by maildns2.freenet.co.uk (NTMail 4.30.0012/NT0619.00.9914eb79) with ESMTP id jslomaaa for ; Wed, 11 Aug 1999 15:21:51 +0100 Message-ID: <37B187D2.8312B4E0@netscape.net> Date: Wed, 11 Aug 1999 15:25:22 +0100 From: Francis Jordan X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: wd0: interrupt timeout (status 58 error 1) References: <199908110702.JAA56801@freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > > Hmm try the patch below so we can tell what command it is failing on.. > > Index: ata-all.c > --- ata-all.c 1999/08/06 17:39:37 1.16 > +++ ata-all.c 1999/08/11 07:00:09 > @@ -693,7 +693,8 @@ > scp->active = ATA_WAIT_INTR; > outb(scp->ioaddr + ATA_CMD, command); > if (tsleep((caddr_t)scp, PRIBIO, "atacmd", 500)) { > - printf("ata_command: timeout waiting for interrupt\n"); > + printf("ata_command: timeout waiting for interrupt (cmd=0x%02x)\n, > + command"); > scp->active = ATA_IDLE; > return -1; > } After removing the quotation mark after the word command in the above patch (smile), it prints: ata_command: timeout waiting for interrupt (cmd=0xa1) What is command 0xa1? Frank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 7:48: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 1868714CF8 for ; Wed, 11 Aug 1999 07:47:56 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id QAA57679; Wed, 11 Aug 1999 16:47:54 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199908111447.QAA57679@freebsd.dk> Subject: Re: wd0: interrupt timeout (status 58 error 1) In-Reply-To: <37B187D2.8312B4E0@netscape.net> from Francis Jordan at "Aug 11, 1999 3:25:22 pm" To: frankrj@netscape.net (Francis Jordan) Date: Wed, 11 Aug 1999 16:47:54 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Francis Jordan wrote: > Soren Schmidt wrote: > > > > Hmm try the patch below so we can tell what command it is failing on.. > > After removing the quotation mark after the word command in the above > patch (smile), it prints: Yeah, so much for writing code without compiling it :) > ata_command: timeout waiting for interrupt (cmd=0xa1) > > What is command 0xa1? From ata-all.h: #define ATA_C_ATAPI_IDENTIFY 0xa1 /* get ATAPI params*/ That makes it difficult to support that drive :), but I think there must be some other reason it fails, hmmm... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 8:40:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id B348214BDD; Wed, 11 Aug 1999 08:40:39 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id LAA01185; Wed, 11 Aug 1999 11:34:57 -0400 (EDT) Date: Wed, 11 Aug 1999 11:34:56 -0400 (EDT) From: "Matthew N. Dodd" To: Warner Losh Cc: Peter Wemm , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: <199908101820.MAA13330@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Aug 1999, Warner Losh wrote: > I'd be very careful of line wrapping probe messages. I have scripts > that rely on them being on one line to get a list of irqs, etc. I would consider information from the kernel probe/attach to be useful only for humans. An interface to query the resource manager directly is likely to be a better solution to your problem. Besides, if your perl skills aren't able to cope with getting all 'fooX:' lines, and stripping out the 'fooX:' bits before parsing then you have other problems. > However, the whole issue of how probe messages should print, and how > much is a religious war that I try to steer clear of... Correct, but the nature of the kernel probe/attach messages is to convey information in a readable, consistent, useful manner. If we didn't want pretty line wrapping we'd all be using linux and have stupid stuff like copyright messages as well. :) At some point all of the boot messages should be wrapped by 'if (bootverbose) { ... }' anyway. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 9: 3:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B29AB14E97; Wed, 11 Aug 1999 09:03:24 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA20314; Wed, 11 Aug 1999 10:03:27 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA17583; Wed, 11 Aug 1999 10:03:51 -0600 (MDT) Message-Id: <199908111603.KAA17583@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: it's time... Cc: Peter Wemm , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Wed, 11 Aug 1999 11:34:56 EDT." References: Date: Wed, 11 Aug 1999 10:03:51 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : On Tue, 10 Aug 1999, Warner Losh wrote: : > I'd be very careful of line wrapping probe messages. I have scripts : > that rely on them being on one line to get a list of irqs, etc. : : I would consider information from the kernel probe/attach to be useful : only for humans. Then we disagree. There are several scripts floating around that use them for purposes where there isn't a kernel interface... It would be ideal if there were interfaces for all this info, but there isn't always. : An interface to query the resource manager directly is likely to be a : better solution to your problem. Well, only kinda. That was one example. The other example is finding out what the ide driver thought the disk geometry of a disk was... : Besides, if your perl skills aren't able to cope with getting all 'fooX:' : lines, and stripping out the 'fooX:' bits before parsing then you have : other problems. Hah! You presume too much. None of these scripts are written in perl, so the size of my perl schl*** isn't at issue here :-) You also assume that the wrapping would be of the form fooX:. FreeBSD's boot messages aren't consistant about this right now, witness the difference between isa and pci devices: sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vs ahc0: irq 10 at device 16.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs The "proper" way to do this would be sio1 at isa0 port 0x2f8-0x2ff irq 3: type 16550A ahc0 at pci0 irq 10 device 16.0: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs if you must introduce wrapping. Each phrase should either fit on the current line or be bumped to the next line. However, what is a line? Also, I use "proper" in quotes because others will reasonably differ with the exact details... : Correct, but the nature of the kernel probe/attach messages is to convey : information in a readable, consistent, useful manner. Agreed. However, what's magical about 80 columns? My editors go out to 180 sometimes. The console can easily be placed into a mode where it is > 80. This is especially true for the serial console where it might be connected to a 132 column printer. : If we didn't want pretty line wrapping we'd all be using linux and have : stupid stuff like copyright messages as well. :) Don't even get me started on linux' boot messages. :-) I happen to like the stark elegance of the OpenBSD/NetBSD boot messages. Here's the entire dmesg from the boot of my rPC44 MIPS machine when booted under OpenBSD. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-1999 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 2.4-current (IMP-PCCARD) #37: Mon Feb 1 13:28:06 MST 1999 imp@local-service.village.org:/home/imp/src/sys/arch/arc/compile/IMP-PCCARD real mem = 32235520 avail mem = 27754496 using 419 buffers containing 1716224 bytes of memory mainbus0 (root) cpu0 at mainbus0: MIPS R4400 CPU Rev. 4.0 with MIPS R4010 FPC Rev. 0.0 L1 Cache I size 16kb(16 line), D size 16kb(16 line), direct mapped. L2 cache doesn't snoop uncached cpu accesses. isabr0 at mainbus0 isa0 at isabr0 isa_io_base 0xb0000000 isa_mem_base 0xa0000000 com0 at isa0 port 0x3f8-0x3ff irq 4: ns16450, no fifo com1 at isa0 port 0x2f8-0x2ff irq 3: ns16450, no fifo wdc0 at isa0 port 0x1f0-0x1f7 irq 14 wd0 at wdc0 drive 0: wd0: 2060MB, 4186 cyl, 16 head, 63 sec, 512 bytes/sec, 4219488 sec total wd0: using 16-sector 16-bit pio transfers, lba addressing (109KB cache) clock0 at isa0 port 0x70-0x6d5 irq 0: mc146818 or compatible pcprobe: reset error 1 pc0 at isa0 port 0x60-0x6c5 irq 1: color joy0 at isa0 port 0x201: joystick not connected ed0 at isa0 port 0x300-0x31f irq 5: address 00:00:1b:1e:52:a7, type NE2000 (16-bit) boot device: wd0. root on wd0a rootdev=0x400 rrootdev=0x1200 rawdev=0x1202 Where OpenBSD has com0 at isa0 port 0x3f8-0x3ff irq 4: ns16450, no fifo com1 at isa0 port 0x2f8-0x2ff irq 3: ns16450, no fifo FreeBSD we has sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: configured irq 5 not in bitmap of probed irqs 0 sio3: configured irq 9 not in bitmap of probed irqs 0 which is much more verbose. The entire boot process (including rc output) fits on the 48x132 mode that my rPC/44 comes up in. With the same config on FreeBSD, the kernel messages it wouldn't even fit, let alone the rc output. : At some point all of the boot messages should be wrapped by 'if : (bootverbose) { ... }' anyway. No! At some point they should use a facility similar to solaris/sysv where they don't display, but do make it into the dmesg buffer... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 9:35:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 889AD14C59; Wed, 11 Aug 1999 09:35:35 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA04157; Wed, 11 Aug 1999 10:34:46 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA28760; Wed, 11 Aug 1999 10:34:45 -0600 Date: Wed, 11 Aug 1999 10:34:45 -0600 Message-Id: <199908111634.KAA28760@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: "Matthew N. Dodd" , Peter Wemm , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: <199908111603.KAA17583@harmony.village.org> References: <199908111603.KAA17583@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : Correct, but the nature of the kernel probe/attach messages is to convey > : information in a readable, consistent, useful manner. > > Agreed. However, what's magical about 80 columns? What's magical is that almost every text console is limited to 80 columns (think serial console), as well as the standard default size for terminal emulators is 80 columns. My editors go out > to 180 sometimes. The console can easily be placed into a mode where > it is > 80. This is especially true for the serial console where it > might be connected to a 132 column printer. Just because it *can* be connected to a 132 column printer doesn't mean it *will* be connected. Most printers that I use are 80 columns wide. Heck, almost *every* printer I use is that wide, hence the whole 80 column thing. The most common case for a console is an 80 column wide console (this is the default for the virtual terminals, most printers, most text terminals, etc..) Changing it is silly, and non-standard. > No! At some point they should use a facility similar to solaris/sysv > where they don't display, but do make it into the dmesg buffer... On my Solaris box, they are displayed at boot time. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 9:48:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 1D6F51558E; Wed, 11 Aug 1999 09:47:58 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id MAA02602; Wed, 11 Aug 1999 12:47:32 -0400 (EDT) Date: Wed, 11 Aug 1999 12:47:31 -0400 (EDT) From: "Matthew N. Dodd" To: Warner Losh Cc: Peter Wemm , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: <199908111603.KAA17583@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999, Warner Losh wrote: > Then we disagree. There are several scripts floating around that use > them for purposes where there isn't a kernel interface... It would be > ideal if there were interfaces for all this info, but there isn't > always. Fine. Due to flux in the bus-system between versions, probe/attach information is essentially a non supported interface for gathering this data. If you do wish to gather it from this source its up to you to DTRT. If you dislike this then your input on a standard interface to this information would likely be of use. > : An interface to query the resource manager directly is likely to be a > : better solution to your problem. > > Well, only kinda. That was one example. The other example is finding > out what the ide driver thought the disk geometry of a disk was... If that information needs to be presented I see no reason why drivers can't do some magic and make /kern/foo/wd0/geometry spit out the right thing. Granted, this is more complex, but depending on boot messages for this information is setting yourself up for problems. > : Besides, if your perl skills aren't able to cope with getting all 'fooX:' > : lines, and stripping out the 'fooX:' bits before parsing then you have > : other problems. > > Hah! You presume too much. None of these scripts are written in > perl, so the size of my perl schl*** isn't at issue here :-) You also > assume that the wrapping would be of the form fooX:. FreeBSD's boot > messages aren't consistant about this right now, witness the > difference between isa and pci devices: > > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > > vs > > ahc0: irq 10 at device 16.0 on pci0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > > The "proper" way to do this would be > > sio1 at isa0 port 0x2f8-0x2ff irq 3: type 16550A > ahc0 at pci0 irq 10 device 16.0: > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Incorrect. The device name should be separated from the rest of the line by a ':'. > if you must introduce wrapping. Each phrase should either fit on the > current line or be bumped to the next line. However, what is a line? > > Also, I use "proper" in quotes because others will reasonably differ > with the exact details... Indeed. But you've still prooved my point that the probe/attach messages are an unsupported source for such information. > : Correct, but the nature of the kernel probe/attach messages is to convey > : information in a readable, consistent, useful manner. > > Agreed. However, what's magical about 80 columns? My editors go out > to 180 sometimes. The console can easily be placed into a mode where > it is > 80. This is especially true for the serial console where it > might be connected to a 132 column printer. In the beginning was the punch card... > : If we didn't want pretty line wrapping we'd all be using linux and have > : stupid stuff like copyright messages as well. :) > > Don't even get me started on linux' boot messages. :-) > > I happen to like the stark elegance of the OpenBSD/NetBSD boot > messages. Here's the entire dmesg from the boot of my rPC44 MIPS > machine when booted under OpenBSD. > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-1999 OpenBSD. All rights reserved. > http://www.OpenBSD.org > > OpenBSD 2.4-current (IMP-PCCARD) #37: Mon Feb 1 13:28:06 MST 1999 > imp@local-service.village.org:/home/imp/src/sys/arch/arc/compile/IMP-PCCARD > real mem = 32235520 > avail mem = 27754496 > using 419 buffers containing 1716224 bytes of memory > mainbus0 (root) > cpu0 at mainbus0: MIPS R4400 CPU Rev. 4.0 with MIPS R4010 FPC Rev. 0.0 > L1 Cache I size 16kb(16 line), D size 16kb(16 line), direct mapped. > L2 cache doesn't snoop uncached cpu accesses. > isabr0 at mainbus0 > isa0 at isabr0 isa_io_base 0xb0000000 isa_mem_base 0xa0000000 > com0 at isa0 port 0x3f8-0x3ff irq 4: ns16450, no fifo > com1 at isa0 port 0x2f8-0x2ff irq 3: ns16450, no fifo > wdc0 at isa0 port 0x1f0-0x1f7 irq 14 > wd0 at wdc0 drive 0: > wd0: 2060MB, 4186 cyl, 16 head, 63 sec, 512 bytes/sec, 4219488 sec total > wd0: using 16-sector 16-bit pio transfers, lba addressing (109KB cache) > clock0 at isa0 port 0x70-0x6d5 irq 0: mc146818 or compatible > pcprobe: reset error 1 > pc0 at isa0 port 0x60-0x6c5 irq 1: color > joy0 at isa0 port 0x201: joystick not connected > ed0 at isa0 port 0x300-0x31f irq 5: address 00:00:1b:1e:52:a7, type NE2000 (16-bit) > boot device: wd0. > root on wd0a > rootdev=0x400 rrootdev=0x1200 rawdev=0x1202 > > Where OpenBSD has > > com0 at isa0 port 0x3f8-0x3ff irq 4: ns16450, no fifo > com1 at isa0 port 0x2f8-0x2ff irq 3: ns16450, no fifo > > FreeBSD we has > > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > sio2: configured irq 5 not in bitmap of probed irqs 0 > sio3: configured irq 9 not in bitmap of probed irqs 0 > > which is much more verbose. The entire boot process (including rc > output) fits on the 48x132 mode that my rPC/44 comes up in. With the > same config on FreeBSD, the kernel messages it wouldn't even fit, let > alone the rc output. I don't think its unreasonable to have multiple levels of verbosity in the probe/attach messages. level meaning 0 no probe/attach messages for bus/device printed 1 device name/bus attachment point 2 bus/device resource reservation announcements 3 device specific versioning/level/other messages > : At some point all of the boot messages should be wrapped by 'if > : (bootverbose) { ... }' anyway. > > No! At some point they should use a facility similar to solaris/sysv > where they don't display, but do make it into the dmesg buffer... The effect is the same. At some point we need to provide output only on error, like the rest of unix. I submit that I like verbose boot messages and want them to be well formatted at the same time as I spend a lot of time yanking cards in and out of systems and need to make sure that my probe/attach routines DTRT. Normal users are likely to enjoy the graphical splash screen more than the frightening spew of boot messages. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 9:50:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 20B6915578; Wed, 11 Aug 1999 09:50:19 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id MAA02636; Wed, 11 Aug 1999 12:49:28 -0400 (EDT) Date: Wed, 11 Aug 1999 12:49:28 -0400 (EDT) From: "Matthew N. Dodd" To: Nate Williams Cc: Warner Losh , Peter Wemm , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: <199908111634.KAA28760@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999, Nate Williams wrote: > The most common case for a console is an 80 column wide console (this is > the default for the virtual terminals, most printers, most text > terminals, etc..) > > Changing it is silly, and non-standard. The line wrapping stuff I brought back for the EISA bus stuff in -current makes it easy to define the wrap point. If some small number of people want the ability to wrap at 132 or 40 or whatever, I don't think its unreasonable to provide them the knob to tweak in the boot loader. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 10: 0:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from bouvreuil.cybercable.fr (bouvreuil.cybercable.fr [212.198.3.12]) by hub.freebsd.org (Postfix) with SMTP id 9C9CB155D0 for ; Wed, 11 Aug 1999 10:00:04 -0700 (PDT) (envelope-from herbelot@cybercable.fr) Received: (qmail 12699 invoked from network); 11 Aug 1999 16:46:45 -0000 Received: from d166.paris-38.cybercable.fr (HELO cybercable.fr) ([212.198.38.166]) (envelope-sender ) by bouvreuil.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 11 Aug 1999 16:46:45 -0000 Message-ID: <37B1A8EF.75A6B84F@cybercable.fr> Date: Wed, 11 Aug 1999 18:46:39 +0200 From: Thierry Herbelot Organization: Les barbus =?iso-8859-1?Q?associ=E9s?=, Paris, France X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: dwhite@resnet.uoregon.edu, freebsd-current@FreeBSD.ORG Subject: Re: wd0: interrupt timeout (status 58 error 1) References: <199908102157.XAA55903@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > [SNIP] > > Have you tried putting disks on the UDMA66 channel ?? I think it > should work in upto WDMA mode now with the ata driver... I have first to install 4.0 and from my wd2 (I've got a little help from RNordier, I should make do) Then, I'll get a UDMA-66 drive (any recommendation ?) TfH > > -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 10:25: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5DA8514CCF; Wed, 11 Aug 1999 10:24:49 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA20600; Wed, 11 Aug 1999 11:24:31 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA18087; Wed, 11 Aug 1999 11:24:56 -0600 (MDT) Message-Id: <199908111724.LAA18087@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: it's time... Cc: Nate Williams , Peter Wemm , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Wed, 11 Aug 1999 12:49:28 EDT." References: Date: Wed, 11 Aug 1999 11:24:56 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : The line wrapping stuff I brought back for the EISA bus stuff in -current : makes it easy to define the wrap point. If some small number of people : want the ability to wrap at 132 or 40 or whatever, I don't think its : unreasonable to provide them the knob to tweak in the boot loader. Despite what nate think about 80 columns, my PDA cannot display more than between 30-45 characters, depending on the font, so having a knob for that would be useful in the long term. It also would allow one to kick the VGA display into 132 columns in the boot loader and have more of a chance to get more of the boot process on the screen. syscons already supports parts of this... There is no reason to hard code 80 into the kernel. Otherwise one could argue why have stty columns at all :-). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 10:30:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id ACB48155CF; Wed, 11 Aug 1999 10:30:45 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA04915; Wed, 11 Aug 1999 11:29:05 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA29297; Wed, 11 Aug 1999 11:29:04 -0600 Date: Wed, 11 Aug 1999 11:29:04 -0600 Message-Id: <199908111729.LAA29297@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: "Matthew N. Dodd" , Nate Williams , Peter Wemm , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: <199908111724.LAA18087@harmony.village.org> References: <199908111724.LAA18087@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : The line wrapping stuff I brought back for the EISA bus stuff in -current > : makes it easy to define the wrap point. If some small number of people > : want the ability to wrap at 132 or 40 or whatever, I don't think its > : unreasonable to provide them the knob to tweak in the boot loader. > > Despite what nate think about 80 columns, my PDA cannot display more > than between 30-45 characters, depending on the font, so having a knob > for that would be useful in the long term. And you plan on booting FreeBSD on your PDA? > It also would allow one to kick the VGA display into 132 columns in > the boot loader and have more of a chance to get more of the boot > process on the screen. syscons already supports parts of this... My firewall doesn't have a VGA display. :( > There is no reason to hard code 80 into the kernel. Otherwise one > could argue why have stty columns at all :-). stty columns is only effective *AFTER* you have a shell and the box has booted. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 10:30:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 14809155D7 for ; Wed, 11 Aug 1999 10:30:46 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id TAA58063; Wed, 11 Aug 1999 19:30:17 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199908111730.TAA58063@freebsd.dk> Subject: Re: wd0: interrupt timeout (status 58 error 1) In-Reply-To: <37B1A8EF.75A6B84F@cybercable.fr> from Thierry Herbelot at "Aug 11, 1999 6:46:39 pm" To: herbelot@cybercable.fr (Thierry Herbelot) Date: Wed, 11 Aug 1999 19:30:17 +0200 (CEST) Cc: dwhite@resnet.uoregon.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Thierry Herbelot wrote: > Soren Schmidt wrote: > > > [SNIP] > > > > Have you tried putting disks on the UDMA66 channel ?? I think it > > should work in upto WDMA mode now with the ata driver... > > I have first to install 4.0 and from my wd2 (I've got a little help from > RNordier, I should make do) > > Then, I'll get a UDMA-66 drive (any recommendation ?) You can put any IDE drive on those channels, but of cause you can only use UDMA66 on capable drives. I'd just be interested in if the newest ata driver finds the controller, UDMA66 is not supported yet anyways only std WDMA... And me, I'm a sucker for IBM or Maxtor drives in that order... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 10:43:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id EE15714D77; Wed, 11 Aug 1999 10:43:44 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA20699; Wed, 11 Aug 1999 11:43:41 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA18270; Wed, 11 Aug 1999 11:44:06 -0600 (MDT) Message-Id: <199908111744.LAA18270@harmony.village.org> To: nate@mt.sri.com (Nate Williams) Subject: Re: it's time... Cc: "Matthew N. Dodd" , Peter Wemm , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Wed, 11 Aug 1999 11:29:04 MDT." <199908111729.LAA29297@mt.sri.com> References: <199908111729.LAA29297@mt.sri.com> <199908111724.LAA18087@harmony.village.org> Date: Wed, 11 Aug 1999 11:44:06 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908111729.LAA29297@mt.sri.com> Nate Williams writes: : And you plan on booting FreeBSD on your PDA? Yes. I'm already booting NetBSD/hpcmips on it.... But that's another thread all by itself... : stty columns is only effective *AFTER* you have a shell and the box has : booted. Yes I know that, but you seem to be arguing that all terminals have 80 columns... This is not the case, although many of them do. I was following your line of reasoning to its logical conclusion (since all terminals have 80 columns, why do we need to tell the kernel how big our terminals are). I agree 100% that 80 shall be the default, since that's how wide these things usually have been since 1890 and this man named Hollereth(sp?)... I just want to make sure that I can change that default. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 10:49:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id EB1BA14D77 for ; Wed, 11 Aug 1999 10:49:07 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb35.imasy.or.jp [202.227.24.163]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id CAA10835; Thu, 12 Aug 1999 02:48:38 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199908111748.CAA10835@tasogare.imasy.or.jp> To: steveo@iol.ie Cc: iwasaki@jp.freebsd.org, freebsd-current@FreeBSD.ORG, plm@xs4all.nl Subject: Re: recent apm changes In-Reply-To: Your message of "Tue, 10 Aug 1999 16:32:37 +0100 (IST)" References: X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 12 Aug 1999 02:52:21 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 42 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > Oh, do you have suspend button on your box? Cool. > > On my poor experience, suspeding by hot-keys easier to > > success than by zzz(8). > > On this point I can report the oppposite experience, on my > machine (a no name special) the trackpad tends to lock up if touched > between power on and resume finishing. The best indicator of safety is > apm -z returning, if I use the button I have to guess. Ahh, I've seen this kind of behavior on some laptops. I guess this is related with some sort of time limits on communication with APM BIOS. APM Spec. v1.2 Appendix D - APM Driver Considerations ----- When an APM connection exists, the APM BIOS transitions into System Standby and System Suspend states only when directed to do so by a call from the APM Driver. The calls to change system states are invoked by the APM Driver only after the APM BIOS indicates that the state transition should be made, and the APM Driver has checked with all APM-aware applications to make sure that it is an appropriate time to change system states. However, there are three cases where the APM BIOS may make the system state transition itself. The first case is if the APM Driver does not pick up a posted Standby Request, Suspend Request or Critical Suspend Notification event within the 2 second ~~~~~~~~~~~~~~~~~~~ (one second plus one second grace period) time limit. The second is when the APM Driver, after picking up the event, does not respond to a Standby Request, Suspend Request or Critical Suspend Notification event with an appropriate Set Power State call within 5 seconds of ~~~~~~~~~~~~~~~~ receiving the event. The last situation is when the APM Driver has responded to an event with a Request Processing Set Power call and does not reply again within another 5 seconds.The CPU is power managed according to CPU Idle and CPU Busy calls made by the APM Driver to the APM BIOS. ------------------------------------------------------------ Last time, we didn't have `Last Request Processing Notification' to APM BIOS at all for the second case. After adding this hack in PAO, we saw greate improvements about system suspending transition (standby also) on a lot of laptops :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 10:55: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 7764F15560; Wed, 11 Aug 1999 10:54:58 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA05227; Wed, 11 Aug 1999 11:53:01 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA29750; Wed, 11 Aug 1999 11:52:59 -0600 Date: Wed, 11 Aug 1999 11:52:59 -0600 Message-Id: <199908111752.LAA29750@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: nate@mt.sri.com (Nate Williams), "Matthew N. Dodd" , Peter Wemm , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: <199908111744.LAA18270@harmony.village.org> References: <199908111729.LAA29297@mt.sri.com> <199908111724.LAA18087@harmony.village.org> <199908111744.LAA18270@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : stty columns is only effective *AFTER* you have a shell and the box has > : booted. > > Yes I know that, but you seem to be arguing that all terminals have 80 > columns... This is not the case, although many of them do. Most of them do. It is the 'least common denominator' that FreeBSD runs into. More than 132 columns is an exception, as well as less than 80 columns. My point was not changing the boot message to more than 80 columns, like you suggested. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 10:58:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id D7E001553D for ; Wed, 11 Aug 1999 10:58:38 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id TAA00197 for freebsd-current@FreeBSD.ORG; Wed, 11 Aug 1999 19:58:03 +0200 (CEST) (envelope-from olli) Date: Wed, 11 Aug 1999 19:58:03 +0200 (CEST) From: Oliver Fromme Message-Id: <199908111758.TAA00197@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: it's time... Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote in list.freebsd-current: > In message <199908111729.LAA29297@mt.sri.com> Nate Williams writes: > : And you plan on booting FreeBSD on your PDA? > > Yes. I'm already booting NetBSD/hpcmips on it.... But that's another > thread all by itself... As a small sidenote: Most PDAs can be used as (simple) serial consoles, so it's definitely useful to be able to see the bootmessages there. I already tried that with a PalmPilot. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 11: 0:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from metriclient-1.uoregon.edu (metriclient-1.uoregon.edu [128.223.172.1]) by hub.freebsd.org (Postfix) with ESMTP id B0C0A155A5 for ; Wed, 11 Aug 1999 11:00:30 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by metriclient-1.uoregon.edu (8.9.1/8.8.7) id LAA09966; Wed, 11 Aug 1999 11:00:01 -0700 (PDT) Message-ID: <19990811110000.05858@hydrogen.fircrest.net> Date: Wed, 11 Aug 1999 11:00:00 -0700 From: John-Mark Gurney To: Nate Williams Cc: current@FreeBSD.ORG Subject: Re: it's time... References: <199908111724.LAA18087@harmony.village.org> <199908111729.LAA29297@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199908111729.LAA29297@mt.sri.com>; from Nate Williams on Wed, Aug 11, 1999 at 11:29:04AM -0600 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams scribbled this message on Aug 11: > > : The line wrapping stuff I brought back for the EISA bus stuff in -current > > : makes it easy to define the wrap point. If some small number of people > > : want the ability to wrap at 132 or 40 or whatever, I don't think its > > : unreasonable to provide them the knob to tweak in the boot loader. > > > > Despite what nate think about 80 columns, my PDA cannot display more > > than between 30-45 characters, depending on the font, so having a knob > > for that would be useful in the long term. > > And you plan on booting FreeBSD on your PDA? I've booted my FreeBSD box w/ my hp48... and that can't do more than about 34 columns in a sucky 3x5 or 4x5 font... and it works great... :) right now my hp48 is the only serial device that I can get close enough to my server, and I don't have any free slots for a mono or vga card.. -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 11:12:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 37D8C1556B for ; Wed, 11 Aug 1999 11:12:56 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA05497; Wed, 11 Aug 1999 12:12:52 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA00050; Wed, 11 Aug 1999 12:12:37 -0600 Date: Wed, 11 Aug 1999 12:12:37 -0600 Message-Id: <199908111812.MAA00050@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mitsuru IWASAKI Cc: steveo@iol.ie, freebsd-current@FreeBSD.ORG, plm@xs4all.nl Subject: Re: recent apm changes In-Reply-To: <199908111748.CAA10835@tasogare.imasy.or.jp> References: <199908111748.CAA10835@tasogare.imasy.or.jp> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > APM Spec. v1.2 Appendix D - APM Driver Considerations ----- FWIW, the wording here is almost the same as the previous specifications. > When an APM connection exists, the APM BIOS transitions into System > Standby and System Suspend states only when directed to do so by a > call from the APM Driver. The calls to change system states are > invoked by the APM Driver only after the APM BIOS indicates that the > state transition should be made, and the APM Driver has checked with > all APM-aware applications to make sure that it is an appropriate time > to change system states. However, there are three cases where the APM > BIOS may make the system state transition itself. The first case is if > the APM Driver does not pick up a posted Standby Request, Suspend > Request or Critical Suspend Notification event within the 2 second > ~~~~~~~~~~~~~~~~~~~ > (one second plus one second grace period) time limit. The second is > when the APM Driver, after picking up the event, does not respond to a > Standby Request, Suspend Request or Critical Suspend Notification > event with an appropriate Set Power State call within 5 seconds of > ~~~~~~~~~~~~~~~~ > receiving the event. We should have no problems responding in this amount of time in FreeBSD, since we don't (didn't used to?) have any code that should cause significant delay in responding. > The last situation is when the APM Driver has > responded to an event with a Request Processing Set Power call and > does not reply again within another 5 seconds.The CPU is power managed > according to CPU Idle and CPU Busy calls made by the APM Driver to the > APM BIOS. I don't follow this. > ------------------------------------------------------------ > > Last time, we didn't have `Last Request Processing Notification' to > APM BIOS at all for the second case. Huh? I don't see any mention of 'last request processing notification' anywhere above. Also, I don't believe the APM driver responds with a request processing call, since I don't see any reason to in FreeBSD, especially with the number of buggy BIOS's out there. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 11:52:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 66199155E3 for ; Wed, 11 Aug 1999 11:52:02 -0700 (PDT) (envelope-from netchild@Vodix.CS.Uni-SB.de) Received: from work.net.local (maxtnt-067.telip.uni-sb.de [134.96.70.194]) by uni-sb.de (8.9.3/1999070600) with ESMTP id UAA27683 for ; Wed, 11 Aug 1999 20:51:20 +0200 (CEST) X-Authentication-Warning: uni-sb.de: Host maxtnt-067.telip.uni-sb.de [134.96.70.194] claimed to be work.net.local Received: from Vodix.CS.Uni-SB.de (localhost.net.local [127.0.0.1]) by work.net.local (8.9.3/8.9.3) with ESMTP id UAA00795 for ; Wed, 11 Aug 1999 20:50:56 +0200 (CEST) (envelope-from netchild@Vodix.CS.Uni-SB.de) Message-Id: <199908111850.UAA00795@work.net.local> Date: Wed, 11 Aug 1999 20:50:54 +0200 (CEST) From: A.Leidinger@WJPServer.CS.Uni-SB.de Subject: Crash with NFS V2 To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a program which does something like userland-nfs (nfs v2 client). It is able to crash the machine. After compiling a debug kernel the only output I get after the crashdump is: ---snip--- (100) root@ttyp3 # gdb -kernel -se /sys/compile/WORK/kernel.debug -c /var/crash/vmcore.1 IdlePTD 3743744 initial pcb at 2cb960 panic messages: --- dmesg: kvm_read: invalid address (c02bcb50) --- #0 boot (howto=Cannot access memory at address 0xc62e6b54. ) at ../../kern/kern_shutdown.c:291 291 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=Cannot access memory at address 0xc62e6b54. ) at ../../kern/kern_shutdown.c:291 Cannot access memory at address 0xc62e6b4c. ---snip--- - System is -current from august 5th. - "mountd -2 -n" - "nfsd -u" My program does a nfs read call and wants a buffer (readres.readres_u.reply.data.data_val) of 32k to be filled. -> crashed from userland (the program and the nfs server are running on the same machine) The core and the debug kernel are available, feel free to give me some advice how to get more information out of it. ----- There is also a strange behavior in nfs_readdir: I get a segfault with readdir (in libc, something xdr relatet if I remember correctly) if the buffer (readdirres.readdirres_u.reply.entries) is less than 8k+1 [NFS_MAXDATA+1] (on Solaris 2.4 this buffer has to be 257 [NFS_MAXNAMLEN+1] or greater). This one is testet with: - NFS-Server: FreeBSD 3.x, Userland-NFS-Client: Solaris 2.4 - NFS-Server + Userland-NFS-Client (on the same machine): FreeBSD 4-current (some months ago) Bye, Alexander. -- Can I trade this job for what's behind door #2? http://netchild.home.pages.de A.Leidinger+Home @ WJPServer.CS.Uni-SB.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 12:38:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from anch01.customcpu.com (anch01.customcpu.com [198.70.210.44]) by hub.freebsd.org (Postfix) with ESMTP id 94DCB15535 for ; Wed, 11 Aug 1999 12:38:12 -0700 (PDT) (envelope-from mand@alaska.com) Received: from windud- ([207.14.79.52]) by anch01.customcpu.com (Post.Office MTA v3.5.3 release 223 ID# 0-59598U2500L250S0V35) with SMTP id com; Wed, 11 Aug 1999 11:36:29 -0800 Message-Id: <3.0.6.32.19990811113647.0084fa60@customcpu.com> X-Sender: al7oj@customcpu.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 11 Aug 1999 11:36:47 -0800 To: Dag-Erling Smorgrav From: mand@alaska.com Subject: Re: vty3 and 4.0 snap 080799 Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: <"Michael A. Endsley"'s message of "Mon, 09 Aug 1999 06:38:47 -0800"> <37AEE7F7.8EA393DD@customcpu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:45 PM 08/11/1999 +0200, Dag-Erling Smorgrav wrote: >"Michael A. Endsley" writes: >> I just downloaded the latest snap (080799) and tried installing it. >> When getting to the media section and configuring ppp for a ftp install, >> I try going to vty3 (alt-f3). However, that vty is not available. I have >> tried this 3 times now. Is this broken? > >ttyv3 is on Alt-F4. I realized my typing mistake after sending this to the group, but hoped that the "alt-F3" would help. Lets just use alt-f3. To further explain (?): During a fresh install the system uses vty0. When the time comes to finally start downloading (using FTP), a screen is shown telling the person to go use the ALT-F3 keys (vty2) to use term. For me, that key combination is not "active". In fact, just vty1 is available (to view what FreeBSD is doing). I will just download the floppies from a later date (19990808-11). Thanks Mike ps- sorry for some of the generalities...I am just going by memory w/o being able to see the screens. > >DES >-- >Dag-Erling Smorgrav - des@flood.ping.uio.no > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 12:46:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id BDA2E154DE for ; Wed, 11 Aug 1999 12:46:08 -0700 (PDT) (envelope-from lile@stdio.com) Received: from heathers.stdio.com (lile@heathers.stdio.com [199.89.192.5]) by heathers.stdio.com (8.8.8/8.8.8) with ESMTP id PAA14124 for ; Wed, 11 Aug 1999 15:45:46 -0400 (EDT) (envelope-from lile@stdio.com) Date: Wed, 11 Aug 1999 15:45:45 -0400 (EDT) From: Larry Lile To: current@freebsd.org Subject: Re: vty3 and 4.0 snap 080799 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Use alt-F4 for the shell during install. vty0 -> alt-F1 [Install] vty1 -> alt-F2 [Debug] vty2 -> alt-f3 [Inactive] vty3 -> alt-F4 [Shell] PrtScr will cycle through all available vty's. HTH. HAND :) Larry Lile lile@stdio.com On Wed, 11 Aug 1999 mand@alaska.com wrote: > At 02:45 PM 08/11/1999 +0200, Dag-Erling Smorgrav wrote: > >"Michael A. Endsley" writes: > >> I just downloaded the latest snap (080799) and tried installing it. > >> When getting to the media section and configuring ppp for a ftp install, > >> I try going to vty3 (alt-f3). However, that vty is not available. I have > >> tried this 3 times now. Is this broken? > > > >ttyv3 is on Alt-F4. > I realized my typing mistake after sending this to the group, but hoped > that the "alt-F3" would help. > Lets just use alt-f3. > To further explain (?): > During a fresh install the system uses vty0. When the time comes to finally > start downloading (using FTP), a screen is shown telling the person to go > use the ALT-F3 keys (vty2) to use term. For me, that key combination is not > "active". In fact, just vty1 is available (to view what FreeBSD is doing). > I will just download the floppies from a later date (19990808-11). > Thanks > Mike > > ps- sorry for some of the generalities...I am just going by memory w/o > being able to see the screens. > > > > >DES > >-- > >Dag-Erling Smorgrav - des@flood.ping.uio.no > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 13: 9:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (Postfix) with ESMTP id 644B714CD3 for ; Wed, 11 Aug 1999 13:09:05 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from localhost (localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id GAA59159; Thu, 12 Aug 1999 06:07:58 +1000 (EST) (envelope-from andyf@speednet.com.au) Date: Thu, 12 Aug 1999 06:07:57 +1000 (EST) From: Andy Farkas X-Sender: andyf@localhost To: Larry Lile Cc: current@FreeBSD.ORG Subject: Re: vty3 and 4.0 snap 080799 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999, Larry Lile wrote: > Use alt-F4 for the shell during install. > > vty0 -> alt-F1 [Install] > vty1 -> alt-F2 [Debug] > vty2 -> alt-f3 [Inactive] How about we emit a message: "This screen intentionally left blank." :) > vty3 -> alt-F4 [Shell] > > PrtScr will cycle through all available vty's. > > HTH. HAND :) > > Larry Lile > lile@stdio.com > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 14:12:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from megadodo.segNET.COM (megadodo.segNET.COM [206.34.181.3]) by hub.freebsd.org (Postfix) with ESMTP id 21A6C14E38; Wed, 11 Aug 1999 14:12:24 -0700 (PDT) (envelope-from adams@digitalspark.net) Received: from arc0a97.wrj.sover.net (arc0a97.wrj.sover.net [209.198.95.97]) by megadodo.segNET.COM (8.9.1a/8.8.5) with ESMTP id RAA20865; Wed, 11 Aug 1999 17:09:45 -0400 (EDT) Date: Wed, 11 Aug 1999 17:12:43 +0000 (GMT) From: Adam Strohl To: Warner Losh Cc: "Matthew N. Dodd" , Nate Williams , Peter Wemm , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: <199908111724.LAA18087@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999, Warner Losh wrote: > It also would allow one to kick the VGA display into 132 columns in > the boot loader and have more of a chance to get more of the boot > process on the screen. syscons already supports parts of this... I was just reading through the thread again, and I was thinking about a Sun style boot where the screen is kicked into the VESA mode of your choice, we could have a FreeBSD daemon displaying in the upper left corner, etc. > There is no reason to hard code 80 into the kernel. Otherwise one > could argue why have stty columns at all :-). I have to agree with this, flexibility == AGoodThing(TM). > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 14:32: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from anch01.customcpu.com (anch01.customcpu.com [198.70.210.44]) by hub.freebsd.org (Postfix) with ESMTP id D187315618 for ; Wed, 11 Aug 1999 14:32:00 -0700 (PDT) (envelope-from mand@alaska.com) Received: from windud- ([207.14.79.55]) by anch01.customcpu.com (Post.Office MTA v3.5.3 release 223 ID# 0-59598U2500L250S0V35) with SMTP id com; Wed, 11 Aug 1999 13:30:44 -0800 Message-Id: <3.0.6.32.19990811133102.00808100@customcpu.com> X-Sender: al7oj@customcpu.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 11 Aug 1999 13:31:02 -0800 To: Dag-Erling Smorgrav From: mand@alaska.com Subject: Re: vty3 and 4.0 snap 080799 Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: <"Michael A. Endsley"'s message of "Mon, 09 Aug 1999 06:38:47 -0800"> <37AEE7F7.8EA393DD@customcpu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just downloaded the latest snap floppies (19990811), and tried installing again. My original post (as shown) was/is correct! Under the "options" screen to set the media type, I choose ftp...(4.0-current). After typing the ip address, host name, etc, I then go through the steps for ppp (username, password, etc). After typing the phone number to my ISP, I get the message that ppp is started on VTY3 (type ALT-F3). It is at this screen that VTY3 (or ALT-F3) is not active/available! The only other vty that is available is vty1 (alt-f2) for monitoring. BTW- this last time, I used the "CLI" screen to configure my pnp modem in case that would help. It didn't ! Thanks again, Mike At 02:45 PM 08/11/1999 +0200, Dag-Erling Smorgrav wrote: >"Michael A. Endsley" writes: >> I just downloaded the latest snap (080799) and tried installing it. >> When getting to the media section and configuring ppp for a ftp install, >> I try going to vty3 (alt-f3). However, that vty is not available. I have >> tried this 3 times now. Is this broken? > >ttyv3 is on Alt-F4. > >DES >-- >Dag-Erling Smorgrav - des@flood.ping.uio.no > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 16:26:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from amukta.gci.net (amukta.gci.net [208.138.130.216]) by hub.freebsd.org (Postfix) with ESMTP id B5E5714C04 for ; Wed, 11 Aug 1999 16:26:33 -0700 (PDT) (envelope-from mandm@alaska.com) Received: from [209.165.149.242] ([209.165.149.242]) by amukta.gci.net (Netscape Messaging Server 4.04 Jul 21 1999 18:33:18) with SMTP id FGBQB601.Y2M for ; Wed, 11 Aug 1999 15:23:30 -0800 Message-Id: <3.0.6.32.19990811152407.00840710@mail.gci.net> X-Sender: mandm@mail.gci.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 11 Aug 1999 15:24:07 -0800 To: freebsd-current@FreeBSD.ORG From: mandm@alaska.com Subject: Re: vty3 and 4.0 snap 080799 In-Reply-To: References: <"Michael A. Endsley"'s message of "Mon, 09 Aug 1999 06:38:47 -0800"> <37AEE7F7.8EA393DD@customcpu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I should have also stated that I tried all the other "F" keys also. The only vty that is available/active is vty1 for debugging. Every other F-key gets the "beep". HTH in solving my problem fwiw dept.- I have been using FreeBSD since 2.21-R To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 16:35:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id 58B651564B for ; Wed, 11 Aug 1999 16:35:15 -0700 (PDT) (envelope-from lile@stdio.com) Received: from heathers.stdio.com (lile@heathers.stdio.com [199.89.192.5]) by heathers.stdio.com (8.8.8/8.8.8) with ESMTP id TAA22748; Wed, 11 Aug 1999 19:32:26 -0400 (EDT) (envelope-from lile@stdio.com) Date: Wed, 11 Aug 1999 19:32:25 -0400 (EDT) From: Larry Lile To: mandm@alaska.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: vty3 and 4.0 snap 080799 In-Reply-To: <3.0.6.32.19990811152407.00840710@mail.gci.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The shell is not started until after the install starts, ie when the ftp connects (the dists start getting untarred.) Larry Lile On Wed, 11 Aug 1999 mandm@alaska.com wrote: > I should have also stated that I tried all the other "F" keys also. > The only vty that is available/active is vty1 for debugging. Every other > F-key gets the "beep". > HTH in solving my problem > > fwiw dept.- I have been using FreeBSD since 2.21-R > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 16:38: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from amukta.gci.net (amukta.gci.net [208.138.130.216]) by hub.freebsd.org (Postfix) with ESMTP id 7735615660 for ; Wed, 11 Aug 1999 16:37:57 -0700 (PDT) (envelope-from mandm@alaska.com) Received: from [209.165.149.242] ([209.165.149.242]) by amukta.gci.net (Netscape Messaging Server 4.04 Jul 21 1999 18:33:18) with SMTP id FGBQXJ00.M2I; Wed, 11 Aug 1999 15:36:55 -0800 Message-Id: <3.0.6.32.19990811153731.008335a0@mail.gci.net> X-Sender: mandm@mail.gci.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 11 Aug 1999 15:37:31 -0800 To: Larry Lile From: mandm@alaska.com Subject: Re: vty3 and 4.0 snap 080799 Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: <3.0.6.32.19990811152407.00840710@mail.gci.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, something is wrong with what I am trying to say :) After entering the phone number to my ISP, the message screen pops up saying "...type ALT-F3..." to go to that vty. A person is supposed to go to that vty and then either type "dial" or "term". It is at this time that the vty (alt-f3) is not active/available! In other words, how do I type "dial" or "term" if I can't get to that vty? HTH, Mike At 07:32 PM 08/11/1999 -0400, Larry Lile wrote: > >The shell is not started until after the install starts, ie when >the ftp connects (the dists start getting untarred.) > >Larry Lile > >On Wed, 11 Aug 1999 mandm@alaska.com wrote: > >> I should have also stated that I tried all the other "F" keys also. >> The only vty that is available/active is vty1 for debugging. Every other >> F-key gets the "beep". >> HTH in solving my problem >> >> fwiw dept.- I have been using FreeBSD since 2.21-R >> >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message >> > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 17:13:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc2.on.home.com (ha1.rdc2.on.home.com [24.9.0.15]) by hub.freebsd.org (Postfix) with ESMTP id D215614CA0 for ; Wed, 11 Aug 1999 17:13:09 -0700 (PDT) (envelope-from street@iname.com) Received: from mired.eh.local ([24.66.100.55]) by mail.rdc2.on.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19990812001201.XMXT12218.mail.rdc2.on.home.com@mired.eh.local>; Wed, 11 Aug 1999 17:12:01 -0700 Received: (from kws@localhost) by mired.eh.local (8.9.3/8.9.3) id UAA04481; Wed, 11 Aug 1999 20:12:00 -0400 (EDT) (envelope-from kws) To: Soren Schmidt Cc: geoffr@is.co.za, brian@pobox.com, current@FreeBSD.ORG Subject: Re: ATA - Trouble mounting secondary master References: <199908110653.IAA56765@freebsd.dk> From: Kevin Street Date: 11 Aug 1999 20:11:59 -0400 In-Reply-To: Soren Schmidt's message of "Wed, 11 Aug 1999 08:53:24 +0200 (CEST)" Message-ID: <87hfm5vovk.fsf@mired.eh.local> Lines: 33 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "20 Minutes to Nikko" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt writes: > It seems Geoff Rehmet wrote: > > Brian McGroarty writes : > > > In using the ATA driver, I'm unable to automatically mount a > > > partition on a master drive on the secondary controller. fsck > > > complains that device rwd2s1e isn't configured and exists. > > > Immediately mounting by hand works perfectly. > > I had exactly the same problem, although it manifested itself with a > > secondary master or slave. It went away a few weeks ago, and I > > was never able to make any sensible progress in tracking the problem > > down. > > Hmm, damn, after the problem went away for Geoff I thought it to be > solved since I've never heard of it anywhere else, and I cant reproduce > it here no matter what I try. > Does it help eany if you only has the root partition use the wd dev > and have the rest use the prober ad dev entries ?? It could be some > artifact from this... I tried with the ad dev entries for my problem as well with no improvement. I've also tried using: dd if=/dev/ad0s6 of=/dev/null bs=512 count=1 as the first access to one of the failing drives (ad0). The first dd fails with device not configured, but any subsequent access works fine. It seems it's left in an odd state by the driver start up, but all it takes is a read to get it sorted out again. Any thoughts on how we can help debug this? -- Kevin Street street@iname.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 17:35:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id C5B7E15610 for ; Wed, 11 Aug 1999 17:35:08 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA79109; Wed, 11 Aug 1999 17:34:08 -0700 (PDT) (envelope-from dillon) Date: Wed, 11 Aug 1999 17:34:08 -0700 (PDT) From: Matthew Dillon Message-Id: <199908120034.RAA79109@apollo.backplane.com> To: A.Leidinger@WJPServer.CS.Uni-SB.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: Crash with NFS V2 References: <199908111850.UAA00795@work.net.local> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Hi, : :I have a program which does something like userland-nfs (nfs v2 client). :It is able to crash the machine. After compiling a debug kernel the :only output I get after the crashdump is: : :---snip--- :(100) root@ttyp3 # gdb -kernel -se /sys/compile/WORK/kernel.debug -c /var/crash/vmcore.1 :IdlePTD 3743744 :initial pcb at 2cb960 :panic messages: :--- :dmesg: kvm_read: invalid address (c02bcb50) :--- :#0 boot (howto=Cannot access memory at address 0xc62e6b54. :) at ../../kern/kern_shutdown.c:291 :291 dumppcb.pcb_cr3 = rcr3(); :(kgdb) bt :#0 boot (howto=Cannot access memory at address 0xc62e6b54. :) at ../../kern/kern_shutdown.c:291 :Cannot access memory at address 0xc62e6b4c. :---snip--- : : - System is -current from august 5th. : - "mountd -2 -n" : - "nfsd -u" : :My program does a nfs read call and wants a buffer :(readres.readres_u.reply.data.data_val) of 32k to be filled. : -> crashed from userland :(the program and the nfs server are running on the same machine) : :The core and the debug kernel are available, feel free to give me some :advice how to get more information out of it. : :----- :There is also a strange behavior in nfs_readdir: : :I get a segfault with readdir (in libc, something xdr relatet if I :remember correctly) if the buffer :(readdirres.readdirres_u.reply.entries) is less than 8k+1 :[NFS_MAXDATA+1] (on Solaris 2.4 this buffer has to be 257 :[NFS_MAXNAMLEN+1] or greater). :This one is testet with: : - NFS-Server: FreeBSD 3.x, Userland-NFS-Client: Solaris 2.4 : - NFS-Server + Userland-NFS-Client (on the same machine): FreeBSD : 4-current (some months ago) : :Bye, :Alexander. The problem regarding the readdir seg faults should be fixed in both STABLE and CURRENT if you update your source tree. I don't know about the first problem... maybe compile up your kernel DDB and do a 'trace' when it panics - record the original panic message as well as the trace. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 18: 8:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from amukta.gci.net (amukta.gci.net [208.138.130.216]) by hub.freebsd.org (Postfix) with ESMTP id 94C3D14D3E for ; Wed, 11 Aug 1999 18:08:06 -0700 (PDT) (envelope-from mandm@alaska.com) Received: from [209.165.149.254] ([209.165.149.254]) by amukta.gci.net (Netscape Messaging Server 4.04 Jul 21 1999 18:33:18) with SMTP id FGBV3B01.I2S for ; Wed, 11 Aug 1999 17:06:47 -0800 Message-Id: <3.0.6.32.19990811170724.007a2c90@mail.gci.net> X-Sender: mandm@mail.gci.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 11 Aug 1999 17:07:24 -0800 To: freebsd-current@FreeBSD.ORG From: "Michael A. Endsley" Subject: vty3 problem solved, but.... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I started a fresh installation with todays floppies. During the installation, I monitored vty1. What I found out is that ifconfig doesn't recognize/config either my modem or cuaa0(ppp0). After clicking "YES" at the "Do you want to try DHCP configuration of the interface" screen, I switched to ALT-F2. It showed: "ifconfig: interface ppp0 does not exist ppp0: not found exiting" However, during boot-up, I hit a key to bring up the commands, and typed "pnpscan". I then typed "autoboot". At the next screen, I used the "CLI" mode to configure my sound card and modem. For the modem, I used "pnp 2 0 enable os irq04 port0 0x3f8". What else can I do? Again, thanks Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 18:11:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc2.on.home.com (ha1.rdc2.on.home.com [24.9.0.15]) by hub.freebsd.org (Postfix) with ESMTP id 246FE14D3E for ; Wed, 11 Aug 1999 18:11:16 -0700 (PDT) (envelope-from street@iname.com) Received: from mired.eh.local ([24.66.100.55]) by mail.rdc2.on.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19990812010933.ZENA12218.mail.rdc2.on.home.com@mired.eh.local>; Wed, 11 Aug 1999 18:09:33 -0700 Received: (from kws@localhost) by mired.eh.local (8.9.3/8.9.3) id VAA00530; Wed, 11 Aug 1999 21:09:33 -0400 (EDT) (envelope-from kws) To: Soren Schmidt Cc: geoffr@is.co.za, brian@pobox.com, current@FreeBSD.ORG Subject: Re: ATA - Trouble mounting secondary master References: <199908110653.IAA56765@freebsd.dk> <87hfm5vovk.fsf@mired.eh.local> From: Kevin Street Date: 11 Aug 1999 21:09:32 -0400 In-Reply-To: Kevin Street's message of "11 Aug 1999 20:11:59 -0400" Message-ID: <87yafhn6sz.fsf@mired.eh.local> Lines: 28 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "20 Minutes to Nikko" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kevin Street writes: > Soren Schmidt writes: > > Hmm, damn, after the problem went away for Geoff I thought it to be > > solved since I've never heard of it anywhere else, and I cant reproduce > > it here no matter what I try. > > Does it help eany if you only has the root partition use the wd dev > > and have the rest use the prober ad dev entries ?? It could be some > > artifact from this... > > I tried with the ad dev entries for my problem as well with no > improvement. I've also tried using: > dd if=/dev/ad0s6 of=/dev/null bs=512 count=1 > as the first access to one of the failing drives (ad0). > The first dd fails with device not configured, but any subsequent > access works fine. It seems it's left in an odd state by the driver > start up, but all it takes is a read to get it sorted out again. More on this. I just booted with -v and now when I do the first dd I see: ad0: invalid primary partition table: no magic and the same on ad2 when the swapon fails. So how do I get the magic back into my relationship with my drives? -- Kevin Street street@iname.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 18:32:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 04ABF14E0D for ; Wed, 11 Aug 1999 18:32:43 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb47.imasy.or.jp [202.227.24.175]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id KAA22707; Thu, 12 Aug 1999 10:31:25 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199908120131.KAA22707@tasogare.imasy.or.jp> To: nate@mt.sri.com Cc: iwasaki@jp.freebsd.org, steveo@iol.ie, freebsd-current@FreeBSD.ORG, plm@xs4all.nl Subject: Re: recent apm changes In-Reply-To: Your message of "Wed, 11 Aug 1999 12:12:37 -0600" <199908111812.MAA00050@mt.sri.com> References: <199908111812.MAA00050@mt.sri.com> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 12 Aug 1999 10:35:08 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 88 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Nate. I'm sorry if my poor english troubled you. > We should have no problems responding in this amount of time in FreeBSD, > since we don't (didn't used to?) have any code that should cause > significant delay in responding. My understanding on system suspend code in FreeBSD is that once APM driver get a system suspend request event from the BIOS, the driver is hurry to put system into suspend state (execute suspend hooks and call set power state function for suspend) as soon as possible without any responses to the BIOS. I think that this style is cool, I like, and no response to the BIOS is not violating the APM specification at all, but there are many BIOSes expecting response from driver. In Linux and NetBSD, they have last request processing notification to the BIOS before transition into suspend state. I guess they obtained the same conclusion to support various BIOS implementations including buggy and bogus BIOSes. That's why `suspending on Linux is OK, but on FreeBSD' like phenomenon is there.... I'd like solve this if possible and need your help or support. From Linux code: static void do_apm_timer(unsigned long unused) { int err; static int pending_count = 0; if (((standbys_pending > 0) || (suspends_pending > 0)) && (apm_bios_info.version > 0x100) && (pending_count-- <= 0)) { pending_count = 4; err = apm_set_power_state(APM_STATE_BUSY); if (err) apm_error("busy", err); } From NetBSD code: static void apm_event_handle(sc, regs) struct apm_softc *sc; struct bioscallregs *regs; { int error; struct bioscallregs nregs; switch(regs->bx) { case APM_USER_STANDBY_REQ: DPRINTF(APMDEBUG_EVENTS, ("apmev: user standby request\n")); if (apm_do_standby) { if (apm_record_event(sc, regs->bx)) apm_userstandbys++; apm_op_inprog++; (void)apm_set_powstate(APM_DEV_ALLDEVS, APM_LASTREQ_INPROG); } else { (void)apm_set_powstate(APM_DEV_ALLDEVS, APM_LASTREQ_REJECTED); /* in case BIOS hates being spurned */ apm_powmgt_enable(1); } break; > > Last time, we didn't have `Last Request Processing Notification' to > > APM BIOS at all for the second case. > > Huh? I don't see any mention of 'last request processing notification' > anywhere above. Also, I don't believe the APM driver responds with a Ah, details are described in `4. Advanced Power Managerment Software Interface - 4.6.8 Set Power State'. `an appropriate Set Power State call' includes 'last request processing notification' too. They say: Set Power State entry codes of CX=0004h and CX=0005h are used by the APM Driver to respond to requests from the system BIOS for the global Standby and Suspend states. The APM Driver uses the Last Request Processing Notification (0004h) to indicate that it is currently in the process of determining whether or not to reject the request. This notification must be sent at least once every five seconds after the APM driver receives the request by calling Get Power Management Event. The APM driver must eventually end this "busy" state by accepting the request, (calling Set Power State with the appropriate state) or by rejecting the request using CX=0005h. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 19: 2:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from xenetserver.harz.de (xenetserver.harz.de [193.159.181.125]) by hub.freebsd.org (Postfix) with ESMTP id B138C14E5F for ; Wed, 11 Aug 1999 19:02:13 -0700 (PDT) (envelope-from frank@vogon.agala.harz.de) Received: (from uucp@localhost) by xenetserver.harz.de (8.9.1/8.9.1) with UUCP id EAA07449 for freebsd-current@freebsd.org; Thu, 12 Aug 1999 04:01:48 +0200 (CEST) Received: (from frank@localhost) by vogon.agala.harz.de (8.9.3/8.8.8) id AAA45838 for freebsd-current@freebsd.org; Thu, 12 Aug 1999 00:02:06 +0200 (CEST) (envelope-from frank) Date: Thu, 12 Aug 1999 00:02:06 +0200 From: "Frank J. Beckmann" To: freebsd-current@freebsd.org Subject: isa shared interupts Message-ID: <19990812000205.A41237@vogon.agala.harz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i X-Address: Frank J. Beckmann, Steinkampring 16, D-38667 Bad Harzburg X-Phone: +49-5322-80008 X-Fax: +49-5322-80082 X-PGP-Fingerprint-1: (1024R/66DC397D) = 25 34 D7 8A 69 04 12 CA 6E 55 DD 63 F6 A3 0E 06 X-PGP-Fingerprint-2: (1024D/46DE66CA) = 7D06 0DFB 23D9 01BA 11EB 88C3 DE8C C167 46DE 66CA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, does current current support isa cards that use shared interupts on the card (eg. multi sio cards) again? Frank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 19:23:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 21D5914D58 for ; Wed, 11 Aug 1999 19:23:53 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA22410; Wed, 11 Aug 1999 19:21:56 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: mandm@alaska.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: vty3 and 4.0 snap 080799 In-reply-to: Your message of "Wed, 11 Aug 1999 15:24:07 -0800." <3.0.6.32.19990811152407.00840710@mail.gci.net> Date: Wed, 11 Aug 1999 19:21:56 -0700 Message-ID: <22406.934424516@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It sounds like ppp is simply exiting immediately. I'll turn debugging on and give it a shot myself; perhaps somebody broke something. - Jordan > I should have also stated that I tried all the other "F" keys also. > The only vty that is available/active is vty1 for debugging. Every other > F-key gets the "beep". > HTH in solving my problem > > fwiw dept.- I have been using FreeBSD since 2.21-R > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 19:58:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id 55CC114D46 for ; Wed, 11 Aug 1999 19:58:12 -0700 (PDT) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id EAA00496; Thu, 12 Aug 1999 04:57:07 +0200 (CEST) To: current@freebsd.org Subject: DEV_MODULE doesn't support dynamic major numbers any longer? Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 12 Aug 1999 04:57:07 +0200 Message-ID: <5lyafhyad8.fsf@assaris.sics.se> Lines: 17 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems to be the case that the possibility of specifying a major number of NOMAJ in DEV_MODULE has vanished. cdevsw_add() doesn't have any code for handling NOMAJ any longer. (The only mention I can find of NOMAJ in a -current kernel tree from 19990811 are these: ./alpha/alpha/promcons.c:284:DEV_MODULE(prom, CDEV_MAJOR, NOMAJ, prom_cdevsw, 0, 0); ./sys/param.h:128:#define NOMAJ 256 /* non-existent device */ which makes me wonder how the promcons works...). Is this intentional that there isn't there any support for dynamically assigning major device numbers or is it an accident that I should go and rectify? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 20:37:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1BD0514CF3; Wed, 11 Aug 1999 20:37:34 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA22083; Wed, 11 Aug 1999 21:35:22 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA01529; Wed, 11 Aug 1999 21:35:04 -0600 (MDT) Message-Id: <199908120335.VAA01529@harmony.village.org> To: nate@mt.sri.com (Nate Williams) Subject: Re: it's time... Cc: "Matthew N. Dodd" , Peter Wemm , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Wed, 11 Aug 1999 11:29:04 MDT." <199908111729.LAA29297@mt.sri.com> References: <199908111729.LAA29297@mt.sri.com> <199908111724.LAA18087@harmony.village.org> Date: Wed, 11 Aug 1999 21:35:04 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After taking a break from this discussion, I do think that I like the idea of wrapping boot messages in a sane way at column n (= 80 by default) so long as one knows where messages from one device end and the next one begin. I'd also oppose things like foo0: ...... irq foo0: 9 as opposed to foo0: ...... foo0: irq 9 Unless there were so many that this couldn't be avoided... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 20:56:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 3B46014D62 for ; Wed, 11 Aug 1999 20:56:20 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id XAA57779 for ; Wed, 11 Aug 1999 23:55:44 -0400 (EDT) Message-Id: <199908120355.XAA57779@cs.rpi.edu> To: current@freebsd.org Subject: IBM ThinkPad 600E with cardbus EtherJet 10/100 :) Date: Wed, 11 Aug 1999 23:55:43 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok... needless to say, I am having problems... 1: any access to the serial port (/dev/cuaa0) locks the machine. 2: I cannot get the ethernet card to work. 2a: It is sort-a recognized by the system, It senses the insert and remove, but it cannot get the CIS. I remember reading somewhere that the CIS on these cards is 'somewhere else' and you can tell pccardd where that is. 2b: I believe that this is in reality a tulip card. I am in no way opposed to beta software, and I will code as need be, I just need to know where things already are before I get my feet wet. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 21: 0:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 2B90914C15; Wed, 11 Aug 1999 21:00:36 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id XAA82186; Wed, 11 Aug 1999 23:58:20 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Wed, 11 Aug 1999 23:58:19 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Warner Losh Cc: "Matthew N. Dodd" , Peter Wemm , Cameron Grant , multimedia@FreeBSD.org, current@FreeBSD.org Subject: Re: it's time... In-Reply-To: <199908111603.KAA17583@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999, Warner Losh wrote: > > No! At some point they should use a facility similar to solaris/sysv > where they don't display, but do make it into the dmesg buffer... > > Warner > What in the world would be the point of doing this? What would be so great about not seeing the system boot up? Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 21:33:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 10DFB14DD6; Wed, 11 Aug 1999 21:33:11 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id AAA11963; Thu, 12 Aug 1999 00:32:04 -0400 (EDT) Date: Thu, 12 Aug 1999 00:32:03 -0400 (EDT) From: "Matthew N. Dodd" To: Warner Losh Cc: Nate Williams , Peter Wemm , Cameron Grant , multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: <199908120335.VAA01529@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999, Warner Losh wrote: > After taking a break from this discussion, I do think that I like the > idea of wrapping boot messages in a sane way at column n (= 80 by > default) so long as one knows where messages from one device end and > the next one begin. > > I'd also oppose things like > > foo0: ...... irq > foo0: 9 > > as opposed to > > foo0: ...... > foo0: irq 9 > > Unless there were so many that this couldn't be avoided... check out eisa_reg_print() and eisa_print_child() in sys/i386/eisa/eisaconf.c Sanity in output is a good thing. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 21:34: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 0FBCB156E7; Wed, 11 Aug 1999 21:33:56 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id AAA11969; Thu, 12 Aug 1999 00:34:01 -0400 (EDT) Date: Thu, 12 Aug 1999 00:34:01 -0400 (EDT) From: "Matthew N. Dodd" To: "Brian F. Feldman" Cc: Warner Losh , Peter Wemm , Cameron Grant , multimedia@FreeBSD.org, current@FreeBSD.org Subject: Re: it's time... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999, Brian F. Feldman wrote: > What in the world would be the point of doing this? What would be so > great about not seeing the system boot up? The same reason that when you type 'cp foo /tmp/' it doesn't say '1 file copied, 3425 bytes.' or other nonesense. If nothings wrong then print nothing. Granted, you and I would have our 'boot_verbose' envar set to '1' or '2' or something that gave us the correct amount of feedback we've grown acustom to. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 22:16:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8B90E14D81 for ; Wed, 11 Aug 1999 22:16:08 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA22364; Wed, 11 Aug 1999 23:14:21 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA02076; Wed, 11 Aug 1999 23:14:06 -0600 (MDT) Message-Id: <199908120514.XAA02076@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: it's time... Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 12 Aug 1999 00:32:03 EDT." References: Date: Wed, 11 Aug 1999 23:14:06 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [[ cc trimmed. ]] In message "Matthew N. Dodd" writes: : check out eisa_reg_print() and eisa_print_child() in : sys/i386/eisa/eisaconf.c : : Sanity in output is a good thing. Agreed. I like what I see there. Maybe it is time to hoist something like that into bus_subr.c Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 22:16:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from tim.Desert.NET (tim.Desert.NET [207.182.32.20]) by hub.freebsd.org (Postfix) with ESMTP id ADB2015722 for ; Wed, 11 Aug 1999 22:16:10 -0700 (PDT) (envelope-from tim@tim.Desert.NET) Received: (from tim@localhost) by tim.Desert.NET (8.9.3/8.9.3) id WAA70880 for freebsd-current@freebsd.org; Wed, 11 Aug 1999 22:12:42 -0700 (MST) (envelope-from tim) Date: Wed, 11 Aug 1999 22:12:42 -0700 From: Thimble Smith To: FreeBSD-current List Subject: Bus error in isatty() from /usr/lib/libc.so.3 Message-ID: <19990811221242.B70843@desert.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. I have a reproducable problem which gdb says is ending up at 0x2818d862 in isatty() from /usr/lib/libc.so.3. A full back trace is below. If this is a problem in FreeBSD, I'm very glad to do any experiments that might be helpful. If it's a problem somewhere else, any pointers on what I might do next would be great. Thanks, Tim How to repeat: I installed MySQL 3.23.2, then DBI-1.11. I compiled Msql-Mysql-modules-1.2200, and ran the test suite. All but the first test dumped core, all with this same error. This is with -CURRENT as of Aug 10 @ 7AM (GMT). I did a complete make buildworld; make installworld;, then I recompiled the kernel. tim@threads$ uname -a FreeBSD threads.polyesthetic.org 4.0-CURRENT FreeBSD 4.0-CURRENT #11: Wed Aug 11 08:57:53 MST 1999 root@threads.polyesthetic.org:/usr/src/sys/compile/THREADS i386 tim@threads:/usr/local/src/Msql-Mysql-modules-1.2200/mysql$ LD_LIBRARY_PATH=`pwd`/../blib/arch/auto/DBD/mysql gdb /usr/bin/perl GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... (gdb) run -I../blib/lib t/10dsnlist.t Starting program: /usr/bin/perl -I../blib/lib t/10dsnlist.t (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... Driver is mysql 1..3 (no debugging symbols found)...(no debugging symbols found)... _login('database=test' 'tim' 'ign0rant') (no debugging symbols found)... Program received signal SIGBUS, Bus error. 0x2818d862 in isatty () from /usr/lib/libc.so.3 (gdb) back #0 0x2818d862 in isatty () from /usr/lib/libc.so.3 #1 0x2818db22 in isatty () from /usr/lib/libc.so.3 #2 0x2818e1de in malloc () from /usr/lib/libc.so.3 #3 0x28236e88 in _thread_fd_table_init () from /usr/lib/libc_r.so.4 #4 0x28238056 in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4 #5 0x28248498 in bind () from /usr/lib/libc_r.so.4 #6 0x2818eeb7 in .cerror () from /usr/lib/libc.so.3 #7 0x28238056 in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4 #8 0x28248498 in bind () from /usr/lib/libc_r.so.4 #9 0x2818eeb7 in .cerror () from /usr/lib/libc.so.3 #10 0x28238056 in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4 #26905 0x28238056 in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4 #26906 0x28248498 in bind () from /usr/lib/libc_r.so.4 #26907 0x2818eeb7 in .cerror () from /usr/lib/libc.so.3 #26908 0x281dbb95 in my_net_init (net=0x8057c54, nettype=NET_TYPE_SOCKET, fd=5, pipe=0x0) at net.c:137 #26909 0x281d97be in mysql_real_connect (mysql=0x8057c54, host=0x281e5bf0 "localhost", user=0x81283d0 "tim", passwd=0x8128650 "ign0rant", db=0x8108650 "test", port=0, unix_socket=0x281e5b80 "/tmp/mysql.sock", client_flag=0) at libmysql.c:1194 #26910 0x281c0ba2 in mysql_dr_connect () from /usr/local/src/Msql-Mysql-modules-1.2200/mysql/../blib/arch/auto/DBD/mysql/mysql.so #26911 0x281c130e in _MyLogin () from /usr/local/src/Msql-Mysql-modules-1.2200/mysql/../blib/arch/auto/DBD/mysql/mysql.so #26912 0x281c139d in mysql_db_login () from /usr/local/src/Msql-Mysql-modules-1.2200/mysql/../blib/arch/auto/DBD/mysql/mysql.so #26913 0x281c90cd in XS_DBD__mysql__db__login () from /usr/local/src/Msql-Mysql-modules-1.2200/mysql/../blib/arch/auto/DBD/mysql/mysql.so #26914 0x280af0b5 in Perl_pp_entersub () from /usr/lib/libperl.so.3 #26915 0x28079d69 in Perl_runops_standard () from /usr/lib/libperl.so.3 #26916 0x280e0519 in perl_call_sv () from /usr/lib/libperl.so.3 #26917 0x281b16a5 in XS_DBI_dispatch () from /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/DBI/DBI.so #26918 0x280af0b5 in Perl_pp_entersub () from /usr/lib/libperl.so.3 #26919 0x28079d69 in Perl_runops_standard () from /usr/lib/libperl.so.3 #26920 0x280dfd6e in perl_run () from /usr/lib/libperl.so.3 #26921 0x8048da8 in perl_free () #26922 0x8048cd5 in perl_free () (gdb) Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration: Platform: osname=freebsd, osvers=4.0-current, archname=i386-freebsd uname='freebsd freefall.freebsd.org 4.0-current freebsd 4.0-current #0: $Date: 1999/05/05 19:09:48 $' hint=recommended, useposix=true, d_sigaction=define usethreads=undef useperlio=undef d_sfio=undef Compiler: cc='cc', optimize='undef', gccversion=egcs-2.91.66 19990314 (egcs-1.1.2 release) cppflags='' ccflags ='' stdchar='char', d_stdstdio=undef, usevfork=true intsize=4, longsize=4, ptrsize=4, doublesize=8 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 alignbytes=4, usemymalloc=n, prototype=define Linker and Libraries: ld='cc', ldflags ='-Wl,-E' libpth=/usr/lib libs=-lm -lc -lcrypt libc=/usr/lib/libc.so, so=so, useshrplib=true, libperl=libperl.so.3 Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' ' cccdlflags='-DPIC -fpic', lddlflags='-shared' Characteristics of this binary (from libperl): Built under freebsd Compiled at Aug 10 1999 12:10:48 @INC: /usr/libdata/perl/5.00503/mach /usr/libdata/perl/5.00503 /usr/local/lib/perl5/site_perl/5.005/i386-freebsd /usr/local/lib/perl5/site_perl/5.005 . Kernel config file: =================== # THREADS -- 586 w/ IDE machine i386 cpu I586_CPU ident THREADS maxusers 32 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores controller isa0 controller pnp0 # PnP support for ISA controller eisa0 controller pci0 # Floppy drives controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 # IDE controller and disks controller wdc0 at isa? port IO_WD1 irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port IO_WD2 irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 # ATAPI devices on wdc? device wcd0 #IDE CD-ROM # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? disable flags 0x31 # Advanced Power Management # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 irq 7 controller ppbus0 # Parallel port bus (required) device lpt0 # Printer # PCI Ethernet NICs. device al0 # ADMtek AL981 (``Comet'') device ax0 # ASIX AX88140A device de0 # DEC/Intel DC21x4x (``Tulip'') device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) device mx0 # Macronix 98713/98715/98725 (``PMAC'') device pn0 # Lite-On 82c168/82c169 (``PNIC'') device rl0 # RealTek 8129/8139 device tl0 # Texas Instruments ThunderLAN device tx0 # SMC 9432TX (83c170 ``EPIC'') device vr0 # VIA Rhine, Rhine II device vx0 # 3Com 3c590, 3c595 (``Vortex'') device wb0 # Winbond W89C840F device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. # The probe order of these is presently determined by i386/isa/isa_compat.c. device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 device ep0 at isa? port 0x300 irq 10 device ex0 at isa? port? irq? device fe0 at isa? port 0x300 irq ? device le0 at isa? port 0x300 irq 5 iomem 0xd0000 device lnc0 at isa? port 0x280 irq 10 drq 0 device cs0 at isa? port 0x300 irq ? # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun 1 # Packet tunnel, for ppp(1) pseudo-device pty 16 # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the legal and administrative consequences of enabling this! pseudo-device bpf 4 #Berkeley packet filter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 22:29:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 4A58314E07 for ; Wed, 11 Aug 1999 22:29:30 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id BAA12604; Thu, 12 Aug 1999 01:29:33 -0400 (EDT) Date: Thu, 12 Aug 1999 01:29:32 -0400 (EDT) From: "Matthew N. Dodd" To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: <199908120514.XAA02076@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999, Warner Losh wrote: > In message "Matthew N. Dodd" writes: > : check out eisa_reg_print() and eisa_print_child() in > : sys/i386/eisa/eisaconf.c > : > : Sanity in output is a good thing. > > Agreed. I like what I see there. Maybe it is time to hoist something > like that into bus_subr.c Lets define exactly what we want before we start our charge. What should be printed? device ID attachment point resource reservation device additional When should it be printed? bootverbose levels? How should it printed? ???N: on ???N ... or... Since we've got things partway tied up with new_bus, maybe we should complete the job, and define a device method for printing out the device additional information so it can be dispatched from a single place. How are we going to enforce the use of this 'pretty printer'? Should we embed this logic in device_printf()? This would be practical if our goal were not only impose order on the probe/attach messages but also anything a driver printed (nothing more annoying that stray error messages for which the issuing device is unknown.) I'm not sure this is our goal at this time? Will we ever have such a goal? I see our goal as follows. 1. one unified format for devce probe/attach ammouncments. 2. the ability to control the amount of information printed during the device probe/attach. Anyhow, just trying to stir up some ideas here; please don't take any of my statements as an indication of intended course. I really don't have any good answers at this point and would like to hear the opinions of others. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 11 22:45:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from mercury.is.co.za (mercury.is.co.za [196.4.160.222]) by hub.freebsd.org (Postfix) with ESMTP id DB8B114E07 for ; Wed, 11 Aug 1999 22:45:47 -0700 (PDT) (envelope-from geoffr@is.co.za) Received: from ISJHBEX (isjhbexnode.is.co.za [196.26.1.2]) by mercury.is.co.za (8.9.3/8.9.3) with ESMTP id HAA14609; Thu, 12 Aug 1999 07:40:03 +0200 Received: by isjhbex.is.co.za with Internet Mail Service (5.5.2448.0) id ; Thu, 12 Aug 1999 07:46:30 +0200 Message-ID: From: Geoff Rehmet To: "'Kevin Street'" , Soren Schmidt Cc: brian@pobox.com, current@FreeBSD.ORG Subject: RE: ATA - Trouble mounting secondary master Date: Thu, 12 Aug 1999 07:46:29 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just rebooted on an August 11 kernel. My system still is happy with the disks. Hmm. I can't remember exactly where my tracing went, before I left off before, but the message you are seeing comes from /sys/i386/isa/diskslice_machdep.c, line 200 (version 1.35). What you will probably find, is that if you put a line that goes: goto reread_mbr instead of "goto done", you will find that, on the second attempt, it reads the mbr successfully. The above is a severe kludge, and that is why I never committed any code to do anything of the sort. I think the error is actually somewhere in the ATA code (sorry Soren). I don't want to patch around a bug. Now somebody remarked that after the probe, a drive status light stayed on - maybe, the probe is not doing something properly for some drives, or there is somethign timing out. > -----Original Message----- > From: Kevin Street [mailto:street@iname.com] > Sent: 12 August 1999 03:10 > To: Soren Schmidt > Cc: geoffr@is.co.za; brian@pobox.com; current@FreeBSD.ORG > Subject: Re: ATA - Trouble mounting secondary master > > > Kevin Street writes: > > Soren Schmidt writes: > > > > Hmm, damn, after the problem went away for Geoff I > thought it to be > > > solved since I've never heard of it anywhere else, and I > cant reproduce > > > it here no matter what I try. > > > Does it help eany if you only has the root partition use > the wd dev > > > and have the rest use the prober ad dev entries ?? It > could be some > > > artifact from this... > > > > I tried with the ad dev entries for my problem as well with no > > improvement. I've also tried using: > > dd if=/dev/ad0s6 of=/dev/null bs=512 count=1 > > as the first access to one of the failing drives (ad0). > > The first dd fails with device not configured, but any subsequent > > access works fine. It seems it's left in an odd state by the driver > > start up, but all it takes is a read to get it sorted out again. > > More on this. > I just booted with -v and now when I do the first dd I see: > ad0: invalid primary partition table: no magic > and the same on ad2 when the swapon fails. > > So how do I get the magic back into my relationship with my drives? > > -- > Kevin Street > street@iname.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 12 0:49:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id A1A7F14C4B for ; Thu, 12 Aug 1999 00:49:02 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id JAA15899; Thu, 12 Aug 1999 09:49:04 +0200 (CEST) (envelope-from des) To: mand@alaska.com Cc: Dag-Erling Smorgrav , freebsd-current@FreeBSD.ORG Subject: Re: vty3 and 4.0 snap 080799 References: <"Michael A. Endsley"'s message of "Mon, 09 Aug 1999 06:38:47 -0800"> <37AEE7F7.8EA393DD@customcpu.com> <3.0.6.32.19990811133102.00808100@customcpu.com> From: Dag-Erling Smorgrav Date: 12 Aug 1999 09:48:59 +0200 In-Reply-To: mand@alaska.com's message of "Wed, 11 Aug 1999 13:31:02 -0800" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mand@alaska.com writes: > I get the message that ppp is started on VTY3 (type ALT-F3). It is at this > screen that VTY3 (or ALT-F3) is not active/available! The only other vty > that is available is vty1 (alt-f2) for monitoring. Get a load of this: the holographic shell is on ttyv3, which is accessed by pressing Alt-F4, as I already told you but you conveniently ignored. Now come back when you have a clue. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 12 1:55:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 43AF9155AA for ; Thu, 12 Aug 1999 01:55:43 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.3/8.9.1) id SAA11622; Thu, 12 Aug 1999 18:58:39 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199908120858.SAA11622@cimlogic.com.au> Subject: Re: Bus error in isatty() from /usr/lib/libc.so.3 In-Reply-To: <19990811221242.B70843@desert.net> from Thimble Smith at "Aug 11, 1999 10:12:42 pm" To: tim@desert.net (Thimble Smith) Date: Thu, 12 Aug 1999 18:58:39 +1000 (EST) Cc: freebsd-current@FreeBSD.ORG (FreeBSD-current List) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thimble Smith wrote: > Hello. I have a reproducable problem which gdb says is ending up at > 0x2818d862 in isatty() from /usr/lib/libc.so.3. A full back trace is > below. If this is a problem in FreeBSD, I'm very glad to do any > experiments that might be helpful. If it's a problem somewhere else, > any pointers on what I might do next would be great. [...] > #1 0x2818db22 in isatty () from /usr/lib/libc.so.3 > #2 0x2818e1de in malloc () from /usr/lib/libc.so.3 > #3 0x28236e88 in _thread_fd_table_init () from /usr/lib/libc_r.so.4 > #4 0x28238056 in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4 You are linking against both libc _and_ libc_r. "Don't do that!" -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 12 3:48: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.41.238]) by hub.freebsd.org (Postfix) with ESMTP id 0EDD315705 for ; Thu, 12 Aug 1999 03:48:00 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id LAA00358; Thu, 12 Aug 1999 11:10:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Assar Westerlund Cc: current@FreeBSD.ORG Subject: Re: DEV_MODULE doesn't support dynamic major numbers any longer? In-reply-to: Your message of "12 Aug 1999 04:57:07 +0200." <5lyafhyad8.fsf@assaris.sics.se> Date: Thu, 12 Aug 1999 11:10:53 +0200 Message-ID: <356.934449053@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5lyafhyad8.fsf@assaris.sics.se>, Assar Westerlund writes: >It seems to be the case that the possibility of specifying a major >number of NOMAJ in DEV_MODULE has vanished. The cmaj and bmaj in DEV_MODULE are only used for ordering the drivers, and otherwise with no significance. You should store your majors in your cdevsw structure. I don't particular like the concept of DEV_MODULE registrating the cdevsw by magic. >cdevsw_add() doesn't have any code for handling NOMAJ any longer. >(The only mention I can find of NOMAJ in a -current kernel tree from >19990811 are these: >which makes me wonder how the promcons works...). Fine, see above. >Is this intentional that there isn't there any support for dynamically >assigning major device numbers or is it an accident that I should go >and rectify? The previous code was a hack and inflicted problems. The right solution, (until DEVFS of course) is to add two new functions: alloc_cmaj() and alloc_bmaj() and use those. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 12 6:51:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id 60FF914FAB for ; Thu, 12 Aug 1999 06:51:20 -0700 (PDT) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id PAA01477; Thu, 12 Aug 1999 15:51:04 +0200 (CEST) To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: DEV_MODULE doesn't support dynamic major numbers any longer? References: <356.934449053@critter.freebsd.dk> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: multipart/mixed; boundary="Multipart_Thu_Aug_12_15:51:01_1999-1" Content-Transfer-Encoding: 7bit From: Assar Westerlund Date: 12 Aug 1999 15:51:02 +0200 In-Reply-To: Poul-Henning Kamp's message of "Thu, 12 Aug 1999 11:10:53 +0200" Message-ID: <5l7ln1umyh.fsf@assaris.sics.se> Lines: 83 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Multipart_Thu_Aug_12_15:51:01_1999-1 Content-Type: text/plain; charset=US-ASCII Poul-Henning Kamp writes: > The cmaj and bmaj in DEV_MODULE are only used for ordering the drivers, > and otherwise with no significance. Yeah, I realized that later. > The previous code was a hack and inflicted problems. The right > solution, (until DEVFS of course) is to add two new functions: > alloc_cmaj() and alloc_bmaj() and use those. Like the following code? And should they be used by cdevsw_add when d_maj and d_bmaj are some magical value such as -1? /assar --Multipart_Thu_Aug_12_15:51:01_1999-1 Content-Type: text/plain; charset=US-ASCII Index: kern/kern_conf.c =================================================================== RCS file: /src/fbsd-repository/src/sys/kern/kern_conf.c,v retrieving revision 1.55 diff -u -w -u -w -r1.55 kern_conf.c --- kern_conf.c 1999/08/08 18:42:47 1.55 +++ kern_conf.c 1999/08/12 13:24:04 @@ -88,6 +88,36 @@ } /* + * Return an unused cdev major or -1 if there are none free. + */ + +int +alloc_cmaj (void) +{ + int i; + + for (i = cdevsw_ALLOCSTART; i < NUMCDEVSW; ++i) + if (cdevsw[i] == NULL) + return i; + return -1; +} + +/* + * Return an unused bdev major or -1 if there are none free. + */ + +int +alloc_bmaj (void) +{ + int i; + + for (i = cdevsw_ALLOCSTART; i < NUMCDEVSW; ++i) + if (bmaj2cmaj[i] == 254) + return i; + return -1; +} + +/* * Add a cdevsw entry */ Index: sys/conf.h =================================================================== RCS file: /src/fbsd-repository/src/sys/sys/conf.h,v retrieving revision 1.69 diff -u -w -u -w -r1.69 conf.h --- conf.h 1999/08/09 18:45:20 1.69 +++ conf.h 1999/08/12 13:21:23 @@ -248,6 +248,8 @@ DECLARE_MODULE(name, name##_mod, SI_SUB_DRIVERS, SI_ORDER_MIDDLE+cmaj*256+bmaj) +int alloc_bmaj __P((void)); +int alloc_cmaj __P((void)); struct cdevsw *bdevsw __P((dev_t dev)); int cdevsw_add __P((struct cdevsw *new)); int cdevsw_remove __P((struct cdevsw *old)); --Multipart_Thu_Aug_12_15:51:01_1999-1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 12 7:35:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id E937F1578F for ; Thu, 12 Aug 1999 07:35:28 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id IAA15813; Thu, 12 Aug 1999 08:35:20 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id IAA05120; Thu, 12 Aug 1999 08:35:19 -0600 Date: Thu, 12 Aug 1999 08:35:19 -0600 Message-Id: <199908121435.IAA05120@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "David E. Cross" Cc: current@FreeBSD.ORG Subject: Re: IBM ThinkPad 600E with cardbus EtherJet 10/100 :) In-Reply-To: <199908120355.XAA57779@cs.rpi.edu> References: <199908120355.XAA57779@cs.rpi.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1: any access to the serial port (/dev/cuaa0) locks the machine. Weird. I haven't tried accessing mine though, but I know there are lots of weird setup issues that must be done to get the serial port to be read correctly. > 2: I cannot get the ethernet card to work. > 2a: It is sort-a recognized by the system, It senses the insert and remove, > but it cannot get the CIS. I remember reading somewhere that the CIS > on these cards is 'somewhere else' and you can tell pccardd where that is. > 2b: I believe that this is in reality a tulip card. Then it's not supported, since it would be a CardBus ethernet card. > I am in no way opposed to beta software, and I will code as need be, I > just need to know where things already are before I get my feet wet. You need to get an old PCCARD ethernet card, since the 600E does work in PCCARD emulation mode. I absolutely *love* mine. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 12 12:48: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48]) by hub.freebsd.org (Postfix) with ESMTP id 8BADB15859 for ; Thu, 12 Aug 1999 12:47:53 -0700 (PDT) (envelope-from plm@smtp1.xs4all.nl) Received: from localhost. (dc2-isdn88.dial.xs4all.nl [194.109.148.88]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id VAA15384; Thu, 12 Aug 1999 21:47:53 +0200 (CEST) Received: (from plm@localhost) by localhost. (8.9.3/8.9.1) id VAA00269; Thu, 12 Aug 1999 21:47:47 +0200 (MET DST) (envelope-from plm) From: Peter Mutsaers MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14259.9442.775107.16749@muon.xs4all.nl> Date: Thu, 12 Aug 1999 21:47:46 +0200 (MET DST) To: Mitsuru IWASAKI Cc: plm@xs4all.nl, freebsd-current@FreeBSD.ORG Subject: Re: recent apm changes In-Reply-To: <199908101504.AAA01219@tasogare.imasy.or.jp> References: <199908100125.KAA19675@tasogare.imasy.or.jp> <199908101504.AAA01219@tasogare.imasy.or.jp> X-Mailer: VM 6.65 under Emacs 20.3.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> "MI" == Mitsuru IWASAKI writes: MI> Please try this patch. MI> If it still fails, it's worth to try increasing APM_SUSPEND_DELAY, MI> something like: MI> #define APM_SUSPEND_DELAY 3 Alas, it doesn't make a difference. I tried too with APM_SUSPEND_DELAY 5. What I see when I issue 'zzz', is a delay of 5 seconds, but in between programs keep running (and thus keep generating interrupts I guess). Then after 5 seconds the screen blanks, the power light starts flashing (indicating suspend mode), but when I hit a key, the console says (slept 00:00:02) only, and programs in fact continued running (thus it didn't go or remain in suspend mode at all). Anyway thanks for you efforts so far. -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know plm@xs4all.nl | the Netherlands | what I'm doing. ---------------+---------------------+------------------ Powered by FreeBSD (-current). See http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 12 12:55:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 4A89E14F80; Thu, 12 Aug 1999 12:55:50 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id OAA33793; Thu, 12 Aug 1999 14:44:54 -0400 (EDT) Date: Thu, 12 Aug 1999 14:44:54 -0400 (EDT) From: Ben Rosengart To: multimedia@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999, Brian F. Feldman wrote: > What in the world would be the point of doing this? What would be so great > about not seeing the system boot up? One might want minimal or no boot messages, just to look nice, while still wanting the dmesg stuff around in case something goes wrong or they need to configure a kernel. It's certainly chrome, but I'd like it. -- Ben UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 12 14: 4:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 046F215040; Thu, 12 Aug 1999 14:04:30 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id RAA86638; Thu, 12 Aug 1999 17:04:04 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <199908122104.RAA86638@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ben Rosengart Cc: multimedia@FreeBSD.ORG, current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: it's time... References: In-reply-to: Your message of "Thu, 12 Aug 1999 14:44:54 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Aug 1999 17:04:04 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 11 Aug 1999, Brian F. Feldman wrote: > > > What in the world would be the point of doing this? What would be so great > > about not seeing the system boot up? > > One might want minimal or no boot messages, just to look nice, while > still wanting the dmesg stuff around in case something goes wrong or > they need to configure a kernel. It's certainly chrome, but I'd like > it. Spash screen. That being said, the capability to have what comes out during a verbose boot go somewhere else for later review, while only the "normal" messages are seen on the console would be sorta cool. I think you could do this by converting the printf()'s in the kernel to something like syslog() with explicity verbosity/priority specifications. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 12 20:52:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 2F8A414CF9 for ; Thu, 12 Aug 1999 20:52:10 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn24.imasy.or.jp [202.227.24.216]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id MAA19931; Fri, 13 Aug 1999 12:52:17 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199908130352.MAA19931@tasogare.imasy.or.jp> To: plm@xs4all.nl Cc: iwasaki@jp.FreeBSD.org, freebsd-current@FreeBSD.ORG Subject: Re: recent apm changes In-Reply-To: Your message of "Thu, 12 Aug 1999 21:47:46 +0200 (MET DST)" <14259.9442.775107.16749@muon.xs4all.nl> References: <14259.9442.775107.16749@muon.xs4all.nl> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 13 Aug 1999 12:55:57 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 21 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > MI> Please try this patch. > MI> If it still fails, it's worth to try increasing APM_SUSPEND_DELAY, > MI> something like: > MI> #define APM_SUSPEND_DELAY 3 > > Alas, it doesn't make a difference. Hmmmm. OK, I'll buy new mather board same one as yours and investigate what's happend on it. Could you tell me which M/B are you using? And I'd like to have your dmesg output from kernel with APM_DEBUG option. # In your kernel config file: # options APM_DEBUG Also, I'll send you few more patches before I purchase new one if I get new ideas. > Anyway thanks for you efforts so far. Not at all. I never give up :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 12 22:43:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 784D914D93 for ; Thu, 12 Aug 1999 22:43:09 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id BAA80699 for ; Fri, 13 Aug 1999 01:43:07 -0400 (EDT) Message-Id: <199908130543.BAA80699@cs.rpi.edu> To: current@freebsd.org Subject: yet more TP 600E fun... Date: Fri, 13 Aug 1999 01:43:07 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I attempt to boot a CD off of the TP600E and I get the following errors: "Can't work out which disk we are booting from." "Guessed BIOS device 0x8b not found by probes, defaulting to disk0:" Then whenever it attmpts to access "disk0:" it goes to the floppy drive. Suggestions? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 12 23:44:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 0600C156F3; Thu, 12 Aug 1999 23:44:28 -0700 (PDT) (envelope-from steveo@iol.ie) Received: from pooh.elsevier.nl (localhost [127.0.0.1]) by pooh.elsevier.nl (8.9.3/8.9.3) with ESMTP id HAA65935; Fri, 13 Aug 1999 07:32:27 +0100 (IST) (envelope-from steveo@iol.ie) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 13 Aug 1999 07:32:26 +0100 (IST) From: "Steve O'Hara-Smith" To: Ben Rosengart Subject: Re: it's time... Cc: current@FreeBSD.ORG, multimedia@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Aug-99 Ben Rosengart wrote: > On Wed, 11 Aug 1999, Brian F. Feldman wrote: > >> What in the world would be the point of doing this? What would be so >> great >> about not seeing the system boot up? > > One might want minimal or no boot messages, just to look nice, while > still wanting the dmesg stuff around in case something goes wrong or > they need to configure a kernel. It's certainly chrome, but I'd like > it. Surely if you don't want to see the boot messages for cosmetic reasons a splash screen is the most cosmeticly pleasing solution. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 7:45:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id 7DA2A14EE1 for ; Fri, 13 Aug 1999 07:45:08 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id PAA42401; Fri, 13 Aug 1999 15:43:37 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id PAA01596; Fri, 13 Aug 1999 15:45:46 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199908131445.PAA01596@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" Cc: mandm@alaska.com, freebsd-current@FreeBSD.ORG, "Josef L. Karthauser" Subject: Re: vty3 and 4.0 snap 080799 In-reply-to: Your message of "Wed, 11 Aug 1999 19:21:56 PDT." <22406.934424516@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Aug 1999 15:45:46 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It sounds like ppp is simply exiting immediately. I'll turn debugging > on and give it a shot myself; perhaps somebody broke something. > > - Jordan > > > I should have also stated that I tried all the other "F" keys also. > > The only vty that is available/active is vty1 for debugging. Every other > > F-key gets the "beep". > > HTH in solving my problem > > > > fwiw dept.- I have been using FreeBSD since 2.21-R Errum, if this is a re-install, I may see what the problem is. I changed sysinstall to run ``ppp install'' as sysinstall now writes an ``install'' label into ppp.conf. Might it be the case that a reinstall doesn't add the ``install'' label ? -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 7:49:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1]) by hub.freebsd.org (Postfix) with ESMTP id E476F14F1D for ; Fri, 13 Aug 1999 07:49:36 -0700 (PDT) (envelope-from crawdad@gungnir.fnal.gov) Received: from gungnir.fnal.gov (localhost [127.0.0.1]) by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id JAA11221; Fri, 13 Aug 1999 09:48:47 -0500 (CDT) Message-Id: <199908131448.JAA11221@gungnir.fnal.gov> To: "Steve O'Hara-Smith" Cc: current@FreeBSD.ORG From: "Matt Crawford" Subject: Re: it's time... In-reply-to: Your message of Fri, 13 Aug 1999 07:32:26 BST. Date: Fri, 13 Aug 1999 09:48:47 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Surely if you don't want to see the boot messages for cosmetic > reasons a splash screen is the most cosmeticly pleasing solution. Speaking of splash screens (a bit far from the thread's original topic), I've got my laptop set up to show the daemon-and-sunset picture on boot, but it seems I now have an extremely small window of time to press a key to get to the boot prompt. What do I need to insert to get this window back up to several seconds? My loader.rc file looks like this: \ Loader.rc \ \ Includes additional commands include /boot/loader.4th \ Reads and processes loader.rc \ start \ Unless set otherwise, autoboot is automatic at this point load kernel load -t splash_image_data daemon_640.bmp load vesa load splash_bmp boot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 8:53:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id B6C6F14F3B for ; Fri, 13 Aug 1999 08:53:19 -0700 (PDT) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id IAA08250; Fri, 13 Aug 1999 08:50:57 -0700 (PDT) Date: Fri, 13 Aug 1999 08:50:57 -0700 (PDT) From: Tom Bartol To: "David E. Cross" Cc: current@FreeBSD.ORG Subject: Re: yet more TP 600E fun... In-Reply-To: <199908130543.BAA80699@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I see the same problem when trying to boot FreeBSD-3.0-RELEASE (or there abouts) and later cdroms on my TP770. I can boot FreeBSD-2.2.8 and earlier FreeBSD-3.0-SNAP cdroms just fine. I think it has something to do with the new boot loader that went in just before 3.0-RELEASE. Tom On Fri, 13 Aug 1999, David E. Cross wrote: > I attempt to boot a CD off of the TP600E and I get the following errors: > > "Can't work out which disk we are booting from." > "Guessed BIOS device 0x8b not found by probes, defaulting to disk0:" > > Then whenever it attmpts to access "disk0:" it goes to the floppy drive. > > Suggestions? > > -- > David Cross | email: crossd@cs.rpi.edu > Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd > Rensselaer Polytechnic Institute, | Ph: 518.276.2860 > Department of Computer Science | Fax: 518.276.4033 > I speak only for myself. | WinNT:Linux::Linux:FreeBSD > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 9: 1:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id C7959159BC for ; Fri, 13 Aug 1999 09:01:23 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11FJaf-000LuU-00; Fri, 13 Aug 1999 17:49:57 +0200 From: Sheldon Hearn To: "Matt Crawford" Cc: "Steve O'Hara-Smith" , current@FreeBSD.ORG Subject: Re: it's time... In-reply-to: Your message of "Fri, 13 Aug 1999 09:48:47 EST." <199908131448.JAA11221@gungnir.fnal.gov> Date: Fri, 13 Aug 1999 17:49:57 +0200 Message-ID: <84225.934559397@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Aug 1999 09:48:47 EST, "Matt Crawford" wrote: > load kernel > load -t splash_image_data daemon_640.bmp > load vesa > load splash_bmp > boot Why boot and not autoboot? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 14: 3:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30]) by hub.freebsd.org (Postfix) with ESMTP id 1192A14DE6 for ; Fri, 13 Aug 1999 14:02:46 -0700 (PDT) (envelope-from ron@zappa.demon.nl) Received: from win98 (win98.demon.nl [192.168.100.2]) by zappa.demon.nl (8.9.3/8.9.3) with ESMTP id XAA00377 for ; Fri, 13 Aug 1999 23:02:21 +0200 (CEST) (envelope-from ron@zappa.demon.nl) From: "Ron Klinkien" To: Subject: Problems with 4.0 keyboard input! Date: Sat, 14 Aug 1999 03:03:05 +0200 Message-ID: <000001bee5f0$c467c7c0$0264a8c0@.demon.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, After building a few succesfull 4.0 releases (last cvsupped on 13 aug 99), the keyboard is acting very strange, i cannot login, i get only strange characters, and when I hit CTRL I get: load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K Login through the network with telnet is no problem.... I also want to know what this means: WARNING: "bktr" is usurping "bktr"'s cdevsw[] It's my Brooktree video capture/tuner card This is my dmesg and config: --- dmesg --- Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #23: Fri Aug 13 22:15:49 CEST 1999 ron@zappa.demon.nl:/usr/src/sys/compile/MOON Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 334092770 Hz CPU: Pentium II/Xeon/Celeron (334.09-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183f9ff real memory = 134205440 (131060K bytes) avail memory = 127098880 (124120K bytes) Preloaded elf kernel "kernel" at 0xc02e2000. VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc028c1e2 (1000022) VESA: Matrox Graphics Inc. Pentium Pro MTRR support enabled Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 WARNING: "bktr" is usurping "bktr"'s cdevsw[] pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 10 at device 0.0 on pci1 isab0: at device 4.0 on pci0 chip1: at device 4.1 on pci0 chip2: at device 4.2 on pci0 chip3: at device 4.3 on pci0 bktr0: irq 14 at device 10.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only smbus0: on bti2c0 Miro TV, Temic PAL tuner. xl0: <3Com 3c905-TX Fast Etherlink XL> irq 15 at device 11.0 on pci0 xl0: Ethernet address: 00:60:08:3e:74:63 xl0: autoneg complete, link status good (half-duplex, 10Mbps) ncr0: irq 10 at device 12.0 on pci0 isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port isic0 at port 0xf80 iomem 0xd0000-0xd0fff irq 5 flags 0x2 on isa0 isic0: Teles S0/16, Creatix ISDN S0-16 or Niccy 1016 isic0: ISAC 2085 Version V2.3 (B3) (IOM-1) (Addr=0xc00d0100) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0xc00d0180, AddrB=0xc00d01c0) Checking for GUS Plug-n-Play ... No Plug-n-Play devices were found gus0 at port 0x220 irq 11 drq 1 flags 0x3 on isa0 snd0: snd0: i4b: ISDN call control device attached i4bisppp: 1 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 4 ISDN trace device(s) attached changing root device to da0s1a da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C) cd0 at ncr0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present -------- --- CONFIG ---- # # MOON -- Kernel configuration for my FreeBSD server. # # $Id: MOON,v 1.000.0.00 1999/08/09 17:12:26 ronk Exp $ machine "i386" cpu "I686_CPU" ident MOON maxusers 64 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=1000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor # System bus controller isa0 controller pnp0 controller pci0 # Floppy controller controller fdc0 at isa? port "IO_FD1" irq 6 drq 2 disk fd0 at fdc0 drive 0 # Scsi controller controller ncr0 controller scbus0 device da0 device sa0 device pass0 device cd0 #Only need one of these, the code dynamically grows # Keyboard & PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 # Display device vga0 at isa? port ? conflicts pseudo-device splash # The following option probably won't work with the LCD displays. options VGA_WIDTH90 # support 90 column modes # To include support for VESA video modes options VESA # Console device sc0 at isa? options MAXCONS=16 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines options SC_DISABLE_REBOOT # disable reboot key sequence device npx0 at nexus? port IO_NPX flags 0x0 irq 13 # Serial ports device sio0 at isa? port "IO_COM1" flags 0x10 irq 4 device sio1 at isa? port "IO_COM2" irq 3 # Parallel port controller ppbus0 device ppc0 at isa? port? flags 0x40 irq 7 device lpt0 # Ethernet NIC device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Misc device pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device pty #Pseudo ttys pseudo-device gzip #Exec gzipped a.out's pseudo-device sppp #Generic Synchronous PPP # System V shared memory and message queues. options SYSVSHM options SYSVMSG options SYSVSEM options SHMMAXPGS=10000 options SHMMNI=100 options SHMSEG=10 options SEMMNS=200 options SEMMNI=70 options SEMMSL=61 # Soft updates options SOFTUPDATES # Teles S0/16 or Creatix ISDN-S0 or Niccy 1016 options "TEL_S0_16" device isic0 at isa? port 0xf80 iomem 0xd0000 irq 5 flags 2 # ISDN Protocol Stack # ------------------- # # Q.921 / layer 2 - i4b passive cards D channel handling pseudo-device "i4bq921" # # Q.931 / layer 3 - i4b passive cards D channel handling pseudo-device "i4bq931" # # layer 4 - i4b common passive and active card handling pseudo-device "i4b" # # ISDN devices # ------------ # # userland driver to do ISDN tracing (for passive cards only) pseudo-device "i4btrc" 4 # # userland driver to control the whole thing pseudo-device "i4bctl" # # userland driver for access to raw B channel pseudo-device "i4brbch" 4 # # userland driver for telephony pseudo-device "i4btel" 2 # # network driver for IP over raw HDLC ISDN pseudo-device "i4bipr" 4 # enable VJ header compression detection for ipr i/f options IPR_VJ # # network driver for sync PPP over ISDN pseudo-device "i4bisppp" # Gravis Ultrasound controller snd0 device gus0 at isa? port 0x220 irq 11 drq 1 flags 0x3 # Brooktree driver has been ported to the new I2C framework. Thus, # you'll need to have the following 3 lines in the kernel config. # controller smbus0 # controller iicbus0 # controller iicbb0 # The iic and smb devices are only needed if you want to control other # I2C slaves connected to the external connector of some cards. # device bktr0 controller smbus0 controller iicbus0 controller iicbb0 ----- Thanks... Ron. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 14:23: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from web1002.mail.yahoo.com (web1002.mail.yahoo.com [128.11.23.92]) by hub.freebsd.org (Postfix) with SMTP id AB99214E8B for ; Fri, 13 Aug 1999 14:22:50 -0700 (PDT) (envelope-from bvmcg@yahoo.com) Message-ID: <19990813212134.3021.rocketmail@web1002.mail.yahoo.com> Received: from [206.71.110.101] by web1002.mail.yahoo.com; Fri, 13 Aug 1999 14:21:34 PDT Date: Fri, 13 Aug 1999 14:21:34 -0700 (PDT) From: Brian McGroarty Reply-To: brian@pobox.com Subject: Re: Problems with 4.0 keyboard input! To: Ron Klinkien , freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get the bktr device usurping its own cdevsw[] as well - I was told it was "most likely" benign, so I've been waiting for others' comments. 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. Resetting seems to be the only remedy. This persists with two different keyboard models and on unplugging and reinserting the keyboard. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #10: Fri Aug 13 07:02:32 CDT 1999 bvmcg@milkymoo.newtoy.com:/usr/src/sys/compile/DOCENT Timecounter "i8254" frequency 1193182 Hz CPU: Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 536870912 (524288K bytes) avail memory = 518422528 (506272K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc028f000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc028f09c. Pentium Pro MTRR support enabled Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 WARNING: "bktr" is usurping "bktr"'s cdevsw[] pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 16 at device 0.0 on pci1 isab0: at device 7.0 on pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 chip1: at device 7.2 on pci0 chip2: at device 7.3 on pci0 bktr0: irq 16 at device 16.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only smbus0: on bti2c0 Hauppauge Model 62471 A Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, dbx stereo. pci0: unknown card DD^0878 (vendor=0x109e, dev=0x0878) at 16.1 irq 16 pcm0: irq 18 at device 18.0 on pci0 pcm0: using I/O space register mapping at 0xef00 fxp0: irq 19 at device 19.0 on pci0 fxp0: Ethernet address 00:90:27:18:a6:fa xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 16 at device 20.0 on pci0 xl0: Ethernet address: 00:50:04:01:77:7b xl0: autoneg complete, link status good (half-duplex, 100Mbps) isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging disabled SMP: AP CPU #1 Launched! ata0: master: setting up UDMA2 mode on PIIX4 chip OK ad0: ATA-4 disk at ata0 as master ad0: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 31 depth queue, DMA mode ata0: slave: setting up UDMA2 mode on PIIX4 chip OK ad1: ATA-4 disk at ata0 as slave ad1: 21557MB (44150400 sectors), 43800 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 31 depth queue, DMA mode ata1: master: setting up UDMA2 mode on PIIX4 chip OK ad2: ATA-4 disk at ata1 as master ad2: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=2 ad2: 16 secs/int, 31 depth queue, DMA mode atapi: piomode=4, dmamode=2, udmamode=-1 ata1: slave: setting up WDMA2 mode on PIIX3/4 chip OK atapi: DMA transfer mode set acd0: CDROM drive at ata1 as slave acd0: drive speed 344 - 1034KB/sec, 384KB cache, DMA acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: supported write types: CD-R, CD-RW, test write acd0: Audio: play, 128 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked, lock protected machine i386 cpu I686_CPU ident DOCENT maxusers 32 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options INET options FFS options FFS_ROOT options CD9660 options PROCFS options COMPAT_43 options KTRACE options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores # To make an SMP kernel, the next two are needed options SMP options APIC_IO controller isa0 controller pnp0 # PnP support for ISA controller pci0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 controller ata0 device atadisk0 device atadisk1 device atadisk2 device atapicd0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts pseudo-device splash device sc0 at isa? options XSERVER options FAT_CURSOR device npx0 at nexus? port IO_NPX irq 13 device fxp0 device xl0 pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device pty 16 # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's pseudo-device bpf 4 #Berkeley packet filter options IPDIVERT options IPFIREWALL controller smbus0 controller iicbus0 controller iicbb0 device bktr0 device pcm0 options SOFTUPDATES --- Ron Klinkien wrote: > > Hello, > > After building a few succesfull 4.0 releases (last cvsupped on > 13 aug 99), > the keyboard is acting very strange, i cannot login, > i get only strange characters, and when I hit CTRL I get: > > load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K > load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K > load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K > > > > Login through the network with telnet is no problem.... > > I also want to know what this means: > > WARNING: "bktr" is usurping "bktr"'s cdevsw[] > > It's my Brooktree video capture/tuner card > > > This is my dmesg and config: > > --- dmesg --- > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights > reserved. > FreeBSD 4.0-CURRENT #23: Fri Aug 13 22:15:49 CEST 1999 > ron@zappa.demon.nl:/usr/src/sys/compile/MOON > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 334092770 Hz > CPU: Pentium II/Xeon/Celeron (334.09-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x651 Stepping = 1 > > Features=0x183f9ff PAT,PSE36,MMX,FXSR> > real memory = 134205440 (131060K bytes) > avail memory = 127098880 (124120K bytes) > Preloaded elf kernel "kernel" at 0xc02e2000. > VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc028c1e2 > (1000022) > VESA: Matrox Graphics Inc. > Pentium Pro MTRR support enabled > Probing for PnP devices: > npx0: on motherboard > npx0: INT 16 interface > pcib0: on > motherboard > pci0: on pcib0 > WARNING: "bktr" is usurping "bktr"'s cdevsw[] > pcib1: at device > 1.0 on pci0 > pci1: on pcib1 > vga-pci0: irq 10 at > device 0.0 on > pci1 > isab0: at device 4.0 on pci0 > chip1: at device 4.1 on pci0 > chip2: at device 4.2 on pci0 > chip3: at device > 4.3 on pci0 > bktr0: irq 14 at device 10.0 on pci0 > iicbb0: on bti2c0 > iicbus0: on iicbb0 master-only > smbus0: on bti2c0 > Miro TV, Temic PAL tuner. > xl0: <3Com 3c905-TX Fast Etherlink XL> irq 15 at device 11.0 > on pci0 > xl0: Ethernet address: 00:60:08:3e:74:63 > xl0: autoneg complete, link status good (half-duplex, 10Mbps) > ncr0: irq 10 at device 12.0 on > pci0 > isa0: on motherboard > fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on > isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60-0x6f on > isa0 > atkbd0: irq 1 on atkbdc0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > vga0: at port 0x3b0-0x3df iomem > 0xa0000-0xbffff on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 > ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode > lpt0: on ppbus 0 > lpt0: Interrupt-driven port > isic0 at port 0xf80 iomem 0xd0000-0xd0fff irq 5 flags 0x2 on > isa0 > isic0: Teles S0/16, Creatix ISDN S0-16 or Niccy 1016 > isic0: ISAC 2085 Version V2.3 (B3) (IOM-1) (Addr=0xc00d0100) > isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0xc00d0180, > AddrB=0xc00d01c0) > Checking for GUS Plug-n-Play ... > No Plug-n-Play devices were found > gus0 at port 0x220 irq 11 drq 1 flags 0x3 on isa0 > snd0: snd0: > i4b: ISDN call control device attached > i4bisppp: 1 ISDN SyncPPP device(s) attached > i4bctl: ISDN system control port attached > i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header > compression) > i4btel: 2 ISDN telephony interface device(s) attached > i4brbch: 4 raw B channel access device(s) attached > i4btrc: 4 ISDN trace device(s) attached > changing root device to da0s1a > da0 at ncr0 bus 0 target 0 lun 0 > da0: Fixed Direct Access > SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), > Tagged Queueing > Enabled > da0: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C) > cd0 at ncr0 bus 0 target 6 lun 0 > cd0: Removable CD-ROM SCSI-2 > device > cd0: 10.000MB/s transfers (10.000MHz, offset 15) > cd0: Attempt to query device size failed: NOT READY, Medium > not present > -------- > > > --- CONFIG ---- > # > # MOON -- Kernel configuration for my FreeBSD server. > # > # $Id: MOON,v 1.000.0.00 1999/08/09 17:12:26 ronk Exp $ > > machine "i386" > cpu "I686_CPU" > ident MOON > maxusers 64 > > options INET #InterNETworking > options FFS #Berkeley Fast Filesystem > options FFS_ROOT #FFS usable as root device [keep this!] > options MSDOSFS #MSDOS Filesystem > options CD9660 #ISO 9660 Filesystem > options PROCFS #Process filesystem > options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] > options SCSI_DELAY=1000 #Be pessimistic about Joe SCSI > device > options UCONSOLE #Allow users to grab the console > options USERCONFIG #boot -c editor > options VISUAL_USERCONFIG #visual boot -c editor > > # System bus > controller isa0 > controller pnp0 > controller pci0 > > # Floppy controller > controller fdc0 at isa? port "IO_FD1" irq 6 drq 2 > disk fd0 at fdc0 drive 0 > > # Scsi controller > controller ncr0 > controller scbus0 > device da0 > device sa0 > device pass0 > device cd0 #Only need one of these, the code dynamically > grows > > # Keyboard & PS/2 mouse > controller atkbdc0 at isa? port IO_KBD > device atkbd0 at atkbdc? irq 1 > device psm0 at atkbdc? irq 12 > > # Display > device vga0 at isa? port ? conflicts > pseudo-device splash > # The following option probably won't work with the LCD > displays. > options VGA_WIDTH90 # support 90 column > modes > > # To include support for VESA video modes > options VESA > > # Console > device sc0 at isa? > options MAXCONS=16 # number of virtual > consoles > options SC_HISTORY_SIZE=200 # number of history > buffer lines > options SC_DISABLE_REBOOT # disable reboot key > sequence > > device npx0 at nexus? port IO_NPX flags 0x0 irq 13 > > # Serial ports > device sio0 at isa? port "IO_COM1" flags 0x10 irq 4 > device sio1 at isa? port "IO_COM2" irq 3 > > # Parallel port > controller ppbus0 > device ppc0 at isa? port? flags 0x40 irq 7 > device lpt0 > > # Ethernet NIC > device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') > > # Misc device > pseudo-device ether #Generic Ethernet > pseudo-device loop #Network loopback device > pseudo-device pty #Pseudo ttys > pseudo-device gzip #Exec gzipped a.out's > pseudo-device sppp #Generic Synchronous PPP > > # System V shared memory and message queues. > options SYSVSHM > options SYSVMSG > options SYSVSEM > > options SHMMAXPGS=10000 > options SHMMNI=100 > options SHMSEG=10 > options SEMMNS=200 > options SEMMNI=70 > options SEMMSL=61 > > # Soft updates > options SOFTUPDATES > > # Teles S0/16 or Creatix ISDN-S0 or Niccy 1016 > options "TEL_S0_16" > device isic0 at isa? port 0xf80 iomem 0xd0000 irq 5 flags 2 > > # ISDN Protocol Stack > # ------------------- > # > # Q.921 / layer 2 - i4b passive cards D channel handling > pseudo-device "i4bq921" > # > # Q.931 / layer 3 - i4b passive cards D channel handling > pseudo-device "i4bq931" > # > # layer 4 - i4b common passive and active card handling > pseudo-device "i4b" > > # > # ISDN devices > # ------------ > # > # userland driver to do ISDN tracing (for passive cards only) > pseudo-device "i4btrc" 4 > # > # userland driver to control the whole thing > pseudo-device "i4bctl" > # > # userland driver for access to raw B channel > pseudo-device "i4brbch" 4 > # > # userland driver for telephony > pseudo-device "i4btel" 2 > # > # network driver for IP over raw HDLC ISDN > pseudo-device "i4bipr" 4 > # enable VJ header compression detection for ipr i/f > options IPR_VJ > # > # network driver for sync PPP over ISDN > pseudo-device "i4bisppp" > > # Gravis Ultrasound > controller snd0 > device gus0 at isa? port 0x220 irq 11 drq 1 flags 0x3 > > # Brooktree driver has been ported to the new I2C framework. > Thus, > # you'll need to have the following 3 lines in the kernel > config. > # controller smbus0 > # controller iicbus0 > # controller iicbb0 > # The iic and smb devices are only needed if you want to > control other > # I2C slaves connected to the external connector of some > cards. > # > device bktr0 > controller smbus0 > controller iicbus0 > controller iicbb0 > > > > ----- > > Thanks... > > Ron. > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > _________________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 14:27:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from amukta.gci.net (amukta.gci.net [208.138.130.216]) by hub.freebsd.org (Postfix) with ESMTP id 2C2B014E8B; Fri, 13 Aug 1999 14:27:07 -0700 (PDT) (envelope-from mandm@alaska.com) Received: from [209.165.151.50] ([209.165.151.50]) by amukta.gci.net (Netscape Messaging Server 4.04 Jul 21 1999 18:33:18) with SMTP id FGFA7200.B18; Fri, 13 Aug 1999 13:25:50 -0800 Message-Id: <3.0.6.32.19990813132650.007bfe50@mail.gci.net> X-Sender: mandm@mail.gci.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 13 Aug 1999 13:26:50 -0800 To: Brian Somers , freebsd-current@freebsd.org From: "Michael A. Endsley" Subject: Re: vty3 and 4.0 snap 080799 Cc: freebsd-current@FreeBSD.ORG, "Josef L. Karthauser" In-Reply-To: <199908131445.PAA01596@keep.lan.Awfulhak.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian (and others). You are correct about the installation. I had a 3.0-R slice, and somehow corrupted it. I decided I would go to 4.0 and follow current. That is when the problem started. However: very early this morning, I got 3.2 (19990812) floppies and did a ftp installation with those. The "ppp" worked great on ALT-F3! I now have a base installation and kernel source for compiling. I won't do a full install of 3.2 because I want to follow current. If I can provide any other information about what is not working on 4.0, let me know. I will do whatever to get this working :) Mike At 03:45 PM 08/13/1999 +0100, Brian Somers wrote: >> It sounds like ppp is simply exiting immediately. I'll turn debugging >> on and give it a shot myself; perhaps somebody broke something. >> >> - Jordan >> >> > I should have also stated that I tried all the other "F" keys also. >> > The only vty that is available/active is vty1 for debugging. Every other >> > F-key gets the "beep". >> > HTH in solving my problem >> > >> > fwiw dept.- I have been using FreeBSD since 2.21-R > >Errum, if this is a re-install, I may see what the problem is. I >changed sysinstall to run ``ppp install'' as sysinstall now writes an >``install'' label into ppp.conf. Might it be the case that a >reinstall doesn't add the ``install'' label ? > >-- >Brian > >Don't _EVER_ lose your sense of humour ! > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 14:55: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id A369614C20 for ; Fri, 13 Aug 1999 14:55:06 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id PAA44793 for ; Fri, 13 Aug 1999 15:17:47 -0400 (EDT) Date: Fri, 13 Aug 1999 15:17:47 -0400 (EDT) From: Ben Rosengart To: current@freebsd.org Subject: SUPFLAGS in /etc/make.conf Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I submit that putting "-z" in here is silly, because the sample cvsup config files turn on compression, and suggest commenting it out if you have a fast link. It seems counterintuitive that one can comment out the compression in the standard supfiles and then have it enabled by default with "make update" anyway. Comments? -- Ben UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 15:59:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 6B2C21501F for ; Fri, 13 Aug 1999 15:59:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id UAA00649; Wed, 11 Aug 1999 20:01:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908120301.UAA00649@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Soren Schmidt Cc: geoffr@is.co.za (Geoff Rehmet), brian@pobox.com, current@FreeBSD.ORG Subject: Re: ATA - Trouble mounting secondary master In-reply-to: Your message of "Wed, 11 Aug 1999 09:25:51 +0200." <199908110725.JAA56854@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Wed, 11 Aug 1999 20:01:33 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems Geoff Rehmet wrote: > > Hmm, > > = > > My root device still lands up on "wd0" - even though my fstab has > > the root filesystem on ad0s1a. I haven't looked at getting it to > > use the ad dev entries for the root file system. (I'm assuming that > > is still WIP.) > = > Our boot blocks/loader dont have the needed computrons to use the > "ad" device name. However I have some patches to boot2 that allows > to boot off an ad root device, provided you dont use the loader, and > put the rigth boot string in boot.config. This should now be totally redundant as long as your /etc/fstab entry = is correct. -- = \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 15:59:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id D444C14C13 for ; Fri, 13 Aug 1999 15:59:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id TAA00452; Wed, 11 Aug 1999 19:18:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908120218.TAA00452@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Cejka Rudolf Cc: freebsd-current@FreeBSD.ORG Subject: Re: VESA module doesn't work with ATI Mach64 RagePro In-reply-to: Your message of "Tue, 10 Aug 1999 08:37:49 +0200." <19990810083749.A55581@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Aug 1999 19:18:09 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes, thanks. Information reported by 0x4F01 function about any video > mode has set MODE_NON_VGA attribute indeed. And now I have found DOS TSR > program for VESA support... Bleagh. Have you tried ignoring that attribute in our code and seeing what happens when you select one? > I hate VESA 2.0/3.0 specification :-( I hate ATI :-( > > Is there any good AGP graphics card with full BIOS support in hardware? I'm having a lot of success with the Voodoo 3... -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 17: 3:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 874A915070 for ; Fri, 13 Aug 1999 17:03:19 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id QAA01992; Fri, 13 Aug 1999 16:55:58 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908132355.QAA01992@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Mutsaers Cc: Mitsuru IWASAKI , freebsd-current@FreeBSD.ORG Subject: Re: recent apm changes In-reply-to: Your message of "Thu, 12 Aug 1999 21:47:46 +0200." <14259.9442.775107.16749@muon.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Aug 1999 16:55:57 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Then after 5 seconds the screen blanks, the power light starts > flashing (indicating suspend mode), but when I hit a key, the console > says (slept 00:00:02) only, and programs in fact continued running > (thus it didn't go or remain in suspend mode at all). I think you'll find that programs didn't, in fact, continue running; rather they paused and then resumed when you came out of suspend. The "slept" message indicates that the system spent that amount of time inside the BIOS in suspend mode; there is no way for programs to be run during that time. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 17:15:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 1B791150E1 for ; Fri, 13 Aug 1999 17:15:52 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA02069; Fri, 13 Aug 1999 17:10:27 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908140010.RAA02069@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "David E. Cross" Cc: current@freebsd.org Subject: Re: yet more TP 600E fun... In-reply-to: Your message of "Fri, 13 Aug 1999 01:43:07 EDT." <199908130543.BAA80699@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Aug 1999 17:10:27 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I attempt to boot a CD off of the TP600E and I get the following errors: > > "Can't work out which disk we are booting from." > "Guessed BIOS device 0x8b not found by probes, defaulting to disk0:" > > Then whenever it attmpts to access "disk0:" it goes to the floppy drive. > > Suggestions? Known weirdness in the TP's BIOS not handled properly by the bootloader. I don't have immediate plans to do anything about this; you could try hacking the loader to accept the 0x8b value and see if that actually works. Or you could pester IBM to DTRT. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 18:48:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8E3F114E9B for ; Fri, 13 Aug 1999 18:48:52 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA28694; Fri, 13 Aug 1999 19:49:05 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA12820; Fri, 13 Aug 1999 19:49:12 -0600 (MDT) Message-Id: <199908140149.TAA12820@harmony.village.org> To: "Ron Klinkien" Subject: Re: Problems with 4.0 keyboard input! Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 14 Aug 1999 03:03:05 +0200." <000001bee5f0$c467c7c0$0264a8c0@.demon.nl> References: <000001bee5f0$c467c7c0$0264a8c0@.demon.nl> Date: Fri, 13 Aug 1999 19:49:12 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <000001bee5f0$c467c7c0$0264a8c0@.demon.nl> "Ron Klinkien" writes: : After building a few succesfull 4.0 releases (last cvsupped on 13 aug 99), : the keyboard is acting very strange, i cannot login, : i get only strange characters, and when I hit CTRL I get: : : load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K : load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K : load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K I get that too from time to time. I think that the boot blocks are putting the keyboard into an odd state since I sometimes can't break into the boot sequence to boot an alternate kernel. So far it has been confined to my Sony VAIO. Never could come up with a good test case for it, however.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 20:11:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 260C514DDF for ; Fri, 13 Aug 1999 20:11:45 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:S7gz0TSE7n4+clRDQnnd/1hGCf9AWVNg@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id MAA22278; Sat, 14 Aug 1999 12:07:59 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id MAA10852; Sat, 14 Aug 1999 12:12:18 +0900 (JST) Message-Id: <199908140312.MAA10852@zodiac.mech.utsunomiya-u.ac.jp> To: brian@pobox.com Cc: Ron Klinkien , freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Problems with 4.0 keyboard input! In-reply-to: Your message of "Fri, 13 Aug 1999 14:21:34 MST." <19990813212134.3021.rocketmail@web1002.mail.yahoo.com> References: <19990813212134.3021.rocketmail@web1002.mail.yahoo.com> Date: Sat, 14 Aug 1999 12:12:18 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [...] >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 hit the keyboard at the "wrong" moment during keyboard initialization, the keyboard driver may get confused. In your case, you type something before the kernel is loaded and that seems to be causing the trouble. Such key input should be discarded by the keyboard driver before it tries to initialize the keyboard. There may be a nasty timing problem here... As a temporary workaround, please apply the following patch to /sys/dev/atkbd.c and see how it works. Kazu >Resetting seems to be the only remedy. This persists with two >different keyboard models and on unplugging and reinserting the >keyboard. Index: atkbd.c =================================================================== RCS file: /src/CVS/src/sys/dev/kbd/atkbd.c,v retrieving revision 1.12 diff -u -r1.12 atkbd.c --- atkbd.c 1999/07/18 06:16:25 1.12 +++ atkbd.c 1999/08/14 03:10:40 @@ -1153,7 +1178,7 @@ } /* save the current controller command byte */ - empty_both_buffers(kbdc, 10); + empty_both_buffers(kbdc, 200); c = get_controller_command_byte(kbdc); if (c == -1) { /* CONTROLLER ERROR */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 21:26:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id 0DAE614E52 for ; Fri, 13 Aug 1999 21:26:17 -0700 (PDT) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id VAA10524; Fri, 13 Aug 1999 21:25:47 -0700 (PDT) Date: Fri, 13 Aug 1999 21:25:45 -0700 (PDT) From: Tom Bartol To: Mike Smith Cc: "David E. Cross" , current@FreeBSD.ORG Subject: Re: yet more TP 600E fun... In-Reply-To: <199908140010.RAA02069@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd be more than happy to do the pestering if some one could write down a detailed description of exactly how the TP's BIOS is non-compliant. I don't know enough about the boot process and BIOS to write such a description. Tom On Fri, 13 Aug 1999, Mike Smith wrote: > > I attempt to boot a CD off of the TP600E and I get the following errors: > > > > "Can't work out which disk we are booting from." > > "Guessed BIOS device 0x8b not found by probes, defaulting to disk0:" > > > > Then whenever it attmpts to access "disk0:" it goes to the floppy drive. > > > > Suggestions? > > Known weirdness in the TP's BIOS not handled properly by the > bootloader. I don't have immediate plans to do anything about this; > you could try hacking the loader to accept the 0x8b value and see if > that actually works. Or you could pester IBM to DTRT. > > -- > \\ The mind's the standard \\ Mike Smith > \\ of the man. \\ msmith@freebsd.org > \\ -- Joseph Merrick \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 21:48:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94]) by hub.freebsd.org (Postfix) with ESMTP id B1EDC14F91 for ; Fri, 13 Aug 1999 21:48:29 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA00388; Fri, 13 Aug 1999 21:43:23 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908140443.VAA00388@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh Cc: "Ron Klinkien" , freebsd-current@FreeBSD.ORG Subject: Re: Problems with 4.0 keyboard input! In-reply-to: Your message of "Fri, 13 Aug 1999 19:49:12 MDT." <199908140149.TAA12820@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Aug 1999 21:43:22 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <000001bee5f0$c467c7c0$0264a8c0@.demon.nl> "Ron Klinkien" writes: > : After building a few succesfull 4.0 releases (last cvsupped on 13 aug 99), > : the keyboard is acting very strange, i cannot login, > : i get only strange characters, and when I hit CTRL I get: > : > : load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K > : load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K > : load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K > > I get that too from time to time. I think that the boot blocks are > putting the keyboard into an odd state since I sometimes can't break > into the boot sequence to boot an alternate kernel. So far it has > been confined to my Sony VAIO. Never could come up with a good test > case for it, however.... It's not the boot blocks doing anything explicit; they just use the BIOS. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 21:54:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 352C914FCE for ; Fri, 13 Aug 1999 21:54:44 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA29185; Fri, 13 Aug 1999 22:54:54 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA13749; Fri, 13 Aug 1999 22:55:03 -0600 (MDT) Message-Id: <199908140455.WAA13749@harmony.village.org> To: Mike Smith Subject: Re: Problems with 4.0 keyboard input! Cc: "Ron Klinkien" , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 13 Aug 1999 21:43:22 PDT." <199908140443.VAA00388@dingo.cdrom.com> References: <199908140443.VAA00388@dingo.cdrom.com> Date: Fri, 13 Aug 1999 22:55:03 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908140443.VAA00388@dingo.cdrom.com> Mike Smith writes: : It's not the boot blocks doing anything explicit; they just use the BIOS. I have noticed that boot[12] doesn't seem to have this problem. However, after /boot/loader has been loaded, I see this problem from time to time. I don't know what is going on, I'm just reporting what I've seen.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 22: 9: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94]) by hub.freebsd.org (Postfix) with ESMTP id 4EF1115054 for ; Fri, 13 Aug 1999 22:08:51 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA00524; Fri, 13 Aug 1999 22:02:59 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908140502.WAA00524@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Tom Bartol Cc: Mike Smith , "David E. Cross" , current@FreeBSD.ORG Subject: Re: yet more TP 600E fun... In-reply-to: Your message of "Fri, 13 Aug 1999 21:25:45 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Aug 1999 22:02:58 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'd be more than happy to do the pestering if some one could write down > a detailed description of exactly how the TP's BIOS is non-compliant. > I don't know enough about the boot process and BIOS to write such a > description. It's expected that the BIOS numbers disk units sequentially; floppies from 0 upwards, fixed-disk devices from 0x80 upwards. The loader searches upwards from 0 and from 0x80 until it fails to find a unit and stops there. It doesn't search all of the unit numbers because many BIOS implementations seem to wrap, eg. you may find that unit 0x90 is the same as unit 0x80. You can't be sure about where the wrap point will be, either. Normally, when you're booting an El Torito image, the virtual floppy is substituted for drive 0 (ie. you can't get at the real first floppy drive). I can see why IBM would move it elsewhere, but 0x8b is just about the most stupid place they could have put it. This is the code (in /sys/boot/i386/libi386/biosdisk.c) that probes for BIOS disk units. You try replacing the 'break' with 'continue' and see if it finds a device at 0x8b. If it does, let me know and I'll send you some more complete patches that will always probe the claimed boot device. static int bd_init(void) { int base, unit; /* sequence 0, 0x80 */ for (base = 0; base <= 0x80; base += 0x80) { for (unit = base; (nbdinfo < MAXBDDEV); unit++) { bdinfo[nbdinfo].bd_unit = unit; bdinfo[nbdinfo].bd_flags = (unit < 0x80) ? BD_FLOPPY : 0; /* XXX add EDD probes */ if (!bd_int13probe(&bdinfo[nbdinfo])) break; /* XXX we need "disk aliases" to make this simpler */ printf("BIOS drive %c: is disk%d\n", (unit < 0x80) ? ('A' + unit) : ('C' + unit - 0x80), nbdinfo); nbdinfo++; } } return(0); } > Tom > > > On Fri, 13 Aug 1999, Mike Smith wrote: > > > > I attempt to boot a CD off of the TP600E and I get the following errors: > > > > > > "Can't work out which disk we are booting from." > > > "Guessed BIOS device 0x8b not found by probes, defaulting to disk0:" > > > > > > Then whenever it attmpts to access "disk0:" it goes to the floppy drive. > > > > > > Suggestions? > > > > Known weirdness in the TP's BIOS not handled properly by the > > bootloader. I don't have immediate plans to do anything about this; > > you could try hacking the loader to accept the 0x8b value and see if > > that actually works. Or you could pester IBM to DTRT. > > > > -- > > \\ The mind's the standard \\ Mike Smith > > \\ of the man. \\ msmith@freebsd.org > > \\ -- Joseph Merrick \\ msmith@cdrom.com > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 13 22:10:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94]) by hub.freebsd.org (Postfix) with ESMTP id ED76E15054 for ; Fri, 13 Aug 1999 22:10:37 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA00566; Fri, 13 Aug 1999 22:05:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908140505.WAA00566@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh Cc: Mike Smith , "Ron Klinkien" , freebsd-current@FreeBSD.ORG Subject: Re: Problems with 4.0 keyboard input! In-reply-to: Your message of "Fri, 13 Aug 1999 22:55:03 MDT." <199908140455.WAA13749@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Aug 1999 22:05:31 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199908140443.VAA00388@dingo.cdrom.com> Mike Smith writes: > : It's not the boot blocks doing anything explicit; they just use the BIOS. > > I have noticed that boot[12] doesn't seem to have this problem. > However, after /boot/loader has been loaded, I see this problem from > time to time. I don't know what is going on, I'm just reporting what > I've seen.... *mumble* We're seeing a few cases where BIOS code in the boot path isn't working too well (or at all) when run in vm86 mode. 8( -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 0:10:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (Postfix) with ESMTP id 7B0B114D2C for ; Sat, 14 Aug 1999 00:10:36 -0700 (PDT) (envelope-from kfarmer@sympatico.ca) Received: from sympatico.ca (ppp12815.on.bellglobal.com [206.172.162.14]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id DAA01057 for ; Sat, 14 Aug 1999 03:14:19 -0400 (EDT) Message-ID: <37B516C7.C5F45D04@sympatico.ca> Date: Sat, 14 Aug 1999 07:12:07 +0000 From: Kelvin Farmer X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: apm problems. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Apm does not seem to be behaving correctly on my computer (running yesterday's CURRENT) eg: with a make world running, the following happens after about 15 mins of not touching the keyboard. Received APM Event: PMEV_STANDBYREQ Execute APM hook "pcm suspend handler" Called APM sound suspend hook for unit 1 Execute APM hook "default suspend" However, disk activity continues and the monitor isn't blanked. then, if a key is pressed: Recieved APM Event: PMEV_STANDBYRESUME Execute APM hook "default resume" resume from suspended mode (Slept 00:28:34) Execute APM Hook "pcm resume handler" Called APM sound resume hook for unit 1 If apm -z is given, then the computer does go to sleep, monitor blanks, no disk activity. However, if apm -z is used while the computer is doing something (eg: compiling a kernel) then the computer goes to sleep, and everything stops, but will not wake up properly. no new process can be started ie: any command typed in starts but does not appear to do anything, and can't be stopped (control -c) if top is runing before apm -z is done then after resuming,top shows and continues to update: process state top RUN make SELECT ld getblk apmd biord syncer drainv etc. alt-ctl-delete also does not work. if more info is needed, just let me know what to do. Thanks =). (I also don't need the apm features of the motherboard that much, so if its likely to take a lot of work making apm work right just for this motherboard it probably isn't worth the effort) DMESG: apm0: on motherboard apm: APM BIOS version 0102 apm: Code16 0xc00f0000, Data 0xc0000400 apm: Code entry 0x0000ef50, Idling CPU disabled, Management enabled apm: CS_limit=0xffff, DS_limit=0xffff apm: Engaged control enabled apm: found APM BIOS v1.2, connected at v1.2 apm: Slow Idling CPU disabled Add hook "default suspend" Add hook "default resume" [I didn't originally have the 'idling CPU disabled' set in the bios, but then the cpu would be put into a slow state while actually busy, resulting in make world taking many more hours than usual...] apm: APM version: 1.2 APM Managment: Enabled AC Line status: on-line Battery status: unknown Remaining battery life: unknown Remaining battery time: unknown Number of batteries: 0 Resume timer: Wed Dec 31 18:59:59 1969 Resume on ring indicator: enabled APM Capacities: global standby state global suspend state resume timer from suspend -- kfarmer@sympatico.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 1: 9:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id DA57915143 for ; Sat, 14 Aug 1999 01:09:34 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id RAA03114; Sat, 14 Aug 1999 17:08:14 +0900 (JST) Message-ID: <37B52262.A5A6EDB7@newsguy.com> Date: Sat, 14 Aug 1999 17:01:38 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Mike Smith Cc: Warner Losh , Ron Klinkien , freebsd-current@FreeBSD.ORG Subject: Re: Problems with 4.0 keyboard input! References: <199908140505.WAA00566@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > In message <199908140443.VAA00388@dingo.cdrom.com> Mike Smith writes: > > : It's not the boot blocks doing anything explicit; they just use the BIOS. > > > > I have noticed that boot[12] doesn't seem to have this problem. > > However, after /boot/loader has been loaded, I see this problem from > > time to time. I don't know what is going on, I'm just reporting what > > I've seen.... > > *mumble* We're seeing a few cases where BIOS code in the boot path > isn't working too well (or at all) when run in vm86 mode. 8( I think it's interrupt-related. A race somewhere. From time to time, if I'm pressing keys during the early stages of boot, the keyboard will freeze. It's rare, and it only happens when I'm pressing keys during the early stages of boot. Alas, I have seen this happen before, with OS/2 Boot Manager, so I take it for granted. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "You intend to eat me, then?" he asked the dragon. "Well, I must admit, more for the amusement than the taste." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 2:49: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30]) by hub.freebsd.org (Postfix) with ESMTP id 7958914DF7 for ; Sat, 14 Aug 1999 02:48:51 -0700 (PDT) (envelope-from ron@zappa.demon.nl) Received: from win98 (win98.demon.nl [192.168.100.2]) by zappa.demon.nl (8.9.3/8.9.3) with ESMTP id LAA03391; Sat, 14 Aug 1999 11:48:50 +0200 (CEST) (envelope-from ron@zappa.demon.nl) From: "Ron Klinkien" To: , Subject: RE: Problems with 4.0 keyboard input! Date: Sat, 14 Aug 1999 15:48:38 +0200 Message-ID: <000401bee65b$b6fd0440$0264a8c0@.demon.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: <19990813212134.3021.rocketmail@web1002.mail.yahoo.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Brian, >I get the bktr device usurping its own cdevsw[] as well - I was >told it was "most likely" benign, so I've been waiting for >others' comments. I have looked in the source code, but what does usurping means? My English is not that good ;) The messages comes from /usr/src/sys/kern/kern_conf.c >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. Thats what I have been doing the last five reboots, I pressed Return to let it boot faster. I shall try without. >Resetting seems to be the only remedy. This persists with two >different keyboard models and on unplugging and reinserting the >keyboard. ---- cut ----- ata0: master: setting up UDMA2 mode on PIIX4 chip OK ad0: ATA-4 disk at ata0 as master ad0: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 31 depth queue, DMA mode ata0: slave: setting up UDMA2 mode on PIIX4 chip OK ad1: ATA-4 disk at ata0 as slave ad1: 21557MB (44150400 sectors), 43800 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 31 depth queue, DMA mode ata1: master: setting up UDMA2 mode on PIIX4 chip OK ad2: ATA-4 disk at ata1 as master ad2: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S --- cut ---- Do you have enough disk space ;-))) Thanks for you reaction. Regards, Ron. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 3: 1:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from mpp.pro-ns.net (mpp.pro-ns.net [208.200.182.72]) by hub.freebsd.org (Postfix) with ESMTP id 4823E1510C for ; Sat, 14 Aug 1999 03:01:52 -0700 (PDT) (envelope-from mpp@mpp.pro-ns.net) Received: (from mpp@localhost) by mpp.pro-ns.net (8.9.3/8.9.3) id EAA05910; Sat, 14 Aug 1999 04:26:34 -0500 (CDT) (envelope-from mpp) From: Mike Pritchard Message-Id: <199908140926.EAA05910@mpp.pro-ns.net> Subject: Re: Problems with 4.0 keyboard input! In-Reply-To: <199908140149.TAA12820@harmony.village.org> from Warner Losh at "Aug 13, 1999 07:49:12 pm" To: imp@village.org (Warner Losh) Date: Sat, 14 Aug 1999 04:26:34 -0500 (CDT) Cc: ron@zappa.demon.nl (Ron Klinkien), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <000001bee5f0$c467c7c0$0264a8c0@.demon.nl> "Ron Klinkien" writes: > : After building a few succesfull 4.0 releases (last cvsupped on 13 aug 99), > : the keyboard is acting very strange, i cannot login, > : i get only strange characters, and when I hit CTRL I get: > : > : load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K > : load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K > : load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K > > I get that too from time to time. I think that the boot blocks are > putting the keyboard into an odd state since I sometimes can't break > into the boot sequence to boot an alternate kernel. So far it has > been confined to my Sony VAIO. Never could come up with a good test > case for it, however.... I've gotten my some login prompts on a vty to mess up like this by leaving a book or something sitting on the keyboard at a vty login prompt. Most of the times it will let you type alphanumeric characters in, so you can login via that vty. Once or twice it just totally hosed up the vty login, and everything I typed acted like I typed control-t and gave me the status message, or printed out odd control characters. It wouldn't even let me switch to a different vty. If I let it sit for long enough, the login would timeout, and it went back to normal. -Mike -- Mike Pritchard mpp@FreeBSD.ORG or mpp@mpp.pro-ns.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 3: 8: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id A73CE151DE for ; Sat, 14 Aug 1999 03:07:53 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id MAA10636; Sat, 14 Aug 1999 12:07:56 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Ron Klinkien" Cc: brian@pobox.com, freebsd-current@FreeBSD.ORG Subject: Re: Problems with 4.0 keyboard input! In-reply-to: Your message of "Sat, 14 Aug 1999 15:48:38 +0200." <000401bee65b$b6fd0440$0264a8c0@.demon.nl> Date: Sat, 14 Aug 1999 12:07:55 +0200 Message-ID: <10634.934625275@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <000401bee65b$b6fd0440$0264a8c0@.demon.nl>, "Ron Klinkien" writes: >>I get the bktr device usurping its own cdevsw[] as well - I was >>told it was "most likely" benign, so I've been waiting for >>others' comments. > >I have looked in the source code, but what does usurping means? >My English is not that good ;) It means "to take or assume and hold (something) by force or without right". Usually used about power in subsaharan our south american countries. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 5:48:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 2E0D914E94 for ; Sat, 14 Aug 1999 05:48:30 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11FdBu-000O98-00; Sat, 14 Aug 1999 14:45:42 +0200 From: Sheldon Hearn To: Ben Rosengart Cc: current@FreeBSD.ORG Subject: Re: SUPFLAGS in /etc/make.conf In-reply-to: Your message of "Fri, 13 Aug 1999 15:17:47 -0400." Date: Sat, 14 Aug 1999 14:45:42 +0200 Message-ID: <92821.934634742@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Aug 1999 15:17:47 -0400, Ben Rosengart wrote: > I submit that putting "-z" in here is silly, because the sample cvsup > config files turn on compression, and suggest commenting it out if you > have a fast link. It seems counterintuitive that one can comment out > the compression in the standard supfiles and then have it enabled by > default with "make update" anyway. This looks like PR material. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 7: 6:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 1F0861518E for ; Sat, 14 Aug 1999 07:06:24 -0700 (PDT) (envelope-from n_hibma@skylink.it) Received: from heidi.plazza.it (va-148.skylink.it [194.185.55.148]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id QAA04943; Sat, 14 Aug 1999 16:06:22 +0200 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id NAA01050; Sat, 14 Aug 1999 13:30:58 GMT Date: Sat, 14 Aug 1999 13:30:58 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Ron Klinkien Cc: freebsd-current@freebsd.org Subject: RE: Problems with 4.0 keyboard input! In-Reply-To: <000401bee65b$b6fd0440$0264a8c0@.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have looked in the source code, but what does usurping means? > My English is not that good ;) 'opslorpen' in Dutch. Nick -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 7: 6:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 70B5C151A9 for ; Sat, 14 Aug 1999 07:06:26 -0700 (PDT) (envelope-from n_hibma@skylink.it) Received: from heidi.plazza.it (va-148.skylink.it [194.185.55.148]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id QAA04946 for ; Sat, 14 Aug 1999 16:06:24 +0200 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id NAA01067; Sat, 14 Aug 1999 13:37:14 GMT Date: Sat, 14 Aug 1999 13:37:13 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Sheldon Hearn Cc: Ben Rosengart , current@freebsd.org Subject: Re: SUPFLAGS in /etc/make.conf In-Reply-To: <92821.934634742@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This looks like commit it and see what happens to me. Nick On Sat, 14 Aug 1999, Sheldon Hearn wrote: > > > On Fri, 13 Aug 1999 15:17:47 -0400, Ben Rosengart wrote: > > > I submit that putting "-z" in here is silly, because the sample cvsup > > config files turn on compression, and suggest commenting it out if you > > have a fast link. It seems counterintuitive that one can comment out > > the compression in the standard supfiles and then have it enabled by > > default with "make update" anyway. > > This looks like PR material. :-) > > Ciao, > Sheldon. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 10:19:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30]) by hub.freebsd.org (Postfix) with ESMTP id AA4B11523E for ; Sat, 14 Aug 1999 10:19:48 -0700 (PDT) (envelope-from ron@zappa.demon.nl) Received: from win98 (win98.demon.nl [192.168.100.2]) by zappa.demon.nl (8.9.3/8.9.3) with ESMTP id TAA10937; Sat, 14 Aug 1999 19:20:51 +0200 (CEST) (envelope-from ron@zappa.demon.nl) From: "Ron Klinkien" To: "'Poul-Henning Kamp'" Cc: , Subject: RE: Problems with 4.0 keyboard input! Date: Sat, 14 Aug 1999 23:20:38 +0200 Message-ID: <000501bee69a$dbe7b4a0$0264a8c0@.demon.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: <10634.934625275@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <000401bee65b$b6fd0440$0264a8c0@.demon.nl>, "Ron Klinkien" writes: >>I get the bktr device usurping its own cdevsw[] as well - I was >>told it was "most likely" benign, so I've been waiting for >>others' comments. > >I have looked in the source code, but what does usurping means? >My English is not that good ;) >>It means "to take or assume and hold (something) by force or without >>right". Usually used about power in subsaharan our south american >>countries. Aha ok. Thanks for the explanation. Ron. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 11:43:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 5FFFD1563F for ; Sat, 14 Aug 1999 11:43:22 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (5561 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sat, 14 Aug 1999 11:41:45 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Sat, 14 Aug 1999 11:41:45 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: a couple of warnings Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG asus p2b-ds, dual P2/350s, 128mb current as of 99.08.13 evening dmesg has a few things which worry me. but the hauppauge/brootree works fine with mbone tools and fxtv. randy Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sat Aug 14 09:01:38 PDT 1999 root@rip.psg.com:/usr/src/sys/compile/RIP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183fbff real memory = 134205440 (131060K bytes) config> pnp 1 0 enable os port0 0x220 port1 0x330 port2 0x388 irq0 5 drq0 1 drq1 5 config> pnp 1 1 enable os port0 0x200 config> pnp 1 2 enable os port0 0x620 port1 0xa20 port2 0xe20 config> quit avail memory = 126959616 (123984K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02f5000. Preloaded userconfig_script "/kernel.config" at 0xc02f509c. Pentium Pro MTRR support enabled ccd0-5: Concatenated disk drivers Probing for PnP devices: CSN 1 Vendor ID: CTL00c3 [0xc3008c0e] Serial 0x1fd0a682 Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp sn 0x1fd0a682) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 WARNING: "bktr" is usurping "bktr"'s cdevsw[] <<<*********************** pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 16 at device 0.0 on pci1 isab0: at device 4.0 on pci0 chip1: at device 4.1 on pci0 chip2: irq 19 at device 4.2 on pci0 intpm0: at device 4.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped e400 ahc0: irq 19 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: irq 19 at device 9.0 on pci0 fxp0: Ethernet address 00:a0:c9:df:c8:4e bktr0: irq 18 at device 10.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only iicsmb0: on iicbus0 smbus1: on iicsmb0 smb1: on smbus1 WARNING: "iic" is usurping "iic"'s cdevsw[] <<<*********************** iic0: on iicbus0 smbus2: on bti2c0 smb2: on smbus2 Hauppauge Model 61111 A M Hauppauge WinCast/TV, Philips NTSC tuner, msp3400c stereo. Detected a MSP3430G-A1 pci0: unknown card DD^0878 (vendor=0x109e, dev=0x0878) at 10.1 irq 18 isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <4 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A wl0 at port 0x300-0x30f irq 7 on isa0 wl0: address 08:00:6a:2b:dd:a7, NWID 0xaaaa APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 wl0 XXX: driver didn't set ifq_maxlen Waiting 15 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 5 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 8.333MB/s transfers (8.333MHz, offset 31) cd1: cd present [140956 x 2048 byte records] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 11:56: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from io.yi.org (24.66.174.118.bc.wave.home.com [24.66.174.118]) by hub.freebsd.org (Postfix) with ESMTP id AAE2B14C2B for ; Sat, 14 Aug 1999 11:55:52 -0700 (PDT) (envelope-from jake@checker.org) Received: from io.yi.org (localhost [127.0.0.1]) by io.yi.org (Postfix) with ESMTP id DD9DA1FBC; Sat, 14 Aug 1999 11:55:15 -0700 (PDT) X-Mailer: exmh version 2.0.2 2/24/98 To: Randy Bush Cc: FreeBSD Current Subject: Re: a couple of warnings In-reply-to: Your message of "Sat, 14 Aug 1999 11:41:45 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Aug 1999 11:55:15 -0700 From: Jake Burkholder Message-Id: <19990814185515.DD9DA1FBC@io.yi.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > asus p2b-ds, dual P2/350s, 128mb > current as of 99.08.13 evening > > dmesg has a few things which worry me. but the hauppauge/brootree works > fine with mbone tools and fxtv. > > WARNING: "bktr" is usurping "bktr"'s cdevsw[] <<<************* > WARNING: "iic" is usurping "iic"'s cdevsw[] <<<************* As is understand it, these are just advisory and can be safely ignored; I get the same messages. -- we are but packets in the internet of life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 12:19:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles547.castles.com [208.214.165.111]) by hub.freebsd.org (Postfix) with ESMTP id 7EAA014EDC for ; Sat, 14 Aug 1999 12:19:52 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA07736; Sat, 14 Aug 1999 12:13:47 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908141913.MAA07736@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jake Burkholder Cc: Randy Bush , FreeBSD Current Subject: Re: a couple of warnings In-reply-to: Your message of "Sat, 14 Aug 1999 11:55:15 PDT." <19990814185515.DD9DA1FBC@io.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Aug 1999 12:13:46 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > asus p2b-ds, dual P2/350s, 128mb > > current as of 99.08.13 evening > > > > dmesg has a few things which worry me. but the hauppauge/brootree works > > fine with mbone tools and fxtv. > > > > WARNING: "bktr" is usurping "bktr"'s cdevsw[] <<<************* > > WARNING: "iic" is usurping "iic"'s cdevsw[] <<<************* > > As is understand it, these are just advisory and can be safely ignored; > I get the same messages. Actually, they're caused by the driver registering it's cdev twice; they're harmless but indicate that the driver needs to be fixed. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 12:55:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48]) by hub.freebsd.org (Postfix) with ESMTP id ECE6C15254 for ; Sat, 14 Aug 1999 12:55:42 -0700 (PDT) (envelope-from plm@smtp1.xs4all.nl) Received: from localhost. (dc2-isdn1937.dial.xs4all.nl [194.109.155.145]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id VAA27095; Sat, 14 Aug 1999 21:55:41 +0200 (CEST) Received: (from plm@localhost) by localhost. (8.9.3/8.9.3) id VAA01810; Sat, 14 Aug 1999 21:55:38 +0200 From: Peter Mutsaers MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14261.51641.622430.411111@muon.xs4all.nl> Date: Sat, 14 Aug 1999 21:55:37 +0200 (CEST) To: Mike Smith Cc: Mitsuru IWASAKI , freebsd-current@FreeBSD.ORG Subject: Re: recent apm changes In-Reply-To: <199908132355.QAA01992@dingo.cdrom.com> References: <14259.9442.775107.16749@muon.xs4all.nl> <199908132355.QAA01992@dingo.cdrom.com> X-Mailer: VM 6.65 under Emacs 20.3.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> "MS" == Mike Smith writes: >> Then after 5 seconds the screen blanks, the power light starts >> flashing (indicating suspend mode), but when I hit a key, the >> console says (slept 00:00:02) only, and programs in fact >> continued running (thus it didn't go or remain in suspend mode >> at all). MS> I think you'll find that programs didn't, in fact, continue MS> running; rather they paused and then resumed when you came out MS> of suspend. I'm running seti@home, and it really continued while my computer was 'suspended'. Also a little test program continued running. -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know plm@xs4all.nl | the Netherlands | what I'm doing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 13: 0:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles547.castles.com [208.214.165.111]) by hub.freebsd.org (Postfix) with ESMTP id 37AA415254 for ; Sat, 14 Aug 1999 13:00:23 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA07929; Sat, 14 Aug 1999 12:54:19 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908141954.MAA07929@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Mutsaers Cc: freebsd-current@FreeBSD.ORG Subject: Re: recent apm changes In-reply-to: Your message of "Sat, 14 Aug 1999 21:55:37 +0200." <14261.51641.622430.411111@muon.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Aug 1999 12:54:19 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> "MS" == Mike Smith writes: > > >> Then after 5 seconds the screen blanks, the power light starts > >> flashing (indicating suspend mode), but when I hit a key, the > >> console says (slept 00:00:02) only, and programs in fact > >> continued running (thus it didn't go or remain in suspend mode > >> at all). > > MS> I think you'll find that programs didn't, in fact, continue > MS> running; rather they paused and then resumed when you came out > MS> of suspend. > > I'm running seti@home, and it really continued while my computer was > 'suspended'. Also a little test program continued running. What you're failing to offer here, and thus why I remain skeptical, is any evidence that suggests that these programs were "running" while the system believed itself to be suspended. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 16:22: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id B83021516B for ; Sat, 14 Aug 1999 16:22:04 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (602 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sat, 14 Aug 1999 16:19:20 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Sat, 14 Aug 1999 16:19:20 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-current@freebsd.org Subject: pex5 and xie load errors Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i just upgraded to current. i still have the following in my /etc/XF86Config Section "Module" Load "pex5.so" Load "xie.so" EndSection during X startup i get load errors for these. but i can see nothing unappy with X. do i delete them from /etc/XF86Config or rebuild X or what? thanks. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 18:30:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from exegrnnts001.seattleu.edu (exegrnnts001.seattleu.edu [206.81.198.91]) by hub.freebsd.org (Postfix) with ESMTP id 38823152A0 for ; Sat, 14 Aug 1999 18:30:34 -0700 (PDT) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu (ppp27.pm3b.wport.com [206.129.99.174]) by exegrnnts001.seattleu.edu with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id QS0G8N3W; Sat, 14 Aug 1999 18:30:31 -0700 Message-ID: <37B615E9.81EFBACC@seattleu.edu> Date: Sat, 14 Aug 1999 18:20:42 -0700 From: Eric Hodel Organization: Dis X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Problems with 4.0 keyboard input! References: <000001bee5f0$c467c7c0$0264a8c0@.demon.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ron Klinkien wrote: > > Hello, > > After building a few succesfull 4.0 releases (last cvsupped on 13 aug 99), > the keyboard is acting very strange, i cannot login, > i get only strange characters, and when I hit CTRL I get: > > load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K > load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K > load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K > > Login through the network with telnet is no problem.... Here's another 'me too,' only I get it with 3.2-RELEASE PAO on a Dell Latitude LM. -- Eric Hodel hodeleri@seattleu.edu "They cook your gonies" -Terry Lambert's uncle on why he doesn't have a microwave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 19:19:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from saturn.terahertz.net (saturn.terahertz.net [209.83.5.170]) by hub.freebsd.org (Postfix) with ESMTP id C73FA151EA for ; Sat, 14 Aug 1999 19:19:30 -0700 (PDT) (envelope-from sideshow@saturn.terahertz.net) Received: from localhost (sideshow@localhost) by saturn.terahertz.net (8.9.3/8.9.3) with ESMTP id VAA45660 for ; Sat, 14 Aug 1999 21:17:22 -0500 (CDT) Date: Sat, 14 Aug 1999 21:17:22 -0500 (CDT) From: Matt Watson To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 19:20:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id C7D28151EA for ; Sat, 14 Aug 1999 19:20:22 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id WAA56500; Sat, 14 Aug 1999 22:21:14 -0400 (EDT) Date: Sat, 14 Aug 1999 22:21:14 -0400 (EDT) From: Ben Rosengart To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: SUPFLAGS in /etc/make.conf In-Reply-To: <92821.934634742@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Aug 1999, Sheldon Hearn wrote: > On Fri, 13 Aug 1999 15:17:47 -0400, Ben Rosengart wrote: > > This looks like PR material. :-) conf/13147 -- Ben UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 14 22:34:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id EDCFA152C4 for ; Sat, 14 Aug 1999 22:34:44 -0700 (PDT) (envelope-from jhs@jhs.muc.de) Received: (qmail 19130 invoked from network); 15 Aug 1999 05:34:15 -0000 Received: from jhs.muc.de (193.149.49.84) by slarti.muc.de with SMTP; 15 Aug 1999 05:34:15 -0000 Received: from wall.jhs.no_domain (localhost [127.0.0.1]) by jhs.muc.de (8.9.3/8.9.3) with ESMTP id OAA02141; Sat, 14 Aug 1999 14:20:06 GMT (envelope-from jhs@wall.jhs.no_domain) Message-Id: <199908141420.OAA02141@jhs.muc.de> To: current@FreeBSD.ORG Cc: "Matthew N. Dodd" Subject: Re: it's time... From: "Julian Stacey" Reply-To: "Julian Stacey" X-Net: jhs@muc.de jhs@freebsd.org www.jhs.muc.de www.freebsd.org/~jhs/ Organization: Vector Systems Ltd In-reply-to: Your message of "Thu, 12 Aug 1999 01:29:32 EDT." Date: Sat, 14 Aug 1999 16:20:05 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > > Agreed. I like what I see there. Maybe it is time to hoist something > > like that into bus_subr.c > Lets define exactly what we want before we start our charge. > What should be printed? > device ID > attachment point > resource reservation > device additional > When should it be printed? > bootverbose levels? Years ago I provided diffs to the kernel boot to report some probes Before as well as after, so one could see which probe was about to hang, - more use than which probe was last to pass. Idea was rejected as some thought it was too verbose, but Nobody (me included) thought of having a bootverbose levels switch to hang on it on. ... Nice Idea ! Some Computer mags reccomend MS-* users to keep a boot flop for Linux or BSD, as we provide much more diagnostics than MS*, Before-probe-announcements would make it more valuable still. Imagine if the more competent of the MS crowd actually wanted to keep a FreeBSD boot floppy around :-) Julian Julian H. Stacey http://www.freebsd.org/~jhs/ Considering Linux ? Then also consider the 2000+ free packages for FreeBSD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message