On Sat, 13 Nov 2010 20:31:37 +0300, Mark Goldshtein wrote: > Have tried to install Debian Squeeze (weekly builds 2010-11-08) on a > laptop with Intel 2100 Wifi card. Card's firmware is packed into native > debianic non-free tarball. As explained here: > http://wiki.debian.org/ipw2200, it is enough to supply the tarball to > the running installer on any removable media mentioned. But the > installer first seek for fd0 floppy and seek forever, endlessly > educating me about FAT16 file system, dangerous uppercase names and > related troubles, as I have noticed at hidden F4 console. No single > warning sign, progress bar or other useful info on a current active > screen. As a countermeasure, I have searched my pockets, found USB > floppy drive and wrote floppy diskette, plugged that into laptop but > installer continue its tries for ghost fd0 and does not react on other > removable media inserted in all sockets and holes. If you, please, help > me to find a workaround to subdue that bad robot? Maybe it is possible > to implant the firmware into installer ISO? And no, I cannot install > using a netinstall image, because the installer does not support WPA and > even if we will resolve firmware situation, the installation will not > continue anyway.
It should work. Or at least it is documented to do it so: 6.4. Loading Missing Firmware http://d-i.alioth.debian.org/manual/en.amd64/ch06s04.html Did you try by putting the firmware into USB stick (not floppy)? > A bit of offtopic, sorry. Dear Debian Team, would you, please, to pay > attention to the installer first? Let us find and pin up bugs, post wise > comments, suggest features, analyze patches, flood up the mailing lists > _after_ the system being installed. Isn't it an installer a thing that > has to be polished first? I've found some "issues" (let's say that way) in Debian installer for both, Lenny and Squeeze. For lenny it was impossible to get GRUB legacy installed and Squeeze was having some trouble with filesystem formatting options (already corrected, I guess). > In addition, it seems to be useful to inform a human side of the > installation process what currently is going on in any situation, not > success stories only. Jumping to tty console where messages are being logged is the common way for debugging problems, at least for an expert installation. You can also save the log for later review. Nevertheless, being a bit more verbose in ncurses GUI should not hurt :-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.11.14.15.56...@gmail.com
