--- In "chris.gurtler" <> wrote:
>
> Hi,
>
> Sorry for all of these messages, but I think I'm close.
Cool, looks like you are close.
> I'm trying to compile the 2.6 kernel for the TS7250 and I'm
getting a
> kernel panic when it loads up. I get a "No NFS server available"
> message that I'm not sure about. I've attached the output at
startup,
> does anyone know what the problem would be?
Well, depends on whether you are trying to use a rootfs on your
Fedora box served by NFS, or if you are trying to use your existing
rootfs on flash. I guess the latter ...
>
> RedBoot> fis load vmlinux
> RedBoot> exec -c "console=ttyAM0,115200 root=/dev/mtdblock1"
> Using base address 0x00218000 and length 0x00160000
> Uncompressing
>
Linux....................................................................................................................
> done, booting the kernel.
> Linux version 2.6.27.4-matt (gcc version 4.0.1)
#2
> PREEMPT Thu Nov 27 10:28:56 EST 2008
> CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=40007177
> Machine: Technologic Systems TS-72xx SBC
> Memory policy: ECC disabled, Data cache writeback
> CPU0: D VIVT write-back cache
> CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8
sets
> CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8
sets
> Built 4 zonelists in Zone order, mobility grouping on. Total
pages: 8128
> Kernel command line: console=ttyAM0,115200 root=/dev/mtdblock1
> PID hash table entries: 128 (order: 7, 512 bytes)
> Console: colour dummy device 80x30
> Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
> Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> Memory: 8MB 8MB 8MB 8MB = 32MB total
> Memory: 28692KB available (3284K code, 339K data, 116K init)
> Calibrating delay loop... 99.73 BogoMIPS (lpj=498688)
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> net_namespace: 592 bytes
> NET: Registered protocol family 16
> ep93xx: PLL1 running at 400 MHz, PLL2 at 192 MHz
> ep93xx: FCLK 200 MHz, HCLK 100 MHz, PCLK 50 MHz
> 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: 1024 (order: 1, 8192 bytes)
> TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
> TCP: Hash tables configured (established 1024 bind 1024)
> TCP reno registered
> NET: Registered protocol family 1
> NetWinder Floating Point Emulator V0.97 (extended precision)
> msgmni has been set to 56
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> Serial: 8250/16550 driver2 ports, IRQ sharing disabled
> Serial: AMBA driver
> apb:uart1: ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA
> console [ttyAM0] enabled
> apb:uart2: ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA
> apb:uart3: ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA
> ep93xx-eth version 0.1 loading
> ep93xx_mii_bus: probed
> Generic PHY 0:01: PHY supports MII frame preamble suppression
> net eth0: attached PHY driver [Generic PHY]
(mii_bus:phy_addr=0:01,
> irq=-1)
> net eth0: ep93xx on-chip ethernet, IRQ 39, 00:d0:69:4f:34:a5
> Driver 'sd' needs updating - please use bus_type methods
> TS-7200 flash mapping: 0x800000 at 0x60000000
Here you should be seeing a message about yaffs. Yaffs is used on
the 7250 (NAND flash) while jffs is used on the 7200 (NOR flash).
So you need to add yaffs (and the NAND driver I think) when you
configure the kernel.
(If you have more than 128M flash, then you have NAND-2k, which
means you need to use yaffs2. Unfortunately that's not in the
vanilla kernel tree, and I don't know if it's in the patch set
you're using. It is available though).
A snip of my 7250 bootlog, for reference: (not sure what's up with
the 'bad erase block's ...)
Searching for NAND flash...
[ 1.260000] NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1
(Samsung NAND 128MiB 3,3V 8-bit)
[ 1.270000] Scanning device for bad blocks
[ 1.280000] Bad eraseblock 0 at 0x00000000
[ 1.280000] Bad eraseblock 1 at 0x00020000
[ 1.340000] Bad eraseblock 1009 at 0x07e20000
[ 1.340000] Bad eraseblock 1010 at 0x07e40000
[ 1.350000] Bad eraseblock 1011 at 0x07e60000
[ 1.350000] Bad eraseblock 1012 at 0x07e80000
[ 1.360000] Using static partition definition
[ 1.360000] Creating 3 MTD partitions on "ts7250-nand":
[ 1.370000] 0x00000000-0x00020000 : "TS-BOOTROM"
[ 1.380000] 0x00020000-0x07d20000 : "Linux"
[ 1.400000] 0x07d20000-0x08000000 : "RedBoot"
> GPIO-18 autorequested
> usbmon: debugfs is not available
> ep93xx-ohci ep93xx-ohci: EP93xx OHCI
> ep93xx-ohci ep93xx-ohci: new USB bus registered, assigned bus
number 1
> ep93xx-ohci ep93xx-ohci: irq 56, io mem 0x80020000
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 3 ports detected
> usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
> usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> usb usb1: Product: EP93xx OHCI
> usb usb1: Manufacturer: Linux 2.6.27.4-matt ohci_hcd
> usb usb1: SerialNumber: ep93xx
> mice: PS/2 mouse device common for all mice
> ep93xx_keypad: platform driver v2.0
> ep93xx-rtc ep93xx-rtc: rtc core: registered ep93xx as rtc0
> rtc-m48t86 rtc-m48t86: rtc core: registered m48t86 as rtc1
> rtc-m48t86 rtc-m48t86: battery ok
IIRC, (when you eventually do boot) your rootfs will look only for
rtc, and will have trouble using the multiple rtc0, rtc1, etc.
Solve this by linking /dev/rtc to /dev/rtc0. Not pretty, but it
works.
> i2c /dev entries driver
> GPIO-15 autorequested
> GPIO-14 autorequested
> GPIO-32 autorequested
> GPIO-33 autorequested
> Registered led device: ep93xx:green
> Registered led device: ep93xx:red
> usb 1-3: new full speed USB device using ep93xx-ohci and address 2
> usb 1-3: configuration #1 chosen from 1 choice
> usb 1-3: New USB device found, idVendor=1307, idProduct=0165
> usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 1-3: Product: USB Flash Drive
> usb 1-3: Manufacturer: USB 2.0
> usb 1-3: SerialNumber: bc1712b4041764
> usbcore: registered new interface driver usbhid
> usbhid: v2.6:USB HID core driver
> IPv4 over IPv4 tunneling driver
> TCP cubic registered
> NET: Registered protocol family 17
> NET: Registered protocol family 15
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> ep93xx-rtc ep93xx-rtc: setting system clock to 1970-01-01 00:00:10
UTC
Do you have the RTC hardware option? If not, disregard my comment
above :)
> (10)
> Root-NFS: No NFS server available, giving up.
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device "mtdblock1" or unknown-block(2,0)
> Please append a correct "root=" boot option; here are the
available
> partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(2,0)
You're getting close. For debugging the yaffs stuff & basic
performance testing, you might consider serving a rootfs from your
fedora box by NFS. If you do, then follow the command line exec
examples Andrew posted. for NFS root booting
Regards, ....... Charlie
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|