Hi! Thanks for the quick response:
> Quoting O. Sharp ([EMAIL PROTECTED]):
> > Can't get any PCMCIA card services or recognition. Everything else
> > seems to be doing okay.
> >
> > The Gateway Solo 2200 is an older laptop, with no built-in network or
> > modem connections, so it's reliant on PCMCIA cards for this. Unfortunately
> > the installer was unable to load the 'i82365' module, and every subsequent
> > attempt to find the network card or modem resulted in a 'modprobe -v
> > i82365' failure.
[...]
>
> Could you try with the Etch installer beta1 which you can get from
> http://www.debian.org/devel/debian-installer? I suggest downloading
> the "netinst" CD image.
I've downloaded and tried it, and unfortunately it doesn't solve the
problem. The 'modprobe -v i82365' failure showed up again early on, and
then reappeared whenever an attempt to access network hardware was made.
When the problem first appeared I had a look at the virtual consoles.
Virtual console #3 remained blank throughout - possibly because the
installer was running in low-memory mode? - but virtual console #4
showed the following after the first 'modprobe' error (hopefully with no
typos on my part; some tabs added for readability):
Dec 6 10:28:16 kernel: [<c01a9964>] kobject_cleanup+0x3c/0x6c
Dec 6 10:28:16 kernel: [<c01a9994>] kobject_release+0x0/0xc
Dec 6 10:28:16 kernel: [<c01aa123>] kref_put+0x27/0x54
Dec 6 10:28:16 kernel: [<c01a99b6>] kobject_put+0x16/0x1c
Dec 6 10:28:16 kernel: [<c01a9994>] kobject_release+0x0/0xc
Dec 6 10:28:16 kernel: [<c382e08f>] init_i82365+0x177/0x18e [i82365]
Dec 6 10:28:16 kernel: [<c012cf85>] sys_init_module+0xa9/0x180
Dec 6 10:28:16 kernel: [<c0103051>] syscall_call+0x7/0xb
Dec 6 10:28:16 hw-detect: Using /lib/modules/2.6.12-1-386/kernel/drivers/
pcmcia/i82365.ko
Dec 6 10:28:16 hw-detect: insmod:
Dec 6 10:28:16 hw-detect: cannot insert 'lib/modules/2.6.12-1-386/kernel/
drivers/pcmcia/i82365.ko': No such device (-1)
Dec 6 10:28:16 hw-detect: No such device
Dec 6 10:28:16 hw-detect: insmod /lib/modules/2.6.12-1-386/kernel/drivers/
pcmcia/pcmcia_core.ko
Dec 6 10:28:16 hw-detect: insmod /lib/modules/2.6.12-1-386/kernel/drivers/
pcmcia/rsrc_nonstatic.ko
Dec 6 10:28:16 hw-detect: insmod /lib/modules/2.6.12-1-386/kernel/drivers/
pcmcia/i82365.ko
Dec 6 10:28:16 hw-detect: modprobe:
Dec 6 10:28:16 hw-detect: failed to load module i82365
Dec 6 10:28:16 hw-detect:
Dec 6 10:28:16 hw-detect: Error loading 'i82365'
I continued on to see if the situation might change later, and when it
reached the network hardware detection it again hit another red screen of
'modprobe -v i82365'. A look at terminal 4 revealed another set of reports
from hw-detect about failing to load i82365, and about nine lines before
the failure there were a few other lines which may or may not be relevant:
Dec 6 10:48:50 kernel: Intel ISA PCIC probe: not found.
Dec 6 10:48:50 kernel: Device 'i82365.0' does not have a release()
function, it is broken and must be fixed.
Dec 6 10:48:50 kernel: Badness in device_release at
drivers/base/core.c:83
(For clarity, the second line "Device 'i82365.0'...": that is a zero, not
an o or O or ko or any other alphabetic manifestation.)
The install program then brought up a screen saying, "No Ethernet card was
detected, but a FireWire interface is present"; it then asked if I had
some exotic FireWire-to-Ethernet setup it should be looking for. My laptop
is an old 133 MHz Pentium, and certainly has no FireWire interface, but
hopefully this is a clue about what the installer is thinking. :)
After a couple unsuccessful attempts to get the network card recognized, I
aborted the install.
Any suggestions? Any other information which may be relevant or helpful?
Is there a way to install the i82365 module after the fact? Any help or
pointers appreciated. :) Thanks!
-O.-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
