Latitude 3540 Freezes During Upload

[Clifford Raymond]

[ATTACH=full]1718[/ATTACH]

[url=“/_imported_xf_attachments/1/1717_IMG_1585 copy.jpg?:”]IMG_1585 copy.jpg[/url][url=“/_imported_xf_attachments/1/1718_IMG_8121 copy.jpg?:”]IMG_8121 copy.jpg[/url]

[Clifford Raymond]

[ATTACH=full]1719[/ATTACH]

[url=“/_imported_xf_attachments/1/1719_IMG_8416 copy.jpg?:”]IMG_8416 copy.jpg[/url]

[Clifford Raymond]

[ATTACH=full]1720[/ATTACH]

[url=“/_imported_xf_attachments/1/1720_IMG_1585 copy.jpg?:”]IMG_1585 copy.jpg[/url]

[Joseph Hales]

Have you tried updating the kernel I try several and save them with a unique name that I specify in the host record for testing to avoid issues with other working systems.

[Clifford Raymond]

So I’ve been trying to update the kernel but I really confused on which version I should get. Any idea on which version number would work best in my situation?

[Tom Elliott]

As you’re running 0.32,

I’d recommend getting the new kernel as such:

[code]sudo wget http://mastacontrola.com/fogboot/kernel/Kernel.TomElliott.3.19.0.32 -O /tftpboot/fog/kernel/bzImage[/code]

[Joseph Hales]

I generally get the latest ks or kitchen sink version when running .32 but I just saw Tom’s reply go with his for sure.

[Clifford Raymond]

Thank you so much for your help but now I get a message that says “Invalid or corrupt kernel image. boot:” I also made sure that the bzimage was not duplicated. The previous version is saved in different folder on the desktop.

[Sebastian Roth]

Sounds a bit like the file is corrupted. md5sum??
[CODE]$ md5sum Kernel.TomElliott.3.19.0.32
1c47679f256378dee6a673d20e766d31 Kernel.TomElliott.3.19.0.32[/CODE]

If you see a different md5sum you should re-download it. If you see the same it might be broken on the server (corrupt upload)…

[Clifford Raymond]

You are correct, I do see the same message. What does it mean when the file is corrupt? Do we have to reconfigure the whole server?

[Sebastian Roth]

[quote=“Clifford Raymond, post: 43552, member: 28730”]You are correct, I do see the same message. What does it mean when the file is corrupt? Do we have to reconfigure the whole server?[/quote]
What do you mean by “same message”??? Does the kernel image have the same md5sum??

[Clifford Raymond]

yes it does.

[Clifford Raymond]

Should I reconfigure the whole server?

[Tom Elliott]

I’m confused.

What has been tried?

You’re using a different kernel? If so, you shouldn’t be seeing anything about uvesa_fb or more than 8 outputs detected.

[Clifford Raymond]

I’m using the kernel that Tom Elliot suggested. After using that kernel I got the message “Invalid or corrupt kernel image. boot:” Uncle Frank ask about the md5sum and we were just confirming that we did get the same response that he stated above. At the moment we still can’t upload an image and now are more confused than ever. We are not really sure what direction we should be going so any advice would greatly be appreciated.

[Tom Elliott]

Well I am Tom Elliott.

When you first tried did you try the Kernel.TomElliott.3.19.0.32 or the Kernel.TomElliott.3.19.0.64

If either one or the other, can you try the :
Kernel.TomElliott.3.19.1.32 (if you’re still running 0.32)

[Clifford Raymond]

We tried both and neither one worked.

[Clifford Raymond]

Is there anything else you would suggest?

[Tom Elliott]

Not to sound crude or anything but I think we need more details than just it didn’t work can you provide a screenshot of trying to boot using one of Lee’s kernels or even a video?

[Clifford Raymond]

This is the first part [ATTACH=full]1794[/ATTACH]and this is the second part
[ATTACH=full]1795[/ATTACH]

[url=“/_imported_xf_attachments/1/1794_Screen%20shot%202015-03-18%20at%2010.22.31%20AM.png?:”]Screen%20shot%202015-03-18%20at%2010.22.31%20AM.png[/url][url=“/_imported_xf_attachments/1/1795_Screen%20shot%202015-03-18%20at%2010.25.42%20AM.png?:”]Screen%20shot%202015-03-18%20at%2010.25.42%20AM.png[/url]