Well close, will try again tomorrow

Ok, run as root chmod +x /etc/rc.d/rc.networkmanager and that should fix that problem when you reboot.

See you tomorrow. At least we all know that your wireless can be made to work again.

That was it. We are up and running again. I actually get to put solved on something. Thanks that was great. I hope the rest of this works out as well. Will talk to you later.

After checking, I really should have told you to run (as root) instead (insmod wants a path to a file, while modprobe is smart enough to look in the right places). "b44" is the kernel module that your system was using to bring up your wired connection before and it comes with the slackware kernel. Your system really should be able to load b44 without any help from you, but first things first.

If eth0 does come back to life, you can use NM to configure your wired connection too. Some folks use NM for the wireless connections and /etc/rc.d/rc.inet1 for wired connections, but if you have a laptop you might as well have NM handle both types of connections for you.

Yep that took care of cable problem too.

Now how do I mark a problem solved?

I think it is on the "Thread Tools" pull-down at the top.

However, when you reboot now, does eth0 show up on its own? Or do you have to run the modprobe command?

It really should show up on its own.

EDIT: You may have a different opinion (hey, it's your machine, not mine!), but I don't think your problem is solved until you can boot up, log into KDE, and your wired connection (if the ethernet cable is plugged in, of course) and your wireless connection connect without you having to load kernel modules by hand.

Had to run modprobe after reboot so I guess still have some work to do

Yeah, that's not good. You can "fix" it by adding the line /sbin/modprobe b44 at the very end of /etc/rc.d/rc.modules.

That should do the trick for you.

I suspect that the SBo broadcom packages blacklisted the b44 module, which would be why your system all of a sudden doesn't think that kernel module should be automatically loaded.
However, my Day Job(TM) is software engineering and that would drive me to figure out why such a system doesn't load the correct kernel modules by itself.

Software engineering, I don't believe, is *your* Day Job; if you just want the *bleeping* thing to work and don't really care why it is acting stupid, then add the line to the end of /etc/rc.d/rc.modules and be happy. (That's not meant as an insult or anything like that. It is an absolutely rational position to take.)

God knows I've done something like that a few times with my Windows boxes.

If you mean
it tells me that its up to date no new kernel dependencies loaded. But /sbin/modprobe b44 brings it right back up

Nope I'm a cop and an instructor at MCC, as well as a farmer in the evening. I do however intend to actually learn slackware this time, so I do not intend to give up, and I like knowing how things work as well as that they just do.

Sorry.

I should have written...(I'm late responding tonight since I'm trying to upgrade my wife's Windows 7 laptop to Windows 10. That's the only machine in the house that is giving me a hard time with the upgrade.)

That did it. Rebooted and came up ready to go both wired and wireless. Did my wifes win 7 to win 10, took forever but it pretty much did itself. WIll mark this thread solved, thanks for all the help. I managed to get flash up and running in fire fox, not Konqueror, but am doing more with it than ever. Appreciate all the help.