 |
| |
|
|
Q Cubed
|
 |
t3h y3ll0w p3ril
Apr 1999
time: 23:34
|
|
when you install windows, it overwrites the mbr.
here's what you do. download a livecd, like gentoo, or whatever, or a floppy, like tomsrtbt, and then boot into linux.
this won't be your kernel, but the cd's.
then, at the command prompt, mount your linux drive type:
mount /dev/hdax /mnt/a_directory
chroot /mnt/a_directory /bin/bash
env-update
where x is the partition number (if the partition is second, with your windows being first, you'd be going into /dev/hda2) and a_directory is the name of the folder you're mounting it to. if you use the gentoo livecd, make it "gentoo". if it's something like knoppix or gnoppix (go into the cli first...), mount it to something else, if you want.
this first mounts your drive, then changes the root path from the cd to your linux partition.
then, since you have grub, type in
grub
to open up the grub program. it'll give you a blank screen with a basic prompt. type:
root (hdy,x)
setup (hdy)
quit
this will set up grub again on the mbr. y is the hard drive number minus 1: your first hd would be hd0.
if you had a boot partition, make sure that while in the first case you boot into the regular linux drive, mounted at / , for grub, you point it to the boot partition, mounted at /boot . if you didn't have a boot partition, ignore that last bit. i think red hat wants you to install a boot partition, that's what i recall anyway.
hopefully, your grub.conf file will not have been messed with. if it is, ask me again, but this should take care of you.
|
|
| |
|
| |
|
|
|
Q Cubed
|
|
t3h y3ll0w p3ril
Apr 1999
time: 23:34
|
|
well, i'll just say gentoo 2004 has yet to have a kernel panic on me. ymmv. i don't know what went wrong with the installation, as i assume you read the manual, but...
===
as far as the ati drivers: it may be trouble for you, but:
1. ati uses closed-source drivers to take full advantage of their chip. the onus is on them to provide good working drivers.
2. the open-source movement, when it writes drivers for closed-source hardware, often has to go by a guess-and-check method to write drivers. which is why a) ati's cards need to wait for ati's drivers for full effect; b) why samba/cifs is such a ***** to set up; c) why ntfs write support can only really be used with the 'captive' drivers. this is again, not the fault of the open-source movement. it certainly sounds like you're blaming them for failing to write drivers that work for hardware that they frankly don't know the deep details about.
as far as other hardware, linux drivers are again reliant on people who have that hardware; which is why you might not be able to find drivers for, say, a gigabit lom made by, say, linksys, if no developer has that hardware. i personally have no hardware that fails to work with linux; alsa/kernel 2.6 works with my santa cruz card as well as windows does; that was the last sticking point, as the kernel in 2.4 did, but in single channel low quality.
the drivers i've been using have never had trouble.
and asher, linux drivers are not the only ones that are craptastic. wasn't it microsoft and its whql that revealed that over half of all system crashes were as a result of non-microsoft written, closed-source, windows drivers?
===
finally, what do you need the drivers for anyway? i can guarantee you that most people in linux don't use it for gaming (one thing which i believe is holding linux back, actually); if they're rendering stuff, they're probably using server farms, and so they probably don't care about those.
i mean, i'm sorry that linux doesn't have the drivers availible for you, but it's not the oss movement's fault, but rather ati's for being so asstasstic about their delivery. yes, it is a hassle, but as long as you can see the screen and have graphics working on a basic level, you can do most of the stuff you need to.
no, linux is not ready for every tom, dick, and harry, and definitely not ready for grandma sue. the system install process for most is rather onerous (redhat's anaconda is one of the better ones), and the package management process isn't stellar either (rpm, apt, and tgz, for instance, aren't great. portage has great potential, but it's still a work in progress). but as far as a desktop system for someone who's willing to learn it, it's come a long way and is hardly a 'joke'.
|
|
| |
|
|
|
Comrade Tassadar
|
|
Danger! Danger! Kernel panic! Danger!
|
|
| |
|
|
|
Q Cubed
|
|
t3h y3ll0w p3ril
Apr 1999
time: 23:34
|
|
i'll agree that the desktop you mention is less than stellar, however: that's a limitation of the x windowing system, not linux. the linux kernel itself really doesn't do much outside of provide the environment that xwindows plays in, and it's xwindows which isn't running the way that it should. wait for xouvert or ywindows, but those are a good ways off. ticks me off too, because xfree86 really has just fallen apart and seems to be filled with shitheads.
as far as the hardware concerned: i stand by everything i said. i've had plenty of issues with hardware in the past; the sound card lasted until alsa was integrated into 2.6; before then, it was things like the firewire card, the tv card... it's not oss's fault; they don't have the resources to write drivers for everything--particularly things they don't have or use--especially when the manufacturer refuses to make details public. tough beans, but that's the way it is. it's a problem, yes, but it's often because those companies are being *****es rather than the oss movement.
you're right in other respects though: plug-and-play is nowhere near as good as it could be. again, much of it is because of what i said above.
i see desktop linux as a valid option arriving in the next few years. why? most common hardware has decent support, and if you're looking for a system that can do wordprocessing and other basic, office tasks, linux can do that. hell, that's what most people use their windows and mac computers for. if you need it for games, well, you'll have to wait longer.
|
|
| |
All times are GMT. The time now is 05:34.
Apolyton Time is 00:34. |
top of page
|
| archivepost |
|
Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is ON
vB code is ON
Smilies are ON
[IMG] code is ON
|
|
|
|
|
|
18-03-2004 03:49
Attachment: 
|
