NIC problems in FC5 upgrade
Thanks Stan. Great idea. Here's my dmidecode result: # dmidecode 2.2 SMBIOS 2.3 present. 43 structures occupying 1783 bytes. Table at 0x000F8EB0. Handle...
Hi Schraalhans, Yes you're right. I checked the man pages for halt & shutdown and found that unless the system is in runlevel...
Michael Heiming
Load of really wacked out manic stuff clipped to save bandwidth at 60 bauds while using Western Electric KSR-33 teletype terminal} Well, Dear Morpheus -- may I call you "Morph" for short, perhaps...
Spescious hyperbole. Cute. =) You were born with all the knowledge in the world, weren't you, and never have had any problems with anything, have you? Nice.
Yep, no information at all like where I said I checked to see if the NIC had itself failed by booting up Windows and seeing that it worked in there, or where I said that I switched from DHCP to static information, or that I tried restarting the network service. Yep, didn't mention that at all, did I. Granted, I should have written down the exact error message, and copied the messages log to a USB drive and copied them over here. But then, I really didn't ask for anyone to figure the problem out for me, did ITo quote myself, I asked: "Is this a known issue with FC5?" I would think that I gave enough info that if someone did know of some issue with the FC5 that would cause symptoms like these, they would recognize it. And if not, they simply wouldn't reply and electrons get wasted.
Nope, same ole address. Hey, kill file me if you like. No tears shed here. =) Thanks for taking precious time out of your perfect day to bother pointlessly replying to an obviously incompetant idiot like me who must rank way below an iMac user on your scale of people you are superior to. I live to force you to read my terrible posts and make you reply to them, you know that don't you? My heart is a little warmer now. =)
Linux groups from Newsgroups