you have won $300,000.00 contact aluy...@yahoo.com for winning claims call our
customer service
on this number:+44 702-409-9031
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
you have won $300,000.00 contact aluy...@yahoo.com for winning claims call our
customer service
on this number:+44 702-409-9031
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at
of the driver into mainline
kernel, so users won't have to be forced to do a hardware upgrade.
Additionally, this problem prevents my machines from being upgraded from
Ubuntu 6.10 (kernel 2.6.17) to Ubuntu 7.04 (kernel 2.6.20 I believe).
With kind regards,
Wiktor Wandachowicz
[1] http://rt2x00
of the driver into mainline
kernel, so users won't have to be forced to do a hardware upgrade.
Additionally, this problem prevents my machines from being upgraded from
Ubuntu 6.10 (kernel 2.6.17) to Ubuntu 7.04 (kernel 2.6.20 I believe).
With kind regards,
Wiktor Wandachowicz
[1] http://rt2x00
Hi,
I'm using the following method and it seems to be working fine
(involving crypto-loop):
i have normal ext3 /boot partition, where i store kernel image & initrd.
after lilo boots the kernel, initrd sets up /dev/loop0 to be
crypto-loop/blowfish for /dev/hda1 (losetup /dev/loop0 /dev/hda1 -e
Hi,
I'm using the following method and it seems to be working fine
(involving crypto-loop):
i have normal ext3 /boot partition, where i store kernel image initrd.
after lilo boots the kernel, initrd sets up /dev/loop0 to be
crypto-loop/blowfish for /dev/hda1 (losetup /dev/loop0 /dev/hda1 -e
Horst von Brand wrote:
Even better: Write a C wrapper for each affected program that just renices
it as needed.
I suggest to implement scalable solution, so the final user wont't have
to write separate wrapper for *each* program. universal wrapper is
better solution, but (now i know, that
Måns Rullgård wrote:
So you are proposing the addition of a per-file attribute, with
restricted access, and potentially dangerous effects if set
incorrectly. This, combined with the fact that is unlikely to receive
much testing, all speaks against it.
Almost every attribute can be dangerous if
Måns Rullgård wrote:
So you are proposing the addition of a per-file attribute, with
restricted access, and potentially dangerous effects if set
incorrectly. This, combined with the fact that is unlikely to receive
much testing, all speaks against it.
Almost every attribute can be dangerous if
Horst von Brand wrote:
Even better: Write a C wrapper for each affected program that just renices
it as needed.
I suggest to implement scalable solution, so the final user wont't have
to write separate wrapper for *each* program. universal wrapper is
better solution, but (now i know, that
Måns Rullgård wrote:
You could wrap /lib/ld-linux.so, and get all dynamically linked
programs done in one sweep.
That's mad idea - keep similar things in one place! starting programs is
done in kernel and nice-value-support is also done in kernel!!
Using a shell to run external programs is quite
Måns Rullgård wrote:
It can be done entirely in userspace, if you want it. Just hack your
shell to examine some extended attribute of your choice, and adjust
the nice value before executing files. Then arrange to have the shell
run with a negative nice value. This can be easily accomplished
Bodo Eggert wrote:
Wiktor <[EMAIL PROTECTED]> wrote:
so i thought that it would be nice to add an attribute to file
(changable only for root) that would modify nice value of process when
it starts. if there is one byte free in ext2/3 file metadata, maybe it
could be used for that? i
Bodo Eggert wrote:
Wiktor [EMAIL PROTECTED] wrote:
so i thought that it would be nice to add an attribute to file
(changable only for root) that would modify nice value of process when
it starts. if there is one byte free in ext2/3 file metadata, maybe it
could be used for that? i think
Måns Rullgård wrote:
It can be done entirely in userspace, if you want it. Just hack your
shell to examine some extended attribute of your choice, and adjust
the nice value before executing files. Then arrange to have the shell
run with a negative nice value. This can be easily accomplished
Måns Rullgård wrote:
You could wrap /lib/ld-linux.so, and get all dynamically linked
programs done in one sweep.
That's mad idea - keep similar things in one place! starting programs is
done in kernel and nice-value-support is also done in kernel!!
Using a shell to run external programs is quite
Hi all,
recently i had to run some program (xmms) with lowered nice value as
normal user. to do that i had to su to the root account and then execute
nice --5 xmms. but, then xmms was run as root and X server refused
connection, so i had to do second su from root account. (total: su nice
--5
, where i could set up
everything sane. but now i need only links to some solutions, so i can
test them.
thanks for your help
--
May the Source be with you
Wiktor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
, where i could set up
everything sane. but now i need only links to some solutions, so i can
test them.
thanks for your help
--
May the Source be with you
Wiktor
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
and network interface). Thanks for replies.
--
May the Source be with you
Wiktor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FA
and network interface). Thanks for replies.
--
May the Source be with you
Wiktor
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
Do you still need atkbd.reset=1?
No, i don't. i've just tried it, because when keyboard was not working,
the only error report was produced by this option.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info
Wiktor, can you try atkbd.dumbkbd=1?
Here you are full dmesg (see attachment). i've been typing alphabet
after kernel boot.
atkbd.dumpkbd.gz
Description: application/gzip
It still looks OK. It seems to be a very ancient keyboard. Can you try with
a newer one? That'd tell us whether it's the controller or the keyboard
that is giving problems.
What keyboard model is it? What machine?
Machine info attached as a part of /dev/proc. i've tried with another AT
keyboard
It still looks OK. It seems to be a very ancient keyboard. Can you try with
a newer one? That'd tell us whether it's the controller or the keyboard
that is giving problems.
What keyboard model is it? What machine?
Machine info attached as a part of /dev/proc. i've tried with another AT
keyboard
Wiktor, can you try atkbd.dumbkbd=1?
Here you are full dmesg (see attachment). i've been typing alphabet
after kernel boot.
atkbd.dumpkbd.gz
Description: application/gzip
Do you still need atkbd.reset=1?
No, i don't. i've just tried it, because when keyboard was not working,
the only error report was produced by this option.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Hi,
We do test AUX port and your port appears to be perfectly functional
from the kernel point of view - it porperly responds to AUX_LOOP
commands, does not claim to support MUX mode and KBC properly sets
status register when asked to disable interface...
ok, but how AUX block KBD port? if
Hi,
Could you please try editing drivers/input/serio/i8042.c and add
udelay(20) before and after calls to i8042_write_data() in
i8042_kbd_write() and i8042_command().
of course i could, will it make kernel not detect smoked AUX port?
(problem is solved by i8042.noaux=1 cause my hardware has
Hi, IT WORKED!
Please try i8042.noaux=1. You say you're using a serial mouse in your
other e-mail, so the system may not have an AUX port yet the kernel
thinks it does. This may cause the keyboard to stop responding.
command line "linux-new init=/bin/bash i8042.noaux=1 atkbd.reset=1"
booted
Hi,
This dmesg looks like the keyboard works perfectly OK. Do new lines
appear in dmesg when you press keys while the system is running?
.no? no, they don't. i've new dmesg for you - it reports
timeouts while trying to perform keyboard reset (by atkbd.reset=1).
after detection
Hi,
This dmesg looks like the keyboard works perfectly OK. Do new lines
appear in dmesg when you press keys while the system is running?
.no? no, they don't. i've new dmesg for you - it reports
timeouts while trying to perform keyboard reset (by atkbd.reset=1).
after detection
Hi, IT WORKED!
Please try i8042.noaux=1. You say you're using a serial mouse in your
other e-mail, so the system may not have an AUX port yet the kernel
thinks it does. This may cause the keyboard to stop responding.
command line linux-new init=/bin/bash i8042.noaux=1 atkbd.reset=1
booted 2.6.8.1
Hi,
Could you please try editing drivers/input/serio/i8042.c and add
udelay(20) before and after calls to i8042_write_data() in
i8042_kbd_write() and i8042_command().
of course i could, will it make kernel not detect smoked AUX port?
(problem is solved by i8042.noaux=1 cause my hardware has
Hi,
We do test AUX port and your port appears to be perfectly functional
from the kernel point of view - it porperly responds to AUX_LOOP
commands, does not claim to support MUX mode and KBC properly sets
status register when asked to disable interface...
ok, but how AUX block KBD port? if
Hi,
here you are gzip-ed dmesg from booting 2.6.8.1 - i've been playing
keyboard while booting, maybe interrupt reports will help you. also my
.config part follows:
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_INPUT_KEYBOARD=y
Hi,
here you are gzip-ed dmesg from booting 2.6.8.1 - i've been playing
keyboard while booting, maybe interrupt reports will help you. also my
.config part follows:
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_INPUT_KEYBOARD=y
Dmitry Torokhov wrote:
Hi,
What kernel version are you using? Have you tried 2.6.8.1? - it looks
like changes in 2.6.9-rc2-bk3 caused problems on some hardware.
Hi,
it looks like 2.6.10 (which I was using) - serio ports are detected ok
(both on 0x60,0x64, keyboard irq 1, aux irq 12), keyboard
to tell him (eg. atkbd.reset preforms keyboard reset but reports
error). Were any hadrware-handling changes made since 2.4? If so, how to
undo them and make keyboard alive? I'm grateful for any help.
---
May the Source be with you.
Wiktor
-
To unsubscribe from this list: send the line
to tell him (eg. atkbd.reset preforms keyboard reset but reports
error). Were any hadrware-handling changes made since 2.4? If so, how to
undo them and make keyboard alive? I'm grateful for any help.
---
May the Source be with you.
Wiktor
-
To unsubscribe from this list: send the line
Dmitry Torokhov wrote:
Hi,
What kernel version are you using? Have you tried 2.6.8.1? - it looks
like changes in 2.6.9-rc2-bk3 caused problems on some hardware.
Hi,
it looks like 2.6.10 (which I was using) - serio ports are detected ok
(both on 0x60,0x64, keyboard irq 1, aux irq 12), keyboard
Hi,
my AT keyboard is dead on 2.6.10. .config was produced by "make
defconfig" (procesor changed to i586) - attached as gz. System works ok,
all programs run but keyboard is like unplugged (but it is plugged of
course). Here is kernel bootup:
Jan 15 20:11:02 wiktor kernel: Linux vers
Hi,
my AT keyboard is dead on 2.6.10. .config was produced by make
defconfig (procesor changed to i586) - attached as gz. System works ok,
all programs run but keyboard is like unplugged (but it is plugged of
course). Here is kernel bootup:
Jan 15 20:11:02 wiktor kernel: Linux version 2.6.10
43 matches
Mail list logo
