Request for Help or maybe just answers
-
I am pretty sure that this is only limited by what the used linux kernel can support. As far as I can see those Apacer UDMs can generally be used with linux!! Have you successfully run any kind of linux on it??
Trying a quick search on the web I couldn’t find a whole lot of information about it but I guess I’ll find some soon.
EDIT: Just had an idea. Please try booting into a debug session with one of your UDM clients. Then see which partitions linux finds: [CODE]cat /proc/partitions
…
fdisk -l
…
ls -al /dev/sd*
…
dmesg | grep sd
…[/CODE]
If you don’t see any maybe try loading the usb storage module with ‘modprobe usb-storage’… -
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.
-
Maybe FOG does not see them (yet). But does linux? Try booting debug mode or any other live linux and check the above commands…
-
generally, fog intentionally ignores storage devices connected by USB. the reason behind this is simple: normally people don’t want to run their systems off of a USB drive and what if someone left a usb drive plugged into the computer? I know that it can be done, however it will probably require some help from tom.
-
You would have to build a custom kernel to allow for this. Just add the drivers for the device (s) you may need and you should be good to go.
-
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]
-
Sorry, I didn’t know about FOG ignoring USB connected storage devices yet! Your screenshots show that any kind of linux would be able to use the UDM devices. Please check out this manual on how to build your custom kernel: [url]http://fogproject.org/wiki/index.php/Build_TomElliott_Kernel[/url]
You’ll find usb storage driver here: Device Drivers -> USB Support -> USB Mass Storage (mark it with <*>) and then build your kernel…
-
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.
-
Hard to tell without knowing the exact steps you made. Please provide more information on how exactly you tried to build the kernel (e.g. install build environment, download kernel source, extract source, config, …)
For sure there is something wrong with the kernel source. Where did you get it from? Extracted without errors? Enough free disk space?
That file should be there! It is part of the kernel source!
[CODE]find /path/to/extracted/kernel/source/linux-3.x.y/ -name “syscall_32.tbl”
…[/CODE] -
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.
-
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]
-
[quote=“Theodor, post: 42631, member: 28660”]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.[/quote]
If this works, you’re a hero in my book.
-
Sounds to me, you built a 32 bit bzImage, but are loading a 64 bit init.xz.
-
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 ?
-
Sounds like the method you created the kernel is a little off. We’re not using cpio information which appears to have been added.
-
Which version of FOG do you use?? It’s probably a good idea to use the same kernel version to match that of init_32.xz provided by FOG.
[CODE]file /var/www/fog/service/ipxe/bzImage32
… Linux kernel … version 3.15.6 …[/CODE]
This is for FOG 1.2.0 on our production server. So I would download linux-3.15.6.tar.xz… What is your version and which kernel source did you use? -
I did use 3.19 with Fog 1.2 but am now downloading 3.15.6. Will keep you posted on results.
-
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.
-
[quote=“Theodor, post: 42811, member: 28660”]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.[/quote]
^ Hero
-
[quote=“Theodor, post: 42811, member: 28660”]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.[/quote]
Oh yes, the SCSI block device driver… forgot about that! Thanks for reporting back! Great to hear that you got it working now…
