Kanga + 10.2.8 = Loss of ADB |
October, 11, 2003 4:42 PM |
Tom_Barrett |
OK now I'm mad..... I've been running 10.2.x on this machine since EPF 2.2 came out without any unexpected problems. You know the usual stuff, Sound in/out etc. So, I installed the first 2.8 over 2.6 when it came out, still NO problems, except I lost PC Cards. No problem, I replaced the new IOPCCardFamily.kext with the 2.6 one. PC Cards back better than ever. Then about 4 or 5 days later I started the machine and found that the keyboard and mouse (Kensington ADB Orbit) wouldn't work. I tried EVERYTHING, and found that they also refused to work when booted from the CD, WTF! This has never happened! I clauked it up to the infamous 10.2.8. Problem was, I couldn't reinstall! The frickin' mouse or track-pad and keyboard wouldn't work when booting from the CD. I don't know what fixed it, two or three dozen resets/flashes and a day later, I remembered that the only difference was that I had replaced the Pram battery recently. I disconnected it. Finally I recovered the use of my ADB. I did a COMPLETE reinstall to 10.2.6. This time I reformatted my external SCSI drive and cloned the 10.2.6 disk to it. I was happy, two disks with a perfectly working 10.2.6. Then along comes the NEW 10.2.8.... Sunday I decide to try it again, only this time I'll leave the clone alone. No problems, except for the IOPCCardFamily.kext thing. Working great, 'TILL TODAY! Same exact thing, I boot the machine and NO mouse, track-pad or keyboard. I later realized that the Pram had been flashed, the date was back to 8/19/72. I DIDN"T DO IT! The main battery has never run down or been removed. Not only that, the 10.2.6 disk and CD have the exact same problem, AGAIN! From the verbose start up it says something like 'ADB present but read or write failed'. Why? I kinda lost it, ran down to the closest store, and bought a SIIG USB2/FW PC Card (only one they had). Yep, I was right, my USB Logitech trackball works fine on both systems. I'm sure my PMG4s USB keyboard will work also (haven't tried it yet). So now what? I'm sure this is some sort of Pram/Open firmware Voodoo, but where did it come from? Any suggestions on how to get my ADB back? I'm not going to do a thing 'till I come up with a game plan. I don't want to trash a perfectly working system again until I can figure out how to fix it or avoid it. Did Apple jump the gun on pulling the plug on ADB Macs? Suggestions please...... Tom |
. |
RE: Kanga + 10.2.8 = Loss of ADB |
October, 24, 2003 11:39 AM |
lyonsdj88 |
. |
No clue, but if the trouble is gone then it looks like the mouth of the gift horse. |
. |
Seems to be Fixed? |
October, 24, 2003 7:55 AM |
Tom_Barrett |
. |
Hey guys, Check the date. It's been almost 7 days and still ticking.... Now I'm interested in this "AppleFlashNVRAM.kext" thing. Anyone know what this extension does? My Kanga doesn't appear to miss it at all..... Thanks, Tom |
. |
RE: Kanga + 10.2.8 = Loss of ADB |
October, 17, 2003 4:06 PM |
Tom_Barrett |
. |
Nope, no LAN. I went back and tried it again, this time I held the CM-OP-P-R for 5 bongs. Date/Time/StartUp CP unchanged, used XPF to boot to X, the first time it said; 0 0 1 ck if 0 and else dup 1 = if 3d 0 1 else f 3d 0 2 then ck if 40 or then the40 and if bye else 11 $I helpb 1e 0 do ['] boot catch drop 1f4 ms loop then 0 $Iunselect-dev $LLover $X $X ;em 7F00 + 4 -7E8D88 $X ; Everytime after it said; unselect-dev $LLover $X $X ;em 7F00 + 4 -7E8D88 $X ;h drop 1f4 ms loop then 0 $I bye ; So, I rebooted without XPF, EVERYTIME I tested it said; 0 0 1 ck if 0 and else dup 1 = if 3d 0 1 else f 3d 0 2 then ck if 40 or then the40 and if bye else 11 $I helpb 1e 0 do ['] boot catch drop 1f4 ms loop then 0 $Iunselect-dev $LLover $X $X ;em 7F00 + 4 -7E8D88 $X ; So, I rebooted to 9 again and rebooted using XPF. EVERYTIME I tested it it gave the long version. It continues to show only the long version now. Strange..... |
. |
RE: Kanga + 10.2.8 = Loss of ADB |
October, 17, 2003 12:43 PM |
lyonsdj88 |
. |
Could just be NVRAMrc file. I think that is @ line #2 bring the terminal to full size and see if it's just a fluke of not enough space to give the full text. AS to 9 if you were on a LAN that is on the net then when you booted OS 9 it checked the date and time network server and set your time as it was booting, if not then????????????? Did you remove the appleflashnvram.kext, if so wait 4 days and see if that helped. I don't know, just shooting in the dark. |
. |
RE: Kanga + 10.2.8 = Loss of ADB |
October, 17, 2003 1:25 AM |
Tom_Barrett |
. |
This is getting stranger and stranger. So, I booted into 9.2.2 (9 Helper), checked the Startup CP, shutdown. Hit the power button and held down Command & Option, P & R for three bongs, then held down the option key to make sure it booted back to 9. Time, Date, and Startup CP were unchanged. No apparent difference. I then used XPF 2.2.5, I had been using 3b up 'till this last clean install, to boot back to X. Line two has changed. The first time line two was; 40 and if bye else 11 $I helpb 1e 0 do ['] boot catch drop 1f4 ms loop then 0 $I bye unselect-dev $LLover $X $X ;em 7F00 + 4 -7E8D88 $X ; Now line two is; 0 0 1 ck if 0 and else dup 1 = if 3d 0 1 else f 3d 0 2 then ck if 40 or then the40 and if bye else 11 $I helpb 1e 0 do ['] boot catch drop 1f4 ms loop then 0 $Iunselect-dev $LLover $X $X ;em 7F00 + 4 -7E8D88 $X ; I went back and ran it again to check something and it said; unselect-dev $LLover $X $X ;em 7F00 + 4 -7E8D88 $X ;h drop 1f4 ms loop then 0 $I bye ; So, I ran it again; 0 0 1 ck if 0 and else dup 1 = if 3d 0 1 else f 3d 0 2 then ck if 40 or then the40 and if bye else 11 $I helpb 1e 0 do ['] boot catch drop 1f4 ms loop then 0 $Iunselect-dev $LLover $X $X ;em 7F00 + 4 -7E8D88 $X ; I'm really scratching my head about now.... It appears to alternate between the last two..... I haven't a clue...... WTF? |
. |
RE: Kanga + 10.2.8 = Loss of ADB |
October, 17, 2003 12:20 AM |
lyonsdj88 |
. |
code-debug? false 40 and if bye else 11 $I helpb 1e 0 do ['] boot catch drop 1f4 ms loop then 0 $I bye unselect-dev $LLover $X $X ;em 7F00 + 4 -7E8D88 $X ; screen- #rows 40 ..............That part is odd the rest seems as it should be. Command+option+p+r should work on your mac try it after you boot OS 9 not while it is set to boot OS X. If it won't work then you MAY have a HardWare trouble. I'd boot OS 9 shutDown zap the Pram 3 times, boot back to OS 9 qnd use XFP to boot back to OS X and nvram -p and post back if the part listed as odd is changed. Could mean nothing as that Mac is one of a kind. If you can't zap the PRam after a 9 boot then that pram battery may need to go. I could be wrong ,but I think All PM's with Open FirmWare Have to be able to use Command+Option+p+r. |
. |
RE: Kanga + 10.2.8 = Loss of ADB |
October, 16, 2003 11:40 PM |
Tom_Barrett |
. |
Yes, "something is messing with your NVRAM", that's my exact feelings. And it appears that the old 'command+option+p+r' doesn't do a thing on this machine. Before and during the reinstall today, I must have tried com+op-P-R at least a dozen times and the Time&Date never changed. It appeared that nothing changed. About the only way to really zap it is to disconnect ALL power for a while. Well, the PBG3's nvram setting is very different than the FW800 PM's settings, I haven't a clue what they mean. It appears my PB has a secret Lover? Here's what the terminal says about the NVram setting: Last login: Thu Oct 16 15:29:18 on ttyp1 Welcome to Darwin! [TomsPBG3:~] tom% nvram -p fcode-debug? false 40 and if bye else 11 $I helpb 1e 0 do ['] boot catch drop 1f4 ms loop then 0 $I bye unselect-dev $LLover $X $X ;em 7F00 + 4 -7E8D88 $X ; screen-#rows 40 boot-file oem-banner boot-command 0 bootr -v oem-logo real-size 0x100000 virt-base -1 boot-args -v input-device output-device boot-device ata0/@0:9 diag-switch? false screen-#columns 100 auto-boot? true oem-logo? false diag-file oem-banner? false load-base 0x600000 selftest-#megs 0 real-base -1 virt-size 0x100000 little-endian? false pci-probe-list -1 diag-device use-nvramrc? true real-mode? false [TomsPBG3:~] tom% Maybe someone can make sense of this? Seems like an awful lot of stuff in line 2 ....... |
. |
RE: Kanga + 10.2.8 = Loss of ADB |
October, 16, 2003 10:40 PM |
lyonsdj88 |
. |
NVRAM=PRAM FlashNVRam=command+option+p+r. I have no clue what that kext does, but from what you have said it sounds like something is messing with you NVRAM settings. To see them in OS X goto the terminal and type:nvram -p(return) that will print the NVRAM setting. |
. |
RE: Kanga + 10.2.8 = Loss of ADB |
October, 16, 2003 2:46 PM |
Tom_Barrett |
. |
OK, AppleFlashNVRAM.kext. Yes that's a new one, it's not in 2.6. It looks like there are a few new ones in 2.8. Well, I forgot what a NVRAM does, and why would Apple want to Flash mine all of a sudden? Hmmm...... Well, I've already done a fresh install of 2.8. I did find out about the 'Bad Bridge Bus Numbering' thing. It's definitely about the PCMCIA slots, and it appears the first time you boot with a PC Card inserted. After that, it appears every time you boot, with or without a card inserted. Seeing as how I have a fresh 2.8, I'm just going to delete the AppleFlashNVRAM.kext and see what happens. Thanks, I'll be back...... |
. |
RE: Kanga + 10.2.8 = Loss of ADB |
October, 16, 2003 10:37 AM |
lyonsdj88 |
. |
I'd revert to 10.2.6 and wait 5days or so. See if the trouble comes back if so blame it on 10.2.8. Look at a kext called AppleFlashNVRAM.kext. |
. |
RE: Kanga + 10.2.8 = Loss of ADB |
October, 16, 2003 7:13 AM |
Tom_Barrett |
. |
Bump. Just thought I'd report back. 4 days since last fix, it's doing it again...... Haven't loss ADB yet but it's displaying the other symptoms. Anyone wanna guess why it works for 4-5 days then goes poof? |
. |
RE: Kanga + 10.2.8 = Loss of ADB |
October, 12, 2003 6:12 PM |
Tom_Barrett |
. |
About two months. The only reason I replaced it was I thought it might help the system clock in 9. Grasping at straws..... Now I find out that it's normal for the clock in 9 not to work on this machine with X installed. I've since found my own cure. After booting to 9, put it to sleep. After waking up, the clock works fine in 9. I didn't need to mess with the battery, it didn't help a thing.... Well, everything works great again. The 10.2.8 system on the internal drive acts like nothing ever happened. I ran the 6R73 10.2.8 Combo installer again on it just for good measure. Let's see what happens in 5 days. I need some way to NUKE the Pram as traditional methods don't work very well. Oh, now I have USB on this machine, the Firewire part's a little flakey but appears to work for video, as if I needed video on the old machine ;-). The USB part is nice though.... |
. |
RE: Kanga + 10.2.8 = Loss of ADB |
October, 12, 2003 9:41 AM |
lyonsdj88 |
. |
How long after the Pram battery was replaced did this trouble start? |
. |
RE: Kanga + 10.2.8 = Loss of ADB |
October, 12, 2003 12:55 AM |
Tom_Barrett |
. |
Well as someone else here mentioned, it does get a little confusing..... The first time was using the 40MB 'OLD' download from Apple onto a few month old 10.2.6. The only problem was the loss of ADB after about 5 days. The second time was with the NEW 97MB Combo (6R73) downloaded from Apple last Saturday night, the latest and greatest, installed on a TWO day old brand new CLEAN 10.2.6 install. The only problem was loss of ADB after about 5 days. See a pattern here? Apparently whatever it is, it's affecting the Open firmware, or whatever, of the machine. Ok, I just did an Archive and install on the SCSI 10.2.6 cloned system. After the first 10.2.0 disk the machine rebooted and said CAN'T BOOT FROM THIS DEVICE! Blue screen with ugly slashed circle appeared and hung.....WTF.....Booted back to 9, restarted to the 10.2.8 disk, installed the 10.2.6 Combo update on the SCSI, rebooted back to the SCSI disk, machine hung twice at the bright grey screen. I then proceeded to Force reboot and flashed the Pram about five times. Then the machine booted to the SCSI drive and nonchalantly stated, ' You need to finish the install from disk two ". The ADB now WORKS again. WTF...... Sorry for my french but I've about had it..... for tonight anyway ;-} |
. |
RE: Kanga + 10.2.8 = Loss of ADB |
October, 11, 2003 11:32 PM |
powderhaus |
. |
If you are talking about the first OS 10.2.8 update you should go to apple.com and download the new one, or i think htere is a patch for it. There waere many problems with the first 10.2.8 update and I think that ADB was part of teh problem list, i never had a problem with it but i use a USB set up. |
. |
RE: Kanga + 10.2.8 = Loss of ADB |
October, 11, 2003 10:33 PM |
Tom_Barrett |
. |
I tested the Pram batteries, calls for 7.2v, old one never gave any trouble is 3.4v, new one is 7.8v. And remember, the last thing I did before the ADB returned was to disconnect the battery and leave it disconnected. What the heck, it was working fine on the almost dead OEM and a little zapping never hurt a Pram anyway. Something DID hurt the Pram and I don't think it was just a little zap. Before, when everything was fine, I never had to use XPF to boot into X after it installed. In fact, the only way not to boot into X was to hold down the option key when you wanted 9. Now, you have to boot into 9 EVERY time and use XPF to boot into X. If you don't, the machine hangs at the bright grey screen just before the Apple appears. I'm using XPF 3.04b and reinstalling the XPF goodies doesn't help. I removed all power, including the Pram battery for two hours. Then reconnected the Pram battery, inserted main battery and connected external power. the machine immediately bonged and booted into 9 on it's own. The date was set to 1904, I'm pretty sure the Pram was cleared however, it still won't load ADB in X. OS 9.2 was never a problem. Something is still corrupt or whatever. New message on verbose boot. Now immediately after "Recording startup extensions" it states, "AppleMacRiscPCI: bad bridge bus numbering, no room to fix, bailing out!" This is new, anyone want to explain what it means (I've got my suspicions), and possibly a fix? It no longer mentions ADB. Then it repeats the old "Warning AppleMacIO self test fails" and goes on and on about the IOPCCard Info, this is normal. The bridge bus error has to be part of the problem, if I only knew what a bridge bus numbering was........ :-{ |
. |
Pram battery? |
October, 11, 2003 7:32 PM |
lyonsdj88 |
. |
could be you got a bad one, look hard at it. Other wise see my New 10.2.8 don't do it tread:p |