Bug#805342: marked as done (Stretch Alpha 4 Installation Report (failed))

2020-08-20 Thread Debian Bug Tracking System
Your message dated Fri, 21 Aug 2020 04:58:02 +0200 with message-id <20200821045802.07acb7c9ded347064600d...@mailbox.org> and subject line Re: Mass-closing old installation-report bugs --- round 5 has caused the Debian Bug report #805342, regarding Stretch Alpha 4 Installation Report (

Bug#805342: Stretch Alpha 4 Installation Report (failed)

2015-11-16 Thread Joe Ciarcia
Package: installation-reports Boot method: USB Stick Image version: http://cdimage.debian.org/cdimage/stretch_di_alpha4/amd64/iso-dvd/debian-stretch-DI-alpha4-amd64-DVD-1.iso Date: 11/16/2015 Machine: Dell XPS 13 (late 2015) with WiFi/Bluetooth card change from stock to an Intel 7265.

Re: Installation report [failed] [Was: Re: No kernel modules were found PowerPC Businesscard and Netinst daily CDs]

2011-08-14 Thread Rick Thomas
Sure did... See bug #636269. Enjoy! Rick On Aug 13, 2011, at 7:52 AM, Otavio Salvador wrote: On Mon, Aug 1, 2011 at 10:15, Rick Thomas rbtho...@pobox.com wrote: Install went without a hitch until it came time to reboot into the newly installed system. Did you try to install a more

Re: Installation report [failed] [Was: Re: No kernel modules were found PowerPC Businesscard and Netinst daily CDs]

2011-08-13 Thread Otavio Salvador
On Mon, Aug 1, 2011 at 10:15, Rick Thomas rbtho...@pobox.com wrote: Install went without a hitch until it came time to reboot into the newly installed system. Did you try to install a more recent image? If don't, could you give it a new try and send us the syslog (gzipped) thus we can guess

Re: Installation report [failed] [Was: Re: No kernel modules were found PowerPC Businesscard and Netinst daily CDs]

2011-08-01 Thread Rick Thomas
In contrast to Jeroen's report that Wheezy installation went fine on G3 Mac... I just tried the sid_d-i testing daily businesscard. (details of exactly which iso are available on request) Install went without a hitch until it came time to reboot into the newly installed system. The

Re: Installation report [failed]

2011-08-01 Thread Rick Thomas
On Aug 1, 2011, at 4:15 AM, Rick Thomas wrote: In contrast to Jeroen's report that Wheezy installation went fine on G3 Mac... I just tried the sid_d-i testing daily businesscard. (details of exactly which iso are available on request) Install went without a hitch until it came time

Installation report [failed] [Was: Re: No kernel modules were found PowerPC Businesscard and Netinst daily CDs]

2011-07-29 Thread Rick Thomas
OK, I downloaded http://cdimage.debian.org/cdimage/daily-builds/sid_d-i/arch-latest/powerpc/iso-cd/debian-testing-powerpc-businesscard.iso Daily build #5 for powerpc, using installer build from sid These images will install the testing version of Debian, currently Wheezy. ... This

Re: Installation report [failed] [Was: Re: No kernel modules were found PowerPC Businesscard and Netinst daily CDs]

2011-07-29 Thread Colin Watson
On Fri, Jul 29, 2011 at 02:18:29AM -0400, Rick Thomas wrote: After booting the CD, there were a lot of messages that scrolled by too fast to get details, but all of them seemed to have something to do with missing some UTF8 localization stuff. This is the cause of everything else. I *think*

Re: Installation report [failed] [Was: Re: No kernel modules were found PowerPC Businesscard and Netinst daily CDs]

2011-07-29 Thread Rick Thomas
Hi David, Hi Colin, On Jul 29, 2011, at 12:35 PM, David Ricar wrote: On 07/29/2011 08:18 AM, Rick Thomas wrote: After booting the CD, there were a lot of messages that scrolled by too fast to get details, but all of them seemed to have something to do with missing some UTF8

Re: Installation report [failed] [Was: Re: No kernel modules were found PowerPC Businesscard and Netinst daily CDs]

2011-07-29 Thread Otavio Salvador
On Fri, Jul 29, 2011 at 20:59, Rick Thomas rbtho...@pobox.com wrote: Colin, do you have any idea when your fix will be available for testing?  Can you let me know when it happens? It is just a matter of waiting a cuple of days. If it doesn't work we can check the build log and see if it has

Re: Installation report [failed] [Was: Re: No kernel modules were found PowerPC Businesscard and Netinst daily CDs]

