Finally switched to linux... what now?

[enorbet2]

Arkain
AFAIK the differences are primarily which desktop you get ie ubuntu = gnome, kubuntu = kde, xubuntu = xfce, etc. Is it possible that you have a friend or a library service that would allow you to use broadband to get the iso? Even if you miraculously manage to average 10 mb/sec w/ dialup where half that is more common that is not only a very long time but also invites CRC errors. If you can't borrow broadband, I'd have a disk mailed to me.

[arkain101]

I think I checked my iso file, ill have to check again for errors. Will that suffice?

[arkain101]

I mean, there is a thing you can select that says "check for errors" or somthing ...will that tell me?

[enorbet2]

Hey Arkain
I have booted Ubuntu in all it's variations maybe a dozen times altogether so I don;t know about "check for errors". I do know about checksum and md5. see here:


cksum Linux Commands: Print CRC checksum and byte counts

How to check an MD5 hash on a file

[Southtown]

Originally Posted by arkain101

I mean, there is a thing you can select that says "check for errors" or somthing ...will that tell me?

Yeah, "Check disk for errors" at the splash menu. I use it before every install, and it did catch a bad one once so it works, at least for that release. Except if it rejects the disk, you don't know if it was the iso or the burn job. So you should still md5 the iso before hand (if you can boot linux some-other-how) so you don't end up burning a bad iso to a whole stack of blank disks.

[freeztar]

My problems have been traced back to a faulty DVD cable.
When I burned the new DVD (with a MD5 check), I was able to install slackware no problem. KDE works now!

Of course, I have several other problems now...

When I was trying to set up my wireless card, it disabled my external mouse (touchpad still works). Eth0 shows me as connected but I'm unable to get anything from Konquerer.

Also, I get an error message on boot that says it can not detect sound.

Fun stuff ahead, but at least it's working. Woohoo!

[enorbet2]

Originally Posted by freeztar

My problems have been traced back to a faulty DVD cable.
When I burned the new DVD (with a MD5 check), I was able to install slackware no problem. KDE works now!

Congratulations Freeze! It's tough to build something precise with coarse tools, especially the first go around. I'm glad you sharpened that scalpel and made your job possible and easy, at the very least by comparison.

Originally Posted by freeztar

Of course, I have several other problems now...

True. As I mentioned the great thing about Slackware is that it snowballs. It takes a little work to reach critical mass where the snowball starts gathering mass creating a solid core you will never lose but that means all the work you put in will continue to reward you as long as you continue to use it and grow.

Originally Posted by freeztar

When I was trying to set up my wireless card, it disabled my external mouse (touchpad still works). Eth0 shows me as connected but I'm unable to get anything from Konquerer.

OK Some of the hardcore CLI guys may give me grief but I am a firm believer in using the skills someone already has to good effect and blending pointy-clicky with sound cli work. So first of all it is a bit unlikely that your usable interface is eth0 since you're trying to configure "The name is the device name that your driver has loaded for the device." often wifi0, wlan0, ath0, etc depending on the card's appropriate driver. Look here
What's difference between eth0, wlan0, wifi0 ath0 etc. - NetStumbler.org Forums

You can look through dmesg for other drivers loading to determine what your wifi nic is called and if seen, google for the info, or look in KInfoCenter menuitem under the System section of the main "K" menu, lower lefthand corner by default.

Also you can try the KWifiManager in your main menu or, at first, open ControlCenter and seek the plus sign for the Internet & Network menuitem and there you will find a great deal of information and setup scripts in menu form (radio buttons and checkboxes). This is falling off a log.

I highly recommend you look in the /etc/rc.d/ directory because this is the repository of most of your important configs for hardware. This is specific to Slackware in it's completeness as some distros have kept it but considerably reduced (or even eliminated) it's role because these are manually edited scripts where the user (as root) can do damn near anything. Very powerful and auto backed up because so. The scripts are well documented with notes in the scripts themselves as well as manpages and help files so don't be afraid to browse - just don;t change anything you aren;t sure of - measure twice, cut once. Even if all you do is look through, say, "/etc/rc.d/rc.wireless" and "wireless.conf" there, and look back after you have employed ControlCenter, you will learn a valuable lesson.

Originally Posted by freeztar

Also, I get an error message on boot that says it can not detect sound.

While there are some cards that aren't supported or well supported, if yours works in Ubuntu it will also work in Slackware. It just has to be started manually with the command "alsaconfig". Then just open your favorite mixer and make sure volumes are up. If you want your system to boot each time to the volumes you set "man alsactl" will tell you how. Otherwise it will go back to default which is in some cases quite loud. Also there is a vast amount of info for tweaking

Main Page - AlsaProject

Originally Posted by freeztar

Fun stuff ahead, but at least it's working. Woohoo!

I completely agree. Again Congrats! So tell everyone.... Can you feel the solid?

[freeztar]

I'm not really concerned about my wireless NIC right now. It doesn't work good in Ubuntu, so it's likely a kernel level problem (though others claim that the updates work for them).

Keep in mind, I'm a newbie. I'm not afraid of CLI, but my knowledge is limited there.

If I could just get my wired ethernet, external mouse, and sound working, I'll be happy.

I'll try out the alsaconfig suggestion as root. I'll also keep a close eye on bootup and check out the /rc.d dir. Beyond that, I'm like a fish out of water.

[enorbet2]

Hey Freeze
Yeah a fish out of water, maybe, but one with a terralung, a brain, and good docs as well as a buddy(s) willing to help. Speaking of which if you use IRC do not go to #Linux without shields up, cloaking on, and plenty of photon torpedoes. However #slackware is full of good people who are very patient and helpful of all levels of new and crusty.

[freeztar]

Originally Posted by enorbet2

Hey Freeze
Yeah a fish out of water, maybe, but one with a terralung, a brain, and good docs as well as a buddy(s) willing to help. Speaking of which if you use IRC do not go to #Linux without shields up, cloaking on, and plenty of photon torpedoes. However #slackware is full of good people who are very patient and helpful of all levels of new and crusty.

I'm familiar with shields and photon torpedoes in Windoze, but what is the Linux equivalent? What are the best security tools for Linux?

Update, I installed Ubuntu 9.04 and it is working great! My wireless NIC (RTL8187B) finally works! My eternal, undying thanks to whoever finally sussed it and added it to the kernel!

So, I'm typing in Ubu now and considering trying the xorg comparison to get slackware fully functional. Any other advice I should know about?

(currently reloading packages )