| Thread Previous • Date Previous • Date Next • Thread Next |
When I choose kernel 3.2 in grub I'm dropped in Busybox shell. If I enter 'dmraid -ay' and 'exit', then normal boot procedure continues. W Op 12-03-12 14:19, Wouter van der Graaf schreef:
Mine is a VPCZ13. Don't know how much difference there is between Z11, Z12 and Z13.While I experience trouble with the 3.2 kernel in 12.04, Craig tells me he's running the 3.2 kernel in 11.10 without problems (even more stable than before).So it seems for Shannon and me that the combination Ubuntu 12.04 and kernel 3.2 is problematic.Kind regards, Wouter Op 12-03-12 14:03, Frederik Questier schreef:Hi, I have a similar, albeit slightly different experience: On my VPCZ1 (VPCZ11X9E, after hacking the bios to static switching, stamina) (K)ubuntu 11.10 installed nicely and everything tested (*) works nicely, with that kernel: 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 But after "apt-get upgrade" and reboot, the screen is black on kernel 3.0.0-15-generic. Selecting 3.0.0-12 in grub boot menu still works flawless. So, I combine this experience with the others ones in this thread, it gives this strange pattern: 2.6.38-11-generic-pae works on VPCZ114GX 3.0.0-12-generic 64-bit works on VPCZ11X9E 3.0.0-15-generic 64-bit fails on VPCZ11X9E 3.0.0-16 works for Wouter van der Graaf 3.2.0-18-generic fails on VPCZ114GX Could it be an (another) upgrade problem instead of a kernel problem? (*) tested to work: - Stamina graphics 1600*900 - VGA out - Sound - Wireless - 1gbit/s ethernet - SD card reader - Sleep, hibernate and resume - Brightness keys - Touchpad - echo 1> /sys/devices/platform/sony-laptop/kbd_backlight Kind regards -- Prof. dr. Frederik Questier Vrije Universiteit Brussel http://questier.comOn Mon, Mar 12, 2012 at 10:06 AM, Wouter van der Graaf<wouter@xxxxxxxxx> wrote:Hi,Same problem here. I upgraded 11.10 to 12.04 and exactly the same error,dropping me in a BusyBox shell. Luckily I still have the 11.10 kernel 3.0.0-16, so booting with that kernel solves it for now.So it seems there's a regression in the 12.04 kernel. Does anyone recognizethis issue? Any suggestions on how to find the cause? Thanks! Wouter Op 10-03-12 05:33, Shannon VanWagner schreef:Hi, I hope this is the right place to ask for help..I've been using Ubuntu 11.10 GNU/Linux on my Sony Vaio VPCZ with success- I wrote up the few steps I took to make it work for me at: http ://linux-on-sony-vaio-z.wikispaces.com/VPCZ114GXBut now, I've i3.2.0-18-genericnstalled Ubuntu 12.04 and it won't boot... Can't find the root device at /dev/by-uuid (nothing shows up in there), then drops to busybox. I've tried a rootdelay=160 and that doesn't help. I also tried replacing the UUID with the path to /dev/mapper/isgwXXX-blah-blah but nosuccess. What's crazy is that the Ubuntu 12.04 runs perfectly on this computer from the LiveCD, that's how I installed it on here. Would be nice if Ubuntu did some kind of sanity comparison check between the running LiveCD system and that which gets installed. One thing I did noticethat is weird though is that the partitions in /dev/mapper/isgwXXXXX arelisted twice in the 12.04 installer.. This is different then when installing 11.10 - where there's only one set of partitions listedthere. I made sure to install the grub on the base /dev/mapper/isgwXXXX- blah device so I don't think it's a grub problem. And when I inspect theUUIDs of the drives in the installed grub.cfg - they match to those listed for the partitions when I run the LiveCD.So here's how I'm booted into this system now... I went and reinstalledUbuntu 11.10 to my separate root partition, then I copied over the /boot/initrd.img-3.0.0-12-generic to my separate /home drive that has been preserved the whole time. I then reinstalled 12.04 to my root partition, backed up initrd.img-3.2.0-18-generic, copied initrd.img-3.0.0-12-generic with a rename to /boot/initrd.img-3.0.0-18-generic and the system now boots. There aresome error messages from the land of /lib that show during startup, andsound doesn't work, but the system boots and that's how I'm submitting this. So.. is it a initrd.img-3.0.0-18-generic problem that's causing my Ubuntu 12.04 system to not be able to see the root device on boot andthus dropping me to busybox instead, or what? If so, how do I fix this?I get the feeling that using the initrd.img-3.0.0-12-generic with the 3.0.0-12-generic kernel is causing my sound not to work.. and I'mthinking when I get a kernel update I'm going to be whacked back to not being able to boot... So does anyone have any suggestions? This is a newhorizon for me. I love this stuff. And, I love all of you for the awesome things you do for this awesome OS.. Thank You! and Thanks for any help you can provide!-- Wouter van der Graaf entreprogrammeur and senior web developer d y n o r a web developers ~ both ends technology, interaction and aesthetics +31 (0)6 2893 0615 | wouter@xxxxxxxxx Burg. de Bruïnelaan 95 | 3331 AC Zwijndrecht | NL +31 (0)78 843 3139 | contact@xxxxxxxxx | www.dynora.nl _______________________________________________ Mailing list: https://launchpad.net/~sony-vaio-z-series Post to : sony-vaio-z-series@xxxxxxxxxxxxxxxxxxx Unsubscribe : https://launchpad.net/~sony-vaio-z-series More help : https://help.launchpad.net/ListHelp
-- Wouter van der Graaf entreprogrammeur and senior web developer d y n o r a web developers ~ both ends technology, interaction and aesthetics +31 (0)6 2893 0615 | wouter@xxxxxxxxx Burg. de Bruïnelaan 95 | 3331 AC Zwijndrecht | NL +31 (0)78 843 3139 | contact@xxxxxxxxx | www.dynora.nl
| Thread Previous • Date Previous • Date Next • Thread Next |
