10.4.8 Really sucks

[Mezzanine224]

My Mac Pro seems to kernel panic when I'm doing video stuff. Sometimes a video is just playing, other times I'm resizing a window, and yet, sometimes it's just idling.

I'm guessing it's a video driver issue?

I also have Boot Camp on an NTFS partition, and I'm wondering if that could be the culprit.

Is anyone else having similar issues?

 

[Soulstorm]

I don't know how is everyone performing maintenance on his/her machine, but nearly every time that something is going on, its the fault of the user, who doesn't repair permissions, update prebindings or run -fsck.

I have 3 machines with 10.4.8 installed, a G5, an iMac G4, and a dual Mac G4 1,25 GHz. All work like a charm. and the latter is used in professional music production.

 

[risc]

I don't know how is everyone performing maintenance on his/her machine, but nearly every time that something is going on, its the fault of the user, who doesn't repair permissions, update prebindings or run -fsck.

I have 3 machines with 10.4.8 installed, a G5, an iMac G4, and a dual Mac G4 1,25 GHz. All work like a charm. and the latter is used in professional music production.

So if I've done all of the above and the machine still doesn't work correctly with OS X 10.4.8 it's my fault? How about if I actually did a fresh install back to 10.4.0 and it worked perfectly, then I updated to 10.4.8 having installed NO OTHER APPS and the problem came back, is it still user error? It's interesting even though it is user error when I just reinstalled OS X and took it back to 10.4.7 on my GFs machine all problems disappeared.

There have been multiple times when Apple have released dodgy updates, anyone who doesn't believe this needs to pull their head out of the sand and get a clue! Security updates have had issues before, but this is the first time I've ever had issues with a OS X point upgrade though.

 

[dpaanlka]

There have been multiple times when Apple have released dodgy updates, anyone who doesn't believe this needs to pull their head out of the sand and get a clue!

I believe there were a lot of issues for 10.3.0.

Anyways, in this case all you can do is submit bug reports, or complain to Apple, and just wait until the next update.

Sorry, but my computer is working fine!

 

[MrSmith]

have you tried the basic maintenance? repaired permissions? ran a full system optimization with Onyx?
also a very little known tip. sometimes the file system can get wonky. just like defragging from the command line (safe mode) is much more efficient in windows...macos has a repair tool thats much better than the ones you normally see.

boot your computer holding down "command + s"
it will boot into a text only console screen. dont freak out.
type "fsck -y"
this will run the built in unix File System Check utility.
it has fixed many a problem that nothing else would and restored system reliability. it takes awhile, just let it run. also on G5s your fans might go crazy for a bit, but it should be fine.

these are isolated issues sounds like..or at least tied to just certain machines. i have a Macbook Pro and an Dual 2ghz G5 and they both run like a champ. ive had no problems with 10.4.8 with either.

I tried the above and got this:

Volume is journaled. No checking performed.
Use the -f option to force checking.​

 

[AndyMulhearn]

I don't know how is everyone performing maintenance on his/her machine, but nearly every time that something is going on, its the fault of the user, who doesn't repair permissions, update prebindings or run -fsck.

I have 3 machines with 10.4.8 installed, a G5, an iMac G4, and a dual Mac G4 1,25 GHz. All work like a charm. and the latter is used in professional music production.

All of which are PowerPC and the vast majority of wireless problems only seem to be with the Intel platform. Or have you not been reading posts properly?

How about these people:

http://discussions.apple.com/thread.jspa?threadID=709005&tstart=0

http://discussions.apple.com/thread.jspa?messageID=3271672&#3271672

http://discussions.apple.com/thread.jspa?messageID=3277364&#3277364 (suggests problems with PPCs)

With the search results here:

http://discussions.apple.com/search.jspa?objID=c140&search=Go&q=10.4.8

With a note from Apple here http://docs.info.apple.com/article.html?artnum=304482 which didn't solve my problem.

The summary is that it's a know problem with 10.4.8 which doesn't affect all users but if it does affect you, it can be pretty hard to solve...

 

[JFreak]

10.4.8 killed the ability to send SMS messages from AddressBook. Prior to the update, everything was fine. After the update, the feature is greyed out. Wonder why

 

[zflauaus]

I'm starting to feel left out....I've not had a single issue with any OS update going back to Panther all the way to 10.4.8

Not one issue.....

Knock on wood, which is actually my desk, I haven't had a single major problem that other people have with each update on Tiger.

(Prays to the Mac God for no problems.)

 

[slb]

10.4.8 is installed in my home on an iBook G4, a MacBook, and an iMac Core Duo. No problems on any machine.

 

[jessep28]

No problems here....

 

[dwishbone]

I tried the above and got this:

Volume is journaled. No checking performed.
Use the -f option to force checking.​

then try fsck -fy

that should force it to check the volume.

 

[macg4]

. i have 10.4.8 installed on my powerbook pismo with no issues at all, havent upgraded my main machine yet because of hearing about all this issues. my main machine is a powermac g5 1.8, but its seems this issue seems to be with the intel machines more than the powerpc machines, so i should be alright i guess

 

[Soulstorm]

All of which are PowerPC and the vast majority of wireless problems only seem to be with the Intel platform. Or have you not been reading posts properly?

I didn't say anything about the specific problem, I only gave a general solution (that may or may not solve the problem) and didn't claim to have this problem solved under OS X and PPC machines. Or have you not been reading my post properly?

If you had been in the forums for a little more, you would notice that although basic maintenance is known to everyone, not everyone seems to know exactly how to do it, and simple problems that can be solved with a permission repair come up all the time in these forums. And if you had read this thread more carefully, XP Defector failed to mention whether he/she had done all these things or not. So, my post was just a reminder.

There have been multiple times when Apple have released dodgy updates, anyone who doesn't believe this needs to pull their head out of the sand and get a clue! Security updates have had issues before, but this is the first time I've ever had issues with a OS X point upgrade though.

I know. I've never had any problems with any machine I've used, but I know many people who have. As I said above, my post was just a reminder. But sometimes it's easy to get angry with the company that made a product just because we want to avoid the frustration of fixing it ourselves. And many threads in these forums prove I'm right. I just offered the obvious possible solution to the problem, since it's the only idea I had!

 

[risc]

IMHO if you have issues with OS X (or its apps) and you have tried to diagnose the issue the best thing is to report a bug to Apple. I currently have a bug report open for the iMac G5 wont wake from sleep issue which I just had to add some extra info to today under instruction from Apples engineeers. Sure you can complain all you want just make sure you are filling in bug reports at the same time.

http://bugreport.apple.com/

 

[AndyMulhearn]

I didn't say anything about the specific problem, I only gave a general solution (that may or may not solve the problem) and didn't claim to have this problem solved under OS X and PPC machines. Or have you not been reading my post properly?

And the comment in which you say explicitly:

"I don't know how is everyone performing maintenance on his/her machine, but nearly every time that something is going on, its the fault of the user, who doesn't repair permissions, update prebindings or run -fsck."

Isn't an indication that you feel it's a user problem? I'm stunned. That's the way I read it.

And there was me thinking that if an update is installed and permissions need to be repaired and prebindings updated then perhaps the installer should do it.

Having said that, if I ever have to boot in to standalone mode and run an fsck then I've got more pressing problems than a wireless card not working.

If you had been in the forums for a little more

Interesting. Why is the length of time I have been registered on this site relevant? Is this the only place where OS X problems are discussed? Does people's experience of OS X only start when they register here?

, you would notice that although basic maintenance is known to everyone, not everyone seems to know exactly how to do it, and simple problems that can be solved with a permission repair come up all the time in these forums. And if you had read this thread more carefully, XP Defector failed to mention whether he/she had done all these things or not. So, my post was just a reminder.

Except that this problem would seem to defy "basic maintenance" attempts at resolution.

I know. I've never had any problems with any machine I've used, but I know many people who have. As I said above, my post was just a reminder. But sometimes it's easy to get angry with the company that made a product just because we want to avoid the frustration of fixing it ourselves. And many threads in these forums prove I'm right.

Feel free to give yourself a pat on the back.

I just offered the obvious possible solution to the problem, since it's the only idea I had!

Yes, unfortunately the issue is that you suggested that these problems are the fault of the user. And they're not. If permissions need to repaired and prebindings updated, the installer should do that. Not the user.

Either way, Apple have stuffed something up with the 10.4.8 update. It'll be quietly fixed in 10.4.9 or a sneaky security update. But blaming it on users not knowing how to run regular maintenance is asinine in the extreme.

 

[dwishbone]

i dont think anyone here has said there were not and have not been issues with updates. there probably is, but they are not for everyone. there seems to be little consistency with who is having problems. the only thing is it seems to be more intel based than PPC based. the installer may have messed things up. but, its something that can sometimes be fixed by the user. if people dont want suggestions to fix them then dont ask or come looking for answers. apple certainly isnt going to come fix it for you. at most they'd tell you the same thing people here are saying...that is repair permissions, run fsck, reinstall, etc.
the fact is the machines that are effected may have had OTHER installers screw up things...and somehow interacted with Apple's update to create problems. apple cant watch everyone's systems. i hate to sound like im in defense of Microsoft, but it's part of the reasons windows updates dont work as they should. people (non savvy users) generally load so much crap that its amazing that the updates work as well as they do.
there may be a problem with 10.4.8...sure. but there may not be too. remember usually only the complainers are usually the ones to speak out...and rightfully so. but when a user base has only a small percentage with problems its not so much the update's fault. tech support is a pain if you cant be at the system in question.
all i can say is i rarely have any problems with apple's software or its updates. anytime i have ever had an issue with a mac since the move to OS X the normal steps have solved the problems.

 

