FX

Sorry to say, but yes it is not supported in Linux. I have the same one. FX

Found this wallpaper over at ATU. Someone posted it and I found it kind of nice. :)

AI you can install KDE if you want to. Just "wajig install kde". Get the repos for your /etc/apt/sources.list that Cybr posted and within about 5 to 10 mins. depending on your connection you'll have KDE. Only problem I've notice with kde is if I my ac line on my laptop isn't plugged in it will kick me back to the log in a couple of times before it actually take hold and finally loads. Outside of that it runs fine. FX

Just to give some idea about this distro. Like I said earlier when I first installed ubuntu picked up my Atheros wireless card. Well I just finally got around to updating to the 2.6.8-smp kernel. I rebooted into the new kernel and I didn't have a wireless connection. So I went back and booted into the old kernel. Did a "wajig search madwifi" It came back with a list of "restricted kernel blah blah". One of them was for the matching smp kernel I just upgrade too. So I installed it. I then rebooted into the new smp kernel and bam I had wireless back. No messing around. IT JUST WORKED!!!! I am really liking this distro. /me steps off soapbox. FX Edit: Oh yea it also fixed the nVidia driver install also. Here is the exact pagckage i installed to get the wireless and nVidia drivers upgraded to the new kernel. linux-restricted-modules-2.6.8.1-3-686-smp

Well I am enjoying it. Believe it or not. :P Now if I could only get my pen drive to mount. Also not that it really matters but XMMS seems to be broke. I get a kind of long error when I try to load it. So using Music Player instead. Outside of those two things its running pretty good, even at a preview release yet. (Its suppose to be an official release sometime today or this month.) FX

I don't know. When I installed my pirated version of XP Pro on all of my pcs here I didn't even know Linux existed. FX

Open a terminal. Type "top". The column all the way on the left is the PID or process id. Find the one you want and the in another terminal type "killall kill <pid #>" If that doesn't work try "killall kill -9 <pid #>". The -9 is a no messing around, kill it "now" command. FX. P.S. Man I hope I got that explanation right.

Ubuntu after a "wajig install kde" FX

Hey cybr your never going to believe this!!!! The problem was with the wireless_ESSID name. I have mshome in small letters. I went into #ubuntu and they gave me a hand and suggested to put mshome in caps. The wireless fired right up. I had no idea that caps would have anything to do with it. I really do appreciate all your help last night. Starting to like Ubuntu a little more now. FX

Well I got my wireless somewhat working. I have signal strength on the monitor but cannot get to the lan or net. I have a dhcp isp, but I have the network here setup on static. Here is my /etc/network/interface configuration. Probably not right. I know some of what it means, but there are things that i don't really now. #Wireless Info # The loopback network interface auto lo iface lo inet loopback # The primary network interface #auto ath0 iface ath0 inet 192.168.0.6 #auto ath0 iface ath0 inet 192.168.0.6 wireless_mode managed wireless_essid mshome wireless_ap auto wireless_keymode open wireless_key1 wireless_defaultkey The cat5 onboard lan works great. Which is eth0. Thanks ahead of time. :) FX

Cybr I did follow the X-Config from my Fedora install, thats how I got it from a little box to a little bit bigger box. After doing the apt-get update and apt-get upgrade my screen is back to normal. I'm going to add the repo's that you have when I get home. (In class now). Add add the 2.6.8-1-smp kernel and the nVidia stuff. Then I'll work on the wireless. Am I mistaken with the results that I posted from iwconfig that it is partly setup? I was watching while the install was going on that Ubuntu did notice the Athreos card. ( I never spell that right ) :P So far is seems pretty neat. I'm gonna install on my desktop that dual boots with windows and see what that setup is like. Thanks again for the help and the postings here. FX

Well I have it installed and everything, well just about everything seems to work fine. I'm having a little trouble with the screen size. At first I could only get 640x480 and a little square 4x4 box for a desktop. Did some playing aroun in the XF86Config and have it at 1024x768 now BUT I still have like a 1in to 1 1/2 black space along the sides. Not sure really what to do with it. :( After I get that fixed I'll work on the wireless and other things. So if its possible would anyone have any ideas about my desktop size? Thanks in advance. FX Edit: Oh yea cybr I just ran iwconfig and this is what came up. Now I didn't load anything "extra" for the wireless. This is just from the stock install. ath0 IEEE 802.11 ESSID:"" Mode:Managed Frequency:2.412GHz Access Point: 00:00:00:00:00:00 Bit Rate:0kb/s Tx-Power:50 dBm Sensitivity=0/3 Retry:off RTS thr:off Fragment thr:off Power Management:off Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

From what I remember and I could be wrong Arch is something like Slack. You can but the commands you are typing into the /etc/rc.d/rc.local file for your wireless to start. That file is for any extra things that you want to have load on start. As your mouse if you have a usb one. Change the /dev/mouse to /dev/input/mice in your xorg.conf. You can also add under in the mouse "options" a new line "ZAxisMapping" "4 5". If you have already done all that, then just forget what I have just typed. FX

I don't understand. What are you trying to say cybr? FX

Its time for my to upgrade and here is what I have picked out. http://www.zipzoomfly.com/jsp/ProductDetai...ctCode=80098-21 http://www.zipzoomfly.com/jsp/ProductDetai...ductCode=241234 http://www.zipzoomfly.com/jsp/ProductDetai...uctCode=80701-R http://www.zipzoomfly.com/jsp/ProductDetai...ductCode=101559 http://www.zipzoomfly.com/jsp/ProductDetai...ductCode=323258 http://www.zipzoomfly.com/jsp/ProductDetai...ductCode=140018 I'll be dual booting with Slackware and XP. For some gaming purposes. Just wondering if the hardware I have picked out will run alright with Slack or Linux. Thanks for the advice a head of time. FX

Fresh install of Slack. Need to do something with the icons yet. FX

I could be wrong which I usually am, but isn't the CVS for Cedega available for a free download? I know it use to be. FX

Ah, ok, good. I was just wondering because I know how many times you have expressed your LOVE for Redhat/Fedora to me in #musb. ;) FX

tyme are you feeling alright? FX

So what your are saying linux_learner is not to operate the software near a microwave? FX

I can't wait until some has to "reboot" themselfs for the first time. Would there be a next? FX

Didn't know if I should post this in here or "other distro" but since its a networking thingy I thought it could go here. I'm using Driverloader with Fedora and it works for reaching the internet. I am having one problem though. When I click on the "network servers" or use SMB4K to search my lan network Samba will not see my "mshome" network. With the "network servers" icon in gnome it will only get as far as "windows network" and thats all it will see. Now when I hook the cat5 cable back up and run the "network server" I have no problem seeing my lan. Both the settings are the same in the network config for eth0 my lan card and eth1 my wireless card. Wonder if anyone might have a idea on what might be wrong. FX [moved from Networking by spinynorman]

I have installed without a floopy. The reason they want you to have a floppy is for the boot disks. If you have linux partions already setup its easy as pie to install. FX

Well to update what I have been doing here. I have FC2 running on here (laptop) all by its self so it works just fine. I installled it on my gaming machine with dual boot XP and I can boot into XP just fine and PM 8 works just fine this time on the XP side. No more 117 error when I start it. What I did right no there was correlty this time did the "linux hda=CHS" command at the very first boot prompt. Installed on my wifes machine, the one where the XP install was hosed up and the geometry was hosed up. This time checking the bios for the HDD setting to change it from auto to LBA. Did the correct "linux hda=CHS also. It boots fine into XP and PM 8 also works without error 117. Finishing up an install on my file server also. Changed the settings in the bios from auto to LBA, did the correct linux hda=CHS command at the boot prompt on install and that also is working just fine. Even PM 8 on there too. So that means that all my machines here have FC 2 on them. Except the wifes laptop which really doesn't run very well with Linux because it onl y has 128 meg of ram. Don't care what anyone says, its slow with only that amount. Plus the wife thinks so too. :P It was just a matter of me taking my time and reading a little closer to what had to be done and doing it correctly. Would I still expect a newbie to do that? Sorry, but No and yes. Its easy to follow along, but Im not sure I would expect a newbie to go through that. FX

Well this is interesting. I thought that I had gone back into the stock kernel and tried, but I didn't. Anyways I did try going back into the stock kernel just now and I had to change back the "nvidia" to "vesa" in the drivers area and logged in. Clicked on the terminal icon and it worked. So I went back into the 2.6.7 kernel and changed the drivers around in there (xorg.conf). Booted and tried a terminal and still nothing. So I think I have it narrowed down to a 2.6.7 thing. Which really makes me lost. Could it be something different I have compiled in with the 2.6.7 kernel? Exactly how would I cp the exact .config file over to use in the 2.6.7 compile? Wonder if that will work. I have reinstalled and changed the drivers around in the 2.4.26 kernel and yes the terminal still works. FX