Ha wouldnt it be mad if all it was is someone just put a 1 in somewhere instead of a 2.by Buttzy10169 - Debian
Any body know how to go about submitting your patch? i think my patch is ready just wanna know what i have to go through to submit it?by Buttzy10169 - Debian
Cool. I dont know whats goiing on with mine today now when i build it's telling me there's no support in the darn kernel for my device. edit: got that fixed think the dtb was appending properly. I cant seem to get the bootargs right in the dtb file but if i use the ones from the bootloader it boots to the sata_mv problem. edit 2: i just tried the nr_ports = <1> and myby Buttzy10169 - Debian
My Bootl og shows 256mb ram on my ix2-200 and i also tried the number of ports thing aswel and it didnt work either for me. Ha any way we can roll back the sata mv changes to the 3.4 kernel ones or something to get them working properly?by Buttzy10169 - Debian
for some reason my uImage and uInitrd wont sync now so i keep getting this: [ 2.370103] Waiting 10sec before mounting root device... [ 12.862871] List of all partitions: [ 12.866379] 1f00 3072 mtdblock0 (driver?) [ 12.871460] 1f01 16384 mtdblock1 (driver?) [ 12.876555] No filesystem could mount root, tried: [ 12.881462] Kernel panic - not syncing: VFS:by Buttzy10169 - Debian
Yeah that looks like what i was getting on my ix2-200.by Buttzy10169 - Debian
I think i tried both declareing in uboot and declareing in the dts file and neither worked i still get the same errors as above with the sata_mv and usb like i posted above with the latest git. if the sata's are working for you in git the latest kernel and git then there must just be sumthing up with my dts or board config.by Buttzy10169 - Debian
I think I have tried that but it still didnt boot but will give it a shot. What way do you clear the bootargs?by Buttzy10169 - Debian
How are you getting them to boot? I have tried multiple time's i think i have a working dts and config but on all kernels i try 3.5, 3.6-rc1 and linux next it seems to hang around the usb and sata_mv initialisation. Only other thing i need is the proper definition for my device as iom,ix2-200 keep's telling me that there is no support in the kernel.by Buttzy10169 - Debian
I just tried the latest kernel source from git as of about 30 minutes ago. The kernel works by modifying the rd88f6281 config file and creating the dts but then hangs and keeps repeating the following: udevd[54]: timeout: killing '/sbin/modprobe -b usb:v13FDp1840d0103dc00dsc00dp00ic08isc06ip50in00' [77] udevd[56]: timeout: killing '/sbin/modprobe -b platform:sata_mv'by Buttzy10169 - Debian
Im almost there its booting but I just have 2 majorish problems: 1st: after loading the uImage and uInitrd there is no output from the serial until the system is booted. 2nd: the sata's are not being setup / detected. Anybody have any idea's? edit 1: fixed the serial issue that was just something in the uboot bootargs that i didnt set properly while testing the kernel. stby Buttzy10169 - Debian
Thanks will see if it does anything.by Buttzy10169 - Debian
I dont know how or why but for some reason the 3.6 kernel just booted. There was no output from the serial from the time the uInitrd was loaded then just all of a sudden it was booted. There was no sata's though so not sure how why or what loaded it. Before this even with my ix2200 selected in the config it didnt work at boot just said board support not available. Anyone have any ideby Buttzy10169 - Debian
is this right for the 256mb ram? reg = <0x00000000 0x10000000> Im gona go a lil crazy with my ix2-200 today i think and put the uInitrd and uImage on the nand instead of on usb and see how it goes. From what i could tell after seeing a lil more of the boot of mine it keeps saying the uInitrd is full of junk or something. so the uInitrd isnt there to load any of the drivers and such forby Buttzy10169 - Debian
did you change the dts file for the iconnect? check the memory setting in the dts file and see if this is right for 256mb of ram: memory { device_type = "memory"; reg = <0x00000000 0x10000000>; Would you have any idea on how to compile and run uboot from ram so i can test a new version? The ix2-200 has 256mb of ram aswel. But i cannot get the system booted with the kby Buttzy10169 - Debian
Im beginning to think that the same way that the goflex net needed a new uboot to use the 3.2 kernels and beyond properly perhapt maybe now the ix2-200 needs a new uboot to be able to use kernels with device tree? edit 1: rpress How did you compile the new uBoot with the dts support?by Buttzy10169 - Debian
Looks like they have been changeing something in the sata_mv alright but thats about as much as i can make out of those patches. im gna try build for the rd88f6281 as thats what iv been working off of for my ix2-200 and thats what the origional patch modified to make it work. then i will see if it boots with it. edit 1: Nope that didn't work.by Buttzy10169 - Debian
Yeah it shows my 2 drives and the are the same both 2tb drives but the serials do show slightly different. 1 ends in zs the other ss. my uboot would be the origional marvell uboot aswel as i dont have a jtag to build and test new uboot's.by Buttzy10169 - Debian
I actualy have a root delay of 10 in mine aswel but it just waits the 10 seconds then panics. Its not even getting to the part of trying to detect any usb's or sata drives. if i build with support for just the rd88f6281 it gets to the point of trying to detect the sata but with my own ix2200 board config and dts it doesnt try to detect any usb's or sata's just tries to mount thby Buttzy10169 - Debian
it must be something silly thats missing somewhere then coz the goflexnet was mainlined and you said it didnt work so it must be something very small somewhere. Im trying to boot from the usb though on my device. Mine is getting weird now telling me the support is not there.and when it was attemting to boot it seemed to be trying to mount the rootfs way too early before any usb's or sataby Buttzy10169 - Debian
Im working on the iomega ix2-200 not the goflex net the goflexnet already has a new uboot and support in 3.6 rc1 kernel This is as far as iv gotten with the ix2-200 but it wont boot it tries to mount the root filesystem before it has even detected the usb or anything I could realy use someone's help as i have no clue where to go from here: this is the dts file for the ix2-200: http:by Buttzy10169 - Debian
I seem to be getting a kernel panic now today this is the most i can get from the kernel panic when it tries to load unless anyone knows how i can capture the entire panic? http://pastebin.com/wyBJEiuy edit1: i removed a kirkwood init line from the board config file and that seem's to of gotten rid of the kernel panic but now during boot it just seems to stop with: turn off bootby Buttzy10169 - Debian
This is a longshot but since im running wheezy its hardly something in it thats messing up would it? Also i moved the i2c into the dts luckily the iconnect had the same lm63 so that made that easy. edit: since im booting from a usb should i do something with this line thats in the board config file? kirkwood_ehci_init(); edit 2: this is how the dts fie looks now: http://pastebin.by Buttzy10169 - Debian
I actually have a GFN here aswel but i dont have any drives or o's on it at the minute and it takes hours to install debian to a usb stick on it (at least in my experience it did anyway) and i have no spare drives to put into it. in the board config i have an i2c : static struct i2c_board_info __initdata ix2200_i2c = { I2C_BOARD_INFO("lm63", 0x4c), }; what about the thinby Buttzy10169 - Debian
I just decided to create an account so i can edit my posts if i think iv found something new. Yeah i have 2 ports and i just looked through a couple of the devices and the ones that have the sata seem to have the same sata@80000. it seems to be haveing trouble with some kind of clock here: sata_mv.0: cannot get optional clkdev and i seen this in one of the other kirkwood devices i wondby Buttzy10169 - Debian