From owner-freebsd-mobile Mon Nov 17 09:52:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA27696 for mobile-outgoing; Mon, 17 Nov 1997 09:52:33 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA27688 for ; Mon, 17 Nov 1997 09:52:27 -0800 (PST) (envelope-from L.Vicisano@cs.ucl.ac.uk) Received: from thud.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Mon, 17 Nov 1997 17:51:44 +0000 To: freebsd-mobile@FreeBSD.ORG Subject: FreeBSD & laptop: state of the art Date: Mon, 17 Nov 1997 17:51:42 +0000 Message-ID: <3117.879789102@cs.ucl.ac.uk> From: Lorenzo VICISANO Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello everybody, I'm a new freebsd-over-laptop user (actually new laptop user!), currently running 2.2.2+PAO on a thinkpad 560. I'm happy with all the power management issues, but not as happy with pccard (sportster modem hangs the machine when going in power saving and 3C589D do the same when I unplug it `hot'). As I'm thinking of upgrading to 2.2.5, my question is: is 2.2.5 supposed to supersede PAO stuff or not? And how is it doing? I'm new in the mailing list and, though I had a look at the archive, it might be that the question has been discussed yet, sorry if it is so. cheers, Lorenzo Vicisano *--------------------*----------------------------------------------* / Lorenzo Vicisano \ http://www.cs.ucl.ac.uk/staff/L.Vicisano / / Dept. of Computer Science \ E-mail L.Vicisano@cs.ucl.ac.uk / / University College London \ Tel +44 171 419 3670 / / Gower Street, London, WC1E 6BT, UK \ Fax +44 171 387 1397 / *----------------------------------------*--------------------------* From owner-freebsd-mobile Mon Nov 17 10:52:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA03191 for mobile-outgoing; Mon, 17 Nov 1997 10:52:04 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA03184 for ; Mon, 17 Nov 1997 10:52:02 -0800 (PST) (envelope-from handy@sag.space.lockheed.com) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA09598; Mon, 17 Nov 1997 10:51:43 -0800 Date: Mon, 17 Nov 1997 10:51:43 -0800 (PST) From: "Brian N. Handy" To: Lorenzo VICISANO Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: FreeBSD & laptop: state of the art In-Reply-To: <3117.879789102@cs.ucl.ac.uk> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I'm a new freebsd-over-laptop user (actually new laptop user!), >currently running 2.2.2+PAO on a thinkpad 560. I'm happy with all the >power management issues, but not as happy with pccard (sportster modem >hangs the machine when going in power saving and 3C589D do the same >when I unplug it `hot'). A lot of changes went into the laptop support after 2.2.5 was released. I don't know how well PAO works, but 2.2-STABLE is working really well on my laptop now. (Also a TP560.) >As I'm thinking of upgrading to 2.2.5, my question is: is 2.2.5 supposed >to supersede PAO stuff or not? And how is it doing? The good stuff isn't in 2.2.5. :-( If you want the stuff that works, you'd need to upgrade to 2.2-STABLE. If I were going to do that I'd use a boot floppy from releng22.freebsd.org. Good luck, Brian From owner-freebsd-mobile Mon Nov 17 11:55:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA08608 for mobile-outgoing; Mon, 17 Nov 1997 11:55:54 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA08597 for ; Mon, 17 Nov 1997 11:55:51 -0800 (PST) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with ESMTP id MAA24847; Mon, 17 Nov 1997 12:55:45 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA27020; Mon, 17 Nov 1997 12:55:44 -0700 (MST) Date: Mon, 17 Nov 1997 12:55:44 -0700 (MST) Message-Id: <199711171955.MAA27020@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Lorenzo VICISANO Cc: freebsd-mobile@freebsd.org Subject: Re: FreeBSD & laptop: state of the art In-Reply-To: <3117.879789102@cs.ucl.ac.uk> References: <3117.879789102@cs.ucl.ac.uk> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm a new freebsd-over-laptop user (actually new laptop user!), > currently running 2.2.2+PAO on a thinkpad 560. I'm happy with all the > power management issues, but not as happy with pccard (sportster modem > hangs the machine when going in power saving and 3C589D do the same > when I unplug it `hot'). These are issues I'm currently working on right now. The serial driver still needs some changes to have it 'quit' when you unplug it 'hot', but the others cards should work now with the code in -current and -stable. > As I'm thinking of upgrading to 2.2.5, my question is: is 2.2.5 supposed > to supersede PAO stuff or not? And how is it doing? Supercede? I wouldn't got that far, but the code in 2.2.5-STABLE is developed independantly of PAO, since both the PAO code and the FreeBSD code is based on the same code that Andrew McRae wrote. However, both the PAO folks and I tend to 'share' ideas, and even code sometimes, so at any point in time the PAO code will have some better features/bugs, and at the same time FreeBSD will have some better features/bugs. For now, PAO's plusses are: 1) PCI/CardBus support - Not at all supported in FreeBSD, and I just got a report of the PCI code in 3.0-current causing problems with a PCI machine that emulates PCCARD. 2) Additional drivers not in FreeBSD. Some ethernet cards, as well as WAVELAN support and frame Grabbers. 3) Better documentation. There is virtually none in FreeBSD, so most of the setup is passed on in mailing lists. 4) Setting up modems and other cards is easier to do in PAO. Changes they've made to the pccard daemon make things *easier* to setup modems. FreeBSD's plusses are: 1) Better suspend/resume support. Simply put, it works better, although it's not perfect yet. 2) It's easier to stay 'current' with it, since the code doesn't requiring any hand-patching, and patches don't get out of date. The following are a bit religious, and I'm quite biased, so take them with a grain of salt. 3) Less bugs. Many of the 'fixes' in the PAO code are workarounds and don't attempt to find the 'real' bugs in the system. This is the main reason that many of the PAO 'fixes' haven't been integrated into the system, since hiding *real* bugs doesn't help the problem, and merely obfuscates the code un-necessarily. (Bruce just gave me a hint on why many of the modems cards don't work, so the sio patches shouldn't be necessary at some point in the future.) 4) Some of the 'feature' additions are well done, but I disagree with them on a 'architectural' view. Basically, the state of the art with pccardd should be to *simplify* it, rather than adding new features to it. So, instead of adding more code to pccardd I'd like to re-write it to make it simpler, and make the kernel code just a little bit smarter. As far as the advantages to PAO, they are all easily overcome with time and effort. 1) PCI support. Could be easily done, but I want to do it 'right', or at least more inline with the other drives in FreeBSD. 2) Driver support. Needs someone to port it to FreeBSD, or send me or another developer the card so we can port it. 3) Someone who can write (not me) can take the PAO docs and pack them up nicely into a handbook entry. 4) I'd like to re-write pccardd, so that it's a moot point. My goals, which are lofty and will never get finished completely are: 1) Finish up the suspend/resume support, or at least make things better than they are now. There are known 'misfeatures' in pccardd that are now a big deal due to changes I made in the kernel. I've got some patches out in the field now (Hi Brian!) that may help, but they may not be adequate. Also, this might involve some of the stuff Bruce mentioned regarding sio probes 2) Bring in additional drivers from PAO so that FreeBSD supports the same cards, or at least a much bigger subset. 3) PCI/CardBus support for PCIC controller 4) Simplify pccardd, extend kernel support. Some of the pccardd stuff will happen in step 1, but I think a total re-write is necessary. 5) Combo-card support. 6) CardBus support for Cards. Totally unknown, but apparently things are different enough so that the current code won't work. Nate From owner-freebsd-mobile Tue Nov 18 07:38:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA29643 for mobile-outgoing; Tue, 18 Nov 1997 07:38:26 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from kn6-045.ktvlpr.inet.fi (ari@kn6-045.ktvlpr.inet.fi [194.197.169.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA29630 for ; Tue, 18 Nov 1997 07:38:07 -0800 (PST) (envelope-from ari@kn6-045.ktvlpr.inet.fi) Received: from localhost (ari@localhost) by kn6-045.ktvlpr.inet.fi (8.8.5/8.8.5) with SMTP id RAA29351 for ; Tue, 18 Nov 1997 17:37:46 +0200 (EET) Date: Tue, 18 Nov 1997 17:37:45 +0200 (EET) From: Ari Suutari To: freebsd-mobile@freebsd.org Subject: APM and Compaq Contura 400CX Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I've been using FreeBSD-current on my Compaq Contura 400CX for some time now. Things are almost perfect, there is just one problem with suspend/resume. When I suspend the machine by pressing suspend button, apm driver seems to get PMEV_SUSPENDREQ as expected. However, in apm_suspend (in i386/apm.c), when system calls apm_processevent after calling apm_suspend_system, it receives many extraneous PMEV_SUSPENDREQ events. I guess that this is caused by bios not clearing the event correctly in this situation, since adding a small delay before calling apm_processevent makes everything to work OK. Otherwise, the system goes into infinite loop trying to process another suspend request and another and another... Eventually it crashes. I have upgraded my bios to newest version available from Compaq - no change in behaviour. Could it be possible to alter apm driver somehow (I don't know what would be the correct way to do it) to make it more tolerable for this kind of bios behaviour ? Ari Lappeenranta, Finland From owner-freebsd-mobile Tue Nov 18 12:44:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA21177 for mobile-outgoing; Tue, 18 Nov 1997 12:44:06 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA21132 for ; Tue, 18 Nov 1997 12:43:53 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA03653; Tue, 18 Nov 1997 13:43:51 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA03016; Tue, 18 Nov 1997 13:43:48 -0700 Date: Tue, 18 Nov 1997 13:43:48 -0700 Message-Id: <199711182043.NAA03016@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: APM and Compaq Contura 400CX In-Reply-To: References: X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk To: undisclosed-recipients:; > I've been using FreeBSD-current on my Compaq Contura > 400CX for some time now. Things are almost perfect, > there is just one problem with suspend/resume. > > When I suspend the machine by pressing suspend button, > apm driver seems to get PMEV_SUSPENDREQ as expected. > However, in apm_suspend (in i386/apm.c), when system > calls apm_processevent after calling apm_suspend_system, > it receives many extraneous PMEV_SUSPENDREQ events. > I guess that this is caused by bios not clearing > the event correctly in this situation, since adding > a small delay before calling apm_processevent makes > everything to work OK. Are you running the latest/greatest bits in apm.c (v1.65)? If so, how long of a delay are you using? > Otherwise, the system > goes into infinite loop trying to process another > suspend request and another and another... Eventually > it crashes. This is no good. I could easily fix this, but I'm not sure what's the best way to do this and still maintain compatability with other machines/specificiations. Fixing it to work on your machine may break it on other machines. :( Nate From owner-freebsd-mobile Tue Nov 18 16:49:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA10165 for mobile-outgoing; Tue, 18 Nov 1997 16:49:39 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from www.giovannelli.it (www.giovannelli.it [194.184.65.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA10135 for ; Tue, 18 Nov 1997 16:49:28 -0800 (PST) (envelope-from gmarco@giovannelli.it) Received: from giovannelli.it (ts1port5d.masternet.it [194.184.65.245]) by www.giovannelli.it (8.8.8/8.8.5) with ESMTP id BAA01139 for ; Wed, 19 Nov 1997 01:54:11 +0100 (MET) Message-ID: <34724617.5AFB15D@giovannelli.it> Date: Wed, 19 Nov 1997 01:51:19 +0000 From: Gianmarco Giovannelli Reply-To: gmarco@giovannelli.it X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: mobile@freebsd.org Subject: Please help me on a Sundisk card... Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am not able to get a SunDisk 15mb compactflash card working... My lucky experince with a 3com and an usr sportser 1626 is irrepetible so I need your help... ############################### Code 128 not found Code 128 not found code Unknown ignored Configuration data for card in slot 1 Tuple #1, code = 0x1 (Common memory descriptor), length = 4 000: df 72 01 ff Common memory device information: Device number 1, type Function specific, WPS = ON Speed = 7.0 x 100 ns, Memory block size = 2Kb, 1 units Tuple #2, code = 0x1c (Other conditions for common memory), length = 4 000: 03 d9 01 ff (MWAIT) (3V card) Tuple #3, code = 0x18 (JEDEC descr for common memory), length = 2 000: df 01 Tuple #4, code = 0x20 (Manufacturer ID), length = 4 000: 45 00 01 04 PCMCIA ID = 0x45, OEM ID = 0x401 Tuple #5, code = 0x15 (Version 1 info), length = 23 000: 04 01 53 75 6e 44 69 73 6b 00 53 44 50 00 35 2f 010: 33 20 30 2e 36 00 ff Version = 4.1, Manuf = [SunDisk],card vers = [SDP] Addit. info = [5/3 0.6],[ÿ] Tuple #6, code = 0x0 (Null tuple), length = 3 000: 14 08 00 Tuple #7, code = 0x21 (Functional ID), length = 2 000: 04 01 Fixed disk card - POST initialize Tuple #8, code = 0x22 (Functional EXT), length = 2 000: 01 01 Modem interface capabilities: Tuple #9, code = 0x22 (Functional EXT), length = 3 000: 02 0c 0f Data modem services available: Tuple #10, code = 0x1a (Configuration map), length = 5 000: 01 07 00 02 0f Reg len = 2, config register addr = 0x200, last config = 0x7 Registers: XXXX---- Tuple #11, code = 0x1b (Configuration entry), length = 11 000: c0 c0 a1 27 55 4d 5d 75 08 00 21 Config index = 0x0(default) Interface byte = 0xc0 (memory) +RDY/-BSY active, wait signal supported Vcc pwr: Nominal operating supply voltage: 5 x 1V Minimum operating supply voltage: 4.5 x 1V Maximum operating supply voltage: 5.5 x 1V Max current average over 10 ms: 8 x 10mA Memory space length = 0x8 Max twin cards = 1 Misc attr: (Power down supported) Tuple #12, code = 0x1b (Configuration entry), length = 6 000: 00 01 21 b5 1e 4d Config index = 0x0 Vcc pwr: Nominal operating supply voltage: 3 x 1V, ext = 0x1e Max current average over 10 ms: 4.5 x 10mA Tuple #13, code = 0x1b (Configuration entry), length = 13 000: c1 41 99 27 55 4d 5d 75 64 f0 ff ff 21 Config index = 0x1(default) Interface byte = 0x41 (I/O) +RDY/-BSY active Vcc pwr: Nominal operating supply voltage: 5 x 1V Minimum operating supply voltage: 4.5 x 1V Maximum operating supply voltage: 5.5 x 1V Max current average over 10 ms: 8 x 10mA Card decodes 4 address lines, full 8/16 Bit I/O IRQ modes: Level, Pulse IRQ level = 4 Max twin cards = 0 Misc attr: (Read-only) (Power down supported) (Ext byte = 0xff) Tuple #14, code = 0x1b (Configuration entry), length = 6 000: 01 01 21 b5 1e 4d Config index = 0x1 Vcc pwr: Nominal operating supply voltage: 3 x 1V, ext = 0x1e Max current average over 10 ms: 4.5 x 10mA Tuple #15, code = 0x1b (Configuration entry), length = 18 000: c2 41 99 27 55 4d 5d 75 ea 61 f0 01 07 f6 03 01 010: ee 21 Config index = 0x2(default) Interface byte = 0x41 (I/O) +RDY/-BSY active Vcc pwr: Nominal operating supply voltage: 5 x 1V Minimum operating supply voltage: 4.5 x 1V Maximum operating supply voltage: 5.5 x 1V Max current average over 10 ms: 8 x 10mA Card decodes 10 address lines, full 8/16 Bit I/O I/O address # 1: block start = 0x1f0 block length = 0x8 I/O address # 2: block start = 0x3f6 block length = 0x2 IRQ modes: Level, Pulse, Shared IRQ level = 14 Max twin cards = 1 Misc attr: (Power down supported) Tuple #16, code = 0x1b (Configuration entry), length = 6 000: 02 01 21 b5 1e 4d Config index = 0x2 Vcc pwr: Nominal operating supply voltage: 3 x 1V, ext = 0x1e Max current average over 10 ms: 4.5 x 10mA Tuple #17, code = 0x1b (Configuration entry), length = 18 000: c3 41 99 27 55 4d 5d 75 ea 61 70 01 07 76 03 01 010: ee 21 Config index = 0x3(default) Interface byte = 0x41 (I/O) +RDY/-BSY active Vcc pwr: Nominal operating supply voltage: 5 x 1V Minimum operating supply voltage: 4.5 x 1V Maximum operating supply voltage: 5.5 x 1V Max current average over 10 ms: 8 x 10mA Card decodes 10 address lines, full 8/16 Bit I/O I/O address # 1: block start = 0x170 block length = 0x8 I/O address # 2: block start = 0x376 block length = 0x2 IRQ modes: Level, Pulse, Shared IRQ level = 14 Max twin cards = 1 Misc attr: (Power down supported) Tuple #18, code = 0x1b (Configuration entry), length = 6 000: 03 01 21 b5 1e 4d Config index = 0x3 Vcc pwr: Nominal operating supply voltage: 3 x 1V, ext = 0x1e Max current average over 10 ms: 4.5 x 10mA Tuple #19, code = 0x1b (Configuration entry), length = 4 000: 07 00 28 d3 Config index = 0x7 Tuple #20, code = 0x14 (No link), length = 0 ############################ ################## kernel ## machine "i386" cpu "I586_CPU" ident ARTURO maxusers 10 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options "VM86" options XSERVER options ATAPI options ATAPI_STATIC #Don't do it as an LKM options KTRACE #Kernel tracing options SYSVSHM # ---------------------------------------------- # config kernel root on wd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr device wcd0 controller scbus0 device sd0 controller ppbus0 controller ppc0 at isa? port ? irq 7 vector ppcintr controller vpo0 at ppbus? # Zip Parallelo device nlpt0 at ppbus? # Stampante device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device apm0 at isa? flags 0x11 # PCCARD (PCMCIA) support controller card0 device pcic0 at card? device pcic1 at card? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? disable port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr #controller snd0 #device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr #device opl0 at isa? port 0x388 conflicts #options "SBC_IRQ=5" device ep0 at isa? port 0x300 net irq 10 vector epintr pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device bpfilter 4 ############# end kernel... This card requires a new hd entry ??? Thanks for any hints and cheats :-) -- Regards... Gianmarco "Unix expert since yesterday" http://www2.masternet.it From owner-freebsd-mobile Tue Nov 18 18:27:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA17169 for mobile-outgoing; Tue, 18 Nov 1997 18:27:36 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA17161 for ; Tue, 18 Nov 1997 18:27:29 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id TAA05640; Tue, 18 Nov 1997 19:27:27 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id TAA04043; Tue, 18 Nov 1997 19:27:26 -0700 Date: Tue, 18 Nov 1997 19:27:26 -0700 Message-Id: <199711190227.TAA04043@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: gmarco@giovannelli.it Cc: mobile@FreeBSD.ORG Subject: Re: Please help me on a Sundisk card... In-Reply-To: <34724617.5AFB15D@giovannelli.it> References: <34724617.5AFB15D@giovannelli.it> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I am not able to get a SunDisk 15mb compactflash card working... The wd driver is not patched to support PCCARD stuff, so it won't work w/out the PAO patches, or at least until someone ports the necessary stuff from PAO, test it, and sends it to me as tested code. Nate From owner-freebsd-mobile Tue Nov 18 19:11:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA20127 for mobile-outgoing; Tue, 18 Nov 1997 19:11:20 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA20121 for ; Tue, 18 Nov 1997 19:11:16 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id UAA05902; Tue, 18 Nov 1997 20:11:14 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id UAA04160; Tue, 18 Nov 1997 20:11:13 -0700 Date: Tue, 18 Nov 1997 20:11:13 -0700 Message-Id: <199711190311.UAA04160@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: HAMADA Naoki Cc: Nate Williams , freebsd-mobile@FreeBSD.org Subject: Re: APM and Compaq Contura 400CX In-Reply-To: References: <199711182043.NAA03016@mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >This is no good. I could easily fix this, but I'm not sure what's the > >best way to do this and still maintain compatability with other > >machines/specificiations. Fixing it to work on your machine may break > >it on other machines. :( > > Compaq seems to have some different idea to cope with APM. When the > APM driver sends APM_SETPWSTATE command which sets the state to > PMST_SUSPEND, the APM BIOS generates PMEV_STANDBYREQ event. Ahh, I see. Thanks for the clarification. Currently, FreeBSD doesn't support 'standby', and only does a full suspend. > Then > FreeBSD's APM driver invokes apm_suspend(), which is quite strange > because the bios requires not suspend but standby. Right, but we don't support it. > The APM driver > sends APM_SETPWSTATE command, and the APM BIOS generates > PMEV_STANDBYREQ event, so, alas, it loops infinitely until the stack > corrupts. *sigh* > Ignoring spurious PMEV_STANDBYREQ is another solution, but it must be > far from the right thing. It is, but it is probably the 'correct' things to do for now until we implement STANDBY. It should be pretty easy to implement STANDBY, but no-one has taken the time to do it, and I'm working on pccardd right now, so I'm not going to get to it anytime soon. Nate From owner-freebsd-mobile Tue Nov 18 19:16:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA20385 for mobile-outgoing; Tue, 18 Nov 1997 19:16:05 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from tokyonet-entrance.astec.co.jp (tokyonet-entrance.astec.co.jp [202.239.16.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA20380 for ; Tue, 18 Nov 1997 19:16:01 -0800 (PST) (envelope-from hamada@astec.co.jp) Received: from amont.astec.co.jp (amont.astec.co.jp [172.20.10.1]) by tokyonet-entrance.astec.co.jp (8.6.12+2.5Wb7/3.4Wbeta5-astecMX2.3) with ESMTP id LAA28522; Wed, 19 Nov 1997 11:58:01 +0900 Received: from stone.astec.co.jp (stone.astec.co.jp [172.20.10.23]) by amont.astec.co.jp (8.7.6/3.6Wbeta5-astecMX2.4) with ESMTP id LAA16964; Wed, 19 Nov 1997 11:58:09 +0900 (JST) Received: (from hamada@localhost) by stone.astec.co.jp (8.8.5/3.5W-solaris1-1.2) id LAA29706; Wed, 19 Nov 1997 11:58:00 +0900 (JST) To: Nate Williams CC: freebsd-mobile@FreeBSD.org Subject: Re: APM and Compaq Contura 400CX References: <199711182043.NAA03016@mt.sri.com> From: HAMADA Naoki Date: 19 Nov 1997 11:57:58 +0900 In-Reply-To: Nate Williams's message of 18 Nov 1997 21:05:33 -0000 Message-ID: Lines: 24 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-mobile@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams writes: >> Otherwise, the system >> goes into infinite loop trying to process another >> suspend request and another and another... Eventually >> it crashes. > >This is no good. I could easily fix this, but I'm not sure what's the >best way to do this and still maintain compatability with other >machines/specificiations. Fixing it to work on your machine may break >it on other machines. :( Compaq seems to have some different idea to cope with APM. When the APM driver sends APM_SETPWSTATE command which sets the state to PMST_SUSPEND, the APM BIOS generates PMEV_STANDBYREQ event. Then FreeBSD's APM driver invokes apm_suspend(), which is quite strange because the bios requires not suspend but standby. The APM driver sends APM_SETPWSTATE command, and the APM BIOS generates PMEV_STANDBYREQ event, so, alas, it loops infinitely until the stack corrupts. Ignoring spurious PMEV_STANDBYREQ is another solution, but it must be far from the right thing. - nao From owner-freebsd-mobile Wed Nov 19 09:43:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA04246 for mobile-outgoing; Wed, 19 Nov 1997 09:43:54 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA04224 for ; Wed, 19 Nov 1997 09:43:45 -0800 (PST) (envelope-from kent@tfd.com) Received: (from kent@localhost) by rtp.tfd.com (8.8.6/8.7.3) id MAA13425 for freebsd-mobile@freebsd.org; Wed, 19 Nov 1997 12:43:44 -0500 (EST) Date: Wed, 19 Nov 1997 12:43:44 -0500 (EST) From: Kent Hauser Message-Id: <199711191743.MAA13425@rtp.tfd.com> To: freebsd-mobile@freebsd.org Subject: need working boot floppy Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The disk on my laptop (which ran -current) just died & after replacing the disk, I need to reload freebsd. Unfortunately, the boot floppies from 3.0-97111[79]-SNAP both panic with a page fault right after the probe. The problem goes away if I remove the 3C389C ethernet card -- but of course, the ethernet install works better with the card installed. Now the qestion: can I use any old boot floppy to install 3.0-currrent? If not, could someone point me to one with a working zp0 driver. Thanks. Kent From owner-freebsd-mobile Wed Nov 19 11:23:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA14243 for mobile-outgoing; Wed, 19 Nov 1997 11:23:54 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA14227; Wed, 19 Nov 1997 11:23:47 -0800 (PST) (envelope-from handy@sag.space.lockheed.com) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA27162; Wed, 19 Nov 1997 11:23:49 -0800 Date: Wed, 19 Nov 1997 11:23:49 -0800 (PST) From: "Brian N. Handy" To: Nate Williams Cc: mobile@freebsd.org Subject: Re: cvs commit: src/etc pccard.conf.sample pccard_ether In-Reply-To: <199711191853.KAA18732@freefall.freebsd.org> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, Nate Williams wrote: >nate 1997/11/19 10:53:37 PST > > Modified files: (Branch: RELENG_2_2) > etc pccard.conf.sample pccard_ether > Log: > - MFC: > * new ACCTON card settings > * setup a default route when an ethernet card is inserted. This brings up something. I've got an ethernet card and a modem card, both often get used in a given day. Anybody come up with a good method of setting up the network stuff when you're on the modem or at home? I seem to remember PHK mentioned something about putting some personal hooks in pccard_ether. What I want to be able to do is have the boss (who's not particularly proficient at unix stuff) be able to go home, click a button in his window manager which in turn trips the hooks that clean up his routing tables so his modem will work. Same thing when it's at the office...clik another button and boom, we're talking over the ethernet card. I don't quite see how to do this without being superuser though, but maybe that's OK. I can put something together, just wondering if anyone has any really clever ideas for dealing with this. It used to never be a problem, as I had to take out the pccards all the time anyway. :-) Brian From owner-freebsd-mobile Wed Nov 19 12:23:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA22405 for mobile-outgoing; Wed, 19 Nov 1997 12:23:47 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA22381; Wed, 19 Nov 1997 12:23:34 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id VAA21099; Wed, 19 Nov 1997 21:17:17 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Brian N. Handy" cc: Nate Williams , mobile@FreeBSD.ORG Subject: Re: cvs commit: src/etc pccard.conf.sample pccard_ether In-reply-to: Your message of "Wed, 19 Nov 1997 11:23:49 PST." Date: Wed, 19 Nov 1997 21:17:16 +0100 Message-ID: <21097.879970636@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message , "B rian N. Handy" writes: >This brings up something. I've got an ethernet card and a modem card, >both often get used in a given day. Anybody come up with a good method of >setting up the network stuff when you're on the modem or at home? I seem >to remember PHK mentioned something about putting some personal hooks in >pccard_ether. > >What I want to be able to do is have the boss (who's not particularly >proficient at unix stuff) be able to go home, click a button in his window >manager which in turn trips the hooks that clean up his routing tables so >his modem will work. Same thing when it's at the office...clik another >button and boom, we're talking over the ethernet card. You should be able to do this entirely without the click. In /etc/pccard.conf you can configure a script to on on insert and remove for each card, so all you have to do is to write the two small scripts to do it. The special gyrations I had to do was because I used the ethernet card several different places, home, work &c... In your case you have two different cards for two different places, no worries :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-mobile Wed Nov 19 12:33:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA23533 for mobile-outgoing; Wed, 19 Nov 1997 12:33:58 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from kn6-045.ktvlpr.inet.fi (ari@kn6-045.ktvlpr.inet.fi [194.197.169.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA23502 for ; Wed, 19 Nov 1997 12:33:47 -0800 (PST) (envelope-from ari@kn6-045.ktvlpr.inet.fi) Received: from localhost (ari@localhost) by kn6-045.ktvlpr.inet.fi (8.8.5/8.8.5) with SMTP id WAA01181; Wed, 19 Nov 1997 22:33:06 +0200 (EET) Date: Wed, 19 Nov 1997 22:33:06 +0200 (EET) From: Ari Suutari To: Nate Williams cc: Ari Suutari , freebsd-mobile@FreeBSD.ORG Subject: Re: APM and Compaq Contura 400CX In-Reply-To: <199711182043.NAA03016@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 18 Nov 1997, Nate Williams wrote: > > it receives many extraneous PMEV_SUSPENDREQ events. > > I guess that this is caused by bios not clearing > > the event correctly in this situation, since adding > > a small delay before calling apm_processevent makes > > everything to work OK. > > Are you running the latest/greatest bits in apm.c (v1.65)? > Yep, 1.65 it is. > If so, how long of a delay are you using? > This was just an experiment. The delay is 1 second, which is quite long I guess. I could try to iterate what is the minimum. (I am also willing to test other solutions to this if needed.) > This is no good. I could easily fix this, but I'm not sure what's the > best way to do this and still maintain compatability with other > machines/specificiations. Fixing it to work on your machine may break > it on other machines. :( I tried first adding a flag into apm_suspend, which makes it just return if it has already been called. Worked also, but it doesn't feel like a very clean solution either. Ari Lappeenranta, Finland From owner-freebsd-mobile Wed Nov 19 12:49:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA25236 for mobile-outgoing; Wed, 19 Nov 1997 12:49:01 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA25219 for ; Wed, 19 Nov 1997 12:48:54 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA11942; Wed, 19 Nov 1997 13:48:52 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA06345; Wed, 19 Nov 1997 13:48:49 -0700 Date: Wed, 19 Nov 1997 13:48:49 -0700 Message-Id: <199711192048.NAA06345@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ari Suutari Cc: Nate Williams , freebsd-mobile@FreeBSD.ORG Subject: Re: APM and Compaq Contura 400CX In-Reply-To: References: <199711182043.NAA03016@mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Are you running the latest/greatest bits in apm.c (v1.65)? > > Yep, 1.65 it is. > > > If so, how long of a delay are you using? > > This was just an experiment. The delay is 1 second, which > is quite long I guess. I could try to iterate what is > the minimum. (I am also willing to test other solutions > to this if needed.) See previous email on this subject. FreeBSD doesn't (yet) support 'standby' mode, so we assume all modes are suspend modes. This is not good, so for now I think your timeout is probably adequate until standby mode is implemented. ;( Nate From owner-freebsd-mobile Wed Nov 19 17:50:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA24268 for mobile-outgoing; Wed, 19 Nov 1997 17:50:00 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from mail0.u-aizu.ac.jp (mail0.u-aizu.ac.jp [163.143.103.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA24259 for ; Wed, 19 Nov 1997 17:49:53 -0800 (PST) (envelope-from sarikaya@u-aizu.ac.jp) Received: from pross114.u-aizu.ac.jp (pross114 [163.143.180.102]) by mail0.u-aizu.ac.jp (8.8.4+2.7Wbeta4+codeconv/3.6Wbeta7internet-gw) with ESMTP id KAA18768 for ; Thu, 20 Nov 1997 10:49:49 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by pross114.u-aizu.ac.jp (8.8.4+2.7Wbeta4+codeconv/3.6Wbeta7istcmx+kanji) with ESMTP id KAA09503; Thu, 20 Nov 1997 10:49:48 +0900 (JST) Message-Id: <199711200149.KAA09503@pross114.u-aizu.ac.jp> X-Mailer: exmh version 1.6.5 12/11/95 To: freebsd-mobile@freebsd.org cc: sarikaya@u-aizu.ac.jp Subject: Wavelan NIC Date: Thu, 20 Nov 1997 10:49:48 +0900 From: Behcet Sarikaya Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On a laptop, I have installed FreeBSD 2.2.2 with PAO driver for Wavelan. Any ideas on how to configure wlp0 in rc.conf? When I insert the card, pccardd recognizes it and it displays 915 MHz although my card is 2.4 GHz? When I do ifconfig on wlp0, it shows wlp0 as an Ethernet? How to configure WaveLan subnet using WAvePoint II bridges? How to configure for Multicast support? How to configure a Wavelan ISA on a desktop? I could not locate any documentation on the above issues. Any help will be very much appreciated. PS. I am not subscribed to this malining list, please send me any replies directly and possibly cc them to freebsd-mobile. -- Behcet Sarikaya Computer Communications Lab. The University of Aizu Tsuruga, Ikki-machi, Aizu-wakamatsu City Fukushima, 965-80 Japan Tel. +81-242-37-2559 Fax. +81-242-37-2742 Home page: http://www.u-aizu.ac.jp/~sarikaya/ Extension: 3205 Extension: 3295 email: sarikaya@rsc.u-aizu.ac.jp From owner-freebsd-mobile Thu Nov 20 06:23:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA07816 for mobile-outgoing; Thu, 20 Nov 1997 06:23:11 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from kn6-045.ktvlpr.inet.fi (ari@kn6-045.ktvlpr.inet.fi [194.197.169.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA07776 for ; Thu, 20 Nov 1997 06:22:18 -0800 (PST) (envelope-from ari@kn6-045.ktvlpr.inet.fi) Received: from localhost (ari@localhost) by kn6-045.ktvlpr.inet.fi (8.8.5/8.8.5) with SMTP id QAA01823; Thu, 20 Nov 1997 16:21:57 +0200 (EET) Date: Thu, 20 Nov 1997 16:21:56 +0200 (EET) From: Ari Suutari To: Nate Williams cc: Ari Suutari , freebsd-mobile@FreeBSD.ORG Subject: Re: APM and Compaq Contura 400CX In-Reply-To: <199711192048.NAA06345@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, Nate Williams wrote: > See previous email on this subject. FreeBSD doesn't (yet) support > 'standby' mode, so we assume all modes are suspend modes. This is not > good, so for now I think your timeout is probably adequate until standby > mode is implemented. ;( > Hmm. My request was *suspend* - maybe there is something that I didn't understand ? Anyway - I can live with my current kludge since it seems to make things work in this case. Ari Lappeenranta, Finland From owner-freebsd-mobile Thu Nov 20 07:53:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA13219 for mobile-outgoing; Thu, 20 Nov 1997 07:53:44 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA13212 for ; Thu, 20 Nov 1997 07:53:41 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id IAA18827; Thu, 20 Nov 1997 08:53:37 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id IAA09960; Thu, 20 Nov 1997 08:53:36 -0700 Date: Thu, 20 Nov 1997 08:53:36 -0700 Message-Id: <199711201553.IAA09960@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Carlos A. Ugarte" Cc: nate@mt.sri.com (Nate Williams), mobile@FreeBSD.org Sender: owner-freebsd-mobile@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Subject: Re: APM and Compaq Contura 400CX In-Reply-To: <199711200447.VAA16323@lectura.CS.Arizona.EDU> References: <199711182043.NAA03016@mt.sri.com> <199711200447.VAA16323@lectura.CS.Arizona.EDU> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Bcc: nate Carlos A. Ugarte writes: > > I'm also having the same problem, with a Compaq Contura Aero. > The symptom is that by suspending the machine (either by > pushing the button or running apm -z) the machine would suspend, > but it would also panic (I'd see ddb right before the screen > would shut off). The faults were not always the same, but a few > times trace showed that apm_suspend and apm_processevent kept > calling each other resulting in a stack overflow. Right, it's because the Compaq wants to do a 'standby' instead of a supsend for some reason...??? > It turns out that PAO has a solution for this using the > APM_NOSUSPEND_IMMEDIATE option. It turns out that PAO has a hack for this, instead of a solution. A hack is better than nothing, but a solution is better than both. I'd like to see someone implement a solution to the problem rather than adding 'yet another' option for laptops. There are already too many options to keep track of, so we need to find solutions so that FreeBSD works 'out of the box' well on all laptops, and solutions to one laptop don't negatively affect another laptop. > By the way, I had first tried out PAO; I thought it was > required to get pccards to work. The pccard stuff did not work > for me, though apm was fine eventually (2.2.2-REL w/ the latest > PAO patches; couldn't get the PAO boot floppy to work either...). I > recently learned that PAO might not be necessary from one of Nate's > messages on the mailing list, so I gave it a go and now both > pccard and apm work with the base system (plus the one patch above). Great, glad to hear it. > Is there some advantage (laptop wise) that warrants > upgrading to 2.2.5-RELEASE? No, but 2.2.5-STABLE contains alot of new fixes for suspend/resume. Suspend/resume works much better now, although there are still a couple of minor (known) bugs in the support which I'm working on. Nate From owner-freebsd-mobile Thu Nov 20 07:56:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA13456 for mobile-outgoing; Thu, 20 Nov 1997 07:56:46 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA13451 for ; Thu, 20 Nov 1997 07:56:43 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id IAA18854; Thu, 20 Nov 1997 08:56:41 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id IAA09995; Thu, 20 Nov 1997 08:56:39 -0700 Date: Thu, 20 Nov 1997 08:56:39 -0700 Message-Id: <199711201556.IAA09995@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ari Suutari Cc: Nate Williams , freebsd-mobile@FreeBSD.ORG Subject: Re: APM and Compaq Contura 400CX In-Reply-To: References: <199711192048.NAA06345@mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > See previous email on this subject. FreeBSD doesn't (yet) support > > 'standby' mode, so we assume all modes are suspend modes. This is not > > good, so for now I think your timeout is probably adequate until standby > > mode is implemented. ;( > > > > Hmm. My request was *suspend* - maybe there is something > that I didn't understand ? Yes, the Compaq's APM BIOS responds with a 'suspend' request with a 'standby' request. Apparently it wants to go into standby mode before it does a full suspend or something. > Anyway - I can live with my current kludge since it > seems to make things work in this case. Great, hopefully someone will come up with the trivial code to implement standby mode. Nate From owner-freebsd-mobile Thu Nov 20 08:24:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA15252 for mobile-outgoing; Thu, 20 Nov 1997 08:24:43 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from inetserver.mpainc.com ([198.246.145.98]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA15227 for ; Thu, 20 Nov 1997 08:24:36 -0800 (PST) (envelope-from RickSiple@mpainc.com) Received: by INETSERVER with Internet Mail Service (5.0.1457.3) id ; Thu, 20 Nov 1997 11:25:17 -0500 Message-ID: <6150EE893AC3D011A3360020AFF799985F05@INETSERVER> From: Rick Siple To: "'freebsd-mobile@freebsd.org'" Subject: Port replicator with PCMCIA slots Date: Thu, 20 Nov 1997 11:25:16 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I sent this message once, but it apparently did not make it through. Exchange says it delivered it but...anyway, here is my question: I am having some trouble with the PCMCIA support in FreeBSD-2.2.5 (-stable as of Thu 11/13, CTM patch 506 if that means anything). The strange bit is this, FreeBSD will not recognize the PCI-to-PCMCIA bridge in the WinBook FX I am using (Cirrus Logic CL-6730) but it will find the bridge in the port replicator (same variety CL-6730). I had at first suspected that FreeBSD was only finding one controller and would find the internal one when undocked, but it does not. 2.2.2 exhibited the same behavior, I was hoping 2.2.5 would fix it. >From dmesg I get: ... Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 3 on pci0:1 chip2 rev 0 on pci0:17 chip3 rev 254 int a irq ?? on pci0:19 vga0 rev 0 int a irq ?? on pci0:20 Probing for devices on PCI bus 1: chip4 rev 238 int a irq ?? on pci1:10 ... ep0 not found at 0x300 PC-Card Cirrus Logic PD672X (5 mem & 2 I/O windows) pcic: controller irq 9 Initializing PC-card drivers: ep sio Card inserted, slot 1 ep0: utp/bnc[*UTP*] address 00:20:af:0e:53:7f Chips 3 and 4 seem to be the PCMCIA bridges (vendor 1013 is Cirrus Logic) as both devices id the same. Also, chips 2 and 4 are not probed if the WinBook FX is undocked (chip2 is presumably the PCI-to-PCI bridge to the port replicator). The only thing different is the rev (revision? 254 vs. 238) which might be the problem. The config file for the kernel has: # # PCCARD/PCMCIA # # crd: slot controller # pcic: slots controller card0 controller card1 controller pcic0 at card0 controller pcic1 at card0 controller pcic2 at card1 controller pcic3 at card1 Obviously I tried to add another controller (card1) and two more slots (pcic2 and 3) to no avail. There do not seem to be any IRQ, DMA, etc settings to tweak. There are four card devices in the /dev directory (card0 through card3) which seem to be the slots (not the controllers as the config file would seem to imply). There does not seem to be any device(s) that I could find that represent the slot controller(s), but I could be wrong. Ideas? Thanks. -Rick Siple RickSiple@MPAInc.com From owner-freebsd-mobile Thu Nov 20 09:36:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA20460 for mobile-outgoing; Thu, 20 Nov 1997 09:36:32 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA20454 for ; Thu, 20 Nov 1997 09:36:27 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA19514; Thu, 20 Nov 1997 10:36:25 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA10447; Thu, 20 Nov 1997 10:36:19 -0700 Date: Thu, 20 Nov 1997 10:36:19 -0700 Message-Id: <199711201736.KAA10447@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Rick Siple Cc: "'freebsd-mobile@freebsd.org'" Subject: Re: Port replicator with PCMCIA slots In-Reply-To: <6150EE893AC3D011A3360020AFF799985F05@INETSERVER> References: <6150EE893AC3D011A3360020AFF799985F05@INETSERVER> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I am having some trouble with the PCMCIA support in > FreeBSD-2.2.5 (-stable as of Thu 11/13, CTM patch 506 if that means > anything). The strange bit is this, FreeBSD will not recognize the > PCI-to-PCMCIA bridge in the WinBook FX I am using (Cirrus Logic CL-6730) > but it will find the bridge in the port replicator (same variety > CL-6730). Weird. > I had at first suspected that FreeBSD was only finding one > controller and would find the internal one when undocked, but it does > not. 2.2.2 exhibited the same behavior, I was hoping 2.2.5 would fix > it. There were no PCCARD changes made from 2.2.2 -> 2.2.5, and any changes made since that point shouldn't affect your box at all. The PAO code *may* work since it has PCI support, but until you test it it's an unknown. > There are four card devices in the /dev directory (card0 through card3) > which seem to be the slots (not the controllers as the config file would > seem to imply). Well, it depends on you how define slot and controller, but yes there is room for confusion. Nate From owner-freebsd-mobile Thu Nov 20 10:19:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA23294 for mobile-outgoing; Thu, 20 Nov 1997 10:19:13 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from church.cse.ogi.edu (cse.ogi.edu [129.95.20.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA23273 for ; Thu, 20 Nov 1997 10:19:08 -0800 (PST) (envelope-from jrb@cse.ogi.edu) Received: from church.cse.ogi.edu (localhost [127.0.0.1]) by church.cse.ogi.edu (8.8.6/8.8.6) with ESMTP id KAA04768; Thu, 20 Nov 1997 10:18:55 -0800 (PST) Message-Id: <199711201818.KAA04768@church.cse.ogi.edu> To: Behcet Sarikaya cc: freebsd-mobile@freebsd.org Subject: Re: Wavelan NIC In-reply-to: Your message of "Thu, 20 Nov 1997 10:49:48 +0900." <199711200149.KAA09503@pross114.u-aizu.ac.jp> Date: Thu, 20 Nov 1997 10:18:55 -0800 From: Jim Binkley Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Your message <199711200149.KAA09503@pross114.u-aizu.ac.jp>: >On a laptop, I have installed FreeBSD 2.2.2 with PAO driver for Wavelan. Any >ideas on how to configure wlp0 in rc.conf? > When I insert the card, pccardd recognizes it and it displays 915 MHz >although my card is 2.4 GHz? When I do ifconfig on wlp0, it shows wlp0 as an >Ethernet? You unfortunately have to compile the driver to get it to work under 2.4 GHz as I recently discovered. grep on band_2400 and you will see what I mean. #define WAVELAN_PCMCIA_24 which I believe can be set as a kernel option. > How to configure WaveLan subnet using WAvePoint II bridges? I fear I have to make a somewhat sarcastic remark. If you have the ISA cards, why use the WAvePoint II bridges? There is no roaming support in the driver, so you should turn roaming off on the bridge. Just make sure the nwids are the same. > How to configure for Multicast support? Get my driver. It is an updated and less buggy version than the one Hosokawa has. I thought I sent him a copy many moons ago but it got lost somewhere apparently. Multicast works and doesn't cause mrouted to blow up either. See http://www.cs.pdx.edu/research/SMN and download the wavelan stuff only. Warning though ... Said driver was for 2.2.older. It may need some tweaking. > How to configure a Wavelan ISA on a desktop? There exists a wl.0 man page. I don't know where it is in terms of freebsd/releases. ifconfig wl0 ... works and use wlconfig to set the magic variables or you simply do it on the dos side. > I could not locate any documentation on the above issues. > Any help will be very much appreciated. > >PS. I am not subscribed to this malining list, please send me any replies >directly and possibly cc them to freebsd-mobile. At some point I hope to have some time to hack on the if_wlp.c driver and teach it how to dynamically figure out what kind of driver it is. It also needs to be ported out of the PAO, given an understanding of "sub-channels" (or whatever they are called), a man page, and a good general all around thrashing. Jim Binkley jrb@cse.ogi.edu From owner-freebsd-mobile Thu Nov 20 11:15:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA27566 for mobile-outgoing; Thu, 20 Nov 1997 11:15:03 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from duncan.cs.utk.edu (DUNCAN.CS.UTK.EDU [128.169.94.83]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA27553 for ; Thu, 20 Nov 1997 11:14:59 -0800 (PST) (envelope-from key@cs.utk.edu) Received: from LOCALHOST.cs.utk.edu by duncan.cs.utk.edu with SMTP (cf v2.11c-UTK) id OAA10214; Thu, 20 Nov 1997 14:14:54 -0500 Message-Id: <199711201914.OAA10214@duncan.cs.utk.edu> To: freebsd-mobile@freebsd.org cc: key@cs.utk.edu Subject: boot floppies for 2.2.5-STABLE that speak PCMCIA? Date: Thu, 20 Nov 1997 14:14:53 -0500 From: Ken Key Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Folks, I've been running v2.2.2-PAO on a ThinkPad 560 w/ LinkSys EC2T. Per the comments of Nate Williams the past few weeks, it sounds like I want to run v2.2.5-STABLE (is that the same as the 2.2-YYMMDD-SNAP?) to get support for my Sony PRD-650WM Diskman (SCSI CD-ROM with rebadged Adaptec 1460) to work. When I pull the 971119 2.2 and 3.0 SNAP boot floppies, the installation procedure doesn't enable the LinkSys ed device, which makes it rather difficult to install over the net. Are there different boot floppy images I should be using for a laptop PCMCIA network install? I'm an old BSD hand but new to FreeBSD and it's installation procedures. Alternatively, does anyone have the Sony PRD650-WM working with PAO that could send me their working pccard.conf and kernel config? I can see the AIC, I just can't see the CD-ROM drive on the SCSI bus. Trying to mount /dev/cd0c wins me a "cd9660: /dev/cd0c on /mnt: Device not configured" even though the aic0 is see and the cd0 device is in the kernel. If this is not the appropriate list to ask PAO questions, please point me in the right direction. Thanks for any clues, K^2 (key@cs.utk.edu) From owner-freebsd-mobile Thu Nov 20 12:22:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA04265 for mobile-outgoing; Thu, 20 Nov 1997 12:22:48 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA04259 for ; Thu, 20 Nov 1997 12:22:42 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA20520; Thu, 20 Nov 1997 13:22:40 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA11157; Thu, 20 Nov 1997 13:22:37 -0700 Date: Thu, 20 Nov 1997 13:22:37 -0700 Message-Id: <199711202022.NAA11157@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ken Key Cc: freebsd-mobile@freebsd.org Subject: Re: boot floppies for 2.2.5-STABLE that speak PCMCIA? In-Reply-To: <199711201914.OAA10214@duncan.cs.utk.edu> References: <199711201914.OAA10214@duncan.cs.utk.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I've been running v2.2.2-PAO on a ThinkPad 560 w/ LinkSys EC2T. > Per the comments of Nate Williams the past few weeks, it sounds like > I want to run v2.2.5-STABLE (is that the same as the 2.2-YYMMDD-SNAP?) No, it's not the same. I don't believe there has been an updated 2.2.5-STABLE snap. > to > get support for my Sony PRD-650WM Diskman (SCSI CD-ROM with rebadged > Adaptec 1460) to work. Mine works great. :) > When I pull the 971119 2.2 and 3.0 SNAP boot > floppies, the installation procedure doesn't enable the LinkSys ed device, > which makes it rather difficult to install over the net. Are there > different boot floppy images I should be using for a laptop PCMCIA network > install? Can you use your existing setup to update just the sources and build from that using CVSup/CTM? That's the 'standard' way of updating, and it let's you continue to update as changes are made once you get things setup initially. The handbook has information on how to do that. I don't know anything about PAO, so I can't say. Nate From owner-freebsd-mobile Thu Nov 20 13:48:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA10983 for mobile-outgoing; Thu, 20 Nov 1997 13:48:48 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA10973 for ; Thu, 20 Nov 1997 13:48:44 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA21071; Thu, 20 Nov 1997 14:48:43 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA11511; Thu, 20 Nov 1997 14:48:40 -0700 Date: Thu, 20 Nov 1997 14:48:40 -0700 Message-Id: <199711202148.OAA11511@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ken Key Cc: Nate Williams , freebsd-mobile@freebsd.org Subject: Re: boot floppies for 2.2.5-STABLE that speak PCMCIA? In-Reply-To: <199711202142.QAA23366@duncan.cs.utk.edu> References: <199711202022.NAA11157@mt.sri.com> <199711202142.QAA23366@duncan.cs.utk.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > I've been running v2.2.2-PAO on a ThinkPad 560 w/ LinkSys EC2T. > > > Per the comments of Nate Williams the past few weeks, it sounds like > > > I want to run v2.2.5-STABLE (is that the same as the 2.2-YYMMDD-SNAP?) > > > > No, it's not the same. I don't believe there has been an updated > > 2.2.5-STABLE snap. > > Ah, I've also been pulling the RELENG_2_2 tag via cvsup, which I now assume > maps to 2.2.5-STABLE. That is true, but you're not getting a SNAP, you're getting the bits. A 'SNAP' is a snapshot/build of the sources at a particular point in time, while what you have is sources, but no binaries or any 'tested' build environment. > Now I'm confused. I had assumed the 3.0-*-SNAP's > were "freebsd-current" and the 2.2-*-SNAPS were "freebsd-stable", per the > handbook. If the 2.2-*-SNAPs aren't RELENG_2_2, what are they? I don't think there have been any SNAP's that have been made since 2.2.5 was released, so any 2.2 SNAPS won't have any post-2.2.5R changes in them. > > Can you use your existing setup to update just the sources and build > > from that using CVSup/CTM? That's the 'standard' way of updating, and > > it let's you continue to update as changes are made once you get things > > setup initially. The handbook has information on how to do that. > > That's what I eventually want to do but I'm worried about failure modes > with the upgrade interacting with PAO already on the system. There shouldn't be any failure modes interacting badly with PAO. You just need to make sure to update your /etc files with the FreeBSD versions when you do your upgrade like you would do with *ANY* source upgrade and it should go fine. > However, it now sounds like my choice for doing the wipe means putting PAO > back on after partitioning/newfs'ing and then cvsup/build/upgrade. If you put PAO back, then you're in the same boat you are in now. Nate From owner-freebsd-mobile Thu Nov 20 14:31:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA14366 for mobile-outgoing; Thu, 20 Nov 1997 14:31:12 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from duncan.cs.utk.edu (DUNCAN.CS.UTK.EDU [128.169.94.83]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA14360 for ; Thu, 20 Nov 1997 14:31:08 -0800 (PST) (envelope-from key@cs.utk.edu) Received: from LOCALHOST.cs.utk.edu by duncan.cs.utk.edu with SMTP (cf v2.11c-UTK) id QAA23366; Thu, 20 Nov 1997 16:42:20 -0500 Message-Id: <199711202142.QAA23366@duncan.cs.utk.edu> To: Nate Williams cc: Ken Key , freebsd-mobile@freebsd.org Subject: Re: boot floppies for 2.2.5-STABLE that speak PCMCIA? From: Ken Key In-reply-to: Your message of Thu, 20 Nov 1997 13:22:37 -0700. <199711202022.NAA11157@mt.sri.com> Date: Thu, 20 Nov 1997 16:42:13 -0500 Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I've been running v2.2.2-PAO on a ThinkPad 560 w/ LinkSys EC2T. > > Per the comments of Nate Williams the past few weeks, it sounds like > > I want to run v2.2.5-STABLE (is that the same as the 2.2-YYMMDD-SNAP?) > > No, it's not the same. I don't believe there has been an updated > 2.2.5-STABLE snap. Ah, I've also been pulling the RELENG_2_2 tag via cvsup, which I now assume maps to 2.2.5-STABLE. Now I'm confused. I had assumed the 3.0-*-SNAP's were "freebsd-current" and the 2.2-*-SNAPS were "freebsd-stable", per the handbook. If the 2.2-*-SNAPs aren't RELENG_2_2, what are they? Or if I'm completely confused, clues into the supfile tag to use for 2.2.5-STABLE would be appreciated. > Mine works great. :) Excellent! A goal is in sight! > Can you use your existing setup to update just the sources and build > from that using CVSup/CTM? That's the 'standard' way of updating, and > it let's you continue to update as changes are made once you get things > setup initially. The handbook has information on how to do that. That's what I eventually want to do but I'm worried about failure modes with the upgrade interacting with PAO already on the system. I also want to wipe and repartition the system, so install time sounded like a good time. However, it now sounds like my choice for doing the wipe means putting PAO back on after partitioning/newfs'ing and then cvsup/build/upgrade. Hmm, that partition map doesn't look so bad after all - I think I'll update the sources and install over the running PAO and see what happens first... Thanks for the info! K^2 -- Ken Key (key@cs.utk.edu) Univ. of Tennessee, Knoxville From owner-freebsd-mobile Thu Nov 20 15:14:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17737 for mobile-outgoing; Thu, 20 Nov 1997 15:14:43 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from grayling.erg.sri.com (grayling.erg.sri.com [128.18.4.194]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA17728 for ; Thu, 20 Nov 1997 15:14:35 -0800 (PST) (envelope-from templin@erg.sri.com) Received: by grayling.erg.sri.com (8.6.12/2.7davy) id PAA02914; Thu, 20 Nov 1997 15:14:22 -0800 Message-Id: <199711202314.PAA02914@grayling.erg.sri.com> Date: Thu, 20 Nov 1997 15:14:22 -0800 From: "Fred L. Templin" To: RickSiple@mpainc.com, freebsd-mobile@FreeBSD.ORG Subject: Re: Port replicator with PCMCIA slots Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Rick, 2.2.5 does not yet have support for multiple PCIC chips, and you only get two PC-CARD slots per PCIC chip. Your config file should work in theory, but the 2.2.5-STABLE kernel does not allow multiples yet. The PAO guys are working support for multiple PCIC's into their code base, but this code is not available in an "official" PAO release just yet... Fred templin@erg.sri.com > The config file for the kernel has: > # > # PCCARD/PCMCIA > # > # crd: slot controller > # pcic: slots > controller card0 > controller card1 > controller pcic0 at card0 > controller pcic1 at card0 > controller pcic2 at card1 > controller pcic3 at card1 > > Obviously I tried to add another controller (card1) and two more slots > (pcic2 and 3) to no avail. There do not seem to be any IRQ, DMA, etc > settings to tweak. > > There are four card devices in the /dev directory (card0 through card3) > which seem to be the slots (not the controllers as the config file would > seem to imply). There does not seem to be any device(s) that I could > find that represent the slot controller(s), but I could be wrong. > > Ideas? > > Thanks. > > -Rick Siple > RickSiple@MPAInc.com From owner-freebsd-mobile Thu Nov 20 20:08:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA09321 for mobile-outgoing; Thu, 20 Nov 1997 20:08:43 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from duncan.cs.utk.edu (DUNCAN.CS.UTK.EDU [128.169.94.83]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA09316 for ; Thu, 20 Nov 1997 20:08:37 -0800 (PST) (envelope-from key@cs.utk.edu) Received: from LOCALHOST.cs.utk.edu by duncan.cs.utk.edu with SMTP (cf v2.11c-UTK) id XAA26400; Thu, 20 Nov 1997 23:08:28 -0500 Message-Id: <199711210408.XAA26400@duncan.cs.utk.edu> To: Nate Williams cc: Ken Key , freebsd-mobile@freebsd.org Subject: Re: boot floppies for 2.2.5-STABLE that speak PCMCIA? From: Ken Key In-reply-to: Your message of Thu, 20 Nov 1997 14:48:40 -0700. <199711202148.OAA11511@mt.sri.com> Date: Thu, 20 Nov 1997 23:08:27 -0500 Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Ah, I've also been pulling the RELENG_2_2 tag via cvsup, which I now assume > > maps to 2.2.5-STABLE. > > That is true, but you're not getting a SNAP, you're getting the bits. A > 'SNAP' is a snapshot/build of the sources at a particular point in time, > while what you have is sources, but no binaries or any 'tested' build > environment. I understand. My problem is mapping your use of the term 2.2.5-STABLE into the externally visiable directory/filenames/tagnames I could find on the various archives. I'm still mounting the learning curve of FreeBSD version and branching terminology. So is it accurate to say that 2.2.5-STABLE == the head of the cvsup RELENG_2_2 tag? Does the 2.2-STABLE that Brain Handy meantion == 2.2.5-STABLE or are they actually separate branches? > I don't think there have been any SNAP's that have been made since 2.2.5 > was released, so any 2.2 SNAPS won't have any post-2.2.5R changes in > them. releng22.freebsd.com and current.freebsd.com have new 2.2-*-SNAP daily directories for the past few weeks. Your statement above makes it sound like they are not the result of the RELENG_2_2 tag at the time of the auto checkout/build but just 2.2.5-RELEASE? But I'm building from source, so it doesn't matter to me. > There shouldn't be any failure modes interacting badly with PAO. You > just need to make sure to update your /etc files with the FreeBSD > versions when you do your upgrade like you would do with *ANY* source > upgrade and it should go fine. I'm did a wholesale whack on /usr/src/ with RELENG_2_2 as of this morning, so I'm not as concerned now. I've only been on FreeBSD for the past month, so I wasn't sure if it would try to patch on top of the PAO patched files. Since I nuked them all, not a problem (I hope. Still waiting for the compile to finish before starting the install.) > > However, it now sounds like my choice for doing the wipe means putting PAO > > back on after partitioning/newfs'ing and then cvsup/build/upgrade. > > If you put PAO back, then you're in the same boat you are in now. Exactly. It allows me to get a working network connection to pull down source to compile/install the non-PAO PCMCIA/network support. The PAO boot floppy is what allows me to install v2.2.2 on the ThinkPad to begin with. I need it or a non-PAO floppy boot/install that can use the PCMCIA network card to the 2.2.5-STABLE parts down on my system. The boot.flp in 2.2-971120-SNAP doesn't do this. (I know I could do the floppy shuffle, but I'd set up a hardwired SLIP linkbefore I stooped to that. I wish I still had that Xircom PE3...) thanks for your help, K^2 -- Ken Key (key@cs.utk.edu) Univ. of Tennessee, Knoxville From owner-freebsd-mobile Thu Nov 20 21:12:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA13353 for mobile-outgoing; Thu, 20 Nov 1997 21:12:10 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id VAA13345 for ; Thu, 20 Nov 1997 21:12:06 -0800 (PST) (envelope-from handy@sag.space.lockheed.com) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA24379; Thu, 20 Nov 1997 21:11:54 -0800 Date: Thu, 20 Nov 1997 21:11:54 -0800 (PST) From: "Brian N. Handy" To: Ken Key Cc: Nate Williams , freebsd-mobile@FreeBSD.ORG Subject: Re: boot floppies for 2.2.5-STABLE that speak PCMCIA? In-Reply-To: <199711210408.XAA26400@duncan.cs.utk.edu> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >2.2.5-STABLE == the head of the cvsup RELENG_2_2 tag? Does the >2.2-STABLE that Brain Handy meantion == 2.2.5-STABLE or are they >actually separate branches? Hehe...that's "Brain Hardy", if you want to match the junkmail I get from Micro$oft. :-) When I talk "2.2-STABLE", what I mean is "RELENG_2_2". This is what you get from releng22.freebsd.org. (Or at least that day's version of it.) Brian From owner-freebsd-mobile Thu Nov 20 21:21:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA13904 for mobile-outgoing; Thu, 20 Nov 1997 21:21:25 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA13898 for ; Thu, 20 Nov 1997 21:21:18 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA23828; Thu, 20 Nov 1997 22:21:14 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id WAA13098; Thu, 20 Nov 1997 22:21:11 -0700 Date: Thu, 20 Nov 1997 22:21:11 -0700 Message-Id: <199711210521.WAA13098@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ken Key Cc: Nate Williams , freebsd-mobile@freebsd.org Subject: Re: boot floppies for 2.2.5-STABLE that speak PCMCIA? In-Reply-To: <199711210408.XAA26400@duncan.cs.utk.edu> References: <199711202148.OAA11511@mt.sri.com> <199711210408.XAA26400@duncan.cs.utk.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > version and branching terminology. So is it accurate to say that > 2.2.5-STABLE == the head of the cvsup RELENG_2_2 tag? Yes. > Does the > 2.2-STABLE that Brain Handy meantion == 2.2.5-STABLE or are they > actually separate branches? 2.2-STABLE became 2.2.5-STABLE as soon as 2.2.5-RELEASE was made (or soon thereafter). > > I don't think there have been any SNAP's that have been made since 2.2.5 > > was released, so any 2.2 SNAPS won't have any post-2.2.5R changes in > > them. > > releng22.freebsd.com and current.freebsd.com have new 2.2-*-SNAP daily > directories for the past few weeks. Your statement above makes it > sound like they are not the result of the RELENG_2_2 tag at the time > of the auto checkout/build but just 2.2.5-RELEASE? But I'm building > from source, so it doesn't matter to me. I had heard that both machines were 'down', so was not aware that they had started up again. Nate From owner-freebsd-mobile Thu Nov 20 22:27:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA17340 for mobile-outgoing; Thu, 20 Nov 1997 22:27:35 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from aryanna.quiddity.org (quiddity.org [204.139.9.231]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA17335 for ; Thu, 20 Nov 1997 22:27:32 -0800 (PST) (envelope-from winter@aryanna.quiddity.org) Received: (from winter@localhost) by aryanna.quiddity.org (8.8.8/8.8.8) id VAA00664; Thu, 20 Nov 1997 21:25:03 -0800 (PST) (envelope-from winter) Message-ID: <19971120212503.32639@quiddity.org> Date: Thu, 20 Nov 1997 21:25:03 -0800 From: Justin Johns To: freebsd-mobile@freebsd.org Subject: PC-Card modem problem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm currently running 2.2.5-STABLE as of today and I'm having problems getting my PCMCIA modem to be recognized. My laptop is a Toshiba Tecra 700CT and I have a 3C389C ethernet card and a XJ2288 modem card. I've tried various configurations for the modem card to no avail. I think this may be related to how the laptop handles serial ports because not even one of them is recognized by the kernel and one port happens to be an IR port. I've got PCMCIA modems to work before using the PAO patches, but only barely. Does anyone have any input or suggestions for my problem? Thanks. -- Justin Johns (winter@quiddity.org) PGP key: http://flag.blackened.net/winter/pgpkey.txt PGP fingerprint: 51 CE CB F4 5A 59 D9 B1 78 FB DE 4A 30 A4 C9 F2 From owner-freebsd-mobile Fri Nov 21 00:10:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA22086 for mobile-outgoing; Fri, 21 Nov 1997 00:10:28 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from mail0.u-aizu.ac.jp (mail0.u-aizu.ac.jp [163.143.103.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA22081 for ; Fri, 21 Nov 1997 00:10:20 -0800 (PST) (envelope-from sarikaya@u-aizu.ac.jp) Received: from pross114.u-aizu.ac.jp (pross114 [163.143.180.102]) by mail0.u-aizu.ac.jp (8.8.4+2.7Wbeta4+codeconv/3.6Wbeta7internet-gw) with ESMTP id RAA19078; Fri, 21 Nov 1997 17:09:55 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by pross114.u-aizu.ac.jp (8.8.4+2.7Wbeta4+codeconv/3.6Wbeta7istcmx+kanji) with ESMTP id RAA12912; Fri, 21 Nov 1997 17:09:54 +0900 (JST) Message-Id: <199711210809.RAA12912@pross114.u-aizu.ac.jp> X-Mailer: exmh version 1.6.5 12/11/95 To: Jim Binkley cc: freebsd-mobile@freebsd.org, sarikaya@u-aizu.ac.jp Subject: Re: Wavelan NIC In-reply-to: Your message of "Thu, 20 Nov 1997 10:18:55 PST." <199711201818.KAA04768@church.cse.ogi.edu> Date: Fri, 21 Nov 1997 17:09:53 +0900 From: Behcet Sarikaya Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks for the help. Today I got the wlp0 working for only ping ' ing to WavePoint II bridge, by manually doing : ifconfig wlp0 IPaddress but I could not reach any other hosts (this means that PAO driver is OK). What I really need is a working sample rc.conf for a laptop with Wavelan PCMCIA card. To what value should I set the default router? I tried to set it to WavePoint II's IP address but it did not work. Any further help will be appreciated. Regards, -- Behcet Sarikaya Computer Communications Lab. The University of Aizu Tsuruga, Ikki-machi, Aizu-wakamatsu City Fukushima, 965-80 Japan Tel. +81-242-37-2559 Fax. +81-242-37-2742 Home page: http://www.u-aizu.ac.jp/~sarikaya/ Extension: 3205 Extension: 3295 email: sarikaya@rsc.u-aizu.ac.jp From owner-freebsd-mobile Fri Nov 21 06:47:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA11964 for mobile-outgoing; Fri, 21 Nov 1997 06:47:12 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from inetserver.mpainc.com ([198.246.145.98]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA11958 for ; Fri, 21 Nov 1997 06:47:08 -0800 (PST) (envelope-from RickSiple@mpainc.com) Received: by INETSERVER with Internet Mail Service (5.0.1457.3) id ; Fri, 21 Nov 1997 09:47:50 -0500 Message-ID: <6150EE893AC3D011A3360020AFF799985F06@INETSERVER> From: Rick Siple To: freebsd-mobile@FreeBSD.ORG Subject: RE: Port replicator with PCMCIA slots Date: Fri, 21 Nov 1997 09:47:47 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > -----Original Message----- > From: Fred L. Templin [SMTP:templin@erg.sri.com] > Sent: Thursday, November 20, 1997 6:14 PM > To: RickSiple@mpainc.com; freebsd-mobile@FreeBSD.ORG > Subject: Re: Port replicator with PCMCIA slots > > Rick, > > 2.2.5 does not yet have support for multiple PCIC chips, and you only > get two PC-CARD slots per PCIC chip. Your config file should work in > theory, but the 2.2.5-STABLE kernel does not allow multiples yet. The > PAO guys are working support for multiple PCIC's into their code base, > but this code is not available in an "official" PAO release just > yet... > > Fred > templin@erg.sri.com > > Bummer, but that was what I suspected. However, FreeBSD will > still not recognize the internal PCIC when undocked. Is there any way > to force it to find the internal one, at least when undocked? > > Thanks again. > > -Rick Siple > RickSiple@MPAInc.com > > From owner-freebsd-mobile Fri Nov 21 07:20:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA14197 for mobile-outgoing; Fri, 21 Nov 1997 07:20:01 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from jli.com (jli.com [199.2.111.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA14153 for ; Fri, 21 Nov 1997 07:19:57 -0800 (PST) (envelope-from uucp@jli.com) Received: by jli.com (Smail3.1.29.1 #3) id m0xYurY-0002THC; Fri, 21 Nov 97 07:19 PST Message-Id: Received: (qmail 13233 invoked from network); 21 Nov 1997 15:10:18 -0000 Received: from softdnserror (127.0.0.1) by softdnserror with SMTP; 21 Nov 1997 15:10:18 -0000 To: Behcet Sarikaya cc: mobile@freebsd.org Subject: Re: Wavelan NIC References: <199711210809.RAA12912@pross114.u-aizu.ac.jp> In-reply-to: Your message of Fri, 21 Nov 1997 17:09:53 +0900. <199711210809.RAA12912@pross114.u-aizu.ac.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13218.880124987.1@cloud.rain.com> Date: Fri, 21 Nov 1997 07:09:47 -0800 From: Bill Trost Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Behcet Sarikaya writes: Today I got the wlp0 working for only ping ' ing to WavePoint II bridge, by manually doing : ifconfig wlp0 IPaddress but I could not reach any other hosts (this means that PAO driver is OK). What I really need is a working sample rc.conf for a laptop with Wavelan PCMCIA card. To what value should I set the default router? Presumably, you need to use an IP address, netmask, and default router that's appropriate for the ethernet the WavePunt is connected to. From owner-freebsd-mobile Fri Nov 21 08:31:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA19087 for mobile-outgoing; Fri, 21 Nov 1997 08:31:25 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA19080 for ; Fri, 21 Nov 1997 08:31:22 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id JAA04433 for ; Fri, 21 Nov 1997 09:31:20 -0700 (MST) Message-Id: <199711211631.JAA04433@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: freebsd-mobile@FreeBSD.ORG Subject: hi-laptops Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Nov 1997 09:31:20 -0700 Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I am shopping for a laptop and am considering the ibm 560x. It seems to use a different graphics chipset than the earlier 560s. Has anyone tried to run freebsd and X11 on this model? How about the newer 760 line? -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-mobile Fri Nov 21 09:06:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA21930 for mobile-outgoing; Fri, 21 Nov 1997 09:06:34 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA21921 for ; Fri, 21 Nov 1997 09:06:30 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA27784; Fri, 21 Nov 1997 10:06:28 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA14332; Fri, 21 Nov 1997 10:06:26 -0700 Date: Fri, 21 Nov 1997 10:06:26 -0700 Message-Id: <199711211706.KAA14332@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Justin Johns Cc: freebsd-mobile@freebsd.org Subject: Re: PC-Card modem problem In-Reply-To: <19971120212503.32639@quiddity.org> References: <19971120212503.32639@quiddity.org> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm currently running 2.2.5-STABLE as of today and I'm having problems > getting my PCMCIA modem to be recognized. My laptop is a Toshiba > Tecra 700CT and I have a 3C389C ethernet card and a XJ2288 modem card. Does the ethernet card work? With what driver? > I've tried various configurations for the modem card to no avail. Do you have the output of 'pccardc dumpcis' available? > I think this may be related to how the laptop handles serial ports > because not even one of them is recognized by the kernel and one port > happens to be an IR port. How FreeBSD finds your internal serial ports and how it finds the PCMCIA modem/serial ports is only slightly related. It can find one and not the other > I've got PCMCIA modems to work before using the PAO patches, but only > barely. Does anyone have any input or suggestions for my problem? Sure, what is the output of 'pccardc dumpcis'? Does your kernel have multiple serial ports configured you can try out? (sio0/sio1/sio2). Are you sure that the IRQ you are trying to use for the modem isn't in use by the serial port that FreeBSD doesn't like? Did you jump up and down 3 times, spin on your head, and spit north singing 'Mary had a Little Lamb' as defined in the handbook? (Whoops, did I forget to add the last part to the handbook. *grin*) Seriously, even if all of the above work out, Bruce pointed out a big bug in the modem/serial probing code that exists in the PCCARD code that negatively affects certain hardware. It's a fairly 'simple' fix, but requires *LOTS* of changes to the entire system. Rather than attack it, I want to finish up the 'suspend/resume' stuff and then see how things fare. Nate From owner-freebsd-mobile Fri Nov 21 09:11:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA22378 for mobile-outgoing; Fri, 21 Nov 1997 09:11:01 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA22370 for ; Fri, 21 Nov 1997 09:10:57 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA27819; Fri, 21 Nov 1997 10:10:55 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA14388; Fri, 21 Nov 1997 10:10:52 -0700 Date: Fri, 21 Nov 1997 10:10:52 -0700 Message-Id: <199711211710.KAA14388@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Behcet Sarikaya Cc: Jim Binkley , freebsd-mobile@freebsd.org Subject: Re: Wavelan NIC In-Reply-To: <199711210809.RAA12912@pross114.u-aizu.ac.jp> References: <199711201818.KAA04768@church.cse.ogi.edu> <199711210809.RAA12912@pross114.u-aizu.ac.jp> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Today I got the wlp0 working for only ping ' ing to WavePoint II bridge, by > manually doing : > ifconfig wlp0 IPaddress > but I could not reach any other hosts (this means that PAO driver is > OK). Not necessarily. The wavepoint bridge is just an ethernet/wireless 'bridge' (not a router), so you should have been able to ping any host connected to the bridge. If not, something is misconfigured. Nate From owner-freebsd-mobile Fri Nov 21 09:39:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA24895 for mobile-outgoing; Fri, 21 Nov 1997 09:39:21 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from aryanna.quiddity.org (quiddity.org [204.139.9.231]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA24883 for ; Fri, 21 Nov 1997 09:39:16 -0800 (PST) (envelope-from winter@aryanna.quiddity.org) Received: (from winter@localhost) by aryanna.quiddity.org (8.8.8/8.8.8) id IAA00605; Fri, 21 Nov 1997 08:36:35 -0800 (PST) (envelope-from winter) Message-ID: <19971121083635.10681@quiddity.org> Date: Fri, 21 Nov 1997 08:36:35 -0800 From: Justin Johns To: Nate Williams Cc: freebsd-mobile@freebsd.org Subject: Re: PC-Card modem problem References: <19971120212503.32639@quiddity.org> <199711211706.KAA14332@mt.sri.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=DocE+STaALJfprDB X-Mailer: Mutt 0.88 In-Reply-To: <199711211706.KAA14332@mt.sri.com>; from Nate Williams on Fri, Nov 21, 1997 at 10:06:26AM -0700 Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk --DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii On Fri, Nov 21, 1997 at 10:06:26AM -0700, Nate Williams wrote: > Does the ethernet card work? With what driver? Yep. It works fine with the ep0 driver. > Do you have the output of 'pccardc dumpcis' available? I'll attach the output to this message since it's kinda lengthy. ;) When I do a dumpcis, it seems to hang when it gets to the modem. Dunno why. Perhaps you can give me a clue. :) > Sure, what is the output of 'pccardc dumpcis'? Does your kernel have > multiple serial ports configured you can try out? (sio0/sio1/sio2). > Are you sure that the IRQ you are trying to use for the modem isn't in > use by the serial port that FreeBSD doesn't like? Did you jump up and > down 3 times, spin on your head, and spit north singing 'Mary had a > Little Lamb' as defined in the handbook? (Whoops, did I forget to add > the last part to the handbook. *grin*) Yep. I tried all of the above and it still didn't work. :/ Well, I didn't try the forgotten handbook entry, but that's a different story. ;) When I tried other IRQ's that I know aren't taken, it'd give a probe error. > Seriously, even if all of the above work out, Bruce pointed out a big > bug in the modem/serial probing code that exists in the PCCARD code that > negatively affects certain hardware. It's a fairly 'simple' fix, but > requires *LOTS* of changes to the entire system. Rather than attack it, > I want to finish up the 'suspend/resume' stuff and then see how things > fare. Perhaps I happen to have that certain hardware. Who knows... :) -- Justin Johns (winter@quiddity.org) PGP key: http://flag.blackened.net/winter/pgpkey.txt PGP fingerprint: 51 CE CB F4 5A 59 D9 B1 78 FB DE 4A 30 A4 C9 F2 --DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dumpcis Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 2 000: 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = reserved, 32 units Tuple #2, code = 0x17 (Attribute memory descriptor), length = 3 000: 43 02 ff Attribute memory device information: Device number 1, type EEPROM, WPS = OFF Speed = 150nS, Memory block size = 8Kb, 1 units Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 01 01 89 05 PCMCIA ID = 0x101, OEM ID = 0x589 Tuple #4, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #5, code = 0x15 (Version 1 info), length = 57 000: 04 01 33 43 6f 6d 20 43 6f 72 70 6f 72 61 74 69 010: 6f 6e 00 33 43 35 38 39 00 54 50 2f 42 4e 43 20 020: 4c 41 4e 20 43 61 72 64 20 56 65 72 2e 20 32 61 030: 00 30 30 30 30 30 32 00 ff Version = 4.1, Manuf = [3Com Corporation],card vers = [3C589] Addit. info = [TP/BNC LAN Card Ver. 2a],[000002] Tuple #6, code = 0x1a (Configuration map), length = 6 000: 02 03 00 00 01 03 Reg len = 3, config register addr = 0x10000, last config = 0x3 Registers: XX------ Tuple #7, code = 0x1b (Configuration entry), length = 15 000: c1 01 1d 71 55 35 55 54 e0 72 5d 64 30 ff ff Config index = 0x1(default) Interface byte = 0x1 (I/O) Vcc pwr: Nominal operating supply voltage: 5 x 1V Max current average over 1 second: 3 x 10mA Max current average over 10 ms: 5 x 10mA Power down supply current: 5 x 1mA Wait scale Speed = 7.0 x 100 ns RDY/BSY scale Speed = 7.0 x 100 ns Card decodes 18 address lines, full 8/16 Bit I/O IRQ modes: Level, Pulse IRQs: IOCK 1 4 5 6 8 10 11 12 14 Tuple #8, code = 0x1b (Configuration entry), length = 7 000: 03 01 71 55 26 26 54 Config index = 0x3 Vcc pwr: Nominal operating supply voltage: 5 x 1V Max current average over 1 second: 2 x 100mA Max current average over 10 ms: 2 x 100mA Power down supply current: 5 x 1mA Tuple #9, code = 0x19 (JEDEC descr for attribute memory), length = 3 000: 00 00 ff Tuple #10, code = 0x14 (No link), length = 0 Tuple #11, code = 0x10 (Checksum), length = 5 000: 89 ff 80 00 00 Checksum from offset -119, length 128, value is 0x0 Tuple #12, code = 0xff (Terminator), length = 218 000: 00 03 00 00 00 00 00 00 43 32 20 54 45 41 4d 2d 010: 45 61 72 6c 20 41 6c 64 72 69 64 67 65 2c 20 52 020: 65 78 20 41 6c 6c 65 72 73 2c 20 52 75 73 73 65 030: 6c 6c 20 43 68 61 6e 67 2c 20 44 61 76 69 64 20 040: 43 68 69 68 2c 20 48 65 72 6d 61 6e 20 4c 61 6f 050: 2c 20 47 65 6e 65 20 4c 69 6e 2c 20 4c 69 61 6e 060: 67 20 4c 69 6e 2c 20 48 69 65 6e 20 4e 67 75 79 070: 65 6e 2c 20 4b 61 70 20 53 6f 68 2c 20 47 61 72 080: 79 20 57 61 6e 67 00 ff ff ff ff ff ff ff ff ff 090: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0d0: ff ff ff ff ff ff ff ff ff ff --DocE+STaALJfprDB-- From owner-freebsd-mobile Fri Nov 21 09:47:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA25413 for mobile-outgoing; Fri, 21 Nov 1997 09:47:11 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA25403 for ; Fri, 21 Nov 1997 09:47:07 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA28060; Fri, 21 Nov 1997 10:47:05 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA14546; Fri, 21 Nov 1997 10:47:02 -0700 Date: Fri, 21 Nov 1997 10:47:02 -0700 Message-Id: <199711211747.KAA14546@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Justin Johns Cc: Nate Williams , freebsd-mobile@freebsd.org Subject: Re: PC-Card modem problem In-Reply-To: <19971121083635.10681@quiddity.org> References: <19971120212503.32639@quiddity.org> <199711211706.KAA14332@mt.sri.com> <19971121083635.10681@quiddity.org> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Does the ethernet card work? With what driver? > > Yep. It works fine with the ep0 driver. Great, just making sure you are using the PCCARD stuff. You'd be amazed at home many people try to use the zp driver and hack the code to try and make it work with the PCCARD code. > > Do you have the output of 'pccardc dumpcis' available? > > I'll attach the output to this message since it's kinda lengthy. ;) > When I do a dumpcis, it seems to hang when it gets to the modem. Dunno why. > Perhaps you can give me a clue. :) I have no clue. Does this card work under another OS? It's possible that it's faulty. You should at least get the output from pccardc. Did you try sticking it in the other slot to see if it can be read there? Nate From owner-freebsd-mobile Fri Nov 21 11:03:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA02123 for mobile-outgoing; Fri, 21 Nov 1997 11:03:26 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from aryanna.quiddity.org (quiddity.org [204.139.9.231]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA02115 for ; Fri, 21 Nov 1997 11:03:21 -0800 (PST) (envelope-from winter@aryanna.quiddity.org) Received: (from winter@localhost) by aryanna.quiddity.org (8.8.8/8.8.8) id KAA00417; Fri, 21 Nov 1997 10:00:44 -0800 (PST) (envelope-from winter) Message-ID: <19971121100044.60485@quiddity.org> Date: Fri, 21 Nov 1997 10:00:44 -0800 From: Justin Johns To: Nate Williams Cc: freebsd-mobile@freebsd.org Subject: Re: PC-Card modem problem References: <19971120212503.32639@quiddity.org> <199711211706.KAA14332@mt.sri.com> <19971121083635.10681@quiddity.org> <199711211747.KAA14546@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199711211747.KAA14546@mt.sri.com>; from Nate Williams on Fri, Nov 21, 1997 at 10:47:02AM -0700 Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, Nov 21, 1997 at 10:47:02AM -0700, Nate Williams wrote: > I have no clue. Does this card work under another OS? It's possible > that it's faulty. You should at least get the output from pccardc. Did > you try sticking it in the other slot to see if it can be read there? Yep. It works normally under (gag) NT and Win95. It also works fine on another laptop, which is a Dell Latitude XP. When I put it in the other slot it still just hangs there. -- Justin Johns (winter@quiddity.org) PGP key: http://flag.blackened.net/winter/pgpkey.txt PGP fingerprint: 51 CE CB F4 5A 59 D9 B1 78 FB DE 4A 30 A4 C9 F2 From owner-freebsd-mobile Fri Nov 21 11:05:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA02409 for mobile-outgoing; Fri, 21 Nov 1997 11:05:40 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA02398 for ; Fri, 21 Nov 1997 11:05:36 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA28591; Fri, 21 Nov 1997 12:05:28 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA14887; Fri, 21 Nov 1997 12:05:27 -0700 Date: Fri, 21 Nov 1997 12:05:27 -0700 Message-Id: <199711211905.MAA14887@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Justin Johns Cc: Nate Williams , freebsd-mobile@freebsd.org Subject: Re: PC-Card modem problem In-Reply-To: <19971121100044.60485@quiddity.org> References: <19971120212503.32639@quiddity.org> <199711211706.KAA14332@mt.sri.com> <19971121083635.10681@quiddity.org> <199711211747.KAA14546@mt.sri.com> <19971121100044.60485@quiddity.org> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I have no clue. Does this card work under another OS? It's possible > > that it's faulty. You should at least get the output from pccardc. Did > > you try sticking it in the other slot to see if it can be read there? > > Yep. It works normally under (gag) NT and Win95. It also works fine on > another laptop, which is a Dell Latitude XP. When I put it in the other slot > it still just hangs there. Sigh, this one has me stumped. Anyone else want to take a crack at it? Is it per-chance a CardBus/32bit modem card? If so, we don't support it at all, and that might explain things. Nate From owner-freebsd-mobile Fri Nov 21 11:17:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA03158 for mobile-outgoing; Fri, 21 Nov 1997 11:17:00 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA03148 for ; Fri, 21 Nov 1997 11:16:57 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA28661; Fri, 21 Nov 1997 12:16:53 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA14952; Fri, 21 Nov 1997 12:16:52 -0700 Date: Fri, 21 Nov 1997 12:16:52 -0700 Message-Id: <199711211916.MAA14952@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Steve Passe Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: hi-laptops In-Reply-To: <199711211631.JAA04433@Ilsa.StevesCafe.com> References: <199711211631.JAA04433@Ilsa.StevesCafe.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I am shopping for a laptop and am considering the ibm 560x. It seems to use > a different graphics chipset than the earlier 560s. Has anyone tried to run > freebsd and X11 on this model? If the 560X is the new CardBus machine, then it's not supported in FreeBSD. Newer CardBus/PCI machines are not supported 'out of the box' yet. The same goes for new 760's if they are also CardBus. Nate From owner-freebsd-mobile Fri Nov 21 11:20:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA03559 for mobile-outgoing; Fri, 21 Nov 1997 11:20:46 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA03543 for ; Fri, 21 Nov 1997 11:20:39 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA28688; Fri, 21 Nov 1997 12:20:30 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA14961; Fri, 21 Nov 1997 12:20:28 -0700 Date: Fri, 21 Nov 1997 12:20:28 -0700 Message-Id: <199711211920.MAA14961@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Nate Williams Cc: Steve Passe , freebsd-mobile@FreeBSD.ORG Subject: Re: hi-laptops In-Reply-To: <199711211916.MAA14952@mt.sri.com> References: <199711211631.JAA04433@Ilsa.StevesCafe.com> <199711211916.MAA14952@mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I am shopping for a laptop and am considering the ibm 560x. It seems to use >> a different graphics chipset than the earlier 560s. Has anyone tried to run >> freebsd and X11 on this model? > > If the 560X is the new CardBus machine, then it's not supported in > FreeBSD. Newer CardBus/PCI machines are not supported 'out of the box' > yet. The same goes for new 760's if they are also CardBus. ps. This is starting to really annoy me, since the PCCARD support in FreeBSD is just starting to get stable, and now they go off and change the hardware on me so it only works on old hardware. :( Nate From owner-freebsd-mobile Fri Nov 21 12:07:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA07384 for mobile-outgoing; Fri, 21 Nov 1997 12:07:47 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from gateway ([209.89.158.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA07379 for ; Fri, 21 Nov 1997 12:07:42 -0800 (PST) (envelope-from philip@gdc.ca) Received: from gdc.ca (smrc [192.34.72.10]) by gateway (SMI-8.6/gdc-gw) with ESMTP id OAA06576 for ; Fri, 21 Nov 1997 14:54:49 -0500 Received: from pc5-200 by gdc.ca (SMI-8.6/SMI-SVR4) id PAA12939; Fri, 21 Nov 1997 15:06:46 -0500 Message-ID: <3475EB8C.689E@gdc.ca> Date: Fri, 21 Nov 1997 15:14:04 -0500 From: Philip Van-Houtte Organization: General DataComm X-Mailer: Mozilla 3.01 (WinNT; I) MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Subject: Cardbus adapter for desktop. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm looking for a cardbud adapter (pci card) for a desk top system. Are these available? Thanks. Philip Van-Houtte From owner-freebsd-mobile Fri Nov 21 12:54:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA10799 for mobile-outgoing; Fri, 21 Nov 1997 12:54:55 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA10792 for ; Fri, 21 Nov 1997 12:54:52 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA29313; Fri, 21 Nov 1997 13:54:50 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA15375; Fri, 21 Nov 1997 13:54:47 -0700 Date: Fri, 21 Nov 1997 13:54:47 -0700 Message-Id: <199711212054.NAA15375@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Philip Van-Houtte Cc: freebsd-mobile@freebsd.org Subject: Re: Cardbus adapter for desktop. In-Reply-To: <3475EB8C.689E@gdc.ca> References: <3475EB8C.689E@gdc.ca> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm looking for a cardbud adapter (pci card) for a desk top system. Are > these available? If you find out anything, please report it to the list. It might be interesting to get one of those to test/debug CardBus stuff... Nate From owner-freebsd-mobile Fri Nov 21 15:46:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA25363 for mobile-outgoing; Fri, 21 Nov 1997 15:46:07 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA25356 for ; Fri, 21 Nov 1997 15:46:00 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xZ2lp-0003xY-00; Fri, 21 Nov 1997 16:45:57 -0700 Received: (from imp@localhost) by harmony.village.org (8.8.7/8.8.3) id QAA27916 for mobile@freebsd.org; Fri, 21 Nov 1997 16:48:04 -0700 (MST) Date: Fri, 21 Nov 1997 16:48:04 -0700 (MST) From: Warner Losh Message-Id: <199711212348.QAA27916@harmony.village.org> To: mobile@freebsd.org Subject: Info on a card... Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was wondering if the New Media Bus Toaster PCMCIA SCSI II Adapter is supported on FreeBSD and if so how well. Anybody out there with one? I ask because I can get one of them and a scsi cdrom for $99.00 Warner P.S. http://www.yesman.com/index.html From owner-freebsd-mobile Fri Nov 21 16:31:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA27797 for mobile-outgoing; Fri, 21 Nov 1997 16:31:27 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA27788 for ; Fri, 21 Nov 1997 16:31:21 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA00973; Fri, 21 Nov 1997 17:31:20 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA16966; Fri, 21 Nov 1997 17:31:17 -0700 Date: Fri, 21 Nov 1997 17:31:17 -0700 Message-Id: <199711220031.RAA16966@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: mobile@FreeBSD.ORG Subject: Re: Info on a card... In-Reply-To: <199711212348.QAA27916@harmony.village.org> References: <199711212348.QAA27916@harmony.village.org> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I was wondering if the New Media Bus Toaster PCMCIA SCSI II Adapter is > supported on FreeBSD and if so how well. Anybody out there with one? Well, from looking at /etc/pccard.conf.sample on a -current machine (which should be exactly the same on -stable now), the following jumps out. # NewMedia Bustoaster SCSI card "New Media" "SCSI" config 0x22 "aic0" 10 insert echo New Media Bus Toaster inserted remove echo New Media Bus Toaster removed And, since the aic0 driver works fine under both -current and -stable, I'd say it's a pretty safe bet, since the aic driver is functionally exactly the same in PAO and FreeBSD except for specific laptop suspend/resume changes. You may have to tweak the CIS information to get it to work, but if it works under PAO then it should work in FreeBSD. If you get it, I'd be very interested in seeing if it works, as well as in any changes needed made to /etc/pccard.conf (if any). Nate From owner-freebsd-mobile Fri Nov 21 16:44:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA28803 for mobile-outgoing; Fri, 21 Nov 1997 16:44:35 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id QAA28793 for ; Fri, 21 Nov 1997 16:44:29 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xZ3gS-0003z7-00; Fri, 21 Nov 1997 17:44:28 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id RAA28159; Fri, 21 Nov 1997 17:46:35 -0700 (MST) Message-Id: <199711220046.RAA28159@harmony.village.org> To: Nate Williams Subject: Re: Info on a card... Cc: mobile@freebsd.org In-reply-to: Your message of "Fri, 21 Nov 1997 17:31:17 MST." <199711220031.RAA16966@mt.sri.com> References: <199711220031.RAA16966@mt.sri.com> <199711212348.QAA27916@harmony.village.org> Date: Fri, 21 Nov 1997 17:46:35 -0700 From: Warner Losh Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199711220031.RAA16966@mt.sri.com> Nate Williams writes: : If you get it, I'd be very interested in seeing if it works, as well as : in any changes needed made to /etc/pccard.conf (if any). Sounds like it is worth the risk to me :-). I'll see what I gotta do to order it. I had hoped someone here had actually used one, but I'll have to settle for it being in pccard.conf.sample. Warner From owner-freebsd-mobile Fri Nov 21 23:44:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA20268 for mobile-outgoing; Fri, 21 Nov 1997 23:44:56 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from DonaldBurr.dyn.ml.org (206-18-115-79.la.inreach.net [206.18.115.79]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA20255 for ; Fri, 21 Nov 1997 23:44:49 -0800 (PST) (envelope-from dburr@POBoxes.com) Received: from DonaldBurr.DonaldBurr.dyn.ml.org (DonaldBurr.DonaldBurr.dyn.ml.org [192.160.60.1]) by DonaldBurr.dyn.ml.org (8.8.7/8.8.7) with SMTP id XAA18913; Fri, 21 Nov 1997 23:46:13 -0800 (PST) (envelope-from dburr@POBoxes.com) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199711212348.QAA27916@harmony.village.org> Date: Fri, 21 Nov 1997 23:44:07 -0800 (PST) Organization: Starfleet Command From: Donald Burr To: Warner Losh Subject: RE: Info on a card... Cc: mobile@FreeBSD.ORG Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- My secret spy satellite informs me that on 21-Nov-97, Warner Losh wrote: >I was wondering if the New Media Bus Toaster PCMCIA SCSI II Adapter is >supported on FreeBSD and if so how well. Anybody out there with one? The New Media card uses the AIC6[23]60 chip, which is supported by FreeBSD (you may or may not need the PAO support modules): the driver name to use is aic. I successfully installed FreeBSD on a machine using a New Media Toast'n'Jam (which is basically a Bus Toaster with an embedded sound card). - --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNHaNwvjpixuAwagxAQGw3QQApwqPAcky3Sq7dPS16gU3Z+KnI7aCvA6g pza7u/ieOkS/Hi5aWKWH3052feZNZCmOUWMprg24id1k3VVb7y/gKZ+BCr4xjT6P oa5uuq/PDzzB93cDpaQlljaHPIUtPFE9VPO+vYePoSMzS/9Gdd9Fn54ugvBKqiGd g9RVPNE7Asw= =jr9W -----END PGP SIGNATURE----- From owner-freebsd-mobile Sat Nov 22 08:33:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA13332 for mobile-outgoing; Sat, 22 Nov 1997 08:33:19 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA13320 for ; Sat, 22 Nov 1997 08:33:14 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xZIUX-0004wE-00; Sat, 22 Nov 1997 09:33:09 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id JAA03355; Sat, 22 Nov 1997 09:35:21 -0700 (MST) Message-Id: <199711221635.JAA03355@harmony.village.org> To: Donald Burr Subject: Re: Info on a card... Cc: mobile@freebsd.org In-reply-to: Your message of "Fri, 21 Nov 1997 23:44:07 PST." References: Date: Sat, 22 Nov 1997 09:35:21 -0700 From: Warner Losh Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Donald Burr writes: : >I was wondering if the New Media Bus Toaster PCMCIA SCSI II Adapter is : >supported on FreeBSD and if so how well. Anybody out there with one? : : The New Media card uses the AIC6[23]60 chip, which is supported by FreeBSD : (you may or may not need the PAO support modules): the driver name to use : is aic. I successfully installed FreeBSD on a machine using a New Media : Toast'n'Jam (which is basically a Bus Toaster with an embedded sound card). But the aic driver is known to be a total flake right now. At least for my 1522 and 1522A cards it won't work with just one item on the bus, properly terminated (my scsi cd changer). Does PAO have a better aic driver? I'll have to try it if that is the case on my desktop. If I do get the card (and it is really cheap), I think that it will give me incentive to get things working if there is some kind of problem... Warner From owner-freebsd-mobile Sat Nov 22 11:41:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA21503 for mobile-outgoing; Sat, 22 Nov 1997 11:41:07 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA21488 for ; Sat, 22 Nov 1997 11:40:58 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA08368; Sat, 22 Nov 1997 12:39:21 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA18798; Sat, 22 Nov 1997 12:39:20 -0700 Date: Sat, 22 Nov 1997 12:39:20 -0700 Message-Id: <199711221939.MAA18798@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: Donald Burr , mobile@FreeBSD.ORG Subject: Re: Info on a card... In-Reply-To: <199711221635.JAA03355@harmony.village.org> References: <199711221635.JAA03355@harmony.village.org> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > But the aic driver is known to be a total flake right now. At least > for my 1522 and 1522A cards it won't work with just one item on the > bus, properly terminated (my scsi cd changer). It works fine with the laptop cards. :) > Does PAO have a better aic driver? Nope, just slightly different laptop support that won't work in the new laptop world order. ;) Nate From owner-freebsd-mobile Sat Nov 22 11:44:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA21607 for mobile-outgoing; Sat, 22 Nov 1997 11:44:10 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA21602 for ; Sat, 22 Nov 1997 11:44:06 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA08397; Sat, 22 Nov 1997 12:43:59 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA18819; Sat, 22 Nov 1997 12:43:58 -0700 Date: Sat, 22 Nov 1997 12:43:58 -0700 Message-Id: <199711221943.MAA18819@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Alan Batie Cc: mobile@FreeBSD.ORG Subject: Re: Hot upgrades In-Reply-To: <19971122101447.61698@agora.rdrop.com> References: <19971122101447.61698@agora.rdrop.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [ Moved to -mobile ] > I just hot-upgraded my laptop from 2.1-PAO to 2.2.5, and now it's off > the net --- it seems that the pccard driver no longer accepts "default" > and "any" for interrupts and memory locations, but wants specific > numbers. 'any' for interrupt was a complete un-necessary hack since '?' was already there. 'default' for 'tuple' id's introduced bugs in the CIS parser code in pccardd, plus added a ton of complexity in already difficult to understand code. If I'm going to maintain the code I want to be able to understand it and also not have new functionality add new bugs. The tradeoff isn't worth it. :( > Which seems like a big step backwards if you ask me, but I haven't yet > gotten a chance to track down what's going on, so don't consider this > a bug report or a complaint yet (unless you know for sure that this was > what was supposed to happen :-) ). This was supposed to happen. The 'any' interrupt code won't go in, but the 'default' stuff should happen sometime, since it is a good thing. However, that's not going to be for a little while, so for now go find a nice configuration entry for your card to get it working using pccardc dumpcis. I'm sorry for breaking this support, but the code that implemented it was too nasty for me to integrate it. :( Nate From owner-freebsd-mobile Sat Nov 22 12:02:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA22642 for mobile-outgoing; Sat, 22 Nov 1997 12:02:57 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from duncan.cs.utk.edu (DUNCAN.CS.UTK.EDU [128.169.94.83]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA22623 for ; Sat, 22 Nov 1997 12:02:50 -0800 (PST) (envelope-from key@cs.utk.edu) Received: from LOCALHOST.cs.utk.edu by duncan.cs.utk.edu with SMTP (cf v2.11c-UTK) id PAA26686; Sat, 22 Nov 1997 15:02:46 -0500 Message-Id: <199711222002.PAA26686@duncan.cs.utk.edu> To: mobile@freebsd.org cc: key@cs.utk.edu Subject: Sony PRD650-WM and 2.2.5-STABLE? Date: Sat, 22 Nov 1997 15:02:44 -0500 From: Ken Key Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Folks, I compiled/installed 2.2.5-STABLE as of 11/20/97 on my TP 560 in hopes of mounting the CD in the Sony PRD650-WM (w/ Adaptec 1460), but no joy. Tweaking the ed0 kernel config and adding an entry for my LinkSys to pccard.conf got the ether back on the air and the ThinkPad sees the aic0 being inserted just like it did under PAO but I still can not access /dev/cd0c, winning a "Device not configured" (and cd0 is in my kernel config). A question for those of you who have this working - When the aic device is loaded on the insert, do you get any notifications about the CD-ROM device on the SCSI bus as well? I'm about ready to wipe and load Win95 (but it won't stay long! :-) just so I can test the darn player to make sure the drive isn't toast. I would have sworn that just after I had PAO installed I had used the CD-ROM successfully about a month ago, so it's entirely possible the drive's dead. Thanks for any info, K^2 BTW, the PCCARD kernrel config file had the aic0 nailed at irq 11 while the pccard.conf had it at irq 10 (or was it vise versa - this is off the top of my head). I tried rendevouzing on 11 as well as trying it as written without success. From owner-freebsd-mobile Sat Nov 22 13:50:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA28602 for mobile-outgoing; Sat, 22 Nov 1997 13:50:25 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA28597 for ; Sat, 22 Nov 1997 13:50:21 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA09090; Sat, 22 Nov 1997 14:50:14 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA19106; Sat, 22 Nov 1997 14:50:11 -0700 Date: Sat, 22 Nov 1997 14:50:11 -0700 Message-Id: <199711222150.OAA19106@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ken Key Cc: mobile@FreeBSD.ORG Subject: Re: Sony PRD650-WM and 2.2.5-STABLE? In-Reply-To: <199711222002.PAA26686@duncan.cs.utk.edu> References: <199711222002.PAA26686@duncan.cs.utk.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I compiled/installed 2.2.5-STABLE as of 11/20/97 on my TP 560 in hopes > of mounting the CD in the Sony PRD650-WM (w/ Adaptec 1460), but no > joy. Tweaking the ed0 kernel config and adding an entry for my > LinkSys to pccard.conf got the ether back on the air and the ThinkPad > sees the aic0 being inserted just like it did under PAO but I still > can not access /dev/cd0c, winning a "Device not configured" (and cd0 > is in my kernel config). OK so far. > A question for those of you who have this working - When the aic device > is loaded on the insert, do you get any notifications about the CD-ROM > device on the SCSI bus as well? Yes. However, when you insert the card into the machine, is it 'ON' and running (you gotta hit the play button *before* inserting it into the machine). > I'm about ready to wipe and load Win95 (but it won't stay long! :-) > just so I can test the darn player to make sure the drive isn't toast. Ahh, you haven't initialized it under Win95? Unfortunately, I couldn't get it to work at all until *after* I used under Win95. Then, it seemed to work fine from that point on, even after power-cycling and has worked since. Maybe the Win95 driver did something to the card/CD player to make it work fine, but it was required for my So y CD650. Nate From owner-freebsd-mobile Sat Nov 22 14:39:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA01072 for mobile-outgoing; Sat, 22 Nov 1997 14:39:53 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from capricorn.loopback.com (loopback.com [205.243.146.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA01064 for ; Sat, 22 Nov 1997 14:39:49 -0800 (PST) (envelope-from elazich@capricorn.loopback.com) Received: from localhost (elazich@localhost) by capricorn.loopback.com (8.8.5/8.7.3) with SMTP id QAA25158 for ; Sat, 22 Nov 1997 16:35:41 -0600 (CST) Date: Sat, 22 Nov 1997 16:35:41 -0600 (CST) From: Eli Lazich To: freebsd-mobile@freebsd.org Subject: PAO 2.2.5 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone gotten what appears to be PAO in 2.2.5 to work? I just installed and the pccard.conf file seems to not work properly. I tried my old file, from 2.2.2 to no avail. Do I need to configure PAO somehow and if so how? ELi From owner-freebsd-mobile Sat Nov 22 15:13:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA02861 for mobile-outgoing; Sat, 22 Nov 1997 15:13:01 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA02850 for ; Sat, 22 Nov 1997 15:12:57 -0800 (PST) (envelope-from kent@tfd.com) Received: (from kent@localhost) by rtp.tfd.com (8.8.6/8.7.3) id UAA13768 for freebsd-mobile@freebsd.org; Wed, 19 Nov 1997 20:33:15 -0500 (EST) Date: Wed, 19 Nov 1997 20:33:15 -0500 (EST) From: Kent Hauser Message-Id: <199711200133.UAA13768@rtp.tfd.com> To: freebsd-mobile@freebsd.org Subject: which 3.0 snapshop works for zp0? Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I get a kernel page fault at the end of the probe with the snapshot 3.0-971117-SNAP when I have my etherlink III (ie zp0) installed. Since the generic kernel does not include the `card' device, I need to have a working ethernet to build a kernel so I can use the pccardd instead of zp0. What's the easiest way to bootstrap here? Or put another way, when did the `zp0' interface get broken? Or yet another way -- am I the only who is having trouble? Thanks for the help. Kent From owner-freebsd-mobile Sat Nov 22 16:12:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA05813 for mobile-outgoing; Sat, 22 Nov 1997 16:12:23 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA05808 for ; Sat, 22 Nov 1997 16:12:18 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA09895; Sat, 22 Nov 1997 17:12:17 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA19442; Sat, 22 Nov 1997 17:12:15 -0700 Date: Sat, 22 Nov 1997 17:12:15 -0700 Message-Id: <199711230012.RAA19442@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eli Lazich Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: PAO 2.2.5 In-Reply-To: References: X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Has anyone gotten what appears to be PAO in 2.2.5 to work? I just > installed and the pccard.conf file seems to not work properly. I tried my > old file, from 2.2.2 to no avail. Do I need to configure PAO somehow and > if so how? What doesn't work? Nate From owner-freebsd-mobile Sat Nov 22 16:13:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA05870 for mobile-outgoing; Sat, 22 Nov 1997 16:13:53 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA05859 for ; Sat, 22 Nov 1997 16:13:49 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA09899; Sat, 22 Nov 1997 17:13:48 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA19449; Sat, 22 Nov 1997 17:13:47 -0700 Date: Sat, 22 Nov 1997 17:13:47 -0700 Message-Id: <199711230013.RAA19449@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Kent Hauser Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: which 3.0 snapshop works for zp0? In-Reply-To: <199711200133.UAA13768@rtp.tfd.com> References: <199711200133.UAA13768@rtp.tfd.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I get a kernel page fault at the end of the probe with the snapshot > 3.0-971117-SNAP when I have my etherlink III (ie zp0) installed. > Since the generic kernel does not include the `card' device, I > need to have a working ethernet to build a kernel so I can use the > pccardd instead of zp0. > > What's the easiest way to bootstrap here? Or put another way, when > did the `zp0' interface get broken? Or yet another way -- am I the > only who is having trouble? Umm, it *should* work fine under 3.0. What kind of error are you seeing? The file hasn't changed significantly in almost a year. Nate From owner-freebsd-mobile Sat Nov 22 17:39:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA09735 for mobile-outgoing; Sat, 22 Nov 1997 17:39:09 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from duncan.cs.utk.edu (DUNCAN.CS.UTK.EDU [128.169.94.83]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA09727 for ; Sat, 22 Nov 1997 17:39:05 -0800 (PST) (envelope-from key@cs.utk.edu) Received: from LOCALHOST.cs.utk.edu by duncan.cs.utk.edu with SMTP (cf v2.11c-UTK) id UAA21467; Sat, 22 Nov 1997 20:38:50 -0500 Message-Id: <199711230138.UAA21467@duncan.cs.utk.edu> To: Nate Williams cc: Ken Key , mobile@freebsd.org Subject: Re: Sony PRD650-WM and 2.2.5-STABLE? From: Ken Key In-reply-to: Your message of Sat, 22 Nov 1997 14:50:11 -0700. <199711222150.OAA19106@mt.sri.com> Date: Sat, 22 Nov 1997 20:38:48 -0500 Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > A question for those of you who have this working - When the aic device > > is loaded on the insert, do you get any notifications about the CD-ROM > > device on the SCSI bus as well? > > Yes. However, when you insert the card into the machine, is it 'ON' > and running (you gotta hit the play button *before* inserting it into > the machine). Yup, did that as that's what the manual said to do for Win95 usage (kind of annoying). > > I'm about ready to wipe and load Win95 (but it won't stay long! :-) > > just so I can test the darn player to make sure the drive isn't toast. > > Ahh, you haven't initialized it under Win95? Unfortunately, I couldn't > get it to work at all until *after* I used under Win95. Then, it seemed > to work fine from that point on, even after power-cycling and has worked > since. Maybe the Win95 driver did something to the card/CD player to > make it work fine, but it was required for my So y CD650. Hmmm, this sort of jibes with what I was putting down to flakey memory. I did run it on Win95 to check out the machine, the card, etc - get a baseline of how things work the way the vendor's most expected. I then installed (at the time) PAO w/ 2.2.5 and I would have sworn I did it via the CD! (I was transitioning jobs and setting up 4 different systems and I'm just not sure). Then I didn't use the drive for about 3 weeks and wham-o, the mail you've seen from me thus far. I wanted to repartition the machine and make a small partition for Win95 or whatever OS du jure I might want to play with (2-gig drive). Now I am doubly motivated. Thanks a bunch for your help! K^2 PS. What's the procedure for submitting working new pccard.conf entries? I have a working LinkSys entry that was on PAO's "Send me mail if this works..." list and not in the 2.2.5-STABLE pccard.conf. -- Ken Key (key@cs.utk.edu) Univ. of Tennessee, Knoxville From owner-freebsd-mobile Sat Nov 22 17:53:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA10278 for mobile-outgoing; Sat, 22 Nov 1997 17:53:02 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA10271 for ; Sat, 22 Nov 1997 17:52:58 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id SAA10433; Sat, 22 Nov 1997 18:52:56 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id SAA19613; Sat, 22 Nov 1997 18:52:53 -0700 Date: Sat, 22 Nov 1997 18:52:53 -0700 Message-Id: <199711230152.SAA19613@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ken Key Cc: Nate Williams , mobile@freebsd.org Subject: Re: Sony PRD650-WM and 2.2.5-STABLE? In-Reply-To: <199711230138.UAA21467@duncan.cs.utk.edu> References: <199711222150.OAA19106@mt.sri.com> <199711230138.UAA21467@duncan.cs.utk.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > PS. What's the procedure for submitting working new pccard.conf > entries? Either send it to mobile, or to me directly. > I have a working LinkSys entry that was on PAO's "Send me mail if this > works..." list and not in the 2.2.5-STABLE pccard.conf. Nate From owner-freebsd-mobile Sat Nov 22 18:48:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA12703 for mobile-outgoing; Sat, 22 Nov 1997 18:48:53 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from capricorn.loopback.com (loopback.com [205.243.146.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA12697 for ; Sat, 22 Nov 1997 18:48:48 -0800 (PST) (envelope-from elazich@capricorn.loopback.com) Received: from localhost (elazich@localhost) by capricorn.loopback.com (8.8.5/8.7.3) with SMTP id UAA25849; Sat, 22 Nov 1997 20:44:37 -0600 (CST) Date: Sat, 22 Nov 1997 20:44:37 -0600 (CST) From: Eli Lazich To: Nate Williams cc: freebsd-mobile@FreeBSD.ORG Subject: Re: PAO 2.2.5 In-Reply-To: <199711230012.RAA19442@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have a 3com 3c589b ethernet card that appears to be recognized as zp0 but is not configurable if I run ifconfig -a. Under PAO-2.2.2 it was configured as ep0. I also have a Motorola Montana Modem that does not get recognized at all. Eli On Sat, 22 Nov 1997, Nate Williams wrote: > > Has anyone gotten what appears to be PAO in 2.2.5 to work? I just > > installed and the pccard.conf file seems to not work properly. I tried my > > old file, from 2.2.2 to no avail. Do I need to configure PAO somehow and > > if so how? > > What doesn't work? > > > Nate > From owner-freebsd-mobile Sat Nov 22 22:06:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA21461 for mobile-outgoing; Sat, 22 Nov 1997 22:06:00 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA21456 for ; Sat, 22 Nov 1997 22:05:55 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA11719; Sat, 22 Nov 1997 23:05:47 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id XAA19910; Sat, 22 Nov 1997 23:05:45 -0700 Date: Sat, 22 Nov 1997 23:05:45 -0700 Message-Id: <199711230605.XAA19910@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eli Lazich Cc: Nate Williams , freebsd-mobile@FreeBSD.ORG Subject: Re: PAO 2.2.5 In-Reply-To: References: <199711230012.RAA19442@mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have a 3com 3c589b ethernet card that appears to be recognized as zp0 > but is not configurable if I run ifconfig -a. How do you know it's recognized? It's possible that the configuration values stored in the card's EEPROM are different than what the FreeBSD driver expects. The zp0 driver is not a 'PCMCIA/generic' driver, so it uses the card's own built-in configuratio (port, IRQ, IOMEM) values to configure the card, similar to a 'point driver' in DOS. > Under PAO-2.2.2 it was configured as ep0. The default FreeBSD boot floppy doesn't have generic PCCARD support in it. You need to build a special kernel with PCCARD support (which will cause your ethernet driver to be ep0, like in PAO.) > I also have a Motorola Montana Modem that does not get > recognized at all. See above. The boot floppy laptop drivers are zp0/ze0, and work with the 3Com 589 and IBM Info-mover cards respectively. No other laptop/PCMCIA cards are supported on the boot floppy. Nate