Date: Thu, 5 Jul 2012 10:31:54 +0530 From: Subhro Sankha Kar <subhro@80386.org> To: Lars Eighner <lars@larseighner.com> Cc: Tobias Rehbein <tobias.rehbein@web.de>, FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Tweetless Message-ID: <39A6D581-F4C3-4A50-AD3E-9ED0BF52F396@80386.org> In-Reply-To: <alpine.BSF.2.00.1207040859230.1533@abbf.ynefrvtuare.pbz> References: <alpine.BSF.2.00.1207030051180.1547@abbf.ynefrvtuare.pbz> <20120703154455.GA1546@oshi.local> <A8BB2490-3BEE-4B41-8ADB-7667B1486E5F@80386.org> <alpine.BSF.2.00.1207031515100.1354@abbf.ynefrvtuare.pbz> <EC3949AE-0721-46A0-AB36-9842D2CE399C@80386.org> <alpine.BSF.2.00.1207040859230.1533@abbf.ynefrvtuare.pbz>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04-Jul-2012, at 7:44 PM, Lars Eighner wrote: > On Wed, 4 Jul 2012, Subhro Sankha Kar wrote: >=20 >> On 04-Jul-2012, at 1:59 AM, Lars Eighner wrote: >>=20 >>> On Wed, 4 Jul 2012, Subhro Sankha Kar wrote: >>>=20 >>>> Hello, >>>>=20 >>>> On 03-Jul-2012, at 9:14 PM, Tobias Rehbein wrote: >>>>=20 >>>>> Am Tue, Jul 03, 2012 at 01:04:07AM -0500 schrieb Lars Eighner: >>>>>>=20 >>>>>> Call me crazy, but it seems that since the perl bump (5.12 -> = threaded-5.16) >>>>>> when firefox (13.0.1,1) got rebuilt, it seems twitter pages do = not fully >>>>>> load, give me the slow loading banner, and the page (not browser = or X) >>>>>> freezes, but no such problems were evident before, and twitter = seems >>>>>> entirely normal in Opera 12.00. >>>>=20 >>>>>=20 >>>>> Disabling SPDY in about:config (a solution proposed on the net) = didn't fix >>>>> this issue. >=20 >>=20 Let us for a minute assume that there is nothing wrong with FF. How = about installing Firebug and see in the "Net" tab that what precisely is = happening when you load the Twitter main page? Is it waiting for = apparently no reason at a particular place? Also, not strictly required, = but can you also pass the traffic through something like LiveHTTPHeaders = and post a traffic dump? As a third step, run a "pcap" session and see = what is happening on the wire/air ? >=20 > Adapter Description > GLXtest process failed (exited with status 1): GLX version older = / > than the required 1.3 >=20 > WebGL Renderer: > Blocked for your graphics card because of unresolved driver = issues. >=20 > GPU Accelerated Windows: 0. Blocked for your graphics driver version. = / > Try updating your graphics driver to version / > <Anything with EXT_texture_from_pixmap support> or newer. This probably means that none of the "advanced" rendering stuff work on = your X setup. >=20 > The only drivers that work with this machine (Intel G33) are intel and = vesa. > The intel driver does occasionally freeze X entirely requiring a boot, = but > this is not what happens when trying to load twitter pages. This is a completely distinct problem but probably it would be = interesting to try and figure out why Graphics Acceleration is not = working. I have very limited experience with Intel Graphics chipsets. In = the i915 days, there used to be something called AIGLX which required = some explicit configuration in xorg.conf. Could you check on that? Thanks -- Subhro Sankha Kar System Administrator Working and Playing with FreeBSD since 2002=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39A6D581-F4C3-4A50-AD3E-9ED0BF52F396>