help with inittab

help with inittab

[Chris Dumoulin]

I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK 
4.0. Currently, I seem to be able to boot without errors, but after the 
root filesystem is mounted, things just stop.

I'm guessing that my problems are related to the setup of the RFS, and 
more specifically, my inittab file. Here is the output I get at boot time:
Linux version 2.6.15 (cdumoulin@localhost.localdomain) (gcc version 
4.0.0 (DENX ELDK 4.0 4.0.0)) #167 PREEMPT Thu Jun 8 6Built 1 zonelists
Kernel command line: console=ttyS0,57600 ip=off
PID hash table entries: 512 (order: 9, 8192 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 62120k available (968k kernel code, 272k data, 76k init, 0k highmem)
Mount-cache hash table entries: 512
checking if image is initramfs...it isn't (no cpio magic); looks like an 
initrd
Freeing initrd memory: 1404k freed
Linux NoNET1.0 for Linux 2.6
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60 
sec (nowayout= 0)
ipmi message handler version 38.0
ipmi device interface
IPMI Watchdog: driver initialized
i8042.c: No controller found.
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 24) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
mice: PS/2 mouse device common for all mice
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).

And here is my initttab file:
::sysinit:/etc/rc.sh
::askfirst:/bin/sh
::ctrlaltdel:/sbin/reboot
::shutdown:/sbin/swapoff -a
::shutdown:/bin/umount -a -r
::restart:/sbin/init

Any ideas would be appreciated.

Cheers,
Chris Dumoulin
-- 
*--Christopher Dumoulin--*
Software Team Leader

<http://ics-ltd.com/>
<http://ics-ltd.com/>

Interactive Circuits and Systems Ltd.
5430 Canotek Road
Ottawa, ON
K1J 9G2
(613)749-9241
1-800-267-9794 (USA only)

------------------------------------------------------------------------
This e-mail is private and confidential and is for the addressee only. 
If misdirected, please notify us by telephone and confirm that it has 
been deleted from your system and any hard copies destroyed. You are 
strictly prohibited from using, printing, distributing or disseminating 
it or any information contained in it save to the intended recipient.

Re: help with inittab

[Steve Iribarne (GMail)]

On 6/8/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
> I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK
> 4.0. Currently, I seem to be able to boot without errors, but after the
> root filesystem is mounted, things just stop.
>
> I'm guessing that my problems are related to the setup of the RFS, and
> more specifically, my inittab file. Here is the output I get at boot time:
> Linux version 2.6.15 (cdumoulin@localhost.localdomain) (gcc version
> 4.0.0 (DENX ELDK 4.0 4.0.0)) #167 PREEMPT Thu Jun 8 6Built 1 zonelists
> Kernel command line: console=ttyS0,57600 ip=off
> PID hash table entries: 512 (order: 9, 8192 bytes)
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Memory: 62120k available (968k kernel code, 272k data, 76k init, 0k highmem)
> Mount-cache hash table entries: 512
> checking if image is initramfs...it isn't (no cpio magic); looks like an
> initrd
> Freeing initrd memory: 1404k freed
> Linux NoNET1.0 for Linux 2.6
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60
> sec (nowayout= 0)
> ipmi message handler version 38.0
> ipmi device interface
> IPMI Watchdog: driver initialized
> i8042.c: No controller found.
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
> serial8250: ttyS0 at MMIO 0x0 (irq = 24) is a 16550A
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> loop: loaded (max 8 devices)
> mice: PS/2 mouse device common for all mice
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (ext2 filesystem).
>
> And here is my initttab file:
> ::sysinit:/etc/rc.sh
> ::askfirst:/bin/sh
> ::ctrlaltdel:/sbin/reboot
> ::shutdown:/sbin/swapoff -a
> ::shutdown:/bin/umount -a -r
> ::restart:/sbin/init
>

Doesn't seem like you are respawning any login stuff?  Where are your
tty's?  Change the askfirst to /bin/sh and you should get a shell at
the start assuming you have /bin/sh.


> Any ideas would be appreciated.
>
> Cheers,
> Chris Dumoulin
> --
> *--Christopher Dumoulin--*
> Software Team Leader
>
> <http://ics-ltd.com/>
> <http://ics-ltd.com/>
>
> Interactive Circuits and Systems Ltd.
> 5430 Canotek Road
> Ottawa, ON
> K1J 9G2
> (613)749-9241
> 1-800-267-9794 (USA only)
>
> ------------------------------------------------------------------------
> This e-mail is private and confidential and is for the addressee only.
> If misdirected, please notify us by telephone and confirm that it has
> been deleted from your system and any hard copies destroyed. You are
> strictly prohibited from using, printing, distributing or disseminating
> it or any information contained in it save to the intended recipient.
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>

Re: help with inittab

[Wolfgang Denk]

In message <44888B92.40409@ics-ltd.com> you wrote:
> I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK 
> 4.0. Currently, I seem to be able to boot without errors, but after the 
> root filesystem is mounted, things just stop.

And  what's  your  console  device?  Are  you  passing  any  console=
arguments  on  the  command  line?  Is the corresponding device entry
present in the /dev/directory?

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Sometimes a feeling is all we humans have to go on.
	-- Kirk, "A Taste of Armageddon", stardate 3193.9

Re: help with inittab

[Chris Dumoulin]

I've now determined that my kernel seems to stop in the following line 
of code, in the function init(void * unused), in init/main.c:
run_init_process("/sbin/init");
I've determined that it stops at this call by stepping through the code 
with a BDI2000.

My boot arguments are:
console=ttyS0,57600n8 ip=off root=/dev/ram0 rw

My current inittab is:
::sysinit:/etc/rc.sh
::ctrlaltdel:/sbin/reboot
::shutdown:/sbin/swapoff -a
::shutdown:/bin/umount -a -r
::restart:/sbin/init
::respawn:/bin/sh

I've tried adding an "echo" command to the /etc/rc.sh script that is 
called, but I don't see any output. I've also trying changing the 
::sysinit line in inittab to point to some non-existent script, to see 
if I'll get some error message, but I still see nothing. Is it possible 
that /sbin/init is dying before it gets to the point of reading inittab?
Any ideas?

Regards,
Chris Dumoulin


Wolfgang Denk wrote:

>In message <44888B92.40409@ics-ltd.com> you wrote:
>  
>
>>I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK 
>>4.0. Currently, I seem to be able to boot without errors, but after the 
>>root filesystem is mounted, things just stop.
>>    
>>
>
>And  what's  your  console  device?  Are  you  passing  any  console=
>arguments  on  the  command  line?  Is the corresponding device entry
>present in the /dev/directory?
>
>Best regards,
>
>Wolfgang Denk
>
>  
>

-- 
*--Christopher Dumoulin--*
Software Team Leader

<http://ics-ltd.com/>
<http://ics-ltd.com/>

Interactive Circuits and Systems Ltd.
5430 Canotek Road
Ottawa, ON
K1J 9G2
(613)749-9241
1-800-267-9794 (USA only)

------------------------------------------------------------------------
This e-mail is private and confidential and is for the addressee only. 
If misdirected, please notify us by telephone and confirm that it has 
been deleted from your system and any hard copies destroyed. You are 
strictly prohibited from using, printing, distributing or disseminating 
it or any information contained in it save to the intended recipient.

Re: help with inittab

[Steve Iribarne (GMail)]

On 6/9/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
> I've now determined that my kernel seems to stop in the following line
> of code, in the function init(void * unused), in init/main.c:
> run_init_process("/sbin/init");

Who's init are  you using??

Are you using Busyboxes or sysinit from GNU?


> I've determined that it stops at this call by stepping through the code
> with a BDI2000.
>
> My boot arguments are:
> console=ttyS0,57600n8 ip=off root=/dev/ram0 rw
>
> My current inittab is:
> ::sysinit:/etc/rc.sh
> ::ctrlaltdel:/sbin/reboot
> ::shutdown:/sbin/swapoff -a
> ::shutdown:/bin/umount -a -r
> ::restart:/sbin/init
> ::respawn:/bin/sh
>
> I've tried adding an "echo" command to the /etc/rc.sh script that is
> called, but I don't see any output. I've also trying changing the
> ::sysinit line in inittab to point to some non-existent script, to see
> if I'll get some error message, but I still see nothing. Is it possible
> that /sbin/init is dying before it gets to the point of reading inittab?
> Any ideas?
>
> Regards,
> Chris Dumoulin
>
>
> Wolfgang Denk wrote:
>
> >In message <44888B92.40409@ics-ltd.com> you wrote:
> >
> >
> >>I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK
> >>4.0. Currently, I seem to be able to boot without errors, but after the
> >>root filesystem is mounted, things just stop.
> >>
> >>
> >
> >And  what's  your  console  device?  Are  you  passing  any  console=
> >arguments  on  the  command  line?  Is the corresponding device entry
> >present in the /dev/directory?
> >
> >Best regards,
> >
> >Wolfgang Denk
> >
> >
> >
>
> --
> *--Christopher Dumoulin--*
> Software Team Leader
>
> <http://ics-ltd.com/>
> <http://ics-ltd.com/>
>
> Interactive Circuits and Systems Ltd.
> 5430 Canotek Road
> Ottawa, ON
> K1J 9G2
> (613)749-9241
> 1-800-267-9794 (USA only)
>
> ------------------------------------------------------------------------
> This e-mail is private and confidential and is for the addressee only.
> If misdirected, please notify us by telephone and confirm that it has
> been deleted from your system and any hard copies destroyed. You are
> strictly prohibited from using, printing, distributing or disseminating
> it or any information contained in it save to the intended recipient.
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>

Re: help with inittab

[Chris Dumoulin]

The init is from Busybox. Since I'm getting output from my serial port 
during the kernel boot process, I think it's safe to say that my 
/dev/ttyS0 is properly configured. Besides passing the kernel argument 
console=ttyS0,57600, is there anything else I need to do to properly 
configure the console? I've looked through my kernel configuration to 
make sure that any serial device or console related stuff was enabled 
and configured.

I'm feeling pretty stumped.

- Chris

Steve Iribarne (GMail) wrote:

> On 6/9/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
>
>> I've now determined that my kernel seems to stop in the following line
>> of code, in the function init(void * unused), in init/main.c:
>> run_init_process("/sbin/init");
>
>
> Who's init are  you using??
>
> Are you using Busyboxes or sysinit from GNU?
>
>
>> I've determined that it stops at this call by stepping through the code
>> with a BDI2000.
>>
>> My boot arguments are:
>> console=ttyS0,57600n8 ip=off root=/dev/ram0 rw
>>
>> My current inittab is:
>> ::sysinit:/etc/rc.sh
>> ::ctrlaltdel:/sbin/reboot
>> ::shutdown:/sbin/swapoff -a
>> ::shutdown:/bin/umount -a -r
>> ::restart:/sbin/init
>> ::respawn:/bin/sh
>>
>> I've tried adding an "echo" command to the /etc/rc.sh script that is
>> called, but I don't see any output. I've also trying changing the
>> ::sysinit line in inittab to point to some non-existent script, to see
>> if I'll get some error message, but I still see nothing. Is it possible
>> that /sbin/init is dying before it gets to the point of reading inittab?
>> Any ideas?
>>
>> Regards,
>> Chris Dumoulin
>>
>>
>> Wolfgang Denk wrote:
>>
>> >In message <44888B92.40409@ics-ltd.com> you wrote:
>> >
>> >
>> >>I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK
>> >>4.0. Currently, I seem to be able to boot without errors, but after 
>> the
>> >>root filesystem is mounted, things just stop.
>> >>
>> >>
>> >
>> >And  what's  your  console  device?  Are  you  passing  any  console=
>> >arguments  on  the  command  line?  Is the corresponding device entry
>> >present in the /dev/directory?
>> >
>> >Best regards,
>> >
>> >Wolfgang Denk
>> >
>> >
>> >
>>
>> -- 
>> *--Christopher Dumoulin--*
>> Software Team Leader
>>
>> <http://ics-ltd.com/>
>> <http://ics-ltd.com/>
>>
>> Interactive Circuits and Systems Ltd.
>> 5430 Canotek Road
>> Ottawa, ON
>> K1J 9G2
>> (613)749-9241
>> 1-800-267-9794 (USA only)
>>
>> ------------------------------------------------------------------------
>> This e-mail is private and confidential and is for the addressee only.
>> If misdirected, please notify us by telephone and confirm that it has
>> been deleted from your system and any hard copies destroyed. You are
>> strictly prohibited from using, printing, distributing or disseminating
>> it or any information contained in it save to the intended recipient.
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>


-- 
*--Christopher Dumoulin--*
Software Team Leader

<http://ics-ltd.com/>
<http://ics-ltd.com/>

Interactive Circuits and Systems Ltd.
5430 Canotek Road
Ottawa, ON
K1J 9G2
(613)749-9241
1-800-267-9794 (USA only)

------------------------------------------------------------------------
This e-mail is private and confidential and is for the addressee only. 
If misdirected, please notify us by telephone and confirm that it has 
been deleted from your system and any hard copies destroyed. You are 
strictly prohibited from using, printing, distributing or disseminating 
it or any information contained in it save to the intended recipient.

RE: help with inittab

[Scott Coulter]

Chris,

Does your serial output stop after "Freeing unused kernel memory..."

If it does, you may have an interrupt problem with the UART.  I had to
track down that very problem the other day.  As a test, even if my UART
interrupt was purposely misconfigured, I still saw all of the output up
to and including "Freeing unused kernel memory..."

Scott




___________________________________________________________________

  Scott N. Coulter
  Senior Software Engineer
 =20
  Cyclone Microsystems         =20
  370 James Street              Phone:  203.786.5536 ext. 118
  New Haven, CT 06513-3051      Email:  scott.coulter@cyclone.com
  U.S.A.                        Web:    http://www.cyclone.com
___________________________________________________________________

-----Original Message-----
From: linuxppc-embedded-bounces+scott.coulter=3Dcyclone.com@ozlabs.org
[mailto:linuxppc-embedded-bounces+scott.coulter=3Dcyclone.com@ozlabs.org]=

On Behalf Of Chris Dumoulin
Sent: Friday, June 09, 2006 3:15 PM
To: Steve Iribarne (GMail)
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: help with inittab

The init is from Busybox. Since I'm getting output from my serial port=20
during the kernel boot process, I think it's safe to say that my=20
/dev/ttyS0 is properly configured. Besides passing the kernel argument=20
console=3DttyS0,57600, is there anything else I need to do to properly=20
configure the console? I've looked through my kernel configuration to=20
make sure that any serial device or console related stuff was enabled=20
and configured.

I'm feeling pretty stumped.

- Chris

Steve Iribarne (GMail) wrote:

> On 6/9/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
>
>> I've now determined that my kernel seems to stop in the following
line
>> of code, in the function init(void * unused), in init/main.c:
>> run_init_process("/sbin/init");
>
>
> Who's init are  you using??
>
> Are you using Busyboxes or sysinit from GNU?
>
>
>> I've determined that it stops at this call by stepping through the
code
>> with a BDI2000.
>>
>> My boot arguments are:
>> console=3DttyS0,57600n8 ip=3Doff root=3D/dev/ram0 rw
>>
>> My current inittab is:
>> ::sysinit:/etc/rc.sh
>> ::ctrlaltdel:/sbin/reboot
>> ::shutdown:/sbin/swapoff -a
>> ::shutdown:/bin/umount -a -r
>> ::restart:/sbin/init
>> ::respawn:/bin/sh
>>
>> I've tried adding an "echo" command to the /etc/rc.sh script that is
>> called, but I don't see any output. I've also trying changing the
>> ::sysinit line in inittab to point to some non-existent script, to
see
>> if I'll get some error message, but I still see nothing. Is it
possible
>> that /sbin/init is dying before it gets to the point of reading
inittab?
>> Any ideas?
>>
>> Regards,
>> Chris Dumoulin
>>
>>
>> Wolfgang Denk wrote:
>>
>> >In message <44888B92.40409@ics-ltd.com> you wrote:
>> >
>> >
>> >>I am using the linux kernel 2.6.15 and initrd ramdisk image from
ELDK
>> >>4.0. Currently, I seem to be able to boot without errors, but after

>> the
>> >>root filesystem is mounted, things just stop.
>> >>
>> >>
>> >
>> >And  what's  your  console  device?  Are  you  passing  any
console=3D
>> >arguments  on  the  command  line?  Is the corresponding device
entry
>> >present in the /dev/directory?
>> >
>> >Best regards,
>> >
>> >Wolfgang Denk
>> >
>> >
>> >
>>
>> --=20
>> *--Christopher Dumoulin--*
>> Software Team Leader
>>
>> <http://ics-ltd.com/>
>> <http://ics-ltd.com/>
>>
>> Interactive Circuits and Systems Ltd.
>> 5430 Canotek Road
>> Ottawa, ON
>> K1J 9G2
>> (613)749-9241
>> 1-800-267-9794 (USA only)
>>
>>
------------------------------------------------------------------------
>> This e-mail is private and confidential and is for the addressee
only.
>> If misdirected, please notify us by telephone and confirm that it has
>> been deleted from your system and any hard copies destroyed. You are
>> strictly prohibited from using, printing, distributing or
disseminating
>> it or any information contained in it save to the intended recipient.
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>


--=20
*--Christopher Dumoulin--*
Software Team Leader

<http://ics-ltd.com/>
<http://ics-ltd.com/>

Interactive Circuits and Systems Ltd.
5430 Canotek Road
Ottawa, ON
K1J 9G2
(613)749-9241
1-800-267-9794 (USA only)

------------------------------------------------------------------------
This e-mail is private and confidential and is for the addressee only.=20
If misdirected, please notify us by telephone and confirm that it has=20
been deleted from your system and any hard copies destroyed. You are=20
strictly prohibited from using, printing, distributing or disseminating=20
it or any information contained in it save to the intended recipient.
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Re: help with inittab

[Chris Dumoulin]

Hi Scott,
That is where my output stops. What was the cause of your interrupt 
problem? Were you able to fix it?

- Chris

Scott Coulter wrote:

