logicpd zoom dev kit and archlinux arm (help?)

[davini]

I am using a Zoom™ DM3730 Torpedo Development Kit which has a DM3730 / AM3703 Torpedo + Wireless SOM.

I have Archlinux ARM booting from an SD Card with two partitions: boot and rootfs. The boot partition contains the uImage, and boot.src (although, I am aware how this is generated) from the downloads sections along with a custom uboot compile using the omap3_logic (machine id 2178). The rootfs partition contains the root file system from the downloads section. This setup is basically the same as the Beagleboard-xM expect I had to change the uboot to pass the correct machineid into the kernel. Anyways, here is my log just when the kernal is botting:

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 0.282348] _omap_mux_get_by_name: Could not find signal uart4_rx.uart4_rx
[ 0.289306] dpll3_m2_clk rate change failed: -22
[ 0.290863] Could not look up dss_hdmi hw_mod
[ 0.291046] Could not look up dmic hw_mod
[ 0.291046] Could not look up mcpdm hw_mod
[ 0.325561] musb-omap2430 musb-omap2430: invalid resource
[ 0.338714] musb-omap2430 musb-omap2430: musb core is not yet ready
[ 1.974761] irq 243: nobody cared (try booting with the "irqpoll" option)
[ 1.982727] handlers:
[ 1.985137] [<c042f2a4>] smsc911x_irqhandler
[ 1.989624] Disabling IRQ #243
[ 2.005645] twl4030_wdt twl4030_wdt: Failed to register misc device
[ 2.428771] omapfb omapfb: no displays
[ 2.432769] omapfb omapfb: failed to setup omapfb
[ 2.437957] failed to register omapfb driver

Welcome to Arch Linux ARM!

Expecting device dev-ttyO0.device...
[ OK ] Reached target Remote File Systems.
Expecting device sys-subsystem-net-devices-eth0.device...
[ OK ] Listening on Delayed Shutdown Socket.
[ OK ] Listening on LVM2 metadata daemon socket.
[ OK ] Listening on Device-mapper event daemon FIFOs.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ OK ] Created slice Root Slice.
[ OK ] Created slice User and Session Slice.
[ OK ] Created slice System Slice.
[ OK ] Created slice system-netctl\x2difplugd.slice.
[ OK ] Created slice system-getty.slice.
[ OK ] Created slice system-serial\x2dgetty.slice.
[ OK ] Reached target Slices.
[ OK ] Reached target Encrypted Volumes.
[ OK ] Set up automount Arbitrary Executable File Formats F...utomount Point.
[ OK ] Reached target Paths.
[ OK ] Listening on udev Kernel Socket.
[ OK ] Listening on udev Control Socket.
[ OK ] Listening on Journal Socket.
Starting udev Coldplug all Devices...
Mounting Debug File System...
Mounting FUSE Control File System...
Mounting POSIX Message Queue File System...
Starting Create list of required static device nodes...rrent kernel...
Starting Setup Virtual Console...
Starting Journal Service...
[ OK ] Started Journal Service.
Starting Apply Kernel Variables...
Mounting Configuration File System...
[ OK ] Reached target Swap.
Mounting Temporary Directory...
Starting Remount Root and Kernel File Systems...
[ OK ] Mounted Debug File System.
[ OK ] Mounted FUSE Control File System.
[ OK ] Mounted POSIX Message Queue File System.
[ OK ] Started Setup Virtual Console.
[ OK ] Started Apply Kernel Variables.
[ OK ] Mounted Configuration File System.
[ OK ] Mounted Temporary Directory.
[ OK ] Started Remount Root and Kernel File Systems.
[ OK ] Started udev Coldplug all Devices.
[ OK ] Started Create list of required static device nodes ...current kernel.
Starting Create static device nodes in /dev...
Starting Load/Save Random Seed...
[ OK ] Started Create static device nodes in /dev.
Starting udev Kernel Device Manager...
[ OK ] Reached target Local File Systems (Pre).
[ OK ] Reached target Local File Systems.
Starting Trigger Flushing of Journal to Persistent Storage...
Starting Recreate Volatile Files and Directories...
[ OK ] Started udev Kernel Device Manager.
[ OK ] Started Load/Save Random Seed.
[ OK ] Started Recreate Volatile Files and Directories.
Starting Update UTMP about System Reboot/Shutdown...
[ OK ] Started Trigger Flushing of Journal to Persistent Storage.
[ OK ] Started Update UTMP about System Reboot/Shutdown.
[ OK ] Reached target System Initialization.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Timers.
[ OK ] Reached target Basic System.
Starting Entropy Harvesting Daemon...
Starting SSH Key Generation...
Starting Login Service...
Starting D-Bus System Message Bus...
[ OK ] Started D-Bus System Message Bus.
Starting Permit User Sessions...
[ OK ] Found device /dev/ttyO0.
[ OK ] Started Entropy Harvesting Daemon.
[ OK ] Started Permit User Sessions.
Starting Getty on tty1...
[ OK ] Started Getty on tty1.
Starting Serial Getty on ttyO0...
[ OK ] Started Serial Getty on ttyO0.
[ OK ] Reached target Login Prompts.
[ OK ] Started Login Service.
[ OK ] Found device /sys/subsystem/net/devices/eth0.
Starting Automatic wired network connection using netctl profiles...
[ OK ] Started Automatic wired network connection using netctl profiles.

Arch Linux 3.7.10-9-ARCH (ttyO0)

alarm login:

This is great, expect the ethernet control's interrupt is being disabled:
...
[ 1.974761] irq 243: nobody cared (try booting with the "irqpoll" option)
[ 1.982727] handlers:
[ 1.985137] [<c042f2a4>] smsc911x_irqhandler
[ 1.989624] Disabling IRQ #243
...
Does anyone know why this is happening or how to correct it? Aside from the other errors, this one is the most important one to correct (for now). I believe the setup is the same as the Beagleboard, which I have been able to get working using the guide. I'm sort of new when it comes to kernel level debugging (specially on an embedded environment such as the ARM7). Any help at all would be much appreciated. Thanks.

[davini]

Okay, maybe this might be more informative. I set a static ip in the wired connection and pinged the router, I got this:
...
[root@alarm ~]# ping 192.168.20.1
PING 192.168.20.1 (192.168.20.1) 56(84) bytes of data.
64 bytes from 192.168.20.1: icmp_seq=1 ttl=64 time=162 ms
64 bytes from 192.168.20.1: icmp_seq=2 ttl=64 time=4.88 ms
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available

--- 192.168.20.1 ping statistics ---
12 packets transmitted, 2 received, 83% packet loss, time 30069ms
rtt min/avg/max/mdev = 4.883/83.923/162.964/79.041 ms
[root@alarm ~]#
...
I hit ctrl-c after ~10 seconds of not receiving a response. I read on some forums that this might be due to an unsupported driver. If this is the case, what do I do? Those forums were not helpful.