LMon

Members
  • Posts

    16
  • Joined

Converted

  • Gender
    Undisclosed

LMon's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Have you got anywhere with enabling ssh yet? Do you want to know how to get ssh working or how to get it working with clients like luckybackup. Because I have no idea on the latter.
  2. I've been banging my head against this for a couple of hours. Hopefully someone can help me out here. I want to restrict my ssh log in to public key only but I can't get it to work without getting in first and doing a ssh-add manually. Doing it in the go file doesn't work on boot, but does when I run the go file manually from a login. I have modified ssh_config to accept PubkeyAuthentication I have my public key stored in /boot/config/ssh. It is copied as ~/.ssh/authorized_keys via the go file. permissions on ~/.ssh are drwx------ permissions on ~/.ssh/authorized_keys are -rw------- What is the correct way to add the key on boot? I'm not that familiar with setting up ssh so if there's anything else I'm overlooking please let me know. Edit: Turns out I was just being impatient. Waiting a bit longer allowed for a public key login, when I could login by password straight away.
  3. No I'm saying that it works fine in 5.0-rc3 but none of the proper releases recognise it. I have tried 5.0.0, 5.0.2 and 5.0.4. None work
  4. I don't understand what you are asking. The device is recognised by the bios, which is proven by unraid currently working fine on rc3. If you are asking what version I am using, I believe I am using the latest but I would have to check.
  5. Ok, I've finally got around to trying this with the latest release (5.0.4) and no luck. It still doesn't detect my ethernet device.
  6. Ah, I hadn't noticed/processed that there was a new version since my initial attempt. The latest then was 5.0.2 and I had just given it another try before posting. I was updating to 5.0 on my way to 5.0.2 because that was in the upgrade instructions and there did not seem to be any change past then that would have helped. 5.0.3 seems like it might, although that page does not mention r8619, which my current install is using, only r8168. I will give it a try next time I have a chance however. Thanks for answering what seems now like a silly question. But as to my original post, is there a way to load the driver I want should Tom decide to change them again?
  7. I am trying to upgrade from 5.0-rc3 to 5.0 but my ethernet is not showing up. It looks like it has something to do with the r8169 drivers. I am using an ASrock G31M-S ( Realtek LAN 8103EL / 8102EL) It's hard to keep track of but from the changelogs it seems like I'm using the Realtek drivers (assuming the firmware files mentioned here are LAN drivers) Changes from 5.0-rc2 to 5.0-rc3 ------------------------------- - linux: use kernel version 3.0.31 - linux: added Realtek firmware files - shfs: fix issue of not recognizing newly-added drives - emhttp: correct disk spindown logic to account for clock adjustments - md: record disk spin up time Although this seems to imply it was stock and got taken out at rc15 Changes from 5.0-rc14 to 5.0-rc15 --------------------------------- - linux: use kernel 3.9.6-patched (patched with reiserfs sync superblock fix) - linux: replace stock r8169 driver with Realtek r8168-8.036.00 - shfs: change "disk0" to "cache" when it appears in user.LOCATON xattr - slack: mount /var/log onto a 'tmpfs' to consume no more than 128MB - slack: got rid of dangling 'initconfig' link in /root - slack: increase timeout waiting for USB flash device from 10 to 30 seconds - syslinux: remove boot option from syslinux.cfg to limit memory - webGui: fix bug where some PHP error message could get output when browsing disk shares - webGui: for NFS private share, increased 'Rule' field from 40 to 256 characters When running 5.0-rc3: lsmod ethtool -i eth0 ethtool eth0 ifconfig ethtool -S eth0 # lsmod Module Size Used by md_mod 45765 4 ntfs 162343 0 coretemp 4627 0 hwmon 945 1 coretemp xor 13945 1 md_mod sata_sil 5434 2 piix 3528 0 i2c_i801 6261 0 i2c_core 12704 1 i2c_i801 ata_piix 17826 4 r8169 30014 0 # ethtool -i eth0 driver: r8169 version: 2.3LK-NAPI firmware-version: N/A bus-info: 0000:01:00.0 # ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes # ifconfig eth0 Link encap:Ethernet HWaddr bc:5f:f4:1d:b6:e6 inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9054710 errors:0 dropped:0 overruns:0 frame:0 TX packets:5294911 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1531591127 (1.4 GiB) TX bytes:1395592843 (1.2 GiB) Interrupt:10 Base address:0x6000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4473 errors:0 dropped:0 overruns:0 frame:0 TX packets:4473 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:469542 (458.5 KiB) TX bytes:469542 (458.5 KiB) # ethtool -S eth0 NIC statistics: tx_packets: 5294960 rx_packets: 9054825 tx_errors: 0 rx_errors: 0 rx_missed: 0 align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 8033299 broadcast: 76906 multicast: 944620 tx_aborted: 0 tx_underrun: 0 When I boot into 5.0 ifconfig only lists 'lo' and there are no r8168/9 drivers shown when I run lsmod. Adding either/both of them with modprobe doesn't seem to do anything. (Do I need to run anything after modprobe to use them? I tried 'rc.inetd restart' (as well as inet1 an inet2). Also the reported size of r8169 is different. syslog trying to start 5.0 attached (I noticed it says "eth0 interface does not exist (yet)" Is there any way to import the drivers from rc3 or any other way of fixing this? syslog.txt
  8. Can anyone see anything wrong with an ASRock G31M-S R2.0? I know it's only got 4 SATA ports but I am hoping to use some old parts and there doesn't seem to be much else (with more ports) available in my country. Is there anything else that might cause a problem with it?