FAQ   Search   Memberlist   Usergroups   Register   Profile   Log in to check your private messages   Log in 

THIS FORUM IS NOW CLOSED FOR ALL NEW POSTING. PLEASE GO TO THE NEW PSUBUNTU FORUMS TO POST NEW TOPICS.

This forum will still be available and searchable, but no posting is allowed. We encourage all users to sign up for an account on the new forums.

You can help us maintain valuable information from this forum by copying it over to the new forums or adding it to the PSUbuntu Wiki.

Fixing the 2.10 crash
Goto page 1, 2, 3, 4, 5, 6, 7  Next
 
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies.    PSUbuntuForums Forum Index -> Network & Connectivity
View previous topic :: View next topic  
Author Message
AliasXNeo



Joined: 31 Dec 2007
Posts: 11

PostPosted: Tue Jan 01, 2008 6:02 am    Post subject: Fixing the 2.10 crash Reply with quote

Well I'm not too sure where this post belongs so feel free to move it mods.

Anyways, I'm sure many of you who have followed this post are now experiencing problems with loading it up. The problem is described below:

Quote:
When I get to kboot and try to run Ubuntu it says it's starting but then completely freezes


If you're not experiencing this problem then this solution is not for you.

Now, I myself am a complete noob to Linux and therefor I felt writing this guide as a noob might help the other ones out there get this fixed. The process is actually pretty simple but requires that you have the following:

- A computer with internet access
- Some kind of storage device (USB, flash, whatever)
- An archive program like WinRAR
- A brain

If you have these then you're ready to begin.

Notes:
- To start up Ubuntu without freezing at the kboot screen type in 'old' then press enter. This will load up the old kernel.
- When using 'sudo' commands the console will ask you for a password. Enter the password you use to login with. When you type you will not see any characters, don't worry it's supposed to be like that. Just type your password in and hit enter. You should only have to do this once.

Step 1: Downloads
There are only 2 downloads:

An ISO file with a kernel fix: Download
The latest version of rpm2cpio: Download

Step 2: Gathering required files
Once you have the above downloaded use a program such as Winrar to look inside of the ISO file (for Winrar just right click, open with, Winrar). You'll want 2 files out of here. Navigate into the 'target' folder and extract the below two files to somewhere where you can easily access them (like your desktop)

kernel-2.6.23-20071219.ppc64.rpm
initrd.img-2.6.23

Now take the above two extracted files along with rpm2cpio-1.2_2.tbz and place them on something like a USB stick so that you can transfer them into the PS3. I'm going to assume you're using a USB stick. So go ahead and plug it in your PS3 (I had a 40gig which only has 2 slots so I just unplugged the keyboard since you'll need the mouse to move the files). Once you're plugged in you'll see a folder looking icon appear on your desktop. Double click this to open up a file browser and see the files on your USB device. Go ahead and drag all three files you added earlier onto your desktop and right click on the folder icon and hit eject for a safe eject (and plug your keyboard back in if you unplugged it). Now we're ready to start Smile

Step 3: Extracting the RPM file

Remember the rpm2cpio we downloaded earlier? Well as you can probably guess we're going to need it to extract the rpm file we now have. Go ahead and right click on the rpm2cpio-1.2_2.tbz file and extract it on your desktop. If you did it right you'll now have a folder called 'rpm2cpio-1.2_2' which contains a few files and another folder which has rpm2cpio.pl (the file we need).

Now I'm sure there's some more "pro" way of doing this, but seeing as I'm a complete noob with Linux this is the way I went about doing it. Go ahead and drag the rpm2cpio.pl file onto your desktop (this is where most of the work will be done since I find it's the easiest place). Now open up a terminal and run the following command:

Code:
cd Desktop
perl rpm2cpio.pl kernel-2.6.23-20071219.ppc64.rpm | cpio -idmv


Assuming you had the the pl and rpm file on your desktop as done earlier you should see a flow of text in the terminal window. Once it's all done go back to your desktop and you should now see three new folders:

test
boot
lib

Congratulations, you just extracted the rpm file Smile

Step 4: Copying the files over

Now that we have the files we need extracted it's time to put them in their proper place. There are two files in the boot directory we need to copy so using the same terminal do:

Code:
cd boot
sudo cp vmlinux-2.6.23 /boot
sudo cp config-2.6.23 /boot


