Jump to content


  • Content count

  • Joined

  • Last visited

  1. Prelinked kernel isn't necessary, i still prefer a higher rate at benchmarking & performance than being able to load compiled kernels. That's why i've still got a leopard install on my laptop . I'll try 10.6.8 today with CStates injection, shall it be better.
  2. Fool of me never thought it could be that, i may had modified it some time ago, but didn't notice. Thanks again my friend!
  3. What i can include for now is my ioreg w/o legacy kext but with generate_pstates and generate_cstates from cham 760, and my dsdt. I'll post what you requested tomorrow, now i have a lot of work to do and little time. DSDTIOReg.zip
  4. Could you please post them both? I have them but still cpuplimit is 0x04. PD: What i'm saying is that you have to let the bios configure it (ie start with the lid closed). Then you'll see everything on the external monitor. Once that's done it's a good change to try mirror out.
  5. I must say i'm impressed with release 760 of chamaleon. It has mirrored display (or extended display support, replicating output) support. I won't test if that means anything for OS X, as i actually need my laptop to work (The other one blew up), but there's a high change that some achievment could be done (i'm using 10.6.6, for those guessing it), because the configuring phase of X3100 should be done already (unless OSX wants to do it again, as far as i know Windows doesn't reconfigure display mirror when it's already done). Good luck! PD: Oh and btw, could someone tell me which kext do i need to activate speedstep on 10.6.6? It keeps at cpuplimit=0x04 and first p-state and this goes laggy as hell.
  6. Look, if you've got an Intel GMA x3100 download the one that labels "Intel Video". If you have, otherwise, an ATI X**** download the one called "Ati Video". Those must be downloaded from the unofficial site, as Juanerson said! If you still can't patch (doesn't matter he's on 7) you'll have to do it the freeDOS - way. Just grab a Pendrive and follow the instructions.
  7. In fact you could boot the image via PXE, as far as chamaleon does support it.
  8. You could try it on linux, using the DSDT provided. Should it work fine, it was the OSX installation.
  9. Completely agree with BlackCH. Windows itself as those with Linux kernel and BSD (not OSX, obviously) discard the DSDT partially or totally if they can't recognize it and try to recognize each and every device your computer has. Your CPU has a driver on Windows, believe it or not, and so knows how to handle your CPU even if DSDT are bad, that's why it gets to work there. OSX is done to be only compatible for hardware they selected and using only the software it was designed for it. So it won't auto recognize the hardware devices (it does on some, as they might be generic for similiar systems) but won't do on CPU for instance as each smc is tighly bound to it's compatible models (and thus it's the DSDT). Just update your BIOS, reset CMOS settings (if it still gives error, as CMOS might be corrupt) and you shouldn't have problems. Otherwise report.
  10. Intel 3945 experimental driver is almost usable. You have to keep a constant connection in order for it to be kept up (ie, ping a server), but besides that it works "fine".
  11. Bluetooth and wlan are managed together on these HP models. You need to install the correct driver in order to get WLAN working.
  12. I also have random kp's but they're because a faulty wifi driver. I'm also using Andy's lastest kext.
  13. Does anybody know if 10.6.7 solves any graphics problem (ie, mirroring). I found this interesting app, at least it allows to avoid restarting computer when trying mirroring. http://www.fabiancanas.com/Projects/MirrorDisplays/ And this: http://www.screenrecycler.com/ScreenRecycler.html. What i'm trying to find is some app that does a virtual mirroring, that's via software. PD: It's possible to do via VNC, having both the client and the server on the same machine. EDIT: Well it's not the best solution, but at least it uses built-in software. Go to System preferences ==> Sharing and turn on remote administration (i guess that's the name in english). I'd advise only to allow the local user, but it's your choice. Enable both Observe and Control options in it. Get a terminal and type: defaults write com.apple.ScreenSharing skipLocalAddressCheck -boolean YES Now start Screen sharing and connect to localhost. VoilĂ ! You have your mirrored display. Of course this is the same as using a vnc server - client combination, but at least it uses apple-updated software. Note that it produces a nice effect if started on the main screen. Also, if i did understood correctly it'll only duplicate main screen, so that you just have to put Screen sharing window in the extended one and that's all. I'd also recommend to select maximum quality, because as it uses internal loop it doesn't matter the connection. One final note, other clients can connect to you via port 5900 using your user & password so i'd recommend a firewall like little snitch to block that users. That's because they actually can control your display using mouse & keyboard.
  14. As I said, if you don't do a cold-boot your devices internal RAM won't be erased, that's because they take more time to get to. Anyways, for what you're saying it's mostr probably a hardware issue, as BlackCH pointed. You might try booting with this BIOS version using the celeron cpu. IF that's fine then it's for sure the FSB. PD: Googling for the mobo id should point you the chpset id.
  15. Kate you must note that some devices do not initialize at once. For instance, i've got a 2 TB HDD which does need a restart (booting twice) for it to start. That behaviour is caused because almost every device out there has an internal PIC & ROM, and does initialization only once, but BIOS doens't wait enough time for it to get ready, so that it doesn't recognize it. Then it comes OS behaviour, there are some OSes that recheck all devices initialization && do it (remember plug&play?) and some that don't. Well, most surely it isn't related to your problem. Try to boot in another OS and check it's correctly working. If it isn't ==> reflash, if it is you might have to reinstall as it's the easiest solution. PD: When flashing an EEPROM be sure to have a good physical device beyond it. That's because, though most flashers nowadays do it, some do not charge the ROM image to memory and so they read from the device as they write it. That's specially dangerous using a cdrom. I'd recommend doing the same as me and blackch did, just get into windows (not a livecd! windows ISN'T designed for that purpose - even winPE) and create a freeDOS usb. Flash it and cross fingers that it doesn't hang. There are many manuals out there on how to flash, which are the dangers and how to proceed. -To me it'd appear a bad flash, or maybe you haven't RESET CMOS settings? -. Altough not strictly necessary, every manufacturer out there recommends doing it. NOTE: If you haven't figured it, whether you modify or not BIOS settings, when you leave the configuration screen your system RESTARTS.