Bug#755848: Patch in preseed src code

[Eric Desrochers]

This patch in preseed source code addresses the situation.

This is the patch we pushed in Ubuntu[1] releases.

Thanks to cyphermox for the joint works (co-authorship).

[1] - https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202

Eric
>From 742808a23407772c516628daecab29b4cbd12b22 Mon Sep 17 00:00:00 2001
From: Eric Desrochers 
Date: Thu, 6 Oct 2016 00:01:59 -0400
Subject: [PATCH] Fix for netcfg/hostname,if set, to take precedence

 Modify debian/network-preseed.postinst
---
 debian/network-preseed.postinst | 15 +++
 1 file changed, 15 insertions(+)

diff --git a/debian/network-preseed.postinst b/debian/network-preseed.postinst
index bf651f4..6102182 100755
--- a/debian/network-preseed.postinst
+++ b/debian/network-preseed.postinst
@@ -14,4 +14,19 @@ if [ -n "$dhcp_url" ]; then
 	preseed_location "$dhcp_url"
 fi
 preseed preseed/url
+
+CURRENT_HOSTNAME=`/bin/hostname`
+if db_get netcfg/hostname && [ "$RET" ]; then
+if ! echo "$RET" | grep -q 'debian'; then
+		# default hostname is debian; if that's what we have in the
+		# netcfg/hostname template, then netcfg will already have
+		# done the right thing.
+		NETCFG_HOSTNAME="$RET"
+		/bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /etc/hostname
+		/bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /etc/hosts
+		/bin/hostname "$NETCFG_HOSTNAME"
+		/usr/bin/logger -t netcfg "d-i netcfg/hostname $NETCFG_HOSTNAME took precedence"
+	fi
+fi
+
 preseed_command preseed/early_command
-- 
2.7.4

Bug#755848: preseed d-i netcfg/hostname does not set hostname

[Eric Desrochers]

Disregard the proposed patch above 
"0001-Fix-netcfg-hostname-that-does-not-set-hostname.patch"

I'll be working on a new one which will include some improvement.

Stay tuned .

Bug#755848: Patch

[Eric Desrochers]

This patch include a script under finish-install.d/56netcfg-hostname that 
detect if netcfg/hostname is set in preseed file and override the hostname at 
the end of the installation. If not set then it keeps the hostname as is.
>From 53522b8129f9542a1d7c9a21344d8b8b2732c9ce Mon Sep 17 00:00:00 2001
From: Eric Desrochers 
Date: Tue, 20 Sep 2016 20:02:16 -0400
Subject: [PATCH] Fix netcfg/hostname that does not set hostname

---
 finish-install.d/56netcfg-hostname | 17 +
 1 file changed, 17 insertions(+)
 create mode 100755 finish-install.d/56netcfg-hostname

diff --git a/finish-install.d/56netcfg-hostname b/finish-install.d/56netcfg-hostname
new file mode 100755
index 000..2256c5b
--- /dev/null
+++ b/finish-install.d/56netcfg-hostname
@@ -0,0 +1,17 @@
+#! /bin/sh
+set -e
+
+PROGNAME=$(basename $0)
+CURRENT_HOSTNAME=`/bin/hostname`
+NETCFG_HOSTNAME=`/bin/debconf-get netcfg/hostname`
+
+# Override hostname, if "netcfg/hostname" is set in preseed file. #
+if [ -n "$NETCFG_HOSTNAME" ]; then
+/bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /target/etc/hostname
+/bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /target/etc/hosts
+/usr/bin/logger "$PROGNAME: d-i netcfg/hostname $NETCFG_HOSTNAME took precedence"
+
+# Keep hostname as is, if "netcfg/hostname" is not set in preseed file. #
+else
+exit 0
+fi
-- 
2.5.0

Bug#759657: console-setup w/ systemd forgets font setting

[Eric Cooper]

On Sat, Dec 12, 2015 at 01:52:29PM +, Brian Potkin wrote:
> On Thu 10 Dec 2015 at 03:47:24 +0100, Michael Biebl wrote:
>
> > Am 10.12.2015 um 00:55 schrieb Samuel Thibault:
> > > Eric Cooper, on Thu 19 Nov 2015 13:31:57 -0500, wrote:
> > >> While booting, it looks like the font switches from VGA to Terminus
> > >> during the boot messages.  But then the screen is cleared and the
> > >> getty login prompts are back in VGA.  If I run "setupcon" manually, it
> > >> changes to Terminus.
> > >
> > > So it seems like something is resetting the font back to VGA (and it's
> > > not console-setup, which loads Terminus).
> > >
> > > systemd people, do you have any idea?  This has started happening with
> > > the switch to systemd.
> >
> > From a cursory look, it doesn't seem to be caused by systemd itself but
> > it's a race condition and the way console-setup works. And the timing
> > under systemd might simply the different then under sysvinit (it's
> > usually faster).
> >
> > When Karsten added the dependency on udev settle, it probably just
> > changed the timing (by delaying it a little) so made it less likely to
> > happen.
> >
> > It might be, that loading the KMS module resets the font.
> > So maybe console-setup should run when hardware shows up.
> > This is a shot in the dark, but can you try and create the following
> > udev rules file:
> >
> > $ cat /etc/udev/rules.d/90-setupcon.rules
> > ACTION=="add", SUBSYSTEM=="vtconsole", KERNEL=="vtcon*",
> > RUN+="/bin/setupcon"
>
> This file does it for me up to now. After about 10 reboots the font is
> not being reset back to VGA.

Yes, this solves the problem for my system too.  Please consider
adding this to the console-setup package.

--
Eric Cooper e c c @ c m u . e d u

Bug#759657: console-setup w/ systemd forgets font setting

[Eric Cooper]

Package: console-setup
Version: 1.134
Followup-For: Bug #759657

I see the same problem on every reboot.

While booting, it looks like the font switches from VGA to Terminus
during the boot messages.  But then the screen is cleared and the
getty login prompts are back in VGA.  If I run "setupcon" manually, it
changes to Terminus.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages console-setup depends on:
ii  console-setup-linux 1.134
ii  debconf 1.5.58
ii  keyboard-configuration  1.134
ii  xkb-data2.16-1

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales   2.19-22
ii  lsb-base  9.20150917

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.58
ii  initscripts 2.88dsf-59.2
ii  liblocale-gettext-perl  1.07-1

Versions of packages console-setup-linux depends on:
ii  kbd 1.15.5-2
ii  keyboard-configuration  1.134

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
pn  console-common  
pn  console-data
pn  console-tools   
ii  kbd 1.15.5-2

-- debconf information:
  keyboard-configuration/modelcode: ibm_spacesaver
  keyboard-configuration/store_defaults_in_debconf_db: true
* console-setup/charmap47: UTF-8
  console-setup/framebuffer_only:
  keyboard-configuration/xkb-keymap: us
  keyboard-configuration/layoutcode: us
* console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
  keyboard-configuration/toggle: No toggling
  console-setup/guess_font:
  console-setup/fontsize-text47: 8x16
  keyboard-configuration/optionscode: ctrl:nocaps
* console-setup/fontsize-fb47: 8x16
  keyboard-configuration/unsupported_layout: true
* keyboard-configuration/compose: No compose key
* console-setup/fontface47: Terminus
  keyboard-configuration/variantcode:
  console-setup/use_system_font:
  console-setup/fontsize: 8x16
* keyboard-configuration/variant: English (US)
* keyboard-configuration/unsupported_config_options: true
  keyboard-configuration/other:
  keyboard-configuration/switch: No temporary switch
  keyboard-configuration/layout:
  debian-installer/console-setup-udeb/title:
  console-setup/store_defaults_in_debconf_db: true
  console-setup/codesetcode: Lat15
  keyboard-configuration/unsupported_config_layout: true
  keyboard-configuration/unsupported_options: true
* keyboard-configuration/model: IBM Space Saver
* keyboard-configuration/altgr: The default for the keyboard layout
* keyboard-configuration/ctrl_alt_bksp: false

Bug#803115: flash-kernel: please provide an option to disable creation of backup files

[Eric Cooper]

Package: flash-kernel
Version: 3.48
Followup-For: Bug #803115

Here's a patch, tested on my Seagate Dockstar.

Default behavior:
$ sudo flash-kernel
DTB: kirkwood-dockstar.dtb
Installing kirkwood-dockstar.dtb into 
/boot/dtbs/4.2.0-0.bpo.1-kirkwood/kirkwood-dockstar.dtb
Taking backup of kirkwood-dockstar.dtb.
Installing new kirkwood-dockstar.dtb.
flash-kernel: installing version 4.2.0-0.bpo.1-kirkwood
flash-kernel: appending 
/usr/lib/linux-image-4.2.0-0.bpo.1-kirkwood/kirkwood-dockstar.dtb to kernel
Generating kernel u-boot image... done.
Taking backup of uImage.
Installing new uImage.
Generating initramfs u-boot image... done.
Taking backup of uInitrd.
Installing new uInitrd.
Taking backup of dtb.
Installing new dtb.

New behavior with NO_BACKUP_FILES=true set in /etc/default/flash-kernel:

$ sudo flash-kernel
DTB: kirkwood-dockstar.dtb
Installing kirkwood-dockstar.dtb into 
/boot/dtbs/4.2.0-0.bpo.1-kirkwood/kirkwood-dockstar.dtb
Skipping backup of kirkwood-dockstar.dtb.
Installing new kirkwood-dockstar.dtb.
flash-kernel: installing version 4.2.0-0.bpo.1-kirkwood
flash-kernel: appending 
/usr/lib/linux-image-4.2.0-0.bpo.1-kirkwood/kirkwood-dockstar.dtb to kernel
Generating kernel u-boot image... done.
Skipping backup of uImage.
Installing new uImage.
Generating initramfs u-boot image... done.
Skipping backup of uInitrd.
Installing new uInitrd.
Skipping backup of dtb.
Installing new dtb.
>From e111d107a0e9453d0af0eb0ed4708a1aea1f901e Mon Sep 17 00:00:00 2001
From: Eric Cooper 
Date: Sat, 7 Nov 2015 13:15:39 -0500
Subject: [PATCH] Add NO_BACKUP_FILES option to /etc/default/flash-kernel.

If set, no backups of kernel, initrd, and dtb files will be created,
to save space on systems with limited storage.

Signed-off-by: Eric Cooper 
---
 README|  9 ++---
 functions | 18 --
 2 files changed, 22 insertions(+), 5 deletions(-)

diff --git a/README b/README
index 4ca5a22..bc7493c 100644
--- a/README
+++ b/README
@@ -191,9 +191,12 @@ Configuration files currently supported:
   script snippets. See "Adding U-Boot Commands for Pre-Boot Execution"
   below for more details.
 
-* /etc/default/flash-kernel currently contains a single variable,
-  LINUX_KERNEL_CMDLINE, which should be used by bootscripts to set kernel
-  options.
+* /etc/default/flash-kernel currently contains the following variables:
+- LINUX_KERNEL_CMDLINE, which should be used by bootscripts to set kernel
+  options.
+- NO_BACKUP_FILES, which if set to "true" or "yes" will prevent
+  flash-kernel from creating backup versions of kernel, initrd,
+  and dtb files.
 
 
 Adding U-Boot Commands for Pre-Boot Execution
diff --git a/functions b/functions
index 35d872b..9bbef2c 100644
--- a/functions
+++ b/functions
@@ -404,13 +404,27 @@ mkimage_multi() {
 	echo "done." >&2
 }
 
+# Return a nonempty string *unless* NO_BACKUP_FILES is set.
+get_backup_preference() {
+. /etc/default/flash-kernel
+	case $(echo "$NO_BACKUP_FILES" | tr '[:upper:]' '[:lower:]') in
+	true|yes|1) ;;
+	*) echo yes ;;
+	esac
+}
+
 backup_and_install() {
 	local source="$1"
 	local dest="$2"
+	local do_backups=$(get_backup_preference)
 
 	if [ -e "$dest" ]; then
-		echo "Taking backup of $(basename "$dest")." >&2
-		mv "$dest" "$dest.bak"
+		if [ -n "$do_backups" ]; then
+			echo "Taking backup of $(basename "$dest")." >&2
+			mv "$dest" "$dest.bak"
+		else
+			echo "Skipping backup of $(basename "$dest")." >&2
+		fi
 	fi
 	echo "Installing new $(basename "$dest")." >&2
 	mv "$source" "$dest"
-- 
2.6.2

Bug#804359: flash-kernel: Little-endianness is tested incorrectly for NSLU2

[Eric Cooper]

Package: flash-kernel
Version: 3.48
Severity: normal
Tags: patch

The nslu2_swap() function incorrectly tests $little_endian and will
always think it is true.

Untested patch attached since I don't have a slug.
>From e719eabe8f4640fb192dae4ce44235653ce8e803 Mon Sep 17 00:00:00 2001
From: Eric Cooper 
Date: Sat, 7 Nov 2015 12:58:04 -0500
Subject: [PATCH] Test $little_endian correctly in nslu2_swap()

Signed-off-by: Eric Cooper 
---
 functions | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/functions b/functions
index ea69df7..35d872b 100644
--- a/functions
+++ b/functions
@@ -425,7 +425,7 @@ sercomm_header() {
 }
 
 nslu2_swap() {
-	if [ "$little_endian" ]; then
+	if [ "$little_endian" -eq 1 ]; then
 		devio "<<$1" "xp $,4"
 	else
 		cat "$1"
-- 
2.6.2

Bug#803115: flash-kernel: please provide an option to disable creation of backup files

[Eric Cooper]

Package: flash-kernel
Version: 3.46
Severity: wishlist

I'd like an option (configurable in /etc/default/flash-kernel ideally)
to prevent flash-kernel from creating .bak files for uImage, uInitrd,
and dtb, in order to same space on my system.  I'm willing to live
dangerously and keep a serial and JTAG cable handy :-)

Bug#765406: ping?

[Eric Dorland]

Any chance this can get fixed before the release?

-- 
Eric Dorland 
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93


signature.asc
Description: Digital signature

Bug#731859: debootstrap: variant=fakechroot fails

[Eric Keller]

Hi josch,

I am currently encountering the same problem with version: debootstrap
1.0.40~ubuntu0.7 using wheezy instead of sid and without using fakeroot
fakechroot, but directly using sudo.

the strange thing is that this exact same error comes when debootstrap is
called from a script. But calling the same debootstrap command in a
terminal finishes without any error.

did you realize further investigation on this bug?

Best Regards
--
Eric Keller

On Tue, 10 Dec 2013 15:48:33 +0100 Johannes Schauer 
wrote:
> Package: debootstrap
> Version: 1.0.55
> Severity: normal
>
> Running debootstrap under Debian Sid yields:
>
> $ fakeroot fakechroot debootstrap --verbose --variant=fakechroot sid
debian-sid
> [...]
> I: Installing core packages...
> W: Failure trying to run: chroot /home/josch/debian-sid dpkg
--force-depends --install /var/cache/apt/archives/base-files_7.2_amd64.deb
/var/cache/apt/archives/base-passwd_3.5.28_amd64.deb
> W: See /home/josch/debian-sid/debootstrap/debootstrap.log for details
(possibly the package archive is at fault)
>
> And the last lines of the log say:
>
> dpkg: warning: parsing file '/var/lib/dpkg/status' near line 5 package
'dpkg':
>  missing description
> dpkg: warning: parsing file '/var/lib/dpkg/status' near line 5 package
'dpkg':
>  missing architecture
> dpkg: regarding .../base-files_7.2_amd64.deb containing base-files,
pre-dependency problem:
>  base-files pre-depends on awk
>   awk is not installed.
>
> dpkg: warning: ignoring pre-dependency problem!
> Selecting previously unselected package base-files.
> (Reading database ... 0 files and directories currently installed.)
> Preparing to unpack .../base-files_7.2_amd64.deb ...
> Unpacking base-files (7.2) ...
> rm: cannot remove '/var/lib/dpkg/tmp.ci': Directory not empty
> dpkg: error while cleaning up:
>  subprocess rm cleanup returned error exit status 1
> rm: cannot remove '/var/lib/dpkg/tmp.ci': Directory not empty
> dpkg: error processing archive
/var/cache/apt/archives/base-passwd_3.5.28_amd64.deb (--install):
>  subprocess rm cleanup returned error exit status 1
> dpkg: base-files: dependency problems, but configuring anyway as you
requested:
>  base-files depends on awk; however:
>   Package awk is not installed.
>
> chown: invalid user: 'root:root'
> dpkg: error processing package base-files (--install):
>  subprocess installed post-installation script returned error exit status
1
> Errors were encountered while processing:
>  /var/cache/apt/archives/base-passwd_3.5.28_amd64.deb
>  base-files
> Setting up base-files (7.2) ...

Bug#609201: [Pkg-utopia-maintainers] Bug#609201: Also affects installation from USB

[Eric Shattow]

On Wed, 15 Feb 2012 08:28:39 +0100 Michael Biebl  wrote:
> On 15.02.2012 05:25, scott wrote:
> >
> > I recently installed a weekly build from
> > http://cdimage.debian.org/cdimage/weekly-builds/ by booting from a USB
stick,
> > and was also affected by this bug.
> >
> > I assume this means that anyone doing a USB installation will also be
> > affected. This make the bug quite serious IMHO.
> >
>
> Imho, d-i shouldn't write fstab entries for USB sticks during
installation.
>
> d-i team: would it be possible/feasible to change this behaviour?
>

See previously closed / similar
bug #597223: udev: The First partition on USB flashdrives always attempts
to be mounted as ISOFS
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597223

Can same fix be applied to this new issue?

Bug#765406: [Pkg-gnupg-maint] Bug#765406: please add dependency on pinentry-gtk2

[Eric Dorland]

* Michael Biebl (bi...@debian.org) wrote:
> Am 26.10.2014 um 01:04 schrieb Eric Dorland:
> > * Michael Biebl (bi...@debian.org) wrote:
> >> Am 24.10.2014 um 06:39 schrieb Eric Dorland:
> >>> Hmmm, are you talking about gnome-keyring? It actually hijacks the
> >>> gpg-agent protocol and breaks some things (see http://b/760102). You
> >>> still need the pinentry program if you disable gnome-keyright AFAIK.
> >>
> >> Couldn't that warning message also include hints to install pinentry-gtk2?
> > 
> > It could but just installing it won't fix anything by itself, you need
> > to disable the agent functionality in gnome-keyring. Which some people
> > will do to work around the bug, and if they do it would be nice if
> > they had a graphical pinentry.
> 
> Sure. The message could say: "If you disable the gnome-keyring
> integration, make sure to install an alternative pinentry program like
> pinentry-gtk2"
> 
> Problem solved.

I mean not really problem solved, perhaps a slightly better
explanation. I still think it makes sense to install it pinentry-gtk2
with the gnome desktop task but I can live without if you object.

-- 
Eric Dorland 
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93


signature.asc
Description: Digital signature

Bug#765406: [Pkg-gnupg-maint] Bug#765406: please add dependency on pinentry-gtk2

[Eric Dorland]

* Michael Biebl (bi...@debian.org) wrote:
> Am 24.10.2014 um 06:39 schrieb Eric Dorland:
> > Hmmm, are you talking about gnome-keyring? It actually hijacks the
> > gpg-agent protocol and breaks some things (see http://b/760102). You
> > still need the pinentry program if you disable gnome-keyright AFAIK.
> 
> Couldn't that warning message also include hints to install pinentry-gtk2?

It could but just installing it won't fix anything by itself, you need
to disable the agent functionality in gnome-keyring. Which some people
will do to work around the bug, and if they do it would be nice if
they had a graphical pinentry.



-- 
Eric Dorland 
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93


signature.asc
Description: Digital signature

Bug#765406: [Pkg-gnupg-maint] Bug#765406: please add dependency on pinentry-gtk2

[Eric Dorland]

* Michael Biebl (bi...@debian.org) wrote:
> Am 23.10.2014 um 03:36 schrieb Eric Dorland:
> > Control: reassign -1 tasksel
> > Control: retitle -1 please add dependencies on pinentry
> > Control: tags -1 patch
> > 
> > Reassigning to tasksel as suggested and patch attached.
> > 
> > * Eric Dorland (e...@debian.org) wrote:
> >> Package: gnome
> >> Version: 1:3.8+8
> >> Severity: wishlist
> >>
> >> This came up at a DebConf discussion around gnupg2. Right now gnupg-agent
> >> (required by newer gnupg versions) needs a pinentry program (basically a
> >> program that prompts for a PIN or password). Right now it depends on
> >> pinentry-gtk2, which gives a good experience for users with a desktop
> >> environment but pulls in a lot of dependencies for a non-graphical system.
> >>
> >> So we would like to switch to pinentry-curses instead to lighten the
> >> dependency load, but we'd also not like to regress the experience for
> >> users of graphical desktops. So if it was added to the task package then
> >> those users would get the better experience and we could move the default
> >> depedency to pinentry-curses.
> >>
> >> I suspect Recommends would also be a strong enough dependency relationship
> >> for this purpose. Thanks for your consideration.
> 
> gnome-shell has a builtin gpg password prompter.
> So at least for GNOME, it's not necessary to install pinentry-gtk2.

Hmmm, are you talking about gnome-keyring? It actually hijacks the
gpg-agent protocol and breaks some things (see http://b/760102). You
still need the pinentry program if you disable gnome-keyright AFAIK.


-- 
Eric Dorland 
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93


signature.asc
Description: Digital signature

Re: [Pkg-gnupg-maint] Bug#764292: gnupg2: brings too many dependencies into standard task

[Eric Dorland]

* Steven Chamberlain (ste...@pyro.eu.org) wrote:
> On 14/10/14 20:18, Eric Dorland wrote:
> > Thanks for the report. We're working on this,
> 
> Okay thanks, although I notice you filed a bug only against "gnome":
> 
>   * Why only gnome?  If it is important to have a gtk2 dialog then
> shouldn't other desktops have it too?
> 
>   * Since this bug affects tasksel, why not also address it in tasksel,
> such as in task-desktop?

Yes good point, let me fix that. I suppose it should be:

task-gnome-desktop, task-xfce-desktop, task-lxde-desktop: recommend
pinentry-gtk2
task-kde-desktop: recommend pinentry-qt4
 
>   * Why only severity 'wishlist' if it is blocking a bug of IMHO higher
> severity?

From the perspective of tasksel, it's a feature request IMHO.

> > but I'm not sure I
> > understand the justification to make this a serious bug. Could you
> > elaborate?
> 
> OK, I've looked and could not find a reference to this in policy.  But I
> felt it was common sense, and policy shouldn't need to exist for such
> things:
> 
> A minimal no-desktop install should not include ~70 additional packages
> with ~30MB download size and taking ~100MB space, if they add no extra
> functionality for that use case.

I agree, it's a bug. I'm just not sure we should hold up the release.

> (Also curious, what will gnupg2 do if
> only pinentry-gtk2 is installed but no desktop is running?)

pinentry-gtk2 will fallback to curses if there's no DISPLAY.
 
> I'm not saying it's gnupg-agent's fault this situation occurred, but it
> is IMHO a serious enough problem affecting d-i/tasksel, to need to fix
> it before release?

But other than bringing in too many packages, does it break anything
else?

-- 
Eric Dorland 
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93


signature.asc
Description: Digital signature

Bug#681691: os-prober relies on grub-mount which fails silently on missing fuse module

[Eric Lavarde]

Hello again,

On 09/11/13 14:34, Eric Lavarde wrote:

i.e. we have multiple errors combined to make a big mess:
a. grub-mount relies on a fuse module which doesn't exist (by default).
b. it fails with an error message but a successful return code.
c. 50mounted-tests thinks that the command is successful (and hides
   the error message which could have been helpful).
Small correction: the fuse module does (of course, stupid me) exist per 
default, but points b and c remain valid, failure must be properly handled.


Thanks again,
Eric


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/527e3d88.9080...@lavar.de

Bug#681691: os-prober relies on grub-mount which fails silently on missing fuse module

[Eric Lavarde]

Package: os-prober
Version: 1.58
Followup-For: Bug #681691

Hello,

there was no reaction on this bug which actually makes my life miserable each
time there is a kernel update, because I need to mount all relevant partitions
by hand.

Anyway, I looked a bit more about it and found the following:

1. os-prober calls "/usr/lib/os-prober/newns /usr/bin/os-prober" which itself
   calls "/usr/lib/os-probes/50mounted-tests /dev/sda2" (for example).
2. 50mounted-tests relies itself on grub-mount to mount the partition.
3. The call to grub-mount looks as such:

mounted=
if type grub-mount >/dev/null 2>&1 && \
   type grub-probe >/dev/null 2>&1 && \
   grub-mount "$partition" "$tmpmnt" 2>/dev/null; then
mounted=1

4. Calling grub-mount gives then the following error:

# grub-mount /dev/sda2 /mnt
fuse: device not found, try 'modprobe fuse' first
# echo $?
0
# modprobe fuse
FATAL: Module fuse not found.

i.e. we have multiple errors combined to make a big mess:
a. grub-mount relies on a fuse module which doesn't exist (by default).
b. it fails with an error message but a successful return code.
c. 50mounted-tests thinks that the command is successful (and hides
   the error message which could have been helpful).

Conclusion, I think this bug should be duplicated, once to fix grub-mount
resp. grub-common package, once to fix os-prober (at least to improve error
handling, at best to stop using grub-mount). I'd be more than happy to
read your opinion.

Thanks, Eric

-- System Information:
Debian Release: 7.2
  APT prefers stable
  APT policy: (1000, 'stable'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.8.11+vdr2 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages os-prober depends on:
ii  libc6  2.17-93

os-prober recommends no packages.

os-prober suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131109133453.27897.78079.report...@hdvdr.lan

Bug#451535: lvm crypted full disk: not able to boot

[Streit Eric]

Hi,

I tried yesterday and today 5 or more  times to install wheezy on my
laptop with crypted lvm full disk: I could just not boot  the system
which hangs on: passphrase never recognised .

This laptop run "squeeze lvm crypted" witout problem as my other laptops
do (amd64 on this, and i386 on the others).

I tried different flavors of install disks:

net install, iso-1, dayly etc ... amd64 and i386 :(:(

I got never past the passphrase asking (and yes, I checked carefully my
passphrase).

There is also something strange with the firmware (network recognition):
I had to answer "no", but the firmwares were on a separate usb-stick:
with no as a answer, everything went ok.

best regards

Eric


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5051af32.5080...@gmail.com

Bug#684596: udhcpc avoid default.script dependency on net-tools

[Eric Cooper]

Package: udhcpc
Version: 1:1.20.0-6
Severity: normal
Tags: patch

If I remove net-tools from my system, udhcpc breaks because its
default.script relies on ifconfig and route, but udhcpc doesn't depend
on net-tools.

Since versions of these are built into busybox, the attached
quick-and-dirty patch just uses those.  A better approach might be to
use the "ip" command, either by depending on iproute2 or using the one
built into busybox.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages udhcpc depends on:
ii  busybox  1:1.20.0-6

udhcpc recommends no packages.

udhcpc suggests no packages.

-- Configuration Files:
/etc/udhcpc/default.script changed [not included]

-- no debconf information
--- /etc/udhcpc/default.script.orig	2012-04-11 15:04:56.0 -0400
+++ /etc/udhcpc/default.script	2012-08-11 11:56:13.0 -0400
@@ -11,15 +11,15 @@
 	[ -n "$broadcast" ] && BROADCAST="broadcast $broadcast"
 	[ -n "$subnet" ] && NETMASK="netmask $subnet"
 
-	/sbin/ifconfig $interface $ip $BROADCAST $NETMASK
+	/bin/busybox ifconfig $interface $ip $BROADCAST $NETMASK
 
 	if [ -n "$router" ]; then
 	echo "$0: Resetting default routes"
-	while /sbin/route del default gw 0.0.0.0 dev $interface; do :; done
+	while /bin/busybox route del default gw 0.0.0.0 dev $interface; do :; done
 
 	metric=0
 	for i in $router; do
-		/sbin/route add default gw $i dev $interface metric $metric
+		/bin/busybox route add default gw $i dev $interface metric $metric
 		metric=$(($metric + 1))
 	done
 	fi
@@ -45,7 +45,7 @@
 	if [ -x /sbin/resolvconf ]; then
 	resolvconf -d "${interface}.udhcpc"
 	fi
-	/sbin/ifconfig $interface 0.0.0.0
+	/bin/busybox ifconfig $interface 0.0.0.0
 	;;
 
 leasefail)

Bug#681691: os-prober and linux-boot-prober fail to mount alternate partition

[Eric Lavarde]

Package: os-prober
Version: 1.54
Severity: important

Hello,

very recently, I noticed that update-grub didn't discover Linux Debian
installed on other partitions (/dev/sda2) than the current one (/dev/sda1),
and I brought the issue down to os-prober which somehow fails to mount
/dev/sda2 in order to properly discover it:

root@hdvdr:/usr/src# os-prober
umount: /var/lib/os-prober/mount: not mounted
root@hdvdr:/usr/src# mount /dev/sda2 /mnt
root@hdvdr:/usr/src# os-prober
/dev/sda2:Debian GNU/Linux (wheezy/sid):Debian:linux
root@hdvdr:/usr/src# linux-boot-prober /dev/sda2 
/dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 
3.4-trunk-amd64:/boot/vmlinuz-3.4-trunk-amd64:/boot/initrd.img-3.4-trunk-amd64:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30
 ro quiet
/dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 3.4-trunk-amd64 
(Wiederherstellungsmodus):/boot/vmlinuz-3.4-trunk-amd64:/boot/initrd.img-3.4-trunk-amd64:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30
 ro single
/dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 
3.2.0-3-amd64:/boot/vmlinuz-3.2.0-3-amd64:/boot/initrd.img-3.2.0-3-amd64:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30
 ro quiet
/dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 3.2.0-3-amd64 
(Wiederherstellungsmodus):/boot/vmlinuz-3.2.0-3-amd64:/boot/initrd.img-3.2.0-3-amd64:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30
 ro single
/dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 
3.1.8+vdr1:/boot/vmlinuz-3.1.8+vdr1:/boot/initrd.img-3.1.8+vdr1:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30
 ro quiet
/dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 3.1.8+vdr1 
(Wiederherstellungsmodus):/boot/vmlinuz-3.1.8+vdr1:/boot/initrd.img-3.1.8+vdr1:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30
 ro single
/dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 
3.1.0-1-amd64:/boot/vmlinuz-3.1.0-1-amd64:/boot/initrd.img-3.1.0-1-amd64:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30
 ro quiet
/dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 3.1.0-1-amd64 
(Wiederherstellungsmodus):/boot/vmlinuz-3.1.0-1-amd64:/boot/initrd.img-3.1.0-1-amd64:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30
 ro single
root@hdvdr:/usr/src# umount /dev/sda2
root@hdvdr:/usr/src# linux-boot-prober /dev/sda2 
umount: /var/lib/os-prober/mount: not mounted

I've done an 'fsck -f' prior to the above test and I've also tried to
mkdir /var/lib/os-prober/mount
prior to similar tests, but it didn't make any difference.

The report was set to important as it is impacting greatly its usage.

Thanks, Eric

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.8+vdr1 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages os-prober depends on:
ii  libc6  2.13-33

os-prober recommends no packages.

os-prober suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120715172510.14193.81282.report...@hdvdr.lan

Re: Emdebian sprint / runtime device fingerprinting in bootloader

[Eric Cooper]

On Thu, Feb 24, 2011 at 07:09:51AM +, Andy Green wrote:
> Well saying that it's very similar, then listing differences like
> GPIOs that could easily be runtime-detectable, doesn't really pin
> down whether that's a problem or not.

See the arch/arm/mach-kirkwood directory in the Linux tree.  All the
*-setup.c files declare different sets of GPIOs in static structures.
If you know a way to "easily" detect them at runtime, that could unify
a lot of this code.  I'm sure a patch would be welcome.

> What does "different amount of UART" mean when it is the "same
> Kirkwood SoC"?

(Note that I didn't say what you quoted.)  But it was a brain slip; I
was just remembering a difference in the physical connectors for the
serial ports.

-- 
Eric Cooper e c c @ c m u . e d u


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110224130819.GA6487@localhost

Re: Emdebian sprint / runtime device fingerprinting in bootloader

[Eric Cooper]

On Wed, Feb 23, 2011 at 04:45:25PM +, Andy Green wrote:
> Maybe Steve Sakoman can suggest some example boards that will be
> difficult to tell apart at runtime, but it matters?

Here's one example: the Seagate DockStar is very similar to the
Marvell Sheevaplug (same Kirkwood SoC), but has a different amount of
SDRAM, different GPIOs, UART, etc.  Many of the other systems based on
this chip ("plug computers") would be similarly difficult to
distinguish at runtime.

-- 
Eric Cooper e c c @ c m u . e d u


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110223182122.GG2845@localhost

Bug#603960: Same problem occurs with amd64 iso image

[Eric Wayman]

Hello Feri,

I just tested the original beta2 squeeze installer. Selecting
"Install" from the splash screen menu exhibited the same behavior as
with the special ISO you had linked me to: a 30-second or so wait, and
then the installer process began and the language menu showed up.

Replacing the closing "-- quiet" with "edd=off" as you instructed, the
installer still worked. In this case however, there was no wait at all
for the language menu to show up.

Best Regards,
Eric


On Fri, Dec 24, 2010 at 4:24 AM, Ferenc Wagner  wrote:
> Eric Wayman  writes:
>
>> I just tested the ISO you linked me to; sorry for the long delay in my
>> response.
>
> Hi Eric,
>
> No problem, thanks for testing!
>
>> Basically, everything works. [...]
>> I think I see what the issue is. When I entered "test" and "test-788",
>> it took about 30 seconds to complete the "Probing EDD (edd-off to
>> disable)..." step. At that time, I thought it might have jammed as
>> before. However, after waiting 30 seconds, everything worked properly.
>>
>> Selecting "Install" from the splash screen menu, I also had to wait
>> about 30 seconds before the splash screen disappeared and I was taken
>> into the installer process.
>>
>> I believe that this wait is probably the "bug" I was experiencing with
>> the beta2 installer. So it is likely that the "bug" is just the long
>> wait time which led me to believe the installer had jammed. This
>> problem did not exist on Debian Lenny.
>>
>> I hope this is helpful! If you would like me to submit this
>> information somewhere, please tell me how so that they know that I
>> used a different install version.
>
> This is immensely useful.  I Cc-d the bug report, so you needn't submit
> this separately anymore.  However, I'd like to ask you test two more
> things if possible: please try the original beta2 squeeze installer
> again, giving the EDD probe some more time to time out.  Then, whatever
> happens, boot again, press TAB on the Install menu item, and replace the
> closing "-- quiet" with "edd=off" on the command line.  Please report
> back your findings with keeping the bug address on Cc.
> --
> Thanks,
> Feri.
>



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktin7yjzvn6eke15=pcnjbfdedqaf7zoymzqcl...@mail.gmail.com

Bug#603960: Same problem occurs with amd64 iso image

[Eric Wayman]

This bug also occurs when using the amd64 iso image
(http://cdimage.debian.org/cdimage/squeeze_di_beta2/amd64/iso-cd/debian-squeeze-di-beta2-amd64-netinst.iso),
downloaded 2010-12-10. Exactly the same behavior is exhibited: I get
to the splash screen, and hit Enter. Then it reads from the CD drive,
and then stops reading, and nothing happens. The splash screen is
still displayed. Then if I start pressing keys, after several presses,
beeping starts.

I was able to install Debian Squeeze by using the HDD method with the
files at 
http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/netboot/debian-installer/amd64/
. No errors occurred.



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktim_s3ezgg48teyu-zso0ate918rfa7uscmre...@mail.gmail.com

Re: Bug#603798: debian-installer: /tmp is not created with 777 mode when doing manual disk partitionning

[VALETTE Eric RD-MAPS-REN]

On 11/19/2010 10:20 AM, Samuel Thibault wrote:

VALETTE Eric RD-MAPS-REN, le Fri 19 Nov 2010 09:20:59 +0100, a écrit :

If you don't want to fix it, I do not care.

We DO want to fix it. But we can't fix something that we don't
understand. When we try to reproduce this bug we just get proper
permissions. So there must be something that we are doing differently.
It could even be a completely unrelated detail like language, chosen debian
mirror, etc. That's why we need precise details to be able to reproduce
the issue, and thus fix it.
What can I say that I have not already said? I started by the netboot 
iso for amd64 from last sunday 14/11 image. I chose the default 
graphical installer. The target disk was already formatted but using a 
32 bit install and with a too small /usr and 32 bits binaries. I thus 
started the partitioning by deleting first one by one the existing 
partitions using only the partman interface and then recreated them one 
by one using partman with different size, adding the LABEL and changing 
the /tmp fs type from ext3 to ext2


I cannot insure the /tmp settings were wrong from beginning immediately 
after the first reboot as I did not install anything beyond the strictly 
basic installer packages and did not have any graphical packages at that 
time and may have missed it. I also logged only as root and thus may 
have missed the tmp permission problem.


Then I did after that
1) restore my apt source list
2) a dpkg --set-selection from a the previously saved 32 bit instal 
get-selection and an apt dselect-upgrade
3) rebooted and verified that KDM was started but did not log in as 
it was past midnight


Again I cannot assure that /tmp setting were wrong at that time.

What I'm sure of:
1) at the end /tmp setting were wrong
2) I never executed a *self cooked script* changing tmp settings

I you looked at the path for tmp permission setting and the path looks 
correct this is enough for me. BTW I have a question: do you set the 
1777 on the root of the real  tmp FS and also on the "umounted" /tmp 
directory? because tmp mounting first failed with my own generated 
kernel because I forgot to enable ext2 (only ext3 was enabled), I had to 
recompile it before being able to actually mount /tmp as an ext2 FS and 
I do not remember with which kernel I did see the wrong permissions (aka 
with /tmp mounted as an ext2 fs or the one available via the / 
filsesystem if the mount is not yet performed or fails).


I would not have opened the bug given all i did in addition to the other 
install if I did not remember have already seen the same bug on another 
totally different install (with a different installer version).


-- eric

Bug#603798: debian-installer: /tmp is not created with 777 mode when doing manual disk partitionning

[VALETTE Eric RD-MAPS-REN]

On 11/18/2010 08:31 PM, Matthew Palmer wrote:

On Thu, Nov 18, 2010 at 01:44:39PM +0100, VALETTE Eric RD-MAPS-REN wrote:

On 11/18/2010 10:09 AM, Christian Perrier wrote:

VALETTE Eric RD-MAPS-REN a écrit :


Done nothing special except creating the partitions manually. This is

^

This is where we need details!

Tmp was created as ext2 FS, with TMP LABEL, what else? ALL other
partition were ext3 and add label = mount point (USR,VAR, HOME, ROOT)
except of course swap. No dedicated boot partition.

Wrong details, I suspect.  With an unreproducible bug like the one you've
got, we need to make it reproducible before it can be fixed.  For that to
happen, we need to be able to do what you did to make it happen.  Until
then, we're helpless.

What we need is a description of how, *precisely*, and in excruciating
detail, you created the partitions manually.  Did you drop into a console
and issue partman/mkfs/mount commands by hand?  If so, what commands did you
run, exactly?  Or did you use the manual method within partman (the
text-based GUI)?  Again, if so, what precisely did you do?  (As in, "First I
selected the 'Flibble with my frufru' option, then 'Blingle the blangle',
then 'You get the idea'..."  Or did you do something else entirely?  If so,
what was it?  (Again, in very fine-grained detail).

- Matt


If you don't want to fix it, I do not care. I did not create the 
partition manullay outside the installer but I created them manually 
within the installer using the graphical install.


I seems, you should know weher you do the chmod 1777 /tmp in the 
installer and look if there are installation path that do not use this path.


-- eric


--
Eric Valette
France Telecom
Recherche&  Developpement
Middleware et Plates-formes Avancées
Architecte Livebox et Set Top Box
tél : (+33) 2 99 12 45 71
mél :<mailto:eric2.vale...@orange-ftgroup.com>

Bug#603960: Debian Installer 6.0 Beta1 bug report

[Eric Wayman]

Package: installation-reports

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/squeeze_di_beta1/i386/iso-cd/debian-squeeze-di-beta1-i386-netinst.iso
Date: 2010-11-18 16:10:00 EST

Machine: Toshiba U205-S5057
Processor:Intel® Core™ 2  Duo Processor T55004 1.66GHz, 2MB L2, 667MHz
FSB with 64-bit
Memory: 1024MB PC4200 DDR2 SDRAM
Partitions: One partition

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

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

Initial boot:   [ O]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ O]
Load installer modules: [ O]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

When I pressed Enter at the first install screen to "Install Debian,"
the installer read from the CD for a few seconds, and then just
halted. After pressing several keys to try to select a different
option, the system began beeping and was totally jammed. The initial
install screen remained displayed.

See 
http://cdgenp01.csd.toshiba.com/content/product/pdf_files/detailed_specs/satellite_U205-S5057.pdf
for full machine specifications.



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlkti=cisqpog8sqo20tsyozorbw1o8kjd62y9qv...@mail.gmail.com

Bug#603798: debian-installer: /tmp is not created with 777 mode when doing manual disk partitionning

[VALETTE Eric RD-MAPS-REN]

On 11/18/2010 10:09 AM, Christian Perrier wrote:

VALETTE Eric RD-MAPS-REN a écrit :


Done nothing special except creating the partitions manually. This is

   ^

This is where we need details!

Tmp was created as ext2 FS, with TMP LABEL, what else? ALL other 
partition were ext3 and add label = mount point (USR,VAR, HOME, ROOT) 
except of course swap. No dedicated boot partition.


--
Eric Valette
France Telecom
Recherche&  Developpement
Middleware et Plates-formes Avancées
Architecte Livebox et Set Top Box
tél : (+33) 2 99 12 45 71
mél :<mailto:eric2.vale...@orange-ftgroup.com>

Bug#603798: debian-installer: /tmp is not created with 777 mode when doing manual disk partitionning

[VALETTE Eric RD-MAPS-REN]

On 11/17/2010 10:46 PM, Christian PERRIER wrote:

tags 603798 unreproducible
thanks

Quoting Eric Valette (eric2.vale...@orange-ftgroup.com):

Package: debian-installer
Version: Debian Installer 14/11/2010
Severity: important
Tags: d-i

I reinstalled a machine this week-end. The install base smootly worked.
I created a separate /tmp file system that was monted but with wrong permission.
root.root 755. Visible effect is that kdm login loops as the X server does not
manage to create some /tmp/ files.

Doing a chmod 777 /tmp with file system monted solves the problem.

We need more details about the way you managed to do this.

I just ran an install with a separate /tmp partition and it ended with
/tmp being 1777 as expected.

Please give details about hos to reproduce this.



Done nothing special except creating the partitions manually. This is 
the second time it appends on different machine and different version of 
the installer. Last intaller was AMD64.


I do the install, configure only the minimum system (no extra package vi 
tasksel). Change the sources.list to add experimental and do the real 
install once rebooted to avoid downloading packages and then upgrading them.


-- eric

Bug#603798: debian-installer: /tmp is not created with 777 mode when doing manual disk partitionning

[Eric Valette]

Package: debian-installer
Version: Debian Installer 14/11/2010
Severity: important
Tags: d-i

I reinstalled a machine this week-end. The install base smootly worked.
I created a separate /tmp file system that was monted but with wrong permission.
root.root 755. Visible effect is that kdm login loops as the X server does not
manage to create some /tmp/ files.

Doing a chmod 777 /tmp with file system monted solves the problem.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.36 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF8)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/ftrdmel10qyx3g5ayy60...@ftrdmel10.rd.francetelecom.fr

Bug#603756: console-setup: [INTL:nl] Updated Dutch PO translation for D-I release

[Eric Spreen]

Package: console-setup
Severity: wishlist
Tags: patch l10n

Dear maintainer,

Hereby you will find attached an updated Dutch PO translation for console-setup.
I would be pleased if this could be included in the package before the next
release of D-I.

Thanks in advance,
Eric Spreen
Dutch Translation Team


-- System Information:
Debian Release: 5.0.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


nl.po.gz
Description: GNU Zip compressed data

Bug#603318: debian-installer: Does not detect the USB wireless keyboard

[Eric Valette]

On 13/11/2010 12:52, Otavio Salvador wrote:

On Sat, Nov 13, 2010 at 9:48 AM, Eric Valette  wrote:

On 13/11/2010 12:03, Otavio Salvador wrote:


It would be good if you could give a try to the installer. You won't
need to reinstall the system just boot the new one and see if has hot
it to work.


OK. I can wait a bit anyway as the machine is running but as XBMC + pvr
recors reading skips a bit (due to context switch between XBMC and VDR +
streamdev as streaming in a remote XBMC works), I'm rather sure I will
reinstall soon. Waiting a week is probably OK.

Drop me a mail or close the bug when a new iso of the installer is ready.


I am in the process of building the kernel udebs for installer. Please
test a daily in a day so it will have the newer kernel into it.



Tested and confirmed working. Thanks.

--eric



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ce04448.70...@free.fr

Bug#603318: debian-installer: Does not detect the USB wireless keyboard

[Eric Valette]

On 13/11/2010 12:03, Otavio Salvador wrote:


It would be good if you could give a try to the installer. You won't
need to reinstall the system just boot the new one and see if has hot
it to work.


OK. I can wait a bit anyway as the machine is running but as XBMC + pvr 
recors reading skips a bit (due to context switch between XBMC and VDR + 
streamdev as streaming in a remote XBMC works), I'm rather sure I will 
reinstall soon. Waiting a week is probably OK.


Drop me a mail or close the bug when a new iso of the installer is ready.

-- eric



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cde7af5.6020...@free.fr

Bug#603318: debian-installer: Does not detect the USB wireless keyboard

[Eric Valette]

On 12/11/2010 23:49, Otavio Salvador wrote:

On Fri, Nov 12, 2010 at 8:22 PM, valette  wrote:

Bus 004 Device 002: ID 04fc:05d8 Sunplus Technology Co., Ltd Wireless 
keyboard/mouse<===


I managed to identify the need of hid-sunplus to get this to work. I
have queued it for next kernel update.


OK. Sounds reasonnable. I have it build in with my own generated kernel.

grep SUNPLUS /usr/src/linux-funtwist/.config
CONFIG_HID_SUNPLUS=y



When this bug is closed please wait one day or so and give it a try.


OK. May not wait until then but good to know it will be fixed. Note that 
my wireless keybord is very common (TRUST) and that for HTPC a wireless 
keyboard is very usefull...


Thanks for your support and have a good week-end.

-- eric





--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cddc714.5020...@free.fr

Bug#568179: progress

[Jean-Eric TORLAY]

Since mid march the debian squeeze install on DELL inspirion 11Z is 
OK as the local Ethernet network is working, even if the Wifi is not
operating.

Thank you so much for your help

regards, 

Jean-Eric TORLAY




-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1283076785.5341.3.ca...@jet.adsl.proxad.net

Bug#594616: busybox-syslogd: typos in initscript messages

[Eric Cooper]

Package: busybox-syslogd
Version: 1:1.17.1-2
Severity: minor

"busybox' syslogd implementation" should be either "busybox's syslogd
implementation" if you want the correct possessive form, or just
"busybox syslogd implmentation" if you want to use busybox as just an
adjective modifying syslogd.  I personally like the 2nd form better,
since it's less busy.

Similarly for the message about klogd.

Thanks for packaging this.
-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20100827183153.9931.38200.report...@stratocaster.home

Bug#472704: Failure while configuring base packages -- But why?

[Eric Estievenart]

Could someone change the title of this bug to something more explicit,
like:
"Dependencies not fetched; unexplained failure"

(I know they are explained in debootstrap.log), and maybe raise its
priority.

Btw, I don't really understand the following concept:

--no-resolve-deps
  By default, debootstrap will attempt to automatically
  resolve any missing dependencies, warning if
  any are found.  Note that this is not a complete
  dependency resolve in the sense of dpkg  or  apt,
  and  that  it is far better to specify the entire base
  system than rely on this option.  With this
  option set, this behaviour is disabled.

What is the point of partially resolving deps ?

The issue is likely to be in the functions script :

resolve_deps () {
local m1="${MIRRORS%% *}"

# XXX: I can't think how to deal well with dependency 
resolution and

#  lots of Packages files. -- aj 2005/06/12
c="${COMPONENTS%% *}"

This only keeps the first component, so if multiple components are used,
--components=main,contrib
and a package from contrib is added in the list of required packages,
its dependencies _will_not_be_fetched_,
thus resulting in the error.

Sincerely




--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c6e9ce5.8020...@free.fr

Bug#591436: busybox-syslogd: initscript prints many error messages

[Eric Cooper]

Package: busybox-syslogd
Version: 1:1.15.3-1
Severity: normal

The busybox-syslogd and -klogd initscripts generate lots of error messages like 
this:
cut: /proc/447/stat: No such file or directory
cut: /proc/452/stat: No such file or directory
cut: /proc/453/stat: No such file or directory
Please redirect the stderr output to /dev/null in the initscripts.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20100803011606.7285.1781.report...@stratocaster.home

Bug#572013: bashism in /usr/share/udhcpc/default.script causes network setup to fail

[Eric Cooper]

Package: udhcpc
Version: 1:1.15.3-1
Severity: normal

The proposed fix -- $((metric += 1)) -- doesn't have the same
semantics.  The routing table metric will start at 1 rather than 0.

You need to increment $metric in a separate command, after using it in
the route command:

for i in $router; do
/sbin/route add default gw $i dev $interface metric $metric
metric=$((metric + 1))
done

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages udhcpc depends on:
ii  busybox   1:1.15.3-1 Tiny utilities for small and embed

udhcpc recommends no packages.

udhcpc suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20100520210108.30723.48811.report...@stratocaster.home

workaround(?) for #578338: grub2 won't install

[Eric Dantan Rzewnicki]

(Please Cc: me since I am not subscribed here)

I reported #578338 on monday. I've found a way to work around it, and
wonder if it would be an acceptable approach for debian-installer to
take. If I switch to a shell during the partioning section and create
the raid manually with --metadata=0 option to mdadm, then return and
have the installer "Detect disks" again i'm able to complete
installation including the grub2 installation.

So, my question now is whether some sort of an option to "create md
array for booting from" that used a 0.90 format superblock would make
sense and be acceptable.

-edrz


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100422215544.gc21...@zhevny.com

Bug#578338: hardware log

[Eric Dantan Rzewnicki]

Here is the hardware-summary from the initial failed installation:

uname -a: Linux x4 2.6.32-3-amd64 #1 SMP Wed Feb 24 18:07:42 UTC 2010 x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS780 Host 
Bridge Alternate [1022:9601]
lspci -knn: Subsystem: Advanced Micro Devices [AMD] RS780 Host Bridge 
Alternate [1022:9601]
lspci -knn: 00:01.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780 PCI 
to PCI bridge (int gfx) [1022:9602]
lspci -knn: 00:0a.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780 PCI 
to PCI bridge (PCIE port 5) [1022:9609]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 
SATA Controller [AHCI mode] [1002:4391]
lspci -knn: Subsystem: Giga-byte Technology Device [1458:b002]
lspci -knn: Kernel driver in use: ahci
lspci -knn: 00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB 
OHCI0 Controller [1002:4397]
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5004]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:12.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 
Controller [1002:4398]
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5004]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB 
EHCI Controller [1002:4396]
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5004]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB 
OHCI0 Controller [1002:4397]
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5004]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:13.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 
Controller [1002:4398]
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5004]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB 
EHCI Controller [1002:4396]
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5004]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller 
[1002:4385] (rev 3c)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:4385]
lspci -knn: 00:14.1 IDE interface [0101]: ATI Technologies Inc SB700/SB800 IDE 
Controller [1002:439c]
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5002]
lspci -knn: Kernel driver in use: ATIIXP_IDE
lspci -knn: 00:14.3 ISA bridge [0601]: ATI Technologies Inc SB700/SB800 LPC 
host controller [1002:439d]
lspci -knn: Subsystem: ATI Technologies Inc SB700/SB800 LPC host controller 
[1002:439d]
lspci -knn: 00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI 
Bridge [1002:4384]
lspci -knn: 00:14.5 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB 
OHCI2 Controller [1002:4399]
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5004]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K10 
[Opteron, Athlon64, Sempron] HyperTransport Configuration [1022:1200]
lspci -knn: 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K10 
[Opteron, Athlon64, Sempron] Address Map [1022:1201]
lspci -knn: 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K10 
[Opteron, Athlon64, Sempron] DRAM Controller [1022:1202]
lspci -knn: 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K10 
[Opteron, Athlon64, Sempron] Miscellaneous Control [1022:1203]
lspci -knn: 00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] K10 
[Opteron, Athlon64, Sempron] Link Control [1022:1204]
lspci -knn: 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc 
RS880 [Radeon HD 4200] [1002:9710]
lspci -knn: Subsystem: Giga-byte Technology Device [1458:d000]
lspci -knn: 01:05.1 Audio device [0403]: ATI Technologies Inc RS880 Audio 
Device [Radeon HD 4200] [1002:970f]
lspci -knn: Subsystem: Giga-byte Technology Device [1458:960f]
lspci -knn: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 02)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:e000]
lspci -knn: Kernel driver in use: r8169
lspci -knn: 03:0e.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB23 
IEEE-1394a-2000 Controller (PHY/Link) [104c:8024]
lspci -knn: Subsystem: Giga-byte Technology Device [1458:1000]
lspci -knn: Kernel driver in use: firewire_ohci
usb-list: 
usb-list: Bus 01 Device 01: EHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 2.6.32-3-amd64 ehci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 02 Device 01: EHCI Host Controller [1d6b:0

Bug#578338: Acknowledgement (debian-installer: grub-install fails to md0)

[Eric Dantan Rzewnicki]

Some further information on this ... 

Today I tried a lenny install on the same system using the lenny
installer, but using the existing partition table and raid1 device
created during the previously reported failed squeeze installation. 

I noticed that the partition table was a little odd. fdisk reported the
swap partitions I had created did not end on cylinder boundaries and the
lenny grub-install also failed. After going back within the installer to
delete and re-create the md device and partitions, lenny installation
was successful, including grub-install.

Seeing that, I decided to see if maybe the daily-image installer would
work with the partion tables created from within the lenny installer.

It did work fine.

So, it seems that something about the partitioner is broken with
respect to grub-pc.

I use manual partioning, not guided, in all cases.

-edrz



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100420182428.ga4...@zhevny.com

Bug#578338: debian-installer: grub-install fails to md0

[Eric Dantan Rzewnicki]

Package: debian-installer
Version: daily-images amd64 netboot.tar.gz 2010-0418
Severity: important


I reported this problem a few weeks ago when attempting to install a very
similar system: http://lists.debian.org/debian-user/2010/04/msg00092.html

This time I again used the daily image (2010-04-18):
http://d-i.debian.org/daily-images/amd64/daily/netboot/netboot.tar.gz

via tftpboot.

The system install works fine up to the point of attempting to install grub:

Apr 19 08:06:09 grub-installer: info: Installing grub on '(hd0)'
Apr 19 08:06:09 grub-installer: info: grub-install supports --no-floppy
Apr 19 08:06:09 grub-installer: info: Running chroot /target grub-install  
--no-floppy --force "(hd0)"
Apr 19 08:06:10 grub-installer: /usr/sbin/grub-probe: error: no mapping exists 
for `md0'.
Apr 19 08:06:10 grub-installer: Auto-detection of a filesystem module failed.
Apr 19 08:06:10 grub-installer: Please specify the module with the option 
`--modules' explicitly.
Apr 19 08:06:10 grub-installer: error: Running 'grub-install  --no-floppy 
--force "(hd0)"' failed.

I saved the full hardware-summary, partman and syslog files. Let me know where
to send them. I do not need this system up immediately, so can help with
sorting it out. I am edrz on irc.

-- System Information:
Debian Release: squeeze
Architecture: amd64

Kernel: Linux 2.6.32-3-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20100419014212.28016.65583.report...@orinen.zhevny.com

Bug#575672: installation-reports: KDE install ends without print management.

[Eric Lavarde]

Package: installation-reports
Severity: normal



-- Package-specific info:

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/squeeze_di_alpha1/i386/iso-cd/debian-testing-i386-netinst.iso
Date: 

Machine: HP Compaq dc5700 Microtower
Partitions: 


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:  [E]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

Everything worked actually quite well, with the exception that I chose the KDE 
install,
and ended with a system that doesn't have any obvious mean to configure 
printing.
And I want to state that I know that I can point my browser to localhost:631, 
but I think
that a first time user (who is deemed to use KDE) won't find this very easy, if 
at all, and
might give up on Linux/Debian.

Eric

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="6.0 (squeeze) - installer build 20100211"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux emil 2.6.30-2-486 #1 Sat Sep 26 00:03:46 UTC 2009 i686 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 82Q963/Q965 Memory 
Controller Hub [8086:2990] (rev 02)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2808]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 
82Q963/Q965 Integrated Graphics Controller [8086:2992] (rev 02)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2808]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation 82Q963/Q965 
Integrated Graphics Controller [8086:2993] (rev 02)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2808]
lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #4 [8086:2834] (rev 02)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2808]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #5 [8086:2835] (rev 02)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2808]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB2 EHCI Controller #2 [8086:283a] (rev 02)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2808]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) 
HD Audio Controller [8086:284b] (rev 02)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2808]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 1 [8086:283f] (rev 02)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 2 [8086:2841] (rev 02)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #1 [8086:2830] (rev 02)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2808]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #2 [8086:2831] (rev 02)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2808]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #3 [8086:2832] (rev 02)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2808]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB2 EHCI Controller #1 [8086:2836] (rev 02)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2808]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge 
[8086:244e] (rev f2)
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801HB/HR (ICH8/R) 
LPC Interface Controller [8086:2810] (rev 02)
lspci -knn:

