sort of success
So (sorry), I got my dual boot system up and running. After a HUGE fiasco (feel free to check my lj or blog for details) it's running. the windows side is more or less complete.
The Linux side is getting there. Debian crapped out and gave me errors all over the place even before the real install while it was cataloging CD's. It might be bad media or it might not like my CD drive, but ether way it was too big a pain in the butt (Sorry,
zenten. I was really excited about it, too). Instead, I've got CentOS 3.4. I had it on hand. I'm about to do a full update, but I've got small issues that I'd like to work out.
Issue one. There was no option to name the machine when I installed it. I'd like it to have a fun name so that it counterpoints the Windows install, but I don't know where to change that. This is the sort of thing I should know, but the last time I tried to change it I got errors of all sorts.
Speaking of errors, when I log in I get the pleasant one about how the system can't find localhost and gnome might not function properly. Bummer. Anyone know what that s and hw to get rid of it?
Here's the big one, though. My system thinks that eth0 is supposed to be confiugured with a 3c501 hardware setup. CentOS didn't like my on board lan conection. I did some googling and I found a soloution (new driver for linux: IP1000A) and I got the file and extracted it into ~/bin/drivers. When I log in eth0 doesn't come up and I have to run the following command:
~/bin/drivers/insmod ./ipg.o
That fixes the problem and my internet connection works just fine after that, but I wonder if I can actually fix the problem. Do I need to move files around? Instinctively I want to copy the driver data to my drivers directory, but I'm not sure that's the thing to do.
That should be all. I'm actually also getting an infamous error (Couldn't display "smb:///", because Nautilus cannot contact the SMB master browser.) but I'm hoping that it won't be an issue. Comand line ssh works and gftp (after some convincing) works, so it should be no big deal, since I don't really use other programs.
The Linux side is getting there. Debian crapped out and gave me errors all over the place even before the real install while it was cataloging CD's. It might be bad media or it might not like my CD drive, but ether way it was too big a pain in the butt (Sorry,
zenten. I was really excited about it, too). Instead, I've got CentOS 3.4. I had it on hand. I'm about to do a full update, but I've got small issues that I'd like to work out. Issue one. There was no option to name the machine when I installed it. I'd like it to have a fun name so that it counterpoints the Windows install, but I don't know where to change that. This is the sort of thing I should know, but the last time I tried to change it I got errors of all sorts.
Speaking of errors, when I log in I get the pleasant one about how the system can't find localhost and gnome might not function properly. Bummer. Anyone know what that s and hw to get rid of it?
Here's the big one, though. My system thinks that eth0 is supposed to be confiugured with a 3c501 hardware setup. CentOS didn't like my on board lan conection. I did some googling and I found a soloution (new driver for linux: IP1000A) and I got the file and extracted it into ~/bin/drivers. When I log in eth0 doesn't come up and I have to run the following command:
~/bin/drivers/insmod ./ipg.o
That fixes the problem and my internet connection works just fine after that, but I wonder if I can actually fix the problem. Do I need to move files around? Instinctively I want to copy the driver data to my drivers directory, but I'm not sure that's the thing to do.
That should be all. I'm actually also getting an infamous error (Couldn't display "smb:///", because Nautilus cannot contact the SMB master browser.) but I'm hoping that it won't be an issue. Comand line ssh works and gftp (after some convincing) works, so it should be no big deal, since I don't really use other programs.
