Package: installation-reports

Debian-installer-version: beta 3 100Mb iso, from 
http://gluck.debian.org/cdimage/testing/sarge_d-i/i386/beta3/sarge-i386-netinst.iso
uname -a: Linux (none) 2.4.25-1-386 #1 Tue Feb 24 08:11:13 EST 2004 i686 unknown
Date: Fri Mar 26 22:25:10 PST 2004
Method: Boot from CD

Machine: Sony Vaio SR-17.  CDROM via PCMCIA.
Processor: Pentium 3 700MHz
Memory: 192M
Root Device: PCMCIA CDROM (attempting to install to internal IDE)
Root Size/partition table: 
Output of lspci: /bin/sh: lspci: not found
  (I can run lspci from this system from a running distro, if desired)

Base System Installation Checklist:

Initial boot worked:    [O]
Configure network HW:   [ ]
Config network:         [ ]
Detect CD:              [E]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [ ]
Create file systems:    [ ]
Mount partitions:       [ ]
Install base system:    [ ]
Install boot loader:    [ ]
Reboot:                 [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

Initial boot from the CD worked, but when it came time to autodetect
the CDROM for further installation, it failed.

I tried booting expert ide1=0x180,0x386 (also tried ide2=0x180,0x386),
which has worked in the past on this machine with other linux installers,
but that didn't help.

The "choose drivers" screen on the expert install didn't list any
pcmcia modules, only usb-storage, base ide and a lot of specific ide
controllers.

lsmod didn't list pcmcia or yenta, and modprobe pcmcia and modprobe
yenta-socket both failed, as did modprobe i82365 (suggested by
gravity on IRC).  The error messages are the same except for mod name:
modprobe: failed to load module yenta-socket
insmod: yenta-socket.o: no module by that name found

There's no /lib/modules/2.4.25-1-386/pcmcia directory (there is
kernel/drivers and lots of stuff under that, but nothing matching
pcmcia* or yenta*).

(If we get this working, is there any chance we could add a listing
in the help for Sony CDROMs (ide1=0x180,0x386 or whatever turns out
to work?)  Maybe I should file that as a separate RFE if I get that
far.)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to