Complaint about apt installing Recommends by default.

[Eric Renfro]

I'm seriously.. VERY seriously enraged by the very thought of Debian 
moving to preconfigure and install "Recommends" by default. This is the 
worst decision Debian could ever make. That very one thing is one of my 
biggest complaints about Ubuntu doing so and strongly /VERY/ strongly 
insist it not be done.


I have been a Debian user since way back when, and I completely disagree 
with this decision. Recommends should NOT be treated as if Required, 
ever. Things such as, for an example, rsyslog-pgsql, to add postgresql 
logging support. Generally such a package could (AND SHOULD!) recommend 
postgresql-server, and at the very least Require postgresql-client. 
Since rsyslog-pgsql would be just a component to add support to log TO a 
PostgreSQL server, it's not essentially required to run it on the same 
system the module is installed on. But to "by default" imposedly install 
postgresql-server on every system you install rsyslog-pgsql to just 
because it's recommend, is outright unacceptably insanely stupid.


Another prime example is a package maintainer may "Recommend" pulseaudio 
for the use of ... Let's use Amarok as an example. Is it absolutely 
Required to use PulseAudio with Amarok to play audio? Absolutely not. 
With the direction PulseAudio has gone as well, it would be hard to 
honestly recommend such a thing, but it can and likely even will happen, 
and unless someone pins pulseaudio packages from ever installing, they 
may very well have it shoved down their throat. Is this acceptable? 
Completely not.


