JohnW Wrote: ------------------------------------------------------- > Bodhi, with systemvinit i had to add "mount -a -t > nfs4" to rc.local to have the second nfs-share > mounted at boot. > > With systemd i did not need to do that. My idea is > that systemd is a bit more intelligent when it > comes to pick the moment when to run stuff... Case > closed.by bodhi - uBoot
All, I'm in need to learn a certain aspect of this SoC that should be in Marvell Function Specifications for the 88F6282 SoC (found in Zyxel NSA325 and other NAS brands). It took Marvell a while to release their spec for 88F6281. As their normal practice, for more recent SoCs that are out in the market, the functional spec can only be had with an NDA. If anybody knows how to get some detby bodhi - uBoot
foursdude Wrote: ------------------------------------------------------- > Hi bodhi, > You are the man! Changing file system to ext2 did > help and I can ssh into the debian OS now. I can > even attach the hard disk and see the files there > again! > Now what are the steps to move the Debian rootfs > to the hard disk so I can boot from there? > Thanks. Cool!by bodhi - uBoot
foursdude, > Good news is that I can boot with the USB drive > made with the link you provided - the green light > is on which I believe is a good sign. Indeed, it is a good sign. Especially if the plug was flashing green after power up, and then became solid green. It means the kernel has been loaded and started successfully. > However I > don't see it on the netby bodhi - uBoot
dibbsy Wrote: ------------------------------------------------------- > I never ran those steps before rebooting as I had > the stock kernel and alarm on usb, I ended up just > interrupting uboot and manually adding the uboot > envs based on your kernel thread and put the 3.17 > rootfs on another usb stick. > > Also to note, using a 99c ttl to usb board cut and >by bodhi - uBoot
dibbsy Wrote: ------------------------------------------------------- > I have alarm on the pogo right now. > > 4. You are running stock kernel, and have gained > SHH access to the box, and have downloaded > u-boot-tools and mtd-utils (fw_setenv, > flash_erase, nandwrite …) to work with NAND > mtds. And plan to run a USB rootfs that came from > any of the aboveby bodhi - uBoot
foursdude, > > Yes I have another Linux machine. > OK. Then you could try booting with Debian rootfs. Given you've installed Arch 2 years ago, try the Debian-3.16.0-kirkwood-tld-2 rootfs: http://forum.doozan.com/read.php?2,12096 Scroll down to the section: QuoteUpdated 02 Sept 2014: Rootfs Debian-3.16.0-kirkwood-tld-2 was uploaded. This rootfs is to keep in synby bodhi - uBoot
Kernel linux-4.1.0-oxnas-tld-1 package was uploaded. Please see 1st post for download link.by bodhi - Debian
Don, > On a more humourous note I managed to "cook" a > Sandisk Ultra micro SD card recently on ext4 ... > and, doh!, I didn't follow my own advice about > overprovisioning ... next time ... > It does happen. Been there done that :)) > The card I think must have decided that there were > too many bad blocks and set itself to read-only > ... Iby bodhi - Debian
Johnny, I've just wanted to test a theory by doing that. I did not have high hope that the test was going to work. The thing that puzzles me is pengu system is working fine without doing any thing extra. I was thinking along the line of what bobafet said above. The possible difference between stock OS and my Debian build is: there might be a kludge in stock OS to configure the etherneby bodhi - Debian
Johnny, One more try. Instead of "shutdown -h now" try: shutdown -H now if that option did not take, try shutdown -h -H now And capture the serial log.by bodhi - Debian
@Johnny, Please try the halt script below. But save it first: cp -a /etc/init.d/halt /etc/init.d/halt.orig Replace the entire halt script content with this: #! /bin/sh -x ### BEGIN INIT INFO # Provides: halt # Required-Start: # Required-Stop: # Default-Start: # Default-Stop: 0 # Short-Description: Execute the halt command. # Description: ### END INIT INFO Nby bodhi - Debian
foursdude, Depend on the state of your GFhome. Let see if I understand what happen: > I installed Arch Linux on my GFH years ago, This mean you have U-Bit running as boot loader. > worked fine until a few weeks ago when I did a > pacman update. But when was the last time you did pacman update before this update? Do you keep any log of dmesg output? > I tried creaby bodhi - uBoot
Johnny, > how do i look for that? I'm tired and my brain is > almost on fire :) Take a break! You can always pull the power cord as a work around :) > > LE: i think i know what you wanted Yes. Your shutdown events log is slightly different from mine. I need to study it.by bodhi - Debian
Johnny, Which serial log is your shutdown log? does it show the network interfaces were deconfigured?by bodhi - Debian
JohnnyUSA Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > Johnny, > > > > My guess is your router. I don't think u-boot > envs > > can affect this. My WAG is the fact that you > need > > to unplug the power cord, that's causing the >by bodhi - Debian
Johnny, My guess is your router. I don't think u-boot envs can affect this. My WAG is the fact that you need to unplug the power cord, that's causing the NIC to clear some data. After you did a shutdown -h now, does the Eternet port still blink green or yellow?by bodhi - Debian
JohnnyUSA Wrote: ------------------------------------------------------- > @bohdi, > > changed the MAC with the one on the case. Strange > thing is, it was the same as the one i've had > already on U-Boot. No change, still same > problems. > > Now i'm trying with rootfs from @pengu, let's see > how it goes. OK. Then the NIC is not Marvell.by bodhi - Debian
@theliquid, Ext4 encryption: I will add this capability in the next release (using it as module is not doable in the current kernel).by bodhi - Debian
JohnnyUSA Wrote: ------------------------------------------------------- > Thanks again for replies guys, now, witch one is > the mac add? > > Here's the pic: > http://s24.postimg.org/5wkvmbmc5/IMG_0157.jpg > > I'm a little bit confused :) It should be outside on the case bottom or rear.by bodhi - Debian
pengu Wrote: ------------------------------------------------------- > This has to be done on the NSA310, otherwhose the > default mac will be used. > It isn't neccesary on (mine) NSA310s, but it > doesn't hurt, give it a try JohnnyUSA I suspect Johnny's router might have something to do with this.by bodhi - Debian
Johnny, The only thing we have not tried is to set the MAC address to be the same as the NIC. You are using the Zyxel MAC address (we all do because of stock FW). This MAC address was set by Zyxel. However, it is NOT the correct one to use when dealing with the NIC (e.g. WOL works only if Marvell MAC addr is used). - find the Marvell MAC address on the case sticker. - interrupt u-boot andby bodhi - Debian
Johnny, QuoteNow I did what you've asked me. I've booted again and unplugged the Ethernet cable and plugged back in, here's the bootlog: http://pastebin.com/zgCa6M3P In this case, I meant you should: - login with ssh - shutdown -h now - power up, we know it will fail to get the link up. - login with serial console - while in Debian, watch dmesg, unplug ethernet cableby bodhi - Debian
schnee, > It seems to make this work kernel needs hiddev > device support to be included. Next release maybe? Sure, I will make sure hiddev support in next release (soon to be).by bodhi - Debian
Johnny, Your link has never been up. When it is up, then this message will be shown in dmesg [ 18.265107] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled So if in serial console, observe that the link still down since powering up, unplug the ethernet cable, and replug it, see if it would trigger the link to be brought up?by bodhi - Debian
JohnnyUSA Wrote: ------------------------------------------------------- > @bodhi, > > no, it's with dynamic IP > > > root@debian:~# cat /etc/network/interfaces > auto lo eth0 > iface lo inet loopback > iface eth0 inet dhcp > > hwaddress ether 5c:f4:ab:df:07:2b > > > but that paste is from when eth failed to get link > on halt.by bodhi - Debian
JohnnyUSA Wrote: ------------------------------------------------------- > LE: Output of ifconfig -a: > > > root@debian:~# ifconfig -a > eth0 Link encap:Ethernet HWaddr > 5c:f4:ab:df:07:2b > UP BROADCAST MULTICAST MTU:1500 > Metric:1 > RX packets:0 errors:0 dropped:0 > overruns:0 frame:0 > TX packets:0 errorsby bodhi - Debian
Johnny, You did not mention what did you do here during boot: From serial boot log: fsck.ext4: Unable to resolve 'UUID=55c72762-02f1-4d09-b8c1-5e6da7f17dd4' fsck exited with status code 8 File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ... A maintenance shell will now be started. Cby bodhi - Debian
Also change this, KERNEL!="Eth*|ath*|Wlan*[0-9]|msh*|ra*|sta*|ctc*|lcs*|hsi*", \ GOTO="persistent_net_generator_end"by bodhi - Debian
Johnny, Log in with serial console and comment out this line. Save, and power down. Power up to test. # Unknown net device (/devices/platform/mv643xx_eth_port.0/net/eth0) (mv643xx_eth_port) #SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:f4:ab:df:07:2b", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="ethby bodhi - Debian