Hey Leif, That's a good news! Where did you get the 64bit Windows driver? Please post the link to it, if possible.
Thanks, Michael Leif Haldorsen wrote: > Michael wrote: > ...NDIS1.1 can not support bcm4318 in 64bit mode, but 32bit mode. This > ..issue has nothing to do with APIC. > > ...- Michael > > Hey Michael. > I'm running my bcm4318 in 64bit bode as well as in 32 bit mode without any > problem. the trick was to use NDIS 1.1 to make the drivers from 64bit mode, > then to reboot into 32bit mode and install the 32bit drivers with add_drv, > and after that to copy the 64bit files into their locations. > I will clam that it is possible to use NDIS1.1 for to run the wifi in 64bit > mode because I am doing that without any problem. I can post the routine for > to make it working if you need it. Great, please post the routine. > > > Hey James > >> Check the BIOS for an option to disable APIC. or remap the resources >> manually if you can figure out which interrupt is causing it, and it >> might solve the issue. > > Thanks for your answer. Of cause I know about APIC in general, and i also had > an idea about turning off the APIC from BIOS, but this is NOT POSSIBLE in my > laptop. Also, i can NOT change any interrupts from bios. My BIOS do not give > me any help for this problem. > >> Basically it's related to context switching, changing the execution >> state of hardware for multitasking and symmetric multi-processing operation. > > you say it has to do with the context switch, then i can suspect to run into > deadlock in some situations!? Now I'm wondering about how Solaris handle > this. The error messages will pop up in the booting sequence just after the > line: use is subjected to license terms. > Like this: > .... > use is subjected to license terms. > APIC Error interupt on CPU 0. Status 0 =0. Status 1 = 40. (*one > to four lines like this*) > Hostname : sol11 > NDIS Api version 5.11 > .... > > The computer do not show any sign of being going to deadlock or in other ways > to running slow. > > As we can see, the OS has found this problem, but what did it do with it -- > did solaris handle this on its own?? HOW do the error handling routines in > solaris handle this? is it solved or is it unsolved?? > > My AMD Turion64 is a single core processor > > >> Disabling SMP by passing a kernel parameter will almost always fix the issue >> but this is a >workaround, the only way to get it fixed is wait, or do it >> yourself. Some motherboards >> have flaky APIC's. (Southbridge chipset) You wont have dual-core >> functionality if you disable >APIC. > > Of cause I can manage to find this kernel parameter and how to send it to the > kernel, but this will take me a days work - i am new in solaris - so if you > can post one example you will give me a big help. > > best regards > lehaldor > > > This message posted from opensolaris.org > _______________________________________________ > laptop-discuss mailing list > laptop-discuss at opensolaris.org
