aparently I broke OSx ... AGAIN

[Paprika]

So since my ps2 keyboard wasn't working natively, I went into OSx86 thru vmware, and... All I did was:

 

- add the Keyboard kexts to /etc/rc

 

- swap the command and control keys on the keyboard thru the control panel

 

- applied the following permissions to fix an error i was getting reguarding the MaxxussAMDPCNET.kext:

 

cd /System/Library/Extensions
sudo find MaxxussAMDPCNET.kext -type d -exec /bin/chmod 0755 {} \;
sudo find MaxxussAMDPCNET.kext -type f -exec /bin/chmod 0644 {} \;
cd /System/Library
rm -rf Extensions.mkext Extensions.kextcache
reboot

 

 

 

 

 

NOW, my gui only comes up when I pull it up in vmware even tho I installed it natively!!

 

 

 

If I try to boot it directly from the bootloader I never see a logon screen but instead it just sits at the screen fulla text... if you know what I mean. I've been getting all sorts of errors from OSx on startup even when I had it working correctly so it's hard to say which errors are new and which have been there.

 

 

 

CD: Jas 10.4.6 w/ all AMD patches and Combo update installed.

 

 

 

 

 

What can I do to fix this?

[Rammjet]

- add the Keyboard kexts to /etc/rc

 

CD: Jas 10.4.6 w/ all AMD patches and Combo update installed.

After modifying the /etc/rc file, you might need to repair permissions.

 

For "all" AMD patches, should select only one of SSE2 or SSE3, not both.

 

To repair permissions, need to start in single-user mode (-s). Type "-s" at the command prompt for the Darwin bootloader. If using a different bootloader, press and hold F8 as soon as you select your OSX partition. Then type "-s" at the command prompt.

 

Single-user mode is a command line environment. Type:

mount -uw /
diskutil repairPermissions /
reboot

[Paprika]

After modifying the /etc/rc file, you might need to repair permissions.

 

For "all" AMD patches, should select only one of SSE2 or SSE3, not both.

 

To repair permissions, need to start in single-user mode (-s). Type "-s" at the command prompt for the Darwin bootloader. If using a different bootloader, press and hold F8 as soon as you select your OSX partition. Then type "-s" at the command prompt.

 

Single-user mode is a command line environment. Type:

mount -uw /
diskutil repairPermissions /
reboot

 

 

 

Okay I will try that, thanks.

 

 

 

And yes, I only selected SSE2.

 

 

 

Let me ask you this: When i tried SSE3 back in the day, OSx would not boot. I have a AMD 64-bit 3800+ X2, and CPU-z tells me I have SSE3. So, is it true that OSx doesn't like SSE3 on the dual core AMD processors right now? I'm trying to speed the system up a bit and thought that the SSE2/SSE3 thing might be a cause?

[joe75]

Yes, X2s are difficult with SSE3

[Rammjet]

Let me ask you this: When i tried SSE3 back in the day, OSx would not boot. I have a AMD 64-bit 3800+ X2, and CPU-z tells me I have SSE3. So, is it true that OSx doesn't like SSE3 on the dual core AMD processors right now? I'm trying to speed the system up a bit and thought that the SSE2/SSE3 thing might be a cause?

The old kernel (8.4.1) like in 10.4.6 appears to have problems with SSE3 on X2's and people have had to use SSE2.

 

This might be solved with the new kernel for 10.4.8 (8.8.1) that works with AMD SSE3 coming out real soon. http://forum.insanelymac.com/index.php?s=&...st&p=228105

[Paprika]

The old kernel (8.4.1) like in 10.4.6 appears to have problems with SSE3 on X2's and people have had to use SSE2.

 

This might be solved with the new kernel for 10.4.8 (8.8.1) that works with AMD SSE3 coming out real soon. http://forum.insanelymac.com/index.php?s=&...st&p=228105

 

 

 

Okay sweet, I appreciate both of you guy's help!

 

Thanks.