I'm going to disagree with the assessment of memory problems, this does appear to be a hardware or driver issue.. but the system shouldn't be locking up, as it does appear the the X server is trying to terminate.

I suppose for the time being you can use the vesa vbe driver instead, it will be slow.. but you should at least get a desktop.

You should let it continue uninterrupted for at least 24 hours. If testing is interrupted, you will need to start over.

2 12-hour tests != 1 24-hour test

Once testing is complete, report the results.

Here is my assessment thus far:

I am asking you to exhaustively test memory because I suspect you cannot account for how this system has been used/treated during its lifespan. Even if you have such knowledge, it is an old system. Thoroughly testing memory now is information which may be useful later -- assuming it is deemed good memory.

If testing does not reveal anything, try BSDfan666's idea of switching to the VESA driver.

It is interesting that you did not test X before installing so many packages. Verifying base system functionality immediately after installation is a more systematic approach than waiting after lots of third-party applications have been installed. It's a more complicated environment now.

The df(1) output also points out something which you will need to monitor throughout the lifetime of this particular installation. Instead of me simply telling you what it is, I'm going to treat this as a teaching moment (while you are waiting for memory testing to complete). So here's the question:

I can understand many thing from df
when I run this command I understand how much space have in each partitions
when I run this command I understand how partitioning my hard disk
when I run this command I understand which partition is full , and this help me to solve some problem for example sometimes when tmp partition is full my system can do anything and maybe it make problem foe my hard disk and my OS
df has many options and this options help me I get better information about Free space and my hard disk .

1-this hard disk has 9 partitions
2- frist partitions is root , this partition has 1005 MB space and 42 MB use by file and 912 MB is free
3- another partition is /home and this partition is 13.4 GB and 364 MB us by file and 12.4 is free
4- another partition is /tmp and this partition is 1.8 GB and 6.0 K use by file and 1.7 GB is free
5- another partition is /usr and this partition is 1021 MB and 928 MB use by file and 42 MB is free , I think this partition dose not have enough free space and free space is not enough .
6- another partition is /usr/X11R6 and this partition is 1005 MB and 145 MB is use by file and 809 MB is free
7- another partition is /usr/local and this partition is 3 GB and 909 MB use by file and 2 GB is free
8- another partition is /usr/obj and this partition is 1.6 GB and 2 K use by file and 1.5 GB is free
9- another partition is /usr/src and this partition is 1.6 GB and 2 K use by file and 1.5 GB is free
10- another partition is /var and this partition is 2.8 GB and 32 MB use by file and 2.7 GB is free

Your /usr partition is essentially full. Hopefully, you have added most of the applications you intent to add. If you intend to add many more, you are running into the chance that /usr will fill completely up preventing you from either completing the installation of the application being installed or any other application.

Auto-partitioning (as BSDfan666 already states...) is simply one way that partitions can be sized. Auto-partitioning cannot guarantee that the partition sizes created will work in all situations. Because you had added so many applications, you have nearly filled up /usr.

You should monitor partition sizes throughout the life of this particular installation watching to see if /usr fills completely up. If it does, you may be forced to re-install.

You should expect that when you move to OpenBSD 4.7, you should do a fresh installation, not upgrade. Upgrading does not allow partition sizes to be changed.

If you look at the sizes of the other partitions, /home doesn't need to be 13GB in size. If in future installations you intend to install the same applications, shrink the size of /home & increase the size of /usr. Yes, this means that you will have to manually size the partitions yourself. Write down in a notebook what sizes work best for you, & refer to this information when you reinstall.

The fact that /usr has filled up the space allotted is not a reason to be concerned unless you intend to add more applications. Simply run df(1) on a regular basis & monitor its size.

Your /usr partition is essentially full. Hopefully, you have added most of the applications you intent to add. If you intend to add many more, you are running into the chance that /usr will fill completely up preventing you from either completing the installation of the application being installed or any other application.

Auto-partitioning (as BSDfan666 already states...) is simply one way that partitions can be sized. Auto-partitioning cannot guarantee that the partition sizes created will work in all situations. Because you had added so many applications, you have nearly filled up /usr.

You should monitor partition sizes throughout the life of this particular installation watching to see if /usr fills completely up. If it does, you may be forced to re-install.

Most likely, you should expect that when you move to OpenBSD 4.7, you should do a fresh installation, not upgrade. Upgrading does not allow partition sizes to be changed.

If you look at the sizes of the other partitions, /home doesn't need to be 13GB in size. If in future installations you intend to install the same applications, shrink the size of /home & increase the size of /usr. Yes, this means that you will have to manually size the partitions yourself. Write down in a notebook what sizes work best for you, & refer to this information when you reinstall.

The fact that /usr has filled up the space allotted is not a reason to be concerned unless you intend to add more applications. Simply run df(1) on a regular basis & monitor its size.

Can say to OpenBSD use home partition and install application in home partititons

Can say to OpenBSD use home partition and install application in home partititons

From the pkg_add(1) man page:

Quote:

-Llocalbase
Install a package under localbase. By default, localbase equals/usr/local, and specifying it is not necessary. However,
packages can be created using a different localbase (see
and those packages can only be installed by
pkg_create(1)), using the same localbase. See bsd.port.mk(5) for a description
of LOCALBASE.

Warning #1: $PATH will need to be altered to use another directory structure.

Warning #2: This will not eliminate the use of /var for data structures deployed by a package.

You should let it continue uninterrupted for at least 24 hours. If testing is interrupted, you will need to start over.

2 12-hour tests != 1 24-hour test

Once testing is complete, report the results.

Here is my assessment thus far:

I am asking you to exhaustively test memory because I suspect you cannot account for how this system has been used/treated during its lifespan. Even if you have such knowledge, it is an old system. Thoroughly testing memory now is information which may be useful later -- assuming it is deemed good memory.

If testing does not reveal anything, try BSDfan666's idea of switching to the VESA driver.

It is interesting that you did not test X before installing so many packages. Verifying base system functionality immediately after installation is a more systematic approach than waiting after lots of third-party applications have been installed. It's a more complicated environment now.

The df(1) output also points out something which you will need to monitor throughout the lifetime of this particular installation. Instead of me simply telling you what it is, I'm going to treat this as a teaching moment (while you are waiting for memory testing to complete). So here's the question: