From owner-freebsd-mobile Sun Aug 2 15:04:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23851 for freebsd-mobile-outgoing; Sun, 2 Aug 1998 15:04:56 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from nohow.demon.co.uk (nohow.demon.co.uk [212.228.18.189]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23844; Sun, 2 Aug 1998 15:04:49 -0700 (PDT) (envelope-from jose@nohow.demon.co.uk) Received: from localhost (jose@localhost) by nohow.demon.co.uk (8.8.8/8.8.8) with SMTP id XAA00245; Sun, 2 Aug 1998 23:04:02 +0100 (BST) (envelope-from jose@nohow.demon.co.uk) Date: Sun, 2 Aug 1998 23:04:01 +0100 (BST) From: Jose Marques To: freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: wd driver multi-sector I/O and laptops 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 am running FreeBSD 2.2.7-stable (last updated on August 1st) on a Toshiba Libretto 70CT. I have replaced the supplied HD with a bigger 3.2GB Hitachi unit. I have been playing with the "32-bit" and "multi-sector transfer" options of the wd driver. I have the following in my kernel config file: controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 flags 0x80ff This produces the following probe message: wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 3102MB (6354432 sectors), 6304 cyls, 16 heads, 63 S/T, 512 B/S Using iozone before and after I see a great improvement in sequential access. The only problem occurs when I suspend my laptop and then resume. If I resume from RAM I have no problem, however, if I resume from disk then I see the following error almost immediately after the system has resumed: wd0s2f: reverting to non-multi sector mode writing fsbn 65776 of 65776-65791 (wd0s2 bn 1761520; cn 218 tn 56 sn 40)wd0: status 51 error 4 Running iozone after this shows that performance has dropped to the level when not using multi-sector transfers. I have tried using 0xc0ff (suspend-hack) but the problem still occurs. Looking at the file "/sys/i386/isa/wd.c" I notice that the driver turns off multi-sector i/o on any such error. I was wondering if it was "safe" to stop it doing this. Alternatively does the problem I describe above constitute a "bug" that I should report - or is it meant to behave that way. Thanks in advance for any advice. -- Jose Marques To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Aug 2 23:20:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03321 for freebsd-mobile-outgoing; Sun, 2 Aug 1998 23:20:19 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03309 for ; Sun, 2 Aug 1998 23:20:14 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id XAA25949; Sun, 2 Aug 1998 23:17:51 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Sun, 2 Aug 1998 23:17:50 -0700 (PDT) From: Doug White To: Brian Somers cc: Jeroen Ruigrok/Asmodai , FreeBSD Mobile Subject: Re: Latitude CP/NeoMagic 128XD In-Reply-To: <199808010223.DAA23578@awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 1 Aug 1998, Brian Somers wrote: > > Hiya, > > > > anyone have a 2.2.6 XF86Config file for the Dell Latitude CP with the > > NeoMagic 128XD. I have one for the 2.2.5 but having some problems with it > > and since X configuration ain't my best part yet =) > > > > Thankee, > > You'd do well to check the mail archive at www.FreeBSD.org. The > NeoMagic was just discussed - along with the url of a site that will > give you a simple driver that you can integrate with your X (svga) > server. If you're not too big on building the X server yourself, I can provide a binary (with absolutely no warranty). I'm using it on my Digital HiNote 575 but that has a 128ZV, not the XD. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Aug 3 12:00:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16557 for freebsd-mobile-outgoing; Mon, 3 Aug 1998 12:00:36 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16535 for ; Mon, 3 Aug 1998 12:00:25 -0700 (PDT) (envelope-from skywise@wxs.nl) Received: from po01.wxs.nl ([195.121.6.41]) by smtp02.wxs.nl (Netscape Messaging Server 3.54) with ESMTP id AAA570C for ; Mon, 3 Aug 1998 20:59:59 +0200 Received: from webmail ([195.121.6.34]) by po01.wxs.nl (Netscape Messaging Server 3.54) with SMTP id AAA433; Mon, 3 Aug 1998 19:59:49 +0100 From: Jeroen Ruigrok To: Doug White Cc: FreeBSD Mobile Subject: Re: Latitude CP/NeoMagic 128XD X-Mailer: Netscape Messenger Express 3.5 [Mozilla/4.05 [en] (Win95; I ;Nav)] Date: Mon, 3 Aug 1998 19:59:49 +0100 Message-ID: <7718493E173D.AAA433@po01.wxs.nl> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >On Sat, 1 Aug 1998, Brian Somers wrote: > >> > Hiya, >> > >> > anyone have a 2.2.6 XF86Config file for the Dell Latitude CP with the >> > NeoMagic 128XD. I have one for the 2.2.5 but having some problems with it >> > and since X configuration ain't my best part yet =) >> > >> > Thankee, >> >> You'd do well to check the mail archive at www.FreeBSD.org. The >> NeoMagic was just discussed - along with the url of a site that will >> give you a simple driver that you can integrate with your X (svga) >> server. > >If you're not too big on building the X server yourself, I can provide a >binary (with absolutely no warranty). I'm using it on my Digital HiNote >575 but that has a 128ZV, not the XD. > >Doug White Thanks for the offer, but I have compiled the server myself now =) And I am now tweaking the XF86Config file. Got it at 640x480 x 8bpp running stable now =) With regards, Jeroen Ruigrok/Asmodai To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Aug 4 00:11:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09898 for freebsd-mobile-outgoing; Tue, 4 Aug 1998 00:11:01 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09861; Tue, 4 Aug 1998 00:10:39 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id IAA25263; Tue, 4 Aug 1998 08:04:29 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199808040704.IAA25263@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Somers cc: Randy Philipp , Doug White , Greg Lehey , freebsd-mobile@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Neomagic chipset - is it a hardware problem ? In-reply-to: Your message of "Sat, 25 Jul 1998 21:32:52 BST." <199807252032.VAA00175@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 08:04:28 +0100 From: Brian Somers Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've found out more about this flickering problem.... it only occurs when the laptop is physically warm - the warmer, the more flickering. If the machine sleeps for ~15 minutes, it'll wake up with a perfect picture and that picture will start to deteriorate with the building heat. If I switch the display off for 15 minutes it makes no difference. This is all under load. If the machine is idle it lasts a lot longer (the fan is more effective I guess....) Has anyone else seen this problem ? I'm pretty much convinced that it's a hardware problem now, so I'll probably return the machine (second time) nearer the end of the week. Cheers. > [.....] > > As for sending you my binary, I would like to test it myself before > > I start giving it out to people. > > I've built this driver into XF86_SVGA (albeit with all the other > drivers too - rather than just ``generic'') and I can get X up at 16 > bits in 800x600, *but* I get a lot of horizontal lines across my > screen - kind of like a huge thin horizontal smear (it's not there > when an empty xterm takes up the entire screen, but when I add some > text, I start getting the lines). > > I've tried changing the Frequency from 40.0 - to no avail. This has > obviously got nothing to do with it. > > I know very little about X - perhaps someone can say ``Ahh, those > horizontal lines are because....'' (and fill in the ....) ? > > FWIW, the text in the xterm is crystal clear at 16 bpp, but the > characters are like blobs of mud at 8 bpp. > > > -------------------- > > Randy Philipp > > cphilipp@pop500.gsfc.nasa.gov > > -- > Brian , , > > Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Aug 4 00:22:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11186 for freebsd-mobile-outgoing; Tue, 4 Aug 1998 00:22:22 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11178 for ; Tue, 4 Aug 1998 00:22:16 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA16313; Tue, 4 Aug 1998 16:51:24 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA01267; Tue, 4 Aug 1998 16:51:01 +0930 (CST) Message-ID: <19980804165101.Y25942@freebie.lemis.com> Date: Tue, 4 Aug 1998 16:51:01 +0930 From: Greg Lehey To: Brian Somers Cc: Randy Philipp , Doug White , freebsd-mobile@FreeBSD.ORG Subject: Re: Neomagic chipset - is it a hardware problem ? References: <199807252032.VAA00175@awfulhak.org> <199808040704.IAA25263@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808040704.IAA25263@awfulhak.org>; from Brian Somers on Tue, Aug 04, 1998 at 08:04:28AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (trimmed -ports) On Tuesday, 4 August 1998 at 8:04:28 +0100, Brian Somers wrote: >> [.....] >>> As for sending you my binary, I would like to test it myself before >>> I start giving it out to people. >> >> I've built this driver into XF86_SVGA (albeit with all the other >> drivers too - rather than just ``generic'') and I can get X up at 16 >> bits in 800x600, *but* I get a lot of horizontal lines across my >> screen - kind of like a huge thin horizontal smear (it's not there >> when an empty xterm takes up the entire screen, but when I add some >> text, I start getting the lines). >> >> I've tried changing the Frequency from 40.0 - to no avail. This has >> obviously got nothing to do with it. >> >> I know very little about X - perhaps someone can say ``Ahh, those >> horizontal lines are because....'' (and fill in the ....) ? >> >> FWIW, the text in the xterm is crystal clear at 16 bpp, but the >> characters are like blobs of mud at 8 bpp. > > I've found out more about this flickering problem.... it only occurs > when the laptop is physically warm - the warmer, the more flickering. > If the machine sleeps for ~15 minutes, it'll wake up with a perfect > picture and that picture will start to deteriorate with the building > heat. If I switch the display off for 15 minutes it makes no > difference. > > This is all under load. If the machine is idle it lasts a lot > longer (the fan is more effective I guess....) > > Has anyone else seen this problem ? I'm pretty much convinced that > it's a hardware problem now, so I'll probably return the machine > (second time) nearer the end of the week. I don't know too much about laptop displays, but if that were to happen on a glass monitor, I'd guess you're driving it out of spec. I know you can fry monitors; maybe you can fry laptop displays. In your position I'd seriously consider reviewing the display parameters. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Aug 4 07:28:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07231 for freebsd-mobile-outgoing; Tue, 4 Aug 1998 07:28:50 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles210.castles.com [208.214.165.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07115; Tue, 4 Aug 1998 07:28:26 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id HAA00456; Tue, 4 Aug 1998 07:24:16 -0700 (PDT) Message-Id: <199808041424.HAA00456@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brian Somers cc: Randy Philipp , Doug White , Greg Lehey , freebsd-mobile@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: Neomagic chipset - is it a hardware problem ? In-reply-to: Your message of "Tue, 04 Aug 1998 08:04:28 BST." <199808040704.IAA25263@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 07:24:15 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've found out more about this flickering problem.... it only occurs > when the laptop is physically warm - the warmer, the more flickering. > If the machine sleeps for ~15 minutes, it'll wake up with a perfect > picture and that picture will start to deteriorate with the building > heat. If I switch the display off for 15 minutes it makes no > difference. > > This is all under load. If the machine is idle it lasts a lot > longer (the fan is more effective I guess....) > > Has anyone else seen this problem ? I'm pretty much convinced that > it's a hardware problem now, so I'll probably return the machine > (second time) nearer the end of the week. I've seen similar symptoms on a Toshiba using the C&T 65555. The part would misbehave so badly that the X server would crash. Windows worked OK on it though; my hypothesis was just that the X driver wasn't doing whatever power management stuff the Windows driver was, and so the chip was overheating. I could be way off on that though; I know nothing about the C&T architecture. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Aug 4 10:03:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10906 for freebsd-mobile-outgoing; Tue, 4 Aug 1998 10:03:08 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA10885 for ; Tue, 4 Aug 1998 10:03:04 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 27215 invoked by uid 1001); 4 Aug 1998 17:02:46 +0000 (GMT) To: mike@smith.net.au Cc: freebsd-mobile@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: Neomagic chipset - is it a hardware problem ? In-Reply-To: Your message of "Tue, 04 Aug 1998 07:24:15 -0700" References: <199808041424.HAA00456@antipodes.cdrom.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 04 Aug 1998 19:02:46 +0200 Message-ID: <27213.902250166@verdi.nethelp.no> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Has anyone else seen this problem ? I'm pretty much convinced that > > it's a hardware problem now, so I'll probably return the machine > > (second time) nearer the end of the week. > > I've seen similar symptoms on a Toshiba using the C&T 65555. The part > would misbehave so badly that the X server would crash. > > Windows worked OK on it though; my hypothesis was just that the X > driver wasn't doing whatever power management stuff the Windows driver > was, and so the chip was overheating. I could be way off on that > though; I know nothing about the C&T architecture. I'm using an Acer Extensa 390 here, with a C&T 65555 graphics chip in 800x600 mode. It's working just fine for me - never had any problem with X. suspend/resume works too. In case anybody's interested, here's the -probeonly output and the config file I use. Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- (--) SVGA: PCI: C&T 65555 rev 198, Memory @ 0x04000000 (--) SVGA: Chipset: ct65555 (--) SVGA: CHIPS: no monitor detected. (**) SVGA: CHIPS: 2048 kB VRAM (--) SVGA: CHIPS: DD-STN probed. (--) SVGA: CHIPS: LCD (--) SVGA: CHIPS: Display Size: x=800; y=600 (--) SVGA: CHIPS: Frame Buffer used. (--) SVGA: CHIPS: Using embedded Frame Buffer. (--) SVGA: CHIPS: Frame Accelerator Enabled. (--) SVGA: CHIPS: PCI Bus (--) SVGA: CHIPS: base address is set at 0x4000000. (--) SVGA: CHIPS: Linear addressing is enabled at 0x4000000. (**) SVGA: CHIPS: 16 bpp. (--) SVGA: CHIPS: Internal DAC disabled. (--) SVGA: CHIPS: using programmable clocks. (--) SVGA: CHIPS: probed memory clock of 44999 KHz (--) SVGA: chipset: ct65555 (**) SVGA: videoram: 2048k (**) SVGA: Using 16 bpp, Depth 16, Color weight: 565 (--) SVGA: Maximum allowed dot-clock: 41.999 MHz (**) SVGA: Mode "800x600": mode clock = 28.320 (**) SVGA: Mode "800x600b": mode clock = 30.150 (**) SVGA: Mode "640x480": mode clock = 25.180 (**) SVGA: Mode "320x240": mode clock = 12.590 (--) SVGA: Virtual resolution set to 800x600 (--) SVGA: SpeedUp code selection modified because virtualX != 1024 (--) SVGA: CHIPS: 1002752 bytes off-screen memory available (--) SVGA: CHIPS: H/W cursor selected (--) SVGA: CHIPS: SpeedUps selected (Flags=0xF) (--) SVGA: CHIPS: Memory mapped I/O selected ---------------------------------------------------------------------- Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1" FontPath "/usr/X11R6/lib/X11/fonts/Speedo" FontPath "/usr/X11R6/lib/X11/fonts/misc" FontPath "/usr/X11R6/lib/X11/fonts/75dpi" FontPath "/usr/X11R6/lib/X11/fonts/100dpi" EndSection Section "ServerFlags" EndSection Section "Keyboard" Protocol "Standard" XkbRules "xfree86" XkbModel "pc101" XkbLayout "us" EndSection Section "Pointer" Protocol "PS/2" Device "/dev/mouse" EndSection Section "Monitor" Identifier "Primary Monitor" VendorName "Unknown" ModelName "Unknown" HorizSync 28-70 VertRefresh 45-80 Modeline "640x480" 25.18 640 664 760 800 480 491 493 525 Modeline "320x240" 12.59 320 336 384 400 240 245 246 262 doublescan Modeline "800x600" 28.32 800 808 848 936 600 600 604 628 Modeline "800x600b" 30.150 800 896 960 1056 600 600 604 628 EndSection Section "Device" Identifier "Primary Card" VendorName "Unknown" BoardName "Chips & Technologies CT65550" videoram 2048 EndSection Section "Screen" Driver "SVGA" Device "Primary Card" Monitor "Primary Monitor" DefaultColorDepth 8 SubSection "Display" Depth 8 Modes "800x600" "800x600b" "640x480" "320x240" EndSubSection SubSection "Display" Depth 15 Modes "800x600" "800x600b" "640x480" "320x240" EndSubSection SubSection "Display" Depth 16 Modes "800x600" "800x600b" "640x480" "320x240" EndSubSection SubSection "Display" Depth 24 Modes "640x480" "320x240" EndSubSection SubSection "Display" Depth 32 Modes "640x480" "320x240" EndSubSection EndSection To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Aug 4 16:11:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13204 for freebsd-mobile-outgoing; Tue, 4 Aug 1998 16:11:33 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13198 for ; Tue, 4 Aug 1998 16:11:28 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id XAA24500; Tue, 4 Aug 1998 23:12:12 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199808042212.XAA24500@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey cc: Brian Somers , Randy Philipp , Doug White , freebsd-mobile@FreeBSD.ORG Subject: Re: Neomagic chipset - is it a hardware problem ? In-reply-to: Your message of "Tue, 04 Aug 1998 16:51:01 +0930." <19980804165101.Y25942@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 23:12:12 +0100 From: Brian Somers Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [.....] > > Has anyone else seen this problem ? I'm pretty much convinced that > > it's a hardware problem now, so I'll probably return the machine > > (second time) nearer the end of the week. > > I don't know too much about laptop displays, but if that were to > happen on a glass monitor, I'd guess you're driving it out of spec. I > know you can fry monitors; maybe you can fry laptop displays. In your > position I'd seriously consider reviewing the display parameters. The display (frequency) parameters seem to be pretty much redundant for LCDs. I can make up any clock line, and pair it up with a modeline that says "800x600" anything 800 anything 600 anything and it'll behave exactly the same. This makes sense as there's no ``beam'' to give orders to on an LCD..... you just have to switch modes and colour the pixels - the rest is beyond software control. > Greg > -- > See complete headers for address and phone numbers > finger grog@lemis.com for PGP public key -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Aug 4 16:56:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20152 for freebsd-mobile-outgoing; Tue, 4 Aug 1998 16:56:09 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20066; Tue, 4 Aug 1998 16:56:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA00457; Tue, 4 Aug 1998 16:53:11 -0700 (PDT) Message-Id: <199808042353.QAA00457@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: sthaug@nethelp.no cc: mike@smith.net.au, freebsd-mobile@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: Neomagic chipset - is it a hardware problem ? In-reply-to: Your message of "Tue, 04 Aug 1998 19:02:46 +0200." <27213.902250166@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 16:53:11 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > Has anyone else seen this problem ? I'm pretty much convinced that > > > it's a hardware problem now, so I'll probably return the machine > > > (second time) nearer the end of the week. > > > > I've seen similar symptoms on a Toshiba using the C&T 65555. The part > > would misbehave so badly that the X server would crash. > > > > Windows worked OK on it though; my hypothesis was just that the X > > driver wasn't doing whatever power management stuff the Windows driver > > was, and so the chip was overheating. I could be way off on that > > though; I know nothing about the C&T architecture. > > I'm using an Acer Extensa 390 here, with a C&T 65555 graphics chip in > 800x600 mode. It's working just fine for me - never had any problem with > X. suspend/resume works too. Sorry, I didn't mean to imply that there was anything wrong with the Toshiba or C&T devices in general (especially since I have been bashing this 220CDS for about a year now), merely that I had seen similar symptoms on one such unit which was overheating. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Aug 4 17:13:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23204 for freebsd-mobile-outgoing; Tue, 4 Aug 1998 17:13:05 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23180 for ; Tue, 4 Aug 1998 17:12:49 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA00546; Tue, 4 Aug 1998 17:07:02 -0700 (PDT) Message-Id: <199808050007.RAA00546@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brian Somers cc: Greg Lehey , Randy Philipp , Doug White , freebsd-mobile@FreeBSD.ORG Subject: Re: Neomagic chipset - is it a hardware problem ? In-reply-to: Your message of "Tue, 04 Aug 1998 23:12:12 BST." <199808042212.XAA24500@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 17:07:02 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > [.....] > > > Has anyone else seen this problem ? I'm pretty much convinced that > > > it's a hardware problem now, so I'll probably return the machine > > > (second time) nearer the end of the week. > > > > I don't know too much about laptop displays, but if that were to > > happen on a glass monitor, I'd guess you're driving it out of spec. I > > know you can fry monitors; maybe you can fry laptop displays. In your > > position I'd seriously consider reviewing the display parameters. > > The display (frequency) parameters seem to be pretty much redundant > for LCDs. I can make up any clock line, and pair it up with a > modeline that says > > "800x600" anything 800 anything 600 anything > > and it'll behave exactly the same. This makes sense as there's no > ``beam'' to give orders to on an LCD..... you just have to switch > modes and colour the pixels - the rest is beyond software control. This is more likely actually due to the driver talking to the LCD and completely ignoring you. On older systems where it wasn't possible to quiz the panel for its parameters, it was possible to screw things up fairly impressively... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Aug 4 19:38:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19313 for freebsd-mobile-outgoing; Tue, 4 Aug 1998 19:38:17 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from crab.rutgers.edu (crab.rutgers.edu [165.230.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA19308 for ; Tue, 4 Aug 1998 19:38:14 -0700 (PDT) (envelope-from jaypeng@crab.rutgers.edu) Received: from crab.rutgers.edu (cmapt409b.rutgers.edu [165.230.171.20]) by crab.rutgers.edu (8.8.8/8.8.8) with ESMTP id WAA06173; Tue, 4 Aug 1998 22:38:01 -0400 (EDT) Message-ID: <35C7C57A.961BC90D@crab.rutgers.edu> Date: Tue, 04 Aug 1998 22:37:46 -0400 From: Jian Peng Organization: Rutgers Camden X-Mailer: Mozilla 4.05 [en] (Win95; U) MIME-Version: 1.0 To: freebsd-mobile@FreeBSD.ORG, Steve Sizemore Subject: ed0: device timeout 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, I have been trying to get a pcmcia ethernet card to work with FreeBSD 2.2.6-RELEASE for months, and I have no luck yet. Hopefully someone will help me out. My laptop is a Acer Extensa 392c with Texas Instrument PCI Cardbus 1250 Controller. The two cards I tried are DAYNA Communicard E and ACCTON EN2216-2. Both are NE2000 clone and on the PAO supporting list. I bought the ACCTON card 2 weeks ago. Mr. Sizemore succeeded in getting a ACCTON EN2216 (don't know -1 or -2) to work with a Acer Extensa 390 so I had lots of hope on this one. (about the difference: I think the 392c and 390 are quite the same; ACCTON EN2216-1 is a 10Base-T model, ACCTON EN2216-2 is a 10BaseT and 10Base2 Duo, autodetect under win95). What he did is installing PAO patch by default and it works immediately. I tried the same thing, either card was probed successfully. Name of the card and right physical address was displayed. Then when I brought the card up, I would always have a "ed0: device timeout" message. I even could not ping my gateway. There are someting I have tried: I tried to change the port, irq for pcic0 and ed0. First I tried to follow all the information given by win95, then I found it makes no difference. One interesting thing is: under win95, the controller is on irq 9 and ethercard is on irq 10. However under FreeBSD, the only way I got the card probed is assigning them the same irq. I tried irq 10 and irq 5 and I can not tell the difference. Though under win95 my build-in sound card uses the irq 5. So please help. If you need more information about my computer, please email me at jaypeng@crab.rutgers.edu. Thank you! Jay P.S This guy has a fabulous collection: http://www.tec.puv.fi/~s99137/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Aug 4 21:13:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04159 for freebsd-mobile-outgoing; Tue, 4 Aug 1998 21:13:28 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles118.castles.com [208.214.165.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04153 for ; Tue, 4 Aug 1998 21:13:20 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id VAA00385; Tue, 4 Aug 1998 21:12:15 -0700 (PDT) Message-Id: <199808050412.VAA00385@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jian Peng cc: freebsd-mobile@FreeBSD.ORG, Steve Sizemore Subject: Re: ed0: device timeout In-reply-to: Your message of "Tue, 04 Aug 1998 22:37:46 EDT." <35C7C57A.961BC90D@crab.rutgers.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 21:12:14 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hello all, > > I have been trying to get a pcmcia ethernet card to work with FreeBSD > 2.2.6-RELEASE for months, and I have no luck yet. Hopefully someone will > help me out. > My laptop is a Acer Extensa 392c with Texas Instrument PCI Cardbus 1250 > Controller. The two cards I tried are DAYNA Communicard E and ACCTON > EN2216-2. Both are NE2000 clone and on the PAO supporting list. I bought > the ACCTON card 2 weeks ago. Mr. Sizemore succeeded in getting a ACCTON > EN2216 (don't know -1 or -2) to work with a Acer Extensa 390 so I had > lots of hope on this one. (about the difference: I think the 392c and > 390 are quite the same; ACCTON EN2216-1 is a 10Base-T model, ACCTON > EN2216-2 is a 10BaseT and 10Base2 Duo, autodetect under win95). The 2216 autodetects in hardware. (I used to use one). > What he > did is installing PAO patch by default and it works immediately. PAO is not necessary for this. I generally ignore messages referring to PAO because I don't run it and thus can't help with it. > I tried the same thing, either card was probed successfully. Name of the > card and right physical address was displayed. Then when I brought the > card up, I would always have a "ed0: device timeout" message. I even > could not ping my gateway. Either you are not receiving interrupts, or your cabling is busted. > There are someting I have tried: > I tried to change the port, irq for pcic0 and ed0. First I tried to > follow all the information given by win95, then I found it makes no > difference. One interesting thing is: under win95, the controller is on > irq 9 and ethercard is on irq 10. However under FreeBSD, the only way I > got the card probed is assigning them the same irq. This may result in the card being probed, but it will never work like this. The card *must* have a different interrupt. > I tried irq 10 and > irq 5 and I can not tell the difference. Though under win95 my build-in > sound card uses the irq 5. This means that IRQ 5 is not available, and you can't use it for PCCARDs. > So please help. If you need more information about my computer, please > email me at jaypeng@crab.rutgers.edu. Simple: let the pcic take the interrupt it's given. Fill in the resource list in /etc/pccard.conf with the resources that are really free. Insert the card. That's all it takes to make the 2216 work. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Aug 5 00:06:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29098 for freebsd-mobile-outgoing; Wed, 5 Aug 1998 00:06:20 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28998 for ; Wed, 5 Aug 1998 00:06:02 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id IAA12582; Wed, 5 Aug 1998 08:02:34 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199808050702.IAA12582@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: Brian Somers , Randy Philipp , Doug White , Greg Lehey , freebsd-mobile@FreeBSD.ORG, "Jeroen van den Boom" Subject: Re: Neomagic chipset - is it a hardware problem ? In-reply-to: Your message of "Tue, 04 Aug 1998 07:24:15 PDT." <199808041424.HAA00456@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 08:02:33 +0100 From: Brian Somers Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Jeroen van den Boom from CTX cc'd - this may interest you!] [Greg cc'd - there's a question/request near the end... :-)] It looks like you're at least partially correct Mike. I've done some more tests with heating up, cooling down, restarting X, restarting FreeBSD, suspend & resume and LCD off & on.... It seems that the screen corruption is due to a combination of the X server initialisation (*not* doing something it should) and the heat of the machine. If I start X and let the machine heat up, or start X when the machine is already hot, I get the flickering. Once it's flickering, the display can be made crystal clear again by either suspending 'till the machine cools down (as I said before) or by simply switching the LCD off and on (there's a small switch for detecting when the lid is down that switches the LCD off by default and can be configured to make the laptop ``sleep''). If I ``sleep 'till cool'', the problem re-occurs as the machine heats up again. I can only guess that the sleep/resume is being caught by the power management stuff and X is re-initialising (wrongly) the display whereas the LCD off/on event is completely transparent and the laptop firmware knows how to make the screen work when hot..... once this `tweak' has happened, the display is fine forever more - up until it goes into text mode and back into graphics mode (ala X server). This is *very* peculiar, but I think it's now looking more like a software thing. I'll continue to test things.... I'm now running KDE 1.0 (window manager) and am using a screensaver - maybe this is relevant. I *do* wish NeoMagic would just publish the damn specs :-( The other ``weird'' thing is that nobody else seems to have reported this problem, although I guess there aren't that many that have gone to the trouble of manually merging the initialisation code, and even fewer (if any) that have a CTX Cybernote. Greg, as you've got a similar setup (although I doubt your machine is a CTX Cybernote), can you try doing a ``make world'' and see if you get similar behaviour, making sure that you *haven't* let the laptops LCD initialise itself (X should be the last thing to have set up the display from text mode) ? It would be much appreciated. Thanks everyone for your help. > > I've found out more about this flickering problem.... it only occurs > > when the laptop is physically warm - the warmer, the more flickering. > > If the machine sleeps for ~15 minutes, it'll wake up with a perfect > > picture and that picture will start to deteriorate with the building > > heat. If I switch the display off for 15 minutes it makes no > > difference. > > > > This is all under load. If the machine is idle it lasts a lot > > longer (the fan is more effective I guess....) > > > > Has anyone else seen this problem ? I'm pretty much convinced that > > it's a hardware problem now, so I'll probably return the machine > > (second time) nearer the end of the week. > > I've seen similar symptoms on a Toshiba using the C&T 65555. The part > would misbehave so badly that the X server would crash. > > Windows worked OK on it though; my hypothesis was just that the X > driver wasn't doing whatever power management stuff the Windows driver > was, and so the chip was overheating. I could be way off on that > though; I know nothing about the C&T architecture. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Aug 5 00:19:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01999 for freebsd-mobile-outgoing; Wed, 5 Aug 1998 00:19:23 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01969 for ; Wed, 5 Aug 1998 00:19:09 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA20401; Wed, 5 Aug 1998 16:48:11 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA06731; Wed, 5 Aug 1998 16:47:47 +0930 (CST) Message-ID: <19980805164747.I6348@freebie.lemis.com> Date: Wed, 5 Aug 1998 16:47:47 +0930 From: Greg Lehey To: Brian Somers , Mike Smith Cc: Randy Philipp , Doug White , freebsd-mobile@FreeBSD.ORG, Jeroen van den Boom Subject: Re: Neomagic chipset - is it a hardware problem ? References: <199808041424.HAA00456@antipodes.cdrom.com> <199808050702.IAA12582@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808050702.IAA12582@awfulhak.org>; from Brian Somers on Wed, Aug 05, 1998 at 08:02:33AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wednesday, 5 August 1998 at 8:02:33 +0100, Brian Somers wrote: > [Jeroen van den Boom from CTX cc'd - this may interest you!] > [Greg cc'd - there's a question/request near the end... :-)] >>> I've found out more about this flickering problem.... it only occurs >>> when the laptop is physically warm - the warmer, the more flickering. >>> If the machine sleeps for ~15 minutes, it'll wake up with a perfect >>> picture and that picture will start to deteriorate with the building >>> heat. If I switch the display off for 15 minutes it makes no >>> difference. >>> >>> This is all under load. If the machine is idle it lasts a lot >>> longer (the fan is more effective I guess....) >>> >>> Has anyone else seen this problem ? I'm pretty much convinced that >>> it's a hardware problem now, so I'll probably return the machine >>> (second time) nearer the end of the week. >> >> I've seen similar symptoms on a Toshiba using the C&T 65555. The part >> would misbehave so badly that the X server would crash. >> >> Windows worked OK on it though; my hypothesis was just that the X >> driver wasn't doing whatever power management stuff the Windows driver >> was, and so the chip was overheating. I could be way off on that >> though; I know nothing about the C&T architecture. > > It looks like you're at least partially correct Mike. I've done some > more tests with heating up, cooling down, restarting X, restarting > FreeBSD, suspend & resume and LCD off & on.... > > It seems that the screen corruption is due to a combination of the X > server initialisation (*not* doing something it should) and the heat > of the machine. If I start X and let the machine heat up, or start > X when the machine is already hot, I get the flickering. > > Once it's flickering, the display can be made crystal clear again by > either suspending 'till the machine cools down (as I said before) or > by simply switching the LCD off and on (there's a small switch for > detecting when the lid is down that switches the LCD off by default > and can be configured to make the laptop ``sleep''). If I ``sleep > 'till cool'', the problem re-occurs as the machine heats up again. OK. We've established that the problem relates to heat, at least in part to heat generated by the system/display. That doesn't happen with Microsoft, if I understand correctly. That makes it difficult to escape the conclusion that something in your setup is not working correctly. > I can only guess that the sleep/resume is being caught by the power > management stuff and X is re-initialising (wrongly) the display > whereas the LCD off/on event is completely transparent and the laptop > firmware knows how to make the screen work when hot..... once this > `tweak' has happened, the display is fine forever more - up until it > goes into text mode and back into graphics mode (ala X server). I'm not convinced that this is the problem. Presumably, under Microsoft you can run the thing for hours (or until the "system" crashes) without this problem occurring. > This is *very* peculiar, but I think it's now looking more like a > software thing. I'll continue to test things.... I'm now running > KDE 1.0 (window manager) and am using a screensaver - maybe this is > relevant. I *do* wish NeoMagic would just publish the damn specs :-( Well, I'd say it's an interaction between hardware and software. > The other ``weird'' thing is that nobody else seems to have reported > this problem, although I guess there aren't that many that have gone > to the trouble of manually merging the initialisation code, and even > fewer (if any) that have a CTX Cybernote. Greg, as you've got a > similar setup (although I doubt your machine is a CTX Cybernote), can > you try doing a ``make world'' and see if you get similar behaviour, > making sure that you *haven't* let the laptops LCD initialise itself > (X should be the last thing to have set up the display from text > mode) ? It would be much appreciated. Well, I don't have a NeoMagic chipset. I've just been passing this information around for people who do. I'll gladly do a make world (if this damn server would give me access), but I don't think it would do much. What I *do* think could be useful would be to extract the video registers under Microsoft and compare them to what gets written in there by X, if you have a Microsoft partition left on the laptop. If you don't have anything suitable, I can check what I have here. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Aug 5 04:02:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26438 for freebsd-mobile-outgoing; Wed, 5 Aug 1998 04:02:33 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA26408 for ; Wed, 5 Aug 1998 04:02:31 -0700 (PDT) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.8.8/8.8.8) id HAA09666; Wed, 5 Aug 1998 07:01:11 -0400 (EDT) (envelope-from larry) Message-ID: <19980805070111.C6263@marso.com> Date: Wed, 5 Aug 1998 07:01:11 -0400 From: "Larry S. Marso" To: Mike Smith , freebsd-mobile@FreeBSD.ORG Subject: Re: Neomagic chipset - is it a hardware problem ? References: <27213.902250166@verdi.nethelp.no> <199808042353.QAA00457@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199808042353.QAA00457@dingo.cdrom.com>; from Mike Smith on Tue, Aug 04, 1998 at 04:53:11PM -0700 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Aug 04, 1998 at 04:53:11PM -0700, Mike Smith wrote: > > Sorry, I didn't mean to imply that there was anything wrong with the > Toshiba or C&T devices in general (especially since I have been bashing > this 220CDS for about a year now), merely that I had seen similar > symptoms on one such unit which was overheating. I can vouch for problems with C&T devices relating to flickering. My Chembook 9750 has had this problem as long as I can remember. 1/2 or more of my X sessions start with some sort of flickering, and it usually gets worse with time (= heat). Interestingly, using the external video port and a monitor, I have absolutely no problem at all. Best regards -- Larry S. Marso larry@marso.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Aug 5 10:11:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19045 for freebsd-mobile-outgoing; Wed, 5 Aug 1998 10:11:43 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from cmpharm.ucsf.edu (cmpharm.ucsf.EDU [128.218.67.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19036 for ; Wed, 5 Aug 1998 10:11:38 -0700 (PDT) (envelope-from steve@cmpharm.ucsf.edu) Received: from piglet.ucsf.edu (piglet.ucsf.edu [128.218.67.20]) by cmpharm.ucsf.edu (8.9.0/8.9.0) with ESMTP id KAA22986; Wed, 5 Aug 1998 10:11:16 -0700 (PDT) Received: (from steve@localhost) by piglet.ucsf.edu (8.9.0/8.9.0) id KAA10410; Wed, 5 Aug 1998 10:11:05 -0700 (PDT) Message-ID: <19980805101105.A10064@cmpharm.ucsf.edu> Date: Wed, 5 Aug 1998 10:11:05 -0700 From: Steve Sizemore To: Mike Smith , Jian Peng Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: ed0: device timeout References: <35C7C57A.961BC90D@crab.rutgers.edu> <199808050412.VAA00385@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199808050412.VAA00385@antipodes.cdrom.com>; from Mike Smith on Tue, Aug 04, 1998 at 09:12:14PM -0700 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Aug 04, 1998 at 09:12:14PM -0700, Mike Smith wrote: > > I have been trying to get a pcmcia ethernet card to work with FreeBSD > > 2.2.6-RELEASE for months, and I have no luck yet. Hopefully someone will > > help me out. > > My laptop is a Acer Extensa 392c with Texas Instrument PCI Cardbus 1250 > > Controller. The two cards I tried are DAYNA Communicard E and ACCTON > > EN2216-2. Both are NE2000 clone and on the PAO supporting list. I bought > > the ACCTON card 2 weeks ago. Mr. Sizemore succeeded in getting a ACCTON > > EN2216 (don't know -1 or -2) to work with a Acer Extensa 390 so I had > > lots of hope on this one. (about the difference: I think the 392c and > > 390 are quite the same; ACCTON EN2216-1 is a 10Base-T model, ACCTON > > EN2216-2 is a 10BaseT and 10Base2 Duo, autodetect under win95). > > The 2216 autodetects in hardware. (I used to use one). I also have the "Duo" model, and I'm using it with 10BaseT. > > What he > > did is installing PAO patch by default and it works immediately. Using the PAO kernel for 2.2.6, I was able to use the Accton 2216 successfully "out of the box" and the 3Com 3C589D by tweaking the irq in the kernel config file to 11, rather than the default 10. (Ken Key's suggestion.) > PAO is not necessary for this. I generally ignore messages referring > to PAO because I don't run it and thus can't help with it. Repeated statements like this one led me to abandon PAO and go with the standard 2.2-stable package. Having a working ethernet connection, thanks to the PAO kernel, I was able to cvsup the stable sources, and make the world. Unfortunately, since that time, I have been unable to build a kernel that works correctly with either of those two ethernet PC cards on my Extensa 390. > > I tried the same thing, either card was probed successfully. Name of the > > card and right physical address was displayed. Then when I brought the > > card up, I would always have a "ed0: device timeout" message. I even > > could not ping my gateway. My current experience with the Accton card is exactly the same as Jay's - the ifconfig works successfully, but the ed0 times out, and no traffic gets passed through it. The 3cd89d behaves slightly better - ep0 gets properly ifconfig'ed and some traffic passes, but with losses and latencies too high to be usable. Interestingly, this was the same problem I originally had with the 3c589d and the PAO kernel, which led me to purchase the Accton. > Either you are not receiving interrupts, or your cabling is busted. Cabling is not busted, since both Jay and I get the same results, and the identical cabling works with Windows 95. I'm convinced (already) that the problem is irq or iomem. > > There are someting I have tried: > > I tried to change the port, irq for pcic0 and ed0. First I tried to > > follow all the information given by win95, then I found it makes no > > difference. One interesting thing is: under win95, the controller is on > > irq 9 and ethercard is on irq 10. However under FreeBSD, the only way I > > got the card probed is assigning them the same irq. > > This may result in the card being probed, but it will never work like > this. The card *must* have a different interrupt. Can we ignore the win irq's and look only at what freebsd reports? e.g. there is presumably a modem on irq 11 which is not seen by freebsd. Can I use irq 11? (I did so successfully under the PAO kernel.) The Accton card can use irq 2(9), 3, 4, 5, 10, 11, 12, 15. dmesg reports that irqs 1, 3, 4, 5, 6, 7, 9, 12, 14, and 15 are detected at boot. I'm assuming that I can use 10 and 11 for ethernet, even though the internal modem is supposed to be at 11. I have seen no functional difference between 10 and 11. > > I tried irq 10 and > > irq 5 and I can not tell the difference. Though under win95 my build-in > > sound card uses the irq 5. This is one difference between my Extensa and Jay's - mine doesn't have a sound card, and the PC controller (pcic) gets irq 5. > > This means that IRQ 5 is not available, and you can't use it for > PCCARDs. Even if bsd doesn't detect the sound card? > > So please help. If you need more information about my computer, please > > email me at jaypeng@crab.rutgers.edu. > > Simple: let the pcic take the interrupt it's given. Fill in the > resource list in /etc/pccard.conf with the resources that are really > free. Insert the card. > > That's all it takes to make the 2216 work. If that's all there was to make it work, mine would have been working quite a while ago. It seems to me that there are two possibilities remaining that could explain the differences in our experiences. First, are you really talking about the situation in the release, or stable branch of freebsd, and not current? (Jay is using 2.2.6-release, and I'm using stable.) Assuming that we're talking about the same code, then there must be some hardware differences in the Extensa machines which make them behave differently than your expectations (and mine). I've seen some anomalies with the PC card controller which make me wonder if that might be at the root of the problem. I won't detail them here, as this is already a pretty long message, but I'll be happy to do so if anyone thinks it might shed some light on this problem. > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > Everything other than PC card stuff, is working fine under the 2.2-stable system, but at this point, I'm seriously considering going back to the PAO package, just to get an ethernet connection. Since I'd have to wipe out everything (I think) to do that, I'd also consider reinstalling stable or current, if you think that has a reasonable probability of fixing the problem. I'd also consider OpenBSD. (If all else fails, I might even be forced to consider linux.) Thanks for listening, if anyone has actually read this far. ;-) Steve ----------------------------------------------#-----#--#####--------------- # # # # Steve Sizemore # # # Dept. of Cellular and Molecular Pharmacology # # # Box 0450, Room HSE-1285 # # # University of California Medical Center # # # # 513 Parnassus Avenue ##### ##### ##### ####### San Francisco CA 94143-0450 # # # # # steve@cmpharm.ucsf.edu ##### ##### (415) 476-6987 FAX: (415) 476-6515 # # # # # -------------------------------------------------------------#####--#------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Aug 5 12:44:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13139 for freebsd-mobile-outgoing; Wed, 5 Aug 1998 12:44:04 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13061 for ; Wed, 5 Aug 1998 12:43:54 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id UAA04919; Wed, 5 Aug 1998 20:15:59 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199808051915.UAA04919@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey cc: Brian Somers , Mike Smith , Randy Philipp , Doug White , freebsd-mobile@FreeBSD.ORG, Jeroen van den Boom Subject: Re: Neomagic chipset - is it a hardware problem ? In-reply-to: Your message of "Wed, 05 Aug 1998 16:47:47 +0930." <19980805164747.I6348@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 20:15:58 +0100 From: Brian Somers Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [.....] > > I can only guess that the sleep/resume is being caught by the power > > management stuff and X is re-initialising (wrongly) the display > > whereas the LCD off/on event is completely transparent and the laptop > > firmware knows how to make the screen work when hot..... once this > > `tweak' has happened, the display is fine forever more - up until it > > goes into text mode and back into graphics mode (ala X server). > > I'm not convinced that this is the problem. Presumably, under > Microsoft you can run the thing for hours (or until the "system" > crashes) without this problem occurring. I've no idea. I installed FreeBSD on the laptop as soon as I got it, but I would think that this is the case - ruling out a hardware problem (which I think I can, as I can make it work by turning the LCD off then on), we must assume that as NeoMagic themselves wrote (or contracted the writing of) the Windows driver, they know how to do what that little switch does. [.....] > Well, I don't have a NeoMagic chipset. I've just been passing this > information around for people who do. I'll gladly do a make world (if > this damn server would give me access), but I don't think it would do > much. No - I was only interested in finding out if the graphics chipset is over-heat-able on other machines given the same software setup. > What I *do* think could be useful would be to extract the video > registers under Microsoft and compare them to what gets written in > there by X, if you have a Microsoft partition left on the laptop. If > you don't have anything suitable, I can check what I have here. I can probably find a 2.5" disk with windows on it, but I would have thought that even Windows 95/98 would GPF a program that tried to read the graphics card registers - even if it didn't, I'm pretty sure that there are probably some read-only registers (I'm talking from UART experience - I know nothing about graphics cards) that would invalidate the exercise. I'm quite happy to live with the limitation of closing and opening the lid after starting X (this makes everything work) - I'd just like to hear if anyone else with a NeoMagic can reproduce the problem - or even better, if someone with a CTX Cybernote running X 3.2.2 (the 3rd patch is just some security stuff - not relevant here) on FreeBSD-current could try to reproduce the problem. When (if?) NeoMagic release the specs, I'm sure everything will become clear :-) > Greg > -- > See complete headers for address and phone numbers > finger grog@lemis.com for PGP public key Thanks for your input. -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Aug 5 16:03:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10615 for freebsd-mobile-outgoing; Wed, 5 Aug 1998 16:03:35 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10605 for ; Wed, 5 Aug 1998 16:03:23 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id QAA25483 for ; Wed, 5 Aug 1998 16:03:08 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 5 Aug 1998 16:03:07 -0700 (PDT) From: Doug White To: mobile@FreeBSD.ORG Subject: pccard_ether doesn't run dhcp properly(?) 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 Hello ... I'm having trouble getting DHCP to work properly on a 2.2.7 box through the PCCARD system. I've change pccard_ether to DHCP and dhclient runs, but for some reason the default route is not added properly. I've added tons of debugging to /etc/dhclient-script and it appears to add the default route but the route itself never appears. All the references are by IP so I don't believe it's a nameserver lookup problem. Is anyone working on this or knows anything about what's going on? It think there may be a race condition but dhclient-script is a tangled mess and I don't have the time at current to hack up a shorter substitute. I can replicate it on my Digital as well as a Dell, and adding the default route manually appears to get everything going. Running 'route monitor' in another window while putting the ethernet card in is interesting. I get *tons* of RTM_FAILs trying to reach the DHCP host (which is the same as our nameserver so it's hard to discern what it's trying to talk to). I can collect more data if anyone can help me out with this. Thanks much for any assistance ... Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Aug 6 19:36:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06331 for freebsd-mobile-outgoing; Thu, 6 Aug 1998 19:36:12 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06301 for ; Thu, 6 Aug 1998 19:36:07 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id TAA28558; Thu, 6 Aug 1998 19:35:49 -0700 (PDT) Date: Thu, 6 Aug 1998 19:35:49 -0700 (PDT) From: Chris Timmons To: Doug White cc: mobile@FreeBSD.ORG Subject: Re: pccard_ether doesn't run dhcp properly(?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hmmm... Are you using the isc dhcp2 from the ports collection? I am running that without any trouble on 2.2.6R+PAO (which granted is not what you asked.) -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Aug 7 12:55:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07806 for freebsd-mobile-outgoing; Fri, 7 Aug 1998 12:55:12 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07793 for ; Fri, 7 Aug 1998 12:55:08 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id MAA02869; Fri, 7 Aug 1998 12:54:03 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 7 Aug 1998 12:54:02 -0700 (PDT) From: Doug White To: Chris Timmons cc: mobile@FreeBSD.ORG Subject: Re: pccard_ether doesn't run dhcp properly(?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 6 Aug 1998, Chris Timmons wrote: > > Hmmm... Are you using the isc dhcp2 from the ports collection? > > I am running that without any trouble on 2.2.6R+PAO (which granted is not > what you asked.) Yup, latest one. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Aug 8 09:26:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28489 for freebsd-mobile-outgoing; Sat, 8 Aug 1998 09:26:53 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28474; Sat, 8 Aug 1998 09:26:50 -0700 (PDT) (envelope-from jrs@mcs.net) Received: from laptop (P28-Chi-Dial-1.pool.mcs.net [205.253.224.28]) by Kitten.mcs.com (8.8.7/8.8.2) with SMTP id LAA28878; Sat, 8 Aug 1998 11:26:32 -0500 (CDT) Message-ID: <014701bdc2e1$52894580$648cfea9@laptop> From: "john" To: , Subject: Laptop install-PCCARD--xwindows--MOUSE Date: Sat, 8 Aug 1998 11:29:22 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've installed freebsd 2.2.6 on my IBM 380ED laptop. I am having 3 problems. 1. Has anyone been able to use the built in mouse on they're laptop?? If so can you tell me how. 2. I have a 3com 10/100 LAN+56K card (Model Number 3ccfem556). I can't get this card working. Can someone help me to get the card working. I've enable PCCARD and have installed a device. still no luck. Even if I could only use the Network interface of the card it would be great. 3. I can get xwindows running (no mouse and not full screen) however I would be interested in any ones xwindows config file that is running on a laptop so I can enhance mine. Thanks in advance, JOHN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Aug 8 10:14:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02911 for freebsd-mobile-outgoing; Sat, 8 Aug 1998 10:14:19 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from eecis.udel.edu (ren.eecis.udel.edu [128.175.7.13]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA02906 for ; Sat, 8 Aug 1998 10:14:17 -0700 (PDT) (envelope-from <@eecis.udel.edu:alexandr@ren.eecis.udel.edu>) Date: Sat, 8 Aug 1998 10:14:17 -0700 (PDT) From: "<"<@eecis.udel.edu:alexandr@ren.eecis.udel.edu> Message-Id: <199808081714.KAA02906@hub.freebsd.org> Received: from localhost by eecis.udel.edu id aa10335; 8 Aug 1998 13:12 EDT To: john MMDF-Warning: Unable to confirm address in preceding line at eecis.udel.edu Cc: freebsd-mobile@FreeBSD.ORG Subject: RE: Laptop install-PCCARD--xwindows--MOUSE Organization: Mos Eisley Candy Store Reply-To: alexandr@louie.udel.edu Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In Reply to Your Message of Sat, 08 Aug 1998 11: 29:22 EDT Date: Sat, 08 Aug 1998 13:12:20 -0400 From: Jerry Alexandratos Message-ID: <199808081312.aa10335@eecis.udel.edu> john says: : 1. Has anyone been able to use the built in mouse on they're laptop?? If You'll have to compile a kernel with psm0 enabled for PS/2 mouse support. : 2. I have a 3com 10/100 LAN+56K card (Model Number 3ccfem556). I can't get This card isn't supported. 8( : 3. I can get xwindows running (no mouse and not full screen) however I : would be interested in any ones xwindows config file that is running on a : laptop so I can enhance mine. This is going to be real tricky. The 380's use the NeoMagic chipset which isn't supported by XFree86. There are two options. The first is to go with a commercial X-server like Xig. The second is to look at some experimental work that some people are working on. The URL is: http://www.mnsinc.com/js/Neomagic.html Good luck. --Jerry 8) Jerry Alexandratos % - % "Nothing inhabits my (8 8) alexandr@louie.udel.edu % - % thoughts, and oblivion (8 8) darkstar@strauss.udel.edu % - % drives my desires." (8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message