Now for the image file:

Code:
cd ../
sudo cp initrd.img-2.6.23 /boot


We now have all the boot files done. The last files that need to be copied over are the modules:

Code:
cd lib
cd modules
sudo cp -r 2.6.23 /lib/modules


Now we have all the needed files copied over Smile

Step 5: Editing kboot.conf

Now to edit our kboot file. You'll want to open it with nano:

Code:
sudo nano /etc/kboot.conf


And at the very end of the file you'll want to add a line looking like this:

Code:
test='/boot/vmlinux-2.6.23 initrd=/boot/initrd.img-2.6.23 root=UUID=48124dc5-2c8f-43d0-a210-0b6549ffde56 quiet splash'


The only thing you'll need to change is the part after UUID= and before quiet. If you look about two lines above your new line you should see something like:

Code:
linux='/boot/vmlinux initrd=/boot/initrd.img root=UUID=48124dc5-2c8f-43d0-a210-0b6549ffde56 quiet splash video=ps3fb:mode:5'


Except the stuff after UUID= will look different. Copy everything from UUID= all the way to right before 'quiet'. Now go back to the test= line and replace everything after UUID= and before 'quiet' with the stuff you copied. Now save the file.

Step 6: The easy part

Now just run the below commands:

Code:
sudo update-initramfs -k 2.6.23 -u
sudo depmod -a


Finally, reboot your system. When kboot loads up instead of just pressing enter type in 'test' and then press enter. This will load up the kernel we just added, the fixed one. Now assuming everything went correctly Ubuntu should load up like normal.

And now you can finally go to your network connections area and you should now see Wireless connection instead of Wired connection. Just fill out the info and you should be back online Smile

Credits goto jms Smile Thanks.

If this is not working for you please try the steps below:
1. Log back into Ubuntu by typing in 'old' and pressing enter
2. Go into your file system and browse to the /boot folder (not the one on your desktop)
3. Verify that vmlinux-2.6.23, config-2.6.23, and initrd.img-2.6.23 are in this folder. (Make sure these files are valid. If you see a little sign above them it means it did not copy over correctly. See below for how to fix this)
4. Go back and now go into the /lib/modules folder and verify you see a folder called 2.6.23.
5. Now open up a terminal and edit your kboot.conf file (sudo nano /etc/kboot.conf). Make sure the last line looks something like this:

Code:
test='/boot/vmlinux-2.6.23 initrd=/boot/initrd.img-2.6.23 root=UUID=48124dc5-2c8f-43d0-a210-0b6549ffde56 quiet splash'


If one of your files did not copy (you see a little red icon above the file) then open up a terminal and do the following:
Code:
cd Desktop
cd boot
sudo rm /boot/vmlinux-2.6.23
sudo rm /boot/config-2.6.23
sudo rm /boot/initrd.img-2.6.23

sudo mv vmlinux-2.6.23 /boot
sudo mv config-2.6.23 /boot
cd ../
sudo mv initrd.img-2.6.23 /boot


Now reboot and try again (by entering 'test' at kboot and pressing enter)

And enjoy!

~ Alias


Last edited by AliasXNeo on Tue Jan 01, 2008 6:30 pm; edited 2 times in total
Back to top
View user's profile Send private message
jimohm



Joined: 01 Jan 2008
Posts: 3

PostPosted: Tue Jan 01, 2008 10:18 am    Post subject: Reply with quote

apologies if i'm being totally thick, but if Ubuntu fails to initially start up, how is the user meant to use the console in step 2 to copy over the various files and run commands? 'cos as you have said that the guide is for the following affected users:

'When I get to kboot and try to run Ubuntu it says it's starting but then completely freezes'

I faced the freexe issue previously also and would like to know how to fix.

Your guide is great apart from the thing above.
Back to top
View user's profile Send private message
tab



Joined: 11 Dec 2007
Posts: 6

PostPosted: Tue Jan 01, 2008 10:31 am    Post subject: Reply with quote

jimohm wrote:
apologies if i'm being totally thick, but if Ubuntu fails to initially start up, how is the user meant to use the console in step 2 to copy over the various files and run commands? 'cos as you have said that the guide is for the following affected users:


Can't the user just type in old and the kboot prompt to boot into an older kernel that does work?
Back to top
View user's profile Send private message
Tazman



Joined: 21 Dec 2007
Posts: 11

PostPosted: Tue Jan 01, 2008 12:16 pm    Post subject: Reply with quote

Hi!

This really seems to work. Now I am able to use Wi-Fi connection again, with Feisty and PS3 Firmware 2.10 Thanks a lot.

Next, I will try to update to Gutsy...
Back to top
View user's profile Send private message
StrikeEagle737



Joined: 31 Dec 2007
Posts: 15

PostPosted: Tue Jan 01, 2008 4:28 pm    Post subject: Reply with quote

Heeeeeellllllllppppp! I am getting stuck on Step 4. When I type in "sudo cp vmlinux-2.6.23/boot", it says " [sudo] password for strikeeagle737" and then I can't type anything! What the heck is going on? Update: I press enter and it lets me type. I type in my password and press enter but it says "Sorry try again". What do I do????? I'm starting to hate Linux. It is extremely complicated. I think I am doing everything right, but it always turns out wrong!? I am SOOO FRUSTRATED! Evil or Very Mad
Back to top
View user's profile Send private message
Tazman



Joined: 21 Dec 2007
Posts: 11

PostPosted: Tue Jan 01, 2008 4:55 pm    Post subject: Reply with quote

Quote:
When I type in "sudo cp vmlinux-2.6.23/boot"


Did you noticed that there must be space before /boot,
Code:

sudo cp vmlinux-2.6.23 /boot
Back to top
View user's profile Send private message
StrikeEagle737



Joined: 31 Dec 2007
Posts: 15

PostPosted: Tue Jan 01, 2008 5:16 pm    Post subject: Reply with quote

Yes, but it still says "[sudo] password for srikeeagle737" after I press enter. This is a "universal" problem with me- as in everytime I type in a command with "sudo" and press enter, it says "[sudo] password for srikeeagle737". I am going to make a separate thread for this.
Back to top
View user's profile Send private message
StrikeEagle737



Joined: 31 Dec 2007
Posts: 15

PostPosted: Tue Jan 01, 2008 5:46 pm    Post subject: Reply with quote

Nevermind, I got the problem solved! Very Happy
Back to top
View user's profile Send private message
AliasXNeo



Joined: 31 Dec 2007
Posts: 11

PostPosted: Tue Jan 01, 2008 5:55 pm    Post subject: Reply with quote

I updated the post to include notes on how to start Ubuntu using the old kernel and clarified what to do when it asks for a password. Glad to see it's working for you guys Smile
Back to top
View user's profile Send private message
StrikeEagle737



Joined: 31 Dec 2007
Posts: 15

PostPosted: Tue Jan 01, 2008 6:13 pm    Post subject: Reply with quote

This is not working for me! I did everything!! I type in "test" at kboot, but it won't load! Why isn't it working!? Crying or Very sad Evil or Very Mad Mad Is there any other linux os that I can fit onto a CD that is a LOT more user friendly?
Back to top
View user's profile Send private message
gyrene



Joined: 01 Jan 2008
Posts: 14

PostPosted: Tue Jan 01, 2008 6:22 pm    Post subject: Completed the steps but.. Reply with quote

I completed all the steps, and when I rebooted into kboot and typed test, it went into the ubuntu quiet screen, stalled for about 45 seconds, and then booted into busybox.

I rebooted again, and typed old, and then it said vmlinux.old wasn't found. I went into the directory, and found out that vmlinux.old actually didn't exist, so I tried to remount the /dev/ps3da1 directory, into read write mode, and that didn't work, because for some reason, it thinks the directory is supposed to be sda1. So, I tried to remount /dev/sda1, and that just said that it was busy.

So, with all these trials, and errors, aside from wanting to take the PS3 and throwing it out of the @#$^^ing window. Is there a way that I can get boot back into Ubuntu, without having to reinstall?
Back to top
View user's profile Send private message
AliasXNeo



Joined: 31 Dec 2007
Posts: 11

PostPosted: Tue Jan 01, 2008 6:32 pm    Post subject: Reply with quote

StrikeEagle737 wrote:
This is not working for me! I did everything!! I type in "test" at kboot, but it won't load! Why isn't it working!? Crying or Very sad Evil or Very Mad Mad Is there any other linux os that I can fit onto a CD that is a LOT more user friendly?


Look at the end of my post where it says "If this didn't work do this...".
Back to top
View user's profile Send private message
AliasXNeo



Joined: 31 Dec 2007
Posts: 11

PostPosted: Tue Jan 01, 2008 6:35 pm    Post subject: Re: Completed the steps but.. Reply with quote

gyrene wrote:
I completed all the steps, and when I rebooted into kboot and typed test, it went into the ubuntu quiet screen, stalled for about 45 seconds, and then booted into busybox.

I rebooted again, and typed old, and then it said vmlinux.old wasn't found. I went into the directory, and found out that vmlinux.old actually didn't exist, so I tried to remount the /dev/ps3da1 directory, into read write mode, and that didn't work, because for some reason, it thinks the directory is supposed to be sda1. So, I tried to remount /dev/sda1, and that just said that it was busy.

So, with all these trials, and errors, aside from wanting to take the PS3 and throwing it out of the @#$^^ing window. Is there a way that I can get boot back into Ubuntu, without having to reinstall?


I think the problem is that for some reason the cp command is messing up the files. I noticed when I tried to copy the img file over my first time that the file was not as big as the image file I had copied over and there was a red icon above the file. So I deleted it and used move instead and it fixed it. I think when you're booting into 'test' it's trying to use the messed up image which may be causing your problem. I don't know how you can get back in, but if you can then try using the solution at the end of my post (where I delete all the files and just move the other ones in).
Back to top
View user's profile Send private message
gyrene



Joined: 01 Jan 2008
Posts: 14

PostPosted: Tue Jan 01, 2008 6:39 pm    Post subject: Thanks Reply with quote

I believe, I have to reinstall. I tried everything I could think of, and I have searched everywhere, on how to edit the kboot.conf file, and tried to remount, and it's not working so I'll just reboot.

I'll let you know what happens.
Back to top
View user's profile Send private message
StrikeEagle737



Joined: 31 Dec 2007
Posts: 15

PostPosted: Tue Jan 01, 2008 6:52 pm    Post subject: Reply with quote

AliasXNeo wrote:
StrikeEagle737 wrote:
This is not working for me! I did everything!! I type in "test" at kboot, but it won't load! Why isn't it working!? Crying or Very sad Evil or Very Mad Mad Is there any other linux os that I can fit onto a CD that is a LOT more user friendly?

Look at the end of my post where it says "If this didn't work do this...".

Ok. It worked. It was able to sort of start up, but now it is hanging at some errors. I am having the same problem as this guy http://psubuntu.com/forum/viewtopic.php?t=571. I am going to see if I can figure out how to fix this based on the replies he got. At least I am one HUGE step closer to get this running again! Very Happy Very Happy Here is the best reply from the thread:
THis is what worked for me....

DK75 was asking the right questions but didnt quite spell it out. his quote

"
Boot up from LiveCD, go to upper menu "Aplications/Accesories/Terminal" and copy&paste result of operation:
Code:

sudo mount /dev/sda1 /mnt -t ext3 -o defaults
cat /mnt/etc/kboot.conf



moreover, copy&paste result:
Code:

sudo blkid /dev/sda1

"
What the first item does allow to identify what went wrong in the kboot.conf. THe wifi update everyone mentions above changes your root= from root= /dev/sda1 to root=uuid="bunchanumbersandletters"

I messed up by going into kboot.conf and changes this back from the uuid to the /dev/sda1. doing this gave the bootloader no access to the volume and kicked me to a nice initramfs mess.

after you mount your vol through the live cd, use the second command line"sudo blkid /dev/sda1" this will give you that uuid you need to replace on your kboot.conf.

changed it back and i was back into my os. with my wifi still intact.

reading this article helped me piece it all together.
http://psubuntu.com/forum/viewtopic.php?t=904

just search for "edit your kboot.conf again" for the section.

hope this helps.

How do I do this if I don't have the live cd? I have the alternate instalation cd.
Back to top
View user's profile Send private message
Display posts from previous:   
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies.    PSUbuntuForums Forum Index -> Network & Connectivity All times are GMT
Goto page 1, 2, 3, 4, 5, 6, 7  Next
Page 1 of 7

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group

Theme xand created by spleen.