> Hi John, you're running an old kernel. Please update as per instructions > in > the email titled: "Updating romfs and new tcpborphserver3" > > Let me know if you have any problems.
Hi Alec. Well, I tried to follow those instructions, but I ran into a snag. First, the kernel image in the repository is the same as the one I already have as noted below. Second, I tried to update uboot as in the instructions, and I bricked 2 of our roaches. The macro writeuboot seems to revert to the one in ROM before being used by the 'run tftpuboot' step. I thought that I messed up typing in the new macro, so I did it again on a second roach, and bricked that one too. I am absolutely positive I entered enough 0s on the cp.b step. I guess you have to save the environment before running the tftpuboot step? Might as well make it a hat trick, I suppose, and try another one. Do I need the romfs step if I'm using nfs? John > > Regards > Alec > > On Thu, Jan 3, 2013 at 5:46 AM, John Ford <[email protected]> wrote: > >> Hi all. Ive picked up where Glenn Jones left off on Dec 5th, working on >> the iic for our R2 system, and I have got to where I think the driver's >> missing or just not loaded. When I try to open the i2c-X devices, I get >> : >> root@vegasr2-1:/usr/local/etc# i2cdetect -r 0 >> Error: Could not open file `/dev/i2c-0': No such device or address >> >> root@vegasr2-1:/usr/local/etc# i2cdetect -r 1 >> Error: Could not open file `/dev/i2c-1': No such device or address >> >> The kernel config indicates that the chardev is built as a module, as >> are >> all the other I2C devices: >> >> CONFIG_I2C_CHARDEV=m >> >> But I can't find any modules. There are none in the usual /lib/modules >> tree, and lsmod says there are no modules loaded. >> >> The system is: >> >> root@vegasr2-1:/bin# uname -a >> Linux vegasr2-1 3.7.0-rc2+ #21 Mon Nov 19 09:30:32 SAST 2012 ppc >> GNU/Linux >> >> Any idea where to go from here? >> >> John >> >> >> >> >
