From owner-freebsd-mobile Mon Apr 7 09:15:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA20627 for mobile-outgoing; Mon, 7 Apr 1997 09:15:03 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA20606 for ; Mon, 7 Apr 1997 09:14:53 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA09777; Mon, 7 Apr 1997 10:14:21 -0600 (MDT) Date: Mon, 7 Apr 1997 10:14:21 -0600 (MDT) Message-Id: <199704071614.KAA09777@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Gianmarco Giovannelli Cc: mobile@freebsd.org Subject: Re: I need help for Usr Sportser v34 :-) In-Reply-To: <334A2E94.41C67EA6@scotty.masternet.it> References: <334A2E94.41C67EA6@scotty.masternet.it> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I am finally succeded in using my 3c589c pcmcia card , but I am still > not able to configure the usr sportser v34 (33.6). Congratulations on the first, and we'll get the second working in a few minutes. > Here is the pccardc dumpcis output : Thanks, this is perfect for what we need. First, a question. Are you using the PAO code or what code? The dumpcis output seems corrupted, and I'd like to know how to blame, me or someone else. :) > Tuple #5, code = 0x1b (Configuration entry), length = 16 > 000: e0 41 99 49 55 26 25 aa 60 f8 03 07 30 ff ff 28 > Config index = 0x20(default) ^^^^ This is the index you have chosen. > Interface byte = 0x41 (I/O) +RDY/-BSY active > Vcc pwr: > Nominal operating supply voltage: 5 x 1V > Continuous supply current: 2 x 100mA > Power down supply current: 2 x 10mA > Card decodes 10 address lines, 8 Bit I/O only > I/O address # 1: block start = 0x3f8 block length = 0x8 ^^^^^ This is 'sio0', which probably conflicts with you built-in serial card. You probably want. > IRQ modes: Level > IRQs: 4 5 8 9 10 11 12 13 14 15 > Max twin cards = 0 > Misc attr: (Audio-BVD2) (Power down supported) > Tuple #6, code = 0x1b (Configuration entry), length = 7 > 000: 21 08 aa 60 f8 02 07 > Config index = 0x21 > Card decodes 10 address lines, 8 Bit I/O only > Tuple #7, code = 0x1b (Configuration entry), length = 7 > 000: 22 08 aa 60 e8 03 07 > Config index = 0x22 ^^^^ > Card decodes 10 address lines, 8 Bit I/O only > I/O address # 1: block start = 0x3e8 block length = 0x8 ^^^^^ sio2. I suspect idex 0x21 is the one you want even though the output is corrupted. > Tuple #8, code = 0x1b (Configuration entry), length = 7 > 000: 23 08 aa 60 e8 02 07 > Config index = 0x23 > Card decodes 10 address lines, 8 Bit I/O only > I/O address # 1: block start = 0x2e8 block length = 0x8 ^^^^^ sio3 > --- end --- > > and here is /etc/pccard.conf > > --- begin --- > > # Sample PCCARD configuration file > [...] > # Generally available IO ports > io 0x240-0x360 > # Generally available IRQs (Built-in sound-card owners remove 5) > irq 9 10 11 15 > # Available memory slots > memory 0xd4000 96k > > # 3Com Etherlink III 3C589B, 3C589C > card "3Com Corporation" "3C589" > config 0x1 "ep0" ? > insert echo 3Com Etherlink III inserted > # insert /etc/pccard_ether ep0 -link0 link1 > insert /etc/pccard_ether ep0 link0 -link1 > remove echo 3Com Etherlink III removed > remove /sbin/ifconfig ep0 delete > > # US Robotics COURIER PCMCIA V.34 > card "U.S. Robotics" "1626" > config 0x20 "sio2" ? ^^^^ > insert echo USRobotics PCMCIA Modem inserted > remove echo USRobotics PCMCIA Modem removed >From the looks of things, you'll want to changes this line to > config 0x21 "sio1" ? *OR* > config 0x22 "sio2" ? and it should work with a kernel modification. > and here there is the relevant part of the kernel config file > > --- begin --- > > # > # Laptop support (see LINT for more options) > # > device apm0 at isa? disable # Advanced Power Management > options APM_BROKEN_STATCLOCK # Workaround some buggy APM BIOS > > # PCCARD (PCMCIA) support > controller crd0 > device pcic0 at crd? > device pcic1 at crd? > > device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr > siointr You'll need to add another serial line here, so the pccard driver has something to use. The first one is for your built-in serial line, and the second one is for you pccard. Whatever serial line you use make sure that it's used above in the /etc/pccard.conf config line. > laptop is a IBM 365XD , with an intel pcmcia controller. > FreeBSD is 2.2.1 (ctm #215) *Ouch* that means it's my problem, unless you've patched it with the PAO stuff. :( > 1) What I wrong for the usr modem card ? Everytime I insert it says > :"Resource allocation failure for U.S. Robotics ...." > Is the config 0x20 the right one ? Any hints ? > I am sorry, but I am not still able to find a little documentation. I > understand a little more reading the PAO readme files, but I don't use > it... See above. > 2) When the kernel boots it first complains about the lack of the ep0 > (it presumes it is an isa card, as I can seen from the kernel). Then it > recognizes as pcmcia card. Is it a correct way of doing thing ? Yes, that is correct. It didn't find a 'normal' ethernet device, so the device driver is available for the PCCARD system to use. > 3) When it recognizes it as card it outputs the string on the boot > screen in a random position. Is it correct ? Or have I to modify > something to have things goes like so : "Slot 0 : ep0 , address ....etc > etc" . Yes I know the important thing is that card works but .... No one has taken the time to make the output look 'pretty'. For now, ignore it. > 4) For use the modem pcmcia must I compile my kernel with a more sio > added ...? In other words have I to add the line of the sio that will > use the modem after it is recognized ... ? Yes, although it doesn't matter which line you use as long as the built-in hardware doesn't use it. The PCCARD code will correctly select the necessary parameters. Nate