Glomation
 
Advanced Search
Welcome, Guest. Please login or register.

Login with username, password and session length
May 22, 2012, 04:02:27 AM
News: Glomation introduces new GECM-9G25 SODIMM system on module
Pages: [1]
Topic Tools  
Read October 29, 2010, 11:07:38 PM #0
jagan

Debian root filesystem

Hi,
I am working on GESBC-9260. I have downloaded linux-2.6.25 kernel, the patch from "www.maxim.org.za/at91_26.html", the kernel configuration from "www.at91.com/linux4sam/bin/view/Linux4SAM/LinuxKernel" and Debian based file system from Glomation website. I have extracted Debian as the root filesystem and changed the bootargs to "console=ttyS0,115200 root=/dev/nfs nfsroot=192.168.2.102:/home/jagan/9260/rootfs ip=192.168.2.167::192.168.2.1:255.255.255.0:eth0 init=/bin/init". I build the kernel, downloaded the uImage via u-boot (at 0x21800000) and able to boot. But when Debian is mounted, it is taking a long time (I mean, few minutes) to get the GESBC shell. Following is the boot process:

RomBOOT
>

U-Boot 1.3.3 (Jan  7 2010 - 12:36:50)

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: 0x45e1)
Hit any key to stop autoboot:  3  0
U-Boot>
U-Boot>
U-Boot> tftp 0x21800000 uImage9260
macb0: link up, 100Mbps full-duplex (lpa: 0x45e1)
Using macb0 device
TFTP from server 192.168.2.102; our IP address is 192.168.2.167
Filename 'uImage9260'.
Load address: 0x21800000
Loading: *#################################################################
    #################################################################
    #################################################################
    #################################################################
    #############################
done
Bytes transferred = 1479644 (1693dc hex)
U-Boot> bootm 0x21800000
## Booting kernel from Legacy Image at 21800000 ...
   Image Name:   linux-2.6
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1479580 Bytes =  1.4 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.25 (jagan@BEATLES) (gcc version 4.2.0 20070413 (prerelease) (CodeSourcery Sourcery G++ Lite 2007q1-10)) #3 Thu Oct 28 15:09:02 IST 2010
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Kernel compiled by JAGAN
Machine: Atmel AT91SAM9260-EK
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 198 MHz, master 99 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: console=ttyS0,115200 root=/dev/nfs rw nfsroot=192.168.2.102:/home/jagan/9260/rootfs,nolock ip=192.168.2.167:192.168.2.102:192.168.2.1:255.255.255.0:f175::off
AT91: 96 gpio irqs in 3 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
console [ttyS0] enabled
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: 61824KB available (2740K code, 224K data, 120K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 152 bytes
NET: Registered protocol family 16
AT91: Power Management
AT91: Starting after software reset
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 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
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory 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
ssc ssc.0: Atmel SSC device at 0xc4870000 (irq 14)
MACB_mii_bus: probed
eth0: Atmel MACB at 0xfffc4000 irq 21 (00:0e:20:02:0a:5b)
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, irq=-1)
Driver 'sd' needs updating - please use bus_type methods
NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)
AT91 NAND: 8-bit, Software ECC
Scanning device for bad blocks
Bad eraseblock 316 at 0x02780000
Bad eraseblock 320 at 0x02800000
Bad eraseblock 322 at 0x02840000
Bad eraseblock 695 at 0x056e0000
Bad eraseblock 989 at 0x07ba0000
Bad eraseblock 1160 at 0x09100000
Bad eraseblock 1481 at 0x0b920000
Bad eraseblock 1774 at 0x0ddc0000
Creating 2 MTD partitions on "at91_nand":
0x00000000-0x00040000 : "Partition 1"
0x00040000-0x10000000 : "Partition 2"
atmel_spi atmel_spi.1: Atmel SPI Controller at 0xfffcc000 (irq 13)
usbmon: debugfs is not available
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
usb usb1: configuration #1 chosen from 1 choice
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 /class/input/input0
rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0
rtc-at91sam9 at91_rtt.0: rtc0: SET TIME!
Registered led device: ds5
Registered led device: ds1
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.16rc2 (Thu Jan 31 16:40:16 2008 UTC).
at73c213 spi1.0: at73c213: supported bitrate is 48500 (64 divider)
ALSA device list:
  #0: AT91SAM9260-EK external DAC on irq 14
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock
IP-Config: Complete:
     device=eth0, addr=192.168.2.167, mask=255.255.255.0, gw=192.168.2.1,
     host=f175, domain=, nis-domain=(none),
     bootserver=192.168.2.102, rootserver=192.168.2.102, rootpath=
