PHY link up/down looping
Hello, Has anybody here had the problem where upon the linux 2.6 kernel booting, the PHY link seems to be in some kind of auto-negotiating loop of going up and down? This has been hapenning in my 2.6.19 kernel with a Marvell PHY (88E1011S). The board i'm working with is similar to the MPC8555CDS, so i'm using that kernel config for this environment. Clinton Thomas ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Kernel crash on mem= argument
So, I am able to get my system to autoboot with a ramdisk out of flash if I leave the mem= argument out of my u-boot bootargs, however since I need to define the range of real memory for my kernel to address, leaving that argument out is not an option for me. When I add it in, this is the error I get. NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. RAMDISK: Couldn't find valid RAM disk image starting at 0. Freeing initrd memory: 3938k freed Oops: kernel access of bad area, sig: 11 NIP: C002EB90 XER: 2000 LR: C0030120 SP: C0419DB0 REGS: c0419d00 TRAP: 0800Not tainted MSR: 9000 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 00 DEAR: 8048486C, ESR: 0080 TASK = c0418000[1] 'swapper' Last syscall: 6 last math last altivec last spe GPR00: C0419DB0 C0418000 C0584820 0001 C058483C 0080 GPR08: C0584838 80484868 C0291000 C0584808 10001000 GPR16: 0001 0001 007FFF00 9002 C0419EA0 C0003DEC GPR24: C0003B40 007FFEB0 C024 C024 CFFAEB6B C0584820 CFBD7000 Call backtrace: C0030120 C000D94C C00F86E0 C003A388 C0038D24 C0003B9C C020019C C0001E98 C0001ACC C00064B8 Kernel panic: Attempted to kill init! 0Rebooting in 180 seconds.. Suddenly, the kernel goes from finding, mounting and loading it's ramdisk RFS, to not being able to find it at all. I have not moved the ramdisk in flash, so i'm unsure why adding a mem= argument on the kernel bootargs would do this. Any ideas? Clinton Thomas ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
RE: Kernel crash on mem= argument
My u-boot config does not currently have a CONFIG_PRAM variable defined. Is doing this as easy as dropping in a #define in my board config? Or do I need to address this in another part of the code? Up until now, I just assumed that if I passed mem=200M to the kernel, it would allocate as necessary, then I could use the remaining RAM as I saw fit, but since this is not working I need to deal with it appropriately. Clint -Original Message- From: Frank D Lombardo [mailto:[EMAIL PROTECTED] Sent: Thursday, April 19, 2007 2:39 PM To: Clint Thomas Cc: linuxppc-embedded@ozlabs.org Subject: Re: Kernel crash on mem= argument Clint Thomas wrote: So, I am able to get my system to autoboot with a ramdisk out of flash if I leave the mem= argument out of my u-boot bootargs, however since I need to define the range of real memory for my kernel to address, leaving that argument out is not an option for me. When I add it in, this is the error I get. NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. RAMDISK: Couldn't find valid RAM disk image starting at 0. Freeing initrd memory: 3938k freed Oops: kernel access of bad area, sig: 11 NIP: C002EB90 XER: 2000 LR: C0030120 SP: C0419DB0 REGS: c0419d00 TRAP: 0800Not tainted MSR: 9000 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 00 DEAR: 8048486C, ESR: 0080 TASK = c0418000[1] 'swapper' Last syscall: 6 last math last altivec last spe GPR00: C0419DB0 C0418000 C0584820 0001 C058483C 0080 GPR08: C0584838 80484868 C0291000 C0584808 10001000 GPR16: 0001 0001 007FFF00 9002 C0419EA0 C0003DEC GPR24: C0003B40 007FFEB0 C024 C024 CFFAEB6B C0584820 CFBD7000 Call backtrace: C0030120 C000D94C C00F86E0 C003A388 C0038D24 C0003B9C C020019C C0001E98 C0001ACC C00064B8 Kernel panic: Attempted to kill init! 0Rebooting in 180 seconds.. Suddenly, the kernel goes from finding, mounting and loading it's ramdisk RFS, to not being able to find it at all. I have not moved the ramdisk in flash, so i'm unsure why adding a mem= argument on the kernel bootargs would do this. Any ideas? Clinton Thomas ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded Make sure that u-boot does not load the initrd in the space above the limit set with the mem variable. See the u-boot README description of CONFIG_PRAM. That should help. Frank ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
RE: Linux 2.6 and uboot
I tried combining the root file system and kernel images so that I could just load a single image in u-boot, and I disabled networking in the kernel config. When I do this, the kernel boots and loads into the shell no problem. The problem seems to be related to the Marvell PHY, so my plan is to investigate the IRQs and make sure it isn't getting the same as another device. Not sure what I'll look for after that, can KGDB step through the enet drivers on boot? Clint -Original Message- From: Guennadi Liakhovetski [mailto:[EMAIL PROTECTED] Sent: Saturday, April 14, 2007 3:02 PM To: Clint Thomas Cc: Kumar Gala; linuxppc-embedded@ozlabs.org Subject: RE: Linux 2.6 and uboot On Fri, 13 Apr 2007, Clint Thomas wrote: mice: PS/2 mouse device common for all mice i2c /dev entries driver TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 This is the point where it stops booting. It might be just the point before root is mounted... That's what I'd check anyway... I see it has 2 eth interfaces. Can it be that their order has changed and it's trying the wrong one? Thanks Guennadi --- Guennadi Liakhovetski ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
RE: Linux 2.6 and uboot
Sorry, not quite the latest kernel. 2.6.19 as distributed in ELDK 4.1, built for the MPC8555CDS, although the actual board is slightly different. Here is the boot time output. U-boot succesfully enables the ethernet to get its kernel image from the TFTP server. ## Booting image at 0100 ... Image Name: Linux-2.6.19.2 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:1475429 Bytes = 1.4 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK Memory CAM mapping: CAM0=256Mb, CAM1=0Mb, CAM2=0Mb residual: 0Mb Linux version 2.6.19.2 ([EMAIL PROTECTED]) (gcc version 4.0.0 (DENX ELDK 4.1 4.0.0)) #3 Mon Apr 13:44:24 EDT 2007 mpc85xx_cds_setup_arch CDS Version = 80 in PCI slot 1 Zone PFN ranges: DMA 0 -65536 Normal 65536 -65536 early_node_map[1] active PFN ranges 0:0 -65536 Built 1 zonelists. Total pages: 65024 Kernel command line: root=/dev/nfs nfsaddrs=204.215.226.247:204.215.226.49:204.215.226.50:255.255.2 5.0 rw nfsroot=/opt/RFS_CAT console=ttyS0,9600 doPci=1 OpenPIC Version 1.2 (1 CPUs and 60 IRQ sources) at fcf78000 PID hash table entries: 1024 (order: 10, 4096 bytes) Warning: real time clock seems stuck! Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 256640k available (2276k kernel code, 704k data, 136k init, 0k highmem) Mount-cache hash table entries: 512 NET: Registered protocol family 16 PCI: Probing PCI hardware Generic PHY: Registered new driver SCSI subsystem initialized 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: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled serial8250.0: ttyS0 at MMIO 0xfdf04500 (irq = 106) is a 16550A serial8250.0: ttyS1 at MMIO 0xfdf04600 (irq = 106) is a 16550A RAMDISK driver initialized: 8 RAM disks of 32768K size 1024 blocksize loop: loaded (max 8 devices) nbd: registered device at major 43 Gianfar MII Bus: probed eth0: Gianfar Ethernet Controller Version 1.2, 00:01:af:07:9b:8b eth0: Running with NAPI enabled eth0: 256/256 RX/TX BD ring size eth1: Gianfar Ethernet Controller Version 1.2, df:f7:bf:7d:72:6f eth1: Running with NAPI enabled eth1: 256/256 RX/TX BD ring size Marvell 88E1101: Registered new driver Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx st: Version 20050830, fixed bufsize 32768, s/g segs 256 ehci_hcd :01:06.2: EHCI Host Controller ehci_hcd :01:06.2: new USB bus registered, assigned bus number 1 ehci_hcd :01:06.2: irq 130, io mem 0x9efbdf00 ehci_hcd :01:06.2: USB 2.0 started, EHCI 0.95, driver 10 Dec 2004 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 4 ports detected ohci_hcd :01:06.0: OHCI Host Controller ohci_hcd :01:06.0: new USB bus registered, assigned bus number 2 ohci_hcd :01:06.0: irq 130, io mem 0x9efbf000 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ohci_hcd :01:06.1: OHCI Host Controller ohci_hcd :01:06.1: new USB bus registered, assigned bus number 3 ohci_hcd :01:06.1: irq 130, io mem 0x9efbe000 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected 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 TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 This is the point where it stops booting. Clint Thomas -Original Message- From: Kumar Gala [mailto:[EMAIL PROTECTED] Sent: Friday, April 13, 2007 4:18 PM To: Clint Thomas Cc: [EMAIL PROTECTED] Subject: Re: Linux 2.6 and uboot On Apr 13, 2007, at 2:55 PM, Clint Thomas wrote: Is there any correlation between the version of U-boot to use on a board and the version of the Linux kernel you plan to use? Current I'm running U-boot 1.1.2 with kernel 2.4.26 on my MPC85xx board, but i'm trying to migrate to the latest 2.6 kernel. I am getting a kernel hang at boot when it registers socket family 17, so I was wondering if it might have
MPC8555CDS ELDK build issue
Hey, Using the ELDK 4.1, I am trying to compile the linux sources for the MPC8555CDS. I installed the source tree provided with ELDK 4.1 (2.6.19) and the associated crosstools. The only factors I changed in the kernel config were to set the processor arch to e500 and the platform to 8555CDS. When I run make, this is where it fails. CC arch/ppc/syslib/mpc85xx_devices.o arch/ppc/syslib/mpc85xx_devices.c:99: error: 'F1_RXCLK' undeclared here (not in a function) arch/ppc/syslib/mpc85xx_devices.c:99: error: 'F1_TXCLK' undeclared here (not in a function) arch/ppc/syslib/mpc85xx_devices.c:117: error: 'F2_RXCLK' undeclared here (not in a function) arch/ppc/syslib/mpc85xx_devices.c:117: error: 'F2_TXCLK' undeclared here (not in a function) arch/ppc/syslib/mpc85xx_devices.c:135: error: 'F3_RXCLK' undeclared here (not in a function) arch/ppc/syslib/mpc85xx_devices.c:135: error: 'F3_TXCLK' undeclared here (not in a function) make[1]: *** [arch/ppc/syslib/mpc85xx_devices.o] Error 1 make: *** [arch/ppc/syslib] Error 2 This is the exact same build error I get when compiling with the same cross-tools, using several other version of the Linux kernel. Any of the Freescale guys know why this is? Thanks Clint Thomas ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Linux 2.6 and SystemAce
Hey, For anybody who has been working with Xilinx SystemAce, I wanted to know if anybody has either a working driver for the Linux 2.6 kernel, or has booted the linux 2.6 kernel on an ML300. I'm trying to avoid the Montavista Linux route if at all possible. Thx Clinton Thomas ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
MTD and U-boot
Hey, I want to be able to write/read from the same boot flash U-boot resides on. Right now, u-boot and the vmlinux.img reside on the same 16bit NAND flash. Is it possible to setup the flash so that from linux, I can erase and write an updated vmlinux.img when I want to update a kernel build on the system, without partitioning off a section of it away from U-boot? Clinton Thomas ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Cross compile GDB 6.6 error
Hey guys, I am trying to build a native GDB to run on my powerpc-405 target. To do this, I run the configure script in gdb-6.6 as such ./configure --build=i386-linux-gnu --target=powerpc-405-linux-gnu --host=powerpc-405-linux-gnu Now beforehand, I tried building this, and the make would always fail with the error No Termcap Library found. After finding out that the --builduserland option is broken, I tried cross-compiling ncurses manually. After doing that, I moved the contents of the ../ncurses/lib directory into the directory containing libc.a in my cross-compiler directory. Now when I build GDB, I get this output powerpc-405-linux-gnu-gcc -c -g -O2 -I. -I.././gdb -I.././gdb/config -LOCALEDIR=\/usr/local/share/locale\ -DHAVE_CONFIG_H -I.././gdb/../include/opcode -I.././gdb/../readline/..-I../bfd -I.././gdb/../bfd -I.././gdb/../include -DMI_OUT=1 -DTUI=1 -Wimplicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith -Wformat-nonliteral -Wunused-label -Wunused-function -Wuninitialized .././gdb/tui/tui-command.c In file included from .././gdb/tui/tui-command.c:28: ./tui/tui-data.h:40: error: parse error before WINDOW ./tui/tui-data.h:40: warning: no semicolon at end of struct or union ./tui/tui-data.h:52: error: parse error before '}' token ./tui/tui-data.h:228: error: field `data_window' has incomplete type ./tui/tui-data.h:282: error: field `generic' has incomplete type In file included from .././gdb/tui/tui-command.c:29: ./tui/tui-win.h:42: error: parse error before tui_border_ulcorner ./tui/tui-win.h:42: warning: type defaults to `int' in declaration of `tui_border_ulcorner' ./tui/tui-win.h:42: warning: data definition has no type or storage class ./tui/tui-win.h:43: error: parse error before tui_border_urcorner ./tui/tui-win.h:43: warning: type defaults to `int' in declaration of `tui_border_urcorner' ./tui/tui-win.h:43: warning: data definition has no type or storage class ./tui/tui-win.h:44: error: parse error before tui_border_lrcorner ./tui/tui-win.h:44: warning: type defaults to `int' in declaration of `tui_border_lrcorner' ./tui/tui-win.h:44: warning: data definition has no type or storage class ./tui/tui-win.h:45: error: parse error before tui_border_llcorner ./tui/tui-win.h:45: warning: type defaults to `int' in declaration of `tui_border_llcorner' ./tui/tui-win.h:45: warning: data definition has no type or storage class ./tui/tui-win.h:46: error: parse error before tui_border_vline ./tui/tui-win.h:46: warning: type defaults to `int' in declaration of `tui_border_vline' ./tui/tui-win.h:46: warning: data definition has no type or storage class ./tui/tui-win.h:47: error: parse error before tui_border_hline ./tui/tui-win.h:47: warning: type defaults to `int' in declaration of `tui_border_hline' ./tui/tui-win.h:47: warning: data definition has no type or storage class .././gdb/tui/tui-command.c: In function `tui_dispatch_ctrl_char': .././gdb/tui/tui-command.c:80: error: `WINDOW' undeclared (first use in this function) .././gdb/tui/tui-command.c:80: error: (Each undeclared identifier is reported only once .././gdb/tui/tui-command.c:80: error: for each function it appears in.) .././gdb/tui/tui-command.c:80: error: `w' undeclared (first use in this function) .././gdb/tui/tui-command.c:85: warning: implicit declaration of function `wgetch' .././gdb/tui/tui-command.c:86: error: `ERR' undeclared (first use in this function) .././gdb/tui/tui-command.c:93: error: `KEY_PPAGE' undeclared (first use in this function) .././gdb/tui/tui-command.c:95: error: `KEY_NPAGE' undeclared (first use in this function) .././gdb/tui/tui-command.c:113: error: `KEY_DOWN' undeclared (first use in this function) .././gdb/tui/tui-command.c:114: error: `KEY_SF' undeclared (first use in this function) .././gdb/tui/tui-command.c:117: error: `KEY_UP' undeclared (first use in this function) .././gdb/tui/tui-command.c:118: error: `KEY_SR' undeclared (first use in this function) .././gdb/tui/tui-command.c:121: error: `KEY_RIGHT' undeclared (first use in this function) .././gdb/tui/tui-command.c:124: error: `KEY_LEFT' undeclared (first use in this function) make[2]: *** [tui-command.o] Error 1 make[2]: Leaving directory `/home/cthomas/gdb-6.6/gdb' make[1]: *** [all-gdb] Error 2 make[1]: Leaving directory `/home/cthomas/gdb-6.6' make: *** [all] Error 2 I've been looking around the mailing lists, it seems like the problem is related to ncurses, but I am unsure of what I am doing wrong, as I have not found a good solution to my problem of building GDB to run native on my target. Clinton Thomas ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Define Linux system memory
To anybody who has done this before or understands how to do this, I was wondering if you know how to tell the kernel how much memory there is in the system. An example would be if I have 512MB of RAM, but only want the system to know that there is about 500MB in RAM, so that 12MB does not exist to the OS/kernel. Would this require mucking about in U-boot? or can I just define this in the kernel source? Thanks Clinton Thomas ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Console Stops on NFS root startup
Hey guys,I have a dev board based loosely off the MPC8540ADS that I am trying to boot over NFS. After setting up the proper kernel configuration and sharing the root filesystem over NFS, I boot up the board. Everything loads up fine, and it even says it mounts the root filesystem, however this is the output I get.IP-Config: Complete: device=eth0, addr=204.215.226.251, mask=255.255.255.0, gw=204.215.226.50, host=204.215.226.251, domain=, nis-domain=(none), bootserver=204.215.226.250, rootserver=204.215.226.250, rootpath=NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.Looking up port of RPC 13/2 on 204.215.226.250Looking up port of RPC 15/1 on 204.215.226.250VFS: Mounted root (nfs filesystem).Mounted devfs on /devFreeing unused kernel memory: 236k init At this point, the serial console no longer displays or accepts input from the keyboard. The system does not appear to hang, because when I try to ping it from another point on the network, it responds. It seems like either init is not executing at this point, or if the console is being changed to another device. I wanted to know if anybody has had this problem before. I tried building BusyBox as a static-linked binary, which has not resolved the issue. I have also tried multiple root file system builds, which has also not yielded a solution. Thanks for any assistance with this. Clinton Thomas ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
PPC405 system slow boot
Hey guys, I've run through the loops to try and figure what could be wrong with this system. The board in question is modeled after the Xilinx ML300 board. It uses a Xilinx System ACE chip to load a FPGA / Kernel image from compact flash. Originally, I was trying to use the CompactFlash as the root file system, but because of issues in either the design or software, this would only work if SysAce was in polled I/O mode. To circumvent this, I built my root filesystem into an initrd image and built a single ELF file with the Kernel and RFS, then strapped that to the FPGA bit file to make a single FPGA/Kernel/RFS SysAce file. Upon decompression, the Linux kernel boots quickly and loads all of the device drivers. However when it gets to the prompt, it starts slowing down. Output and input to and from the board becomes very very slow (it displays 2 characters roughly every 20 seconds). Originally I believed this to be the CPU still polling SystemAce, so I disabled the Linux System ACE drivers to remove that as a possibility, however after doing this, the problem still persists, even with the RFS in ram! Has anybody encountered a similar situation to this before, with possible insight towards a solution? Thank you for your time. Clinton Thomas cthomas at soneticom.com -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060828/14d4c450/attachment.htm
PCI resource allocation MPC8540ADS
Hey guys, I have a development board based loosely off the MPC8540ADS design that I am trying to move to the Linux kernel 2.6. I already have this system working successfully in Linux Kernel 2.4, but after dealing with compilation and load errors, i've come to the point where I can get to a console. However, this problem at boot time keeps me from using a lot of onboard hardware. When I enable PCI support in the Kernel configuration, this is the text I get at boot time... PCI: Probing PCI hardware PCI: Cannot allocate resource region 1 of PCI bridge 1 PCI: Cannot allocate resource region 2 of PCI bridge 1 PCI: bridge 1 resource 2 moved to 9ff0..9fff PCI: Cannot allocate resource region 1 of PCI bridge 2 PCI: Cannot allocate resource region 2 of PCI bridge 2 PCI: bridge 2 resource 2 moved to 9fe0..9fef PCI: Cannot allocate resource region 1 of device :00:14.0 PCI: Cannot allocate resource region 2 of device :00:14.0 PCI: Cannot allocate resource region 0 of device :01:01.0 PCI: Cannot allocate resource region 1 of device :01:01.0 PCI: Cannot allocate resource region 2 of device :01:01.0 PCI: Cannot allocate resource region 0 of device :01:05.0 PCI: Cannot allocate resource region 1 of device :01:05.0 PCI: Cannot allocate resource region 2 of device :01:05.0 PCI: Cannot allocate resource region 0 of device :01:06.0 PCI: Cannot allocate resource region 0 of device :01:06.1 PCI: Cannot allocate resource region 0 of device :01:06.2 PCI: Failed to allocate mem resource #0:100 at 0 for :01:01.0 PCI: Failed to allocate I/O resource #1:100 at 1000 for :01:01.0 PCI: Failed to allocate mem resource #2:1000 at 0 for :01:01.0 PCI: Failed to allocate mem resource #0:1 at 0 for :01:05.0 PCI: Failed to allocate mem resource #2:1 at 0 for :01:05.0 PCI: Failed to allocate mem resource #0:1000 at 0 for :01:06.0 PCI: Failed to allocate mem resource #0:1000 at 0 for :01:06.1 PCI: Failed to allocate mem resource #0:100 at 0 for :01:06.2 the system is using a PLX PCI bridge chip. Like I said, this works fine in my 2.4 distribution. Thanks for any and all help! Clinton Thomas cthomas at soneticom.com -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060823/c95004fa/attachment.htm
Linux hanging on Xilinx SystemACE
Hey, Using the powerpc development tree of Linux 2.4, I am trying to boot my system from CompactFlash using Xilinx SystemACE. My compact flash card has two partitions, a 16MB FAT16 that holds the combination FPGA image / Linux Kernel ELF file, and an Ext2 partition that holds the root file system. The system starts the boot process, uncompresses the Linux kernel and begins loading drivers. Part way into this process, it conducts a partition check of the drive being reported to it by SystemACE, however, it hangs at that point. No kernel panic, no error message, it simply hangs. Here is the output at that point... Partition check: xsysacea: what I am trying to find out is if this problem has been seen/fixed in the past? or did I format the CF card incorrectly? Clinton Thomas cthomas at soneticom.com -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060816/b26e7df6/attachment.htm
Booting Linux Kernel without bootloader
Hey guys, I have gone through the Linuxppc embedded and dev lists for information related to what I am trying to do, but was unable to find exactly what i'm looking for. Basically, the system I want linux running on does not require the initialization of hardware that U-boot provides, or at least it does not need it to boot the linux kernel. I want to load an uncompressed linux kernel into memory and start the execution of the kernel, without using any kind of bootloader. Is this possible? Or does linux need some kind of firmware or other software to tell it to start executing? Thanks for any info you might have. Clinton Thomas cthomas at soneticom.com -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060725/d7bbff33/attachment.htm
