From owner-freebsd-mobile Sun May 21 11:59:39 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 8FBE237B574 for ; Sun, 21 May 2000 11:59:32 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn4.imasy.or.jp [202.227.24.196]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.04) with ESMTP id DAA43534; Mon, 22 May 2000 03:59:28 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: nate@yogotech.com Cc: iwasaki@jp.FreeBSD.org, wietse@porcupine.org, dwhite@resnet.uoregon.edu, freebsd-mobile@FreeBSD.ORG Subject: Re: Thanks! In-Reply-To: <200005200120.TAA05714@nomad.yogotech.com> References: <20000519201058.BB6914563D@spike.porcupine.org> <20000520054857B.iwasaki@jp.FreeBSD.org> <200005200120.TAA05714@nomad.yogotech.com> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000522035927K.iwasaki@jp.FreeBSD.org> Date: Mon, 22 May 2000 03:59:27 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 47 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > As I wrote in earlier email, the bug goes away when I remove the > > > modem and ethernet card. However, doing so was not necessary with > > > FreeBSD 2.2.8. > > > Can anyone explain why FreeBSD must wake up prematurely when cards > > > are present, even without cables attached? > > > > It seems the features of some ThinkPad machines. I've heard that NIC > > and Modem pccards cause problems on some TP. > > Nope. It's a FreeBSD bug in newer releases, since it works fine in > older releases (2.2.8), as Wietse already pointed out. Really? I don't have TP here, but I found this at http://home.jp.FreeBSD.ORG/cgi-bin/showmail/bsd-nomads/10522 but it's from TP manual in Japanese. I translate them in English for you. IBM support pages also say almost same thing such as http://www-1.ibm.com/servlet/support/manager?rt=0&rs=0&org=psg&doc=E2AB5DFBFCE082E685256512005C419B ---- Notes on power management features when PC cards are used Some of the PC cards might case problems on ThinkPad by combination of AC/DC and power management modes. PC card support software prevent this by doing special process when power state change. [snip] Type of PC card Suspend request(Fn+F4) Hibernation(Fn+F12) AC DC AC DC Modem, NIC OK (*) OK NG OK Others OK OK OK OK *: However the machine enters in standby, not suspend. ---- I wonder if older releases have a special hack for this... Do you remember it? > > We had cli asm (disable interrupts) before calling APM BIOS call in > > FreeBSD 2.2.8, but this also seems to cause other problems and cli was > > deleted. > > Actually, with the cli, it didn't work on my box (same hardware as > Weitse), so it was removed by me (and the call is probably gone on his > box as well I suspect, since it works fine. :) Yes, I know. This seems originally came from CONFIG_APM_ALLOW_INTS in linux. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun May 21 12:47: 9 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from spike.porcupine.org (umbilical.porcupine.org [168.100.189.1]) by hub.freebsd.org (Postfix) with ESMTP id 4200F37B5C9 for ; Sun, 21 May 2000 12:47:01 -0700 (PDT) (envelope-from wietse@porcupine.org) Received: by spike.porcupine.org (Postfix, from userid 100) id 1A1774565A; Sun, 21 May 2000 15:46:57 -0400 (EDT) Subject: Re: Thanks! In-Reply-To: <20000522035927K.iwasaki@jp.FreeBSD.org> from Mitsuru IWASAKI at "May 22, 0 03:59:27 am" To: iwasaki@jp.FreeBSD.org (Mitsuru IWASAKI) Cc: nate@yogotech.com, iwasaki@jp.FreeBSD.org, wietse@porcupine.org, dwhite@resnet.uoregon.edu, freebsd-mobile@FreeBSD.ORG X-Time-Zone: USA EST, 6 hours behind central European time MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1907 Message-Id: <20000521194657.1A1774565A@spike.porcupine.org> Date: Sun, 21 May 2000 15:46:57 -0400 (EDT) From: wietse@porcupine.org (Wietse Venema) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mitsuru IWASAKI: > > > > As I wrote in earlier email, the bug goes away when I remove the > > > > modem and ethernet card. However, doing so was not necessary with > > > > FreeBSD 2.2.8. > > > > Can anyone explain why FreeBSD must wake up prematurely when cards > > > > are present, even without cables attached? > > > > > > It seems the features of some ThinkPad machines. I've heard that NIC > > > and Modem pccards cause problems on some TP. > > > > Nope. It's a FreeBSD bug in newer releases, since it works fine in > > older releases (2.2.8), as Wietse already pointed out. > > Really? Two Thinkpad 600 FreeBSd 2.2.8 users have reported that suspend works wven when cards are present. FreeBSD 2.2.8 does not have apmd. > I don't have TP here, but I found this at > http://home.jp.FreeBSD.ORG/cgi-bin/showmail/bsd-nomads/10522 > but it's from TP manual in Japanese. I translate them in English for you. > IBM support pages also say almost same thing such as > http://www-1.ibm.com/servlet/support/manager?rt=0&rs=0&org=psg&doc=E2AB5DFBFCE082E685256512005C419B [omitted] > I wonder if older releases have a special hack for this... > Do you remember it? I am not qualified to make such a judment. Rather, I trust your judgment and will send FreeBSD 2.2.8 apm source code in private mail. That is the code with the change to turn off cli (which is #ifdef-ed out). > > > We had cli asm (disable interrupts) before calling APM BIOS call in > > > FreeBSD 2.2.8, but this also seems to cause other problems and cli was > > > deleted. > > > > Actually, with the cli, it didn't work on my box (same hardware as > > Weitse), so it was removed by me (and the call is probably gone on his > > box as well I suspect, since it works fine. :) > > Yes, I know. This seems originally came from CONFIG_APM_ALLOW_INTS in linux. I had to disable the cli, otherwise the machine would not wake up. Wietse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 1:28:24 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from gandalf.axion.bt.co.uk (gandalf.axion.bt.co.uk [132.146.17.29]) by hub.freebsd.org (Postfix) with ESMTP id 2ADBE37BBB5 for ; Mon, 22 May 2000 01:28:21 -0700 (PDT) (envelope-from arnaud.gibier@bt.com) Received: from cbtlipnt01.btlabs.bt.co.uk by gandalf (local) with ESMTP; Mon, 22 May 2000 09:27:51 +0100 Received: by cbtlipnt01.btlabs.bt.co.uk with Internet Mail Service (5.5.2651.88) id ; Mon, 22 May 2000 09:27:57 +0100 Message-ID: From: arnaud.gibier@bt.com To: freebsd-mobile@FreeBSD.ORG Subject: Date: Mon, 22 May 2000 09:27:37 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2651.88) Content-Type: text/plain Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org auth 4cd460b6 subscribe freebsd-mobile arnaud.gibier@bt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 2: 8:36 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from alpha.dante.org.uk (alpha.dante.org.uk [193.63.211.19]) by hub.freebsd.org (Postfix) with ESMTP id DA98137BBBF for ; Mon, 22 May 2000 02:08:31 -0700 (PDT) (envelope-from Konstantin.Chuguev@dante.org.uk) Received: from theta.dante.org.uk ([193.63.211.7] helo=dante.org.uk) by alpha.dante.org.uk with esmtp (Exim 3.12 #4) id 12to4d-0004gv-00; Mon, 22 May 2000 10:00:31 +0100 Message-ID: <3928F715.E7ABE0D@dante.org.uk> Date: Mon, 22 May 2000 10:00:05 +0100 From: Konstantin Chuguev Organization: Delivery of Advanced Network Technology to Europe Ltd. X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: ru, en MIME-Version: 1.0 To: Darryl Okahata Cc: Ted Faber , Lyndon Nerenberg , Tom Glover , freebsd-mobile@freebsd.org Subject: Re: Mach64 ATI Rage Mobility on Inspiron 5000-7000 [Re: apmd] References: <200005191827.LAA01670@mina.sr.hp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Darryl Okahata wrote: > Ted Faber wrote: > > > Konstantin Chuguev wrote: > > >Well, the message is both about accelerated X server and its APM behaviour. > > > > > >I don't remember the original location of the patch, but I have put it > > I wrote the above "patch", and can say the following about it: > Darryl, many thanks for this patch! > > That said, I can say that the XFree86 4.0 Mach64 server works fine > under FreeBSD 4.0-STABLE. You don't need any of my patches or > programs. The Mach64 server works with suspend/resume and closing/opening > the lid. I also haven't gotten any of the nasty graphics corruption > that I was getting with the patched server. You do, however, have to > write your own XF86Config file, as the "XFree86 -configure" command > doesn't work. > Sorry, I didn't understand this. According the documentation on XFree86 4.0 at their site, there is only one server, called XFree86, which has various drivers. There is a driver called ATI which supports Mach64 Rage Mobility, but without acceleration. XFree86 3.3.6 ATI driver for SVGA server does this as well. If you are talking about 3.3.6 Mach64 server, then yes, it recognizes this videochip/card, but it requires completely different X video mode settings (synchronisation). If I start it with a mode of the patched 3.3.5 server, I get either flashing screen or dualized picture. I don't want to experiment much with settings, because I haven't found any examples of 1400x1050 settings and I don't want to damage my display. So, is the documentation wrong or you are using another server? What video settings? Thanks, Konstantin. -- * * Konstantin Chuguev - Application Engineer * * Francis House, 112 Hills Road * Cambridge CB2 1PQ, United Kingdom D A N T E WWW: http://www.dante.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 6:19:44 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from p2.acadia.net (p2.acadia.net [205.217.210.2]) by hub.freebsd.org (Postfix) with ESMTP id D1FE037B565; Mon, 22 May 2000 06:19:29 -0700 (PDT) (envelope-from tbuswell@acadia.net) Received: from smpbox (ip142167012045.acadia.net [142.167.12.45]) by p2.acadia.net (8.9.3/8.9.3) with ESMTP id JAA15473; Mon, 22 May 2000 09:19:21 -0400 (EDT) Received: (from tbuswell@localhost) by smpbox (8.9.3/8.9.3) id JAA00699; Mon, 22 May 2000 09:24:23 -0400 (EDT) (envelope-from tbuswell) From: Ted Buswell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 22 May 2000 09:23:22 -0400 (EDT) To: wietse@porcupine.org (Wietse Venema) Cc: freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Data point: FreeBSD 4.0 + removable SCSI support In-Reply-To: <20000520143950.0D9664563D@spike.porcupine.org> References: <20000519154650.2816B4563D@spike.porcupine.org> <20000520143950.0D9664563D@spike.porcupine.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14633.12600.583933.997406@smpbox> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wietse Venema writes: > Without devices attached to the SlimSCSI 1460B, "camcontrol rescan 0" > reports success. > > With random hardware connected to the SlimSCSI 1460B, "camcontrol > rescan 0" reports success, and the kernel says: You didn't say it explicitly, I assume (from the message subject) that the limited success (with other targets or no targets attached) is with a 4.0 kernel? I did a quick check, and my understanding is that 3.4 is using the driver in /sys/i386/isa which is the same as the driver in 2.2, while 4.0 and on use the driver in /sys/dev/aic ("old" works vs. "new" doesn't). So your original complaint about the aic driver in 4.0 is probably well founded: it sounds to me like the aic driver is not handling garbage from the Jaz device gracefully. -Ted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 6:41:12 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from spike.porcupine.org (umbilical.porcupine.org [168.100.189.1]) by hub.freebsd.org (Postfix) with ESMTP id D4DE337BACA; Mon, 22 May 2000 06:40:58 -0700 (PDT) (envelope-from wietse@porcupine.org) Received: by spike.porcupine.org (Postfix, from userid 100) id 4419C4565A; Mon, 22 May 2000 09:40:53 -0400 (EDT) Subject: Re: Data point: FreeBSD 4.0 + removable SCSI support In-Reply-To: <14633.12600.583933.997406@smpbox> from Ted Buswell at "May 22, 0 09:23:22 am" To: tbuswell@acadia.net (Ted Buswell) Cc: wietse@porcupine.org, freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Time-Zone: USA EST, 6 hours behind central European time MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1430 Message-Id: <20000522134053.4419C4565A@spike.porcupine.org> Date: Mon, 22 May 2000 09:40:53 -0400 (EDT) From: wietse@porcupine.org (Wietse Venema) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ted Buswell: > > Wietse Venema writes: > > Without devices attached to the SlimSCSI 1460B, "camcontrol rescan 0" > > reports success. > > > > With random hardware connected to the SlimSCSI 1460B, "camcontrol > > rescan 0" reports success, and the kernel says: > > You didn't say it explicitly, I assume (from the message subject) that > the limited success (with other targets or no targets attached) is > with a 4.0 kernel? Indeed, this is the same 4.0-20000518-STABLE kernel that "hangs" with the Jaz 2GB drive plugged into the SlimSCSI 1460B controller. > I did a quick check, and my understanding is that 3.4 is using the > driver in /sys/i386/isa which is the same as the driver in 2.2, while > 4.0 and on use the driver in /sys/dev/aic ("old" works vs. "new" doesn't). Unfortunately, I am not qualified to debug the aic driver. This is better handled by someone who has studied that code before. > So your original complaint about the aic driver in 4.0 is probably well > founded: it sounds to me like the aic driver is not handling garbage > from the Jaz device gracefully. I expect the problem to show up with Jaz 2GB drives on other SCSI controllers, too, and expect that it will eventually be fixed. So there is hope that my primary enviroment will be supported again by mainstream FreeBSD code, which is my preferred solution. Meanwhile, I will migrate to 3.4+PAO so that I can do useful work. Wietse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 8:21:12 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id B835F37B9C4 for ; Mon, 22 May 2000 08:20:29 -0700 (PDT) (envelope-from mpenagar@we.lc.ehu.es) Received: from we.lc.ehu.es (saturno [158.227.6.120]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id RAA07901; Mon, 22 May 2000 17:18:36 +0200 (MET DST) Message-ID: <39294FC7.2A837A5F@we.lc.ehu.es> Date: Mon, 22 May 2000 17:18:31 +0200 From: Mikel Penagaricano X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: eu, es, en MIME-Version: 1.0 To: "Sean O'Connell" , freebsd-mobile@FreeBSD.ORG Subject: Re: Gateway Solo 2150 References: <392517A1.729641FC@we.lc.ehu.es> <20000519085643.C45347@stat.Duke.EDU> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sean O'Connell wrote: > > Mikel Penagaricano stated: > > Hi! > > > > I'm having some problems configuring FreeBSD4.0 on my Gateway Solo 2150: > > > > - Video: ATI Movility M AGPx2 (4MB) doesn't seem to work under Mach64 > > driver ( no problem under SVGA, but of course, quite slow) > > If you have money burning a hole in your pocket you could try the > accelerated X (www.xig.org ... you can also pick this up through > www.freebsdmall.com) or maybe Metro-X (www.metrolink.com), which is > cheaper (it lists support for generic mobility chipset). I do know > that xig has a downloadable demo display. > > > - Audio: Creative EV1938 is not recognized at boot (should be similar to > > SB 64PCI ???) > > Are you running -stable? I think that there were recent commits > for the SB Live card... you may need to hack in pci identifiers > (please don't ask me how :) > > Good Luck > S I did tried hacking in ES1371 pci identifiers, and got my EV1938 working!!! Anyway, sound volume is extremely low, which could mean mixer is not working correctly. I looked at ES1371 source an think it uses ac97 mixer. I will try to get more information around. Thanks, Mikel :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 11:16:49 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id 58D1D37BBBD for ; Mon, 22 May 2000 11:16:36 -0700 (PDT) (envelope-from karsten@rohrbach.de) Received: (qmail 7036 invoked by uid 1000); 22 May 2000 18:16:30 -0000 Date: Mon, 22 May 2000 20:16:30 +0200 From: "Karsten W. Rohrbach" To: Warner Losh Cc: Eric Brunner , freebsd-mobile@FreeBSD.ORG Subject: Re: Sony VAIO and CDROM Message-ID: <20000522201629.A6686@rohrbach.de> Reply-To: karsten@rohrbach.de References: <200005182158.RAA29816@world.std.com> <200005192257.QAA04126@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200005192257.QAA04126@harmony.village.org>; from imp@village.org on Fri, May 19, 2000 at 04:57:58PM -0600 X-Arbitrary-Number-Of-The-Day: 42 X-Sender: karsten@rohrbach.de Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hm basically this looks to me like the toshiba 40x cdrom withj sony 16bit atapi controller pcmcia card. as this is a stupid ata controller, you just have to recognize NinjaATA when you use 3.3pao. i do not know the status of attachment code of the ata device in -current, some while ago it would not dynamically attach an ata? to the controller wehn the pcmcia slot was going power high. what works with these cdrom is boot time recognotion (i did NOT try this with freebsd), when the card is plugged in during cold boot of the machine it gets attached by the bios at port 0x180/0x386 and some irq the driver code should probe when initialising /k Warner Losh(imp@village.org)@Fri, May 19, 2000 at 04:57:58PM -0600: > In message <200005182158.RAA29816@world.std.com> Eric Brunner writes: > : I know this has been asked and answered previously, but I can't find the > : cannonical how-to and I'd appreciate it if someone would help. > : > : h/w: PGC-505TX > : s/w: FreeBSD 3.3-RELEASE (GENERIC) > : c/d: PCGA-CD5 > : > : I've not enjoyed the use of the CDROM with 2.2.8, and 3.3, and my goal is > : to go -CURRENT on this laptop. > > -current supports the good cdrom. I don't know if this cdrom is the > good sony one, or the brain dead one. > > I use a microtech cdrom on my 505ts all the time. > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message -- > A Puritan is someone who is deathly afraid that someone, somewhere, is > having fun. http://www.webmonster.de http://www.apache.de http://www.splatterworld.de (NIC-HDL KR433/KR11-RIPE) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 11:19: 1 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id ECAF137BCF4 for ; Mon, 22 May 2000 11:18:53 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA07277; Mon, 22 May 2000 12:18:50 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA96739; Mon, 22 May 2000 12:17:50 -0600 (MDT) Message-Id: <200005221817.MAA96739@harmony.village.org> To: karsten@rohrbach.de Subject: Re: Sony VAIO and CDROM Cc: Eric Brunner , freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Mon, 22 May 2000 20:16:30 +0200." <20000522201629.A6686@rohrbach.de> References: <20000522201629.A6686@rohrbach.de> <200005182158.RAA29816@world.std.com> <200005192257.QAA04126@harmony.village.org> Date: Mon, 22 May 2000 12:17:49 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20000522201629.A6686@rohrbach.de> "Karsten W. Rohrbach" writes: : hm : basically this looks to me like the toshiba 40x cdrom withj sony 16bit : atapi controller pcmcia card. as this is a stupid ata controller, you : just have to recognize NinjaATA when you use 3.3pao. : i do not know the status of attachment code of the ata device in : -current, some while ago it would not dynamically attach an ata? to the : controller wehn the pcmcia slot was going power high. : what works with these cdrom is boot time recognotion (i did NOT try this : with freebsd), when the card is plugged in during cold boot of the : machine it gets attached by the bios at port 0x180/0x386 and some irq : the driver code should probe when initialising The ata stuff will dynamically attach after boot now. I think that as part of boot we specifically kill the power on all the pccard slots. I may be mistaken about this. One cannot boot off the cdrom for FreeBSD and then mount the root partition from the cdrom. We don't support that for pccard (or usb) at this time. Other than that, I think that these devices will work with -current and -stable. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 11:32:36 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id 330F137B9AD for ; Mon, 22 May 2000 11:32:27 -0700 (PDT) (envelope-from karsten@rohrbach.de) Received: (qmail 7226 invoked by uid 1000); 22 May 2000 18:32:25 -0000 Date: Mon, 22 May 2000 20:32:25 +0200 From: "Karsten W. Rohrbach" To: Warner Losh Cc: Eric Brunner , freebsd-mobile@FreeBSD.ORG Subject: Re: Sony VAIO and CDROM Message-ID: <20000522203225.B6686@rohrbach.de> Reply-To: karsten@rohrbach.de References: <20000522201629.A6686@rohrbach.de> <200005182158.RAA29816@world.std.com> <200005192257.QAA04126@harmony.village.org> <20000522201629.A6686@rohrbach.de> <200005221817.MAA96739@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200005221817.MAA96739@harmony.village.org>; from imp@village.org on Mon, May 22, 2000 at 12:17:49PM -0600 X-Arbitrary-Number-Of-The-Day: 42 X-Sender: karsten@rohrbach.de Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Warner Losh(imp@village.org)@Mon, May 22, 2000 at 12:17:49PM -0600: > The ata stuff will dynamically attach after boot now. I think that as > part of boot we specifically kill the power on all the pccard slots. > I may be mistaken about this. One cannot boot off the cdrom for > FreeBSD and then mount the root partition from the cdrom. We don't > support that for pccard (or usb) at this time. what the deal is actually about is that the vaio n505x/se/* (celeron/pii boxes, not the pentiums) have atapi boot support for cdrom on a pc card. they probe the pcmcia socket at cold boot and attach the ata controller at ports 0x180 and 0x386 (some black magic, one just has to know). i have linux installed this way on my n505x by telling the kernel at boot time to hook up the pccard ide controller as ide2 appending "ide2=0x180,0x386" to the lilo command line and there you go ;-) the only time you would need that is for booting the install cd, since those boxes only got one pc card slot which basically means: cdrom OR network, there you go... while actually installing the dist from the cd (which implies booting from the cdrom through the bios floppy emulation code and loading the ramdisk image from the eltorito image which gets booted) this just means that the kernel once in his lifetime gets the address of the controller hardwired one time. after install is done and you boot you got pccardd which handles the device attachment. > > Other than that, I think that these devices will work with -current > and -stable. if it dynamically attaches ata this should not be much of an issue, but as i mentioned before, installing is ;-) the problem with the little vaios is, that if you boot it from floppy, everything will be fine until you swap the disks since bios boot support for the floppy drive is just for booting. when the kernel wants to read the ramdisk image it gets confronted with a rather unlikely-to-be-supported-natively usb floppy (y-e data flashbuster 3.5"). if the kernel would use the realmode bios irq interface to the floppy to load the ramdisk image it might work to get all that stuff into the mfs and fetch the dist over the network card using a standard ftp install. /k -- > "Dope will get you through times of no money better that money will get > you through times of no dope." -- Gilbert Shelton http://www.webmonster.de http://www.apache.de http://www.splatterworld.de (NIC-HDL KR433/KR11-RIPE) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 12:37:15 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from jasper.southwind.net (jasper.southwind.net [206.53.103.7]) by hub.freebsd.org (Postfix) with ESMTP id 4ECA137BADE for ; Mon, 22 May 2000 12:37:10 -0700 (PDT) (envelope-from gmains@southwind.net) Received: from localhost (gmains@localhost) by jasper.southwind.net (8.10.1/8.10.1) with ESMTP id e4MJb8I05516 for ; Mon, 22 May 2000 14:37:08 -0500 (CDT) X-Authentication-Warning: jasper.southwind.net: gmains owned process doing -bs Date: Mon, 22 May 2000 14:37:08 -0500 (CDT) From: Gabriel To: freebsd-mobile@freebsd.org Subject: Xircom 10/100 Ethernet +56k modem in 4.0-RELEASE? 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 [THIS IS THE NON-CARDBUS VERSION, BTW] Has anyone gotten this PCMCIA card to work? It recognizes that there is a card in slot 0 but it gives me one of the following error messages every time: May 22 13:19:36 meteor /kernel: pccard: card inserted, slot 0 May 22 13:19:36 meteor pccardd[46]: Config id 1 not present in this card May 22 13:19:36 meteor pccardd[46]: Resource allocation failure for Xircom or May 22 14:14:01 meteor /kernel: pccard: card inserted, slot 0 May 22 14:14:01 meteor pccardd[46]: No card database for ""("") My /etc/pccard.conf file is as follows: # Generally available IO ports io 0x240-0x360 # Generally available IRQs (Built-in sound-card owners remove 5) irq 9 10 # Available memory slots memory 0xd4000 96k # Xircom Realport card + modem card "Xircom" "16-bit Ethernet + Modem 56" config 0x27 "xe0" 10 insert logger -t pccard:$device -s Xircom Realport Ethernet inserted insert /etc/pccard_ether $device remove logger -t pccard:$device -s Xircom Realport Ethernet removed remove /etc/pccard_ether $device delete and I have xe enabled in the kernel, although it doesn't seem to load on boot up. (don't see it in /var/log/messages). I have read that this may be broken in 4.0 but working in 3.4 and 5.0-current. Is this true? =============================================================================== ------------------------------------------------------------------------------- Gabriel SouthWind Internet Access, Inc. Department Manager 120 S. Market SouthWind Technical Support 800-525-7963 ------------------------------------------------------------------------------- =============================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 13: 8:13 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id D61FC37BC0C for ; Mon, 22 May 2000 13:08:11 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from mina.sr.hp.com (mina.sr.hp.com [15.4.42.247]) by palrel3.hp.com (Postfix) with ESMTP id B16AA24B; Mon, 22 May 2000 13:08:11 -0700 (PDT) Received: from localhost (darrylo@localhost [127.0.0.1]) by mina.sr.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id NAA21237; Mon, 22 May 2000 13:08:11 -0700 (PDT) Message-Id: <200005222008.NAA21237@mina.sr.hp.com> To: Konstantin Chuguev Cc: freebsd-mobile@freebsd.org Subject: Re: Mach64 ATI Rage Mobility on Inspiron 5000-7000 [Re: apmd] Reply-To: Darryl Okahata In-reply-to: Your message of "Mon, 22 May 2000 10:00:05 PDT." <3928F715.E7ABE0D@dante.org.uk> Mime-Version: 1.0 (generated by tm-edit 1.5) Content-Type: text/plain; charset=US-ASCII Date: Mon, 22 May 2000 13:08:10 PDT From: Darryl Okahata Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Konstantin Chuguev wrote: > > That said, I can say that the XFree86 4.0 Mach64 server works fine > > under FreeBSD 4.0-STABLE. You don't need any of my patches or [ ... ] > > Sorry, I didn't understand this. According the documentation on XFree86 4.0 a > t their > site, there is only one server, called XFree86, which has various drivers. > There is a driver called ATI which supports Mach64 Rage Mobility, but without > acceleration. XFree86 3.3.6 ATI driver for SVGA server does this as well. If you want to get technical, I'm using the XFree86 4.0 server, using the ATI drivers that support the ATI Rage Mobility-P chipset in my Dell Inspiron 7500 laptop. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 13:16:22 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 0552737BC1C for ; Mon, 22 May 2000 13:14:05 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: from ragnet.demon.co.uk ([158.152.46.40]) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 12tyYw-000GIC-0A; Mon, 22 May 2000 20:12:31 +0000 Received: from dmlb by ragnet.demon.co.uk with local (Exim 3.03 #1) id 12tyTQ-000B89-00; Mon, 22 May 2000 21:06:48 +0100 Content-Length: 476 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 22 May 2000 21:06:47 +0100 (BST) From: Duncan Barclay To: Gabriel Subject: RE: Xircom 10/100 Ethernet +56k modem in 4.0-RELEASE? Cc: freebsd-mobile@freebsd.org Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 22-May-00 Gabriel wrote: > I have read that this may be broken in 4.0 but working in 3.4 and > 5.0-current. Is this true? Yes, check the archives of this list to understand why. Duncan --- ________________________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@ragnet.demon.co.uk | the alcoholics, and the permanently stoned. ________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 14: 6:58 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from smtp1.medianstrip.net (medianstrip.net [206.113.38.30]) by hub.freebsd.org (Postfix) with ESMTP id 02FAE37BB8B for ; Mon, 22 May 2000 14:06:56 -0700 (PDT) (envelope-from mike@medianstrip.net) Received: by smtp1.medianstrip.net (Postfix, from userid 1000) id F3EC959B0; Mon, 22 May 2000 16:44:10 -0400 (EDT) Date: Mon, 22 May 2000 16:44:10 -0400 From: mike ryan To: freebsd-mobile@freebsd.org Subject: Re: suspend/resume on z505hs Message-ID: <20000522164410.A18562@medianstrip.net> Mail-Followup-To: mike ryan , freebsd-mobile@freebsd.org References: <20000428141659.A74587@medianstrip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000428141659.A74587@medianstrip.net>; from mike+fbsd@medianstrip.net on Fri, Apr 28, 2000 at 02:16:59PM -0400 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org on Apr 28, mike wrote: > i've got a couple suspend/resume problems on a sony vaio z505hs. > > the first is that after a resume usb devices no longer work. > kern/18261 contains a patch for this, translated from netbsd. > > the second is far more problematic: if i boot a kernel with fxp > support then suspend and resume, the machine wedges in fxp_init > while waiting for the "config command/DMA" to complete (if_fxp.c > revision 1.77.2.1 line 1518). > > anybody got any ideas on this one? kern/18756 contains a patch. with these two patches, suspend/resume finally works for me, both via "apm -z" and Fn-Esc. suspend-to-disk also works, but only via Fn-F12. "apm -Z" just results in this syslog message: "Entire system suspend failure: errcode = 96". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 14:14: 7 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from tethys.cep.unc.edu (tethys.cep.unc.edu [152.2.72.107]) by hub.freebsd.org (Postfix) with ESMTP id 81DD437B727 for ; Mon, 22 May 2000 14:14:03 -0700 (PDT) (envelope-from tshay@tethys.cep.unc.edu) Received: (from tshay@localhost) by tethys.cep.unc.edu (8.9.3/8.9.3) id RAA32387; Mon, 22 May 2000 17:14:00 -0400 Date: Mon, 22 May 2000 17:14:00 -0400 (EDT) From: Thomas Shay X-Sender: tshay@tethys.cep.unc.edu To: freebsd-mobile@freebsd.org Subject: Should pcmcia card be recognized in install? 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'm messing around witj various pcmcia cards. I just installed 4.0-release on a Thinkpad 600e (2645-UN1). I have a Megahertz CC10BT/2 10MBps ethernet card installed and connected to the net during install. I go about installing the system, and then when it gets to networking, my only choices are slip and ppp. Does this indicate that the card is not being recognized at this point, or does networking with pcmcia ethernet cards always have to be configured after installation is complete? Thanks, tjs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 15:49:18 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 3286D37B5C7 for ; Mon, 22 May 2000 15:49:10 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (lxpxfr.lx.ehu.es [158.227.99.247]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id AAA09530; Tue, 23 May 2000 00:41:33 +0200 (MET DST) Message-ID: <3929B79C.AFC90693@we.lc.ehu.es> Date: Tue, 23 May 2000 00:41:32 +0200 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dpto. de Electricidad y Electronica X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Darryl Okahata Cc: Konstantin Chuguev , freebsd-mobile@FreeBSD.ORG Subject: Re: Mach64 ATI Rage Mobility on Inspiron 5000-7000 [Re: apmd] References: <200005222008.NAA21237@mina.sr.hp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Darryl Okahata wrote: > > If you want to get technical, I'm using the XFree86 4.0 server, > using the ATI drivers that support the ATI Rage Mobility-P chipset in my > Dell Inspiron 7500 laptop. > Is the XFree86/Mach64 4.0 server slower than XF86_Mach64 3.3.[56]? The XFree86 4.0 docs say that the Mach64 driver is _not_ accelerated. -- JMA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 16: 0: 5 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 144BF37B599 for ; Mon, 22 May 2000 16:00:00 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from mina.sr.hp.com (mina.sr.hp.com [15.4.42.247]) by palrel1.hp.com (Postfix) with ESMTP id C234758; Mon, 22 May 2000 15:59:58 -0700 (PDT) Received: from localhost (darrylo@localhost [127.0.0.1]) by mina.sr.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id PAA22706; Mon, 22 May 2000 15:59:58 -0700 (PDT) Message-Id: <200005222259.PAA22706@mina.sr.hp.com> To: "Jose M. Alcaide" Cc: freebsd-mobile@freebsd.org Subject: Re: Mach64 ATI Rage Mobility on Inspiron 5000-7000 [Re: apmd] Reply-To: Darryl Okahata In-reply-to: Your message of "Tue, 23 May 2000 00:41:32 PDT." <3929B79C.AFC90693@we.lc.ehu.es> Mime-Version: 1.0 (generated by tm-edit 1.5) Content-Type: text/plain; charset=US-ASCII Date: Mon, 22 May 2000 15:59:51 PDT From: Darryl Okahata Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Jose M. Alcaide" wrote: > Is the XFree86/Mach64 4.0 server slower than XF86_Mach64 3.3.[56]? The > XFree86 4.0 docs say that the Mach64 driver is _not_ accelerated. I've only used 3.3.5 and 4.0. I haven't done any benchmarks, as my "major" X apps are XEmacs and gimp/xv. I'm also using 4.0 in 24-bit mode, whereas I used 3.3.5 in 16-bit mode; this can make it difficult to compare. I haven't noticed any real slowdowns, except when exiting KDE: graying out the entire screen takes a couple seconds and is very noticeably slower. Still, I'm quite happy with 4.0. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 21: 1:37 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 783B537B5BB for ; Mon, 22 May 2000 21:01:33 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA08981; Mon, 22 May 2000 22:01:31 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA00112; Mon, 22 May 2000 22:00:29 -0600 (MDT) Message-Id: <200005230400.WAA00112@harmony.village.org> To: Thomas Shay Subject: Re: Should pcmcia card be recognized in install? Cc: freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Mon, 22 May 2000 17:14:00 EDT." References: Date: Mon, 22 May 2000 22:00:29 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Thomas Shay writes: : I'm messing around witj various pcmcia cards. I just installed 4.0-release : on a Thinkpad 600e (2645-UN1). I have a Megahertz CC10BT/2 10MBps ethernet : card installed and connected to the net during install. I go about : installing the system, and then when it gets to networking, my only : choices are slip and ppp. Does this indicate that the card is not being : recognized at this point, or does networking with pcmcia ethernet cards : always have to be configured after installation is complete? Should be. However, there are lots of problems. If your pcic has a different irq than 10, it won't work. You may also need to get the irq's right for the pccard in the setup. It is all a big pita right now. The CC10BT/2 is supported in 4.0, to a point (only one of them will work on a segment at a time). I'm using that exact card right now in -current (which has had this bug fixed). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 21: 3:35 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E00E837B5BB for ; Mon, 22 May 2000 21:03:32 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA08994; Mon, 22 May 2000 22:03:30 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA00159; Mon, 22 May 2000 22:02:29 -0600 (MDT) Message-Id: <200005230402.WAA00159@harmony.village.org> To: mike ryan Subject: Re: suspend/resume on z505hs Cc: freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Mon, 22 May 2000 16:44:10 EDT." <20000522164410.A18562@medianstrip.net> References: <20000522164410.A18562@medianstrip.net> <20000428141659.A74587@medianstrip.net> Date: Mon, 22 May 2000 22:02:29 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20000522164410.A18562@medianstrip.net> mike ryan writes: : suspend-to-disk also works, but only via Fn-F12. "apm -Z" just : results in this syslog message: : : "Entire system suspend failure: errcode = 96". apm -Z make the system go into what APM calls standby mode. This is a power mode that uses more power than suspend, but less than being on. Not all BIOSes support it. There's no way, with apm, to force suspend to memory vs suspend to disk. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon May 22 21:15:50 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from jasper.southwind.net (jasper.southwind.net [206.53.103.7]) by hub.freebsd.org (Postfix) with ESMTP id EA04337B999 for ; Mon, 22 May 2000 21:15:47 -0700 (PDT) (envelope-from gmains@southwind.net) Received: from localhost (gmains@localhost) by jasper.southwind.net (8.10.1/8.10.1) with ESMTP id e4N4Flx09582 for ; Mon, 22 May 2000 23:15:47 -0500 (CDT) X-Authentication-Warning: jasper.southwind.net: gmains owned process doing -bs Date: Mon, 22 May 2000 23:15:47 -0500 (CDT) From: Gabriel To: freebsd-mobile@FreeBSD.ORG Subject: xe0 not using rc.conf settings... 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 a Xircom Realport 10/100 + 56k modem PCMCIA card running on an HP Omnibook 3000. It is working fine, but xe0 seems to come up AFTER the rc.conf file is read (ie. xe0 is not up at the time of rc.conf being read at boot) and therefor not initializing. I can set the ip address using ifconfig, but it will not use DHCP as specified in rc.conf. Anyone have any ideas on how to make it use the rc.conf settings at boot time? Thanks! Gabriel =============================================================================== ------------------------------------------------------------------------------- Gabriel SouthWind Internet Access, Inc. Department Manager 120 S. Market SouthWind Technical Support 800-525-7963 ------------------------------------------------------------------------------- =============================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 23 2:24: 4 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 468F237B657 for ; Tue, 23 May 2000 02:23:13 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id LAA11030; Tue, 23 May 2000 11:22:00 +0200 (MET DST) Message-ID: <392A4DB8.D9C2AE51@we.lc.ehu.es> Date: Tue, 23 May 2000 11:22:00 +0200 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dpto. de Electricidad y Electronica X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Warner Losh Cc: mobile@FreeBSD.ORG Subject: Re: Xircom cards References: <390B1BFE.12525FB4@free.fr> <200004291738.LAA67302@harmony.village.org> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Warner Losh wrote: > > I plan on doing a MFC around May 15, but need to make sure that it > basically works, so even one tester would be enough :-) > I have just noticed the CVS log messages of the pccard MFC. Should the Xircom cards now work under 4.0-STABLE? -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 23 6:47:27 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 7498937BADB for ; Tue, 23 May 2000 06:46:44 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id PAA12692; Tue, 23 May 2000 15:46:04 +0200 (MET DST) Message-ID: <392A8B9C.6072A89F@we.lc.ehu.es> Date: Tue, 23 May 2000 15:46:04 +0200 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dpto. de Electricidad y Electronica X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Warner Losh , mobile@FreeBSD.ORG Subject: Re: Xircom cards References: <390B1BFE.12525FB4@free.fr> <200004291738.LAA67302@harmony.village.org> <392A4DB8.D9C2AE51@we.lc.ehu.es> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Jose M. Alcaide" wrote: > > Warner Losh wrote: > > > > I plan on doing a MFC around May 15, but need to make sure that it > > basically works, so even one tester would be enough :-) > > > > I have just noticed the CVS log messages of the pccard MFC. Should > the Xircom cards now work under 4.0-STABLE? > Oops, I have just checked the CVS logs and if_xe.c has not been MFC'ed yet. My question, then, has an obvious answer 8). Sorry! -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 23 7:30:30 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 390AE37B9C7 for ; Tue, 23 May 2000 07:28:22 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id QAA12884; Tue, 23 May 2000 16:26:41 +0200 (MET DST) Message-ID: <392A9521.E6B5242A@we.lc.ehu.es> Date: Tue, 23 May 2000 16:26:41 +0200 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dpto. de Electricidad y Electronica X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Warner Losh , mobile@FreeBSD.ORG Subject: Re: Xircom cards References: <390B1BFE.12525FB4@free.fr> <200004291738.LAA67302@harmony.village.org> <392A4DB8.D9C2AE51@we.lc.ehu.es> <392A8B9C.6072A89F@we.lc.ehu.es> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Jose M. Alcaide" wrote: > > "Jose M. Alcaide" wrote: > > > > I have just noticed the CVS log messages of the pccard MFC. Should > > the Xircom cards now work under 4.0-STABLE? > > > > Oops, I have just checked the CVS logs and if_xe.c has not been MFC'ed yet. > My question, then, has an obvious answer 8). Sorry! > Warner, I have just cvsupped and compiled a 4.0-STABLE with the xe driver MFC'ed (locally, of course 8) ), and voilà! my Xircom RealPort 100BTX works nicely. Just FYI. Regards, -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 23 7:43:45 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6134337BB3D for ; Tue, 23 May 2000 07:43:39 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id IAA10762; Tue, 23 May 2000 08:43:35 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id IAA81380; Tue, 23 May 2000 08:43:31 -0600 (MDT) Message-Id: <200005231443.IAA81380@billy-club.village.org> To: "Jose M. Alcaide" Subject: Re: Xircom cards Cc: mobile@FreeBSD.ORG In-reply-to: Your message of "Tue, 23 May 2000 11:22:00 +0200." <392A4DB8.D9C2AE51@we.lc.ehu.es> References: <392A4DB8.D9C2AE51@we.lc.ehu.es> <390B1BFE.12525FB4@free.fr> <200004291738.LAA67302@harmony.village.org> Date: Tue, 23 May 2000 08:43:31 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <392A4DB8.D9C2AE51@we.lc.ehu.es> "Jose M. Alcaide" writes: : I have just noticed the CVS log messages of the pccard MFC. Should : the Xircom cards now work under 4.0-STABLE? Soon. I need to integreate the 56k patch to -current, then backport the results to -stable. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 23 9:19: 7 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from cwb.pacific.net.hk (cwb.pacific.net.hk [202.14.67.92]) by hub.freebsd.org (Postfix) with ESMTP id 9CD6837B797 for ; Tue, 23 May 2000 09:19:04 -0700 (PDT) (envelope-from alexkwan@pacific.net.hk) Received: from tsingyi.pacific.net.hk (tsingyi.pacific.net.hk [202.14.67.240]) by cwb.pacific.net.hk with ESMTP id AAA04832 for ; Wed, 24 May 2000 00:19:01 +0800 (HKT) Received: from alexkwan (ppp195.dyn29.pacific.net.hk [202.64.29.195]) by tsingyi.pacific.net.hk with SMTP id AAA02187 for ; Wed, 24 May 2000 00:18:57 +0800 (HKT) Message-ID: <000701bfc4d2$b14c3100$c31d40ca@alexkwan> From: "Alex Kwan" To: Subject: Sony Z-505VA build-in 10/100 LAN Card Date: Wed, 24 May 2000 00:19:33 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! Does the Build-in 10/100 LAN Card of Sony Z-505VA supported by FreeBSD4.0? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 23 9:27:37 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from jasper.southwind.net (jasper.southwind.net [206.53.103.7]) by hub.freebsd.org (Postfix) with ESMTP id C179C37BA5C for ; Tue, 23 May 2000 09:27:32 -0700 (PDT) (envelope-from gmains@southwind.net) Received: from localhost (gmains@localhost) by jasper.southwind.net (8.10.1/8.10.1) with ESMTP id e4NGRTK19312 for ; Tue, 23 May 2000 11:27:29 -0500 (CDT) X-Authentication-Warning: jasper.southwind.net: gmains owned process doing -bs Date: Tue, 23 May 2000 11:27:29 -0500 (CDT) From: Gabriel To: mobile@FreeBSD.ORG Subject: Sound on an HP Omnibook 3000 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 Anyone have any experience in getting sound to work on an HP Omnibook 3000? It uses a Crystal Sound chipset, but I can't seem to find out what chipset exactly. I have Win95 as a dual boot option and here are the resources it is using: IRQ 5 DMA 1 sound playback DMA 0 sound record I/O 0220 I am running 3.4-STABLE and the following is currently compiled into my kernel: device pcm0 at isa? port ? tty irq 5 drq 1 The kernel compiles just fine and I can see it come up at boot up w/o any error messages, but sound does not work. Any help would be GREATLY appreciated! Thanks, Gabriel =============================================================================== ------------------------------------------------------------------------------- Gabriel SouthWind Internet Access, Inc. Department Manager 120 S. Market SouthWind Technical Support 800-525-7963 ------------------------------------------------------------------------------- =============================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 23 13:33:24 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0CD6C37B8E1 for ; Tue, 23 May 2000 13:33:22 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA11746; Tue, 23 May 2000 14:33:20 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA04085; Tue, 23 May 2000 14:32:14 -0600 (MDT) Message-Id: <200005232032.OAA04085@harmony.village.org> To: Gabriel Subject: Re: xe0 not using rc.conf settings... Cc: freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Mon, 22 May 2000 23:15:47 CDT." References: Date: Tue, 23 May 2000 14:32:14 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Gabriel writes: : I have a Xircom Realport 10/100 + 56k modem PCMCIA card running on an HP : Omnibook 3000. It is working fine, but xe0 seems to come up AFTER the : rc.conf file is read (ie. xe0 is not up at the time of rc.conf being read : at boot) and therefor not initializing. I can set the ip address using : ifconfig, but it will not use DHCP as specified in rc.conf. Anyone have : any ideas on how to make it use the rc.conf settings at boot time? I don't understand this. works great for me. Do you have xe0 listed in the interfaces? Do you have it runnign pccard_ether? I use this setup all the time with my 3com, ne2000 and sn based cards w/o a hitch. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue May 23 20:54: 5 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from mauna-kea.lart.net (mauna-kea.lart.net [206.50.17.2]) by hub.freebsd.org (Postfix) with ESMTP id 867C337BB84 for ; Tue, 23 May 2000 20:54:02 -0700 (PDT) (envelope-from sthomas@mauna-kea.lart.net) Received: (from sthomas@localhost) by mauna-kea.lart.net (8.9.1/8.9.1) id DAA22979 for freebsd-mobile@freebsd.org; Wed, 24 May 2000 03:54:00 GMT Date: Wed, 24 May 2000 03:54:00 +0000 From: Sam Thomas To: freebsd-mobile@freebsd.org Subject: wd0: interrupt timeout Message-ID: <20000524035400.A22927@lart.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org my machine: Dell Latitude CPi R400GT 128M RAM 6G hd 3.4R+PAO I was using my laptop in its normal capacity as a portable vt100 when it started chomping on the disk wildly. everything just stopped. I rebooted, and when it came up it started giving me error messages and stopped with: wd0: Last time I say: interrupt timeout. Probably a portable PC. (status 50 error 1) wd0: wdtimeout() DMA status 4 so, has anyone else experienced this? (I would suspect so, since the error message indicates a psychic ability to know that it's on a laptop) is there anything besides re-installing that I can do to recover from this? am I totally %$#@ed? tia, Sam -- Sam Thomas Geek Mercenary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 24 5:27:47 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 364F537B932; Wed, 24 May 2000 05:27:43 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from daniel.sobral (p12-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.77]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id VAA01296; Wed, 24 May 2000 21:27:40 +0900 (JST) Received: (from root@localhost) by daniel.sobral (8.9.3/8.9.3) id VAA00370; Wed, 24 May 2000 21:29:01 +0900 (JST) (envelope-from root) From: "Daniel C. Sobral" Message-Id: <200005241229.VAA00370@daniel.sobral> Subject: PCCardd To: imp@freebsd.org Date: Wed, 24 May 2000 21:28:55 +0900 (JST) Cc: freebsd-mobile@freebsd.org Disclaimer: Klaatu Barada Nikto! X-Mailer: ELM [version 2.4ME+ PL68 (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 Why is pccardd so late in the startup? I notice that it is being compiled static (through direct CFLAGS specification, instead of setting NOSHARED, though), but... Since aic0 is an indispensible part of my system (it has my local/, my X11R6, my dumpdev and my /var/crash, among other things), I finally tired of waiting my setup script finish post-boot, and decided to see if I could get pccardd to do what flag -z does (man pages are wonderful :). Motivated, I further investigated /etc/rc, and moved pccard initialization to right before swapon, edited my fstab, added dumpdev to my /etc/rc.conf (with the -z), moved pccard* and logger to /sbin and voila'! Things now work as I need them to. Now, I know the new card stuff is going to be very different, but will I have the ability to get my aic drives up and running before swapon gets run? Depending on how things are planned to work, I'd suggest adding some sort of flag by which devices that need to get going earlier, such as aic, can be probed for separately (and earlier) than those that need to be brought up later, for whatever reasons. MMMmmmmm. Maybe I should cc this somewhere. :-) I'll cc it to -mobile. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@root.bsdconspiracy.net Those who express random thoughts to legislative committees are often surprised and appalled to find themselves the instigators of law. -- Mark B. Cohen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 24 8:18:20 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id F348E37BC74 for ; Wed, 24 May 2000 08:18:16 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 12ucvH-0004U0-00 for freebsd-mobile@freebsd.org; Wed, 24 May 2000 11:18:15 -0400 Date: Wed, 24 May 2000 11:18:14 -0400 From: Peter Radcliffe To: freebsd-mobile@freebsd.org Subject: Re: wd0: interrupt timeout Message-ID: <20000524111814.C16056@pir.net> Mail-Followup-To: freebsd-mobile@freebsd.org References: <20000524035400.A22927@lart.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000524035400.A22927@lart.net>; from sthomas@lart.net on Wed, May 24, 2000 at 03:54:00AM +0000 X-fish: < Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sam Thomas probably said: > wd0: Last time I say: interrupt timeout. Probably a portable PC. > (status 50 error 1) > wd0: wdtimeout() DMA status 4 > has anyone else experienced this? (I would suspect so, since the > error message indicates a psychic ability to know that it's on a > laptop) > is there anything besides re-installing that I can do to recover from this? > am I totally %$#@ed? Every time I've seen this come up on the list it has meant the disk has gone bad ... P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 24 8:44:41 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from orpheus.so-com.net (orpheus.so-com.net [212.110.130.71]) by hub.freebsd.org (Postfix) with ESMTP id D75F437BD22 for ; Wed, 24 May 2000 08:44:30 -0700 (PDT) (envelope-from kivvy@orpheus.so-com.net) Received: (from kivvy@localhost) by orpheus.so-com.net (8.9.3/8.9.3) id SAA18462 for freebsd-mobile@freebsd.org; Wed, 24 May 2000 18:45:52 +0300 (EEST) (envelope-from kivvy) Message-Id: <200005241545.SAA18462@orpheus.so-com.net> Subject: TI1225 + ORINOCO aka WaveLAN IEEE 802.11 11Mb To: freebsd-mobile@freebsd.org Date: Wed, 24 May 2000 18:45:52 +0300 (EEST) From: Igor Kucherenko Reply-To: Igor Kucherenko X-Mailer: ELM [version 2.4ME+ PL68 (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 Hello all. Some weeks ego I saw letters with subject like this. Question is .. Have this hardware configuration (subj) properly supported by FreeBSD-4.0 or FreeBSD-current ? Thank you for comments for this letter. -- Igor Kucherenko Simferopol, Crimea, UA +380 652 511616 kivvy@so-com.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 24 11:50:17 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 5F80137BD3C for ; Wed, 24 May 2000 11:50:01 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from mina.sr.hp.com (mina.sr.hp.com [15.4.42.247]) by palrel3.hp.com (Postfix) with ESMTP id E97D0938 for ; Wed, 24 May 2000 11:49:59 -0700 (PDT) Received: from localhost (darrylo@localhost [127.0.0.1]) by mina.sr.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id LAA23904 for ; Wed, 24 May 2000 11:49:59 -0700 (PDT) Message-Id: <200005241849.LAA23904@mina.sr.hp.com> To: freebsd-mobile@freebsd.org Subject: Howto: FreeBSD & WaveLan [ was: Re: TI1225 + ORINOCO aka WaveLAN IEEE 802.11 11Mb ] Reply-To: Darryl Okahata In-reply-to: Your message of "Wed, 24 May 2000 18:45:52 PDT." <200005241545.SAA18462@orpheus.so-com.net> Mime-Version: 1.0 (generated by tm-edit 1.5) Content-Type: text/plain; charset=US-ASCII Date: Wed, 24 May 2000 11:49:58 PDT From: Darryl Okahata Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Some weeks ego I saw letters with subject like this. > Question is .. Have this hardware configuration (subj) > properly supported by FreeBSD-4.0 or FreeBSD-current ? I can't help with the TI1225, but here's a document that I've been writing on using the WaveLan cards with FreeBSD. I've been toying with submitting it to FreeBSD diary or 'zine, but I don't know if I'll ever get around to finishing it. It's taking up a lot of my time, and I don't know if there's really a big audience for it. It's a bit rough and a bit wordy, but it should cover most of the bases. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. =============================================================================== FreeBSD 4.X and WaveLan IEEE 802.11 Wireless Networking Wed May 24, 2000 (C) Copyright 2000, by Darryl Okahata (darrylo@sonic.net) INTRODUCTION This article describes how to set up a small home wireless LAN, using the Orinoco (previously Lucent) WaveLan IEEE 802.11 PC cards, a desktop PC, and a laptop. The idea here is that the desktop is always on, and can function as a gateway/router for the laptop. I have a desktop FreeBSD system running at home 24 hours a day, 7 days a week, and so this is a good solution for me. The hardware organization is simple: both the desktop and the laptop use the silver (64-bit encryption) or gold (128-bit encryption) PCMCIA WaveLan IEEE 802.11 cards to communicate. The laptop should already have an available PCMCIA slot for a WaveLan card, and the desktop uses the WaveLan PCMCIA adapter. Note that there is more than one type of "WaveLan" card. This article deals with the IEEE 802.11 WaveLan cards, and not older ones. Some people don't have a system that's always running, and so they may prefer using an Apple airport in place of the desktop. While this is another good solution, it's beyond the scope of this article. However, I'll list a few pros and cons of the desktop vs airport approach: Desktop: Pro: Somewhat inexpensive solution (around US$220-$250 for just the desktop-related hardware, not counting the laptop interface). Pro: No (registered) IP address required. (Assuming the use of NATD with unregistered source addresses such as 10.0.0.1, and assuming that the desktop is using a registered IP address instead of an unregistered one). Pro: No additional ethernet wiring (great if you have an ethernet hub with no free ports). Con: Noisier than an airport (assuming a typically- noisy power supply fan). Con: Not very portable. Con: Uses more power. (Well, perhaps not, if you use an old laptop in place of the desktop.) Airport: Con: More expensive (around US$300, not counting the laptop interface). Con: Currently needs a Macintosh to fully configure. Can be partially configured from Windows (but no NATD or DHCP available under Windows). Con: Yet another ethernet device to wire up to some hub that's short on ports. Needs an IP address. Pro: Very quiet. Pro: Very portable. Pro: Uses less power. Pro: Can be wall-mounted. Wall-mounting a desktop is problematic. If you're interested in using the airport, you can start here: Upgrading the airport to 128-bit encryption: http://www.msrl.com/airport-gold/ Check out the links near the bottom. Another solution, instead of a desktop or an airport, is to use a WaveLan Access Point. However, this is a fairly expensive solution, and one that's best used in commercial/business environments. REQUIREMENTS Here's what you need: * A good working knowledge of FreeBSD and system administration. In particular, you need to know how to configure and rebuild a kernel. You also need to know how to install and configure a (wired) network card. For example, if you don't know what a netmask is, why it's needed, and how routing works, stop now. The following instructions are not for novices and beginners. * A desktop and laptop running FreeBSD 4.0. I've used 4.0-Stable as of April 29 and May 2, and they work well. I'm sure other snapshots work. You'll need to have installed and configured FreeBSD 4.0 on these systems. I'm not going to cover anything related to installation or configuration, except for WaveLan-related issues. You'll also need to have installed and configured any (wired) ethernet LAN card(s) in the desktop. Make sure the wired LAN is functional before proceeding. * The desktop and laptop each need at least one free IRQ. One is required for the WaveLan PCMCIA card, and another should be used for the PCMCIA adapter. The PCMCIA adapter does not require an IRQ, but one should be used for best performance. If one is not used, the adapter will be used in "polled" mode. Note that the WaveLan PCMCIA card may not work with IRQ9 (not surprising, as IRQ9 is shared with IRQ2). If IRQ9 is all you have free, you'll have to come up with another free IRQ. (However, the default pccard.conf file does not allow IRQ9 to be used by PCMCIA cards.) * Two WaveLan IEEE 802.11 PCMCIA cards (gold or silver). The gold cards support 128-bit encryption, while the silver cards support 64-bit encryption. You'll use one in the desktop, and one in the laptop. * One WaveLan PCMCIA adapter interface for the desktop. I'm sure you can use any PCMCIA adapter card that FreeBSD supports; however, I know the WaveLan-specific one works, and it's not all that expensive (I paid US$65 for mine, and you can probably get it for less). I'm also only going to cover the ISA version of the adapter; I'm not going to talk about the PCI version. Where I am, it's pretty difficult to find the PCI version, and so I settled for the ISA one. One advantage of this is that it's possible to use an old 386 box as a WaveLan gateway. A disadvantage is that the ISA bus is going away, and so newer PCs may not have any ISA slots. CONFIGURING THE DESKTOP Here are the steps for configuring the desktop: 1. For the WaveLan PCMCIA adapter card, follow the card's instructions for installing it into the desktop. Just follow the hardware installation instructions; you don't have to follow the instructions for installing software drivers. On the other hand, if you are dual-booting Windows and FreeBSD, installing the Windows drivers will allow you to use the WaveLan under Windows, as well as allowing you to run the hardware and wireless LAN diagnostics. However, before you install the card, follow the instructions to set the card's base port address to 0x3E0. The default is 0x3E2. You don't really have to change the address to 0x3E0, but the default for FreeBSD is 0x3E0; if you don't change it here, you'll have to change the value used by the kernel (see below). Whatever you decide, make a note of the base port address. 2. Decide if you're going to use an IRQ for the PCMCIA adapter card. You need to use an IRQ for the WaveLan PCMCIA card, but the use of an IRQ for the PCMCIA adapter is optional. For best performance, an IRQ should be assigned to the PCMCIA adapter, but the adapter should still function in polled mode (without an IRQ). I haven't tested the polled mode, though. If you're not going to use an IRQ, skip to the next step. If you are going to use an IRQ, go into the desktop's BIOS setup routines, and tell the BIOS to not auto-assign IRQ 10. Hopefully, you have this free; if not, you should be able to use other IRQ values, as long as they are not shared or already used by other devices (I haven't tried this, though). In the following, I'm going to assume that IRQ 10 is used (if not, change "10" to whatever you're using). What's happening is that the WaveLan ISA PCMCIA adapter is not a plug-and-play card, and so you want to insure that the BIOS does not assign its IRQ to some other device/card. Note that the adapter IRQ is set via software (by FreeBSD) and not by some jumper setting. When you configure the FreeBSD kernel (see below), you'll be specifying the IRQ to use (as part of the pcic device), and you want to insure that this IRQ is free, and has not been assigned by the BIOS to some other device/card. To do this, you need to tell the BIOS that this IRQ is not available for use by PNP or PCI cards. For the AWARD BIOS, this setting is usually under the "PNP/PCI CONFIGURATION" or "PNP, PCI, & ONBOARD I/O" page. You'll want to set the BIOS settings to: Resources Controlled By: Manual IRQ 10: N (or "Legacy ISA") If the BIOS does assign IRQ 10 to another device/card (you do not want this to happen), the pccard functions will not work, and a good indication of this is an IRQ mismatch in dmesg, like: pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 11 Note the IRQ mismatch (10 vs 11). If this part is configured properly, the IRQ values should match, like: pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 If you have no free IRQs, you could try to use the WaveLan PCMCIA adapter in "polled" mode, which does not require an IRQ, but is more inefficient. I haven't tried this, though. If you're short on IRQs, you may want to disable any device that you don't need. For example, I don't need the second serial port, and so I disabled it, freeing the corresponding IRQ (IRQ3) for use by the WaveLan card. 3. Boot FreeBSD. 4. Edit /etc/rc.conf, and add lines like the following to it: pccard_enable="YES" pccard_mem="0xd0000" pccard_ifconfig="inet 10.0.0.1 netmask 255.255.255.0" pccard_conf="/etc/pccard.conf" gateway_enable="YES" firewall_enable="YES" firewall_type="simple" natd_enable="YES" natd_interface="fxp0" Here, you will have to edit the values for "pccard_mem", "pccard_ifconfig", and "natd_interface". You may also want to change "firewall_type". If the desktop is connected to the public Internet, you'll definitely want to change the firewall type. Read the ipfw(8) man page, as well as the comments in "/etc/rc.firewall". If you leave "firewall_type" set to "simple", you will have to edit /etc/rc.firewall; in that file, see the section for "simple" (search for "simple firewall") and follow the instructions there. The value of "pccard_mem" must match the setting used in the kernel configuration (i.e., the value of "iomem" in "device pcic0" -- see step X, below). You'll probably want to change "pccard_ifconfig" to reflect your local LAN settings. Here, the values you'll be placing here are the values that will be used by the WaveLan card. Since we will be using natd, we can use an unregistered IP address here. Change "natd_interface" to the interface of your wired, public LAN interface. The idea is that LAN packets will be arriving on the WaveLan interface, translated by natd, and then sent back out on the wired LAN specified by "natd_interface", and vice-versa. Save "/etc/rc.conf". 5. At the bottom of this message, there is an appended file, "/etc/setup_wi0". Install the file as "/etc/setup_wi0". Make sure the first line is "#! /bin/sh". Make sure it's executable. (If you don't know what I'm talking about, you really should not be doing this.) 6. Edit "/etc/setup_wi0". Read the comments at the beginning of the file and set the variables appropriately. This script will be executed when the WaveLan card is inserted, or at bootup if the card is present at bootup. This script sets up various WaveLan parameters, such as the frequency channel and optional encryption key. 7. Copy "/etc/defaults/pccard.conf.sample" to "/etc/pccard.conf". 8. Edit "/etc/pccard.conf", and look for the entry: # Lucent WaveLAN/IEEE card "Lucent Technologies" "WaveLAN/IEEE" config 0x1 "wi0" ? insert logger -t pccard:$device -s WaveLAN/IEEE inserted insert /etc/pccard_ether $device remove logger -t pccard:$device -s WaveLAN/IEEE removed remove /sbin/ifconfig $device delete In this entry, add the line: insert /etc/setup_$device So that the entry looks like: # Lucent WaveLAN/IEEE card "Lucent Technologies" "WaveLAN/IEEE" config 0x1 "wi0" ? insert logger -t pccard:$device -s WaveLAN/IEEE inserted insert /etc/pccard_ether $device insert /etc/setup_$device remove logger -t pccard:$device -s WaveLAN/IEEE removed remove /sbin/ifconfig $device delete Save "/etc/pccard.conf". 9. Next, you'll have to reconfigure and build a new kernel. IMPORTANT NOTE: READ EVERYTHING IN THIS STEP. YOU MAY RUN INTO PROBLEMS LATER, IF YOU DON'T. First, add the following parameters to your kernel config file, if they're not already there: options IPFIREWALL options IPDIVERT device wi [ Technically, you don't need to compile "device wi" into the kernel, as you can, theoretically, load the "if_wi" module at bootup (e.g., "kldload if_wi"). However, I haven't tested this, and, while it should work, I know that compiling the device into the kernel works. If anyone has any success with "kldload if_wi", please tell me, so that I can update this. ] Also, in your kernel config file, locate the section on PCCARD support, like: # PCCARD (PCMCIA) support device card device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd0000 If you previously deleted or commented out the above, put it back (you can copy the above lines from GENERIC or LINT). You don't need the following line, but, if you are using 0x3e2 for the WaveLan PCMCIA ISA adapter base address, you'll have to delete or comment it out: device pcic1 at isa? irq 11 port 0x3e2 iomem 0xd4000 disable However, you may have to edit this line: device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd0000 Here, you may have to change the IRQ and port settings, depending on what you did in steps 1 & 2, above. If you are not using an IRQ for the PCMCIA adapter (you're using it in polled mode), eliminate the IRQ setting, like: device pcic0 at isa? port 0x3e0 iomem 0xd0000 IMPORTANT NOTE: You may also have to change the value of iomem. If, after rebuilding the kernel and rebooting, the pccard interface doesn't work (assuming that you followed the instructions BELOW to enable it), try setting iomem to one of 0xd4000, 0xd8000, or 0xdc000. You may run into memory conflicts with 0xd0000. A good indication of a memory conflict is when "pccardc dumpcis" produces garbage (e.g, "code XXX ignored", where "XXX" is a number like "192"). It seems that people with SCSI controllers can run into this problem. If you change iomem, note that you must also change the corresponding entry in /etc/rc.conf. Build the new kernel, install it, and reboot. 10. If all goes well, after rebooting, you should see a message like (by default, this goes to the console only, is not visible via dmesg, and is not written to a log file): pccardd[44]: Card "Lucent Technologies"("WaveLAN/IEEE") matched "Lucent Technologies" ("WaveLAN/IEEE") This will be all on one line. After another moment or two, you should see a message like this: wi0: at port 0x240-0x27f irq 3 slot 0 on pccard0 Fortunately, this message is visible via dmesg, and so does get put into /var/log/messages. CONFIGURING THE LAPTOP Configuring the laptop is very similar to configuring the desktop, except that it's simpler, due to the fact that the PCMCIA interface is built into the laptop. TROUBLESHOOTING 1. Nothing appears to happen after rebooting. Run dmesg. Look for lines that start with "pcic0:". If you find some, the PCMCIA adapter was found, and you should skip to the next item. If you can't find any, this probably means that there is a problem with the PCMCIA adapter/controller: * Did you just reboot from Windows 95/98/NT? FreeBSD 4.X has a minor problem where the PCMCIA controller is not recognized if you just rebooted from Windows. If you reboot again, the PCMCIA controller should be found. (Basically, if you were running Windows, you need to reboot twice -- or turn off the power -- to get FreeBSD to recognize the adapter.) * Is the PCMCIA adapter port address correct? Note that the default address of the WaveLan PCMCIA adapter is 0x3E2, but the default for the FreeBSD driver is 0x3E0. They've got to match. 2. The ISA PCMCIA adapter does not recognize the WaveLan card; nothing happens when the card is inserted. If you assigned an IRQ to the ISA PCMCIA adapter (recommended), did you tell the BIOS that this IRQ is not available for use by PNP/PCI cards (see step #2 in the configuration section, above)? One indication that you didn't do this is an IRQ mismatch, like: pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 11 Note the IRQ mismatch (10 vs 11). If this is configured properly, the IRQ values should match, like: pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 3. The PCMCIA adapter does not recognize the WaveLan card; you get error messages like: pccardd: No card in database for ""("") This particular error is usually caused by a memory address conflict; if so, the solution is to set "iomem" to a different address (see step #9 in the configuration section, above). To verify a memory conflict, try running "pccard dumpcis"; if you get messages like "code XXX ignored", where "XXX" is a number, then you probably have a memory conflict. If you changed iomem, did you also edit /etc/rc.conf to reflect that fact? The values for iomem and pccard_mem in /etc/rc.conf must match. If you edit rc.conf, you'll have to reboot. If the memory addresses are correct (iomem and pccard_mem), "pccard dumpcis" should output a section like (in addition to a lot of other text): Tuple #4, code = 0x15 (Version 1 info), length = 80 000: 05 00 4c 75 63 65 6e 74 20 54 65 63 68 6e 6f 6c 010: 6f 67 69 65 73 00 57 61 76 65 4c 41 4e 2f 49 45 020: 45 45 00 56 65 72 73 69 6f 6e 20 30 31 2e 30 31 030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff Version = 5.0, Manuf = [Lucent Technologies],card vers = [WaveLAN/IEEE] Addit. info = [Version 01.01],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[] Note that the above is approximate; it may change with different card firmware revisions. 4. Did you edit /etc/pccard.conf to allow the use of IRQ9 for the WaveLan card (wi0)? IRQ9 may not work with the WaveLan card. You may have to come up with another IRQ. 5. The WaveLan driver complains about: wi0: No irq?! This means that the driver could not allocate a free IRQ for the WaveLan card. Unfortunately, there's no easy solution for this -- you've got to somehow free up an IRQ for the card. Note that the list of possible IRQs to use is listed in /etc/pccard.conf; if you free up an IRQ, make sure it's listed there. 6. The driver complains about: wi0: No I/O space?! This means that the driver could not allocate a range of I/O ports to use to access the card. I've only seen this when I tried to insert the WaveLan card into a laptop that already has another PCMCIA card in another slot, and the wi0 driver failed because it could not allocate an IRQ ("wi0: No irq?!"). If I ejected the other card and re-inserted the WaveLan card, I would then get the "No I/O space?!" error. The solution is to reboot. (I think this is caused by a minor bug in the pccard or wi driver code.) If the card is found and properly initialized, the problem is probably caused by some network-related error (the same types that afflict wired LAN cards), and so is beyond the scope of this article. =============================================================================== = Here is the "/etc/setup_wi0" script. ====== cut here ===== cut here ===== cut here ================================= #! /bin/sh set -e ############################################################################### # # Configuration variables: # IFC is the wavelan interface to use (e.g., "wi0"); this must be # specified: IFC=wi0 # STATION_NAME is, well, the "station name", which is really only used # by the WaveLan diagostic tools. When using the tools (in a remote # PC -- not this one), the tools will display this name when # identifying the WaveLan card in this system. Because it's only used # by remote diagnostic tools, it's not essential to set SYSTEM_NAME. # However, it is recommended that, if it is set, it be set to be the # same as the hostname (otherwise, you'll have to remember which # station name goes with which hostname). # # Note, however, that the following uses `hostname` as the default. # This may not work if this script is called at bootup (especially # when called from pccard.conf), because the hostname may not yet have # been set. In this case, you should hardcode a value here. STATION_NAME=`hostname | sed -e 's/\..*$//'` # NETWORK_NAME is the name of the network that you wish to join (be a # part of). NETWORK_NAME must be set if you wish this system to talk # to a WaveLan access point. The NETWORK_NAME can be "ANY" # (upper-case is required), in which case the card will talk to any # access point; otherwise, NETWORK_NAME must be set to the same name # used by the access point. If you are using "ad-hoc mode" (not using # an access point), which generally is the case with an home LAN, you # do not need to set NETWORK_NAME (because ad-hoc mode ignores the # NETWORK_NAME). NETWORK_NAME='ANY' # MODE determines how the WaveLan card talks to other cards. If you # are using a WaveLan access point, you must set this to "1" (BSS # mode), and you must also set a valid NETWORK_NAME (above), as the # NETWORK_NAME must correspond to the name used by the access point. # For LANs without an access point (the usual case for home LANs), # MODE should be "3" (ad-hoc mode). MODE=3 # 1 --> BSS, 3 --> ad-hoc mode # CHANNEL is the frequency channel to use. The default for cards sold # in the USA and Europe (except France) is channel 3, 11 in France, # and 14 in Japan. Valid channels are: # # USA: 1-11 # Europe (except France): 1-13 # France: 10-13 # Japan: 14 (only -- unchangeable) # # See wicontrol(8) for more information. CHANNEL=3 # Card default is channel 3 # KEY is the encryption key to use. If KEY is blank/empty or not set, # the encryption key is not set, and encryption will not be enabled. # If a key is specified here, encryption will be enabled (this script # does not support enabling/disabling encryption independently of key # values). Note that, although the wavelan supports up to four # different keys (but only one can be used at any one time), only one # key (key 1) is used here. # # Remember that all systems that talk to each other must use the same # key. # # See wicontrol(8) for valid key values. KEY= # # End of configuration variables. Nothing should have to be changed # past this point. # ############################################################################### PATH="/usr/sbin:/usr/bin:/sbin:/bin:$PATH" if [ "X$STATION_NAME" != "X" ] then wicontrol -i $IFC -s "$STATION_NAME" fi wicontrol -i $IFC -p $MODE if [ "X$NETWORK_NAME" != "X" ] then wicontrol -i $IFC -n "$NETWORK_NAME" fi if [ "X$CHANNEL" != "X" ] then wicontrol -i $IFC -f $CHANNEL fi if [ \( "X$KEY" != "X" \) -a \ \( "X$KEY" != "XNO" \) -a \ \( "X$KEY" != "Xno" \) -a \ \( "X$KEY" != "XNo" \) \ ] then wicontrol -i $IFC -k $KEY wicontrol -i $IFC -e 1 fi exit 0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed May 24 19: 1:25 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from PacHell.TelcoSucks.org (pachell.telcosucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 8D93837B88C for ; Wed, 24 May 2000 19:01:21 -0700 (PDT) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id TAA60696; Wed, 24 May 2000 19:01:12 -0700 (PDT) (envelope-from ulf) Date: Wed, 24 May 2000 19:01:12 -0700 From: Ulf Zimmermann To: Alex Kwan Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Sony Z-505VA build-in 10/100 LAN Card Message-ID: <20000524190112.D352@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net References: <000701bfc4d2$b14c3100$c31d40ca@alexkwan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <000701bfc4d2$b14c3100$c31d40ca@alexkwan>; from alexkwan@pacific.net.hk on Wed, May 24, 2000 at 12:19:33AM +0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.4-STABLE Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 24, 2000 at 12:19:33AM +0800, Alex Kwan wrote: > Hi! > > Does the Build-in 10/100 LAN Card of Sony Z-505VA > supported by FreeBSD4.0? Assuming its the same as on the Z505S[X] and Z505R[X], it would be a pci based Intel EtherExpress 100/Pro which is supported fine by the fxp driver. Only problem I once in a while run into is being in Win98, then reboot into FreeBSD and the driver says no MAC address assigned to the card it then hangs. Completly restarting it cleans that up. > > > Thanks > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 25 9: 0:56 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from jasper.southwind.net (jasper.southwind.net [206.53.103.7]) by hub.freebsd.org (Postfix) with ESMTP id 8F77A37C728 for ; Thu, 25 May 2000 09:00:53 -0700 (PDT) (envelope-from gmains@southwind.net) Received: from localhost (gmains@localhost) by jasper.southwind.net (8.10.1/8.10.1) with ESMTP id e4PG0rg05801 for ; Thu, 25 May 2000 11:00:53 -0500 (CDT) X-Authentication-Warning: jasper.southwind.net: gmains owned process doing -bs Date: Thu, 25 May 2000 11:00:53 -0500 (CDT) From: Gabriel To: mobile@FreeBSD.ORG Subject: HP Omnibook 3000 still no sound 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 Ok, I have been working on this for 3 days now and it is closer to having sound, but still it doesn't work. Here is the setup: FreeBSD 3.4 HP Omnibook 3000 128 MB RAM bla bla Uses a Crystal Sound chipset (still don't know which one exactly.) Dual boot with Win95 BIOS is set to ENABLE for the sound with the following hard coded in: IRQ 5 DMA 1 (playback) DMA 0 (record) I/O 220h (sb compat.) I/O 530h (WSS compat.) Kernel has the following in it: controller pnp device pcm0 at isa? port 0x220 tty irq 5 drq 1 I have tried setting the BIOS to PNP OS for the sound and setting up pnp in the kernel and kernel.conf but it never finds the card under PNP. I also tried to set it to PNP and in the kernel.conf file I set it to bios enable, still with no luck. At this point it finds the card on boot and seems to initialize it. But when I go into xmms and try to play an MP3, the speakers "pop" and xmms freezes. I think it is a DNA problem. Could FreeBSD be assigning DMA 1 to another piece of hardware? How would I find this out? Any help would be greatly appreciated. I have searched thru the archives and someone had posted a way to get an Omnibook 4100 working, but it did work for mine. (it said to use PNP and mine would work with PNP.) Thanks, Gabriel =============================================================================== ------------------------------------------------------------------------------- Gabriel SouthWind Internet Access, Inc. Department Manager 120 S. Market SouthWind Technical Support 800-525-7963 ------------------------------------------------------------------------------- =============================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 25 12: 2:28 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id BE27737B70C for ; Thu, 25 May 2000 12:02:18 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.7/nospam) with UUCP id VAA27532 for freebsd-mobile@FreeBSD.ORG; Thu, 25 May 2000 21:02:17 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 036C4885A; Thu, 25 May 2000 20:18:47 +0200 (CEST) Date: Thu, 25 May 2000 20:18:47 +0200 From: Ollivier Robert To: freebsd-mobile@FreeBSD.ORG Subject: Re: apmd Message-ID: <20000525201847.A26834@keltia.freenix.fr> Mail-Followup-To: freebsd-mobile@FreeBSD.ORG References: <200005162342.QAA24829@sodium.network-alchemy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.11i In-Reply-To: ; from tomg@egg.net on Wed, May 17, 2000 at 05:25:44AM -0700 X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Tom Glover: > Unfortunately not. I still cannot get 4.0 to recognize a lid > closure. However, thanks for the suggestion. There's a setting in the BIOS for sleep-upon-closure IIRC. Mine (a Z505SX) does it fine. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #78: Sun Feb 27 15:32:39 CET 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 25 12: 2:36 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id DC8C337B70C for ; Thu, 25 May 2000 12:02:28 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.7/nospam) with UUCP id VAA27537 for freebsd-mobile@FreeBSD.ORG; Thu, 25 May 2000 21:02:27 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 4650D885A; Thu, 25 May 2000 20:24:17 +0200 (CEST) Date: Thu, 25 May 2000 20:24:17 +0200 From: Ollivier Robert To: freebsd-mobile@FreeBSD.ORG Subject: Re: apmd Message-ID: <20000525202417.B26834@keltia.freenix.fr> Mail-Followup-To: freebsd-mobile@FreeBSD.ORG References: <200005162342.QAA24829@sodium.network-alchemy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.11i In-Reply-To: <200005162342.QAA24829@sodium.network-alchemy.com>; from Ken.Key@Nokia.com on Tue, May 16, 2000 at 04:42:39PM -0700 X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Ken Key: > device apm0 > > no "at nexus?, etc... As I recall, I found the above on the mobile Mine work with the following although I can't find the meaning of 0x31... # SIDHE # # Kernel config file (without PAO) # # $Id: //depot/sidhe/kernel/nSIDHE#4 $ machine i386 cpu I686_CPU ident SIDHE maxusers 32 ... # Power management support (see LINT for more options) device apm0 at isa? flags 0x31 # Advanced Power Management -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #78: Sun Feb 27 15:32:39 CET 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 25 12:14:14 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from web901.mail.yahoo.com (web901.mail.yahoo.com [128.11.23.76]) by hub.freebsd.org (Postfix) with SMTP id DD81F37B64E for ; Thu, 25 May 2000 12:14:10 -0700 (PDT) (envelope-from sorc_qd@yahoo.com) Received: (qmail 928 invoked by uid 60001); 25 May 2000 19:14:10 -0000 Message-ID: <20000525191410.927.qmail@web901.mail.yahoo.com> Received: from [196.28.130.212] by web901.mail.yahoo.com; Thu, 25 May 2000 12:14:10 PDT Date: Thu, 25 May 2000 12:14:10 -0700 (PDT) From: Tristan Seligmann Subject: PCMCIA Modem not working!! 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 After installing 4.0-CURRENT I fiddled around with /etc/pccard.conf and managed to get it to pick up my modem. It now prints something like "sio2 on pccard0" or something like that. However, whenever I cat /dev/cuaa2, the entire system locks up completely, requiring a cold reboot. Rule #1. Ignore all other rules except for this one. Rule #2. Ignore rule #1. -=-=-=- Tristan Seligmann sorc_qd@yahoo.com __________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 25 12:26:53 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 73EC637B56C for ; Thu, 25 May 2000 12:26:50 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA40662; Thu, 25 May 2000 21:26:43 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200005251926.VAA40662@freebsd.dk> Subject: Re: PCMCIA Modem not working!! In-Reply-To: <20000525191410.927.qmail@web901.mail.yahoo.com> from Tristan Seligmann at "May 25, 2000 12:14:10 pm" To: sorc_qd@yahoo.com (Tristan Seligmann) Date: Thu, 25 May 2000 21:26:43 +0200 (CEST) Cc: freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Tristan Seligmann wrote: > After installing 4.0-CURRENT I fiddled around with /etc/pccard.conf and > managed to get it to pick up my modem. It now prints something like > "sio2 on pccard0" or something like that. However, whenever I cat > /dev/cuaa2, the entire system locks up completely, requiring a cold > reboot. This is sortof a known problem, try to insert a reset 1000 command in the entry for your modem, it helped me at least... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 25 12:29: 5 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from www.chasm.org (adsl-63-195-80-23.dsl.snfc21.pacbell.net [63.195.80.23]) by hub.freebsd.org (Postfix) with ESMTP id 9FA4437B56C for ; Thu, 25 May 2000 12:29:03 -0700 (PDT) (envelope-from martin@chasm.org) Received: from aria.gotomydoc.com (aria [192.168.0.3]) by www.chasm.org (8.9.3/8.9.3) with ESMTP id MAA83902 for ; Thu, 25 May 2000 12:27:38 -0700 (PDT) (envelope-from martin@chasm.org) Message-Id: <4.3.1.0.20000525122304.00b24390@chasm.org> X-Sender: martin@chasm.org X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Thu, 25 May 2000 12:28:38 -0700 To: freebsd-mobile@freebsd.org From: Charles Martin Subject: 4.0 Release doesn't initialize pccard? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am trying to install 4.0-RELEASE on a Sony Vaio PCG-F490. I have a Netgear FA410TXC card. The PCCARD initialization part of the install asks about memory area and IRQ. I have tried all twelve combinations (four for the memory address and three for the IRQs), but the link lights on my connection do not come on. Is there anything I can do, perhaps at the boot prompt? It sounds as if people do have this card working with their laptops, so there must be a way... also, at what point in the process should the link lights come on for the ethernet connection? Also, is there anyway to get back to the pccard initialization portion of the install, without having to reboot kern.flp and mfsroot.flp? (And shouldn't the pccard initialization test to see if the link exists, if that is possible?) Thanks for any help... Charles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu May 25 21:55:27 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from cwb.pacific.net.hk (cwb.pacific.net.hk [202.14.67.92]) by hub.freebsd.org (Postfix) with ESMTP id D87B237B570 for ; Thu, 25 May 2000 21:55:23 -0700 (PDT) (envelope-from alexkwan@pacific.net.hk) Received: from kwaifong.pacific.net.hk (kwaifong.pacific.net.hk [202.14.67.7]) by cwb.pacific.net.hk with ESMTP id MAA28555 for ; Fri, 26 May 2000 12:55:22 +0800 (HKT) Received: from alexkwan (ppp105.dyn9.pacific.net.hk [202.64.9.105]) by kwaifong.pacific.net.hk with SMTP id MAA19871 for ; Fri, 26 May 2000 12:55:21 +0800 (HKT) Message-ID: <000701bfc6d0$7371d380$690940ca@alexkwan> From: "Alex Kwan" To: Subject: Re: How to edit /etc/remote for PCMCIA modem Date: Fri, 26 May 2000 13:08:36 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! I am using PCMCIA modem to dialup to connect Internet, the interface of modem is sio3, also I make a device ttyd4 and edit the /etc/ppp/ppp.conf (set device /dev/ttyd4), everything is going right. Now I wanted to remote login to another host with the PCMCIA modem thorough the phone line, How to edit the /etc/remote (1. or 2. or other?) 1) cd /dev and ./MAKEDEV cuaa4 edit the /etc/remote as: cuaa4:dv=/dev/cuaa4:br#115200:pa=none or 2) edit the /etc/remote as: ttyd4:dv=/dev/ttyd4:br#115200:pa=none Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 26 8:23:24 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id F109E37B752 for ; Fri, 26 May 2000 08:23:20 -0700 (PDT) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id e4QFNJn26041 for ; Fri, 26 May 2000 08:23:19 -0700 (PDT) Message-Id: <200005261523.e4QFNJn26041@ptavv.es.net> To: freebsd-mobile@freebsd.org Subject: apm on IBM ThinkPad 600E Date: Fri, 26 May 2000 08:23:19 -0700 From: "Kevin Oberman" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I want to enable APM on my ThinkPad 600E, but a scan of the archives makes me a bit nervous. Does anyone have either information on a functional kernel configuration for this beast or a site where I might find it? Thanks, R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 26 11:29:48 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id BD3B637B74F for ; Fri, 26 May 2000 11:29:44 -0700 (PDT) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id e4QITVn22584; Fri, 26 May 2000 11:29:31 -0700 (PDT) Message-Id: <200005261829.e4QITVn22584@ptavv.es.net> To: "Sean O'Connell" , "Ross A Lippert" Cc: freebsd-mobile@freebsd.org Subject: Re: apm on IBM ThinkPad 600E In-reply-to: Your message of "Fri, 26 May 2000 12:49:14 EDT." <20000526124914.A8361@stat.Duke.EDU> Date: Fri, 26 May 2000 11:29:31 -0700 From: "Kevin Oberman" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks to both of you. I had the kernel built OK (albeit with flags 0x13), but I forgot to put the apm_enable="YES" into my rc.config. Sigh. It now works like a champ except that the Ethernet will wake my system up instantly if I leave it connected. But that's a minor annoyance. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 26 11:56:47 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 4C0CE37B577; Fri, 26 May 2000 11:56:29 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id PAA12930; Fri, 26 May 2000 15:15:26 +0100 (BST) (envelope-from nik) Date: Fri, 26 May 2000 15:15:25 +0100 From: Nik Clayton To: Nik Clayton Cc: mobile@freebsd.org Subject: Re: DFE650 unresponsive after reattaching balun Message-ID: <20000526151525.A12192@catkin.nothing-going-on.org> References: <20000510011357.A11828@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000510011357.A11828@catkin.nothing-going-on.org>; from nik@freebsd.org on Wed, May 10, 2000 at 01:13:57AM +0100 Organization: FreeBSD Project Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 10, 2000 at 01:13:57AM +0100, Nik Clayton wrote: > Having just made the jump from 3.2-PAO to 4.0-stable on my Vaio F270, > things are going fairly well. [...] > Under 3.2-PAO I could disconnect the balun (or 'dongle', if you prefer) > from the network card, but leave the network card in the machine. I could > then use the machine off the network as normal -- I'd get a few messages > in syslog about the network not responding, but nothing that seemed to > cause any problems. [...] > I just tried it today with 4.0-stable and it doesn't work. I get the usual > syslog messages about the network not being contactable. Then, when I > plug the balun back in the link lights don't come on. "ifconfig -a" shows > the ed1 interface as being "UP", and with an IP address. I tried removing > and reinserting the card to see if I could force pccardd to redetect it, > but no joy. I tried killing and restarting pccard, and then removing and > reinserting the card -- again, no joy. In the end I rebooted, and the card > came back to life. Following a suggestion from Sean O'Connell, I've been playing around with this a little bit more. Two things have helped. The first was replacing the complete "device ed1 ..." line in the kernel config file with just "device ed". The second was using pccardc to power the card off and on. When I plug the balun back in the power lights don't come on. If I eject the card there are no kernel messages printed, and similarly, if I reinsert the card, nothing happens. However, if I leave the card in and run "pccardc power 0 0" then the kernel prints that the card in slot 0 has been removed, and if I then run "pccardc power 0 1" then the kernel reports the card has been inserterd, prints the recognition string for the DFE 650, and then things can proceed as normal. This is the same laptop and card as I was using with PAO 3.2, so it looks like the functionality to do this automatically has been lost somewhere along the way. From memory, I recall that with 3.2 if I suspended the machine the kernel would print that the cards had been removed, and would print that they'd been reinserted when I resumed. I assume I could use apmd to automatically do the power off then on trick when I suspend and resume now? N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri May 26 15: 6: 6 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 094E537B90A for ; Fri, 26 May 2000 15:06:03 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA24335; Fri, 26 May 2000 16:06:01 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA92794; Fri, 26 May 2000 16:04:47 -0600 (MDT) Message-Id: <200005262204.QAA92794@harmony.village.org> To: "Daniel C. Sobral" Subject: Re: PCCardd Cc: freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Wed, 24 May 2000 21:28:55 +0900." <200005241229.VAA00370@daniel.sobral> References: <200005241229.VAA00370@daniel.sobral> Date: Fri, 26 May 2000 16:04:47 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200005241229.VAA00370@daniel.sobral> "Daniel C. Sobral" writes: : Motivated, I further investigated /etc/rc, and moved pccard : initialization to right before swapon, edited my fstab, added dumpdev to : my /etc/rc.conf (with the -z), moved pccard* and logger to /sbin and : voila'! Things now work as I need them to. Cool. One reason we didn't do that is that it will take a long time to boot on some machines. The card init stuff takes approx 30 seconds in OLDCARD. : Now, I know the new card stuff is going to be very different, but will I : have the ability to get my aic drives up and running before swapon gets : run? Depending on how things are planned to work, I'd suggest adding : some sort of flag by which devices that need to get going earlier, such : as aic, can be probed for separately (and earlier) than those that need : to be brought up later, for whatever reasons. Well, NetBSD kinda supports having root on a pccard device, if the ROMs support it. I say kinda, because it supports 1 card, but not two last time I checked. NEWCARD, which is a port from NetBSD, will have at most a couple of seconds of delays and won't need pccardd to be running to do device attachment. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat May 27 1:16:23 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E9EAF37B6C4 for ; Sat, 27 May 2000 01:16:19 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p23-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.152]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id RAA17212; Sat, 27 May 2000 17:16:12 +0900 (JST) Message-ID: <392F849B.D1D5D147@newsguy.com> Date: Sat, 27 May 2000 17:17:31 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Warner Losh Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: PCCardd References: <200005241229.VAA00370@daniel.sobral> <200005262204.QAA92794@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Warner Losh wrote: > > In message <200005241229.VAA00370@daniel.sobral> "Daniel C. Sobral" writes: > : Motivated, I further investigated /etc/rc, and moved pccard > : initialization to right before swapon, edited my fstab, added dumpdev to > : my /etc/rc.conf (with the -z), moved pccard* and logger to /sbin and > : voila'! Things now work as I need them to. > > Cool. One reason we didn't do that is that it will take a long time > to boot on some machines. The card init stuff takes approx 30 seconds > in OLDCARD. I know that, but -z can be specified on rc.conf optionally. The moving around requires changing rc, which causes trouble with mergemaster later, and the /usr/[s]bin->/sbin change. > : Now, I know the new card stuff is going to be very different, but will I > : have the ability to get my aic drives up and running before swapon gets > : run? Depending on how things are planned to work, I'd suggest adding > : some sort of flag by which devices that need to get going earlier, such > : as aic, can be probed for separately (and earlier) than those that need > : to be brought up later, for whatever reasons. > > Well, NetBSD kinda supports having root on a pccard device, if the > ROMs support it. I say kinda, because it supports 1 card, but not two > last time I checked. Are there ROMs which support pccard? Interesting... > NEWCARD, which is a port from NetBSD, will have at most a couple of > seconds of delays and won't need pccardd to be running to do device > attachment. Good. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@another.bsdconspiracy.org "Sentience hurts." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat May 27 8:29:38 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 962EE37B7E9 for ; Sat, 27 May 2000 08:29:35 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb47.imasy.or.jp [202.227.24.175]) by tasogare.imasy.or.jp (8.10.1+3.3W/3.7W-tasogare/smtpfeed 1.04) with ESMTP id e4RFTOR94187 for ; Sun, 28 May 2000 00:29:26 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: mobile@FreeBSD.ORG Subject: CFR: MFPAO pccard.conf regex matching support X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000528002918N.iwasaki@jp.FreeBSD.org> Date: Sun, 28 May 2000 00:29:18 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 19 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Here is patches for card line parameters matching by regex(3). http://people.freebsd.org/~iwasaki/pccard/pccardd-regex.diff You can describe the card strings which is somewhat difficult to specify or slightly different with one entry. This feature will be enabled only if the string is enclosed by '/' something like; card "SunDisk" "/.*/" Also, this patch set includes matching additional information strings followed by version string. This is for the card which is difficult to idendentify by only the manufacturer and card version strings matching. card "MACNICA" "MIRACLE SCSI" "mPS100" "D.0" I'll commit this on comming Tuesday if no objections. Have fun! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat May 27 17:42:22 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8FF4337B990 for ; Sat, 27 May 2000 17:42:17 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA29966; Sat, 27 May 2000 18:42:16 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA01598; Sat, 27 May 2000 18:42:04 -0600 (MDT) Message-Id: <200005280042.SAA01598@harmony.village.org> To: Igor Kucherenko Subject: Re: TI1225 + ORINOCO aka WaveLAN IEEE 802.11 11Mb Cc: freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Wed, 24 May 2000 18:45:52 +0300." <200005241545.SAA18462@orpheus.so-com.net> References: <200005241545.SAA18462@orpheus.so-com.net> Date: Sat, 27 May 2000 18:42:04 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200005241545.SAA18462@orpheus.so-com.net> Igor Kucherenko writes: : Some weeks ego I saw letters with subject like this. : Question is .. Have this hardware configuration (subj) : properly supported by FreeBSD-4.0 or FreeBSD-current ? Should be. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat May 27 17:44:24 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6589437B5D6 for ; Sat, 27 May 2000 17:44:21 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA29979; Sat, 27 May 2000 18:44:19 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA01625; Sat, 27 May 2000 18:44:09 -0600 (MDT) Message-Id: <200005280044.SAA01625@harmony.village.org> To: Tristan Seligmann Subject: Re: PCMCIA Modem not working!! Cc: freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Thu, 25 May 2000 12:14:10 PDT." <20000525191410.927.qmail@web901.mail.yahoo.com> References: <20000525191410.927.qmail@web901.mail.yahoo.com> Date: Sat, 27 May 2000 18:44:09 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20000525191410.927.qmail@web901.mail.yahoo.com> Tristan Seligmann writes: : After installing 4.0-CURRENT I fiddled around with /etc/pccard.conf and : managed to get it to pick up my modem. It now prints something like : "sio2 on pccard0" or something like that. However, whenever I cat : /dev/cuaa2, the entire system locks up completely, requiring a cold : reboot. Add a delay in the reset. # AT&T Paradyne KeepInTouch 14.4 modem card "AT&T Paradyne" "KeepInTouch Card" config 0x23 "sio3" ? reset 1000 insert logger -t pccard:$device -s ATT Paradyne 14.4 inserted remove logger -t pccard:$device -s ATT Paradyne 14.4 removed And let me know what the card is so I can add it to pccard.conf. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat May 27 17:46: 8 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CB76B37B5D6 for ; Sat, 27 May 2000 17:46:04 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA29990; Sat, 27 May 2000 18:46:03 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA01648; Sat, 27 May 2000 18:45:53 -0600 (MDT) Message-Id: <200005280045.SAA01648@harmony.village.org> To: "Daniel C. Sobral" Subject: Re: PCCardd Cc: freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Sat, 27 May 2000 17:17:31 +0900." <392F849B.D1D5D147@newsguy.com> References: <392F849B.D1D5D147@newsguy.com> <200005241229.VAA00370@daniel.sobral> <200005262204.QAA92794@harmony.village.org> Date: Sat, 27 May 2000 18:45:53 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <392F849B.D1D5D147@newsguy.com> "Daniel C. Sobral" writes: : I know that, but -z can be specified on rc.conf optionally. The moving : around requires changing rc, which causes trouble with mergemaster : later, and the /usr/[s]bin->/sbin change. Hmmm. I'll have to think about this... : Are there ROMs which support pccard? Interesting... Yes. I've seen them in the embedded world. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat May 27 17:48:57 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0BCC337B51F for ; Sat, 27 May 2000 17:48:55 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA30011; Sat, 27 May 2000 18:48:54 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA01689; Sat, 27 May 2000 18:48:43 -0600 (MDT) Message-Id: <200005280048.SAA01689@harmony.village.org> To: Mitsuru IWASAKI Subject: Re: CFR: MFPAO pccard.conf regex matching support Cc: mobile@FreeBSD.ORG In-reply-to: Your message of "Sun, 28 May 2000 00:29:18 +0900." <20000528002918N.iwasaki@jp.FreeBSD.org> References: <20000528002918N.iwasaki@jp.FreeBSD.org> Date: Sat, 27 May 2000 18:48:43 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20000528002918N.iwasaki@jp.FreeBSD.org> Mitsuru IWASAKI writes: : I'll commit this on comming Tuesday if no objections. These patches look good to me. Please also MFC after a little while. BTW, is the "function" change close to being ready to commit? 90% of the cards I add these days are for modems and compact flash/ata cdrom cards. :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat May 27 23: 2:19 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from oxygen.yy.ics.keio.ac.jp (oxygen.yy.ics.keio.ac.jp [131.113.47.3]) by hub.freebsd.org (Postfix) with ESMTP id 4212537B5D3 for ; Sat, 27 May 2000 23:02:07 -0700 (PDT) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (ppp171.dialup.st.keio.ac.jp [131.113.27.171]) by oxygen.yy.ics.keio.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id OAA16476; Sun, 28 May 2000 14:57:42 +0900 (JST) (envelope-from sanpei@sanpei.org) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id OAA00419; Sun, 28 May 2000 14:57:49 +0900 (JST) Date: Sun, 28 May 2000 14:57:49 +0900 (JST) Message-Id: <200005280557.OAA00419@lavender.yy.cs.keio.ac.jp> To: imp@village.org Cc: kivvy@so-com.net, freebsd-mobile@FreeBSD.ORG Subject: Re: TI1225 + ORINOCO aka WaveLAN IEEE 802.11 11Mb In-Reply-To: Your message of "Sun, 28 May 2000 09:42:04 JST". <200005280042.SAA01598@harmony.village.org> From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org imp@village.org wrote: >> In message <200005241545.SAA18462@orpheus.so-com.net> Igor Kucherenko writes: >> : Some weeks ego I saw letters with subject like this. >> : Question is .. Have this hardware configuration (subj) >> : properly supported by FreeBSD-4.0 or FreeBSD-current ? >> >> Should be. By the way, Warner-san, do you have any plan to MFC about ti1xxx_pci_init in sys/pci/pcic_p.c. http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/pci/pcic_p.c.diff?r1=1.20&r2=1.21 http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/pci/pcic_p.h.diff?r1=1.10&r2=1.11 Some TI-1xxx Chip needs this change. MIHIRA Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat May 27 23:11:31 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7196E37B5D3 for ; Sat, 27 May 2000 23:11:28 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA31499; Sun, 28 May 2000 00:11:25 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA50563; Sun, 28 May 2000 00:11:14 -0600 (MDT) Message-Id: <200005280611.AAA50563@harmony.village.org> To: sanpei@sanpei.org (MIHIRA Yoshiro) Subject: Re: TI1225 + ORINOCO aka WaveLAN IEEE 802.11 11Mb Cc: kivvy@so-com.net, freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Sun, 28 May 2000 14:57:49 +0900." <200005280557.OAA00419@lavender.yy.cs.keio.ac.jp> References: <200005280557.OAA00419@lavender.yy.cs.keio.ac.jp> Date: Sun, 28 May 2000 00:11:14 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200005280557.OAA00419@lavender.yy.cs.keio.ac.jp> MIHIRA Yoshiro writes: : By the way, Warner-san, do you have any plan to MFC about : ti1xxx_pci_init in sys/pci/pcic_p.c. I thought I already had. Oh wait, I missed this one. It was in sys/pci. Yes. I do plan on it. I'll do it shortly. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat May 27 23:24:42 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 08B5437B6AC for ; Sat, 27 May 2000 23:24:40 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb30.imasy.or.jp [202.227.24.158]) by tasogare.imasy.or.jp (8.10.1+3.3W/3.7W-tasogare/smtpfeed 1.04) with ESMTP id e4S6OZR47310; Sun, 28 May 2000 15:24:36 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: imp@village.org Cc: iwasaki@jp.FreeBSD.org, mobile@FreeBSD.ORG Subject: Re: CFR: MFPAO pccard.conf regex matching support In-Reply-To: <200005280048.SAA01689@harmony.village.org> References: <20000528002918N.iwasaki@jp.FreeBSD.org> <200005280048.SAA01689@harmony.village.org> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000528152435T.iwasaki@jp.FreeBSD.org> Date: Sun, 28 May 2000 15:24:35 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 26 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > : I'll commit this on comming Tuesday if no objections. > > These patches look good to me. Please also MFC after a little while. OK, I'll MFC it on the next weekend together with sanpei-san and my recent works such as multi io-win support, dumpcis improvement, etc. > BTW, is the "function" change close to being ready to commit? 90% of > the cards I add these days are for modems and compact flash/ata cdrom > cards. :-) 4-STABLE pccardd has already "function" feature, it MFCed on April 15th :-) % cvs -R log -rRELENG_4 file.c : revision 1.24.2.1 date: 2000/04/15 10:56:20; author: iwasaki; state: Exp; lines: +328 -53 MFC: - default config file changed from /etc/pccard.conf to /etc/defaults/pccard.conf in pccardd. - remove etc/pccard.conf.sample. This file is no longer used. - support wildcard entry for generic serial and fixed disk as fallthrough entry. - add restart capability by SIGHUP. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message