Re: Newer kernel for N4100?
Riku Voipio wrote:
> On Mon, Jul 14, 2008 at 12:35:21PM -0500, Bill Gatliff wrote:
>> 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 mem=256M@0xa0000000 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 (bgat@mercury) (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
>
> Thats probable the wrong machine. Try prependig the N2100 machine-id
> for fixups.
>
> devio > vmlinuz 'wl 0xe3a01c04,4' 'wl 0xe381104d,4'
> cat arch/arm/boot/zImage >> vmlinuz
Finally got around to trying this out (it's been a rough summer), this time on
2.6.27-rc5. It definitely changes things:
...
scsi0 : sata_vsc
scsi1 : sata_vsc
scsi2 : sata_vsc
scsi3 : sata_vsc
ata1: SATA max UDMA/133 mmio m4096@0x80080000 port 0x80080200 irq 29
ata2: SATA max UDMA/133 mmio m4096@0x80080000 port 0x80080400 irq 29
ata3: SATA max UDMA/133 mmio m4096@0x80080000 port 0x80080600 irq 29
ata4: SATA max UDMA/133 mmio m4096@0x80080000 port 0x80080800 irq 29
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-6: WDC WD3000JD-00KLB0, 08.05J08, max UDMA/100
ata1.00: 586072368 sectors, multi 0: LBA48
ata1.00: configured for UDMA/100
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATA-6: WDC WD3000JD-00KLB0, 08.05J08, max UDMA/100
ata2.00: 586072368 sectors, multi 0: LBA48
ata2.00: configured for UDMA/100
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: ATA-6: WDC WD3000JD-00KLB0, 08.05J08, max UDMA/100
ata3.00: 586072368 sectors, multi 0: LBA48
ata3.00: configured for UDMA/100
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: ATA-6: WDC WD3000JD-00KLB0, 08.05J08, max UDMA/100
ata4.00: 586072368 sectors, multi 0: LBA48
ata4.00: configured for UDMA/100
scsi 0:0:0:0: Direct-Access ATA WDC WD3000JD-00K 08.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 586072368 512-byte hardware sectors (300069 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO
or FUA
sd 0:0:0:0: [sda] 586072368 512-byte hardware sectors (300069 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO
or FUA
sda: sda1 sda2
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:0: Direct-Access ATA WDC WD3000JD-00K 08.0 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 586072368 512-byte hardware sectors (300069 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO
or FUA
sd 1:0:0:0: [sdb] 586072368 512-byte hardware sectors (300069 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO
or FUA
sdb: sdb1 sdb2
sd 1:0:0:0: [sdb] Attached SCSI disk
sd 1:0:0:0: Attached scsi generic sg1 type 0
scsi 2:0:0:0: Direct-Access ATA WDC WD3000JD-00K 08.0 PQ: 0 ANSI: 5
sd 2:0:0:0: [sdc] 586072368 512-byte hardware sectors (300069 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO
or FUA
sd 2:0:0:0: [sdc] 586072368 512-byte hardware sectors (300069 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO
or FUA
sdc: sdc1 sdc2
sd 2:0:0:0: [sdc] Attached SCSI disk
sd 2:0:0:0: Attached scsi generic sg2 type 0
scsi 3:0:0:0: Direct-Access ATA WDC WD3000JD-00K 08.0 PQ: 0 ANSI: 5
sd 3:0:0:0: [sdd] 586072368 512-byte hardware sectors (300069 MB)
sd 3:0:0:0: [sdd] Write Protect is off
sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO
or FUA
sd 3:0:0:0: [sdd] 586072368 512-byte hardware sectors (300069 MB)
sd 3:0:0:0: [sdd] Write Protect is off
sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO
or FUA
sdd: sdd1 sdd2
sd 3:0:0:0: [sdd] Attached SCSI disk
sd 3:0:0:0: Attached scsi generic sg3 type 0
physmap platform flash device: 01000000 at f0000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
cmdlinepart partition parsing not available
Searching for RedBoot partition table in physmap-flash.0 at offset 0xfe0000
7 RedBoot partitions found on MTD device physmap-flash.0
Creating 7 MTD partitions on "physmap-flash.0":
0x00000000-0x00040000 : "RedBoot"
0x00040000-0x001c0000 : "zImage"
0x001c0000-0x00d40000 : "unallocated"
0x00d40000-0x00ea0000 : "kernel"
0x00ea0000-0x00fc0000 : "unallocated"
0x00fc0000-0x00fc1000 : "RedBoot config"
0x00fe0000-0x01000000 : "FIS directory"
usbmon: debugfs is not available
USB Universal Host Controller Interface driver v3.0
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
rtc-rs5c372 0-0032: rs5c372b found, 24hr, driver version 0.5
rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
raid6: int32x1 55 MB/s
raid6: int32x2 52 MB/s
raid6: int32x4 50 MB/s
raid6: int32x8 42 MB/s
raid6: using algorithm int32x1 (55 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com
iop-adma iop-adma.0: Intel(R) IOP: ( cpy intr )
iop-adma iop-adma.1: Intel(R) IOP: ( cpy intr )
TCP cubic registered
NET: Registered protocol family 10
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
XScale DSP coprocessor detected.
rtc-rs5c372 0-0032: setting system clock to 2038-09-09 12:47:59 UTC (2167649279)
IP-Config: Failed to open eth0
IP-Config: Device `eth0' not found.
md: Autodetecting RAID arrays.
md: Scanned 4 and added 4 devices.
md: autorun ...
md: considering sdd2 ...
md: adding sdd2 ...
md: adding sdc2 ...
md: adding sdb2 ...
md: adding sda2 ...
md: created md0
md: bind<sda2>
md: bind<sdb2>
md: bind<sdc2>
md: bind<sdd2>
md: running: <sdd2><sdc2><sdb2><sda2>
raid5: device sdd2 operational as raid disk 3
raid5: device sdc2 operational as raid disk 2
raid5: device sdb2 operational as raid disk 1
raid5: device sda2 operational as raid disk 0
raid5: allocated 4201kB for md0
raid5: raid level 5 set md0 active with 4 out of 4 devices, algorithm 2
RAID5 conf printout:
--- rd:4 wd:4
disk 0, o:1, dev:sda2
disk 1, o:1, dev:sdb2
disk 2, o:1, dev:sdc2
disk 3, o:1, dev:sdd2
md: ... autorun DONE.
...
So now the kernel is very happy talking to the drives, apparently. But it
doesn't like the e1000's:
...
Intel(R) PRO/1000 Network Driver - version 7.3.20-k3-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e1000: 0000:00:01.0: e1000_probe: The EEPROM Checksum Is Not Valid
/*********************/
Current EEPROM Checksum : 0xffff
Calculated : 0xbaf9
Offset Values
======== ======
00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00000010: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00000020: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00000030: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00000040: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00000050: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00000060: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00000070: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Include this output when contacting your support provider.
This is not a software error! Something bad happened to your hardware or
EEPROM image. Ignoring this problem could result in further problems,
possibly loss of data, corruption or system hangs!
The MAC Address will be reset to 00:00:00:00:00:00, which is invalid
and requires you to set the proper MAC address manually before continuing
to enable this network device.
Please inspect the EEPROM dump and report the issue to your hardware vendor
or Intel Customer Support.
/*********************/
e1000: 0000:00:01.0: e1000_probe: Invalid MAC Address
e1000: 0000:00:01.0: e1000_probe: (PCI:33MHz:32-bit) 00:00:00:00:00:00
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: 0000:00:02.0: e1000_probe: The EEPROM Checksum Is Not Valid
/*********************/
Current EEPROM Checksum : 0xffff
Calculated : 0xbaf9
Offset Values
======== ======
00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00000010: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00000020: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00000030: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00000040: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00000050: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00000060: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00000070: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Include this output when contacting your support provider.
This is not a software error! Something bad happened to your hardware or
EEPROM image. Ignoring this problem could result in further problems,
possibly loss of data, corruption or system hangs!
The MAC Address will be reset to 00:00:00:00:00:00, which is invalid
and requires you to set the proper MAC address manually before continuing
to enable this network device.
Please inspect the EEPROM dump and report the issue to your hardware vendor
or Intel Customer Support.
/*********************/
e1000: 0000:00:02.0: e1000_probe: Invalid MAC Address
e1000: 0000:00:02.0: e1000_probe: (PCI:33MHz:32-bit) 00:00:00:00:00:00
e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
e100: Intel(R) PRO/100 Network Driver, 3.5.23-k4-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
...
That makes it tough to do root-over-NFS, which is how I was planning on running
the installer. :)
I found in the .17 kernel where Thecus commented out the EEPROM checksum test in
the e1000 driver, I'm going to do the same and see what happens. My first
attempt caused the code to load all ff's for the MAC, which obviously isn't what
I want.
Lennert allocated a machid for the N4100. I guess at some point, I need to
clone the n2100 board code and continue from there...
b.g.
--
Bill Gatliff
bgat@billgatliff.com
Reply to: