You can tack on "> filename" on the end of a command to output it to a plain text file instead, e.g.
lsmod -a > /tmp/blahdeblah
then you can do as you wish with the file
You can tack on "> filename" on the end of a command to output it to a plain text file instead, e.g.
lsmod -a > /tmp/blahdeblah
then you can do as you wish with the file
Specifically what kind of ethernet card do you have? I don't see any modules in that list you posted that look like ethernet cards. The <b>lspci</b> command will list all your PCI cards, if you need to see a list. Post the contents of lspci here, even better. If you'd like to look at the stuff that gets output at boot time, you can use <b>dmesg</b>.
Anyways, I think that eth1394 thing might be what's causing the problem. 1394 refers to firewire, yes? It might be detecting your firewire port as a network card. Do this:
rmmod mii
rmmod eth1394
to unload those modules. Then do <b>ifconfig -a</b> and see what it says; if that was what the kernel was assigning to eth0, then eth0 should go away. If eth0 goes away when you do that, then that's a good thing; then you just figure out what your ethernet card's module is and modprobe it.
If worse comes to worse, I can SSH to your machine and do it all for you.
(You can highlight and paste text from the console with the mouse, if you run gpm. In linux, highlighting text automatically "copies" it, and middle-clicking "pastes" it. Just remember that. Probably doesn't help you right now, but it will once your internet works.)
NVIDIA nFORCE Networking Controller
It's part of the ASUS NVIDIA Motherboard.
Check the attachment in my first post too. Those four devices appear in my device manager.
I have two ethernet ports in the back of my machine. The top one works, the bottom one doesn't. I think the bottom one is if I want to add that gigabit ethernet card later on, which my motherboard supports.
Did you try what I said about rmmod'ing those Firewire modules and seeing if eth0 frees up?
Onboard ethernet cards are evil. "NVIDIA nFORCE Networking Controller" sounds vague. <b>lspci</b> will give you more information, as I said. <b>ls /lib/modules/`uname -r`/kernel/drivers/net</b> will list all the ethernet modules on the CD. (Those are backticks around `uname -r`, i.e. the character below the ~ on the keyboard.) Find a module in there that looks like it goes with your card, and do
modprobe nforce-net
or whatever the name of the module is you want to use. Keep trying until one succeeds, and ifconfig -a shows your ethernet device. nforce-net might be the one you want, but there's no way for me to know.
Yay! eth0 frees up!
I'll try loading modules now.
lspci gives me this:
<b>00:04.0 Ethernet controller: Nvidia Corporation nForce ethernet Controller (rev a1)</b>
I loaded the modules, but I have no idea which one to load. There are dozens.
Is there one called "forcedeth"? Or "nforce-net"? Or "nvnet"? Try those. ifconfig -a after you try each one, to see if you get an eth0.
Ok, I get eth0 now with encap:Ethernet, but I still can't ping yahoo.com or connect to gentoo.org.
Now that it's recognized, you have to enable it. Try <b>/etc/init.d/net.eth0 restart</b>.
If that doesn't work you can try <b>dhcpcd eth0</b>.
Success! I'm using Links now!
I've already made the partitions with the correct filesystems using Partition Magic. Should I still look over them with fdisk or continue with stage3 extraction?
EDIT: fdisk is giving me the error "unable to open /dev/hda" when I run "fdisk /dev/hda".
Post the output of
<b>mount</b>
If you run links as <b>links -driver fb</b>, it'll even load graphics and stuff. Very nice.
(Be sure to remember what module you used for your network card, so you can put it in your kernel later when you compile your own.)
tmpfs on / type tmpfs (rw)
none on /dev type devfs (rw)
devfs on /dev type devfs (rw)
/newroot/dev/cdroms/cdrom0 on /mnt/cdrom type iso9660 (ro)
none on /proc type proc (rw)
none on /proc/bus/usb type usbfs (rw)
According to your blog, you have SATA HDs, right? Does /dev/sda exist? Or /dev/hd[anything]? Maybe /dev/hde or /dev/hdg. Or do <b>dmesg | more</b> and look for what it called your hard drives.
Here's the output of "fdisk /dev/hde":
The number of cylinders for this disk is set to 14593.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
That shouldn't be a problem, right?
Mine says that too. Not a problem.
Posting Permissions
Reply With Quote