Serial console?

Serial console?

[Craig Metz]

  I went to install Ultrapenguin 1.0.9 on one of our spare Ultra Enterprise
450s. I hooked up a serial terminal, did a network boot, and the kernel came
up but everything stopped after "VFS: Mounted root filesystem (ext2)". On a
hunch, I installed a spare Creator 3D in the box, and it worked fine.

  It appears that Ultrapenguin's boot kernel built without serial console
support. Is it possible to add that to the distributed kernel, and is that
useful for installing (can the install be made to work over such a terminal,
or is it a lost cause)? If not, can this be added to the documentation as a
caveat?

									-Craig

Re: Serial console?

[djb]

> 
>   I went to install Ultrapenguin 1.0.9 on one of our spare Ultra Enterprise
> 450s. I hooked up a serial terminal, did a network boot, and the kernel came
> up but everything stopped after "VFS: Mounted root filesystem (ext2)". On a
> hunch, I installed a spare Creator 3D in the box, and it worked fine.
> 
>   It appears that Ultrapenguin's boot kernel built without serial console
> support. Is it possible to add that to the distributed kernel, and is that
> useful for installing (can the install be made to work over such a terminal,
> or is it a lost cause)? If not, can this be added to the documentation as a
> caveat?

Did you do 'boot net serial'?  You have to *tell* it you're on a serial
console and it should work fine...


--Donnie

--
 Donnie Barnes    http://www.redhat.com/~djb    djb@redhat.com   "Bah."
   Challenge Diversity.  Ignore People.  Live Life.  Use Linux.  879.
My Dad used to say I have deceptive quickness.  I'm slower than I look.

Re: Serial console?

[David S. Miller]

add "serial" to the end of the "boot net" command line, works fine
here on all my Ultras

Later,
David S. Miller
davem@dm.cobaltmicro.com

Re: Serial console?

[Jakub Jelinek]

> Did you do 'boot net serial'?  You have to *tell* it you're on a serial
> console and it should work fine...

That should not be necessary. Our install just checks the console, whether
it is serial or not.

Cheers,
    Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
Ultralinux - first 64bit OS to take full power of the UltraSparc
Linux version 2.1.106 on a sparc64 machine (498.80 BogoMips).
___________________________________________________________________

Re: Serial console?

[Marc Duponcheel]

> > Did you do 'boot net serial'?  You have to *tell* it you're on a serial
> > console and it should work fine...
> 
> That should not be necessary. Our install just checks the console, whether
> it is serial or not.

Funny, I could only make it work with serial added [but then, I did not
try again without 'serial' after it was over ;-)]

	Great Job, this UltraPenguin! Congratulations.

PS: I could see some complaints about 'cua' being depreciated in favour of
'ttyS' on first bootup. I'll check what this is about.

 Greetings,

---                  Cisco Systems                  ---
Marc Duponcheel mduponch@cisco.com tel: +32 2 778 42 40
CATS Team TAC Brussels  ---*---  pager: +32 72 53 30 01

Re: Serial console?

[Jakub Jelinek]

> 
> Hi,
> 
> Marc Duponcheel wrote:
> > PS: I could see some complaints about 'cua' being depreciated in favour of
> > 'ttyS' on first bootup. I'll check what this is about.
> 
> What it is: an attempt to get rid of the confusion caused by having pairs
> of devices for one physical serial port - make all users go away, then
> remove cua* in 2.3.
> 
> Why you are seeing this: no idea, some program is accessing cua*, but I
> have no idea which one...

setconsole program is broken, if it detects serial console, it ln -sf
/dev/console to /dev/cuaX. That is wrong with 2.1 kernels, where
/dev/console should be always character 5,1. Install program runs
setconsole, if it detects a serial console during install. So, either do you
install from framebuffer, or after install 
rm -f /dev/console
mknod /dev/console c 5 1

I promise to fix this soon, but as I mentioned in the last mail, we have to
get consoles working again with 2.1.107 first.

Cheers,
    Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
Ultralinux - first 64bit OS to take full power of the UltraSparc
Linux version 2.1.106 on a sparc64 machine (498.80 BogoMips).
___________________________________________________________________

Re: Serial console?

[Ward Deng]

Yes. No need here. Both AXi and AX boards work the same way with 1.0.9 and
2.1.99 kernel.

--ward

Ward Deng, Ph.D                   |  Kachina Technologies, Inc.
Vice President and COO            |  4708 Douglas MacArthur Road NE,
Tel: 505-888-5934                 |  Albuquerque NM 87110
Fax: 505-888-5902                 |  info@KachinaTech.COM
Email: Ward.Deng@KachinaTech.COM  |  URL: http://www.KachinaTech.COM

On Fri, 26 Jun 1998, Jakub Jelinek wrote:

> > Did you do 'boot net serial'?  You have to *tell* it you're on a serial
> > console and it should work fine...
> 
> That should not be necessary. Our install just checks the console, whether
> it is serial or not.
> 
> Cheers,
>     Jakub
> ___________________________________________________________________
> Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
> Administrator of SunSITE Czech Republic, MFF, Charles University
> ___________________________________________________________________
> Ultralinux - first 64bit OS to take full power of the UltraSparc
> Linux version 2.1.106 on a sparc64 machine (498.80 BogoMips).
> ___________________________________________________________________
> 

Re: Serial Console!!

[Jim Dennis]

Apparently "Green" <greeen@iii.org.tw>  wrote:

> Hi all,
 
> I want to login to my MIPS box through serial port.
> I execute 'make menuconfig' and select the 'serial console'.
> But I can't see the login prompt in my window(I use netterm).
 
> May I ask how serial console work?
> Or I forget something?
 
> P.S I skip /sbin/init program.

 In order for you to have full serial console port you 
 must do more than simply enable the option in your kernel.

 Your BIOS/firmware should have serial console support of
 its own (most PCs don't, most other systems, even most 
 PowerPC based Macs and workstations do, in the form of 
 OpenFirmware --- formerly known as Sun's FCODE).  

 Your MIPS box might have a firmware with serial console
 support, or it might not.

 That should allow you to access any pre-boot configuration
 options or diagnostics (including providing some mechanism
 to reset the NVRAM and to set the boot device or sequence)

 Your bootloader would have to support serial console
 to allow you to select which kernel you want to load
 and/or to pass kernel command line options and set
 initial environment variable/value pairs (a feature
 that seems unique to Linux).

 Of course, the Linux kernel support must be enabled,
 though that *only* applies to whether the kernel messages
 are copied to that device.  If you would see it from 
 dmesg, then it won't get copied to the console.

 To enable logins on a serial device you must spawn 
 some form of getty process (normally done by init).  That
 will listen for connections (normallly by taking login names)
 and exec() your login program (usually with the login name passed
 on its argument list).

 Since you specify that you're not running init, it's obvious
 why you can't "login."

 So, please tell me that you didn't actually think that 
 logins and shells were handled directly by UNIX and Linux
 kernels!
 
 
--
Jim Dennis               
Software Analyst		
Axis Personal Trainers			http://www.axispt.com

Serial console??

[Nicholas Lee]

I'm trying to setup a login getty session via the console with Xen 3.0
so I can access it via the v20z SP console.

I've managed get bios, grub and linux boot console access, but getty
refuses to start.


I'm wondering if anyone has any pointers.

I note this particular error in dmesg:
"WARNING: Failed to register Xen virtual console driver as 'ttyS0'"

===

nic@wuwei:~$ grep xen /boot/grub/menu.lst
  kernel /xen-3.0-devel.gz dom0_mem=262144 com1=38400,8n1
  module /vmlinuz-2.6.12-xen0 root=/dev/sda3 ro console=ttyS0,38400
console=tty0 hda=none hdb=none


from dmesg:
eth1: dma_rwctrl[769f0000]
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
WARNING: Failed to register Xen virtual console driver as 'ttyS0'
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx

nic@wuwei:~$ tail -15 /var/log/mgetty/mg_ttyS0.log
11/18 14:14:30 yS0  mg_init_device failed, exiting: Input/output error
11/18 14:14:30 yS0  cannot get terminal line dev=ttyS0, exiting:
Input/output error
--
11/18 14:14:30 yS0  tio_get_rs232_lines: TIOCMGET failed: Input/output error
11/18 14:14:30 yS0  TIOCMBIC failed: Input/output error
11/18 14:14:30 yS0  cannot turn off soft carrier: Input/output error
11/18 14:14:30 yS0  tcgetattr failed: Input/output error
11/18 14:14:30 yS0  cannot get TIO: Input/output error
11/18 14:14:30 yS0  tio_get_rs232_lines: TIOCMGET failed: Input/output error
11/18 14:14:30 yS0  TIOCMBIC failed: Input/output error
11/18 14:14:30 yS0  cannot turn off soft carrier: Input/output error
11/18 14:14:30 yS0  tcgetattr failed: Input/output error
11/18 14:14:30 yS0  cannot get TIO: Input/output error
11/18 14:14:30 yS0  mg_init_device failed, exiting: Input/output error
11/18 14:14:30 yS0  cannot get terminal line dev=ttyS0, exiting:
Input/output error

nic@wuwei:~$ grep ttyS0 /etc/inittab
7:12345:respawn:/sbin/mgetty -x1 -s 38400 ttyS0



--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C