Re: Please test xkb-data 0.8-12exp2 in experimental
On Mon, 2006-09-18 at 19:11 +, Jörg Sommer wrote: Why is Fn+6 num_lock? On my system, (powerbook 5,6), Fn+F6 -is- numlock (but I thought it was handled by the kernel) -- Yves-Alexis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: powerpc d-i daily ISOs are back but broken. (was: one week out of date. )
On Fri, Sep 15, 2006 at 04:55:02PM +0200, Wouter Verhelst wrote: On Fri, Sep 15, 2006 at 11:24:02AM +0200, Sven Luther wrote: someone who does the whole stuff, right ? It was an honest question, why do you respond so agressively ? Maybe because the question was asked in a rather aggressive tone? That's at least what it looked to IMNSHO. Bah, ... First, i am still hurt over how i was threated, and nobody is ever going to aknowledge that i was not the only guy responsible in this whole disaster, and the only one who actually openly recognized his errors and tried to work on it in a positive way. It has been going for months now, and there is no sign that it changes, and yes, doing the submit-patch-to-BTS plays hell with one's svn checkout, especially if the patch is changed a bit before being applied, or is not applied immediately. Second, i am not the only using a bit-more-aggresive-than-usual wordings, Frans itself is not someone who has been addressing me in the nicest way lately, but also since fall last year or even earlier, so he can hardly complain. I don't see why i should be held to a different criteria than all the rest of the debian developers, especially, as Frans, who is clearly not neutral in this, is supposed to be judge over my behaviour. Furthermore, if frans is saying stupid things or is plainly in error, i don't see why i should not say so, as i have a right to do, without him feeling offended. Third, it has been months now, and there is no sign that anything will change in this, so being handled like a sub-DD for d-i purpose is clearly very very poor on motivation, either for doing work, or for being over-nice. Fourth, Frans was quick to kick me out, but he failed in his implicit promise to find a replacement for the d-i port, even despite the laudable efforts done by you and Colin. So, all in all, the ball is now in Frans and the d-i team's camp, i did all i was asked to do, i played nice, but there is no visible return to it, and Frans can at any time feel offended by the slightest of not-over-nice comments i made. This has been going for too long now, and altough the d-i team may discutabily have had some reason back then in april/may, it is currently not valide any more, and is hurting both me and our powerpc users, and yes, it is only due to stuborness and childish 'i always need to be right' on frans and the d-i's team part. Anyway, i expect nothing of them, i did my part, i am acting correctly since some time, and any team who believes in a dictatorial concept of trying to block one fellow's right to technical expression by tactics as these is not dign to be part of debian. An no, i don't believe an in-face discussion will in any way change the above without at least some token action on the other side's part on this, like said, the ball is in the other side's camp, there is nothing i can do more. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please test xkb-data 0.8-12exp2 in experimental
On Sun, Sep 17, 2006 at 11:24:26AM +0200, Denis Barbier wrote: Hi, xkb-data 0.8-12exp2 is in experimental. The macintosh_old2 version has been removed from this version, there are only 2 models: - macintosh_old (old kernels with ADB keycodes) - macintosh (new kernels with PC keycodes) This logs me out of a running underprivileged user X: [output slightly shortened for better readability]: -- $ ll usr ls: usr: No such file or directory $ dpkg -x /home/shorty/downloads/xkb-data_0.8-12exp2_all.deb . $ cd usr/share/X11/xkb/ $ setxkbmap -option -model macintosh -layout de -variant nodeadkeys -print | xkbcomp - :0 Is the log-out a feature or a bug? -- $ cat /proc/cpuinfo processor : 0 cpu : 7447A, altivec supported clock : 833.333000MHz revision: 0.5 (pvr 8003 0105) bogomips: 16.57 timebase: 832 platform: PowerMac machine : PowerBook5,8 motherboard : PowerBook5,8 MacRISC3 Power Macintosh detected as : 287 (PowerBook G4 15) pmac flags : 0019 L2 cache: 512K unified pmac-generation : NewWorld Thanks in anticipation Best Regards Wolfgang -- Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/ http://profiles.yahoo.com/wolfgangpfeiffer Key ID: E3037113 http://keyserver.mine.nu/pks/lookup?search=0xE3037113fingerprint=on -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Regression in sleep code for PowerBook5,2
On 15/09/06, Eddy Petrişor [EMAIL PROTECTED] wrote: On 03/09/06, Benjamin Herrenschmidt [EMAIL PROTECTED] wrote: On Sun, 2006-09-03 at 04:02 +0300, Eddy Petrişor wrote: Ok, I will take the debian configuration and test with linus' current tree (bah, git, again; it was not such a pleasent experience last time I tried it). Done, tried it. Almost same result. The screen went blank before blocking once and blocked as before another time. This is strange. I have been running the 2.6.18-rc5 (curent git at the time) for some time now and I haven't encountered the problem anymore. Hmm, this is really odd. The problems are there, it seems that somehow I managed to trick myself into thinking this was stable. The problems definetly did NOT disappear. Also, with the old kernel I haven't experienced locks (although at first I remember one happening). OTOH, the old kernel doesn't have the r300 driver compatible with the new mesa which I need because I am in the Debian Games Team and need it for accelerated grapihcs. -- Regards, EddyP = Imagination is more important than knowledge A.Einstein
pbbuttons - issues with lidclose-display off options (backlight remains off)
Hello, I am not sure if the reason behind this problem is pbbuttonsd, although I am fairly sure, I want to have a confirmation (this happens from time to time on my laptop). I have configured pbuttonsd to just turn off the display when on AC and the lid is closed. I found that, sometimes, when opening the lid again, the backlight will not be turned back on (I can see the locking screen of KDE); if I try o swith to a text console, the backlight is turned back on for a split second, I can see the display properly, then is back to off. Switching back and forth between the X console and a text console does not fix the issue, but the light-on-for-a-split-second thing is present. Also I have found that I can work arund the issue if I put the laptop to sleep and wake it up. (But even this work around doesn't always work for me since I am experincing lock-ups before sleep - nobody has an idea why). Does anybody else has this issues? Can someone confirm this? How can I fix it? Help would be appreciated. 8 $ LANG=C apt-cache policy pbbuttonsd pbbuttonsd: Installed: 0.7.5-2 Candidate: 0.7.5-2 Version table: *** 0.7.5-2 0 900 http://ftp.ro.debian.org unstable/main Packages 900 http://snapshot.debian.net unstable/main Packages 100 /var/lib/dpkg/status 8 $ uname -a Linux merci 2.6.18-rc5-merci #1 Wed Sep 13 23:44:36 EEST 2006 ppc GNU/Linux compiled from Linus' git version as it was on 2006-09-02 00:35:01.0 +0300 8 $ cat /etc/pbbuttonsd.conf # Configuration file for pbbuttonsd = version 0.5 # for options see man pbbuttonsd.conf [SYSTEM] #userallowed = ; user who is allowed to use IPC autorescan= yes ; automatic rescan of event devices CmdTimeout= 8 ; timeout in seconds for launched scripts, etc. [MODULE PMAC] dev_PMU = /dev/pmu dev_ADB = /dev/adb TPModeUpKey = 225 + alt TPModeDownKey = 224 + alt TPMode= drag; 'notap', 'tap', 'drag' or 'lock' KBDMode = fkeysfirst ; 'disabled', 'fkeyslast' or 'fkeysfirst' Batlog= log ; 'none', 'cycle' or 'log' NoTapTyping = yes ; switch trackpad to 'notap-mode' while typing [MODULE POWERSAVE] onAC_Policy = performance ; 'nochange', 'powersave', 'custom' or 'performance' onAC_TimerAction = none; 'none', 'suspend-to-ram', 'suspend-to-disk', 'blankscreen' or 'shutdown' #onAC_CoverAction = suspend-to-ram ; see TimerAction for possible values onAC_CoverAction = blankscreen ; see TimerAction for possible values onAC_KeyAction= suspend-to-ram ; Action (see TimerAction) for the sleepkey onAC_SuspendTime = 36000 onAC_DimTime = 0 onBattery_Policy = powersave ; 'nochange', 'powersave', 'custom' or 'performance' onBattery_TimerAction = suspend-to-ram ; 'none', 'suspend-to-ram', 'suspend-to-disk', 'blankscreen' or 'shutdown' onBattery_CoverAction = suspend-to-ram ; see TimerAction for possible values onBattery_KeyAction = suspend-to-ram ; Action (see TimerAction) for the sleepkey onBattery_SuspendTime = 3000 #onBattery_DimTime = 1200 onBattery_DimTime = 0 SleepKey = 116 SleepKeyDelay = 0 ; values 0 may be dangerous, if the power key is used to trigger sleep BWL_first = 22 ; first battery warnlevel, time in minutes BWL_second= 10 ; second battery warnlevel, time in minutes BWL_last = 5 ; last battery warnlevel, time in minutes Script_PMCS = /etc/power/pmcs-pbbuttonsd %s %s %s EmergencyAction = sleep ; action, if battery is critically low HeartbeatBeep = yes ; beep, if nothing else showed that the computer lives CPULoad_sleeplock = yes CPULoad_min = 5 ; value in percent CPULoad_period= 20 ; time in seconds NETLoad_sleeplock = yes NETLoad_min = 4096; traffic in Bytes/s NETLoad_period= 20 ; time in seconds NETLoad_device= eth0 tun0 IBAM_DataDir = /var/lib/ibam [MODULE DISPLAY] LCD_Brightness= 15 ; initial LCD brightness level LCD_FadingSpeed = 5 ; 0 = no smooth fading LCD_AutoAdjust= yes ; only on Aluminum PowerBooks LCD_IllumUpKey= 225 LCD_IllumDownKey = 224 LCD_Threshold = 94 ; ambient light threshold in percent for backlight autoadj. LCD_AutoAdjMin_Bat= 2 ; autoadjustment range parameters LCD_AutoAdjMax_Bat= 7 LCD_AutoAdjMin_AC = 1 LCD_AutoAdjMax_AC = 15 KBD_Brightness= 0 ; initial keyboard illumination level KBD_OnBrightness = 5 ; initial level if KBD
Re: Regression in sleep code for PowerBook5,2
On Wed, 2006-09-20 at 14:26 +0300, Eddy Petrişor wrote: OTOH, the old kernel doesn't have the r300 driver compatible with the new mesa which I need because I am in the Debian Games Team and need it for accelerated grapihcs. Building the DRM from git is easy, see http://dri.freedesktop.org/wiki/Building#head-d3dcc7d83ae38d3b36f7f23ddcd4f5268396b2b4 . -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Installation report Quicksilver 733 MHz G4
I tried the regular install. The keyboard selection step hung (khubd was in uninterruptible wait). I got around that by killing processes. I omitted the usb-storage module but a later HW detection step still tried to load it. I had to kill another process. The final installation report HW detection also hung and I had to kill a process. The box rebooted for phase 2 and the boot hung with: Detecting hardware: drivers/usb/input/hid-core.c: ctrl urb status -2 received drivers/usb/input/hid-core.c: usb_submit_urb(ctrl) failed I haven't tried install-2.4 yet. John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pbbuttons - issues with lidclose-display off options (backlight remains off)
On Wednesday 20 September 2006 13:52, Eddy Petrişor wrote: Hello, I am not sure if the reason behind this problem is pbbuttonsd, although I am fairly sure, I want to have a confirmation (this happens from time to time on my laptop). I have configured pbuttonsd to just turn off the display when on AC and the lid is closed. I found that, sometimes, when opening the lid again, the backlight will not be turned back on (I can see the locking screen of KDE); if I try o swith to a text console, the backlight is turned back on for a split second, I can see the display properly, then is back to off. Switching back and forth between the X console and a text console does not fix the issue, but the light-on-for-a-split-second thing is present. Also I have found that I can work arund the issue if I put the laptop to sleep and wake it up. (But even this work around doesn't always work for me since I am experincing lock-ups before sleep - nobody has an idea why? Does anybody else has this issues? Can someone confirm this? How can I fix it? Not exactly that issue, but the the dim down when not active works this way with my pb. however if you close to blind, if not in bright light (or know exactly what to write (witch is /etc/init.d/pbbuttonsd restart) at console) - no use continuing the sentence since my point is written. That fixes it for the time being. Comment the corresponding line in pbbuttons.conf to be rid of the problem. On the other hand, whats wrong? dunno. maby it stops taking the adb kbd or usb/bt mouse as input/movement (witch happened once'n while with my x86 compute). Now if you do not set the dim console to option, you can switch to console and that part should work as normal. UseFBBlank= yes/no - this one I think. Help would be appreciated. 8 $ LANG=C apt-cache policy pbbuttonsd pbbuttonsd: Installed: 0.7.5-2 Candidate: 0.7.5-2 Version table: *** 0.7.5-2 0 900 http://ftp.ro.debian.org unstable/main Packages 900 http://snapshot.debian.net unstable/main Packages 100 /var/lib/dpkg/status 8 $ uname -a Linux merci 2.6.18-rc5-merci #1 Wed Sep 13 23:44:36 EEST 2006 ppc GNU/Linux compiled from Linus' git version as it was on 2006-09-02 00:35:01.0 +0300 8 $ cat /etc/pbbuttonsd.conf # Configuration file for pbbuttonsd = version 0.5 # for options see man pbbuttonsd.conf [SYSTEM] #userallowed = ; user who is allowed to use IPC autorescan= yes ; automatic rescan of event devices CmdTimeout= 8 ; timeout in seconds for launched scripts, etc. [MODULE PMAC] dev_PMU = /dev/pmu dev_ADB = /dev/adb TPModeUpKey = 225 + alt TPModeDownKey = 224 + alt TPMode= drag; 'notap', 'tap', 'drag' or 'lock' KBDMode = fkeysfirst ; 'disabled', 'fkeyslast' or 'fkeysfirst' Batlog= log ; 'none', 'cycle' or 'log' NoTapTyping = yes ; switch trackpad to 'notap-mode' while typing [MODULE POWERSAVE] onAC_Policy = performance ; 'nochange', 'powersave', 'custom' or 'performance' onAC_TimerAction = none; 'none', 'suspend-to-ram', 'suspend-to-disk', 'blankscreen' or 'shutdown' #onAC_CoverAction = suspend-to-ram ; see TimerAction for possible values onAC_CoverAction = blankscreen ; see TimerAction for possible values onAC_KeyAction= suspend-to-ram ; Action (see TimerAction) for the sleepkey onAC_SuspendTime = 36000 onAC_DimTime = 0 onBattery_Policy = powersave ; 'nochange', 'powersave', 'custom' or 'performance' onBattery_TimerAction = suspend-to-ram ; 'none', 'suspend-to-ram', 'suspend-to-disk', 'blankscreen' or 'shutdown' onBattery_CoverAction = suspend-to-ram ; see TimerAction for possible values onBattery_KeyAction = suspend-to-ram ; Action (see TimerAction) for the sleepkey onBattery_SuspendTime = 3000 #onBattery_DimTime = 1200 onBattery_DimTime = 0 SleepKey = 116 SleepKeyDelay = 0 ; values 0 may be dangerous, if the power key is used to trigger sleep BWL_first = 22 ; first battery warnlevel, time in minutes BWL_second= 10 ; second battery warnlevel, time in minutes BWL_last = 5 ; last battery warnlevel, time in minutes Script_PMCS = /etc/power/pmcs-pbbuttonsd %s %s %s EmergencyAction = sleep ; action, if battery is critically low HeartbeatBeep = yes ; beep, if nothing else showed that the computer lives CPULoad_sleeplock = yes CPULoad_min = 5 ; value in percent CPULoad_period= 20 ; time in seconds
Re: Please test xkb-data 0.8-12exp2 in experimental
On Wed, Sep 20, 2006 at 12:47:22PM +0200, Wolfgang Pfeiffer wrote: On Sun, Sep 17, 2006 at 11:24:26AM +0200, Denis Barbier wrote: Hi, xkb-data 0.8-12exp2 is in experimental. The macintosh_old2 version has been removed from this version, there are only 2 models: - macintosh_old (old kernels with ADB keycodes) - macintosh (new kernels with PC keycodes) This logs me out of a running underprivileged user X: [output slightly shortened for better readability]: -- $ ll usr ls: usr: No such file or directory $ dpkg -x /home/shorty/downloads/xkb-data_0.8-12exp2_all.deb . $ cd usr/share/X11/xkb/ $ setxkbmap -option -model macintosh -layout de -variant nodeadkeys -print | xkbcomp - :0 Is the log-out a feature or a bug? A bug, of course ;) You have the same configuration as Helge Kreutzmann, can you please have a look at http://bugs.debian.org/387917 and follow instructions there? Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Regression in sleep code for PowerBook5,2
OTOH, the old kernel doesn't have the r300 driver compatible with the new mesa which I need because I am in the Debian Games Team and need it for accelerated grapihcs. It could be a problem with DRI and r300.. There are some fixes going in real soon that might help. Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installation report Quicksilver 733 MHz G4
OK, install-2.4 ramdisk_size=13000 worked. Now I need to figure out how to get X and the network set up. I have an nVidia GeForce 2 MX. I have an original AirPort card and a DLink wireless router using WPA. I also need an IPSec/L2TP client. Oh, and I also need to set up my Bluetooth Mighty Mouse (via DLink DBT-120). John On Sep 19, 2006, at 10:33 PM, John Dalbec wrote: I tried the regular install. The keyboard selection step hung (khubd was in uninterruptible wait). I got around that by killing processes. I omitted the usb-storage module but a later HW detection step still tried to load it. I had to kill another process. The final installation report HW detection also hung and I had to kill a process. The box rebooted for phase 2 and the boot hung with: Detecting hardware: drivers/usb/input/hid-core.c: ctrl urb status -2 received drivers/usb/input/hid-core.c: usb_submit_urb(ctrl) failed I haven't tried install-2.4 yet. John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
