Jump to content
3411 posts in this topic

Recommended Posts

Testing Rel 860.

 

I have found this:

I have a bluetooth native tied to my wireless...if i push the switch to turn off the wireless, the bluetooth is disabled too, some times it gives errors on load...so you adviced me to uninstall the driver to avoid interferences, ok, did it, but now i have much more errors cause seems the firmware is looking for his missing brother and give this errors

(greatest bluetooh hits recopilation).

 

Can you check if the BLuetooth brothership code is correct? or better separate them forever? :offtopic:

 

 

Apr 27 01:55:33 Pere kernel[0]: iwl3945: U iwl3945_send_cmd_sync Wait REPLY_BT_CONFIG Condition: 0ms left

Apr 27 01:55:33 Pere kernel[0]: error iwl3945: Error sending REPLY_BT_CONFIG: time out after 500ms.

Apr 27 01:58:31 Pere kernel[0]: iwl3945: U iwl3945_enqueue_hcmd Sending command REPLY_BT_CONFIG (#9b), seq: 0x0400, 16 bytes at 0[0]:4

Apr 27 01:58:31 Pere kernel[0]: error iwl3945: SYSASSERT (#5) 0001978490 0x0089A 0x00FE0 0x00304 0x00000 57iwl3945: U iwl3945_send_cmd_sync Wait REPLY_BT_CONFIG Condition: 47ms left

Apr 27 01:58:31 Pere kernel[0]: iwl3945: U iwl3945_send_cmd_sync Command REPLY_BT_CONFIG failed: FW Error

Apr 27 02:01:50 Pere kernel[0]: iwl3945: U iwl3945_enqueue_hcmd Sending command REPLY_BT_CONFIG (#9b), seq: 0x0400, 16 bytes at 0[0]:4

Apr 27 02:01:50 Pere kernel[0]: error iwl3945: Start IWL Error Log Dump:iwl3945: U iwl3945_send_cmd_sync Wait REPLY_BT_CONFIG Condition: 32ms left

Apr 27 02:01:50 Pere kernel[0]: iwl3945: U iwl3945_send_cmd_sync Command REPLY_BT_CONFIG failed: FW Error

Apr 27 02:01:53 Pere kernel[0]: iwl3945: U iwl3945_send_cmd_sync Wait REPLY_BT_CONFIG Condition: 49ms left

Apr 27 02:01:53 Pere kernel[0]: iwl3945: U iwl3945_send_cmd_sync Command REPLY_BT_CONFIG failed: FW Error

Apr 27 02:01:55 Pere kernel[0]: iwl3945: U iwl3945_send_cmd_sync Wait REPLY_BT_CONFIG Condition: 49ms left

Pere could you put 3945 860 kext please?

Im still downloading xcode (15kb/s on a 128k ISDN), so i cant compile yet...

 

Yep. Kext rel 860 attached.

 

Javalui ,i try to execute network selector and it crash, attached is the log from the crash too.

network_selector_crash.rtf

iwi3945.kext.zip

Here are my logs for 860:

It is completing scan

Apr 26 19:30:22 pabmacpro kernel[0]: iwl3945: U iwl3945_bg_scan_completed SCAN complete scan
Apr 26 19:30:22 pabmacpro kernel[0]: ieee80211_scan_completed

860log.txt

oke here's my log for latets iwi 4965... missing all the firmware and channel stuff, will try a reboot now to see if i get a full log.

 

 

ok after a reboot i got a better log... did some manual scanning and now see "Request scan" and then you can clearly see scanning log lines. :wacko:

system.txt

system2.txt

I've been checking in so often until I could help with the 4965, and it looks like that time has come. I'm a fairly advanced PC user, but a novice to OS X, so could anyone give me step by step directions for what I have to do to test this driver, or send me a link or something to where this is explained? I haven't been able to find anything so far.

 

Thanks,

Beeve

It's really nice to see the ongoing progress! Keep it up! :)

 

r861, iwi3945:

No kernel panics, I could work on my machine for about 45 minutes!

Scans successfully started at 11:44:39 and 11:47:43.

 

Logs are attached, as well as the kext.

iwi3945_r861.zip

dmesg_0.txt

dmesg_1.txt

ioreg.txt

system.txt

Testing 860

 

-x boot, then kextload, gives system_860-1.txt

 

No errors as the card starts. Seems to scan ok, although no SCAN_COMPLETE.

 

system860_1.txt

 

 

system.txt as logs for a normal boot. Often get FW errors as the card starts, however it seems to recover.

 

Many of the bssid addr are correct for the APs in my area.

 

I'm able to start a scan using network_selector, although I still don't get SCAN_COMPLETE

 

system.txt

Testing 860

 

I'm able to start a scan using network_selector, although I still don't get SCAN_COMPLETE

 

can you explainhow do you get this logs

looks like your card is the only that works

can you test the timer hack? - if this works without errors for you i'll add it to svn

I booted with -x.

 

Build the kext, kext_helper to install. Manual kextload.

 

 

Not sure if it makes any difference, but I have added the chunnan IOPCCard patch.

 

 

I haven't made any changes to 860. What timer hack would you like me to test?

I got fed up floundering about in the dark, so I've been working on getting 1.2.23 compiled with debug enabled on Linux.

 

After much faffing, rebuilding kernels etc. here's the result. :(

 

Hopefully it might be some use as a reference?

iwl4965_linux_syslog.txt

Hey all,

 

861 logs attached. init lines missign again. manual kextload. Looks like you all did a lot of work yesterday.

 

it looks like its scanning a little bit. oh and this is new:

 

Apr 27 09:21:42 Sony kernel[0]: iwl3945: U iwl3945_rx_handle r = 30, i = 29, REPLY_3945_RX, 0x1b

Apr 27 09:21:42 Sony kernel[0]: iwl3945: U iwl3945_rx_reply_rx Bad CRC or FIFO: 0x00000702.

 

Hope this log helps some. But, as you know, my card seems different than most.

 

861.txt

I booted with -x.

 

Build the kext, kext_helper to install. Manual kextload.

 

 

Not sure if it makes any difference, but I have added the chunnan IOPCCard patch.

 

 

I haven't made any changes to 860. What timer hack would you like me to test?

 

 

Go to the file iwi3945-base.c and look into for

 

//IOSleep(750);//hack

ret = UCODE_READY_TIMEOUT;

while(!(test_bit(STATUS_READY, &priv->status))) {

IOSleep(1);

ret--;

if(ret==0)

 

Erase the two black slash in the begining, save,build again, test... and give us good news!! :(

break;

I got fed up floundering about in the dark, so I've been working on getting 1.2.23 compiled with debug enabled on Linux.

 

After much faffing, rebuilding kernels etc. here's the result. :(

 

yes - i was asking for this since my 1st post

can you guys follow this example and do the same for 3945

 

mlazy,

Apr 27 09:21:43 Sony kernel[0]: iwl3945: U iwl3945_rx_scan_complete_notif Scan pass on 2.4GHz took 200ms

Apr 27 09:21:43 Sony kernel[0]: queue_te @ /Users/super/Desktop/iwi3945/861/compatibility.cpp:6535

Apr 27 09:21:43 Sony kernel[0]: test_function @ /Users/super/Desktop/iwi3945/861/compatibility.cpp:6524

Apr 27 09:21:43 Sony kernel[0]: iwl3945: U iwl3945_bg_request_scan Initiating indirect scan.

Apr 27 09:21:43 Sony kernel

this mean the scan complete and started a loop

nice :(

 

 

the Cxddev linux log is similar for 3945/4965

inspired by this i'm going to change the code

wait...

 

you can get a kp with this

i'm not shore if i write the same code for both versions - i'll see it in logs

try to get first drive log lines - very important in this release

 

iwi3945 rel 862

iwi4965 rel 863

I booted with -x.

 

Build the kext, kext_helper to install. Manual kextload.

Not sure if it makes any difference, but I have added the chunnan IOPCCard patch.

I haven't made any changes to 860. What timer hack would you like me to test?

 

He bobobear, can you tell me what you did to get your 02micro device installed? was ist only iopcifamily and iopccardfamily from chun nan, or somthing more

 

 

Sorry for OT, please pm me.

I've been trying 860 with and without the IOSleep(750) hack

 

Initially with hack in place.

 

IOSleep(750);//hack

ret = UCODE_READY_TIMEOUT;

 

log shows kextload from -x boot, followed by normal boots at 15:57 and 16:00

 

Lots of MicroCode errors with second normal boot, but log does mention starting indirect scans.

 

Manual scans from network_selector result in "Scan already in progress"

 

 

 

Removed hack

 

//IOSleep(750);//hack

ret = UCODE_READY_TIMEOUT;

 

-x boot at 16:05 followed by kextload, 16:18 normal reboot. Both show lots of Microcode errors again.

 

manual scan now starts scan.

 

Hope this helps.

 

system.txt.zip

oke logs for 4965 rel 863

 

It seems like i only getting a completer log when starting after i removed all power :rolleyes:

 

 

o jalavoui,, because of my reinstall, now the network is know as eth0 does that still matter or should it be eth1?

system.txt

HowTo build iwl3945/iwl4965 in Linux

 

You'll need the debian 2.6.22 kernel and source - I couldn't get it to work with ubuntu or newer versions.

 

		   sudo aptitude install linux-headers-`uname -r` linux-source-2.6.22

	   #Unpack the source in /usr/src
	   cd /usr/src
	   sudo tar jxf linux-source-2.6.22.tar.bz2

	   #Link modules directory to the source
	   sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/`uname -r`/source 

	   #Get the iwl source
	   wget http://www.intellinuxwireless.org/iwlwifi/downloads/iwlwifi-1.2.23.tgz 
	   tar zxf iwlwifi-1.2.23.tgz
	   cd iwlwifi-1.2.23
	   make

	   #Get and install firmware
	   wget http://www.intellinuxwireless.org/iwlwifi/downloads/iwlwifi-3945-ucode-2.14.1.5.tgz
	   tar zxf iwlwifi-3945-ucode-2.14.1.5.tgz
	   sudo cp iwlwifi-3945-ucode-2.14.1.5/iwlwifi-3945.ucode /lib/firmware/iwlwifi-3945-1.ucode

	   #Load module with debug enabled
	   sudo modprobe mac80211
	   sudo insmod ./iwlwifi-1.2.23/compatible/iwl3945.ko debug=0x43fff

Guest
This topic is now closed to further replies.
×
×
  • Create New...