spectere.net
The Chatterbox => Computing => Topic started by: K-Mann on October 01, 2009, 05:07:03 PM
-
For me.
Now that I have your attention, HELP ME OUT.
The laptop is my moms old one, and I'm going to reformat the thing. Once everything is completely blown away, what should I load it up with? An opinion thread, if you will. I was thinking Ubuntu because I've always wanted to try it, I've never used anything linux before, so I though Ubuntu would be a good way to get started. once I have the OS and everything, I'll take the time to learn it and linux and so on. I also thought XP but I'm not sure. Its what she had on there before, and it would be nice to have a windows laptop with me.
So what do you think? I'm kind of leaning towards Ubuntu. If I chose it would someone like to teach me in some sort of messenger?
Also I'm not exactly sure what the specs of it are, all I know is that it has 2 gigs of ram, because she came online one day and was all happy and excited that she upgraded the RAM.
Thanks
-
Ubuntu is definitely more of a plug and play linux than others.. fedora is okay as well. You may not see any particular advantage to it in terms of performance, because you have to install shit so damn anally with packages and admin roots and bullshit like that. If you want to toy around with it and learn something new, I would suggest loading XP on it first on a blank slate format, then use a partitioning software (Acronis Disk Director is my fave.), and install ubuntu/whatever on the 2nd partition. Using linux as your main go-to would be a mistake in my book, unless you're like spec or boobies and know exactly what's goin on and how to fix what you will break.
have fun with your new toy
-
unless you're like spec or boobies and know exactly what's goin on and how to fix what you will break.
You have no idea how much that just made me laugh. If it involves me and linux, A) It WILL fail, B) in the word way possible, C) I will employ google (note: this only works when the computer is still capable of running, or I have another computer available), D) I will spend 4 times the amount of time it should take to install and set up, and still end up with a half-working program/setup.
And occasionally somewhere in there will be a posting here asking what I do and why it's s broken.
-
Fine then just spectere :p you always seem to be in these kinds of threads so I ASSumed you knew something more than the average bear
-
If it involves linux, A) It WILL fail, B) in the worst way possible, C) I will employ google (note: this only works when the computer is still capable of running, or I have another computer available), D) I will spend 4 times the amount of time it should take to install and set up, and still end up with a half-working program/setup.
fixed for you lol
-
lol, well, that's how I feel about it, but I'm aware that for some people, linux just works.
-
I got my laptop today.
There wasn't too much left on there, just some wireless network stuff and a web browser and chat stuff. But they forgot to bring the recovery disc, so I guess I'll just wait for it, and then do what sneaky suggested. I am still considering ubuntu as well, but I would just leave it simple when I load it. I'm not gonna start totally messing with things right away, I just want to see lol. Then when I feel like it I can maybe start with a bunch of simple stuff. Its really just going to be a computer away from home, I'm not going to do any coding or anything like that. Its just I really want to fix this laptop, get rid of all the junk and so on.
-
Ubuntu is definitely going to be your best bet if it's your first time using Linux. Frankly, I don't like it* (Debian (http://www.debian.org/) and Gentoo (http://www.gentoo.org/) are my two preferred systems), but it's perfect when you're looking for something that's easy to get running. The Ubuntu forums are absolutely amazing when it comes to getting support. The people that frequent it are very knowledgeable and helpful -- definitely the exception rather than the norm (looking right at you, "RTFM/lrn2howto/LOLN00B" douchebags).
*Things I don't like: broken network control software (out of the box, I was unable to assign static IPs through the GUI on several PCs), tons of bloat (lots of programs that I simply don't need getting installed), poor RAID support (it's easier to set up RAID 1+0 in Gentoo and that's REALLY saying something), blurry line between "development" and "stable" (Ubuntu tends to put beta software in the stable tree).
Things that I do like about it: one of the most up-to-date package repositories I've seen in a binary distribution, helpful wiki and forums (I can't emphasize this enough), regular release cycle, and, most importantly, the ability to update the entire distribution in-place almost effortlessly (i.e. you can upgrade from Ubuntu 8.04 to 8.10 without reinstalling).
-
Yes, there are definitely some pluses there. Mind you, after SSHing into a Linux distro mainly comprised of busybox, I've learned a lot more about linux than I did before, lol. At the cost of having to googling some things for hours before attempting them :/
-
lawl, busybox. I've done my share of time in that environment, haha.
Fun thing to do: have Gentoo generate you a tar.gz of gcc, glibc, and binutils and build your own self-reliant Linux environment out of it (you could go the full LFS (http://www.linuxfromscratch.org/) route, but it's much faster to set up a build environment using portage). I started by building busybox, the deps for building gcc, glibc, and binutils, and then the development tools themselves, then went from there. I didn't get as far as I would have liked (I didn't even get around to getting <insert init provider here> installed) but it was still a lot of fun. I plan to do it again sometime.
Edit: Oh yeah...speaking of busybox and other minimal shells:
(http://files.spectere.net/pictures/screenshots/g1-shell.jpg)
My phone is awesome.
-
lol, well, I learned the hard way that integrated linux environments can be SLOW when building large binaries.
It took me about 45 minutes (3 or 4 times to get it right) to compile PHP..... Not to mention however long it took to compile MySQL.
In SSH sessions, 45 minutes is quite a while.
-
Wooooooo.
Guys my laptop is awesome. Ubuntu 9.04 on there now. Everything works beautifully except the sound, but there have been many issues for many people with sound and Jaunty, so I'm not the only person. Even though I can't play music yet, I'm still really enjoying it.
Did a tiny bit of playing in the terminal, but only following one of the many guides I tried for my sound. Gonna see what else I can do with this baby.
-
lol, well, I learned the hard way that integrated linux environments can be SLOW when building large binaries.
That's why you set up an ARM (or whatever) toolchain on your powerful x86 rig. ;)
Whenever I'm compiling PPC code I always make sure to set up either distcc or just do all of the work on my x86 box. Every PPC I've seen (including the mighty Cell) sucks ass at software compilation. Fortunately, Gentoo makes it so easy to set up alternate toolchains that a drooling retard could practically do it. Most of the other distros, not so much (though there are plenty of prefabbed ARM, SH, etc, toolchains for Win32).
It took me about 45 minutes (3 or 4 times to get it right) to compile PHP..... Not to mention however long it took to compile MySQL.
That's it?
You need to try compiling Linux 2.6 on a Pentium 120 (or, hell, compiling OpenOffice on anything). It's an eye-opening experience, believe me.
Wooooooo.
Guys my laptop is awesome. Ubuntu 9.04 on there now.
Sweet. Glad you like it. 8)
Everything works beautifully except the sound, but there have been many issues for many people with sound and Jaunty, so I'm not the only person. Even though I can't play music yet, I'm still really enjoying it.
Hop into a terminal and type in "lspci | grep Audio" (note: it's case-sensitive). It should give you something like this:
00:09.0 Audio device: nVidia Corporation MCP73 High Definition Audio (rev a1)
The two information that you need to know are the first two. "00:09" in this case. Now, get some more information on that by typing in "sudo lspci -vv -s 00:09" (substituting "00:09" with whatever it is on your box). Copy and paste the result here. It should look something like this:
00:09.0 Audio device: nVidia Corporation MCP73 High Definition Audio (rev a1)
Subsystem: Micro-Star International Co., Ltd. Device 7518
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (500ns min, 1250ns max)
Interrupt: pin A routed to IRQ 22
Region 0: Memory at fcf78000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Masking: 00000000 Pending: 00000000
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
-
That's why you set up an ARM (or whatever) toolchain on your powerful x86 rig. ;)
Whenever I'm compiling PPC code I always make sure to set up either distcc or just do all of the work on my x86 box. Every PPC I've seen (including the mighty Cell) sucks ass at software compilation. Fortunately, Gentoo makes it so easy to set up alternate toolchains that a drooling retard could practically do it. Most of the other distros, not so much (though there are plenty of prefabbed ARM, SH, etc, toolchains for Win32).
That's it?
You need to try compiling Linux 2.6 on a Pentium 120 (or, hell, compiling OpenOffice on anything). It's an eye-opening experience, believe me.
If I could remember my damn password to log in (any idea on how to find it out, or break in?) I might consider setting a toolchain up, if I'll ever need it.
Just to let you know what's the issue seems to stem from, spec, he's trying to get PulseAudio working, and an update seems to have broken it (since it worked fine before the update).
-
So as it turns out, it must be something else. I did reinstall it, and the sound was done even with a totally clean reinstall. I guess the first time I didn't listen to it long enough, as this second time I listened for about 5 minutes and it went haywire. So its not the updates.
Also spec:
00:14.5 Multimedia audio controller: ATI Technologies Inc IXP SB400 AC'97 Audio Controller (rev 80)
Subsystem: Toshiba America Info Systems Device ff00
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx+
Latency: 64 (500ns min), Cache Line Size: 32 bytes
Interrupt: pin B routed to IRQ 17
Region 0: Memory at c0007400 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Address: 00000000 Data: 0000
Kernel driver in use: ATI IXP AC97 controller
Kernel modules: snd-atiixp
No idea what I just did. I'm guessing I got the specifications of my audio driver?
-
Let's break down the command you entered.
lspci
This is short for List PCI, as in "List all the PCI busses and devices"
the | (pipe) command is a way of chaining commands together.
grep Audio
grep is basically a way to search through files or input (in this case, from that pipe command we used earlier) using regex statements. The regex statement here is the word "Audio". What that does is give us only the line we want in the lspci command. (Basically, we filtered out anything that didn't contain the word Audio)
sudo lspci -vv -s 00:09
Once again, I'll break it down. Bear in mind that I'm getting pretty much all my info here from googling, because I haven't touched linux in
a LONG time, and I've honestly forgotten almost everything I learned.
sudo
Ok, get ready to see this a LOT. I'll give you a bit of a background here because this actually shows a significant difference between windows and *nix systems. The command itself stands for Super User DO (I think). It's a way to bypass permissions and run a program as the Super User, or root, without being logged into the root account. The reason we use it is because it allows us to do stuff we couldn't as a regular user. In windows, it's somewhat common that if your going to be doing something (installing programs, etc.) that requires administrative rights, your going to log in as the administrator. On *nix systems you generally NEVER log in as the root, or super user. You simply use the sudo command on anything that might require root privileges. It's much safer than logging in as root.
lspci -vv -s 00:09
This is all one command. Once again, we're using the lspci command, but this time we're using options, or switches.
We're using the -vv switch, which stands for Very Verbose (basically, "tell us everything you know").
We're also using the -s switch, which stands for Show only devices matching the given input.
The input we give it is 00:09 This stands for Bus 00, Slot 09 (which is where your card is physically attached to the PCI bus on your motherboard.)
The .5 is the Function that the card implements. I'm really not too sure on what that means, but it seems to me that it has to do with cases where you might have a card capable of doing multiple things at once. Say, a USB expansion card with 2 USB connectors might have 2 different functions on one physical card, thus requiring 2 different functions. Of course, I could be dead wrong, but regardless, the function value really isn't of any interest for us.
The overall function of those commands is to locate where the sound card is located (physically, on the PCI bus) and then ask lspci what the hardware connected in that location is.
We do that because we don't know where the sound card is actually connected.
We could have simply used lspci, and visually searched for Audio, but it was just easier to use the first command, because we didn't need to know anything else.