>Chris,
>
>Does your serial output stop after "Freeing unused kernel memory..."
>
>If it does, you may have an interrupt problem with the UART.  I had to
>track down that very problem the other day.  As a test, even if my UART
>interrupt was purposely misconfigured, I still saw all of the output up
>to and including "Freeing unused kernel memory..."
>
>Scott
>
>
>
>
>___________________________________________________________________
>
>  Scott N. Coulter
>  Senior Software Engineer
>  
>  Cyclone Microsystems          
>  370 James Street              Phone:  203.786.5536 ext. 118
>  New Haven, CT 06513-3051      Email:  scott.coulter@cyclone.com
>  U.S.A.                        Web:    http://www.cyclone.com
>___________________________________________________________________
>
>-----Original Message-----
>From: linuxppc-embedded-bounces+scott.coulter=cyclone.com@ozlabs.org
>[mailto:linuxppc-embedded-bounces+scott.coulter=cyclone.com@ozlabs.org]
>On Behalf Of Chris Dumoulin
>Sent: Friday, June 09, 2006 3:15 PM
>To: Steve Iribarne (GMail)
>Cc: linuxppc-embedded@ozlabs.org
>Subject: Re: help with inittab
>
>The init is from Busybox. Since I'm getting output from my serial port 
>during the kernel boot process, I think it's safe to say that my 
>/dev/ttyS0 is properly configured. Besides passing the kernel argument 
>console=ttyS0,57600, is there anything else I need to do to properly 
>configure the console? I've looked through my kernel configuration to 
>make sure that any serial device or console related stuff was enabled 
>and configured.
>
>I'm feeling pretty stumped.
>
>- Chris
>
>Steve Iribarne (GMail) wrote:
>
>  
>
>>On 6/9/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
>>
>>    
>>
>>>I've now determined that my kernel seems to stop in the following
>>>      
>>>
>line
>  
>
>>>of code, in the function init(void * unused), in init/main.c:
>>>run_init_process("/sbin/init");
>>>      
>>>
>>Who's init are  you using??
>>
>>Are you using Busyboxes or sysinit from GNU?
>>
>>
>>    
>>
>>>I've determined that it stops at this call by stepping through the
>>>      
>>>
>code
>  
>
>>>with a BDI2000.
>>>
>>>My boot arguments are:
>>>console=ttyS0,57600n8 ip=off root=/dev/ram0 rw
>>>
>>>My current inittab is:
>>>::sysinit:/etc/rc.sh
>>>::ctrlaltdel:/sbin/reboot
>>>::shutdown:/sbin/swapoff -a
>>>::shutdown:/bin/umount -a -r
>>>::restart:/sbin/init
>>>::respawn:/bin/sh
>>>
>>>I've tried adding an "echo" command to the /etc/rc.sh script that is
>>>called, but I don't see any output. I've also trying changing the
>>>::sysinit line in inittab to point to some non-existent script, to
>>>      
>>>
>see
>  
>
>>>if I'll get some error message, but I still see nothing. Is it
>>>      
>>>
>possible
>  
>
>>>that /sbin/init is dying before it gets to the point of reading
>>>      
>>>
>inittab?
>  
>
>>>Any ideas?
>>>
>>>Regards,
>>>Chris Dumoulin
>>>
>>>
>>>Wolfgang Denk wrote:
>>>
>>>      
>>>
>>>>In message <44888B92.40409@ics-ltd.com> you wrote:
>>>>
>>>>
>>>>        
>>>>
>>>>>I am using the linux kernel 2.6.15 and initrd ramdisk image from
>>>>>          
>>>>>
>ELDK
>  
>
>>>>>4.0. Currently, I seem to be able to boot without errors, but after
>>>>>          
>>>>>
>
>  
>
>>>the
>>>      
>>>
>>>>>root filesystem is mounted, things just stop.
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>And  what's  your  console  device?  Are  you  passing  any
>>>>        
>>>>
>console=
>  
>
>>>>arguments  on  the  command  line?  Is the corresponding device
>>>>        
>>>>
>entry
>  
>
>>>>present in the /dev/directory?
>>>>
>>>>Best regards,
>>>>
>>>>Wolfgang Denk
>>>>
>>>>
>>>>
>>>>        
>>>>
>>>-- 
>>>*--Christopher Dumoulin--*
>>>Software Team Leader
>>>
>>><http://ics-ltd.com/>
>>><http://ics-ltd.com/>
>>>
>>>Interactive Circuits and Systems Ltd.
>>>5430 Canotek Road
>>>Ottawa, ON
>>>K1J 9G2
>>>(613)749-9241
>>>1-800-267-9794 (USA only)
>>>
>>>
>>>      
>>>
>------------------------------------------------------------------------
>  
>
>>>This e-mail is private and confidential and is for the addressee
>>>      
>>>
>only.
>  
>
>>>If misdirected, please notify us by telephone and confirm that it has
>>>been deleted from your system and any hard copies destroyed. You are
>>>strictly prohibited from using, printing, distributing or
>>>      
>>>
>disseminating
>  
>
>>>it or any information contained in it save to the intended recipient.
>>>_______________________________________________
>>>Linuxppc-embedded mailing list
>>>Linuxppc-embedded@ozlabs.org
>>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>>
>>>      
>>>
>
>
>  
>


-- 
*--Christopher Dumoulin--*
Software Team Leader

<http://ics-ltd.com/>
<http://ics-ltd.com/>

Interactive Circuits and Systems Ltd.
5430 Canotek Road
Ottawa, ON
K1J 9G2
(613)749-9241
1-800-267-9794 (USA only)

------------------------------------------------------------------------
This e-mail is private and confidential and is for the addressee only. 
If misdirected, please notify us by telephone and confirm that it has 
been deleted from your system and any hard copies destroyed. You are 
strictly prohibited from using, printing, distributing or disseminating 
it or any information contained in it save to the intended recipient.

RE: help with inittab

[Scott Coulter]

Chris,

I was getting linux 2.6.15 running an MPC8560 board with an external
UART.  In my board specific code that was setting up the Programmable
Interrupt Controller (openpic), I had a problem with a loop index and
the external interrupts were not getting setup correctly, but the
internal interrupts were...

Once I fixed the loop, there was output from the init process...

What type of board are you running on?  Do you have the UART interrupt
configured correctly (interrupt level high or low, interrupt input
definition, etc.)?


Scott





___________________________________________________________________

  Scott N. Coulter
  Senior Software Engineer
 =20
  Cyclone Microsystems         =20
  370 James Street              Phone:  203.786.5536 ext. 118
  New Haven, CT 06513-3051      Email:  scott.coulter@cyclone.com
  U.S.A.                        Web:    http://www.cyclone.com
___________________________________________________________________

-----Original Message-----
From: Chris Dumoulin [mailto:cdumoulin@ics-ltd.com]=20
Sent: Friday, June 09, 2006 3:50 PM
To: Scott Coulter
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: help with inittab

Hi Scott,
That is where my output stops. What was the cause of your interrupt=20
problem? Were you able to fix it?

- Chris

Scott Coulter wrote:

