LinuxQuestions.org - [SOLVED] Terminal Emulation & /dev/pts and /dev/shm Issues on Kernel 3.4.3

- Gentoo (https://www.linuxquestions.org/questions/gentoo-87/)

- - Terminal Emulation & /dev/pts and /dev/shm Issues on Kernel 3.4.3 (https://www.linuxquestions.org/questions/gentoo-87/terminal-emulation-and-dev-pts-and-dev-shm-issues-on-kernel-3-4-3-a-4175434377/)

Terminal Emulation & /dev/pts and /dev/shm Issues on Kernel 3.4.3

About a week ago I lost the ability to run any terminal emulation in the X windows environment (running openbox). Today I noticed that during boot up I receive a warning that my system was unable to create /dev/pts and /dev/shm. After doing some searching I think these two errors might be related.

The problem is I have no idea where to begin troubleshooting.

-the /dev/pts and /dev/shm directories do exist as empty directories within the system when logged in
-terminal emulator results
terminator:"unable to locate /bin/bash" then crashes X once closed
xterm:will not start
urxvt:will not start
qterminal:displays a blank screen with no input or prompt
-Searching the forms and search engines yield no results, more than likely because I am not searching for the "right" phrase/keywords.

If anyone has some insight into these parts of the Gentoo system or could provide links to anything that would help me diagnose the problem, it would be appreciated.

As always, let me know if you require any further information regarding my system.

Can you get into a virtual terminal ( ctl FX ) ? :scratch:

Did you try reinstalling the terminal emulators ? :scratch:

Quote:

Originally Posted by jv2112 (Post 4816268)

Can you get into a virtual terminal ( ctl FX ) ? :scratch:

Yes, all the virtual terminals work fine.

Quote:

Originally Posted by jv2112 (Post 4816268)

Did you try reinstalling the terminal emulators ? :scratch:

Yes, Terminator was the only terminal I had installed at the time. I tried reinstalling and rolling back one version with no luck. The other emulators I installed after the issue presented itself.

You have mentioned the kernel in the thread name, did you compiled it yourself? If so maybe you missed something in the config?
Have you check the health of your hard drive ? Maybe there are bad sectors resulting corrupted files. Run palimpsest to check if you have it.
The directories you mentioned are empty here in my system as well, my terminal works fine, doesn't looks like it is related, but just a result of something else.

Quote:

Originally Posted by unassailable (Post 4816257)

...
terminator:"unable to locate /bin/bash" then crashes X once closed
..

Maybe a problem with xserver and paths.
Now this will help us to help you, please post dmesg and xorg.0.log also .xsession-errors.

Quote:

Originally Posted by unassailable (Post 4816273)

...Yes, Terminator was the only terminal I had installed at the time. I tried reinstalling and rolling back one version with no luck. ..The other emulators I installed after the issue presented itself.

More than one terminal emulator is having problems, maybe isn't the terminals but something else effecting them.

Regards

Thanks for the suggestions, I am almost sure there is an underlying problem with the system rather than with the terminal emulators. But so far, nothing else seems off.

I am not able to locate an .xsession-errors log. A search of my system turns up nothing. Does this mean X is not crashing?

Looking through these files, I did not see anything that automatically stands out as an error. I need to clean up my configuration of X a little bit (calling on modules that do not exist) but that has not affected anything in the past.

Here are my log dumps:

dmesg on fresh boot, before starting X
http://pastebin.com/jATRg1tt

dmesg after starting and terminator crashing X (stripped to save msg space):
http://pastebin.com/4MqriKQM

Xorg.0.log on fresh boot
http://pastebin.com/ZYHJYbzH

Xorg.0.log after starting and crashing X
http://pastebin.com/hnWZ6T1t

Quote:

Originally Posted by ukiuki (Post 4816281)

Yes I compiled it from scratch. I have never had an issue with it prior to last week and have been using 3.4.3 for quite some time now. I did recently recompile my current config, but I only changed two variables relating to my ext4 security (EXT4_FS_SECURITY=y and EXT3_FS_SECURITY=y). These might have created an issue, but a recent update required that they be set (I forget for which program).

The drives are scanned regularly and I have not seen any isues that came up with those. (I am not familiar with palimpsest, perhaps I will look into it to see if that might help)

The .xsession-errors file is in your user directory.

About the kernel make sure you have the options for consoles enabled under:

Code:

Device Drivers > Character Devices > Virtual Terminal

I did found some things in your logs, take a look:
dmesg

Code:

[    0.000000] No AGP bridge found

[    0.000000] No NUMA configuration found



[    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!



[    0.550103] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored



[    0.974003] ACPI: No dock devices found.



[    0.974077] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug



[    1.085553] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)

[    1.085641] uvesafb: vbe_init() failed with -22

[    1.085715] uvesafb: probe of uvesafb.0 failed with error -22



[    1.158787] [drm] MTRR allocation failed.  Graphics performance may suffer.

[    1.160276] [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed



[    1.883253] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS



[    1.909699] video: probe of LNXVIDEO:00 failed with error -5



[    2.185332] ACPI Warning: 0x000000000000f040-0x000000000000f05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20120320/utaddress-251)

[    2.186200] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver



[  17.566546] rts51x: Bad LUN (0:1)

[  17.566600] rts51x: Bad target number (1:0)

[  17.566648] rts51x: Bad target number (2:0)

[  17.566694] rts51x: Bad target number (3:0)

[  17.566738] rts51x: Bad target number (4:0)

[  17.566768] rts51x: Bad target number (5:0)

[  17.566797] rts51x: Bad target number (6:0)

[  17.566825] rts51x: Bad target number (7:0)

I would check the config file again more carefully for things related to the ones in the log.
Run lspci -v to know exactly what hardware do you have, so then you know what have to stay and what have to be gone from your config.

xorg.0.log

Code:

[  330.481] (EE) Failed to load module "vesa" (module does not exist, 0)

[  330.481] (EE) Failed to load module "modesetting" (module does not exist, 0)

[  2914.621] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)

Check if everything is ok in your xorg.conf file.

Regards

Quote:

Originally Posted by ukiuki (Post 4816405)

The .xsession-errors file is in your user directory.

Hmm...checked my user directory and the one for root, still no .xsession-errors file... something might be wrong with my install of X.

Quote:

Originally Posted by ukiuki (Post 4816405)

About the kernel make sure you have the options for consoles enabled under:

Code:

Device Drivers > Character Devices > Virtual Terminal

I have verified that this option was correctly set in my config

Quote:

Originally Posted by ukiuki (Post 4816405)

I did found some things in your logs, take a look:
dmesg

Code:

[    0.000000] No AGP bridge found

[    0.000000] No NUMA configuration found



[    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!



[    0.550103] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored



[    0.974003] ACPI: No dock devices found.



[    0.974077] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug



[    1.085553] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)

[    1.085641] uvesafb: vbe_init() failed with -22

[    1.085715] uvesafb: probe of uvesafb.0 failed with error -22



[    1.158787] [drm] MTRR allocation failed.  Graphics performance may suffer.

[    1.160276] [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed



[    1.883253] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS



[    1.909699] video: probe of LNXVIDEO:00 failed with error -5



[    2.185332] ACPI Warning: 0x000000000000f040-0x000000000000f05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20120320/utaddress-251)

[    2.186200] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver



[  17.566546] rts51x: Bad LUN (0:1)

[  17.566600] rts51x: Bad target number (1:0)

[  17.566648] rts51x: Bad target number (2:0)

[  17.566694] rts51x: Bad target number (3:0)

[  17.566738] rts51x: Bad target number (4:0)

[  17.566768] rts51x: Bad target number (5:0)

[  17.566797] rts51x: Bad target number (6:0)

[  17.566825] rts51x: Bad target number (7:0)

Code:

[  330.481] (EE) Failed to load module "vesa" (module does not exist, 0)

[  330.481] (EE) Failed to load module "modesetting" (module does not exist, 0)

[  2914.621] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)

Check if everything is ok in your xorg.conf file.

Regards

I know exactly what this is all from. I attempted to get a wireless USB display/USB hub working via the DisplayLink drivers a while back. I am guessing I did some permanent damage to my config. I am going to rename the .config file and recompile the kernel with the default config to see if that fixes it.

Well I managed to figure it out. After stumbling upon an illusive thread regarding openrc-11.0 and the same issues, I re-emerged openrc-11.2 and udev-init-scripts. As an install note, udev-init-scripts now requires udev-mount at sysinit via rc-update. After a reboot the errors on boot and terminal issues were resolved.

Here is the link: http://forums.gentoo.org/viewtopic-p-7167918.html

Thanks again to everyone that helped me get through this.