benzolius

Thanks, Funtoo!
 
Thanks, Daniel and others and for every contribution. It was a long journey, but now from a Kubuntu background I'm in the process of adopting a Funtoo system with KDE Plasma 5.
 
Regards

Thanks, Funtoo!
 
Thanks, Daniel and others and for every contribution. It was a long journey, but now from a Kubuntu background I'm in the process of adopting a Funtoo system with KDE Plasma 5.
 
Regards

Hi cardinal,
 
I'd like to rotate Left = Counterclockwise
 
Here are the values:
Xorg.0.log:
 
https://bpaste.net/show/4bbf576df8d8
 
lxrandr -q
 
Resolution: 1920x1200   Refresh Rate: 59.95
 
lspci -nn | grep VGA:
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] [1002:6658] Currently I have only the default /etc/X11/xorg.conf.d/20opengl.conf:
 
Section "Files"                                                                                                                                                                                                                                                                 EndSection  
 
Thanks for help.

My guess is rotation fails on your graphics system because direct rendering is not working.
Xorg.0.log lines 338,436-439,444-447
According to https://wiki.gentoo.org/wiki/Radeon your Sea Islands Bonaire XTX [Radeon R7 260X/360] should have:
VIDEO_CARDS="radeon radeonsi" set in /etc/portage/make.conf
USE="glamor" in xorg-server and xf86-video-ati build.
USE="gbm egl gles2 llvm" in the mesa build.
Install mesa-progs which provides glxgears and glxinfo for troubleshooting.
 
The information below is from my system:
The rotation configuration works on my system using an evergreen cedar R5450 which is a cheaper lower spec card that uses the radeon driver.
I have VIDEO_CARDS="radeon r600 nouveau" so I can use my nvidia geforce 8400gs card when needed.

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] Xorg.0.log 

rj@funtoo ~ $ xrandr -q Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192 HDMI-0 disconnected primary (normal left inverted right x axis y axis) DVI-0 disconnected (normal left inverted right x axis y axis) VGA-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm 1280x1024 60.02*+ 75.02 1280x960 60.00 1152x864 75.00 1024x768 75.08 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 640x480 75.00 72.81 66.67 60.00 720x400 70.08 rj@funtoo ~ $ equery u xorg-server [ Legend : U - final flag setting for installation] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for x11-base/xorg-server-1.17.4: U I - - dmx : Build the Distributed Multiheaded X server - - doc : Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally + + glamor : Enable Glamor OpenGL 2D acceleration + + ipv6 : Add support for IP version 6 - - kdrive : Build the kdrive X servers - - libressl : Use dev-libs/libressl as SSL provider (might need ssl USE flag), packages should not depend on this USE flag - - minimal : Install a very minimal build (disables, for example, plugins, fonts, most drivers, non-critical features) + + nptl : Enable support for Native POSIX Threads Library, the new threading module (requires linux-2.6 or better usually) - - static-libs : Build static versions of dynamic libraries as well + + suid : Enable setuid root program, with potential security risks - - systemd : Enable use of systemd-specific libraries and features like socket activation or session tracking - - tslib : Build with tslib support for touchscreen devices + + udev : Enable virtual/udev integration (device discovery, power and storage device support, etc) - - unwind : Enable libunwind usage for backtraces - - wayland : Enable dev-libs/wayland backend - - xephyr : Build the Xephyr server - - xnest : Build the Xnest server + + xorg : Build the Xorg X server (HIGHLY RECOMMENDED) - - xvfb : Build the Xvfb server rj@funtoo ~ $ equery u xf86-video-ati [ Legend : U - final flag setting for installation] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for x11-drivers/xf86-video-ati-7.7.0: U I + + glamor : Enable Glamor OpenGL 2D acceleration + + udev : Enable virtual/udev integration (device discovery, power and storage device support, etc) rj@funtoo ~ $ equery u mesa [ Legend : U - final flag setting for installation] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for media-libs/mesa-11.2.2: U I - - bindist : Disable patent-encumbered ARB_texture_float, EXT_texture_shared_exponent, and EXT_packed_float extensions. + + classic : Build drivers based on the classic architecture. - - d3d9 : Enable Direct 3D9 API through Nine state tracker. Can be used together with patched wine. - - debug : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see https://wiki.gentoo.org/wiki/Project :Quality_Assurance/Backtraces + + dri3 : Enable DRI3 support. + + egl : Enable EGL support. + + gallium : Build drivers based on Gallium3D, the new architecture for 3D graphics drivers. + + gbm : Enable the Graphics Buffer Manager for EGL on KMS. - - gles1 : Enable GLESv1 support. - - gles2 : Enable GLESv2 support. + + llvm : Enable LLVM backend for Gallium3D. + + nptl : Enable support for Native POSIX Threads Library, the new threading module (requires linux-2.6 or better usually) - - opencl : Enable the Clover Gallium OpenCL state tracker. - - openmax : Enable OpenMAX video decode/encode acceleration for Gallium3D. - - osmesa : Build the Mesa library for off-screen rendering. - - pax_kernel : Enable if the user plans to run the package under a pax enabled hardened kernel - - pic : disable optimized assembly code that is not PIC friendly + + udev : Enable virtual/udev integration (device discovery, power and storage device support, etc) - - vaapi : Enable Video Acceleration API for hardware decoding + + vdpau : Enable the VDPAU acceleration interface for the Gallium3D Video Layer. - - video_cards_i915 : VIDEO_CARDS setting to build driver for Intel i915 video cards - - video_cards_i965 : VIDEO_CARDS setting to build driver for Intel i965 video cards - - video_cards_ilo : VIDEO_CARDS setting to build unofficial gallium driver for Intel gen6/7 video cards - - video_cards_intel : VIDEO_CARDS setting to build driver for Intel video cards + + video_cards_nouveau : VIDEO_CARDS setting to build reverse-engineered driver for nvidia cards - - video_cards_r100 : VIDEO_CARDS setting to build only r100 based chips code for radeon - - video_cards_r200 : VIDEO_CARDS setting to build only r200 based chips code for radeon - - video_cards_r300 : VIDEO_CARDS setting to build only r300, r400 and r500 based chips code for radeon + + video_cards_r600 : VIDEO_CARDS setting to build only r600, r700, Evergreen and Northern Islands based chips code for radeon + + video_cards_radeon : VIDEO_CARDS setting to build driver for ATI radeon video cards - - video_cards_radeonsi : VIDEO_CARDS setting to build only Southern Islands based chips code for radeon - - video_cards_vmware : VIDEO_CARDS setting to build driver for vmware video cards - - wayland : Enable support for dev-libs/wayland + + xa : Enable the XA (X Acceleration) API for Gallium3D. + + xvmc : Enable the XvMC acceleration interface for the Gallium3D Video Layer. Reference:http://www.funtoo.org/Package:Radeon_Video_Drivers
https://wiki.gentoo.org/wiki/Radeon#Driver
https://www.x.org/wiki/RadeonFeature/

