Latitude 3540 Freezes During Upload
-
[quote=“Clifford Raymond, post: 42764, member: 28730”]I have a latitude 3540 that is running on Win 7 and the server is running on Ubunto. We are running FOG .32 and every time I try to upload an image it freezes. We have restarted the server a few times with thinking that either an image was “stuck” or something else was processing and causing the issue. We read through many threads and thought it could be a kernel issue but no one has stated how to fix it on Ubunto only on Windows.[/quote]
There may be a solution to your problem (I wouldn’t know it, that’d be up to a more experienced FOG user), but have you considered upgrading to the latest release or a solid development version?
-
Yes, it is something we are planning on doing but cannot do at the moment. Thanks for your response.
-
Wayne is right. You’re probably better off upgrading. But for the time being we can still try to nail this issue down. But you’d have to be more specific! There is no way we can help you with such little information on when things go wrong…
[quote]every time I try to upload an image it freezes[/quote]
What’s the last thing you see? Any error messages? Freezes always at the exact same time? -
I have the same model and we don’t have any issues under SVN 2952 but as you can’t upgrade that doesn’t help you much pics or a video of where it happens would help a lot.
-
[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]
-
[ATTACH=full]1719[/ATTACH]
[url=“/_imported_xf_attachments/1/1719_IMG_8416 copy.jpg?:”]IMG_8416 copy.jpg[/url]
-
[ATTACH=full]1720[/ATTACH]
[url=“/_imported_xf_attachments/1/1720_IMG_1585 copy.jpg?:”]IMG_1585 copy.jpg[/url]
-
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.
-
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?
-
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]
-
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.
-
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.
-
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)…
-
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=“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?? -
yes it does.
-
Should I reconfigure the whole server?
-
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.
-
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.
-
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)
