From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 18 17:37:10 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 17F3616A403 for ; Mon, 18 Dec 2006 17:37:10 +0000 (UTC) (envelope-from valenok@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id D65B943C9F for ; Mon, 18 Dec 2006 17:34:02 +0000 (GMT) (envelope-from valenok@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so1889222nfc for ; Mon, 18 Dec 2006 09:33:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=un/yHp1HF+U8w/jkOFzLbWBu/cxEv5HfS3Sw31M9Vpd81dL1t6LC39mk5MHCIJtBKzC49vIZuOTLDfbl4aVmkxUhXvkepbH7mQ/saeBice9nX+k9TsypzeULNtV5nwcHkzRdxj8ptIUmE+Uy6ysiUjFDSbL3LjthoLw8E+Vz7Y0= Received: by 10.49.8.1 with SMTP id l1mr7960910nfi.1166461471291; Mon, 18 Dec 2006 09:04:31 -0800 (PST) Received: by 10.48.216.12 with HTTP; Mon, 18 Dec 2006 09:04:31 -0800 (PST) Message-ID: <72c3a9570612180904t6dba47das5ea0cbcc34cd2b4b@mail.gmail.com> Date: Mon, 18 Dec 2006 17:04:31 +0000 From: "Sergey Lyubka" To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Dell Poweredge 1950, boot problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2006 17:37:10 -0000 Hi, when booting FreBSD 6.2 on Dell Poweredge, I see the following: 1. It boots OK only in 'safe mode' . acpi is disabled, and only 1 cpu is detected. 2. If boot normally (with ACPI), boot almost always hangs just before detecting the harddrive (SAS). If it boots, 8 CPUs are detected, while only 2 are under the cover. Has anybody any idea on how to boot it properly? From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 18 18:54:28 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 050FF16A407 for ; Mon, 18 Dec 2006 18:54:28 +0000 (UTC) (envelope-from mureninc@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C0E243CA7 for ; Mon, 18 Dec 2006 18:54:23 +0000 (GMT) (envelope-from mureninc@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so1406219wxc for ; Mon, 18 Dec 2006 10:53:54 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PolZ8r25DNAMOLPE4/2gO0rg29QZQvAhkHtDRFn6BLBv8li2YPSXGIqv2cw2wOS44h81lwGRJxKou98nrsDREj13gkPf6X3dCedxPz24cyqTqfqHgThVrGoIrJIkIg46EZOCiInJruPsJkqXqCiv1IBL56xGvceqmpsYhR1RsIc= Received: by 10.70.125.2 with SMTP id x2mr7992711wxc.1166466510713; Mon, 18 Dec 2006 10:28:30 -0800 (PST) Received: by 10.70.36.16 with HTTP; Mon, 18 Dec 2006 10:28:30 -0800 (PST) Message-ID: Date: Mon, 18 Dec 2006 13:28:30 -0500 From: "Constantine A. Murenin" To: "Sergey Lyubka" In-Reply-To: <72c3a9570612180904t6dba47das5ea0cbcc34cd2b4b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <72c3a9570612180904t6dba47das5ea0cbcc34cd2b4b@mail.gmail.com> Cc: freebsd-hardware@freebsd.org Subject: Re: Dell Poweredge 1950, boot problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2006 18:54:28 -0000 On 18/12/06, Sergey Lyubka wrote: > Hi, when booting FreBSD 6.2 on Dell Poweredge, I see the following: > > 1. It boots OK only in 'safe mode' . acpi is disabled, and only 1 cpu > is detected. > 2. If boot normally (with ACPI), boot almost always hangs just before > detecting the > harddrive (SAS). If it boots, 8 CPUs are detected, while only 2 are > under the cover. > > Has anybody any idea on how to boot it properly? You probably should have attached some dmesg. You may have 8 CPUs because of the Hyper-threading and such. So I wouldn't necessarily count many CPUs being detected as an indication of something being wrong... Cheers, Constantine. From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 18 19:06:00 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EF07416A501 for ; Mon, 18 Dec 2006 19:06:00 +0000 (UTC) (envelope-from simon@optinet.com) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.FreeBSD.org (Postfix) with SMTP id 3EFC243D68 for ; Mon, 18 Dec 2006 19:05:51 +0000 (GMT) (envelope-from simon@optinet.com) Received: (qmail 9210 invoked by uid 110); 18 Dec 2006 18:39:02 -0000 Received: from unknown (HELO desktop1) (simon%optinet.com@69.112.29.182) by cobra.acceleratedweb.net with SMTP; 18 Dec 2006 18:39:02 -0000 From: "Simon" To: "freebsd-hardware@freebsd.org" , "Sergey Lyubka" Date: Mon, 18 Dec 2006 13:39:07 -0500 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2717) For Windows 2000 (5.1.2600;2) In-Reply-To: <72c3a9570612180904t6dba47das5ea0cbcc34cd2b4b@mail.gmail.com> MIME-Version: 1.0 Message-Id: <20061218190551.3EFC243D68@mx1.FreeBSD.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Dell Poweredge 1950, boot problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2006 19:06:01 -0000 Are you booting amd64 on it? default kernel? -Simon On Mon, 18 Dec 2006 17:04:31 +0000, Sergey Lyubka wrote: >Hi, when booting FreBSD 6.2 on Dell Poweredge, I see the following: >1. It boots OK only in 'safe mode' . acpi is disabled, and only 1 cpu >is detected. >2. If boot normally (with ACPI), boot almost always hangs just before >detecting the >harddrive (SAS). If it boots, 8 CPUs are detected, while only 2 are >under the cover. >Has anybody any idea on how to boot it properly? >_______________________________________________ >freebsd-hardware@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 19 15:02:42 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0EE6316A407 for ; Tue, 19 Dec 2006 15:02:42 +0000 (UTC) (envelope-from valenok@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FF0343CA2 for ; Tue, 19 Dec 2006 15:02:39 +0000 (GMT) (envelope-from valenok@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so2163067nfc for ; Tue, 19 Dec 2006 07:02:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=asgbAIhhKFGObHaxMM3rXM+FXHqrlASs43ivYpK/VKY/W7J9evohpByVV2Dy42h4r2J+XY8mxhxFR8JDLUdyxqoUg85cXWIIJJKV9fpxqT0XHUoaPKcFZasUEL8eRIr0pPnLcjXppWEHtW7P8DYAQOKsJQlb0M0IXZ3SvcPu39g= Received: by 10.49.19.18 with SMTP id w18mr684128nfi.1166540548746; Tue, 19 Dec 2006 07:02:28 -0800 (PST) Received: by 10.48.216.12 with HTTP; Tue, 19 Dec 2006 07:02:28 -0800 (PST) Message-ID: <72c3a9570612190702j55d98b48s64a471e0923c786b@mail.gmail.com> Date: Tue, 19 Dec 2006 15:02:28 +0000 From: "Sergey Lyubka" To: Simon In-Reply-To: <4586e047.0c5f3bc7.600b.ffff85e7SMTPIN_ADDED@mx.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <72c3a9570612180904t6dba47das5ea0cbcc34cd2b4b@mail.gmail.com> <4586e047.0c5f3bc7.600b.ffff85e7SMTPIN_ADDED@mx.google.com> Cc: "freebsd-hardware@freebsd.org" Subject: Re: Dell Poweredge 1950, boot problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2006 15:02:42 -0000 I figured out, that the APIC is responsible for that. If APIC is turned off, then the box boots fine (although it cannot see more that 1 CPU). Here is the dmesg with APIC disabled: Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-PRERELEASE #1: Tue Dec 19 14:29:09 GMT 2006 devnull@valenok.netfort-iss.com:/usr/var/tmp/devnull/obj/usr/src/sys/MANAGER Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2995.51-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf64 Stepping = 4 Features=0xbfebfbff Features2=0xe4bd,> AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 Logical CPUs per core: 2 real memory = 1073381376 (1023 MB) avail memory = 999518208 (953 MB) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci5: on pcib1 pcib2: at device 0.0 on pci5 pci6: on pcib2 pcib3: at device 0.0 on pci6 pci7: on pcib3 pcib4: at device 1.0 on pci6 pci9: on pcib4 pcib5: at device 0.3 on pci5 pci10: on pcib5 pcib6: at device 3.0 on pci0 pci1: on pcib6 pcib7: at device 0.0 on pci1 pci2: on pcib7 mpt0: port 0xec00-0xecff mem 0xfddfc000-0xfddfffff,0xfdde0000-0xfddeffff irq 6 at device 8.0 on pci2 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.5.12.0 mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). mpt0: mpt_cam_event: 0x12 mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). pcib8: at device 4.0 on pci0 pci11: on pcib8 bge0: mem 0xfd8f0000-0xfd8fffff irq 6 at device 0.0 on pci11 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:10:18:19:68:ae pcib9: at device 5.0 on pci0 pci12: on pcib9 pcib10: at device 6.0 on pci0 pci13: on pcib10 pcib11: at device 7.0 on pci0 pci14: on pcib11 pcib12: at device 28.0 on pci0 pci3: on pcib12 uhci0: port 0xcce0-0xccff irq 11 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xccc0-0xccdf irq 10 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xcca0-0xccbf irq 11 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib13: at device 30.0 on pci0 pci15: on pcib13 pci15: at device 13.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 sio0: configured irq 0 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 0 not in bitmap of probed irqs 0 sio0: port may not be enabled fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 sio0: configured irq 0 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 0 not in bitmap of probed irqs 0 sio0: port may not be enabled orm0: at iomem 0xc0000-0xc8fff,0xec000-0xeffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled uhub3: vendor 0x04b4 product 0x6560, class 9/0, rev 2.00/0.0b, addr 2 uhub3: 4 ports with 4 removable, self powered ukbd0: Dell Dell USB Keyboard, rev 1.10/3.01, addr 3, iclass 3/1 kbd1 at ukbd0 Timecounter "TSC" frequency 2995514748 Hz quality 800 Timecounters tick every 1.000 msec mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). acd0: CDROM at ata0-master UDMA33 ses0 at mpt0 bus 0 target 8 lun 0 ses0: Fixed Enclosure Services SCSI-5 device ses0: 300.000MB/s transfers ses0: SCSI-3 SES Device da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 300.000MB/s transfers, Tagged Queueing Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) Trying to mount root from ufs:/dev/md0 bge0: link state changed to UP However, with APIC turned on, the boot stops here: Timecounters tick every 1.000 msec mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). acd0: CDROM at ata0-master UDMA33 <---- hang ---> It looks like it stopped on ses0 detection. The hang is nasty: event the powercycle button didn't work, I had to unplug the power led and plug it again. Any ideas ? Please advise. sergey From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 21 15:19:55 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8E1B216A403 for ; Thu, 21 Dec 2006 15:19:55 +0000 (UTC) (envelope-from ebbe@bornholmermail.dk) Received: from web11.talkactive.net (web11.talkactive.net [195.128.174.111]) by mx1.freebsd.org (Postfix) with ESMTP id 135A513C455 for ; Thu, 21 Dec 2006 15:19:54 +0000 (UTC) (envelope-from ebbe@bornholmermail.dk) Received: from bornholmermail.dk (localhost.web13.talkactive.net [127.0.0.1]) by web11.talkactive.net (8.13.3/8.13.3) with ESMTP id kBLF9XgA073161 for ; Thu, 21 Dec 2006 16:09:34 +0100 (CET) (envelope-from ebbe@bornholmermail.dk) Received: from 217.157.0.66 (SquirrelMail authenticated user ebbe@bornholmermail.dk) by bornholmermail.dk with HTTP; Thu, 21 Dec 2006 16:09:34 +0100 (CET) Message-ID: <63586.217.157.0.66.1166713774.squirrel@bornholmermail.dk> Date: Thu, 21 Dec 2006 16:09:34 +0100 (CET) From: "Ebbe Hjorth" To: freebsd-hardware@freebsd.org User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: FreeBSD on Dell PowerEdge 860 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Dec 2006 15:19:55 -0000 Hi, Did anyone try FreeBSD on a Dell PowerEdge 860? Best regards Ebbe, Denmark From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 21 15:35:32 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6682B16A555 for ; Thu, 21 Dec 2006 15:35:32 +0000 (UTC) (envelope-from ebbe@bornholmermail.dk) Received: from web11.talkactive.net (web11.talkactive.net [195.128.174.111]) by mx1.freebsd.org (Postfix) with ESMTP id 008FF13C46F for ; Thu, 21 Dec 2006 15:35:31 +0000 (UTC) (envelope-from ebbe@bornholmermail.dk) Received: from bornholmermail.dk (localhost.web13.talkactive.net [127.0.0.1]) by web11.talkactive.net (8.13.3/8.13.3) with ESMTP id kBLFZQxR085367 for ; Thu, 21 Dec 2006 16:35:26 +0100 (CET) (envelope-from ebbe@bornholmermail.dk) Received: from 217.157.0.66 (SquirrelMail authenticated user ebbe@bornholmermail.dk) by bornholmermail.dk with HTTP; Thu, 21 Dec 2006 16:35:26 +0100 (CET) Message-ID: <1596.217.157.0.66.1166715326.squirrel@bornholmermail.dk> In-Reply-To: <1166715176.13877.36.camel@picard.scorec.rpi.edu> References: <63586.217.157.0.66.1166713774.squirrel@bornholmermail.dk> <1166715176.13877.36.camel@picard.scorec.rpi.edu> Date: Thu, 21 Dec 2006 16:35:26 +0100 (CET) From: "Ebbe Hjorth" To: freebsd-hardware@freebsd.org User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: FreeBSD on Dell PowerEdge 860 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Dec 2006 15:35:32 -0000 Hi, Ohh, soo cool - Do you know if the 6.1 works? -> Ebbe > Yes. 6.2-RC1 works fine with the SAS5/i RAID controller (haven't tried > onboard SATA controller). > > Adam > > On Thu, 2006-12-21 at 16:09 +0100, Ebbe Hjorth wrote: >> Hi, >> >> Did anyone try FreeBSD on a Dell PowerEdge 860? >> >> >> Best regards Ebbe, Denmark >> >> _______________________________________________ >> freebsd-hardware@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >> To unsubscribe, send any mail to >> "freebsd-hardware-unsubscribe@freebsd.org" > > > From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 21 16:01:08 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3688D16A412 for ; Thu, 21 Dec 2006 16:01:08 +0000 (UTC) (envelope-from todora@scorec.rpi.edu) Received: from janeway.scorec.rpi.edu (mail.scorec.rpi.edu [128.113.131.17]) by mx1.freebsd.org (Postfix) with ESMTP id 10EBA13C459 for ; Thu, 21 Dec 2006 16:01:08 +0000 (UTC) (envelope-from todora@scorec.rpi.edu) Received: from janeway.scorec.rpi.edu (localhost.localdomain [127.0.0.1]) by janeway.scorec.rpi.edu (Postfix) with ESMTP id 3B0D8C821B; Thu, 21 Dec 2006 10:32:57 -0500 (EST) Received: from picard.scorec.rpi.edu (picard.scorec.rpi.edu [128.113.131.145]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by janeway.scorec.rpi.edu (Postfix) with ESMTP id 25CB9C8048; Thu, 21 Dec 2006 10:32:57 -0500 (EST) From: Adam Todorski To: Ebbe Hjorth In-Reply-To: <63586.217.157.0.66.1166713774.squirrel@bornholmermail.dk> References: <63586.217.157.0.66.1166713774.squirrel@bornholmermail.dk> Content-Type: text/plain Date: Thu, 21 Dec 2006 10:32:56 -0500 Message-Id: <1166715176.13877.36.camel@picard.scorec.rpi.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-27) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD on Dell PowerEdge 860 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Dec 2006 16:01:08 -0000 Yes. 6.2-RC1 works fine with the SAS5/i RAID controller (haven't tried onboard SATA controller). Adam On Thu, 2006-12-21 at 16:09 +0100, Ebbe Hjorth wrote: > Hi, > > Did anyone try FreeBSD on a Dell PowerEdge 860? > > > Best regards Ebbe, Denmark > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 22 08:08:58 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EC22916A407 for ; Fri, 22 Dec 2006 08:08:58 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (keira.kiwi-computer.com [63.224.10.3]) by mx1.freebsd.org (Postfix) with SMTP id 5FFDA13C46D for ; Fri, 22 Dec 2006 08:08:58 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: (qmail 47670 invoked by uid 2001); 22 Dec 2006 08:05:14 -0000 Date: Fri, 22 Dec 2006 02:05:14 -0600 From: "Rick C. Petty" To: freebsd-hardware@freebsd.org Message-ID: <20061222080514.GA47148@keira.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: broken USB in 5.5-stable X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Dec 2006 08:08:59 -0000 Hello. I freshly upgraded a 5.1+ i386 box to the latest 5.5-stable. For some reason, I can't get it to recognize any USB devices (I've only tried mice, a scanner, and a printer). I know usbd is running: # ps axww | grep usbd 414 ?? Ss 0:00:00 /usr/sbin/usbd At first I thought maybe my mouse was broken, so I booted to my old 5.1 drive, works like a charm. Maybe USB wasn't being correctly reset, but it still doesn't work after a cold restart. I tried running "usbd -dv" and nothing is output as I plug in or unplug any device. One time after warm booting into 5.5 from 5.1, the already-plugged-in mouse was recognized on boot but subsequent unplugs and replugs went unnoticed. Any suggestions? I plan on trying all the 5.x series until I can nail down where it breaks, but I have limited physical access to the machine. Below is my dmesg. The board is an Asus A7N8X-E (nForce2) and I have another almost identical one at home running 5.4 whose USB works like a charm. -- Rick C. Petty Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.5-STABLE #2: Fri Dec 22 01:12:01 CST 2006 rick@myhostname:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) (1730.72-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 Features=0x383fbff AMD Features=0xc0400000 real memory = 1610547200 (1535 MB) avail memory = 1568509952 (1495 MB) mptable_probe: Unable to map end of MP Config Table ACPI APIC Table: ioapic0 irqs 0-23 on motherboard npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xc0000000-0xcfffffff at device 0.0 on pci0 pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xdd080000-0xdd080fff irq 22 at device 2.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xdd083000-0xdd083fff at device 2.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci0: at device 2.2 (no driver attached) pci0: at device 4.0 (no driver attached) pci0: at device 5.0 (no driver attached) pci0: at device 6.0 (no driver attached) pcib1: at device 8.0 on pci0 pci1: on pcib1 pci1: at device 6.0 (no driver attached) rl0: port 0x9000-0x90ff mem 0xda000000-0xda0000ff irq 19 at device 7.0 on pci1 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:48:54:84:17:1d ahc0: port 0x9400-0x94ff mem 0xda001000-0xda001fff irq 17 at device 9.0 on pci1 aic7870: Single Channel A, SCSI Id=7, 16/253 SCBs atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 9.0 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pcib2: at device 12.0 on pci0 pci2: on pcib2 xl0: <3Com 3c920B-EMB Integrated Fast Etherlink XL> port 0xa000-0xa07f mem 0xdc000000-0xdc00007f irq 20 at device 1.0 on pci2 miibus1: on xl0 acphy0: on miibus1 acphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:26:54:0e:9e:8f fwohci0: <1394 Open Host Controller Interface> mem 0xdd087000-0xdd08703f,0xdd086000-0xdd0867ff irq 20 at device 13.0 on pci0 fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:e0:18:00:00:24:35:8b fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:24:35:8b fwe0: Ethernet address: 02:e0:18:24:35:8b fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) fwohci0: phy int pcib3: at device 30.0 on pci0 pci3: on pcib3 speaker0: port 0x61 on acpi0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 ppbus0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: PRINTER ESCPL2,PRPXL24,BDC plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 orm0: at iomem 0xd9000-0xd97ff,0xd6000-0xd87ff,0xd4000-0xd57ff,0xd0000-0xd3fff,0xc0000-0xcf7ff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1730724432 Hz quality 800 Timecounters tick every 1.000 msec ad0: 57278MB [116375/16/63] at ata0-master UDMA100 ad1: 57278MB [116375/16/63] at ata0-slave UDMA100 ad2: 58623MB [119108/16/63] at ata1-master UDMA66 acd0: CDRW at ata1-slave UDMA33 GEOM_MIRROR: Device gm0 created (id=3973574214). GEOM_MIRROR: Device gm0: provider ad0 detected. GEOM_MIRROR: Device gm0: provider ad1 detected. GEOM_MIRROR: Device gm0: provider ad1 activated. GEOM_MIRROR: Device gm0: provider ad0 activated. GEOM_MIRROR: Device gm0: provider mirror/gm0 launched. pass0 at ahc0 bus 0 target 6 lun 0 pass0: Fixed Scanner SCSI-CCS device pass0: 3.300MB/s transfers Mounting root from ufs:/dev/mirror/gm0s1a Pre-seeding PRNG: kickstart . Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart . swapon: adding /dev/mirror/gm0s1b as swap device Starting file system checks: /dev/mirror/gm0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mirror/gm0s1a: clean, 479282 free (610 frags, 59834 blocks, 0.1% fragmentation) /dev/mirror/gm0s1d: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mirror/gm0s1d: clean, 1013008 free (56 frags, 126619 blocks, 0.0% fragmentation) /dev/mirror/gm0s1e: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mirror/gm0s1e: clean, 986255 free (231 frags, 123253 blocks, 0.0% fragmentation) /dev/mirror/gm0s1f: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mirror/gm0s1f: clean, 2664271 free (41943 frags, 327791 blocks, 0.8% fragmentation) /dev/mirror/gm0s1g: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mirror/gm0s1g: clean, 18974819 free (843 frags, 2371747 blocks, 0.0% fragmentation) Setting hostname: myhostname. xl0: flags=8843 mtu 1500 options=9 inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255 inet6 fe80::226:54ff:fe0e:9e8f%xl0 prefixlen 64 tentative scopeid 0x2 ether 00:26:54:0e:9e:8f media: Ethernet autoselect (none) status: no carrier lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to deny, logging disabled Flushed all rules. ipfw: getsockopt(IP_FW_ADD) : Invalid argument 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 00300 deny ip from 127.0.0.0/8 to any 65000 allow ip from any to any Firewall rules loaded, starting divert daemons: natd natd: Unable to create divert socket. : Protocol not supported . net.inet.ip.fw.enable: 1 -> 1 Starting dhclient. rl0: flags=8843 mtu 1500 options=8 inet6 fe80::248:54ff:fe84:171d%rl0 prefixlen 64 scopeid 0x1 inet 66.242.73.217 netmask 0xffffffe0 broadcast 66.242.73.223 ether 00:48:54:84:17:1d media: Ethernet autoselect (100baseTX ) status: active Additional routing options: IP gateway=YES . Starting devd. Mounting NFS file systems: . Starting syslogd. Setting date via ntp. Looking for host north-america.pool.ntp.org and service ntp host found : meow.febo.com 22 Dec 01:37:00 ntpdate[342]: adjust time server 24.123.66.139 offset -0.414642 sec ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib /usr/local/libdata/ldconfig/portupgrade a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout Starting usbd. Starting local daemons: . Starting lpd. Updating motd . Configuring syscons: keymap keyrate blanktime . Starting sshd. Starting sendmail. Initial i386 initialization: . Additional ABI support: linux . Starting cron. Local package initialization: Starting openvpn. . Additional TCP options: . Starting moused: moused: unable to open /dev/psm0: No such file or directory . Starting background file system checks in 60 seconds. Fri Dec 22 01:37:05 CST 2006 From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 22 21:27:43 2006 Return-Path: X-Original-To: hardware@freebsd.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 85CAC16A407 for ; Fri, 22 Dec 2006 21:27:43 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp102.rog.mail.re2.yahoo.com (smtp102.rog.mail.re2.yahoo.com [206.190.36.80]) by mx1.freebsd.org (Postfix) with SMTP id 1AED913C41A for ; Fri, 22 Dec 2006 21:27:42 +0000 (UTC) (envelope-from mikej@rogers.com) Received: (qmail 18098 invoked from network); 22 Dec 2006 19:12:42 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=JvzB20Wut7ovDTUsvhW85sbvN4hgq23NE7c8fsHkhfD0Vk89ZthVRVRNeqz9EWg/RT6bhPj/wt85fzyyEFAdfRT3nLNGPNw3dzBLQpEeKr16Gn0KwRUZ58eWj6PH2lzSbm2al1gq8yxfb1HrqTTBRTeJqhaSzcDMCFxiwGC0L60= ; Received: from unknown (HELO ?172.16.0.200?) (mikej@rogers.com@74.111.253.239 with plain) by smtp102.rog.mail.re2.yahoo.com with SMTP; 22 Dec 2006 19:12:42 -0000 X-YMail-OSG: J5SXpGoVM1mCXcOHNeVc5MRDzfy8VnI2Ff4TBgHbYzE9Irb4mqZSgY3FJcMoPLgihOBM8h1YN6L0m2OiMQG3IbRXssIzmYn42m6G516VF4F_G7asVRwJ2l.aihirYqzzsym5yP7itVRl9nAuDpRMD9dWkU59gJynf82bJnFYWoh.unWzIPkwZqrEk.ie Message-ID: <458C2E51.50605@rogers.com> Date: Fri, 22 Dec 2006 14:13:21 -0500 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: John Polstra References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hardware@freebsd.org Subject: Re: Is Dell SC1435 likely to work with FreeBSD? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Dec 2006 21:27:43 -0000 John Polstra wrote: > Do any of you have an opinion as to whether the new Dell SC1435 is > likely to work with FreeBSD (either 6.x or -current)? I don't think > they're shipping yet, so I doubt anybody has actually tried it. The > machine has Opteron 2200 series CPUs with a Broadcom HT-2100 and > HT-1000 chipset, according to the spec sheet. > I've been waiting for support of this chipset for quite some time. It was promised by Scott L months ago, but i've been unable to get any feedback on the status. Do you know if this is supported on 6.2? From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 22 22:28:05 2006 Return-Path: X-Original-To: hardware@freebsd.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C210E16A403 for ; Fri, 22 Dec 2006 22:28:05 +0000 (UTC) (envelope-from jdp@polstra.com) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.freebsd.org (Postfix) with ESMTP id 73C1B13C460 for ; Fri, 22 Dec 2006 22:28:05 +0000 (UTC) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [64.81.189.67]) by blake.polstra.com (8.13.8/8.13.8) with ESMTP id kBMM5XxD040587; Fri, 22 Dec 2006 14:05:33 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <458C2E51.50605@rogers.com> Date: Fri, 22 Dec 2006 14:05:33 -0800 (PST) From: John Polstra To: Mike Jakubik Cc: hardware@freebsd.org Subject: Re: Is Dell SC1435 likely to work with FreeBSD? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Dec 2006 22:28:05 -0000 On 22-Dec-2006 Mike Jakubik wrote: > John Polstra wrote: >> Do any of you have an opinion as to whether the new Dell SC1435 is >> likely to work with FreeBSD (either 6.x or -current)? I don't think >> they're shipping yet, so I doubt anybody has actually tried it. The >> machine has Opteron 2200 series CPUs with a Broadcom HT-2100 and >> HT-1000 chipset, according to the spec sheet. >> > > I've been waiting for support of this chipset for quite some time. It > was promised by Scott L months ago, but i've been unable to get any > feedback on the status. Do you know if this is supported on 6.2? I just booted the 6.2-RC1 install CD on the system, and it seems to work fine. It recognized the SATA controller, the hard drive, and the network ports, and the outputs from fdisk and disklabel were correct. I didn't see any signs of problems. I've been running -current on the system for a week or two without any problems. John From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 22 22:33:24 2006 Return-Path: X-Original-To: hardware@freebsd.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AC26816A492 for ; Fri, 22 Dec 2006 22:33:24 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp100.rog.mail.re2.yahoo.com (smtp100.rog.mail.re2.yahoo.com [206.190.36.78]) by mx1.freebsd.org (Postfix) with SMTP id 7334D13C463 for ; Fri, 22 Dec 2006 22:33:24 +0000 (UTC) (envelope-from mikej@rogers.com) Received: (qmail 4191 invoked from network); 22 Dec 2006 22:33:19 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=ho6PnvGHWRSPYRfdidK26FHlF8zgiaoa84TebaxIGVKxwTpwcOf4A2uagYWV4xGnEmZFXUAArPjRyBGLh8hA7z6UgTWz/sCMV2xnJ27HJkd1TPCj9fkY1zjlRsPRlvh27CqEGi3W8lYsFCqvTPTgrIqSTf5iZJJ4ZupGFewHm4M= ; Received: from unknown (HELO ?172.16.0.200?) (mikej@rogers.com@74.111.253.239 with plain) by smtp100.rog.mail.re2.yahoo.com with SMTP; 22 Dec 2006 22:33:19 -0000 X-YMail-OSG: 73UcE4sVM1lgm4b8pt60mbtT6hefiySoiKaqVdK6EePtqeMJMxfGXv14Dq5sdY_RwTn05Iesae9gXOaWWtc20EbuGM8pW.4bX53GN8jZa9FPRB5xjHtg86gN7voxGDG.gMZ5f86w5BbTwFQ- Message-ID: <458C5D57.2060003@rogers.com> Date: Fri, 22 Dec 2006 17:33:59 -0500 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: John Polstra References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hardware@freebsd.org Subject: Re: Is Dell SC1435 likely to work with FreeBSD? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Dec 2006 22:33:24 -0000 John Polstra wrote: > On 22-Dec-2006 Mike Jakubik wrote: > >> John Polstra wrote: >> >>> I just booted the 6.2-RC1 install CD on the system, and it seems to >>> work fine. It recognized the SATA controller, the hard drive, and the >>> network ports, and the outputs from fdisk and disklabel were >>> correct. I didn't see any signs of problems. >>> >>> I've been running -current on the system for a week or two without >>> any problems. >>> >>> >> Excellent, thank you. Just to be clear though, it is detected as a >> HT1000 SATA controller, not a generic one, right? >> > > Right. I've attached the dmesg output for you to look at. > > I asked Soeren Schmidt about this message: > > ad4: DMA limited to UDMA33, device found non-ATA66 cable > > He says it's because the BIOS set up the SATA controller in ATA > compatibility mode. I asked him whether it affects performance, and > he said "not much". He noted that the memory-mapped region does > appear for the SATA controllers, and said that it may be possible to > modify ata-chipset.c slightly to make it use native SATA mode. I > haven't pursued that because (a) I know very little about SATA, and > (b) the hard drive seems to work fine. > > John > Thanks again John, I've CC'd the list for others that may find this information useful. Also, i made a mistake, i referred to Scott L, when i meant Soren S, thanks for the work Soren. > ------------------------------------------------------------------------ > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 6.2-RC1 #0: Thu Nov 16 05:01:36 UTC 2006 > root@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > ACPI APIC Table: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Dual-Core AMD Opteron(tm) Processor 2210 (1800.08-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x40f12 Stepping = 2 > Features=0x178bfbff MOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> > Features2=0x2001 > AMD Features=0xea500800 > AMD Features2=0x1f,,CR8> > Cores per package: 2 > real memory = 2146402304 (2046 MB) > avail memory = 2091376640 (1994 MB) > ioapic0: Changing APIC ID to 2 > ioapic1: Changing APIC ID to 3 > ioapic1: WARNING: intbase 32 != expected base 16 > ioapic2: Changing APIC ID to 4 > ioapic2: WARNING: intbase 64 != expected base 48 > MADT: Forcing active-low polarity and level trigger for SCI > ioapic0 irqs 0-15 on motherboard > ioapic1 irqs 32-47 on motherboard > ioapic2 irqs 64-79 on motherboard > kbd1 at kbdmux0 > ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > cpu0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci3: on pcib1 > pcib2: at device 13.0 on pci3 > pci4: on pcib2 > atapci0: port 0xecb0-0xecb7,0xeca0-0xeca > 3,0xecb8-0xecbf,0xeca4-0xeca7,0xece0-0xecef mem 0xefdfe000-0xefdfffff irq 6 at d > evice 14.0 on pci3 > ata2: on atapci0 > ata3: on atapci0 > atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x > 177,0x376,0x8c0-0x8cf at device 2.1 on pci0 > ata0: on atapci1 > ata1: on atapci1 > isab0: at device 2.2 on pci0 > isa0: on isab0 > ohci0: port 0xd000-0xd0ff mem 0xefbed000-0xefbed > fff irq 11 at device 3.0 on pci0 > ohci0: [GIANT-LOCKED] > usb0: OHCI version 1.0, legacy support > usb0: SMM does not respond, resetting > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > ohci1: port 0xd400-0xd4ff mem 0xefbee000-0xefbee > fff irq 11 at device 3.1 on pci0 > ohci1: [GIANT-LOCKED] > usb1: OHCI version 1.0, legacy support > usb1: on ohci1 > usb1: USB revision 1.0 > uhub1: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > ehci0: port 0xd800-0xd8ff mem 0xefbef000-0xe > fbeffff irq 11 at device 3.2 on pci0 > ehci0: [GIANT-LOCKED] > usb2: EHCI version 1.0 > usb2: companion controllers, 2 ports each: usb0 usb1 > usb2: on ehci0 > usb2: USB revision 2.0 > uhub2: (0x1166) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > uhub2: 4 ports with 4 removable, self powered > uhub3: vendor 0x413c product 0xa001, class 9/0, rev 2.00/0.00, addr 2 > uhub3: multiple transaction translators > uhub3: 2 ports with 2 removable, self powered > pci0: at device 4.0 (no driver attached) > pcib3: irq 32 at device 7.0 on pci0 > pci5: on pcib3 > pcib4: irq 33 at device 8.0 on pci0 > pci1: on pcib4 > bge0: mem 0xefef0000-0xefefffff irq 33 a > t device 0.0 on pci1 > miibus0: on bge0 > brgphy0: on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX > -FDX, auto > bge0: Ethernet address: 00:18:8b:78:b7:b1 > pcib5: irq 37 at device 9.0 on pci0 > pci2: on pcib5 > bge1: mem 0xefff0000-0xefffffff irq 37 a > t device 0.0 on pci2 > miibus1: on bge1 > brgphy1: on miibus1 > brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX > -FDX, auto > bge1: Ethernet address: 00:18:8b:78:b7:b2 > pcib6: irq 35 at device 10.0 on pci0 > pci6: on pcib6 > pcib7: irq 36 at device 11.0 on pci0 > pci7: on pcib7 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > sio0: type 16550A, console > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > pmtimer0 on isa0 > orm0: at iomem 0xc0000-0xc8fff,0xc9000-0xc9fff,0xec000-0xeffff > on isa0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > ppc0: parallel port not found. > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x100> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounter "TSC" frequency 1800080089 Hz quality 800 > Timecounters tick every 1.000 msec > md0: Preloaded image 4423680 bytes at 0xc0af4014 > acd0: CDROM at ata0-master UDMA33 > ad4: DMA limited to UDMA33, device found non-ATA66 cable > ad4: 238418MB at ata2-master UDMA33 > Trying to mount root from ufs:/dev/md0 > /stand/sysinstall running as init on serial console > From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 22 23:12:49 2006 Return-Path: X-Original-To: hardware@freebsd.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0A20B16A403 for ; Fri, 22 Dec 2006 23:12:49 +0000 (UTC) (envelope-from jdp@polstra.com) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.freebsd.org (Postfix) with ESMTP id AC05513C43A for ; Fri, 22 Dec 2006 23:12:48 +0000 (UTC) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [64.81.189.67]) by blake.polstra.com (8.13.8/8.13.8) with ESMTP id kBMNClMG042330; Fri, 22 Dec 2006 15:12:47 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <458C5D57.2060003@rogers.com> Date: Fri, 22 Dec 2006 15:12:47 -0800 (PST) From: John Polstra To: Mike Jakubik Cc: hardware@freebsd.org Subject: Re: Is Dell SC1435 likely to work with FreeBSD? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Dec 2006 23:12:49 -0000 On 22-Dec-2006 Mike Jakubik wrote: > Also, i made a mistake, i referred to Scott L, when > i meant Soren S, thanks for the work Soren. What _is_ it about Scott? A couple of days ago, I referred to him when I meant John Baldwin. :-} John From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 23 14:21:23 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C84B516A407 for ; Sat, 23 Dec 2006 14:21:23 +0000 (UTC) (envelope-from erik.u@dnainternet.net) Received: from isolokki.dnainternet.net (isolokki.dnainternet.net [212.149.75.39]) by mx1.freebsd.org (Postfix) with ESMTP id 8D94F13C45F for ; Sat, 23 Dec 2006 14:21:23 +0000 (UTC) (envelope-from erik.u@dnainternet.net) Received: from [192.168.1.11] (host-212-149-186-30.kpylaajakaista.net [212.149.186.30]) by isolokki.dnainternet.net (Postfix) with ESMTP id 5136DDD67 for ; Sat, 23 Dec 2006 16:02:17 +0200 (EET) Message-ID: <458D36E4.9000900@dnainternet.net> Date: Sat, 23 Dec 2006 16:02:12 +0200 From: Erik Udo User-Agent: Thunderbird 1.5.0.8 (X11/20061114) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org CC: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: memory holes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Dec 2006 14:21:23 -0000 I upgraded my hardware and software yesturday, and for some reason, FreeBSD only 'detects' 128MB of the memory, when the BIOS is clearly seeing 512MB. OpenBSD also finds 512MB of memory. So i added one 128MB ECC memory. There was one 128MB PC100 and 256MB PC133 memory before, and it worked fine on 6.2-PRERELASE. Now that i upgraded to 6.2-RC1, from 6.2-PRERELEASE and added the 128MB memory to the 384MB i had, the kernel started giving me this error on the first line of the kernel output: "Too many holes in the physical address space, giving up" Now, i searched google for anything, and found this earlier thread: http://www.mail-archive.com/freebsd-hardware@freebsd.org/msg01624.html I also found this: http://lists.freebsd.org/pipermail/freebsd-hackers/2005-October/013932.html Like the previous post says, the memory was found after the increased PHYSMAP_SIZE. I increased mine to 2*32, later 2*128. It didn't work. Also someone told me to add this line to the kernel config: options MAXMEM=524288 That didn't work either. I also tried to toggle all the bios settings on the computer, i even upgraded the bios. Nothing. Now i found out that OpenBSD sees 512MB of memory, so there must be some kind of trick to make FreeBSD recognize that memory too. Here is some output of my verbose boot: with 512MB: real memory = 134234112 (128 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000c25000 - 0x0000000007d82fff, 118874112 bytes (29022 pages) avail memory = 121798656 (116 MB) Anyone have any ideas? Thanks, Erik From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 23 17:30:54 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 75D0E16A407 for ; Sat, 23 Dec 2006 17:30:54 +0000 (UTC) (envelope-from erik.u@dnainternet.net) Received: from satakieli.dnainternet.net (satakieli.dnainternet.net [212.149.75.40]) by mx1.freebsd.org (Postfix) with ESMTP id 3F54C13C41A for ; Sat, 23 Dec 2006 17:30:54 +0000 (UTC) (envelope-from erik.u@dnainternet.net) Received: from [192.168.1.11] (host-212-149-186-30.kpylaajakaista.net [212.149.186.30]) by satakieli.dnainternet.net (Postfix) with ESMTP id 49C4ECAC8 for ; Sat, 23 Dec 2006 19:30:51 +0200 (EET) Message-ID: <458D67CC.1050102@dnainternet.net> Date: Sat, 23 Dec 2006 19:30:52 +0200 From: Erik Udo User-Agent: Thunderbird 1.5.0.8 (X11/20061114) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <458D36E4.9000900@dnainternet.net> In-Reply-To: <458D36E4.9000900@dnainternet.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: memory holes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Dec 2006 17:30:54 -0000 OK. I've tested OpenBSD and NetBSD. Both find 512MB of ram, but.. NetBSD crashes after boot stage when it starts to load the kernel. (thanks NetBSD team for not building the kernel image with debugging symbols, but you did build it with DDB) OpenBSD finds 512MB of ram too, but... it wont find my hard disk, even thought it has wd0 as a hard disk in dmesh. To add to my previous post, i tested with 128MB PC100 + 32MB PC100. Both memory modules was found by FreeBSD and put to use. Which leads me to the conclusion: Why can't FreeBSD use PC133 memory when OpenBSD can? Did someone forget to port drivers for memory modules? :P Erik Udo wrote: > I upgraded my hardware and software yesturday, and for some reason, > FreeBSD only 'detects' 128MB of the memory, when the BIOS is clearly > seeing 512MB. OpenBSD also finds 512MB of memory. > > So i added one 128MB ECC memory. There was one 128MB PC100 and 256MB > PC133 memory before, and it worked fine on 6.2-PRERELASE. > > Now that i upgraded to 6.2-RC1, from 6.2-PRERELEASE and added the 128MB > memory to the 384MB i had, the kernel started giving me this error on > the first line of the kernel output: > "Too many holes in the physical address space, giving up" > > Now, i searched google for anything, and found this earlier thread: > http://www.mail-archive.com/freebsd-hardware@freebsd.org/msg01624.html > > I also found this: > http://lists.freebsd.org/pipermail/freebsd-hackers/2005-October/013932.html > > Like the previous post says, the memory was found after the increased > PHYSMAP_SIZE. I increased mine to 2*32, later 2*128. It didn't work. > > Also someone told me to add this line to the kernel config: > options MAXMEM=524288 > > That didn't work either. > > I also tried to toggle all the bios settings on the computer, i even > upgraded the bios. Nothing. > > Now i found out that OpenBSD sees 512MB of memory, so there must be some > kind of trick to make FreeBSD recognize that memory too. > > Here is some output of my verbose boot: > > with 512MB: > real memory = 134234112 (128 MB) > Physical memory chunk(s): > 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) > 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) > 0x0000000000c25000 - 0x0000000007d82fff, 118874112 bytes (29022 pages) > avail memory = 121798656 (116 MB) > > Anyone have any ideas? > > Thanks, > Erik > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 23 18:59:24 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 629F716A40F for ; Sat, 23 Dec 2006 18:59:24 +0000 (UTC) (envelope-from erik.u@dnainternet.net) Received: from satakieli.dnainternet.net (satakieli.dnainternet.net [212.149.75.40]) by mx1.freebsd.org (Postfix) with ESMTP id EA54D13C461 for ; Sat, 23 Dec 2006 18:59:23 +0000 (UTC) (envelope-from erik.u@dnainternet.net) Received: from [192.168.1.11] (host-212-149-186-30.kpylaajakaista.net [212.149.186.30]) by satakieli.dnainternet.net (Postfix) with ESMTP id 358CECA0D for ; Sat, 23 Dec 2006 20:59:20 +0200 (EET) Message-ID: <458D7C87.2090106@dnainternet.net> Date: Sat, 23 Dec 2006 20:59:19 +0200 From: Erik Udo User-Agent: Thunderbird 1.5.0.8 (X11/20061114) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <458D36E4.9000900@dnainternet.net> <458D67CC.1050102@dnainternet.net> In-Reply-To: <458D67CC.1050102@dnainternet.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: memory holes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Dec 2006 18:59:24 -0000 Ok... I got it solved by switching the memory modules of this computer to an another. Seemes like the motherboard-memory combination didn't work perfectly. It passed memtest afterwards, though i didn't run it for more than 5 minutes. Erik Udo wrote: > OK. I've tested OpenBSD and NetBSD. > > Both find 512MB of ram, but.. > NetBSD crashes after boot stage when it starts to load the kernel. > (thanks NetBSD team for not building the kernel image with debugging > symbols, but you did build it with DDB) > > OpenBSD finds 512MB of ram too, but... > it wont find my hard disk, even thought it has wd0 as a hard disk in dmesh. > > To add to my previous post, i tested with 128MB PC100 + 32MB PC100. Both > memory modules was found by FreeBSD and put to use. > > Which leads me to the conclusion: Why can't FreeBSD use PC133 memory > when OpenBSD can? Did someone forget to port drivers for memory modules? :P > > > Erik Udo wrote: >> I upgraded my hardware and software yesturday, and for some reason, >> FreeBSD only 'detects' 128MB of the memory, when the BIOS is clearly >> seeing 512MB. OpenBSD also finds 512MB of memory. >> >> So i added one 128MB ECC memory. There was one 128MB PC100 and 256MB >> PC133 memory before, and it worked fine on 6.2-PRERELASE. >> >> Now that i upgraded to 6.2-RC1, from 6.2-PRERELEASE and added the >> 128MB memory to the 384MB i had, the kernel started giving me this >> error on the first line of the kernel output: >> "Too many holes in the physical address space, giving up" >> >> Now, i searched google for anything, and found this earlier thread: >> http://www.mail-archive.com/freebsd-hardware@freebsd.org/msg01624.html >> >> I also found this: >> http://lists.freebsd.org/pipermail/freebsd-hackers/2005-October/013932.html >> >> >> Like the previous post says, the memory was found after the increased >> PHYSMAP_SIZE. I increased mine to 2*32, later 2*128. It didn't work. >> >> Also someone told me to add this line to the kernel config: >> options MAXMEM=524288 >> >> That didn't work either. >> >> I also tried to toggle all the bios settings on the computer, i even >> upgraded the bios. Nothing. >> >> Now i found out that OpenBSD sees 512MB of memory, so there must be >> some kind of trick to make FreeBSD recognize that memory too. >> >> Here is some output of my verbose boot: >> >> with 512MB: >> real memory = 134234112 (128 MB) >> Physical memory chunk(s): >> 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) >> 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) >> 0x0000000000c25000 - 0x0000000007d82fff, 118874112 bytes (29022 pages) >> avail memory = 121798656 (116 MB) >> >> Anyone have any ideas? >> >> Thanks, >> Erik >> _______________________________________________ >> freebsd-hardware@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >> To unsubscribe, send any mail to >> "freebsd-hardware-unsubscribe@freebsd.org" >> > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 23 20:48:24 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BB18F16A407 for ; Sat, 23 Dec 2006 20:48:24 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c58-107-94-118.belrs4.nsw.optusnet.com.au [58.107.94.118]) by mx1.freebsd.org (Postfix) with ESMTP id E858413C458 for ; Sat, 23 Dec 2006 20:48:23 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id kBNKRSAn015229; Sun, 24 Dec 2006 07:27:28 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id kBNKRSLI015228; Sun, 24 Dec 2006 07:27:28 +1100 (EST) (envelope-from peter) Date: Sun, 24 Dec 2006 07:27:28 +1100 From: Peter Jeremy To: Erik Udo Message-ID: <20061223202728.GF837@turion.vk2pj.dyndns.org> References: <458D36E4.9000900@dnainternet.net> <458D67CC.1050102@dnainternet.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MrRUTeZlqqNo1jQ9" Content-Disposition: inline In-Reply-To: <458D67CC.1050102@dnainternet.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-hardware@freebsd.org Subject: Re: memory holes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Dec 2006 20:48:24 -0000 --MrRUTeZlqqNo1jQ9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, 2006-Dec-23 19:30:52 +0200, Erik Udo wrote: >Both find 512MB of ram, but.. >NetBSD crashes after boot stage when it starts to load the kernel.=20 >(thanks NetBSD team for not building the kernel image with debugging=20 >symbols, but you did build it with DDB) > >OpenBSD finds 512MB of ram too, but... >it wont find my hard disk, even thought it has wd0 as a hard disk in dmesh. > >To add to my previous post, i tested with 128MB PC100 + 32MB PC100. Both= =20 >memory modules was found by FreeBSD and put to use. > >Which leads me to the conclusion: Why can't FreeBSD use PC133 memory=20 >when OpenBSD can? Did someone forget to port drivers for memory modules? :P Actually, crashing or misbehaving whist trying to boot suggests to me that neither OpenBSD nor NetBSD can use the extra memory they "find". Correctly configuring the memory controllers for the physical memory you have is the responsibility of the BIOS. It seems likely that either some of your RAM is bad (a 5 minute memtest may not detect this) and/or mixing different sizes and types of memory has confused the BIOS. There are a variety of different ways to work out how much memory is in your computer. It's quite possible that {Free,Net,Open}BSD are using different mechanisms and coming up with different amounts. --=20 Peter Jeremy --MrRUTeZlqqNo1jQ9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFjZEw/opHv/APuIcRAsBsAJ9BFDWpcl3e2DlxcTFC49DfE+j5zgCgv3w6 wNVx+j9HLo+YQotf0MwCUng= =fOuo -----END PGP SIGNATURE----- --MrRUTeZlqqNo1jQ9--