[thewhitehart]

Assuming this thread is about 10.4.8 problems,

There is definitely a problem with wireless for intel macs. I have exhausted just about all possible and suggested solutions, both from users' advice here and Apple's own support. I don't have the link, but Apple confirmed the airport problems with intel core duos and WPA2 networks specifically caused by the 10.4.8 upgrade. Their suggestion was to remove the offending network from the preferred list and re-add it again.

It worked for a while, and then it started acting up again. Any subsequent changes to the network settings will require you to re-add the network all over again.

All I can say is, bring on 10.4.9. I doubt there will be any fix in the meantime. I've had no problems with my PPC ibook.

 

[phuong]

i have 10.4.8 installed on MP and MB. all are running fine.

i'm still wondering though, what are the differences between 10.4.7 and 10.4.8?
if there are not much, why just stick to 10.4.7 which seems to be a very stable build?

 

[AndyMulhearn]

i have 10.4.8 installed on MP and MB. all are running fine.

i'm still wondering though, what are the differences between 10.4.7 and 10.4.8?
if there are not much, why just stick to 10.4.7 which seems to be a very stable build?

I ended up rolling back to 10.4.7 because none of the suggested fixed worked for me at all. Removing the connection seemed to work for about 2 hours and then just fell apart. The problem is it seems that there is no way tell if you will have this problem until you update to 10.4.8

 

[Soulstorm]

Interesting. Why is the length of time I have been registered on this site relevant? Is this the only place where OS X problems are discussed? Does people's experience of OS X only start when they register here?

Nope. But it's relevant to the threads you have viewed in this forum that concern many problems that are solved through basic maintenance. That's what I said, I didn't try to imply that I know more things in any way than you just because of my post count.

Except that this problem would seem to defy "basic maintenance" attempts at resolution.

If it defies them, then by all means, figure something else out. Noone claimed to have this problem solved under basic maintenance, including me.

Yes, unfortunately the issue is that you suggested that these problems are the fault of the user.

No, I wrote that this MAY be the fault of a basic maintenance script not having been ran properly. That would indeed be the fault of the user, if it happened. And I have all the right in the world to imply that the problem may have been provoked by 1)false system configurations 2)unability to ran maintenance scripts. It hasn't been provoked by it? Fine. It's OS X's fault. Just wanted to make sure that all basic actions have been taken to prove that the problem the user is facing is severe. The problem here is that the phrase that we are arguing about was intended as an innocent suggestion-realisation. Nothing more.

If permissions need to repaired and prebindings updated, the installer should do that. Not the user.

Indeed. And all system upgrades by Apple do that. But every time, additional permission repair is needed, because for some strange reason, errors in permissions still exist, even if they have been partially repaired by the installer's repair permissions script. Yup, I agree, Apple should do something about that. But since it's a known problem, it wouldn't hurt to repair permissions manually after each system update. I also agree that the OP (and many others) do not ought to know about that, and I didn't imply that they should in any way.

Either way, Apple have stuffed something up with the 10.4.8 update. It'll be quietly fixed in 10.4.9 or a sneaky security update. But blaming it on users not knowing how to run regular maintenance is asinine in the extreme.

The only clear blame I see in this thread is you blaming me for saying that the OP doesn't know how to repair permissions, run -fsck etc. But, since he/she didn't mention wether he/she had done these things, I can easily fall into the 'trap' and assume that this may be his/her fault, that's why I asked

Anyway, we are giving more attention to blames than deserved. I will refrain from further comments, since we are simply arguing about a simple misunderstanding here, while we should be figuring out a solution.

 

[AndyMulhearn]

The only clear blame I see in this thread is you blaming me for saying that the OP doesn't know how to repair permissions, run -fsck etc. But, since he/she didn't mention wether he/she had done these things, I can easily fall into the 'trap' and assume that this may be his/her fault, that's why I asked

My final word on the subject. What you said, and I seem to have had to quote this a number of times, is:

"I don't know how is everyone performing maintenance on his/her machine, but nearly every time that something is going on, its the fault of the user, who doesn't repair permissions, update prebindings or run -fsck."

It is the fault of the user. Not have you repaired permissions and updated prebindings, but it is the fault of the user.

Is that clear now?