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

Bug#701493: marked as done (installation-reports: successful installation on an Acer TravelMate P253, but fstab had to be fixed)

Your message dated Sun, 1 Sep 2013 19:23:42 +0200
with message-id <201309011924.00219.holger@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #701493,
regarding installation-reports: successful installation on an Acer TravelMate P253, but fstab had to be fixed
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.)


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

Hello,
I would like to report a successful (well, let's say almost successful)
installation, with a single little issue in the auto-generated /etc/fstab
file. 
The issue may be easily fixed by hand, but, still, I think it's caused
by a bug: that's why I am reporting it.

Thanks a lot for the great job in developing debian-installer: it's
getting more and more practical to use. Well done!   :-)

See below for the details.


-- Package-specific info:

Boot method: USB stick
Image version: http://cdimage.debian.org/cdimage/daily-builds/sid_d-i/current/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: 2013-02-23 10:13
MD5SUM of image: a344ded2e4a1895a28b87acda348098b  debian-testing-amd64-netinst.iso

Machine: Acer TravelMate P253-E-B9602G32Mnks (NX.V7XET.004)
Partitions: some partitions and LVM volumes inside /dev/sda, created through
            manual partitioning; I think the details are not especially
            relevant


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:              [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:    [O]
Detect hard drives:     [O]
Partition hard drives:  [O]
Install base system:    [O]
Install tasks:          [ ]
Install boot loader:    [O]
Overall install:        [O]

Comments/Problems:

The machine is a Acer TravelMate P253-E-B9602G32Mnks (NX.V7XET.004)
laptop. The output of "lspci -n" and of "lspci -vvv" are attached.

Overall, the installation went fine.

I downloaded the above mentioned debian-installer image today and
wrote it to a USB stick with "dd". After configuring the BIOS so that
the laptop can boot from USB HDD or USB CDROM, I started the
installation process.
The Ethernet adapter (Broadcom Corporation NetLink BCM57785 Gigabit
Ethernet PCIe) was correctly detected and used as primary network
interface. It also seems to work fine after booting the installed
system (without any non-free drivers or firmware blobs!).
I still have to test the wireless network adapter (Atheros
Communications Inc. AR9485 Wireless Network Adapter), but it was
correctly detected during the installation and offered as a possible
alternative, when choosing the primary network interface. And the ath9k
kernel module is automatically loaded on the installed system
(the wireless adapter should work without any non-free drivers or
firmware blobs, as far as I know!).

Please note that I worked around the bug in the GRUB installation,
as currently suggested in the errata page:
http://www.debian.org/devel/debian-installer/errata
In other words, I answered "No" when asked to install GRUB to the MBR,
and then explicitly specified "/dev/sda" as device for boot loader
installation.
I don't know what would have happened, if I had not followed this
strategy.

After booting the installed system, I noticed that the /etc/fstab
needed to be fixed by hand.
The last four lines looked like:

  /dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
  /dev/sr1        /media/cdrom1   udf,iso9660 user,noauto     0       0
  /dev/sdb1       /media/usb0     auto    rw,user,noauto  0       0
  /dev/sdb2       /media/usb1     auto    rw,user,noauto  0       0

The last three lines should not be present: only the first one (of the
above mentioned lines) is correct, since the laptop has only one
DVD drive and there is no /dev/sdb (after removing the USB stick...).
I manually deleted the last three lines with a text editor.
I also had to remove the extraneous mount points:

  # ls -F /media
  cdrom@  cdrom0/  cdrom1/  usb@  usb0/  usb1/
  # rmdir /media/cdrom1 /media/usb?
  # rm /media/usb
  # ls -F /media
  cdrom@  cdrom0/

I don't know exactly why the fstab file was created that way, but
it really looks wrong (even though easy to fix).

Please investigate and fix this little bug.
Thanks for your time!

00:00.0 0600: 8086:0104 (rev 09)
00:02.0 0300: 8086:0106 (rev 09)
00:16.0 0780: 8086:1e3a (rev 04)
00:1a.0 0c03: 8086:1e2d (rev 04)
00:1b.0 0403: 8086:1e20 (rev 04)
00:1c.0 0604: 8086:1e10 (rev c4)
00:1c.1 0604: 8086:1e12 (rev c4)
00:1d.0 0c03: 8086:1e26 (rev 04)
00:1f.0 0601: 8086:1e5e (rev 04)
00:1f.2 0106: 8086:1e03 (rev 04)
00:1f.3 0c05: 8086:1e22 (rev 04)
02:00.0 0200: 14e4:16b5 (rev 10)
02:00.1 0805: 14e4:16bc (rev 10)
02:00.2 0880: 14e4:16be (rev 10)
02:00.3 0880: 14e4:16bf (rev 10)
03:00.0 0280: 168c:0032 (rev 01)

Attachment: lspci-vvv.out.gz
Description: GNU Zip compressed data


--- 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: