Re: Big troubles running FreeBSD on a Shuttle nForce2
On Tue, Jan 20, 2004 at 09:08:53PM +, anubis wrote: > On Tue, 20 Jan 2004 02:26 am, Raphael Dinge wrote: > > I've installed a long ago FreeBSD 5.1 on my mother's computer which > > is a shuttle with nvidia nforce2 motherboard. The computer crashes > > for reasons I can't explain. Since 5.2 was out, I installed it, and > > the problems are still consistent. > There are a number of issues with this kind of machine and they arent > limited to freebsd. We have a number of these machines running windas > at work. 1 works perfectly and the others are a bit flakey. We had a > long look at this problem and what it comes down to is these machines > have shared memory for the video. They are very fussy about what kind > of ram they use. This is why when you start using the video heavily > there is problems. > > Our good machine used "good" ram and the other funky ones use > unsupported ram. > > There are 2 possible solutions. One solution is to look at the nvidia > site and only use the ram they suggest for igp boards. Second > solution is put in a seperate video card. I am using a stick of Crucial 256MB DDR266 PC2100 RAM. I picked it up a few months ago from www.ebuyer.com for £29.99. I have no problems with this, so it might be worth checking out. What I'd suggest is swap the RAM from your Shuttle to your Mum's Shuttle and see how you get on. If they switch around you can really be sure it is the RAM. Best wishes, -lewiz. -- I was so much older then, I'm younger than that now. --Bob Dylan, 1964. -| msn:[EMAIL PROTECTED] | jabber:[EMAIL PROTECTED] | url:www.lewiz.org |- pgp0.pgp Description: PGP signature
Re: Big troubles running FreeBSD on a Shuttle nForce2
On Tue, Jan 20, 2004 at 03:09:10PM +0100, Raphael Dinge wrote: > Those solutions sounds good to me. > Is there a sysutil that would heavily test the ram > in my very specific case ? http://www.memtest86.com/ Gautam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Big troubles running FreeBSD on a Shuttle nForce2
Hi Anubis, We had a long look at this problem and what it comes down to is these machines have shared memory for the video. There are 2 possible solutions. One solution is to look at the nvidia site and only use the ram they suggest for igp boards. Second solution is put in a seperate video card. Those solutions sounds good to me. Is there a sysutil that would heavily test the ram in my very specific case ? Many thanks for the quick answer, -- +=== Raphael Dinge | Ohm Force DSP developer & Software designer | DA Software mailto:[EMAIL PROTECTED] | www.ohmforce.com +=== ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Big troubles running FreeBSD on a Shuttle nForce2
On Tue, 20 Jan 2004 02:26 am, Raphael Dinge wrote: > Hi, > > I've installed a long ago FreeBSD 5.1 on my mother's > computer which is a shuttle with nvidia nforce2 > motherboard. > The computer crashes for reasons I can't explain. > Since 5.2 was out, I installed it, and the problems > are still consistent. > > The problem is that the computer is crashing (freezing or > suddenly rebooting). The problem occurs on both 5.1 and > 5.2. > > - In console vga text mode, the computer did not ever crash, >and I was available to 'make install' via ssh from my home >a big variety of different programs, > - When I launch X, the problems comes, what ever window >manager I used, namely WindowMaker and KDE 3. > - Crash can occurs when moving a window, launching an >application, clicking on a link in a web browser, > - The computer is stable running with X if I don't do >anything with the GUI. I can still use ssh to administrate >from my home flawlessly. > - Crashes are very likely to freeze the computer or to make >it reboot suddenly. Sometimes it will just crash X, > - Sometimes when X crash, I can see that KDE did catch >a "Bad drawable" error (this is all the local machine, no >distributed X), > - Sometimes when moving windows, I can see small horizontal >lines as if the screen was not refreshed well, > - I was thinking that it did come from the kernel modules, >so I tried : > - with or without acpi.ko (in 5.1 since acpi >won't run on 5.2 on this computer now) didn't change, > - with various X card driver, namely 'vesa', 'nv' and >'nvidia' from the ports, didn't change > - I didn't enable sound kernel module for now > - Enabling nvidia.ko in loader.conf always stall computer >startup after keyboard probe (did not try on 5.2) > - I don't use the onchip network controller (not supported >in 5.1), and did bought a network controller running >with sis, flawlessly. > > I must admit I'm completely lost with that problem, since > I have the same computer at home, but my mother's computer > was bought 1 year later after mine. > > I don't know from where to start, (hardware test, bios > params, bios revision, nforce2 motherboard support) since it > seems I can't find panic log (and I don't know if they exist > anyway). Googling and searching list archive did not > give me more informations. > > Any advice will be greatly apreciated. > > Many thanks, > There are a number of issues with this kind of machine and they arent limited to freebsd. We have a number of these machines running windas at work. 1 works perfectly and the others are a bit flakey. We had a long look at this problem and what it comes down to is these machines have shared memory for the video. They are very fussy about what kind of ram they use. This is why when you start using the video heavily there is problems. Our good machine used "good" ram and the other funky ones use unsupported ram. There are 2 possible solutions. One solution is to look at the nvidia site and only use the ram they suggest for igp boards. Second solution is put in a seperate video card. Note that there have been revisions on these boards so the one bought 1 year later may have significant changes to the bios and the chips such as the on board nics. The nforce 2 boards are great feature wise but they are a bit temperamental. I want to beat them like a red headed step child sometimes. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Big troubles running FreeBSD on a Shuttle nForce2
Hi, I've installed a long ago FreeBSD 5.1 on my mother's computer which is a shuttle with nvidia nforce2 motherboard. The computer crashes for reasons I can't explain. Since 5.2 was out, I installed it, and the problems are still consistent. The problem is that the computer is crashing (freezing or suddenly rebooting). The problem occurs on both 5.1 and 5.2. - In console vga text mode, the computer did not ever crash, and I was available to 'make install' via ssh from my home a big variety of different programs, - When I launch X, the problems comes, what ever window manager I used, namely WindowMaker and KDE 3. - Crash can occurs when moving a window, launching an application, clicking on a link in a web browser, - The computer is stable running with X if I don't do anything with the GUI. I can still use ssh to administrate from my home flawlessly. - Crashes are very likely to freeze the computer or to make it reboot suddenly. Sometimes it will just crash X, - Sometimes when X crash, I can see that KDE did catch a "Bad drawable" error (this is all the local machine, no distributed X), - Sometimes when moving windows, I can see small horizontal lines as if the screen was not refreshed well, - I was thinking that it did come from the kernel modules, so I tried : - with or without acpi.ko (in 5.1 since acpi won't run on 5.2 on this computer now) didn't change, - with various X card driver, namely 'vesa', 'nv' and 'nvidia' from the ports, didn't change - I didn't enable sound kernel module for now - Enabling nvidia.ko in loader.conf always stall computer startup after keyboard probe (did not try on 5.2) - I don't use the onchip network controller (not supported in 5.1), and did bought a network controller running with sis, flawlessly. I must admit I'm completely lost with that problem, since I have the same computer at home, but my mother's computer was bought 1 year later after mine. I don't know from where to start, (hardware test, bios params, bios revision, nforce2 motherboard support) since it seems I can't find panic log (and I don't know if they exist anyway). Googling and searching list archive did not give me more informations. Any advice will be greatly apreciated. Many thanks, Below is my latest dmesg : Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2-RELEASE #0: Sun Jan 11 04:21:45 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc09e1000. mptable_probe: MP Config Table has bad signature: F8/I Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) XP 2600+ (2079.56-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x681 Stepping = 1 Features=0x383fbff AMD Features=0xc040 real memory = 503250944 (479 MB) avail memory = 479174656 (456 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 5 entries at 0xc00fdf10 pcib0: at pcibus 0 on motherboard pci0: on pcib0 agp0: mem 0xd000-0xd3ff at device 0.0 on pci0 pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xe0084000-0xe0084fff irq 10 at device 2.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x10de) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.10, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. ohci1: mem 0xe0082000-0xe0082fff irq 11 at device 2.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: (0x10de) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci0: at device 2.2 (no driver attached) pci0: at device 5.0 (no driver attached) pci0: at device 6.0 (no driver attached) pcib1: at device 8.0 on pci0 pci1: on pcib1 pci_cfgintr: 1:6 INTA BIOS irq 11 sis0: port 0xc000-0xc0ff mem 0xdf00-0xdf000fff irq 11 at device 6.0 on pci1 sis0: Silicon Revision: DP83815D sis0: Ethernet address: 00:40:f4:60:74:15 miibus0: on sis0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci0: port 0xf000-0xf00f at device 9.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pcib2: at device 30.0 on pci0 pci2: on pcib2 pci2: at device 0.0 (no driver attached) pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: at port 0x3f7,0x3f0-0x3f5 irq
