[SOLVED] Serious problems with GDB on Porteus 3.0

[gfabbrocino]

I downloaded and installed the gdb package with usm, but on reboot when the Porteus read the package gdb, the machine is turned off.

[fanthom]

hi gfabbrocino,

very interesting case
please boot in 'Always Fresh' mode (external modules wont be loaded) and upload this gdb module somewhere so i can check what's wrong with it.

thanks

[gfabbrocino]

Hello fanthom,
I am afraid that the problem lies not in the package GDB, but it is an instability of the system, at least on my machine.
The same problem happened even just running the update package from USM.
It seems that every change in the system, reboot the system fails to rise.
In practice, it loads all the modules and the time when start xorg for the opening of the screen, the machine turns off.
Maybe it could be a problem with the video card, but I can not explain why the system in "fresh mode" or "without modification", functions perfectly.
This defect was absent in the previous version od Porteus, in any case, tomorrow I try on different hardware.

[brokenman]

but I can not explain why the system in "fresh mode" or "without modification", functions perfectly.

Try booting into fresh mode. Download your package. Put the resulting module into the porteus/modules folder and reboot without using changes= cheatcode. Does it crash?

[gfabbrocino]

do not crash

[brokenman]

Then the problem lies somewhere in your changes. Difficult to troubleshoot since we don't know exactly what you have changed.

[francois]

Best thing to do is to save your save changes folder under another name and restart the building of your environment anew.

Once you have your basic de settle down you can save it for future use in case of corruption of the save changes folder.

There is the Porteus save session utility, which will save the de in the form of a file, afolder, or a module, see:
kde > applications > system > disquette icon > porteus save session.

[gfabbrocino]

the change was the upgrade of all the repository, with "usm -u all".
On reboot after loading packages *xzm, the machine turn off.
I think it's a problem with hardware, in particular with the video card.
I have to do a test with different hardware.

[gfabbrocino]

I did another test, I removed the folder changes, I restarted the system and the result was ok!
I again made ​​some settings, like language setting, update the repository (usm-u all), I then rebooted the system.
The problem is presented, but this time the computer was not shut down, but was stopped at the login in text mode.
I logged in and I run startx, and the system displays the error messages on the graphics card.

[dstruct2k]

I did another test, I removed the folder changes, I restarted the system and the result was ok!
I again made ​​some settings, like language setting, update the repository (usm-u all), I then rebooted the system.
The problem is presented, but this time the computer was not shut down, but was stopped at the login in text mode.
I logged in and I run startx, and the system displays the error messages on the graphics card.

Even a full-on kernel panic shouldn't cause a reboot; You should see a textmode error screen if any software is at fault. It sounds much more likely that you've got failing hardware that needs to be replaced.

In my experience, it's quite likely that during the first boot (or in "always fresh" mode), the GPU (or another related component such as the northbridge, etc) is being run with "basic" drivers, and after a reboot more model-specific drivers are being loaded and attempting to use hardware-specific functions that don't work due to the hardware issues, causing your reboots.

Again, software alone should never "just reboot" the machine without first telling you why. Only Windows reboots without telling you what's going on (if BSoDs are disabled, like they are by default); Porteus (and Linux in general) is a lot more helpful.

[gfabbrocino]

I tested the system on a different hardware and it worked fine.
So it was the home PC that probably has some damage to the video card.
Thank you for your willingness.

[wread]

@gfabbrocino

Don't forget to add [SOLVED] to your post