I will firmly say this. It is completely stupid to, by default, install 
Recommends. In the past, only Ubuntu has ever done this, and it is by 
far, one of the stupidest things they have ever done. Absolutely /no/ 
other reasonable distribution does this.


Eric Renfro


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ba683a5.1000...@gmail.com

Bug#562557: console-setup: Wrong keyboard in single mode/normal boot failure

[Eric Valette]

On 27/12/2009 13:20, Anton Zinoviev wrote:


Indeed copying ckbcomp  to /bin instead of /usr/bin fixes the problem.


Yes, I can confirm this.  Setupcon tests the existence of ckbcomp even
when it doesn't require ckbcomp.  Thanks for the debugging.

When this bug is fixed (maybe in the next upload) don't forget to remove
/bin/ckbcomp.



Will try to remember it when I receive the notification for the bug 
being closed. Now, I that I cured the side effect, I have to cure the 
real problem, that is, why checkfs script always returns an error even 
if the FS are good and I have to press  to finish booting. But I 
guess its because I use the experimental RC for dosfsck and it fails 
over a FS flagged purposely flagged with noauto as its for USB stick.


But that's another story. Thanks for your support and happy holidays/new 
year.


-- eric





--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#562557: console-setup: Wrong keyboard in single mode/normal boot failure

[Eric Valette]

On 26/12/2009 22:47, Eric Valette wrote:


I finally found the bug: I traced setupcons -k in error mode and it
expects to find ckbcomp but unfortunately /usr is not mounted and
ckbcomp is /usr/bin/ckbcomp

I traced the setupcons -k with set -x and it exist with doing anyting
because it does not find ckbcomp in the path.


Indeed copying ckbcomp  to /bin instead of /usr/bin fixes the problem.

--eric





--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#562557: console-setup: Wrong keyboard in single mode/normal boot failure

[Eric Valette]

I finally found the bug: I traced setupcons -k in error mode and it 
expects to find ckbcomp but unfortunately /usr is not mounted and 
ckbcomp is /usr/bin/ckbcomp


I traced the setupcons -k with set -x and it exist with doing anyting 
because it does not find ckbcomp in the path.


-- eric






--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#562557: console-setup: Wrong keyboard in single mode/normal boot failure

[Eric Valette]

On 26/12/2009 20:16, Anton Zinoviev wrote:

On Sat, Dec 26, 2009 at 06:39:13PM +0100, Eric Valette wrote:


I tested manually after entering the maintenance mode S06keyboard-setup
and yes it does print something and does a "setupcon -k" but the
keyboard is still wrong after the script has executed.


By wrong do you mean it is a QWERTY keyboard?  Or it is a French one but
wrong in some other way?


Its a qwerty keyboard.



What happens if you execute

loadkeys /etc/console-setup/cached.kmap.gz


Well I just removed it just in case. I will have to wait until reboot 
but I cannot now...



Is the contents of /etc/default/keyboard correct?  It has to contain
lines like the following:

XKBMODEL="pc105"
XKBLAYOUT="fr"
XKBVARIANT=""


XKBMODEL="pc105"
XKBLAYOUT="fr"
XKBVARIANT=""
XKBOPTIONS="lv3:ralt_switch"



What happens with the keyboard if you use the command 'setupcon' when
the machine is in regular mode (not in maintenance mode)?


Well I have tried t log on a console and this does no more work either.


I am puzzled by the fact you say the keyboard doesn't work in
maintenance mode but it works in normal mode.  This is because in both
cases the keyboard is configured by the command

loadkeys /etc/console-setup/cached.kmap.gz


I was simply wrong: I discovered it when entering in maintenance mode 
and last time I used the console to kill xbmc or kdm it worked. 
Something did chnage in the mean time.




and there is nothing there to depend on /usr being mounted.  Can you
edit /etc/default/console-setup and put there the line

VERBOSE_OUTPUT="yes"

and see if there are some error messages?


Yes I get a syntax error! for Lat15-Fixed16.psf.gz. You got it because 
it. I attach it




--
   __
  /  `  Eric Valette
 /--   __  o _. 6 rue Paul Le Flem
(___, / (_(_(__ 35740 Pace

Tel: +33 (0)2 99 85 26 76   Fax: +33 (0)2 99 85 26 76
E-mail: eric.vale...@free.fr





Lat15-Fixed16.psf.gz
Description: application/gzip

Bug#562557: console-setup: Wrong keyboard in single mode/normal boot failure

[Eric Valette]

On 26/12/2009 18:11, Eric Valette wrote:

On 26/12/2009 17:39, Eric Valette wrote:
Here are the buggy lines in keymap.sh

# If setupcon is present, then we've been superseded by console-setup.
if type setupcon >/dev/null 2>&1; then
exit 0
fi

because console-setup is run tto late in case of voluntary single mode
or failure during file system checks.


I should have read the next script!

I tested manually after entering the maintenance mode S06keyboard-setup
and yes it does print something and does a "setupcon -k" but the 
keyboard is still wrong after the script has executed.


-- eric





--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#562557: console-setup: Wrong keyboard in single mode/normal boot failure

[Eric Valette]

On 26/12/2009 17:39, Eric Valette wrote:
Here are the buggy lines in keymap.sh

# If setupcon is present, then we've been superseded by console-setup.
if type setupcon >/dev/null 2>&1; then
exit 0
fi

because console-setup is run tto late in case of voluntary single mode 
or failure during file system checks.



--eric





--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#562557: console-setup: Wrong keyboard in single mode/normal boot failure

[Eric Valette]

BTW readding the scripts, it look like the bug is more in console-common
and that for some reason, the /etc/console/boottime.kmap.gz does not get
loaded.


I entered rescue mode again and did the loadkeys 
/etc/console/boottime.kmap.gz and got my french keyboard back. 
Unfortunately I had still to enter the passwd using the wrong keyboard 
layout!


-- eric





--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#562557: console-setup: Wrong keyboard in single mode/normal boot failure

[Eric Valette]

On 26/12/2009 17:04, Eric Valette wrote:

On 26/12/2009 14:52, Anton Zinoviev wrote:

On Fri, Dec 25, 2009 at 09:35:42PM +0100, Eric Valette wrote:


I had a file system witha date set in the future, and thus entered
single mode. I had then a wrong keyboard


This shouldn't be happening so I need you to make few tests in order to
see what went wrong.


OK.


First, to make it clear - I suppose you you entered single user mode
from the corresponding menu item of grup? If you used 'emergency' mode
(option -b at grub menu) then it would be normal for the keyboard to be
leaven unconfigured.


No I entered this mode because the check of the filesystem failed
(S30checkfs in rcS.d that is after S06keyboard-setup)


Second, while you machine is entering single user mode do you see the
text 'Setting preliminary keymap'?


I do not see it but my screen is full of message because of the various
drivers and file system so I may have missed it.

If you don't, do you have a file

/etc/rcS.d/S06keyboard-setup?


ls -l /etc/rcS.d/S06keyboard-setup
lrwxrwxrwx 1 root root 24 avril 11 2009 /etc/rcS.d/S06keyboard-setup ->
../init.d/keyboard-setup



Third, if you see the text 'Setting preliminary keymap', can you test
that the keyboard is still unconfigured? What is the output of the
command

ls -l /etc/default/keyboard /etc/console-setup/cached.kmap.gz


ls -l /etc/default/keyboard /etc/console-setup/cached.kmap.gz
-rw-r--r-- 1 root root 4776 déc. 26 09:55 /etc/console-setup/cached.kmap.gz
-rw-r--r-- 1 root root 668 déc. 25 21:23 /etc/default/keyboard



Console-setup uses time-stamps in order to determine whether the
keyboard map needs recompiling. If your date/time was incorrect and
cached.kmap.gz seems newer than /etc/default/keyboard then console-setup
will never recompile the keymap. If this is the case, then you need to
remove /etc/console-setup/cached.kmap.gz.


BTW if I hit ctlr D, and let the boot finish the kerboard on the console
are OK. And I alraedy done dpkg-reconfigure console-setup several times
(2X)



BTW readding the scripts, it look like the bug is more in console-common 
and that for some reason, the /etc/console/boottime.kmap.gz does not get 
loaded.


--
   __
  /  `  Eric Valette
 /--   __  o _. 6 rue Paul Le Flem
(___, / (_(_(__ 35740 Pace

Tel: +33 (0)2 99 85 26 76   Fax: +33 (0)2 99 85 26 76
E-mail: eric.vale...@free.fr









--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#562557: console-setup: Wrong keyboard in single mode/normal boot failure

[Eric Valette]

On 26/12/2009 14:52, Anton Zinoviev wrote:

On Fri, Dec 25, 2009 at 09:35:42PM +0100, Eric Valette wrote:


I had a file system witha date set in the future, and thus entered
single mode. I had then a wrong keyboard


This shouldn't be happening so I need you to make few tests in order to
see what went wrong.


OK.


First, to make it clear - I suppose you you entered single user mode
from the corresponding menu item of grup?  If you used 'emergency' mode
(option -b at grub menu) then it would be normal for the keyboard to be
leaven unconfigured.


No I entered this mode because the check of the filesystem failed 
(S30checkfs in rcS.d that is after S06keyboard-setup)



Second, while you machine is entering single user mode do you see the
text 'Setting preliminary keymap'?


I do not see it but my screen is full of message because of the various 
drivers and file system so I may have missed it.


 If you don't, do you have a file

/etc/rcS.d/S06keyboard-setup?


ls -l /etc/rcS.d/S06keyboard-setup
lrwxrwxrwx 1 root root 24 avril 11  2009 /etc/rcS.d/S06keyboard-setup -> 
../init.d/keyboard-setup




Third, if you see the text 'Setting preliminary keymap', can you test
that the keyboard is still unconfigured? What is the output of the
command

ls -l /etc/default/keyboard /etc/console-setup/cached.kmap.gz


ls -l /etc/default/keyboard /etc/console-setup/cached.kmap.gz
-rw-r--r-- 1 root root 4776 déc.  26 09:55 /etc/console-setup/cached.kmap.gz
-rw-r--r-- 1 root root  668 déc.  25 21:23 /etc/default/keyboard



Console-setup uses time-stamps in order to determine whether the
keyboard map needs recompiling.  If your date/time was incorrect and
cached.kmap.gz seems newer than /etc/default/keyboard then console-setup
will never recompile the keymap.  If this is the case, then you need to
remove /etc/console-setup/cached.kmap.gz.


BTW if I hit ctlr D, and let the boot finish the kerboard on the console 
are OK. And I alraedy done dpkg-reconfigure console-setup several times (2X)


-- eric






--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#562557: console-setup: Wrong keyboard in single mode/normal boot failure

[Eric Valette]

Package: console-setup
Version: 1.50
Severity: normal

I had a file system witha date set in the future, and thus entered single mode. 
I had
then a wrong keyboard which is annoying because when you are in this mode you
are likely to kill your machine if using the wrong key (even enetring the 
passwd may 
be challenging).

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32.2 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages console-setup depends on:
ii  console-terminus  4.30-2 Fixed-width fonts for fast reading
ii  debconf [debconf-2.0] 1.5.28 Debian configuration management sy
ii  keyboard-configuration1.50   system-wide keyboard preferences
ii  xkb-data  1.7-1  X Keyboard Extension (XKB) configu

Versions of packages console-setup recommends:
ii  console-tools  1:0.2.3dbs-66 Linux console and font utilities
ii  kbd-compat [kbd]   1:0.2.3dbs-66 Wrappers around console-tools for 

Versions of packages console-setup suggests:
ii  locales   2.10.2-2   GNU C Library: National Language (
pi  lsb-base  3.2-23 Linux Standard Base 3.2 init scrip

-- debconf information:
* console-setup/variant: France
* console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
  console-setup/unsupported_options: true
  console-setup/ctrl_alt_bksp: false
  console-setup/modelcode: pc105
  console-setup/use_system_font:
  console-setup/fontsize: 16
  console-setup/unsupported_layout: true
  console-setup/layoutcode: fr
  debian-installer/console-setup/title:
  console-setup/codesetcode: Lat15
  console-setup/altgr: Right Alt
  console-setup/ttys: /dev/tty[1-6]
  console-setup/codeset: # Latin1 and Latin5 - western Europe and Turkic 
languages
  console-setup/toggle: No toggling
  console-setup/fontface: Fixed
  console-setup/fontsize-text: 16
  console-setup/compose: No compose key
  debian-installer/console-setup-udeb/title:
  console-setup/other:
  console-setup/switch: No temporary switch
  console-setup/unsupported_config_layout: true
  console-setup/charmap: UTF-8
* console-setup/fontface47: Fixed
* console-setup/fontsize-text47: 16
  console-setup/optionscode: lv3:ralt_switch
  console-setup/unsupported_config_options: true
* console-setup/charmap47: ISO-8859-15
* console-setup/layout: France
  console-setup/variantcode:
  console-setup/model: PC générique 105 touches (intl)
  console-setup/fontsize-fb: 16
  console-setup/fontsize-fb47: 16





--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#547218: debootstrap: cannot create squeeze chroot

[Eric Cooper]

Package: debootstrap
Version: 1.0.15
Severity: important
Tags: patch

debootstrap currently fails to create a squeeze chroot.  The log
output shows that readline-common depends either on dpkg >= 1.15.4
(which is not yet in squeeze) or on install-init (which isn't being
installed), so it fails.

If I add
--include=install-init
to the command line to break the cycle it works correctly.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (400, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages debootstrap depends on:
ii  binutils  2.19.51.20090723-1 The GNU assembler, linker and bina
ii  wget  1.11.4-4   retrieves files from the web

Versions of packages debootstrap recommends:
ii  gnupg 1.4.9-4GNU privacy guard - a free PGP rep

debootstrap suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Illustrated Guide to Installing Debian GNU/Linux

[Eric Doviak]

Frans Pop wrote:
IMO that means the debian-edu concept is not suitable for this document as 
it is not intended to be published as a separate manual. We have the 
Installation Guide for that.


This document is intended to remain on the Wiki as an optional reference 
for users and as such translations should also be done and be available 
as wiki pages.
  


With all due respect to the Debian Installer team, who produced a 
fabulous installation manual[1], I would like to encourage you to 
publish the "Illustrated Guide ..."[2] as a separate manual because the 
two documents serve two distinctly different audiences.


The comprehensive nature (143 pages) of the official installation manual 
is invaluable to anyone who has to perform a complex and/or uncommon 
task (such as using TFTP to boot a computer over a network from another 
machine).


The "Illustrated Guide" is designed to serve desktop users who are 
installing a GNU/Linux operating system for the first time. While the 
official installation manual provides a nice 3-page installation HowTo 
(in Appendix A), it does not cater directly to the needs of new 
GNU/Linux users.


By contrast, the "Illustrated Guide" is 10 pages long and is filled with 
screenshots (to make the new user feel comfortable). To add a touch of 
comprehensiveness, I also included 12 pages of appendices to introduce 
them to package management, help them select packages (e.g. office 
software, music managers, etc.) and work with an MS Windows partition.


In summary, the "Illustrated Guide" serves a different audience than the 
official manual does. On that basis, I hope you will consider it for 
inclusion as a separate manual.


Sincerely,
- Eric Doviak


[1] http://www.debian.org/releases/stable/installmanual
[2] http://wiki.debian.org/LennyIllustratedInstall



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Illustrated Guide to Installing Debian GNU/Linux

[Eric Doviak]

Frank Lin PIAT wrote:

Your recommendation aren't consistent with Debian.
  
Given my preference for consistency over confusion, I will definitely 
edit the guide to make it consistent with Debian's recommendations. Just 
give me a week or two to make the changes. I'm rather busy at the moment.




 * openoffice, gimp, ekiga, pigin... are installed by default[1]
   so there is no need to explain how to install them. 
Explaining that the packages are there is also valuable information, so 
instead of removing those items, I think I'll just include a note that 
says that they are installed by default.




* Debian has chosen to install openoffice rather that abiword and
   gnumeric, so it's awkward that your first example is to install
   it.
  

Shuffling the order shouldn't be too difficult. Will do!



Also the wiki pages http://wiki.debian.org/WindowsEquivalent aims to
list equivalent application, *in* Debian. It isn't complete yet.
  

I'll definitely include that list. (I might even add to it myself).


Holger Levsen wrote:
I'd suggest Eric puts this document under a proper licence (/me suggests 
GPL2+, just add another appendix add the bottom with the licence text...) and 
then hopefully everybody is happy to add/edit content :-)
  

Will do!


Thanks Franklin and Holger!
- Eric


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Illustrated Guide to Installing Debian GNU/Linux

[Eric Doviak]

At Holger's suggestion, I placed the "Illustrated Guide to Installing
Debian" on the Debian Wiki[1].

The text is pretty much the same, but I made some changes so that it
would be appropriate for Debian documentation (e.g. removing the word
"I," removing my opinions, etc.). At Praveen's suggestion, I also
recommended that users install the "icedtea-gcjwebplugin" (which uses
OpenJDK) instead of "java-gcj-compat-plugin."

I'm not sure what the next step is here, so please let me know what
else I can do/should do to help.

Enjoy!,
- Eric

[1] http://wiki.debian.org/LennyIllustratedInstall


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Illustrated Guide to Installing Debian GNU/Linux

[Eric Doviak]

Dear Debian Installer Team,

Congratulations on the recent release of Debian Lenny.

I would also like to tip my hat to the people who worked on the installation
guide[1] and its translations into 16 languages. They did a fantastic job.
The comprehensive nature of that 141-page guide is invaluable to anyone who
has to perform a complex and/or uncommon task (such as using TFTP to boot a
computer over a network from another machine).

The trouble with comprehensiveness is that it frightens a new user who is
simply trying to set up a home desktop. For them, Debian's official
installation guide is not a good introduction to Debian and it is completely
at odds with the spirit of projects like Robert Millan's
Goodbye-Microsoft.com[2], where the goal is to provide the simplest possible
transition from MS Windows to Debian GNU/Linux.

For people who are new to GNU/Linux and are simply trying to install Debian
on a home desktop, I wrote an "Illustrated Guide to Installing Debian
GNU/Linux."[3]

The guide is 10 pages long and is filled with screenshots (to make the user
feel comfortable). To add a touch of comprehensiveness, I also included 12
pages of appendices to help them select partition sizes, introduce them to
package management, etc.

When I wrote the guide, I had the users of Goodbye-Microsoft.com in mind, so
I submitted it to Robert Millan, who asked me to send it to you.

I never intended to create an official Debian document, but -- if you think
that it is of good quality -- I would be happy to help you turn it into one
("source code"[4] and all 73 screenshots[5]).

Let me know what you think of the documents and please let me know what I
can do to help make Debian more friendly to new users.

Thanks,
- Eric Doviak


[1] http://www.debian.org/releases/stable/installmanual
[2] http://goodbye-microsoft.com/
[3] http://www.doviak.net/debian/debian_install_guide.pdf
[4] http://www.doviak.net/debian/debian_install_guide.tar.gz
[5] http://www.doviak.net/debian/debian_install_shots.tar.gz

Re: Bug#509937: installation-guide-i386: suggested image for memory-stick booting does not contain network drivers

[Eric Cooper]

On Mon, Feb 16, 2009 at 09:40:08PM +0100, Frans Pop wrote:
> Did you actually copy a CD image (ISO file) onto the USB stick?
> Exactly what image did you copy?

You're right -- I completely skipped that.  Somehow I must have
thought everything was in the boot.img.gz file.  
In my defense, there is some misleading language in the 4.3.1
paragraph:
"all-in-one file" ... "contains all the installer files ..."
"To use this image you *only* have to extract it directly to your
USB stick" (emphasis mine)

I suggest changing "only" to "first".  And perhaps the paragraph
beginning "After that, mount the USB memory stick " could be
emphasized somehow (bold face or whatever).

Anyway, sorry for the noise, and thanks and congratulations for the
lenny release.

-- 
Eric Cooper e c c @ c m u . e d u


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Bug#509937: installation-guide-i386: suggested image for memory-stick booting does not contain network drivers

[Eric Cooper]

On Mon, Feb 16, 2009 at 08:02:04PM +0100, Frans Pop wrote:
> This has absolutely nothing to do with this bug report! Please report your 
> issue separately, but first verify that you are doing things correctly.
> 
> hd-media/boot.img.gz indeed does not contain any net drivers: it does not 
> need them! They get loaded later during the installation.

I booted from the memory stick, and chose the basic install.  After
searching the local disks, it reported that it couldn't find any ISO
images and said I'd have to net boot (fine).  I continued, and it
attempted to set up networking, which failed because it couldn't
discover any networking hardware. At that point, I assumed (maybe
incorrectly) I wouldn't be able to net boot, because the only menu
choices were to go back and re-try what I had already tried.

> You are simply not using the installer correctly.

If there was something else I was supposed to do, it certainly wasn't
obvious.

By comparison, I wiped that memory stick and recreated it the "hard
way" using syslinux and the linux and initrd images from the
netboot/debian-installer directory.  That worked fine.

-- 
Eric Cooper e c c @ c m u . e d u


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#509937: installation-guide-i386: suggested image for memory-stick booting does not contain network drivers

[Eric Cooper]

Package: installation-guide-i386
Version: lenny
Followup-For: Bug #509937

Section 4.3.1 ("Copying the files -- the easy way") says:
There is an all-in-one file hd-media/boot.img.gz which contains
all the installer files (including the kernel) as well as syslinux
and its configuration file.

As far as I can tell, this image does not contain any network drivers.
At least, the installer on this image could not detect the Intel
Gigabit Ethernet hardware on my box (which the etch installer had no
problem with).  There is no /lib/modules/.../drivers/net subdirectory,
and there doesn't appear to be any compiled-in support in the kernel
either.

-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (400, 'unstable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#497478: Lenny Installer on Intel D945GCLF based system does a Kernel Oops

[Eric A. Cottrell]

Jérémy Bobbio wrote:

On Mon, Sep 01, 2008 at 07:31:28PM -0400, Eric A. Cottrell wrote:
  
I am testing the Lenny weekly build 2008-09-01 and the installer fails 
to detect the on-board Realtek network adapter.  Manual selection of
the r8169 driver does not work.  If I skip the network portion and 
manually configure the network after installation the network card

is detected and works.



Could you try a daily built image?  In order to test support for you
network card, a netboot mini.iso [1] should do it.

[1] http://people.debian.org/~joeyh/d-i/images/daily/netboot/mini.iso

Please note that due to #497619, ext3 filesystems can't be used to
perform an installation right now.

Cheers,
  

Hello,

I burnt the iso in the link you provided today and it works.  It 
detected the network, configured the network, and downloaded the 
packages off the network.  I did not do a complete install.


I found information that the r8169 driver in recent kernels (2.6.24, 
2.6.25) does not work with the Realtek eithernet chip used on this 
motherboard.  The r8169 driver bugs were fixed in the 2.6.26 version of 
the kernel.


73 Eric



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#497478: Lenny Installer on Intel D945GCLF based system does a Kernel Oops

[Eric A. Cottrell]

eate_link+0xa3/0xe5
Sep  1 18:29:03 kernel:  [] netlink_broadcast+0x24a/0x28a
Sep  1 18:29:03 kernel:  [] kobject_get+0xf/0x13
Sep  1 18:29:03 kernel:  [] pci_device_probe+0x36/0x57
Sep  1 18:29:03 kernel:  [] driver_probe_device+0xdd/0x15a
Sep  1 18:29:03 kernel:  [] klist_next+0x46/0x61
Sep  1 18:29:03 kernel:  [] __driver_attach+0x0/0x75
Sep  1 18:29:03 kernel:  [] __driver_attach+0x44/0x75
Sep  1 18:29:03 kernel:  [] bus_for_each_dev+0x39/0x5b
Sep  1 18:29:03 kernel:  [] driver_attach+0x16/0x18
Sep  1 18:29:03 kernel:  [] __driver_attach+0x0/0x75
Sep  1 18:29:03 kernel:  [] bus_add_driver+0x6d/0x197
Sep  1 18:29:03 kernel:  [] __pci_register_driver+0x3e/0x6a
Sep  1 18:29:03 kernel:  [] sys_init_module+0x1303/0x140d
Sep  1 18:29:03 kernel:  [] disable_irq+0x0/0x1d
Sep  1 18:29:03 kernel:  [] syscall_call+0x7/0xb
Sep  1 18:29:03 kernel:  ===
Sep  1 18:29:03 kernel: Code: 85 c0 79 23 b9 2d 24 30 c0 31 d2 b8 76 d4 31 c0 89 1c 24 c7 44 24 04 c4 1d 3f c0 e8 3b b3 ee ff eb 05 b8 ed ff ff ff 5a 59 5b c3 <8b> 90 b8 00 00 00 85 d2 75 0a 8b 90 b4 00 00 00 85 d2 74 03 8b 
Sep  1 18:29:03 kernel: EIP: [] dev_driver_string+0x0/0x29 SS:ESP 0068:f4c19da8

Sep  1 18:29:03 kernel: ---[ end trace 15e601a22412a35a ]---
Sep  1 18:29:03 udevd-event[6599]: run_program: '/sbin/modprobe' abnormal exit
Sep  1 18:29:11 net/hw-detect.hotplug: Detected hotpluggable network interface 
lo
Sep  1 18:29:25 main-menu[1256]: INFO: Falling back to the package description 
for auto-install
Sep  1 18:29:25 main-menu[1256]: INFO: Falling back to the package description 
for ai-choosers
Sep  1 18:29:25 main-menu[1256]: INFO: Menu item 'save-logs' selected

73 Eric




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#484121: tasksel: let's sync on the GNOME task

[Eric Dorland]

* Mike Hommey ([EMAIL PROTECTED]) wrote:
> On Wed, Jun 25, 2008 at 03:48:32AM -0400, Eric Dorland <[EMAIL PROTECTED]> 
> wrote:
> > * Mike Hommey ([EMAIL PROTECTED]) wrote:
> > > On Tue, Jun 24, 2008 at 03:25:08AM -0400, Eric Dorland wrote:
> > > > * Joey Hess ([EMAIL PROTECTED]) wrote:
> > > > > Eric Dorland wrote:
> > > > > > Well I think Google generally does treat the Iceweasel user agent
> > > > > > properly.
> > > > > 
> > > > > Not in the case of maps.google.com, where the sidebar cannot be hidden
> > > > > in iceweasel, can in firefox.
> > > > > 
> > > > > > > I'm afraid that documenting it in README.Debian won't help 
> > > > > > > desktop users
> > > > > > > who just find that this strange "iceweasel" browser we install by
> > > > > > > default doesn't work on sites that firefox works on.
> > > > > > 
> > > > > > Could we do it in a more prominent perhaps?  
> > > > > 
> > > > > FWIW, I got from the README.Debian to #354622, but I was unable to 
> > > > > from
> > > > > there figure out how to quickly and easily change the user agent.
> > > > > 
> > > > > A more prominent thing might be a hyperlink directly to the relevant
> > > > > about:config setting from the default start page .. or a pre-installed
> > > > > user agent switcher that has firefox in it as an option. I think that
> > > > > something like that would go a certian distance to making it 
> > > > > accessible
> > > > > to users, though it would still be a bother.
> > > > 
> > > > I thought about this this week and I've come to agree with Joey's
> > > > position.
> > > > 
> > > > We could document exactly how to change the useragent for the user,
> > > > but why wouldn't they do this? From there perspective there are all
> > > > upsides and no downsides to making the useragent be Firefox, And if
> > > > everyone is going to mechanically change it (or want to change it),
> > > > then it's not really a good default.
> > > > 
> > > > While I agree that websites shouldn't be abusing useragent strings the
> > > > way they do, we can't win this fight on our own and in the mean time
> > > > our users are getting broken results that are in our power to fix.
> > > > 
> > > > Thoughts?
> > > 
> > > We have plenty other browsers that are not Firefox and don't try to
> > > claim to be Firefox...
> > 
> > In the case of Iceweasel it is in fact 99.9% Firefox, so claiming it's
> > Firefox isn't much of a stretch.
> 
> In the case of kazehakase, galeon and epiphany, rendering-wise, it is
> also 99.9% Firefox. Do you suggest they replace their user-agent, too?

Possibly. It should at least be an option to work around broken
sites. 
 
> > As much as we would like it not to be so, even people who should know
> > better are not handling non-Firefox useragent strings correctly. We
> > can present the user with documentation on how to change the useragent
> > string, but why wouldn't they change it? There's no downside from
> > there perspective, sites just work better. If the user should always
> > set this themselves, then it should be the default.
> 
> The fact is users don't *always* have to set this, because far from all
> websites require it. If so many users were impacted, we would be drowned
> under piles of bug reports about this issue, yet, there is only a few of
> them (only one, iirc). With concerning issues, we usually get much more,
> especially when they are longstanding issues.

Most sites do work. But the breakages are subtle and just reinforces
the perception that Iceweasel is inferior to Firefox.

I feel like I keep reiterating this but i think it's the central
point. If we took J. Random Debian User and sat them down and
explained you can have User-Agent Iceweasel or Firefox and explained
the pros and cons to them which would the pick? From their perspective
there is no downside to using "Firefox". So shouldn't we represent
their interests in this?

> Finally, for those sites that do bad user agent sniffing, there is a a
> "Report Broken Site" item in the Help menu that users can use (though I
> haven't verified if unbranding didn't break it).

What does that do exactly? Send a report to mozilla? Will they
actually put pressure on websites to fix this?


-- 
Eric Dorland <[EMAIL PROTECTED]>
ICQ: #61138586, Jabber: [EMAIL PROTECTED]



signature.asc
Description: Digital signature

Bug#484121: tasksel: let's sync on the GNOME task

[Eric Dorland]

* Mike Hommey ([EMAIL PROTECTED]) wrote:
> On Tue, Jun 24, 2008 at 03:25:08AM -0400, Eric Dorland wrote:
> > * Joey Hess ([EMAIL PROTECTED]) wrote:
> > > Eric Dorland wrote:
> > > > Well I think Google generally does treat the Iceweasel user agent
> > > > properly.
> > > 
> > > Not in the case of maps.google.com, where the sidebar cannot be hidden
> > > in iceweasel, can in firefox.
> > > 
> > > > > I'm afraid that documenting it in README.Debian won't help desktop 
> > > > > users
> > > > > who just find that this strange "iceweasel" browser we install by
> > > > > default doesn't work on sites that firefox works on.
> > > > 
> > > > Could we do it in a more prominent perhaps?  
> > > 
> > > FWIW, I got from the README.Debian to #354622, but I was unable to from
> > > there figure out how to quickly and easily change the user agent.
> > > 
> > > A more prominent thing might be a hyperlink directly to the relevant
> > > about:config setting from the default start page .. or a pre-installed
> > > user agent switcher that has firefox in it as an option. I think that
> > > something like that would go a certian distance to making it accessible
> > > to users, though it would still be a bother.
> > 
> > I thought about this this week and I've come to agree with Joey's
> > position.
> > 
> > We could document exactly how to change the useragent for the user,
> > but why wouldn't they do this? From there perspective there are all
> > upsides and no downsides to making the useragent be Firefox, And if
> > everyone is going to mechanically change it (or want to change it),
> > then it's not really a good default.
> > 
> > While I agree that websites shouldn't be abusing useragent strings the
> > way they do, we can't win this fight on our own and in the mean time
> > our users are getting broken results that are in our power to fix.
> > 
> > Thoughts?
> 
> We have plenty other browsers that are not Firefox and don't try to
> claim to be Firefox...

In the case of Iceweasel it is in fact 99.9% Firefox, so claiming it's
Firefox isn't much of a stretch.

As much as we would like it not to be so, even people who should know
better are not handling non-Firefox useragent strings correctly. We
can present the user with documentation on how to change the useragent
string, but why wouldn't they change it? There's no downside from
there perspective, sites just work better. If the user should always
set this themselves, then it should be the default.

-- 
Eric Dorland <[EMAIL PROTECTED]>
ICQ: #61138586, Jabber: [EMAIL PROTECTED]



signature.asc
Description: Digital signature

Bug#484121: tasksel: let's sync on the GNOME task

[Eric Dorland]

* Joey Hess ([EMAIL PROTECTED]) wrote:
> Eric Dorland wrote:
> > Well I think Google generally does treat the Iceweasel user agent
> > properly.
> 
> Not in the case of maps.google.com, where the sidebar cannot be hidden
> in iceweasel, can in firefox.
> 
> > > I'm afraid that documenting it in README.Debian won't help desktop users
> > > who just find that this strange "iceweasel" browser we install by
> > > default doesn't work on sites that firefox works on.
> > 
> > Could we do it in a more prominent perhaps?  
> 
> FWIW, I got from the README.Debian to #354622, but I was unable to from
> there figure out how to quickly and easily change the user agent.
> 
> A more prominent thing might be a hyperlink directly to the relevant
> about:config setting from the default start page .. or a pre-installed
> user agent switcher that has firefox in it as an option. I think that
> something like that would go a certian distance to making it accessible
> to users, though it would still be a bother.

I thought about this this week and I've come to agree with Joey's
position.

We could document exactly how to change the useragent for the user,
but why wouldn't they do this? From there perspective there are all
upsides and no downsides to making the useragent be Firefox, And if
everyone is going to mechanically change it (or want to change it),
then it's not really a good default.

While I agree that websites shouldn't be abusing useragent strings the
way they do, we can't win this fight on our own and in the mean time
our users are getting broken results that are in our power to fix.

Thoughts?

-- 
Eric Dorland <[EMAIL PROTECTED]>
ICQ: #61138586, Jabber: [EMAIL PROTECTED]



signature.asc
Description: Digital signature

Re: Considerations for lilo removal

[Eric Pozharski]

On Mon, Jun 16, 2008 at 11:19:03AM +0200, Mike Hommey wrote:
*SKIP*

> OTOH, aren't most of these choosing lilo over grub only doing so by
> habit ?

OTOH, aren't most of theses choosing emacs over vim only doing so by
habit?

-- 
Torvalds' goal for Linux is very simple: World Domination


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#484121: tasksel: let's sync on the GNOME task

[Eric Dorland]

* Joey Hess ([EMAIL PROTECTED]) wrote:
> Eric Dorland wrote:
> > So the user agent thing is fairly well documented at
> > http://bugs.debian.org/399633, but basically it's our stand against
> > user-agent insanity. We could of course make it say Firefox easily,
> > but this certainly seems a bit defeatist.
> 
> s/defeatist/defeated/
> 
> I realized this battle was over when discussion on debian-user revieled
> that google maps behaved differently in firefox than iceweasel, because it
> used a firefox-UA specific test to enable a feature (closing the sidebar
> to make the map take up the full screen).
> 
> If the top website out there gets it "wrong", the battle is effectively 
> over; "right" or "wrong" no longer really matters (victors write history
> etc).

Well I think Google generally does treat the Iceweasel user agent
properly. Not everyone understands these issues as well as they
should, mistakes get made. I mean we could set the User-Agent to IE
like some other browsers do, that would make more sites work.
 
> > I think we should almost
> > certainly document the workaround better in the README.Debian. Of
> > course I highly respect Joey's opinion so I'm open to more
> > convincing. 
> 
> I'm afraid that documenting it in README.Debian won't help desktop users
> who just find that this strange "iceweasel" browser we install by
> default doesn't work on sites that firefox works on.

Could we do it in a more prominent perhaps?  


-- 
Eric Dorland <[EMAIL PROTECTED]>
ICQ: #61138586, Jabber: [EMAIL PROTECTED]



signature.asc
Description: Digital signature

Bug#484121: tasksel: let's sync on the GNOME task

[Eric Dorland]

[+pkg-mozilla-maintainers]

* Joey Hess ([EMAIL PROTECTED]) wrote:
> Josselin Mouette wrote:
> > Le mardi 03 juin 2008 à 10:24 -0300, Otavio Salvador a écrit :
> > > I think providing multiple alternatives for same task confuses the user.
> > 
> > Cool, are you finally willing to drop iceweasel from the gnome-desktop
> > task then?
> 
> I won't try to argue with gnome people about more choices confusing
> users. You've drunk that cool-aide too. ;-)
> 
> I'd *love* to not have two browsers in the desktop task.
> The reasons firefox was originally included were:
> 
> - Name-brand recognition. Now eliminated by the mozilla project.
> - Vast number of plugins and other market-share advantages.
> - Some sites only work with MSIE and firefox. Or that have some features
>   that only work with browsers claiming to be these. (Including google
>   maps.) Horrible but true. This advantage also eliminated from iceweasel
>   to the sad detriment of many of our users. (#401507)
> - Not wanting users to have to go manually install it, especially as
>   a somewhat scarily large fraction apparently install it by downloading
>   a tarball.
> 
> On the balance, most of the reasons to install iceweasel by default have
> withered away. A few still remain, and the user-agent problem is really
> a bug in iceweasel, that should be RC IMHO[1]. I had been hoping that it
> would be fixed. If it continues to not be fixed, I'll continue to
> unhappily lean toward dropping iceweasel from the task.

So the user agent thing is fairly well documented at
http://bugs.debian.org/399633, but basically it's our stand against
user-agent insanity. We could of course make it say Firefox easily,
but this certainly seems a bit defeatist. I think we should almost
certainly document the workaround better in the README.Debian. Of
course I highly respect Joey's opinion so I'm open to more
convincing. 

As to whether to include Iceweasel over epiphany (or whatever) in the
gnome task, that's probably the gnome team's call. However, Iceweasel
is clearly the more popular one and 3.0 does have better integration
with Gnome (at least look at feel wise).

-- 
Eric Dorland <[EMAIL PROTECTED]>
ICQ: #61138586, Jabber: [EMAIL PROTECTED]



signature.asc
Description: Digital signature

business card vga=790

[Eric Reinbold]

hello,

i installed debian testing on bussiness card in vga=790 (other is the
same, 771, 791...)
the installation is ok, but after reboot the vga is normal (640x480).
it says: try the 8139too driver

thank for all

auzain


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[sun]debian : Install

[Eric Rapilly]

hello ! I downloaded plenty of files,
i.e :/net/download/debian-testing-sparc-CD-1.iso
to  /net/download/debian-testing-sparc-CD-21.iso
and also the same with "jigdo" 
What is the purpose of jigdo ? 
How to install all thes file on the sun? I will indeed write a cdrom ,
but after this , what shall I do ? many thanks





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[sun]debian

[Eric Rapilly]

hello, I want to know which version of Debian I shoiuld download for my
Sun Ultra 1, where I can download it , and please laso how to install
It . thanks !!



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[sun]debian

[Eric Rapilly]

hello, guys. sorry to disturb you. I want to know which debian I may
install on my SUN Ultra one, with only two 2.17 Go HD, and few memory.
And also where I can download it Thanks. 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#414367: Sony VAIO z505-js succesful install

[Eric]

Package: installation-reports
 
Boot method: Floppy, the Sarge disk images detected the USB Floppy just fine

Image version: /debian/dists/sarge/main/installer-i386/current//images
4-Aug-2006
Date: 3/10/2007 2AM
 
Machine: Sony VAIO Z505-JS Super Slim note book with no CD-ROM and USB
Floppy   
Processor:645MHZ pentiumIII
Memory:128 MB
Partitions: 4.8GB Windows  7.0 GB ext3  255MB Swap
 
Output of lspci and lspci -n:
 
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
 
Initial boot worked:[ o]
Configure network HW:   [ o]
Config network: [ o]
Detect CD:  [ ]
Load installer modules: [ o]
Detect hard drives: [ o]
Partition hard drives:  [ o]
Create file systems:[ o]
Mount partitions:   [ o]
Install base system:[ o]
Install boot loader:[ o]
Reboot: [ o]
 
Comments/Problems:
 
I was a little surprised after what I’d found about my specific laptop and
installing
Debian on the internet the It went so smoothly. I was expecting the initial
boot to stall 
When changing floppies, and was pleasantly surprised that it finished
booting.  It downloaded
>From the ftp sight and seems to work just fine.




-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.8/717 - Release Date: 3/10/2007
2:25 PM
 

Bug#414344: Sarge with SATA - failure

[Eric David Fielding]

Package: installation-reports
Boot method: DVD
Image version: Sarge
Date: A week ago
Machine: Brand new Core 2 Duo
Hard Drive: SATA
MB = ASUS P5L-MX
Booted fine off DVD but did not see onboard ethernet nor SATA




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410022: installation report

[Eric Streit]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: installation-reports

Boot method: CD and dvd
Image version: http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd
http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-dvd
Date: the 6th of february

Machine: Asus P5W motherboard, Intel core 2 duo 6600 processor, 2GOs of ram
Processor: Core2duo 6600
Memory:2Go
Partitions:
Sys. de fich. Type1K-blocs   Occupé Disponible Capacité Monté sur
/dev/sda5 ext3 9614116   5053468   4072276  56% /
tmpfstmpfs 1038236 0   1038236   0% /lib/init/rw
udev tmpfs   10240   112 10128   2% /dev
tmpfstmpfs 1038236 0   1038236   0% /dev/shm
/dev/sda1 ext3   90297 11471 74009  14% /boot
/dev/sda2 vfat1952547216  19525456   1% /dos
/dev/sda6 ext328834716   3989416  23380576  15% /home
/dev/sda8 ext3   237873536527780 225262468   1% /mnt/pool
/dev/sda9 ext310096236   1838076   7745288  20% /mnt/ubuntu

Output of lspci -nn and lspci -vnn:
 lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 975X Express Memory
Controller Hub  [8086:277c] (rev c0)
00:01.0 PCI bridge [0604]: Intel Corporation 975X Express PCI Express
Root Port [8086:277d] (rev c0)
00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High
Definit ion Audio Controller [8086:27d8] (rev 01)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI
Express Po rt 1 [8086:27d0] (rev 01)
00:1c.3 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI
Express Po rt 4 [8086:27d6] (rev 01)
00:1c.4 PCI bridge [0604]: Intel Corporation 82801GR/GH/GHM (ICH7
Family) PCI Ex press Port 5 [8086:27e0] (rev 01)
00:1c.5 PCI bridge [0604]: Intel Corporation 82801GR/GH/GHM (ICH7
Family) PCI Ex press Port 6 [8086:27e2] (rev 01)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family)
USB UHCI # 1 [8086:27c8] (rev 01)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family)
USB UHCI # 2 [8086:27c9] (rev 01)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family)
USB UHCI # 3 [8086:27ca] (rev 01)
00:1d.3 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family)
USB UHCI # 4 [8086:27cb] (rev 01)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family)
USB2 EHCI Controller [8086:27cc] (rev 01)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge
[8086:244e] (rev e 1)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family)
LPC Interf ace Bridge [8086:27b8] (rev 01)
00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE
Control ler [8086:27df] (rev 01)
00:1f.2 IDE interface [0101]: Intel Corporation 82801GB/GR/GH (ICH7
Family) Seri al ATA Storage Controller IDE [8086:27c0] (rev 01)
00:1f.3 SMBus [0c05]: Intel Corporation 82801G (ICH7 Family) SMBus
Controller [8 086:27da] (rev 01)
01:01.0 Multimedia video controller [0400]: Brooktree Corporation Bt878
Video Ca pture [109e:036e] (rev 11)
01:01.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio
Capture [109e:0878] (rev 11)
01:03.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB22/A
IEEE-1394a-20 00 Controller (PHY/Link) [104c:8023]
02:00.0 IDE interface [0101]: JMicron Technologies, Inc. JMicron
20360/20363 AHC I Controller [197b:2363] (rev 02)
02:00.1 IDE interface [0101]: JMicron Technologies, Inc. JMicron
20360/20363 AHC I Controller [197b:2363] (rev 02)
03:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd.
88E8053 PCI-E Gigabit Ethernet Controller [11ab:4362] (rev 20)
04:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd.
88E8053 PCI-E Gigabit Ethernet Controller [11ab:4362] (rev 20)
06:00.0 VGA compatible controller [0300]: ATI Technologies Inc Unknown
device [1 002:724b]
06:00.1 Display controller [0380]: ATI Technologies Inc Unknown device
[1002:726 b]

 lspci -vnn
00:00.0 Host bridge [0600]: Intel Corporation 975X Express Memory
Controller Hub [8086:277c] (rev c0)
Subsystem: ASUSTeK Computer Inc. Unknown device [1043:8178]
Flags: bus master, fast devsel, latency 0
Capabilities: 

00:01.0 PCI bridge [0604]: Intel Corporation 975X Express PCI Express
Root Port [8086:277d] (rev c0) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
I/O behind bridge: c000-cfff
Memory behind bridge: ff90-ff9f
Prefetchable memory behind bridge: cff0-efef
Capabilities: 

00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High
Definition Audio Controller [8086:27d8] (rev 01)
Subsystem: ASUSTeK Computer Inc. Unknown device [1043:81d8]
Flags: bus master, fast devsel, latency 0, IRQ 177
Memory at ffafc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: 

00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (I

Bug#297536: installation-guide-powerpc: netbooting from open firmware

[Eric Cooper]

Package: installation-guide-powerpc
Version: http://d-i.alioth.debian.org/manual/en.powerpc/ch05s01.html
Followup-For: Bug #297536

On my gray & white G4, I had to use the OF command
   boot enet:0,yaboot
instead of just "boot enet:0" as specified in the manual.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#408408: installation-guide-i386: possible typo in "Submitting Installation Reports"

[Eric Cooper]

Package: installation-guide-i386
Version: http://d-i.alioth.debian.org/manual/en.i386
Severity: normal

Section ch05s03.html#submit-bug says:
run the command reportbug installation-report
Shouldn't this be
run the command reportbug installation-reports

i.e., against the installation-reports pseudo-package, not the actual
installation-report package?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#407492: Add ieee80211_crypt_wep for use during install

[Eric Work]

Package: debian-installer
Version: etch rc1 netinstall

I am trying to use the bcm43xx module during installation for "Debian 
Etch Rc1 NetInstall" but I am unable to since module ieee80211_crypt_wep 
is not available.  This is required to access networks which require WEP 
using the BCM43XX based cards.  Also it would be nice to have the 
related wpa modules available but it seems the installer doesn't handle 
that right now.


My system does not have a wired ethernet card so I need wireless access 
to install with the latest packages.  To prepare the system I put the 
firmware, which was previously extracted using a livecd, on a USB memory 
stick.  I then switch to tty2 right after the installed boots (before hw 
detection) and copy the files to /lib/firmware as needed.  When the 
installer gets to the network setup it finds the card with no problem 
and even finds the network on its own.


As a workaround for not using WEP, I setup my powerbook as an access 
point with no required WEP key then manually specified the network 
settings.  After doing this I was able to update apt source and install 
the latest packages.


What are the chances of getting this module included in the next release?



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Debian has failed us

[Eric Cooper]

On Thu, Jan 11, 2007 at 07:18:24PM +0100, Frans Pop wrote:
> [...]
> False: it was not compiled into the standard Debian kernel. The installer
> does not use custom kernels. This was explained to you at the time.
> [...]
> Please check your facts before sending such mails:
> [...] 
> I'll ignore the rest of your rant as it is obviously based on false
> assumptions.
> [...]

This is an incredibly arrogant and hostile response to a long-time,
technically competent Debian user who posted a calm and informative
message.

> P.S. Some apologies would be appreciated.

On the contrary, he attacked nobody personally, and his tone was not
inflammatory. Your response made an unfortunate situation worse.  It's
you who should apologize.

-- 
Eric Cooper e c c @ c m u . e d u


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#397920: installation-reports

[Eric Ristad]

Package: installation-reports

Boot method: network
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso
Date: 11/06/2006

Machine: Dell Dimension 8400
Processor: 3.0GHz P4 5300 800FSB
Memory: 4GB DDR2 533Mhz
Partitions: 

> df -Tl
FilesystemType   1k-blocks  Used Available Use% Mounted on
/dev/hda1 ext212413032   9076952   2705532  78% /

Output of lspci -nn and lspci -vnn:


> lspci -nn
00:00.0 Class 0600: 1106:0691 (rev c2)
00:01.0 Class 0604: 1106:8598
00:04.0 Class 0601: 1106:0596 (rev 12)
00:04.1 Class 0101: 1106:0571 (rev 06)
00:04.2 Class 0c03: 1106:3038 (rev 08)
00:04.3 Class 0600: 1106:3050 (rev 20)
00:0a.0 Class 0200: 8086:1229 (rev 0c)
00:0b.0 Class 0200: 8086:1229 (rev 08)
00:0c.0 Class 0401: 1274:1371 (rev 07)
01:00.0 Class 0300: 102b:0525 (rev 04)

> lspci -vnn
00:00.0 Class 0600: 1106:0691 (rev c2)
Subsystem: 1043:8017
Flags: bus master, medium devsel, latency 0
Memory at d000 (32-bit, prefetchable)
Capabilities: 

00:01.0 Class 0604: 1106:8598
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: cc80-cdcf
Prefetchable memory behind bridge: cdf0-cfff
Capabilities: 

00:04.0 Class 0601: 1106:0596 (rev 12)
Subsystem: 1043:8017
Flags: bus master, stepping, medium devsel, latency 0

00:04.1 Class 0101: 1106:0571 (rev 06) (prog-if 8a [Master SecP PriP])
Flags: bus master, stepping, medium devsel, latency 32
I/O ports at d800

00:04.2 Class 0c03: 1106:3038 (rev 08)
Subsystem: 0925:1234
Flags: bus master, medium devsel, latency 32, IRQ 9
I/O ports at d400

00:04.3 Class 0600: 1106:3050 (rev 20)
Flags: medium devsel

00:0a.0 Class 0200: 8086:1229 (rev 0c)
Subsystem: 8086:0040
Flags: bus master, medium devsel, latency 32, IRQ 5
Memory at cc00 (32-bit, non-prefetchable)
I/O ports at d000
Memory at cb80 (32-bit, non-prefetchable)
Capabilities: 

00:0b.0 Class 0200: 8086:1229 (rev 08)
Subsystem: 8086:000c
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at cb00 (32-bit, non-prefetchable)
I/O ports at b800
Memory at ca80 (32-bit, non-prefetchable)
Capabilities: 

00:0c.0 Class 0401: 1274:1371 (rev 07)
Subsystem: 1274:8001
Flags: bus master, slow devsel, latency 32, IRQ 11
I/O ports at b400
Capabilities: 

01:00.0 Class 0300: 102b:0525 (rev 04)
Subsystem: 102b:0338
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at ce00 (32-bit, prefetchable)
Memory at cd00 (32-bit, non-prefetchable)
Memory at cc80 (32-bit, non-prefetchable)
Expansion ROM at cdff [disabled]
Capabilities: 


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:[E]

Comments/Problems:

Failed to detect maximum LCD monitor resolution correctly for Samsung
SyncMaster 243T.  Installation put the maximum resolution as 1600x1200
instead of 1920x1200.  I had to manually edit the xorg.conf file to
add the 1920x1200 option.

This is by far the fastest, easiest, and least painful operating
system installation that I have *ever* experienced in my 20+ year
career of installing operating systems.  I kept waiting for something
to go wrong and it never did!!!  I have also installed this release on
an HP DL145 w/ Opterons w/o any problems.  CONGRATULATIONS ON AN
AMAZING ACCOMPLISHMENT!  Long live Debian!



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#396482: [Fwd: Re: Installing Debian amd64 on an asus P5W DH Deluxe + E6600 : kernel on installer broken + bugs in d-i when changing kernel + modules]

[Eric Valette]

At least include full message => Franz is ok to fix it and at least it
would be consistent with the other modprobe calls in other SXX init
scripts (e.g. ACPI, udev, video, ...)

-- eric
--- Begin Message ---
On Wednesday 01 November 2006 01:05, Eric Valette wrote:
> Found the culprit : S61mouse-support-x86 is incorrectly written  : it
> does not use -q option for modeprobe not the || true.

Nice job of tracing that!

The installer is not really set up to work with kernels that are 
configured totally different from the standard Debian kernels.

If you really have a totally different kernel, you may run into other 
issues as well later on in the installation.

> Will fill a bug because it almost prevent to easilly upgrade to a
> newer/better configured kernel.

Note that "better configured" is a subjective opinion.
For the installer, it is much better (or at least safer) to start with the 
configuration the Debian kernel uses. How you configure the kernel for 
your installed system is of course completely up to you.

This particular issue is fairly easily avoided, so I have no problem with 
fixing it. Please file your bug report against the package rootskel-gtk.

Cheers,
FJP


pgpJDYfXfa5Rn.pgp
Description: PGP signature
--- End Message ---

Bug#396482: installation-reports: S61mouse-support-x86 should use modprobe in the same way than other scripts (-q + || true)

[Eric Valette]

Geert Stappers wrote:

  Op 01-11-2006 om 01:07 schreef Eric Valette:
  
  
Using this version of the script make this system boot with a kernel where all modules are built-in

if [ "$DEBIAN_FRONTEND" = gtk ] ; then
modprobe -q evdev || true
modprobe psmouse || true
fi

  
  

Why modprobe another module when all modules are built-in?
(i.o.w. I don't understand the reason for this bugreport)

  

Because if the modules is not there and modprobe fails then you end up
with an endless loop. Besides all other call in the installer are made
this way.

-- eric





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Installing Debian amd64 on an asus P5W DH Deluxe + E6600 : kernel on installer broken + bugs in d-i when changing kernel + modules

[Eric Valette]

Frans Pop wrote:
> On Wednesday 01 November 2006 08:45, Eric Valette wrote:
>> BTW = I have written a script to update the installer to a new kernel
>> *almost* automatically. Interested in putting this somewhere?
> 
> Sure. Can you put it on a website somewhere? Then maybe first send a link 
> to it with some background info to the list for comments.
> After that we (or you yourself) can add it on the wiki below [1] 
> somewhere.
> 
> (I've just moved the existing instructions on how to create an image with 
> a modified kernel to the wiki.)


<http://eric.valette.free.fr/changeDebianInstallCDkernel.sh>

The patch that solved the infinite loop trying to load evdev and that is
referenced by the script is there

<http://eric.valette.free.fr/patch-debian-installer>

Comments welcome.

-- eric


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Installing Debian amd64 on an asus P5W DH Deluxe + E6600 : kernel on installer broken + bugs in d-i when changing kernel + modules

[Eric Valette]

Frans Pop wrote:
> On Wednesday 01 November 2006 01:05, Eric Valette wrote:
>> Found the culprit : S61mouse-support-x86 is incorrectly written  : it
>> does not use -q option for modeprobe not the || true.
> 
> Nice job of tracing that!

Want to use my new computer :-)


> The installer is not really set up to work with kernels that are 
> configured totally different from the standard Debian kernels.
> 
> If you really have a totally different kernel, you may run into other 
> issues as well later on in the installation.
> 
>> Will fill a bug because it almost prevent to easilly upgrade to a
>> newer/better configured kernel.
> 
> Note that "better configured" is a subjective opinion.

Sure. But for me this one at least works!. Was 2 AM. So I did not finish
the install. I boot into the gtk mode, an started to partition the disk.

Will report until I finish.

BTW = I have written a script to update the installer to a new kernel
*almost* automatically. Interested in putting this somewhere?

--eric



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#396482: installation-reports: S61mouse-support-x86 should use modprobe in the same way than other scripts (-q + || true)

[Eric Valette]

Package: installation-reports
Severity: normal

Using this version of the script make this system boot with a kernel where all 
modules are built-in

if [ "$DEBIAN_FRONTEND" = gtk ] ; then
modprobe -q evdev || true
modprobe psmouse || true
fi

-- System Information:
Debian Release: 4.0
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19-rc3-git5
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Installing Debian amd64 on an asus P5W DH Deluxe + E6600 : kernel on installer broken + bugs in d-i when changing kernel + modules

[Eric Valette]

Eric Valette wrote:
> Please CC me when anwsering: I'm not suscribed.
>
> 1) Did anybody else tried to replace a kernel with all drivers build in?
> Why did the "modprobe -q evdev ||true" fail? Has it anything to do with
> SMP support as the shell will probably spawn the two child on different
> proc but should receive exit status as on UP? Sound like a bug in d-i
> isn't it?

Found the culprit : S61mouse-support-x86 is incorrectly written  : it
does not use -q option for modeprobe not the || true.

Will fill a bug because it almost prevent to easilly upgrade to a
newer/better configured kernel.


-- eric


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#396480: installation-reports: D-I does not work on ASUS P5W DH de luxe + E6600

[Eric Valette]

Package: installation-reports
Severity: grave
Justification: renders package unusable

boot starts, but enter an endless loop resetting the SATA controller when it 
tries to find the disks. Also, dmesg shows spurious irq not handled on this 
hardware. Apparently fixed via the libata upgrade available in 2.6.18.x

-- System Information:
Debian Release: 4.0
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19-rc3-git5
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Installing Debian amd64 on an asus P5W DH Deluxe + E6600 : kernel on installer broken + bugs in d-i when changing kernel + modules

[Eric Valette]

Please CC me when anwsering: I'm not suscribed.

OK I knew this would be painful although I've installed debian on 
hundred of machines over the past ten years. No deception on this point.


At least I will report the actual status and seek for advices for 
finishing. What I did so far:


	1) Took a knoppix 5.01 DVD booted it. Works like a charm except the X 
nv driver. Defaults to vesa after some trials. Unfortunately kernel is 
2.6.15 and I need a SKY2 ethernet driver for my dual marvell Gigabit 
ethernet onbaord + I want to run in 64 bit mode. At least I noted the 
drivers used by doing an lsmod.
	2) Downloaded 
ftp://ftp.fr.debian.org/debian/dists/unstable/main/installer-amd64/20061022/images/gtk-miniiso
burned it and booted it. Starts well but hangs after a while because of 
spurious interrupts related to disk activities (SATA) endless reset of 
controller. Have also spurious irq listed in dmesg. Did not know if a 
kernel was correctly running on this mtherboard + CPU combination. So 
tried to find another instable AMD64 distrib.
	3) Downloaded the brand new opensuze 10.2 beta1 ISO because it includes 
