Bug#506252: success: d-i lenny rc1 on nslu2 armel

2009-01-06 Thread Devin Carraway
On Tue, Jan 06, 2009 at 05:03:54PM +0100, Martin Michlmayr wrote: > Devin, I'm inclined to close this bug report since I believe that d-i > is doing the right thing. There are reports that the clock sometimes > gets "stuck" on the NSLU2, but I don't think Debian/debian-installer > can do anything

Bug#506252: success: d-i lenny rc1 on nslu2 armel

2008-11-20 Thread Devin Carraway
On Thu, Nov 20, 2008 at 08:40:59AM -0200, Otavio Salvador wrote: > >> Could you give a try in current daily installer since it has a new > >> kernel version and see if RTC looks OK? If it doesn't it looks like a > >> kernel issue to me. > > > > Devin, don't waste your time - nothing has changed in

Bug#506252: success: d-i lenny rc1 on nslu2 armel

2008-11-19 Thread Devin Carraway
Package: installation-reports Severity: normal -- Package-specific info: Boot method: network (upslug2) Image version: Unofficial nslu2 image (stock lenny image plus onboard ethernet microcode), http://www.slug-firmware.net/d-dls.php Date: Machine: Linksys NSLU2 Partitions: Base System In

Bug#272636: Retry with pre-rc2

2004-10-02 Thread Devin Carraway
Repeated the install, same machine, with pre-rc2. No regressions, but the same highlighting issue. -- Devin \ aqua(at)devin.com, IRC:Requiem; http://www.devin.com Carraway \ 1024D/E9ABFCD2: 13E7 199E DD1E 65F0 8905 2E43 5395 CA0D E9AB FCD2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a

Bug#272636: installation-reports: Netra T105: nearly perfect

2004-09-21 Thread Devin Carraway
Package: installation-reports Debian-installer-version: 20040802 netboot Date: 2004-09-19 Severity: normal Method: rarp+tftp+http from http.us.debian.org Machine: Sun Netra T105 Processor: TI UltraSparc IIi (Sabre) Memory: 311296k Root Device: Seagate ST39102LC, symbios SCSI Partition Table: Dis

Bug#241009: installation-reports: success with minor issues, 1ghz tibook

2004-03-30 Thread Devin Carraway
Slight clarification, since the reportbug data might be misleading otherwise. I went through the whole install for sarge, and the report is against that. I then took the machine up to sid before filing the report. (I did ask for unstable the first time around without thinking; base went in just

Bug#241009: installation-reports: success with minor issues, 1ghz tibook

2004-03-30 Thread Devin Carraway
Package: installation-reports Version: d-i beta3; cdrom images, http install Severity: normal INSTALL REPORT Debian-installer-version: beta3, March 29th uname -a: Linux cricket 2.6.5-rc2-ben0 #1 Tue Mar 30 00:12:29 PST 2004 ppc GNU/Linux Date: March 30th, ~8pm Method: CDROM bootstrap, HTTP insta

Bug#145469: boot-floppies: [woody] installer went into infinite loop after rebooted

2002-05-02 Thread Devin Carraway
This is probably a duplicate of Bug #145434. Installing base-config 1.33.18 (currently in Sid) fixes the problem. -- Devin \ aqua(at)devin.com, 1024D/E9ABFCD2; http://www.devin.com Carraway \ IRC: Requiem GCS/CC/L s-:--- !a !tv C$ ULB+++$ O+@ P L+++ -- To UNSUBSCRIBE, email to [EMAIL

Bug#145469: [woody] installer went into infinite loop after rebooted

2002-05-02 Thread Devin Carraway
This also occurs on powerpc (new-powerpc on ibook) using this afternoon's Woody bootfloppies. Scripts from /tmp/base-config.$$/ are failing in association with db_* calls. After disabling a couple by inserting "exit 0" at the beginning, I switched 50tasksel to be run with bash -x, yielding this