anonymous comment, 5 weeks ago
Flash erase block sizes are typically 4MB or a near power of two these days - pretty large.
Newer, more advanced SSD controllers such as those on the Intel SSDs make this irrelevant by being intelligent about small writes, but with SSDs like those on the Eee PC, you are stuck with erasing and rewriting entire 4MB or so block for small writes. Hence why Flash writes are only high performing when writing 4MB or more.
comment by jim, 5 weeks ago
The OpenWRT folks "resolved" this by adding a printk that mentions the FPU emulation is disabled somewhere early in the boot, but not making the kernel option visible or preventing the infinite emulator trap.
At best this will let your kernel tell you "I told you so." after you spend four days debugging.
anonymous comment, 2 months ago
You should note that grub-pc for lenny is missing part_msdos.mod and will not install, you need to fetch it from backports to get the file.
Thanks for the info though, it helped me to confirm what I was doing would work before I sent a remote machine through a reboot (I know, dangeous, but couldn't be helped)
Thanks for the info though, it helped me to confirm what I was doing would work before I sent a remote machine through a reboot (I know, dangeous, but couldn't be helped)
comment by jim, 5 months ago
anonymous comment, 8 months ago
comment by jim, 8 months ago
anonymous comment, 10 months ago
You saved me many (more) hours of head pounding with this blog entry. I am thoroughly grateful.
At some point in the past I managed to screw up my file server's lenny install in such a way that I ended up with the non-lvm ext2 boot partition commented out of fstab and a separate /boot directory on the lvm root.
I forgot about this incident and went about continuing to run apt-get dist-upgrade periodically. Everything worked until I went to squeeze and rebooted, at which point I made some more poor choices ("Why am I not running the new kernel? I'll just apt-get remove the old one!") and ended up unable to mount ext2 partitions (while still able to boot from one).
After about eight hours of head scratching I found this page and by following your steps had no trouble upgrading to GRUB 2 which booted the new kernel which fixed all the problems, allowing me to get on with my life (such as it is).
You are awesome and so is GRUB 2.
At some point in the past I managed to screw up my file server's lenny install in such a way that I ended up with the non-lvm ext2 boot partition commented out of fstab and a separate /boot directory on the lvm root.
I forgot about this incident and went about continuing to run apt-get dist-upgrade periodically. Everything worked until I went to squeeze and rebooted, at which point I made some more poor choices ("Why am I not running the new kernel? I'll just apt-get remove the old one!") and ended up unable to mount ext2 partitions (while still able to boot from one).
After about eight hours of head scratching I found this page and by following your steps had no trouble upgrading to GRUB 2 which booted the new kernel which fixed all the problems, allowing me to get on with my life (such as it is).
You are awesome and so is GRUB 2.
anonymous comment, 10 months ago
comment by jim, 13 months ago
Aw nuts, now I need to implement "delete attachment". The 1.3 version adds a little 'flash' badge instead of just a grey box and a way to edit your whitelist.
I've had no problems with this over the weeks I've been using it, in fact it has saved me from canceling my American Express card because their commercial no longer tries to play in my browser when I go to pay the bill.
anonymous comment, 13 months ago
anonymous comment, 13 months ago
comment by jim, 14 months ago
Those google ads are nice. I almost never get enticed by an ad, but two of the google ads on this site have lured me into visiting the advertiser. (Google's terms forbid me from clicking, so I have to type in the URL.)
Virtually 100% of the writing on this site is mine, so they have their little demographic cross hairs right on my brain, and it works.
comment by jim, 14 months ago
comment by jim, 17 months ago
comment by jim, 18 months ago
I just built dfu-programmer for etch with these steps, and attached it to the parent article (I guess I should implement attachments for comments.)
- Go to the Debian packages page for the Lenny package.
- Download the original source and debian diffs.
- Unpack the original sourcestar -zxvf dfu-programmer_0.4.3.orig.tar.gz
- Apply debian patches... zcat dfu-programmer_0.4.3-1.diff.gz | patch -p0
- Hop in cd dfu-programmer-0.4.3
- Build packages fakeroot ./debian/rules binary-arch
- Fail... fix x flags on rules chmod +x debian/rules
- Fail... install libusb-dev
- Success! I now have a dfu-programmer_0.4.3-1_i386.deb in the parent directory.
- I can't test it, my only Etch machines are remote servers, but it installs ok and I expect it works.
I probably should have modified the version number to mark it as an Etch build, but this works for private use.
anonymous comment, 18 months ago
anonymous comment, 18 months ago
anonymous comment, 18 months ago