Bug#253470: di-rep: i386 netboot 20040607

2004-06-10 Thread Geert Stappers
On Wed, Jun 09, 2004 at 04:35:12PM -0300, Margarita Manterola wrote:
> Hola Geert Stappers!
> 
> > Debian-installer-version: 
> > http://people.debian.org/~joeyh/d-i/images/20040607/netboot/
> > a network boot using http://etherboot.org for the boot software at client side.
> > Used unstable from http://ftp.nl.debian.org for packages.
> 
> Could you try using testing, and tell us what happened?
With testing I'm able to do a succesfull install.

> 
> It seems to me that the problems you experienced might be due to a
> problem in unstable.
Yes, it seems something in unstable.

> 
> Love,
> Margarita.

Cheers
Geert Stappers


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



Re: New amd64 Debian-installer cdrom iso image

2004-06-10 Thread Geert Stappers
On Thu, Jun 10, 2004 at 08:01:32AM +0200, Goswin von Brederlow wrote:
> Hi,
> 
> I have updated the sid-amd64-cdrom.iso on alioth to the latest D-I
> images, debs and udebs from alioth including a fixed sid console-data.
That console-data fix, is that related to #253470
where an undocumented debconf "feature" is used ?

If yes, then please provide the changes ( a patch )


Thanks
Geert Stappers


pgpApuFzWlhr0.pgp
Description: PGP signature


Processed: Re: Bug#253470: triage

2004-06-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> reassign 253470 console-data
Bug#253470: di-rep: i386 netboot 20040607
Bug reassigned from package `installation-reports' to `console-data'.

> retitle 253470 console-data: uses undocumented debconf "feature"
Bug#253470: di-rep: i386 netboot 20040607
Changed Bug title.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#253470: triage

2004-06-10 Thread Geert Stappers
reassign 253470 console-data
retitle 253470 console-data: uses undocumented debconf "feature"
thanks

Hope This Helps

On Wed, Jun 09, 2004 at 08:11:33PM -0400, Joey Hess wrote:
> Geert Stappers wrote:
> > I had a closer look at /var/log/messages and found:
> > 
> > Setting up console-data (2002.12.04dbs-40) ...
> > Bareword "previous_module" not allowed while "strict subs" in use at 
> > /var/lib/dpkg/info/console-data.config line 1045.
> > Execution of /var/lib/dpkg/info/console-data.config aborted due to compilation 
> > errors.
> > dpkg: error processing console-data (--configure):
> >  subprocess post-installation script returned error exit statut 255
> 
> This is console-data apparently using an undocumented debconf "feature"
> that never did anything and that was removed from the latest version.
> I've put it back, sigh.
> 
> -- 
> see shy jo

Cheers
Geert Stappers


pgpo5Z8s1zZqc.pgp
Description: PGP signature


kernel oops decoder

2004-06-10 Thread Geert Stappers
On Wed, Jun 09, 2004 at 04:42:36PM -0400, Joey Hess wrote:
> Geert Stappers wrote:
> > Two attempts with 20040608 images failed in kernels oopses.
> > 
> > Attempts with 20040607 had also OOPSES at several places,
> > but did bring me to debian base system install.
> 
> Kernel oopses are of course either a kernel problem or a hardware
> problem, and so the rest of the problems seem likely to be related. So
> which is it, kernel or hardware? Get that oops decoder out..

Please tell me and the other lurkers here more
how to decode kernel oopses in debian-installer.

For what I see, is that the package ksymoops is needed at the target system.

When there are other ways, then please enlighten me/us.


Cheers
Geert Stappers


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



Re: New amd64 Debian-installer cdrom iso image

2004-06-10 Thread Goswin von Brederlow
Christian Perrier <[EMAIL PROTECTED]> writes:

> Quoting Goswin von Brederlow ([EMAIL PROTECTED]):
>> Hi,
>> 
>> I have updated the sid-amd64-cdrom.iso on alioth to the latest D-I
>> images, debs and udebs from alioth including a fixed sid console-data.
>
> I suppose that testing it on an already installed machine is not
> "dangerous" ? No risk of breaking an existing installation of another
> Linux distribution ? I think we have some AMD64 machines here and thus
> I could try some tests.

The partitioner will ask you if you want to erase the disk completly
or manually partition (default the first). Thats the most dangerous
part along with partitioning/formating.

And then installing the bootloader will overwrite your old one. In
case it doesn't detect all your existing OSes (it did detect my other
debian on the same disk) or otherwise messes up you might need a
rescue floppy/cd to get your OS back.


Apart from that nothing else _should_ happen. Some risk remains. If
you have valuable data on the disk better make a backup first or
replace the disk with an empty one for the test.

MfG
Goswin


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



Bug#253536: debian-installer: Amd64 kernel updates

2004-06-10 Thread Goswin von Brederlow
Joey Hess <[EMAIL PROTECTED]> writes:

> Goswin von Brederlow wrote:
>> Package: debian-installer
>> Version: 20040528
>> Severity: important
>> Tags: patch
>> Justification: fails to build from source
>
> Please stop using important as a severity for amd64 packages until amd64
> is an official arch or there is a consensus that it's the right
> severity.

Sorry but that is the consensus within the debian-amd64 team.  Our
current notion of amd64 is "official but not a release architecture
included on ftp.d.o".

>> debian-installer FTBFS because the kernel has been updated a few times
>> and input-modules are now compiled in. Patch attached.
>
> Should I add you back to the d-i project on alioth so you could commit
> such patches yourself?

That would be nice and save you from future bugreports.

> I've (hand-)applied the patch, but it would have been better if it
> included a debian/changelog entry.

Thanks.

MfG
Goswin


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



Bug#253536: debian-installer: Amd64 kernel updates

2004-06-10 Thread Wouter Verhelst
On Thu, Jun 10, 2004 at 09:43:05AM +0200, Goswin von Brederlow wrote:
> Joey Hess <[EMAIL PROTECTED]> writes:
> > Goswin von Brederlow wrote:
> >> Package: debian-installer
> >> Version: 20040528
> >> Severity: important
> >> Tags: patch
> >> Justification: fails to build from source
> >
> > Please stop using important as a severity for amd64 packages until amd64
> > is an official arch or there is a consensus that it's the right
> > severity.
> 
> Sorry but that is the consensus within the debian-amd64 team.

Well, then that consensus is wrong.

> Our current notion of amd64 is "official but not a release
> architecture included on ftp.d.o".

Those are in conflict. An "official" architecture is one that is
included on ftp.d.o; you can't be both official and not on ftp.d.o

Please stop filing "important" severity bugreports; the right severity
is "wishlist".

-- 
 EARTH
 smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
 WATER
 -- with thanks to fortune


signature.asc
Description: Digital signature


Re: New amd64 Debian-installer cdrom iso image