>Chris,
>
>Does your serial output stop after "Freeing unused kernel memory..."
>
>If it does, you may have an interrupt problem with the UART.  I had to
>track down that very problem the other day.  As a test, even if my UART
>interrupt was purposely misconfigured, I still saw all of the output up
>to and including "Freeing unused kernel memory..."
>
>Scott
>
>
>
>
>___________________________________________________________________
>
>  Scott N. Coulter
>  Senior Software Engineer
> =20
>  Cyclone Microsystems         =20
>  370 James Street              Phone:  203.786.5536 ext. 118
>  New Haven, CT 06513-3051      Email:  scott.coulter@cyclone.com
>  U.S.A.                        Web:    http://www.cyclone.com
>___________________________________________________________________
>
>-----Original Message-----
>From: linuxppc-embedded-bounces+scott.coulter=3Dcyclone.com@ozlabs.org
>[mailto:linuxppc-embedded-bounces+scott.coulter=3Dcyclone.com@ozlabs.org=
]
>On Behalf Of Chris Dumoulin
>Sent: Friday, June 09, 2006 3:15 PM
>To: Steve Iribarne (GMail)
>Cc: linuxppc-embedded@ozlabs.org
>Subject: Re: help with inittab
>
>The init is from Busybox. Since I'm getting output from my serial port=20
>during the kernel boot process, I think it's safe to say that my=20
>/dev/ttyS0 is properly configured. Besides passing the kernel argument=20
>console=3DttyS0,57600, is there anything else I need to do to properly=20
>configure the console? I've looked through my kernel configuration to=20
>make sure that any serial device or console related stuff was enabled=20
>and configured.
>
>I'm feeling pretty stumped.
>
>- Chris
>
>Steve Iribarne (GMail) wrote:
>
> =20
>
>>On 6/9/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
>>
>>   =20
>>
>>>I've now determined that my kernel seems to stop in the following
>>>     =20
>>>
>line
> =20
>
>>>of code, in the function init(void * unused), in init/main.c:
>>>run_init_process("/sbin/init");
>>>     =20
>>>
>>Who's init are  you using??
>>
>>Are you using Busyboxes or sysinit from GNU?
>>
>>
>>   =20
>>
>>>I've determined that it stops at this call by stepping through the
>>>     =20
>>>
>code
> =20
>
>>>with a BDI2000.
>>>
>>>My boot arguments are:
>>>console=3DttyS0,57600n8 ip=3Doff root=3D/dev/ram0 rw
>>>
>>>My current inittab is:
>>>::sysinit:/etc/rc.sh
>>>::ctrlaltdel:/sbin/reboot
>>>::shutdown:/sbin/swapoff -a
>>>::shutdown:/bin/umount -a -r
>>>::restart:/sbin/init
>>>::respawn:/bin/sh
>>>
>>>I've tried adding an "echo" command to the /etc/rc.sh script that is
>>>called, but I don't see any output. I've also trying changing the
>>>::sysinit line in inittab to point to some non-existent script, to
>>>     =20
>>>
>see
> =20
>
>>>if I'll get some error message, but I still see nothing. Is it
>>>     =20
>>>
>possible
> =20
>
>>>that /sbin/init is dying before it gets to the point of reading
>>>     =20
>>>
>inittab?
> =20
>
>>>Any ideas?
>>>
>>>Regards,
>>>Chris Dumoulin
>>>
>>>
>>>Wolfgang Denk wrote:
>>>
>>>     =20
>>>
>>>>In message <44888B92.40409@ics-ltd.com> you wrote:
>>>>
>>>>
>>>>       =20
>>>>
>>>>>I am using the linux kernel 2.6.15 and initrd ramdisk image from
>>>>>         =20
>>>>>
>ELDK
> =20
>
>>>>>4.0. Currently, I seem to be able to boot without errors, but after
>>>>>         =20
>>>>>
>
> =20
>
>>>the
>>>     =20
>>>
>>>>>root filesystem is mounted, things just stop.
>>>>>
>>>>>
>>>>>         =20
>>>>>
>>>>And  what's  your  console  device?  Are  you  passing  any
>>>>       =20
>>>>
>console=3D
> =20
>
>>>>arguments  on  the  command  line?  Is the corresponding device
>>>>       =20
>>>>
>entry
> =20
>
>>>>present in the /dev/directory?
>>>>
>>>>Best regards,
>>>>
>>>>Wolfgang Denk
>>>>
>>>>
>>>>
>>>>       =20
>>>>
>>>--=20
>>>*--Christopher Dumoulin--*
>>>Software Team Leader
>>>
>>><http://ics-ltd.com/>
>>><http://ics-ltd.com/>
>>>
>>>Interactive Circuits and Systems Ltd.
>>>5430 Canotek Road
>>>Ottawa, ON
>>>K1J 9G2
>>>(613)749-9241
>>>1-800-267-9794 (USA only)
>>>
>>>
>>>     =20
>>>
>-----------------------------------------------------------------------
-
> =20
>
>>>This e-mail is private and confidential and is for the addressee
>>>     =20
>>>
>only.
> =20
>
>>>If misdirected, please notify us by telephone and confirm that it has
>>>been deleted from your system and any hard copies destroyed. You are
>>>strictly prohibited from using, printing, distributing or
>>>     =20
>>>
>disseminating
> =20
>
>>>it or any information contained in it save to the intended recipient.
>>>_______________________________________________
>>>Linuxppc-embedded mailing list
>>>Linuxppc-embedded@ozlabs.org
>>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>>
>>>     =20
>>>
>
>
> =20
>


--=20
*--Christopher Dumoulin--*
Software Team Leader

<http://ics-ltd.com/>
<http://ics-ltd.com/>

Interactive Circuits and Systems Ltd.
5430 Canotek Road
Ottawa, ON
K1J 9G2
(613)749-9241
1-800-267-9794 (USA only)

------------------------------------------------------------------------
This e-mail is private and confidential and is for the addressee only.=20
If misdirected, please notify us by telephone and confirm that it has=20
been deleted from your system and any hard copies destroyed. You are=20
strictly prohibited from using, printing, distributing or disseminating=20
it or any information contained in it save to the intended recipient.

Re: help with inittab

[Steve Iribarne (GMail)]

On 6/9/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
> The init is from Busybox. Since I'm getting output from my serial port
> during the kernel boot process, I think it's safe to say that my
> /dev/ttyS0 is properly configured. Besides passing the kernel argument
> console=ttyS0,57600, is there anything else I need to do to properly
> configure the console? I've looked through my kernel configuration to
> make sure that any serial device or console related stuff was enabled
> and configured.
>
> I'm feeling pretty stumped.
>

