You are not logged in.
Has anyone gotten encrypted drives working with the new kernel?
i'm trying to create an initrd that includes an encrypt hook using
sudo mkinitcpio -g /boot/vmlinuzeee.img -k 2.6.24.4eee
however all i get at boot is:
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuzeee root=/dev/sda2 ro
Error 13: Invalid or unsupported executable format
so i guess the problem is with my image
"This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats"
when i make the image i get these errors at the beginning:
ERROR: module 'ata[-_]generic' not found
ERROR: module 'ahci' not found
ERROR: module 'ata[-_]piix' not found
and my menu.lst looks like
kernel /vmlinuzeee root=/dev/sda2 ro
initrd /vmlinuzeee.img
Offline
I compiled it, but the one i've installed is from the eee repo. i've tried removing everything but the default arch kernel and reinstalling, but at the time it doesn't seem to help. by the way, as long as i am the only one who's having this problem (and i do not need the ethernet device most of the time), this can remain a curiosity.
saten
Just make sure you are really booting /boot/vmlinuzeee kernel and not the generic one from kernel26 package.
(╯°□°)╯~ ┻━┻
Offline
Has anyone gotten encrypted drives working with the new kernel?
i'm trying to create an initrd that includes an encrypt hook using
sudo mkinitcpio -g /boot/vmlinuzeee.img -k 2.6.24.4eee
however all i get at boot is:root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /vmlinuzeee root=/dev/sda2 ro Error 13: Invalid or unsupported executable format
so i guess the problem is with my image
"This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats"
when i make the image i get these errors at the beginning:
ERROR: module 'ata[-_]generic' not found
ERROR: module 'ahci' not found
ERROR: module 'ata[-_]piix' not foundand my menu.lst looks like
kernel /vmlinuzeee root=/dev/sda2 ro
initrd /vmlinuzeee.img
At least those ERRORs while creating the initrd image are caused by missing modules which are already built in the kernel-eee so you can safely remove them from /etc/mkinitcpio.conf's MODULES array.
I don't use encryption at all so sadly I can't help you with this but you can at least try running hwdetect --hooks and update your HOOKS array in /etc/mkinitcpio.conf (don't forget to include the encryption stuff). There's also a possibility that we are still missing some kernel features.
By the way has somebody got the intelfb working? I always end up with "intelfb: Cannot reserve FB region." error.
I have been running some tests with all three framebuffer drivers and it seems that only special feature with the uvesafb is native 800x480 resolution but that can't be done without 915resolution-tweak and uvesafb built as module.
So for now I suggest removing the intelfb from the kernel (less annoying errors at the boot time) and compiling uvesafb as module. General vesafb driver is working just fine. :E
(╯°□°)╯~ ┻━┻
Offline
i've installed v86d and used the vga option of 640x480 at 256 colors in grub. what i got is a black screen after grub until x starts.
@ighea: yes i'm sure i'm booting the right kernel, otherwise i would have a different output on uname and i could modprobe the modules that are no longer built in, right?
Offline
i've installed v86d and used the vga option of 640x480 at 256 colors in grub. what i got is a black screen after grub until x starts.
Yes, we are still missing the framebuffer console support I mentioned before.
@ighea: yes i'm sure i'm booting the right kernel, otherwise i would have a different output on uname and i could modprobe the modules that are no longer built in, right?
Well, you are at least having really strange errors there. I hope reinstalling the kernel-tuff would fix them, but dunno.
(╯°□°)╯~ ┻━┻
Offline
UPDATED: acpi-eee-8-1
Here is once again amazing update for one of the best acpi-script packages available!
http://kapsi.fi/~ighea/eee/acpi-eee/acp … pkg.tar.gz
So what's new in this release?
* In /etc/acpi/eee.conf
** one can now specify screen position for the asusosd (I always thought the left top corner was weird >p)
** set optional commands to be run once wlan is turned on/off with Fn-F2
* minor tweaks in wlan.sh
Tip: As the wlan on/off scripts something similar to http://kapsi.fi/~ighea/eee/wpa can be used if you use wpa_supplicant for you wlan management.
If you happen to have any improvement ideas feel free to tell them!
(╯°□°)╯~ ┻━┻
Offline
Wow, nice update ighea!
Will try this out as soon as I can.
PS. Is there a way to have my screen turned off when closed the lip instate of suspend?
Offline
PS. Is there a way to have my screen turned off when closed the lip instate of suspend?
Sure, just set COMMAND_ON_LID_CLOSE=yes to COMMAND_ON_LID_CLOSE=no.
Make sure you have the XUSER entry set and turning off the screen should work just fine.
Last edited by ighea (2008-03-26 20:41:34)
(╯°□°)╯~ ┻━┻
Offline
Thanks for the updates.
zodmaner wrote:PS. Is there a way to have my screen turned off when closed the lip instate of suspend?
Sure, just set COMMAND_ON_LID_CLOSE=yes to COMMAND_ON_LID_CLOSE=no.
Make sure you have the XUSER entry set and turning off the screen should work just fine.
This is great, Is it possible to have lid closure do different actions depending on power status (if ac on turn off screen, if ac off turn off eee)?
Does anyone have any suggestions on a battery monitor app? I would also like something to give me low battery warnings and maybe even be able to issue a power down command when power gets to a certain level. I have tried several apps with no luck.
Also, I have been trying to get a bluetooth headset working. I read the wiki but was unable to load snd-bt-sco. It would really cool to get this working.
Thanks
brncmp
Offline
Thanks for the updates.
ighea wrote:zodmaner wrote:PS. Is there a way to have my screen turned off when closed the lip instate of suspend?
Sure, just set COMMAND_ON_LID_CLOSE=yes to COMMAND_ON_LID_CLOSE=no.
Make sure you have the XUSER entry set and turning off the screen should work just fine.This is great, Is it possible to have lid closure do different actions depending on power status (if ac on turn off screen, if ac off turn off eee)?
Does anyone have any suggestions on a battery monitor app? I would also like something to give me low battery warnings and maybe even be able to issue a power down command when power gets to a certain level. I have tried several apps with no luck.
Also, I have been trying to get a bluetooth headset working. I read the wiki but was unable to load snd-bt-sco. It would really cool to get this working.
Thanks
brncmp
At this point it is best to start writing your own acpi event handlers- then you can do most of this kind of stuff. Take a look at ighea's and I's acpi scripts (mine are still not in an 'official' package but they are in my GIT repo) to see how to do this sort of thing.
Offline
Ok i got toofishes kernel to boot sorta but when i get to the "enter luks passphrase:" part and enter my password it says
device-mapper: table: 253:0: crypt: Error allocating crypto tfm
device-mapper: ioctl: error adding target to table
device-mapper: ioctl: device doesn't appear to be in the dev hash table.
Command failed: No key available with this passphrase.
The fallback image with the stock kernel still boots fine. Can anyone guess whats going on here?
Offline
Thanks for the updates.
ighea wrote:zodmaner wrote:PS. Is there a way to have my screen turned off when closed the lip instate of suspend?
Sure, just set COMMAND_ON_LID_CLOSE=yes to COMMAND_ON_LID_CLOSE=no.
Make sure you have the XUSER entry set and turning off the screen should work just fine.This is great, Is it possible to have lid closure do different actions depending on power status (if ac on turn off screen, if ac off turn off eee)?
Does anyone have any suggestions on a battery monitor app? I would also like something to give me low battery warnings and maybe even be able to issue a power down command when power gets to a certain level. I have tried several apps with no luck.
Also, I have been trying to get a bluetooth headset working. I read the wiki but was unable to load snd-bt-sco. It would really cool to get this working.
Thanks
brncmp
Here's acpi-eee-8-2 with new ON_AC_LID_CLOSE_ACTION and ON_BATTERY_LID_CLOSE_ACTION variables which can be used just like you wanted.
See /etc/acpi/eee.conf for more details.
http://kapsi.fi/ighea/eee/acpi-eee/acpi … pkg.tar.gz
For battery monitoring I use gkrellm and gnome-power-manager. Gkrellm is much more than just a battery monitoring app, but it can be used only for that. You can also specify warning and alert states/messages in it.
The gnome-power-manager is mosty only for show because one can't specify low and critical battery status values or at least I couldn't find anything useful with geconf-editor. :E
Are you sure that the driver really is "snd-bt-sco" and not just "sco"? I think you should try out that one, if you have not already.
(╯°□°)╯~ ┻━┻
Offline
xfce4-battery-plugin with xfce4-panel. You can juste have a window to popup when your battery is running low, or you can execute a specific command.
For those who want to play (don't know if there's many here), juste download the PKGBUILD for wesnoth on AUR (devel version, the one in community is outdated), Add "--enable-smallgui" and you'll be able to launch the game in 800x480
Now I will update my acpi-eee, thank you ighea !
Offline
For those who want to play (don't know if there's many here), juste download the PKGBUILD for wesnoth on AUR (devel version, the one in community is outdated), Add "--enable-smallgui" and you'll be able to launch the game in 800x480
Nice tip! Thank you, I'm also one of Wesnoth fan.
Offline
Ok i got toofishes kernel to boot sorta but when i get to the "enter luks passphrase:" part and enter my password it says
device-mapper: table: 253:0: crypt: Error allocating crypto tfm device-mapper: ioctl: error adding target to table device-mapper: ioctl: device doesn't appear to be in the dev hash table. Command failed: No key available with this passphrase.
The fallback image with the stock kernel still boots fine. Can anyone guess whats going on here?
Crypto works perfectly fine here, maybe the algorithm you used for encrypting your partition isn't in twofishes kernel? Try comparing zgrep CONFIG_CRYPTO /proc/config.gz from twofishes kernel with the stock kernels config.
Offline
czar wrote:Ok i got toofishes kernel to boot sorta but when i get to the "enter luks passphrase:" part and enter my password it says
device-mapper: table: 253:0: crypt: Error allocating crypto tfm device-mapper: ioctl: error adding target to table device-mapper: ioctl: device doesn't appear to be in the dev hash table. Command failed: No key available with this passphrase.
The fallback image with the stock kernel still boots fine. Can anyone guess whats going on here?
Crypto works perfectly fine here, maybe the algorithm you used for encrypting your partition isn't in twofishes kernel? Try comparing zgrep CONFIG_CRYPTO /proc/config.gz from twofishes kernel with the stock kernels config.
How do i test that command against toofishes kernel? i can run the command but i can only boot using stock kernel. Assuming i figure out a way to test this can i use the results to fix this myself or is this just a test to see if need to start over again using supported encryption? (if its the latter then could you let me know which algorithims ARE supported?)
for reference i encrypted using the algorithms specified in the luks wiki here.
Thanks for pointing me in a direction! can't wait to get back on toofishes kernel again!
Any additional help is still much appreciated thanks!!
Offline
How do i test that command against toofishes kernel? i can run the command but i can only boot using stock kernel. Assuming i figure out a way to test this can i use the results to fix this myself or is this just a test to see if need to start over again using supported encryption? (if its the latter then could you let me know which algorithims ARE supported?)
for reference i encrypted using the algorithms specified in the luks wiki here.
Thanks for pointing me in a direction! can't wait to get back on toofishes kernel again!
Any additional help is still much appreciated thanks!!
Here is the output of the command: http://kapsi.fi/~ighea/eee/config_crypto.txt
(╯°□°)╯~ ┻━┻
Offline
czar wrote:How do i test that command against toofishes kernel? i can run the command but i can only boot using stock kernel. Assuming i figure out a way to test this can i use the results to fix this myself or is this just a test to see if need to start over again using supported encryption? (if its the latter then could you let me know which algorithims ARE supported?)
for reference i encrypted using the algorithms specified in the luks wiki here.
Thanks for pointing me in a direction! can't wait to get back on toofishes kernel again!
Any additional help is still much appreciated thanks!!Here is the output of the command: http://kapsi.fi/~ighea/eee/config_crypto.txt
The kernel config is also in my GIT repo. If you need anymore crypto modules, let me know.
http://code.toofishes.net/gitweb.cgi?p= … rnelconfig
Offline
ighea wrote:czar wrote:How do i test that command against toofishes kernel? i can run the command but i can only boot using stock kernel. Assuming i figure out a way to test this can i use the results to fix this myself or is this just a test to see if need to start over again using supported encryption? (if its the latter then could you let me know which algorithims ARE supported?)
for reference i encrypted using the algorithms specified in the luks wiki here.
Thanks for pointing me in a direction! can't wait to get back on toofishes kernel again!
Any additional help is still much appreciated thanks!!Here is the output of the command: http://kapsi.fi/~ighea/eee/config_crypto.txt
The kernel config is also in my GIT repo. If you need anymore crypto modules, let me know.
http://code.toofishes.net/gitweb.cgi?p= … rnelconfig
Thanks but i just wiped and encrypted with aes256 so now everything works perfect. turned out lrw wasn't supported by your kernel. But no matter, every install has been a learning experience. thanks for the help guys
Offline
brncmp wrote:Thanks for the updates.
ighea wrote:Sure, just set COMMAND_ON_LID_CLOSE=yes to COMMAND_ON_LID_CLOSE=no.
Make sure you have the XUSER entry set and turning off the screen should work just fine.This is great, Is it possible to have lid closure do different actions depending on power status (if ac on turn off screen, if ac off turn off eee)?
Does anyone have any suggestions on a battery monitor app? I would also like something to give me low battery warnings and maybe even be able to issue a power down command when power gets to a certain level. I have tried several apps with no luck.
Also, I have been trying to get a bluetooth headset working. I read the wiki but was unable to load snd-bt-sco. It would really cool to get this working.
Thanks
brncmpHere's acpi-eee-8-2 with new ON_AC_LID_CLOSE_ACTION and ON_BATTERY_LID_CLOSE_ACTION variables which can be used just like you wanted.
See /etc/acpi/eee.conf for more details.
http://kapsi.fi/ighea/eee/acpi-eee/acpi … pkg.tar.gzFor battery monitoring I use gkrellm and gnome-power-manager. Gkrellm is much more than just a battery monitoring app, but it can be used only for that. You can also specify warning and alert states/messages in it.
The gnome-power-manager is mosty only for show because one can't specify low and critical battery status values or at least I couldn't find anything useful with geconf-editor. :EAre you sure that the driver really is "snd-bt-sco" and not just "sco"? I think you should try out that one, if you have not already.
Thanks ighea!!
This is exactly what I wanted.
I tried gkrellm but did not like it and I'm now using gnome-power-manager for now.
However I am taking toofishs advice and I'm trying to make a acpi battery event. This is what I have so far:
In /etc/acpi/events/battery
event=battery.*
action=/etc/acpi/battery.sh
In /etc/acpi/battery.sh
#!/bin/sh
if grep -q on-line /proc/acpi/ac_adapter/AC0/state; then
exit 0
fi
BAT_DIR=/proc/acpi/battery/BAT0
FULL_BAT=`grep 'last full capacity' ${BAT_DIR}/info | awk '{ print $4 }'`
CUR_BAT=`grep 'remaining capacity' ${BAT_DIR}/state | awk '{ print $3 }'`
AVG=`expr $(expr ${CUR_BAT} \* 100) / ${FULL_BAT}`
if [ "$AVG" -le "90" ]; then
/usr/bin/showbatt
fi
Wright now battery.sh seems to works, it will call showbatt (part of osdbattery) only when ac is off line and battery is below 90%
I just cant get it to work as an event, nothing happens.
This seems like this should be easy but I'm new to scripts and acip. btw, I did not make these scripts I just found them and adjusted them.
I know the script needs work but I think this might be great way of having low battery warning while running a light weight desktop.
Thanks,
brncmp
Offline
Am I the only one to have trouble with toofishe's trick concerning alsa & shutdown?
It was working fine a few days ago, but since a fresh install, the system is simply freezing at shutdown (hanging at "the system is going to halt NOW!"), and the only solution is to hold the power button, which of course produces inconsistent fs at reboot.
[eko@nodrom ~]$ cat /etc/rc.local.shutdown
#!/bin/bash
#
# /etc/rc.local.shutdown: Local shutdown script.
#
#/etc/rc.d/alsa stop #tried with and without this line: same results.
echo -n "0000:00:1b.0" > /sys/bus/pci/drivers/HDA\ Intel/unbind
I think the pci bus is the same:
[eko@nodrom ~]$ lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)
I've also tried to execute the echo -n... command before halting and after stoping alsa, but without succes, the system is still hanging at shutdown.
Offline
Am I the only one to have trouble with toofishe's trick concerning alsa & shutdown?
It was working fine a few days ago, but since a fresh install, the system is simply freezing at shutdown (hanging at "the system is going to halt NOW!"), and the only solution is to hold the power button, which of course produces inconsistent fs at reboot.
[eko@nodrom ~]$ cat /etc/rc.local.shutdown #!/bin/bash # # /etc/rc.local.shutdown: Local shutdown script. # #/etc/rc.d/alsa stop #tried with and without this line: same results. echo -n "0000:00:1b.0" > /sys/bus/pci/drivers/HDA\ Intel/unbind
I think the pci bus is the same:
[eko@nodrom ~]$ lspci | grep Audio 00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)
I've also tried to execute the echo -n... command before halting and after stoping alsa, but without succes, the system is still hanging at shutdown.
that doesn't work for me too. actually my eee shuts down normally most of the times, but freezed with that command.
Offline
In latest version of acpi-eee, file suspend2ram.sh, I suggest to save current vt instead of always switching to 7th:
# change virtual terminal to not screw up X
vt=$(fgconsole)
chvt 6
...
chvt $vt #Back to old vt
Offline
In latest version of acpi-eee, file suspend2ram.sh, I suggest to save current vt instead of always switching to 7th:
# change virtual terminal to not screw up X vt=$(fgconsole) chvt 6 ... chvt $vt #Back to old vt
Suggestion approved.
I'll do something about that soon.
And there's a new bios version 910 available: http://forum.eeeuser.com/viewtopic.php?id=21711 .
(╯°□°)╯~ ┻━┻
Offline
@toofishes:
could you please set CONFIG_FRAMEBUFFER_CONSOLE=y in the eeepc kernel? It is required for uvesafb to work.
Offline