Tag Info

New answers tagged

1

I use "setxkbmap" with no arguments. It seems to reset the keyboard. I have a "shortcut" in my panel that I can use with a mouse for when the keyboard is completely inoperable.


1

You are missing one of the drivers that is necessary to access your root filesystem. The code in the initramfs is looking for a block device to mount and failing, so the problem is in accessing that device. You won't get a more explicit message because the code in the initramfs can only see what it has access to and the problem is that it doesn't have access ...


0

Found it!!! It was the drivers for my hard disk controller, SATA AHCI was not added while configuring kernel before compilation. Now I added, recompiled and viola! new installed kernel booted up. :)


1

Reading the documentation and man pages leads me to believe that you should use netconf. According to its manual page, something like: netconf -a and then answering any interactive questions, likely does what you wan. You're existing configuration exists in: /etc/inet.conf It seems you can also get dhcpd to print its current view of the world with: ...


0

2.6.X kernels You can increase the resolution at the console like so via your /etc/grub.conf file. Find the kernel ... line pertaining to your system booting up: kernel /vmlinuz-2.6.32-358.11.1.el6.x86_64 ro root=/dev/mapper/vg_mungr-lv_root rd_LVM_LV=vg_mungr/lv_root rd_LVM_LV=vg_mungr/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM ...


0

I found this thread titled: VERR_SUPLIB_OWNER_NOT_ROOT - solved which describes several possible reasons why you'd get this message. Most of them stem from the permissions not being set properly. In addition to making sure the permissions are correct for the file you mentioned you'll want to make sure that the permissions for the directories that its inside ...


3

First of all, DNS is primarily a UDP service, not a TCP service. DNS is on UDP port 53; make sure that UDP port is open for incoming connections on the DNS server machine. In addition, DNS can optionally use TCP, which uses TCP port 53, but while DNS can work fine without TCP, it doesn't work without UDP. Second of all, it's far better to use dig instead ...


0

You have to check whether the firewall configuration allows forwarding: iptables -L -nv But it is not enough to configure the firewall to allow routing. The routing feature itself must be enabled in the kernel. If the kernel does not even try to route then it does not matter whether the firewall would let the packets through or not. You can check the ...


1

This looks like you're using VirtualBox VM with a NAT network (it seems to give the address 10.0.2.15 by default). If so, you need to set up a port forward to access port 22 on the VM from the host. Open Settings->Network for the VM Click the little blue arrow next to the Advanced box Click the box at the bottom labelled "Port Forwarding" Click the green ...


1

Depends on how you configured your network interfaces. I would check in /etc/sysconfig/network-scripts/ifcfg-eth0 on the new VM and see if you can just change the value for IPADDR if it's present. If you have NetworkManager running and the interface is configured with NM_CONTROLLED=yes then the change will be applied when you save the file, otherwise you'll ...


0

Since you're getting a 403 I'm going to assume that you're have internet access working. Try downloading the .deb files directly via the command line. $ wget http://security.debian.org/pool/updates/main/p/pidgin/pidgin_2.10.9-1~deb7u1_amd64.deb Things that could be an issue here: DNS APT installation/config is hosed The URL is down As I said since ...


1

open a terminal su cd /mount/yourcd ./VBoxLinuxAdditions.run The problem you faced is that there's no autorun on the CD and it's a very good thing, because autoruns can be dangerous.


2

What desktop environment? Gnome comes with a plain desktop. Move the mouse to the border or the upper right corner. Does it help? If it doesn't help or it's not Gnome post a screenshot. Where did you download the installation or virtual machine? 32 or 64 bit? What size of Hard disk did you use? How much CPU / Ram? Where did you place the virtual box files / ...



Top 50 recent answers are included