From owner-freebsd-mobile@FreeBSD.ORG Sun Dec 7 20:51:45 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AC4E16A4CE for ; Sun, 7 Dec 2003 20:51:45 -0800 (PST) Received: from mail-aubervilliers.netaktiv.com (soyouz.netaktiv.com [80.67.170.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD96A43F75 for ; Sun, 7 Dec 2003 20:51:38 -0800 (PST) (envelope-from stephane@fetiche.sources.org) Received: by mail-aubervilliers.netaktiv.com (Postfix, from userid 10) id 99AAF23CCB; Mon, 8 Dec 2003 05:51:37 +0100 (CET) Received: by fetiche.sources.org (Postfix, from userid 1001) id 2FD289AD0; Sun, 7 Dec 2003 21:01:28 +0430 (AFT) Date: Sun, 7 Dec 2003 21:01:27 +0430 From: Stephane Bortzmeyer To: freebsd-mobile@freebsd.org Message-ID: <20031207163127.GA791@fetiche.sources.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Transport: UUCP rules X-Operating-System: FreeBSD 5.1-RELEASE i386 Subject: X freezes my Sony Vaio PCG-F801 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 04:51:45 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On a Sony Vaio PCG-F801, I installed FreeBSD 5.1-RELEASE, which comes with Xfree 4.3.0. When I work in console mode, the machine is OK. I can spend hours editing texts with Emacs without problems. When I use X, edition with Emacs makes the machine freezes after ten or twenty minutes of use. The cursor no longer moves, Crtl-Alt-F1 and Ctrl-Alt-Backspace are ignored. I have to reboot the hard way. It seems that the problem only occurs with Emacs. If I spend my time surfing with Mozilla, I do not have the problem, may be because I do not type. I attached the XFree86 log, hoping it is not too large. --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="XFree86.0.log" XFree86 Version 4.3.0 Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: FreeBSD 5.1 i386 [ELF] Build Date: 24 May 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Sun Dec 7 19:42:15 2003 (==) Using config file: "/etc/X11/XF86Config" (==) ServerLayout "Layout0" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Keyboard0" (**) Option "XkbModel" "pc102" (**) XKB: model: "pc102" (**) Option "XkbLayout" "fr" (**) XKB: layout: "fr" (==) Keyboard: CustomKeycode disabled (**) |-->Input Device "Mouse0" (WW) `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/100dpi/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/100dpi/"). (==) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/" (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on freebsd (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x00000000, mode1Res1 = 0x80000000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0501 card 0000,0000 rev 04 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8501 card 0000,0000 rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,0686 card 1106,0000 rev 22 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1106,0571 card 0000,0000 rev 10 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 10 class 0c,03,00 hdr 00 (II) PCI: 00:07:4: chip 1106,3057 card 0000,0000 rev 30 class 06,01,00 hdr 00 (II) PCI: 00:0a:0: chip 104c,ac51 card fffc,ffff rev 00 class 06,07,00 hdr 82 (II) PCI: 00:0a:1: chip 104c,ac51 card fffc,ffff rev 00 class 06,07,00 hdr 82 (II) PCI: 00:0d:0: chip 125d,1998 card 104d,80a6 rev 00 class 04,01,00 hdr 80 (II) PCI: 00:0d:1: chip 125d,1999 card 104d,80a6 rev 00 class 07,80,00 hdr 80 (II) PCI: 00:0e:0: chip 104c,8020 card 104d,80ac rev 00 class 0c,00,10 hdr 00 (II) PCI: 01:00:0: chip 1023,8420 card 104d,80ab rev 5d class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set) (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xfb100000 - 0xfc7fffff (0x1700000) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:7:4), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(1:0:0) Trident Microsystems CyberBlade/i7d rev 93, Mem @ 0xfc000000/23, 0xfb100000/17, 0xfb800000/23 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) PCI Memory resource overlap reduced 0xe0000000 from 0xffffffff to 0xdfffffff (II) PCI Memory resource overlap reduced 0xfb000000 from 0xfbffffff to 0xfb0fffff (II) Active PCI resource ranges: [0] -1 0 0xfb000000 - 0xfb0fffff (0x100000) MX[B]E [1] -1 0 0xfb006000 - 0xfb007fff (0x2000) MX[B]E [2] -1 0 0xfb004000 - 0xfb007fff (0x4000) MX[B]E [3] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]EO [4] -1 0 0xfb800000 - 0xfbffffff (0x800000) MX[B](B) [5] -1 0 0xfb100000 - 0xfb11ffff (0x20000) MX[B](B) [6] -1 0 0xfc000000 - 0xfc7fffff (0x800000) MX[B](B) [7] -1 0 0x00001400 - 0x000014ff (0x100) IX[B]E [8] -1 0 0x00001000 - 0x000010ff (0x100) IX[B]E [9] -1 0 0x00001800 - 0x000018ff (0x100) IX[B]E [10] -1 0 0x00001840 - 0x0000187f (0x40) IX[B]E (II) PCI Memory resource overlap reduced 0xfb000000 from 0xfb0fffff to 0xfb003fff (II) PCI Memory resource overlap reduced 0xfb004000 from 0xfb007fff to 0xfb005fff (II) PCI I/O resource overlap reduced 0x00001800 from 0x000018ff to 0x0000183f (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xfb000000 - 0xfb003fff (0x4000) MX[B]E [1] -1 0 0xfb006000 - 0xfb007fff (0x2000) MX[B]E [2] -1 0 0xfb004000 - 0xfb005fff (0x2000) MX[B]E [3] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]EO [4] -1 0 0xfb800000 - 0xfbffffff (0x800000) MX[B](B) [5] -1 0 0xfb100000 - 0xfb11ffff (0x20000) MX[B](B) [6] -1 0 0xfc000000 - 0xfc7fffff (0x800000) MX[B](B) [7] -1 0 0x00001400 - 0x000014ff (0x100) IX[B]E [8] -1 0 0x00001000 - 0x000010ff (0x100) IX[B]E [9] -1 0 0x00001800 - 0x0000183f (0x40) IX[B]E [10] -1 0 0x00001840 - 0x0000187f (0x40) IX[B]E (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xfb000000 - 0xfb003fff (0x4000) MX[B]E [6] -1 0 0xfb006000 - 0xfb007fff (0x2000) MX[B]E [7] -1 0 0xfb004000 - 0xfb005fff (0x2000) MX[B]E [8] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]EO [9] -1 0 0xfb800000 - 0xfbffffff (0x800000) MX[B](B) [10] -1 0 0xfb100000 - 0xfb11ffff (0x20000) MX[B](B) [11] -1 0 0xfc000000 - 0xfc7fffff (0x800000) MX[B](B) [12] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [13] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [14] -1 0 0x00001400 - 0x000014ff (0x100) IX[B]E [15] -1 0 0x00001000 - 0x000010ff (0x100) IX[B]E [16] -1 0 0x00001800 - 0x0000183f (0x40) IX[B]E [17] -1 0 0x00001840 - 0x0000187f (0x40) IX[B]E (II) LoadModule: "extmod" (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a (II) Module extmod: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.2 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension FontCache (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "glx" (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a (II) Module glx: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Server Extension, version 0.2 (II) Loading sub module "GLcore" (II) LoadModule: "GLcore" (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a (II) Module GLcore: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Server Extension, version 0.2 (II) Loading extension GLX (II) LoadModule: "dri" (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a (II) Module dri: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Server Extension, version 0.2 (II) Loading sub module "drm" (II) LoadModule: "drm" (II) Loading /usr/X11R6/lib/modules/freebsd/libdrm.a (II) Module drm: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Server Extension, version 0.2 (II) Loading extension XFree86-DRI (II) LoadModule: "dbe" (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a (II) Module dbe: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.2 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "record" (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.13.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.2 (II) Loading extension RECORD (II) LoadModule: "xtrap" (II) Loading /usr/X11R6/lib/modules/extensions/libxtrap.a (II) Module xtrap: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.2 (II) Loading extension DEC-XTRAP (II) LoadModule: "type1" (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a (II) Module type1: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.2 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Type1 (II) Loading font CID (II) LoadModule: "speedo" (II) Loading /usr/X11R6/lib/modules/fonts/libspeedo.a (II) Module speedo: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.1 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Speedo (II) LoadModule: "trident" (II) Loading /usr/X11R6/lib/modules/drivers/trident_drv.o (II) Module trident: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.6 (II) LoadModule: "mouse" (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 XInput Driver ABI class: XFree86 XInput driver, version 0.4 (II) TRIDENT: driver for Trident chipsets: tvga9000, tvga9000i, tvga8900c, tvga8900d, tvga9200cxr, tgui9400cxi, cyber9320, cyber9388, cyber9397, cyber9397dvd, cyber9520, cyber9525dvd, cyberblade/e4, tgui9420dgi, tgui9440agi, tgui9660, tgui9680, providia9682, providia9685, cyber9382, cyber9385, 3dimage975, 3dimage985, blade3d, cyberbladei7, cyberbladei7d, cyberbladei1, cyberbladei1d, cyberbladeAi1, cyberbladeAi1d, bladeXP, cyberbladeXPAi1 (II) Primary Device is: PCI 01:00:0 (--) Assigning device section with no busID to primary device (--) Chipset cyberbladei7d found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xfb000000 - 0xfb003fff (0x4000) MX[B]E [6] -1 0 0xfb006000 - 0xfb007fff (0x2000) MX[B]E [7] -1 0 0xfb004000 - 0xfb005fff (0x2000) MX[B]E [8] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]EO [9] -1 0 0xfb800000 - 0xfbffffff (0x800000) MX[B](B) [10] -1 0 0xfb100000 - 0xfb11ffff (0x20000) MX[B](B) [11] -1 0 0xfc000000 - 0xfc7fffff (0x800000) MX[B](B) [12] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [13] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [14] -1 0 0x00001400 - 0x000014ff (0x100) IX[B]E [15] -1 0 0x00001000 - 0x000010ff (0x100) IX[B]E [16] -1 0 0x00001800 - 0x0000183f (0x40) IX[B]E [17] -1 0 0x00001840 - 0x0000187f (0x40) IX[B]E (II) resource ranges after probing: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xfb000000 - 0xfb003fff (0x4000) MX[B]E [6] -1 0 0xfb006000 - 0xfb007fff (0x2000) MX[B]E [7] -1 0 0xfb004000 - 0xfb005fff (0x2000) MX[B]E [8] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]EO [9] -1 0 0xfb800000 - 0xfbffffff (0x800000) MX[B](B) [10] -1 0 0xfb100000 - 0xfb11ffff (0x20000) MX[B](B) [11] -1 0 0xfc000000 - 0xfc7fffff (0x800000) MX[B](B) [12] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [13] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [14] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [17] -1 0 0x00001400 - 0x000014ff (0x100) IX[B]E [18] -1 0 0x00001000 - 0x000010ff (0x100) IX[B]E [19] -1 0 0x00001800 - 0x0000183f (0x40) IX[B]E [20] -1 0 0x00001840 - 0x0000187f (0x40) IX[B]E [21] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [22] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (**) TRIDENT(0): Depth 24, (--) framebuffer bpp 32 (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/X11R6/lib/modules/libvgahw.a (II) Module vgahw: vendor="The XFree86 Project" compiled for 4.3.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.6 (II) TRIDENT(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Loading /usr/X11R6/lib/modules/libramdac.a (II) Module ramdac: vendor="The XFree86 Project" compiled for 4.3.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.6 (==) TRIDENT(0): RGB weight 888 (==) TRIDENT(0): Default visual is TrueColor (==) TRIDENT(0): Using gamma correction (1.0, 1.0, 1.0) (==) TRIDENT(0): Linear framebuffer at 0xFC000000 (--) TRIDENT(0): IO registers at 0xFB100000 (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/X11R6/lib/modules/libvbe.a (II) Module vbe: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.1.0 ABI class: XFree86 Video Driver, version 0.6 (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/X11R6/lib/modules/libint10.a (II) Module int10: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) TRIDENT(0): initializing int10 (==) TRIDENT(0): Write-combining range (0xa0000,0x20000) was already clear (==) TRIDENT(0): Write-combining range (0xc0000,0x40000) was already clear (II) TRIDENT(0): Primary V_BIOS segment is: 0xc000 (==) TRIDENT(0): Write-combining range (0x0,0x1000) was already clear (II) TRIDENT(0): VESA BIOS detected (II) TRIDENT(0): VESA VBE Version 1.2 (II) TRIDENT(0): VESA VBE Total Mem: 4096 kB (II) TRIDENT(0): VESA VBE OEM: Copyright 1998 TRIDENT MICROSYSTEMS INC. (==) TRIDENT(0): Write-combining range (0x0,0x1000) was already clear (==) TRIDENT(0): Write-combining range (0xfb100000,0x20000) was already clear (--) TRIDENT(0): Revision is 93 (--) TRIDENT(0): Found CyberBlade/DSTN/i7 chip (--) TRIDENT(0): RAM type is SDRAM (--) TRIDENT(0): Using SW cursor (--) TRIDENT(0): VideoRAM: 4096 kByte (--) TRIDENT(0): TFT Panel 800x600 found (--) TRIDENT(0): Memory Clock is 57.27 MHz (==) TRIDENT(0): Min pixel clock is 12 MHz (--) TRIDENT(0): Max pixel clock is 115 MHz (II) TRIDENT(0): Monitor0: Using hsync range of 31.50-57.00 kHz (II) TRIDENT(0): Monitor0: Using vrefresh range of 50.00-70.00 Hz (II) TRIDENT(0): Clock range: 12.00 to 115.00 MHz (II) TRIDENT(0): Not using default mode "640x350" (vrefresh out of range) (II) TRIDENT(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "640x400" (vrefresh out of range) (II) TRIDENT(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "720x400" (vrefresh out of range) (II) TRIDENT(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "640x480" (vrefresh out of range) (II) TRIDENT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "640x480" (vrefresh out of range) (II) TRIDENT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "640x480" (vrefresh out of range) (II) TRIDENT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "800x600" (vrefresh out of range) (II) TRIDENT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "800x600" (vrefresh out of range) (II) TRIDENT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "800x600" (vrefresh out of range) (II) TRIDENT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Removing mode (1024x768) larger than the LCD panel (800x600) (II) TRIDENT(0): Not using default mode "1024x768" (unknown reason) (II) TRIDENT(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Removing mode (1024x768) larger than the LCD panel (800x600) (II) TRIDENT(0): Not using default mode "1024x768" (unknown reason) (II) TRIDENT(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Removing mode (1024x768) larger than the LCD panel (800x600) (II) TRIDENT(0): Not using default mode "1024x768" (unknown reason) (II) TRIDENT(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Removing mode (1024x768) larger than the LCD panel (800x600) (II) TRIDENT(0): Not using default mode "1024x768" (unknown reason) (II) TRIDENT(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Removing mode (1024x768) larger than the LCD panel (800x600) (II) TRIDENT(0): Not using default mode "1024x768" (unknown reason) (II) TRIDENT(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Removing mode (1152x864) larger than the LCD panel (800x600) (II) TRIDENT(0): Not using default mode "1152x864" (unknown reason) (II) TRIDENT(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1280x960" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1280x960" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1280x1024" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1280x1024" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1280x1024" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1792x1344" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1792x1344" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1856x1392" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1856x1392" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1920x1440" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1920x1440" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Removing mode (832x624) larger than the LCD panel (800x600) (II) TRIDENT(0): Not using default mode "832x624" (unknown reason) (II) TRIDENT(0): Not using default mode "416x312" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Removing mode (1152x768) larger than the LCD panel (800x600) (II) TRIDENT(0): Not using default mode "1152x768" (unknown reason) (II) TRIDENT(0): Not using default mode "576x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1400x1050" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1400x1050" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1024" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "800x512" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1920x1440" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "2048x1536" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "2048x1536" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "2048x1536" (insufficient memory for mode) (II) TRIDENT(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using mode "1268x1024" (no mode of this name) (II) TRIDENT(0): Not using mode "1024x768" (no mode of this name) (--) TRIDENT(0): Virtual size is 800x600 (pitch 800) (**) TRIDENT(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz (II) TRIDENT(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (**) TRIDENT(0): Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz (II) TRIDENT(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (**) TRIDENT(0): Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz (II) TRIDENT(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (==) TRIDENT(0): DPI set to (75, 75) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/X11R6/lib/modules/libfb.a (II) Module fb: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 ANSI C Emulation, version 0.2 (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Loading /usr/X11R6/lib/modules/libi2c.a (II) Module i2c: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.2.0 ABI class: XFree86 Video Driver, version 0.6 (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/X11R6/lib/modules/libxaa.a (II) Module xaa: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.1.0 ABI class: XFree86 Video Driver, version 0.6 (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Loading /usr/X11R6/lib/modules/libddc.a (II) Module ddc: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (--) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] 0 0 0xfb800000 - 0xfbffffff (0x800000) MX[B] [1] 0 0 0xfb100000 - 0xfb11ffff (0x20000) MX[B] [2] 0 0 0xfc000000 - 0xfc7fffff (0x800000) MX[B] [3] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [4] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [8] -1 0 0xfb000000 - 0xfb003fff (0x4000) MX[B]E [9] -1 0 0xfb006000 - 0xfb007fff (0x2000) MX[B]E [10] -1 0 0xfb004000 - 0xfb005fff (0x2000) MX[B]E [11] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]EO [12] -1 0 0xfb800000 - 0xfbffffff (0x800000) MX[B](B) [13] -1 0 0xfb100000 - 0xfb11ffff (0x20000) MX[B](B) [14] -1 0 0xfc000000 - 0xfc7fffff (0x800000) MX[B](B) [15] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprU) [16] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprU) [17] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprU) [18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [19] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [20] -1 0 0x00001400 - 0x000014ff (0x100) IX[B]E [21] -1 0 0x00001000 - 0x000010ff (0x100) IX[B]E [22] -1 0 0x00001800 - 0x0000183f (0x40) IX[B]E [23] -1 0 0x00001840 - 0x0000187f (0x40) IX[B]E [24] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [25] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) (==) TRIDENT(0): Write-combining range (0xa0000,0x10000) was already clear (==) TRIDENT(0): Write-combining range (0xfb100000,0x20000) was already clear (==) TRIDENT(0): Write-combining range (0xfc000000,0x400000) (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/X11R6/lib/modules/libint10.a (II) TRIDENT(0): Initializing int10 (==) TRIDENT(0): Write-combining range (0xa0000,0x20000) was already clear (II) TRIDENT(0): Primary V_BIOS segment is: 0xc000 (==) TRIDENT(0): Write-combining range (0x0,0x1000) was already clear (II) TRIDENT(0): Overriding Horizontal timings. (II) TRIDENT(0): Shadow off (II) TRIDENT(0): H-timing shadow registers: 0x7f 0x00 0x69 0x7f (II) TRIDENT(0): H-timing registers: 0x7f 0x63 0x63 0x00 0x69 0x7f (II) TRIDENT(0): V-timing shadow registers: 0x72 0xf0 0x59 0x0d 0x00 (0x08) (II) TRIDENT(0): V-timing registers: 0x72 0xf0 0x59 0x0d 0x57 0x00 0x00 (II) TRIDENT(0): Setting BIOS Mode: 6d (II) TRIDENT(0): Found Clock 80.00 n=249 m=21 k=1 (II) TRIDENT(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles CPU to Screen color expansion Solid Horizontal and Vertical Lines Image Writes Offscreen Pixmaps Setting up tile and stipple cache: 30 128x128 slots (==) TRIDENT(0): Backing store disabled (II) TRIDENT(0): Trident Video Flags: VID_ZOOM_INV VID_ZOOM_MINI (==) RandR enabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension LBX (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Keyboard "Keyboard0" handled by legacy driver (**) Option "Protocol" "SysMouse" (**) Mouse0: Protocol: "SysMouse" (**) Option "CorePointer" (**) Mouse0: Core Pointer (**) Option "Device" "/dev/sysmouse" (**) Option "BaudRate" "1200" (**) Option "StopBits" "2" (**) Option "DataBits" "8" (**) Option "Parity" "None" (**) Option "Vmin" "1" (**) Option "Vtime" "0" (**) Option "FlowControl" "None" (**) Option "Emulate3Buttons" (**) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 (==) Mouse0: Buttons: 3 (**) Mouse0: BaudRate: 1200 (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) --cWoXeonUoKmBZSoM-- From owner-freebsd-mobile@FreeBSD.ORG Mon Dec 8 08:26:19 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EFA916A4CE for ; Mon, 8 Dec 2003 08:26:19 -0800 (PST) Received: from gs166.sp.cs.cmu.edu (GS166.SP.CS.CMU.EDU [128.2.205.169]) by mx1.FreeBSD.org (Postfix) with SMTP id 09F5043F93 for ; Mon, 8 Dec 2003 08:26:18 -0800 (PST) (envelope-from dpelleg@gs166.sp.cs.cmu.edu) Sender: dpelleg@gs166.sp.cs.cmu.edu To: Sanluca References: <20031206160717.45247988.sanluca78@virgilio.it> From: Dan Pelleg Date: 08 Dec 2003 11:25:34 -0500 In-Reply-To: <20031206160717.45247988.sanluca78@virgilio.it> Message-ID: Lines: 13 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-mobile@freebsd.org Subject: Re: irda X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 16:26:19 -0000 Sanluca writes: > hello to all, > I have portable toshiba a satellite 1410 and would want to make to work the door irda, someone knows gives to me to some address web or council on like beginning? > thanks to all and excused for my English I'm not sure what exactly you want. But as a first step, did you try the birda port? -- Dan Pelleg From owner-freebsd-mobile@FreeBSD.ORG Mon Dec 8 15:16:29 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74C3F16A4CE for ; Mon, 8 Dec 2003 15:16:29 -0800 (PST) Received: from basie.internet2.edu (basie.internet2.edu [207.75.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 854AA43D1D for ; Mon, 8 Dec 2003 15:16:28 -0800 (PST) (envelope-from shalunov@internet2.edu) Received: from localhost (localhost.localdomain [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id DD2F159B; Mon, 8 Dec 2003 18:16:27 -0500 (EST) Received: by basie.internet2.edu (Postfix, from userid 1057) id DF45E5B3; Mon, 8 Dec 2003 18:16:26 -0500 (EST) Date: Mon, 8 Dec 2003 18:16:26 -0500 From: stanislav shalunov To: Kevin Oberman Message-ID: <20031208231626.GA2153@internet2.edu> References: <20031203194445.GA2941@internet2.edu> <20031203221921.C523E5D04@ptavv.es.net> <20031205065616.GE15993@internet2.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031205065616.GE15993@internet2.edu> User-Agent: Mutt/1.4i X-Virus-Scanned: by mail.internet2.edu virus scanner cc: freebsd-mobile@FreeBSD.org Subject: Re: FreeBSD 5.1-RELEASE on IBM ThinkPad T30 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 23:16:29 -0000 Thanks for all the help, Kevin! I had a chance to play with the machine again today and I now have everything but the builtin wireless card mostly working. Is the Cisco Aironet MPI350 card supposed to work on this machine? I found a vague pointer at http://lists.freebsd.org/pipermail/freebsd-mobile/2003-May/000481.html (with GENERIC, I had the same symptoms as the OP of that thread). Is it still necessary to downgrade the firmware? What is the procedure to do that? --Stanislav From owner-freebsd-mobile@FreeBSD.ORG Mon Dec 8 16:15:49 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5748116A4CE for ; Mon, 8 Dec 2003 16:15:49 -0800 (PST) Received: from Espresso.NEEBU.Net (espresso.neebu.net [66.166.158.130]) by mx1.FreeBSD.org (Postfix) with SMTP id E0C9643D21 for ; Mon, 8 Dec 2003 16:15:46 -0800 (PST) (envelope-from khuon@Espresso.NEEBU.Net) Received: from Espresso.NEEBU.Net (khuon@localhost [127.0.0.1]) by Espresso.NEEBU.Net (8.12.10/8.12.10) with ESMTP id hB90Boic026640; Mon, 8 Dec 2003 16:11:52 -0800 (PST) Received: from Espresso.NEEBU.Net (khuon@localhost)hB90Bnd3026639; Mon, 8 Dec 2003 16:11:49 -0800 (PST) Message-Id: <200312090011.hB90Bnd3026639@Espresso.NEEBU.Net> From: "Jake Khuon" To: stanislav shalunov Dcc: In-reply-to: stanislav shalunov's message of Mon, 08 Dec 2003 18:16:26 -0500. <20031208231626.GA2153@internet2.edu> Action: Expires: Precedence: Priority: Normal X-Face: "(e&e|OIYrcV1x8y?txN%k1E2f[qWLjRjOn+a30)3>x`Wx%_9XiXs\IO2#G5L1m=c/|^h|z29wJ#]D/.?Ks,Mw1 X-URI: http://Espresso.NEEBU.Net/~khuon/ X-Organisation: Network Engineers for Effective Bandwidth Utilisation X-Header: /usr/include gives great headers X-System: Sun UltraSPARCstation2/2300MP running SunOS Release 5.8 X-Shell: tcsh 6.07.02 (Astron) 1996-10-27 (sparc-sun-solaris) options 8b,nls,dl,al,ng,rh X-Chtorr: History is full of revisionists. Where it used to say "THOU SHALT NOT KILL" it now says, "except as specified in section III-B, Paragraph 12, Sub-section D, Schedule 3." If that still doesn't suit you, wait till next year's commandments come out and trade it in for something that does. X-Mailer: MH 6.8.4 #4[UCI] (Espresso.NEEBU.Net) of Mon Feb 19 15:14:03 EST 1996 Date: Mon, 08 Dec 2003 16:11:49 -0800 Sender: khuon@Espresso.NEEBU.Net cc: freebsd-mobile@freebsd.org Subject: Re: FreeBSD 5.1-RELEASE on IBM ThinkPad T30 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Reply-To: Jake Khuon List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2003 00:15:49 -0000 ### On Mon, 8 Dec 2003 18:16:26 -0500, stanislav shalunov ### casually decided to expound upon Kevin Oberman ### the following thoughts about "Re: FreeBSD 5.1-RELEASE ### on IBM ThinkPad T30": ss> I had a chance to play with the machine again today ss> and I now have everything but the builtin wireless ss> card mostly working. Is the Cisco Aironet MPI350 card ss> supposed to work on this machine? I found a vague pointer at ss> http://lists.freebsd.org/pipermail/freebsd-mobile/2003-May/000481.html ss> (with GENERIC, I had the same symptoms as the OP of that thread). I did a firmware downgrade but still couldn't get it to boot the 5.1R installer... hangs in the same place after attempting to probe the card. I was able to get it working under 4.9R though. ss> Is it still necessary to downgrade the firmware? What is the procedure ss> to do that? This is what I did: [0] boot into Windows [1] download firmware 5.00.01 from Cisco's site [2] run self-extracting exectuable file and store new firmware in someplace like C:\Program Files\Cisco System\Aironet Client Utility\Firmware [3] download NDIS Windows driver 2.22 from Cisco's site (necessary to have Windows work with older firmware) [4] run self-extracting exectuable file and store new drivers in someplace like C:\Program Files\Cisco Systems\MPI350v222 [5] launch Cisco's client utility app [6] click on load firmware and maneuver through until you get to where you placed your firmware and select it then follow the instructions to continue flashing it --- Skip step 7 if you don't care about Windows --- [7] open up the properties page for your wireless card and attempt to update the drivers (this will be different for various versions of Windows) and update with the 2.22 NDIS drivers [8] shutdown Windows and boot into FreeBSD [9] confirm you can see the card with ifconfig and ancontrol Hope that helps... Note - You don't need to download the whole kit-n-kaboodle from Cisco... just the firmware and drivers. The latest client utility will still work fine. -- /*===================[ Jake Khuon ]======================+ | Packet Plumber, Network Engineers /| / [~ [~ |) | | --------------- | | for Effective Bandwidth Utilisation / |/ [_ [_ |) |_| N E T W O R K S | +=========================================================================*/ From owner-freebsd-mobile@FreeBSD.ORG Mon Dec 8 20:25:07 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 003D716A4CE for ; Mon, 8 Dec 2003 20:25:07 -0800 (PST) Received: from mail-aubervilliers.netaktiv.com (soyouz.netaktiv.com [80.67.170.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6544643D13 for ; Mon, 8 Dec 2003 20:25:05 -0800 (PST) (envelope-from stephane@laperouse.internatif.org) Received: by mail-aubervilliers.netaktiv.com (Postfix, from userid 10) id 9D7E123D14; Tue, 9 Dec 2003 05:25:04 +0100 (CET) Received: by fetiche.sources.org (Postfix, from userid 1001) id B1DE29AD0; Mon, 8 Dec 2003 20:45:47 +0430 (AFT) Date: Mon, 8 Dec 2003 20:45:47 +0430 From: Stephane Bortzmeyer To: freebsd-mobile@freebsd.org Message-ID: <20031208161547.GA1983@fetiche.sources.org> References: <20031207163127.GA791@fetiche.sources.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031207163127.GA791@fetiche.sources.org> User-Agent: Mutt/1.4.1i X-Transport: UUCP rules X-Operating-System: FreeBSD 5.1-RELEASE i386 Subject: Re: X freezes my Sony Vaio PCG-F801 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2003 04:25:07 -0000 On Sun, Dec 07, 2003 at 09:01:27PM +0430, Stephane Bortzmeyer wrote a message of 608 lines which said: > It seems that the problem only occurs with Emacs. If I spend my time > surfing with Mozilla, I do not have the problem, may be because I do > not type. Wrong: it freezes as well even when I take care of not using Emacs at all. From owner-freebsd-mobile@FreeBSD.ORG Tue Dec 9 12:31:18 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EB8F16A4CF for ; Tue, 9 Dec 2003 12:31:18 -0800 (PST) Received: from ran.psg.com (ip166.usw253.dsl-acs2.sea.iinet.com [209.20.253.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50E9943D1D for ; Tue, 9 Dec 2003 12:31:17 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com) by ran.psg.com with esmtp (Exim 4.24; FreeBSD) id 1AToVk-0001OI-Hz; Tue, 09 Dec 2003 12:31:12 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 9 Dec 2003 12:31:11 -0800 To: Lars References: <3FAA2761.8090808@ecad.org> <200311060618.59528.rodperson@comcast.net> <3FAA3663.5000304@ecad.org> <20031106123347.GA17013@gmx.at> Message-Id: cc: Jev cc: freebsd-mobile@freebsd.org Subject: Re: thinkpad R40 freebsd preperation questions... X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2003 20:31:18 -0000 > About the CDs, I also didn't receive any CDs with the notebook. > But just after I received the notebook I called IBM and asked them > to send me them. I had to haggle with Support however, since they > didn't want to send me the disks without me having a problem. > I then told them I borked my hdd and then they sent them. i have a brand new t40p, purchased with winxp. i called support about the getting the winxp cd-roms. they said no problem. we talked a bit and i made clear i needed winxp installs, not something that would wipe my disk drive, i.e., the standard recovery. i got a four disk set and they all seem to be part of a full wipe-your-drive recovery set. the problem is i need to pick some dlls from a winxp distro so a winxp guest under vmware3 uses apm not acpi (see vmware hints somewhere on the vmware site). specifically, what do i ask ibm support for? got a part number? randy From owner-freebsd-mobile@FreeBSD.ORG Tue Dec 9 12:35:16 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49CE716A4CE for ; Tue, 9 Dec 2003 12:35:16 -0800 (PST) Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03BE643D2E for ; Tue, 9 Dec 2003 12:35:15 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 1AToZe-0003WA-00 for freebsd-mobile@freebsd.org; Tue, 09 Dec 2003 15:35:14 -0500 Date: Tue, 9 Dec 2003 15:35:14 -0500 From: Peter Radcliffe To: freebsd-mobile@freebsd.org Message-ID: <20031209203514.GI9505@pir.net> Mail-Followup-To: freebsd-mobile@freebsd.org References: <3FAA2761.8090808@ecad.org> <200311060618.59528.rodperson@comcast.net> <3FAA3663.5000304@ecad.org> <20031106123347.GA17013@gmx.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Subject: Re: thinkpad R40 freebsd preperation questions... X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-mobile@freebsd.org List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2003 20:35:16 -0000 Randy Bush probably said: > i have a brand new t40p, purchased with winxp. i called support > about the getting the winxp cd-roms. they said no problem. we > talked a bit and i made clear i needed winxp installs, not > something that would wipe my disk drive, i.e., the standard > recovery. i got a four disk set and they all seem to be part of a > full wipe-your-drive recovery set. That's the only type of CDs I've ever received with or for a laptop. > the problem is i need to pick some dlls from a winxp distro so a > winxp guest under vmware3 uses apm not acpi (see vmware hints > somewhere on the vmware site). > > specifically, what do i ask ibm support for? got a part number? I think you're SOL. ALl the IBM install CDs for laptops I've seen have been recovery CDs that will install over whatever is currently there. P. -- pir From owner-freebsd-mobile@FreeBSD.ORG Tue Dec 9 12:42:52 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DE3716A4CE for ; Tue, 9 Dec 2003 12:42:52 -0800 (PST) Received: from arbornet.org (m-net.arbornet.org [209.142.209.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C0CE43D2D for ; Tue, 9 Dec 2003 12:42:45 -0800 (PST) (envelope-from lei@m-net.arbornet.org) Received: from m-net.arbornet.org (localhost [127.0.0.1]) by arbornet.org (8.12.3p2/8.11.2) with ESMTP id hB9KkADr009264 for ; Tue, 9 Dec 2003 15:46:10 -0500 (EST) (envelope-from lei@m-net.arbornet.org) Received: from localhost (lei@localhost)hB9KkApf009261 for ; Tue, 9 Dec 2003 15:46:10 -0500 (EST) Date: Tue, 9 Dec 2003 15:46:10 -0500 (EST) From: Lei Z To: freebsd-mobile@freebsd.org In-Reply-To: Message-ID: <20031209150801.H94358-100000@m-net.arbornet.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Has anyone tried this trick? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2003 20:42:52 -0000 Hi, A while ago, I read somewhere on the web that, with an adapter, it's possible to take out the laptop hard drive and put it into a desktop machine. After installing OS('s) on it, put the hard drive back to the laptop and generally things should work with some minor re-configurations such as X. I bought an Armada m300 (it came with no floppy or CD-ROM drive) from ebay a few days ago. I tried various possibilities to get this to work. When the laptop hard disk was in the desktop, it worked flawlessly just like a regular desktop hard disk with every OS I tested with including DOS, win 98, win2k (no chance to try FreeBSD yet). But after I put it back to the laptop with installed OS, the partition was recognized and bootable only when DOS was installed. When the primary partion was installed with win98, or win2k, the disk is simply not bootable. Also, DOS extended partition is not recognized in the laptop either. I created the primary partition under DOS, during Windows 2000 installation, or under desktop's Windows XP (laptop disk mounted as slave), but the results were mostly the same. Is this a BIOS incompatibility, or something else? Has anybody got successful experience with this trick? A quick search showed that Armada m300 doesn't seem to have a special reserved partition like some other laptops. Thanks for any hints, suggestions to get this work. Leo From owner-freebsd-mobile@FreeBSD.ORG Tue Dec 9 12:47:50 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDFBA16A4CE for ; Tue, 9 Dec 2003 12:47:50 -0800 (PST) Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F3AA43D1F for ; Tue, 9 Dec 2003 12:47:50 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 1ATolp-0003bW-00 for freebsd-mobile@freebsd.org; Tue, 09 Dec 2003 15:47:49 -0500 Date: Tue, 9 Dec 2003 15:47:49 -0500 From: Peter Radcliffe To: freebsd-mobile@freebsd.org Message-ID: <20031209204749.GK9505@pir.net> Mail-Followup-To: freebsd-mobile@freebsd.org References: <20031209150801.H94358-100000@m-net.arbornet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031209150801.H94358-100000@m-net.arbornet.org> User-Agent: Mutt/1.4.1i X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Subject: Re: Has anyone tried this trick? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-mobile@freebsd.org List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2003 20:47:51 -0000 Lei Z probably said: > When the laptop hard disk was in the desktop, it worked flawlessly > just like a regular desktop hard disk with every OS I tested with > including DOS, win 98, win2k (no chance to try FreeBSD yet). But > after I put it back to the laptop with installed OS, the partition > was recognized and bootable only when DOS was installed. When the > primary partion was installed with win98, or win2k, the disk is > simply not bootable. I've had this problem with several laptops, ended up doing the original partition setup and a small install on the laptop itself and then removing the disk to do the rest of the install. P. -- pir From owner-freebsd-mobile@FreeBSD.ORG Tue Dec 9 13:25:33 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B020F16A4CE for ; Tue, 9 Dec 2003 13:25:33 -0800 (PST) Received: from basie.internet2.edu (basie.internet2.edu [207.75.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 973AB43D2C for ; Tue, 9 Dec 2003 13:25:32 -0800 (PST) (envelope-from shalunov@internet2.edu) Received: from localhost (localhost.localdomain [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id D718A4F4; Tue, 9 Dec 2003 16:25:31 -0500 (EST) Received: by basie.internet2.edu (Postfix, from userid 1057) id D7A755A4; Tue, 9 Dec 2003 16:25:30 -0500 (EST) Date: Tue, 9 Dec 2003 16:25:30 -0500 From: stanislav shalunov To: Jake Khuon Message-ID: <20031209212530.GC17284@internet2.edu> References: <20031208231626.GA2153@internet2.edu> <200312090011.hB90Bnd3026639@Espresso.NEEBU.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200312090011.hB90Bnd3026639@Espresso.NEEBU.Net> User-Agent: Mutt/1.4i X-Virus-Scanned: by mail.internet2.edu virus scanner cc: freebsd-mobile@freebsd.org Subject: SOLVED: FreeBSD 5.1-RELEASE on IBM ThinkPad T30 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2003 21:25:33 -0000 Thank you very much. The machine appears to work now, including the internal Cisco Aironet MPI350 card. I documented what I had to do to make it work at http://www.internet2.edu/~shalunov/FreeBSD-IBM-T30/ From owner-freebsd-mobile@FreeBSD.ORG Tue Dec 9 13:45:34 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3990416A4CE for ; Tue, 9 Dec 2003 13:45:34 -0800 (PST) Received: from guldan.demon.nl (cust.13.38.adsl.cistron.nl [62.216.13.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F66943D09 for ; Tue, 9 Dec 2003 13:45:21 -0800 (PST) (envelope-from robert@guldan.demon.nl) Received: from bombur.guldan.demon.nl ([192.168.1.3] helo=localhost) by guldan.demon.nl with esmtp (Exim 4.24; FreeBSD) id 1ATpfb-0006Me-3K for freebsd-mobile@freebsd.org; Tue, 09 Dec 2003 22:45:27 +0100 Date: Tue, 9 Dec 2003 22:45:22 +0100 From: Robert Blacquiere To: freebsd-mobile@freebsd.org Message-ID: <20031209214522.GB66019@bombur.guldan.demon.nl> References: <20031209150801.H94358-100000@m-net.arbornet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031209150801.H94358-100000@m-net.arbornet.org> User-Agent: Mutt/1.4.1i X-Spam-Score: 0.0 (/) X-Spam-Report: Spam detection software, running on the system "thorin.guldan.demon.nl", hasmessageblock similar future email. If you have any questions, see the administrator of that system for details.wrote: > Hi, > > I bought an Armada m300 (it came with no floppy or laptop, i've got the same notebook and the intel pxe boot works. There is a document on the web about jumpstarting FreeBSD that's a usefull guide to do the install. [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description -------------------------------------------------- Subject: Re: Has anyone tried this trick? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2003 21:45:34 -0000 On Tue, Dec 09, 2003 at 03:46:10PM -0500, Lei Z wrote: > Hi, > > I bought an Armada m300 (it came with no floppy or CD-ROM drive) from ebay > a few days ago. Try pxebooting of the laptop, i've got the same notebook and the intel pxe boot works. There is a document on the web about jumpstarting FreeBSD that's a usefull guide to do the install. >I tried various possibilities to get this to work. When > the laptop hard disk was in the desktop, it worked flawlessly just like a > regular desktop hard disk with every OS I tested with including DOS, win > 98, win2k (no chance to try FreeBSD yet). But after I put it back to the > laptop with installed OS, the partition was recognized and bootable only > when DOS was installed. When the primary partion was installed with win98, > or win2k, the disk is simply not bootable. Also, DOS extended partition is > not recognized in the laptop either. I created the primary partition under > DOS, during Windows 2000 installation, or under desktop's Windows XP > (laptop disk mounted as slave), but the results were mostly the same. Net boot seems to be a good alternative. > > Is this a BIOS incompatibility, or something else? Has anybody got > successful experience with this trick? A quick search showed that Armada > m300 doesn't seem to have a special reserved partition like some other > laptops. Thanks for any hints, suggestions to get this work. > > Leo > > Robert -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? OpenBSD: Hey guys you left some holes out there! From owner-freebsd-mobile@FreeBSD.ORG Tue Dec 9 20:26:12 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B66D16A4CE for ; Tue, 9 Dec 2003 20:26:12 -0800 (PST) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2274043D21 for ; Tue, 9 Dec 2003 20:26:11 -0800 (PST) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.9/8.12.9) with ESMTP id hBA4Q9FW058950; Tue, 9 Dec 2003 23:26:10 -0500 (EST) (envelope-from mdodd@FreeBSD.ORG) Date: Tue, 9 Dec 2003 23:26:09 -0500 (EST) From: "Matthew N. Dodd" X-X-Sender: winter@sasami.jurai.net To: Lei Z In-Reply-To: <20031209150801.H94358-100000@m-net.arbornet.org> Message-ID: <20031209232514.W39190@sasami.jurai.net> References: <20031209150801.H94358-100000@m-net.arbornet.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Has anyone tried this trick? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 04:26:12 -0000 On Tue, 9 Dec 2003, Lei Z wrote: > But after I put it back to the laptop with installed OS, the partition > was recognized and bootable only when DOS was installed. You should try turning packet mode on with 'boot0cfg'. That typically fixes the unbootable partition problems I've encountered. -- 10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00 From owner-freebsd-mobile@FreeBSD.ORG Wed Dec 10 01:10:19 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC20516A4CF for ; Wed, 10 Dec 2003 01:10:19 -0800 (PST) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44C0543D1F for ; Wed, 10 Dec 2003 01:10:18 -0800 (PST) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.24; FreeBSD) id 1AU0Pi-0000Hi-QU; Wed, 10 Dec 2003 12:13:46 +0300 From: "Vladimir B. Grebenschikov" To: stanislav shalunov In-Reply-To: <20031209212530.GC17284@internet2.edu> References: <20031208231626.GA2153@internet2.edu> <200312090011.hB90Bnd3026639@Espresso.NEEBU.Net> <20031209212530.GC17284@internet2.edu> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Organization: SWsoft Inc. Message-Id: <1071047625.740.3.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Wed, 10 Dec 2003 12:13:46 +0300 Sender: Vladimir Grebenschikov cc: Jake Khuon cc: freebsd-mobile Subject: Re: SOLVED: FreeBSD 5.1-RELEASE on IBM ThinkPad T30 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 09:10:19 -0000 =F7 =D3=D2, 10.12.2003, =D7 00:25, stanislav shalunov =D0=C9=DB=C5=D4: > Thank you very much. The machine appears to work now, including the > internal Cisco Aironet MPI350 card. I documented what I had to do to > make it work at http://www.internet2.edu/~shalunov/FreeBSD-IBM-T30/ Congratulations. Have your T30 integrated BlueTooth adapter ? Is it works out of box or somehow ? --=20 Vladimir B. Grebenschikov SWsoft Inc. From owner-freebsd-mobile@FreeBSD.ORG Wed Dec 10 02:56:19 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1E0616A4CE for ; Wed, 10 Dec 2003 02:56:19 -0800 (PST) Received: from mailhub02.unibe.ch (mailhub02.unibe.ch [130.92.9.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id A639943D1F for ; Wed, 10 Dec 2003 02:56:17 -0800 (PST) (envelope-from roth@lara.unibe.ch) Received: from localhost (scanhub02.unibe.ch [130.92.254.66]) by mailhub02.unibe.ch (Postfix) with ESMTP id 69AEA7648A; Wed, 10 Dec 2003 11:56:16 +0100 (MET) Received: from mailhub02.unibe.ch ([130.92.9.53]) by localhost (scanhub02 [130.92.254.66]) (amavisd-new, port 10024) with LMTP id 04841-01-2; Wed, 10 Dec 2003 11:56:15 +0100 (CET) Received: from asterix.unibe.ch (asterix.unibe.ch [130.92.64.4]) by mailhub02.unibe.ch (Postfix) with ESMTP id 8E96F7649B; Wed, 10 Dec 2003 11:56:13 +0100 (MET) Received: from lara.unibe.ch (lara [130.92.64.90]) by asterix.unibe.ch (8.11.7p1+Sun/8.11.7) with ESMTP id hBAAuD508390; Wed, 10 Dec 2003 11:56:13 +0100 (MET) Received: (from roth@localhost) by lara.unibe.ch (8.12.9+Sun/8.12.9/Submit) id hBAAuCVD024455; Wed, 10 Dec 2003 11:56:12 +0100 (MET) Date: Wed, 10 Dec 2003 11:56:12 +0100 From: Tobias Roth To: "Vladimir B. Grebenschikov" Message-ID: <20031210105612.GA24445@lara.unibe.ch> Mail-Followup-To: "Vladimir B. Grebenschikov" , freebsd-mobile@freebsd.org References: <20031208231626.GA2153@internet2.edu> <200312090011.hB90Bnd3026639@Espresso.NEEBU.Net> <20031209212530.GC17284@internet2.edu> <1071047625.740.3.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1071047625.740.3.camel@localhost> User-Agent: Mutt/1.4i X-Operating-System: SunOS lara 5.9 Generic_112233-04 sun4u sparc SUNW,Ultra-5_10 X-Virus-checked: by University of Berne cc: freebsd-mobile@freebsd.org Subject: Re: SOLVED: FreeBSD 5.1-RELEASE on IBM ThinkPad T30 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 10:56:19 -0000 On Wed, Dec 10, 2003 at 12:13:46PM +0300, Vladimir B. Grebenschikov wrote: > ÷ ÓÒ, 10.12.2003, × 00:25, stanislav shalunov ÐÉÛÅÔ: > > > Thank you very much. The machine appears to work now, including the > > internal Cisco Aironet MPI350 card. I documented what I had to do to > > make it work at http://www.internet2.edu/~shalunov/FreeBSD-IBM-T30/ > > Congratulations. > > Have your T30 integrated BlueTooth adapter ? > Is it works out of box or somehow ? mine has and it works very well: kernel: ubt0: TDK IBM Integrated Bluetooth, rev 1.10/3.1 0, addr 2 cheers, t. From owner-freebsd-mobile@FreeBSD.ORG Wed Dec 10 06:49:52 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6723B16A4CE for ; Wed, 10 Dec 2003 06:49:52 -0800 (PST) Received: from mail.aguntum.de (aguntum.de [213.133.109.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBCBA43D1D for ; Wed, 10 Dec 2003 06:49:46 -0800 (PST) (envelope-from ov@baily.de) Received: by mail.aguntum.de (Postfix, from userid 30) id 306D613980; Wed, 10 Dec 2003 15:53:34 +0100 (CET) Received: from 62.245.233.95 (SquirrelMail authenticated user oliver) by intranet.aguntum.dyndns.org with HTTP; Wed, 10 Dec 2003 15:53:34 +0100 (CET) Message-ID: <3453.62.245.233.95.1071068014.squirrel@intranet.aguntum.dyndns.org> Date: Wed, 10 Dec 2003 15:53:34 +0100 (CET) From: "Oliver Velten" To: freebsd-mobile@FreeBSD.ORG User-Agent: SquirrelMail/1.4.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Subject: Proxim Harmony Installation Problems X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 14:49:52 -0000 Hi! I bought a Proxim Harmony PCI 802.11b and tried to install it under FreeBSD 4.9 . The Problem ist that FreeBSD does not create a wi Interface when it comes up. The Card has a PCI to PCMCIA bridge which is recognized. I have built in the Kernel the wi device and pccardd support. Here some output of several Programs: > root@zeus:~> scanpci pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x1022 device 0x7006 Advanced Micro Devices [AMD] AMD-751 [Irongate] System Controller pci bus 0x0000 cardnum 0x01 function 0x00: vendor 0x1022 device 0x7007 Advanced Micro Devices [AMD] AMD-751 [Irongate] AGP Bridge pci bus 0x0000 cardnum 0x07 function 0x00: vendor 0x1022 device 0x7408 Advanced Micro Devices [AMD] AMD-756 [Viper] ISA pci bus 0x0000 cardnum 0x07 function 0x01: vendor 0x1022 device 0x7409 Advanced Micro Devices [AMD] AMD-756 [Viper] IDE pci bus 0x0000 cardnum 0x07 function 0x03: vendor 0x1022 device 0x740b Advanced Micro Devices [AMD] AMD-756 [Viper] ACPI pci bus 0x0000 cardnum 0x07 function 0x04: vendor 0x1022 device 0x740c Advanced Micro Devices [AMD] AMD-756 [Viper] USB pci bus 0x0000 cardnum 0x08 function 0x00: vendor 0x10b7 device 0x9200 3Com Corporation 3c905C-TX/TX-M [Tornado] pci bus 0x0000 cardnum 0x09 function 0x00: vendor 0x9005 device 0x0081 Adaptec AIC-7892B U160/m pci bus 0x0000 cardnum 0x0a function 0x00: vendor 0x10b7 device 0x7646 3Com Corporation 3cSOHO100-TX Hurricane pci bus 0x0000 cardnum 0x0b function 0x00: vendor 0x1013 device 0x1100 Cirrus Logic CL 6729 pci bus 0x0001 cardnum 0x05 function 0x00: vendor 0x10de device 0x0020 nVidia Corporation NV4 [RIVA TNT] root@zeus:~> > root@zeus:~> pccardc dumpcis Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 3 000: 00 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = 512b, 1 units Tuple #2, code = 0x17 (Attribute memory descriptor), length = 4 000: 67 5a 08 ff Attribute memory device information: Device number 1, type SRAM, WPS = OFF Speed = 5.0 x 100 ns, Memory block size = 512b, 2 units Tuple #3, code = 0x1d (Other conditions for attribute memory), length = 5 000: 03 67 5a 08 ff (MWAIT) (3V card) Tuple #4, code = 0x15 (Version 1 info), length = 80 000: 05 00 50 52 4f 58 49 4d 00 4c 41 4e 20 50 43 49 010: 20 43 41 52 44 20 48 41 52 4d 4f 4e 59 20 38 30 020: 32 31 31 42 00 00 00 00 00 00 00 00 00 00 00 00 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 = [PROXIM], card vers = [LAN PCI CARD HARMONY 80211B] Addit. info = [],[] Tuple #5, code = 0x20 (Manufacturer ID), length = 4 000: 26 01 02 00 PCMCIA ID = 0x126, OEM ID = 0x2 Tuple #6, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #7, code = 0x22 (Functional EXT), length = 2 000: 01 07 Network technology: Wireless Tuple #8, code = 0x22 (Functional EXT), length = 5 000: 02 40 42 0f 00 Network speed: 1 Mb/sec Tuple #9, code = 0x22 (Functional EXT), length = 5 000: 02 80 84 1e 00 Network speed: 2 Mb/sec Tuple #10, code = 0x22 (Functional EXT), length = 5 000: 02 60 ec 53 00 Network speed: 5 Mb/sec Tuple #11, code = 0x22 (Functional EXT), length = 5 000: 02 c0 d8 a7 00 Network speed: 11 Mb/sec Tuple #12, code = 0x22 (Functional EXT), length = 2 000: 03 07 Network media: 2.4 GHz Tuple #13, code = 0x22 (Functional EXT), length = 8 000: 04 06 00 00 f0 64 00 00 Network node ID: 00 00 f0 64 00 00 Tuple #14, code = 0x22 (Functional EXT), length = 2 000: 05 01 Network connector: closed connector standard Tuple #15, code = 0x1a (Configuration map), length = 7 000: 03 01 e0 03 00 00 01 Reg len = 4, config register addr = 0x3e0, last config = 0x1 Registers: X------- Tuple #16, code = 0x1b (Configuration entry), length = 13 000: c1 01 09 77 b5 1e 35 b5 3c 36 36 05 46 Config index = 0x1(default) Interface byte = 0x1 (I/O) Vcc pwr: Nominal operating supply voltage: 3 x 1V, ext = 0x1e Minimum operating supply voltage: 3 x 1V Maximum operating supply voltage: 3 x 1V, ext = 0x3c Max current average over 1 second: 3 x 100mA Max current average over 10 ms: 3 x 100mA Power down supply current: 1 x 10mA Card decodes 6 address lines, limited 8/16 Bit I/O Tuple #17, code = 0xff (Terminator), length = 0 2 slots found root@zeus:~> > root@zeus:~> less /boot/loader.conf userconfig_script_load="YES" autoboot_delay="2" hw.pcic.pd6729_intr_path="2" root@zeus:~> > root@zeus:~> ifconfig -a xl0: flags=8843 mtu 1500 options=3 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::204:76ff:fe8d:58d3%xl0 prefixlen 64 scopeid 0x1 ether 00:04:76:8d:58:d3 media: Ethernet autoselect (100baseTX ) status: active xl1: flags=8843 mtu 1500 options=3 inet 10.0.0.1 netmask 0xff000000 broadcast 10.255.255.255 inet6 fe80::204:76ff:fe8c:f7d7%xl1 prefixlen 64 scopeid 0x2 ether 00:04:76:8c:f7:d7 media: Ethernet autoselect (100baseTX ) status: active lp0: flags=8810 mtu 1500 faith0: flags=8002 mtu 1500 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet 127.0.0.1 netmask 0xff000000 ppp0: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 ipr0: flags=2810 mtu 1500 ipr1: flags=2810 mtu 1500 ipr2: flags=2810 mtu 1500 ipr3: flags=2810 mtu 1500 isp0: flags=8010 mtu 1500 ether 00:00:00:00:00:00 isp1: flags=8010 mtu 1500 ether 00:00:00:00:00:00 isp2: flags=8010 mtu 1500 ether 00:00:00:00:00:00 isp3: flags=8010 mtu 1500 ether 00:00:00:00:00:00 tun0: flags=8051 mtu 1500 inet 62.245.233.95 --> 62.245.233.1 netmask 0xffffffff Opened by PID 59598 root@zeus:~> If someone has an idea please let me know. Regards, Oliver From owner-freebsd-mobile@FreeBSD.ORG Wed Dec 10 13:40:22 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E914F16A4CF for ; Wed, 10 Dec 2003 13:40:22 -0800 (PST) Received: from biocandy.shapeshifter.se (h125n2fls31o270.telia.com [217.208.199.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B8B643D2A for ; Wed, 10 Dec 2003 13:40:20 -0800 (PST) (envelope-from NOfreddeSPAM@shapeshifter.se) Received: from biocandy.shapeshifter.se (localhost [127.0.0.1]) hBALeJVN000967 for ; Wed, 10 Dec 2003 22:40:19 +0100 (CET) (envelope-from NOfreddeSPAM@shapeshifter.se) Received: (from fredde@localhost) by biocandy.shapeshifter.se (8.12.10/8.12.10/Submit) id hBALeJqA000966 for freebsd-mobile@freebsd.org; Wed, 10 Dec 2003 22:40:19 +0100 (CET) (envelope-from NOfreddeSPAM@shapeshifter.se) X-Authentication-Warning: biocandy.shapeshifter.se: fredde set sender to NOfreddeSPAM@shapeshifter.se using -f Date: Wed, 10 Dec 2003 22:40:19 +0100 From: Fredrik Lindberg To: freebsd-mobile@freebsd.org Message-ID: <20031210213840.GA870@shapeshifter.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: ACPI/PCI-bus issue with compaq evo n160 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 21:40:23 -0000 Hi, I have a Compaq evo n160 running FreeBSD biocandy 5.2-RC FreeBSD 5.2-RC #10: Mon Dec 8 19:08:38 CET 2003 The machine fails (and always has) to boot with acpi enabled (locks up when mounting /), however, I managed to find out that booting with the following option debug.acpi.disable="pci" in /boot/loader.conf made the machine boot correctly and acpi related functions such as battry monitoring worked just fine. But, and a huge but, no pci devices are detected during boot (maybe quite obvious because of that debug option) All pci-devices works perfectly with acpi disabled. Now, is there any chance to make freebsd use acpi and the "normal" pci-bus driver at the same time, overriding the acpi pci-bus implementation? I believe linux has a kernel option called pci=noacpi (atleast acording to google), which does this. With acpi enabled scanpci reports all the pci devices, but pciconf -l doesn't return anything. With acpi disabled, scanpci reports all pci devices, pciconf -l reports all devices. dmesg output with acpi enabled http://shapeshifter.se/~fredde/tmp/dmesg.acpi.enabled dmesg out with acpi disabled http://shapeshifter.se/~fredde/tmp/dmesg.acpi.disabled Any, and I mean any, help on this will be very appreciated. Thanks, Fredrik From owner-freebsd-mobile@FreeBSD.ORG Wed Dec 10 19:55:10 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9317C16A4CE for ; Wed, 10 Dec 2003 19:55:10 -0800 (PST) Received: from mail-aubervilliers.netaktiv.com (soyouz.netaktiv.com [80.67.170.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 814FD43D2F for ; Wed, 10 Dec 2003 19:55:06 -0800 (PST) (envelope-from stephane@laperouse.internatif.org) Received: by mail-aubervilliers.netaktiv.com (Postfix, from userid 10) id B14E423D07; Thu, 11 Dec 2003 04:55:05 +0100 (CET) Received: by fetiche.sources.org (Postfix, from userid 1001) id A90DA9AD0; Wed, 10 Dec 2003 20:59:52 +0430 (AFT) Date: Wed, 10 Dec 2003 20:59:51 +0430 From: Stephane Bortzmeyer To: freebsd-mobile@freebsd.org Message-ID: <20031210162951.GA727@fetiche.sources.org> References: <20031207163127.GA791@fetiche.sources.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031207163127.GA791@fetiche.sources.org> User-Agent: Mutt/1.4.1i X-Transport: UUCP rules X-Operating-System: FreeBSD 5.1-RELEASE i386 Subject: Re: X freezes my Sony Vaio PCG-F801 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 03:55:10 -0000 On Sun, Dec 07, 2003 at 09:01:27PM +0430, Stephane Bortzmeyer wrote a message of 608 lines which said: > On a Sony Vaio PCG-F801, I installed FreeBSD 5.1-RELEASE, which comes > with Xfree 4.3.0. ... > When I use X, edition with Emacs makes the machine freezes after ten > or twenty minutes of use. The cursor no longer moves, Crtl-Alt-F1 and > Ctrl-Alt-Backspace are ignored. I have to reboot the hard way. What I tried: > (**) Option "Protocol" "SysMouse" > (**) Mouse0: Protocol: "SysMouse" > (**) Option "CorePointer" > (**) Mouse0: Core Pointer > (**) Option "Device" "/dev/sysmouse" 1) Changing the protocol to PS/2 and stopping moused. X works but freezes the same. 2) Testing with a color depth of 8 only. No change. 3) I tried to test with the "svga" driver instead of "trident" but I d not find it in /usr/X11R6/lib/modules/drivers. Is it normal? From owner-freebsd-mobile@FreeBSD.ORG Wed Dec 10 23:46:12 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDCAF16A4CF for ; Wed, 10 Dec 2003 23:46:12 -0800 (PST) Received: from smtp.hccnet.nl (smtp.hccnet.nl [62.251.0.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8739543D2C for ; Wed, 10 Dec 2003 23:46:10 -0800 (PST) (envelope-from d.wylie@hccnet.nl) Received: from webmail10.hccnet.nl by smtp.hccnet.nl via webmail10.hccnet.nl [62.251.0.62] with ESMTP id hBB7k82W017850 (8.12.10/2.03); Thu, 11 Dec 2003 08:46:08 +0100 (MET) Message-Id: <200312110746.hBB7k82W017850@smtp.hccnet.nl> Content-Transfer-Encoding: binary Content-Type: multipart/mixed; boundary="_----------=_1071128768206437" MIME-Version: 1.0 X-Mailer: MIME::Lite 2.106 (A1.17; B2.12; Q2.03) Date: Thu, 11 Dec 2003 07:46:08 UT From: d.wylie@hccnet.nl To: stephane@laperouse.internatif.org cc: freebsd-mobile@freebsd.org Subject: Re: X freezes my Sony Vaio PCG-F801 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 07:46:12 -0000 This is a multi-part message in MIME format. --_----------=_1071128768206437 Content-Disposition: inline Content-Length: 1905 Content-Transfer-Encoding: binary Content-Type: text/plain My Compaq Presario 1600 also freezes with the trident driver and XFree 4.3.0. and any 5.x. Was ok under 4.8, don't remember the XFree version. Try "vesa" instead of "trident" and I think you'll be fine. I don't know the extent of speed disadvantages of vesa versus trident. There've several disccusions concerning freezing trident systems, but I've never heard of a real solution yet. I'm just using the vesa driver for now, cvsup-ing often hoping for some-one to fix it. Also check the XFree site for know bugs. There are a few concerning trident. oh, running at 24bit color depth works fine here. I (and others, obviously) would much appreciate a _real_ solution. Dylan > On Sun, Dec 07, 2003 at 09:01:27PM +0430, > Stephane Bortzmeyer wrote > a message of 608 lines which said: > > > On a Sony Vaio PCG-F801, I installed FreeBSD 5.1-RELEASE, which comes > > with Xfree 4.3.0. > ... > > When I use X, edition with Emacs makes the machine freezes after ten > > or twenty minutes of use. The cursor no longer moves, Crtl-Alt-F1 and > > Ctrl-Alt-Backspace are ignored. I have to reboot the hard way. > > What I tried: > > > (**) Option "Protocol" "SysMouse" > > (**) Mouse0: Protocol: "SysMouse" > > (**) Option "CorePointer" > > (**) Mouse0: Core Pointer > > (**) Option "Device" "/dev/sysmouse" > > 1) Changing the protocol to PS/2 and stopping moused. X works but > freezes > the same. > > 2) Testing with a color depth of 8 only. No change. > > 3) I tried to test with the "svga" driver instead of "trident" but I d > not find it in /usr/X11R6/lib/modules/drivers. Is it normal? > > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile- > unsubscribe@freebsd.org" --_----------=_1071128768206437-- From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 11 02:12:35 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1624216A4CE for ; Thu, 11 Dec 2003 02:12:35 -0800 (PST) Received: from mail-aubervilliers.netaktiv.com (soyouz.netaktiv.com [80.67.170.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8135543D2A for ; Thu, 11 Dec 2003 02:12:32 -0800 (PST) (envelope-from stephane@laperouse.internatif.org) Received: by mail-aubervilliers.netaktiv.com (Postfix, from userid 10) id 86FEA23F86; Thu, 11 Dec 2003 11:12:31 +0100 (CET) Received: by fetiche.sources.org (Postfix, from userid 1001) id 1E3FC9AD2; Thu, 11 Dec 2003 14:42:10 +0430 (AFT) Date: Thu, 11 Dec 2003 14:42:09 +0430 From: Stephane Bortzmeyer To: d.wylie@hccnet.nl Message-ID: <20031211101209.GD609@fetiche.sources.org> References: <200312110746.hBB7k82W017850@smtp.hccnet.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200312110746.hBB7k82W017850@smtp.hccnet.nl> User-Agent: Mutt/1.4.1i X-Transport: UUCP rules X-Operating-System: FreeBSD 5.1-RELEASE i386 cc: freebsd-mobile@freebsd.org cc: stephane@laperouse.internatif.org Subject: Re: X freezes my Sony Vaio PCG-F801 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 10:12:35 -0000 On Thu, Dec 11, 2003 at 07:46:08AM +0000, d.wylie@hccnet.nl wrote a message of 52 lines which said: > My Compaq Presario 1600 also freezes with the trident driver and > XFree 4.3.0. and any 5.x. Was ok under 4.8, don't remember the XFree > version. Try "vesa" instead of "trident" and I think you'll be > fine. Thanks but same problem with "vesa". > I (and others, obviously) would much appreciate a _real_ solution. Me too. From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 11 03:46:24 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D405116A4CE for ; Thu, 11 Dec 2003 03:46:24 -0800 (PST) Received: from smtp.hccnet.nl (smtp.hccnet.nl [62.251.0.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67A4B43D29 for ; Thu, 11 Dec 2003 03:46:23 -0800 (PST) (envelope-from d.wylie@hccnet.nl) Received: from webmail10.hccnet.nl by smtp.hccnet.nl via webmail10.hccnet.nl [62.251.0.62] with ESMTP id hBBBkM2W004015 (8.12.10/2.03); Thu, 11 Dec 2003 12:46:22 +0100 (MET) Message-Id: <200312111146.hBBBkM2W004015@smtp.hccnet.nl> Content-Transfer-Encoding: binary Content-Type: multipart/mixed; boundary="_----------=_10711431822071880" MIME-Version: 1.0 X-Mailer: MIME::Lite 2.106 (A1.17; B2.12; Q2.03) Date: Thu, 11 Dec 2003 11:46:22 UT From: d.wylie@hccnet.nl To: stephane@laperouse.internatif.org cc: freebsd-mobile@freebsd.org Subject: Re: X freezes my Sony Vaio PCG-F801 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 11:46:24 -0000 This is a multi-part message in MIME format. --_----------=_10711431822071880 Content-Disposition: inline Content-Length: 558 Content-Transfer-Encoding: binary Content-Type: text/plain Which same problem; freeze or lib? vesa solves my freeze. > On Thu, Dec 11, 2003 at 07:46:08AM +0000, > d.wylie@hccnet.nl wrote > a message of 52 lines which said: > > > My Compaq Presario 1600 also freezes with the trident driver and > > XFree 4.3.0. and any 5.x. Was ok under 4.8, don't remember the XFree > > version. Try "vesa" instead of "trident" and I think you'll be > > fine. > > Thanks but same problem with "vesa". > > > I (and others, obviously) would much appreciate a _real_ solution. > > Me too. --_----------=_10711431822071880-- From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 11 05:34:27 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4653A16A4CE for ; Thu, 11 Dec 2003 05:34:27 -0800 (PST) Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E05A43D29 for ; Thu, 11 Dec 2003 05:34:25 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtpzilla2.xs4all.nl (8.12.9/8.12.9) with ESMTP id hBBDYICb008357; Thu, 11 Dec 2003 14:34:23 +0100 (CET) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.10/8.12.9) with ESMTP id hBBDYI3k055378; Thu, 11 Dec 2003 14:34:18 +0100 (CET) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.10/8.12.9/Submit) id hBBDYIWj055377; Thu, 11 Dec 2003 14:34:18 +0100 (CET) (envelope-from wkb) Date: Thu, 11 Dec 2003 14:34:18 +0100 From: Wilko Bulte To: Fredrik Lindberg Message-ID: <20031211133418.GA55336@freebie.xs4all.nl> References: <20031210213840.GA870@shapeshifter.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031210213840.GA870@shapeshifter.se> User-Agent: Mutt/1.4.1i X-OS: FreeBSD 4.9-STABLE X-PGP: finger wilko@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: ACPI/PCI-bus issue with compaq evo n160 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 13:34:27 -0000 On Wed, Dec 10, 2003 at 10:40:19PM +0100, Fredrik Lindberg wrote: FWIW: my N160 at least does exactly the same ;) Quite recently the firewire interface started to show itself for the first time. Wilko > Hi, > > I have a Compaq evo n160 running > FreeBSD biocandy 5.2-RC FreeBSD 5.2-RC #10: Mon Dec 8 19:08:38 CET 2003 > > The machine fails (and always has) to boot with acpi enabled > (locks up when mounting /), however, I managed to find out that > booting with the following option > > debug.acpi.disable="pci" > > in /boot/loader.conf made the machine boot correctly and acpi related > functions such as battry monitoring worked just fine. > > But, and a huge but, no pci devices are detected during boot > (maybe quite obvious because of that debug option) > All pci-devices works perfectly with acpi disabled. > > Now, is there any chance to make freebsd use acpi and the > "normal" pci-bus driver at the same time, overriding the > acpi pci-bus implementation? > > I believe linux has a kernel option called pci=noacpi (atleast acording to google), > which does this. > > With acpi enabled scanpci reports all the pci devices, but pciconf -l > doesn't return anything. > With acpi disabled, scanpci reports all pci devices, pciconf -l > reports all devices. > > dmesg output with acpi enabled > http://shapeshifter.se/~fredde/tmp/dmesg.acpi.enabled > > dmesg out with acpi disabled > http://shapeshifter.se/~fredde/tmp/dmesg.acpi.disabled > > Any, and I mean any, help on this will be very appreciated. > > Thanks, > Fredrik > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" ---end of quoted text--- -- | / o / /_ _ |/|/ / / /( (_) Bulte wilko@FreeBSD.org From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 11 09:16:58 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8821716A4CE for ; Thu, 11 Dec 2003 09:16:58 -0800 (PST) Received: from hotmail.com (law10-oe54.law10.hotmail.com [64.4.14.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82CED43D31 for ; Thu, 11 Dec 2003 09:16:54 -0800 (PST) (envelope-from chrisheaththomas@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 11 Dec 2003 09:16:54 -0800 Received: from 158.234.10.144 by law10-oe54.law10.hotmail.com with DAV; Thu, 11 Dec 2003 17:16:54 +0000 X-Originating-IP: [158.234.10.144] X-Originating-Email: [chrisheaththomas@hotmail.com] X-Sender: chrisheaththomas@hotmail.com From: "Chris Thomas" To: Date: Thu, 11 Dec 2003 17:16:52 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: X-OriginalArrivalTime: 11 Dec 2003 17:16:54.0559 (UTC) FILETIME=[930992F0:01C3C00A] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Xircom on Sony Viao X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 17:16:58 -0000 Hi, I am having problems getting FreeBSD 4.9 on a Sony Viao PCG-GR114EK to = recognise a Xircom CE3 Ethernet card.=20 The boot log recognises that a pc card is present with: /kernel: pccard: card inserted, slot 0 but that's it. No mention of the xe interface coming up, or even failing = to come up and it's not present when I try ifconfig. I can forward the boot log and kernel configuration file if required. Thanks in advance, Chris. From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 11 10:23:34 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 388E216A4CE for ; Thu, 11 Dec 2003 10:23:34 -0800 (PST) Received: from postal2.es.net (proxy.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72CC043D2B for ; Thu, 11 Dec 2003 10:23:32 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465 for ; Thu, 11 Dec 2003 10:23:30 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 0D26C5D04 for ; Thu, 11 Dec 2003 10:23:30 -0800 (PST) To: mobile@freebsd.org Date: Thu, 11 Dec 2003 10:23:30 -0800 From: "Kevin Oberman" Message-Id: <20031211182330.0D26C5D04@ptavv.es.net> Subject: I think I wounded by Prism card X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 18:23:34 -0000 I have an IBM ThinkPad T30 running CURRENT as of 12/9/03. On that day I also updated the firmware on my WiFi card from 1.3.6 to 1.4.9 and my troubles began. My wireless card starts and associated normally and runs fine until I start a large transfer (such as an scp of a file of a MB or so). Then I get the dreaded: wi0: timeout in wi_cmd -x010b; event status 0x8000 wi0: xmit failed wi0: timeout in wi_seek to 13c/0 wi0: timeout in wi_seek to 13c/0 wi0: timeout in wi_seek to 13c/0 wi0: timeout in wi_seek to 13c/0 wi0: timeout in wi_seek to 13c/0 wi0: timeout in wi_seek to 13c/0 wi0: timeout in wi_seek to 151/0 wi0: timeout in wi_seek to 151/0 wi0: timeout in wi_seek to 151/0 wi0: timeout in wi_seek to 151/0 wi0: timeout in wi_seek to 151/0 wi0: timeout in wi_seek to 151/0 wi0: timeout in wi_seek to 151/0 wi0: timeout in wi_seek to 151/0 wi0: wi_cmd: busy bit won't clear. wi0: device timeout At this point the card is dead and I have only been able to recover by rebooting the system. I will try backing out the recent changes to if_wi and rebuild the module ASAP, but I only have wireless available at home, so that won't be until tonight. First, any idea as to whether the recent fixes to wi to correct timeouts in old firmware versions might have caused this? Or is it a problem with 1.4 firmware? If it is the firmware, is there any place to find the old firmware to back it off? wi0: mem 0xf8000000-0xf8000fff irq 11 at device 2.0 on pci2 wi0: 802.11 address 00:05:3c:02:43:2d wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9) wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps -- 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 From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 11 10:25:02 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FF2416A4F7 for ; Thu, 11 Dec 2003 10:25:02 -0800 (PST) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4254143D2B for ; Thu, 11 Dec 2003 10:25:01 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 20567 invoked from network); 11 Dec 2003 18:24:58 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 11 Dec 2003 18:24:58 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id hBBIOt1S011631; Thu, 11 Dec 2003 13:24:55 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20031210213840.GA870@shapeshifter.se> Date: Thu, 11 Dec 2003 13:24:56 -0500 (EST) From: John Baldwin To: Fredrik Lindberg X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-mobile@freebsd.org Subject: RE: ACPI/PCI-bus issue with compaq evo n160 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 18:25:02 -0000 On 10-Dec-2003 Fredrik Lindberg wrote: > Hi, > > I have a Compaq evo n160 running > FreeBSD biocandy 5.2-RC FreeBSD 5.2-RC #10: Mon Dec 8 19:08:38 CET 2003 > > The machine fails (and always has) to boot with acpi enabled > (locks up when mounting /), however, I managed to find out that > booting with the following option > > debug.acpi.disable="pci" > > in /boot/loader.conf made the machine boot correctly and acpi related > functions such as battry monitoring worked just fine. > > But, and a huge but, no pci devices are detected during boot > (maybe quite obvious because of that debug option) > All pci-devices works perfectly with acpi disabled. > > Now, is there any chance to make freebsd use acpi and the > "normal" pci-bus driver at the same time, overriding the > acpi pci-bus implementation? > > I believe linux has a kernel option called pci=noacpi (atleast acording to google), > which does this. > > With acpi enabled scanpci reports all the pci devices, but pciconf -l > doesn't return anything. > With acpi disabled, scanpci reports all pci devices, pciconf -l > reports all devices. > > dmesg output with acpi enabled > http://shapeshifter.se/~fredde/tmp/dmesg.acpi.enabled > > dmesg out with acpi disabled > http://shapeshifter.se/~fredde/tmp/dmesg.acpi.disabled > > Any, and I mean any, help on this will be very appreciated. If you can drop into ddb and do a 'show intrcnt' when the machine locks up that might help fix the hang. It sounds like the interrupt routing may not have worked correctly. Also, a dmesg of acpi with pci enabled would be helpful. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 11 12:29:43 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7272916A4CE for ; Thu, 11 Dec 2003 12:29:43 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6807143D2D for ; Thu, 11 Dec 2003 12:29:41 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id hBBKTZ5h008947; Thu, 11 Dec 2003 13:29:35 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 11 Dec 2003 13:26:47 -0700 (MST) Message-Id: <20031211.132647.55844740.imp@bsdimp.com> To: oberman@es.net From: "M. Warner Losh" In-Reply-To: <20031211182330.0D26C5D04@ptavv.es.net> References: <20031211182330.0D26C5D04@ptavv.es.net> X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: mobile@freebsd.org Subject: Re: I think I wounded by Prism card X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 20:29:43 -0000 In message: <20031211182330.0D26C5D04@ptavv.es.net> "Kevin Oberman" writes: : : I have an IBM ThinkPad T30 running CURRENT as of 12/9/03. On that day I : also updated the firmware on my WiFi card from 1.3.6 to 1.4.9 and my : troubles began. My wireless card starts and associated normally and runs : fine until I start a large transfer (such as an scp of a file of a MB or : so). Then I get the dreaded: : wi0: timeout in wi_cmd -x010b; event status 0x8000 That sucks. I assume no other wi messages before that? And that the - is really a 0 and you typed it in by hand. Was this under heavy load? : At this point the card is dead and I have only been able to recover by : rebooting the system. damn. : I will try backing out the recent changes to if_wi : and rebuild the module ASAP, but I only have wireless available at home, : so that won't be until tonight. I wish I'd seen this earlier, I just committed something to releng_5_2. You might try hard wiring it or something similar. : First, any idea as to whether the recent fixes to wi to correct timeouts : in old firmware versions might have caused this? Or is it a problem with : 1.4 firmware? If it is the firmware, is there any place to find the old : firmware to back it off? http://www.netgate.com/ has old images. : wi0: mem 0xf8000000-0xf8000fff irq 11 at device 2.0 on pci2 : wi0: 802.11 address 00:05:3c:02:43:2d : wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) : wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9) : wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps This should be a fairly good card to have. Warner From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 11 14:39:26 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C4C816A4CF for ; Thu, 11 Dec 2003 14:39:26 -0800 (PST) Received: from citrine.spiritone.com (citrine.spiritone.com [216.99.193.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DFB543E46 for ; Thu, 11 Dec 2003 14:21:06 -0800 (PST) (envelope-from henryt_NOSPAM@aracnet.com) Received: from aracnet.com (216-99-194-252.dial.spiritone.com [216.99.194.252]) (authenticated bits=0)hBBMVTXw013965; Thu, 11 Dec 2003 14:31:37 -0800 Message-ID: <3FD8EEA3.3060508@aracnet.com> Date: Thu, 11 Dec 2003 14:24:35 -0800 From: henry tieman User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031124 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stephane Bortzmeyer References: <20031207163127.GA791@fetiche.sources.org> In-Reply-To: <20031207163127.GA791@fetiche.sources.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-mobile@freebsd.org Subject: Re: X freezes my Sony Vaio PCG-F801 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 22:39:26 -0000 I have only seen 2 kinds of errors crash FreeBSD - bad device drivers and bad memory. Have you tried a memory checker like MemTest86 or MemMXTest? The default memory boot memory test is almost completely useless. I don't know much about MemMXTest but I have used MemTest86 several times. MemTest86 takes a long time to run - think hours. I had a machine with bad ram and I could run for about an hour before I saw any memory errors. MemTest86 ran for about 1 1/2 hours and said I had 8 bad bits at about 480meg on a 512meg dimm. Henry Stephane Bortzmeyer wrote: >On a Sony Vaio PCG-F801, I installed FreeBSD 5.1-RELEASE, which comes >with Xfree 4.3.0. > >When I work in console mode, the machine is OK. I can spend hours >editing texts with Emacs without problems. > >When I use X, edition with Emacs makes the machine freezes after ten >or twenty minutes of use. The cursor no longer moves, Crtl-Alt-F1 and >Ctrl-Alt-Backspace are ignored. I have to reboot the hard way. > >It seems that the problem only occurs with Emacs. If I spend my time >surfing with Mozilla, I do not have the problem, may be because I do >not type. > >I attached the XFree86 log, hoping it is not too large. > > -- Henry Tieman Objects in the mirror are closer than they appear. From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 11 14:39:27 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C980A16A4CF for ; Thu, 11 Dec 2003 14:39:27 -0800 (PST) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5321343E1C for ; Thu, 11 Dec 2003 14:19:16 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Thu, 11 Dec 2003 14:19:09 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id EEE885D04; Thu, 11 Dec 2003 14:19:03 -0800 (PST) To: "M. Warner Losh" In-Reply-To: Message from "M. Warner Losh" <20031211.132647.55844740.imp@bsdimp.com> Date: Thu, 11 Dec 2003 14:19:03 -0800 From: "Kevin Oberman" Message-Id: <20031211221903.EEE885D04@ptavv.es.net> cc: mobile@freebsd.org Subject: Re: I think I wounded by Prism card X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 22:39:28 -0000 > Date: Thu, 11 Dec 2003 13:26:47 -0700 (MST) > From: "M. Warner Losh" > > In message: <20031211182330.0D26C5D04@ptavv.es.net> > "Kevin Oberman" writes: > : > : I have an IBM ThinkPad T30 running CURRENT as of 12/9/03. On that day I > : also updated the firmware on my WiFi card from 1.3.6 to 1.4.9 and my > : troubles began. My wireless card starts and associated normally and runs > : fine until I start a large transfer (such as an scp of a file of a MB or > : so). Then I get the dreaded: > : wi0: timeout in wi_cmd -x010b; event status 0x8000 > > That sucks. I assume no other wi messages before that? And that the > - is really a 0 and you typed it in by hand. Was this under heavy > load? Yes. I hand transcribed and clearly had my finger off by one. > > : At this point the card is dead and I have only been able to recover by > : rebooting the system. > > damn. > > : I will try backing out the recent changes to if_wi > : and rebuild the module ASAP, but I only have wireless available at home, > : so that won't be until tonight. > > I wish I'd seen this earlier, I just committed something to > releng_5_2. You might try hard wiring it or something similar. Unfortunately, I only saw it last night. I've been working late and had not booted my laptop on the wireless for several days. > > : First, any idea as to whether the recent fixes to wi to correct timeouts > : in old firmware versions might have caused this? Or is it a problem with > : 1.4 firmware? If it is the firmware, is there any place to find the old > : firmware to back it off? > > http://www.netgate.com/ has old images. Cool! Just what I was looking for. (Not that I've found them at the site, yet, but I have just started looking around the site. (Just found them!) > : wi0: mem 0xf8000000-0xf8000fff irq 11 at device 2.0 on pci2 > : wi0: 802.11 address 00:05:3c:02:43:2d > : wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) > : wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9) > : wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > > This should be a fairly good card to have. It's always worked pretty well until last night. :-( My only prior issue was locking up when I had the card active but no signal. That made it lock up fairly often, so I now just load the driver when I need it. I'll know more tomorrow when I have backed out the timeout adjustments (which don't look likely to be the cause of the problem). 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 From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 11 17:04:43 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61BB316A4D8 for ; Thu, 11 Dec 2003 17:04:43 -0800 (PST) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33F9243D32 for ; Thu, 11 Dec 2003 17:04:40 -0800 (PST) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (blackwater.lemis.com [192.109.197.80]) by ozlabs.org (Postfix) with ESMTP id 9460C2BD4D for ; Fri, 12 Dec 2003 12:04:36 +1100 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id C5A4751206; Fri, 12 Dec 2003 11:34:34 +1030 (CST) Date: Fri, 12 Dec 2003 11:34:34 +1030 From: Greg 'groggy' Lehey To: "M. Warner Losh" Message-ID: <20031212010434.GY81968@wantadilla.lemis.com> References: <20031211182330.0D26C5D04@ptavv.es.net> <20031211.132647.55844740.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8M+BMcg+0CmQ2H7L" Content-Disposition: inline In-Reply-To: <20031211.132647.55844740.imp@bsdimp.com> User-Agent: Mutt/1.4.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: mobile@freebsd.org Subject: Still problems with Lucent wi0 (was: I think I wounded by Prism card) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 01:04:43 -0000 --8M+BMcg+0CmQ2H7L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thursday, 11 December 2003 at 13:26:47 -0700, M. Warner Losh wrote: > In message: <20031211182330.0D26C5D04@ptavv.es.net> > "Kevin Oberman" writes: >> >> I have an IBM ThinkPad T30 running CURRENT as of 12/9/03. On that day I >> also updated the firmware on my WiFi card from 1.3.6 to 1.4.9 and my >> troubles began. My wireless card starts and associated normally and runs >> fine until I start a large transfer (such as an scp of a file of a MB or >> so). Then I get the dreaded: >> wi0: timeout in wi_cmd -x010b; event status 0x8000 > > That sucks. I assume no other wi messages before that? And that the > - is really a 0 and you typed it in by hand. Was this under heavy > load? FWIW, another data point. At some point in the last few months my last problems with Lucent cards went away, I thought. Then I put a different card in and had problems again: the boot wouldn't complete. Here are the results of the two probes: Dec 12 11:04:06 adelaide kernel: wi0: at port 0x100-0x13f irq 10 function 0 config 1 on pccard0 Dec 12 11:04:06 adelaide kernel: wi0: 802.11 address: 00:02:2d:04:09:3a Dec 12 11:04:06 adelaide kernel: wi0: using Lucent Technologies, WaveLAN/IEEE Dec 12 11:04:06 adelaide kernel: wi0: Lucent Firmware: Station (6.6.1) Dec 12 11:04:06 adelaide kernel: wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Dec 12 11:04:06 adelaide kernel: wi0: bad alloc 4c2 != ff, cur 0 nxt 0 Despite the error message, this card works fine. The other one is: Dec 11 11:49:14 adelaide kernel: wi0: 802.11 address: 00:02:2d:28:d3:6e Dec 11 11:49:14 adelaide kernel: wi0: using Lucent Technologies, WaveLAN/IEEE Dec 11 11:49:14 adelaide kernel: wi0: Lucent Firmware: Station (6.16.1) Dec 11 11:49:14 adelaide kernel: wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Dec 11 11:49:23 adelaide kernel: wi0: bad alloc 1cd != ea, cur 0 nxt 0 Dec 11 11:49:27 adelaide kernel: wi0: bad alloc 633 != 1e3, cur 0 nxt 0 This one continues with messages like: Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_cmd 0x0002; event status 0x8080 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_cmd 0x0121; event status 0x8080 Dec 12 11:26:40 adelaide kernel: wi0: wi_cmd: busy bit won't clear. Dec 12 11:26:40 adelaide last message repeated 11 times Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc0e/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc85/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc20/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc80/0 Dec 12 11:26:40 adelaide kernel: wi0: wi_cmd: busy bit won't clear. This continues until I remove the card, when I get Dec 12 11:26:40 adelaide kernel: wi0: failed to allocate 2372 bytes on NIC Dec 12 11:26:40 adelaide kernel: wi0: tx buffer allocation failed (error 12) Dec 12 11:26:40 adelaide kernel: wi0: interface not running Dec 12 11:26:40 adelaide kernel: wi0: wi_cmd: busy bit won't clear. Dec 12 11:26:40 adelaide kernel: wi0: wi_cmd: busy bit won't clear. Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc00/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc81/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc0c/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc02/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc03/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc04/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc01/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc09/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc07/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc83/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc06/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc25/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc84/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc0e/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc85/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc20/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc80/0 Dec 12 11:26:40 adelaide kernel: wi0: wi_cmd: busy bit won't clear. Dec 12 11:26:40 adelaide kernel: wi0: failed to allocate 2372 bytes on NIC Dec 12 11:26:40 adelaide kernel: wi0: tx buffer allocation failed (error 12) Dec 12 11:26:40 adelaide kernel: wi0: interface not running Dec 12 11:26:40 adelaide kernel: wi0: wi_cmd: busy bit won't clear. Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc80/0 Dec 12 11:26:40 adelaide kernel: wi0: detached After the final message, the system unlocks. Apart from the different firmware level, the second card has only 40 bit WEP, while the first one has 104 bit WEP. I'm not too fussed about the situation, since the gold card works fine, but if you want me to try something out, I can do so. Greg -- See complete headers for address and phone numbers. --8M+BMcg+0CmQ2H7L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/2RQiIubykFB6QiMRAsr/AJ4mKkv/9TvyQxaDHWyo45di9I/KfgCfakCD fA+aFhC5CZ/zqR43bQyraIg= =8unQ -----END PGP SIGNATURE----- --8M+BMcg+0CmQ2H7L-- From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 11 17:15:47 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74C8A16A4D2; Thu, 11 Dec 2003 17:15:47 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id F403143D09; Thu, 11 Dec 2003 17:15:45 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id hBC1FV5h011364; Thu, 11 Dec 2003 18:15:31 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 11 Dec 2003 18:12:41 -0700 (MST) Message-Id: <20031211.181241.58839617.imp@bsdimp.com> To: grog@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <20031212010434.GY81968@wantadilla.lemis.com> References: <20031211182330.0D26C5D04@ptavv.es.net> <20031211.132647.55844740.imp@bsdimp.com> <20031212010434.GY81968@wantadilla.lemis.com> X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: mobile@FreeBSD.org Subject: Re: Still problems with Lucent wi0 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 01:15:47 -0000 Are you runnign current? The 'bad alloc' stuff was fixed a little while ago. Warner From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 11 17:25:41 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BF1B16A4CF for ; Thu, 11 Dec 2003 17:25:41 -0800 (PST) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6303E43D42 for ; Thu, 11 Dec 2003 17:25:38 -0800 (PST) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (blackwater.lemis.com [192.109.197.80]) by ozlabs.org (Postfix) with ESMTP id 20CF52BD4C for ; Fri, 12 Dec 2003 12:25:36 +1100 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 6D2EB51206; Fri, 12 Dec 2003 11:55:32 +1030 (CST) Date: Fri, 12 Dec 2003 11:55:32 +1030 From: Greg 'groggy' Lehey To: "M. Warner Losh" Message-ID: <20031212012532.GB81968@wantadilla.lemis.com> References: <20031211182330.0D26C5D04@ptavv.es.net> <20031211.132647.55844740.imp@bsdimp.com> <20031212010434.GY81968@wantadilla.lemis.com> <20031211.181241.58839617.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Ro1PRY3Rtw8g7IwX" Content-Disposition: inline In-Reply-To: <20031211.181241.58839617.imp@bsdimp.com> User-Agent: Mutt/1.4.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: mobile@FreeBSD.org Subject: Re: Still problems with Lucent wi0 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 01:25:41 -0000 --Ro1PRY3Rtw8g7IwX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thursday, 11 December 2003 at 18:12:41 -0700, M. Warner Losh wrote: > Are you runnign current? For some definition of "current", yes. 30 November. > The 'bad alloc' stuff was fixed a little while ago. Yes, I thought so too. I haven't seen any more commits of that nature since then. Should I go to today's current? Greg -- See complete headers for address and phone numbers. --Ro1PRY3Rtw8g7IwX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/2RkMIubykFB6QiMRAkyjAJ9q0/gkIqTZWtX77p2DIpKffY4GiQCbBOdQ G3fWf5IvO2GV4R9/6TnJyhc= =Qo9R -----END PGP SIGNATURE----- --Ro1PRY3Rtw8g7IwX-- From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 11 17:52:16 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2BCB16A4CE; Thu, 11 Dec 2003 17:52:16 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FDB343D33; Thu, 11 Dec 2003 17:52:15 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id hBC1q95h011572; Thu, 11 Dec 2003 18:52:09 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 11 Dec 2003 18:49:21 -0700 (MST) Message-Id: <20031211.184921.67799178.imp@bsdimp.com> To: grog@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <20031212012532.GB81968@wantadilla.lemis.com> References: <20031212010434.GY81968@wantadilla.lemis.com> <20031211.181241.58839617.imp@bsdimp.com> <20031212012532.GB81968@wantadilla.lemis.com> X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: mobile@FreeBSD.org Subject: Re: Still problems with Lucent wi0 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 01:52:17 -0000 In message: <20031212012532.GB81968@wantadilla.lemis.com> "Greg 'groggy' Lehey" writes: : On Thursday, 11 December 2003 at 18:12:41 -0700, M. Warner Losh wrote: : > Are you runnign current? : : For some definition of "current", yes. 30 November. That's not current enough. I committed the fixes for that the next day: imp 2003/12/01 20:59:59 PST FreeBSD src repository Modified files: sys/dev/wi if_wi.c Log: Fix Lucent cards. o Back out workaround for not resetting lucent cards more than once. With these fixes, it appaers they are no longer necessary. o Set wi_gone when the card goes awol: typically when we get 0xffff back from the card. Also, don't interact with a card that's gone, so we fail in seconds rather than minutes. Also reduce amount of time we wait to .5s in wi_cmd. o clear wi_gone on ifconfig down to give some cards a chance after they wedge (this appears to unwedge one of my prism cards with old firmware). ifconfig up will fail quickly enough if the card really is out to lunch. o Add delay in wi_init of 100ms. o wi_stop(ifp, 0->1) changes so that we clear sc_enabled so that we exit out of the interrupt routine by just acking the interrupt Submitted by: iedowse Approved by: re@ (scottl) # after the freeze I'll fix some of the minor style issues that reviewers # of this patch have told me about. Revision Changes Path 1.158 +25 -10 src/sys/dev/wi/if_wi.c : > The 'bad alloc' stuff was fixed a little while ago. : : Yes, I thought so too. I haven't seen any more commits of that nature : since then. Should I go to today's current? Yes. It should be much better. Warner From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 11 21:25:19 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E53A816A4CF for ; Thu, 11 Dec 2003 21:25:19 -0800 (PST) Received: from idiom.com (idiom.com [216.240.32.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C30443D32 for ; Thu, 11 Dec 2003 21:25:19 -0800 (PST) (envelope-from druid45@idiom.com) Received: from idiom.com (216-240-38-214.ip.idiom.com [216.240.38.214]) by idiom.com (8.12.9p2/8.12.9) with ESMTP id hBC5PFCa098618 for ; Thu, 11 Dec 2003 21:25:17 -0800 (PST) (envelope-from druid45@idiom.com) Message-ID: <3FD92658.9040302@idiom.com> Date: Thu, 11 Dec 2003 21:22:16 -0500 From: Chris Neustrup User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Vaio 505GL PC-CARD (pccardd) problmes X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 05:25:20 -0000 Warner wrote... > In message: <20030805011859.M5601 at collins-ca.com> > "Chris Collins" writes: > : My linksys WPC11 card works now... However the WPC54G does not... I > get the > : following error message when I put teh 54G in.. Do you have anymore > ticks up > : your sleve that might help me out... :) I might be wrong but I don't > think > : there is any support yet for the Linksys 54G card. > : > : Aug 4 21:25:37 vaio kernel: cardbus0: at device 0.0 (no > > driver > : attached) > > No support yet. Need to write a driver for the prism G chipset. > > Warner Is there any further progress on this driver? I would very musch like 1) to get one, or 2) to write or cobble one together. I can do device drivers on FreeBSD boxes, although not recently. I would be very very happy to help with this if its not yet available. Peace, Chris From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 11 22:33:40 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29F5316A4CE for ; Thu, 11 Dec 2003 22:33:40 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB52943D36 for ; Thu, 11 Dec 2003 22:33:38 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id hBC6Xb3u001342; Thu, 11 Dec 2003 23:33:37 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 11 Dec 2003 23:30:11 -0700 (MST) Message-Id: <20031211.233011.40956303.imp@bsdimp.com> To: druid45@idiom.com From: "M. Warner Losh" In-Reply-To: <3FD92658.9040302@idiom.com> References: <3FD92658.9040302@idiom.com> X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-mobile@freebsd.org Subject: Re: Vaio 505GL PC-CARD (pccardd) problmes X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 06:33:40 -0000 In message: <3FD92658.9040302@idiom.com> Chris Neustrup writes: : > No support yet. Need to write a driver for the prism G chipset. : > : > Warner : : Is there any further progress on this driver? I would very musch like : 1) to get one, or 2) to write or cobble one together. I can do device : drivers on FreeBSD boxes, although not recently. I would be very very : happy to help with this if its not yet available. I've had 0 time for endevors such at this. Warner From owner-freebsd-mobile@FreeBSD.ORG Fri Dec 12 01:22:30 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BEDD16A4CE; Fri, 12 Dec 2003 01:22:30 -0800 (PST) Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE00C43D1D; Fri, 12 Dec 2003 01:22:28 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtpzilla2.xs4all.nl (8.12.9/8.12.9) with ESMTP id hBC9MRIG015649; Fri, 12 Dec 2003 10:22:27 +0100 (CET) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.10/8.12.9) with ESMTP id hBC9MQ3k063994; Fri, 12 Dec 2003 10:22:26 +0100 (CET) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.10/8.12.9/Submit) id hBC9MQfH063993; Fri, 12 Dec 2003 10:22:26 +0100 (CET) (envelope-from wkb) Date: Fri, 12 Dec 2003 10:22:26 +0100 From: Wilko Bulte To: John Baldwin Message-ID: <20031212092226.GA63968@freebie.xs4all.nl> References: <20031210213840.GA870@shapeshifter.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-OS: FreeBSD 4.9-STABLE X-PGP: finger wilko@freebsd.org cc: Fredrik Lindberg cc: freebsd-mobile@freebsd.org Subject: Re: ACPI/PCI-bus issue with compaq evo n160 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 09:22:30 -0000 On Thu, Dec 11, 2003 at 01:24:56PM -0500, John Baldwin wrote: > > On 10-Dec-2003 Fredrik Lindberg wrote: > > Hi, > > > > I have a Compaq evo n160 running > > FreeBSD biocandy 5.2-RC FreeBSD 5.2-RC #10: Mon Dec 8 19:08:38 CET 2003 > > > > The machine fails (and always has) to boot with acpi enabled > > (locks up when mounting /), however, I managed to find out that > > booting with the following option > > > > debug.acpi.disable="pci" > > ... > If you can drop into ddb and do a 'show intrcnt' when the machine > locks up that might help fix the hang. It sounds like the interrupt > routing may not have worked correctly. Also, a dmesg of acpi > with pci enabled would be helpful. I for one was never able to get anywhere when the 'mount / lockup' occured :-( I hope Fredrik fares better here.. And this machine does not have a serial port (well, it does, but you need a docking station to get access to it; a ds I do not own). -- | / o / /_ _ |/|/ / / /( (_) Bulte wilko@FreeBSD.org From owner-freebsd-mobile@FreeBSD.ORG Fri Dec 12 01:45:09 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29D0C16A4CE for ; Fri, 12 Dec 2003 01:45:09 -0800 (PST) Received: from mail-aubervilliers.netaktiv.com (soyouz.netaktiv.com [80.67.170.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBB4743D33 for ; Fri, 12 Dec 2003 01:45:06 -0800 (PST) (envelope-from stephane@laperouse.internatif.org) Received: by mail-aubervilliers.netaktiv.com (Postfix, from userid 10) id AC363240C9; Fri, 12 Dec 2003 10:45:06 +0100 (CET) Received: by fetiche.sources.org (Postfix, from userid 1001) id E11B79AD0; Thu, 11 Dec 2003 19:51:16 +0430 (AFT) Date: Thu, 11 Dec 2003 19:51:16 +0430 From: Stephane Bortzmeyer To: d.wylie@hccnet.nl Message-ID: <20031211152116.GA1086@fetiche.sources.org> References: <200312111146.hBBBkM2W004015@smtp.hccnet.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200312111146.hBBBkM2W004015@smtp.hccnet.nl> User-Agent: Mutt/1.4.1i X-Transport: UUCP rules X-Operating-System: FreeBSD 5.1-RELEASE i386 cc: freebsd-mobile@freebsd.org cc: stephane@laperouse.internatif.org Subject: Re: X freezes my Sony Vaio PCG-F801 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 09:45:09 -0000 On Thu, Dec 11, 2003 at 11:46:22AM +0000, d.wylie@hccnet.nl wrote a message of 28 lines which said: > Which same problem; freeze or lib? Freeze, unfortunately. > vesa solves my freeze. Not mine :-( From owner-freebsd-mobile@FreeBSD.ORG Fri Dec 12 02:12:02 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13A1A16A4CE for ; Fri, 12 Dec 2003 02:12:02 -0800 (PST) Received: from arbornet.org (m-net.arbornet.org [209.142.209.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 719F243D36 for ; Fri, 12 Dec 2003 02:12:00 -0800 (PST) (envelope-from lei@m-net.arbornet.org) Received: from m-net.arbornet.org (localhost [127.0.0.1]) by arbornet.org (8.12.3p2/8.11.2) with ESMTP id hBCAFfDr061679 for ; Fri, 12 Dec 2003 05:15:41 -0500 (EST) (envelope-from lei@m-net.arbornet.org) Received: from localhost (lei@localhost)hBCAFf74061674 for ; Fri, 12 Dec 2003 05:15:41 -0500 (EST) Date: Fri, 12 Dec 2003 05:15:39 -0500 (EST) From: Lei Z To: freebsd-mobile@FreeBSD.ORG In-Reply-To: <20031209232514.W39190@sasami.jurai.net> Message-ID: <20031212044810.J41983-100000@m-net.arbornet.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Has anyone tried this trick? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 10:12:02 -0000 Thanks for all the inputs. I have contacted HP technical support by email. They suggested that the BIOS information should be updated to reflect the new hard disk parameter, which could have changed, through a sequence of function keys after cold boot. I will try it, and also PXE boot, when I find time. As I can always set up a primary DOS partition (FAT32 with DOS only) on desktop and boot up the notebook with it with no problem (weird ?), I have put a copy of zipslack on it, created e2fs on /dev/hda5 with it from the notebook, and moved the linux to the extended partition. X is running fine as expected and I boot into linux using loadlin now. So the trick could be that I need to clear up the partition table first, run fdisk, and create the file systems all on the notebook, using the BIOS parameters. BSD's might have a better chance than other OS's to get around this as it relies less on the BIOS disk setting. Thanks again to the folks who have given their input. Lei From owner-freebsd-mobile@FreeBSD.ORG Fri Dec 12 06:29:00 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D54416A4CE for ; Fri, 12 Dec 2003 06:29:00 -0800 (PST) Received: from biocandy.shapeshifter.se (h125n2fls31o270.telia.com [217.208.199.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id E561C43D32 for ; Fri, 12 Dec 2003 06:28:57 -0800 (PST) (envelope-from NOfreddeSPAM@shapeshifter.se) Received: from biocandy.shapeshifter.se (localhost [127.0.0.1]) hBCESukZ000876 for ; Fri, 12 Dec 2003 15:28:56 +0100 (CET) (envelope-from NOfreddeSPAM@shapeshifter.se) Received: (from fredde@localhost) by biocandy.shapeshifter.se (8.12.10/8.12.10/Submit) id hBCESu8R000875 for freebsd-mobile@freebsd.org; Fri, 12 Dec 2003 15:28:56 +0100 (CET) (envelope-from NOfreddeSPAM@shapeshifter.se) X-Authentication-Warning: biocandy.shapeshifter.se: fredde set sender to NOfreddeSPAM@shapeshifter.se using -f Date: Fri, 12 Dec 2003 15:28:56 +0100 From: Fredrik Lindberg To: freebsd-mobile@freebsd.org Message-ID: <20031212142856.GA859@shapeshifter.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: ACPI/PCI-bus issue with compaq evo n160 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 14:29:00 -0000 Hi, Thank you for your reply. The information you requested is avaiable at http://shapeshifter.se/~fredde/tmp/db http://shapeshifter.se/~fredde/tmp/dmesg.acpi-pci.enabled Fredrik On Thu, Dec 11, 2003 at 01:42:06PM -0500, John Baldwin (jhb@FreeBSD.org) wrote: > [ Resent due to NO.*SPAM bounce the first time ] > > On 10-Dec-2003 Fredrik Lindberg wrote: > > Hi, > > > > I have a Compaq evo n160 running > > FreeBSD biocandy 5.2-RC FreeBSD 5.2-RC #10: Mon Dec 8 19:08:38 CET 2003 > > > > The machine fails (and always has) to boot with acpi enabled > > (locks up when mounting /), however, I managed to find out that > > booting with the following option > > > > debug.acpi.disable="pci" > > > > in /boot/loader.conf made the machine boot correctly and acpi related > > functions such as battry monitoring worked just fine. > > > > But, and a huge but, no pci devices are detected during boot > > (maybe quite obvious because of that debug option) > > All pci-devices works perfectly with acpi disabled. > > > > Now, is there any chance to make freebsd use acpi and the > > "normal" pci-bus driver at the same time, overriding the > > acpi pci-bus implementation? > > > > I believe linux has a kernel option called pci=noacpi (atleast acording to google), > > which does this. > > > > With acpi enabled scanpci reports all the pci devices, but pciconf -l > > doesn't return anything. > > With acpi disabled, scanpci reports all pci devices, pciconf -l > > reports all devices. > > > > dmesg output with acpi enabled > > http://shapeshifter.se/~fredde/tmp/dmesg.acpi.enabled > > > > dmesg out with acpi disabled > > http://shapeshifter.se/~fredde/tmp/dmesg.acpi.disabled > > > > Any, and I mean any, help on this will be very appreciated. > > If you can drop into ddb and do a 'show intrcnt' when the machine > locks up that might help fix the hang. It sounds like the interrupt > routing may not have worked correctly. Also, a dmesg of acpi > with pci enabled would be helpful. > > -- > > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ ----- End forwarded message ----- From owner-freebsd-mobile@FreeBSD.ORG Fri Dec 12 14:34:21 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4871516A4CE for ; Fri, 12 Dec 2003 14:34:21 -0800 (PST) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D4F143D09 for ; Fri, 12 Dec 2003 14:34:12 -0800 (PST) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (blackwater.lemis.com [192.109.197.80]) by ozlabs.org (Postfix) with ESMTP id A51BD2BD4C for ; Sat, 13 Dec 2003 09:34:09 +1100 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id B4CD951200; Sat, 13 Dec 2003 09:04:06 +1030 (CST) Date: Sat, 13 Dec 2003 09:04:06 +1030 From: Greg 'groggy' Lehey To: "M. Warner Losh" Message-ID: <20031212223406.GC95737@wantadilla.lemis.com> References: <20031212010434.GY81968@wantadilla.lemis.com> <20031211.181241.58839617.imp@bsdimp.com> <20031212012532.GB81968@wantadilla.lemis.com> <20031211.184921.67799178.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GZVR6ND4mMseVXL/" Content-Disposition: inline In-Reply-To: <20031211.184921.67799178.imp@bsdimp.com> User-Agent: Mutt/1.4.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: mobile@FreeBSD.org Subject: Re: Still problems with Lucent wi0 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 22:34:21 -0000 --GZVR6ND4mMseVXL/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thursday, 11 December 2003 at 18:49:21 -0700, M. Warner Losh wrote: > In message: <20031212012532.GB81968@wantadilla.lemis.com> > "Greg 'groggy' Lehey" writes: >> On Thursday, 11 December 2003 at 18:12:41 -0700, M. Warner Losh wrote: >>> Are you runnign current? >> >> For some definition of "current", yes. 30 November. > > That's not current enough. I committed the fixes for that the next > day: > > imp 2003/12/01 20:59:59 PST > ... Oops, missed that one. >>> The 'bad alloc' stuff was fixed a little while ago. >> >> Yes, I thought so too. I haven't seen any more commits of that nature >> since then. Should I go to today's current? > > Yes. It should be much better. Done. And you're right: no problems with either card. Sorry for the noise. Greg -- See complete headers for address and phone numbers. --GZVR6ND4mMseVXL/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/2kJeIubykFB6QiMRAoOiAJ4tnF/3CapE7/lIRVCJF+t0lR2mqgCfT88Z bmOuu4cTnmss5oGu1Vju3Ng= =E4Do -----END PGP SIGNATURE----- --GZVR6ND4mMseVXL/-- From owner-freebsd-mobile@FreeBSD.ORG Fri Dec 12 16:23:31 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D60D16A4D0; Fri, 12 Dec 2003 16:23:31 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33F2243D2D; Fri, 12 Dec 2003 16:23:29 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id hBD0NN1p000465; Fri, 12 Dec 2003 17:23:23 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 12 Dec 2003 17:19:23 -0700 (MST) Message-Id: <20031212.171923.09280015.imp@bsdimp.com> To: grog@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <20031212223406.GC95737@wantadilla.lemis.com> References: <20031212012532.GB81968@wantadilla.lemis.com> <20031211.184921.67799178.imp@bsdimp.com> <20031212223406.GC95737@wantadilla.lemis.com> X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: mobile@FreeBSD.org Subject: Re: Still problems with Lucent wi0 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2003 00:23:31 -0000 In message: <20031212223406.GC95737@wantadilla.lemis.com> "Greg 'groggy' Lehey" writes: : >>> The 'bad alloc' stuff was fixed a little while ago. : >> : >> Yes, I thought so too. I haven't seen any more commits of that nature : >> since then. Should I go to today's current? : > : > Yes. It should be much better. : : Done. And you're right: no problems with either card. Sorry for the : noise. No problem. Warner From owner-freebsd-mobile@FreeBSD.ORG Fri Dec 12 20:05:09 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DCCE16A4CF for ; Fri, 12 Dec 2003 20:05:09 -0800 (PST) Received: from mail-aubervilliers.netaktiv.com (soyouz.netaktiv.com [80.67.170.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id A08EA43D1F for ; Fri, 12 Dec 2003 20:05:06 -0800 (PST) (envelope-from stephane@laperouse.internatif.org) Received: by mail-aubervilliers.netaktiv.com (Postfix, from userid 10) id A159724298; Sat, 13 Dec 2003 05:05:05 +0100 (CET) Received: by fetiche.sources.org (Postfix, from userid 1001) id 65EDB9AD2; Fri, 12 Dec 2003 21:45:30 +0430 (AFT) Date: Fri, 12 Dec 2003 21:45:30 +0430 From: Stephane Bortzmeyer To: henry tieman Message-ID: <20031212171530.GH1367@fetiche.sources.org> References: <20031207163127.GA791@fetiche.sources.org> <3FD8EEA3.3060508@aracnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FD8EEA3.3060508@aracnet.com> User-Agent: Mutt/1.4.1i X-Transport: UUCP rules X-Operating-System: FreeBSD 5.1-RELEASE i386 cc: freebsd-mobile@freebsd.org cc: Stephane Bortzmeyer Subject: Re: X freezes my Sony Vaio PCG-F801 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2003 04:05:09 -0000 On Thu, Dec 11, 2003 at 02:24:35PM -0800, henry tieman wrote a message of 38 lines which said: > I have only seen 2 kinds of errors crash FreeBSD - bad device drivers > and bad memory. Formally speaking, it doesn't crash, it freezes. But you're right, not only the Xfree server is down, the machine stops replying to ping also, which seems to indicate that the kernel (or the PCI bus) was frozen. > Have you tried a memory checker like MemTest86 or MemMXTest? No defect detected yet, still running. From owner-freebsd-mobile@FreeBSD.ORG Sat Dec 13 07:46:27 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F4EE16A4CE for ; Sat, 13 Dec 2003 07:46:27 -0800 (PST) Received: from freek.com (freek.com [206.252.131.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45FE843D35 for ; Sat, 13 Dec 2003 07:46:26 -0800 (PST) (envelope-from dorqus@freek.com) Received: by freek.com (Postfix, from userid 1000) id 8D0349E789; Sat, 13 Dec 2003 10:46:25 -0500 (EST) Date: Sat, 13 Dec 2003 10:46:25 -0500 From: josh To: freebsd-mobile@freebsd.org Message-ID: <20031213154625.GA32034@freek.com> References: <20031207163127.GA791@fetiche.sources.org> <3FD8EEA3.3060508@aracnet.com> <20031212171530.GH1367@fetiche.sources.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031212171530.GH1367@fetiche.sources.org> User-Agent: Mutt/1.4.1i Subject: Re: X freezes my Sony Vaio PCG-F801 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2003 15:46:27 -0000 Stephane Bortzmeyer wrote... > Formally speaking, it doesn't crash, it freezes. But you're right, not > only the Xfree server is down, the machine stops replying to ping > also, which seems to indicate that the kernel (or the PCI bus) was > frozen. This also happens to me on my Thinkpad R32 if I reboot from WinXP and go into FreeBSD and start X, the laptop just freezes, cannot be reached over the network and I have to remove the battery. However, if I shut down the computer from XP, then start FreeBSD, X works just fine for me. I don't think it's a FreeBSD specific issue, as it did the same thing with both OpenBSD and Debian Linux installed - I *had* to power off the computer when going from WinXP into FreeBSD. I'm not sure if a warm boot of FreeBSD will cause the same behaviour, so just to be safe I always just power it off. On another note, I can't seem to get the laptop to suspend at all. It does suspend under X using "apm -z" but then when I turn it back on, the display gets all funky and the laptop needs to be powered off and the battery removed. If I do 'acpiconf -s 5' the box just shuts down. *shrug* so for now I just close the lid, at least that kind of blanks the display. josh From owner-freebsd-mobile@FreeBSD.ORG Sat Dec 13 18:17:24 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33F0616A4CE for ; Sat, 13 Dec 2003 18:17:24 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29D4743D58 for ; Sat, 13 Dec 2003 18:17:19 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id hBE2HGEJ013318; Sat, 13 Dec 2003 19:17:16 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 13 Dec 2003 19:13:11 -0700 (MST) Message-Id: <20031213.191311.110244758.imp@bsdimp.com> To: stephane@laperouse.internatif.org From: "M. Warner Losh" In-Reply-To: <20031212171530.GH1367@fetiche.sources.org> References: <20031207163127.GA791@fetiche.sources.org> <3FD8EEA3.3060508@aracnet.com> <20031212171530.GH1367@fetiche.sources.org> X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-mobile@freebsd.org Subject: Re: X freezes my Sony Vaio PCG-F801 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2003 02:17:24 -0000 In message: <20031212171530.GH1367@fetiche.sources.org> Stephane Bortzmeyer writes: : On Thu, Dec 11, 2003 at 02:24:35PM -0800, : henry tieman wrote : a message of 38 lines which said: : : > I have only seen 2 kinds of errors crash FreeBSD - bad device drivers : > and bad memory. : : Formally speaking, it doesn't crash, it freezes. But you're right, not : only the Xfree server is down, the machine stops replying to ping : also, which seems to indicate that the kernel (or the PCI bus) was : frozen. I've seen similar things on my VAIO PCG-505TS. I believe that it is some kind of hang, since if it were an interrupt storm it would still reply to pings (at least in 5.x that's what I've observed). Warner