RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

1 hour ago, WiteWulf said:

ot of people are incorrectly assuming (and this bears repeating) is that when they see the "Booting the kernel." message, and nothing else follows, that the system has failed to boot. The Synology kernel has no video drivers or framebuffer in it (as "real" Synology devices don't have a video card or display connected), so the console output is all sent to serial console (virtual or physical) one the kernel is loaded. You will not see anything else on screen after this point.

 

 

Hi WiteWulf, just a quick question, is it because of the change in DSM6/7 that we can no longer see console booting message like what we did in the DSM5 xpenology loader? No I am not urging anybody to include this nostalgic function, just curious, and it also seems to be easier for debugging.

Link to post
Share on other sites
30 minutes ago, Rebutia said:

Hi WiteWulf, just a quick question, is it because of the change in DSM6/7 that we can no longer see console booting message like what we did in the DSM5 xpenology loader? No I am not urging anybody to include this nostalgic function, just curious, and it also seems to be easier for debugging.

I honestly can't remember that far back :) , did we used to have console output to the screen? Was that in the xpenoboot days? I don't think there's been console output to the screen at all since we moved to Jun's bootloader.

 

To be honest, I find it *much* easier to debug with a virtual serial port via the iLO on my HP MicroServer, but I appreciate that not everyone has such hardware.

Link to post
Share on other sites
35 minutes ago, Mixpower said:

I have tried 7.0 and 7.0.1 on my Gen8 Microserver but after booting is does not come online,

I have used pocopico's tg3 module in all the images I build without any luck.


I have the impression that Gen 8 uses bnx2x?

Link to post
Share on other sites
9 minutes ago, nemesis122 said:

Hi all

 

Now on Gen8 the newest redpill build is stable for 3615xs and is there planned a 3617xs Version (More Power :-)) ? thank you

https://github.com/RedPill-TTG/dsm-research/blob/master/quirks/mysteries.md#usb-hot-plug-is-not-functional-some-models

 

https://github.com/RedPill-TTG/redpill-load/issues/18

Edited by Orphée
  • Like 1
  • Thanks 1
Link to post
Share on other sites

I have try a lot of loaders on my server builds with different loaders here is my experience:

DSM 918+ Pro: has Kernel 4.4 und with the correct config you have hardware decoding. cons: with VMM you cant install/ load other loaders 1.02b 1.03b or 1.04b there is no lan connection i dont know why i tried everyting with linux ubuntu or windows all is ok.

 

DSM 3615+ : pro is the most stable loader VMM works great also with loader 1.02b and 1.03 and 1.04 for virtualmaschines con: with 10Gbit you have only 500 MB read and write

DSM3617+ : pro this loader is very fast in DSM /it has the most read and write 10 gbit 700 - 800 Mb with raid 0 and 5 HDD and 1 SSD and VMM works great the same as 3615 but all is running super fast and smooth .

 

I have tested this loaders on gen8 with CPU 1240v2 1230v2 original Xeon and on a  ASUS87iplus MB i hate this f**** Bios but with the 3617 loader MBR i have now installed my favorite system 3617xs 😍 

 

So in short the best Loader at the moment is for me 1.03b with 3617 DSM 6.2 my config is always volume1 SSD for plex libary/ virtual Maschines / and and all apps / volume2 5x6tb is for the data.

 

Edited by nemesis122
Link to post
Share on other sites
1 hour ago, WiteWulf said:

bnx2x is 10GbE, isn't it?

 

I think the Gen8's onboard NIC uses tg3.ko, but I've not successfully tested this myself.

Confirmed:

$ sudo insmod libphy.ko
Password:
[ 1441.477154] WARNING: module 'libphy' built without retpoline-enabled compiler, may affect Spectre v2 mitigation
$ sudo insmod tg3.ko
[ 1457.964161] tg3.c:v3.132 (May 21, 2013)
[ 1457.996728] tg3 0000:03:00.0 eth2: Tigon3 [partno(N/A) rev 5720000] (PCI Express) MAC address 00:11:32:11:22:33
[ 1458.047412] tg3 0000:03:00.0 eth2: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 1458.096052] tg3 0000:03:00.0 eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 1458.134917] tg3 0000:03:00.0 eth2: dma_rwctrl[00000001] dma_mask[64-bit]
[ 1458.177824] tg3 0000:03:00.1 eth3: Tigon3 [partno(N/A) rev 5720000] (PCI Express) MAC address 00:11:32:11:22:33
[ 1458.227580] tg3 0000:03:00.1 eth3: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 1458.276282] tg3 0000:03:00.1 eth3: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 1458.314943] tg3 0000:03:00.1 eth3: dma_rwctrl[00000001] dma_mask[64-bit]

 

Using the drivers you posted here (which I think may have originally come from labrouss?):

 

Edited by WiteWulf
  • Thanks 1
Link to post
Share on other sites
1 hour ago, pocopico said:


I have the impression that Gen 8 uses bnx2x?

 

33 minutes ago, WiteWulf said:

Confirmed:


$ sudo insmod libphy.ko
Password:
[ 1441.477154] WARNING: module 'libphy' built without retpoline-enabled compiler, may affect Spectre v2 mitigation
$ sudo insmod tg3.ko
[ 1457.964161] tg3.c:v3.132 (May 21, 2013)
[ 1457.996728] tg3 0000:03:00.0 eth2: Tigon3 [partno(N/A) rev 5720000] (PCI Express) MAC address 00:11:32:ca:77:d5
[ 1458.047412] tg3 0000:03:00.0 eth2: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 1458.096052] tg3 0000:03:00.0 eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 1458.134917] tg3 0000:03:00.0 eth2: dma_rwctrl[00000001] dma_mask[64-bit]
[ 1458.177824] tg3 0000:03:00.1 eth3: Tigon3 [partno(N/A) rev 5720000] (PCI Express) MAC address 00:11:32:ca:77:d6
[ 1458.227580] tg3 0000:03:00.1 eth3: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 1458.276282] tg3 0000:03:00.1 eth3: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 1458.314943] tg3 0000:03:00.1 eth3: dma_rwctrl[00000001] dma_mask[64-bit]

 

Using the drivers you posted here (which I think may have originally come from labrouss?):

 

I thought tg3.ko was the correct driver for the gen8 at least from what I read in this topic,

seems I was correct but I still don't know why it does not come online.

Link to post
Share on other sites

I wanted to ask, has ayone got a working compiled poweroff module for DSM 6.2.3?
Currently AHCI shutdown does not work and so you have to manually get into the dashboard for starting DSM shutdown.

 

If someone has one i wouldn't mind helping in packaging it into a REDPill mod.

Link to post
Share on other sites
il y a 51 minutes, WiteWulf a dit :

Confirmed:


$ sudo insmod libphy.ko
Password:
[ 1441.477154] WARNING: module 'libphy' built without retpoline-enabled compiler, may affect Spectre v2 mitigation
$ sudo insmod tg3.ko
[ 1457.964161] tg3.c:v3.132 (May 21, 2013)
[ 1457.996728] tg3 0000:03:00.0 eth2: Tigon3 [partno(N/A) rev 5720000] (PCI Express) MAC address 00:11:32:11:22:33
[ 1458.047412] tg3 0000:03:00.0 eth2: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 1458.096052] tg3 0000:03:00.0 eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 1458.134917] tg3 0000:03:00.0 eth2: dma_rwctrl[00000001] dma_mask[64-bit]
[ 1458.177824] tg3 0000:03:00.1 eth3: Tigon3 [partno(N/A) rev 5720000] (PCI Express) MAC address 00:11:32:11:22:33
[ 1458.227580] tg3 0000:03:00.1 eth3: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 1458.276282] tg3 0000:03:00.1 eth3: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 1458.314943] tg3 0000:03:00.1 eth3: dma_rwctrl[00000001] dma_mask[64-bit]

 

Using the drivers you posted here (which I think may have originally come from labrouss?):

 

Thanks a lot again my Friend, I'll try this in few hours.

I've already test with bnx2x and bnx2 but no success on HP Proliant Gen 8.

I Hope proxmox is not the only way for this server :)

 