almost all the up-to-date stuff. Booted installer. Works like a charm 
kernel wise.
	3) Downloaded 2.6.19-rc3-git5, configured it with all needed drivers IN 
+ SMP. Made a modules_install to get the module directory. Then replaced 
the kernel, replaced the /lib/modules by the correct modules directory 
in initrd.img, rebuild the CD iso. Booted it. Boots fine, no freeze, 
detected almost all hardware part necessary to installation (network, 
disks, DVD,s, ...). Unfortunately d-i fails with a series of error when 
trying to load evdev modules (that I have'nt because its compiled in). 
Found the scripts that tries to load the modules and saw that it is 
called like "modprobe -q evdev ||true" so do not know why it loops with 
an error.


So now I have some questions because I do not want to explore all the 
dead ends by myself if other s have already gone struggling this path.


1) Did anybody else tried to replace a kernel with all drivers build in? 
Why did the "modprobe -q evdev ||true" fail? Has it anything to do with 
SMP support as the shell will probably spawn the two child on different 
proc but should receive exit status as on UP? Sound like a bug in d-i 
isn't it?


2) If I recompile my kernel with all code as modules actually loaded 
with modprobe by d-i, will it have a change to work? I personnaly would 
prefer to comment all the modprobe in the scripts...


3) Shall I build the kernel without SMP? Is the installer known to be 
broken when using SMP kernel?


