
Although you didn't post your X log files, I **assume** that you *did* already check in there and it *didn't* explain why it failed to start up...?Benson wrote:But now i have another problem: after booting it doesn't start kdm, xdm is in the rc.conf and starts in default runlevel, also the X Font server starts, but after saying "starting local" the screen flickers once (with nvidia in xfree, changing it to nv it flickers three thimes!) and i remain in console modus. In Console 7 where X should start, is no login, no X at all started... Login in as root and starting then kdm (or X) works without problems. Searched the forums, re-read the docs, have done everything there was mentioned, still no success to get my kdm automatically up... anyone else having this issue???
After 3 days of pulling my hair out, you have found my answerRcomian wrote:Ok, looks like it works now. I've got nearly all the main USB options and drivers enabled except EHCI (USB2).
It looks like it's USB2 which is breaking things.
Code: Select all
NForce2 chipset mobo..
Bus 0, device 2, function 0:
USB Controller: nVidia Corporation nForce2 USB Controller (rev 163).
IRQ 10.
Master Capable. No bursts. Min Gnt=3.Max Lat=1.
Non-prefetchable 32 bit memory at 0xee003000 [0xee003fff].
Bus 0, device 2, function 1:Code: Select all
Bus 2, device 0, function 0:
VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX - nForce GPU] (rev 163).
IRQ 10.
Yeap. Looks like EHCI is breaking stuff. I disabled EHCI in my kernel and now I am able to boot into the 2.6.7 series using the nvidia driver.Rcomian wrote:Ok, looks like it works now. I've got nearly all the main USB options and drivers enabled except EHCI (USB2).
It looks like it's USB2 which is breaking things.

I don't think all of EHCI is responible for this behavior. Just to put my experience in...Ateo wrote:Yeap. Looks like EHCI is breaking stuff. I disabled EHCI in my kernel and now I am able to boot into the 2.6.7 series using the nvidia driver.
Is this a kernel bug? A driver bug? An IRQ conflict? Luckily, none of the devices on this system uses USB2 so I'm ok for the time being.... At least now we have concluded that it might be EHCI..
Code: Select all
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
Code: Select all
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
I have this exact same problem (using a p4p800 board, 865 chipset). The screen doesn't flicker tho, monitor loses video sync and i have to reboot. (also, i am running XFree.. not xorg)Narusegawa wrote:I had a problem with this all day. I've just gone into my kernel and changed EHCI to not loaded (it was module before) and now the nvidia works with Xorg.
Latest version of Xorg from emerge (~x86)
NVidia 6601
and 2.6.7-r9 gentoo-dev kernel
Only issue is when killing X it goes into a flickering color screen and I can only ctrl-alt-delete to reboot to get system back.
I'm using an MSI K7N2G-ILSR mobo with NForce2 chipsets and GF4 MX GPU onboard.
Code: Select all
# 19990713 Artur Skawina <skawina@geocities.com>
# Added '-march' and '-mpreferred-stack-boundary' support
#
LDFLAGS := -m elf_i386
OBJCOPYFLAGS := -O binary -R .note -R .comment -S
LDFLAGS_vmlinux :=
CHECK := $(CHECK) -D__i386__=1
CFLAGS += -pipe -msoft-float
# prevent gcc from keeping the stack 16 byte aligned
CFLAGS += $(call check_gcc,-mpreferred-stack-boundary=2,)
align := $(subst -functions=0,,$(call check_gcc,-falign-functions=0,-malign-functions=0))
cflags-$(CONFIG_M386) += -march=i386
cflags-$(CONFIG_M486) += -march=i486
cflags-$(CONFIG_M586) += -march=i586
cflags-$(CONFIG_M586TSC) += -march=i586
cflags-$(CONFIG_M586MMX) += $(call check_gcc,-march=pentium-mmx,-march=i586)
cflags-$(CONFIG_M686) += -march=i686
cflags-$(CONFIG_MPENTIUMII) += $(call check_gcc,-march=pentium2,-march=i686)
cflags-$(CONFIG_MPENTIUMIII) += $(call check_gcc,-march=pentium3,-march=i686)
cflags-$(CONFIG_MPENTIUMM) += $(call check_gcc,-march=pentium3,-march=i686)
cflags-$(CONFIG_MPENTIUM4) += $(call check_gcc,-march=prescott,-march=i686)
cflags-$(CONFIG_MK6) += -march=k6
# Please note, that patches that add -march=athlon-xp and friends are pointless.
# They make zero difference whatsosever to performance at this time.
cflags-$(CONFIG_MK7) += $(call check_gcc,-march=athlon,-march=i686 $(align)-functions=4)
cflags-$(CONFIG_MK8) += $(call check_gcc,-march=k8,$(call check_gcc,-march=athlon,-march=i686 $(align)-functions=4))
cflags-$(CONFIG_MCRUSOE) += -march=i686 $(align)-functions=0 $(align)-jumps=0 $(align)-loops=0
cflags-$(CONFIG_MWINCHIPC6) += $(call check_gcc,-march=winchip-c6,-march=i586)
cflags-$(CONFIG_MWINCHIP2) += $(call check_gcc,-march=winchip2,-march=i586)
cflags-$(CONFIG_MWINCHIP3D) += $(call check_gcc,-march=winchip2,-march=i586)
cflags-$(CONFIG_MCYRIXIII) += $(call check_gcc,-march=c3,-march=i486) $(align)-functions=0 $(align)-jumps=0 $(align)-loops=0
cflags-$(CONFIG_MVIAC3_2) += $(call check_gcc,-march=c3-2,-march=i686)
Code: Select all
Fontconfig warning: line 251: invalid edit binding "same"
Fontconfig warning: line 263: invalid edit binding "same"
No fonts found; this probably means that the fontconfig
library is not correctly configured. You may need to
edit the fonts.conf configuration file. More information
about fontconfig can be found in the fontconfig(3) manual
page and on http://fontconfig.orgif you reinstalled xfree or xorg you have to rebuild qt. kde should be ok. i had to uninstall all nvidia stuff and fontconfig and freetype to get qt to build.Benson wrote:Ok, i had the same problem with my new computer (GeForce FX5700, nforce2 Ultra, Kernel 2.6.7-r8). After disabling the USB 2.0 support, it works now! Thx socke for finding this solution!!!![]()
But now i have another problem: after booting it doesn't start kdm, xdm is in the rc.conf and starts in default runlevel, also the X Font server starts, but after saying "starting local" the screen flickers once (with nvidia in xfree, changing it to nv it flickers three thimes!) and i remain in console modus. In Console 7 where X should start, is no login, no X at all started... Login in as root and starting then kdm (or X) works without problems. Searched the forums, re-read the docs, have done everything there was mentioned, still no success to get my kdm automatically up... anyone else having this issue???
I got one hdd at the moment, so haven't seen the 2 drive problem. Thanks for letting me know, I'll keep it in mind when I upgradeisnogood wrote:BTW:Rcomian - do you got one or two drives in your box?Got the same mobo and that thing crashes every five minutes with two hdd's on the same channel.
Not sure about the dri thing. But the "NvAGP" "1" needs to go inside the 'Section "Device"' for the vid card, as in:PEETIE wrote:When unchecking dev/agpgart in the kernel compile menu do you need to uncheck the dri line that appears below it when you uncheck it?
and does it matter where you add the line Option "NvAGP" "1"' in XF86Config?
Code: Select all
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
Option "DigitalVibrance" "4" # <i>
#Option "PageFlip" # [<bool>]
#Option "Dac8Bit" # [<bool>]
#Option "NoLogo" # [<bool>]
#Option "Overlay" # [<bool>]
#Option "UBB" # [<bool>]
#Option "Stereo" # <i>
#Option "WindowFlip" # [<bool>]
#Option "SWcursor" "True" # [<bool>]
#Option "HWcursor" "True" # [<bool>]
#Option "VideoKey" # <i>
Option "NvAGP" "1" # <i>
#Option "IgnoreEDID" # [<bool>]
#Option "NoDDC" # [<bool>]
#Option "ConnectedMonitor" # <str>
#Option "ConnectedMonitors" # <str>
#Option "TVStandard" # <str>
#Option "TVOutFormat" # <str>
#Option "RenderAccel" # [<bool>]
#Option "CursorShadow" # [<bool>]
#Option "CursorShadowAlpha" # <i>
#Option "CursorShadowXOffset" # <i>
#Option "CursorShadowYOffset" # <i>
#Option "UseEdidFreqs" "True" # [<bool>]
#Option "FlatPanelProperties" # <str>
#Option "TwinView" # [<bool>]
#Option "TwinViewOrientation" # <str>
#Option "SecondMonitorHorizSync" # <str>
#Option "SecondMonitorVertRefresh" # <str>
#Option "MetaModes" # <str>
#Option "UseInt10Module" # [<bool>]
#Option "SwapReady" # [<bool>]
#Option "NoTwinViewXineramaInfo" # [<bool>]
#Option "NoRenderExtension" # [<bool>]
#Option "UseClipIDs" # [<bool>]
#Option "CIOverlay" # [<bool>]
#Option "TransparentIndex" # <i>
#Option "OverlayDefaultVisual" # [<bool>]
#Option "NvEmulate" # <i>
#Option "NoBandWidthTest" # [<bool>]
#Option "CustomEDID-CRT-0" # <str>
#Option "CustomEDID-CRT-1" # <str>
#Option "CustomEDID-DFP-0" # <str>
#Option "CustomEDID-DFP-1" # <str>
#Option "CustomEDID-TV-0" # <str>
#Option "CustomEDID-TV-1" # <str>
#Option "TVOverScan" # <f>
#Option "IgnoreDisplayDevices" # <str>
#Option "MultisampleCompatibility" # [<bool>]
Identifier "Card_nvidia"
Driver "nvidia"
# Driver "nv" # builtin
# Driver "vesa"
VendorName "nVidia Corporation"
BoardName "NV17 [GeForce4 MX 440]"
BusID "PCI:2:0:0"
EndSectionWorked perfectly for me, thanks!orick wrote:Hi,
I had similar problems with the latest 2.6.7-gentoo-r5 kernel and nvidia,emerging the latest masked nvidia-glx-1.0.5336-r2 and nvidia-kernel-1.0.5336-r4 solved my problem:However, unfortunately updating with emerge -uDV world insists to bring back the older, stable, nvidia versions. So, until these new nvidia versions are marked stable you should reemerge the latest ones after a world update.Code: Select all
ACCEPT_KEYWORDS="~x86" emerge -Dv nvidia-glx nvidia-kernel