Bug#270599: Testing newoldworld pmac miboot 2.6 floppies
Sven Luther wrote: Oh, and btw, I'm just installing my oldworld 4400/200 mac with d-i and the daily built 2.4-floppy images (with root.img and root-2.img) and it seems to work fine - right now. I'll keep you informed in another mail. BTW, as of tomorrows build, the 2.6 images should be fine also. The 2.6 images now fit on a physical floppy, so that's good. Unfortunately, the resulting floppy doesn't boot on my G3. It reads and gives me a tux-mac icon, but when it gets to the end the screen colors invert, and it just sits there. No text screen. The boot floppy doesn't eject. When I eject it manually, feed it the root floppy, and hit return, nothing happens -- specifically, it doesn't start reading the root floppy. This same behavior happens for both the boot and ofonlyboot floppies. Meanwhile, back at the 2.4 ranch... The 2.4 boot floppy read, switched to text mode, asked for root, which read, asked for language (English), then gave me a blue screen which lasted for more than a minute. I switched to the F2 console, killed 4 processes: udpkg --configure --force-configure countrychooser, two more countrychooser, and grep US [this may be a clue]. Back on the main menu on F1 console, I told it to load drivers and fed it the root-2. It read that and decoded it, then put me in the country chooser screen (not blue, this time) I chose US. [possible clue: There is probably a file (the one the grep US was looking for) that is on the root-2 floppy, but is needed by the country chooser, so should be on the root floppy...] It asked for an ethernet driver. The 8139too wasn't listed so I said none of the above to get it to read the net-drivers floppy. It did, and things continued normally til we got to choose a mirror. I chose ftp.us.debian.org but it didn't ask for protocol type or debian version, and when it tried to read stuff, I got the no driver modules message. I hit go back and re-did the mirror choice (presumably at lower priority). This time it did ask for Debian version. I said unstable, and it proceeded without problems until it got to the partitioner. As with previous attempts, the partitioner said no disks found. Also as with previous attempts, poking around on the F2 console shows that it really hasn't found any disks. Back at the main menu, I changed installer priority to low, and re-ran detect hardware. It said unable to load some modules listing: ide-scsi, ide-mod, ide-probe-mod, ide-detect, ide-generic, ide-floppy. Presumably one of those is needed to get it to see my IDE disk. Just for fun, I did a modprobe mesh, and re-ran detect hardware. This time it found my SCSI ZIP disk, and offered to partition it for me. I declined and rebooted to write up this report. Hope this helps! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Testing newoldworld pmac miboot 2.6 floppies
On Fri, Sep 17, 2004 at 02:31:09AM -0400, Rick Thomas wrote: Sven Luther wrote: Oh, and btw, I'm just installing my oldworld 4400/200 mac with d-i and the daily built 2.4-floppy images (with root.img and root-2.img) and it seems to work fine - right now. I'll keep you informed in another mail. BTW, as of tomorrows build, the 2.6 images should be fine also. The 2.6 images now fit on a physical floppy, so that's good. Unfortunately, the resulting floppy doesn't boot on my G3. It reads and gives me a tux-mac icon, but when it gets to the end the screen colors invert, and it just sits there. No text screen. The boot floppy doesn't eject. When I eject it manually, feed it the root floppy, and hit return, nothing happens -- specifically, it doesn't start reading the root floppy. This same behavior happens for both the boot and ofonlyboot floppies. Damnit. But Jens reported it as working on his oldworld box. Could you maybe fill a bug report against kernel-image-2.6.8-powerpc about this ? Anyway, we will work on that at the Oldenbourg meeting next week, so there may be progress done there. Meanwhile, back at the 2.4 ranch... The 2.4 boot floppy read, switched to text mode, asked for root, which read, asked for language (English), then gave me a blue screen which lasted for more than a minute. I switched to the F2 console, killed 4 processes: udpkg --configure --force-configure countrychooser, two more countrychooser, and grep US [this may be a clue]. Back on the main menu on F1 console, I told it to load drivers and fed it the root-2. It read that and decoded it, then put me in the country chooser screen (not blue, this time) I chose US. [possible clue: There is probably a file (the one the grep US was looking for) that is on the root-2 floppy, but is needed by the country chooser, so should be on the root floppy...] Indeed. Do you know the name of the floppy in question ? It asked for an ethernet driver. The 8139too wasn't listed so I said none of the above to get it to read the net-drivers floppy. It did, and things continued normally til we got to choose a mirror. I chose ftp.us.debian.org but it didn't ask for protocol type or debian version, and when it tried to read stuff, I got the no driver modules message. I hit go back and re-did the mirror choice (presumably at lower priority). This time it did ask for Debian version. I said unstable, and it proceeded without problems until it got to the partitioner. Yes, this is the infamous 2.6.8 modules not in sarge. I may have a solution for this, but it will need some convincing and work. As with previous attempts, the partitioner said no disks found. Also as with previous attempts, poking around on the F2 console shows that it really hasn't found any disks. Ok. We need to know what is your ide controller, and in which udeb it is found, and if discover lists it or not. Back at the main menu, I changed installer priority to low, and re-ran detect hardware. It said unable to load some modules listing: ide-scsi, ide-mod, ide-probe-mod, ide-detect, ide-generic, ide-floppy. Presumably one of those is needed to get it to see my IDE disk. Strange. Just for fun, I did a modprobe mesh, and re-ran detect hardware. This time it found my SCSI ZIP disk, and offered to partition it for me. I declined and rebooted to write up this report. Definitively a bug in discover, could you fill a bug report against discover1 with your lspci and lspci -n output ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release Notes available for translation
On Thu, Sep 16, 2004 at 10:29:09PM +0100, Rob Bradford wrote: On Thu, Sep 16, 2004 at 10:05:14PM +0200, Frans Pop wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (CC'ing d-boot; however, I propose to keep the discussion on d-doc.) IMHO a call for translation of the Release Notes is a bit premature. I have just downloaded the latest English version from [1] with the intention of starting a Dutch translation. A quick scan gave me the impression that the main text of the release notes still refers more to Woody than to Sarge. At the bottom of the mail I have copied some examples of this. I seems a shame to start a new translation while a significant part of the text needs rewriting. Oh. Now thats interesting, i made some significant changes to the release notes. For instance the sections on using dselect and apt-get were both replaced with a single version documenting aptitude. You'd be suprised how much of this document goes back to potato and before. Besides that general point, I have some observations and suggestions. - - PowerPC will be installed with kernel 2.6.8 by default. No one had been able to give me a straight answer on this. Thanks for letting me know. Bah, you obviously didn't follow this clear enough :) We switched to 2.6 kernels by default on powerpc even prior to RC1 i think. Only oldworld miboot floppies are still problematic. apus is being dropped though, so this should make it in the Release Notes i think. I believe there where something like 3 users left, and the kernels in sarge probably didn't work on apus anyway. Maybe it would be worth mentioning full support for the Pegasos boards, since this is new previously unsupported hardware ? G5 pmacs and power3/4 hardware where also not supported by woody, i think. - - The alternative kernel for i386 will be 2.6.8 (not 2.6.7). When i checked the package database the other day i thought i only saw 2.6.7 available for testing. Both the above are now being fixed. On all arches, sarge will release with 2.4.27 as a 2.4 kernel and 2.6.8 as a 2.6 kernel on the arches which support it. All will default to 2.4 except powerpc. There is at least m68k still using 2.2 kernels. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272088: netboot: wrong cfg
Package: debian-installer Version: N/A; reported 2004-09-17 Severity: important Tags: patch Hi, I've just tried netboot to install sarge on a new box (DELL OptiPlex 280). I've had to change pxelinux.cfg/default: I've removed prefix debian-installer/i386 from every path. So now it is: display boot-screens/syslinux.txt default linux F1 boot-screens/f1.txt F2 boot-screens/f2.txt F3 boot-screens/f3.txt F4 boot-screens/f4.txt F5 boot-screens/f5.txt F6 boot-screens/f6.txt F7 boot-screens/f7.txt F8 boot-screens/f8.txt F9 boot-screens/f9.txt F0 boot-screens/f10.txt label linux kernel linux append vga=normal initrd=initrd.gz ramdisk_size=9268 root=/dev/rd/0 devfs=mount,dall rw -- label expert kernel linux append DEBCONF_PRIORITY=low vga=normal initrd=initrd.gz ramdisk_size=9268 root=/dev/rd/0 devfs=mount,dall rw -- label linux26 kernel 2.6/linux append vga=normal initrd=2.6/initrd.gz ramdisk_size=10778 root=/dev/rd/0 devfs=mount,dall rw -- label expert26 kernel 2.6/linux append DEBCONF_PRIORITY=low vga=normal initrd=2.6/initrd.gz ramdisk_size=10778 root=/dev/rd/0 devfs=mount,dall rw -- prompt 1 timeout 0 And it works fine now. I have tftpd server tftpd-hpa run with -s (chroot) parameter. Regards Ondrej Medek -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux zeus07 2.4.26-zeus07-1 #1 SMP St èen 2 23:11:44 CEST 2004 i686 Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
No /dev/modem or similar created on PowerPC?
Hello all... I'm just poking around on my G3/266 and I'm noticing that I don't have a /dev/modem, or any tty that links to it. Does the d-i create such a device only if you say that you want to install via ppp? This could be a problem if, for example, you want to use your modem to output a serial console (which is my situation, actually :-) In fact, I can't find (and neither can kppp) which tty connects to my modem. I'll bug the ppc people next. Russell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install woody or sarge on IBM 7025-F50
Now really forwarding to debian-boot. On Fri, Sep 17, 2004 at 02:13:35PM +0200, Helfrich Markus wrote: Hello, i am getting really tiered installing Debian(Woody or Sarge) on this little Bastard Box called 7025-F50 Right now i got Debian Sarge installer booting... How this work !! I create an iso cd with the content of ftp://ftp.debian.org/debian/dists/sarge/main/installer-powerpc/current/images/powerpc/cdrom/ in it... also i create a /etc/ dir with yaboot.conf at the root of the cd an i put yaboot from ftp://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/powerpc/current/sarge-powerpc-netinst.iso at the root of the cd. Then i boot the Box ... Pressing F8 to get the OF Prompt then make a boot cdrom:,\yaboot right now i can boot the 2.4/vmlinux from directory above... because the 2.6 vmlinux does not work with the symbios scsi controller in the box. Ok the debian-installer boot, i have to cahnge the cd (put sarge-powerpc-netinst.iso) in the drive Everything works fine the Partitioner came up (not really a good thing i missed cfdisk) .. and the system begin a Base system installation. Until the Error the bootloader was not configured correct (during kernel-image-2.4.27-pmac install) ... Ok i skiped to installing without bootloader but the same thing it can't install the kernel-image Any hints ?? I am really tired with this Box... -- Mit freundlichem Gruß, Best regards, Helfrich Markus Dipl. Inf. (FH) Markus Helfrich Fachhochschule Kaiserslautern Standort Zweibrücken University of applied Science Amerikastr. 1 66482 Zweibrücken Tel.: +49 6332 914 154 Fax.: +49 6332 914 155 mailto: [EMAIL PROTECTED] PGP KeyID 0xD8E95B7C _ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272099: netboot: wrong cfg
Package: debian-installer Version: N/A; reported 2004-09-17 Severity: important Sorry, I've missed a link pxelinux.0 - debian-installer/i386/pxelinux.0. When I use this file, everything works well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272099: marked as done (netboot: wrong cfg)
Your message dated Fri, 17 Sep 2004 15:37:31 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#272099: netboot: wrong cfg 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 Sep 2004 12:55:30 + From [EMAIL PROTECTED] Fri Sep 17 05:55:30 2004 Return-path: [EMAIL PROTECTED] Received: from zeus07.fsv.cvut.cz [147.32.153.9] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C8IGw-0008My-00; Fri, 17 Sep 2004 05:55:30 -0700 Received: from xmedeko by zeus07.fsv.cvut.cz with local (Exim 3.35 #1 (Debian)) id 1C8IGS-0001mW-00 for [EMAIL PROTECTED]; Fri, 17 Sep 2004 14:55:00 +0200 Date: Fri, 17 Sep 2004 14:55:00 +0200 To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: Re: netboot: wrong cfg Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] User-Agent: Mutt/1.3.28i From: Ondrej Medek [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=-5.1 required=4.0 tests=BAYES_44,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: debian-installer Version: N/A; reported 2004-09-17 Severity: important Sorry, I've missed a link pxelinux.0 - debian-installer/i386/pxelinux.0. When I use this file, everything works well. --- Received: (at 272099-done) by bugs.debian.org; 17 Sep 2004 13:38:03 + From [EMAIL PROTECTED] Fri Sep 17 06:38:03 2004 Return-path: [EMAIL PROTECTED] Received: from (elrond.fjphome.nl) [195.240.184.66] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C8Iw7-0003ZS-00; Fri, 17 Sep 2004 06:38:03 -0700 Received: from strider.fjphome.nl ([10.19.66.86] ident=fjp) by elrond.fjphome.nl with esmtp (Exim 3.35 #1 (Debian)) id 1C8Ivc-0004bv-00 for [EMAIL PROTECTED]; Fri, 17 Sep 2004 15:37:32 +0200 From: Frans Pop [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Bug#272099: netboot: wrong cfg Date: Fri, 17 Sep 2004 15:37:31 +0200 User-Agent: KMail/1.6.2 References: [EMAIL PROTECTED] [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Message-Id: [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=-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: I've just tried netboot to install sarge on a new box (DELL OptiPlex 280). I've had to change pxelinux.cfg/default: I've removed prefix debian-installer/i386 from every path. So now it is: Problem solved by submitter; closing this report accordingly. FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
debian-installer beta3/rc1 doesn't boot
Debian-installer beta3 and rc1 doesn't seem to boot. It doesn't matter if I choose GRUB or Lilo, after the first reboot 2 things happen probably from the same problem: 1. If Lilo is choosen, in the boot process the word LILO appears infinitelly through out the screen: LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO ... it never stops. 2. If GRUB is choose, almost the same happens but it doesn't loop forever. After one or 2 screen full's the GRUB word stop appearing. I thought this was a problem with Lilo but after seeing GRUB doing the same thing I think the problem may be in the partitioning program (fdisk). I can't remeber if I've choosen the automatic partitioning scheme or if I did the partitions myself. Forgive me if I've missed something and this problem already have been reported. -- Marco Ferra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272120: debian-installer beta3/rc1 doesn't boot
Package: debian-installer Version: Beta3 / RC1 Debian-installer beta3 and rc1 doesn't seem to boot. It doesn't matter if I choose GRUB or Lilo, after the first reboot 2 things happen probably from the same problem: 1. If Lilo is choosen, in the boot process the word LILO appears infinitelly through out the screen: LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO ... it never stops. 2. If GRUB is choose, almost the same happens but it doesn't loop forever. After one or 2 screen full's the GRUB word stop appearing. I thought this was a problem with Lilo but after seeing GRUB doing the same thing I think the problem may be in the partitioning program (fdisk). I can't remeber if I've choosen the automatic partitioning scheme or if I did the partitions myself. Forgive me if I've missed something and this problem already have been reported. -- Marco Ferra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272123: debian-installer: tg3 network card not recognized automatically
Package: debian-installer Version: N/A; reported 2004-09-17 Severity: minor Hi, I've just installed sarge from netboot (the 16th September release). I've choosed expert26 mode. The installer does not recognized Broadcom Tigon3 (BCM95751) network card. (PCI ID 14e4:1677). I had to load the module manually. P.S. the module tg3 of kernel 2.4.26 from rc1 release does not works with this card either. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux zeus07 2.4.26-zeus07-1 #1 SMP St èen 2 23:11:44 CEST 2004 i686 Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
sarge m68k CD/DVD build downloads things
Erm, is there any reason why we're still downloading m68k bootloader stuff from people.debian.org rather than it being in the archive??? from tools/boot/sarge/boot-m68k: for subarch in $SUBARCHS; do TARF=bootloaders-$subarch.tar.bz2 if `wget -q -O $TARF $DI_BOOTLOADER/$TARF` ; then tar -xjf $TARF fi rm -f $TARF done Can we get this lot moved into the archive properly please? -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] This dress doesn't reverse. -- Alden Spiess signature.asc Description: Digital signature
Bug#270599: Testing newoldworld pmac miboot 2.6 floppies
On Fri, Sep 17, 2004 at 09:42:09AM -0700, Brad Boyer wrote: On Fri, Sep 17, 2004 at 09:55:17AM +0200, Sven Luther wrote: Damnit. But Jens reported it as working on his oldworld box. Could you maybe fill a bug report against kernel-image-2.6.8-powerpc about this ? I suspect that the one that worked was SCSI only. All the first generation PCI powermacs (7x00,8x00,9x00) had one or two SCSI controllers, but no onboard IDE. However, most of the G3 models had IDE and SCSI onboard, and used mostly IDE devices. Ah, maybe ... Ok. We need to know what is your ide controller, and in which udeb it is found, and if discover lists it or not. If it is the onboard stuff, it can't be built as a separate module from the way the source looks. It appears that ide/ppc/pmac.c is always compiled into ide-core if it is enabled. Yes, indeed it is. Definitively a bug in discover, could you fill a bug report against discover1 with your lspci and lspci -n output ? You won't get much help out of lspci. These are not PCI devices. The macio chip shows up as one huge PCI device, and the macio layer knows how to /proc/device-tree/aliases then. And this probably means that there is no chance ever of discover discovering them. Oh well. read data from OF to find the sub-devices. I don't think either version of discover has any knowledge of macio, which prevents detection of drivers like mac53c94, mesh, mace, pmac_zilog, and lots of other older mac stuff. The pmac IDE support can handle both PCI and macio devices, but I'm pretty sure that only newworld macs came with onboard IDE that showed up as separate PCI devices. Probably yes. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272132: Package: installation-reports
Package: installation-reports Debian-installer-version: http://people.debian.org/~joeyh/d-i/images/daily/netboot/netboot.tar.gz (16-Sep-2004 12:32 7.5M ) uname -a: 2.6.8-1 and CD Debian testing (Sarge) from date: Fri, 06 Aug 2004 19:36:21 UTC Date: 11-sep-2004 Method: Network install, with dhcp server in second computer. Machine: Toshiba Portege R100. Processor: 900MHz Pentium M with 1MB of Level 2 cache. Memory: 256MB onboard, with a spare slot which can take 128-1024MB. Root Device: Toshiba MK3004GAH 30GBi. Root Size/partition table: lspci 00:1d.0 USB Controller: Intel Corp.: Unknown device 24c2 (rev 03) 00:1d.1 USB Controller: Intel Corp.: Unknown device 24c4 (rev 03) 00:1d.7 USB Controller: Intel Corp.: Unknown device 24cd (rev 03) 00:1e.0 PCI bridge: Intel Corp. 82820 820 (Camino 2) Chipset PCI (-M) (rev 83) 00:1f.0 ISA bridge: Intel Corp.: Unknown device 24cc (rev 03) 00:1f.1 IDE interface: Intel Corp.: Unknown device 24ca (rev 03) 00:1f.5 Multimedia audio controller: Intel Corp.: Unknown device 24c5 (rev 03) 00:1f.6 Modem: Intel Corp.: Unknown device 24c6 (rev 03) 01:00.0 VGA compatible controller: Trident Microsystems: Unknown device 2100 (rev 91) 02:08.0 Ethernet controller: Intel Corp.: Unknown device 103d (rev 83) 02:0a.0 Network controller: Intel Corp.: Unknown device 1043 (rev 04) 02:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus Bridge with ZV Support (rev 33) 02:0d.0 System peripheral: Toshiba America Info Systems: Unknown device 0805 (rev 05) lspci -n: 00:00.0 Class 0600: 8086:3340 (rev 03) 00:01.0 Class 0604: 8086:3341 (rev 03) 00:1d.0 Class 0c03: 8086:24c2 (rev 03) 00:1d.1 Class 0c03: 8086:24c4 (rev 03) 00:1d.7 Class 0c03: 8086:24cd (rev 03) 00:1e.0 Class 0604: 8086:2448 (rev 83) 00:1f.0 Class 0601: 8086:24cc (rev 03) 00:1f.1 Class 0101: 8086:24ca (rev 03) 00:1f.5 Class 0401: 8086:24c5 (rev 03) 00:1f.6 Class 0703: 8086:24c6 (rev 03) 01:00.0 Class 0300: 1023:2100 (rev 91) 02:08.0 Class 0200: 8086:103d (rev 83) 02:0a.0 Class 0280: 8086:1043 (rev 04) 02:0b.0 Class 0607: 1179:0617 (rev 33) 02:0d.0 Class 0880: 1179:0805 (rev 05) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:OK Configure network HW: OK Config network: OK Detect CD: [ ] Load installer modules: Error Detect hard drives: ( ) Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: I'm using the network install from [1]. I was try the next kernel parameters: linux, expert, linux26 and expert26. The problem happens in the Download installer components. The message is: No kernel modules were found. Probaly is due to a mismatch between the kernel ... This problem start happend happen after the image from the day 11 of september, before that I was report another bug (Bug#271214) I also write in [2] the file 'var/log/messages' from the net-install. thank you. [1] http://people.debian.org/~joeyh/d-i/images/daily/netboot/ [2] var/log/messages: insmod /lib/modules/2.6.8-1-386/kernel/drivers/net/mii.ko insmod /lib/modules/2.6.8-1-386/kernel/drivers/net/e100.ko -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBPgRbgm/Kwh6ICoQRAk37AJ4rUiXraRjibEnURT/ZTHF2nr894gCgpvDc QsB1o82LAXTXwyVILhuRcVU= =1TVe -END PGP SIGNATURE-
Bug#270599: Testing newoldworld pmac miboot 2.6 floppies
On Fri, Sep 17, 2004 at 09:55:17AM +0200, Sven Luther wrote: Damnit. But Jens reported it as working on his oldworld box. Could you maybe fill a bug report against kernel-image-2.6.8-powerpc about this ? I suspect that the one that worked was SCSI only. All the first generation PCI powermacs (7x00,8x00,9x00) had one or two SCSI controllers, but no onboard IDE. However, most of the G3 models had IDE and SCSI onboard, and used mostly IDE devices. Ok. We need to know what is your ide controller, and in which udeb it is found, and if discover lists it or not. If it is the onboard stuff, it can't be built as a separate module from the way the source looks. It appears that ide/ppc/pmac.c is always compiled into ide-core if it is enabled. Definitively a bug in discover, could you fill a bug report against discover1 with your lspci and lspci -n output ? You won't get much help out of lspci. These are not PCI devices. The macio chip shows up as one huge PCI device, and the macio layer knows how to read data from OF to find the sub-devices. I don't think either version of discover has any knowledge of macio, which prevents detection of drivers like mac53c94, mesh, mace, pmac_zilog, and lots of other older mac stuff. The pmac IDE support can handle both PCI and macio devices, but I'm pretty sure that only newworld macs came with onboard IDE that showed up as separate PCI devices. Brad Boyer [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272123: debian-installer: tg3 network card not recognized automatically
On Fri, Sep 17, 2004 at 05:51:26PM +0200, Ondrej Medek wrote: Package: debian-installer Version: N/A; reported 2004-09-17 Severity: minor Hi, I've just installed sarge from netboot (the 16th September release). I've choosed expert26 mode. The installer does not recognized Broadcom Tigon3 (BCM95751) network card. (PCI ID 14e4:1677). I had to load the module manually. What is the name of the module(s) that you load manually? P.S. the module tg3 of kernel 2.4.26 from rc1 release does not works with this card either. Cheers Geert Stappers pgpYtaVtUVfs4.pgp Description: PGP signature
Bug#272132: marked as done (Package: installation-reports)
Your message dated Fri, 17 Sep 2004 19:23:33 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#272132: Package: installation-reports 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 Sep 2004 16:51:35 + From [EMAIL PROTECTED] Fri Sep 17 09:51:35 2004 Return-path: [EMAIL PROTECTED] Received: from mail.actcom.co.il (smtp4.actcom.co.il) [192.114.47.66] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C8LxO-0007rK-00; Fri, 17 Sep 2004 09:51:34 -0700 Received: from technion.ac.il (line108-195.adsl.actcom.co.il [192.117.108.195]) by smtp4.actcom.co.il (8.12.11/8.12.11) with ESMTP id i8HGpSlY031089 for [EMAIL PROTECTED]; Fri, 17 Sep 2004 19:51:31 +0300 Message-ID: [EMAIL PROTECTED] Date: Fri, 17 Sep 2004 19:50:48 +0200 From: gustavo [EMAIL PROTECTED] User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, es-ar, he MIME-Version: 1.0 To: [EMAIL PROTECTED] Subject: Package: installation-reports Content-Type: multipart/alternative; boundary=010601080900050605070908 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.4 required=4.0 tests=BAYES_00,HAS_PACKAGE, HTML_MESSAGE,HTML_TITLE_EMPTY autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: This is a multi-part message in MIME format. --010601080900050605070908 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Package: installation-reports Debian-installer-version: http://people.debian.org/~joeyh/d-i/images/daily/netboot/netboot.tar.gz (16-Sep-2004 12:32 7.5M ) uname -a: 2.6.8-1 and CD Debian testing (Sarge) from date: Fri, 06 Aug 2004 19:36:21 UTC Date: 11-sep-2004 Method: Network install, with dhcp server in second computer. Machine: Toshiba Portege R100. Processor: 900MHz Pentium M with 1MB of Level 2 cache. Memory: 256MB onboard, with a spare slot which can take 128-1024MB. Root Device: Toshiba MK3004GAH 30GBi. Root Size/partition table: lspci 00:1d.0 USB Controller: Intel Corp.: Unknown device 24c2 (rev 03) 00:1d.1 USB Controller: Intel Corp.: Unknown device 24c4 (rev 03) 00:1d.7 USB Controller: Intel Corp.: Unknown device 24cd (rev 03) 00:1e.0 PCI bridge: Intel Corp. 82820 820 (Camino 2) Chipset PCI (-M) (rev 83) 00:1f.0 ISA bridge: Intel Corp.: Unknown device 24cc (rev 03) 00:1f.1 IDE interface: Intel Corp.: Unknown device 24ca (rev 03) 00:1f.5 Multimedia audio controller: Intel Corp.: Unknown device 24c5 (rev 03) 00:1f.6 Modem: Intel Corp.: Unknown device 24c6 (rev 03) 01:00.0 VGA compatible controller: Trident Microsystems: Unknown device 2100 (rev 91) 02:08.0 Ethernet controller: Intel Corp.: Unknown device 103d (rev 83) 02:0a.0 Network controller: Intel Corp.: Unknown device 1043 (rev 04) 02:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus Bridge with ZV Support (rev 33) 02:0d.0 System peripheral: Toshiba America Info Systems: Unknown device 0805 (rev 05) lspci -n: 00:00.0 Class 0600: 8086:3340 (rev 03) 00:01.0 Class 0604: 8086:3341 (rev 03) 00:1d.0 Class 0c03: 8086:24c2 (rev 03) 00:1d.1 Class 0c03: 8086:24c4 (rev 03) 00:1d.7 Class 0c03: 8086:24cd (rev 03) 00:1e.0 Class 0604: 8086:2448 (rev 83) 00:1f.0 Class 0601: 8086:24cc (rev 03) 00:1f.1 Class 0101: 8086:24ca (rev 03) 00:1f.5 Class 0401: 8086:24c5 (rev 03) 00:1f.6 Class 0703: 8086:24c6 (rev 03) 01:00.0 Class 0300: 1023:2100 (rev 91) 02:08.0 Class 0200: 8086:103d (rev 83) 02:0a.0 Class 0280: 8086:1043 (rev 04) 02:0b.0 Class 0607: 1179:0617 (rev 33) 02:0d.0 Class 0880: 1179:0805 (rev 05) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:OK Configure network HW: OK Config network: OK Detect CD: [ ] Load installer modules: Error Detect hard drives: ( ) Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: I'm using the network install from [1]. I
Re: fresh Sarge install, boot failes
Harald Dunkel wrote: Please check http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=263169 Welcome to the family. Doesn't sound like Jan's problem at all. IIRC, Jan is seeing no boot loader messages. -- see shy jo signature.asc Description: Digital signature
Re: grub floppy fails to boot
Haines Brown wrote: The object is to boot a new installation of debian sarge, filesystem reiserfs, from a grub (0.95+cvs20040624-8) boot loader installed on a diskette. Grub has not yet been installed on the target disk because I want the security of a boot floppy in case it gums things up when I do install it (I assume that a grub boot floppy does not need to have grub installed on the hard disk). This diskette boots my current system (debian sarge, reiserfs) just fine. And the bootloader on my current disk (sda) MBR can boot the target disk (sdc). It's only using the boot floopy to boot the target disk that I get into trouble. At this point I'm trying to understand the set of boot error messages associated with a kernel panic when try to use it to boot the target disk: 1. kmod failed to exec /sbin/modprobe -s -k block-major-8 errno=2 Is this message relevant? This is a new installation of sarge and so I've not yet run depmod -a to create the module database. So is this error to be expected at this point? Or is it a hint of trouble? I assume the reiserfs driver is in the kernel and does not require being loaded by modprobe. The program /sbin/modprobe exists on sdc. I've no idea what errno=2 is. Reiserfs is a module and you need to have grub load the initrd that goes with your kernel. With the target disk (sdc1) mounted on my running system (sda), I did try to run depmod from a chroot. Although I do have /lib/modules/2.6.7-1-386 directory on the target disk (sdc), when I try to create a module database from chroot: :/# depmod -a depmod: Can't open /lib/modules/2.4.18-bf2.4/modules.dep for writing It seems depmod is looking at the running system (sda), which uses kernel 2.4.18-bf2.4, rather than the target system with which has the 2.6.7-1-386 kernel. Is this behavior to be expected? Depmod defaults to running for the currently running kernel yes. Your problem has nothing to do with depmod, however. 2. VFS: Cannot open root devices sdc1 or 08:21 The device I want to mount is definitely sdc1. This is because you didn't load the initrd, the kernel you've booted has no disk drivers built into it. Is it possible that the mount failure results from there being no reiserfs driver present? I added reiserfs_stage1_5 to the /boot/grub directory on the diskette, but it didn't help. You're confusing grub filesystem modules and kernel filesystem modules, these are two very different things. -- see shy jo signature.asc Description: Digital signature
Bug#271890: marked as done (Please add the initial boot options to lilo.conf)
Your message dated Fri, 17 Sep 2004 13:34:29 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#271890: Installation process on Sarge 20040801 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; 15 Sep 2004 22:14:44 + From [EMAIL PROTECTED] Wed Sep 15 15:14:43 2004 Return-path: [EMAIL PROTECTED] Received: from postfix3-1.free.fr [213.228.0.44] (postfix) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C7i31-0002VP-00; Wed, 15 Sep 2004 15:14:43 -0700 Received: from Deborah.RocknRoll.org (rouen-1-62-147-101-78.dial.proxad.net [62.147.101.78]) by postfix3-1.free.fr (Postfix) with ESMTP id 8AE73173AF9 for [EMAIL PROTECTED]; Thu, 16 Sep 2004 00:14:40 +0200 (CEST) Received: by Deborah.RocknRoll.org (Postfix, from userid 1000) id 07D3E10750; Wed, 15 Sep 2004 18:40:14 +0200 (CEST) Date: Wed, 15 Sep 2004 18:40:14 +0200 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Installation process on Sarge 20040801 Message-ID: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Organization: Guilde des Gardiens de la Foi Debianiste X-Operating-System: Debbie (2.6.7) running on a [EMAIL PROTECTED]/512MB X-Uptime: up 42 days cut User-Agent: Mutt/1.5.5.1+cvs20040105i Content-Transfer-Encoding: quoted-printable 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.5 required=4.0 tests=BAYES_40,DATE_IN_PAST_03_06, HAS_PACKAGE,NO_REAL_NAME,SUBJ_HAS_UNIQ_ID autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: installation-reports There is a possibility this bug report has gone its way in the BTS, but there is a much more high probability it has been forwarded to Dave Null because the first time I have sent it, I have forgotten the Package: line (just because I didn't know what package it was all about). So here is the bug report, it all about Sarge official snapshot 20040801. In the first days of August, using the ADSL connection of my father I have downloaded the 7 first CD of Sarge 20040801 (becoming Sarge 20040808 for the last 2 CDs).=20 =20 Back to my house with a new Centino NoteBook, I tried to install the Sarge on it. =20 * 1) The ACPI problem: The only way to boot the first CD was to enter expert26 acpi=3Doff' boot option. There is no problem with that, the first part of the installation ran OK (except the point with partman: see below).=20 But at the end of the first part of the installation procedure, there is no way to edit the /etc/lilo.conf. (I tried but the boot=3D/dev/hda lin= e was rejected for unknow reasons). And the acpi=3Doff option is not added to this file... :/=20 So the reboot crashed... I turned the problem around by booting with the first CD of the Woody in rescue mode, corrected the /etc/lilo.conf and ran /sbin/lilo. So, please add to the bootloader configuration files the options the user passed to boot on the first CD. It seems as an evidence that if the user (luser, lurker) passed the acpi=3Doff option when booting the first CD, this option as to be added to the /etc/lilo.conf file (forget about grub... I'm too old :) =20 =20 * 2) The partman problem During the first process install you are prompted to make partitions on your disk(s). The only problem (but it is a big one) is that it is nowhere said that you should press the F12 key to edit the fields you can see. =20 I wanted to make a 4 GB partition for Windows as hda1 (for an eventually future install), then a /dev/hda2 (1GB) for Linux swap and /dev/hda3 (6 GB) for OpenBSD and hda4 extented and full of hda5 to hda14 partitions for my new Linux/Debian/Sarge OS. =20 The problem is that you have to strike the F12 to modify the fields of partman, but it is not said anywhere. I found this out by striking all the keys of the keyboard in a =ABal=E9atoire=BB way which is not a good i= dea in a partition program ! =20 (Sorry I don't know how to translate =ABal=E9atoire=BB, it means I stroke all keys on the keyboard and finally (finlandly ? (it's ajoke: have a smile)) found out F12 makes something). =20 =20 Off course I opened the shell that is proposed in the install menu... The problem is that it is said the HDD partitions are mounted on /target but there is no /target directory. But even if there would
Bug#272136: countrychooser: db_go fails when choosing Arabic as language
Package: countrychooser Version: 1.03 Severity: important This bug may be reproduced on any sid_d-i ISO image. When choosing Arabic as language, the screen flickers instead of displaying countrychooser first screen. Then this screen is displayed, however it is displayed in English. Tracking down this bug, I found that countrychooser postinst fails at the db_go call in the state machine: if db_go; then STATE=$(($STATE + 1)) This makes the debian-installer script fail...It is then restarted by init, but the environment then lacks the LANG variable, so countrychooser postinst is displayed in English and the whole installer then continues in English. This seems related to the display of the Arabic screen, with country names in Arabic. This does not happen in RC1in which the country names were not translated to Arabic because of incomplete iso-codes translation. I suspect some nasty thing related to Arabic display in these conditions but I have no idea how to track this down. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (ignored: LC_ALL set to fr_FR.UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#268491: mapdevfs disk names before showing to user
Jim Lieb wrote: The following patch re-maps partition file names for the select menu. This patch also re-positions the error code capture for the elilo command to immediately follow the command. This patch closes bug 268491. Don't you have commit access? Anyway, I've applied it. -- see shy jo signature.asc Description: Digital signature
Bug#271782: debian-installer: Build-Depends on kbd-chooser udebs which are not in sarge
Goswin von Brederlow wrote: Some more udeb sources missing in sarge: rootskel cdrom-checker anna ddetect debian-installer-utils lowmemcheck main-menu No udeb sources are in sarge, but I am not seeing these build-depends on them that you speak of. -- see shy jo signature.asc Description: Digital signature
Bug#271914: marked as done (Please add the initial boot options to menu.lst)
Your message dated Fri, 17 Sep 2004 13:34:29 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#271890: Installation process on Sarge 20040801 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; 15 Sep 2004 22:14:44 + From [EMAIL PROTECTED] Wed Sep 15 15:14:43 2004 Return-path: [EMAIL PROTECTED] Received: from postfix3-1.free.fr [213.228.0.44] (postfix) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C7i31-0002VP-00; Wed, 15 Sep 2004 15:14:43 -0700 Received: from Deborah.RocknRoll.org (rouen-1-62-147-101-78.dial.proxad.net [62.147.101.78]) by postfix3-1.free.fr (Postfix) with ESMTP id 8AE73173AF9 for [EMAIL PROTECTED]; Thu, 16 Sep 2004 00:14:40 +0200 (CEST) Received: by Deborah.RocknRoll.org (Postfix, from userid 1000) id 07D3E10750; Wed, 15 Sep 2004 18:40:14 +0200 (CEST) Date: Wed, 15 Sep 2004 18:40:14 +0200 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Installation process on Sarge 20040801 Message-ID: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Organization: Guilde des Gardiens de la Foi Debianiste X-Operating-System: Debbie (2.6.7) running on a [EMAIL PROTECTED]/512MB X-Uptime: up 42 days cut User-Agent: Mutt/1.5.5.1+cvs20040105i Content-Transfer-Encoding: quoted-printable 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.5 required=4.0 tests=BAYES_40,DATE_IN_PAST_03_06, HAS_PACKAGE,NO_REAL_NAME,SUBJ_HAS_UNIQ_ID autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: installation-reports There is a possibility this bug report has gone its way in the BTS, but there is a much more high probability it has been forwarded to Dave Null because the first time I have sent it, I have forgotten the Package: line (just because I didn't know what package it was all about). So here is the bug report, it all about Sarge official snapshot 20040801. In the first days of August, using the ADSL connection of my father I have downloaded the 7 first CD of Sarge 20040801 (becoming Sarge 20040808 for the last 2 CDs).=20 =20 Back to my house with a new Centino NoteBook, I tried to install the Sarge on it. =20 * 1) The ACPI problem: The only way to boot the first CD was to enter expert26 acpi=3Doff' boot option. There is no problem with that, the first part of the installation ran OK (except the point with partman: see below).=20 But at the end of the first part of the installation procedure, there is no way to edit the /etc/lilo.conf. (I tried but the boot=3D/dev/hda lin= e was rejected for unknow reasons). And the acpi=3Doff option is not added to this file... :/=20 So the reboot crashed... I turned the problem around by booting with the first CD of the Woody in rescue mode, corrected the /etc/lilo.conf and ran /sbin/lilo. So, please add to the bootloader configuration files the options the user passed to boot on the first CD. It seems as an evidence that if the user (luser, lurker) passed the acpi=3Doff option when booting the first CD, this option as to be added to the /etc/lilo.conf file (forget about grub... I'm too old :) =20 =20 * 2) The partman problem During the first process install you are prompted to make partitions on your disk(s). The only problem (but it is a big one) is that it is nowhere said that you should press the F12 key to edit the fields you can see. =20 I wanted to make a 4 GB partition for Windows as hda1 (for an eventually future install), then a /dev/hda2 (1GB) for Linux swap and /dev/hda3 (6 GB) for OpenBSD and hda4 extented and full of hda5 to hda14 partitions for my new Linux/Debian/Sarge OS. =20 The problem is that you have to strike the F12 to modify the fields of partman, but it is not said anywhere. I found this out by striking all the keys of the keyboard in a =ABal=E9atoire=BB way which is not a good i= dea in a partition program ! =20 (Sorry I don't know how to translate =ABal=E9atoire=BB, it means I stroke all keys on the keyboard and finally (finlandly ? (it's ajoke: have a smile)) found out F12 makes something). =20 =20 Off course I opened the shell that is proposed in the install menu... The problem is that it is said the HDD partitions are mounted on /target but there is no /target directory. But even if there would
Processed: reassign 271978 to netcfg
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.4 reassign 271978 netcfg Bug#271978: netinst, wep key with spaces w/ patch Bug reassigned from package `debian-installer' to `netcfg'. 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]
Bug#271907: Partman doesn't display cciss driver names properly
On Friday 17 September 2004 10:53, Joey Hess wrote: I haven't gotten my cciss hooked up to any disks yet, but this looks obviously either correct, or unlikely to break anything else, so applied.. If you could use some more testing of this, I can try to get my cciss working, just lemme know. I do have one on my rx2600 and have tested against it. some testing on other archs would be useful. -- * Jim LiebWild Open Source Inc. [EMAIL PROTECTED] Cell: 831.295.9317 Office: 831.421.0883Fax: 831.421.0885 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Testing newoldworld pmac miboot 2.6 floppies
On Friday, September 17, 2004, at 01:00 PM, Sven Luther wrote: On Fri, Sep 17, 2004 at 09:42:09AM -0700, Brad Boyer wrote: [Lots of stuff about what's where in a beige G3 ...] Bottom line, Sven, what pieces of information about the G3 do you need from me? Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#271907: Partman doesn't display cciss driver names properly
Jim Lieb wrote: This is a re-submit to add the package header line. Disreard the previous email w/ this same subject line. Sorry. Partman doesn't know how to display the info for various integrated raid controllers. In particular, it cannot display for the HP SMART controller (cciss). This patch properly parses and displays the controller. Patch set follows as attachment I haven't gotten my cciss hooked up to any disks yet, but this looks obviously either correct, or unlikely to break anything else, so applied.. If you could use some more testing of this, I can try to get my cciss working, just lemme know. -- see shy jo signature.asc Description: Digital signature
Re: fresh Sarge install, boot failes
Harald Dunkel wrote: Please check http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=263169 Welcome to the family. Ooops, sorry, I klicked on the [Reply] button in the wrong EMail window. Sorry for the confusion. Harri -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 271978 to netcfg
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.4 reassign 271978 netcfg Bug#271978: netinst, wep key with spaces w/ patch Bug reassigned from package `netcfg' to `netcfg'. 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]
Bug#266872: [i386] [20040816] [netinstall] hwconfig shows minor error
maks attems wrote: finally got this piece of log, it's attached. -- insmod: init_module: ohci1394: No such device -- Smells of a kernel bug, since your lspci clearly shows a Ricoh Co Ltd R5C552 IEEE 1394 Controller. I wonder, does the module load on the final installed system? Also, by now we have a newer kernel in the installer, 2.4.27, it would be interesting to know if you have the same problem with either the currently daily build of installer, or if you cannot try the installer, then with the installed system upgraded to this newer kernel. -- see shy jo signature.asc Description: Digital signature
Fixed in NMU of elilo-installer 1.0
tag 268491 + fixed quit This message was generated automatically in response to a non-maintainer upload. The .changes file follows. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 17 Sep 2004 13:38:54 -0400 Source: elilo-installer Binary: elilo-installer Architecture: source ia64 Version: 1.0 Distribution: unstable Urgency: low Maintainer: Debian Install System Team [EMAIL PROTECTED] Changed-By: Joey Hess [EMAIL PROTECTED] Description: elilo-installer - Install elilo on a hard disk (udeb) Closes: 268491 Changes: elilo-installer (1.0) unstable; urgency=low . * Jim Lieb - Make partition names more people readable. Closes: #268491 * Joey Hess - Insane version number bump. Files: edd8ee76d0948345e3102a6948988442 601 debian-installer standard elilo-installer_1.0.dsc 5f9d20cf08946ffa8c3b3c014b06a79e 28544 debian-installer standard elilo-installer_1.0.tar.gz 1e7d2e85e02e335d399727772ff4bbba 17598 debian-installer standard elilo-installer_1.0_ia64.udeb package-type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBSyZP2tp5zXiKP0wRApEHAJwIzzNT6VJt4RN4rsDyoZwY7OZhVQCghoSt f56ItObCMrgOzF0PtcS/97M= =d8YQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of partman_57_i386.changes
partman_57_i386.changes uploaded successfully to localhost along with the files: partman_57.dsc partman_57.tar.gz partman_57_i386.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of elilo-installer_1.0_ia64.changes
elilo-installer_1.0_ia64.changes uploaded successfully to localhost along with the files: elilo-installer_1.0.dsc elilo-installer_1.0.tar.gz elilo-installer_1.0_ia64.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Fixed in NMU of elilo-installer 1.0
Processing commands for [EMAIL PROTECTED]: tag 268491 + fixed Bug#268491: mapdevfs disk names before showing to user Tags were: d-i Tags added: fixed quit 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]
partman_57_i386.changes ACCEPTED
Accepted: partman_57.dsc to pool/main/p/partman/partman_57.dsc partman_57.tar.gz to pool/main/p/partman/partman_57.tar.gz partman_57_i386.udeb to pool/main/p/partman/partman_57_i386.udeb Announcing to [EMAIL PROTECTED] Closing bugs: 271907 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
elilo-installer_1.0_ia64.changes ACCEPTED
Accepted: elilo-installer_1.0.dsc to pool/main/e/elilo-installer/elilo-installer_1.0.dsc elilo-installer_1.0.tar.gz to pool/main/e/elilo-installer/elilo-installer_1.0.tar.gz elilo-installer_1.0_ia64.udeb to pool/main/e/elilo-installer/elilo-installer_1.0_ia64.udeb Announcing to [EMAIL PROTECTED] Setting bugs to severity fixed: 268491 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272142: Installation Report (Dell Precision 650 + FastTrak S150 TX2plus Controller)
Package: installation-reports INSTALL REPORT Debian-installer-version: sarge-i386-businesscard.iso (Aug 3 Daily) uname -a: Linux sandbox 2.6.8-1-686-smp #1 SMP Sat Aug 28 12:51:43 EDT 2004 i686 GNU/Linux Date: Fri Sep 17 14:20 EDT 2004 Method: Installed from business card cd. Packages downloaded from ftp.debian.org (no proxy was involved) Machine: Dell Precision 650 Processor: 2 x 3.06GHz Xeon Memory: 2 Gig Root Device: sata IDE (FastTrak S150 TX2plus) Root Size/partition table: Disk /dev/sda: 250.0 GB, 2500 bytes 255 heads, 63 sectors/track, 30394 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System Mountpoint /dev/sda1 * 1 486 3903763+ 83 Linux / /dev/sda2 487 30394 2402360105 Extended /dev/sda5 487 972 3903763+ 83 Linux /tmp /dev/sda6 9731945 7815591 83 Linux /usr /dev/sda719462918 7815591 83 Linux /var /dev/sda829193404 3903763+ 82 Linux swap swap /dev/sda93405 30394 216797143+ 83 Linux /home Output of lspci and lspci -n: -- lspci -- :00:00.0 Host bridge: Intel Corp. E7505 Memory Controller Hub (rev 03) :00:01.0 PCI bridge: Intel Corp. E7505/E7205 PCI-to-AGP Bridge (rev 03) :00:02.0 PCI bridge: Intel Corp. E7505 Hub Interface B PCI-to-PCI Bridge (rev 03) :00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01) :00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01) :00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01) :00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI Controller (rev 01) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 81) :00:1f.0 ISA bridge: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) LPC Bridge (rev 01) :00:1f.1 IDE interface: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) UltraATA-100 IDE Controller (rev 01) :00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01) :01:00.0 VGA compatible controller: nVidia Corporation NV30GL [Quadro FX 1000] (rev a2) :02:1c.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04) :02:1d.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04) :02:1e.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04) :02:1f.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04) :03:0e.0 Ethernet controller: Intel Corp. 82545EM Gigabit Ethernet Controller (Copper) (rev 01) :04:0d.0 RAID bus controller: Promise Technology, Inc. PDC20371 (FastTrak S150 TX2plus) (rev 02) :05:0c.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) :05:0e.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04) :05:0e.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04) --- -- lspci -n -- :00:00.0 0600: 8086:2550 (rev 03) :00:01.0 0604: 8086:2552 (rev 03) :00:02.0 0604: 8086:2553 (rev 03) :00:1d.0 0c03: 8086:24c2 (rev 01) :00:1d.1 0c03: 8086:24c4 (rev 01) :00:1d.2 0c03: 8086:24c7 (rev 01) :00:1d.7 0c03: 8086:24cd (rev 01) :00:1e.0 0604: 8086:244e (rev 81) :00:1f.0 0601: 8086:24c0 (rev 01) :00:1f.1 0101: 8086:24cb (rev 01) :00:1f.3 0c05: 8086:24c3 (rev 01) :01:00.0 0300: 10de:0309 (rev a2) :02:1c.0 0800: 8086:1461 (rev 04) :02:1d.0 0604: 8086:1460 (rev 04) :02:1e.0 0800: 8086:1461 (rev 04) :02:1f.0 0604: 8086:1460 (rev 04) :03:0e.0 0200: 8086:100f (rev 01) :04:0d.0 0104: 105a:3371 (rev 02) :05:0c.0 0c00: 104c:8023 :05:0e.0 0401: 1102:0004 (rev 04) :05:0e.2 0c00: 1102:4001 (rev 04) -- 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: [E] [1] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: I popped the disc in, booted, used 'linux26 vga=791' at the prompt and everything went smooth until it was time to detect the hard drives. They didn't appear. I looked at dmesg and didn't see any sign of controllers. So, I dropped to console on vt2 and manually did a: modprobe sata_promise dmesg showed the controller and drives recognized but the installer wouldn't pick up. Based on something I read on google, I rebooted, and at the first prompt for language, dropped to vt2 and installed the module with
Bug#272141: discover1-data: add sata_nv PCI ids
Package: discover1-data Version: 1.2004.08.11 Severity: wishlist Hi, This patch adds support for all the PCI ids that the sata_nv driver in the current kernel claims to support. http://www.no-name-yet.com/patches/discover1-data.sata_nv.diff Thanks, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Testing newoldworld pmac miboot 2.6 floppies
On Friday, September 17, 2004, at 03:55 AM, Sven Luther wrote: On Fri, Sep 17, 2004 at 02:31:09AM -0400, Rick Thomas wrote: Meanwhile, back at the 2.4 ranch... The 2.4 boot floppy read, switched to text mode, asked for root, which read, asked for language (English), then gave me a blue screen which lasted for more than a minute. I switched to the F2 console, killed 4 processes: udpkg --configure --force-configure countrychooser, two more countrychooser, and grep US [this may be a clue]. Back on the main menu on F1 console, I told it to load drivers and fed it the root-2. It read that and decoded it, then put me in the country chooser screen (not blue, this time) I chose US. [possible clue: There is probably a file (the one the grep US was looking for) that is on the root-2 floppy, but is needed by the country chooser, so should be on the root floppy...] Indeed. Do you know the name of the floppy in question ? I'm not sure what you're asking, but here's the table of contents of the directory I got the floppies from... Index of /~luther/d-i/images/2004-09-16/powerpc/floppy-2.4 NameLast modified Size Description Parent Directory26-Aug-2004 21:35 - asian-root.img 16-Sep-2004 01:55 1.1M boot.img16-Sep-2004 01:55 1.4M cd-drivers.img 16-Sep-2004 01:56 1.4M net-drivers.img 16-Sep-2004 01:56 1.4M ofonlyboot.img 16-Sep-2004 01:56 1.4M root-2.img 16-Sep-2004 01:56 1.4M root.img16-Sep-2004 01:58 1.2M Apache/1.3.26 Server at people.debian.org Port 80 It asked for an ethernet driver. The 8139too wasn't listed so I said none of the above to get it to read the net-drivers floppy. It did, and things continued normally til we got to choose a mirror. I chose ftp.us.debian.org but it didn't ask for protocol type or debian version, and when it tried to read stuff, I got the no driver modules message. I hit go back and re-did the mirror choice (presumably at lower priority). This time it did ask for Debian version. I said unstable, and it proceeded without problems until it got to the partitioner. Yes, this is the infamous 2.6.8 modules not in sarge. I may have a solution for this, but it will need some convincing and work. Remember, this is the *2.4* floppy set I'm using here. Does that make any difference? As with previous attempts, the partitioner said no disks found. Also as with previous attempts, poking around on the F2 console shows that it really hasn't found any disks. Ok. We need to know what is your ide controller, and in which udeb it is found, and if discover lists it or not. It's an UltraATA 133/100 Pro for Mac PCI-card, from SIIG, Inc of Freemont CA. It works with kernel 2.4.25 and 2.6.8 installed from a businesscard CD. Output of lspci and lspci -n: :00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) :00:0d.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10) :00:0e.0 SCSI storage controller: Artop Electronic Corp ATP865 (rev 06) :00:0f.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 13) :00:10.0 ff00: Apple Computer Inc. Heathrow Mac I/O (rev 01) :00:12.0 VGA compatible controller: ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT] (rev 9a) :01:08.0 USB Controller: NEC Corporation USB (rev 41) :01:08.1 USB Controller: NEC Corporation USB (rev 41) :01:08.2 USB Controller: NEC Corporation USB 2.0 (rev 02) :01:0b.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link) :00:00.0 0600: 1057:0002 (rev 40) :00:0d.0 0200: 1186:1300 (rev 10) :00:0e.0 0100: 1191:0009 (rev 06) :00:0f.0 0604: 3388:0021 (rev 13) :00:10.0 ff00: 106b:0010 (rev 01) :00:12.0 0300: 1002:4754 (rev 9a) :01:08.0 0c03: 1033:0035 (rev 41) :01:08.1 0c03: 1033:0035 (rev 41) :01:08.2 0c03: 1033:00e0 (rev 02) :01:0b.0 0c00: 104c:8020 I *think* the driver it needs is aec62xx, but doing lspci | grep aec62xx on the F2 console during the install show that driver as having been loaded. So I don't kow what to think. Unless one of the ide-* drivers it claimed to have not found is the culprit? Back at the main menu, I changed installer priority to low, and re-ran detect hardware. It said unable to load some modules listing: ide-scsi, ide-mod, ide-probe-mod, ide-detect, ide-generic, ide-floppy. Presumably one of those is needed to get it to see my IDE disk. Strange. Just for fun, I did a modprobe mesh, and re-ran detect hardware. This time it found my SCSI ZIP disk, and offered to partition it for me. I declined and rebooted to write up this report. Definitively a bug in discover, could you fill a bug report against discover1 with
Processed: reassign 271102 to base-installer
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.4 reassign 271102 base-installer Bug#271102: debian-installer: Installation issue with Installing Base System and mdadm Bug reassigned from package `debian-installer' to `base-installer'. 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]
Bug#268491: marked as done (mapdevfs disk names before showing to user)
Your message dated Fri, 17 Sep 2004 14:51:04 -0400 with message-id [EMAIL PROTECTED] and subject line FWD: Fixed in NMU of elilo-installer 1.0 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; 28 Aug 2004 02:03:16 + From [EMAIL PROTECTED] Fri Aug 27 19:03:16 2004 Return-path: [EMAIL PROTECTED] Received: from kitenet.net [64.62.161.42] (postfix) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C0sYm-0004Pi-00; Fri, 27 Aug 2004 19:03:16 -0700 Received: from dragon.kitenet.net (unknown [66.168.94.144]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN Joey Hess, Issuer Joey Hess (verified OK)) by kitenet.net (Postfix) with ESMTP id 5434A18B7E for [EMAIL PROTECTED]; Sat, 28 Aug 2004 02:03:15 + (GMT) Received: by dragon.kitenet.net (Postfix, from userid 1000) id A8DE36E3FA; Fri, 27 Aug 2004 22:03:34 -0400 (EDT) Date: Fri, 27 Aug 2004 22:03:33 -0400 From: Joey Hess [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: mapdevfs disk names before showing to user Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=sm4nu43k4a2Rpi4c Content-Disposition: inline X-Reportbug-Version: 2.64 User-Agent: Mutt/1.5.6+20040818i 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: --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Package: elilo-installer Severity: wishlist Tags: d-i It would be nicer if elilo-installer could run mapdevfs on the partition name(s) before displaying them in elilo-installer/bootpart. Since bootpart is mapdevfsed right after it's taken from the answer to that question, no necessary info will be lost, and users find devfs names offputting. --=20 see shy jo --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature; name=signature.asc Content-Description: Digital signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBL+f1d8HHehbQuO8RApxDAKC5EUXUay5Kzx2Vlfy38F55q4TB8gCgxqfy FDPyim8dPScg+GM7FSu3q7w= =UdPt -END PGP SIGNATURE- --sm4nu43k4a2Rpi4c-- --- Received: (at 268491-done) by bugs.debian.org; 17 Sep 2004 18:56:13 + From [EMAIL PROTECTED] Fri Sep 17 11:56:13 2004 Return-path: [EMAIL PROTECTED] Received: from kitenet.net [64.62.161.42] (postfix) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C8Nu1-0002uM-00; Fri, 17 Sep 2004 11:56:13 -0700 Received: from dragon.kitenet.net (unknown [66.168.94.144]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN Joey Hess, Issuer Joey Hess (verified OK)) by kitenet.net (Postfix) with ESMTP id 2D41918B04 for [EMAIL PROTECTED]; Fri, 17 Sep 2004 18:50:30 + (GMT) Received: by dragon.kitenet.net (Postfix, from userid 1000) id 415036E7AC; Fri, 17 Sep 2004 14:51:05 -0400 (EDT) Date: Fri, 17 Sep 2004 14:51:04 -0400 From: Joey Hess [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: FWD: Fixed in NMU of elilo-installer 1.0 Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=oiL9LJXJsdjS5rzq Content-Disposition: inline User-Agent: Mutt/1.5.6+20040818i 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=-5.0 required=4.0 tests=BAYES_00,VALID_BTS_CONTROL autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: --oiL9LJXJsdjS5rzq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable - Forwarded message from Joey Hess [EMAIL PROTECTED] - =46rom: Joey Hess [EMAIL PROTECTED] Date: Fri, 17 Sep 2004 14:17:02 -0400 To: [EMAIL PROTECTED] Cc: Joey Hess [EMAIL PROTECTED], Debian Install System Team [EMAIL PROTECTED] Subject: Fixed in NMU of elilo-installer 1.0 tag 268491 + fixed quit This message was
Re: No /dev/modem or similar created on PowerPC?
Russell Hires wrote: I'm just poking around on my G3/266 and I'm noticing that I don't have a /dev/modem, or any tty that links to it. Does the d-i create such a device only if you say that you want to install via ppp? This could be a problem if, for example, you want to use your modem to output a serial console (which is my situation, actually :-) In fact, I can't find (and neither can kppp) which tty connects to my modem. d-i does not know about modems. I think that pppconfig might set a /dev/modem link if you choose to use it to install via modem in base-config, but in general yes, new installs have no /dev/modem link. Probing for modems is a rather risky business that has been known to turn off UPSes and do other fun stuff, I don't think the installer wants to go there. I don't understand what a modem has to do with a serial console BTW. -- see shy jo signature.asc Description: Digital signature
Bug#271102: Aha! I understand the problem now.
Paul Hampson wrote: The issues arises when apt-install mdadm installs mdadm, mdadm --monitor is run without debconf asking questions, as it does if it's installed with apt-get install. In particular, mdadm/start_daemon is skipped, and defaults to true. Now that I've found the process being undertaken for this menu option, I can either manually simulate it myself, or try and stop mdadm starting mdadm --monitor... It looks to me like a change in mdadm caused this, in particular 1.6.0-1's changelog lists: * Changed default to autostart RAID array. (closes: Bug#250792) Of course the bug there was that without this change, mdadm did not start when booting the installed system, so we didn't get raid at all then. Kinda damned if we do and damned if we don't. It sounds as if we need to arrange for mdadm to not be started when the installer is run, but do continue to let it be started afterwards. My ideal preference would be for mdadm --monitor to not run during the install, irrespective of whether the user wants it when the system's running. But short of adding 'killall mdadm' after apt-install mdadm in base-install's postinst, I dunno how else to do that. Well, I think that would be a good quick fix. Note there's no killall in the installer, but you can probably instead add this: chroot /target /etc/init.d/mdadm stop If that works for you well enough we can look for a better fix.. such as applying the patch in bug #264451. -- see shy jo signature.asc Description: Digital signature
Bug#258136: marked as done (Allow reboot action to halt instead)
Your message dated Fri, 17 Sep 2004 15:05:48 -0400 with message-id [EMAIL PROTECTED] and subject line closing 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 Jul 2004 20:44:54 + From [EMAIL PROTECTED] Wed Jul 07 13:44:54 2004 Return-path: [EMAIL PROTECTED] Received: from mta10.adelphia.net [68.168.78.202] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BiJHi-0005LW-00; Wed, 07 Jul 2004 13:44:54 -0700 Received: from mizar.alcor.net ([69.167.148.207]) by mta10.adelphia.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Wed, 7 Jul 2004 16:44:24 -0400 Received: from mdz by mizar.alcor.net with local (Exim 4.34) id 1BiJHE-8O-1Q for [EMAIL PROTECTED]; Wed, 07 Jul 2004 13:44:24 -0700 Date: Wed, 7 Jul 2004 13:44:24 -0700 From: Matt Zimmerman [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: Allow reboot action to halt instead Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Reportbug-Version: 2.63 User-Agent: Mutt/1.5.6+20040523i Sender: Matt Zimmerman [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: di-utils-reboot Severity: wishlist Tags: patch I find it convenient sometimes (especially when using UML) to have d-i halt the system as its final step, rather than rebooting it. Rebooting in UML re-execs the kernel with exactly the same command line, which causes the installer to be started, rather than booting from the installed system. I could also see this being useful for embedded systems, where it is sometimes common to perform the first stage of installation and then stop, shipping an image which will be configured by the end user after flashing it into a device such as a PDA. Anyway, here's a patch: http://www.no-name-yet.com/patches/debian-installer-utils.reboot-halt.diff -- System Information: Debian Release: unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.6-deb1-skas3 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 -- - mdz --- Received: (at 258136-done) by bugs.debian.org; 17 Sep 2004 19:11:13 + From [EMAIL PROTECTED] Fri Sep 17 12:11:13 2004 Return-path: [EMAIL PROTECTED] Received: from kitenet.net [64.62.161.42] (postfix) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C8O8X-0004JC-00; Fri, 17 Sep 2004 12:11:13 -0700 Received: from dragon.kitenet.net (unknown [66.168.94.144]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN Joey Hess, Issuer Joey Hess (verified OK)) by kitenet.net (Postfix) with ESMTP id A593A1885C for [EMAIL PROTECTED]; Fri, 17 Sep 2004 19:05:14 + (GMT) Received: by dragon.kitenet.net (Postfix, from userid 1000) id 2BBCC6E7AC; Fri, 17 Sep 2004 15:05:48 -0400 (EDT) Date: Fri, 17 Sep 2004 15:05:48 -0400 From: Joey Hess [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: closing Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=zhXaljGHf11kAtnf Content-Disposition: inline User-Agent: Mutt/1.5.6+20040818i 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=-3.0 required=4.0 tests=BAYES_00 autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable AFAIK Bastian implemented this for s390 in a different way, so I'm closing the report. Let me know if you need anything else. --=20 see shy jo --zhXaljGHf11kAtnf Content-Type: application/pgp-signature; name=signature.asc Content-Description: Digital signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBSzWMd8HHehbQuO8RAg+PAKDQBFs6wk6e69nHKkAdqrn/Djo4TQCdHmQD
Processed: retitle 272120 to installed system does not boot
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.4 retitle 272120 installed system does not boot Bug#272120: debian-installer beta3/rc1 doesn't boot Changed Bug title. 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: reassign 272120 to installation-reports
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.4 reassign 272120 installation-reports Bug#272120: installed system does not boot Bug reassigned from package `debian-installer' to `installation-reports'. 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: reassign 272123 to discover1-data
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.4 reassign 272123 discover1-data Bug#272123: debian-installer: tg3 network card not recognized automatically Bug reassigned from package `debian-installer' to `discover1-data'. 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]
Bug#272136: countrychooser: db_go fails when choosing Arabic as language
Christian Perrier wrote: This bug may be reproduced on any sid_d-i ISO image. When choosing Arabic as language, the screen flickers instead of displaying countrychooser first screen. Then this screen is displayed, however it is displayed in English. Tracking down this bug, I found that countrychooser postinst fails at the db_go call in the state machine: if db_go; then STATE=$(($STATE + 1)) This makes the debian-installer script fail...It is then restarted by init, but the environment then lacks the LANG variable, so countrychooser postinst is displayed in English and the whole installer then continues in English. This seems related to the display of the Arabic screen, with country names in Arabic. This does not happen in RC1in which the country names were not translated to Arabic because of incomplete iso-codes translation. I suspect some nasty thing related to Arabic display in these conditions but I have no idea how to track this down. This sounds similar to the also unexplained #256405. -- see shy jo signature.asc Description: Digital signature
Bug#272120: debian-installer beta3/rc1 doesn't boot
Marco Ferra wrote: 1. If Lilo is choosen, in the boot process the word LILO appears infinitelly through out the screen: LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO LILO ... it never stops. 2. If GRUB is choose, almost the same happens but it doesn't loop forever. After one or 2 screen full's the GRUB word stop appearing. I've never heard of this exact problem. Can you please tell us the details about your hardware and how the disk is partitioned? I thought this was a problem with Lilo but after seeing GRUB doing the same thing I think the problem may be in the partitioning program (fdisk). Why do you say that the partitioning program is fdisk? -- see shy jo signature.asc Description: Digital signature
Re: No /dev/modem or similar created on PowerPC?
On Friday, September 17, 2004, at 03:12 PM, Joey Hess wrote: Russell Hires wrote: I'm just poking around on my G3/266 and I'm noticing that I don't have a /dev/modem, or any tty that links to it. Does the d-i create such a device only if you say that you want to install via ppp? This could be a problem if, for example, you want to use your modem to output a serial console (which is my situation, actually :-) In fact, I can't find (and neither can kppp) which tty connects to my modem. d-i does not know about modems. I think that pppconfig might set a /dev/modem link if you choose to use it to install via modem in base-config, but in general yes, new installs have no /dev/modem link. Probing for modems is a rather risky business that has been known to turn off UPSes and do other fun stuff, I don't think the installer wants to go there. I don't understand what a modem has to do with a serial console BTW. I think I can clear up a point or two here. OldWorld Macs have two serial RS-232 ports (actually RS-422, but who's counting?) one is marked Printer and the other is marked Modem. In at least some models, the Printer port did not have the RS-232 modem flow-control signals enabled, but the Modem port did -- hence the distinction and the naming convention. Russell is probably *not* talking about using an actual real-live modem. What he's probably talking about is the fact that the Mac Open Firmware sometimes uses the Modem port as a serial console. In order to see the stuff that appears on that line, you need to use a serial cross-over cable (also -- confusingly -- called a null-modem cable) to connect the Modem port to another machine running a terminal emulator (such as macKermit) or an actual real-live terminal from the dark ages. To answer the question Russell is probably asking: The Modem port is called /dev/ttyS0. You didn't ask, and you could probably figure it out for yourself, but just for completeness, the Printer port is called /dev/ttyS1. Note the upper-case S. I've never been able to make it work, but I'm told that when you use kernel boot-time command-line arguments to tell the booting kernel to send it's messages to the serial console port, you should leave off the /dev. Thus: console=ttyS0 Hope this helps! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 272142 to discover1-data
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.4 reassign 272142 discover1-data Bug#272142: Installation Report (Dell Precision 650 + FastTrak S150 TX2plus Controller) Bug reassigned from package `installation-reports' to `discover1-data'. 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]
Bug#272120: debian-installer beta3/rc1 doesn't boot
On Fri, Sep 17, 2004 at 03:23:06PM -0400, Joey Hess wrote: [...] I've never heard of this exact problem. Can you please tell us the details about your hardware and how the disk is partitioned? Of course. I have an asus cuv4x motherboard with bios firmware revision 9 using the ProSavage PM133 chipset. The hard disk is a Western Digital of 30GB (WDC WD307AA). I thought this was a problem with Lilo but after seeing GRUB doing the same thing I think the problem may be in the partitioning program (fdisk). Why do you say that the partitioning program is fdisk? I'm not sure. I remember using the partitioning program with the new devfs and the tool was fdisk. I have made partitions by hand and automatically and the result was the same (the LILO loops). Actually I have seen the common errors of LILO (L... or LI... or LIL...) but I've never seen anything like this before. Before the installation the hard drive was filled with zeros. Could the partitioning program don't understand that the MBR was clean (only ending in 55AA) ? I don't think is a problem with the boot manager because GRUB and LILO showed the same behaviour. My humble guess is that something is bad written in the MBR. Best regards Marco -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Testing newoldworld pmac miboot 2.6 floppies
On Fri, Sep 17, 2004 at 09:55:17AM +0200, Sven Luther wrote: Definitively a bug in discover, could you fill a bug report against discover1 with your lspci and lspci -n output ? You won't get much help out of lspci. These are not PCI devices. The macio chip shows up as one huge PCI device, and the macio layer knows how to /proc/device-tree/aliases then. And this probably means that there is no chance ever of discover discovering them. Oh well. Attached is a tar-ball of /proc/device-tree from this machine. I hope it helps! Rick device-tree.tar.gz Description: GNU Zip compressed data
Bug#272161: Syntax errors in postinst
Package: countrychooser
Version: 1.03
Please apply the attached patch against the postinst.
This will get rid of the following message in the syslog for the
installation after countrychooser has run:
main-menu (process: ): [ :
main-menu (process: ): -n: argument expected
main-menu (process: ):
--- postinst 2004-09-14 01:09:50.0 +0200
+++ new/postinst 2004-09-17 23:51:44.0 +0200
@@ -260,7 +260,7 @@
-a \
${LANGUAGE}_${COUNTRYCODE} != ${LOCALE_LANGUAGECHOOSER} \
-a \
- -n ${LOCALE_LANGUAGECHOOSER_COMPLETE} \
+ -n ${LOCALE_LANGUAGECHOOSER_COMPLETE} \
] ; then
# In details : we revert back to the locale
# defined in languagechooser if countrychooser
@@ -294,7 +294,7 @@
#ar_SY:ar_EG:ar:en_UC:en
# We shouldn't just add this before the former list in case the country
# is changed several times.
-if [ $COUNTRYCODE != $COUNTRYCODE_LANGUAGECHOOSER -a -n $COUNTRYCODE -a -n $LANGUAGE ]; then
+if [ $COUNTRYCODE != $COUNTRYCODE_LANGUAGECHOOSER -a -n $COUNTRYCODE -a -n $LANGUAGE ]; then
LANGUAGELIST=${LANGUAGE}_${COUNTRYCODE}:${LANGUAGELIST}
# Languagelist setting
db_set $languagecode $LANGUAGELIST
Re: grub floppy fails to boot
Haines Brown wrote: The object is to boot a new installation of debian sarge, filesystem reiserfs, from a grub (0.95+cvs20040624-8) boot loader installed on a diskette. Grub has not yet been installed on the target disk because I want the security of a boot floppy in case it gums things up when I do install it (I assume that a grub boot floppy does not need to have grub installed on the hard disk). Reiserfs is a module and you need to have grub load the initrd that goes with your kernel. Joey, I incorrectly assumed that the 2.6.7 kernel had the reiserfs module included, for the 2.4.18-bf2.4 did. I stand corrected, thanks. There's an initrd.img symlink on my target disk / partition that points to /boot/initrd-2.6.7-1-386.img, and so I assumed that all I needed was a grub stanza line such as: initrd /initrd.img No luck. The boot failed. Grub reports: ... initrd /initrd.img Error 15: File not found I tried various things without luck, including initrd /boot/initrd-2.6.7-1-386.img I decided to install grub on the target hard disk MBR and create a grub boot diskette from it (I can mount the target HD for some reason from the grub bootloader in the MBR of my principal running disk). Although I confirmed that grub was installed/configured on the target HD, it had failed to create the /boot/grub subdirectory, and so stage1, stage2 and menu.lst were not available for the creation a grub boot floppy. When I created that grub subdirectory and copied the stage1 and stage2 files from target HD /lib/boot/386-pc into it, only then could I run #grub on the booted target HD to create a boot floppy: grub setup (fd0) checking if boot/grub/stage1 exists... yes checking if boot/grub/stage2 exists... yes Running install /boot/grub/stage1 (fd0) /boot/grub/stage2 (fd0) p /boot/grub/menu.lst... suceeded Done However, it lied. There was no /boot/grub/menu.lst file on the floppy. It seems that that grub installation on the target HD failed to create the grub subdirectory on the floppy and put stage1 and stage2 into it and create a menu.lst, just as it had failed to do so on the target HD. I assume this is why I could not then create a grub boot floppy from my target system. Incidentally, is the p in the fifth line above significant? Haines Brown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Modifying d-i to replicate hosts (revisited)
In re: http://lists.debian.org/debian-boot/2004/05/msg03855.html http://lists.debian.org/debian-boot/2004/05/msg03873.html Joey Hess wrote: If you mae replicator-udeb provide all the same things as base-installer, as well as providing base-installer, and have a XB-Installer-Menu-Item that is say, one less than base-installer's, it should be run before base-installer, and then the base-installer run skipped over. I'm working on a system restore setup based on d-i, and am creating a udeb that will unpack a 'dar' archive from CD, DVD(, or NFS; future). I'd like the same disc to double as a standard d-i netinst, and I'm wondering if there's a way to offer a choice between running 'base- installer' or my 'base-dar-installer'? That could be done either with a boot command line option or by prompting. If I have it provide the same things that base-installer does and give it the same menu priority, will the menu be displayed? Perhaps what I ought to do is give it a menu sort priority slightly lower than base-installer, then if it's to be used as a d-i netinst, just boot it in expert mode. Will that do what I expect, which is that at each stage I get the full menu, with no automatic progression? -- Karl Hegbloom (o_ mailto:[EMAIL PROTECTED] //\ jabber:[EMAIL PROTECTED] V_/_ yahoo:karlheg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
partman-auto recipes (RAID and LVM2, leaving /home intact) ?
Does anyone have any partman-auto recipes developed that I can have a look at? Is it possible for it to automate setup of RAID and LVM2? Is it possible to automate not formatting a /home partition, leaving it intact and mounting it on the /target/home? The project I'm trying to do is a restore / rescue disc that can restore from a 'dar' archive on CD or DVD. It should be capable of leaving /home and /opt alone, since the dar image may be nothing more than a VAR distro image. In the case where there is only one large / partition, I would like to have the capability of noticing that, and moving aside all but /target/home and /target/opt, say to /target/oldsys prior to calling on a (to be written rsn) 'base-dar-installer'. How should I manage that, in the context of d-i? Is that something that an extension of 'partman' should do, or what? I need help. -- Karl Hegbloom (o_ mailto:[EMAIL PROTECTED] //\ jabber:[EMAIL PROTECTED] V_/_ yahoo:karlheg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
is this a bug
debain installer seems unable to load net drivers from the second floppy drive is this a bug and if so where should it be reported -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
plans for d-i rc2 (and Oldenburg meeting)
We seem to be in relatively good shape for another release at the moment; as far as I know there's little significant new breakage. We seem to have a lot of patches piling up in the BTS, and we should perhaps try to go over those and work out which are worth applying before a release. We also need to think about scheduling a string freeze for the next release. We've been tracking issues at the top of TODO, though most of them lately have not been problems with d-i, but with the second stage install. I'll trim it to the d-i issues: Things we really should fix before rc2: - finish 2.6.8 and 2.4.27 kernel upgrades, all applicable arches - fix syslinux parameter bug #269424 Things that would be nice for rc2, but can't block it: - pcmcia-cs resource range detection (untested patch from per) - vmelilo-installer needs to remove no_bootloader from /target/etc/kernel-img.conf - support for root on raid Since a string freeze takes at least a week, and getting all the images built and tested for release took two weeks last time, we're still some time from a rc2 release. The Oldenburg meeting is coming up next week, and I dislike trying to do releases at such meetings. Still, we've probably now reached the point where installation reports from rc1 are less useful, and where we want users to be trying the latest version of the installer. So I propose that we do a release that is not a release candidate. We could call this a test candidate (but users seemed to find that confusing before), or a technology preview release. Some of the nice new features would include - - root on LVM (done) - preseeding automatic installs (nearly done) - new kernels (nearly done) - whatever else has been done that I've forgotten about - whatever else we do at Oldenburg This release would not rc1 involve a string freeze and a full set of updated translations. It might even be broken on some architectures, if some arches are currently broken. It would simply be a consistent snapshot of what we have accomplished in the 2 months since rc1. It would probably still take about a week to get it built and released; the release building could begin right after Oldenburg for a release near the beginning of next month. The rc2 release would then probably not happen until the end of next month. Alternatively, we could skip this and go ahead with getting rc2 out immediatly after Oldenburg. That would mean probably a string freeze the last week of this month, and a rc2 release near the middle of next month. Which alternative is better, I leave up to you -- and the timetables of the release managers. I also wanted to touch on what we plan to work on at the Oldenburg meeting. I realise that everyone has their own set of things they'd like to work on there, but I also I think we should have a group goal for that meeting. If we had a new architecture available, then would be a great time to do a port to it. (Or we could try to port d-i to debian bsd there..). Or we could try to get the root raid stuff finally sorted out, or add some other new feature or important bug fix to the installer. Or make sure the installation manual is ready for all architectures. The point is to have a set goal that everyone can work on and that we can complete during the meeting. -- see shy jo signature.asc Description: Digital signature
Re: partman-auto recipes (RAID and LVM2, leaving /home intact) ?
Karl Hegbloom wrote:
Does anyone have any partman-auto recipes developed that I can have a
look at?
I have a few trivial and unintersting ones for things like a small /boot
partition.
Is it possible for it to automate setup of RAID and LVM2?
It's not possible yet since partman-auto does not run the lvmcfg and
mdcfg setup programs. I suspect that the recipe file format is
sufficient, but it will take some more work to make those programs
automatable and get it to work.
Is it possible to automate not formatting a /home partition, leaving it
intact and mounting it on the /target/home?
Yes of course. I suggest you read
installer/doc/devel/partman-auto-recipe.txt. Note the format{ }
specifier.
In the case where there is only one large / partition, I would like to
have the capability of noticing that, and moving aside all
but /target/home and /target/opt, say to /target/oldsys prior to calling
on a (to be written rsn) 'base-dar-installer'. How should I manage
that, in the context of d-i? Is that something that an extension of
'partman' should do, or what? I need help.
I think you would need some kind of additional udeb to do what you need,
either before partman runs or as part of partman.
--
see shy jo
signature.asc
Description: Digital signature
Re: Modifying d-i to replicate hosts (revisited)
Karl Hegbloom wrote: I'd like the same disc to double as a standard d-i netinst, and I'm wondering if there's a way to offer a choice between running 'base- installer' or my 'base-dar-installer'? That could be done either with a boot command line option or by prompting. If I have it provide the same things that base-installer does and give it the same menu priority, will the menu be displayed? No, main-menu does not currently give a choice in this situation, it always picks the first one. Perhaps what I ought to do is give it a menu sort priority slightly lower than base-installer, then if it's to be used as a d-i netinst, just boot it in expert mode. Will that do what I expect, which is that at each stage I get the full menu, with no automatic progression? Yes, that's right. You can do interesting things with isinstallable files, to, for example, make your new menu item disappaear from the menu. Take a look at the isinstallable file of grub-installer, which does this if the root filesystem is on XFS, to let lilo-installer be autorun instead, for example. -- see shy jo signature.asc Description: Digital signature
Re: is this a bug
peter green wrote: debain installer seems unable to load net drivers from the second floppy drive is this a bug and if so where should it be reported Does this describe your problem? http://bugs.debian.org/225220 -- see shy jo signature.asc Description: Digital signature
RE: is this a bug
sounds like it the boot floppy was still in the first floppy drive at the time -Original Message- From: Joey Hess [mailto:[EMAIL PROTECTED] Sent: 18 September 2004 01:24 To: peter green Cc: [EMAIL PROTECTED] Subject: Re: is this a bug peter green wrote: debain installer seems unable to load net drivers from the second floppy drive is this a bug and if so where should it be reported Does this describe your problem? http://bugs.debian.org/225220 -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
bypassing partman
for various reasons i want to be able to use debian installer to install on a block device that is not a partition is there any way to bypass partman and set up the mappings between mountpoints and block devices manually? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272176: does not show size of new partitions when making VG
Package: partman-lvm Severity: normal Tags: d-i I had a few existing partitions, and I switched one of them from ext3 to part be used for LVM in partman, and configud LVM. WHen creating the volume group, it prompts what partitions to put it in. Other partitions that already existed and were already set to be used as LVM before this install run show up here with their size in parens, but for this new partition, it does not seem to have size information at this point. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27 Locale: LANG=en_US, LC_CTYPE=en_US -- see shy jo signature.asc Description: Digital signature
Processing of debian-installer-utils_1.06_i386.changes
debian-installer-utils_1.06_i386.changes uploaded successfully to localhost along with the files: debian-installer-utils_1.06.dsc debian-installer-utils_1.06.tar.gz di-utils-reboot_1.06_all.udeb di-utils-exit-installer_1.06_all.udeb di-utils_1.06_all.udeb di-utils-terminfo_1.06_all.udeb di-utils-shell_1.06_i386.udeb di-utils-mapdevfs_1.06_i386.udeb di-utils-bootfloppy_1.06_i386.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#264451: marked as done (di-utils: apt-install should not start daemons)
Your message dated Fri, 17 Sep 2004 21:32:02 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#264451: fixed in debian-installer-utils 1.06
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; 8 Aug 2004 22:34:22 +
From [EMAIL PROTECTED] Sun Aug 08 15:34:22 2004
Return-path: [EMAIL PROTECTED]
Received: from 217-13-7-10.dd.nextgentel.com (minerva.hungry.com) [217.13.7.10]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BtwFC-0006ZS-00; Sun, 08 Aug 2004 15:34:22 -0700
Received: from pere by minerva.hungry.com with local (Exim 3.35 #1 (Debian))
id 1BtwFp-0006Fq-00; Mon, 09 Aug 2004 00:35:01 +0200
To: [EMAIL PROTECTED]
Subject: di-utils: apt-install should not start daemons
From: Petter Reinholdtsen [EMAIL PROTECTED]
Message-Id: [EMAIL PROTECTED]
Sender: Petter Reinholdtsen [EMAIL PROTECTED]
Date: Mon, 09 Aug 2004 00:35:01 +0200
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=-5.0 required=4.0 tests=BAYES_00,DRUGSPAM,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: di-utils
Version: 1.00
Severity: important
Tags: d-i
Packages installing daemons should not be allowed to start the daemon
inside /target/. Packages installed with debootstrap will not do
this, because debootstrap replaces start-stop-daemon, but apt-install
do not do anything to avoid this.
See debian-boot thread cardmgr start message during base install
(extra packages) for a discussion around this issue.
Here is an untested patch with a proposed solution:
From: Per Olofsson
Subject: Re: cardmgr start message during base install (extra packages)
To: debian-boot
Date: Thu, 29 Jul 2004 18:09:17 +0200
Petter Reinholdtsen wrote:
Here is a patch to divert start-stop-daemon. Mostly unsteded, but
half of it is cut-n-paste from my upgrade-testing script.
And here's an (untested) patch which also adds policy-rc.d
support. Furthermore it corrects a problem in your patch: it runs
cleanup code if apt-get fails.
Index: apt-install
===
--- apt-install (revision 18584)
+++ apt-install (working copy)
@@ -36,6 +36,42 @@
fi
fi
+# Create a policy-rc.d to stop maintainer scripts using invoke-rc.d from
+# running init scripts
+make_policy-rc.d() {
+ cat /target/usr/sbin/policy-rc.d EOF
+#!/bin/sh
+exit 101
+EOF
+ chmod a+rx /target/usr/sbin/policy-rc.d
+}
+remove_policy-rc.d() {
+ rm -f /target/usr/sbin/policy-rc.d
+}
+
+# This way to make start-stop-daemon do not work on upgrades, when
+# start-stop-daemon is replaced with a new version. I tried to use
+# dpkg-divert to solve this, but am not sure I got it right. [pere
+# 2004-07-29]
+make_dummy_start_stop_daemon() {
+ cat /target/sbin/start-stop-daemon.dummy EOF
+#!/bin/sh
+echo 12
+echo 'Warning: Fake start-stop-daemon called, doing nothing.' 12
+exit 0
+EOF
+ chmod a+rx /target/sbin/start-stop-daemon.dummy
+ chroot /target dpkg-divert --add --local --rename /sbin/start-stop-daemon
+ ln -s start-stop-daemon.dummy /target/sbin/start-stop-daemon
+}
+remove_dummy_start_stop_daemon() {
+ rm /target/sbin/start-stop-daemon
+ chroot /target dpkg-divert --remove --local --rename /sbin/start-stop-daemon
+}
+
+make_policy-rc.d
+make_dummy_start_stop_daemon
+
# Unset to avoid problems with packages using debconf. This should
# avoid the following error when installing dash:
# /var/lib/dpkg/info/ash/config: 1: Bad file descriptor
@@ -59,8 +95,12 @@
mount -t proc proc /target/proc
fi
-DEBIAN_FRONTEND=noninteractive \
-chroot /target apt-get -y install $@ /dev/null $log 21
+if ! DEBIAN_FRONTEND=noninteractive \
+ chroot /target apt-get -y install $@ /dev/null $log 21; then
+ remove_dummy_start_stop_daemon
+ remove_policy-rc.d
+ exit 1
+fi
# Undo the mounts done by the packages during installation.
# Reverse sorting to umount the deepest mount points first.
@@ -77,4 +117,7 @@
rm -f /tmp/mount.pre
+remove_dummy_start_stop_daemon
+remove_policy-rc.d
+
exit 0
--
Pelle
---
Received: (at 264451-close) by bugs.debian.org; 18 Sep 2004 01:38:09 +
From [EMAIL PROTECTED] Fri Sep 17 18:38:09 2004
Return-path: [EMAIL PROTECTED]
Received: from
debian-installer-utils_1.06_i386.changes ACCEPTED
Accepted: debian-installer-utils_1.06.dsc to pool/main/d/debian-installer-utils/debian-installer-utils_1.06.dsc debian-installer-utils_1.06.tar.gz to pool/main/d/debian-installer-utils/debian-installer-utils_1.06.tar.gz di-utils-bootfloppy_1.06_i386.udeb to pool/main/d/debian-installer-utils/di-utils-bootfloppy_1.06_i386.udeb di-utils-exit-installer_1.06_all.udeb to pool/main/d/debian-installer-utils/di-utils-exit-installer_1.06_all.udeb di-utils-mapdevfs_1.06_i386.udeb to pool/main/d/debian-installer-utils/di-utils-mapdevfs_1.06_i386.udeb di-utils-reboot_1.06_all.udeb to pool/main/d/debian-installer-utils/di-utils-reboot_1.06_all.udeb di-utils-shell_1.06_i386.udeb to pool/main/d/debian-installer-utils/di-utils-shell_1.06_i386.udeb di-utils-terminfo_1.06_all.udeb to pool/main/d/debian-installer-utils/di-utils-terminfo_1.06_all.udeb di-utils_1.06_all.udeb to pool/main/d/debian-installer-utils/di-utils_1.06_all.udeb Announcing to [EMAIL PROTECTED] Closing bugs: 264451 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#271102: Aha! I understand the problem now.
On Fri, Sep 17, 2004 at 03:07:12PM -0400, Joey Hess wrote: Paul Hampson wrote: The issues arises when apt-install mdadm installs mdadm, mdadm --monitor is run without debconf asking questions, as it does if it's installed with apt-get install. In particular, mdadm/start_daemon is skipped, and defaults to true. Now that I've found the process being undertaken for this menu option, I can either manually simulate it myself, or try and stop mdadm starting mdadm --monitor... It looks to me like a change in mdadm caused this, in particular 1.6.0-1's changelog lists: * Changed default to autostart RAID array. (closes: Bug#250792) Of course the bug there was that without this change, mdadm did not start when booting the installed system, so we didn't get raid at all then. Kinda damned if we do and damned if we don't. It sounds as if we Actually, not quite... I'm referring to mdadm --monitor which is seperate from starting raid support, as far as I can tell It's two different environment variables in /etc/default/mdadm. (I can't recall what they _are_ mind you... AUTOSTART and AUTOSTART_DAEMON I think.) As I said, I'm not sure if the above change modified _both_ variables to default to true. My initial reading suggested that only one was, but I've not looked through snapshots.debian.net to check. need to arrange for mdadm to not be started when the installer is run, but do continue to let it be started afterwards. My ideal preference would be for mdadm --monitor to not run during the install, irrespective of whether the user wants it when the system's running. But short of adding 'killall mdadm' after apt-install mdadm in base-install's postinst, I dunno how else to do that. Well, I think that would be a good quick fix. Note there's no killall in the installer, but you can probably instead add this: chroot /target /etc/init.d/mdadm stop If that works for you well enough we can look for a better fix.. such as applying the patch in bug #264451. That would work, since the mdadm-udeb (I think?) already starts the raid arrays... I'll give it a try hopefully this weekend, and see how it goes with that patch (which I see has been applied. ^_^) I suspect a tangent to this issue is that when apt-install installs mdadm, the debconf prompts aren't shown. (Since it sets DEBCONF_FRONTEND=noninteractive)... I assume it does this to not muck with debian-installer, but... Hmm. I guess that's why we _have_ defaults... Maybe base-installer could put up a note If you want to change where your mdadm notification emails go, dpkg-reconfigure mdadm or change /etc/default/mdadm? -- --- Paul TBBle Hampson, MCSE 7th year CompSci/Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] No survivors? Then where do the stories come from I wonder? -- Capt. Jack Sparrow, Pirates of the Caribbean This email is licensed to the recipient for non-commercial use, duplication and distribution. --- signature.asc Description: Digital signature
Bug#272136: countrychooser: db_go fails when choosing Arabic as language
I suspect some nasty thing related to Arabic display in these conditions but I have no idea how to track this down. This sounds similar to the also unexplained #256405. (Arabic hanging on countrychooser) I will try to narrow down this to either the short country list template or the list of countries. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#256405: Bug#272136: countrychooser: db_go fails when choosing Arabic as language
This sounds similar to the also unexplained #256405. By the way, 256405 does not happen anymore Should we close it even if it not explained? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272142: Installation Report (Dell Precision 650 + FastTrak S150 TX2plus Controller)
I popped the disc in, booted, used 'linux26 vga=791' at the prompt and everything went smooth until it was time to detect the hard drives. They didn't appear. I looked at dmesg and didn't see any sign of controllers. So, I dropped to console on vt2 and manually did a: modprobe sata_promise dmesg showed the controller and drives recognized but the installer wouldn't pick up. Based on something I read on google, I rebooted, and at the first prompt for language, dropped to vt2 and installed the module with 'modprobe' This time, the drives were correctly found and easily partitioned. Other than that, the install went smoothly. This is probably already a fixed issue (since my iso is old but I didn't have any spare media around to try a new daily) but I wanted to mention it just in case. Could you re-test with a daily build in the next days ? Just go up to the HD detection step and see if the SATA controller is detected now. As nothing is written on the disk, you can do this without killing the installed system. Testing this is somewhat important as such machines are relatively common. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272132: No kernel modules found
I confirmed that this is happening with a fresh checkout from CVS this evening, under both netboot and netboot_2.6 builds. I've not read the hardware detection and module loading parts of this installer before and will probably not dig deeper this evening. Thanks Bruce gustavo wrote: Package: installation-reports Debian-installer-version: http://people.debian.org/~joeyh/d-i/images/daily/netboot/netboot.tar.gz (16-Sep-2004 12:32 7.5M ) uname -a: 2.6.8-1 and CD Debian testing (Sarge) from date: Fri, 06 Aug 2004 19:36:21 UTC Date: 11-sep-2004 Method: Network install, with dhcp server in second computer. Machine: Toshiba Portege R100. Processor: 900MHz Pentium M with 1MB of Level 2 cache. Memory: 256MB onboard, with a spare slot which can take 128-1024MB. Root Device: Toshiba MK3004GAH 30GBi. Root Size/partition table: lspci 00:1d.0 USB Controller: Intel Corp.: Unknown device 24c2 (rev 03) 00:1d.1 USB Controller: Intel Corp.: Unknown device 24c4 (rev 03) 00:1d.7 USB Controller: Intel Corp.: Unknown device 24cd (rev 03) 00:1e.0 PCI bridge: Intel Corp. 82820 820 (Camino 2) Chipset PCI (-M) (rev 83) 00:1f.0 ISA bridge: Intel Corp.: Unknown device 24cc (rev 03) 00:1f.1 IDE interface: Intel Corp.: Unknown device 24ca (rev 03) 00:1f.5 Multimedia audio controller: Intel Corp.: Unknown device 24c5 (rev 03) 00:1f.6 Modem: Intel Corp.: Unknown device 24c6 (rev 03) 01:00.0 VGA compatible controller: Trident Microsystems: Unknown device 2100 (rev 91) 02:08.0 Ethernet controller: Intel Corp.: Unknown device 103d (rev 83) 02:0a.0 Network controller: Intel Corp.: Unknown device 1043 (rev 04) 02:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus Bridge with ZV Support (rev 33) 02:0d.0 System peripheral: Toshiba America Info Systems: Unknown device 0805 (rev 05) lspci -n: 00:00.0 Class 0600: 8086:3340 (rev 03) 00:01.0 Class 0604: 8086:3341 (rev 03) 00:1d.0 Class 0c03: 8086:24c2 (rev 03) 00:1d.1 Class 0c03: 8086:24c4 (rev 03) 00:1d.7 Class 0c03: 8086:24cd (rev 03) 00:1e.0 Class 0604: 8086:2448 (rev 83) 00:1f.0 Class 0601: 8086:24cc (rev 03) 00:1f.1 Class 0101: 8086:24ca (rev 03) 00:1f.5 Class 0401: 8086:24c5 (rev 03) 00:1f.6 Class 0703: 8086:24c6 (rev 03) 01:00.0 Class 0300: 1023:2100 (rev 91) 02:08.0 Class 0200: 8086:103d (rev 83) 02:0a.0 Class 0280: 8086:1043 (rev 04) 02:0b.0 Class 0607: 1179:0617 (rev 33) 02:0d.0 Class 0880: 1179:0805 (rev 05) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:OK Configure network HW: OK Config network: OK Detect CD: [ ] Load installer modules: Error Detect hard drives: ( ) Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: I'm using the network install from [1]. I was try the next kernel parameters: linux, expert, linux26 and expert26. The problem happens in the Download installer components. The message is: No kernel modules were found. Probaly is due to a mismatch between the kernel ... This problem start happend happen after the image from the day 11 of september, before that I was report another bug (Bug#271214) I also write in [2] the file 'var/log/messages' from the net-install. thank you. [1] http://people.debian.org/~joeyh/d-i/images/daily/netboot/ [2] var/log/messages: insmod /lib/modules/2.6.8-1-386/kernel/drivers/net/mii.ko insmod /lib/modules/2.6.8-1-386/kernel/drivers/net/e100.ko -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBPgRbgm/Kwh6ICoQRAk37AJ4rUiXraRjibEnURT/ZTHF2nr894gCgpvDc QsB1o82LAXTXwyVILhuRcVU= =1TVe -END PGP SIGNATURE-
