SEO

Hi

New to BSD here. Have been able to snatch some time for installing OpenBSD
from snapshot (the stable one was hanging on install). It seemed to install
ok, getting the sets over from the ftp server at openbsd.org, but upon
reboot, the machine hangs on :

biomask ef6d netmask ef6d ttymask ffef
pctr: user-level cycle counter enabled

(on a white text on blue background on dark background)

Have waited for nearly 10 minutes now, but it does not show any console
login.

Upon pressing <ctrl>+<alt>+<f6>, the screen goes blank, with a cursor
blinking on the top left corner.

The hardware in question is a Dell Poweredge Server SC420.

Thanks.

> The hardware in question is a Dell Poweredge Server SC420.

You're doing better than I did (see thread from last night). Are you using the
internal gigether port?

Chris Kantarjiev wrote:

>
>> The hardware in question is a Dell Poweredge Server SC420.
>
> You're doing better than I did (see thread from last night). Are you using
> the internal gigether port?

I am using the Broadcom Gigabit Ethernet port (bge0).

Madhusudan Singh wrote:
> Chris Kantarjiev wrote:
>
>
>>>The hardware in question is a Dell Poweredge Server SC420.
>>
>>You're doing better than I did (see thread from last night). Are you using
>>the internal gigether port?
>
>
> I am using the Broadcom Gigabit Ethernet port (bge0).

Could you drop me an email with a valid address? Maybe we can help each other
out without bothering the entire world in this newsgroup.

I still can't get my bge to come up correctly. I installed a different NIC (a
Linksys dc), and am using that for the install. One thing that you should note
when installing sets from the network - even if you boot from a snapshot, as you
did, the default FTP directory to fetch the sets is the release directory, not
the snapshot directory. So the GENERIC kernel that gets written to your new boot
disk is the one that didn't work in the first place.

Could that be your problem? I've managed to install the system fine over the dc,
and have booted cleanly.

(I've noticed a couple other doubtful messages on boot, which I will post
separately.)

chris

Christopher A. Kantarjiev wrote:

> I still can't get my bge to come up correctly. I installed a different NIC
> (a Linksys dc), and am using that for the install. One thing that you

Surprising. My bge0 worked right out of the box.

> should note when installing sets from the network - even if you boot from
> a snapshot, as you did, the default FTP directory to fetch the sets is the
> release directory, not the snapshot directory. So the GENERIC kernel that
> gets written to your new boot disk is the one that didn't work in the
> first place.
>

I see !

I will be trying to install the server again tomorrow. I think I need to
look at the directory that comes up on choosing ftp carefully before
pushing forward.

> Could that be your problem? I've managed to install the system fine over
> the dc, and have booted cleanly.

Let me check this tomorrow and get back to you.

> Surprising. My bge0 worked right out of the box.

What does your dmesg read? Mine says

bge0 at pci2 dev 0 function 0 "Broadcom BCM5751" rev 0x01, BCM5750 A1: irq 11
address 00:11:11:cc:a4:f0
brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0

I'm a little concerned that the chip thinks it's a 5751 but the driver thinks
it's a 5750.

> I see !
>
> I will be trying to install the server again tomorrow. I think I need to
> look at the directory that comes up on choosing ftp carefully before
> pushing forward.

The default is definitely wrong. Good luck.

Christopher A. Kantarjiev wrote:

>
>> Surprising. My bge0 worked right out of the box.
>
> What does your dmesg read? Mine says
>
> bge0 at pci2 dev 0 function 0 "Broadcom BCM5751" rev 0x01, BCM5750 A1: irq
> 11 address 00:11:11:cc:a4:f0
> brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
>

Mine says :

bge0 at pci2 dev 0 function 0 "Broadcom BCM5751" rev 0x01, BCM5750 A1: irq
11 address xx:xx:xx:xx:xx:xx
brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0

where I have obfuscated the MAC address.

In other words, identical to yours.

> I'm a little concerned that the chip thinks it's a 5751 but the driver
> thinks it's a 5750.

Well, mine works. So, I am not too worried about that

>
>> I see !
>>
>> I will be trying to install the server again tomorrow. I think I need to
>> look at the directory that comes up on choosing ftp carefully before
>> pushing forward.
>
> The default is definitely wrong. Good luck.


Your suggestion worked ! The system booted after I upgraded it to the
snapshot. Thanks.

Madhusudan Singh wrote:
> Christopher A. Kantarjiev wrote:
>
>
>>>Surprising. My bge0 worked right out of the box.
>>
>>What does your dmesg read? Mine says
>>
>>bge0 at pci2 dev 0 function 0 "Broadcom BCM5751" rev 0x01, BCM5750 A1: irq
>>11 address 00:11:11:cc:a4:f0
>>brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
>>
>
>
> Mine says :
>
> bge0 at pci2 dev 0 function 0 "Broadcom BCM5751" rev 0x01, BCM5750 A1: irq
> 11 address xx:xx:xx:xx:xx:xx
> brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
>
> where I have obfuscated the MAC address.
>
> In other words, identical to yours.
>
>
>>I'm a little concerned that the chip thinks it's a 5751 but the driver
>>thinks it's a 5750.
>
>
> Well, mine works. So, I am not too worried about that

Weird. What kind of hub/switch are you connected to? I'm hooked up to a 10bT
hub, which could conceivably be an issue, but it's all I've got at the moment.

> Your suggestion worked ! The system booted after I upgraded it to the
> snapshot. Thanks.

Glad to hear it!

Christopher A. Kantarjiev wrote:

> Madhusudan Singh wrote:
>> Christopher A. Kantarjiev wrote:
>>
>>
>>>>Surprising. My bge0 worked right out of the box.
>>>
>>>What does your dmesg read? Mine says
>>>
>>>bge0 at pci2 dev 0 function 0 "Broadcom BCM5751" rev 0x01, BCM5750 A1:
>>>irq 11 address 00:11:11:cc:a4:f0
>>>brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
>>>
>>
>>
>> Mine says :
>>
>> bge0 at pci2 dev 0 function 0 "Broadcom BCM5751" rev 0x01, BCM5750 A1:
>> irq 11 address xx:xx:xx:xx:xx:xx
>> brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
>>
>> where I have obfuscated the MAC address.
>>
>> In other words, identical to yours.
>>
>>
>>>I'm a little concerned that the chip thinks it's a 5751 but the driver
>>>thinks it's a 5750.
>>
>>
>> Well, mine works. So, I am not too worried about that
>
> Weird. What kind of hub/switch are you connected to? I'm hooked up to a
> 10bT hub, which could conceivably be an issue, but it's all I've got at
> the moment.
>

I guess I am connected to something similar as well.

>> Your suggestion worked ! The system booted after I upgraded it to the
>> snapshot. Thanks.
>
> Glad to hear it!

Well, I have decided to migrate to FreeBSD 5.3-RELEASE because it installs
out of the box and I won't have to probably worry about the ports / date
mismatch that I ran into when I tried to compile bash yesterday. The server
I am trying to deploy is a production server, and I do not have the time to
waste on an OS that becomes a headache of this kind. Especially, if the
hardware is pretty standard these days.

That and the fact that I have had some rather nasty experiences on the misc
list at openbsd where unprovoked invective against newbies and lying in
public (by the Exalted One - Theo de Raadt, no less) seem to be commonplace
and socially accepted activities. I guess arrogance can sometimes get to
one's head and its all downhill from there.

I wish you the best of luck with your OpenBSD adventures, only that I would
not want to be a part of a community that is beholden to one person, even
when that person is a foul-mouthed arrogant liar.