Save original firmware for later restoration

[fvdw]

seems the staging driver doesn't like the new kernel. I see modprobe page allocation errors in dmesg when trying a dongle with this driver

I will have look

[fvdw]

attached the patched realtek driver.
I had to make one more change to get it compiled for this kernel.
On my system it loads...and shows up in the usb devices window

ps not that this module has name 8712u.ko
(the staging driver has name r8712u.ko, remove this form /lib/modules/3.13.6 and give the command depmod to update the modules database now it should be possible to modprobe 8712

Code: Select all

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 1
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=03.13
S:  Manufacturer=Linux 3.13.6 ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=orion-ehci.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 2
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=02 MxPS=64 #Cfgs=  1
P:  Vendor=0424 ProdID=2512 Rev=0b.b3
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=2mA
I:  If#= 0 Alt= 1 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=02 Driver=hub

T:  Bus=01 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#=  3 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=0df6 ProdID=006c Rev=02.00
S:  Manufacturer=Manufacturer Realtek
S:  Product=RTL8191S WLAN Adapter
S:  SerialNumber=00e04c000001
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=ff Prot=ff Driver=r871x_usb_drv

Code: Select all

root@fvdwsl-5big2:/ # modprobe 8712u
root@fvdwsl-5big2:/ # dmesg
[219679.803399] Register Driver 'r871x_usb_drv'
[219679.807812] ==DriverVersion: v2.6.6.0.20120405==
[219679.814124] register rtl8712_netdev_ops to netdev_ops
[219679.819414] rtw_wdev_alloc
[219679.823218]
[219679.823218] 8712_usb_endpoint_descriptor(0):
[219679.829115] bLength=7
[219679.832943] bDescriptorType=5
[219679.835984] bEndpointAddress=83
[219679.839189] wMaxPacketSize=200
[219679.842379] bInterval=0
[219679.844918]
[219679.844918] 8712_usb_endpoint_descriptor(1):
[219679.851012] bLength=7
[219679.853377] bDescriptorType=5
[219679.856430] bEndpointAddress=4
[219679.859600] wMaxPacketSize=200
[219679.862742] bInterval=0
[219679.865265]
[219679.865265] 8712_usb_endpoint_descriptor(2):
[219679.871172] bLength=7
[219679.873516] bDescriptorType=5
[219679.876548] bEndpointAddress=6
[219679.879762] wMaxPacketSize=200
[219679.882890] bInterval=0
[219679.885404]
[219679.885404] 8712_usb_endpoint_descriptor(3):
[219679.891326] bLength=7
[219679.893673] bDescriptorType=5
[219679.896705] bEndpointAddress=d
[219679.899838] wMaxPacketSize=200
[219679.902961] bInterval=0
[219679.905474]
[219679.907038] 8712u : USB_SPEED_HIGH
[219679.910656] nr_endpoint=4
[219679.916727] Boot from EFUSE
[219679.919627] Autoload OK!!
[219680.692353] CustomerID = 0x   0
[219680.695575] MAC Address from efuse= 64-d1-a3-18-e5-cd
root@fvdwsl-5big2:/ #

[matzi]

Yep this driver works with manual modprobing. I have to recall about the automatic way in insert-modules. And 5big2 has 2 lan ports. Do you know which one is eth0 ?

[fvdw]

Lan1 is eth0

ps I used the upload driver option in usb-devices menu of the webinterface to install it
It creates a udev rule so that the driver is automatically loaded at boot

[matzi]

I am just trying to add a second disk to the 5big2- In the document

First time install instruction for 5big2 and 2big2 Cloudbox, internetspace 2, networkspace max v2 and 2big1 using fvdw-sl console and fvdw-sl-installer script.

it is that that the second disc has to be fully installed with the complete firmware. That in principle means to take disc1 out and setup disc2 as disc1 from scratch. Is that necessary? Why do all discs need the complete firmware and kernel on it?

I already tried to setup correct partion table and formatting but that is not enough to make it run.

[fvdw]

no the second disc doesn't need the full firmware only the partition structure.
And you need to format partion 8 in ext3, it is written very cleary in the document you are referring to ;)

and yes it will run but you need to reboot, did you do that, At boot the firmware will update the database and add disks (when tey are prepared properly).
I am sure it works I have a 5big2 myself

[Jocko]

Hi matzi,

Why do all discs need the complete firmware and kernel on it?

Indeed it is not required to have the same partitions table with all disks but we want it because :
- if the system disk (sda) is broken then it is easy to swap this disk with a data disk and copy on it the firmware image and the kernel.
- by this way, you don't lose data on the new system disk because the data partition is not changed !

This will be important with the RAID feature and why unlike Lacie firmware, only the data partition may be build on a logical RAID with the version 16.0 :tapfoot : the partition system will be never mounted on a RAID (Too many users, have issues to restore their NAS if the RAID is broken with the Lacie firmware)

By this way, It will be easy to restore the fvdw-sl firmware and the user will be able to rebuild easily the RAID table via the SSH access. :mrgreen:

[matzi]

It seems my device is a little bit strange.

I did many tries to get a second disc running. But whatever I did (including your recommendations), 5big2 did not work when a second disc was present in slot2. So I prepared the second disc completely with kernel and firmware in version 15-1. Now it booted normally. From watching firmware version in the webinterface it turned out that it boots from slot 2 when a second disc is installed!

How that? Can it be chosen or might it be a rule, it boots from the highest installed slot number? (slots 3 to 5 are empty)

Edit: Text in quotes is not fully right. From the Firmware version that is shown in the webinterface the quoted is correct. But from the file structure it is wrong. That means: It uses slot 1 for booting. It shows firmware version that is in slot 2. It does not boot when a disc is in slot 2 that has no firmware installed. That is strange to me.

[Jocko]

:scratch
What kernel version do you use ?
Maybe there is an issue with the last version and the device mapper.

What is dmesg output ?all lines like these

Code: Select all

[   10.695140] scsi 0:0:0:0: Direct-Access     ATA      ST2000DL001-9VT1 CC41 PQ: 0 ANSI: 5
[   10.703758] fvdw1 disk index before get_sd_name = 0
[   10.708701] No LaCie disk map available
[   10.712523] fvdw2 disk index after get_sd_name = 0
[   10.717332] fvdw3 prefix[0]=s  prefix[1]=d
[   10.721415] fvdw4 diskname = sda
[   10.725243] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[   10.732963] sd 0:0:0:0: [sda] 4096-byte physical blocks
[   10.739112] sd 0:0:0:0: [sda] Write Protect is off
[   10.743897] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   10.744035] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   10.820112]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
[   10.829187] sd 0:0:0:0: [sda] Attached SCSI disk
[   11.084737] ata2: SATA link down (SStatus 0 SControl F300)


[matzi]

kernel from webinterface is:
Linux 3.13.6 #19 PREEMPT Sun Apr 6 21:15:00 GMT+1 2014