I've got a new amd64 system with the Supermicro H8DCE mobo:
Aside from a DA disk, the SATA controller seems to work fine, (though I
haven't done any RAID tests - I plan to use RAIDframe).
But the -current floppy can't find any network ports to use. This is the
nVideia nForce Pro 2200/2050 chipset.
Any chance there will be support 'soon'? can someone recommend a
gigether card that works, in the meantime?
Thanks,
chris

Well, that's disappointing. I bought a D-Link DGE-530T, which is claimed
to be supported at as sk(4), but the
amd64 kernel doesn't see it.
What am I likely to be doing wrong here?
chris

Is there some way to catch the boot messages? I don't seem to be able to
even use ^S. Are they also being spit out on the console port, perhaps?
It would be nice to see if the device is being probed, even if not
configured

Sun, 11 Sep 2005, Chris Kantarjiev wrote:
Well, that's disappointing. I bought a D-Link DGE-530T, which is claimed to
be supported at as sk(4), but the amd64
kernel doesn't see it.

What am I likely to be doing wrong here?

At the very least, give ~zero information to help you.

Is "sk" in your kernel config file?
If so, what does dmesg say?

- Hubert

Sun, 11 Sep 2005, Chris Kantarjiev wrote:
Is there some way to catch the boot messages? I don't seem to be able to even
use ^S. Are they also being spit out on the console port, perhaps? It would
be nice to see if the device is being probed, even if not configured

kernel boot messages can be printed by dmesg(8), a copy of that output
right after booting is usually kept in /var/run/dmesg.boot.

- Hubert

Hubert Feyrer wrote:
Sun, 11 Sep 2005, Chris Kantarjiev wrote:

>Is there some way to catch the boot messages? I don't seem to be able
>to even use ^S. Are they also being spit out on the console port,
>perhaps? It would be nice to see if the device is being probed, even
>if not configured

kernel boot messages can be printed by dmesg(8), a copy of that output
right after booting is usually kept in /var/run/dmesg.boot.

- Hubert

I'm working from the -current boot floppies. dmesg isn't there, nor is
there anything in /var/run

I'm afraid I don't know what's in the config file for the boot floppy. I
was assuming that it was GENERIC, which has sk/skc in it.

The DGE-350T and Linksys EG1032 are the only gig ether interfaces on the
shelf at my local store; they both seem to have the same chipset. Is
there some other one I should try ordering, that is known to work in the
amd64 port?

Thanks.

Chris Kantarjiev wrote:
I've got a new amd64 system with the Supermicro H8DCE mobo:

Aside from a DA disk, the SATA controller seems to work fine, (though I
haven't done any RAID tests - I plan to use RAIDframe).

But the -current floppy can't find any network ports to use. This is the
nVideia nForce Pro 2200/2050 chipset.

Any chance there will be support 'soon'? can someone recommend a
gigether card that works, in the meantime?

Thanks,
chris

Well, I pulled a network card from another system that comes up as tlc0.
Yay. But now I can't find the head of the FTP tree to copy. The floppy
wants to start at pub/NetBSD/NetBSD-3.0_BETA, which doesn't exist.

I got the floppy images from
, which no longer
exists there's a 200508270000Z directory now, but it's empty.

So, where *am* I supposed to get sets from when installing the beta?
do I need to install 2.0.2 and upgrade? The 2.0.2 kernel hasn't been a
winning thing for me - it's pretty hungry for VM resources, so I thought
I'd just start with 3.0

chris

That's tlp0, not tlc0, for anyone that's really paying attention.

I ended up, for now at least, installing the 2.1-RC3 sets. Didn't really
work very well, but I got a kernel that seems to support the skc/sk
DGE-530T (Marvell 88E1011 chipset), at least to the point where it will
light up the link LED on the hub, even if it doesn't light up its own
LEDs in any way. Very odd behaviour there - I think I'll try another card

But the file system isn't really quite right; no big surprise, I guess,
since I used the 3.0 floppies. Would really like to find the correct
sets to install

Manuel Bouyer wrote:
Sun, Sep 11, 2005 at 09:10:25PM -0700, Chris Kantarjiev wrote:

>That's tlp0, not tlc0, for anyone that's really paying attention.
>>
>>I ended up, for now at least, installing the 2.1-RC3 sets. Didn't really
>>work very well, but I got a kernel that seems to support the skc/sk
>>DGE-530T (Marvell 88E1011 chipset), at least to the point where it will
>>light up the link LED on the hub, even if it doesn't light up its own
>>LEDs in any way. Very odd behaviour there - I think I'll try another card
>>
>>But the file system isn't really quite right; no big surprise, I guess,
>>since I used the 3.0 floppies. Would really like to find the correct
>>sets to install

I'd expect a new 3.0_BETA sets would appear in pub/NetBSD-daily in a few days.
That's a problem with the current autobuild scripts: for branches, it will
keep only one instance of the build. So if the build goes bad, you end
up with no binary sets for the branch on the ftp server :(

K, I'll try to be patient. I tried the 2.1-RC3 'daily' last night and
had a lot of network problems. I really don't want to drop back to 2.0.2
if I can avoid it works, but crashes every other day in our usage.