[SOLVED] system.log growing large after forcedeth-nockd.kext install

[meesterexx]

*SOLVED* Thanks to Moderator Colonel for the quick fix.

It was indeed the debug option turned on in the Info.plist of the forcedeth-nockd kext that caused the problem. Changing the true value to false and properly chown/chmod-ing the file solved the problem.

Thanks again Colonel for the working driver and the debug fix!

 

Original post=====================================================

Noob to osx86 here. Just installed jas 10.4.8. AMD Intel SSE2 SSE3. I have:

asus a8n-vm csm / Athlon64 3200+

1024mb ddr400

bfg 7900gs pci-e 256mb

 

I tried the regular forcedeth and forcedeth-nockd kexts, but they didn't work. Then I tried the forcedeth-nockd.kext from Colonel in this thread:

http://forum.insanelymac.com/index.php?act...st&id=10649

 

It works fine, but I get a TON of these messages repeated every second in my /var/log/system.log:

May 11 16:22:46 magics-computer kernel[0]: forcedeth: packet 80000000 - 8000062e

 

After only a few minutes, my system.log is over 30mb. I noticed in the Info.plist that debug is on. Could this cause it? If so, how do I properly edit the Info.plist? (I was able to display it using cat):

 

magic$ cat Info.plist

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>CFBundleDevelopmentRegion</key>

<string>English</string>

<key>CFBundleExecutable</key>

<string>forcedeth</string>

<key>CFBundleIconFile</key>

<string></string>

<key>CFBundleIdentifier</key>

<string>com.triton.forcedeth</string>

<key>CFBundleInfoDictionaryVersion</key>

<string>6.0</string>

<key>CFBundleName</key>

<string>forcedeth</string>

<key>CFBundlePackageType</key>

<string>KEXT</string>

<key>CFBundleSignature</key>

<string>????</string>

<key>CFBundleVersion</key>

<string>1.0.0d2</string>

<key>IOKitPersonalities</key>

<dict>

<key>nForce 4 LAN</key>

<dict>

<key>CFBundleIdentifier</key>

<string>com.triton.forcedeth</string>

<key>ChecksumReceive</key>

<false/>

<key>ChecksumTransmit</key>

<false/>

<key>Debug</key>

<true/>

<key>IOClass</key>

<string>com_triton_forcedeth</string>

<key>IOKitDebug</key>

<integer>0</integer>

<key>IOMatchCategory</key>

<string>nForce4 LAN</string>

<key>IOPCIPrimaryMatch</key>

<string>0x026910DE</string>

<key>IOProviderClass</key>

<string>IOPCIDevice</string>

<key>IOResourceMatch</key>

<string>IOKit</string>

<key>IRQTimer</key>

<true/>

<key>MultipleSegments</key>

<false/>

</dict>

</dict>

<key>OSBundleLibraries</key>

<dict>

<key>com.apple.iokit.IONetworkingFamily</key>

<string>1.0.0b1</string>

<key>com.apple.iokit.IOPCIFamily</key>

<string>1.0.0b1</string>

<key>com.apple.kernel.iokit</key>

<string>1.0.0b1</string>

<key>com.apple.kernel.libkern</key>

<string>1.0.0b1</string>

<key>com.apple.kpi.bsd</key>

<string>8.0.0b1</string>

</dict>

</dict>

</plist>

If not the debug, what is causing so many of these messages in system.log? I am worried about exponential growth of the log file.

Thanks in advance.

[meesterexx]

Update:

Still not sure what is causing it, but if I

 

sudo rm -R /var/log/system.log

sudo touch /var/log/system.log

 

then the file stops growing. It's like the initial loading of the kext causes a looping of messages to the log, then removing/recreating the log stops it.

 

I would still like to solve this, removing then recreating the log is not really a graceful solution for such an elegant OS.

[cycle]

I also got this working on my A8N-VM CSM board, FWIW. Many thanks, Colonel and OP.