Kernel 3.0

English Install/Boot/Login
21

They got to 3.0.0-2-desktop #1 SMP PREEMPT Fri Jul 22 19:29:25 UTC 2011 (bbe1cb6) x86_64 already, rpm kernel-desktop-3.0.0-2.1.x86_64 :slight_smile:
Rather than self-compile, most ppl can conveniently use Kernel:HEAD, Kernel:stable which also constains vanilla “Linus” kernels if you don’t want SuSE patches.

Before updating remember to set multiversion kernel though, just in case!

# grep multiversion /etc/zypp/zypp.conf
##      provides:multiversion(kernel)   - all packages providing 'multiversion(kernel)'
# multiversion = provides:multiversion(kernel)
multiversion = provides:multiversion(kernel)
22

I’ve installed the 3.0 kernel and lost broadcom wifi, too, Here’s netinfo

Model: "Broadcom Network controller"
  Vendor: pci 0x14e4 "Broadcom"
  Device: pci 0x4727

When I try manually compile the driver downloaded from Broadcom itself I get

linux-y70s:/home/stan/hybrid_wl # make
KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd`
make[1]: Entering directory `/home/stan/Kernel/linux-3.0'
  CC [M]  /home/stan/hybrid_wl/src/wl/sys/wl_linux.o
/home/stan/hybrid_wl/src/wl/sys/wl_linux.c: In function ‘wl_attach’:
/home/stan/hybrid_wl/src/wl/sys/wl_linux.c:485:3: error: implicit declaration of function ‘init_MUTEX’
make[2]: *** [/home/stan/hybrid_wl/src/wl/sys/wl_linux.o] Error 1
make[1]: *** [_module_/home/stan/hybrid_wl] Error 2
make[1]: Leaving directory `/home/stan/Kernel/linux-3.0'
make: *** [all] Error 2
linux-y70s:/home/stan/hybrid_wl #

I’ve only used “make” three or four times in my life and so have no idea what exactly went wrong, please be kind to a noob.

B43 page, b43 - Linux Wireless also offers brcm80211 - Linux Wireless as an alternative. Is it worth trying?

23

I’ve managed to pass this first hurdle (implicit declaration of function ‘init_MUTEX’) by following instructions in this thread

Patching 802.11 Linux STA driver for Kernel 2.6.37 - LinuxQuestions.org

Now I get

linux-y70s:/home/stan/hybrid_wl # make
KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd`
make[1]: Entering directory `/home/stan/Kernel/linux-3.0'
  LD      /home/stan/hybrid_wl/built-in.o
  CC [M]  /home/stan/hybrid_wl/src/shared/linux_osl.o
  CC [M]  /home/stan/hybrid_wl/src/wl/sys/wl_linux.o
  CC [M]  /home/stan/hybrid_wl/src/wl/sys/wl_iw.o
  LD [M]  /home/stan/hybrid_wl/wl.o
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: modpost: missing MODULE_LICENSE() in /home/stan/hybrid_wl/wl.o
see include/linux/module.h for more information
  CC      /home/stan/hybrid_wl/wl.mod.o
  LD [M]  /home/stan/hybrid_wl/wl.ko
make[1]: Leaving directory `/home/stan/Kernel/linux-3.0'
linux-y70s:/home/stan/hybrid_wl #

So far no luck with the “missing MODULE_LICENSE()”

24

Turns out that error can be ignored, I got the driver anyway, proceeded with installing it as per Readme and now a perfectly working wifi.

25

On 08/01/2011 05:46 AM, Stan Ice wrote:
>
> Turns out that error can be ignored, I got the driver anyway, proceeded
> with installing it as per Readme and now a perfectly working wifi.

As Broadcom does not open-source their code, it cannot have a license that Linux
likes. That is the reason for that warning. If you look carefully at the dmesg
output when wl loads, you will see a message that it “taints your kernel”. That
is also due to the lack of a proper license.

In general, things that called WARNINGS can be ignored. Things that are called
ERRORS cannot. As with all general declarations, of course there are exceptions.

With kernel 3.0, the support of the newer Broadcom cards with b43 is much
better. To see for yourself, do the following:


sudo /usr/sbin/install_bcm43xx_firmware
sudo /sbin/modprobe -rv wl
sudo /sbin/modprobe -v b43

To return back to wl:


sudo /sbin/modprobe -rv b43
sudo /sbin/modprobe -v wl

One of the advantages of using any in-kernel driver such as b43 is that it is
automatically updated when the kernel is changed.

26

I created a bug report about some wifi being broken with the 3.0 kernel.

[https://bugzilla.novell.com/show_bug.cgi?id=709073

C](https://bugzilla.novell.com/show_bug.cgi?id=709073)urrently I’m using an ethernet connection until this problem is resolved.

27

Compiled and installed on my Toshiba and lost wifi also. I thought the rtl8192se driver was to be included with the 3.0 kernel but apparently not.
Tried to install the driver from Realtek and had problems which I have not had time to resolve, will revisit this evening.
Drivers from Realtek have been easy to install previously.

28

On 08/03/2011 12:46 PM, zuser wrote:
>
> Compiled and installed on my Toshiba and lost wifi also. I thought the
> rtl8192se driver was to be included with the 3.0 kernel but apparently
> not.
> Tried to install the driver from Realtek and had problems which I have
> not had time to resolve, will revisit this evening.
> Drivers from Realtek have been easy to install previously.

The driver is in 3.0. Did you install the linux-firmware package? The firmware
file needed is /lib/firmware/rtlwifi/rtl8192sefw.bin.

29

Possible that kernel did not compile properly. Driver is not installed and download from realtek will not in install although it has installed in 38.2 kernel.

30

On 08/04/2011 05:16 AM, zuser wrote:
>
> Possible that kernel did not compile properly. Driver is not installed
> and download from realtek will not in install although it has installed
> in 38.2 kernel.

If you post details, we might be able to help. The kernel API changes with time.
Unless a driver is modified to account for such changes, it will fail to
compile. I do not describe this as a failure to install - it is a failure to build!

31

Recompiled the kernel after new download but still no joy. Firmware is in place but no driver
Apparently not seeing the card at all.
Networkmanager does not show any wireless available.
Configuring with Yast using ‘ifup’ option shows the card and goes through the motions but still
nothing there after it’s complete

What info do you need from me to suggest a fix.

32

On 08/06/2011 08:36 AM, zuser wrote:
>
> Recompiled the kernel after new download but still no joy. Firmware is
> in place but no driver
> Apparently not seeing the card at all.
> Networkmanager does not show any wireless available.
> Configuring with Yast using ‘ifup’ option shows the card and goes
> through the motions but still
> nothing there after it’s complete
>
> What info do you need from me to suggest a fix.

Did you fix the configuration? Please post the output of

grep 8192 .config

33

Appears there is no configuration file. not found

34

In order to use the command: grep 8192 .config, you must be located in the same folder as .config, else there is no error output. When using sakc to compile a kernel, the .config file is located in the main kernel compile folder for that version of the kernel. For instance, with kernel 3.0, this would be located in the folder ~/Kernel/linux-3.0. You must change to the folder where .config is located. When I run this (grep 8192 .config) command in the ~/Kernel/linux-3.0 folder where the Linux kernel 3.0 was compiled using sakc I get :

james@linux-6m6e:~/Kernel/linux-3.0> grep 8192 .config
# CONFIG_RTL8192CE is not set
# CONFIG_RTL8192SE is not set
# CONFIG_RTL8192CU is not set
CONFIG_RTL8192U=m
CONFIG_RTL8192E=m

Thank You,

35

Thanks for the explanation, seems I get the same

CONFIG_RTL8192CE is not set

CONFIG_RTL8192SE is not set

CONFIG_RTL8192CU is not set

CONFIG_RTL8192U=m
CONFIG_RTL8192E=m

36

Thanks for the explanation, seems I get the same

CONFIG_RTL8192CE is not set

CONFIG_RTL8192SE is not set

CONFIG_RTL8192CU is not set

CONFIG_RTL8192U=m
CONFIG_RTL8192E=m

That is good. Larry (lwfinger) is a kernel and wireless expert here. Lets see what he determines that this output means.

Thank You,

37

On 08/06/2011 12:46 PM, jdmcdaniel3 wrote:
>
>> Thanks for the explanation, seems I get the same
>>
>>
>>
>> # CONFIG_RTL8192CE is not set
>> # CONFIG_RTL8192SE is not set
>> # CONFIG_RTL8192CU is not set
>> CONFIG_RTL8192U=m
>> CONFIG_RTL8192E=m
>
> That is good. Larry (lwfinger) is a kernel and wireless expert here.
> Lets see what he determines that this output means.

As has been reported several times in these forums, the standard configuration
file does not enable the driver for RTL8192SE - i.e. “# CONFIG_RTL8192SE is not
set”. To use the device, you can do one of three options:

(1) Edit .config and change “# CONFIG_RTL8192SE is not set” to
“CONFIG_RTL8192SE=m”
(2) run ‘make xconfig’, find “Device Drivers” and “Wireless”, the change the
entry for RTL8192SE
(3) run ‘make menuconfig’ and make the RTL8192SE change yourself.

As (1) does not require adding any extra packages, I recommend it; however, at
your liesure, you might try the others and install the packages that they need.
When you want to make large-scale changes to the configuration, the menus are
easier.

38

tried #1 and rebooted but still no wireless , what next?

CONFIG_RTL8192CE is not set

CONFIG_RTL8192SE=m

CONFIG_RTL8192CU is not set

CONFIG_RTL8192U=m
CONFIG_RTL8192E=m

39

On 08/06/2011 04:26 PM, zuser wrote:
>
> tried #1 and rebooted but still no wireless , what next?
>
> # CONFIG_RTL8192CE is not set
> CONFIG_RTL8192SE=m
> # CONFIG_RTL8192CU is not set
> CONFIG_RTL8192U=m
> CONFIG_RTL8192E=m

First of all, is the driver loaded? What does ‘lsmod | grep 8192’ show?

If it is available, look at the output of ‘dmesg’.

40

Driver is not loading.
‘lsmod’ give no results