>After some thinking, you should even be able to just get the libc6 etc. debs
>from unstable and continue with testing otherwise.
I finally switched over to sid and now doing a dist-upgrade (finger crossed ;)
Ben.
My email address is changing ! Please, now use
[EMAIL PROTECTED]
Thanks !
Ben.
>I'm running with kernel 2.2.17 and X-4.0.1. I might try disabling the X
>server and see if that makes any difference. Maybe I have to setup my
>sound system some how ???
>
>Does anybody else have a new powerbook th
Are you using a sound daemon like esound ? Or directly playing thru /dev/
dsp
>I am not doing anything with audio at all (not actively anyways). I do
>however seem to have esound installed. I have enlightenment installed
>but have now switched to sawmill-gnome.
>
>Is esound known to be broken on powerpc ?
>Is there a better sound daemon that is recommended for powerpc ?
>However I read some reports on linuxppc-users from people not being
>able to boot Linux from MacOS 9.1/BootX anymore. Has anyone else had
>trouble/success booting into Linux from 9.1 with BootX, especially
>on an OldWorld machine? Thanks,
Don't kill you existing MacOS so you can revert to it if
>
>I just actually tried the "snooze -f" on my laptop, and it works very
>very fine.
>Thanks a lot for that.
I don't know what snooze -f flag does, but AFAIK, the snooze command that
comes with pmud just calls pmud and so triggers the "emulated" sleep. Am
I wrong ?
The sleep code hasn't changed l
>I am very glad that Linux runs this well on my Pismo, yet I belong to that
>apparently vanishing (at least in Steve Jobs' opinion) group of people who
>still use floppies on a regular basis, and therefore decided to order a
>VSTTech Superdisk/1.44 floppy drive for my Pismo's right-hand side exp
>Yep, simple naming inconsistency. There was a patch for this floating
>around some time ago (it might even have been submitted to sourceforge).
>But like so many useful patches, it went into the wind...
Looks like that inconsistency takes its origins from the original PC
serial driver. The funny
>
>Nope, just missing sleep support in the kernel. Will be fixed as soon as
>someone with a Pismo does some serious kernel hacking to properly
>implement sleep, and posts the patch to linuxppc-dev.
Well, I'm doing regular serious kernel hacking with a Pismo and still
couldn't get sleep to work...
>
>That wasn't directed at you, as I hope you knew well enough. But we could
>need a few more eyes looking at this problem. Even though it seems to fall
>into the 'hopeless' class :-)
Well, we are close to it. Darwin source has sleep support for the
machine, so except for some binary only drivers,
dist-upgrade to current unstable leads to all sorts of weird segfaults on
a dual G4 running a recent 2.4.2pre kernel here, including with locally
compiled apps. One example I have in mind is gkrellm (who works perfectly
well on another box using a slightly older snapshot of unstable).
libc issue ?
>On 02/22/2001 17:49, "Ethan Benson" <[EMAIL PROTECTED]> wrote:
>
>> On Thu, Feb 22, 2001 at 01:28:04PM -0500, Advertising wrote:
>>
>> all the problems you describe are the fault of Aladdin and thier
>> proprietary crap product and monopolistic practices.
>
>With all respect, that is nonsense. An
>On Mon, 26 Feb 2001, Michel Dänzer wrote:
>> I just had an interesting idea: The flat panel code could never
>determine the
>> panel dimensions because our machines don't have a BIOS. So I
specified them
>> with
>>
>> Option "PanelWidth" "1024"
>> Option "PanelHeight" "768"
>>
>> and it wo
>> I'd know a way... the same way that the fbdev drivers use.
>> cat /proc/cpuinfo | grep machine to see what i mean
>
>I see. Unfortunately, this has the same 'problems' as the fbdev approach
>(Linux only, /proc must be mounted, ...)
That won't help for machines like the wallstreet that exist in
>AFAIK yaboot only works with NewWorld-Macs and a boot-menu run by
>OpenFirmware doesn´t help because OpenFirmware on this machine is so buggy.
I think there's a utility SetPRAMBoot floating around that allow you to
change the ROM boot device in nvram from Linux on oldworld
Ben.
>there is always quikboot, works fine on my machine. For setting OF
>parameters, check the manpage of 'nvsetenv'. You will find usefull
>information there.
>
>Unfortunately, when booting MacOS, they like to erase the OF settings to
>default. There is a program called systemdisk. I found very usefu
>I think that the answer to the original question is that when
>booting from BootX, you have to have a kernel that supports SMP, but
>the stock kernel does not, so you have to build your own, and put it
>where BootX can find it.
>
>I don't think there is anything that you need to do to your PRAM,
>
> With kernel 2.4.2, I can boot my quad CPU Daystar Mac clone from BootX and
>run all four CPUs. (I'm going to have to do something about that kernel,
>since I've already had it lock up once. I'm trying to get the machine set
>up well enough to use it for my primary workstation, but I don't have
>Use nvsetenv:
>
>[EMAIL PROTECTED] ~]$ rpm -qf `which nvsetenv`
>pmac-utils-1.1.1-1b
>
>-- on my LinuxPPC box.
>
>nvsetenv boot-device "/AAPL,ROM"
>
>and on next reboot you go into MacOS. From MacOS, use your existing
>tools (if any) or bootvars to reset boot-device and boot-file back to
>what yo
>
> I haven't been using the machine much. I booted it up again to look
>through the logs, and I noticed that I had 2.4.1, not .2, so things were
>even worse! While compiling 2.4.2, I saw an error message:
>_spin_unlock(c014301c): cpu3 trying clear of cpu 2 pc c0042d34 val ff
>There are a cou
>That would explain it, because the youngest macos I have is 8.1. I
>take it that the latest dual G4s are a different architecture?
They are a completely different architecture, and you don't boot them
with BootX or miBoot, but from OpenFirmware.
>If he doesn't change kernels a lot he can use th
>Can you send me your System.map for that kernel?
>
>The linuxcare.com kernels that Paul keeps have changes that he's not ready
>to push into the main tree yet. It's likely you discovered one of the
>reasons he holds off on pushing his changes :) You may want let Paul know,
>too.
I would rather
>
>The First two days I need to discover that yaboot 1.1.1 does not work
>with the TiPB and to find a typo in my bootscript. So I copied the
>yaboot from the LinuxPPC 2000 Q4-CD.
Can you tell me what happend with yaboot 1.1.1 ? It should work.
>I tried to boot with a selfcompiled kernel that I us
>it would be non-trivial, the codec only work with quicktime which is
>not available for anything but macos and windows. in theory it would
>be possible to make a binary compatibility system where you could run
>osx binaries on linux similar to running linux binaries on freebsd.
>but if the macosx
>> I want to try building my own kernel for my TiBook (2.4.x) but I don't know
>> what sort of ethernet hardware it has.
>
>Should be gmac, like any recent Apple machine.
I've had reports that the ethernet PHY of the TiBook was not recognized by
the current kernel.
I suggest you try my "devel" ke
> just successfully put this Pismo to sleep with snooze and woke it up with
>the space bar. :)
>
>Will this also work by just closing the lid, or will I have to tweak the
>pwrctl script for that?
If you have pmud installed, closing the lid will work. I added today some
support for USB remote wakeu
>> I just successfully put this Pismo to sleep with snooze and woke it up with
>> the space bar. :)
>>
>> Will this also work by just closing the lid, or will I have to tweak the
>> pwrctl script for that?
>
>AFAIR pmud doesn't actually shut down the Pismo when the lid is closed.
>The tweaks to the
>> I think I know why the TiPB dies. Looks like the kernel doesn't properly
>> recognize the 7410 CPU as having an L2 cache, and so we don't properly
>> flush it & invalidate it. (We don't catch the altivec neither). I'm
>> working on a fix.
>
>Do you regard sleep support on Pismo and the Ti suffic
>
>I am now able to use snooze -f to put my pismo to sleep!! Thankyou Ben
>H.
>
>When I do, however, isntead of going black my display does this slowly
>evolving technicolor firework thing that doesn't look healthy for the
>display.
>
>Is there a new pwrctl file that handles sleep better for core9
>Yup, that was it. No more purple haze effects. However sleep is
>unreliable at best. It usually fails to wakeup properly most times I
>attempt it. No screen, no disk, green sleep light stops, but nothing
>happens.
Keep up to date with rsync. The current tree works just fine on my
Pismo and most
>From my experience with the iBook sleep a couple of months ago, I think
>it is actually possible to plug some juice back in and wake the machine
>up. At that point I experienced some video garbling, but nothing else.
>It was enough for me to close down the applications and restart the
>computer in
>On Sat, Mar 31, 2001 at 02:49:55PM +0200, Benjamin Herrenschmidt wrote:
>> Keep up to date with rsync. The current tree works just fine on my
>> Pismo and most other testers using Pismos, iMacs or iBooks. The only
>> one known to still cause problems is the TiPb.
>
>I
>
>Also, can Batmon be made to give battery status on the TiBook, or is
>there another tool that can? Right now running Batmon returns
>"/usr/bin/Batmon: no such file" (i.e. Batmon exists, but it is
>looking for some file that isn't). Any suggestions?
There's also a nice pmud plugin for gkrel
>I´ve just tested your kernel on my TiPB and can tell that both users are
>right. I ´ve just put my TiPB to sleep with mol running (close lid)
>after 30 minutes I opened the lid and mol was running fine, no problems,
>
>At this moment I ran X and the TiPB is sleeping, with this nice blinking
>LED.
>> I'm afraid the problem with the pmud still exists.
>> Okay, I'm running 2.2.17 paulus (self-compiled)
>> on a powerbook 2400; dist is debian 2.2, pmud
>> is version 0.7-3 (the most recent).
>>
>> When the PB2400 is going to snooze while the
>> harddisk is currently working, it won't properly
>>
>
>Do you have something new to test for sleep on TiPB?
>
>BTW. If I remember right, FireWire is not switched off during sleep,
>will this happen in the near future?
>Maybe some interface to configure which device should be powered on
>during sleep and which device can be powered off during sleep.
>I've a similar problem (that almost cost me my sanity a few minutes
>ago when my powerbook3400 wouldn't boot up, the very same pb that
>contained my very important project to be handed in tomorrow)
>
>Basically, if I disconnect it from the ac adapter and put it to sleep
>or wake it up, it won't wa
>> Hmmm... using 'fblevel 0' I don't see any ghosts, but when I use
>> snooze I do...
>
>curiouser and curiouser. I just tested on my TiPB, with both fblevel and
>backlight (I assume they do the same thing), and setting the level to
>either 0 or off shows the same ghosts, as does "snooze".
My ker
>Have other TiPB owners noticed the 'book heating up more under Linux than
>MacOS(X)? I especially notice the area around the ethernet connector gets
>toasty. Keeps my right hand warm ;)
>
>What's the status of power management in the current kernels?
The current kernel won't properly enable the
>I am trying to get Debian 2.2 on a 9600/200MP.
>When I reboot I get the Disk with the X in it. Which means I
>need to configure My boot loader. I can't get into OF I get a
>black screen.
>
>I boot with the floppies and go to a shell I mount my root
>partion (/dev/sda3) to /target and run ybin -b /
>My very subjective impression is that compiling (kernels, or anything
>else, for that matter) _is_ slower on PPC than on i386. No hard figures
>here; but that has been my impression all the time during the 4 years
>I'm following PPC Linux.
>
>Reasons might be many and various: memory bandwidth bei
>
>okay, I now got your kernel tree (as well
>as the bitkeeper tree) booting, using quik.
>however, when putting the PB2400 to sleep
>(either by "snooze" or by closing the lid),
>it darkens the screen, but will *not* awake
>again. (and it doesn't blink at the lid shutter,
>when sleeping, as it does
>Last one I successfully got to boot was
>linux-2.4.0-test11 from paulus.
Well, that's fairly old. I'll see if I can figure out
what's wrong.
>btw, I got somewhat confused about the
>kernel image: Is it correct to always take
>the image to be found in the kernel-source-root
>(or would I have to
>
>DPMS stands for something like 'Display Power Management System'. With this
>option, the server tries to put the monitor to standby, suspend and
eventually
>power it down (which can damage monitors that don't support DPMS). I don't
>know if it makes any difference on a Pismo, anyway. :)
Well, i
>
>is the full path to your kernel really .../target/boot/... If you are
>booted into the installer, and your hd11 partition is mounted on target,
>then that's the path you'll see, but on hd11 itself, the path should be
>/boot/vmlinux-2.2.18pre21, shouldn't it? That's where the default kernel
>w
>on the subject of using the Fn key to access the fucntion keys, I notied one
>day when I first got my pismo that there was an opion in macos (I think I
>read it in the little book that came with the pismo) that there is a way to
>tell macos to reverse the function keys, so the F1-F12 work by defau
>Then I tried to compile kernel 2.4. I rsync'd with benh's tree at
>penguinppc.org like Jason told me to do. I also took his config, but made a
>few changes to it, i.e. filesystems. So they shoudn't really matter.
Now, the
>kernel compiled fine, but when it came to linking everything together, i
>On Friday 13 April 2001 16:14, Benjamin Herrenschmidt wrote:
>> Well, if you don't tell me which the errors are, I'll have difficulties
>> fixing them :)
>
>ok. Sorry. The linking fails with the following error message:
>
>arch/ppc/kernel/kernel.o: In fu
>
>
>Another snooze problem I had was this: (TiBook, btw)
>eth1: Error -19 transmitting packet
>hermes @ 0xd4a9d000: Card removed while waiting for command completion.
>
>I got hundreds of those in /var/log/syslog, and my system slowed to a
>crawl. I expect it's just something about pcmcia that I d
>
>OTOH the wireless plugin for gkrellm is showing quality around 200,
dunno what
>that number means...
>
Looks like the raw number as returned by the driver. Not too sure about
the meaning, I hacked my plugin to have a scale of 200 instead of 100 :)
Ben.
>So far, so good. Closing it makes it sleep. Now, here's my question: Is
there
>a way to make it
>a) wake up on a LAN connection and/or
>b) wake up at a certain time, thus still allow it to execute cron jobs for
>example?
I don't know if those are possible. Wake on Lan might be if the PHY is
pro
>I'm having trouble building the latest rsync of the benh kernel. First I
>got an undefined symbol "xmon_printf" trying to link kernel.o, so I ran
>menuconfig and added xmon into the kernel. Now I fail trying to build
>misc.o with
>
>/usr/src/linux-2.4/include/asm/cputable.h:45: `NR_CPUS' undecla
>
>hehehe, well what got me thinking, is mol runs with root privileges
>full time. and macos has no security whatsoever.. so does this mean
>that an errant MacOS app can screw with things on the linux side that
>would ordinarily be privileged? i would guess not, but its fun to
>think about.
>
>Maybe BenH would like some info on what you where typing when it happened
>:-)
Don't worry about this message, it's harmless (unless you get something
different than -1 or -2 as the value).
It's a kind of debug stuff I added to check that the CPU wouldn't miss
a DEC interrupt when put in NAP mod
>
>2.4 apparently has the patches merged into a config option.
>
>as for 2.2 mol DOES sucessfully patch the kernel, or so it says, its
>just that after forcing the mismatched modules in and attempting to
>run mol that it claims the kernel patches are too old, mismatched or
>something like that. s
>Thank you all for your help. Following michel's suggestion, I compiled
>benh's kernel and changed my append to "video=aty128fb:vmode:14,cmode:8".
>It work without problem after that. I tried taking out the append line,
>but it would just hang with the OF path to the video card on a white
>screen.
>Other point: performance. I am getting around 70 dropped frames out of
>each block of 200... Which makes DVD useable, but impossible to really
>_watch_ a movie. What are others getting? This is on a G4/400 TiBook.
>Has anybody made any atttempt at using Altivec to speed things up?
I'm pretty sure
>
>Another thing is that there is now infrastructure for motion compensation,
>apparently an Intel guy is working on a DRI based driver for that for the
>i810/5 chipset. Am I right to assume that the M3 has such capabilities and
>when used they would solve all our problems? :)
I think the ATI chip
>
>pci.c : In function 'pci_bus_to_phys'
>pci.c:936: 'dev' undeclared (first use in this function)
>[...]
>make[1]: *** [pci.o] Error 1
>[...]
Looks like you compiled with CONFIG_POWER4 which is definitely
wrong for 32 bits machines. Make sure you selected the 6xx/7xx
CPU in the config.
Ben.
Note that if you don't want to mess with XFree, I recently added the
ability to control the CRT & LCD outputs of the Rage M3 to aty128fb in my
rsync tree. The tool to control it is on www.penguinppc.org/~benh
Ben.
>> Note that if you don't want to mess with XFree, I recently added the
>> ability to control the CRT & LCD outputs of the Rage M3 to aty128fb in my
>> rsync tree. The tool to control it is on www.penguinppc.org/~benh
>
>BTW, the recently released ibook is said to only have the capacity to mirror,
>
>So mirroring will work, i guess.
Well, it works fine on the Pismo, but the composite output may need
additional configuration of the composite encoder.
>for dual head you will need X, isn't it, fbdev seems broken (well at least
>those using fbgen) for dualhead anyway. Don't know if aty128fb us
>
>
>If you point the second CRTC to the same frame buffer region, you'll have
>mirrorring, else you have two different heads.
In most cases (like what I do with aty128fb), you don't even need to use the
second CRTC. Just enable both outputs and let them source from the first CRTC.
>> So i suppos
>> Yep. The same is true for atyfb (yes, I should add mirrorring/dualhead
>support
>> for the Mobility in my Vaio :-).
>
>Please do - I tried Ben's mirror utility on the Lombard but no success.
>And I still have no aty docs to look up the details in.
Well, if you do that, it may be interesting to
>i am not sure if its the disk based MacOS that trashes nvram or the
>ROM based MacOS that does. if its ROM based then the MacOS version is
>irrelevent, if the ROM is ever run, regardless of whether it even
>finds a copy of macos on any disk, the nvram will be reset.
>
>someone was saying on irc
>> We need a way to use multiple ioBases from inside xfree to fix the problem.
>> The best solution will be to disable ISA I/O for now and get a better fix
>> later on.
>
>No, that's not the solution. The solution is to get the kernel to return
>the *correct* iobase for the sepecific devfn, right
>
>That's the problem, it doesn't work on AGP. outb works but inb segfaults.
>
>The syscall should only return an iobase for known working busses IMHO.
At the
>very least, it shouldn't return any for busses known not to work.
>
That's the case. I mean it should know all busses and does support all
>I had tried your guide too, Ethan, but it didnt work the same way Ron
>describes it here (on a TiBook).
>
>I had first tried with a pure bootp server, since OF should fall back to
>using bootp if DHCP didn't work. No dice...
>
>I then tried with a dhcp server, for which I got the same log entries
>G4/450MP w/SAGEM ISDN PCI card
>
>does this card (Unknown device 5049) require a special driver to go
>online or no?
I'd suggest looking at the various ISDN pci drivers in the kernel,
I _think_ one of them was adapted to handle at least some models
of SAGEM cards.
Ben.
>This is all still a bit rough, I am looking for comments and
>suggestions on how to proceed. I want this transition to occur for
>woody so it needs to start ASAP.
Additional maps are needed as, even with linux keycodes, PC keymaps
won't be ok for a lot of international Mac keyboards. Apple ten
>Is anyone else out there using a recentish benh 2.4.6 kernel with a
>TiBook? 2.4.4 from a while ago worked fine for me for pretty much
>everything, but 2.4.6 kills the machine when I close the lid.
>
>I would just stick with 2.4.4, except that it locks the machine when I
>try to build the Debian
>> Does anyone have experience with this?
>>
>> I plan to usa an external FireWire disk w. my G4 at home, as well as
>> in a studio.
>
>Won't currently work (with Linux). Firewire support on PPC is a pretty
>recent addition, and won't work with Apple hardware yet (or so Ethan
>claims).
It works, a
>Thanks for correcting me. I shouldn't take Ethan's word on kernel support
>:-)
>
>Regarding APM emulation: does that make apmd work on Powermacs, or will
>pmud still be necessary?
APM emulation is not a replacement for pmud. It doesn't emulate all APM
messages in /dev/apm_bios, only the strict m
>I finally got 2.4.6-pre8 from penguinppc.org (or wherever it is they
tell you
>rsync from) to work on my machine. Funny thing, though, is that the console
>is bright ugly green, until I get into X. So when I'm booting, it is green,
>with other neon colors in the console that make it impossible
>
>AFAIK the airport unload hack is no longer required with 2.4 kernels
>(what's with 2.2.19?). If Ben says 2.4 sleep support on Core99 is stable,
>I'll just have to check the kernel version number and either shutdown or
>sleep. If someone backports the Core99 sleep code to 2.2, the better.
2.2.19
>
>> and it implements /proc/apm for battery infos, but the infos there are
>
>That part was actually fairly easy IIRC (did that for 2.2.19).
Well, the 2400/3400/3500 is not so easy, especially without the
floats in kernel ;) I'd be glad to have some testers with these
machines to tell me if /proc
>
>I just finished to rsync and compile benh kernel for my pismo(thank's
>ben for your work) and I notice a problem wille using gpm, with my usb
>external 3
>buttons mouse
>as I spend a lot of time in console mode, I eavily use gpm.
>with 2.2.19 everything is OK
>with benh kernel, when I mouse sele
>MOL rsync? Do share ...
rsync:
rsync -vcaz zorn.theophys.kth.se::mol mol-rsync
BitKeeper:
bk clone bk://zorn.theophys.kth.se:5000 mol-bk
>
>To make the behaviour consistent? The default for PMU_VERSION_KEYLARGO
>is SIGPWR, for everything else is snooze.
>
>The justification for this as given by the comments in the code is
>incidentally somewhat different to the behaviour it produces.
>
>/* HACK: shut the machine down when lid i
>
>I have my Microsoft USB optical mouse plugged in, and I do have the
>Airport card installed now, but I don't have the Airport driver module
>running.
Did you try without the USB mouse ? And also without compiling the
USB OHCI driver in the kernel at all ?
If I understand you properly, it hangs
>On Wed, Jun 13, 2001 at 12:46:52PM +1000, [EMAIL PROTECTED] wrote:
>>
>> It has always been a problem, memset(,0,) should take into
consideration the
>> cacheline size but does not.
>>
>> > If this is the only difference between powerpc and power3, then the
>> > only choice I have is to remove
>> This should be fixed in pmud. The PMU driver now supports an ioctl telling
>> you if sleep is supported or not on the machine. If the ioctl is
>> not implemented, you get an error and can revert to the old mecanism.
#define PMU_IOC_CAN_SLEEP _IOR('B',5,sizeof(__u32 *))
The param points to
>
>close lid within console - TiPB goes to sleep and LED is off - TiPB only
>comes back with hard-reset (ctrl-apple-power)
>
>with the 2.4.6 kernel (without thermal management) it is the same like
>with 2.4.4 and closing the lid within console. It doesn´t matter if i´m
>in console or X the TiPB nev
>
>giveup_altivec:
> mfpvr r24 /* check if we are on a G4 */
> srwir24,r24,16
> cmpwi r24,[EMAIL PROTECTED]
> beq 3f /* continue */
> mflrr24
> bl msr_vec_debug /* debug thingy in process.c *
>failing again (as it does even with older kernels). X11 sleep still
>works. It seems like the problem is in aty128_sleep_notifier because
>this debug code you suggested:
>
>> - edit drivers/video/aty128fb.c, comment out the call to
>> pmu_register_sleep_notifier() line 1907, and add
>> a "re
>
>I installed successfully Debian sid on my new iBook. Everything works. X11
>was a little hassle but works accelerated, pmu works (only have to switch
>to some tty before going to sleep, otherwise my X screen is garbage).
>Sound doesn't work. (I expected this.. ;)
X will work provided that you
>> Disabling altivec seemed to fix the problem sleeping. It went to
>> sleep and woke up 7 or 8 times with no problems aside from
>> temporarily scrambling the console a bit.
>
>Yep, disabling altivec worked for me too.
Could one of you quickly test if the problem still happen with
my current rsyn
>> The param points to an u32 that will be set to 0 or 1 (or the ioctl
>> will return an error if not implemented).
>
>Thanks. BTW /proc/apm is broken on my Lombard (returns -1 for both
>timeleft and percentage), I'll look into that soonish.
That's weird. Make sure you get the latest tree. Also, d
>> So your best chance would be to reverse engineer either the macos or
>windows driver, and try to get something out of it.
>
>Set your email client to wrap lines, would ya'? And don't be daft.
>Nvidia just released their latest driver for X4 for x86 linux that
>supports not only their new GeFor
>Sorry for the non-technical description, but has anyone else
>noticed this?
It's a side effect of my tentative to save more power by shutting
down the DAC and LVDS transmittr. I'm trying to trace the MacOS
driver to figure out what it actually does.
Did you notice a loss in battery life
>Okay, the power consumption during sleep has improved.
>Without the latest changes, sleeping for 12 hours used up about 42% of
>the battery. With your latest kernel, it used up about 25%. (I
>haven't measured it on MacOS yet.) Is that about what you would
>expect?
What would be interes
>
>cdrecord -v -dummy fs=10 driveropts=burnproof speed=16 dev=1,0,0
>/tmp/foo.iso
>
>then process finishes with message about correct fifo-size.
>
>If I do the same without the -dummy option my box locks.
Some of the people hacking around linux-1394-devel have experienced
similar lockups when I t
>
>There are a few too many patches floating around (see the 1394 list
>archives for all the stuff Dan Berlin, Ira Weiny, Ben H, and Ben C
>have posted).
>
>It has to do with very low level endianness issues in the OHCI
>protocol, and how apple build's it's 1394 hardware. All my firewire
>hardware
>I should be more precise:
>
>m3mirror crt:0
>
>shuts off only the crt (in both X and console)
>
>m3mirror lcd:0
>
>shuts off *both* the lcd and the crt (in both X and console)
In drivers/video/aty128fb.c, find
#define BACKLIGHT_DAC_OFF
and change it to
#undef BACKLIGHT_DAC_OFF
The fix is alre
>Shure but does endianess explain that cdrecord works with option
>-dummy enabled and kernel-lock happens when disabling the option (see
>my follow-up mail). If this simulation with -dummy does everything
>except turning on the laser-beam in the CDRW? (see man cdrecord).
>
>Cheers
I think it can l
>This doesn't work currently:
> - AirPort and gmac wakeup (doesn't crash at sleep, but need to poke
>around at wakeup to reinit network)
This should work properly with my recent trees. It works at least
on my Pismo which has a very similar chipset to the TiPbook
> - Sleep from the console
That s
>
>For those of you using the newest benh kernels with PMAC_APM_EMU, here's
>my experience:
>
>PMAC_APM_EMU does _not_ mean that you should use the apmd package (i386
>power management daemon). What it does is translate the status messages
>from pmud (Powerpc power management daemon) so that the Gn
>The kernel pukes on the terminal - nothing alarming, except the following
>right before falling asleep (or so I believe, it is just below AirPort
>going to sleep):
>
>ALSA pmac.c:892: error 2
>
That should be harmless.
Ben.
I've uploaded yaboot 1.2.3 to http://www.penguinppc.org/~benh.
This is a critical update. I found a nasty bug in all previous
versions that could cause some issues with the kernel memory mappings.
Newer kernels (including my rsync) are likely to be more affected,
but the problem is potentially he
>Whoops, should have said:
>
>Is this also likely to affect 2.4 kernels on oldworld Macs using BootX?
No. BootX is not affected, nor miBoot, nor quik.
Ben.
1 - 100 of 2143 matches
Mail list logo
