Xorg Video Wizard runs after every reboot

[bucketmouse]

Hey, everybody! I recently installed Puppy Linux 5.0.1. It was a full install to a partition on my hard drive and everything went smooth and everything is working great except for one thing that is more of an annoyance than a problem really.

Sometimes when I shutdown and then restart, the Xord Video Wizard starts. Why is Puppy not saving my xorg.conf?

[RetroTechGuy]

Hey, everybody! I recently installed Puppy Linux 5.0.1. It was a full install to a partition on my hard drive and everything went smooth and everything is working great except for one thing that is more of an annoyance than a problem really.

Sometimes when I shutdown and then restart, the Xord Video Wizard starts. Why is Puppy not saving my xorg.conf?

I have seen that under Puppy 4.3.1

I think it has to do (at least partially) with not umounting the pupsave cleanly.

What I've found that clears it up, is boot normally. If it asks you to configure xorg, do it. Then when fully booted, run the xorg video wizard wizard, and fully rebuild the config files (yeah, you thought that you just did that, but I'm not sure that you did...).

The only other thing that I've seen confuse the Puppy video is my KVM (when I do not wait for Puppy to fully boot before switching to the other computer).

[samarai]

choose "probe" or "vesa"

or you can refer this post

[Béèm]

Hey, everybody! I recently installed Puppy Linux 5.0.1. It was a full install to a partition on my hard drive and everything went smooth and everything is working great except for one thing that is more of an annoyance than a problem really.

Sometimes when I shutdown and then restart, the Xord Video Wizard starts. Why is Puppy not saving my xorg.conf?

I have seen that under Puppy 4.3.1

I think it has to do (at least partially) with not umounting the pupsave cleanly.

What I've found that clears it up, is boot normally. If it asks you to configure xorg, do it. Then when fully booted, run the xorg video wizard wizard, and fully rebuild the config files (yeah, you thought that you just did that, but I'm not sure that you did...).

The only other thing that I've seen confuse the Puppy video is my KVM (when I do not wait for Puppy to fully boot before switching to the other computer).

The OP has a full install.
So there is no save file involved.

[looseSCREWorTWO]

I had Puppy Lucid running as a Full Install on an old laptop and it did the same thing. Also I had to run ALSA setup to get sound working - then next re-boot it had "forgotten" the Xorg and ALSA settings, so I had to re-do everything all over again.

In the end I ditched the Full Install, replaced it with a Frugal Install and none of these problems happened. And the PC didn't run any slower or hotter. Performance was the same under Frugal as under a Full Install.

[Béèm]

bucketmouse, please post your system specs.
Alternatively, you can use the puppysearch link in my sig and try to find post concerning your system model.

[RetroTechGuy]

Hey, everybody! I recently installed Puppy Linux 5.0.1. It was a full install to a partition on my hard drive and everything went smooth and everything is working great except for one thing that is more of an annoyance than a problem really.

Sometimes when I shutdown and then restart, the Xord Video Wizard starts. Why is Puppy not saving my xorg.conf?

I have seen that under Puppy 4.3.1

I think it has to do (at least partially) with not umounting the pupsave cleanly.

What I've found that clears it up, is boot normally. If it asks you to configure xorg, do it. Then when fully booted, run the xorg video wizard wizard, and fully rebuild the config files (yeah, you thought that you just did that, but I'm not sure that you did...).

The only other thing that I've seen confuse the Puppy video is my KVM (when I do not wait for Puppy to fully boot before switching to the other computer).

The OP has a full install.
So there is no save file involved.

There are lots of saved files in a full install, or otherwise.

I don't believe that a full install negates the possibility of an unclean dismount (I run a frugal, so I can't tell you if the FS umount is consistently clean).

When I see the behavior described, it looks like Puppy is not doing a full xorg rebuild, though it probably should if it's having that sort of error. Using the wizard forces a full xorg rebuild, and then the problem seems to go away.

The KVM issue is simply that Puppy can't directly see the monitor attached, but only the KVM...and thinks that you hooked it to a new device.

[Béèm]

In a full install there is no pupsave file which is to be unmounted at the end of the session. There is only a pupsave in a frugal install.
During the session, it's clear that files are updated and saved as there is a need for it.

It has been occurred already that the partition on which a full install is made got corrupted. A file check can get the file systel correct again, but it is no guarantee that installation can still be used.

[RetroTechGuy]

In a full install there is no pupsave file which is to be unmounted at the end of the session. There is only a pupsave in a frugal install.
During the session, it's clear that files are updated and saved as there is a need for it.

It has been occurred already that the partition on which a full install is made got corrupted. A file check can get the file systel correct again, but it is no guarantee that installation can still be used.

But the pupsave is simply the file system. If I crash out of the full install filesystem, I still have crashed (and potentially corrupted) the filesystem. And thus I suspect you would get the same effect (with the pupsave, there was the problem that it ALWAYS crashed out, so it was always potentially damaged -- BTW I recently installed the patch to make the pupsave shutdown clean -- works great).