You are not logged in.
I've uploaded new refracta-9 no-X isos:
https://sourceforge.net/projects/refrac … s/testing/
Based on Devuan-2.0 ASCII (pre-beta by probably a few days)
No-X does not mean minimal. It's crammed with a lot of extra utilities, as usual.
login:password user:user root:root
No refracta9 desktop isos yet. I might upload ones made from systems upgraded from jessie, but they are bigger than CD size. I haven't decided yet how to get them down to CD size. I'll take suggestions on what packages to leave out.
Update (2017-12-30): Newer installer fixes some bugs. Also includes partial German translation.
https://sourceforge.net/projects/refrac … b/download
* select_grub_dev if grub-pc is copied to /target and installed. (Fixes no bootloader installed on bios system)
* Fixed disable autologin when sudo is default.
* Include preliminary (partial) German translation file. refractainstaller-base (9.3.2)
1. Install wicd-curses or wicd-cli or connman or setnet. (setnet is in the experimental repo)
2.
dpkg-reconfigure locales
dpkg-reconfigure keyboard-configurationInstall task-french. (and maybe task-french-desktop - check the dependencies)
3.
dpkg-reconfigure tzdataCopy a jpg or png image file into /boot/grub/
Run 'update-grub'
You'll see the background image on the next boot.
Pinning systemd-sysv to -1 is sufficient to prevent installation of systemd. In fact, you don't even need that. I just tried installing systemd after removing /etc/apt/preferences.d/avoid-systemd and it's not possible.
root@ascii:/home/user# aptitude -s install systemd
No candidate version found for systemd
Unable to apply some actions, aborting
root@ascii:/home/user# aptitude -s install systemd-sysv
No candidate version found for systemd-sysv
Unable to apply some actions, abortingYou could try editing /etc/xdg/tumbler/tumbler.rc to reduce the priority of the image thumbnailers. The range is -20 to 19. Try something like -17. (or +17 if I'm wrong about which way the scale goes.)
I have tried to upgrade to ASCII and PLENTIES of my detailed desktop features are hence lost, esp I should mostly need suspension, which I wanna take a rest for my machine but dnt wanna reboot, so I will remian Jessie and will try OpenRC in my Jessie system.
Any problems with ascii that we don't know about will not get fixed. Any problems caused by misconfiguration on your end won't get fixed until you seek help.
BTW, suspend works fine here. What destkop are you using?
If I typed <ctl><alt><f1> it switches to tty1 with the login prompt, but after a few seconds a couple of system messages flash up, making it difficult to log in. Typing <ctl><alt><f1> again would get me to the login prompt, but it proved too hard for me to actually log in.
If you haven't typed anything yet, presssing ENTER will give you another login prompt. Then, do not look at the screen while you are typing. Just log in normally. (give it a couple seconds to prompt you for the password.)
Alternatively, you could turn off those messages by editing /etc/sysctl.conf:
# Uncomment the following to stop low-level messages on console
#kernel.printk = 3 4 1 3Keep a terminal open with top running and look at it when the thrashing starts. Or click on the cpu activity monitor in the panel - it will open a terminal with top.
You should put your own configs in /etc/X11/xorg.conf.d so they won't be overwritten on upgrades. Quote from 'man xorg.conf' (I don't know why they list the dir twice. They do that in a few places.)
Finally, configuration files will also be searched for in directories reserved for system use. These are to
separate configuration files from the vendor or 3rd party packages from those of local administration. These
files are found in the following directories:/usr/share/X11/xorg.conf.d
/usr/share/X11/xorg.conf.d
I found this. It's from 2014, so it may no longer be accurate. Also, please run the grep command I posted above to see if you get the same output that I got.
OK, then, that's a weird message to get.
4.9.0-4-amd64 is not a realtime kernel.
4.9.0-4-rt-amd64 is a realtime kernel.
grep PREEMPT /boot/config*That gives me the same thing for 4.9 in ascii and for 3.16 in jessie:
CONFIG_PREEMPT_NOTIFIERS=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not setI don't have a 4.9 kernel on the box with the nvidia graphics right now, so I can't test this.
I haven't heard much discussion of perl among the devuan devs. Maybe it just hasn't come up, or maybe we don't have any avid perl programmers. I think a lot of the package management stuff in debian (and consequently in devuan) is written in perl.
You can do a ./configure and make on a source package. Then run it from there. Don't do a 'make install' or you may screw up the system and confuse apt. Figure out what you need to do to get it to work. If you have to install other libraries, you should install them from the repo. After that, you can figure out how to get it into a debian package. The basic steps for that are pretty simple. The devil is in the details. And looking at the current debian source to see how it was done should be helpful.
It should be safe to wait. I've been using the older version in ascii until a few minutes ago. I upgraded to the newer package (the one you can't get) and so far, it seems to be working. It can be installed without the recommended packages. I don't know if that breaks anything.
apt-get --no-install-recommends install openssh-serverIf there are any problems using the newer version, it's possible to revert by installing the older .deb package in /var/cache/apt/archives
What kernel are you using? The message is clear. Either use a rt kernel or use nvidia driver, but you can't use both together. Which one is more important?
Edit: How are you installing the nvidia driver? Package from repo or binary from nvidia?
You could upgrade to ascii, which has the same packages as stretch. And you can install openrc:
$ apt-cache policy openrc
openrc:
Installed: (none)
Candidate: 0.13.1-4
Version table:
0.27-3 0
100 http://pkgmaster.devuan.org/merged/ ceres/main amd64 Packages
0.23-1+b1 0
100 http://pkgmaster.devuan.org/merged/ ascii/main amd64 Packages
0.13.1-4 0
500 http://auto.mirror.devuan.org/merged/ jessie/main amd64 PackagesSorry, I was busy doing other things. No, I'm not offended easily, as golinux mentioned, and certainly not about which editor to use. .I knew you were kidding. However, if I ever announce that I'm going to run notepad in wine, you are welcome to come down on me hard.
If you can make a package that works, you could put it up anywhere and tell people about it. If you want to try to get it into the devuan repo, you should set it up on git.devuan.org and follow the d1h directions in the Documentation section of this forum. Other than that, you seem to know what to do. Mess with the package, test it, and then I'm not sure why you would revert your system if you just created a solution. For versioning, you should check the debian documentation on that. You could use the same version as the source you're using and add a +something like we do for the devuan packages. But really, check the docs. It can be a bit confusing. (is for me, anyway).
Mint/ubuntu seem to be slow at everything. Not just booting. Trying to run them in a VM can give me an anxiety attack from waiting for something to respond.
When you get to the part in the installer where it wants to install grub, everything should already be mounted. The efi partition should be mounted at /boot/efi, and /sys /proc /dev and /dev/pts should all be mounted to the corresponding point on /target. It sounds like grub found it anyway.
When you get to the grub boot menu, press "e" and add to the linux line: nomodeset
Then ctrl-x to boot.
And the install was slightly different form before (as /sys/firmware/efi existed), and at the end I did the dpkg -i grub*deb in the chroot. grub complained about a missing BIOS boot block.
Yeah, that makes sense. You tried to install grub-pc in a uefi system. You only need to install the grub packages if the wrong grub is installed in the live system. In this case, grub-efi is installed, so you should boot in efi mode and let the installer handle to bootloader. You might not be able to use legacy bios with gpt partitions. And that uefi readme in the user's home is probably wrong and needs to be updated.
It might be better to use the cli installer, because that's a newer version, and I know it works well in a uefi install. Run 'refractainstaller' in a root terminal, or even better, (if you can stand to look at additional and distracting output on the screen) 'refractainstaller -d' to get a more verbose error log. One drawback is that you'll have to type in /dev/nvme-whatever to tell it which partition to install.
Sounds like you're in legacy mode. If you boot in uefi mode, there should be a /sys/firmware/efi. Check your bios settings.
When you boot the refracta iso, do you get a grub boot menu or an isolinux boot menu? (with grub, 'e' will get you to edit the boot command, with isolinux, TAB will get you to edit the boot command.)
No emacs here. Just vi, which I do not like. I can tolerate vim, but plain old vi always screws me up. I inevitably hit an arrow key to move the cursor, and it spits out inappropriate characters. I would put vim on my isos, except for the fact that it takes up too much space, and I try to keep the isos down to CD size. But I'm perfectly happy with nano. If I forget how to use it, the instructions are right there in front of my face.
When you tried to boot after installing, did you get anything? A grub boot menu or even a grub prompt? If so, it should be possible to boot with the right commands.
Did you look at the efi partition to see if anything got copied there?
There should be /boot/efi/EFI/<devuan or refracta>/grubx64.efi
I'm still in the neolithic age...
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 3800+(I actually have something a lot newer than that for building isos.)
Here's an ascii live iso with 4.12 backports kernel. There's not a lot installed, but it should be enough to get you going. I'd hate for anyone to be forced to use debian when they don't want to.
I'm sure others will see this and want it, so here are some important notes...
First of all, this is not an official release (of devuan or refracta.) See that it's in the EXPERIMENTAL folder. If something doesn't work or goes wrong, don't be surprised. Feel free to ask for help, but there should be no whining or complaining.
The backports repo is commented out in sources.list. There are also a few wireless firmware packages installed from backports. Regular ascii firmware packages can be found in /firmware. Also, contrib and non-free are enabled.
The installers should see your nvme disks and handle it correctly. If you use the cli installer, you'll have to type in the device name when you select a partition for installation. If you prefer, you can use this live iso to do a debootstrap install of devuan. I forgot to include the instructions for that.
There's no display manager. You should not need to log into a live session, but in case you do,
login name: user
password: user.
Root password is root.
Run 'startx' to get into an openbox session.
grub-efi-amd64 is installed. If you are installing to legacy bios, I recommend using the cli installer (run 'refractainstaller' in a root terminal). It will find the grub-pc packages in the root of the filesystem and do the right thing.
http://distro.ibiblio.org/refracta/file … 8_1525.iso
There's no gpg signature, but here's the sha256sum of the iso.
$ sha256sum snapshot-ascii-bpo-20171208_1525.iso
22f4bd23457c9a3619243967824bee14625777cc60e586b5c892bf1da069f8e3 snapshot-ascii-bpo-20171208_1525.isoCatprints, you got the one that's in ascii-proposed. I think it's the same as the one in ascii main except for the version.
Geoff42 is right - I forgot about libeudev1.
# apt-get install eudev=3.2.2-9 libeudev1=3.2.2-9
To force old interface names, add 'net.ifnames=0' to the boot command. (edit /etc/default/grub and then run update-grub)
GRUB_CMDLINE_LINUX_DEFAULT="net.ifnames=0"A couple of additional notes:
If you don't have the kernel metapackage installed (e.g. linux-image-amd64) then you won't get the new kernel automatically on dist-upgrade and will need to install linux-image-4.9.0-4-<arch> or install the metapackage and dist-upgrade again. After installing the new kernel, you should reboot, so you're running the new kernel.
You might lose policykit-1 on the dist-upgrade. Unless you're a stoic minimalist, you'll want to reinstall it.
If you're upgrading from debian jessie or stretch, you'll need to remove systemd and systemd-shim after the upgrade. You might need to reinstall some other packages, too.
If you're upgrading from debian with gnome, you are a glutton for punishment, and you are heading for a big adventure. It can be done, but a fresh install would be easier and faster.
fungus, 220:whatever is not the newest version. I think it's the oldest version.
Something like this should work...
apt-get install eudev=3.2.2-9and you'll probably be warned that you're downgrading. (It's not a downgrade. We changed the way it's numbered.)
You need the ascii-backports kernel. (4.10 or newer, so plain ascii won't do it.) I did put an iso up, but it was meant for one person. It was only there for a few hours. Been thinking about putting up another one. (One that doesn't have a copyrighted desktop background) But I wanted to wait until after the regular ascii isos were up before I do the bpo. Guess that's not helpful for all you razor-edge ryzenistas.
Lemme figure out which VM has the right system, whether or not 'less' is installed, add the bpo kernel, and upload it. I guess it'll happen later today.