Re: serial console install

[David Wright]

On Mon 21 Nov 2022 at 13:02:13 (-0500), jeanrocco jr wrote:
> Hello, I just installed debian-11.5.0-amd64-netinst.iso on my APU2E4, which
> does not have a vga display but only a serial console.
> 
> I could not find any documentation in Debian regarding the "Debian
> GNU/Linux installer boot menu" where you have to type H (help), then TAB
> and type "boot: install console=ttyS0, 115200n8" and a few returns to make
> the installer aware there is no graphics card and to proceed with a serial
> install.  This site (
> https://teklager.se/en/knowledge-base/installing-debian-over-serial-console-apu-board/)
> explains how to do it, but I was expecting Debian to informs us that the
> installer works also for a serial install if you coax it properly.
> 
> Because of this there is a lot of well intended posts on the web about
> changes you have to make to get the serial install to works.
> 
> Im I missing something here ? Could you point me in the right direction
> please, thank's !

Using the bullet point Steps from the reference above:

Step
↓

1. https://www.debian.org/ and press the Download button. Top of page.

2. Immediately underneath that item, there's a link "USB sticks",
   which covers writing the stick. But before pressing it, best
   pick up the Installation Guide and Release Notes from lower
   down on the page.

3. Your reference assumes the use of a particular device and PuTTY.
   People with other hardware may use different connection methods, so
   that's not something that Debian covers for each and every device.

4. Turn to §5.1.7 in the Installation Guide, "The Boot Screen".
   The final boxed Note in that section covers how to get to the
   Help Index with H.

4—(the last sentence). For that, Debian provides the entirety of
   the Installation Guide. If you've used Debian in the past,
   then the Release Notes may keep you from making false assumptions
   based on previous experience that might be outdated. (They're
   principally aimed at people who are upgrading the previous release.)

5. That's §6.3.8.2 in the Installation Guide; and you're done.

Cheers,
David.

serial console install

[jeanrocco jr]

Hello, I just installed debian-11.5.0-amd64-netinst.iso on my APU2E4, which
does not have a vga display but only a serial console.

I could not find any documentation in Debian regarding the "Debian
GNU/Linux installer boot menu" where you have to type H (help), then TAB
and type "boot: install console=ttyS0, 115200n8" and a few returns to make
the installer aware there is no graphics card and to proceed with a serial
install.  This site (
https://teklager.se/en/knowledge-base/installing-debian-over-serial-console-apu-board/)
explains how to do it, but I was expecting Debian to informs us that the
installer works also for a serial install if you coax it properly.

Because of this there is a lot of well intended posts on the web about
changes you have to make to get the serial install to works.

Im I missing something here ? Could you point me in the right direction
please, thank's !

jrb.

Installing Debian using serial console error 'Undefined video mode'

[john doe]

Debians,

I'm trying to troubleshoot what I'm doing rong when trying to install
Debian through serial console.

If I start a Qemu VM like so:

qemu-system-x86_64 -cdrom debian-bullseye-DI-alpha2-amd64-netinst.iso
-nographic -vga none -m 1024

At the Debian install prompt pressing the escape key get me to the boot
prompt.

boot: install console=ttyS0,115200n8 DEBIAN_FRONTEND=text gfxpayload=text
Undefined video mode number: 314
Press  to see video modes available,  to continue, or wait
30 sec


If I use 'vga=none' the above is suppressed but Debian will not start
properly after installation by saying that 'vga=none' is deprecated and
that 'set gfxpayload=text' should be used instead.

What am I missing?


--
John Doe

Re: Using serial console as a poor mans IP kvm?

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Sep 09, 2016 at 09:03:33PM +0300, Jarle Aase wrote:
> Hi,
> 
> I was just about to order some usb2serial hardware when I read this.
[...]
> I'll try it when I get the first server assembled. Thanks a lot!

Hey, glad to help :-)

- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlfTBAQACgkQBcgs9XrR2kb2oQCfXciqNGw+duZSi0+j293y9X26
mFcAnRJFuhTP641mbXmJ9YS0l5VZnd6j
=3unC
-END PGP SIGNATURE-

Re: Using serial console as a poor mans IP kvm?

[Jarle Aase]

Hi,

I was just about to order some usb2serial hardware when I read this. 
Your suggestion will give fewer "moving parts" and is actually very 
simple to implement. I will loose the ability to do a cold boot, but it 
will probably not matter too much in my case, at least not for now.


I'll try it when I get the first server assembled. Thanks a lot!

Jarle

Den 09. sep. 2016 10:31, skrev to...@tuxteam.de:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Sep 08, 2016 at 10:26:59PM +0300, Jarle Aase wrote:

I want to set up a few servers at home. Unfortunately, as I live in
Bulgaria at the moment, the electric power is gone pretty often for
longer periods than my UPS'es can deal with. So my servers will have
to be started at least a few times every quarter.

[...]


That means that I need to reboot the servers relatively often, and
provide the luks passwords every time. Some times I am far away when
this happens [...]

An interesting alternative to the serial console thing is baking
in an SSH server into the initramfs. There are small SSH servers
built for that, like Dropbear.

Upside is that you don't need any additional hardware and it's
pretty well integrated into Debian. Downside is that you need
BIOS, the bootloader and initramfs working (with the serial you
at least get a chance to fix the bootloader remotely).

https://packages.debian.org/sid/dropbear-initramfs
https://wiki.debian.org/RescueInitramfs
https://projectgus.com/2013/05/encrypted-rootfs-over-ssh-with-debian-wheezy/

Might be worth a try.

Regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlfSZVMACgkQBcgs9XrR2kZGNgCfZhrMlouUceQSVJgzimE+b2YG
GokAn0PpEqnw2lgmFiGTu554OQtpt9Wa
=AKQd
-END PGP SIGNATURE-

Re: Using serial console as a poor mans IP kvm?

[Eike Lantzsch]

On Freitag, 9. September 2016 08:15:37 PYT Tixy wrote:
> On Fri, 2016-09-09 at 08:46 +0300, Lars Noodén wrote:
> > I've used USB-to-serial adapters with the Prolific chipset.  They've
> > worked fine for me, in various models.  (I haven't tried FTDI and am
> > suspicious of them.)
> 
> And my experience is the opposite. I have genuine (there's apparently a
> lot of fakes) FTDI devices in pretty much daily use for many years
> without problems. This is using ser2net on a local network for accessing
> serial consoles on ARM based development boards. ser2net will be
> insecure telnet or raw port forwarding but if it's not exposed to the
> internet and you can ssh tunnel into the local network then that's a lot
> better. I've done that method for carrying on working with my boards
> whilst across the other side of the world. Of course, a means of power
> cycling devices is also essential.

I second that. I had many weird problems with PL2303 but never any on any OS* 
with FTDI FT232 chips.

[*] Debian-Linux, OpenBSD, OSX and MS-Windows 
-- 
Eike Lantzsch ZP6CGE

Re: Using serial console as a poor mans IP kvm?

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Sep 08, 2016 at 10:26:59PM +0300, Jarle Aase wrote:
> I want to set up a few servers at home. Unfortunately, as I live in
> Bulgaria at the moment, the electric power is gone pretty often for
> longer periods than my UPS'es can deal with. So my servers will have
> to be started at least a few times every quarter.

[...]

> That means that I need to reboot the servers relatively often, and
> provide the luks passwords every time. Some times I am far away when
> this happens [...]

An interesting alternative to the serial console thing is baking
in an SSH server into the initramfs. There are small SSH servers
built for that, like Dropbear.

Upside is that you don't need any additional hardware and it's
pretty well integrated into Debian. Downside is that you need
BIOS, the bootloader and initramfs working (with the serial you
at least get a chance to fix the bootloader remotely).

https://packages.debian.org/sid/dropbear-initramfs
https://wiki.debian.org/RescueInitramfs
https://projectgus.com/2013/05/encrypted-rootfs-over-ssh-with-debian-wheezy/

Might be worth a try.

Regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlfSZVMACgkQBcgs9XrR2kZGNgCfZhrMlouUceQSVJgzimE+b2YG
GokAn0PpEqnw2lgmFiGTu554OQtpt9Wa
=AKQd
-END PGP SIGNATURE-

Re: Using serial console as a poor mans IP kvm?

[Tixy]

On Fri, 2016-09-09 at 08:46 +0300, Lars Noodén wrote:
> I've used USB-to-serial adapters with the Prolific chipset.  They've
> worked fine for me, in various models.  (I haven't tried FTDI and am
> suspicious of them.)

And my experience is the opposite. I have genuine (there's apparently a
lot of fakes) FTDI devices in pretty much daily use for many years
without problems. This is using ser2net on a local network for accessing
serial consoles on ARM based development boards. ser2net will be
insecure telnet or raw port forwarding but if it's not exposed to the
internet and you can ssh tunnel into the local network then that's a lot
better. I've done that method for carrying on working with my boards
whilst across the other side of the world. Of course, a means of power
cycling devices is also essential.

-- 
Tixy

Re: Using serial console as a poor mans IP kvm?

[Lars Noodén]

On 09/08/2016 10:26 PM, Jarle Aase wrote:
>...
> So I'm thinking about serial consoles. My gateway router will reboot
> after an outage, and it can act as a VPN endpoint. So I can access IP
> devices. With a rasberry pi and some relays, I can probably trigger a
> cold reboot whenever I need to. If I could log on to the grub console on
> the servers over a serial link, that's all I need, really.
> 
> Does anyone here have any experience with remote control with Debian
> boxes over serial? Will it work reliable?

Quite a while back (Etch) I had some Debian machines running via serial
console.  As far as I know everything should still work just as nicely
over serial console.  From what I recall, you'll have to set console
settings several places in the system to cover all contingencies for
booting and recovery.

I've used USB-to-serial adapters with the Prolific chipset.  They've
worked fine for me, in various models.  (I haven't tried FTDI and am
suspicious of them.)  There are also specialized PCI and PCIe serial
console servers which add 4 or 8 extra serial ports to a machine.  But
if you're going to run everything off of a single rpi then a
USB-to-serial adapter is the way to go.  There are ones that go USB to 4
or 8 serial ports, but they are hard to find affordably any more.

About the power relays, I did that before and had a lot of help to make
some custom ones, nothing being on the market back then.  I found
someone with skill to build a custom setup that worked over GPIO.
However, nowadays there are several devices that look interesting.  One
pre-made series that caught my eye a few weeks ago was this one:

https://unipi.technology/shop/

However, I have not evaluated any units so that is just to point to
what's on the market and not any endorsement.  You'll need to wire plugs
and such, too, and I can't see any fuses on those units.

Regards,
Lars

Re: Using serial console as a poor mans IP kvm?

[Don Armstrong]

On Thu, 08 Sep 2016, Jarle Aase wrote:
> Does anyone here have any experience with remote control with Debian boxes
> over serial? Will it work reliable?

It's fairly reliable; I actually prefer it to using KVM in almost all
cases. You just need to get it configured properly in grub, the bios,
and the kernel, and you should be fine.

That said, providing LUKS input over the wire is always going to be
problematic unless you have known secured links to the terminal. [But
maybe you'll know if the government has done this to you.]


-- 
Don Armstrong  https://www.donarmstrong.com

Whatever you do will be insignificant, but it is very important that
you do it.
 -- Mohandas Karamchand Gandhi

Re: Using serial console as a poor mans IP kvm?

[Neal P. Murphy]

On Thu, 8 Sep 2016 15:43:31 -0600
Glenn English  wrote:

> For remote access, the RPi sounds like a good idea to me. I've had one on the 
> 'Net for several years, doing things not requiring major CPU power. It's on 
> my UPS, and it's had no reliability problems.
> 
> A relatively small dedicated UPS would likely keep your border router and an 
> RPi going for quite a while.
> 
> An RPi is just a small Debian box, so you could reliably get to it over a 
> VPN. Then, with a little innovative routing, you could look around the net(s) 
> and see what's going on. 
> 
> With a relay board on the RPi's GPIO connector, you could turn things back 
> on, if necessary. No RS-232, new motherboards, or KVM anythings required.

Except for entering the encryption keys, and seeing when to enter them

Re: Using serial console as a poor mans IP kvm?

[Glenn English]

For remote access, the RPi sounds like a good idea to me. I've had one on the 
'Net for several years, doing things not requiring major CPU power. It's on my 
UPS, and it's had no reliability problems.

A relatively small dedicated UPS would likely keep your border router and an 
RPi going for quite a while.

An RPi is just a small Debian box, so you could reliably get to it over a VPN. 
Then, with a little innovative routing, you could look around the net(s) and 
see what's going on. 

With a relay board on the RPi's GPIO connector, you could turn things back on, 
if necessary. No RS-232, new motherboards, or KVM anythings required.

Assuming you can write a little Python...

No?

-- 
Glenn English

Re: Using serial console as a poor mans IP kvm?

[Neal P. Murphy]

On Thu, 8 Sep 2016 22:26:59 +0300
Jarle Aase <j...@jgaa.com> wrote:

> I want to set up a few servers at home. Unfortunately, as I live in 
> Bulgaria at the moment, the electric power is gone pretty often for 
> longer periods than my UPS'es can deal with. So my servers will have to 
> be started at least a few times every quarter.
> 
> Another challenge with living in Bulgaria is that there is no law or 
> order. The Police is just a branch of the Mafia. I need to protect the 
> data on the servers with full disk encryption in case they are stolen.
> 
> That means that I need to reboot the servers relatively often, and 
> provide the luks passwords every time. Some times I am far away when 
> this happens. I have been considering Supermicro motherboards with built 
> in support for remote management - or old KVM IP switches from Ebay. The 
> problem with Supermicro is that it's expensive and difficult to get the 
> RAM required for their recent Skylake boards. The problem with Ebay is 
> that few suppliers ships to Bulgaria, and getting anything trough the 
> custom's here takes a whole day. Then there is the question if the 
> device works at all...
> 
> So I'm thinking about serial consoles. My gateway router will reboot 
> after an outage, and it can act as a VPN endpoint. So I can access IP 
> devices. With a rasberry pi and some relays, I can probably trigger a 
> cold reboot whenever I need to. If I could log on to the grub console on 
> the servers over a serial link, that's all I need, really.
> 
> Does anyone here have any experience with remote control with Debian 
> boxes over serial? Will it work reliable?

Generally speaking

I haven't used a serial console on Debian in particular. I do it on a 
Linux-based system I maintain; serial console works very well, provided you 
remember the main differences: it's not a VESA console, it doesn't know about 
CTRL-ALT-DEL, and you may see no output until grub starts (unless the 
BIOS/firmware can do serial console). The system's terminal type may not match 
the emulator's type and the display may be somewhat garbled; the use of serial 
ports for interactive use has declined greatly over the years, as has 
conformance to serial terminal protocols. Also, a  starts SysRq.

I suspect grub should work with a serial console; I've never tried it with the 
new grub. I wrote a 6-line patch for grub legacy (which I use for my system) 
that allows one to use either VESA or serial console, or choose one with a 
keystroke. I've been using it for 3-4 years now without trouble.

To tell linux to use a serial console, connect a terminal (or emulator) to 
ttyS0 (COMa) on the server and set it to 115200-8-N-1, let grub start, then 
edit the boot entry and add the option "console=ttys0,115200" to the kernel 
command line, and boot. 

Your main problem will be operating the servers' reset switches should it be 
necessary. I think this is usually done by having the DCD, DSR, RI, or CTS line 
of the TIA-232 port close-then-open a relay that acts as the reset switch. (But 
your idea of using an rPI would work, too.)

Of course, the encryption key reader has to work on a serial port as well.

What would be interesting is if there were a 'VGA scanner' for the rPI so it 
could send you the screen changes, say, ten times a second. (And there are some 
USB devices that may work.) And if the rPI had a client USB port (so it could 
act like a keyboard) you would be able to see the 'monitor' and type on the 
'keyboard'.

Re: Using serial console as a poor mans IP kvm?

[Miles Fidelman]

On 9/8/16 3:26 PM, Jarle Aase wrote:

I want to set up a few servers at home. Unfortunately, as I live in 
Bulgaria at the moment, the electric power is gone pretty often for 
longer periods than my UPS'es can deal with. So my servers will have 
to be started at least a few times every quarter.


Another challenge with living in Bulgaria is that there is no law or 
order. The Police is just a branch of the Mafia. I need to protect the 
data on the servers with full disk encryption in case they are stolen.


That means that I need to reboot the servers relatively often, and 
provide the luks passwords every time. Some times I am far away when 
this happens. I have been considering Supermicro motherboards with 
built in support for remote management - or old KVM IP switches from 
Ebay. The problem with Supermicro is that it's expensive and difficult 
to get the RAM required for their recent Skylake boards. The problem 
with Ebay is that few suppliers ships to Bulgaria, and getting 
anything trough the custom's here takes a whole day. Then there is the 
question if the device works at all...


So I'm thinking about serial consoles. My gateway router will reboot 
after an outage, and it can act as a VPN endpoint. So I can access IP 
devices. With a rasberry pi and some relays, I can probably trigger a 
cold reboot whenever I need to. If I could log on to the grub console 
on the servers over a serial link, that's all I need, really.


Does anyone here have any experience with remote control with Debian 
boxes over serial? Will it work reliable?




It sort of works.

I've done this two ways:

1.  External serial-to-ethernet box.  The external box turns out to be 
somewhat flakey, and a security hole (unpatched embedded linux with some 
vulnerabilities, and it needs to be rekeyed annually, but that doesn't 
actually work very smoothly).


2. Supermicro IPMI board:  Sometimes works, sometimes simply doesn't 
respond - usually when one needs it most.


In both cases, unless you layer a VPN on top of them, they are really 
nasty security holes.  I've ended up resorting to the old "call the data 
center and have a human push the button" - but that doesn't sound like 
it applies to your situation.


Good luck finding a solution.

Miles Fidelman

--
In theory, there is no difference between theory and practice.
In practice, there is.   Yogi Berra

Re: Using serial console as a poor mans IP kvm?

[Dan Ritter]

On Thu, Sep 08, 2016 at 10:26:59PM +0300, Jarle Aase wrote:
> I want to set up a few servers at home. Unfortunately, as I live in Bulgaria
> at the moment, the electric power is gone pretty often for longer periods
> than my UPS'es can deal with. So my servers will have to be started at least
> a few times every quarter.
> 
> Another challenge with living in Bulgaria is that there is no law or order.
> The Police is just a branch of the Mafia. I need to protect the data on the
> servers with full disk encryption in case they are stolen.
> 
> That means that I need to reboot the servers relatively often, and provide
> the luks passwords every time. Some times I am far away when this happens. I
> have been considering Supermicro motherboards with built in support for
> remote management - or old KVM IP switches from Ebay. The problem with
> Supermicro is that it's expensive and difficult to get the RAM required for
> their recent Skylake boards. The problem with Ebay is that few suppliers
> ships to Bulgaria, and getting anything trough the custom's here takes a
> whole day. Then there is the question if the device works at all...
> 
> So I'm thinking about serial consoles. My gateway router will reboot after
> an outage, and it can act as a VPN endpoint. So I can access IP devices.
> With a rasberry pi and some relays, I can probably trigger a cold reboot
> whenever I need to. If I could log on to the grub console on the servers
> over a serial link, that's all I need, really.
> 
> Does anyone here have any experience with remote control with Debian boxes
> over serial? Will it work reliable?

We use serial consoles on Debian and Oracle Linux boxes all the
time, and have done so for more than a decade. They are more
dependable than anything else -- once you have set them up and
tested them through a full reboot cycle.

There are relatively expensive, but compact, devices that will
do both serial access and power switching. 8 of each is a common
configuration, as is 16. We like WTI boxes.

I am somewhat suspicious of USB-to-serial adapters in general,
but they are cheap and you can hook up lots at once through a
USB hub. You will probably want to test several brands in order
to find something reliable.

Incidentally, there are very few applications in which a Skylake
processor will be notably faster than the previous generation of 
Broadwells -- and Broadwells can use DDR3. You might save a lot 
of money and get built-in KVMs that way.

-dsr-

Using serial console as a poor mans IP kvm?

[Jarle Aase]

I want to set up a few servers at home. Unfortunately, as I live in 
Bulgaria at the moment, the electric power is gone pretty often for 
longer periods than my UPS'es can deal with. So my servers will have to 
be started at least a few times every quarter.


Another challenge with living in Bulgaria is that there is no law or 
order. The Police is just a branch of the Mafia. I need to protect the 
data on the servers with full disk encryption in case they are stolen.


That means that I need to reboot the servers relatively often, and 
provide the luks passwords every time. Some times I am far away when 
this happens. I have been considering Supermicro motherboards with built 
in support for remote management - or old KVM IP switches from Ebay. The 
problem with Supermicro is that it's expensive and difficult to get the 
RAM required for their recent Skylake boards. The problem with Ebay is 
that few suppliers ships to Bulgaria, and getting anything trough the 
custom's here takes a whole day. Then there is the question if the 
device works at all...


So I'm thinking about serial consoles. My gateway router will reboot 
after an outage, and it can act as a VPN endpoint. So I can access IP 
devices. With a rasberry pi and some relays, I can probably trigger a 
cold reboot whenever I need to. If I could log on to the grub console on 
the servers over a serial link, that's all I need, really.


Does anyone here have any experience with remote control with Debian 
boxes over serial? Will it work reliable?


Thanks in advance.

Jarle

Re: Getting a serial console to work on Jessie

[Sven Hartge]

Stephen Powell  wrote:
> On Mon, 07 Sep 2015 11:47:56 -0400 (EDT), Sven Hartge wrote:
 
>> Looks fine, from a cursory glance.
>> 
>> Maybe you can add a section about using
>> 
>>"systemctl cat serial-getty@ttyS0.service"
>> 
>> to verfiy that the override.conf has been
>> read successfully after "systemctl daemon-reload".

> Done.  Refresh the page and see if that's what you had in mind.

Yes, this is what I had in mind.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Getting a serial console to work on Jessie

[Stephen Powell]

On Mon, 07 Sep 2015 18:08:05 -0400 (EDT), Bob Bernstein wrote:
> 
> What a great contribution!
> 
> My null-modem cable ought to still be around here somewhere!
> 
> :-)

I try to focus on the latest technology.  

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

Re: Getting a serial console to work on Jessie

[David Parker]

Hello,

Thanks for all the clarification.  I now find myself in need of doing this
again on another server running Jessie, and I just want to make sure I'm
clear on what the best procedure is.  As I understand it, I should
copy /lib/systemd/system/serial-getty@.service to
/etc/systemd/system/serial-getty@ttyS0.service, then
edit serial-getty@ttyS0.service to include the following:

[Service]
ExecStart=
ExecStart=-/sbin/agetty -8 --noclear %I 9600 vt100
...

Is that correct?

Thanks!
Dave

On Sun, Sep 6, 2015 at 9:52 PM, Stephen Powell  wrote:

> On Sun, 06 Sep 2015 16:06:35 -0400 (EDT), Michael Biebl wrote:
> > Am 06.09.2015 um 21:04 schrieb Stephen Powell:
> >> ...
> >>[Service]
> >>ExecStart=-/sbin/agetty -8 --noclear %I 38400 ibm3151
> >>
> >> But when I restart the service, I get the following error:
> >>
> >> systemd[1]: serial-getty@ttyS0.service: Service has more than one
> ExecStart= setting, which is only allowed for Type=oneshot services.
> Refusing.
> >>
> >> I want to override "ExecStart", not add a new one.  What am I doing
> wrong?
> >
> > By default, systemd will simply merge all drop-ins.
> > In your case, ExecStart is a setting which can not be specified more
> > then once. So you need to "clear" it first. The following should do the
> > trick:
> >
> > [Service]
> > ExecStart=
> > ExecStart=-/sbin/agetty -8 --noclear %I 38400 ibm3151
> >
> >
> > The "ExecStart=" resets the existing setting.
> >
> > ...
>
> That works.  This is definitely a better solution than copying
> serial-getty@.service from /lib/systemd/system to /etc/systemd/system
> and then editing the copy in /etc/systemd/system to change the ExecStart
> value.  It is better for two reasons:
>
> (1) When systemd is serviced, I don't need to recopy and reedit the file
> in order to keep my changes synced up with changes to the file made by
> service to systemd.
>
> (2) It allows two different serial ports to have different ExecStart values
> for two different terminal types, for example.  Using my original method,
> both serial ports would be locked into the same terminal type.
>
> I shall change my documentation accordingly.  Thanks, Michael and Sven
> for your suggestions and help.
>
> Regards,
>
> --
>   .''`. Stephen Powell
>  : :'  :
>  `. `'`
>`-
>
>


-- 
Dave Parker
Systems Administrator
Utica College
Integrated Information Technology Services
(315) 792-3229
Registered Linux User #408177

Re: Getting a serial console to work on Jessie

[Sven Hartge]

Stephen Powell  wrote:

> Sven and Michael, please review this also and correct me if I made a
> mistake.  I do not want to publish bad advice.

Looks fine, from a cursory glance.

Maybe you can add a section about using "systemctl cat
serial-getty@ttyS0.service" to verfiy that the override.conf has been
read successfully after "systemctl daemon-reload".

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Getting a serial console to work on Jessie

[Stephen Powell]

On Mon, 07 Sep 2015 09:56:12 -0400 (EDT), David Parker wrote:
> 
> Thanks for all the clarification.  I now find myself in need of doing this
> again on another server running Jessie, and I just want to make sure I'm
> clear on what the best procedure is.
> ...

I just finished updating my web page to reflect the new information.
Once again, go to

   http://users.wowway.com/~zlinuxman/serial.htm

Make sure that you press F5 to refresh the page (or whatever your browser's
refresh key is), since an old version of the page may be in your browser's
cache if you've looked at it recently.  Then read the new instructions for
enabling a serial terminal under systemd.  If you then have any questions, 
please post a follow-up.

Sven and Michael, please review this also and correct me if I made a mistake.
I do not want to publish bad advice.

Regards,

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

Re: Getting a serial console to work on Jessie

[Bob Bernstein]

On Mon, 7 Sep 2015, Stephen Powell wrote:

I just finished updating my web page to reflect the new 
information. Once again, go to



  http://users.wowway.com/~zlinuxman/serial.htm


What a great contribution!

My null-modem cable ought to still be around here somewhere!

:-)


--
Bob Bernstein

Re: Getting a serial console to work on Jessie

[Stephen Powell]

On Mon, 07 Sep 2015 11:47:56 -0400 (EDT), Sven Hartge wrote:
> 
> Looks fine, from a cursory glance.
> 
> Maybe you can add a section about using
> 
>"systemctl cat serial-getty@ttyS0.service"
> 
> to verfiy that the override.conf has been
> read successfully after "systemctl daemon-reload".

Done.  Refresh the page and see if that's what you had in mind.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

Re: Getting a serial console to work on Jessie

[Michael Biebl]

Am 06.09.2015 um 21:04 schrieb Stephen Powell:

>[Service]
>ExecStart=-/sbin/agetty -8 --noclear %I 38400 ibm3151
> 
> But when I restart the service, I get the following error:
> 
> systemd[1]: serial-getty@ttyS0.service: Service has more than one ExecStart= 
> setting, which is only allowed for Type=oneshot services. Refusing.
> 
> I want to override "ExecStart", not add a new one.  What am I doing wrong?

By default, systemd will simply merge all drop-ins.
In your case, ExecStart is a setting which can not be specified more
then once. So you need to "clear" it first. The following should do the
trick:

[Service]
ExecStart=
ExecStart=-/sbin/agetty -8 --noclear %I 38400 ibm3151


The "ExecStart=" resets the existing setting.

See also man 5 systemd.unit , "Example 2. Overriding vendor settings":

>Note that for drop-in files, if one wants to remove entries from a 
> setting that is
>parsed as a list (and is not a dependency), such as 
> ConditionPathExists= (or e.g.
>ExecStart= in service units), one needs to first clear the list before 
> re-adding all
>entries except the one that is to be removed. See below for an example.



Cheers,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Re: Getting a serial console to work on Jessie

[Sven Hartge]

Stephen Powell  wrote:

> Well, Sven, that's a nice idea, but I can't get it to work for me in this
> situation.  I issued

>systemctl edit serial-getty@ttyS0.service

> and placed the following two lines into the file:

>[Service]
>ExecStart=-/sbin/agetty -8 --noclear %I 38400 ibm3151

> But when I restart the service, I get the following error:

> systemd[1]: serial-getty@ttyS0.service: Service has more than one ExecStart= 
> setting, which is only allowed for Type=oneshot services. Refusing.

> I want to override "ExecStart", not add a new one.  What am I doing wrong?

You have to first clear the old ExecStart and then set a new one:
https://wiki.archlinux.org/index.php/Systemd#Drop-in_snippets

,
| As another example, in order to replace the ExecStart directive for a unit
| that is not of type oneshot, create the following file:
| ,
| | /etc/systemd/system/unit.d/customexec.conf
| | [Service]
| | ExecStart=
| | ExecStart=new command
| `
`

Yes, this is a bit counterintuitive.

So, in your case, the config file should look like this:

,
| [Service]
| ExecStart=
| ExecStart=-/sbin/agetty -8 --noclear %I 38400 ibm3151
`

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Getting a serial console to work on Jessie

[Stephen Powell]

On Sun, 06 Sep 2015 16:06:35 -0400 (EDT), Michael Biebl wrote:
> Am 06.09.2015 um 21:04 schrieb Stephen Powell:
>> ... 
>>[Service]
>>ExecStart=-/sbin/agetty -8 --noclear %I 38400 ibm3151
>> 
>> But when I restart the service, I get the following error:
>> 
>> systemd[1]: serial-getty@ttyS0.service: Service has more than one ExecStart= 
>> setting, which is only allowed for Type=oneshot services. Refusing.
>> 
>> I want to override "ExecStart", not add a new one.  What am I doing wrong?
> 
> By default, systemd will simply merge all drop-ins.
> In your case, ExecStart is a setting which can not be specified more
> then once. So you need to "clear" it first. The following should do the
> trick:
> 
> [Service]
> ExecStart=
> ExecStart=-/sbin/agetty -8 --noclear %I 38400 ibm3151
> 
> 
> The "ExecStart=" resets the existing setting.
> 
> ...

That works.  This is definitely a better solution than copying
serial-getty@.service from /lib/systemd/system to /etc/systemd/system
and then editing the copy in /etc/systemd/system to change the ExecStart
value.  It is better for two reasons:

(1) When systemd is serviced, I don't need to recopy and reedit the file
in order to keep my changes synced up with changes to the file made by
service to systemd.

(2) It allows two different serial ports to have different ExecStart values
for two different terminal types, for example.  Using my original method,
both serial ports would be locked into the same terminal type.

I shall change my documentation accordingly.  Thanks, Michael and Sven
for your suggestions and help.

Regards,

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

Re: Getting a serial console to work on Jessie

[Christian Seiler]

Hello Michael,

On 09/06/2015 10:06 PM, Michael Biebl wrote:
> See also man 5 systemd.unit , "Example 2. Overriding vendor settings":
> 
>>Note that for drop-in files, if one wants to remove entries from a 
>> setting that is
>>parsed as a list (and is not a dependency), such as 
>> ConditionPathExists= (or e.g.
>>ExecStart= in service units), one needs to first clear the list 
>> before re-adding all
>>entries except the one that is to be removed. See below for an 
>> example.

Note that that passage in the man page is only present in versions
of systemd beginning with either 216 or 217, while Jessie only has
systemd 215, and thus the man pages in Jessie don't contain that
text yet.

Christian



signature.asc
Description: OpenPGP digital signature

Re: Getting a serial console to work on Jessie

[Stephen Powell]

On Wed, 02 Sep 2015 17:29:40 -0400 (EDT), Sven Hartge wrote:
> 
> systemd provides a way to override or ammend parts of units. You do this
> by creating a directory structure like this:
> 
>   /etc/systemd/system/foo.service.d/
> 
> This will contain all additional config files for the unit
> "foo.service".
> 
> For example: I don't want systemd to clear the screen on tty1 when it
> starts a new getty. The unit responsible for this TTY is named
> "getty@tty1.service". I created
> 
>   /etc/systemd/system/getty@tty1.service.d
> 
> and put a file named "noclear.conf" in it with this content:
> 
> ,
> | [Service]
> | TTYVTDisallocate=no
> `
> 
> This will add (or change) the TTYVTDisallocate option to the unit.
> The original path to the unit is "/lib/systemd/system/getty@.service"
> and if this file is changed by a package update, its new content will be
> used.
> 
> If I had copied the _whole_ file to /etc/systemd/system then the new
> version of the unit in "/lib/systemd/system" would never get used, just
> my own version. This may be fine but may also cause major problems in
> the future.
> 
> This is what I meant by "future changes are preserved" as you don't just
> clobber them with your own full copy of the (then) old unit file.
> 
> You can check which files are used for a unit with systemctl:
> 
>   systemctl cat getty@tty1.service
> 
> and you will get an output like this (a bit shortened by me for this
> mail):
> 
> ,
> | # /lib/systemd/system/getty@.service
> |
> | [Unit]
> | Description=Getty on %I
> | Documentation=man:agetty(8) man:systemd-getty-generator(8)
> | Documentation=http://0pointer.de/blog/projects/serial-console.html
> | After=systemd-user-sessions.service plymouth-quit-wait.service
> | <<8<--->>
> | [Service]
> | # the VT is cleared by TTYVTDisallocate
> | TTYVTDisallocate=yes
> | KillMode=process
> | IgnoreSIGPIPE=no
> | SendSIGHUP=yes
> |
> | # Unset locale for the console getty since the console has problems
> | # displaying some internationalized messages.
> | Environment=LANG= LANGUAGE= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE=
> | LC_MONETARY= LC_MESSAGES= LC_
> |
> | [Install]
> | WantedBy=getty.target
> | DefaultInstance=tty1
> |
> | # /etc/systemd/system/getty@tty1.service.d/noclear.conf
> | [Service]
> | TTYVTDisallocate=no
> `
> 
> Note how my own addition shows up at the bottom.
> 
> Also note how a later "TTYVTDisallocate=no" overrides the earlier
> "TTYVTDisallocate=yes".
> 
> You can also use "systemd-delta" to check which units have overrides or
> extentions. And with newer systemd (Stretch and newer) you can even use
> "systemctl edit unitname" and it will create the needed directory
> structure in the correct place for you.
> 
> But you are also correct that this "override feature" is a bit different
> than the normal proceedings during upgrades and dealing with
> .dpkg-{old,new,dist}.
> 
> But it is the way systemd is designed and you can either work with it or
> fight it every centimeter of the way.
> 

Well, Sven, that's a nice idea, but I can't get it to work for me in this
situation.  I issued

   systemctl edit serial-getty@ttyS0.service

and placed the following two lines into the file:

   [Service]
   ExecStart=-/sbin/agetty -8 --noclear %I 38400 ibm3151

But when I restart the service, I get the following error:

systemd[1]: serial-getty@ttyS0.service: Service has more than one ExecStart= 
setting, which is only allowed for Type=oneshot services. Refusing.

I want to override "ExecStart", not add a new one.  What am I doing wrong?

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

Re: Getting a serial console to work on Jessie

[Stephen Powell]

On Thu, 03 Sep 2015 20:06:43 -0400 (EDT), Michael Biebl wrote:
> 
> Am 03.09.2015 um 03:14 schrieb Stephen Powell:
>> Do you know a similar technique for overriding individual udev rules in
>> a system-provided rules file?
> 
> A similar mechanism exists for udev rules file.
> See man 7 udev -> "RULES FILES"

I do know about user-written rules files, and I have used them in
the past, but for some reason it never occurred to me to use a
user-written rule to change an already-applied system-written rule.
Duh!  Why didn't I think of that?  How embarrassing!  Thanks.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

Re: Getting a serial console to work on Jessie

[Sven Hartge]

Stephen Powell  wrote:

> Do you know a similar technique for overriding individual udev rules in
> a system-provided rules file?

Ah, that part is a white spot on my (mind)map.

Maybe Michael Biebl can provide more input, as one of the DDs
maintaining systemd and udev he should be able to provide more input.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Getting a serial console to work on Jessie

[Michael Biebl]

Am 03.09.2015 um 03:14 schrieb Stephen Powell:
> Do you know a similar technique for overriding individual udev rules in
> a system-provided rules file?

A similar mechanism exists for udev rules file.
See man 7 udev -> "RULES FILES"


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Re: Getting a serial console to work on Jessie

[Stephen Powell]

On Wed, 02 Sep 2015 17:29:40 -0400 (EDT), Sven Hartge wrote:
> ...
> 
> systemd provides a way to override or ammend parts of units.
> You do this by creating a directory structure like this:
> 
>   /etc/systemd/system/foo.service.d/
> 
> This will contain all additional config files for the unit
> "foo.service".
> 
> For example: I don't want systemd to clear the screen on tty1 when it
> starts a new getty. The unit responsible for this TTY is named
> "getty@tty1.service". I created
> 
>   /etc/systemd/system/getty@tty1.service.d
> 
> and put a file named "noclear.conf" in it with this content:
> 
> ,
> | [Service]
> | TTYVTDisallocate=no
> `
> 
> This will add (or change) the TTYVTDisallocate option to the unit.
> The original path to the unit is "/lib/systemd/system/getty@.service"
> and if this file is changed by a package update, its new content will be
> used.
> 
> If I had copied the _whole_ file to /etc/systemd/system then the new
> version of the unit in "/lib/systemd/system" would never get used, just
> my own version. This may be fine but may also cause major problems in
> the future.
> 
> This is what I meant by "future changes are preserved" as you don't just
> clobber them with your own full copy of the (then) old unit file.
> 
> You can check which files are used for a unit with systemctl:
> 
>   systemctl cat getty@tty1.service
> 
> and you will get an output like this (a bit shortened by me for this
> mail):
> 
> ,
> | # /lib/systemd/system/getty@.service
> |
> | [Unit]
> | Description=Getty on %I
> | Documentation=man:agetty(8) man:systemd-getty-generator(8)
> | Documentation=http://0pointer.de/blog/projects/serial-console.html
> | After=systemd-user-sessions.service plymouth-quit-wait.service
> | <<8<--->>
> | [Service]
> | # the VT is cleared by TTYVTDisallocate
> | TTYVTDisallocate=yes
> | KillMode=process
> | IgnoreSIGPIPE=no
> | SendSIGHUP=yes
> |
> | # Unset locale for the console getty since the console has problems
> | # displaying some internationalized messages.
> | Environment=LANG= LANGUAGE= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE=
> | LC_MONETARY= LC_MESSAGES= LC_
> |
> | [Install]
> | WantedBy=getty.target
> | DefaultInstance=tty1
> |
> | # /etc/systemd/system/getty@tty1.service.d/noclear.conf
> | [Service]
> | TTYVTDisallocate=no
> `
> 
> Note how my own addition shows up at the bottom.
> 
> Also note how a later "TTYVTDisallocate=no" overrides the earlier
> "TTYVTDisallocate=yes".
> 
> You can also use "systemd-delta" to check which units have overrides or
> extentions. And with newer systemd (Stretch and newer) you can even use
> "systemctl edit unitname" and it will create the needed directory
> structure in the correct place for you.

Thanks for the tip, Sven.  I'll try to incorporate your suggestion in the
next revision of my serial console document.  With luck, I may get to it
this weekend.

Do you know a similar technique for overriding individual udev rules in
a system-provided rules file?

-- 
  .''`. Stephen Powell<zlinux...@wowway.com>
 : :'  :
 `. `'`
   `-

Re: Getting a serial console to work on Jessie

[Sven Hartge]

David Parker  wrote:

> Thanks.  I actually found that site in a Google search, and it's where
> I found the tip on copying the
> /lib/systemd/system/serial-getty@.service template file to customize
> the baud rate, etc.  Specifically, I found the info I needed at:

> http://users.wowway.com/~zlinuxman/serial.htm#Systemd

Well, the advise given on that website is wrong, or at least suboptimal,
because it totally overrides the system configuration instead of only
ammending it, which preserves future changes to the system file.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Getting a serial console to work on Jessie

[Eike Lantzsch]

On Wednesday 02 September 2015 23:29:40 Sven Hartge wrote:
> Eike Lantzsch  wrote:
> > On Wednesday 02 September 2015 20:58:29 Sven Hartge wrote:
> >> David Parker  wrote:
> >>> Thanks.  I actually found that site in a Google search, and it's where
> >>> I found the tip on copying the
> >>> /lib/systemd/system/serial-getty@.service template file to customize
> >>> the baud rate, etc.  Specifically, I found the info I needed at:
> >>> 
> >>> http://users.wowway.com/~zlinuxman/serial.htm#Systemd
> >> 
> >> Well, the advise given on that website is wrong, or at least suboptimal,
> >> because it totally overrides the system configuration instead of only
> >> ammending it, which preserves future changes to the system file.
> > 
> > May I kindly ask you to elaborate on that? Please, because I'm
> > interested too.  Where is better information to be had or can you at
> > least point out where exactly one needs to start to iron out the
> > failings of the mentioned document?
> > 
> > I'm not exactly understanding what you mean by "preserves future
> > changes to the system file". I always had the impression that my
> > changes to config files can either be overwritten by updates (bad),
> > merged into the newer config files (difficult without administrator
> > intervention) or left alone and new config files installed as
> > "release" files, or the new files installed and the old ones backed-up
> > as *.pkg-old.
> > 
> > Preserves seem always to be from the past yield, can the future be
> > preserved?
> > 
> > Also, what do you mean exactly by "system file" in the case of systemd
> > - those in /lib/systemd/system/?
> 
> Please excuse this misunderstanding, my native language got the better
> of me in that case. "system file" means "the one from the package".
> 
> Now, the explanation:
> 
> systemd provides a way to override or ammend parts of units. You do this
> by creating a directory structure like this:
> 
>   /etc/systemd/system/foo.service.d/
> 
> This will contain all additional config files for the unit
> "foo.service".
> 
> For example: I don't want systemd to clear the screen on tty1 when it
> starts a new getty. The unit responsible for this TTY is named
> "getty@tty1.service". I created
> 
>   /etc/systemd/system/getty@tty1.service.d
> 
> and put a file named "noclear.conf" in it with this content:
> 
> ,
> 
> | [Service]
> | TTYVTDisallocate=no
> 
> `
> 
> This will add (or change) the TTYVTDisallocate option to the unit.
> The original path to the unit is "/lib/systemd/system/getty@.service"
> and if this file is changed by a package update, its new content will be
> used.
> 
> If I had copied the _whole_ file to /etc/systemd/system then the new
> version of the unit in "/lib/systemd/system" would never get used, just
> my own version. This may be fine but may also cause major problems in
> the future.
> 
> This is what I meant by "future changes are preserved" as you don't just
> clobber them with your own full copy of the (then) old unit file.
> 
> You can check which files are used for a unit with systemctl:
> 
>   systemctl cat getty@tty1.service
> 
> and you will get an output like this (a bit shortened by me for this
> mail):
> 
> ,
> 
> | # /lib/systemd/system/getty@.service
> | 
> | [Unit]
> | Description=Getty on %I
> | Documentation=man:agetty(8) man:systemd-getty-generator(8)
> | Documentation=http://0pointer.de/blog/projects/serial-console.html
> | After=systemd-user-sessions.service plymouth-quit-wait.service
> | <<8<--->>
> | [Service]
> | # the VT is cleared by TTYVTDisallocate
> | TTYVTDisallocate=yes
> | KillMode=process
> | IgnoreSIGPIPE=no
> | SendSIGHUP=yes
> | 
> | # Unset locale for the console getty since the console has problems
> | # displaying some internationalized messages.
> | Environment=LANG= LANGUAGE= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE=
> | LC_MONETARY= LC_MESSAGES= LC_
> | 
> | [Install]
> | WantedBy=getty.target
> | DefaultInstance=tty1
> | 
> | # /etc/systemd/system/getty@tty1.service.d/noclear.conf
> | [Service]
> | TTYVTDisallocate=no
> 
> `
> 
> Note how my own addition shows up at the bottom.
> 
> Also note how a later "TTYVTDisallocate=no" overrides the earlier
> "TTYVTDisallocate=yes".
> 
> You can also use "systemd-delta" to check which units have overrides or
> extentions. And with newer systemd (Stretch and newer) you can even use
> "systemctl edit unitname" and it will create the needed directory
> structure in the correct place for you.
> 
> But you are also correct that this "override feature" is a bit different
> than the normal proceedings during upgrades and dealing with
> .dpkg-{old,new,dist}.
> 
> But it is the way systemd is designed and you can either work with it or
> fight it every centimeter of the way.
I sure won't fight anything I do not thoroughly understand. That's always a 
means to lose.
> 
> I hope this explains my thoughts.
Very well.
> 
> Grüße,
> Sven.

Thank you Sven!

Re: Getting a serial console to work on Jessie

[Eike Lantzsch]

On Wednesday 02 September 2015 20:58:29 Sven Hartge wrote:
> David Parker  wrote:
> > Thanks.  I actually found that site in a Google search, and it's where
> > I found the tip on copying the
> > /lib/systemd/system/serial-getty@.service template file to customize
> > the baud rate, etc.  Specifically, I found the info I needed at:
> > 
> > http://users.wowway.com/~zlinuxman/serial.htm#Systemd
> 
> Well, the advise given on that website is wrong, or at least suboptimal,
> because it totally overrides the system configuration instead of only
> ammending it, which preserves future changes to the system file.
> 
> Grüße,
> Sven.

Sven,

May I kindly ask you to elaborate on that? Please, because I'm interested too. 
Where is better information to be had or can you at least point out where 
exactly one needs to start to iron out the failings of the mentioned document?

I'm not exactly understanding what you mean by "preserves future changes to 
the system file". I always had the impression that my changes to config files 
can 
either be overwritten by updates (bad), merged into the newer config files 
(difficult without administrator intervention) or left alone and new config 
files 
installed as "release" files, or the new files installed and the old ones 
backed-up as *.pkg-old.

Preserves seem always to be from the past yield, can the future be preserved?

Also, what do you mean exactly by "system file" in the case of systemd - those 
in /lib/systemd/system/?

Cheers and thank you
Eike

Re: Getting a serial console to work on Jessie

[Sven Hartge]

Eike Lantzsch  wrote:
> On Wednesday 02 September 2015 20:58:29 Sven Hartge wrote:
>> David Parker  wrote:

>>> Thanks.  I actually found that site in a Google search, and it's where
>>> I found the tip on copying the
>>> /lib/systemd/system/serial-getty@.service template file to customize
>>> the baud rate, etc.  Specifically, I found the info I needed at:
>>> 
>>> http://users.wowway.com/~zlinuxman/serial.htm#Systemd

>> Well, the advise given on that website is wrong, or at least suboptimal,
>> because it totally overrides the system configuration instead of only
>> ammending it, which preserves future changes to the system file.

> May I kindly ask you to elaborate on that? Please, because I'm
> interested too.  Where is better information to be had or can you at
> least point out where exactly one needs to start to iron out the
> failings of the mentioned document?

> I'm not exactly understanding what you mean by "preserves future
> changes to the system file". I always had the impression that my
> changes to config files can either be overwritten by updates (bad),
> merged into the newer config files (difficult without administrator
> intervention) or left alone and new config files installed as
> "release" files, or the new files installed and the old ones backed-up
> as *.pkg-old.

> Preserves seem always to be from the past yield, can the future be
> preserved?

> Also, what do you mean exactly by "system file" in the case of systemd
> - those in /lib/systemd/system/?

Please excuse this misunderstanding, my native language got the better
of me in that case. "system file" means "the one from the package". 

Now, the explanation:

systemd provides a way to override or ammend parts of units. You do this
by creating a directory structure like this:

  /etc/systemd/system/foo.service.d/

This will contain all additional config files for the unit
"foo.service".

For example: I don't want systemd to clear the screen on tty1 when it
starts a new getty. The unit responsible for this TTY is named
"getty@tty1.service". I created

  /etc/systemd/system/getty@tty1.service.d

and put a file named "noclear.conf" in it with this content:

,
| [Service]
| TTYVTDisallocate=no
`

This will add (or change) the TTYVTDisallocate option to the unit.
The original path to the unit is "/lib/systemd/system/getty@.service"
and if this file is changed by a package update, its new content will be
used.

If I had copied the _whole_ file to /etc/systemd/system then the new
version of the unit in "/lib/systemd/system" would never get used, just
my own version. This may be fine but may also cause major problems in
the future.

This is what I meant by "future changes are preserved" as you don't just
clobber them with your own full copy of the (then) old unit file.

You can check which files are used for a unit with systemctl:

  systemctl cat getty@tty1.service

and you will get an output like this (a bit shortened by me for this
mail):

,
| # /lib/systemd/system/getty@.service
|
| [Unit]
| Description=Getty on %I
| Documentation=man:agetty(8) man:systemd-getty-generator(8)
| Documentation=http://0pointer.de/blog/projects/serial-console.html
| After=systemd-user-sessions.service plymouth-quit-wait.service
| <<8<--->>
| [Service]
| # the VT is cleared by TTYVTDisallocate
| TTYVTDisallocate=yes
| KillMode=process
| IgnoreSIGPIPE=no
| SendSIGHUP=yes
|
| # Unset locale for the console getty since the console has problems
| # displaying some internationalized messages.
| Environment=LANG= LANGUAGE= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE=
| LC_MONETARY= LC_MESSAGES= LC_
|
| [Install]
| WantedBy=getty.target
| DefaultInstance=tty1
|
| # /etc/systemd/system/getty@tty1.service.d/noclear.conf
| [Service]
| TTYVTDisallocate=no
`

Note how my own addition shows up at the bottom.

Also note how a later "TTYVTDisallocate=no" overrides the earlier
"TTYVTDisallocate=yes".

You can also use "systemd-delta" to check which units have overrides or
extentions. And with newer systemd (Stretch and newer) you can even use
"systemctl edit unitname" and it will create the needed directory
structure in the correct place for you.

But you are also correct that this "override feature" is a bit different
than the normal proceedings during upgrades and dealing with
.dpkg-{old,new,dist}.

But it is the way systemd is designed and you can either work with it or
fight it every centimeter of the way.

I hope this explains my thoughts.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Getting a serial console to work on Jessie

[David Parker]

Thanks.  I actually found that site in a Google search, and it's where I
found the tip on copying the /lib/systemd/system/serial-getty@.service
template file to customize the baud rate, etc.  Specifically, I found the
info I needed at:

http://users.wowway.com/~zlinuxman/serial.htm#Systemd

Thanks!

On Tue, Sep 1, 2015 at 6:43 PM, Stephen Powell  wrote:

> On Tue, 01 Sep 2015 12:13:56 -0400 (EDT), David Parker wrote:
> >
> > I have a bunch of Debian Wheezy servers set up with the console available
> > via the serial port.  Generally, I just add this line to /etc/inittab:
> > ...
> > That's all fine and good, but when I try to do this on my desktop PC
> > running Jessie, it doesn't work.
> > ...
>
> I realize that you already have a resolution to your problem, but if you're
> using serial consoles on Debian Linux, you might find some useful
> information here:
>
>http://users.wowway.com/~zlinuxman/serial.htm
>
> --
>   .''`. Stephen Powell
>  : :'  :
>  `. `'`
>`-
>
>


-- 
Dave Parker
Systems Administrator
Utica College
Integrated Information Technology Services
(315) 792-3229
Registered Linux User #408177

Re: Getting a serial console to work on Jessie

[Sven Hartge]

Michael Biebl  wrote:

> As for overriding the system provided service files, I usually recommend
> to use drop-ins, i.e. creating a
> /etc/systemd/system/foo.service.d/my_custom_config.conf
> This way you only need to override what you are actually interested in.

Users of Testing/Stretch or Unstable/Sid can use systemctl directly:

# systemctl edit foo.service

and this will create the override directory in the right place and open
a new file in your preferred editor. Very handy.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Getting a serial console to work on Jessie

[Michael Biebl]

Am 01.09.2015 um 18:13 schrieb David Parker:
> And still not in the same way that they appear on Wheezy ("/sbin/getty
> 38400 tty1", etc.).  If I add the line for the serial console to
> /etc/inittab and reload the init deamon, or even reboot the PC, it simply
> does nothing.  No getty process shows up on ttyS0, and no serial console is
> available.
> 
> I know the serial port itself works, because I can connect to it from my
> laptop, then do "screen /dev/ttyS0 9600" on the PC and see characters in
> the screen session as I type them on the laptop.  So the serial port works,
> and I/O seems to work, but I can't seem to start a persistent getty process
> on that port and access the console through it.

Reading your description, I assume you have systemd-sysv installed and
systemd is your active PID 1. systemd no longer reads /etc/inittab, so
any configuration changes there don't have any effect.

getty's are started on demand by systemd-logind [1] and then show up as
instances of getty@.service, e.g. getty@tty1.service.
If you wanted to see your currently running instances you could use
something like "systemctl list-units | grep getty@"

For getty's on a serial console, there is a serial-getty@.service unit,
which is also started on demand.

If for some reason you want to enable those units statically, i.e.
always start them during boot, then this is no problem either.
Run
systemctl enable getty@tty2.service
systemctl enable getty@tty3.service
..
systemctl enable serial-getty@ttyS0.service
etc.

Regards,
Michael




[1] see man logind.conf -> NAutoVTs



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Re: Getting a serial console to work on Jessie

[Michael Biebl]

Am 01.09.2015 um 19:31 schrieb David Parker:
> Thanks, Michael!  That was indeed the problem.  I
> copied /lib/systemd/system/serial-getty@.service to /etc/systemd/system,
> edited it to use the correct baud rate and terminal type, and then ran
> "systsystemctl start serial-getty@ttyS0.service" and it worked like a charm.

Glad we could solve your problem this easily.

As for overriding the system provided service files, I usually recommend
to use drop-ins, i.e. creating a
/etc/systemd/system/foo.service.d/my_custom_config.conf
This way you only need to override what you are actually interested in.

You can use drop-ins for template files itself or for instances itself:

/etc/systemd/system/serial-getty@.service.d/my_stuff.conf
-> will apply to all instances of serial-getty@

/etc/systemd/system/serial-getty@ttyS0.service.d/my_stuff.conf
-> only applies to serial-getty@ttyS0.service.d

> Guess I need to get with the times and learn systemd!

Welcome!

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Re: Getting a serial console to work on Jessie

[Stephen Powell]

On Tue, 01 Sep 2015 12:13:56 -0400 (EDT), David Parker wrote:
> 
> I have a bunch of Debian Wheezy servers set up with the console available
> via the serial port.  Generally, I just add this line to /etc/inittab:
> ...
> That's all fine and good, but when I try to do this on my desktop PC
> running Jessie, it doesn't work.
> ...

I realize that you already have a resolution to your problem, but if you're
using serial consoles on Debian Linux, you might find some useful information 
here:

   http://users.wowway.com/~zlinuxman/serial.htm

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

Getting a serial console to work on Jessie

[David Parker]

Hello,

I have a bunch of Debian Wheezy servers set up with the console available
via the serial port.  Generally, I just add this line to /etc/inittab:

co:2345:respawn:/sbin/getty -L ttyS0 9600 vt102

And then run "kill -HUP 1" and the serial console works (I could also use
"telinit q" or "init q" instead of kill -HUP").  I just did this on a
Wheezy server to make sure, and checked the getty processes prior to making
the change:

# ps -ef | grep getty
root  2660 1  0 Jul24 tty1 00:00:00 /sbin/getty 38400 tty1
root  2661 1  0 Jul24 tty2 00:00:00 /sbin/getty 38400 tty2
root  2662 1  0 Jul24 tty3 00:00:00 /sbin/getty 38400 tty3
root  2663 1  0 Jul24 tty4 00:00:00 /sbin/getty 38400 tty4
root  2664 1  0 Jul24 tty5 00:00:00 /sbin/getty 38400 tty5
root  2665 1  0 Jul24 tty6 00:00:00 /sbin/getty 38400 tty6

And then after:

# ps -ef | grep getty
root  2660 1  0 Jul24 tty1 00:00:00 /sbin/getty 38400 tty1
root  2661 1  0 Jul24 tty2 00:00:00 /sbin/getty 38400 tty2
root  2662 1  0 Jul24 tty3 00:00:00 /sbin/getty 38400 tty3
root  2663 1  0 Jul24 tty4 00:00:00 /sbin/getty 38400 tty4
root  2664 1  0 Jul24 tty5 00:00:00 /sbin/getty 38400 tty5
root  2665 1  0 Jul24 tty6 00:00:00 /sbin/getty 38400 tty6
root 31705 1  0 11:33 ttyS000:00:00 /sbin/getty -L ttyS0 9600
vt102

And there's the getty on ttyS0 as expected.

That's all fine and good, but when I try to do this on my desktop PC
running Jessie, it doesn't work.  My PC is running an X server, Gnome,
etc., whereas the servers are not.  Also, on Wheezy, /sbin/getty and
/sbin/agetty seem to be two copies of the same file, wheras on Jessie,
/sbin/getty is a symlink to /sbin/agetty.

The PC is using the default /etc/inittab file.  When I check the list of
getty processes after a clean reboot, there's only this:

# ps -ef | grep getty
root  2092 1  0 11:50 tty1 00:00:00 /sbin/agetty --noclear tty1
linux

If I access the virtual consoles via CTRL-ALT-F1, etc., they show up in the
process list only after they have been accessed:

# ps -ef | grep getty
root  2092 1  0 11:50 tty1 00:00:00 /sbin/agetty --noclear tty1
linux
root  2998 1  0 11:56 tty2 00:00:00 /sbin/agetty --noclear tty2
linux
root  3001 1  0 11:56 tty3 00:00:00 /sbin/agetty --noclear tty3
linux

And still not in the same way that they appear on Wheezy ("/sbin/getty
38400 tty1", etc.).  If I add the line for the serial console to
/etc/inittab and reload the init deamon, or even reboot the PC, it simply
does nothing.  No getty process shows up on ttyS0, and no serial console is
available.

I know the serial port itself works, because I can connect to it from my
laptop, then do "screen /dev/ttyS0 9600" on the PC and see characters in
the screen session as I type them on the laptop.  So the serial port works,
and I/O seems to work, but I can't seem to start a persistent getty process
on that port and access the console through it.

Any ideas or suggestions are very much appreciated.

Thanks!
Dave

-- 
Dave Parker
Systems Administrator
Utica College
Integrated Information Technology Services
(315) 792-3229
Registered Linux User #408177

Re: Serial console over Bluetooth dongle to an android device {Will serial console satisfy my need}

[Stuart Longland]

On 30/06/15 22:04, venkat wrote:
 Dear all
 I am trying to display all the boot screen information in a android
 device. For this trial ,
 I notice that serial console is one of the available option to forward
 all display information messages to serial port.
 
 Before starting this process would like to understand the Pro' and
 cons on this
 
 setup information:
 Will follow the Link instruction to setup serial console.
 (changing TTYS1 to rfcomm) **Need to know that will that work
 http://www.cyberciti.biz/faq/linux-serial-console-howto/

I would love to be proven wrong, but I strongly doubt it'll be as simple
as that.

My understanding is that in addition to kernel drivers, Bluetooth serial
requires some userspace utilities in order to configure the stack.

USB Serial has a similar problem, USB initialisation happens so late in
the boot process, for a long time you couldn't use USB serial as a
console.  I understand this has been resolved now, it's worth pointing
out that USB serial doesn't require anything in userspace to work,
unlike Bluetooth.

The kernel would need to buffer output until the rfcomm connection was
established, then send its console output there.

Regards,
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55944ff8.7070...@longlandclan.yi.org

Serial console over Bluetooth dongle to an android device {Will serial console satisfy my need}

[venkat]

Dear all
I am trying to display all the boot screen information in a android 
device. For this trial ,
I notice that serial console is one of the available option to forward 
all display information messages to serial port.


Before starting this process would like to understand the Pro' and 
cons on this


setup information:
Will follow the Link instruction to setup serial console. 
(changing TTYS1 to rfcomm) **Need to know that will that work

http://www.cyberciti.biz/faq/linux-serial-console-howto/

Then the device should be auto paired with android
Run serial console app in android.

So far this is my understanding and planning to do a small POC on 
this.

request corrections and guidance

--
Regards
Venkat.S


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/559285c1.7060...@vortexindia.co.in

Re: Serial console, missing some output

[Geert Stappers]

On Thu, Sep 25, 2014 at 11:43:55PM +0200, Paul van der Vlis wrote:
 op 25-09-14 23:07, Geert Stappers schreef:
  On Thu, Sep 25, 2014 at 08:05:46PM +0200, Paul van der Vlis wrote:
  op 25-09-14 19:44, Geert Stappers schreef:
 
  De regels die nu nog gemist worden, welke zijn dat?
 
  Bijvoorbeeld deze regels:
  [ ok ] Mounting local filesystems...done.
  [ ok ] Activating swapfile swap...done.
 
  Zie bijvoorbeeld http://www.youtube.com/watch?v=PEJJ96_Qltw
  om 5:32. Het is wat klein, maar als je de video full-screen zet is het
  goed te lezen. En ook zonder flash ;-)
  
  Mijn observating van het werkende voorbeeld:
  * System V init
  * Er zit kleur in, de ok uit '[ ok ] Activating swapfile swap...done.'
is groen.
  * De ok, die pas bekend is als de actie klaar is, staat aan het begin
van de regel. Voor serial output is cursor verplaatsen complex
 
 Dat verbaasde mij ook.
 
  Over de _niet_ werkende configuratie, met serial console:
  * Is dat misschien systemd?
 
 Nee, gewoon init.d.
 
  * Wat is er voor TERM ingesteld? Zit dat ook aan de andere kant
van de serial line?
 
} in /etc/inittab:
 T1:23:respawn:/sbin/getty -L ttyS1 115200 vt100
 In de IPMI is ook vt100 ingesteld.

Ja, en dan voordat die getty wakker wordt. De log in werkt immers.
We zijn opzoek naar output die eerder dan de login prompt komt.

Waar TERM ingesteld is voor het opstart deel waar nu output gemist wordt,
weet ik zo ook niet. Waarschijnlijk in /etc/init.d/rcS, maar heb ik niet
verder onderzocht. Die /etc/init.d/rcS komt van deze regel
  si::sysinit:/etc/init.d/rcS
uit /etc/inittab

Een debug tip:

   logger herkenpunt T=${TERM} C=$(tty)_
of in ouderwetse syntax
   logger herkenpunt T=$TERM C=`tty`_
toevoegen aan /etc/init.d/rcS of de scripts daaronder.
En later dan kijken wat je gevangen hebt
   grep herkenpunt /var/log/syslog

Zo is te achterhalen of TERM op iets staat wat ook aan de andere kant
van de lijn begrepen wordt.

Mocht je C=_ krijgen, dan was er geen TTY.
Dat hoeft niet de oorzaak van het probleem te zijn.
Dezelfde meting (debugging) dan op een werkend systeem uitvoeren
om zien of daar wel een TTY is.


Groeten
Geert Stappers



 Maar ik ben nog achter iets anders gekomen. Ik heb de laatste tijd
 getest met een webinterface die in de IPMI van de server zit, en daarin
 zit een Java-applicatie die SOL (serial over LAN) doet.
   knip/
A.u.b. on topic blijven.


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140926063105.gk9...@gpm.stappers.nl

Re: Serial console

[Paul van der Vlis]

op 26-09-14 01:10, Diederik de Haas schreef:
 On Wednesday 24 September 2014 13:20:23 Paul van der Vlis wrote:
 # toegevoegd door Paul voor IPMI
 T1:23:respawn:/sbin/getty -L ttyS1 115200 vt100
 
 Moet dat geen ttyS0 zijn?

Ik gebruik de tweede seriele poort. De eerste is een fysieke seriele
poort, de tweede wordt doorgelust naar IPMI, wat ik gebruik.

Groet,
Paul.



-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54252c24.6030...@vandervlis.nl

Re: Serial console, missing some output

[Paul van der Vlis]

op 26-09-14 08:31, Geert Stappers schreef:

 Ja, en dan voordat die getty wakker wordt. De log in werkt immers.
 We zijn opzoek naar output die eerder dan de login prompt komt.
 
 Waar TERM ingesteld is voor het opstart deel waar nu output gemist wordt,
 weet ik zo ook niet. Waarschijnlijk in /etc/init.d/rcS, maar heb ik niet
 verder onderzocht. Die /etc/init.d/rcS komt van deze regel
   si::sysinit:/etc/init.d/rcS
 uit /etc/inittab
 
 Een debug tip:
 
logger herkenpunt T=${TERM} C=$(tty)_
 of in ouderwetse syntax
logger herkenpunt T=$TERM C=`tty`_
 toevoegen aan /etc/init.d/rcS of de scripts daaronder.
 En later dan kijken wat je gevangen hebt
grep herkenpunt /var/log/syslog
 
 Zo is te achterhalen of TERM op iets staat wat ook aan de andere kant
 van de lijn begrepen wordt.
 
 Mocht je C=_ krijgen, dan was er geen TTY.
 Dat hoeft niet de oorzaak van het probleem te zijn.
 Dezelfde meting (debugging) dan op een werkend systeem uitvoeren
 om zien of daar wel een TTY is.

Ik ga je tips nog beter bestuderen.

 Maar ik ben nog achter iets anders gekomen. Ik heb de laatste tijd
 getest met een webinterface die in de IPMI van de server zit, en daarin
 zit een Java-applicatie die SOL (serial over LAN) doet.
knip/
 A.u.b. on topic blijven.

Dit is heel on topic. Ik dacht een seriele console te testen, maar ik
heb hiervoor een applicatie gebruikt die waarschijnlijk een ander
protocol gebruikt (VNC?). Daarom moet ik wat testen over gaan doen.

Dit is wel off-topic:
Die java-applicatie (Redirection Viewer 1.46 van AMI) geeft overigens
een heel mooi resultaat, mooier dan de seriele console. Misschien
gebruikt het een open protocol zoals VNC, en is het dus vervangbaar door
wat anders met een soortgelijk mooi resultaat. Ik vond hier wat
informatie: http://www.webhostingtalk.com/showthread.php?t=1242946
Dit mooie resultaat heeft overigens ook een nadeel: omdat het grafisch
is kun je geen copy/paste doen van bijvoorbeeld errors.

Groet,
Paul.

-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5425325a.3020...@vandervlis.nl

Re: Serial console

[Jan-Rens Reitsma]

On 09/25/2014 03:14 PM, Paul van der Vlis wrote:

op 25-09-14 13:24, Frans van Berckel schreef:

Paul,

Voor wat betreft het niet op een scherm verschijnen van de kernel
output, heb ik reeds aangegeven dat je GRUB_CMDLINE_LINUX_DEFAULT=
moet aanpassen.


Maar dat is niet de oplossing, zie mijn andere berichten.

Op een vers geinstalleerde laptop staat er ook quiet en ik zie daar de
meldingen van startende services wel.

Ik heb de indruk dat de berichten van startende services op een snelle
machine niet getoond worden, en op een langzame machine wel.


Het zou wel eens kunnen kloppen dat het probleem veroorzaakt wordt door 
verschillen in snelheid tussen bepaalde onderdelen in het systeem. Na de 
discussie over de snel langsflitsende foutmeldingen heb ik op een 
vieze laptop bootlogd geïnstalleerd om te zien hoe dat werkt.


Het resultaat valt een beetje tegen. MEESTAL krijg ik alle foutmeldingen 
te zien, maar dat is niet gegarandeerd, want soms vallen ze halverwege 
weg. Misschien bevindt jou probleem zich aan de andere kant van de 
scheidslijn en vallen bepaalde foutmeldingen op een ttyS0 altijd weg.



Op een snelle machine is het wellicht ook minder zinvol, de berichten
schieten te snel voorbij. Dit ben ik nu aan het navragen op de
engelstalige debian-user lijst, nog geen reactie.


Voor wat betreft de [...]- en [ok]-meldingen heb ik
reeds aangegeven dat je GRUB_CMDLINE_LINUX=console=tty1
console=ttyS2,115200n81 moet aanpassen.


De [..] meldingen zie ik wel (ik noem dat de berichten van initramfs).
Dus daarmee geen problemen.

De [ok] meldingen zie ik niet (ik noem dat de berichten van startende
services).

Als ik console=tty0 in console=tty1 verander, dan zie ik geen verschil.


Wil je de bestaande grub configuratie niet aanpassen, doe het dan met e
in Grub. Voor de duidelijkheid, check of dit werk bij de computer!


Een duistere reden zou bijvoorbeeld kunnen zijn dat er een buffer 
overschreven of gewist wordt.


Groeten,
Jan-Rens.


--
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54254894.5050...@gmail.com

Re: Serial console

[Jan-Rens Reitsma]

On 09/24/2014 01:20 PM, Paul van der Vlis wrote:

Hoi,

Ik ben bezig met het instellen van de serial console van een server.
alles werkt, alleen zie ik de services niet starten.


Bedoel je met alles werkt dat je bijvoorbeeld via ssh kunt inloggen of 
met je browser een webpagina op de server kunt zien?


Wat ik zie:
- de berichten aan het begin, ik kan in het bios komen
- het grub menu
- de meldingen van initramfs


Bedoel je de melding van het opstarten van INIT: version 2.88 en de 
meldingen die vervolgens door init naar de console geschreven worden?



- GEEN meldingen van services die starten


Bedoel je de [...]- en [ok]-meldingen van init over het opstarten van de 
services?



- de loginprompt, ik kan inloggen e.d.

Wat ik dus niet zie zijn de meldingen van de services, en ik snap niet
goed hoe ik dat moet veranderen.


Zijn de services na het inloggen ook niet met

# ps -edaf | grep servicenaam

te zien?

Groeten,
Jan-Rens.


--
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5423d532.4060...@gmail.com

Re: Serial console

[Frans van Berckel]

Paul,

  Wat ik zie:
  - de berichten aan het begin, ik kan in het bios komen
  - het grub menu
  - de meldingen van initramfs
  
  Bedoel je de melding van het opstarten van INIT: version 2.88 en de
  meldingen die vervolgens door init naar de console geschreven worden?
 
 Nee. Ik bedoel de meldingen van initrd. Dat wordt door het kernel
 geladen, helemaal aan het begin van het booten.
 Het zijn van die meldingen met nummers ervoor, zoals in dmesg.
 
  - GEEN meldingen van services die starten
  
  Bedoel je de [...]- en [ok]-meldingen van init over het opstarten van de
  services?
 
 Ja. Maar het bleek later dat deze ook niet op een scherm te zien zijn
 wat aan de computer hangt.

Voor wat betreft het niet op een scherm verschijnen van de kernel
output, heb ik reeds aangegeven dat je GRUB_CMDLINE_LINUX_DEFAULT=
moet aanpassen. Voor wat betreft de [...]- en [ok]-meldingen heb ik
reeds aangegeven dat je GRUB_CMDLINE_LINUX=console=tty1
console=ttyS2,115200n81 moet aanpassen.

Wil je de bestaande grub configuratie niet aanpassen, doe het dan met e
in Grub. Voor de duidelijkheid, check of dit werk bij de computer!

Laat ons svp weten wat er anders is. Daarna kan je met serieel verder.

Met vriendelijke groet,

Frans van Berckel


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1411644259.1787.1.ca...@xs4all.nl

Re: Serial console

[sp113438]

On Thu, 25 Sep 2014 15:14:47 +0200
Paul van der Vlis p...@vandervlis.nl wrote:

 op 25-09-14 13:24, Frans van Berckel schreef:
  Paul,
  
  Wat ik zie:
  - de berichten aan het begin, ik kan in het bios komen
  - het grub menu
  - de meldingen van initramfs
 
  Bedoel je de melding van het opstarten van INIT: version 2.88 en
  de meldingen die vervolgens door init naar de console geschreven
  worden?
 
  Nee. Ik bedoel de meldingen van initrd. Dat wordt door het kernel
  geladen, helemaal aan het begin van het booten.
  Het zijn van die meldingen met nummers ervoor, zoals in dmesg.
 
  - GEEN meldingen van services die starten
 
  Bedoel je de [...]- en [ok]-meldingen van init over het opstarten
  van de services?
 
  Ja. Maar het bleek later dat deze ook niet op een scherm te zien
  zijn wat aan de computer hangt.
  
  Voor wat betreft het niet op een scherm verschijnen van de kernel
  output, heb ik reeds aangegeven dat je GRUB_CMDLINE_LINUX_DEFAULT=
  moet aanpassen. 
 
 Maar dat is niet de oplossing, zie mijn andere berichten.
 
 Op een vers geinstalleerde laptop staat er ook quiet en ik zie daar
 de meldingen van startende services wel.
 
 Ik heb de indruk dat de berichten van startende services op een snelle
 machine niet getoond worden, en op een langzame machine wel.
 Op een snelle machine is het wellicht ook minder zinvol, de berichten
 schieten te snel voorbij. Dit ben ik nu aan het navragen op de
 engelstalige debian-user lijst, nog geen reactie.
 
  Voor wat betreft de [...]- en [ok]-meldingen heb ik
  reeds aangegeven dat je GRUB_CMDLINE_LINUX=console=tty1
  console=ttyS2,115200n81 moet aanpassen.
 
 De [..] meldingen zie ik wel (ik noem dat de berichten van
 initramfs). Dus daarmee geen problemen.
 
 De [ok] meldingen zie ik niet (ik noem dat de berichten van startende
 services).
 
 Als ik console=tty0 in console=tty1 verander, dan zie ik geen
 verschil.
 
ik heb quiet console=tty12, dan komen de meldingen op console 12 en
daar blijven ze staan.

groet


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140925153744.67adc40f@fx4100

Re: Serial console

[Paul van der Vlis]

op 25-09-14 15:37, sp113438 schreef:

 Als ik console=tty0 in console=tty1 verander, dan zie ik geen
 verschil.

 ik heb quiet console=tty12, dan komen de meldingen op console 12 en
 daar blijven ze staan.

Wel een interessant idee, maar niet erg geschikt voor de seriele console
lijkt me.

Je hebt overigens ook het pakket bootlogd, waarmee de meldingen in een
logbestand komen.

Ik was nu echter niet op zoek naar een work-arround, ik wil graag zeker
weten dat de seriele console helemaal goed werkt.

Met vriendelijk groet,
Paul van der Vlis



-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54242589.10...@vandervlis.nl

Re: Serial console, missing some output

[Paul van der Vlis]

op 25-09-14 19:44, Geert Stappers schreef:
 On Thu, Sep 25, 2014 at 04:24:09PM +0200, Paul van der Vlis wrote:

 Ik was nu echter niet op zoek naar een work-arround, ik wil graag zeker
 weten dat de seriele console helemaal goed werkt.
 
 De regels die nu nog gemist worden, welke zijn dat?

Bijvoorbeeld deze regels:
[ ok ] Mounting local filesystems...done.
[ ok ] Activating swapfile swap...done.

 Ja, dat mogen de regels zijn van de laptop waar ze wel zijn.
 Dus a.u.b. geen het probleem is juist dat het er niet is,
 maar wat de verwachting is. Het mag ook een (matige) foto zijn
 van het beeldscherm op het moment dat ze er wel zijn.

Zie bijvoorbeeld http://www.youtube.com/watch?v=PEJJ96_Qltw
om 5:32. Het is wat klein, maar als je de video full-screen zet is het
goed te lezen. En ook zonder flash ;-)

Groet,
Paul.






-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5424597a.8040...@vandervlis.nl

Re: Serial console, missing some output

[Geert Stappers]

On Thu, Sep 25, 2014 at 08:05:46PM +0200, Paul van der Vlis wrote:
 op 25-09-14 19:44, Geert Stappers schreef:
  On Thu, Sep 25, 2014 at 04:24:09PM +0200, Paul van der Vlis wrote:
 
  Ik was nu echter niet op zoek naar een work-arround, ik wil graag zeker
  weten dat de seriele console helemaal goed werkt.
  
  De regels die nu nog gemist worden, welke zijn dat?
 
 Bijvoorbeeld deze regels:
 [ ok ] Mounting local filesystems...done.
 [ ok ] Activating swapfile swap...done.
 
 Zie bijvoorbeeld http://www.youtube.com/watch?v=PEJJ96_Qltw
 om 5:32. Het is wat klein, maar als je de video full-screen zet is het
 goed te lezen. En ook zonder flash ;-)

Mijn observating van het werkende voorbeeld:
* System V init
* Er zit kleur in, de ok uit '[ ok ] Activating swapfile swap...done.'
  is groen.
* De ok, die pas bekend is als de actie klaar is, staat aan het begin
  van de regel. Voor serial output is cursor verplaatsen complex


Over de _niet_ werkende configuratie, met serial console:
* Is dat misschien systemd?
* Wat is er voor TERM ingesteld? Zit dat ook aan de andere kant
  van de serial line?


Groeten
Geert Stappers
-- 
Leven en laten leven


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140925210706.gi9...@gpm.stappers.nl

Re: Serial console, missing some output

[Paul van der Vlis]

op 25-09-14 23:07, Geert Stappers schreef:
 On Thu, Sep 25, 2014 at 08:05:46PM +0200, Paul van der Vlis wrote:
 op 25-09-14 19:44, Geert Stappers schreef:
 On Thu, Sep 25, 2014 at 04:24:09PM +0200, Paul van der Vlis wrote:

 Ik was nu echter niet op zoek naar een work-arround, ik wil graag zeker
 weten dat de seriele console helemaal goed werkt.

 De regels die nu nog gemist worden, welke zijn dat?

 Bijvoorbeeld deze regels:
 [ ok ] Mounting local filesystems...done.
 [ ok ] Activating swapfile swap...done.

 Zie bijvoorbeeld http://www.youtube.com/watch?v=PEJJ96_Qltw
 om 5:32. Het is wat klein, maar als je de video full-screen zet is het
 goed te lezen. En ook zonder flash ;-)
 
 Mijn observating van het werkende voorbeeld:
 * System V init
 * Er zit kleur in, de ok uit '[ ok ] Activating swapfile swap...done.'
   is groen.
 * De ok, die pas bekend is als de actie klaar is, staat aan het begin
   van de regel. Voor serial output is cursor verplaatsen complex

Dat verbaasde mij ook.

 Over de _niet_ werkende configuratie, met serial console:
 * Is dat misschien systemd?

Nee, gewoon init.d.

 * Wat is er voor TERM ingesteld? Zit dat ook aan de andere kant
   van de serial line?

De environment variable $TERM geeft xterm. Zelfs op de server waar
niet eens X geinstalleerd is.

Maar waarschijnlijk bedoel je dit in /etc/inittab:
T1:23:respawn:/sbin/getty -L ttyS1 115200 vt100
In de IPMI is ook vt100 ingesteld.

Maar ik ben nog achter iets anders gekomen. Ik heb de laatste tijd
getest met een webinterface die in de IPMI van de server zit, en daarin
zit een Java-applicatie die SOL (serial over LAN) doet.
Uit luiheid heb ik regelmatig die java-applicatie gebruikt in plaats van
vrije IPMI-tools.

Ik heb nu de indruk dat dat deze java-applicatie helemaal geen gewone
SOL (serial over ethernet) doet, of een andere vorm. Als ik nu weer met
OSS applicaties test, dan krijg ik andere resultaten. Ik zie nu
bijvoorbeeld geen meldingen van initrd meer via IPMI, en die staan wel
op het scherm aan de server. En de kwaliteit is een stuk minder, het
scherm wordt soms niet goed gewist.

Verder had ik met een debian live usb-stick gestart, en ik zag alle
output van die stick in kleur op het scherm via die java-applicatie.
Zelfs Gnome! En op die livestick is er natuurlijk niets geredirect naar
serieel. Ik heb dus wellicht verkeerd lopen testen met die
java-applicatie, want ik wil OSS-tools gebruiken.

Groet,
Paul.


-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54248c9b.7010...@vandervlis.nl

Re: Serial console

[Diederik de Haas]

On Wednesday 24 September 2014 13:20:23 Paul van der Vlis wrote:
 # toegevoegd door Paul voor IPMI
 T1:23:respawn:/sbin/getty -L ttyS1 115200 vt100

Moet dat geen ttyS0 zijn?
-- 
GPG: 0x138E41915C7EFED6

signature.asc
Description: This is a digitally signed message part.

Serial console

[Paul van der Vlis]

Hoi,

Ik ben bezig met het instellen van de serial console van een server.
alles werkt, alleen zie ik de services niet starten.

Wat ik zie:
- de berichten aan het begin, ik kan in het bios komen
- het grub menu
- de meldingen van initramfs
- GEEN meldingen van services die starten
- de loginprompt, ik kan inloggen e.d.

Wat ik dus niet zie zijn de meldingen van de services, en ik snap niet
goed hoe ik dat moet veranderen.

De serial console zit aan com2, dat kan moeilijk anders.

Dit staat er in mijn /etc/default/grub op het moment:

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2 /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=quiet
GRUB_SERIAL_COMMAND=serial --unit=2 --speed=115200 --stop=1
GRUB_TERMINAL=console serial
GRUB_CMDLINE_LINUX=console=tty0 console=ttyS2,115200n81


Raar is die --unit=2, want volgens de grub manual moet dat --unit=1
moeten zijn voor COM2. Maar als ik dat opgeef dan doet het grub-menu het
niet meer, en ook de meldingen van de services niet.
http://www.gnu.org/software/grub/manual/grub.html#serial

Heeft iemand een idee wat me verder kan helpen?

Uiteraard zou het probleem ook in /etc/inittab kunnen zitten.
Ik zal het script hieronder afdrukken.

Groet,
Paul.

/etc/inittab
---
# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# The default runlevel.
id:2:initdefault:

# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS

# What to do in single-user mode.
~~:S:wait:/sbin/sulogin

# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin

# What to do when CTRL-ALT-DEL is pressed.
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now

# Action on special keypress (ALT-UpArrow).
#kb::kbrequest:/bin/echo Keyboard Request--edit /etc/inittab to let
this work.

# What to do when the power fails/returns.
pf::powerwait:/etc/init.d/powerfail start
pn::powerfailnow:/etc/init.d/powerfail now
po::powerokwait:/etc/init.d/powerfail stop

# /sbin/getty invocations for the runlevels.
#
# The id field MUST be the same as the last
# characters of the device (after tty).
#
# Format:
#  id:runlevels:action:process
#
# Note that on most Debian systems tty7 is used by the X Window System,
# so if you want to add more getty's go ahead but skip tty7 if you run X.
#
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6

# Example how to put a getty on a serial line (for a terminal)
#
#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
#T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100

# Example how to put a getty on a modem line.
#
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3

# toegevoegd door Paul voor IPMI
T1:23:respawn:/sbin/getty -L ttyS1 115200 vt100



-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5422a8f7.2000...@vandervlis.nl

Re: Serial console

[Frans van Berckel]

On Wed, 2014-09-24 at 13:20 +0200, Paul van der Vlis wrote:
 Hoi,
 
 Ik ben bezig met het instellen van de serial console van een server.
 alles werkt, alleen zie ik de services niet starten.
 
 Wat ik zie:
 - de berichten aan het begin, ik kan in het bios komen
 - het grub menu
 - de meldingen van initramfs
 - GEEN meldingen van services die starten
 - de loginprompt, ik kan inloggen e.d.
 
 Wat ik dus niet zie zijn de meldingen van de services, en ik snap niet
 goed hoe ik dat moet veranderen.
 
 De serial console zit aan com2, dat kan moeilijk anders.
 
 Dit staat er in mijn /etc/default/grub op het moment:
 
 GRUB_DEFAULT=0
 GRUB_TIMEOUT=5
 GRUB_DISTRIBUTOR=`lsb_release -i -s 2 /dev/null || echo Debian`
 GRUB_CMDLINE_LINUX_DEFAULT=quiet
 GRUB_SERIAL_COMMAND=serial --unit=2 --speed=115200 --stop=1
 GRUB_TERMINAL=console serial
 GRUB_CMDLINE_LINUX=console=tty0 console=ttyS2,115200n81
 

Paul,

Haal in deze regel GRUB_CMDLINE_LINUX_DEFAULT=quiet even quiet weg!

Met vriendelijke groet,

Frans van Berckel 


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1411562328.16643.1.ca...@xs4all.nl

Berichten van startende services (was: Re: Serial console)

[Paul van der Vlis]

Hallo Frans, en anderen,

op 24-09-14 14:38, Frans van Berckel schreef:
 On Wed, 2014-09-24 at 13:20 +0200, Paul van der Vlis wrote:
 Hoi,

 Ik ben bezig met het instellen van de serial console van een server.
 alles werkt, alleen zie ik de services niet starten.

 Wat ik zie:
 - de berichten aan het begin, ik kan in het bios komen
 - het grub menu
 - de meldingen van initramfs
 - GEEN meldingen van services die starten
 - de loginprompt, ik kan inloggen e.d.

 Wat ik dus niet zie zijn de meldingen van de services, en ik snap niet
 goed hoe ik dat moet veranderen.

 De serial console zit aan com2, dat kan moeilijk anders.

 Dit staat er in mijn /etc/default/grub op het moment:
 
 GRUB_DEFAULT=0
 GRUB_TIMEOUT=5
 GRUB_DISTRIBUTOR=`lsb_release -i -s 2 /dev/null || echo Debian`
 GRUB_CMDLINE_LINUX_DEFAULT=quiet
 GRUB_SERIAL_COMMAND=serial --unit=2 --speed=115200 --stop=1
 GRUB_TERMINAL=console serial
 GRUB_CMDLINE_LINUX=console=tty0 console=ttyS2,115200n81
 
 
 Paul,
 
 Haal in deze regel GRUB_CMDLINE_LINUX_DEFAULT=quiet even quiet weg!

Dat heb ik voor de grap even gedaan, en tot mijn verbazing wou de
machine daarna helemaal niet meer starten. Ik zag Linux en initrd wel
starten met veel berichten, maar daarna niets meer, ook geen netwerk.

Via een boot-stick heb ik de boel weer aan de praat gekregen, dat had
achteraf gezien ook prima via het grub-menu gekund.

Maar omdat ik fysiek naar de machine ben toegegaan (bah, wat maakt dat
ding een klereherrie) zag ik dat hij ook op een aangesloten monitor geen
berichten geeft over services die starten. Vreemd. En dit is een machine
met harddisks, dus zo snel gaat het niet.

Iemand een idee hoe je de berichten over startende services aan/uit kunt
zetten?

Met vriendelijke groet,
Paul van der Vlis.





-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5422cc3c.3080...@vandervlis.nl

Re: Berichten van startende services (was: Re: Serial console)

[Thijs Kinkhorst]

Dag Paul,

On Wed, September 24, 2014 15:50, Paul van der Vlis wrote:
 op 24-09-14 14:38, Frans van Berckel schreef:
 On Wed, 2014-09-24 at 13:20 +0200, Paul van der Vlis wrote:
 Hoi,

 Ik ben bezig met het instellen van de serial console van een server.
 alles werkt, alleen zie ik de services niet starten.

 Wat ik zie:
 - de berichten aan het begin, ik kan in het bios komen
 - het grub menu
 - de meldingen van initramfs
 - GEEN meldingen van services die starten
 - de loginprompt, ik kan inloggen e.d.

 Wat ik dus niet zie zijn de meldingen van de services, en ik snap niet
 goed hoe ik dat moet veranderen.

 De serial console zit aan com2, dat kan moeilijk anders.

 Dit staat er in mijn /etc/default/grub op het moment:
 
 GRUB_DEFAULT=0
 GRUB_TIMEOUT=5
 GRUB_DISTRIBUTOR=`lsb_release -i -s 2 /dev/null || echo Debian`
 GRUB_CMDLINE_LINUX_DEFAULT=quiet
 GRUB_SERIAL_COMMAND=serial --unit=2 --speed=115200 --stop=1
 GRUB_TERMINAL=console serial
 GRUB_CMDLINE_LINUX=console=tty0 console=ttyS2,115200n81
 

 Paul,

 Haal in deze regel GRUB_CMDLINE_LINUX_DEFAULT=quiet even quiet weg!

 Dat heb ik voor de grap even gedaan, en tot mijn verbazing wou de
 machine daarna helemaal niet meer starten. Ik zag Linux en initrd wel
 starten met veel berichten, maar daarna niets meer, ook geen netwerk.

 Via een boot-stick heb ik de boel weer aan de praat gekregen, dat had
 achteraf gezien ook prima via het grub-menu gekund.

 Maar omdat ik fysiek naar de machine ben toegegaan (bah, wat maakt dat
 ding een klereherrie) zag ik dat hij ook op een aangesloten monitor geen
 berichten geeft over services die starten. Vreemd. En dit is een machine
 met harddisks, dus zo snel gaat het niet.

 Iemand een idee hoe je de berichten over startende services aan/uit kunt
 zetten?

I denk toch zeker dat dat moet met quiet zoals Frans zei, en als je
systeem unbootable wordt dan is er toch iets anders misgegaan denk ik. Je
kunt overigens quiet ook verwijderen van de kernel command line als je in
het grub-menu op e drukt.


Groeten,
Thijs


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/92622a84163deff41bf61be3dc5b16ae.squir...@aphrodite.kinkhorst.nl

Re: Berichten van startende services (was: Re: Serial console)

[Frans van Berckel]

On Wed, 2014-09-24 at 16:03 +0200, Thijs Kinkhorst wrote:
 Dag Paul,
 
 On Wed, September 24, 2014 15:50, Paul van der Vlis wrote:
  op 24-09-14 14:38, Frans van Berckel schreef:
  On Wed, 2014-09-24 at 13:20 +0200, Paul van der Vlis wrote:
  Hoi,
 
  Ik ben bezig met het instellen van de serial console van een server.
  alles werkt, alleen zie ik de services niet starten.
 
  Wat ik zie:
  - de berichten aan het begin, ik kan in het bios komen
  - het grub menu
  - de meldingen van initramfs
  - GEEN meldingen van services die starten
  - de loginprompt, ik kan inloggen e.d.
 
  Wat ik dus niet zie zijn de meldingen van de services, en ik snap niet
  goed hoe ik dat moet veranderen.
 
  De serial console zit aan com2, dat kan moeilijk anders.
 
  Dit staat er in mijn /etc/default/grub op het moment:
  
  GRUB_DEFAULT=0
  GRUB_TIMEOUT=5
  GRUB_DISTRIBUTOR=`lsb_release -i -s 2 /dev/null || echo Debian`
  GRUB_CMDLINE_LINUX_DEFAULT=quiet
  GRUB_SERIAL_COMMAND=serial --unit=2 --speed=115200 --stop=1
  GRUB_TERMINAL=console serial
  GRUB_CMDLINE_LINUX=console=tty0 console=ttyS2,115200n81
  
 
  Paul,
 
  Haal in deze regel GRUB_CMDLINE_LINUX_DEFAULT=quiet even quiet weg!
 
  Dat heb ik voor de grap even gedaan, en tot mijn verbazing wou de
  machine daarna helemaal niet meer starten. Ik zag Linux en initrd wel
  starten met veel berichten, maar daarna niets meer, ook geen netwerk.
 
  Via een boot-stick heb ik de boel weer aan de praat gekregen, dat had
  achteraf gezien ook prima via het grub-menu gekund.
 
  Maar omdat ik fysiek naar de machine ben toegegaan (bah, wat maakt dat
  ding een klereherrie) zag ik dat hij ook op een aangesloten monitor geen
  berichten geeft over services die starten. Vreemd. En dit is een machine
  met harddisks, dus zo snel gaat het niet.
 
  Iemand een idee hoe je de berichten over startende services aan/uit kunt
  zetten?
 
 I denk toch zeker dat dat moet met quiet zoals Frans zei, en als je
 systeem unbootable wordt dan is er toch iets anders misgegaan denk ik. Je
 kunt overigens quiet ook verwijderen van de kernel command line als je in
 het grub-menu op e drukt.

Voor de regel GRUB_CMDLINE_LINUX=console=tty0 console=ttyS2,115200n81
moet console=tty0 niet tty1 zijn?

Met vriendelijke groet

Frans van Berckel


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1411567812.17497.1.ca...@xs4all.nl

Re: help using serial console w/ netboot - SOLVED

[Chris Bannister]

On Mon, Oct 01, 2012 at 04:58:25PM -0400, Miles Fidelman wrote:
 turn into this:
  append vga=788 inited=debian-installer/i386/initrd.gz --
  ^^
 console=ttyS2,19200 earlyprint=serial,ttyS2,19200
 
 Now all seems to be working.

Weird.


-- 
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing. --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121003120854.GC25029@tal

Re: help using serial console w/ netboot - SOLVED

[Chris Bannister]

On Tue, Oct 02, 2012 at 12:10:02PM +0300, Lars Noodén wrote:
 On 10/1/12 11:58 PM, Miles Fidelman wrote:
 Sorry.  There's a typo, intited should be initrd.

Ahh! OOPs didn't read whole thread.

Still, it does show the reason why you should copy 'n' paste instead of
laboriously typing it out by hand.

-- 
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing. --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121003121154.GD25029@tal

Re: help using serial console w/ netboot - SOLVED

[lars nooden]

On 10/3/12, Chris Bannister cbannis...@slingshot.co.nz wrote:
 On Tue, Oct 02, 2012 at 12:10:02PM +0300, Lars Noodén wrote:
 Sorry.  There's a typo, intited should be initrd.

 Ahh! OOPs didn't read whole thread.

 Still, it does show the reason why you should copy 'n' paste instead of
 laboriously typing it out by hand.

Yeah.  I've since spent the effort to find out how to cut and paste in
plain vanilla tmux.

Regards
/Lars


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cacq_q0fg6-0tdmqtjf5op_psaa7kzzsdlnghgf4jpokyqhv...@mail.gmail.com

Re: help using serial console w/ netboot - SOLVED

[Lars Noodén]

On 10/1/12 11:58 PM, Miles Fidelman wrote:
 Turns out that the remote serial-over-ip terminal redirects COM3, and
 shows up as ttys2, which makes this
 

 debian-installer/i386/boot-screens/txt.cfg:
 append vga=788 inited=debian-installer/i386/initrd.gz --
 console=ttyS0,19200 earlyprint=serial,ttyS0,19200

 turn into this:
  append vga=788 inited=debian-installer/i386/initrd.gz --
 console=ttyS2,19200 earlyprint=serial,ttyS2,19200
 
 Now all seems to be working.
 
 Thanks folks.
 
 Miles

 
 
Sorry.  There's a typo, intited should be initrd.

Regards
/Lars


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/506aaf6a.8090...@gmail.com

help using serial console w/ netboot

[Miles Fidelman]

Hi Folks,

I'm trying to build a headless, remote server - using an IPMI serial 
terminal and PXEboot.  The thing is, that I've got everything set up to 
the point that the install system is booting (I can see the splash 
screen via a remote KVM), but can't access it via a remote serial console.


I think I need to put some magic incantation in   ../pxelinux.cfg, or 
possibly some other config file - but can't find any documentation on 
how to do it (what I have found is contradictory and doesn't work for 
me).  (For what it's worth, it's a supermicro rack-mount server, with 
on-board IPMI 2, but I think the issue is configuring the boot file 
properly.)


Any help would be much appreciated.

Thanks!

Miles Fidelman

--
In theory, there is no difference between theory and practice.
In practice, there is.    Yogi Berra


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/5069d194.9050...@meetinghouse.net

Re: help using serial console w/ netboot

[Lars Noodén]

On 10/1/12 8:23 PM, Miles Fidelman wrote:
 Hi Folks,
 
 I'm trying to build a headless, remote server - using an IPMI serial
 terminal and PXEboot.  The thing is, that I've got everything set up to
 the point that the install system is booting (I can see the splash
 screen via a remote KVM), but can't access it via a remote serial console.
 
 I think I need to put some magic incantation in   ../pxelinux.cfg, or
 possibly some other config file - but can't find any documentation on
 how to do it (what I have found is contradictory and doesn't work for
 me).  (For what it's worth, it's a supermicro rack-mount server, with
 on-board IPMI 2, but I think the issue is configuring the boot file
 properly.)
 
 Any help would be much appreciated.
 
 Thanks!
 
 Miles Fidelman
 
Serial booting with PXE booting needs changes in three places, from what
I recall.  These are from my notes, speed 19200:

debian-installer/i386/boot-screens/syslinux.cfg:

serial 0 19200 0


debian-installer/i386/boot-screens/txt.cfg: 

append vga=788 inited=debian-installer/i386/initrd.gz --
console=ttyS0,19200 earlyprint=serial,ttyS0,19200


debian-installer/i386/pxelinux.cfg/default:

serial 0 19200 0

There's a fair amount of more complete notes out there if you search a bit.

Regards,
/Lars


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5069d3ad.3060...@gmail.com

Re: help using serial console w/ netboot

[Miles Fidelman]

Hi Lars,

Lars Noodén wrote:

On 10/1/12 8:23 PM, Miles Fidelman wrote:

Hi Folks,

I'm trying to build a headless, remote server - using an IPMI serial
terminal and PXEboot.  The thing is, that I've got everything set up to
the point that the install system is booting (I can see the splash
screen via a remote KVM), but can't access it via a remote serial console.

Serial booting with PXE booting needs changes in three places, from what
I recall.  These are from my notes, speed 19200:

debian-installer/i386/boot-screens/syslinux.cfg:
serial 0 19200 0

debian-installer/i386/boot-screens/txt.cfg: 
append vga=788 inited=debian-installer/i386/initrd.gz --
console=ttyS0,19200 earlyprint=serial,ttyS0,19200

This is the line the seemed to be needed.  I've made progress, but not 
quite there yet (see below).

debian-installer/i386/pxelinux.cfg/default:
serial 0 19200 0

There's a fair amount of more complete notes out there if you search a bit.


Not that I've found.  The txt.cfg file fix wasn't in anything I found!

I now see the loading debian-installer/i386/initrd.gz line show up on 
the remote serial console, followed by lots of line feeds, then 
everything freezes, and there's nothing on the KVM screen this time (as 
I recall from my last install with a monitor connected, the installer 
will continue to feed info to the VGA console).


Any thoughts?

Thanks!

Miles



--
In theory, there is no difference between theory and practice.
In practice, there is.    Yogi Berra


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/5069d83b.7050...@meetinghouse.net

Re: help using serial console w/ netboot - SOLVED

[Miles Fidelman]

Turns out that the remote serial-over-ip terminal redirects COM3, and 
shows up as ttys2, which makes this




debian-installer/i386/boot-screens/txt.cfg:
append vga=788 inited=debian-installer/i386/initrd.gz --
console=ttyS0,19200 earlyprint=serial,ttyS0,19200


turn into this:
 append vga=788 inited=debian-installer/i386/initrd.gz --
console=ttyS2,19200 earlyprint=serial,ttyS2,19200

Now all seems to be working.

Thanks folks.

Miles





--
In theory, there is no difference between theory and practice.
In practice, there is.    Yogi Berra


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/506a03f1.4070...@meetinghouse.net

Re: Live Squeeze system: ConsoleKit does not see serial console as active, cannot mount with udisk

[Tom H]

On Mon, Apr 9, 2012 at 9:36 PM, Jason Heeris jason.hee...@gmail.com wrote:
 On 5 April 2012 21:08, Tom H tomh0...@gmail.com wrote:

 Re /usr/share/polkit-1/actions/org.freedesktop.udisks.policy: (It's
 better to create a pkla file in
 /etc/polkit-1/localauthority/50-local.d than edit a
 /usr/share/polkit-1/ file) Does pkaction display the changed values
 for org.freedesktop.udisks.filesystem-mount?

 I was not aware of the pkaction command, that's quite useful! Anyway,
 pkaction does list org.freedesktop.udisks.filesystem-mount, but I
 still get the Not authorized error when trying to mount the
 filesystem via the serial line.

You have to use pkaction --verbose --action-id
org.freedesktop.udisks.filesystem-mount to check whether the settings
are active.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=SxMCi0K7BhCD66UQVR=t4kzfy-dtnyiopc4efl0p-t...@mail.gmail.com

Re: Live Squeeze system: ConsoleKit does not see serial console as active, cannot mount with udisk

[Jason Heeris]

On 5 April 2012 16:52, Andrei POPESCU andreimpope...@gmail.com wrote:
 Maybe libpam-ck-connector helps?

Alas no :/

— Jason


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/CA+Zd3FcaDWYQBnVii38FVRhCED5A4KpcC
qcdmtlkpew+...@mail.gmail.com

Re: Live Squeeze system: ConsoleKit does not see serial console as active, cannot mount with udisk

[Jason Heeris]

On 5 April 2012 21:08, Tom H tomh0...@gmail.com wrote:
 Re pkexec true: Is your user a member of the sudo group? sudo group
 members can use pkexec via
 /etc/polkit-1/localauthority.conf.d/51-debian-sudo.conf. If you
 don't want that user in the sudo group, you can create a conf file in
 /etc/polkit-1/localauthority.conf.d to allow it to use pkexec.

I've added the live user to the sudo group, but it didn't make a
difference (I confirmed that 51-debian-sudo.conf is there, too).

 Re /usr/share/polkit-1/actions/org.freedesktop.udisks.policy: (It's
 better to create a pkla file in
 /etc/polkit-1/localauthority/50-local.d than edit a
 /usr/share/polkit-1/ file) Does pkaction display the changed values
 for org.freedesktop.udisks.filesystem-mount?

I was not aware of the pkaction command, that's quite useful! Anyway,
pkaction does list org.freedesktop.udisks.filesystem-mount, but I
still get the Not authorized error when trying to mount the
filesystem via the serial line.

— Jason


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/ca+zd3fesbkh6ddsslciasotxc3j07kpraf5pwtyx9u--at-...@mail.gmail.com

Re: Live Squeeze system: ConsoleKit does not see serial console as active, cannot mount with udisk

[Andrei POPESCU]

On Jo, 05 apr 12, 09:30:17, Jason Heeris wrote:
 
 So how do I get ConsoleKit to either recognise the serial console as
 active, or let udisks mount the partition?

Maybe libpam-ck-connector helps?

Kind regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: Live Squeeze system: ConsoleKit does not see serial console as active, cannot mount with udisk

[keith]

Jason Heeris wrote:

My problem is this: when I try to use udisk to mount an image via a
serial console, I get:


user@my-live-usb:~$ udisks --mount /dev/disk/by-label/image-data
--mount-options ro
Mount failed: Not Authorized


I read through a heap of forum postings and bug reports, and
eventually figured to try:


user@my-live-usb:~$ pkexec true
Error executing command as another user: Not authorized

This incident has been reported.

Do you need to be root?


--
Sent from Free Open Source Software
Debian GNU/Linux


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f7d6062.8090...@yahoo.co.uk

Re: Live Squeeze system: ConsoleKit does not see serial console as active, cannot mount with udisk

[Tom H]

On Wed, Apr 4, 2012 at 9:30 PM, Jason Heeris jason.hee...@gmail.com wrote:


 I'm building a Debian Squeeze system with live-builder 3.0~a45 (from
 Ubuntu 11.10). I'm running into a problem where I can't use udisk to
 mount devices using a serial console on the live system (perhaps due
 to problems with consolekit or policykit).

 I configure a serial console using the boot line and some boot-time
 sedding to produce this line in /etc/inittab:

  T0:23:respawn:/bin/login -f user /dev/ttyS0 /dev/ttyS0 21

 My problem is this: when I try to use udisk to mount an image via a
 serial console, I get:

 
 user@my-live-usb:~$ udisks --mount /dev/disk/by-label/image-data
 --mount-options ro
 Mount failed: Not Authorized
 

 I read through a heap of forum postings and bug reports, and
 eventually figured to try:

 
 user@my-live-usb:~$ pkexec true
 Error executing command as another user: Not authorized

 This incident has been reported.
 

 Then I ran ck-list-sessions and saw that only Session 5, on
 /dev/tty1, has active = TRUE - the console I'm actually using
 (Session 1 on /dev/ttyS0) has active = FALSE.

 Am I right in thinking that this is why udisk is failing to mount the
 device when run on a serial console? I checked that my udisks command
 worked with a video console, and it does. But unfortunately, this is
 not practical - I need to be able to run the command at a serial
 console OR a video console.

 It's worth pointing out that under this live system, the default user
 (user) is automatically logged in on every video console and the
 serial console.

 If I look in /usr/share/polkit-1/actions/org.freedesktop.udisks.policy,
 there's a group of keys under action
 id=org.freedesktop.udisks.filesystem-mount:

  allow_anyno/allow_any
  allow_inactiveno/allow_inactive
  allow_activeyes/allow_active

 Changing the allow_inactive and allow_any keys to yes makes no
 difference. I figure that I somehow need to tell consolekit that the
 serial port is an active console. But how?

I haven't used polkit since Fedora 12 was released with weird package
installation defaults and I don't have access to the notes that I made
at the time so what follows is just from looking at a Sid VM that I
have running.

Re pkexec true: Is your user a member of the sudo group? sudo group
members can use pkexec via
/etc/polkit-1/localauthority.conf.d/51-debian-sudo.conf. If you
don't want that user in the sudo group, you can create a conf file in
/etc/polkit-1/localauthority.conf.d to allow it to use pkexec.

Re /usr/share/polkit-1/actions/org.freedesktop.udisks.policy: (It's
better to create a pkla file in
/etc/polkit-1/localauthority/50-local.d than edit a
/usr/share/polkit-1/ file) Does pkaction display the changed values
for org.freedesktop.udisks.filesystem-mount?

No idea what to say or do about your ck-list-sessions output, sorry.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=SyWqb+rVWY-ks9N2t9n3t+=pwozek1knpo2uctp9...@mail.gmail.com

Re: Live Squeeze system: ConsoleKit does not see serial console as active, cannot mount with udisk

[Tom H]

On Thu, Apr 5, 2012 at 5:05 AM, keith keith...@yahoo.co.uk wrote:
 Jason Heeris wrote:

 user@my-live-usb:~$ pkexec true
 Error executing command as another user: Not authorized

 This incident has been reported.

 Do you need to be root?

pkexec is like sudo so you don't need to be root but you do need to be
authorized to use it.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=sxdkcquvdse+anaev0g_mzoo5tvjkeh18w2kg_zohn...@mail.gmail.com

Live Squeeze system: ConsoleKit does not see serial console as active, cannot mount with udisk

[Jason Heeris]

I'm building a Debian Squeeze system with live-builder 3.0~a45 (from
Ubuntu 11.10). I'm running into a problem where I can't use udisk to
mount devices using a serial console on the live system (perhaps due
to problems with consolekit or policykit). Sorry for the cross-post -
I've already asked about this on the debian-live list, and they had no
idea, so I'm asking here.

I configure a serial console using the boot line and some boot-time
sedding to produce this line in /etc/inittab:

  T0:23:respawn:/bin/login -f user /dev/ttyS0 /dev/ttyS0 21

My problem is this: when I try to use udisk to mount an image via a
serial console, I get:


user@my-live-usb:~$ udisks --mount /dev/disk/by-label/image-data
--mount-options ro
Mount failed: Not Authorized


I read through a heap of forum postings and bug reports, and
eventually figured to try:


user@my-live-usb:~$ pkexec true
Error executing command as another user: Not authorized

This incident has been reported.


Then I ran ck-list-sessions and saw that only Session 5, on
/dev/tty1, has active = TRUE - the console I'm actually using
(Session 1 on /dev/ttyS0) has active = FALSE.

Am I right in thinking that this is why udisk is failing to mount the
device when run on a serial console? I checked that my udisks command
worked with a video console, and it does. But unfortunately, this is
not practical - I need to be able to run the command at a serial
console OR a video console.

It's worth pointing out that under this live system, the default user
(user) is automatically logged in on every video console and the
serial console.

If I look in /usr/share/polkit-1/actions/org.freedesktop.udisks.policy,
there's a group of keys under action
id=org.freedesktop.udisks.filesystem-mount:

 allow_anyno/allow_any
 allow_inactiveno/allow_inactive
 allow_activeyes/allow_active

Changing the allow_inactive and allow_any keys to yes makes no
difference. I figure that I somehow need to tell consolekit that the
serial port is an active console. But how?

I dug around the ConsoleKit docs and played around with the DBUS
methods for activating the current session, but it didn't work:

user@mwa-live-usb:~$ dbus-send --system --print-reply
--dest=org.freedesktop.ConsoleKit
/org/freedesktop/ConsoleKit/Session7
org.freedesktop.ConsoleKit.Session.Activate
Error org.freedesktop.DBus.GLib.UnmappedError.CkSeatError.Code0:
Unable to activate session

So how do I get ConsoleKit to either recognise the serial console as
active, or let udisks mount the partition?

(udisks is 1.0.1+git20100614-3, consolekit is 0.4.1-4)

Thanks,
Jason


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CA+Zd3FcVOrVV1eN1gFYwK8K-Jqq=FJnY=4k-a+amqy6evre...@mail.gmail.com

Re: Serial Console Access

[Chris Brennan]

On Mon, May 23, 2011 at 12:04 AM, David Parker dpar...@utica.edu wrote:

Was your onboard serial port disabled in the BIOS at the time you installed
 Debian?  If it was, then the first port on your serial card should be mapped
 to /dev/ttyS0.  If not, then udev may have picked up the onboard port as
 /dev/ttyS0 and made your card /dev/ttyS1 (or another number).


No, originally the on-board serial device was enabled in the BIOS when I
plopped the card in, I've since disabled it in the BIOS and sometimes now
when I reboot this box, and run setserial, I will see either one or two
serial devices listed. The on-board device always showed up with a low IRQ
and the Serial card is IRQ16, so I was able to tell which device I was
using. During my troubleshooting, before sending my initial email), I had
set everything up to use ttyS0 and ttyS1 anyway, just to cover all my bases,
but I still got no login when I tried to connect via serial.



 I have two Debian 4 boxes with the serial console working.  It has been
 quite a while since I set this up, but I'm pretty sure that I just added
 this line to /etc/inittab and then restarted init:

 co:2345:respawn:/sbin/getty -L ttyS0 9600 vt102



I think the co may have something to do with it.  Sorry I can't be more
 help, I'm really rusty on this.  I did this 5 years ago and I've never had
 to do it again.


What does co do vs TO? Admittidly, I don't know much about how this works,
so like a smart monkey, I did what I saw wrote about the most. Also, how are
you restarting init w/o rebooting?

-- 
 A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting frowned upon?

Re: Serial Console Access

[Camaleón]

On Sun, 22 May 2011 18:05:47 -0400, Chris Brennan wrote:

 I've embarked on the trial and error process of setting up a serial
 console on my Debian 6 machine. So far, the configuration has been
 pretty straight forward. As a reference point I used the following two
 websites

(...)

115200 is a bit high speed rate, for testing I would lower that value and 
once it works, you can play with this.

 In windows, I've got a 2-port serial card, it is properly recognized as
 COM3 and COM4. When I try to open a connection to the Debian box via
 COM3/COM4, all I get is a black screen and I can't tell if I am actually
 connected to the serial console or not  I am curious if I missed
 something here ... I tend to experiment a lot and serial access would
 just make things so much easier when I am forced to reboot this box and
 it doesn't come back up ... a lot easier then lugging a 60lb CRT onto my
 desk to plug into that computer 

I suppose you already rebooted the computer you wanted to connect to, 
right?

OTOH, /etc/inittab can be restarted/reloaded by issuing telinit q, or 
at least that was what I used on another distributions, in Debian I'm not 
sure if remains the same (reviewing the manual...) hum, yep, it's the 
same :-)

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.05.23.16.07...@gmail.com

Re: Serial Console Access

[Chris Brennan]

On Mon, May 23, 2011 at 12:07 PM, Camaleón noela...@gmail.com wrote:

115200 is a bit high speed rate, for testing I would lower that value and
 once it works, you can play with this.


Yeah, it is high, that was just my last change, I started at the typical
9600, went to 19200, 38400 and then 115200. All produces the same black
window from putty.


 I suppose you already rebooted the computer you wanted to connect to,
 right?


Many times ...



 OTOH, /etc/inittab can be restarted/reloaded by issuing telinit q, or
 at least that was what I used on another distributions, in Debian I'm not
 sure if remains the same (reviewing the manual...) hum, yep, it's the
 same :-)


This saves me from having to repeatedly reboot the box  thanks :D

For shiggles, I changed 115200 back to 9600 and used telinit q :D, same
thing, black screen, no login prompt

-- 
 A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.

 Q: Why is top posting frowned upon?

Re: Serial Console Access

[Camaleón]

On Mon, 23 May 2011 12:17:29 -0400, Chris Brennan wrote:

 On Mon, May 23, 2011 at 12:07 PM, Camaleón noela...@gmail.com wrote:

(...)

 OTOH, /etc/inittab can be restarted/reloaded by issuing telinit q, or
 at least that was what I used on another distributions, in Debian I'm
 not sure if remains the same (reviewing the manual...) hum, yep, it's
 the same :-)


 This saves me from having to repeatedly reboot the box  thanks :D
 
 For shiggles, I changed 115200 back to 9600 and used telinit q :D, same
 thing, black screen, no login prompt

What happens if you press any key although there is no prompt?

Can you test the serial connection from a client other than windows
+putty? Just to start discarding culprits...

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.05.23.17.14...@gmail.com

Re: Serial Console Access

[Chris Brennan]

On Mon, May 23, 2011 at 1:14 PM, Camaleón noela...@gmail.com wrote:

On Mon, 23 May 2011 12:17:29 -0400, Chris Brennan wrote:

  On Mon, May 23, 2011 at 12:07 PM, Camaleón noela...@gmail.com wrote:

 (...)

  OTOH, /etc/inittab can be restarted/reloaded by issuing telinit q, or
  at least that was what I used on another distributions, in Debian I'm
  not sure if remains the same (reviewing the manual...) hum, yep, it's
  the same :-)
 
 
  This saves me from having to repeatedly reboot the box  thanks :D
 
  For shiggles, I changed 115200 back to 9600 and used telinit q :D, same
  thing, black screen, no login prompt

 What happens if you press any key although there is no prompt?


Sonofa! I never thought to press enter ... when I did, it prompted for a
password, so I just hit enter again and was immediately prompted for a user
to login with.



 Can you test the serial connection from a client other than windows
 +putty? Just to start discarding culprits...


No need now :D see above. Thanks for the obvious tip lol.

-- 
 A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.

 Q: Why is top posting frowned upon?

Re: Serial Console Access

[Chris Brennan]

On Mon, May 23, 2011 at 1:21 PM, Chris Brennan xa...@xaerolimit.net wrote:

On Mon, May 23, 2011 at 1:14 PM, Camaleón noela...@gmail.com wrote:

 On Mon, 23 May 2011 12:17:29 -0400, Chris Brennan wrote:

  On Mon, May 23, 2011 at 12:07 PM, Camaleón noela...@gmail.com wrote:

 (...)

  OTOH, /etc/inittab can be restarted/reloaded by issuing telinit q, or
  at least that was what I used on another distributions, in Debian I'm
  not sure if remains the same (reviewing the manual...) hum, yep, it's
  the same :-)
 
 
  This saves me from having to repeatedly reboot the box  thanks :D
 
  For shiggles, I changed 115200 back to 9600 and used telinit q :D, same
  thing, black screen, no login prompt

 What happens if you press any key although there is no prompt?


 Sonofa! I never thought to press enter ... when I did, it prompted for a
 password, so I just hit enter again and was immediately prompted for a user
 to login with.



 Can you test the serial connection from a client other than windows
 +putty? Just to start discarding culprits...


 No need now :D see above. Thanks for the obvious tip lol.


How ironic ... the power blinked and that machine rebooted, when it came
back up, I saw it boot via the serial console, but it would freeze during
the boot process w/

Loading the saved-state of the serial devices...

I then manually rebooted the box a few times and it always said the same
thing, a few times though, it would print a few characters of garbage and
then hang, no physical console access or serial access. The only way I got
the machine to come back up was to unplug the serial cable from that box and
it came back up normal ... now this isn't normal or wanted behavior and it
needs to be adjusted.

BTW, I bumped it back up to 115200 (as that is the max speed of that card
and the card in my windows machine, when I do connect via serial, it does
work and quite well. I also updated my inittab from TO to use co, not sure
if that made a difference but based on what I read, as long as it was
unique, it didn't matter, co seemed more logical anyway. Now question, does
Debian treat co special? Would there be issues or should I choose another
two-letter abriviation such as se/SE/sc/SC for serial console? Only reason I
point it out is because of my trouble getting console w/ keyboard and not
serial

-- 
 A: Yes.  Q: Are you sure?  A: Because it reverses the logical flow of
conversation.  Q: Why is top posting frowned upon?

Re: Serial Console Access

[Camaleón]

On Mon, 23 May 2011 14:09:54 -0400, Chris Brennan wrote:

 How ironic ... the power blinked and that machine rebooted, when it came
 back up, I saw it boot via the serial console, but it would freeze
 during the boot process w/
 
 Loading the saved-state of the serial devices...
 
 I then manually rebooted the box a few times and it always said the same
 thing, a few times though, it would print a few characters of garbage
 and then hang, no physical console access or serial access. The only way
 I got the machine to come back up was to unplug the serial cable from
 that box and it came back up normal ... now this isn't normal or wanted
 behavior and it needs to be adjusted.

Check if you have any parameters for the serial ports saved in one of the 
configuration files where the init script look at, that is, /etc/
serial.conf or /var/lib/setserial/autoserial.conf.
 
 BTW, I bumped it back up to 115200 (as that is the max speed of that
 card and the card in my windows machine, when I do connect via serial,
 it does work and quite well. I also updated my inittab from TO to use
 co, not sure if that made a difference but based on what I read, as long
 as it was unique, it didn't matter, co seemed more logical anyway. Now
 question, does Debian treat co special? Would there be issues or should
 I choose another two-letter abriviation such as se/SE/sc/SC for serial
 console? Only reason I point it out is because of my trouble getting
 console w/ keyboard and not serial

man inittab states that the id field can be whatever string, 
containing 1-4 characters so that's up to the user. I think the pre-
selected ones T0, T1... are just a matter of identification easiness 
(Terminal 0, Terminal 1, etc...).

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.05.23.20.05...@gmail.com

Serial Console Access

[Chris Brennan]

I've embarked on the trial and error process of setting up a serial console
on my Debian 6 machine. So far, the configuration has been pretty straight
forward. As a reference point I used the following two websites

http://www.cyberciti.biz/faq/howto-setup-serial-console-on-debian-linux/
http://www.cyberciti.biz/faq/howto-setup-serial-console-on-debian-linux/
http://www.cyberciti.biz/tips/replace-windows-vista-hyperterminal-with-putty.html

http://www.cyberciti.biz/tips/replace-windows-vista-hyperterminal-with-putty.htmlIn
a nut-shell, this is what is how my Debian box is configured (for serial
console)

root@leviathan:~# setserial -g /dev/ttyS[0123]
/dev/ttyS0, UART: 16550A, Port: 0xdc00, IRQ: 16
/dev/ttyS1, UART: 16550A, Port: 0xdc00, IRQ: 16
/dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4
/dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3
root@leviathan:~# grep -e tty -e serial /etc/default/grub
GRUB_CMDLINE_LINUX='console=tty0 console=ttyS0,115200n8'
GRUB_TERMINAL=serial
GRUB_SERIAL_COMMAND=serial --speed=115200 --unit=0 --word=8 --parity=no
--stop=1
#GRUB_CMDLINE_LINUX='console=ttyS1 console=ttyS1,38400n8'
#GRUB_TERMINAL=serial
#GRUB_SERIAL_COMMAND=serial --speed=38400 --unit=0 --word=8 --parity=no
--stop=1
root@leviathan:~# grep ttyS /etc/inittab
#T0:23:respawn:/sbin/getty -L ttyS0 19200 vt100
#T1:23:respawn:/sbin/getty -L ttyS1 19200 vt100
T0:2345:respawn:/sbin/getty -L ttyS0 115200 vt100
#T0:2345:respawn:/sbin/getty -L ttyS1 38400 vt100
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3
root@leviathan:~# grep ttyS /etc/securetty
ttyS0
#ttyS1
root@leviathan:~#

Now, the one part that could be causing a problem on the server but I can't
tell is setserial's output, which is noteworthy. The motherboards COM header
is expressly disabled in the bios (as I don't have the header to physically
put in this box), but I do have a Serial Card and many working null modem
cables.

The serial card is: 01:09.0 Serial controller: NetMos Technology PCI 9835
Multi-I/O Controller (rev 01)

In windows, I've got a 2-port serial card, it is properly recognized as COM3
and COM4. When I try to open a connection to the Debian box via COM3/COM4,
all I get is a black screen and I can't tell if I am actually connected to
the serial console or not  I am curious if I missed something here ... I
tend to experiment a lot and serial access would just make things so much
easier when I am forced to reboot this box and it doesn't come back up ... a
lot easier then lugging a 60lb CRT onto my desk to plug into that computer



-- 
 A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting frowned upon?

Re: Serial Console Access

[David Parker]

 In a nut-shell, this is what is how my Debian box is configured (for serial 
 console)
   root@leviathan:~# setserial -g /dev/ttyS[0123] /dev/ttyS0, UART: 16550A, 
Port: 0xdc00, IRQ: 16 /dev/ttyS1, UART: 16550A, Port: 0xdc00, IRQ: 16 
/dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4   /dev/ttyS3, UART: unknown, 
Port: 0x02e8, IRQ: 3 root@leviathan:~# grep -e tty -e serial 
/etc/default/grub GRUB_CMDLINE_LINUX='console=tty0 console=ttyS0,115200n8' 
GRUB_TERMINAL=serial   GRUB_SERIAL_COMMAND=serial --speed=115200 --unit=0 
--word=8 --parity=no --stop=1 #GRUB_CMDLINE_LINUX='console=ttyS1 
console=ttyS1,38400n8' #GRUB_TERMINAL=serial #GRUB_SERIAL_COMMAND=serial 
--speed=38400 --unit=0 --word=8 --parity=no --stop=1   root@leviathan:~# grep 
ttyS /etc/inittab #T0:23:respawn:/sbin/getty -L ttyS0 19200 vt100 
#T1:23:respawn:/sbin/getty -L ttyS1 19200 vt100 T0:2345:respawn:/sbin/getty -L 
ttyS0 115200 vt100   #T0:2345:respawn:/sbin/getty -L ttyS1 38400 vt100 
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3 root@leviathan:~# grep ttyS 
/etc/securetty ttyS0 #ttyS1 root@leviathan:~#  
 Now, the one part that could be causing a problem on the server but I can't 
 tell is setserial's output, which is noteworthy. The motherboards COM header 
 is expressly disabled in the bios (as I don't have the header to physically 
 put in this box), but I do have a Serial Card and many working null modem 
 cables.  
 The serial card is: 01:09.0 Serial controller: NetMos Technology PCI 9835 
 Multi-I/O Controller (rev 01)
Was your onboard serial port disabled in the BIOS at the time you installed 
Debian?  If it was, then the first port on your serial card should be mapped to 
/dev/ttyS0.  If not, then udev may have picked up the onboard port as 
/dev/ttyS0 and made your card /dev/ttyS1 (or another number).

I have two Debian 4 boxes with the serial console working.  It has been quite a 
while since I set this up, but I'm pretty sure that I just added this line to 
/etc/inittab and then restarted init:

co:2345:respawn:/sbin/getty -L ttyS0 9600 vt102

I think the co may have something to do with it.  Sorry I can't be more help, 
I'm really rusty on this.  I did this 5 years ago and I've never had to do it 
again.

Hope this helps.

    - Dave

Re: No input in serial console

[Niccolò Belli]

SOLVED: https://savannah.gnu.org/bugs/index.php?32115

Il 12 gennaio 2011 20:57, Niccolò Belli darkbas...@gmail.com ha scritto:
 I'm sorry, it isn't Lenny, it's Squeeze (Debian unstable).

 Il 12 gennaio 2011 20:53, Niccolò Belli darkbas...@gmail.com ha scritto:
 Hi, I'm using an RS232 serial console with Debian Lenny. Output works
 fine (I can see the output since grub starts), but input doesn't (both
 in grub and when it prompts for login).

 Here is my /etc/default/grub:
 [...]
 GRUB_CMDLINE_LINUX_DEFAULT=quiet console=tty0 console=ttyS0,115200n8
 [...]
 GRUB_TERMINAL=console serial
 GRUB_SERIAL_COMMAND=serial --speed=115200 --unit=0 --word=8
 --parity=no --stop=1
 [...]

 and my /etc/inittab:
 [...]
 T0:23:respawn:/sbin/getty -L ttyS0 115200 vt100

 Here is how I configured minicom in the client:
    | A -    Serial Device      : /dev/ttyS0
    | B - Lockfile Location     : /var/lock
    | C -   Callin Program      :
    | D -  Callout Program      :
    | E -    Bps/Par/Bits       : 115200 8N1|
    | F - Hardware Flow Control : No
    | G - Software Flow Control : No


 Can someone help me?

 Thank you,
 Darkbasic




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTinMGJeZ803XoYExJH8E+OsXwwaSiXbiqÛv...@mail.gmail.com

No input in serial console

[Niccolò Belli]

Hi, I'm using an RS232 serial console with Debian Lenny. Output works
fine (I can see the output since grub starts), but input doesn't (both
in grub and when it prompts for login).

Here is my /etc/default/grub:
[...]
GRUB_CMDLINE_LINUX_DEFAULT=quiet console=tty0 console=ttyS0,115200n8
[...]
GRUB_TERMINAL=console serial
GRUB_SERIAL_COMMAND=serial --speed=115200 --unit=0 --word=8
--parity=no --stop=1
[...]

and my /etc/inittab:
[...]
T0:23:respawn:/sbin/getty -L ttyS0 115200 vt100

Here is how I configured minicom in the client:
| A -Serial Device  : /dev/ttyS0
| B - Lockfile Location : /var/lock
| C -   Callin Program  :
| D -  Callout Program  :
| E -Bps/Par/Bits   : 115200 8N1|
| F - Hardware Flow Control : No
| G - Software Flow Control : No


Can someone help me?

Thank you,
Darkbasic


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktim9waa5zj5u1bopf0y+8uaboi7yf+5whzw7z...@mail.gmail.com

Re: No input in serial console

[Niccolò Belli]

I'm sorry, it isn't Lenny, it's Squeeze (Debian unstable).

Il 12 gennaio 2011 20:53, Niccolò Belli darkbas...@gmail.com ha scritto:
 Hi, I'm using an RS232 serial console with Debian Lenny. Output works
 fine (I can see the output since grub starts), but input doesn't (both
 in grub and when it prompts for login).

 Here is my /etc/default/grub:
 [...]
 GRUB_CMDLINE_LINUX_DEFAULT=quiet console=tty0 console=ttyS0,115200n8
 [...]
 GRUB_TERMINAL=console serial
 GRUB_SERIAL_COMMAND=serial --speed=115200 --unit=0 --word=8
 --parity=no --stop=1
 [...]

 and my /etc/inittab:
 [...]
 T0:23:respawn:/sbin/getty -L ttyS0 115200 vt100

 Here is how I configured minicom in the client:
    | A -    Serial Device      : /dev/ttyS0
    | B - Lockfile Location     : /var/lock
    | C -   Callin Program      :
    | D -  Callout Program      :
    | E -    Bps/Par/Bits       : 115200 8N1|
    | F - Hardware Flow Control : No
    | G - Software Flow Control : No


 Can someone help me?

 Thank you,
 Darkbasic



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikup_1u5mihsgiyzy6h0qkqnqrum-vcoslg0...@mail.gmail.com

Re: debian lenny serial console garbage with a cyclades

[Angel L. Mateo]

El vie, 06-11-2009 a las 19:08 +0100, Emanoil Kotsev escribió:

 What's your kernel line on boot?
 
 I have this one
 
 kernel /vmlinuz-2.6.26.2eko2 ro console=0,115200
 
I have this:

title   Debian GNU/Linux, kernel 2.6.26-2-686
root(hd0,1)
kernel  /boot/vmlinuz-2.6.26-2-686 root=/dev/sda2 ro
rootdelay=10 console=ttyS0,115200n8 console=tty0
initrd  /boot/initrd.img-2.6.26-2-686

I have tried with your configuration, but I get the same error.


-- 
Angel L. Mateo Martínez
Sección de Telemática
Área de Tecnologías de la Información   _o)
y las Comunicaciones Aplicadas (ATICA)  / \\
http://www.um.es/atica_(___V
Tfo: 868887590
Fax: 86337


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

debian lenny serial console garbage with a cyclades

[Angel L. Mateo]

Hello,

I have a few dell poweredge servers (with debian lenny) connected
through a serial port with a cyclades console server.

I can log in into the cyclades and connect to one of this server. Then,
I can see the boot of the server and so on.

The problem I have is that during the boot, while loading drivers, when
it loads serial driver, I get a lot of garbage and console doesn't work
until login (that is, I can't see messages displays by init.d scripts).
When login is run, it works again without any problem.

The garbage I get is:

[2.982482] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ
sharingd
[2.991704] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
[2.998232] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A

Debian GNU/Linux 5.0 felis116 ttyS0

felis116 login: 

Then, I can't see anything until login is reached.

The cyclades configuration for this port is (I configured it as a
Console (Telnet) port):

s26.tty ttyS26
s26.alias felis116
s26.issue \r\n Welcome to Console Server Management Server %h port S
%p \n\r\n
s26.speed 115200
s26.datasize 8
s26.stopbits 1
s26.parity none
s26.flow none
s26.dcd 0

any idea?

-- 
Angel L. Mateo Martínez
Sección de Telemática
Área de Tecnologías de la Información   _o)
y las Comunicaciones Aplicadas (ATICA)  / \\
http://www.um.es/atica_(___V
Tfo: 868887590
Fax: 86337


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: It's possible to install Debian 5.0 using serial console?

[Emanoil Kotsev]

 
 
 thanks for this, but if i mus enter the extra parameter, i need keyboard
 and monitor attached into this machine, can i add this parameter into
 grub?

Not necessary. the device should either provide access to configuration menu
with kind of vga cable you plugin to reconfigure the bios, or if there is
no vga console it would be configured to output everything to the console

 
 if i can what program i can use to edit the debian dvd iso so i can edit
 the boot configuration
 
 many2 thanks

I would do following. 
1) find out which speed the device supports on the serial console by reading
the documentation and/or specification. 
2) Take a computer with serial port and configure it to match the spec of
the device (useally setserial on linux)
3) connect the pc with the device with a serial cable
4) run a program to talk to the serial port (usually minicom on linux)
5) configure the program (minicom) to talk to the local serial port which is
connected to the device
6) fire up the device (I mean turn it on) - and there it is in the serial
chat program (minicom) I see how the device displays the debian logo in
monochrom colors

regards





-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: It's possible to install Debian 5.0 using serial console?

[my mail]

--- On Thu, 3/12/09, Tzafrir Cohen tzaf...@cohens.org.il wrote:

From: Tzafrir Cohen tzaf...@cohens.org.il
Subject: Re: It's possible to install Debian 5.0 using serial console?
To: debian-user@lists.debian.org
Date: Thursday, March 12, 2009, 1:39 PM


-Inline Attachment Follows-

On Thu, Mar 12, 2009 at 09:04:26AM -0400, Celejar wrote:
 On Thu, 12 Mar 2009 02:31:30 -0700 (PDT)
 my mail am...@yahoo.com wrote:
 
  
  hi all
  
  I want install Debian 5.0, it possible to install Debian using serial 
  console just like another os freebsd?
  
  if possible how to do it, thanks 
 
 Never done this, YMMV, these references are old, etc.
 
 http://www.patoche.org/LTT/install/0103.html
 http://www.debian-administration.org/articles/221

 Hmm I recently ran a (PXE) serial console isntallation on an Alix
 board of mine, and had no problem whatsoever .
 
 Just make sure to pass the extra parameter:
 
   console=ttyS0,9600n8
 
 to the installer (well, I actually used there 115200 rather than 9600)


thanks for this, but if i mus enter the extra parameter, i need keyboard and 
monitor attached into this machine,
can i add this parameter into grub?

if i can what program i can use to edit the debian dvd iso so i can edit the 
boot configuration

many2 thanks








--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

It's possible to install Debian 5.0 using serial console?

[my mail]

hi all

I want install Debian 5.0, it possible to install Debian using serial console 
just like another os freebsd?

if possible how to do it, thanks 


  


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: It's possible to install Debian 5.0 using serial console?

[Celejar]

On Thu, 12 Mar 2009 02:31:30 -0700 (PDT)
my mail am...@yahoo.com wrote:

 
 hi all
 
 I want install Debian 5.0, it possible to install Debian using serial console 
 just like another os freebsd?
 
 if possible how to do it, thanks 

Never done this, YMMV, these references are old, etc.

http://www.patoche.org/LTT/install/0103.html
http://www.debian-administration.org/articles/221

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: It's possible to install Debian 5.0 using serial console?

[Tzafrir Cohen]

On Thu, Mar 12, 2009 at 09:04:26AM -0400, Celejar wrote:
 On Thu, 12 Mar 2009 02:31:30 -0700 (PDT)
 my mail am...@yahoo.com wrote:
 
  
  hi all
  
  I want install Debian 5.0, it possible to install Debian using serial 
  console just like another os freebsd?
  
  if possible how to do it, thanks 
 
 Never done this, YMMV, these references are old, etc.
 
 http://www.patoche.org/LTT/install/0103.html
 http://www.debian-administration.org/articles/221

Hmm I recently ran a (PXE) serial console isntallation on an Alix
board of mine, and had no problem whatsoever .

Just make sure to pass the extra parameter:

  console=ttyS0,9600n8

to the installer (well, I actually used there 115200 rather than 9600)

-- 
Tzafrir Cohen | tzaf...@jabber.org | VIM is
http://tzafrir.org.il || a Mutt's
tzaf...@cohens.org.il ||  best
ICQ# 16849754 || friend


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: It's possible to install Debian 5.0 using serial console?

[Emanoil Kotsev]

Tzafrir Cohen wrote:

 On Thu, Mar 12, 2009 at 09:04:26AM -0400, Celejar wrote:
 On Thu, 12 Mar 2009 02:31:30 -0700 (PDT)
 my mail am...@yahoo.com wrote:
 
  
  hi all
  
  I want install Debian 5.0, it possible to install Debian using serial
  console just like another os freebsd?
  
  if possible how to do it, thanks
 
 Never done this, YMMV, these references are old, etc.
 
 http://www.patoche.org/LTT/install/0103.html
 http://www.debian-administration.org/articles/221
 
 Hmm I recently ran a (PXE) serial console isntallation on an Alix
 board of mine, and had no problem whatsoever .
 
 Just make sure to pass the extra parameter:
 
   console=ttyS0,9600n8

the command line is for pxe - at least the one below still works for me with
grub as a kernel command line 

use console=0,BAUDRATE 

regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Grub serial console does not work

[jimmi]

Hi,

I'm using since several years the serial console to get the grub menu
from a headless PC, that I configured following the instruction of the
Remote Serial Console HOWTO [1]. I'm now replacing the machine with a
mini-itx assembled with an Intel D201GLY2 board [2]. Using the same
configuration the grub menu appears (Press any key to continue) only
on the local monitor, while the output on the serial console starts
working only when the kernel boots off.

Any idea which test may I do to understand where the problem is?

Thanks in advance.
Jimmi

[1]http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel-
grub.html
[2]http://www.intel.com/products/motherboard/d201gly2/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Grub serial console does not work

[Douglas A. Tutty]

On Wed, Jan 23, 2008 at 06:11:20AM -0800, jimmi wrote:
 Hi,
 
 I'm using since several years the serial console to get the grub menu
 from a headless PC, that I configured following the instruction of the
 Remote Serial Console HOWTO [1]. I'm now replacing the machine with a
 mini-itx assembled with an Intel D201GLY2 board [2]. Using the same
 configuration the grub menu appears (Press any key to continue) only
 on the local monitor, while the output on the serial console starts
 working only when the kernel boots off.
 
 Any idea which test may I do to understand where the problem is?

Grub isn't finding that serial port.  Perhaps the numbering has changed
at the grub level.  The kernel, on the other hand, is finding the serial
port at the same /dev/ttyS?.  I don't know how to get grub to search for
serial ports but I hope this points you in the right direction.

Doug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Grub serial console does not work

[jimmi]

On 23 Gen, 16:10, Douglas A. Tutty [EMAIL PROTECTED] wrote:
 at the grub level.  The kernel, on the other hand, is finding the serial
 port at the same /dev/ttyS?.  I don't know how to get grub to search for

Yes Doug,

the kernel option is still ttyS0 as before.

I'll look for information on how grub serial port connection works.

Thanks for your help.
Jimmi


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]