PS : the documentation to make the kind of trick like in 3) above is 
rather sparse. Finding the right cpio command to rebuild the initrd 
image is rather difficult! and the mkisofs command also. Annd  no I do 
not want to use the debvian scripts like bootcd or initrd-tools because 
its not convenient in my case.





-- eric


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#383866: first tests ...

[Eric Streit]

Package: installation-reports

Boot method: 
Image version: 
Date: 

Machine: 
Processor:centrino 1.6Ghz
Memory:521Mo
Partitions: <
[EMAIL PROTECTED]:~$ df -Tl
Sys. de fich. Type1K-blocs   Occupé Disponible Capacité Monté sur
/dev/hda3 ext328835220  22596944   4773528  83% /
tmpfstmpfs  258140 0258140   0% /dev/shm
/dev/hda1 ext3   28305 17790  9005  67% /boot
/dev/hda2 vfat14636968   5319184   9317784  37% /dos
/dev/hda6 ext313439048345876  12410508   3% /mnt/hda6
tmpfstmpfs   10240   732  9508   8% /dev


Output of lspci and lspci -n:
***
[EMAIL PROTECTED]:~$ lspci
:00:00.0 Host bridge: Intel Corp. 82855PM Processor to I/O
Controller (rev 03)
:00:01.0 PCI bridge: Intel Corp. 82855PM Processor to AGP Controller
(rev 03)
:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB
2.0 EHCI Controller (rev 01)
:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 81)
:00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller
(rev 01)
:00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA
Storage Controller (rev 01)
:00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
SMBus Controller (rev 01)
:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
:00:1f.6 Modem: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
AC'97 Modem Controller (rev 01)
:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250
Lf [Radeon Mobility 9000 M9] (rev 01)
:02:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
Controller (rev 80)
:02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 20)
:02:02.0 Network controller: Intel Corp. PRO/Wireless LAN 2100 3B
Mini PCI Adapter (rev 04)
:02:04.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus
Controller (rev 01)
[EMAIL PROTECTED]:~$