This is really weird, try to see if udev report any error, run as root 'udevadm monitor' and plug the device, and watch the contents of /proc/net/dev and /proc/net/wireless, I don't think the problem is the kernel, but can try using sys-kernel/gentoo-sources, and use iwconfig from wireless-tools, and ip from iproute2, instead of ifconfig, there might be a bug that's causing this, in which case I can only help you find out what is causing it, it's up to you to report it to the proper people.

At least we know now the kernel is detecting it, What's the output of 'rfkill list' is phy0 blocked?
 
PD: If you ever need to troubleshoot a wireless adapter again, go from bottom to top in this thread, we did it all backwards haha, sorry for that. I really thought from the beginning you didn't even had your driver compiled.

This is starting to sound like a firmware problem, you should have then the module rt3573 in /lib/modules/${kernel_version}/, search with `find` in that directory for "rt3573*" just  to confirm the *.ko file exist, if is there try to load it, if still nothing, this might be a firmware problem, do you have sys-kernel/linux-firmware installed in your system? I had a problem with firmware not being available to load for a Linksys card too some time ago(I just recalled this, though that was in debian).

What kernel version are you using? 
You should also search the specific firmware you need and check it is in /lib/firmware, and boot the kernel to test.
 
I found that blog, when I googled a bit about your device, but it's from 2012, and things have changed since, don't try it, you won't  even find the file it's said to edit, anyway a couple of "grep -rin" inside drivers/net/wireless/rt2x00/, in the kernel sources, got me to:
drivers/net/wireless/rt2x00/rt2800usb.c, see line 1216, your device its already there.
 
 
 
As previously said I'm running a 3.15.* gentoo-sources kernel.
Since its a usb device, try when running funtoo(not in chroot), run dmesg without the device, imediatly plug it in, run dmesg again, and see what happened, or post it here.
EDIT: I enabled the options you need in my kernel config, basically RT2x00, RT2800USB, RT2800USB_RT3573, and build a tarball, then looking at the drivers built here is a list of the relevant files, created:
kernel/drivers/net/wireless/rt2x00/rt2x00lib.ko
kernel/drivers/net/wireless/rt2x00/rt2x00usb.ko
kernel/drivers/net/wireless/rt2x00/rt2800usb.ko
kernel/drivers/net/wireless/rt2x00/rt2800lib.ko
 
So what you need to load is rt2800usb, not rt3573 nor rt3573sta as we were thinking.

Google says that the USB controller on your MB is a VIA VL805 chip.  The advice to get that chip working appears to be to add the kernel parameter "iommu=soft".
 
 
 

It would seem your issue is kernel related, you may want to try a different kernel.
Although, the Debian kernel is built to be "one size fits all", but then again, so is the systemrescuecd standard kernel and yet, you had to use the alternate.
The usb drivers are part of the kernel, either built-in or modules.

