You are not logged in.
Hi there!
When I leave my PC for a short time I use suspend-to-ram („Bereitschaft“) which works fine.
In order to save energy I would like to use suspend-to-disk („Ruhezustand“), which either gives me an error message:
when pressing the power button (swap is 11.8G [says fdisk], RAM is 8G)
-or-
when using pm-hibernate leaves my system powered on with a blank screen - and I can't bring it back to life.
So, what can I do to put my system into a state where I can „pull the plug“ without using „halt“?
TIA
Gregor
Yes, I'm aware of the problems that can arise from backing up a disk in use. I usually use grml for this kind of tasks.
Gregor
Investigate the use of the apt options --get-selections and --set-selections in the apt man page
Btw, do NOT use dd to backup your disk to an existing backup drive. Unless you don't care about the data that's already on it :-\
What I meant is something like
dd if=/dev/sda of=/media/backup/sda-backup.dd
with the USB disk mounted at /media/backup. So my dd backup would just be a ~30 GB file on that disk (among other back-uped things).
Thanks for the get/set selection examples!
Gregor
Hi there!
Since Devuan looks very promising to me, I want to give it some kind of "harder try". Which means: I want to keep my home and some minor /usr/local things. Everything else I want to be fresh like morning dew. So what I'm thinking of is ...
- dd-Backup of my system disk (just about 30 GB SSD) to an external backup-disk (a 4 TB USB disk which I use for my weekly backups.
- export a list of currently installed programs
- make a fresh base installation of Devuan
- do some apt magic to install the programs (use the list created in step 2)
So, what do you think? Am I missing something? What would be the fitting commands for the steps 2 and 4?
At least, if anything goes terribly wrong, I could dd the backup back ...
TIA
Gregor
Gregors wrote:... Maybe you don't see such pop-ups because you accept every cookie you're offered. I don't like this kind of cookies. This is why I don't surf sites that offer them. ...
No...I'm just a boring user. Only visit 3 or 4 sites regularly. Periodically slip into the dark-side and visit one or two more.
I can make a screen shot if you like :-) I guess SF has a new owner that wants to annoy people like me. Who cares.
BTW: Your hint helped. Thanks a lot!
Gregor
Gregors wrote:MiyoLinux wrote:See if this will help.
...I'm not sure if it might. When I clicked the link I saw some „we value your privacy“ crap. It would be great if they'd value the mood I'm in.
Okay. You are in quite a mood, aren't you? I've never seen a message like you described there, and I'm not even running an adblocker right now.
You guess right :-) Maybe you don't see such pop-ups because you accept every cookie you're offered. I don't like this kind of cookies. This is why I don't surf sites that offer them.
Here, I will copy and paste the instructions...
Thanks a lot!
Gregor
alsactl store
NOT restore
Yep. I used alsactl store after sound worked again.Then I tried alsactl restore after there was no sound after rebooting.
Maybe you have to disable the undesired card somewhere, years ago we did that via a motherboard dip switch! Maybe someone else can help with multiple sound cards.
I thought dip switches are history. But I'll check that. Thanks!
Gregor
See if this will help.
...
I'm not sure if it might. When I clicked the link I saw some „we value your privacy“ crap. It would be great if they'd value the mood I'm in.
Regards,
Gregor
It appears you have 2 sound cards?
Yes. Well, the first „sound card“ is the one on my graphics card (Nvidia something). The second is the „real“ sound card.
In a terminal, if you run alsamixer, hit F6; does the desired sound card show there?
You can use alsamixer to get the sound settings to your liking, then run alsactl store (as root) and those settings will become the default.
That helped until the next reboot. Now I can use alsamixer and change to whatever sound card I like, there's no sound. 'alsactl restore' doesn't change that.
Well, I recall there was some OS that behaved similarly. The one that made me use Linux. Please don't tell me that everything would work if I switched back to that.
SIGH
Gregor
What does aplay -l report?
Geoff
**** Liste der Hardware-Geräte (PLAYBACK) ****
Karte 0: NVidia [HDA NVidia], Gerät 3: HDMI 0 [HDMI 0]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 0: NVidia [HDA NVidia], Gerät 7: HDMI 0 [HDMI 0]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 0: NVidia [HDA NVidia], Gerät 8: HDMI 0 [HDMI 0]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 0: NVidia [HDA NVidia], Gerät 9: HDMI 0 [HDMI 0]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 1: Live [SB Live! 5.1 [SB0060]], Gerät 0: emu10k1 [ADC Capture/Standard PCM Playback]
Sub-Geräte: 32/32
Sub-Gerät #0: subdevice #0
Sub-Gerät #1: subdevice #1
Sub-Gerät #2: subdevice #2
Sub-Gerät #3: subdevice #3
Sub-Gerät #4: subdevice #4
Sub-Gerät #5: subdevice #5
Sub-Gerät #6: subdevice #6
Sub-Gerät #7: subdevice #7
Sub-Gerät #8: subdevice #8
Sub-Gerät #9: subdevice #9
Sub-Gerät #10: subdevice #10
Sub-Gerät #11: subdevice #11
Sub-Gerät #12: subdevice #12
Sub-Gerät #13: subdevice #13
Sub-Gerät #14: subdevice #14
Sub-Gerät #15: subdevice #15
Sub-Gerät #16: subdevice #16
Sub-Gerät #17: subdevice #17
Sub-Gerät #18: subdevice #18
Sub-Gerät #19: subdevice #19
Sub-Gerät #20: subdevice #20
Sub-Gerät #21: subdevice #21
Sub-Gerät #22: subdevice #22
Sub-Gerät #23: subdevice #23
Sub-Gerät #24: subdevice #24
Sub-Gerät #25: subdevice #25
Sub-Gerät #26: subdevice #26
Sub-Gerät #27: subdevice #27
Sub-Gerät #28: subdevice #28
Sub-Gerät #29: subdevice #29
Sub-Gerät #30: subdevice #30
Sub-Gerät #31: subdevice #31
Karte 1: Live [SB Live! 5.1 [SB0060]], Gerät 2: emu10k1 efx [Multichannel Capture/PT Playback]
Sub-Geräte: 8/8
Sub-Gerät #0: subdevice #0
Sub-Gerät #1: subdevice #1
Sub-Gerät #2: subdevice #2
Sub-Gerät #3: subdevice #3
Sub-Gerät #4: subdevice #4
Sub-Gerät #5: subdevice #5
Sub-Gerät #6: subdevice #6
Sub-Gerät #7: subdevice #7
Karte 1: Live [SB Live! 5.1 [SB0060]], Gerät 3: emu10k1 [Multichannel Playback]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Regards,
Gregor
Hi there!
Yesterday I removed pulseaudio from my system. Directly after that everything worked like expected. But today I don't hear anything but silence after turning on my amplifier. Alsamixergui only shows the „sound card“ of my graphics card (Nvidia something).
Has Linux changed to being Windows? Is it necessary to reboot after each fart I let go?
Yep, I'm sort of pissed off. A bit like on the day I heard that Debian switches from Sys-V-init to that piece of shit called systemd. Since pulseaudio is from the same author I don't want to have this in my system. Well, systemd is the reason for moving to devuan. Do I have to go back to debian?! OMG ...
So, what can I do to hear my music? Rhythmbox seems to have changed a lot since Debian 7. It seems that there is no way to tell it where to output sound.
Thanks in advance!
Gregor
If it's just the older version of that programme you want, then maybe try adding the Debian wheezy src repository, get the source and just build it for your current release.
Oh. This advice is the least I would have thinked of. I'll try this asap.
Thanks a lot!
Gregor
Hi there!
When I was younger I believed everything would get better as times goes by. Especially software. Just like wine.
But today I tried using Hugin to stitch a panorama consisting of some photos I took just two hours ago. And guess what ... the output is that brilliant I would wipe my a. with.
So I want to get my „old“ system back (be able to boot into my old system). Hugin on my old system will feel like stepping back some decades. But it will work in a way I can handle. It always did.
The bad thing is that I cannot boot into that system because the devuan/lilo installation gave me a system that is unable to boot my old configuration. So I'm thinking of using qemu to setup a configuration with the old harddisk partitions. I'm sure Hugin would work (it always did).
But how can I achieve this? Or what can I do to make lilo to be able to boot my old debian system?
I'm some sort of helpless 'though I'm pretty used to solve problems.
So here's some information I consider helpful:
Harddisk partitions I use (Partitions marked with * are the ones I use for Devuan, some of them also used with old system):
Part. size used for
----- --------- ---------------
* sda1 10,00 GB Devuan /
* sda2 11,17 GB swap
* sda3 9,78 GB /usr/local
sda4 extended
* sda5 15,29 GB /home/gszaktilla/dokumente
* sda6 29,49 GB Devuan /usr
* sda7 322,09 GB /home/gszaktilla/dokumente/datensammlung
* sda8 514,62 GB /home/gszaktilla/dokumente/qemu
sda9 9,75 GB Debian /tmp
sda10 9,32 GB Debian /var
sdb1 21,24 GB Debian 7.11 / <------------------ old root partition
sdb2 13,20 GB Devuan /tmp
sda is a hard disk (one of those with rotating magnet discs), sdb is an SSD.
/etc/fstab on sdb1 (old system) reads
/dev/sdb1 / ext4 errors=remount-ro,noatime 0 1
/dev/sda2 none swap 0 0
/dev/sda3 /usr/local ext4 user,exec 0 8
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sdd1 /media/usb0 auto rw,user,noauto 0 0
/dev/sdd2 /media/usb1 auto rw,user,noauto 0 0
/dev/sda9 /tmp ext4 rw,user,exec 0 6
/dev/sda10 /var ext4 rw,user,exec 0 7
/dev/sda5 /home/gszaktilla/dokumente ext3 rw,user,exec 0 2
/dev/sda7 /home/gszaktilla/dokumente/datensammlung ext4 ro,user,noexec 0 3
/dev/sda8 /home/gszaktilla/dokumente/qemu ext4 rw,user,exec 0 4
/dev/sdc1 /home/gszaktilla/dokumente/datensammlung/video auto rw,user,noexec 0 0
/etc/lilo.conf („new“ system) reads
large-memory
#boot = /dev/disk/by-id/ata-WDC_WD10EZEX-07M2NA0_WD-WCC3F3147296
#root = "UUID=6515d096-c5c2-4081-adf7-e778e324fee8"
compact
install=menu
menu-scheme = Wb:Yr:Wb:Wb
map=/boot/map
vga=normal
delay=200
prompt
timeout=1000
default=debian
image=/vmlinuz
label=Linux
read-only
optional
# alias=1
initrd=/initrd.img
image=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted
# alias=2
initrd=/initrd.img.old
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
other=/dev/sdb1
label=debian
# restricted
# alias=3
image = /boot/vmlinuz-3.2.0-6-amd64
label = "Debian"
root = /dev/sdb1
read-only
initrd = /boot/initrd.img-3.2.0-6-amd64
Well ... just for your entertainment: The output of the „newer“ Hugin is here: http://test.szaktilla.de/result.jpg
Do you need further information?
TIA
Gregor
Yes, there may be a Devuan newsgroup.
Regards
Gregor
Hi, Gregor. I don't use rhythmbox but can imagine that it keeps all your personal settings (including song ratings) somewhere in your home folder. Look for a folder such as /home/gregor/.rhythmbox or /home/gregor/.config/rhythmbox.
If you upgrade without wiping your home folder, rhythmbox should behave as before without any intervention from you. Nevertheless, I'd copy the rhythmbox config folder to a flashdrive just in case.
Shame on me. I should have tried this before posting.
Now I have all the "ratings" back. Rebuilding my mostly automated playlists shouldn't be a big job.
Thanks a lot!
Gregor
PS: High temperatures cause exhaustion.In all possible ways.
Hi there!
Because Debian 7 is „out of LTS“ I am moving from Debian 7 to Devuan 2.
Now I would like my „new“ rhythmbox to behave like my old did. I don't want to rate every song again.
Is it possible to „convert“ the respective files? Hm, *are* there any files I could use to prevent me from doiing all the things I did in my old rhythmbox?
Thanks in advance!
Gregor