rule-list
[Top][All Lists]
Advanced

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

Re: [RULE] Xircom NIC: xirc2ps_cs.o doesn't load.


From: C David Rigby
Subject: Re: [RULE] Xircom NIC: xirc2ps_cs.o doesn't load.
Date: Sun, 23 May 2004 16:10:34 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040413 Debian/1.6-5

Hi Gabriel, et. al.,

I have experimented a bit with a Presario 1080 that I have which also possesses a Cirrus Logic controller. The problem with this machine is that apparently the base address of the controller is non-standard, and so it is not found by the i82365 driver module. Here is how I got it to work for an NFS install:

You will need all three of the diskettes, slinky-v0.3.96 boot/root diskette, disk2 diskette and pcmcia diskette.

Boot off of the slinky disk. Once you get the initial "do you want to install" message, press CTL-ALT-F2 to get to the 2nd virtual console, and press ENTER to activate it. Now issue the command:

cat /proc/pci

and you will get some cryptic-looking lines of information about the hardware. Due to space constraints, our kernel does not include the pci device name database, so some experimentation may be necessary to get the controller recognized. The line that turned out to be important for me was this one:

Bus 0, device 19, function 0:
   Class 0605: PCI device 1013:1100 (rev 238).
      I/O at 0xfcfc [0xfcff].

The details for your controller will almost certainly be different. next, eject the slinky boot disk and insert the pcmcia support disk. Mount it with

mount /dev/fd0 /mnt/floppy

and edit /mnt/floppy/pcmcia.sh to add the information on the base address to the PCIC_OPTS line:

PCIC_OPTS=i365_base=0xfcfc

Then, edit /scripts/init_network.sh to indicate the network parameters you wish to use. You should NOT need to indicate the NIC module to load, since cardmgr (invoked in /mnt/floppy/pcmcia.sh) should be able to handle that. But if you do have to do it, you should leave off the ending ".o" unless you give the full path name to the module. You can also the name servers entry in this script if you are working on your own LAN - just use absolute IP addresses.

Now, run the pcmcia scripts on the floppy:

/mnt/floppy/setup_pcmcia.sh

followed by

/mnt/floppy/pcmcia.sh start

Check that the network is operational by issuing:

ifconfig

You should see that your eth0 interface is active and has an address. If so, you can unmount the floppy disk (umount /mnt/floppy) and press CTRL-ALT-F1 to return to the installer and proceed.

Note that in figuring this out I did do some experimenting. In particular, in testing to get the i82365 driver to load, I used modprobe to try to install modules in the kernel. Since I did this before running /mnt/floppy/setup_pcmcia.sh, which exports the variable pcmcia_dir=/mnt/floppy to set the base directory for modules, it will be necessary to refer to modules by their full pathname to get them to load. So, to setup pcmcia support manually, I had to do this:

modprobe /mnt/floppy/modules/pcmcia/pcmcia_core.o
modprobe /mnt/floppy/modules/pcmcia/i82365.o i365_base=0xfcfc
modprobe /mnt/floppy/modules/pcmcia/ds.o

Let me know if this cannot get your network activated, and perhaps I can think of something else to try...

CDR

address@hidden wrote:
Marco,

No, I'm fairly certain that FC2 is not the problem. I haven't even gotten that far, yet... otherwise I would have posted to the FC2 list. I'm still struggling with slinky. However, searching Red Hat's archives did yield some better information.

The problem with xirc2ps_cs.o is that in /scripts/pcmcia.sh, I changed PCIC from i82365 to xirc2ps_cs.

Now, while I still can't get i82365 to work, I've confirmed that it's the correct PCIC. My PCMCIA controller is a Cirrus Logic CL-PD6730 (PCI bus)... and so I need to use i82365.

I tried fiddling with options on "insmod i82365"... but to no avail... not even the options in the man page directed toward the Cirrus Logic chip.

I recently found /etc/pcmcia/config.opts, and I'm guessing that I might need to fiddle around in there... but thus far it's yielded no fruit.

Here's my session... no edits... using slinky v0.3.96.  Anybody got an idea?

#######################################################################

boot: linux dd updates
Loading vmlinuz........
loading rootfs.gz........


(A lot of stuff went by fast)

hda:1058400 sectors (542 MB) w/96KiB Cache, CHS=525/32/63
IDE-FLOPPY DRIVER 0.99.NEWIDE
Partition check:
 hda:
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 2048K size 1024 blocksize
loop: loaded (max 8 devices)
ide-floppy driver 0.99.newide
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 1024)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 659k freed
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel emmory: 152k freed
init started: BusyBox v0.60.5 (2002.12.11-03:01+0000) multi-call binary

You may start the RULE project's slinky installer, or answer
'no' to drop out to a shell prompt.

Would you like to begin the installation process? [ yes / no ] : no

When you are ready to begin installation, simply
execute /scripts/setup.sh.


BusyBox v0.60.5 (2002.12.11-03:01+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# (here, I put in the PCMCIA disk)
# mount /mnt/floppy
mount: /dev/fd0 is write-protected, mounting read-only
# /mnt/floppy/setup_pcmcia.sh

Edit /scripts/init_network.sh for your needs.
You may also want to edit /scripts/pcmcia.sh
if you need to define base options or modules.

Then execute '/scripts/pcmcia.sh start' to
Initialize the pcmcia services and bring up
the network.

After the network is up, unmount the floppy.
#
(To keep it simple... let's not worry about the network just yet.)
# /scripts/pcmcia.sh start
$Starting PCMCIA services:Using /mnt/floppy/modules/pcmcia/pcmcia_core.o
Linux Kernel Card Services 3.1.22
  options:  [pci] [cardbus]
Using /mnt/floppy/modules/pcmcia/i82365.o
Intel PCIC probe: not found.
insmod: init_module: i82365: No such device
Using /mnt/floppy/modules/pcmcia/ds.o
ds: no socket drivers loaded!
insmod: init_module: ds: Operation not permitted
May 21 19:37:16 cardmgr[113]: starting version is 3.1.22
May 21 19:37:16 cardmgr[113]: config error, file 'config' line 1053: syntax error May 21 19:37:16 cardmgr[113]: config error, file 'config' line 2129: no function bindings
May 21 19:37:16 cardmgr[113]: no pcmcia driver in /proc/devices
May 21 19:37:16 cardmgr[113]: exiting
insmod: tulip.o: no module by that name found
SIOCSIFADDR: No such device
SIOCSIFNETMASK: No such device
SIOCADDRT: Network is unreachable
#

###########################################################################





Quoting Marco Fioretti <address@hidden>:


Upon your suggestion, I'm trying a network install.
However, I can't get the PCMCIA NIC to work. When
/scripts/pcmcia.sh gets to ln 96,  here's what happens:

$/sbin/insmod $PC/xirc2ps_cs.o


Gabriel,

I have *no* idea if this is even remotely related to your
problem, but have you checked the last week or so of
the fedora-list archives?
Other people were having problems with the PCMCIA
setup, and then found a solution (which I obviously
don't remember, and have no web access now, sorry...)

HTH,
Marco F.



_______________________________________________
Rule Project HOME PAGE:  http://www.rule-project.org/en/
Rule Development Site:   http://savannah.gnu.org/projects/rule/
address@hidden
http://mail.nongnu.org/mailman/listinfo/rule-list







_______________________________________________
Rule Project HOME PAGE:  http://www.rule-project.org/en/
Rule Development Site:   http://savannah.gnu.org/projects/rule/
address@hidden
http://mail.nongnu.org/mailman/listinfo/rule-list





reply via email to

[Prev in Thread] Current Thread [Next in Thread]