Re: Fwd: Re: laptop question for this or the mobile group?
Hello Have you tried to using the XF86Config file from your Linux computer? You will need to disable the dri stuff, make sure all the font paths are the same. On Sunday 27 July 2003 08:39 pm, Karl Agee wrote: Date: Sun, 27 Jul 2003 19:15:57 -0700 To: Greg 'groggy' Lehey [EMAIL PROTECTED] From: Karl Agee [EMAIL PROTECTED] Subject: Re: laptop question for this or the mobile group? Hi Greg and all: 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). 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. This notebook works fine with suse 8.1, Red Hat 9, Knoppix 3.1, etc. 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). --karl 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. Greg -- See complete headers for address and phone numbers ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Fwd: Re: laptop question for this or the mobile group?
Date: Sun, 27 Jul 2003 19:15:57 -0700 To: Greg 'groggy' Lehey [EMAIL PROTECTED] From: Karl Agee [EMAIL PROTECTED] Subject: Re: laptop question for this or the mobile group? Hi Greg and all: 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). 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. This notebook works fine with suse 8.1, Red Hat 9, Knoppix 3.1, etc. 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). --karl 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. Greg -- See complete headers for address and phone numbers ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: laptop question for this or the mobile group?
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. 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: (==) RADEON(0): Write-combining range (0xc,0x4) was already clear (WW) RADEON(0): Bad V_BIOS checksum (II) RADEON(0): Primary V_BIOS segment is: 0xc000 (==) RADEON(0): Write-combining range (0x0,0x1000) was already clear (--) RADEON(0): Chipset: ATI Radeon Mobility M7 LW (AGP) (ChipID = 0x4c57) (--) RADEON(0): Linear framebuffer at 0xf000 (--) RADEON(0): MMIO registers at 0xe010 (==) RADEON(0): Write-combining range (0xe010,0x8) was already clear (--) RADEON(0): VideoRAM: 16384 kByte (64-bit DDR SDRAM) (==) RADEON(0): Write-combining range (0xe010,0x8) was already clear (II) RADEON(0): CloneDisplay option not set -- defaulting to auto-detect (II) RADEON(0): Primary Display == Type 2 (II) RADEON(0): Panel ID string: (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. 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 [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: laptop question for this or the mobile group?
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: (==) RADEON(0): Write-combining range (0xc,0x4) was already clear (WW) RADEON(0): Bad V_BIOS checksum (II) RADEON(0): Primary V_BIOS segment is: 0xc000 (==) RADEON(0): Write-combining range (0x0,0x1000) was already clear (--) RADEON(0): Chipset: ATI Radeon Mobility M7 LW (AGP) (ChipID = 0x4c57) (--) RADEON(0): Linear framebuffer at 0xf000 (--) RADEON(0): MMIO registers at 0xe010 (==) RADEON(0): Write-combining range (0xe010,0x8) was already clear (--) RADEON(0): VideoRAM: 16384 kByte (64-bit DDR SDRAM) (==) RADEON(0): Write-combining range (0xe010,0x8) was already clear (II) RADEON(0): CloneDisplay option not set -- defaulting to auto-detect (II) RADEON(0): Primary Display == Type 2 (II) RADEON(0): Panel ID string: (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 message. But, it says: (II) Silicon Motion(0): U2C device I2C bus:SAA 7111A registered at address 0x48. (II) Silicon Motion(0): U2C device I2C bus:SAA 7111A removed. ***If unresolved symbols were reported above..(wont repeat it you know 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 [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
more Re: laptop question for this or the mobile group?
Ok, I just made a change to the monitor setting.and it froze up like before. Here is the log message: (II) Silicon Motion(0): Primary V_BIOS segment is: 0xc000 (II) Silicon Motion(0): Write-combining range (0x0, 0x1000) was already clear (II) Silicon Motion(0): Current Mode 0x00 (II) Silicon Motion(0): SMI_GEReset called from smi_driver.c line 1559 (II) Silicon Motion(0): SMI_GEReset called from smi_driver.c line 263 #above line repeated many times --karl ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: laptop question for this or the mobile group?
[Format recovered--see http://www.lemis.com/email/email-format.html] Quoted text inappropriately wrapped. On Sunday, 27 July 2003 at 20:49:55 -0700, Karl Agee wrote: 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: 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. They'll do it too. Nobody expects a 640x480 maximum resolution. 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: ... 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 message. But, it says: (II) Silicon Motion(0): U2C device I2C bus:SAA 7111A registered at address 0x48. (II) Silicon Motion(0): U2C device I2C bus:SAA 7111A removed. It looks as if you have trimmed too much. Look for lines starting with (WW) and (EE). ***If unresolved symbols were reported above..(wont repeat it you know what the rest is I am sure) Fatal Server Error: Caught Signal 11 Server Aborting. that is where it crashes. OK, so this looks similar. Take a look in /var/run/dmesg.boot and find a line starting with orm0. I'd be interested to see what it looks like. Also check for any warnings about checksum mismatches in the dmesg.boot. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: more Re: laptop question for this or the mobile group?
[Format recovered--see http://www.lemis.com/email/email-format.html] Computer output wrapped. On Sunday, 27 July 2003 at 21:06:04 -0700, Karl Agee wrote: Ok, I just made a change to the monitor setting.and it froze up like before. Here is the log message: (II) Silicon Motion(0): Primary V_BIOS segment is: 0xc000 (II) Silicon Motion(0): Write-combining range (0x0, 0x1000) was already clear (II) Silicon Motion(0): Current Mode 0x00 (II) Silicon Motion(0): SMI_GEReset called from smi_driver.c line 1559 (II) Silicon Motion(0): SMI_GEReset called from smi_driver.c line 263 #above line repeated many times There's nothing interesting there. See my other message. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: laptop question for this or the mobile group?
Karl Agee snipped: (II) Silicon Motion(0): U2C device I2C bus:SAA 7111A registered at address 0x48. (II) Silicon Motion(0): U2C device I2C bus:SAA 7111A removed. It looks as if you have trimmed too much. Look for lines starting with (WW) and (EE). (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log File. (==) Using config file.. that is all it says. ***If unresolved symbols were reported above..(wont repeat it you know what the rest is I am sure) Fatal Server Error: Caught Signal 11 Server Aborting. that is where it crashes. OK, so this looks similar. Take a look in /var/run/dmesg.boot and find a line starting with orm0. I'd be interested to see what it looks like. orm0: Option ROM at iomem 0xc-0xcbfff on isa0 Also check for any warnings about checksum mismatches in the dmesg.boot. Nope. no checksum errers. --karl ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: laptop question for this or the mobile group?
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. Greg -- See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
laptop question for this or the mobile group?
I am having problems getting X set up properly on a laptop. Should I post the question here or on the mobile list? --karl ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