Link to post
Share on other sites
19 minutes ago, Schyzo said:

Thanks a lot again my Friend, I'll try this in few hours.

I've already test with bnx2x and bnx2 but no success on HP Proliant Gen 8.

I Hope proxmox is not the only way for this server :)

 

You hope is real, there is also VMWare ESXi ;)

Link to post
Share on other sites

@OrphéeGod, it's seem more difficult than Proxmox ^^

Once the image created, I had tg3.ko in i386-pc and in x86_64-efi with OSFMount. Edited the grub.cfg with add "insmod tg3.ko" under "insmod gzio"

Save and copy the image.

But same problem, no network on the Proliant. I don't know what to do now. Maybe look Proxmox tutorial ? 😢 :D

 

Edit : Trying with add libphy before t3g, testing in progress :)

Result : Same problem, no network 😢

Edited by Schyzo
Link to post
Share on other sites

I am trying to find out what is going wrong, so I'm using VSP on my Gen8 to check the output.

It says at the beginning that com0 can not be found is this a problem?

[    2.256293] <redpill/runtime_config.c:187> Found platform definition for "DS3615xs"
[    2.258820] <redpill/runtime_config.c:198> Validating runtime config...
[    2.261028] <redpill/runtime_config.c:48> Configured boot device type to USB
[    2.263364] <redpill/runtime_config.c:207> Config validation resulted in OK
[    2.265755] <redpill/runtime_config.c:224> Runtime config populated
[    2.267810] <redpill/uart_fixer.c:72> Registering UART fixer shim
[    2.270015] <redpill/uart_swapper.c:410> Swapping ttyS1<=>ttyS0 started
[    2.272211] <redpill/override_symbol.c:257> Overriding uart_match_port() with uart_match_port_collector [redpill]()<ffffffffa0004290>
[    2.273728] <redpill/override_symbol.c:172> Saved uart_match_port() ptr <ffffffff813101d0>
[    2.273730] <redpill/memory_helper.c:18> Disabling memory protection for page(s) at ffffffff813101d0+12/1 (<<ffffffff81310000)
[    2.273859] <redpill/call_protected.c:84> Got addr ffffffff810303e0 for flush_tlb_all
[    2.273874] <redpill/override_sol.c:221> Obtaining lock for <uart_match_port+0x0/0x70/ffffffff813101d0>
[    2.273874] <redpill/override_symbol.c:182> Generating trampoline
[    2.273879] <redpill/override_symbol.c:188> Generated trampoline to uart_match_port_collector+0x0/0x60 [redpill]<ffffffffa0004290> for uart_match_port<ffffffff813101d0>:
[    2.273880] <redpill/override_symbol.c:221> Writing trampoline code to <ffffffff813101d0>
[    2.273880] <redpill/override_symbol.c:221> Released lock for <ffffffff813101d0>
[    2.273881] <redpill/memory_helper.c:34> Enabling memory protection for page(s) at ffffffff813101d0+12/1 (<<ffffffff81310000)
[    2.273893] <redpill/override_symbol.c:269> Successfully overrode uart_match_port() with trampoline to uart_match_port_collector+0x0/0x60 [redpill]<ffffffffa0004290>
[    2.275464] <redpill/call_protected.c:108> Got addr ffffffff813168b0 for serial8250_find_port
[    2.275465] <redpill/uart_swapper.c:113> Found ptr to line=0 iobase=0x2f8 irq=3
[    2.275466] <redpill/uart_swapper.c:113> Found ptr to line=1 iobase=0x3f8 irq=4
[    2.275467] <redpill/uart_swapper.c:113> Found ptr to line=2 iobase=0x3e8 irq=4
[    2.275467] <redpill/uart_swapper.c:113> Found ptr to line=3 iobase=0x2e8 irq=3
[    2.275468] <redpill/override_symbol.c:279> Restoring uart_match_port<ffffffff813101d0> to original code
[    2.275469] <redpill/memory_helper.c:18> Disabling memory protection for page(s) at ffffffff813101d0+12/1 (<<ffffffff81310000)
[    2.275479] <redpill/override_symbol.c:250> Obtaining lock for <uart_match_port+0x0/0x70/ffffffff813101d0>
[    2.275480] <redpill/override_symbol.c:250> Writing original code to <ffffffff813101d0>
[    2.275480] <redpill/override_symbol.c:250> Released lock for <ffffffff813101d0>
[    2.275481] <redpill/memory_helper.c:34> Enabling memory protection for page(s) at ffffffff813101d0+12/1 (<<ffffffff81310000)
[    2.275489] <redpill/override_symbol.c:287> Successfully restored original code of uart_match_port
[    2.275490] <redpill/override_symbol.c:145> FreeingS for uart_match_port
[    2.550824] <redpill/uart_swapper.c:425> Disabling preempt & locking console
[    2.553179] <redpill/uart_swapper.c:427> ======= OUTPUT ON THIS PORT WILL STOP AND CONTINUE ON ANOTHER ONE (swapping ttyS1 & ttyS0) =======
[    2.557453] <redpill/uart_swapper.c:429> ### LAST MESSAGE BEFORE SWAP ON "OLD" PORT ttyS1<=>ttyS0

 

