Uncompressing Linux.............................................................
...... done, booting the kernel.
Linux version 2.6.20 (root@localhost.localdomain) (gcc version 3.4.1) #1 Sat May
19 21:53:53 EDT 2007
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
Machine: Atmel AT91RM9200-DK
Warning: bad configuration page, trying to continue
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 179 MHz, master 59 MHz, main 18.432 MHz
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 1 zonelists. Total pages: 8128
Kernel command line: mem=32M console=ttyS0,115200 initrd=0x20410000,5242880 root
=/dev/ram0 rw
AT91: 128 gpio irqs in 4 banks
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: 32MB = 32MB total
Memory: 25192KB available (1840K code, 192K data, 96K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
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: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 1024 bind 512)
TCP reno registered
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like a
n initrd
Freeing initrd memory: 5120K
NetWinder Floating Point Emulator V0.97 (double precision)
io scheduler noop registered
io scheduler anticipatory registered (default)
at91_spi: Baud rate set to 5990400
AT91 SPI driver loaded
AT91 Watchdog Timer enabled (5 seconds, nowayout)
atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
atmel_usart.1: ttyS1 at MMIO 0xfffc4000 (irq = 7) is a ATMEL_SERIAL
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
at91_ether: Your bootloader did not configure a MAC address.
eth0: Link now 10-HalfDuplex
eth0: AT91 ethernet at 0xfefbc000 int=24 10-HalfDuplex (00:00:00:00:00:00)
eth0: Davicom 9161 PHY (Copper)
physmap platform flash device: 00200000 at 10000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
NOR chip too large to fit in mapping. Attempting to cope...
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Reducing visibility of 8192KiB chip to 2048KiB
RedBoot partition parsing not available
at91_cf: irqs det #64, io #0
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 23, io mem 0x00300000
usb usb1: Product: AT91 OHCI
usb usb1: Manufacturer: Linux 2.6.20 ohci_hcd
usb usb1: SerialNumber: at91
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
udc: at91_udc version 3 May 2006
mice: PS/2 mouse device common for all mice
at91_rtc at91_rtc: rtc core: registered at91_rtc as rtc0
AT91 Real Time Clock driver.
i2c /dev entries driver
at91_i2c at91_i2c: AT91 i2c bus driver.
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
at91_rtc at91_rtc: setting the system clock to 1998-01-01 00:01:49 (883612909)
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 5120KiB [1 disk] into ram disk... done.
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 96K
Warning: unable to open an initial console.
usb 1-2: new low speed USB device using at91_ohci and address 2
usb 1-2: device descriptor read/64, error -62
usb 1-2: device descriptor read/64, error -62
usb 1-2: new low speed USB device using at91_ohci and address 3
usb 1-2: device descriptor read/64, error -62
usb 1-2: device descriptor read/64, error -62
usb 1-2: new low speed USB device using at91_ohci and address 4
usb 1-2: device not accepting address 4, error -62
usb 1-2: new low speed USB device using at91_ohci and address 5
usb 1-2: device not accepting address 5, error -62

run to here and cannot continue ??

check to make sure you have /dev/console in your rfs.

yes, that's the most common issue, if a console device is not present in the rfs, the kernel will panic. You could also create a console device in the start-up init script by way of mknod or mdev(if using busybox) or udev. Or create the console device during the packaging of the rfs image before uploading the rfs image to the board.

I had the same problem, and to start, I created the missing console device with mknod in the script that builds my initrd. At least I was able to get to a prompt and look around the system.

I notice that '/dev' is not populated (except by the items I created with mknod); shouldn't udev have done its magic? What am I missing?

I used to use 2.4.27, and devfs would fill '/dev' for me.

Any insights would be appreciated.

Alright, so here's more info:

You must create '/sys' in your initrd/root file system, in order for sysfs to populate it. udev needs this to work, and when done, you should see a bunch of stuff in '/sys' on your next boot. You probably need '/dev' to exist for udev to do its stuff, but I'm not sure yet.

Also, if creating '/dev/console' manually (e.g. mknod), you should apparently create '/dev/null' also, though it's not strictly necessary (at least in my case).

The issue is that on the new kernels "devfs" I.E /dev is not how things are done now.

There are still some items such as console &fb etc sitting in there, but now all new stuff is added to /sys.
specifically if you look through the drivers you can see they are being converted to register inside of /sys rather than /dev

so if you have a new kernel and your startup script does something like:

if mount | grep "devfs" .......

then anything that appears after the "if" will not be put in place, as "devfs" is no longer mounted on many systems.

this includes the console & tty mapping.

Which is the case with many of the embedded products.
It's exactly the problem i'm having wih my touch screen.
the apps expect it to be in "/dev/fs" , but it is actually sitting in "/sys" under the spi tree.


Basically you have to "move" any setup that is relying on "devfs" from outside of the "if" , but don't expect doing it for everything will work.

Thanks for the reply.

Initially, I thought udev was built into the kernel, but actually it must be built separately and added to the system. I learned this by starting to read the documentation; here's a handy link to the base:
http://www.kernel.org/pub/linux/utils/k ... /udev.html

Good luck with your touchscreen system!