2004-06-10 Thread Gaudenz Steinlin
On Thu, Jun 10, 2004 at 08:01:32AM +0200, Goswin von Brederlow wrote:
> The init.d script of discover1 tries to rm /media/cdrom0/* which of
> course if read-only and fails (between installing base and grub).
> 
> After adding an exit 0 at the top of the script I was able to install
> grub and reboot the system into the freshly installed one.

I do not really understand your problem. Why is /media/cdrom0 read-only?
Is this problem specific to amd64 or general? Does it only occur if you
install sid or is it also in sarge?
Can you please file a bug report if this is really a problem with
discover1.

Gaudenz


signature.asc
Description: Digital signature


Bug#249346: discover1: Mouse module isn't loaded when using 2.6 kernel

2004-06-10 Thread Gaudenz Steinlin
On Sun, May 16, 2004 at 11:24:24PM +0300, Egle Pusaite wrote:
> Package: discover1
> Version: 1.5-9
> Severity: normal
> 
> 
> After the installation of 2.6 kernel the mouse stopped working.
> I must manually run: modprobe mousedev
> 
> I believe, it would be wise if the discover program loaded the mousedev
>  module automatically if the mouse device is connected to the computer.
> If it is impossible to check is the  mouse connected, discover has to
> try to load mousedev module in any case, because the majority of the
> computers have mouses connected.

Sorry for not replying earlier to your bug report. Discover1 is
currently only optimized for kernel 2.4. The problem is that the format
of the discover1 hardware database cannot hold information about kernel
versions. 

Please try discover version 2 (Package: discover) and test if your bug
is still present with the new version. 

Gaudenz
> 
> -- System Information:
> Debian Release: 3.0
> Architecture: i386
> Kernel: Linux mantas.namai.lt 2.6.3-1-k7 #2 Tue Feb 24 20:39:50 EST 2004 i686
> Locale: LANG=lt_LT, LC_CTYPE=lt_LT
> 
> Versions of packages discover1 depends on:
> ii  ash 0.3.8-37 NetBSD /bin/sh
> ii  dash0.4.21   The Debian Almquist Shell
> ii  debconf 1.2.23woody1 Debian configuration management sy
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries an
> ii  libdiscover11.1-6hardware identification library
> 
> -- debconf information excluded
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 


signature.asc
Description: Digital signature


Bug#236423: Numerous error messages at boot

2004-06-10 Thread Gaudenz Steinlin
On Thu, May 20, 2004 at 12:48:37AM -0500, Joe Hester wrote:
> Numerous error messages at boot:
> JEDEC: Found no ICH2 rom device at location zero
> 
> Stopped the error messages by adding a line to
> /etc/discover-modprobe.conf
> 
> skip ="ich2rom"
The only PCI ID that lists this kernel module is 8086:2480. According to
your lspci -n output you don't have a device with this PCI ID. Can you
please retest with the latest version of discover1-data (1.2004.02.08-7)
if this bug is still present.

Please also provide the versions of the packages discover1 and
discover1-data installed on your system. 

Gaudenz
> 
> lspci:
> :00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM
> Controller/Host-Hub Interface (rev 03)
> :00:02.0 VGA compatible controller: Intel Corp.
> 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03)
> :00:1d.0 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #1 (rev
> 02)
> :00:1d.1 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #2 (rev
> 02)
> :00:1d.2 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #3 (rev
> 02)
> :00:1d.7 USB Controller: Intel Corp. 82801DB (ICH4) USB2 EHCI
> Controller (rev 02)
> :00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface
> to PCI Bridge (rev 82)
> :00:1f.0 ISA bridge: Intel Corp. 82801DB (ICH4) LPC Bridge (rev 02)
> :00:1f.1 IDE interface: Intel Corp. 82801DB (ICH4) Ultra ATA 100
> Storage Controller (rev 02)
> :00:1f.3 SMBus: Intel Corp. 82801DB/DBM (ICH4) SMBus Controller (rev
> 02)
> :00:1f.5 Multimedia audio controller: Intel Corp. 82801DB (ICH4)
> AC'97 Audio Controller (rev 02)
> :01:09.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T
> (rev 01)
> 
> lspci -n:
> :00:00.0 Class 0600: 8086:2560 (rev 03)
> :00:02.0 Class 0300: 8086:2562 (rev 03)
> :00:1d.0 Class 0c03: 8086:24c2 (rev 02)
> :00:1d.1 Class 0c03: 8086:24c4 (rev 02)
> :00:1d.2 Class 0c03: 8086:24c7 (rev 02)
> :00:1d.7 Class 0c03: 8086:24cd (rev 02)
> :00:1e.0 Class 0604: 8086:244e (rev 82)
> :00:1f.0 Class 0601: 8086:24c0 (rev 02)
> :00:1f.1 Class 0101: 8086:24cb (rev 02)
> :00:1f.3 Class 0c05: 8086:24c3 (rev 02)
> :00:1f.5 Class 0401: 8086:24c5 (rev 02)
> :01:09.0 Class 0200: 14e4:4401 (rev 01)
> 
> 
> Hope this helps,
> Joe Hester
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 


signature.asc
Description: Digital signature


Re: New amd64 Debian-installer cdrom iso image

2004-06-10 Thread Petter Reinholdtsen
[Gaudenz Steinlin]
> I do not really understand your problem. Why is /media/cdrom0 read-only?
> Is this problem specific to amd64 or general? Does it only occur if you
> install sid or is it also in sarge?
> Can you please file a bug report if this is really a problem with
> discover1.

It is probably read-only because the CD is mounted there.  I've seen
it many times when installing from CD.


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



HP Proliant ML350 G3 - problems with HP Smart Array 641 Controller

2004-06-10 Thread Mikael Ljungberg, technordic
Hi!
I've bought an HP Proliant ML350 G3. On this computer there is a harddisk
controller (HP Smart Array 641 Controller) that doesn't work with any
linuxdistribution out of the box (the installation programs can't locate
the SCSI disks). HP has drivers for Red Hat 8 (and a few other 
distributions)
but I'd like to make this server work with debian.

Do you know about this controller and if I can find drivers for it that
will work with debian?
Regards, Micke!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Bug#242959: uhci + ehci

2004-06-10 Thread Gaudenz Steinlin
On Wed, Jun 02, 2004 at 12:47:39AM -0700, Karl Hegbloom wrote:
> I think it should load both.  UHCI is for USB 1, and EHCI is for USB 2.
In your bugreport you indicated that a module named usb-ehci should be
loaded. But there is no such module in the debian kernel packages. The
current version of discover1-data lists "ehci-hcd" as the module for your
device. Can you confirm that this is the correct module?

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


signature.asc
Description: Digital signature


Bug#238648: d-i, sata, netinst.iso 30.05.2004

2004-06-10 Thread Gaudenz Steinlin
On Sat, Jun 05, 2004 at 05:02:45PM +0200, Markus Haiml wrote:
> 
> 
> --On Montag, 31. Mai 2004 15:42 -0300 Martin Michlmayr <[EMAIL PROTECTED]> 
> wrote:
> 
> >Can you boot debian-installer and manually load the module with:
> >
> >  modprobe sata_promise
> >
> >Does debian-installer then see your disk?
> 
> d-i 30.05.2004 netinstall.
> 
> yes, I can 'modprobe sata_promise' in console 2 (alt-F2).
> debian-installer sees the sata disk as /dev/sda.

I'm somwhat lost with this bug report as I'm not sure if I understand it
correctly. 
Is it correct to add the moudle "sata_promise" for the device with PCI
ID "8086:24cb" which is labeled " Intel Corp. 82801DB (ICH4) Ultra ATA
100 Storage Controller (rev 02)"?

I'm a little bit unsure because the device description does not mention
SATA and the only reference to the sata_promise module in the current
database is for a device with an other vendor ID. Martin or Markus do
you have more information.

Gaudenz
> 
> Initially I had problems to install on this disk.
> # configuring 'base-installer' failed with error code 1
> last line in console 3 (alt-F3) was
> setting up initrd-tools(0.1.69)
> 
> I got this error 3 times, reproducibly.
> 
> I switched the BIOS setting of the sata-controller
> 'onbord ATA device first' from "yes" to "no"
> 
> Then I entered the Promise Fast-Track setup during boot (ctrl-F)
> and deleted the sata array and created a new one
> (0+1 striping array - I have only one sata disk).
> 
> Now it works.
> I switched 'onboard ATA device first' back from "no" to "yes"
> because I didn't see any changes. It still works.
> 
> Maybe the Fast-track setup was the key ?!
> 
> I tried the following configurations and successfully installed Debian-base
> 
> -
> dev/sda1 /
> -
> /dev/hda1 swap
> /dev/hda2 /boot
> /dev/hda3 /tmp
> /dev/hda4 /var
> 
> /dev/hdb1 /home
> 
> /dev/sda1 /
> -
> /dev/hda1 /usr
> 
> /dev/hdb1 /home
> 
> /dev/sda1 /boot
> /dev/sda2 /
> -
> I tried ext2, ext3, reiserfs.
> 
> Is there anything special I should test concerning SATA?
> Otherwise I would put back the SATA disk into my P4P800.
> 
> If you need feedback, I could test sata in the P4P800 too.
> Which module should I load for the ICH5R ?
> The debain-installer does not see the sata disk automatically.
> 
> =
> 
> >From my scan through newsgroups etc. I got the impression
> that sata uses ide commands rather than scsi commands,
> with some scsi-like extensions to the ide set,
> which are going to be implemented
> but are not yet fully supported by sata controllers.
> 
> Consequently, I suppose that /dev/sda needs a scsi->ide translation
> and /dev/hde should be the better choice.
> 
> - Am I completely wrong here?
> - How would I address the sata disk (connected to a ICH5R) as /dev/hde?
> 
> =
> 
> >
> >Can you paste the output of
> >  lspci
> >  lspci -n
> >
> 
> Don't know if you still need the lspci from the P4PE.
> Anyway, here it is.
> btw: there is no lspci in the busybox.
> This is the output from the installed debain.
> 
> lspci
> 
> :00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM 
> Controller/Host-Hub Interface (rev 02)
> :00:01.0 PCI bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE 
> Host-to-AGP Bridge (rev 02)
> :00:1d.0 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #1 (rev 02)
> :00:1d.1 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #2 (rev 02)
> :00:1d.2 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #3 (rev 02)
> :00:1d.7 USB Controller: Intel Corp. 82801DB (ICH4) USB2 EHCI 
> Controller (rev 02)
> :00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to 
> PCI Bridge (rev 82)
> :00:1f.0 ISA bridge: Intel Corp. 82801DB (ICH4) LPC Bridge (rev 02)
> :00:1f.1 IDE interface: Intel Corp. 82801DB (ICH4) Ultra ATA 100 
> Storage Controller (rev 02)
> :00:1f.3 SMBus: Intel Corp. 82801DB/DBM (ICH4) SMBus Controller (rev 02)
> :00:1f.5 Multimedia audio controller: Intel Corp. 82801DB (ICH4) AC'97 
> Audio Controller (rev 02)
> :01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 
> If [Radeon 9000] (rev 01)
> :01:00.1 Display controller: ATI Technologies Inc Radeon RV250 [Radeon 
> 9000] (Secondary) (rev 01)
> :02:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host 
> Controller (rev 80)
> :02:04.0 RAID bus controller: Promise Technology, Inc. PDC20376 (rev 02)
> :02:05.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702 
> Gigabit Ethernet (rev 02)
> :02:0a.0 Multimedia video controller: Brooktree Corporation Bt878 Video 
> Capture (rev 02)
> :02:0a.1 Multimedia controller: Brooktree Corporation Bt878 Audio 
> Capture (rev 02)
> 
> lspci -n
> ++

Re: New amd64 Debian-installer cdrom iso image

2004-06-10 Thread Goswin von Brederlow
[EMAIL PROTECTED] (Geert Stappers) writes:

> On Thu, Jun 10, 2004 at 08:01:32AM +0200, Goswin von Brederlow wrote:
>> Hi,
>> 
>> I have updated the sid-amd64-cdrom.iso on alioth to the latest D-I
>> images, debs and udebs from alioth including a fixed sid console-data.
> That console-data fix, is that related to #253470
> where an undocumented debconf "feature" is used ?
>
> If yes, then please provide the changes ( a patch )
>
>
> Thanks
> Geert Stappers

The Bugreport in the BTS says

| This is console-data apparently using an undocumented debconf "feature"
| that never did anything and that was removed from the latest version.
| I've put it back, sigh.

Since it didn't do anything removing it should have the same
effect. So thats what I did.

MfG
Goswin

--
diff -Nurd console-data-2002.12.04dbs/debian/changelog 
console-data-2002.12.04dbs.amd64/debian/changelog
--- console-data-2002.12.04dbs/debian/changelog 2004-06-08 20:34:35.0 +
+++ console-data-2002.12.04dbs.amd64/debian/changelog   2004-06-10 04:28:30.0 
+
@@ -1,3 +1,9 @@
+console-data (2002.12.04dbs-41.0.0.1.pure64) unstable; urgency=low
+
+  * Remove use of previous_module in console-data.config
+
+ -- Goswin von Brederlow <[EMAIL PROTECTED]>  Thu, 10 Jun 2004 02:38:10 +0200
+
 console-data (2002.12.04dbs-41) unstable; urgency=low
 
   * Translations:
diff -Nurd console-data-2002.12.04dbs/debian/console-data.config 
console-data-2002.12.04dbs.amd64/debian/console-data.config
--- console-data-2002.12.04dbs/debian/console-data.config   2004-06-05 
07:29:50.0 +
+++ console-data-2002.12.04dbs.amd64/debian/console-data.config 2004-06-10 
04:28:55.0 +
@@ -1042,7 +1042,6 @@
   @retval = go;
   if ($retval[0] eq 30) {
set ('console-data/keymap/policy', "Don't touch keymap");
-   previous_module;
exit 30; 
   }
 
@@ -1067,7 +1066,6 @@
if ($seen eq 'false') {
  # Hitting "back" here has no meaning mostly, but try to behave as sanely 
as I
  # can think of.
- previous_module;
  exit 30;
} else {
  next;




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



Re: New amd64 Debian-installer cdrom iso image

2004-06-10 Thread Goswin von Brederlow
Petter Reinholdtsen <[EMAIL PROTECTED]> writes:

> [Gaudenz Steinlin]
>> I do not really understand your problem. Why is /media/cdrom0 read-only?
>> Is this problem specific to amd64 or general? Does it only occur if you
>> install sid or is it also in sarge?
>> Can you please file a bug report if this is really a problem with
>> discover1.
>
> It is probably read-only because the CD is mounted there.  I've seen
> it many times when installing from CD.

Exactly. The cd is still mounted there since thats where discover1.deb
comes from.

I haven't had time to try to install i386 yet or to test and debug
discover1 post installation. So I can't say if its amd64 specific or
what exactly makes discover want to delete the mounted cd.

What archs did you see it on and did you file a bug already?

MfG
Goswin


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



(forw) ne reconnait pas le disque dur

2004-06-10 Thread Christian Perrier
OK, this is in french and I currently don't have time for translating
carefully. I asked Sophie to report here in English possibly with
needed details (is this with Debian Installer? If so, which image
exactly? Which kind of PowerMac?). She will maybe report in
French...and then I'll translate.

Given the mention of "Debian 3.2.0" I suspect this is with Debian Installer
but the mention of "install24" raises a doubt to me...

Besides this, this is a disk detection problem.

- Forwarded message from Sophie Maitrejean <[EMAIL PROTECTED]> -

Date: Thu, 10 Jun 2004 13:57:22 +0200
Subject: ne reconnait pas le disque dur
From: Sophie Maitrejean <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Mailer: Apple Mail (2.553)
X-Mailing-List: <[EMAIL PROTECTED]> archive/latest/22447

Bonjour,


Nous aimerions pouvoir installer Debian 3.2.0 sur un macOSX 10.2.8. 
Pour ceci, nous avons ajouté un deuxième disque dur. C'est un disque 
dur IBM DHEA-36481 de 6,4 Go,
de février 1999.


Après avoir mis le disque IBM à la place de celui
du Macintosh et le CD-ROM de Debian dans le lecteur,
nous avons  commencé le processus d'installation
(en choisissant 'install24').

Arrivé au moment de partitionner le disque dur,
nous avons été bloqué par le message suivant :
"Aucun disque n'a été détecté changer les
paramètres des pilotes à l'amorçage du système ..."

Nous avons vérifié que le disque fonctionnait en
redémarrant avec le système Macintosh : il fonctionne
effectivement bien en tant que deuxième disque.

Nous avons essayé de le raccorder à la première nappe,
à la deuxième, nous avons retiré les cavaliers du disque, ...
mais il n'y a rien eu à faire.

En faisant un 'dmesg | more' dans le terminal de secours
de l'installeur de Debian, nous avons vu qu'il n'arrivait pas à
détecter le disque dur.

Quelques extraits des messages :

PCI : probing PCI hardware
PCI -> 0F bus map
0 -> 0
1 -> 0
2 -> 0
No OF node for device 1:18
No OF node for device 1:19
...
ide : Assuming 33MHz system bus speed for PIO mode ;
override with idebus=xx
IN from bad port cfc at c00f5598
pmac_ide : enabling IDE bus ID 2
  enabling IDE bus ID 0
hde : TOSHIBA DVD-ROM ...
...

On constate que la mention 'hda : ...' n'apparait jamais
dans la liste des messages.

Comme nous l'indique le message de l'installeur Debian,
n'y aurait-il pas quelques paramètres à donner au noyau
au moment de l'amorçage ?
Cela peut-il concerner le paramètre 'idebus' ?

Vous est-il déjà arrivé quelque chose de semblable
et que nous conseillez-vous ?

S'il y a des paramètres à passer, où les met-on ?
- à la suite de la ligne : boot cd:,install\powermac\yaboot ?
- à la suite de : install24 ?

Un grand merci pour votre aide,
Sophie.

- End forwarded message -

-- 



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



egb4car.com Ihre Automobilplattform in Europa

2004-06-10 Thread egb4car . com team
Title: egb4car.com - Ihre Automobilplattform in Europa




Herzlich willkommen 

Sie wollen Ihr Auto, Motorrad, Bus, Wohnmobil, Transporter, Bau- oder Landwirtschaftmaschine in ganz Europa kaufen oder verkaufen?



West go to East ... East go to West ...



Wir sind für Sie da 
www.egb4car.com - kostenlos und ohne Grenzen mit simultaner Übersetzung inserieren oder suchen.

Ihr egb4car team




Sollten Sie diese Mail versehendlich erhalten haben, so bitten wir Sie vielmals um Entschuldigung.
Benutzen Sie bitte diesen Link um eine weitere Zusendung zu vermeiden.






Re: Re: Installer fails on initrd-tools

2004-06-10 Thread Colin Watson
On Wed, Jun 09, 2004 at 12:52:39PM -0400, Joey Hess wrote:
> Dan C wrote:
> > + rootpart_devfs=/dev/ide/host0/bus0/target0/lun0/part1156681320
> 
> It seems that base-installer finds the root partition by the rather
> broken method of doing a "df /target". I assume that you have a large
> root partition, of more than 100 gb in size, and probably the df
> output does not add whitespace between the partition name and the size
> in this case.

Oof. We probably need to fix a load of *-installer packages if that's
going to be a problem. (I don't have that much disk on my test system,
so I've never seen this ...)

-- 
Colin Watson  [EMAIL PROTECTED]


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



Bug#242228: marked as done (installation-reports: failed: cannot repartition hard drive)

2004-06-10 Thread Debian Bug Tracking System
Your message dated Thu, 10 Jun 2004 16:39:19 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Cannot reproduce
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; 5 Apr 2004 13:39:42 +
>From [EMAIL PROTECTED] Mon Apr 05 06:39:42 2004
Return-path: <[EMAIL PROTECTED]>
Received: from boy.univ.kiev.ua (mail.univ.kiev.ua) [193.125.78.122] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BAUKE-CI-00; Mon, 05 Apr 2004 06:39:42 -0700
Received: from intel4.icc.univ.kiev.ua (intel4.icc.univ.kiev.ua [10.25.0.243])
by mail.univ.kiev.ua (8.12.2/8.12.2) with ESMTP id i35DdaX4076464;
Mon, 5 Apr 2004 16:39:37 +0300 (EEST)
Received: from eugen by intel4.icc.univ.kiev.ua with local (Exim 4.30)
id 1BAUK7-LG-AW; Mon, 05 Apr 2004 16:39:35 +0300
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Eugeniy Meshcheryakov <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: installation-reports: failed: cannot repartition hard drive
X-Mailer: reportbug 2.56
Date: Mon, 05 Apr 2004 16:39:34 +0300
Message-Id: <[EMAIL PROTECTED]>
Sender: Eugeniy Meshcheryakov <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Scores: 1

Package: installation-reports
Version: Daily netboot initrd, 20040404
Severity: normal
Tags: d-i

   I have tryed to install Debian unstable with daily netboot image. 
When partman dialog appeared it was only whole hard drive in list,
so I was not able to modify existing partitions.
   Alternative partitioner (cfdisk ?) displays error message end exits:

 FATAL ERROR: Bad logical partiton 6: enlarged logical partitions overlap

Output of 'fdisk -l /dev/hda' follows:
---
omitting empty partition (8)

Disk /dev/hda: 40.0 GB, 40060403712 bytes
255 heads, 63 sectors/track, 4870 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
   /dev/hda1   1450036146218+   f  W95 Ext'd
   (LBA)
   /dev/hda2   *45014870 2972025   39  Plan 9
   /dev/hda5   1  64  514017   83  Linux
   /dev/hda6  65 103  313236   82  Linux swap
   /dev/hda7 104255019655496   8e  Linux LVM


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=uk_UA, LC_CTYPE=uk_UA

---
Received: (at 242228-done) by bugs.debian.org; 10 Jun 2004 13:39:26 +
>From [EMAIL PROTECTED] Thu Jun 10 06:39:26 2004
Return-path: <[EMAIL PROTECTED]>
Received: from boy.univ.kiev.ua (mail.univ.kiev.ua) [193.125.78.122] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BYPm9-00047h-00; Thu, 10 Jun 2004 06:39:26 -0700
Received: from intel4.icc.univ.kiev.ua (intel4.icc.univ.kiev.ua [10.25.0.243])
by mail.univ.kiev.ua (8.12.2/8.12.2) with ESMTP id i5ADdJ8h074255
for <[EMAIL PROTECTED]>; Thu, 10 Jun 2004 16:39:19 +0300 (EEST)
Received: from eugen by intel4.icc.univ.kiev.ua with local (Exim 4.34)
id 1BYPm3-J1-4S
for [EMAIL PROTECTED]; Thu, 10 Jun 2004 16:39:19 +0300
To: [EMAIL PROTECTED]
Subject: Cannot reproduce
Message-Id: <[EMAIL PROTECTED]>
From: Eugeniy Meshcheryakov <[EMAIL PROTECTED]>
Date: Thu, 10 Jun 2004 16:39:19 +0300
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=0.0 required=4.0 tests=none autolearn=no 
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

  I cannot reproduce this bug anymore, so closing
this bug report now.


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



Bug#242959: uhci + ehci

2004-06-10 Thread Colin Watson
On Thu, Jun 10, 2004 at 11:50:04AM +0200, Gaudenz Steinlin wrote:
> On Wed, Jun 02, 2004 at 12:47:39AM -0700, Karl Hegbloom wrote:
> > I think it should load both.  UHCI is for USB 1, and EHCI is for USB 2.
> 
> In your bugreport you indicated that a module named usb-ehci should be
> loaded. But there is no such module in the debian kernel packages. The
> current version of discover1-data lists "ehci-hcd" as the module for your
> device. Can you confirm that this is the correct module?

I can confirm that.

-- 
Colin Watson  [EMAIL PROTECTED]


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



Re: (forw) ne reconnait pas le disque dur

2004-06-10 Thread Colin Watson
On Thu, Jun 10, 2004 at 03:23:06PM +0200, Christian Perrier wrote:
> OK, this is in french and I currently don't have time for translating
> carefully. I asked Sophie to report here in English possibly with
> needed details (is this with Debian Installer? If so, which image
> exactly? Which kind of PowerMac?). She will maybe report in
> French...and then I'll translate.
> 
> Given the mention of "Debian 3.2.0" I suspect this is with Debian Installer
> but the mention of "install24" raises a doubt to me...

There's no "install24" in d-i, indeed. I suspect she's talking about
3.0r2.

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]


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



Bug#252930: Installation-Reports: Beta 4 as a VMware Guest

2004-06-10 Thread Thiemo Seufer
Joey Hess wrote:
[snip]
> Looking at it again, the root cause seems to be that a root login shell
> does not get the sbin directories in the PATH. The PATH is
> "/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games". That seems broken
> to me, shouldn't root have those directories in its path when you log in
> as root? Anyway, probably a base-config bug, since base-config was
> recently changed to call sh -l.
> 
> Apparently /root/.profile is supposed to set the PATH for root to
> include the sbin directories. I don't know why this isn't happening, but
> I have seen the same problem on fresh debian installs. I can't reproduce
> it after install.

~/.profile gets ignored, because $HOME is set to / instead of /root,
so it uses only the definitions in /etc/profile. (This also leaves
a .bash_history file in /.)


Thiemo


signature.asc
Description: Digital signature


Bug#238648: d-i, sata, netinst.iso 30.05.2004

2004-06-10 Thread Markus Haiml
--On Donnerstag, 10. Juni 2004 11:59 +0200 Gaudenz Steinlin 
<[EMAIL PROTECTED]> wrote:

On Sat, Jun 05, 2004 at 05:02:45PM +0200, Markus Haiml wrote:

--On Montag, 31. Mai 2004 15:42 -0300 Martin Michlmayr <[EMAIL PROTECTED]>
wrote:
> Can you boot debian-installer and manually load the module with:
>
>  modprobe sata_promise
>
> Does debian-installer then see your disk?
d-i 30.05.2004 netinstall.
yes, I can 'modprobe sata_promise' in console 2 (alt-F2).
debian-installer sees the sata disk as /dev/sda.
I'm somwhat lost with this bug report as I'm not sure if I understand it
correctly.
Me too. I reported Bug #238648 on [2004-03-18 08:17]:
"could not install debian, because tg3 module did not load correctly."
and got an email 9-1/2 weeks later:
On [2004-05-24 18:16] Martin Michlmayr wrote
# * Haiml, Markus <[EMAIL PROTECTED]> [2004-03-18 08:17]:
# > Machine: 
#
# Your installation report mentioned that you're using a machine with SATA
# disks.  Since the last beta of debian-installer was released, a large
# number of changes related to SATA have been made.  In particular, we now
# ship a 2.4.26 kernel with (some) SATA support.  We're currently preparing 
a
# new test release of debian-installer (release candidate 1), and we'd
# appreciate it if you could try our daily image and tell us whether this
# works.  This will give us some time to make important changes if so
# requires before rc1 is released.  You can find current images at
# http://gluck.debian.org/cdimage/testing/sarge_d-i/
#
# We'd appreciate it if you could test this image and tell us if the issues
# you mentioned in your bug report have been dealt with, and in particular
# whether your SATA disks are recognized and work.  You can either boot
# normally (by pressing enter or typing "linux") and will get a 2.4.26 
kernel
# with SATA, or you can type "linux26" and get a 2.6 kernel; both should
# work, and we'd appreciate feedback about both of them.  Thanks
#
# > d-i detects NIC and tries correct module tg3. However, "modprobe -v
# > tg3" results in "no hardware found" with sarge-i386-netinst.iso
# > (beta3).
#
# Can you try the daily image and check if this works?  If not, can you
# show me the output of the kernel when you load the tg3 module (this
# will show what chip you have exactly).
# --
# Martin Michlmayr
# [EMAIL PROTECTED]

So I tested the d-i 2004-05-30 image and found that 2.4 installs fine and 
2.6 does not install because the tg3 and bcm5700 nic modules were not 
ported to 2.6 yet.

In addition, Martin Michlmayr asked me to test my sata configuration.
So I put a sata disk in my P4PE with onboard Promise 20376 sata controller.
Linux24 (d-i 2004-05-30) did not recognize my sata disk out of the box, but 
when I loaded the sata_promise module manually, I could install several 
combinations of ide/sata partitions.
Linux26 (d-i 2004-05-30) could not be tested due to the misson nic module.

This was my reply. However, it is not related to the original tg3-bug 
#238648. Bug #238648 has been closed by Martin Michlmayr on [31.05.2004 
11:54]

# I'm closing this bug.  2.4 works and 2.6 does't work because currently
# the module doesn't exist; this will be fixed in the near future.
# --
# Martin Michlmayr
# [EMAIL PROTECTED]
Maybe I should not have replied to Martin's request to the same thread but 
create a new bug report? Anyway.

Is it correct to add the moudle "sata_promise" for the device with PCI
ID "8086:24cb" which is labeled " Intel Corp. 82801DB (ICH4) Ultra ATA
100 Storage Controller (rev 02)"?
No. The sata_promise was added for the PCI device:
:02:04.0 RAID bus controller: Promise Technology, Inc. PDC20376 (rev02)
I'm a little bit unsure because the device description does not mention
SATA and the only reference to the sata_promise module in the current
database is for a device with an other vendor ID. Martin or Markus do
you have more information.
I have installed Debain on a Seagate Baracuda 7200.7 SATA on the Asus 
P4PE/Promise PDC20736 after manually loading sata_promise. It did not work 
in the first time, but after I created a RAID with this single disk in 
'Promise Fast Track Setup' (Ctrl-F during boot), everything works fine.

(1)
However, I did not exactly know what I was ask to do.
# "if you could try our daily image and tell us whether this works."
If I should try something more but installing debain, let me know.
(2)
I was asked to test SATA on the Promise PDC20376 in my Asus P4PE.
I also have a Asus P4P800 deluxe with Intels 82801EB (ICH5R).
Therefore I asked, if I should test d-i on a sata-disk attached to the 
ICH5R.
Out of the box d-i does not recognize my sata.
Therefore I asked, which module I should load.
The BIOS configures the SATA disk as third IDE master.

If I should not test the sata disk attached to ICH5R - That's fine for me.
Gaudenz
Markus
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Bug#228269: marked as done (installation-report: beta2 test on i386 : doesn't boot at all)

2004-06-10 Thread Debian Bug Tracking System
Your message dated Thu, 10 Jun 2004 17:02:03 +0200
with message-id <[EMAIL PROTECTED]>
and subject line installation-report: beta2 test on i386 : doesn't boot at all
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; 17 Jan 2004 21:30:02 +
>From [EMAIL PROTECTED] Sat Jan 17 13:30:02 2004
Return-path: <[EMAIL PROTECTED]>
Received: from smtp1.wanadoo.fr (mwinf0102.wanadoo.fr) [193.252.22.30] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Ahy13-tH-00; Sat, 17 Jan 2004 13:30:01 -0800
Received: from seb128 (ANancy-111-1-12-215.w81-251.abo.wanadoo.fr [81.251.58.215])
by mwinf0102.wanadoo.fr (SMTP Server) with ESMTP
id 394AC1BFD3EA; Sat, 17 Jan 2004 22:29:29 +0100 (CET)
Received: from seb128 by seb128 with local (Exim 3.36 #1 (Debian))
id 1Ahy0T-0007Ct-00; Sat, 17 Jan 2004 22:29:25 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Sebastien Bacher <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: installation-report: beta2 test on i386 : doesn't boot at all
X-Mailer: reportbug 2.37
Date: Sat, 17 Jan 2004 22:29:25 +0100
Message-Id: <[EMAIL PROTECTED]>
Sender: Sebastien Bacher <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_01_14 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.9 required=4.0 tests=FROM_ENDS_IN_NUMS,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_01_14
X-Spam-Level: 

Package: installation-report
Version: beta2
Severity: normal
Tags: d-i

(Same config as in #220014).

Initial boot worked:[E]

I've made a bunch on tests with daily iso of the first days of january without any 
problem on boot, but the beta 2 doesn't boot at all here.
The boot just hang with "Loading" after the "Boot :" validation. No "." drawing at 
screen, and not changes.


Machine: i386 (pentium III), IDE drives 
hda: FUJITSU MPD3043AT, ATA DISK drive
hdb: HITACHI CDR-8335, ATAPI CD/DVD-ROM drive
hdc: IBM-DTLA-307030, ATA DISK drive

Processor: Pentium III (Coppermine), 750Mhz

Memory: 128M

Root Device: /dev/hdc

Root Size/partition table:  
Disk /dev/hdc: 30.7 GB, 30738677760 bytes
255 heads, 63 sectors/track, 3737 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
/dev/hdc1   *   1 637 5116671b  W95 FAT32
/dev/hdc2 6381500 6932047+   c  W95 FAT32 (LBA)
/dev/hdc315011657 1261102+  83  Linux
/dev/hdc416583737167076005  Extended
/dev/hdc516581683  208813+  82  Linux swap
/dev/hdc61684373716498723+  83  Linux

Output of lspci:

00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller 
Hub (rev 02)
00:01.0 PCI bridge: Intel Corp. 82815 815 Chipset AGP Bridge (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev 02)
00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 02)
00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 02)
00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 02)
00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R100 QD [Radeon 7200]
02:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)

---
Received: (at 228269-done) by bugs.debian.org; 10 Jun 2004 15:02:39 +
>From [EMAIL PROTECTED] Thu Jun 10 08:02:39 2004
Return-path: <[EMAIL PROTECTED]>
Received: from smtp6.wanadoo.fr (mwinf0602.wanadoo.fr) [193.252.22.25] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BYR4h-0005W1-00; Thu, 10 Jun 2004 08:02:39 -0700
Received: from seb128 (ANancy-111-1-16-149.w81-50.abo.wanadoo.fr [81.50.241.149])
by mwinf0602.wanadoo.fr (SMTP Server) with ESMTP id 75FA25400341
for <[EMAIL PROTECTED]>; Thu, 10 Jun 2004 17:02:08 +0200 (CEST)
Received: from seb128 by seb128 with local (Exim 3.36 #1 (Debian))
id 1BYR48-0006aI-00
for <[EMAIL PROTECTED]>; Thu, 10 Jun 2004 17:02:04 +0200
Subject: Re: installation-report: beta2 test on i386 : doesn't boot at all
From: Sebastien Bacher <[EMAIL PROTECTED]>
To: [EMAI

Re: state of the test candidate

2004-06-10 Thread Kenshi Muto
At 9 Jun 04 16:29:36 GMT,
Joey Hess wrote:
> Kenshi Muto wrote:
> > My known issue:
> > 
> > - - linux26 + i386 + vga16fb + some languages (Chinese, Japanese,
> >   Korean, Greek, Bulgarian) goes serious screen lockup on 2nd stage.
> >   This is not d-i's fault, but is kernel 2.6.6 problem. (Bug#251861)
> > - - 'netcfg/use_dhcp=false' is ignored although d-i installer describes
> >   this parameter. (Bug#248147)
> > - - debconf priority problem (Sorry for my bad patch, JoeyH).
> >   debconf priorities are different during/after base-config. (Bug#245164?)
> > - - pppconfig i18n/l10n is under maintainer's work. (Bug#246520)
> 
> I don't think any of these are release critical. The 2.6 stuff is still

OK, these are not RC.

But I hope these are needed to solve till really Sarge release.

May I remove mention about netcfg/use_dhcp from
installer/build/boot/*/f7.txt at this time?

> basically experimental, but if you do think that is RC, you should make
> bug #251861 release critical. The rest seems minor.

#251861 will be resolved by Herbert's next kernel upload.
He understood and promised to fix this problem.

Thanks,
-- 
Kenshi Muto
[EMAIL PROTECTED]


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



Re: (forw) ne reconnait pas le disque dur

2004-06-10 Thread Christian Perrier
Quoting Colin Watson ([EMAIL PROTECTED]):

> There's no "install24" in d-i, indeed. I suspect she's talking about
> 3.0r2.

Hmmm, you're certainly right. So let's convince her to test d-i,
now..:-)



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



Bug#253640: USB drivers not loaded with 2.6 on powerpc

2004-06-10 Thread Laurent Bigonville
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: debian-installer
Severity: important
The usb driver doesn't seem to be loaded on my powermac when I boot 
with the 2.6 kernel(sid daily-build).
It's realy annoying with an usb keyboard...

Laurent Bigonville
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFAyH0DVLyDt/3apY8RAsolAKCo4gHXHJz08Jj98O97S8YyPghCdgCfVq3d
q1kiks+ztCYqkZjOLSrqvWk=
=GSxb
-END PGP SIGNATURE-

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


initrd.list output from build process

2004-06-10 Thread Colin Watson
The following patch causes the d-i build process to output an
initrd.list file beside each initrd listing the packages it contains and
the versions of each package. What do people think - should I commit
this? I think it would be very useful for:

  * figuring out what versions of everything went into the initrd part
of a given image without having to find and read through build logs,
which is our only way of doing this at the moment and is a
nightmare;

  * arranging for debian-cd to exclude packages already in the initrd
automatically rather than using its current manually-maintained
exclude-udebs thing;

  * allowing third parties building d-i-based images to work out which
set of packages is sufficient.

Index: config/dir
===
--- config/dir  (revision 16700)
+++ config/dir  (working copy)
@@ -53,6 +53,7 @@
 
 # The files we may want to have in dest/
 INITRD = $(SOME_DEST)/$(EXTRANAME)initrd.gz
+INITRD_LIST = $(SOME_DEST)/$(EXTRANAME)initrd.list
 KERNEL = $(foreach name,$(KERNELNAME),$(SOME_DEST)/$(EXTRANAME)$(name))
 BOOT = $(SOME_DEST)/$(EXTRANAME)boot.img$(GZIPPED)
 ROOT = $(SOME_DEST)/$(EXTRANAME)root.img$(GZIPPED)
@@ -63,6 +64,7 @@
 
 # some intersting files in tmp/ we may need
 TEMP_INITRD = $(TEMP)/initrd.gz
+TEMP_INITRD_LIST = $(TEMP)/initrd.list
 TEMP_KERNEL = $(foreach name,$(KERNELNAME),$(TEMP)/$(name))
 TEMP_BOOT = $(TEMP)/boot.img
 TEMP_ROOT = $(TEMP)/root.img
Index: Makefile
===
--- Makefile(revision 16700)
+++ Makefile(working copy)
@@ -312,6 +312,9 @@
done
sort -n < $(TEMP)/diskusage.txt > $(TEMP)/diskusage.txt.new && \
mv $(TEMP)/diskusage.txt.new $(TEMP)/diskusage.txt
+   grep-dctrl -nsPackage,Version '' $(TREE)/var/lib/dpkg/status | \
+   perl -nle '$$p = $$_; $$v = <>; chomp $$v; <>; print "$$p $$v"' | \
+   sort > $(TEMP_INITRD_LIST)
 
# Clean up after dpkg.
rm -rf $(DPKGDIR)/updates
@@ -572,8 +575,9 @@
 # Create the images for dest/. Those are the targets called from config.
 #
 # Create a compressed image of the root filesystem by way of genext2fs.
-$(INITRD): $(TEMP_INITRD)
+$(INITRD): $(TEMP_INITRD) $(TEMP_INITRD_LIST)
install -m 644 -D $< $@
+   install -m 644 -D $(TEMP_INITRD_LIST) $(INITRD_LIST)
./update-manifest $@ $(MANIFEST-INITRD)
 
 $(TEMP_INITRD): $(STAMPS)tree-$(targetstring)-stamp
@@ -600,6 +604,8 @@
esac
gzip -v9f $(TEMP)/initrd
 
+$(TEMP_INITRD_LIST): $(STAMPS)tree-$(targetstring)-stamp
+
 # raw kernel images
 $(KERNEL): TEMP_REAL_KERNEL = $(TEMP)/$(shell echo ./$@ |sed 
's,$(SOME_DEST)/$(EXTRANAME),,')
 $(KERNEL):

-- 
Colin Watson  [EMAIL PROTECTED]


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



Bug#253645: modconf does not write options into /etc/modules

2004-06-10 Thread Florian Schmidt
Package: modconf
Version: 0.2.45.1

Hi, 

i tried around with jack o'quins realtime lsm for 2.6.x kernels and i found something 
weird..

when i pass the options any=1 allcaps=1 via the modconf program these options do get 
written into /etc/modutils/realtime, but not into /etc/modules. Weird enough, they 
also do not seem to get applied to the loaded module.. therefore right now i need to 
load the module manually via modprobe realtime any=1 allcaps=1.

Versions: Debian unstable
Kernel: Vanilla selfbuilt 2.6.6

Realtime Module: http://www.joq.us/realtime/realtime-lsm-0.1.1.tar.gz

Thanks,
Florian Schmidt

P.S.
-- 
Palimm Palimm!



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



Install via PPPoE

2004-06-10 Thread Arthur Wiebe
I haven't been able to find any info on how to install Sarge through the 
Internet using PPPoE to connect. Is this possible yet? If so how? I 
haven't been able to test the latest test candidate because Virtual PC 
can't initialize the virtual switch.
Any pointers would be much appreciated.

Or is there a better place to ask this?
Thanks,

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


Review of arcboot-installer template wanted

2004-06-10 Thread Alastair McKinstry
Hi,

I'm planning to include a patch to arcboot-installer,
for #241178, which posts a reminder note about prom variables.
(Assuming joeyh says ok).

Before I go stressing out all the translators, can people please
review the English version below?


Template: arcboot/prom_variables
Type: note
Description: Setting PROM variables for Arcboot
 If this is your first Linux installation on this machine, or if you have
repartitioned your hard drives, you will need to set certain variables
 in the PROM before the system will boot normally.
 .
 At the end of this installation phase, you will reboot your system.  When
 you do, select "Stop for Maintenance", then press "5" to enter the command

 monitor.  There, type the following commands:
 .
setenv SystemPartition 
scsi(${abootbus})disk(${abootid})rdisk(${abootlun})partition(8)

setenv OSLoadPartition 
scsi(${arootbus})disk(${arootid})rdisk(${arootlun})partition(${arootpart})

setenv OSLoader arcboot
setenv OSLoadFilename Linux
 .
 You will only need to do this once.  Afterwards, type "boot" or reboot the

 system to proceed.


Regards,
Alastair McKinstry


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



Processed: tags

2004-06-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> tags 244978 moreinfo
Bug#244978: Should apt-install usbutils if USB is found
Tags were: d-i
Tags added: moreinfo

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Need help..here for you-House dollars

2004-06-10 Thread Augusta Olson
How are you TOday
HERE IS THE LO.AN FOR YOU

I can strongly recommend a new company for your new HO.ME Dollars

http://www.reficom.com/b1a/index.php


NOW WE WILL SHOW YOU THE VA.LUE OF WHAT WE CAN DO FOR YOU
THANK-YOU FOR YOUR TIME


Bug#253640: USB drivers not loaded with 2.6 on powerpc

2004-06-10 Thread Colin Watson
On Thu, Jun 10, 2004 at 05:23:41PM +0200, Laurent Bigonville wrote:
> Package: debian-installer
> Severity: important
> 
> The usb driver doesn't seem to be loaded on my powermac when I boot 
> with the 2.6 kernel(sid daily-build).
> It's realy annoying with an usb keyboard...

Exactly which URL did you use to download this image? I added
input-modules to the initrd some days ago ...

-- 
Colin Watson  [EMAIL PROTECTED]


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



Bug#244978: is usbutils ever needed?

2004-06-10 Thread Alastair McKinstry
Hi,

I'm working on Debian bug #244978, which asks if usbutils
is needed for anything, or will hotplug suffice.

In /etc/hotplug/hotplug.functions, there is a note:
" usbmodules used for (a) multi-interface devices, (b) coldplug"

Do you know if usbutils is needed for multi-interface 
devices, or will hotplug suffice?

Regards
Alastair McKinstry



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



Bug#244886: kbd-chooser: can't select keymap on sparc64 netboot 20040411 image

2004-06-10 Thread Alastair McKinstry
Hi,

Can you please confirm whether or not you still see this problem?

I do not have access to a sparc machine and cannot debug
this without help

Regards
Alastair


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



Help! Debian-Installer Dies with various umount errors

2004-06-10 Thread [EMAIL PROTECTED]
I have tried the Beta 4 Sarge installer, Beta 4 Net Installer, and 
Testing Candidate 1 Net Install (all for i386) and my installs always 
die at Installing the Base System. (I always do a clean install, letting 
the installer use the entire disk).

Looking in the error logs, I see:
umount: /target/dev/pts: No such file or directory
umount: /target/dev/shm: No such file or directory
umount: /target/proc/bus/usb: Invalid argument
I also have Googled and searched the BTS, and I note that there are 
quite a few reports on multiple architectures that list this same 
issue BUT I can't find any resolution or work-around.

Can anyone point me in the right direction here? Why is this bug coming up?
I feel like I'm really in a weird twilight zone where everyone else 
seems to be doing fine with the new Debian Installer, but I keep running 
into this same problem

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


Bug#252930: Installation-Reports: Beta 4 as a VMware Guest

2004-06-10 Thread Thiemo Seufer
Joey Hess wrote:
> Thiemo Seufer wrote:
> > ~/.profile gets ignored, because $HOME is set to / instead of /root,
> > so it uses only the definitions in /etc/profile. (This also leaves
> > a .bash_history file in /.)
> 
> I thought that might be it too, but I cannot reproduce it in a sarge
> chroot with HOME unset. I think that bash looks at getpwent to find the
> home directory in this case.

For a unset HOME it seems to do that, but we have "HOME=/". I can
reproduce the bug with that setting.


Thiemo


signature.asc
Description: Digital signature


Bug#252930: Installation-Reports: Beta 4 as a VMware Guest

2004-06-10 Thread Joey Hess
Hmm, but setting HOME in base-config does fix it. Go figure. Perhaps
whatever bash used to get root's home in my chroot is not present during
a base-config run.

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#253536: debian-installer: Amd64 kernel updates

2004-06-10 Thread Joey Hess
Goswin von Brederlow wrote:
> Joey Hess <[EMAIL PROTECTED]> writes:
> 
> > Goswin von Brederlow wrote:
> >> Package: debian-installer
> >> Version: 20040528
> >> Severity: important
> >> Tags: patch
> >> Justification: fails to build from source
> >
> > Please stop using important as a severity for amd64 packages until amd64
> > is an official arch or there is a consensus that it's the right
> > severity.
> 
> Sorry but that is the consensus within the debian-amd64 team.  Our
> current notion of amd64 is "official but not a release architecture
> included on ftp.d.o".

Well I'm afraid that the amd64 team does not have the final say over
severities in the BTS. Every inflated severity bug report I receive just
wastes some of my time to downgrade it, and is then fixed as quickly as
it would be no matter what its severity.

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#252930: Installation-Reports: Beta 4 as a VMware Guest

2004-06-10 Thread Joey Hess
Thiemo Seufer wrote:
> ~/.profile gets ignored, because $HOME is set to / instead of /root,
> so it uses only the definitions in /etc/profile. (This also leaves
> a .bash_history file in /.)

I thought that might be it too, but I cannot reproduce it in a sarge
chroot with HOME unset. I think that bash looks at getpwent to find the
home directory in this case.

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#252930: Installation-Reports: Beta 4 as a VMware Guest

2004-06-10 Thread Joey Hess
Thiemo Seufer wrote:
> ~/.profile gets ignored, because $HOME is set to / instead of /root,
> so it uses only the definitions in /etc/profile. (This also leaves
> a .bash_history file in /.)

Ooh, now I get it, HOME is /. Why? Anyway, thanks for the analysis, and
fixed.

-- 
see shy jo


signature.asc
Description: Digital signature


Re: initrd.list output from build process

2004-06-10 Thread Thiemo Seufer
Colin Watson wrote:
[snip]
> @@ -572,8 +575,9 @@
>  # Create the images for dest/. Those are the targets called from config.
>  #
>  # Create a compressed image of the root filesystem by way of genext2fs.
> -$(INITRD): $(TEMP_INITRD)
> +$(INITRD): $(TEMP_INITRD) $(TEMP_INITRD_LIST)
>   install -m 644 -D $< $@
> + install -m 644 -D $(TEMP_INITRD_LIST) $(INITRD_LIST)
>   ./update-manifest $@ $(MANIFEST-INITRD)

You may want to add also

./update-manifest $(INITRD_LIST) $(MANIFEST-INITRD_LIST)

>  $(TEMP_INITRD): $(STAMPS)tree-$(targetstring)-stamp
> @@ -600,6 +604,8 @@
>   esac
>   gzip -v9f $(TEMP)/initrd
>  
> +$(TEMP_INITRD_LIST): $(STAMPS)tree-$(targetstring)-stamp

This should depend on $(TEMP_INITRD) for clarity.


Thiemo


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



Re: New amd64 Debian-installer cdrom iso image

2004-06-10 Thread Joey Hess
Goswin von Brederlow wrote:
> I have updated the sid-amd64-cdrom.iso on alioth to the latest D-I
> images, debs and udebs from alioth including a fixed sid console-data.
> 
> I managed to install and boot a debian system from the cdrom with one
> problem:
> 
> The init.d script of discover1 tries to rm /media/cdrom0/* which of
> course if read-only and fails (between installing base and grub).
> 
> After adding an exit 0 at the top of the script I was able to install
> grub and reboot the system into the freshly installed one.
> 
> 
> The image is available from: (ETA 45m)
> http://debian-amd64.alioth.debian.org/install-images/sid-amd64-cdrom.iso
> 
> 286a2279babf50bd09bf6427248e2efa 102871040 sid-amd64-cdrom.iso
> 
> 
> It would be nice if you could add amd64 to the status page with the
> businesscard CD and netboot CD both available and working.

I don't see a businesscard CD st that link, just a netinst. Do you plan
to make other images bseides CDs available? Maybe hd-media or something?
The ports status page has been updated.

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#253640: USB drivers not loaded with 2.6 on powerpc

2004-06-10 Thread Laurent Bigonville
Le 10 juin 2004, à 17:58, Colin Watson a écrit :
Exactly which URL did you use to download this image? I added
input-modules to the initrd some days ago ...
there:
http://cdimage.debian.org/pub/cdimage-testing/sid_d-i/powerpc/current/ 
sarge-powerpc-netinst.iso



PGP.sig
Description: =?ISO-8859-1?Q?Ceci_est_une_signature_=E9lectronique_PGP?=


Re: New amd64 Debian-installer cdrom iso image

2004-06-10 Thread Kurt Roeckx
On Thu, Jun 10, 2004 at 12:47:42PM -0400, Joey Hess wrote:
> > The image is available from: (ETA 45m)
> > http://debian-amd64.alioth.debian.org/install-images/sid-amd64-cdrom.iso
> 
> I don't see a businesscard CD st that link, just a netinst. Do you plan
> to make other images bseides CDs available? Maybe hd-media or something?
> The ports status page has been updated.

The d-i images I build are available at:
http://debian-amd64.alioth.debian.org/debian-installer/current/images/

Those are the "real" d-i images as build by the debian-installer
package.


Kurt


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



Bug#253683: TC1

2004-06-10 Thread Don Jackson (AE5K)
Package: installation-reports

Debian-installer-version: TC1, downloaded from 
 and shows version 20040528 on the 
help page.

uname -a: n/a
Date: 2004 Jun 10
Method: Booted from CD iso

Machine: FIC VA503+ motherboard
Processor: AMD K6-2 400 MHz
Memory: 128 MB
Root Device: IDE DVD writer HP DVD300i
Root Size/partition table: n/a
Output of lspci: n/a

Base System Installation Checklist:

Initial boot worked:[O]
Configure network HW:   [E ]
Config network: [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Create file systems:[ ]
Mount partitions:   [ ]
Install base system:[ ]
Install boot loader:[ ]
Reboot: [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems: Does not recognize my NIC which is a 
National/Anthem NE2000 compatible and uses ne.o driver.  Gave it the 
ne driver selection and IRQ=3 IO=0x340 params which work in existing 
Woody 2.2.20 version.  Comes back to not recognizing NIC.  Also tried 
"8390" and nothing happens.

Appears to be a nice "start", but cannot comment further until I get 
past 1st base ;-)

Don



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



Re: kernel oops decoder

2004-06-10 Thread Joey Hess
Geert Stappers wrote:
> On Wed, Jun 09, 2004 at 04:42:36PM -0400, Joey Hess wrote:
> > Geert Stappers wrote:
> > > Two attempts with 20040608 images failed in kernels oopses.
> > > 
> > > Attempts with 20040607 had also OOPSES at several places,
> > > but did bring me to debian base system install.
> > 
> > Kernel oopses are of course either a kernel problem or a hardware
> > problem, and so the rest of the problems seem likely to be related. So
> > which is it, kernel or hardware? Get that oops decoder out..
> 
> Please tell me and the other lurkers here more
> how to decode kernel oopses in debian-installer.
> 
> For what I see, is that the package ksymoops is needed at the target system.

Well we use the stock debian i386 kernel, so you just get another system
with that kernel and run ksymoops on the oops output there.

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#253211: Fix and some thoughts [Was: Bug#253211: Problems with the screen display in second stage]

2004-06-10 Thread Joey Hess
Christian Perrier wrote:
> (1) means reverting Kenshi Muto changes to termwrap. These were needed
> by different console font handling in 2.6 and 2.4 which lead to broken
> dialog boxes in 2.6 installs (boxes bordered with "strange"
> characters). This has a drawback-->we need termwrap to behave
> differently with 2.4 and 2.6 kernels

Yes, that's what I'm leaning toward doing: Make it it check the running
kernel version and do different things.

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#253687: installation-reports

2004-06-10 Thread Jean-Baptiste Rouquier
Package: installation-reports
Debian-installer-version: downloaded June 3, 2004 from 
http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/tc1/sarge-i386-netinst.iso
uname -a: Linux galdo 2.4.26-1-386 #2 Sat May 1 16:31:24 EST 2004 i686 GNU/Linux
Date: June 4, 2004, 8 am to 10 am (local time: Paris)
Method: boot on freshly burnt RW CD (110Mo). no proxy.
Machine: HP NX9005 laptop
Processor: AMD Athlon 2400+
Memory:708Mo RAM (460Mo recognized)
Root Device: Toshiba MK3021GAS, ide
Root Size/partition table: 30Go
/dev/hda3  ext3  4316Mo /  (linux system)
/dev/hda5  vfat 17994Mo /home/jrouquie/windows (my data)
/dev/hda6  swap   346Mo none   (swap)
/dev/hda? ntfs ~5000Mo (windows system)

Output of lspci:
pcilib: Cannot open /sys/bus/pci/devices
:00:00.0 Host bridge: ATI Technologies Inc AGP Bridge [IGP 320M] (rev 13)
:00:01.0 PCI bridge: ATI Technologies Inc PCI Bridge [IGP 320M] (rev 01)
:00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
:00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller 
Audio Device (rev 02)
:00:07.0 ISA bridge: ALi Corporation M1533 PCI to ISA Bridge [Aladdin IV]
:00:08.0 Modem: ALi Corporation Intel 537 [M5457 AC-Link Modem]
:00:09.0 Network controller: Harris Semiconductor Prism 2.5 Wavelan chipset (rev 
01)
:00:0a.0 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller (rev 01)
:00:0a.1 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller (rev 01)
:00:0c.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 
Controller (PHY/Link)
:00:10.0 IDE interface: ALi Corporation M5229 IDE (rev c4)
:00:11.0 Bridge: ALi Corporation M7101 PMU
:00:12.0 Ethernet controller: National Semiconductor Corporation DP83815 
(MacPhyter) Ethernet Controller
:01:05.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility U1
:04:00.0 USB Controller: NEC Corporation USB (rev 43)
:04:00.1 USB Controller: NEC Corporation USB (rev 43)
:04:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
Base System Installation Checklist:
Initial boot worked:[O]
Configure network HW:   [ ]
Config network: [O]
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:[O]
Install boot loader:[O]
Reboot: [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
Great work ! I was afraid of installing Debian, but the installation went good and 
easy. Thanks !
Dual boot with windows.
I got the known bug of keybord not responding and used the classic workaround of 
repeatedly pressing caps-lock while booting for the installation.
I didn't tried all the devices (usb, wifi, ...).
cdrom fails to eject under kde (read fine), I didn't tried to fix the problem.
Thanks again,
Jean-Baptiste Rouquier. 


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


Re: New amd64 Debian-installer cdrom iso image

2004-06-10 Thread Joey Hess
Kurt Roeckx wrote:
> The d-i images I build are available at:
> http://debian-amd64.alioth.debian.org/debian-installer/current/images/
> 
> Those are the "real" d-i images as build by the debian-installer
> package.

If you would build those using the installer/build/daily-build script,
then I could add them to the build tracking page
(http://people.debian.org/~joeyh/d-i/build-logs.html).

Which reminds me: Would someone like to set up a new powerpc daily
build? I'm tired of waiting for Sven to fix his build so it will appear
on the above page, and the lack of tracking of build failures cannot be
good for the powerpc port.

Anyway, I've added them to the ports status page, though they're all
marked as only "building" since I don't know which images work except
for the CD image.

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#244978: is usbutils ever needed?

2004-06-10 Thread Frans Pop
On Thursday 10 June 2004 17:51, Alastair McKinstry wrote:
> Do you know if usbutils is needed for multi-interface
> devices, or will hotplug suffice?

/etc/hotplug/usb.rc contains the following code

LISTER=`which usbmodules`
if [ "$LISTER" = "" -o ! -f /proc/bus/usb/devices ]; then
echo "** can't synthesyze root hub events"
return
fi


usbmodules is a part of package usbutils.

But see also the comment just above that code which says the dependency on 
usbmodules should be dropped (starting kernel version 2.5?).
(I guess there should be a test for kernelversion in this script...)

Currently though I guess it's still needed (and not installed by default).

Hope this helps.
FJP


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



Re: Install via PPPoE

2004-06-10 Thread Joey Hess
Arthur Wiebe wrote:
> I haven't been able to find any info on how to install Sarge through the 
> Internet using PPPoE to connect. Is this possible yet? If so how? I 
> haven't been able to test the latest test candidate because Virtual PC 
> can't initialize the virtual switch.
> Any pointers would be much appreciated.

Try http://dsl.linux.it/DebianNetinstall

-- 
see shy jo


signature.asc
Description: Digital signature


Re: Help! Debian-Installer Dies with various umount errors

2004-06-10 Thread Joey Hess
[EMAIL PROTECTED] wrote:
> I have tried the Beta 4 Sarge installer, Beta 4 Net Installer, and 
> Testing Candidate 1 Net Install (all for i386) and my installs always 
> die at Installing the Base System. (I always do a clean install, letting 
> the installer use the entire disk).
> 
> Looking in the error logs, I see:
> 
> umount: /target/dev/pts: No such file or directory
> umount: /target/dev/shm: No such file or directory
> umount: /target/proc/bus/usb: Invalid argument

These are not errors. You need to look further up in the log for the
actual error message.

-- 
see shy jo


signature.asc
Description: Digital signature


Processed: netcfg

2004-06-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> reassign 253683 netcfg
Bug#253683: TC1
Bug reassigned from package `ethdetect' to `netcfg'.

> --
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Processed: Re: Bug#253575: Default partitioning doesn't create a space for ELILO

2004-06-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> tag 253575 d-i
Bug#253575: Default partitioning doesn't create a space for ELILO
There were no tags set.
Tags added: d-i

> clone 253575 -1
Bug#253575: Default partitioning doesn't create a space for ELILO
Bug 253575 cloned as bug 253696.

> clone 253575 -2
Bug#253575: Default partitioning doesn't create a space for ELILO
Bug 253575 cloned as bug 253697.

> reassign -1 kernel-image-2.6.4-ia64
Bug#253696: Default partitioning doesn't create a space for ELILO
Bug reassigned from package `installation-reports' to `kernel-image-2.6.4-ia64'.

> retitle -1 does not depend on module-init-tools
Bug#253696: Default partitioning doesn't create a space for ELILO
Changed Bug title.

> reassign -2 partman-auto
Bug#253697: Default partitioning doesn't create a space for ELILO
Bug reassigned from package `installation-reports' to `partman-auto'.

> retitle -2 needs ia64 specific recipe for elilo fat16 partition
Bug#253697: Default partitioning doesn't create a space for ELILO
Changed Bug title.

> reassign 253575 netcfg
Bug#253575: Default partitioning doesn't create a space for ELILO
Bug reassigned from package `installation-reports' to `netcfg'.

> retitle 253575 does not say how to use different port on mirror, has ia64 mirrors
Bug#253575: Default partitioning doesn't create a space for ELILO
Changed Bug title.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Processed: reassign 253683 to ethdetect

2004-06-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 253683 ethdetect
Bug#253683: TC1
Bug reassigned from package `installation-reports' to `ethdetect'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Processing of base-config_2.27_i386.changes

2004-06-10 Thread Archive Administrator
base-config_2.27_i386.changes uploaded successfully to localhost
along with the files:
  base-config_2.27.dsc
  base-config_2.27.tar.gz
  base-config_2.27_all.deb

Greetings,

Your Debian queue daemon


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



Bug#253683: TC1

2004-06-10 Thread Martin Michlmayr
* Don Jackson (AE5K) <[EMAIL PROTECTED]> [2004-06-10 12:35]:
> Comments/Problems: Does not recognize my NIC which is a 
> National/Anthem NE2000 compatible and uses ne.o driver.  Gave it the 
> ne driver selection and IRQ=3 IO=0x340 params which work in existing 
> Woody 2.2.20 version.  Comes back to not recognizing NIC.  Also tried 
> "8390" and nothing happens.

Can you open a shell on the 2nd virtual console and check if the
module has successfully been loaded?
-- 
Martin Michlmayr
[EMAIL PROTECTED]


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



Bug#253575: Default partitioning doesn't create a space for ELILO

2004-06-10 Thread Joey Hess
tag 253575 d-i
clone 253575 -1
clone 253575 -2
reassign -1 kernel-image-2.6.4-ia64
retitle -1 does not depend on module-init-tools
reassign -2 partman-auto
retitle -2 needs ia64 specific recipe for elilo fat16 partition
reassign 253575 netcfg
retitle 253575 does not say how to use different port on mirror, has ia64 mirrors
thanks

Peter Chubb wrote:
> 2.  If you select a 2.6 kernel you need to have module-init-tools
> installed, which doesn;t happen by default.  Otherwise the
> installation of the kernel fails when depmod is run.

On i386 the 2.6 kernel packages depend on module-init-tools. It seems
that this is not the case with eg, kernel-image-2.6.4-itanium.

> 3.  (The biggy).  The default partitioning doesn't leave a FAT16
> partition at the start of the disc for elilo to install a boot image
> on.

The new version of partman-auto has support for architecture specific
things like this, so this could be fixed there as it was for powerpc,
iirc. You can work around this by doing manual partitioning and setting
up the fat16 partition by hand, I presume.

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#253683: TC1

2004-06-10 Thread Joey Hess
Don Jackson (AE5K) wrote:
> Output of lspci: n/a

Why did you not provide this information? Unless your NIC is not a PCI
device, it's very important information we need to solve your problem.

> Comments/Problems: Does not recognize my NIC which is a 
> National/Anthem NE2000 compatible and uses ne.o driver.  Gave it the 
> ne driver selection and IRQ=3 IO=0x340 params which work in existing 
> Woody 2.2.20 version.  Comes back to not recognizing NIC.  Also tried 
> "8390" and nothing happens.

Do you have any messages from dmesg that might be useful in determining
why the kernel isn't finding your NIC even when you load the right
module with the right settings?

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#244978: is usbutils ever needed?

2004-06-10 Thread Joey Hess
Alastair McKinstry wrote:
> I'm working on Debian bug #244978, which asks if usbutils
> is needed for anything, or will hotplug suffice.
> 
> In /etc/hotplug/hotplug.functions, there is a note:
> " usbmodules used for (a) multi-interface devices, (b) coldplug"
> 
> Do you know if usbutils is needed for multi-interface 
> devices, or will hotplug suffice?

I don't know much about this stuff, but I've been told that on the 2.6
kernel, lack of usbutils results in hotplug complaining that it "can't
synthesize root hub events". After that report, I made hw-detect
apt-install usbutils when apt-installing hotplug. I think that's a
better place than usb-discover, probably. So this bug can be closed..

-- 
see shy jo


signature.asc
Description: Digital signature


Re: Help! Debian-Installer Dies with various umount errors

2004-06-10 Thread Joey Hess
Ralph Crongeyer wrote:
> I had simalar issues on one machine. It looks like the installer can't 
> read from the disk at some point. Anyway try a different/newer CDROM 
> drive. It worked for me.

Actually, since [EMAIL PROTECTED] did not include any real error
messages in his report, there is no way to tell if he experienced a
problem similar to yours or not. Jumping tyo the kind of conclusion you
did is not good diagnostics.

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#253211: marked as done (No line box drawing characters in 2.4 installs for Latin languages)

2004-06-10 Thread Debian Bug Tracking System
Your message dated Thu, 10 Jun 2004 14:32:02 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#253211: fixed in base-config 2.27
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; 7 Jun 2004 21:55:14 +
>From [EMAIL PROTECTED] Mon Jun 07 14:55:14 2004
Return-path: <[EMAIL PROTECTED]>
Received: from smtp.netizen.com.ar [200.49.100.81] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BXS5J-0003WC-00; Mon, 07 Jun 2004 14:55:14 -0700
Received: from apolo.home (host-221.8.60.66-ta.adsl.netizen.com.ar [66.60.8.221])
by smtp.netizen.com.ar (Postfix) with ESMTP id 433B7186A32
for <[EMAIL PROTECTED]>; Mon,  7 Jun 2004 18:39:10 -0300 (ART)
Received: from ulises.home ([192.168.13.13] ident=mail)
by apolo.home with esmtp (Exim 3.35 #1 (Debian))
id 1BXS4k-0005Dm-00
for <[EMAIL PROTECTED]>; Mon, 07 Jun 2004 18:54:38 -0300
Received: from marga by ulises.home with local (Exim 3.36 #1 (Debian))
id 1BXS4f-0003pl-00
for <[EMAIL PROTECTED]>; Mon, 07 Jun 2004 18:54:33 -0300
Date: Mon, 7 Jun 2004 18:54:33 -0300
From: Margarita Manterola <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Problems with the screen display in second stage
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.5.1+cvs20040105i
Sender: Margarita Manterola <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: installation-reports
Severity: normal

Hi! I tested the daily-build floppies installation on a normal computer,
with network access.  

Everything went quite fine, but when it rebooted, the screen was broken.
Not as before, instead of showing messy characters in place of the
borders, there were no borders at all.

I might be wrong, but I think this floppies use linux 2.4, and the
problem we were having (messy characters in the borders in second stage) 
only happened with linux 2.6.  

As a remainder, the fix to the old problem was to execute:
consolechars lat0-sun16.psf.gz 
when the encoding was ISO-8859-1.

I think this might be useful to fix the present problem.

-- 
 Bezos, (o.
 Marga. (/)_

---
Received: (at 253211-close) by bugs.debian.org; 10 Jun 2004 18:38:23 +
>From [EMAIL PROTECTED] Thu Jun 10 11:38:23 2004
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BYURT-Gj-00; Thu, 10 Jun 2004 11:38:23 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1BYULK-0007DD-00; Thu, 10 Jun 2004 14:32:02 -0400
From: Joey Hess <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.49 $
Subject: Bug#253211: fixed in base-config 2.27
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 10 Jun 2004 14:32:02 -0400
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Score: 2

Source: base-config
Source-Version: 2.27

We believe that the bug you reported is fixed in the latest version of
base-config, which is due to be installed in the Debian FTP archive:

base-config_2.27.dsc
  to pool/main/b/base-config/base-config_2.27.dsc
base-config_2.27.tar.gz
  to pool/main/b/base-config/base-config_2.27.tar.gz
base-config_2.27_all.deb
  to pool/main/b/base-config/base-config_2.27_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joey Hess <[EMAIL PROTECTED]> (supplier of updated base-config package)

(This message was generated automatically at their request; if you
believe that there is a problem wit

Re: Help! Debian-Installer Dies with various umount errors

2004-06-10 Thread Ralph Crongeyer




I had simalar issues on one machine. It looks like the installer can't
read from the disk at some point. Anyway try a different/newer CDROM
drive. It worked for me.

Ralph

Joey Hess wrote:

  [EMAIL PROTECTED] wrote:
  
  
I have tried the Beta 4 Sarge installer, Beta 4 Net Installer, and 
Testing Candidate 1 Net Install (all for i386) and my installs always 
die at Installing the Base System. (I always do a clean install, letting 
the installer use the entire disk).

Looking in the error logs, I see:

umount: /target/dev/pts: No such file or directory
umount: /target/dev/shm: No such file or directory
umount: /target/proc/bus/usb: Invalid argument

  
  
These are not errors. You need to look further up in the log for the
actual error message.

  






base-config_2.27_i386.changes ACCEPTED

2004-06-10 Thread Debian Installer

Accepted:
base-config_2.27.dsc
  to pool/main/b/base-config/base-config_2.27.dsc
base-config_2.27.tar.gz
  to pool/main/b/base-config/base-config_2.27.tar.gz
base-config_2.27_all.deb
  to pool/main/b/base-config/base-config_2.27_all.deb
Announcing to [EMAIL PROTECTED]
Closing bugs: 252930 253211 


Thank you for your contribution to Debian.


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



Bug#252930: marked as done (still PATH problems in shell menu item)

2004-06-10 Thread Debian Bug Tracking System
Your message dated Thu, 10 Jun 2004 14:32:02 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#252930: fixed in base-config 2.27
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; 6 Jun 2004 02:11:26 +
>From [EMAIL PROTECTED] Sat Jun 05 19:11:26 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mail.keyway.net [216.117.199.18] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BWn8A-0007Q6-00; Sat, 05 Jun 2004 19:11:26 -0700
Received: from [192.168.1.241] (ip-216-117-212-48.keyway.net [216.117.212.48])
by mail.keyway.net (8.12.11/8.12.11) with ESMTP id i562BTle039979
for <[EMAIL PROTECTED]>; Sat, 5 Jun 2004 19:11:30 -0700 (PDT)
Message-ID: <[EMAIL PROTECTED]>
Date: Sat, 05 Jun 2004 19:11:20 -0700
From: Satchmo Dancelegs <[EMAIL PROTECTED]>
User-Agent: Mozilla Thunderbird 0.6+ (X11/20040503)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: Installation-Reports: Beta 4 as a VMware Guest
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_01,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: installation-reports

Debian-installer-version: Beta 4, 110 MB CD image, (with Debian base)
  06/03/04   http://www.debian.org/devel/debian-installer/
uname -a: Linux cliffisle3 2.4.25-1-386 #2 Wed Apr 14 19:38:08 EST 2004 i686 GNU/Linux
Date: 06/03/04  13:00 EDT
Method: 110 MB CD image, (with Debian base) booted from CD-ROM

Machine: Generic Desktop - VMware Guest
Processor:   Athlon 2200+
Memory:  512 Mb -  256 Mb devoted to VMware Guest
Root Device: Actual: 5Gb (Max) file on SATA device VMware: SCSI  /dev/sda
Root Size/partition table: (Inside VMware Guest)
Disk /dev/sda: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End  Blocks   Id  System  MountPt
/dev/sda1   *  1  621 4988151   83  Linux  /
/dev/sda2622  652  249007+   5  Extended  none 
/dev/sda5622  652  248976   82  Linux swapnone 
 
Output of lspci: (Inside VMware Guest)
pcilib: Cannot open /sys/bus/pci/devices
:00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 01)
:00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 01)
:00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 08)
:00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
:00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB
:00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 08)
:00:0f.0 VGA compatible controller: VMWare Inc [VMWare SVGA II] PCI Display Adapter
:00:10.0 SCSI storage controller: BusLogic BT-946C (BA80C30) [MultiMaster 10] (rev 
01)
:00:11.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] 
(rev 10)
:00:12.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 02)


Base System Installation Checklist:

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
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:[O]
Install boot loader:[O]
Reboot: [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems: 
After I got VMware to recognize my CD-ROM drive, the initial install went without a 
hitch. Took about
30 mins, and could have gone faster if I hadn't stopped to check out the installer 
along the way.
I was a little shy about letting the installer auto-partition the drive, as this is a 
Virtual Drive inside
VMware, so I parititioned manually, and it went fine. Everything went as advertised, 
and it was a very
pleasant experience. As a matter of fact, it was the quickest install ever. 

The rest of the day was spent in getting X11 downloaded (350Mb takes a while) & up, 
but everything went pretty well.

only PROBLEM: Root did not have /sbin in $PATH during tasksel install, I had to move 

Re: New amd64 Debian-installer cdrom iso image

2004-06-10 Thread Ben Kochie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

is there any chance that amd64 is going to get a build/install option for
sarge any time soon?

- -ben

 "Unix is user friendly, Its just picky about its friends."

On Thu, 10 Jun 2004, Goswin von Brederlow wrote:

> Hi,
>
> I have updated the sid-amd64-cdrom.iso on alioth to the latest D-I
> images, debs and udebs from alioth including a fixed sid console-data.
>
> I managed to install and boot a debian system from the cdrom with one
> problem:
>
> The init.d script of discover1 tries to rm /media/cdrom0/* which of
> course if read-only and fails (between installing base and grub).
>
> After adding an exit 0 at the top of the script I was able to install
> grub and reboot the system into the freshly installed one.
>
>
> The image is available from: (ETA 45m)
> http://debian-amd64.alioth.debian.org/install-images/sid-amd64-cdrom.iso
>
> 286a2279babf50bd09bf6427248e2efa 102871040 sid-amd64-cdrom.iso
>
>
> It would be nice if you could add amd64 to the status page with the
> businesscard CD and netboot CD both available and working.
>
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAyK+zflzKmtpiQEMRAqU4AJ9548sVbZMKabtXT7c/3sdJ+0ksEwCcDRxp
0OXqS9z8U025bjYcF0vqdl0=
=q66w
-END PGP SIGNATURE-


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



Bug#253709: (no subject)

2004-06-10 Thread Heikki Lindholm


Package: installation-reports

INSTALL REPORT

Debian-installer-version:
Used the 
http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/tc1/sarge-i386-netinst.iso
image downloaded at 9th June 2004.

uname -a: Linux (none) 2.4.26-1-386 #2 Sat May 1 16:31:24 EST 2004 i686 unknown
Date: 9th June 2004
Method: How did you install?  What did you boot off?  If network
  install, from where?  Proxied?
Network install (debian mirror ftp.fi.debian.org) booted off from the
above-mentioned CD-image in the machine's internal CD-drive. No proxy used.

Machine: Fujitsu/Siemens Lifebook S5582
Processor: Intel Pentium III-M 800MHz
Memory: 256MB
Root Device: /dev/hda Fujitsu 20GB IDE disk
Root Size/partition table:
/dev/hda1 19G  Linux
/dev/hda2  W95 Ext'd (LBA)
/dev/hda5 512M Linux swap

Output of lspci and lspci -n:
:00:00.0 Host bridge: Intel Corp. 82440MX Host Bridge (rev 01)
:00:00.1 Multimedia audio controller: Intel Corp. 82440MX AC'97 Audio Controller
:00:00.2 Modem: Intel Corp. 82440MX AC'97 Modem Controller
:00:07.0 Bridge: Intel Corp. 82440MX ISA Bridge (rev 01)
:00:07.1 IDE interface: Intel Corp. 82440MX EIDE Controller
:00:07.2 USB Controller: Intel Corp. 82440MX USB Universal Host Controller
:00:07.3 Bridge: Intel Corp. 82440MX Power Management Controller
:00:11.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 
Controller (PHY/Link)
:00:12.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ (rev 10)
:00:13.0 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller (rev 02)
:00:13.1 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller (rev 02)
:00:14.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M (rev 64)



:00:00.0 Class 0600: 8086:7194 (rev 01)
:00:00.1 Class 0401: 8086:7195
:00:00.2 Class 0703: 8086:7196
:00:07.0 Class 0680: 8086:7198 (rev 01)
:00:07.1 Class 0101: 8086:7199
:00:07.2 Class 0c03: 8086:719a
:00:07.3 Class 0680: 8086:719b
:00:11.0 Class 0c00: 104c:8026
:00:12.0 Class 0200: 10ec:8139 (rev 10)
:00:13.0 Class 0607: 1217:6933 (rev 02)
:00:13.1 Class 0607: 1217:6933 (rev 02)
:00:14.0 Class 0300: 1002:4c52 (rev 64)



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

Comments/Problems:

Rootfs was chosen as XFS. GRUB warning came out and was ignored and when the
boot loader install came up, it halted. In its virtual console it said it was
"Probing devices to guess BIOS drives". Couple of CTRL-C's brought up the same
message again and again. After 10 minutes no progress. Swithing to other
console and killing the GRUB process by hand (kill -TERM) helped and install
continued flawlessly and GRUB booted from HD just fine!

Once you have filled out this report, mail it to [EMAIL PROTECTED]


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



Re: initrd.list output from build process

2004-06-10 Thread Colin Watson
On Thu, Jun 10, 2004 at 06:25:18PM +0200, Thiemo Seufer wrote:
> Colin Watson wrote:
> > @@ -572,8 +575,9 @@
> >  # Create the images for dest/. Those are the targets called from config.
> >  #
> >  # Create a compressed image of the root filesystem by way of genext2fs.
> > -$(INITRD): $(TEMP_INITRD)
> > +$(INITRD): $(TEMP_INITRD) $(TEMP_INITRD_LIST)
> > install -m 644 -D $< $@
> > +   install -m 644 -D $(TEMP_INITRD_LIST) $(INITRD_LIST)
> > ./update-manifest $@ $(MANIFEST-INITRD)
> 
> You may want to add also
> 
>   ./update-manifest $(INITRD_LIST) $(MANIFEST-INITRD_LIST)

I was hoping to avoid that, since I thought that would mean I'd have to
set MANIFEST-INITRD_LIST in all the .cfg files. Maybe I can just set
MANIFEST-INITRD_LIST = "contents of initrd" in config/common and leave
it at that, though.

> >  $(TEMP_INITRD): $(STAMPS)tree-$(targetstring)-stamp
> > @@ -600,6 +604,8 @@
> > esac
> > gzip -v9f $(TEMP)/initrd
> >  
> > +$(TEMP_INITRD_LIST): $(STAMPS)tree-$(targetstring)-stamp
> 
> This should depend on $(TEMP_INITRD) for clarity.

Good point. Thanks.

-- 
Colin Watson  [EMAIL PROTECTED]


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



Re: New amd64 Debian-installer cdrom iso image

2004-06-10 Thread Kurt Roeckx
On Thu, Jun 10, 2004 at 02:15:33PM -0400, Joey Hess wrote:
> 
> If you would build those using the installer/build/daily-build script,
> then I could add them to the build tracking page
> (http://people.debian.org/~joeyh/d-i/build-logs.html).

It's now available from:
http://debian-amd64.alioth.debian.org/debian-installer/daily


Kurt


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



Re: Re: Installer fails on initrd-tools

2004-06-10 Thread Dan C
On Wed, 2004-06-09 at 12:52 -0400, Joey Hess wrote:
> Dan C wrote:
> > + rootpart_devfs=/dev/ide/host0/bus0/target0/lun0/part1156681320
> It seems that base-installer finds the root partition by the rather
> broken method of doing a "df /target". I assume that you have a large
> root partition, of more than 100 gb in size, and probably the df
> output does not add whitespace between the partition name and the size
> in this case. Can you show the output of the df /target command to
> verify this?

That's it. I don't know why I didn't catch this myself and (properly)
report the error, but df /target returns:
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/ide/host0/bus0/target0/lun0/part1157076776 36284 149061412
0% /target
with the -h flag
/dev/ide/host0/bus0/target0/lun0/part1 149.8G 44.9M 142.1G 0% /target

Considering "One large / partition" is what d-i advises for new users,
and that's the option I picked to generate the above partition sizes,
this looks like a rather critical issue :)

Thanks for your response and assistance!
-Dan C

Further, it looks like [EMAIL PROTECTED] ( "Help! Debian-Installer
Dies with various umount errors" ) may be experiencing the same issue --
of particular interest is the "clean install, letting the installer use
the entire disk."


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



Re: Help! Debian-Installer Dies with various umount errors

2004-06-10 Thread Dan Callahan
On Thu, 2004-06-10 at 12:34 -0400, [EMAIL PROTECTED] wrote:
> I have tried the Beta 4 Sarge installer, Beta 4 Net Installer, and 
> Testing Candidate 1 Net Install (all for i386) and my installs always 
> die at Installing the Base System. (I always do a clean install, letting 
> the installer use the entire disk).

How large is your disk? I was running into similar issues, and it turns
out base-installer at some point runs `df /target/` to determine the
target disk. If your disk is large enough, the "1k-blocks" column runs
into the "Filesystem" column, adding all manner of digits to the end of
the filesystem address.

My email on the issue is under the subject "Installer fails on
initrd-tools"

-Dan C


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



Bug#253418: Installation report

2004-06-10 Thread Martin Michlmayr
* Gabriel Kerneis <[EMAIL PROTECTED]> [2004-06-09 12:51]:
> I got an error message when i tried to use LVM at the partition step. It 
> seemed to be impossible for the partitions wasn't created or something 
> like that but he asked just before whether i wanted to create the 
> partitions... Anyway i don't reallly neeed LVM but i wanted to try it.

What exactly was wrong with LVM.  Can you mention the steps in which
you tried to set it up?
-- 
Martin Michlmayr
[EMAIL PROTECTED]


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



Bug#253312: Installation failure for XFS over LVM on Test1 Sarge Netinstall CD

2004-06-10 Thread Martin Michlmayr
* Samuel P Howard <[EMAIL PROTECTED]> [2004-06-08 11:11]:
> Root Size/partition table: LVM (see comments below for config)
> Basic CD Netinst (no boot options).
> Configured 2 x 120GB HD's the same.
> Configured the whole disk for LVM.
> Created 1 VG (rootvg).
> Created 3 LV's: boot (50M), root (10G), local (100+GB remainder).

root on LVM is currently not supported, and you should have received a
warning about this.  Did you not get this?

-- 
Martin Michlmayr
[EMAIL PROTECTED]


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



Re: Install via PPPoE

2004-06-10 Thread Arthur Wiebe
Joey Hess wrote:
Arthur Wiebe wrote:
 

I haven't been able to find any info on how to install Sarge through the 
Internet using PPPoE to connect. Is this possible yet? If so how? I 
haven't been able to test the latest test candidate because Virtual PC 
can't initialize the virtual switch.
Any pointers would be much appreciated.
   

Try http://dsl.linux.it/DebianNetinstall
 

That web page mentions nothing about PPPoE. Just PPP modems. I need to 
connect via an Ethernet card using the PPPoE (PPP Over Ethernet) 
protocol, not though a modem.

I read that the Linux 2.6 kernel has built in support for PPPoE and that 
the debian installer was going to have built in support for this, 
probably using pppoeconf or like it.

Thanks anyway.

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


Jochen Eversmeier ist außer Haus.

2004-06-10 Thread Jochen_Eversmeier
Ich werde ab  08.06.2004 nicht im Büro sein. Ich kehre zurück am
21.06.2004.

Bitte wenden Sie sich in meiner Abwesenheit in dringenden Fällen an unsere
Zentrale unter Telefon 0 40/3 80 80-3 33.



Bug#252164: Package: installation-reports

2004-06-10 Thread Martin Michlmayr
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2004-06-02 22:21]:
> OK, I went back through the steps.  Indeed I did all of 1 through 5 in 
> the correct order.  I can't for the life of me figure out 6.  In the main 
> menu of Partition Disks, I can see all partitions including the two 
> lvm partitions, but I can't see the vg they are both assigned to and I 
> can't see the lv I created in the vg.  How do I select each lv so I can 
> assign it's filesystem and mount point?

You should see entries like:
   LVM VG foo, LV bar
   #1 ...
for every LV you create.

Can you open a shell on alt-f2 and check with vgscan and lvscan if
those VGs & LVs have really been created?
-- 
Martin Michlmayr
[EMAIL PROTECTED]


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



Re: Install via PPPoE

2004-06-10 Thread Marco d'Itri
[EMAIL PROTECTED] wrote:

>> I haven't been able to find any info on how to install Sarge through the 
>> Internet using PPPoE to connect. Is this possible yet? If so how? I 
>> haven't been able to test the latest test candidate because Virtual PC 
>> can't initialize the virtual switch.
>> Any pointers would be much appreciated.
>Try http://dsl.linux.it/DebianNetinstall
No, this is totally unrelated and PPPoE is not discussed there.

Only ppp-udeb and the ppp kernel modules udeb are needed for a PPPoE
install, but I do not know which images provide them.

-- 
ciao,
Marco


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



Bug#253724: daily-20040515: some suggestions and typos

2004-06-10 Thread Peter Cordes
Package: installation-reports
Severity: normal

INSTALL REPORT

Debian-installer-version: 20040515 daily build for i386
uname -a: Linux nb-Spencer 2.4.26-1-386 #2 Sat May 1 16:31:24 EST 2004 i686 GNU/Linux
Date: 2004/05/17, ~1500h ADT.
Method: booted netinst CD (2.4 kernel)

Machine: P4 desktop, non-HT 2.8GHz Pentium 4 (Northwood), 512MB RAM.
nb-Spencer:~# fdisk -l /dev/hda
Disk /dev/hda: 40.0 GB, 40060403712 bytes
255 heads, 63 sectors/track, 4870 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
/dev/hda1   1247819904503+   7  HPFS/NTFS
/dev/hda2   *2479480818715725   83  Linux   <- root dev
/dev/hda348094870  498015f  W95 Ext'd (LBA)
/dev/hda548094870  497983+  82  Linux swap
Output of lspci and lspci -n:  only ones of interest are:
:00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast 
Ethernet (rev 91)
:00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ (rev 10)
:01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 65x/M650/740 
PCI/AGP VGA Display Adapter

:00:04.0 Class 0200: 1039:0900 (rev 91)
:00:0d.0 Class 0200: 10ec:8139 (rev 10)
:01:00.0 Class 0300: 1039:6325


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

Comments/Problems:

 I conf'ed the network manually because udhcpc doesn't work at my site.  (the
far-superior dhclient in the test-candidate version works fine, so good job
getting that working.)  I was worried that wanting to use eth1 would be a
problem, but the menu to choose which nic worked great. :)

 GRUB installed fine, but it didn't have an entry for the winxp partition.
(which was re-sized and the disk repartitioned before I booted the
debian-installer).  I haven't re-tested with the test-candidate installer on
a machine that has a windoze partition, so I don't know if this is still a
problem.  I had to manually add the winxp partition to my GRUB menu.lst.
GRUB's config file has some typos: "default optons", and "specifiv".

 I also have some comments on base-config and the various packages' postinst
scripts: 
- The add user dialog had two versions of the same sentence: "Enter a full
name for the new user" displayed in the same dialog box.  I don't remember
if this is fixed in the test-candidate.

- /etc/hosts doesn't have entries for ip6-localhost, etc.  netbase's
postinst is supposed to add them.

- the installer never asked for a debconf question-ignore priority level.
I haven't made up my mind whether that's a bad thing or not.

X11:
-- X was set up for 800x600 and 640x480, even though the machine has a
1024x768 LCD screen (LG L1511S).  butt-ugly :(  I wish it used ddc-probed
monitor information, or at least read it with get-edid | parse-edid and put
that info into a dialog box.
-- I had to do a dpkg-reconfigure xserver-xfree86 to get a decent X setup.
It complained about  "cannot open /sys/bus/pci/devices", since I wasn't
running Linux 2.6, but it worked anyway.  It still didn't use probed values
for hsync and vsync, which is dumb on reconfig because all the binaries are
there for it to use to do any probing.  I don't remember everything I did,
but my notes indicate that after dpkg-reconfigure, the hsync/vrefresh values
were closer to the probed ones, and that the X server log file had a warning
line about "config file hsync range not within DDC".  I manually editted
XF86Config-4 after that.
-- The mouse setup (/dev/psaux and /dev/input/mice) will give a double-speed
mouse pointer if you run a 2.6 kernel with input support for ps/2 mice.
(The X server will get the mouse motion twice, once from each device file).
I don't know a way to write a config file that works well for 2.4 and 2.6 :(

 In short, the major hurdle for people who don't already know what they're
doing will be getting X running.  Modern hardware is so easily
autodetectable that it seems odd that the installer doesn't do as well with
X as with everything else.  (I guess Brandon's X stuff doesn't have anything
to do with debian-installer, but people setting up desktop machines do need
to configure X.  It looks like that's by far the hardest thing for a typical
desktop install, in terms of requiring detailed knowledge of how things are
supposed to work, and all your hardware specs.).

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-386
Locale: LANG=en_CA, LC

Re: Install via PPPoE

2004-06-10 Thread Frans Pop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday 10 June 2004 22:10, Marco d'Itri wrote:
> Only ppp-udeb and the ppp kernel modules udeb are needed for a PPPoE
> install, but I do not know which images provide them.

The TC1 i386 netinst iso contains:
./pool/main/l/linux-kernel-di-i386/ppp-modules-2.4.26-1-386-di_0.62_i386.udeb
./pool/main/l/linux-kernel-di-i386-2.6/
ppp-modules-2.6.5-1-386-di_0.59_i386.udeb
./pool/main/p/ppp/ppp_2.4.2+20040202-3_i386.deb
./pool/main/p/ppp/ppp-udeb_2.4.2+20040202-3_i386.udeb
./pool/main/p/pppconfig/pppconfig_2.3.2_all.deb
./pool/main/p/pppoeconf/pppoeconf_1.0.1_all.deb
./pool/main/r/rp-pppoe/pppoe_3.5-3_i386.deb

You will have to start the installer with 'expert(26)' or with
'linux(26) DEBCONF_PRIORITY=medium' and select 'ppp' as extra component to be 
used for d-i.

I don't know how it goes from there. It would be good if we could get a little 
HOWTO for inclusion in the d-i manual.

Cheers,
FJP
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAyMqAgm/Kwh6ICoQRAha8AJ9VvoMPt3demWTI+3Ja9xqJVl/n1QCg2MGJ
56XaPnMZnVHGJbsjCy6Qqew=
=h2st
-END PGP SIGNATURE-



Re: Install via PPPoE

2004-06-10 Thread Arthur Wiebe
Frans Pop wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 10 June 2004 22:10, Marco d'Itri wrote:
 

Only ppp-udeb and the ppp kernel modules udeb are needed for a PPPoE
install, but I do not know which images provide them.
   

The TC1 i386 netinst iso contains:
./pool/main/l/linux-kernel-di-i386/ppp-modules-2.4.26-1-386-di_0.62_i386.udeb
./pool/main/l/linux-kernel-di-i386-2.6/
ppp-modules-2.6.5-1-386-di_0.59_i386.udeb
./pool/main/p/ppp/ppp_2.4.2+20040202-3_i386.deb
./pool/main/p/ppp/ppp-udeb_2.4.2+20040202-3_i386.udeb
./pool/main/p/pppconfig/pppconfig_2.3.2_all.deb
./pool/main/p/pppoeconf/pppoeconf_1.0.1_all.deb
./pool/main/r/rp-pppoe/pppoe_3.5-3_i386.deb
You will have to start the installer with 'expert(26)' or with
'linux(26) DEBCONF_PRIORITY=medium' and select 'ppp' as extra component to be 
used for d-i.

I don't know how it goes from there. It would be good if we could get a little 
HOWTO for inclusion in the d-i manual.
 

Yeah, that would be nice. I'll try a few things. If somehow something I 
do works I'll write a tutorial if nobody else does.

Cheers,
FJP
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFAyMqAgm/Kwh6ICoQRAha8AJ9VvoMPt3demWTI+3Ja9xqJVl/n1QCg2MGJ
56XaPnMZnVHGJbsjCy6Qqew=
=h2st
-END PGP SIGNATURE-
 


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


Bug#253730: libdb2 missing from 6/9/2004 daily build

2004-06-10 Thread Eric Harvieux
Package: installation-reports
Debian-installer-version: Daily Build 6/9/2004 
http://cdimage.debian.org/pub/cdimage-testing/daily/i386/20040609/sarge-i386-netinst.iso

uname -a: Linux nitrogen 2.4.26-1-686-smp #1 SMP Sat May 1 19:17:11 EST 
2004 i686 GNU/Linux

Date: 6/9/2004
Method: Booted off CD-ROM containing 6/9/2004 daily build netinst iso
Machine: Penguin Computing 2u
Processor: 2x PIII 1.0ghz
Memory: 1 GB
Root Device: sda
Root Size/partition table: n/a
Output of lspci: n/a
Base System Installation Checklist:
Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
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:[E]
Install boot loader:[ ]
Reboot: [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
Installing base system failed due to package libdb2 missing from 
packages on netinst CD. I searched the disc for the package file myself, 
but did not find it.

--
==
Eric Harvieux   | [EMAIL PROTECTED]
IMA Systems Office  | (612) 624 - 4353
   http://www.ima.umn.edu/
==
Institute for Mathematics and its Applications
University of Minnesota
400 Lind Hall, 207 Church St. SE
Minneapolis, MN 55455-0463
==
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Processing of base-installer_0.083_i386.changes

2004-06-10 Thread Archive Administrator
base-installer_0.083_i386.changes uploaded successfully to localhost
along with the files:
  base-installer_0.083.dsc
  base-installer_0.083.tar.gz
  base-installer_0.083_i386.udeb

Greetings,

Your Debian queue daemon


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



Bug#253731: test-candidate-1: linux26: some cosmetic and usability problems

2004-06-10 Thread Peter Cordes
Package: installation-reports
Severity: minor

INSTALL REPORT

Debian-installer-version: test candidate 1
uname -a: machine isn't booted up right now, but it's running 2.6.6-k7 from sarge
Date: 2004/6/5?  +/- a couple days
Method: booted netinst CD, net install from an up-to-date local mirror.

Machine: Athlon T-bird 1200MHz, A7V133 rev 1.05 mobo, BIOS 1010beta.
  usb keyboard, ps/2 mouse.
Root Device: 1 80GB IDE hard drive
Root Size/partition table: 10GB root, rest is an LVM physical
volume with logical volumes for swap, /home and /usr/local
Output of lspci and lspci -n:
not interesting, except for a Radeon 7200 video card.

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

 LVM install with linux26 kernel worked great.  I was really impressed that
it all worked :)  I'm glad cfdisk is included, so you don't have to use
those menus to partition the disk.  I love that the installer knows about
LVM.  nice job :)

 udhcpc from a late-May daily build failed, but dhclient in this release
worked. :)

 I don't remember if this was while the installer was running, or only after
the reboot, but the dialog boxes looked funny.  Instead of being surrounded
by lines, the boundary character looked like CE, but squished into one
character.  fb or vga font problem?

 In tasksel, the cursor flashes under task tickboxes even when I've tabbed
to  or .  This makes it non-obvious what's going to
happen when you press return, but it's purely a cosmetic problem.

 In the mirror-selection, the option to enter a hostname should be more
prominent.  Maybe outside the list, as a separate button?

 After selecting a mirror, it should prompt you for another one, so you can
get a non-US source too.  (Or maybe it's best to keep things simple and
avoid not-totally-necessary questions?)

 The problems in my previous report about typos and missing ipv6 /etc/hosts
entries still apply to the test candidate 1.  I won't repeat myself, so see 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=253724

 Configuring X wasn't much better this time.  In fact it was worse, because
I installed some font packages which apparently provided fonts that got used
by default (e.g. by konqueror), but didn't have glyphs for all the
characters.  (I think '/' or '-' was missing).  Things were ok after I
removed ttf-dustin.  I hate messing with fonts, so there's probably nothing
wrong with dustin's fonts, just the way they were getting used...


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



base-installer_0.083_i386.changes ACCEPTED

2004-06-10 Thread Debian Installer

Accepted:
base-installer_0.083.dsc
  to pool/main/b/base-installer/base-installer_0.083.dsc
base-installer_0.083.tar.gz
  to pool/main/b/base-installer/base-installer_0.083.tar.gz
base-installer_0.083_i386.udeb
  to pool/main/b/base-installer/base-installer_0.083_i386.udeb
Announcing to [EMAIL PROTECTED]


Thank you for your contribution to Debian.


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



Bug#253736: discover1: Tries to remove /media/cdrom0 which fails in d-i - cd is mounted there

2004-06-10 Thread Joerg Jaspert
Package: discover1
Version: 1.5-12
Severity: important

Hi

discover1 has this change in its changelog for 1.5-10:
  - Change default CD-ROM mountpoint base to /media (Closes: #245898)

Since then it breaks d-i cdroms, because they are mounted in /media and
discover tries to remove the directories there.
Gives an error while installing grub on i386 (you can simply go on
after this, but it still is an error message).


-- Package-specific info:

-- System Information:
Debian Release: testing/unstable
Architecture: i386 (i686)
Kernel: Linux 2.6.5-mm4
Locale: LANG=de_DE, LC_CTYPE=de_DE

Versions of packages discover1 depends on:
ii  ash 0.4.26-2 Compatibility package for the Debi
ii  dash0.4.26-2 The Debian Almquist Shell
ii  debconf 1.4.25   Debian configuration management sy
ii  libc6   2.3.2.ds1-13 GNU C Library: Shared libraries an
ii  libdiscover11.5-12   hardware identification library

-- debconf information:
* discover/manage_cdrom_devices: false
  discover/cdrom_base_mountpoint: /media/
  discover/cdrom_base_mountpoint_error: 

-- 
bye Joerg
<_DeadBull_> ohne speicher, tastatur, mouse, pladde, monitor, also nur die
Hardware...


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



Bug#253730: libdb2 missing from 6/9/2004 daily build

2004-06-10 Thread Joey Hess
Eric Harvieux wrote:
> http://cdimage.debian.org/pub/cdimage-testing/daily/i386/20040609/sarge-i386-netinst.iso

Please try again with today's build, which should fix this.

-- 
see shy jo


signature.asc
Description: Digital signature


Re: kernel oops decoder

2004-06-10 Thread Thiemo Seufer
Joey Hess wrote:
[snip]
> > Please tell me and the other lurkers here more
> > how to decode kernel oopses in debian-installer.
> > 
> > For what I see, is that the package ksymoops is needed at the target system.
> 
> Well we use the stock debian i386 kernel, so you just get another system
> with that kernel and run ksymoops on the oops output there.

ksymoops has even a -t flag to select the target architecture.
You usually do

ksymoops -t  -m  -v  \
-o  oopsfile > oopsfile.decoded

for cross-target oops dump decoding.


Thiemo


signature.asc
Description: Digital signature


Bug#253742: SparcStation2 netboot problems

2004-06-10 Thread Alan Woodland
Package: installation-reports
Debian-installer-version: http://http.us.debian.org/debian/dists/testing/main/installer-sparc/current/images/sparc32/netboot/boot.img (beta4)
uname -a: Linux limey 2.2.19 #1 Mon Apr 2 13:29:46 EDT 2001 sparc unknown (clock is wrong)
Date: 7th June 2004
Method: netboot 
Machine: SparcStation 2
Processor: Fujitsu or Weitek Power-UP
Memory: 48Mb
Root Device: SCSI
Root Size/partition table: N/A
Output of lspci: N/A

Base System Installation Checklist:
Initial boot worked:[E]
Configure network HW:   [ ]
Config network: [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Create file systems:[ ]
Mount partitions:   [ ]
Install base system:[ ]
Install boot loader:[ ]
Reboot: [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
Machine appears to lock up after downloading the image via tftp from one of my servers. I've repeated this many times, each with the exact same failure. 

After downloading the image it says:
bootmem_init: Scan sp_banks, init_bootmem(spfn[27a],bpfn[3c7],mlpfn[3000])
free_bootmem: base[0] size[fef000]
free_bootmem: base[100] size[1fc]
free_bootmem: base[2fcb000] size[35000]
reserve_bootmem: base[27a000] size[14c4fd]
reserve_bootmem: base[0] size[27a000]
reserve_bootmem: base[3c7000] size[600]
Bootling Linux...
mem_init: Calling free_all_bootmem().
After that no more activity ever. I've verified the md5 sum of the image on the server 
it's being hosted on. The sparcstation 2 has a keyboard and monitor physicaly attached 
to it during these tests. I was unable to find a suitable null modem cable to further 
test with. After starting booting the status of numlock cannot be toggled by me on the 
keyboard until the machine is reset.
Thanks,
Alan

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


Re: initrd.list output from build process

2004-06-10 Thread Thiemo Seufer
Colin Watson wrote:
[snip]
> > >   ./update-manifest $@ $(MANIFEST-INITRD)
> > 
> > You may want to add also
> > 
> > ./update-manifest $(INITRD_LIST) $(MANIFEST-INITRD_LIST)
> 
> I was hoping to avoid that, since I thought that would mean I'd have to
> set MANIFEST-INITRD_LIST in all the .cfg files.

You don't have to, an unset MAINFEST-* is simply ignored.

> Maybe I can just set
> MANIFEST-INITRD_LIST = "contents of initrd" in config/common and leave
> it at that, though.

Would be the best solution, I think. Any configuration which wants
to give a more specific description can override it with its own
value then.


Thiemo


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



Processed: reassign 253575 to choose-mirror

2004-06-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 253575 choose-mirror
Bug#253575: does not say how to use different port on mirror, has ia64 mirrors
Bug reassigned from package `netcfg' to `choose-mirror'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Processing of yaboot-installer_0.0.25_powerpc.changes

2004-06-10 Thread Archive Administrator
yaboot-installer_0.0.25_powerpc.changes uploaded successfully to localhost
along with the files:
  yaboot-installer_0.0.25.dsc
  yaboot-installer_0.0.25.tar.gz
  yaboot-installer_0.0.25_powerpc.udeb

Greetings,

Your Debian queue daemon


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



yaboot-installer_0.0.25_powerpc.changes ACCEPTED

2004-06-10 Thread Debian Installer

Accepted:
yaboot-installer_0.0.25.dsc
  to pool/main/y/yaboot-installer/yaboot-installer_0.0.25.dsc
yaboot-installer_0.0.25.tar.gz
  to pool/main/y/yaboot-installer/yaboot-installer_0.0.25.tar.gz
yaboot-installer_0.0.25_powerpc.udeb
  to pool/main/y/yaboot-installer/yaboot-installer_0.0.25_powerpc.udeb
Announcing to [EMAIL PROTECTED]


Thank you for your contribution to Debian.


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



Re: Help! Debian-Installer Dies with various umount errors

2004-06-10 Thread [EMAIL PROTECTED]
If you were blonde, female, and weighed less than 400 lbs I'd kiss you :)
Yes, you're 100% right... that's exactly the problem. If you're 
installing to a hard disk of 100gig or greater, the Beta 4 installer and 
the Testing Candidate 1 installer will fail, giving you no real error 
messages, etc.

I was able to verify this, and with a little disk-juggling, got this 
working.

I didn't see this in the BTS have you filed a bug report on it? I'd 
say this was a pretty major problem that while easy to fix, really needs 
to be corrected in TC1.

Once again, Dan, thanks so much for your help!
Moe
Dan Callahan wrote:
On Thu, 2004-06-10 at 12:34 -0400, [EMAIL PROTECTED] wrote:
I have tried the Beta 4 Sarge installer, Beta 4 Net Installer, and 
Testing Candidate 1 Net Install (all for i386) and my installs always 
die at Installing the Base System. (I always do a clean install, letting 
the installer use the entire disk).

How large is your disk? I was running into similar issues, and it turns
out base-installer at some point runs `df /target/` to determine the
target disk. If your disk is large enough, the "1k-blocks" column runs
into the "Filesystem" column, adding all manner of digits to the end of
the filesystem address.
My email on the issue is under the subject "Installer fails on
initrd-tools"
-Dan C


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


Processed: tagging 253736

2004-06-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 253736 d-i
Bug#253736: discover1: Tries to remove /media/cdrom0 which fails in d-i - cd is 
mounted there
There were no tags set.
Tags added: d-i

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Processed: severity of 253736 is serious

2004-06-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> severity 253736 serious
Bug#253736: discover1: Tries to remove /media/cdrom0 which fails in d-i - cd is 
mounted there
Severity set to `serious'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Processed: severity of 253736 is serious, tagging 253736

2004-06-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> severity 253736 serious
Bug#253736: discover1: Tries to remove /media/cdrom0 which fails in d-i - cd is 
mounted there
Severity set to `serious'.

> tags 253736 d-i
Bug#253736: discover1: Tries to remove /media/cdrom0 which fails in d-i - cd is 
mounted there
Tags were: d-i
Tags added: d-i

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



  1   2   >