MikeaP

Even after enabling usb manually and clearly getting /dev/synoboot* installation fails (at random % from 46 to 55 - at least it never gets beyond 55%). In syno console it says the following during installation: and an error in /tmp/installer_sh.log any help or guidance on where to dig further would be appreciated.

And now some weirdness - I have done a few insmods manually: Why did it not start usb support automatically ? How is this process controlled ?

I finally got my hands on my box server I have troubles with. Following advise from Pocopico: a straight comparison of lsmod between TC and Syno on the server with usb stick in the very same port: TinyCore Syno: Just to make sure modules are there: and some more things that might be interesting: In TC pci and usb buses looked as following:

Hej Pocopico, the message about unknown LPC device is not from rploader,sh - this message pops up in dmesg of a syno kernel. As there is something fishy with loader (there are no /dev/synoboot* entries) and there is no mentioning of my usb stick pid/vid - this was the only meaningful error in the dmesg to start investigation from. I will provide output of identifyusb (and can do so for lspci/lsblk/whatever from within tinycore) once i get back home. However one more funny thing: usb kernel modules are there in syno image but trying to insmod them trom command prompt (i see it's busybox version) results in complains unresolved symbols. Seems like some other dependency is not loaded.

I might not made myself clear - there is no issue with bnx2 driver - it loads and works as expected. A reference to bnx2 was there to illustrate my question about lpc_ich: is lpc_ich driver built into/statically linked with the kernel or should i look for a loadable kernel module (lpc_ich.ko) like i had to do for bnx2 network card ?

Hej Peter, thank you for your reply I did find the reference to my HW as well in the modules alias file trying to figure out if some kernel module did not get into the redpill-ed image (like i have to add bnx2 support along with firmware files). As there is no lpc_ich.ko among modules and hardware seens to be on "known" list - my only guess is that the module is statically linked with the kernel. When playing with freshly launched system ("junior mode" if I'm not mistaken): if I issue lsmod command - I can see very few modules loaded (ie bnx2) but nothing related to lpc_ich or usb. At the same time I can see usb-related *.ko files in a folder where modules presumably are. My USB stick is not an SD card - a "genuine" 1 Gb stick in a USB port on the backplane of the server. Looking through the dmesg - I was able to see some boot wait script reporting waiting for ~30 seconds for a device to come up, but there are no entries in dmesg with pid/vid of my USB stick which makes me think USB support does not come up at all. I also tried with my USB keyboard plugged during boot but I see no traces of keyboard (pid/vid) in dmesg as well (I would expect at least it listed as unsupported/unknown device on USB bus). I have yet to try a different USB stick, but honestly I can't see why current one might have failed to work (it managed to work before with bromolow 7.0.1 but does not work with exactly same image right now). Are there any other logs worth investigating ? is lpc_ics linked statically as I assume or has to be compiled/packed into image? (i have not found corresponding *.ko among files in repo used by redpill)

Hello fellow users, I need a hand in doing baremetal installation and I beg your pardon upfront if I'm posting in the wrong forum thread (I have read through quite a lot of stuff here and this one seemed most appropriate). I have previously done a successful installation using this guide on the very same hardware I'm trying to do an installation now. However it was quite some time ago with redpill v 0.4.something. This time following instructions and modifications I did last time to meet my hardware I face an issue - after running redpill I'm able to see my NAS on the network asking me for the initial installation of DSM, I feed in the PAT file and installation fails at around 55% telling me the file is wrong. My hardware is Dell R210II (pretty old one) which most closely meets bromolow image. Having started a fresh build with redpill and looking into the system via serial console I can see that: 1) there are no /dev/synoboot* entries (I made sure pid/vid of my USB stick are correct; /dev/synobios is there). 2) in dmesg output I see kernel lpc_ich is complaining about unknown LPC device with devId 0x1C52 3) I don't see any trace of USB block device drivers / USB as such in the system Could you please help me with some guidance on where to look further: 1) given a very first start after building image with redpill: should there be /dev/synoboot* entries (though not mounted) ? or are they expected to appear only after successfully installing DSM from PAT file? 2) Do I suspect it right that failing to start ICH (in my case Intel C202 south bridge) kernel also fails to load USB support appropriately? 3) Were kernel files used by redpill modified somehow to drop ICH support which seems to be a part of standard lpc_ich.c according to "conventional" kernel sources ? P.S. I have tried both bromolow (seems to be 3.x kernel) and broadwellnk (4.x kernel) with the same result - complaining about unknown LPC device 0x1c52 and failing to install PAT file.