Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 22

Thread: Kernel headers

  1. #11

    Default Re: Kernel headers

    My wireless setup/woes can be found at: Wireless problems w/ Broadcom - openSUSE Forums

  2. #12
    Join Date
    Nov 2009
    Location
    Uruguay
    Posts
    737

    Default Re: Kernel headers

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    OK OK, I supose you have a wired network, add some repo for the broadcom
    driver, "zypper ar
    http://download.opensuse.org/reposit.../openSUSE_11.2
    broadcom" as root and then as root too type "zypper se broadcom" and
    install the correct package for you kernel, for example "zypper in
    broadcom-wl-kmp-default"

    - --
    VampirD
    No in elenath hlar nan hd gn
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v2.0.12 (GNU/Linux)
    Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

    iEYEARECAAYFAksm1b0ACgkQJQ+0ABWtaVkhUgCfdDBEAdCZqXRpdddElO5bux6a
    rx4AoPDdUqsJSznMklr7u6hfxm2VvNn3
    =7MWo
    -----END PGP SIGNATURE-----

  3. #13

    Default Re: Kernel headers

    I was able to install it, but still no luck in getting it to recognize the hardware. Do I need to reboot?

    EDIT: How does one turn on a driver? YaST can see that there's a driver for the wireless under Hardware Information, but it's 'Active' attribute has a value of 'No"

  4. #14
    Join Date
    Nov 2009
    Location
    Uruguay
    Posts
    737

    Default Re: Kernel headers

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    Try rebooting, I don't remember the driver module to load it manually

    - --
    VampirD
    No in elenath hlar nan hd gn
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v2.0.12 (GNU/Linux)
    Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

    iEYEARECAAYFAksm2+4ACgkQJQ+0ABWtaVn8eACeKicQcQP9oBt5iGwLO58Ri1tu
    0IYAn3V0fZj3PUpWpV5u+dRzXj7bP8xM
    =daS3
    -----END PGP SIGNATURE-----

  5. #15

    Default Re: Kernel headers

    Actually, I think I got it. I had to fiddle with the kernel settings in YaST. It recognized my wireless router.

    Here's hoping it works!

  6. #16

    Default Re: Kernel headers

    Okay, here's where I'm at.

    The drivers I downloaded seemed to have worked, at least partially. YaST's Network Device screen still doesn't have a wireless option, but I was able to get the Network Connections screen to recognize the Broadcom by adding its PCI value to the kernel under the kernel modification screen.

    So, it recognized my wireless router, which is definitely a step in the right direction. Unfortunately, it's still not working. Here's what iwconfig says:

    Code:
    kevin@linux-r20v:~> /usr/sbin/iwconfig
    lo        no wireless extensions.
    
    eth0      no wireless extensions.
    
    eth1      IEEE 802.11  Access Point: Not-Associated
              Link Quality:5  Signal level:0  Noise level:160
              Rx invalid nwid:0  invalid crypt:0  invalid misc:0
    I'm a bit concerned with that signal level value. I know a signal is being sent as it recognized the name of my router, and it's working on my Windows partition. Is it a firewall issue? Or do I need to play with my Linksys to get it working?

    I'm going to cross-post this back in my topic in the wireless sub-forum as well.

  7. #17
    Join Date
    Nov 2009
    Location
    Uruguay
    Posts
    737

    Default Re: Kernel headers

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    Do you try NetworkManager to configure the wireless card?


    - --
    VampirD
    No in elenath hlar nan hd gn
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v2.0.12 (GNU/Linux)
    Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

    iEYEARECAAYFAksm5oQACgkQJQ+0ABWtaVkHXgCgtxCuCR0hLrkI6qtXNbsu0Ib7
    faUAn3AgS073g2yn2WRigi9LcXpiohN1
    =tQhA
    -----END PGP SIGNATURE-----

  8. #18

    Default Re: Kernel headers

    Well, after having to tweak the config file, I got NetworkManager to work. Pretty sad that a bug reported back in version 10 (according to the wiki) hasn't been addressed yet.

    Now, I'm stuck because Kwallet is acting buggy and not accepting my password (I'm certain I'm typing it correctly).

    For an OS that's supposed to be rock solid, it certainly is buggy as hell. Missing kernel header (no build), not automatically turning on the wireless card itself, forcing me to add it to the kernel settings, not automatically having NetworkManager run out of the box, and now a centralized password program that keeps bugging out on me (I got a KDE module had an error message before rebooting).

    It shouldn't be this hard, time consuming, and frustrating.

  9. #19
    Join Date
    Jun 2008
    Location
    Finland, European Union
    Posts
    1,879

    Default Re: Kernel headers

    Quote Originally Posted by KevinM1 View Post
    It shouldn't be this hard, time consuming, and frustrating.
    How much did you pay for it again?

    Also, I'm not having any of the issues you're having but then again, I know what I'm doing and you're just whining because you don't understand how things work.

  10. #20
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,723
    Blog Entries
    20

    Default Re: Kernel headers

    Quote Originally Posted by KevinM1 View Post
    Well, after having to tweak the config file, I got NetworkManager to work. Pretty sad that a bug reported back in version 10 (according to the wiki) hasn't been addressed yet.

    Now, I'm stuck because Kwallet is acting buggy and not accepting my password (I'm certain I'm typing it correctly).

    For an OS that's supposed to be rock solid, it certainly is buggy as hell. Missing kernel header (no build), not automatically turning on the wireless card itself, forcing me to add it to the kernel settings, not automatically having NetworkManager run out of the box, and now a centralized password program that keeps bugging out on me (I got a KDE module had an error message before rebooting).

    It shouldn't be this hard, time consuming, and frustrating.
    I'd be surprised if anywhere openSUSE professes to be 'Rock Solid' - because it's more or less a testing ground for Novell Enterprise products. I doubt even Windows would make the 'Rock Solid' claim, because it isn't.

    I might personally make such a claim, because for me, it is, well it feels that way.

    All the kernel and build packages have worked spot on for me.

    Networkmanager has been fraught with issues, but for me it works perfectly (Good for me)
    Kwallet has not, at least that I am aware of, had any real problems. Again, for me it's faultless. I suggest deleting all your kwallet config files and start again.
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

Page 2 of 3 FirstFirst 123 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
  •