Originally posted by: Dark54555
alright...i've got a few issues to work out, hope someof you guys can help.
1. I tried installing Core 2, but after hitting enter on the install screen, the computer reboots. Ideas? I installed core 1.
2. For some reason, the onboard lan on my P4P800 Deluxe won't work without a driver I got from Asus (and this is a redhat problem, from what I read, as most other versions of Linux have no problem running it). I downloaded the files, unzipped them, and followed the directions in the readme. But this is what happens:
[root@localhost 3c2000]# make load
/bin/sh: line 1: gcc: command not found
/bin/sh: line 1: gcc: command not found
gcc -D__KERNEL__ -Wall -Wstrict-prototypes -O2 -DMODULE -I. -DSK_USE_CSUM -I /us r/src/linux-2.4/include -c -o skge.o skge.c
make: gcc: Command not found
make: *** [skge.o] Error 127
Any ideas what that means? I'm a linux n00b, and my unix experience is very, very rusty.
GCC is the Gnu C Compiler. It's used to compile C/C++ and other types of programs.
Either it's not installed or it's not in your path... The path variable is used to indicate to the computer which directories to go to when you are trying to execute a command and the computer needs to find it.
Try
echo $PATH to show your path, and then
locate gcc, and/or
cd / ; find | grep gcc is what I do when looking for a file.
If you choosed the "desktop" or "server" install then it's likely that it didn't install the developement tools stuff. "Workstation" install is the desktop + developement tools and libraries headers and such needed to compile your own programs/modules. For a newbie install usually it is best to choose the "install everything" so that you don't accidently miss out on anything.
Don't worry though, you can install them easily thru one of the system configuration tools, or use
Yum tools to install RPM packages + depedances easily over the internet.
reading more how-tos on linux.com, tried using the modprobe ne and modprobe 3c59x commands (ethernet). here's what I got...
[root@localhost root]# modprobe ne
/lib/modules/2.4.22-1.2115.nptlsmp/unsupported/drivers/net/ne.o: init_module: No such device or address
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.22-1.2115.nptlsmp/unsupported/drivers/net/ne.o: insmod /lib/modules/2.4.22-1.2115.nptlsmp/unsupported/drivers/net/ne.o failed
/lib/modules/2.4.22-1.2115.nptlsmp/unsupported/drivers/net/ne.o: insmod ne failed
[root@localhost root]# modprobe 3c59x
/lib/modules/2.4.22-1.2115.nptlsmp/unsupported/drivers/net/3c59x.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.22-1.2115.nptlsmp/unsupported/drivers/net/3c59x.o: insmod /lib/modules/2.4.22-1.2115.nptlsmp/unsupported/drivers/net/3c59x.o failed
/lib/modules/2.4.22-1.2115.nptlsmp/unsupported/drivers/net/3c59x.o: insmod 3c59x failed
It means that it's trying to install the modules (drivers) but the modules can't find any hardware to use so they are exiting with a error message.
Either something is broke or those modules don't support your hardware, which is more likely.
3. Also with my mobo, to get the drives on the raid controller to show up, you have to patch something. The RAID drivers don't work, but apparently this patch will make them work as simple IDE drives. Here's the patch text:
--- linux/drivers/ide/pci/generic.h Mon Aug 25 13:44:41 2003
+++ linux-2.4.22.2/drivers/ide/pci/generic.h Mon Sep 22 20:36:26 2003
@@ -140,6 +140,19 @@
.enablebits = {{0x00,0x00,0x00}, {0x00,0x00,0x00}},
.bootable = ON_BOARD,
.extra = 0,
+ },{ /* 10 */
+ .vendor = PCI_VENDOR_ID_VIA,
+ .device = PCI_DEVICE_ID_VIA_610,
+ .name = "VIA_610",
+ .init_chipset = init_chipset_generic,
+ .init_iops = NULL,
+ .init_hwif = init_hwif_generic,
+ .init_dma = init_dma_generic,
+ .channels = 2,
+ .autodma = AUTODMA,
+ .enablebits = {{0x00,0x00,0x00}, {0x00,0x00,0x00}},
+ .bootable = ON_BOARD,
+ .extra = 0,
},{
.vendor = 0,
.device = 0,
--- linux/drivers/ide/pci/generic.c Mon Aug 25 13:44:41 2003
+++ linux-2.4.22.2/drivers/ide/pci/generic.c Mon Sep 22 20:42:48 2003
@@ -65,6 +65,8 @@
hwif->ultra_mask = 0x7f;
hwif->mwdma_mask = 0x07;
hwif->swdma_mask = 0x07;
+ if (hwif->pci_dev->device == PCI_DEVICE_ID_VIA_610)
+ hwif->udma_four = 1; /* mj */
if (!noautodma)
hwif->autodma = 1;
@@ -141,6 +143,7 @@
{ PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C561, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 7},
{ PCI_VENDOR_ID_OPTI, PCI_DEVICE_ID_OPTI_82C558, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 8},
{ PCI_VENDOR_ID_TOSHIBA, PCI_DEVICE_ID_TOSHIBA_PICCOLO, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 9},
+ { PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_610, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 10},
{ 0, },
};
--- linux/include/linux/pci_ids.h Mon Aug 25 13:44:44 2003
+++ linux-2.4.22.2/include/linux/pci_ids.h Mon Sep 22 20:36:13 2003
@@ -1085,6 +1085,7 @@
#define PCI_DEVICE_ID_VIA_8233A 0x3147
#define PCI_DEVICE_ID_VIA_P4M266 0x3148
#define PCI_DEVICE_ID_VIA_8237_SATA 0x3149
+#define PCI_DEVICE_ID_VIA_610 0x3164
#define PCI_DEVICE_ID_VIA_P4X333 0x3168
#define PCI_DEVICE_ID_VIA_8235 0x3177
#define PCI_DEVICE_ID_VIA_8377_0 0x3189
it's a .patch file...but what do I DO with it?
Thanks guys.
That patch, I beleive, is to patch the kernel sources so that when you compile your kernel you can have better support for the hardware.
In order to use it your going to have to find the kernel sources for "linux-2.4.22.2" which looks like one of Redhat's own modified kernels. You can probably use Yum to help you find it, or you can probably locate the correct RPM file out their on the internet, if you don't already have the sources installed.
--- linux/include/linux/pci_ids.h Mon Aug 25 13:44:44 2003
+++ linux-2.4.22.2/include/linux/pci_ids.h Mon Sep 22 20:36:13 2003
Show which files are being compared. The plusses are lines going to be added, the minus are lines going to be deleted, I beleive. Never made a patch myself so I can't be too sure.
To apply a patch you usually cd into the directory containing the source code, usually /usr/src, but not nessicarially. Then you copy the patch to that directory. Then you cd into the directory tree of your kernel, something like /usr/src/linux-2.4.22.2 in this case. Then you go
patch -p0 < cat ../patchname
Or something like that, I don't patch much and I forget the actual syntax. Sometimes takes a couple tries to get it right. Try something like
cat ../patchname | patch -p0 or
cat ../patchname | patch -p1. One of those aught to work. It should do it's work without any questions if it's done right.
Allthough all that patching and kernel compiling may not be a good idea... It's pretty involved and usually takes a couple tries to get right. :/
All in all kernel 2.4.22 is fairly old... I thought that fedora core2 installed a 2.6.5 kernel buy default, and it's a SMP kernel? Do you need SMP or is it for hyperthreading?
I am a bit suprised, is this a upgrade from a older OS, or maybe it's a "test" version? Eitherway try to install a newer kernel and chances are that it already has support for your hardware. Use Yum or Apt or whatever to help you install it if you want, or download the RPMs from a place like
http://mirrors.kernel.org/fedora.us/fedora/fedora/2/i386/RPMS.os/
The kernels aviable their are:
kernel-2.6.5-1.358.i586.rpm
kernel-2.6.5-1.358.i686.rpm
kernel-smp-2.6.5-1.358.i586.rpm
kernel-smp-2.6.5-1.358.i686.rpm
And the kernel 2.6.5 sources are their, too. You may need to download a couple other rpms files, too. Then after it's all installed and it seems ok go ahead and reboot and select the new kernel and see if that helps....
If that screws up then you can always go back to the earlier kernel... be sure to check your bootloader configuration /boot/grub/grub.conf, or menu.lst. I think that Fedora mostly uses grub nowadays. If something bad happens the bootloader has a command line you can get into to manually edit the entries if something doesn't work.
Facebook
Twitter