installed 2.4.1 inside a VM and would like to run it headless, therefore
I did the usual to get the boot output on COM1, but this is not quite
working.
I put -Dh in /boot.config and removed the Booteasy manager. Upon boot I
see (on vidconsole!)
Try using /boot/boot.config;
boot.config needs to
loader 1.00 ... the usual
...
So I set console=comconsole in /boot/loader.conf and at least the loader
shows up on my serial console, but what about earlier boot stages?
Then I tried installing boot0sio, which also fails
dragonfly# boot0cfg -b /boot/boot0sio ad0
boot0cfg: /dev/ad0: unknown
On Tue, 16 Dec 2008, walt wrote:
...
sigh The kvm folks just committed a (relatively) huge update from the qemu
folks, and I'm running it now. As of this particular moment, today's kvm
seems
to be behaving much better than yesterday's kvm.
Great news. Yesterday's update from qemu
walt schrieb:
Great news. Yesterday's update from qemu definitely fixed the problem--even
the dragonfly and freebsd installers are back to normal.
Thanks much for your help.
OK, all's well that ends well.
Sascha
--
http://yoyodyne.ath.cx
walt schrieb:
Can you try one more thing? From qemu, do 'kldload vesa', choose some valid
mode number from the output of 'vidcontrol -i mode' (15, 16 or 32 bit will
do), and set a VESA mode with 'vidcontrol MODE_number'. Tell me if the
problem persists with the new resolution.
Hey, that works!
Sascha Wildner wrote:
walt schrieb:
On Fri, 12 Dec 2008, Sascha Wildner wrote:
walt schrieb:
I've installed dfly using the kvm/qemu emulator and I'm seeing
strange corruption of the console screen at times.
Hm, you can change to 80x50 with 'vidcontrol -f 8x8 iso-8x8.fnt 80x50'.
After
On Mon, Dec 15, 2008 at 10:23:54AM -0800, walt wrote:
Sascha Wildner wrote:
walt schrieb:
On Fri, 12 Dec 2008, Sascha Wildner wrote:
walt schrieb:
I've installed dfly using the kvm/qemu emulator and I'm seeing
strange corruption of the console screen at times.
Hm, you can change
walt schrieb:
Also, can you recompile with
options VGA_DEBUG=2
options FB_DEBUG=2
in your kernel config and post or mail me a verbose boot message?
I put the dmesg in my leaf account: leaf.dragonflybsd.org/~wa1ter
Thanks. However, it doesn't look unusual at the first sight.
Can you try
I've installed dfly using the kvm/qemu emulator and I'm seeing
strange corruption of the console screen at times.
Some lines of text will have every other character blacked out,
and some lines display perfectly. Does this sound like some sort
of confusion between ascii and utf-8, perhaps
:I've installed dfly using the kvm/qemu emulator and I'm seeing
:strange corruption of the console screen at times.
:
:Some lines of text will have every other character blacked out,
:and some lines display perfectly. Does this sound like some sort
:of confusion between ascii and utf-8, perhaps
walt schrieb:
I've installed dfly using the kvm/qemu emulator and I'm seeing
strange corruption of the console screen at times.
Does it happen randomly or when you do some specific thing? Did you
change the mode using vidcontrol(8) or does it happen with plain 80x25?
Some lines of text
On Fri, Dec 12, 2008 at 08:59:30PM +0100, Sascha Wildner wrote:
walt schrieb:
I've installed dfly using the kvm/qemu emulator and I'm seeing
strange corruption of the console screen at times.
Does it happen randomly or when you do some specific thing? Did you
change the mode using
On Fri, 12 Dec 2008, Sascha Wildner wrote:
walt schrieb:
I've installed dfly using the kvm/qemu emulator and I'm seeing
strange corruption of the console screen at times.
Does it happen randomly or when you do some specific thing? Did you change the
mode using vidcontrol(8) or does
walt schrieb:
On Fri, 12 Dec 2008, Sascha Wildner wrote:
walt schrieb:
I've installed dfly using the kvm/qemu emulator and I'm seeing
strange corruption of the console screen at times.
Does it happen randomly or when you do some specific thing? Did you change the
mode using vidcontrol(8
Hallo - a question from a person pretty new to DragonFlyBSD:
As I can see, DragonFlyBSD uses just cons25 terminal, taken from FreeBSD
most probably. I would to ask: is there support for smacs/rmacs strings
planned? It's needed for full internationalization of text-console, without
a loss
:Hallo - a question from a person pretty new to DragonFlyBSD:
:
:As I can see, DragonFlyBSD uses just cons25 terminal, taken from FreeBSD
:most probably. I would to ask: is there support for smacs/rmacs strings
:planned? It's needed for full internationalization of text-console, without
:a loss
needed for full internationalization of text-console, without
:a loss of semigraphics.
Not that I know of.
What a pity - it would be nice to keep both national characters and
semigraphics in text mode.
:Uh, I forgot - another one: I read, that DragonFlyBSD has two releases
:yearly
Zbigniew Baniewski wrote:
:As I can see, DragonFlyBSD uses just cons25 terminal, taken from FreeBSD
:most probably. I would to ask: is there support for smacs/rmacs strings
:planned? It's needed for full internationalization of text-console, without
:a loss of semigraphics.
Not that I know
On 2008-07-27 20:08, Zbigniew Baniewski wrote:
On Sun, Jul 27, 2008 at 10:54:00AM -0700, Matthew Dillon wrote:
:Uh, I forgot - another one: I read, that DragonFlyBSD has two releases
:yearly. Wouldn't be reasonable to switch to rolling release model then? It
:could mean less work for both the
knowledge about terminals. Was just wondering, if anything planned in that
area.
probably this would require a graphics console, however.
No, not at all - smacs/rmacs strings are kind of switch, which allows to
utilize both charsets of standard VGA card at one time. Such way one can
have 512
On Sun, Jul 27, 2008 at 09:57:55PM +0200, Erik Wikström wrote:
Yes, in a way. [..]
Either one can choose to use the absolute latest code in HEAD, or one
can go the safe route and follow the changes to a release branch. A
third alternative is to follow the Preview-tag, which is somewhere
On Tue, 05 Jun 2007 13:04:26 -0700, Matthew Dillon wrote:
I think the last time I used screen was 20 years ago. I just leave all my
xterms open.
I stop using screen when I got my VAXstation II/GPX running ULTRIX. :-)
Adios emacs!
But I don't like sitting in the machine room in the basement,
I think the last time I used screen was 20 years ago. I just leave
all my xterms open. Sometimes I have upwards of 30 windows open across
four virtual screens in X. When people were describing the NATA bugs
I had an xterm open in an unsaved vi for over a week with all my notes
Matthew Dillon wrote:
I think the last time I used screen was 20 years ago. I just leave
all my xterms open. Sometimes I have upwards of 30 windows open across
four virtual screens in X. When people were describing the NATA bugs
I had an xterm open in an unsaved vi for over a
I will note one thing on remote sessions... if you are running through
NAT (network address translation), which is a very typical function of
today's cable modems, the NAT translation will often timeout if the
link stays idle too long. This will cause the link to die when you
I never remember to launch screen or dtach before I start some long-
running job. Wouldn't it be handy to be able to
- detach
- attach
- lock
- dup
- log
- snoop
- share
any tty, any time? Or is there already an elegant way of doing it I
haven't heard of?
It's also be handy to be able to
On 6/4/07, Simon 'corecode' Schubert [EMAIL PROTECTED] wrote:
how about this: use screen as your login shell
That works until you accidently ssh in and are having to hit ctrl-a,
a, a, d in order to log out -- and the number of ctrl-a and a keys
just gets longer and longer the more boxes you
Eric wrote:
I've installed Dragonfly on a Dell Optiplex with a normal old fashion box monitor with no problem. However, when I tried running Dragonfly on a Dimension with a flat panel FP153 monitor, the console screen turns a pale green right after booting. I've had similar problems
When exactly is right after booting?
After the countdown ends after the splash screen with the dragonfly. Before
that everything is black and white and looks good. Then things get ugly
(unless you like lime green!).
--
Eric [EMAIL PROTECTED]
On Thu, 3 May 2007 19:53:47 -0700 (PDT)
Matthew Dillon [EMAIL PROTECTED] wrote:
:The green tint goes away after I start X, and when I close X and go back
:into console, the console is the normal black and white. Its not a
:hardware issue, since the problem doesnt replicate in other BSD's
Eric wrote:
On Thu, 3 May 2007 19:53:47 -0700 (PDT)
Matthew Dillon [EMAIL PROTECTED] wrote:
:The green tint goes away after I start X, and when I close X and go back
:into console, the console is the normal black and white. Its not a
:hardware issue, since the problem doesnt replicate
Disregard, just read the man page. Figured it out.
On Fri, 4 May 2007, Eric wrote:
On Thu, 3 May 2007 19:53:47 -0700 (PDT)
Matthew Dillon [EMAIL PROTECTED] wrote:
:The green tint goes away after I start X, and when I close X and go back
:into console, the console is the normal black
Eric wrote:
I've installed Dragonfly on a Dell Optiplex with a normal old fashion box monitor with no problem. However, when I tried running Dragonfly on a Dimension with a flat panel FP153 monitor, the console screen turns a pale green right after booting. I've had similar problems
Is there a way to set vidcontrol during start-up? I played with it
using VMWare but after rebooting it goes back to the old video mode.
If the same happens with a regular hard drive install I don't think it
will solve the issue.
Maybe /etc/rc.d/syscons will help.
And see the rc.conf(5)
I've installed Dragonfly on a Dell Optiplex with a normal old fashion box
monitor with no problem. However, when I tried running Dragonfly on a
Dimension with a flat panel FP153 monitor, the console screen turns a pale
green right after booting. I've had similar problems with FreeBSD, but can
On Thu, May 3, 2007 4:33 pm, Eric wrote:
I've installed Dragonfly on a Dell Optiplex with a normal old fashion box
monitor with no problem. However, when I tried running Dragonfly on a
Dimension with a flat panel FP153 monitor, the console screen turns a pale
green right after booting. I've
On Thu, 3 May 2007, Justin C. Sherrill wrote:
On Thu, May 3, 2007 4:33 pm, Eric wrote:
I've installed Dragonfly on a Dell Optiplex with a normal old fashion box
monitor with no problem. However, when I tried running Dragonfly on a
Dimension with a flat panel FP153 monitor, the console
:The green tint goes away after I start X, and when I close X and go back
:into console, the console is the normal black and white. Its not a
:hardware issue, since the problem doesnt replicate in other BSD's (other
:than Free) or in Slackware or DOS.
That is really odd. Well, we do
Thomas Schlesinger pravi:
Hi,
I get sometimes the console message sched_ithd: stray interrupt 7 on my
notebook with SMP kernel.
What does this message mean?
you have LPT disabled in Bios, right?
Tomaž
Hi,
I get sometimes the console message sched_ithd: stray interrupt 7 on my
notebook with SMP kernel.
What does this message mean?
Thomas
Hi everyone,
I've always been a little curious about the way the typical unix
console works. Why is it that applications must wait for text to be
displayed on the console before continuing operation? Shouldn't these
messages merely enter into a queue to be displayed whenever the system
can get
Ben Cadieux wrote:
Hi everyone,
I've always been a little curious about the way the typical unix
console works. Why is it that applications must wait for text to be
displayed on the console before continuing operation? Shouldn't these
messages merely enter into a queue to be displayed
Nigel Weeks wrote:
I was reading through FBSD6's /usr/src/sys/dev/syscons to find out more
about libVGL programming, when I noticed some code based on DF code.
Does anyone know of examples of code using these syscons graphics libraries?
(Want to have a shot at porting Qtopia (was QT-embedded)
to look at it again.
It does look big - 1.3MB patch to the 5.4 sources...
If I had unlimited time I'd like to move most of syscons into
userland
(leave only a dumb emergency text console in the kernel for
ddb and so
on). Then we could properly care about UTF8 for syscons,
implement small
On Thu, March 2, 2006 7:12 pm, Nigel Weeks wrote:
and I like the look of Mac OS X(forgive me), and it'd be nice to
have a nice gui-based distro of a BSD...
I completely agree with you on this - the ability to render graphics on
boot, without having to deal with X11 configuration (immediately)
Op maandag 27 februari 2006 16:28, schreef Matthew Dillon:
:Ok, ive managed to get the console to 1024x768, ive tried 1280x1024 too
:because thats the native resolution for my LCD display, but for some
:reason the top and the right side are off the screen. Is there anything I
:can do about
If you want to use framebuffer in console, you'd better use special
set of fonts, for example, terminus-fonts because of it's dearness...
ps. Don't forget to use ter-langheightf.fnt as symbol 'f' means
that you are recommended to use this font with framebuffer...
pps. Sorry for my English
If the LCD screen has an auto-adjust feature, hit it and see if it
realigns the edges.
Be sure to set a different background border color so the auto-adjust
picks up on what the real screen edges are. :)
My LCD has this feature, but its not working for some reason in the
console
On 26.02.2006, at 17:06, [EMAIL PROTECTED] wrote:
Does DF have framebuffer support? I cant stand looking at 1cm large
letters in the console. How do i go about setting it up?
man vidcontrol
--
Serve - BSD +++ RENT this banner advert +++ASCII Ribbon /\
Work - Mac +++ space
How?
--
#include std/disclaimer.h
#define POWERED_BY http://www.DragonFlyBSD.org/;
50 matches
Mail list logo
