kernel 3.5 and device-tree support...
Posted by davygravy
|
Re: kernel 3.5 and device-tree support... August 11, 2012 08:10AM |
Registered: 11 years ago Posts: 52 |
|
Re: kernel 3.5 and device-tree support... August 11, 2012 08:29AM |
Registered: 11 years ago Posts: 115 |
is this right for the 256mb ram?
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 for the device.
and i think by mistake im after deleting the ubuntu vm i was doing the work on DOH!
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 for the device.
and i think by mistake im after deleting the ubuntu vm i was doing the work on DOH!
|
Re: kernel 3.5 and device-tree support... August 11, 2012 04:57PM |
Registered: 11 years ago Posts: 115 |
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 idea what the arcNumber for the ix2-200 i saw it before but cant find it again?
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 idea what the arcNumber for the ix2-200 i saw it before but cant find it again?
|
Re: kernel 3.5 and device-tree support... August 11, 2012 05:15PM |
Admin Registered: 13 years ago Posts: 18,570 |
|
Re: kernel 3.5 and device-tree support... August 11, 2012 05:23PM |
Registered: 11 years ago Posts: 115 |
|
Re: kernel 3.5 and device-tree support... August 12, 2012 04:55AM |
Registered: 11 years ago Posts: 115 |
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.
still have the issue with the sata though this is how the serial output is when the kernel gets to the sata part:
edit 2:
Has anyone seen a fix for the sata_mv problem?
i have a working config and dts file but i also need a different entry instead of "iom,ix2-200" as it does not seem to be detecting right just says the support is not there.
But if i just modify the rd88f6281 setup file and use my dts everything works fine except for the sata's.
Edited 2 time(s). Last edit at 08/12/2012 11:07AM by Buttzy10169.
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.
still have the issue with the sata though this is how the serial output is when the kernel gets to the sata part:
[....] Starting the hotplug events dispatcher: udevd[ 25.082778] udevd[340]: starting version 175 . ok [....] Synthesizing the initial hotplug events...udevd[370]: timeout 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [ 25.636981] sata_mv sata_mv.0: cannot get optional clkdev [ 25.642492] sata_mv sata_mv.0: slots 32 ports 2 udevd[370]: timeout '/sbin/blkid -o udev -p /dev/sda' done. [....] Waiting for /dev to be fully populated...^_udevd[374]: timeout: killing '/sbin/modprobe -b platform:sata_mv' [401] udevd[374]: timeout: killing '/sbin/modprobe -b platform:sata_mv' [401] udevd[374]: timeout: killing '/sbin/modprobe -b platform:sata_mv' [401]
edit 2:
Has anyone seen a fix for the sata_mv problem?
i have a working config and dts file but i also need a different entry instead of "iom,ix2-200" as it does not seem to be detecting right just says the support is not there.
But if i just modify the rd88f6281 setup file and use my dts everything works fine except for the sata's.
Edited 2 time(s). Last edit at 08/12/2012 11:07AM by Buttzy10169.
|
Re: kernel 3.5 and device-tree support... August 13, 2012 07:28AM |
Registered: 11 years ago Posts: 115 |
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:
Seems like something is broken in either the sata_mv or the ehci controller that stops drives from being loaded or mounted. Anyone run into similar problems? or have any idea's of what i can try next?
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' [73]
Seems like something is broken in either the sata_mv or the ehci controller that stops drives from being loaded or mounted. Anyone run into similar problems? or have any idea's of what i can try next?
|
Re: kernel 3.5 and device-tree support... August 13, 2012 09:11AM |
Registered: 11 years ago Posts: 52 |
|
Re: kernel 3.5 and device-tree support... August 13, 2012 11:19AM |
Registered: 11 years ago Posts: 115 |
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.
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.
|
Re: kernel 3.5 and device-tree support... August 13, 2012 11:42AM |
Registered: 11 years ago Posts: 52 |
|
Re: kernel 3.5 and device-tree support... August 13, 2012 12:31PM |
Registered: 11 years ago Posts: 115 |
|
Re: kernel 3.5 and device-tree support... August 13, 2012 01:02PM |
Registered: 11 years ago Posts: 52 |
|
Re: kernel 3.5 and device-tree support... August 13, 2012 02:14PM |
Registered: 11 years ago Posts: 115 |
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.
|
Re: kernel 3.5 and device-tree support... August 13, 2012 05:05PM |
Registered: 11 years ago Posts: 52 |
Looks like there was a regression somewhere, I'm seeing the same hang on 3.6-rc1 and the current next cut, the last thing I see is:
Then all is silent. I'm also not seeing my LED turn green, so something is amiss. This was working in 3.5 when I submitted my GFN patch set for inclusion in 3.6. I'm going to take it up with the arm kernel list to see if I can get some pointers on how to proceed.
[ 15.283577] VFS: Disk quotas dquot_6.5.2 [ 15.287832] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 15.296545] jffs2: version 2.2. (NAND) ?© 2001-2006 Red Hat, Inc. [ 15.303202] msgmni has been set to 240 [ 15.308503] Block layer SCSI generic (bsg) driver version 0.4 loaded (major ) [ 15.316021] io scheduler noop registered [ 15.320149] io scheduler deadline registered [ 15.324558] io scheduler cfq registered (default) [ 15.329462] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver [ 15.335962] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver [ 15.376751] mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) [ 15.416736] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy ) [ 15.456735] mv_xor mv_xor.2: Marvell XOR: ( xor cpy ) [ 15.496734] mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy ) [ 15.506309] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 15.518967] brd: module loaded [ 15.524991] loop: module loaded [ 15.528584] sata_mv sata_mv.0: cannot get optional clkdev [ 15.534180] sata_mv sata_mv.0: slots 32 ports 2
Then all is silent. I'm also not seeing my LED turn green, so something is amiss. This was working in 3.5 when I submitted my GFN patch set for inclusion in 3.6. I'm going to take it up with the arm kernel list to see if I can get some pointers on how to proceed.
|
Re: kernel 3.5 and device-tree support... August 13, 2012 06:02PM |
Registered: 11 years ago Posts: 115 |
|
Re: kernel 3.5 and device-tree support... August 13, 2012 06:05PM |
Registered: 11 years ago Posts: 52 |
|
Re: kernel 3.5 and device-tree support... August 13, 2012 09:14PM |
Registered: 11 years ago Posts: 115 |
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: Unable to mount root fs on unknown-block(0,0) [ 12.889798] [<c000e2a4>] (unwind_backtrace+0x0/0xe0) from [<c02e3c8c>] (panic+0x78/0x1d4) [ 12.898027] [<c02e3c8c>] (panic+0x78/0x1d4) from [<c03f8c90>] (mount_block_root+0x238/0x288) [ 12.906513] [<c03f8c90>] (mount_block_root+0x238/0x288) from [<c03f8e68>] (prepare_namespace+0x124/0x184) [ 12.916131] [<c03f8e68>] (prepare_namespace+0x124/0x184) from [<c03f8914>] (kernel_init+0x198/0x1d8) [ 12.925311] [<c03f8914>] (kernel_init+0x198/0x1d8) from [<c000a004>] (kernel_thread_exit+0x0/0x8)
|
Re: kernel 3.5 and device-tree support... August 13, 2012 09:40PM |
Registered: 11 years ago Posts: 17 |
Has anyone been able to reproduce my findings, where setting nr_ports = <1> allows booting? My GFN is currently working, but with just one port.
And as I mentioned before, the DTS file shows the correct 256 MB of RAM, but the kernel when booting only shows 128 MB. Something else is wrong here.
And as I mentioned before, the DTS file shows the correct 256 MB of RAM, but the kernel when booting only shows 128 MB. Something else is wrong here.
|
Re: kernel 3.5 and device-tree support... August 13, 2012 09:46PM |
Registered: 11 years ago Posts: 52 |
|
Re: kernel 3.5 and device-tree support... August 13, 2012 09:56PM |
Registered: 11 years ago Posts: 17 |
Kurlon Wrote:
-------------------------------------------------------
> I haven't tried dropping nr_ports yet, lemmie test
> that real quick.
>
> In the mean time, you're saying you have a GoFlex
> Net with 256MB RAM?
No, I have two Marvell Kirkwood devices. A GoFlexNet, with 128 MB RAM and now only one working SATA port on 3.6.0-rc1, with nr_ports = <1>. I also have an Iomega iConnect with 256 MB RAM, and only 128 MB accessible with 3.6.0-rc1. I used the appropriate DTB file for each, of course.
Buttzy,
What does your kernel boot log show for RAM on your ix2-200?
Edited 1 time(s). Last edit at 08/14/2012 12:10AM by rpress.
-------------------------------------------------------
> I haven't tried dropping nr_ports yet, lemmie test
> that real quick.
>
> In the mean time, you're saying you have a GoFlex
> Net with 256MB RAM?
No, I have two Marvell Kirkwood devices. A GoFlexNet, with 128 MB RAM and now only one working SATA port on 3.6.0-rc1, with nr_ports = <1>. I also have an Iomega iConnect with 256 MB RAM, and only 128 MB accessible with 3.6.0-rc1. I used the appropriate DTB file for each, of course.
Buttzy,
What does your kernel boot log show for RAM on your ix2-200?
Edited 1 time(s). Last edit at 08/14/2012 12:10AM by rpress.
|
Re: kernel 3.5 and device-tree support... August 13, 2012 09:59PM |
Registered: 11 years ago Posts: 52 |
|
Re: kernel 3.5 and device-tree support... August 13, 2012 11:15PM |
Registered: 11 years ago Posts: 17 |
Here is my .config file for both:
Kernel config
And kernel log from the GFN:
GFN kernel log
I'll get the kernel log from the iConnect later if you want, but in any case it shows "Memory: 128MB = 128MB total"
Edited 1 time(s). Last edit at 08/13/2012 11:30PM by rpress.
Kernel config
And kernel log from the GFN:
GFN kernel log
I'll get the kernel log from the iConnect later if you want, but in any case it shows "Memory: 128MB = 128MB total"
Edited 1 time(s). Last edit at 08/13/2012 11:30PM by rpress.
|
Re: kernel 3.5 and device-tree support... August 14, 2012 03:53AM |
Registered: 11 years ago Posts: 115 |
|
Re: kernel 3.5 and device-tree support... August 14, 2012 05:02AM |
Registered: 11 years ago Posts: 52 |
Ok, I forgot to set CONFIG_SERIAL_OF_PLATFORM=y on my 3.6-rc1 test kernel. That with SATA set to 1 port has me booting into 3.6-rc1 cleanly. I'm going to retest with SATA set to two ports next.
Edit: 2 ports, same hang I've been chasing...
Edited 1 time(s). Last edit at 08/14/2012 05:28AM by Kurlon.
Edit: 2 ports, same hang I've been chasing...
Edited 1 time(s). Last edit at 08/14/2012 05:28AM by Kurlon.
|
Re: kernel 3.5 and device-tree support... August 14, 2012 05:21AM |
Registered: 11 years ago Posts: 115 |
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 my ix2-200 boots perfectly with it but set it back to 2 and it hangs so it's affecting all kirkwood's it would seem.
Seems like haveing bootargs set in uboot does interfere with the kernel booting i needed to enable
Edited 3 time(s). Last edit at 08/14/2012 08:17AM by Buttzy10169.
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 my ix2-200 boots perfectly with it but set it back to 2 and it hangs so it's affecting all kirkwood's it would seem.
Seems like haveing bootargs set in uboot does interfere with the kernel booting i needed to enable
CONFIG_ARM_ATAG_DTB_COMPATthen remove my bootagrs from uboot.
Edited 3 time(s). Last edit at 08/14/2012 08:17AM by Buttzy10169.
|
Re: kernel 3.5 and device-tree support... August 14, 2012 10:05AM |
Registered: 11 years ago Posts: 115 |
|
Re: kernel 3.5 and device-tree support... August 14, 2012 11:11AM |
Registered: 11 years ago Posts: 17 |
So I think my iConnect RAM problem is caused by U-boot not setting up the registers correctly. I tried to modify them in U-boot but it didn't work, so I need to JTAG now. Anyway when I get that figured out I think it will be ok.
Now that just leaves the sata_mv problem on my GFN, it's something pretty simple I'm guessing.
Now that just leaves the sata_mv problem on my GFN, it's something pretty simple I'm guessing.
|
Re: kernel 3.5 and device-tree support... August 14, 2012 12:05PM |
Registered: 11 years ago Posts: 115 |
|
Re: kernel 3.5 and device-tree support... August 14, 2012 07:00PM |
Registered: 11 years ago Posts: 52 |
|
Re: kernel 3.5 and device-tree support... August 14, 2012 07:51PM |
Registered: 11 years ago Posts: 52 |
