Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
X-org : how to remove CONFIG_FB_RADEON in /proc/config.gz?
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
lowley
n00b
n00b


Joined: 22 Jul 2016
Posts: 47

PostPosted: Fri Jul 29, 2016 3:09 pm    Post subject: X-org : how to remove CONFIG_FB_RADEON in /proc/config.gz? Reply with quote

hello,

I am facing to a problem in the launching of startx (which could allow me to test the X server.)

I've got these errors :

Quote:
[ 1360.866] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 1360.866] (--) using VT number 7

[ 1360.869] (II) [KMS] drm report modesetting isn't supported.
[ 1360.869] (EE) open /dev/dri/card0: No such file or directory
[ 1360.869] (WW) Falling back to old probe method for modesetting
[ 1360.869] (EE) open /dev/dri/card0: No such file or directory
[ 1360.869] (EE) Screen 0 deleted because of no matching config section.
[ 1360.869] (II) UnloadModule: "radeon"
[ 1360.870] (EE) Screen 0 deleted because of no matching config section.
[ 1360.870] (II) UnloadModule: "modesetting"
[ 1360.870] (EE) Device(s) detected, but none match those in the config file.
[ 1360.870] (EE)
Fatal server error:
[ 1360.870] (EE) no screens found(EE)
[ 1360.870] (EE)



and the kernel is : http://pastebin.com/7hzRke7J
this kernel has got CONFIG_FB_RADEON not set, which is good, but the module seems to be present anyway :

Quote:
gentoo linux # zgrep -iE 'radeon|firm' /proc/config.gz
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_FIRMWARE_IN_KERNEL is not set
CONFIG_EXTRA_FIRMWARE=""
# Altera FPGA firmware download module
CONFIG_LIBERTAS_THINFIRM=m
# CONFIG_LIBERTAS_THINFIRM_DEBUG is not set
CONFIG_LIBERTAS_THINFIRM_USB=m
CONFIG_HOSTAP_FIRMWARE=y
CONFIG_HOSTAP_FIRMWARE_NVRAM=y
CONFIG_RT2X00_LIB_FIRMWARE=y
# CONFIG_CYPRESS_FIRMWARE is not set
CONFIG_DRM_LOAD_EDID_FIRMWARE=y
CONFIG_DRM_RADEON=m
# CONFIG_DRM_RADEON_USERPTR is not set
CONFIG_DRM_RADEON_UMS=y
# CONFIG_FIRMWARE_EDID is not set
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
# Firmware Drivers
CONFIG_FIRMWARE_MEMMAP=y
# CONFIG_GOOGLE_FIRMWARE is not set
# EFI (Extensible Firmware Interface) Support
# CONFIG_TEST_FIRMWARE is not set




in the kernel menu, the line "support for frame buffer devices" has got a star that I can't remove. all the frame buffer hardware drivers are unset, and a search of "fb_radeon" gives me :

Symbol: FB_RADEON [=n]
│ Type : tristate
│ Prompt: ATI Radeon display support
│ Location:
│ -> Device Drivers
│ -> Graphics support
│ (1) -> Frame buffer Devices
│ Defined at drivers/video/fbdev/Kconfig:1327
│ Depends on: HAS_IOMEM [=y] && FB [=y] && PCI [=y]
│ Selects: FB_BACKLIGHT [=n] && FB_MODE_HELPERS [=n] && FB_CFB_FILLRECT

how can I remove this module and thus enabling X?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Fri Jul 29, 2016 6:32 pm    Post subject: Reply with quote

lowley,

A few things ...

/proc/config.gz is the configuration of the kernel that is actually running.
The whole /proc filesystem shows internal kernel data structures from the running kernel.

The kernel in the pastebin does indeed have # CONFIG_FB_RADEON is not set.
That means that you are not using the kernel that is derived fron that .config file.
The output of
Code:
uname -v
may help convince you. That is the build time of the running kernel.

lowley wrote:
... support for frame buffer devices" has got a star that I can't remove. all the frame buffer hardware drivers are unset ...


That's correct. You do have a framebuffer driver but its not one in the list of framebuffer drivers. Its provided as part of the Radeon kernel option.
You should see one Tux logo pec CPU core at boot. Only frame buffer consoles can display graphics.

Lastly, This thread is relevant to your other thread on starting Xorg the posts would both fit and be useful there.
As you have made a reference to this topic and merging your two topics would be confusing for later readers, I will not merge the topics this time.
_________________
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
lowley
n00b
n00b


Joined: 22 Jul 2016
Posts: 47

PostPosted: Fri Jul 29, 2016 7:22 pm    Post subject: Reply with quote

hello NeddySeagoon

I see I've got to learn a lot of things!

For the moment, my goal is to master a little the gentoo install process, in order to being able to install it rather rapidly.
next, I planned to see the USE variable.

thank you for helping me!

I am disappointed : I followed the tuto at https://wiki.gentoo.org/wiki/Kernel/Rebuild, but after the reboot, "uname -v" gives me the date of 2 days ago... do you know where does the problem come from?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Fri Jul 29, 2016 8:04 pm    Post subject: Reply with quote

lowley,

Normally, the error comes from not mounting /boot before you installed the kernel to boot.
Another cause is not updating grub to use the new kernel.

You have three places called boot on your system. They often appear to be the same and the naming is used interchangeably, which makes it harder to understand.
There is the /boot directory on the root filesystem
There is the boot partition (no leading /), it refers to an area on your HDD.
There is the filesystem on the boot partition (no leading /) of your HDD. This is often referred to as boot or /boot but really its not. However, it is mounted at /boot when you want to write to it.

Keep those things in mind. Now a little of the boot process.
Grub reads the kernel into memory and passes control to it. Grub cannot use the kernels filesystem tree to lead the kernel as it does net yet exist. The kernel is not even in memory
Instead, grub makes its own arrangements to read the filesystem on the boot partition of your HDD. That's important too.

When the filesystem on the boot partition is not mounted an the /boot directory on the root filesystem, anything written to /boot goes onto the root partition.
Its not an error, the write will succeed. Grub will not find a kernel installed here.
When the filesystem on the boot partition is mounted on /boot and you install a kernel, it goes to the boot partition where grub can find it.

Normally, Gentoo does not automatically mount the filesystem on the boot partition at /boot. You need to do it yourself.
Everyone forgets once in a while, so
Code:
uname -v
is a good test after your first boot into a new/updated kernel.

The test is
Code:
ls /boot
It should be empty.
Then
Code:
mount /boot
ls /boot
This time, you should see your kernel and the grub directory.

Its not an error to mount a filesystem on a directory that contains files or other directories.
However, the original content will be hidden until the filesystem is unmounted.
_________________
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
lowley
n00b
n00b


Joined: 22 Jul 2016
Posts: 47

PostPosted: Fri Jul 29, 2016 8:57 pm    Post subject: Reply with quote

well, I understand, but every time I follow the kernel tutorial, I use the statement "mount /boot". I retried just a few seconds ago and the "uname -v" statement gives a date 2 days ago.
this is not a calendar error of my computer, the statement "date" gives me the date of today.

here is some potential interesting stuff:

Quote:
[00:49:31,root@gentoo$ ls /boot
[00:49:59,root@gentoo$ mount /boot
[00:50:05,root@gentoo$ ls /boot
config-4.4.6-gentoo
config-4.4.6-gentoo.old
grub
initramfs-genkernel-x86_64-4.4.6-gentoo
kernel-genkernel-x86_64-4.4.6-gentoo
lost+found
System.map-4.4.6-gentoo
System.map-4.4.6-gentoo.old
System.map-genkernel-x86_64-4.4.6-gentoo
vmlinuz-4.4.6-gentoo
vmlinuz-4.4.6-gentoo.old
[00:50:09,root@gentoo$ make install
sh ./arch/x86/boot/install.sh 4.4.6-gentoo arch/x86/boot/bzImage \
System.map "/boot"
[00:50:39,root@gentoo$ grub2-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/kernel-genkernel-x86_64-4.4.6-gentoo
Found initrd image: /boot/initramfs-genkernel-x86_64-4.4.6-gentoo
Found linux image: /boot/vmlinuz-4.4.6-gentoo
Found initrd image: /boot/initramfs-genkernel-x86_64-4.4.6-gentoo
Found linux image: /boot/vmlinuz-4.4.6-gentoo.old
Found initrd image: /boot/initramfs-genkernel-x86_64-4.4.6-gentoo
done
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Fri Jul 29, 2016 9:05 pm    Post subject: Reply with quote

lowley,

That shows that boot was always correctly mounted. That's good.

Code:
mount /boot
ls /boot -l
will be interesting too as it will show the file timestamps.

Please post the output using code tags rather than quote tags as it makes it easier to read.
_________________
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
lowley
n00b
n00b


Joined: 22 Jul 2016
Posts: 47

PostPosted: Fri Jul 29, 2016 9:22 pm    Post subject: Reply with quote

ok, here are the results:

Code:
gentoo ~ # ls /boot
gentoo ~ # mount /boot
gentoo ~ # ls /boot -l
total 55457
-rw-r--r-- 1 root root   141960 Jul 30  2016 config-4.4.6-gentoo
-rw-r--r-- 1 root root   141960 Jul 29 23:14 config-4.4.6-gentoo.old
drwxr-xr-x 6 root root     1024 Jul 30  2016 grub
-rw-r--r-- 1 root root 30294488 Jul 27 19:58 initramfs-genkernel-x86_64-4.4.6-gentoo
-rw-r--r-- 1 root root  5231072 Jul 27 18:00 kernel-genkernel-x86_64-4.4.6-gentoo
drwx------ 2 root root    12288 Jul 27 16:15 lost+found
-rw-r--r-- 1 root root  3126740 Jul 30  2016 System.map-4.4.6-gentoo
-rw-r--r-- 1 root root  3433556 Jul 29 23:14 System.map-4.4.6-gentoo.old
-rw-r--r-- 1 root root  3126740 Jul 27 18:00 System.map-genkernel-x86_64-4.4.6-gentoo
-rw-r--r-- 1 root root  5231072 Jul 30  2016 vmlinuz-4.4.6-gentoo
-rw-r--r-- 1 root root  6041952 Jul 29 23:14 vmlinuz-4.4.6-gentoo.old


it seems to be a mess, as the kernel file seems to be 2 days old...
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Fri Jul 29, 2016 9:44 pm    Post subject: Reply with quote

lowley,

You have 3 kernel files there.
Code:
Jul 27 18:00 kernel-genkernel-x86_64-4.4.6-gentoo
Jul 30  2016 vmlinuz-4.4.6-gentoo
Jul 29 23:14 vmlinuz-4.4.6-gentoo.old


Previously, grub found all three.
Code:
Generating grub configuration file ...
Found linux image: /boot/kernel-genkernel-x86_64-4.4.6-gentoo
Found initrd image: /boot/initramfs-genkernel-x86_64-4.4.6-gentoo
Found linux image: /boot/vmlinuz-4.4.6-gentoo
Found initrd image: /boot/initramfs-genkernel-x86_64-4.4.6-gentoo
Found linux image: /boot/vmlinuz-4.4.6-gentoo.old
Found initrd image: /boot/initramfs-genkernel-x86_64-4.4.6-gentoo
done
so that's right too.

Is it that you are choosing the wrong menu item in the grub menu?

You only have a single initrd file i
Code:
nitramfs-genkernel-x86_64-4.4.6-gentoo
which matches your original genkernel built kernel/initrd pair.
That may be harmless, I have not looked at your config in detail. Its possible that the vmlinuz-4.4.6-gentoo (your new kernel) has settings that are incompatible with the initrd initramfs-genkernel-x86_64-4.4.6-gentoo.
However, you have not been using vmlinuz-4.4.6-gentoo as your kernel yet.
_________________
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
lowley
n00b
n00b


Joined: 22 Jul 2016
Posts: 47

PostPosted: Fri Jul 29, 2016 9:58 pm    Post subject: Reply with quote

Is initrd really always needed?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Fri Jul 29, 2016 10:18 pm    Post subject: Reply with quote

lowley,

No, an initrd is not always needed. To boot without one, everything needed to boot must be configured in the kernel as <*>.
The initrd provides a way to load modules before root is mounted.
It also offers a home for userspace programs needed to mount root.

You cannot use root=UUID= ... in grub either, as working with UUID, requires the userspace mount command.
_________________
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
lowley
n00b
n00b


Joined: 22 Jul 2016
Posts: 47

PostPosted: Fri Jul 29, 2016 10:28 pm    Post subject: Reply with quote

I would rather keep initramfs.

I don't know what to do
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Sat Jul 30, 2016 10:40 am    Post subject: Reply with quote

lowley,

genkernel can help.

I've never used it, so my knowledge is limited.
It can 'automatically' build your kernel and initrd.
It can 'automatically' build your kernel and initrd allowing you some manual configuration changes in the process.
genkernel can build your kernel and initrd using a .config file you give it.
genkernel can just build your initrd.

As far as I'm aware, genkernel is the only tool that does both kernel and initrd. There are other tools that will build your initrd only.
You can also do it all yourself.

Learning the kernel setup is something you can sidestep for a long time by using genkernel. Indeed, there is no need to learn it at all as long as you know how to make genkernel work for you.

Personally, I hate automatic things involved in the boot process, so I make both the kernel and initrd by hand.
To make that easy, there are no kernel modules in the initrd, so it is good for the life of the install. It was made in 2009.
The kernel contains all the options it needs to boot as built in.

Right now, go with genkernel doing everything, allowing you some manual configuration changes.
When you have something that works, save the .config and learn how to use that with genkernel in the future.

Start a new thread if you need detailed help with genkernel.
_________________
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
lowley
n00b
n00b


Joined: 22 Jul 2016
Posts: 47

PostPosted: Sat Jul 30, 2016 2:33 pm    Post subject: Reply with quote

ok, with genkernel is works.
thank you.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
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