cdlenfert Wrote: ------------------------------------------------------- > Oh nice. I didn't know you could set up a read onl > y mode for Wheezy. For a dedicated device like an > airplay speaker that makes a lot of sense. I manag > ed to tweak settings a bit and make the volume con > trol a lot better. In my testing the Pogoplug hasn > 't dropped a stream nearlby bodhi - Debian
OK. I think I know why. Most likely because there is no power regulator for the USB yet. Update: Yup. That was it. There is no power to the USB ports right now (I had to implement that for the NAS326 DTS starting from a reference board 38x DTS). So this current DTS and one from hmartin zip file will not power up the USB ports. I'll modify the DTS and upload it.by bodhi - Debian
Use a USB 3.0 stick or a different stick might help. [ 2.098806] usb 2-1: New USB device found, idVendor=045b, idProduct=0209 [ 2.105544] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.113073] hub 2-1:1.0: USB hub found [ 2.116903] hub 2-1:1.0: 4 ports detected [ 2.238774] usb 3-1: new SuperSpeed USB device number 2 using xhci-hcd [ 2.270181] usbby bodhi - Debian
> XHCI is built into the kernel. So it is not the sl > owness of module loading. This works fine in the N > AS326 box. I'll compare with the NAS326 log to se > e if anything stands out. > I need to review 4.9 kernel config. Perhaps you guys need to install 4.10.9 kernel. Update: Nope. XHCI is the same in 4.9 and 4.10.9.by bodhi - Debian
hmartin Wrote: ------------------------------------------------------- > Quotebodhi > I see. Does this EX4100 have USB 2.0 port? You are > using USB 3.0. > > > Neither EX2100 or EX4100 have a USB 2.0 port, all > populated USB ports are USB 3.0 > > Is this simply a problem because the xhci module i > sn't loaded soon enough in the boot process to finby bodhi - Debian
saschadd, > USB0: Port (usbActive) : 0 Interface (usbType > = 3) : USB XHCI 1.00 > scanning bus 0 for devices... 4 USB Device(s) foun > d > scanning usb for storage devices... 1 Stora > ge Device(s) found > scanning usb for ethernet devices... 0 Ethe > rnet Device(s) found > Booting from USB ... > (Re)start USB... > USB0: Port (usbActive) : 0by bodhi - Debian
- Temporarily remove any HDD that you have attached. - and revise the uboot envs to boot this way (the bold line is the modified env). setenv bootdev usb setenv device '0:1' setenv dtb_file '/boot/dts/armada-385-wd-ex4100.dtb' setenv load_dtb_addr 0x1000000 setenv load_initrd_addr 0x3900000 setenv load_image_addr 0x02000000 setenv load_dtb 'echo loading DTBby bodhi - Debian
hmartin, > No problem, I am booting from tftp, so there are n > o SATA drives anyway. Hence I could put the rootfs > on a USB stick and use /dev/sda. If the drivers fo > r ext3/4 and usb are compiled into the kernel and > not modules, then no initrd is required. > > I am actually here for other motives. I want a wor > king mainline kernel and then I plan to builby bodhi - Debian
hmartin, > Could you share your kernel .config and the dts fo > r armada-385-wd-ex4100.dtb? Sure. You already have the kernel .config in the tarball. I'll post the DTS.by bodhi - Debian
All, Very good tests :) Just briefly scanning the boot log, I think I'm on the right track thinking that the loading of uInitrd that caused problem. saschadd log is a good indicator that the kernel and the DTB file are correctly executed. Marvell>> setenv bootdev usb Marvell>> setenv device '0:1' Marvell>> setenv dtb_file '/boot/dts/armada-385-wby bodhi - Debian
saschadd & hmartin, Stock u-boot behavior is a little bit weird to me. What will we see when booting without initrd? we will not be able to mount the rootfs, but let's see if the problem is in where the initramfs was loaded. setenv bootdev usb setenv device '0:1' setenv dtb_file '/boot/dts/armada-385-wd-ex4100.dtb' setenv load_dtb_addr 0x1000000 setenvby bodhi - Debian
csulaguy Wrote: ------------------------------------------------------- > Is there any way to unbrick a T5325? I issued a fw > _setenv command from my completed install (bodhi's > 4.4.0), and the device no longer brings up uboot. > I confimed my cable setup works, as I have another > T5325 that still brings up uboot and bootstraps pr > operly. I'm wondering if Iby bodhi - Debian
Hi hmartin, > This might be common knowledge already, but I thin > k I found the dtb that Western Digital is using fo > r the EX2100/4100: Cool :) This might help in coming up with the new DTS. > EDIT: derp, didn't see page 2 of this thread. bodh > i any chance for a 385 DTB? I'm using the EX2100. > I tried the DTB for EX4100 (load addresses for the >by bodhi - Debian
pengu Wrote: ------------------------------------------------------- > yes, this seems the only working "envs" > > other than ghis gives me a > > > pc : [<0064c700>] lr : [<00620da0>] > sp : 005fb1d0 ip : 00000003 fp : 00000002 > r10: 00690c80 r9 : 00000001 r8 : 005fffcc > r7 : dc87b18b r6 : c19c3a76 r5 : 93e752by bodhi - Debian
Let's try setenv bootdev usb setenv device '0:1' setenv dtb_file '/boot/dts/armada-385-wd-ex4100.dtb' setenv load_dtb_addr 0x1000000 setenv load_initrd_addr 0x3900000 setenv load_image_addr 0x02000000 setenv load_dtb 'echo loading DTB $dtb_file ...; ext2load $bootdev $device $load_dtb_addr $dtb_file' setenv load_initrd 'echo loading uInitrd ..by bodhi - Debian
This does not look right setenv load_initrd_addr 0x02900000 setenv load_image_addr 0x02000000 Probably my typo. Update: No. I took it back. It is not a typo.by bodhi - Debian
saschadd Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > saschadd, > > > > Your boot log showed 88F6820 (unless its u-boot > wa > > s wrong). > > > > QuoteMarvell HW specs > > ARMADA 380 (88F6810) – Single-core ARM CPU > > by bodhi - Debian
saschadd, Your boot log showed 88F6820 (unless its u-boot was wrong). QuoteMarvell HW specs ARMADA 380 (88F6810) – Single-core ARM CPU ARMADA 385 (88F6820) – Dual-core ARM CPU ARMADA 388 (88F6828) – Dual-core ARM CPUby bodhi - Debian
Samba QuoteDebian Security Advisory DSA-3860-1 security@debian.org https://www.debian.org/security/ Salvatore Bonaccorso May 24, 2017 https://www.debian.org/security/faq - ------------------------------------------------------------------------- Package : samba CVE ID : CVE-2017-7494 steelo discovered a remby bodhi - Debian
saschadd, Here is the armada-385-wd-ex4100.dtb (attached in this post). Note: you 'll have only 2 SATA drives in this version. Please try.by bodhi - Debian
umd Wrote: ------------------------------------------------------- > >Update: > > >Note: if you use netconsole, then the IP 192.168. > 0.xx should be the same one as defined in u-boot e > nv for ipaddr. > > >-bodhi > > > Makes sense. Would you recommend choosing a static > IP somewhere within the DHCP range? I would not use one in the rby bodhi - uBoot
bodhi Wrote: ------------------------------------------------------- > umd, > > > It looks like a new Debian stick seems to have f > ix > > ed it. It booted with the correct MAC. > > Cool! > > It is a good solution to use static IP. > > Add in /etc/network/interfaces, like: > > > auto lo eth0 > iface lo inet loopback > iby bodhi - uBoot
balanga, Basically all correct, except one important requirement that you did not mention. Before starting, you must log in as root. This is basically step 0. > 1. Format a new USB drive with a single Ext3 parti > tion, and label it rootfs. > > 2. Mount the drive on a Linux box. cd to top level > directory and extract it (https://bitly.com/20KHWq > 5). > >by bodhi - uBoot
Trond Melen, Your info is a different setting (not GPIO). Power Button GPIO key is 36. And Reset Button GPIO key is 38. So to implement these actions, GPO keys cannot be used. It probably needs to be monitored as input event data.by bodhi - Debian
iomega ez, > looks ok to me? Looks OK, but not enough info. You are very close to boot Debian on USB rootfs. Since you can log into stock: Quote/root $ uname -a Linux EZ 2.6.31.8 Thu Aug 22 17:40:31 KST 2013 v0.0.9 Thu Aug 22 17:40:31 KST 2013 armv5tel GNU/Linux You can check the usb rootfs at the Linux prompt, like I described previously. - Check file system for errors:by bodhi - Debian
Trond Melen, > believe "34+Y*" is "POWER button pushed" and "44+Y > *" is "POWER button released": Thanks for the info! I'll take a look at the kernel DTS for the Stora, perhaps it needs some modification.by bodhi - Debian
Trond Melen, Since we are running the latest kernel (not stock), we need to set up to use Power button (and other buttons) this way: http://forum.doozan.com/read.php?2,32460,32467#msg-32467by bodhi - Debian
umd, > It looks like a new Debian stick seems to have fix > ed it. It booted with the correct MAC. Cool! It is a good solution to use static IP. Add in /etc/network/interfaces, like: auto lo eth0 iface lo inet loopback iface eth0 inet static address 192.168.0.xx netmask 255.255.255.0 gateway 192.168.0.1 where 192.168.0.1 is your router IP. xxby bodhi - uBoot
Mount on a Linux box and assuming it is assigned as /dev/sdb1 Check file system: e2fsck /dev/sdb1 Check label: e2label /dev/sdb1 Mount to /media and check /boot folder files attributes: ls -lart /media/sdb1/bootby bodhi - Debian
Very encouraging. Kernel has booted ok. But your rootfs might have some problem. Retrace your steps when you created the rootfs. Were you root user when running tar? Was the rootfs partion labeled rootfs (lower case)?by bodhi - Debian