Vikas Sharma ??: > > Brian, > > The script did not do any changes to the current situation. Any other > idea? > 1. Command login as root
>>>>>means exit the graphic login (Alt+Crtl+Backspace) and then select the command line login 2. #rem_drv iwk 3. #mdb -KF >>>>>this makes the system into 'kmdb', then you have a '>' prompt. 4. >20::wrpcicfg 00 1c 03 f030f030 5. >4::wrpcicfg 00 1c 03 100046 6. >10::wrpcicfg 06 00 00 f0300000 7. >4::wrpcicfg 06 00 00 100046 >>>>>run 4-7 in 'kmdb'. 8. >:c >>>>>this makes the system exit 'kmdb' 9. #add_drv -i '"pciex8086,4229" "pciex8086,4230"' iwk After step9, you can exit the command line login shell(run 'exit') and the system will automatically makes you enter the graphic login. Then maybe the wifi can work. Even the wifi works, you have to run the above each time the machine reboots. Any other questions, let me know pls. Thanks, Brian > Thanks, > > Vikas > > # ./iwk_bdg_workaround.ksh > > Warning: Your system may hit CR6419924. For detail, See > > "http://bugs.opensolaris.org/view_bug.do?bug_id=6419924"; > > This script tries to give you a workaround. > > Note: You have no 'pcitool' on your system. If you are > > SUN internal user and can access SWAN, Pls get one at > > "/ws/onnv-gate/proto/root_i386/usr/sbin/pcitool", > > and put it under /usr/sbin/, then an autorun script > > would work for you, otherwise, you have to manually > > enter 'kmdb' to hack your system each time it reboots. > > steps for 'kmdb' hack: > > 1. Command login as root > > 2. #rem_drv iwk > > 3. #mdb -KF > > 4. >20::wrpcicfg 00 1c 03 f030f030 > > 5. >4::wrpcicfg 00 1c 03 100046 > > 6. >10::wrpcicfg 06 00 00 f0300000 > > 7. >4::wrpcicfg 06 00 00 100046 > > 8. >:c > > 9. #add_drv -i '"pciex8086,4229" "pciex8086,4230"' iwk > > Try wifi as usual after you do the above! > > Any questions, pls contact [EMAIL PROTECTED] > > # > > # > > # > > # rem_drv iwk > > # > > # mdb -KF > > # > > # > > # > > # > > # te > > # mdb -KF > > 20::wrpcicfg 00 1c 03 f030f030 > > 4::wrpcicfg 00 1c 03 100046 > > 10::wrpcicfg 06 00 00 f0300000 > > 4::wrpcicfg 06 00 00 100046 > > :c# 20::wrpcicfg: not found > > # 4::wrpcicfg: not found > > # 10::wrpcicfg: not found > > # 4::wrpcicfg: not found > > # > > :c: not found > > # > > # > > # mdf b -KF > > # > > # > > # > > # > > # add_drv -i '"pciex8086,4229" "pciex8086,4230"' iwk > > # > > # ifconfig -a > > lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu > 8232 index 1 > > inet 127.0.0.1 netmask ff000000 > > lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu > 8252 index 1 > > inet6 ::1/128 > > # > > # ifconfig -a plumb > > # > > # ifconfig -a > > lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu > 8232 index 1 > > inet 127.0.0.1 netmask ff000000 > > iwk0: flags=201000802<BROADCAST,MULTICAST,IPv4,CoS> mtu 1500 index 2 > > inet 0.0.0.0 netmask 0 > > ether ff:ff:ff:ff:ff:ff > > lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu > 8252 index 1 > > inet6 ::1/128 > > # > > # wificonfig -i iwk0 scan > > essid bssid type encryption signallevel > > # > > # > > # > > # tail -50 /c var/adm/messages > > Apr 10 21:30:28 punix mac: [ID 736570 kern.info] NOTICE: iwk0 unregistered > > Apr 10 21:38:12 punix pcplusmp: [ID 444295 kern.info] pcplusmp: ide > (ata) instance #1 vector 0xf ioapic 0x1 intin 0xf is bound to cpu 0 > > Apr 10 21:38:12 punix unix: [ID 954099 kern.info] NOTICE: IRQ19 is > being shared by drivers with different interrupt levels. > > Apr 10 21:38:12 punix This may result in reduced system performance. > > Apr 10 21:38:12 punix mac: [ID 469746 kern.info] NOTICE: iwk0 registered > > Apr 10 21:38:28 punix iwk: [ID 425513 kern.warning] WARNING: > iwk_init(): failed to setup boot firmware > > Apr 10 21:38:28 punix last message repeated 1 time > > Apr 10 21:38:28 punix iwk: [ID 871236 kern.warning] WARNING: > iwk_init(): failed to load firmware > > Apr 10 21:38:29 punix iwk: [ID 425513 kern.warning] WARNING: > iwk_init(): failed to setup boot firmware > > Apr 10 21:38:29 punix last message repeated 1 time > > Apr 10 21:38:29 punix iwk: [ID 871236 kern.warning] WARNING: > iwk_init(): failed to load firmware > > Apr 10 21:38:31 punix iwk: [ID 425513 kern.warning] WARNING: > iwk_init(): failed to setup boot firmware > > Apr 10 21:38:31 punix last message repeated 1 time > > Apr 10 21:38:31 punix iwk: [ID 871236 kern.warning] WARNING: > iwk_init(): failed to load firmware > > Apr 10 21:38:34 punix iwk: [ID 425513 kern.warning] WARNING: > iwk_init(): failed to setup boot firmware > > Apr 10 21:38:34 punix last message repeated 1 time > > Apr 10 21:38:34 punix iwk: [ID 871236 kern.warning] WARNING: > iwk_init(): failed to load firmware > > Apr 10 21:38:37 punix iwk: [ID 425513 kern.warning] WARNING: > iwk_init(): failed to setup boot firmware > > Apr 10 21:38:37 punix last message repeated 1 time > > Apr 10 21:38:37 punix iwk: [ID 871236 kern.warning] WARNING: > iwk_init(): failed to load firmware > > Apr 10 21:38:41 punix iwk: [ID 425513 kern.warning] WARNING: > iwk_init(): failed to setup boot firmware > > Apr 10 21:38:41 punix last message repeated 1 time > > Apr 10 21:38:41 punix iwk: [ID 871236 kern.warning] WARNING: > iwk_init(): failed to load firmware > > Apr 10 21:38:46 punix iwk: [ID 425513 kern.warning] WARNING: > iwk_init(): failed to setup boot firmware > > Apr 10 21:38:46 punix last message repeated 1 time > > Apr 10 21:38:46 punix iwk: [ID 871236 kern.warning] WARNING: > iwk_init(): failed to load firmware > > Apr 10 21:38:51 punix iwk: [ID 425513 kern.warning] WARNING: > iwk_init(): failed to setup boot firmware > > Apr 10 21:38:51 punix last message repeated 1 time > > Apr 10 21:38:51 punix iwk: [ID 871236 kern.warning] WARNING: > iwk_init(): failed to load firmware > > Apr 10 21:38:56 punix iwk: [ID 425513 kern.warning] WARNING: > iwk_init(): failed to setup boot firmware > > Apr 10 21:38:56 punix last message repeated 1 time > > Apr 10 21:38:56 punix iwk: [ID 871236 kern.warning] WARNING: > iwk_init(): failed to load firmware > > Apr 10 21:39:02 punix iwk: [ID 425513 kern.warning] WARNING: > iwk_init(): failed to setup boot firmware > > Apr 10 21:39:02 punix last message repeated 1 time > > Apr 10 21:39:02 punix iwk: [ID 871236 kern.warning] WARNING: > iwk_init(): failed to load firmware > > Apr 10 21:39:08 punix iwk: [ID 425513 kern.warning] WARNING: > iwk_init(): failed to setup boot firmware > > Apr 10 21:39:08 punix last message repeated 1 time > > Apr 10 21:39:08 punix iwk: [ID 871236 kern.warning] WARNING: > iwk_init(): failed to load firmware > > Apr 10 21:39:15 punix iwk: [ID 425513 kern.warning] WARNING: > iwk_init(): failed to setup boot firmware > > Apr 10 21:39:15 punix last message repeated 1 time > > Apr 10 21:39:15 punix iwk: [ID 871236 kern.warning] WARNING: > iwk_init(): failed to load firmware > > Apr 10 21:39:23 punix iwk: [ID 425513 kern.warning] WARNING: > iwk_init(): failed to setup boot firmware > > Apr 10 21:39:23 punix last message repeated 1 time > > Apr 10 21:39:23 punix iwk: [ID 871236 kern.warning] WARNING: > iwk_init(): failed to load firmware > > Apr 10 21:39:31 punix iwk: [ID 425513 kern.warning] WARNING: > iwk_init(): failed to setup boot firmware > > Apr 10 21:39:31 punix last message repeated 1 time > > Apr 10 21:39:31 punix iwk: [ID 871236 kern.warning] WARNING: > iwk_init(): failed to load firmware > > Apr 10 21:39:39 punix iwk: [ID 425513 kern.warning] WARNING: > iwk_init(): failed to setup boot firmware > > Apr 10 21:39:39 punix last message repeated 1 time > > Apr 10 21:39:39 punix iwk: [ID 871236 kern.warning] WARNING: > iwk_init(): failed to load firmware > > # > > # date > > Thu Apr 10 21:39:53 PDT 2008 > > # > > # > > # modinfo | grep iwk > > 155 fffffffff8719000 36e50 271 1 iwk (Intel(R) 4965AGN driver(N)) > > # > > # > > > > ----- Original Message ---- > From: Kerry Shu <[EMAIL PROTECTED]> > To: Vikas Sharma <[EMAIL PROTECTED]> > Cc: Brian Xu - Sun Microsystems - Beijing China <[EMAIL PROTECTED]>; > [email protected] > Sent: Thursday, April 10, 2008 9:13:27 PM > Subject: Re: [networking-discuss] Problems in configuiring wireless > networking > > Hi, > > My fix for pci_autoconfig is in snv_b87. Pls have a try when snv_87 > comes out. > > Thanks, > Kerry > > Brian Xu - Sun Microsystems - Beijing China wrote: > > Vikas Sharma ??: > >> Hi Brian, > >> > >> Here is the output of "ifconfig -a", "prtconf -v" and "scanpci -v" > >> commands. > >> > > Yes. your system does hit the CR. > >> I also came to know that there is another version of iwk packages > >> version 1.1 released recently. Could you please, if possible, let me > >> know if this problem is fixed in that version? This one is available > >> at > >> > http://www.opensolaris.org/os/community/laptop/downloads/iwk-1.1-pkg.tar.gz > > >> > >> > >> > > The new version makes the connect more stable, especially for chip > > 'pci8086,4229', just as yours. However, the problem you encountered > is a > > pci bridge & boot bug, not an iwk driver one. So the new version has no > > relationship to the problem. > > > > The workaround I send to you tries to manually modify the pcie bridge > > configuration. > > > > I Cc this email to [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>, who > I think is working on the > > bugfix. Before the fix is available, you may try the workaround I send > > to you and follow the instructions the workaround prompt to you. > >> I will try to install this package also to check if it helps. In the > >> meantime, you can send me the workaround, if available. > >> > > You can directly pkgadd the new version of the iwk though it does not > > help to the current issue, then run the attached script and follow up > > according to the instructions the script prompts to you step by step. > > > > Any other questions, let me know pls. > > > > Thanks, > > Brian > >> Have a good day! > >> > >> Regards, > >> V > >> > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com _______________________________________________ networking-discuss mailing list [email protected]