*

*
[EMAIL PROTECTED]:~$ lspci -n
:00:00.0 0600: 8086:3340 (rev 03)
:00:01.0 0604: 8086:3341 (rev 03)
:00:1d.0 0c03: 8086:24c2 (rev 01)
:00:1d.1 0c03: 8086:24c4 (rev 01)
:00:1d.2 0c03: 8086:24c7 (rev 01)
:00:1d.7 0c03: 8086:24cd (rev 01)
:00:1e.0 0604: 8086:2448 (rev 81)
:00:1f.0 0601: 8086:24cc (rev 01)
:00:1f.1 0101: 8086:24ca (rev 01)
:00:1f.3 0c05: 8086:24c3 (rev 01)
:00:1f.5 0401: 8086:24c5 (rev 01)
:00:1f.6 0703: 8086:24c6 (rev 01)
:01:00.0 0300: 1002:4c66 (rev 01)
:02:00.0 0c00: 1106:3044 (rev 80)
:02:01.0 0200: 10ec:8139 (rev 20)
:02:02.0 0280: 8086:1043 (rev 04)
:02:04.0 0607: 1524:1410 (rev 01)
[EMAIL PROTECTED]:~$

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

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

Comments/Problems:

1) test in graphical mode: the pointer of the mouse desappeared after
the first click (the messages on the console showed that he synaptic
touchpad was correctly detected)

2) I continue with the keyboard:
  the network cards were not correctly detected:
There is one ethernet (eth0) with RTL-8139/8139C/8139C+  and one
wifi
ipw2100 (intel).
The list was incorrect (the installer on etime detected the 
ttl8139 as eth1 and in a second run as eth0 (as it had to)
I could never enter the essid and wep key for my wifi card . The
modules didn't seem to exist in the kernel.
3) Entering the real name and passwords
It was impossible to enter the uppercase letters when typing my 
real
name. Only lower case letters ? and I don't know if it was  the same
with the passwords ... I could not go further as I  could 
not enter
the network parameters.


I will try with cable-ethernet ater

Bug#369793: installation-reports: net-retriever unable to fetch hw-detect-full

[Eric Van Buggenhaut]

On Sat, Jul 29, 2006 at 09:18 +0200, Geert Stappers wrote:
> On Thu, Jun 01, 2006 at 01:13:18PM +0200, Eric Van Buggenhaut wrote:
> > Package: installation-reports
> > Severity: critical
> > Justification: breaks the whole system
> > 
> > Boot method: USB stick
> > Image version: stable (Sarge)
> > Date:  June, 1st 2006 - 12AM GMT
> > 
> 
> > 
> > I'm trying to install Debian stable on a i386 box. Medium used is a USB 
> > stick.
> > 
> > Boot is OK. System hangs when downloading installer components at 
> > retrieving hw-detect-full with the message:
> > 
> > The installer failed to download a file from the mirror
> > 
> > Network connection is OK. I tried with +10 mirrors, same problem 
> > everywhere.
> 
> Where all mirrors tried at the same day?
> Could you retry today?
> 
> I'm asking because suspect the file was missing on the mirror(s)
> and I asume that the mirrors are okay now.

Yes, indeed. It works fine now.

-- 
Eric VAN BUGGENHAUT
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#369793: installation-reports: net-retriever unable to fetch hw-detect-full

[Eric Van Buggenhaut]

Package: installation-reports
Severity: critical
Justification: breaks the whole system

Boot method: USB stick
Image version: stable (Sarge)
Date:  June, 1st 2006 - 12AM GMT

Machine: i386 workstation
Processor: AMD Sempron
Memory: 512MB
Root Device: not detected
Partitions: no disk detected


Initial boot worked:[O] <¿Funcionó el arranque inicial?>
Configure network HW:   [O] <¿Se configuró el hardware de red?>
Config network: [O] <¿Se configuró la red?>
Detect CD:  [O] <¿Se detectó la unidad de CD?>
Load installer modules: [E] <¿Se cargaron los módulos del instalador?>
Detect hard drives: [E] <¿Se detectaron los discos duros?>
Partition hard drives:  [ ] <¿Se particionó el disco duro?>
Create file systems:[ ] <¿Se crearon los sistemas de ficheros?>
Mount partitions:   [ ] <¿Se montaron las particiones?>
Install base system:[ ] <¿Se instaló el sistema base?>
Install boot loader:[ ] <¿Se instaló el gestor de arranque?>
Reboot: [ ] <¿Reinició correctamente?>

I'm trying to install Debian stable on a i386 box. Medium used is a USB 
stick.

Boot is OK. System hangs when downloading installer components at 
retrieving hw-detect-full with the message:

The installer failed to download a file from the mirror

Network connection is OK. I tried with +10 mirrors, same problem 
everywhere.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#368633: partman: LVM automatic partitioning not undoable

[Eric Monson]

Package: partman
Severity: critical
Justification: causes serious data loss

I burned a D-I image for a friend (the latest weekly Debian CD as of Mar
12 15:12) and chose to play with it a bit to see if it was clearly
broken in some obvious way or likely okay for out purposes.

Once I had verified enough that I thought the build was fine (and It did
work for the install), I decided to try out the LVM option in the
"guided partitioning", since I had never done so before and I wanted to
see what how it would arrange the partitions.  The guided partitioning
page clearly states that you will have a chance to review and undo the
guided partitioning, and is correct for regular partitions, but LVM
occurs immeditely, it seems, and even gpart was unable to restore my
data.  I was able to salvage the python programs I had been working on,
but nothing else.

Since there is almost certainly a reason LVM gets applied immeditely,
most likely that cannot be changed, but I am of the opinion that the
diolog where you can select it should clearly state that the operation
cannot be undone and may well kill working installations.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-eriix
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

custom debian for zaurus cl1000

[eric taylor]

Gentlemen,  I would like to know if it is possible to purchase a custom made debian package for the zaurus CL1000one large file to be placed upon a sd card an unzipped...shipped via cd?  A custom debian that has all of debian software and ALL of the games on Debian page???     Sincerely  Eric Taylor
		Yahoo! Mail
Bring photos to life! New PhotoMail  makes sharing a breeze. 

Bug#287322: Bug#287321: Installation Report - Cobalt RaQ

[Eric Evans]

On Mon, Dec 27, 2004 at 05:23:05PM +, Martin Michlmayr muttered these words:
> * Eric Evans <[EMAIL PROTECTED]> [2004-12-26 17:20]:
> > Machine: Cobalt RaQ
> > 
> > Everything worked flawlessly, outstanding work.
> 
> Thanks for the report.  Can you please upgrade CoLo to test if that
> works well (on both machines):
> 
> % wget http://www.cyrius.com/debian/cobalt/colo_1.16-1_mipsel.deb
> % dpkg -i colo_1.16-1_mipsel.deb
> 
> After reboot, you'll get a menu where you can choose to turn the
> console on or off.  You have to choose "on" there.  See
> /usr/share/doc/colo/NEWS.Debian.gz for more information (after
> installing the package, but before rebooting).

I upgraded colo on both machines and did not encounter any problems,
(except for the hours of my life that I have now lost playing with
paneld :).

One thing I wanted to note, I was not prompted to turn the console 
on/off after rebooting, (it immediately went to the boot selection
menu instead). I did get the console menu when I rebooted immediately
after the initial install of Sarge, I selected "console on" at that
time.

Hope this helps.

Regards,

-- 
Eric Evans
[EMAIL PROTECTED]


signature.asc
Description: Digital signature

Bug#287322: Installation Report - Cobalt RaQ2

[Eric Evans]

Package: installation-reports

INSTALL REPORT

Debian-installer-version: 12/24/2004,
http://people.debian.org/~tbm/d-i/images/mipsel/daily/cobalt/nfsroot.tar.gz
uname -a: Linux cobalt3 2.4.27-r5k-cobalt #1 Sun Sep 12 01:00:12 UTC 2004 mips 
GNU/Linux
Date: Fri, 17 Dec 2004 07:08:41 -0600
Method: Booted NFS, performed net install using an official mirror

Machine: Cobalt RaQ2
Processor: Mips
Memory: 128
Root Device: /dev/hda
Root Size/partition table:

  FilesystemSize  Used Avail Use% Mounted on
  /dev/hda2 7.4G  393M  6.6G   6% /
  tmpfs  63M 0   63M   0% /dev/shm
  /dev/hda1  93M  3.3M   85M   4% /boot

Output of lspci and lspci -n:

:00:00.0 Memory controller: Marvell Technology Group Ltd.: Unknown device 
4146 (rev 11)
:00:07.0 Ethernet controller: Digital Equipment Corporation DECchip 
21142/43 (rev 41)
:00:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c860 (rev 02)
:00:09.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA [Apollo 
VP] (rev 27)
:00:09.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
:00:09.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 
Controller (rev 02)
:00:0c.0 Ethernet controller: Digital Equipment Corporation DECchip 
21142/43 (rev 41)

:00:00.0 0580: 11ab:4146 (rev 11)
:00:07.0 0200: 1011:0019 (rev 41)
:00:08.0 0100: 1000:0006 (rev 02)
:00:09.0 0601: 1106:0586 (rev 27)
:00:09.1 0101: 1106:0571 (rev 06)
:00:09.2 0c03: 1106:3038 (rev 02)
:00:0c.0 0200: 1011:0019 (rev 41)

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

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

Comments/Problems:

Worked flawlessly, no problems whatsoever.

-- 
Eric Evans
[EMAIL PROTECTED]


signature.asc
Description: Digital signature

Bug#287321: Installation Report - Cobalt RaQ

[Eric Evans]

Package: installation-reports

INSTALL REPORT

Debian-installer-version: 12/24/2004, 
http://people.debian.org/~tbm/d-i/images/mipsel/daily/cobalt/nfsroot.tar.gz
uname -a: Linux cobalt 2.4.27-r5k-cobalt #1 Sun Sep 12 01:00:12 UTC 2004 mips 
GNU/Linux
Date: Fri, 24 Dec 2004 19:41:12 -0600 
Method: Booted NFS using files from above, and instructions found at
http://www.cyrius.com/debian/cobalt/sarge.html. Completed the remainder 
of the install using an official mirror. 

Machine: Cobalt RaQ
Processor: Mips
Memory: 64MB
Root Device: /dev/hda
Root Size/partition table:

  Filesystem   1K-blocks  Used Available Use% Mounted on
  /dev/hda2  5418272369188   4773852   8% /
  tmpfs31132 0 31132   0% /dev/shm
  /dev/hda194635  3293 86455   4% /boot
  /dev/hda6 14054608 32872  13307800   1% /home

Output of lspci and lspci -n:

:00:00.0 Host bridge: Marvell Technology Group Ltd.: Unknown device 4146 
(rev 02)
:00:07.0 Ethernet controller: Digital Equipment Corporation DECchip 
21142/43 (rev 41)
:00:09.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA [Apollo 
VP] (rev 27)
:00:09.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
:00:09.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 
Controller (rev 02)

:00:00.0 0600: 11ab:4146 (rev 02)
:00:07.0 0200: 1011:0019 (rev 41)
:00:09.0 0601: 1106:0586 (rev 27)
:00:09.1 0101: 1106:0571 (rev 06)
:00:09.2 0c03: 1106:3038 (rev 02)


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

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

Comments/Problems:

Everything worked flawlessly, outstanding work.

-- 
Eric Evans
[EMAIL PROTECTED]


signature.asc
Description: Digital signature

Bug#286534: Installer fails to read partition table.

[Eric Carlsen]

First of all, thanks for the message.

> Just one thing, the version of parted in sarge is 1.6.11 + some
> backported
> patches, and the version in experimental is 1.6.20, so in no way is the
> version in knoppix newer than the debian version, unless there is a
> mistake
> here somewhere.

Secondly, you're right. I later noticed that I was mistaken and the
version of parted used in the installer was 1.6.11, so I'm not sure what
the problem is. Thanks again.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]