Question How to get terminal output from a system without GPU?

[Blazing Blast]

I have built a system without integrated non dedicated GPU for server usage, and I want to get terminal output. I have another system that I can plug the boot drive in to install the OS to. In the long term, I want to set up SSH. But I need some way of interfacing with the PC during the SSH setup process. Is there a way to do this before installing SSH and without getting a GPU?

 

[ex_bubblehead]

You need some sort of video adapter in the server, whether discrete or integrated. This cannot be bypassed.

 

[Blazing Blast]

You need some sort of video adapter in the server, whether discrete or integrated. This cannot be bypassed.

I do want to confirm that I am able to boot into a USB and type in commands blindly. My PC does respond to it (it responds to the shutdown command). I just need a way to install Arch and setup an SSH server with minimal human interaction.

 

[Eximo]

Install GPU, setup, remove GPU. The common method.

Doesn't have to be pretty either, and you can pick up cheap GPUs and a 1x PCIe riser cable. Also some USB video adapters. Not sure how well those play with Arch though.

 

[ex_bubblehead]

I do want to confirm that I am able to boot into a USB and type in commands blindly. My PC does respond to it (it responds to the shutdown command). I just need a way to install Arch and setup an SSH server with minimal human interaction.

That doesn't in any way change things.

 

[Blazing Blast]

That doesn't in any way change things.

Could you please elaborate? In what part of that process do I need a graphics adapter?

 

[ex_bubblehead]

Could you please elaborate? In what part of that process do I need a graphics adapter?

How do you expect to receive (and see) any error messages? (and there will be when blindly typing). There will also be the inevitable console errors displayed. How do you expect to be made aware of those without a display?

 

[Blazing Blast]

How do you expect to receive (and see) any error messages? (and there will be when blindly typing).

I want to automate it as much as possible. I have another system with graphics output that I want to reinstall anyway, so I can use that to debug whatever automated installer I choose. And then I have a laptop that I can use to flash the USB drives needed for the installation.

 

[ex_bubblehead]

I want to automate it as much as possible. I have another system with graphics output that I want to reinstall anyway, so I can use that to debug whatever automated installer I choose. And then I have a laptop that I can use to flash the USB drives needed for the installation.

Unless you are somehow redirecting output to a printer or terminal you MUST have some form of display attached to the target system.

 

[Blazing Blast]

Unless you are somehow redirecting output to a printer or terminal you MUST have some form of display attached to the target system.

The idea is to automate it to the point of installing the OS and setting it up to launch an SSH server autonomously, and maybe activating the system beeper once it's ready. Then, I should be able to connect to it using another machine and complete the setup from there.

 

[ex_bubblehead]

The idea is to automate it to the point of installing the OS and setting it up to launch an SSH server autonomously, and maybe activating the system beeper once it's ready. Then, I should be able to connect to it using another machine and complete the setup from there.

Not practical. But then again it's your party/funeral

 

[Blazing Blast]

Not practical. But then again it's your party/funeral

I am hoping that I can get 95% of the way there by marking an ArchISO that includes a fork of ArchInstaller. Then I'd only need to do the script to configure and autolaunch SSH myself. It can't be much worse than that time I automated compiling and installing the kernel.

 

[USAFRet]

The idea is to automate it to the point of installing the OS and setting it up to launch an SSH server autonomously, and maybe activating the system beeper once it's ready. Then, I should be able to connect to it using another machine and complete the setup from there.

To build the script, you do it on a system with a video output.
This allows you to see the myriad errors that result in the many repeats of building the script.

Once it is done and run through more than once, with no errors....then you can apply that script to some new system, blind.

At work, I build lots of things that run blind and unattended.
"Enter this command and let it run"

But to build it...I need to see what it is doing.

 

[Blazing Blast]

To build the script, you do it on a system with a video output.
This allows you to see the myriad errors that result in the many repeats of building the script.

Once it is done and run through more than once, with no errors....then you can apply that script to some new system, blind.

At work, I build lots of things that run blind and unattended.
"Enter this command and let it run"

But to build it...I need to see what it is doing.

Indeed, that is what my idea was with the 3rd most recent message (excluding this one).