How about on kernel 4.4?by Yama - Debian
@Val So are you able to see CPU temperature and control the fan with fancontrol?by Yama - Debian
I have a 3.18.x, don't know exact version. Like echor told me, I got the OpenWRT patches for 3.18 and applied them. And also applied the patch from echor and used his config. I guess your compile failed, cause you didn't use his config maybe?by Yama - Debian
That would require to recompile uboot and flash it via UART, like bodhi mentions here. But you can let uboot automatically boot your own kernel with your own root, like I explained in my last post. How did you oversee it? oOby Yama - Debian
@echor Isn't that the same state from some months ago? Your patch also works on the 2-Bay NAS, I didn't do anything else than applying the OpenWRT patches and your patch. You say in the README.md, that the bootloader wants to boot from sda, but that was cause of your old config. uboot tries to boot from the internal flash. This is from the uboot source of the Central NAS: #defiby Yama - Debian
With the help of some friends, I found out, that the network is working on the 2-Bay NAS, too. I needed to assign a mac-address, cause it was set to 00:00:00:00:00 On Archlinux, I set it that way. $ cat /etc/systemd/network/eth0.network Name=eth0 DHCP=yes # Original Mac-Adresse of Port1 MACAddress=00:10:75:6E:83:32 I found the mac-addresses in uboot, with the command printeby Yama - Debian
Finally had time to test it. I loaded the kernel from tftp, but still the OS says Cannot assign requested addressby Yama - Debian
I tried more things out, like activating everything what has "CNS3XXX" in the name. Couldn't get USB, network and 512MB RAM to work, but the internal flash. I checked the original bootarg and yes, uboot loads the kernel with mem=512M. Our self compiled 2.6 kernels are able to boot with that, I already set up earlier to boot my kernel with my rootfs without interrupting uboot.by Yama - Debian
Found out how to boot to specific partition with using UUIDs. The kernel uses PARTUUID, which is "Disk identifier" on fdisk, displayed like: 0x06e268c9 You need the part after 0x and add "-01" or "-02" for the partitionnumber. root=PARTUUID=06e268c9-02 Add this in the kernel config to "CONFIG_CMDLINE" like in the config of echor. The kernel doesnby Yama - Debian
Compiled the kernel, applied all the patches and finally my system was up with kernel 3.18! Nice work dood :D SMP seems to work. USB not and I couldn't manage to get network working. I'm using the root from RPi of Archlinux. eth0 is shown, but down and I can't bring it up. On both ports the LEDs are flashing as I plug the network cable in. I noticed that you typed in /deby Yama - Debian
I plan to compile the kernel with the patches now, but I really have no clue where to start... All the files here are confusing me XDby Yama - Debian
QuoteARM Maintainer > Are you having ideas how we could make SMP and USB work? They should work with OpenWrt patches. IIRC the USB support require a cosmetic patch to compile (drivers/usb/dwc/otg_pcd.h contents must be disabled by #ifndef DWC_HOST_ONLY). You should simply enable SMP support and the DWC_OTG driver and both SMP and USB should be functional. USB could require some additby Yama - Debian
Wow... Amazed Yama is amazed :D Just posting to show my appreciation^^ I messaged the ARM maintainer again and update you as soon as I get an answer :)by Yama - Debian
Very nice work, dood! On Debian, we always had problems with DHCP. It only worked sporadically. Maybe try with another OS, like Arch or something, dunno. I guess you didn't look onto getting SMP to work?by Yama - Debian
bodhi Wrote: ------------------------------------------------------- > Not sure why. I think Val did compile OK with the > patch. Are you using the same config file? Yes, just added cross-compile prefix and set the two lines for sata to yby Yama - Debian
So Bodhi? Val said, that it doesn't recognizes the drives even with both options set to y. I wasn't able to compile from source. First it was asking for the two files: tools/be_byteshift.h tools/le_byteshift.h After I found em and typed the full paths in scripts/sortextable.c many unknown type errors appeared: HOSTCC scripts/sortextable In file included from scripts/soby Yama - Debian
The same root works on the kernel v2.6. I am also loading the uImage from the same device but other partition, so uboot recognizes the hard drive, but not the kernel. Like blackdevil said, the kernel v3 might be missing the sata drivers. Don't know how easy it will be to port the Seagate sata drivers to the newer kernel. I would upload the patches, but I am not at home. Anyway, iamneby Yama - Debian
I made a template of uboot commands based on several posts in the original thread for this device: #Next two lines only for tftp booting setenv serverip 192.168.1.102;setenv tftp_serverip 192.168.1.102; setenv ipaddr 192.168.1.103 setenv bootcmd_load 'tftp 0x800000 uImage;tftp 0x1100000 uInitrd' #Next one line only for loading from drive setenv bootcmd_load 'scsi init;fatlby Yama - Debian
Right, only USB 3.0 ports, one on back, one front. No USB 2.0 ports.by Yama - Debian
bodhi Wrote: ------------------------------------------------------- > Yama & blackdevil, > > Sure I will if I could get to my development box. > But can't promise that will happen before a few > weeks passes (I did not prepare the patch, since > it is still under testing). And I want to see if > anybody can boot Debian and identify what's > missingby Yama - Debian
Well, nobody knows if it works or not :D And since he can't provide new builds for few weeks, we might be able to work on it ourself after his great help :)by Yama - Debian
Bodhi, you forgot to upload the prepatched source inlcuding config? :/ I thought you would do that xD We need to compile it ourself in order to be able to boot directly to our own rootfs without canceling uboot.by Yama - Debian
Whitney # printenv bootargs=root=/dev/mtdblock0 mem=256M console=ttyS0 baudrate=38400 ipaddr=192.168.1.2 port=0 boardtest_state_memory=none model_name=whitney_2bay cpu_clock=700 mfgmodel=halfdome netmask=255.255.0.0 bootfile="/tftpboot/uImage" tftp_bsize=512 udp_frag_size=512 whitney_state=saved opid=Z1290178 hddlocation=T hddpn=1CH164-515 eby Yama - Debian
Like this? Same result :/ > dpkg -i linux-image-4.0.0-cns3xxx-tld-1_0.1_armel.deb Selecting previously unselected package linux-image-4.0.0-cns3xxx-tld-1. (Reading database ... 21817 files and directories currently installed.) Preparing to unpack linux-image-4.0.0-cns3xxx-tld-1_0.1_armel.deb ... Examining /etc/kernel/preinst.d/ Done. Unpacking linux-image-4.0.0-cns3xxx-tld-1 (0.1)by Yama - Debian
Nope... The uImage is really smal, just 2.1mb. Commands I used: wget https://www.dropbox.com/s/9iwa5keqvbutevt/linux-image-4.0.0-cns3xxx-tld-1_0.1_armel.deb?dl=1 ar -x linux-image-4.0.0-cns3xxx-tld-1_0.1_armel.deb?dl=1 mkdir kernel-4.0 cd kernel-4.0 tar xf ../data.tar.xz mkimage -A arm -O linux -a 0x2000000 -a 0x2000000 -T kernel -C none -d boot/vmlinuz-4.0.0-cns3xxx-tld-1 -n linux uIby Yama - Debian
Only via svn, which really sucked. I attached it. I hope I didn't modified anything^^by Yama - Debian
I texted the ARM-Maintainer to get help regarding to make kernel v3 working. This is the answer: Quote Have you tried booting a recent kernel, something like 3.17 or later? There were some issues in older kernels (I have to check if all of them are resolved). Some stuff (IIRC Ethernet and SMP) is included in OpenWrt and can quite easily be ported to Linux. The official Linux may be missiby Yama - Debian
Uh, this member just read randomly here and gave you ideas? :D I did not tried UART booting. My device has the exact same output like iamnewbie's device. I am looking forward for your results, bodhi :D The kernel source provided here works, but only on one CPU core. And if I'm right, the kernel is from the Central source. Which isn't our device. I'm trying to comby Yama - Debian
Yes, I am using the first Jessie rootfs "This rootfs is the first Debian jessie rootfs..." Well, I'm not sure if there are errors, but my goal is to get a kernel on version 3 working, so Arch Linux boots on it. The arm-code maintainer wrote me, that he is able to boot vanilla kernels on a CNS3XXX hardware, on only one core and without network support. Well, the "one core&by Yama - Debian
I also was only able to compile the source which is shared in this thread. But this kernel works only on one CPU core. Thats why i tried to compile the right source for our device (the not-Central source) but the compiling fails. I will try again someday. For cross-compiling you need the packages for cross-compiling. Install gcc-arm-linux-gnueabi and always put ARCH=arm to your compiling comby Yama - Debian