Re: Speed of aptitude on NSLU2
On Sat, Apr 19, 2008 at 08:57:59AM +0100, Barry Tennison wrote: That's interesting. aptitude on my slug is annoyingly rather slow, but the slow parts for me are: * building the dependency tree * reading writing extended state info * building tag database (wish I could get rid of that - an option?) Me too. * building view If you do a non-ncurses activity (aptitude update, aptitude install foo) you have to pay that price _after_ the operation completes, but before the program exits. This makes sense if you were returning to the UI afterwards but with these use-cases youdon't. I expect this would be an easy win for anyone who wanted to poke at the aptitude source :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: running linux 2.6.24-5 on etch/NSLU2
On Mon, Apr 21, 2008 at 12:11:36PM +0200, [EMAIL PROTECTED] wrote: Yes. These are the instructions sent to me by Martin Michlmayer in response to a bug I had reported against the etch kernel: wget http://ftp.de.debian.org/debian/pool/main/l/linux-2.6/linux-image-2.6.24-1-ixp4xx_2.6.24-4_arm.deb sudo dpkg -i linux-image-2.6.24-1-ixp4xx_2.6.24-4_arm.deb sudo reboot thanks for the data point. That's exactly what I did, but mine never makes it past initramfs. I grabbed the latest d-i daily build from http://people.debian.org/~joeyh/d-i/armel/images/daily/ixp4xx/netboot/ and used it to install unstable on a spare drive. So 2.6.24 definitely works, and the installer worked normally. But on reboot into the new system, I get the same result - the status LED stays orange forever. Jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Big trouble
* Mikael Rudberg [EMAIL PROTECTED] [2008-04-21 20:51]: Using mkinitramfs-kpkg to build the ramdisk. Running postinst hook script flash-kernel. *Flashing kernel: devio: stdout: write error: No space left on device done. - This dosn't look good at all I'm not quite sure how this can happen. I looked at the 2.6.24-6 kernel image and it's 1338520 bytes whereas we hae 1441792 available for the kernel. Can you show the content of /proc/mtd ? Is this a regular Debian installation (using debian-installer)? I haven't dared to reboot yet as I'm very unsure what is going to happened. Try flashing an older kernel with flash-kernel 2.6.xxx-xx-ixp4xx; look at /boot to see which older versions you have installed. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Big trouble
Thanks for you quick response Martin :) nd it's 1338520 bytes whereas we hae 1441792 available for the kernel. Can you show the content of /proc/mtd ? Is this a regular Debian installation (using debian-installer)? Yes it's installed using the installer Here is the mtd nas:~# cat /proc/mtd dev:size erasesize name mtd0: 0004 0002 RedBoot mtd1: 0002 0002 SysConf mtd2: 0002 0002 Loader mtd3: 0014 0002 Kernel mtd4: 0062 0002 Ramdisk mtd5: 0002 0002 FIS directory Try flashing an older kernel with flash-kernel 2.6.xxx-xx-ixp4xx; look at /boot to see which older versions you have installed. flash-kernel 2.6.18-6-ixp4xx seem to have worked fine Thanks Mikael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: 2 Disks (by label/UUID)
I know I had problems too with the UUID method at First ... The thing was, everyone mentioned to use UUID=x syntax, but mine only worked when using the full syntax like /dev/disk/by-uuid/ Don't know about others ! Bart -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Stuart Read Verzonden: maandag 21 april 2008 4:41 Aan: debian-arm@lists.debian.org Onderwerp: 2 Disks (by label/UUID) Hello, I was preparing to add a second harddisk to my NSLU2, and since previous messages on this list referenced a boot order problem with this, I followed the directions on the wiki (and some previous messages on this list). I have two questions: 1) Why does the troubleshooting page on the wiki say that the UUID method there is no good when that's the method suggested on this list by Martin M. et al? 2) After updating the flash, the NSLU2 failed to boot (orange LED) so I had to restore my old fstab and flash to get it booting again. Is there a step besides updating fstab, creating a new initramfs, and flashing it? I noticed that in /etc/initramfs-tools/conf.d there is a file named resume which references /dev/sda5 (which is the swap). Could this be the problem? Let me know if there's more info required. I'm running a (mostly up-to-date) lenny system. -Stuart -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: 2 Disks (by label/UUID)
my thecus n2100 also stopped booting when trying to mont a memory stick to /media/sth via fstab and UUID. Someone should file a bug against .. Well, that was actually the problem: I do not know excatly what causedit (=whom to blame), but I did not find time. Maybe you could investigate? On Mon, 2008-04-21 at 21:39 +0200, DE POOTER Bart wrote: I know I had problems too with the UUID method at First ... The thing was, everyone mentioned to use UUID=x syntax, but mine only worked when using the full syntax like /dev/disk/by-uuid/ Don't know about others ! Bart -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Stuart Read Verzonden: maandag 21 april 2008 4:41 Aan: debian-arm@lists.debian.org Onderwerp: 2 Disks (by label/UUID) Hello, I was preparing to add a second harddisk to my NSLU2, and since previous messages on this list referenced a boot order problem with this, I followed the directions on the wiki (and some previous messages on this list). I have two questions: 1) Why does the troubleshooting page on the wiki say that the UUID method there is no good when that's the method suggested on this list by Martin M. et al? 2) After updating the flash, the NSLU2 failed to boot (orange LED) so I had to restore my old fstab and flash to get it booting again. Is there a step besides updating fstab, creating a new initramfs, and flashing it? I noticed that in /etc/initramfs-tools/conf.d there is a file named resume which references /dev/sda5 (which is the swap). Could this be the problem? Let me know if there's more info required. I'm running a (mostly up-to-date) lenny system. -Stuart -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
