Here is the lspci from someone who managed to get linux to boot on one:
Looks like it might have a broadcom wireless chip after all?
On Feb 15, 2006, at 6:04 PM, themacuser wrote:
Can someone with an intel Mac do the following things: Open Terminal and type cd Desktop ioreg -l -w0 > ioreg.txt ls /System/Library/Extensions/ > extensions.txt system_profiler > sysprofile.txt
and attatch the three text files to an email (ioreg.txt, extensions.txt, sysprofile.txt - they should be on your desktop) , send them to the list (and to me if the list doesn't do attatchments, I'll host them in that case).
This will help us a lot in determining what hardware is in these Macs.
On 16/02/2006, at 11:10 AM, Geoffrey Kruse wrote:
Also, for those using usb devices, try
There were some endianess issues with the driver that have been fixed, but further testing is still needed.
On Feb 15, 2006, at 5:38 PM, Kevin Bringard wrote:
My guess is its doing this because its not using the same wireless card as the G4s. I heard that they were going to be using the intel pro wireless... but that was just a rumor last I heard *shrug*
On 2/15/06, Mike Williams <resu-cam@xxxxxxx> wrote: Hi,
the app starts without problems. AE active mode works well. AE passive mode does not work "Could not enable monitor mode - Drivers were not found"
Am 15.02.2006 um 22:22 schrieb Geoffrey Kruse:
> For those with an Intel Mac:
> This version is completely untested on an intel machine since I
> don't have one. Use at your own risk. Please let me know what
> works / doesn't. This information will help me continue with the
>> I have OSX86 10.4.3 running on a P4 Prescott and a DWL-122 USB Prism2
>> dongle if its any help.
>> Will get an iMac Core Duo in the near future.
>> On 2/15/06, Geoffrey Kruse < gkruse@xxxxxxxxxxxxxx> wrote:
>>> Please try the patch attached to ticket 15 in trac. It is probably
>>> really broken, but it does compile a universal binary fine for me.
>>> Feedback would be appreciated as I don't have an Intel mac to
>>> test on.
>>> On Feb 11, 2006, at 11:12 AM, Geoffrey Kruse wrote
>>>> Unfortunately, there are some other problems besides the cpu flag.
>>>> While the cpu flag can be set differently for different
>>>> architectures, there is some altivec specific code that somehow
>>>> needs to be addressed. Also, the atheros driver uses a binary only
>>>> hardware abstraction layer. This issue will also have to be
>>>> addressed. I am opening a ticket in trac for intel compilation,
>>>> however i expect it to take a fair amount of effort to get this to
>>>> On Feb 11, 2006, at 5:48 AM, Mike Williams wrote:
>>>>> Ahh - I tried to set it to x86 or something - without this option
>>>>> it works...
>>>>> _but_ nor I get this problem.
>>>>> I'm using a default installation of MacOS and developer-tools.
>>>>> I was able to build release 65 without problem - after 65 no build
>>>>> was compiled without problems.