6.1-RELEASE disk hangs after loading kernel on sparc64

I've downloaded 6.1-RELEASE-sparc64-disc1.iso and try to boot. loader boots kernel and hangs on message: jumping to kernel entry at 0x... What can I do? PS. It's sun 480 with 4 CPU. I have no complete info on the configuration. -- Dixi. Sem. ___

Re: Messages from rc-scripts are not displayed at all

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

Re: 6.1-RELEASE disk hangs after loading kernel on sparc64

On Mon, 2006-06-19 at 12:08 +0400, Sergey Matveychuk wrote: I've downloaded 6.1-RELEASE-sparc64-disc1.iso and try to boot. loader boots kernel and hangs on message: jumping to kernel entry at 0x... What can I do? PS. It's sun 480 with 4 CPU. I have no complete info on the configuration.

Re: 6.1-RELEASE disk hangs after loading kernel on sparc64

Gavin Atkinson wrote: On Mon, 2006-06-19 at 12:08 +0400, Sergey Matveychuk wrote: I've downloaded 6.1-RELEASE-sparc64-disc1.iso and try to boot. loader boots kernel and hangs on message: jumping to kernel entry at 0x... What can I do? PS. It's sun 480 with 4 CPU. I have no complete info on

Re: 6.1-RELEASE disk hangs after loading kernel on sparc64

Sergey Matveychuk wrote: Gavin Atkinson wrote: On Mon, 2006-06-19 at 12:08 +0400, Sergey Matveychuk wrote: I've downloaded 6.1-RELEASE-sparc64-disc1.iso and try to boot. loader boots kernel and hangs on message: jumping to kernel entry at 0x... What can I do? PS. It's sun 480 with 4 CPU.

portupgrade failure

After upgrading to the latest portupgrade: dns root:~#portupgrade -v portupgrade 2.0.1 (2006/06/18) I got a failure on 2 out of 4 boxes. Now when I use portversion, portupgrade, or pkgdb I get: backup root:/usr/ports#portversion [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 34

bridge.ko, sysctrl.conf and ifconfig_XXX_name, SCSI as a boot device

Hello list, I have two minor problems: First one: I want to make bridging on two of my interfaces but have problem when I use ifconfig_XXX_name directrive in rc.conf . After each restart of machine I must enter manually commands for sysctrl to enable bridging. After reboot dmesg shows:

Re: puc and sio

On Mon, 2006-06-19 at 02:56 +0400, Dmitry Morozovsky wrote: Dear colelagues, playing with puc compatible MOXA card I found that it's rather useless with contemporary DEFAULT kernel: - sio compiled in, puc as module - puc identified, but no sio ports detected, even when puc.ko is loaded

Re: bridge.ko, sysctrl.conf and ifconfig_XXX_name, SCSI as a boot device

On Jun 19, 2006, at 4:38 PM, Todor Dragnev wrote: First one: I want to make bridging on two of my interfaces but have problem when I use ifconfig_XXX_name directrive in rc.conf . After each restart of machine I must enter manually commands for sysctrl to enable bridging.

HEADSUP: default for hw.acpi.reset_video changed

I thought this would be a small change (since the default was already supposed to be this way) but as usual with acpi, there is a lot of variation out there. I think it's split about 50/50 between systems where enabling this feature is helpful/neutral and those that it is harmful. The

Re: bridge.ko, sysctrl.conf and ifconfig_XXX_name, SCSI as a boot device

On Mon, Jun 19, 2006 at 05:38:43PM +0300, Todor Dragnev wrote: Hello list, I have two minor problems: First one: I want to make bridging on two of my interfaces but have problem when I use ifconfig_XXX_name directrive in rc.conf . After each restart of machine I must enter manually

Re: ath problems when in if_bridge mode

On Saturday 10 June 2006 18:00, Andrew Thompson wrote: On Tue, Jun 06, 2006 at 11:53:30AM -0300, JoaoBR wrote: Hi I find some problems when running ath cards in if_bridge mode. I have continuous UP/DOWN events on the uplink card. The connection is really interrupted for a second or so

Re: atheros 'device timeout'

As was spoken by Sam Leffler on 06/16/06 22:14~ Reid Linnemann wrote: On 6/14/2006, Sam Leffler [EMAIL PROTECTED] wrote: Reid Linnemann wrote: Thanks Sam, I've disabled power save mode in both wireless windows clients and I'll see if the problem lightens up. Also, do you know why device

Re: bridge.ko, sysctrl.conf and ifconfig_XXX_name, SCSI as a boot device

Thanks, I will use if_bridge from now. Anyone have ideas about second problem? Maybe I must remove device usb from GENERIC config and recompile kernel ? On 6/19/06, Brooks Davis [EMAIL PROTECTED] wrote: /etc/sysctl.conf is processed really early in the startup process so the renaming hasn't

make rerelease broken at camcontrol...

Thanks to all who answered my 'make release' questions; now that I have done the initial release cut, now I am trying out 'make rerelease', and it's bombing at the stage 4.4: building everything stage. -=- === sbin/camcontrol (all) cc -O2 -fno-strict-aliasing -pipe -Wsystem-headers -Werror -Wall

RE: save-entropy

Olivier, That process is meant to be there. I don't know why it has the '--' argument but it isn't likely to be a symptom of the problem you are having. Try sh -x /usr/libexec/save-entropy To get more insight into when it is failing. This will show you surrounding commands which will

Re: make rerelease broken at camcontrol...

Peter Losher wrote: Thanks to all who answered my 'make release' questions; now that I have done the initial release cut, now I am trying out 'make rerelease', and it's bombing at the stage 4.4: building everything stage. -=- === sbin/camcontrol (all) cc -O2 -fno-strict-aliasing -pipe