Your message dated Wed, 11 Jun 2008 13:01:43 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#485508: SV: SV: Bug#485508: Bug report
has caused the Debian Bug report #485508,
regarding Bug report
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
485508: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485508
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: installation-reports
Boot method: CD-rom
Image version:
http://cdimage.debian.org/debian-cd/4.0_r3/i386/bt-cd/debian-40r3-i386-CD-1.
iso.torrent
Date: 2008-06-10
Machine: No-brand homebuilt Pentium-2 system, IBM Deskstar 2gb HD, Unknown
50gb HD, Memorex DVDMAXX DVD-rom
Processor: Pentium 2
Memory: 128mb
Partitions: N/A
Utskrift från lspci -nn och lspci -vnn:
Base System Installation Checklist:
[O] = OK, [E] = Fel (förklara nedan), [ ] = provade det inte
Initial boot: [E]
Detect network card: [ ]
Configure network: [ ]
Detect CD: [O]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Install base system: [ ]
Clock/timezone setup: [ ]
User/password setup: [ ]
Install tasks: [ ]
Install boot loader: [ ]
Overall install: [ ]
Comments/Problems:
The system hung when I tried to boot the installation CD-rom. The prompt
ISOLINUX 3.31 Debian-2007-02-14 appears, but then nothing happends.
I tried burning onto two different CD-rom brands but exactly the same error
occured.
No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 270.0.0/1490 - Release Date: 2008-06-08
17:32
--- End Message ---
--- Begin Message ---
On Wednesday 11 June 2008, Patrick Fabrizius wrote:
> As I stated in my bug report, the system hung a lot earlier than
> "initrd", so I did not consider it to be that same problem. Perhaps it
> is, I have however already solved the problem by instead using another
> motherboard so I will not test the alternative image this time, but it
> helps to know its there.
My suggestion did not really have anything to do with the initrd, but with
the bootloader (isolinux). The actual symptoms (what messages are/are not
shown) may vary a bit per system.
Because the problem was very early, the most likely problem was with the
bootloader and I wanted to at least rule that out as the cause.
However, as you've worked around the issue and it seems we cannot expect
any further info on the issue, I'm closing your report.
Good luck installing with the other motherboard.
Cheers,
FJP
--- End Message ---
