Re: huge xfree86 problems with an acer on freebsd 5.2.1

2004-05-30 Thread Jorn Argelo
[EMAIL PROTECTED] wrote:
Hi, i already posted this on x11 but hey i really need help so please don't hold it 
against me...
I have an acer aspire 1350LC with a via chipset for the graphics. I got x working once 
on 4.9, same laptop when i had been messing around with 4.4.0 and ports so after a 
while it was a really broken install but suddenly it started working using the auto 
configure thing, first thing i tried to do was to write my own conf file which failed 
over and over again. I can't use the auto configure thing since it produced a very low 
resolution, even if i could figure out how to use auto configure with xfree and 
increase the res i doubt i'd be able to reproduce last time on 5.2.1 now because it 
was all a large mess of ports and bloody xfree86 guts all over the place.
Anyways the situation now is that i get no errors to stdout. Checking the logfile i 
see that everything is going just fine until it reads the hsync value, this is what it 
looks like:
(--) via(0): No DDC signal
(II) via(0): Monitor0: Using hsync value of 31.50 kHz
(II) via(0): Monitor0: Using vrefresh range of 50.00-90.00 Hz
(II) via(0): Clock range:  20.00 to 230.00 MHz
(II) via(0): Not using default mode 640x350 (hsync out of range)
(II) via(0): Not using default mode 320x175 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 640x400 (hsync out of range)
(II) via(0): Not using default mode 320x200 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 720x400 (hsync out of range)
(II) via(0): Not using default mode 360x200 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 320x240 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 640x480 (hsync out of range)
(II) via(0): Not using default mode 320x240 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 640x480 (hsync out of range)
(II) via(0): Not using default mode 320x240 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 640x480 (hsync out of range)
(II) via(0): Not using default mode 320x240 (bad mode clock/interlace/doublescan)
[...]
(II) via(0): Not using default mode 1600x1024 (hsync out of range)
(II) via(0): Not using default mode 800x512 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 1920x1440 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 960x720 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 2048x1536 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 1024x768 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 2048x1536 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 1024x768 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 2048x1536 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 1024x768 (bad mode clock/interlace/doublescan)
(II) via(0): Not using mode 1024x768 (no mode of this name)
(--) via(0): Virtual size is 640x480 (pitch 640)
(**) via(0): *Default mode 640x480: 25.2 MHz (scaled from -1206751.2 MHz), 31.5 kHz, 
60.0 Hz
(II) via(0): Modeline 640x480   25.20  640 656 752 800  480 490 492 525 -hsync -vsync
After this it goes on with loading a few modules, showing me some resource ranges 
after preInit, mapping frambuffer and exits after a few of these messages.
(II) via(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x
(==) via(0): Write-combining range (0xa,0x1) was already clear


Med vänliga hälsningar
Stefan Midjich, Swebase AB
Tel: 042-20 15 00
Fax: 042-20 15 03
E-post: [EMAIL PROTECTED]
Webb: http://swebase.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
.
 

Why don't you just run the auto configurator and change the resolution 
yourself? Then you won't have the problem that your hsync is out of 
range, since it has been auto probed by XFree86 itself.

Section  Screen
Identifier   Screen0
Device  Device0
MonitorMonitor0
DefaultDepth 16
SubSection Display
Depth16
Modes 1280x1074
EndSection
Cheers,
Jorn
Jorn
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


huge xfree86 problems with an acer on freebsd 5.2.1

2004-05-29 Thread stefan
Hi, i already posted this on x11 but hey i really need help so please don't hold it 
against me...

I have an acer aspire 1350LC with a via chipset for the graphics. I got x working once 
on 4.9, same laptop when i had been messing around with 4.4.0 and ports so after a 
while it was a really broken install but suddenly it started working using the auto 
configure thing, first thing i tried to do was to write my own conf file which failed 
over and over again. I can't use the auto configure thing since it produced a very low 
resolution, even if i could figure out how to use auto configure with xfree and 
increase the res i doubt i'd be able to reproduce last time on 5.2.1 now because it 
was all a large mess of ports and bloody xfree86 guts all over the place.

Anyways the situation now is that i get no errors to stdout. Checking the logfile i 
see that everything is going just fine until it reads the hsync value, this is what it 
looks like:

(--) via(0): No DDC signal
(II) via(0): Monitor0: Using hsync value of 31.50 kHz
(II) via(0): Monitor0: Using vrefresh range of 50.00-90.00 Hz
(II) via(0): Clock range:  20.00 to 230.00 MHz
(II) via(0): Not using default mode 640x350 (hsync out of range)
(II) via(0): Not using default mode 320x175 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 640x400 (hsync out of range)
(II) via(0): Not using default mode 320x200 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 720x400 (hsync out of range)
(II) via(0): Not using default mode 360x200 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 320x240 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 640x480 (hsync out of range)
(II) via(0): Not using default mode 320x240 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 640x480 (hsync out of range)
(II) via(0): Not using default mode 320x240 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 640x480 (hsync out of range)
(II) via(0): Not using default mode 320x240 (bad mode clock/interlace/doublescan)
[...]
(II) via(0): Not using default mode 1600x1024 (hsync out of range)
(II) via(0): Not using default mode 800x512 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 1920x1440 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 960x720 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 2048x1536 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 1024x768 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 2048x1536 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 1024x768 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 2048x1536 (bad mode clock/interlace/doublescan)
(II) via(0): Not using default mode 1024x768 (bad mode clock/interlace/doublescan)
(II) via(0): Not using mode 1024x768 (no mode of this name)
(--) via(0): Virtual size is 640x480 (pitch 640)
(**) via(0): *Default mode 640x480: 25.2 MHz (scaled from -1206751.2 MHz), 31.5 kHz, 
60.0 Hz
(II) via(0): Modeline 640x480   25.20  640 656 752 800  480 490 492 525 -hsync -vsync

After this it goes on with loading a few modules, showing me some resource ranges 
after preInit, mapping frambuffer and exits after a few of these messages.

(II) via(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x
(==) via(0): Write-combining range (0xa,0x1) was already clear






Med vänliga hälsningar

Stefan Midjich, Swebase AB
Tel: 042-20 15 00
Fax: 042-20 15 03
E-post: [EMAIL PROTECTED]
Webb: http://swebase.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]