From owner-freebsd-hardware Tue Jan 5 19:22:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02933 for freebsd-hardware-outgoing; Tue, 5 Jan 1999 19:22:13 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from amerasu.brel.com (amerasu.brel.com [203.127.231.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02914; Tue, 5 Jan 1999 19:22:10 -0800 (PST) (envelope-from calvinng@brel.com) Received: from localhost (calvinng@localhost) by amerasu.brel.com (8.8.8/8.8.8) with ESMTP id LAA09443; Wed, 6 Jan 1999 11:30:49 +0800 (SGT) (envelope-from calvinng@brel.com) Date: Wed, 6 Jan 1999 11:30:49 +0800 (SGT) From: Calvin NG To: hardware@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Summary: NetFinity 5500-41U, cannot detect SCSI controller Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, After receiving Mike's reply that ServeRAID is really not supported. This is in the TROUBLE.TXT somewhere. I have given up on it, and went out to purchase an Adaptec 2940U2W. After a couple of hours fiddling, finally got it working, I mean the SCSI card. Installing the latest FreeBSD is of course a breeze. Only problem I had is when I first install my new SCSI card, the system did not detect it. A few words with the IBM tech support engr told me that which slot I put it in is important. I have to install it at the first slot to get the Netfinity to recognise the SCSI card. After that everything went smoothly. My first impression of FreeBSD on the Netfinity, now a couple of hours old, is that everything runs so fast. I think the Ultra-2 architecture, the 256MB RAM, and the 400MHz PII helps a lot. :-) Thanks, Mike. Thanks, everyone. Regards, /calvin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 6 09:08:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07519 for freebsd-hardware-outgoing; Wed, 6 Jan 1999 09:08:48 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from toad.async.org (hun-al2-17.ix.netcom.com [205.184.6.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07514; Wed, 6 Jan 1999 09:08:44 -0800 (PST) (envelope-from dono@async.org) Received: from localhost (dono@localhost) by toad.async.org (8.9.1a+ysyi1/8.9.1a) with ESMTP id KAA00465; Wed, 6 Jan 1999 10:49:02 -0600 (CST) Date: Wed, 6 Jan 1999 10:49:02 -0600 (CST) From: Pilo Phlat To: questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Keyboard (PS/2?) problems (follow-up) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok, I've tried different types of keyboards, including the ones mentioned below, a standard 104-key "win95 design" keyboard, Microsoft Natural Elite(TM)(R)(SM)(C) Microsoft, and some others. With all of them, I've had the same problems with the console locking up. I found out that after a lot (not sure how many exactly) of switching vty's, this happens, and locks up in mid-switch (using alt-Fkey). Is this a bug with the syscons driver? Please let me know if any of you have had this problem before. Thanks. -d. KeyID 1024/570E72C5 Fingerprint 8A 74 C8 E4 A8 8D 00 FE 01 EF 9F BB 75 38 17 6F ---------- Forwarded message ---------- Date: Thu, 24 Dec 1998 02:06:47 -0600 (CST) From: Pilo Phlat To: questions@feebsd.org, hardware@freebsd.org Subject: Keyboard (PS/2?) problems Hello, I have a PS/2 keyboard here, from "PC Concepts". It is the split-key (ergonomic), 107-key version (not the 109-key w/ touchpad). The keyboard is connected to a FreeBSD 2.2.8-RELEASE machine, with syscons driver, psm driver for the PS/2 mouse, and so on (mail me if you need to see the entire kernel config). The problem is that somewhat randomly (I cannot repeat this on-demand), about every 2-3 days (sometimes not even 1 day, sometimes 4-5 days) of being up, the keyboard freezes. It is usually after switching virtual consoles (with alt+Fkey). I could not find a way to reset the keyboard after it froze, and had to reboot the machine remotely. When I un-plug the keyboard and plug it back in, the Num/Caps/Scroll lock LEDs flash, but the keyboard is still frozen. Only way I could get it back to work is by rebooting the machine. It seems, though, that this is a problem with the keyboard itself, not FreeBSD (I haven't verified this). I've had this problem with Linux and Windows 98 as well, but in those cases, simply un-plugging and plugging the keyboard back in fixes the problem. Assuming that this is a problem with the keyboard, is there way to prevent this somehow (I doubt it, but ...)? If not, is there any way to reset it, so that I could use the keyboard again without rebooting (something like /usr/sbin/kcon -R won't help, since I'm using the syscons driver, not pcvt)? If any of you readers have experienced a similar problem with the same kind of keyboard, or a different kind, I'd like to know. Thanks for your time. -d. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 6 11:31:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25130 for freebsd-hardware-outgoing; Wed, 6 Jan 1999 11:31:40 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from cannon.ma.ikos.com (cannon.ma.ikos.com [137.103.105.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25123; Wed, 6 Jan 1999 11:31:38 -0800 (PST) (envelope-from tich@cannon.ma.ikos.com) Received: from lonesome.ma.ikos.com (lonesome [137.103.105.44]) by cannon.ma.ikos.com (8.9.1/8.8.8) with ESMTP id OAA13108; Wed, 6 Jan 1999 14:32:09 -0500 (EST) From: Richard Cownie Received: (from tich@localhost) by lonesome.ma.ikos.com (8.8.8/8.8.8) id OAA10265; Wed, 6 Jan 1999 14:32:09 -0500 (EST) Date: Wed, 6 Jan 1999 14:32:09 -0500 (EST) Message-Id: <199901061932.OAA10265@lonesome.ma.ikos.com> To: freebsd-hardware@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: SMP Xeon SC450NX 2G Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My SC450NX Xeon box (from www.sagelec.com) is now up and running 3.0-RELEASE with 2 cpus and 1GB of DRAM. I bought an Adaptec 2940 to get round the ncr driver problem with the onboard Symbios 53C896. The onboard video (Cirrus Logic CL-GD5480) also seems to work ok with XFree86 (choosing GD5464 as the card type in XF86Setup). Everything runs fine so far, and the 400MHz Xeon blows away our 300MHz UltraSPARC-2 boxes (did a big gcc compile in 440 sec vs 761 sec). With 2GB of DRAM it still crashes - here are the details: ... BIOS basemem (633K) != RTC basemem (640K), setting to BIOS value BIOS extmem (15360K) != RTC extmem (65535K) Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Fatal trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 03000000 fault virtual address = 0x68 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01e41c0 stack pointer = 0x10:0xf02c3e8c frame pointer = 0x10:0xf02c3eac code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 0 () interrupt mask = net tty bio cam <- SMP: XXX kernel: type 12 trap, code=0 Stopped at _vm_page_select_free+0x20: movl 0x68(%esi),%ebx db> trace _vm_page_select_free(0,9,1,f2205000,f2c00000) at _vm_page_select_free+0x20 _vm_page_alloc(0,9,2,f2205000,f0269188) at _vm_page_alloc+0xba _pmap_growkernel(f2a05000,4,f025e07c,800000,f02691a8) at _pmap_growkernel+0xa5 _vm_map_findspace(f0269188,effbf000,800000,f02c3f58,f0269188,2,0,f027b75c) _kmem_alloc at _kmem_alloc+0x3e _pmap_init at _pmap_init+0x57 _vm_mem_init at _vm_mem_init+0x50 _main at _main+0x8b begin() at begin+0x54 Cheers Richard Cownie (tich@ma.ikos.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 6 13:20:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10164 for freebsd-hardware-outgoing; Wed, 6 Jan 1999 13:20:43 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from chopin.seattleu.edu (chopin.seattleu.edu [206.81.198.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10156; Wed, 6 Jan 1999 13:20:39 -0800 (PST) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu ([172.17.41.90]) by chopin.seattleu.edu (8.8.5/8.8.5) with ESMTP id NAA20506; Wed, 6 Jan 1999 13:19:34 -0800 (PST) Message-ID: <3693D34E.F06A5C1F@seattleu.edu> Date: Wed, 06 Jan 1999 13:19:10 -0800 From: Eric Hodel X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Pilo Phlat CC: questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Keyboard (PS/2?) problems (follow-up) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Pilo Phlat wrote: > > Ok, I've tried different types of keyboards, including the ones mentioned > below, a standard 104-key "win95 design" keyboard, Microsoft Natural > Elite(TM)(R)(SM)(C) Microsoft, and some others. With all of them, I've had > the same problems with the console locking up. I found out that after a > lot (not sure how many exactly) of switching vty's, this happens, and > locks up in mid-switch (using alt-Fkey). Is this a bug with the syscons > driver? > > Please let me know if any of you have had this problem before. Thanks. Occasionally I will have to hit the numlock button a couple time to type anything (the first time it beeps, the second time it toggles) but I haven't noticed this in conjunction with switching consoles. -- Eric Hodel hodeleri@seattleu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 6 14:00:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13771 for freebsd-hardware-outgoing; Wed, 6 Jan 1999 14:00:16 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from george.lbl.gov (george.lbl.gov [131.243.2.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13751; Wed, 6 Jan 1999 14:00:14 -0800 (PST) (envelope-from jin@george.lbl.gov) Received: (from jin@localhost) by george.lbl.gov (8.8.8/8.8.8) id NAA28692; Wed, 6 Jan 1999 13:59:34 -0800 (PST) Date: Wed, 6 Jan 1999 13:59:34 -0800 (PST) From: Jin Guojun (FTG staff) Message-Id: <199901062159.NAA28692@george.lbl.gov> To: dono@async.org, hodeleri@seattleu.edu Subject: Re: Keyboard (PS/2?) problems (follow-up) Cc: hardware@FreeBSD.ORG, questions@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org } > Ok, I've tried different types of keyboards, including the ones mentioned } > below, a standard 104-key "win95 design" keyboard, Microsoft Natural } > Elite(TM)(R)(SM)(C) Microsoft, and some others. With all of them, I've had } > the same problems with the console locking up. I found out that after a } > lot (not sure how many exactly) of switching vty's, this happens, and } > locks up in mid-switch (using alt-Fkey). Is this a bug with the syscons } > driver? } > } > Please let me know if any of you have had this problem before. Thanks. } } Occasionally I will have to hit the numlock button a couple time to type } anything (the first time it beeps, the second time it toggles) but I haven't } noticed this in conjunction with switching consoles. Constantly, I can lose the keyboard and/or have malfunctioned keyboard during switching a keyboard to different CPU by using a keyboard switching box in X window section. About less than 35% times, using alt-Fkey may recover the keyboard, but most time I have to quit the X window (if keyboard still alive) or even reboot machine (lost keyboard). I do not know if we trigged a same bug. -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 6 17:17:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06746 for freebsd-hardware-outgoing; Wed, 6 Jan 1999 17:17:24 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mail5.realtime.net (mail5.realtime.net [205.238.128.241]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA06738; Wed, 6 Jan 1999 17:17:20 -0800 (PST) (envelope-from jktheowl@bga.com) Received: from barnowl ([205.238.146.129]) by mail5.realtime.net ; Wed, 06 Jan 1999 19:17:19 -600 Date: Wed, 6 Jan 1999 19:26:22 -0600 (CST) From: John Kenagy X-Sender: jktheowl@barnowl To: Eric Hodel cc: Pilo Phlat , questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Keyboard (PS/2?) problems (follow-up) In-Reply-To: <3693D34E.F06A5C1F@seattleu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 6 Jan 1999, Eric Hodel wrote: > Pilo Phlat wrote: > > > > Ok, I've tried different types of keyboards, including the ones mentioned > > below, a standard 104-key "win95 design" keyboard, Microsoft Natural > > Elite(TM)(R)(SM)(C) Microsoft, and some others. With all of them, I've had > > the same problems with the console locking up. I found out that after a > > lot (not sure how many exactly) of switching vty's, this happens, and > > locks up in mid-switch (using alt-Fkey). Is this a bug with the syscons > > driver? > > > > Please let me know if any of you have had this problem before. Thanks. > > Occasionally I will have to hit the numlock button a couple time to type > anything (the first time it beeps, the second time it toggles) but I haven't > noticed this in conjunction with switching consoles. I've had similar problems. It's the mouse - ps/2 variety - for me. Moving the mouse in the root window while holding down the control key (to pop up a menu) will freeze it up tight. The other situation is during an edit session with Xemacs. During those sessions and if the xconsole window is visible, I see errors indicating psmintr breaking lock or losing sync. I do not remember the exact error. I've rebuilt the kernel there is a variable that needs to be set in 2.2.1R, anyway: options PSM_CHECKSYNC You might want to check the documentation for your version to see if this might help. As far as I know this is a maybe. I've given up and run a serial mouse with no problems. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 6 18:49:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15954 for freebsd-hardware-outgoing; Wed, 6 Jan 1999 18:49:36 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15934; Wed, 6 Jan 1999 18:49:32 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id VAA10567; Wed, 6 Jan 1999 21:49:03 -0500 (EST) (envelope-from luoqi) Date: Wed, 6 Jan 1999 21:49:03 -0500 (EST) From: Luoqi Chen Message-Id: <199901070249.VAA10567@lor.watermarkgroup.com> To: freebsd-hardware@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG, tich@ma.ikos.com Subject: Re: SMP Xeon SC450NX 2G Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In i386/i386/pmap.c function pmap_init(), try to move the allocation of kptobj to the beginning of the function (before the kmem_alloc call). -lq > My SC450NX Xeon box (from www.sagelec.com) is now up and running > 3.0-RELEASE with 2 cpus and 1GB of DRAM. I bought an Adaptec 2940 > to get round the ncr driver problem with the onboard Symbios 53C896. > The onboard video (Cirrus Logic CL-GD5480) also seems to work ok > with XFree86 (choosing GD5464 as the card type in XF86Setup). > > Everything runs fine so far, and the 400MHz Xeon blows away our > 300MHz UltraSPARC-2 boxes (did a big gcc compile in 440 sec vs 761 sec). > > With 2GB of DRAM it still crashes - here are the details: > > ... > BIOS basemem (633K) != RTC basemem (640K), setting to BIOS value > BIOS extmem (15360K) != RTC extmem (65535K) > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > > > Fatal trap 12: page fault while in kernel mode > mp_lock = 00000002; cpuid = 0; lapic.id = 03000000 > fault virtual address = 0x68 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf01e41c0 > stack pointer = 0x10:0xf02c3e8c > frame pointer = 0x10:0xf02c3eac > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 0 () > interrupt mask = net tty bio cam <- SMP: XXX > kernel: type 12 trap, code=0 > Stopped at _vm_page_select_free+0x20: movl 0x68(%esi),%ebx > db> trace > _vm_page_select_free(0,9,1,f2205000,f2c00000) at _vm_page_select_free+0x20 > _vm_page_alloc(0,9,2,f2205000,f0269188) at _vm_page_alloc+0xba > _pmap_growkernel(f2a05000,4,f025e07c,800000,f02691a8) at _pmap_growkernel+0xa5 > _vm_map_findspace(f0269188,effbf000,800000,f02c3f58,f0269188,2,0,f027b75c) > _kmem_alloc at _kmem_alloc+0x3e > _pmap_init at _pmap_init+0x57 > _vm_mem_init at _vm_mem_init+0x50 > _main at _main+0x8b > begin() at begin+0x54 > > Cheers > Richard Cownie (tich@ma.ikos.com) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 6 22:13:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11177 for freebsd-hardware-outgoing; Wed, 6 Jan 1999 22:13:28 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA11146; Wed, 6 Jan 1999 22:13:23 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id BAA07854; Thu, 7 Jan 1999 01:20:04 -0500 From: Bill Paul Message-Id: <199901070620.BAA07854@skynet.ctr.columbia.edu> Subject: Call for testers: ASIX AX88140A fast ethernet driver To: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Date: Thu, 7 Jan 1999 01:20:03 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Today I finally obtained a fast ethernet adapter with an ASIX AX88140A chip (thanks Ulf!) and have finished preliminary testing of a driver for this device. Boards based on this chip are usually very cheap and apparently can be had for $20US or less. You can obtain the driver from: http://www.freebsd.org/~wpaul/ASIX/3.0 source for FreeBSD 3.0 http://www.freebsd.org/~wpaul/ASIX/2.2 source for FreeBSD 2.2.x To add the driver to an existing system, do the following: - Download the correct version of if_ax.c and if_axreg.h for your version of FreeBSD. - Unpack the kernel source code under /usr/src. - Copy if_ax.c and if_axreg.h to /sys/pci. - Edit /sys/conf/files and add a line that says: pci/if_ax.c optional ax device-driver - Edit your kernel config file (e.g. /sys/i386/conf/GENERIC) and add a line that says: device ax0 - Configure and compile a kernel and boot it. Devices should be detected as ax0, ax1, etc... You will probably want to edit /etc/rc.conf to have the interface brought up when the system boots. The ASIX Electronics AX88140A is another DEC tulip clone (big surprise). The chip supports both serial and MII transceivers, however it does not have its own internal NWAY support so most boards based on this chip will probably include an MII-compliant NWAY-capable PHY. The main difference between the DEC tulip and the ASIX chip is that the ASIX's receive filter is not programmed by downloading a special setup frame into the transmit DMA channel. Instead, the filter is configured using two special registers. Filtering is restricted to a 64-bit multicast hash table and a single perfect filter entry for the station address. (Those who are curious can obtain a copy of the ASIX datasheet from www.asix.com.tw.) The ASIX chip has one unusual quirk, which is that the reset bit in the bus configuration register is not self-clearing: the driver has to manually clear it. Neither the real DEC tulip nor any of the clones work like this. Also, although the chip supports chaining descriptors in linked list mode, there is no 'use linked list mode' bit in the descriptor control word. Note: I cobbled the 2.2.x version of the driver together tonight and haven't actually tested it yet, having spent most of the day testing the board under 3.0. (I have verified that it compiles and tried to make sure I didn't make any serious goofs). I'm not going to be able to work on it for a while as I got tagged for jury duty, which starts tomorrow. I'm not sure how long it will last. I will of course be keeping track of e-mail during this time, but I may be a bit slow in responding. Note II: I also received a Macronix 98713 board today and finally fixed the mx driver (in -current and on the http server) to properly handle the internal NWAY registers on this chip (the mx_mii_readreg() routine wasn't quite right, and a few other things needed to be tweaked). This means that if you have a board with an original 98713 chip (as opposed to the 98713A), media autoselection and link detection should work properly now. As usual, send your reports, good or bad, to wpaul@skynet.ctr.columbia.edu. Share and enjoy! -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-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 6 22:24:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12555 for freebsd-hardware-outgoing; Wed, 6 Jan 1999 22:24:14 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA12550; Wed, 6 Jan 1999 22:24:13 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.1/8.9.1) id WAA04010; Wed, 6 Jan 1999 22:23:50 -0800 (PST) (envelope-from ulf) Message-ID: <19990106222349.S28818@TelcoSucks.org> Date: Wed, 6 Jan 1999 22:23:49 -0800 From: Ulf Zimmermann To: Bill Paul , hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Call for testers: ASIX AX88140A fast ethernet driver Reply-To: ulf@Alameda.net References: <199901070620.BAA07854@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901070620.BAA07854@skynet.ctr.columbia.edu>; from Bill Paul on Thu, Jan 07, 1999 at 01:20:03AM -0500 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.0-19980930-BETA Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jan 07, 1999 at 01:20:03AM -0500, Bill Paul wrote: > Today I finally obtained a fast ethernet adapter with an ASIX AX88140A > chip (thanks Ulf!) and have finished preliminary testing of a driver for > this device. Boards based on this chip are usually very cheap and > apparently can be had for $20US or less. You can obtain the driver from: $17.50 at a store in the S.F. Bay Area. > > http://www.freebsd.org/~wpaul/ASIX/3.0 source for FreeBSD 3.0 > http://www.freebsd.org/~wpaul/ASIX/2.2 source for FreeBSD 2.2.x > > -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-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jan 7 00:36:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24601 for freebsd-hardware-outgoing; Thu, 7 Jan 1999 00:36:25 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.6.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24596 for ; Thu, 7 Jan 1999 00:36:23 -0800 (PST) (envelope-from schofiel@xs4all.nl) Received: from xs2.xs4all.nl (root@xs2.xs4all.nl [194.109.6.43]) by smtp3.xs4all.nl (8.8.8/8.8.8) with ESMTP id JAA26274 for ; Thu, 7 Jan 1999 09:35:52 +0100 (CET) Received: from excelsior (enterprise.xs4all.nl [194.109.14.215]) by xs2.xs4all.nl (8.8.8/8.8.6) with SMTP id JAA09598 for ; Thu, 7 Jan 1999 09:35:51 +0100 (MET) Message-ID: <36947FF3.74D1@xs4all.nl> Date: Thu, 07 Jan 1999 09:35:47 +0000 From: Rob Schofield Reply-To: schofiel@xs4all.nl Organization: Knights of the Round Table Ltd. X-Mailer: Mozilla 3.04Gold (WinNT; I) MIME-Version: 1.0 To: Free BSD Hardware list Subject: Re: Keyboard (PS/2?) problems (follow-up) References: <199901062159.NAA28692@george.lbl.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jin Guojun (FTG staff) wrote: > Constantly, I can lose the keyboard and/or have malfunctioned keyboard > during switching a keyboard to different CPU by using a keyboard switching box > in X window section. About less than 35% times, using alt-Fkey may recover the > keyboard, but most time I have to quit the X window (if keyboard still alive) > or even reboot machine (lost keyboard). I do not know if we trigged a same bug. I have been seeing similar behaviour switching between one of 4 CPUs using a Viper SmartView 4. The FBSD box is dual boot with NT; under NT I can switch successfully 100% of the time. Under FBSD, it is 50-50. Rob Schofield -- The Ninety-Ninety Rule of Project Scheduling: The first ninety percent of the job takes ninety percent of the allotted time, the last ten percent takes the other ninety percent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jan 7 12:22:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00765 for freebsd-hardware-outgoing; Thu, 7 Jan 1999 12:22:40 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from cannon.ma.ikos.com (cannon.ma.ikos.com [137.103.105.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00757; Thu, 7 Jan 1999 12:22:36 -0800 (PST) (envelope-from tich@cannon.ma.ikos.com) Received: from lonesome.ma.ikos.com (lonesome [137.103.105.44]) by cannon.ma.ikos.com (8.9.1/8.8.8) with ESMTP id PAA22002; Thu, 7 Jan 1999 15:23:09 -0500 (EST) From: Richard Cownie Received: (from tich@localhost) by lonesome.ma.ikos.com (8.8.8/8.8.8) id PAA12219; Thu, 7 Jan 1999 15:23:09 -0500 (EST) Date: Thu, 7 Jan 1999 15:23:09 -0500 (EST) Message-Id: <199901072023.PAA12219@lonesome.ma.ikos.com> To: freebsd-hardware@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: SC450NX - thanks for patches Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Here's the latest on the SC450NX quad-Xeon machine 1) With this patch to i386/i386/pmap.c (thanks to Luoqi Chen) it now runs with 2GB DRAM >In i386/i386/pmap.c function pmap_init(), try to move the allocation of >kptobj to the beginning of the function (before the kmem_alloc call). 2) With this patch to pci/ncr.c (thanks to Gerard Roudier) it can now find and boot the kernel using the onboard 53C896 scsi >If you want the driver to work immediately for you, the following trick >should be enough, but it is not kind of beauty, by the way: > >$ vi ncr.c >:1,$ s/ctest0/sdid/g 3) With the disk on the 53C896 scsi, it fails to mount the root filesystem (perhaps because moving the disk causes confusion ?) So I'm still using the Adaptec 2940 for now. 4) Increasing the process size limit to 2GB seems to cause some trouble - the system boots, but the console getty complains and doesn't put up a login prompt. Kernel configured with this has the problem: options "MAXDSIZ=(2000*1024*1024)" options "DFLDSIZ=(2000*1024*1024)" Kernel configured with this is ok: options "MAXDSIZ=(1800*1024*1024)" options "MAXDSIZ=(1800*1024*1024)" 5) Performance is good, 400MHz Xeon is 1.35 x faster than 300MHz Ultrasparc2 on our application (compiling Verilog onto a box full of FPGA's) - and the SC450NX is about $11.5K, compared to about $30K for a dual UltraSPARC. With 500MHz Tanner cpu's (in March ?) the SC450NX will be just awesome. Thanks to everyone for helping to make this fly Richard Cownie (tich@ma.ikos.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jan 7 19:10:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19717 for freebsd-hardware-outgoing; Thu, 7 Jan 1999 19:10:56 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from toad.async.org (hun-al1-07.ix.netcom.com [205.184.6.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA19695; Thu, 7 Jan 1999 19:10:51 -0800 (PST) (envelope-from dono@async.org) Received: from localhost (dono@localhost) by toad.async.org (8.9.1a+ysyi1/8.9.1a) with ESMTP id VAA00763; Thu, 7 Jan 1999 21:09:15 -0600 (CST) Date: Thu, 7 Jan 1999 21:09:15 -0600 (CST) From: Pilo Phlat To: Rakesh Vidyadharan cc: questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Keyboard (PS/2?) problems (follow-up) In-Reply-To: <369573AE.A236C539@geocities.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 7 Jan 1999, Rakesh Vidyadharan wrote: >I had that problem a long time ago. My keyboard used to freeze up every >day, and I would have to switch the PC off and then on to get to work >again. The problem went away when I used a commercial X-server, which >leads me to believe that it is essentially a problem with your X-server, >and not with you keyboard. Perhaps, except that I am not running an X server. My problems are at the console.. which is why I mentioned syscons and switching vty's, not using the "Zoom" feature of an X server. I can reproduce the problem by rapidly switching vty's (using alt-Fkey). Just hold down your alt key, while pounding on the Fkeys corresponding to the enabled vty's in /etc/ttys. After about a minute or two of bashing the keys, the console/keyboard should freeze (well, at least in my case). Of course, this problem was noticed after several days worth of regular tty-switching, not by pounding on the keys from boredom :) In the mean time, I've ordered some more Microsoft(R) Natural(R)(TM)(SM) 3|337(SM)(TM)(R) keyboards to do some more testing (I don't have another 2.2.8R machine to test on). Woopie. -d KeyID 1024/570E72C5 Fingerprint 8A 74 C8 E4 A8 8D 00 FE 01 EF 9F BB 75 38 17 6F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jan 9 21:06:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29891 for freebsd-hardware-outgoing; Sat, 9 Jan 1999 21:06:13 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29868; Sat, 9 Jan 1999 21:06:09 -0800 (PST) (envelope-from shocking@bandicoot.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id NAA10990; Sun, 10 Jan 1999 13:05:27 +0800 (WST) Received: by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id NAA05628; Sun, 10 Jan 1999 13:05:26 +0800 Date: Sun, 10 Jan 1999 13:05:26 +0800 From: shocking@prth.pgs.com (Stephen Hocking-Senior Programmer PGS Tensor Perth) Message-Id: <199901100505.NAA05628@ariadne.tensor.pgs.com> To: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Support for Netgear ethernet cards Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone know if the Netgear series of ethernet cards (PCI, 10/100Mb/s) is supported by the current bunch of drivers? I had a look at the card and couldn't see any familiar names silk-screened on the chips, with main chip having NetGear splattered all over it. Stephen PS - They're going dirt cheap at a local PC place. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jan 9 21:43:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03510 for freebsd-hardware-outgoing; Sat, 9 Jan 1999 21:43:16 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (castles156.castles.com [208.214.165.156]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03505; Sat, 9 Jan 1999 21:43:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA03464; Sat, 9 Jan 1999 21:39:39 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901100539.VAA03464@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: shocking@prth.pgs.com (Stephen Hocking-Senior Programmer PGS Tensor Perth) cc: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Support for Netgear ethernet cards In-reply-to: Your message of "Sun, 10 Jan 1999 13:05:26 +0800." <199901100505.NAA05628@ariadne.tensor.pgs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Jan 1999 21:39:38 -0800 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Does anyone know if the Netgear series of ethernet cards (PCI, 10/100Mb/s) > is supported by the current bunch of drivers? I had a look at the > card and couldn't see any familiar names silk-screened on the chips, > with main chip having NetGear splattered all over it. Yes; as Bill recently posted, we now have support either in the tree or available as addons from Bill's page (www.freebsd.org/~wpaul) for prettymuch all of the 100Mbps chipsets. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message