powermanagement

[jsfarinet]

First of all: Thanks a lot for your patience.

What i did before reboot was:

1) I removed the block of kernel in gslapt, then i installed kernel source; i saw (but i cannot say exactly since i do not have salix access anymore) there were 2 different ones; i chose those with ending "-3". I also saw there were activated some other kernel parts (modules) to be reinstalled. When gslapt closed, saying all has been done correctly. I went to do

2) The build and installation of the amd catalyst driver step by step exactly how the HowTo page of slackware explained. After that i went, like the HowTo proposes to

3) Reoot and, merde ...

May be i should have run lilo after (if so, i'm sorry i've been so unadept)? 1). If so, could that be done ex-post?

And yes, i saw the wiki http://docs.salixos.org/wiki/Boot_into_ ... llation_CD but that did not work for me or i did something wrong. There is no cd here but an installation usb created by unetbootin. When i try to get the prompt (esc in the Unetbootin boot choice window) there is no hugesmp.s kernel available. The UNetbootin windows looks like this:

Code: Select all

|----------------------------------------------------------------------------|
|                             UNetbootin                                     |
|----------------------------------------------------------------------------|
| Default                                                                    |
|                                                                            |
| huge.s                                                                     |
| Salix 14.1 huge.s kernel                                                   |
| Salix 14.1 huge.s kernel  (use KMS console)                                |
| Detect/boot any installed operating system                                 |
|----------------------------------------------------------------------------|

PS. There's no cd drive here (not even on the machine i'm actually using - a semi-broken powerbook).

[gapan]

My guess is that you didn't just install the kernel-source package, but you also upgraded the other kernel packages by removing them from the blacklist in gslapt. There's a reason these are blacklisted and you should not be undoing that without consideration. There is even a wiki page on how to install the kernel-source package that doesn't require unblacklisting anything (there's also a page about installing the ATI/AMD driver too, but that's a different matter). Anyway, you upgraded the kernel, but you didn't run lilo, so the boot loader doesn't know about the new kernel. You'll have to chroot to your salix installation from somewhere else (the installation CD/USB will do, just as any live CD will too) and run lilo from there.

[jsfarinet]

Did that and - YESSSS! I'm back with a working Salix and the catalyst driver.

Thanks a lot for your patience! Now some small tweaks are still needed:

The boot screen has a horrible large font. Can that be changed (in lilo?)?

My /etc/lilo.conf looks like this:

Code: Select all

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append="quiet  vt.default_utf8=1 rootfstype=ext4"
boot = /dev/sda

compact

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/salix.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 255,20,255,20,255,20
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 15,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 65,6,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and 
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 50
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda1
  label = Salix
  read-only
# Linux bootable partition config ends

The administrator access to the catalyst configuration center looks like this:

Code: Select all

amdxdg-su -c amdcccle

Now, su (to become root) does not work in Salix. Executing that command in a terminal i get this error msg:

Code: Select all

$ amdxdg-su -c amdcccle
Error org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.gnome.zeitgeist.Engine': no such name
amdxdg-su: no graphical method available for invoking 'amdcccle' as 'root'

Sure, there is a simple way to get around: 'gksudo amdcccle' But i wonder if there is a solution more adhering to the original command (in the end i installed a slackware built package)?

[jsfarinet]

Getting on further on powermanagement:

I'm not sure, where exactly the close_lid (=suspend) is presumed to be set? I installed laptop-mode-tools and checked the acpi events. Apparently all is set fine there. May be there is somewhere a HowTo for slackware? Ich checked here and there in the wiki but i did not see anything specific (?)

My guess is that you didn't just install the kernel-source package, but you also upgraded the other kernel packages by removing them from the blacklist in gslapt. There's a reason these are blacklisted and you should be undoing that without consideration. There is even a wiki page on how to install the kernel-source package that doesn't require unblacklisting anything (there's also a page about installing the ATI/AMD driver too, but that's a different matter).

I think you're absolutely correct on this. Now, when i successfully rebooted Salix i was prompted with an info about available upgrades: In the end that changed kernel kernel-modules and kernel-source from *64-3 to *64-2. What's the reason that, as it seems to be from the numbers, the lower version is the - by default (?) -preferred one? And here attached an additional question: Is it reasonable to follow the advice of the slackware site and to substitute the huge kernel by the generic one (and if, what should be considered specifically - if any ...)?

The wiki page on how to install the kernel-source package without unblacklisting i did not find. May be i've overseen it?

In any case, a big thank you for your patience!

[laprjns]

The wiki page on how to install the kernel-source package without unblacklisting i did not find. May be i've overseen it?

http://docs.salixos.org/wiki/How_to_ins ... nel_source

[jsfarinet]

Thanks a lot!

[gapan]

In the end that changed kernel kernel-modules and kernel-source from *64-3 to *64-2. What's the reason that, as it seems to be from the numbers, the lower version is the - by default (?) -preferred one?

That was a mixup by slackware. The -2 in this case is actually newer than the -3.

Is it reasonable to follow the advice of the slackware site and to substitute the huge kernel by the generic one (and if, what should be considered specifically - if any ...)?

Same thing applies to salix, as it's using the exact same kernels. You can replace the huge kernel with the generic one, but make sure that your initrd includes the correct modules first (or your system won't boot).

[rooma]

How respectively where do in set them in lilo (in grub it is GRUB_CMDLINE_LINUX_DEFAULT)?

Open /etc/lilo.conf file in text editor as root and find line that begins with append=. Inside parenthis (after = sign) add string

Code: Select all

resume=/dev/sda2

where

Code: Select all

/dev/sda2

is your swap partition. It`s better to use UUID or labels instead of partition numbers (but I do not know does LILO supports them) because they can change (you attached HDD to a different port or added one more HDD) and you may hibernate to Windows or your root partition. After editing & saving changes in /etc/lilo.conf you have to reinstall LILO by excuting lilo command as root.

[jsfarinet]

How respectively where do in set them in lilo (in grub it is GRUB_CMDLINE_LINUX_DEFAULT)?

Open /etc/lilo.conf file in text editor as root and find line that begins with append=. Inside parenthis (after = sign) add string

Code: Select all

resume=/dev/sda2

where

Code: Select all

/dev/sda2

is your swap partition. It`s better to use UUID or labels instead of partition numbers (but I do not know does LILO supports them) because they can change (you attached HDD to a different port or added one more HDD) and you may hibernate to Windows or your root partition. After editing & saving changes in /etc/lilo.conf you have to reinstall LILO by excuting lilo command as root.

Thanks. Ok then the statement would look this:

Code: Select all

resume=<uuid here>

?

With quotes or without quotes (blkid produces e.g.

Code: Select all

/dev/hda1: uuid="<uuid here>" Type="swap"

), that's the question

[jsfarinet]

For the moment i used (in lilo append " " ) swap=/dev/sda3 (but i'll change that to uuid when someone can tell how exactly that should look like). In any case hibernate now works (big progress compared to debian and grub)

Some small adjustments are still needed:

Hibernate blocks wlan (i have to do manually 'rfkill unblock wlan' and then start wicd to (re)connect. How can i avoid, that hibernate blocks wlan?
Hibernate also seems to kill the powermanagement (acpi (?) ), since after a hibernate suspend does not work anymore.
There are also problems with tor after hibernate.