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.
Thanks, Eric, for the quick reply.
When I went multilib I used the -9alien compat32-tools to convert packages from my 12.2 DVD. I just wondered whether these would still be OK.
It would be better to use the "11alien" package and re-create those "-compat32" packages (or download them again from my website if you do not have a local 32-bit Slackware package tree).
I've made some changes to the "convertpkg-compat32" script - which does the actual conversion - and the resulting packages are cleaner.
It's not required though, as long as you re-installed Slackware's original hal/dbus/mysql packages and upgraded to the latest version of my compat32-tools package.
Eric
Click here to see the post LQ members have rated as the most helpful post in this thread.
It's not required though, as long as you re-installed Slackware's original hal/dbus/mysql packages and upgraded to the latest version of my compat32-tools package.
Eric
Yes, I've done that.
Quote:
Originally Posted by Alien Bob
It would be better to use the "11alien" package and re-create those "-compat32" packages (or download them again from my website if you do not have a local 32-bit Slackware package tree).
I've made some changes to the "convertpkg-compat32" script - which does the actual conversion - and the resulting packages are cleaner.
Right, I'll do that if any problems crop up.
Thanks again.
I've been working with problems of my own with 'KDE 4.2' an stumbled on this thread to solve issues with a laptop.
For users that need to use their touchpad with 'synaptics' vertical scroll and double-tap you can look at 'synaptics touchpad settings in xorg.conf not persisting upon reboot' thread. Hope this aids you in setting things up properly. One thing, you don't have to unload/reload the mouse driver. Just exit your 'X' session then restart a session.
Quote:
Originally Posted by vinegaroon
In Slackware 13.0 this type of configuration has changed.
You most likely do not need any xorg.conf file.
Input stuff is now handled by hal, to edit these settings first copy over /usr/share/hal/fdi/policy/10osvendor/11-x11-synaptics.fdi to /etc/hal/fdi/policy
Then take a look at that file, it's fairly obvious if you follow the examples.
Don't make the same mistake as the OP with mistaking the <!-- and --> text comment tags (Red in sample);
Code:
sample '/etc/hal/fdi/policy';
<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.touchpad">
<merge key="input.x11_driver" type="string">synaptics</merge>
<!-- Arbitrary options can be passed to the driver using
the input.x11_options property since xorg-server-1.5. -->
<!-- EXAMPLES:
Switch on shared memory, enables the driver to be configured at runtime
<merge key="input.x11_options.SHMConfig" type="string">true</merge>
Maximum movement of the finger for detecting a tap
<merge key="input.x11_options.MaxTapMove" type="string">2000</merge>
Enable vertical scrolling when dragging along the right edge
<merge key="input.x11_options.VertEdgeScroll" type="string">true</merge>
Enable vertical scrolling when dragging with two fingers anywhere on the touchpad
<merge key="input.x11_options.VertEdgeScroll" type="string">true</merge>
Enable horizontal scrolling when dragging with two fingers anywhere on the touchpad
<merge key="input.x11_options.HorizTwoFingerScroll" type="string">true</merge>
Enable left click
<merge key="input.x11_options.TapButton1" type="string">1</merge>
If on, circular scrolling is used
<merge key="input.x11_options.CircularScrolling" type="string">true</merge>
For other possible options, check CONFIGURATION DETAILS in synaptics man page
-->
<merge key="input.x11_options.SHMConfig" type="string">true</merge>
<merge key="input.x11_options.TapButton1" type="string">1</merge>
<merge key="input.x11_options.VertEdgeScroll" type="string">true</merge> <merge key="input.x11_options.HorizEdgeScroll" type="string">true</merge>
</match>
</device>
</deviceinfo>
Quote:
excerpt 'man synaptics';
NOTES
There is an example hal policy file in ${sourcecode}/fdi/11-x11-synap-
tics.fdi which will enable the driver based on the information if the
hardware is available. Feel free to copy it to /etc/hal/fdi/policy and
customize it to your needs. You can pass custom options to the driver
using x11_options properties. Note that this requires xorg-server-1.5
or higher.
Look at the 'man synaptics' for detailed information.
Last edited by onebuck; 10-03-2009 at 02:26 PM.
Reason: corrections
I really haven't looked lately. The 'SlackwareŽ Essentials' book was due out mid 2009 but then pushed back to late 2009. The installation is basically the same. Take a look at the above link then if you have any problems you can always post back here or create a new thread within the Slackware forums.
The next 'SlackwareŽ Essentials' should be out soon. If your interested in listening to Alan Hicks interview.
I need to 'Thank' cwizardone for his post, which got the old thoughts back out front for this issue of trailing the need to document some of the things that just don't appear or jump out at you. That is unless you happen to read a lot here on the Slackware LQ forum or just a doc addict.
I know that to spend time to weed through to find the jewel which will afford that special repair can become frustrating.
pwc101 and I have been working on this new wiki for a short while. As a wiki goes there's always room to improve and with this one we are still shaking things out. So please be patient as we work out some of the kinks.
I created another wiki page 'Slackware-Cellar' to avail the sharing of Slackware Test Beds/Benches/Experimental System Setups.
I'm sure someone is bound to say; 'What's the damn purpose?'.
As I said above it's a place to share your custom setups. I'm hoping that both will come to the aid of the Slackware community.
I want too introduce a new member and the recent post by Josh; 'Slackware 13 - The Odyssey'. The writer is a newbie to Slackware Linux and wishes to share his experiences by writing a good thread about his introduction.
I wish to encourage Josh (aka jpcrow) to continue with the excellent writing style and the sharing of his experiences. To other members, if you haven't read the Thread then I suggest that you look it over.
If you happen to have a 'ATI' graphics then you may find 'Radeon kms works!' a good reference and a possible solution to your problems with older cards.
You should be aware that not all users will be able to get those older 'ATI' units functional by using 'kms' but it's worth a try.
I'm still working on a laptop with issues. I have too get back on this just to get it off my mind.
The weather here has allowed or should I say availed me time away from my farm duties so I should get things resolved. Soon, I hope!
Heads up for Slackware 13 'ATI Xpress 200M' users.
Hi,
I'm getting closer to getting this little laptop functional. I work with 'X' but not a 'X'pert. The work on 2.6.32-rc5,vmlinuz-2.6.32-rc7 kernels to work with 'KMS' to attempt to get the 'libdrm', 'mesa' and 'xf86-video-ati' to work with this 'Dell 1501 (ATI Xpress 200M)'. It's been a nightmare. I do keep detailed notes in the 'system maintenance log' to provide the means to track or back track when necessary. No joy when using 'git'.
I shuffle configuration files when needed and edit to suit. But I failed to revert some items and configure files. There were some stale files left behind and my xorg-server was having problems.
# glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGI_swap_control,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group
client glx vendor string: SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory,
GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control,
GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control,
GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
GLX version: 1.2
GLX extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method,
GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group
OpenGL vendor string: DRI R300 Project
OpenGL renderer string: Mesa DRI R300 20060815 NO-TCL
OpenGL version string: 1.4 Mesa 7.5.1
OpenGL extensions:
GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_fragment_program,
GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture,
GL_ARB_point_parameters, GL_ARB_shadow, GL_ARB_shadow_ambient,
GL_ARB_texture_border_clamp, GL_ARB_texture_compression,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar,
GL_ARB_texture_env_dot3, GL_MESAX_texture_float,
GL_ARB_texture_mirrored_repeat, GL_ARB_texture_rectangle,
GL_ARB_transpose_matrix, GL_ARB_vertex_buffer_object,
GL_ARB_vertex_program, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra,
GL_EXT_blend_color, GL_EXT_blend_equation_separate,
GL_EXT_blend_func_separate, GL_EXT_blend_logic_op, GL_EXT_blend_minmax,
GL_EXT_blend_subtract, GL_EXT_compiled_vertex_array, GL_EXT_convolution,
GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_fog_coord,
GL_EXT_gpu_program_parameters, GL_EXT_histogram, GL_EXT_multi_draw_arrays,
GL_EXT_packed_pixels, GL_EXT_point_parameters, GL_EXT_polygon_offset,
GL_EXT_rescale_normal, GL_EXT_secondary_color,
GL_EXT_separate_specular_color, GL_EXT_shadow_funcs,
GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_subtexture,
GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp,
GL_EXT_texture_env_add, GL_EXT_texture_env_combine,
GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic,
GL_EXT_texture_lod_bias, GL_EXT_texture_mirror_clamp,
GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array,
GL_APPLE_packed_pixels, GL_ATI_blend_equation_separate,
GL_ATI_texture_env_combine3, GL_ATI_texture_mirror_once,
GL_ATI_separate_stencil, GL_IBM_multimode_draw_arrays,
GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat,
GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_ycbcr_texture,
GL_MESA_window_pos, GL_NV_blend_square, GL_NV_light_max_exponent,
GL_NV_texture_rectangle, GL_NV_texgen_reflection, GL_NV_vertex_program,
GL_OES_read_format, GL_SGI_color_matrix, GL_SGI_color_table,
GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp,
GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SUN_multi_draw_arrays
8 GLX Visuals
visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
0x21 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x22 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x61 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x62 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x63 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x64 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x65 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x58 32 tc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 Ncon
8 GLXFBConfigs:
visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
0x59 0 tc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x5a 0 tc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x5b 0 tc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x5c 0 tc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x5d 0 dc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x5e 0 dc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x5f 0 dc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x60 0 dc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
# glxinfo |grep -i r300
OpenGL vendor string: DRI R300 Project
OpenGL renderer string: Mesa DRI R300 20060815 NO-TCL
By the above it shows that 'Mesa DRI R300' is used but I thought the 'ATI Xpress 200M' uses the R400. I'm still investigating the driver issues since the problem is intermittent. Whenever it occurs on exit of 'X' the screen is rasterized, vertical scan lines along with dots. I have to do a TFS or blind re-boot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.