onsdag 01 december 2004 20:50 skrev yep(a)osterbo-net.dk:
Yast detects one of the on-board nics (realtek 8169) sets it up and then:
dhcpcd still waiting for data (forever)
That's a kernel issue, have you tried another kernel? I'm using a MSI
NEO FIS2R motherboard, with a 8110S gigabit lan card built in. It didn't
work out of the box with 9.1, but does with 9.2, no problems whatsoever.
Have you looked at kernel messages concerning the device?
Have you taken a look behind the mobo to see if the lights go on?
What lan type are you using 1Gb? 100Mb? 10Mb? have you tried putting up a 10Mb
hub between, or a 100Mb hub, to force the network rate? Tried setting up the
kernel parameters to fix the network rate, in case that's the problem?
I suspect I'll have to delete those "unique
keys" somewhere in
the /var/lib/somewhere and have a go with the nvdia module (nvnet) and see
if it gets detected
What on earth for?
And copy appropiate files to floppy (he he .... ) I kind of need the floppy
entry in media ;-) (missing). Didn't get to fight adressing directly with
the fd0: yet.
Doh? works ok here, are you sure the floppy is installed in the bios?
OK For the 3'rd and 4'th SATA port on the
board it's a plain no show.
Any action with the Promise SATA II TX4 is just a dream for now I guess.
(And I only need "ordinary" access)
I'm using a 160Gb Seagate hard disk on the 3rd SATA port (The promise SATA
controller), without any problems. Tried it first on the 2nd SATA port, then
switch to the third, as I believe that controller has better leverage as the
CDROM's are connected to the plain ATA device (DVD Rom and DVD RW).
I've tried with the latest and greatest from nVidia too
Sure the mobo isn't out of order?