Re: Users of testing (lenny) - do not upgrade!
Simon Voortman wrote: I did a fresh install with the latest release from http://www.slug-firmware.net/ because it says: Latest release Debian/NSLU2 Experimental 5.0beta1 (Unreleased Beta) Old releases These releases are obsolete and no longer supported. Please use the latest release. Debian/NSLU2 Stable 4.0r3 I've fixed that page so that it recommends the latest stable release instead of recommending the unreleased beta version. Sorry for the incorrect advice caused by an automatically generated page layout. -- Rod -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Thecus N299
How does "solder onto the RedBoot UART" count as a "remote exploit"? ;) -Original Message- From: "Michael Goetze" <[EMAIL PROTECTED]> To: debian-arm@lists.debian.org Sent: 4/29/08 3:42 PM Subject: Thecus N299 Hi, aparently Thecus has released a new, incredibly cheap, 2-Bay NAS, the N299. It seems to run on the Gemini SL3516[1] which seems to have all the necessary code already available under the GPL [2]. Now, since I'm a cheapo, and the N2100 costs twice as much, I'm quite interested. I wonder if anyone could (maybe someone has actually seen one?) could give me an educated guess as to ... whether it will be possible to get a root shell without waiting for a new remote exploit? ... whether it will eventually be possible to run Debian on this box? ... how it might stack up to the N2100 performance-wise? All comments appreciated! Kind regards, Michael (Please CC me as I am not subscribed.) [1] http://www.storlinksemi.com/product_page.cfm?RecordID=3 [2] http://laforge.gnumonks.org/weblog/2008/01/20/ - currently down? But available in Google's cache -- 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]
Thecus N299
Hi, aparently Thecus has released a new, incredibly cheap, 2-Bay NAS, the N299. It seems to run on the Gemini SL3516[1] which seems to have all the necessary code already available under the GPL [2]. Now, since I'm a cheapo, and the N2100 costs twice as much, I'm quite interested. I wonder if anyone could (maybe someone has actually seen one?) could give me an educated guess as to ... whether it will be possible to get a root shell without waiting for a new remote exploit? ... whether it will eventually be possible to run Debian on this box? ... how it might stack up to the N2100 performance-wise? All comments appreciated! Kind regards, Michael (Please CC me as I am not subscribed.) [1] http://www.storlinksemi.com/product_page.cfm?RecordID=3 [2] http://laforge.gnumonks.org/weblog/2008/01/20/ - currently down? But available in Google's cache -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Users of testing (lenny) - do not upgrade!
Martin Michlmayr schreef: Kevin Price reported that the new initramfs-tools in testing (version 0.92) generates a ramdisk that does not boot correctly on the NSLU2 - it makes your system unbootable (see bug #478236). Note that this bug only affects users of testing - users of Debian 4.0 are not affected. I did a fresh install with the latest release from http://www.slug-firmware.net/ because it says: Latest release Debian/NSLU2 Experimental 5.0beta1 (Unreleased Beta) Old releases These releases are obsolete and no longer supported. Please use the latest release. Debian/NSLU2 Stable 4.0r3 1) If your root partition is on sda1 and you run arm (rather than armel), you can download the following image and flash it with upslug2: http://www.cyrius.com/debian/nslu2/files/sda1-2.6.24-1.bin It is, I do, and I downloaded and flashed this kernel. I hope this works for you. If not, please let me know. It does! Thank you very much! I thought you would be pleased to know it works, too! Sorry for the inconveniences. Oh, nevermind - it's working now! Cheers, Simon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Users of testing (lenny) - do not upgrade!
Kevin Price reported that the new initramfs-tools in testing (version 0.92) generates a ramdisk that does not boot correctly on the NSLU2 - it makes your system unbootable (see bug #478236). Note that this bug only affects users of testing - users of Debian 4.0 are not affected. If you run Debian testing (lenny) rather than stable (etch) on your NSLU2, please do _not_ upgrade until a fixed package enters testing. If you have already upgraded but not rebooted yet, you should be able to flash the old, working image with: cd /boot mv initrd.img-2.6.24-1-ixp4xx initrd.img-2.6.24-1-ixp4xx~ mv initrd.img-2.6.24-1-ixp4xx initrd.img-2.6.24-1-ixp4xx.bak flash-kernel If you have upgraded, rebooted and your NSLU2 now fails to boot, there are two recovery options: 1) If your root partition is on sda1 and you run arm (rather than armel), you can download the following image and flash it with upslug2: http://www.cyrius.com/debian/nslu2/files/sda1-2.6.24-1.bin 2) If the first option doesn't work for you, you can download the "etch" installer from http://slug-firmware.net, flash it, start it, run it until the partitioning software starts, then go back, open a shell (last but one point in the menu) and issue the following commands: ~ # mkdir /x ~ # mount /dev/sda1 /x ~ # mount -t proc none /x/proc ~ # mount --bind /dev/ /x/dev ~ # chroot /x sh-3.1# cd /boot sh-3.1# mv initrd.img-2.6.24-1-ixp4xx initrd.img-2.6.24-1-ixp4xx~ sh-3.1# mv initrd.img-2.6.24-1-ixp4xx initrd.img-2.6.24-1-ixp4xx.bak sh-3.1# sh-3.1# flash-kernel Flashing kernel: done. Flashing initramfs: done. sh-3.1# sh-3.1# exit ~ # umount /x/proc ~ # umount /x/dev ~ # umount /x ~ # reboot I hope this works for you. If not, please let me know. Sorry for the inconveniences. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#478236: initramfs 0.92 makes slug unbootable (armel/lenny)
I can confirm this bug. Do not upgrade your nslu2 in case you're running testing (lenny) rather than stable (etch)! The initramfs-tools maintainer will upload a fixed package later today. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2 Disks (by label/UUID)
* Stuart Read <[EMAIL PROTECTED]> [2008-04-27 23:23]: > Reading package lists... Error! > E: Malformed 3rd word in the Status line > E: Error occurred while processing initramfs-tools (UsePackage2) > E: Problem with MergeList /var/lib/dpkg/status > E: The package lists or status file could not be parsed or opened. This doesn't look good. Can you send /var/lib/dpkg/status to me? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#478236: initramfs 0.92 makes slug unbootable (armel/lenny)
On Mon, 28 Apr 2008, Kevin Price wrote: > maximilian attems schrieb: > > is it reproducible? > > Yes. I updated a bunch of packages, making the slug unbootable. Then I > flashed the backup. After a normal boot, I installed initramfs-tools > 0.91e, flashed again, which made it boot OK. Then I updated only > initrd-tools to 0.92, making it unbootable again. so it happened 1x, i wouldn't call that yet reproducible ;) anyway 0.92 added a bunch of network drivers new one, so yes bigger size. can you please reinstall 0.92 and set MODULES=dep in /etc/initramfs-tools/initramfs.conf > So generating a broken initrd seems to be well reproducible. I presume > that the bad initrd always fails to boot and the good one always boots > OK, which was confirmed at least a few times. > > > if yes please put somewhere the good and the bad initramfs for review. > > http://www.kevin-price.de/478236/ look both ok. > I can see that the broken one is bigger. Might there be a capacity issue > in my flash ROM? Here's my /proc/mtd: (good working state) > dev:size erasesize name > mtd0: 0004 0002 "RedBoot" > mtd1: 0002 0002 "SysConf" > mtd2: 0002 0002 "Loader" > mtd3: 0016 0002 "Kernel" > mtd4: 0060 0002 "Ramdisk" > mtd5: 0002 0002 "FIS directory" > > "cat /dev/mtdblock*" produces 8388608 bytes of output. hmm might be the indication. > > ok cool so it will be debuggable > > Yes. Is there a clean way to activate debugging messages in the initrd? man initramfs-tools, search for debug boot param. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Progress on Bug#444271 / N2100 disk performance
Martin Michlmayr schrieb: * Tomasz Chmielewski <[EMAIL PROTECTED]> [2008-04-29 14:56]: Odd, they definitely sped up things here (on N2100). Could you send me your .config for N2100? I've attached a config file, but basically, you just need to enable the DMA engine and the options that the patches add. I tried all possible DMA combinations without much success. But I see you have SATA as modules, whereas I have them built-in. And some other minor changes. Something has to make a difference here. I didn't use n4100 for some time now: it is all covered in dust now and I won't check it any time soon. Perhaps I'll order a mini-PCI - CF adapter[1] first, so that I can boot the device even if it doesn't have any hard drives, and rootfs (on a CF card) is independent of storage. [1] http://www.globalamericaninc.com/product_info.php?products_id=1801120 -- Tomasz Chmielewski http://wpkg.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Progress on Bug#444271 / N2100 disk performance
* Tomasz Chmielewski <[EMAIL PROTECTED]> [2008-04-29 14:56]: >> Odd, they definitely sped up things here (on N2100). > Could you send me your .config for N2100? I've attached a config file, but basically, you just need to enable the DMA engine and the options that the patches add. -- Martin Michlmayr http://www.cyrius.com/ # # Automatically generated make config: don't edit # Linux kernel version: 2.6.24 # Mon Feb 18 18:53:23 2008 # CONFIG_ARM=y CONFIG_SYS_SUPPORTS_APM_EMULATION=y # CONFIG_GENERIC_GPIO is not set # CONFIG_GENERIC_TIME is not set # CONFIG_GENERIC_CLOCKEVENTS is not set CONFIG_MMU=y # CONFIG_NO_IOPORT is not set CONFIG_GENERIC_HARDIRQS=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_TRACE_IRQFLAGS_SUPPORT=y CONFIG_HARDIRQS_SW_RESEND=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_RWSEM_GENERIC_SPINLOCK=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ZONE_DMA=y CONFIG_VECTORS_BASE=0x CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y # CONFIG_USER_NS is not set # CONFIG_PID_NS is not set CONFIG_AUDIT=y # CONFIG_IKCONFIG is not set CONFIG_LOG_BUF_SHIFT=14 CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set CONFIG_CGROUP_NS=y CONFIG_FAIR_GROUP_SCHED=y CONFIG_FAIR_USER_SCHED=y # CONFIG_FAIR_CGROUP_SCHED is not set CONFIG_CGROUP_CPUACCT=y CONFIG_SYSFS_DEPRECATED=y CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLAB=y # CONFIG_SLUB is not set # CONFIG_SLOB is not set CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_MODVERSIONS=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_BLOCK=y CONFIG_LBD=y # CONFIG_BLK_DEV_IO_TRACE is not set CONFIG_LSF=y # CONFIG_BLK_DEV_BSG is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" # # System Type # # CONFIG_ARCH_AAEC2000 is not set # CONFIG_ARCH_INTEGRATOR is not set # CONFIG_ARCH_REALVIEW is not set # CONFIG_ARCH_VERSATILE is not set # CONFIG_ARCH_AT91 is not set # CONFIG_ARCH_CLPS7500 is not set # CONFIG_ARCH_CLPS711X is not set # CONFIG_ARCH_CO285 is not set # CONFIG_ARCH_EBSA110 is not set # CONFIG_ARCH_EP93XX is not set # CONFIG_ARCH_FOOTBRIDGE is not set # CONFIG_ARCH_NETX is not set # CONFIG_ARCH_H720X is not set # CONFIG_ARCH_IMX is not set # CONFIG_ARCH_IOP13XX is not set CONFIG_ARCH_IOP32X=y # CONFIG_ARCH_IOP33X is not set # CONFIG_ARCH_IXP23XX is not set # CONFIG_ARCH_IXP2000 is not set # CONFIG_ARCH_IXP4XX is not set # CONFIG_ARCH_L7200 is not set # CONFIG_ARCH_KS8695 is not set # CONFIG_ARCH_NS9XXX is not set # CONFIG_ARCH_MXC is not set # CONFIG_ARCH_PNX4008 is not set # CONFIG_ARCH_PXA is not set # CONFIG_ARCH_RPC is not set # CONFIG_ARCH_SA1100 is not set # CONFIG_ARCH_S3C2410 is not set # CONFIG_ARCH_SHARK is not set # CONFIG_ARCH_LH7A40X is not set # CONFIG_ARCH_DAVINCI is not set # CONFIG_ARCH_OMAP is not set # # IOP32x Implementation Options # # # IOP32x Platform Types # CONFIG_MACH_EP80219=y CONFIG_MACH_GLANTANK=y CONFIG_ARCH_IQ80321=y CONFIG_ARCH_IQ31244=y CONFIG_MACH_N2100=y CONFIG_IOP3XX_ATU=y # CONFIG_MACH_EM7210 is not set # # Boot options # # # Power management # CONFIG_PLAT_IOP=y # # Processor Type # CONFIG_CPU_32=y CONFIG_CPU_XSCALE=y CONFIG_CPU_32v5=y CONFIG_CPU_ABRT_EV5T=y CONFIG_CPU_CACHE_VIVT=y CONFIG_CPU_TLB_V4WBI=y CONFIG_CPU_CP15=y CONFIG_CPU_CP15_MMU=y # # Processor Features # # CONFIG_ARM_THUMB is not set # CONFIG_CPU_DCACHE_DISABLE is not set # CONFIG_OUTER_CACHE is not set # CONFIG_IWMMXT is not set CONFIG_XSCALE_PMU=y # # Bus support # CONFIG_PCI=y CONFIG_PCI_SYSCALL=y # CONFIG_ARCH_SUPPORTS_MSI is not set CONFIG_PCI_LEGACY=y # CONFIG_PCCARD is not set # # Kernel Features # # CONFIG_TICK_ONESHOT is not set # CONFIG_PREEMPT is not set # CONFIG_NO_IDLE_HZ is not set CONFIG_HZ=100 # CONFIG_AEABI is not set # CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set CONFIG_SELECT_MEMORY_
Re: Progress on Bug#444271 / N2100 disk performance
Martin Michlmayr schrieb: * Tomasz Chmielewski <[EMAIL PROTECTED]> [2008-04-29 14:36]: Last time I tried those patches on N4100, which should be similar, (2.6.23-iop series, and every earlier release) disk performance was still very poor. Odd, they definitely sped up things here (on N2100). Could you send me your .config for N2100? -- Tomasz Chmielewski http://wpkg.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Progress on Bug#444271 / N2100 disk performance
* Tomasz Chmielewski <[EMAIL PROTECTED]> [2008-04-29 14:36]: > Last time I tried those patches on N4100, which should be similar, > (2.6.23-iop series, and every earlier release) disk performance was > still very poor. Odd, they definitely sped up things here (on N2100). -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Progress on Bug#444271 / N2100 disk performance
Martin Michlmayr schrieb: * Tomasz Chmielewski <[EMAIL PROTECTED]> [2008-04-24 13:23]: Are these patches the same as those on http://sf.net/projects/xscaleiop or is it something different? Yeah, the patches are in there. Also look for Dan William's mail to linux-arm-kernel a few weeks ago where he submitted the DMA related patches. Last time I tried those patches on N4100, which should be similar, (2.6.23-iop series, and every earlier release) disk performance was still very poor. I didn't try 2.6.24-iop1 though. -- Tomasz Chmielewski http://wpkg.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
