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

Bug#692437: marked as done (installation report)

Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id <201308311253.30231.holger@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #692437,
regarding 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.)


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

Boot method: <How did you boot the installer? CD? floppy? network?>	USB
Image version: <Full URL to image you downloaded is best>		http://cdimage.debian.org/cdimage/wheezy_di_beta3/amd64/iso-cd/debian-wheezy-DI-b3-amd64-netinst.iso
Date: <Date and time of the install>					Nov 04, 2012

Machine: <Description of machine (eg, IBM Thinkpad R32)>		Assembled Machine with ASUS mother board
Processor:								AMP Sempron 1GHz
Memory:									1GB
Partitions: <df -Tl will do; the raw partition table is preferred>	500GB HDD with 160GB partitioned for root /

Filesystem                                             Type     1K-blocks     Used Available Use% Mounted on
rootfs                                                 rootfs   163199520  5997792 148911388   4% /
udev                                                   devtmpfs     10240        0     10240   0% /dev
tmpfs                                                  tmpfs        89536      628     88908   1% /run
/dev/disk/by-uuid/f496b538-7099-45bc-8cf7-956acdf19ee9 ext4     163199520  5997792 148911388   4% /
tmpfs                                                  tmpfs         5120        0      5120   0% /run/lock
tmpfs                                                  tmpfs       222420       88    222332   1% /run/shm
/dev/sda5                                              fuseblk   46829440 10345948  36483492  23% /media/KRISHNA
/dev/sda7                                              fuseblk   50050472 14111480  35938992  29% /media/KRISHNA_
/dev/sda9                                              fuseblk   75152036 41163364  33988672  55% /media/KRISHNA__
/dev/sda8                                              fuseblk  150328204 32220356 118107848  22% /media/KRISHNA___

Output of lspci -knn (or lspci -nn):

root@gml:~# lspci -knn
00:00.0 RAM memory [0500]: NVIDIA Corporation MCP61 Memory Controller [10de:03ea] (rev a1)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
00:01.0 ISA bridge [0601]: NVIDIA Corporation MCP61 LPC Bridge [10de:03e0] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
00:01.1 SMBus [0c05]: NVIDIA Corporation MCP61 SMBus [10de:03eb] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
        Kernel driver in use: nForce2_smbus
00:01.2 RAM memory [0500]: NVIDIA Corporation MCP61 Memory Controller [10de:03f5] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
00:02.0 USB controller [0c03]: NVIDIA Corporation MCP61 USB 1.1 Controller [10de:03f1] (rev a3)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
        Kernel driver in use: ohci_hcd
00:02.1 USB controller [0c03]: NVIDIA Corporation MCP61 USB 2.0 Controller [10de:03f2] (rev a3)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
        Kernel driver in use: ehci_hcd
00:04.0 PCI bridge [0604]: NVIDIA Corporation MCP61 PCI bridge [10de:03f3] (rev a1)
00:05.0 Audio device [0403]: NVIDIA Corporation MCP61 High Definition Audio [10de:03f0] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8290]
        Kernel driver in use: snd_hda_intel
00:06.0 IDE interface [0101]: NVIDIA Corporation MCP61 IDE [10de:03ec] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
        Kernel driver in use: pata_amd
00:07.0 Bridge [0680]: NVIDIA Corporation MCP61 Ethernet [10de:03ef] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
        Kernel driver in use: forcedeth
00:08.0 IDE interface [0101]: NVIDIA Corporation MCP61 SATA Controller [10de:03f6] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
        Kernel driver in use: sata_nv
00:09.0 PCI bridge [0604]: NVIDIA Corporation MCP61 PCI Express bridge [10de:03e8] (rev a2)
        Kernel driver in use: pcieport
00:0b.0 PCI bridge [0604]: NVIDIA Corporation MCP61 PCI Express bridge [10de:03e9] (rev a2)
        Kernel driver in use: pcieport
00:0c.0 PCI bridge [0604]: NVIDIA Corporation MCP61 PCI Express bridge [10de:03e9] (rev a2)
        Kernel driver in use: pcieport
00:0d.0 VGA compatible controller [0300]: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
        Kernel driver in use: nouveau
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103]
        Kernel driver in use: k8temp

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

Initial boot:           [O]
Detect network card:    [O]
Configure network:      [O]
Detect CD:              [ ]-NO CD-drive in the system
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [O]-Why should you erase the old system?  It took nearly 6 hours to erase 160GB.  Is there any way to avoid it?
Install base system:    [O]
Clock/timezone setup:   [O]
User/password setup:    [O]
Install tasks:          [O]
Install boot loader:    [O]
Overall install:        [O]

Comments/Problems:

 <Description of the install, in prose, and any thoughts, comments
      and ideas you had during the initial install.>

I had to do the installation twice as the first install went in to the USB stick.
Some indication to user that may avoid such a mistake would be better.

There should be one selection for root partition and it should be confirmed.
Rest of the task should happen automatically.

I had read somewhere that the default desktop environment is xfce.  It turned out to be gnome.  Is is intentional?


begin:vcard
fn:Krishna Murthy TN
n:Murthy TN;Krishna
org:Global Multimedia Priavate Limited
adr:5th Phase, JP Nagar;;204, CLOCK House, Nanjundeswara Layout;Bangalore;Karnataka;560078;India
email;internet:krishna@globalmultimedia.in
tel;work:+91-80-26592051
tel;cell:+91-9341235426
url:www.globalmultimedia.in
version:2.1
end:vcard

--- End Message ---
--- Begin Message --- 
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: