You are not logged in.
Not a problem here. I can get to tty1-6 from the login screen or from the desktop. Say a little more about how and what you installed. Full desktop? Minimal install and then added stuff?
Is there some other key you need to press to get the function keys to work on this laptop?
I installed grub from CentOS, Debian 8, Devuan, Fedora
I tried run openSUSE after every grub installation in each distribution.
This is a confused mess to begin with. It won't help if you keep installing grub from different distros. Have you been closely examining and comparing the grub.cfg files from each distro every time you run grub-install? How can you keep track of what you're doing?
Pick one disto to be in charge of grub. Then see which ones you can boot from that menu. If any don't work, try starting them from grub command line. It might be that one or more installations is not where you think it is or not where grub thinks it is. https://www.linux.com/learn/how-rescue- … ub-2-Linux
@miyolinux
The Miyo-XTRA-ascii isos from October have an older version of eudev which has a higher epoch number than the current version. This causes problems on upgrade. You should make new isos when you get a chance.
With this in /etc/apt/sources.list
deb http://pkgmaster.devuan.org/merged ascii main
deb http://pkgmaster.devuan.org/merged ascii-security main
deb http://pkgmaster.devuan.org/merged ascii-updates main
I think this was missing, so you couldn't see the version. I had the same problem when I tried to download it today. I got it after updating the package cache.
apt-get update
You might be able to install them with apt-get. If not, download the packages and install with dpkg --force-downgrade -i *.deb.
apt-cache policy libeudev1 libudev1
libeudev1:
Installed: 3.2.2-9
Candidate: 3.2.2-9
Version table:
*** 3.2.2-9 500
500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages
100 /var/lib/dpkg/status
libudev1:
Installed: 1:3.2.2+devuan2.10
Candidate: 1:3.2.2+devuan2.10
Version table:
*** 1:3.2.2+devuan2.10 500
500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages
100 /var/lib/dpkg/status
215-17+deb8u7 500
500 http://pkgmaster.devuan.org/merged jessie/main amd64 Packages
user@snapshot-ascii:~$ apt-get download libeudev1 libudev1
Get:1 http://pkgmaster.devuan.org/merged ascii/main amd64 libeudev1 amd64 3.2.2-9 [92.3 kB]
Get:2 http://pkgmaster.devuan.org/merged ascii/main amd64 libudev1 amd64 1:3.2.2+devuan2.10 [2,092 B]
Fetched 94.4 kB in 0s (110 kB/s)
user@snapshot-ascii:~$ ls lib*
libeudev1_3.2.2-9_amd64.deb libudev1_1%3a3.2.2+devuan2.10_amd64.deb
So, whichever one ran grub-install last should be the one in charge of booting. And update-grub (or whatever command generates a new boot menu on that installation) should include an entry for each installation on that machine. Right now, which system is listed first, and will it boot?
If you can boot into devuan enough to run root commands, or if you can chroot into it, you might try the following. I can't tell if this is what you need for sure, but there's at least a small chance it will fix the problem with devuan.
apt-get remove live-tools
CRYPTSETUP=y update-initramfs -u (and maybe -k <kernel> if you want to be specific)
apt-get install eudev=3.2.2-9 libeudev1=3.2.2-9
You may get a warning that you are downgrading. Proceed. You are "downgrading" to a newer version that has a smaller version number.
Did this installation ever work normally? Was it ok up until it complained about fsck, or did it complain on the first reboot into the new system?
Is this a uefi system, or legacy bios?
Are you using gpt or msdos partition table?
Please post the output of 'fdisk -l' and 'blkid'
Which installations will boot and which will not? Which one is in charge of grub?
Aha! Did you notice that what was in the video looks completely different from what you saw during the installation? I recognize the warnings about using uuid or labels with encryption. That was the live installer. You can use uuids or labels with encrypted partition, but you have to do it manually after the install. The installer won't do it for you.
Are there any files in /etc/initramfs-tools/conf.d/ in the devuan installation? If so, what's there?
Is there more than one hard drive on the computer? If so, please say a little more about your setup.
Here's a video showing the creation of an encrypted filesystem in the installer. In this case, I made a separate /boot partition so I could encrypt the root filesystem. But the procedure for creating the encrypted volume would be the same for /home. Take a look and see if you did something significantly different from this. It is confusing. The -4 in the filename is there because I had to do it four times before I got it right for the video.
http://distro.ibiblio.org/refracta/misc … rypt-4.ogv
You said above that you were able to fix it in one installation. What did you do on that one that you didn't do on the one that's still failing?
Did you try it like this?
fstab
/dev/sda14 / ext4 defaults,noatime 0 1
/dev/mapper/home_fs /home ext4 defaults,noatime 0 2
/dev/sda10 swap swap defaults 0 0
crypttab
home_fs /dev/sda15 none luks
If you lost your home directory after editing files, you should restore those files to their previous working state. Exactly what edits did you do?
That doesn't make sense. If it was working before you commented those lines, it should work again when you uncomment them. Where is that volume already mounted or mapped?
Look at the output of
df -h
mount
ls -l /dev/mapper/
It makes sense that your /home is not visible after you comment out the lines for /home in fstab and cryupttab. That's not the right solution.
1. Boot a live CD/DVD/USB
2. As root, run:
cryptsetup luksOpen /dev/sda15 homefs
fsck /dev/mapper/homefs
3. When that's done, you can fix those two files:
mount /dev/mapper/homefs /mnt
Then edit fstab and crypttab to uncomment the lines you commented.
4. Finish
umount /mnt
cryptsetup luksClose homefs
5. Reboot into the installed system.
I decommented the jessie-backports lines (and had to comment-out jessie lines) to get 2.0.0 displayed in synaptic:
But it shows an exclamation mark and is not able to resolve the dependencies.
The dependencies are probably in the jessie repos that you commented out. When you enable jessie-backports, you should leave the jessie repos enabled. Then
apt-get update
apt-get -t jessie-backports install <package>
Or, you could upgrade to ascii, as Catprints suggested. Even though it hasn't been released yet, it's pretty stable - it's based on Debian Stretch, which is the current stable release.
There is no package named suspend in the repos, but there are these. I didn't know about these three - I always install pm-utils for suspend and hibernate. If you want to see a longer list, run 'apt-cache search suspend'.
aptitude search suspend
p autosuspend - daemon to suspend a system in case of inactivity
p gnome-shell-extension-suspend-button - Gnome-shell extension to modify the suspend/shutdown buttons
p razorqt-autosuspend - Autosuspend component for Razor-qt desktop environment
nano /etc/apt/preferences.d/hopeforthebest
Add the following:
Package: *
Pin: release n=jessie
Pin-Priority: 1001
Then update/upgrade, and just like I named the file, hope for the best. If it works, you can then delete that file. (you can name the file whatever you want.)
What was that first step, anyway?
Maybe the better question is "Why?"
I just tried Subsurface, and it works in Refracta jessie (Devuan) and also works when I boot miyolinux-64bit-20161217.iso in virtualbox. I did not run any commands except chmod to make it executable, and then ./Subsurface-<version>.Appimage. A couple of popup windows asked me some questions. I declined to install it, and then the app opened.
So I guess the answer is yes, appimages can work on devuan. I don't know if that means they'll all work. What did you try?
I got a response. They are gathering feedback. I hope they get feedback from some graphic artists.
I just created a ticket asking them to revert to the old UI.
Now I need to go stare at a blank sheet of paper until I can see again.
Dolphins and whales are very intelligent, they just don't have arms and hands to make tools with. Maybe we can teach them linux and give them access to industrial robotics, then they can exterminate us humans and save the planet.
Wouldn't it be better if we could get them to teach us how to spend our days swimming, eating fish and having sex?
The aptitude message about dbus-user-session breaking policykit-1 just means that the packages are incomatible with each other. Not that anything is broken. A broken package would be marked with a B in the first column of the 'dpkg -l' output.
The only idea I can come up with at this point is that the dist-upgrade wasn't complete. On some of the upgrades I did, I had to run 'apt-get dist-upgrade' a second time to get everything. A few other people have reported the same.
I have a toshiba laptop, but anything that involves using special keys is out - this thing has no keyboard. (using a regular usb keyboard). Here's a list of files in the package.
apt-file list acpi-support
acpi-support: /etc/acpi/always-mute.sh
acpi-support: /etc/acpi/asus-keyboard-backlight.sh
acpi-support: /etc/acpi/asus-wireless.sh
acpi-support: /etc/acpi/ejectbtn.sh
acpi-support: /etc/acpi/events/ac
acpi-support: /etc/acpi/events/asus-keyboard-backlight-down
acpi-support: /etc/acpi/events/asus-keyboard-backlight-up
acpi-support: /etc/acpi/events/asus-media-eject
acpi-support: /etc/acpi/events/asus-wireless-off
acpi-support: /etc/acpi/events/asus-wireless-on
acpi-support: /etc/acpi/events/asus-wireless-wlan
acpi-support: /etc/acpi/events/battery
acpi-support: /etc/acpi/events/ibm-wireless
acpi-support: /etc/acpi/events/lenovo-undock
acpi-support: /etc/acpi/events/lidbtn
acpi-support: /etc/acpi/events/sleepbtn
acpi-support: /etc/acpi/events/sony-brightness-down
acpi-support: /etc/acpi/events/sony-brightness-up
acpi-support: /etc/acpi/events/sony-eject
acpi-support: /etc/acpi/events/sony-mute
acpi-support: /etc/acpi/events/sony-sleep
acpi-support: /etc/acpi/events/sony-volume-down
acpi-support: /etc/acpi/events/sony-volume-up
acpi-support: /etc/acpi/events/suspendbtn
acpi-support: /etc/acpi/events/thinkpad-cmos
acpi-support: /etc/acpi/events/thinkpad-mute
acpi-support: /etc/acpi/events/thinkpad-volume-down
acpi-support: /etc/acpi/events/thinkpad-volume-up
acpi-support: /etc/acpi/events/thinkpad-wireless-wlan
acpi-support: /etc/acpi/events/tosh-wireless
acpi-support: /etc/acpi/ibm-wireless.sh
acpi-support: /etc/acpi/lid.sh
acpi-support: /etc/acpi/mutebtn.sh
acpi-support: /etc/acpi/power.sh
acpi-support: /etc/acpi/sleep_suspend.sh
acpi-support: /etc/acpi/sleep_suspendbtn.sh
acpi-support: /etc/acpi/sonybright.sh
acpi-support: /etc/acpi/tosh-wireless.sh
acpi-support: /etc/acpi/undock.sh
acpi-support: /etc/acpi/voldownbtn.sh
acpi-support: /etc/acpi/volupbtn.sh
acpi-support: /etc/default/acpi-support
acpi-support: /etc/init.d/acpi-support
acpi-support: /usr/share/acpi-support/key-constants
acpi-support: /usr/share/acpi-support/screenblank
acpi-support: /usr/share/acpi-support/state-funcs
acpi-support: /usr/share/doc/acpi-support/README
acpi-support: /usr/share/doc/acpi-support/README.Debian
acpi-support: /usr/share/doc/acpi-support/README.asus
acpi-support: /usr/share/doc/acpi-support/README.thinkpad
acpi-support: /usr/share/doc/acpi-support/README.toshiba
acpi-support: /usr/share/doc/acpi-support/changelog.Debian.gz
acpi-support: /usr/share/doc/acpi-support/copyright
acpi-support: /usr/share/doc/acpi-support/examples/acpi/ac.d/90-hdparm.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/battery.d/90-hdparm.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/prepare.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/10-thinkpad-standby-led.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/11-video-pci-restore.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/13-855-resolution-set.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/15-video-post.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/17-video-restore.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/35-modules-load.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/40-infra-red.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/49-855-resolution-set.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/50-framebuffer-enable.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/50-tosh-restore-brightness.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/55-screen.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/58-proc-sysfs-restore-state.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/60-asus-wireless-led.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/62-ifup.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/65-console.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/67-sound.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/69-services.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/72-acpi-pain.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/89-asus-restore-brightness.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/90-hdparm.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/90-thinkpad-unstandby-led.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/90-xscreensaver.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/95-laptop-mode.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.d/98-acpi-unlock.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/resume.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/start.d/90-hdparm.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspend.d/01-laptop-mode.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspend.d/05-acpi-lock.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspend.d/10-thinkpad-standby-led.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspend.d/30-proc-sysfs-save-state.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspend.d/50-irda-stop.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspend.d/50-tosh-save-brightness.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspend.d/55-down-interfaces.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspend.d/60-generate-modules-list.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspend.d/65-services-stop.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspend.d/70-modules-unload.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspend.d/75-console-switch.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspend.d/80-video-vesa-state.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspend.d/81-video-pci-state.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspend.d/85-alsa-state.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspend.d/90-framebuffer-stop.sh
acpi-support: /usr/share/doc/acpi-support/examples/acpi/suspendorhibernate.gz
acpi-support: /usr/share/doc/acpi-support/examples/config/56548.config
acpi-support: /usr/share/doc/acpi-support/examples/config/ASUSTeK Computer Inc..config
acpi-support: /usr/share/doc/acpi-support/examples/config/Acer, inc..config
acpi-support: /usr/share/doc/acpi-support/examples/config/Acer.config
acpi-support: /usr/share/doc/acpi-support/examples/config/Compaq.config
acpi-support: /usr/share/doc/acpi-support/examples/config/Dell Computer Corporation.config
acpi-support: /usr/share/doc/acpi-support/examples/config/Dell Inc..config
acpi-support: /usr/share/doc/acpi-support/examples/config/ECS.config
acpi-support: /usr/share/doc/acpi-support/examples/config/FUJITSU SIEMENS.config
acpi-support: /usr/share/doc/acpi-support/examples/config/FUJITSU.config
acpi-support: /usr/share/doc/acpi-support/examples/config/Hewlett-Packard.config
acpi-support: /usr/share/doc/acpi-support/examples/config/IBM.config
acpi-support: /usr/share/doc/acpi-support/examples/config/NEC Computers International.config
acpi-support: /usr/share/doc/acpi-support/examples/config/SHARP Corporation.config
acpi-support: /usr/share/doc/acpi-support/examples/config/Samsung Electronics.config
acpi-support: /usr/share/doc/acpi-support/examples/config/Sony Corporation.config
acpi-support: /usr/share/doc/acpi-support/examples/config/TOSHIBA.config
acpi-support: /usr/share/doc/acpi-support/examples/default/acpi-support.gz
acpi-support: /usr/share/doc/acpi-support/examples/init.d/vbesave
acpi-support: /usr/share/lintian/overrides/acpi-support
If it's a bug, it must be reproducible. Please say more about how and what you installed and how you upgraded so someone can repeat it and get the same result.
How is policykit-1 broken? Not because it says that dbus-user-session breaks policykit-1. There is no dbus-user-session in devuan. Installing dbus-x11 should have corrected the situation.
I can't reproduce your error. I can install xfce4-terminal and thunar in my ascii with openbox. I tried it on a live-iso I made two weeks ago and also on an upgraded install of the same iso. In both cases, I used your sources.list.
Do you have any packages or repos pinned? Did you change anything in /etc/apt/apt.conf.d or preferences.d?
Try it with aptitude and see what alternate solutions it offers. That might provide an explanation of why those things won't install.
Makh,
It should have worked. I've installed openbox in ascii several times recently, from upgraded minimal jessie installs and from debootstrap installs of ascii. And I've run it with and without a display manager. What repository did you use for ascii - was it auto.mirror.devuan.org or pkgmaster.devuan.org?
Oh, good catch, rrq. No, I did not mean to get the package from ascii. I gave the solution to the wrong problem. The legacy issue is related to the newer version of xorg, not the newer kernel. Sorry about that, Steve.
jessie... xorg...
First thing I would try is adding 'nomodeset' to the boot command. At the grub boot menu, press 'e' to edit the boot entry, scroll down to the linux line and add nomodeset to the end of that line. Then ctrl-x to boot.
If that doesn't work, it might be a firmware issue.
What is the output of lspci? (so we can see what hardware you have)
For future reference, you're better off using debian documentation than ubuntu. Here' s a wiki page for your wireless. The package you need is firmware-iwlwifi, and you should get it from jessie-backports.
https://wiki.debian.org/iwlwifi