On Fri, 19 Nov 2010, John Baldwin wrote:
On Thursday, November 18, 2010 10:14:44 pm Ian Smith wrote:
On Thu, 18 Nov 2010, John Baldwin wrote:
On Thursday, November 18, 2010 4:07:27 pm Andrew Reilly wrote:
Hi John,
On 18/11/2010, at 23:59 , John Baldwin wrote:
on 19/11/2010 05:14 Ian Smith said the following:
On Thu, 18 Nov 2010, John Baldwin wrote:
On Thursday, November 18, 2010 4:07:27 pm Andrew Reilly wrote:
Hi John,
On 18/11/2010, at 23:59 , John Baldwin wrote:
You used devinfo -v, so it shows the devices that exist even
On Thursday, November 18, 2010 10:14:44 pm Ian Smith wrote:
On Thu, 18 Nov 2010, John Baldwin wrote:
On Thursday, November 18, 2010 4:07:27 pm Andrew Reilly wrote:
Hi John,
On 18/11/2010, at 23:59 , John Baldwin wrote:
You used devinfo -v, so it shows the devices that
On Wednesday, November 17, 2010 7:46:38 pm Alexandre Sunny Kovalenko wrote:
On Thu, 2010-11-18 at 11:13 +1100, Andrew Reilly wrote:
Hi Alexandre,
On Wed, Nov 17, 2010 at 06:56:53PM -0500, Alexandre Sunny Kovalenko wrote:
On Thu, 2010-11-18 at 10:40 +1100, Andrew Reilly wrote:
Hi John,
On 18/11/2010, at 23:59 , John Baldwin wrote:
You used devinfo -v, so it shows the devices that exist even if they failed
to attach. Try just using 'devinfo' and seeing if est1 still shows up.
OK, you're right: running without -v shows only est0:
nexus0
apic0
ram0
acpi0
On Tue, Nov 16, 2010 at 07:41:02PM -0500, Jung-uk Kim wrote:
On Tuesday 16 November 2010 06:55 pm, Andrew Reilly wrote:
On Tue, Nov 16, 2010 at 06:36:16PM -0500, Jung-uk Kim wrote:
You may try sysctl hw.acpi.handle_reboot=1. If it works, just
add it in /etc/sysctl.conf.
FYI, it is
On Thursday, November 18, 2010 4:07:27 pm Andrew Reilly wrote:
Hi John,
On 18/11/2010, at 23:59 , John Baldwin wrote:
You used devinfo -v, so it shows the devices that exist even if they failed
to attach. Try just using 'devinfo' and seeing if est1 still shows up.
OK, you're right:
On Thu, 18 Nov 2010, John Baldwin wrote:
On Thursday, November 18, 2010 4:07:27 pm Andrew Reilly wrote:
Hi John,
On 18/11/2010, at 23:59 , John Baldwin wrote:
You used devinfo -v, so it shows the devices that exist even if they
failed
to attach. Try just using
On Wed, Nov 17, 2010 at 01:42:15PM +1100, Ian Smith wrote:
I'm used to seeing est either attach to both CPUs, or fail to attach to
either CPU. Here it's attached to cpu0, but not to cpu1. Is that odd?
It seems odd, but since I don't know what est does (there isn't
a man page), I'm not sure
On Thu, 2010-11-18 at 10:06 +1100, Andrew Reilly wrote:
On Wed, Nov 17, 2010 at 01:42:15PM +1100, Ian Smith wrote:
I'm used to seeing est either attach to both CPUs, or fail to attach to
either CPU. Here it's attached to cpu0, but not to cpu1. Is that odd?
It seems odd, but since I
On Wed, Nov 17, 2010 at 06:26:56PM -0500, Alexandre Sunny Kovalenko wrote:
On Thu, 2010-11-18 at 10:06 +1100, Andrew Reilly wrote:
On Wed, Nov 17, 2010 at 01:42:15PM +1100, Ian Smith wrote:
I'm used to seeing est either attach to both CPUs, or fail to attach to
either CPU. Here it's
On Thu, 2010-11-18 at 10:40 +1100, Andrew Reilly wrote:
On Wed, Nov 17, 2010 at 06:26:56PM -0500, Alexandre Sunny Kovalenko wrote:
On Thu, 2010-11-18 at 10:06 +1100, Andrew Reilly wrote:
On Wed, Nov 17, 2010 at 01:42:15PM +1100, Ian Smith wrote:
I'm used to seeing est either attach to
Hi Alexandre,
On Wed, Nov 17, 2010 at 06:56:53PM -0500, Alexandre Sunny Kovalenko wrote:
On Thu, 2010-11-18 at 10:40 +1100, Andrew Reilly wrote:
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
On 15-11-2010 05:55, Andrew Reilly wrote:
Oh: the other thing about this system: I can't warm-start
it, have to power down and then manually hit the power-on
button. Attempting to reboot leaves the console sitting at
something like Stopping other CPUs forever.
Andrew,
No solution for you
On Thu, 2010-11-18 at 11:13 +1100, Andrew Reilly wrote:
Hi Alexandre,
On Wed, Nov 17, 2010 at 06:56:53PM -0500, Alexandre Sunny Kovalenko wrote:
On Thu, 2010-11-18 at 10:40 +1100, Andrew Reilly wrote:
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location:
On Wed, 17 Nov 2010, Alexandre Sunny Kovalenko wrote:
On Thu, 2010-11-18 at 11:13 +1100, Andrew Reilly wrote:
Hi Alexandre,
On Wed, Nov 17, 2010 at 06:56:53PM -0500, Alexandre Sunny Kovalenko wrote:
On Thu, 2010-11-18 at 10:40 +1100, Andrew Reilly wrote:
dev.cpu.0.%desc: ACPI
On Sunday 14 November 2010 11:55 pm, Andrew Reilly wrote:
Oh: the other thing about this system: I can't warm-start
it, have to power down and then manually hit the power-on
button. Attempting to reboot leaves the console sitting at
something like Stopping other CPUs forever. I assume that
On Tue, Nov 16, 2010 at 06:36:16PM -0500, Jung-uk Kim wrote:
On Sunday 14 November 2010 11:55 pm, Andrew Reilly wrote:
Oh: the other thing about this system: I can't warm-start
it, have to power down and then manually hit the power-on
button. Attempting to reboot leaves the console sitting
On Tuesday 16 November 2010 06:55 pm, Andrew Reilly wrote:
On Tue, Nov 16, 2010 at 06:36:16PM -0500, Jung-uk Kim wrote:
On Sunday 14 November 2010 11:55 pm, Andrew Reilly wrote:
Oh: the other thing about this system: I can't warm-start
it, have to power down and then manually hit the
On Mon, 15 Nov 2010, Andrew Reilly wrote:
Hi there,
[..]
Oh: the other thing about this system: I can't warm-start
it, have to power down and then manually hit the power-on
button. Attempting to reboot leaves the console sitting at
something like Stopping other CPUs forever. I assume
Hi there,
I've replaced my old desktop with a laptop and a server, which
is mostly working great. Naturally, the server is running
FreeBSD-stable. It's built on an intel i3 MiniITX motherboard
that has lots of SATA sockets, a respectable number of USB
sockets, gigabit ethernet, eSATA, DVI, ...
on 15/11/2010 06:55 Andrew Reilly said the following:
Hi there,
I've replaced my old desktop with a laptop and a server, which
is mostly working great. Naturally, the server is running
FreeBSD-stable. It's built on an intel i3 MiniITX motherboard
that has lots of SATA sockets, a
It's been suggested that I make the output of dmidecode (from
ports/sysutils), pciconf -lv and dmesg.boot available, to help
answer my previosu question. Since all of that output is
relatively small and I don't really have a good web site to put
it, I'll just include it, below. Hope this helps!
On Mon, Nov 15, 2010 at 10:52:10AM +0200, Andriy Gapon wrote:
If I find a USB-to-RS232 dongle, will the console mechanism be
able to find it? I worry that only legacy-16550-ish serial
ports need apply.
Any other possibilities or common practices?
Is there a firewire port?
I'm
Hi,
Your board has a serial port:
[stuff deleted]
/var/run/dmesg.boot:
Copyright (c) 1992-2010 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
Bob Bishop wrote:
Hi,
Your board has a serial port:
[...more stuff deleted...]
uart0:16550 or compatible port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: [FILTER]
[etc]
The diagram on page 12 of
http://downloadmirror.intel.com/18702/eng/DH57JG_ProductGuide03_English.pdf
shows the
On Mon, Nov 15, 2010 at 12:03:38PM +, Bob Bishop wrote:
Your board has a serial port:
[...more stuff deleted...]
uart0: 16550 or compatible port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: [FILTER]
[etc]
Ha! I'd not noticed that. Wasn't looking for it, I guess.
The diagram on
27 matches
Mail list logo
