Benno Schulenberg wrote:
Well, somewhere deep in the BIOS peripheral settings, there are
things like Enable AGP Fast Write or similar. Set all those
things to Off or Disabled. You wil want stability first, speed
maybe later. It probably won't make a difference, but it at least
excludes
Benno Schulenberg wrote:
You've said you have an MSI K8M800 motherboard. Looking at
http://www.msicomputer.com/product/p_list.asp?class=mbcpu=3, such
boards only support Sempron 2600+, 2800+, 3000+, 3100+, 3300+,
not a 2500+. This may not be a problem, but then again, it might
not be
Benno Schulenberg wrote:
Flaky hardware? Timings too fast in the BIOS?
What timings? :S
Kernel misconfigured? When the vesa driver doesn't give acceptable
performance, there is something wrong. You might want to actually
answer the questions I asked earlier.
I couldn't answer the
Mrugesh Karnik wrote:
Benno Schulenberg wrote:
Flaky hardware? Timings too fast in the BIOS?
What timings? :S
Well, somewhere deep in the BIOS peripheral settings, there are
things like Enable AGP Fast Write or similar. Set all those
things to Off or Disabled. You wil want stability
Well hi again,
It took longer than I expected to change the server. Anyway.
The VIA Unichrome situation turned out to be a no-go for me. I had to
install an NVIDIA GeForce FX5200 on the machine and get X running.
I think this whole thread and me compiling various Xorg versions about 8
or 9
On Thursday 17 Nov 2005 10:55 pm, Mrugesh Karnik wrote:
I still am confused about one thing though... which exactly is the 2D
driver for VIA Unichrome?
Could this be it?
http://unichrome.sourceforge.net/
Abhay
pgpO6lNw5C6kd.pgp
Description: PGP signature
Mrugesh Karnik wrote:
Something interesting did happen though. I had that Unknown
device in my lspci output for both Gentoo and FC4 when I was on
VIA Unichrome. Now after switching to nvidia, I can see a Host
Bridge properly identified in its place. I wonder why that would
be?
Flaky
Benno Schulenberg wrote:
Mrugesh Karnik wrote:
Well, the kernel modules have been loaded already...
Which ones precisely? See the output of 'lsmod'.
Do an 'lsmod' on your FC4 too and compare.
That'd be drm and via
I noticed one thing, the agpgart option in the kernel is always
Mrugesh Karnik wrote:
Benno Schulenberg wrote:
Which ones precisely? See the output of 'lsmod'.
Do an 'lsmod' on your FC4 too and compare.
That'd be drm and via
Could you post the output of 'lsmod' on your FC4?
00:00.0 Host Bridge: VIA Technologies, Inc.: Unknown Device 0204
Hmm,
Mrugesh Karnik wrote:
Well, the kernel modules have been loaded already...
Which ones precisely? See the output of 'lsmod'.
Do an 'lsmod' on your FC4 too and compare.
I noticed one thing, the agpgart option in the kernel is always
disabled... !x86_64 says the Help for that option. As it is,
Richard Fish wrote:
I think we have a failure to communicate here
Actually no...
The via_drv I am talking about is an _x.org_ driver, not a kernel
driver. It has nothing to do with the kernel sources or rebuilding
the kernel. It should exist at /usr/lib/modules/drivers/via_drv.o
(along
Mrugesh Karnik schreef:
Richard Fish wrote:
The via_drv I am talking about is an _x.org_ driver, not a kernel
driver. It has nothing to do with the kernel sources or rebuilding
the kernel. It should exist at /usr/lib/modules/drivers/via_drv.o
(along with all other X11 drivers).
I
Holly Bostick wrote:
Possibly because you don't have the 'insecure-drivers' USE flag enabled:
I had insecure-drivers enabled the first time I compiled xorg. I think I
had disabled it in the subsequent compilations. I found an ebuild with
VIA Unichrome USE flag and patches added; in the
On 11/12/05, Mrugesh Karnik [EMAIL PROTECTED] wrote:
So what I tried
was to enable the VIA drivers in the kernel. It then compiled both
drm.ko and via.ko and also via_drv.o, but the via_drv.o never left the
/usr/src directory.
Which is the exactly correct and expected behavior.
I don't
Richard Fish wrote:
Too many variables to answer that question...kernel versions, kernel
configuration, kernel patches, frame buffer options, xorg versions,
xorg patches, and so on. You could try to eliminate some of those
variables by using the same kernel version .config under both.
Ay!
On 11/11/05, Mrugesh Karnik [EMAIL PROTECTED] wrote:
Still no luck. I tried compiling VIA Unichrome suppport in the kernel,
but the kernel version of via_drv.o doesn't move out of /usr/src.
xorg-x11-6.8.2-r6 doesn't compile via_drv.o and my X is performing very
badly!
I think we have a
Hi,
I just installed Gentoo on an AMD64 Sempron machine. RAM is not a
problem.. 1GB of it.
I just emerged xorg-x11. The graphics card is VIA Unichrome onboard. I
have a perfectly fine working FC4 system. I used the FC4 xorg.conf file.
First ran Xorg -configure. Kept all the paths from
On 11/10/05, Mrugesh Karnik [EMAIL PROTECTED] wrote:
Hi,
I just installed Gentoo on an AMD64 Sempron machine. RAM is not a
problem.. 1GB of it.
I just emerged xorg-x11. The graphics card is VIA Unichrome onboard. I
have a perfectly fine working FC4 system. I used the FC4 xorg.conf file.
Richard Fish wrote:
On 11/10/05, Mrugesh Karnik [EMAIL PROTECTED] wrote:
Hi,
I just installed Gentoo on an AMD64 Sempron machine. RAM is not a
problem.. 1GB of it.
I just emerged xorg-x11. The graphics card is VIA Unichrome onboard. I
have a perfectly fine working FC4 system. I used the FC4
On 11/10/05, Mrugesh Karnik [EMAIL PROTECTED] wrote:
Hmmm. I am using the stable version. That's 6.8.2-r4. I'll try emerging
r6.
Well, give it shot. But looking at the ChangeLog, I don't see any
references to via driver changes in -r5 or -r6, so I wouldn't hold my
breath that you will see a
Richard Fish wrote:
On 11/10/05, Mrugesh Karnik [EMAIL PROTECTED] wrote:
Hmmm. I am using the stable version. That's 6.8.2-r4. I'll try emerging
r6.
Well, give it shot. But looking at the ChangeLog, I don't see any
references to via driver changes in -r5 or -r6, so I wouldn't hold my
21 matches
Mail list logo
