-   Linux - Software (
-   -   Transport Problems (

mparsons0164 11-11-2001 11:15 AM

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?

taz.devil 11-11-2001 02:59 PM

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! :)

All times are GMT -5. The time now is 04:16 PM.