From owner-freebsd-mobile Mon Jul 6 08:28:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25143 for freebsd-mobile-outgoing; Mon, 6 Jul 1998 08:28:49 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from jli.com (jli.com [199.2.111.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA25133 for ; Mon, 6 Jul 1998 08:28:44 -0700 (PDT) (envelope-from trost@cloud.rain.com) Received: (qmail 20457 invoked by uid 4); 6 Jul 1998 15:28:12 -0000 Received: (qmail 3472 invoked from network); 6 Jul 1998 15:27:33 -0000 Received: from softdnserror (HELO cloud.rain.com) (127.0.0.1) by softdnserror with SMTP; 6 Jul 1998 15:27:33 -0000 To: Steve Tracy cc: freebsd-mobile@FreeBSD.ORG Subject: Re: ActionTec FastNet pccard.conf entry References: <199807030454.VAA04057@antipodes.cdrom.com> In-reply-to: Your message of Thu, 02 Jul 1998 21:54:17 PDT. <199807030454.VAA04057@antipodes.cdrom.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3468.899738852.1@cloud.rain.com> Date: Mon, 06 Jul 1998 08:27:32 -0700 Message-ID: <3469.899738852@cloud.rain.com> From: Bill Trost Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith writes: ... A 16-byte I/O window, as well as 1K and 16K memory windows - this is not an NE2000. ... > card "PMX " "PE-200" > config 0x1 "ed0" 13 0x10 > insert echo ActionTec PCMCIA Ethernet inserted > insert /etc/pccard_ether ed0 > remove echo ActionTec PCMCIA Ethernet removed > remove /sbin/ifconfig ed0 delete Ah yes, this looks like the Card of Doom. I had the honor of being the first person on the list to take one of these back to the place I bought it. )-: I once did get contacted by someone who got this card to work, but I lost track of him and vice-versa. Enjoy your trip back to the computer store.... )-: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Jul 6 14:18:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20197 for freebsd-mobile-outgoing; Mon, 6 Jul 1998 14:18:26 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA20178 for ; Mon, 6 Jul 1998 14:18:17 -0700 (PDT) (envelope-from dcmyers@concord.Corp.Sun.COM) Received: from Corp.Sun.COM ([129.145.35.78]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id OAA15936 for ; Mon, 6 Jul 1998 14:17:46 -0700 Received: from concord.Corp.Sun.COM by Corp.Sun.COM (SMI-8.6/SMI-5.3) id OAA04065; Mon, 6 Jul 1998 14:17:46 -0700 Received: from concord.corp.sun.com by concord.Corp.Sun.COM (SMI-8.6/SMI-SVR4) id OAA27023; Mon, 6 Jul 1998 14:17:40 -0700 Message-Id: <199807062117.OAA27023@concord.Corp.Sun.COM> Date: Mon, 6 Jul 1998 14:17:37 -0700 (PDT) From: david.myers@Corp.Sun.COM Subject: More on Adaptec SlimSCSI timeouts... To: freebsd-mobile@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Folks: I got a number of responses to my question about device timeouts while using the Adaptec 1460A SlimSCSI device; most asked me if I had checked termination and cabling. Yes, the bus is properly terminated, with the last device in the chain providing termination power. Windows has no trouble accessing the attached SCSI devices, so I believe that the hardware is not the problem. To recap: the card is recognized as aic0 by the PAO-980430 PCMCIA drivers, gets attached properly, and manages to locate all SCSI devices. But every time I try to access a SCSI device, I get a long delay, and ultimately a SCSI timeout message on the console. Laptop is a Toshiba 440CDT. Again, any help in diagnosing the problem would be greatly appreciated. -David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Jul 6 15:22:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01922 for freebsd-mobile-outgoing; Mon, 6 Jul 1998 15:22:15 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from mindcrime.termfrost.org (mindcrime.termfrost.org [208.141.2.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01914 for ; Mon, 6 Jul 1998 15:22:12 -0700 (PDT) (envelope-from mandrews@termfrost.org) Received: from localhost (mandrews@localhost) by mindcrime.termfrost.org (8.9.1/8.9.1/mindcrime-19980706) with SMTP id SAA07222; Mon, 6 Jul 1998 18:21:33 -0400 (EDT) (envelope-from mandrews@termfrost.org) Date: Mon, 6 Jul 1998 18:21:33 -0400 (EDT) From: Mike Andrews To: Bill Trost cc: Steve Tracy , freebsd-mobile@FreeBSD.ORG Subject: Re: ActionTec FastNet pccard.conf entry In-Reply-To: <3469.899738852@cloud.rain.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ah yes, I meant to follow up on this... I too gave up on mine. The patches I got from you made it get at least a little further... it found the first memory block, the IO space, and an IRQ, then locked the machine up *hard* trying to attach the device. It made it as far as the last ioctl call in cardd.c, which never returned. I'm trying to remember if I ever made it panic, or just freeze. I think freezing only. I gave up and (still being a cheapskate) bought a Linksys card, which worked perfectly almost immediately. (I couldn't quite afford a 3com card at the time.) Anyone who has more time to hack on these things want my card? It's way too late for me to return mine to the store I bought it from -- it's been years. It wasn't much fun to get going under DOS or Win95 either, but it can at least be done there. It's rumored to work on Linux, though I haven't actually tried... Mike Andrews (MA12) icq 6602506 -------------- mandrews@dcr.net Senior Systems/Network Administrator --- mandrews@termfrost.org Digital Crescent, Frankfort, KY ----- http://www.termfrost.org/ "Eagles may soar, but weasels don't get sucked into jet engines." -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/MU d- s: a- C++ UBX++++ P++ L+ !E W+++ N++ K++ w--- O+ M+ V+++ PS+++ PE- Y+ !t !5 !X !R tv- b+ DI++ D++ e++ h++ r++ y++*@ -----END GEEK CODE BLOCK----- On Mon, 6 Jul 1998, Bill Trost wrote: > Mike Smith writes: > ... > > A 16-byte I/O window, as well as 1K and 16K memory windows - this is > not an NE2000. > > ... > > card "PMX " "PE-200" > > config 0x1 "ed0" 13 0x10 > > insert echo ActionTec PCMCIA Ethernet inserted > > insert /etc/pccard_ether ed0 > > remove echo ActionTec PCMCIA Ethernet removed > > remove /sbin/ifconfig ed0 delete > > Ah yes, this looks like the Card of Doom. I had the honor of being the > first person on the list to take one of these back to the place I bought > it. )-: > > I once did get contacted by someone who got this card to work, but I > lost track of him and vice-versa. > > Enjoy your trip back to the computer store.... )-: > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Jul 6 19:08:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25394 for freebsd-mobile-outgoing; Mon, 6 Jul 1998 19:08:27 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from jazz.viagenie.qc.ca (jazz.viagenie.qc.ca [206.123.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25337 for ; Mon, 6 Jul 1998 19:08:14 -0700 (PDT) (envelope-from Florent.Parent@viagenie.qc.ca) Received: from blues (riq-129-47.riq.qc.ca [199.84.129.47]) by jazz.viagenie.qc.ca (Viagenie/8.8.8) with SMTP id WAA16053; Mon, 6 Jul 1998 22:02:12 -0400 (EDT) Message-Id: <3.0.5.32.19980706220705.009b8d90@jazz.viagenie.qc.ca> X-Sender: parent@jazz.viagenie.qc.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 06 Jul 1998 22:07:05 -0400 To: david.myers@Corp.Sun.COM From: Florent Parent Subject: Re: More on Adaptec SlimSCSI timeouts... Cc: freebsd-mobile@FreeBSD.ORG In-Reply-To: <199807062117.OAA27023@concord.Corp.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 14:17 06/07/98 -0700, david.myers@Corp.Sun.COM wrote: > > >Folks: > >I got a number of responses to my question about device timeouts while >using the Adaptec 1460A SlimSCSI device; most asked me if I had checked >termination and cabling. Yes, the bus is properly terminated, with the >last device in the chain providing termination power. Windows has no >trouble accessing the attached SCSI devices, so I believe that the >hardware is not the problem. To recap: the card is recognized as aic0 >by the PAO-980430 PCMCIA drivers, gets attached properly, and manages to >locate all SCSI devices. But every time I try to access a SCSI device, >I get a long delay, and ultimately a SCSI timeout message on the >console. Laptop is a Toshiba 440CDT. > >Again, any help in diagnosing the problem would be greatly appreciated. > >-David Hi David, I observe the same symptoms with a Compaq Armada 1598 and a 1460A (not 1460B) SlimSCSI. I'm using 2.2.6-release without the PAO. The devices are recognized by the scsi card (although after a ~30 sec delay during which my laptop is completly frozen). After that, no response (mount, disklabel...) from the device (tried Zip drive and then a CDROM). I was about to get some new SCSI cables to do some more tests. Anyone has a working setup with an Adaptec 1460A SlimSCSI ? Florent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Jul 6 21:12:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15012 for freebsd-mobile-outgoing; Mon, 6 Jul 1998 21:12:35 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14988 for ; Mon, 6 Jul 1998 21:12:31 -0700 (PDT) (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 WAA04596; Mon, 6 Jul 1998 22:12:22 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id WAA22765; Mon, 6 Jul 1998 22:12:20 -0600 Date: Mon, 6 Jul 1998 22:12:20 -0600 Message-Id: <199807070412.WAA22765@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Florent Parent Cc: david.myers@Corp.Sun.COM, freebsd-mobile@FreeBSD.ORG Subject: Re: More on Adaptec SlimSCSI timeouts... In-Reply-To: <3.0.5.32.19980706220705.009b8d90@jazz.viagenie.qc.ca> References: <199807062117.OAA27023@concord.Corp.Sun.COM> <3.0.5.32.19980706220705.009b8d90@jazz.viagenie.qc.ca> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Anyone has a working setup with an Adaptec 1460A SlimSCSI ? Since I ported the driver to FreeBSD, I guess I can say yes. :) However, I haven't tested it since 2.2.5R, since I was laptop-less during the 2.2.5-2.2.6 transition. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Jul 7 03:19:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA03037 for freebsd-mobile-outgoing; Tue, 7 Jul 1998 03:19:58 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from mail3.mailsorter.net (mail3.mailsorter.net [209.132.10.33] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA03032 for ; Tue, 7 Jul 1998 03:19:57 -0700 (PDT) (envelope-from jose@nobody.org) Received: from nohow.demon.co.uk ([131.227.178.102]) by mail3.mailsorter.net (Netscape Mail Server v2.02) with ESMTP id AAA12330 for ; Tue, 7 Jul 1998 03:19:22 -0700 Received: from localhost (jose@localhost) by nohow.demon.co.uk (8.8.8/8.8.8) with SMTP id LAA17983 for ; Tue, 7 Jul 1998 11:19:20 +0100 (BST) (envelope-from jose@nohow.demon.co.uk) Date: Tue, 7 Jul 1998 11:19:20 +0100 (BST) From: Jose Marques To: freebsd-mobile@FreeBSD.ORG Subject: Product support question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Do anybody know if FreeBSD would support the following product: http://www.microtech-pc.com/english/products_xpressdock.html It's an PCMCIA hard-disk controller that allows one to connect bare IDE drives. -- Jose Marques To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Jul 7 09:59:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27824 for freebsd-mobile-outgoing; Tue, 7 Jul 1998 09:59:41 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from jli.com (jli.com [199.2.111.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA27807 for ; Tue, 7 Jul 1998 09:59:36 -0700 (PDT) (envelope-from trost@cloud.rain.com) Received: (qmail 4666 invoked by uid 4); 7 Jul 1998 16:58:59 -0000 Received: (qmail 3847 invoked from network); 7 Jul 1998 16:58:20 -0000 Received: from softdnserror (HELO cloud.rain.com) (127.0.0.1) by softdnserror with SMTP; 7 Jul 1998 16:58:20 -0000 To: Florent Parent , freebsd-mobile@FreeBSD.ORG To: david.myers@Corp.Sun.COM Subject: Re: More on Adaptec SlimSCSI timeouts... References: <3.0.5.32.19980706220705.009b8d90@jazz.viagenie.qc.ca> In-reply-to: Your message of Mon, 06 Jul 1998 22:07:05 EDT. <3.0.5.32.19980706220705.009b8d90@jazz.viagenie.qc.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3843.899830700.1@cloud.rain.com> Date: Tue, 07 Jul 1998 09:58:20 -0700 Message-ID: <3844.899830700@cloud.rain.com> From: Bill Trost Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Florent Parent writes: >Yes, the bus is properly terminated, with the last device in >the chain providing termination power. Windows has no trouble >accessing the attached SCSI devices, so I believe that the hardware >is not the problem.... I observe the same symptoms with a Compaq Armada 1598 and a 1460A (not 1460B) SlimSCSI. I'm using 2.2.6-release without the PAO. The devices are recognized by the scsi card (although after a ~30 sec delay during which my laptop is completly frozen). After that, no response (mount, disklabel...) from the device (tried Zip drive and then a CDROM). I have a half-baked idea here. I have vague recollection of experiencing similar problems with my aic0 *ISA* card when I first installed it, and it seems like the solution at the time was to fiddle with jumpers to remap interrupts or something equally simple (and seemingly unrelated to SlimSCSIs). You might try looking at what IRQ Windows uses and make pccardd use the same one. By the way, what's a "good" price for a SlimSCSI these days? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Jul 8 02:40:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13195 for freebsd-mobile-outgoing; Wed, 8 Jul 1998 02:40:41 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from mail.lbfe.org.tw (h253.n26.lbfe.org.tw [210.63.26.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13147 for ; Wed, 8 Jul 1998 02:40:33 -0700 (PDT) (envelope-from jonahk@mail.lbfe.org.tw) Received: from mail.lbfe.org.tw ([210.63.26.198]) by mail.lbfe.org.tw (Netscape Messaging Server 3.01) with ESMTP id AAA2CF1 for ; Wed, 8 Jul 1998 18:01:03 +0800 Message-ID: <35A34133.390F2F2C@mail.lbfe.org.tw> Date: Wed, 08 Jul 1998 17:51:48 +0800 From: Jonah Kuo X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: mobile@FreeBSD.ORG Subject: PD-6832 & DE-660 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I'm new to freebsd.moblie and having a little quesiton. I have installed FreeBSD 2.2.6 on (my boss's) laptop, I download PAO-980430 today for better support of Cirrus Logic PD6832. This chip is well identified in boot message: pcic0 rev 193 class 60700 int a irq 9 on pci0:23:0 pcic0 rev 193 class 60700 int b irq 9 on pci0:23:1 ...... PC-Card ctlr(0) Cirrus Logic PD-6832 [i82365 compatible mode] (5 mem & 2 I/O windows) pcic0: slot 0 controller I/O address 0x3e0 pcic0: slot 1 controller I/O address 0x3e0 pcic0 at 0x3e0-0x3e1 irq 9 on isa But there are still messages that I can't understand: pccardd[39]: Card "D-Link"("DE-660") [118b6603] [^?] matched "D-Link"("DE-660") [(null)] [(null)] --( repeat twice) pccardd[39]: driver allocation failed for D-Link (Device not configured) --(repeat twice) Could anybody guide me on these messages? thanks, Jonah To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Jul 8 07:31:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07032 for freebsd-mobile-outgoing; Wed, 8 Jul 1998 07:31:14 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from cray-ymp.acm.vt.edu (cray-ymp.acm.vt.edu [128.173.43.251]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07012 for ; Wed, 8 Jul 1998 07:31:05 -0700 (PDT) (envelope-from dlacroix@cray-ymp.acm.vt.edu) Received: (from dlacroix@localhost) by cray-ymp.acm.vt.edu (8.8.8/8.8.8) id KAA15284; Wed, 8 Jul 1998 10:35:00 -0400 (EDT) (envelope-from dlacroix) From: David La Croix Message-Id: <199807081435.KAA15284@cray-ymp.acm.vt.edu> Subject: Re: PD-6832 & DE-660 In-Reply-To: <35A34133.390F2F2C@mail.lbfe.org.tw> from Jonah Kuo at "Jul 8, 98 05:51:48 pm" To: jonahk@mail.lbfe.org.tw (Jonah Kuo) Date: Wed, 8 Jul 1998 09:35:00 -0500 (CDT=) Cc: freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jonah Kuo wrote: > Hello, > > I'm new to freebsd.moblie and having a little quesiton. > > I have installed FreeBSD 2.2.6 on (my boss's) laptop, I download > PAO-980430 today for better support of Cirrus Logic PD6832. > This chip is well identified in boot message: > > pcic0 rev 193 class 60700 > int a irq 9 on pci0:23:0 > > pcic0 rev 193 class 60700 > int b irq 9 on pci0:23:1 > > ...... > > PC-Card ctlr(0) Cirrus Logic PD-6832 [i82365 compatible mode] (5 mem & 2 > I/O windows) > pcic0: slot 0 controller I/O address 0x3e0 > pcic0: slot 1 controller I/O address 0x3e0 > pcic0 at 0x3e0-0x3e1 irq 9 on isa > > > But there are still messages that I can't understand: > > pccardd[39]: Card "D-Link"("DE-660") [118b6603] [^?] matched > "D-Link"("DE-660") [(null)] [(null)] > --( repeat twice) > pccardd[39]: driver allocation failed for D-Link (Device not configured) > > --(repeat twice) > > > Could anybody guide me on these messages? My experience has been (on a Gateway SOLO 9100) -- you have to turn the machine off after it's been in Windows 95 to reset the interface. On mine, FreeBSD wasn't able to collect the PCCARD info at all until I did a hard reset (turned machine off all the way before rebooting with FreeBSD). This may or may not have something to do with your problem. -- dlacroix@acm.vt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Jul 8 17:46:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24981 for freebsd-mobile-outgoing; Wed, 8 Jul 1998 17:46:53 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from acs.stritch.edu (acs.stritch.edu [140.189.33.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24974 for ; Wed, 8 Jul 1998 17:46:49 -0700 (PDT) (envelope-from stevet@acs.stritch.edu) Received: from localhost (stevet@localhost) by acs.stritch.edu (8.9.0/8.9.0) with SMTP id SAA19219 for ; Wed, 8 Jul 1998 18:47:21 -0500 (CDT) Date: Wed, 8 Jul 1998 18:47:20 -0500 (CDT) From: Steve Tracy To: freebsd-mobile@FreeBSD.ORG Subject: /kernel: ed0: device timeout Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have switched to a LinkSys Combo PCMCIA EthernetCard (EC2T) and am now getting the message /kernel: ed0: device timeout when I try to set the cards address with ifconfig. I've checked the mailing list archives, and although the question has been asked several times, the only answer that I have seen is that this is probably due to an incorrect IRQ setting. How can I check to make sure that the PCMCIA card is set at the IRQ that I have specified? or if I let the card try to find it's own IRQ, how can I check which one it has? I've disabled both COM ports and an internal sound card, freeing up IRQ's 3, 4, and 9 as well as 5 which was free to begin with. If anyone has any ideas I would greatly appreciate them. Thank you, Steve Tracy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Jul 8 22:37:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00532 for freebsd-mobile-outgoing; Wed, 8 Jul 1998 22:37:52 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from chipweb.ml.org (qmailr@c1003518-a.plstn1.sfba.home.com [24.1.82.47]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA00527 for ; Wed, 8 Jul 1998 22:37:49 -0700 (PDT) (envelope-from ludwigp@bigfoot.com) Received: (qmail 11012 invoked by uid 666); 9 Jul 1998 05:37:50 -0000 Received: from speedy.chipweb.ml.org (172.16.1.1) by inet.chipweb.ml.org with SMTP; 9 Jul 1998 05:37:50 -0000 Message-Id: <3.0.3.32.19980708222236.03349448@mail.plstn1.sfba.home.com> X-Sender: ludwigp@mail.plstn1.sfba.home.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 08 Jul 1998 22:22:36 -0700 To: Steve Tracy , freebsd-mobile@FreeBSD.ORG From: Ludwig Pummer Subject: Re: /kernel: ed0: device timeout In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 06:47 PM 7/8/98 -0500, Steve Tracy wrote: >I have switched to a LinkSys Combo PCMCIA EthernetCard (EC2T) and am now >getting the message /kernel: ed0: device timeout when I try to set the >cards address with ifconfig. I've checked the mailing list archives, and >although the question has been asked several times, the only answer that I >have seen is that this is probably due to an incorrect IRQ setting. How >can I check to make sure that the PCMCIA card is set at the IRQ that I >have specified? or if I let the card try to find it's own IRQ, how can I >check which one it has? I've disabled both COM ports and an internal >sound card, freeing up IRQ's 3, 4, and 9 as well as 5 which was free to >begin with. If anyone has any ideas I would greatly appreciate them. > >Thank you, >Steve Tracy timeouts can also be caused by bad cabling/bad cable detection/bad termination on coax cabling. as far as i know, if you specify an IRQ, a PCMCIA card will take that IRQ or pccardd will give some error message. --Ludwig Pummer ludwigp@bigfoot.com ICQ UIN: 692441 http://chipweb.home.ml.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Jul 9 02:24:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20879 for freebsd-mobile-outgoing; Thu, 9 Jul 1998 02:24:47 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from mail.lbfe.org.tw (h253.n26.lbfe.org.tw [210.63.26.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20872 for ; Thu, 9 Jul 1998 02:24:44 -0700 (PDT) (envelope-from jonahk@mail.lbfe.org.tw) Received: from mail.lbfe.org.tw ([210.63.26.198]) by mail.lbfe.org.tw (Netscape Messaging Server 3.01) with ESMTP id AAA2E94 for ; Thu, 9 Jul 1998 17:45:31 +0800 Message-ID: <35A48F2D.F48746F0@mail.lbfe.org.tw> Date: Thu, 09 Jul 1998 17:36:46 +0800 From: Jonah Kuo X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: mobile@FreeBSD.ORG Subject: OK, I got it but...(Was PD-6832 & DE-660) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello everyone, My laptop has recognized the DE-660, but it hangs the laptop when this card is inserted, if I remove DE-660 manually, then things goes fine, any ideas? Jonah Kuo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Jul 9 07:55:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24161 for freebsd-mobile-outgoing; Thu, 9 Jul 1998 07:55:13 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from ns2.t3tech.com (ns2.t3tech.com [207.19.215.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24156 for ; Thu, 9 Jul 1998 07:55:11 -0700 (PDT) (envelope-from bikesh@tum.net) Received: from bikesh (helo=localhost) by ns2.t3tech.com with local-smtp (Exim 1.92 #1) for freebsd-mobile@freebsd.org id 0yuI6I-0005KO-00; Thu, 9 Jul 1998 10:55:10 -0400 Date: Thu, 9 Jul 1998 10:55:10 -0400 (EDT) From: The UNIX Mighty! X-Sender: bikesh@ns2.t3tech.com To: freebsd-mobile@FreeBSD.ORG Subject: Etherexpress PRO/100 Mobile PCMCIA Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Howdy folks, does freebsd support Intel Etherexpress PRO/100 Mobile PCMCIA card this is a 32bit cardbus. If not does freebsd support any 10/100 pcmcia cards thanks bikesh@tum.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Jul 9 08:04:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25411 for freebsd-mobile-outgoing; Thu, 9 Jul 1998 08:04:38 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from amber.bios.unc.edu (amber.bios.unc.edu [152.2.94.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25404 for ; Thu, 9 Jul 1998 08:04:36 -0700 (PDT) (envelope-from jensen@bios.unc.edu) Received: from cthulhu.bios.unc.edu (cthulhu.bios.unc.edu [152.2.94.98]) by amber.bios.unc.edu (8.9.0/8.9.0) with SMTP id LAA00571 for ; Thu, 9 Jul 1998 11:04:34 -0400 (EDT) Message-Id: <199807091504.LAA00571@amber.bios.unc.edu> Date: Thu, 9 Jul 1998 11:09:02 -0400 (Eastern Daylight Time) From: jensen@bios.unc.edu ("Michael E. Jensen") To: freebsd-mobile@FreeBSD.ORG Subject: IBM TP 770ED and 2.2.6 X-Mailer: Siren Mail (Windows Version 4.0.2 (Windows 95/NT)) X-Sender: jensen@mail.bios.unc.edu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET="US-ASCII" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am trying to install the 2.2.6 release on a IBM Thinkpad 770ED Model with DVD, 128MB RAM, 8.0GB HDD, 3COM 3C589D-TP. The initial install was problem free, however, the initial reboot locked the machine. When I turn the machine on, the boot process gets as far as the probe for the hard drive and beeps 5 times and locks. Sometimes this occurs after probing the fd0 device. I have tried to do the following: At the boot prompt: wd(0,a)kernel.GENERIC -c Entered 'visual' The machine locks tight after 5 beeps. Sometimes the machine boots successfully. I have tried recompiling a 'bare bones' kernel, still locks up on reboot. Does FreeBSD 2.2.6 support the memory that the 770ED model utilizes? I have successfully install the 2.2.6 release on a plain IBM TP770, but not a 770ED. Any suggestions or comments? Thank you for your assistance, - Michael Jensen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Jul 9 09:01:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03890 for freebsd-mobile-outgoing; Thu, 9 Jul 1998 09:01:50 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA03885 for ; Thu, 9 Jul 1998 09:01:48 -0700 (PDT) (envelope-from dcmyers@concord.Corp.Sun.COM) From: dcmyers@concord.Corp.Sun.COM Received: from Corp.Sun.COM ([129.145.35.78]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id JAA10668; Thu, 9 Jul 1998 09:00:40 -0700 Received: from concord.Corp.Sun.COM by Corp.Sun.COM (SMI-8.6/SMI-5.3) id JAA01602; Thu, 9 Jul 1998 09:00:40 -0700 Received: from concord.corp by concord.Corp.Sun.COM (SMI-8.6/SMI-SVR4) id JAA02426; Thu, 9 Jul 1998 09:00:26 -0700 Date: Thu, 9 Jul 1998 09:00:26 -0700 Message-Id: <199807091600.JAA02426@concord.Corp.Sun.COM> To: "Steve Tracy" , freebsd-mobile@FreeBSD.ORG Reply-To: dcmyers@concord.Corp.Sun.COM X-Mailer: Sun NetMail 2.1.6 Subject: Re: /kernel: ed0: device timeout Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I have switched to a LinkSys Combo PCMCIA EthernetCard (EC2T) and am now >getting the message /kernel: ed0: device timeout when I try to set the >cards address with ifconfig. I've also got a LinkSys card (the 10/100), and I get intermittent ed0:timeout messages as well, but the card still works. I've come to the point where I just ignore them. On a possibly related note, I happened to trip on the Ethernet cable once, yanking the whole dongle assembly out from the card. When putting it back in, I got a stream of ed0:timeout messages, and the card *wouldn't* work. Checking the tiny little pins inside the dongle, I saw that I had managed to bend the rightmost two. Using a safety pin, I bent them back, and the card came up again. What the heck, take a look... (Considering the very real possibility of future clumsiness on my part, let me ask this: can one buy replacement dongles from LinkSys?) -David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Jul 9 10:12:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14141 for freebsd-mobile-outgoing; Thu, 9 Jul 1998 10:12:19 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from enterprise.dfacades.com (aria.dfacades.com [207.155.93.3] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14104; Thu, 9 Jul 1998 10:12:09 -0700 (PDT) (envelope-from dleeds@dfacades.com) Received: from bukowski.hepcat.org (cosmos@bukowski.hepcat.org [207.155.93.198]) by enterprise.dfacades.com (8.8.7/8.8.7) with ESMTP id KAA04819; Thu, 9 Jul 1998 10:05:31 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on Solaris X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 09 Jul 1998 10:13:44 -0700 (PDT) Reply-To: dleeds@dfacades.com Organization: DigitalFacades From: Daniel Leeds To: questions@FreeBSD.ORG, mobile@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: us robotics pcmcia modem, CC1336 supported? Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a megahertz/usrobotics pcmcia 33.6 modem, model CC1336 and cannot get it to work :( i looked around for a HCL, but couldnt find it. it has an entry in /etc/pccard.conf on 3.0-SNAP which i am running. but i cannot get it to work. i can connect to it via cu, and get it to dial, but i get no output. i can connect to /dev/cuaa0 and get output, but no dialtone, etc. i can connect to /dev/cuaa1 and get no output, but dial numbers and connect. i can connect to /dev/cuaa2 and get no output, but dial numbers and connect. can anyone help me? anyone running freebsd on a laptop with this modem? id appreciate ALL pointers/help/suggestions. i need to get this running ppp eventually... thanks ---------------------------------- E-Mail: Daniel Leeds Date: 09-Jul-98 Time: 10:09:45 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Jul 9 11:41:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01091 for freebsd-mobile-outgoing; Thu, 9 Jul 1998 11:41:25 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from dns.webwizard.net.mx (mexcom.net.mx [207.249.162.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01043; Thu, 9 Jul 1998 11:41:17 -0700 (PDT) (envelope-from rafareta@mexcom.net.mx) Received: from mexcom.net.mx (rafa.nix.mexcom.net [206.103.64.101]) by dns.webwizard.net.mx (8.8.8/8.8.7) with ESMTP id NAA13088; Thu, 9 Jul 1998 13:39:57 -0500 (CDT) Message-ID: <35A50E84.FF61A50F@mexcom.net.mx> Date: Thu, 09 Jul 1998 13:40:04 -0500 From: "Rafael A. Reta Rodriguez" Organization: MexCom.Net X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD sunix3.0.1 i386) MIME-Version: 1.0 To: dleeds@dfacades.com CC: questions@FreeBSD.ORG, mobile@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: us robotics pcmcia modem, CC1336 supported? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Daniel Leeds wrote: > > Hi, > > I have a megahertz/usrobotics pcmcia 33.6 modem, model CC1336 and cannot get it > to work :( i looked around for a HCL, but couldnt find it. > > it has an entry in /etc/pccard.conf on 3.0-SNAP which i am running. but i > cannot get it to work. i can connect to it via cu, and get it to dial, but i > get no output. > > i can connect to /dev/cuaa0 and get output, but no dialtone, etc. > i can connect to /dev/cuaa1 and get no output, but dial numbers and connect. > i can connect to /dev/cuaa2 and get no output, but dial numbers and connect. > > can anyone help me? anyone running freebsd on a laptop with this modem? > > id appreciate ALL pointers/help/suggestions. > > i need to get this running ppp eventually... > > thanks > Are you in a PBX? I've been having problems to dial with a PCMCI USR from a PBX extension. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Jul 9 11:45:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02018 for freebsd-mobile-outgoing; Thu, 9 Jul 1998 11:45:00 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from enterprise.dfacades.com (aria.dfacades.com [207.155.93.3] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01997; Thu, 9 Jul 1998 11:44:56 -0700 (PDT) (envelope-from dleeds@dfacades.com) Received: from bukowski.hepcat.org (cosmos@bukowski.hepcat.org [207.155.93.198]) by enterprise.dfacades.com (8.8.7/8.8.7) with ESMTP id LAA06012; Thu, 9 Jul 1998 11:38:02 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on Solaris X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <35A50E84.FF61A50F@mexcom.net.mx> Date: Thu, 09 Jul 1998 11:46:15 -0700 (PDT) Reply-To: dleeds@dfacades.com Organization: DigitalFacades From: Daniel Leeds To: "Rafael A. Reta Rodriguez" Subject: Re: us robotics pcmcia modem, CC1336 supported? Cc: hackers@FreeBSD.ORG, mobile@FreeBSD.ORG, questions@FreeBSD.ORG Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> > Are you in a PBX? I've been having problems to dial with a PCMCI USR > from a PBX extension. no. just a standard analog phone line. it seems to work somewhat...im at a loss :( ---------------------------------- E-Mail: Daniel Leeds Date: 09-Jul-98 Time: 11:44:28 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Jul 9 13:37:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21104 for freebsd-mobile-outgoing; Thu, 9 Jul 1998 13:37:18 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21099 for ; Thu, 9 Jul 1998 13:37:17 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id NAA05901; Thu, 9 Jul 1998 13:37:13 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 9 Jul 1998 13:37:12 -0700 (PDT) From: Doug White To: The UNIX Mighty! cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Etherexpress PRO/100 Mobile PCMCIA In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 9 Jul 1998, The UNIX Mighty! wrote: > > > Howdy folks, > does freebsd support Intel Etherexpress PRO/100 Mobile PCMCIA card > this is a 32bit cardbus. No, CardBus is not supported yet. > If not does freebsd support any 10/100 pcmcia cards I think there is a 100mbit PCCARD one, I think 3com makes it, but I'm not sure if it works or not. Check the -mobile mail archives at www.freebsd.org; we've had a discussion on this fairly recently. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Jul 9 17:41:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25087 for freebsd-mobile-outgoing; Thu, 9 Jul 1998 17:41:29 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from lily.ezo.net (root@lily.ezo.net [206.102.130.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25080 for ; Thu, 9 Jul 1998 17:41:25 -0700 (PDT) (envelope-from jflowers@ezo.net) Received: from violet.eznets.canton.oh.us (violet.ezo.net [206.102.130.138]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id UAA28967; Thu, 9 Jul 1998 20:39:24 -0400 (EDT) From: "Jim Flowers" To: Cc: Subject: WaveLAN Driver for FreeBSD Date: Thu, 9 Jul 1998 20:41:45 -0400 Message-ID: <01bdab9b$84139b80$8a8266ce@violet.eznets.canton.oh.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike, I see you were one of the last to overhaul the wl driver in 1997. I just moved an old style (pre 802.11) wavelan isa card and the hard drive with FreeBSD 2.2.6 on it from a 486 machine to a Pentium 133 and it stopped initializing with the following log entries: wl0: bldcu() not ready after reset wl0: diag() failed; status=0,inw=0,outw=e0a0 scb_status 0 scb_command 100 scb_cbl adaa cu_cmd 8007 wl0: init(): trouble resetting board Pings to the ifconfigged address work; beyond that, no response. Not surprising as it's marked up but not running. Same problem on a Pentium 200MMX. Any suggestions on where to start looking? I know the driver is well documented so that's where I'll be but I'm hoping this is something obvious as I would like to use a lot of these boxes for a wireless network. Jim Flowers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Jul 9 21:39:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18589 for freebsd-mobile-outgoing; Thu, 9 Jul 1998 21:39:59 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles10.castles.com [208.214.165.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18584 for ; Thu, 9 Jul 1998 21:39:56 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id UAA05047; Thu, 9 Jul 1998 20:02:45 -0700 (PDT) Message-Id: <199807100302.UAA05047@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jim Flowers" cc: mobile@FreeBSD.ORG Subject: Re: WaveLAN Driver for FreeBSD In-reply-to: Your message of "Thu, 09 Jul 1998 20:41:45 EDT." <01bdab9b$84139b80$8a8266ce@violet.eznets.canton.oh.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Jul 1998 20:02:44 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I see you were one of the last to overhaul the wl driver in 1997. I just > moved an old style (pre 802.11) wavelan isa card and the hard drive with > FreeBSD 2.2.6 on it from a 486 machine to a Pentium 133 and it stopped > initializing with the following log entries: The ISA Wavelans are *extremely* touchy about timing. You might want to start by checking the ISA config on your new board, and perhaps crank out some of the I/O delays, etc. > wl0: bldcu() not ready after reset > wl0: diag() failed; status=0,inw=0,outw=e0a0 > scb_status 0 > scb_command 100 > scb_cbl adaa > cu_cmd 8007 > wl0: init(): trouble resetting board You could also try upping STATUS_TRIES in sys/i386/isa/if_wl.c. There are quite a few hardcoded spin loops in this driver; the diag() failure may be symptomatic of this too. What motherboard chipset(s) are you using? > Pings to the ifconfigged address work; beyond that, no response. Not > surprising as it's marked up but not running. Same problem on a Pentium > 200MMX. Um, actually if it's responding to pings, then it's more or less working. > Any suggestions on where to start looking? I know the driver is well > documented so that's where I'll be but I'm hoping this is something obvious > as I would like to use a lot of these boxes for a wireless network. Try increasing the STATUS_TRIES value to start with, and see if that makes the 'not ready after reset' message go away. If that works, then increase the value in the poll loop above the 'failed; status' message. It may be that when the first is fixed, the card will be happy enough that the rest work. Apart from that, it actually appears to be running well enough - the interrupt handler is being called, and it's sending stuff in response OK, it's just not passing the startup tests. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Jul 10 21:39:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24737 for freebsd-mobile-outgoing; Fri, 10 Jul 1998 21:39:24 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24728; Fri, 10 Jul 1998 21:39:22 -0700 (PDT) (envelope-from dcarmich@Mars.mcs.net) Received: from Mars.mcs.net (dcarmich@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id XAA19858; Fri, 10 Jul 1998 23:39:22 -0500 (CDT) Received: (from dcarmich@localhost) by Mars.mcs.net (8.8.7/8.8.2) id XAA29567; Fri, 10 Jul 1998 23:39:21 -0500 (CDT) From: Douglas Carmichael Message-Id: <199807110439.XAA29567@Mars.mcs.net> Subject: Region of horizontal lines on right region of screen (duplib err -d uplication of leftr region) To: freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Date: Fri, 10 Jul 1998 23:39:21 -0500 (CDT) Action: urgent Reply-To: dcarmich@mcs.com X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry for the subject. My backspace seems to be messed up. I have a problem with XFree86 3.3.2 on a NEC Versa LX with an ATI 3D RAGE PRO LT video chip. (I'm using FreeBSD 2.2.6 with the pcvt console driver). When I start X with startx -- -bpp 32, X starts up fine and I can see the screen but on the right of the screen, there are horizontal lines going down to the bottom of the screen (not on the whole screen, but on about 1/4th of it) and anything dragged in that area cannot be seen. (Also, when I have my X cursor near that region, I see a mirror immage of it with a little white box before it in that region). Here's my XF86Config: # File generated by xf86config. # # Copyright (c) 1995 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the "Software"), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # ********************************************************************** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ********************************************************************** # ********************************************************************** # Files section. This allows default font and rgb paths to be set # ********************************************************************** Section "Files" # The location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. RgbPath "/usr/X11R6/lib/X11/rgb" # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # If you don't have a floating point coprocessor and emacs, Mosaic or other # programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out). # FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" # For OSs that support Dynamically loaded modules, ModulePath can be # used to set a search path for the modules. This is currently supported # for Linux ELF, FreeBSD 2.x and NetBSD 1.x. The default path is shown # here. # ModulePath "/usr/X11R6/lib/modules" EndSection # ********************************************************************** # Module section -- this is an optional section which is used to specify # which dynamically loadable modules to load. Dynamically loadable # modules are currently supported only for Linux ELF, FreeBSD 2.x # and NetBSD 1.x. Currently, dynamically loadable modules are used # only for some extended input (XInput) device drivers. # ********************************************************************** # # Section "Module" # # This loads the module for the Joystick driver # # Load "xf86Jstk.so" # # EndSection # ********************************************************************** # Server flags section. # ********************************************************************** Section "ServerFlags" # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging # NoTrapSignals # Uncomment this to disable the server abort sequence # This allows clients to receive this key event. # DontZap # Uncomment this to disable the / mode switching # sequences. This allows clients to receive these key events. # DontZoom # Uncomment this to disable tuning with the xvidtune client. With # it the client can still run and fetch card and monitor attributes, # but it will not be allowed to change them. If it tries it will # receive a protocol error. # DisableVidModeExtension # Uncomment this to enable the use of a non-local xvidtune client. # AllowNonLocalXvidtune # Uncomment this to disable dynamically modifying the input device # (mouse and keyboard) settings. # DisableModInDev # Uncomment this to enable the use of a non-local client to # change the keyboard or mouse settings (currently only xset). # AllowNonLocalModInDev EndSection # ********************************************************************** # Input devices # ********************************************************************** # ********************************************************************** # Keyboard section # ********************************************************************** Section "Keyboard" Protocol "Standard" # when using XQUEUE, comment out the above line, and uncomment the # following line # Protocol "Xqueue" AutoRepeat 500 5 # Let the server do the NumLock processing. This should only be required # when using pre-R6 clients # ServerNumLock # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Xleds 1 2 3 # To set the LeftAlt to Meta, RightAlt key to ModeShift, # RightCtl key to Compose, and ScrollLock key to ModeLock: # LeftAlt Meta # RightAlt ModeShift # RightCtl Compose # ScrollLock ModeLock # To disable the XKEYBOARD extension, uncomment XkbDisable. # XkbDisable # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # XkbModel "pc102" # If you have a US Microsoft Natural keyboard, you can use: # XkbModel "microsoft" # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # XkbLayout "de" # or: # XkbLayout "de" # XkbVariant "nodeadkeys" # # If you'd like to switch the positions of your capslock and # control keys, use: # XkbOptions "ctrl:swapcaps" # These are the default XKB settings for XFree86 # XkbRules "xfree86" # XkbModel "pc101" # XkbLayout "us" # XkbVariant "" # XkbOptions "" XkbKeymap "xfree86(us)" EndSection # ********************************************************************** # Pointer section # ********************************************************************** Section "Pointer" Protocol "PS/2" Device "/dev/mouse" # When using XQUEUE, comment out the above two lines, and uncomment # the following line. # Protocol "Xqueue" # Baudrate and SampleRate are only for some Logitech mice # BaudRate 9600 # SampleRate 150 # Emulate3Buttons is an option for 2-button Microsoft mice # Emulate3Timeout is the timeout in milliseconds (default is 50ms) Emulate3Buttons Emulate3Timeout 50 # ChordMiddle is an option for some 3-button Logitech mice # ChordMiddle EndSection # ********************************************************************** # Xinput section -- this is optional and is required only if you # are using extended input devices. This is for example only. Refer # to the XF86Config man page for a description of the options. # ********************************************************************** # # Section "Xinput" # SubSection "WacomStylus" # Port "/dev/ttyS1" # DeviceName "Wacom" # EndSubSection # SubSection "WacomCursor" # Port "/dev/ttyS1" # EndSubSection # SubSection "WacomEraser" # Port "/dev/ttyS1" # EndSubSection # # SubSection "Elographics" # Port "/dev/ttyS1" # DeviceName "Elo" # MinimumXPosition 300 # MaximumXPosition 3500 # MinimumYPosition 300 # MaximumYPosition 3500 # Screen 0 # UntouchDelay 10 # ReportDelay 10 # EndSubSection # # SubSection "Joystick" # Port "/dev/joy0" # DeviceName "Joystick" # TimeOut 10 # MinimumXPosition 100 # MaximumXPosition 1300 # MinimumYPosition 100 # MaximumYPosition 1100 # # CenterX 700 # # CenterY 600 # Delta 20 # EndSubSection # # The Mouse Subsection contains the same type of entries as the # standard Pointer Section (see above), with the addition of the # DeviceName entry. # # SubSection "Mouse" # Port "/dev/mouse2" # DeviceName "Second Mouse" # Protocol "Logitech" # EndSubSection # EndSection # ********************************************************************** # Monitor section # ********************************************************************** # Any number of monitor sections may be present Section "Monitor" Identifier "NEC Internal LCD" VendorName "NEC" ModelName "NEC" # HorizSync is in kHz unless units are specified. # HorizSync may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. HorizSync 24.18 - 56.48 # HorizSync 30-64 # multisync # HorizSync 31.5, 35.2 # multiple fixed sync frequencies # HorizSync 15-25, 30-50 # multiple ranges of sync frequencies # VertRefresh is in Hz unless units are specified. # VertRefresh may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. VertRefresh 30-120 # Modes can be specified in two formats. A compact one-line format, or # a multi-line format. # These two are equivalent # ModeLine "1024x768i" 45 1024 1048 1208 1264 768 776 784 817 Interlace # Mode "1024x768i" # DotClock 45 # HTimings 1024 1048 1208 1264 # VTimings 768 776 784 817 # Flags "Interlace" # EndMode # This is a set of standard mode timings. Modes that are out of monitor spec # are automatically deleted by the server (provided the HorizSync and # VertRefresh lines are correct), so there's no immediate need to # delete mode timings (unless particular mode timings don't work on your # monitor). With these modes, the best standard mode that your monitor # and video card can support for a given resolution is automatically # used. # 640x480 @ 60 Hz, 31.5 kHz hsync Modeline "640x480" 24 640 664 760 800 480 491 493 525 # 800x600 @ 56 Hz, 35.15 kHz hsync ModeLine "800x600" 36 800 824 896 1024 600 601 603 625 #ModeLine "1024x768" 62 1024 1064 1240 1280 768 774 776 808 ModeLine "1024x768" 75 1024 1048 1184 1328 768 771 777 806 -hsync -vsync EndSection # ********************************************************************** # Graphics device section # ********************************************************************** # Any number of graphics device sections may be present # Standard VGA Device: Section "Device" Identifier "Generic VGA" VendorName "Unknown" BoardName "Unknown" Chipset "generic" # VideoRam 256 # Clocks 25.2 28.3 EndSection # Sample Device for accelerated server: # Section "Device" # Identifier "Actix GE32+ 2MB" # VendorName "Actix" # BoardName "GE32+" # Ramdac "ATT20C490" # Dacspeed 110 # Option "dac_8_bit" # Clocks 25.0 28.0 40.0 0.0 50.0 77.0 36.0 45.0 # Clocks 130.0 120.0 80.0 31.0 110.0 65.0 75.0 94.0 # EndSection # Sample Device for Hercules mono card: # Section "Device" # Identifier "Hercules mono" # EndSection # Device configured by xf86config: Section "Device" Identifier "NEC Internal" VendorName "NEC Internal" BoardName "NEC" #MemBase 0xfd000000 #IOBase 0xec00 #VideoRam 4096 #DacSpeed 135 ChipID 0x4754 ChipRev 0x7 EndSection # ********************************************************************** # Screen sections # ********************************************************************** # The Colour SVGA server Section "Screen" Driver "svga" Device "Generic VGA" #Device "NEC Internal" Monitor "NEC Internal LCD" Subsection "Display" Depth 8 Modes "1024x768" "800x600" "640x480" EndSubsection EndSection # The 16-color VGA server Section "Screen" Driver "vga16" Device "Generic VGA" Monitor "NEC Internal LCD" Subsection "Display" Modes "640x480" "800x600" ViewPort 0 0 Virtual 800 600 EndSubsection EndSection # The Mono server Section "Screen" Driver "vga2" Device "Generic VGA" Monitor "NEC Internal LCD" Subsection "Display" Modes "640x480" "800x600" ViewPort 0 0 Virtual 800 600 EndSubsection EndSection # The accelerated servers (S3, Mach32, Mach8, 8514, P9000, AGX, W32, Mach64) Section "Screen" Driver "accel" Device "NEC Internal" Monitor "NEC Internal LCD" Subsection "Display" Depth 8 Modes "800x600" "640x480" ViewPort 0 0 EndSubsection Subsection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" ViewPort 0 0 EndSubsection Subsection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" ViewPort 0 0 EndSubsection Subsection "Display" Depth 32 Modes "1024x768" "800x600" "640x480" ViewPort 0 0 EndSubsection EndSection And the output from startx -- -bpp 32: XFree86 Version 3.3.2 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: February 28 1998 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: FreeBSD 2.2.5-STABLE i386 Configured drivers: Mach64: accelerated server for ATI Mach64 graphics adaptors (Patchlevel 0) Using pcvt driver (version 3.20) XF86Config: /etc/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: keymap: "xfree86(us)" (overrides other XKB settings) (**) Mouse: type: PS/2, device: /dev/mouse, buttons: 3 (**) Mouse: 3 button emulation (timeout: 50ms) (**) Mach64: Graphics device ID: "NEC Internal" (**) Mach64: Monitor ID: "NEC Internal LCD" (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fon ts/100dpi/" (--) Mach64: PCI: unknown ATI (0x4c50) rev 220, Aperture @ 0xfd000000, Block I/O @ 0xec00 (**) Mach64: Mach64 chipset override, using ChipID 0x4754 instead of 0x4c50 (**) Mach64: Mach64 chipset override, using ChipRev 0x07 instead of 0xdc (--) Mach64: Card type: PCI (--) Mach64: Memory type: 5 (--) Mach64: Clock type: Internal (--) Mach64: Maximum allowed dot-clock: 170.000 MHz (**) Mach64: Mode "1024x768": mode clock = 75.000 (**) Mach64: Mode "800x600": mode clock = 36.000 (**) Mach64: Mode "640x480": mode clock = 24.000 (--) Mach64: Virtual resolution: 1024x768 (--) Mach64: Video RAM: 4096k (--) Mach64: Using hardware cursor (--) Mach64: Using 16 MB aperture @ 0xfd000000 (--) Mach64: Ramdac is Internal (--) Mach64: Ramdac speed: 170 MHz (--) Mach64: Pixmap cache: 0 256x256 slots, 0 128x128 slots, 0 64x64 slots (--) Mach64: Font cache: 0 fonts System: `/usr/X11R6/lib/X11/xkb/xkbcomp -w 1 -R/usr/X11R6/lib/X11/xkb -xkm -m us -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" keymap/xfree86 /var/tmp/xfree86.xkm' waiting for X server to shut down X connection to :0.0 broken (explicit kill or server shutdown). xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0" xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0" And the output from FreeBSD's dmesg: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.6-RELEASE #0: Sat Jul 11 02:00:02 CDT 1998 dcarmich@dcarmich.pr.mcs.net:/usr/src/sys/compile/VERSALX CPU: Pentium Pro (233.29-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping=0 Features=0x183f9ff,,MMX,> real memory = 33554432 (32768K bytes) avail memory = 31055872 (30328K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0:0 vga0 rev 220 int a irq 10 on pci0:2:0 chip1 rev 2 int a irq ?? on pci0:3:0 chip2 rev 2 int b irq ?? on pci0:3:1 pci0:4: vendor=0x125d, device=0x1978, class=multimedia (audio) int a irq 5 [no driver assigned] chip3 rev 2 on pci0:7:0 chip4 rev 1 on pci0:7:1 chip5 rev 1 int d irq ?? on pci0:7:2 chip6 rev 2 on pci0:7:3 Probing for devices on the ISA bus: vt0 at 0x60-0x6f irq 1 on motherboard vt0: generic, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24] sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 2067MB (4233600 sectors), 4200 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordis wcd0: 4134Kb/sec, 128Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked npx0 flags 0x1 on motherboard npx0: INT 16 interface What could be the problem? (I've tried fussing with xvidtune, but no change.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Jul 10 22:35:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28542 for freebsd-mobile-outgoing; Fri, 10 Jul 1998 22:35:51 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28523; Fri, 10 Jul 1998 22:35:43 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.0/8.9.0) id PAA24585; Sat, 11 Jul 1998 15:05:11 +0930 (CST) Message-ID: <19980711150510.D23241@freebie.lemis.com> Date: Sat, 11 Jul 1998 15:05:10 +0930 From: Greg Lehey To: dcarmich@mcs.com Cc: FreeBSD Questions Subject: Re: Region of horizontal lines on right region of screen (duplib err -d uplication of leftr region) References: <199807110439.XAA29567@Mars.mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807110439.XAA29567@Mars.mcs.net>; from Douglas Carmichael on Fri, Jul 10, 1998 at 11:39:21PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Friday, 10 July 1998 at 23:39:21 -0500, Douglas Carmichael wrote (to -mobile and -hackers) This isn't a -hackers topic, and I suspect it's not really a -mobile topic either: it's a question, so I'm following up there. > Sorry for the subject. My backspace seems to be messed up. Try stty erase ^H > I have a problem with XFree86 3.3.2 on a NEC Versa LX with an ATI 3D RAGE > PRO LT video chip. (I'm using FreeBSD 2.2.6 with the pcvt console driver). > When I start X with startx -- -bpp 32, X starts up fine and I can see the > screen but on the right of the screen, there are horizontal lines going > down to the bottom of the screen (not on the whole screen, but on about > 1/4th of it) and anything dragged in that area cannot be seen. > (Also, when I have my X cursor near that region, I see a mirror immage of > it with a little white box before it in that region). This looks like a disagreement between the display and your XF86config as to the correct scan timing. There are a number of things you can do: 1. Check whether it happens in other resolutions. You don't say, but I suppose you were doing this at 1024x768. Does it still happen at 800x600 and 640x480? 2. Check whether it happens in other colour depths. If it doesn't, check the dot clocks. Your current ones are: > (**) Mach64: Mode "1024x768": mode clock = 75.000 > (**) Mach64: Mode "800x600": mode clock = 36.000 > (**) Mach64: Mode "640x480": mode clock = 24.000 3. I note that for 1024x768 you have the following mode line: ModeLine "1024x768" 75 1024 1048 1184 1328 768 771 777 806 -hsync -vsync I don't know if this is some decision by xf86setup that you need negative sync just for this speed, but I suspect it's bogus. You could try removing the -hsync -vsync and see if that improves things, though at the moment I can't see how. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Jul 11 10:58:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24586 for freebsd-mobile-outgoing; Sat, 11 Jul 1998 10:58:04 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from dcarmich.pr.mcs.net (dcarmich.pr.mcs.net [204.95.63.202]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24520 for ; Sat, 11 Jul 1998 10:57:58 -0700 (PDT) (envelope-from dcarmich@dcarmich.pr.mcs.net) Received: (from dcarmich@localhost) by dcarmich.pr.mcs.net (8.8.8/8.8.8) id TAA02765; Sat, 11 Jul 1998 19:59:16 -0500 (CDT) (envelope-from dcarmich) From: Douglas Carmichael Message-Id: <199807120059.TAA02765@dcarmich.pr.mcs.net> Subject: Followup on my display problems To: grog@lemis.com Date: Sat, 11 Jul 1998 19:59:16 -0500 (CDT) Cc: freebsd-mobile@FreeBSD.ORG Action: urgent Reply-To: dcarmich@mcs.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The reason why I wrote to freebsd-mobile because I have the 3D RAGE LT PRO chipset on my NEC Versa LX *laptop*. I get the same problem at 800x600 and 640x480. I tried removing -hsync -vsync, but it is still there. When I run fvwm, I see sort of an expansion of whatever's on the left region (i.e. the little GoodStuff window seems to be made into horizontal lines). And things displayed in that region (i.e. the xclock from the system xinitrc), are not seen. What could be the problem? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Jul 11 12:15:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04576 for freebsd-mobile-outgoing; Sat, 11 Jul 1998 12:15:19 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA04571 for ; Sat, 11 Jul 1998 12:15:14 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 24210 invoked by uid 1001); 11 Jul 1998 19:15:11 +0000 (GMT) To: dcarmich@mcs.com Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Followup on my display problems In-Reply-To: Your message of "Sat, 11 Jul 1998 19:59:16 -0500 (CDT)" References: <199807120059.TAA02765@dcarmich.pr.mcs.net> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 11 Jul 1998 21:15:11 +0200 Message-ID: <24208.900184511@verdi.nethelp.no> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The reason why I wrote to freebsd-mobile because I have the 3D RAGE LT PRO > chipset on my NEC Versa LX *laptop*. > I get the same problem at 800x600 and 640x480. I tried removing -hsync > -vsync, but it is still there. > When I run fvwm, I see sort of an expansion of whatever's on the left > region (i.e. the little GoodStuff window seems to be made into horizontal > lines). > And things displayed in that region (i.e. the xclock from the system > xinitrc), are not seen. > What could be the problem? Some info which may be relevant: The LT chipset is *not* directly supported in XFree86 3.3.2. I don't know how similar the LT PRO is. Below is a message I sent to comp.windows.x.i386unix after the problem I had with a board with the LT chipset was resolved. Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- From: sthaug@nethelp.no (Steinar Haug) Subject: Re: ASUS TX97-N card with built in ATI 3D RAGE LT - no luck with XFree86 Date: 30 May 1998 10:04:52 GMT Message-ID: <6kolk4$cjs$1@verdi.nethelp.no> I wrote: | Hi, I'm trying to get XFree86 3.3.2 running on a FreeBSD 2.2.6 system | with the graphics being ATI 3D RAGE LT (according to the ASUS Web Site), | with 2 MB VRAM. | | I've had no luck at all so far - only a black screen. Thanks to the help of Marc Aurele La France, I now have the 3D RAGE LT running smoothly with XF86_Mach64. Points to note: - It runs "out of the box" with the XF86_SVGA driver. I never tried this until it was suggested by Marc Aurele La France, since I "knew" I had a Mach64 type card (and thus should use the XF86_Mach64 driver). - It runs with the XF86_Mach64 driver *if* you insert the following in the "Device" section of the XF86Config file: ChipID 0x4754 ChipRev 0x7 Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message