Bug#58051: Network install using PCMCIA totally hosed
Package: boot-floppies
Version: 2.2.5-2000-01-27
This may be related to #57894 "Network config hangs with PCMCIA".
I also experienced the bogus azerty keyboard as reported in #58009.
Hardware: Gateway Solo 9300 (Japanese model)
TI 1450 PCMCIA controller
3Com 3C589C ethernet + modem PCMCIA
The contents of /debian/dists/potato/main/disks-i386/2.2.5-2000-01-27/
are in C:\LINUX under Windows 98. Reboot to DOS from Windows using a
floppy (DOS installed to floppy from Windows 98). Start install.bat
from C:\LINUX.
PCMCIA configuration worked OK, it seems, although it did not offer to
configure a network interface---it really should.
Attempts to configure Network generally failed with "no network
interface". If I did everything exactly right, which at least
involved going directly to Network configuration after completing
PCMCIA configuration, I could sometimes configure the network.
Then I successfully downloaded base.tgz on at least one attempt.
I also used the base.tgz in C:\LINUX on at least one occasion.
Either way, following the base install, the network was not
configured, and the package install failed. I managed to configure
the network from a subshell and get dselect started up, but this left
the system in very confused state. In particular, my other partitions
were not mounted (this may be due to the fact that I didn't configure
them, but this option was not offered so I assumed the partition
config was already done). The default keymap was correctly configured
as jp106 in the first stage install, but somehow left as azerty, and I
couldn't log in. (This was very confusing because my initial accounts
were "root" and "steve", both of which use the same keystrokes in
qwerty and in azerty. Maybe there was some confusion between
/etc/kbd/default.map.gz and /etc/kbd/default.kmap.gz? Copying the
former to the latter fixed the problem. This seems to be the same as
#58009, maybe it is unrelated to the PCMCIA install.)
Also the network scripts were not updated. I configured these by
hand, I think. Nor was the network for PCMCIA. Finally, when I did
get some stuff installed, I discovered that /etc/init.d/network is
invoked as /etc/rcS.d/S40network, while /etc/init.d/pcmcia is invoked
as /etc/rc[2345].d/S11pcmcia, which order seems very dubious to me,
especially for installation.
For reasons I don't understand starting PCMCIA as rcS.d/S35pcmcia
doesn't get the network properly configured, while starting it earlier
than that results in a hung system on boot. (Reboot to single-user
avoided the hang; it may have something to do with the Wnn package for
Japanese input, which was the last thing that printed any messages to
the console. Wnn does use the network, which may be why there was a
hang---I was low on batteries and didn't feel like seeing maybe if
something would timeout, those gethostby*() timeouts are hell on one's
patience...).
Why does all this remind of Red Hat or Turbolinux? This is what I
switched to Debian to avoid....
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."
Reply to: