Bug#241179: successful install, no network in 2nd stage (pcmcia)
Frederik Dannemare wrote: I will suggest an errata item for the release candidate installer that should be available in a couple of days from now: * PCMCIA device shifting (between CD-ROM and NIC) during install: If you choose to install Debian via CD, but you only have your CD-ROM drive and NIC (which you want to setup and use as primary NIC during installation) accessible via a single PCMCIA slot in your computer, here is what you can do to work around this situation. Boot the installer with the CD-ROM device plugged into the PCMCIA slot and do a normal 1st stage installation, except that you should skip network setup or just type in dummy values at this point. Then when it says Installation complete, choose 'Go back' to drop back to the main menu. Now change the PCMCIA device from CD-ROM to NIC, and choose to 'Detect network hardware'. Your NIC should now be detected and you can continue (again 'Go back' to main menu) to 'Network configuration'. If your NIC is a wireless, press Alt+F2 to get a shell. Change the PCMCIA device from NIC to CD-ROM and type in the shell: chroot /target mount /cdrom apt-get install wireless-tools umount /cdrom exit Go back to Alt+F1 and change the PCMCIA device from CD-ROM to NIC. Choose 'Continue' to reboot (with NIC in PCMCIA slot) and thereby finish the 1st stage of the installation process. When 2st stage comes up after the reboot, you should have a working NIC and as such you can choose to download extra packages via ftp, http, etc. Should you, however, not have a working NIC at this point, go to the shell (Alt+F2) and try to reload your NIC: ifdown iface ifup iface Return to Alt+F1 and continue installation (assuming networking now works)... * I think this might be more appopriate as a kind of howto page on our wiki than as an errata item. -- see shy jo signature.asc Description: Digital signature
Bug#241179: successful install, no network in 2nd stage (pcmcia)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 06 August 2004 20:43, Joey Hess wrote: Frederik Dannemare wrote: I will suggest an errata item for the release candidate installer that should be available in a couple of days from now: *** ** PCMCIA device shifting (between CD-ROM and NIC) during install: If you choose to install Debian via CD, but you only have your CD-ROM drive and NIC (which you want to setup and use as primary NIC during installation) accessible via a single PCMCIA slot in your computer, here is what you can do to work around this situation. Boot the installer with the CD-ROM device plugged into the PCMCIA slot and do a normal 1st stage installation, except that you should skip network setup or just type in dummy values at this point. Then when it says Installation complete, choose 'Go back' to drop back to the main menu. Now change the PCMCIA device from CD-ROM to NIC, and choose to 'Detect network hardware'. Your NIC should now be detected and you can continue (again 'Go back' to main menu) to 'Network configuration'. If your NIC is a wireless, press Alt+F2 to get a shell. Change the PCMCIA device from NIC to CD-ROM and type in the shell: chroot /target mount /cdrom apt-get install wireless-tools umount /cdrom exit Go back to Alt+F1 and change the PCMCIA device from CD-ROM to NIC. Choose 'Continue' to reboot (with NIC in PCMCIA slot) and thereby finish the 1st stage of the installation process. When 2st stage comes up after the reboot, you should have a working NIC and as such you can choose to download extra packages via ftp, http, etc. Should you, however, not have a working NIC at this point, go to the shell (Alt+F2) and try to reload your NIC: ifdown iface ifup iface Return to Alt+F1 and continue installation (assuming networking now works)... *** ** I think this might be more appopriate as a kind of howto page on our wiki than as an errata item. Sounds reasonable, I guess. It's been added to http://wiki.debian.net/index.cgi?DebianInstallerWorkarounds - -- Frederik Dannemare | mailto:[EMAIL PROTECTED] GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu Key fingerprint: BB7B 078A 0DBF 7663 180A F84A 2D25 FAD5 9C4E B5A8 http://frederik.dannemare.net | http://www.linuxworlddomination.dk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBFAjZLSX61ZxOtagRAu85AJ9py1ph05Y1XvXQhEvtOraMwi4RQgCfc0Bu 0ZxDe9CSB/GDO0KToB8IXp0= =xdqW -END PGP SIGNATURE-
Bug#241179: successful install, no network in 2nd stage (pcmcia)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 05 August 2004 05:42, Akkana Peck wrote: Frederik Dannemare writes: No, the package is not needed for wired cards, but I assumed that you wanted to use your wireless card as your primary NIC during the installation, since the installer only handles the setup of one NIC. And since your very first mail was about wireless pcmcia not working (no mention of a second (3com) card), I have focused only on getting your I'm not sure why you say that. I looked back over the bug and I don't see anywhere I mention wireless, and I've never been using wireless, always this 3com ethernet (wired) card. It's not the second card, it's the only card (I do own a wireless card, but have never been using it during this install scenario). Argh. Sorry, I was mixing up your report with another one that looks like like it (I have been processing so many reports lately) but that other one is wireless. If I said something somewhere to imply otherwise, it was an error (where was that?) My fault. Hence, my howto/work-around was targeted for situations where the user has a CD-ROM and (wireless) NIC only accessible via a single pcmcia slot in the computer. I think I followed it except for the wireless-tools part. okay I don't get that. I'm really no expoert in d-i internals, and 2.4.18-bf2.4 sounds to me like a kernel from good old woody. Still, Yes, you're right. Ignore the 2.4.18 stuff, that was booting off the wrong kernel. (This testing is complicated by the fact that the installer doesn't seem willing to re-use my existing /boot, so I have to go through three screens until grub fails, then boot into the working system and copy files by hand into /boot, then reboot into the stage 2 installer. I was using the wrong kernel that time. Please ignore anything I said about modprobe errors.) will do With the correct kernel, 2.4.26-1-386, it does start pcmcia (and probably hotplug, though I missed seeing the messages for that) and I do see an eth0 device with ifconfig -a, but it has no IP address. (I set a static IP address, netmask, gateway, and nameservers during stage 1 after I disconnected the cdrom and connected the ethernet card.) However, if I ctrl-alt-f2 to get a shell while the stage 2 installer is still running, log in as root, and run ifup eth0, then it sees the network and I can proceed with installation. Why doesn't it run ifup when the stage 2 installer boots? Might there be a sequence problem, with the network being initialized before pcmcia/cardbus? (I'm booting with the card still inserted from the stage1 network config step, not trying to hotplug it after booting.) let's focus on my initial attempt which is to get wireless working (disregaring the fact that you have a wired card also) disregard this :) I'm so sorry to have tried to mislead you. Wireless ads two extra device swaps, and I'd have to specify an essid at some point during the process (does the sarge installer handle that, yes, the installer can handle stup of essid (and wep, btw). or would I have to ctl-alt-F2 and run iwconfig by hand?), so I'm hoping it's okay if I keep testing with the wired card. no problem. you do that. One other difference is that my wireless card is pcmcia while my ethernet card is cardbus, so if there's a problem with cardbus initialization during stage 2, the wireless card may not point that out. Most modern cards are cardbus. [ description of new workaround for stage 1 ] When 2st stage comes up after the reboot, you should have a working wireless NIC and as such you can choose to download extra packages via ftp, http, etc. Nope, that part still doesn't work. bugger. It looks like we're down to two problems: 1. No provision during stage 1 for saying I really have a network even though the card isn't plugged in. Your workaround seems to work (probably including the extra parts with wireless-tools, for those using a wireless card). 2. Stage 2 does not initialize the network when it's running off a cardbus card. The ctrl-alt-F2, log in, ifup, ctrl-alt-F1 workaround seems to solve this. How about consecutive reboots when the system is installed via the sarge installer and up'n'running? Is the network then also not initialized so that you have to always do ifup manually upon every reboot? I forget if you have already mentioned this earlier on, but have you actually had the wireless card in question working in Linux at anytime? The 3Com card I'm using works fine on my working sarge (installed using the woody installer, then upgrading; it also works on libranet, xandros and various redhats). I have had some issues with some versions of debian when hotplugging the card, because the hotplug scripts reference $INTERFACE$LIFACE, where $LIFACE is the string =hotplug, and causes ifup to fail to see the card (removing the $LIFACE
Bug#241179: successful install, no network in 2nd stage (pcmcia)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 05 August 2004 06:04, you wrote: Akkana Peck writes: I'll run a test using a pcmcia ethernet card and report back. I tried it with an old Xircom PCMCIA card that used to work absolutely everywhere (I think the module was called xircom-cs). The Sarge installer doesn't recognize it. Oh, well. :-( Well, thanks for trying. - -- Frederik Dannemare | mailto:[EMAIL PROTECTED] GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu Key fingerprint: BB7B 078A 0DBF 7663 180A F84A 2D25 FAD5 9C4E B5A8 http://frederik.dannemare.net | http://www.linuxworlddomination.dk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBEfqFLSX61ZxOtagRAqN/AJ94GscZiAKcEWfI2BGif4p1SjNJ1wCeIXLS JP+leV4EjxRuOL5WwYLXWEY= =dynW -END PGP SIGNATURE-
Bug#241179: successful install, no network in 2nd stage (pcmcia)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 06 August 2004 00:20, you wrote: Frederik Dannemare writes: How about consecutive reboots when the system is installed via the sarge installer and up'n'running? Is the network then also not initialized so that you have to always do ifup manually upon every reboot? It looks like I have to do ifup manually each time. :-( Though it's possible that something didn't get initialized properly when I installed, since I had to skip back and forth in the installation steps. Thanks. I really appreciate all the time and offert you have put into testing this matter. No problem -- I hope I'm helping! ...Akkana I will suggest an errata item for the release candidate installer that should be available in a couple of days from now: * PCMCIA device shifting (between CD-ROM and NIC) during install: If you choose to install Debian via CD, but you only have your CD-ROM drive and NIC (which you want to setup and use as primary NIC during installation) accessible via a single PCMCIA slot in your computer, here is what you can do to work around this situation. Boot the installer with the CD-ROM device plugged into the PCMCIA slot and do a normal 1st stage installation, except that you should skip network setup or just type in dummy values at this point. Then when it says Installation complete, choose 'Go back' to drop back to the main menu. Now change the PCMCIA device from CD-ROM to NIC, and choose to 'Detect network hardware'. Your NIC should now be detected and you can continue (again 'Go back' to main menu) to 'Network configuration'. If your NIC is a wireless, press Alt+F2 to get a shell. Change the PCMCIA device from NIC to CD-ROM and type in the shell: chroot /target mount /cdrom apt-get install wireless-tools umount /cdrom exit Go back to Alt+F1 and change the PCMCIA device from CD-ROM to NIC. Choose 'Continue' to reboot (with NIC in PCMCIA slot) and thereby finish the 1st stage of the installation process. When 2st stage comes up after the reboot, you should have a working NIC and as such you can choose to download extra packages via ftp, http, etc. Should you, however, not have a working NIC at this point, go to the shell (Alt+F2) and try to reload your NIC: ifdown iface ifup iface Return to Alt+F1 and continue installation (assuming networking now works)... * Also, I will clone off this report to the netcfg developers to inform them of the problem you are having where you have to 'up' your Cardbus interface manually upon every reboot (they might ask you for further info regarding this). After having cloned off this report to the developers in charge of networking, I will close this one. Many thanks for all your time. - -- Frederik Dannemare | mailto:[EMAIL PROTECTED] GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu Key fingerprint: BB7B 078A 0DBF 7663 180A F84A 2D25 FAD5 9C4E B5A8 http://frederik.dannemare.net | http://www.linuxworlddomination.dk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBEr6aLSX61ZxOtagRAvZiAJ9HXKz5ldp+kPL10l3BvVahRsnQxwCcC+yV Nz/t/IzIMsvDHSEIj18ZuoQ= =t+PQ -END PGP SIGNATURE-
Bug#241179: successful install, no network in 2nd stage (pcmcia)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 04 August 2004 21:42, Akkana Peck wrote: Frederik Dannemare writes: One more thing: You'll have to 'apt-get install wireless-tools' from the CD after you have finished to whole installation. I can confirm that this works on my laptop with PCMCIA NIC, if I don't plugin my PCMCIA NIC until 1st stage says Installation complete, and then 'go back' to main menu to detect/reconfigure networking. It worked, but wireless-tools had to be installed afterwards, manually. It didn't work for me. I unplugged the cdrom after it ejected, plugged in the ethernet card, said go back and arrowed up to detect network hardware. It detected my network card (3c59x) just fine, then dumped me back into the end-of-installation sequence. So I said go back again and went through configure networking and gave it my IP, netmask, DNS etc. It dumped me back into the end sequence, so this time I let it reboot (was this where I was supposed to install wireless-tools, or did you mean later, after the reboot? In any case, I'm using a wired network for this, so wireless-tools shouldn't matter yet). No. You did everything just right so far. Install wireless-tools when you have finished both 1st and 2nd stage of the installation (ie. when the installation is 100% completed and you get at login prompt). After the reboot, it went through the time setting, then said You don't seem to be connected to the internet and when I gave it http and ftp.debian.org Remember: at this point you haven't yet installed wireless-tools. Thus, your wireless NIC doesn't work just yet, so skip downloading any packages at this point. (are those two mutually exclusive? anyway, I tried ftp as well as http) I'm not 100% sure what you mean here, but you can certainly have both http and ftp sources to download from in your /etc/apt/sources.list and got Failed to access the Debian archive. As mentioned above: skip downloading stuff at this point, and just finish up this 2nd stage of the installer. When 2nd stage has finished and you get the login prompt, you should login as root and install the wireless-tools. Finally, do: 'idfown iface ifup iface'. This should get your wirelesss NIC going. At this point you can choose 'apt-setup' to add ftp and/or http sources to download new packages from. I tried unplugging the card, then plugging it back in (I had initially just left the card in while booting) but I didn't get a beep (I did get a beep when I plugged it in earlier, when I was running off the installer kernel; but I don't get a beep when I plug it in to my normal installed sarge running 2.4.26, because it's cardbus, not pcmcia, so it calls hotplug instead of pcmcia, which doesn't beep.) If I go into ctl-alt-F2 at this point and run dmesg, there are no messages indicating it saw any pcmcia events or loaded the driver for the network card. If I do dmesg | grep -i pcmcia I see nothing; same for dmesg | grep -i hotplug. So it looks like it's not running any pcmcia/cardbus services which would enable it to see the card. I don't think grep'ing for hotplug or pcmcia necessarily shows anything (at least it does not for me). However, you should see some lines which mention that a driver has been loaded, and you should see a few lines with the interface name (e.g. eth1). - -- Frederik Dannemare | mailto:[EMAIL PROTECTED] GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu Key fingerprint: BB7B 078A 0DBF 7663 180A F84A 2D25 FAD5 9C4E B5A8 http://frederik.dannemare.net | http://www.linuxworlddomination.dk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBEYGULSX61ZxOtagRAtzDAJ9ddUIRhpVcbjcrneuFhTKAy4/grgCfQ00X DEi4Wki9VxHqsTrUObc0v9w= =SXeP -END PGP SIGNATURE-
Bug#241179: successful install, no network in 2nd stage (pcmcia)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 05 August 2004 03:04, Akkana Peck wrote: Frederik Dannemare writes: this where I was supposed to install wireless-tools, or did you mean later, after the reboot? In any case, I'm using a wired network for this, so wireless-tools shouldn't matter yet). No. You did everything just right so far. Install wireless-tools when you have finished both 1st and 2nd stage of the installation (ie. when the installation is 100% completed and you get at login prompt). After the reboot, it went through the time setting, then said You don't seem to be connected to the internet and when I gave it http and ftp.debian.org Remember: at this point you haven't yet installed wireless-tools. Thus, your wireless NIC doesn't work just yet, so skip downloading any packages at this point. I don't understand where wireless-tools comes in. I'll repeat, I am not using a wireless network. I'm using a normal wired one, with a 3Com 3c59x card. Are you saying wireless-tools is needed even for a network that's not wireless? No, the package is not needed for wired cards, but I assumed that you wanted to use your wireless card as your primary NIC during the installation, since the installer only handles the setup of one NIC. And since your very first mail was about wireless pcmcia not working (no mention of a second (3com) card), I have focused only on getting your wireless to work - not even thinking about your wired card, since (as mentioned) the installer doesn't handle setting up more than one card during the installation, anyways. Hence, my howto/work-around was targeted for situations where the user has a CD-ROM and (wireless) NIC only accessible via a single pcmcia slot in the computer. (are those two mutually exclusive? anyway, I tried ftp as well as http) I'm not 100% sure what you mean here, but you can certainly have both http and ftp sources to download from in your /etc/apt/sources.list The sequence of screens in the second stage of the installer is: - Pick a protocol (http, ftp, cdrom, plus a couple others I don't remember). It only seems to take one; I tried it once with http, then I tried it with ftp. - Pick a country (I'm in the US) - Pick a mirror site for that country. (I'm picking ftp.debian.org, and I wasn't clear whether it was kosher to use that mirror even if I picked http rather than ftp two screens earlier. But it doesn't matter since it's pretty clear I don't have a network at all.) As mentioned above: skip downloading stuff at this point, and just finish up this 2nd stage of the installer. When 2nd stage has finished and you get the login prompt, you should login as root and install the wireless-tools. Finally, do: 'idfown iface ifup iface'. This should get your wirelesss NIC going. At this point you can choose 'apt-setup' to add ftp and/or http sources to download new packages from. Okay, I did that, skipped installing new packages (I hit cancel) and went straight to finish configuring the installer (I also skipped configuring the MTA). I got a login prompt, so I logged in, and typed ifconfig, and as expected, I only have lo, no eth0 (because it still doesn't see the network card). I tried modprobe 3c59x as root, but I got: modprobe: Can't open dependencies file /lib/modules/2.4.18-bf2.4/modules.dep (no such file or directory) I don't get that. I'm really no expoert in d-i internals, and 2.4.18-bf2.4 sounds to me like a kernel from good old woody. Still, let's focus on my initial attempt which is to get wireless working (disregaring the fact that you have a wired card also) Looking over the whole situation again, I would suggest you to try again exactly like this (where you install wireless-tools just before finishing 1st stage): ( I have just tried it on two different laptops here, and it works beautifully... ) = Boot the installer with the CD-ROM device plugged into the PCMCIA slot and do a normal 1st stage installation, except that you should skip network setup or just type in dummy values at this point. Then when it says Installation complete, choose 'Go back' to drop back to the main menu. Now change the PCMCIA device from CD-ROM to NIC, and choose to 'Detect network hardware'. Your wireless NIC should now be detected and you can continue (again 'Go back' to main menu) to 'Network configuration'. After having configured the wireless NIC, press Alt+F2 to get a shell. Change the PCMCIA device from NIC to CD-ROM and type in the shell: chroot /target mount /cdrom apt-get install wireless-tools umount /cdrom exit Go back to Alt+F1 and change the PCMCIA device from CD-ROM to NIC. Choose 'Continue' to reboot and thereby finishing the 1st stage of the installation process. When 2st stage comes up after the reboot, you should have a
Bug#241179: successful install, no network in 2nd stage (pcmcia)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 01 August 2004 19:22, Akkana Peck wrote: Frederik Dannemare writes: first and foremost: thank you for your bug report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=241179 I'm currently processing old installation reports, and since you reported some problems back in March, I would very much appreciate it, if you could find time to download and test the latest[1] cd image and confirm whether you still see the problems you've mentioned. I just tried it, with the daily build from yesterday, from http://cdimage.debian.org/pub/cdimage-testing/daily/ The bug is still there. Early in the installation, it asks me what driver to use for networking, I tell it, it tries to load the module and fails (because the network card isn't plugged in, because the pcmcia slot is being used by the cdrom drive) and it never gives me another chance. When I reboot, it says It appears you don't have networking, do you want to use PPP? (which seems a bit strange, since no real modem is plugged in and I'm sure debian doesn't include the non-free driver for my winmodem). I did have the ethernet card plugged in when I booted into the new installation. Hotplugging the card doesn't work either. I'd be happy to test further, or come on #debian-installer to discuss it if anyone is interested in looking into this bug. ...Akkana Try a reinstall with the PCMCIA CD device. Then when it says Installation complete, 'go back' to drop back to the main menu. Now change PCMCIA device from CD to NIC and choose to detect network hardware. Your PCMCIA NIC should now be detected and you can continue with network configuration. If the PCMCIA device shift does not allow for PCMCIA NIC detection (for whatever reason), choose instead to finish the installer (but keep the CD in drive to load 1st stage again (boot installer in 'expert' mode)). Now go directly to the 'detect network hw' step. When done with networking: finish, eject cdrom, reboot. I know it's a bit akward, but you have a special case wrt. your PCMCIA hardware setup. I think it'll work. Let us know. Thanks, - -- Frederik Dannemare | mailto:[EMAIL PROTECTED] GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu Key fingerprint: BB7B 078A 0DBF 7663 180A F84A 2D25 FAD5 9C4E B5A8 http://frederik.dannemare.net | http://www.linuxworlddomination.dk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBD3qHLSX61ZxOtagRAum/AJ9/HFMJcCJOpug+XCxGYtHKImL+lQCbBncc /a2QFeDuFp9CC2eK1Jxc280= =46sf -END PGP SIGNATURE-
Bug#241179: successful install, no network in 2nd stage (pcmcia)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 03 August 2004 13:44, Frederik Dannemare wrote: On Sunday 01 August 2004 19:22, Akkana Peck wrote: Frederik Dannemare writes: first and foremost: thank you for your bug report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=241179 [ snip ] Try a reinstall with the PCMCIA CD device. Then when it says Installation complete, 'go back' to drop back to the main menu. Now change PCMCIA device from CD to NIC and choose to detect network hardware. Your PCMCIA NIC should now be detected and you can continue with network configuration. If the PCMCIA device shift does not allow for PCMCIA NIC detection (for whatever reason), choose instead to finish the installer (but keep the CD in drive to load 1st stage again (boot installer in 'expert' mode)). Now go directly to the 'detect network hw' step. When done with networking: finish, eject cdrom, reboot. I know it's a bit akward, but you have a special case wrt. your PCMCIA hardware setup. I think it'll work. Let us know. Thanks, One more thing: You'll have to 'apt-get install wireless-tools' from the CD after you have finished to whole installation. I can confirm that this works on my laptop with PCMCIA NIC, if I don't plugin my PCMCIA NIC until 1st stage says Installation complete, and then 'go back' to main menu to detect/reconfigure networking. It worked, but wireless-tools had to be installed afterwards, manually. If you can make it work with this workaround, I will close this report. It's unlikely to be fixed in time for the release of the final installer images, so I will make sure to file an errata item to the d-i developers where I mention how to work around the problem. Thanks, - -- Frederik Dannemare | mailto:[EMAIL PROTECTED] GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu Key fingerprint: BB7B 078A 0DBF 7663 180A F84A 2D25 FAD5 9C4E B5A8 http://frederik.dannemare.net | http://www.linuxworlddomination.dk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBD4OxLSX61ZxOtagRAkwPAJwKz11tVaLH6c7PRcbxPS3EGJDUBACfZGmk 1PZ4UMLNjncOaR+Gr7xhUWs= =tH0i -END PGP SIGNATURE-
Bug#241179: successful install, no network in 2nd stage (pcmcia)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 03 August 2004 13:44, Frederik Dannemare wrote: On Sunday 01 August 2004 19:22, Akkana Peck wrote: Frederik Dannemare writes: first and foremost: thank you for your bug report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=241179 [ snip ] If the PCMCIA device shift does not allow for PCMCIA NIC detection (for whatever reason), choose instead to finish the installer (but keep the CD in drive to load 1st stage again (boot installer in 'expert' mode)). Now go directly to the 'detect network hw' step. When done with networking: finish, eject cdrom, reboot. Forget I ever said this last bit. It doesn't make sence to suggest it, since: if the PCMCIA shift didn't work in the first suggestion (where you use 'go back'), why should it be any different here upon reloading 1st stage, where you again have to shift PCMCIA device. Also, you really can't just skip directly to 'detect network hw' like I described and make it all work... - -- Frederik Dannemare | mailto:[EMAIL PROTECTED] GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu Key fingerprint: BB7B 078A 0DBF 7663 180A F84A 2D25 FAD5 9C4E B5A8 http://frederik.dannemare.net | http://www.linuxworlddomination.dk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBD6iYLSX61ZxOtagRAm95AJ9HiE34VhKIonVF98PNGCuVjltUAgCfZS1K s2X34MgxYSVEfaZFpATAQiw= =LukN -END PGP SIGNATURE-
Bug#241179: successful install, no network in 2nd stage (pcmcia)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, first and foremost: thank you for your bug report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=241179 I'm currently processing old installation reports, and since you reported some problems back in March, I would very much appreciate it, if you could find time to download and test the latest[1] cd image and confirm whether you still see the problems you've mentioned. If you can confirm they are no longer present, I will close this report. Much has changed with the installer since March, and it is not unlikely that these problems may have been dealt with by the Debian Developers working on the installer. Looking forward to hearing from you again. Thank you for your time. [1]http://cdimage.debian.org/pub/cdimage-testing/daily/ - -- Frederik Dannemare | mailto:[EMAIL PROTECTED] GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu Key fingerprint: BB7B 078A 0DBF 7663 180A F84A 2D25 FAD5 9C4E B5A8 http://frederik.dannemare.net | http://www.linuxworlddomination.dk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBCq34LSX61ZxOtagRAosgAJ9oHMQBHfRiJhyXiuMxOuYNx5YCowCeJxtc wtieY1s2m84OeN9M5IQXYdo= =Dxyd -END PGP SIGNATURE-
