Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
04-14-2019, 03:27 AM
|
#1
|
LQ Newbie
Registered: Dec 2018
Posts: 15
Rep: 
|
Maintain Connection To Headless Debian Server During Reboot
Hi, I have a headless server running Debian and I only manage it using CLI over SSH and 99% of the time this is OK.
However, if something were to happen during boot sequence I would have to go down to the basement and get an old monitor (and keyboard) I keep just for this purpose (VGA) and it's all just a hassle.
My Question is: Is there a hardware where I can maintain connection to the server during reboots/etc by having VGA and USB connected on one side and network (preferably WiFi) on the other side. Maybe using telnet?
What I've done so far: Googled the subject an insane amount from time to time over the past year but I just can't seem to find the correct terminology for what I'm searching for.
Thank you all! 
|
|
|
04-14-2019, 04:11 AM
|
#2
|
LQ Addict
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316
|
Perhaps it's built-in already? E.g. Proliants have iLO, Dell servers have DRAC etc. They allow you to view the console via the network.
If not, and if you can enable a serial console, use a Raspberry Pi or other small server. While the small server might not have a serial connector, you can either wire one using GPIO or use a USB-to-serial cable.
I found several tutorials, like this one https://networklessons.com/uncategor...console-server, by searching for raspberry console server.
Last edited by berndbausch; 04-14-2019 at 04:13 AM.
|
|
|
04-14-2019, 04:25 AM
|
#3
|
Moderator
Registered: Aug 2002
Posts: 26,741
|
There are KVM over IP devices that could be connected to a wireless extender. That would allow you to connect and see all the BIOS boot messages.
They are not cheap so it depends on what that 1% is worth...
|
|
|
04-14-2019, 04:57 AM
|
#4
|
LQ Guru
Registered: Apr 2005
Distribution: Linux Mint, Devuan, OpenBSD
Posts: 7,743
|
Quote:
Originally Posted by berndbausch
If not, and if you can enable a serial console, use a Raspberry Pi or other small server. While the small server might not have a serial connector, you can either wire one using GPIO or use a USB-to-serial cable.
|
If it does not have a serial port built-in then it is not really a server. 
|
|
|
04-14-2019, 05:36 AM
|
#5
|
LQ Newbie
Registered: Dec 2018
Posts: 15
Original Poster
Rep: 
|
Quote:
Originally Posted by michaelk
There are KVM over IP devices that could be connected to a wireless extender. That would allow you to connect and see all the BIOS boot messages.
They are not cheap so it depends on what that 1% is worth...
|
Aaah, that sounds like the solution I'm looking for. Although the price, as you say, might not be worth it from what I've found so far.
I wished there were something like this: https://www.aten.com/au/en/products/...sories/ka7570/
But where I could connect directly to the "KVM over IP-module" without the the need for a KVM-switch.
Do you know of something like that?
berndbausch & Turbocapitalist: Sorry I should have specified that the hardware ain't an enterprise server, it's just an ATX with lots of disks etc. No serial from what I can read on the specs.
|
|
|
04-14-2019, 07:23 AM
|
#6
|
Moderator
Registered: Aug 2002
Posts: 26,741
|
I don't know how that particular device works.
Last edited by michaelk; 04-14-2019 at 07:45 AM.
|
|
|
04-22-2019, 06:54 AM
|
#7
|
LQ Newbie
Registered: Dec 2018
Posts: 15
Original Poster
Rep: 
|
Thanks for your help everyone. It got me on the right track 
|
|
|
04-22-2019, 09:31 AM
|
#8
|
LQ Veteran
Registered: Feb 2013
Location: Tucson, AZ, USA
Distribution: Rocky 9.5
Posts: 5,885
|
Quote:
Originally Posted by MrBamse
Thanks for your help everyone. It got me on the right track 
|
Please share your solution here once you figure it out. Thanks!
|
|
|
04-22-2019, 11:25 AM
|
#9
|
LQ Newbie
Registered: Dec 2018
Posts: 15
Original Poster
Rep: 
|
Sure thing, I'll see if I go about trying a solution. The current options seem to expensive.
|
|
|
04-22-2019, 12:06 PM
|
#11
|
Moderator
Registered: Aug 2002
Posts: 26,741
|
A remote system console would let you see the boot messages but not bootloader or BIOS messages. You didn't post what problems you encounter so it just depends.
|
|
|
04-22-2019, 02:02 PM
|
#12
|
LQ Newbie
Registered: Dec 2018
Posts: 15
Original Poster
Rep: 
|
Quote:
Originally Posted by pan64
|
Cool thanks 
|
|
|
04-22-2019, 02:07 PM
|
#13
|
LQ Newbie
Registered: Dec 2018
Posts: 15
Original Poster
Rep: 
|
Quote:
Originally Posted by michaelk
A remote system console would let you see the boot messages but not bootloader or BIOS messages. You didn't post what problems you encounter so it just depends.
|
Sorry for not specifying further earlier. But the most "common" issues I've had have occured during OS boot (fstab errors etc, or sometimes it takes longer that usual and its probably running a diskcheck and it would be nice to see). Once it was an error with GRUB.
Sorry for being dumb, but what is a "remote system console"?
|
|
|
04-22-2019, 03:43 PM
|
#14
|
Moderator
Registered: Aug 2002
Posts: 26,741
|
The system console displays the boot and administrator messages and now days is attached to tty1 by default. There are 6 virtual terminals that you can switch between them by using the alt-F1 to alt-F6 keys and the desktop uses F7. In the old days before PCs all terminals were connected to the server using RS232 (serial) wiring and the system console was a special dedicated terminal.
You can still create a dedicated system console using RS-232 by adding a kernel boot option. The serial port is connected to another computer and the console accessed via a terminal application like PuTTy or minicom. In the link that pan64 posted the serial console is connected to a Raspberry Pi (USB RS-232 adapter) and then using a special service converts the RS232 data to ethernet. You can then access the system console by connecting to the Pi using that port.
While the link use telnet you can create a virtual tty port using socat and access the console using any application with a device ID.
https://techtinkering.com/2013/04/02...rt-over-tcpip/
|
|
|
04-23-2019, 12:26 AM
|
#15
|
LQ Newbie
Registered: Dec 2018
Posts: 15
Original Poster
Rep: 
|
Quote:
Originally Posted by michaelk
The system console displays the boot and administrator messages and now days is attached to tty1 by default. There are 6 virtual terminals that you can switch between them by using the alt-F1 to alt-F6 keys and the desktop uses F7. In the old days before PCs all terminals were connected to the server using RS232 (serial) wiring and the system console was a special dedicated terminal.
You can still create a dedicated system console using RS-232 by adding a kernel boot option. The serial port is connected to another computer and the console accessed via a terminal application like PuTTy or minicom. In the link that pan64 posted the serial console is connected to a Raspberry Pi (USB RS-232 adapter) and then using a special service converts the RS232 data to ethernet. You can then access the system console by connecting to the Pi using that port.
While the link use telnet you can create a virtual tty port using socat and access the console using any application with a device ID.
https://techtinkering.com/2013/04/02...rt-over-tcpip/
|
Cool! Can ser2net be started before SSHD and do you need a physical serial port?
|
|
|
All times are GMT -5. The time now is 11:58 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|