Apple Pulls 10.2.8 Update
physicsnerd writes "Apple has apparently pulled the Mac OS X 10.2.8 update from Software Update. The standalone updates have also been pulled. There have been reports of problems with 10.2.8 on iMacs and eMacs." People have also reported network problems.
I finished the update earlier on my PowerBook G3 with no problems.
*knock wood*
Are we certain this is an [e|i]mac-specific issue?
El riesgo vive siempre!
By "all the bugs" I mean most of the big bugs...cause there seem to be some major bugs surrounding this update....
http://chrono.posterous.com/
I just installed the updates this morning on two computers. PowerMac Dual G4 1Ghz MDD and a PowerBook G4 550Mhz.
No problems, encountered but I installed the updates and ran a Repair Permissions afterwards.
The only problem:
The PowerMac screen saver went to sleep and would not wake up after the Software Update mandatory reboot. I had walked away from the machine after telling it to reboot and did not even login to it. It froze with the screen blanked. I ended up SSHing into it from another computer and doing a sudo shutdown -h now then powered it back up. This is when I ran the Repair Permissions.
The PowerBook was upgraded after this and it didn't have a single problem. I didn't have a chance to test it though.
Hope they roll out an updated 10.2.8 soon so whatever major bug(s) were let loose; would get reined in quickly.
Serves me right in not waiting 2 days before I applied the updates. Some were having problems but most were do to people running haxies.
As far as I know, the problem is limited to a few iMacs/eMacs. I have no problems on the iBook, powerbook g4, or powermac G4 in my house... all on 10.2.8. I would expect Apple to put it back up as soon as they fix the apparent failure, either through a modified 10.2.8 or a patch for the systems affected. This update is nothing all that exciting, so it's not a mistake that it ever went up. In other words, don't worry if you have 10.2.8. You'll be fine.
With one weird, but possibly-not-related, exception.
I did the 10.2.8 update on my G4 PowerMac. After the initial reboot and before I had a chance to actually do anything, my keyboard and mouse stopped responding. But a power cycle later and things seem to be working fine. I've since run a couple Classic apps (mainly the scanning software for a Canon), plus OS X Photoshop 7 and connected to a couple Samba shares on a Linux server. The only network connection is wired Ethernet.
I should have thought to try and ssh in before cycling the machine, but I didn't. So, for all I know it could have either been just the kb/mouse, or it could have been the entire machine, that froze up.
Baited breath huh? I updated a 1GHz G4 Powerbook and a WallStreet Powerbook today. Everything looks ok for now...
Quicksilver G4/933 running 100Base-T through DHCP:
I upgraded last night and then rebooted. Everything worked fine. Then this morning I suddenly lost all Internet access. Tried to renew the DHCP lease, and that failed. I rebooted and things are working (for now).
Other problems: The Firewall pane of the System Preferences says I already have a firewall running and therefore it will not let me change/configure it.
All in all, most OS X upgrades have been pretty problem-free for me. It sucks these things happen, and they should not happen, but...
Something else funny - right before the machine went down I was complaining on IRC about the new SSH patch and how I was going to have to take down my machine again for that.
- (c) 2018 Hank Zimmerman
My 17 inch powerbook was rendered useless overnight. Upon rebooting, the video display renedered the grey screen of death. Hopefully, doing an 'archive and install' and going back to 10.2.6 will fix my woes... At least they are doing the responsible thing and pulling the plug on it.
This may imply something important is broken in the OS, or in the latest Office. In either case, it's important for Apple to keep it working.
"We have temporarily removed the Mac OS X v10.2.8 software update while we resolve an issue affecting Ethernet networking on small number of Power Mac G4 desktop systems. We anticipate that the issue will be resolved soon," said the statement in its entirety.
The full article can be found here:2 8pulled/index.php?redirect=1064334986000
http://maccentral.macworld.com/news/2003/09/23/10
Physicsnerd
Like a lot of other people, this update seems to have completely screwed up ethernet networking for me. A lot of the reports I've read (Apple's site Slashdot comment, MacFixit article, MacSlash, etc) suggest that people with dual processor G4s running 400-500mhz are having a lot of problems, and a broken driver for the Intel gigabit ethernet chipset has been blamed -- though I haven't seen anything that conclusively says that this component is at fault. Other reports have come from people running faster G4s & PowerBooks, so if the Intel ethernet driver is a cause, it doesn't seem to be the only cause. All I can say personally is that my dual G4/450mhz is definitely messed up right now.
The best remedy I've seen so far is to restore the pre-10.2.8 version of the AppleGMACEthernet ethernet driver. If you can -- and for most people it'll be too late for this advice to do any good -- make a backup of the .kext driver before updgrading to 10.2.8, then use that to rebuild is things go awry. For everyone else, your best bet is to download it from Andrew McPherson's MIT site, either by establishing a dialup connection, by booting into OS9 and getting it from there, or by grabbing it with another machine and transferring it to your broken Mac by e.g. a burned CD, a Zip disc, etc.
Here are the repair steps, as slightly modified from McPherson's suggestion at Apple's site:
This advice is close to that which McPherson suggested, but he recommended deleting the broken driver, and the commands I give above make a backup just in case. If all goes well you may remove that ~/enet_backup directory, but I have a hunch that somehow you're going to have to end up re-installing it, so keeping a copy around seems prudent to me -- and it's not like it even takes up that much space (well under a megabyte).
Other people have reported success with other solutions. One proposal was to run the command "ifconfig en0 media autoselect", but in my case that didn't work. Others have suggested rebooting, zapping the PRAM a few times, then letting the machine boot again; others have said that that didn't work either.
Replacing the driver, as described above, seems to be the remedy that has had the most success for the most users -- but even still, it isn't working for everybody. In my case, it has allowed me to reconnect to my PPPoE/
DO NOT LEAVE IT IS NOT REAL
I have a MOTU 828 audio recording interface, and since i installed 10.2.8 this morning, i get a kernel panic every time i plug in the MOTU. Hope they get that one fixed in 10.2.(x|x>8)...
I've used the ibook quite a bit since I updated it and everything seems fine so far. The battery indicator has the same problem someone else here mentioned of showing only half as much battery power as you would expect, but my battery has been flaky lately anyway due to another problem so I didn't attribute that to 10.2.8 until I read the comments about it. All in all, I'm having problems with these computers but I haven't noticed anything significant due to 10.2.8 yet. (keeping fingers crossed...)
I was downloading the update this morning (via Software Update), left the room, came back a few minutes later and my screen was blank...as if the machine were sleeping. Nothing would rouse it, however.
I ssh'd in and tried killing various processes but nothing worked...couldn't even reboot!
Only thing that worked was a hard restart (holding down the power button) and then running fsck a couple of times.
Everything is OK now but that was most un-Apple like.
If this gives you an error that says that the filesystem is mounted read-only, then do:
Now do:
And the applicaiton launch problems should be gone.
120 character sigs suck. Make it 250.
You're right that most of the time, Jaguar does do a prebinding fixup in the background when it something incorrectly prebound. That assumes that the prebinding isn't so badly hosed that it can't launch, however.
At least in my case, when 10.2.2 (or was it 10.2.3) did this to me (after crashing during optimization), doing an update_prebinding fixed the problem. Whether it will help for the 10.2.8 early adopters or not, of course, is anybody's guess.
As for the exit, updating prebinding does some scary stuff in the VM system. If it were me, I might continue booting, but giving advice to others, rebooting is a good idea. :-)
120 character sigs suck. Make it 250.
DO NOT INSTALL IF YOU HAVE A REVOLUTION 7.1 SOUND CARD INSTALLED! The update disables the driver, because the .kext driver specifies a Darwin version below that of OS 10.2.8
I wonder what they'll call the 10.2.8 update when they re-release it? 10.2.8.1? This brings them awfully close to 10.3, and they usually roll some fixes in to the old OS when they release a new one.
Yes, they pulled System 7.5.4 after some problems were discovered with the updater. It barely made it into the market, though.
I believe they also pulled one of the 10.1.x updates, but I can't remember which.
I'm quite happy with 10.2.8. It finally fixed my USB!
Turn it off. In the Bluetooth Preferences.
As you might have noticed, 10.2.8 killed your M-Audio Revolution. They posted an updated driver last night, and on my system at least, the card works again.
r ch.php
If you want to know -
G4 800 dual
1.5 GB RAM
GeForce 3 / ATI Radeon
OS X 10.2.8
M-Audio Revolution 7.1
Get the update here...
http://www.midiman.net/support/driversea
jaz
"CAN-2003-0693" refers to the vulnerability.
http://public.www.planetmirror.com/pub/apple/Mac_O S_X/MacOSXUpdate10.2.8.dmg
No indication of that in the articles (did you read them?) -- an Ethernet driver bug and boot problems on some models of Mac would be reason enough.
Beside, why pull the update? Smarter to release a separate (much-smaller) openssh patch afterwards rather than hold back the entire, ~40 Mb 10.2.8 package.
As a fellow dialer-up I feel your pain at the ever-larger updates. Fortunately, I have bandwidth at work and can bring home the standalone packages on a ZIP disk from an office Mac.
je ne suis pas un fou