@tanya, I don't see the card being detected at all in serial boot log either. It seems to point to a HW problem, i.e. it's incompatible. However, I will have to verify that. When I have sometime, I'll plug in my Atheros card and see what happen. Usually even if the kernel does not have driver for it (this kernel does), the device is stil detected by the kernel.by bodhi - Debian
AA666, > Works fine for me on NSA320. Just booted from USB > stick 3.18.5-kirkwood-tld-1 kernel and rootfs. Thanks for confirming.by bodhi - uBoot
I don't have anything better to offer other than Almaz and Gravelrash already said, but am interested in how this problem is solved! @tufkal, Even though the kernel config is mostly the same between mainline Debianwheezy and my config, I think you've probly overlooked this point: if you install from mainline, there are a lot of default configurations settings were done by that pby bodhi - Debian
@Waynosan, You need to verify these: - Check if you have used the copy command cp -aR while logged in as root. - After cloning the rootfs, check udev rules files: http://forum.doozan.com/read.php?2,18007,18008#msg-18008 Also, if the USB flash drive is plugged in, u-boot envs should be modified to boot with both drives attached.by bodhi - uBoot
InfoScav, > 2. will also be connecting an HDD via SATA to the > plug. would you recommend installing debian to > that instead and booting from it? or USB is fine? As Gravelrash said, if you're going to do something that will be disk I/O intensive then HDD is a must. However, it does not mean in all cases that the rootfs must be on it. 1) if you are going to compile appliby bodhi - Debian
@Almaz, Which kernel are you running (uname -a) that works for TUN/TAP as you've mentioned here?by bodhi - Debian
@Felipe, Please redo the flashing, get only the relevant commands and their output and post here.by bodhi - uBoot
@Joe, It looks normal. And you've already swapped the cable and switch port. So I think could it be other software you have running in your system? Are there daemons running that could have been monitoring the network status, i.e. errounously brought the link down? 5 minutes interval is very suspected.by bodhi - Debian
@Joe, I have no idea why. Perhaps you could post the entire dmesg log? I don't see this behavior on my NSA325v2. BTW, I'm running sysvinit, but left systemd intact: apt-get install sysvinit-core sysvinit sysvinit-utils and add this to the kernel bootargs when I want to boot with systemd: init=/bin/systemdby bodhi - Debian
LeggoMyEggo, > would be nice to have bluetooth to use it for BT > audio to connect to a a bluetooth speaker for use > with the Shairport client I am running > (http://drewlustro.com/hi-fi-audio-via-airplay-on- > raspberry-pi/). The AR9485 uses the Ath3k > driver.for bluetooth. I'll take a look.by bodhi - Debian
@ InfoScav, You can update it to 3.18.5 kernel using the above steps, but step 6 is not needed, since you have already done it during u-boot installation. Look at your current fw_printenv output and compare it with the ones listed in step 6. BTW, the Pogo V3 rootfs can not be upgraded to jessie, atm, because of systemd dependency is not satisfied. So stay with wheezy until my next Oxnas kerby bodhi - Debian
@ Robert, OK, will include it for kernel 4.0. I think it will be out in the near future.by bodhi - Debian
morph027 Wrote: ------------------------------------------------------- > Upgrading to newer version needs some changes when > booting from SATA (at least here in my case, as > ide command does not know start/stop > anymore) > > I've changed > > > dt_bootcmd_ide=ide start; run dt_ide_bootcmd; ide > stop; reset > > > > to > &gby bodhi - uBoot
> 2. It is fun when people hear the gong and start > looking around for a clock. :)) cool! thanks.by bodhi - Debian
Hey everybody, Please try to post a new different Debian topic if you can (but of course do post here if you think it is something to do with this kernel). I lost track of which post that I have not answered (there is no way of marking a post as unread :) Thanks.by bodhi - Debian
@tanya, It does not seem that your card was recognized at all. Try reinsert it again. Usually, even if the kernel does not have module supports, the card would appear on the list when you do lspci. For example, for the iConnect stock Wifi card: dmesg: [ 0.969969] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00 [ 0.969993] pci_bus 0000:00: root bus resource [by bodhi - Debian
FelipeC Wrote: ------------------------------------------------------- > Ok Bodhi, so rootfs is running now, however, i > can't make the flash_erase to be recognized. also, > still confused with the MTD1, mtd2, mtd3 and mtd4 > restore. How should i define the number of blocks > for each one. > > thanks in advance. In the new rootfs, to get all the NAND tools,by bodhi - uBoot
electrosam, The Pogo V4 is a different SoC, albeit in the Kirkwood series, but it is different enough that its u-boot can't start the E02/Dockstar/GoFlexHome boxes . So with the Pogo E02, the ony way to revive it is JTAG.by bodhi - Rescue System
electrosam, > Yes, but speaking of uboot, I think I flashed V4 > boot image with erase flash and nandump commands. This is bad news. Again, try swapping the TX and RX just in case.by bodhi - Rescue System
electrosam Wrote: ------------------------------------------------------- > Thanks a lot for reply Bodhi. > Here are putty settings I used- > Baud = 125200 > COM3 > Data Bits 8 > Stop Bits 1 > Parity - None > Flow Control - None > > Why is it sending just zero! If you have kept the log of your installation, look into it and let us know if you have insby bodhi - Rescue System
electrosam Wrote: ------------------------------------------------------- > Bad news :( > I was able to open, connect serial. Connection > seems right, GND, Rx, Tx and 3.3v/5v from serial > cable not connected. > > Opened putty with 115200 baud and NO xon/xoff > control. Shows me garbage on poweron. > Then used hterm, and noticed it sends me one or > two 00.by bodhi - Rescue System
@InfoScav, This step might be the problem: > 4. Create uImage with embbeded DTB to run with > older u-boot. Please see Note 2 below if you are > running this kernel witht the new U-Boot. > > Pogo Pro vs. Pogo Classic: If you're installing > this on a Pogo V3 Classic (no PCI), replace the > ox820-pogoplug-pro.dtb below with > ox820-pogoplug-classic.dtb.by bodhi - Debian
@jfp, I have not seen this problem on my boxes. Are you running systemd? try switch back to sysvinit to see if it makes any difference.by bodhi - Debian
tufkal Wrote: ------------------------------------------------------- > Bodhi, > > Does your kernel support TUN/TAP for using things > like OpenVPN and N2N? I compiled a copy last > night and everything seems OK but I am getting no > connection. Yes. It does have TUN in kernel config.by bodhi - Debian
Val532, Try UART bootng with this attached kwb file, the bin binary won't work with UART.by bodhi - uBoot
@Val532, Try this attached bin: tftp 0x80000 uboot.2014.07-tld-3.d2net_v2.bin go 0x80000 I'm not sure that it's going to work chainloading from a much older u-boot to this version. But it's worth a try :)by bodhi - uBoot
Val532 Wrote: ------------------------------------------------------- > Sorry but it's not the netspace_v2 but the D2 > network v2. > And in this web site i have not found > d2-network_v2_config or something else. So you do indeed have the D2 Net V2, not the Nespace V2. That's what I did built the image for previously. This D2Net_V2 variant has arcNumber 2203. OKby bodhi - uBoot
Val532 Wrote: ------------------------------------------------------- > @bodhi > > So i tried to load it by tftp methode by this way > : > > tftp 0x800000 uboot.kwb (i rename the file) > then > go 0x800200 > > and nothing happens. > > I found on the net a uboot ( version 2011.12 on > this web site > http://lacie-nas.org/doku.php?id=ubooby bodhi - uBoot
InfoScav, > 9. Erase 1 block starting 0x00100000 (See caveat > in step 2, do not do this step this if the kernel > is stock kernel, or not a FDT kernel) > > > /usr/sbin/flash_erase /dev/mtd0 0x00100000 1 > > Erasing 128 Kibyte @ 100000 -- 100 % complete > > > > 10. Flash uboot environment to 0x00100000 (See > caveat in step 2, do not flasby bodhi - Debian
LeggoMyEggo, > > If I can't do this from the OS level, is it > guaranteed to be changeable at the serial console? > I have to admit, I was kinda hoping that I would > have at least one PP that I didn't have to crack > open as that would indicate a little bit of > acquired skill and Linux mastery :) You can also change it in netconsole since you'reby bodhi - uBoot