blackdevil Wrote: ------------------------------------------------------- > @MarkTurner, > I would be great to get PCI express and with that > USB 3.0 working. I tried it and found no way :( > > @tommy79, > Booting with the netboot command is a nice > workaround, thanks :-) I'm glad I was able to help you with the netboot trick :) blackdevil, I have theby tommy79 - Debian
MarkTurner Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > > So when you set envs to boot into kernel 4.4.x > and > > used saveenv before boot, it did not stick to > the > > next boot? did you have any error or it was > just > > silently not executingby tommy79 - Debian
Mark, Did you use my config (with SATA_PMP enabled) or your config? I saw some options are different in your config.by tommy79 - Debian
Mark, I enabled this CONFIG_SATA_PMP but the result was that none of the drives got recognized....by tommy79 - Debian
Hi again, You can check the sourcecode: https://www.dropbox.com/s/4c9jhtajmzxqcb6/linux-4.4.121-tommy.tar.gz?dl=0 blackdevil, I have no idea what is wrong. The pcie driver is picky. Today in my box after few reboots pcie&usb stopped working, I unpluged all cables (power, ethernet, uart cable), plugged again and it resumed working. I am trying to find out any pattern when it is workingby tommy79 - Debian
blackdevil Wrote: ------------------------------------------------------- > I think PCIe is not working and so USB is not working too. > PCI-E0 uses external clock source. > PCIe: Port[0] Enable PCIe LTSSM > PCIe: Port[0] Check data link layer... > > > > Device not found. > It should be "Link up" in the log instead of "Device not found&quby tommy79 - Debian
blackdevil Wrote: ------------------------------------------------------- > tommy, I cannot boot with bootargs from uboot. I > have to compile the bootargs into the kernel. i > will give it a try when you uploaded the kernel > and compile it myself. > > thank you! blackdevil, Why can't you run following code in u-boot? It works for me setenv bootargs 'by tommy79 - Debian
MarkTurner Wrote: ------------------------------------------------------- > tommy79 Wrote: > ------------------------------------------------------- > > > > Please test and let me know what are your > opinions > > :) > > Also, when can I get your source code? :-) Hi Mark, I will try to publish tomorrow, I do not have time todayby tommy79 - Debian
blackdevil Wrote: ------------------------------------------------------- > Hi tommy, > I tested the kernel on my 2-bay NAS. It starts > loading but dont get far. Also tested with > 0x800000 and 0x2000000 as address. > > > Whitney # setenv loaduimage 'ext2load scsi 0 > 0x28000000 /boot/uImage.tommy' > Whitney # setenv bootcmd_scsi 'scsi init;by tommy79 - Debian
Hi All, You can check this out: https://www.dropbox.com/sh/vc0suib2su60b0d/AAA2lXRE2j5DfwO-VVFWVeYEa?dl=0 This is my brand new 4.4.121 kernel and modules for our machines :) I used mainline newest 4.4 kernel and applied patches from here: https://github.com/KL-Yang/seagate_central_linux This was the foundation and on top of this I ported a lot of stuff from Seagate's 2.65 kernel.by tommy79 - Debian
I do not use initrd. I do not know how to handle this, but you may try to increase all adresses you use by 0x20000000. It means use 0x21100000 instead of 0x1100000 and so on. Your init ramdisk is loaded at 00000000 while I think it should at 20000000. Check if you can supply LOADADDR when building ramdisk and try to change it to 20000000by tommy79 - Debian
First I tried to patch the kernel, i.e. tried to port the fixup function from 2.65 kernel. But it did not work as the PHYS_OFFSET, which defined the start of physical memory in 2.65, on current kernel (at least for our architecture) can't be set to anything else than 0x00000000. So I assumed it somehow has to be passed in kernel args and then I found out that we can set the starting point ofby tommy79 - Debian
Hi All, I found out how to run 2-bay box (and most likely 4-bay as well) with 512MB of RAM:) I am using kernel 4.4.88 I mentioned above. To do this you actually do not need to patch the kernel. You only change LOADADDR for uImage and change kernel parameters. Our boxes have 512MB of ram and its physical adress is 0x20000000 to 0x3FFFFFFF. Out of it 256MB is mirrored at 0x00000000 to 0x0FFFby tommy79 - Debian
Mark, chech this repo: https://github.com/KL-Yang/seagate_central_linux This is the 4.4.88 kernel that I mentioned above. It has some patches on smp, ethernet, etc. but many things still missing (rtc, fancontrol, usb, problems with poweroff).by tommy79 - Debian
nothing changed Whitney # tftp 0x02000000 uImage41424 TFTP from server 192.168.1.1; our IP address is 192.168.1.154 Filename 'uImage41424'. Load address: 0x2000000 Loading: ################################################################# ################################################################# #######################################################by tommy79 - Debian
This is Makefile.boot from 4.4.88 kernel that is working for us, Maybe this will be helpful as it sets atag, right? zreladdr-y += 0x00008000 params_phys-y := 0x00000100 initrd_phys-y := 0x00C00000by tommy79 - Debian
Hi bodhi, I think the problem why the kernel is not booting might be memory map/offsets. In your dts you declare RAM starting at 0x00000000 (and its size 256MB) + memory { + /* 256MB at address 0 */ + reg = <0x00000000 0x10000000>; + }; while in Seagate's sources it starts at 0x20000000 /* * Memory map */ #define CNS3XXX_FLASH_BASE 0x10000000 /* Flash/SRAMby tommy79 - Debian
And I can confirm what Mark wrote that our u-boot apparently doesn't have usb enabled, as I also failed to load or boot anything from usb disc or pen.by tommy79 - Debian