X crashes under SuSE 9.0
Hi all, I'm new to the list. My name is Eric Pierce. I'm having some problems with my new SuSE 9.0 network install. Read on if you have a minute. My network install went fine. However, X will load up and freeze under a minute. I can swirl around the mouse for 10-20 seconds then everything freezes up. I'm unable to jump to other terminals at this point. The kernel, however, is still purring along. I can ssh into the machine. But killing X remotely doesn't give me back any control over said machine. I've tried quite a few things to figure this out, but to no avail. I deleted the XF86Config to get a fresh start and ran Sax2. Sax2 crashes in less than a minute after X is up. I also tried using my working XF86Config file from SuSE 8.2, but that didn't help any (ie., X still froze). I have 2 devices that are getting different IRQ assignments under SuSE 9.0 than what they got under 8.2. 8.2 had: 10: 2 XT-PIC ohci1394, Intel 82801BA-ICH2 11: 30 XT-PIC eth0 9.0 had: 5: 25 XT-PIC eth0, ohci1394 Everything is the same except for these 2 devices grabbing IRQ 5 (they had 10 & 11 under SuSE 8.2). I'm not so sure if this IRQ reassignment under 9.0 is really the problem anyhow. I popped out the firewire card (ohci1394 above) so eth0 could grab IRQ 5 all for itself, but X still dies. I don't see anywhere in BIOS to reassign these particular IRQs. Not knowing exactly what I'm doing, I also tried setpci -s 02:08.8 INTERRUPT_LINE=11 (11 was what SuSE 8.2 put eth0 at). That went in quietly. I also did setpci -s 02:08.8 INTERRUPT_PIN=11 which went in quietly too. I reassigned the firewire card as SuSE8.2 had it as well, but I saw no change when doing 'cat /proc/interrupts'. I don't see any errors in /var/log/XFree86.0.log either. A few Warnings, but nothing that looks detrimental. I also tried pci=noacpi at bootup. When I 'dmesg' it suggested that I try this. Still no go. My video card is a NVidia TNT2 32MB / AGP. It more or less worked find with SuSE 8.2. I'm truly stumped on this one. Anyone have any ideas? Anyway, thanks for reading! Eric Pierce __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
On Friday 12 December 2003 04:31, Julie A wrote:
Hi all,
I'm new to the list. My name is Eric Pierce.
I'm having some problems with my new SuSE 9.0 network install.
(snip) Hi Eric/Julie I don't have any answers, but I do have a full SuSE9.0 Pro disc set if you want to try that, just in case it's a general SuSE problem with your hardware. I did experience a complete FUBAR about 18 months ago when trying to install SuSE8.1 on a new P4 system with an SIS 650/961 chipset. YAST incorrectly installed an SMP kernel, which froze as soon as the sound settings were touched. SuSE's knowledge base provided the answer: to install the generic kernel, which fortunately was provided on the installation discs. -- GT
On 2003-12-12 04:31:36 +0000 Julie A <juliebread@yahoo.com> wrote:
I'm having some problems with my new SuSE 9.0 network install.
http://sdb.suse.com/ has nothing interesting. http://hardwaredb.suse.com/ claims one of the TNT2 is "unknown" and the other has full support. Are you using the "nv" driver?
I'm not so sure if this IRQ reassignment under 9.0 is really the problem anyhow. I popped out the firewire card (ohci1394 above) so eth0 could grab IRQ 5 all for itself, but X still dies.
X does use the network, but you can test whether eth0 is a problem by using the network from the console before X starts. ping, lynx, ssh or something. Does it work?
My video card is a NVidia TNT2 32MB / AGP. It more or less worked find with SuSE 8.2.
I guess if you have bought the SuSE 9.0, then you get some support from SuSE themselves. -- MJR/slef My Opinion Only and possibly not of any group I know. Please http://remember.to/edit_messages on lists to be sure I read http://mjr.towers.org.uk/ gopher://g.towers.org.uk/ slef@jabber.at Creative copyleft computing services via http://www.ttllp.co.uk/
--- MJ Ray <mjr@dsl.pipex.com> wrote:
On 2003-12-12 04:31:36 +0000 Julie A <juliebread@yahoo.com> wrote:
I'm having some problems with my new SuSE 9.0 network install.
http://sdb.suse.com/ has nothing interesting. http://hardwaredb.suse.com/ claims one of the TNT2 is "unknown" and the other has full support. Are you using the "nv" driver? SuSE 8.2 (w/my NVidia TNT2 32mB) starts out with the 'nv' driver, and once I d/l NVidia's driver it goes with 'nvidia'. I installed the NVidia driver under 9.0, but nothing change for the better.
I'm not so sure if this IRQ reassignment under 9.0 is really the problem anyhow. I popped out the firewire card (ohci1394 above) so eth0 could grab IRQ 5 all for itself, but X still dies.
X does use the network, but you can test whether eth0 is a problem by using the network from the console before X starts. ping, lynx, ssh or something. Does it work?
Yep. I did a little browsing w/Lynx. I could also ssh into the problem box.
My video card is a NVidia TNT2 32MB / AGP. It more or less worked find with SuSE 8.2.
I guess if you have bought the SuSE 9.0, then you get some support from SuSE themselves.
You got me there. I freeloaded my copy. Thanks, Eric __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
On Sun, 2003-12-14 at 00:18, Julie A wrote:
--- MJ Ray <mjr@dsl.pipex.com> wrote:
I guess if you have bought the SuSE 9.0, then you get some support from SuSE themselves.
Hmmmm. I just tried SuSE's free installation support on my problem with D-link DSL-300G+. Guess what.... "Sir, unfortunatly networking services, network cards and routers are not covered by our free installation support:" How short sighted is that ? Plus the actuall problem is with their firewall scripts, not my ADSL/network card/router ! Oh well :-( I'll just fix it myself ! Peter
On 2003-12-14 00:18:55 +0000 Julie A <juliebread@yahoo.com> wrote:
SuSE 8.2 (w/my NVidia TNT2 32mB) starts out with the 'nv' driver, and once I d/l NVidia's driver it goes with 'nvidia'. I installed the NVidia driver under 9.0, but nothing change for the better.
In my experience, it never does, which is why I asked. I wonder if you can try the "vesa" driver to see if that avoids the locking up. After that, try "vga" as an act of desperation. Given that your network connection seems to work otherwise, I doubt that is the problem. If it still locks up with the vga driver, I'm stumped. Maybe someone who knows SuSE will have some better ideas to try. -- MJR/slef My Opinion Only and possibly not of any group I know. Please http://remember.to/edit_messages on lists to be sure I read http://mjr.towers.org.uk/ gopher://g.towers.org.uk/ slef@jabber.at Creative copyleft computing services via http://www.ttllp.co.uk/
MJ, That did it! 'vesa' worked in place of 'nv'. Incidentally, 'sax2' still wanted to use 'nv' as its default (so it would crash), but I found a sneaky binary called 'sax2-vesa'. Basically, Sax2 in vesa mode. That allowed me to turn on NVidia's 3D acceleration via Sax2. Strange. SuSE 8.2/X86Config used 'nv' w/o problems. What exactly is the difference between 'nv' & 'vesa'? How about I throw 'aa' in there and see what happens! ;) Anyway, much thanks to you, MJ! Eric Pierce --- MJ Ray <mjr@dsl.pipex.com> wrote:
On 2003-12-14 00:18:55 +0000 Julie A <juliebread@yahoo.com> wrote:
SuSE 8.2 (w/my NVidia TNT2 32mB) starts out with the 'nv' driver, and once I d/l NVidia's driver it goes with 'nvidia'. I installed the NVidia driver under 9.0, but nothing change for the better.
In my experience, it never does, which is why I asked. I wonder if you can try the "vesa" driver to see if that avoids the locking up. After that, try "vga" as an act of desperation. Given that your network connection seems to work otherwise, I doubt that is the problem. If it still locks up with the vga driver, I'm stumped. Maybe someone who knows SuSE will have some better ideas to try.
-- MJR/slef My Opinion Only and possibly not of any group I know. Please http://remember.to/edit_messages on lists to be sure I read http://mjr.towers.org.uk/ gopher://g.towers.org.uk/ slef@jabber.at Creative copyleft computing services via http://www.ttllp.co.uk/
__________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/
On 2003-12-16 00:41:24 +0000 Julie A <juliebread@yahoo.com> wrote:
What exactly is the difference between 'nv' & 'vesa'?
XFree86 comes with many different display drivers. "vesa" only uses the basic VESA instructions and should work on nearly any modern PC card. It gives a reasonably good display, but I don't think it's accelerated at all and performance is quite bad compared to some of the other drivers. "nv" is the XFree86 driver for NVidia-based cards, which I think is accelerated but has no 3D support. I've found it works on most older NVidia cards without any problems. Sometimes there's a short delay before they upgrade it for new models (I don't think they get enough help.) Yours is the second I've heard of it breaking on, I think, which is even stranger as you say it used to work, so it shouldn't be the "new unsupported card" problem. "nvidia" is a proprietary software driver from the manufacturer, which has 3D support but has caused problems almost every time I've encountered it. You basically have to cry to NVidia if it breaks and hope they help you. I don't see that as a long-term solution. -- MJR/slef My Opinion Only and possibly not of any group I know. Please http://remember.to/edit_messages on lists to be sure I read http://mjr.towers.org.uk/ gopher://g.towers.org.uk/ slef@jabber.at Creative copyleft computing services via http://www.ttllp.co.uk/
On Tuesday 16 December 2003 18:34, MJ Ray wrote:
"nvidia" is a proprietary software driver from the manufacturer, which has 3D support but has caused problems almost every time I've encountered it.
I keep reading this, but I've never encountered it. For me, over various Linux Distributions and various nvidia cards from TNT2's to the low end Gforce 4 I am running now, I have never had a problem with either stability or installation that was caused by the Nvidia drivers. The closest I have come was my current machine when it was young, crashing infrequently. and that turned out to be a Kernel issue with AGP and the Chipset (Via) it just so happened that it only occurred when the Graphics subsystem was being pushed, therefore I suspected the Card drivers. In fact I'd go as far to say that the quality of both the Windows and Linux drivers for Nvidia cards has kept me buying them for 3-4 years now.
participants (5)
-
Graham Trott -
Julie A -
MJ Ray -
Peter Onion -
Wayne Stallwood