Looking up port of RPC 100003/2 on 192.168.2.102
eth0: link up (100/Full)
Looking up port of RPC 100005/1 on 192.168.2.102
VFS: Mounted root (nfs filesystem).
Freeing init memory: 120K
INIT: version 2.86 booting
Activating swap...done.
Setting the system clock..
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
Cleaning up ifupdown....
Loading kernel modules...done.
Loading device-mapper support.
Checking file systems...fsck 1.40-WIP (14-Nov-2006)
WARNING: Your /etc/fstab does not contain the fsck passno
   field.  I will kludge around things for you, but you
   should fix your /etc/fstab file as soon as you can.

done.
Setting kernel variables...done.
Mounting local filesystems...done.
Activating swapfile swap...done.
rm: cannot remove `./crond.pid': Read-only file system
rm: cannot remove `./sshd.pid': Read-only file system
rm: cannot remove `./crond.reboot': Read-only file system
rm: cannot remove `./motd': Read-only file system
* bootclean: Failure cleaning /var/run.
/etc/init.d/bootclean: line 24: /var/lock/.clean: Read-only file system
* bootclean: Failure creating '/var/lock/.clean'.
Setting up networking....
Configuring network interfaces...SIOCADDRT: File exists
Failed to bring up eth0.
done.
Starting thttpd server
rm: cannot remove `./crond.pid': Read-only file system
rm: cannot remove `./sshd.pid': Read-only file system
rm: cannot remove `./crond.reboot': Read-only file system
rm: cannot remove `./motd': Read-only file system
* bootclean: Failure cleaning /var/run.
/etc/init.d/bootclean: line 24: /var/lock/.clean: Read-only file system
* bootclean: Failure creating '/var/lock/.clean'.
/etc/rcS.d/S55bootmisc.sh: line 28: /var/run/utmp: Read-only file system
INIT: Entering runlevel: 2
Starting system log daemon: syslogdchmod: changing permissions of `/dev/xconsole': Read-only file system
chown: changing ownership of `/dev/xconsole': Read-only file system
.
Starting kernel log daemon: klogd.
Starting internet superserver: inetd.
Starting OpenBSD Secure Shell server: sshdPRNG is not seeded
Starting periodic command scheduler: crond.

Debian GNU/Linux 4.0 GESBC console

GESBC login:


The booting process is halting for a long period at the step:

chown: changing ownership of `/dev/xconsole': Read-only file system


Can anyone tell me, what was the issue? What changes need to be done with /etc/init.d/rcS script?

Also, let me know, how to extract ' 9260rootfs.img'? I tried by making RAM Disk image, but could not. Can anyone tell me the steps in-detail?

Thanks & regards,
Jagan
 
Read November 01, 2010, 08:51:16 PM #1
admin

Re: Debian root filesystem

It appears that you are using a NFS.  There are several messages indicating the file system was read only.  Maybe the NFS export was not set correctly.  Also the network traffic can contribute to the amount of the time the system needs to boot to the login prompt.
 
Read November 03, 2010, 10:58:17 PM #2
jagan

Re: Debian root filesystem

It appears that you are using a NFS.  There are several messages indicating the file system was read only.  Maybe the NFS export was not set correctly.  Also the network traffic can contribute to the amount of the time the system needs to boot to the login prompt.

The rootfs was not having write permissions, and it is solved. Thanks a lot. Now, booting is proper.
But it is asking for 'username' and the user is 'root'. How to skip this and get the shell as root user?

Apart from this, can you please provide me the steps to use ' 9260rootfs.img' as my root fs? I tried by making RAM Disk image, but could not. Can you please give steps in-detail?
thanks & regards,
Jagan
 
Read November 04, 2010, 11:16:37 AM #3
admin

Re: Debian root filesystem

The /etc/inittab file can be modified to run different programs on the serial line.  Or use -l option for the getty to run a different login program.

The basic steps to extract JFFS2 image are,

1) create a RAM disk
2) copy JFFS2 image to RAM disk with raw copy
3) mount the RAM disk as a JFFS2 disk

The RAM disk then is ready to be accessed.

 
Read November 08, 2010, 07:54:29 AM #4
brady

Re: Debian root filesystem

Apart from this, can you please provide me the steps to use ' 9260rootfs.img' as my root fs? I tried by making RAM Disk image, but could not. Can you please give steps in-detail?

Jagan,

To use the 9260rootfs.img as the root file system you just need to write it to flash memory.  The procedure for doing this is described in the users manual (found here).

-B.
 
Pages: [1]
Jump to:  

Theme Update by Runic Warrior Originally created by m3talc0re