Jump to content
funtoo forums

erikr

Members
  • Content count

    38
  • Joined

  • Last visited

  • Days Won

    2

erikr last won the day on December 1 2016

erikr had the most liked content!

1 Follower

About erikr

  • Rank
    Advanced Member

Recent Profile Visitors

74 profile views
  1. ZFS Mountpoints

    Hi, I have been using btrfs on my rootfs for quite a while and one of the ways I am using it is that I always do upgrades in a snapshot of root and when upgrade is done I use that as new root. In btrfs this is very simple. I have my root in /mnt/btrfs/root I make the snapshot as /mnt/btrfs/root-upgrade, I chroot into this an perform the upgrade. When I am done I simple rename the dirs; mv root root-fallback mv root-upgrade root Nothing is changes on my system and as mount with -o subvol=root applies to the subvolume named root at the specific point in time when mount runs I will simply enter the upgraded system. Question is; can I do something similar in zfs? Is there a way to make zfs use another name or mountpoint next time I boot but not directly? Regards, Erik
  2. Over time I have experienced problem that my keyboard does not work during early boot, the time where I am supposed to make key-map selection on system-rescue-cd, but - more important - at the time I am expected to enter encryption key to unlock my encrypted partitions. If I end up in rescue mode I can't do anything, not even ctrl-alt-delete to reboot. I have had the problem on my current and previous hardware if I am using debian-sources (4.8 and 4.14). I have this problem with all kernels I have tested with my present hardware (ASUS Prime Z370). Naturally it failes with my ordinary logitech k750 keyboard but it also fails with a ordinary plain USB cable connected USB-keyboard. I have played around with different settings in kernel (gentoo-sources) to build in or not support for USB, logitech modules, the fundamental USB HIDBP, etc and cannot observe any difference during boot (but I managed to disable mouse in KDE). I can see that the logitech modules are loaded when booting debian-kernel but it still wont work. This is the latest dmesg where HID is loaded [ 1.239301] hidraw: raw HID events driver (C) Jiri Kosina [ 1.239542] usbcore: registered new interface driver usbhid [ 1.239780] usbhid: USB HID core driver . . . [ 20.619928] logitech-djreceiver 0003:046D:C52B.0003: hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-5.1/input2 [ 20.732809] input: Logitech K750 as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.1/1-5.1:1.2/0003:046D:C52B.0003/0003:046D:4002.0005/input/input9 [ 20.732897] logitech-hidpp-device 0003:046D:4002.0005: input,hidraw2: USB HID v1.11 Keyboard [Logitech K750] on usb-0000:00:14.0-5.1:1 [ 21.154637] usbcore: registered new interface driver snd-usb-audio [ 25.298802] logitech-hidpp-device 0003:046D:4002.0005: HID++ 2.0 device connected. I am quite sure that luks is opened long before the 20 seconds and the HID is hidraw. The very same rows with the very same keyboard on a working setup where I can enter the password: One difference I found is that in a working boot (where keyboard is working) the same rows as above seems to happen earlier: Dec 30 09:20:37 nuffsan kernel: [ 2.440038] usb 8-2.1: new full-speed USB device number 4 using xhci_hcd Dec 30 09:20:37 nuffsan kernel: [ 2.624861] usb 8-2.1: New USB device found, idVendor=046d, idProduct=c52b Dec 30 09:20:37 nuffsan kernel: [ 2.624866] usb 8-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Dec 30 09:20:37 nuffsan kernel: [ 2.624869] usb 8-2.1: Product: USB Receiver Dec 30 09:20:37 nuffsan kernel: [ 2.624872] usb 8-2.1: Manufacturer: Logitech Dec 30 09:20:37 nuffsan kernel: [ 2.628778] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:09.0/0000:04:00.0/usb8/8-2/8-2.1/8-2.1:1.0/0003:046D:C52B.0001/input/input5 Dec 30 09:20:37 nuffsan kernel: [ 2.680543] hid-generic 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:04:00.0-2.1/input0 Dec 30 09:20:37 nuffsan kernel: [ 2.683897] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:09.0/0000:04:00.0/usb8/8-2/8-2.1/8-2.1:1.1/0003:046D:C52B.0002/input/input6 Dec 30 09:20:37 nuffsan kernel: [ 2.735411] hid-generic 0003:046D:C52B.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:04:00.0-2.1/input1 Dec 30 09:20:37 nuffsan kernel: [ 2.738136] hid-generic 0003:046D:C52B.0003: hiddev1,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:04:00.0-2.1/input2 . . . Dec 30 09:20:38 nuffsan kernel: [ 12.393989] cryptsetup (4105) used greatest stack depth: 13648 bytes left Dec 30 09:20:38 nuffsan kernel: [ 20.241508] cryptsetup (4179) used greatest stack depth: 13520 bytes left Password was entered before 12 and 20 seconds. I use the very same and slightly modified linuxrc and initrd.scripts. Modification is an own luks open function that is similar but independent from the cryptroot-stuff. Instead I open encrypted partitions specified at kernel line in specified order right before BTRFS scan is performed. Eventually I might send a patch. I have tried the solution mentioned in https://forums.gentoo.org/viewtopic-t-1063372.html but it didn't work.
  3. Well, thanks for the help in this thread. I started to test combinations of my 4 memory modules and found out that something is wrong and it is possible that there is a problem with the motherboard. I have moved on to greener pastures and are now installing on my brand new I7-8700K setup instead. It is fabulous. After I managed to boot on debian-sources I also had to rebuild webkit-gtk that would actually freeze the computer after 20 minutes. That is what I used to test the memory modules. Eventually I will return to that motherboard and try to find the problem, it is intended to be a server taking backups. If I decide to trust it. Regards, Erik
  4. I managed to boot with UEFI and debian-sources. All 16GB of memory are there but keyboard wont work during boot so I cannot enter password for encrypted disks, thus the time delay. Seems like I have some miss-configuration in my kernel config but on the other hand it has been around for some time and are based on the one for my previous hardware that is based on the hardware before that.
  5. EFI boot with linux mint and ubuntu/kubuntu seems to work and I have all the memory. Still not booted into debian-sources.
  6. I am using crucial, forgot the exact module right now. I am not overclocking. I did build the PC my self. I have suspected memory problems at some stage (some 6 month ago) and tested to remove them in pair. I think they are purchased as a set of 4x4 modules. There is a lot of BIOS settings, any particular of interest, and I have tried quite some combinations. I have verified the problem in UEFI Only mode as well as combined Legacy/UEFI. UEFI only mode used my DIsplayPort as main output while legacy enabled uses the DVI-port. I (think) I have disabled secure boot, it is only used when instaƶlling kubuntu and is disabled directly when the nvidia drivers is installed so there is little point. I am currently installing debian-sources but that will take quite some hours so I know more later tonight :) // Erik
  7. I forgot to mention; I am booting the very same linux root and home partitions from BOIS and EFI, using the very same kernel-file and initramfs-file and get different results. 16GB if I boot using BOIS and 4 if I boot using EFI.
  8. I don't think so. I have tried with the exactly same kernel and initrd and lines for both BIOS and EFI (named it memory-test and copied the files between the two boot partitions) so I guess should have the very same problem when booting in BIOS. /etc/motd tells me I used stage3-amd64-piledriver-funtoo-current-2017-10-18 as a starting point, I would not be able to do anything if I booted with a 32 bit kernel. Right? I recall I tried that during transition; nothing works and that is how you can tell it went wrong.
  9. After many many considerations I went for EFI-boot in faovour of good old BIOS-boot using syslinux. The fall back solution is still BIOS-boot using extlinux. Problem is that with the very same (carefully verified) initramfs and kernel all my 16GB ram shows up in BIOS boot while only 4GB (well, 3.5) shows up booting from EFI. Any hint on the reason to this? My world does not depend on EFI-boot, the BOIS boot works very well and will be my primary until this is sorted out, but it would be good to understand. Some facts; Motherboard is ASUSTeK SABERTOOTH 990FX R2.0 Rev 1.xx BIOS is dated Date: 05/04/2016 and version 2901 that seems to be the latest version. # uname -a Linux kalle 4.13.12-gentoo #6 SMP PREEMPT Thu Dec 14 07:42:52 CET 2017 x86_64 AMD FX(tm)-9590 Eight-Core Processor AuthenticAMD GNU/Linux I have tried several combinations of legacy modes including no legacy support (CSM disabled).
  10. It is still empty when I look. Meanwhile I browse manually from this URL (taken from the example in the installation guide): https://build.funtoo.org/funtoo-current/
  11. crypttab and openRC

    :) I stick with genkernel and the slightly modified scripts (my own modifications). Most guides refer to another initrd-script set but I prefer Funtoo original flavour - thats why I use Funtoo instead of Gentoo ;)
  12. crypttab and openRC

    And well, what is the role of /etc/config.d/dmcrypt in this case? Will it be included in the initramfs and deal with root and swap before root is mounted or will it execute after root is mounted and take care of the rest (swap, home etc)? None of the the guides I read mentioned this file :( // Erik
  13. crypttab and openRC

    Hi, On one of my laptops I have gone encrypted along with syslinux. To get there I had to hack the initrd scripts a bit but well, I got it working. In some documentation I have come across (funtoo, gentoo, and arch linux) there are quite some references to /etc/crypttab that seems to be used along with systemd but are there any scripts making use of crypttab in if open RC is used? // Erik
  14. We gave up and went a completely other way - we are going to put a light switch to the access point and only turn it on when it is supposed to be used. Password to be changed when motivated (i.e. not very often). There will be a light in the switch so one can see if access point is on or not from distance. The access point will be covered by a box with plexiglass front and wooden sides to avoid being messed with. All involved are very satisfied by a low tech solution and ready for cover design :)
  15. Hi, I am looking for a software or combination of software running on Linux to manage network guest passwords for a semi public facility. Semi-public means a facility owned by a compound that can b e rented. There is a WiFi connected to fiber (100Gbit/s) that can be shared to visitors but we do not want to have publicly open since the facility is centrally located. What we try to achieve is: * In advance generate passwords for the period of time (some months) and let the system change password Fridays and Mondays. Someone need to know the expected password in advance * Have a WebGUI from LAN but not from WAN * Can be installed on a Raspberry Pi 3 with Linux possible located between internal public LAN and the router. (Will a Raspberry Pi 3 be able to cope with HD streamed movie?) * Users without a ticket shall preferably be redirected to a web page on the Raspberry The alternatives I have found so far either looks abandoned or I cant figure out if they help (like hostapd) Thankful for all pointers or ideas.
×