download the latest driver from
http://us.download.nvidia.com/XFree86/nforce/1.23/NFORCE-Linux-x86-1.23.zip
1) unzip NFORCE-Linux-x86-1.23.zip
2) cd NV_Linux_DRV_PKG_v1.23/SuSE10.2/rpm
3) rpm -Uvh nvlan-suse10.2-0.62-1.23.i586.rpm
4) cp /lib/modules/2.6.18.2-34-default/kernel/drivers/net/forcedeth.ko
/lib/modules/2.6.18.8-0.5-default/kernel/drivers/net/
reboot
5) use Yast to configure, you will get this "Giga-byte Ethernet
controller" at the network card configuration setting.
Enjoy!!!
Notes: assumed u download the NFORCE-Linux-x86-1.23 and your kernel is
2.6.18.8-0.5 (32bits), if you install 64bits OpenSuse10.2, then changed
accordingly.
Peter Sjoberg wrote:
On Tue, 2007-09-11 at 18:36 -0700, Joseph Loo wrote:
On Mon, 2007-09-10 at 23:42 -0400, Peter Sjoberg wrote:
On Mon, 2007-09-10 at 19:34 -0700, Joseph Loo wrote:
I just recently bought the Gigabyte M61P-s3 motherboard. I have an x2
AMD processor running on it. I installed opensuse 10.2 on it and found
out it will not recognize the ethernet Realtek RTL 8211 and Realtek
ALC883 Codec chip (audio). Has anyone found a way to get them to work?
or will I have to buy a LAN card and audio card for this computer as the
simplest solution?
Are you sure about the mobo, I have Gigabyte M61P-S3 but the
network/audio is MCP61, not realtek.
In my case I had network issues, it seems that the driver/card disagree
on the mac address order (fixed in latest upstream version of forcedeth)
and then the driver takes a random ip throwing of suse network
management.
I had to modify the startup scripts and udev rules to set a fixed mac
address (the correct one) to get it to work properly.
Did also find out that Gigabyte does support AM2 cpu but not
virtualization so it doesn't work for what I was planning on using it to
(unless I hack the bios my self). That act (and lack of response from
support) put gigabyte on my blacklist.
--
Joseph Loo
[EMAIL PROTECTED]
That is what the documentation says. I am runnning read hat and it does
report the same thing as you say.
Well, then I can only help you with the network side, newer tried the
Audio (I use it as a server running xen with a few virtual guests).
The network driver that works is forcedeth
It loaded automatically for me so I got eth0 configured properly the
first round
Next round it loaded again but I got a new MAC address for it and since
suse network config is based on mac it became unconfigured
next round, new mac and new config
I checked on the logs, google etc and it seems like it's a bug so that
the driver reads the mac address backwards, declare it invalid and
creates a random mac for this device. The bug is fixed in upstream
forcedeth (v0.57 and later I think) but even latest kernel 10.2 still
doesn't include the fix (only 0.56) and just adding upstream forcedeth.c
fails to compile so another solution is needed.
What I did (that works):
# dmesg |grep 'Invalid Mac address detected'
0000:00:07.0: Invalid Mac address detected: ad:42:92:4d:1a:00
This gives you the bus id and the reversed MAC
Edit /etc/udev/rules.d/30-net_persistent_names.rules and change the rule
for eth0 to say
SUBSYSTEM=="net", ACTION=="add", SYSFS{device}=="0000:00:07.0", \
IMPORT="/lib/udev/rename_netiface %k eth0"
This way the rule is based on the bus id, not the mac=same eth every
time.
In /etc/rc.d/boot.local I then put in a line to force the correct mac
(reversed version of the "Invalid" one from above
ifconfig eth0 hw ether "00:1a:4d:92:42:ad" &>/dev/null || true
After this I configured the port with "yast lan" and now it works fine
after every (re)boot.
Regarding the sound, as a test I did just try "yast sound" but got an
error that "The kernel module snd-hda-intel for sound support could not
be loaded." so I guess you need to find someone else to help you there.
/ps
--
Joseph Loo
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
