May 2004 - openSUSE AMD64 - openSUSE Mailing Lists

kernel update
by Franz Mach 01 Jun '04

01 Jun '04

Hi, I want to update the SuSE kernel from 2.6.4-52 to 2.6.4.54 with YOU. Is it necessary to reinstall drivers as nvida or oss after that ? (maybe a naiv question but i never updated the kernel before ;-) best regards Franz Mit schönen Grüßen von Yahoo! Mail - http://mail.yahoo.de

2 1

registration code for SuSE 9.0/AMD64
by M. Ranjit Mathews 31 May '04

31 May '04

The only thing I can seem to find of my SuSE 9.0/ AMD64 distribution is the original DVD and 2 manuals. I presume that my wife got rid of the box during house cleaning, thinking that only the manuals and DVD were necessary. Consequently, having reinstalled the OS from the patch CD Andi Kleen pointed me to in January followed by the original DVD, I find that I have no registration code for Online Updates. I had done an Online Update after the last install of the OS (actually, it was a preinstall by Monarch Computer). If I had entered a code and password from a registration card in the box to accomplish that update (I can't remember whether I entered these), are they saved in some database at SuSE in a form whereby they can be emailed to me so that I can once again take advantage of YOU? If not, short of buying another boxed copy of SuSE 9.0/AMD64, what can I do to gain access to YOU?

3 3

Re: registration code for SuSE 9.0/AMD64
by M. Ranjit Mathews 31 May '04

31 May '04

I looks like I wrote too soon. I have found a 14 character string that looks like a registration code on the back of the DVD's jewel box. I'm reinstalling yet again; when I'm done, I'll need to figure out what to use for a password for YOU. "M. Ranjit Mathews" <ranjit_mathews(a)yahoo.com> wrote:The only thing I can seem to find of my SuSE 9.0/ AMD64 distribution is the original DVD and 2 manuals. I presume that my wife got rid of the box during house cleaning, thinking that only the manuals and DVD were necessary. Consequently, having reinstalled the OS from the patch CD Andi Kleen pointed me to in January followed by the original DVD, I find that I have no registration code for Online Updates. I had done an Online Update after the last install of the OS (actually, it was a preinstall by Monarch Computer). If I had entered a code and password from a registration card in the box to accomplish that update (I can't remember whether I entered these), are they saved in some database at SuSE in a form whereby they can be emailed to me so that I can once again take advantage of YOU? If not, short of buying another boxed copy of SuSE 9.0/AMD64, what can I do to gain access to YOU?

1 0

Re: [suse-amd64] Anyone running MSI K8T Master2
by chu＠tes-mail.jpl.nasa.gov 30 May '04

30 May '04

Manfred is absolutely right; the wiring I did to drive my fans with low voltage is probably not the safest thing to do, and it may subject the other hardware to potential risks of short circuiting between the power supplies. Do so at your own risk. eyc

1 0

Re: [suse-amd64] AMD 64 Bit und 3D Grafik
by Sergei Klink 30 May '04

30 May '04

On May 29, 2004 10:30 pm, you wrote: > On Sun, 2004-05-30 at 16:06, Sergei Klink wrote: > > On May 29, 2004 09:34 pm, you wrote: > > > On Sun, 2004-05-30 at 06:31, Sergei Klink wrote: > > > > On May 28, 2004 11:22 pm, Joel Wiramu Pauling wrote: > > > > > Word to the Wise... Get Nvidia. > > > > > > > > > > Reasons: > > > > > > > > > > 1) Ati Driver support for linux even in 2.4 series kernels > > > > > and 32bit is bad. You will get artifacting in alot of > > > > > applications. (i.e celestia) and Even in games like UT2004. > > > > > WineX emulation support is also alot better with Nvidia. > > > > > > > > Btw, would be also nice to hear from anyone who tried the > > > > latest ATI drivers, which supposedly fix issues with winex. > > > > > > > > > Nvidia drivers have all the functionality of the windows > > > > > counterparts and have very good performance. With very few > > > > > errors and a very complete opengl implementation > > > > > > > > > > 2) Currently ati's drivers don't support 2.6 kernels it is > > > > > possible to get them working with significant effort. > > > > > > > > > > Nvidia: Currently support 2.6 kernels under 32bit right > > > > > from the nvidia page. > > > > > > > > Why's that? ATI's 32bit drivers had support for 2.5/2.6 > > > > kernels for quite a while, even the -test ones, although it > > > > wasn't updated quickly enough until 2.6.0 release(I was using > > > > it for a while without problems until I bought my amd64 box). > > > > IIRC I still wasn't able to use nvidia's drivers under 2.6 > > > > without patches from minion.de > > > > > > ATI's drivers are terrible under 2.6 I've just spent a > > > frustrating weekend of debuging the latest (3.9.0) to compile > > > and work on a 2.6.x fedora core... It's not fun. They have > > > screwed up big time... > > > > I suspect something very much Fedora related(if it would've been > > the same for XFree86). I used those in both Debian(sarge) and > > SuSE(9.0) with 2.6 without any problems. I wonder how'd you be > > debugging those, btw? :) > > Debugging the make scripts at least =-). I'm not a coder but I know > shell scripting quite well. Your right some of the issues are > primarily fedora related. But the problem occurs in many > distrobutions (i.e slackware) anything 2.6 built with regparms will > have the problem. (Most of the new distros) > I'll have to check, that was a while ago, I think it was 2.6.3 that I used. > > > Have a look: > > > http://www.rage3d.com/board/showthread.php?threadid=33757007 > > > > Besides, you're talking about xorg and not xfree86 support here > > as well. I'd really not expect them to take xorg seriously until > > it appears as the default in at least one more popular distro. > > Slackware =-) I beleive next release of Debian is going to xorg, > and also gentoo is xorg default. > Good to hear, actually. I'm all waiting for SuSE :) > > > rage3d forums are really good on info about the linux ati > > > drivers... > > > > > > As for nvidia not working... if you are using suse 9.1 kernel + > > > yast online update... you should have no problems... > > > > Same thing as getting patches from minion.de :P I didn't check if > > there's a SuSE rpm for fglrx as there was for 9.0, though. > > > > > > > 3) ATI do not support 64bit in either 2.4 or 2.6 Forget > > > > > about running accelerated ATI drivers on a 64bit platform > > > > > > > > I wouldn't say "forget", there are DRI drivers(and btw, they > > > > support 32bit apps unlike nvidia's drivers) for up to Radeon > > > > 9200, but they won't be much use for most games. > > > > > > ??? I've had no trouble running 32bit apps with nvidia's 64bit > > > drivers... I use winex all the time. And mplayer compiled for > > > 32bit. > > > > You're probably using the 32bit Mesa library still hanging around > > the system(which is what you'd be using with DRI drivers). It > > does work in the simplest cases, but, for example, running ET > > with it yields a lot of black textures where they shouldn't be as > > well as other weirdness(I mean, not just small artifacts, it's > > completely unplayable). In fact, I'm amazed it works at all. If > > you don't believe me, download the installer and see that the > > only library included is 64bit(or just poke around the site). > > I guarantee that i'm not using mesa for these applications. I think > I would notice it running maya if this was the case =-P. I beleive > it's probably because suse have been nice enough to patch and > backport the nvidia librarys and drivers to work with 9.1.... > Minion.de I no doubt your right.. NVIDIA through YOU... you are > definately wrong. > Both the drivers and the libraries are closed source, AFAIK, and I've not heard of a way to convert code compiled for amd64 to i386... Are you absolutely sure that you're running 32bit apps? > > Even the latest nvidia release doesn't support 32bit opengl, > > unless you take the libs from the 32bit release and set a > > variable which disables direct rendering(forgot what it was), > > which disables a lot of extensions, and is _very_ > > unstable(slower, too, obviously). > > > > > Yah the opensource dri drivers are messed up tho... Rendering > > > is all wrong in alot of apps. > > > > Can't blame them, but at least ATI _was_(emphasis) one of the > > companies that actually provided some information about its video > > cards. Meaning that I can play ET on my amd64 box now :) > > What is ET that you are revering too? I dare you to go and download > UT2004 demo for linux... and play it with ATI... you will see very > quickly how screwey the ATI drivers are. > Enemy Territory. Almost everything I need as far as gaming(not a lot, if you've noticed, that's why I have an option of using DRI :). I admit I haven't tried UT2004 on an ATI card(just UT2003, and I wasn't particularly happy with the game itself(I didn't see anything particularly weird with graphics, but I wasn't looking closely); neither did an nvidia card improve it :) > > > > > Nvidia AMD64 support is good under 2.4 series (again > > > > > working from the nvidia installer "Out of the box". 2.6 is > > > > > still getting there but it does work. suse 9.1 support > > > > > 64bit nvidia drivers on their 2.6 kernels "out of the box" > > > > > using YAST online update. You can also patch nvidia > > > > > installer for 2.6 64bit from minion.de. > > > > > > > > > > Short answer get a nvidia if you want to run linux. ATI are > > > > > years behind in their linux support. > > > > > > > > IMHO they both have terrible linux support. Last nvidia's > > > > driver release was in January, numerous issues discovered > > > > since then, and I don't see much of reaction from their side. > > > > 32bit emulation is another thing... > > > > ATI's drivers are (IMHO) OK for 32bit, and I certainly had > > > > better experience with them as far as stability goes(and > > > > working on both console and X), if you don't mind 24bit > > > > colour as the only option, but I still don't understand where > > > > are the 64bit drivers. Either they want to test them > > > > internally(and have the same set of functionality) before > > > > releasing, or they just decided to ignore us for a while, > > > > using existing DRI drivers as an excuse... > > > > > > I agree they both don't have GREAT linux driver support. But > > > NVIDIA is noticeably in front of the game compared to ATI. > > > > Don't know. Just because they tend to have more opengl extensions > > working doesn't necessarily put them ahead. In fact, the problems > > when working on the console(framebuffer especially) is enough to > > spoil any of the greatest features they might have over ATI for > > me. On the other hand, 24bit only colour support and rendering > > problems for ATI set them back just as well. > > Of course, none of the above is of any concern to people like > > recent Windoze converts, so apparently nobody causes enough noise > > for the companies to start doing anything about them. > > IMHO it's not even satisfactory for either(and AFAIK these are > > about the only choices we have for relatively low-cost cards), > > and comparing them at this low level is just useless. > > Hmm AFAIK Nvidia actually implements less Opengl Extensions now > than ATI... But ATI hasn't fixed problems in many of the simple > extensions that they've known about for a long time.... There is > also the whole memory leak with ALL ati drivers.... > My point exactly. And nvidia drivers crashing X when closing glxgears. And not being able to work on a framebuffer console(ok, I guess there could be workarounds, but there isn't much I can change in my setup; and I could really use it, since my monitor works better on higher frequencies). How long have those been around? You might not care about those, but they're just as serious to me. > > > > > Personally I would wait untill the nv 6800's come out in > > > > > another couple of week.. (if you have the money =-). The > > > > > 5200's are good if your on a budget. And if you can't wait > > > > > and have money the 5950's > > > > > > Latest nvidia release added support =-PPPP > > > > 5950? Yes. 6800? No. I've just grepped through > > ftp://download.nvidia.com/XFree86/Linux-x86/1.0-5336/README, and > > found no mention of 6800. > > It's on the website. > Okay, where?? I see the list of supported cards in front of me, and there's no mention of 6800 there, or maybe I'm blind and grep isn't working right. All I've seen is the 2D support in the nv driver from cvs, and rumours about nvidia making a new driver release "soon". I don't discard the possibility of them simply not updating the readme, but if you've seen it, could you please give a link? > > > > I haven't seen 6800 on the list of supported cards, btw, and > > > > I wouldn't count on a new driver release in a few weeks, > > > > either. FX5200(from Asus) worked horribly slow(no, not > > > > software emulation, but still slower than I expected) for > > > > me(yes, I visited the forums), I don't know if I'd recommend > > > > it to anyone for anything > > > > gaming-related(I was more than satisfied with a Radeon 9000 > > > > performance, so I figured this would be about right, turned > > > > out it's way too far...). Video overlay worked in a very > > > > strange way, too - I'm still trying to find the cause, > > > > though(on my athlon1.2 machine), sometimes the colour is > > > > completely messed up, or the aspect ratio is changed > > > > slightly(in any player). > > > > > > > > > are currently the best (Beating the radeon 9800 pro's > > > > > currently available from ati (yes rx chips are comming... i > > > > > know... but nvidia's nv6800 feature wise is alot better ) > > > > > > > > ... and AFAICS neither of them will be supported in linux for > > > > a while. > > > > > > See above > > > > Same :) Unless there are some "unofficial" drivers, which I doubt > > > > > > > Hope this answers some of your questions... > > > > > > > > > > On Sat, 2004-05-29 at 00:22, Markus Feilner wrote: > > > > > > Hello List, > > > > > > I am thinking about buying a AMD 64 System (Shuttle > > > > > > SN85G4 with an Athlon 64) and I am still searching for a > > > > > > Grafix CArd with 3D Support and good-qualitiy video > > > > > > rendering for 64bit Suse. I would prefer ATI cards, > > > > > > because i have had very good experience, but are there 64 > > > > > > bit drivers? > > > > > > If not, which cards can you recommend? > > > > > > > > > > > > [The System is going to be a Multimedia Game/Cinema/TV > > > > > > Streaming Server (...someday) which I want to be based on > > > > > > VLAN CLient or similar.] -- > > > > > > > > I think all of those are currently much, much easier to be > > > > done in 32bit(especially games and cinema).

1 0

Re: [suse-amd64] AMD 64 Bit und 3D Grafik
by Sergei Klink 30 May '04

30 May '04

On May 29, 2004 09:34 pm, you wrote: > On Sun, 2004-05-30 at 06:31, Sergei Klink wrote: > > On May 28, 2004 11:22 pm, Joel Wiramu Pauling wrote: > > > Word to the Wise... Get Nvidia. > > > > > > Reasons: > > > > > > 1) Ati Driver support for linux even in 2.4 series kernels and > > > 32bit is bad. You will get artifacting in alot of applications. > > > (i.e celestia) and Even in games like UT2004. WineX emulation > > > support is also alot better with Nvidia. > > > > Btw, would be also nice to hear from anyone who tried the latest > > ATI drivers, which supposedly fix issues with winex. > > > > > Nvidia drivers have all the functionality of the windows > > > counterparts and have very good performance. With very few > > > errors and a very complete opengl implementation > > > > > > 2) Currently ati's drivers don't support 2.6 kernels it is > > > possible to get them working with significant effort. > > > > > > Nvidia: Currently support 2.6 kernels under 32bit right from > > > the nvidia page. > > > > Why's that? ATI's 32bit drivers had support for 2.5/2.6 kernels > > for quite a while, even the -test ones, although it wasn't > > updated quickly enough until 2.6.0 release(I was using it for a > > while without problems until I bought my amd64 box). IIRC I still > > wasn't able to use nvidia's drivers under 2.6 without patches > > from minion.de > > ATI's drivers are terrible under 2.6 I've just spent a frustrating > weekend of debuging the latest (3.9.0) to compile and work on a > 2.6.x fedora core... It's not fun. They have screwed up big time... > I suspect something very much Fedora related(if it would've been the same for XFree86). I used those in both Debian(sarge) and SuSE(9.0) with 2.6 without any problems. I wonder how'd you be debugging those, btw? :) > Have a look: > http://www.rage3d.com/board/showthread.php?threadid=33757007 > Besides, you're talking about xorg and not xfree86 support here as well. I'd really not expect them to take xorg seriously until it appears as the default in at least one more popular distro. > rage3d forums are really good on info about the linux ati > drivers... > > As for nvidia not working... if you are using suse 9.1 kernel + > yast online update... you should have no problems... > Same thing as getting patches from minion.de :P I didn't check if there's a SuSE rpm for fglrx as there was for 9.0, though. > > > 3) ATI do not support 64bit in either 2.4 or 2.6 Forget about > > > running accelerated ATI drivers on a 64bit platform > > > > I wouldn't say "forget", there are DRI drivers(and btw, they > > support 32bit apps unlike nvidia's drivers) for up to Radeon > > 9200, but they won't be much use for most games. > > ??? I've had no trouble running 32bit apps with nvidia's 64bit > drivers... I use winex all the time. And mplayer compiled for > 32bit. > You're probably using the 32bit Mesa library still hanging around the system(which is what you'd be using with DRI drivers). It does work in the simplest cases, but, for example, running ET with it yields a lot of black textures where they shouldn't be as well as other weirdness(I mean, not just small artifacts, it's completely unplayable). In fact, I'm amazed it works at all. If you don't believe me, download the installer and see that the only library included is 64bit(or just poke around the site). Even the latest nvidia release doesn't support 32bit opengl, unless you take the libs from the 32bit release and set a variable which disables direct rendering(forgot what it was), which disables a lot of extensions, and is _very_ unstable(slower, too, obviously). > Yah the opensource dri drivers are messed up tho... Rendering is > all wrong in alot of apps. > Can't blame them, but at least ATI _was_(emphasis) one of the companies that actually provided some information about its video cards. Meaning that I can play ET on my amd64 box now :) > > > Nvidia AMD64 support is good under 2.4 series (again working > > > from the nvidia installer "Out of the box". 2.6 is still > > > getting there but it does work. suse 9.1 support 64bit nvidia > > > drivers on their 2.6 kernels "out of the box" using YAST online > > > update. You can also patch nvidia installer for 2.6 64bit from > > > minion.de. > > > > > > Short answer get a nvidia if you want to run linux. ATI are > > > years behind in their linux support. > > > > IMHO they both have terrible linux support. Last nvidia's driver > > release was in January, numerous issues discovered since then, > > and I don't see much of reaction from their side. 32bit emulation > > is another thing... > > ATI's drivers are (IMHO) OK for 32bit, and I certainly had better > > experience with them as far as stability goes(and working on both > > console and X), if you don't mind 24bit colour as the only > > option, but I still don't understand where are the 64bit drivers. > > Either they want to test them internally(and have the same set of > > functionality) before releasing, or they just decided to ignore > > us for a while, using existing DRI drivers as an excuse... > > I agree they both don't have GREAT linux driver support. But NVIDIA > is noticeably in front of the game compared to ATI. > Don't know. Just because they tend to have more opengl extensions working doesn't necessarily put them ahead. In fact, the problems when working on the console(framebuffer especially) is enough to spoil any of the greatest features they might have over ATI for me. On the other hand, 24bit only colour support and rendering problems for ATI set them back just as well. Of course, none of the above is of any concern to people like recent Windoze converts, so apparently nobody causes enough noise for the companies to start doing anything about them. IMHO it's not even satisfactory for either(and AFAIK these are about the only choices we have for relatively low-cost cards), and comparing them at this low level is just useless. > > > Personally I would wait untill the nv 6800's come out in > > > another couple of week.. (if you have the money =-). The 5200's > > > are good if your on a budget. And if you can't wait and have > > > money the 5950's > > Latest nvidia release added support =-PPPP > 5950? Yes. 6800? No. I've just grepped through ftp://download.nvidia.com/XFree86/Linux-x86/1.0-5336/README, and found no mention of 6800. > > I haven't seen 6800 on the list of supported cards, btw, and I > > wouldn't count on a new driver release in a few weeks, either. > > FX5200(from Asus) worked horribly slow(no, not software > > emulation, but still slower than I expected) for me(yes, I > > visited the forums), I don't know if I'd recommend it to anyone > > for anything > > gaming-related(I was more than satisfied with a Radeon 9000 > > performance, so I figured this would be about right, turned out > > it's way too far...). Video overlay worked in a very strange way, > > too - I'm still trying to find the cause, though(on my athlon1.2 > > machine), sometimes the colour is completely messed up, or the > > aspect ratio is changed slightly(in any player). > > > > > are currently the best (Beating the radeon 9800 pro's currently > > > available from ati (yes rx chips are comming... i know... but > > > nvidia's nv6800 feature wise is alot better ) > > > > ... and AFAICS neither of them will be supported in linux for a > > while. > > See above > Same :) Unless there are some "unofficial" drivers, which I doubt. > > > Hope this answers some of your questions... > > > > > > On Sat, 2004-05-29 at 00:22, Markus Feilner wrote: > > > > Hello List, > > > > I am thinking about buying a AMD 64 System (Shuttle SN85G4 > > > > with an Athlon 64) and I am still searching for a Grafix CArd > > > > with 3D Support and good-qualitiy video rendering for 64bit > > > > Suse. I would prefer ATI cards, because i have had very good > > > > experience, but are there 64 bit drivers? > > > > If not, which cards can you recommend? > > > > > > > > [The System is going to be a Multimedia Game/Cinema/TV > > > > Streaming Server (...someday) which I want to be based on > > > > VLAN CLient or similar.] -- > > > > I think all of those are currently much, much easier to be done > > in 32bit(especially games and cinema).

1 0

Re: [suse-amd64] Anyone running MSI K8T Master2
by chu＠tes-mail.jpl.nasa.gov 30 May '04

30 May '04

Manfred, Sorry about mis-spelling of your name. My typing is pretty bad, and I don't always see my mistakes when the character echoes are delayed over my sometimes problematic and always slow dial-up line. Now as to the power supply thing, I've tested a number of supplies from various vendors by intentionally shorting out the +12 to +5 lines while the system is on, and what usually happens is the power supply trips some kind of protection. In all cases, the +5 supply has much greater current capacity, and thus much less internal impedance, so it will bring down the +12 supply, causing an overload, and trip the +12 supply protector. Most will come back on as soon as I remove the short, but some required unplugging the line cord to reset, and a couple blew their internal fuses. I've yet to burn out any components on the motherboard doing this test ("so far so good"). Along this line, shorting out the +5 line to ground can cause a lot of fireworks, as the +5 supply usually has the most current capacity, so it will not trip unless its limit is exceeded. For example, even a 180 watt power supply will have about 30 amps on the +5 supply, and that's enough to burn out small wires without tripping the protection. I agree that if the power supply does not have adequate protection, it is possible to apply +12 volts to +5 volt devices if the fan connected across them should develop an internal short, but I think most modern power supplies must be protected from these events; the +12 traces on most circuit boards are just too close to the +5 traces to assume that no one will ever accidentally short them out. Now you have me thinking about the next test: put a fan across the two supplies and jam it so it can not turn, and see if the power supply will burn it out to an open circuit or turn it into slag that forms a short circuit. eyc

2 1

Re: [suse-amd64] Anyone running MSI K8T Master2
by chu＠tes-mail.jpl.nasa.gov 29 May '04

29 May '04

Manfred Kick wrote: >Slow and Easy going typically does the task already: > 80mm: 5V supply > 60mm: ~7,5V supply (they typically won't run below 6,2V) >For the latter, you can use a 12V line, reduced by a 27 Ohm resistor >(you may want to inject this into a separate Y-12/5V-cable :-). Attend >to the power marking ("W" ) on your fan! The resistor has to be able to >match it - don't take it too thin. For the latter, you might be able to connect the fan wires across the +5v and +12v wires on your power cable. This gives you 7v to drive the fan, which should be enough to get it running at a low speed. This avoids the use of a dropping resistor, which will be yet another source of heat that has to be removed. This is a trick for helping to make a desk top computer quieter, which was developed by a group of people who might refer to themselves as "underclockers"; when silence is more important than screaming fast CPU speeds. eyc

2 2

AMD 64 Bit und 3D Grafik
by Markus Feilner 29 May '04

29 May '04

Hello List, I am thinking about buying a AMD 64 System (Shuttle SN85G4 with an Athlon 64) and I am still searching for a Grafix CArd with 3D Support and good-qualitiy video rendering for 64bit Suse. I would prefer ATI cards, because i have had very good experience, but are there 64 bit drivers? If not, which cards can you recommend? [The System is going to be a Multimedia Game/Cinema/TV Streaming Server (...someday) which I want to be based on VLAN CLient or similar.] -- Mit freundlichen Grüßen Markus Feilner -- Linux Solutions, Training, Seminare und Workshops - auch Inhouse Feilner IT Linux & GIS Erlangerstr. 2 93059 Regensburg fon: +49 941 70 65 23 - mobil: +49 170 302 709 2 web: http://feilner-it.net mail: mfeilner(a)feilner-it.net

6 5

Can't start second processor on IWILL DK8S2
by bob＠Baruch.pantasys 28 May '04

28 May '04

I've installed SuSE 9.1 Professional on an iWill DK8S2 with 512 MB. This is a fairly generic dual processor Opteron MB. Kernel version is 2.6.4-52-smp no patches applied, straight from the Distribution. Runs fine as a single processor system; however, dual processor often won't complete boot (dies in the cold plug scan), or machine checks after some random (short) time: CPU0 machine check 4bank4: 0xb200002000010c0f RIP !INEXACT! 10:<ffffffff8034cfc0> accel_putcs+0x220/0x340 TSC 397101057 Sorry about any inaccuracies in the above, had to transcribe it by hand, so some number of f's or 0's may be off. However, this same board boots SuSE 8.0 Pro (2.4.19) on the same hardware. The bank interleave is disabled in the BIOS, but the node interleave is set to "auto". When node interleave is disabled, the machine check isn't seen, but the machine quietly hangs. Included below is the cat of /proc/cpuinfo and an edited dmesg from the faulting combination, followed by the 2.4.19 version. Any help getting the second processor reliably on-line is greatly appreciated. -bob ---- cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 5 model name : AMD Opteron(tm) Processor 242 stepping : 0 cpu MHz : 1603.663 cache size : 1024 KB fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow bogomips : 3153.92 TLB size : 1088 4K pages clflush size : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts ttp processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 5 model name : AMD Opteron(tm) Processor 242 stepping : 0 cpu MHz : 1603.663 cache size : 1024 KB fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow bogomips : 3203.07 TLB size : 1088 4K pages clflush size : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts ttp edited dmesg... No AGP bridge found Built 2 zonelists Kernel command line: root=/dev/hda3 vga=0x31a splash=silent console=tty0 desktop resume=/dev/hda2 showopts 3 maxcpus=2 bootsplash: silent mode. Initializing CPU#0 PID hash table entries: 16 (order 4: 256 bytes) CKRM Initialized time.c: Using 1.193182 MHz PIT timer. time.c: Detected 1603.663 MHz processor. Console: colour dummy device 80x25 Memory: 508716k/524224k available (3505k kernel code, 0k reserved, 1274k data, 228k init) Calibrating delay loop... 3153.92 BogoMIPS Security Scaffold v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode There is already a security framework initialized, register_security failed. Failure registering capabilities with the kernel selinux_register_security: Registering secondary module capability Capability LSM initialized Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Mount-cache hash table entries: 256 (order: 0, 4096 bytes) checking if image is initramfs...it isn't (no cpio magic); looks like an initrd Looking for DSDT in initrd ...No customized DSDT found in initrd! CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) POSIX conformance testing by UNIFIX Using local APIC NMI watchdog using perfctr0 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU0: AMD Opteron(tm) Processor 242 stepping 00 per-CPU timeslice cutoff: 1024.37 usecs. task migration cache decay timeout: 2 msecs. Booting processor 1/1 rip 6000 rsp 1001fd37f58 Initializing CPU#1 Calibrating delay loop... 3203.07 BogoMIPS CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) AMD Opteron(tm) Processor 242 stepping 00 Total of 2 processors activated (6356.99 BogoMIPS). ENABLING IO-APIC IRQs init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22, 2-23, 3-0, 3-1, 3-2, 3-3, 4-0, 4-1, 4-2, 4-3 not connected. ..TIMER: vector=0x31 pin1=2 pin2=-1 Using local APIC timer interrupts. Detected 12.528 MHz APIC timer. checking TSC synchronization across 2 CPUs: passed. time.c: Using PIT/TSC based timekeeping. Brought up 2 CPUs do_initcalls init_elf32_binfmt init_elf_binfmt NET: Registered protocol family 16 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20040326 No customized DSDT found! ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (00:00) PCI: Probing PCI hardware (bus 00) ... the first call_usermodehelper: pci_bus ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.GOLA._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.GOLB._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) SCSI subsystem initialized drivers/usb/core/usb.c: registered new driver usbfs drivers/usb/core/usb.c: registered new driver hub IOAPIC[0]: Set PCI routing entry (2-16 -> 0xa9 -> IRQ 16 Mode:1 Active:1) 00:00:07[A] -> 2-16 -> IRQ 16 IOAPIC[0]: Set PCI routing entry (2-17 -> 0xb1 -> IRQ 17 Mode:1 Active:1) 00:00:07[B] -> 2-17 -> IRQ 17 IOAPIC[0]: Set PCI routing entry (2-18 -> 0xb9 -> IRQ 18 Mode:1 Active:1) 00:00:07[C] -> 2-18 -> IRQ 18 IOAPIC[0]: Set PCI routing entry (2-19 -> 0xc1 -> IRQ 19 Mode:1 Active:1) 00:00:07[D] -> 2-19 -> IRQ 19 IOAPIC[1]: Set PCI routing entry (3-1 -> 0xc9 -> IRQ 25 Mode:1 Active:1) 00:02:01[A] -> 3-1 -> IRQ 25 IOAPIC[1]: Set PCI routing entry (3-2 -> 0xd1 -> IRQ 26 Mode:1 Active:1) 00:02:01[B] -> 3-2 -> IRQ 26 IOAPIC[1]: Set PCI routing entry (3-3 -> 0xd9 -> IRQ 27 Mode:1 Active:1) 00:02:01[C] -> 3-3 -> IRQ 27 IOAPIC[1]: Set PCI routing entry (3-0 -> 0xe1 -> IRQ 24 Mode:1 Active:1) 00:02:01[D] -> 3-0 -> IRQ 24 IOAPIC[2]: Set PCI routing entry (4-1 -> 0xe9 -> IRQ 29 Mode:1 Active:1) 00:01:01[A] -> 4-1 -> IRQ 29 IOAPIC[2]: Set PCI routing entry (4-2 -> 0x32 -> IRQ 30 Mode:1 Active:1) 00:01:01[B] -> 4-2 -> IRQ 30 IOAPIC[2]: Set PCI routing entry (4-3 -> 0x3a -> IRQ 31 Mode:1 Active:1) 00:01:01[C] -> 4-3 -> IRQ 31 IOAPIC[2]: Set PCI routing entry (4-0 -> 0x42 -> IRQ 28 Mode:1 Active:1) 00:01:01[D] -> 4-0 -> IRQ 28 number of MP IRQ sources: 15. number of IO-APIC #2 registers: 24. number of IO-APIC #3 registers: 4. number of IO-APIC #4 registers: 4. testing the IO APIC....................... IO APIC #2...... .... register #00: 02000000 ....... : physical APIC id: 02 .... register #01: 00170011 ....... : max redirection entries: 0017 ....... : PRQ implemented: 0 ....... : IO APIC version: 0011 .... register #02: 02000000 ....... : arbitration: 02 .... IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 1 0 0 0 0 0 0 00 01 001 01 0 0 0 0 0 1 1 39 02 001 01 0 0 0 0 0 1 1 31 03 001 01 0 0 0 0 0 1 1 41 04 001 01 0 0 0 0 0 1 1 49 05 001 01 0 0 0 0 0 1 1 51 06 001 01 0 0 0 0 0 1 1 59 07 001 01 0 0 0 0 0 1 1 61 08 001 01 0 0 0 0 0 1 1 69 09 001 01 0 1 0 1 0 1 1 71 0a 001 01 0 0 0 0 0 1 1 79 0b 001 01 0 0 0 0 0 1 1 81 0c 001 01 0 0 0 0 0 1 1 89 0d 001 01 0 0 0 0 0 1 1 91 0e 001 01 0 0 0 0 0 1 1 99 0f 001 01 0 0 0 0 0 1 1 A1 10 001 01 1 1 0 1 0 1 1 A9 11 001 01 1 1 0 1 0 1 1 B1 12 001 01 1 1 0 1 0 1 1 B9 13 001 01 1 1 0 1 0 1 1 C1 14 000 00 1 0 0 0 0 0 0 00 15 000 00 1 0 0 0 0 0 0 00 16 000 00 1 0 0 0 0 0 0 00 17 000 00 1 0 0 0 0 0 0 00 IO APIC #3...... .... register #00: 03000000 ....... : physical APIC id: 03 .... register #01: 00030011 ....... : max redirection entries: 0003 ....... : PRQ implemented: 0 ....... : IO APIC version: 0011 .... register #02: 00000000 ....... : arbitration: 00 .... IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 001 01 1 1 0 1 0 1 1 E1 01 001 01 1 1 0 1 0 1 1 C9 02 001 01 1 1 0 1 0 1 1 D1 03 001 01 1 1 0 1 0 1 1 D9 IO APIC #4...... .... register #00: 04000000 ....... : physical APIC id: 04 .... register #01: 00030011 ....... : max redirection entries: 0003 ....... : PRQ implemented: 0 ....... : IO APIC version: 0011 .... register #02: 00000000 ....... : arbitration: 00 .... IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 001 01 1 1 0 1 0 1 1 42 01 001 01 1 1 0 1 0 1 1 E9 02 001 01 1 1 0 1 0 1 1 32 03 001 01 1 1 0 1 0 1 1 3A IRQ to pin mappings: IRQ0 -> 0:2 IRQ1 -> 0:1 IRQ3 -> 0:3 IRQ4 -> 0:4 IRQ5 -> 0:5 IRQ6 -> 0:6 IRQ7 -> 0:7 IRQ8 -> 0:8 IRQ9 -> 0:9 IRQ10 -> 0:10 IRQ11 -> 0:11 IRQ12 -> 0:12 IRQ13 -> 0:13 IRQ14 -> 0:14 IRQ15 -> 0:15 IRQ16 -> 0:16 IRQ17 -> 0:17 IRQ18 -> 0:18 IRQ19 -> 0:19 IRQ24 -> 1:0 IRQ25 -> 1:1 IRQ26 -> 1:2 IRQ27 -> 1:3 IRQ28 -> 2:0 IRQ29 -> 2:1 IRQ30 -> 2:2 IRQ31 -> 2:3 .................................... done. PCI: Using ACPI for IRQ routing PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off' PCI-DMA: Disabling IOMMU. vesafb: framebuffer at 0xfd000000, mapped to 0xffffff0000009000, size 8128k vesafb: mode is 1280x1024x16, linelength=2560, pages=2 vesafb: scrolling: redraw vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0 fb0: VESA VGA frame buffer device Initial HugeTLB pages allocated: 0 IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ ikconfig 0.7 with /proc/config* ... 2.4.19 cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 5 model name : AMD Opteron(tm) Processor 242 stepping : 0 cpu MHz : 1603.656 cache size : 1024 KB fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow bogomips : 3153.92 TLB size : 1088 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts ttp processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 5 model name : AMD Opteron(tm) Processor 242 stepping : 0 cpu MHz : 1603.656 cache size : 1024 KB fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow bogomips : 3203.07 TLB size : 1088 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts ttp 2.4.19 dmesg id 2 IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23 ACPI: IOAPIC (id[0x03] address[0xfebfe000] global_irq_base[0x18]) IOAPIC[1]: Assigned apic_id 3 IOAPIC[1]: apic_id 3, version 17, address 0xfebfe000, GSI 24-27 ACPI: IOAPIC (id[0x04] address[0xfebff000] global_irq_base[0x1c]) IOAPIC[2]: Assigned apic_id 4 IOAPIC[2]: apic_id 4, version 17, address 0xfebff000, GSI 28-31 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) Using ACPI (MADT) for SMP configuration information Checking aperture... CPU 0: aperture @ eef2000000 size 32 MB Aperture from northbridge cpu 0 too small (32 MB) No AGP bridge found Built 2 zonelists Kernel command line: root=/dev/hda5 vga=791 console=tty0 Initializing CPU#0 PID hash table entries: 16 (order 4: 256 bytes) CKRM Initialization CKRM Initialization done time.c: Using 1.193182 MHz PIT timer. time.c: Detected 1603.656 MHz processor. Console: colour dummy device 80x25 Memory: 509192k/524224k available (3620k kernel code, 0k reserved, 1282k data, 216k init) Calibrating delay loop... 3153.92 BogoMIPS Security Scaffold v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode There is already a security framework initialized, register_security failed. Failure registering capabilities with the kernel selinux_register_security: Registering secondary module capability Capability LSM initialized Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Mount-cache hash table entries: 256 (order: 0, 4096 bytes) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) POSIX conformance testing by UNIFIX Using local APIC NMI watchdog using perfctr0 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU0: AMD Opteron(tm) Processor 242 stepping 00 per-CPU timeslice cutoff: 1024.37 usecs. task migration cache decay timeout: 2 msecs. Booting processor 1/1 rip 6000 rsp 1001ff0bf58 Initializing CPU#1 Calibrating delay loop... 3203.07 BogoMIPS CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) AMD Opteron(tm) Processor 242 stepping 00 Total of 2 processors activated (6356.99 BogoMIPS). ENABLING IO-APIC IRQs init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22, 2-23, 3-0, 3-1, 3-2, 3-3, 4-0, 4-1, 4-2, 4-3 not connected. ..TIMER: vector=0x31 pin1=2 pin2=-1 Using local APIC timer interrupts. Detected 12.528 MHz APIC timer. checking TSC synchronization across 2 CPUs: passed. time.c: Using PIT/TSC based timekeeping. Brought up 2 CPUs NET: Registered protocol family 16 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20040326 No customized DSDT found! ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (00:00) PCI: Probing PCI hardware (bus 00) ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.GOLA._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.GOLB._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) SCSI subsystem initialized drivers/usb/core/usb.c: registered new driver usbfs drivers/usb/core/usb.c: registered new driver hub IOAPIC[0]: Set PCI routing entry (2-16 -> 0xa9 -> IRQ 16 Mode:1 Active:1) 00:00:07[A] -> 2-16 -> IRQ 16 IOAPIC[0]: Set PCI routing entry (2-17 -> 0xb1 -> IRQ 17 Mode:1 Active:1) 00:00:07[B] -> 2-17 -> IRQ 17 IOAPIC[0]: Set PCI routing entry (2-18 -> 0xb9 -> IRQ 18 Mode:1 Active:1) 00:00:07[C] -> 2-18 -> IRQ 18 IOAPIC[0]: Set PCI routing entry (2-19 -> 0xc1 -> IRQ 19 Mode:1 Active:1) 00:00:07[D] -> 2-19 -> IRQ 19 IOAPIC[1]: Set PCI routing entry (3-1 -> 0xc9 -> IRQ 25 Mode:1 Active:1) 00:02:01[A] -> 3-1 -> IRQ 25 IOAPIC[1]: Set PCI routing entry (3-2 -> 0xd1 -> IRQ 26 Mode:1 Active:1) 00:02:01[B] -> 3-2 -> IRQ 26 IOAPIC[1]: Set PCI routing entry (3-3 -> 0xd9 -> IRQ 27 Mode:1 Active:1) 00:02:01[C] -> 3-3 -> IRQ 27 IOAPIC[1]: Set PCI routing entry (3-0 -> 0xe1 -> IRQ 24 Mode:1 Active:1) 00:02:01[D] -> 3-0 -> IRQ 24 IOAPIC[2]: Set PCI routing entry (4-1 -> 0xe9 -> IRQ 29 Mode:1 Active:1) 00:01:01[A] -> 4-1 -> IRQ 29 IOAPIC[2]: Set PCI routing entry (4-2 -> 0x32 -> IRQ 30 Mode:1 Active:1) 00:01:01[B] -> 4-2 -> IRQ 30 IOAPIC[2]: Set PCI routing entry (4-3 -> 0x3a -> IRQ 31 Mode:1 Active:1) 00:01:01[C] -> 4-3 -> IRQ 31 IOAPIC[2]: Set PCI routing entry (4-0 -> 0x42 -> IRQ 28 Mode:1 Active:1) 00:01:01[D] -> 4-0 -> IRQ 28 number of MP IRQ sources: 15. number of IO-APIC #2 registers: 24. number of IO-APIC #3 registers: 4. number of IO-APIC #4 registers: 4. testing the IO APIC....................... IO APIC #2...... .... register #00: 02000000 ....... : physical APIC id: 02 .... register #01: 00170011 ....... : max redirection entries: 0017 ....... : PRQ implemented: 0 ....... : IO APIC version: 0011 .... register #02: 02000000 ....... : arbitration: 02 .... IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 1 0 0 0 0 0 0 00 01 001 01 0 0 0 0 0 1 1 39 02 001 01 0 0 0 0 0 1 1 31 03 001 01 0 0 0 0 0 1 1 41 04 001 01 0 0 0 0 0 1 1 49 05 001 01 0 0 0 0 0 1 1 51 06 001 01 0 0 0 0 0 1 1 59 07 001 01 0 0 0 0 0 1 1 61 08 001 01 0 0 0 0 0 1 1 69 09 001 01 0 1 0 1 0 1 1 71 0a 001 01 0 0 0 0 0 1 1 79 0b 001 01 0 0 0 0 0 1 1 81 0c 001 01 0 0 0 0 0 1 1 89 0d 001 01 0 0 0 0 0 1 1 91 0e 001 01 0 0 0 0 0 1 1 99 0f 001 01 0 0 0 0 0 1 1 A1 10 001 01 1 1 0 1 0 1 1 A9 11 001 01 1 1 0 1 0 1 1 B1 12 001 01 1 1 0 1 0 1 1 B9 13 001 01 1 1 0 1 0 1 1 C1 14 000 00 1 0 0 0 0 0 0 00 15 000 00 1 0 0 0 0 0 0 00 16 000 00 1 0 0 0 0 0 0 00 17 000 00 1 0 0 0 0 0 0 00 IO APIC #3...... .... register #00: 03000000 ....... : physical APIC id: 03 .... register #01: 00030011 ....... : max redirection entries: 0003 ....... : PRQ implemented: 0 ....... : IO APIC version: 0011 .... register #02: 00000000 ....... : arbitration: 00 .... IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 001 01 1 1 0 1 0 1 1 E1 01 001 01 1 1 0 1 0 1 1 C9 02 001 01 1 1 0 1 0 1 1 D1 03 001 01 1 1 0 1 0 1 1 D9 IO APIC #4...... .... register #00: 04000000 ....... : physical APIC id: 04 .... register #01: 00030011 ....... : max redirection entries: 0003 ....... : PRQ implemented: 0 ....... : IO APIC version: 0011 .... register #02: 00000000 ....... : arbitration: 00 .... IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 001 01 1 1 0 1 0 1 1 42 01 001 01 1 1 0 1 0 1 1 E9 02 001 01 1 1 0 1 0 1 1 32 03 001 01 1 1 0 1 0 1 1 3A IRQ to pin mappings: IRQ0 -> 0:2 IRQ1 -> 0:1 IRQ3 -> 0:3 IRQ4 -> 0:4 IRQ5 -> 0:5 IRQ6 -> 0:6 IRQ7 -> 0:7 IRQ8 -> 0:8 IRQ9 -> 0:9 IRQ10 -> 0:10 IRQ11 -> 0:11 IRQ12 -> 0:12 IRQ13 -> 0:13 IRQ14 -> 0:14 IRQ15 -> 0:15 IRQ16 -> 0:16 IRQ17 -> 0:17 IRQ18 -> 0:18 IRQ19 -> 0:19 IRQ24 -> 1:0 IRQ25 -> 1:1 IRQ26 -> 1:2 IRQ27 -> 1:3 IRQ28 -> 2:0 IRQ29 -> 2:1 IRQ30 -> 2:2 IRQ31 -> 2:3 .................................... done. PCI: Using ACPI for IRQ routing PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off' PCI-DMA: Disabling IOMMU. vesafb: framebuffer at 0xfd000000, mapped to 0xffffff0000009000, size 8128k vesafb: mode is 1024x768x16, linelength=2048, pages=4 vesafb: scrolling: redraw vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0 fb0: VESA VGA frame buffer device Initial HugeTLB pages allocated: 0 IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ CPU0: online domain 0: span 03 groups: 01 02 CPU1: online domain 0: span 03 groups: 02 01 ikconfig 0.7 with /proc/config* VFS: Disk quotas dquot_6.5.1 klog channel created (2097152 bytes) Installing knfsd (copyright (C) 1996 okir(a)monad.swb.de) NTFS driver 2.1.6 [Flags: R/O]. SELinux: Registering netfilter hooks Initializing Cryptographic API ACPI: Power Button (FF) [PWRF] ACPI: Processor [CPU1] (supports C1, 8 throttling states) ACPI: Processor [CPU2] (supports C1) Console: switching to colour frame buffer device 128x48 Real Time Clock Driver v1.12 Non-volatile memory driver v1.2 hw_random: AMD768 system management I/O registers at 0x5000. hw_random hardware driver 1.0.0 loaded ppdev: user-space parallel port driver --

1 0