Your message dated Mon, 4 Apr 2016 15:15:38 +0200
with message-id <20160404151538.3a6c8dd2@a68n.lokal>
and subject line no need to keep this report open
has caused the Debian Bug report #755230,
regarding 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 ow...@bugs.debian.org
immediately.)
--
755230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Boot method: Hard disk
Image version: an ISO image. I still have it, if you can tell me how to
extract its identity.
Date: 10 July 2014
Machine: Dell tower. 5 years old, at least
Processor: Intel
Memory: 512 MB
Partitions:
Filesystem Type 1K-blocks
Used Available Use% Mounted on
rootfs rootfs 48060296
3813692 41805236 9% /
udev devtmpfs 10240
0 10240 0% /dev
tmpfs tmpfs 51268
640 50628 2% /run
/dev/disk/by-uuid/910ebbba-e8db-45c2-95f1-6d4f9805b7d4 ext3 48060296
3813692 41805236 9% /
tmpfs tmpfs 5120
0 5120 0% /run/lock
tmpfs tmpfs 493080
224 492856 1% /run/shm
/dev/sda3 ext3 103812344
13443604 85095348 14% /home
/dev/sdb1 vfat 1956224
1226112 730112 63% /media/usb0
Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM
Controller/Host-Hub Interface [8086:2570] (rev 02)
Subsystem: Dell Device [1028:01d5]
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated
Graphics Controller [8086:2572] (rev 02)
Subsystem: Dell Device [1028:01d5]
Kernel driver in use: i915
00:06.0 System peripheral [0880]: Intel Corporation 82865G/PE/P Processor to
I/O Memory Interface [8086:2576] (rev 02)
00:1d.0 USB controller [0c03]: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #1 [8086:24d2] (rev 02)
Subsystem: Dell Device [1028:01d5]
Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #2 [8086:24d4] (rev 02)
Subsystem: Dell Device [1028:01d5]
Kernel driver in use: uhci_hcd
00:1d.3 USB controller [0c03]: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #4 [8086:24de] (rev 02)
Subsystem: Dell Device [1028:01d5]
Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2
EHCI Controller [8086:24dd] (rev 02)
Subsystem: Dell Device [1028:01d5]
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev
c2)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC
Interface Bridge [8086:24d0] (rev 02)
00:1f.1 IDE interface [0101]: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE
Controller [8086:24db] (rev 02)
Subsystem: Dell Device [1028:01d5]
Kernel driver in use: ata_piix
00:1f.3 SMBus [0c05]: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus
Controller [8086:24d3] (rev 02)
Subsystem: Dell Device [1028:01d5]
Kernel driver in use: i801_smbus
00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801EB/ER
(ICH5/ICH5R) AC'97 Audio Controller [8086:24d5] (rev 02)
Subsystem: Dell Device [1028:01d5]
Kernel driver in use: snd_intel8x0
01:01.0 Communication controller [0780]: Conexant Systems, Inc. HSF 56k
Data/Fax Modem [14f1:2f20]
Subsystem: Conexant Systems, Inc. Dimension 3000 [14f1:200f]
01:08.0 Ethernet controller [0200]: Intel Corporation 82562EZ 10/100 Ethernet
Controller [8086:1050] (rev 02)
Subsystem: Dell Device [1028:01d5]
Kernel driver in use: e100
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]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system: [O]
Clock/timezone setup: [O]
User/password setup: [O]
Install tasks: [O]
Install boot loader: [O]
Overall install: [O]
Comments/Problems:
Because my machine will boot from a Flash Ram Stick (henceforth FRS) when I'm
booting Puppy Linux, I
wanted to go that way. The doc says your new ISO image will boot from either
DVD, CD, or FRS. But, it
would not actually boot. I presume that its a problem with the elderly BIOS.
So, instead, I used Puppy to repartition the HD and wrote the kernel and initrd
there (following guidance
in the doc on what was needed for the installer to boot). I used Puppy's
command-line Grub. However,
when I was telling it where the kernel and initrd were, it complained.
The Grub doc says that the command-line version is just a simulation, so
inferior. Thus, I asked the
command-line to write Grub into the MBR. Then I booted successfully from there.
>From there, the installer ran without problems.
I will add one subsequent problem: When I ran apt-get, it could not find the
image, expecting it to be
on DVD, but I was able to use the sym-link in /media to point to the FRS, after
which it seemed happy
and ran to completion.
A note in the doc would be helpful about /media: how it duplicates some of the
funtion of /mnt
I just had to guess what was going on.
Of course, I will now be tuning up things, so will run into many small bugs,
but the big problem is
solved.
I must add that the place in the doc where it says how to report installation
needs more info. It offers
no alternative to setting up mail on the target box in sect. A.4
(https://www.debian.org/releases/stable/i386/apas04.html.en)
Please put a pointer to the section I used for this: Sect 5.4.7
Andrew
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Your feedback is appreciated, although it lacks a speaking message-subject.
You write, you were able to resolve the problem yourself and it doesn't really
seem to be
a problem in Debian, but one with the BIOS of your computer, that makes the
installer-image not bootable from USB.
So I think it is safe to close this issue.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlcCaPoACgkQ5+rBHyUt5wsXYACeImVuLgyzSpDGRP2dIeq4clyG
XNMAoK4dHQD+V/5wbGMi8h2Z3rOOwbe0
=Sjz6
-----END PGP SIGNATURE-----
--- End Message ---
