I had this problem with a wubi install. Ubuntu would highly pester me and drop to command shell (that of grub) without showing the boot options (Why and who knows??). I every time will have to boot by manually entering boot options (really painful). So I did this. I entered the boot command of the “recovery console” manually by finding it out from grub.cfg through the Live CD. After getting to the repair option I selected the option “Update GRUB”.

This one seems to be a really famous problem for most folks in Ubuntu 9.10 Karmic Koala. So I had it too. The problem was on the initrd file. It is a kernel related file needed for booting. So i did a simple thing. I replaced initrd.img file of my kernel version with “initrd.lz” file from the Ubuntu LiveCD and edited my grub.cfg file (equivalent of menu.lst in older Ubuntu releases), to boot using initrd.

Nvidia Proprietary Drivers need nvidia-settings to set screen resolution and change other settings. In previous versions of Ubuntu and in other distros to make them permanent (used in every session) you click the “Save to X configuration file”. From Karmic on there is no xorg.conf by default!

As a result, nvidia-settings is not able to save the settings and every time I logged in I had  to change the resolution (Phew!!!). Then Sathya helped me. He gave me a link from Ubuntu Forums{#aptureLink_MZsWFB9Cv4}. Then I did the following to fix the problem:

Saw this question on SuperUser : How can I add menu items to the Gnome “Applications” menu from the command line? Yet another SuperUser Q RSS Feed Notifier for Linux Seems Canonical will set limits to those who can order free CD’s via Shipit. The discs will still be made available to Local Community team members and Ubuntu contributors. And new Ubuntu users will be able to request a CD.

This is one problem that has affected me the most in my history of Linux usage, so far. Imagine, for two full years I just din’t know that the solution to this problem is so simple. Too late of me to find out. Anyway, better late than never. So the problem is, with my graphics card GeForce FX 5200, Ubuntu liveCD/post-installation boot will hang mid-way, with the boot-screen freezing or a big set of hexadecimal codes getting emitted.

In Karmic the restart Xserver shortcut is disabled by default. Enable it thus: In the menu, go to System->Preferences->Keyboard (not Keyboard Shortcuts) Go to Layouts tab, click Layout options Expand “Key sequence to kill the X server”. Check “Ctrl+Alt+Backspace” You’re Done.

Ubuntu 9.10 “Karmic Koala” released, but reception hasn’t been spectacular. Poll on Ubuntu forums indicates that ~ 39% of users have had problems they could not fix{#aptureLink_w7mk4Gj53R}. Upgrading from{#aptureLink_o93sno8FFY} Ubuntu 9.04 Jaunty Jackalope to 9.10 Karmic Koala. Installing nVidia drivers{#aptureLink_cSXrJksL0x} (v190.42) in Ubuntu KDE 4.3.3 released{#aptureLink_oXTbIbKNeA}, brings in few bug fixes. Experiencing Sabayon 5{#aptureLink_9hqyejQU50} //personal note: must try it soon. First GNOME 3.0 development release available{#aptureLink_Dr8Kjty26c}.

Found this blog while surfing. Very useful!

These are some various linux/unix problems I’ve encountered over the years, but which I was not able to find a solution for online. Hopefully this will save you the trouble I had.

by Vidar Holen

Homepage

[]1Problem:

Network interface (or anything else on the pci bus) says “SIOCSIFFLAGS: Resource temporarily unavailable”

Cause:

No IRQ assigned to the device, check /proc/pci (irq says 0)

Solution:

Enter the bios setup (F1 or Del on boot), disable the option ‘Plug n Play OS’.

Reason:

This will make your bios set up IRQs for you.

Problem:

USB mouse using /dev/psaux, the ps/2 mouse device.

Cause:

Bios usb legacy support in action, probably because Linux didn’t probe for USB devices (which causes the bios to release control of them).

Solution:

Compile the kernel with USB support, Input Core and USB HID.

Reason:

Duh.

Problem:

USB mouse still doesn’t work on /dev/input/mice, but /dev/psaux, even when USB support is compiled in.

Cause:

Legacy USB support again. You might not have compiled in support for your USB chipset (the UHCI parts in USB support).

Solution:

Compile UHCI. If not working, try the alternate drivers.

Reason:

Duh.