Help

barabus · 05-11-2005, 02:57 PM

Hi All,

Had the system (Suse 9.3 pro) running nicely and seemigly configured for about 4 hours or so. Was able to switch sessions without any problem but eventually XConsole hijacked me onve again.

I cannot log in as either root or user at the present and am stuck with the beautiful Grey screen to irritate me even further!

XConsole thows up a variety of messages each time I reboot from XTerm among the most frequent being:

Code:

linux kernel: drivers/usb.media/ov511.c: ov518 config failed
linux kernel: drivers/usb.media/ov511.c: Camera initialisation failed
linux kernel: ov511.probe od 4-1.3.1.0 failed with error -5
linux kernel: ieee80211-crypt_ktip: unsupported module tainting kernel
linux kernel: ieee80211-crypt-comp: unsupported module taintink kernel
linux ifup: No configuration found on eth1
linux MDNSResponder: Duplicate registration of DNS Entries

Any idea what i need to fix here to get into the KDE - and how to fix it?

The Duplicate DNS entries are set by my Cable Provider who seemingly have 2 servers running at www.intercable.com.ve and at www.intercable.net.ve. My DHCP client picks up both and both have similar DNS adresses. These values seeminlgly change at different hours of the day so its necessary to have the automatic settings enabled.

This is an ongoing problem thats been plagueing me for several days now and numerous reintalls etc. I finally thought I had everything right until Nasty Mr. XConsole had his say.

Please someone give me a solution to this!

Also is it normal to lose the graphical reboot/shutdown options that previously existed in KDE straight after installation? It seems all I can do anymore is to end session open XTerm or similar - log on as super user and either type halt or reboot (a pain in the butt!) or otherwise logout and hit the power button on the laptop. (This of course is when I am blessed with a GUI)

I hope someone can get me through these nervous times......thanks!!!

- Blackbeard

ehawk · 05-12-2005, 07:54 AM

I think you could log in using the installation CD and looking at the recovery/emergency option (or something like that). If that doesn't work, you can login when the bootloader comes up. Google for ""linux single" login".

teckk · 05-14-2005, 11:20 AM

each time I reboot from XTerm among the most frequent being:

Are you issuing a halt or shutdown command from Xterm to shut off or reboot in KDE instead of logging out with KDM. That will cause you problems, like KDE not saving things. If you are using KDE use the logout function of KDE.

If you are set to auto graphic boot then, boot to recovery mode howerver you do it and change your inittab file to boot run level 1 instead of 5. 5 is graphic boot, 1 will boot you in a single user to CLI. Then you can troubleshoot what you have.

inittab is located at /etc/inittab

Use a CLI editor like vi, vim, mcedit, ee, emacs or whatever you use to edit the file.

Once you get where you can login, then you can troubleshoot.

Ok I read the rest of your post, you don't have a logout option in KDM. This probably what is causing the prob. You might want to consider re-install of KDE.

I'll let others look at this and respond.

Good luck.

Filmoscope · 05-14-2005, 11:55 AM

your file system seems to be crashed after system hang or reset. You should boot using recovery CD or boot using single mode and recover your system partition.

barabus · 05-14-2005, 12:43 PM

I tried to go into the rescue mode. Logged in as rootand get a RESCUE prompt. What next?have no idea of how to run the rescue commands or whatever.

I browse the dir and don't find much there.

Windows is so much simpler!!!

My Partitions seem fine as I can boot into Windows........... problem being simply that SuSe is not mounting the partitions at boot up.

So how do I tell it to?

Filmoscope · 05-14-2005, 09:51 PM

YES,YES, you have to know something to work in Linux.
But some time later you will find you prefer to work in Linux becouse you can't do many things in windows
(Joke)

Boot from CD, log in as root,
check your linux partitions with fsck(for ex. for file system reiserfs you should use reiserfsck, for ext2/3 - e2fsck,
and so on)
then sync and reboot(not reset!)
If you boot as single from hdd, you should remount your root partition as read-only before checking. Google for more info