I cannot boot after installing Squeeze. /home partition is missing.
Here is the related information.
df -h
Code:
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 6.5G 4.5G 1.7G 73% /
tmpfs 1.7G 0 1.7G 0% /lib/init/rw
udev 1.7G 196K 1.7G 1% /dev
tmpfs 1.7G 0 1.7G 0% /dev/shm
[Code].......
Hardware at issue is an nVidia GeForce 9600 GT. Issue occurs regardless whether the driver is downloaded and installed from nVidia, or installed via Synaptic courtesy of the new dkms package in the repositories.
It should also be noted that the issue only arose after an update today, as follows:
I do not believe it is related to the last three items in that list. Because everything worked perfectly before todays update, it would appear that one of those other updates is causing KDM and nVidia to not want to co-operate with each other.I also notice that, new to the boot sequence, the system is booting with "concurrency" - never seen that scroll by before - which may have something to do with it too.
OK, what happens. KDM "fails" to start when booting the computer. Symptoms : At the appropriate spot in the boot sequence, the screen goes black (as usual), but then, instead of the cycling cursor followed by the logon screen, the nVidia logo appears, and after about 7 or 8 seconds, the screen goes black for about a second, then drops me back at the console. From there, I can log in as root.
Now, the thing is, KDM is actually running, but using <control> <alt> <F7> only brings me to a blank black screen. By issuing the command /etc/init.d/kdm restart, I come up to a normal logon and can proceed as usual. As well, if I delete xorg.conf, system boots OK.
Looking at the system log, we find :
And then some way past that we get :
Should mention that was using the latest stable driver from nVidia (195.36.24), but in the hope that maybe something in the latest beta may solve the issue, installed that, but the answer is nope And yes, completely uninstalled the nVidia drivers between each test of the nVidia driver, the same driver in the repositories and the latest beta driver, before anyone mentions.
I have tried many times to load Debian on a new HD without any success. I used bittorrent to download it to my windows vista laptop and preceded to burn the image to a cd using Active@isoburner. But it only gets to where it says boot failure.
AMD 64X2 3800 CPU
1.5 G RAM
ASUS A8N5X MOTHERBOARD
ATI RADEON HD 545O GRAPHICS
HITACHI DESKSTAR SATA 500G HD
The installer for powerpc is broken in Squeeze. If yaboot is installed, it will break the whole boot process. I don't know exactly what goes wrong but it is a serious bug. I tried many times until I found out that yaboot is broken in Squeeze. In Lenny it still works luckily, so I could get something back after a complete sweep of my hard disk (the Lenny installer could not do anything with the ext4 partition of Squeeze as it is not supported in Lenny, so trying to put yaboot back did not work from there). Let this be a warning to people and a reminder for developers that there is a serious bug in yaboot.
View 2 Replies View RelatedI recently upgraded this machine from Ubuntu Maverick 10.10 to Debian Squeeze, x86_64, by wiping the root partition (I kept my backup and my home partitions). Everything has gone OK except this: for whatever reason I cannot pair my Microsoft Bluetooth Notebook Mouse 5000 with this machine any longer. In bluetooth-applet I can see the mouse when I go to pair it with the machine, but it simply times out and the pairing fails.
The target mouse definitely used to work in Ubuntu, so I doubt it's a problem in the physical layer. I tried another Bluetooth mouse (a Rocketfish/BestBuy POS), and it doesn't pair either. The Microsoft mouse I would like to use pairs just fine with my Debian squeeze laptop, but they're not using identical Bluetooth adapters as far as I can tell. lsusb reports that I've got a Broadcom BCM2210 in my workstation (the subject of this post), and lsusb on my laptop reports some kind of Broadcom Bluetooth adapter, but doesn't report its chipset.I'd really like to stay on squeeze if possible, but my googling for this has only led me to old documentation, or stuff that applies to wheezy or sid.
'rolling' release as redoing install /upgrade every 6 months is getting 'old' My machine is triple boot
Hard drive is 320 GB
Windows 7 - 167 GB
Ubuntu - Maverick - 73 GB
Ubuntu - Natty - testing version - 65 GB
I do not want to screw up my 'grub' as it's been trashed a couple of times recently and had to re-install everything, which went great with install setting up partitions. I am not sure where 'grub' is installed to. I did install Windows 7 first then let installer split hard drive in half to put Ubuntu on then while installing my second Ubuntu, I let installer split the Ubuntu partition in half, hence the 167 GB Windows and the 2 smaller partitions for Ubuntu.I was thinking to maybe let Debian install over my Maverick install. Would that work and not mess up my Grub and cause me to not be able to boot and have to fix the drama?
I recently purchased a new Lenovo Thinkpad T420i and am having problems installing the latest version of Squeeze from CD. After receiving the laptop, I started it up, configured Windows 7, and confirmed everything is working correctly. Next I went through the Debian installer, which completed successfully. I'll be dual-booting Windows 7 and Debian, so at the partitioning stage I resized my NTFS partition, added a shared VFAT partition, then used the "Guided" install to create my root and swap partitions. My partition layout is code...
I assumed something was wrong with grub, so I booted the CD into rescue mode and chose to reinstall grub onto the Master Boot Record. But nothing changed. Just to experiment, I went into fdisk, deleted all my new partitions (leaving just the Windows ones), and tried rebooting, but the same error happened. I then went through the Debian installer again, being careful to set everything up correctly, but still, the device won't boot.
I'm not even getting to the grub boot screen, so something is wrong even before the point. Reinstalling grub to the Master Boot Record (grub-install /dev/sda) isn't changing anything. How can I troubleshoot this?
For several days I stuck on a problem despite my various searches on the net. I just installed a machine in RC1 Squeeze.
My Partitioning
Disc 1
/ boot RAID 1
/ swap RAID 1 and encrypted
/ RAID 1 and encrypted
[Code]....
Lately I'm encountering a somewhat annoying malfunction: almost every boot, my desktop is stuck, HD red led is constatnly on, and i get a message from kerneloops that I had a kernel failure. I can move the cursor a little and slowly or not at all. Few violent reboots and I get a clean boot. Running Debian Lenny kernel 2.6.26-2-686 on a Pentium 4 2.0 GHz with 250 MiB ram.
View 4 Replies View RelatedResently I installed OpenSUSE 11.1 including XEN as I planned to use virtual machines. XEN item appeared in GRUB boot menu along with other items (OpenSUSE, windows...).I was instructed to boot XEN in order to use virtual machines.During boot, XEN was examining my disks and partitions, and when it reached CD and DVD drives, seemingly it went into infinite loop between the two drives. Finaly the screen went dark, and I have to make hard reboot. How can I work around this problem?
View 3 Replies View RelatedSo, I installed AGAIN Squeeze
And again boot fails
Now it shows error 15
I tried booting into a LiveCD (ubuntu) to see what is happening
But I can't open grub.cfg file (you're not the owner, it says)
What do I do to boot into my new squeeze?
Is usplash supposed to work? It hasn't worked correctly in squeeze (for me) for some time. It appears for like 2 seconds never to be seen again. And I never see it at shutdown. I tried splashy, but no splash. Plymouth has been no go with nVidia cards. I don't know if that's changed, but I get no splash with that either. usplash doesn't seem to be in the sid repos. Is it obsolete, or just not packaged yet?
View 5 Replies View RelatedI've been running squeeze for a couple of weeks now, no problems, just some minor sound issues but that is not important ATM.Everything was working fine until this morning i guess, the boot process goes as normal but at one moment it just freezes for no apparent reason it just says Starting K Display Manager:kdm. Has anyone experienced this problem before, or has a solution?
View 3 Replies View RelatedI tried to intall DEBIAN on a P6 machine(Power 570 processor)'s LPAR. Using debian-504-powerpc-DVD-1.iso from http://cdimage.debian.org/debian-cd/5.0 ... c/iso-dvd/I used "install64" option and it completed normally. All using default/recommended options during the installation. i.e. whole disk, one filesystem, etc.However, after the installation(seemed succesful), I got the following error during reboot."root=/dev/sda2:2,/vmlinux: Unable to open file, Invalid device"
View 1 Replies View RelatedMy laptop died while installing F12, without completing installation. Now I can not boot the computer from HD, CD, or USB. I have flashed the BIOS with the most recent ROM. I can access the BIOS setup and exhausted all my options there, which is mainly boot order. At the moment, the boot process goes to a blinking cursor and does not allow for input. The laptop in question is a lenovo Y510 that was previously running F10 with a single partition.
View 2 Replies View RelatedI downloaded Fedora 15 Live and Fedora 14 Live to try to see where Linux is for music and broadcast audio on a laptop. It turns out I have to use 14. 14 and 15 both sort of work as live out of the box, although why they ship with the common Broadcom wifi driver missing and the touchpad tap disabled beats me. I also never found the magic button to close down 15. There must be one, but blow me I couldn't find it. Then I tried to follow the instructions at [URL] which mostly seemed to work. I need to keep Win 7 as this is the 32-bit test machine. I used EasyBCD v2.1 rather than the older version the guide is written for.
Booting into Win7 at first worked, then a boot into Linux stopped at a line that said something about a kernel thread helper Then Win 7 blue screened on boot, although it would boot to Safe Mode. Removed Veriface from the Lenovo laptop and it would boot Win 7. Tried setting Drive in EasyBCD to "Boot" rather than "C:" for Fedora. Now booting Fedora gave a Windows missing file message and croaked. Repairing startup with the Win 7 boot CD cured Win 7. Repeated the loop with the same failures. Re-partitioned and re-installed Fedora and just the same - a screen of text that stops. I can now boot to Windows and need help to sort out the Linux boot. How do I start to investigate the screen of text saying things like "__bad_area_nosemaphore" ?
When I install either desktop version of Ubuntu 9.10 or Xubantu 9.10 it boots ok when ask to reboot at the end of the install, but will not reboot after that (2nd attempt and all after fail)On 2nd and later attempts the grub menu comes up and I choose default Ubantu and the Ubuntu circle logo displays for about 30 seconds, and most of time I see it try to access my floppy drive (sometimes the floppy drive light stays on, sometimes it does not) a cursor then blinks in the upper left hand corner for about 10 seconds and then the screen goes blank and freezes there until I power down.
My System
Dell Dimension 2350
Celeron 1.80 G Hz
768 Meg RAM
30 Gig hard drive
Note: Xubantu installs OK to HD on another system I have, but not on this Dell. To test the Dell I did install Puppy Linux with default grub loader to HD ant it works OK (boots OK to HD each time).Side note: At first I tried this Dell to set up dual boot with XP and Ubantu and same symptoms Ubantu only booting OK once and then never again so I thought it was dual boot issue so I deleted all partions (XP is now gone) with latest GParted version and attempted installing Ubuntu 9.10 and then Xubanto 9.10 on the whole harddrive but still no boot past the first time I though this might not be a grub issue since it seems to get past grub and the Ubantu circle shows for about 30 seconds before the system freezes. only a guess on my part as I don't know enough about Grub or Ubuntu to troubleshoot without help. I see I can hit "e" to get to the grub editor and I looked at the grub boot code but don't enough about it to edit for a fix. I thought about Lilo but did not see an option on the normal Xbuntu ,or even when I used the alternate install CD,for a Lilo option. Also note I can run the live CDs for Ubuntu and Xubuntu OK on this Dell. Only HD install gives me problems.
on my pc, that was running WinXP, I thought of installing Ubuntu. (I did install linux already a few times in the past years and use it on another couple of pcs) But something went wrong. This machine has 2 x 200MB maxtor drives, in raid 0 configuration, supported by the motherboard Nvidia chipset, and working well in Windows. When ran the live Ubuntu 10.04 cd, gparted was not able to access the drives in raid configuration, until I installed the mdadm and kpartx packages then the existing data became visible. So after that initial moment I thought all was ok and proceeded to install Lucid on the machine, dual booting with Windows. I did partition manually so that in my 400GB raid drive there is an 80GB NTFS partition with WinXP, a 90GB extended partition for Linux Ext4 and Swap and then a last NTFS 200GB partition for data. All went well, but now on restarting the computer nothing happens, nothing loads, Grub is not showing, and it looks like I cannot launch Linux nor Windows. All the data from WinXP and the Ubuntu installation seems to be on the disks but the pc is just not booting. I suppose the problem is with the raid configuration that is not handled properly during the installation, but is there anything that I can do now, apart from reinstalling Windows Xp or installing Ubuntu in a non raid configuration?
View 9 Replies View Relatedhow to install Dropbox for Debian Squeeze from source.Please read everything before you begin. I prepared it as I installed Dropbox for my own system. Please Note: I use sudo, you may have to use root or 'su' from the command line. If you don't know the difference between sudo and su, then you shouldn't try this until you know. At the time I did this, the lastest dropbox version was 0.6.7.
View 7 Replies View RelatedI was finally able to install Fedora 11 x64 after choosing to only install packages from the repository on the install DVD. Prior to that when I had chosen tio install from the default online repositories, the install itself failed with a Python exception ( see my other post ). Now, however, once I boot after the install I eventually receive a kernel panic message, and failure. The exact same thing happened with CentOS 5.3 x64 after a flawless install. So unless someone knows what might be going on I will assume that Fedore, Red hat, and offshoots for x64 bit systems are just not for me. I have been able to successfully install the latest Mandriva and SUSE x64 Linux distros so whatever Red Hat/Fedora has done just does not work on my system.
View 3 Replies View RelatedRecently, I had to switch harddrives on one of my servers due to the need for hardware.
However, when I switched back to the original harddrive I got a surprise : Instead of booting normally in OpenSuse 11.3, it booted in the grub shell.
I did a root ( hd0,1) but when I attempted the setup cmd it failed. Thinking that I probably was a configuration error ( nothing was changed - the drive had spent some time in a nice anti static bag ) I booted using a USB key.
To my surprise I got a message stating that parted couldn't read the other partitions ( boot and swap ) and hence I would not be able to edit then. Fortunately, the data partition seemed OK so I can backup the data.
Preferbly, I would like to be able to restore my original system.
After buying a new PC, I decided to "reorganize" my former PC as follows:Initially it has been a dual (SATA) disk dual boot PC- one disk for each OS, while XP was fully installed on a single NTFS partition. Using Gparted I shrunk the XP partition, and created some Linux partitions. I've verified that the XP partition (sda1) is bootable. Afterwards, I removed the other (former Linux) disk from the computer. While doing so, I had to temporarily disconnect cables from both drives. Finally, I fresh installed Mint 9 (Ubuntu 10.04 derivative), on my pre-prepared Linux partitions. Installation completed flawlessly, and during the install, I've noticed that GRUB2 has been installed on sda. Rebooted and got "Disk boot failure" error.
I've checked the BIOS and noticed that the (single) drive was not recognized.
I manually tested from the BIOS and located the drive as IDE3. Saving the new configuration (F10) and rebooting- the HD gain is not identified (the CMOS battery is fine- keeps time).
Booting a live CD I can see and access all above partitions.
How do I install an additional kernel in Linux Ubuntu 10.10, in case of a boot failure? Also how do I make the Grub Menu Visible, so that I am able to select multiple kernels. There is an older solution below, but is there a way to do this in Linux Ubuntu 10.10. I just suffered an update failure, possibly due to a corrupt kernel upgrade, which made my system unbootable. The cursor just flashed continuously.
Solution of 2007[URL].... "The next obvious rescue aid is to always have a working kernel installed. I usually work from a kernel updated via yum. Kernels have occasionally been released with flaws that have caused one or more of my machines to not boot. To this end, I always make sure I have at least one perfectly running kernel on a machine. A great way to handle this is to first add plugins=1 in your /etc/yum.conf file. The next step is to take this script (written by Jeremy Katz from Red Hat) and save it as n-installonly.py in /usr/lib/yum-plugins. You can change the number of kernels to retain on the system by changing the tookeep variable (default = 2).
With a known working kernel on your system, you can upgrade safely. If the new kernel is hosed, simply boot the old kernel to solve the issue with the new kernel be it to remove it, recompile it, or update it."
I'm using Debian Squeeze on my Presario CQ40-115AU. Whenever Squeeze finished boot (when the login screen appears), there a loud beep sound come out. The same sound also come out when rebooting/shutting down my laptop and this had never happened when I'm using Lenny. Where can I configure so the sound won't come out ever again.
View 2 Replies View RelatedAfter doing a dist-upgrade today, my one year old install of squeeze will no longer boot. It stops with a black screen and has to be hard reset. Cant even get to tty1. The last line in dmesg is: cfg80211: Calling CRDA to update world regulatory domain
mike@vaio ~ $ lspci | grep Network 06:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100.Just wondered if anyone has any ideas before I restore from a backup?
Whenever I reboot, I get GRUB and the _ pinking, and that's it. With rescue cd I can have chroot shell, to troubleshoot I did the upgrade-from-grub-legacy and installed it to both /dev/sda and /dev/sdb In recovery I redid the upgrade-grub and grub-install commands but still have the same "GRUB and _ blinking".
Because the text "GRUB" and then nothing I didn't enouncter while googling, I need to ask here for further troubleshooting.
I tried installing a live version of Debian Squeeze 6.0.0 for the i386 architecture. I am using a first generation MacBook Pro (Intel Core Duo, not Core 2 Duo).
I managed to boot the live cd and install everything using the "guided installation" option, using the whole drive for Debian (I don't have the Mac OS X Snow Leopard disc so I just wanted to install a strictly Debian system). I installed GRUB to the master boot-record, but after finishing the installation and rebooting I was confronted with the dreaded "question mark". After doing a bit of reading, I found that I should have installed the EFI LILO bootloader to the MBR instead of GRUB, so I reinstalled everything, choosing this option instead. But that didn't work either. More question marks. I imagine I must have to configure either of these bootloaders in the shell, but I don't know how to go about doing this.
How to do this without using a Mac OS X installation disc.
i'm used eeepc here the situation i've already install squeeze AMD64 KDE but i want to try using i386 gnome which is more friendly for my eeepc spec. problem is there other boot in my pc. i'm currently using win7, ubuntu 10.10 32 gnome, and ubuntu ultimate 64 gnome and i don't have external HDD.
Question is i want to remove all linux OS and keep my win7 is it ok if i'm using Gparted to delete all linux OS and then installing deb squeeze i386. my next project is to build portable server on eeepc.
Before I ask I know what I'm asking is not recommended.
On Lenny It was possible to change the boot login to permit logins as root
I can't find how to do that since I installed Squeeze.
I've installed 6.0.1a on my xi3 box [URL] and it works great. However when I remove the monitor and keyboard it doesn't boot (I don't know how far it gets, there is no monitor...). I did not install, and do not want, any kind of GUI interface, command line only. This is going in a closet as a solid state rsync backup repo. I have another small system (not this exact one) running Lenny that runs just fine headless - is this some kind of Squeeze regression? Is there any way I can get this running headless (I can't run Lenny on this box because I don't think the Marvell GbE driver is there or is working in Lenny.
View 7 Replies View Related