Hi Joakim, --- Joakim Wennergren wrote:
> > > I've tracked down the problem to an earlier issue in > the boot, the PCI > bus doesn't seem to initialize properly. I've > attached the start of the > boot sequence both before and after I switched > kernel. > > The first row that really differs (except the PID > tables and stuff, I > assume that's just new default sizes in the kernel) > is the new line > > "IXP4xx: Using 16MiB expansion bus window size" > > I don't know if this matters, but after that the PCI > initialization goes > wrong, at the line > > "PCI: Failed to allocate mem resource > #0:[EMAIL PROTECTED] for 0000:00:0c.0" > > And after that the memory addresses are all worng, > and later all > initializations of PCI devices seem to fail. > > Where do I set up these things? Any ideas how to fix > them? > The internal ethernets and PCI are separate. I would think that a PCI error, although bad, would not affect the operation of the internal ethernet. I would compare (or re-compare) config.linux-2.6.x and config.modules between the working and not-working trees. Regards, ...doug > > > Old kernel: > > Uncompressing > Linux.............................................................................................. > > done, booting the kernel. > Linux version 2.6.14.2 ([EMAIL PROTECTED]) (gcc > version 3.3.2) #38 Thu > Dec 20 11:49:33 CET 2007 > CPU: XScale-IXP42x Family [690541f1] revision 1 > (ARMv5TE) > Machine: Intel IXDPG425 > Memory policy: ECC disabled, Data cache writeback > CPU0: D VIVT undefined 5 cache > CPU0: I cache: 32768 bytes, associativity 32, 32 > byte lines, 32 sets > CPU0: D cache: 32768 bytes, associativity 32, 32 > byte lines, 32 sets > Built 1 zonelists > Kernel command line: console=ttyS0,115200 > root=/dev/mtdblock4 > rootfstype=cramfs [EMAIL PROTECTED] > PID hash table entries: 256 (order: 8, 4096 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: 32MB = 32MB total > Memory: 29312KB available (2440K code, 523K data, > 100K init) > Mount-cache hash table entries: 512 > CPU: Testing write buffer coherency: ok > NET: Registered protocol family 16 > PCI: IXP4xx is host > PCI: IXP4xx Using indirect access for memory space > PCI: bus0: Fast back to back transfers disabled > dmabounce: registered device 0000:00:0c.0 on pci bus > dmabounce: registered device 0000:00:0d.0 on pci bus > PCI: Bus 1, cardbus bridge: 0000:00:0d.0 > IO window: 00001000-000010ff > IO window: 00001400-000014ff > PREFETCH window: 48000000-48ffffff > MEM window: 49000000-49ffffff > Generic PHY: Registered new driver > > > > New kernel: > > Uncompressing > Linux........................................................................................ > > done, booting the kernel. > Linux version 2.6.19-uc1 ([EMAIL PROTECTED]) (gcc > version 3.4.4) #169 > Thu Dec 20 11:07:40 CET 2007 > CPU: XScale-IXP42x Family [690541f1] revision 1 > (ARMv5TE), cr=000039ff > Machine: Intel IXDPG425 > Memory policy: ECC disabled, Data cache writeback > CPU0: D VIVT undefined 5 cache > CPU0: I cache: 32768 bytes, associativity 32, 32 > byte lines, 32 sets > CPU0: D cache: 32768 bytes, associativity 32, 32 > byte lines, 32 sets > Built 1 zonelists. Total pages: 8128 > Kernel command line: console=ttyS0,115200 > root=/dev/mtdblock4 > rootfstype=squashfs [EMAIL PROTECTED] > 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: 29592KB available (2276K code, 472K data, > 100K init) > Mount-cache hash table entries: 512 > CPU: Testing write buffer coherency: ok > NET: Registered protocol family 16 > IXP4xx: Using 16MiB expansion bus window size > PCI: IXP4xx is host > PCI: IXP4xx Using direct access for memory space > PCI: bus0: Fast back to back transfers disabled > dmabounce: registered device 0000:00:0c.0 on pci bus > dmabounce: registered device 0000:00:0d.0 on pci bus > PCI: Failed to allocate mem resource > #0:[EMAIL PROTECTED] for 0000:00:0c.0 > PCI: Failed to allocate mem resource > #0:[EMAIL PROTECTED] for 0000:00:0d.0 > PCI: Bus 1, cardbus bridge: 0000:00:0d.0 > IO window: 00001000-000010ff > IO window: 00001400-000014ff > PREFETCH window: 48000000-49ffffff > MEM window: 4a000000-4bffffff > pci 0000:00:0d.0: Error creating sysfs bridge > symlink, continuing... > Generic PHY: Registered new driver > > > /jocke > > Doug Kehn wrote: > > Hi Joakim, > > > > --- Joakim Wennergren wrote: > > > >> Doug Kehn wrote: > >>> Hi Joakim, > >>> > >>> --- Joakim Wennergren wrote: > >>> > >>>> I'm getting an error when trying to ifconfig up > >>>> interface eth0: > >>>> > >>>> xp400_eth: ixEthMiiLinkStatus failed on PHY0. > >>>> Can't determine > >>>> the auto negotiated parameters. Using > default > >>>> values. > >>>> > >>>> > >>>> I'm using snapgear 3.5.0 with ixp400 Access > >> library > >>>> 2.1, with the > >>>> patches from snapgear applied. > >>>> > >>>> There was a previous mail here with the same > >> problem > >>>> > > > (http://mailman.uclinux.org/pipermail/uclinux-dev/2006-January/036476.html), > >>>> but I have already applied the patches > mentioned > >> in > >>>> his solution... > >>>> > >>>> Any ideas? > >>>> > >>> What target are you building for? > >>> > >>> Regards, > >>> ....doug > >>> > >>> > >> The target platform is an IXP422, and I've chosen > >> the target IXDPG425 in > >> the kernel configuration (MACH_IXDPG425). > >> > >> I had a working previous version of snapgear with > >> this configuration, so > >> I guess it's correct. > >> > >> > > > > Try poking some printk in ixEthMiiLinkStatus > > (IxEthMii.c). There are only a couple of things > that > > would cause ixEthMiiLinkStatus to return failure. > > > > One is the reading of the PHY MII register(s). An > > indication that the PHY may not be working > properly. > > > > The other is the setting of phyNum/phyAddr. In > your > > case phyNum/phyAddr is 0. Is this consistent with > the > > working version? If not, maybe the configuration > > isn't what you expect it to be. > > > > Regards, > > ....doug > > > > > > > ____________________________________________________________________________________ > > Looking for last minute shopping deals? > > Find them fast with Yahoo! Search. > http://tools.search.yahoo.com/newsearch/category.php?category=shopping > > _______________________________________________ > > uClinux-dev mailing list > > [email protected] > > > http://mailman.uclinux.org/mailman/listinfo/uclinux-dev > > This message was resent by [email protected] > > To unsubscribe see: > > > http://mailman.uclinux.org/mailman/options/uclinux-dev > > > > This email was Anti Virus checked by Astaro > Security Gateway. > > > > > This email was Anti Virus checked by Astaro Security > Gateway. > > _______________________________________________ > uClinux-dev mailing list > [email protected] > http://mailman.uclinux.org/mailman/listinfo/uclinux-dev > This message was resent by [email protected] > To unsubscribe see: > http://mailman.uclinux.org/mailman/options/uclinux-dev > ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs _______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
