This is what my computer looks like while it's booting. Gdm pops up shortly, and I can use my computer with no problems. More recently, I screwed up something in gdm, so I can't do anything with my ubuntu computer.
View 3 RepliesAfter installing Opensuse 11.3 i get massive graphical errors after reboot. Those errors directly start after the first resolution change after grub. So i used nomodeset from now on and installed the drivers from nvidia.
After this X11 only flasht up very shortly and i got this logs:
Code:
since I upgraded from Debian 5 to 6 there are strange red (and blue) stripes all over my GNOME desktop.I have experienced these graphical glitches in the past, but only in 3d-intense applications, never on the desktop. What is wrong with my setup? Does GNOME (my version is 2.30.2) make use of 3d acceleration features that were not used in past versions (that is, in the version that I had prior to upgrading)? If so, I may have a driver problem -- however, the glitches occur with the free Nvidia drivers as well as with the proprietary drivers (I tried version 195.36.31, which should be fairly new). I am beginning to suspect that my video card is broken.
View 4 Replies View RelatedI have a samba file server that has Windows XP machines connecting to it. Fairly regularly, I get messages such as the following. Are these anything to worry about? What do they mean? Nobody ever has problems with disconnecting or losing their mapped drive or their desktop shortcut not working.
Code:
Nov 15 15:37:21 servername smbd[27516]: [2010/11/15 15:37:21, 0] lib/util_sock.c:read_socket_data(384)
Nov 15 15:37:21 servername smbd[27516]: read_socket_data: recv failure for 4. Error = No route to host
[code]....
Installed 6.01a from DVD 1 on a system with 4GB ram. Installer installed amd64 version by default. When I try to install amd64.deb files I get "wrong architecture" error messages from the package manager.
root@Laptop-RalphDeb:/home/ralphq# uname -r
2.6.32-5-amd64
root@Laptop-RalphDeb:/home/ralphq# uname -p
unknown
Why I can install amd64 programs and why I get unknown for the uname -p command?
I know how to manage them from a commandline but I was wondering if there are any graphical partition editors that understand and work with lvm2?
View 1 Replies View RelatedI am using 10.04. The grub is working properly but i can't login in graphical environment because the system stops at the ubuntu boot logo. However, TTY is working properly and i am able to login in all the tty [F1-F6]. I think the problem is with xserver but I don't know how to fix it.
View 4 Replies View Relatedi am trying to keep my gui from loading unless i want it to. does any one know how i can go about doing this? also how do i uninstall the graphical boot also i have heard that you can add a 3 on to the end of a your kernel line in grub to get a non graphical boot. this also sounds interesting to me
View 9 Replies View RelatedI just installed the Catalyst drivers under FC13 (package xorg-x11-drv-catalyst-10.9-1.fc13.i686 ) and I am superhappy, as it worked straight out of the box.
The only little annoying thing is that I lost the Plymouth graphical boot, which is now substituted with the text scrollbar...
I edited grub.conf and added
Code:
Somewhere I read that that attribute is now obsolete and has to be changed to
Code:
But that did not work either.
My Fedora11 hangs on boot. I have no idea where or why it is hanging so I want to disable graphical boot. I booted the installation media, the root file system mounted on /mnt, seted /mnt as my root with the chroot command and edited /etc/inittab, then unmounted and rebooted but it didn't help me. Is it possible to run gconf-editor under live cd and disable splash? How can I boot Fedora in single mode? For example use the following steps I'll be able to boot RHEL into single-user mode:
At the GRUB splash screen at boot time, press any key to enter the GRUB interactive menu.
Select Red Hat Enterprise Linux with the version of the kernel that you wish to boot and type a to append the line.
Go to the end of the line and type single as a separate word (press the Spacebar and then type single ). Press Enter to exit edit mode.
Since I've been using the nvidia drivers (from rpmfusion) and followed Leigh123's nvidia guide, I don't have a Plymouth graphical boot anymore. Instead I get the black screen and the blue/white bar at the bottom. I installed the plymouth-theme-solar (or whatever) and switched to that, updated initrd too, but no difference - same thing happened. This is an AMD64 system, latest kernel, latest nvidia drivers. Snippet of grub.conf:-
title Fedora (2.6.31.9-174.fc12.x86_64)
root (hd0,2)
kernel /vmlinuz-2.6.31.9-174.fc12.x86_64 ro root=/dev/mapper/vg_undertaker-lv_root LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet selinux=0
rdblacklist=nouveau
initrd /initramfs-2.6.31.9-174.fc12.x86_64.img
Recently, I accidentally erased plymouth from my Fedora 12 system.I now have reinstalled plymouth.But I still do not have my graphical boot. How do I switch back to graphical boot?
View 2 Replies View RelatedI have updated 11.3 to 11.4 with downloaded iso (64 bits). I have a ATI hd2400 card that in 11.3 had no additional or other drivers. Now after install of 11.4 the systems reboots in the splasscreen everytime I am now in failsafe mode to get graphical.
Output of /sbin/lspci -nnk
00:00.0 Host bridge [0600]: Intel Corporation 82915G/P/GV/GL/PL/910GL Memory Controller Hub [8086:2580] (rev 04)
Subsystem: Dell Device [1028:01c4]
Kernel driver in use: agpgart-intel
00:02.0 Display controller [0380]: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller [8086:2582] (rev 04) .....
After messing up with gnome3-branding(gfxboot),I removed itow grub is back to minimal.There is no graphical bootloader anymore.I tried reinstalling opensuse-brandingt it says "message not found"
View 9 Replies View RelatedThe problem is when I boot from the lubuntu CD & select Try Lubuntu or Install Lubuntu the computer hangs. Xubuntu 10.04 was aready installed & I could easily boot to it. I thought may be some partition table error is causing that issue & I deleted all the existing partitions with Parted Magic Cd in Console Mode.
NB: When I tried to boot to the Parted Magic graphical session the PC hanged then too.I am totally confused. Cant understand what is going wrong here. I am now left with a broken system.
After a recent "yum update", my laptop screen locks up during graphical boot. I use rhgb on the kernel line. The container on the screen fills up with charge and then the screen locks. I have to use the power button to reboot. If I press ESC when the boot splash appears (i.e., boot in text mode), it works.
If I set plymouth to "details" mode using
$ plymouth-set-default-theme details --rebuild-initrd
It boots up correctly. This is equivalent to a text boot screen. I doubt whether it is a video driver problem. I reinstalled the nvidia driver and it is working. I also reinstalled plymouth and plymouth-themes-*.
I've put a fresh install of Fedora 13 x86_64 on my new server and I have it automatically log in to the gnome desktop so I can control it via VNC. However this only happens when there is a monitor physically connected when the computer boots. If there is no monitor present at boot time, there is no graphical session started, however I want it to start whether or not a monitor is present.
My hardware is a Zotac IONITX-G-E board (which has an Atom N330 and a NVidia ion chipset of some description). I'm using the Fedora default graphics driver (nouveau). Why doesn't it start a graphical session with no monitor, and is there any way to get Fedora to start one whether or not there is a monitor connected?
I am having a very strange problem with GRUB: it refuses to boot from certain partitions, and in a very strange way. This is what I've noticed so far:When using GRUB in the default OpenSUSE 11.3 graphical interface and trying to boot it, GRUB almost always gives me Error Message 16: Inconsistent filesystem structure. The GRUB manual says that "This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB. " I've ran fsck on all the partitions and neither of them has any corruption. When I switch to the non-graphical GRUB window, the message changes to Error Message 18: "Selected cylinder exceeds maximum supported by BIOS".
The GRUB manual says that "This error is returned when a read is attempted at a linear block address beyond the end of the BIOS translated area. This generally happens if your disk is larger than the BIOS can handle (512MB for (E)IDE disks on older machines or larger than 8GB in general). " However, I haven't touched any BIOS settings when the problem started to appear, and the BIOS is brand new anyway so it doesn't have such limits. When I try to boot directly from the command line, it roots to the boot partition just fine, but refuses to load the kernel, giving me the error 16 again.
When I try to boot Windows from the non-graphical GRUB list, it gives me the error 18 again, but it always succeeds when I do all the booting directly from the command line. One time I was able to boot Linux from the command line by using rootnoverify instead of root, but never again since then. One time it didn't boot Windows even from the OpenSUSE graphical interface, error 18 again. Sometimes it boots even Linux just fine, but it happens quite rarely now. The problems started appearing just recently, and without any reason that I could think of. I also ran setup again in order to reinstall GRUB, and it worked for one boot, but not any more...
My partition list is like this:
(hd0,0) Windows 7 boot, NTFS, primary
(hd0,1) Windows 7, NTFS, primary
(hd0,2) Windows XP, NTFS, primary
(hd0,3) Extended
(hd0,4) /root, EXT3, logical
(hd0,5) /home, EXT3, logical
(hd0,6) swap, logical
(hd0,7) /boot, EXT2, logical
I have successfully installed the Nvidia driver on my FC13 system that is using an Nvidia NV44 (Ge 6200) card. It seems to be working as I see the nvidia driver when I do a lsmod | grep nvidia and the glxgears program works as well as the nvidia-settings program.Basically, I did the following:
Code:
yum install kmod-nvidia-PAE
new-kernel-pkg --mkinitrd --dracut --update $(rpm -q --queryformat="%{version}-%{release}.%
[code]...
I just upgraded to 10.04 through the Update Manager. During the updated however I got an error telling me that it was unable to install something. Sorry, I can't remember what it was; it didn't stop the updated so I assumed it wasn't that important. Anyways, I don't know if this is because of that error, but during the boot process and when shutting the computer I get console messages. When I boot it tells me that "mounting none on /dev failed No such device" and when I shut down I get these messages.I see this was asked before and that it isn't a big issue, but I'd still like to solve it. The problem is that I'm pretty new to Ubuntu and Linux in general I don't know how to follow the very general instructions given in that thread.
View 2 Replies View RelatedI have Ubuntu 9.10. The batter drained several days ago, and now when I attempt to boot I simply get a string of indecipherable error messages which last for about 5 minutes, and the screen then goes completely black. I am not able to even get to the login screen. Windows 7 Starter boots fine, so it's definitely a software issue. Any solutions short of completely reinstalling? I really don't want to lose all of my data.
View 2 Replies View RelatedSo I'm using opensuse 11.2 and recently installed ubuntu 10.04 to a different partition and all went well. when I boot opensuse I get a lot of interesting messages yet everything seems to load fine and I've not noticed anything behaving differently. I checked the boot log via
Code:
Looking through it i did see a line in there that looked familiar from the boot up and it is
Howto configure Ubuntu 11.4 with Gnome to show boot text messages on the screen, each time during the startup?
View 3 Replies View RelatedDuring boot-up and shutdown of Fedora-14-x86_64-Live-Desktop.iso live USB, I just see some graphical stuff. What needs to be done so that the screen shows text messages about what's happening during boot-up and shutdown?
View 2 Replies View RelatedWhat /where is the file, that shows boot up messages.
View 2 Replies View RelatedI'm getting a boot message that goes by too quickly to read. Is there a way to slow them down?
View 11 Replies View RelatedI've enabled BOOTLOGD_ENABLE=Yes in /etc/default/bootlogd on my Squeeze (Upgrade from Lenny) installed on the notebook, but after Retsrat NO bootlog messages in /var/log/boot. Is it a BUG?
View 2 Replies View RelatedEDIT: not fully solved; there is (at time of writing) still an issue about bootlogd buffering until the logfile is accessible but that's probably as far as we are going to get for now, until someone peeks into the bootlogd source code.
Is it possible to review boot messages after boot? Kernel messages are available via dmesg (and many are logged early in the rc.M script by the /bin/dmesg -s 65536 > /var/log/dmesg) but many console boot messages are not kernel messages. During boot, messages can be viewed using Shift+PgUp but when the rc.S script finishes, init starts an agetty on tty1 which prints a login prompt. Then tty1 is no longer the console and Shift+PgUp cannot be used to scroll back through the boot messages. Any delayed boot messages do not have effective carriage returns so "marquee" across the screen, one following another, a line below.
Is it possible to leave tty1 as the console by de-configuring the tty1/agetty line in inittab, thus allowing Shift+PgUp to be used to scroll back through older messages and allowing proper horizontal alignment for delayed boot messages? I would try it but the inittab line x1:4:respawn:/etc/rc.d/rc.4 runs /usr/X11R6/bin/xdm and this grabs the first unused tty<n>. The xdm man page and xdm config file comments do not reveal whether it is possible to make xdm use a specific tty<n>.
Another solution may be something like the sysvinit binary that intercepts all console writes and then dumps them to log at the end of the boot process but if it were that easy or useful it would already be done and publicised (wouldn't it?).
I'm running slack64 13.0. At initial boot i see the two penguins and text from th kernel scrolls past until my root partition is mounted where upon all messages stop until the console prompt or KDM pops up. Everything seems to be operating as normal but i've no idea whats happening during the rc scripts (FS checking, etc). When shutting down though the rc.6/rc.0 script messages appear in the console though.
To my knowledge i've not changed anything that would effect this (just modified inittab for runlevel 4 & tty4,5,6 in runlevel 4).
There's nothing in dmesg but most messages don't get logged there as i understand.
I have removed desktop manager from /etc/init, and GRUB is configured to use console. After upgrading from Karmic to Lucid I have noticed just before login invitation all previuos console output is cleaning. As a result I can not see boot process messages with Shift-PgUp/PgDown. How to prevent console output cleaning?
View 2 Replies View Related