You can also get a shell by booting off the kubuntu install CD (make sure its amd64 if you did the amd64 install), manually mounting your disk say as /a, and issuing a "chroot /a /bin/bash" Hopefully you just messed up fstab :) Rohit David A. Desrosiers wrote: > >> the kubuntu initial splash appears and the list of loading stuff >> scrolls on the botton. Shortly after it states "starting network..." >> the screen changes to a similar kubuntu splash with the blue progress >> bar under it. That's it!!!! No more, no less, NADA! > > Edit grub, (hit 'e' then 'e' again at the grub menu), and add > 'vga=0 init=/bin/bash' to the kernel load line, then 'b' to boot that > entry. > > It should give you a shell, where you can then edit your fstab and > check your disks and such to make sure things are intact. Roll it back > to a pre-edited state and see if you can get it booting. Once that is > done, try booting up as normal and fix from there. > >> I know this is a rather open ended questions but the startup process >> seems so different that what I am used to (SUSE, RH and AIX) that I >> am stumped. > > Did you add any hardware? Can you be sure your motherboard and > power lines (from the PSU) are not overloaded with too many devices on > one line and not enough on the others? Everything seated properly? > > In my experience, things like this are generally due to simple > "out-of-band" errors like something vibrating loose or some easy to > fix problem. > > Can you verify that the system works by booting up to a KNOPPIX cd > or dvd? That would at least eliminate most of the hardware as being > damaged in anyway, so you can then explore local configuration changes > that may need to be adjusted. > > Start with the basics and work your way up from there. > > > David A. Desrosiers > desrod at gnu-designs.com > http://gnu-designs.com
More information about the ECLUG mailing list