Results 1 to 4 of 4

Thread: Another install problem

  1. #1
    sgh1947
    Guest

    Another install problem

    I just installed RedHat 7.2 from downloaded .iso images. Overall, the system is working, however my NIC was not detected (an ISA NE2000 compatible).

    I thought I'd try to redo the kernel to ensure I had all the proper device support, but the CD-ROM drive (which was used to install the system) keeps giving me 'Not a valid block device' when I try to mount a disk. So I can't load the source. Also, when I try to mount a floppy, it tells me the kernel is not configured to recognize the msdos filesystem type. ???


    Any suggestions would be greatly appreciated.

  2. #2
    JimH
    Guest

    Re: Another install problem

    I just installed RedHat 7.2 from downloaded .iso images. Overall, the system is working, however my NIC was not detected (an ISA NE2000 compatible).
    ISA NIC cards are not auotmatically detected, you have manually configure them. Easiest way for to configure it is to login as the root user and run the Network Configuration Utility. It is listed in the menu under System.

    On the hardware tab, click add. Select the adapter type: ethernet. Then select "NE1000, NE2000, and compatible", select the Device "eth0". For an ISA card you will have to also fill in the IRQ and IO settings. The rest of the setting are not needed. If you don't know what to use for those setting, if you are dual booting, you can copy this information from the Windows device manager.

    Just for reference you can boot the installer with: linux text isa
    This will prompt you do manually configure you isa cards during the install. Unfortunately you have to use the text mode install.

    I thought I'd try to redo the kernel to ensure I had all the proper device support, but the CD-ROM drive (which was used to install the system) keeps giving me 'Not a valid block device' when I try to mount a disk. So I can't load the source. Also, when I try to mount a floppy, it tells me the kernel is not configured to recognize the msdos filesystem type. ???
    This is a bug in RH 7.2, to work around it, as the root user, at a command prompt type: /sbin/depmod -ae

    You need too update your system with all the lastest errata for RH 7.2 to fix this problem. Well, you actually don't need all the errata to fix "this" problem but you should install all the updates.

    The kernel does have built-in support for the msdos filesystem, this may be related to the cdrom problem. I have not seen any reports of it. Update your system first and see if it cures the problem. If not we can look into it.

    First time using Linux or just Red Hat?

    Jim H

  3. #3
    sgh1947
    Guest

    Re: Another install problem

    Thanks for the prompt response, Jim. Yes, this is my first Linux installation. A few years back I had quite a bit of Unix Sys V experience, all command line stuff. This is my first look at Xwindows.

    I've gotten a little farther. The Network Config utility wouldn't even run. Running it from a terminal window showed me there was no /boot/module-info file. I linked /boot/module-info-2.4.7-10 to /boot/module-info and now neat will run.

    I'm having trouble entering my NIC. I've tried several different ways of entering the IO addr (300, 300h, 0x300, even 768 ) but it keeps telling me that the card can't be initialized. What format is the program looking for in this address?

  4. #4
    JimH
    Guest

    Re: Another install problem

    It should be looking for the format as: 0x300

    The file it modifies is /etc/modules.conf. It will add an entry like;

    alias eth0 ne
    options ne irq=11 io=0x300

    What make/model of card is this? Maybe it requires something other then the NE2000 compatible module.
    The card might be looking for different setting then you are supplying.

    You can manually edit modules.conf in a text editor. To load the module at the command prompt: modprobe eth0
    Might give a better error message.

    You can see what modules are loaded using:
    /sbin/lsmod

    You can see what interrupts are assigned with:
    cat /proc/interrupts

    You can see what IO addresses are in use with:
    cat /proc/ioports

    Jim H

Similar Threads

  1. Realplayer install problem
    By Lixus Looser in forum Linux - Software, Applications & Programming
    Replies: 15
    Last Post: 01-26-2004, 04:46 AM
  2. Maya install problem
    By mojo jojo in forum Linux - Software, Applications & Programming
    Replies: 2
    Last Post: 12-30-2003, 06:40 AM
  3. Debian 3.0 install problem
    By papanohair in forum Linux - General Topics
    Replies: 5
    Last Post: 09-09-2002, 01:29 AM
  4. Install Problem
    By Ace8080 in forum Linux - Software, Applications & Programming
    Replies: 10
    Last Post: 04-29-2002, 11:11 AM
  5. RH 7.1 and Mandrake 8.1 install problem
    By conroe in forum Redhat / Fedora
    Replies: 6
    Last Post: 12-18-2001, 07:04 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •