Jump to content

frizbot

Members
  • Content count

    377
  • Joined

  • Last visited

  1. Nvidia 7600GT on Snow Leopard in x64

    True, 64bit OSX86 should not be a requirement for anyone right now AFAIK. Still, it is vaguely desirable, and Apple needs a way to obsolete hardware. Anyway, I am in the same situation, 7600GT. 10.6.4 Chameleon RC5 32bit vanilla. NVInject works in -x32 bit mode. Switching to graphicsenabler=yes and removing -x32 booted but lacked QuartzExtreme etc. (I suggest trying this anyway to see about 64bit compatibility aside from graphicscard). EFIString works in -x32 with QE, so I have removed NVInject. Booting NVInject64 or EFIString in 64bit mode will boot, but it stops at a blue screen that otherwise disappears quickly under 32bit kernel. 64bit also did not work under SnowOSX 3.6 for me. If EFIString does not work, 64bit appears incompatible with this card at the moment. Options I have not tried include NVEnabler, the nVidia graphics update from Apple, and any graphics-related DSDT patching. As Beerkex'd said, 64bit isn't necessary now, so I'm not going to continue testing on it (I'm sick of nervous "-s -x -v -x32" booting). If anyone has an update regarding a nvidia 7600 GT booting 64bit OSX86, it would be appreciated.
  2. Ethernet Kernel Panic under iATKOS 1.0

    I'm afraid I didn't save a copy of the kext. PolishOX's original kext didn't work for my MT variant which differs in that it uses the 82541GI chipset. If you have a MT card, you can find out what chipset by looking at the small CPU-looking component on it, and reading the topmost product code silkscreened on the top in grey. My MT card is actually on my desk at the moment and has been for a month. The ethernet jack's solder connections are weak. I actually resoldered the pins down maybe a year ago, but a different grounding connection came loose a couple months ago. It had started getting intermittent "cable not plugged in" type errors. I've since upgraded my machines to the Intel 1000 CT, the improved and rare updated version of the PCI-E ethernet card I had mentioned a while back. Excellent card that I recommend highly. It didn't work automatically in my copy of 10.5.4, and there was no information available on getting it to work, so I didn't try any harder. I just did a google search now, and someone named Flitskikker lists owning a CT card and says later "Network works, as I'm typing this from my iDeneb installation (Mac OS X 10.5.6 (iDeneb 1.4)).", but I have 10.5.4 and can't verify it. Someone messaged me about the MT with the note "Seems to me it's only working on device id 8086 100E.", but that person seems to still be having trouble. I don't know what is best to do, and I've forgotten entirely what the device ID changes did. My recommendations are still not helpful. I changed the motherboard for one that includes what I believe is the Marvell 88E8056, which works with a minor edit of a native kext. USB 2.0 adapters should work fine, but they'll have poor performance, high CPU usage, and fewer features (not a problem on a desktop machine, but bad for a server of any kind). I forget if Apple's PCs can still use firewire as ethernet the way some Macintosh hardware could. I still see the Intel Gigabit 1000 GT PCI card everywhere (IOW it's hard to find my PCI-E cards still), and I seem to remember the GT worked better in OSX86. I actually prefer OSX86 10.4, so that's still an option, and who knows what 10.6 will be like for ethernet compatibility. Good modern PC ethernet cards are surprisingly hard to find (eg. PCI-E, gigabit, jumbo frames, RX/TX offload), and among the three or four cards available, I don't think any are OSX86 compatible. If it's of any interest to anyone, because of the P5K-e Wifi motherboard and its working Marvell ethernet (and extra Realtek RTL8110SC port for extra OSX86 insurance), I'm not on these forums much anymore since everything just works fine and reliably.
  3. I've made some progress on this. It turns out that this isn't Apple's quarantine. Quarantine might have similar issues, but this is a Windows issue that 10.5 is supporting erroneously. Using xattr -l [filename], you'll get this data- :ZONE.IDENTIFIER:$DATA: [ZoneTransfer] ZoneId=3 The attribute (@) in ls -all is showing this attribute, not Quarantine, though Quarantine would also show the file has an attribute. ZoneId is a Windows feature that tells what "zone" or security level a file is. Zone 3 is Microsoft's untrusted online download zone, which is why it can add attributes to any file type. The quirky bit is that this stupidness is being supported in OS X. Windows uses NTFS streams to store this data. Samba on OS X advanced enough to support these alternate data streams as file attributes. The problem is that Windows will write a file on a network share with this stream, which turns into an attribute, but it can't read it back fully. It will read the file, but it can't copy it back. Under Windows, you can clear this attribute by getting properties and clicking "unlock". To get Samba to stop working in this half broken way, in the /etc/smb.conf , change "vfs objects = darwinacl, darwin_streams" to "vfs objects = darwinacl", and change each "yes" in "stream support = yes" and "ea support = yes" to "no". That prevents writing the attribute, and disables all alternative stream saving (which might cause problems, but likely is just more secure anyway). This should work, unless it ignores the configuration. The files that still have the attribute are harder to clear. There's a program pack called ACP that purports to do it by searching out all Xattr attributes on OS X, but it is neither opensource nor free. There's also Windows programs that can clear Alternative Data Streams, like Sysinternals' Streams, or other annoying {censored} (like ADSSpy (integrated into Hijack This), which only works on NTFS local drives). The best I've found is ZoneIDTrimmer, which is freeware but annoying as a contextual menu explorer addon, at http://www.gasanov.net/ZoneIDTrimmer.asp . I ran that and found a thousand ZoneID settings on my network share. That tool won't remove all attributes, but it should fix the problem on any given file. This somewhat solves the issue. Changing Samba's configuration stops the files from being written in an unsupported way. ZoneIDTrimmer removes the offending attribute.
  4. USB Audio Problem

    I apologize, I had thought I had fixed the issue on my machine. It returned. In searching for instances of the kernel function clock_get_uptime, I found some people talking about it while overclocking their Macintosh G5's. I remembered I had overclocked. Looking at my BIOS settings, I see that I enabled the motherboard's automatic overclocking feature, not wanting to damage anything and let it do modest speed increases. The description for my Asus feature is "When N.O.S. is enabled FSB frequency will be optimized automaticall (SIC) depending on CPU loading". Clearly this would change timing dynamically, and "radically". I've set up a moderate overclock, but set manually. I'm not seeing the error. If it returns, I'll try disabling all overclocking. I don't mean to be annoying with the double post, but this kind of information is very useful when searching for information on errors like this.
  5. USB Audio Problem

    I don't know. This can happen in 10.5 as well. It causes audio stuttering, pausing, etc. Try restarting. Also try reseating the USB plugs in the ports. Try a different USB cable if you use an extension. Try another USB port. This could be related to power saving features that slow the CPU clock, which the USB audio is relying on for timing. I did not disable this feature, and my audio is working again after the steps above. Apparently there are nanosecond APIs available, but not in use for these drivers. OS X is getting better with integrated audio cards, so try your motherboard's audio chipset again if the USB can't be helped.
  6. I need to post this somewhere on the internet so that I'll be able to find it again, and other people will be able to find it. 10.5 institutes a new feature called File Quarantine. It sets a HFS+ attribute to files that were "downloaded from the internet", effectively locking them from certain file operations until cleared in the GUI. When double-clicked, these files will give some warning about executing them. Fine. When files are transferred to an OS X Samba share from Windows 2008 (and probably Windows 2003 (Win2008 & Win2003) and probably any other system), the Quarantine attribute is set. You can see this by in a terminal entering "ls -all" in the folder, and noting the "@" at symbol in the permissions for the new files. These files are "Quarantined". Fine. When trying to copy these files from the share to another machine, Windows 2003 will give the error "Cannot copy <filename>: Cannot read from source file or disk". Windows 2008 will give the error "Invalid File Handle". The file is not corrupted in any way despite these errors being associated with disk corruption and corrupted data (specifically a WHS drive corruption issue). The file is simply "Quarantined", which Samba is respecting (or is affected by), and Windows is simply freaking out. This is not a Windows issue despite looking like one, and the Apple Quarantine feature explains a few Windows people freaking out lately. I've been searching, but there appears to be no way to disable Apple File Quarantine directly. One option is to set more "safe" file extensions or MIME types, another is to run an apple/shell script that unsets the quarantine attributes recursively over every drive. The apple UNIX application in question is xattr, which has no man page. The command would be "xattr -d com.apple.quarantine thefilenamehere", but here that gives the error "No such xattr: com.apple.quarantine", and there appears to be no fix for this. If this post in the wrong place, please move it instead of deleting it, since I want people searching for the information to be able to find it. I'd also like to thank Apple for emulating Microsoft's quagmire of various and unhelpful security "features".
  7. Ethernet Kernel Panic under iATKOS 1.0

    That's good news. Mine never did work reliably with any kext combination. There are different versions of the MT I'm told. I might try the 1000PT PCI-E card that's out now eventually. Onboard is working here now, so I'm putting it off.
  8. Ethernet Kernel Panic under iATKOS 1.0

    No status, didn't work for me. I replaced the motherboard with one that had built-in ethernet that is known to work. Sorry. It's a bad solution, but it's the only one I knew would work. I'll no longer be posting any new troubleshooting info on OSX86 and this problem since I've replaced the hardware.
  9. Distro Corruption?

    I'd like to note that "freekz" has the same problem here- http://forum.insanelymac.com/index.php?showtopic=109249 I've posted there on it. I have updated to the new iTunes 7.7, and have not yet crashed making smart playlists. This could be due to the old one being Uphuck-modified, or to the new one fixing the issue.
  10. iTunes Smart Playlist Crash

    I also have this problem with a similar setup. I'd like to note Geo Mandell also has it here- http://forum.insanelymac.com/index.php?sho...4&hl=itunes He deleted iTunes and reinstalled it, but the problem later came back. I have updated to the new iTunes 7.7, and have not yet crashed making smart playlists. This could be due to the old one being Uphuck-modified, or to the new one fixing the issue. My only other suggestion is to try another distribution, or a more vanilla OS X. The Uphuck team makes extensive modifications to OS X that have annoyed me, like deleting the dictionaries. Problems occur with Adium and iTunes when they shouldn't. There's a newer iAtkos that might fix these problems, but I'm going to be exploring the retail DVD options.
  11. I haven't yet. Older versions, like Adium 1,2.4 still work. If you login as a different user, Adium can launch. It could require administrator privileges. I'm not sure about the cause, but it happens with Uphuck systems. Neither deleting the preferences, nor application support files help. Using chown -R username /users/username also does not help. These are fixes I've seen elsewhere that do not help this problem.
  12. Iatkos 2.0 help!

    Try burning a new copy. Try downloding a new copy. Did your ISO checksum match the one they published?
  13. Were Back !

    Have any x86 (-64) motherboards enabled EFI booting? That's why Windows' new EFI boot feature was exciting.
  14. Help with Kernel Panics?

    It does not. There is an alternate method. In the Darwin bootloader, type without the quotes "debug=0x100". KirbySaysHi on these forums found this trick. It will display kernel panic text onscreen.
  15. Interesting Shutdown Solution

    Try booting with -v and note any messages on shutdown. The problem is where the shutdown fails, if it's after disks are unmounted etc.
×