Re: [Ltib] Old uImage Won't Boot (Rebuilt from scratch)

[Stuart Hughes]

Hi Carolyn,

Glad it's working.

You must have had access to the Freescale BSP for the old kernel build,
as not all the patches are public (yet).

You can check rootfs/boot/linux.config to see if that configuration at
least had the appropriate option built.  At run time I'm not sure.
Really a question for Freescale.

Regards, Stuart


Reer, Carolyn (SA-1) wrote:
> I gave up trying to reload the old kernel uImage.
> I created a clean rootfs directory and started from scratch.
> The 1st time I built (2 hours), I had 33 unbuilt pkgs including the kernel.
> I built a 2nd time (90 minutes), I had 14 unbuilt pkgs but I had a kernel.
> Copied all the files in ./ltib/rootfs/boot to backup and /tftpboot and it 
> boots. Hoorah!
> I copied the boot log for future reference.
> 
> Next question: I am building with mpc8536ds_ipsec_sec_offloading.config.
> How do I verify the offload engine is enabled?
> I am going to run my iSCSI throughput tests now to see if there is any change.
> 
> Thanks for all your help. 
> 
> Carolyn Reer
> 
> 
> 
> -----Original Message-----
> From: address@hidden [mailto:address@hidden On Behalf Of Peter Barada
> Sent: Tuesday, November 09, 2010 12:26 AM
> To: address@hidden
> Subject: Re: [Ltib] Old uImage Won't Boot
> 
> On 11/08/2010 06:57 PM, Reer, Carolyn (SA-1) wrote:
>> Hi Stuart:
>> I don't have immediate access to another Linux machine to try mounting the 
>> NFS. Will try later.
>>
>> I cleaned out the /var/log/messages file and reran the boot. But no messages.
>> How do I log the LTIB process?
>> How do I log the boot process?
>>    
> At least for building LTIB, you can "./ltib 2>&1 | tee 
> /tmp/ltib-build.log" to capture the output from the build process.
> For the boot process, your terminal emulator that you connect to the 
> board's serial console should have a logging option to capture output 
> from the board...
> 
>> I usually go back and copy and paste all the lines I can grab
>>
>> PS: I started building the image fresh with a new 
>> /home/mpc8536ds/ltib/rootfs directory.
>> Cd /home/mpc8536ds/ltib
>> ./ ltib --configure --continue
>> After 2 hours LTIB failed to build 33 pkgs including the kernel.
>>
>> I had removed 'gcc' from the pkgs list because that ALWAYS fails to build.
>> I restored all the previous defaults, except I have Ipsec Offload Engine 
>> selected, and build NFS only.
>>
>> Carolyn Reer
>>
>> -----Original Message-----
>> From: address@hidden [mailto:address@hidden
>> Sent: Monday, November 08, 2010 11:44 AM
>> To: Reer, Carolyn (SA-1)
>> Cc: address@hidden
>> Subject: RE: [Ltib] Old uImage Won't Boot
>>
>> Hi Carolyn,
>>
>> Look on the nfsserver in /var/log/messages (or ??) to see if it has
>> anything helpful in there.
>>
>> Also, try on another machine (not the target) to nfs mount that directory
>> and then as root try creating a file.  This should prove whether or not
>> the nfs export is working as it should.
>>
>> Regards, Stuart
>>
>>
>>    
>>> Hi Stuart:
>>> My host /etc/exports file is:
>>> /tftpboot/ltib 192.168.1.100(rw,no_root_squash,sync)
>>>
>>> /tftpboot/ltib is a link to the root file system
>>> /tftpboot/ltib ->  /home/vrams/mpc8536ds/ltib/rootfs
>>>
>>> I also changed /home/vrams/mpc8536ds/ltib/rootfs/etc/exports file to:
>>> /tftpboot/ltib 192.168.1.100(rw,no_root_squash,sync)
>>>
>>> But that didn't help
>>> ******************************************************************
>>> Here's another clue:
>>> When I don't explicitly define console&  null in my rootfs/dev, it gives
>>> up immediately. Can't open console?
>>> IP-Config: Complete:
>>>       device=eth0, addr=192.168.1.100, mask=255.255.255.0, gw=192.168.1.1,
>>>       host=mpc8536ds, domain=, nis-domain=(none),
>>>       bootserver=192.168.1.1, rootserver=192.168.1.1, rootpath=
>>> Looking up port of RPC 100003/2 on 192.168.1.1
>>> PHY: address@hidden:01 - Link is Up - 1000/Full
>>> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>>> Looking up port of RPC 100005/1 on 192.168.1.1
>>> VFS: Mounted root (nfs filesystem).
>>> Freeing unused kernel memory: 188k init
>>> Warning: unable to open an initial console.<-------This is different
>>> init has generated signal 4 but has no handler for it
>>> Kernel panic - not syncing: Attempted to kill init!
>>> Rebooting in 180 seconds..<7>eth0: no IPv6 routers present
>>> *****************************************************************
>>> When I explicitly define console&  null in my rootfs/dev, it tries to
>>> mount devices but can't:
>>> Cd /home/vrams/mpc8536ds/ltib/rootfs/dev
>>> mknod -m 660 console c 5 1
>>> mknod -m 660 null c 1 3
>>>
>>> IP-Config: Complete:
>>>       device=eth0, addr=192.168.1.100, mask=255.255.255.0, gw=192.168.1.1,
>>>       host=mpc8536ds, domain=, nis-domain=(none),
>>>       bootserver=192.168.1.1, rootserver=192.168.1.1, rootpath=
>>> Looking up port of RPC 100003/2 on 192.168.1.1
>>> PHY: address@hidden:01 - Link is Up - 1000/Full
>>> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>>> Looking up port of RPC 100005/1 on 192.168.1.1
>>> VFS: Mounted root (nfs filesystem).
>>> Freeing unused kernel memory: 188k init
>>> Mounting /proc and /sys<-------This is different
>>> mount: permission denied. (are you root?)
>>> mount: permission denied. (are you root?)
>>> /etc/rc.d/init.d/udev: line 11: /proc/sys/kernel/hotplug: No such file or
>>> directory
>>> mount: permission denied. (are you root?)
>>> mknod: `/dev/console': File exists
>>> mknod: `/dev/null': File exists
>>> Starting the hotplug events dispatcher udevd
>>> udevd[1181]: main: error disabling OOM: No such file or directory
>>> Synthesizing initial hotplug events
>>> mkdir: cannot create directory `/dev/pts': File exists
>>> mount: permission denied. (are you root?)
>>> mkdir: cannot create directory `/dev/shm': File exists
>>> Setting the hostname to mpc8536ds
>>> Mounting filesystems
>>> mount: permission denied. (are you root?)
>>> mount: permission denied. (are you root?)
>>> mount: permission denied. (are you root?)
>>> cat: /proc/cmdline: No such file or directory
>>> ln: creating symbolic link `/etc/mtab': File exists
>>> mount: permission denied. (are you root?)
>>> Starting syslogd and klogd
>>> Running sysctl
>>> Setting up networking on loopback device:
>>> Setting up networking on eth0:
>>> Adding static route for default gateway to 192.168.1.1:
>>> SIOCADDRT: File exists
>>> Setting nameserver to 192.168.1.1 in /etc/resolv.conf:
>>> Setting up networking on eth1:
>>> ADDRCONF(NETDEV_UP): eth1: link is not ready
>>> Adding static route for default gateway to 192.168.1.1:
>>> Setting nameserver to 192.168.1.1 in /etc/resolv.conf:
>>> Starting inetd:
>>> Starting the port mapper:
>>> Setting time from ntp server:
>>> /bin/ntpclient: option requires an argument -- 'h'
>>> Usage: /bin/ntpclient [-c count] [-d] [-g goodness] -h hostname [-i
>>> interval]
>>>          [-l] [-p port] [-r] [-s]
>>> cat: /proc/devices: No such file or directory
>>>
>>> Carolyn Reer
>>>
>>> -----Original Message-----
>>> From: Stuart Hughes [mailto:address@hidden
>>> Sent: Sunday, November 07, 2010 6:27 AM
>>> To: Reer, Carolyn (SA-1)
>>> Cc: address@hidden
>>> Subject: Re: [Ltib] Old uImage Won't Boot
>>>
>>> Hi Carolyn,
>>>
>>> Make sure you have the right export permissions on your NFS server.  For
>>> example, make sure you have no_root_squash listed in the options.
>>>
>>> You can verify this independently by mounting the rootfs on some other
>>> machine and trying to touch a file somewhere on that filesystem.
>>>
>>> Regards, Stuart
>>>
>>>
>>>
>>> Reer, Carolyn (SA-1) wrote:
>>>      
>>>> I am trying to boot my baseline uImage&  dtb built (dated 22-Jul-2010)
>>>> using
>>>>
>>>> LTIB dated 13-Mar-2009 for
>>>>
>>>> Freescale MPC8536DS
>>>>
>>>> Linux 2.6.28 for PPC
>>>>
>>>>
>>>>
>>>> I have attached the log from the bootloader.
>>>>
>>>>
>>>>
>>>> It won’t boot any more. Wondering if I messed up the file system
>>>> somehow.
>>>>
>>>>
>>>>
>>>> During the boot process every mount fails after NFS filesystem mounted:
>>>>
>>>> mount: permission denied. (are you root?)
>>>>
>>>>
>>>>
>>>> All files are at the user level, not root.
>>>>
>>>> Could I have copied the directory incorrectly?
>>>>
>>>> How do I fix?
>>>>
>>>>
>>>>
>>>> Thanks. This is my baseline and it doesn’t work!
>>>>
>>>>
>>>>
>>>> *Carolyn Reer*
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> LTIB home page: http://ltib.org
>>>>
>>>> Ltib mailing list
>>>> address@hidden
>>>> http://lists.nongnu.org/mailman/listinfo/ltib
>>>>        
>>>      
>>    
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> LTIB home page: http://ltib.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib