DTBs for Asus_m25, Netgear_Stora, Qizhitong_501m_v2.by bodhi - Debian
Sash, Try using the kernel 4.6 DTB with kernel 4.8: http://forum.doozan.com/read.php?2,12096,30563#msg-30563by bodhi - Debian
Looks like PCI is broken in kernel 4.8 due to the difference in DTS. So if you have the NSA325 v1/v2, the Pogo V4, and the Iomega ix4 200d, please replace the DTB with the kernel 4.6 DTB (attached in this post). mv /boot/dts/kirkwood-nsa325.dtb /boot/dts/kirkwood-nsa325.dtb.v4.8 cp -a kirkwood-nsa325.dtb /boot/dts/ mv /boot/dts/kirkwood-pogoplug_v4.dtb /boot/dts/kirkwood-pogoplug_v4by bodhi - Debian
Sash, Kernel 4.6 PCI is OK. Try install that version and let me know. QuoteUpdated 20 May 2016: Kernel linux-4.6.0-kirkwood-tld-1 package has been uploaded. The following features were added/updated:by bodhi - Debian
It's been a long time. So I'm not sure if this will work, try: ip route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1 dev wlan0 where 192.168.2.1 is your router.by bodhi - Debian
Problem with PCI (i.e. USB 3.0 and other PCIe interfaces) in kernel 4.8. Fixed in the following 3 posts.by bodhi - Debian
Sash Wrote: ------------------------------------------------------- > yep there seems to be a problem with the bus, else > there should be an output when calling lspci, > right!? > i have posted the dmesg above. PCI seems broken. I'm investigating this.by bodhi - Debian
Hold on to installing this kernel, possibly the USB 3.0 interface is broken.by bodhi - Debian
SiliCAT Wrote: ------------------------------------------------------- > Box: Pogoplug V4 > > Just updated to Kernel 4.8 Kirkwood (10 Oct > 2016). > Nothing happened when plugged in usb external hard > drive. Post serial console log. Or dmesg log after plugging the USB drive. Did it detect the drive in previous kernel?by bodhi - Debian
You could send PM to damacc, and hopefully damacc will reponds to forum post to tell us how the 4-bay setup should be. In the meantime, let's look at dmesg to see if PCIe is initialized OK.by bodhi - Debian
I see. damacc posted this in the first post: Quotedamacc After a lot research about the device tree and fiddling around with dts files I also managed to get the four sata ports and dual gigabit ports to work. There is a second sata controller on the PCI bus, and the ethernet interfaces had to be configured based on a very old kernel patch I found online that never made it into the kernel (httpby bodhi - Debian
bxwen Wrote: ------------------------------------------------------- > It is sort of work now. > > It didn't work in the first place, is because the > mt7601u.bin under /lib/firmware has 0 bytes. I > downloaded another one from github. Yes, usually you do need to take care of this for the RALINK. The good way to have this by default is to install the firmware-ralinkby bodhi - Debian
If you have serial console, power up and interrupt serial console, and do: ide reset See if stock u-boot does bring up all 4 drives. This is interesting: [ 8.822394] sata_mv f1080000.sata: slots 32 ports 2by bodhi - Debian
sodd Wrote: ------------------------------------------------------- > Hi Bodhi, > i would like to try install docker on my NSA310, > but when i checked dependences for than I stuck > with missing CONFIG_MEMCG in your kernel 4.6. So > my question is... Is it possible to include this > module to your next kernel release? > > Thx for you work ! Hi sodd, I didby bodhi - Debian
Sash, I'm really not worrying about upstream until before I retire from this forum :) I don't think the magic number number error has anything to do with arcNumber/machid. Usually, when you try to boot stock OS on NAND, its u-boot does a checksum and if it does not match what's in NAND then it refuses to boot. If you can find a consistent NAND mtds, it will boot OK. Iby bodhi - Debian
beggles, This usually has a couple of reasons. You should have posted the entire bootlog (not snipet where problem occurred). However, here are possible reasons: either your rootfs has file system errors, or the rootfs could not be mounted because of wrong u-boot envs for bootargs. Based on your u-boot envs, bootargs seems to be the cause. These envs were malformed: bootcmd=ide reset;by bodhi - uBoot
bxwen, The MT7601 module is already in the kernel 4.6-tld-1, no need to compile it separately. Try modprobe mt7601uby bodhi - Debian
Sash Wrote: ------------------------------------------------------- > he guys! > > i'm facing a little problem with my box. i guess > other have the same problem but nobody recognized > it so far. > > i uses the latest rootfs and the 4-8 kernel. > running fine so far, but is see the 2 of the 4 > sata ports missing. as is can see the port isnt > loadby bodhi - Debian
Kernel linux-4.8.0-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link.by bodhi - Debian
Cool! now you should install new u-boot and new default envs.by bodhi - Debian
Please post all the log files you have in text format, not screenshot. I need to to be able search the text. open | download - help.tiff (362.4 KB) open | download - printenv.tiff (259 KB) open | download - Version.tiff (72.1 KB) open | download - wrong_image.tiff (209.8 KB)by bodhi - Debian
audiocrush, > As I said... this thing is reeeeeeeally old. I > can't even remember when I got it. > It is not that old. The installed u-boot should be working perfectly. All your logs showed a good setup and there is notthing wrong. So my conclusion: your USB drive is no good. Try using a different one, such as a Sandisk brand USB flash drive. Format a single partition tby bodhi - Debian
audiocrush Wrote: ------------------------------------------------------- > Hi there, > > does anybody have an idea how I can sort this > out? > I have an old Goflex Net with uBoot version > 2011.12 (Apr 18 2012 ...) > With no rescue system installed an I really can't > manage to make this thing boot anything. > > Could someone point me in the rightby bodhi - Debian
Comment out this line will ensure that the MAC address is not read by udev (originally this line was uncommented): #SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="4c:9e:ff:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" So if the rootfs stays with one box (not reusedby bodhi - uBoot
Unknown532 Wrote: ------------------------------------------------------- > How is it possible to boot back to stock? If I > unplug the usb stick, the device stuck at "Bad > magic number" like described at the guide, but I > have read, that normally if there is no usb > device, the NAS will boot to stock... > > Edit: > > I have tried it with "by bodhi - Debian
Preacher, > > In NC I see "loading kernel", LED on USB-stick is > blinking for some time, then nothing happens. With netconsole, sometime that's all the output you will see during kernel booting. There shoud be a little bit tmore output, but the problem is most likely what I'm going to suggest a solution for below. > I have set the same IP-adress as forby bodhi - uBoot
Preacher, > But while V4 boots fine, mobile gets stuck after > loading kernel with same USB-stick, Doesn't load > until IP-adress is assigned. I'm not sure what you meant by "Doesn't load until IP-adress is assigned." ? > loading envs from usb 0 ... > usb > 1 bytes read in 123 ms (0 Bytes/s) What is the content of /boot/uEnv.txt fileby bodhi - uBoot
I've moved last post to its own thread: http://forum.doozan.com/read.php?3,30488by bodhi - uBoot
iamauser Wrote: ------------------------------------------------------- > Hi Bodhi, > > For some reason, after a recent reboot, ssh > service has crashed or something, I can't ssh into > the system. I don't have a console to see what's > going on ! Any suggestions ? > I have ordered a couple of USB-TTL cables to hook > up so that I can have a USB cby bodhi - uBoot