ntp doesn't like large jumps in time. Instead, to set the clock initially run: /etc/init.d/ntp stop ntpdate-debian /etc/init.d/ntp startby ayrlander - Debian
You're running Squeeze, which has finally transitioned to be the stable release. As a result, it doesn't get updates anymore until a new release comes out. 6.0.1 should be out in a week or two, so I expect the stable repositories to have updates then. In the meantime, put these into /etc/apt/sources.list deb http://security.debian.org/ squeeze/updates main contrib non-freeby ayrlander - Debian
It should go fine; I update my system pretty regularly (running aptitude dist-upgrade every day or two), and I don't remember any showstoppers since I first installed using Jeff's script in September. But you're right, the kernel will be an issue as it was upgraded (multiple times) since October. After you upgrade squeeze, and before you reboot, make sure to run the following, otby ayrlander - Debian
Mine beeped for a few days, and then stopped. It hasn't beeped since. I never did get an answer as to what could have been causing the beep, much less why it was beeping at all.by ayrlander - Debian
Now you're beyond the file system errors problem you were having, so you may want to consider starting a new thread so others will know to look in there. :-) You said after you ran apt-get update, you couldn't boot because of a boot image failure. My guess about what happened is your kernel was upgraded (which has been happening a lot lately), but your boot images in /boot werenby ayrlander - Debian
Okay, that's good at least, that -n specifies read-only mode. I agree that it would almost definitely find problems in that case. Papst01, my answer is to stop running fsck -n on the mounted filesystem, as it won't say anything useful and is only scaring you into thinking there's a real problem when most likely there isn't. As restamp said, if you run your system for a whilby ayrlander - Debian
The clue to your problem is in the line: "Warning! /dev/sda1 is mounted." Never, never, NEVER run fsck on a mounted filesystem. I can't believe this version of e2fsck doesn't have this warning if you try to do so: /dev/sda1 is mounted. WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage. Do you really want to continue (y/n)? That&by ayrlander - Debian
There's only a few differences in a system installed with Jeff's script than a standard Debian install. A -kirkwood kernel variant gets installed for use on Marvell Kirkwood based systems like the Sheevaplug and Dockstar. A couple of uboot packages get installed. The bootloader is modified on the Dockstar itself. A standard Debian install goes onto your external drive. A few filesby ayrlander - Debian
Are you sure it's not booting? Most likely, if you changed the MAC address, your router is giving it a new IP address. Check to make sure it's not just getting a different IP address than you're expecting.by ayrlander - Debian
I'm pretty sure it's coming from the body of the DockStar itself. I unplugged an X10 USB device I have plugged in, and moved my hard drive as far away as I could. The plug is pretty far down from the box itself. I'm not sure why my DockStar would start vibrating, though, and this was a pretty regular chirp. I'd record it if I could. My wife asked me if a cell phone was goby ayrlander - Debian
I just had something very odd start happening today, and I was curious if it's happened to anyone else. My DockStar has started chirping at me. It beeps twice, like a cell phone, a little more than once a minute (e.g. it beeps twice, then again 62 seconds later, then again 65 seconds later, then 60 seconds later...). First off, I didn't even know the thing had a speaker in it (I haveby ayrlander - Debian
Yep, far too late at this point. :-) But it also depends on what operating system you're running now. I was running Plugbox Linux on one hard drive, and then wanted to install Debian on a second, new hard drive. But you might be able to run Jeff's script from the default boot environment (what you get if you boot the Dockstar with no hard drives or flash/thumb/USB drives attached, Aby ayrlander - Debian
Quotesandbasser I partially understand the sources.list's function; but, if they're all mirrored (as, I believe they're supposed to be) what difference does it make which one is used??? I suppose some of the mirrors are busier than others -- is that it??? Some are busier, and some are closer to where you live. It looks like you have some program (maybe the one petergunn sugby ayrlander - Debian
If you're looking for apps, I'd say go with Debian. I started with Plugbox, which is basically Archlinux recompiled for the Dockstar and other plug computers, and it was nice and for the basics, easy to use. But several packages and Perl libraries that I wanted hadn't been "ported" to Plugbox. I tried building stuff for myself from the Archlinux repositories, but it goby ayrlander - Debian
Glad you both got it working. How the arcNumber is read and used by the kernel would be a question for Jeff or for ecc, as he submitted and had approved the kernel patch to get the LEDs working. But this might help a little: http://www.plugcomputer.org/plugwiki/index.php/ArcNumberby ayrlander - Debian
I'm hoping they didn't break support for the LEDs in a later kernel, but odds are, they're not showing up properly because of the arcNumber issue; the kernel doesn't know you're running a Dockstar if that isn't set, I believe, so it's not giving you Dockstar LED configurations. Sanity check: does "ls -l /usr/sbin/fw_setenv" show an executable? If sby ayrlander - Debian
rat, you went into several issues, so I'll separate them out. If you've run apt-get upgrade lately, then you've no doubt downloaded a new kirkwood kernel; there have been several updates to the kernel over the past couple of months, as squeeze incorporates patches to become the stable distribution. I can't speak for it overwriting any other kernel you've installed.by ayrlander - Debian
I tried gallery2 when I was still running PogoPlug Linux. It didn't work very well. The software itself was fine, but the helper apps (ffmpeg, imagemagick) ground my Dockstar to a halt for 5-10 minutes per page as it generated thumbnails. It wasn't pretty. I haven't tried under Debian yet to see if that was an Archlinux thing, or if it was a Dockstar limitation. Since Galleryby ayrlander - Debian
The chrony and ntp packages conflict with each other, so aptitude and apt-get won't let you install one without removing the other.by ayrlander - Debian
I've never used chrony, so I can't say one way or the other about it. I also don't know if it comes configured out of the box, like ntp does. You can always give it a try, and if it doesn't work out, uninstall it and go back to ntp (which does usually work, just not 100% for some odd reason). Ntp is by far the most common tool for doing the job, though.by ayrlander - Debian
Feel free to try it without installing ntpdate; the man page says that it should work. But sometimes, even with ntp installed and running, I notice my time drifts. It shouldn't, but it does. (This is true on desktops and laptops, too; it's not something specific with the Dockstar.) So I like having ntpdate installed just so once in a while, I can run it manually only if I notice thaby ayrlander - Debian
It's strange that DHCP wouldn't overwrite /etc/resolv.conf for others automatically. I thought that it normally does; it makes me wonder if that's a configuration option that isn't enabled by default. Anyway, take a look at this link in Debian's wiki page; at the end of that section, they say how to add the entry to /etc/network/interfaces, so I would presume thatby ayrlander - Debian
There are no stupid questions, only questions that reflect a lack of knowledge of Debian. And of course there are rude people who answer questions.... The package resolvconf isn't needed to do name resolution on any Unix variant (i.e. it's not just a Debian thing, and it's not just a Linux thing). /etc/resolv.conf is a long-standing standard used by various low-level library cby ayrlander - Debian
The 'ntp' package is the easiest, in my opinion. Install it, and it's already configured to start at bootup, set the clock from a remote pool of servers, and keep the clock up to date while it's running. That's how I keep my dockstar's clock set. You can also install 'ntpdate' to set the time one time manually from the Internet (run the command /usr/sbinby ayrlander - Debian
The files listed in the beginning of Jeff's script are only his Dockstar specific versions and local scripts that wouldn't be in a Debian repository. The vast majority of files are downloaded automatically by the debootstrap command, located halfway through the file. There's no list anywhere in the script of the full list of packages that gets installed, so looking at the scriptby ayrlander - Debian
As Elfish said, Google might be a better bet for you on configuring a NAS. Keep in mind that the main, if not only, purpose of this site is to get Debian running on this hardware. No trivial task, obviously. But once you've got Debian up and running, then your Dockstar is just like any other generic Debian computer out there, and you can take advantage of a huge expertise base, much largeby ayrlander - Debian
You can also try tweaking the usb_rootdelay variable; I think that's the one that says how long to wait before timing out (I could be wrong and it could be bootdelay; I couldn't find it after searching through the forums). Booting from cold, some USB devices take longer to become ready. When doing a warm reboot, they're already ready, so it works. Try "fw_setenv usb_rootdelby ayrlander - uBoot
According to the instructions, it looks like it should have. But, I suspect those are written if you're running install_uboot_mtd0.sh from within the original Pogoplug firmware, not if you're running it from within Debian (since within Debian, the package should already be installed). If it didn't install the binaries, though, then you can manually do the appropriate steps from tby ayrlander - uBoot
From which OS are you trying to run fw_setenv? In Debian and (I think) the rescue system, it should be in /usr/sbin . In the default Pogoplug firmware, it wouldn't be there. For Debian, it's in the package "uboot-envtools", which is installed automatically by Jeff's install script. But you also need the file /etc/fw_env.config for fw_setenv and fw_printenv to write/by ayrlander - uBoot
Quotejmandawg Do a uname -r and see what kernal is running, here is the result of mine: That kernel version doesn't matter all that much in Debian; several kernel updates can be done, and have been done, and not have that number change. Since I installed Debian on my Dockstar in the beginning of September, I've seen aptitude upgrade the kernel at least twice, and that kernel versionby ayrlander - Debian