From owner-freebsd-alpha Sun May 28 23:47:32 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 4836E37BBD6 for ; Sun, 28 May 2000 23:47:28 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (nobody@relay.nuxi.com [169.237.7.38]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA22527 for ; Sun, 28 May 2000 23:47:25 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA47144 for alpha@freebsd.org; Sun, 28 May 2000 23:47:17 -0700 (PDT) (envelope-from obrien) Date: Sun, 28 May 2000 23:47:16 -0700 From: "David O'Brien" To: alpha@freebsd.org Subject: Interesting article compairing the speed of the DS10 vs. Athlon 850 Message-ID: <20000528234716.A47110@dragon.nuxi.com> Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Of course take the benchmarks with a grain of salt. But interesting never the less. From www.alphalinux.org: Ace's Hardware is running a review of a Compaq DS10, comparing it with an Athlon and Pentium III. There are a few mistakes in the article (highest clock speed available and Flashing of ROMs) but they did make the comparisons using the Compaq C compilers not just gcc. http://www.aceshardware.com/Spades/read.php?article_id=145 -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue May 30 9:29:49 2000 Delivered-To: freebsd-alpha@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id C81A937B892; Tue, 30 May 2000 09:29:46 -0700 (PDT) Subject: Re: Looking for testers for if_dc patches In-Reply-To: <20000530175945.A20508@cicely7.cicely.de> from Bernd Walter at "May 30, 2000 05:59:45 pm" To: ticso@cicely.de (Bernd Walter) Date: Tue, 30 May 2000 09:29:46 -0700 (PDT) Cc: current@FreeBSD.ORG, alpha@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 Message-Id: <20000530162946.C81A937B892@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Tue, May 30, 2000 at 12:28:25AM -0700, Bill Paul wrote: > > Several people have reported problems with if_dc botching autonegotiation > > on 21143 NICs with non-MII media, such as the DEC/Compaq DE500-BA and > > the built-in 10/100 ethernet on some alphas. As my first official act > > as a BSDi/WC employee, I sat down and tried to fix this. I produced > > some patches for if_dc.c/if_dcreg.h and dcphy.c, which are sitting at > > http://people.freebsd.org/~wpaul/dc_test. To apply them, do the following: > > [...] > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing -prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -ffixed-8 -Wa,-mev56 ../../pci/if_dc.c > ../../pci/if_dc.c: In function `dc_init': > ../../pci/if_dc.c:2697: structure has no member named `dc_flgs' > *** Error code 1 > > Stop in /var/d7/src-2000-05-28/src/sys/compile/CICELY9. > > This is on 5.0-CURRENT as of 28th May on alpha Grrr. Typo on my part, sorry. It should be flags, not flgs. I just fixed the patch file. You can download it again, or just correct the typo manually. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed May 31 3:31: 3 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id 0767D37B816; Wed, 31 May 2000 03:30:55 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000531103041.BGSG13476.relay02@chello.nl>; Wed, 31 May 2000 12:30:41 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id MAA86941; Wed, 31 May 2000 12:30:52 +0200 (CEST) (envelope-from wkb) Date: Wed, 31 May 2000 12:30:51 +0200 From: Wilko Bulte To: Bill Paul Cc: Bernd Walter , current@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: Looking for testers for if_dc patches Message-ID: <20000531123051.A86871@freebie.wbnet> Reply-To: wc.bulte@chello.nl References: <20000530175945.A20508@cicely7.cicely.de> <20000530162946.C81A937B892@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000530162946.C81A937B892@hub.freebsd.org>; from wpaul@FreeBSD.ORG on Tue, May 30, 2000 at 09:29:46AM -0700 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, May 30, 2000 at 09:29:46AM -0700, Bill Paul wrote: > > On Tue, May 30, 2000 at 12:28:25AM -0700, Bill Paul wrote: > > > Several people have reported problems with if_dc botching autonegotiation > > > on 21143 NICs with non-MII media, such as the DEC/Compaq DE500-BA and > > > the built-in 10/100 ethernet on some alphas. As my first official act > > > as a BSDi/WC employee, I sat down and tried to fix this. I produced > > > some patches for if_dc.c/if_dcreg.h and dcphy.c, which are sitting at > > > http://people.freebsd.org/~wpaul/dc_test. To apply them, do the following: > > > > [...] > > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing -prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -ffixed-8 -Wa,-mev56 ../../pci/if_dc.c > > ../../pci/if_dc.c: In function `dc_init': > > ../../pci/if_dc.c:2697: structure has no member named `dc_flgs' > > *** Error code 1 > > > > Stop in /var/d7/src-2000-05-28/src/sys/compile/CICELY9. > > > > This is on 5.0-CURRENT as of 28th May on alpha > > Grrr. Typo on my part, sorry. It should be flags, not flgs. I just fixed > the patch file. You can download it again, or just correct the typo manually. Hi Bill, I applied your patches to -current without incidents. I have a testbox (Digital dual P6) that gives: May 31 10:56:38 p6 /kernel: dc0: port 0xec00-0xec7f m em 0xfdfffc00-0xfdfffc7f irq 9 at device 3.0 on pci0 May 31 10:56:38 p6 /kernel: dc0: Ethernet address: 00:00:f8:75:3c:6a May 31 10:56:38 p6 /kernel: miibus0: on dc0 May 31 10:56:38 p6 /kernel: dcphy0: on miibus 0 May 31 10:56:38 p6 /kernel: dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX- FDX, auto May 31 10:56:38 p6 /kernel: dc0: supplying EUI64: 00:00:f8:ff:fe:75:3c:6a May 31 10:56:38 p6 /kernel: isab0: at device 7 ... May 31 10:56:39 p6 /kernel: dc0: starting DAD for fe80:0001::0200:f8ff:fe75:3c6a May 31 10:56:39 p6 /kernel: dc0: DAD complete for fe80:0001::0200:f8ff:fe75:3c6a - no duplicates found May 31 10:56:43 p6 /kernel: dc0: watchdog timeout May 31 10:57:18 p6 last message repeated 3 times May 31 10:57:58 p6 /kernel: dc0: watchdog timeout May 31 10:58:53 p6 login: ROOT LOGIN (root) ON ttyv0 May 31 10:58:56 p6 login: ROOT LOGIN (root) ON ttyv0 May 31 10:59:57 p6 /kernel: dc0: watchdog timeout May 31 11:03:27 p6 /kernel: dc0: watchdog timeout This box can also house an Alpha Miata MX5 mainboard, the Intel & Alpha boards use the same PCI riser card that also contains the 21143 chip. The patches don't seem to help on this particular hardware. I will try to give the Alpha a spin too, later today. BTW: ifconfig-ing to use 10baseT/UTP does not help either. The media bulkhead is a 10baseT/10base2 one. if_de has no problems: May 31 11:12:21 p6 /kernel: de0: port 0xec00-0xec7 f mem 0xfdfffc00-0xfdfffc7f irq 9 at device 3.0 on pci0 May 31 11:12:21 p6 /kernel: de0: DEC 21142 [10-100Mb/s] pass 1.1 May 31 11:12:21 p6 /kernel: de0: address 00:00:f8:75:3c:6a May 31 11:12:21 p6 /kernel: de0: supplying EUI64: 00:00:f8:ff:fe:75:3c:6a May 31 11:12:21 p6 /kernel: isab0: at device ... May 31 11:12:21 p6 /kernel: de0: enabling 10baseT port Rather than repeating please see also: To: FreeBSD-alpha mailing list Subject: dc driver for embedded ethernet on Miata MX5 problems Message-ID: <20000406212804.A1731@yedi.wbnet> and PR: alpha/17833: dc driver for embedded ethernet on Miata MX5 problems Thanks for your efforts, please let me know if you want me to try something particular. -- Wilko Bulte FreeBSD, the power to serve http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed May 31 9:49:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 23DE137B8CC; Wed, 31 May 2000 09:49:26 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.10.1/8.10.1) with ESMTP id e4VGnNO04961; Wed, 31 May 2000 18:49:23 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id SAA24805; Wed, 31 May 2000 18:50:06 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id SAA84565; Wed, 31 May 2000 18:50:02 +0200 (CEST) (envelope-from ticso) Date: Wed, 31 May 2000 18:50:01 +0200 From: Bernd Walter To: wc.bulte@chello.nl Cc: Bill Paul , Bernd Walter , current@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: Looking for testers for if_dc patches Message-ID: <20000531185001.B83699@cicely8.cicely.de> References: <20000530175945.A20508@cicely7.cicely.de> <20000530162946.C81A937B892@hub.freebsd.org> <20000531123051.A86871@freebie.wbnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000531123051.A86871@freebie.wbnet>; from wkb@chello.nl on Wed, May 31, 2000 at 12:30:51PM +0200 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 31, 2000 at 12:30:51PM +0200, Wilko Bulte wrote: > On Tue, May 30, 2000 at 09:29:46AM -0700, Bill Paul wrote: > May 31 10:56:38 p6 /kernel: dc0: port > 0xec00-0xec7f m > em 0xfdfffc00-0xfdfffc7f irq 9 at device 3.0 on pci0 > May 31 10:56:38 p6 /kernel: dc0: Ethernet address: 00:00:f8:75:3c:6a > May 31 10:56:38 p6 /kernel: miibus0: on dc0 > May 31 10:56:38 p6 /kernel: dcphy0: on > miibus > 0 > May 31 10:56:38 p6 /kernel: dcphy0: 10baseT, 10baseT-FDX, 100baseTX, > 100baseTX- > FDX, auto Similar here on alpha with Adaptec 6911A without the watchdog timeouts. But after rereading the original mail I asume I'm on the wrong train as my card has an additional tranceiver which is not detected and the patch is for the internal one. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jun 1 10:29:50 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id 322CA37B827; Thu, 1 Jun 2000 10:29:31 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000601172913.MSPN13476.relay02@chello.nl>; Thu, 1 Jun 2000 19:29:13 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id TAA99302; Thu, 1 Jun 2000 19:29:23 +0200 (CEST) (envelope-from wkb) Date: Thu, 1 Jun 2000 19:29:23 +0200 From: Wilko Bulte To: wc.bulte@chello.nl Cc: Bill Paul , Bernd Walter , current@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: Looking for testers for if_dc patches Message-ID: <20000601192923.F99044@freebie.wbnet> Reply-To: wc.bulte@chello.nl References: <20000530175945.A20508@cicely7.cicely.de> <20000530162946.C81A937B892@hub.freebsd.org> <20000531123051.A86871@freebie.wbnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000531123051.A86871@freebie.wbnet>; from wkb@chello.nl on Wed, May 31, 2000 at 12:30:51PM +0200 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 31, 2000 at 12:30:51PM +0200, Wilko Bulte wrote: > On Tue, May 30, 2000 at 09:29:46AM -0700, Bill Paul wrote: > > > On Tue, May 30, 2000 at 12:28:25AM -0700, Bill Paul wrote: > > > > Several people have reported problems with if_dc botching autonegotiation > > > > on 21143 NICs with non-MII media, such as the DEC/Compaq DE500-BA and > > > > the built-in 10/100 ethernet on some alphas. As my first official act > > > > as a BSDi/WC employee, I sat down and tried to fix this. I produced > > > > some patches for if_dc.c/if_dcreg.h and dcphy.c, which are sitting at > > > > http://people.freebsd.org/~wpaul/dc_test. To apply them, do the following: > > > > > > [...] > boards use the same PCI riser card that also contains the 21143 chip. > The patches don't seem to help on this particular hardware. I will try > to give the Alpha a spin too, later today. BTW: ifconfig-ing to use I finally got around to try the Miata MX5. In short: the problem is the same as on the x86. The de driver works OK. -- Wilko Bulte FreeBSD, the power to serve http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jun 1 12:51:30 2000 Delivered-To: freebsd-alpha@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 8AE5F37B958; Thu, 1 Jun 2000 12:51:25 -0700 (PDT) Subject: Re: Looking for testers for if_dc patches In-Reply-To: <20000531123051.A86871@freebie.wbnet> from Wilko Bulte at "May 31, 2000 12:30:51 pm" To: wc.bulte@chello.nl Date: Thu, 1 Jun 2000 12:51:25 -0700 (PDT) Cc: ticso@cicely.de, current@FreeBSD.ORG, alpha@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 Message-Id: <20000601195125.8AE5F37B958@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi Bill, > > I applied your patches to -current without incidents. > > I have a testbox (Digital dual P6) that gives: > > May 31 10:56:38 p6 /kernel: dc0: port [...] > May 31 11:03:27 p6 /kernel: dc0: watchdog timeout > > This box can also house an Alpha Miata MX5 mainboard, the Intel & Alpha > boards use the same PCI riser card that also contains the 21143 chip. > The patches don't seem to help on this particular hardware. I will try > to give the Alpha a spin too, later today. BTW: ifconfig-ing to use > 10baseT/UTP does not help either. The media bulkhead is a 10baseT/10base2 > one. if_de has no problems: Alright, hold it. Stop. Just to make sure I understand: - There's one interface involved here - It has a 21143 chip - It has 10baseT and AUI ports - It's supposed to be 10Mbps only If this is all correct, then I'd like you to try the following: - Run pciconf -l on this machine and obtain the PCI ID for this device. The device ID is the hex number after the "chip=" section in the output. For the sake of this example, let's say it's 0x12345678. - Bring up /sys/dev/mii/dcphy.c in your favorite editor. - Look for the following code in the dcphy_attach() routine: case COMPAQ_PRESARIO_ID: /* Example of how to only allow 10Mbps modes. */ sc->mii_capabilities = BMSR_ANEG|BMSR_10TFDX|BMSR_10THDX; break; - Add your PCI device ID like this: case COMPAQ_PRESARIO_ID: case 0x12345678: /* Example of how to only allow 10Mbps modes. */ sc->mii_capabilities = BMSR_ANEG|BMSR_10TFDX|BMSR_10THDX; break; One thing I discovered is that trying to enable 100Mbps autoneg on a device that only has a 10Mbps port doesn't work. This broke the support for the 10Mbps ethernet in certain Compaq Presario machines, which is why I special-cased it. This will not make the AUI port work (I need to add extra code for that) but it if this is the same problem as the Compaq, it should allow the 10baseT port to work. Let me know if this has any effect. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jun 1 15:28:24 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144]) by hub.freebsd.org (Postfix) with ESMTP id 7E7DA37B837; Thu, 1 Jun 2000 15:28:04 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay01.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000601222836.LFDC13246.relay01@chello.nl>; Fri, 2 Jun 2000 00:28:36 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id AAA00477; Fri, 2 Jun 2000 00:27:58 +0200 (CEST) (envelope-from wkb) Date: Fri, 2 Jun 2000 00:27:57 +0200 From: Wilko Bulte To: Bill Paul Cc: wc.bulte@chello.nl, ticso@cicely.de, current@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: Looking for testers for if_dc patches Message-ID: <20000602002757.B99732@freebie.wbnet> Reply-To: wc.bulte@chello.nl References: <20000531123051.A86871@freebie.wbnet> <20000601195125.8AE5F37B958@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000601195125.8AE5F37B958@hub.freebsd.org>; from wpaul@FreeBSD.ORG on Thu, Jun 01, 2000 at 12:51:25PM -0700 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jun 01, 2000 at 12:51:25PM -0700, Bill Paul wrote: > > Hi Bill, > > > > I applied your patches to -current without incidents. > > > > I have a testbox (Digital dual P6) that gives: > > > > May 31 10:56:38 p6 /kernel: dc0: port > [...] > > May 31 11:03:27 p6 /kernel: dc0: watchdog timeout > > > > This box can also house an Alpha Miata MX5 mainboard, the Intel & Alpha > > boards use the same PCI riser card that also contains the 21143 chip. > > The patches don't seem to help on this particular hardware. I will try > > to give the Alpha a spin too, later today. BTW: ifconfig-ing to use > > 10baseT/UTP does not help either. The media bulkhead is a 10baseT/10base2 > > one. if_de has no problems: > > Alright, hold it. Stop. Just to make sure I understand: Don't panic ;-) This is definitely a confusing piece of hardware. > - There's one interface involved here Correct. > - It has a 21143 chip Well, the de driver says 21142. The dc driver says 21143. > - It has 10baseT and AUI ports No, it has 10baseT and 10base2 (Cheapernet). > - It's supposed to be 10Mbps only With the current bulkhead yes. There is a replacement bulkhead in existence that is 10baseT/100baseT capable. > If this is all correct, then I'd like you to try the following: > > - Run pciconf -l on this machine and obtain the PCI ID for this device. > The device ID is the hex number after the "chip=" section in the output. > For the sake of this example, let's say it's 0x12345678. For reference the ID reported is: de0@pci0:3:0: class=0x020000 card=0x00000000 chip=0x00191011 rev=0x11 hdr=0x00 > - Bring up /sys/dev/mii/dcphy.c in your favorite editor. > > - Look for the following code in the dcphy_attach() routine: > > case COMPAQ_PRESARIO_ID: > /* Example of how to only allow 10Mbps modes. */ > sc->mii_capabilities = BMSR_ANEG|BMSR_10TFDX|BMSR_10THDX; > break; > > - Add your PCI device ID like this: > > case COMPAQ_PRESARIO_ID: > case 0x12345678: > /* Example of how to only allow 10Mbps modes. */ > sc->mii_capabilities = BMSR_ANEG|BMSR_10TFDX|BMSR_10THDX; > break; > > One thing I discovered is that trying to enable 100Mbps autoneg on > a device that only has a 10Mbps port doesn't work. This broke the > support for the 10Mbps ethernet in certain Compaq Presario machines, > which is why I special-cased it. This will not make the AUI port > work (I need to add extra code for that) but it if this is the same > problem as the Compaq, it should allow the 10baseT port to work. This one does not have AUI so that is not going to be a problem. What I do wonder, though, is what will happen if a 10/100Mbit bulkhead is installed on this machine. I don't expect the PCI ID to change (right?). I can pull the 10/100 bulkhead from my Miata GL to give this a try. In the meantime I gave your patch a quick try and I unfortunately don't see a change in behaviour. Still watchdog timeouts and no connection. Question: I had expected dmesg and ifconfig to report 10Mbit only modes. They still show 100 as supported media in addition to the 10Mbit modes. There is something else that might interest you: when replacing a 10 Mbit only bulkhead with a 10/100 one you need to connect it to the PCI bulkhead with a different cable to a different connector (on the PCI bulkhead). The 10/100 one is silkscreened as MII. Could this mean the driver sees a MII interface while in this particular setup the bulkhead is connected to something non-MII ? Wild guess maybe.. Once again: very special hardware... Thanks, Wilko -- Wilko Bulte FreeBSD, the power to serve http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jun 1 16:32:46 2000 Delivered-To: freebsd-alpha@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 9784837B52B; Thu, 1 Jun 2000 16:32:42 -0700 (PDT) Subject: Re: Looking for testers for if_dc patches In-Reply-To: <20000602002757.B99732@freebie.wbnet> from Wilko Bulte at "Jun 2, 2000 00:27:57 am" To: wc.bulte@chello.nl Date: Thu, 1 Jun 2000 16:32:42 -0700 (PDT) Cc: wc.bulte@chello.nl, ticso@cicely.de, current@FreeBSD.ORG, alpha@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 Message-Id: <20000601233242.9784837B52B@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > - There's one interface involved here > > Correct. > > > - It has a 21143 chip > > Well, the de driver says 21142. The dc driver says 21143. It's just a difference in chip revision, really. > This one does not have AUI so that is not going to be a problem. What I do > wonder, though, is what will happen if a 10/100Mbit bulkhead is installed on > this machine. I don't expect the PCI ID to change (right?). I can pull > the 10/100 bulkhead from my Miata GL to give this a try. It would help if you could look at both of them and tell me what chips are on them. The 21143 can do 10Mbps all by itself, but for 100Mbps you'd need an extra transceiver. I've been working under the assumption that they're just using the built-in 10baseT port on the 21143, but it's possible they're using the GPIO bits to do some funny business to switch the ports. > In the meantime I gave your patch a quick try and I unfortunately don't > see a change in behaviour. Still watchdog timeouts and no connection. > > Question: I had expected dmesg and ifconfig to report 10Mbit only modes. > They still show 100 as supported media in addition to the 10Mbit modes. You have to be able to tell that the chip only supports 10Mbps modes. The 21143 is a 100Mbps chip, and only in certain cases do people design 10Mbps-only NICs around it. The problem is that to know if you've got only 10Mbps, you normally have to slog through the SROM info, however a lot of card vendors get this wrong, so I don't even bother with it. > There is something else that might interest you: when replacing a 10 Mbit > only bulkhead with a 10/100 one you need to connect it to the PCI bulkhead > with a different cable to a different connector (on the PCI bulkhead). The > 10/100 one is silkscreened as MII. Then it probably has a 10/100 PHY on it. Assuming the driver can probe it without having to flip any magic GPIO bits, it should work. > Could this mean the driver sees a MII interface while in this particular > setup the bulkhead is connected to something non-MII ? Wild guess maybe.. I'm sure it is non-MII. It's still supposed to work, however it's hard to tell just what I'm supposed to do to make it happy from way over here. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jun 1 19:31:20 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from eel.radicalmedia.com (eel.radicalmedia.com [204.254.246.9]) by hub.freebsd.org (Postfix) with ESMTP id 8E2F437B671 for ; Thu, 1 Jun 2000 19:31:18 -0700 (PDT) (envelope-from phiber@eel.radicalmedia.com) Received: (from phiber@localhost) by eel.radicalmedia.com (8.9.3/8.9.3) id WAA06473 for freebsd-alpha@freebsd.org; Thu, 1 Jun 2000 22:31:48 -0400 (EDT) Message-ID: <20000601223147.C20341@radicalmedia.com> Date: Thu, 1 Jun 2000 22:31:47 -0400 From: Mark Abene To: freebsd-alpha@freebsd.org Subject: JDK status? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I was just curious how the effort was coming along in porting the JDK to freebsd-alpha. Thanks, -Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jun 2 0:30:19 2000 Delivered-To: freebsd-alpha@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 9A69137B5BB; Fri, 2 Jun 2000 00:30:13 -0700 (PDT) Subject: Re: Looking for testers for if_dc patches In-Reply-To: <20000602002757.B99732@freebie.wbnet> from Wilko Bulte at "Jun 2, 2000 00:27:57 am" To: wc.bulte@chello.nl Date: Fri, 2 Jun 2000 00:30:13 -0700 (PDT) Cc: wc.bulte@chello.nl, ticso@cicely.de, current@FreeBSD.ORG, alpha@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 Message-Id: <20000602073013.9A69137B5BB@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > For reference the ID reported is: > > de0@pci0:3:0: class=0x020000 card=0x00000000 chip=0x00191011 rev=0x11 hdr=0x00 Hm, ok. First of all, I made a mistake in what I told you. The code in dcphy.c checks the subsystem ID, not the device ID. The device ID is always the same, since that identifies the 21143 chip, however the subsystem ID can vary from board to board depending on the manufacturer's whims. The odd thing is that the subsystem ID here is 0x00000000 (the "card=" value), however that doesn't rule out running our test. So, go back to dcphy.c and do this: case COMPAQ_PRESARIO_ID: case 0x00000000: /* Example of how to only allow 10Mbps modes. */ sc->mii_capabilities = BMSR_ANEG|BMSR_10TFDX|BMSR_10THDX; break; Let me know if this has any effect. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jun 2 12:48:11 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144]) by hub.freebsd.org (Postfix) with ESMTP id 9D30B37BF3F; Fri, 2 Jun 2000 12:48:03 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay01.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000602194837.DPBV8610.relay01@chello.nl>; Fri, 2 Jun 2000 21:48:37 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id VAA65392; Fri, 2 Jun 2000 21:47:57 +0200 (CEST) (envelope-from wkb) Date: Fri, 2 Jun 2000 21:47:56 +0200 From: Wilko Bulte To: Bill Paul Cc: wc.bulte@chello.nl, ticso@cicely.de, current@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: Looking for testers for if_dc patches Message-ID: <20000602214756.B65309@freebie.wbnet> Reply-To: wc.bulte@chello.nl References: <20000602002757.B99732@freebie.wbnet> <20000602073013.9A69137B5BB@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000602073013.9A69137B5BB@hub.freebsd.org>; from wpaul@FreeBSD.ORG on Fri, Jun 02, 2000 at 12:30:13AM -0700 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jun 02, 2000 at 12:30:13AM -0700, Bill Paul wrote: > > > > For reference the ID reported is: > > > > de0@pci0:3:0: class=0x020000 card=0x00000000 chip=0x00191011 rev=0x11 hdr=0x00 > > Hm, ok. First of all, I made a mistake in what I told you. The code in > dcphy.c checks the subsystem ID, not the device ID. The device ID is always > the same, since that identifies the 21143 chip, however the subsystem ID > can vary from board to board depending on the manufacturer's whims. > The odd thing is that the subsystem ID here is 0x00000000 (the "card=" > value), however that doesn't rule out running our test. > > So, go back to dcphy.c and do this: > > case COMPAQ_PRESARIO_ID: > case 0x00000000: > /* Example of how to only allow 10Mbps modes. */ > sc->mii_capabilities = BMSR_ANEG|BMSR_10TFDX|BMSR_10THDX; > break; > > Let me know if this has any effect. Unfortunately not. More data on this bulkhead: It contains a black plastic module that calls itself: ALL-IN-ONE Ethernet COAX TC3095 along with a 20Mc xtal oscillator. It looks like this is a selfcontained DC-DC converter, pulse xformer and a 10base2 medium interface in a single module. The cable connection to the PCI riser goes to a connector labeled "AUI". My best guess is that this bulkhead is not much more than a 10baseT/10base2 transceiver in disguise, connected to an AUI interface. I'm currently performing surgery on my other machine to see what the 10/100 bulkhead contains. -- Wilko Bulte FreeBSD, the power to serve http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jun 2 13:44:59 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id 3B72D37B711; Fri, 2 Jun 2000 13:44:47 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000602204432.DTAY17505.relay02@chello.nl>; Fri, 2 Jun 2000 22:44:32 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id WAA65673; Fri, 2 Jun 2000 22:44:44 +0200 (CEST) (envelope-from wkb) Date: Fri, 2 Jun 2000 22:44:44 +0200 From: Wilko Bulte To: Bill Paul Cc: current@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: Looking for testers for if_dc patches Message-ID: <20000602224444.C65309@freebie.wbnet> Reply-To: wc.bulte@chello.nl References: <20000602002757.B99732@freebie.wbnet> <20000601233242.9784837B52B@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000601233242.9784837B52B@hub.freebsd.org>; from wpaul@FreeBSD.ORG on Thu, Jun 01, 2000 at 04:32:42PM -0700 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jun 01, 2000 at 04:32:42PM -0700, Bill Paul wrote: > > > - It has a 21143 chip > > > > Well, the de driver says 21142. The dc driver says 21143. > > It's just a difference in chip revision, really. OK. > > This one does not have AUI so that is not going to be a problem. What I do > > wonder, though, is what will happen if a 10/100Mbit bulkhead is installed on > > this machine. I don't expect the PCI ID to change (right?). I can pull > > the 10/100 bulkhead from my Miata GL to give this a try. > > It would help if you could look at both of them and tell me what chips > are on them. The 21143 can do 10Mbps all by itself, but for 100Mbps > you'd need an extra transceiver. I've been working under the assumption > that they're just using the built-in 10baseT port on the 21143, but > it's possible they're using the GPIO bits to do some funny business > to switch the ports. The 10/100 bulkhead has two National Semiconductor chips, DP83840AVCE and DP83223V > You have to be able to tell that the chip only supports 10Mbps modes. > The 21143 is a 100Mbps chip, and only in certain cases do people design > 10Mbps-only NICs around it. The problem is that to know if you've got > only 10Mbps, you normally have to slog through the SROM info, however a > lot of card vendors get this wrong, so I don't even bother with it. > > > There is something else that might interest you: when replacing a 10 Mbit > > only bulkhead with a 10/100 one you need to connect it to the PCI bulkhead > > with a different cable to a different connector (on the PCI bulkhead). The > > 10/100 one is silkscreened as MII. > > Then it probably has a 10/100 PHY on it. Assuming the driver can probe > it without having to flip any magic GPIO bits, it should work. With the 10/100 in place I get a 100mbit connection (according to my hub's LEDs) after powerup. After FreeBSD has booted (with the Compaq-like hack in dcphy in place) I see the 100mbit LED of the hub switch off. But I don't get a working 10mbit link either. In the machine I borrowed the 10/100 from (a later model Miata GL) 100mbit works like a charm with the dc driver. On the Alphas there is also the SRM ewa speed select variable [ as if this was not confusing enough ]. I tried setting ewa0_mode to both 10baseT and 100baseT. In both cases there results were the same, no working link. > I'm sure it is non-MII. It's still supposed to work, however it's hard > to tell just what I'm supposed to do to make it happy from way over here. Using the de driver I got a working connection and here is pciconf -l with the 10/100 card installed: bash-2.04# pciconf -l de0@pci0:3:0: class=0x020000 card=0x00000000 chip=0x00191011 rev=0x11 hdr=0x00 none0@pci0:4:0: class=0x010180 card=0x00000000 chip=0x06461095 rev=0x01 hdr=0x00 isab0@pci0:7:0: class=0x000000 card=0x00000000 chip=0x04848086 rev=0x43 hdr=0x00 pcib1@pci0:8:0: class=0x060400 card=0x00000000 chip=0x00241011 rev=0x01 hdr=0x01 isp0@pci0:11:0: class=0x010000 card=0x53492050 chip=0x10201077 rev=0x05 hdr=0x00 none1@pci0:12:0: class=0x000100 card=0x00000000 chip=0x88d05333 rev=0x00 hdr=0x00 I don't think there is something relevant to be found that differs from the 10 mbit bulkhead. There is something else that bothers me: I remove the 'device dc' line from the kernel config file (leaving a device miibus and device xl in) and adding 'device de'. config MX5, make depend && make && make install in /sys/compile/MX5. reboot. Pang: kernel stack not valid, halt. When I do a config -r MX5 I can build a kernel that works/boots OK. Could it be that there is something in the dependency for miibus? I don't recall that it rebuilt the miibus module. And the 'kernel stack not valid' thing happens just after the module loading message says "miibus". I don't pretend to understand this to be honest. I hope the info above helps a bit, and does not add too much to the confusion. W/ -- Wilko Bulte FreeBSD, the power to serve http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jun 2 21:23:23 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from caffeine.gerp.org (caffeine.gerp.org [216.80.26.45]) by hub.freebsd.org (Postfix) with SMTP id 67F7C37B9F6 for ; Fri, 2 Jun 2000 21:23:15 -0700 (PDT) (envelope-from kdulzo@caffeine.gerp.org) Received: (qmail 20045 invoked by uid 100); 3 Jun 2000 04:12:32 -0000 Date: Fri, 2 Jun 2000 23:12:32 -0500 From: "Kevin M. Dulzo" To: Sparhawk Cc: freebsd-stable@freebsd.org, freebsd-alpha@freebsd.org Subject: Re: Reboots on Alpha System running 4.0 Stable Message-ID: <20000602231231.A19283@caffeine.gerp.org> Reply-To: kdulzo@gerp.org References: <4.3.2.20000531202654.01750668@192.168.1.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <4.3.2.20000531202654.01750668@192.168.1.69>; from sparhawk@sparhawk.bc.ca on Wed, May 31, 2000 at 09:03:17PM -0700 X-Operating-System: OpenBSD caffeine 2.7 CAFFEINE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 31, 2000 at 09:03:17PM -0700, Sparhawk wrote: > I updated from 4.0 RELEASE to STABLE about 3 or 4 days ago on my Digital > AlphaServer 400 4/233, since then I have noticed a few reboots. The > following Message appears in my log file. I am running an opennap napster > server on the machine. > > Any ideas what might be causing this? > > Sparhawk > sparhawk@sparhawk.bc.ca > > Jun 2 04:13:55 wintermute /kernel: > Jun 2 04:13:55 wintermute /kernel: fatal kernel trap: > Jun 2 04:13:55 wintermute /kernel: > Jun 2 04:13:55 wintermute /kernel: trap entry = 0x2 (memory management fault) > Jun 2 04:13:55 wintermute /kernel: a0 = 0x61feffa59f0 > Jun 2 04:13:55 wintermute /kernel: a1 = 0x1 > Jun 2 04:13:55 wintermute /kernel: a2 = 0x0 > Jun 2 04:13:55 wintermute /kernel: pc = 0xfffffc00003cd520 > Jun 2 04:13:55 wintermute /kernel: ra = 0xfffffc00003b8a60 > Jun 2 04:13:55 wintermute /kernel: curproc = 0xfffffe000aca44c0 > Jun 2 04:13:55 wintermute /kernel: pid = 356, comm = opennap > Jun 2 04:13:55 wintermute /kernel: > Jun 2 04:13:55 wintermute /kernel: panic: trap > Jun 2 04:13:55 wintermute /kernel: > Jun 2 04:13:55 wintermute /kernel: syncing disks... 22 22 22 22 22 22 22 > 22 22 > 22 22 22 22 22 22 22 22 22 22 22 > Jun 2 04:13:55 wintermute /kernel: giving up on 22 buffers > Jun 2 04:13:55 wintermute /kernel: Uptime: 13h30m36s > Jun 2 04:13:55 wintermute /kernel: Automatic reboot in 15 seconds - press > a key > on the console to abort > Jun 2 04:13:55 wintermute /kernel: Rebooting... > I have had the same issue, I thought it was due to nullfs mounts, so I removed them. a gdb showed an unknown symbol point in it wierd heuristic error as well in gdb -k. I rebuilt a kernel with nullfs build in to hopefully have the symbol show up next time I try them...but I lost the kernel.debug for the core files. I will follow up with a set if it occurs again. In my case cvsup caused one (last known symbol was in ufs something read or write) and cp caused another...no debug info. Just thought Id let it be known thats not an isolated error. Mines a PC164 at 500MHz underclocked to 466. -Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jun 2 23: 0:32 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from eel.radicalmedia.com (eel.radicalmedia.com [204.254.246.9]) by hub.freebsd.org (Postfix) with ESMTP id 542FD37B7F7 for ; Fri, 2 Jun 2000 23:00:27 -0700 (PDT) (envelope-from phiber@eel.radicalmedia.com) Received: (from phiber@localhost) by eel.radicalmedia.com (8.9.3/8.9.3) id CAA18328 for freebsd-alpha@freebsd.org; Sat, 3 Jun 2000 02:00:58 -0400 (EDT) Message-ID: <20000603020057.G20341@radicalmedia.com> Date: Sat, 3 Jun 2000 02:00:57 -0400 From: Mark Abene To: freebsd-alpha@freebsd.org Subject: vn driver broken? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm having an odd problem with the vnode (vn) driver. It's built as a module by default. I'm running 4.0-RELEASE. I want to mount and work with msdos floppy image files. I do: vnconfig vn0c dosboot.flp mount -tmsdos /dev/vn0c /mnt This works fine, and kldstat show that the vn.ko module gets loaded. However, trying to read or write anything greater than exactly 1024 bytes results in the error "Argument list too long" and fails. What's the deal? Can anyone else verify this problem? Thanks, -Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jun 3 4: 5:25 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id 1921437BB52 for ; Sat, 3 Jun 2000 04:05:23 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000603110508.GVZP17505.relay02@chello.nl> for ; Sat, 3 Jun 2000 13:05:08 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id NAA73927 for freebsd-alpha@freebsd.org; Sat, 3 Jun 2000 13:05:19 +0200 (CEST) (envelope-from wkb) Date: Sat, 3 Jun 2000 13:05:19 +0200 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: Miata console after 'halt' Message-ID: <20000603130518.A73911@freebie.wbnet> Reply-To: wc.bulte@chello.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I wonder if anybody has ever seen the following: Miata MX5 or Miata GL. Both run -current without any problems. Shutdown FreeBSD. Now the SRM console yells for every keystroke: "scancode foo not supported" or something close to that. Needless to say the (DEC) keyboard works just fine when FreeBSD is running. A reset is needed to get the SRM to work with the keyboard again. Not critical, but annoying. -- Wilko Bulte FreeBSD, the power to serve http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jun 3 13:12:35 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8CA2A37BF4C for ; Sat, 3 Jun 2000 13:12:29 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA17456; Sat, 3 Jun 2000 16:12:25 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA52514; Sat, 3 Jun 2000 16:11:55 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 3 Jun 2000 16:11:54 -0400 (EDT) To: wc.bulte@chello.nl Cc: FreeBSD-alpha mailing list Subject: Re: Miata console after 'halt' In-Reply-To: <20000603130518.A73911@freebie.wbnet> References: <20000603130518.A73911@freebie.wbnet> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14649.26030.594976.699497@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > I wonder if anybody has ever seen the following: > > Miata MX5 or Miata GL. Both run -current without any problems. Shutdown > FreeBSD. > > Now the SRM console yells for every keystroke: "scancode foo not supported" > or something close to that. Needless to say the (DEC) keyboard works just > fine when FreeBSD is running. A reset is needed to get the SRM to work with > the keyboard again. > > Not critical, but annoying. Yes, I see this. It hasn't been very high in my priority list. FWIW, I don't think it happens with an AS200 or an AS600... Have you seen any keyboard related oddities when running X? A while ago I noticed that if I had Xkbd enabled on my Miata GL at home, I'd get a random ` (back-quote) characters appearing about every 500th keypress. Turning putting XkbDisable in my /etc/XF86Config made the problem go away -- I assumed it was just a bad keyboard. (BTW, XkbDisable doesn't help the console problem you mention) Yesterday I fired up X (an old build of 3.3.4) on the UP1000 I'm working on (FreeBSD mostly works, BTW) and noticed that the keyboard didn't work at all. In fact, I had to reboot the machine after starting X in order to get the keyboard back. XkbDisable cures this problem too.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jun 3 23:20:46 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id A34AD37C8C5 for ; Sat, 3 Jun 2000 23:20:44 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.hiwaay.net (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e546Kfk22693; Sun, 4 Jun 2000 01:20:42 -0500 (CDT) Date: Sun, 4 Jun 2000 01:20:41 -0500 (CDT) From: Steve Price To: Mark Abene Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: JDK status? In-Reply-To: <20000601223147.C20341@radicalmedia.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 1 Jun 2000, Mark Abene wrote: # I was just curious how the effort was coming along in porting the JDK # to freebsd-alpha. I haven't seen a reply to this one. Since I'm the one that was working on this (that I'm aware of), I guess I should say that it has been put on hold. I've been swamped at my paying job, but I'll get back to it just as soon as things calm down. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message