Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've just rebooted the system and it stuck on a white page with the timer icon(the ubuntu icon for the window's on. I saw this same page on another laptop when I installed the ubuuntu live cd mode. It appeared just before entering the ubuntu desktop. I hope I.ve been explicit enough.
Something new. According to this thread http://ubuntuforums.org/showthread.php?t=334220&page=2 this issue is still related with that f*****g I/O apic. I tried to follow their instruction but apparently they dont work. I know this is another version of ubuntu and maybe I must act differently.
There's another suggestion in that thread that might help: Boot to the command line, connect to the Internet, and run dpkg-reconfigure xserver-xorg. Then check that the Driver setting in /etc/X11/xorg.conf is still openchrome and the one in xorg.conf.failsafe is vesa.
Then reboot and try the failsafe boot option.
After you bring up your Internet connection, before running the dkpg-reconfigure, you might consider an apt-get install mc to install the "Midnight Commander" package. Then the mc command will bring up a semi-gui, dual pane, "file manager" that I've found "nice to have" when I'm stuck in a terminal session for some reason.
Hey Ptre you know what?
I am writing this post from MY LAPTOP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Finally with your precious help,and mr. bridge too, I got my ubuntu up and running. I still dont know if the sound card is working or not but I dont care, I am too happy. THANX THANX THANX THANX.
Ifollowed your last suggestion and finally it worked. I stiil dont know if the apic is involved , but I think I havent modified the kernel on my last reboot!
I am very glad to have joined the linux community and thanx again!
Last edited by marco v.; 04-05-2009 at 03:59 PM.
Reason: spell errors
Great! Do note the "thumbs up" in the bottom right of a post where you can flag a post as having helped you. (Eventually, Jeremy will look at posts ranked by "number of times flagged" to see if that information can be used to identify common problems and solutions.)
Very bad news!!!
Hope somebody is still reading this thread. Last night I had a very nice session with my ubuntu:a great feeling. Ptre is maybe right it does not seem that openchrome drive support the 3d. Anyway: today ubuntu is till stuck.Ichecked the kernel: the command noapic is still there, and xorg.conf is not changed.
Itried again to boot ubuntu but it sticks just before the log in.
Ptre suggested to open ubuntu from recovery mode but I cannot see that option. These are the options I am offered in recovery mode menu: Resume normal boot, Try to make free space,Repair broken packages, File system check, Drop to root shell prompt, and try to fix x server.
I really dont understand why last night I coud run ubuntu and today I cant, with the same settings.The difference is that I started but not completed to download all the upgrades.
Ah, the problem may be that you've got incompatible programs installed, which can happen if you interrupt an update after the files are downloaded but before the installation of those files is complete.
Anyhow, the first thing to do is get you up in "rescue" mode so you can finish the update. The "secret" to the list of options you quoted is that that's not the whole list. The list you see will scroll up if you use the arrow key to move the highlight down the list or, if it works, the mouse to move the scroll bar, on the right of the window, down.
Then you should be able to select the "Terminal" option to get to a command prompt. (I've forgotten the exact wording of the option, but it should be obvious.)
After you get a command prompt, connect to the Internet (dhclient) and then do an apt-get update followed by an apt-get upgrade.
If you want to learn more about apt-get, the command man apt-get will show you most of the details, and, for example, explain the difference between an update and an upgrade.
You might also like to look at the aptitude command which provides a "semi" GUI for the apt-get command. A man aptitude will provide details of that alternative.
Unfortunately my recovery mode menu is all there. I tried already to scroll down but there arent other options. I completed the upgrade in command line(in the menu is open a command shell prompt) and upgdated and upgraded. The only knew thing I noticed is that in xorg.conf the comment driver with the specific one(openchrome) is no more there and editing it again from nano does not change anything.
This the situation in my kernel line after the "ro": noapic quiet splash. First there was the xforcevesa command that I removed, I put there again with no difference(and I think tehere is no point to force ubuntu to load vesa is my chipset does not support it).I also tried to fi omit noapic, with no effect.
Now this is the situation when I load aptitude after upgrade: there are several packages not installed, among teose there are 423 GNOME desktop system packages 549 graphic packages and 549 graphic package still to install.Not to mention taht after atp upgrade ubuntu upgraded a lot of packages I really dont know what to do with this stuff.My laptop still freezes just before the log in. Just for the record I checked the disk for errors when I installed Ubuntu for the firdst time and it was ok. another info: when I type start x from the command in line with this setting(driver of choice openchrome)it doesnt see any error as it did when I was starting the system with other drivers.I am sligthly desperate but I will win at last!!!!!!!!!!!!!!!!
P,S. I also tried to disactivate apci with nohpet in the kernel with no efffect
Last edited by marco v.; 04-07-2009 at 03:39 PM.
Reason: more info
If the noacpi makes no difference, leave it out since disabling the ACPI when you don't need to do so will make your system work harder than it needs to. And, likewise, disabling the HPET will unnecessarily slow down your system if it can, in fact, use your HPET.
Many graphics packages and GNOME packages are for special situations, and there's seldom any need to install, for example, everything that has "GNOME" in it's description.
When you say that aptitude shows "423 GNOME and 549 graphics packages still to install," I suspect that you're looking at the list of available packages, not the ones with problems.
At this point, I'm not clear about the state of your system. It seem to me that you can start a command line session, but can you then run startx and start a GUI session as "root?" If you can, can you instead issue the command su marco to log in as "marco" at the command prompt? (I'm assuming that you created your Ubuntu login name to be "marco." If it's something else, you should, of course, use whatever you used when you installed the system.) If you can't log in as "marco," then there's something wrong with the way your login has been set up, and we'll need to start over. (This is fairly easy to do, but there's no point in describing the process if you can log in as "marco," so I'll assume that you can do so until you tell us otherwise.)
Once you've logged in a "marco," the "#" prompt should change to a "$" and you can then try a "startx" to start a GNOME session for "marco." Hopefully, one of two things will happen: Either you'll see some error messages in the terminal window that will give us some clue about the "freeze" problem, or, instead, your GNOME session will start.
So, try the above and let us know what happens.
Now I need to go cook a risotto for supper, but I'll try to check back in a few hours.
I can trade linux lessons with italian cuisine lessons!
I did what you suggested in the last post(hitting startx in $) and ubuntu still freezes, but every time(I tried three times) it freezes in different waysnce I could see the ubuntu wall paper and a piece of upper task bar and the other times something not clear. Browsing man xserver I found out you can start a session with xinit and Xorg. Itried both options in order to gather more info and this was the error msg for Xorg and xinit:
(EE)[drm] drnOpen failed ; (EE) CHROME (0):[dri]DRIScreen Init failed.Disabling DRI.Isuppose this is the same msg appeared when I tried to open startx but the msg disappeared too fast and I couldnt read it. Hope these pieces of info have been useful.
Hey, the risotto was great: An asparagus risotto (using American-style green asparagus), but: (1) The broth was enriched by pureeing the lower (excluding the tough part) part of the stalks into the broth, and (2) I replaced half the grated hard cheese with soft goat-milk cheese. Much richer asparagus flavour, and smooth and creamy for my one-year-old grand daughter.
So, to return to your problem:
I'm wondering if the GNOME window manager is attempting to use display features which are not supported by the openchrome driver. Perhaps you should try the XFWM "light weight" display manager to see if that might work.
To do that, you need to use apt-get to install the XFWM, so boot to the terminal window, do the dhclient to start your Internet connection and then run the command apt-get install xfce4 xfwm4* to install the alternative display manager.
When that finishes, there are two ways to proceed. The simplest is to try a normal boot to see if the standard log-on screen is displayed. If it is, there should be a "menu" button somewhere on the screen. Press that and select the "Session Type" option. Then check XFWM, enter your password, and see if it works.
If that doesn't work, well, post here again. I was going to describe how to start the XFWM from the command line, or, at least, set it to be the default, but I can't figure it out. I though all I'd need to do was change /etc/X11/default-display-manager, but that had no effect when I rebooted my system. (I'm typing this from a XFWM session, so I know that that the apt-get command, above, installs the alternative display manager, but startx /usr/bin/xfwm4 -- :1 just gets me a black screen with a mouse cursor.)
Anyone else viewing this thread have any ideas?
Oops! The /etc/X11/default-display-manager file is the display manager, not the window manager. (I'd forgotten that I hadn't rebooted when I claimed, above, that changing the value had no effect.) Possible values for the file are:
To use either of the alternates to gdm, do an apt-get install xdm or kdm. When you do so, you'll get a pop-up where you can select the one to use as your default, and you can change the default by editing the file.
The combination of xdm and xfwm4 probably places the least demands on your display hardware.
Last edited by PTrenholme; 04-10-2009 at 12:05 PM.
Yumm! your risotto must be great. Are you also a senior member in cooking forum ?
I found the way to start the xfce window manager from the command line and is as simple as startxfce4 , but it happened the same thing that happened to you(blank screen and a mouse arrow).I managed to come back to the command line and the error msg was the same with DRI. (check my previous post).Haven't checked the part you edited yet but I'd like you to have a look at this two threads, because maybe the solution of my problem is there but I really need advice. http://www.mepis.org/node/13367 and http://www.pclinuxos.com/forum/index.php?topic=54950.0 . I dont know if it s rude to qoute posts from other forums, but i think the more info we put together the best is for the solution of this issue.
Well, your problem appears to be with the DRI, and the first thread suggested that the /etc/X11/xorg.conf file should contain a stanza like this:
So, again, boot to the command line, do a nano /etc/X11/xorg.conf and add that block at the end of the file. Then reboot, and a normal login to see if it helped. (The "mode" is just setting access permissions for users to invoke the direct rendering. Basically, "666" means "let any program that needs DRI use it." I would have thought that was the default, but maybe it's not.)
and the ibex is now up and running!!!!
I found out that a lot of users with other distros have the same issues with Via chipsets, and somebody suggested to edit that option beneath the driver line, and it worked!
Thank you Linuxquestions.org community!
A special thanx to ptrenholme, without his/her patience I could have never solved this problem!!!!!!!!!