ltib
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] linux console is not coming up

From: utkarsh rawat
Subject: Re: [Ltib] linux console is not coming up
Date: Mon, 30 Sep 2013 10:09:22 +0530
>ttyS1 is an odd tty for the console.  Are you sure you are connected
>to ttyS1? Are you sure ttyS1 is brought out to the external connector,
>if there one?

 Is this question is after seeing this line
console handover: boot [udbg0] -> real [ttyS1]

Well before making any changes I am getting login prompt easily where i can type user  login name(root) & password(root). Then command prompt is available & I can play with console. But when I made changes from

In /etc/intab it was
::respawn:/sbin/getty -L ttS0 115200 VT100  //orginal setting
I changed to
::respawn:-/bin/sh  //new setting
command prompt is not visible it get stuck here
console handover: boot [udbg0] -> real [ttyS1]

Is there any command where I can show for which tty it is connected




My MPC8xxx uses ttyS0 and I am pretty it's external DB9 is not
connected and jumpered to an internal header (by default).



On Sat, Sep 28, 2013 at 8:28 PM, Mike Goins <address@hidden> wrote:
On Sat, Sep 28, 2013 at 8:05 AM, utkarsh rawat <address@hidden> wrote:
> Hi Stuart
>
>>This should have worked.  What is does is to set the following in
>>/etc/inittab
>
>># see busybox-1.00rc2/examples/inittab for more examples
>>::sysinit:/etc/rc.d/rcS
>>::respawn:-/bin/sh
>>::ctrlaltdel:/sbin/reboot
>>::shutdown:/etc/rc.d/rcS stop
>>::restart:/sbin/init
>
> In /etc/intab it was
> ::respawn:/sbin/getty -L ttS0 115200 VT100
> I changed to
> ::respawn:-/bin/sh
> and load file system(rootfs.ext2.gz.uboot). But still console get stuck
> .Below I have put the log
>
> ## Booting image at ffc00000 ...
>    Image Name:   Linux-2.6.23
>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>    Data Size:    2303803 Bytes =  2.2 MB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
> ## Loading RAMDisk Image at 01000000 ...
>    Image Name:
>    Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
>    Data Size:    4486554 Bytes =  4.3 MB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Booting using the fdt at 0xff900000
>    Loading Ramdisk to 0fa45000, end 0fe8c59a ... OK
>    Loading Device Tree to 007fa000, end 007fcfff ... OK
> Using MPC86xx HPCN machine description
> Total memory = 1024MB; using 2048kB for hash table (at cf800000)
> Linux version 2.6.23 (address@hidden) (gcc version 4.1.2 (Sourcery G++ Lite
> 4.1-78))
> #1 SMP Thu Jan 17 11:10:22 CST 2008
> Found initrd at 0xcfa45000:0xcfe8c59a
> console [udbg0] enabled
> setup_arch: bootmem
> mpc86xx_hpcn_setup_arch()
> Found FSL PCI host bridge at 0x00000000f8008000.Firmware bus number: 0->2
> Found FSL PCI host bridge at 0x00000000f8009000.Firmware bus number: 0->0
> MPC86xx HPCN board from Freescale Semiconductor
> arch: exit
> Zone PFN ranges:
>   DMA             0 ->   196608
>   Normal     196608 ->   196608
>   HighMem    196608 ->   262144
> Movable zone start PFN for each node
> early_node_map[1] active PFN ranges
>     0:        0 ->   262144
> Built 1 zonelists in Zone order.  Total pages: 260096
> Kernel command line: root=/dev/ram rw console=ttyS1,115200
> mpic: Setting up MPIC " MPIC     " version 1.2 at f8040000, max 2 CPUs
> mpic: ISU size: 88, shift: 7, mask: 7f
> mpic: Initializing for 88 sources
> i8259 legacy interrupt controller initialized
> PID hash table entries: 4096 (order: 12, 16384 bytes)
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> Memory: 1027024k/1048576k available (4500k kernel code, 282828k reserved,
> 152k d
> ata, 186k bss, 176k init)
> Mount-cache hash table entries: 512
> mpic: requesting IPIs ...
> Processor 1 found.
> Synchronizing timebase
> Got ack
> score 299, offset 1000
> score 299, offset 500
> score 299, offset 250
> score 299, offset 125
> score 299, offset 62
> score 299, offset 31
> score -299, offset 15
> score 299, offset 23
> score 299, offset 19
> score -299, offset 17
> score 295, offset 18
> score -299, offset 17
> Min 17 (score -299), Max 18 (score 267)
> Final offset: 18 (293/300)
> Brought up 2 CPUs
> NET: Registered protocol family 16
>
> PCI: Probing PCI hardware
> PCI: 0000:00:00.0: class b20 doesn't match header type 01. Ignoring class.
> PCI: Transparent bridge - 0000:00:00.0
> PCI: Transparent bridge - 0000:01:00.0
> PCI: 0001:03:00.0: class b20 doesn't match header type 01. Ignoring class.
> PCI: Transparent bridge - 0001:03:00.0
> Generic PHY: Registered new driver
> SCSI subsystem initialized
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> NET: Registered protocol family 2
> IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
> TCP established hash table entries: 131072 (order: 8, 1572864 bytes)
> TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
> TCP: Hash tables configured (established 131072 bind 65536)
> TCP reno registered
> checking if image is initramfs...it isn't (no cpio magic); looks like an
> initrd
> Freeing initrd memory: 4381k freed
> Setting up RapidIO peer-to-peer network /address@hidden/address@hidden
> RIO: Of-device full name /address@hidden/address@hidden
> RIO: LAW start 0x00000000c0000000, size 0x0000000020000000.
> RIO: Regs start 0xf80c0000 size 0x00020000
> RIO: Phy type: serial
> RIO: Hardware port width: 4
> RIO: Training connection status: Four-lane
> RIO fsl_rio_setup: Port is not ready. Try to restart connection...
> RIO fsl_rio_setup: Port restart failed.
> of-rio: probe of f80c0000.rapidio failed with error -67
> of-fsl-dma f8021300.dma: Probe the Freescale DMA driver for fsl,mpc8540-dma
> cont
> roller at 0xf8021300...
> of-fsl-dma-channel f8021100.dma-channe: #0 (fsl,mpc8540-dma-channel), irq 20
> of-fsl-dma-channel f8021180.dma-channe: #1 (fsl,mpc8540-dma-channel), irq 21
> of-fsl-dma-channel f8021200.dma-channe: #2 (fsl,mpc8540-dma-channel), irq 22
> of-fsl-dma-channel f8021280.dma-channe: #3 (fsl,mpc8540-dma-channel), irq 23
> audit: initializing netlink socket (disabled)
> audit(0.587:1): initialized
> highmem bounce pool size: 64 pages
> Installing knfsd (copyright (C) 1996 address@hidden).
> fuse init (API version 7.8)
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> Generic RTC Driver v1.07
> Macintosh non-volatile memory driver v1.1
> Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing enabled
> serial8250.0: ttyS0 at MMIO 0xf8004500 (irq = 42) is a 16550A
> serial8250.0: ttyS1 at MMIO 0xf8004600 (irq = 28) is a 16550A
> console handover: boot [udbg0] -> real [ttyS1]  //GET STUCK HERE AFTER THAT
> LOGIN SHOULD COME


ttyS1 is an odd tty for the console.  Are you sure you are connected
to ttyS1? Are you sure ttyS1 is brought out to the external connector,
if there one?

My MPC8xxx uses ttyS0 and I am pretty it's external DB9 is not
connected and jumpered to an internal header (by default).



>
>
>
> On Sat, Sep 28, 2013 at 3:22 PM, Stuart Hughes <address@hidden> wrote:
>>
>> Hi Utkash,
>>
>> On 27/09/13 10:59, utkarsh rawat wrote:
>> > Hi All
>> >
>> > I have eval board MPC8641 where my linux kernel is coming up properly .I
>> > want to disable the login  & password (login: root & password :root) i.e
>> > looking for autologin
>> > For that I went to Target System Configuration -->option->bootup with
>> > tty & login option I disabled
>> >
>> > After that my console itself is not coming . After some study I came to
>>
>> This should have worked.  What is does is to set the following in
>> /etc/inittab
>>
>> # see busybox-1.00rc2/examples/inittab for more examples
>> ::sysinit:/etc/rc.d/rcS
>> ::respawn:-/bin/sh
>> ::ctrlaltdel:/sbin/reboot
>> ::shutdown:/etc/rc.d/rcS stop
>> ::restart:/sbin/init
>>
>> The important thing is the line: ::respawn:-/bin/sh
>> so provided you have /bin/sh on your system, the startup should end up
>> at the shell prompt rather than the login prompt.
>>
>> > know its better not to disabled the root login & password . So I want to
>> > try as user login where i can look for autologin .
>> > I ltib also I have seen there is not auto login option .
>> > Kindly reply
>> > Thank you
>> >
>>
>> Do you mean log in as a different user? if so there is another user in
>> the default LTIB build: username: user, password: password (IIRC).
>>
>> There is no mechanism in LTIB to log you in automatically, you'd have to
>> devise something (normally on the client end with something like Expect).
>>
>> > --
>> > Utkarsh Rawat
>> >
>> >
>> > _______________________________________________
>> > LTIB home page: http://ltib.org
>> >
>> > Ltib mailing list
>> > address@hidden
>> > https://lists.nongnu.org/mailman/listinfo/ltib
>> >
>
>
>
>
> --
> Utkarsh Rawat
>
> _______________________________________________
> LTIB home page: http://ltib.org
>
> Ltib mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/ltib
>

_______________________________________________
LTIB home page: http://ltib.org

Ltib mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/ltib



--
Utkarsh Rawat
reply via email to
[Prev in Thread] Current Thread [Next in Thread]