aMule Forum
English => en_Linux => Topic started by: Stu Redman on March 21, 2010, 02:31:13 PM
-
Well, I tried to upgrade my Ubuntu Karmic to Lucid beta (which I will call "Lousy" from now on) today. Ok, I expected this to take a while. After returning it had opened a Grub configure dialog asking for harddisks where it should be installed, nothing preselected (hello ? why not install it where it had been ?). I selected /dev/sda1 and was rewarded with " the symbol 'grub_puts_' not found" after reboot. Duh.
I got the Lousy disc and booted from it (to a shell prompt, duh me to expect more). With some googling I managed to reinstall grub (to sda instead of sda1). It reported a zillion fopen errors and then said "everything ok" or something.
After reboot I got some more error messages, then a boot screen "Ubuntu 10.04" with 4 blinking dots below. Still blinking, as I've finished typing this nothing more (well, it activated a screensaver meanwhile).
Man, am I delighted. I expect some quirks from a beta, but not a total loss. I will mow down the (virtual) disk image now and try to reinstall Lousy from scratch. See if that works.
Why am I typing this? As a warning for those who considered trying the beta, and as good laugh for the others.
-
Well, Debuian testing can be considered beta, too. I spent the last 2 days now with getting the system running again, after I ran fsck on my ext3 fs, which moved ~300 blocks to lost and found. When booting, it told me the disk is readonly. With init=/bin/bash, mount told me rw, but running any command gave me again readonly. With KNOPPIX, some dpkg and awk magic, I just have to recreate the symlinks for lilo, install the kernel-packages and the nvidia module. I don't know what exactly happened, but I want to warn anyone, that a disk that runs flawlessly for 1,5 years now, should be fsck'ed just for fun.
-
After upgrading VirtualBox to 3.1.6 (and installing 300+ MB of updates) I got it finally running.
Lousy feature of the day: I had to dig in the gnome registry editor (gconf-editor /apps/metacity/general/button_layout) to move the window buttons back to the right where they belong. ::)
-
Nice, I just created a virtual device for alsa, because I can't use amarok with output over libxine and xine in parallell, so created a dmix enabled virtual device that just forwards it to the real alsa-device. Beside the fact, that this is a base functionality and neither xine nor pulseaudio nor jackd nor gstreamer can make use of this if not explicitely activated (like alsaplay -d:dmix), the initscript just inserts the right modules and sets some basic config options on the devices but isn't able to redo so or unset them. So long story short: I had to reboot.
-
You mean, we all have our little problems and I shouldn't bother you with mine... ;)
-
No, thought you're saerching the fuckup of the day. And the last two weeks I had almost everyday such an experience. And it's always good to see that you're not the only one who finds problems noone complained already about. I, for myself, am very happy to be not the only one that has everyday problems that look simple, everybody thinks that should work out of the box and makes me googling and testing for days.
-
http://thedailywtf.com/Articles/That_is_Off-Limits_As_Well.aspx
-
More fun with it. >:(
Installed Kubuntu Lousy today. Runs through, reboots, login screen. I log in, flicker, flicker, login screen again (http://newyork.ubuntuforums.org/showthread.php?t=1462745). I log in in console, get 250MB updates, reboot, same. Build Vbox guest additions in console, reboot. Kubuntu screen, Window enlarges, flicker, flicker, shrinks again, black window. Console login still works, but that's not entirely satisfying.
I'm suspecting the Oracle guys who own VirtualBox now have fucked up. Maybe I'll take another look at VMWare.
-
Sounds a bit as if your X11 configuration is faulty. But in such a case you shouldn't even get to the login screen, so I am not sure about it. Perhaps you could try "xorg -configure" and set a different resolution/bitrate/frequency.
-
Switched to VMWare, and that works. As long as you don't put the host computer into standby which kills the network. >:(
-
I use QEMU, but that's not for Windows.
-
You might try VirtualBox, which is available for Windows too.
-
Marcell, he's been using VirtualBox until now. Read more carefully ;)