Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 07-17-05, 02:05 PM   #1
Santiago
Registered User
 
Join Date: Jul 2005
Posts: 4
Default X instafreeze with 7668/2.6.11-1.1369_FC4/gf4mx4000

I've searched the forum for similar problems to this one and there doesn't seem to be any threads - my search terms may be badly chosen, however - apologies if so, if you could point me to a thread that'd be ace.

Anyway, here's current system setup (important bits anyway):
AMD xp 1500 mobile
Abit nf7-s nforce 2
1024mb RAM
Aopen Geforce MX 4000
Fedora Core 4, kernel 2.6.11-1.1369_FC4

The problem I'm having seems very simple - X simply refuses to start using the nvidia driver/kernel module (I'm ridiculously new to this, so I'm not sure which is which, or even if they are the same thing [they aren't though, right?]).

Steps to get to where I was - stopped x, installed driver (which compiled a kernel interface), modprobed nvidia (fine), init 5...black screen, swiftly followed by no signal to monitor at all!

sshed in from a windows box downstairs to run the bug report jobby - you can find it here - I haven't used the verbose option (forgot, sorry) - if theres not enough info there I'll get it to crash again and post the full report.

System works absolutely fine on the "nv" driver (using it to write this), which leads me to believe it's probably not a hardware fault.

Any ideas on how to fix this would be greatly appreciated - if you have please post your solution in words of one syllable! This is still very much a learning experience for me, and I'm not too bright anyway .

Cheers,
James.
Santiago is offline   Reply With Quote
Old 07-17-05, 11:09 PM   #2
energyman76b
Registered User
 
Join Date: Dec 2002
Location: Clausthal/Germany
Posts: 1,104
Default Re: X instafreeze with 7668/2.6.11-1.1369_FC4/gf4mx4000

Hi,

could you be more specific about the 'refuse' part?
From a quick glance, your xorg.log says that everything is fine. Hm, and the card sits properly in its slot?
energyman76b is offline   Reply With Quote
Old 07-18-05, 06:41 AM   #3
Santiago
Registered User
 
Join Date: Jul 2005
Posts: 4
Default Re: X instafreeze with 7668/2.6.11-1.1369_FC4/gf4mx4000

Quote:
Originally Posted by energyman76b
Hi,

could you be more specific about the 'refuse' part?
From a quick glance, your xorg.log says that everything is fine. Hm, and the card sits properly in its slot?
Yeah, no problem:

Say I start the system in runlevel 3, and login...

I startx, and the screen goes blank immediately, some activity occurs (hard disk spins, clearly something is happening), eventually the hard disk stops spinning, and by this time my monitor is telling me that it isn't receiving a signal from the box. It might well be something other than X causing the problem but I don't know - is it that Xid error at the end of dmesg that I should be worrying about?

That would suggest something up with the kernel module, yes?

Card is definitely in its slot .
Santiago is offline   Reply With Quote
Old 07-18-05, 01:20 PM   #4
energyman76b
Registered User
 
Join Date: Dec 2002
Location: Clausthal/Germany
Posts: 1,104
Default Re: X instafreeze with 7668/2.6.11-1.1369_FC4/gf4mx4000

Hi,

hmhm, the Xid's.. well nobody except nvidia knows, what they really mean, and it is the last thing in your dmesg.

Hm, does the box react to the sysrq-keys anymore?
Oh, and is it possible that you try a vanilla kernel.org kernel?
Maybe that helps, maybe not. Some people with Xid's solved the problem by updating their cards bios.


EDIT:

oh, you have a problem!

ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[5] MMIO=[ef084000-ef0847ff] Max Packet=[2048]
Badness in get_phy_reg at drivers/ieee1394/ohci1394.c:238 (Not tainted)
[<f8a5e288>] get_phy_reg+0x288/0x28d [ohci1394]
[<c028f9d6>] freed_request+0x16/0x66
[<c0290734>] __blk_put_request+0x5a/0x74
[<f8a5f856>] ohci_devctl+0x618/0xaf6 [ohci1394]
[<c011b903>] scheduler_tick+0x1a/0x518
[<c028ced0>] elv_queue_empty+0x12/0x1b
[<c02b2486>] ide_do_request+0xb1/0x4ff
[<f8a619a6>] ohci_irq_handler+0x655/0xce2 [ohci1394]
[<c0108c4a>] timer_interrupt+0x7c/0x1b5
[<f89c8bf4>] cx8802_irq+0x4e/0x93 [cx8802]
[<c015085d>] handle_IRQ_event+0x2e/0x5a
[<c015093c>] __do_IRQ+0xb3/0x367
[<c0105b1d>] do_IRQ+0x4a/0x82
=======================
[<c0138c75>] delayed_work_timer_fn+0x0/0xa
[<c0103c0e>] common_interrupt+0x1a/0x20
[<c01282cc>] __do_softirq+0x2c/0x8a
[<c0105c29>] do_softirq+0x3e/0x42
=======================
[<c0105b24>] do_IRQ+0x51/0x82
[<c0103c0e>] common_interrupt+0x1a/0x20
[<f8a5e36e>] set_phy_reg+0xe1/0x270 [ohci1394]
[<c0156d9b>] __free_pages_ok+0x9d/0xc4
[<f8a5f843>] ohci_devctl+0x605/0xaf6 [ohci1394]
[<f9bf3c2b>] csr1212_fill_cache+0xdf/0x106 [ieee1394]
[<f9bf3d99>] csr1212_generate_csr_image+0x147/0x240 [ieee1394]
[<f9be9133>] hpsb_reset_bus+0x20/0x26 [ieee1394]
[<c0138e82>] worker_thread+0x198/0x457
[<c0372d6d>] schedule+0x31d/0x7b3
[<c011be46>] __wake_up_common+0x39/0x59
[<f9bebbd0>] delayed_reset_bus+0x0/0xc0 [ieee1394]
[<c011be01>] default_wake_function+0x0/0xc
[<c0138cea>] worker_thread+0x0/0x457
[<c013f50b>] kthread+0x87/0x8b
[<c013f484>] kthread+0x0/0x8b
[<c01012ad>] kernel_thread_helper+0x5/0xb
Badness in set_phy_reg at drivers/ieee1394/ohci1394.c:267 (Not tainted)
[<f8a5e4f8>] set_phy_reg+0x26b/0x270 [ohci1394]
[<c028f9d6>] freed_request+0x16/0x66
[<c0290734>] __blk_put_request+0x5a/0x74
[<f8a5f868>] ohci_devctl+0x62a/0xaf6 [ohci1394]
[<c011b903>] scheduler_tick+0x1a/0x518
[<c028ced0>] elv_queue_empty+0x12/0x1b
[<c02b2486>] ide_do_request+0xb1/0x4ff
[<f8a619a6>] ohci_irq_handler+0x655/0xce2 [ohci1394]
[<c0108c4a>] timer_interrupt+0x7c/0x1b5
[<f89c8bf4>] cx8802_irq+0x4e/0x93 [cx8802]
[<c015085d>] handle_IRQ_event+0x2e/0x5a
[<c015093c>] __do_IRQ+0xb3/0x367
[<c0105b1d>] do_IRQ+0x4a/0x82
=======================
[<c0138c75>] delayed_work_timer_fn+0x0/0xa
[<c0103c0e>] common_interrupt+0x1a/0x20
[<c01282cc>] __do_softirq+0x2c/0x8a
[<c0105c29>] do_softirq+0x3e/0x42
=======================
[<c0105b24>] do_IRQ+0x51/0x82
[<c0103c0e>] common_interrupt+0x1a/0x20
[<f8a5e36e>] set_phy_reg+0xe1/0x270 [ohci1394]
[<c0156d9b>] __free_pages_ok+0x9d/0xc4
[<f8a5f843>] ohci_devctl+0x605/0xaf6 [ohci1394]
[<f9bf3c2b>] csr1212_fill_cache+0xdf/0x106 [ieee1394]
[<f9bf3d99>] csr1212_generate_csr_image+0x147/0x240 [ieee1394]
[<f9be9133>] hpsb_reset_bus+0x20/0x26 [ieee1394]
[<c0138e82>] worker_thread+0x198/0x457
[<c0372d6d>] schedule+0x31d/0x7b3
[<c011be46>] __wake_up_common+0x39/0x59
[<f9bebbd0>] delayed_reset_bus+0x0/0xc0 [ieee1394]
[<c011be01>] default_wake_function+0x0/0xc
[<c0138cea>] worker_thread+0x0/0x457
[<c013f50b>] kthread+0x87/0x8b
[<c013f484>] kthread+0x0/0x8b
[<c01012ad>] kernel_thread_helper+0x5/0xb
ohci1394: fw-host0: SelfID received outside of bus reset sequence

is not good. Could you try to deactivate firewire and retry?
energyman76b is offline   Reply With Quote
Old 07-22-05, 01:40 PM   #5
Santiago
Registered User
 
Join Date: Jul 2005
Posts: 4
Default Re: X instafreeze with 7668/2.6.11-1.1369_FC4/gf4mx4000

Sorry for the thread revival, been busy, only just got round to looking into this again.

Tried all of those, bar the bios flash (can't find a bios!)- same result, no firewire mess, but Xid : 13 in dmesg. Box only responds to ssh and the power button (shuts down when pressed) - keyboard doesn't get through at all.

I'm going to try out some older drivers / other kernels / prebuilt stuff from livna.org and atrpms and (if that fails) e-mail the ladies and gents at nvidia, unless you've got any other suggestions?

Cheers,
James.
Santiago is offline   Reply With Quote
Old 07-25-05, 11:12 AM   #6
Santiago
Registered User
 
Join Date: Jul 2005
Posts: 4
Default Re: X instafreeze with 7668/2.6.11-1.1369_FC4/gf4mx4000

Solution found:

add selinux=0 to kernel arguments
reinstall as usual

...which then led to the mouse moves but ui frozen bug, which I've managed to solve by adding the following to xorg.conf (thanks, Shenwo!)

Option "RenderAccel" "0"
Option "nvagp" "0"
Option "HWCursor" "false"

Not looking forward to making it do anything in opengl though...mind you it only needs to run stepmania on this mythtv box, and it seems to do that admirably.

Last edited by Santiago; 07-25-05 at 04:10 PM.
Santiago is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 11:49 AM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.