Jeremy Chadwick wrote:
> Is there a PS/2 keyboard hooked up to this machine when you're
> attempting to get serial console output?
Kind of. It's connected to a local KVM switch.
> If so, I'm not too surprised it doesn't work (re: -P flag).
If -P is not supposed to activate the serial console
On Mon, Sep 13, 2010 at 09:21:21AM +0200, Oliver Fromme wrote:
> Jeremy Chadwick wrote:
> > Is there a PS/2 keyboard hooked up to this machine when you're
> > attempting to get serial console output?
>
> Kind of. It's connected to a local KVM switch.
Does the KVM switch provide power to a PS/2
per...@pluto.rain.com wrote:
> [...]
> Beyond that, I suspect
> that dropping an HBA or three would have been far less burdensome
> on users of the hardware in question than dropping ISDN is on its
> users. One can always replace a no-longer-supported HBA with a
> supported one, or (worst ca
Am 12.09.2010 um 17:26 schrieb Oliver Fromme:
> I cannot even su(1) to root because it tries to print
> a message to the console, so it hangs, too. For the same
> reason I can't use shutdown(8) either. :-(
>
> This is what a hanging su(1) command looks like in ps -alxww:
> UID PID PPID CPU
Hello, Freebsd-stable.
You wrote 13 сентября 2010 г., 00:14:31:
> I have VirtualBox-based FreeBSD 8.1 installation (32 bit, VirtualBox
> 3.2.8, WinXP/x64 host, but I thinks that host config is irrelevant).
Sorry for noise, it seems to be VirtualBox instability: I've
re-createddis
I can confirm there is much weirdness with the uart on 8-STABLE.
I'm using FBSD in several virtual machines on Parallels Desktop.
It is possible to set the serial port on the VM to output to a file on the host
OS
I try something like 'cat file > /dev/cuad0 on FBSD 7 and 8. This works
on 7 b
Am 13.09.2010 um 13:04 schrieb David Evans:
> I can confirm there is much weirdness with the uart on 8-STABLE.
OTOH, I have real hardware where things are working just fine:
$ grep uart /var/run/dmesg.boot
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: [FILTER]
u
Jeremy Chadwick wrote:
> On Mon, Sep 13, 2010 at 09:21:21AM +0200, Oliver Fromme wrote:
> > Jeremy Chadwick wrote:
> > > Is there a PS/2 keyboard hooked up to this machine when you're
> > > attempting to get serial console output?
> >
> > Kind of. It's connected to a local KVM switch.
>
On 13/09/2010 08:41, Max Khon wrote:
George,
On Sat, Sep 11, 2010 at 12:12 AM, George Mamalakis
mailto:mama...@eng.auth.gr>> wrote:
On 10/09/2010 19:05, pluknet wrote:
On 10 September 2010 17:32, George
Mamalakismailto:mama...@eng.auth.gr>>
wrote:
TB --- 2010-09-13 12:31:52 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-13 12:31:52 - starting RELENG_8_0 tinderbox run for ia64/ia64
TB --- 2010-09-13 12:31:52 - cleaning the object tree
TB --- 2010-09-13 12:32:38 - cvsupping the source tree
TB --- 2010-09-13 12:32:38 - /usr
On Fri 2010-09-10 (10:43), Jack Vogel wrote:
> No, not the add-on adapter, i have no trouble finding those, what I want to
> know about is the details about the system that has em0 LOM, only
> way to check on that is to have the whole enchilada :)
Ah right. These are snippets from dmidecode, is t
TB --- 2010-09-13 14:21:57 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-13 14:21:57 - starting RELENG_8_1 tinderbox run for arm/arm
TB --- 2010-09-13 14:21:57 - cleaning the object tree
TB --- 2010-09-13 14:22:19 - cvsupping the source tree
TB --- 2010-09-13 14:22:19 - /usr/b
Rick Macklem wrote:
> Btw, if anyone who didn't see the posting on freebsd-fs and would
> like to run a quick test, it would be appreciated.
> Bascially do both kinds of mount using a FreeBSD8.1 or later client
> and then read a greater than 100Mbyte file with dd.
>
> # mount -t nfs -o nfsv3
On Monday, September 13, 2010 8:49:48 am Oliver Fromme wrote:
> Jeremy Chadwick wrote:
> > On Mon, Sep 13, 2010 at 09:21:21AM +0200, Oliver Fromme wrote:
> > > Jeremy Chadwick wrote:
> > > > Is there a PS/2 keyboard hooked up to this machine when you're
> > > > attempting to get serial console
>
> Ok ...
>
> NFS server:
> - FreeBSD 8.1-PRERELEASE-20100620 i386
> - intel Atom 330 (1.6 GHz dual-core with HT --> 4-way SMP)
> - 4 GB RAM
> - re0:
>
> NFS client:
> - FreeBSD 8.1-STABLE-20100908 i386
> - AMD Phenom II X6 1055T (2.8 GHz + "Turbo Core", six-core)
> - 4 GB RAM
> - re0:
>
> T
On Mon, Sep 13, 2010 at 11:15:34AM -0400, Rick Macklem wrote:
> >
> > instead of from the local cache. I also made sure that
> > the file was in the cache on the server, so the server's
> > disk speed is irrelevant.
> >
> > So, nfs is roughly twice as fast as newnfs, indeed.
Hmm, I have the s
John Baldwin wrote:
> On Monday, September 13, 2010 8:49:48 am Oliver Fromme wrote:
> > Now I get your point ... Yes, -P does probe the keyboard
> > first. That's probably why I see the boot0/boot2 on the
> > VGA console, not on the serial port. As far as I know,
> > /boot.config is read by
On Monday, September 13, 2010 11:55:27 am Oliver Fromme wrote:
> John Baldwin wrote:
> > On Monday, September 13, 2010 8:49:48 am Oliver Fromme wrote:
> > > Now I get your point ... Yes, -P does probe the keyboard
> > > first. That's probably why I see the boot0/boot2 on the
> > > VGA console
--On September 12, 2010 11:44:40 -0400 Rick Macklem
wrote:
On Wed, Sep 01, 2010 at 11:46:30AM -0400, Rick Macklem wrote:
My results seems to confirm a factor of two (or 1.5) but it's stable:
new nfs nfsv4
369792 bytes transferred in 71.932692 secs (55607119 bytes/sec)
369792 b
John Baldwin wrote:
> On Monday, September 13, 2010 11:55:27 am Oliver Fromme wrote:
> > I think the boot.config stuff might be a red herring.
> > The console breaks (i.e. freezes) as soon as I try to run
> > a getty process on it -- That seems to indicate that getty
> > does *something* to t
On Mon, Sep 13, 2010 at 06:59:58PM +0200, Oliver Fromme wrote:
>
> John Baldwin wrote:
> > On Monday, September 13, 2010 11:55:27 am Oliver Fromme wrote:
> > > I think the boot.config stuff might be a red herring.
> > > The console breaks (i.e. freezes) as soon as I try to run
> > > a getty pr
Hello, I'm hoping somebody can shed some light on this.
One of my machines has a Radeon X1550 graphics card. When first
installed (then as either 7.1 or 7.1 prerelease), the radeonhd driver
hung the machine hard, screen went blank, numlock and capslock
didn't work, no network (so no ssh) and I co
Just replying to a random message in this thread.
Maybe we should just implement /dev/console in such a way that it can
never get stuck on dcd. I've seen this break too many times.
Below is an untested patch. Anyone willing to test it for me?
As Jeremy did point out, FreeBSD's TTY/serial/etc cod
Ed Schouten wrote:
> Just replying to a random message in this thread.
>
> Maybe we should just implement /dev/console in such a way that it can
> never get stuck on dcd. I've seen this break too many times.
>
> Below is an untested patch. Anyone willing to test it for me?
Thank you! I w
* Oliver Fromme wrote:
> @ Jeremy: Thank you for the detailed response! I will
> make sure to bring a multimeter with me and check the
> pin connections on my nullmodem cable. I'm still curious
> why this cable worked with 7.x with the same configuration.
I seem to remember some of the drivers
Eivind E wrote:
> One of my machines has a Radeon X1550 graphics card. When first
> installed (then as either 7.1 or 7.1 prerelease), the radeonhd driver
> hung the machine hard, screen went blank, numlock and capslock
> didn't work, no network (so no ssh) and I couldn't do much but
> hard re
On Mon, Sep 13, 2010 at 10:16:48PM +0200, Oliver Fromme wrote:
> Eivind E wrote:
> > One of my machines has a Radeon X1550 graphics card. When first
> > installed (then as either 7.1 or 7.1 prerelease), the radeonhd driver
> > hung the machine hard, screen went blank, numlock and capslock
> >
On Mon, 13 Sep 2010, Oliver Fromme wrote:
Eivind E wrote:
> One of my machines has a Radeon X1550 graphics card. When first
> installed (then as either 7.1 or 7.1 prerelease), the radeonhd driver
> hung the machine hard, screen went blank, numlock and capslock
> didn't work, no network (so no s
We don't deal with desktop systems that much in my group, it was pointed out
by a coworker that the BIOS has settings that could disable MSI, please
check
out how yours is set.
Jack
On Mon, Sep 13, 2010 at 7:42 AM, Gareth de Vaux wrote:
> On Fri 2010-09-10 (10:43), Jack Vogel wrote:
> > No, no
On Mon, 13 Sep 2010, Roland Smith wrote:
On Mon, Sep 13, 2010 at 10:16:48PM +0200, Oliver Fromme wrote:
Eivind E wrote:
> One of my machines has a Radeon X1550 graphics card. When first
> installed (then as either 7.1 or 7.1 prerelease), the radeonhd driver
> hung the machine hard, screen went
On 09/13/10 18:04, Eivind E wrote:
Tried to substitute the driver with ati and loading radeon.ko (which
automatically loaded drm.ko) and had the same results as the plain
radeon driver. X starts up once in a while, but the screen goes
to about half of normal brightness and the view is moved down
On Tue, Sep 14, 2010 at 12:04:16AM +0200, Eivind E wrote:
> On Mon, 13 Sep 2010, Roland Smith wrote:
> >> Did you try the normal radeon driver (not radeonhd)?
> >> It supports the RV515 chip used by the X1550, too.
> >
> > Keep in mind that normal radeon driver is called x11-drivers/xf86-video-ati
On Mon, Sep 13, 2010 at 08:44:02PM +0200, Ed Schouten wrote:
> Maybe we should just implement /dev/console in such a way that it can
> never get stuck on dcd. I've seen this break too many times.
>
> Below is an untested patch. Anyone willing to test it for me?
I'll test this out on our RELENG_8
33 matches
Mail list logo
