Bill Gatliff <[EMAIL PROTECTED]> writes: Hi,
> Riku Voipio wrote: >> On Sat, Jul 12, 2008 at 10:49:09AM -0500, Bill Gatliff wrote: >>> Anyone know of a recent kernel for the n4100? I was using the 2.6.17.8 >>> sources >>> from wpkg.org, which are a bit out of date. Is anyone else paying any >>> attention >>> to this platform? >> >> What patches does the "wpkg.org 2.6.17.8" add to the kernel? Are these >> in mainline kernels already? If they are, the -iop32x kernel should >> probably work just fine. If they are not, it should not be a big job. >> N4100 is almost identical to n2100. Similar enough that it would be >> a pity if support were lost. However, it needs someone with the actual >> hardware to make it possible. > > I just built mainline 2.6.26 with iop32x_defconfig and arm-linux-gnueabi-gcc > (GCC) 4.2.4 (Debian 4.2.4-2). Booting on my n4100, I get this: > > RedBoot> exec -c "console=ttyS0,115200 [EMAIL PROTECTED] panic=5 root=nfs > nfsroot=192.168.2.10:/exports/arm > ip=192.168.2.8:192.168.2.10:192.168.2.1:255.255.255.0:n4100:eth0:off > init=/bin/sh" > Using base address 0x00200000 and length 0x00200594 > i82544_stop > i82544_stop 0 flg 17 > Uncompressing > Linux............................................................... > ..................................................................... done, > booting the kernel. > Linux version 2.6.26 ([EMAIL PROTECTED]) (gcc version 4.2.4 (Debian 4.2.4-2)) > #9 Mon > Jul 14 11:41:31 CDT 2008 > CPU: XScale-80219 [69052e30] revision 0 (ARMv5TE), cr=0000397f > Machine: Intel IQ31244 IQ31244 ? Looks weird. I wouldn't be surprised that the vendor kept IQ31244 machine id in redboot but did some incompatible changes. > ... > scsi0 : sata_vsc > scsi1 : sata_vsc > scsi2 : sata_vsc > scsi3 : sata_vsc > ata1: SATA max UDMA/133 mmio [EMAIL PROTECTED] port 0x80080200 irq 27 > ata2: SATA max UDMA/133 mmio [EMAIL PROTECTED] port 0x80080400 irq 27 > ata3: SATA max UDMA/133 mmio [EMAIL PROTECTED] port 0x80080600 irq 27 > ata4: SATA max UDMA/133 mmio [EMAIL PROTECTED] port 0x80080800 irq 27 > ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > ata1.00: qc timeout (cmd 0x27) > ata1.00: failed to read native max address (err_mask=0x4) > ata1.00: HPA support seems broken, skipping HPA handling > ata1: failed to recover some devices, retrying in 5 secs "qc timeout" is a good sign that there's something wrong somewhere. I'm far from being a sata dev but iirc, this may be caused by things like : - wrong i/o address - wrong irq - wrong irq and i/o address It would be interesting to see a boot log or 'lspci -v' with a working kernel (in case you have it somewhere on a harddrive). One can try to find what's wrong with a working kernel source but it'll be harder to than reading a kernel boot log. Arnaud -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
