Ps3 Debug Settings Installer
Eustacio Gadit
The installer will guide you through the setup, allowing you to partition thelocal disk(s), apply basic system configurations (for example, timezone,language, network) and install all required packages. This process should nottake more than a few minutes. Installing with the provided ISO is therecommended method for new and existing users.
Starts the terminal-mode installation wizard. It provides the same overallinstallation experience as the graphical installer, but has generally bettercompatibility with very old and very new hardware.
Starts the terminal-mode installation wizard, additionally setting up the Linuxkernel to use the (first) serial port of the machine for in- and output. Thiscan be used if the machine is completely headless and only has a serial consoleavailable.
Starts the installation in debug mode. A console will be opened at severalinstallation steps. This helps to debug the situation if something goes wrong.To exit a debug console, press CTRL-D. This option can be used to boot a livesystem with all basic tools available. You can use it, for example, torepair a degraded ZFS rpool or fix thebootloader for an existing Proxmox VE setup.
With this option you can boot an existing installation. It searches all attachedhard disks. If it finds an existing installation, it boots directly into thatdisk using the Linux kernel from the ISO. This can be useful if there areproblems with the bootloader (GRUB/systemd-boot) or the BIOS/UEFI is unable toread the boot block from the disk.
The Options button lets you select the target file system, whichdefaults to ext4. The installer uses LVM if you selectext4 or xfs as a file system, and offers additional options torestrict LVM space (see below).
The next page asks for basic configuration options like your location, timezone, and keyboard layout. The location is used to select a nearby downloadserver, in order to increase the speed of updates. The installer is usually ableto auto-detect these settings, so you only need to change them in raresituations when auto-detection fails, or when you want to use a keyboard layoutnot commonly used in your country.
Avoid character repetition, keyboard patterns, common dictionary words, letter or number sequences, usernames, relative or pet names, romantic links (current or past), and biographical information (for example ID numbers, ancestors' names or dates).
The last step is the network configuration. Network interfaces that are UPshow a filled circle in front of their name in the drop down menu. Please notethat during installation you can either specify an IPv4 or IPv6 address, but notboth. To configure a dual stack node, add additional IP addresses after theinstallation.
After clicking Install, the installer will begin to format the disks and copypackages to the target disk(s). Please wait until this step has finished; thenremove the installation medium and restart your system.
Upload your subscription key to gain access to the Enterprise repository. Otherwise, you will need to set up one of the public, less tested package repositories to get updates for security fixes, bug fixes, and new features.
Defines the total hard disk size to be used. This way you can reserve free spaceon the hard disk for further partitioning (for example for an additional PV andVG on the same hard disk that can be used for LVM storage).
The installer creates the ZFS pool rpool, if ZFS is used. No swap space iscreated but you can reserve some unpartitioned space on the install disks forswap. You can also create a swap zvol after the installation, although this canlead to problems (see ZFS swap notes).
Defines the ashift value for the created pool. The ashift needs to be set atleast to the sector-size of the underlying disks (2 to the power of ashift isthe sector-size), or any disk which might be put in the pool (for example thereplacement of a defective disk).
Defines the total hard disk size to be used. This is useful to save free spaceon the hard disk(s) for further partitioning (for example to create aswap-partition). hdsize is only honored for bootable disks, that is only thefirst disk or mirror for RAID0, RAID1 or RAID10, and all disks in RAID-Z[123].
Problems may arise on very old or very new hardware due to graphics drivers. Ifthe installation hangs during boot, you can try adding the nomodesetparameter. This prevents the Linux kernel from loading any graphics drivers andforces it to continue using the BIOS/UEFI-provided framebuffer.
On the Proxmox VE bootloader menu, navigate to Install Proxmox VE (Terminal UI) andpress e to edit the entry. Using the arrow keys, navigate to the line startingwith linux, move the cursor to the end of that line and add theparameter nomodeset, separated by a space from the pre-existing lastparameter.
It is possible to install Proxmox VE automatically in an unattended manner. Thisenables you to fully automate the setup process on bare-metal. Once theinstallation is complete and the host has booted up, automation tools likeAnsible can be used to further configure the installation.
For packages that have the PHP version in the package name, such as inphp81-php-xdebug3, you can substitute the PHPversion with the one that matches the PHP version that you are running.
In some cases pecl will change the php.ini file toadd a configuration line to load Xdebug. You can check whether it did byrunning php -v. If Xdebug shows up with a version number, thanyou're all set and you can configure Xdebug's other functions, such asStep Debugging, or Profiling.
On Apple M1 hardware, programs can either be compiled for the native M1/ARM64architecture, or for the emulated x86_64 architecure. Sometimes there is amismatch with the default and PECL will fail, or Xdebug won't load with amessage such as:
You compile Xdebug separately from the rest of PHP. You need access to thescripts phpize and php-config. If your systemdoes not have phpize and php-config, you willneed to install the PHP development headers.
It is important that the source version matches the installed version as thereare slight, but important, differences between PHP versions. Once you haveaccess to phpize and php-config, take thefollowing steps:
If phpize is not in your path, please make surethat it is, by expanding the PATH environment variable. Make sureyou use the phpize that belongs to the PHP version that you want to use Xdebugwith. See this FAQ entry if you're having someissues with finding which phpize to use.
With Xdebug loaded, you can now enable individual features, such asStep Debugging, or Profiling. Information on what these featers are,how they work, and how to configure them is available on each feature'sdocumentation page:
This video teaches you how to troubleshoot your Xdebug setup. It explains how to find out how Xdebug is configured, which settings have been made, and what it is attempting to do regarding its different features.
All warnings and errors are described on the Description of errors page, withdetailed instructions on how to resolve the problem, if possible. All errors are always logged throughPHP's internal logging mechanism (configured with error_login php.ini). All warnings and errors also show up in thediagnostics log that you can view by calling xdebug_info().
You can also set Xdebug's mode by setting the XDEBUG_MODEenvironment variable on the command-line; this will take precedence over thexdebug.mode setting, but will not change the value of the xdebug.modesetting.
InstallBuilder provides a number of features to help you debug failing installations. Installations can fail either because of internal factors (such as faulty logic) or external factors (such as runningout of disk space)
InstallBuilder allows including an embedded debugger within your installers. This built-in debugger makes easier to identify and correct issues, speeding and simplifying installer development. Its main features, detailed in successive sections, are:
As the debugger is only available in xwindow, win32, osx and unattended modes, calling the installer with --enable-debugger will also reconfigure the graphical mode to the appropriate one in the running platform:
After the debugger is initialized, it will keep waiting until the run button is clicked, and then the installer will start the installation (the ). This allows you to set the appropriate breakpoints in those sections of your project that require debugging.
Disable Debugger: When the debugger is disabled, it does not stop at breakpoints or log messages. This speeds up the execution in big projects until the installation reaches the desired point or simply lets the installation finish after you are done with the debugging.
The project tree editor allows basic modifications of the project. It is especially useful when the debugger is initialized, before the execution of the installer starts, to set breakpoints in the desired actions to debug.
When an action list contains a breakpoint (either in the action list or in any of its child actions) or the debugger stops at it because of a step, it is loaded in the Action List Execution Editor. The action list is represented in a tree with a left strip, displaying the breakpoints (represented by red dots) of the actions and the action being executed (marked by an orange arrow).
Skip: When the debugger is stopped at a breakpoint or because it was performing an step, clicking on the Skip button will make the debugger jump to the next action. In the figure, the next action is a action, by clicking Skip, the debugger will not execute it and step into the next one, the .
Repeat: This button makes the debugger execute the current action without stepping into the next one afterwards. This is useful for troubleshooting an action that is failing by trial and error, for example, a regexp not matching.
The debugger log allows configuring which elements to log as well as the verbosity and color of the messages. These settings can be configured in the Log section of the Configure->Preferences menu. The configurable elements to log are:
c80f0f1006