LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-02-2010, 09:21 AM   #46
rvdboom
Member
 
Registered: Jul 2007
Distribution: Slackware
Posts: 223

Rep: Reputation: 30

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 :

http://people.freedesktop.org/~agd5f/radeon_ucode/

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.
Old 09-02-2010, 10:46 AM   #47
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 5,597

Rep: Reputation: Disabled
Quote:
Originally Posted by ponce View Post
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)
Code:
Section "ServerLayout"
	Identifier     "X.org Configured"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
	ModulePath   "/usr/lib64/xorg/modules"
	FontPath     "/usr/share/fonts/local"
	FontPath     "/usr/share/fonts/TTF"
	FontPath     "/usr/share/fonts/OTF"
	FontPath     "/usr/share/fonts/Type1"
	FontPath     "/usr/share/fonts/misc"
	FontPath     "/usr/share/fonts/CID"
	FontPath     "/usr/share/fonts/75dpi/:unscaled"
	FontPath     "/usr/share/fonts/100dpi/:unscaled"
	FontPath     "/usr/share/fonts/75dpi"
	FontPath     "/usr/share/fonts/100dpi"
	FontPath     "/usr/share/fonts/cyrillic"
EndSection

Section "Module"
	Load  "glx"
	Load  "dri"
	Load  "record"
	Load  "dri2"
	Load  "extmod"
	Load  "dbe"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "auto"
	Option	    "Device" "/dev/input/mice"
	Option	    "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
	Identifier   "Monitor0"
	VendorName   "Monitor Vendor"
	ModelName    "Monitor Model"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
        ### <percent>: "<f>%"
        ### [arg]: arg optional
        #Option     "SWcursor"           	# [<bool>]
        #Option     "HWcursor"           	# [<bool>]
        #Option     "NoAccel"            	# [<bool>]
        #Option     "ShadowFB"           	# [<bool>]
        #Option     "VideoKey"           	# <i>
	Identifier  "Card0"
	Driver      "nouveau"
	BusID       "PCI:10:0:0"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
	DefaultDepth	24
	SubSection "Display"
		Viewport   0 0
		Depth     1
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     4
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     8
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     15
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     16
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection
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
 
1 members found this post helpful.
Old 09-02-2010, 11:11 AM   #48
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 399Reputation: 399Reputation: 399Reputation: 399
Quote:
Originally Posted by rvdboom View Post
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 :

http://people.freedesktop.org/~agd5f/radeon_ucode/

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.
 
Old 09-02-2010, 11:26 AM   #49
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,479

Original Poster
Rep: Reputation: 1084Reputation: 1084Reputation: 1084Reputation: 1084Reputation: 1084Reputation: 1084Reputation: 1084Reputation: 1084
Quote:
Originally Posted by dolphin77 View Post
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.
Probably you're looking for this:

http://who-t.blogspot.com/2010/06/ne...emulation.html
 
Old 09-02-2010, 11:30 AM   #50
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,479

Original Poster
Rep: Reputation: 1084Reputation: 1084Reputation: 1084Reputation: 1084Reputation: 1084Reputation: 1084Reputation: 1084Reputation: 1084
Quote:
Originally Posted by rvdboom View Post
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 :

http://people.freedesktop.org/~agd5f/radeon_ucode/

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/)
 
Old 09-02-2010, 11:43 AM   #51
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 5,597

Rep: Reputation: Disabled
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).
 
Old 09-02-2010, 01:22 PM   #52
rvdboom
Member
 
Registered: Jul 2007
Distribution: Slackware
Posts: 223

Rep: Reputation: 30
Quote:
Originally Posted by rworkman View Post
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.
 
Old 09-02-2010, 02:01 PM   #53
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,479

Original Poster
Rep: Reputation: 1084Reputation: 1084Reputation: 1084Reputation: 1084Reputation: 1084Reputation: 1084Reputation: 1084Reputation: 1084
If it's the "radeon" module looking for that firmware, show me the output of this:

Code:
$ modinfo radeon | grep firmware
For example, here's what zd1211rw shows:

Code:
$ modinfo zd1211rw | grep firmware
firmware:       zd1211/zd1211_uphr
firmware:       zd1211/zd1211b_uphr
firmware:       zd1211/zd1211_ub
firmware:       zd1211/zd1211b_ub
firmware:       zd1211/zd1211_ur
firmware:       zd1211/zd1211b_ur
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...
 
Old 09-02-2010, 03:36 PM   #54
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-14.2
Posts: 1,620

Rep: Reputation: 424Reputation: 424Reputation: 424Reputation: 424Reputation: 424
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.
 
Old 09-02-2010, 03:47 PM   #55
rvdboom
Member
 
Registered: Jul 2007
Distribution: Slackware
Posts: 223

Rep: Reputation: 30
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 :

Code:
/var/log/syslog.3:Aug  2 19:20:16 coyote kernel: [   60.640235] r600_cp: Failed to load firmware "radeon/R600_rlc.bin"
/var/log/syslog.3:Aug  2 19:20:16 coyote kernel: [   60.640285] [drm:r600_startup] *ERROR* Failed to load firmware!
Also, there's the following line in the kernel source file linux/drivers/gpu/drm/radeon/r600.c :

Code:
r600.c:MODULE_FIRMWARE("radeon/R600_rlc.bin");
So I guess this is the default path, within the default firmware install path, which is /lib/firmware.

