Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Software
User Name
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.


  Search this Thread
Old 11-11-2001, 11:15 AM   #1
LQ Newbie
Registered: Nov 2001
Posts: 1

Rep: Reputation: 0
Transport Problems

Using Slackware 8.0, Had a 2.2.19 kernel system. Wiped it out (repartitioned/reformatted/reinstalled clean) and put in Slackware 8 with 2.4.5 base kernel.

Booted up fine with bare.i (2.4.5). Had to recompile kernel. Have a very stripped-down kernel, lots of things modularized.

Trying to configure KDE/X-windows. Used to work perfect with 2.2.19 kernel with same settings. Grey X-window and pointer come up, but won't transfer to KDE. After aborting X-window (ctrl-alt-backsp), note the following messages:

_X11TransSocketOpen: socket() failed for local
_X11TransSocketOpenCOTSClient: Unable to open socket for local
_X11TransOpen: transport open failed for local/darkstar:0

xinit: Address family not supported by protocol (errno 97): unable to connect to X server

Started troubleshooting X-windows/KDE. Checked xinitrc and all that, and all appears good (and X is running anyway).

Then noticed following messages on boot:

Starting syslogk daemons: /usr/sbin/syslogd syslogd: cannot create /dev/log: Address family not suppoted by protocol
/usr/sbin/klogd -c 3

Running gpm:
gpm: oops() invoked from gpm.c(1003)
socket(): Address family not supported by protocol

I'm thinking I've got some sort of transport problem. Could I be missing a module of some sort?
Old 11-11-2001, 02:59 PM   #2
Senior Member
Registered: Nov 2001
Location: Wa. State
Distribution: Slackware
Posts: 1,261

Rep: Reputation: 45
I've gotten a few of those errors and due to trial and error in the kernels config, got things going good. My biggest problem was video, and not getting any. I hadn't built frame buffer (D'oh) support into the rebuilt kernel. The gpm oops i've had a many times due to kernel config and xf86config misconfigs. My 2 peanuts is to rebuild the kernel again and on every single option click ? and read the help file. It takes longer yes, but until I did that and realized it wasn't a pick and choose atmosphere, i would have error after error. There are alot of dependancies. Building as a module isn't necessarily always good either. Some things, will crap out if you do. My idear is that your kernel is goofy somewhere with more than two or three errors. That's just me though, I'm a restart and do-over all or nuthing kinda guy!


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
Email Transport WLReed SUSE / openSUSE 1 10-24-2005 05:58 AM
Postfix transport problems BarrySharpen Linux - Networking 1 12-02-2004 05:36 PM
jabber 1.4.3 and the icq-transport mule Linux - Software 0 06-24-2004 02:15 AM
Using different transport mechanisms hypernetics Linux - Networking 0 12-07-2003 10:04 AM
anyone remember transport tycoon on the PC? flapjackboy General 5 10-26-2003 02:39 AM > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 09:30 AM.

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