64bit kernel, sorry for the typo. Edgar Merino
2009/4/25 Edgar Merino <donvodka at gmail.com> > Yes I'm sure this is a 65bit kernel, anyone else got a clue on what the > problem might be? maybe some logs I may have not seen, this is clearly a bug > in the X window system for solaris, I just don't know how to troubleshoot > this. > > Please help me out, any information would be greatly appreciated, > Edgar Merino > > > > > > 2009/4/24 Jasse Jansson <jasse at yberwaffe.com> > > >> On Apr 24, 2009, at 9:36 PM, Edgar Merino wrote: >> >> This is a 64bit system, the chip does not share memory with the cpu, it's >>> got it's own internal dedicated memory (nvidia 8500gt). I tried looking for >>> any option in the BIOS regarding RAM but had no luck. This happens only with >>> 4gb of memory, with less than that it all works fine. What else can I do to >>> troubleshoot this? anyone else had/having a similar problem? >>> >>> Edgar Merino >>> >> >> Are you sure that you are running a 64 bit kernel ? >> If you are then you have to ask someone else for clues. >> >> The memory hole BIOS setting works for me, but that machine is a few years >> old. >> >> >> >> >> >>> >>> >>> >>> >>> >>> Jasse Jansson escribi?: >>> >>>> >>>> On Apr 23, 2009, at 11:58 PM, Edgar Merino wrote: >>>> >>>> Hello, >>>>> >>>>> Today I upgraded my ram from 2gb to 4gb, to my surprise opensolaris >>>>> 2008.11 b109 booted but locked just before opening gdm, so I tried >>>>> different >>>>> bay configurations which resulted in the same. So I tested the new dimm >>>>> and >>>>> osol worked fine, added 1 dimm of the older 1gb and it kept working, then >>>>> added the the other 1gb dimm and the system was locked again. So I booted >>>>> to >>>>> osol using 3gb, disabled gdm and booted again using 4gb: it worked, but >>>>> when >>>>> trying to load X manually again the system locked. No error messages were >>>>> found in /var/adm/messages nor in /var/log/Xorg.0.log. >>>>> >>>>> What can I do to troubleshoot this? GNU/Linux and Windows XP are >>>>> working fine. >>>>> >>>> >>>> It seems to be a 32 bit system. >>>> >>>> Is it one with a gfx chip that shares memory with the cpu ? >>>> You might be running out of memory address space. >>>> >>>> If there is some "memory hole" options in the BIOS, try playing around >>>> with them. >>>> >>>> >>>> >>>>> System Specs >>>>> >>>>> SunOS powersolaris 5.11 snv_109 i86pc i386 i86pc >>>>> OpenSolaris 2009.06 snv_109 X86. >>>>> >>>>> Status of virtual processor 0 as of: 04/23/2009 16:56:31 on-line since >>>>> 04/23/2009 15:41:51. The i386 processor operates at 2200 MHz, and has an >>>>> i387 compatible floating point processor. >>>>> Status of virtual processor 1 as of: 04/23/2009 16:56:31 on-line since >>>>> 04/23/2009 15:41:54. The i386 processor operates at 2200 MHz, and has an >>>>> i387 compatible floating point processor. >>>>> >>>>> total: 819228k bytes allocated + 275644k reserved = 1094872k used, >>>>> 986040k available >>>>> >>>>> swapfile dev swaplo blocks free /dev/zvol/dsk/rpool/swap 182,1 8 >>>>> 2095096 2095096 >>>>> >>>>> System Configuration: Sun Microsystems i86pc Memory size: 3071 >>>>> Megabytes >>>>> >>>>> Edgar Merino >>>>> _______________________________________________ >>>>> xwin-discuss mailing list >>>>> xwin-discuss at opensolaris.org >>>>> >>>> >>>> >>>> >>>> >>>> Kaiser Jasse -- Authorized Stealth Oracle >>>> >>>> The axioms of wisdom: >>>> 1. Go the SPARC way of life >>>> 2. You can't conquer the universe without the knowledge of FORTRAN >>>> 3. In the Unix realm, 10% of work fixes 90% of the problems >>>> >>>> >>>> >>>> _______________________________________________ >>>> xwin-discuss mailing list >>>> xwin-discuss at opensolaris.org >>>> >>>> >>> >> >> >> >> Kaiser Jasse -- Authorized Stealth Oracle >> >> The axioms of wisdom: >> 1. Go the SPARC way of life >> 2. You can't conquer the universe without the knowledge of FORTRAN >> 3. In the Unix realm, 10% of work fixes 90% of the problems >> >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/xwin-discuss/attachments/20090425/b6cf5a0b/attachment.html>
