Re: Install report with UEFI Debian CD on HP elitebook 840 G1
In the installer on the usbstick with upload3 in UEFI Boot only (Without CSM) mode: # cat /sys/firmware/efi/fw_platform_size 64 You had my attention, but now you have my curiosity... -- Jean PRIVAT, professeur/professor Département d'informatique/Department of Computer Science U.Q.A.M. CP , succ. centre-ville Montréal (Québec) Canada H3C 3P8 Bureau/Office: PK-4830 Site/Web: http://info.uqam.ca/~privat/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/camqw0oma1nfng76inwjbfeamcl4iu0o2h-w1xgtxsrijoyh...@mail.gmail.com
Re: Install report with UEFI Debian CD on HP elitebook 840 G1
On Tue, Jan 13, 2015 at 09:49:22AM -0500, Jean Privat wrote: In the installer on the usbstick with upload3 in UEFI Boot only (Without CSM) mode: # cat /sys/firmware/efi/fw_platform_size 64 I was hoping (maybe?) that you might have got 32 there, implying that the system wasn't booting automatically for that reason. Oh well, I think you just have awkward/buggy firmware then... :-/ -- Steve McIntyre, Cambridge, UK.st...@einval.com We don't need no education. We don't need no thought control. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150113145427.ga22...@einval.com
Re: Install report with UEFI Debian CD on HP elitebook 840 G1
Hmmm, sounds like a BIOS/firmware bug if you need to add that custom boot method - UEFI boot option registration should work without that. After the install, the computer booted to windows. Using the bios bootmenu (F9) the default option is OS Boot Manager that boots windows. But debian is present in the menu at the last position and selecting it successfully boot debian. In the bios setup (F10), in the boot option menu, I can change the order of the boot options but there is no debian present in the list : only OS Boot Manager, a lot of hardware boot option like USD Hard Drive or SD Card, the last option is Customized Boot. So I just moved Customized Boot to the first place and give it the value recommended by https://wiki.debian.org/InstallingDebianOn/HP/EliteBook%20840%20G1 Also: you've tried my unofficial Jessie development image - is that because the standard images didn't work, or is this just the first image you tried? I tried first a daily USB image from http://d-i.debian.org/daily-images/amd64/daily/ But: * I had to use UEFI Hybrid (With CSM) (instead of UEFI Boot only (Without CSM)) so that the bios can see the USB key * The install was successful but it seems that the grub install silently failed since, after the reboot, there was no debian (or any new option) in the boot menu * I retried the USB key in rescue mode, so I can force-install grub manually but it failed (I do not remember the error message) and the grub-efi version did not work either because no EFI (no /sys/firmware/efi/ ). It is possible that the bios option UEFI Hybrid (With CSM) hides the EFI to the installer * Seeing that the installer did not like the EFI, I remembered http://blog.einval.com/2015/01/11#Jessie-EFI_5 and just tried the proposed image * I reseted the bios to UEFI Boot only (Without CSM) and the bios showed the new USB key, so could retry the install. -- Jean PRIVAT, professeur/professor Département d'informatique/Department of Computer Science U.Q.A.M. CP , succ. centre-ville Montréal (Québec) Canada H3C 3P8 Bureau/Office: PK-4830 Site/Web: http://info.uqam.ca/~privat/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/camqw0op_op4qsufcw6bdwyky_xdwkhk0m2r70pyvmn8jue-...@mail.gmail.com
Re: Install report with UEFI Debian CD on HP elitebook 840 G1
On Mon, Jan 12, 2015 at 03:40:50PM -0500, Jean Privat wrote: Yes, that sounds like the problem. You've ended up booting in BIOS mode, so the installer can't do any EFI things at all. Roughly when did you try this daily image? In the last month or so, or older than that? last wednesday if I remember correctly. so 2015-01-07 OK, thanks. * Seeing that the installer did not like the EFI, I remembered http://blog.einval.com/2015/01/11#Jessie-EFI_5 and just tried the proposed image * I reseted the bios to UEFI Boot only (Without CSM) and the bios showed the new USB key, so could retry the install. OK, that's very odd. You've booted using 64-bit grub-efi. But the new image *shouldn't* be showing any differences there! Can you test something else for me please? What does # cat /sys/firmware/efi/fw_platform_size say on the installed system, please? This file does not exist neither on the installed system, nor within the installer from the USB stick that contains your upload2 image. I tried to `find` it but still nothing. The file fw_vendor exists and contains 0xbb32e318 Ah, sorry - I got confused. Tha file should exist in the upload3 image. If it's not too much trouble, could I ask you to try that please, and run 64-bit install? I've got a suspicion that your system is a bit odd! -- Steve McIntyre, Cambridge, UK.st...@einval.com Support the Campaign for Audiovisual Free Expression: http://www.eff.org/cafe/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150112204754.gu21...@einval.com
Re: Install report with UEFI Debian CD on HP elitebook 840 G1
Yes, that sounds like the problem. You've ended up booting in BIOS mode, so the installer can't do any EFI things at all. Roughly when did you try this daily image? In the last month or so, or older than that? last wednesday if I remember correctly. so 2015-01-07 * Seeing that the installer did not like the EFI, I remembered http://blog.einval.com/2015/01/11#Jessie-EFI_5 and just tried the proposed image * I reseted the bios to UEFI Boot only (Without CSM) and the bios showed the new USB key, so could retry the install. OK, that's very odd. You've booted using 64-bit grub-efi. But the new image *shouldn't* be showing any differences there! Can you test something else for me please? What does # cat /sys/firmware/efi/fw_platform_size say on the installed system, please? This file does not exist neither on the installed system, nor within the installer from the USB stick that contains your upload2 image. I tried to `find` it but still nothing. The file fw_vendor exists and contains 0xbb32e318 -- Jean PRIVAT, professeur/professor Département d'informatique/Department of Computer Science U.Q.A.M. CP , succ. centre-ville Montréal (Québec) Canada H3C 3P8 Bureau/Office: PK-4830 Site/Web: http://info.uqam.ca/~privat/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/camqw0on3kqfwcjqvdtqosrvahjczmc+rq9k4283f2d46t-b...@mail.gmail.com
Re: Install report with UEFI Debian CD on HP elitebook 840 G1
On Mon, Jan 12, 2015 at 09:35:30AM -0500, Jean Privat wrote: Hmmm, sounds like a BIOS/firmware bug if you need to add that custom boot method - UEFI boot option registration should work without that. After the install, the computer booted to windows. Using the bios bootmenu (F9) the default option is OS Boot Manager that boots windows. But debian is present in the menu at the last position and selecting it successfully boot debian. In the bios setup (F10), in the boot option menu, I can change the order of the boot options but there is no debian present in the list : only OS Boot Manager, a lot of hardware boot option like USD Hard Drive or SD Card, the last option is Customized Boot. So I just moved Customized Boot to the first place and give it the value recommended by https://wiki.debian.org/InstallingDebianOn/HP/EliteBook%20840%20G1 Also: you've tried my unofficial Jessie development image - is that because the standard images didn't work, or is this just the first image you tried? I tried first a daily USB image from http://d-i.debian.org/daily-images/amd64/daily/ But: * I had to use UEFI Hybrid (With CSM) (instead of UEFI Boot only (Without CSM)) so that the bios can see the USB key * The install was successful but it seems that the grub install silently failed since, after the reboot, there was no debian (or any new option) in the boot menu * I retried the USB key in rescue mode, so I can force-install grub manually but it failed (I do not remember the error message) and the grub-efi version did not work either because no EFI (no /sys/firmware/efi/ ). It is possible that the bios option UEFI Hybrid (With CSM) hides the EFI to the installer Yes, that sounds like the problem. You've ended up booting in BIOS mode, so the installer can't do any EFI things at all. Roughly when did you try this daily image? In the last month or so, or older than that? * Seeing that the installer did not like the EFI, I remembered http://blog.einval.com/2015/01/11#Jessie-EFI_5 and just tried the proposed image * I reseted the bios to UEFI Boot only (Without CSM) and the bios showed the new USB key, so could retry the install. OK, that's very odd. You've booted using 64-bit grub-efi. But the new image *shouldn't* be showing any differences there! Can you test something else for me please? What does # cat /sys/firmware/efi/fw_platform_size say on the installed system, please? -- Steve McIntyre, Cambridge, UK.st...@einval.com Can't keep my eyes from the circling sky, Tongue-tied twisted, Just an earth-bound misfit, I... -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150112171749.gh13...@einval.com
Re: Install report with UEFI Debian CD on HP elitebook 840 G1
On Tue, Jan 06, 2015 at 04:05:15PM -0500, Jean Privat wrote: Hi, Hi Jean, I just received a new laptop so naturally I installed Debian on it. *grin* Of course! My steps: * on the elitebook, update the bios firmware trough the bios setup * on an other computer, dd the image from http://cdimage.debian.org/cdimage/unofficial/efi-development/jessie-upload2/ on a USB stick * the USB stick appears in the list of boot options (F9). Note that the computer is in pure uefi without CSM emulation * install Debian from the usbstick. Everything seems to be recognized (except wifi that need a non-free firmware) * on reboot, `debian` now appears on the boot options (F9) * in the bios setup, configure custom boot method with path \EFI\debian\grubx64.efi. Also, change the boot order so custom boot method is the first choice Hmmm, sounds like a BIOS/firmware bug if you need to add that custom boot method - UEFI boot option registration should work without that. Also: you've tried my unofficial Jessie development image - is that because the standard images didn't work, or is this just the first image you tried? Cheers, -- Steve McIntyre, Cambridge, UK.st...@einval.com I can't ever sleep on planes ... call it irrational if you like, but I'm afraid I'll miss my stop -- Vivek Dasmohapatra -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150112025613.go21...@einval.com
Re: install report
On Mon, 2004-07-05 at 19:57 +, digital fredy wrote: 4 put rescue mode for recover the system I would like to see a small DFS (Debian From Scratch) Live-CD on the same disc as d-i, so that it can be dual-booted to either the installer or a rescue CD. Or, perhaps the rescue system could have a command that launches the installer? That would work if they use the same kernel. For this to work right, the DFS system must be very small, and must totally run from RAM. The idea is to find the CD, umount it, dd the .iso into ramdisk, then loop mount that, freeing the CD to be changed at will. This will of course not work in a low-memory computer. I will probably require a minimum of 256 to 512 Mb ram. Ideas? -- Karl Hegbloom [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install Report (22 June 04 Daily Build), Problem with Time Zones
Quoting Michael Bonert ([EMAIL PROTECTED]): Debian-installer-version: 22 June 2004 $ md5sum sarge-i386-netinst.iso 5db3c8d500380d664c748356910a6d2e sarge-i386-netinst.iso For the record, this is 20040622 sid_d-i There appears to be some problem with the time zone settings. I set the clock to UTC and my time zone to Eastern (Canada). Then I noticed... the time that is displayed is UTC. I then poked around in the /etc files and another directory I found: --- [EMAIL PROTECTED]:/usr/share/zoneinfo$ ls -lat localtime lrwxrwxrwx1 root root 14 2004-06-23 20:07 localtime - /etc/localtime --- The above is RED (broken link) -- '/etc/localtime' does NOT exist-- I suspect this is an install quirk! I can't reproduce this with my usual test install path (French+Francewhich leads me to Europe/Paris as timezone)and clock not being UTC. /etc/localtime there is a ling to /usr/share/zoneinfo/Europe/Paris Any case, it was nice to see that the normal user I created was put into the group audio -- the sound worked without me having to do anything. :-) When I first installed Debian last August, I remember Hmmm, I missed that change. I think this is a base-config hack so that the user created in base-config is kinda special and this allows not changing shadow (who is really in charge of the user creation). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install Report (22 June 04 Daily Build), Problem with Time Zones
Christian, I'm not sure what to say to the fact that you can't reproduce it. Well, here are some more settings--perhaps they may help you track down the problem: Base System Install - language setting: - en (other countries) english Country: - Canada Kernel: kernel-image-2.6.6-1-386 - Debian System Configuration (after reboot) - Set hardware clock to GMT? - YES Time Zone: - Eastern Software selection method: - nothing, you may manually run apt-get or any of the above later = The above issue aside, I just remembered one thing I really disliked--not directly related to the installer but installing in general. It relates to the package 'shorewall' -- the directory that (usually) holds the configuration files /etc/shorewall/ was empty. The default configuration files were in /usr/share/doc/shorewall/default-config/. I don't know if there is a good reason for the change (they used to be in /etc/shorewall/) --but I can't help think the current arrangement (of default config files) is less newbie friendly. Also, isn't the first thing one does is--copy the default config files to the /usr/shorewall/ directory? Michael On Thu, 24 Jun 2004, Christian Perrier wrote: Quoting Michael Bonert ([EMAIL PROTECTED]): Debian-installer-version: 22 June 2004 $ md5sum sarge-i386-netinst.iso 5db3c8d500380d664c748356910a6d2e sarge-i386-netinst.iso For the record, this is 20040622 sid_d-i There appears to be some problem with the time zone settings. I set the clock to UTC and my time zone to Eastern (Canada). Then I noticed... the time that is displayed is UTC. I then poked around in the /etc files and another directory I found: --- [EMAIL PROTECTED]:/usr/share/zoneinfo$ ls -lat localtime lrwxrwxrwx1 root root 14 2004-06-23 20:07 localtime - /etc/localtime --- The above is RED (broken link) -- '/etc/localtime' does NOT exist-- I suspect this is an install quirk! I can't reproduce this with my usual test install path (French+Francewhich leads me to Europe/Paris as timezone)and clock not being UTC. /etc/localtime there is a ling to /usr/share/zoneinfo/Europe/Paris Any case, it was nice to see that the normal user I created was put into the group audio -- the sound worked without me having to do anything. :-) When I first installed Debian last August, I remember Hmmm, I missed that change. I think this is a base-config hack so that the user created in base-config is kinda special and this allows not changing shadow (who is really in charge of the user creation). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install Report (22 June 04 Daily Build), Problem with Time Zones
Well, here are some more settings--perhaps they may help you track down the problem: After running exactly this setup in VmWare, I finally ended with date showing a time in EDT timezone. and /etc/localtime was properly linked to /usr/share/zoneinfo/Canada/Eastern So, I'm afraid investigating the issue you reported will be very difficult. Can you retry this setup or was it a one-time install? It relates to the package 'shorewall' -- the directory that (usually) holds the configuration files /etc/shorewall/ was empty. The default configuration files were in /usr/share/doc/shorewall/default-config/. I don't know if there is a good reason for the change (they used to be in /etc/shorewall/) --but I can't help think the current arrangement (of default config files) is less newbie friendly. Also, isn't the first thing one does is--copy the default config files to the /usr/shorewall/ directory? I suggest you report this as a bug against the shorewall package and deal it with the maintainer. Michael On Thu, 24 Jun 2004, Christian Perrier wrote: Quoting Michael Bonert ([EMAIL PROTECTED]): Debian-installer-version: 22 June 2004 $ md5sum sarge-i386-netinst.iso 5db3c8d500380d664c748356910a6d2e sarge-i386-netinst.iso For the record, this is 20040622 sid_d-i There appears to be some problem with the time zone settings. I set the clock to UTC and my time zone to Eastern (Canada). Then I noticed... the time that is displayed is UTC. I then poked around in the /etc files and another directory I found: --- [EMAIL PROTECTED]:/usr/share/zoneinfo$ ls -lat localtime lrwxrwxrwx1 root root 14 2004-06-23 20:07 localtime - /etc/localtime --- The above is RED (broken link) -- '/etc/localtime' does NOT exist-- I suspect this is an install quirk! I can't reproduce this with my usual test install path (French+Francewhich leads me to Europe/Paris as timezone)and clock not being UTC. /etc/localtime there is a ling to /usr/share/zoneinfo/Europe/Paris Any case, it was nice to see that the normal user I created was put into the group audio -- the sound worked without me having to do anything. :-) When I first installed Debian last August, I remember Hmmm, I missed that change. I think this is a base-config hack so that the user created in base-config is kinda special and this allows not changing shadow (who is really in charge of the user creation). -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#230440: marked as done (FWD: Re: INSTALL REPORT with 2004-01-09 netinst, failed)
Your message dated Fri, 11 Jun 2004 20:03:58 -0400 with message-id [EMAIL PROTECTED] and subject line processing 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; 30 Jan 2004 23:36:44 + From [EMAIL PROTECTED] Fri Jan 30 15:36:44 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 1AmiBo-NX-00; Fri, 30 Jan 2004 15:36:44 -0800 Received: from dragon.kitenet.net (pm3naxs21-50.access.naxs.com [216.98.95.50]) (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 010DD18059 for [EMAIL PROTECTED]; Fri, 30 Jan 2004 23:36:40 + (GMT) Received: by dragon.kitenet.net (Postfix, from userid 1000) id BA1F96ECB2; Fri, 30 Jan 2004 18:44:21 -0500 (EST) Date: Fri, 30 Jan 2004 18:44:21 -0500 From: Joey Hess [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: FWD: Re: INSTALL REPORT with 2004-01-09 netinst, failed Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=6Vw0j8UKbyX0bfpA Content-Disposition: inline User-Agent: Mutt/1.5.5.1+cvs20040105i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_01_27 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_01_27 X-Spam-Level: --6Vw0j8UKbyX0bfpA Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Package: installation-reports =20 The following installation report was posted to debian-boot, and, according to my records, never followed up on. I am putting it in the BTS so it will not be lost. - Forwarded message from Yann Dirson [EMAIL PROTECTED] - =46rom: Yann Dirson [EMAIL PROTECTED] Date: Mon, 12 Jan 2004 16:41:51 +0100 To: [EMAIL PROTECTED] Subject: Re: INSTALL REPORT with 2004-01-09 netinst, failed As I attempt to do more not-so-uncommon things (with the 2004-01-03 snapshot)... - I initially have a HD with a single ext3 partition + swap (from a previous RH install). If I repartition by deleting the ext3 and repartitionning that space in 2, on the partition setup screen I notice the 1st partition is already listed as ext3, and the 2nd not. Then I realize it comes from the previous (RH) install. I had not realized that when just selecting a single partition, when I thought ext3 was just a default. Now if my original single-partition-over-RH had gone throught the reboot stage, I may surely have ended up with a strange install. And indeed the nc binary I had noticed, as well as the __libc_stack_end issues probably derive from that. - Maybe the partition-setup screen could emphasize this issue ? - How about forcing system partitions (/, /usr(/*)?, /var(/*)?) to be formatted, or at least require confirmation ? - Is it really a good idea to use those programs just installed before rebooting ? - Now when I decide to split the existing partition in 2, but do not realize I must explicitely select format as ext3, since my partition already appears as having ext3 selected (I thought), and go on, I'm brought back to the main menu on the next step, and requesting to install the base system brings me back there again almost instantly. Only by looking at syslog I finally notice a read beyond end of device attempt, which finally enlighten me on what's going on. - the user should be notified of such errors by an error box. - What about forcing the user to reformat such partitions, which we can decide must be invalid because they just reuse an existing block ? =20 Or, probably better, when destroying a partition, we (cfdisk ?) could ask the user whether to nuke the 1st sectors, to avoid further misdetection. - Once base packages are unpacked, while setting up lilo, I'm now presented with a textbox containing the devfs name for the disk. If I want to install lilo in another location, it looks like I have to know the devfs path, whereas in the old installer I could choose in a list, which is much more suited to people not knowing devfs BTW, is it wise at all to use devfs, which is tagged as OBSOLETE in 2.6 !? - Selecting French as the keyboard
Bug#230440: FWD: Re: INSTALL REPORT with 2004-01-09 netinst, failed
On 27.V.2004 at 13:55 (+0200) Yann Dirson wrote: Then partition objects in memory should probably be initialized as having no fs on them, instead of looking up the disk. This is exactly what the newer versions of partman do. Or, maybe better, they could be initialized from disk only if the fs size matches (or maybe is smaller than) the new partition This is necessary for partitions that exist on the disk but difficult to implement because such checks depend on the file system, libparted doesn't support them and no library packaged as udeb does. Anton Zinoviev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#230440: FWD: Re: INSTALL REPORT with 2004-01-09 netinst, failed
On Tue, May 25, 2004 at 02:17:50PM +0100, Martin Michlmayr wrote: As I attempt to do more not-so-uncommon things (with the 2004-01-03 snapshot)... This is very old now can you please try a new image from http://gluck.debian.org/cdimage/testing/sarge_d-i/ and see if that works better? Yes, I've planned to test the latest beta, I'll let you know. BTW, this @alcove email will expire soon, please use the @d.o one for further contact. - I initially have a HD with a single ext3 partition + swap (from a previous RH install). If I repartition by deleting the ext3 and repartitionning that space in 2, on the partition setup screen I notice the 1st partition is already listed as ext3, and the 2nd not. Then I realize it comes from the previous (RH) install. I had not realized that when just selecting a single partition, when I thought ext3 was just a default. The partitioning tool recognizes the existing file system on that partition and shows it. The 2nd partition didn't have the start of a new partition... maybe the partitioning tool should overwrite the beginning of a partion when creating one. Hmm, no, that wouldn't work because creating partitions is first only done in memory. Then partition objects in memory should probably be initialized as having no fs on them, instead of looking up the disk. Or, maybe better, they could be initialized from disk only if the fs size matches (or maybe is smaller than) the new partition, and maybe offer to resize2fs to the partition size if it was smaller than the new partition ? Now if my original single-partition-over-RH had gone throught the reboot stage, I may surely have ended up with a strange install. And Well, you have to mark the partition as to be formated. I've assimilated this by now ;), but for some reason it did not seem intuitive to me when doing this first install with d-i. I'll look at the latest version, and see if I still feel some needed improvements in this area. - Now when I decide to split the existing partition in 2, but do not realize I must explicitely select format as ext3, since my partition already appears as having ext3 selected (I thought), and go on, I'm brought back to the main menu on the next step, and requesting to install the base system brings me back there again almost instantly. Oh, hold on. So you used the new tool. So you didn't select format as ext3. But what did you select instead? dont touch ? Because if you choose nothing at all, you shouldn't have been able to assign a mount point at all. I suppose I used the default choice, thinking the partitionner was by default suggesting to put an ext3 fs on the 1st partition I created (which could have been a reasonable suggestion), whereas it was telling me something different - see above. - Selecting French as the keyboard layout after reboot, I do not have time to see the keymap name, and subsequent error message, before the next dialog screen. And I end up with a querty-looking layout. Can you check if this has been fixed? I think it has, and beta3 was correct here. Regards, -- Yann Dirson [EMAIL PROTECTED] http://www.alcove.com/ Senior Free-Software Consultant Consultant senior en Logiciels Libres Debian developer ([EMAIL PROTECTED])Développeur Debian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248998: [avl@planet.nl: Re: INSTALL REPORT]
- Forwarded message from [EMAIL PROTECTED] - From: [EMAIL PROTECTED] Subject: Re: INSTALL REPORT Date: Wed, 26 May 2004 20:56:10 +0200 To: Martin Michlmayr [EMAIL PROTECTED] X-Mailer: Pegasus Mail for Windows (v4.01) X-Spam-Status: No, hits=-4.7 required=5.0 tests=BAYES_00,NO_REAL_NAME autolearn=no version=2.63 Hello Martin, Everything is working fine now. I installed this with trail and error (learing by doing). I first worked mostly with Windows :-( Some questions i do not understand 100%. Sorry, not yet enough linux experience :-) On 25 May 2004 at 10:30, Martin Michlmayr wrote: * [EMAIL PROTECTED] [EMAIL PROTECTED] [2004-05-14 14:04]: Machine: shuttle an50r motherboard amd64 with samsung sata drive Did you use those disk in SATA or in legalcy (parallel) mode? I don't know i changed nothing on my bios and changed nothing on the default installation beta4 for my harddisk. Configure network HW: [E] FORECDETH module not loaded at boot i added forcedeth to /etc/modules Can you try the image from http://gluck.debian.org/cdimage/testing/sarge_d-i/ and see if they recognize this network card? The network card is now working. Can you try both kernel 2.4 and kernel 2.6 (boot with linux and linux26; btw, do you not have a CD drive or why did you boot from disk?) I could not find a working cd, and then i found this http://www.debianhelp.org/modules.php?op=modloadname=Newsfile=articlesid=329 6mode=threadorder=0thold=0 I saw beta and take this because i had a new motherboard. Mount partitions: [E] I changed grub because it points to /dev/hde and i edited fstab on an other machine because i could not change it on this machine. I'm not sure why you had to change this file. Did it not say /dev/hde originally? No /dev/hda, i think that this is because a sata disk is plugged into a sata interface, not into an ide interface where my cdromplayer is plugged in. fatal server error: no screens found dpkg-reconfigure xserver-xfree86 and it works. How did you choose to install X? Did you use tasksel or something else? Default installation i don't know what tasksel is. -- Thanks Andre' Martin Michlmayr [EMAIL PROTECTED] - End forwarded message - -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#230440: FWD: Re: INSTALL REPORT with 2004-01-09 netinst, failed
As I attempt to do more not-so-uncommon things (with the 2004-01-03 snapshot)... This is very old now can you please try a new image from http://gluck.debian.org/cdimage/testing/sarge_d-i/ and see if that works better? - I initially have a HD with a single ext3 partition + swap (from a previous RH install). If I repartition by deleting the ext3 and repartitionning that space in 2, on the partition setup screen I notice the 1st partition is already listed as ext3, and the 2nd not. Then I realize it comes from the previous (RH) install. I had not realized that when just selecting a single partition, when I thought ext3 was just a default. The partitioning tool recognizes the existing file system on that partition and shows it. The 2nd partition didn't have the start of a new partition... maybe the partitioning tool should overwrite the beginning of a partion when creating one. Hmm, no, that wouldn't work because creating partitions is first only done in memory. Now if my original single-partition-over-RH had gone throught the reboot stage, I may surely have ended up with a strange install. And Well, you have to mark the partition as to be formated. - How about forcing system partitions (/, /usr(/*)?, /var(/*)?) to be formatted, or at least require confirmation ? What happened exactly? You split one partition in two, and then assigned mount points? But you can only assign mount points after choosing the method - e.g. format, or don't touch. Considering the age of your installation report, I think the old partitioning tool was used... we have a newer one now. Can you try to replicate this problem with the new image mentioned above? - Now when I decide to split the existing partition in 2, but do not realize I must explicitely select format as ext3, since my partition already appears as having ext3 selected (I thought), and go on, I'm brought back to the main menu on the next step, and requesting to install the base system brings me back there again almost instantly. Oh, hold on. So you used the new tool. So you didn't select format as ext3. But what did you select instead? dont touch ? Because if you choose nothing at all, you shouldn't have been able to assign a mount point at all. Or, probably better, when destroying a partition, we (cfdisk ?) could ask the user whether to nuke the 1st sectors, to avoid further misdetection. Yeah, maybe a good idea, but see above. But maybe file system detection should not be done after splitting a partition. - Once base packages are unpacked, while setting up lilo, I'm now presented with a textbox containing the devfs name for the disk. If I want to install lilo in another location, it looks like I have to know the devfs path, whereas in the old installer I could choose in a list, which is much more suited to people not knowing devfs This is much better now. - Selecting French as the keyboard layout after reboot, I do not have time to see the keymap name, and subsequent error message, before the next dialog screen. And I end up with a querty-looking layout. Can you check if this has been fixed? Looking at base-config.log, it appears that the selected layout is mac-usb-fr (!). That reminds me of a long-gone issue in console-tools Can you check? - When asked to select (again) an http mirror for downloading packages, 1) my previous selection is not the default, maybe because Yeah, this is a known bug. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: INSTALL REPORT
Processing commands for [EMAIL PROTECTED]: tags 231003 + help Bug#231003: Should include IPv6 support from the beginning Tags were: d-i Tags added: help 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: Install report about localized install
On Mon, Feb 09, 2004 at 12:03:31PM +0100, Christian Perrier wrote: Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]): After reboot (to second-stage), I don't see (czech) accented characters, but some other symbols (like percent, box, average mark, ...) instead of ,,... Some texts are not localized and are showing in english (creating user and mail setup). Exim4 is indeed translated to Czechthat's a bit strange that you don't see translated templates...Miroslav, could you look at this more deeply? I've downloaded today's (20040209) sarge-i386-netinst.iso for sid and there is Exim4 4.30-4 -- almost all messages are translated to Czech. The only English screen is unfortunately the first one, where you choose type of configuration (there happened some rephrasing since my original translation) -- this should be fixed in version 4.30-5. (M. Bauer selected the default option which asks no further questions, so he concluded it's not translated at all.) The accented charcater problem is more worrying. However, it may probably be related to #226200 which was closed on Feb 5th by a base-config upload. I did some test with today's 20040209 netinst sid iso (Base Config 2.08) and indeed, accented characters are broken (see the second screenshot at http://www.debian.cz/~kurem/shots/) -- black boxes shouldn't be there, all characters whith following ` above them are wrong (we use only ' (and wedge and circlet) :-) [ ... common boot messages] termwrap: locale-gen: Generating locales... termwrap: locale-gen: cs_CZ.ISO-8859-2... done termwrap: locale-gen: Generation complete info: Switching console charset mapping to ISO-8859-2 /usr/bin/charset: line 117: /dev/tty: Such device or address doesn't exist [base-config starts ... ] I suppose previous line should be the problem. (The error message was localized (see the first picture), so my reverse translation may not be acurate). I skimmed through the base-config, logged in and tried to get it working. Standard locale was set to POSIX. I suppose we need to load correct (iso-8859-2) font: # echo set SCREEN_FONT=iso02.f16 /etc/console-tools/config # echo set APP_CHARSET_MAP=iso02 /etc/console-tools/config # /etc/init.d/console-screen.sh restart Next, we would like to be able to _type_ accented characters (we can switch to the Czech layout by the Pause key): # echo set convert-meta off /etc/inputrc log in on the next console, run # export LANG=cs_CZ #obvious locale stuff # echo -ne \033(K #so we can see accented chars. (blanks otherwise) # base-config #our testing program and voila! (see the last picture). I'm not quite sure if all these steps are necessary - this is proven setup which inherits itself for generations. -- Miroslav Kure -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report about localized install
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]): Dear list. I am trying new Debian installer (sid_d-i sarge-i386-netinst.iso from 5.2.2004). I choose installation in czech, everything goes ok, but labels in cfdisk are showing only to the first accented character and then disappear. Yes, this is bug #229875 for which Kenshi Muto provided a patch to util-linux After reboot (to second-stage), I don't see (czech) accented characters, but some other symbols (like percent, box, average mark, ...) instead of ,,... Some texts are not localized and are showing in english (creating user and mail setup). The non localized strings are due to missing translation in sarge versions of exim4 and shadow packages. Exim4 is indeed translated to Czechthat's a bit strange that you don't see translated templates...Miroslav, could you look at this more deeply? User creation is done by the shadow package. The czech trnaslation is sitting in #229125 as well as many other debconf translations for this package. The accented charcater problem is more worrying. However, it may probably be related to #226200 which was closed on Feb 5th by a base-config upload. You should check with a more recent daily build, if possible. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report about localized install
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, At 9 Feb 04 11:03:31 GMT, Christian Perrier wrote: After reboot (to second-stage), I don't see (czech) accented characters, but some other symbols (like percent, box, average mark, ...) instead of ~,~,~... Some texts are not localized and are showing in english (creating user and mail setup). The accented charcater problem is more worrying. However, it may probably be related to #226200 which was closed on Feb 5th by a base-config upload. Hmm, I think this isn't covered by #226200. Czech locale is cs_CZ, and validlocale says cs_CZ ISO-8859-2. When charset is ISO-8859-2, termwrap simply runs 'charset G0 iso02' for console setting. I suspect this doesn't suite for Czech. Here are other languages using ISO-8859-2. bs_BA, hr_HR, hu_HU, pl_PL, ro_RO, sk_SK, sl_SI, sr_YU How about these languages? Thanks, - -- Kenshi Muto [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8 http://mailcrypt.sourceforge.net/ iEYEARECAAYFAkAnjWoACgkQQKW+7XLQPLHEZACdETeTFB1nUCdhqh3/J6gfQj6u 4e4AmgL9qRB1zHivXy86a/oYF70++6th =28vF -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report about localized install
On Mon, Feb 09, 2004 at 12:03:31PM +0100, Christian Perrier wrote: Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]): After reboot (to second-stage), I don't see (czech) accented characters, but some other symbols (like percent, box, average mark, ...) instead of ,,... Some texts are not localized and are showing in english (creating user and mail setup). The non localized strings are due to missing translation in sarge versions of exim4 and shadow packages. Exim4 is indeed translated to Czechthat's a bit strange that you don't see translated templates...Miroslav, could you look at this more deeply? Updated translation should be up-to-date as of version 4.30-5 (in unstable now). I'm running on stable (modem...), so I don't know details. I have a report from one guy, that 'dpkg-reconfigure exim suddenly speaks Czech' :-) User creation is done by the shadow package. The czech trnaslation is sitting in #229125 as well as many other debconf translations for this package. Yep. Also translation for dialog buttons (newt) is just a matter of closing bug #227116. The accented charcater problem is more worrying. However, it may probably be related to #226200 which was closed on Feb 5th by a base-config upload. I can remember this problem vaguely (I usualy test only the first stage). I'll beg someone for bandwitch and I'll test some new image tomorrow. -- Miroslav Kure -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report: kernel-image*.deb is missing
Eric Bus [EMAIL PROTECTED] a écrit : | I used apt-get to install kernel-image-2.4.24-1-686. When you get the | LILO (or GRUB) configuration screen, press ALT-F2, Enter (which will | give you an linux prompt). Type 'apt-get install | kernel-image-2.4.24-1-686' (or change 686 to another arch if you're | using a pre-PentiumIII machine). It should download and install the | kernel. I intervene in this thread as I ran into the same problem. First, I had to do a chroot /target before I can run apt-get (or else: error while loading shared libraries). Then, apt-get install kernel-image-2.4.23-1-686 installs and sets up cramfsprogs and initrd-tools, but fails at configuring kernel-image-*. Here is what I get: error reading /lib/modules/2.4.23-1-686/build: No such f. or d. Deleting /lib/same_path/build /usr/sbin/mkinitrd: /dev/fd does not exist Failed to create initrd image Same problem with 2.4.22. For info, I do not have a floppy drive. Next, if I try to continue installation and install lilo, it fails. I can almost read line like modprobe: failed to load vga-stuff but it blinks too quickly. That reminds me of one thing: in early stage of installation (hardware detection), I can read in /var/log/messages insmod ide-detect (this takes some time, a few seconds, although all other insmods are very fast) and is followed by modprobe: failed to load module ide-disk. Could that be unusual/related? Thanks for any help, and regards. -- Daniel Déchelotte http://yo.dan.free.fr/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report: kernel-image*.deb is missing
Eric Bus [EMAIL PROTECTED] a écrit : | I used apt-get to install kernel-image-2.4.24-1-686. When you get the | LILO (or GRUB) configuration screen, press ALT-F2, Enter (which will | give you an linux prompt). Type 'apt-get install | kernel-image-2.4.24-1-686' (or change 686 to another arch if you're | using a pre-PentiumIII machine). It should download and install the | kernel. I intervene in this thread as I ran into the same problem. First, I had to do a chroot /target before I can run apt-get (or else: error while loading shared libraries). Then, apt-get install kernel-image-2.4.23-1-686 installs and sets up cramfsprogs and initrd-tools, but fails at configuring kernel-image-*. Here is what I get: error reading /lib/modules/2.4.23-1-686/build: No such f. or d. Deleting /lib/same_path/build /usr/sbin/mkinitrd: /dev/fd does not exist Failed to create initrd image Same problem with 2.4.22. For info, I do not have a floppy drive. Next, if I try to continue installation and install lilo, it fails. I can read things like modprobe: failed to load vga-stuff but it blinks too quickly. That reminds me of one thing: in early stage of installation (hardware detection), I encountered a modprobe ide-detect failed (or was it ide-disk? Can't remember exactly) Could that be unusual/related? Thanks for any help, and regards. -- Daniel Déchelotte http://yo.dan.free.fr/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report: kernel-image*.deb is missing
On Sat, 7 Feb 2004, Eric Bus wrote: I have the same problem with d-i images from 20040131 and up. But I can install the kernel from tty2. I have no idea why it skips it during base-system-installation. Well - I trried that as well but I'm not clever enough to do it without dpkg-. I tried to ar x a manually grabbed kernel-package and untared it but I was nnot able to boot from this partition. Moreover I tried to copy a knoppix kernel but it failed as well. While fiddling around I noticed that the businesscard iso does not work as Rescue Disc. I hope that this feature will not be left out inn general. Do you have any step by step workaround to get a working kernel? Kind regards Andreas. PS: Please CC me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report: kernel-image*.deb is missing
Well - I trried that as well but I'm not clever enough to do it without dpkg-. I used apt-get to install kernel-image-2.4.24-1-686. When you get the LILO (or GRUB) configuration screen, press ALT-F2, Enter (which will give you an linux prompt). Type 'apt-get install kernel-image-2.4.24-1-686' (or change 686 to another arch if you're using a pre-PentiumIII machine). It should download and install the kernel. Now return to the installer by pressing ALT-F1. You should still see the LILO (or GRUB) configuration window. Press enter to accept the default (if that's ok for you, but for many people it is) and it should install LILO. You can see the progress on the screen when pressing ALT-F3. After LILO completed you should have the option to Finish and reboot. I hope this works :) Btw, LI (and no LO) problems most often occur when you 'change' the kernel without updating LILO. Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report: kernel-image*.deb is missing
On Sun, 8 Feb 2004, Eric Bus wrote: I used apt-get to install kernel-image-2.4.24-1-686. When you get the LILO (or GRUB) configuration screen, press ALT-F2, Enter (which will give you an linux prompt). Type 'apt-get install kernel-image-2.4.24-1-686' (or change 686 to another arch if you're using a pre-PentiumIII machine). It should download and install the kernel. Uhmm - that's a nice feature which I did not expected. I've thought I would have to do some magic because the installation goes to /target and thus I downloaded a kernel-image package and tried manual installation which failed. :-( Now return to the installer by pressing ALT-F1. You should still see the LILO (or GRUB) configuration window. Press enter to accept the default (if that's ok for you, but for many people it is) and it should install LILO. You can see the progress on the screen when pressing ALT-F3. OK, I'll keep this information for the next installation - for the moment I switched to an old woody install cd and upgraded ... Btw, LI (and no LO) problems most often occur when you 'change' the kernel without updating LILO. Sure - but there was nothing to change ... Kind regards Andreas. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report: kernel-image*.deb is missing
Everyone is running into this missing kernel thing. Can someone get a debug trace of base-installer/apt-install and find out why it's failing to install the kernel? -- see shy jo signature.asc Description: Digital signature
Re: Install report: kernel-image*.deb is missing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joey Hess wrote: | Everyone is running into this missing kernel thing. Can someone get a | debug trace of base-installer/apt-install and find out why it's | failing to install the kernel? The machine I used to test the floppy installer will be re-installed tomorrow. I will try to get the logs you requested. I will try to reproduce the bug on a free machine tonight, but maybe it related to specific hardware. Eric -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3-nr1 (Windows XP) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAJoggAzbf6aXcH0sRAiYRAKCdWh5Hx6W2ZB3N03egiwabQWhjXACfcqHp QKSOd9wZF5P5zEhlayTvMM8= =BL0I -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: install report: sid on i386, pure SCSI, part 2
On Thu, 5 Feb 2004 20:51:09 +1000, Andrew Pollock wrote: On Thu, Feb 05, 2004 at 12:31:49AM +0100, Herbert Kaminski wrote: saying: modprobe -k ini9100u . /lib/modules of the initrd does not contain any file with this name, but there is initio.o, and also all other moules loaded in 'loadmodules'. But actually, I do not know how the initrd works ;-) It sounds to me as if something has come unstuck during the initrd creation. Odd that it's detected that it needs to load this module, but failed to add the actual module to the initrd... Found the bug in mkinitrd and filed a bug report for initrd-tools. Herbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report: kernel-image*.deb is missing
I tried d-i image from today (6.2.2004) and noticed that grub and lilo installation failed. The reason is that there was no kernel on the /target at all. When I looked at the apt cache there was no kernel-image* package avialable. I have the same problem with d-i images from 20040131 and up. But I can install the kernel from tty2. I have no idea why it skips it during base-system-installation. Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#218774: main-menu retreiver selection still broken (Re: install report: sid on i386, pure SCSI)
On Wed, Feb 04, 2004 at 11:34:21PM -0500, Joey Hess wrote: Funny, I'd run into this same problem 94 days ago, and I filed a bug then, but forgot about it. This is bug #218774 (main-menu). I'm tempted to fix this bug by putting load-cdrom and load-floppy[1] on the CDROM, dropping load-installer entirly, and removing (or ignoring?) the apparently broken code in main-menu that handles chooing amoung virtual packages that satisfy a dependency. Matt, do you have any thoughts? As far as I can see, you touched this part of main-menu last. No, I don't know why it isn't displaying a menu of packages that satisfy the virtual dependency. I was just fixing a random bug. -- Matt Kraai[EMAIL PROTECTED]http://ftbfs.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: install report: sid on i386, pure SCSI, part 2
On Thu, Feb 05, 2004 at 12:31:49AM +0100, Herbert Kaminski wrote: Booting Knoppix and having a look at the hard disk does not reveal anything suspicious (to me), maybe with one exception: when I mount the /boot/initrd.img-xxx from the hard disk, it contains a file 'loadmodules' with, among other lines, one line saying: modprobe -k ini9100u . /lib/modules of the initrd does not contain any file with this name, but there is initio.o, and also all other moules loaded in 'loadmodules'. But actually, I do not know how the initrd works ;-) It sounds to me as if something has come unstuck during the initrd creation. Odd that it's detected that it needs to load this module, but failed to add the actual module to the initrd... Any thoughts Herbert (Xu)? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: main-menu retreiver selection still broken (Re: install report: sid on i386, pure SCSI)
Here is what's going on. cdrom-detect fails to configure as it cannot find the drive. The user selects anna from the main menu. Anna depends on retriever, a virtual package provided by floppy-retriever, and cdrom-retriever. main-menu needs to configure at least one of these to continue, and it chooses to configure cdrom-retriever. Which depends on cdrom-detect. Around and around we go. :-( If instead the cdrom detect is successful, things work as they are supposed to: anna is run and displays a list of retrievers. Note that since none of the retreivers are menu items, main-manu's satisfy_virtual() does not display a list of them for the user to choose from. Instead it apparently defaults to the package with the highst priority, with an arbitrary tie-breaker that currently favours cdrom-retreiver over floppy-retreiver. -- see shy jo signature.asc Description: Digital signature
Re: install report: sid on i386, pure SCSI
Herbert Kaminski wrote: Hi, trying to install sarge-i386-netinst.iso from http://gluck.debian.org/cdimage/testing/sid_d-i/netinst/i386/20040131/ on a pure SCSI drives me crazy :-] First, the CD does not boot with standard settings, where KNOPPIX boots easily. What is the error message / Exactly where did it fail? Fiddling around with controller and BIOS settings finally gets the system up, What did you change for that? but soon it loops endlessly: after selecting language and keyboard, hardware detection executes and then the CD could not be mounted (as expected after reading the Instalaltion-HOWTO). Next screen says ...failed to find and mount a Debian CD Next screen is Main Menu. Selecting either Detect and mount CD-ROM or Load installer components both restarts hardware detection, this time telling me that it is missing modules 'initio' and '8238too' and I need to load them from a floppy. This continues endlessly. From a shell, I can mount the CDrom_driver floppy (BTW: the HOWTO says I need the SCSI_drivers floppy, but there is none. It would reduce the pain to test the installer somewhat if the HOWTO would suggest the right floppy). Now if I only knew what to do with the udebs on that floppy... googling around did not help at all.. Probably something like switching to console 2 and typing udpkg -i your_missing_scsi_driver.udeb Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: install report - powerbook failure
Matt Kraai wrote: Howdy, Thanks for testing Debian-Installer. On Tue, Feb 03, 2004 at 05:23:06PM -0600, Nicholas Williams wrote: The base system would not install. It says it could not download the package libgcrypt7. I tried both normal and expert installs, I also tried configuring the network settings manually. This is bug 229989. Which is of course, marked as done. If you would like a daily build that actually works, go here: http://gluck.debian.org/cdimage/testing/sid_d-i/netinst/powerpc/daily/ -- see shy jo signature.asc Description: Digital signature
Re: Install Report: Failure - Dell PowerApp Web 100 - Failed to detect scsi controller
Erik Dykema wrote: Everything seems to boot up fine, but the kernel fails to detect the adaptec scsi controller, so the installer gets to the 'Partition Hard Drives' part without any warning and then won't go any further. There is no error message suggesting that hard drives were not detected. We currently have the following situation with netboot installs of unstable debian-installer: - The netboot image needs to download the scsi and ide drivers from the debian archive; they are not included in the image. - By default, d-i uses the versions of the udebs in testing. - In unstable, d-i has switched to the 2.4.24 kernel. The version of d-i in testing uses the 2.4.22 kernel. Therefore, if you want to do a netboot install using the unstable version of d-i, you need to make sure that you tell it to install unstable. This will include looking in unstable for the scsi, ide, and other kernel modules, where it will find the 2.4.24 ones. It will also include installing debian unstable to your hard drive, unless you go back to the mirror configuration step after d-i downloads the rest of itself, and switch it back to using testing. -- see shy jo signature.asc Description: Digital signature
Re: Install Report: Failure - Dell PowerApp Web 100 - Failed to detect scsi controller
Hi- OK, I think i get it, thanks! I was attempting to install the 'testing' distribution, that must be why it didn't work. So the 'fix' for this is to get the 2.4.24 kernel into testing. OR, to build a 'testing' version of d-i. As a side note, I have a question regarding why the netboot images need not contain all the necessary drivers? At their current size (2.1 megs) they are too small to fit onto a floppy disk, so they are mostly used by (perhaps here is where I am wrong?) those doing PXE boots (like me)? On the sizes that we are working with ( 1 - 10 megabytes ) I don't think it would necessarily hurt to include more drivers / modules in the netboot image. Is my thinking missing something / wrong, or is this something that just hasn't been discussed yet? thanks again for your help erik Joey Hess wrote: Erik Dykema wrote: Everything seems to boot up fine, but the kernel fails to detect the adaptec scsi controller, so the installer gets to the 'Partition Hard Drives' part without any warning and then won't go any further. There is no error message suggesting that hard drives were not detected. We currently have the following situation with netboot installs of unstable debian-installer: - The netboot image needs to download the scsi and ide drivers from the debian archive; they are not included in the image. - By default, d-i uses the versions of the udebs in testing. - In unstable, d-i has switched to the 2.4.24 kernel. The version of d-i in testing uses the 2.4.22 kernel. Therefore, if you want to do a netboot install using the unstable version of d-i, you need to make sure that you tell it to install unstable. This will include looking in unstable for the scsi, ide, and other kernel modules, where it will find the 2.4.24 ones. It will also include installing debian unstable to your hard drive, unless you go back to the mirror configuration step after d-i downloads the rest of itself, and switch it back to using testing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install Report: Failure - Dell PowerApp Web 100 - Failed to detect scsi controller
Erik Dykema wrote: OK, I think i get it, thanks! I was attempting to install the 'testing' distribution, that must be why it didn't work. So the 'fix' for this is to get the 2.4.24 kernel into testing. OR, to build a 'testing' version of d-i. Yes, I may see about getting the 2.4.24 kernel into testing eventually. However, if you want to test unstable d-i -- and there's no reason to use the unstable netboot images if you don't -- then you should still pick unstable. As a side note, I have a question regarding why the netboot images need not contain all the necessary drivers? At their current size (2.1 megs) they are too small to fit onto a floppy disk, so they are mostly used by (perhaps here is where I am wrong?) those doing PXE boots (like me)? On the sizes that we are working with ( 1 - 10 megabytes ) I don't think it would necessarily hurt to include more drivers / modules in the netboot image. I think there are some netboot image size limits, though I really don't know. -- see shy jo signature.asc Description: Digital signature
Re: install report: sid on i386, pure SCSI
On Wed, 4 Feb 2004 13:11:39 -0500, Joey Hess wrote: Herbert Kaminski wrote: trying to install sarge-i386-netinst.iso from http://gluck.debian.org/cdimage/testing/sid_d-i/netinst/i386/20040131/ on a pure SCSI drives me crazy :-] What scsi controller please? d-i's CD knows about several common Initio 9100UW (it needs module initio.o) controllers, but the less common ones do still require a driver floppy. I've updated all the docs, which were a bit out of date in this area. Well, not only the docs, the floppy images I downloaded from links on the D-I homepage two days ago contain modules for version 2.4.22, whereas 2.4.24 is needed. Consequently, trying to load the module initio.o manually returns an error message. BTW thanks to Thiemo Seufer for telling me what to do with udebs :-) In Load Installer Components, you pick Fetch modules from a floppy from the little menu that appears after the hardware detection. Sorry, there is no little menu after hardware detection. I immediately get the screen titled [!!] Detecting hardware and loading kernel modules that says Your installation CD-ROM couldn't be mounted.This probably... ...Try again to mount the CD-ROM? Selecting Yes just repeats this screen, selecting No displays the next screen Failed to find and mount a Debian CD. The only choice Continue gets me back into the main menu where I could select Load installer components which starts HW detection again. The second time around, I get some more detailed information: modules initio and 8139too are missing (if I understand D-I correctly by now, priorty has been changed). But then this loops endlessly. Typing net at the boot prompt yesterday got me further up to the reboot before it failed too. Unfortunately, I was not able to reproduce this today, so I will try to describe this from memory in a separate report. Herbert -- Herbert Kaminski D-26122 Oldenburg Tel. +49-441-5090133 Fax -9558939 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: install report: sid on i386, pure SCSI
Herbert Kaminski wrote: Well, not only the docs, the floppy images I downloaded from links on the D-I homepage two days ago contain modules for version 2.4.22, whereas 2.4.24 is needed. The prominant links on the d-i home page are prominantly marked as being for for beta2 of the debian installer, and will not go with daily builds of the CD images. The section on daily builds includes links to daily built floppy images such as mine. You cannot mix these two types of images. In Load Installer Components, you pick Fetch modules from a floppy from the little menu that appears after the hardware detection. Sorry, there is no little menu after hardware detection. I immediately get the screen titled [!!] Detecting hardware and loading kernel modules that says Your installation CD-ROM couldn't be mounted.This probably... ...Try again to mount the CD-ROM? Selecting Yes just repeats this screen, selecting No displays the next screen Failed to find and mount a Debian CD. The only choice Continue gets me back into the main menu where I could select Load installer components which starts HW detection again. The second time around, I get some more detailed information: modules initio and 8139too are missing (if I understand D-I correctly by now, priorty has been changed). Yes, and right after that you will get the little menu that I alluded to. But then this loops endlessly. I have no idea what you are describing here. -- see shy jo signature.asc Description: Digital signature
Re: install report: sid on i386, pure SCSI
On Wed, 4 Feb 2004 16:51:08 -0500, Joey Hess wrote: Sorry, there is no little menu after hardware detection. I immediately get the screen titled [!!] Detecting hardware and loading kernel modules that says Your installation CD-ROM couldn't be mounted.This probably... ...Try again to mount the CD-ROM? Selecting Yes just repeats this screen, selecting No displays the next screen Failed to find and mount a Debian CD. The only choice Continue gets me back into the main menu where I could select Load installer components which starts HW detection again. The second time around, I get some more detailed information: modules initio and 8139too are missing (if I understand D-I correctly by now, priorty has been changed). Yes, and right after that you will get the little menu that I alluded to. Sorry, no little menu, but the screen saying my CD could not be mounted. This is the loop: Main Menu (Load Installer components) HW detection Unable to load some modules Your installation CD could not be mounted Failed to find and mount a Debian CD-ROM Main Menu (Detect and mount CD-ROM) Or, exactly the same except for the starting point: Main Menu (Detect and mount CD-ROM) HW detection Unable to load some modules Your installation CD could not be mounted Failed to find and mount a Debian CD-ROM Main Menu (Detect and mount CD-ROM) I have no idea what you are describing here. I hope the description above makes it clear now. Cold it be that the installer thinks this box got no floppy drive? Admittedly, I first also tried to mount /dev/floppy0, and it took me a while to find out that I should use /dev/floppy/0 (sorry, no prior experience with this new stuff). Herbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
main-menu retreiver selection still broken (Re: install report: sid on i386, pure SCSI)
Herbert Kaminski wrote: On Wed, 4 Feb 2004 16:51:08 -0500, Joey Hess wrote: Sorry, there is no little menu after hardware detection. I immediately get the screen titled [!!] Detecting hardware and loading kernel modules that says Your installation CD-ROM couldn't be mounted.This probably... ...Try again to mount the CD-ROM? Selecting Yes just repeats this screen, selecting No displays the next screen Failed to find and mount a Debian CD. The only choice Continue gets me back into the main menu where I could select Load installer components which starts HW detection again. The second time around, I get some more detailed information: modules initio and 8139too are missing (if I understand D-I correctly by now, priorty has been changed). Yes, and right after that you will get the little menu that I alluded to. Sorry, no little menu, but the screen saying my CD could not be mounted. This is the loop: Main Menu (Load Installer components) HW detection Unable to load some modules Your installation CD could not be mounted Failed to find and mount a Debian CD-ROM Main Menu (Detect and mount CD-ROM) Or, exactly the same except for the starting point: Main Menu (Detect and mount CD-ROM) HW detection Unable to load some modules Your installation CD could not be mounted Failed to find and mount a Debian CD-ROM Main Menu (Detect and mount CD-ROM) Funny, I'd run into this same problem 94 days ago, and I filed a bug then, but forgot about it. This is bug #218774 (main-menu). I'm tempted to fix this bug by putting load-cdrom and load-floppy[1] on the CDROM, dropping load-installer entirly, and removing (or ignoring?) the apparently broken code in main-menu that handles chooing amoung virtual packages that satisfy a dependency. Matt, do you have any thoughts? As far as I can see, you touched this part of main-menu last. -- see shy jo [1] Actually it would be a special late-load-floppy, with a menu-item-number that puts it after load-cdrom. signature.asc Description: Digital signature
Re: Install Report: Success, dell powerapp web 100
Erik Dykema wrote: Everything worked great, with one exception: I setup APT with an http source from my local mirror. Afterwards, it went back to the apt setup screen and didn't say 'You've setup one apt-source, want to setup another?' or anything like that, I had to hit cancel to kick out to the menu and skip to the next step. Thanks for your report. What you've described is a known problem, that will be fixed in the next beta release. -- see shy jo signature.asc Description: Digital signature
Re: Install Report: Failure - Dell PowerApp Web 100 - Failed to detect scsi controller
Erik == Erik Dykema [EMAIL PROTECTED] writes: Erik INSTALL REPORT Debian-installer-version: Feb 3nd Daily, Erik from: http://people.debian.org/~sjogren/d-i/images/daily/ Erik Comments: I am booting with vmlinuz / netboot-initrd.gz from Erik ~sjogren: Erik http://people.debian.org/~sjogren/d-i/images/daily/ I'm trying the same thing on a variety of machines. Erik Everything seems to boot up fine, but the kernel fails to Erik detect the adaptec scsi controller, so the installer gets to Erik the 'Partition Hard Drives' part without any warning and Erik then won't go any further. There is no error message Erik suggesting that hard drives were not detected. I see it too, with IDE. The root filesystem just doesn't have any of the ide modules for some reason. Erik Note that the hard drive IS detected in the netboot CD-ROM Erik image today (see previous install report), and that they Erik used to be detected by the netboot image (see my install Erik report dated 1/12/04 , this is the exact same machine). Yes, it used to work last week for me too. Cheers, Kenny. -- Desktop Services Team, EUCS. University of Edinburgh, Scotland. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: install report - powerbook failure
Howdy, Thanks for testing Debian-Installer. On Tue, Feb 03, 2004 at 05:23:06PM -0600, Nicholas Williams wrote: The base system would not install. It says it could not download the package libgcrypt7. I tried both normal and expert installs, I also tried configuring the network settings manually. This is bug 229989. -- Matt Kraai[EMAIL PROTECTED]http://ftbfs.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install Report - Failure to detect SCSI Adaptec AIC-7892a
Hi- I was / am using the daily builds here: http://people.debian.org/~sjogren/d-i/images/daily/ I just download the kernel and initrd as I am using pxelinux to boot everything off the network. Are these images no longer maintained / fixed? Erik Joey Hess wrote: Erik Dykema wrote: I have been testing the daily builds almost every weekday since at least december, so far progress has continued to the point where i can get almost all the way through the installer :) However in the past few days the installer has failed to detect the scsi card in my machine, which seems to be a big step backwards. It's a Dell PowerApp Web 100 1U server. The installer stops on the 'Partition Hard Disk' step, and won't go any further. I have checked dmesg and the usual lines where it picks up on the scsi controller are gone. Which set of daily builds are you using? There are two sets of CD images, as explained on our website, the set that uses the version of d-i in testing, and the set that uses the version of d-i in unstable. The former is liklely to be broken right now, but I hope that the latter will work. Make sure the url you download the CD image from has sid_d-i in it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install Report - Failure to detect SCSI Adaptec AIC-7892a
Erik Dykema wrote: I have been testing the daily builds almost every weekday since at least december, so far progress has continued to the point where i can get almost all the way through the installer :) However in the past few days the installer has failed to detect the scsi card in my machine, which seems to be a big step backwards. It's a Dell PowerApp Web 100 1U server. The installer stops on the 'Partition Hard Disk' step, and won't go any further. I have checked dmesg and the usual lines where it picks up on the scsi controller are gone. Which set of daily builds are you using? There are two sets of CD images, as explained on our website, the set that uses the version of d-i in testing, and the set that uses the version of d-i in unstable. The former is liklely to be broken right now, but I hope that the latter will work. Make sure the url you download the CD image from has sid_d-i in it -- see shy jo signature.asc Description: Digital signature
Bug#230440: FWD: Re: INSTALL REPORT with 2004-01-09 netinst, failed
Package: installation-reports The following installation report was posted to debian-boot, and, according to my records, never followed up on. I am putting it in the BTS so it will not be lost. - Forwarded message from Yann Dirson [EMAIL PROTECTED] - From: Yann Dirson [EMAIL PROTECTED] Date: Mon, 12 Jan 2004 16:41:51 +0100 To: [EMAIL PROTECTED] Subject: Re: INSTALL REPORT with 2004-01-09 netinst, failed As I attempt to do more not-so-uncommon things (with the 2004-01-03 snapshot)... - I initially have a HD with a single ext3 partition + swap (from a previous RH install). If I repartition by deleting the ext3 and repartitionning that space in 2, on the partition setup screen I notice the 1st partition is already listed as ext3, and the 2nd not. Then I realize it comes from the previous (RH) install. I had not realized that when just selecting a single partition, when I thought ext3 was just a default. Now if my original single-partition-over-RH had gone throught the reboot stage, I may surely have ended up with a strange install. And indeed the nc binary I had noticed, as well as the __libc_stack_end issues probably derive from that. - Maybe the partition-setup screen could emphasize this issue ? - How about forcing system partitions (/, /usr(/*)?, /var(/*)?) to be formatted, or at least require confirmation ? - Is it really a good idea to use those programs just installed before rebooting ? - Now when I decide to split the existing partition in 2, but do not realize I must explicitely select format as ext3, since my partition already appears as having ext3 selected (I thought), and go on, I'm brought back to the main menu on the next step, and requesting to install the base system brings me back there again almost instantly. Only by looking at syslog I finally notice a read beyond end of device attempt, which finally enlighten me on what's going on. - the user should be notified of such errors by an error box. - What about forcing the user to reformat such partitions, which we can decide must be invalid because they just reuse an existing block ? Or, probably better, when destroying a partition, we (cfdisk ?) could ask the user whether to nuke the 1st sectors, to avoid further misdetection. - Once base packages are unpacked, while setting up lilo, I'm now presented with a textbox containing the devfs name for the disk. If I want to install lilo in another location, it looks like I have to know the devfs path, whereas in the old installer I could choose in a list, which is much more suited to people not knowing devfs BTW, is it wise at all to use devfs, which is tagged as OBSOLETE in 2.6 !? - Selecting French as the keyboard layout after reboot, I do not have time to see the keymap name, and subsequent error message, before the next dialog screen. And I end up with a querty-looking layout. Looking at base-config.log, it appears that the selected layout is mac-usb-fr (!). That reminds me of a long-gone issue in console-tools debconf settings. Is it possible that some old config-scripts/templates are kept around ? Just after that, I get KDGKBENT at index 128 in table 8: invalid argument, failed to dump keymap and not loading keymap messages, which may explain why I still have a qwerty layout. In the meantime, I was asked to enter the root password... and did that using the qwerty layout, which is sure to give me an unretrievable password when I change back to the correct layout (ie. fr-pc). If then I attempt to loadkeys fr-pc it works fine, but if I install-keymap fr-pc I get the same error messages. - When asked to select (again) an http mirror for downloading packages, 1) my previous selection is not the default, maybe because of 2) the country names being listed in english, despite all other text being correctly in french. However, the proxy information was correctly memorized. Regards, -- Yann Dirson [EMAIL PROTECTED] http://www.alcove.com/ Technical support managerResponsable de l'assistance technique Senior Free-Software Consultant Consultant senior en Logiciels Libres Debian developer ([EMAIL PROTECTED])Développeur Debian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] - End forwarded message - -- see shy jo signature.asc Description: Digital signature
Re: Install Report - Failure to detect SCSI Adaptec AIC-7892a
On Fri, Jan 30, 2004 at 09:09:33AM -0500, Erik Dykema wrote: However in the past few days the installer has failed to detect the scsi card in my machine, which seems to be a big step backwards. It's a Dell PowerApp Web 100 1U server. The installer stops on the 'Partition Hard Disk' step, and won't go any further. I have checked dmesg and the usual lines where it picks up on the scsi controller are gone. I think this might have something to do with the new kernel. Previous attempts at installation got past this point, but they were .22 In bug 230344, I reported that anna downloaded an incompatible md-modules package. Would you please check to see if it downloaded an incompatible modules package by looking in /var/lib/dpkg/status? -- Matt Kraai[EMAIL PROTECTED]http://ftbfs.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report
Quoting Andreas Tille ([EMAIL PROTECTED]): I tried the German installation and I think I found only one not yet translated screen - so thanks to all the translators as well. Which one? Damn - I forgot it because I've thought there would be a tool which shows untranslated stuff, but it's no problem I'll do a further install in the next couple of days and will report it. Well, we have a tool for translators for checking unstranslated stuff, but there are some cases where, even if the string is translated, the translations is not shown by debconf. So, this is why you may be asked about what you found. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report
On Fri, 16 Jan 2004, Christian Perrier wrote: Well, we have a tool for translators for checking unstranslated stuff, but there are some cases where, even if the string is translated, the translations is not shown by debconf. So, this is why you may be asked about what you found. I hereby promise to write it down on my next install which will be next week or the week after the next week. Kind regards Andreas. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report
On Fri, 16 Jan 2004, Steve Langasek wrote: severity 226742 grave Thanks for adjusting this and sharing my opinion. BTW, I had the same observation that in the first install process the keyboard was adjusted fine and after the reboot changing the keymap failed. Kind regards Andreas. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: install report: successful install on iBook
Quoth Thorsten Sauter [EMAIL PROTECTED]: * Michael Rex [EMAIL PROTECTED] [2004-01-14 19:30]: | Booting from image didn't work, like all other images I tried before. why not? It's working fine for me. I just checked an image yesterday and it boots. The image I tested before, built on 09.01.04, didn't work. In fact, all the images from different distributions that I've tried before didn't boot on my new iBook G4, but this seems to be solved by now. Bye, Michael -- A computer lets you make more mistakes faster than any invention in human history, with the possible exceptions of handguns and tequila. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report
I tried the German installation and I think I found only one not yet translated screen - so thanks to all the translators as well. Which one? Damn - I forgot it because I've thought there would be a tool which shows untranslated stuff, but it's no problem I'll do a further install in the next couple of days and will report it. Kind regards Andreas. PS: I'm not subscribed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report
On Wed, 14 Jan 2004 Christian Perrier wrote: This is a known console-data bug...not BTS available to me currently but it is easy to find. Yes, I found it immediately after my posting to this list: #226742. The problem is that I think it should be of RC priority if we would not like to leave all people with non-EN keyboards alone. Please comment on this whether I'm overreacting and perhaps some knowledgeable person could find a fix, because it smells not very complicated for a person who is involved. We just should make sure that this will be fixed before release! Kind regards Andreas. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report
2. A more serious problem is that the keymap was not set correctly. I verified this by dpkg-reconfigure console-data (selected: qwertz / German / Standard / latin1 - no dead keys) and got the following stderr output: Looking for keymap to install: de-latin1-nodeadkeys KDGKBENT at index 128 in table 0: Invalid argument Failed to dump keymap! This might be because your console cannot be opened. Perhaps you don't have video card, are connected via the serial console or ssh. Not loading keymap! This is a real bug which should be fixed. The same here. At the first boot this error message also shows up very quickly, but then the next dialog (whiptail) screen covers the error. So I'm actually not sure if it is the exact same error. However, I believe that /var/log/base-config.log is a transcript of this and there I have this error. Needless to say that I have very well a VGA card attached and am logged in via normal keyboard. -- Try Linux 2.6 from BitKeeper for PXA2x0 CPUs at http://www.mn-logistik.de/unsupported/linux-2.6/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report
Andreas Tille wrote: 1. I selected testing as distribution. In this case it makes no sense to include security.debian.org into source.list. I would include a check here whether the distribution is stable and if not security should be left out here. The installer does make that check for unstable, but since testing does not get security updates even as fast as unstable, I made it leave the security lines in for testing. If you're very lucky, security updates from unstable may have newer versions that what is in testing, and so you'd get an update. Failing that, at least this should let you use apt to downgrade to the fixed version in stable. 2. A more serious problem is that the keymap was not set correctly. I verified this by dpkg-reconfigure console-data (selected: qwertz / German / Standard / latin1 - no dead keys) and got the following stderr output: Looking for keymap to install: de-latin1-nodeadkeys KDGKBENT at index 128 in table 0: Invalid argument Failed to dump keymap! This might be because your console cannot be opened. Perhaps you don't have video card, are connected via the serial console or ssh. Not loading keymap! This is a real bug which should be fixed. Please file a bug report on console-data. -- see shy jo signature.asc Description: Digital signature
Re: Install report
Quoting Andreas Tille ([EMAIL PROTECTED]): 2. A more serious problem is that the keymap was not set correctly. I verified this by dpkg-reconfigure console-data (selected: qwertz / German / Standard / latin1 - no dead keys) and got the following stderr output: Looking for keymap to install: de-latin1-nodeadkeys KDGKBENT at index 128 in table 0: Invalid argument Failed to dump keymap! This might be because your console cannot be opened. Perhaps you don't have video card, are connected via the serial console or ssh. Not loading keymap! This is a known console-data bug...not BTS available to me currently but it is easy to find. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report
Quoting Andreas Tille ([EMAIL PROTECTED]): I tried the German installation and I think I found only one not yet translated screen - so thanks to all the translators as well. Which one? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report
On Wed, Jan 14, 2004 at 12:01:50PM +0100, Andreas Tille wrote: at first thanks for all your fine work at d-i. I never installed a Debian box so easy and so fast as with http://gluck.debian.org/cdimage/testing/netinst/i386/daily/sarge-i386-businesscard.iso (downloaded today size = 38535168 time = 2004-01-11 23:17). I tried the German installation and I think I found only one not yet translated screen - so thanks to all the translators as well. Only some minor issues could be solved better: 1. I selected testing as distribution. In this case it makes no sense to include security.debian.org into source.list. I would include a check here whether the distribution is stable and if not security should be left out here. I would prefer to always offer security.d.o (and default to yes) regardless of what distro is being installed. For one thing, users may install from the beta while sarge==testing, and want to use security updates afterwards once it becomes stable, and having this already in sources.list may be an important reminder to some admins. Cheers, -- Steve Langasek postmodern programmer pgp0.pgp Description: PGP signature
Re: install report: successful install on iBook
* Michael Rex [EMAIL PROTECTED] [2004-01-14 19:30]: | Booting from image didn't work, like all other images I tried before. why not? It's working fine for me. | Is http://people.debian.org/cdimage/testing/sid_d-i/netinst/powerpc/daily/ | the right place to get official daily builds? If so I'll check an image | from there to see if the booting issue is finally solved. it's ok Bye Thorsten signature.asc Description: Digital signature
Re: Install report
On Wed, 14 Jan 2004, Steve Langasek wrote: I would prefer to always offer security.d.o (and default to yes) regardless of what distro is being installed. For one thing, users may install from the beta while sarge==testing, and want to use security updates afterwards once it becomes stable, and having this already in sources.list may be an important reminder to some admins. This makes sens, but only if sarge would be offered in the menu. Moreover I wonder if a list of distributions would make sense while the stablest has the highest priority (via a generated preferences file). This auto generated preferences files has the additional advantage that beginners learn to know that this feature exists. Kind regards Andreas. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report
On Wed, 14 Jan 2004, Joey Hess wrote: Please file a bug report on console-data. I checked this immediately after sending my first mail and found #226742. I added my observation and the opinion that Severity normal is to low in this case. I'm not an installer expert but from a installer point of view I would make it RC because many boxes end up unusable from a beginners point of view. Kind regards Andreas. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: INSTALL REPORT with 2004-01-09 netinst, failed
On Mon, Jan 12, 2004 at 12:46:01PM +0100, ydirson wrote: Comments/Problems: Partition hard drives: if I just follow the steps lineraly, no problem. At first, I had hit cancel at some point before (have to check and reproduce), and the HD selection menu was incomplete (did not mention the probbedname of the drive, only the devfs name, and no terminate choice). When selecting the drive, all I could see was the blue background - could Ctrl-C out of it, but could not achieve partitionning at all. I could narrow the problem, here are the steps to reproduce. You'll need a broken mirror for this to work (at least a mirror with not all of the files required to download the initial packages): - when 1st asked to select a mirror, enter informations manually to point to your local incomplete mirror (FWIW there is a proxy between the test machine and the mirror). - when the download step fails, go back to mirror selection (note: we have here Z choices go back and continue, both of which lead into the main menu to the next step, despite the error). - then select a valid one (I use ftp2.de.d.o) - download completes fine, and the list of discs to partition is presented, featuring the problem described above I could find nothing obviously alarming on this subject in syslog, although there are many broken dependency reported all around. I saved the syslog through nc (hopefully installed by a previous run on the target HD, kudos to you for having put it here ;) Syslog filtered for partition reads the following - full syslog available on request: [...] Jan 12 13:02:25 (none) user.debug main-menu[227]: DEBUG: search for package resolving mounted-partitions, dependency from base-installer Jan 12 13:02:25 (none) user.info main-menu[227]: INFO: broken dependency: debootstrap-udeb to mounted-partitions Jan 12 13:02:25 (none) user.info main-menu[227]: INFO: Falling back to the package description for di-utils-partitioner [...] Jan 12 13:02:25 (none) user.debug main-menu[227]: DEBUG: Menu item 'di-utils-partitioner' selected Jan 12 13:02:25 (none) user.debug main-menu[227]: DEBUG: configure di-utils-partitioner, status: 2 Jan 12 13:02:25 (none) user.warn main-menu[227]: WARNING **: Unable to set title for di-utils-partitioner. HTH, -- Yann Dirson [EMAIL PROTECTED] http://www.alcove.com/ Technical support managerResponsable de l'assistance technique Senior Free-Software Consultant Consultant senior en Logiciels Libres Debian developer ([EMAIL PROTECTED])Développeur Debian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: INSTALL REPORT with 2004-01-09 netinst, failed
Ah, I forgot to fill some boxes On Mon, Jan 12, 2004 at 12:46:01PM +0100, ydirson wrote: Memory: 192MB Root Size/partition table: single ~9GB root, 512M swap And to mention yet other problems: - the items in the initial language menu all start with choose this or a translation of it, which makes it impossible to quickly jump to a particular language with one keystroke, as was possible in old installer - in the list of country to select mirrors from (and possibly other lists), when using french as a language, the coutries are not sorted according to their translation, but appear to be sorted by their english name, which is quite awkward - in the step where one assigns fstype/mountpoints to partitions, when one selects a swap partition, and just validates current choice for fstype, the swap partiton is assigned a mountpoint matching the last mountpoint assigned (eg. /, which then causes an error because of duplicate / being found) -- Yann Dirson [EMAIL PROTECTED] http://www.alcove.com/ Technical support managerResponsable de l'assistance technique Senior Free-Software Consultant Consultant senior en Logiciels Libres Debian developer ([EMAIL PROTECTED])Développeur Debian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: INSTALL REPORT with 2004-01-09 netinst, failed
Quoting Yann Dirson ([EMAIL PROTECTED]): - the items in the initial language menu all start with choose this or a translation of it, which makes it impossible to quickly jump to a particular language with one keystroke, as was possible in old installer I've proposed a new prospective languagechooser package (#226575): http://www.perrier.eu.org/debian/packages/languagechooser.tar.gz Screenshot at http://www.perrier.eu.org/debian/debian-installer/new-languagechooser.png It allows what you want as all choices are prefixed by the ISO language code. This package waits for a parallel countrychooser to be written. - in the list of country to select mirrors from (and possibly other lists), when using french as a language, the coutries are not sorted according to their translation, but appear to be sorted by their english name, which is quite awkward Denis, do you have an idea about this one ? - in the step where one assigns fstype/mountpoints to partitions, when one selects a swap partition, and just validates current choice for fstype, the swap partiton is assigned a mountpoint matching the last mountpoint assigned (eg. /, which then causes an error because of duplicate / being found) Hm. Bug report needed, probably. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: INSTALL REPORT with 2004-01-09 netinst, failed
As I attempt to do more not-so-uncommon things (with the 2004-01-03 snapshot)... - I initially have a HD with a single ext3 partition + swap (from a previous RH install). If I repartition by deleting the ext3 and repartitionning that space in 2, on the partition setup screen I notice the 1st partition is already listed as ext3, and the 2nd not. Then I realize it comes from the previous (RH) install. I had not realized that when just selecting a single partition, when I thought ext3 was just a default. Now if my original single-partition-over-RH had gone throught the reboot stage, I may surely have ended up with a strange install. And indeed the nc binary I had noticed, as well as the __libc_stack_end issues probably derive from that. - Maybe the partition-setup screen could emphasize this issue ? - How about forcing system partitions (/, /usr(/*)?, /var(/*)?) to be formatted, or at least require confirmation ? - Is it really a good idea to use those programs just installed before rebooting ? - Now when I decide to split the existing partition in 2, but do not realize I must explicitely select format as ext3, since my partition already appears as having ext3 selected (I thought), and go on, I'm brought back to the main menu on the next step, and requesting to install the base system brings me back there again almost instantly. Only by looking at syslog I finally notice a read beyond end of device attempt, which finally enlighten me on what's going on. - the user should be notified of such errors by an error box. - What about forcing the user to reformat such partitions, which we can decide must be invalid because they just reuse an existing block ? Or, probably better, when destroying a partition, we (cfdisk ?) could ask the user whether to nuke the 1st sectors, to avoid further misdetection. - Once base packages are unpacked, while setting up lilo, I'm now presented with a textbox containing the devfs name for the disk. If I want to install lilo in another location, it looks like I have to know the devfs path, whereas in the old installer I could choose in a list, which is much more suited to people not knowing devfs BTW, is it wise at all to use devfs, which is tagged as OBSOLETE in 2.6 !? - Selecting French as the keyboard layout after reboot, I do not have time to see the keymap name, and subsequent error message, before the next dialog screen. And I end up with a querty-looking layout. Looking at base-config.log, it appears that the selected layout is mac-usb-fr (!). That reminds me of a long-gone issue in console-tools debconf settings. Is it possible that some old config-scripts/templates are kept around ? Just after that, I get KDGKBENT at index 128 in table 8: invalid argument, failed to dump keymap and not loading keymap messages, which may explain why I still have a qwerty layout. In the meantime, I was asked to enter the root password... and did that using the qwerty layout, which is sure to give me an unretrievable password when I change back to the correct layout (ie. fr-pc). If then I attempt to loadkeys fr-pc it works fine, but if I install-keymap fr-pc I get the same error messages. - When asked to select (again) an http mirror for downloading packages, 1) my previous selection is not the default, maybe because of 2) the country names being listed in english, despite all other text being correctly in french. However, the proxy information was correctly memorized. Regards, -- Yann Dirson [EMAIL PROTECTED] http://www.alcove.com/ Technical support managerResponsable de l'assistance technique Senior Free-Software Consultant Consultant senior en Logiciels Libres Debian developer ([EMAIL PROTECTED])Développeur Debian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: INSTALL REPORT with 2004-01-09 netinst, failed
Quoting Yann Dirson ([EMAIL PROTECTED]): I won't anwser to all of these. Only those I have a kind of answer or something to add. BTW, is it wise at all to use devfs, which is tagged as OBSOLETE in 2.6 !? I have the same objection. This breaks out from woody AND from next release. The argument for using devfs is that the default kernel for sarge is 2.4. - Selecting French as the keyboard layout after reboot, I do not have time to see the keymap name, and subsequent error message, before the next dialog screen. And I end up with a querty-looking layout. Hm. Have to look at this. I'm not sure I understand properly the problem. - When asked to select (again) an http mirror for downloading packages, 1) my previous selection is not the default, maybe because of 2) the country names being listed in english, despite all other text being correctly in french. However, the proxy information was correctly memorized. 1) is not because of 2) 2) is because of an outdated french translation in these images, which is corrected in HEAD now 1) is however a problemplease report this as a bug against base-config -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: INSTALL REPORT with 2004-01-09 netinst, failed
On Mon, Jan 12, 2004 at 03:40:07PM +0100, Christian Perrier wrote: [...] - in the list of country to select mirrors from (and possibly other lists), when using french as a language, the coutries are not sorted according to their translation, but appear to be sorted by their english name, which is quite awkward Denis, do you have an idea about this one ? Yes, I will work on it very soon, see http://lists.debian.org/debian-boot/2004/debian-boot-200401/msg00336.html Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: INSTALL REPORT with 2004-01-09 netinst, failed
Yann Dirson wrote: I could find nothing obviously alarming on this subject in syslog, although there are many broken dependency reported all around. I saved the syslog through nc (hopefully installed by a previous run on the target HD, kudos to you for having put it here ;) nc is not included in the base system, you are seeing leakage from some old install by my guess. Syslog filtered for partition reads the following - full syslog available on request: [...] Jan 12 13:02:25 (none) user.debug main-menu[227]: DEBUG: search for package resolving mounted-partitions, dependency from base-installer Jan 12 13:02:25 (none) user.info main-menu[227]: INFO: broken dependency: debootstrap-udeb to mounted-partitions Jan 12 13:02:25 (none) user.info main-menu[227]: INFO: Falling back to the package description for di-utils-partitioner [...] Jan 12 13:02:25 (none) user.debug main-menu[227]: DEBUG: Menu item 'di-utils-partitioner' selected Jan 12 13:02:25 (none) user.debug main-menu[227]: DEBUG: configure di-utils-partitioner, status: 2 Jan 12 13:02:25 (none) user.warn main-menu[227]: WARNING **: Unable to set title for di-utils-partitioner. It seems d-i somehow managed not to download partconf. -- see shy jo signature.asc Description: Digital signature
Re: Install Report - mkinitrd / cciss error at kernel install step
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 fredag 9. januar 2004, 17:35, skrev Erik Dykema: Comments/Problems: 1. Everything seems to install fine excepting the kernel. The red screen comes up and says that the kernel failed. I hit alt-f3 to see what happened, and find the following: I managed to install Skolelinux, with d-i a few days ago. Briefly I did the following: [1]insmod cciss right before choosing what Skolelinux profile to install [2] After first attempt to install kernel fails, edit /target/etc/fstab to use /dev/cciss/c0d0p1 as / partition, did this in chroot /target [3] Install kernel-image. [4] Edit /target/etc/fstab to use the old device as /-partition (not /dev/cciss/c0d0p1), did this in chroot /target [5] In chroot /target mkdir /dev/cciss/disc0 ln -s /dev/cciss/c0d0 /dev/cciss/disc0/disc ln -s /dev/cciss/c0d0p1 /dev/cciss/disc0/part1 then run lilo from Main-menu This works. I'm not sure how correct this way of doing it is, or if it is really stable, but at least I managed to install a new smp-kernel afterwards on this machine, which is a ML350 G3. The machine is not yet in production, so I can't say that this is a stable solution. The next thing is to get the new HP Systems Insight Manager installed, as soon as they release the linux version. So far I have briefly tried to get the Compaq Health driver installed, without success, URL:http://www.sk-tech.net/support/cpqhealth.html There is some bugreport on this machine in the Skolelinux-project, URL:http://bugs.skolelinux.no/show_bug.cgi?id=589 All done in the spirit of looks hairy, but it works. - -- Klaus -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE//9YxhJ+fXyb6R30RAt/WAJ4mzzRDr8dOeFrbCL6XTSrG0NtQJwCeJfvW rWiybB1TRqDmd83t5uPdovc= =DjBW -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install Report - mkinitrd / cciss error at kernel install step
Things that seem curious: Why is mkinitd caring about my hardware devices, doesn't it just need to see the files in /target? mkinitrd needs to build an initrd that will be able to find the real root device after booting. If /target/dev/cciss doesn't exist, mkinitrd has nothing to work from to figure out what the correct device is. IIRC, devfs is not actually used in the target, only in the root; so probably d-i needs to know how to map /dev/cciss/disc0/partX to a non-devfs device name (and make sure this mapped device is available in the target, i.e., MAKEDEV). Ok, I think I understand a little better now. My next question is, I think, how does it get fixed? It looks like Mr. Lovergine had a similar problem in this thread: http://lists.debian.org/debian-boot/2003/debian-boot-200312/msg00605.html Why are there 3 partitions, there are only two in cfdisk (ext2, swap). Unless it counts a few megs of free space as another partition. You seem to have created one primary and one logical (extended) partition. part5 would be the first logical partition in a DOS partition table, and is contained within whichever one of part1 or part2 is the extended partition. Here you are correct as well, it turns out that partition 1 was a 34 gig ext2 partition, and partition 2 was a 1 gig logical partition containing partition 5 which was also 1 gig. I am very curious as to why it is so. This partition setup was created by the autopartition part of the installer, why would it use those logical partition things? It seems a complicated way to do it. thanks again, Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install Report - mkinitrd / cciss error at kernel install step
On Fri, Jan 09, 2004 at 11:35:23AM -0500, Erik Dykema wrote: This is my third install report, apoligies for errors, welcome correction. It is similar but more complete (due to the busybox bug being fixed) than yesterday's with the same kernel install problem. Is there an outstanding bug in mkinitrd / initrd-tools that is causing this? INSTALL REPORT Debian-installer-version: Jan 09 Daily, from http://people.debian.org/~manty/testing/netinst/i386/daily/ uname -a: Linux hpdemo 2.4.22-1-386 #9 Sat Oct 4 14:30:39 EST 2003 i686 unknown Date: Jan 8, 2004, 11:00am Method: sarge-i386-netinst.iso Machine: HP DL360 G3 Processor: 1 Intel Xeon Memory: 1024 mb Root Device: Smart Array 5i/532 w/ 2 36g scsi drives as raid 0+1 array. Root Size/partition table: disk1 ext2 34 gigs disk5 linux swap 1 gig Output of lspci: lspci not found 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] * See prev. report Create file systems:[E] * See prev. report Mount partitions: [E] * See prev. report Install base system:[E] Install boot loader:[ ] Reboot: [ ] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: 1. Everything seems to install fine excepting the kernel. The red screen comes up and says that the kernel failed. I hit alt-f3 to see what happened, and find the following: Selecting ... Unpacking ... Selecting ... Unpacking kernel-image-2.4.386 (from ...) ... Setting up kernel-image-2.4.23-1-386 (2.4.23-1) error reading /lib/modules/2.4.23-1-386/build : No such file or directory Deleting /lib/modules/2.4.23-1-386/build /usr/sbin/mkinitrd: constituant device /dev/cciss/disc0/part1 does not exist Failed to create initrd image. dpkg: error processing kernel-image-2.4.23-1-386 (--configure): subprocess post-installation script returned error exit status 9 etc /dev/cciss is the hardware raid device. ~ # ls -l /dev/cciss/disc0 brw--- 1 root root 104, 0 disc brw--- 1 root root 104, 1 part1 brw--- 1 root root 104, 2 part2 brw--- 1 root root 104, 5 part5 Things that seem curious: Why is mkinitd caring about my hardware devices, doesn't it just need to see the files in /target? mkinitrd needs to build an initrd that will be able to find the real root device after booting. If /target/dev/cciss doesn't exist, mkinitrd has nothing to work from to figure out what the correct device is. IIRC, devfs is not actually used in the target, only in the root; so probably d-i needs to know how to map /dev/cciss/disc0/partX to a non-devfs device name (and make sure this mapped device is available in the target, i.e., MAKEDEV). Why are there 3 partitions, there are only two in cfdisk (ext2, swap). Unless it counts a few megs of free space as another partition. You seem to have created one primary and one logical (extended) partition. part5 would be the first logical partition in a DOS partition table, and is contained within whichever one of part1 or part2 is the extended partition. -- Steve Langasek postmodern programmer pgp0.pgp Description: PGP signature
Re: Install Report - mkinitrd / cciss error at kernel install step
On Fri, Jan 09, 2004 at 02:14:34PM -0500, Erik Dykema wrote: Things that seem curious: Why is mkinitd caring about my hardware devices, doesn't it just need to see the files in /target? mkinitrd needs to build an initrd that will be able to find the real root device after booting. If /target/dev/cciss doesn't exist, mkinitrd has nothing to work from to figure out what the correct device is. IIRC, devfs is not actually used in the target, only in the root; so probably d-i needs to know how to map /dev/cciss/disc0/partX to a non-devfs device name (and make sure this mapped device is available in the target, i.e., MAKEDEV). Ok, I think I understand a little better now. My next question is, I think, how does it get fixed? It looks like Mr. Lovergine had a similar problem in this thread: http://lists.debian.org/debian-boot/2003/debian-boot-200312/msg00605.html I don't have an answer for that, as I haven't worked on that part of the d-i code. Hopefully, someone else can shed some light. Why are there 3 partitions, there are only two in cfdisk (ext2, swap). Unless it counts a few megs of free space as another partition. You seem to have created one primary and one logical (extended) partition. part5 would be the first logical partition in a DOS partition table, and is contained within whichever one of part1 or part2 is the extended partition. Here you are correct as well, it turns out that partition 1 was a 34 gig ext2 partition, and partition 2 was a 1 gig logical partition containing partition 5 which was also 1 gig. I am very curious as to why it is so. This partition setup was created by the autopartition part of the installer, why would it use those logical partition things? It seems a complicated way to do it. No idea, really. The boot partition needs to be a primary partition so that it can be marked bootable, and using logical partitions gives you the flexibility to support more than 4 partitions on the disk, but obviously only 2 real partitions were created... This seems overly complicated to me as well, since you're not likely to want to take space away from your swap partition to make another partition. -- Steve Langasek postmodern programmer pgp0.pgp Description: PGP signature
Re: INSTALL REPORT - Gnome does NOT! load
Daniel Cardenas [EMAIL PROTECTED] writes: According to vorlon on irc, the install code contains no Gnome code, so this is an upstream problem. Tried apt-get install gnome-session, after apt-get different errors were received. Seems like very little of the gnome system was installed. The problem is than tasksel install gnome-core (the meta package for the gnome base) ... but meta-gnome2 has not reached testing yet. So instead of grabbing the new Gnome2.4 it installs a more than 1 year old gnome-core for Gnome1.4. The result is: no gnome-panel, no gnome-session ... no working gnome at all. It should be fixed soon. (This bug is already reported as #218549) Cheers, Sebastien Bacher -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: install report : jan 03 vmware businesscard
Christian Perrier wrote: The screen is occasionnaly not cleaned up before the main menu pops up again : for instance, when running prebaseconfig, getting an error because of network problems while trying to fetch the Release file.the Retrieving window remained behind the main menu when I came back to te main menu. This is a symptom of a program forgetting to stop the progress bar when erroring out. Please file a bug. Configure keyboard does nothing This is because your keyboard is already configured by d-i. First screen of exim-config way too long. Users will probably hit Enter and then won't see the second part...:-( I worked with its maintainer on fixing this around christmas, the fixed version should be uploaded eventually. -- see shy jo signature.asc Description: Digital signature
Re: INSTALL REPORT - Gnome does NOT! load
I know why it worked 10 days ago when I installed. I was following someone else's install instructions at: http://www.pcc-services.com/debian_install.html Thanks Sebastien and Steve for the help and fix. - Daniel Sebastien Bacher wrote: The problem is than tasksel install gnome-core (the meta package for the gnome base) ... but meta-gnome2 has not reached testing yet. So instead of grabbing the new Gnome2.4 it installs a more than 1 year old gnome-core for Gnome1.4. The result is: no gnome-panel, no gnome-session ... no working gnome at all. It should be fixed soon. (This bug is already reported as #218549) Interesting that this perceived easy to fix critical bug was first reported on Oct 31 and took 2 months for a fix. I hope not too many Debian newbies were turned off in this time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report, take 2: alpha businesscard 2004-01-02
On Sun, Jan 04, 2004 at 11:45:02PM -0600, Steve Langasek wrote: So, I figured I'd give this image another go after pulling the SCSI controller out of the machine. The SCSI card happens to be an integrated SCSI/ethernet device, so there was definitely no network configuration happening on this one -- and the netinst image quite persistently let me know that this wasn't going to work, but I continued on anyway to see how far I could get. :) With the qlogic card out, detecting the remaining IDE hard drives worked just fine. When it came time to partition, though, the installer failed miserably. Although the partitioner udeb has a script to tell it which partitioning program to use, and knew that it was supposed to use fdisk for SRM-based systems, fdisk-udeb wasn't installed. Installing the udeb by hand let the partitioning run normally, showing that everything else was being detected correctly. By this point, the ailing IDE drive I'd thrown in for the test was giving me frequent read errors, so I never got through creating a new filesystem; though mounting the existing fs did work when I tested it, and formatting only failed because the hardware balked. I've also tested the kernel-image-2.4.23-1-generic package on this system, and it shows the same problem initializing the SCSI driver as the 2.4.22 kernel on the CD did. I'll continue trying to get to the bottom of that little failure. Oh, I think I've also figured out why /var/log/syslog wasn't created: syslogd failed to start because there was no driver for unix socket support in any of the kernel udebs. The socket-modules udeb is conspicuously absent from pkg-lists/*/alpha, even though it does exist. I'll update this in my local working directory so it can be fixed on the dailies, and commit it as soon as alioth is back. Is there any reason this shouldn't be considered a common package? It seems to be in the list for all i386 and powerpc targets. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
[Fwd: Re: INSTALL REPORT - Gnome does NOT! load]
I have the same or similar issue with the Jan 2nd build. KDE seems to work fine. Gnome error: could not find /usr/bin/gnome-session If I try to run failsafe gnome, I get an error that says the Gnome installation could not be found. I used ReiserFS. I'm some what new to Linux this so pardon the lack of a good template. INSTALL REPORT Debian-installer-version: sarge-i386-businesscard.iso uname -a: Linux debian 2.4.22-1-386 # 9 Sat Oct 4 14:30:39 EST 2003 i686 Date: 01.03.2004 9am Method: Net install from ftp us debian mirror. Machine: home built Processor: Celeron 850 Mhz Memory: 512 Mbytes Root Device: IDE Root Size/partition table: How do you get that info? Output of lspci: intel 815 chipset, nv11, Geforce MX400 Base System Installation Checklist: All o.k. Comments/Problems: Keep up the good work! I'm a programmer from the Microsoft world, so perhaps I can help after I learn a bit. [EMAIL PROTECTED] wrote: INSTALL REPORT Debian-installer-version: 12.30.2003 .ISO ftp.uio.no uname -a: Linux debian. 2.4.22-1-386 #9 Sat Oct 4 14:30:39 EST 2003 i686 GNU/Linux Date: 01.01.2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? Machine: Home build Processor: AMD TH 1.3 GHZ Memory: 256 + 128 Root Device: IDE Root Size/partition table: Device Boot Start End Blocks Id System /dev/hda1 * 1 16 128488+ 83 Linux /dev/hda2 17 908 7164990 83 Linux /dev/hda3 909 957 393592+ 82 Linux swap /dev/hda4 958486531391010f W95 Ext'd (LBA) /dev/hda5 958486531390978+ 83 Linux Output of lspci:00:00.0 Host bridge: Silicon Integrated Systems [SiS] 735 Host (rev 01) 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS 530 Virtual PCI-to-PCI bridge (AGP) 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 00:02.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07) 00:02.3 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07) 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) 00:03.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet (rev 90) 00:11.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 06) 00:11.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 06) 01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1) Base System Installation Checklist: Initial boot worked:[0] Configure network HW: [0] Config network: [0] Detect CD: [0] Load installer modules: [0] Detect hard drives: [0] Partition hard drives: [0] Create file systems:[0] Mount partitions: [0] Install base system:[0] Install boot loader:[0] Reboot: [0] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Gnome does NOT! load, only KDE works. Gnome fails instantly, complaining about some permission in /usr/bin/gnome-session And return me back to gdm. When I manualy fix the permission with chmod 777 it only fails and give no reason and return me back to gdm This installer looks good : ) keep doing the good work! Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. Nvidia drivers should be supported out of bock. Better intigration betwen the installer setup and the X config We give the same information over and over again? Easyer setup of X and gnome/kde. More autodetection X setup sets in the xf86config-4 mouse to be in the USB port, even when I chose psaux in the installer meny. VH Torleif Salte 408 48 008 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: INSTALL REPORT - Gnome does NOT! load
According to vorlon on irc, the install code contains no Gnome code, so this is an upstream problem. Tried apt-get install gnome-session, after apt-get different errors were received. Seems like very little of the gnome system was installed. Daniel Cardenas wrote: I have the same or similar issue with the Jan 2nd build. KDE seems to work fine. Gnome error: could not find /usr/bin/gnome-session If I try to run failsafe gnome, I get an error that says the Gnome installation could not be found. I used ReiserFS. I'm some what new to Linux this so pardon the lack of a good template. INSTALL REPORT Debian-installer-version: sarge-i386-businesscard.iso uname -a: Linux debian 2.4.22-1-386 # 9 Sat Oct 4 14:30:39 EST 2003 i686 Date: 01.03.2004 9am Method: Net install from ftp us debian mirror. Machine: home built Processor: Celeron 850 Mhz Memory: 512 Mbytes Root Device: IDE Root Size/partition table: How do you get that info? Output of lspci: intel 815 chipset, nv11, Geforce MX400 Base System Installation Checklist: All o.k. Comments/Problems: Keep up the good work! I'm a programmer from the Microsoft world, so perhaps I can help after I learn a bit. [EMAIL PROTECTED] wrote: INSTALL REPORT Debian-installer-version: 12.30.2003 .ISO ftp.uio.no uname -a: Linux debian. 2.4.22-1-386 #9 Sat Oct 4 14:30:39 EST 2003 i686 GNU/Linux Date: 01.01.2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? Machine: Home build Processor: AMD TH 1.3 GHZ Memory: 256 + 128 Root Device: IDE Root Size/partition table: Device Boot Start End Blocks Id System /dev/hda1 * 1 16 128488+ 83 Linux /dev/hda2 17 908 7164990 83 Linux /dev/hda3 909 957 393592+ 82 Linux swap /dev/hda4 958486531391010f W95 Ext'd (LBA) /dev/hda5 958486531390978+ 83 Linux Output of lspci:00:00.0 Host bridge: Silicon Integrated Systems [SiS] 735 Host (rev 01) 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS 530 Virtual PCI-to-PCI bridge (AGP) 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 00:02.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07) 00:02.3 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07) 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) 00:03.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet (rev 90) 00:11.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 06) 00:11.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 06) 01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1) Base System Installation Checklist: Initial boot worked:[0] Configure network HW: [0] Config network: [0] Detect CD: [0] Load installer modules: [0] Detect hard drives: [0] Partition hard drives: [0] Create file systems:[0] Mount partitions: [0] Install base system:[0] Install boot loader:[0] Reboot: [0] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Gnome does NOT! load, only KDE works. Gnome fails instantly, complaining about some permission in /usr/bin/gnome-session And return me back to gdm. When I manualy fix the permission with chmod 777 it only fails and give no reason and return me back to gdm This installer looks good : ) keep doing the good work! Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. Nvidia drivers should be supported out of bock. Better intigration betwen the installer setup and the X config We give the same information over and over again? Easyer setup of X and gnome/kde. More autodetection X setup sets in the xf86config-4 mouse to be in the USB port, even when I chose psaux in the installer meny. VH Torleif Salte 408 48 008 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: INSTALL REPORT - Gnome does NOT! load
On Sat, Jan 03, 2004 at 07:50:17PM -0700, Daniel Cardenas wrote: According to vorlon on irc, the install code contains no Gnome code, so this is an upstream problem. I didn't mean to suggest that this was an upstream problem, only that it wasn't an installer problem. This may well be a bug in the Debian gnome-session package, in whatever GNOME task/metapackage you installed, or in gdm for not knowing that GNOME wasn't installed. Knowing more about what packages you selected for installation (and how) would give us a better idea which of the above applies. Tried apt-get install gnome-session, after apt-get different errors were received. Seems like very little of the gnome system was installed. That seems entirely possible. -- Steve Langasek postmodern programmer Daniel Cardenas wrote: I have the same or similar issue with the Jan 2nd build. KDE seems to work fine. Gnome error: could not find /usr/bin/gnome-session If I try to run failsafe gnome, I get an error that says the Gnome installation could not be found. I used ReiserFS. I'm some what new to Linux this so pardon the lack of a good template. INSTALL REPORT Debian-installer-version: sarge-i386-businesscard.iso uname -a: Linux debian 2.4.22-1-386 # 9 Sat Oct 4 14:30:39 EST 2003 i686 Date: 01.03.2004 9am Method: Net install from ftp us debian mirror. Machine: home built Processor: Celeron 850 Mhz Memory: 512 Mbytes Root Device: IDE Root Size/partition table: How do you get that info? Output of lspci: intel 815 chipset, nv11, Geforce MX400 Base System Installation Checklist: All o.k. Comments/Problems: Keep up the good work! I'm a programmer from the Microsoft world, so perhaps I can help after I learn a bit. [EMAIL PROTECTED] wrote: INSTALL REPORT Debian-installer-version: 12.30.2003 .ISO ftp.uio.no uname -a: Linux debian. 2.4.22-1-386 #9 Sat Oct 4 14:30:39 EST 2003 i686 GNU/Linux Date: 01.01.2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? Machine: Home build Processor: AMD TH 1.3 GHZ Memory: 256 + 128 Root Device: IDE Root Size/partition table: Device Boot Start End Blocks Id System /dev/hda1 * 1 16 128488+ 83 Linux /dev/hda2 17 908 7164990 83 Linux /dev/hda3 909 957 393592+ 82 Linux swap /dev/hda4 958486531391010f W95 Ext'd (LBA) /dev/hda5 958486531390978+ 83 Linux Output of lspci:00:00.0 Host bridge: Silicon Integrated Systems [SiS] 735 Host (rev 01) 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS 530 Virtual PCI-to-PCI bridge (AGP) 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 00:02.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07) 00:02.3 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07) 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) 00:03.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet (rev 90) 00:11.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 06) 00:11.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 06) 01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1) Base System Installation Checklist: Initial boot worked:[0] Configure network HW: [0] Config network: [0] Detect CD: [0] Load installer modules: [0] Detect hard drives: [0] Partition hard drives: [0] Create file systems:[0] Mount partitions: [0] Install base system:[0] Install boot loader:[0] Reboot: [0] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Gnome does NOT! load, only KDE works. Gnome fails instantly, complaining about some permission in /usr/bin/gnome-session And return me back to gdm. When I manualy fix the permission with chmod 777 it only fails and give no reason and return me back to gdm This installer looks good : ) keep doing the good work! Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. Nvidia drivers should be supported out of bock. Better intigration betwen the installer setup and the X config We give the same information over and over again? Easyer setup of X and gnome/kde. More autodetection X setup sets in the xf86config-4 mouse to be in the USB port, even when I chose psaux in the installer meny. VH Torleif Salte 408 48 008 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: install report; jan 02 vmware netinst
Joey Hess wrote: base-config priority is still screwed up (foiled again!). Which is just weird. I did 2 installs to my test laptop, one of the same netinst, one of the jan 2 businesscard, and both got the base-config priority right. In vmware, it was medium, and that was a non-default value in questions.dat. It's possible that I somehow entered medium priority in d-i, but I don't remember that. I am running the vmware install again to test. -- see shy jo signature.asc Description: Digital signature
Re: Install report (not successfull, 2nd image of 20031230, i386)
Erich Waelde wrote: Debian-installer-version: 30-Dec-2003 11:11h netinst.iso 2nd build from http://people.debian.org/~manty/testing/netinst/i386/daily/ just to be sure: md5sum sarge-i386-netinst-20031230.2.iso 8d88a368fc2225144b8592d75684 sarge-i386-netinst-20031230.2.iso That's the same as my copy.. to make it short: This image is no good for my box. - network cannot be configured, because ne2k-pci fails to load with unresolved symbols: insmod: unresolved symbol ei_close_Rc8e3042e insmod: unresolved symbol ei_open_R8c9e3b69 insmod: unresolved symbol ethdev_init_R2342cc80 insmod: unresolved symbol ei_interrupr_Rb93d8fa5 insmod: unresolved symbol NS8390_init_Rd79efca9 this worked on the image before. I can't reproduce this, just booted and manually modprobed it and it loaded without problem. I don't have a card to try it with, but all the symbols are resolved. Also tried it with net boot type, same result. The symbols you list as missing are in the 8390 module AFAIK. It sounds as if you got a broken modules.dep somehow and modprobe did not load 8390; but it works here. - ncr53c8xx (scsi) is missing and sym53c8xx is not loaded through the hw detection phase. loading sym53c8xx, sr_mod and sd_mod manually results in the SCSI disks being avaliable, though. this worked on the image before ncr53c8xx is available in the installer initrd after the installer loaded is components from CD. sym53c8xx is part of the debian-installer CD boot initrd, so it should be available the instant the installer boots (and is, in my testing). - booting net still results in the di-utils-devicefiles problem, see my last message I have just verified that di-utils-devicefiles is not in the Packages file anymore. It may have been still when you did your testing, and may still be on mirrors that are *very* slow to update. Anyway, I cannot recommend using the net boot method, as it is laregly untested. I also don't know what it's good for at all, frankly. I have been pondering remmoving it from the netinst CD entirely. - ext3 has vanished from the selection in conf.+mount filesystems Cannot reproduce. ext2, ext3, and reiserfs are all listed, and I have done installs with all of them used for the root filesystem today, using this image. I have successfully installed using this image on two computers a total of 12 times today.. Something went badly wrong, but I cannot find the problems in the image you say you used. Perhaps the CD you burnt is bad, or you accidentially swapped in one from Dec 30th, 2002? ;-) -- see shy jo signature.asc Description: Digital signature
Re: INSTALL REPORT
Martin Michlmayr [EMAIL PROTECTED] writes: What's the status of partman? Is that available for testing already? The packages can be used and finally there is support for i18n. I am going to have better connection to Internet on 6 Jan 2004. On this date I will put the packages on http://lml.bas.bg/~anton/partman. If joey gives me acces to the repository (I am zinoviev AT debian org) I will be able to add partman to the official repository. I hope that partman-auto will be ready before this date. This means that the only missing part (comparingly to the current state) will be LVM. I won't be able to add support for LVM alone but I can work together with someone who understands LVM better than me. What is the best place for partman in the repository? I see two options: 1. directory `partman' with subdirectories for each package as well as subdirectory for the documentation. 2. subdirectory in `tools' for each package and directory `doc/partman' for the documentation. Anton Zinoviev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: INSTALL REPORT
Anton Zinoviev wrote: gives me acces to the repository (I am zinoviev AT debian org) I will be able to add partman to the official repository. I've added you, it might take up to an hour for the change to take effect and you'll need to request a missing password on alioth if you have not already. What is the best place for partman in the repository? I see two options: 1. directory `partman' with subdirectories for each package as well as subdirectory for the documentation. 2. subdirectory in `tools' for each package and directory `doc/partman' for the documentation. #1 sounds right to me. -- see shy jo signature.asc Description: Digital signature
Re: INSTALL REPORT
Robert [EMAIL PROTECTED] writes: Manually HDD partitioning didn't work. cfdisk quit's with an error. Used automatic partitioning. cfdisk can not handle partition tables where the order of the logical partitions in the disk does not follow their numbers. For example when /dev/hda6 is phisicaly before /dev/hda5. In this case cfdisk prints the message FATAL ERROR: Bad logical partition 6: enlarged logical partitions overlap and exits. For such partition tables fdisk can be used instead of cfdisk. fdisk prints the message Partition table entries are not in disk order but has no problems. Anton Zinoviev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: INSTALL REPORT
* Anton Zinoviev [EMAIL PROTECTED] [2003-12-28 00:40]: cfdisk can not handle partition tables where the order of the logical [...] What's the status of partman? Is that available for testing already? -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: INSTALL REPORT
Joey Hess wrote: Robert wrote: Manually HDD partitioning didn't work. cfdisk quit's with an error. Used automatic partitioning. Any chance you can tell us what the error wis? Hmmm... I'am sorry but I can't remember the error message exactly. I know - not a very useful answer... As far as I remember cfdisk could'nt read the partition table and cfdisk was right. The partition table was indeed currupted. It's my testsystem and that's why I descided to give the new installer a try. For me it seems that cfdisk can't deal with currupted partition tables if someone try's to do manual partitioning... Robert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: INSTALL REPORT
Processing commands for [EMAIL PROTECTED]: retitle 224996 Cannot install initrd-tools, UHCI problems Bug#224996: INSTALL REPORT Changed Bug title. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: INSTALL REPORT
Robert wrote: Manually HDD partitioning didn't work. cfdisk quit's with an error. Used automatic partitioning. Any chance you can tell us what the error wis? -- see shy jo signature.asc Description: Digital signature
Re: Install report
Joey Hess [EMAIL PROTECTED] writes: Jukka Neppius wrote: 1. No documents! The page http://www.debian.org/devel/debian-installer/ has a promising link to The Debian-Installer's INSTALLATION HOWTO. Unfortunately it does not give anything. I think you'll find that link is working now. We're still in the process of restoring services after the recent security breach of the Debian servers. Yes it started working soon after I send that message, but now link at above page gives: /debian-installer/doc/INSTALLATION-HOWTO: unknown location - Jukka -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report
Joey Hess [EMAIL PROTECTED] writes: Jukka Neppius wrote: 1. No documents! The page http://www.debian.org/devel/debian-installer/ has a promising link to The Debian-Installer's INSTALLATION HOWTO. Unfortunately it does not give anything. I think you'll find that link is working now. We're still in the process of restoring services after the recent security breach of the Debian servers. I think there should be some kind of README in dists/sid/main/installer-i386/ with one line explanation of every file in it and a link to The Debian-Installer's INSTALLATION HOWTO 5. An old problem: I usually make a 'small' root partition. (currently it should be about 150 MB, my first Linux computer had total 80 MB disk space.) This computer had relatively small disk, so I made only / /usr. I should have made symlinks /var - /usr/var ... I forget that while trying to configure non existing CD, so I run out of disk space. Tasksel did hide the error message so I had to use old reliable dselect. It told immediately what is the problem. Fix was easy. Perhaps installer could check the size of / and if it is small and not all big partition were made, ask user where /var should be moved (same with /usr, /home, /tmp). How exactly did tasksel hide the error message? I am not sure if I remember this correctly. I made selections in tasksel and clicked 'Finish'. Screen flashed and I got selection page again with nothing selected. I got out of it and started dselect. I soon got 'disk full' error. I don't think that having the installer make symlinks would be very good. It would be good if it tried to ensure that the disk sizes were sane, but of course different people's definitions of sane varies in this area. I agree. But warning would be nice. Something like: You have very small /, /usr, /var, /tmp 1. Fix by making new partitions. 2. Repeat this test. 3. Proceed anyway. Hint: for example if your / is too small to contain /var you can: ALT-F2 mkdir /usr/var (or if /var is already created 'mv /var /usr/ ') ln -s /usr/var /var For installation to succeed / should be big enough for everything without its own partition. Result was working system. Network and sound drivers were found automatically. Good deal, you should fill out the installation report template you'll find in /root, and file a proper install report with that template that includes the hardware you installed to so we can track it. I'll do that later. - Jukka -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Install report
Jukka Neppius wrote: 1. No documents! The page http://www.debian.org/devel/debian-installer/ has a promising link to The Debian-Installer's INSTALLATION HOWTO. Unfortunately it does not give anything. I think you'll find that link is working now. We're still in the process of restoring services after the recent security breach of the Debian servers. 2. Guessing name of the first boot diskette was easy. 2. took some time. If first diskette asks for 2. boot floppy, there should be a file bootfloppy2.img (or something like it). Rootfloppy.img would also be good name, but then boot floppy should ask for it. The INSTALLATION-HOWTO makes it much easier, but we do plan to rename these images, particularly the badly named floppy image, in the future. 3. I wanted to install from network. Two boot floppies found network interface from Epox 8K9A71 motherboard. Everything went well until installer wanted to configure CD-drive. Installer refused to believe that there is no CD-drive! I can get debs from local network easier than from CD, so I didn't install a CD drive. I was able to finish installation by selecting next installation step from the menu. After each step installer wanted to configure non existing CD. This is a known problem that's on our list to fix. 4. Keyboard configuration was easy as usual. Unfortunately after first boot Debian had forgotten that I don't have US keyboard. This is a base-config bug, and is fixed in the version of base-config in unstable. I'm not sure if that version of base-config has made it to testing yet, but it will eventually. 5. An old problem: I usually make a 'small' root partition. (currently it should be about 150 MB, my first Linux computer had total 80 MB disk space.) This computer had relatively small disk, so I made only / /usr. I should have made symlinks /var - /usr/var ... I forget that while trying to configure non existing CD, so I run out of disk space. Tasksel did hide the error message so I had to use old reliable dselect. It told immediately what is the problem. Fix was easy. Perhaps installer could check the size of / and if it is small and not all big partition were made, ask user where /var should be moved (same with /usr, /home, /tmp). How exactly did tasksel hide the error message? I don't think that having the installer make symlinks would be very good. It would be good if it tried to ensure that the disk sizes were sane, but of course different people's definitions of sane varies in this area. Result was working system. Network and sound drivers were found automatically. Good deal, you should fill out the installation report template you'll find in /root, and file a proper install report with that template that includes the hardware you installed to so we can track it. -- see shy jo signature.asc Description: Digital signature
Re: install report
On Sun, Nov 30, 2003 at 09:01:25PM -0500, Joey Hess wrote: Before installing debs from the CD it displayed a new progress bar as it checked the size of each udeb. I'm not sure what this was (not cdrom-checker), and it should be a bit clearer what it's doing there. Sounds like the extra progress bar I added to debootstrap a while ago -- basically, what it does is fetching the size for each .deb so it can build up a proper progress bar later. Note that this was there earlier too, there just wasn't a progress bar for it (on a slow link, debootstrap would just hang with a blank screen for several minutes). /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: install report
On Mon, Dec 01, 2003 at 10:29:15AM +0100, Steinar H. Gunderson wrote: On Sun, Nov 30, 2003 at 09:01:25PM -0500, Joey Hess wrote: Before installing debs from the CD it displayed a new progress bar as it checked the size of each udeb. I'm not sure what this was (not cdrom-checker), and it should be a bit clearer what it's doing there. Sounds like the extra progress bar I added to debootstrap a while ago -- basically, what it does is fetching the size for each .deb so it can build up a proper progress bar later. Note that this was there earlier too, there just wasn't a progress bar for it (on a slow link, debootstrap would just hang with a blank screen for several minutes). I noticed that a blank blue screen appears also during fs making. For large disks this is quite annoying. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: install report
On Mon, Dec 01, 2003 at 11:27:21AM +0100, Francesco P. Lovergine wrote: I noticed that a blank blue screen appears also during fs making. For large disks this is quite annoying. Known bug, should be fixed for beta 2. We're a bit unsure as of how to do this best, though. :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: install report
Steinar H. Gunderson wrote: Sounds like the extra progress bar I added to debootstrap a while ago -- basically, what it does is fetching the size for each .deb so it can build up a proper progress bar later. Note that this was there earlier too, there just wasn't a progress bar for it (on a slow link, debootstrap would just hang with a blank screen for several minutes). Where is the template for that progress bar? -- see shy jo signature.asc Description: Digital signature
Re: INSTALL REPORT
Am Mon, den 01.12.2003 schrieb Robert Staudinger um 14:27: INSTALL REPORT Debian-installer-version: 2003-11-29 http://www.soziologie.ch/~steinlin/d-i/powerpc/sarge-powerpc-netinst.iso uname -a: Linux localhost.localdomain 2.4.20-8d_owen_aty128 #1 Wed Jul 16 13:04:19 CEST 2003 ppc ppc ppc GNU/Linux Date: 2003-12-01 12:00 Method: Install from CD Boot off CD Machine: late 2001 iBook2 Processor: G3 600MHz Memory: 384MB Root Device: IBM 40GB ide (not 100% sure) = Partition map (with 512 byte blocks) on '/dev/hda' #:type name length base ( size ) 1: Apple_partition_map Apple 63 @ 1 2: Apple_Bootstrap*untitled 2048 @ 64 ( 1.0M) 3: Apple_UNIX_SVR2 untitled 1024 @ 2112 ( 4.9G) 4: Apple_UNIX_SVR2 swap 1228800 @ 10242112 (600.0M) 5: Apple_UNIX_SVR2 untitled 9248 @ 11470912 ( 31.8G) Device block size=512, Number of Blocks=78140160 (37.3G) DeviceType=0x0, DeviceId=0x0 Drivers- 1: 23 @ 64, type=0x1 2: 36 @ 118, type=0x 3: 21 @ 192, type=0x701 4: 34 @ 246, type=0xf8ff = Want to mount 4: as swap and 5: as / Output of lspci: 00:0b.0 Host bridge: Apple Computer Inc. UniNorth/Pangea AGP 00:10.0 VGA compatible controller: ATI Technologies Inc Rage Mobility M3 AGP 2x (rev 02) 10:0b.0 Host bridge: Apple Computer Inc. UniNorth/Pangea PCI 10:17.0 Class ff00: Apple Computer Inc. KeyLargo/Pangea Mac I/O 10:18.0 USB Controller: Apple Computer Inc. KeyLargo/Pangea USB 10:19.0 USB Controller: Apple Computer Inc. KeyLargo/Pangea USB 20:0b.0 Host bridge: Apple Computer Inc. UniNorth/Pangea Internal PCI 20:0e.0 Class : Apple Computer Inc. UniNorth/Pangea FireWire (rev ff) 20:0f.0 Ethernet controller: Apple Computer Inc. UniNorth/Pangea GMAC (Sun GEM) Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[E] Install boot loader:[ ] Reboot: [ ] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: After selecting the kernel the progress-bar started but the kernel couldn't be installed and the kernel-selection came again. No way to install kernel and continue. This image has a know and fixed bug, that kernel-installer tries to install initrd-tools, which is not on the cd and is not needed by the current powerpc kernels. Unfortunately nobody seems to have a more recent powerpc image around and gluck is still down. You could try the cdrom-udeb-all-none.img. this one should not have this bug. Gaudenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: install report
Am Mon, den 01.12.2003 schrieb Joey Hess um 03:01: Network config found my card, but did not get a dhcp lease from vmware. Probably a problem with my vmware, but this let me experience the oh-so-pleasant path of dhcp failing after a long timeout, and main-menu running it again and again when I piced unrelated items like cdrom-detect (or perhaps rather, increasing debconf priority and re-selecting the failing netcfg-dhcp, after cdrom-detect succeeds). Manual network config succeeded, modulo dvorak keyboard which I had to go back and switch to qwerty first. I put the source tarball of the current status of my netcfg modifications to http://www.soziologie.ch/~steinlin/d-i/netcfg_0.33.tar.gz This version implements the dhcp background idea and combines dhcp and static configuration in one new udeb (netcfg). The old netcfg-static and netcfg-dhcp udebs still exist for custom installers or architectures without dhcp support. The tarball contains some cruft I will remove as soon as I have time for it (editor backups, templates for local testing, test scripts, ...) and lacks all the po files because I accidentally deleted them just before cvs went down :-( I also messed a little bit with the indentation (wich was already messy :-( ) I will have to fix that too. There is still one little bug remaining: If you get a dhcp lease while you are asked if you want to retry, then things go bad..., will fix that soon. btw, what are the authoritative d-i coding standards? there is doc/codingstyle.txt which recommends indentation with spaces, but I know joeyh does not like that. Is there an emacs setting to automate joeyh's style (indentation with tabs, formatting with spaces?) gaudenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: INSTALL REPORT
Andrew Pollock wrote: * The initial net install gave me no option but to download from ftp.au.debian.org, which from Australia is slooow :-( I forget what the bug behind that is, or whether it's being fixed. You can get access to the lists of mirrors by booting with DEBCONF_PRIORITY=medium * The generated LILO configuration is rather minimal and in particular doesn't pause much to let you press Shift to interrupt it I agree that this is annoying, and have filed a bug. * I didn't get a lot of choice in whether or not I was going to get pcmcia-cs installed, and it's pointless on my system That's a debootstrap bug, bug filed. -- see shy jo signature.asc Description: Digital signature
