Here is the boot log for this board running 2.6.27.4-matt-4.. I
checked the kernel config and CONFIG_PATA_TS72XX=y and
CONFIG_PATA_TS7200_CF=y . I think i will try 2.6.21 TS tomorrow and
see how that goes..
RedBoot> exec -c "console=ttyAM1,115200 root=/dev/sda1"
Using base address 0x00218000 and length 0x001b1bf0
�Linux version 2.6.27.4-matt (gcc version
3.4.4 (release) (CodeSourcery ARM 2005q3-2)) #4 PREEMPT Wed Feb 11
17:14:18 CST 2009
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=40007177
Machine: Technologic Systems TS-72xx SBC
Ignoring memory bank 0xd0000000 size 8192KB
Ignoring memory bank 0xd1000000 size 8192KB
Ignoring memory bank 0xd4000000 size 8192KB
Ignoring memory bank 0xd5000000 size 8192KB
Ignoring memory bank 0xe0000000 size 8192KB
Ignoring memory bank 0xe1000000 size 8192KB
Ignoring memory bank 0xe4000000 size 8192KB
Ignoring memory bank 0xe5000000 size 8192KB
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 8 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: console=ttyAM1,115200 root=/dev/sda1
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 8MB 8MB 8MB 8MB 8MB 8MB 8MB 8MB = 64MB total
Memory: 61156KB available (3300K code, 331K 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: 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
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (extended precision)
msgmni has been set to 119
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
apb:uart2: ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA
console [ttyAM1] enabled
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:14:14:40:0f:3c
Driver 'sd' needs updating - please use bus_type methods
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-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
i2c /dev entries driver
i2c-gpio i2c-gpio.0: using pins 14 (SDA) and 15 (SCL)
Registered led device: green
Registered led device: 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=0c76, idProduct=0005
usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-3: Product: TS32MJFLASHA
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:30 UTC
(30)
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "sda1" 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)
--- In "charliem_1216" <> wrote:
>
> Hi Steve --
>
> --- In "s_ladendorf" <s_ladendorf@> wrote:
> >
> > I've banged my head enough and now I need to ask. How do I get the
> > 2.6.27.4 kernel with the matt-4 patch to recognize the CompactFlash as
> > a root partition? I can load the kernel via tftp but when I execute
> > it the kernel panics as it never finds the /dev/sda1 partition. Do I
> > need to use an initrd image with a kernel module? Can the device
> > support be monolithic and what features do I need to turn on? I did
> > use the ts7200_defconfig as my kernel config when building.
>
> Please see the thread starting here for another person currently
> trying to do this (but with the 2.6.21-TS kernel):
> http://tech.groups.yahoo.com/group/ts-7000/message/13731
>
> No feedback yet on whether it worked, but there are a few suggestions
> in there. You shouldn't _need_ an initrd; a mostly monolithic kernel
> is a good approach in an embedded system IMHO.
>
> > We have about 2 dozen of these units that were manufactured for a
> > company called JumpNode that is no longer in business. We would like
> > to use them with the 2.6 kernel but I can't get past this one last
> issue.
> >
> > I am more than willing to send one to who ever can provide a working
> > solution (you don't need to do the work - just tell me now ;-).
> >
> > They are a variation of the ts7250 with a 512 Meg CF card, dual usb,
> > eth100, modem and 128 Meg (kernel ignores 8192K 8 times - a fix for
> > that would be nice as well ;-).
>
> 128M RAM? If so, then a full dmesg listing from a 2.4-TS kernel
> booting would be helpful, so we have a known-good memory layout
> listing. The current discussion about getting Matt's 2.6.28.3 patch
> going with SPARSEMEM may help here too. It seems to be almost there.
>
> In fact posting a full 2.4-TS kernel dmesg or minicom boot log would
> probably be helpful in any case, showing any other non-standard
> features that need to be enabled in the 2.6 configs.
>
> regards, ......... Charlie
>
> >
> > steve.ladendorf at spanlink.com if anyone is interested.
> >
> > Thanks!
> >
>
------------------------------------
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/
|