Can't Boot Init 5 with Suse 10 OSS
I have an older Compaq Workstation SP700. I loaded Windows Server 2003
Enterprise without a hitch for a class that I just finished. It has 2
SCSI drives (the third failed recently), so I kept the Windows on drive
0, and put Suse 10 OSS on the second drive, drive 1. After the first
disk installed it did the reboot, then failed to load the graphical
server. I was able to finish the install, including downloading the
updates (except OpenOffice and the newer kernel). When I try a normal
boot it freezes around the time the firewall initializes. (During the
install it froze at the syslog entry). I can boot to init 3 no
problem. I can not start sax2 (screen goes blank and freezes the
computer). I can not access the graphic card settings using YaST2 (same
thing, it freezes). I tried doing:
# sax2 -a
and
# sax2 -l
to no avail. Starting init 5 from init 3 results in a freeze. This is
a dual cpu machine (Pentium II Xeon 450 mhz) with a Gbyte of RAM. It
appears that Suse is having trouble using both CPUs. To add some
headache, this machine uses a NVIDIA graphics chip. During the install
Internet update I did download the nvidia.sh script, I ran the script
and it put me back at the command line without reporting any errors. If
I run top it does not appear to see the second CPU. When I run dmesg I
see a few errors:
<snipped head>
Processor #1 6:5 APIC version 16
WARNING: maxcpus limit of 0 reached. Processor ignored.
Processor #0 6:5 APIC version 16
WARNING: maxcpus limit of 0 reached. Processor ignored.
<more snipped>
SMP mptable: no processors registered!
BIOS bug, MP table errors detected!...
... disabling SMP support. (tell your hw vendor)
<more snipped>
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 65536 bytes)
Detected 449.011 MHz processor.
<more snipped>
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 65536 bytes)
Detected 449.011 MHz processor.
On Thursday 18 May 2006 14:12, James Wright wrote:
SMP mptable: no processors registered! BIOS bug, MP table errors detected!... ... disabling SMP support. (tell your hw vendor)
Hi James, The above error message seems to indicate there might be a problem with the BIOS. Have you checked to see if it's the latest available? Carl
Carl Hartung wrote:
On Thursday 18 May 2006 14:12, James Wright wrote:
SMP mptable: no processors registered! BIOS bug, MP table errors detected!... ... disabling SMP support. (tell your hw vendor)
Hi James,
The above error message seems to indicate there might be a problem with the BIOS. Have you checked to see if it's the latest available?
Carl Not yet.... Doing so now.....
Thank you, -James W.
James Wright wrote:
Carl Hartung wrote:
On Thursday 18 May 2006 14:12, James Wright wrote:
SMP mptable: no processors registered! BIOS bug, MP table errors detected!... ... disabling SMP support. (tell your hw vendor)
Hi James,
The above error message seems to indicate there might be a problem with the BIOS. Have you checked to see if it's the latest available?
Carl Not yet.... Doing so now.....
Thank you,
-James W. Ok, it was a real PITA, but I got the BIOS updated. I somehow corrupted Server 2003, spent a couple of hours trying to fix that, then gave up. I installed XP Pro to create the ROM update diskette (no floppy drives except the machine I am working on). The new BIOS was created 7/13/99, so it isn't exactly new. I have started re-installing Suse 10, the first disk finished, computer rebooted, and froze at "Starting syslog services" again. I am currently finishing the install via failsafe mode, but it appears that I am going to be having the same problem.
- James W.
On Saturday 20 May 2006 11:15, James Wright wrote:
Ok, it was a real PITA, but I got the BIOS updated. I somehow corrupted Server 2003, spent a couple of hours trying to fix that, then gave up. I installed XP Pro to create the ROM update diskette (no floppy drives except the machine I am working on). The new BIOS was created 7/13/99, so it isn't exactly new. I have started re-installing Suse 10, the first disk finished, computer rebooted, and froze at "Starting syslog services" again. I am currently finishing the install via failsafe mode, but it appears that I am going to be having the same problem.
Hi James, How much are you charging yourself per hour? :-) Does your system match the specs on the following page? http://developer.novell.com/yes/75843.htm Carl
Carl Hartung wrote:
On Saturday 20 May 2006 11:15, James Wright wrote:
Ok, it was a real PITA, but I got the BIOS updated. I somehow corrupted Server 2003, spent a couple of hours trying to fix that, then gave up. I installed XP Pro to create the ROM update diskette (no floppy drives except the machine I am working on). The new BIOS was created 7/13/99, so it isn't exactly new. I have started re-installing Suse 10, the first disk finished, computer rebooted, and froze at "Starting syslog services" again. I am currently finishing the install via failsafe mode, but it appears that I am going to be having the same problem.
Hi James,
How much are you charging yourself per hour? :-)
not enough ;-)
Does your system match the specs on the following page?
http://developer.novell.com/yes/75843.htm
Carl Not quite, I believe that my cpu's are 450mhz, and an Elsa graphics card. Something that I noticed just now, is my dmesg came from the computer running in failsafe. Failsafe boot options include nosmp and maxcpu=0. This may have led me (us) in the wrong direction. I am starting to believe that the problem lies with the graphics card. Windows XP and Suse 10 determine that the card is NVidia TNT2/TNT2 Pro. I can get 1280x1024 in XP.
- James W.
two recommendations: 1) show us what "cat /proc/cpuinfo" returns. 2) try to start sax2 from console - in VESA mode. 3) the installation you did - was in graphical or text mode?
two recommendations: 1) show us what "cat /proc/cpuinfo" returns. In Failsafe Mode (the only way I can get to init 3) with option nosmp and maxcpu=0 (so this may not be relevent) is:
Alexey Eremenko wrote: linux:~ # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 5 model name : Pentium II (Deschutes) stepping : 3 cpu MHz : 449.011 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr bogomips : 899.09 _______________________________ After a reboot into failsafe without the nosmp and maxcpu=0 I now get: linux:~ # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 5 model name : Pentium II (Deschutes) stepping : 3 cpu MHz : 449.011 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr bogomips : 899.12 processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 5 model name : Pentium II (Deschutes) stepping : 3 cpu MHz : 449.011 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr bogomips : 897.99
2) try to start sax2 from console - in VESA mode.
linux:~ # sax2 --vesa 0:800x600@60 SaX: initializing please wait... SaX: no X-Server is running SaX: will start own server if needed SaX: including [Driver:0] profile: Depth24... SaX: including [Driver:0] profile: NVidia... SaX: calling [Driver:0] profile script: NVidia.sh SaX: startup (here is where it stops responding and I reboot) I get the same with lower resolutions too. I am using a CTX CRT monitor. I am running these tests through SSH to make it easier to paste the results. When I run sax2 the monitor goes black on the computer in question and locks the SSH session.
3) the installation you did - was in graphical or text mode?
I started out in graphical. When the first CD finished the reboot would not complete. I then finished the install by booting to failsafe. Thanks. - James W.
On Saturday 20 May 2006 14:50, James Wright wrote: Hi James, I have to apologize... your original post threw me completely off track. Your subject line and first paragraph contained important clues that I overlooked because they were overshadowed by the volume of information you later supplied. Those clues were:
When I try a normal boot it freezes... I can boot to init 3 no problem.
and
I can not start sax2 (screen goes blank and freezes the computer).
and
I can not access the graphic card settings using YaST2 (same thing, it freezes).
If you'd simply stopped there, I and others would have immediately recognized this as a very common problem... affectionately known as the 'black screen of death'. ;-) This is a graphics adapter configuration problem. It *isn't* necessarily just a driver/module problem, but it's too soon to make that determination. In the meantime, chances are very good that the whole of your Linux system is correctly installed. You just can't run it in graphics mode, i.e. use X, until this part of your configuration is straightened out. The few threads I've been able to study show that people have successfully run SuSE 9.1 Pro on that hardware... some even in dual head mode... but they've had to pay particular attention to the allocation of resources in the BIOS... like the 'old days.' ;-) Fortunately, being able to operate at run level 3 makes diagnostics and configuration 'tweaking' a lot easier. Ready to 'start over' with some targeted diagnostics? Carl
Carl Hartung wrote:
Fortunately, being able to operate at run level 3 makes diagnostics and configuration 'tweaking' a lot easier. Ready to 'start over' with some targeted diagnostics?
Carl I am ready to rock and/or roll ;-). Sorry about the flood of information. Had I realized that the nosmp and maxcpu settings were being applied when booting into safemode I would have realized that this was a graphics problem. Just to add some info, the BIOS has a setting for IRQs. I will have to look to see what I can actually change, but everything was set to IRQ 11. I seem to remember that I could either use IRQ 11 or change that setting to 'Disable', I don't think that I could actually change which IRQ was being used for each individual piece of hardware. I am ready to follow any advice, tests, ect. Thanks for being so helpful. I see that you jump into a lot of threads with some great advice.
- James W.
On Saturday 20 May 2006 23:45, James Wright wrote:
I am ready to rock and/or roll ;-). Sorry about the flood of information.
Sorry I didn't focus a little longer on the subject line! ;-) I don't know how comfortable you are working in command line mode. Do you know how to launch YaST's ncurses interface? Are you familiar with mc? Can you change file ownership and permissions?... do basic things like create/remove directories, rename and copy files? I'd just like to know how 'finely grained' my writing of instructions should be. ;-) The first thing I'd do is reset the default to runlevel 3. That way, every time I miss the boot menu countdown timer or forget that I can't boot to runlevel 5, I avoid having to hard reset the system unnecessarily. The default is set in /etc/inittab: # The default runlevel is defined here id:5:initdefault: Change '5' to '3'. The next thing I'd do is pull some information together and e-mail it to me :-) hwinfo > /home/james/forensics/hwinfo.txt lspci -v > /home/james/forensics/lspci.txt lsmod > /home/james/forensics/lsmod.txt cp /etc/X11/xorg.conf /home/james/forensics/xorg.conf cp /var/log/messages /home/james/forensics/messages.txt cp /var/log/Xorg.0.log /home/james/forensics/Xorg.0.log.txt cp /var/log/Xorg.99.log /home/james/forensics/Xorg.99.log.txt cp /var/log/SaX.log /home/james/forensics/SaX.log.txt tar and compress it so it's suitable for e-mail: cd /home/james/forensics tar -czf jamesdata.tar.gz *.txt I'll catch up with you tomorrow, James, it's very late and I'm beat! Carl
Well this seems to be just a video issue. I can do a normal (not failsafe) boot to init 3, as long as 'vga=normal' is set in the grub boot parameters. The graphics card is an Nvidia TNT2/TNT2 Pro. I downloaded the Nvidia driver installation script that supports this card, NVIDIA-Linux-x86-1.0-6629-pkg1.run. When I run the script I get the rivafb warning, then the install continues. It reached 100%, then goes to a screen that says it failed to build the driver. Below is a snipped version of the log: NVIDIA: calling KBUILD... make CC=cc KBUILD_VERBOSE=1 -C /usr/src/linux SUBDIRS=/tmp/selfgz7426/NVIDI A-Linux-x86-1.0-6629-pkg1/usr/src/nv modules mkdir -p /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/.tmp_vers ions WARNING: Symbol version dump /usr/src/linux-2.6.13-15/Module.symvers is missing; modules will have no dependencies and modversions. make -f scripts/Makefile.build obj=/tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629 -pkg1/usr/src/nv echo \#define NV_COMPILER \"`cc -v 2>&1 | tail -n 1`\" > /tmp/selfgz7426/NVI DIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv_compiler.h cc -Wp,-MD,/tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/.nv.o .d -nostdinc -isystem /usr/lib/gcc/i586-suse-linux/4.0.2/include -D__KERNEL __ -Iinclude -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -Werror-impli cit-function-declaration -fno-strict-aliasing -fno-common -ffreestanding -O2 -fomit-frame-pointer -pipe -msoft-float -mpreferred-stack-boundary=2 -fn o-unit-at-a-time -march=i586 -mregparm=3 -mtune=i686 -Iinclude/asm-i386/mach -generic -Iinclude/asm-i386/mach-default -Wdeclaration-after-statement -Wno- pointer-sign -I/tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv -Wa ll -Wimplicit -Wreturn-type -Wswitch -Wformat -Wchar-subscripts -Wparenthese s -Wpointer-arith -Wno-multichar -Werror -O -fno-common -MD -Wno-cast-qu al -Wno-error -D_LOOSE_KERNEL_NAMES -D__KERNEL__ -DMODULE -DNTRM -D_GNU_SOU RCE -D_LOOSE_KERNEL_NAMES -D__KERNEL__ -DMODULE -DNV_MAJOR_VERSION=1 -DNV_M INOR_VERSION=0 -DNV_PATCHLEVEL=6629 -DNV_UNIX -DNV_LINUX -DNV_INT64_OK -DNVCPU_X86 -UDEBUG -U_DEBUG -DNDEBUG -DNV_REMAP_PFN_RANGE_PRESENT -DN V_CHANGE_PAGE_ATTR_PR ESENT -DNV_PCI_DISABLE_DEVICE_PRESENT -DNV_PCI_GET_CLASS_PRESENT -DMODULE - DKBUILD_BASENAME=nv -DKBUILD_MODNAME=nvidia -c -o /tmp/selfgz7426/NVIDIA-Lin ux-x86-1.0-6629-pkg1/usr/src/nv/.tmp_nv.o /tmp/selfgz7426/NVIDIA-Linux-x86-1 .0-6629-pkg1/usr/src/nv/nv.c In file included from include/linux/list.h:7, from include/linux/wait.h:23, from include/asm/semaphore.h:41, from include/linux/sched.h:20, from include/linux/module.h:10, from /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src /nv/nv-linux.h:52, from /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src /nv/nv.c:14: include/linux/prefetch.h: In function ‘prefetch_range’: include/linux/prefetch.h:62: warning: pointer of type ‘void *’ used in a rithmetic In file included from include/linux/dmapool.h:14, from include/linux/pci.h:870, from /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src /nv/nv-linux.h:75, from /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src /nv/nv.c:14: include/asm/io.h: In function ‘check_signature’: include/asm/io.h:253: warning: wrong type argument to increment In file included from /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src /nv/nv.c:14: /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv-linux.h:203:5: warning: "NV_ENABLE_MEM_TRACKING" is not defined /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv-linux.h:231:5: warning: "NV_ENABLE_MEM_TRACKING" is not defined /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c:223:5: warnin g: "NV_ENABLE_MEM_TRACKING" is not defined /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c: In function ‘nvidia_init_module’: /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c:930: warning: ‘pm_register’ is deprecated (declared at include/linux/pm.h:107) /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c: In function ‘nvidia_exit_module’: /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c:1051: warning : ‘pm_unregister’ is deprecated (declared at include/linux/pm.h:112) /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c:1097:5: warni ng: "NV_ENABLE_MEM_TRACKING" is not defined /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c: In function ‘_get_phys_address’: /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c:2509: warning : passing argument 1 of ‘pmd_offset’ from incompatible pointer type /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c: In function ‘nv_agp_init’: /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c:2991: error: implicit declaration of function ‘inter_module_get’ /tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c:2992: warning : ‘inter_module_put’ is deprecated (declared at include/linux/module.h:5 73) make[3]: *** [/tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.o ] Error 1 make[2]: *** [_module_/tmp/selfgz7426/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src /nv] Error 2 NVIDIA: left KBUILD. nvidia.ko failed to build! make[1]: *** [module] Error 1 make: *** [module] Error 2 -> Error. ERROR: Unable to build the NVIDIA kernel module. ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com. If anyne knows what to do about this, please clue me in. Thank you. - James W.
James Wright wrote:
Well this seems to be just a video issue. I can do a normal (not failsafe) boot to init 3, as long as 'vga=normal' is set in the grub boot parameters. The graphics card is an Nvidia TNT2/TNT2 Pro. I downloaded the Nvidia driver installation script that supports this card, NVIDIA-Linux-x86-1.0-6629-pkg1.run. When I run the script I get the rivafb warning, then the install continues. It reached 100%, then goes to a screen that says it failed to build the driver. Below is a snipped version of the log: Ok, the 6629 wasn't the last Nvidia driver to support the TNT2/TNT2 Pro card. I downloaded the 7167 driver and that installed fine. The computer still isn't booting to init 5 or with the boot parameter 'vga' set to anything but 'normal'. Sax2 still will not load. Here is what I have done:
Install 7167 driver. ran 'switch2nvidia' did a: # modprobe nvidia ran makedevices.sh tried init 5, which then said ready, but didn't go further. I hit CTRL-C and got dropped to the CLI. Tried startx, and the computer entirely froze. Added makedevices.sh to boot.local. Reboot. No go. Still freezes. Sax2 -m 0=nvidia reports that no screen is found. xorgcfg reports the same. I have been watching the 'Nvidia / AV Out Not Center' thread as well as http://www.linuxquestions.org/questions/showthread.php?t=380061. I checked out the threads in the Nvidia forums, others have similar problems, but not real solution. I should mention that the nvidia module is not getting loaded into the kernel, I seem to have to do it by hand each time. I'm still plugging away at this, and if I find a solution I will post it. I welcome any suggestions. Windows XP and Server 2003 have not problems with this card, so I assume the card is fine. - James W.
On Tuesday 23 May 2006 07:33, James Wright wrote:
Windows XP and Server 2003 have not problems with this card, so I assume the card is fine.
Hi James, The fact that your card still works under a M$ OS is interesting, but not particularly relevant. Linux is constantly progressing... unlike dinosaurs. ;-) Did you see this thread excerpt?:
Those cards are 6+ generations** (over 5 years**) old. ... Exactly! ... since one can buy a brand new (and _much_ faster than TNT2) nVIDIA card (geforce mx4000) which _is_ supported by nVIDIA's accelerated drivers, on AGP for less
[re TNT2] than UKP20 (or PCI for less than 30), then why not just do that to use xgl? Then sell the TNT2 on eBay (to a museum :-)
I hadn't realized the card was that old. Developers don't get much 'bang for the buck' maintaining drivers for obsolete hardware. In this case, X has progressed. So have graphics hardware capabilities (by leaps and bounds) and the graphics/3D applications that take advantage of them. It is looking to me like the driver for that card was maintained up to some 'final' version of X then dropped in favor of development supporting the newer generation cards, which incidentally are many times faster and relatively inexpensive. If you desperately need to use *that* specific card, then you'll need to 'fix' the driver yourself or downgrade to an earlier X that is supported by the driver and/or even downgrade to a compatible installation of Linux. Sorry, but that's how I'm beginning to interpret your situation. regards, Carl
Carl Hartung wrote:
If you desperately need to use *that* specific card, then you'll need to 'fix' the driver yourself or downgrade to an earlier X that is supported by the driver and/or even downgrade to a compatible installation of Linux. Sorry, but that's how I'm beginning to interpret your situation.
regards,
Carl
I am beginning to believe the same. I am going to re-install 10.0, install the correct legacy driver, modify boot.local and see what happens. If it doesn't work I may drop back to 9.3 or 9.2. I suppose that moving ahead to 10.1 isn't going to help at all..... - James W.
On Tuesday 23 May 2006 09:51, James Wright wrote:
I am beginning to believe the same. I am going to re-install 10.0, install the correct legacy driver, modify boot.local and see what happens. If it doesn't work I may drop back to 9.3 or 9.2. I suppose that moving ahead to 10.1 isn't going to help at all.....
Before going to all that work, there's a great deal of information provided with the legacy driver... I know because I downloaded it and all the incidental documentation surrounding it. If you take your time to just scan through it all, you'll eventually find which versions of X the driver was supported through and also what kernels have been tested plus any known errata and/or workarounds. I mean, if you're going to make the effort you might as well aim for the latest possible SUSE version the driver is known to work with and it can't hurt to have a lot more background knowledge about how to set the card up and how to use the supplied configuration/test utilities. Good luck & keep in touch! Carl
I mean, if you're going to make the effort you might as well aim for the latest possible SUSE version the driver is known to work with and it can't hurt to have a lot more background knowledge about how to set the card up and how to use the supplied configuration/test utilities.
Good luck & keep in touch!
Carl Thank you Carl. I am currently downloading 10.1 and plan on following
Carl Hartung wrote: the directions on http://en.opensuse.org/NVIDIA to a T. It appears as though it just may work. Looking further into the BIOS I have found that I can change the default IRQ from 11 to another number. Currently the video, IDE, and SCSI are all using IRQ 11. Is this a problem? And if it is, do I need to change it before I install 10.1? Thanks, James W.
On Tuesday 23 May 2006 15:34, James Wright wrote:
Thank you Carl. I am currently downloading 10.1 and plan on following the directions on http://en.opensuse.org/NVIDIA to a T. It appears as though it just may work. Looking further into the BIOS I have found that I can change the default IRQ from 11 to another number. Currently the video, IDE, and SCSI are all using IRQ 11. Is this a problem? And if it is, do I need to change it before I install 10.1?
I wouldn't expect this to cause a problem. The system and video card are older but still recent enough to understand IRQ sharing. You can always change it if you run into a problem, but I'd wait to see if having the correct module loading at boot doesn't straighten your graphics issue out, first. Carl
Carl Hartung wrote:
On Tuesday 23 May 2006 15:34, James Wright wrote:
Thank you Carl. I am currently downloading 10.1 and plan on following the directions on http://en.opensuse.org/NVIDIA to a T. It appears as though it just may work. Looking further into the BIOS I have found that I can change the default IRQ from 11 to another number. Currently the video, IDE, and SCSI are all using IRQ 11. Is this a problem? And if it is, do I need to change it before I install 10.1?
I wouldn't expect this to cause a problem. The system and video card are older but still recent enough to understand IRQ sharing. You can always change it if you run into a problem, but I'd wait to see if having the correct module loading at boot doesn't straighten your graphics issue out, first.
Carl
Thank you Carl, I am just finishing the new install (opted for 10.0 again). I have 9.2 and 9.3 handy to test if this doesn't work out. BTW, if you need to PM me, notice the e-mail change. I can't access my other account for the time being. - James W.
participants (4)
-
Alexey Eremenko -
Carl Hartung -
James Wright -
James Wright