Re: more install problems

From: Andrew McGuinness (andrew_at_arobeia.co.uk)
Date: 08/04/03

  • Next message: Christophe Courtois: "Re: --purge when package already gone ?" 
    Date: Mon, 04 Aug 2003 19:39:56 +0000
To: debian-user@lists.debian.org

    Richard Lyons wrote:
    > Hello again.
    >
    > I have found the configurator that I needed, in theory. It is
    > modconf. But I cannot install i82368, the errors include 'No such
    > device' and
    > 'depmod: *** Unresolved symbols in /lib/modules/.../8139too.o'
    >
    > So the compilation was not successful apparently.
    >
    > Perhaps I should reinitialize the root partition and re-install, using
    > the 2.4.18-686 kernel -- there is a way to select the kernel during
    > the install, isn't there?
    >
    I wouldn't bother doing that. If you're in doubt, install the
    kernel-image-2.4.18-686 and kernel-pcmcia-modules-2.4.18-686 packages
    over again with dpkg -i That's all that the reinstall would do anyway.

    Do you have the "hotplug"

    When you install the kernel-image-2.4.18-686 package, it would have
    asked you if you wanted to install a boot block for it with LILO (you
    do). You would then need to reboot to run the new kernel.

    If you are running the right kernel, "uname -r" should display
    2.4.18-686 (not 2.4.18-bf2.4)

    I don't know where i82368 comes from. There is a module i82365, which
    is possibly your PCMCIA bridge.

    If you think your modules are out of sync, run "depmod -a" to update the
    dependency information. This should not normally be needed, as the
    kernel package postinst should do it. If it produces any errors,
    they're probably important: post them.

    "modinfo 8139too" will tell you where it's getting the module from.

    I'd like to see your "lspci" output. I think your card ought to show up
    there, but I'm not sure. My laptop's pcmcia network card doesn't, but
    it's not a cardbus card, and I think that makes a difference. Your
    cardctl output showed a PCI device ID (unlike mine), and that device ID
    is one that is tested for by the stock 8139too driver. Interestingly,
    the device ID is 8139, which the driver considers an ordinary PCI card,
    not 8138, which is described as being the cardbus version. But the
    driver doesn't do anything different based on the different IDs, so by
    my way of thinking it ought to work.

    Andrew 

    


    -- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Christophe Courtois: "Re: --purge when package already gone ?"

    Relevant Pages

    • Newbie - Installing drivers, compiling drivers, and compiling source.
      ... MSI Wireless card, PC54G2 ... I have installed the Nvidia driver. ... install the motherboard chipset drivers but will get to that (don't know how ... to compile, or recompile the kernel). ...
      (Fedora)
    • NVIDIA driver on Suse 9.1
      ... I've got a NVIDIA FX 5600 and I'm trying to install the driver from the ... the kernel module is build 100%. ...
      (alt.os.linux)
    • Re: Fedora 7 - RPM Build Nvidia 9755 [revisited]
      ... Livna NVIDIA driver RPMs doesn't mean that the same problem exists ... to have to do it everytime I boot a different kernel, ... echo install of nvidia.ko driver failed ...
      (Fedora)
    • Re: Make Error (please help i need my webcam to work)...
      ... Did you look at line 485 in the Makefile? ... There should be a README and INSTALL file in the driver source ... I'm confused as to why you needed to use a 2.4 driver for a 2.6 ... >> Looks like you have to create a soft link into the kernel source. ...
      (comp.os.linux.misc)
    • Re: Constant restarting and not completely booting
      ... Linksys had packed it with a driver CD for Taiwan Language. ... Band WMP55AG card. ... > Cisco WMP55AG WI-Fi card. ... > than the driver date from the install disk for the card. ...
      (microsoft.public.windowsxp.hardware)