Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
BCM4352 Broadcom WiFi not working
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5  Next  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 45435
Location: 56N 3W

PostPosted: Thu Apr 16, 2020 7:12 pm    Post subject: Reply with quote

spike32,

Your problem reports are a bit on the terse side.

What does
Code:
uname -a
show?
The date and time will be sometime during April 16, or you are not running your new kernel?

Did you do
Code:
emerge @module-rebuild
after the new kernel was installed?

Does dmesg show that your kernel is tainted?
If not the module failed to load.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Thu Apr 16, 2020 8:34 pm    Post subject: Reply with quote

NeddySeagoon wrote:
spike32,

Your problem reports are a bit on the terse side.

What does
Code:
uname -a
show?
The date and time will be sometime during April 16, or you are not running your new kernel?

Did you do
Code:
emerge @module-rebuild
after the new kernel was installed?

Does dmesg show that your kernel is tainted?
If not the module failed to load.

uname -a
Code:
Linux mauro 5.4.28-gentoo-x86_64 #1 SMP Tue Apr 14 01:21:35 CEST 2020 x86_64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz GenuineIntel GNU/Linux

dmesg https://pastebin.com/mx10UFaU
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Thu Apr 16, 2020 8:36 pm    Post subject: Reply with quote

fturco wrote:
I suggest verifying broadcom-sta ebuild's requirements directly from /proc/config.gz.

What do you mean with this?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 45435
Location: 56N 3W

PostPosted: Thu Apr 16, 2020 8:56 pm    Post subject: Reply with quote

spike32,

You have messed up the kernel install or not rebooted into your new kernel.
Code:
Tue Apr 14 01:21:35 CEST
is Tuesdays kernel. I was expecting todays date.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Thu Apr 16, 2020 8:59 pm    Post subject: Reply with quote

NeddySeagoon wrote:
spike32,

You have messed up the kernel install or not rebooted into your new kernel.
Code:
Tue Apr 14 01:21:35 CEST
is Tuesdays kernel. I was expecting todays date.

Could you please just clarify one thing? When I apply changes to the kernel what I do is:
- cd /usr/src/linux
- make menuconfig
- save and exit
- make oldconfig
- make -j5
- reboot
Is this process right?
Back to top
View user's profile Send private message
axl
Veteran
Veteran


Joined: 11 Oct 2002
Posts: 1027
Location: Romania

PostPosted: Thu Apr 16, 2020 10:34 pm    Post subject: Reply with quote

Well, these steps are lacking the install part. I never used make install. So not sure how that works.

But i do make modules_install. And I do manually copy arch/x86/boot/bzImage /boot/${kernel}. This last part being the most important one. Again, not sure what make install does... but in your case you're not booting the new kernel.
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 15324

PostPosted: Fri Apr 17, 2020 1:47 am    Post subject: Reply with quote

Those steps are correct, but incomplete. They leave you with a compiled kernel that is not active, because you never installed it or updated your bootloader to use it.
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Fri Apr 17, 2020 7:19 am    Post subject: Reply with quote

Hu wrote:
Those steps are correct, but incomplete. They leave you with a compiled kernel that is not active, because you never installed it or updated your bootloader to use it.

So which is the missing step?
Back to top
View user's profile Send private message
fturco
Veteran
Veteran


Joined: 08 Dec 2010
Posts: 1051
Location: Italy

PostPosted: Fri Apr 17, 2020 9:47 am    Post subject: Reply with quote

- cd /usr/src/linux
- make menuconfig
- save and exit
- make oldconfig
- make -j5
- make install
- make modules_install
- update boot loader configuration
- reboot
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Fri Apr 17, 2020 9:50 am    Post subject: Reply with quote

fturco wrote:

- update boot loader configuration

This one with
Code:
grub-mkconfig -o /boot/grub/grub.cfg
am I right?
Back to top
View user's profile Send private message
fturco
Veteran
Veteran


Joined: 08 Dec 2010
Posts: 1051
Location: Italy

PostPosted: Fri Apr 17, 2020 9:51 am    Post subject: Reply with quote

spike32 wrote:
fturco wrote:
I suggest verifying broadcom-sta ebuild's requirements directly from /proc/config.gz.

What do you mean with this?

Basically, if you enable those options you will be able to get the currently running kernel configuration from the /proc/config.gz file.
I suggested that in order to detect possible user mistakes when building/installing a new kernel, since in those cases it may happen that /usr/src/linux/.config and /proc/config.gz differ.
Back to top
View user's profile Send private message
fturco
Veteran
Veteran


Joined: 08 Dec 2010
Posts: 1051
Location: Italy

PostPosted: Fri Apr 17, 2020 9:52 am    Post subject: Reply with quote

spike32 wrote:
fturco wrote:

- update boot loader configuration

This one with
Code:
grub-mkconfig -o /boot/grub/grub.cfg
am I right?

If you use GRUB 2, then yes, it's right.
Back to top
View user's profile Send private message
fturco
Veteran
Veteran


Joined: 08 Dec 2010
Posts: 1051
Location: Italy

PostPosted: Fri Apr 17, 2020 9:58 am    Post subject: Reply with quote

I'm sorry, I forgot one important step:
- cd /usr/src/linux
- make menuconfig
- save and exit
- make oldconfig
- make -j5
- make install
- make modules_install
- emerge @module-rebuild
- update boot loader configuration
- reboot
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7677
Location: Saint Amant, Acadiana

PostPosted: Fri Apr 17, 2020 10:26 am    Post subject: Reply with quote