Also the output stops right here is there anything I can change about that?

Any help would be appreciated!

Link to post
Share on other sites
10 hours ago, pigr8 said:

 

does dmesg | grep sas from terminal show the hba loaded? if yes as @Orphée said check with fdisk -l if the disks show up.

Thank you @Orphée and @pigr8.

 

Here is the fdisk -l output. All disks showing up but not sure why the disks are showing sde, sdf etc:
 

Disk /dev/synoboot: 128 MB, 134217728 bytes, 262144 sectors
16 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device       Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/synoboot1    0,32,33     6,62,56           2048     100351      98304 48.0M 83 Linux
/dev/synoboot2    6,62,57     15,205,62       100352     253951     153600 75.0M 83 Linux
/dev/synoboot3    15,205,63   16,81,1         253952     262143       8192 4096K 83 Linux
Disk /dev/sde: 1863 GB, 2000398934016 bytes, 3907029168 sectors
243201 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sde1    0,32,33     310,37,47         2048    4982527    4980480 2431M fd Linux raid autodetect
/dev/sde2    310,37,48   571,58,63      4982528    9176831    4194304 2048M fd Linux raid autodetect
/dev/sde3    587,111,37  1023,254,63    9437184 3907015007 3897577824 1858G  f Win95 Ext'd (LBA)
/dev/sde5    588,112,5   1023,254,63    9453280 3906822239 3897368960 1858G fd Linux raid autodetect
Disk /dev/sdf: 1863 GB, 2000398934016 bytes, 3907029168 sectors
243201 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdf1    0,32,33     310,37,47         2048    4982527    4980480 2431M fd Linux raid autodetect
/dev/sdf2    310,37,48   571,58,63      4982528    9176831    4194304 2048M fd Linux raid autodetect
/dev/sdf3    587,111,37  1023,254,63    9437184 3907015007 3897577824 1858G  f Win95 Ext'd (LBA)
/dev/sdf5    588,112,5   1023,254,63    9453280 3906822239 3897368960 1858G fd Linux raid autodetect
Disk /dev/sdg: 1863 GB, 2000398934016 bytes, 3907029168 sectors
243201 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdg1    0,32,33     310,37,47         2048    4982527    4980480 2431M fd Linux raid autodetect
/dev/sdg2    310,37,48   571,58,63      4982528    9176831    4194304 2048M fd Linux raid autodetect
/dev/sdg3    587,111,37  1023,254,63    9437184 3907015007 3897577824 1858G  f Win95 Ext'd (LBA)
/dev/sdg5    588,112,5   1023,254,63    9453280 3906822239 3897368960 1858G fd Linux raid autodetect
Disk /dev/sdh: 1863 GB, 2000398934016 bytes, 3907029168 sectors
243201 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdh1    0,32,33     310,37,47         2048    4982527    4980480 2431M fd Linux raid autodetect
/dev/sdh2    310,37,48   571,58,63      4982528    9176831    4194304 2048M fd Linux raid autodetect
/dev/sdh3    587,111,37  1023,254,63    9437184 3907015007 3897577824 1858G  f Win95 Ext'd (LBA)
/dev/sdh5    588,112,5   1023,254,63    9453280 3906822239 3897368960 1858G fd Linux raid autodetect
Disk /dev/sdi: 224 GB, 240057409536 bytes, 468862128 sectors
29185 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdi1    0,32,33     1023,254,63       2048  468857024  468854977  223G fd Linux raid autodetect
Disk /dev/sdj: 93 GB, 100030242816 bytes, 195371568 sectors
12161 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdj1    0,32,33     1023,254,63       2048  195366464  195364417 93.1G fd Linux raid autodetect
Disk /dev/sdk: 1863 GB, 2000398934016 bytes, 3907029168 sectors
243201 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdk1    0,32,33     310,37,47         2048    4982527    4980480 2431M fd Linux raid autodetect
/dev/sdk2    310,37,48   571,58,63      4982528    9176831    4194304 2048M fd Linux raid autodetect
/dev/sdk3    587,111,37  1023,254,63    9437184 3907015007 3897577824 1858G  f Win95 Ext'd (LBA)
/dev/sdk5    588,112,5   1023,254,63    9453280 3906822239 3897368960 1858G fd Linux raid autodetect
Disk /dev/sdl: 1863 GB, 2000398934016 bytes, 3907029168 sectors
243201 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdl1    0,32,33     310,37,47         2048    4982527    4980480 2431M fd Linux raid autodetect
/dev/sdl2    310,37,48   571,58,63      4982528    9176831    4194304 2048M fd Linux raid autodetect
/dev/sdl3    587,111,37  1023,254,63    9437184 3907015007 3897577824 1858G  f Win95 Ext'd (LBA)
/dev/sdl5    588,112,5   1023,254,63    9453280 3906822239 3897368960 1858G fd Linux raid autodetect

 

dmesg | grep sas output:

[    1.318327] <redpill/intercept_execve.c:57> Filename /tmpData/upd@te/sas_fw_upgrade_tool will be blocked from execution
[    2.390160] mpt2sas version 20.00.00.00 loaded
[    2.392635] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (8152752 kB)
[    2.465986] mpt2sas0: MSI-X vectors supported: 1, no of cores: 4, max_msix_vectors: -1
[    2.466973] mpt2sas 0000:03:00.0: irq 73 for MSI/MSI-X
[    2.468960] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 73
[    2.469954] mpt2sas0: iomem(0x00000000fd4fc000), mapped(0xffffc90000018000), size(16384)
[    2.470951] mpt2sas0: ioport(0x0000000000004000), size(256)
[    2.596914] mpt2sas0: Allocated physical memory: size(7445 kB)
[    2.597912] mpt2sas0: Current Controller Queue Depth(3305), Max Controller Queue Depth(3432)
[    2.598910] mpt2sas0: Scatter Gather Elements per IO(128)
[    2.658630] mpt2sas0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.27.01.00)
[    2.658901] mpt2sas0: 0x1F4E: Vendor(0x1000), Device(0x0072), SSVID(0x1028), SSDID(0x1F4E)
[    2.659902] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
[    2.663103] mpt2sas0: sending port enable !!
[    2.669634] mpt2sas0: host_add: handle(0x0001), sas_addr(0x500605b006bea440), phys(8)
[    2.674918] mpt2sas0: port enable: SUCCESS
[    2.679023] scsi 4:0:0:0: SATA: handle(0x000c), sas_addr(0x4433221103000000), phy(3), device_name(0x50014ee0ae347ea7)
[    2.709273] scsi 4:0:1:0: SATA: handle(0x0009), sas_addr(0x4433221100000000), phy(0), device_name(0x500003993c40037e)
[   18.513653] scsi 4:0:2:0: SATA: handle(0x000a), sas_addr(0x4433221101000000), phy(1), device_name(0x50014ee2b1b4bb32)
[   33.610139] scsi 4:0:3:0: SATA: handle(0x000b), sas_addr(0x4433221102000000), phy(2), device_name(0x50000397dbd81f98)
[   48.893537] scsi 4:0:4:0: SATA: handle(0x000d), sas_addr(0x4433221104000000), phy(4), device_name(0x50015178f366abf7)
[   64.002050] scsi 4:0:5:0: SATA: handle(0x000e), sas_addr(0x4433221105000000), phy(5), device_name(0x55cd2e400033064c)
[   79.102315] scsi 4:0:6:0: SATA: handle(0x000f), sas_addr(0x4433221106000000), phy(6), device_name(0x50000398bd101889)
[   94.173073] scsi 4:0:7:0: SATA: handle(0x0010), sas_addr(0x4433221107000000), phy(7), device_name(0x50014ee60331902f)

 

I changed SataPortMap to 4 as suggested. I notice that all my disks are being picked up but I still end up with no drives detected message.

 

 

Link to post
Share on other sites
4 hours ago, Mixpower said:

 

I thought tg3.ko was the correct driver for the gen8 at least from what I read in this topic,

seems I was correct but I still don't know why it does not come online.


tg3.ko has a dependency libphy.ko which is also included in the tg3 extension. 
 

https://raw.githubusercontent.com/pocopico/rp-ext/main/tg3/rpext-index.json

 

Link to post
Share on other sites
4 minutes ago, Orphée said:

@urundai
what are you disk size ?

On github we have a report disks bigger than 2Tb can't be used currently.

My disks are 2TB each. I have 6 disks.

 

Forgot to mention - I was running these in 6.2.3 Jun's loader before, in a raid config. 

Edited by urundai
Link to post
Share on other sites
2 hours ago, pocopico said:


tg3.ko has a dependency libphy.ko which is also included in the tg3 extension. 
 

https://raw.githubusercontent.com/pocopico/rp-ext/main/tg3/rpext-index.json

 

Thanks, I used that indeed!

44 minutes ago, WiteWulf said:

Try swapping the com ports in bios settings. 

I tried that and put it on com1 but when I ssh into iLO using putty and type VSP it always connects on com2 even when I disable VSP it still does that.

 

EDIT: Just found there is another setting in the BIOS for the port and now it works on com1! Looks like there is something wrong with my vid/pid settings I'll dig into it and report back.

 

EDIT2: It just does this over and over and over, tried different usb ports but it does not matter it keeps doing this, I checked the VID and PID again and there are correct anyone has a clue?

 

:: Mounting procfs ... [  OK  ]
:: Mounting tmpfs ... [  OK  ]
:: Mounting devtmpfs ... [FAILED]
:: Mounting devpts ... [  OK  ]
:: Mounting sysfs ... [  OK  ]
[   10.647880]  sdu: sdu1 sdu2 sdu3
[   10.667520] sd 7:0:0:0: [sdu] No Caching mode page found
:: Loading modul[   10.693251] sd 7:0:0:0: [sdu] Assuming drive cache: write through
e sg[   10.723056] sd 7:0:0:0: [sdu] Attached SCSI disk
[   15.738964] usb 3-1: USB disconnect, device number 2
[   17.968475] usb 3-1: new full-speed USB device number 3 using uhci_hcd
[   18.156068] Got empty serial number. Generate serial number from product.
[   18.195263] <redpill/usb_boot_shim.c:75> Found new device <vid=03f0, pid=7029> - didn't match expected <vid=26bd, pid=9917> (prev_shimmed=1)
[   27.752685] usb 3-1: USB disconnect, device number 3
[   29.982199] usb 3-1: new full-speed USB device number 4 using uhci_hcd
[   30.170009] Got empty serial number. Generate serial number from product.
[   30.209179] <redpill/usb_boot_shim.c:75> Found new device <vid=03f0, pid=7029> - didn't match expected <vid=26bd, pid=9917> (prev_shimmed=1)
[   39.766411] usb 3-1: USB disconnect, device number 4
[   41.995925] usb 3-1: new full-speed USB device number 5 using uhci_hcd
[   42.183925] Got empty serial number. Generate serial number from product.
[   42.223078] <redpill/usb_boot_shim.c:75> Found new device <vid=03f0, pid=7029> - didn't match expected <vid=26bd, pid=9917> (prev_shimmed=1)
[   51.780135] usb 3-1: USB disconnect, device number 5
[   54.009649] usb 3-1: new full-speed USB device number 6 using uhci_hcd
[   54.197887] Got empty serial number. Generate serial number from product.
[   54.236997] <redpill/usb_boot_shim.c:75> Found new device <vid=03f0, pid=7029> - didn't match expected <vid=26bd, pid=9917> (prev_shimmed=1)
[   63.793860] usb 3-1: USB disconnect, device number 6
[   66.023374] usb 3-1: new full-speed USB device number 7 using uhci_hcd
[   66.210735] Got empty serial number. Generate serial number from product.
[   66.250919] <redpill/usb_boot_shim.c:75> Found new device <vid=03f0, pid=7029> - didn't match expected <vid=26bd, pid=9917> (prev_shimmed=1)
[   75.807584] usb 3-1: USB disconnect, device number 7
[   78.037099] usb 3-1: new full-speed USB device number 8 using uhci_hcd
[   78.225662] Got empty serial number. Generate serial number from product.
[   78.264836] <redpill/usb_boot_shim.c:75> Found new device <vid=03f0, pid=7029> - didn't match expected <vid=26bd, pid=9917> (prev_shimmed=1)
[   87.821310] usb 3-1: USB disconnect, device number 8

 

