Find the answer to your Linux question:
Page 4 of 5 FirstFirst 1 2 3 4 5 LastLast
Results 31 to 40 of 42
Originally Posted by waterhead As you can see, it installed the driver for a different kernel version! I don't know why it would do that, so you will need to ...
  1. #31
    Linux Engineer nujinini's Avatar
    Join Date
    Apr 2009
    Location
    An Island in the Pacific!
    Posts
    1,197


    Quote Originally Posted by waterhead View Post
    As you can see, it installed the driver for a different kernel version! I don't know why it would do that, so you will need to specify the version that you want it to install.
    Code:
    yum install kmod-wl-2.6.27.5-117.fc10.i686
    Code:
    [root@localhost ~]# yum install kmod-wl-2.6.27.29-170.2.78.fc10.i686
    Loaded plugins: refresh-packagekit
    fedora                                               | 2.8 kB     00:00     
    rpmfusion-free                                       | 2.7 kB     00:00     
    rpmfusion-free-updates                               | 2.8 kB     00:00     
    rpmfusion-nonfree                                    | 2.7 kB     00:00     
    rpmfusion-nonfree-updates                            | 2.8 kB     00:00     
    updates                                              | 3.4 kB     00:00     
    updates/primary_db                                   | 4.2 MB     02:23     
    Setting up Install Process
    Package kmod-wl-2.6.27.29-170.2.78.fc10.i686-5.10.91.9-2.fc10.4.i686 already installed and latest version
    Nothing to do
    [root@localhost ~]#
    I will try and reboot. Be right back.

  2. #32
    Linux Guru waterhead's Avatar
    Join Date
    Jul 2004
    Location
    Franklin, Wisconsin
    Posts
    4,570
    I posted the wrong command. I since corrected it, but you're too fast! Go back and reread the command, it now has your current kernel version in it.

    Another way of doing it is to include the uname -r command, surrounded by backticks.
    Code:
    yum install kmod-wl-`uname -r`
    Paul

    Please do not send Private Messages to me with requests for help. I will not reply.

  3. #33
    Linux Engineer nujinini's Avatar
    Join Date
    Apr 2009
    Location
    An Island in the Pacific!
    Posts
    1,197
    Quote Originally Posted by waterhead View Post
    As you can see, it installed the driver for a different kernel version! I don't know why it would do that, so you will need to specify the version that you want it to install.
    Code:
    yum install kmod-wl-2.6.27.5-117.fc10.i686
    woopsi...I was too quick to the draw. I will redo it again Paul, sorry...


    Code:
    [root@localhost ~]# yum install kmod-wl-2.6.27.5-117.fc10.i686
    Loaded plugins: refresh-packagekit
    Setting up Install Process
    Resolving Dependencies
    --> Running transaction check
    ---> Package kmod-wl-2.6.27.5-117.fc10.i686.i686 0:5.10.27.6-5.fc10.5 set to be updated
    --> Finished Dependency Resolution
    
    Dependencies Resolved
    
    ================================================================================
     Package                        Arch Version            Repository         Size
    ================================================================================
    Installing:
     kmod-wl-2.6.27.5-117.fc10.i686 i686 5.10.27.6-5.fc10.5 rpmfusion-nonfree 463 k
    
    Transaction Summary
    ================================================================================
    Install      1 Package(s)         
    Update       0 Package(s)         
    Remove       0 Package(s)         
    
    Total download size: 463 k
    Is this ok [y/N]:
    Code:
    Transaction Summary
    ================================================================================
    Install      1 Package(s)         
    Update       0 Package(s)         
    Remove       0 Package(s)         
    
    Total download size: 463 k
    Is this ok [y/N]: y
    Downloading Packages:
    kmod-wl-2.6.27.5-117.fc10.i686-5.10.27.6-5.fc10.5.i686.r | 463 kB     00:11     
    Running rpm_check_debug
    Running Transaction Test
    Finished Transaction Test
    Transaction Test Succeeded
    Running Transaction
      Installing     : kmod-wl-2.6.27.5-117.fc10.i686-5.10.27.6-5.fc10.5.i686   1/1 
    
    Installed:
      kmod-wl-2.6.27.5-117.fc10.i686.i686 0:5.10.27.6-5.fc10.5                      
    
    Complete!
    [root@localhost ~]#

  4. #34
    Linux Engineer nujinini's Avatar
    Join Date
    Apr 2009
    Location
    An Island in the Pacific!
    Posts
    1,197
    Guess what?

    I AM CABLE FREEE!!!!! Its working! Its alive....!!!

    Whew! I really developed a splittin headache with that one.

    Thank you very much to waterhead and miketbob for your patience, guidance and wisdom.

    Bless your heart!

    If its not to much to ask from Paul, do you think its ok if you can summarize for me what happened so I can understand it better please? )

  5. #35
    Linux Guru waterhead's Avatar
    Join Date
    Jul 2004
    Location
    Franklin, Wisconsin
    Posts
    4,570
    Umm... From the beginning, or just the problem with the module version?

    When you installed the broadcom-wl package, it also installed thedependecy packages. One of these is the kernel module. The kernel module is specific to the kernel version. One made for a different kernel version won't work.

    YUM usually is pretty good with this, but this time it installed a module for a newer kernel. So, you needed to specify the version that you wanted it to install.

    I suspect that the reason it installed a newer version, is because you have that kernel installed, but you are not booting into it. You can check which versions you have, by checking the /boot/grub/grub.conf file.
    Code:
    su -c 'cat /boot/grub/grub.conf'
    Paul

    Please do not send Private Messages to me with requests for help. I will not reply.

  6. #36
    Linux Engineer nujinini's Avatar
    Join Date
    Apr 2009
    Location
    An Island in the Pacific!
    Posts
    1,197
    Quote Originally Posted by waterhead View Post
    Umm... From the beginning, or just the problem with the module version?

    When you installed the broadcom-wl package, it also installed thedependecy packages. One of these is the kernel module. The kernel module is specific to the kernel version. One made for a different kernel version won't work.

    YUM usually is pretty good with this, but this time it installed a module for a newer kernel. So, you needed to specify the version that you wanted it to install.

    I suspect that the reason it installed a newer version, is because you have that kernel installed, but you are not booting into it. You can check which versions you have, by checking the /boot/grub/grub.conf file.
    Code:
    su -c 'cat /boot/grub/grub.conf'

    Your right Paul, now I understand. Do you think its safe to just delete the other one using
    nano /boot/grub/menu.lst?

    Code:
    # NOTICE:  You do not have a /boot partition.  This means that
    #          all kernel and initrd paths are relative to /, eg.
    #          root (hd0,7)
    #          kernel /boot/vmlinuz-version ro root=/dev/sda8
    #          initrd /boot/initrd-version.img
    #boot=/dev/sda
    default=0
    timeout=5
    splashimage=(hd0,7)/boot/grub/splash.xpm.gz
    hiddenmenu
    title Fedora (2.6.27.29-170.2.78.fc10.i686)
    	root (hd0,7)
    	kernel /boot/vmlinuz-2.6.27.29-170.2.78.fc10.i686 ro root=UUID=07dd005b-e6e4-4a01-8500-7addc59e0ace rhgb quiet
    	initrd /boot/initrd-2.6.27.29-170.2.78.fc10.i686.img
    title Fedora (2.6.27.5-117.fc10.i686)
    	root (hd0,7)
    	kernel /boot/vmlinuz-2.6.27.5-117.fc10.i686 ro root=UUID=07dd005b-e6e4-4a01-8500-7addc59e0ace rhgb quiet
    	initrd /boot/initrd-2.6.27.5-117.fc10.i686.img
    title Other
    	rootnoverify (hd0,0)
    	chainloader +1
    [root@localhost ~]#

  7. #37
    Linux Guru waterhead's Avatar
    Join Date
    Jul 2004
    Location
    Franklin, Wisconsin
    Posts
    4,570
    You should want to use the latest kernel, unless you experienced problems with it. It is actually set to be the default boot kernel, so I don't know why you are booting into the older kernel. Are you manually selecting the kernel version at boot?

    Edit: Don't manually edit the file that way. The kernel will still be installed even if you do.
    Paul

    Please do not send Private Messages to me with requests for help. I will not reply.

  8. #38
    Linux Engineer nujinini's Avatar
    Join Date
    Apr 2009
    Location
    An Island in the Pacific!
    Posts
    1,197
    Quote Originally Posted by waterhead View Post
    You should want to use the latest kernel, unless you experienced problems with it. It is actually set to be the default boot kernel, so I don't know why you are booting into the older kernel. Are you manually selecting the kernel version at boot?

    Edit: Don't manually edit the file that way. The kernel will still be installed even if you do.
    Yes, I would really prefer to use the latest kernel.
    No, I do not manually select kernel version at boot.
    If not by nano, what would be the best way to remove the old kernel AND...
    If I remove the old kernel, would it not affect my wl since the version I downloaded was based on the old kernel that I intend to remove?

  9. #39
    Linux Guru waterhead's Avatar
    Join Date
    Jul 2004
    Location
    Franklin, Wisconsin
    Posts
    4,570
    I don't understand why it is booting into the older kernel. The line that specifies the kernel to boot is this.
    Code:
    default=0
    Zero means the first one in the list. The first one in the list is this:
    Code:
    title Fedora (2.6.27.29-170.2.78.fc10.i686)
    That is the one that should be booting. When you boot, it is set to show the menu for 5 seconds. You can select the kernel by hitting the up/down arrow during the 5 seconds. The list of available kernels should show, and you can select the one to boot.

    You already installed the driver for that kernel the first time you tried. So the wireless should work OK in that kernel too.
    Paul

    Please do not send Private Messages to me with requests for help. I will not reply.

  10. #40
    Linux Engineer nujinini's Avatar
    Join Date
    Apr 2009
    Location
    An Island in the Pacific!
    Posts
    1,197
    Quote Originally Posted by waterhead View Post
    I don't understand why it is booting into the older kernel. The line that specifies the kernel to boot is this.
    Code:
    default=0
    Zero means the first one in the list. The first one in the list is this:
    Code:
    title Fedora (2.6.27.29-170.2.78.fc10.i686)
    That is the one that should be booting. When you boot, it is set to show the menu for 5 seconds. You can select the kernel by hitting the up/down arrow during the 5 seconds. The list of available kernels should show, and you can select the one to boot.

    You already installed the driver for that kernel the first time you tried. So the wireless should work OK in that kernel too.
    Ok Paul, thank you very much for all the help. Sincerely!

    I will try to go over everything to make sure I understand and then perhaps by tomorrow I will try to remove the older kernel. Good night!

Page 4 of 5 FirstFirst 1 2 3 4 5 LastLast

Posting Permissions

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