![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>> I discovered that many if not most live CDs can be coaxed into seeing
>> the drives by manually executing a modprobe command. (No, I have no
>> idea which one... and it wouldn't help you anyway.)
>>
>
> That's what I ran across - I just didn't have the energy to dig into
> which one.
>
> I guess I should learn it sometime as this PC is going to have this
> issue for a while and I plan on doing some fun Linux things with it.
IIRC, most live CDs failed to find either my harddrives or my NIC. To
fix it, you have to say something like
modprobe nv_forcedeth
modprobe nv_sata
and then they both work again. I figured this out by searching several
billion manpages, discovering where kernal modules (such as device
drivers) are stored, and then listing the contents of the folder and
looking for anything that sounded like it might work.
Hard to fix? No. User-friendly? No!
I still have no idea what "force deth" actually means...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Invisible wrote:
>>> I discovered that many if not most live CDs can be coaxed into seeing
>>> the drives by manually executing a modprobe command. (No, I have no
>>> idea which one... and it wouldn't help you anyway.)
>>>
>>
>> That's what I ran across - I just didn't have the energy to dig into
>> which one.
>>
>> I guess I should learn it sometime as this PC is going to have this
>> issue for a while and I plan on doing some fun Linux things with it.
>
> IIRC, most live CDs failed to find either my harddrives or my NIC. To
> fix it, you have to say something like
>
> modprobe nv_forcedeth
> modprobe nv_sata
>
> and then they both work again. I figured this out by searching several
> billion manpages, discovering where kernal modules (such as device
> drivers) are stored, and then listing the contents of the folder and
> looking for anything that sounded like it might work.
>
> Hard to fix? No. User-friendly? No!
>
> I still have no idea what "force deth" actually means...
>
I find that I can get into Linux fairly easily and remember quite a bit,
but when i step back from the guts for a while I have to figure things
out again. Granted it all seems familiar and doesn't take as long, but
it's hard to remember exactly what everything does when you mess with it
once in a while.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Thu, 04 Sep 2008 17:34:37 +0200, Invisible <voi### [at] dev null> wrote:
>
> I still have no idea what "force deth" actually means...
It makes more sense as "forced eth", even though the idea of a module that
forces death is somewhat amusing...
Apparently, the ambiguity is at least partially intentional.
--
FE
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Tom Austin wrote:
> I find that I can get into Linux fairly easily and remember quite a bit,
> but when i step back from the guts for a while I have to figure things
> out again. Granted it all seems familiar and doesn't take as long, but
> it's hard to remember exactly what everything does when you mess with it
> once in a while.
I know what you mean...
At one time I installed Gentoo Linux. (As in, that Linux that doesn't
come with an installer and has to be manually compiled from source and
installed piece by piece.) Now I have _no clue_ how I did it.
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Tom Austin wrote:
> And all I wanted - fdisk
What does fdisk give you that diskpart doesn't?
--
Darren New / San Diego, CA, USA (PST)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Thu, 04 Sep 2008 16:12:22 +0100, Invisible wrote:
> My motherboard uses the nVidia nForce 4 chipset, and as a result many
> Linux live CDs can't see any of the SATA drives. However, they all find
> the PATA ones just fine.
Weird, my HP system here has that same chipset on it, and the live discs
do OK with it - SATA drive works beautifully with openSUSE 11.0 running
on it, too.
Jim
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Orchid XP v8 wrote:
> I know what you mean...
>
> At one time I installed Gentoo Linux. (As in, that Linux that doesn't
> come with an installer and has to be manually compiled from source and
> installed piece by piece.) Now I have _no clue_ how I did it.
>
I usually do a Linux From Scratch for most things.
While I do the automated build, it at least keeps me in touch with the
roots of what is going on.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Darren New wrote:
> Tom Austin wrote:
>> And all I wanted - fdisk
>
> What does fdisk give you that diskpart doesn't?
>
I know how to use it and get to it easier than thru the XP recovery console.
I actually tried to get to it, but was prompted for an XP installation
to recover before I got to a prompt that I could use.
I figured that at that point I would rather learn how to get Linux
running on my machine because I plan on messing around with it later.
Tom
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Tom Austin wrote:
> I know how to use it and get to it easier than thru the XP recovery
> console.
Diskpart runs for me from the XP command line. Oh, I see what you mean.
You had nothing at all on the machine. OK.
> I actually tried to get to it, but was prompted for an XP installation
> to recover before I got to a prompt that I could use.
Yeah, I can see where that would slow you down. :-) BartPE is a good
cure if you do that sort of thing regularly.
> I figured that at that point I would rather learn how to get Linux
> running on my machine because I plan on messing around with it later.
Yeah. And live CDs are certainly easier to find for Linux than Windows.
I just thought there might have been functionality missing or something
that I didn't know about in fdisk.
--
Darren New / San Diego, CA, USA (PST)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Darren New <dne### [at] san rr com> wrote:
> Yeah. And live CDs are certainly easier to find for Linux than Windows.
Does Windows support creating so-called live CDs at all (maybe through
extensive hacking)? I know you can create recovery boot disks from Windows,
but if I'm not completely mistaken, those just basically create a DOS disk
with some text-based utilities. You *could* call that a "live CD", but
not really, IMO.
Of course even if Windows had full support, there's always the pesky
limiation that it's commercial software which is illegal to distribute
without permission. There really are certain situations where free
software does have its advantages.
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |