Got it working with Tom’s 32 bit .config file using Linux 3.15.6 kernel, linux-firmware.git and added USB Mass Storage and SCSI Block Storage drivers, all that did the trick. Thank you all.
Latest posts made by Theodor
-
RE: Request for Help or maybe just answers
-
RE: Request for Help or maybe just answers
I did use 3.19 with Fog 1.2 but am now downloading 3.15.6. Will keep you posted on results.
-
RE: Request for Help or maybe just answers
UPDATE: I was able to video the sequence and there is an intial error that scrolls off before the above image:
/bzImage32… ok
/init_32.xz… ok
Probing EDD (edd=off to disable)… ok
[ 0.269404] Initramfs unpacking failed: no cpio magicDoes this help ?
-
RE: Request for Help or maybe just answers
I got the kernel re-compiled and ran a quick registration on the client in question and got this:
[ATTACH=full]1709[/ATTACH]
In the menuconfig I changed USB Mass Storage support from a “M” to a “*”. Is there another driver(s) I should be including ?
Thanks,
-John[ATTACH=full]1710[/ATTACH]
[url=“/_imported_xf_attachments/1/1709_IMG_20150223_161620.jpg?:”]IMG_20150223_161620.jpg[/url][url=“/_imported_xf_attachments/1/1710_IMG_20150223_162327.jpg?:”]IMG_20150223_162327.jpg[/url]
-
RE: Request for Help or maybe just answers
Ok… figured it out. Blond moment… was in the wrong folder trying to do the make. Doh…
I finally got the kernel made and in place when I got the “This kernel requires an x86-64 CPU, but only detected an i686 CPU.”
So I am now recompiling after using the ARCH=i386 commands instead.
Thanks.
-
RE: Request for Help or maybe just answers
Ok getting closer…
I followed the thread to rebuild the Kernel but hit another wall when trying to make:
make[1]: *** No rule to make target ‘arch/x86/syscalls/syscall_32.tbl’, needed by ‘arch/x86/syscalls/…/include/generated/asm/syscalls_32.h’. Stop. arch/x86/Makefile:180: recipe for target ‘archheaders’ failed make: *** [archheaders] Error 2
Any ides ?
Thanks.
-
RE: Request for Help or maybe just answers
Here is the output for the commands suggested. I am not a huge Linux guru, so I’m not certain if this shows you what you need to see. From this can you tell what drivers would need to be in an updated kernel ?
[ATTACH=full]1699[/ATTACH][ATTACH=full]1700[/ATTACH][ATTACH=full]1701[/ATTACH][ATTACH=full]1702[/ATTACH][url=“/_imported_xf_attachments/1/1699_IMG_20150223_131128.jpg?:”]IMG_20150223_131128.jpg[/url][url=“/_imported_xf_attachments/1/1700_IMG_20150223_130933.jpg?:”]IMG_20150223_130933.jpg[/url][url=“/_imported_xf_attachments/1/1702_IMG_20150223_130820.jpg?:”]IMG_20150223_130820.jpg[/url][url=“/_imported_xf_attachments/1/1701_IMG_20150223_131039.jpg?:”]IMG_20150223_131039.jpg[/url]
-
RE: Request for Help or maybe just answers
No, the devices are purchased pre-setup and running Windows XP Embedded.
I have updated to Tom’s latest kernel but that didn’t seem to have the correct drivers to see the USB SSD.
-
Request for Help or maybe just answers
Hello, our company is evaluating a Fog solution for our imaging needs. Everything was looking good but we have hit a wall.
One of the devices that we need to image has a USB Disk Module ( [url]http://www.radiant.su/eng/news/?action=show&id=167[/url] ) and Fog doesn’t see it and fails the compatibility test.
My question is: Is this something that can be remedied by a modified/custom Kernel (or some other means), or not ?
And if it can not, is this something that Fog development has plans to support in the near future ?
Love the product, just wish it could do everything we need.
Thanks,
-John