Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
lilo kernel panic blah blah help read pls
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5  Next  
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
accountcreation4
Tux's lil' helper
Tux's lil' helper


Joined: 15 Oct 2006
Posts: 135

PostPosted: Thu Oct 19, 2006 3:15 pm    Post subject: Reply with quote

o yeah i do have nvidia in my video cards, i followed the guide exactly, however, it still doesn't work... i wanted it to work because it says there will be 3-d only with nvidia, and i don't want to keep reducing what my system could be because of errors =( hope i can fix this
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Thu Oct 19, 2006 3:40 pm    Post subject: Reply with quote

You seem to have an xorg.conf now. Could you post (more typing, I'm afraid) the part starting
Code:
Section "Device"
down to the following
Code:
EndSection

Could you find the Horizontal and Vertical sync frequency ranges for your monitor and post those too? The monitor maker and model number will do (I hope!).

In another post, which, sadly, I can't find, NeddySeagoon recommends starting with the vesa driver and then going on to the nv or nvidia drivers. To get the vesa driver, emerge x11-drivers/xf86-video-vesa (while you're at it, emerge x11-drivers/xf86-video-nv too as you then have both the Xorg vesa and Nvidia drivers), please.
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.
Back to top
View user's profile Send private message
accountcreation4
Tux's lil' helper
Tux's lil' helper


Joined: 15 Oct 2006
Posts: 135

PostPosted: Thu Oct 19, 2006 4:00 pm    Post subject: Reply with quote

my monitor thing is 48 and 60 horrizontal / vertical , and uh, monitor is made by NEC model 77F

and uh, i gotta do the other stuff later cus i typed emerge xorg-server and its taking a long time to finish
Back to top
View user's profile Send private message
accountcreation4
Tux's lil' helper
Tux's lil' helper


Joined: 15 Oct 2006
Posts: 135

PostPosted: Thu Oct 19, 2006 4:42 pm    Post subject: Reply with quote

Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"

Driver "vga"

EndSection

Section "Device"
Identifier "My Video Card"
Driver "vga"
Back to top
View user's profile Send private message
accountcreation4
Tux's lil' helper
Tux's lil' helper


Joined: 15 Oct 2006
Posts: 135

PostPosted: Thu Oct 19, 2006 5:08 pm    Post subject: Reply with quote

hey i got a question, when they say rivafb , in my kernel menuconfig it shows only two things for nvidia, first is says:

nvidia framebuffer support, which is already unchecked when i had the rivafb conflict error, second

nvidia riva support , which was checked when i had the rivafb conflict error,

i disabled the second one, but did i disable the right one? it has no framebuffer in the name, only the first one did, which was already unchecked, but the second one has the riva word in it... so the question is:

does rivafb = nvidia riva support?
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Thu Oct 19, 2006 5:16 pm    Post subject: Reply with quote

accountcreation4 wrote:
hey i got a question, when they say rivafb , in my kernel menuconfig it shows only two things for nvidia, first is says:

nvidia framebuffer support, which is already unchecked when i had the rivafb conflict error, second

nvidia riva support , which was checked when i had the rivafb conflict error,

i disabled the second one, but did i disable the right one? it has no framebuffer in the name, only the first one did, which was already unchecked, but the second one has the riva word in it... so the question is:

does rivafb = nvidia riva support?
Code:
CONFIG_FB_RIVA:

 This driver supports graphics boards with the nVidia Riva/Geforce
 chips.
 Say Y if you have such a graphics board.

 To compile this driver as a module, choose M here: the
 module will be called rivafb.
This is the help for the Riva config option, it was the right one, they are both for framebuffer support.

It is usually enough to use the vesa framebuffer support (or vesa-tng, if it works for you)
Code:
<*>   VESA VGA graphics support
        VESA driver type (vesafb-tng)  --->
(1280x1024@75) VESA default mode

_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Thu Oct 19, 2006 5:21 pm    Post subject: Reply with quote

accountcreation4 wrote:
my monitor thing is 48 and 60 horrizontal / vertical , and uh, monitor is made by NEC model 77F

and uh, i gotta do the other stuff later cus i typed emerge xorg-server and its taking a long time to finish
Thanks for the model and manufacturer, the specs needed for your xorg.conf are
Code:
Synchronization Range (Automatic):
Horizontal: 31 kHz to 70 kHz
Vertical: 55 Hz to 120 Hz

_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.
Back to top
View user's profile Send private message
accountcreation4
Tux's lil' helper
Tux's lil' helper


Joined: 15 Oct 2006
Posts: 135

PostPosted: Thu Oct 19, 2006 5:25 pm    Post subject: Reply with quote

uh.. i have the vesa thing u just mentioned disabled, shud i have a star in it? following the guide, it was automatically disabled =\...and if so, shud i have tng or not cus i dunno if its needed or not lol
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Thu Oct 19, 2006 5:34 pm    Post subject: Reply with quote

Here's what seems to be the right "Device" section, it uses the vesa driver to get an xorg.conf which will run. When that stage is reached, the nvidia drivers (and 3D acceleration) can be tackled
Code:
Section "Device"
    Identifier  "Card0"
    Driver      "vesa"
EndSection
and a "Monitor" section
Code:
Section "Monitor"
    Identifier  "Monitor0"
    HorizSync  31-70
    VertRefresh 55-120
EndSection
and in your "Screen" section, you should change the "Device" and "Monitor" lines to
Code:
    Device         "Card0"
    Monitor        "Monitor0"
and try again
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.
Back to top
View user's profile Send private message
accountcreation4
Tux's lil' helper
Tux's lil' helper


Joined: 15 Oct 2006
Posts: 135

PostPosted: Thu Oct 19, 2006 5:39 pm    Post subject: Reply with quote

what about the vesa default mode (1080x1024@75) ? the "@75" is your vertical ? so if my vertical is 60, i should change it to 60? just so i know what to type, it says i should not use something that exceeds what my monitor can handle =\
Back to top
View user's profile Send private message
accountcreation4
Tux's lil' helper
Tux's lil' helper


Joined: 15 Oct 2006
Posts: 135

PostPosted: Thu Oct 19, 2006 6:20 pm    Post subject: Reply with quote

ok well i just recompiled my kernel to have vesa , but when i get back to my xorg , and use the test xorg provides, still don't work....

fatal server error:
no screens found

i have put the fbdev nv nvidia vesa in the video cards.... typed emerge x11-drivers/xf86-video-nv , vesa , and xorg base/server .... i dunno wut cud be wrong... but i'm gonna go play games on my trusty windows :)
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Thu Oct 19, 2006 6:27 pm    Post subject: Reply with quote

accountcreation4 wrote:
what about the vesa default mode (1080x1024@75) ? the "@75" is your vertical ? so if my vertical is 60, i should change it to 60? just so i know what to type, it says i should not use something that exceeds what my monitor can handle =\
Sorry, I forgot that. The specs for your monitor (http://www.nm-select.com/product.asp?sku=2520236) say the maximum resolution is 1280 x 1024 @ 66 Hz so you could try that.
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Thu Oct 19, 2006 6:37 pm    Post subject: Reply with quote

accountcreation4 wrote:
ok well i just recompiled my kernel to have vesa , but when i get back to my xorg , and use the test xorg provides, still don't work....

fatal server error:
no screens found

i have put the fbdev nv nvidia vesa in the video cards.... typed emerge x11-drivers/xf86-video-nv , vesa , and xorg base/server .... i dunno wut cud be wrong... but i'm gonna go play games on my trusty windows :)
The kernel "vesa-tng" is just for booting, the screen you see with all the information of what the kernel is doing and the initscripts are doing. When you get the login: prompt with the black background, this is still the vesa-tng framebuffer.

X is something completely different. Its setup is controlled by /etc/X11/xorg.conf.

I'm afraid the only way forward now after
Code:
fatal server error:
no screens found
is to see the xorg log in /var/log/Xorg.0.log and your /etc/X11/xorg.conf.

If you can only post (and cut'n'paste) from Windows, you could take Corona688's advice and copy the files to floppy disk and then read them back in to Windows for posting.
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.
Back to top
View user's profile Send private message
accountcreation4
Tux's lil' helper
Tux's lil' helper


Joined: 15 Oct 2006
Posts: 135

PostPosted: Thu Oct 19, 2006 6:47 pm    Post subject: Reply with quote

ok i will do that in a few hours, i've ... emerged gnome =x , 200 something packages to go, i cry T.T
Back to top
View user's profile Send private message
accountcreation4
Tux's lil' helper
Tux's lil' helper


Joined: 15 Oct 2006
Posts: 135

PostPosted: Thu Oct 19, 2006 6:53 pm    Post subject: Reply with quote

woot , error: cairo needs the xflag set while emerging gnome, hahahahaha i am a error magnet, which means now i have time to post the error log file for xorg
Back to top
View user's profile Send private message
accountcreation4
Tux's lil' helper
Tux's lil' helper


Joined: 15 Oct 2006
Posts: 135

PostPosted: Thu Oct 19, 2006 7:04 pm    Post subject: Reply with quote

okay here is the log file:


X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.17-gentoo-r7 i686
Current Operating System: Linux livecd 2.6.17-gentoo-r7 #1 SMP Mon Sep 18 01:26:27 UTC 2006 i686
Build Date: 19 October 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 19 14:21:23 2006
(++) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Simple Layout"
(**) |-->Screen "Screen 1" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Card0"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
(**) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
(==) RgbPath set to "/usr/share/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 1.0
X.Org XInput driver : 0.6
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so
(II) Module bitmap: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules/libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.0
(--) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,1a30 card 1043,8025 rev 03 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,1a31 card 0000,0000 rev 03 class 06,04,00 hdr 01
(II) PCI: 00:1e:0: chip 8086,244e card 0000,0000 rev 12 class 06,04,00 hdr 01
(II) PCI: 00:1f:0: chip 8086,2440 card 0000,0000 rev 12 class 06,01,00 hdr 80
(II) PCI: 00:1f:1: chip 8086,244b card 104d,80f0 rev 12 class 01,01,80 hdr 00
(II) PCI: 00:1f:2: chip 8086,2442 card 104d,80f0 rev 12 class 0c,03,00 hdr 00
(II) PCI: 00:1f:3: chip 8086,2443 card 104d,80f0 rev 12 class 0c,05,00 hdr 00
(II) PCI: 00:1f:4: chip 8086,2444 card 104d,80f0 rev 12 class 0c,03,00 hdr 00
(II) PCI: 00:1f:5: chip 8086,2445 card 104d,80e4 rev 12 class 04,01,00 hdr 00
(II) PCI: 01:00:0: chip 10de,002d card 1043,4003 rev 15 class 03,00,00 hdr 00
(II) PCI: 02:0b:0: chip 11c1,044e card 13e0,0401 rev 02 class 07,80,00 hdr 00
(II) PCI: 02:0d:0: chip 10ec,8139 card 104d,80ea rev 10 class 02,00,00 hdr 00
(II) PCI: 02:0e:0: chip 104c,8020 card 104d,80d2 rev 00 class 0c,00,10 hdr 00
(II) PCI: End of PCI scan
(II) Intel Bridge workaround enabled
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0xf4000000 - 0xf5efffff (0x1f00000) MX[B]
(II) Bus 1 prefetchable memory range:
[0] -1 0 0xf5f00000 - 0xf7ffffff (0x2100000) MX[B]
(II) Subtractive PCI-to-PCI bridge:
(II) Bus 2: bridge is at (0:30:0), (0,2,2), BCTRL: 0x0006 (VGA_EN is cleared)
(II) Bus 2 I/O range:
[0] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B]
[1] -1 0 0x0000c400 - 0x0000c4ff (0x100) IX[B]
[2] -1 0 0x0000c800 - 0x0000c8ff (0x100) IX[B]
[3] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[B]
[4] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[B]
[5] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]
[6] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[B]
[7] -1 0 0x0000dc00 - 0x0000dcff (0x100) IX[B]
(II) Bus 2 non-prefetchable memory range:
[0] -1 0 0xf2000000 - 0xf3ffffff (0x2000000) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI:*(1:0:0) nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] rev 21, Mem @ 0xf4000000/24, 0xf6000000/25, BIOS @ 0xf5ff0000/16
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) PCI Memory resource overlap reduced 0xf8000000 from 0xfbffffff to 0xf7ffffff
(II) Active PCI resource ranges:
[0] -1 0 0xf2000000 - 0xf2003fff (0x4000) MX[B]
[1] -1 0 0xf2800000 - 0xf28007ff (0x800) MX[B]
[2] -1 0 0xf3000000 - 0xf30000ff (0x100) MX[B]
[3] -1 0 0xf3800000 - 0xf38000ff (0x100) MX[B]
[4] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]O
[5] -1 0 0xf5ff0000 - 0xf5ffffff (0x10000) MX[B](B)
[6] -1 0 0xf6000000 - 0xf7ffffff (0x2000000) MX[B](B)
[7] -1 0 0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B)
[8] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[B]
[9] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]
[10] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B]
[11] -1 0 0x0000e100 - 0x0000e13f (0x40) IX[B]
[12] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B]
[13] -1 0 0x0000b000 - 0x0000b01f (0x20) IX[B]
[14] -1 0 0x0000e800 - 0x0000e80f (0x10) IX[B]
[15] -1 0 0x0000b400 - 0x0000b41f (0x20) IX[B]
[16] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[B]
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xf2000000 - 0xf2003fff (0x4000) MX[B]
[1] -1 0 0xf2800000 - 0xf28007ff (0x800) MX[B]
[2] -1 0 0xf3000000 - 0xf30000ff (0x100) MX[B]
[3] -1 0 0xf3800000 - 0xf38000ff (0x100) MX[B]
[4] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]O
[5] -1 0 0xf5ff0000 - 0xf5ffffff (0x10000) MX[B](B)
[6] -1 0 0xf6000000 - 0xf7ffffff (0x2000000) MX[B](B)
[7] -1 0 0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B)
[8] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[B]
[9] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]
[10] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B]
[11] -1 0 0x0000e100 - 0x0000e13f (0x40) IX[B]
[12] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B]
[13] -1 0 0x0000b000 - 0x0000b01f (0x20) IX[B]
[14] -1 0 0x0000e800 - 0x0000e80f (0x10) IX[B]
[15] -1 0 0x0000b400 - 0x0000b41f (0x20) IX[B]
[16] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[B]
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xf2000000 - 0xf2003fff (0x4000) MX[B]
[5] -1 0 0xf2800000 - 0xf28007ff (0x800) MX[B]
[6] -1 0 0xf3000000 - 0xf30000ff (0x100) MX[B]
[7] -1 0 0xf3800000 - 0xf38000ff (0x100) MX[B]
[8] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]O
[9] -1 0 0xf5ff0000 - 0xf5ffffff (0x10000) MX[B](B)
[10] -1 0 0xf6000000 - 0xf7ffffff (0x2000000) MX[B](B)
[11] -1 0 0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B)
[12] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[13] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[14] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[B]
[15] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]
[16] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B]
[17] -1 0 0x0000e100 - 0x0000e13f (0x40) IX[B]
[18] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B]
[19] -1 0 0x0000b000 - 0x0000b01f (0x20) IX[B]
[20] -1 0 0x0000e800 - 0x0000e80f (0x10) IX[B]
[21] -1 0 0x0000b400 - 0x0000b41f (0x20) IX[B]
[22] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[B]
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 7.1.1, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font FreeType
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.2.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 1.0
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.1.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.6
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input/kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.1.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.6
(II) VESA: driver for VESA chipsets: vesa
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset vesa found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xf2000000 - 0xf2003fff (0x4000) MX[B]
[5] -1 0 0xf2800000 - 0xf28007ff (0x800) MX[B]
[6] -1 0 0xf3000000 - 0xf30000ff (0x100) MX[B]
[7] -1 0 0xf3800000 - 0xf38000ff (0x100) MX[B]
[8] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]O
[9] -1 0 0xf5ff0000 - 0xf5ffffff (0x10000) MX[B](B)
[10] -1 0 0xf6000000 - 0xf7ffffff (0x2000000) MX[B](B)
[11] -1 0 0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B)
[12] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[13] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[14] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[B]
[15] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]
[16] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B]
[17] -1 0 0x0000e100 - 0x0000e13f (0x40) IX[B]
[18] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B]
[19] -1 0 0x0000b000 - 0x0000b01f (0x20) IX[B]
[20] -1 0 0x0000e800 - 0x0000e80f (0x10) IX[B]
[21] -1 0 0x0000b400 - 0x0000b41f (0x20) IX[B]
[22] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[B]
(II) resource ranges after probing:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xf2000000 - 0xf2003fff (0x4000) MX[B]
[5] -1 0 0xf2800000 - 0xf28007ff (0x800) MX[B]
[6] -1 0 0xf3000000 - 0xf30000ff (0x100) MX[B]
[7] -1 0 0xf3800000 - 0xf38000ff (0x100) MX[B]
[8] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]O
[9] -1 0 0xf5ff0000 - 0xf5ffffff (0x10000) MX[B](B)
[10] -1 0 0xf6000000 - 0xf7ffffff (0x2000000) MX[B](B)
[11] -1 0 0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B)
[12] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[13] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[14] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[17] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[B]
[18] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]
[19] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B]
[20] -1 0 0x0000e100 - 0x0000e13f (0x40) IX[B]
[21] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B]
[22] -1 0 0x0000b000 - 0x0000b01f (0x20) IX[B]
[23] -1 0 0x0000e800 - 0x0000e80f (0x10) IX[B]
[24] -1 0 0x0000b400 - 0x0000b41f (0x20) IX[B]
[25] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[B]
[26] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[27] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules/libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.1.0
ABI class: X.Org Video Driver, version 1.0
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules/libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.0
(II) VESA(0): initializing int10
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(EE) VESA(0): unknown type(0xffffffff)=0xff
(II) VESA(0): EAX=0x00004f00, EBX=0x00000000, ECX=0x00000000, EDX=0x00000000
(II) VESA(0): ESP=0x00000ffa, EBP=0x00000000, ESI=0x00000000, EDI=0x00002000
(II) VESA(0): CS=0xc000, SS=0x0100, DS=0x0040, ES=0x0000, FS=0x0000, GS=0x0000
(II) VESA(0): EIP=0x00001ef0, EFLAGS=0x00003200
(II) VESA(0): code at 0x000c1ef0:
e8 a1 e8 e8 69 00 e8 c4 e8 cf e8 97 e8 e8 5f 00
e8 ba e8 66 c3 2e 8e 1e 6e 00 e8 4f ff 2e a1 66
(II) stack at 0x00001ffa:
00 06 00 00 00 32
(II) VESA(0): VESA BIOS not detected
(II) UnloadModule: "vesa"
(II) UnloadModule: "int10"
(II) Unloading /usr/lib/xorg/modules/libint10.so
(II) UnloadModule: "vbe"
(II) Unloading /usr/lib/xorg/modules/libvbe.so
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
Back to top
View user's profile Send private message
accountcreation4
Tux's lil' helper
Tux's lil' helper


Joined: 15 Oct 2006
Posts: 135

PostPosted: Thu Oct 19, 2006 7:05 pm    Post subject: Reply with quote

and here is the conf file:

# File generated by xorgconfig.

#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#

# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# **********************************************************************

# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the font modules
# Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"

# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"

EndSection

# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

# RgbPath "/usr/share/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#

FontPath "/usr/share/fonts/misc/"
# FontPath "/usr/share/fonts/TTF/"
# FontPath "/usr/share/fonts/OTF"
FontPath "/usr/share/fonts/Type1/"
# FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/local/"
# FontPath "/usr/lib/X11/fonts/misc/"
# FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/Speedo/"
# FontPath "/usr/lib/X11/fonts/Type1/"
# FontPath "/usr/lib/X11/fonts/TrueType/"
# FontPath "/usr/lib/X11/fonts/freefont/"
# FontPath "/usr/lib/X11/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/100dpi/"

# The module search path. The default path is shown here.

# ModulePath "/usr/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

# Option "NoTrapSignals"

# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option "DontVTSwitch"

# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

# Option "DontZap"

# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.

# Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

# Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

# Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

# Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

# Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

Identifier "Keyboard1"
Driver "kbd"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

# Option "Protocol" "Xqueue"

Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"

# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"

# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto" # Auto detect
Option "Device" "/dev/input/mice"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