Only one is needed, make menuconfig or make oldconfig, not both.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Fri Apr 17, 2020 10:44 am    Post subject: Reply with quote

fturco wrote:
I'm sorry, I forgot one important step:
- cd /usr/src/linux
- make menuconfig
- save and exit
- make oldconfig
- make -j5
- make install
- make modules_install
- emerge @module-rebuild
- update boot loader configuration
- reboot

I have done all these steps but now it stucks at boot
Code:
>> Determining root devices (trying UUID=1c3516c6-4431-49d3-91d3-955f1a7b4884) ........
!! Block device UUID=1c3516c6-4431-49d3-91d3-955f1a7b4884 is not a valid root device ...
!! Could not find the root block device in UUID=1c3516c6-4431-49d3-91d3-955f1a7b4884.
!! Please specify another value or:
!! - press Enter for the same
!! - type “shell” for a shell
!! - type “q” to skip ...
root block device(UUID=1c3516c6-4431-49d3-91d3-955f1a7b4884) ::
Back to top
View user's profile Send private message
fturco
Veteran
Veteran


Joined: 08 Dec 2010
Posts: 1051
Location: Italy

PostPosted: Fri Apr 17, 2020 10:54 am    Post subject: Reply with quote

Please paste the output of the following commands (from a live CD/USB):
Code:
grep GRUB_CMDLINE_LINUX /etc/default/grub
lsblk -f
blkid
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7677
Location: Saint Amant, Acadiana

PostPosted: Fri Apr 17, 2020 11:09 am    Post subject: Reply with quote

You need initramfs for mounting root by UUID during boot.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Fri Apr 17, 2020 11:11 am    Post subject: Reply with quote

fturco wrote:
grep GRUB_CMDLINE_LINUX /etc/default/grub

Code:
GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash”
GRUB_CMDLINE_LINUX=“”

Quote:
lsblk -f

Code:
sda1 vfat         EFI          67E3-17ED
sda2
sda3 ntfs                                01D56AEE8KECAAF0
sda4 vfat                 DATA
sda5 ntfs
sda6 swap                              337f5f42-e2da-485e-a87c-08c5288b5530
sda7 ext4                               1c3516c6-4431-49d3-955f1a7b4884

Quote:
blkid

Code:
/dev/sda1: LABEL_FATBOOT=“EFI” LABEL=“EFI” UUID=“67E3-17ED” TYPE=“vfat” PARTLABEL=“EFI System Partition” PARTUUID=“43d688b8-4b17-41e5-9fe2-29b82d2bf68f”

Do you need the other partitions too? Quite hard to write everything on an iPad ahaha
Back to top
View user's profile Send private message
fturco
Veteran
Veteran


Joined: 08 Dec 2010
Posts: 1051
Location: Italy

PostPosted: Fri Apr 17, 2020 11:47 am    Post subject: Reply with quote

Is /dev/sda7 your root partition? I noticed /dev/sda7's UUID does not match the UUID in the boot error message, but it may depend on the fact that you're using a tablet...

Do you use UUIDs in /etc/fstab?
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7677
Location: Saint Amant, Acadiana

PostPosted: Fri Apr 17, 2020 12:09 pm    Post subject: Reply with quote

I see we are getting lost here.

The easiest way to boot it right now is to edit the kernel command line and replace the UUID with proper sdaX device. I'm not a Grub user myself, but I believe you can edit the commandline after you hit 'e' at Grub menu screen.

fstab is irrelevant, it resides in root filesystem which is not accessible at this stage of boot.

Once booted you need to use PARTUUID instead of UUID and reconfigure your Grub.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
fturco
Veteran
Veteran


Joined: 08 Dec 2010
Posts: 1051
Location: Italy

PostPosted: Fri Apr 17, 2020 12:58 pm    Post subject: Reply with quote

I'm a GRUB user and I confirm one can hit the "e" key at the menu for editing kernel parameters. I suggest to add the root=/dev/sda7 parameter.
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Fri Apr 17, 2020 1:07 pm    Post subject: Reply with quote

fturco wrote:
Is /dev/sda7 your root partition? I noticed /dev/sda7's UUID does not match the UUID in the boot error message, but it may depend on the fact that you're using a tablet...

Do you use UUIDs in /etc/fstab?

Yes it is, and yes I do
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Fri Apr 17, 2020 1:09 pm    Post subject: Reply with quote

fturco wrote:
I'm a GRUB user and I confirm one can hit the "e" key at the menu for editing kernel parameters. I suggest to add the root=/dev/sda7 parameter.

If I add this it doesn’t change anything
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Fri Apr 17, 2020 1:31 pm    Post subject: Reply with quote

spike32 wrote:
fturco wrote:
I'm a GRUB user and I confirm one can hit the "e" key at the menu for editing kernel parameters. I suggest to add the root=/dev/sda7 parameter.

If I add this it doesn’t change anything

Code:
Could not find the root block device in /dev/sda7

Is it strange, isn’t it?
Back to top
View user's profile Send private message
fturco
Veteran
Veteran


Joined: 08 Dec 2010
Posts: 1051
Location: Italy

PostPosted: Fri Apr 17, 2020 1:52 pm    Post subject: Reply with quote

Make sure you enabled support for the following kernel options:
  • CONFIG_BLK_DEV_SD=y
  • CONFIG_ATA=y
  • CONFIG_EXT4_FS=y
  • CONFIG_MSDOS_PARTITION=y (if you use MSDOS partition tables)
  • CONFIG_EFI_PARTITION=y (if you use GPT partition tables)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page Previous  1, 2, 3, 4, 5  Next
Page 4 of 5

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum