Re: volunteer to fix ALSA for every PPC subarch found! :-)
> > I can provide almost all the necessary informations. I have specs for > > most chips, and those I don't have spec for have Darwin drivers that > > should tell us all we need to know. > > > > There are several issues though, as I wrote earlier. More than just > > "fixups", we need some real re-architecture of the driver. We need to > > properly separate the transport layer (can be davbus or i2s) from the > > codecs, deal with multiple codecs (G5s have that typically) and multiple > > transport busses (some machines have codecs on the 2 i2s interfaces), we > > need to properly reprogram the i2s clocks, we need to do clock switching > > when fed with a digital input signal, etc... > > > > Also, on pretty much all recent machines, the only info that you have > > about the sound hardware is an "ID" value in the device-tree. Apple code > > matches that value with some XML structure in the driver property list > > that indicates what set of codecs etc... to use. > > > > I don't have time to actually do the work, but I'm willing to help. > > Adding the above info as a comment to the ALSA BTS bug I opened would already > be > a tremendous start. :) Please do it for me, I can't be bothered opening yet another account to some random BTS ... Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: volunteer to fix ALSA for every PPC subarch found! :-)
On Tue, 9 Aug 2005, Benjamin Herrenschmidt wrote: I can provide almost all the necessary informations. I have specs for most chips, and those I don't have spec for have Darwin drivers that should tell us all we need to know. There are several issues though, as I wrote earlier. More than just "fixups", we need some real re-architecture of the driver. We need to properly separate the transport layer (can be davbus or i2s) from the codecs, deal with multiple codecs (G5s have that typically) and multiple transport busses (some machines have codecs on the 2 i2s interfaces), we need to properly reprogram the i2s clocks, we need to do clock switching when fed with a digital input signal, etc... Also, on pretty much all recent machines, the only info that you have about the sound hardware is an "ID" value in the device-tree. Apple code matches that value with some XML structure in the driver property list that indicates what set of codecs etc... to use. I don't have time to actually do the work, but I'm willing to help. Adding the above info as a comment to the ALSA BTS bug I opened would already be a tremendous start. :) Please do it for me, I can't be bothered opening yet another account to some random BTS ... Given how you already have a clear strategy in mind for the rearchitecturing of the ALSA PowerMac subsystem, it would probably be a good idea for you to come and participate in the thread on the ALSA BTS for this bug, so you can guide the ALSA team and explain to them exactly what you have in mind. NOTE: I sympatize with the account creation complaint. I in fact pointed out to the ALSA people that they are not likely to get PowerMac users to report every broken ALSA item they encounter, because of the account creation obligation. I also suggested that they adopt an e-mail filtering based aproach similar to the Debian BTS, instead, as a way of making it easier for people to report bugs. -- Martin-Eric Racine http://q-funk.iki.fi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
MOL packages to be orphaned.
Hi all. As a result of an unfortunate accident, Jens Schmalzing passed away. He was the maintainer of, amongst others, mol, mol-drivers-linux, mol-modules-* and mol-drivers-macos* [0]. Thus, in the very near future, those package will be orphaned. Please, if someone has the time and the needed skils to adopt those packages, proceed to do so. I cannot do it myself due to the lack of both of the aforementioned requirements. Thanks. -- Jesus Climent info:www.pumuki.org Unix SysAdm|Linux User #66350|Debian Developer|2.6.12|Helsinki Finland GPG: 1024D/86946D69 BB64 2339 1CAA 7064 E429 7E18 66FC 1D7F 8694 6D69 Look at my fingers: four stones, four crates. Zero stones? ZERO CRATES! --Zorg (The Fifth Element) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: MOL packages to be orphaned.
On Tue, Aug 09, 2005 at 01:15:18PM +0200, Jesus Climent wrote: > Hi all. > > As a result of an unfortunate accident, Jens Schmalzing passed away. > > He was the maintainer of, amongst others, mol, mol-drivers-linux, > mol-modules-* and mol-drivers-macos* [0]. [0] The complete list can be found here: http://qa.debian.org/[EMAIL PROTECTED] -- Jesus Climent info:www.pumuki.org Unix SysAdm|Linux User #66350|Debian Developer|2.6.12|Helsinki Finland GPG: 1024D/86946D69 BB64 2339 1CAA 7064 E429 7E18 66FC 1D7F 8694 6D69 Look at my fingers: four stones, four crates. Zero stones? ZERO CRATES! --Zorg (The Fifth Element) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: My Debian/MacMini web pages
On Aug 8, 2005, at 5:10 AM, Dean Hamstead wrote: macosx has the same locked root as ubuntu to enable root, log in as an user with admin privileges. then open a shell sudu bash put in your password youll then be in a bash shell as root, you can then go passwd change your root password. then you can 'su' to root. This is the hard way to do it. Instead, in OS-X, launch NetInfo (Bootdisk->Applications->Utilities->NetInfo Manager) and select the "Security" menu. One of the selections allows you to unlock the root account & set its password. Dan Killoran -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
PR05 of Sarge-based Debian-edu, also for PowerPC
We've now release pr05 of Debian-edu, both for i386 and for Powerpc. I would very much like to get feedback from users of other PowerPC's than pegasos (I would like feedback from pegasos users as well) As far as I know, there is only 1 limitation: Automatic partitioning is not working for the Main Profile, which is the Server profile. A Short description of the different profiles: Main - file,email,web,dns,dhcp,print,ldap (and more) server Thin Client Server - Set up thin client using lessdisks Workstation - based on KDE Thin client server and Workstation needs to have a main-server - it could be the same host (combined mainserver and workstation or thin-client-server) There is also a Standalone profile, which are ment to be used without any Mainserver. look at http://www.skolelinux.org/portal/get_started/download for download instructions -- Finn-Arne Johansen [EMAIL PROTECTED] http://bzz.no/ PreRelease manager for sarge-based Debian-edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pbbuttonsd, synaptics and sleep on lid close
On Sun, 7 Aug 2005 19:21:53 +0200 Luca Bigliardi - shammash <[EMAIL PROTECTED]> wrote: > > Hi, > below you can find a little patch for pbbuttonsd that partially solve > the incompatibility with mouses (in absolute mode) > managed by synaptics x module. > > With this patch you don't need anymore to change "/dev/adb" in > "/dev/null" in pbbuttonsd.conf > > > Now i'll try to know why mouse movements are ignored by pbbuttonsd: > sometimes you have to press a key on the keyboard or it performs the > timer action. Have a look at event_handler() in input_manager.c. You will see that only keyboard events and relative mouse events are processed. Any other event will be ignored. Best Regrads Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pbbuttonsd, synaptics and sleep on lid close
On Tue, 2005-08-09 at 19:33 +0200, Matthias Grimm wrote: > Have a look at event_handler() in input_manager.c. You will see that > only keyboard events and relative mouse events are processed. Any > other event will be ignored. That's obviously the problem. For synaptics compatibility, the appletouch driver reports absolute events. Could you change the code to also reset the timer on absolute mouse events? (What is the reason for not resetting the timer on them?) For reference, here's the cev output of the appletouch driver: [7] ids - 3 5ac 20e 7 Name: appletouch Supported Events: 0 (Reset) 1 (Key) 3 (Absolute) or from evtest: Input driver version is 1.0.0 Input device ID: bus 0x3 vendor 0x5ac product 0x20e version 0x7 Input device name: "appletouch" Supported events: Event type 0 (Reset) Event code 0 (Reset) Event code 1 (Key) Event code 3 (Absolute) Event type 1 (Key) Event code 272 (LeftBtn) Event code 325 (ToolFinger) Event code 330 (Touch) Event code 333 (?) Event code 334 (?) Event type 3 (Absolute) Event code 0 (X) Value644 Min0 Max 959 Fuzz 16 Event code 1 (Y) Value385 Min0 Max 644 Fuzz 16 Event code 24 (Pressure) Value 0 Min0 Max 300 johannes signature.asc Description: This is a digitally signed message part
Re: pbbuttonsd, synaptics and sleep on lid close
On Tue, 09 Aug 2005 20:35:14 +0200 Johannes Berg <[EMAIL PROTECTED]> wrote: > On Tue, 2005-08-09 at 19:33 +0200, Matthias Grimm wrote: > > > Have a look at event_handler() in input_manager.c. You will see that > > only keyboard events and relative mouse events are processed. Any > > other event will be ignored. > > That's obviously the problem. For synaptics compatibility, the > appletouch driver reports absolute events. > > Could you change the code to also reset the timer on absolute mouse > events? (What is the reason for not resetting the timer on them?) Yes, I will do it. What does the appletouch device report on /dev/adb? Does lsadb report anything about the touchpad? The reason to block absolute events is simple: Nobody needed them till now. Best Regards Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pbbuttonsd, synaptics and sleep on lid close
On Tue, 2005-08-09 at 21:42 +0200, Matthias Grimm wrote: > Yes, I will do it. What does the appletouch device report on /dev/adb? > Does lsadb report anything about the touchpad? Nothing, it isn't an adb device at all, it's usb. johannes signature.asc Description: This is a digitally signed message part
Re: pbbuttonsd, synaptics and sleep on lid close
On Tue, 09 Aug 2005 20:35:14 +0200 Johannes Berg <[EMAIL PROTECTED]> wrote: Sourceforge CVS is down for maintenance till Tuesday morning (CET) so I can't upload the patched version. Please checkout CVS late afternoon on Tuesday (CET). I think I got it up till then. This includes the patch from Luca. Best Regards Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pbbuttonsd, synaptics and sleep on lid close
On Tue, 09 Aug 2005 22:03:38 +0200 Johannes Berg <[EMAIL PROTECTED]> wrote: > On Tue, 2005-08-09 at 21:42 +0200, Matthias Grimm wrote: > > > Yes, I will do it. What does the appletouch device report on /dev/adb? > > Does lsadb report anything about the touchpad? > > Nothing, it isn't an adb device at all, it's usb. But if reading /dev/adb couldn't find the device, what would Luca's patch change? Best Regards Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pbbuttonsd, synaptics and sleep on lid close
On Tue, 2005-08-09 at 22:25 +0200, Matthias Grimm wrote: > But if reading /dev/adb couldn't find the device, what would Luca's patch > change? Hmmm. Maybe Luca doesn't have a new model with USB actually, and I just thought so. johannes signature.asc Description: This is a digitally signed message part
Re: PR05 of Sarge-based Debian-edu, also for PowerPC
Finn-Arne Johansen wrote: We've now release pr05 of Debian-edu, both for i386 and for Powerpc. look at http://www.skolelinux.org/portal/get_started/download for download instructions Hi , looking at http://d.skolelinux.no/dokumentasjon/debian-edu_sarge_installation.txt 1. I fount a 'typo' in 'First stage installation' ... for normal 2.6 kernel installation, type _linuix26_ the CD boot prompt ... 2. Using i.e. :Debian-edu-config upgraded to 0.398+svn4246 (from 0.398+svn3920) * Finn-Arne Johansen - Replaced all occurences of "installasjon" with "installation" maybe you may change also the norvegian spelling in 'http://d.skolelinux.no/_dokumentasjon_' Thanks for all your works. Eugen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
X.org (gdm?) stopped working
I bravely managed to screw up again... I had foolishly tried to be on the bleeding edge, and bleed I did... After some days of happily using X.org, Gnome 2.10, OpenOffice.org2 and even -- oh glory! -- emacs-snapshot-gtk, I discovered my iBook rebooted (quite common, I have a faulty power connection) and X screwed. I get the grey background with X-shaped cursor in VC7, and a dialog in VC8 stating that X is already running, and would I like to have it try another display number? No matter what I do, nothing works. If I answer no, I end up with the same grey background in VC8, and the dialog on VC7; if yes, the sitation stays the same I have checked /var/log, and the only interesting thing was /var/log/gdm/:0.log: Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. Problem is, if I do kill the running servers with C-A-Backspace /tmp/.X0-lock, so this helps me nothing. Also in /tmp is a .gdm_socket. I found nothing else that seemed like helping me. What should I do next? I cringe at the thought of reinstalling XFree86 and Gnome 2.8... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X.org (gdm?) stopped working
Leandro Guimaraes Faria Corcete DUTRA dutra.fastmail.fm> writes: > I bravely managed to screw up again... Sorry for the autoreply, but I just remembered to include gdm debug output, I hope it's not excessive to post here: Aug 9 23:32:37 c gdm[15094]: gdm_main: Here we go... Aug 9 23:32:37 c gdm[15094]: gdm_start_first_unborn_local: Starting :0 Aug 9 23:32:37 c gdm[15094]: gdm_display_manage: Managing :0 Aug 9 23:32:37 c gdm[15094]: loop check: last_start 0, last_loop 0, now: 1123641157, retry_count: 0 Aug 9 23:32:37 c gdm[15094]: Resetting counts for loop of death detection Aug 9 23:32:37 c gdm[15095]: gdm_slave_start: Starting slave process for :0 Aug 9 23:32:37 c gdm[15095]: gdm_slave_start: Loop Thingie Aug 9 23:32:37 c gdm[15095]: Sending VT_NUM == -1 for slave 15095 Aug 9 23:32:37 c gdm[15095]: Sending VT_NUM 15095 -1 Aug 9 23:32:37 c gdm[15094]: gdm_display_manage: Forked slave: 15095 Aug 9 23:32:37 c gdm[15094]: Handling message: 'VT_NUM 15095 -1' Aug 9 23:32:37 c gdm[15094]: Got VT_NUM == -1 Aug 9 23:32:37 c gdm[15094]: (child 15095) gdm_slave_usr2_handler: :0 got USR2 signal Aug 9 23:32:37 c gdm[15095]: gdm_server_start: :0 Aug 9 23:32:37 c gdm[15095]: gdm_auth_secure_display: Setting up access for :0 Aug 9 23:32:37 c gdm[15095]: gdm_auth_secure_display: Setting up access Aug 9 23:32:37 c gdm[15095]: gdm_auth_secure_display: Setting up access for :0 - 1 entries Aug 9 23:32:37 c gdm[15095]: Sending COOKIE == for slave 15095 Aug 9 23:32:37 c gdm[15095]: Sending COOKIE 15095 6... Aug 9 23:32:37 c gdm[15094]: Handling message: 'COOKIE 15095 6...' Aug 9 23:32:37 c gdm[15094]: Got COOKIE == Aug 9 23:32:37 c udev[15097]: creating device node '/dev/vcs8' Aug 9 23:32:37 c udev[15101]: creating device node '/dev/vcsa8' Aug 9 23:32:37 c gdm[15095]: gdm_server_spawn: Forked server on pid 15109 Aug 9 23:32:37 c gdm[15095]: do_server_wait: Before mainloop waiting for server Aug 9 23:32:37 c gdm[15094]: (child 15095) gdm_slave_usr2_handler: :0 got USR2 signal Aug 9 23:32:37 c gdm[15109]: gdm_server_spawn: '/usr/X11R6/bin/X :0 -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt8' Aug 9 23:32:38 c gdm[15094]: (child 15095) gdm_server_child_handler: Got SIGCHLD Aug 9 23:32:38 c gdm[15094]: (child 15095) gdm_slave_child_handler Aug 9 23:32:38 c gdm[15094]: (child 15095) gdm_slave_child_handler: 15109 died Aug 9 23:32:38 c gdm[15094]: (child 15095) gdm_slave_child_handler: 15109 returned 1 Aug 9 23:32:38 c gdm[15094]: Handling message: 'XPID 15095 0' Aug 9 23:32:38 c gdm[15094]: Got XPID == 0 Aug 9 23:32:38 c gdm[15095]: gdm_server_start: After mainloop waiting for server Aug 9 23:32:38 c gdm[15095]: gdm_server_start: Server :0 died during startup! Aug 9 23:32:38 c gdm[15095]: A tela :0 está ocupada. Já existe um outro servidor X em execução. Aug 9 23:32:38 c gdm[15095]: gdm_server_start: Display :0 busy. Trying once again (after 2 sec delay) Aug 9 23:32:38 c udev[15116]: removing device node '/dev/vcs8' Aug 9 23:32:38 c udev[15118]: removing device node '/dev/vcsa8' Aug 9 23:32:39 c gdm[15094]: (child 15095) gdm_slave_usr2_handler: :0 got USR2 signal Aug 9 23:32:40 c gdm[15095]: Sending VT_NUM == -1 for slave 15095 Aug 9 23:32:40 c gdm[15095]: Sending VT_NUM 15095 -1 Aug 9 23:32:40 c gdm[15094]: Handling message: 'VT_NUM 15095 -1' Aug 9 23:32:40 c gdm[15094]: Got VT_NUM == -1 Aug 9 23:32:40 c gdm[15095]: gdm_server_start: :0 Aug 9 23:32:40 c gdm[15095]: gdm_auth_secure_display: Setting up access for :0 Aug 9 23:32:40 c gdm[15095]: gdm_auth_secure_display: Setting up access Aug 9 23:32:40 c gdm[15095]: gdm_auth_secure_display: Setting up access for :0 - 1 entries Aug 9 23:32:40 c gdm[15095]: Sending COOKIE == for slave 15095 Aug 9 23:32:40 c gdm[15095]: Sending COOKIE 15095 d... Aug 9 23:32:40 c gdm[15094]: (child 15095) gdm_slave_usr2_handler: :0 got USR2 signal Aug 9 23:32:40 c gdm[15094]: Handling message: 'COOKIE 15095 d...' Aug 9 23:32:40 c gdm[15094]: Got COOKIE == Aug 9 23:32:40 c gdm[15094]: (child 15095) gdm_slave_usr2_handler: :0 got USR2 signal Aug 9 23:32:40 c gdm[15137]: gdm_server_spawn: '/usr/X11R6/bin/X :0 -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt8' Aug 9 23:32:40 c gdm[15095]: gdm_server_spawn: Forked server on pid 15137 Aug 9 23:32:40 c gdm[15095]: do_server_wait: Before mainloop waiting for server Aug 9 23:32:40 c udev[15134]: creating device node '/dev/vcs8' Aug 9 23:32:40 c udev[15136]: creating device node '/dev/vcsa8' Aug 9 23:32:41 c gdm[15094]: (child 15095) gdm_server_child_handler: Got SIGCHLD Aug 9 23:32:41 c gdm[15094]: (child 15095) gdm_slave_child_handler Aug 9 23:32:41 c gdm[15094]: (child 15095) gdm_slave_child_handler: 15137 died Aug 9 23:32:41 c gdm[15094]: (child 15095) gdm_slave_child_handler: 15137 returned 1 Aug 9 23:32:41 c gdm[15094]: Handling message: 'XPID 15095 0' Aug 9 23:32:41 c gdm[15094]: Got XPID == 0 Aug 9 23:32:41 c gdm[15095]: gdm_server_start: After mainloop waiting for server Aug 9 23:32:41 c gdm[15094]: (child 15095) gdm_slave_
