recording with alsa on tibook
Hello, I could have sworn that sometime ago I read in this mailinglist that the microphone works with alsa on a tibook. Several times I searched the archives, and the web in general, but could not find it again. Was I just fantasizing? Here's what /proc/cpuinfo says: motherboard : PowerBook3,4 MacRISC2 MacRISC Power Macintosh detected as : 73 (PowerBook Titanium III) and I'm using the benh kernals. At the moment 2.4.20-ben8 and alsa 0.9.0rc8d. Actually looking at /proc/asound/ I don't see anything to capture with just playback. Is recording possible at all? Thanks digger
Re: New sleep code for ATI M6, M7 and M9
Yaaahooo! This morning both Myrna (powerbook G4) and I woke up. For Myrna it was the the first good night sleep since I install Linux. So far I've seen none of the degradation over time that I had before the patch. Alsa -- at first it didn't seem to work but then discovered that, fiddling with the volume, it had just muted. Decided I actually prefer that to the possibility of waking up screaming. Below are my particulars Let me join everyone else in thanking you and everyone else involved. Thanks! digger Using unstable and experimental along with dri-trunk /proc/cpuinfo: cpu : 7455, altivec supported clock : 667MHz revision: 2.1 (pvr 8001 0201) bogomips: 665.19 machine : PowerBook3,4 motherboard : PowerBook3,4 MacRISC2 MacRISC Power Macintosh detected as : 73 (PowerBook Titanium III) pmac flags : 000b L2 cache: 256K unified memory : 512MB pmac-generation : NewWorld 00:10.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] On Fri, 2003-03-14 at 12:49, Benjamin Herrenschmidt wrote: > Ladies & Gentlemens The long awaited new power management > code coming right from the ATI labs is here ! Finally :) >
Re: recording with alsa on tibook
On Fri, 2003-03-14 at 13:33, Brett Carter wrote: > On Wed, Mar 12, 2003 at 10:55:48PM -0500, digger vermont wrote: > > Hello, > > I could have sworn that sometime ago I read in this mailinglist that > > the microphone works with alsa on a tibook. Several times I searched the > > archives, and the web in general, but could not find it again. Was I > > just fantasizing? > > Nope, I believe recording works on the 'clipper' chipset (tibooks v1 & > v2), but not yet on the 'snapper' chipset (ti v3 & above). The irony > here being the tibook III was the first to include a line-in jack :) > You can grab a griffin iMic for $40 if you really need line-in - it's > fully supported under alsa. > -Brett > Too bad. I was hoping to be able to at least do something like record some web-radio. But I guess not. Would also be nice to use the internal mic for some quick and dirty voice. Thanks for recommending the iMic. I hadn't seen that before. I was also looking at edirol's usb boxes. Need to look at the driver situation for them. digger
Re: New sleep code for ATI M6, M7 and M9
Don't feel too bad, Soebbi. As infrequently as I apply patches I always have to refigure it out. The secret is in the "<" From the "root" dir. I believe what I had is patch -p1 Hi everyone! > > I'm feeling a bit ashamed, since I now must admit that I am quite new > to Linux, but how do I apply the patch? > I tried "patch -p0 new_sleep.diff" in the root of the kernel source > directory and in the directory of the file which is mentioned on top of > the .diff-file, but every time I ran this command it seems to get stuck > till i kill it. > > Could someone please explain in short how to apply this patch!? > > Thanks a lot in advance! > > To Ben: Keep up your great work! > > -Soebbi >
Re: yaboot
On Mon, 2003-05-19 at 01:20, [EMAIL PROTECTED] wrote: > Hi! > > I have a tibook, so i don't have any floppy drive. > If i reinstall osX, i need to run ybin to recover the boot control? > > but how can i acces linux to run ybin? > > Thanks. > Hello, I recently had to reinstall osx on a powerbook G4. Maybe I was lucky, but all I had to do was press and hold the alt/option key at bootup. I held it through the initial bong and until I got a blue screen (OF screen?) with icons of my bootable partitions, linux and osx. It was as simple as choosing linux and after it had booted up, running ybin. good luck, digger
Re: booting on kernel-2.4.21-ben1
Hello, On Tue, 2003-06-17 at 16:54, Benjamin Herrenschmidt wrote: > On Tue, 2003-06-17 at 21:53, Laurent Bigonville wrote: > > Hi, > You tried the pmac defconfig ? > > (first make distclean, then make pmac_defconfig; make oldconfig; and buid it) > I've never used pmac_defconfig. Make says there is no rule for the target. I see it show up though in the arch/ppc/ directory. How do you use it? Thanks, digger
Re: ibook2
On Sat, 2003-07-26 at 14:47, Thomas Otto wrote: > > Problem 1: > > I can't record anything with my soundcard. Playing is no problem. I > If you are talking about the little microphone top-right of the screen: > IIRC you will have to wait for the 2.6 kernels with alsa since dmasound > isn't supporting recording (I guess externel USB Microphones won't work > either). Will alsa with the 2.6 kernel work without dmasound and/or allow recording? I would like to believe its true. I (and many others) am using alsa and as far as I can see have only playback available. On the alsa mailing list I've asked if the reason for no recording is due a lack of specs for the sound chip or a lack of desire and time on the developer end. I've yet to get a response. Does anyone here know? For me, its the last thing that keeps my powerbook from being fully functional. digger
Re: Ben's 2.4.21-benx curent kernel version
Hello Adam, head Makefile gives me: VERSION = 2 PATCHLEVEL = 4 SUBLEVEL = 21 EXTRAVERSION = -ben2 KERNELRELEASE=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION) On Thu, 2003-08-21 at 12:01, Adam H. Done wrote: > A quick question. Is Ben's current 2.4.21 kernel version 2 or 3? I > did the rsysnc but I don't know if it has changed from 2. I am using > 2.4.21-ben2 very nicely for the time being.
rsync hangs with benh-kernel
Hello All, I've been having trouble the last couple of days syncing the benh kernel. It seems to be stopping at the same place each time. Here's the command line: rsync -az rsync.penguinppc.org::linux-2.4-benh ~/src/benh_kernel and here's where it stops: recv_generator(arch/cris/boot/rescue/head.S,1087) recv_generator(arch/cris/boot/rescue/kimagerescue.S,1088) recv_generator(arch/cris/boot/rescue/rescue.ld,1089) recv_generator(arch/cris/boot/rescue/testrescue.S,1090) recv_generator(arch/cris/boot/tools,1091) recv_generator(arch/cris/boot/tools/build.c,1092) recv_generator(arch/cris/config.in,1093) recv_generator(arch/cris/cris.ld,1094) Any ideas? Thanks, digger
Re: apt-get problem with ~homedirs?
Hi Frank, On Fri, 2003-10-03 at 13:40, Frank Murphy wrote: > I just tried to add the unofficial xfce4 deb list to apt's sources.list, but > it doesn't work. Then I realized that the line for Michael Däzner's DRI X was > failing too. > > Does anyone else see this when doing apt-get (or aptitude) update? > > Hit http://people.debian.org ./ Packages > Ign http://people.debian.org ./ Release > Ya know I always saw that line with Ign and disregarded it. I did however just tried putting the URL in quotes and Ign is now Hit. Don't know if thats the right way to deal with it though. > This should be http://people.debian.org/~daenzer/dri-mach64-sid/, but it gets > cut off at the tilde. > > Frank > digger
Re: kernel 2.6.0-test8 console
On Fri, 2003-10-24 at 12:51, Adam Done wrote: > On Wed, 2003-10-22 at 06:20, Michael Schmitz wrote: > > > > Straight kernel.org or -benh ?? > > > > > > Straight kernel.org kernel :-) > > > > Big mistake. Use Ben's tree. > > Where is Ben's tree found.. I tried using rsync and reading over 5500 > emails with 2.6.0 kernel and could not find any location. > I can understand your frustration, I've done those kind of searches myself. Here's what I've been using: rsync.penguinppc.org::linux-2.4-benh I found the info on http://www.penguinppc.org/dev/kernel.shtml Have fun, digger
Sound capture on PB with 2.6
Hello All, I was pleasantly surprised to to find that Alsa now has capture on a Powerbook with Snapper. I haven't been able to figure out how to use it. I have /proc/asound/card0/pcm0c/ but amixer doesn't report anything for Capture. Is Mic or Line yet to be implemented? Thanks digger
CapsLock makes powerbook go to sleep with benh2.6-test11
Hello All, With the benh-2.6-test11 kernel pressing CapsLock on my powerbook is putting it to sleep. This is not fun since I habitually hit it. Its happening both on the console and in X. It does not happen with benh-2.6-test9. With showkey I get, keycode 58 press keycode 58 release keycode 116 press keycode 116 release with a single key press and release. I believe both kernels were built with the same config. Any Ideas? Thanks for any help, digger
Re: CapsLock makes powerbook go to sleep with benh2.6-test11
On Thu, 2003-12-04 at 18:54, Benjamin Herrenschmidt wrote: > > To be precise: caps lock behaves like the power button. That putting the > > machine to sleep is pbbuttonsd silliness of course. > > Of course that doesn't happen on my tipb here... > > Can one of you check where those keycode come from ? I did changes If you mean look into the code, I'm sorry to say my coding skills are about zero. > a few bits in adbhid, but nothing that would cause that (well, I > don't think at least). Are we getting spurrious 0x7f codes from the > PMU itself ? I fail to see how that would happen with test11 and > not with another kernel though... > I just rsync'd and built a new kernel and it seems to be working correctly now. If your curious about the dates here's uname -a for the kernels: Linux myrna 2.6.0-test11 #1 Wed Dec 3 09:54:35 EST 2003 ppc GNU/Linux CapsLock goes to sleep (keycode 58 + 116) Linux myrna 2.6.0-test11 #1 Thu Dec 4 23:32:17 EST 2003 ppc GNU/Linux CapsLock fine Thanks for you help, digger
Re: How to get rid of sungem at boot time?
On Mon, 2005-10-17 at 08:54 +1000, Benjamin Herrenschmidt wrote:
> > I've done tests this afternoon, and what I found is that the devices
> > change that the system "sees" from one reboot to another. Specifically
> > it is this device on a Titanium IV that the system knows about in one
> > instance, that it does not know about any more at another reboot:
> >
...
> The solution would be to able to specify interfaces by MAC or position
> in sysfs rather than ethX name in /etc/network/interfaces... Volunteer
> to fix those scripts ?
>
The sysfs approach works for me. I have the file
"/etc/udev/local.rules" and a link to it in "/etc/udev/rules.d"
---
# /etc/udev/local.rules
#
# name the ethernet devices clearly
# Help provided by http://www.reactivated.net/udevrules.php
#
# To use make a simlink to /etc/udev/rules.d
KERNEL="eth*", SYSFS{address}="00:30:65:20:89:6d", NAME="airport"
KERNEL="eth*", SYSFS{address}="00:03:93:9d:ff:92", NAME="sungem"
#KERNEL="eth*", SYSFS{address}="", NAME="pcmcia"
--
Looks like I never got around to finishing it for my pcmcia card and
firewire port.
It's works nicely for me. I don't use ethX anymore
In /etc/network/interfaces I use "iface airport inet dhcp"
or "ifup sungem"
This link discusses how to do it.
http://www.reactivated.net/writing_udev_rules.html
digger
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to get rid of sungem at boot time?
On Mon, 2005-10-17 at 08:54 +1000, Benjamin Herrenschmidt wrote:
...
> > If the eth0 device above is missing at another system boot the whole
> > devices order is shifting, and changed, and as a consequence
> > previous eth2 (radio card) simply does not exist any more, thus
> > rendering my settings in the /etc/network/interfaces useless ... :)
>
> The solution would be to able to specify interfaces by MAC or position
> in sysfs rather than ethX name in /etc/network/interfaces... Volunteer
> to fix those scripts ?
>
The sysfs approach works for me. I have the file
"/etc/udev/local.rules" and a link to it in "/etc/udev/rules.d"
---
# /etc/udev/local.rules
#
# name the ethernet devices clearly
# Help provided by http://www.reactivated.net/udevrules.php
#
# To use make a simlink to /etc/udev/rules.d
KERNEL="eth*", SYSFS{address}="00:30:65:20:89:6d", NAME="airport"
KERNEL="eth*", SYSFS{address}="00:03:93:9d:ff:92", NAME="sungem"
#KERNEL="eth*", SYSFS{address}="", NAME="pcmcia"
--
Looks like I never got around to finishing it for my pcmcia card and
firewire port.
It's works nicely for me. I don't use ethX anymore
In /etc/network/interfaces I use "iface airport inet dhcp"
or "ifup sungem"
This link discusses how to do it.
http://www.reactivated.net/writing_udev_rules.html
digger
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bitkeeper trees: where is the debian linux bk for powerpc?
Hi Wolfgang, This isn't the answer to your question regarding bk, but may help. I use rsync for the benh kernels. rsync -avz --delete source.mvista.com::linuxppc-2.5-benh ~/src/2.5-benh Hope this is of help, digger On Fri, 2004-01-02 at 16:22, Wolfgang Pfeiffer wrote: > Hi All, > > I'm looking for bk for powerpc to download the benh kernel from > bk://ppc.bkbits.net/linuxppc-2.5-benh > according to the instructions given on > http://penguinppc.org/dev/kernel.shtml > > Where is it? > > All I found was > http://www.bitmover.com/cgi-bin/download.cgi > which is a form to fill out to download > bk-3.0.1-powerpc-glibc21-linux.bin > (At least I think I get this .bin after filling out the form there .. ) > > But is there a powerpc debian-tool for bk? > > Thanks in anticipation. > > Best regards > Wolfgang > > -- > Profile, Links: http://profiles.yahoo.com/wolfgangpfeiffer >
Re: Files in /var/log/ksymoops ?
On Mon, 2004-01-05 at 09:58, Simon Vallet wrote: > Hi, > > On Mon, 5 Jan 2004 12:12:33 +0100 > Sebastian Henschel <[EMAIL PROTECTED]> wrote: > ... > > > > are you sure, that vmlinuz and System.map have really been copied from > > the same source tree and generated from the same kernel-build? > well, not 100%, but I can't imagine how I could have messed this > up... > cp vmlinux /boot/vmlinux-2.4.23 && > cp System.map /boot/System.map-2.4.23 > ?? > Not so important anyway, I'll double-check > Thanks again, > Simon > Do you have a line in /etc/yaboot.conf like this: sysmap=/boot/System.map-2.4.23 digger
Re: Openfirmware & yaboot
Hello Joanary, Do you have have appropriate entries in yaboot.conf and run ybin? digger On Mon, 2004-01-19 at 17:02, Jaonary Rabarisoa wrote: > Hi all, > Is it possible to configure Openfirmware so that it can boot directly > debian. When booting I always have to open OF and type "boot > hd:9,yaboot" otherwise my machine boot directly with mac os 10.3 > > Thanks > > _ > Envie de discuter en "live" avec vos amis ? Tlcharger MSN Messenger > http://www.ifrance.com/_reloc/m la 1re messagerie instantane de France >
Re: Burning CD's on TiBook IV
Hi Wolfgang On Thu, 2004-02-12 at 15:53, Wolfgang Pfeiffer wrote: > Hi All > > I need some valid docs for burning CD's on a > Powerbook G4. > > I'm on unstable, 2.4.22-ben2., Gnome-2.4 > I'm using unstable also with a powerbook G4. > nautilus-cd-burner doesn't work, and the docs I found so far on CD > Burning don't seem to be reliable enough (outdated?) to change my > settings with them. > I believe that nautilus-cd-burner worked for me in the past. But then we are using unstable ;) I've also had good results with xcdroast. I believe the doc's that came with it were enough to help me get started. With the 2.4 kernel you'll probably want to use ide-scsi(?) module. I'm using a 2.6 kernel and its no longer needed. Hope this gives you something to go on digger
Re: ibook2 dmasound issues...
Hello Jared, On Thu, 2004-02-12 at 14:35, [EMAIL PROTECTED] wrote: > I am experiencing problems with my dmasound driver when trying to run > audacity. > It appears to be attempting to initialize the device for recording (which is > not supported) which causes dmasound to dump the device all together. Does > anyone know a workaround for this? I am not interested in recording, but my > job > requires analysis and playback of sound files. Thanks! > > -Jared > I'm also having trouble audacity along with alsa. What computer, kernel, sound driver, etc are you using? digger
Re: Burning CD's on TiBook IV
Hi wolfgang On Thu, 2004-02-12 at 20:11, Wolfgang Pfeiffer wrote: > On Thu, 2004-02-12 at 22:44, digger vermont wrote: > > Hi Wolfgang ... > > > > I've also had good results with xcdroast. I believe the doc's that came > > with it were enough to help me get started. With the 2.4 kernel you'll > > probably want to use ide-scsi(?) module. I'm using a 2.6 kernel and its > > no longer needed. > > Thanks. And yes, it helps .. > > Problem is, if I set up my CD stuff for 2.4, it won't work (or least > these 2.4 settings are deprecated) for 2.6. Or that's at least what I > found in the article below (which is, BTW, part of the cdrtools-doc > package). > > Actually the document (the "README.ATAPI.setup.gz") seems to be a good > starting point -- but I think I'll have to make a decision for 2.4 or > 2.6 ... :) More on it in the following docs, second part, below "Kernel > 2.6.*", first few lines there: README.atapi from the xcdroast docs "feel" less complicated. I don't recall having to do that much work. Perhaps because I use devfs? Keep in mind I don't burn too many cd's. With a 2.6.2-ben1 kernel I just started xcdroast and scanned for devices and it found the atapi cd-drive. I then booted a 2.4.24-ben1 kernel, started xcdroast, and scanned for devices. It found the "scsi" cd-drive. In neither case did I actually try to burn a cd. I just scanned the empty drive. As far as I can see the only difference is that I have the line, append="hdc=ide-scsi" in yaboot.conf's section for the 2.4 kernel. It seems to happen automagically. digger
Is Audacity working for anyone?
Hello All, Does anyone have audacity working? In particular for me the playback is horribly distorted. I imagine its the endian issue, but I thought that problem had been ironed out and it worked for me in the past. The playback is the same with both 2.4 and 2.6 both using alsa. Along with using the debian unstable pkg I also compiled audacity. Once again distortion. I'd appreciate hearing if it works or doesn't work for anyone. And/or what I might do to get it working. I've asked on the audacity-users list and have gotten no response. Thanks, digger
Re: Is Audacity working for anyone?
On Sun, 2004-02-15 at 14:17, Gregory Seidman wrote: > On Sat, Feb 14, 2004 at 09:45:10AM +0100, Joe Malik wrote: > } On Sat, Feb 14, 2004 at 12:35:25AM -0500, digger vermont wrote: > } > Hello All, > } > Does anyone have audacity working? In particular for me the playback is > } > horribly distorted. > } ... > } > } audacity from unstable seems to introduce a bug manifesting here as > } playback is distorted, where the version from testing plays nicely. > } You migt wanna give testing a try. > [...] > > I've experienced the same thing with my PPC 604. The sarge version works > fine, the side version is not so much distorted as pure static. I will > note that on x86 there is no problem with either version. > > --Greg > Thanks Joe and Greg for the info. I tried 1.0.1 from testing and it does playback okay. The features are on the sparse side though. This is probably going over old ground but I did trace it to an endian problem. I decided to compile different versions to see where it fails. Right off the bat the source for 1.0.0 from the audacity site played back with the same "noise". The only difference was a test to set big or little endian. adding that solve the problem. Unfortunately, the next higher version seemed to be completely rewritten and the same simple fix doesn't work. At this point I'm hoping that if I can compile audacity with alsa and jack support it may work. digger
Re: Is Audacity working for anyone?
On Sun, 2004-02-15 at 20:45, Gregory Seidman wrote: > On Sun, Feb 15, 2004 at 07:45:57PM -0500, digger vermont wrote: > [...] > } At this point I'm hoping that if I can compile audacity with alsa and > } jack support it may work. > > Please make sure to submit a bug on the Debian package. It will get > fixed, and that fix should find its way to the upstream distribution. > > } digger > --Greg I just filed one. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=232972 Thanks for the push I needed Greg! digger
Re: Is Audacity working for anyone?
Hello All, Just to let anyone interested know. I've compiled the source for Audacity 1.2.0-pre4 by replacing the portaudio-v19 directory with http://www.portaudio.com/archives/pa_snapshot_v19.tar.gz Playback is now okay for alsa and oss. Jack doesn't work though. digger On Sun, 2004-02-15 at 22:15, digger vermont wrote: > On Sun, 2004-02-15 at 20:45, Gregory Seidman wrote: > > On Sun, Feb 15, 2004 at 07:45:57PM -0500, digger vermont wrote: > > [...] > > } At this point I'm hoping that if I can compile audacity with alsa and > > } jack support it may work. > > > > Please make sure to submit a bug on the Debian package. It will get > > fixed, and that fix should find its way to the upstream distribution. > > > > } digger > > --Greg > > I just filed one. > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=232972 > > Thanks for the push I needed Greg! > > digger > >
Re: Need testers: G3 @ G4 laptops (powerbooks & ibooks)
On Wed, 2004-02-18 at 11:09, Colin Leroy wrote: > > 2.6.3-rc2-ben1 compiled fine. Does this have to do with your patch or > > did I screw up my configuration? > > > new radeonfb wants i2c-core in the kernel (CONFIG_I2C_CORE=y). Thanks digger
Re: Need testers: G3 @ G4 laptops (powerbooks & ibooks)
Hello Ben, I just rsync'd to 2.6.3-rc3-ben1 and added your patch. I get these errors: UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 drivers/built-in.o(.text+0x5f01c): In function `radeon_setup_i2c_bus': : undefined reference to `i2c_bit_add_bus' drivers/built-in.o(.text+0x5f17c): In function `radeon_delete_i2c_busses': : undefined reference to `i2c_bit_del_bus' drivers/built-in.o(.text+0x5f184): In function `radeon_delete_i2c_busses': : undefined reference to `i2c_bit_del_bus' drivers/built-in.o(.text+0x5f18c): In function `radeon_delete_i2c_busses': : undefined reference to `i2c_bit_del_bus' drivers/built-in.o(.text+0x5f194): In function `radeon_delete_i2c_busses': : undefined reference to `i2c_bit_del_bus' drivers/built-in.o(.text+0x5f224): In function `radeon_do_probe_i2c_edid': : undefined reference to `i2c_transfer' make: *** [.tmp_vmlinux1] Error 1 2.6.3-rc2-ben1 compiled fine. Does this have to do with your patch or did I screw up my configuration? digger On Tue, 2004-02-17 at 22:21, Benjamin Herrenschmidt wrote: > Hi need people who own those machiens, especially the recent iBook2 models > with a G3 CPU and titanium powerbooks with a G4, to test this patch and > tell me if sleep mode still works reliably or becomes unstable. > > (It won't help machines that cannot already sleep). > > Applies on top of current 2.6 but may apply to 2.4 as well.. > > Thanks ! > > Ben.
Re: Need testers: G3 @ G4 laptops (powerbooks & ibooks)
Hi Ben, On Tue, 2004-02-17 at 22:21, Benjamin Herrenschmidt wrote: > Hi need people who own those machiens, especially the recent iBook2 models > with a G3 CPU and titanium powerbooks with a G4, to test this patch and > tell me if sleep mode still works reliably or becomes unstable. > > (It won't help machines that cannot already sleep). > > Applies on top of current 2.6 but may apply to 2.4 as well.. It seems okay here. Linux myrna 2.6.3-rc3-ben1 #3 Wed Feb 18 11:28:22 EST 2004 ppc GNU/Linux processor : 0 cpu : 7455, altivec supported clock : 667MHz revision: 2.1 (pvr 8001 0201) bogomips: 665.60 machine : PowerBook3,4 motherboard : PowerBook3,4 MacRISC2 MacRISC Power Macintosh detected as : 73 (PowerBook Titanium III) pmac flags : 000b L2 cache: 256K unified memory : 512MB pmac-generation : NewWorld Thanks. digger
Kernel Oops after wakeup
Hello All, Occasionally I've been have kernel Oops. I've just started to recognize the the signs to look for before it ends in freezing. It tends to happen after sleeping but I'm not sure if it starts there. I'm using a 2.6.3-ben2 kernel but I believe the same thing was happening with the 2.4 kernels. This time one partition ended up pretty corrupted. Once in the past the mac osx side was corrupted to the point it wouldn't boot. Does this look like a hard drive problem? I've included the entire dmesg not sure where it begins to be relevant. Unfortunately I didn't realize I should have ran it through ksymoops before I rebooted to get /proc/kysms, lsmod etc. Is there any other info I can provide? Thanks for any help, digger e2109c5c IN from bad port 2f0 at e2109c38 IN from bad port 2f1 at e2109c5c IN from bad port 2f8 at e2109c38 IN from bad port 2f9 at e2109c5c IN from bad port 300 at e2109c38 IN from bad port 301 at e2109c5c IN from bad port 308 at e2109c38 IN from bad port 309 at e2109c5c IN from bad port 310 at e2109c38 IN from bad port 311 at e2109c5c IN from bad port 318 at e2109c38 IN from bad port 319 at e2109c5c IN from bad port 320 at e2109c38 IN from bad port 321 at e2109c5c IN from bad port 328 at e2109c38 IN from bad port 329 at e2109c5c IN from bad port 330 at e2109c38 IN from bad port 331 at e2109c5c IN from bad port 338 at e2109c38 IN from bad port 339 at e2109c5c IN from bad port 340 at e2109c38 IN from bad port 341 at e2109c5c IN from bad port 348 at e2109c38 IN from bad port 349 at e2109c5c IN from bad port 350 at e2109c38 IN from bad port 351 at e2109c5c IN from bad port 358 at e2109c38 IN from bad port 359 at e2109c5c IN from bad port 360 at e2109c38 IN from bad port 361 at e2109c5c IN from bad port 368 at e2109c38 IN from bad port 369 at e2109c5c IN from bad port 370 at e2109c38 IN from bad port 371 at e2109c5c IN from bad port 378 at e2109c38 IN from bad port 379 at e2109c5c IN from bad port 380 at e2109c38 IN from bad port 381 at e2109c5c IN from bad port 388 at e2109c38 IN from bad port 389 at e2109c5c IN from bad port 390 at e2109c38 IN from bad port 391 at e2109c5c IN from bad port 398 at e2109c38 IN from bad port 399 at e2109c5c IN from bad port 3a0 at e2109c38 IN from bad port 3a1 at e2109c5c IN from bad port 3a8 at e2109c38 IN from bad port 3a9 at e2109c5c IN from bad port 3b0 at e2109c38 IN from bad port 3b1 at e2109c5c IN from bad port 3b8 at e2109c38 IN from bad port 3b9 at e2109c5c IN from bad port 3c0 at e2109c38 IN from bad port 3c1 at e2109c5c IN from bad port 3c8 at e2109c38 IN from bad port 3c9 at e2109c5c IN from bad port 3d0 at e2109c38 IN from bad port 3d1 at e2109c5c IN from bad port 3d8 at e2109c38 IN from bad port 3d9 at e2109c5c IN from bad port 3e0 at e2109c38 IN from bad port 3e1 at e2109c5c IN from bad port 3e8 at e2109c38 IN from bad port 3e9 at e2109c5c IN from bad port 3f0 at e2109c38 IN from bad port 3f1 at e2109c5c IN from bad port 3f8 at e2109c38 IN from bad port 3f9 at e2109c5c IN from bad port 400 at e2109c38 IN from bad port 401 at e2109c5c IN from bad port 408 at e2109c38 IN from bad port 409 at e2109c5c IN from bad port 410 at e2109c38 IN from bad port 411 at e2109c5c IN from bad port 418 at e2109c38 IN from bad port 419 at e2109c5c IN from bad port 420 at e2109c38 IN from bad port 421 at e2109c5c IN from bad port 428 at e2109c38 IN from bad port 429 at e2109c5c IN from bad port 430 at e2109c38 IN from bad port 431 at e2109c5c IN from bad port 438 at e2109c38 IN from bad port 439 at e2109c5c IN from bad port 440 at e2109c38 IN from bad port 441 at e2109c5c IN from bad port 448 at e2109c38 IN from bad port 449 at e2109c5c IN from bad port 450 at e2109c38 IN from bad port 451 at e2109c5c IN from bad port 458 at e2109c38 IN from bad port 459 at e2109c5c IN from bad port 460 at e2109c38 IN from bad port 461 at e2109c5c IN from bad port 468 at e2109c38 IN from bad port 469 at e2109c5c IN from bad port 470 at e2109c38 IN from bad port 471 at e2109c5c IN from bad port 478 at e2109c38 IN from bad port 479 at e2109c5c IN from bad port 480 at e2109c38 IN from bad port 481 at e2109c5c IN from bad port 488 at e2109c38 IN from bad port 489 at e2109c5c IN from bad port 490 at e2109c38 IN from bad port 491 at e2109c5c IN from bad port 498 at e2109c38 IN from bad port 499 at e2109c5c IN from bad port 4a0 at e2109c38 IN from bad port 4a1 at e2109c5c IN from bad port 4a8 at e2109c38 IN from bad port 4a9 at e2109c5c IN from bad port 4b0 at e2109c38 IN from bad port 4b1 at e2109c5c IN from bad port 4b8 at e2109c38 IN from bad port 4b9 at e2109c5c IN from bad port 4c0 at e2109c38 IN from bad port 4c1 at e2109c5c IN from bad port 4c8 at e2109c38 IN from bad port 4c9 at e2109c5c IN from bad port 4d0 at e2109c38 IN from bad port 4d1 at e2109c5c IN from bad port 4d8 at e2109c38 IN from bad port 4d9 at e2109c5c IN from bad port 4e0 at e2109c38 IN from bad port 4e1 at e2109c5c IN from bad port 4e8 at e2109c38 IN from bad port 4e9 at e2109c5c IN from bad po
Re: Kernel Oops after wakeup
Hello, I realized at least this could be useful. digger cat /proc/cpuinfo processor : 0 cpu : 7455, altivec supported clock : 667MHz revision: 2.1 (pvr 8001 0201) bogomips: 665.60 machine : PowerBook3,4 motherboard : PowerBook3,4 MacRISC2 MacRISC Power Macintosh detected as : 73 (PowerBook Titanium III) pmac flags : 000b L2 cache: 256K unified memory : 512MB pmac-generation : NewWorld Module Size Used by snd_vxpocket4736 1 snd_vx_cs 13920 1 snd_vxpocket snd_vx_lib 38304 1 snd_vx_cs snd_hwdep 8900 1 snd_vx_lib snd_seq_oss39000 0 snd_seq_midi_event 7168 1 snd_seq_oss snd_seq59096 4 snd_seq_oss,snd_seq_midi_event snd_pcm_oss64548 0 snd_mixer_oss 20544 1 snd_pcm_oss snd_usb_audio 73600 0 snd_rawmidi24064 1 snd_usb_audio snd_seq_device 8008 3 snd_seq_oss,snd_seq,snd_rawmidi snd_powermac 38864 0 snd_pcm 108056 4 snd_vx_lib,snd_pcm_oss,snd_usb_audio,snd_powermac snd_page_alloc 11236 1 snd_pcm snd_timer 24452 2 snd_seq,snd_pcm snd59832 14 snd_vx_cs,snd_vx_lib,snd_hwdep,snd_seq_oss,snd_seq_midi_event,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_usb_audio,snd_rawmidi,snd_seq_device,snd_powermac,snd_pcm,snd_timer soundcore 8804 1 snd ds 15076 6 snd_vxpocket,snd_vx_cs yenta_socket 16288 1 pcmcia_core75256 3 snd_vx_cs,ds,yenta_socket radeon132204 2 rfcomm 32728 0 l2cap 23780 5 rfcomm bluetooth 53984 4 rfcomm,l2cap ipt_ttl 2208 1 ipt_limit 2560 33 ipt_state 2112 5 ipt_MASQUERADE 3648 0 ipt_TOS 2720 0 ipt_REDIRECT2432 0 ipt_REJECT 6720 0 ip_conntrack_irc 71196 0 ip_conntrack_ftp 71872 0 i2c_keywest 9668 0 ipt_LOG 7008 1 iptable_mangle 2912 0 iptable_filter 2880 1 iptable_nat24530 2 ipt_MASQUERADE,ipt_REDIRECT ip_conntrack 33452 6 ipt_state,ipt_MASQUERADE,ipt_REDIRECT,ip_conntrack_irc,ip_conntrack_ftp,iptable_nat ip_tables 17856 11 ipt_ttl,ipt_limit,ipt_state,ipt_MASQUERADE,ipt_TOS,ipt_REDIRECT,ipt_REJECT,ipt_LOG,iptable_mangle,iptable_filter,iptable_nat ohci_hcd 20836 0 ehci_hcd 27236 0 usbcore 112184 5 snd_usb_audio,ohci_hcd,ehci_hcd uninorth_agp6752 1 agpgart33228 2 uninorth_agp vfat 13952 0 ide_cd 45156 0 cdrom 43836 1 ide_cd fat46212 1 vfat apm_emu 6604 1 airport 5760 0 orinoco50452 1 airport hermes 13536 2 airport,orinoco On Wed, 2004-02-25 at 23:28, digger vermont wrote: > Hello All, > Occasionally I've been have kernel Oops. I've just started to > recognize the the signs to look for before it ends in freezing. It > tends to happen after sleeping but I'm not sure if it starts there. I'm > using a 2.6.3-ben2 kernel but I believe the same thing was happening > with the 2.4 kernels. This time one partition ended up pretty > corrupted. Once in the past the mac osx side was corrupted to the point > it wouldn't boot. > > Does this look like a hard drive problem? > > I've included the entire dmesg not sure where it begins to be relevant. > Unfortunately I didn't realize I should have ran it through ksymoops > before I rebooted to get /proc/kysms, lsmod etc. > > Is there any other info I can provide? > > Thanks for any help, > > digger > > e2109c5c > IN from bad port 2f0 at e2109c38 > IN from bad port 2f1 at e2109c5c > IN from bad port 2f8 at e2109c38 > IN from bad port 2f9 at e2109c5c > IN from bad port 300 at e2109c38 > IN from bad port 301 at e2109c5c > IN from bad port 308 at e2109c38 > IN from bad port 309 at e2109c5c > IN from bad port 310 at e2109c38 > IN from bad port 311 at e2109c5c > IN from bad port 318 at e2109c38 > IN from bad port 319 at e2109c5c > IN from bad port 320 at e2109c38 > IN from bad port 321 at e2109c5c > IN from bad port 328 at e2109c38 > IN from bad port 329 at e2109c5c > IN from bad port 330 at e2109c38 > IN from bad port 331 at e2109c5c > IN from bad port 338 at e2109c38 > IN from bad port 339 at e2109c5c > IN from bad port 340 at e2109c38 > IN from bad port 341 at e2109c5c > IN from bad port 348 at e2109c38 > IN from bad port 349 at e2109c5c > IN from bad port 350 at e2109c38 >
Re: Kernel Oops after wakeup
On Fri, 2004-02-27 at 05:07, Benjamin Herrenschmidt wrote: > > IN from bad port 2f0 at e2109c38 > > IN from bad port 2f1 at e2109c5c > > IN from bad port 2f8 at e2109c38 > > IN from bad port 2f9 at e2109c5c > > etc... > > What is this driver from hell ? You are running a driver for > some legacy x86 junk that is tapping random IO ports, that's > very bad. It comes from pcmcia-cs. This is all without any card in the slot. 2.6.3-ben2: Feb 28 18:33:08 [sudo] digger : TTY=pts/2 ; PWD=/home/digger ; USER=root ; COMMAND=/etc/init.d/pcmcia restart Feb 28 18:33:08 [cardmgr] exiting Feb 28 18:33:08 [cardmgr] watching 1 socket Feb 28 18:33:08 [kernel] cs: IO port probe 0x0c00-0x0cff:<7>IN from bad port c00 at e2109c38 Feb 28 18:33:08 [kernel] IN from bad port c01 at e2109c5c Feb 28 18:33:08 [kernel] cs: IO port probe 0x0800-0x08ff:<7>IN from bad port 800 at e2109c38 Feb 28 18:33:08 [kernel] IN from bad port 801 at e2109c5c Feb 28 18:33:08 [kernel] IN from bad port 808 at e2109c38 Feb 28 18:33:08 [kernel] cs: IO port probe 0x0100-0x04ff:<7>IN from bad port 100 at e2109c38 Feb 28 18:33:08 [kernel] IN from bad port 101 at e2109c5c Feb 28 18:33:08 [kernel] IN from bad port 3b8 at e2109c38 Feb 28 18:33:08 [kernel] IN from bad port 3c8 at e2109d1c Feb 28 18:33:08 [kernel] IN from bad port 3d0 at e2109d1c Feb 28 18:33:08 [cardmgr] starting, version is 3.2.5 This from 2.4.25-ben1: Feb 28 18:42:54 [sudo] digger : TTY=pts/2 ; PWD=/home/digger ; USER=root ; COMMAND=/etc/init.d/pcmcia restart Feb 28 18:42:54 [cardmgr] exiting Feb 28 18:42:55 [kernel] ti113x: Routing card interrupts to PCI Feb 28 18:42:55 [kernel] unloading Kernel Card Services Feb 28 18:42:55 [kernel] Linux Kernel Card Services 3.1.22 Feb 28 18:42:55 [kernel] Yenta ISA IRQ mask 0x, PCI irq 58 Feb 28 18:42:55 [cardmgr] watching 1 socket Feb 28 18:42:55 [kernel] cs: IO port probe 0x0c00-0x0cff: clean. Feb 28 18:42:55 [kernel] cs: IO port probe 0x0800-0x08ff: clean. Feb 28 18:42:55 [kernel] cs: IO port probe 0x0100-0x04ff: clean. Feb 28 18:42:55 [cardmgr] starting, version is 3.2.5 One thing I noticed is that with a 2.6 kernel the pcmcia modules aren't unloaded with /etc/init.d/pcmcia stop or restart. and the initial starting of card services at boot isn't right. 2.6.3-ben2: Feb 28 19:00:44 [kernel] Linux Kernel Card Services Feb 28 19:00:44 [kernel] bus pci: add driver yenta_cardbus Feb 28 19:00:44 [kernel] bound device '0001:01:1a.0' to driver 'yenta_cardbus' Feb 28 19:00:44 [kernel] bus type 'pcmcia' registered Feb 28 19:00:44 [cardmgr] starting, version is 3.1.33 Feb 28 19:00:45 [cardmgr] no sockets found! Feb 28 19:00:45 [cardmgr] exiting Sometimes restarting pcmcia will cause the computer to "freeze." No mouse, keys, or disk io. Also, if the vxpocket modules are loaded first by also with 2.6 it seems to add to the problems. If I stop alsa and restart pcmcia it seems to work. And then, I'm using the testing version of pcmcia-cs. With the unstable version of pcmcia-cs, vxloader doesn't find vxpocket to load the firmware. Don't know how that relates to it. At this point I've tried so many combinations and rebooted so often I'm a bit lost. If there any suggestions I can give then a try. thanks, digger If of any use the output of uname proc/cpuinfo, lsmod, /proc/ioports, /proc/iomem, and entries in /etc/pcmcia/config.opts are below. uname -a Linux myrna 2.6.3-ben2 #1 Sat Feb 28 11:53:07 EST 2004 ppc GNU/Linux cat /proc/cpuinfo processor : 0 cpu : 7455, altivec supported clock : 667MHz revision: 2.1 (pvr 8001 0201) bogomips: 665.60 machine : PowerBook3,4 motherboard : PowerBook3,4 MacRISC2 MacRISC Power Macintosh detected as : 73 (PowerBook Titanium III) pmac flags : 000b L2 cache: 256K unified memory : 512MB pmac-generation : NewWorld lsmod Module Size Used by radeon132204 2 ds 15076 0 yenta_socket 16288 0 pcmcia_core75256 2 ds,yenta_socket ipt_ttl 2208 1 ipt_limit 2560 33 ipt_state 2112 5 ipt_MASQUERADE 3648 0 ipt_TOS 2720 0 ipt_REDIRECT2432 0 ipt_REJECT 6720 0 ip_conntrack_irc 71196 0 ip_conntrack_ftp 71872 0 snd_seq_oss39000 0 snd_seq_midi_event 7168 1 snd_seq_oss snd_seq59096 4 snd_seq_oss,snd_seq_midi_event snd_seq_device 8008 2 snd_seq_oss,snd_seq snd_pcm_oss64548 0 snd_mixer_oss 20544 1 snd_pcm_oss i2c_keywest 9668 0 snd_powermac 38864 0 snd_pcm 108056 2 snd_pcm_oss,snd_powermac snd_page_alloc 11236 1 snd_pcm snd_timer 24452 2 snd_seq,snd_pcm snd59832 9 snd_seq_oss,snd_seq_midi_event,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_powermac,snd_pcm,snd_timer soundcore 8804 1 sn
Re: Alsa configuration problem
Hello, On Fri, 2004-03-05 at 05:55, Utilisateur Debian wrote: > Hi all, > Alsa seems to be correctly installed in my system but I don't still have > the sound. Here is the out put when I restart it with: > "/etc/init.d/alsa restart" > > debian:/etc/init.d# /etc/init.d/alsa restart > Storing ALSA mixer settings ... done. > Shutting down ALSA (version 0.9.7): done. > Starting ALSA (version 0.9.7): ALSA appears to be compiled statically. On my computer, with alsa compiled as modules (is there any other way?), I get this message if the modules are already loaded when alsa is starting. digger
Re: [YABOOT] Preliminary ofpath with 2.6 kernel support NEEDS TESTING
Hello Ethan, The new ofpath gives the same dir's for 2.4.25 and 2.6.4. It works fine to boot linux and macosx on my powerbook. I didn't try a cd. I never had any problems though and yaboot.conf used /dev/xxx statements to begin with: boot=/dev/hda9 device=hd: partition=11 root=/dev/hda11 timeout=30 install=/usr/lib/yaboot/yaboot magicboot=/usr/lib/yaboot/ofboot macosx=/dev/hda16 /proc/cpuinfo processor : 0 cpu : 7455, altivec supported clock : 667MHz revision: 2.1 (pvr 8001 0201) bogomips: 665.60 machine : PowerBook3,4 motherboard : PowerBook3,4 MacRISC2 MacRISC Power Macintosh detected as : 73 (PowerBook Titanium III) pmac flags : 000b L2 cache: 256K unified memory : 512MB pmac-generation : NewWorld Thanks, digger On Sun, 2004-03-21 at 21:35, Ethan Benson wrote: > Hello, > > As many are painfully aware ofpath in current yaboot does not function > correctly under 2.6 systems, worse case it gives out bogus paths > therefore causing the system to fail to boot. > > I have preliminary changes in current development version of yaboot > which fixes ofpath to support 2.6.4 and above kernels. > > I need everyone with 2.6.4 or newer systems to test this version of > ofpath and verify that it produces correct OpenFirmware paths to your > devices (compare with ofpath output from a recent 2.4 kernel (2.4.23 > or newer)) > > Prerequisites: > > * You must have 2.6.4 or newer, previous versions lack necessary > sysfs information. > > * You must have sysfs mounted (normally on /sys, but ofpath should be > able to detect where its mounted). > > * You must still have /proc/ide so if this becomes a configurable > option like /proc/scsi you must have it enabled (/proc/scsi is also > required for machines with SATA drives). > > The easiest way to test the new ofpath is download the current version > from http://penguinppc.org/~eb/files/ofpath and install it manually: > > as root enter: > > which ofpath > > this will return the path of the active ofpath program, probably > /usr/sbin/ofpath > > move it to safe place: > > mv `which ofpath` /root > > install the new version (put it in the same place as the old one was, > see step 1): > > install -m 755 /home/youruser/ofpath /usr/sbin/ofpath > > run ofpath on all your disk devices and ensure its output is correct. > > then comment out any ofboot= lines in /etc/yaboot.conf and change your > macos* entries back to /dev/ nodes, run ybin and ensure the bootloader > functions correctly. > > MOST IMPORTANTLY: > > * REPORT SUCCESS *AND* FAILURE * > > I want to know what kind of machine you have, and that ofpath worked > correctly, I will release yaboot 1.3.12 once I have enough success > reports for enough differing machines, very new machines are most > important, as they are the ones which old ofpath failed on. > > Thanks in advance, and thanks to Nick Lopez for granting me local > shell access to his machine so I could get this done.
Re: gtkpbbuttons 0.6.2 unofficial package
Hello Stefano, Have you any thought to package powerprefs? Thanks for the other pbbuttons pkgs, digger On Tue, 2004-03-23 at 10:40, Stefano Zacchiroli wrote: > On Tue, Mar 23, 2004 at 02:23:44PM +0100, Stefano Zacchiroli wrote: > > I've just packaged pbbuttonsd 0.5.9. I've forward ported the last 0.5.3 > > and reviewed a bit the old packaging, for more info the changelog is > > attached. > > > > The packages are available at: > > > > deb http://www.bononia.it/~zack/ debian/ > > deb-src http://www.bononia.it/~zack/ debian/ > > Same for gtkpbbuttons 0.6.2, packages available at the same URLs. > > Cheers.
Re: pbbuttonsd script interface - future?
Hi Matthias, On Mon, 2004-04-19 at 14:01 +0200, Matthias Grimm wrote: > Hi, > Today I would ask for opinions and ideas about the future of pbbuttonsd's > script interface. To become more flexible and maybe share development and > infrastructure with other powermanagement systems (like apmd) for sure the > script environment and maybe the interface must be reformed. > ... > Are two modes (minimum power consumption, maximum performance) enough or > do we need an additional custom mode? Makes such a mode sense? Will it be > used > by the user? > I'd like to see some scripts for "sleep" and "wakeup". In particular I would like, if while logged in, scripts in my home directory (perhaps ".sleeprc" and "wakeuprc") could be sourced. Would be useful for say waking a fetchmail daemon to check mail. Also, as someone else mentioned, differentiate between ac and battery for different power/performance levels. Thanks for asking for input, digger
Re: recording sound ?
Hi Soeren, On Sun, 2004-03-07 at 20:42 +0100, Soeren Sonnenburg wrote: > Hi all... > > is it possible to somehow use the internal microphone (full duplex ?!) > to get h323 voip to run (using e.g. gnomemeeting) ? > I believe it depends on what computer you have. I have a powerbook g4 with a Snapper sound-chip. Unfortunately the last time I tried the internal mic barely worked. There is a capture device, but no real control of it. The best I can get is a distorted low level signal. digger
Re: recording sound ?
Hi Soeren, On Wed, 2004-04-21 at 07:14 +0200, Soeren Sonnenburg wrote: > On Wed, 2004-04-21 at 00:36, digger vermont wrote: ... > > > > I believe it depends on what computer you have. I have a powerbook g4 > > with a Snapper sound-chip. Unfortunately the last time I tried the > > internal mic barely worked. There is a capture device, but no real > > control of it. The best I can get is a distorted low level signal. > > Actually I tried gnomemeeting yesterday. And YES it really works with > the internal microphone on kernel 2.6.5+ with alsa enabled. > Great! I hadn't tried since alsa 1.01 or so. I'm also now getting better results, actually usable results. It is very touchy to set the levels though. Would be nice to have a recording level control. > I did check whether line-in works nicely... > > However I was pretty excited that it worked at all :) Me too! digger
Where to find libltdl3-dev_1.5.2-1_powerpc.deb?
Hello All, Thinking that the problem with gnucash and libltdl was solved I upgraded them both. The problem is not fixed. Now I'd like to downgrade libltdl3 to 1.5.2-1 but it doesn't exist any more on the repositories. The only platform its available for is hurd. What happened to it? I thought older versions were kept on the sites for awhile? The source doesn't seem to be available either. Other than the usual repositories is there any place I might find it? Thanks digger
Re: Where to find libltdl3-dev_1.5.2-1_powerpc.deb?
On Tue, 2004-05-04 at 17:30 -0400, Mike Small wrote: > If you don't mind missing the business core module functionality > you could do what I did and comment out the following line (#427) in > /usr/share/gnucash/guile-modules/gnucash/main.scm: > > (load-module "gnucash/business-gnome" 0 #t) > > Doing this hasn't caused me any problems and gets past the > related so being absent without downgrading libltdl3. > Thanks Mike, that took care of it. No excuses to pay my bills now :( digger
Re: Mol problem loading OSX partition 2.6.6 kernel
On Tue, 2004-05-25 at 17:18 +0100, Rory Campbell-Lange wrote: > I'm trying to get mol to load my OSX partition. > > I've set > blkdev: /dev/hda16 -rw > > startmol --osx > > --> The volume '/dev/hda16' is locked > ... > Can't read Elf32 image header > Fatal error: drivers/bootx is not an ELF image > Ahh! Funny thing, I had exactly the same problem last night. On a reinstall I had accidentally installed the mac 0s9 drivers instead of osx. Do you have mol-drivers-macosx installed? Good luck, digger