You don't need to boot other OS in order to get a new driver, you should already have the kernel source code on your system, first find out which driver supports your device(google might help you with that) and the name of the kernel configuration variable that enables it, should be something like 'CONFIG_YOURMODULE', then verify its compiled and supported for the specific kernel version you are using, if your hardware is new you might need the latests version you can get.
modprobe 'module_name'
If  you don't have it,  you can compile it you just need to enable it in your kernel .config, rebuild and reinstall, no need to reboot if you build it as a module and not inside the kernel image.
If you need further help post the hardware model and version, and your kernel configuration.

Hello benzolius!
 
As j-g- mentioned, you don't have to boot into another system, unless that's the only way to download the driver because of your wireless connection.
 
My question would be, what wireless card do you have. If the wireless card is so new that it's not in the kernel (as happened with my new laptop recently), you'll have to do some research to find and compile the module yourself.
 
could you post the output of :
sudo lspci

Previous responses contain good information about identifying the correct driver.  But the comment that he has only the loopback interface suggests that he needs to run Kubuntu to have the network connection he needs to get the driver.
 
Yes, when you chroot your network connection will remain active.
 
On your chroot command, try using the full path to your chroot executable, possibly '/bin/chroot'.

If you haven't found out yet you need, to enable 'CONFIG_RT2800PCI_RT35XX' to build it, see [1], the easiest way is to run 'make menuconfig' on your kernel source directory, and use '/' and search for 'RT2800PCI_RT35XX', or go:


I'm running a 3.15.3 gentoo-sources kernel, and when I searched with menuconfig, this particular config was marked as 'EXPERIMENTAL', so it seems like recently added, make sure it is actually supported if you're planning to run an older kernel.
 
[1] http://cateee.net/lkddb/web-lkddb/RT2800USB.html

I didn't compile the default funtoo kernel, but I bet it has CONFIG_IKCONFIG enabled, so look for /proc/config.gz and copy it anywhere, as a backup of your current kernel, if you are going to use the same version you can try building a new configuration to use with genkernel, if you already have the source under /usr/src/linux, you might do something as follows:
# zcat /proc/config.gz > /usr/src/linux/.config # cd /usr/src/linux # make menuconfig Using '/' you can get a search dialog, and you can search for 'RT2800PCI_RT35XX'.
You'll get something like this:
 Symbol: RT2800PCI_RT35XX [=y]                                                                                                                              Type  : boolean                                                                                                                                            Prompt: rt2800pci - Include support for rt35xx devices (EXPERIMENTAL)                                                                                        Location:                                                                                                                                                    -> Device Drivers                                                                                                                                            -> Network device support (NETDEVICES [=y])                                                                                                                  -> Wireless LAN (WLAN [=y])                                                                                                                                  -> Ralink driver support (RT2X00 [=m])                                                                                                           (1)         -> Ralink rt27xx/rt28xx/rt30xx (PCI/PCIe/PCMCIA) support (RT2800PCI [=m])                                                                        Defined at drivers/net/wireless/rt2x00/Kconfig:87                                                                                                          Depends on: NETDEVICES [=y] && WLAN [=y] && RT2X00 [=m] && RT2800PCI [=m]                                                                               you can hit '1' (or if you got more options the number you want) and it will take right to the config section, if you have the Dependencies already enabled, Notice:
Depends on: NETDEVICES [=y] && WLAN [=y] && RT2X00 [=m] && RT2800PCI [=m] I Had to enable first those, to be able to see 'CONFIG_RT2800PCI_RT35XX', in my case(I build a only-what-i-need kernel) so my desktop had wireless completely disabled, I don't think that is your case, but, make sure the dependecies for the module you are building are enabled , in this case the last three if you notice  above are in the location in cascade, so if you navigate through menuconfig when you enable CONFIG_WLAN you get a submenu where CONFIG_RT2X00 is available, as 'Ralink driver support' :
... < > Softmac Prism54 support <M> Ralink driver support ---> < > Realtek rtlwifi family of devices ---- [ ] TI Wireless LAN support ---- ... And in there is what you need, you can also change 'CONFIG_LOCALVERSION' to something you like, so your anything you have now stays untouched(kernel-image and modules), when you finish save your config, you will be asked for a name, defaults to .config. Then recompile I've never used genkernel to build my kernels so I really don't know it but, funtoo wiki says this should do the work:
# genkernel --kernel-config=$YOUR_CONFIG_NAME all I hope this helps you, and give it a read at 'make help' in the kernel source directory, all the 'make *config' and building/packaging options are described there, if you are more curious unpack a kernel tarball under any directory you want as an unprivileged user copy your running config file as mentioned above to the as .config, run make menuconfig and start tweaking, you can even build binary tarballs of your  kernel image and modules with 'make tarxz-pkg' as an example before installing anything for real in your system.