PlaneShift
Fan Area => The Hydlaa Plaza => Topic started by: RussianVodka on June 10, 2005, 05:27:27 pm
-
Ok, I don\'t have much time for this, seeing as I\'m gona do it as soon as I get home.
Here is my problem:
1. Windows is being a bitch.
2. Having alot of trouble with linux because I am connected through a router.
Here is my plan:
1. Coppy valuable files to CD\'s.
2. Bring computer (just case) downstairs (where the internet connection is).
3. Switch cases with the computer downstairs.
4. Partition ENTIRE system.
5. Instal Linux via boot CD and internet.
6. Instal all the drivers I will need for linux from the internet.
7. Maby instal windows.
8. Bring case back upstairs and hook up to original setup.
My concern:
1. Will things like the speaker, keyboard and monitor effect the Linux instalation? Or does it check for those at every startup? I\'m using Debian.
2. Any other problems you think this may cause?
-
er, I don\'t know about Debian specifically, but usually hardware is handled in your kernel config. I dont think moniter and speakers will give you any problems at all, but video and sound hardware might. If they dont work automatically after you insall (again, I dont know how debian works) you will probably have to recompile your kernel. If you have never done this before, don\'t panic: It is not as difficult as it sounds, and there is plenty of help available on the web.
What trouble is your router giving you? Linux=good with networking.
-
The bigest problem is that there is no official Linux driver for it. So I\'m usingan unofficial driver.
-
lol it\'s a problem ?
There is no \"official drivers\" installed by default because everything is installed with the open source drivers but there is no problem. They works !
NB : if you are using a pppoe modem (ethernet non DHCP modem), enter that command line to reach internet :
# pppoeconf
Debian will ask you some strange questions for a Windows user. Read each question screen and if you dunno just type enter (in general, debian know what should work but it ask you what do you really want...).
For the screen and the graphic card drivers : choose automatic detection : it works ! and if it doesnt work you can look for the spec of your screen, choose the serverX compatible with the hardware acceleration and the graphic card driver compatible with your video card (generally nvidia or radeon or ati)
oh and dont make the same mistake than me: the first time I installed debian, I said to the installer my keyboard code was \"ger\" (instead of \"de\" because it was a german one and because the keyboard\'s codes are written with 2 LETTERS... and what\'s worse is that I knew that).
Oh and dont forget to install \"kde\" ;-) and \"kdm\"
EDIT: omg I hadnt seen! Install Windows before! or windows will steal linux boot...
-
Originally posted by fken
EDIT: omg I hadnt seen! Install Windows before! or windows will steal linux boot...
tp prevent this you can create a boot floppy before installing windows. and if the grub loader disappears after the windows installation, but from floppy and run grub-install /dev/hda as root.
or if you are familiar with mount you can boot from a \"live cd\" mount your hd and run grub-install lilo, whatever you want.
-
IMHO starting with Debian is not a good idea.
Also if you would like to have multiboot with Windows you have to install Windows first.
Regards.
-
Originally posted by lethe
Originally posted by fken
EDIT: omg I hadnt seen! Install Windows before! or windows will steal linux boot...
tp prevent this you can create a boot floppy before installing windows. and if the grub loader disappears after the windows installation, but from floppy and run grub-install /dev/hda as root.
or if you are familiar with mount you can boot from a \"live cd\" mount your hd and run grub-install lilo, whatever you want.
Actually, you can even install lilo or grub from inside windows, which in some cases works better for installing then floppies, as you can set the whole thing up, and then target whatever you\'d like. Haven\'t finished trying it, but looks good so far :)
-
my windows is on the slave harddisk .. to manage this you have to map the disks within grub e.g.
title Windows XP
map (hd1) (hd0)
map (hd0) (hd1)
rootnoverify (hd1,0)
makeactive
chainloader +1
boot
-
Oh, what I meant by \"official drivers\" are drivers that are made by the company.
Like Nvidia, and ATI have \"official\" dirvers. As opposed to my router that does not have \"official\" linux drivers support.
Another problem that I\'m encountering is that Debian doesn\'t see my sound card.... Grrrr...
-
almost nothing is created by the company. But off course when you look at companies website they have no problem to say \"our product is compatible linux!\" and simply give the link.
If you read quickly, you think the drivers belong to the company but no! They did nothing to help and then they say we have a driver for linux...
Trust in the linux \"unofficial\" drivers!
(and in fact dont worry, Windows has its own drivers I think - called Microsoft publisher or something like that...)
And what\'s your sound card ?
-
Seriously, recompile your kernel. There is support for most hardare (except for really new stuff) in the kernel config. You mostly don\'t have to bother with additional software--except, of course, for video cards.
-
seriously I dont think a newbie in linux applications could easily recompile his kernel...
So try Mandriva if its your first linux. Thanks to Mandriva you will know how linux works and if the your sound card works, it would mean off course that it would work with debian and others linux distributions.
It\'s not dumb things to begin with a MS software (MS = MandrivaSoft off course)
-
I was planing on downloading FC4, seeing as I already has experience with FC3. But people say that the FC project is weak and isn\'t good for learning.
-
then, as long as you are able to use internet, try to find the name of the driver required by your sound card.
#apt-cache search NAME_OF_YOUR_SOUND_CARD
if it\'s a SB 5.1 or a AC\'97 ... it would be strange if it doesnt work... because it works on my computers.
-
A router doesn\'t need a driver, assuming of course that it really is a router. As long as you have a driver for the network card, and specify the correct IP address (or DHCP if you use that), it should work.
-
Nope, as seen here (http://www.ralinktech.com/supp-1.htm) my router requirese a driver.
-
I don\'t think its a router - in fact I\'m sure it isn\'t. More than likely its a dsl modem, cable modem, or some wacko ethernet card. The fact that its an internal component means that it will require a driver. Routers aren\'t usually internal as their sole purpose is to allow multiple machines a network connection. Thus they are usually standalone pieces.
Edit: Ahh I see now its a wireless card. Wireless can be a small pain. I ended up using ndiswrapper for my wireless pcmcia card.
-
yay ndiswrapper! I\'m using version .08 to get my wi-fi pci card with an unsupported broadcom chipset running in linux. (for some odd reason, any newer version, even the gentoo ebuild, causes a run-time kernel panick.)
About FC, I actualy don\'t think it\'s such a bad way to learn linux. I started with FC1 about a year ago, recompiled my kernel (strictly following a guide and causing many kernel panicks) about a month later, switched to FC2, and then finally, gentoo. I think FC is great for learning, but you won\'t be happy with it for long because there are many things in it that should work but don\'t. Also, last I checked, gnome is the default desktop environment, which is dumb. And you can switch to KDE, but it\'s some stupid version that they altered, or at least messed with the default settings.
-
Originally posted by RussianVodka
Nope, as seen here (http://www.ralinktech.com/supp-1.htm) my router requirese a driver.
It\'s not a router. As Induane already said, it\'s a wireless network card.
A lot of misunderstandings in tech support (on a forum like this, usenet or regular phone support) happens by people trying to sound smart and using tech jargon, which they don\'t know the precise meaning of. If you don\'t know the correct word, it\'s better to describe the thing, than use the word you think is right. Example: It\'s better to say \"The box under the TV thingie\", than \"the hard disc\". The first one is a precise description, and the techie will know what you\'re talking about. The second is just wrong (like \"router\" in your case), and will just cause confusion.
Ok, in your case the only thing that went wrong was a couple of extra posts, while people tried to figure out what you were talking about, so it wasn\'t really that bad. But at work I have driven 80 km / 50 miles (and back) with the wrong spare parts, because the moron at the other end of the phone was trying to sound like he knew what he was talking about.
-
Delete