* inittab is not executing after my Linux box boots up @ 2011-06-14 17:07 Prajosh Premdas 2011-06-14 17:19 ` Dave Hylands 0 siblings, 1 reply; 11+ messages in thread From: Prajosh Premdas @ 2011-06-14 17:07 UTC (permalink / raw) To: kernelnewbies Hi I am stuck with a problem. inittab is not executing after my Linux box boots up. The problem in detail. I have a linux box, i load the Linux image uImage using TFTP and my root file system is configured in NFS. After the security key is generated, my box just waits there infinity. Its not starting a new terminal. The new terminal has been specified in the inittab as ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL Can anybody help me out with this problem? Since i am not able to set password i cannot do a secure shell access too. -- Regards, Prajosh Premdas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110614/95a092ea/attachment.html ^ permalink raw reply [flat|nested] 11+ messages in thread
* inittab is not executing after my Linux box boots up 2011-06-14 17:07 inittab is not executing after my Linux box boots up Prajosh Premdas @ 2011-06-14 17:19 ` Dave Hylands 2011-06-14 17:22 ` Prajosh Premdas 0 siblings, 1 reply; 11+ messages in thread From: Dave Hylands @ 2011-06-14 17:19 UTC (permalink / raw) To: kernelnewbies Hi Prajosh, On Tue, Jun 14, 2011 at 10:07 AM, Prajosh Premdas <premdas.prajosh@gmail.com> wrote: > Hi > I am stuck with a problem. inittab is not executing after my Linux box boots > up. > The problem in detail. I have a linux box, i load the Linux image uImage > using TFTP and my root file system is configured in NFS. After the security > key is generated, my box just waits there?infinity. Its not starting a new > terminal. > The new terminal has been specified in the inittab as > ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL > Can anybody help me out with this problem? > Since i am not able to set password i cannot do a secure shell?access?too. If I had to guess (since you didn't include any boot logs, that's pretty much all I can do), I'd say that your NFS mount of the root file system isn't working. You can always try and see if you can even boot into a shell manually, by adding init=/bin/sh to the kernel command line. Have you tried booting without using NFS, and verifying that you can mount the NFS volume? -- Dave Hylands Shuswap, BC, Canada http://www.davehylands.com ^ permalink raw reply [flat|nested] 11+ messages in thread
* inittab is not executing after my Linux box boots up 2011-06-14 17:19 ` Dave Hylands @ 2011-06-14 17:22 ` Prajosh Premdas 2011-06-15 6:40 ` Raseel Bhagat 0 siblings, 1 reply; 11+ messages in thread From: Prajosh Premdas @ 2011-06-14 17:22 UTC (permalink / raw) To: kernelnewbies Hi Dave I tried booting with the root file system in my flash and uImage i copy using TFTP everything is fine. On Tue, Jun 14, 2011 at 10:49 PM, Dave Hylands <dhylands@gmail.com> wrote: > Hi Prajosh, > > On Tue, Jun 14, 2011 at 10:07 AM, Prajosh Premdas > <premdas.prajosh@gmail.com> wrote: > > Hi > > I am stuck with a problem. inittab is not executing after my Linux box > boots > > up. > > The problem in detail. I have a linux box, i load the Linux image uImage > > using TFTP and my root file system is configured in NFS. After the > security > > key is generated, my box just waits there infinity. Its not starting a > new > > terminal. > > The new terminal has been specified in the inittab as > > ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL > > Can anybody help me out with this problem? > > Since i am not able to set password i cannot do a secure > shell access too. > > If I had to guess (since you didn't include any boot logs, that's > pretty much all I can do), I'd say that your NFS mount of the root > file system isn't working. > > You can always try and see if you can even boot into a shell manually, > by adding init=/bin/sh to the kernel command line. > > Have you tried booting without using NFS, and verifying that you can > mount the NFS volume? > > -- > Dave Hylands > Shuswap, BC, Canada > http://www.davehylands.com > -- Regards, Prajosh Premdas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110614/14a84a68/attachment.html ^ permalink raw reply [flat|nested] 11+ messages in thread
* inittab is not executing after my Linux box boots up 2011-06-14 17:22 ` Prajosh Premdas @ 2011-06-15 6:40 ` Raseel Bhagat 2011-06-19 15:24 ` Prajosh Premdas 0 siblings, 1 reply; 11+ messages in thread From: Raseel Bhagat @ 2011-06-15 6:40 UTC (permalink / raw) To: kernelnewbies On Tue, Jun 14, 2011 at 7:22 PM, Prajosh Premdas <premdas.prajosh@gmail.com>wrote: > Hi Dave > > I tried booting with the root file system in my flash and uImage i copy > using TFTP everything is fine. > > > On Tue, Jun 14, 2011 at 10:49 PM, Dave Hylands <dhylands@gmail.com> wrote: > >> Hi Prajosh, >> >> On Tue, Jun 14, 2011 at 10:07 AM, Prajosh Premdas >> <premdas.prajosh@gmail.com> wrote: >> > Hi >> > I am stuck with a problem. inittab is not executing after my Linux box >> boots >> > up. >> > The problem in detail. I have a linux box, i load the Linux image uImage >> > using TFTP and my root file system is configured in NFS. After the >> security >> > key is generated, my box just waits there infinity. Its not starting a >> new >> > terminal. >> > The new terminal has been specified in the inittab as >> > ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL >> > Can anybody help me out with this problem? >> > Since i am not able to set password i cannot do a secure >> shell access too. >> >> If I had to guess (since you didn't include any boot logs, that's >> pretty much all I can do), I'd say that your NFS mount of the root >> file system isn't working. >> >> You can always try and see if you can even boot into a shell manually, >> by adding init=/bin/sh to the kernel command line. >> >> Have you tried booting without using NFS, and verifying that you can >> mount the NFS volume? >> >> -- >> Dave Hylands >> Shuswap, BC, Canada >> http://www.davehylands.com >> > > > > -- > Regards, > > Prajosh Premdas > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies at kernelnewbies.org > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > > Hi Prajosh, Could you post what exact error are you getting. I had a very similar problem recently when trying to boot the kernel using tftp and then mounting the Rootfs over NFS. The issue I faced was that the Rootfs' /dev directory was not correctly populated and was missing the /dev/console device. I was getting an error on the lines of "Unable to start init console" and I too spent time mucking about in my inittab. Thanks, Raseel -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110615/4dd2cbac/attachment.html ^ permalink raw reply [flat|nested] 11+ messages in thread
* inittab is not executing after my Linux box boots up 2011-06-15 6:40 ` Raseel Bhagat @ 2011-06-19 15:24 ` Prajosh Premdas 2011-06-19 15:53 ` Mulyadi Santosa ` (2 more replies) 0 siblings, 3 replies; 11+ messages in thread From: Prajosh Premdas @ 2011-06-19 15:24 UTC (permalink / raw) To: kernelnewbies Hi Please find the entire boot sequence here *RomBOOT* * * * * *U-Boot 1.3.4 (Mar 9 2010 - 19:35:35)* * * *DRAM: 64 MB* *NAND: 256 MiB* *In: serial* *Out: serial* *Err: serial* *Net: macb0* *macb0: Starting autonegotiation...* *macb0: Autonegotiation complete* *macb0: link up, 100Mbps full-duplex (lpa: 0xc5e1)* *Hit any key to stop autoboot: 0* *U-Boot>* *U-Boot> set bootcmd 'tftp 0x22200000 uImage; bootm 0x22200000'* *U-Boot> set bootargs 'root=/dev/nfs nfsroot=10.0.0.1:/nfs ip=10.220.4.200: :10.220.4.35:::eth0:off console=ttyS0,115200'* *U-Boot> print* *ethaddr=3a:1f:34:08:54:54* *bootdelay=3* *baudrate=115200* *ethact=macb0* *ipaddr=10.0.0.2* *serverip=10.0.0.1* *stdin=serial* *stdout=serial* *stderr=serial* *bootcmd=tftp 0x22200000 uImage; bootm 0x22200000* *bootargs=root=/dev/nfs nfsroot=10.0.0.1:/nfs ip=10.220.4.200::10.220.4.35:::eth0:off console=ttyS0,115200* * * *Environment size: 297/131067 bytes* *U-Boot> boot* *macb0: link up, 100Mbps full-duplex (lpa: 0xc5e1)* *Using macb0 device* *TFTP from server 10.0.0.1; our IP address is 10.0.0.2* *Filename 'uImage'.* *Load address: 0x22200000* *Loading: #################################################################* * #####################################################* *done* *Bytes transferred = 1720076 (1a3f0c hex)* *## Booting kernel from Legacy Image at 22200000 ...* * Image Name: Linux-2.6.37* * Image Type: ARM Linux Kernel Image (uncompressed)* * Data Size: 1720012 Bytes = 1.6 MB* * Load Address: 20008000* * Entry Point: 20008000* * Verifying Checksum ... OK* * Loading Kernel Image ... OK* *OK* * * *Starting kernel ...* * * *Uncompressing Linux... done, booting the kernel.* *Linux version 2.6.37 (prajosh at prajosh) (gcc version 4.3.5 (Buildroot 2011.02) ) #2 Sun Jun 19 15:27:13 IST 2011* *CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177* *CPU: VIVT data cache, VIVT instruction cache* *Machine: Atmel AT91SAM9G20-EK* *Memory policy: ECC disabled, Data cache writeback* *Clocks: CPU 396 MHz, master 132 MHz, main 18.432 MHz* *Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256* *Kernel command line: root=/dev/nfs nfsroot=10.0.0.1:/nfs ip=10.220.4.200: :10.220.4.35:::eth0:off console=ttyS0,115200* *PID hash table entries: 256 (order: -2, 1024 bytes)* *Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)* *Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)* *Memory: 64MB = 64MB total* *Memory: 61416k/61416k available, 4120k reserved, 0K highmem* *Virtual kernel memory layout:* * vector : 0xffff0000 - 0xffff1000 ( 4 kB)* * fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)* * DMA : 0xffc00000 - 0xffe00000 ( 2 MB)* * vmalloc : 0xc4800000 - 0xfee00000 ( 934 MB)* * lowmem : 0xc0000000 - 0xc4000000 ( 64 MB)* * modules : 0xbf000000 - 0xc0000000 ( 16 MB)* * .init : 0xc0008000 - 0xc0028000 ( 128 kB)* * .text : 0xc0028000 - 0xc032e0f8 (3097 kB)* * .data : 0xc0330000 - 0xc0350fe0 ( 132 kB)* *NR_IRQS:192* *AT91: 96 gpio irqs in 3 banks* *Console: colour dummy device 80x30* *console [ttyS0] enabled* *Calibrating delay loop... 197.83 BogoMIPS (lpj=989184)* *pid_max: default: 32768 minimum: 301* *Mount-cache hash table entries: 512* *CPU: Testing write buffer coherency: ok* *NET: Registered protocol family 16* *AT91: Power Management* *AT91: Starting after user reset* *bio: create slab <bio-0> at 0* *SCSI subsystem initialized* *usbcore: registered new interface driver usbfs* *usbcore: registered new interface driver hub* *usbcore: registered new device driver usb* *Advanced Linux Sound Architecture Driver Version 1.0.23.* *Switching to clocksource pit* *NET: Registered protocol family 2* *IP route cache hash table entries: 1024 (order: 0, 4096 bytes)* *TCP established hash table entries: 2048 (order: 2, 16384 bytes)* *TCP bind hash table entries: 2048 (order: 1, 8192 bytes)* *TCP: Hash tables configured (established 2048 bind 2048)* *TCP reno registered* *UDP hash table entries: 256 (order: 0, 4096 bytes)* *UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)* *NET: Registered protocol family 1* *RPC: Registered udp transport module.* *RPC: Registered tcp transport module.* *RPC: Registered tcp NFSv4.1 backchannel transport module.* *NetWinder Floating Point Emulator V0.97 (double precision)* *JFFS2 version 2.2. (NAND) (SUMMARY) ?? 2001-2006 Red Hat, Inc.* *msgmni has been set to 119* *io scheduler noop registered (default)* *atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL* *atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL* *atmel_usart.2: ttyS2 at MMIO 0xfffb4000 (irq = 7) is a ATMEL_SERIAL* *brd: module loaded* *loop: module loaded* *NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung )* *Scanning device for bad blocks* *Bad eraseblock 532 at 0x000004280000* *Bad eraseblock 1572 at 0x00000c480000* *Creating 3 MTD partitions on "atmel_nand":* *0x000000000000-0x000000400000 : "Bootstrap"* *0x000000400000-0x000004000000 : "Partition 1"* *0x000004000000-0x000010000000 : "Partition 2"* *atmel_spi atmel_spi.0: Atmel SPI Controller at 0xfffc8000 (irq 12)* *atmel_spi atmel_spi.1: Atmel SPI Controller at 0xfffcc000 (irq 13)* *MACB_mii_bus: probed* *eth0: Atmel MACB at 0xfffc4000 irq 21 (3a:1f:34:08:54:54)* *eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, irq=-1)* *usbmon: debugfs is not available* *ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver* *at91_ohci at91_ohci: AT91 OHCI* *at91_ohci at91_ohci: new USB bus registered, assigned bus number 1* *at91_ohci at91_ohci: irq 20, io mem 0x00500000* *hub 1-0:1.0: USB hub found* *hub 1-0:1.0: 2 ports detected* *Initializing USB Mass Storage driver...* *usbcore: registered new interface driver usb-storage* *USB Mass Storage support registered.* *udc: at91_udc version 3 May 2006* *mice: PS/2 mouse device common for all mice* *input: gpio-keys as /devices/platform/gpio-keys/input/input0* *rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0* *rtc-at91sam9 at91_rtt.0: rtc0: SET TIME!* *usbcore: registered new interface driver usbhid* *usbhid: USB HID core driver* *ALSA device list:* * No soundcards found.* *TCP cubic registered* *NET: Registered protocol family 17* *rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock* *IP-Config: Guessing netmask 255.0.0.0* *IP-Config: Complete:* * device=eth0, addr=10.220.4.200, mask=255.0.0.0, gw=10.220.4.35,* * host=10.220.4.200, domain=, nis-domain=(none),* * bootserver=255.255.255.255, rootserver=10.0.0.1, rootpath=* *eth0: link up (100/Full)* *VFS: Mounted root (nfs filesystem) on device 0:12.* *Freeing init memory: 128K* *Starting network...* *ip: RTNETLINK answers: File exists* *Starting dropbear sshd: generating rsa key... generating dsa key... OK* I have put down the entire sequence. I have also shown the u-boot parameters. Could anybody please tell me why the board stops after the command. I have the same file system flashed on my NAND flash and if i show that path for the boot operation every thing works fine. (i.e. i load the kernel on tftp and boot from that.) Regards Prajosh Premdas On Wed, Jun 15, 2011 at 12:10 PM, Raseel Bhagat <raseelbhagat@gmail.com>wrote: > > > On Tue, Jun 14, 2011 at 7:22 PM, Prajosh Premdas < > premdas.prajosh at gmail.com> wrote: > >> Hi Dave >> >> I tried booting with the root file system in my flash and uImage i copy >> using TFTP everything is fine. >> >> >> On Tue, Jun 14, 2011 at 10:49 PM, Dave Hylands <dhylands@gmail.com>wrote: >> >>> Hi Prajosh, >>> >>> On Tue, Jun 14, 2011 at 10:07 AM, Prajosh Premdas >>> <premdas.prajosh@gmail.com> wrote: >>> > Hi >>> > I am stuck with a problem. inittab is not executing after my Linux box >>> boots >>> > up. >>> > The problem in detail. I have a linux box, i load the Linux image >>> uImage >>> > using TFTP and my root file system is configured in NFS. After the >>> security >>> > key is generated, my box just waits there infinity. Its not starting a >>> new >>> > terminal. >>> > The new terminal has been specified in the inittab as >>> > ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL >>> > Can anybody help me out with this problem? >>> > Since i am not able to set password i cannot do a secure >>> shell access too. >>> >>> If I had to guess (since you didn't include any boot logs, that's >>> pretty much all I can do), I'd say that your NFS mount of the root >>> file system isn't working. >>> >>> You can always try and see if you can even boot into a shell manually, >>> by adding init=/bin/sh to the kernel command line. >>> >>> Have you tried booting without using NFS, and verifying that you can >>> mount the NFS volume? >>> >>> -- >>> Dave Hylands >>> Shuswap, BC, Canada >>> http://www.davehylands.com >>> >> >> >> >> -- >> Regards, >> >> Prajosh Premdas >> >> _______________________________________________ >> Kernelnewbies mailing list >> Kernelnewbies at kernelnewbies.org >> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies >> >> > > Hi Prajosh, > > Could you post what exact error are you getting. > I had a very similar problem recently when trying to boot the kernel using > tftp and then mounting the Rootfs over NFS. > The issue I faced was that the Rootfs' /dev directory was not correctly > populated and was missing the /dev/console device. > > I was getting an error on the lines of "Unable to start init console" and I > too spent time mucking about in my inittab. > > > Thanks, > Raseel > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies at kernelnewbies.org > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > > -- Regards, Prajosh Premdas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110619/40ded59f/attachment-0001.html ^ permalink raw reply [flat|nested] 11+ messages in thread
* inittab is not executing after my Linux box boots up 2011-06-19 15:24 ` Prajosh Premdas @ 2011-06-19 15:53 ` Mulyadi Santosa 2011-06-19 17:52 ` Dave Hylands 2011-06-21 17:32 ` dinesh bhaskar 2 siblings, 0 replies; 11+ messages in thread From: Mulyadi Santosa @ 2011-06-19 15:53 UTC (permalink / raw) To: kernelnewbies Hi ... I might be wrong but...( see below) On Sun, Jun 19, 2011 at 22:24, Prajosh Premdas <premdas.prajosh@gmail.com> wrote: > U-Boot> set bootargs 'root=/dev/nfs nfsroot=10.0.0.1:/nfs > ip=10.220.4.200::10.220.4.35:::eth0:off console=ttyS0,115200' so you're contacting NFS server at 10.0.0.1 but you set yourself having IP address 10.220.4.200 (or something like that)? I am not sure what your subnet mask is...but isn't that sound like at two different network? CMIIW -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com ^ permalink raw reply [flat|nested] 11+ messages in thread
* inittab is not executing after my Linux box boots up 2011-06-19 15:24 ` Prajosh Premdas 2011-06-19 15:53 ` Mulyadi Santosa @ 2011-06-19 17:52 ` Dave Hylands 2011-06-20 6:24 ` Prajosh Premdas 2011-06-21 17:32 ` dinesh bhaskar 2 siblings, 1 reply; 11+ messages in thread From: Dave Hylands @ 2011-06-19 17:52 UTC (permalink / raw) To: kernelnewbies Hi Projish, On Sun, Jun 19, 2011 at 8:24 AM, Prajosh Premdas <premdas.prajosh@gmail.com> wrote: > Hi > Please find the entire boot sequence here > RomBOOT ...snip... > TCP cubic registered > NET: Registered protocol family 17 > rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock > IP-Config: Guessing netmask 255.0.0.0 > IP-Config: Complete: > ? ? ?device=eth0, addr=10.220.4.200, mask=255.0.0.0, gw=10.220.4.35, > ? ? ?host=10.220.4.200, domain=, nis-domain=(none), > ? ? ?bootserver=255.255.255.255, rootserver=10.0.0.1, rootpath= > eth0: link up (100/Full) > VFS: Mounted root (nfs filesystem) on device 0:12. So it looks like your root file system was mounted successfully. > Freeing init memory: 128K All message from this point onwards come from init. > Starting network... > ip: RTNETLINK answers: File exists > Starting dropbear sshd: generating rsa key... generating dsa key... OK And since sshd is starting, it's actually processing stuff from your root file system. You may want to try disabling ssh. Generating the rsa key can take several minutes, depending on how fast your target is. So it may look like the system is hung, but it will actually continue to boot. You may want save away the generated RSA key and include it in your generated image so that this step is faster. For a given filesystem, it only happens the first time, and once the generated key is stored, ssh will just use the previously generated key. But if you're constantly rebuilding your filesystem without any generated keys then the first time you boot the new filesystem you'lll gget a long delay. -- Dave Hylands Shuswap, BC, Canada http://www.davehylands.com ^ permalink raw reply [flat|nested] 11+ messages in thread
* inittab is not executing after my Linux box boots up 2011-06-19 17:52 ` Dave Hylands @ 2011-06-20 6:24 ` Prajosh Premdas [not found] ` <BANLkTikR191M+gLTYVstGiNbR3-DNa58Dw@mail.gmail.com> 0 siblings, 1 reply; 11+ messages in thread From: Prajosh Premdas @ 2011-06-20 6:24 UTC (permalink / raw) To: kernelnewbies Hi Dave and Mulyadi Can you tell me where to place the previously generated RSA key. I even suspected this but this line *Starting dropbear sshd: generating rsa key... generating dsa key... OK* and the OK pulled me off the track. One more thing can you tell me what does the OK mean there... My mask is mask=255.0.0.0 so it is able to get the NFS server location I typed a wrong command after changing the commands i find no difference On Sun, Jun 19, 2011 at 11:22 PM, Dave Hylands <dhylands@gmail.com> wrote: > Hi Projish, > > On Sun, Jun 19, 2011 at 8:24 AM, Prajosh Premdas > <premdas.prajosh@gmail.com> wrote: > > Hi > > Please find the entire boot sequence here > > RomBOOT > ...snip... > > TCP cubic registered > > NET: Registered protocol family 17 > > rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock > > IP-Config: Guessing netmask 255.0.0.0 > > IP-Config: Complete: > > device=eth0, addr=10.220.4.200, mask=255.0.0.0, gw=10.220.4.35, > > host=10.220.4.200, domain=, nis-domain=(none), > > bootserver=255.255.255.255, rootserver=10.0.0.1, rootpath= > > eth0: link up (100/Full) > > VFS: Mounted root (nfs filesystem) on device 0:12. > > So it looks like your root file system was mounted successfully. > > > Freeing init memory: 128K > > All message from this point onwards come from init. > > > Starting network... > > ip: RTNETLINK answers: File exists > > Starting dropbear sshd: generating rsa key... generating dsa key... OK > > And since sshd is starting, it's actually processing stuff from your > root file system. > > You may want to try disabling ssh. Generating the rsa key can take > several minutes, depending on how fast your target is. So it may look > like the system is hung, but it will actually continue to boot. > > You may want save away the generated RSA key and include it in your > generated image so that this step is faster. For a given filesystem, > it only happens the first time, and once the generated key is stored, > ssh will just use the previously generated key. But if you're > constantly rebuilding your filesystem without any generated keys then > the first time you boot the new filesystem you'lll gget a long delay. > > -- > Dave Hylands > Shuswap, BC, Canada > http://www.davehylands.com > -- Regards, Prajosh Premdas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110620/81eacb27/attachment.html ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <BANLkTikR191M+gLTYVstGiNbR3-DNa58Dw@mail.gmail.com>]
[parent not found: <BANLkTi=wQ3BHUtVKXu5_UH_x7oXFKvZdJw@mail.gmail.com>]
* inittab is not executing after my Linux box boots up [not found] ` <BANLkTi=wQ3BHUtVKXu5_UH_x7oXFKvZdJw@mail.gmail.com> @ 2011-06-21 8:50 ` Prajosh Premdas 2011-06-21 9:31 ` Bernd Petrovitsch 0 siblings, 1 reply; 11+ messages in thread From: Prajosh Premdas @ 2011-06-21 8:50 UTC (permalink / raw) To: kernelnewbies Hi I have copied the generated rsa key and placed it in my nfs root filesystem. I find the problem still persists Please see the last leg of the logs below *eth0: link up (100/Full)* *VFS: Mounted root (nfs filesystem) on device 0:12.* *Freeing init memory: 128K* *Starting network...* *ip: RTNETLINK answers: File exists* *Starting dropbear sshd: OK* * * I feel the already generated key has been detected. And still the initab doesn't execute. Please advice On Tue, Jun 21, 2011 at 11:15 AM, Vladimir Murzin <murzin.v@gmail.com>wrote: > On Mon, Jun 20, 2011 at 10:24 AM, Prajosh Premdas > <premdas.prajosh@gmail.com> wrote: > > Hi Dave and Mulyadi > > Can you tell me where to place the previously generated RSA key. I even > > suspected this but this line > > Starting dropbear sshd: generating rsa key... generating dsa key... OK > > > > and the OK pulled me off the track. One more thing can you tell me what > > does the OK mean there... > > My mask is mask=255.0.0.0 so it is able to get the NFS server location > > I typed a wrong command after changing the commands i find no difference > > On Sun, Jun 19, 2011 at 11:22 PM, Dave Hylands <dhylands@gmail.com> > wrote: > >> > >> Hi Projish, > >> > >> On Sun, Jun 19, 2011 at 8:24 AM, Prajosh Premdas > >> <premdas.prajosh@gmail.com> wrote: > >> > Hi > >> > Please find the entire boot sequence here > >> > RomBOOT > >> ...snip... > >> > TCP cubic registered > >> > NET: Registered protocol family 17 > >> > rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock > >> > IP-Config: Guessing netmask 255.0.0.0 > >> > IP-Config: Complete: > >> > device=eth0, addr=10.220.4.200, mask=255.0.0.0, gw=10.220.4.35, > >> > host=10.220.4.200, domain=, nis-domain=(none), > >> > bootserver=255.255.255.255, rootserver=10.0.0.1, rootpath= > >> > eth0: link up (100/Full) > >> > VFS: Mounted root (nfs filesystem) on device 0:12. > >> > >> So it looks like your root file system was mounted successfully. > >> > >> > Freeing init memory: 128K > >> > >> All message from this point onwards come from init. > >> > >> > Starting network... > >> > ip: RTNETLINK answers: File exists > >> > Starting dropbear sshd: generating rsa key... generating dsa key... OK > >> > >> And since sshd is starting, it's actually processing stuff from your > >> root file system. > >> > >> You may want to try disabling ssh. Generating the rsa key can take > >> several minutes, depending on how fast your target is. So it may look > >> like the system is hung, but it will actually continue to boot. > >> > >> You may want save away the generated RSA key and include it in your > >> generated image so that this step is faster. For a given filesystem, > >> it only happens the first time, and once the generated key is stored, > >> ssh will just use the previously generated key. But if you're > >> constantly rebuilding your filesystem without any generated keys then > >> the first time you boot the new filesystem you'lll gget a long delay. > >> > >> -- > >> Dave Hylands > >> Shuswap, BC, Canada > >> http://www.davehylands.com > > > > > > > > -- > > Regards, > > > > Prajosh Premdas > > > > _______________________________________________ > > Kernelnewbies mailing list > > Kernelnewbies at kernelnewbies.org > > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > > > > > > Hi Prajosh, > > I believe, that generating keys by sshd involve blocked operation on > /dev/random. > It's strict requirement to use /dev/random instead of /dev/urandom in such > case. > > Actually, it's well-known problem in embedded world to fill up entropy > pool, because of > lack random events into some solutions. > > I've heard it's possible to save and restore entropy pool, but it's > not safe, I think. > In my opinion, Dave's suggestion about saving keys into image is quite > suitable, as > soon as you aren't intend to distribute you solution on the market. > > P.S. Sorry for my English. > -- Regards, Prajosh Premdas -- Regards, Prajosh Premdas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110621/6fcfa7f3/attachment.html ^ permalink raw reply [flat|nested] 11+ messages in thread
* inittab is not executing after my Linux box boots up 2011-06-21 8:50 ` Prajosh Premdas @ 2011-06-21 9:31 ` Bernd Petrovitsch 0 siblings, 0 replies; 11+ messages in thread From: Bernd Petrovitsch @ 2011-06-21 9:31 UTC (permalink / raw) To: kernelnewbies Hi! First, don't top-post. On Die, 2011-06-21 at 14:20 +0530, Prajosh Premdas wrote: [...] > I have copied the generated rsa key and placed it in my nfs root > filesystem. I find the problem still persists > Please see the last leg of the logs below > eth0: link up (100/Full) > VFS: Mounted root (nfs filesystem) on device 0:12. > Freeing init memory: 128K > Starting network... > ip: RTNETLINK answers: File exists > Starting dropbear sshd: OK And you are sure, you cannot login per ssh? > I feel the already generated key has been detected. And still the > initab doesn't execute. Please advice Apart from the fact, that this isn't a kernel issue: The output from above clearly says that user-space stuff is running - daemons, programs, scripts started either indirectly from init or from a /linuxrc (which may explain why inittab is ignored - I don't not remember what happens if a /linuxrc exits). Kind regards, Bernd -- Bernd Petrovitsch Email : bernd at petrovitsch.priv.at LUGA : http://www.luga.at ^ permalink raw reply [flat|nested] 11+ messages in thread
* inittab is not executing after my Linux box boots up 2011-06-19 15:24 ` Prajosh Premdas 2011-06-19 15:53 ` Mulyadi Santosa 2011-06-19 17:52 ` Dave Hylands @ 2011-06-21 17:32 ` dinesh bhaskar 2 siblings, 0 replies; 11+ messages in thread From: dinesh bhaskar @ 2011-06-21 17:32 UTC (permalink / raw) To: kernelnewbies Hi Prajosh, On Sun, Jun 19, 2011 at 11:24 AM, Prajosh Premdas <premdas.prajosh@gmail.com > wrote: > Hi > > Please find the entire boot sequence here > > *RomBOOT* > * > * > > *Machine: Atmel AT91SAM9G20-EK* > *Memory policy: ECC disabled, Data cache writeback* > *Clocks: CPU 396 MHz, master 132 MHz, main 18.432 MHz* > *Built 1 zonelists in Zone order, mobility grouping on. Total pages: > 16256* > *Kernel command line: root=/dev/nfs nfsroot=10.0.0.1:/nfs ip=10.220.4.200: > :10.220.4.35:::eth0:off console=ttyS0,115200* > > *MACB_mii_bus: probed* > *eth0: Atmel MACB at 0xfffc4000 irq 21 (3a:1f:34:08:54:54)* > *eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, > irq=-1)* > Could it be the problem with the ethernet. Were you able to ping the LAN when booted without the NFS? Phy address seems to be wrong(ffff...) and the irq as well. Dinesh > > > > On Wed, Jun 15, 2011 at 12:10 PM, Raseel Bhagat <raseelbhagat@gmail.com>wrote: > >> >> >> On Tue, Jun 14, 2011 at 7:22 PM, Prajosh Premdas < >> premdas.prajosh at gmail.com> wrote: >> >>> Hi Dave >>> >>> I tried booting with the root file system in my flash and uImage i copy >>> using TFTP everything is fine. >>> >>> >>> On Tue, Jun 14, 2011 at 10:49 PM, Dave Hylands <dhylands@gmail.com>wrote: >>> >>>> Hi Prajosh, >>>> >>>> On Tue, Jun 14, 2011 at 10:07 AM, Prajosh Premdas >>>> <premdas.prajosh@gmail.com> wrote: >>>> > Hi >>>> > I am stuck with a problem. inittab is not executing after my Linux box >>>> boots >>>> > up. >>>> > The problem in detail. I have a linux box, i load the Linux image >>>> uImage >>>> > using TFTP and my root file system is configured in NFS. After the >>>> security >>>> > key is generated, my box just waits there infinity. Its not starting a >>>> new >>>> > terminal. >>>> > The new terminal has been specified in the inittab as >>>> > ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL >>>> > Can anybody help me out with this problem? >>>> > Since i am not able to set password i cannot do a secure >>>> shell access too. >>>> >>>> If I had to guess (since you didn't include any boot logs, that's >>>> pretty much all I can do), I'd say that your NFS mount of the root >>>> file system isn't working. >>>> >>>> You can always try and see if you can even boot into a shell manually, >>>> by adding init=/bin/sh to the kernel command line. >>>> >>>> Have you tried booting without using NFS, and verifying that you can >>>> mount the NFS volume? >>>> >>>> -- >>>> Dave Hylands >>>> Shuswap, BC, Canada >>>> http://www.davehylands.com >>>> >>> >>> >>> >>> -- >>> Regards, >>> >>> Prajosh Premdas >>> >>> _______________________________________________ >>> Kernelnewbies mailing list >>> Kernelnewbies at kernelnewbies.org >>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies >>> >>> >> >> Hi Prajosh, >> >> Could you post what exact error are you getting. >> I had a very similar problem recently when trying to boot the kernel using >> tftp and then mounting the Rootfs over NFS. >> The issue I faced was that the Rootfs' /dev directory was not correctly >> populated and was missing the /dev/console device. >> >> I was getting an error on the lines of "Unable to start init console" and >> I too spent time mucking about in my inittab. >> >> >> Thanks, >> Raseel >> >> _______________________________________________ >> Kernelnewbies mailing list >> Kernelnewbies at kernelnewbies.org >> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies >> >> > > > -- > Regards, > > Prajosh Premdas > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies at kernelnewbies.org > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110621/82e079a6/attachment.html ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2011-06-21 17:32 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-06-14 17:07 inittab is not executing after my Linux box boots up Prajosh Premdas
2011-06-14 17:19 ` Dave Hylands
2011-06-14 17:22 ` Prajosh Premdas
2011-06-15 6:40 ` Raseel Bhagat
2011-06-19 15:24 ` Prajosh Premdas
2011-06-19 15:53 ` Mulyadi Santosa
2011-06-19 17:52 ` Dave Hylands
2011-06-20 6:24 ` Prajosh Premdas
[not found] ` <BANLkTikR191M+gLTYVstGiNbR3-DNa58Dw@mail.gmail.com>
[not found] ` <BANLkTi=wQ3BHUtVKXu5_UH_x7oXFKvZdJw@mail.gmail.com>
2011-06-21 8:50 ` Prajosh Premdas
2011-06-21 9:31 ` Bernd Petrovitsch
2011-06-21 17:32 ` dinesh bhaskar
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).