Re: AGPGART driver for ArticiaS - ioremap() problem
Hi, > --- Ursprüngliche Nachricht --- > Von: Benjamin Herrenschmidt <[EMAIL PROTECTED]> > An: Gerhard Pircher <[EMAIL PROTECTED]> > Kopie: [EMAIL PROTECTED], debian-powerpc@lists.debian.org > Betreff: Re: AGPGART driver for ArticiaS - ioremap() problem > Datum: Thu, 12 Jan 2006 15:44:27 +1100 > > On Wed, 2006-01-11 at 22:00 +0100, Gerhard Pircher wrote: > > Hi, > > > > David Bentam and I are trying to get a AGPGART driver working for the > > AmigaOne and the Pegasos1. The driver detects the aperture size of the > > ArticiaS AGP bridge, but fails at the ioremap() function in the generic > > GATT table create function. Does the PowerPC platform behaves > > differently for the mapping of address location for AGP operation than > > the x86 platform? Is it possible to use a mask to relocate the AGP > > address space to a specific location? > > Well, what value are you passing to ioremap ? > > Ben. > Please take a look at the end of my previous mail, where I included the debug messages of the driver and the driver code itself. The log shows that the physical address is mapped (IMHO) to the PCI memory range (> 0x0c000). Is this correct? Shouldn't it be mapped to the system memory address range? The aperture size is 4MB, page_order should be 1 and num_entries = 1024. Hope this helps!? :-) Thanks! Regards, Gerhard -- DSL-Aktion wegen großer Nachfrage bis 28.2.2006 verlängert: GMX DSL-Flatrate 1 Jahr kostenlos* http://www.gmx.net/de/go/dsl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: quik 7600 "out of scan range"
> Remind me what video chip you have on this machine ? It's a control or a > platinum ? > > Ben. Motherboard os "TNT", OF is 1.05 and video controler is identified as "Chaos Control" . Googling I found this :http://www.cpu.lu/~mlan/linux/dev/g3upgrade.html Maybe the issue is the G3 upgrade ? I no longer have the original processor, but I have another G3 upgrade with 233 clock, I'll try it .
Re: quik 7300 Auto of scan range
On 1/11/06, Hans Ekbrand <[EMAIL PROTECTED]> wrote: > On Wed, Jan 11, 2006 at 05:56:32PM -0200, Fábio Rabelo wrote: > > But after that, in the first boot within Sarge, my monitor just shows a > > msg "scan ou of range" . > > The noise from HD sugests the boot is going fine, but I can do anything > > from that on . > > OK. But if quik boots alright, then what good would it be to boot with > BootX instead? > To change quik for bootX > One simple test is to press Ctrl-alt-delete. If the box reboots, then > it was properly booted. After all noise in HD stops, the Ctrl+alt+del restarts the machine yes . > > > I can use bootX in this machine, there are room in HD, but how can I > > copy a suitable Kernel to MAC OS partition without a normal boot ? > > I would use the debian-installer as a rescue system and chroot into > the installed system and investigate the problem the monitor. If the > box is connected to a network, I would install ssh so one could ssh > into it when/if there is no display. > > If it turns out that quik does not really boot the box (in spite of > the sound that you interpreted as a successful boot), then (still > within the chroot) mount the MacOS partition and copy the kernel + > initrd to that partition for use with BootX. The Sarge installer is not finished yet, in the first boot the installer setup the apt.sources, and then download any update available , and then I can install anything I want ( like ssh ) so before it can not do anything . The goal is power the machine and never more power off, remove keyboard and mouse and use ssh/webmin to manage everything . Fábio Rabelo
Re: quik 7300 Auto of scan range
On Thu, Jan 12, 2006 at 07:48:21AM -0200, Fábio Rabelo wrote: > On 1/11/06, Hans Ekbrand <[EMAIL PROTECTED]> wrote: > > On Wed, Jan 11, 2006 at 05:56:32PM -0200, Fábio Rabelo wrote: > > > But after that, in the first boot within Sarge, my monitor just shows a > > > msg "scan ou of range" . > > > The noise from HD sugests the boot is going fine, but I can do anything > > > from that on . > > > > OK. But if quik boots alright, then what good would it be to boot with > > BootX instead? > > > To change quik for bootX But if the machine boots with quik, what would be gained if it was booted by BootX instead? > > One simple test is to press Ctrl-alt-delete. If the box reboots, then > > it was properly booted. > > After all noise in HD stops, the Ctrl+alt+del restarts the machine yes . So, the booting is working. Then I fail to see how BootX would help. Wouldn't the machine get to the same final state after the boot anyhow? > > > I can use bootX in this machine, there are room in HD, but how can I > > > copy a suitable Kernel to MAC OS partition without a normal boot ? > > > > I would use the debian-installer as a rescue system and chroot into > > the installed system and investigate the problem the monitor. If the > > box is connected to a network, I would install ssh so one could ssh > > into it when/if there is no display. > > > > If it turns out that quik does not really boot the box (in spite of > > the sound that you interpreted as a successful boot), then (still > > within the chroot) mount the MacOS partition and copy the kernel + > > initrd to that partition for use with BootX. > > The Sarge installer is not finished yet, in the first boot the > installer setup the apt.sources, and then download any update > available , and then I can install anything I want ( like ssh ) so > before it can not do anything . What I scetched above was a procedure to get into the installed system (wheter or not the installation was finished). I assume the installer finished the first stage (since quik was installed, and the system sounds like it boots correctly). Start the installation again. When the installer has detected the hardware, get a shell, mount the partition where debian is installed and chroot into it. Did you run base-config during the first stage? If not, do that in the chroot, so password is set for root. > The goal is power the machine and never more power off, remove > keyboard and mouse and use ssh/webmin to manage everything . Well then you might not even have to resolve the display issue, just install ssh in the chroot and reboot. -- Hans Ekbrand (http://sociologi.cjb.net) <[EMAIL PROTECTED]> Q. What is that strange attachment in this mail? A. My digital signature, see www.gnupg.org for info on how you could use it to ensure that this mail is from me and has not been altered on the way to you. signature.asc Description: Digital signature
Re: DRI not working with libgl1-mesa-dri (r300)
On Wed, 2006-01-11 at 21:00 +0100, Ruben wrote: > > The radeon module gets loaded by xorg, but /dev/dri remains empty :( > Shouldn't the /dev/dri/card0 be created by udev upon loading the > radeon module? Maybe, but the X server creates the device nodes on the fly as necessary anyway. > drmOpenDevice: node name is /dev/dri/card0 > > drmOpenDevice: open result is -1, (No such device) > 'No such device' usually occurs when the kernel module isn't loaded. -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
powercenter ethernet problem (mace)
Hey guys first post! I have a problem with my PowerCenter Pro 180, I have tried both Debian 3.0r5 and also 3.1r1. The Ethernet refuses to function correctly, I can assign it an ip and bring it up – but as soon as It has received the exact same number of bytes that the MTU is set to, it will not respond. If I change The mtu to 1000 or so and down/up the interface it will talk intermittently. I’ve tried additional network cards but they aren’t picked up by the machine, they make a brief appearance in dmesg (the pci bios has not enabled the device at xxx..) Are these two problems interrelated? Does anyone know why its doing this and how it can be corrected? Cheers, logik
Re: Now that the gates for 2.6.16 patches are opened...
Hi, I think I can create a patch which changes the compilation #define with a global variable. If someone can create a patch that links this variable to a /sys pseudo-file... -- Eugen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Now that the gates for 2.6.16 patches are opened...
On 1/12/06, Eugen Dedu <[EMAIL PROTECTED]> wrote: > Hi, > > I think I can create a patch which changes the compilation #define with > a global variable. > > If someone can create a patch that links this variable to a /sys > pseudo-file... It should help to say that you are reffering to the blink led patch ;-) As far as I managed to look over it, the current status is that the entry is in /sys but has to linked to a hwif structure, so there is one per device, not one per system, as it is now (iirc). -- Regards, EddyP = "Imagination is more important than knowledge" A.Einstein
Re: therm_adm103x: inquiry
On Thu, Jan 12, 2006 at 07:49 AM, Cedric Pradalier wrote: > I'd like to know if there is still people using this module, I've used it for a while: http://lists.debian.org/debian-powerpc/2005/01/msg00453.html Now i'm living without thermal control. The logic board of my ibook has been substituted two times, but i don't know if this is somehow correlated with the lack of thermal control: my laptop is in the "Repair Extension Program". > if these users would like to see this module included an > official kernel Yes, of course (but, IIRC, BenH didn't like degrees symbol). > if, knowing that lm_sensors should be able to read this > chip, you still need the therm_adm103x module (I think so > since I believe lm_sensor does not provide control over > the chip, or does it?). So you can say that therm_adm103x is definitively better than lm_sensors? > Thanks for you answers. Thank to you for your work. luca -- Beware of programmers who carry screwdrivers. -- Leonard Brandwein http://shammash.homelinux.org/ - http://www.artha.org/shammash/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Patch-File
Hello, I'm trying to define a de_CH keyboard in debian PPC. I've found http://lists.debian.org/debian-powerpc/2003/08/msg00709.html what is this good for? Fritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Now that the gates for 2.6.16 patches are opened...
According to Eddy Petrişor, on Thu, 12 Jan 2006 14:08:31 +0200, >On 1/12/06, Eugen Dedu <[EMAIL PROTECTED]> wrote: >> Hi, >> >> I think I can create a patch which changes the compilation #define with >> a global variable. >> >> If someone can create a patch that links this variable to a /sys >> pseudo-file... > >It should help to say that you are reffering to the blink led patch ;-) > >As far as I managed to look over it, the current status is that the >entry is in /sys but has to linked to a hwif structure, so there is >one per device, not one per system, as it is now (iirc). > Which is the version in the attached patch (against 2.6.12). When I tried to do it I could not find the dev object in the hwif structure, but surely someone would have the time to do it :) Also, in the patch above, the sysfs function may have to be slightly modified to have an additional argument introduced in 13 or 14. Sorry, I really don't have the resources to do it myself in a reasonnable time frame. Happy hacking... -- Cedric pmac-rtblink.diff.gz Description: Binary data
Re: therm_adm103x: inquiry
According to Luca Bigliardi, on Thu, 12 Jan 2006 12:07:21 +0100, >On Thu, Jan 12, 2006 at 07:49 AM, Cedric Pradalier wrote: > >> I'd like to know if there is still people using this module, > >I've used it for a while: >http://lists.debian.org/debian-powerpc/2005/01/msg00453.html > >Now i'm living without thermal control. >The logic board of my ibook has been substituted two times, but i don't >know if this is somehow correlated with the lack of thermal control: >my laptop is in the "Repair Extension Program". > I don't believe so, this is a general ibook problem which also happen to people using only OSX. A cheap HW design... >> if these users would like to see this module included an >> official kernel > >Yes, of course (but, IIRC, BenH didn't like degrees symbol). > I've made them a compile time parameter in latest version. I usually use the * symbol on my machine. >> if, knowing that lm_sensors should be able to read this >> chip, you still need the therm_adm103x module (I think so >> since I believe lm_sensor does not provide control over >> the chip, or does it?). > >So you can say that therm_adm103x is definitively better than lm_sensors? No, I've not managed to use lm_sensors :) I did not try very hard neither... I would really like to know if someone managed to use it, and if so, gives a comparative evaluation of both modules. -- Cedric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: therm_adm103x: inquiry
On Thu, Jan 12, 2006 at 10:49 PM, Cedric Pradalier wrote: > I would really like to know if someone managed to use it, > and if so, gives a comparative evaluation of both modules. I remember that there were some problems with fan startup using lm_sensors (but i don't know now). I think you should try by yourself, your tests will be surely more accurate! IMHO you should go on with your module and, at most, write a little note in Kconfig help about a '(nearly?) working lm_sensors support'. luca -- Beware of programmers who carry screwdrivers. -- Leonard Brandwein http://shammash.homelinux.org/ - http://www.artha.org/shammash/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DRI not working with libgl1-mesa-dri (r300)
At Thu, 12 Jan 2006 12:15:34 +0100, Michel Dänzer wrote: > > Maybe, but the X server creates the device nodes on the fly as necessary > anyway. Not in my case it seems. I tried creating the device node manually (mknod /dev/dri/card0 c 226 0) before starting X, but then X removes it. > > drmOpenDevice: node name is /dev/dri/card0 > > > > drmOpenDevice: open result is -1, (No such device) > > > > 'No such device' usually occurs when the kernel module isn't loaded. That was what I thought at first, but I did have DRM+Radeon enabled in the kernel. I even changed my kernel configuration to have those as modules, but that doesn't change a thing (and it shouldn't). X does load the radeon module though, but still no entry in /dev/dri. Ruben [EMAIL PROTECTED] ~ $ lsmod Module Size Used by bcm43xx 429716 0 ieee80211_crypt_ccmp 7840 0 ieee80211_crypt_tkip12096 0 ieee80211_crypt_wep 5312 1 ieee80211softmac 27968 1 bcm43xx ieee80211 32904 2 bcm43xx,ieee80211softmac ieee80211_crypt 5536 4 ieee80211_crypt_ccmp,ieee80211_crypt_tkip,ieee80211_crypt_wep,ieee80211 radeon126440 0 drm80664 1 radeon uninorth_agp9384 1 agpgart32796 2 drm,uninorth_agp [EMAIL PROTECTED] ~ $ dmesg | grep drm [drm] Initialized drm 1.0.0 20040925 [EMAIL PROTECTED] ~ $ gunzip -c /proc/config.gz | grep DRM CONFIG_DRM=m # CONFIG_DRM_TDFX is not set # CONFIG_DRM_R128 is not set CONFIG_DRM_RADEON=m # CONFIG_DRM_MGA is not set # CONFIG_DRM_SIS is not set # CONFIG_DRM_VIA is not set # CONFIG_DRM_SAVAGE is not set Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
bluetooth mouses not working in recent Debian bluez-utils
Hello, I have just seen recently that my bluetooth mouse has stopped functioning (I haven't been using it daily so I can't say when this regression happened). The device is discovered if I hcitool scan. Please also note that I might not have a recent version as I couldn't update for some time (conectivity issues). Can somebody say if they encountered this problem with current versions of bluez-utils? (I have tested older kernels that I know that worked in thepast) With hcidump I see that there is some feature which is not supported, apparently, but I have used this mouse before. Sorry for th lack of details, I am not at home, so I can't reproduce the exact message. -- Regards, EddyP = "Imagination is more important than knowledge" A.Einstein
Re: DRI not working with libgl1-mesa-dri (r300)
On Thu, 2006-01-12 at 14:50 +0100, Ruben wrote: > At Thu, 12 Jan 2006 12:15:34 +0100, Michel Dänzer wrote: > > > > Maybe, but the X server creates the device nodes on the fly as necessary > > anyway. > > Not in my case it seems. I tried creating the device node manually > (mknod /dev/dri/card0 c 226 0) before starting X, but then X removes > it. The X server creates and removes the nodes as they are (not) needed. If the missing node was the problem, the error would be 'No such file or directory'. > > > drmOpenDevice: node name is /dev/dri/card0 > > > > > > drmOpenDevice: open result is -1, (No such device) > > > > > > > 'No such device' usually occurs when the kernel module isn't loaded. > > That was what I thought at first, but I did have DRM+Radeon enabled in > the kernel. I even changed my kernel configuration to have those as > modules, but that doesn't change a thing (and it shouldn't). You're right that it shouldn't in theory, but in reality the modular case is much better tested. > X does load the radeon module though, but still no entry in /dev/dri. What about /proc/dri/? > [EMAIL PROTECTED] ~ $ dmesg | grep drm > [drm] Initialized drm 1.0.0 20040925 There should be some output from the radeon module here. Please post the kernel output that results from modprobe -r radeon; modprobe radeon (or the full kernel output, if in doubt) > [EMAIL PROTECTED] ~ $ gunzip -c /proc/config.gz | grep DRM > CONFIG_DRM=m > # CONFIG_DRM_TDFX is not set > # CONFIG_DRM_R128 is not set > CONFIG_DRM_RADEON=m This is fine. Have you verified that the 'device scape' patch you're using doesn't cause the problem? I must confess I haven't got around to running 2.6.15 yet, so there's the possibility of radeon DRM breakage there, although I'd expect more noise about that on this list. :) -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
linux-image-2.6.15-2-powerpc: No initramfs generators as dependancies?
As of version 2.6.15-2 of linux-image-powerpc I can no longer find Depends: yaird|initramfs-tools|linux-initramfs-tools Is it a packaging error (either simple lack of Depends:, or lack of --initrd switch in make-kpkg line), or have the initramfs been dropped (which I doubt, especially since that wouldn't happen without a huge note in changelog)? Latest i386 kernels have all dependancies necessary, I've already tested them, and they work well, but I don't know what to do with powerpc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bluetooth mouses not working in recent Debian bluez-utils
On 1/12/06, Yves-Alexis Perez <[EMAIL PROTECTED]> wrote: > Eddy Petrisor wrote: > > Hello, > > > > I have just seen recently that my bluetooth mouse has stopped > > functioning (I haven't been using it daily so I can't say when this > > regression happened). The device is discovered if I hcitool scan. > > > > Please also note that I might not have a recent version as I couldn't > > update for some time (conectivity issues). > > > > Can somebody say if they encountered this problem with current > > versions of bluez-utils? (I have tested older kernels that I know that > > worked in thepast) > > My mouse works fine. > ii bluez-utils2.24-1 Bluetooth tools and daemons > > Do you have: > > HIDD_ENABLED=1 > HIDD_OPTIONS="--master --server" > > In your /etc/default/bluetooth ? Will check tonight and answer tomorrow. -- Regards, EddyP = "Imagination is more important than knowledge" A.Einstein
ALSA config file for Toonie broken
After several months of working with half-functional custom ~/.asound.rc file I managed to somehow nuke this file and faces the folowing problem: Initializing SDL audio subsystem. ALSA lib conf.c:1596:(snd_config_load1) :51:1:Unexpected } ALSA lib conf.c:2837:(snd_config_hook_load) /usr/share/alsa/cards/PMacToonie.conf may be old or corrupted: consider to remove or fix it ALSA lib conf.c:2700:(snd_config_hooks_call) function snd_config_hook_load_for_all_cards returned error: Invalid argument ALSA lib pcm.c:1969:(snd_pcm_open_conf) Invalid type for PCM default definition (id: default, value: cards.pcm.default) SDL audio subsystem initialized. Opening SDL audio device. Unable to open audio device: No available audio device Sound driver initialization failed. This may happen when a soundcard is not present or not available. while trying to launch UQM. /usr/share/alsa/cards/PMacToonie.conf is indeed corrupted, with spurious "}" at the end, making the default configuration unusable. Fixing that gave me a fully functional ALSA without a need Is this a Debian-specific bug, or has it been broken by ALSA team (if so, could someone with their BTS account file a bug?)? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xorg-6.9.0
On Wed, 2006-01-11 at 18:53 +0100, Elimar Riesebieter wrote: > The changelog of 6.9.0.dfsg.1-3 doesn't tell me signifant changes > which should solve aur problem. I am using 2.6.15. Which is yours? still at 2.6.15-rc7. johannes signature.asc Description: This is a digitally signed message part
Re: ALSA config file for Toonie broken
On Thu, 2006-01-12 at 16:29 +0100, Andrzej Mendel wrote:
> After several months of working with half-functional custom ~/.asound.rc
> file I managed to somehow nuke this file and faces the folowing problem:
> Initializing SDL audio subsystem.
> ALSA lib conf.c:1596:(snd_config_load1) :51:1:Unexpected }
[...]
> This may happen when a soundcard is not present or not available.
> while trying to launch UQM. /usr/share/alsa/cards/PMacToonie.conf is
> indeed corrupted, with spurious "}" at the end, making the default
> configuration unusable. Fixing that gave me a fully functional ALSA
> without a need
With something like the attached patch, I assume.
> Is this a Debian-specific bug, or has it been broken by
> ALSA team (if so, could someone with their BTS account file a bug?)?
reportbug -f /usr/share/alsa/cards/PMacToonie.conf
--
Earthling Michel Dänzer | Debian (powerpc), X and DRI developer
Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
--- /usr/share/alsa/cards/PMacToonie.conf.dpkg-dist 2006-01-12 16:57:40.297534306 +0100
+++ /usr/share/alsa/cards/PMacToonie.conf 2006-01-12 16:58:09.833809071 +0100
@@ -28,6 +28,7 @@ PMacToonie.pcm.default {
type string
}
type asym
+ playback.pcm {
type plug
slave.pcm {
type softvol
Re: bluetooth mouses not working in recent Debian bluez-utils
Hi alltogether! On Thu, Jan 12, 2006 at 05:29:53PM +0200, Eddy Petrişor wrote: > On 1/12/06, Yves-Alexis Perez <[EMAIL PROTECTED]> wrote: > > Eddy Petrisor wrote: > > > Hello, > > > > > > I have just seen recently that my bluetooth mouse has stopped > > > functioning (I haven't been using it daily so I can't say when this > > > regression happened). The device is discovered if I hcitool scan. > > > > > > Please also note that I might not have a recent version as I couldn't > > > update for some time (conectivity issues). > > > > > > Can somebody say if they encountered this problem with current > > > versions of bluez-utils? (I have tested older kernels that I know that > > > worked in thepast) > > > > My mouse works fine. > > ii bluez-utils2.24-1 Bluetooth tools and daemons > > > > Do you have: > > > > HIDD_ENABLED=1 > > HIDD_OPTIONS="--master --server" > > > > In your /etc/default/bluetooth ? Mine works fine too, I have HIDD_ENABLED=1 HIDD_OPTIONS="--connect > Will check tonight and answer tomorrow. > > -- > Regards, > EddyP > = > "Imagination is more important than knowledge" A.Einstein signature.asc Description: Digital signature
Re: xorg-6.9.0
On Thu, 12 Jan 2006 the mental interface of Ben Racher told: [...] > I'm experiencing similar freezing on my powerbook 5,4 with ATI mobility radio > 9600, after upgrading to 6.9.0 Have you figured out what's wrong at all? > Could > you point to any links, is it the ATI driver? No, not really :( > I finally just downgraded back down to 6.8.2 after fiddling with > it forever... jeez, what a waste of time for me. You are not allone ;) Elimar -- Do you smell something burning or ist it me? pgpYaG3UEybOT.pgp Description: PGP signature
Re: ALSA config file for Toonie broken
On Thu, 12 Jan 2006 the mental interface of
Michel Dänzer told:
> On Thu, 2006-01-12 at 16:29 +0100, Andrzej Mendel wrote:
> > After several months of working with half-functional custom ~/.asound.rc
> > file I managed to somehow nuke this file and faces the folowing problem:
> > Initializing SDL audio subsystem.
> > ALSA lib conf.c:1596:(snd_config_load1) :51:1:Unexpected }
>
> [...]
>
> > This may happen when a soundcard is not present or not available.
> > while trying to launch UQM. /usr/share/alsa/cards/PMacToonie.conf is
> > indeed corrupted, with spurious "}" at the end, making the default
> > configuration unusable. Fixing that gave me a fully functional ALSA
> > without a need
>
> With something like the attached patch, I assume.
Thanks for the patch ;) Has someone tested the apatch? I don't have
a Toonie handy. Jordi and Thomas hve to update alsalib at next
upload then ;)
> --- /usr/share/alsa/cards/PMacToonie.conf.dpkg-dist 2006-01-12
> 16:57:40.297534306 +0100
> +++ /usr/share/alsa/cards/PMacToonie.conf 2006-01-12 16:58:09.833809071
> +0100
> @@ -28,6 +28,7 @@ PMacToonie.pcm.default {
> type string
> }
> type asym
> + playback.pcm {
> type plug
> slave.pcm {
> type softvol
Elimar
--
>what IMHO then?
IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
--posting from alex in debian-user--
Re: ALSA config file for Toonie broken
On Thu, Jan 12, 2006 at 07:01:56PM +0100, Elimar Riesebieter wrote: > On Thu, 12 Jan 2006 the mental interface of > Michel Dänzer told: > > > On Thu, 2006-01-12 at 16:29 +0100, Andrzej Mendel wrote: > > > After several months of working with half-functional custom ~/.asound.rc > > > file I managed to somehow nuke this file and faces the folowing problem: > > > Initializing SDL audio subsystem. > > > ALSA lib conf.c:1596:(snd_config_load1) :51:1:Unexpected } > > > > [...] > > > > > This may happen when a soundcard is not present or not available. > > > while trying to launch UQM. /usr/share/alsa/cards/PMacToonie.conf is > > > indeed corrupted, with spurious "}" at the end, making the default > > > configuration unusable. Fixing that gave me a fully functional ALSA > > > without a need > > > > With something like the attached patch, I assume. > > Thanks for the patch ;) Has someone tested the apatch? I don't have > a Toonie handy. Jordi and Thomas hve to update alsalib at next > upload then ;) This is bug #340478, which is apparently already fixed in experimental. The patch in that bug report (which seems to be the same one as posted here) works fine for me. Bram Senders signature.asc Description: Digital signature
Re: [Pkg-alsa-devel] Re: ALSA config file for Toonie broken
Elimar Riesebieter wrote:
> Thanks for the patch ;) Has someone tested the apatch? I don't have
> a Toonie handy. Jordi and Thomas hve to update alsalib at next
> upload then ;)
[...]
>> type asym
>> +playback.pcm {
>> type plug
This is bug #340478. It was fixed in the 1.0.10+1.0.11rc1-1 upload of
libasound2.
Cheers
--
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA config file for Toonie broken
Dnia 12-01-2006, czw o godzinie 19:01 +0100, Elimar Riesebieter
napisał(a):
> On Thu, 12 Jan 2006 the mental interface of
> Michel Dänzer told:
>
> > On Thu, 2006-01-12 at 16:29 +0100, Andrzej Mendel wrote:
> > > After several months of working with half-functional custom ~/.asound.rc
> > > file I managed to somehow nuke this file and faces the folowing problem:
> > > Initializing SDL audio subsystem.
> > > ALSA lib conf.c:1596:(snd_config_load1) :51:1:Unexpected }
> >
> > [...]
> >
> > > This may happen when a soundcard is not present or not available.
> > > while trying to launch UQM. /usr/share/alsa/cards/PMacToonie.conf is
> > > indeed corrupted, with spurious "}" at the end, making the default
> > > configuration unusable. Fixing that gave me a fully functional ALSA
> > > without a need
> >
> > With something like the attached patch, I assume.
>
> Thanks for the patch ;) Has someone tested the apatch? I don't have
> a Toonie handy. Jordi and Thomas hve to update alsalib at next
> upload then ;)
>
>
> > --- /usr/share/alsa/cards/PMacToonie.conf.dpkg-dist 2006-01-12
> > 16:57:40.297534306 +0100
> > +++ /usr/share/alsa/cards/PMacToonie.conf 2006-01-12 16:58:09.833809071
> > +0100
> > @@ -28,6 +28,7 @@ PMacToonie.pcm.default {
> > type string
> > }
> > type asym
> > + playback.pcm {
> > type plug
> > slave.pcm {
> > type softvol
>
> Elimar
To be frank, in my first atempt to fix it I just removed "}" at the end
and it worked. Applying this patch mendel Toonie as well. I don't know,
which aproach is better, I'm no ALSA expert.
To sum things up, the proposed patch works, at least for audio output.
Even if it doesn't make audio input work (I'm not sure, if there are any
Toonies with audio in), it's still better than before.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AGPGART driver for ArticiaS - ioremap() problem
Hi, > --- Ursprüngliche Nachricht --- > Von: Benjamin Herrenschmidt <[EMAIL PROTECTED]> > An: Gerhard Pircher <[EMAIL PROTECTED]> > Kopie: [EMAIL PROTECTED], debian-powerpc@lists.debian.org > Betreff: Re: AGPGART driver for ArticiaS - ioremap() problem > Datum: Thu, 12 Jan 2006 15:44:27 +1100 > > On Wed, 2006-01-11 at 22:00 +0100, Gerhard Pircher wrote: > > Hi, > > > > David Bentam and I are trying to get a AGPGART driver working for the > > AmigaOne and the Pegasos1. The driver detects the aperture size of the > > ArticiaS AGP bridge, but fails at the ioremap() function in the generic > > GATT table create function. Does the PowerPC platform behaves > > differently for the mapping of address location for AGP operation than > > the x86 platform? Is it possible to use a mask to relocate the AGP > > address space to a specific location? > > Well, what value are you passing to ioremap ? > > Ben. I added some debug code to the agp_generic_create_gatt_table() function. This is the debug output of it (function renamed to articias_create_gatt_table()): agpgart: [ARTICIAS] articias_fetch_size() agpgart: [ARTICIAS] * non masked temp = 0x1 agpgart: [ARTICIAS] * aperature size loop index #0 agpgart: [ARTICIAS] * values[0].size_value = 1 agpgart: [ARTICIAS] * masked temp = 0x1 agpgart: [ARTICIAS] * values[0].size = 4 agpgart: [ARTICIAS] * current_size->size = 4 agpgart: [ARTICIAS] * current_size->page_order = 1 agpgart: [ARTICIAS] * current_size->num_entries = 1024 agpgart: [ARTICIAS] * current_size->size_value = 1 agpgart: [ARTICIAS] articias_create_gatt_table() agpgart: [ARTICIAS] * table address = 0xdfad2000 agpgart: [ARTICIAS] * table end address = 0xdfad3fff agpgart: [ARTICIAS] * page = 0xc08f9a80 agpgart: [ARTICIAS] * gatt_table_real = 0xdfad2000 agpgart: [ARTICIAS] * agp_gatt_table = 0xdfad2000 agpgart: [ARTICIAS] * virt_to_gart(table) = 0x1fad2000 __ioremap(): phys addr 1fad2000 is RAM lr c000ec3c agpgart: [ARTICIAS] * gatt_table_real = 0x0 agpgart: unable to get memory for graphics translation table. agpgart: agp_backend_initialize() failed. agpgart-articias: probe of :00:00.0 failed with error -12 As far as I can see, the physical address of the table is in the PCI memory range, right? Any ideas? Thanks! Regards, Gerhard -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Install mini-iso and kernel available for new AlBook
Hi all, Since I also received my new PowerBook (Powerbook5,8, aka post-October 15,2" Aluminum)a few days ago :-), I have been working hard to get Debian on it's disk. I have built a custom kernel that includes the two patches needed to support the post-October Powerbooks (namely trackpad updates and fn-key patch, although that one is still heavily discussed...). I have also put this kernel on one of Sven's daily-built d-i mini-iso, the one from January 10. I didn't recreate the mini-iso out of debian-installer completely, just replaced the kernel (netboot-linux) and produced a new ISO. Here are the links: http://www.cpu.lu/~mlan/ftp/debian/albook-mini.iso http://www.cpu.lu/~mlan/ftp/debian/kernel-image-2.6.15-ln2-powerpc_10.00.Custom_powerpc.deb Since the name of the kernel deb is a bit hard to type by hand from the installer shell, here is a simpler symlink: http://www.cpu.lu/~mlan/ftp/debian/kernel-albook.deb Once you have installed most parts of the system, after installing yaboot BUT BEFORE REBOOTING, you need to go into a shell and download the kernel deb, and install it (chroot target dpkg -i ). Good luck :-) Michel PS I'm still struggling myself to get everything working, I'll be back with more... - Michel Lanners | " Read Philosophy. Study Art. 23, Rue Paul Henkes|Ask Questions. Make Mistakes. L-1710 Luxembourg | email [EMAIL PROTECTED]| http://www.cpu.lu/~mlan| Learn Always. " -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Strange behavior
I have the following Problem: [EMAIL PROTECTED]:~$ sudo mkdir /sda1 [EMAIL PROTECTED]:~$ sudo chown swe /sda1 [EMAIL PROTECTED]:~$ ls -la /sda1 total 8 drwxr-xr-x 2 swe root 4096 Jan 11 16:19 . drwxr-xr-x 37 root root 4096 Jan 11 16:19 .. [EMAIL PROTECTED]:~$ mount /dev/sda1 /sda1 mount: only root can do that [EMAIL PROTECTED]:~$ sudo mount /dev/sda1 /sda1 [EMAIL PROTECTED]:~$ ls -la /sda1 total 4908 drwxr-xr-x 14 root root 16384 Jan 1 1970 . drwxr-xr-x 37 root root4096 Jan 11 16:19 .. -rwxr-xr-x 1 root root6148 Jan 10 13:56 .DS_Store drwxr-xr-x 2 root root2048 Nov 23 12:27 .Trash-swe . . . -rwxr-xr-x 1 root root 180 Jan 11 15:59 hints . . . [EMAIL PROTECTED]:~$ sudo mount /dev/sda1 /sda1 [EMAIL PROTECTED]:~$ sudo chown -R swe /sda1 chown: changing ownership of `/sda1': Operation not permitted chown: changing ownership of `/sda1/.Trashes': Operation not permitted chown: changing ownership of `/sda1/macintosh.pdf': Operation not permitted . . . chown: changing ownership of `/sda1/hints': Operation not permitted . . . [EMAIL PROTECTED]:~$ cat >>/sda1/hints bash: /sda1/hints: Permission denied [EMAIL PROTECTED]:~$ sudo cat >>/sda1/hints bash: /sda1/hints: Permission denied [EMAIL PROTECTED]:~$ su - Password: LinuxPPC:~# cat >>/sda1/hints The user swe has the same group as root (0). What's going on here? Fritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: OT: Open Firmware oem-logo
I've tried and failed on an iMac G4. You may use (instead) oem-banner; this is a variable which stores only text and it is shown when OF is entered. HTH Marco. ps: to use it set (of) > setenv oem-banner your message > setenv oem-banner? true or (terminal) sudo nvram oem-banner="your message" sudo nvram oem-banner?="true" Il giorno 11/gen/06, alle ore 23:12, Aaron Kerr ha scritto: Slightly off topic, but Has anyone tried added a personalised logo to the Open Firmware by setting oem-logo? On other (OpenBoot) platforms this is a good way to label the HW as owned by a particular person because oem-logo is not cleared by a "set-defaults". I have tried and failed. Perhaps oem-logo is not fully supported by the ibook? Aaron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Strange behavior
[...] > [EMAIL PROTECTED]:~$ ls -la /sda1 > total 4908 > drwxr-xr-x 14 root root 16384 Jan 1 1970 . > drwxr-xr-x 37 root root4096 Jan 11 16:19 .. > -rwxr-xr-x 1 root root6148 Jan 10 13:56 .DS_Store > drwxr-xr-x 2 root root2048 Nov 23 12:27 .Trash-swe > . > . > . > -rwxr-xr-x 1 root root 180 Jan 11 15:59 hints > . > . > . > [EMAIL PROTECTED]:~$ sudo mount /dev/sda1 /sda1 > [EMAIL PROTECTED]:~$ sudo chown -R swe /sda1 > chown: changing ownership of `/sda1': Operation not permitted > chown: changing ownership of `/sda1/.Trashes': Operation not permitted > chown: changing ownership of `/sda1/macintosh.pdf': Operation not permitted > . > . > . > chown: changing ownership of `/sda1/hints': Operation not permitted > . > . > . That seems strange to me, what filesystem is it? The only thing I could imagine is that the filesystem doesn't support the operation - VFAT? > [EMAIL PROTECTED]:~$ cat >>/sda1/hints > bash: /sda1/hints: Permission denied > [EMAIL PROTECTED]:~$ sudo cat >>/sda1/hints > bash: /sda1/hints: Permission denied > [EMAIL PROTECTED]:~$ su - > Password: > LinuxPPC:~# cat >>/sda1/hints > > The user swe has the same group as root (0). > What's going on here? > I think that's pretty much ok. "sudo cat >>/sda1/hints" will run cat as root, but ">>/sda1/hints" is interpreted by your shell, running as swe... And, as listed above, the group swe is a member of (0) doesn't have priveledges to write to the file. HTH, Michael signature.asc Description: Digital signature
Re: quik 7300 Auto of scan range
On 1/12/06, Hans Ekbrand <[EMAIL PROTECTED]> wrote: > On Thu, Jan 12, 2006 at 07:48:21AM -0200, Fábio Rabelo wrote: > > On 1/11/06, Hans Ekbrand <[EMAIL PROTECTED]> wrote: > > > On Wed, Jan 11, 2006 at 05:56:32PM -0200, Fábio Rabelo wrote: > > > > But after that, in the first boot within Sarge, my monitor just shows a > > > > msg "scan ou of range" . > > > > The noise from HD sugests the boot is going fine, but I can do anything > > > > from that on . > > > > > > OK. But if quik boots alright, then what good would it be to boot with > I assume the installer finished the first stage (since quik was > installed, and the system sounds like it boots correctly). > > Start the installation again. When the installer has detected the > hardware, get a shell, mount the partition where debian is installed > and chroot into it. I've try ed this, do not works, when I try to install ssh with dpkg ( apt do not work in chroot env ) I get error msg like this "subproccess pre-installation script returned error exit status 255" > > Did you run base-config during the first stage? If not, do that in the > chroot, so password is set for root. Yes, base system installs smoothly > > > The goal is power the machine and never more power off, remove > > keyboard and mouse and use ssh/webmin to manage everything . > > Well then you might not even have to resolve the display issue, just > install ssh in the chroot and reboot. Googling around I found this :http://www.cpu.lu/~mlan/linux/dev/g3upgrade.html but I do not found any command called "nvsetenv" , there are another way to change OF parameters ? I am almost giving up ! Fábio Rabelo
Re: quik 7300 Auto of scan range
> > Well then you might not even have to resolve the display issue, just > > install ssh in the chroot and reboot. > Googling around I found this > :http://www.cpu.lu/~mlan/linux/dev/g3upgrade.html > but I do not found any command called "nvsetenv" , there are another > way to change OF parameters ? > I am almost giving up ! All right, within chroot the command nvsetenv works, but I have no idea how to input this parameters !?! man nvsetenv is the most confusing I ever see, tells nothing useful . Someone can help me with this ? Fábio Rabelo
Re: therm_adm103x: inquiry
On Thu, 2006-01-12 at 14:16 +0100, Luca Bigliardi wrote: > On Thu, Jan 12, 2006 at 10:49 PM, Cedric Pradalier wrote: > > > I would really like to know if someone managed to use it, > > and if so, gives a comparative evaluation of both modules. > > I remember that there were some problems with fan startup using > lm_sensors (but i don't know now). I think you should try by yourself, > your tests will be surely more accurate! > > IMHO you should go on with your module and, at most, write a little note > in Kconfig help about a '(nearly?) working lm_sensors support'. I susually don't want to see lm_sensors anywhere near a mac.. Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [ANN] Broadcom Wireless Chipsets reverse engineered
Hello.Actually I did. I just noticed that the very first time I ty modprobe, I getbcm43xx: no version for "ieee80211softmac_wx_set_rate" found: kernel tainted.bcm43xx: Unknown symbol udelay (and only the second line appears again if I re-try)So, I guess I'm missing something when I build the driver, but it's quite wierd because it seems to run smootly. Thanks anyhow for your suggestion maurizioOn 1/11/06, Bin Zhang <[EMAIL PROTECTED] > wrote:On 1/12/06, Maurizio <[EMAIL PROTECTED] > wrote:> Hello. I was able to follow the procedure to build the> bcm43xx driver. Anyhow, when I try to modprobe the it I get>Maybe you forgot "make install" the driver. Bin> "Unknown symbol in module, or unknown parameter (see dmesg)">> and dmesg says>> bcm43xx: Unknown symbol udelay>> I guess I did something stupid, but I don't know what. Does domeone > have any idea?>> Thanks a lot for your help>>> maurizio>
Re: Strange behavior
>I have the following Problem: >[EMAIL PROTECTED]:~$ sudo mkdir /sda1 >[EMAIL PROTECTED]:~$ sudo chown swe /sda1 >[EMAIL PROTECTED]:~$ ls -la /sda1 >total 8 >drwxr-xr-x 2 swe root 4096 Jan 11 16:19 . >drwxr-xr-x 37 root root 4096 Jan 11 16:19 .. As shown, /sda1 only has write permission for the owner of the file(directory in this case). >[EMAIL PROTECTED]:~$ mount /dev/sda1 /sda1 >mount: only root can do that >[EMAIL PROTECTED]:~$ sudo mount /dev/sda1 /sda1 >[EMAIL PROTECTED]:~$ ls -la /sda1 >total 4908 >drwxr-xr-x 14 root root 16384 Jan 1 1970 . >drwxr-xr-x 37 root root4096 Jan 11 16:19 .. >-rwxr-xr-x 1 root root6148 Jan 10 13:56 .DS_Store >drwxr-xr-x 2 root root2048 Nov 23 12:27 .Trash-swe >. >. >. >-rwxr-xr-x 1 root root 180 Jan 11 15:59 hints >. >. >. >[EMAIL PROTECTED]:~$ sudo mount /dev/sda1 /sda1 >[EMAIL PROTECTED]:~$ sudo chown -R swe /sda1 >chown: changing ownership of `/sda1': Operation not permitted >chown: changing ownership of `/sda1/.Trashes': Operation not permitted >chown: changing ownership of `/sda1/macintosh.pdf': Operation not permitted >. >. >. >chown: changing ownership of `/sda1/hints': Operation not permitted >. >. >. >[EMAIL PROTECTED]:~$ cat >>/sda1/hints >bash: /sda1/hints: Permission denied >[EMAIL PROTECTED]:~$ sudo cat >>/sda1/hints >bash: /sda1/hints: Permission denied >[EMAIL PROTECTED]:~$ su - >Password: >LinuxPPC:~# cat >>/sda1/hints >The user swe has the same group as root (0). >What's going on here? >Fritz I suspect `touch hello in /sda1 will also FAIL. What I can suggest is: $ chmod g+swx /sda1 then, as swe user, $ touch /sda1/hello should succeed...? Regards, TEH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DRI not working with libgl1-mesa-dri (r300)
At Thu, 12 Jan 2006 15:58:54 +0100, Michel Dänzer wrote: > > The X server creates and removes the nodes as they are (not) needed. If > the missing node was the problem, the error would be 'No such file or > directory'. ok > > That was what I thought at first, but I did have DRM+Radeon enabled in > > the kernel. I even changed my kernel configuration to have those as > > modules, but that doesn't change a thing (and it shouldn't). > > You're right that it shouldn't in theory, but in reality the modular > case is much better tested. I see, I tend to avoid modules, since builtin is (was) less hassle. > > X does load the radeon module though, but still no entry in /dev/dri. > > What about /proc/dri/? Nothing in /proc/dri either. > > [EMAIL PROTECTED] ~ $ dmesg | grep drm > > [drm] Initialized drm 1.0.0 20040925 > > There should be some output from the radeon module here. Please post the > kernel output that results from > > modprobe -r radeon; modprobe radeon > > (or the full kernel output, if in doubt) I don't get anything from the radeon module: [drm] Module unloaded [drm] Initialized drm 1.0.0 20040925 I attached the whole dmesg at the end, just to be sure. Does the DRM module require something else or conflict with something else that I might not have or do have? > Have you verified that the 'device scape' patch you're using doesn't > cause the problem? I must confess I haven't got around to running 2.6.15 > yet, so there's the possibility of radeon DRM breakage there, although > I'd expect more noise about that on this list. :) I tested with vanilla 2.6.15 + outside-the-tree-softmac and a vanilla 2.6.14 kernel, and the debian 2.6.12 kernel but in all cases, /dev/dri remains empty. Ruben Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm dmesg-2.6.15 Description: Binary data
Re: quik 7300 Auto of scan range
On Thu, Jan 12, 2006 at 07:56:54PM -0200, Fábio Rabelo wrote: > On 1/12/06, Hans Ekbrand <[EMAIL PROTECTED]> wrote: > > On Thu, Jan 12, 2006 at 07:48:21AM -0200, Fábio Rabelo wrote: > > > On 1/11/06, Hans Ekbrand <[EMAIL PROTECTED]> wrote: > > > > On Wed, Jan 11, 2006 at 05:56:32PM -0200, Fábio Rabelo wrote: > > > > > But after that, in the first boot within Sarge, my monitor just shows > > > > > a > > > > > msg "scan ou of range" . > > > > > The noise from HD sugests the boot is going fine, but I can do > > > > > anything > > > > > from that on . > > > > > > > > OK. But if quik boots alright, then what good would it be to boot with > > I assume the installer finished the first stage (since quik was > > installed, and the system sounds like it boots correctly). > > > > Start the installation again. When the installer has detected the > > hardware, get a shell, mount the partition where debian is installed > > and chroot into it. > > I've try ed this, do not works, when I try to install ssh with dpkg ( > apt do not work in chroot env ) I get error msg like this "subproccess > pre-installation script returned error exit status 255" apt-get does work in chroot, I have used it many times. Since that part of your problem is not powerpc specific, you might try post it on debian-user to get more help. You should be able to get apt-get to work correctly within the croot and also install ssh. While you are in the chroot, read the syslog to verify that the system boots correctly. While in the croot you could also mount the MacOS partition and copy vmlinux and initrd.img to that partition for use with BootX. I thought that the kernel would be able to fix modelines when it takes over. That might be wrong in which case booting with BootX would likely fix it. Another workaround would be to try change the modeline with fbset. You could add a "fbset 800x600-56" to a script that is run at boottime. I have no opinion on the forth code you mention. I would try less disruptive ways to work around the problem before I tried it though. -- Hans Ekbrand (http://sociologi.cjb.net) <[EMAIL PROTECTED]> A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? signature.asc Description: Digital signature
