Show all posts by user
Bootloader tips and tricks
Re: ntp stopped working - here's the workaround - 11 years ago
bodhi Wrote: ------------------------------------------------------- > I have name server 8.8.8.8 in this file. Google > seems to be very reliable. The one problem I've had with Google nameservers, aside from their penchant for collecting personal information on us, is that for some reason they completely break the dnsbl feature of sendmail. Dnsbl works by using especially craftby restamp - Debian
Re: ntp stopped working - here's the workaround - 11 years ago
I've noticed that on my Pogoplugs (also no RTC) it used to take some time for them to sync up to the correct date and time after a reboot. I run with both ntpd and a local named DNS server installed and the problem seemed to be that ntp and DNS would come up before the networking and then sleep (actually, DNS goes into "svrfail") for a while before retrying. In addition, there isby restamp - Debian
Re: dockstar: update from squeeze to wheezy? - 11 years ago
See the following thread: http://forum.doozan.com/read.php?2,5746,5749 This worked for me, leaving only a few minor details which needed to be addressed. Good luck. Make sure you make a backup first!by restamp - Debian
Re: [Pogoplug Mobile] Install uBoot/Debian - 11 years ago
I see. Thanks syong and bodhi for the information. The only thing the "machid=dd6"-knowledgeable kernel buys you is the ability to control the green LED, right? If this is the case, I think I'll just wait until wheezy incorporates the Pogo line. (Heck, most of the machines I run are still on squeeze, so it's immaterial.) If I install bodhi's special kernel, then I�by restamp - Debian
Re: [Pogoplug Mobile] Install uBoot/Debian - 11 years ago
Sigh. Try as I might to make "machid=dd6" work on a Pogoplug E02, every time I add it to the uBoot environment, I wind up with a box that won't boot. I thought it was due to the squeeze kernel (2.6.32-5-kirkwood) that I had been running not recognizing the Pogo dd6 id, but tonight I genned up a wheezy load (complete with 3.2.0-4-kirkwood kernel) and it still wouldn't boot.by restamp - Debian
Re: Pogoplug E02G for $24.99 - 11 years ago
The slickdeals.net offering are clearly for the P21 (Pink) and B01 (Black) Pogos, not the E02. I don't know a lot about these, and the archlinuxarm.org site seems to be down right now, but I think (and someone correct me if I am wrong) that (1) both of these have only 128 MB rather than 256 MB of RAM memory, and (2) at least one of these has the slower albeit dual-core Oxnas processor, as bby restamp - Off-Topic
Pogoplug E02G for $24.99 - 11 years ago
Adorama Camera has Pogoplug E02Gs (that's the gray version of the normally pink E02 -- same innards) for $24.99 with free shipping. I ordered two and can confirm they really are the E02 with 256 MB of RAM. Both flashed the latest Jeff/davygravy uBoot with nary a complaint, so I just ordered two more. Don't know if it is significant overall, but the NANDs on my two looked pretty healtby restamp - Off-Topic
Re: How to jailbreak a used Pogoplug E02 - 11 years ago
Hi bodhi, Since you are, by far, the most active person in this forum, I personally think Jeff ought to make you a moderator! Thanks for your quick reply. I do have one of those 3V Nokia USB connectors that purportedly could be used to access the console, so it's not outside the realm of possibility that I could access the original uBoot. But, what then? Does this uBoot have the capabby restamp - Off-Topic
Re: Booting Debian on Pogoplug Pro - 11 years ago
Back your system up first, and then you have an out if the upgrade causes problems.by restamp - uBoot
How to jailbreak a used Pogoplug E02 - 11 years ago
The market for new Pogoplug E02 seems to have dried up. This is my personal favorite ARM device, so I'm considering bidding on several used units for spares and to play around with. However, these units will have previously been activated and my understanding is that the default root password will no longer work. (Is this indeed correct?) So, my question is: Should I acquire one of thby restamp - Off-Topic
Re: I installed Rescue System, now I can't boot into anything. - 11 years ago
bodhi Wrote: ------------------------------------------------------- > - Make sure the USB stick is formatted Ext2. If > you ran the installation script at the ALARM stie, > the Arch stick is Ext3. So you need to convert it > to Ext2 (remove journal) in order to boot with > current setting of uBoot env > (usb_rootfstype=ext2). I believe (and in the past I've succeby restamp - Rescue System
Re: Pogo-Squeeze permissions - 11 years ago
One problem that I suspect you'll encounter is that, in all likelihood, you've lost any set-uid and set-gid bits which were set on your filesystem. Also (as you found out with ssh), some programs check and require tightened permissions to run. The Sendmail MTA is another one that is strict about permissions. I remember once doing an "rm *" in /bin by mistake and the sinkiby restamp - Debian
Re: Newer uBoot as workaround to 3.2 kernel problem? - 11 years ago
Thanks for your help, moonman and bodhi. Based on your reports and suggestions, I used Jeff's install script and it worked like a champ. (I suppose I ought rightly tip my hat to davygravy and Jeff at this point, too!) Unfortunately, for me, setting "machid=dd6" in the uBoot environment (with "archNumber=3542") did not work. It would act like it was booting, but woulby restamp - uBoot
Re: Newer uBoot as workaround to 3.2 kernel problem? - 11 years ago
It's been a while since I've hacked on my arm hardware, but I still have a couple of pristine PogoPlug E02s which need to be jail broken and have their uBoot reflashed so that they can eventually become the backup hardware for when my existing servers bite the dust. I am wondering what is the latest uBoot that I should use for this purpose. I am still running Squeeze here, not Wheezy,by restamp - uBoot
Re: Booting Debian on Pogoplug Pro - 12 years ago
Here are my personal notes to myself on the subject of RTC setting, which may prove helpful to you. There may still be issues of the order in which NTP vs. Ethernet comes up, but on my boxes, this forces a good RTC fairly quickly after a boot. YMMV. 20 Mar 2011: The Dockstar does not have a RTC, so the network must be used to set the date and time on every boot. To set the date, "ntpby restamp - uBoot
Re: Help! My DockStar Squeeze don't boot anymore. - 12 years ago
Glad you got the issue resolved. I was about to suggest rebooting your router. The MAC address is set as part of the uBoot's environment. Changing MTD1 & MTD2 shouldn't affect it. Was the MAC address the same as on the underside of the Dockstar or something different?by restamp - Debian
Re: Help! My DockStar Squeeze don't boot anymore. - 12 years ago
I'm running out of ideas. 192.168.1.1 is the IP address of your router, which is connected to the internet, right? And, your Dockstar is on the same LAN as the router? Can you ping the router?by restamp - Debian
Re: Help! My DockStar Squeeze don't boot anymore. - 12 years ago
Hmm, I don't see any obvious problems so far. When you say you have no web access, do you mean no IP access outside your local LAN or no access to a DNS server? What is the results of a "traceroute 8.8.8.8"? ("apt-get install traceroute" if you need to.) Also, do you currently have an /etc/resolv.conf, and if so, what is in it?by restamp - Debian
Re: Help! My DockStar Squeeze don't boot anymore. - 12 years ago
This is very typical of a DNS issue. The Dockstar is trying to do a reverse lookup for recording the login attempt, but the nameserver for whatever reason is not responding. So, everything pauses until the DNS subsystem times out. 1. Are you using a dynamic or static IP assignment? 2. What is the output of "ifconfig -a"? 3. What is the output of "netstat -rn"? 4.by restamp - Debian
Re: Dockstar watchdog supported? - 12 years ago
astker, I think the hardware watchdog timer is integral to the Marvel chipset, at least the 88f5182 and 88f6281 architectures. Whether the Debian kernel uses it is anyone's guess. The details of the timer can be found in this document: http://www.marvell.com/embedded-processors/kirkwood/assets/FS_88F6180_9x_6281_OpenSource.pdf Start reading around page 283. Frankly, when I was pby restamp - Debian
Re: Newer uBoot as workaround to 3.2 kernel problem? - 12 years ago
For some time now, I've wondered about the viability of adding an option to the uBoot to initialize and start the hardware watchdog timer before dispatching to the kernel. Then, in the kernel's boot sequence, it could reset or re-initialize the watchdog for its own purposes. One problem would be that the watchdog doesn't really provide much range time-wise. I think its timer canby restamp - uBoot
Re: NetConsole with USB cable? - 12 years ago
Jussi, netconsole does not use USB at all. I believe you mean "Can I use USB to talk to the hardware console of the Dockstar?" and the answer is yes, if you use a special USB device. The device you want is known as a CA-42 cable and it is sold as an accessory for Nokia phones. It is actually an implementation of a serial port, but using 3.3V signals (if I recall correctly) rather thaby restamp - uBoot
Re: Newer uBoot as workaround to 3.2 kernel problem? - 12 years ago
davygravy, could you perhaps put together a post which explains what the problem is with the original Doozan uBoot and what had to be done to allow it to work with the 3.2+ kernels? From this forum I've been able to surmise that apparently the 3.2 kernels used a different compression scheme and that it is somehow incompatible with L2cache. (Well, maybe... tell me if I am wrong here...)by restamp - uBoot
Re: Pogoplug won't boot with USB HDD attached. - 12 years ago
rc.local should be the last thing executed, after all the scripts in /etc/rd?.d.by restamp - Debian
Re: Pogoplug won't boot with USB HDD attached. - 12 years ago
An interesting solution I had somehow overlooked before. Thanks for pointing it out bodhi. In all honestly, these little ARM devices are changing the very way I think about servers. Until now, I've opted for fairly bullet-proof hardware (old Sun Sparcs) mated with mirrored drives. (That combination has served me amazingly well for the past 15 years. FWIW, in all that time, I've eby restamp - Debian
Re: Pogoplug won't boot with USB HDD attached. - 12 years ago
An addendum to my previous message: One solution that has been proposed, and which I believe works, although not cleanly, is to specify the root partition by its UUID number instead of by a device itself. The problem with this approach is that, when this is done, the kernel goes off attempting to search every block device for a partition with that UUID in it, and this in turn causes a cascadeby restamp - Debian
Re: Pogoplug won't boot with USB HDD attached. - 12 years ago
Typically, this sort of thing is due to the kernel making the wrong decision about the relative device letters to assign each of the two "sd" devices. With one "sd" device, it always winds up becoming "sda". (And, you are specifying /dev/sda1 as the root partition, right?) With more than one "sd" device, it becomes a toss-up as to which device becomes &qby restamp - Debian
Re: Installing Asterisk - 12 years ago
I can't suggest a solution to lewy1, or even suggest anything to try, but I did build asterisk-1.8.9.2 earlier this week from source on a Pogo E02 without any problems, so I can attest that it is doable. I did not have to make any changes to utils.c. I also checked and found that the mod to channels/chan_gralk.c to pick up both "redirect" and "sta:redirect" had also beeby restamp - Debian
Re: Using all 256mb RAM onPOGO-E02? - 12 years ago
I'm running Rick's default uboot and Debian 6.0.3 on mine and it sees 256 Megs. I was late to the game with the E02's, but I've never seen anything less than 256 MB (well 249.7 after the OS takes its chunk) from them.by restamp - uBoot
Re: Use netconsole to troubleshoot uBoot without a serial cable - 12 years ago
It looks to me like you're missing the /boot/uInitrd file. Did the system just spontaneously stop booting, or did something else happen which might have precipitated this problem? Here's what I'd do: Take the USB drive to another Linux machine and fsck the file systems on it manually. If you find corruption, make sure you restore it to a viable state. This sometimes involvesby restamp - uBoot