SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I think the black console is probably caused by some who don't use the correct frame buffer driver, either that the frame buffer console is missing or they load a frame buffer driver for their card, while being in KMS.
As for ATI frimware for R600 and above, they can be downloaded from here :
Only the R600_rlc.bin and R700_rlc.bin are needed.
I didn't have much luck loading them at boot so I ended up compiling them into the kernel. :-|
Probably not something Slackware can afford. If you succeed making it load at boot, I'm interested.
Appart from that, for ATI cards, KMS works perfectly. I understood that it's better now for these cards to use KMS instead of UMS.
Last edited by rvdboom; 09-02-2010 at 09:23 AM.
Click here to see the post LQ members have rated as the most helpful post in this thread.
I'll have a deeper look on how to force console output on one of the two (fb1 looks ok)
obviously I have not found (it can be it exists, though) any specific documentation, but I discovered the fbcon=map:x option that is used by the fbcon kernel module to map the framebuffer console on a specific framebuffer device, so I tried it with nouveaufb (I said myself, it can't be much different ) passing to the kernel at boot
Code:
nouveaufb=map:1
dmesg lists this two new lines
Code:
fbcon: nouveaufb (fb1) is primary device
fbcon: Remapping primary device, fb1, to tty 1-63
and this way the nouveau console framebuffer works fine on my hardware
FYI, I added also
Code:
/sbin/modprobe fbcon
/sbin/modprobe nouveau
to /etc/rc.d/rc.modules (haven't tried yet if superfluous) and created an /etc/X11/xorg.conf (needed for me) with "X -configure" (it gives an error, probably still because of my configuration but it creates xorg.conf.new the same)
maybe other people with multi-head/multi-gpu configurations will probably need to pass the map option to the kernel for having a working console with the present nouveau kernel driver.
Last edited by ponce; 09-02-2010 at 11:31 AM.
Reason: added needed (for me) sample xorg.conf
I think the black console is probably caused by some who don't use the correct frame buffer driver, either that the frame buffer console is missing or they load a frame buffer driver for their card, while being in KMS.
As for ATI frimware for R600 and above, they can be downloaded from here :
Only the R600_rlc.bin and R700_rlc.bin are needed.
For evergreen cards (HD5xxx), the other firmware is needed for KMS. All three files from each set, and the set depends on the specific model unfortunately. I'm fairly certainly they are not needed unless KMS is enabled.
While using your packages, normal *nix behavior of mouse copy and paste disappeared. (when you select with a mouse text, and them press either wheel, or middle button or left and right button to paste). Any ideas why it happened and how can I get it back? I used to it so much, and I really miss it now.
I think the black console is probably caused by some who don't use the correct frame buffer driver, either that the frame buffer console is missing or they load a frame buffer driver for their card, while being in KMS.
As for ATI frimware for R600 and above, they can be downloaded from here :
Only the R600_rlc.bin and R700_rlc.bin are needed.
I didn't have much luck loading them at boot so I ended up compiling them into the kernel. :-|
Probably not something Slackware can afford. If you succeed making it load at boot, I'm interested.
Appart from that, for ATI cards, KMS works perfectly. I understood that it's better now for these cards to use KMS instead of UMS.
The license on those files looks acceptable for redistribution, so I'll look into packaging them up. Can you paste the kernel log buffer from when the firmware loader looks for those files? (I need to know where the kernel expects to find the firmware files -- toplevel /lib/firmware/ or in a subdirectory, e.g. /lib/firmware/radeon/)
I forgot (maybe not that important but just to report any issue with nouveau): I'm using Xrender for kde 4.5.0 desktop effects, because opengl (the default?) doesn't work.
and with Xrender there are nice (lols) deformation effects while resizing windows (probably because of how compositing is handled).
The license on those files looks acceptable for redistribution, so I'll look into packaging them up. Can you paste the kernel log buffer from when the firmware loader looks for those files? (I need to know where the kernel expects to find the firmware files -- toplevel /lib/firmware/ or in a subdirectory, e.g. /lib/firmware/radeon/)
I'm sorry, I'm totally inept and I've not managed to make the kernel load the firmware at boot. It always hanged for a while and then continue but after disabling DRM/DRI.
So I ended up compiling the firmware in the kernel.
It seems to me that it's supposed to look for it in /lib/firmware/radeon but I actually failed to make it load from there, so I may just be wrong.
That means the firmware files for this module should be in a 'zd1211' subdirectory in one of the toplevel firmware search paths; those paths are /lib/firmware and a few other places that escape my memory at the moment, and I don't feel like digging through udev source and build scripts to refresh it right now...
Installed last night and so far everything is working perfectly. I'm using a GTX-460 with the nvidia binary driver. I will try nouveau in a few days when I get time.
I compile my own kernel from vanilla and do not use modules...
However, at some point, I forgot to compile the firmware in and here are the messages that went into syslog :
Yep, now I am testing xinerama under my Intel 82..GM cards on my notebook Fujitsu-Siemens. Before when I tried to run both LCD display of the notebook and a VGA monitor with they native modes - LVDS 1400x1050/60 Hz, VGA 1280x1024/60 Hz, X server was going stuck.
It's annoying me because under slack 12.2 everything goes smoothly. Now I am working under Xfce (new kernel, new Xorg) - seems it's OK. But....We'll see.
Nouveau driver is working with an xorg.conf file on a nvidia GeForce 6150SE with a 2.6.35.4 kernel compiled with x86_64.config file. Startx Without xorg.conf file tries to load nv or vesa driver and get black screen. When xorgsetup is ran the xorg.conf video driver is nv. changed to nouveau and is working so far using xfce desktop.
Nouveau driver is working with an xorg.conf file on a nvidia GeForce 6150SE with a 2.6.35.4 kernel compiled with x86_64.config file. Startx Without xorg.conf file tries to load nv or vesa driver and get black screen. When xorgsetup is ran the xorg.conf video driver is nv. changed to nouveau and is working so far using xfce desktop.
Is nv of any use now that theres nouveau?
Although personally i wouldnt bother installing it, it seems worthless now.
The license on those files looks acceptable for redistribution, so I'll look into packaging them up. Can you paste the kernel log buffer from when the firmware loader looks for those files? (I need to know where the kernel expects to find the firmware files -- toplevel /lib/firmware/ or in a subdirectory, e.g. /lib/firmware/radeon/)
Sorrry my last post was not very useful.
Info about my notebook: Fujitsu-Siemens E Series Lifebook E4010D, 512 MB RAM. Here my $(uname -srmpi) (slackware-current)
Code:
Linux 2.6.35-smp i686 Intel(R) Pentium(R) M processor 1400MHz GenuineIntel
(centrino technology). Here cuts from my Xorg.0.log (important info, warnings and errors)
Code:
[ 943.952] (II) LoadModule: "fbdev"
[ 943.954] (WW) Warning, couldn't open module fbdev
[ 943.954] (II) UnloadModule: "fbdev"
[ 943.954] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 943.967] (WW) Falling back to old probe method for vesa
[ 943.971] (II) intel(0): Integrated Graphics Chipset: Intel(R) 855GM
[ 943.971] (--) intel(0): Chipset: "852GM/855GM"
[ 943.971] (==) intel(0): video overlay key set to 0x101fe
[ 944.082] (II) intel(0): Output VGA1 has no monitor section
[ 944.082] (II) intel(0): Output LVDS1 has no monitor section
[ 944.082] (II) intel(0): found backlight control interface /sys/class/backlight/fujitsu-laptop
[ 944.250] (II) intel(0): EDID for output DVI1
[ 944.250] (II) intel(0): Output VGA1 connected
[ 944.250] (II) intel(0): Output LVDS1 connected
[ 944.250] (II) intel(0): Output DVI1 disconnected
[ 944.250] (II) intel(0): Using exact sizes for initial modes
[ 944.250] (II) intel(0): Output VGA1 using initial mode 1280x1024
[ 944.250] (II) intel(0): Output LVDS1 using initial mode 1280x1024
[ 944.250] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 944.250] (II) intel(0): Kernel page flipping support detected, enabling[ 944.252] (II) intel(0): [DRI2] Setup complete
[ 944.252] (II) intel(0): [DRI2] DRI driver: i915
[ 944.252] (**) intel(0): Tiling enabled
[ 944.252] (**) intel(0): SwapBuffers wait enabled
[ 944.252] (==) intel(0): VideoRam: 131072 KB
[ 945.287] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 945.289] (==) intel(0): DPMS enabled
[ 945.289] (==) intel(0): Intel XvMC decoder disabled[ 946.310] (**) Option "xkb_rules" "evdev"
[ 946.310] (**) Option "xkb_model" "evdev"[ 946.376] (WW) Option "xkb_variant" requires an string value
[ 946.376] (WW) Option "XkbVariant" requires an string value
[ 946.391] (**) 2.4GHz 2way RF Receiver: Device: "/dev/input/mouse2"
[ 946.391] (EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device
[ 946.391] (II) UnloadModule: "evdev"
[ 946.391] (EE) PreInit returned NULL for "2.4GHz 2way RF Receiver"[ 946.404] (**) Option "TapButton3" "3"
[ 946.424] (EE) Query no Synaptics: 6003C8
[ 946.424] (--) AlpsPS/2 ALPS GlidePoint: no supported touchpad found
[ 946.424] (EE) AlpsPS/2 ALPS GlidePoint Unable to query/initialize Synaptics hardware.
[ 946.424] (EE) PreInit failed for input device "AlpsPS/2 ALPS GlidePoint"
[ 946.424] (II) UnloadModule: "synaptics"
The glxinfo
Code:
direct rendering: Yes
I dont't use xorg.conf file. Now I'm working in the xinerama mode under Xfce. KDE not tested. The external monitor is a LCD hp pavilion f1723 panel with VGA connector. Here cuts from xrandr -q
Code:
Screen 0: minimum 320 x 200, current 1400 x 2048, maximum 2048 x 2048
VGA1 connected 1280x1024+0+1024 (normal left inverted right x axis y axis) 340mm x 270mm
1280x1024 60.0*+ 75.0
LVDS1 connected 1400x1050+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1400x1050 60.0*+ 74.8 60.0
The outputs overlap as they do not fit all together into a maximal size of a virtual desktop (1050 + 1024 > 2048). I set a xinerama mode dynamically using xrandr (as there is no my custom config file).
Last edited by igadoter; 09-03-2010 at 03:34 AM.
Reason: added information
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
) passing to the kernel at boot
