[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#381257: marked as done (EtchBeta3 attempted installation report)



Your message dated Wed, 08 Sep 2010 03:58:16 +0000
with message-id <E1OtBnc-0005GB-6k@ravel.debian.org>
and subject line Closing old installation report #381257
has caused the Debian Bug report #381257,
regarding EtchBeta3 attempted installation 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 owner@bugs.debian.org
immediately.)


-- 
381257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381257
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- Package: installation-reports

INSTALL REPORT

Debian-installer-version: <Fill in date and from where you got the image>
 | Netinstall.iso debian.org 8/1/06
uname -a: <The result of running uname -a on a shell prompt>

Date: <Date and time of the install>
 | Tuesday 8/1/06
Method: How did you install?  What did you boot off?  If network
      install, from where?  Proxied?
 | Using bootx, copied vmlinux and initrd from cd, tried several versions
of macos 8.1/6,9.1/2 with minimal extension, both bootx control panel and extension

Machine: <Description of machine (eg, IBM Thinkpad R32)>
 | tried both my old world macs, neither would boot
Processor: 603ev powerbook / G3 desktop
Memory:  80MB / 192MB
Root Device: <IDE?  SCSI?  Name of device?>
Root Size/partition table:  Feel free to paste the full partition
      table, with notes on which partitions are mounted where.
Output of lspci and lspci -n:

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:    [E]
Configure network HW:   [ ]
Config network:         [ ]
Detect CD:              [ ]
Load installer modules: [ ]
Detect hard drives:     [ ]
Partition hard drives:  [ ]
Create file systems:    [ ]
Mount partitions:       [ ]
Install base system:    [ ]
Install boot loader:    [ ]
Reboot:                 [ ]
Comments/Problems:

  | neither system displays tux/penguin.

  | the powerbook prints only the first line "Welcome to Linux ..."

  | the desktop gets just a little bit further, prints 2 short blocks of
  | (normal) diagnostic, then also hang - last line printed is
  | "MMU:exit"

<Description of the install, in prose, and any thoughts, comments
      and ideas you had during the initial install.>
 
  | Very frustrating. i tried to read the updated installation guides, and
  |  got more frustrated.

  | ideas : since i have sarge going on both machines,
  |  what alternatives may i boot the installer ? neither machine
  |  has a working floppy, both dead a long time ago. however powerbook
  |  can boot "virtual floppy" ie RAM DISK. but perhaps other ways
  | 
  |  can i make a partition with /boot and load it with quik ?
  | 
  |  there is discussion in appendix D at end of install guide about
  |  doing a manual install from a working 'nix system, don't know
  |  how out of date the directions are though ...
  |
  | more ideas: is any of that relevant ? if there is something wrong
  | in the kernel or rd setups ? is it possible to install using the sarge
  | installer &/or kernel but using the etch cd for system files ?
  
  |
  |  i can always do the upgrade from sarge routine, although there are
  |  technical barriers, i would rather see this work.

Install logs and other status info is available in /var/log/debian-installer/.
Once you have filled out this report, mail it to submit@bugs.debian.org.




--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
  Installer.
- indications in the installation report give the feeling that
  the reported problem waslying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful


The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.



--- End Message ---

Reply to: