Your message dated Sat, 31 Jan 2004 14:31:28 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#230279: Installer report for HP Omnibook 6000
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 29 Jan 2004 17:46:30 +0000
>From [EMAIL PROTECTED] Thu Jan 29 09:46:30 2004
Return-path: <[EMAIL PROTECTED]>
Received: from kotol.kotelna.sk [212.89.232.170] (daemon)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AmGFK-0003NE-00; Thu, 29 Jan 2004 09:46:30 -0800
Received: from cassiel.kotelna.sk ([::ffff:81.0.220.98])
(IDENT: postfix, AUTH: CRAM-MD5 mato, TLS: TLSv1/SSLv3,168bits,DES-CBC3-SHA)
by kotol.kotelna.sk with esmtp; Thu, 29 Jan 2004 18:46:26 +0100
Received: by cassiel.kotelna.sk (Postfix, from userid 1000)
id 719F7680D35A; Thu, 29 Jan 2004 18:36:16 +0100 (CET)
Date: Thu, 29 Jan 2004 18:36:16 +0100
From: Martin Lucina <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Installer report for HP Omnibook 6000
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_01_27
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no
version=2.60-bugs.debian.org_2004_01_27
X-Spam-Level:
Package: installation-reports
Debian-installer-version: 2004-01-02,
ftp://ftp.r-net.sk/pub/linux/debian/dists/sarge/main/installer-i386/current/images/netboot-initrd.gz
uname -a: <The result of running uname -a on a shell prompt>
Date: 2004-01-28, 17:00 CET
Method: network, via PXE from a local machine running Debian Woody
Machine: HP Omnibook 6000
Processor: Intel Pentium III-M 1133 Mhz
Memory: 256MB
Root Device: IDE 30GB
Root Size/partition table:
part1 nfts 8 GB (not mounted)
part2 reiserfs 20 GB (/)
part3 swap 0.8 GB
Output of lspci:
Base System Installation Checklist:
Initial boot worked: [O]
Configure network HW: [O]
Config network: [O]
Detect CD: [ ]
Load installer modules: [O]
Detect hard drives: [E]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O]
Install base system: [E]
Install boot loader: [ ]
Reboot: [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
Problems
During hardware detection the installer complained about not being able
to load ide-disk. The disk was however dectected correctly.
deboostrap failed on the base system install. It appears to be because
of some dependency (possibly circular) involving gnutls. I'd paste the
original output from apt here, but my second try at running deboostrap
hosed the list of installed packages, so I don't have it no more.
Also in the deboostrap log was something like "sleep: command not
found". Strange since /target/bin/sleep exists.
Is there a way to convice the installer that deboostrap was successful
and continue with the next step? If there is, I couldn't find it.
Attempting to select "install kernel" just retried the deboostrap again.
(And hosed the list of installed packages, as mentioned above).
Network hardware detection found both eth0 (Intersil PRISM wireless) and
eth1 (Intel eepro100). The network configuration screen is confusing, it
didn't say which interface was which card, had to try DHCP on both until
I figured out that eth1 was the eepro100.
Disk partitioning is confusing. Once you create the partitions you get a
screen that lets you create filesystems. It's not at all obvious here
whether the filesystem names it prints are what it's going to create or
what is already on the disk or in fact if the disk partitioning was
successful.
Example:
I had two NTFS partitions originally. Deleted one of them and kept
part1. Thus part2 which was to be reiserfs got created at the start of
the old (now deleted) NTFS partition. However the partition selector
when creating filesystems was trying to be "smart" and (presumably)
examining the start of the new partition, where it still found NTFS.
This confused the hell out of me since it looked like the fdisk hadn't
done anything.
After re-reading it a few times, checking with the command line fdisk
and dmesg that the change had *really* been made, I realised what was
going on and went and created the new filesystem anyway.
---------------------------------------
Received: (at 230279-done) by bugs.debian.org; 31 Jan 2004 13:27:44 +0000
>From [EMAIL PROTECTED] Sat Jan 31 05:27:44 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mxout.hispeed.ch (smtp.hispeed.ch) [62.2.95.247]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AmvA0-0005ub-00; Sat, 31 Jan 2004 05:27:44 -0800
Received: from 80-219-175-152.dclient.hispeed.ch (80-219-175-152.dclient.hispeed.ch
[80.219.175.152])
by smtp.hispeed.ch (8.12.6/8.12.6/tornado-1.0) with ESMTP id i0VDRfKf017400
for <[EMAIL PROTECTED]>; Sat, 31 Jan 2004 14:27:42 +0100
From: Simon =?iso-8859-1?q?H=FCrlimann?= <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#230279: Installer report for HP Omnibook 6000
Date: Sat, 31 Jan 2004 14:31:28 +0100
User-Agent: KMail/1.5.4
References: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_01_27
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=HAS_BUG_NUMBER autolearn=no
version=2.60-bugs.debian.org_2004_01_27
X-Spam-Level:
Am Thursday 29 January 2004 18:36 schrieb Martin Lucina:
> Package: installation-reports
>
> Debian-installer-version: 2004-01-02,
> ftp://ftp.r-net.sk/pub/linux/debian/dists/sarge/main/installer-i386/current
>/images/netboot-initrd.gz uname -a: <The result of running uname -a on a
> shell prompt>
> Date: 2004-01-28, 17:00 CET
> Method: network, via PXE from a local machine running Debian Woody
>
> Comments/Problems:
>
> Problems
>
> During hardware detection the installer complained about not being able
> to load ide-disk. The disk was however dectected correctly.
I think this has been fixed. But I'm not sure. Please report again if this
still happens on a new install.
> deboostrap failed on the base system install. It appears to be because
> of some dependency (possibly circular) involving gnutls. I'd paste the
> original output from apt here, but my second try at running deboostrap
> hosed the list of installed packages, so I don't have it no more.
>
> Also in the deboostrap log was something like "sleep: command not
> found". Strange since /target/bin/sleep exists.
This seems to be bug #225741 which has been closed now.
> Is there a way to convice the installer that deboostrap was successful
> and continue with the next step? If there is, I couldn't find it.
> Attempting to select "install kernel" just retried the deboostrap again.
> (And hosed the list of installed packages, as mentioned above).
Not sure what you exactly mean. But debootstrap should work now (and
forever:-). So this is regarded as fixed.
> Network hardware detection found both eth0 (Intersil PRISM wireless) and
> eth1 (Intel eepro100). The network configuration screen is confusing, it
> didn't say which interface was which card, had to try DHCP on both until
> I figured out that eth1 was the eepro100.
See http://lists.debian.org/debian-boot/2004/debian-boot-200401/msg02753.html
for some discussion about a new way for simple network configuration.
> Disk partitioning is confusing. Once you create the partitions you get a
> screen that lets you create filesystems. It's not at all obvious here
> whether the filesystem names it prints are what it's going to create or
> what is already on the disk or in fact if the disk partitioning was
> successful.
>
> Example:
>
> I had two NTFS partitions originally. Deleted one of them and kept
> part1. Thus part2 which was to be reiserfs got created at the start of
> the old (now deleted) NTFS partition. However the partition selector
> when creating filesystems was trying to be "smart" and (presumably)
> examining the start of the new partition, where it still found NTFS.
> This confused the hell out of me since it looked like the fdisk hadn't
> done anything.
>
> After re-reading it a few times, checking with the command line fdisk
> and dmesg that the change had *really* been made, I realised what was
> going on and went and created the new filesystem anyway.
Filed as bug against partitioner with title "confusing if shown filesystems
exist or get created" (don't wanna wait to get the bug number:-)
This installation report has been analyzed and is now being closed.
Thanx for your installation report
Simon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
