LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
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 01-23-2005, 12:12 PM   #16
xmeson
Member
 
Registered: Jul 2003
Location: Random
Distribution: Slackware
Posts: 63

Original Poster
Rep: Reputation: 15
there is /var/


_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/lagezi:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X Window System Version 6.8.1
Release Date: 17 September 2004
X Protocol Version 11, Revision 0, Release 6.8.1
Build Operating System: Linux 2.4.27 i686 [ELF]
Current Operating System: Linux lagezi 2.4.26 #6 Mon Jun 14 19:07:27 PDT 2004 i686
Build Date: 18 October 2004
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Jan 23 18:59:09 2005
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Server Layout"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "ATI Graphics Adapter"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
(WW) `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/local/".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/local/").
(WW) `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/Speedo/".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/Speedo/").
(**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(WW) Open APM failed (/dev/apm_bios) (No such device)
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.2
X.Org Video Driver: 0.7
X.Org XInput driver : 0.4
X.Org Server Extension : 0.2
X.Org Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(--) using VT number 7

(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x8000002c, mode1Res1 = 0x80000000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,2570 card 8086,2570 rev 02 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,2571 card 0000,0000 rev 02 class 06,04,00 hdr 01
(II) PCI: 00:1d:0: chip 8086,24d2 card 1462,0480 rev 02 class 0c,03,00 hdr 80
(II) PCI: 00:1d:1: chip 8086,24d4 card 1462,0480 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:2: chip 8086,24d7 card 1462,0480 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:3: chip 8086,24de card 1462,0480 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:7: chip 8086,24dd card 1462,0480 rev 02 class 0c,03,20 hdr 00
(II) PCI: 00:1e:0: chip 8086,244e card 0000,0000 rev c2 class 06,04,00 hdr 01
(II) PCI: 00:1f:0: chip 8086,24d0 card 0000,0000 rev 02 class 06,01,00 hdr 80
(II) PCI: 00:1f:1: chip 8086,24db card 1462,0480 rev 02 class 01,01,8a hdr 00
(II) PCI: 00:1f:3: chip 8086,24d3 card 1462,0480 rev 02 class 0c,05,00 hdr 00
(II) PCI: 00:1f:5: chip 8086,24d5 card 1462,0480 rev 02 class 04,01,00 hdr 00
(II) PCI: 01:00:0: chip 1002,4e4a card 1787,9560 rev 00 class 03,00,00 hdr 80
(II) PCI: 01:00:1: chip 1002,4e6a card 1787,9561 rev 00 class 03,80,00 hdr 00
(II) PCI: 02:09:0: chip 1106,3106 card 1462,048c rev 8b class 02,00,00 hdr 00
(II) PCI: 02:0a:0: chip 1106,3044 card 1462,048d rev 80 class 0c,00,10 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set)
(II) Bus 1 I/O range:
[0] -1 0 0x0000a000 - 0x0000a0ff (0x100) IX[B]
[1] -1 0 0x0000a400 - 0x0000a4ff (0x100) IX[B]
[2] -1 0 0x0000a800 - 0x0000a8ff (0x100) IX[B]
[3] -1 0 0x0000ac00 - 0x0000acff (0x100) IX[B]
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0xf8000000 - 0xf9ffffff (0x2000000) MX[B]
(II) Bus 1 prefetchable memory range:
[0] -1 0 0xe8000000 - 0xf7ffffff (0x10000000) MX[B]
____________

__________

____________
(II) fglrx(0): UMM area: 0xe8501000 (size=0x07aff000)
(II) fglrx(0): driver needs XFree86 version: 4.3.x
(WW) fglrx(0): could not detect XFree86 version (query_status=-3)
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmOpenByBusid: drmOpenMinor returns 5
drmOpenByBusid: drmGetBusid reports
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card2
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card3
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card4
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card5
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card6
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card7
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card8
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card9
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card10
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card11
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card12
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card13
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card14
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmGetBusid returned ''
(II) fglrx(0): [drm] loaded kernel module for "fglrx" driver
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:0:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0xe0bbd000
(II) fglrx(0): [drm] mapped SAREA 0xe0bbd000 to 0x40022000
(II) fglrx(0): [drm] framebuffer handle = 0xe8000000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): DRIScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.8.25
(II) fglrx(0): Date: Jan 14 2005
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0): Build-Kernel UTS_RELEASE: 2.4.26
(II) fglrx(0): Build-Kernel MODVERSIONS: no
(II) fglrx(0): Build-Kernel __SMP__: no
(II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
(II) fglrx(0): [drm] register handle = 0xf9000000
(II) fglrx(0): [agp] Mode=0x1f004a1b bridge: 0x8086/0x2570
(II) fglrx(0): [agp] AGP v1/2 disable mask 0x00000000
(II) fglrx(0): [agp] AGP v3 disable mask 0x00000000
(II) fglrx(0): [agp] enabling AGP with mode=0x1f004b1a
(II) fglrx(0): [agp] AGP protocoll is enabled for grafics board. (cmd=0x1f004312)
(II) fglrx(0): [agp] grafics chipset has AGP v3.0 (native mode)
(II) fglrx(0): [drm] ringbuffer size = 0x00100000 bytes
(II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 28672
(II) fglrx(0): [drm] texture shared area handle = 0xe8cd3000
(II) fglrx(0): shared FSAAScale=1
(II) fglrx(0): DRI initialization successfull!
(II) fglrx(0): FBADPhys: 0xe8000000 FBMappedSize: 0x00501000
(II) fglrx(0): FBMM initialized for area (0,0)-(1024,1281)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1024,768) (front color buffer - assumption)
(==) fglrx(0): Backing store disabled
(==) fglrx(0): Silken mouse enabled
(II) fglrx(0): Using hardware cursor (scanline 768)
(II) fglrx(0): Largest offscreen area available: 1024 x 505
(**) Option "dpms"
(**) fglrx(0): DPMS enabled
(II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Solid Lines
Dashed Lines
Offscreen Pixmaps
Setting up tile and stipple cache:
24 128x128 slots
(II) fglrx(0): Acceleration enabled
(II) fglrx(0): X context handle = 0x00000001
(II) fglrx(0): [DRI] installation complete
(II) fglrx(0): Direct rendering enabled
(II) Loading extension FGLRXEXTENSION
(II) Loading extension ATITVOUT
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(**) Option "Protocol" "IMPS/2"
(**) Mouse1: Device: "/dev/mouse"
(**) Mouse1: Protocol: "IMPS/2"
(**) Option "CorePointer"
(**) Mouse1: Core Pointer
(**) Option "Device" "/dev/mouse"
(==) Mouse1: Emulate3Buttons, Emulate3Timeout: 50
(==) Mouse1: Buttons: 3
(**) Option "CoreKeyboard"
(**) Keyboard1: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard1: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xfree86"
(**) Keyboard1: XkbRules: "xfree86"
(**) Option "XkbModel" "pc105"
(**) Keyboard1: XkbModel: "pc105"
(**) Option "XkbLayout" "se"
(**) Keyboard1: XkbLayout: "se"
(**) Option "CustomKeycodes" "off"
(**) Keyboard1: CustomKeycodes disabled
(II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
(II) Mouse1: ps2EnableDataReporting: succeeded
SetClientVersion: 0 8
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xe0bbd000 at 0x40022000
 
Old 01-23-2005, 12:53 PM   #17
BajaNick
Senior Member
 
Registered: Jul 2003
Location: So. Cal.
Distribution: Slack 11
Posts: 1,737

Rep: Reputation: 46
It looks like what needs loading is, Your mouse section of xorg is exactly as mine is except zaxis mapping but that doesnt matter now.
Have you tried xwmconfig? what happens when you do? What are the errors you get when you do startx? That will tell alot.
 
Old 01-23-2005, 01:13 PM   #18
slackMeUp
Member
 
Registered: Nov 2003
Distribution: Slack-where?
Posts: 654

Rep: Reputation: 30
My god. . .

I just can't stand it. . .

Swaret does not screw up your system, YOU DO!

Swaret is a tool, LEARN how to use your tools before using them.

I have been using swaret to keep up to date for almost as long as I have been using Slackware. . .
and I have never had even half the trouble people keep bitching about.

Swaret only does exactly what you would do to upgrade a package by hand. . . uninstalls, installs, and then checks for deps.
The only two differences is that it does the hard work for you, and when you do updates on your own, fucking up your system, there is no program to blame but yourself.
But of course swaret will take the heat because *it* fucked your system. Why not RTFM for once and stop being a blind monkey?

I'm done with this thread. .. I can't be of any help or any use besides bitching out people who blame swaret for their mistake.

Last edited by slackMeUp; 01-23-2005 at 01:15 PM.
 
Old 01-23-2005, 04:06 PM   #19
black hole sun
Member
 
Registered: Jul 2004
Distribution: Slackware Current
Posts: 127

Rep: Reputation: 15
slapt-get is the best slackware package update system, period I LOVE it!, you guys should check it out. It is simpler than swaret and for those of you familier to debian, you'll feel right at home. Pick a fast mirror, then just do two commands to update the system;

slapt-get --update
slapt-get --upgrade

and you're golden!

Last edited by black hole sun; 01-23-2005 at 04:07 PM.
 
Old 01-23-2005, 09:17 PM   #20
sporks
Member
 
Registered: Dec 2004
Location: Indonesia
Distribution: Slackware
Posts: 211

Rep: Reputation: 30
Quote:
Originally posted by slackMeUp
My god. . .

I just can't stand it. . .

Swaret does not screw up your system, YOU DO!

Swaret is a tool, LEARN how to use your tools before using them.

I have been using swaret to keep up to date for almost as long as I have been using Slackware. . .
and I have never had even half the trouble people keep bitching about.

Swaret only does exactly what you would do to upgrade a package by hand. . . uninstalls, installs, and then checks for deps.
The only two differences is that it does the hard work for you, and when you do updates on your own, fucking up your system, there is no program to blame but yourself.
But of course swaret will take the heat because *it* fucked your system. Why not RTFM for once and stop being a blind monkey?

I'm done with this thread. .. I can't be of any help or any use besides bitching out people who blame swaret for their mistake.
Well said!
 
Old 01-24-2005, 10:34 AM   #21
cythrawll
Member
 
Registered: Nov 2004
Location: IL, USA
Distribution: Slackware 10
Posts: 167

Rep: Reputation: 31
I have done alot with swaret, and yes it can screw up your system, if you don't know what you are doing, and you don't know what you are installing! And if you don't upgrade the configs!!

swaret broke my system, and other systems i work on many many times. but it has ALWAYS been a matter of reconfiguring and tweaking. and I ALWAYS fixed everything

**edit** could xmeson fix his xorg log so we dont' have to scroll horizontally to read?

Last edited by cythrawll; 01-24-2005 at 10:36 AM.
 
Old 01-24-2005, 11:44 AM   #22
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 53
swaret is like a mean dog, you've got to watch it.
if you get lazy on that......it'll ruin your system.

beware.....

egag
 
Old 01-24-2005, 03:31 PM   #23
shilo
Senior Member
 
Registered: Nov 2002
Location: Stockton, CA
Distribution: Slackware 11 - kernel 2.6.19.1 - Dropline Gnome 2.16.2
Posts: 1,132

Rep: Reputation: 50
what is the output of:

Code:
find /etc -name "*.new"
It's been mentioned before, but that will look for updated config files.
 
Old 02-03-2005, 02:45 PM   #24
dmadcat
Member
 
Registered: Aug 2003
Location: Columbus, OH
Distribution: Slackware
Posts: 32

Rep: Reputation: 15
Or even simpler (as long as you run updatedb regularly) you can just type slocate *.new. Nothing really hard about it.

I've had zero issues with Swaret updating my system. I doubt the issue at hand is a swaret issue anyway which puts all of this way off-topic.

For the problem at hand, I too am experiencing the same issue (no mouse with 2.6.9+) although it works fine with 2.4.26 to .28

The odd thing is, I've used the 2.6 (.5 and .7) kernel before and had no trouble with the mouse. Also, for you swaret bashers, there are no .new configs that would affect mouse functionality and if there were it would likely affect 2.4 also.

I've left the problem alone for awhile but I suppose I'll have to jump back in and attempt to figure it out. If I do I'll post the solution here.
 
Old 02-03-2005, 03:18 PM   #25
DaWallace
Member
 
Registered: Feb 2004
Location: Southern Maine, United States
Distribution: Slackware Ubuntu Debian FreeBSD
Posts: 418

Rep: Reputation: 31
I use it for reupgrading my system after BACKING UP /etc, I never have a problem. I've done it a few times..
I also use it for installing individual apps conveniently

the real trouble is with people who use it to blindly upgrade EVERYTHING from a default installation without even looking over the changelog..

however.. there is always a chance that it'll work perfectly.. if not.. look through the changelog and see what might have gone wrong.. if you know what you're doing you'll see what most-likely screwed up your system and check it out

Last edited by DaWallace; 02-03-2005 at 03:22 PM.
 
Old 02-03-2005, 03:39 PM   #26
shilo
Senior Member
 
Registered: Nov 2002
Location: Stockton, CA
Distribution: Slackware 11 - kernel 2.6.19.1 - Dropline Gnome 2.16.2
Posts: 1,132

Rep: Reputation: 50
Quote:
Or even simpler (as long as you run updatedb regularly) you can just type slocate *.new.
Yeah, that's what I used to do. The problems with that are two-fold.

a) if you just ran SWareT, there is no way that the *.new files have been added to the slocate database. This means that you need to run updatedb immediatley after SWareT. That takes time. I always recommend running updatedb before starting SWareT, since I have SWareT configured to use slocate to find dependencies. That's alot of disk activity running updatedb twice to run SWareT. Using find is WAY quicker. I also used to think that the find command was not as "simple" to use. Now that I use it, I am much more familiar with the "find" command, which is very useful in and of itself.

b) using "slocate "*.new" gives false positives, as there are files outside of the /etc directory that come with the .new extension. To overcome that, it is possible to use a command like:
Code:
slocate "*.new"|grep etc
But that really doesn't seem any more simple.
 
Old 02-03-2005, 10:13 PM   #27
dmadcat
Member
 
Registered: Aug 2003
Location: Columbus, OH
Distribution: Slackware
Posts: 32

Rep: Reputation: 15
Either one works.

For the record, I've used swaret to keep my system up to date with any changes to 10.0 for a year now and the number of .new files that turn up in a search is (even using slocate with all the false positives) doesn't fill even half of a console screen. Also, I haven't touched any of them even so much as to see what changes are present in the new configs and my system runs flawlessly.

For the original mouse problem (assuming he hasn't already discovered this or given up) the solution is to add

Code:
append = "psmouse.proto=imps"
to the 2.6.x section of your lilo.conf.
 
Old 02-05-2005, 06:11 PM   #28
darkRoom
Member
 
Registered: Mar 2004
Location: Valencia, espaņa
Distribution: Slack, Gentoo, Custom
Posts: 162

Rep: Reputation: 30
An interesting thread, i got a few points to make,

Firstly what was this guy on about
Quote:
I've installed SUSE LINUX 9.2 recently , everything is working fine....But 'm not able to find a way to get into GNOME 2.6 desktop enviornment.. Everytime after giving my credentials i log into my sys and by default it launches KDE 3.3 ..
Infact the GNOME option is also not available in the drop down menu on the Login screen.
I wouls be glad if somebody can help me out with my problem !!
And secondly i just installed slack afresh this morning and feeling in a flippant and stupid mood i decided to use swarat
to blindly update everything to current (also this was in the name of research).

Anyway the results of this very scientific and controlled research is that my new install is very broken, perhaps irretrievably so

The x-server refuses to start and apparently it seems as if every section of xorg.conf is bad.

Oh dear.
 
Old 02-05-2005, 06:47 PM   #29
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 53
first...:dunno, lost on this site....
second, swaret cannot read the changelog and you can.
some new packages you just don't need, and it's said so in the changelog.

best for keeping up to date is just download the packages you need once a week ( month )
to a directoty and use either pkgtool or "upgradepkg "
and read the changelog before you download.

and for your current setup....hard to say where the errors are.
maybe reinstall ......

egag
 
Old 02-05-2005, 07:08 PM   #30
darkRoom
Member
 
Registered: Mar 2004
Location: Valencia, espaņa
Distribution: Slack, Gentoo, Custom
Posts: 162

Rep: Reputation: 30
Ok thanks for stating the obvious egag, i was only messing around
 
  


Reply



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
:tisk: For Newbies and roF elpoeP ohW etaH swodniW matthewm Linux - General 1 11-15-2005 12:08 PM
To Swaret or not to Swaret...? QzarBaron Slackware 8 01-31-2005 06:07 AM
Deleting Swaret files in /var/swaret?? Garibaldi3489 Slackware 2 12-30-2004 04:10 PM
Swaret ?? BajaNick Slackware 10 06-13-2004 12:46 AM
Need a little swaret help tigerflag Slackware 4 03-22-2004 09:45 PM

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

All times are GMT -5. The time now is 03:51 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