[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Report of slink installation with 2.1.3 disks



Got everything installed, but had problems with PCMCIA.

CONFIGURATION:
  machine:    IBM ThinkPad 560e
  memory:     32MB
  disk:       2016MB IBM-DTNA-22110
  partitions: hda1 660MB fat32
              hda2 96MB Linux swap
              hda3 1.3GB Linux root
  scsi:       PCMCIA Adaptec AHA152x for Sony CD-diskman, not used
  sound:      internal, not tried
  video card: 2MB VRAM, Trident Cyber 9382
  cd-rom:     Sony SCSI CD-diskman, not used this time
  net card:   PCMCIA 3Com 589 (3c562)

TESTING TARGET:
  task:       Base system installation (slink)
  source:     boot-floppies 2.1.3 from upload@erlangen

PREPARATION:
  Used dd to create rescue and drivers floppies. Prepared NFS server on
  another machine to export directory containing base2_1.tgz and other
  boot related files (rescue, drivers, etc.). The machine running NFS
  server has also complete mirror of slink and hamm and was later used
  to install the rest of the packages with dselect/apt over HTTP.

PROCESS:
  Booted with tecra rescue disk since the normal rescue caused reboot
  after "Loading linux..." message even with kernel option
  "floppy=thinkpad".

  When it was time to configure PCMCIA, I had same problems as reported 
  by Ian Redfern on debian-boot. When PCMCIA scripts were run, at least 
  fuser, sed and expr were not found, causing error messages and
  segmentation faults. However, eth0 was available but disappeared when
  the network configuration was done.

  I was able to recover from missing eth0 by killing cardmgr, removing 
  all the PCMCIA related modules and then manually using the running
  cardmgr from the other virtual console.

  When I proceeded installing the base system via NFS, I had to first
  move /target/sbin/cardmgr to /target/sbin/cardmgr.something so that 
  base2_1.tgz could be untarred without errors.

  After that everything went well and I proceeded to install lilo and 
  do the first reboot.

  After reboot I decided not to try "choose from several selections",
  but went straight to dselect. I configured apt to use HTTP and 
  accepted the default selections which were installed with no 
  problems. There was no need to run [I]nstall many times and the 
  installation process was very smooth. Good job guys :)

  After quitting dselect, I logged in and noticed that my fi-latin1 
  keymap was not loaded. There seems to be a bug somewhere still.

COMMENTS:
  As someone else already noted, why not have
  o "Another system will be the DNS server." as default when 
     configuring DNS server? Currently it defaults to
  o "The system will be its own DNS server."

-- 
Heikki Vatiainen                  * hessu@cs.tut.fi
Tampere University of Technology  * Tampere, Finland



--  
To UNSUBSCRIBE, email to debian-testing-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: