|
|
|
Perhaps this "unsupported" statement is a little harsh since the support system requirement page says that "the ATI FireGL card has not been tested yet, therefore compatibility is unknown" (paraphrased). The ATI FireGL chipset is used in a significant percentage of mobile machines these days. I am hoping that there is at least some effort to figure out how to avoid a system crash and fail gracefully, and provide some sort of work around for this class of machine (like maybe set screen resolution to nnnXnnn or disable Bumpmapping and Shiny or set Terrain Detail to Low or ....).
In the mean time, is there a way that I can get the older driver so that I can reinstall it until a work around or fix is available? I can't find any link to the older driver even though this upgrade was supposed to be optional. As I said, the prior version that I had installed seemed to work fine...it is only the latest version which seems to have the problem. Please let me know if you need any additional information when working on this problem. Older viewer downloads are here:
https://wiki.secondlife.com/wiki/Downloads 
If you really meant "drivers" when you asked for older drivers, you'll need to get those from ATI, not us. I've imported the issue. The challenge for us is that I'm not sure that we have the hardware in-house to test, so there may not be much we can do about this issue right now. Yes, you are correct; I improperly used the term Drivers to reference the older SL Viewer code. The link you provided is exactly what I was looking for (not the graphics drivers). Thanks!!
I understand about potentially not having the hardware in house to test against. If there is something I can do to help here, I am willing to do this (i.e. perhaps I can run debug versions of the code and send trace files or memory dumps?). I know this is not particularly helpful, but I just wanted to add my offer of support for this problem. I have a Lenovo T60p laptop (2007-82U) with the same issue, but I can't seem to get any combination of older viewers, ATI drivers, and viewer and hardware acceleration settings to work reliably. Sometimes it hangs right away, sometimes after an hour (hardware acceleration enabled, all viewer advanced shaders disabled, viewer vertex buffer objects disabled, etc.).
Thanks. I have similar problems now with lenovo T60P.
Whilst this is a subset of users this will be every IBM employee soon as we have these machines as a standard rollout. The t60P machine and the T60's seem to not be able to run SL. we have 1,000's of people with variations on the problem. Whilst I appreciate that makes us a small % of the population the eightbar.com preseence and the IBM presence is going to get affected by this. Here's another ThinkPad T60p with ATI FireGL 5200 that hangs often. In this case, however, the hang is almost always a totally black screen, the computer does not respond to keyboard or mouse, all activity suspended, and the only recourse is to force the power off. Perhaps the reason this issue has only two votes is that all the T60p owners gave up on Second Life long ago. Can someone loan Rob Linden a T60p so that lack of hardware is not a reason to ignore this issue?
It runs significantly better in a window with a low resolution (like 800x600, so that the search box runs annoyingly off the screen and gets a lot of cursing from me), and the problem went away for a while. It seems to be back again one or two releases after the voice client, and this time I'm not reducing the size of the window anymore. I suspect it has to do with the refresh rate and certain render calculations not being completed in time.
I've had a Thinkpad T60p since late last year. I've consistently failed to get it to work reliably with Second Life. Over the various releases of viewer, the problems have ranged from random hangs, to blue screens, to the viewer freezing whenever the cursor is over the Second Life viewer window (which obviously makes Second Life practically unusable). As this is my only machine, I now rarely use Second Life - I occasionally stop by to try a newer viewer, but as they (so far) haven't solved the problem, I've pretty much given up on Second Life.
Sorry Linden Labs, but this is a REALLY common mobile graphics chipset. You need to go buy a machine with this chipset, or get the IBM people to lend you one, and get it fixed. Any possibility that the problem seen here is related to this bug because the symptoms are very similar (I run on both linux and windows on a t60p)
https://jira.secondlife.com/browse/VWR-1320 FWIW on Vista after applying the procedure here: http://forums.secondlife.com/showthread.php?t=182519&highlight=ati+driver SL has been stable for me on my t60p. I'm much the same as what Itchy said above. So it's not the viewer version in my case either. For what it's worth, I've never been able to run S.L. on my work T60p - ever for more than a few minutes. I've updated BIOS x4, tried every driver I could get my hands on. I am able to get onto Second Life from my own Mac at home - but I don't often have access to that so I usually only log in maybe once a week to read saved IMs. All my screen caps for my team report were taken from that Mac but when people asked me to give them a tour, I had to sheepishly acknowledge I had no access at work.
Everyone on my team that has T60ps has the same problem. When world kindly did an S.L. beginner's class, we invaded them taking over a whole corner just so the team could actually see what S.L. looked like (fortunately they were using the older T41s). This would all be very amusing except that I have a project in S.L. that I'm supposed to be working on and that I've wasted hours trying to debug this issue. I've finally thrown in the towel and gone on to other things. I just don't have time to spend on this anymore. I told my boss that I'm not pursuing it further. I have to go find the absolute cheapest machine that can run S.L. well-enough from a development perspective and just wait until there's room in the budget for it. Until then, project on hold. I have an IBM/Lenovo ThinkPad X60 also with this problem, and have given up on SL until the viewer is fixed.
Add my name to the list of users experiencing this problem. I have tried the variety of solutions posed around the 'net for fixing this. All to no avail. After the latest attempt to get SL running (my 4th) and failing, I have uninstalled SL and am setting aside my attempts to get it working. Too bad I won't be able to see what all the hype is about.
OMG! I'm on SecondLife! On my T60p!
After many BSoDs, after installing new display drivers and bios updates and more BSoDs, today I installed one more bios update, twiddled with CCC because I was getting "you do not have permission to change Catalyst Control Center settings", I installed the RC viewer 1.8.3(4). Imagine my suprise when I clicked connect and it did. I'm even running Notes and 3 JVMs and everything is chugging along quite nicely. I've got the same configuration as listed in the original problem report. With the latest flurry of activity around this issue (especially fargo's comment), I updated by BIOS, Video drivers, and installed the latest SL viewer – and had success! I have a T60p (type 2007-82U, ATI FireGL V5200, running Windows XP). I installed the latest Lenovo BIOS update version 79ETD7WW (2.17) which was posted 9/12/2007, the Lenovo video drivers update version 8.383.1.1.3-070621a2-0508 posted 9/11/2007, and installed the SL viewer version 1.18.3.5 (candidate release). I do not have any fancy graphics features enabled in my preferences, and I am running in a window (as opposed to full screen). I was able to run fine for over an hour without any glitches. Yeah!
After 3-4 hours of flawless operation, I restarted my machine, and now I get an infinite loop in the atidvag driver every time I try to connect to SL....sigh...
Question - how do you use an older level version of the viewer? When you launch it you are forced to download the new version...
This bug really is serious. As a T60P User access to SecondLife is virtually impossible. I am working on a project aimed at demonstrating SecondLife to Customers and find it virtually imposssible to get onto the system. I've even downloaded and compiled the Open Source code, however the last time I tried to logon using my own compilation I received the dialogue box telling me that there was a mandatory download of the new viewer. This needs to be fixed urgently.
I think I have found a clue. The ATI Catalyst Control Center states that my FireGL V5200 graphics support has 512MB of HyperMemory. The SL viewer also sets the graphics card memory setting to 512MB upon auto-detecting hardware. The problem appears to be that Windows XP (professional 5.1.2600 service pack 2 build 2600) only allocates 256MB of memory to the PCI-Express bridge (and therefore to the card). Here's what is reported via the device manager for
the FireGL V5200: memory range: D0000000 - DFFFFFFF The first memory range is the main graphics memory, and it is 2^28 bytes (256MB) in size. If I manually set the graphics card size to 256MB, the latest SL viewer (version 1.18.2(1)) appears to be stable with all sorts of advanced mapping and 3D operations turned on...If the auto-detect is ever activated, then it will go back to 512MB – and it crashes (sooner or later)...at least this is how it appears from my limited testing so far. I hope this helps. I've been having blue-screen crash issues for months now with my laptop (T60p, FireGL 5250).
I took Gennifer's advice, and switched my graphics card memory setting down to 256 from 512 (what it defaults to), and I haven't crashed once since then... This may actually make SL usable for me again !!! Thanks Okay, I take it back - I crashed twice today, just after I posted this...
I disagree with Rob Linden's Comment "Downgrading to critical. This is important, but only affects some users".
This impacts alot of people. The Lenovo Thinkpad T60p Machines.is the computer of choice for many schools that supply students with laptops. We are in the process of developing a virtual campus and this is the computer we use. This issue needs to be resolved ASAP. I have the exact symptoms as reported by the originator of this problem, but I have some additional information that might assist. I logon to SL using one of two machines - a T60P thinkpad or my home desktop - and today as it crashed again, I noticed that I had asked to go to my home and that the image presented was an old home location. When I had restarted, I asked to logon to my last location and this worked and kept working without crashing. Given that the home location displayed was an old one, it appears to me that I may have reset my home location on my desktop at home, but not on my T60p and at some point during the logon this confuses the client leading to the blue screen of death.
I'd like to add myself to the list of affected IBM employees affected by this. I've a Lenovo T60p model 2007-CQ8. On my team I am aware of at least 3 other people with this exact issue as well. As for myself, I've only been able to successfully connect to SL once on this machine without a BSOD. So I'm eagerly awaiting the resolution of this issue.
I'll add my vote to this issue. I'm not an IBM'er but I'm amazed, given IBM's footprint in SL and the number of IBM'ers that carry around T60P's, that they can't collectively muster a solution to this rather annoying problem. I made the mistake of choosing a Lenovo T60P (Type 8741 running XP)over a Mac Book for my new laptop computer and thus I'm unable to connect to SL without the above described behavior. Various solutions seem to be posted, then qualified (i.e. victory declared, then rescinded or qualified). Would it be possible for IBM, or some SL-dependent sub-group within IBM to sort through these various suggestions, then post a step-by-step fix which is repeatable, as LL doesn't seem to have any interest and/or ability to fix the problem.
Alright LL you need to get your act together and fix this problem. I have a workforce of approx 50 people who need to access SL and they all have T60p's. This is becoming ridiculous. Yet another example of poor service from LL. I beginning to think we should take our business elsewhere.
Just updated my Lenovo T60p (8742) BIOS to version 7IET31WW and ATI Mobility FireGL V5250 to version 6.14.10.6698 with video memory turned down to 256MB after many crashes at varying times during SL viewer operation. Didn't fix the problem. SL still crashes (causing BSOD quoting ATIDVAG Stop:000000EA.
Considering we have a global agreement with Lenovos for our >80K corporate users (not IBM); would have thought it important to focus on getting the SL viewer working with the ATI Mobility FireGL (in all current R, T and X61's as well). Am happy to wait but would like to know how long I should wait for... I've got a T60p as well, and I can barely do any work these days without crashing my entire system. It has gotten to the point where I only use the laptop to log into the IBM network and seek a desktop computer to get into SL whenever i'm doing work outside the office.
Ironically, the very same hardware is quite capable of running Half Life 2: Chapter 2 and Portal without any complaints. I am a new IBMer with a T60p and am experiencing this issue as well.
To Rob Linden
Please note that I am the originator of this problem report. I am formally requesting that you upgrade this problem priority. When I first opened this problem I presumed that I was one of only a small number of folks that had this problem. After 3 months of watching and hoping for a fix, there doesn't seem to be one in the works. The number of people affected by this problem is very very large. Please understand that the Lenovo TP60 is a workhorse for many companies. At this point it is unusable for SecondLife. Over the last three months, I have tried nearly every SL client version that has come out and all of the following have the problem. I have tried nearly every combination of ATI graphics drivers and many many different graphics settings within the SL client. The problem sometimes appears to have gone away with certain settings or combinations, but it is just a matter of time (sometimes after a few minutes of use, sometimes after a few hours) before the same symptoms return and one can no longer even log in to SL. Once it returns, it seems to be random chance when it starts working again...maybe several reboots, maybe uninstallation of SL Client, maybe a few sleep cycles, maybe ... During the last 3 months I have been able to log in maybe 3 or 4 times for a total of 2 hours but have spent 80+ hours just trying to get something to work. BSoD's are painful for users and this one is especially painful because once hung, the system takes a long time to get to the BSoD, then you have to reboot to do anything, then when you launch SL again it takes a while for it to process the fact that it crashed and collect logs. I HAVE COME TO THE CONCLUSION THAT SECOND LIFE WILL NEVER WORK WITH LENOVO TP60P MACHINES AND THAT NO ONE AT LINDEN SEEMS TO CARE. Not once have I been asked for a crash log, not once have I been asked to install a trace module in order to track the problem down or at least narrow it down. By the way, ATI says it's not their problem, talk to the PC vendor. Lenovo says it's not their problem talk to the application vendor. The application vendor (Linden Labs) doesn't seem to want to even look at the problem. I would suggest that you contact IBM to request a loaner machine for looking at the problem. They provide a LOT of $'s to support Linden Labs. They have a large number of TP60's in their work force and I suspect that they would like to see this problem resolved too. Please advise. I am also an IBMer with a T43 and have this problem: https://jira.secondlife.com/browse/VWR-2220
. SL refuses to even boot for me.However, in the next 4 weeks I am upgrading to a T60, along with 4 other work mates. We are atm starting a virtual world research project and are assessing various systems. So far, Second Life cannot even be considered because of these problems. I will add my vote to the Lenovo T60p problem being a serious problem for IBMer's trying to use Second Life. I have been totally unable to get into it. I have done all of the following:
Updated the Versions affected to all versions 1.18.0 through 1.18.4.3 (no option for selecting 1.18.5.1 yet...but it appears based on Looking4 Destiny's comment that the problem continues there too.
I would advise anyone who is looking to upgrade to a Lenovo T60 to not even try Second Life...find another Virtual World until this problem is fixed. You can spend lots of hours in Second Life only to find out one day that you have been bitten by this problem. Usually it crashes even before you can get fully logged in. Occasionally it allows you to log in and you can wander around Second Life for some time before it crashes. When it crashes, the machine hangs (liely due to a tight loop for a module with a high priority). You cannot do anything during this time which lasts anywhere from about 3 to 10 minutes before you get the blue screen of death described in the original problem report. I would advise anyone with this problem to vote for this problem as the more votes it gets the more likely it is that someone from Linden will sit up and take notice that there is a whole class of users out here 10's of thousands that cannot use Second Life and because of this it is drawing bad comments about Second Life in general. I also have received my new T60p and find that after the first connection I get the blue screen of death. I am with the long line of people expressing their interest in this problem. Not only does IBM have a large presence in this arena, we are encouraged to look into this as employees. the T60 set of Thinkpads are the latest rollout level to IBM employees. Linden is severely limiting itself by approximately 540,000 employees. I also hold up the torch to have this issue resolved.
Add me to the list of people getting constant BSODs using Second Life. I got so frustrated that I just reloaded my T60p with a vanilla load of XP. I installed SP2 and then downloaded the latest hot fixes from MS. I also installed the latest ATI video drivers. I was fine for about two hours doing nothing more than walking and flying around. As soon as I tried to teleport, SL froze and then took the now infamous 'ati2dvag' BSOD. Funny part is that I also have a three year old IBM T40 laptop with a 32MB video card that works like a champ in SL.
Thanks to those of you who've chimed in to express your frustration – it does help to see the votes + comments letting us know you are affected by this. Others encountering this problem should also post here.
I've asked that this issue be looked at by our devs again during internal triage, including exploring the possibility of working with IBM to get this resolved. Another IMer having this problem with a t60.
Add me to the list with my T60p.
[UPDATE] I was contacted by Michael Schmedlen of Lenovo, who's helping us with equipment so we can test this serious issue "in-house". Aric Linden & his QA Team here at Linden Lab have made arrangements to work together closely on resolving this... it'd be good for all involved. Furthermore, in an interesting finding, it seems our technology preview of First Look: WindLight (at least under some conditions) ran well for us on a "FireGL V5250", which is slightly different. This is tentative, but if you're continuing to have these crashes/BSODs, I suggest downloading it and trying it out, and letting us know your experiences: http://secondlife.com/community/firstlook.php You can add me to this issue as an IBM Employee and T60p User. I am going to try all of the updates that people have listed but am somewhat encouraged that it looks like Linden Labs, especially Torley Linden, is now looking into this and taking it seriously.
This is absolutely ridiculous. Linden Labs needs to get their act together regarding this T60p issue. I actually was running fine for the last 6 months untl the latest update. I was smart enough to wait before installing the new version, until I started getting BSODs with the older version. So, I migrated over, and it was downhill from there. I'm an IBM employee, and I've missed my Dec. 1 deadline for a project I'm running with an external organization due to this issue. This actually will start making us look bad to outside clients and organizations due to the issues within Secondlife. My deadline has moved to Dec. 15, now 2 weeks late, but since this problem is so persistent, I'm going to borrow an older laptop to get this completed. The MAJOR problem is that our external clients who use this may relate issues with Linden Labs to IBM...
Possible path to a fix – No more Blue Screen when I connect to OpenSim as server for my Second Life client. Diagnose the difference.
Starting point is IBM T60p with up-to-date drivers and Blue Screen most of the time connecting my Second Life 1.18.4 (3) client to Linden Servers. I downloaded OpenSim, which is an Open Source reimplementation of a Second Life Server, from http://daltonic.blogspot.com/2007/08/getting-latest-and-greatest-bleeding.html The hypothesis is that the SL client is told to do some dangerous thing by the Linden Labs Server that the OpenSim server does not. Linden developers could try reproducing the message traffic from OpenSim, and then changing the content, order, and timing of the traffic to make it more and more like traffic to the Linden Server. When the Blue screen happens, look in the code paths executed within the client to see the difference between Blue Screen and not. Go for it. Oops. Meant Dec. 6 version of OpenSim, not Nov. 6.
Additional check: I connected to several other OpenSim servers, older versions, with no Blue Screen. To all concerned, thanks for your feedback. I know how frustrating this is, and per my comment above, Linden Lab and Lenovo are working together to resolve this presently – I'll forward your latest feedback too.
And... has anyone else had luck with using WindLight and a T60p?
WindLight been very stable for the last 42 minutes of SL...still holding my breath...
Second Life 1.18.5 (75173) Dec 6 2007 10:26:10 (Second Life WindLight) You are at 237321.8, 260369.7, 31.4 in Svarga located at sim235.agni.lindenlab.com (8.4.128.111:13004) CPU: Intel Core Series Processor (2161 MHz) I had the very same problem on my T60p. I tried everything. But nothing seem to help. Yesterday I installed the Windlight Viewer.
Surprise!!!! It works. It did run for about 6 hours no crash. No Problem during log in. And, I think I get a higher FPS Judy Just a follow-up to my comment on Dec. 10, I've had no problems with Windlight for about 5 hours of activity, traipsing all over SL...
Gennifer I've tried the WindLight viewer, and it has not crashed the t60 at all. the performance is just awful though.
Hopefully this should be a hint as to what the SL viewer is doing wrong. @Gennifer, Judy, Astrella – thanks for the feedback, I'll forward it.
@Astrella: When you say "performance is just awful", out of curiosity, what are your Preferences > Graphics set to? Is performance bad even when you click "Low" on the slider? Yes, Graphics is set to low on slider. I see very blocky looking avatars, and what appears to be a lot of lag, particularly in places where there's a lot of prims being run. Dance places with lot's if dressed up avatars.
I'll play a bit with settings more and post feedback here. Thanks for paying attention to this Torley. We (IBM) appreciate this. Wow...and I thought my T60p had a broken graphics adapter or something. Nice to know that Linden folks are on it now. But as many of you have mentioned, its quite strange that such a "common and widely used" chipset was untested by LL.
 I'll watch this space. WindLight Freezes on T60p
I installed WindLight – Second_Life_1-18-5-75173_WindLight_Setup_No_BSOD.exe – on a T60p with graphics set to 32 bits with a second monitor attached, also 32 bits. WINDLIGHT FREEZE- Connecting to an OpenSim server, about once a day for the past 2 days my cursor disappeared. I could do nothing, soI had to power cycle the laptop. The one time I paid attention to conditions was when I left the computer for a spell, and WIndLight may have changed state because of my inactivity. Possible trigger. Both days after reboot I accepted the client's offer to send a crash report to Linden Labs, so find details there. Further exploration of this behavior is problematical because ... Today WindLight refused to run unless I installed required update – Second Life 1.18.6 (75762) Dec 13 2007 16:08:39 (Second Life WindLight) following which .... WINDLIGHT NEW-TODAY LOGINURI BUG - This new version of WindLight does not allow me to access my OpenSim server. Connecting to OpenSim is done by right clicking on the WindLight icon and changing the Target field to add a "-loginuri" directive like this, changing from "C:\Program Files\SecondLifeWindLight\SecondLifeWindLight.exe" -settings settings_windlight.xml -channel "Second Life WindLight" -set SystemLanguage en-us to "C:\Program Files\SecondLifeWindLight\SecondLifeWindLight.exe" -settings settings_windlight.xml -channel "Second Life WindLight" -set SystemLanguage en-us -loginuri http://YourOpenSim.WhereEver.com:9000 This new version of WindLight evidently no longer honors the -loginuri directive. On my lenovo t60p I'm getting the same error, exact same scenario / driver / config / blue screen, very frustrating. I downloaded and installed the SL client for winxp pro sp2 just yesterday. This type of laptop is used extensively at my company, about 4500 employees. PLEASE FIX THIS.
I have a brand new Toshiba Satelite Pro A200 and I get the same problem. My graphics card is a ATI Radeon 2400HD, I have 4 gd of ram, 1.8ghz intel dual core processor with Windows XP Pro service pack 2. This Laptop should run Second life easily. But I keep getting this infinite loop error everytime I log in. It is very frustrating especially when my old computer - a non dual core pentinum 4, 2 gb of ram and a Geforce 4 was super stable.
I have tried everything, ATI drivers, Omega drivers, every suggestion from the internet I can find. Changing all my settings graphics resolution, I have even tried windlight - no good! Even a different mouse! I've given up! Is there anyone who can help me! I to have a Thinkpad T60p and am having this problem.
When I first started having the problem the crash / blue screen happened with ATI2MTAG. However, when I uninstalled QuickTime (as suggested by a different site/game) then reinstalled 1.18.5 (3) the problem appeared to be "resolved". However, I am now back to the same issue but now it is happening in ATI2DVAG. So I will vote for this one as well and add any additional comments and findings I have as I go along. BTW--My older T42 does not have this problem. Same issue with a T60- Desktop works without a problem.
I am using an Lenovo T60-1951 (Not the T60p) and have been having the same BSOD issues as everyone else here. (Currently crashing on the login screen before connecting to sim!). But from reading this thread Im convinced that the issue is not related to the ATI drivers as my T60 is using the Mobile Intel 945 Express chipset (GMA950 128mb ram). One of the main common video elements is the screen with its native 1400x1050 resolution. Could this be part of the issue?
I have just changed my screen resolution to be 1280x1024 and relaunched the client and its running smoothly for a few hours now (as smootly as possible with this noddy graphics card anyway!)... It would be interesting to get a sensus of the active native resolutions used by those who are experiencing BSOD to rule this in/out of the ongoing problem determination. Regards, Groove. UPDATE: BSOD is back with 1280x1024 resolution. Back to the drawing board. I have also been experiencing this problem for a while now on my T60P ... I always thought it was heating issue (these laptops run WAY TOO HOT when SL is running).
Hi Torey, Looking for an update on this one. I notice it's unassigned. What is the vote count that needs to be achieved to get some time on this one?
[UPDATE] We're anxious to work on this ASAP but we haven't heard back at latest from Lenovo; we're waiting to get a test laptop from them. I pinged them a few days ago and heard nothing yet – I will ask Aric Linden (head of Quality Assurance @ Linden Lab) today about how we can reach them.
Hi Torley, IM me... I'll see if there's a way I can help move that for you.
@elmsplitter: I'll email you (my IMs are unmanageable).
Groove Market & Company
I'm also an IBMer who has experienced the problem with my T60p and also witnessed the widespread nature of the problem. My problems- But to underscore to our friends at LL, this is a very big problem, since many of us at IBM are trying to evangelize virtual worlds, within IBM and to our clients, but this systemic problem is a huge, strategic hindrance. So the attention being paid is, I would assert, very much in LL's interest. Finally, I was contemplating upgrading my video driver Driver Packaging Version 8.293.1-060913a-036475C-Lenovo to the latest from ATI, but think I will wait a bit in case in might worsen my ability to access SL. I just changed my laptop for a Lenovo T60p and so went into the trouble described above and finally stopped using SL.
Is there any plan to fix this problem or to provide a work around ? Hi Oboy... I did the upgrade you mentioned to the Video driver, and there is no improvement.
I'm attempting to help Linden get the needed hardware to debug the situation from inside IBM. It looks like i'm having the exact issue with my Dell D620
I also have a Lenovo T60 w/an Intel 945GM Chipset. I have had SL crash twice in October with a blue screen and an error message stating: Unmountable Boot Volume. I haven't tried it on the laptop since. Would love to use SL on the laptop again, but don't want to take any chances.
IBM has worked with Lenovo to get Linden Labs the machines impacted by this issue. Hopefully, this will aid Linden in resolving this issue.
IBM/Lenovo T60P. Same issue running under Windows XP Pro and Linux. Under XP it BSODs regularly with an error indicating an issue with the video hardware / driver. Something about the driver being locked in an infinite loop. Under Linux (Gentoo, kernel 2.6.23 with the most recent drivers) it crashes hard. So hard, it actually won't reboot without firing it up off a CD or booting into Windows temporarily.
That one is a scary crash. Apparently there is something getting set on the video card which is persistent across power off. One successful reboot is enough to clear the issue and allow normal operation. Encountered this with .18., the latest RC and Dazzle under Windows. Have only tried the .18. client under Linux. Hello,
The T61 is also unusable and in rollout in IBM now. All I can use is Windlight with lowest graphics resolution. Standard viewer shows frame rate decreasing until one has enough (sometimes immediately after login). This post may be premature: I upgraded to RC 1.19.1.1 for Windows today and have been running the client for the last hour or so without any failures. I've teleported around the grid and hit some fairly graphics intensive areas, and run across several versions of the simulator. All with reasonable framerates and no appreciable glitches.
I tried 1.19.1.0 under Linux and it ran for over an hour, but would crash every time on restart. It did not hard crash the box as it had previously. I'd read somewhere in the release notes a reference to FireGL not being correctly identified. Is that a reference to the correction of this issue? I keep crashing at startup using RC 1.19.1.1 on my thinkpad t60p with FireGL 5200
Possible clue to a fix –
Up until now, RC 1.19 versions have been giving the BSOD only once a month or so on my IBM T60p But Second Life 1.19.1 (3) Mar 26 2008 12:59:02 (Second Life Release Candidate) after working once gave me BSOD on 3 or 4 subsequent startups in a row. First BSOD happened after I moved the cursor outside the SL Window after clicking Connect. Uninstall, reboot, reinstall, had no effect, still BSOD when the progress bar reached the end during "precaching,' at which point the hourglass cursor diappears, then BSOD. BSOD seems resolved now. I've logged in several times OK. The change came when I tried a login as follows: So, evidently action 2 or 4, or both together, somehow unstuck my T60p from the BSOD in a way that even uninstall-reboot-reinstall could not. This could be a clue to a fix. ------------------------ The next day it is BSOD no matter what I do. Perhaps there has been some graphics improvement in 1.19.1 (3) that is fatal for my T60p. I have had pretty good success running SL on my T60. There are some considerations though (which I found with a LOT of tweaking):
1) Disable "Power Play" in the ATI Catalyst Control Center (ATI Icon in toolbar -> Catalyst Control Center -> PowerPlay). If PowerPlay is enabled, Second Life WILL crash after a short period. Note: The ATI driver appears to sometimes reset PowerPlay back to "enabled" after a reboot - not always - just sometimes. I'm not sure why that is, but make sure you check it every time before starting SL. 2) Never run on battery power - plugged in only. Otherwise Second Life WILL crash. 3) Buy a "Laptop Cooling Stand" with a fan to cool the underside of the T60. Otherwise the T60 appears to shut itself down after about 15 minutes of SL due to overheating. If step 1-3 doesn't get you going try these: 4) With the "Second Life Release Candiate" that I'm running, I seam to be more stable if I run full screen instead of in a Window. 5) If you have problems getting SL started at all, try the following: a) Go into the Windows Control Panel and select the "Display" Icon I'm not sure why step 5 often makes a difference (maybe it somehow resets stuff in the graphics driver) - and please don't ask how I came up with the idea to try that in the first place The above works on my ATI Mobility Radeon X1400 on a T60 2007-69M I hope this helps a few people Much better luck with version 1.19.1.4 than with 1.19.1.3. No Blue-Screen Of Death yet on my T60p.
1.19.1.4 includes this fix (among many others): "Fix for white areas on lenovo with ATI FireGL 5200". I would have expected something like "Fix horrendously hard crash on Lenovo with ATI FireGL 5200". I installed it from scratch, fired it up, it ran for about 1 minute, then it crashed again. No BOD, just switched off. Restarted... hung half way through Windows startup screen.
I was in windowed mode, setting the preference for full screen when it crashed. Maybe it would work if I started in full screen, but this is getting pretty annoying. I guess it will take a call from Sam Palmisano to Philip Rosedale to get this fixed. That might happen when the floodgates are opened based on a recent announcement that IBM will be hosting some private SL sims (a.k.a. zones). I'm sure many of those 6,000 or so IBMers that will be invited will be using T60ps. Of course, at that time Philip might ask someone, "How long has this been an open issue?" A sure workaround is to delete all of the application user files, network cache and browser cache. Works everytime. User files are in c:\documents and settings\administrator\application data\SecondLife. Delete the entire folder. You can then start normally.
I just installed the 1.19.1.4 and I keep crashing at startup... using t60p lenovo, I also removed the directory SecondLife under my user account...
Just installed the new candidate release 1.20.2.85278 and I finally can startup... yahoooooo keep finger crossed
Sigh... Longtime SL user here and I've had problems with my T60P for about the last year. I don't have a solution, but I do want my voice heard as well as the others that have posted their comments on here. I've done all the BIOS updates and video updates and still no success. It's something specific to the SL client, as this was working just fine about a year ago - then with one of the Client updates, all went to hell.
LL PLEASE PLEASE Find us a solution to this problem. I second the comment that nevik jackalope made. I have been doing this since my last post and it works! Delete the entire Second Life folder under application data and SL starts up just fine and runs until I exit the client.
I was google for this problem and i came across Second Life Wiki:
http://wiki.secondlife.com/wiki/Bug_triage/2007-08-15 No Patch: VWR-2141-Machine crashes during login with Blue Screen of Death page complaining about infinite loop in ati2dvag file - Skibo Torok -Seems this issue says about machine crashes with the infinite loop in ati2dvag, i would love to post this update too.. -It does not happens to notebooks or laptop too, it also happens to my desktop ATI 9250 128MB as well..., and neither switching back to old SL viewer nor upgrade the driver works.... -I sincerely hope that this can be fix, as i was just thinking of starting to do investment in SL, but because of this problem, i have to retract this idea. -Well., it never occurs when i started joining SL on January.., the problem start only a few days ago... Thanks again.. I gave up working in SL - there's just no point if my machine crashes 4 out of 5 times I try to logon. After several months I've tried re-visiting and am shocked to see this issue is still open. Why isn't such a major problem being fixed?
Here comes another T60P IBMer facing this problem from last 2 years. Even I opened a support tickets with SL guys 2 yrs back, with my second life account. I never ever got any response on that. I finally gave up with SL more than a year back and today I thought of checking is there is any update from these guys and what I find is my ticket is even not there I can not see my ticket in open or resolved issues
Great guys, keep it up. It was really not expected. I updated the video driver from www.pc.ibm.com for my T60p 2007-DQ6 and for last few hours do not see the crash. usually it has happened with minutes of launching of the secondlife client. I would suggest try uploading a new driver and try.
I updated video driver and it seems to be fixed.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Open
Critical
Blue screen with ATI Mobility FireGL V5200
Per the system requirements, this is currently unsupported hardware:
http://secondlife.com/corporate/sysreqs.php