Jump to content

CommanderData

Members
  • Content count

    6
  • Joined

  • Last visited

About CommanderData

  • Rank
    InsanelyMac Protégé
  1. fight the backlight brightness control feature

    That is very interesting, I have never used Reggie SE. I'll download the CHUD tools from Apple so I can try to do the same thing. My laptop is a Fujitsu P1620 (also have a P1610), both with GMA950 graphics. The program I wrote for Windows brightness control is kind of tied to the Fujitsu line because it also reads accelerometer feedback to know when you're holding the tablet/laptop. It basically does the multi-step dimming based on lack of user interaction, just like a MacBook would dim, and then later go dark if you leave it alone. It will be a dead end for us in the Mac world. What seems really odd is the X3100 kext (and possibly the GMA950) must be monitoring that register and setting it back every time you change it. If we could disassemble or get the source for the kext someone might be able to see where it is happening and remove it. SticMan- off topic but I'd guess his SD reader was on the USB bus in that laptop, rather than an offshoot of the PC Card / PCI bus like it is in mine. Or you could use a PC Card to SD adapter if your PCMCIA slot works.
  2. fight the backlight brightness control feature

    cele_82, we may be able to trace what is happening with the brightness buttons or my API call samples in Windows using a debugger (like SoftICE) or disassembler (like IDA). I do not have access to those myself at the moment, but someone here might.
  3. fight the backlight brightness control feature

    Nice Summary! In Windows I've written applications to control the display brightness, but it relies on Windows specific APIs like CreateFile ("\\.\LCD",.... and DeviceIoControl. These methods DO work for Windows XP, the brightness range (Min and Max settings) and current brightness can be queried, the actual brightness can be set (as long as it falls within the Min and Max). Maybe there's someone with more knowledge of what happens after the Windows API calls I mention? What registers are written, and where? Looking forward to cracking the display brightness issue sometime soon, my battery life could use a boost.
  4. TabletMagic for TabletPCs

    Scott, Since Wrayal is unable to help at the moment I figured I would give you some info. My ioreg was taken from a P1610, which has a serial touch screen the same size as the P1510, but higher resolution. From what I've read it seems that the P1510 linux interface method works on the P1610 with some small modifications. See here: http://www.coderaptors.com/?Kubuntu_on_a_Lifebook_P1610 More specifically, his link to a modified linux driver: http://82.110.105.85/coderaptors.com/files...ble_touchscreen Here is the ioreg from my P1610: ioreg_fujitsu_P1610.out.txt I'll do whatever I can to help your data gathering and testing. If you can make this generic enough to support both the P1510 and P1610 it would be awesome! Thank you for your efforts.
  5. CardBus/PCMCIA PC Cards for Leopard

    Chun-Nan, first let me say thank you for your incredible efforts! I have tested your Beta 2 package that Equate bundled for you and it does fix some of my problems. First, a bit of info for you: Laptop: Fujitsu P1620 CPU: Core 2 Duo RAM: 2 GB GPU: GMA 950 Sound: Realtek Hi Def Audio (262) - Working Network: Marvell Yukon 88E8055 - Working Wifi: Dell Truemobile 1390 - Not Working (removed Atheros AR5006EXS, see below for more) Bluetooth: Cambridge Silicon Radio - Appears to be working well PC Card Slot: O2Micro? - Appears to be working well SD Card Slot: not detected (a common problem it seems) Running Kalyway 10.5.1 with combo update. Prior to your PCIFamily/PCCard kexts I had no working network connectivity. The devices were just not detected at all by the system (even after editing info.plists to add the matching PCI/Vender IDs). After your kexts the wired Ethernet works fine, and it appears my PC Card slot is detected and initialized (I do not have any cards to test it with at the moment). Now, on to my problem. The original Atheros Wifi Mini PCI-Express card would be seen at the boot and then I would get an error (something along the lines of "error at line 481 blah blah blah.cpp") and then it would report kext was loaded UNsuccessfully. This was after installing your kexts, prior to that it I don't think it was seen at all. After a lot of reading in the forums here I decided to pick up a Dell Truemobile 1390 Mini PCI Express card and swap it with the Atheros one. This new 1390 Mini PCI-E card is partially detected on boot into OS X, as I can verify in System Profiler after booting that the kexts AppleAirPortBrcm4311 and IO80211Family are loaded. However, under Airport it shows "No Information Found", and I cannot find or add an Airport connection at all in System Preferences -Network. The 1390 is working fine in Windows XP, I have no trouble with it there. I have included a few highlights of Dmesg and Ioreg here, as well as their full output in the attached files. Dmesg PCI section: pciBridgeCheckConfiguration(bus 9, state 1) Checking PCI bus 9 BIOS config retained pciBridgeCheckConfiguration(bus 2, state 0) Checking PCI bus 2 BIOS config retained pciBridgeCheckConfiguration(bus 5, state 0) Checking PCI bus 5 MEM: new range size 100000 align 100000 flags 0 PFM: new range size 0 align 100000 flags 0 I/O: new range size 0 align 1000 flags 0 BUS: new range size 1 align 1 flags 0 pciBridgeCheckConfiguration(bus 6, state 0) Checking PCI bus 6 BIOS config retained pciBridgeCheckConfiguration(bus 8, state 0) Checking PCI bus 8 MEM: new range size 200000 align 100000 flags 1 PFM: new range size 0 align 100000 flags 0 I/O: new range size 1000 align 1000 flags 1 BUS: new range size 2 align 1 flags 1 PCI configuration changed (bridge=2 device=14 yenta=1) IOPCCard info: Mac OS X PCMCIA Card Services 3.1.22 IOPCCard info: options: [pci] [cardbus] [pnp] AppleIntelPIIXPATA: Secondary PCI IDE channel is disabled IOPCCard info: Intel PCIC probe: IOPCCard info: O2Micro OZ711SP1 rev 01 PCI-to-CardBus phys mem 0x80100000 virt mem 0x34bf1000 IOPCCard info: host opts [0]: [pci/way] [pci irq 19] [lat 64/64] [bus 4/4] IOPCCard info: PCI card interrupts, PCI status changes Ioreg for the Dell 1390 MiniPCI-E card: +-o PXS3@0 <class IOPCIDevice, registered, matched, active, busy 0, retain 8> | | | { | | | "IOPCIResourced" = Yes | | | "IOInterruptControllers" = ("io-apic-0","IOPCIMessagedInterruptController") | | | "IOName" = "pci14e4,4311" | | | "subsystem-id" = <07000000> | | | "IOPCIExpressLinkCapabilities" = 222225 | | | "class-code" = <00800200> | | | "IOPowerManagement" = {"CurrentPowerState"=2} | | | "revision-id" = <01000000> | | | "IOInterruptSpecifiers" = (<1200000007000000>,<0600000000000100>) | | | "assigned-addresses" = <1000018200000000000000f00000000000400000> | | | "IOChildIndex" = 1 | | | "built-in" = <00> | | | "acpi-device" = "IOACPIPlatformDevice is not serializable" | | | "device-id" = <11430000> | | | "vendor-id" = <e4140000> | | | "acpi-path" = "IOACPIPlane:/_SB/PCI0@0/RP03@1c0002/PXS3@0" | | | "subsystem-vendor-id" = <28100000> | | | "name" = "pci14e4,4311" | | | "IOPCIExpressLinkStatus" = 4113 | | | "reg" = <0000010000000000000000000000000000000000100001020000000000000000000000000040 000> | | | "compatible" = <"pci1028,7","pci14e4,4311","pciclass,028000"> | | | } Can you see anything that would help me get Wifi working correctly? From what I can gather the card is correctly detected and it is something misconfigured with the PCI-E bus that prevent it from being powered up and visible. Dmesg.rtf Ioreg_l.rtf Hope that you can help me out. If I forgot any important info that could help you please let me know Thank you!
  6. Atheros (Visible on PSX3) not powering up?

    Hi Ferret-Simpson, I've been lurking here for ages, actually did my first Hackintosh install way back when the first intel build was leaked as a VMware image. OSx86project was only a wiki back then, these forums didn't exist Anyway I decided to register here to help the cause and get some answers for myself. I'm starting here because we have common ground with the Fujitsu laptop / tablet line. I've recently acquired a Fujitsu P1620 and installed Kalyway 10.5.1 on a separate partition. Some things work immediately after the base install, many do not. With the help of info collected throughout these forums I have gotten Networking, Audio, and Power features active. Wifi is still not working. I'll start a new thread devoted to how to get the P1620 fully functional soon. On to the wireless issue- the P1620 uses an Atheros chipset as well, which appears to be similar to a standard issue Mac PCI-E card. My card is detected on boot, and I also get the "loaded unsuccessfully" blurb. The funny thing is if I try kextload in terminal it claims to load successfully, but I don't see any indications of it other than in System Profiler. What is even more strange is my unit has Bluetooth, which is (to the best of my knowledge, looking at service manuals) integrated on the same Mini PCI-E card that the Wifi is on, and that is detected, loaded, and functional. Have you made any progress on yours? I would like to help out if possible on other fronts too. My Mac-Fu is weak presently, but I have years of PC based programming experience (including disassembly and tracing of accelerometer functions on my older Fujitsu P1610, which I've used to create some cool test apps on the PC). Ideally I'd like to get Wifi working, the HIDs working for my screen buttons, and modify the HID for the Touch Screen (which actually detects and works out of the box, but calibration is way off with no way to adjust it). Some cool extras would be to get Accelerometer data feedback into OSX, and get the SD card reader working. Let me know what you've accomplished so far. Thanks!
×