If I unplug the usbdrive and plug it back in it does this but then goes back to the same again.

[  198.784282] usb-storage 1-1.5:1.0: USB Mass Storage device detected
[  198.815397] scsi8 : usb-storage 1-1.5:1.0
[  198.835055] <redpill/usb_boot_shim.c:91> Device <vid=26bd, pid=9917> shimmed to <vid=f400, pid=f400>
[  199.910770] scsi 8:0:0:0: Direct-Access              USB DISK 2.0             PMAP PQ: 0 ANSI: 6
[  199.954664] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim
[  199.990468] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications
[  200.028866] <redpill/scsi_notifier.c:87> Calling original sd_probe()
[  200.060103] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0
[  200.962090] sd 8:0:0:0: [synoboot] 15654912 512-byte logical blocks: (8.01 GB/7.46 GiB)
[  201.002757] sd 8:0:0:0: [synoboot] Write Protect is off
[  201.028251] sd 8:0:0:0: [synoboot] Mode Sense: 23 00 00 00
[  201.058571] sd 8:0:0:0: [synoboot] No Caching mode page found
[  201.087422] sd 8:0:0:0: [synoboot] Assuming drive cache: write through
[  201.123769] sd 8:0:0:0: [synoboot] No Caching mode page found
[  201.151792] sd 8:0:0:0: [synoboot] Assuming drive cache: write through
[  201.206746]  synoboot: synoboot1 synoboot2 synoboot3
[  201.234149] sd 8:0:0:0: [synoboot] No Caching mode page found
[  201.262376] sd 8:0:0:0: [synoboot] Assuming drive cache: write through
[  201.294711] sd 8:0:0:0: [synoboot] Attached SCSI removable disk
[  207.958562] usb 3-1: USB disconnect, device number 18
[  210.188074] usb 3-1: new full-speed USB device number 19 using uhci_hcd
[  210.376874] Got empty serial number. Generate serial number from product.
[  210.415992] <redpill/usb_boot_shim.c:75> Found new device <vid=03f0, pid=7029> - didn't match expected <vid=26bd, pid=9917> (prev_shimmed=1)

 

Edited by Mixpower
Link to post
Share on other sites

I updated my test nas to 7.0.1-42218. First I had a small problem with the tool-chain v0.11. I added the lines for the 42218 version, but this time I used a "blank" in the folder name. The tool-chain didn't liked it and showed an error at line 75. I removed the "blank", then it worked.

 

As next I think I have to learn how the extensions work and find drivers. My test nas has two e-sata ports on a SiliconImage 3132 chipset, I think I have to add a driver for it. I really don't need that feature, but if it's there...   Maybe I wait for RP beta or final to play with extensions and test on other platforms (thinclients with Atom or AMD mainboard).

 

 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.