Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
On Sat, Apr 10, 2004 at 01:24:27AM -0400, Rick_Thomas wrote: > On Fri, 2004-04-09 at 14:28, Rick Thomas wrote: > > > Malte Cornils wrote: > > > > > > but I would appreciate it if someone > > > could test the current images (Holger?) on similar hardware. > > > > > > I'll test the latest daily-build boot floppies this weekend on both of > > my test machines and send you a report. > > > Sven and/or Colin: For this purpose, please tell me the location of the > latest/greatest boot-floppy images. http://people.debian.org/~luther/debian-installer/daily-powerpc-built/current/powerpc-small/floppy/ Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
On Fri, 2004-04-09 at 16:02, Frans Pop wrote: > > On Friday 09 April 2004 21:49, Rick Thomas wrote: > > This is OldWorld PowerMac. > > > > Booting off of floppy uses the miboot bootloader. It's not like lilo or > > grub on i386. There's no point in the process where you get to enter > > that kind of stuff. > > > That means you'd probably like one of the first questions the installer asks > to be "At which level would you like to install: normal, medium, expert". > Or something like that. > (There have been several discussions on the list about the best naming of the > different levels.) > > Personally I wouldn't mind a question like that for i386, but it looks like it > is necessary for your platform. Yes. I'd say that something like that is necessary for full functionality on OldWorld Macs. Actually, I'd go much farther than that. Here's part of my wish-list for my dream installer someday: I'd like to be able -- easily, simply, and transparently -- to navigate up and down the detail hierarchy at will. For example, here's one possible way to do what I'd like. There are a whole universe of other ways, many probably much better than this one. This is just the first one that came to my mind. At any point in the process, the user should be able to hit "escape" (or some other key -- "escape" just has the advantage that it's mnemonic for "stepping out of line") and immediately switch to the next more detailed level of configuration questions. Some other key (maybe "alt-escape"?) should do the opposite -- shift to the next less detailed level. It may be necessary to insert additional check-points in the lowest detail (most fully automatic) level of the process to allow the user to "escape" at those points if they need to. This extra interactivity would slow down the default installation process -- a possible drawback. Maybe this could be made less of a problem by allowing a sort of "zero detail"/"batch mode" install, where all the configuration questions are answered in advance of the installation by filling out a configuration file. It may be desirable to have a more fine-grained hierarchy of levels of detail than the current three "normal"/"medium"/"expert". Carrying this principle to it's logical extreme, it should be possible (and easy) for the user to navigate *any and all* hierarchies in the d-i. Examples of the kind of hierarchies I'm referring to are: (*) the above mentioned "automatic" vs "user-specified" configuration spectrum. (*) the spectrum between "novice who needs chatty explanations" vs "expert who is thoroughly familiar with the installer, and just wants to get the job done as fast as possible" (*) the spectrum between "bare-bones minimal" vs "fully-featured" application package-sets. etc... As I said, it's all wish-list stuff. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#212921: marked as done (cdebconf: Merge in new translations in templates)
Your message dated Sat, 10 Apr 2004 01:47:02 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#212921: fixed in cdebconf 0.60 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; 26 Sep 2003 21:57:47 + >From [EMAIL PROTECTED] Fri Sep 26 16:57:45 2003 Return-path: <[EMAIL PROTECTED]> Received: from worksh02.hrz.uni-oldenburg.de (minerva.hungry.com) [134.106.38.33] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1A30av-0002sV-00; Fri, 26 Sep 2003 16:57:45 -0500 Received: from pere by minerva.hungry.com with local (Exim 3.35 #1 (Debian)) id 1A30av-0002Il-00; Fri, 26 Sep 2003 23:57:45 +0200 To: [EMAIL PROTECTED] Subject: cdebconf: Merge in new translations in templates From: Petter Reinholdtsen <[EMAIL PROTECTED]> Message-Id: <[EMAIL PROTECTED]> Sender: Petter Reinholdtsen <[EMAIL PROTECTED]> Date: Fri, 26 Sep 2003 23:57:45 +0200 Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-4.0 required=4.0 tests=BAYES_60,HAS_PACKAGE version=2.53-bugs.debian.org_2003_9_21 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_9_21 (1.174.2.15-2003-03-30-exp) Package: cdebconf Version: 0.42 We should modify cdebconf to do a compare of the English text and merge when loading new templates. This is to support add-on modules that may contain a complete translation for a given language, detached from the modules that are translated. If the English text differ, the new template should replace the old one. --- Received: (at 212921-close) by bugs.debian.org; 10 Apr 2004 05:53:02 + >From [EMAIL PROTECTED] Fri Apr 09 22:53:01 2004 Return-path: <[EMAIL PROTECTED]> Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BCBQL-0007QT-00; Fri, 09 Apr 2004 22:53:01 -0700 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1BCBKY-00011Q-00; Sat, 10 Apr 2004 01:47:02 -0400 From: Joey Hess <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.47 $ Subject: Bug#212921: fixed in cdebconf 0.60 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Sat, 10 Apr 2004 01:47:02 -0400 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: X-CrossAssassin-Score: 1 Source: cdebconf Source-Version: 0.60 We believe that the bug you reported is fixed in the latest version of cdebconf, which is due to be installed in the Debian FTP archive: cdebconf-newt-udeb_0.60_i386.udeb to pool/main/c/cdebconf/cdebconf-newt-udeb_0.60_i386.udeb cdebconf-priority_0.60_i386.udeb to pool/main/c/cdebconf/cdebconf-priority_0.60_i386.udeb cdebconf-text-udeb_0.60_i386.udeb to pool/main/c/cdebconf/cdebconf-text-udeb_0.60_i386.udeb cdebconf-udeb_0.60_i386.udeb to pool/main/c/cdebconf/cdebconf-udeb_0.60_i386.udeb cdebconf_0.60.dsc to pool/main/c/cdebconf/cdebconf_0.60.dsc cdebconf_0.60.tar.gz to pool/main/c/cdebconf/cdebconf_0.60.tar.gz cdebconf_0.60_i386.deb to pool/main/c/cdebconf/cdebconf_0.60_i386.deb libdebconfclient0-dev_0.60_i386.deb to pool/main/c/cdebconf/libdebconfclient0-dev_0.60_i386.deb libdebconfclient0-udeb_0.60_i386.udeb to pool/main/c/cdebconf/libdebconfclient0-udeb_0.60_i386.udeb libdebconfclient0_0.60_i386.deb to pool/main/c/cdebconf/libdebconfclient0_0.60_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joey Hess <[EMAIL PROTECTED]> (supplier of updated cdebconf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 10 Apr 2004 01:15:58 -0400 Source: cdebconf Binary: cdebconf-slang-udeb libdebconfclient0 cdebconf-priority cdebconf libdebconfclient0-dev cdebconf-udeb libdebconfclient0-udeb cdeb
Processed: Reassign bug
Processing commands for [EMAIL PROTECTED]: > reassign 242983 console-data Bug#242983: keyboard list untranslated Bug reassigned from package `kbd-chooser' to `console-data'. > tags 242983 pending Bug#242983: keyboard list untranslated Tags were: d-i Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Who do you have to sleep with / bribe / shoot to get an answer about RAID support
Quoting Mark Demma ([EMAIL PROTECTED]): > this happen on my own. Its a shame that something this important is No it is not a "shame". I maybe overreact because I'm not a native speaker but calling this a "shame" as we call this in french "c'est une honte" is needlessly aggressive, especially to people who are currently doing other work on Debian Installer even for getting it install on that old Sinclair. You may regret this, for sure. But, well, this is the way Debian works for years : things are done when someone has enough interest AND skills AND time for doing them. So, sorry to say this, but if software RAID is that important for you that the world should stop if you don't have itmake all your possible for finding someone to do it. *this* is definitely the way Debian works. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cdebconf_0.60_i386.changes ACCEPTED
Accepted: cdebconf-newt-udeb_0.60_i386.udeb to pool/main/c/cdebconf/cdebconf-newt-udeb_0.60_i386.udeb cdebconf-priority_0.60_i386.udeb to pool/main/c/cdebconf/cdebconf-priority_0.60_i386.udeb cdebconf-text-udeb_0.60_i386.udeb to pool/main/c/cdebconf/cdebconf-text-udeb_0.60_i386.udeb cdebconf-udeb_0.60_i386.udeb to pool/main/c/cdebconf/cdebconf-udeb_0.60_i386.udeb cdebconf_0.60.dsc to pool/main/c/cdebconf/cdebconf_0.60.dsc cdebconf_0.60.tar.gz to pool/main/c/cdebconf/cdebconf_0.60.tar.gz cdebconf_0.60_i386.deb to pool/main/c/cdebconf/cdebconf_0.60_i386.deb libdebconfclient0-dev_0.60_i386.deb to pool/main/c/cdebconf/libdebconfclient0-dev_0.60_i386.deb libdebconfclient0-udeb_0.60_i386.udeb to pool/main/c/cdebconf/libdebconfclient0-udeb_0.60_i386.udeb libdebconfclient0_0.60_i386.deb to pool/main/c/cdebconf/libdebconfclient0_0.60_i386.deb Announcing to [EMAIL PROTECTED] Closing bugs: 212921 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No network after install w/ realtek/8139too-fixed
On Fri, 9 Apr 2004 18:58:11 -0400 glenn <[EMAIL PROTECTED]> wrote: > Using the boot/root floppies I am able to configure the network and install Debian > from the >net and everything seems to work fine. On reboot however I have no > network. dmesg says the >card is detected but I have no tools available to see if > the modules are lodeded nor can I >probe them if not. This is just a generic > realtek chipset that uses the 8139too driver. It >always worked fine w/ the older > boot floppies. I have no idea why it doesn't with the new >isntaller. Thanks for > any ideas. Interestingly enough, the onboard nic that has never worked before began working. After booting hdd install, eth0 was the onboard nic not the realtek card. Why the installer used the realtek for installation but didn't set it up as eth0 I dunno. At any rate it worked out for the best - it's nice to have the onboard working. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of cdebconf_0.60_i386.changes
cdebconf_0.60_i386.changes uploaded successfully to localhost along with the files: cdebconf_0.60.dsc cdebconf_0.60.tar.gz libdebconfclient0-dev_0.60_i386.deb libdebconfclient0_0.60_i386.deb cdebconf_0.60_i386.deb cdebconf-udeb_0.60_i386.udeb cdebconf-priority_0.60_i386.udeb libdebconfclient0-udeb_0.60_i386.udeb cdebconf-newt-udeb_0.60_i386.udeb cdebconf-text-udeb_0.60_i386.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#242785: marked as done (termwrap: does not understand devfs terminal devices)
Your message dated Sat, 10 Apr 2004 01:17:03 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#242785: fixed in base-config 2.18 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 Apr 2004 18:37:39 + >From [EMAIL PROTECTED] Thu Apr 08 11:37:39 2004 Return-path: <[EMAIL PROTECTED]> Received: from boy.univ.kiev.ua (mail.univ.kiev.ua) [193.125.78.122] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BBePC-0004bd-00; Thu, 08 Apr 2004 11:37:38 -0700 Received: from intel4.icc.univ.kiev.ua (intel4.icc.univ.kiev.ua [10.25.0.243]) by mail.univ.kiev.ua (8.12.2/8.12.2) with ESMTP id i38IbXZc012645; Thu, 8 Apr 2004 21:37:33 +0300 (EEST) Received: from eugen by intel4.icc.univ.kiev.ua with local (Exim 4.31) id 1BBeOt-0007QB-3V; Thu, 08 Apr 2004 21:37:19 +0300 Content-Type: multipart/mixed; boundary="===0070860492==" MIME-Version: 1.0 From: Eugeniy Meshcheryakov <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: termwrap: does not understand devfs terminal devices X-Mailer: reportbug 2.56 Date: Thu, 08 Apr 2004 21:37:17 +0300 Message-Id: <[EMAIL PROTECTED]> Sender: Eugeniy Meshcheryakov <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: X-CrossAssassin-Scores: 1 This is a multi-part MIME message sent by reportbug. --===0070860492== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Package: base-config Version: 2.17 Severity: minor Tags: patch termwrap does not understand devfs device names. That is not a problem during installation but it may be useful after installation. Attached patch fixes this problem -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.25 Locale: LANG=uk_UA, LC_CTYPE=uk_UA Versions of packages base-config depends on: ii adduser 3.52 Add and remove users and groups ii apt 0.5.24 Advanced front-end for dpkg ii aptitude0.2.14.1-2 curses-based apt frontend ii bsdutils1:2.12-6 Basic utilities from 4.4BSD-Lite ii console-data2002.12.04dbs-35 Keymaps, fonts, charset maps, fall ii console-tools 1:0.2.3dbs-50Linux console and font utilities ii debconf 1.4.21 Debian configuration management sy ii debianutils 2.8.1Miscellaneous utilities specific t ii gettext-base0.14.1-2 GNU Internationalization utilities ii passwd 1:4.0.3-26 Change and administer password and -- debconf information excluded --===0070860492== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="termwrap-devfs.diff" ? termwrap-devfs.diff Index: termwrap === RCS file: /cvsroot/base-config/base-config/termwrap,v retrieving revision 1.32 diff -u -r1.32 termwrap --- termwrap31 Mar 2004 01:21:12 - 1.32 +++ termwrap8 Apr 2004 18:22:02 - @@ -184,10 +184,10 @@ #esac ;; -/dev/tty|/dev/tty[1-9]*) +/dev/tty|/dev/tty[1-9]*|/dev/vc/*) TERMINAL=console ;; -/dev/tty[p-za-e]*) +/dev/tty[p-za-e]*|/dev/pts/*) TERMINAL=pseudo if [ ! -z "$DISPLAY" ]; then TERMINAL=x --===0070860492==-- --- Received: (at 242785-close) by bugs.debian.org; 10 Apr 2004 05:23:16 + >From [EMAIL PROTECTED] Fri Apr 09 22:23:16 2004 Return-path: <[EMAIL PROTECTED]> Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BCAxY-0004fX-00; Fri, 09 Apr 2004 22:23:16 -0700 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1BCArX-0008L9-00; Sat, 10 Apr 2004 01:17:03 -0400 From: Joey Hess <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.47 $ Subje
Bug#242375: marked as done (installation-reports)
Your message dated Sat, 10 Apr 2004 01:17:03 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#242375: fixed in base-config 2.18 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 6 Apr 2004 10:42:05 + >From [EMAIL PROTECTED] Tue Apr 06 03:42:05 2004 Return-path: <[EMAIL PROTECTED]> Received: from mandy.eunet.fi [193.66.1.129] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BAo1t-00056q-00; Tue, 06 Apr 2004 03:42:05 -0700 Received: from tsk.fi (ip212-226-160-73.adsl.kpnqwest.fi [212.226.160.73]) by mandy.eunet.fi (Postfix) with ESMTP id 19DDB1419FC for <[EMAIL PROTECTED]>; Tue, 6 Apr 2004 13:41:38 +0300 (EEST) Message-ID: <[EMAIL PROTECTED]> Date: Tue, 06 Apr 2004 13:34:58 +0300 From: =?ISO-8859-1?Q?Saku_Sepp=E4l=E4?= <[EMAIL PROTECTED]> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: [EMAIL PROTECTED] Subject: installation-reports Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: X-CrossAssassin-Scores: 1 Package: installation-reports Debian-installer-version: beta 3, 5.4.2004=20 http://gluck.debian.org/cdimage/testing/sarge_d-i/i386/beta3/sarge-i386-n= etinst.iso uname -a: Linux debian 2.4.25-1-686 #1 Tue Feb 24 10:55:59 EST 2004 i686=20 GNU/Linux Date: 5.4.2004 13:00 Method: installation from debian installer beta3 cd and apt from=20 ftp.fi.debian.org Machine: Intel 440BX Processor: 600 Mhz Pentium3 Memory: 128Mb Root Device: IDE Root Size/partition table: Disk /dev/hda: 41.1 GB, 41110142976 bytes 255 heads, 63 sectors/track, 4998 cylinders Units =3D cylinders of 16065 * 512 =3D 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 510 4096543+ 7 HPFS/NTFS /dev/hda2 5114998360498605 Extended /dev/hda5 5111020 4096543+ 6 FAT16 /dev/hda6 *10211036 128488+ 83 Linux /dev/hda710371067 248976 83 Linux /dev/hda810681675 4883728+ 83 Linux Output of lspci: 00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge=20 (rev 03) 00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge=20 (rev 03) 00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02) 00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) 00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) 00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02) 00:09.0 Ethernet controller: 3Com Corporation 3c900B-Combo [Etherlink XL=20 Combo] (rev 04) 00:0b.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 06= ) 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP=20 (rev 04) Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [E] [O] =3D OK, [E] =3D Error (please elaborate below), [ ] =3D didn't try it Comments/Problems: My installation problems exist only in the finnish language translation of the installation CD. The US English installation went just fine. First the in the manual partitioning section of the installer "Finish partitioning and write changes to disk" is translated "Keskeyt=E4 osioiden teko (=E4l=E4 tallenna muutoksia)" which means "Interrupt partitioning (don't save changes)" . It should be translated as "Lopeta osioiden muokkaus ja tallenna muutokset". Secondly the configuration of apt does not work. The reason is that the name of the entry in the installation menu is "Tee apt:n asetukset". Because in the menu-mapping file the display text and the corresponding configuration script file are separated with ":", the script file name does not get recognized correctly. solution: change "Tee apt:n asetukset" t
Bug#241117: marked as done (base-config: A patch for termwrap to work with koi8-r)
Your message dated Sat, 10 Apr 2004 01:17:03 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#241117: fixed in base-config 2.18 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; 30 Mar 2004 20:31:00 + >From [EMAIL PROTECTED] Tue Mar 30 12:31:00 2004 Return-path: <[EMAIL PROTECTED]> Received: from mail.dubki.ru [80.240.116.2] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1B8Psy-0003cp-00; Tue, 30 Mar 2004 12:31:00 -0800 Received: by mail.dubki.ru (Postfix, from userid 1708) id AB1E9D3; Wed, 31 Mar 2004 00:30:56 +0400 (MSD) Received: from sercond (sercond.dubki.ru [172.16.4.21]) by mail.dubki.ru (Postfix) with ESMTP id A146DA0; Wed, 31 Mar 2004 00:30:56 +0400 (MSD) Received: from nikita by sercond with local (Exim 3.35 #1 (Debian)) id 1B8PtM-0004Fv-00; Wed, 31 Mar 2004 00:31:24 +0400 Content-Type: multipart/mixed; boundary="===1172247566==" MIME-Version: 1.0 From: "Nikita V. Youshchenko" <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: base-config: A patch for termwrap to work with koi8-r X-Mailer: reportbug 2.48 Date: Wed, 31 Mar 2004 00:31:23 +0400 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=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: This is a multi-part MIME message sent by reportbug. --===1172247566== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Package: base-config Version: 2.17 Severity: normal Tags: patch Attached is a patch for termwrap that enables russian installation in koi8-r encoding. -- System Information: Architecture: i386 (i686) Kernel: Linux 2.4.23 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R --===1172247566== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="termwrap.diff" --- termwrap.orig 2004-03-28 20:14:35.0 +0400 +++ termwrap2004-03-30 18:19:00.0 +0400 @@ -277,7 +277,13 @@ # Russian case $TERMINAL in console) - # What's do we must do? + if [ -x /usr/bin/cyr ]; then + /usr/bin/cyr -s uni -t 16 -e koi8-r --ttys=/dev/tty1 ru_ms ctrl_shift_toggle + else + # Don't try to install in russian withour cyrrilic support on console + LANG=C + LC_ALL=C + fi ;; esac ;; @@ -317,7 +323,7 @@ # Fallback to C case $ENCODING in - ISO-8859-1|ISO-8859-2|ISO-8859-13|ISO-8859-15) + ISO-8859-1|ISO-8859-2|ISO-8859-13|ISO-8859-15|KOI8-R) # Nothing to do ;; *) @@ -330,7 +336,7 @@ $@ case $ENCODING in -ISO-8859-1) +ISO-8859-1|KOI8-R) # Nothing to do, using default config ;; ISO-8859-2) --===1172247566==-- --- Received: (at 241117-close) by bugs.debian.org; 10 Apr 2004 05:23:12 + >From [EMAIL PROTECTED] Fri Apr 09 22:23:12 2004 Return-path: <[EMAIL PROTECTED]> Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BCAxU-0004f8-00; Fri, 09 Apr 2004 22:23:12 -0700 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1BCArX-0008L5-00; Sat, 10 Apr 2004 01:17:03 -0400 From: Joey Hess <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.47 $ Subject: Bug#241117: fixed in base-config 2.18 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Sat, 10 Apr 2004 01:17:03 -0400 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-4.0 required=4.0 tests=BAYES_00,DATING, HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: X-CrossAssassin-Score: 1 Source: base-config Source-Version: 2.18 We believe that the bug you reported is fixed in the latest version
Bug#242787: marked as done (termwrap: [INTL:uk] patch for KOU8-U support in text mode console)
Your message dated Sat, 10 Apr 2004 01:17:03 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#242787: fixed in base-config 2.18 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 Apr 2004 18:39:50 + >From [EMAIL PROTECTED] Thu Apr 08 11:39:50 2004 Return-path: <[EMAIL PROTECTED]> Received: from boy.univ.kiev.ua (mail.univ.kiev.ua) [193.125.78.122] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BBeRJ-0004o7-00; Thu, 08 Apr 2004 11:39:49 -0700 Received: from intel4.icc.univ.kiev.ua (intel4.icc.univ.kiev.ua [10.25.0.243]) by mail.univ.kiev.ua (8.12.2/8.12.2) with ESMTP id i38IdkZc013014; Thu, 8 Apr 2004 21:39:46 +0300 (EEST) Received: from eugen by intel4.icc.univ.kiev.ua with local (Exim 4.31) id 1BBeR2-0007Qg-Aj; Thu, 08 Apr 2004 21:39:32 +0300 Content-Type: multipart/mixed; boundary="===1207105522==" MIME-Version: 1.0 From: Eugeniy Meshcheryakov <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: termwrap: [INTL:uk] patch for KOU8-U support in text mode console X-Mailer: reportbug 2.56 Date: Thu, 08 Apr 2004 21:39:32 +0300 Message-Id: <[EMAIL PROTECTED]> Sender: Eugeniy Meshcheryakov <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: X-CrossAssassin-Scores: 1 This is a multi-part MIME message sent by reportbug. --===1207105522== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Package: base-config Version: 2.17 Severity: wishlist Tags: patch l10n Attached patch adds support for KOI8-U to termwrap. There is no need to use fbterm for koi8-u. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.25 Locale: LANG=uk_UA, LC_CTYPE=uk_UA Versions of packages base-config depends on: ii adduser 3.52 Add and remove users and groups ii apt 0.5.24 Advanced front-end for dpkg ii aptitude0.2.14.1-2 curses-based apt frontend ii bsdutils1:2.12-6 Basic utilities from 4.4BSD-Lite ii console-data2002.12.04dbs-35 Keymaps, fonts, charset maps, fall ii console-tools 1:0.2.3dbs-50Linux console and font utilities ii debconf 1.4.21 Debian configuration management sy ii debianutils 2.8.1Miscellaneous utilities specific t ii gettext-base0.14.1-2 GNU Internationalization utilities ii passwd 1:4.0.3-26 Change and administer password and -- debconf information excluded --===1207105522== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="termwrap-koi8u.diff" ? termwrap-devfs.diff ? termwrap-koi8u.diff Index: termwrap === RCS file: /cvsroot/base-config/base-config/termwrap,v retrieving revision 1.32 diff -u -r1.32 termwrap --- termwrap31 Mar 2004 01:21:12 - 1.32 +++ termwrap8 Apr 2004 18:32:44 - @@ -253,6 +253,10 @@ # Load ISO-8859-15 charset mapping into console try_load_charset "$ENCODING" iso15 lat0-sun16 ;; +KOI8-U) + # Load KOU8-U charset mapping into console + try_load_charset "$ENCODING" koi8u koi8u_8x16 + ;; eucJP|EUC-JP) # Japanese case $TERMINAL in @@ -323,7 +327,7 @@ # Fallback to C case $ENCODING in - ISO-8859-1|ISO-8859-2|ISO-8859-13|ISO-8859-15|KOI8-R) + ISO-8859-1|ISO-8859-2|ISO-8859-13|ISO-8859-15|KOI8-R|KOI8-U) # Nothing to do ;; *) @@ -336,7 +340,7 @@ $@ case $ENCODING in -ISO-8859-1|KOI8-R) +ISO-8859-1|KOI8-R|KOI8-U) # Nothing to do, using default config ;; ISO-8859-2) --===1207105522==-- --- Received: (at 242787-close) by bugs.debian.org; 10 Apr 2004 05:23:11 + >From [EMAIL PROTECTED] Fri Apr 09 22:23:11 20
baseconfig-udeb_0.032_i386.changes ACCEPTED
Accepted: baseconfig-udeb_0.032.dsc to pool/main/b/baseconfig-udeb/baseconfig-udeb_0.032.dsc baseconfig-udeb_0.032.tar.gz to pool/main/b/baseconfig-udeb/baseconfig-udeb_0.032.tar.gz baseconfig-udeb_0.032_all.udeb to pool/main/b/baseconfig-udeb/baseconfig-udeb_0.032_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
On Fri, 2004-04-09 at 14:28, Rick Thomas wrote: > Malte Cornils wrote: > > > > but I would appreciate it if someone > > could test the current images (Holger?) on similar hardware. > > > I'll test the latest daily-build boot floppies this weekend on both of > my test machines and send you a report. Sven and/or Colin: For this purpose, please tell me the location of the latest/greatest boot-floppy images. Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of baseconfig-udeb_0.032_i386.changes
baseconfig-udeb_0.032_i386.changes uploaded successfully to localhost along with the files: baseconfig-udeb_0.032.dsc baseconfig-udeb_0.032.tar.gz baseconfig-udeb_0.032_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
debian-installer-utils_0.52_i386.changes ACCEPTED
Accepted: debian-installer-utils_0.52.dsc to pool/main/d/debian-installer-utils/debian-installer-utils_0.52.dsc debian-installer-utils_0.52.tar.gz to pool/main/d/debian-installer-utils/debian-installer-utils_0.52.tar.gz di-utils-bootfloppy_0.52_i386.udeb to pool/main/d/debian-installer-utils/di-utils-bootfloppy_0.52_i386.udeb di-utils-exit-installer_0.52_all.udeb to pool/main/d/debian-installer-utils/di-utils-exit-installer_0.52_all.udeb di-utils-mapdevfs_0.52_i386.udeb to pool/main/d/debian-installer-utils/di-utils-mapdevfs_0.52_i386.udeb di-utils-reboot_0.52_all.udeb to pool/main/d/debian-installer-utils/di-utils-reboot_0.52_all.udeb di-utils-shell_0.52_i386.udeb to pool/main/d/debian-installer-utils/di-utils-shell_0.52_i386.udeb di-utils-terminfo_0.52_all.udeb to pool/main/d/debian-installer-utils/di-utils-terminfo_0.52_all.udeb di-utils_0.52_all.udeb to pool/main/d/debian-installer-utils/di-utils_0.52_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
bugreporter-udeb_0.22_i386.changes ACCEPTED
Accepted: bugreporter-udeb_0.22.dsc to pool/main/b/bugreporter-udeb/bugreporter-udeb_0.22.dsc bugreporter-udeb_0.22.tar.gz to pool/main/b/bugreporter-udeb/bugreporter-udeb_0.22.tar.gz bugreporter-udeb_0.22_all.udeb to pool/main/b/bugreporter-udeb/bugreporter-udeb_0.22_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
net-retriever_0.31_i386.changes ACCEPTED
Accepted: download-installer_0.31_all.udeb to pool/main/n/net-retriever/download-installer_0.31_all.udeb net-retriever_0.31.dsc to pool/main/n/net-retriever/net-retriever_0.31.dsc net-retriever_0.31.tar.gz to pool/main/n/net-retriever/net-retriever_0.31.tar.gz net-retriever_0.31_all.udeb to pool/main/n/net-retriever/net-retriever_0.31_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
nobootloader_0.0.13_i386.changes ACCEPTED
Accepted: nobootloader_0.0.13.dsc to pool/main/n/nobootloader/nobootloader_0.0.13.dsc nobootloader_0.0.13.tar.gz to pool/main/n/nobootloader/nobootloader_0.0.13.tar.gz nobootloader_0.0.13_all.udeb to pool/main/n/nobootloader/nobootloader_0.0.13_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
anna_0.056_i386.changes ACCEPTED
Accepted: anna_0.056.dsc to pool/main/a/anna/anna_0.056.dsc anna_0.056.tar.gz to pool/main/a/anna/anna_0.056.tar.gz anna_0.056_i386.udeb to pool/main/a/anna/anna_0.056_i386.udeb load-installer_0.056_all.udeb to pool/main/a/anna/load-installer_0.056_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
base-config_2.18_i386.changes ACCEPTED
Accepted: base-config_2.18.dsc to pool/main/b/base-config/base-config_2.18.dsc base-config_2.18.tar.gz to pool/main/b/base-config/base-config_2.18.tar.gz base-config_2.18_all.deb to pool/main/b/base-config/base-config_2.18_all.deb Announcing to [EMAIL PROTECTED] Closing bugs: 241117 242375 242785 242787 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cdrom-detect_0.54_i386.changes ACCEPTED
Accepted: cdrom-detect_0.54.dsc to pool/main/c/cdrom-detect/cdrom-detect_0.54.dsc cdrom-detect_0.54.tar.gz to pool/main/c/cdrom-detect/cdrom-detect_0.54.tar.gz cdrom-detect_0.54_all.udeb to pool/main/c/cdrom-detect/cdrom-detect_0.54_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cdrom-retriever_0.24_i386.changes ACCEPTED
Accepted: cdrom-retriever_0.24.dsc to pool/main/c/cdrom-retriever/cdrom-retriever_0.24.dsc cdrom-retriever_0.24.tar.gz to pool/main/c/cdrom-retriever/cdrom-retriever_0.24.tar.gz cdrom-retriever_0.24_all.udeb to pool/main/c/cdrom-retriever/cdrom-retriever_0.24_all.udeb load-cdrom_0.24_all.udeb to pool/main/c/cdrom-retriever/load-cdrom_0.24_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
choose-mirror_0.041_i386.changes ACCEPTED
Accepted: choose-mirror_0.041.dsc to pool/main/c/choose-mirror/choose-mirror_0.041.dsc choose-mirror_0.041.tar.gz to pool/main/c/choose-mirror/choose-mirror_0.041.tar.gz choose-mirror_0.041_i386.udeb to pool/main/c/choose-mirror/choose-mirror_0.041_i386.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
iso-scan_0.24_i386.changes ACCEPTED
Accepted: iso-scan_0.24.dsc to pool/main/i/iso-scan/iso-scan_0.24.dsc iso-scan_0.24.tar.gz to pool/main/i/iso-scan/iso-scan_0.24.tar.gz iso-scan_0.24_all.udeb to pool/main/i/iso-scan/iso-scan_0.24_all.udeb load-iso_0.24_all.udeb to pool/main/i/iso-scan/load-iso_0.24_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
floppy-retriever_0.26_i386.changes ACCEPTED
Accepted: floppy-retriever_0.26.dsc to pool/main/f/floppy-retriever/floppy-retriever_0.26.dsc floppy-retriever_0.26.tar.gz to pool/main/f/floppy-retriever/floppy-retriever_0.26.tar.gz floppy-retriever_0.26_all.udeb to pool/main/f/floppy-retriever/floppy-retriever_0.26_all.udeb load-floppy_0.26_all.udeb to pool/main/f/floppy-retriever/load-floppy_0.26_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of anna_0.056_i386.changes
anna_0.056_i386.changes uploaded successfully to localhost along with the files: anna_0.056.dsc anna_0.056.tar.gz load-installer_0.056_all.udeb anna_0.056_i386.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of choose-mirror_0.041_i386.changes
choose-mirror_0.041_i386.changes uploaded successfully to localhost along with the files: choose-mirror_0.041.dsc choose-mirror_0.041.tar.gz choose-mirror_0.041_i386.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of debian-installer-utils_0.52_i386.changes
debian-installer-utils_0.52_i386.changes uploaded successfully to localhost along with the files: debian-installer-utils_0.52.dsc debian-installer-utils_0.52.tar.gz di-utils-reboot_0.52_all.udeb di-utils-exit-installer_0.52_all.udeb di-utils_0.52_all.udeb di-utils-terminfo_0.52_all.udeb di-utils-shell_0.52_i386.udeb di-utils-mapdevfs_0.52_i386.udeb di-utils-bootfloppy_0.52_i386.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of cdrom-retriever_0.24_i386.changes
cdrom-retriever_0.24_i386.changes uploaded successfully to localhost along with the files: cdrom-retriever_0.24.dsc cdrom-retriever_0.24.tar.gz cdrom-retriever_0.24_all.udeb load-cdrom_0.24_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of net-retriever_0.31_i386.changes
net-retriever_0.31_i386.changes uploaded successfully to localhost along with the files: net-retriever_0.31.dsc net-retriever_0.31.tar.gz net-retriever_0.31_all.udeb download-installer_0.31_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cdrom-checker_0.26_i386.changes ACCEPTED
Accepted: cdrom-checker_0.26.dsc to pool/main/c/cdrom-checker/cdrom-checker_0.26.dsc cdrom-checker_0.26.tar.gz to pool/main/c/cdrom-checker/cdrom-checker_0.26.tar.gz cdrom-checker_0.26_i386.udeb to pool/main/c/cdrom-checker/cdrom-checker_0.26_i386.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#242986: installation-reports: xserver does not start for sis 745gx video chipset
Package: installation-reports Version: beta 3 Severity: normal Debian-installer-version: 30 March 2004 http://gluck.debian.org/cdimage/testing/sarge_d-i/i386/beta3/sarge-i386-netinst.iso uname -a: Linux ada 2.4.25-1-k7 #1 Tue Feb 24 14:24:28 EST 2004 i686 GNU/Linux (But I have upgraded to the k7 kernel image after installation, initially it was just i386.) Date: 30 March 2004 22:00 Method: Booted from burnt CD. Machine: White box PC Chips M863G mainboard Processor: Athlon XP 2400+ Memory: 512 MB Root Device: IDE Western Digital 80 GB Root Size/partition table: Before: Single partition + swap potato debian. After: Single root partition + swap. Disk /dev/hda: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1948376172166 83 Linux /dev/hda294849729 1975995f W95 Ext'd (LBA) /dev/hda594849729 1975963+ 82 Linux swap (I'm not sure how /dev/hda2 ended up in there.) Output of lspci: $ lspci 00:00.0 Host bridge: Silicon Integrated Systems [SiS]: Unknown device 0741 (rev 03) 00:01.0 PCI bridge: Silicon Integrated Systems [SiS]: Unknown device 0003 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 (rev 25) 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound Controller (rev a0) 00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller 00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet (rev 90) 01:00.0 VGA compatible controller: nVidia Corporation NV10DDR [GeForce 256 DDR] (rev 10) $ cat /proc/pci PCI devices found: Bus 0, device 0, function 0: Host bridge: PCI device 1039:0741 (Silicon Integrated Systems [SiS]) (rev 3). Master Capable. Latency=32. Non-prefetchable 32 bit memory at 0xd000 [0xd3ff]. Bus 0, device 1, function 0: PCI bridge: PCI device 1039:0003 (Silicon Integrated Systems [SiS]) (rev 0). Master Capable. Latency=64. Min Gnt=10. Bus 0, device 2, function 0: ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 (rev 37). Bus 0, device 2, function 5: IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 0). Master Capable. Latency=128. I/O at 0xffa0 [0xffaf]. Bus 0, device 2, function 7: Multimedia audio controller: Silicon Integrated Systems [SiS] Sound Controller (rev 160). IRQ 10. Master Capable. Latency=64. Min Gnt=52.Max Lat=11. I/O at 0xe800 [0xe8ff]. I/O at 0xec00 [0xec7f]. Bus 0, device 3, function 1: USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (#2) (rev 15). IRQ 3. Master Capable. Latency=64. Max Lat=80. Non-prefetchable 32 bit memory at 0xcfffe000 [0xcfffefff]. Bus 0, device 3, function 0: USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 15). IRQ 7. Master Capable. Latency=64. Max Lat=80. Non-prefetchable 32 bit memory at 0xcfffd000 [0xcfffdfff]. Bus 0, device 3, function 3: USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller (rev 0). IRQ 5. Master Capable. Latency=64. Max Lat=80. Non-prefetchable 32 bit memory at 0xc000 [0xcfff]. Bus 0, device 4, function 0: Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet (rev 144). IRQ 10. Master Capable. Latency=64. Min Gnt=52.Max Lat=11. I/O at 0xe400 [0xe4ff]. Non-prefetchable 32 bit memory at 0xcfffc000 [0xcfffcfff]. Bus 1, device 0, function 0: VGA compatible controller: nVidia Corporation NV10DDR [GeForce 256 DDR] (rev 16). IRQ 11. Master Capable. Latency=248. Min Gnt=5.Max Lat=1. Non-prefetchable 32 bit memory at 0xce00 [0xceff]. Prefetchable 32 bit memory at 0xc000 [0xc7ff]. $ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 8 model name : AMD Athlon(tm) XP 2400+ stepping: 1 cpu MHz : 2000.090 cache size : 256 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow bogomips: 3984.58 Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules
Bug#241516: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
Colin, On Fri, 2004-04-09 at 18:06, Colin Watson wrote: > On Fri, Apr 09, 2004 at 02:40:37PM -0400, Rick Thomas wrote: > > it always tries to install yaboot (even though archdetect says it's an > > oldworld machine. I think something's broken in the yaboot installer) > > I've filed a bug report. > > Hang on, are you saying that it always tries to install *yaboot*, not > *yaboot-installer*? I thought you meant the latter. In that case, yes, > debootstrap always installs yaboot on powerpc. yaboot-installer needs to > be fixed to apt-install it before beta4 (so that we don't break beta4 > testing), then debootstrap can stop installing it. > > -- > Colin Watson [EMAIL PROTECTED] > I apologize in advance for my ignorance. I don't know the difference between "install yaboot" and "yaboot-installer". I just try it and report what I think I see. My lack of knowledge of the detailed internals seems to have caused some confusion. This weekend, I have already promised to try out the latest boot floppy images. I will keep a detailed log of everything that happens and post it here. I sincerely hope this will help you figure out what needs to be done. Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of floppy-retriever_0.26_i386.changes
floppy-retriever_0.26_i386.changes uploaded successfully to localhost along with the files: floppy-retriever_0.26.dsc floppy-retriever_0.26.tar.gz floppy-retriever_0.26_all.udeb load-floppy_0.26_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of nobootloader_0.0.13_i386.changes
nobootloader_0.0.13_i386.changes uploaded successfully to localhost along with the files: nobootloader_0.0.13.dsc nobootloader_0.0.13.tar.gz nobootloader_0.0.13_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of cdrom-detect_0.54_i386.changes
cdrom-detect_0.54_i386.changes uploaded successfully to localhost along with the files: cdrom-detect_0.54.dsc cdrom-detect_0.54.tar.gz cdrom-detect_0.54_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of bugreporter-udeb_0.22_i386.changes
bugreporter-udeb_0.22_i386.changes uploaded successfully to localhost along with the files: bugreporter-udeb_0.22.dsc bugreporter-udeb_0.22.tar.gz bugreporter-udeb_0.22_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of iso-scan_0.24_i386.changes
iso-scan_0.24_i386.changes uploaded successfully to localhost along with the files: iso-scan_0.24.dsc iso-scan_0.24.tar.gz iso-scan_0.24_all.udeb load-iso_0.24_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of base-config_2.18_i386.changes
base-config_2.18_i386.changes uploaded successfully to localhost along with the files: base-config_2.18.dsc base-config_2.18.tar.gz base-config_2.18_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of cdrom-checker_0.26_i386.changes
cdrom-checker_0.26_i386.changes uploaded successfully to localhost along with the files: cdrom-checker_0.26.dsc cdrom-checker_0.26.tar.gz cdrom-checker_0.26_i386.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#242982: marked as done (successful debian linux and hurd simulantaneous install)
Your message dated Sat, 10 Apr 2004 00:29:37 -0400 with message-id <[EMAIL PROTECTED]> and subject line closing successful installation report 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; 10 Apr 2004 04:08:02 + >From [EMAIL PROTECTED] Fri Apr 09 21:08:02 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 1BC9mk-0002km-00; Fri, 09 Apr 2004 21:08:02 -0700 Received: from dragon.kitenet.net (216-98-95-212.access.naxs.com [216.98.95.212]) (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 B737117DF4 for <[EMAIL PROTECTED]>; Sat, 10 Apr 2004 04:07:09 + (GMT) Received: by dragon.kitenet.net (Postfix, from userid 1000) id BC4656E12D; Sat, 10 Apr 2004 00:06:46 -0400 (EDT) Date: Sat, 10 Apr 2004 00:06:46 -0400 From: Joey Hess <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: successful debian linux and hurd simulantaneous install Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline X-Reportbug-Version: 2.54 User-Agent: Mutt/1.5.5.1+cvs20040105i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: X-CrossAssassin-Scores: 1 --J/dobhs11T7y2rNN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Package: installation-reports Severity: normal INSTALL REPORT Debian-installer-version: handbuilt from svn Method: from 128 mb usb keychain for linux plus another 256 mb keychain for hurd, with a hurd bochs disk image on it Machine: linuxcertified test laptop, described in past reports Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect Keychain:[O] Load installer modules: [O] Detect hard drives: [O] Manually mount second keychain: [O] Cat hurd disk image to disk:[O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: The blinkenlights on the pair of keychains was very pretty as one of them copied the hurd image to disk, and debs were installed from the other. The hurd zcat beat the debootstrap. Grub told me: The following other operating systems have been detected on this computer: GNU/Hurd, Debian GNU/Linux (testing/unstable) The other Debian install was a laftover from past installs. It wanted to put grub in the MBR, and I answered yes. 8 minutes after booting d-i, I was at a grub menu. It offered to let me boot debian or the hurd. Both worked fine. --=20 see shy jo --J/dobhs11T7y2rNN Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAd3LVd8HHehbQuO8RAi2qAJsE31hFIVhwZ0uHATJQMImPf3u6oQCdF4nb RIK5hjxo6caDG0uA0ml1OP8= =fs4A -END PGP SIGNATURE- --J/dobhs11T7y2rNN-- --- Received: (at 242982-done) by bugs.debian.org; 10 Apr 2004 04:29:59 + >From [EMAIL PROTECTED] Fri Apr 09 21:29:59 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 1BCA7z-0004wP-00; Fri, 09 Apr 2004 21:29:59 -0700 Received: from dragon.kitenet.net (216-98-95-212.access.naxs.com [216.98.95.212]) (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 9CAB0181F5 for <[EMAIL PROTECTED]>; Sat, 10 Apr 2004 04:29:58 + (GMT) Received: by dragon.kitenet.net (Postfix, from userid 1000) id 9B0666E12D;
Bug#242976: Automated Reply from Testyann
Desole -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#242983: keyboard list untranslated
Package: kbd-chooser Severity: normal Tags: d-i The list of keyboard types for pc/at has just two letter country codes, not names any more. Lack of full translation? -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.4.25 Locale: LANG=en_US, LC_CTYPE=en_US -- see shy jo signature.asc Description: Digital signature
Bug#242982: successful debian linux and hurd simulantaneous install
Package: installation-reports Severity: normal INSTALL REPORT Debian-installer-version: handbuilt from svn Method: from 128 mb usb keychain for linux plus another 256 mb keychain for hurd, with a hurd bochs disk image on it Machine: linuxcertified test laptop, described in past reports Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect Keychain:[O] Load installer modules: [O] Detect hard drives: [O] Manually mount second keychain: [O] Cat hurd disk image to disk:[O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: The blinkenlights on the pair of keychains was very pretty as one of them copied the hurd image to disk, and debs were installed from the other. The hurd zcat beat the debootstrap. Grub told me: The following other operating systems have been detected on this computer: GNU/Hurd, Debian GNU/Linux (testing/unstable) The other Debian install was a laftover from past installs. It wanted to put grub in the MBR, and I answered yes. 8 minutes after booting d-i, I was at a grub menu. It offered to let me boot debian or the hurd. Both worked fine. -- see shy jo signature.asc Description: Digital signature
os-prober_0.04_i386.changes ACCEPTED
Accepted: os-prober_0.04.dsc to pool/main/o/os-prober/os-prober_0.04.dsc os-prober_0.04.tar.gz to pool/main/o/os-prober/os-prober_0.04.tar.gz os-prober_0.04_i386.udeb to pool/main/o/os-prober/os-prober_0.04_i386.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of os-prober_0.04_i386.changes
os-prober_0.04_i386.changes uploaded successfully to localhost along with the files: os-prober_0.04.dsc os-prober_0.04.tar.gz os-prober_0.04_i386.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#242976: forgets to display screen for question on backup (very strange)
Package: cdebconf Severity: normal Tags: d-i Version: 0.59 I found a very strange problem. The script below should reproduce it, at least run in d-i from the shell in console #2 after grub-installer is loaded. At the first question shown, hit the back button. It seems to hang, and set -x reveals that it's at 'read -r _LINE' inside the confmodule. Now, if I type "hi mom", and enter (nothing is displayed on screen as I do this), it will stop blocking and continue. The last line, which gets the value of the question, includes my "hi mom" in the value. So it's like the dialog box is just not being displayed, but cdebconf is still waiting for me to type input in it and hit enter. I've even used line editing commands, blind, and all happens as I'd expect. #!/bin/sh . /usr/share/debconf/confmodule set -x db_capb backup db_progress START 0 6 grub-installer/progress/title db_progress INFO grub-installer/progress/step_install db_input high grub-installer/apt-installer-failed db_go db_input critical grub-installer/bootdev db_go db_get grub-installer/bootdev The above is nearly the minimal testcase to reproduce this. The set -x, the INFO line and the final db_get can be removed and it will still happen. The progress bar must have been brought up, or the bug will not occur. -- see shy jo signature.asc Description: Digital signature
Re: Who do you have to sleep with / bribe / shoot to get an answer about RAID support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 10 April 2004 03:04, Thiemo Seufer wrote: [snap] > Why don't you just join the d-i team and add the RAID stuff to the > svn repository? I would love to. Who should I contact? I would have kept it a bit more quiet until I had more working. But the interrest for it seems greater than I had thought. - -- Paul Fleischer // ProGuy PGP key fingerprint: 755A 9FB3 F7E4 DB62 8154 C5D6 381B BBCD 7BE1 FF30 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAd062OBu7zXvh/zARAptjAJ9LZt3/Dw5FMsCaICgb7mbeJyfi8QCdH5MQ orrhlInpga21OuIOyByugNo= =aam9 -END PGP SIGNATURE-
No network after install w/ realtek/8139too
This box is a small form factor Compaq deskpro w/ intel bx440 chipset 1-2.3G & 1-3.2G hdd's 400Mhz, 128M. I've ran the installer 3 times. The first 2 in expert the 3rd standard and it is the same each time. No network on reboot. This seems to be the culprit: starting hotplug failed can't synthesize pci hotplug events It also fails w/ usb hotplugging but I only see this on boot. dmesg doesn't mention it. I typed this relevent part of dmesg by hand so hopefully not any major errors. PCI: Sharing IRQ 9 with 00:0a.0 usb-uhci.c: USB UHCI at I/O 0x2020, IRQ 9 usb-uhci.c: Detected 2 ports usb.c new USB bus registered, assigned bus number 1 usb.c 2 ports detected /snip/ PCI: Enabling device 00:0a.0 (0004 -> 0007) PCI: Found IRQ 9 for device 00:0a.0 PCI: Sharing IRQ 9 with 00:14.2 eth0: OEM i82557/i82558 10/100 Ethernet, 00:08:C7:77:54:93, IRQ 9. Receiver lock-up bug exists -- enabling work-around Board assembly 307295-101, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1 General self-test: passed Serial sub-system self-test: passed Internal registers self-test: passed ROM checksum self-test: passed (0x24c9f043) Receiver lock-up workaround activated 8139too Fast Ethernet driver 0.9.26 PCI: Found IRQ 11 for device 00:0d.0 eth1: RealTek RTL8139 at 0xc488, 00:02:2a:c4:6c:36, IRQ 11 eth1: Identified 8139 chip type 'RTL-8100B/8139d' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Who do you have to sleep with / bribe / shoot to get an answer about RAID support
Paul Fleischer wrote: [snip] > However, it takes quite some time to make the support stable enough to be > included in anything. And currently time is something I don't have too much > of :-) > That said, I hope to be able to supply an up-to-date and a better working > image within too long (I won't give any timeframe, and don't hold your > breath, real life needs attention too). > Of course development will go faster if other people join in (especially > people with knowledge of the d-i). Why don't you just join the d-i team and add the RAID stuff to the svn repository? Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
partman-newworld_1_powerpc.changes ACCEPTED
Accepted: partman-newworld_1.dsc to pool/main/p/partman-newworld/partman-newworld_1.dsc partman-newworld_1.tar.gz to pool/main/p/partman-newworld/partman-newworld_1.tar.gz partman-newworld_1_powerpc.udeb to pool/main/p/partman-newworld/partman-newworld_1_powerpc.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
partman-newworld_2_powerpc.changes ACCEPTED
Accepted: partman-newworld_2.dsc to pool/main/p/partman-newworld/partman-newworld_2.dsc partman-newworld_2.tar.gz to pool/main/p/partman-newworld/partman-newworld_2.tar.gz partman-newworld_2_powerpc.udeb to pool/main/p/partman-newworld/partman-newworld_2_powerpc.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 242958 to debian-cd
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.7.95.1 > reassign 242958 debian-cd Bug#242958: cdrom-checker: several problems / md5sum for README.html incorrect Bug reassigned from package `debian-installer' to `debian-cd'. > 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]
Re: Who do you have to sleep with / bribe / shoot to get an answer about RAID support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanx man! I'll download it and take a look, let you know how it goes! Mark Demma iWin, Inc. Senior Network and Systems Administrator http://www.iwin.com/ http://www.playsite.com On 9 Apr 2004, at 17:54, Paul Fleischer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 10 April 2004 01:29, Mark Demma wrote: Sorry to be a pest, but will SOMEONE PLEASE give status / make bloody sure that software RAID support is FINALLY in Debian ... what 3 years after all the other distro's have it? You know its lovely that so much work is going into "old world mac" floppies, making sure you can install Debian off the tape drive on that Sinclair you dusted off from the attic, etc etc, but for those of us trying to use Debian on, gasp, brand new machines with, gasp brand new SCSI controllers and gasp, raid controllers and software RAID to support thousands of people, you can set your hair on fire and no one will say boo. Please, for gods sake, everything is there! I'll help test, I have over 50 machines running Debian with software RAID! Hi there, I have been working a bit on making software RAID work in the Debian-installer, and have had partly success with it. My work can be found here: http://www.daimi.au.dk/~pg/debian/netinst-raid1.iso But I have to warn you, people have had different levels of sucess with it. However, it takes quite some time to make the support stable enough to be included in anything. And currently time is something I don't have too much of :-) That said, I hope to be able to supply an up-to-date and a better working image within too long (I won't give any timeframe, and don't hold your breath, real life needs attention too). Of course development will go faster if other people join in (especially people with knowledge of the d-i). Cheers, - -- Paul Fleischer // ProGuy PGP key fingerprint: 755A 9FB3 F7E4 DB62 8154 C5D6 381B BBCD 7BE1 FF30 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAd0XgOBu7zXvh/zARAsDVAJ4z7HEh9a/NQh6atY6w4JniMFOkqACZASZ8 u8a5OERxyjyIaVfSc1z0nlY= =CUUG -END PGP SIGNATURE- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iD8DBQFAd0ebTw/rh8k29J8RAnZOAJ9yiZLfYeXsY/Sg7bPEJNudsoRKbwCeJ/c6 eU+uq7reyGRWDldyoyPlpqc= =SSun -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
No network after install w/ realtek/8139too
Using the boot/root floppies I am able to configure the network and install Debian from the net and everything seems to work fine. On reboot however I have no network. dmesg says the card is detected but I have no tools available to see if the modules are lodeded nor can I probe them if not. This is just a generic realtek chipset that uses the 8139too driver. It always worked fine w/ the older boot floppies. I have no idea why it doesn't with the new isntaller. Thanks for any ideas. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Who do you have to sleep with / bribe / shoot to get an answer about RAID support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 10 April 2004 01:29, Mark Demma wrote: > Sorry to be a pest, but will SOMEONE PLEASE give status / make bloody > sure that software RAID support is FINALLY in Debian ... what 3 years > after all the other distro's have it? You know its lovely that so much > work is going into "old world mac" floppies, making sure you can > install Debian off the tape drive on that Sinclair you dusted off from > the attic, etc etc, but for those of us trying to use Debian on, gasp, > brand new machines with, gasp brand new SCSI controllers and gasp, raid > controllers and software RAID to support thousands of people, you can > set your hair on fire and no one will say boo. Please, for gods sake, > everything is there! I'll help test, I have over 50 machines running > Debian with software RAID! Hi there, I have been working a bit on making software RAID work in the Debian-installer, and have had partly success with it. My work can be found here: http://www.daimi.au.dk/~pg/debian/netinst-raid1.iso But I have to warn you, people have had different levels of sucess with it. However, it takes quite some time to make the support stable enough to be included in anything. And currently time is something I don't have too much of :-) That said, I hope to be able to supply an up-to-date and a better working image within too long (I won't give any timeframe, and don't hold your breath, real life needs attention too). Of course development will go faster if other people join in (especially people with knowledge of the d-i). Cheers, - -- Paul Fleischer // ProGuy PGP key fingerprint: 755A 9FB3 F7E4 DB62 8154 C5D6 381B BBCD 7BE1 FF30 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAd0XgOBu7zXvh/zARAsDVAJ4z7HEh9a/NQh6atY6w4JniMFOkqACZASZ8 u8a5OERxyjyIaVfSc1z0nlY= =CUUG -END PGP SIGNATURE-
linux-kernel-di-alpha_0.57_source+alpha.changes ACCEPTED
Accepted: brltty-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/brltty-modules-2.4.25-1-generic-di_0.57_alpha.udeb cdrom-core-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/cdrom-core-modules-2.4.25-1-generic-di_0.57_alpha.udeb cdrom-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/cdrom-modules-2.4.25-1-generic-di_0.57_alpha.udeb ext3-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/ext3-modules-2.4.25-1-generic-di_0.57_alpha.udeb fat-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/fat-modules-2.4.25-1-generic-di_0.57_alpha.udeb fb-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/fb-modules-2.4.25-1-generic-di_0.57_alpha.udeb ide-core-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/ide-core-modules-2.4.25-1-generic-di_0.57_alpha.udeb ide-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/ide-modules-2.4.25-1-generic-di_0.57_alpha.udeb ipv6-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/ipv6-modules-2.4.25-1-generic-di_0.57_alpha.udeb isa-pnp-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/isa-pnp-modules-2.4.25-1-generic-di_0.57_alpha.udeb jfs-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/jfs-modules-2.4.25-1-generic-di_0.57_alpha.udeb kernel-image-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/kernel-image-2.4.25-1-generic-di_0.57_alpha.udeb linux-kernel-di-alpha_0.57.dsc to pool/main/l/linux-kernel-di-alpha/linux-kernel-di-alpha_0.57.dsc linux-kernel-di-alpha_0.57.tar.gz to pool/main/l/linux-kernel-di-alpha/linux-kernel-di-alpha_0.57.tar.gz md-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/md-modules-2.4.25-1-generic-di_0.57_alpha.udeb nic-extra-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/nic-extra-modules-2.4.25-1-generic-di_0.57_alpha.udeb nic-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/nic-modules-2.4.25-1-generic-di_0.57_alpha.udeb nic-shared-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/nic-shared-modules-2.4.25-1-generic-di_0.57_alpha.udeb parport-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/parport-modules-2.4.25-1-generic-di_0.57_alpha.udeb plip-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/plip-modules-2.4.25-1-generic-di_0.57_alpha.udeb ppp-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/ppp-modules-2.4.25-1-generic-di_0.57_alpha.udeb reiserfs-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/reiserfs-modules-2.4.25-1-generic-di_0.57_alpha.udeb scsi-common-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/scsi-common-modules-2.4.25-1-generic-di_0.57_alpha.udeb scsi-core-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/scsi-core-modules-2.4.25-1-generic-di_0.57_alpha.udeb scsi-extra-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/scsi-extra-modules-2.4.25-1-generic-di_0.57_alpha.udeb scsi-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/scsi-modules-2.4.25-1-generic-di_0.57_alpha.udeb serial-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/serial-modules-2.4.25-1-generic-di_0.57_alpha.udeb socket-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/socket-modules-2.4.25-1-generic-di_0.57_alpha.udeb srm-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/srm-modules-2.4.25-1-generic-di_0.57_alpha.udeb usb-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/usb-modules-2.4.25-1-generic-di_0.57_alpha.udeb usb-storage-modules-2.4.25-1-generic-di_0.57_alpha.udeb to pool/main/l/linux-kernel-di-alpha/usb-storage-modules-2.4.25-1-generic-di_0.57_alpha.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Who do you have to sleep with / bribe / shoot to get an answer about RAID support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OK its good to finally hear from someone, even if it is bad news. Unfortunately I have neither the money more programming skills to make this happen on my own. Its a shame that something this important is being left out and ignored. It is maddening that releases get held up forever to get things working on those Amigas, old world macs and other machines that should be in a museum or junk pile, while important critical features for a modern installer get ignored. For Debian to be taken seriously, not just something hobbyists play with, some one needs to pay attention to stuff like this. Mark Demma iWin, Inc. Senior Network and Systems Administrator http://www.iwin.com/ http://www.playsite.com On 9 Apr 2004, at 17:36, Joey Hess wrote: Mark Demma wrote: Sorry to be a pest, but will SOMEONE PLEASE give status / make bloody sure that software RAID support is FINALLY in Debian ... what 3 years after all the other distro's have it? I don't know of anyone working on software raid support in d-i right now. It would be nice, I agree. The only way you can ensure that it happens, though, is to do it yourself, or hire someone to do it. Otherwise, you're at the mercy of someone else deciding/finding the time to do it. work is going into "old world mac" floppies, making sure you can install Debian off the tape drive on that Sinclair you dusted off from the attic, etc etc, but for those of us trying to use Debian on, gasp, brand new machines with, gasp brand new SCSI controllers and gasp, raid controllers This is a matter of people working on what they feel they should work on. d-i will support hardware RAID. -- see shy jo -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iD8DBQFAd0U7Tw/rh8k29J8RAmj+AKCLN2smkrplZaw4N/aQs9K8mKdFuwCeLVn9 sAbgTCPNY7Xih3Fk/KSgNww= =V3Jd -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Who do you have to sleep with / bribe / shoot to get an answer about RAID support
Mark Demma wrote: > Sorry to be a pest, but will SOMEONE PLEASE give status / make bloody > sure that software RAID support is FINALLY in Debian ... what 3 years > after all the other distro's have it? I don't know of anyone working on software raid support in d-i right now. It would be nice, I agree. The only way you can ensure that it happens, though, is to do it yourself, or hire someone to do it. Otherwise, you're at the mercy of someone else deciding/finding the time to do it. > work is going into "old world mac" floppies, making sure you can > install Debian off the tape drive on that Sinclair you dusted off from > the attic, etc etc, but for those of us trying to use Debian on, gasp, > brand new machines with, gasp brand new SCSI controllers and gasp, raid > controllers This is a matter of people working on what they feel they should work on. d-i will support hardware RAID. -- see shy jo signature.asc Description: Digital signature
Re: proposal for less scary grub installation
Per Olofsson wrote: > On Fri, Apr 09, 2004 at 15:00 -0400, Joey Hess wrote: > > If the user answers no to either question, prompt for a device: > > > > Template: grub-installer/bootdev > > Type: string > > _Description: Device for boot loader installation: > > You need to make the newly installed Debian system bootable, by installing > > the GRUB bootloader on a bootable device. The usual way to do this is to > > install GRUB on the master boot record of your first hard drive. If you > > prefer, you can install grub to elsewhere on the drive, or to another > > drive, or even to a floppy. > > What about a simple menu first, something like: > > Template: grub-installer/bootdev_select > Type: select > _Choices: Root/boot partition, Floppy, Other > _Description: Device for boot loader installation: > ... > > Or perhaps this has already been discussed? It would be nice to have a list of devices at that point indeed instead of a device prompt. My idea though is that it's unnecessary for most users, so most sers should not have to see it, so we can worry about making it better later. -- see shy jo signature.asc Description: Digital signature
boulder
Joyce, Get Vicodin, Hydrocodone, or Soma.. 3 of the best pain killers out! and other popular meds..valiumXanaxCialis http://www.realsun855meds.biz/b32/ -- harrington,it will never.
Bug#242967: installation-reports: install from cdrom (not http/ftp)
Package: installation-reports Severity: wishlist Package: installation-reports Debian-installer-version: beta3 uname -a: Linux lazy 2.6.5 #13 Sun Apr 4 17:08:39 CEST 2004 i686 GNU/Linux Date: Sam Apr 10 01:06:01 CEST 2004 Method: install from modified cdrom Machine: Desktop PC Processor: AMD Athlon XP Memory:256 MB Root Device: na. Root Size/partition table: na. Output of lspci: :00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80) :00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge :00:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) :00:08.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02) :00:0b.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) :00:0b.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) :00:10.0 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 80) :00:10.1 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 80) :00:10.2 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 80) :00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) :00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge :00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C/VT8235 PIPC Bus Master IDE (rev 06) :00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) :01:00.0 VGA compatible controller: nVidia Corporation NV11DDR [GeForce2 MX 100 DDR/200 DDR] (rev b2) Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: I modified the sarge-i386-businesscard.iso, to include some packages on the cdrom (ie. the local mirror that apt-move maintains); and remastered with the current beta3 boot image. The extra packages were put in the directory "extra" ;) Unfortunately, when selecting the mirror, I could not choose file://cdrom/extra. Alternatively, I'd burn the sarge iso as a session, and then add the extra packages in another session in the "dists" and "pool" directories, though this might conflict with the files on the first session (dists/unstable is a link there and would become a directory...) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.5 Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Who do you have to sleep with / bribe / shoot to get an answer about RAID support
Sorry to be a pest, but will SOMEONE PLEASE give status / make bloody sure that software RAID support is FINALLY in Debian ... what 3 years after all the other distro's have it? You know its lovely that so much work is going into "old world mac" floppies, making sure you can install Debian off the tape drive on that Sinclair you dusted off from the attic, etc etc, but for those of us trying to use Debian on, gasp, brand new machines with, gasp brand new SCSI controllers and gasp, raid controllers and software RAID to support thousands of people, you can set your hair on fire and no one will say boo. Please, for gods sake, everything is there! I'll help test, I have over 50 machines running Debian with software RAID! Mark Demma iWin, Inc. Senior Network and Systems Administrator http://www.iwin.com/ http://www.playsite.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
On Fri, Apr 09, 2004 at 07:33:23PM +0200, Malte Cornils wrote: > Am Freitag, 9. April 2004 16:16 schrieb Sven Luther: > > On Fri, Apr 09, 2004 at 03:30:05PM +0200, Malte Cornils wrote: > > > Floppy ejection at this point is normal and could also > > > mean that the kernel boots fine, only that the local console is > > > broken. > > > > Can you tell me what kind of graphic those boxes do have, and i will > > check the fbdev driver for those. > > Sure: > > The PowerMacintosh 4400 on-board video has output-device /bandit/ATY,264VT probably the atyfb or whatever, will check. > The 7200/75's booted Linux kernel (with a woody-installed Debian) shows a > "platinum" device. Where can I find more info on that? Platinumfb probably. > There is also an 8200/120 which should also have the platinum control chip. controlfb. > We have an G3 here (ATY,mach64 GT-C) which might eventually work, too. atyfb. All of themshould be supported : CONFIG_FB_OF=y CONFIG_FB_CONTROL=y CONFIG_FB_PLATINUM=y CONFIG_FB_ATY=y CONFIG_FB_ATY_GX=y CONFIG_FB_ATY_CT=y Don't know what is wrong. > All of them were tested with d-i from 06/Apr, but none worked. (the new disk > images from today still do not have the correct floppy images AFAIK) 09 should have them. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#242958: cdrom-checker: several problems / md5sum for README.html incorrect
Package: debian-installer Version: 20040407 md5sum for README.html is incorrect === If I run md5sum -c md5sum.txt from a shell on a d-i i386 Netinst CD, I get: md5sum: MD5 check failed for './README.html' $ md5sum README.html 2c540198b02dc5492ad5161deae366e1 README.html $ grep "README.html" md5sum.txt 73d7988165adaf1722ffafb4ba66b2ec ./README.html (I have seen this on a lot of builds so far and also on businesscard CD!) cdrom-checker: CD is not checked correctly == If I try to run 'Check the CD-ROM(s) integrity' from the d-i menu on the same CD, I get: The ./dists/sarge/main/binary-i386/Release file failed the MD5 checksum verification. cdrom-checker: problems if run _after_ the main installation If cdrom-checker is run after most of the installation has taken place (e.g. just before rebooting), it causes /dev/cdroms/cdrom0 to be unmounted. This causes the following problems: - If you answer Yes to the question 'Test another?', you get a message 'CD is not a valid Debian CD'. - The CD is no longer ejected if you next select 'Finish installation' before the system is rebooted. I guess this could be fixed by testing if the cdrom is mounted at the start of the test and unmount it after the test if that's the case. Hope this helps. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#242959: FW: Package: discover1-data
Package: discover1-data Version: whatever came with 20040408's netinst daily CD kernel version: 2.4.25-1-386 General hardware: stock Dell Precision 350 Bios rev A01 [3.06GHz Pentium IV w/Hyperthreading turned on] Relevant hardware: PS/2 keyboard, USB mouse problem vector: /usr/sbin/usb-discover Synopsis: Insertion of usb-uhci.o module DISABLES PS/2 keyboard. Installation is rendered impossible. The Short Version: PS/2 Keyboard stops functioning immediately after insertion of usb-uhci.o PS/2 Keyboard stops functioning with or without any USB devices installed. PS/2 Keyboard continues functioning with usb-ehci.o inserted. PS/2 Keyboard stops functioning with or without framebuffer. PS/2 Keyboard functions normally under RedHat [2.4.18][this is probably apples vs. oranges] with usb-uhci.o inserted. Troubleshooting (aka, the long version): When I boot from the sarge netinst CD image daily 03/29 or 04/08, the keyboard locks at the first screen [choose your lang].. booting init=/bin/sh works, and invoking usb-discover locks the keyboard. modprobing /lib/modules/`uname -r`/kernel/drivers/usb/host/usb-uhci.o works, the module when inserts without error, BUT the keyboard is then non-functional. While PS/2 keyboard input is impossible, inserting/removing a usb mouse does result in expected USB kernel messages. So machine is not locked. In short: Machine currently has RedHat 8 on it. [i know this is apples and oranges, but] usb-uhci and usb-ehci both seem to work fine. Machine is equipped with both UHCI and EHCI controllers, the output of lspci [when invoked under redhat, for informational purposes] is as follows: lspci -n 00:00.0 Class 0600: 8086:2530 (rev 04) 00:01.0 Class 0604: 8086:2532 (rev 04) 00:1e.0 Class 0604: 8086:244e (rev 04) 00:1f.0 Class 0601: 8086:2440 (rev 04) 00:1f.1 Class 0101: 8086:244b (rev 04) 00:1f.3 Class 0c05: 8086:2443 (rev 04) 00:1f.5 Class 0401: 8086:2445 (rev 04) 01:00.0 Class 0300: 10de:0258 (rev a3) 02:01.0 Class 0c03: 1106:3038 (rev 50) 02:01.1 Class 0c03: 1106:3038 (rev 50) 02:01.2 Class 0c03: 1106:3104 (rev 51) 02:02.0 Class 0c03: 1106:3038 (rev 50) 02:02.1 Class 0c03: 1106:3038 (rev 50) 02:02.2 Class 0c03: 1106:3104 (rev 51) 02:0c.0 Class 0200: 8086:100e (rev 02) (END) and: lspci -v 00:00.0 Host bridge: Intel Corp. 82850 850 (Tehama) Chipset Host Bridge (MCH) (r ev 04) Subsystem: Dell Computer Corporation: Unknown device 0144 Flags: bus master, fast devsel, latency 0 Memory at e000 (32-bit, prefetchable) [size=128M] Capabilities: [a0] AGP version 2.0 00:01.0 PCI bridge: Intel Corp. 82850 850 (Tehama) Chipset AGP Bridge (rev 04) ( prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, fast devsel, latency 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 Memory behind bridge: fc00-fdff Prefetchable memory behind bridge: e800-f7ff 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 04) (prog-if 00 [N ormal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=64 I/O behind bridge: e000-efff Memory behind bridge: fe10-fe2f 00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 04) Flags: bus master, medium devsel, latency 0 00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 04) (prog-if 80 [Master ]) Subsystem: Dell Computer Corporation: Unknown device 0144 Flags: bus master, medium devsel, latency 0 [virtual] I/O ports at 01f0 [virtual] I/O ports at 03f4 [virtual] I/O ports at 0170 [virtual] I/O ports at 0374 I/O ports at ffa0 [size=16] 00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 04) Subsystem: Dell Computer Corporation: Unknown device 0144 Flags: medium devsel, IRQ 11 I/O ports at dcf0 [size=16] 00:1f.5 Multimedia audio controller: Intel Corp. 82801BA/BAM AC'97 Audio (rev 04 ) Subsystem: Dell Computer Corporation: Unknown device 0144 Flags: bus master, medium devsel, latency 0, IRQ 11 I/O ports at d800 [size=256] I/O ports at dc80 [size=64] 01:00.0 VGA compatible controller: nVidia Corporation Quadro4 900XGL (rev a3) (p rog-if 00 [VGA]) Subsystem: nVidia Corporation: Unknown device 0138 Flags: 66Mhz, medium devsel, IRQ 9 Memory at fc00 (32-bit, non-prefetchable) [size=16M] Memory at f000 (32-bit, prefetchable) [size=128M] Memory at eff8 (32-bit, prefetchable) [size=512K] Expansion ROM at 8000 [disabled] [size=128K] Capabilities: [60] Power Management version 2 Capabilities: [44] AGP version 2.0 02:01.0 USB Controller: VIA Technologies, Inc. USB (rev 50) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller Flags: bus master, medium devsel, latency 64, IRQ 10 I/O ports at ece0 [size=3
Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
On Fri, Apr 09, 2004 at 02:40:37PM -0400, Rick Thomas wrote: > > > Sven Luther wrote: > > > > On Fri, Apr 09, 2004 at 01:37:21AM -0400, Rick Thomas wrote: > > > Malte, > > > > > > > Rick, does this mean that the daily build floppies work for you now ? > > > > Friendly, > > > > Sven Luther > > > Yes. It reads all the floppies and launches d-i as expected. > > I still have problems with d-i once it gets launched. Specifically: > > Booting off of floppy, there is no way to invoke "...PRIORITY=medium" > mode. It just does the default. > > In default PRIORITY mode it always does: > > the dhcp thing -- which succeeds, but it give me a random IP address -- > I need to be able to specify the IP address manually. I think some > other folks have noted this and filed a bug report. > > it always tries to install yaboot (even though archdetect says it's an > oldworld machine. I think something's broken in the yaboot installer) > I've filed a bug report. > > > In summary, there are still problems with d-i on oldworld machines, but > the floppy boot stuff works just fine. Cool. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
On Fri, Apr 09, 2004 at 02:40:37PM -0400, Rick Thomas wrote: > it always tries to install yaboot (even though archdetect says it's an > oldworld machine. I think something's broken in the yaboot installer) > I've filed a bug report. Hang on, are you saying that it always tries to install *yaboot*, not *yaboot-installer*? I thought you meant the latter. In that case, yes, debootstrap always installs yaboot on powerpc. yaboot-installer needs to be fixed to apt-install it before beta4 (so that we don't break beta4 testing), then debootstrap can stop installing it. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: proposal for less scary grub installation
Christian Perrier wrote: > Quoting Joey Hess ([EMAIL PROTECTED]): > > > _Description: Install the GRUB boot loader to the master boot record? > > Install GRUB for managing your system boot? > > Maybe less scary for Bob's and for geeks girlfriends...:-) "... system startup?", then. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: proposal for less scary grub installation
On Fri, Apr 09, 2004 at 15:00 -0400, Joey Hess wrote: > If the user answers no to either question, prompt for a device: > > Template: grub-installer/bootdev > Type: string > _Description: Device for boot loader installation: > You need to make the newly installed Debian system bootable, by installing > the GRUB bootloader on a bootable device. The usual way to do this is to > install GRUB on the master boot record of your first hard drive. If you > prefer, you can install grub to elsewhere on the drive, or to another > drive, or even to a floppy. What about a simple menu first, something like: Template: grub-installer/bootdev_select Type: select _Choices: Root/boot partition, Floppy, Other _Description: Device for boot loader installation: ... Or perhaps this has already been discussed? -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: proposal for less scary grub installation
Quoting Joey Hess ([EMAIL PROTECTED]):
> _Description: Install the GRUB boot loader to the master boot record?
Install GRUB for managing your system boot?
Maybe less scary for Bob's and for geeks girlfriends...:-)
> _Description: Install the GRUB boot loader to the master boot record?
Ditto.
> The following operating systems have been detected on this computer:
> ${OS_LIST}
> .
> If this is all of your other operating systems, it should be safe to
> install the boot loader to the master boot record of your first hard
> drive. You will be able to choose among the operating systems listed
> above, and your new Debian installation, when the computer boots.
When your computer will reboot, you will be prompted for booting
one these operating systems or your new Debian installation.
> Template: grub-installer/bootdev
> Type: string
> _Description: Device for boot loader installation:
> You need to make the newly installed Debian system bootable, by installing
> the GRUB bootloader on a bootable device. The usual way to do this is to
> install GRUB on the master boot record of your first hard drive. If you
> prefer, you can install grub to elsewhere on the drive, or to another
> drive, or even to a floppy.
s/grub/GRUB
s/to elsewhere/elsewhere...but you are the native English speaker
here..:-)
> Probably all of the above would be displayed at high priority, although
> the first could conceivably only be asked at low priority, depending on
> how confident we are that the probe won't miss operating systems.
Hmmm. I tend to prefer high for everything.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#242930: marked as done ("Error reading configuration information")
Your message dated Fri, 9 Apr 2004 15:35:16 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#242930: "Error reading configuration information" 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; 9 Apr 2004 18:17:40 + >From [EMAIL PROTECTED] Fri Apr 09 11:17:40 2004 Return-path: <[EMAIL PROTECTED]> Received: from web11901.mail.yahoo.com [216.136.172.185] by spohr.debian.org with smtp (Exim 3.35 1 (Debian)) id 1BC0ZQ-0005bo-00; Fri, 09 Apr 2004 11:17:40 -0700 Message-ID: <[EMAIL PROTECTED]> Received: from [82.225.76.93] by web11901.mail.yahoo.com via HTTP; Fri, 09 Apr 2004 20:17:29 CEST Date: Fri, 9 Apr 2004 20:17:29 +0200 (CEST) From: =?iso-8859-1?q?Yannick=20Tailliez?= <[EMAIL PROTECTED]> Subject: "Error reading configuration information" To: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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_20,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: X-CrossAssassin-Scores: 1 Package: debian-installer Version: ? I'm trying to install Sarge 20040402 and Sid 20040402 on a Dell Optiplex GX110 and a other self-made computer (both with ps2 keyboard). I have a error message like this, after the boot of the kernel: /home/joey/src/d-i/packages/cdebconf/src/debconf-loadtemplate.c:68 (main) Error reading configuration information modprobe: failed to load module usb-uhci modprobe: failed to load module usbkbd modprobe: failed to load module keybdev modprobe: failed to load module usbserial /home/joey/src/d-i/packages/cdebconf/src/debconf.c:115 (main) Error reading configuration information I need to increase the size of ramdisk before, so i use : - boot: linux ramdisk_size=16384 - boot: expert ramdisk_size=16384 Yannick Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout ! Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/ Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !Téléchargez Yahoo! Messenger sur http://fr.messenger.yahoo.com --- Received: (at 242930-done) by bugs.debian.org; 9 Apr 2004 19:37:08 + >From [EMAIL PROTECTED] Fri Apr 09 12:37:08 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 1BC1oK-00071V-00; Fri, 09 Apr 2004 12:37:08 -0700 Received: from dragon.kitenet.net (dial212.pm3bloun2.bloun.naxs.com [216.98.69.212]) (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 BC22617F54; Fri, 9 Apr 2004 19:37:06 + (GMT) Received: by dragon.kitenet.net (Postfix, from userid 1000) id A5A336E12D; Fri, 9 Apr 2004 15:35:16 -0400 (EDT) Date: Fri, 9 Apr 2004 15:35:16 -0400 From: Joey Hess <[EMAIL PROTECTED]> To: Yannick Tailliez <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Bug#242930: "Error reading configuration information" Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J2SCkAp4GZ/dPZZf" Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> User-Agent: Mutt/1.5.5.1+cvs20040105i 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,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: X-CrossAssassin-Scores: 1 --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Yannick Tailliez wrote: > I'm trying to install Sarge 20040402 and Sid 20040402 on a Dell Optiplex = GX110 > and a other self-made computer (both with ps2 keyboard). Today is Aptil 9th, which means that there are 6 newer builds of images to choose from. The current ones have this problem fixed. --=20 see shy jo --J2SCkAp4GZ/dPZZf Content-Type: application/pgp-signature; name="signature
advertise
Braun, Govenment don't want me to sell UndergroundCD !Check Your spouse and staff Investigate Your Own CREDIT-HISTORY hacking someone PC! Disappear in your city bannedcd2004 http://www.8006hosting.com/cd/ ogre,inflammatory tales about.
Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 09 April 2004 21:49, Rick Thomas wrote: > This is OldWorld PowerMac. > > Booting off of floppy uses the miboot bootloader. It's not like lilo or > grub on i386. There's no point in the process where you get to enter > that kind of stuff. > That means you'd probably like one of the first questions the installer asks to be "At which level would you like to install: normal, medium, expert". Or something like that. (There have been several discussions on the list about the best naming of the different levels.) Personally I wouldn't mind a question like that for i386, but it looks like it is necessary for your platform. Frans -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAdwFvgm/Kwh6ICoQRApYXAKCg5wk4+Q5nJURiWxbVw72uWgomBgCePS2r 0SfhzZrn5Ux0XORv7DxMi/w= =FLRG -END PGP SIGNATURE-
net-retriever_0.30_i386.changes ACCEPTED
Accepted: download-installer_0.30_all.udeb to pool/main/n/net-retriever/download-installer_0.30_all.udeb net-retriever_0.30.dsc to pool/main/n/net-retriever/net-retriever_0.30.dsc net-retriever_0.30.tar.gz to pool/main/n/net-retriever/net-retriever_0.30.tar.gz net-retriever_0.30_all.udeb to pool/main/n/net-retriever/net-retriever_0.30_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cdrom-retriever_0.23_i386.changes ACCEPTED
Accepted: cdrom-retriever_0.23.dsc to pool/main/c/cdrom-retriever/cdrom-retriever_0.23.dsc cdrom-retriever_0.23.tar.gz to pool/main/c/cdrom-retriever/cdrom-retriever_0.23.tar.gz cdrom-retriever_0.23_all.udeb to pool/main/c/cdrom-retriever/cdrom-retriever_0.23_all.udeb load-cdrom_0.23_all.udeb to pool/main/c/cdrom-retriever/load-cdrom_0.23_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
floppy-retriever_0.25_i386.changes ACCEPTED
Accepted: floppy-retriever_0.25.dsc to pool/main/f/floppy-retriever/floppy-retriever_0.25.dsc floppy-retriever_0.25.tar.gz to pool/main/f/floppy-retriever/floppy-retriever_0.25.tar.gz floppy-retriever_0.25_all.udeb to pool/main/f/floppy-retriever/floppy-retriever_0.25_all.udeb load-floppy_0.25_all.udeb to pool/main/f/floppy-retriever/load-floppy_0.25_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
Frans Pop wrote: > > On Friday 09 April 2004 20:40, you wrote: > > Booting off of floppy, there is no way to invoke "...PRIORITY=medium" > > mode. It just does the default. > > > Are you sure? > You have to enter 'linux DEBCONF_PRIORITY=medium' > > Frans This is OldWorld PowerMac. Booting off of floppy uses the miboot bootloader. It's not like lilo or grub on i386. There's no point in the process where you get to enter that kind of stuff. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of cdrom-retriever_0.23_i386.changes
cdrom-retriever_0.23_i386.changes uploaded successfully to localhost along with the files: cdrom-retriever_0.23.dsc cdrom-retriever_0.23.tar.gz cdrom-retriever_0.23_all.udeb load-cdrom_0.23_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Reopening #239386
Processing commands for [EMAIL PROTECTED]: > reopen 239386 Bug#239386: Allows to deselect unnecessary modules but tries to use them later Bug reopened, originator not changed. > severity 239386 wishlist Bug#239386: Allows to deselect unnecessary modules but tries to use them later Severity set to `wishlist'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: timeline for beta 4
Will beta 4 have support for installing on software RAID? Sorry to be whining about this, but I've been desperately wanting this for YEARS. I've installed Debian on over 100 commercial machines now with software raid and will SO bake you guys cookies if you can make this happen! Heck I'll even go down to Haight Street and get some extra special ingredients for it! Mark Demma iWin, Inc. Senior Network and Systems Administrator http://www.iwin.com/ http://www.playsite.com On 8 Apr 2004, at 17:55, Joey Hess wrote: This may seem early, but beta 4 is closer than it may appear. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of net-retriever_0.30_i386.changes
net-retriever_0.30_i386.changes uploaded successfully to localhost along with the files: net-retriever_0.30.dsc net-retriever_0.30.tar.gz net-retriever_0.30_all.udeb download-installer_0.30_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of floppy-retriever_0.25_i386.changes
floppy-retriever_0.25_i386.changes uploaded successfully to localhost along with the files: floppy-retriever_0.25.dsc floppy-retriever_0.25.tar.gz floppy-retriever_0.25_all.udeb load-floppy_0.25_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
proposal for less scary grub installation
I've wanted to make the grub boot loader installation screen less scary
for a while. This proposal hinges on the new os-prober stuff working
reasonably well. The idea is to make grub-installer on startup probe for
other OS's using os-prober. If it seems that all drives were used by the
debian install, display this template:
Template: grub-installer/only_debian
Type: boolean
Default: true
_Description: Install the GRUB boot loader to the master boot record?
It seems that Debian will be the only operating system on this computer,
so it should be safe to install the boot loader to the master boot record
of your first hard drive.
If some other OSes were found, display this template instead:
Template: grub-installer/with_other_os
Type: boolean
Default: true
_Description: Install the GRUB boot loader to the master boot record?
The following operating systems have been detected on this computer:
${OS_LIST}
.
If this is all of your other operating systems, it should be safe to
install the boot loader to the master boot record of your first hard
drive. You will be able to choose among the operating systems listed
above, and your new Debian installation, when the computer boots.
If the user answers no to either question, prompt for a device:
Template: grub-installer/bootdev
Type: string
_Description: Device for boot loader installation:
You need to make the newly installed Debian system bootable, by installing
the GRUB bootloader on a bootable device. The usual way to do this is to
install GRUB on the master boot record of your first hard drive. If you
prefer, you can install grub to elsewhere on the drive, or to another
drive, or even to a floppy.
Probably all of the above would be displayed at high priority, although
the first could conceivably only be asked at low priority, depending on
how confident we are that the probe won't miss operating systems.
I'll try implementing this in people/joeyh/grub-installer in svn.
--
see shy jo
signature.asc
Description: Digital signature
Bug#239386: #239386: Allows to deselect unnecessary modules but tries to use them later
Frans Pop wrote: > After I have deselected modules for the 1st hardware detection, I am now given > a new list for the 2nd hw detection. In this list the previously deselected > modules are again presented and _selected_ by default. > If I manually deselect them, no problems. But if I just continue, the red > screens still appear. > > I think either the previously deselected modules should be not be included in > later lists or should be deselected by default. You're probably right, feel free to reopen it (as wishlist). -- see shy jo signature.asc Description: Digital signature
Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
Sven Luther wrote: > > On Fri, Apr 09, 2004 at 01:37:21AM -0400, Rick Thomas wrote: > > Malte, > > > > Rick, does this mean that the daily build floppies work for you now ? > > Friendly, > > Sven Luther Yes. It reads all the floppies and launches d-i as expected. I still have problems with d-i once it gets launched. Specifically: Booting off of floppy, there is no way to invoke "...PRIORITY=medium" mode. It just does the default. In default PRIORITY mode it always does: the dhcp thing -- which succeeds, but it give me a random IP address -- I need to be able to specify the IP address manually. I think some other folks have noted this and filed a bug report. it always tries to install yaboot (even though archdetect says it's an oldworld machine. I think something's broken in the yaboot installer) I've filed a bug report. In summary, there are still problems with d-i on oldworld machines, but the floppy boot stuff works just fine. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#242930: "Error reading configuration information"
Package: debian-installer Version: ? I'm trying to install Sarge 20040402 and Sid 20040402 on a Dell Optiplex GX110 and a other self-made computer (both with ps2 keyboard). I have a error message like this, after the boot of the kernel: /home/joey/src/d-i/packages/cdebconf/src/debconf-loadtemplate.c:68 (main) Error reading configuration information modprobe: failed to load module usb-uhci modprobe: failed to load module usbkbd modprobe: failed to load module keybdev modprobe: failed to load module usbserial /home/joey/src/d-i/packages/cdebconf/src/debconf.c:115 (main) Error reading configuration information I need to increase the size of ramdisk before, so i use : - boot: linux ramdisk_size=16384 - boot: expert ramdisk_size=16384 Yannick Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout ! Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/ Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !Téléchargez Yahoo! Messenger sur http://fr.messenger.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#242787: termwrap: [PATCH] use console-cyrrilic if available for KOI8-U
Package: base-config Version: 2.17 Severity: normal Followup-For: Bug #242787 Please apply this additional patch. It adds possibility to use console-cyrillic if it is available for KOI8-U. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.25 Locale: LANG=uk_UA, LC_CTYPE=uk_UA Versions of packages base-config depends on: ii adduser 3.52 Add and remove users and groups ii apt 0.5.24 Advanced front-end for dpkg ii aptitude0.2.14.1-2 curses-based apt frontend ii bsdutils1:2.12-6 Basic utilities from 4.4BSD-Lite ii console-data2002.12.04dbs-35 Keymaps, fonts, charset maps, fall ii console-tools 1:0.2.3dbs-50Linux console and font utilities ii debconf 1.4.21 Debian configuration management sy ii debianutils 2.8.1Miscellaneous utilities specific t ii gettext-base0.14.1-2 GNU Internationalization utilities ii passwd 1:4.0.3-26 Change and administer password and -- debconf information excluded ? termwrap-devfs.diff ? termwrap-koi8u.diff ? termwrap-ukr-cyr.diff Index: termwrap === RCS file: /cvsroot/base-config/base-config/termwrap,v retrieving revision 1.34 diff -u -r1.34 termwrap --- termwrap8 Apr 2004 21:06:01 - 1.34 +++ termwrap9 Apr 2004 18:15:25 - @@ -255,7 +255,11 @@ ;; KOI8-U) # Load KOU8-U charset mapping into console - try_load_charset "$ENCODING" koi8u koi8u_8x16 + if [ -x /usr/bin/cyr ]; then + /usr/bin/cyr -s uni -f 16 -e koi8-u ua_ms ctrl_shift_toggle + else + try_load_charset "$ENCODING" koi8u koi8u_8x16 + fi ;; eucJP|EUC-JP) # Japanese
Bug#241117: termwrap: cyr has not option -t
Package: base-config Version: 2.17 Severity: normal Followup-For: Bug #241117 Program cyr used for KOI8-R support has no option -t Option -f should be used instead. # LANG=ru_RU.KOI8-R ./termwrap true cyr: Unknown option: -t cyr: Try `cyr --help for more information. info: Switching console charset mapping to KOI8-R # -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Need help for SVN pseudo-URLs
Quoting Bart Cornelis ([EMAIL PROTECTED]): > looking at the alioth page for debian-installer trorrr-guest, does not seem > to be a member of the debian-installer project. You need to contact one of > the project admins, so he can add you to the project. OK. Hector, you now have commit access to d-i, base-config and tasksel... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [deb-installer] Failure at boot loader phase
Nicolas Will wrote: > What about the lilo/devfs stuff? I wasn't very clear on what you were talking about. Lilo has been recently fixed to accept non-devfs names, and it seems to work. -- see shy jo signature.asc Description: Digital signature
Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
Hi! See comments interleaved below... Rick Malte Cornils wrote: > > Hi Rick, > > On Fri, Apr 09, 2004 at 01:37:21AM -0400, Rick Thomas wrote: > > Errors like that are usually symptomatic of a dirty/dusty floppy drive. > > > > In particular, if the boot floppy is ejected, it means that the > > firmware got an error trying to read it, or couldn't find the magic > > numbers in the magic places that it was expecting from a real-live > > Macintosh boot floppy. > > The boot floppy is ejected after the miboot run (the little icon > with the penguin) had finished and few more seconds (enough time for > the kernel to boot and display the usual "insert root disk" message) > have passed. Floppy ejection at this point is normal and could also > mean that the kernel boots fine, only that the local console is > broken. In my experience, the floppy is *not* automatically ejected when the "insert root disk" message comes up. I always have to use the paper-clip trick to get the disk out so I can put the root disk in. (Again, in my experience) the only time the disk is automatically ejected is when the firmware has a problem reading it. This is with two machines -- a beige G3 mini-tower and a PowerMac 6500/225. > > > You should clean *both* the drive you will be writing the disk on, > > and the one you will be reading it on. > > That is the second attempt was made on completely unrelated systems > (both the PC generating the floppy and the Mac were different). > > Disk was made apparently without errors, and cmp showed no > differences. (I was more careful with that after your last mail > regarding that topic). That's a good sign. But (as you've seen) not conclusive -- the reading drive could be dirty (or out of calibration -- which is actually more serious because the only fix for that is to replace it. It would cost more to have it recalibrated than the drive's worth.) > > > Also, buy a box of new floppies. Don't use floppys that have been > > sitting around the house for a few years. They accumulate dust > > over time and the oxide deteriorates. > > Yeah, that was when I was shocked how (relatively) expensive floppies > had become now that almost no one uses them anymore. Sigh! So true... > > I will buy a cleaning set soon, I think you'll see a dramatic difference when you do. I couldn't get anything to work at all until I'd cleaned all the drives twice! > but I would appreciate it if someone > could test the current images (Holger?) on similar hardware. I'll test the latest daily-build boot floppies this weekend on both of my test machines and send you a report. > > Yours > -Malte > Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: timeline for beta 4
Heya! On Fri, Apr 09, 2004 at 07:30:29AM +0200, Christian Perrier wrote: > leaving for my holidays (4/16 to 4/24) but as I won't have net access, > I won't be able to get the translators team ready for beta4 > release. They will be on their own.but most of them can manage > this..:-) (..) > Maybe Dennis Stampfer or Denis Barbier would be of some help ? > (guys, CC'ing you just to be sure) sure, I will have a eye on -boot and commits and IRC. (and of course 2nd and 3rd-stage stats) and helping translator to commit. I am available for ping'ing :) dennis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [deb-installer] Failure at boot loader phase
Joey Hess wrote: Nicolas Will wrote: OK, so it finally worked, it just takes an awfuly long time, it says so on the console, but I wasn't expecting it to be that long... Apparently it is linked to the lack of floppy drive in my system. This is fixed in the daily builds, grub-installer will not probe for a floppy drive by default. Nice. That floppy drive thing On the first choice of hardware detection, I unchecked the floppy part. But then later on during the intall (at least in expert mode) it just inserts the module without asking...and makes grub even longer... I don't know what would have loaded the floppy module behind your back in expert mode. I had the error messages on the consoles, so they must have been due to Grub then. Please excuse my confusion. What about the lilo/devfs stuff? Nico -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
995-8-2-41 Egliash for you!
Привет "Debian-boot"! Как дела? Предлагаем быстро выучить Разговорный английский язык Уникальная методика обучения - МЫШЛЕНИЕ, произношение, стиль речи. Тел.995-8241 Moscow Russia Звоните сейчас! Приходите сегодня! Наш сайт .amercenterpub.info -start learning english Today! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] PCMCIA network cards + Cardbus
On Fri, Apr 09, 2004 at 13:30 -0400, Joey Hess wrote: > Hmm, could there be a race between hw-detect registering the hotplug > script, and netcfg reading the list of hotpluggable interfaces? Hmm... possibly. I do not know exactly how hotplug events are delivered. I will have to check this. > Other than that, aside from the *ew* factor of having to do it this way, > looks ok to me. Feel free to commit if it works, it's certianly a step > up from what we have now. OK, thanks. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
Am Freitag, 9. April 2004 16:16 schrieb Sven Luther: > On Fri, Apr 09, 2004 at 03:30:05PM +0200, Malte Cornils wrote: > > Floppy ejection at this point is normal and could also > > mean that the kernel boots fine, only that the local console is > > broken. > > Can you tell me what kind of graphic those boxes do have, and i will > check the fbdev driver for those. Sure: The PowerMacintosh 4400 on-board video has output-device /bandit/ATY,264VT The 7200/75's booted Linux kernel (with a woody-installed Debian) shows a "platinum" device. Where can I find more info on that? There is also an 8200/120 which should also have the platinum control chip. We have an G3 here (ATY,mach64 GT-C) which might eventually work, too. All of them were tested with d-i from 06/Apr, but none worked. (the new disk images from today still do not have the correct floppy images AFAIK) -Malte -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] PCMCIA network cards + Cardbus
Per Olofsson wrote: > I have created patches now for ddetect and netcfg which implement > Cardbus support and proper configuration of PCMCIA network > interfaces. The latter means that it doesn't create an auto entry for > PCMCIA cards but lists it in a "mapping hotplug" stanza. The whole > thing is implemented by a temporary hotplug agent. The module loading > part for Cardbus devices isn't very nice but I'm not sure how to do it > otherwise, and besides, we will have to do it differently for 2.6 > kernels anyway. Hmm, could there be a race between hw-detect registering the hotplug script, and netcfg reading the list of hotpluggable interfaces? Other than that, aside from the *ew* factor of having to do it this way, looks ok to me. Feel free to commit if it works, it's certianly a step up from what we have now. -- see shy jo signature.asc Description: Digital signature
Re: [deb-installer] Failure at boot loader phase
Nicolas Will wrote: > OK, so it finally worked, it just takes an awfuly long time, it says so > on the console, but I wasn't expecting it to be that long... Apparently > it is linked to the lack of floppy drive in my system. This is fixed in the daily builds, grub-installer will not probe for a floppy drive by default. > That floppy drive thing On the first choice of hardware detection, I > unchecked the floppy part. But then later on during the intall (at least > in expert mode) it just inserts the module without asking...and makes > grub even longer... I don't know what would have loaded the floppy module behind your back in expert mode. -- see shy jo signature.asc Description: Digital signature
