Hello.
Yesss!!! At last we found the source of problem!
The problem with displaying messages from rc-scripts caused
by option "dcons_crom" in kernel (dumb console on Firewire).
When it is enabled on PC with FireWire port, all output
goes there instead of system console. Disabling this
option so
Do you have a /boot.config file? If so, delete it. Also, try enabling
console logging in /etc/syslog.conf, and see if you get anything there.
hth,
Doug
--
This .signature sanitized for your protection
___
freebsd-stable@freebsd.org mailing list
Hello.
> > The problem is much more complex, I suppose. Not only
> > rc-scripts messages aren't display, there are no messages at
> > all, from any scripts and programs, started between kernel
> > boot and login prompt.
>
> Strange.
>
> - What does ls -la /dev/console show?
0 crw--- 1 root
On Wed, May 17, 2006, Sergei Mozhaisky wrote:
> This does not help :( There is no output at all, commands
> aren't display too.
Maybe 'dmesg -a' will give you a hint what's going on.
-cs
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd
On Wed, May 17, 2006 at 06:00:50PM +0300, Sergei Mozhaisky wrote:
> Hello.
>
> > > This bug was seen not on all computers. Currently
> > > I found 3 PC with this problem (two on AMD platform,
> > > one on Intel). Video adapters on them are also
> > > different.
> > >
> > > Any suggestions?
> >
>
The problem is much more complex, I suppose. Not only
rc-scripts messages aren't display, there are no messages at
all, from any scripts and programs, started between kernel
boot and login prompt.
Strange.
- What does ls -la /dev/console show?
- Does a single user boot (boot -s) drop you to a '
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sergei Mozhaisky
Sent: Wednesday, May 17, 2006 5:57 AM
To: freebsd-stable@freebsd.org
Subject: Messages from rc-scripts are not displayed at all
Hello everyone.
Got a problem on FreeBSD 6.1.
After kernel
Hello.
> > This bug was seen not on all computers. Currently
> > I found 3 PC with this problem (two on AMD platform,
> > one on Intel). Video adapters on them are also
> > different.
> >
> > Any suggestions?
>
> Its really unlikely to be a video adapter problem. You
> could debug this by adding
This bug was seen not on all computers. Currently
I found 3 PC with this problem (two on AMD platform,
one on Intel). Video adapters on them are also
different.
Any suggestions?
Its really unlikely to be a video adapter problem. You
could debug this by adding a 'set -x' to the beginning
of /et
