Re: !! SOLVED !! Re: [gentoo-user] New monitor problems. sighs
On Wednesday 15 December 2010 13:37:33 Dale wrote: J. Roeleveld wrote: On Wednesday 15 December 2010 12:39:27 Dale wrote: Pintér Tibor wrote: how about just checking the bloody Xorg logs to see what could have gone wrong? (/var/log/Xorg.0.log) That's where the errors came from that I posted in my first post. Here is the results of the latest test. I shut down the rig and unplugged the rig and monitor. Glad to see the monitor switched back to English too. It was Chinese or something. Anyway. Before the shutdown, I rebuilt the kernel, re-emerged the nvidia drivers and did a manual switch on opengl to nvidia. I let the rig sit there unplugged for about 30 minutes. I then booted it up. BIOS came up, I saw the services scroll up then it switched to vt7 and gave me a blinking cursor. It just sat there. I'm attaching both the new just tried xorg.conf and the xorg.log file. No grep or anything this time. Let me know if you see anything fishy or that needs changing. Thanks. Dale :-) :-) Ok, check your kernel config. The following error into google gave me a hint, [ 2082.101] (EE) NVIDIA(0): Failed to obtain a shared memory identifier: Function not [ 2082.101] (EE) NVIDIA(0): implemented http://www.nvnews.net/vbulletin/showthread.php?t=118109 This one says: Try enabling CONFIG_SYSVIPC. -- Joost You da man !!! That was it. Yeppie !!! I got my nice new monitor back. I bet this was what was wrong with the other monitor too. I'm happy so I'm not going to try it. Whew. I was about ready to try the ATI card too. Yuck !! lol THANKS MUCH !! Dale :-) :-) Am glad you got it working. Enjoy the new machine :) -- Joost
Re: !! SOLVED !! Re: [gentoo-user] New monitor problems. sighs
J. Roeleveld wrote: On Wednesday 15 December 2010 13:37:33 Dale wrote: J. Roeleveld wrote: Ok, check your kernel config. The following error into google gave me a hint, [ 2082.101] (EE) NVIDIA(0): Failed to obtain a shared memory identifier: Function not [ 2082.101] (EE) NVIDIA(0): implemented http://www.nvnews.net/vbulletin/showthread.php?t=118109 This one says: Try enabling CONFIG_SYSVIPC. -- Joost You da man !!! That was it. Yeppie !!! I got my nice new monitor back. I bet this was what was wrong with the other monitor too. I'm happy so I'm not going to try it. Whew. I was about ready to try the ATI card too. Yuck !! lol THANKS MUCH !! Dale :-) :-) Am glad you got it working. Enjoy the new machine :) -- Joost I went back and looked at the nvidia driver guide on gentoo.org. There is no mention of nvidia needing that. Should I tell the doc team so they can mention that for others or is my machine a little unique? Since someone else ran into it on the link you posted, it may be something that at least needs a mention even tho it is not nvidia specific. Thoughts? I like this thing. The rig is super fast and the monitor is really nice. These bad eyes can read this better. Thanks. Dale :-) :-)
Re: !! SOLVED !! Re: [gentoo-user] New monitor problems. sighs
On Wednesday 15 December 2010 08:26:11 Dale wrote: J. Roeleveld wrote: On Wednesday 15 December 2010 13:37:33 Dale wrote: J. Roeleveld wrote: snipped Am glad you got it working. Enjoy the new machine :) -- Joost I went back and looked at the nvidia driver guide on gentoo.org. There is no mention of nvidia needing that. Should I tell the doc team so they can mention that for others or is my machine a little unique? Since someone else ran into it on the link you posted, it may be something that at least needs a mention even tho it is not nvidia specific. Thoughts? Might be usefull to have it in the docs, but I think, as it is something other software requires as well, it might be an idea to stick it in the install- guide and in the ebuild-notes as well? Am wondering, isn't it in the X11 documents on the site yet? I like this thing. The rig is super fast and the monitor is really nice. These bad eyes can read this better. I've got the same CPU as you have, actually, just on an older mainboard. When I bought mine, I did stock it full with the max memory the board can take (8 gig). Not sure how much memory you have, but a 6Gig ramdisk mounted at /var/tmp/portage is sufficient to compile openoffice. That speeds things up even more ;) -- Joost
Re: !! SOLVED !! Re: [gentoo-user] New monitor problems. sighs
J. Roeleveld wrote: On Wednesday 15 December 2010 08:26:11 Dale wrote: J. Roeleveld wrote: On Wednesday 15 December 2010 13:37:33 Dale wrote: J. Roeleveld wrote: snipped Am glad you got it working. Enjoy the new machine :) -- Joost I went back and looked at the nvidia driver guide on gentoo.org. There is no mention of nvidia needing that. Should I tell the doc team so they can mention that for others or is my machine a little unique? Since someone else ran into it on the link you posted, it may be something that at least needs a mention even tho it is not nvidia specific. Thoughts? Might be usefull to have it in the docs, but I think, as it is something other software requires as well, it might be an idea to stick it in the install- guide and in the ebuild-notes as well? Am wondering, isn't it in the X11 documents on the site yet? I'll post it on gentoo-doc and see what they say. I like this thing. The rig is super fast and the monitor is really nice. These bad eyes can read this better. I've got the same CPU as you have, actually, just on an older mainboard. When I bought mine, I did stock it full with the max memory the board can take (8 gig). Not sure how much memory you have, but a 6Gig ramdisk mounted at /var/tmp/portage is sufficient to compile openoffice. That speeds things up even more ;) -- Joost Mine maxes out at 16Gbs. I have a single 4Gb stick in it right now. I plan to add a stick every few months until I get it full. Then I will have plenty of room to put portage on the ramdisk like you. It should be pretty fast then. I rarely use more than 1Gb tho. Even then, I have a lot of images open in Gimp or something to use that much. Now that my rig is fixed, I'm going to take a nap. I'm beat. Dale :-) :-)
Re: !! SOLVED !! Re: [gentoo-user] New monitor problems. sighs
On Wednesday 15 December 2010 13:33:03 J. Roeleveld wrote: Not sure how much memory you have, but a 6Gig ramdisk mounted at /var/tmp/portage is sufficient to compile openoffice. That speeds things up even more ;) The same size of tmpfs on /tmp also works even if you have only 4GB RAM, as I have. When it gets too full it just starts swapping. Actually, now that I check again, I see I've raised the size to 16G: $ grep 16G /etc/fstab tmpfs /tmp tmpfs nodev,nosuid,size=16G 0 0 $ grep swap /etc/fstab /dev/sda3 none swap sw,pri=10 0 0 /dev/sdb3 none swap sw,pri=10 0 0 /dev/sda7 none swap sw,pri=10 0 /dev/sdb7 none swap sw,pri=10 0 /dev/sdX3 are 2GB and /dev/sdX7 are 20GB (probably far too much swap, but disks are cheap). -- Rgds Peter. Linux Counter 5290, 1994-04-23.
Re: !! SOLVED !! Re: [gentoo-user] New monitor problems. sighs
Peter Humphrey wrote: On Wednesday 15 December 2010 13:33:03 J. Roeleveld wrote: Not sure how much memory you have, but a 6Gig ramdisk mounted at /var/tmp/portage is sufficient to compile openoffice. That speeds things up even more ;) The same size of tmpfs on /tmp also works even if you have only 4GB RAM, as I have. When it gets too full it just starts swapping. Actually, now that I check again, I see I've raised the size to 16G: $ grep 16G /etc/fstab tmpfs /tmp tmpfs nodev,nosuid,size=16G 0 0 $ grep swap /etc/fstab /dev/sda3 none swap sw,pri=10 0 0 /dev/sdb3 none swap sw,pri=10 0 0 /dev/sda7 none swap sw,pri=10 0 /dev/sdb7 none swap sw,pri=10 0 /dev/sdX3 are 2GB and /dev/sdX7 are 20GB (probably far too much swap, but disks are cheap). Interesting. I didn't know it would go to swap when it started getting full. Considering a emerge -e world takes about 3 days on my old rig and only takes about 10 hours on my new one, I already got a pretty good increase. We are always looking for more tho ain't we? lol Dale :-) :-)
Re: !! SOLVED !! Re: [gentoo-user] New monitor problems. sighs
On Wed, Dec 15, 2010 at 9:09 AM, Peter Humphrey pe...@humphrey.ukfsn.org wrote: On Wednesday 15 December 2010 13:33:03 J. Roeleveld wrote: Not sure how much memory you have, but a 6Gig ramdisk mounted at /var/tmp/portage is sufficient to compile openoffice. That speeds things up even more ;) The same size of tmpfs on /tmp also works even if you have only 4GB RAM, as I have. When it gets too full it just starts swapping. In my experience if it starts swapping, that is much slower than just using disk for /tmp in the first place. YMMV :)
Re: !! SOLVED !! Re: [gentoo-user] New monitor problems. sighs
Paul Hartman wrote: On Wed, Dec 15, 2010 at 9:09 AM, Peter Humphrey pe...@humphrey.ukfsn.org wrote: On Wednesday 15 December 2010 13:33:03 J. Roeleveld wrote: Not sure how much memory you have, but a 6Gig ramdisk mounted at /var/tmp/portage is sufficient to compile openoffice. That speeds things up even more ;) The same size of tmpfs on /tmp also works even if you have only 4GB RAM, as I have. When it gets too full it just starts swapping. In my experience if it starts swapping, that is much slower than just using disk for /tmp in the first place. YMMV :) My thought was that at least portage wouldn't stop the compile when it ran out of room. I usually put /var on a separate partition and always forget that OOo needs some space. I usually don't give it enough the first time around. Doesn't OOo need about 4 or 5Gbs now? Dale :-) :-)
Re: !! SOLVED !! Re: [gentoo-user] New monitor problems. sighs
I went back and looked at the nvidia driver guide on gentoo.org. There is no mention of nvidia needing that. Should I tell the doc team so they can mention that for others or is my machine a little unique? Since someone else ran into it on the link you posted, it may be something that at least needs a mention even tho it is not nvidia specific. Ideally it would be in the ebuild's kernel config checks. The Changelog mentions it; http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-drivers/nvidia-drivers/ChangeLog?view=markup But obviously its not in the ebuild you used.
Re: !! SOLVED !! Re: [gentoo-user] New monitor problems. sighs
On Wednesday 15 December 2010 20:35:15 Dale wrote: Paul Hartman wrote: On Wed, Dec 15, 2010 at 9:09 AM, Peter Humphrey pe...@humphrey.ukfsn.org wrote: On Wednesday 15 December 2010 13:33:03 J. Roeleveld wrote: Not sure how much memory you have, but a 6Gig ramdisk mounted at /var/tmp/portage is sufficient to compile openoffice. That speeds things up even more ;) The same size of tmpfs on /tmp also works even if you have only 4GB RAM, as I have. When it gets too full it just starts swapping. In my experience if it starts swapping, that is much slower than just using disk for /tmp in the first place. YMMV :) My thought was that at least portage wouldn't stop the compile when it ran out of room. I usually put /var on a separate partition and always forget that OOo needs some space. I usually don't give it enough the first time around. Doesn't OOo need about 4 or 5Gbs now? Dale :-) :-) Yes, provided you don't have debugging enabled for the resulting code. Apparently, that doubles the required size. -- Joost
