USB support + Supermicro IPMI KVM = no keyboard

Steve Were you ever able to solve this? we are experiencing the same problem. Thanks Jurgen -- --> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 ___ freeb

Re: Upgrade FreeBSD 7.1 to 7.2

Lowell Gilbert wrote: > Mikael Bak writes: > >> I would like to do a binary upgrade from 7.1 to 7.2. I've seen the >> instructions here: >> http://www.freebsd.org/releases/7.2R/announce.html >> Miroslav, Robert, Lowell, Thank you all for the useful information! The binary upgrade from 7.1 -> 7

Re: USB support + Supermicro IPMI KVM = no keyboard

Jurgen Weber wrote: Steve Were you ever able to solve this? we are experiencing the same problem. Can I ask you, what type of Supermicro server you have or what IPMI/KVM module? We have 6016TT-TF with onboard IPMI, and "virtual USB keyboard" doesn't work only on 7.2 installation CD/ISO, bu

Re: USB support + Supermicro IPMI KVM = no keyboard

Nope, we just compiled out USB support from the kernel. Regards Steve - Original Message - From: "Jurgen Weber" Steve Were you ever able to solve this? we are experiencing the same problem. This e.mail is private and confid

Re: USB support + Supermicro IPMI KVM = no keyboard

Our testing was on 7.0 at the time. - Original Message - From: "Miroslav Lachman" <000.f...@quip.cz> Jurgen Weber wrote: Steve Were you ever able to solve this? we are experiencing the same problem. Can I ask you, what type of Supermicro server you have or what IPMI/KVM module?

x11/nvidia-driver cannot obtain EDID under 8.0-BETA3/i386

Hi! Fresh install of 8.0-BETA2 upgraded to 8.0-BETA3 using source, x.org installed from fresh ports tree. It cannot read EDID from Samsung 959NF CRT monitor. The same time, it can read EDID under 7.2-STABLE just fine. I've tried older nvidia-driver-180.60 (downgrading port) and current port's vers

(no subject)

Subject r196566 broke to assign IPv6 address on bridge0 User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.7 Emacs/22.3 (i386-portbld-freebsd7.2) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 7.2-STABLE X-PGP-Key: http://www.imasy.or.jp/~um

Re: portmaster not ask for port deletion

Skip Ford wrote: > So, basically, portmaster stopped and asked for input because it thought I > might've forgotten that I installed an +IGNOREME file 10 minutes prior. > I'd prefer to not have tools that try to "think" about what I'm doing. > It should do what I say it should do, not what it think

Re: Upgrade FreeBSD 7.1 to 7.2

Mikael Bak writes: > Lowell Gilbert wrote: >> Mikael Bak writes: >> >>> I would like to do a binary upgrade from 7.1 to 7.2. I've seen the >>> instructions here: >>> http://www.freebsd.org/releases/7.2R/announce.html >>> > > Miroslav, Robert, Lowell, > > Thank you all for the useful information

Re: Upgrade FreeBSD 7.1 to 7.2

On 2009-08-28T09:58:58+0200, Mikael Bak wrote: > The reason why I didn't go to single user mode was that my /usr and /var > were not mounted in single user. I had only /. I wasn't sure how to deal > with that. If your filesystems are listed in /etc/fstab, then mount -a will mount the rest of them

Re: Upgrade FreeBSD 7.1 to 7.2

> From: Lowell Gilbert > Date: Fri, 28 Aug 2009 16:08:14 -0400 > Sender: owner-freebsd-sta...@freebsd.org > > Mikael Bak writes: > > > Lowell Gilbert wrote: > >> Mikael Bak writes: > >> > >>> I would like to do a binary upgrade from 7.1 to 7.2. I've seen the > >>> instructions here: > >>> htt

Re: portmaster not ask for port deletion

Doug Barton wrote: > Skip Ford wrote: > > > So, basically, portmaster stopped and asked for input because it thought I > > might've forgotten that I installed an +IGNOREME file 10 minutes prior. > > I'd prefer to not have tools that try to "think" about what I'm doing. > > It should do what I say

Re: livelocks and deadlocks on 8.0BETA2

On Fri, 21 Aug 2009, Ed Jobs wrote: > On Friday 21 August 2009 02:56, Kevin Oberman wrote: > > I have a quad-core system that I updated to 8.0 about 2 weeks > ago. It > > ran fine until yesterday when I used the PATA/ATAPI DVD drive to > read a > > disk. Then the fun began. I saw two totally dif

[releng_8 tinderbox] failure on i386/pc98

TB --- 2009-08-28 21:20:38 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-08-28 21:20:38 - starting RELENG_8 tinderbox run for i386/pc98 TB --- 2009-08-28 21:20:38 - cleaning the object tree TB --- 2009-08-28 21:21:34 - cvsupping the source tree TB --- 2009-08-28 21:21:34 - /usr/b

[releng_8 tinderbox] failure on i386/i386

TB --- 2009-08-28 21:20:38 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-08-28 21:20:38 - starting RELENG_8 tinderbox run for i386/i386 TB --- 2009-08-28 21:20:38 - cleaning the object tree TB --- 2009-08-28 21:21:34 - cvsupping the source tree TB --- 2009-08-28 21:21:34 - /usr/b

[releng_8 tinderbox] failure on ia64/ia64

TB --- 2009-08-28 21:20:38 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-08-28 21:20:38 - starting RELENG_8 tinderbox run for ia64/ia64 TB --- 2009-08-28 21:20:38 - cleaning the object tree TB --- 2009-08-28 21:21:37 - cvsupping the source tree TB --- 2009-08-28 21:21:38 - /usr/b

[releng_8 tinderbox] failure on amd64/amd64

TB --- 2009-08-28 21:20:38 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-08-28 21:20:38 - starting RELENG_8 tinderbox run for amd64/amd64 TB --- 2009-08-28 21:20:38 - cleaning the object tree TB --- 2009-08-28 21:22:07 - cvsupping the source tree TB --- 2009-08-28 21:22:07 - /usr