[Manual] New installer options versus old boot options
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I noticed there are three new installer options. I'd like to add them in the manual. 1) debian-installer/probe/usb=false Is this i386 only? Is this for systems that freeze when USB is probed? Does this option replace the 'nousb' option currently described in: http://d-i.alioth.debian.org/manual/en.i386/ch05s01.html#id2453879 or are they for different situations? 2) hw-detect/start_pcmcia=false Is this i386 only? When should this option be used? Is the procedure described in: http://d-i.alioth.debian.org/manual/en.i386/ch05s01.html#id2453819 still valid? 3) netcfg/use_dhcp=false I guess this is valid for all archs. TIA, FJP -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAipeSgm/Kwh6ICoQRAkTuAKC01tX4HdSZBVjkKrZqqxpmN7jxOgCgqzUs CN8G1dHGyBW/opS0/kGJn0Y= =+pOQ -END PGP SIGNATURE-
Re: [Manual] New installer options versus old boot options
On Sat, Apr 24, 2004 at 18:36 +0200, Frans Pop wrote: 2) hw-detect/start_pcmcia=false Is this i386 only? No. When should this option be used? When you don't want d-i to try to start PCMCIA, because it crashes your computer. This mostly happens when the resource ranges are wrong. It will probably become a medium priority question as well after the string freeze. Is the procedure described in: http://d-i.alioth.debian.org/manual/en.i386/ch05s01.html#id2453819 still valid? You need to put the parameters in /etc/pcmcia/config.opts (not /target) before running the hardware detection step. Then you need to put them in /target as well, after the base installation. There is no PCMCIA configuration part either, it is part of the hardware detection. If you don't need PCMCIA for installing, you can disable it during the installation and then install pcmcia-cs and modify /etc/pcmcia/config.opts afterwards. Hmm... pcmcia-cs is also part of the laptop task which I'm not sure is such a good idea. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Manual] New installer options versus old boot options
Frans Pop wrote: 1) debian-installer/probe/usb=false Is this i386 only? Is this for systems that freeze when USB is probed? Does this option replace the 'nousb' option currently described in: http://d-i.alioth.debian.org/manual/en.i386/ch05s01.html#id2453879 or are they for different situations? Some systems might freeze, I also had a report of a system that disabled the legacy keyboard when usb was probed, but did not really freeze. The nousb thing must be a boot-floppies parameter (I don't think it's a kernel parameter, is it?), and won't work. This is most likely i386 specific, but if we have the wrong module listed for some other arch, maybe needed there too, dunno. 2) hw-detect/start_pcmcia=false Is this i386 only? When should this option be used? If you see a freeze when starting PC card services during hardware detection. Oddly, some report that it says it's skipping the ide-floppy driver and then freezes. That is right before it starts pcmcia, and maybe it does not update the progress bar quite right. This is probably i386 only, at least all reported hangs are on i386 hardware. Is the procedure described in: http://d-i.alioth.debian.org/manual/en.i386/ch05s01.html#id2453819 still valid? This might work, but with d-i you have to do it before the hardware detection pass, so boot in expert mode and run a shell before running hardware detection. 3) netcfg/use_dhcp=false I guess this is valid for all archs. Yes. -- see shy jo signature.asc Description: Digital signature
Re: [Manual] New installer options versus old boot options
On Sat, Apr 24, 2004 at 13:11 -0400, Joey Hess wrote: Oddly, some report that it says it's skipping the ide-floppy driver and then freezes. That is right before it starts pcmcia, and maybe it does not update the progress bar quite right. But it is updated, I see Starting PC card services when I run hw-detect. Is db_progress fully synchronous? This is probably i386 only, at least all reported hangs are on i386 hardware. Yes, you're right, I thought he meant whether it was possible to use to option on non-i386 machines. I know that there are problems with the resource ranges on other archs, but I don't think it causes any freezes. Is the procedure described in: http://d-i.alioth.debian.org/manual/en.i386/ch05s01.html#id2453819 still valid? This might work, but with d-i you have to do it before the hardware detection pass, so boot in expert mode and run a shell before running hardware detection. One user reported success when I told him to edit /etc/pcmcia/config.opts prior to hardware detection. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Manual] New installer options versus old boot options
On Sat, Apr 24, 2004 at 21:12 +0200, Frans Pop wrote: On Saturday 24 April 2004 19:07, you wrote: On Sat, Apr 24, 2004 at 18:36 +0200, Frans Pop wrote: 2) hw-detect/start_pcmcia=false Is this i386 only? No. Do you know which others? Uhm, as I said in another mail, I misunderstood the question. It is possible to use this option on other archs, but I am not aware of any where it's useful. It isn't impossible that it could be, though. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Manual] New installer options versus old boot options
Per Olofsson wrote: On Sat, Apr 24, 2004 at 13:11 -0400, Joey Hess wrote: Oddly, some report that it says it's skipping the ide-floppy driver and then freezes. That is right before it starts pcmcia, and maybe it does not update the progress bar quite right. But it is updated, I see Starting PC card services when I run hw-detect. Is db_progress fully synchronous? The display update could easily have a race. Yes, you're right, I thought he meant whether it was possible to use to option on non-i386 machines. I know that there are problems with the resource ranges on other archs, but I don't think it causes any freezes. It's interesting to see that the resource range has been a known problem since the woody release at least, with nothing done about it. -- see shy jo signature.asc Description: Digital signature
Re: [Manual] New installer options versus old boot options
How does this look for the PCMCIA option? (I have removed most of the SGML tags.) Some laptop models produced by DELL are known to crash when PCMCIA device detection tries to access some hardware addresses. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the userinputhw-detect/start_pcmcia=false/userinput boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems. Alternatively you can try the following workaround: - boot the installation system in expert mode, choose your language and country, but stop before hardware detection - enter the system shell (see xref linkend=shell/ for details) - execute this command: 'echo exclude port 0x810-0x81f /etc/pcmcia/config.opts' - now return to the main menu and continue with the installation process You will also have to exclude the same address range in '/target/etc/pcmcia/config.opts' before you reboot the computer to avoid running into the same problem when you boot into your new Debian system. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Manual] New installer options versus old boot options
On Sat, Apr 24, 2004 at 22:20 +0200, Frans Pop wrote: How does this look for the PCMCIA option? Good! Some laptop models produced by DELL are known to crash when PCMCIA device detection tries to access some hardware addresses. I think it's written Dell. It might also be worth noting that this can happen on other laptop models than those that Dell produces. - execute this command: 'echo exclude port 0x810-0x81f /etc/pcmcia/config.opts' And then it should also be noted here that this particular option only applies to the Dell computers. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Manual] New installer options versus old boot options
On Sat, Apr 24, 2004 at 15:43 -0400, Joey Hess wrote: But it is updated, I see Starting PC card services when I run hw-detect. Is db_progress fully synchronous? The display update could easily have a race. Then I suspect that this is the case. Yes, you're right, I thought he meant whether it was possible to use to option on non-i386 machines. I know that there are problems with the resource ranges on other archs, but I don't think it causes any freezes. It's interesting to see that the resource range has been a known problem since the woody release at least, with nothing done about it. Yeah, I just remembered about the powerpc problem, where the default resource ranges are way off, and I've now sent a mail to debian-powerpc asking about this. Nobody has sent a bug report about it until recently. Or are you talking about the i386 problems? I don't really know what to do about these. In the PCMCIA HOWTO, there is a long [1]list of computers where you have to tweak the resource ranges. Interesting to note, however, is that Redhat by default excludes 0x800-0x8ff (the Dell Inspiron range), 0x380-0x3ff and IRQ 12. Perhaps we should do something similar. The old maintainer's opinion was that we shouldn't modify the upstream defaults. I don't know what consequences there are when you exclude resource ranges. [1] http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-2.html#ss2.5 -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
