Pandu Poluan wrote: > > > On Oct 15, 2013 10:51 AM, "Dale" <rdalek1...@gmail.com > <mailto:rdalek1...@gmail.com>> wrote: > > > > Howdy, > > > > I ordered the new mobo as much as I needed to wait. The mobo is the > > same brand but a different chipset and a couple other things are > > different. I have already built a kernel for those changes. I plan to > > put everything on the old mobo on the new mobo. That includes the CPU. > > I'm pretty sure this will not be needed but want to ask to be sure. Do > > I need to do a emerge -e world or should it "just work" like it is? > > Since the CPU is going to be the exact same CPU, I'm thinking it is not > > needed. I do have march=native set in make.conf. > > > > Thoughts? Thanks. > > > > Personally, I think all you need to do is to ensure that the kernel > has all the drivers it needs to speak to the new mobo. Other members > of the @world set relies on the drivers in the kernel. > > But I don't use any GUI or audio; if you're using a GUI and/or audio, > you might also have to re-emerge the relevant bits. > > BSTS: just re-emerge @world :-) > > Rgds, > -- >
It uses the same audio chip so that should be OK but that is something that I hadn't thought of tho. I have a seperate video card which will be moving over as well. So that *should* work. We hope. I'm hoping this will be as painless as I hope it will be. I just got to remember how to hook the drivers up. Especially the first one. I certainly want sda to be correct. ;-) Thanks. You thought of something I hadn't thought of. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