Ok.. so if you are using the init from Busybox, there should be a
softlink and I can't remember where they put it.  I think it is the
root file system.  I think they call in linuxrc or something like
that.  I'd make sure you have that.

**OR** what I did..

Get sysinit from GNU and tell Busybox not to use the init.  I've had
this exact same problem and it was my init.

-stv
> - Chris
>
> Steve Iribarne (GMail) wrote:
>
> > On 6/9/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
> >
> >> I've now determined that my kernel seems to stop in the following line
> >> of code, in the function init(void * unused), in init/main.c:
> >> run_init_process("/sbin/init");
> >
> >
> > Who's init are  you using??
> >
> > Are you using Busyboxes or sysinit from GNU?
> >
> >
> >> I've determined that it stops at this call by stepping through the code
> >> with a BDI2000.
> >>
> >> My boot arguments are:
> >> console=ttyS0,57600n8 ip=off root=/dev/ram0 rw
> >>
> >> My current inittab is:
> >> ::sysinit:/etc/rc.sh
> >> ::ctrlaltdel:/sbin/reboot
> >> ::shutdown:/sbin/swapoff -a
> >> ::shutdown:/bin/umount -a -r
> >> ::restart:/sbin/init
> >> ::respawn:/bin/sh
> >>
> >> I've tried adding an "echo" command to the /etc/rc.sh script that is
> >> called, but I don't see any output. I've also trying changing the
> >> ::sysinit line in inittab to point to some non-existent script, to see
> >> if I'll get some error message, but I still see nothing. Is it possible
> >> that /sbin/init is dying before it gets to the point of reading inittab?
> >> Any ideas?
> >>
> >> Regards,
> >> Chris Dumoulin
> >>
> >>
> >> Wolfgang Denk wrote:
> >>
> >> >In message <44888B92.40409@ics-ltd.com> you wrote:
> >> >
> >> >
> >> >>I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK
> >> >>4.0. Currently, I seem to be able to boot without errors, but after
> >> the
> >> >>root filesystem is mounted, things just stop.
> >> >>
> >> >>
> >> >
> >> >And  what's  your  console  device?  Are  you  passing  any  console=
> >> >arguments  on  the  command  line?  Is the corresponding device entry
> >> >present in the /dev/directory?
> >> >
> >> >Best regards,
> >> >
> >> >Wolfgang Denk
> >> >
> >> >
> >> >
> >>
> >> --
> >> *--Christopher Dumoulin--*
> >> Software Team Leader
> >>
> >> <http://ics-ltd.com/>
> >> <http://ics-ltd.com/>
> >>
> >> Interactive Circuits and Systems Ltd.
> >> 5430 Canotek Road
> >> Ottawa, ON
> >> K1J 9G2
> >> (613)749-9241
> >> 1-800-267-9794 (USA only)
> >>
> >> ------------------------------------------------------------------------
> >> This e-mail is private and confidential and is for the addressee only.
> >> If misdirected, please notify us by telephone and confirm that it has
> >> been deleted from your system and any hard copies destroyed. You are
> >> strictly prohibited from using, printing, distributing or disseminating
> >> it or any information contained in it save to the intended recipient.
> >> _______________________________________________
> >> Linuxppc-embedded mailing list
> >> Linuxppc-embedded@ozlabs.org
> >> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >>
> >
>
>
> --
> *--Christopher Dumoulin--*
> Software Team Leader
>
> <http://ics-ltd.com/>
> <http://ics-ltd.com/>
>
> Interactive Circuits and Systems Ltd.
> 5430 Canotek Road
> Ottawa, ON
> K1J 9G2
> (613)749-9241
> 1-800-267-9794 (USA only)
>
> ------------------------------------------------------------------------
> This e-mail is private and confidential and is for the addressee only.
> If misdirected, please notify us by telephone and confirm that it has
> been deleted from your system and any hard copies destroyed. You are
> strictly prohibited from using, printing, distributing or disseminating
> it or any information contained in it save to the intended recipient.
>

Re: help with inittab

[Chris Dumoulin]

Scott, you are my saviour. The problem was in fact the IRQ setting. I 
changed the IRQ and now I get a shell, prompt, and everything. I never 
would have thought to check the UART settings, since I was getting 
output during kernel boot-up, I thought everything was good.

Thanks again,
Chris

Scott Coulter wrote:

>Chris,
>
>I was getting linux 2.6.15 running an MPC8560 board with an external
>UART.  In my board specific code that was setting up the Programmable
>Interrupt Controller (openpic), I had a problem with a loop index and
>the external interrupts were not getting setup correctly, but the
>internal interrupts were...
>
>Once I fixed the loop, there was output from the init process...
>
>What type of board are you running on?  Do you have the UART interrupt
>configured correctly (interrupt level high or low, interrupt input
>definition, etc.)?
>
>
>Scott
>
>
>
>
>
>___________________________________________________________________
>
>  Scott N. Coulter
>  Senior Software Engineer
>  
>  Cyclone Microsystems          
>  370 James Street              Phone:  203.786.5536 ext. 118
>  New Haven, CT 06513-3051      Email:  scott.coulter@cyclone.com
>  U.S.A.                        Web:    http://www.cyclone.com
>___________________________________________________________________
>
>-----Original Message-----
>From: Chris Dumoulin [mailto:cdumoulin@ics-ltd.com] 
>Sent: Friday, June 09, 2006 3:50 PM
>To: Scott Coulter
>Cc: linuxppc-embedded@ozlabs.org
>Subject: Re: help with inittab
>
>Hi Scott,
>That is where my output stops. What was the cause of your interrupt 
>problem? Were you able to fix it?
>
>- Chris
>
>Scott Coulter wrote:
>
>  
>
>>Chris,
>>
>>Does your serial output stop after "Freeing unused kernel memory..."
>>
>>If it does, you may have an interrupt problem with the UART.  I had to
>>track down that very problem the other day.  As a test, even if my UART
>>interrupt was purposely misconfigured, I still saw all of the output up
>>to and including "Freeing unused kernel memory..."
>>
>>Scott
>>
>>
>>
>>
>>___________________________________________________________________
>>
>> Scott N. Coulter
>> Senior Software Engineer
>> 
>> Cyclone Microsystems          
>> 370 James Street              Phone:  203.786.5536 ext. 118
>> New Haven, CT 06513-3051      Email:  scott.coulter@cyclone.com
>> U.S.A.                        Web:    http://www.cyclone.com
>>___________________________________________________________________
>>
>>-----Original Message-----
>>From: linuxppc-embedded-bounces+scott.coulter=cyclone.com@ozlabs.org
>>[mailto:linuxppc-embedded-bounces+scott.coulter=cyclone.com@ozlabs.org]
>>On Behalf Of Chris Dumoulin
>>Sent: Friday, June 09, 2006 3:15 PM
>>To: Steve Iribarne (GMail)
>>Cc: linuxppc-embedded@ozlabs.org
>>Subject: Re: help with inittab
>>
>>The init is from Busybox. Since I'm getting output from my serial port 
>>during the kernel boot process, I think it's safe to say that my 
>>/dev/ttyS0 is properly configured. Besides passing the kernel argument 
>>console=ttyS0,57600, is there anything else I need to do to properly 
>>configure the console? I've looked through my kernel configuration to 
>>make sure that any serial device or console related stuff was enabled 
>>and configured.
>>
>>I'm feeling pretty stumped.
>>
>>- Chris
>>
>>Steve Iribarne (GMail) wrote:
>>
>> 
>>
>>    
>>
>>>On 6/9/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
>>>
>>>   
>>>
>>>      
>>>
>>>>I've now determined that my kernel seems to stop in the following
>>>>     
>>>>
>>>>        
>>>>
>>line
>> 
>>
>>    
>>
>>>>of code, in the function init(void * unused), in init/main.c:
>>>>run_init_process("/sbin/init");
>>>>     
>>>>
>>>>        
>>>>
>>>Who's init are  you using??
>>>
>>>Are you using Busyboxes or sysinit from GNU?
>>>
>>>
>>>   
>>>
>>>      
>>>
>>>>I've determined that it stops at this call by stepping through the
>>>>     
>>>>
>>>>        
>>>>
>>code
>> 
>>
>>    
>>
>>>>with a BDI2000.
>>>>
>>>>My boot arguments are:
>>>>console=ttyS0,57600n8 ip=off root=/dev/ram0 rw
>>>>
>>>>My current inittab is:
>>>>::sysinit:/etc/rc.sh
>>>>::ctrlaltdel:/sbin/reboot
>>>>::shutdown:/sbin/swapoff -a
>>>>::shutdown:/bin/umount -a -r
>>>>::restart:/sbin/init
>>>>::respawn:/bin/sh
>>>>
>>>>I've tried adding an "echo" command to the /etc/rc.sh script that is
>>>>called, but I don't see any output. I've also trying changing the
>>>>::sysinit line in inittab to point to some non-existent script, to
>>>>     
>>>>
>>>>        
>>>>
>>see
>> 
>>
>>    
>>
>>>>if I'll get some error message, but I still see nothing. Is it
>>>>     
>>>>
>>>>        
>>>>
>>possible
>> 
>>
>>    
>>
>>>>that /sbin/init is dying before it gets to the point of reading
>>>>     
>>>>
>>>>        
>>>>
>>inittab?
>> 
>>
>>    
>>
>>>>Any ideas?
>>>>
>>>>Regards,
>>>>Chris Dumoulin
>>>>
>>>>
>>>>Wolfgang Denk wrote:
>>>>
>>>>     
>>>>
>>>>        
>>>>
>>>>>In message <44888B92.40409@ics-ltd.com> you wrote:
>>>>>
>>>>>
>>>>>       
>>>>>
>>>>>          
>>>>>
>>>>>>I am using the linux kernel 2.6.15 and initrd ramdisk image from
>>>>>>         
>>>>>>
>>>>>>            
>>>>>>
>>ELDK
>> 
>>
>>    
>>
>>>>>>4.0. Currently, I seem to be able to boot without errors, but after
>>>>>>         
>>>>>>
>>>>>>            
>>>>>>
>> 
>>
>>    
>>
>>>>the
>>>>     
>>>>
>>>>        
>>>>
>>>>>>root filesystem is mounted, things just stop.
>>>>>>
>>>>>>
>>>>>>         
>>>>>>
>>>>>>            
>>>>>>
>>>>>And  what's  your  console  device?  Are  you  passing  any
>>>>>       
>>>>>
>>>>>          
>>>>>
>>console=
>> 
>>
>>    
>>
>>>>>arguments  on  the  command  line?  Is the corresponding device
>>>>>       
>>>>>
>>>>>          
>>>>>
>>entry
>> 
>>
>>    
>>
>>>>>present in the /dev/directory?
>>>>>
>>>>>Best regards,
>>>>>
>>>>>Wolfgang Denk
>>>>>
>>>>>
>>>>>
>>>>>       
>>>>>
>>>>>          
>>>>>
>>>>-- 
>>>>*--Christopher Dumoulin--*
>>>>Software Team Leader
>>>>
>>>><http://ics-ltd.com/>
>>>><http://ics-ltd.com/>
>>>>
>>>>Interactive Circuits and Systems Ltd.
>>>>5430 Canotek Road
>>>>Ottawa, ON
>>>>K1J 9G2
>>>>(613)749-9241
>>>>1-800-267-9794 (USA only)
>>>>
>>>>
>>>>     
>>>>
>>>>        
>>>>
>>-----------------------------------------------------------------------
>>    
>>
>-
>  
>
>> 
>>
>>    
>>
>>>>This e-mail is private and confidential and is for the addressee
>>>>     
>>>>
>>>>        
>>>>
>>only.
>> 
>>
>>    
>>
>>>>If misdirected, please notify us by telephone and confirm that it has
>>>>been deleted from your system and any hard copies destroyed. You are
>>>>strictly prohibited from using, printing, distributing or
>>>>     
>>>>
>>>>        
>>>>
>>disseminating
>> 
>>
>>    
>>
>>>>it or any information contained in it save to the intended recipient.
>>>>_______________________________________________
>>>>Linuxppc-embedded mailing list
>>>>Linuxppc-embedded@ozlabs.org
>>>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>>>
>>>>     
>>>>
>>>>        
>>>>
>> 
>>
>>    
>>
>
>
>  
>


-- 
*--Christopher Dumoulin--*
Software Team Leader

<http://ics-ltd.com/>
<http://ics-ltd.com/>

Interactive Circuits and Systems Ltd.
5430 Canotek Road
Ottawa, ON
K1J 9G2
(613)749-9241
1-800-267-9794 (USA only)

------------------------------------------------------------------------
This e-mail is private and confidential and is for the addressee only. 
If misdirected, please notify us by telephone and confirm that it has 
been deleted from your system and any hard copies destroyed. You are 
strictly prohibited from using, printing, distributing or disseminating 
it or any information contained in it save to the intended recipient.

Re: help with inittab

[David H. Lynch Jr.]

   
    For debugging or single user purposes you do not need to run init or
have an inittab.
    There have been several sugestions that there may be a hardware
problem - there are a number that are possible.

    I was stalled here for some time because my UartDriver was
accidentally using the physical IO address instead of the virtual one
    and I had created a temporary phys=virtual entry in the tbl that was
conveniently getting blow away just here.

    You can try to isolate your problem by changing your boot ramdisk
(inramfs or initrd)

    Eliminate or rename /init /sbin/init /linuxrc and any of the other
permutations that linux tries to execute in init/main.c they are all
listed very near where you stopped.
    make sure you have /bin/sh

    reboot on that ramdisk  if you have an "init" related problem then
you should get a standalone shell.
    If you have a hardware problem you will likely still stop at the
same place.
   




-- 
Dave Lynch 					  	    DLA Systems
Software Development:  				         Embedded Linux
717.627.3770 	       dhlii@dlasys.net 	  http://www.dlasys.net
fax: 1.253.369.9244 			           Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.

"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein

Re: help with inittab

[Anantharaman Chetan-W16155]

I've tried what you've mentioned below, i.e removing the /sbin/init and
just having the /bin/sh in the init/main.c file and I don't get a
standalone shell. I am having a Linux 2.4 Kernel (Montavista 3.1)
running on a PPC405 in a Xilinx Virtex4 FX100 FPGA.

You mentioned it could be a hardware problem. Are there any errata which
could explain the h/w bug?=20


Thanks,
Chetan Anantharaman

----------------------------------------------------------------------

Message: 1
Date: Sun, 11 Jun 2006 22:02:02 -0400
From: "David H. Lynch Jr." <dhlii@dlasys.net>
Subject: Re: help with inittab
Cc: Chris Dumoulin <cdumoulin@ics-ltd.com>,
	linuxppc-embedded@ozlabs.org
Message-ID: <448CCB1A.409@dlasys.net>
Content-Type: text/plain; charset=3DISO-8859-1

  =20
    For debugging or single user purposes you do not need to run init or
have an inittab.
    There have been several sugestions that there may be a hardware
problem - there are a number that are possible.

    I was stalled here for some time because my UartDriver was
accidentally using the physical IO address instead of the virtual one
    and I had created a temporary phys=3Dvirtual entry in the tbl that =
was
conveniently getting blow away just here.

    You can try to isolate your problem by changing your boot ramdisk
(inramfs or initrd)

    Eliminate or rename /init /sbin/init /linuxrc and any of the other
permutations that linux tries to execute in init/main.c they are all
listed very near where you stopped.
    make sure you have /bin/sh

    reboot on that ramdisk  if you have an "init" related problem then
you should get a standalone shell.
    If you have a hardware problem you will likely still stop at the
same place.
  =20




--=20
Dave Lynch 					  	    DLA Systems
Software Development:  				         Embedded Linux
717.627.3770 	       dhlii@dlasys.net 	  http://www.dlasys.net
fax: 1.253.369.9244 			           Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too
numerous to list.

"Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction."
Albert Einstein

Re: help with inittab

[David H. Lynch Jr.]

    My specific problem turned out to be that the serial driver I had
written was still using the physical IO address that I had temporarily
mapped (virtual=physical) during very early boot, and when that
temporary mapping went away I instantly became deaf and dump and it just
happend to go away while starting init.

    But for a long time I though I had other problems, so things I tried
included:
          Writing a simple "hello world" program and running that from
where the kernel starts init.

          I think where the kernel starts init is the first place that
Linux actually starts making use of virtual memory.
    I beleive that the way the kernel loads a program involves actually
forcing pagefaults, so alot of things can work, but if paging is not
working perfectly
    you will not be able to start another process.

          Another thing you should watch out for is that there are two
places Linux looks to start an "init" process.
       The first uses whatever might be specified as a commandline
argument (or in your .config, or hardcoded in some BSP's)
        If that fails then it starts through a list of potential init
processes until one starts.
       I recently had a problem where I wanted to start "/bin/sh" as my
init so I commented out everything else, but left the command line
argument option in and still did not get /bin/sh because it was picking
up the argument from elsewhere.
      

Anantharaman Chetan-W16155 wrote:
> I've tried what you've mentioned below, i.e removing the /sbin/init and
> just having the /bin/sh in the init/main.c file and I don't get a
> standalone shell. I am having a Linux 2.4 Kernel (Montavista 3.1)
> running on a PPC405 in a Xilinx Virtex4 FX100 FPGA.
>
> You mentioned it could be a hardware problem. Are there any errata which
> could explain the h/w bug? 
>
>
> Thanks,
> Chetan Anantharaman
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 11 Jun 2006 22:02:02 -0400
> From: "David H. Lynch Jr." <dhlii@dlasys.net>
> Subject: Re: help with inittab
> Cc: Chris Dumoulin <cdumoulin@ics-ltd.com>,
> 	linuxppc-embedded@ozlabs.org
> Message-ID: <448CCB1A.409@dlasys.net>
> Content-Type: text/plain; charset=ISO-8859-1
>
>    
>     For debugging or single user purposes you do not need to run init or
> have an inittab.
>     There have been several sugestions that there may be a hardware
> problem - there are a number that are possible.
>
>     I was stalled here for some time because my UartDriver was
> accidentally using the physical IO address instead of the virtual one
>     and I had created a temporary phys=virtual entry in the tbl that was
> conveniently getting blow away just here.
>
>     You can try to isolate your problem by changing your boot ramdisk
> (inramfs or initrd)
>
>     Eliminate or rename /init /sbin/init /linuxrc and any of the other
> permutations that linux tries to execute in init/main.c they are all
> listed very near where you stopped.
>     make sure you have /bin/sh
>
>     reboot on that ramdisk  if you have an "init" related problem then
> you should get a standalone shell.
>     If you have a hardware problem you will likely still stop at the
> same place.
>    
>
>
>
>
>   


-- 
Dave Lynch 					  	    DLA Systems
Software Development:  				         Embedded Linux
717.627.3770 	       dhlii@dlasys.net 	  http://www.dlasys.net
fax: 1.253.369.9244 			           Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.

"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein