Date: Sun, 27 Jul 2003 20:49:55 -0700 From: Karl Agee <kdagee@owt.com> To: "Greg 'groggy' Lehey" <grog@lemis.com> Cc: FreeBSD Questions <questions@FreeBSD.org> Subject: Re: laptop question for this or the mobile group? Message-ID: <5.1.0.14.0.20030727204408.030b0af0@pop3.owt.com> In-Reply-To: <20030728032318.GO45069@wantadilla.lemis.com> References: <5.1.0.14.0.20030727190858.030af838@pop3.owt.com> <5.1.0.14.0.20030724214606.026ee978@pop3.owt.com> <5.1.0.14.0.20030724214606.026ee978@pop3.owt.com> <5.1.0.14.0.20030727190858.030af838@pop3.owt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=======49C345F======= Content-Type: text/plain; x-avg-checked=avg-ok-586C6D77; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable At 12:53 PM 7/28/2003 +0930, Greg 'groggy' Lehey wrote: >On Sunday, 27 July 2003 at 19:15:57 -0700, Karl Agee wrote: > > At 11:10 AM 7/27/2003 +0930, you wrote: > > > >> On Thursday, 24 July 2003 at 21:47:23 -0700, Karl Agee wrote: > >>> I am having problems getting X set up properly on a laptop. Should > >>> I post the question here or on the mobile list? > >> > >> Start here, but give some details. If this is a Dell Inspiron 5100, > >> I'm working on it. > > > > Hi Greg and all: > >You forgot to copy "and all". I'm doing it now. > > > Laptop: Thinkpad iSeries 1300 > > Video: Silicon Motion LynxEM+ chip > > Screen: 800x600 hpa > > > > system: FreeBSD 4.8-RELEASE > > > > Only the vga driver works, and not very well. Gives me only a 640x480 > > display and the windows etc are not displayed properly (too large for= the > > display). > >That's a window manager issue. Well, both twm and windowmaker do it.........havent tried kde, gnome. > > This setup was configured using either xf86config or xf86cfg > > -textmode. Using the "autodetect" selection froze the display, as > > does trying to setup manually using the above and the silicon motion > > driver. Killing X server doesnt work, have to reboot the machine. > >Hmm. Anything unusual in /var/log/XFree86.0.log? I had this recently: > > (=3D=3D) RADEON(0): Write-combining range (0xc0000,0x40000) was already= clear > (WW) RADEON(0): Bad V_BIOS checksum > (II) RADEON(0): Primary V_BIOS segment is: 0xc000 > (=3D=3D) RADEON(0): Write-combining range (0x0,0x1000) was already= clear > (--) RADEON(0): Chipset: "ATI Radeon Mobility M7 LW (AGP)" (ChipID =3D= =20 > 0x4c57) > (--) RADEON(0): Linear framebuffer at 0xf0000000 > (--) RADEON(0): MMIO registers at 0xe0100000 > (=3D=3D) RADEON(0): Write-combining range (0xe0100000,0x80000) was= already=20 > clear > (--) RADEON(0): VideoRAM: 16384 kByte (64-bit DDR SDRAM) > (=3D=3D) RADEON(0): Write-combining range (0xe0100000,0x80000) was= already=20 > clear > (II) RADEON(0): CloneDisplay option not set -- defaulting to= auto-detect > (II) RADEON(0): Primary Display =3D=3D Type 2 > (II) RADEON(0): Panel ID string: =FF=FF=FF=FF=FF=FF=FF=FF=FF=FF=FF=FF= =FF=FF=FF=FF=FF=FF=FF=FF=FF=FF=FF=FF > (II) RADEON(0): Panel Size from BIOS: 65535x65535 > > *** If unresolved symbols were reported above, they might not > *** be the reason for the server aborting. > > Fatal server error: > Caught signal 11. Server aborting > >This was on a Dell Inspiron 5100, and it's caused by incorrect mapping >of the video BIOS. It would be interesting to see if you're having a >similar problem. well, I dont see anything like that, but, now it is crashing with the same= =20 message. But, it says: "(II) Silicon Motion(0): U2C device "I2C bus:SAA 7111A" registered at=20 address 0x48. "(II) Silicon Motion(0): U2C device "I2C bus:SAA 7111A" removed. ***If unresolved symbols were reported above......(wont repeat it you know= =20 what the rest is I am sure) Fatal Server Error: Caught Signal 11 Server Aborting. that is where it crashes. --karl > > This notebook works fine with suse 8.1, Red Hat 9, Knoppix 3.1, etc. > >I also tried my laptop with Knoppix 3.1, and it worked fine. It's >obviously a FreeBSD problem, and I'm currently trying to localize it. > > > I did notice the XF86Config file is the old XFree 3.x series format, > > apparently not the newer series 4.x format. (dont know if that is > > significant). > >Depends on where it came from. The log file is more interesting, and >it'll tell you which of the myriad possible config files it uses. > >Greg >-- >Finger grog@lemis.com for PGP public key >See complete headers for address and phone numbers > --=======49C345F=======--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.1.0.14.0.20030727204408.030b0af0>