> The > ethernet port is still lit but USB stick light is > off. > this is ArchLinux installed and maybe this > explains some of the boot corruption. No it does not. > If you know of a better shutdown command than > poweroff, I'll try it and see. > Do a few sync commands before shutting down. Use the standard "shutdown -h now" on system withby bodhi - Off-Topic
@gray, > Too funny. You've been in doubt ever since I > mentioned wanting to boot the default Pogoplug OS > on the PPV4. :) Now I really think it over (not the 1st time :)) I agree it would work. Because how I wrote the instruction to flash u-boot image, it would leave the stock envs untouched :) OTOH, the mtds restoration procedure would need CESVCID and MAC addr adjustby bodhi - uBoot
metric, > BTW Does anybody know > if ZFS is supported on our Dockstar Debian? I > cannot find anything. I want to boot with flash > but store data on a ZFS hard disc. No, it is not supported. ZFS takes too much memory to run (> 1GB), so I have given up on compiling it for ARM. Soon it'll be revisited given there are quite a few ARM boards now begin to support >= 1Gby bodhi - Debian
@Don, It looks pretty fine and going to work to me. That's all it matters. As a more elegant solution, iirc, there is one in that you would perform all these routing table logics inside /etc/network/interfaces.by bodhi - Debian
@grayman4hire, Are you sure that it will help to run the Dockstar orgininal u-boot on the Pogo V4? I don't doubt it will run Pogo OS, but will that allow the CE Pogoplug service registration? i.e. as in the original condition with the serial number and all that?by bodhi - uBoot
Gravelrash, > if i can > offer a "helping hand" to someone else then karma > demands it. Tip of the hat! > It will definitely be aimed solely at one > particular box the Pogov2 with the 2014* uboot. I think this specific target is good (as widely used as the V4/mobile, if not more so), and achievable without too much effort.by bodhi - uBoot
@Gravelrash, Please don't be offended if my questions sound like I'm against the idea of an image for noobs (or even doubting your technical ability). I'm agnostic on this. IMO, I think people who starts hacking Linux should at least learn how to create a bootable rootfs with tar, fdisk,.. commands on Live CD, or a Ubuntu box. OTOH, I understood the appeal of the rPi communityby bodhi - uBoot
@robert, You did not misunderstand! keyboard was not included in the kernel 3.17 config for OXNAS. I'll include it in the next release.by bodhi - Debian
megov, boot ROM is not a reliable indicator if it's not at 0xFF00003C. The NSA325 has UART booting, but no bootROM version found at 0xFF00003C. Did the box reply with anything at all when you power up while kwboot running? or did it ignore the handshake and start stock u-boot right away?by bodhi - uBoot
@denexo, > I tried to > modprobe bluetooth and bluez kernel module, but it > seems they are not compiled. Do you have any idea > how this could work? As soon as i find some time, > i will try to compile the kernel modules in order > to manually probe them. Confirmed, bluetooth was not compiled in the OXNAS kernel. Pls try compile the modules to see if it will work. I&by bodhi - Debian
twinclouds, > The purpose of upgrading to jessie was to try > out Asterisk 11 by apt-get and it works now. > Wheezy can only directly install Asterisk 1.8. Awesome! this is what I was curious to know. Thanks for the hint.by bodhi - Debian
megov, > So either ix2-dl ignore UART boot procedures or > something goes wrong. Did you check the bootROM version? it is not a reliable indicator if it is absent (it might or might not work), but it is quite reliable if you get the correct bootROM version (most likely will work).by bodhi - uBoot
@samad, > Now, at least the front LED comes on, but still no > network. I've even tried setting a static lease on > my router for the Pogoplug's mac address. Best way to recover without serial console in this situaton is to boot into a working rootfs, and then mount your Arch stick, examine it. You can temporarily boot into Debian. Get the rootfs 3.16 from this threby bodhi - uBoot
@twinclouds, Let us know what your resolution was. It'll help others upgrading to jessie.by bodhi - Debian
@denexo, Let me double check, bluetooth is fully supported on the Kirkwood boxes, but I'm not sure I had it compiled on the Pogo V3.by bodhi - Debian
Kidding aside, when you are modding the boxes, you should be root all the time. When you are using the box as a user, then you should not be root.by bodhi - Debian
habibie, Here is what the disassembled GF Home looks like: http://archlinuxarm.org/forum/viewtopic.php?f=18&t=3397by bodhi - uBoot
rayknight, > What do you mean by UART booting? Is this > different then booting from the serial console? See this thread: http://forum.doozan.com/read.php?3,7852,7852by bodhi - uBoot
> I'm of the opinion that best practice is to > disable root ssh logins, and login as a regular > unprivileged user. If root access is required, > then su to root from within the unprivileged user > shell. It is certainly appropriate and a good practice to do that for desktop users. But we are hardcore embedded Linux devices modders ;)by bodhi - Debian
rayknight Wrote: ------------------------------------------------------- > I currently have 2 Kirkwood based systems not > covered by the latest Kirkwood builds. > > 1. Cisco ON100-K9 Marvell 88F6282 @ 1.6 GHz, > 512MB Flash, 512MB RAM, stock U-Boot 1.1.4 > 2. D-Link DNS-320 Marvell 88F6281 @ 800 Mhz, > 128MB Flash, 128MB RAM, stock U-Boot 1.1.4 > > Theby bodhi - uBoot
twinclouds, > I upgraded to jessie and everything looks fine. > However, when reboot, I cannot login anymore. I > googled and found it does not allow root access > through ssh anymore. This is strange, it should not happen. I dont't have this problem. Ah, I recall now, there was a question regarding root ssh login. You must have selected a wrong option. As Frederiby bodhi - Debian
habibi, It is very easy. After you've removed the screws, just use a thin plastic wedge or even a thin knife will work, but will leave some marks. Pry open the bottom plate at the groove, very gently and slowly. There are hinges inside the plate that snap to the vertical walls. I've done it a few times. You'll might break some small hinges, but as long as there are some remaby bodhi - uBoot
FelipeC Wrote: ------------------------------------------------------- > So the idea is that after i manage to boot from > debian i must then follow your instructions to > restore the factory image as described on the > initial link you posted? > > http://forum.doozan.com/read.php?3,16789,16789#msg > -16789 > > Thanks for all your help, > FelipeC Exby bodhi - uBoot
habibie Wrote: ------------------------------------------------------- > Hello Bohdi, > > Thank you and I noticed that too on ALARM forum. > > I am tempted to use netconsole. However, I was > told netconsole will only work for u-boot. In > other words, it cease to work once the device > boots Linux kernel. I was hoping it will continue > to work even withinby bodhi - uBoot
FelipeC, > I don't know if i realy mess it up to the total > "brick" level but i hope there is still some hope > to revert it to stock! No you did not brick it! all you need to do now is to create a USB rootfs and boot with it. Once you got in Debian, you can go back to stock easily. Follow the instruction in this thread to create the rootfs using the 3.16 verison:by bodhi - uBoot
@nat, > You know Bodhi, I tried so hard to try and filter > through the prior posts to solve my problem > because I didn't want to bug you. You have > devoted a lot of time to repeating the same > information to different people with the same > problem, and I'm very conscious of this. I > appreciate that you took the time to assist me. No problem! we aby bodhi - uBoot
Frederick Grayson Wrote: ------------------------------------------------------- > But not functioning at the same time. Agree, of course not. The keyword is "functioning". They are "operating" at the same time. And the packet is routed through only one interface. So the issue at hand is: in order to keep wlan0 working when the eth cable is unplugged, we need to tweakby bodhi - Debian
@Frederick, Think about this with these plugs: the Pogo Pro V3 and the iConnect both have wifi and ethernet. Their IP are usually dhcp from the same router and on the same subnet. Gravelrash explained this above.by bodhi - Debian
twinclouds, Install these 3 packages: sysvinit-core, sysvinit, and sysvinit-utils.by bodhi - Debian
@Gravelrash, > The env settings look to be a mashup of both Arch > and Bodhi settings :)) It happens! Use this to reset the envs to a default state in serial console: http://forum.doozan.com/read.php?3,18105,18124#msg-18124by bodhi - uBoot