2011-07-29 Thread Rick Thomas
OK. I'll try again on Monday or Tuesday (busy weekend coming up). Rick On Jul 29, 2011, at 3:59 PM, Otavio Salvador wrote: On Fri, Jul 29, 2011 at 20:59, Rick Thomas rbtho...@pobox.com wrote: Colin, do you have any idea when your fix will be available for testing? Can you let me know

Bug#396469: marked as done (Installation report: failed install on Toshiba Satellite)

2010-09-08 Thread Debian Bug Tracking System
Your message dated Wed, 08 Sep 2010 03:58:19 + with message-id e1otbnf-0005ny...@ravel.debian.org and subject line Closing old installation report #396469 has caused the Debian Bug report #396469, regarding Installation report: failed install on Toshiba Satellite to be marked as done

Bug#405397: marked as done (installation-report: Failed wireless install on Sony Vaio )

2010-09-08 Thread Debian Bug Tracking System
Your message dated Wed, 08 Sep 2010 03:58:23 + with message-id e1otbnj-0005tx...@ravel.debian.org and subject line Closing old installation report #405397 has caused the Debian Bug report #405397, regarding installation-report: Failed wireless install on Sony Vaio to be marked as done

Bug#494978: marked as done (installation-report: failed to install Debian 4.0r4a powerpc on an IBM 52a using VIOS 1.5 with virtual optical drive)

2010-09-08 Thread Debian Bug Tracking System
Your message dated Wed, 08 Sep 2010 03:58:31 + with message-id e1otbnr-0005kt...@ravel.debian.org and subject line Closing old installation report #494978 has caused the Debian Bug report #494978, regarding installation-report: failed to install Debian 4.0r4a powerpc on an IBM 52a using VIOS

Bug#280598: marked as done (installation-report (failed))

2010-09-07 Thread Debian Bug Tracking System
Your message dated Wed, 08 Sep 2010 03:57:46 + with message-id e1otbn8-0004g4...@ravel.debian.org and subject line Closing old installation report #280598 has caused the Debian Bug report #280598, regarding installation-report (failed) to be marked as done. This means that you claim

Bug#306786: marked as done (Debian-Installer installation report: failed on Dell PowerEdge 2850 with Perc 4e/Di RAID with 2.6 kernel)

2010-09-07 Thread Debian Bug Tracking System
Your message dated Wed, 08 Sep 2010 03:57:57 + with message-id e1otbnj-0004ea...@ravel.debian.org and subject line Closing old installation report #306786 has caused the Debian Bug report #306786, regarding Debian-Installer installation report: failed on Dell PowerEdge 2850 with Perc 4e/Di

Bug#349250: marked as done (installation-report: failed to detect volume device)

2010-09-07 Thread Debian Bug Tracking System
Your message dated Wed, 08 Sep 2010 03:58:09 + with message-id e1otbnv-00053a...@ravel.debian.org and subject line Closing old installation report #349250 has caused the Debian Bug report #349250, regarding installation-report: failed to detect volume device to be marked as done. This means

Bug#352750: marked as done (Installation report (failed w/ daily))

2009-10-08 Thread Debian Bug Tracking System
Your message dated Thu, 8 Oct 2009 14:14:18 +0200 with message-id bb145bd20910080514k2b78f610se49d5988407e3...@mail.gmail.com and subject line Re: Bug#352750: Installation report (failed w/ daily) has caused the Debian Bug report #352750, regarding Installation report (failed w/ daily

Bug#494978: installation-report: failed to install Debian 4.0r4a powerpc on an IBM 52a using VIOS 1.5 with virtual optical drive

2008-08-13 Thread Folkert van Heusden
Package: installation-reports Version: 2.35 Severity: normal failed to install Debian 4.0r4a powerpc on an IBM 52a using VIOS 1.5 with virtual optical drive - created an LPAR - connected to the internal virtual lan with access to the world - 32GB logical volume from VIOS served via

Bug#385188: marked as done (installation-report: Failed to determine the codename for the release (sparc, daily 20060828))

2007-02-01 Thread Debian Bug Tracking System
Your message dated Thu, 01 Feb 2007 19:23:20 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#385188: installation-report: Failed to determine the codename for the release (sparc, daily 20060828) has caused the attached Bug report to be marked as done. This means that you claim

Bug#405397: installation-report: Failed wireless install on Sony Vaio

2007-01-05 Thread Joey Hess
Toshikazu Aiyama, Ph.D. wrote: 3. Expert install fails producing the following message: [!!] Configure the network Network autoconfiguration failed Your network is probably not using the DHCP protocol. Alternatively, the DHCP server may be slow or some network hardware is not working

Bug#405397: installation-report: Failed wireless install on Sony Vaio

2007-01-03 Thread Toshikazu Aiyama, Ph.D.
Package: installation-reports Version: ??? report templates are not produced Severity: ??? I used testing netinst image obtained from http://cdimage.debian.org/cdimage/daily-builds/daily/current/i386/iso-cd/ The image is dated Jan 1, 2007 Machine: Sony Vaio Note PCG-V505S/PB Partitions:

Bug#396469: Installation report: failed install on Toshiba Satellite

2006-11-03 Thread Frans Pop
On Tuesday 31 October 2006 23:23, Bill McNeill wrote: I'm stuck. Can't get Debian to work on this machine. I did some Googling and determined that others have hit this error, but there appears to be no clear workaround. Could it be that you were using the installer for Sarge? If so, could

Bug#396469: Installation report: failed install on Toshiba Satellite

2006-11-02 Thread Frans Pop
On Wednesday 01 November 2006 15:45, Bill McNeill wrote: The machine is hard hung, so I'm not in a debug shell and I can't page up to see what came before the segment fault. Unfortunately, I can't see what was loading before the fault: the very top of the screen is filled up with the register

Bug#396469: Installation report: failed install on Toshiba Satellite

2006-11-02 Thread Bill McNeill
Here's the entire screen:cc8394ed*pde = 012ef067 *pte = Oops: CPU: 0EIP: 001:[cc8394ed] Not tainted EFLAGS: 00010046eax: ebx: cc825b50 ecx: edx: 0cfc esi: 00ff edi: cbfe3400 ebp: esp: cb19e84 ds: 0018 es: 0018 ss: 0018Process modprobe (pid: 43,

Bug#396469: Installation report: failed install on Toshiba Satellite

2006-11-01 Thread Bill McNeill
The machine is hard hung, so I'm not in a debug shell and I can't page up to see what came before the segment fault. Unfortunately, I can't see what was loading before the fault: the very top of the screen is filled up with the register dump and whatnot. I don't know how to figure out what was

Bug#396469: Installation report: failed install on Toshiba Satellite

2006-10-31 Thread Bill McNeill
Package: installation-reports Boot method: CDImage version: www.debian.org in October 2006 Date: 2:00 p.m. October 31, 2006 Machine: Toshiba SatelliteProcessor: Intel Celeron 2.80 GHz Memory: ???Partitions: Can't run df. I took the defaults the install program gave me: one for files plus a swap

Bug#396469: Installation report: failed install on Toshiba Satellite

2006-10-31 Thread Frans Pop
On Tuesday 31 October 2006 23:23, Bill McNeill wrote: Machine: Toshiba Satellite Processor: Intel Celeron 2.80 GHz Strange, I have a quite similar machine which I reinstalled very recently and which works perfectly (Toshiba Satellite A40, Mobile Pentium 4, 2.8 GHz). Comments/Problems: I

Bug#385188: installation-report: Failed to determine the codename for the release (sparc, daily 20060828)

2006-08-29 Thread Joost van Baal
Package: installation-reports Version: 2.18 Severity: important Boot method: CD, via serial console using cu(1) Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/20060827/sparc/iso-cd/debian-testing-sparc-businesscard.iso , built on 20060828 Date: 2006-08-29, 18:00 Machine:

Bug#280598: installation-report (failed)

2004-11-10 Thread BranchingFactor
Package: installation-reports Debian-installer-version: debian.org, test version i386 of 08 Nov 2004 Date: 09 nov 2004 Team Debian, Attempts to install i386/20041108/sarge-i386-netinst on a new Dell Dimension 8400 3.0GHz P4 with 4GB RAM and two SATA drives failed with a no partitionable media

Bug#234768: marked as done (Installation Report (Failed horribly))

2004-07-05 Thread Debian Bug Tracking System
1Aw2jP-0003UC-00 for [EMAIL PROTECTED]; Wed, 25 Feb 2004 14:21:59 -0300 Date: Wed, 25 Feb 2004 14:21:59 -0300 From: Margarita Manterola [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Installation Report (Failed horribly) Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain

Bug#244451: Installation Report; Failed

2004-06-04 Thread Stephen T. Bellis
PROTECTED] To: Stephen T. Bellis [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, April 19, 2004 8:43 PM Subject: Re: Bug#244451: Installation Report; Failed Stephen T. Bellis wrote: It doesn't matter what I do I can't get this machine to mount ANY cd to preform the install. I've tried several d-i

Bug#244451: Installation Report; Failed

2004-06-04 Thread Joey Hess
Stephen T. Bellis wrote: I figured out that this problem is caused by the service partition on the hard drive. I don't know why but if there is no service partition everything goes fine. Having the service partition causes d-i to not be able to detect the cdrom. That's strange. Can you send

Re: Bug#244451: Installation Report; Failed

2004-06-04 Thread Stephen T. Bellis
That's strange. Can you send us enough info about this service partitionso we can try to set one up, and perhaps reprocude the bug? Thepartition layout, partition type, and the first several kilobytes ofsuch a partition might suffice to do it. It's listed as a compaq service partition in

Bug#234768: Installation Report (Failed horribly)

2004-05-26 Thread Martin Michlmayr
* tbm [EMAIL PROTECTED] [2004-05-03 02:09]: Can you please try the new beta4 from http://www.debian.org/devel/debian-installer/ to see if these other problems are still there? Can you please try new images from http://gluck.debian.org/cdimage/testing/sarge_d-i/ -- Martin Michlmayr [EMAIL

Bug#234768: Installation Report (Failed horribly)

2004-05-02 Thread Martin Michlmayr
* Margarita Manterola [EMAIL PROTECTED] [2004-02-25 14:21]: The prompting for the following floppy is not friendly. A polite and verbose message can be added quite easily. I think this has been done. * Config network: The host's name was not configured (known problem) Fixed.

Re: Bug#244451: Installation Report; Failed

2004-04-22 Thread Stephen T. Bellis
What happens if you go to a shell and manually try to mount the CD? I get a "not a directory" error Have you tried running the menu item that checks a CD for validity? Same Thing

Bug#244451: Installation Report; Failed

2004-04-19 Thread Joey Hess
Stephen T. Bellis wrote: It doesn't matter what I do I can't get this machine to mount ANY cd to preform the install. I've tried several d-i cd's including older versions that worked previously. I've also tried changing the cd drive to a HP 9900i with the same results. If you have a CD

Bug#244451: Installation Report; Failed

2004-04-18 Thread Stephen T. Bellis
Package: installation-reportsINSTALL REPORTDebian-installer-version: Daily Builds from 1-18, 4-9, 4.12, 4-15 and beta 3uname -a:Linux athena 2.4.24.p4smp.1 #1 SMP Wed Feb 18 23:56:52 CST 2004 i686 GNU/LinuxDate: My last attempt was todayMethod:netinstcd and business card cdMachine:Intel

Bug#239004: installation report (failed)

2004-03-25 Thread Jukka Neppius
Jukka Neppius [EMAIL PROTECTED] writes: Few hours ago I tried again with daily boot-floppies. I tried to install unstable from ftp.fi.debian.org. Same result as earlier: /usr/sbin/mkinird: Cannot determine root device Failed to create initrd image. dpkg: error processing

Bug#239004: installation report (failed)

2004-03-19 Thread Jukka Neppius
Package: installation-reports Version: 20040315 Debian-installer-version: debian/dists/testing/main/installer-i386/20040315/images/floppy Date: Fri Mar 19 19:25:04 EET 2004 Method: Boot from floppy. Packages from local md5sum tested partial mirror Machine: A PC Processor: K7 1.8 GHz Memory:

Re: Installation report: FAILED on i386

2004-03-17 Thread Nathanael Nerode
Martin Michlmayr wrote: Apparently beta3 has better SATA support. Can you try? I did. :-P Here's the lowdown: the installer basically works and installs the system. Unfortunately I can't get either grub or lilo to work, so I can't boot it. This may have something to do with device mapping

Re: Installation report: FAILED on i386

2004-03-17 Thread elijah wright
Apparently beta3 has better SATA support. Can you try? This may have something to do with device mapping in the BIOS -- I may not be feeding the right information to lilo and/or grub. Or it may have something to do with the fact that my system doesn't appear to have a 'compatibility

Re: Installation report: FAILED on i386

2004-03-17 Thread Nathanael Nerode
elijah wright wrote: Apparently beta3 has better SATA support. Can you try? This may have something to do with device mapping in the BIOS -- I may not be feeding the right information to lilo and/or grub. Or it may have something to do with the fact that my system doesn't appear to have a

Installation report: FAILED on i386

2004-03-17 Thread Toshikazu Aiyama, Ph.D.
About Message-id: [EMAIL PROTECTED] I have similar setup as follows: CPU: P4 1.6 GHz Make:Myself Chipset: i875/ICH5R M/B: Gigabyte GA-8i875 PATA Primary: Maxtor 160 GBSlave: None 2ndary: LG GSA-4081B Slave Ymaha CRW-F1 SATA0: Seagate 160GB

Bug#234768: Installation Report (Failed horribly)

2004-02-25 Thread Margarita Manterola
Package: installation-reports Debian-installer-version: Beta2 uname -a: Linux debian 2.4.22-1-386 #9 Sat Oct 4 14:30:39 EST 2003 i686 GNU/Linux ** Disclaimer: The installer failed horribly and did not install any kernel image at all. The kernel was install manually afterwards. ** Second

Re: Installation report - failed install

2004-02-24 Thread David Fries
What about compiling in CONFIG_IDEDISK_STROKE? I wouldn't think that it would hurt anything and it is required on older systems. [EMAIL PROTECTED] Wrote: It seems that debootstrap from unstable is already aware of the libdevmapper1.00 dependency. See

Installation report - failed install

2004-02-21 Thread David Fries
Two big problems, libdevmapper1.00 now needs to be installed, Another system with a 120GB drive requires CONFIG_IDEDISK_STROKE compiled into the kernel to see the entire drive. I used the three floppy images (boot, root, net drivers) off the business card iso from here.

Re: Installation report - failed install

2004-02-21 Thread Andre Luis Lopes
Hello, On Sat, Feb 21, 2004 at 11:14:31AM -0600, David Fries wrote: Two big problems, libdevmapper1.00 now needs to be installed, Another system with a 120GB drive requires CONFIG_IDEDISK_STROKE compiled into the kernel to see the entire drive. I used the three floppy images (boot, root,

Re: Installation report: FAILED on i386

2004-01-27 Thread Nathanael Nerode
Herbert Xu wrote: Nathanael Nerode [EMAIL PROTECTED] wrote: 2 Serial ATA drives, 1 IDE drive, e1000 Ethernet card. * It hangs on loading module ide-detect if RAID is disabled in the BIOS. * If RAID is enabled in the BIOS, it gets past that, but it never detects either Serial ATA drive. *

Re: Re: Installation report: FAILED on i386

2004-01-20 Thread Martin Michlmayr
* Nathanael Nerode [EMAIL PROTECTED] [2004-01-20 12:03]: So it turns out, having installed Linux to the one drive which is visible to Linux, that the BIOS won't boot from that drive. And I can't Boot from floppy or CD and use root=/dev/... or boot from the net via PXE. Or can you add a

Re: Re: Installation report: FAILED on i386

2004-01-20 Thread Nathanael Nerode
* Nathanael Nerode [EMAIL PROTECTED] [2004-01-18 18:44]: Perhaps you didn't notice that I'm completely stuck on another matter (the wget failure). Happy to try once I can work around that. Put the drive in another PC and use debootstrap to create a base system. Or install another distro, make a

Re: Re: Installation report: FAILED on i386

2004-01-20 Thread Joey Hess
Martin Michlmayr wrote: Boot from floppy or CD and use root=/dev/... I don't think that works, you get the d-i initrd, which is not very good at booting a regular debian system. -- see shy jo signature.asc Description: Digital signature

Re: Re: Installation report: FAILED on i386

2004-01-20 Thread Martin Michlmayr
* Joey Hess [EMAIL PROTECTED] [2004-01-20 12:43]: Boot from floppy or CD and use root=/dev/... I don't think that works, you get the d-i initrd, which is not very good at booting a regular debian system. Yeah, you'll need a special CD. However, this used to work with woody - I really hope

Re: Re: Installation report: FAILED on i386

2004-01-20 Thread Joey Hess
Martin Michlmayr wrote: Yeah, you'll need a special CD. However, this used to work with woody - I really hope we can make a rescue option which allows this. It has been useful many times. If we had a good and reasonably small rescue initrd, we could include it on the CD easily. -- see shy

Re: Re: Installation report: FAILED on i386

2004-01-20 Thread Martin Michlmayr
* Joey Hess [EMAIL PROTECTED] [2004-01-20 13:12]: If we had a good and reasonably small rescue initrd, we could include it on the CD easily. Yeah, but even booting without an initrd (from an existing installation) should be possible. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE,

Re: Re: Installation report: FAILED on i386

2004-01-20 Thread Joey Hess
Martin Michlmayr wrote: * Joey Hess [EMAIL PROTECTED] [2004-01-20 13:12]: If we had a good and reasonably small rescue initrd, we could include it on the CD easily. Yeah, but even booting without an initrd (from an existing installation) should be possible. The standard debian install

Re: Installation report: FAILED on i386

2004-01-20 Thread Nathanael Nerode
Martin Michlmayr wrote: * Nathanael Nerode [EMAIL PROTECTED] [2004-01-20 12:03]: So it turns out, having installed Linux to the one drive which is visible to Linux, that the BIOS won't boot from that drive. And I can't Boot from floppy or CD and use root=/dev/... or boot from the net via PXE.

Re: Installation report: FAILED on i386

2004-01-18 Thread Herbert Xu
Nathanael Nerode [EMAIL PROTECTED] wrote: 2 Serial ATA drives, 1 IDE drive, e1000 Ethernet card. * It hangs on loading module ide-detect if RAID is disabled in the BIOS. * If RAID is enabled in the BIOS, it gets past that, but it never detects either Serial ATA drive. * DHCP configuration

Re: Installation report: FAILED on i386

2004-01-18 Thread Nathanael Nerode
Herbert Xu wrote: Nathanael Nerode [EMAIL PROTECTED] wrote: 2 Serial ATA drives, 1 IDE drive, e1000 Ethernet card. * It hangs on loading module ide-detect if RAID is disabled in the BIOS. * If RAID is enabled in the BIOS, it gets past that, but it never detects either Serial ATA drive. *

Re: Installation report: FAILED on i386

2004-01-18 Thread Martin Michlmayr
* Nathanael Nerode [EMAIL PROTECTED] [2004-01-18 18:44]: Perhaps you didn't notice that I'm completely stuck on another matter (the wget failure). Happy to try once I can work around that. Put the drive in another PC and use debootstrap to create a base system. Or install another distro,

Installation report: FAILED on i386

2004-01-17 Thread Nathanael Nerode
2 Serial ATA drives, 1 IDE drive, e1000 Ethernet card. * It hangs on loading module ide-detect if RAID is disabled in the BIOS. * If RAID is enabled in the BIOS, it gets past that, but it never detects either Serial ATA drive. * DHCP configuration is slow and flaky but eventually works. *

Re: Installation report: FAILED on i386

2004-01-17 Thread Martin Michlmayr
* Nathanael Nerode [EMAIL PROTECTED] [2004-01-17 19:15]: 2 Serial ATA drives, 1 IDE drive, e1000 Ethernet card. * If RAID is enabled in the BIOS, it gets past that, but it never detects either Serial ATA drive. Does a standard 2.4 kernel normally work? Or do you have patches or 2.6? --

Re: Installation report: FAILED on i386

2004-01-17 Thread Martin Michlmayr
* Nathanael Nerode [EMAIL PROTECTED] [2004-01-17 20:26]: the mysterious hang was much more disturbing. I know. :/ Other people have experienced it as well (e.g. 224494), but I don't think our kernel maintainer has looked at it yet. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE,

Re: Installation report: FAILED on i386

2004-01-17 Thread Nathanael Nerode
Martin Michlmayr wrote: * Nathanael Nerode [EMAIL PROTECTED] [2004-01-17 19:15]: 2 Serial ATA drives, 1 IDE drive, e1000 Ethernet card. * If RAID is enabled in the BIOS, it gets past that, but it never detects either Serial ATA drive. Does a standard 2.4 kernel normally work? Or do you have

Bug#227917: Fw: Debian Sarge Installation report: failed on Alpha DS 10 (netinst image)

2004-01-15 Thread Szymon Juraszczyk
Package: installation-reports INSTALL REPORT Debian-installer-version: http://gluck.debian.org/cdimage/testing/netinst/alpha/20040114/sarge-alpha-netinst.iso uname -a: N/A Date: 2004-01-15 Method: burned CD, booted with 'boot dqb0' Machine: Compaq AlphaServer DS 10 Processor: ??? 600 MHz (can

Bug#227904: Debian Sarge Installation report: failed on Alpha DS 10

2004-01-15 Thread Steve Langasek
Hi Szymon, On Thu, Jan 15, 2004 at 03:58:47PM +0100, Szymon Juraszczyk wrote: Debian-installer-version: http://gluck.debian.org/cdimage/testing/netinst/alpha/20040114/sarge-alpha-businesscard.iso uname -a: N/A Date: 2004-01-15 Method: burned CD, booted with 'boot dqb0' Machine: Compaq