@erwin, Try this: unplug the SSD, boot with USB. After it booted into Debian, plug in the Sandisk SDD. Do you see the kernel recognizing and initializing the SSD ? I am hoping the behavior is the same as we've seen with the Sandisk Readycache SSD. Eventhough u-boot failed to detect the identity of the SSD, Debian will detect it just fine. If that is the case, then it can be used as theby bodhi - uBoot
Ah! looks like it is the same problem as the Readycache Sandisk SSD. Reset IDE: Bus 0: OK Bus 1: not available Device 0: Model: ?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?� Firm: ?�?�?�?� Ser#: ?�?�?�?�?�?�?�?�?�?� Type: Hard Disk Supports 48-bit addressing Capacity: 427923841.5 MB = 417894.3 GB (4611474908973580287 x 5by bodhi - uBoot
erwin Wrote: ------------------------------------------------------- > The info seams correct for me. (I have reported 4 > chars to less in ser#, copy paste error) > I cannot find the firmware version on sandisk > site. > Its this thing. > http://www.sandisk.com/products/ssd/sata/standard/ > #Specifications > > dmesg | grep ata[12] > [ 12.784613] ata1:by bodhi - uBoot
erwin Wrote: ------------------------------------------------------- > Hello, > > I have a boot problem with a 6G/s SSD. (1.5 G/s WD > drive works fine) > > U-Boot 2014.07-tld-2 (Sep 20 2014 - 00:58:11) > Seagate GoFlex Net > gcc (Debian 4.6.3-14) 4.6.3 > GNU ld (GNU Binutils for Debian) 2.22 > Hit any key to stop autoboot: 0 > (Re)start USB... &gby bodhi - uBoot
Although it seems we don't have a lot of users with Allwinner devices, this is interesting nonetheless for a few who do. This means a patch is available to build Debian kernel.by bodhi - Allwinner A10
pbg4, Thanks for the confirmation: Quotethis is just another verification that your latest uBoot i.e. NSA320 u-boot 2014.07-tld-3 image worked fine with uart booting and kwboot on a NSA320 box here, so I flashed it and configured the uboot envs and its running properly with only minor issue,by bodhi - uBoot
East2West, I plan to investigate this problem in a couple weeks when I have more time.by bodhi - uBoot
dalin, > what should i do if i want boot from sata? You and Peter are looking for the same thing: http://forum.doozan.com/read.php?3,22226 I'm on the road, away from my development environment, so I was hoping others who have installed this u-boot and boots from SATA will help by posting their u-boot envs. Let's wait for a day or two to see if anybody is going to do thaby bodhi - uBoot
@dalin, > Do I need to make a USB system on the portable > hdd,boot from USB and do the operation on it? This is the best approach. Since you have installed the new u-boot, you can boot from either USB or HDD. > I saw this uboot support booting from tftp/nfs, > can i just boot from network?if so, how? > You can load the kernel that way, but you still need the wholeby bodhi - uBoot
@leo, Sorry this is possibly the kernel headers mistmatched, since the module was from kernel 4.0. The solution is either: - I have to compile this module in kernel 3.18.5 for you. Or, - You need to install kernel 4.0 I'm away from my development environment, so I can't do that until at least a couple weeks form now. I think you should upgrade to kernel 4.0.0-kirwood-tld-2.by bodhi - Debian
@leo, Here is the hwmon module. Extract this ko file and put this in: /lib/modules/3.18.5-kirkwood-tld-1/kernel/drivers/hwmon Try to modprobe this and see if you can use it. According to pbg4 above, it lacks some GPIOs so we need to fix the DTS so it will provide full functionality. However, just the module itself might be useful for you to confirm that it is running OK. Once we have theby bodhi - Debian
pbg4, > as you own a nsa325, is the nsa3xx-hwmon included > in linux-4.0.0-kirkwood-tld-2driver working for > you properly with the > nsa325 ?? The NSA325 does not use nsaxx-hwmon module. The sensors are controlled automatically in hardware (e.g. we can't control fan speed). To read the sensors output, we have to use i2c. Hence, I can't verify the hwnmon for other nby bodhi - Debian
pbg4, > the linux devs who made the transition from > nsa320-setup.c where everything was contained > in the pre dts time simply looked if there is a > driver requesting it, as the nsa3xx-hwmon never > got upstream, > the GPIO's were not included, but it should be > relatively easy to add this, if I have some time, > maybe > I'll give it a try,by bodhi - Debian
leo Wrote: ------------------------------------------------------- > hello bodhi, > > thank you for reply. I would rather stay with 3.18 > for now (too much to learn ab. upates:) > > regards, In that case, I will upload the module and you can modprobe it.by bodhi - Debian
@pbg4, 1. problems with the sandisk ultra fit usb 3.0 stick: Yes, I think this is definitely the problem with the Sandisk Ultra Fit USB 3.0. This is possibly can be resolved with a quirk, but we don't know what that quirk should be. 2. sandisk ssd problem Yes, it seems some Sandisk SSDs have some kind of timing problem. We've seen this exact behavior with the Sandisk Readycby bodhi - uBoot
leo, Kernel 4.0 has the module. Do you need to stay with 3.18 or can you update to linux-4.0.0-kirkwood-tld-2 ?by bodhi - Debian
workingman, > Apparently the uboot that they include with the > RPi NAS has all the goodness but I'm not getting > it to chainload correctly. I don't think you can use the rPi rootfs, if that's what you are trying to do. And I don't think chainloading that u-boot will work, either. If BSD require UFS file system then our GoFlex Net u-boot needs to either haveby bodhi - Off-Topic
aquaboy, Have you tried sudo su whoamiby bodhi - uBoot
aquaboy, > I formatted to EXT2 only because uboot is > specifically looking for EXT2 extension. I will > try to change this to EXT3 tonight and do the > process of extraction again. The default u-boot env for rootfs type is Ext3. Don't be mislead by the command name extt2load, it is just a command that will load files from ext2/ext3 file system. rootfstype=ext3 Youby bodhi - uBoot
Val532 Wrote: ------------------------------------------------------- > Hi, > > I think we have a big probleme, where is the sata > driver ?!? > > In 2.35 kernel source i found in drivers/ata > cns3xxx_ahci.c and not in 3.18 source. > > I think it's not needed to search anoter reason > for what it does not work. > > There are some missingby bodhi - Debian
dips0502, > Ah..I see. There are actually 2 partitions on the > HDD. Both are of type ext3. I thought if I labeled > the partition holding rootfs as 'rootfs', it'll > do. Exactly! if there is one partition then the partition label is not that important. When there are more than one partition, regardless whether they are in the same drive or in different drivesby bodhi - Debian
pengu, 325 GPIOs are different from the 310S. Perhaps the 310 GPIOs are the correct ones to use.by bodhi - Debian
dips0502, This is the rootfs mounting problem. Make sure the following were done: - There is only one partition on the HDD. And this partition is labeled rootfs. This partition should be type Ext3. - The copying command cp -aR were executed while you are root user (not sudo). The copying must be done on a different Linux box. Try booting after you've made adjustments as above. If iby bodhi - Debian
sylvester Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > Yes, it is normal. And you do need to > regenerate > > uInitrd so that the new packages hooks are > used. > > Old uInird is still usable for booting, but > will > > point to the older hooks. &by bodhi - Debian
sylvester Wrote: ------------------------------------------------------- > I just carried out "apt-get upgrade" the first > time after upgrading to jessie. > > I noticed it regenerated initrd.img in the last > step: > > > Setting up php5 (5.6.9+dfsg-0+deb8u1) ... > Processing triggers for libc-bin (2.19-18) ... > Processing triggers for initraby bodhi - Debian
workingman, > Any interest around here in getting BSD kernels > booting on kirkwood? I am a willing and hopefully > capable tester! What does the BSD rootfs look like? if you could show the top level content of this I might be able to help in getting it booted. For example, these or their equivalences: ls -l / ls -l /boot ls -l /lib/modules I'm not familiar with BSby bodhi - Off-Topic
I've made this a separate topic in this u-boot forum so that others who already have this setup will notice and help (ATM, I don't have access to my development environment). Please post your current u-boot envs to help Peter, if you are booting your Pogo V3 with HDD, and have set it up so that it will try USB if the HDD is not plugged in.by bodhi - uBoot
zzbao, sda1 is what assigned to the USB drive. So that's is always what the kernel looking for to mount rootfs. A couple things that are possibly wrong: 1. Did you label the USB rootfs as rootfs? 2. Also, this is not right, since you have append the DTB to uImage. This is for booting with a separate DTB: usb_boot=run load_dtb; run load_uimage; if run load_initrd; then bootm 0xby bodhi - Debian
dips0502, Take a look at this post. I explained the booting process with multiple drives: http://forum.doozan.com/read.php?3,19093by bodhi - Debian
dips0502, Cool! everything looks great. The warning messages were expected, since you only have USB drive (no HDD or SD).by bodhi - Debian