bbswitch: no discrete VGA device found

English Install/Boot/Login
#1

I am running version 20210914 and since the last update I get several times the following message at boot; “bbswitch: no discrete VGA device found”. On the internet I can find all kind of information that this refers to the bumblebee driver and Nvidia cards etc. But I have Intel graphics. Why do I get several of these messages at boot? This is no urgent cry for help - everything works fine but I would like to know what is going on and possibly if this message, if it does not refer to anything problematic, can be turned off.
CHeers
Uli

#2

Remove bbswitch packages perhaps?

#3

Might be interesting to show us output from

inxi -GSxxx
#4

Even better, inxi -GSay.

#5

I was really only after the graphics card info and for that the first suffices. In any case the OP may need to update inxi first (as I did for inxi version 3.1.00-00)…

sudo inxi -U
#6

Back again on my computer. Here the commands (as root to be sure nothing is missing)

**linux-4skc:~ #** inxi -GSxxx 
**System:    Host:** linux-4skc **Kernel:** 5.14.2-1-default x86_64 **bits:** 64 **compiler:** gcc **v:** 11.2.1 **Console:** tty pts/1 **wm:** kwin_x11  
           **DM:** SDDM **Distro:** openSUSE Tumbleweed 20210914  
**Graphics:  Device-1:** Intel UHD Graphics 620 **vendor:** Hewlett-Packard **driver:** i915 **v:** kernel **bus-ID:** 00:02.0 **chip-ID:** 8086:5917  
           **class-ID:** 0300  
           **Device-2:** Cheng Uei Precision Industry (Foxlink) HP Wide Vision HD Camera **type:** USB **driver:** uvcvideo **bus-ID:** 1-3:3  
           **chip-ID:** 05c8:03ab **class-ID:** 0e02  
           **Display:** **server:** X.Org 1.20.13 **compositor:** kwin_x11 **driver:** **loaded:** modesetting **unloaded:** fbdev,vesa  
           **alternate:** intel **resolution:** 1920x1080~60Hz **s-dpi:** 96  
           **OpenGL:** **renderer:** Mesa Intel UHD Graphics 620 (KBL GT2) **v:** 4.6 Mesa 21.2.1 **direct render:** Yes  
**linux-4skc:~ #** inxi -GSay 
**System:** 
  **Host:** linux-4skc **Kernel:** 5.14.2-1-default x86_64 **bits:** 64 **compiler:** gcc  
  **v:** 11.2.1  
  **parameters:** BOOT_IMAGE=/boot/vmlinuz-5.14.2-1-default  
  root=UUID=5e72aed7-50c1-44b3-93b3-fb097175e0ac  
  resume=/dev/disk/by-id/ata-Samsung_SSD_860_EVO_500GB_S3YANB0K300461Z-part3  
  acpi_osi=! plymouth.enable=0 quiet showopts  
  **Console:** tty pts/1 **wm:** kwin_x11 **DM:** SDDM  
  **Distro:** openSUSE Tumbleweed 20210914  
**Graphics:** 
  **Device-1:** Intel UHD Graphics 620 **vendor:** Hewlett-Packard **driver:** i915  
  **v:** kernel **bus-ID:** 00:02.0 **chip-ID:** 8086:5917 **class-ID:** 0300  
  **Device-2:** Cheng Uei Precision Industry (Foxlink) HP Wide Vision HD Camera  
  **type:** USB **driver:** uvcvideo **bus-ID:** 1-3:3 **chip-ID:** 05c8:03ab **class-ID:** 0e02  
  **Display:** **server:** X.Org 1.20.13 **compositor:** kwin_x11 **driver:**  
  **loaded:** modesetting **unloaded:** fbdev,vesa **alternate:** intel **display-ID:** :0  
  **screens:** 1  
  **Screen-1:** 0 **s-res:** 1920x1080 **s-dpi:** 96 **s-size:** 508x285mm (20.0x11.2")  
  **s-diag:** 582mm (22.9")  
  **Monitor-1:** eDP-1 **res:** 1920x1080 **hz:** 60 **dpi:** 142 **size:** 344x193mm (13.5x7.6")  
  **diag:** 394mm (15.5")  
  **OpenGL:** **renderer:** Mesa Intel UHD Graphics 620 (KBL GT2) **v:** 4.6 Mesa 21.2.1  
  **direct render:** Yes  
**linux-4skc:~ #**
#7

No need to run both - same output with respect to your graphics card. Did you remove the bbswitch packages yet?

#8

Do you know the reason why acpi_osi=! is in use? Kaby Lake GT2 seems awfully new to need something like that. If you don’t know, try removing it. Neither of my Kaby Lakes need it. If you do need it, check to see if a BIOS upgrade is available.

#9

TW’s 3.3.whatever isn’t problematic like 3.1.00 is in Leap. G received serious improvement between them, and y was added. Whether a existed in 3.1.00 I don’t remember, but likely not.

#10

I assumed that would be the case. However, both report the same hardware, and I guess it is only that bbswitch is installed that the OP observes the message “bbswitch: no discrete VGA device found”, rather than any other issue. I just wanted to know if an additional graphics card was present.

#11

Thank you, mrmazda. I haven’t removed bbswitch yet but will do this now. What package do you mean when you wrtie removing Kaby Lake? I tried a zypper se Kaby Lake which resulted in approx 80 packages none of which were installed. BTW I have
inxi-3.3.03-1.2.noarch installed.

#12

Thank you deano_ferrari for your help. This computer never had a different graphics card. It is a laptop which I bought some years ago and I selected it because it had the intel graphics as I wanted it to be used with Tumbleweed. That bbswich package is removed now and I don’t know why it was installed. Must have been at the last update because this error message was not there before.

#13

Kaby Lake is the codename of your 14nm 7th gen CPU’s series. Intel likes naming after lakes. I was referring to the relationship between CPU age and the ACPI workaround parameter.

#14

Thanks mrmazda, what you are talking is beyond my inderstanding (acpi_osi=!; etc.) I don’t know wat you mean to be removed. But I just restarted and it went OK without error message after these 2 bbswitch packages were removed. So everything works now as it should. Thanks you for your help.
Uli

#15

Ok, that should be the end of it.

#16

acpi_osi=! is a kernel command line option. Such options are often added, amended or removed in the process of troubleshooting, or avoiding or mitigating bugs. Making such change on a temporary basis is done by striking the E key when the Grub menu appears, which puts Grub into edit mode.

I suppose acpi_osi=! could be responsible for the installation of bbswitch packages, which are used when an Intel IGP is accompanied by an AMD or NVidia GPU in a laptop.

#17

Do you have tlp installed? Starting with TW20210914 tlp-1.3.1-4.1.noarch pulls in the additional packages bbswitch and bbswitch-kmp-default (i.e. recommends bbswitch). According to https://build.opensuse.org/request/show/900571 this was introduced because “the proposed change allows me to control ThinkPad Carbon X1 4th Gen battery without installation of acpi_call from third party repos.” It is obvious that there have not been any further tests with different hardware. I have opened a bug report regarding tlp a cuple of days ago, but closed it as invalid (https://bugzilla.opensuse.org/show_bug.cgi?id=1190631). Please feel free to open it again.

#18

Thanks for chiming in here, that might indeed explain it. (I don’t see how any grub option might be related to this.)

#19

Good evening everyone!
That message started to appear to me too.
Not to open another topic like it…
Can I put a lock on tlp, and then uninstall bbswitch and bbswitch-kmp-default?
Or maybe leave the message if it doesn’t cause any problems?

#20

I would uninstall bbswitch and bbswitch-kmp-default, then zypper al bbswitc*.