From owner-freebsd-hardware Sun Jun 4 21:20:10 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from web115.yahoomail.com (web115.yahoomail.com [205.180.60.88]) by hub.freebsd.org (Postfix) with SMTP id A6B3237B7BC for ; Sun, 4 Jun 2000 21:19:56 -0700 (PDT) (envelope-from eaglez69@yahoo.com) Received: (qmail 1844 invoked by uid 60001); 5 Jun 2000 04:19:51 -0000 Message-ID: <20000605041951.1843.qmail@web115.yahoomail.com> Received: from [136.152.194.139] by web115.yahoomail.com; Sun, 04 Jun 2000 21:19:51 PDT Date: Sun, 4 Jun 2000 21:19:51 -0700 (PDT) From: Eaglez Subject: Re: Unknown Devices To: John Hengstler , freebsd-current@freebsd.org Cc: hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, i'm not sure about 5.0's new funky support (i mean, if it supports the SB Live, who knows), but in the past, PCI modems have never been supported, because they all tend to be win modems (only MS windows drivers available). I'd advise possibly an external modem. (Hey, they're probably still cheaper than USB modems, although i'd go with that if it IS somehow cheaper.) -Jesse --- John Hengstler wrote: > Greetings, > > I just subscribed to -current list to get > suggestions on the following so if > I have missed comments on this already I am sorry > for the redundancy. > > I have just upgraded to 5.0-current in order to get > the driver for my ether > card, which has corrected that problem (xe device). > > But I still can't access my pci modem, because it is > listed as an unknown > device. There are many other unknown devices as > well. The following is > dmesg output: > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All > rights reserved. > FreeBSD 5.0-CURRENT #0: Thu Jun 1 22:20:39 PDT 2000 > root@laptop.atbd.com:/usr/src/sys/compile/ATBD > Timecounter "i8254" frequency 1193182 Hz > CPU: AMD-K6(tm) 3D processor (473.17-MHz 586-class > CPU) > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > > Features=0x8021bf > AMD Features=0x80000800 > real memory = 29294592 (28608K bytes) > avail memory = 25411584 (24816K bytes) > Preloaded elf kernel "kernel" at 0xc033e000. > K6-family MTRR support enabled (2 registers) > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > apm0: on motherboard > apm: found APM BIOS v1.2, connected at v1.2 > pcib0: on motherboard > pci0: on pcib0 > pcib1: > at device 1.0 on pci0 > pci1: on pcib1 > pci1: device> at 0.0 irq 9 > isab0: at device 7.0 on > pci0 > isa0: on isab0 > atapci0: port > 0x1820-0x182f at device 7.1 on > pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > pci0: at 7.2 irq 11 > isab1: > at device 7.4 on pci0 > chip1: port > 0x1830-0x1833,0x1834-0x1837,0x1000-0x10ff irq 11 at > device 7.5 on pci0 > > ***built in card here ? also appeared in prior sys > releases *** > pci0: (vendor=0x11c1, dev=0x0441) at > 9.0 irq 9 > > pcic-pci0: at > device 10.0 on pci0 > pcic-pci0: TI12XX PCI Config Reg: [ring > enable][speaker enable][pwr > save][CSC serial isa irq] > fdc0: at port > 0x3f0-0x3f5,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,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > vga0: at port 0x3c0-0x3df iomem > 0xa0000-0xbffff on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > pcic0: at port 0x3e0-0x3e1 on isa0 > pcic0: Polling mode > pccard0: on pcic0 > pccard1: on pcic0 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > ppc0: This ppc chipset does not support the extended > I/O port range...no > problem > ppc0: at port 0x378-0x37b irq 7 on > isa0 > ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE > mode > ppi0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > plip0: on ppbus0 > unknown0: at port > 0x80,0x62,0x66,0x72-0x75,0x92,0xa8-0xa9,0x38a-0x38b,0x8040-0x807f,0x9050-0x9 > 051 iomem 0xfffe0000-0xffffffff on isa0 > unknown1: at iomem > 0-0x9ffff,0xec000-0xfffff,0x100000-0x1bfffff on > isa0 > unknown2: at port > 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 > unknown: can't assign resources > unknown3: at port 0x40-0x43 irq 0 on isa0 > unknown4: at port 0x70-0x71 irq 8 on isa0 > unknown: can't assign resources > npxisa0: at port > 0xf0-0xff irq 13 on isa0 > unknown5: at port 0x61 on isa0 > unknown6: at port 0xcf8-0xcff on isa0 > unknown7: at port > 0x4d0-0x4d1,0x8000-0x803f,0x8080-0x808f on isa0 > unknown8: at port 0x3400-0x347f on isa0 > unknown9: at iomem 0xdc000-0xdffff on isa0 > unknown10: on isa0 > unknown: can't assign resources > unknown: can't assign resources > unknown: can't assign resources > unknown: can't assign resources > IP packet filtering initialized, divert disabled, > rule-based forwarding > enabled, default to deny, logging limited to 10 > packets/entry by default > ad0: 5729MB [12416/15/63] at > ata0-master using UDMA66 > acd0: CDROM at ata1-master > using UDMA33 > Mounting root from ufs:/dev/ad0s3a > pccard: card inserted, slot 0 > > Everything else on the system works for now, except > for the modem. This > same results were in 4.0-release, and stable as > well.. > > Any suggestions are appreciated. > > John Hengstler > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of > the message __________________________________________________ Do You Yahoo!? Yahoo! Photos -- now, 100 FREE prints! http://photos.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 5 6:10:18 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id D78D537BAEE for ; Mon, 5 Jun 2000 06:10:06 -0700 (PDT) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id JAA87525 for freebsd-hardware@freebsd.org; Mon, 5 Jun 2000 09:17:22 -0400 (EDT) From: Brian Hechinger Message-Id: <200006051317.JAA87525@entropy.tmok.com> Subject: Celeron Question To: freebsd-hardware@freebsd.org Date: Mon, 5 Jun 2000 09:17:22 -0400 (EDT) Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases 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-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org i've held the celeron in very low respect, i just don't like what it is (keep in mind i'm a long time sun guy so i tend to have a problem with x86 in general) and i have noticed that under WinNT/98 it tends to be rather unstable. for example. we have a couple Celeron based laptops at work, and running both 98 and NT they would crash constantly. our internal systems guy put 2000 on these laptops and POOF, stable as a rock. so my question is, obviously some kernel tuning was done on 2000 to make it work well with the celeron. maybe the celeron has a hangup or two with certain bits of the current x86 instruction set, i don't know, but anyway, back to the question.... what is the current status of FreeBSD on the Celeron? i'd like to throw together some low cost, moderately powerful FreeBSD boxes, and the Celeron looks like it would fit the bill, as long as it is stable, otherwise i'll look to the Athlon, or worst case, K6-II, although a slot2/370 combo motherboard so i can upgrade to full strength Pentium IIIs when the time comes is an attractive deal. (the time being after the Pentium VII has been released and the IIIs are dirt cheap) thanks, -brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 5 8:21: 7 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id 0A9B837BC3D; Mon, 5 Jun 2000 08:21:01 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA17373; Mon, 5 Jun 2000 08:23:53 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200006051523.IAA17373@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Eaglez Cc: John Hengstler , freebsd-current@freebsd.org, hardware@freebsd.org Subject: Re: Unknown Devices In-reply-to: Your message of "Sun, 04 Jun 2000 21:19:51 PDT." <20000605041951.1843.qmail@web115.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Jun 2000 08:23:53 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Well, i'm not sure about 5.0's new funky support (i > mean, if it supports the SB Live, who knows), but in > the past, PCI modems have never been supported, > because they all tend to be win modems (only MS > windows drivers available). I'd advise possibly an > external modem. (Hey, they're probably still cheaper > than USB modems, although i'd go with that if it IS > somehow cheaper.) Watch out - some USB modems are also WinModems. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 5 8:27:28 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.dbitech.bc.ca (i.caniserv.com [139.142.95.1]) by hub.freebsd.org (Postfix) with SMTP id B843037BAA7 for ; Mon, 5 Jun 2000 08:27:22 -0700 (PDT) (envelope-from swen@wavefire.com) Received: (qmail 20477 invoked from network); 5 Jun 2000 15:27:20 -0000 Received: from swen.wavefire.com (139.142.167.220) by 139.142.95.81 with SMTP; 5 Jun 2000 15:27:20 -0000 Message-Id: <4.3.2.7.2.20000605082305.00c118e0@mail.wavefire.com> X-Sender: swen@mail.wavefire.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 05 Jun 2000 08:24:52 -0700 To: wonko@entropy.tmok.com, freebsd-hardware@freebsd.org From: Chameleon Subject: Re: Celeron Question In-Reply-To: <200006051317.JAA87525@entropy.tmok.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Not sure what celery chips you've been using... But we've had zero problems with them on NT or 98. Except of course, the programmed in software crashes... :) They also run FreeBSD great. ( i think they are happier with the real OS) Swen At 09:17 AM 6/5/00 -0400, Brian Hechinger wrote: >i've held the celeron in very low respect, i just don't like what it is (keep >in mind i'm a long time sun guy so i tend to have a problem with x86 in >general) >and i have noticed that under WinNT/98 it tends to be rather unstable. for >example. we have a couple Celeron based laptops at work, and running both 98 >and NT they would crash constantly. our internal systems guy put 2000 on >these >laptops and POOF, stable as a rock. so my question is, obviously some kernel >tuning was done on 2000 to make it work well with the celeron. maybe the >celeron has a hangup or two with certain bits of the current x86 instruction >set, i don't know, but anyway, back to the question.... what is the current >status of FreeBSD on the Celeron? i'd like to throw together some low cost, >moderately powerful FreeBSD boxes, and the Celeron looks like it would fit >the bill, as long as it is stable, otherwise i'll look to the Athlon, or worst >case, K6-II, although a slot2/370 combo motherboard so i can upgrade to full >strength Pentium IIIs when the time comes is an attractive deal. (the time >being after the Pentium VII has been released and the IIIs are dirt cheap) > >thanks, > >-brian > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message Your mouse has moved. Windows NT must be restarted for the change to take effect. Reboot now? [ OK ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 5 8:38: 2 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id 78A6637BAA7 for ; Mon, 5 Jun 2000 08:37:58 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA17504; Mon, 5 Jun 2000 08:40:50 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200006051540.IAA17504@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: wonko@entropy.tmok.com Cc: freebsd-hardware@freebsd.org Subject: Re: Celeron Question In-reply-to: Your message of "Mon, 05 Jun 2000 09:17:22 EDT." <200006051317.JAA87525@entropy.tmok.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Jun 2000 08:40:50 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > i've held the celeron in very low respect, i just don't like what it is (keep > in mind i'm a long time sun guy so i tend to have a problem with x86 in general) > and i have noticed that under WinNT/98 it tends to be rather unstable. for > example. we have a couple Celeron based laptops at work, and running both 98 > and NT they would crash constantly. our internal systems guy put 2000 on these > laptops and POOF, stable as a rock. so my question is, obviously some kernel > tuning was done on 2000 to make it work well with the celeron. maybe the > celeron has a hangup or two with certain bits of the current x86 instruction > set, i don't know, This is all insane speculation, and totally off the mark. The Celeron shares the same core as the other PII/III family parts, and the aspersions you're casting against it are simply not true. > but anyway, back to the question.... what is the current > status of FreeBSD on the Celeron? i'd like to throw together some low cost, > moderately powerful FreeBSD boxes, and the Celeron looks like it would fit > the bill, as long as it is stable, otherwise i'll look to the Athlon, or worst > case, K6-II, although a slot2/370 combo motherboard so i can upgrade to full > strength Pentium IIIs when the time comes is an attractive deal. (the time > being after the Pentium VII has been released and the IIIs are dirt cheap) It works "just fine". The Celeron is a very attractive cost-competitive processor for a lot of low-end server applications, where "low end" is a very relative term. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 5 8:42:51 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from c014.sfo.cp.net (c014-h022.c014.sfo.cp.net [209.228.12.86]) by hub.freebsd.org (Postfix) with SMTP id 32E8E37BEA4 for ; Mon, 5 Jun 2000 08:42:46 -0700 (PDT) (envelope-from john@hei.net) Received: (cpmta 28213 invoked from network); 5 Jun 2000 08:31:49 -0700 Received: from unknown (HELO trout) (209.222.163.131) by smtp.transport.com with SMTP; 5 Jun 2000 08:31:49 -0700 X-Sent: 5 Jun 2000 15:31:49 GMT Message-ID: <001501bfcf00$5b905b00$83a3ded1@hei.net> From: "John Hengstler" To: "Mike Smith" Cc: , References: <200006051523.IAA17373@mass.cdrom.com> Subject: Re: Unknown Devices Date: Mon, 5 Jun 2000 08:11:42 -0700 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.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't know that what the actual modem is inside. The system is a Compaq Presario 1200. I am waiting for the compaq restore CD to reinstall the windows side to figure out what really on here. (Needs a compaq driver?) John ----- Original Message ----- From: "Mike Smith" To: "Eaglez" Cc: "John Hengstler" ; ; Sent: Monday, June 05, 2000 8:23 AM Subject: Re: Unknown Devices > > Well, i'm not sure about 5.0's new funky support (i > > mean, if it supports the SB Live, who knows), but in > > the past, PCI modems have never been supported, > > because they all tend to be win modems (only MS > > windows drivers available). I'd advise possibly an > > external modem. (Hey, they're probably still cheaper > > than USB modems, although i'd go with that if it IS > > somehow cheaper.) > > Watch out - some USB modems are also WinModems. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ 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-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 5 12:43: 3 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id 8214537B55E for ; Mon, 5 Jun 2000 12:43:00 -0700 (PDT) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id PAA91115 for freebsd-hardware@freebsd.org; Mon, 5 Jun 2000 15:50:17 -0400 (EDT) From: Brian Hechinger Message-Id: <200006051950.PAA91115@entropy.tmok.com> Subject: Celeron (Celery) Question To: freebsd-hardware@freebsd.org Date: Mon, 5 Jun 2000 15:50:17 -0400 (EDT) Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases 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-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org i thank everybody who replied, i feel much more confident about purchasing them now. thank you again. -brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 5 13:25:35 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id 5CFD837BB2B for ; Mon, 5 Jun 2000 13:25:29 -0700 (PDT) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id QAA91534 for freebsd-hardware@freebsd.org; Mon, 5 Jun 2000 16:32:43 -0400 (EDT) From: Brian Hechinger Message-Id: <200006052032.QAA91534@entropy.tmok.com> Subject: Celeron Summary To: freebsd-hardware@freebsd.org Date: Mon, 5 Jun 2000 16:32:42 -0400 (EDT) Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases 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-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ok, due to popular request (ok, one guy) here is the summary of the responses to this topic (which i failed to notice weren't CCed to the list) with some comments of my own. > I would take a long hard look at Duron. It will be available in SocketA >so you will be able to drop-in upgrade to an T-bird Athlon. It outperforms the >Celeron and both of the AMD chips cost less than Intel chips. while this does look attractive (price and performance), availability is an issue. just released to OEMs and VARs, but when can i buy one. >Not sure what celery chips you've been using... >But we've had zero problems with them on NT or 98. Except of course, the >programmed in software crashes... :) >They also run FreeBSD great. ( i think they are happier with the real OS) maybe it is just i happened to see hardware that was flakey outside of the CPU that 2000 cleaned up, keep in mind i only really started following x86 again earlier this year. >Your mouse has moved. >Windows NT must be restarted >for the change to take effect. > >Reboot now? [ OK ] ok, i just think this is funny and should be shared. >> laptops and POOF, stable as a rock. so my question is, obviously some kernel >> tuning was done on 2000 to make it work well with the celeron. maybe the >> celeron has a hangup or two with certain bits of the current x86 instruction >> set, i don't know, > >This is all insane speculation, and totally off the mark. The Celeron >shares the same core as the other PII/III family parts, and the >aspersions you're casting against it are simply not true. again, see my above statement on this subject. >> but anyway, back to the question.... what is the current >> status of FreeBSD on the Celeron? i'd like to throw together some low cost, >> moderately powerful FreeBSD boxes, and the Celeron looks like it would fit >> the bill, as long as it is stable, otherwise i'll look to the Athlon, or worst >> case, K6-II, although a slot2/370 combo motherboard so i can upgrade to full >> strength Pentium IIIs when the time comes is an attractive deal. (the time >> being after the Pentium VII has been released and the IIIs are dirt cheap) > >It works "just fine". The Celeron is a very attractive cost-competitive >processor for a lot of low-end server applications, where "low end" is a >very relative term. good news all around. low end in my dictionary? well, how low can you go? :) >> i've held the celeron in very low respect, i just don't like what it is (keep >> in mind i'm a long time sun guy so i tend to have a problem with x86 in general) >> and i have noticed that under WinNT/98 it tends to be rather unstable. for >> example. we have a couple Celeron based laptops at work, and running both 98 > Grrr! Yes, I have Suns too. And they are very stable. BUT, the Celeron is every > bit as stable as a Sun is. I have several Celerons running RH Linux > (sorry, no FreeBSD at the moment), and have never had any sort of crash. so we see some examples of people using celerons wothout trouble with a variety os OSes. so something to take seriously. > Hope I haven't bored you with my ranting. this guy goes into insane detail of various things, and while extremely interesting, i think it isn't appropriate for this posting. overall, i don't see any reason why i shouldn't get a celeron system. price is good, and with a quality motherboard i could upgrade to a "true" pentium at any time if need be. so if you want dirt cheap super performance, then you may want to wait for the Duron, but if you want cheap excellent performance and you need it NOW NOW NOW, then the celeron should be a wise choice. cheers, -brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 6 2:39:28 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from whale.sunbay.crimea.ua (sunbay-10BASE-T.cris.net [212.110.130.67]) by hub.freebsd.org (Postfix) with ESMTP id 08E9E37BF80 for ; Tue, 6 Jun 2000 02:39:17 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.9.3/1.13) id MAA10330; Tue, 6 Jun 2000 12:38:56 +0300 (EEST) Date: Tue, 6 Jun 2000 12:38:55 +0300 From: Ruslan Ermilov To: Doug Rabson Cc: hardware@freebsd.org Subject: Re: Intel 810 Message-ID: <20000606123855.A9603@sunbay.com> Mail-Followup-To: Doug Rabson , hardware@freebsd.org References: <200003080420.SAA27681@mauibuilt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dfr@nlsystems.com on Wed, Mar 08, 2000 at 08:39:41AM +0000 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 08, 2000 at 08:39:41AM +0000, Doug Rabson wrote: > On Tue, 7 Mar 2000, FreeBSD MAIL wrote: > > > Sorry if this is a repost but I didnt see it come throug yet and my mail was > > screwed up. > > > > I am working with a BookPC whith an intel 810 all in one chipset. > > > > I was wondering if there was planned support for the sound and if someone > > has heard anyting about the Xfree86 (linux) LKM being ported to FreeBSD. > > I have been working on something which should be adequate for the purposes > of XFree86-4.0. I've been distracted by having to ship some software at > work but I hope to get back to this soon, probably next week. > Did you achieve any results here, Doug? Thank you, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 6 3:41: 5 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id 3E7A237B717; Tue, 6 Jun 2000 03:41:00 -0700 (PDT) (envelope-from kuriyama@FreeBSD.org) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e56AejY45097; Tue, 6 Jun 2000 19:40:46 +0900 (JST) Date: Tue, 06 Jun 2000 19:40:45 +0900 Message-ID: <863dmr5byq.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: john@hei.net Cc: freebsd-current@FreeBSD.org, hardware@FreeBSD.org Subject: Re: Unknown Devices In-Reply-To: In your message of "2 Jun 2000 21:09:16 GMT" <001201bfccd2$1643be00$83a3ded1@hei.net> References: <001201bfccd2$1643be00$83a3ded1@hei.net> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 9) (Canyonlands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 2 Jun 2000 21:09:16 GMT, John Hengstler wrote: > pci0: (vendor=0x11c1, dev=0x0441) at 9.0 irq 9 http://www.yourvote.com/pci/pciread.asp?venid=0x11c1 says that chip is AT&T Microelectronics' WinModem. This is not yet supported by FreeBSD. -- Jun Kuriyama // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 6 3:53: 6 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from sohara.dyndns.org (pooh.elsevier.nl [145.36.13.27]) by hub.freebsd.org (Postfix) with ESMTP id DAC4837C007; Tue, 6 Jun 2000 03:52:57 -0700 (PDT) (envelope-from steve@sohara.dyndns.org) Received: (from steve@localhost) by sohara.dyndns.org (8.9.3/8.9.3) id LAA96948; Tue, 6 Jun 2000 11:59:20 +0100 (IST) (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <001501bfcf00$5b905b00$83a3ded1@hei.net> Date: Tue, 06 Jun 2000 11:59:19 +0100 (IST) From: "Steve O'Hara-Smith" To: John Hengstler Subject: Re: Unknown Devices Cc: current@freebsd.org, hardware@freebsd.org, Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 05-Jun-00 John Hengstler wrote: > I don't know that what the actual modem is inside. The system is a Compaq > Presario 1200. I rather think that means Lucent windows only modem. It does in my 1690. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 6 7:34:34 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1]) by hub.freebsd.org (Postfix) with ESMTP id 5F29637B52C for ; Tue, 6 Jun 2000 07:34:30 -0700 (PDT) (envelope-from hinman@us.networkcs.com) Received: from us.networkcs.com (us.networkcs.com [137.66.11.15]) by marcos.networkcs.com (8.9.3/8.9.3) with ESMTP id JAA53864; Tue, 6 Jun 2000 09:34:29 -0500 (CDT) (envelope-from hinman@us.networkcs.com) Received: (from hinman@localhost) by us.networkcs.com (8.9.2/8.9.2) id JAA33442; Tue, 6 Jun 2000 09:34:28 -0500 (CDT) (envelope-from hinman) Date: Tue, 6 Jun 2000 09:34:28 -0500 From: "Lee E. Hinman Ph.D." To: wonko@entropy.tmok.com Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Celeron Question Message-ID: <20000606093428.A22349@us.networkcs.com> References: <200006051317.JAA87525@entropy.tmok.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200006051317.JAA87525@entropy.tmok.com>; from wonko@users.tmok.com on Mon, Jun 05, 2000 at 09:17:22AM -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 06/05, Brian Hechinger wrote: > i've held the celeron in very low respect, i just don't like what it is (keep > in mind i'm a long time sun guy so i tend to have a problem with x86 in general) > and i have noticed that under WinNT/98 it tends to be rather unstable. for > example. we have a couple Celeron based laptops at work, and running both 98 > and NT they would crash constantly. our internal systems guy put 2000 on these > laptops and POOF, stable as a rock. so my question is, obviously some kernel > tuning was done on 2000 to make it work well with the celeron. maybe the > celeron has a hangup or two with certain bits of the current x86 instruction > set, i don't know, but anyway, back to the question.... what is the current > status of FreeBSD on the Celeron? i'd like to throw together some low cost, > moderately powerful FreeBSD boxes, and the Celeron looks like it would fit > the bill, as long as it is stable, otherwise i'll look to the Athlon, or worst > case, K6-II, although a slot2/370 combo motherboard so i can upgrade to full > strength Pentium IIIs when the time comes is an attractive deal. (the time > being after the Pentium VII has been released and the IIIs are dirt cheap) > > thanks, > > -brian > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message End included message from Brian Hechinger I had a Celeron 300A that was overclocked to 450 that was rock solid stable, up time of over 3 months. It only went down for OS upgrades and FreeBSD worked great on it. Having said that I now have an Athlon 700, and it has been just as stable. As long as you get a power supply that can feed the Athlon they run great and I don't think you can find a better price/performance ratio, espicially with the release of the TBird with should cut the price on the classic Athlons. Lee -- Lee E. Hinman hinman@networkcs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 6 11:42:41 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by hub.freebsd.org (Postfix) with ESMTP id 161D837B5E8 for ; Tue, 6 Jun 2000 11:42:30 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1) id 12zOIn-000Odf-0W; Tue, 6 Jun 2000 19:42:13 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id TAA02306; Tue, 6 Jun 2000 19:42:58 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 6 Jun 2000 19:47:16 +0100 (BST) From: Doug Rabson To: Ruslan Ermilov Cc: hardware@freebsd.org Subject: Re: Intel 810 In-Reply-To: <20000606123855.A9603@sunbay.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 Tue, 6 Jun 2000, Ruslan Ermilov wrote: > On Wed, Mar 08, 2000 at 08:39:41AM +0000, Doug Rabson wrote: > > On Tue, 7 Mar 2000, FreeBSD MAIL wrote: > > > > > Sorry if this is a repost but I didnt see it come throug yet and my mail was > > > screwed up. > > > > > > I am working with a BookPC whith an intel 810 all in one chipset. > > > > > > I was wondering if there was planned support for the sound and if someone > > > has heard anyting about the Xfree86 (linux) LKM being ported to FreeBSD. > > > > I have been working on something which should be adequate for the purposes > > of XFree86-4.0. I've been distracted by having to ship some software at > > work but I hope to get back to this soon, probably next week. > > > Did you achieve any results here, Doug? Not so far. I have been stuck trying to fix a bug in the generic intel AGP driver and this has prevented be from getting to work on the i810 driver. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 6 17: 5:49 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail2.rdc3.on.home.com (mail2.rdc3.on.home.com [24.2.9.41]) by hub.freebsd.org (Postfix) with ESMTP id 1F9A037BB9F; Tue, 6 Jun 2000 17:05:39 -0700 (PDT) (envelope-from gbuchana@home.com) Received: from localhost.on.rogers.wave.ca ([24.112.85.94]) by mail2.rdc3.on.home.com (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000607000534.HNZZ1114.mail2.rdc3.on.home.com@localhost.on.rogers.wave.ca>; Tue, 6 Jun 2000 17:05:34 -0700 Content-Length: 634 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 06 Jun 2000 20:05:34 -0400 (EDT) Reply-To: gbuchana@home.com From: Gardner Buchanan To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: 4.0R install kernel panics on if_le Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm trying to use a DEC EtherWORKS DE204 (le) with the 4.0R install kernel. During the probe the kernel reports a few obscure problems with "shims" - evidently the le driver hasn't been brought forward into the newbus framework or something. As soon as I ifconfig le0, the kernel panics. I can't capture the kernel probe messages unfortunately, as I have no suitable alternate console to use. I don't see anything in errata. Any pointers? ============================================================ Gardner Buchanan Ottawa, ON FreeBSD: Where you want to go. Today. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jun 7 2:50:44 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 7865237B7A7 for ; Wed, 7 Jun 2000 02:50:42 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JQBJQQMP3Q00015X@research.kpn.com> for freebsd-hardware@FreeBSD.ORG; Wed, 7 Jun 2000 11:50:40 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Wed, 07 Jun 2000 11:50:40 +0100 Content-return: allowed Date: Wed, 07 Jun 2000 11:50:39 +0100 From: "Koster, K.J." Subject: RE: Celeron Question To: freebsd-hardware@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7601@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > classic Athlons. > C'mon it's only been out for a few months. %-) Kees Jan ============================================== Everyone is responsible for his own actions, and (people tend to forget this) the effect they have on others. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jun 7 6:27:57 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from apollo.ocsny.com (apollo.ocsny.com [204.107.76.2]) by hub.freebsd.org (Postfix) with ESMTP id 6799437BC44 for ; Wed, 7 Jun 2000 06:27:49 -0700 (PDT) (envelope-from mikel@ocsny.com) Received: from ocsny.com (thoth.upan.org [204.107.76.16]) by apollo.ocsny.com (8.9.2/8.9.3) with ESMTP id JAA14386 for ; Wed, 7 Jun 2000 09:28:34 -0400 (EDT) Message-ID: <393E4EAE.3D312E1@ocsny.com> Date: Wed, 07 Jun 2000 09:31:26 -0400 From: Mikel Organization: Optimized Computer Solutions, Inc. X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en,it MIME-Version: 1.0 To: fBSD-hw Subject: very strange problem...on compaq proliant 800... Content-Type: multipart/mixed; boundary="------------092718E63401C6E2CBC57FC0" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------092718E63401C6E2CBC57FC0 Content-Type: multipart/alternative; boundary="------------388BE94829B2A59FBA393020" --------------388BE94829B2A59FBA393020 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I've been trying to catch this for two or three months now... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x8 fault code = Supervisor read, page not present instruction pointer = 0x8:0xc01cf0c4 stack pointer = 0x10:0xc031ac10 frame pointer = 0x10:0xc031ac18 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1 def 321, gran 1 processor flags = Interrupt enabled, resume, IOPL=0 current process = idle interrupt mask = trap number = 12 panic: page fault = syncing disks....3 3 uptime: 1H39m9s Any suggestions? Usually this thing reboots late at night...or when you step away to get coffee...etc so I was lucky to catch it as it whent by... This is a freash build maybe 2 weeks old...added ipfw stuff this past weekend I'd like to say that that's when the instability started but I've have other compaqs without ipfw...staright install and it's been this way.. -- Cheers, Mikel +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ | Optimized Computer Solutions, Inc http://www.ocsny.com | 39 W14th Street, Suite 203 212 727 2238 x132 | New York, NY 10011 +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ --------------388BE94829B2A59FBA393020 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit I've been trying to catch this for two or three months now...

Fatal trap 12: page fault while in kernel mode
fault virtual address    = 0x8
fault code               = Supervisor read, page not present
instruction pointer      = 0x8:0xc01cf0c4
stack pointer            = 0x10:0xc031ac10
frame pointer            = 0x10:0xc031ac18
code segment             = base 0x0, limit 0xfffff, type 0x1b
                         = DPL 0, pres 1 def 321, gran 1
processor flags          = Interrupt enabled, resume, IOPL=0
current process          = idle
interrupt mask           =
trap number              = 12
panic: page fault        =
 

syncing disks....3 3
uptime: 1H39m9s
 
 

Any suggestions?  Usually this thing reboots late at night...or when you step away to get coffee...etc so I was lucky to catch it as it whent by...

This is a freash build maybe 2 weeks old...added ipfw stuff this past weekend I'd like to say that that's when the instability started but I've have other compaqs without ipfw...staright install and it's been this way..
--
Cheers,
Mikel
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+
| Optimized Computer Solutions, Inc        http://www.ocsny.com
| 39 W14th Street, Suite 203                   212 727 2238  x132
| New York, NY 10011
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+
  --------------388BE94829B2A59FBA393020-- --------------092718E63401C6E2CBC57FC0 Content-Type: text/x-vcard; charset=us-ascii; name="mikel.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Mikel Content-Disposition: attachment; filename="mikel.vcf" begin:vcard n:King;Mikel tel;fax:2124638402 tel;home:http://www.upan.org tel;work:2127272100 x-mozilla-html:TRUE org:Optimized Computer Solutions version:2.1 email;internet:mikel@ocsny.com title:Director of Network Operations & Technology adr;quoted-printable:;;39 W14th St.=0D=0ASte 203;New York;NY;10011;US note;quoted-printable:fBSD, PHP, MySql and OCS Rule!!!=0D=0A=0D=0AGoal is to be MS free by the end of 2k. x-mozilla-cpt:;7312 fn:Mikel King end:vcard --------------092718E63401C6E2CBC57FC0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jun 7 14:32:17 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (Postfix) with ESMTP id CDA0537B6DE; Wed, 7 Jun 2000 14:31:55 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from partitur.se (elbas.partitur.se [193.219.246.222]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id XAA13210; Wed, 7 Jun 2000 23:31:50 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <393EBF45.B67A6655@partitur.se> Date: Wed, 07 Jun 2000 23:31:49 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Cc: freebsd-hardware@freebsd.org Subject: fxp0: device timeout - reboot required Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! I've seen it happen twice in a weeks time on our server, that has always been rock stable before: fxp0: device timeout (many many times, repeated in syslog) The machine does not answer to ping. This time, it think it started during a secure copy (scp(1)) of a ~70MB file over my cable modem (128 kbit/s upstream) to our file server, which is another freebsd machine (4-stable) on the same network. (I mention this since I found other people have had problems when moving large files.) ifconfig fxp0 down && sleep 2 && ifconfig fxp0 up did *not* help! neither did ifconfig fxp0 delete && ifconfig fxp0 inet ... When this happened last week, we switched cables and hub port. This didn't seem to help then, and since it happened again, this is probably not the case, right? The system was very sluggish when running from the console last time, which might be due to syslog working hard fetch all the timeouts? I dunno what happened this time. My colleague did the hands-on. Anyway, the fastest solution I could come up with was rebooting! It is amazing that it actually helped; I suspect this indicates software problems (or more likely, a combination?). It's an SMP machine, intel dual server motherboard (bx, if memory server me), FreeBSD 3.3-RELEASE, intel etherexpress 10/100B running half duplex 100Mbit/s. Will upgrading to 3.4-RELEASE help? I didn't see anything interesting in the if_fxp.c diffs, but there might be stuff done in other areas? Upgrading to 4.0 is not really an option at the moment. Side note: I have seen a few single device timeouts the weeks before the first major incident. I asked on the questions list, and got the advice to check the cabling. I didn't find the time to do this before the first incident. -- Palle Here's a dmesg: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.3-RELEASE #0: Thu Oct 7 05:27:00 CEST 1999 root@:/usr/src/sys/compile/PUKA Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183fbff real memory = 268435456 (262144K bytes) avail memory = 258318336 (252264K 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 0xc02a8000. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 ncr0: rev 0x37 int a irq 11 on pci0.13.0 ncr1: rev 0x37 int b irq 10 on pci0.13.1 fxp0: rev 0x05 int a irq 5 on pci0.15.0 fxp0: Ethernet address 00:a0:c9:d4:38:fa chip1: rev 0x02 on pci0.18.0 chip2: rev 0x02 on pci0.18.3 vga0: rev 0x23 on pci0.20.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 Waiting 3 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! changing root device to da0s1a da0 at ncr0 bus 0 target 8 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jun 7 14:40:38 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id A321D37B8BE for ; Wed, 7 Jun 2000 14:40:32 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 2150 invoked by uid 1001); 7 Jun 2000 21:40:26 +0000 (GMT) To: girgen@partitur.se Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: fxp0: device timeout - reboot required From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 07 Jun 2000 23:31:49 +0200" References: <393EBF45.B67A6655@partitur.se> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 07 Jun 2000 23:40:26 +0200 Message-ID: <2148.960414026@verdi.nethelp.no> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've seen it happen twice in a weeks time on our server, that > has always been rock stable before: > > fxp0: device timeout (many many times, repeated in syslog) > > The machine does not answer to ping. I see you're using the fxp driver in combination with the ncr driver. Have you considered using the sym driver instead? That has cured a number of stability problems for us. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jun 7 15:28:55 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from cell-works.com (cell-works.com [216.112.245.226]) by hub.freebsd.org (Postfix) with ESMTP id 49F9037B7D3 for ; Wed, 7 Jun 2000 15:28:46 -0700 (PDT) (envelope-from john@cell-works.com) Received: from localhost (john@localhost) by cell-works.com (8.8.8/8.8.8) with ESMTP id TAA19339 for ; Wed, 7 Jun 2000 19:14:32 -0400 (EDT) (envelope-from john@cell-works.com) Date: Wed, 7 Jun 2000 19:14:32 -0400 (EDT) From: John Daniel To: freebsd-hardware@FreeBSD.ORG Subject: amptron book pc 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 Is the amptron book pc like the one on www.directron.com/bookpc.html worth looking at for a practice box? I want to put together a mp3 player and web surfer in my living room. If it is no good what can I use to do the same thing? TIA ------------------------------------------------------------------------------- "I hope that after I die, people will say of me : " That guy sure owed me a lot of money." -JH ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jun 7 17: 6:56 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (Postfix) with ESMTP id C098E37B8EC; Wed, 7 Jun 2000 17:06:45 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from partitur.se (elbas.partitur.se [193.219.246.222]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id CAA14915; Thu, 8 Jun 2000 02:06:32 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <393EE388.411D6E56@partitur.se> Date: Thu, 08 Jun 2000 02:06:32 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: sthaug@nethelp.no Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: fxp0: device timeout - reboot required References: <393EBF45.B67A6655@partitur.se> <2148.960414026@verdi.nethelp.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org sthaug@nethelp.no wrote: > > > I've seen it happen twice in a weeks time on our server, that > > has always been rock stable before: > > > > fxp0: device timeout (many many times, repeated in syslog) > > > > The machine does not answer to ping. > > I see you're using the fxp driver in combination with the ncr driver. > Have you considered using the sym driver instead? That has cured a > number of stability problems for us. Hi Steinar, No, I haven't considered that. I will, when upgrading to fbsd-4. It seems that the sym driver is not available before release-4.0. :( Thanks for input anyway! Cheers, Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jun 7 17:21:51 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 9C47837BE0A; Wed, 7 Jun 2000 17:21:46 -0700 (PDT) (envelope-from paul@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1000) id F03392B2CF; Wed, 7 Jun 2000 19:21:45 -0500 (CDT) Date: Wed, 7 Jun 2000 17:21:45 -0700 From: Paul Saab To: Palle Girgensohn Cc: sthaug@nethelp.no, freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: fxp0: device timeout - reboot required Message-ID: <20000607172145.A72618@elvis.mu.org> References: <393EBF45.B67A6655@partitur.se> <2148.960414026@verdi.nethelp.no> <393EE388.411D6E56@partitur.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <393EE388.411D6E56@partitur.se>; from girgen@partitur.se on Thu, Jun 08, 2000 at 02:06:32AM +0200 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Palle Girgensohn (girgen@partitur.se) wrote: > sthaug@nethelp.no wrote: > > > > > I've seen it happen twice in a weeks time on our server, that > > > has always been rock stable before: > > > > > > fxp0: device timeout (many many times, repeated in syslog) > > > > > > The machine does not answer to ping. > > > > I see you're using the fxp driver in combination with the ncr driver. > > Have you considered using the sym driver instead? That has cured a > > number of stability problems for us. > > Hi Steinar, > > No, I haven't considered that. I will, when upgrading to > fbsd-4. It seems that the sym driver is not available before > release-4.0. :( The sym driver is in 3.4-STABLE. -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jun 7 20:44: 6 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from moffetimages.com (alar.scruz.predictive.com [207.251.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 909DF37B9DD; Wed, 7 Jun 2000 20:43:59 -0700 (PDT) (envelope-from brianm@moffetimages.com) Received: from brianm.moffetimages.com (dhcp8.moffetimages.com [10.0.1.8]) by moffetimages.com (8.9.3/8.9.3) with SMTP id UAA37103; Wed, 7 Jun 2000 20:49:40 -0700 (PDT) (envelope-from brianm@moffetimages.com) Message-Id: <3.0.5.32.20000607203619.007dbb20@orac.moffetimages.com> X-Sender: brianm@orac.moffetimages.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 07 Jun 2000 20:36:19 -0700 To: Mike Smith , wonko@entropy.tmok.com From: "Brian D. Moffet" Subject: Re: Celeron Question Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: <200006051540.IAA17504@mass.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 08:40 AM 6/5/00 -0700, Mike Smith wrote: >> i've held the celeron in very low respect, i just don't like what it is (keep >> in mind i'm a long time sun guy so i tend to have a problem with x86 in general) >> and i have noticed that under WinNT/98 it tends to be rather unstable. for >> example. we have a couple Celeron based laptops at work, and running both 98 >> and NT they would crash constantly. our internal systems guy put 2000 on these >> laptops and POOF, stable as a rock > >This is all insane speculation, and totally off the mark. The Celeron >shares the same core as the other PII/III family parts, and the >aspersions you're casting against it are simply not true. I run a Celeron 400 on a FreeBSD machine, solid as a rock. Never had a problem with the machine crashing. Runs just fine with the internal modem, the 13 Gig drive, the 3com 905, as well as the Matrox 8 meg video card (AGP). But then again, I'm a long time Intel Unix guy, so maybe that's why it works so well ;-) Brian PS. I got my printer problem solved, it was a combination problem of the parallel driver sending an bouncing the init line on close, as well as the lpd system lopping off the input. I've modified the parallel port driver, and changed to lprng. Brian D. Moffet www.moffetimages.com brianm@ricochet.net photographer, pilot, musician, programmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jun 7 22:36:48 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 365D737BA1A for ; Wed, 7 Jun 2000 22:36:42 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 12925 invoked by uid 1001); 8 Jun 2000 05:36:40 +0000 (GMT) To: paul@mu.org Cc: girgen@partitur.se, freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: fxp0: device timeout - reboot required From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 7 Jun 2000 17:21:45 -0700" References: <20000607172145.A72618@elvis.mu.org> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Thu, 08 Jun 2000 07:36:39 +0200 Message-ID: <12923.960442599@verdi.nethelp.no> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > I see you're using the fxp driver in combination with the ncr driver. > > > Have you considered using the sym driver instead? That has cured a > > > number of stability problems for us. > > > > No, I haven't considered that. I will, when upgrading to > > fbsd-4. It seems that the sym driver is not available before > > release-4.0. :( > > The sym driver is in 3.4-STABLE. Also, I wouldn't be surprised if the sym driver from 3.4-STABLE could be used for 3.3. You might want to ask the author, Gérard Roudier (). Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 8 5:53:22 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [209.0.55.68]) by hub.freebsd.org (Postfix) with ESMTP id 8075337B997 for ; Thu, 8 Jun 2000 05:53:19 -0700 (PDT) (envelope-from ragnar@sysabend.org) Received: by moo.sysabend.org (Postfix, from userid 1004) id 7D2AD759F; Thu, 8 Jun 2000 05:54:41 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id 7ABB51D94 for ; Thu, 8 Jun 2000 05:54:41 -0700 (PDT) Date: Thu, 8 Jun 2000 05:54:41 -0700 (PDT) From: Jamie Bowden To: hardware@FreeBSD.org Subject: Plextor CD-R Message-ID: Approved: yep X-representing: Only myself. 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-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just bought and installed the Plextor PlexWriter 8/20 CD-R. FreeBSD of course recognizes and uses it as a SCSI CD-ROM, so no issue there. What I'm curious about is whether it's a supported writeable drive. I didn't buy it with the intention of doing writes in FreeBSD, but it would be nice to know if I could. Jamie Bowden -- "Of course, that's sort of like asking how other than Marketing, Microsoft is different from any other software company..." Kenneth G. Cavness To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 8 6:15:18 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from majestix.cmr.no (majestix.cmr.no [129.177.31.53]) by hub.freebsd.org (Postfix) with ESMTP id BA40437B997 for ; Thu, 8 Jun 2000 06:15:13 -0700 (PDT) (envelope-from tl@cmr.no) Received: from shark.cmr.no (shark.cmr.no [129.177.31.34]) by majestix.cmr.no id PAA50911; Thu, 8 Jun 2000 15:15:00 +0200 (CEST) Date: Thu, 8 Jun 2000 15:15:05 +0200 (CEST) From: Tom Lislegaard To: Jamie Bowden Cc: hardware@FreeBSD.ORG Subject: Re: Plextor CD-R In-Reply-To: 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 Cdrecord supports just about any cdwriter you can buy today. See http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html -tom On Thu, 8 Jun 2000, Jamie Bowden wrote: > > I just bought and installed the Plextor PlexWriter 8/20 CD-R. FreeBSD of > course recognizes and uses it as a SCSI CD-ROM, so no issue there. What > I'm curious about is whether it's a supported writeable drive. I didn't > buy it with the intention of doing writes in FreeBSD, but it would be nice > to know if I could. > > Jamie Bowden > > -- > > "Of course, that's sort of like asking how other than Marketing, > Microsoft is different from any other software company..." > Kenneth G. Cavness > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" 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 Thu Jun 8 6:37: 5 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (Postfix) with ESMTP id C774B37B991; Thu, 8 Jun 2000 06:36:59 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from partitur.se (elbas.partitur.se [193.219.246.222]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id PAA22531; Thu, 8 Jun 2000 15:36:49 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <393FA171.DD5D8F23@partitur.se> Date: Thu, 08 Jun 2000 15:36:49 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: sthaug@nethelp.no Cc: paul@mu.org, freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: fxp0: device timeout - reboot required References: <20000607172145.A72618@elvis.mu.org> <12923.960442599@verdi.nethelp.no> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org sthaug@nethelp.no wrote: > = > > > > I see you're using the fxp driver in combination with the ncr dri= ver. > > > > Have you considered using the sym driver instead? That has cured = a > > > > number of stability problems for us. > > > > > > No, I haven't considered that. I will, when upgrading to > > > fbsd-4. It seems that the sym driver is not available before > > > release-4.0. :( > > > > The sym driver is in 3.4-STABLE. > = > Also, I wouldn't be surprised if the sym driver from 3.4-STABLE could > be used for 3.3. You might want to ask the author, G=E9rard Roudier > (). Hmm... I think upgrading to 3.4 stable is feasible. Hope it helps. Thanks for all your input. /palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 8 6:59:10 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ns3.tstt.net.tt (ns3.tstt.net.tt [196.3.132.3]) by hub.freebsd.org (Postfix) with ESMTP id CDC1237B522 for ; Thu, 8 Jun 2000 06:59:04 -0700 (PDT) (envelope-from dchulhan@uwi.tt) Received: from mis-dale (cuscon2290.tstt.net.tt [209.94.210.112]) by ns3.tstt.net.tt with SMTP id JAA83658; Thu, 8 Jun 2000 09:53:09 -0400 Message-ID: <002501bfce92$fdd4ec00$0dc8cb83@mis-dale> From: "Dale Chulhan - Work" To: "Tom Lislegaard" , "Jamie Bowden" Cc: Subject: Re: Plextor CD-R Date: Sun, 4 Jun 2000 22:08:35 -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 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok cool I read it what about re-writables? I have a plex 8x4x32 ..... any takers.... PS: If you need a vacation come to Trinidad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 8 7: 0:33 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 9117237B522 for ; Thu, 8 Jun 2000 07:00:27 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id KAA91965 for ; Thu, 8 Jun 2000 10:01:20 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Thu, 8 Jun 2000 10:01:20 -0400 (EDT) From: Adam To: hardware@freebsd.org Subject: Re: Plextor CD-R In-Reply-To: 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 Also see the gcombust port if you'd like a nice, stable, helpful interface to burning. On Thu, 8 Jun 2000, Tom Lislegaard wrote: >Cdrecord supports just about any cdwriter you can buy today. >See >http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html > >-tom > >On Thu, 8 Jun 2000, Jamie Bowden wrote: > >> >> I just bought and installed the Plextor PlexWriter 8/20 CD-R. FreeBSD of >> course recognizes and uses it as a SCSI CD-ROM, so no issue there. What >> I'm curious about is whether it's a supported writeable drive. I didn't >> buy it with the intention of doing writes in FreeBSD, but it would be nice >> to know if I could. >> >> Jamie Bowden >> >> -- >> >> "Of course, that's sort of like asking how other than Marketing, >> Microsoft is different from any other software company..." >> Kenneth G. Cavness >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hardware" in the body of the message >> > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" 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 Thu Jun 8 7: 2:56 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 0C27C37BFE9 for ; Thu, 8 Jun 2000 07:02:54 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id KAA91977; Thu, 8 Jun 2000 10:03:32 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Thu, 8 Jun 2000 10:03:32 -0400 (EDT) From: Adam To: Dale Chulhan - Work , hardware@freebsd.org Subject: Re: Plextor CD-R In-Reply-To: <002501bfce92$fdd4ec00$0dc8cb83@mis-dale> 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 cdrecord and cdrdao both support rewritables. Be sure to check into both to realize what one does and doesn't. On Sun, 4 Jun 2000, Dale Chulhan - Work wrote: >Ok cool I read it what about re-writables? > >I have a plex 8x4x32 ..... any takers.... > >PS: If you need a vacation come to Trinidad. > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" 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 Thu Jun 8 12:20:45 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mendota.terracom.net (mendota.terracom.net [208.170.71.129]) by hub.freebsd.org (Postfix) with ESMTP id E79DC37BCC0 for ; Thu, 8 Jun 2000 12:20:35 -0700 (PDT) (envelope-from gdfriou@terracom.net) Received: from [10.0.0.51] (gw1.terracom.net [208.170.71.143]) by mendota.terracom.net (8.9.1a/8.8.7) with SMTP id OAA08467; Thu, 8 Jun 2000 14:29:23 -0500 (CDT) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 8 Jun 2000 14:23:38 -0500 To: hardware@FreeBSD.ORG From: gdfriou@terracom.net (George Friou) Subject: help with sendmail error message 554 Cc: gunther@terracom.net Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Trying to get sendmail v8.9.3 working on a warm spare. It works completely correctly from the command line but when we use a POP client (ie eudora and netscape on a client) We get the sendmail error "554 rewrite map resolve not found" Anybody run into this? Please, HELLLLLLPPPPPP!!! arghhhh. Thanks, George ------------------------------------------------------------------------ George D. Friou TerraCom, Inc. gdfriou@terracom.net Data Communications & Internet Access (608) 250-4444 http://www.terracom.net/ ------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 8 13:46:35 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from brs.com.br (brs.com.br [192.41.24.32]) by hub.freebsd.org (Postfix) with ESMTP id 8BD4B37C04E for ; Thu, 8 Jun 2000 13:46:30 -0700 (PDT) (envelope-from email@carlos.eti.br) Received: from fraga.carlos.eti.br ([200.241.0.6]) by brs.com.br (8.8.5) id SAA13041; Thu, 8 Jun 2000 18:46:27 -0200 (GMT+2) X-Authentication-Warning: brs.com.br: Host [200.241.0.6] claimed to be fraga.carlos.eti.br Message-Id: <4.3.2.7.2.20000608174807.00b2ac50@carlos.eti.br> X-Sender: email@carlos.eti.br X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 08 Jun 2000 17:48:12 -0300 To: freebsd-hardware@FreeBSD.ORG From: Carlos Fraga Subject: Re: It's worth ! Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A site that pays you to receive some e-mails. No more than that. Nothing to buy, just to receive the e-mail and click on the link to visit the site. Don't you believe it exists ? Yes, it exists. And I have already received a US$ 50,00 check. Will you say that you don't want some money ? It's up to you to subscribe and start receiving e-mails and money ! Follow the link: http://www.sendmoreinfo.com/id/871883 See you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 8 18:18:33 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from endplay.inode.org (cpu1532.adsl.bellglobal.com [206.47.27.13]) by hub.freebsd.org (Postfix) with ESMTP id C8EE237B681 for ; Thu, 8 Jun 2000 18:18:19 -0700 (PDT) (envelope-from dej@inode.org) Received: from coup.inode.org (coup.inode.org [172.16.2.203]) by endplay.inode.org (8.9.3/8.9.3) with SMTP id VAA10731 for ; Thu, 8 Jun 2000 21:18:16 -0400 (EDT) From: David Jones To: freebsd-hardware@freebsd.org Subject: VIA 82C686 AC'97 audio driver for FreeBSD 4.0: BETA Date: Thu, 8 Jun 2000 21:16:07 -0400 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00060821181305.12650@coup.inode.org> Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Several users have asked about the on-board AC'97 audio on motherboards u= sing the VIA Technologies VT82C686A south bridge chip. I have developed a beta driver that fits into the "pcm" framework. http://www.inode.org/sw/auvia/ for details. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 9 15:12: 9 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id D555F37B756 for ; Fri, 9 Jun 2000 15:12:05 -0700 (PDT) (envelope-from jin@portnoy.lbl.gov) Received: (from jin@localhost) by george.lbl.gov () id PAA21446 for hardware@freebsd.org; Fri, 9 Jun 2000 15:12:05 -0700 (PDT) Date: Fri, 9 Jun 2000 15:12:05 -0700 (PDT) From: Jin Guojun (FTG staff) Message-Id: <200006092212.PAA21446@george.lbl.gov> To: hardware@freebsd.org Subject: which is a better GigB network adapter supported in FreeBSD Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I see two group of GigB network NIC listed in supported hardware. (1) Alteon Networks PCI gigabit ethernet NICs based on the Tigon 1 and Tigon 2 chipsets including the Alteon AceNIC (Tigon 1 and 2), 3Com 3c985-SX (Tigon 1 and 2), Netgear GA620 (Tigon 2), Silicon Graphics Gigabit Ethernet, DEC/Compaq EtherWORKS 1000, NEC Gigabit Ethernet (2) SysKonnect SK-984x PCI gigabit ethernet cards including the SK-9841 1000baseLX (single mode fiber, single port), the SK-9842 1000baseSX (multimode fiber, single port), the SK-9843 1000baseLX (single mode fiber, dual port), and the SK-9844 1000baseSX (multimode fiber, dual port). I heard from people, who use them under Linux, said that SysKonnect has better performance (20% higher) than Alteon, but price is high ($700 : $250). Just by look at the list, I think I will buy some of following NICs and would like to get information on these NIC: Alteon AceNIC (Tigon 1 and 2), 3Com 3c985-SX (Tigon 1 and 2), and Netgear GA620 (Tigon 2) from group 1, and/or SK-9842 1000baseSX (multimode fiber, single port) and the SK-9844 1000baseSX (multimode fiber, dual port) from group 2. If people have used any some of these adapters can drop me the info. about how reliable these NICs are, how is the performance and price ratio, and what are the maximum MTUs they support, it will be appreciated. Thanks, -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 9 15:53: 6 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id B50ED37C821 for ; Fri, 9 Jun 2000 15:52:56 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA78031; Fri, 9 Jun 2000 16:52:45 -0600 (MDT) (envelope-from ken) Date: Fri, 9 Jun 2000 16:52:45 -0600 From: "Kenneth D. Merry" To: Jin Guojun Cc: hardware@FreeBSD.ORG Subject: Re: which is a better GigB network adapter supported in FreeBSD Message-ID: <20000609165245.A77888@panzer.kdm.org> References: <200006092212.PAA21446@george.lbl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006092212.PAA21446@george.lbl.gov>; from jin@george.lbl.gov on Fri, Jun 09, 2000 at 03:12:05PM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jun 09, 2000 at 15:12:05 -0700, Jin Guojun wrote: > I see two group of GigB network NIC listed in supported hardware. > > (1) > Alteon Networks PCI gigabit ethernet NICs based on the Tigon 1 and Tigon 2 > chipsets including the > Alteon AceNIC (Tigon 1 and 2), > 3Com 3c985-SX (Tigon 1 and 2), > Netgear GA620 (Tigon 2), > Silicon Graphics Gigabit Ethernet, > DEC/Compaq EtherWORKS 1000, NEC Gigabit Ethernet > > (2) > SysKonnect SK-984x PCI gigabit ethernet cards including > the SK-9841 1000baseLX (single mode fiber, single port), > the SK-9842 1000baseSX (multimode fiber, single port), > the SK-9843 1000baseLX (single mode fiber, dual port), > and the SK-9844 1000baseSX (multimode fiber, dual port). > > I heard from people, who use them under Linux, said that SysKonnect has > better performance (20% higher) than Alteon, but price is high ($700 : $250). I find that hard to believe. I have personally gotten 800Mbps performance from an Alteon board on Pentium II 450's. Drew Gallatin has gotten almost a gigabit out of them (988Mbps, I think). There's not much room for 20% better performance there. One thing you have to be careful about is that there are two big measures that people use for performance in high speed networking -- latency and bandwidth. My main interest is bandiwdth. People who are into clustering get more excited about low latency. The SysKonnect boards may well have lower latency, I don't know. In any case, IIRC, with the SysKonnect board, you've got a choice between jumbo frames and checksum offloading -- you can't do both at the same time. I believe the current sk(4) driver chooses jumbo frames over checksum offloading. You might talk to Bill Paul for confirmation on the jumbo frames/checksum offloading tradeoff. With the Alteon boards, you can have both jumbo frames and checksum offloading. > Just by look at the list, I think I will buy some of following NICs > and would like to get information on these NIC: > > Alteon AceNIC (Tigon 1 and 2), 3Com 3c985-SX (Tigon 1 and 2), and > Netgear GA620 (Tigon 2) from group 1, > > and/or > > SK-9842 1000baseSX (multimode fiber, single port) and > the SK-9844 1000baseSX (multimode fiber, dual port) from group 2. > > If people have used any some of these adapters can drop me the info. > about how reliable these NICs are, how is the performance and price ratio, > and what are the maximum MTUs they support, it will be appreciated. I have 12+ FreeBSD machines with 1MB Alteon ACEnics, and I would highly recommend Alteon based boards. I would recommend getting a Tigon 2 board over a Tigon 1 board. It would probably be hard to get a Tigon 1 board now anyway. You can buy the boards straight from Alteon, but it will probably be cheaper to get the Netgear or 3Com versions. The Netgear boards have 512K SRAM, the 3Com boards have 1MB SRAM, thus the price difference between the two. If you get a 3Com board, you'll want the 3c985B, the 'B' being the important part, since I think that indicates the Tigon 2 version of the board. As far as reliability, I haven't run into a bad card yet. One thing to watch out for with the Netgear boards, if you're going to use them under Windows, is that Netgear's Windows driver doesn't support jumbo frames. That's probably just a marketing gimmick, but the boards support jumbo frames just fine under FreeBSD. If you're interested in jumbo frames (you really need jumbo frames to get decent bandwidth), you should be careful about what switch you buy. The Alteon switches all support jumbo frames, but many other switch vendors don't support jumbo frames. I think Cisco supports jumbo frames on one or more of their high end Catalyst switches, but IIRC you can do VLANs or jumbo frames, but not both at the same time. One interesting thing about the Catalyst (at least the spec sheet I looked at on Cisco's web site), is that they support up to 10240 byte frames, not just the standard 9000 byte jumbo frame. (The maximum MTU is configurable.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jun 10 13: 5:50 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net [207.172.4.62]) by hub.freebsd.org (Postfix) with ESMTP id DF15237B5C5 for ; Sat, 10 Jun 2000 13:05:47 -0700 (PDT) (envelope-from goldtech@worldpost.com) Received: from 209-122-224-14.s268.tnt3.nyw.ny.dialup.rcn.com ([209.122.224.14] helo=beefstew) by smtp03.mrf.mail.rcn.net with smtp (Exim 2.12 #3) id 130rVp-0003wG-00 for hardware@FreeBSD.ORG; Sat, 10 Jun 2000 16:05:45 -0400 Message-ID: <000701bfd317$63005d20$0ee07ad1@beefstew> From: "leegold" To: Subject: tweak geometric shapes Date: Sat, 10 Jun 2000 16:06:37 -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.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org i have a mitsubishi diamondtron71 monitor. i use xFree86 3.3.6. I have a slight problem - not major but it's bugging me. I noticed that my shapes were a bit out of whack - squares not square, lines not straight ect. So I pressed the factory reset button on the monitor - it said "user timing can not reset". I called mitsubishi, they said since the x-windows is using some "custom" configs for the refresh rates ect. the monitor will not reset. So, I connected the monitor to my NT4.0 box, and it was able to reset. But, then when I reconnected it to my FreeBSD box w/X it was back to the distorted shapeds - but note: imo, it is not x that's doing it, - it's imo, only a matter of reseting the monitor to the right geometry. There are about 7 different geometric adjustments on this monitor. Does anyone have any idea how I could get it correct? Are there any test patterns or procedures I could use to (instead of reset) tweak the geometric rendition? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jun 10 22: 4:47 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ren.sasknow.com (ren.sasknow.com [207.195.92.131]) by hub.freebsd.org (Postfix) with ESMTP id E1DD737BECE for ; Sat, 10 Jun 2000 22:04:41 -0700 (PDT) (envelope-from ryan@sasknow.com) Received: from localhost (ryan@localhost) by ren.sasknow.com (8.9.3/8.9.3) with ESMTP id XAA54232 for ; Sat, 10 Jun 2000 23:06:18 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Sat, 10 Jun 2000 23:06:18 -0600 (CST) From: Ryan Thompson To: freebsd-hardware@freebsd.org Subject: 3COM 3C900B-TPO (xl0) under FreeBSD 4.0-RELEASE Message-ID: Organization: SaskNow Technologies [www.sasknow.com] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, I scanned the mailing lists with no real luck. Are there any known problems with the 3C900B-TPO cards (xl0 driver) under 4.0? I got the following message in relation to xl0 (if memory serves!) xl0: could not map memory/ports (I assume this means "conflict" in one form or another). This is a PCI card with no jumpers, so there appears to be little I can do to move the card to a different memory range. As luck (or planning!) would have it, I didn't have another card (same or different type) handy to test. I may try a netgear (dc0) card next week. - Ryan -- Ryan Thompson Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jun 10 22:12: 0 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from europa.engg.ksu.edu (Europa.engg.ksu.edu [129.130.81.112]) by hub.freebsd.org (Postfix) with ESMTP id 7F34637BECE for ; Sat, 10 Jun 2000 22:11:57 -0700 (PDT) (envelope-from dave@europa.engg.ksu.edu) Received: from phobos.engg.ksu.edu (phobos.engg.ksu.edu [129.130.81.133]) by europa.engg.ksu.edu (8.9.3/8.9.3) with ESMTP id AAA19656; Sun, 11 Jun 2000 00:11:54 -0500 (CDT) Received: from phobos.engg.ksu.edu (phobos.engg.ksu.edu [129.130.81.133]) by phobos.engg.ksu.edu (8.9.3+Sun/8.9.1) with SMTP id AAA12872; Sun, 11 Jun 2000 00:20:59 -0500 (CDT) Message-Id: <200006110520.AAA12872@phobos.engg.ksu.edu> Date: Sun, 11 Jun 2000 00:20:58 -0500 (CDT) From: Dave Haney Reply-To: Dave Haney Subject: Re: 3COM 3C900B-TPO (xl0) under FreeBSD 4.0-RELEASE To: ryan@sasknow.com Cc: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: 2MGAhRDuDQnYGSwtak2czg== X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4m sparc Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ryan, For what it's worth; I have this card working under FreeBSD on a AlphaStation 200. I've never had any problems with it. Have a nice day. [snip] xl0: <3Com 3cSOHO100-TX OfficeConnect> port 0x10100-0x1017f mem 0x82020100-0x8202017f irq 9 at device 13.0 on pci0 xl0: interrupting at ISA irq 9 xl0: Ethernet address: 00:50:da:75:d9:d2 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto [snip] >Delivered-To: freebsd-hardware@freebsd.org >Date: Sat, 10 Jun 2000 23:06:18 -0600 (CST) >From: Ryan Thompson >To: freebsd-hardware@FreeBSD.ORG >Subject: 3COM 3C900B-TPO (xl0) under FreeBSD 4.0-RELEASE >MIME-Version: 1.0 >X-Loop: FreeBSD.org > > >Hello all, > >I scanned the mailing lists with no real luck. Are there any known >problems with the 3C900B-TPO cards (xl0 driver) under 4.0? I got the >following message in relation to xl0 (if memory serves!) > >xl0: could not map memory/ports > >(I assume this means "conflict" in one form or another). This is a PCI >card with no jumpers, so there appears to be little I can do to move the >card to a different memory range. > >As luck (or planning!) would have it, I didn't have another card (same or >different type) handy to test. I may try a netgear (dc0) card next week. > >- Ryan > >-- > Ryan Thompson > Systems Administrator, Accounts > Phone: +1 (306) 664-1161 > > SaskNow Technologies http://www.sasknow.com > #106-380 3120 8th St E Saskatoon, SK S7H 0W2 > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message Dave Haney College of Engineering Computer Systems Analyst Kansas State University dave@engg.ksu.edu 785.532.4643 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message