![]() ![]() Once that is done, go to YaST/Software Management, search for 'broadcom-wl' and select that for installation. The place to get commonly used "extras" for openSuSE is the packman repository, which can easily be added to the active repository list by going to YaST/Software Repositories/Add, selecting Community Repositories, and then choosing the Packman Repository. So it's time to go back and look at them to see if I can get wireless going. Now, if I recall correctly from my previous systems with Broadcom adapters, this driver that Ubuntu calls "STA" is known on other distribusions as the "Broadcom WL" driver. I removed the ASUS USB adapter, connected to my wi-fi network via the Broadcom adapter, and everything was working just fine. I moved that item to the top of the priority list, crossed my fingers and rebooted. I didn't recall seeing that entry when I was in the Boot menu the first time. There was nothing about "openSuSE" in the list, but there was a strange new entry for "HDD: WDE WD5000LPVX-22VOTTO", which is absolutely as clear as mud. On the 'Boot' page, there is a 'Boot priority order ' list, and "Windows Boot Manager" was right at the top of that list. I rebooted again, and this time went into BIOS setup (F2). Sure enough, the boot order had been changed back to have Windows Boot Manager first. Then I checked the boot configuration again. I rebooted and used F12 to get Boot Select, then selected openSuSE from there, and it came up ok. ARRRRGGGHHHH! NO! Acer doesn't do this kind of garbage, HP/Compaq does! I have two or three other Acer laptops around here, and the boot configuration is perfectly stable on them! It was correct, with "opensuse-secureboot" defined and first in the boot sequence list. How do i mark this question as solved? editing the title tells me that's a no-no.The best VR headsets right now (and they're not just from Meta)Īfter the installation process completed, and before I rebooted, I checked the UEFI boot configuration ( efibootmgr -v). it seems like i did all this before but apparently not. ran it through hex2hcd, then moved the output to \lib\firmware\brcm as both BCM.hcd and BCM43142A0-0a5c-216c.hcd based on the info returned by lsusb ( Bus 001 Device 004: ID 0a5c:216c Broadcom Corp. If I need to post more info, pls tell what else would be useful.įinally i went back to windows, looked in the device manager for the. Any suggestions/comments would be gratefully appreciated. I'm not exactly a noob, but the road signs all seem to be written in a language I can't quite translate. Bluetooth: hci0: BCM: Reading local version info failed (-110)īCM43142A0_001.001. and BCM43142A0_001.001. over from the Windows partition, but again, I don't know what to do with them. Bluetooth: hci0: command 0x1001 tx timeout Bluetooth: hci0: BCM: Patch command 0a0a failed (-110) Bluetooth: BNEP socket layer initialized Bluetooth: BNEP filters: protocol multicast Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: hci0: command 0x0a0a tx timeout ![]() Bluetooth: L2CAP socket layer initialized Bluetooth: HCI device and connection manager initialized Grep-ing through dmesg gives me Bluetooth: Core ver 2.22 Lsusb gives me Bus 001 Device 004: ID 0a5c:216c Broadcom Corp. I managed to download something (at this point I can't remember exactly what) but now When I started, I was getting complaints about missing firmware. I managed to configure most everything but blueman tells me there are no adaptors. ![]() I repartitioned the drive and installed Ubuntu 18.04 (kernel 4.15.0-33.generic). I have a hp notebook 15 with Windows 10 (Bluetooth works there). hoping that someone can guide me through this specifically. I can see that many people have problems with this, but many slightly different answers are adding to my confusion. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |