Re: Problems with startx on 5.2-RC2

2004-01-03 Thread List Man
Hi,

I am curious if the problem persists if you put the 
following in your device.hints using the default kernel.

hint.acpi.0.disabled="1"


Lucio

On  0, Martin Brecher <[EMAIL PROTECTED]> wrote:
:Jaroslaw Nozderko wrote:
:[...]
:>>Yes, see my post from earlier today called "Can't shutdown, logout,
:>>or restart cleanly."
:[...]
:>thanks, I've read it - I have Asus P3B-F motherboard :))
:>But seriously, I'm not sure it's hardware-related - I don't remember
:>a single occurence of this problem in 5.1 and 5.0. It seems to have 
:>something to do with 5.2.
:[...]
:
:I agree: I experienced X11 freezes on 5.2 with both a nvidia card as
:well as a card using the i740 chipset. The nv freezed the computer as
:soon as I started X, the i740 happend to freeze it when I killed the X
:server
:Also, I saw two similar reports on the -current list.
:
:However, I managed to work around these freezes by removing the two
:SMP-related lines from my kernel configuration:
:
:options SMP  # Symmetric MultiProcessor Kernel
:device  apic # I/O APIC
:
:
:Additionally, I am sure ACPI does not have anything to do with this --
:at least on this box.
:
:HTH
:- Martin
:___
:[EMAIL PROTECTED] mailing list
:http://lists.freebsd.org/mailman/listinfo/freebsd-questions
:To unsubscribe, send any mail to "[EMAIL PROTECTED]"

-- 
:wq!
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: 1024x768 on a toshiba 8100 tecra in a text (Non X) Console

2003-12-30 Thread List Man
Hi,

This problem even appears when installing the OS though
sysinstall. Disabeling acpi was the solution.

Greetings

Lucio

On  0, "Michael L. Squires" <[EMAIL PROTECTED]> wrote:
:> Anyway right know I am having too many system freezes
:> when trying to start X.. most of the time starting X will
:
:I'm entering this message from a KDE Konsole screen running on a Tecra
:8100 under 5.2-CURRENT of 12/22.  I usually use the 8100 in a docking
:station with an external monitor, but the few times I've run the laptop
:out of the dock I've had no problems.
:
:My XF86Config file has
:
:Section "Device"
:
:   Identifier  "Card0"
:   Driver  "savage"
:   VendorName  "S3 Inc."
:   BoardName   "86C270-294 Savage/MX-MV"
:   BusID   "PCI:1:0:0"
:
:EndSection
:
:for the video hardware.
:
:Mike Squires

-- 
:wq!
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: 1024x768 on a toshiba 8100 tecra in a text (Non X) Console screen

2003-12-28 Thread List Man
Hi,

I seems indeed that only the VESA_800x600 can be set.
I had hopes that this would not be the case..
Anyway right know I am having too many system freezes
when trying to start X.. most of the time starting X will
just freeze the whole system. But that is another issue
since I am using 5.2 RC2 and this is not the right place
to discuss this. 

I use FreeBSD for server (Proxy, DNS, DHCP etc) purposes for
I am used to it an knows how to tweak it for very high performance.
I work the whole day with a text interface so I want something
different when at home. I want it to be easy enough to setup
without the need to recompile or set any special settings in
for instance device.hints or loader.conf. I used to use Apple
for this and later on Windows.. 

Greetings,

Lucio


On  0, Francesco Casadei <[EMAIL PROTECTED]> wrote:
:On Sat, Dec 27, 2003 at 11:59:24AM +0100, List Man wrote:
snip
:> I want to be able to use my full screen in text (Not X) mode. Right now the 
:> standard resolution is 640x480 and I would like to get it to 1024x768.
:> 
:> When I do a "vidcontrol -i mode" I get plenty of resolution options
:> presented.
:> 
:> One of them : 
:> 261 (0x105) 0x000f G 1024x768x8 18x16  0xa 64k 64k 0xf000 8192k
:> 
:> "vidcontrol -g 1024x768x8" will not give me error messages but the screen resolution
:> doesn't change.
:> 
:> This is a piece of my dmesg output :
:> VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc0a01c82 (122)
:> VESA: S3 Incorporated. M7 BIOS
:> 
:> In case some of you might wonder where you can get splash screens, this is where I 
got
:> mine : http://www.baldwin.cx/splash/.
:> 
snip
:
:From vidcontrol(1) manpage:
:
:[...]
: modeSelect a new video mode.  The modes currently recognized are:
: 80x25, 80x30, 80x43, 80x50, 80x60, 132x25, 132x30, 132x43,
: 132x50, 132x60, VGA_40x25, VGA_80x25, VGA_80x30, VGA_80x50,
: VGA_80x60, VGA_90x25, VGA_90x30, VGA_90x43, VGA_90x50, VGA_90x60,
: EGA_80x25, EGA_80x43, VESA_132x25, VESA_132x43, VESA_132x50,
: VESA_132x60.  The raster text mode VESA_800x600 can also be cho-
: sen.  See Video Mode Support below.
:[...]
:
:It seems that you can't set 1024x768 VESA mode, only 800x600.
:Furthermore, to achieve this you have to recompile your kernel with the
:SC_PIXEL_MODE option.
:
:See section 'Video Mode Support', as suggested in the above snippet.
:
:   Francesco Casadei
:

-- 
:wq!
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


1024x768 on a toshiba 8100 tecra in a text (Non X) Console screen

2003-12-27 Thread List Man
First of all the best wishes for all of you.

I have seen people puzzling with the following before but
never saw a definitive answer on the topic.

I have FreeBSD 5.2 on a toshiba tecra 8100 with the following in
/boot/loader.conf.

snd_pcm_load="YES"   # Digital sound subsystem
snd_ds1_load="YES"   # ds1
vesa_load="YES"  # Set this to YES to load the vesa module
#
splash_bmp_load="YES"# Set this to YES for bmp splash screen!
bitmap_load="YES"# Set this to YES if you want splash screen!
bitmap_name="/boot/daemon.bmp"   # Set this to the name of the bmp or pcx file
#
console="vidconsole" # Set the current console

I want to be able to use my full screen in text (Not X) mode. Right now the 
standard resolution is 640x480 and I would like to get it to 1024x768.

When I do a "vidcontrol -i mode" I get plenty of resolution options
presented.

One of them : 
261 (0x105) 0x000f G 1024x768x8 18x16  0xa 64k 64k 0xf000 8192k

"vidcontrol -g 1024x768x8" will not give me error messages but the screen resolution
doesn't change.

This is a piece of my dmesg output :
VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc0a01c82 (122)
VESA: S3 Incorporated. M7 BIOS

In case some of you might wonder where you can get splash screens, this is where I got
mine : http://www.baldwin.cx/splash/.


Greetings,

LJ

-- 
:wq!
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"