# Option "Protocol" "Xqueue"

# Mouse-speed setting for PS/2 mouse.

# Option "Resolution" "256"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option "BaudRate" "9600"
# Option "SampleRate" "150"

# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.

Option "ZAxisMapping" "4 5 6 7"

# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"

# ChordMiddle is an option for some 3-button Logitech mice

# Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

Identifier "Monitor0"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 31-70

# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 55-120

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"

# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.

# Chipset "generic"

# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.

# BusID "PCI:0:10:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
Identifier "Card0"
Driver "vesa"
# unsupported card
#VideoRam 32768
# Insert Clocks lines here if appropriate
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24

Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
Identifier "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.

Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
# Mode 0666
# EndSection
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Thu Oct 19, 2006 7:26 pm    Post subject: Reply with quote

accountcreation4 wrote:
woot , error: cairo needs the xflag set while emerging gnome, hahahahaha i am a error magnet, which means now i have time to post the error log file for xorg
Everybody trips over this, I tripped over it.

You can set the X flag in USE in /etc/make.conf and then
Code:
emerge --resume
and it will start running where it left off.
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Thu Oct 19, 2006 7:34 pm    Post subject: Reply with quote

Quote:
Code:
(II) VESA(0): initializing int10
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(EE) VESA(0): unknown type(0xffffffff)=0xff
(II) VESA(0): EAX=0x00004f00, EBX=0x00000000, ECX=0x00000000, EDX=0x00000000
(II) VESA(0): ESP=0x00000ffa, EBP=0x00000000, ESI=0x00000000, EDI=0x00002000
(II) VESA(0): CS=0xc000, SS=0x0100, DS=0x0040, ES=0x0000, FS=0x0000, GS=0x0000
(II) VESA(0): EIP=0x00001ef0, EFLAGS=0x00003200
(II) VESA(0): code at 0x000c1ef0:
e8 a1 e8 e8 69 00 e8 c4 e8 cf e8 97 e8 e8 5f 00
e8 ba e8 66 c3 2e 8e 1e 6e 00 e8 4f ff 2e a1 66
(II) stack at 0x00001ffa:
00 06 00 00 00 32
(II) VESA(0): VESA BIOS not detected
That's a surprise, no VESA BIOS that it can recognize!

Ok, Plan B, try "nv".

Please change
Code:
 Driver "vesa"
in Section "Device" to
Code:
 Driver "nv"
and try again.
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.
Back to top
View user's profile Send private message
accountcreation4
Tux's lil' helper
Tux's lil' helper


Joined: 15 Oct 2006
Posts: 135

PostPosted: Thu Oct 19, 2006 7:51 pm    Post subject: Reply with quote

lol ok
Back to top
View user's profile Send private message
accountcreation4
Tux's lil' helper
Tux's lil' helper


Joined: 15 Oct 2006
Posts: 135

PostPosted: Thu Oct 19, 2006 8:30 pm    Post subject: Reply with quote

nv worked, but then when i type startx, i get this error:

xterm: Error 32, errno 2: No such file or directory
Reason: get_pty: not enough ptys
it says it 3 times, exactly as this line says, then it says:

waiting for X server to shut down FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing.

well thats wut it says everytime i type startx =(
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Fri Oct 20, 2006 8:44 am    Post subject: Reply with quote

accountcreation4 wrote:
nv worked, but then when i type startx, i get this error:

xterm: Error 32, errno 2: No such file or directory
Reason: get_pty: not enough ptys
it says it 3 times, exactly as this line says, then it says:

waiting for X server to shut down FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing.

well thats wut it says everytime i type startx =(
If you run
Code:
cd /usr/src/linux
make menuconfig
and go to
Code:
 Device Drivers  --->
  Character devices  --->
you will see
Code:

[*] Legacy (BSD) PTY support
(256) Maximum number of legacy PTY in use
This is what it should be set to, can you check it, change it if necessary and, if changed, then recompile your kernel?

If you have saved System.map and .config as well as bzimage then you will need to copy the new .config on top of the old one.

Posts here have said, and the kernel log confirms, that, on x86, System.map isn't needed.

Don't worry about "FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing." it seems to be a non-optional extra that came in with x11-xorg-7, it does no harm.
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Fri Oct 20, 2006 2:31 pm    Post subject: Reply with quote

accountcreation4 wrote:
o yeah i do have nvidia in my video cards, i followed the guide exactly, however, it still doesn't work... i wanted it to work because it says there will be 3-d only with nvidia, and i don't want to keep reducing what my system could be because of errors =( hope i can fix this
Forgot to mention this but you will need to emerge x11-drivers/nvidia-legacy-drivers for your RIVA TNT2 Model 64/Model 64 Pro not the nvidia-drivers.
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.
Back to top
View user's profile Send private message
accountcreation4
Tux's lil' helper
Tux's lil' helper


Joined: 15 Oct 2006
Posts: 135

PostPosted: Fri Oct 20, 2006 7:04 pm    Post subject: Reply with quote

the legacy drivers conflicts with another , but i won't worry about that at the moment, the pty's and stuff were already checked lol :( so i dunno wut else cud be wrong..

"If you have saved System.map and .config as well as bzimage then you will need to copy the new .config on top of the old one."

me confused =*(
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Fri Oct 20, 2006 7:12 pm    Post subject: Reply with quote

accountcreation4 wrote:
the legacy drivers conflicts with another , but i won't worry about that at the moment, the pty's and stuff were already checked lol :( so i dunno wut else cud be wrong..
I'm sorry I can't think of anything else. The legacy pty setting is standard so it seemed that you would have it but it was just a thought.

The legacy drivers will conflict with x11-drivers/nvidia-drivers so you will have to unmerge these first
Code:
emerge -Ca x11-drivers/nvidia-drivers

accountcreation4 wrote:
"If you have saved System.map and .config as well as bzimage then you will need to copy the new .config on top of the old one."

me confused =*(
All I wanted to say was that, if you had changed your .config, it should be saved in boot as well as your new kernel. That is, if you saved your previous .config. You see, it doesn't get any better with the telling, does it? :)
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Goto page Previous  1, 2, 3, 4, 5  Next
Page 4 of 5

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum