On 03/04/2014 02:31 PM, m.roth at 5-cent.us wrote: > Kenny Noe wrote: >> My apologies.... what is top post and how am I doing this? >> >> I thought I was just replying to the mailing list... Hit reply and type >> my message. (I'm such a noobie) >> >> I did find dd files that have the driver update but am lost on trying to >> get these into the install. Sorry but I don't understand what you are >> saying. >> >> I appreciate your willingness to help and all the others that have >> replied. >> My apologies for being frustrating. I'll have to read more. > > You just top posted, again. #0: fuck Outlook, and anything like it. > FOLLOW, or intercollate, with the responses to your email. Follow, as in > put your response AT THE BOTTOM, of the email, not the top. > > Just the way I'm responding to the email, above. Think of it as a > conversation - you know what someone's said, *before* you respond. Top > posting means I have no idea what you're responding to - you're not > talking to someone in person.... And for anyone coming into an email > thread late... I, and I think most folks, have *zero* intention of going > to the bottom of an email which contains everything said in the thread, > esp. with nothing edited out, and reading down a message, then paging up > to read the response, then paging up *again* to read the next response. > > That's a M$ asinine introduction, and I despise it, since it makes it > incredibly difficult to follow what's going on. > > I dunno, though - just dd'ing in the driver isn't going to work, if you > mean that you dd'd the driver itself in, or was there an .rpm? If the > latter, you need to find out what it does when it installs - where the > actual driver's supposed to go, in what subdirectory, and then, of course, > the last step would be to insmod it, and *then* rebuild the initrd so that > it's included on boot. > > mark Google for "anaconda driverdisk", and you will find many write-ups on howto supply drivers during installation. Thomas