Last edited by rvdboom; 09-02-2010 at 03:49 PM.
 
Old 09-02-2010, 07:09 PM   #56
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 1,596
Blog Entries: 1

Rep: Reputation: Disabled
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.
 
Old 09-02-2010, 07:56 PM   #57
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,661

Rep: Reputation: 836Reputation: 836Reputation: 836Reputation: 836Reputation: 836Reputation: 836Reputation: 836
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.
 
Old 09-03-2010, 12:46 AM   #58
sahko
Senior Member
 
Registered: Sep 2008
Distribution: Slackware
Posts: 1,041

Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
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.
 
Old 09-03-2010, 01:20 AM   #59
dolphin77
Member
 
Registered: May 2009
Posts: 202

Rep: Reputation: 58
Quote:
Originally Posted by rworkman View Post
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/)
Code:
root@darkstar:/home/vladimir# modinfo radeon | grep firmware
firmware:       radeon/R520_cp.bin
firmware:       radeon/RS600_cp.bin
firmware:       radeon/RS690_cp.bin
firmware:       radeon/R420_cp.bin
firmware:       radeon/R300_cp.bin
firmware:       radeon/R200_cp.bin
firmware:       radeon/R100_cp.bin
firmware:       radeon/RV710_me.bin
firmware:       radeon/RV710_pfp.bin
firmware:       radeon/RV730_me.bin
firmware:       radeon/RV730_pfp.bin
firmware:       radeon/RV770_me.bin
firmware:       radeon/RV770_pfp.bin
firmware:       radeon/RS780_me.bin
firmware:       radeon/RS780_pfp.bin
firmware:       radeon/RV670_me.bin
firmware:       radeon/RV670_pfp.bin
firmware:       radeon/RV635_me.bin
firmware:       radeon/RV635_pfp.bin
firmware:       radeon/RV620_me.bin
firmware:       radeon/RV620_pfp.bin
firmware:       radeon/RV630_me.bin
firmware:       radeon/RV630_pfp.bin
firmware:       radeon/RV610_me.bin
firmware:       radeon/RV610_pfp.bin
firmware:       radeon/R600_me.bin
firmware:       radeon/R600_pfp.bin
firmware:       radeon/R520_cp.bin
firmware:       radeon/RS600_cp.bin
firmware:       radeon/RS690_cp.bin
firmware:       radeon/R420_cp.bin
firmware:       radeon/R300_cp.bin
firmware:       radeon/R200_cp.bin
firmware:       radeon/R100_cp.bin
firmware:       radeon/CYPRESS_rlc.bin
firmware:       radeon/CYPRESS_me.bin
firmware:       radeon/CYPRESS_pfp.bin
firmware:       radeon/JUNIPER_rlc.bin
firmware:       radeon/JUNIPER_me.bin
firmware:       radeon/JUNIPER_pfp.bin
firmware:       radeon/REDWOOD_rlc.bin
firmware:       radeon/REDWOOD_me.bin
firmware:       radeon/REDWOOD_pfp.bin
firmware:       radeon/CEDAR_rlc.bin
firmware:       radeon/CEDAR_me.bin
firmware:       radeon/CEDAR_pfp.bin
firmware:       radeon/R700_rlc.bin
firmware:       radeon/R600_rlc.bin
firmware:       radeon/RV710_me.bin
firmware:       radeon/RV710_pfp.bin
firmware:       radeon/RV730_me.bin
firmware:       radeon/RV730_pfp.bin
firmware:       radeon/RV770_me.bin
firmware:       radeon/RV770_pfp.bin
firmware:       radeon/RS780_me.bin
firmware:       radeon/RS780_pfp.bin
firmware:       radeon/RV670_me.bin
firmware:       radeon/RV670_pfp.bin
firmware:       radeon/RV635_me.bin
firmware:       radeon/RV635_pfp.bin
firmware:       radeon/RV620_me.bin
firmware:       radeon/RV620_pfp.bin
firmware:       radeon/RV630_me.bin
firmware:       radeon/RV630_pfp.bin
firmware:       radeon/RV610_me.bin
firmware:       radeon/RV610_pfp.bin
firmware:       radeon/R600_me.bin
firmware:       radeon/R600_pfp.bin
it should definitely go to /lib/firmware/radeon/

For those who runs 2.6.35.x on a notebook, powersaving is now working. All you need to do is add additional option dynclks=1
Code:
root@darkstar:/home/vladimir# cat /etc/modprobe.d/radeon.conf 
options radeon modeset=1 dynclks=1
and the line
Code:
echo mid > /sys/class/drm/card0/device/power_profile
for example to rc.local.

After this KDE effects still works, but the machine produces much less heat and doesn't roll the fan most of the time.
 
1 members found this post helpful.
Old 09-03-2010, 03:24 AM   #60
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 1,596
Blog Entries: 1

Rep: Reputation: Disabled
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
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
No updates in Testing? war1025 Debian 2 07-08-2009 12:16 PM
[Call for testing] ibus SlackBuild grissiom Slackware 6 05-19-2009 10:39 AM
Testing is inadequate for new updates Lsatenstein Fedora 3 12-24-2006 11:19 AM
security updates for testing branch uselpa Debian 4 09-15-2006 01:09 AM
Anyone tried 2.6.11 in updates/testing ? snecklifter Fedora 7 04-08-2005 09:13 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:57 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration