MikeaP
-
Posts
7 -
Joined
-
Last visited
Posts posted by MikeaP
-
-
And now some weirdness - I have done a few insmods manually:
QuoteSynologyNAS> ls /usr/lib/modules
adt7475.ko leds-atmega1608.ko syno_hddmon.ko
cdc-acm.ko leds-lp3943.ko synobios.ko
dca.ko lockd.ko synofsbd.ko
e1000e.ko loop.ko synorbd.ko
ehci-hcd.ko mpt3sas.ko udp_tunnel.ko
ehci-pci.ko mv14xx.ko usb-common.ko
fat.ko nfs.ko usb-storage.ko
grace.ko nfsv3.ko usbcore.ko
hid.ko pgdrv.ko usbhid.ko
i2c-algo-bit.ko phy_alloc_0810_x64.ko vfat.ko
i40e.ko r8168.ko vxlan.ko
igb.ko sg.ko xhci-hcd.ko
ip6_udp_tunnel.ko sha256_generic.ko xhci-pci.ko
ixgbe.ko sunrpc.ko
SynologyNAS> insmod /usr/lib/modules/usb-common.ko
SynologyNAS> insmod /usr/lib/modules/usbcore.ko
[ 2972.283571] ACPI: bus type USB registered
[ 2972.287599] usbcore: registered new interface driver usbfs
[ 2972.293092] usbcore: registered new interface driver hub
[ 2972.298425] usbcore: registered new interface driver ethub
[ 2972.303921] usbcore: registered new device driver usb
[ 2972.308970] <redpill/usb_boot_shim.c:166> usbcore registered, adding device watcher
[ 2972.316625] <redpill/call_protected.c:112> Got ptr ffffffffa00bddb0 for usb_register_notify
[ 2972.324966] <redpill/usb_boot_shim.c:127> Registered USB device notifier
SynologyNAS> lsmod
Module Size Used by Tainted: G
usbcore 199999 0
usb_common 2286 1 usbcore
mpt3sas 336499 2
bnx2 72295 0
redpill 149032 0
SynologyNAS> insmod /usr/lib/modules/usb-storage.ko
[ 3008.504224] usbcore: registered new interface driver usb-storage
SynologyNAS> ls /proc/bu
buddyinfo bus/
SynologyNAS> ls /proc/bus/
input pci usb
SynologyNAS> insmod /usr/lib/modules/ehci-hcd.ko
[ 3050.895123] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
SynologyNAS> insmod /usr/lib/modules/ehci-pci.ko
[ 3061.797531] ehci-pci: EHCI PCI platform driver
[ 3061.802090] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 3061.807320] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[ 3061.814716] ehci-pci 0000:00:1a.0: debug port 2
[ 3061.819254] DMAR: 32bit 0000:00:1a.0 uses non-identity mapping
[ 3061.825091] DMAR: Setting identity map for device 0000:00:1a.0 [0x0 - 0xfff]
[ 3061.836046] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
[ 3061.842838] ehci-pci 0000:00:1a.0: irq 20, io mem 0xc5206000
[ 3061.853989] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 3061.859869] hub 1-0:1.0: USB hub found
[ 3061.863636] hub 1-0:1.0: 2 ports detected
[ 3061.867763] <redpill/usb_boot_shim.c:75> Found new device <vid=1d6b, pid=0002> - didn't match expected <vid=0781, pid=5567> (prev_shimmed=0)
[ 3061.880467] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 3061.885696] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 3061.893094] ehci-pci 0000:00:1d.0: debug port 2
[ 3061.897633] DMAR: 32bit 0000:00:1d.0 uses non-identity mapping
[ 3061.903467] DMAR: Setting identity map for device 0000:00:1d.0 [0x0 - 0xfff]
[ 3061.914415] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[ 3061.921206] ehci-pci 0000:00:1d.0: irq 23, io mem 0xc5205000
[ 3061.931986] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 3061.937852] hub 2-0:1.0: USB hub found
[ 3061.941641] hub 2-0:1.0: 2 ports detected
[ 3061.945729] <redpill/usb_boot_shim.c:75> Found new device <vid=1d6b, pid=0002> - didn't match expected <vid=0781, pid=5567> (prev_shimmed=0)
SynologyNAS> [ 3062.189982] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 3062.267982] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 3062.337286] Got empty serial number. Generate serial number from product.
[ 3062.344172] hub 1-1:1.0: USB hub found
[ 3062.348168] hub 1-1:1.0: 6 ports detected
[ 3062.353308] <redpill/usb_boot_shim.c:75> Found new device <vid=8087, pid=0024> - didn't match expected <vid=0781, pid=5567> (prev_shimmed=0)
[ 3062.411285] Got empty serial number. Generate serial number from product.
[ 3062.418069] drivers/usb/core/hub.c (2940) Same device found. Change serial to ffffffd1ffffffb2ffffffdbffffffa0
[ 3062.428299] hub 2-1:1.0: USB hub found
[ 3062.432162] hub 2-1:1.0: 6 ports detected
[ 3062.437307] <redpill/usb_boot_shim.c:75> Found new device <vid=8087, pid=0024> - didn't match expected <vid=0781, pid=5567> (prev_shimmed=0)
[ 3062.720983] usb 2-1.1: new low-speed USB device number 3 using ehci-pci
[ 3062.827282] Got empty serial number. Generate serial number from product.
[ 3062.834470] <redpill/usb_boot_shim.c:75> Found new device <vid=0461, pid=4e22> - didn't match expected <vid=0781, pid=5567> (prev_shimmed=0)
[ 3062.929985] usb 2-1.2: new low-speed USB device number 4 using ehci-pci
[ 3063.060157] Got empty serial number. Generate serial number from product.
[ 3063.068204] <redpill/usb_boot_shim.c:75> Found new device <vid=046d, pid=c30e> - didn't match expected <vid=0781, pid=5567> (prev_shimmed=0)
[ 3063.163987] usb 2-1.5: new high-speed USB device number 5 using ehci-pci
[ 3063.265283] Got empty serial number. Generate serial number from product.
[ 3063.272070] drivers/usb/core/hub.c (2940) Same device found. Change serial to ffffffd1ffffffb2ffffffdbffffffa0
[ 3063.282146] drivers/usb/core/hub.c (2940) Same device found. Change serial to ffffffd1ffffffb2ffffffdbffffffa1
[ 3063.292616] hub 2-1.5:1.0: USB hub found
[ 3063.296657] hub 2-1.5:1.0: 4 ports detected
[ 3063.301663] <redpill/usb_boot_shim.c:75> Found new device <vid=0424, pid=2514> - didn't match expected <vid=0781, pid=5567> (prev_shimmed=0)
[ 3122.344596] usb 2-1.1: USB disconnect, device number 3
[ 3123.811157] usb 2-1.1: new low-speed USB device number 6 using ehci-pci
[ 3123.917588] Got empty serial number. Generate serial number from product.
[ 3123.924741] <redpill/usb_boot_shim.c:75> Found new device <vid=0461, pid=4e22> - didn't match expected <vid=0781, pid=5567> (prev_shimmed=0)
[ 3184.040401] usb 2-1.1: USB disconnect, device number 6
[ 3185.507330] usb 2-1.1: new low-speed USB device number 7 using ehci-pci
[ 3185.613518] Got empty serial number. Generate serial number from product.
[ 3185.620714] <redpill/usb_boot_shim.c:75> Found new device <vid=0461, pid=4e22> - didn't match expected <vid=0781, pid=5567> (prev_shimmed=0)
[ 3245.736205] usb 2-1.1: USB disconnect, device number 7
[ 3247.202503] usb 2-1.1: new low-speed USB device number 8 using ehci-pci
[ 3247.308697] Got empty serial number. Generate serial number from product.
[ 3247.315849] <redpill/usb_boot_shim.c:75> Found new device <vid=0461, pid=4e22> - didn't match expected <vid=0781, pid=5567> (prev_shimmed=0)
[ 3320.389710] usb 2-1.5.1: new high-speed USB device number 9 using ehci-pci
[ 3320.492656] usb-storage 2-1.5.1:1.0: USB Mass Storage device detected
[ 3320.499136] scsi host7: usb-storage 2-1.5.1:1.0
[ 3320.503735] <redpill/usb_boot_shim.c:91> Device <vid=0781, pid=5567> shimmed to <vid=f400, pid=f400>
[ 3321.508645] scsi 7:0:0:0: Direct-Access SanDisk Cruzer Blade 1.27 PQ: 0 ANSI: 6
[ 3321.517462] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim
[ 3321.524851] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications
[ 3321.532763] <redpill/scsi_notifier.c:87> Calling original sd_probe()
[ 3321.539136] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0
[ 3321.540265] sd 7:0:0:0: [synoboot] 7821312 512-byte logical blocks: (4.00 GB/3.73 GiB)
[ 3321.541636] sd 7:0:0:0: [synoboot] Write Protect is off
[ 3321.541638] sd 7:0:0:0: [synoboot] Mode Sense: 43 00 00 00
[ 3321.542634] sd 7:0:0:0: [synoboot] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 3321.554636] synoboot: synoboot1 synoboot2 synoboot3
[ 3321.562280] sd 7:0:0:0: [synoboot] Attached SCSI removable diskSynologyNAS> ls /dev/syno*
/dev/synobios /dev/synoboot1 /dev/synoboot3
/dev/synoboot /dev/synoboot2
SynologyNAS>Why did it not start usb support automatically ? How is this process controlled ?
-
On 8/1/2022 at 6:36 PM, pocopico said:
I suggest you compare the lsmod from tinycore for USB related modules and then see whats not loading on your system. Since this is the first time of reading something like that i suggest changing the USB stick and/or the USB port that its connected.
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
QuoteModule Size Used by Not tainted
cpufreq_powersave 12288 0
cpufreq_conservative 12288 0
cpufreq_userspace 12288 0
mgag200 24576 1
drm_kms_helper 114688 4 mgag200
drm 286720 3 mgag200,drm_kms_helper
agpgart 28672 1 drm
backlight 12288 1 drm
cec 32768 1 drm_kms_helper
squashfs 32768 57
loop 24576 114
ipmi_ssif 20480 0
wmi 16384 0
acpi_ipmi 12288 0
ipmi_si 36864 1
ipmi_msghandler 32768 3 ipmi_ssif,acpi_ipmi,ipmi_si
pcspkr 12288 0
lpc_ich 20480 0
bnx2 61440 0Syno:
QuoteSynologyNAS> lsmod
Module Size Used by Tainted: G
mpt3sas 336499 2
bnx2 72295 0
redpill 149032 0Just to make sure modules are there:
QuoteSynologyNAS> ls /usr/lib/modules/
adt7475.ko leds-atmega1608.ko syno_hddmon.ko
cdc-acm.ko leds-lp3943.ko synobios.ko
dca.ko lockd.ko synofsbd.ko
e1000e.ko loop.ko synorbd.ko
ehci-hcd.ko mpt3sas.ko udp_tunnel.ko
ehci-pci.ko mv14xx.ko usb-common.ko
fat.ko nfs.ko usb-storage.ko
grace.ko nfsv3.ko usbcore.ko
hid.ko pgdrv.ko usbhid.ko
i2c-algo-bit.ko phy_alloc_0810_x64.ko vfat.ko
i40e.ko r8168.ko vxlan.ko
igb.ko sg.ko xhci-hcd.ko
ip6_udp_tunnel.ko sha256_generic.ko xhci-pci.ko
ixgbe.ko sunrpc.koand some more things that might be interesting:
QuoteSynologyNAS> ls /proc/bus/
input pciIn TC pci and usb buses looked as following:
Quotelspci:
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/Ivy Bridge DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4)
00:1f.0 ISA bridge: Intel Corporation C202 Chipset Family LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
01:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
02:00.0 Ethernet controller: Broadcom Limited NetXtreme II BCM5716 Gigabit Ethernet (rev 20)
02:00.1 Ethernet controller: Broadcom Limited NetXtreme II BCM5716 Gigabit Ethernet (rev 20)
03:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a)lsusb:
Bus 002 Device 006: ID 0781:5567 SanDisk Corp. Cruzer Blade
Bus 002 Device 005: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 002 Device 004: ID 046d:c30e Logitech, Inc. UltraX Keyboard (Y-BL49)
Bus 002 Device 003: ID 0461:4e22 Primax Electronics, Ltd Dell Mouse, 2 Buttons, Modell: MS111-P
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubtree view:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
|__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 5: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 6, If 0, Class=Mass Storage, Driver=usb-storage, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480Midentifying USB with script:
tc@box:~$ ./rploader.sh identifyusb now
Found SanDisk Cruzer SerialNumber: 20060266521896B3438C
Vendor ID : 0x0781 Product ID : 0x5567
Should i update the user_config.json with these values ? [Yy/Nn]
y
tc@box:~$ -
15 minutes ago, pocopico said:
EDIT : I read also few posts back.
The message doesnt mean anything. It just means rploader tried to scan on the list of extensions for a matching extension and it couldnt find any. I'm curious though as of why this PCI device gets scanned. I only scan for known devices.
BTW : https://elixir.bootlin.com/linux/latest/source/drivers/mfd/lpc_ich.c Thats not related to USB.
Please send the output of ./rploader.sh identifyusb
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.
-
17 minutes ago, Peter Suh said:
bnx2 seems to be listed as Qlogic's NIC.
Looking at the Junior log analysis, maybe there is another NIC?
As a result of decompressing the kernel module file(bnx2-4.4.180plus-broadwellnk.tgz), the bnx2.ko file clearly exists.
Does the /var/log/*rc* file in the junior log say it can't find the bnx2.ko file?
The bnx2.ko file must exist somewhere under the /exts/pocopico.bnx2/ directory.
Please send the log and directory contents around the above on junior.I haven't analyzed the log yet.
Perhaps when an error starts in bnx2 ext, processing of the next ext is stopped and a 30 second timeout may occur.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 ?
-
22 minutes ago, Peter Suh said:
I found your hardware at line 4516 of the modules.alias.4.json file.
"name": "lpc_ich",
"alias": "pci:v00008086d00001C52sv*sd*bc*sc*i*"Is your USB stick an SD card?
Have you tried changing the USB memory to another one?
And, in order not to meet the 55% damage message
The /dev/synoboot* list is absolutely necessary.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.
RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal
in Tutorials and Guides
Posted
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.