Re: connecting projector to titanium laptop

[Julien BLACHE]

Richard Otte <[EMAIL PROTECTED]> wrote:

Hi,

> I use Debian on my normal pc, but for work I will soon need to give
> presentations using a mac titanium laptop, connected to various

If it's a G4 Ti with a Rage128 card, you need m3mirror and a kernel
patch (if you're running a 2.6 kernel).

Google for m3mirror.c and look in the debian-powerpc archives for the
kernel patch I posted.

There is no other way that I know of to get the external monitor
output to work on Linux on these machines.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: connecting projector to titanium laptop

[Julien BLACHE]

Vincent Lefevre <[EMAIL PROTECTED]> wrote:

Hi,

> Anyone knows when the official kernels will be patched?
> This is rather annoying, it was working in the past.

It won't be. The current kernel behaviour is actually appropriate, and
you must remember that m3mirror is just a hack over the previous
behaviour.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: connecting projector to titanium laptop

[Julien BLACHE]

Ric Otte <[EMAIL PROTECTED]> wrote:

Hi,

> I think the video card is a ATI Radeon Mobility 9000.  Does that make
> a difference in using m3mirror.c?

Yes, in this case you need a multihead X config, not m3mirror.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Debian has failed us

[Julien BLACHE]

Mathew Binkley <[EMAIL PROTECTED]> wrote:

> Thus I am including the people who have a chance to change that.  Debian
> may never die as a distribution, but it's heading down the road towards
> losing it's relevance because of issues like this, and that's sad.

You are over-exagerating this issue quite a bit.

Frans will eventually go away just like others did in the past, and
Debian will just move on. In fact, Debian has moved on already.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Debian has failed us

[Julien BLACHE]

Ralf Saalmüller <[EMAIL PROTECTED]> wrote:

> It's high time to get a little bit more professional.

You're taking the fun out of it, you know ?

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: PowerBook disk drive

[Julien BLACHE]

"Andrew J. Barr" <[EMAIL PROTECTED]> wrote:

Hi,

> Can someone tell me why Apple computer hard drives, at least in laptops,
> are very slow? E.g. is the drive or the controller? Responsiveness in my
> Powerbook still seems rather bad, and from what I can tell it seems to

Years ago I upgraded my PB G4 500 hard drive from the original 5400
RPM 30 GB disk to a 7200 RPM 60 GB disk, both IBM drives. The new disk
had a lower latency and higher throughput (comparing both datasheets
-- and same power consumption too).

The machine instantly felt 2 times faster with the new disk.

And now I'm just considering doing something alike with my MacBook
Pro, because the disk is just so slow. Apple have a really hard time
properly balancing the performance in their machines.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: CONFIG_LEGACY_PTYS is not set on PowerPC

[Julien BLACHE]

Vincent Lefevre <[EMAIL PROTECTED]> wrote:

Hi,

> OK. But CONFIG_LEGACY_PTYS was defined in official Debian x86
> kernels, so that most maintainers probably could not see the
> problems, and it could take months/years to get them fixed.

Err, switching for BSD PTYs to POSIX PTYs is not hard at all, so if
packages "take years" to get fixed it's either because they're
unmaintained or nobody cares about them. In both cases they should be
removed from the distribution.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Please unban S. Luther from debian-powerpc@lists.debian.org

[Julien BLACHE]

Mike Hore <[EMAIL PROTECTED]> wrote:

> Yes -- I've only been reading the list for 6 months or so and to me
> this action looks quite arbitrary and extreme -- IMHO of course --
> some background would be very welcome.  List regulars say things like
> "we all know" and "it's obvious" -- but to me at least it isn't.

Read the archives for debian-project, debian-vote and debian-devel for
the past 18 months. Then it'll be obvious for you too.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Do nvidia based ibooks/powerbooks support backlight adjustment via sysfs?

[Julien BLACHE]

Sjoerd Simons <[EMAIL PROTECTED]> wrote:

Hi,

>   For hal we want to deprecate using the PMU for brighness control if 
> possible.
>   With recent kernels it seems both Nvidia and Radeon have backlight support
>   now. On my powerbook G4 with a radeon this works fine.

Yes it works, that's what pommed uses on these machines.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Pommed ignores fnmode option in the conf file

[Julien BLACHE]

Francesco Pedrini <[EMAIL PROTECTED]> wrote:

Hi,

> i'm having some problems with pommed on an ibook g4 2005,
> it seems that he can't use the fn+functionkey working right.

Hmmm, if this machine still has an ADB keyboard (vs. USB), then you
cannot change the Fn behaviour. It's only possible on USB keyboards.

Check your logs or stop pommed and run pommed -f and you should see an
error message.

> Also, and that is really strange, the key are fully functional (with the 
> wrong behaviour) even when pommed is stopped, this leads me to think 
> that it's not only a bug of pommed, i think that there are other parts 
> of the system that are involved in this stuff.

If only the backlight keys work, then they're handled by the kernel on
its own. If other keys work too, then something else is running,
either pbbuttonsd or some GNOME stuff via HAL.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Pommed ignores fnmode option in the conf file

[Julien BLACHE]

Francesco Pedrini <[EMAIL PROTECTED]> wrote:

Hi,

> Ok, i've an ADB keboard... but i don't get any error from pommed (except 
> the stuff about LMU, but is it related only to the cdrom, right?), the 
> full log is attached.

The LMU error is expected on this machine and harmless. It's related
to the keyboard backlight (which you don't have).

Also there's no error message because the USB HID module is loaded on
your machine, so the path exists. I used to run a kernel with ADB only
on my PowerBook :-)

> There is anything that i can try without switching back to pbbuttonsd?
> Some sort of experimental patch or things like that, it should not be 
> impossible since pbbuttonsd does that... i'll offer cputime and 
> tests :D

Indeed I've overlooked a chunk of code in pbbuttonsd at the time the
pmac support was added to pommed :)

I'll prepare a patch and I'll send it to you for testing. Should be
tomorrow or sometime this week.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Suggestions for running Mac OS 9.0.1 on debian-x86-64

[Julien BLACHE]

Christian Jaeger <[EMAIL PROTECTED]> wrote:

> What are you using for running Mac OS 9 (*) on a x86-64 machine? It
> seems there are only two ways:
> (a) running a ppc linux kernel with MOL under QEMU, run Mac OS inside MOL.
> (b) running SheepShaver

(c) PearPC

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Suggestions for running Mac OS 9.0.1 on debian-x86-64

[Julien BLACHE]

Christian Jaeger <[EMAIL PROTECTED]> wrote:

>> (c) PearPC
> http://pearpc.sourceforge.net/faq.html says "Can I run Mac OS 9.x.y? 
> So far no one has succeeded in doing that. Have a look at the forums." 
> and I didn't find something relevant in the forums when I looked.

Hmm I'm pretty sure I saw a couple of OS 9 screenshots within PearPC,
and it wasn't Classic mode. Oh well.

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Apple bluetooth aluminum keyboard working?

[Julien BLACHE]

"Antonio-M. Corbi Bellot"  wrote:

Hi,

> I've been trying to configure an Apple bluetooth aluminum keyboard
> under Debian with latest 2.6.26 stock kernel.
>
> So far the keyboard gets paired and works ok except for the 'fn' key
> and the keys tha it helps to emulate (PgUp. PgDwn, multimedia keys,
> etc...).
>
> Has anyone managed to get it fully working?

You need a newer kernel, or a fix to your current one wrt the HID
quirks for this keyboard. If memory serves me well, 2.6.27 is OK.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer -  
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Apple bluetooth aluminum keyboard working?

[Julien BLACHE]

"Antonio-M. Corbi Bellot"  wrote:

Hi,

> Just tried 2.6.27-1~experimental.1~snapshot.12506 from
> kernel-archive.buildserver.net/debian-kernel and I get the _same_
> results as with 2.6.26, that is, the 'fn'-key does not work.
>
> Any ideas to try now?

Actually, you want a 2.6.28-rc. The latest one should work, otherwise
you'll need to grab the git tree.

JB.

-- 
 Julien BLACHE   |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Apple bluetooth aluminum keyboard working?

[Julien BLACHE]

Elimar Riesebieter  wrote:

> In newer kernels we have
> /sys/module/hid_apple/parameters/fnmode

That's only in 2.6.28 with the rework of the HID quirks.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer -  
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Kooka Broken in Lenny?

[Julien BLACHE]

Irena & Richard Jenkins  wrote:

Hi,

> Is it a permissions problem?  That was a suggestion from xsane ... and 
> puppylinux runs as 'root' so avoiding all these issues.  Of course I would 
> never recommend running as 'root' ... 

Add your user to the scanner group, log out and log in again, and
it'll work.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer -  
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: hwclock: NVRAM flat battery sets date to 1904

[Julien BLACHE]

Mark Purcell  wrote:

Hi,

> +if `/sbin/hwclock | /bin/grep -q 1904`; then

It's not necessarily 1904. Can be 1903 or 1933 too.

You're better off checking the year isn't < 2000, for instance.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer -  
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: udev 146-5 and ppc64 kernel

[Julien BLACHE]

Stephane Louise  wrote:

Hi,

> marie:/home/luigi# grep -i inotify /boot/config-2.6.30-2-powerpc64
> CONFIG_INOTIFY=y
> CONFIG_INOTIFY_USER=y
> marie:/home/luigi# grep -i signalfd /boot/config-2.6.30-2-powerpc64
> CONFIG_SIGNALFD=y

udev's preinst checks for those features by looking for
sys_inotify_init and sys_signalfd in /proc/kallsyms.

Look at the preinst script and check your system; you should find
pretty quickly what's wrong with your system/config or udev.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer -  
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: udev 146-5 and ppc64 kernel

[Julien BLACHE]

Paul Mackerras  wrote:

Hi,

>> udev's preinst checks for those features by looking for
>> sys_inotify_init and sys_signalfd in /proc/kallsyms.

> The symbols in /proc/kallsyms are .sys_inotify_init and .sys_signalfd,
> not sys_inotify_init and sys_signalfd, so the preinst script thinks
> they're not there.  I kludged around it by doing "sudo touch

That's what I had in mind, thanks for the confirmation. Too bad my PB
G4 is kind of dead (of old age) now :(

JB.

-- 
 Julien BLACHE   |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

2.4.22-ben2 : backlight (F1/F2) not working on console, little freeze

[Julien BLACHE]

Hi,

Running 2.4.22-ben2 for a few days now, I just realized the backlight
keys (F1/F2) do not work on console anymore. Is that known/intended ?

I'm also having a little freeze (up to 2s) while launching XEmacs,
which is something I never experienced on Linux :( and I've got plenty
of RAM...

The machine is a PB G4 500 MHz (PowerBook3,2 71).

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: 2.4.22-ben2 : backlight (F1/F2) not working on console, little freeze

[Julien BLACHE]

Stewart Smith <[EMAIL PROTECTED]> wrote:

> i haven't actually tried it, and i don't see why it would make the
> buttons work (maybe it will, the place i was at while researching this
> issue stopped serving coffee at about that time) but it should at least
> stop the error message coming up - which is an improvement for me at
> least :)

Correcting my initial posting : the keys actually work.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

m3mirror broken in 2.4.22-ben2 ?

[Julien BLACHE]

Hi,

Is there any know problem with m3mirror and 2.4.22-ben2 ? All I'm
getting on the VGA output at the moment is garbage :(

It works fine with 2.4.20-benh, any idea ?

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: How to get infrared and/or Nokia working

[Julien BLACHE]

Christian Jaeger <[EMAIL PROTECTED]> wrote:

Hi,

> I'd like to connect to my new mobile, a nokia 6100.
>
> Running 2.4.22-ben1 (august 31), debian unstable (in a chroot so I can
> keep my woody installation), on a powerbook g3 lombard.

[...]

> a) anyone succeeded in using a mobile with a mac?

I've got my 8210 working with my PB G4 500. As it turns out, the 8210
couldn't keep up with an irda port at 115200 bauds, so after a _lot_
of googling I found that doing

echo "57600" > /proc/sys/net/irda/max_baud_rate

was enough to get everything working. After that the 8210 appeared in
the irdadump logs, which it didn't previously.

I've successfully established a PPP connection over the irda link,
with an average ping of about 6 seconds %-)

> b) anyone succeeded in using gnokii with a mac?

Yes, works fine. At least last I tried, which was some months ago with
a 2.4.20-benh kernel.

But you shouldn't use /dev/ttyS1. You should load the ircomm module
and use /dev/ircomm0.

> c) what to do against the kernel bug?

What kernel bug ?

> d) what are all those other infrared kernel modules for. Any use for
> my purpose?

The irda port on the mac can be used as a SIR device (what you're
currently doing), I think it could be used as a FIR device too but
there is currently no driver for that (assuming it's possible at all,
which I'm not sure).

I haven't used this irda setup for a while, but I have some time this
week to play with it if you need some more help. Google is your
friend, you can also find some help on mobilix.org^Wtuxmobil.org
(although the docs often cover FIR devices, there are some bits of
information on SIR devices).

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: How to get infrared and/or Nokia working

[Julien BLACHE]

Christian Jaeger <[EMAIL PROTECTED]> wrote:

>>echo "57600" > /proc/sys/net/irda/max_baud_rate
>>
>>was enough to get everything working. After that the 8210 appeared in
>>the irdadump logs, which it didn't previously.
>
> (What do I need in order to make irdadump output anything? load which
> modules etc?. I haven't got any output so far.)

irattach must be running ; it's automatically started if you have
irda-common installed. Check that it's running, and you should at
least see the computer sending discovery messages (you must of course
run irdadump as root) :

11:30:12.270024 xid:cmd 83d208ff >  S=6 s=0 (14) 
11:30:12.360009 xid:cmd 83d208ff >  S=6 s=1 (14) 
11:30:12.450007 xid:cmd 83d208ff >  S=6 s=2 (14) 
11:30:12.540008 xid:cmd 83d208ff >  S=6 s=3 (14) 
11:30:12.630007 xid:cmd 83d208ff >  S=6 s=4 (14) 
11:30:12.720006 xid:cmd 83d208ff >  S=6 s=5 (14) 
11:30:12.810009 xid:cmd 83d208ff >  S=6 s=* frigate hint=0400 [ 
Computer ] (23) 

With my 8210 in sight :

11:35:48.810013 xid:cmd 2b6438b6 >  S=6 s=* frigate hint=0400 [ 
Computer ] (23) 
11:35:51.270028 xid:cmd 2b6438b6 >  S=6 s=0 (14) 
11:35:51.360016 xid:cmd 2b6438b6 >  S=6 s=1 (14) 
11:35:51.360005 xid:rsp 2b6438b6 < 3607 S=6 s=0 Nokia 8210 hint=b125 [ PnP 
Modem Fax Telephony IrCOMM IrOBEX ] (27) 

It may be necessary to set the max_baud_rate to 115200 to get that,
but you'll have to set it to 57600 once you'll want to use gnokii.

gnokii --identify is a good test tool.

That's with 2.4.22-ben2, so it works at least on my PB :-)

>>I've successfully established a PPP connection over the irda link,
>>with an average ping of about 6 seconds %-)
>
> (Are non-GPRS connections (forgot the name, those connection oriented
> ones) better?)

That wasn't GPRS, but using the built-in modem of the 8210 via
/dev/ircomm0. Plain old GSM I guess :)

>>But you shouldn't use /dev/ttyS1. You should load the ircomm module
>>and use /dev/ircomm0.
>
> How to use ircomm? Can I use minicom on it?

Yes. It works just like a serial port.

>>  > c) what to do against the kernel bug?
>>
>>What kernel bug ?
>
> The one that crashes the machine. (fiddling with ttyS1 shouldn't do
> that, right?) Ok maybe if I do everything as I should and hold my
> breath, it won't happen anymore.

Probably. Once irtty is loaded, you shouldn't touch /dev/ttyS1
anymore, I think.

> Is it correct that ircomm is a layer above one of SIR|FIR|..?

Yes. IrComm is one of the protocols that can be used over an IrDA
link. See the irdadump log, each device advertises the protocols it
supports (inside the brackets).

> So should I first get SIR working? Using minicom for debugging?

Loading the irda, irtty, ircomm (and ircomm-tty, but this one is
loaded automatically I believe) modules and echoing to
/proc/.../max_baud_rate should basically get you started, I think.

Check that irattach is running and run irdadump ; you must see the
computer sending discovery messages.

Beware, the irda stack doesn't like when you put the machine into
sleep ; you'll need to restart irattach (/etc/init.d/irda restart
does the trick).

> More questions:
> - where does the infrared beam leave the mobile? From what I read in
> the nokia docs, it's a laser diode, not an led. So maybe it's not
> hidden behind a black (IR-permeable) plastic window, but instead,
> probably, in a slit on the right side, about where usually your thumb
> is when holding the mobile to the ear.

I have no idea. On my 8210 there is a window on the side, so it's
pretty obvious.

> - is there maybe any real lowlevel access to the infrared port, so I
> can see if light is physically entering the laptop ir port even if
> drivers are not working?

Not that I know of.

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: How to get infrared and/or Nokia working

[Julien BLACHE]

Christian Jaeger <[EMAIL PROTECTED]> wrote:

Hi Christian,

> Thanks again for your help. But I still haven't succeeded. (Linux
> seems to confirm an old prejudice that it's immature and difficult to
> use.)

IrDA isn't something easy to set up. It took me some months to finally
get it working.

>>irattach must be running ; it's automatically started if you have
>>irda-common installed.
>
> Thanks. I wasn't even aware that I need this package.

There are others, apt-cache search irda will give you a list. Not all
are needed, though.

> I've configured irda-common to
> - serial port (vs. native)
> - driver: none (since none matched what I found in the kernel config)
> - device: /dev/ircomm0

Here's what I answered when installing irda-common :

% debconf-show irda-common
* irda-common/ttydev: /dev/ttyS1
* irda-common/aboutdoc: 
* irda-common/enable: true
* irda-common/changes: 
  irda-common/mkirdev: 
* irda-common/discovery: true
* irda-common/regen: false
* irda-common/dongle: none
* irda-common/firdev: smc-ircc
* irda-common/firopt: 
* irda-common/selectdevice: serial

The device (ttydev) to use is the _serial_ device on which the IrDA
port is attached, so that would be /dev/ttyS1 and not /dev/ircomm0
(that you should use when you want to reach a device over the IrDA
link).

Run "dpkg-reconfigure irda-common" to change the configuration of
irda-common, then restart the irda service.

> It starts irattach, and a running irdadump outputs exactly *one* of

Use ps to see what options where passed to irattach. You should find
the serial device (/dev/ttyS1) and the discovery option (-s).

> the above lines. /etc/init.d/irda restarts a new instance of
> irattach. /etc/init.d/irda stop does not terminate them. kill does

Yes, I've had this problem, however, I no longer experience that with
2.4.22-ben2 and an up-to-date unstable system (dunno which of the
kernel or userspace tools changed, but that doesn't happen anymore).

> neither. kill -9 finally does. /etc/init.d/irda start does make
> irdadump issue one line again.

I think this is because of the wrong device setting.

> I've rebooted my laptop and tried again (without any sleep cycle
> inbetween), no joy.

Hope you'll have more luck this time...

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: VGA-out not working any longer on old TiBook 400

[Julien BLACHE]

Percy Zahl <[EMAIL PROTECTED]> wrote:

Hi,

> I've a bunch of questions about the m3mirror/vga-out and XFree with the
> current ppc-kernel on an old TiBook 400:
>
> Since a kernel update from 2.4.19 to 2.4.20 and now to 2.4.23 I cannot
> use the VGA output any longer, I can switch it on/off (using m3mirror),
> but the signal produces a funny colorfull but almost random pixelized
> CRT  image, the LCD image is uneffected and OK. 

According to what BenH told me :

This is due to a change in prom_init.c ; now OF is asked to open all
displays.

Backing out the change should be enough (haven't tried yet), otherwise
you can revert to 2.4.20 for your presentations (what I'm doing atm),
or fix aty128fb.c (or XFree) to implement a real dual-head
support... The radeonfb code should help in this area.


It's not a good feeling to be left alone sitting in a corner with our
old PowerBooks... but hey, at least we've got an ATI chip. :)

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: How to get infrared and/or Nokia working

[Julien BLACHE]

 your 6100
will work with gnokii by using model = AT, just as my 8210 does. [in
fact I'm pretty sure it'll work, as it advertises the same
capabilities as my 8210 does]

Here's the content of my /etc/irda.conf, in case you'd like to compare
with yours :

#irda.conf Version: 1.0
IRDADEV=/dev/ttyS1
#DONGLE= # specify dongle type
DISCOVERY=-s
ENABLE=yes # if you do not need to start irattach, set "no"

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: How to get infrared and/or Nokia working

[Julien BLACHE]

Christian Jaeger <[EMAIL PROTECTED]> wrote:

> Wohoo, it works (sort of), with your configuration!

Great !

> I can fetch the address list - but some numbers are just empty strings
> :(. This happens with both xgnokii and gnokii --getphonebook ME 1 20
> [ -r ]. It happens for some phone numbers in RAM, not for those in SIM
> but there are only ~4 of them in SIM so that may be luck. It looks
> like it happens for those nicknames longer than 15 chars. (+1 nullbyte
> gives 16 bytes). (Firmware bug or protocol/gnokii issue? I guess I'll
> have to subscribe to the gnokii mailing list if there is any.)

There's a mailing list on sourceforge, it was quite active last I
checked :) I hope you'll get proper support for your phone...

> (And yes, it only works at all if I echo 57600 into the kernel baud
> rate limiter. 115200 does seem to work for discovery,  but not for
> gnokii. And the 57600 setting in .gnokiirc alone does not help either,
> hmm.)

Indeed. I spent a whole week-end tracking down this missing bit...

[GPRS]
> 9 packets transmitted, 8 packets received, 11% packet loss
> round-trip min/avg/max = 950.6/1180.8/1440.7 ms

Not so bad at all :)

> So, apart from a little bit of disappointment about not (yet) being
> able to sync address/calendar data, I've reached my goal.

Glad to read that :-)

> Thanks Julien (and thanks to all involved programmers listening)

You're welcome ! Have fun :)

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Orinoco/hermes (original Airport) WPA support status

[Julien BLACHE]

Hi,

What's the status of WPA support in the orinoco driver ? Back in July,
it wasn't supported, IIRC. Has anything happened since then ? Any
plans ?

Is the Agere driver usable either directly or after merging the
relevant parts into the orinoco driver ?

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Orinoco/hermes (original Airport) WPA support status

[Julien BLACHE]

Soeren Sonnenburg <[EMAIL PROTECTED]> wrote:

> Wait, as kernel 2.6.14 has these config options now
>
> CONFIG_IEEE80211
> CONFIG_IEEE80211_CRYPT_WEP
> CONFIG_IEEE80211_CRYPT_CCMP
> CONFIG_IEEE80211_CRYPT_TKIP
>
> and if the orinoco driver supported (or even already supports thsi
> framework ?!) it would work as this is done in software IIUC or is this
> a hardware limitation ?

Indeed, it can be done in software using the ieee80211 framework.

But this requires some work on the driver to adapt it. It's on my todo
list, with a gazillion other things ...

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Sudden Power Loss (Resolution?)

[Julien BLACHE]

Michel Dänzer <[EMAIL PROTECTED]> wrote:

Hi,

> FWIW, I used to have regular sudden shutdowns a couple of months ago.

As a data point, I'm seeing that too on a rev1 Ti (G4 500), but it
might be a slightly different issue.

It happened today for the second time in a couple of months, the
machine just shut itself down right after I woke it up from sleep (the
wake up procedure didn't complete).

Kernel is a vanilla 2.6.11, no ntp daemon running, I use pmud, no
cpufreq daemon running (but cpufreq support is in the kernel, although
I never use it), the battery is a brand new one and it was on AC power.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

HOWTO: m3mirror & recent 2.6 kernels

[Julien BLACHE]

Hi,

For those of you still relying on m3mirror for slideshows, here's
how to make it work with a modern 2.6 kernel.

Edit arch/powerpc/kernel/prom_init.c, then, in prom_check_displays()
add a break; statement at the very end of the for() loop.

As usual, the idea is that only the first display must be opened by
the prom, otherwise m3mirror doesn't work.

HTH,

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: HOWTO: m3mirror & recent 2.6 kernels

[Julien BLACHE]

Peter Plessas <[EMAIL PROTECTED]> wrote:

Hi,

>> Edit arch/powerpc/kernel/prom_init.c, then, in prom_check_displays()
>
> isn't it:
> prom_num_displays()
> in:
> /usr/src/linux/arch/ppc/syslib/prom_init.c?

No, arch/ppc is deprecated for most modern, non-embedded PPC machines
(and for some/most of embedded ones too).

>> add a break; statement at the very end of the for() loop.
>
> So this snippet:
>
> for (i = 0; i < prom_num_displays; ++i)
> prom_display_paths[i] = PTRUNRELOC(prom_display_paths[i]);
>
> would become:
>
> for (i = 0; i < prom_num_displays; ++i)
> prom_display_paths[i] =
> PTRUNRELOC(prom_display_paths[i])break;
>
> right?

Absolutely not :) This looks like it is the old code from arch/ppc,
right ?

If you don't have arch/powerpc, then replace prom_num_displays by 1 in
the above.

> This is on a debian 2.6.14 kernel, sources from kernel.org.

Never built this version of the kernel, I waited a bit for the dust to
settle around the ppc -> powerpc move :)

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: woody installation confusion

[Julien BLACHE]

Andreas Wüst <[EMAIL PROTECTED]> wrote:

Hi,

> After reading this one can say that it is, at the moment, impossible to
> install woody on a ppc machine?

I did it on a Tibook 2 days ago, and my Debian runs just fine at the
moment (I made a bootable CD 1 of Woody using my local mirror --
boot-floppies 3.0.13). *But* the boot-floppies are quite broken :

 - it will hang up if you configure your keyboard, leave it as it is
for the installation, then reconfigure it later (could be my fault --
bad choice ?) ;
 - the installer mounts ext2 partitions with type usbdevfs, you'll
have to remount them manually before continuing ;
 - it refuses to activate a swap partition, but this one could be my
fault (bad type on this very partition ?) ;
 - there are a bunch of warnings printed out each time you do
something, but it seems to be harmless ;
 - you'll have to write a yaboot.conf by hand, then run mkofboot and
ybin (chroot to /target, then mount /proc, run mkofboot and ybin).

After that, it's like any other Debian installation, it runs just fine
once rebooted.

So, uhm, actually for a clueless user it's impossible. I'm going to
file some bugs on the boot-floppies package.

This list was of a great help while installing/configuring the Tibook,
thanks to all the contributors.

 -- JB.

Re: yaboot killed after MacOS X update

[Julien BLACHE]

Carsten Friede <[EMAIL PROTECTED]> wrote:

> I recently updated my MacOS X to 10.3.8 and after that my boot manager
> was lost! There was no boot menu anymore, nothing but starting MacOS
> by default. How can I install yaboot again, without a complete
> reinstallation of my whole system?

If your bootstrap partition was remapped, boot on a debian-installer
CD, grab a shell, run mac-fdisk and remap it back to its proper
location.

Mac OS X can't deal with remapped partitions. If this isn't the
problem you're facing, then I have no idea. I got rid of OS X on my PB
months ago already...

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Getting rid of hotplug & Co. for 2.6

[Julien BLACHE]

Wolfgang Pfeiffer <[EMAIL PROTECTED]> wrote:

> So all I need to know: Can I run a 2.6 kernel without hal, udev and
> hotplug being installed, or with these packages being disabled at boot
> time at least?

You can, provided your kernel has built-in support for all of your
hardware.

As for hotplug, you should keep it installed to take care of your USB
devices, by disabling everything else in /etc/default/hotplug.

That's what I'm doing here, and my PB G4 500 boots faster than a fresh
Sarge install on a 1.4 GHz Athlon.

Do not forget to remove discover* if you haven't done so already; it's
even slower than hotplug, which is kind of a performance.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Battery charge cycles

[Julien BLACHE]

Joerg Sommer <[EMAIL PROTECTED]> wrote:

> I saw OS X can show the count of charge cycles. Can we have this in Linux
> too?
>
> http://www-astro.phys.metro-u.ac.jp/users/masai/darwin-app.html

Very interesting... Benjamin, is there any chance to find some code in
Darwin for that ? I really hope they didn't keep that
proprietary... (and would be interested in knowing whether this works
on a rev1 PB too)

Maybe it'd give me some information on the real state of my batteries,
because I just can't believe they degraded so fast.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[PATCH 2.6] Add back beep support to snd-powermac

[Julien BLACHE]

Hi,

The attached patch adds back the beep support to sound/ppc/pmac.c, aka
snd-powermac, and adds a dependency on INPUT in sound/ppc/Kconfig.

The patch is based on the code that used to be present in that file,
and got removed in early april last year. I ported it to the input
event interface based on the code used in dmasound_awacs.c.

Patch against linux-2.6.6 vanilla. Comments welcome, please apply.

JB.

-- 
Julien BLACHE   <http://www.jblache.org> 
<[EMAIL PROTECTED]>  GPG KeyID 0xF5D65169

diff -u linux-2.6.6/sound/ppc/Kconfig linux-2.6.6-BEEP/sound/ppc/Kconfig
--- linux-2.6.6/sound/ppc/Kconfig	2004-05-10 04:32:28.0 +0200
+++ linux-2.6.6-BEEP/sound/ppc/Kconfig	2004-06-19 14:09:46.916631952 +0200
@@ -5,7 +5,7 @@
 
 config SND_POWERMAC
 	tristate "PowerMac (AWACS, DACA, Burgundy, Tumbler, Keywest)"
-	depends on SND
+	depends on SND && INPUT
 	select SND_PCM
 
 endmenu
diff -u linux-2.6.6/sound/ppc/pmac.c linux-2.6.6-BEEP/sound/ppc/pmac.c
--- linux-2.6.6/sound/ppc/pmac.c	2004-05-10 04:33:21.0 +0200
+++ linux-2.6.6-BEEP/sound/ppc/pmac.c	2004-06-19 14:06:02.850695152 +0200
@@ -4,6 +4,10 @@
  * Copyright (c) by Takashi Iwai <[EMAIL PROTECTED]>
  * code based on dmasound.c.
  *
+ * 20040609 Julien BLACHE <[EMAIL PROTECTED]>
+ *  * Added back beep support code
+ *  * Updated to the 2.6 input system, based on dmasound_awacs.c
+ *
  *   This program is free software; you can redistribute it and/or modify
  *   it under the terms of the GNU General Public License as published by
  *   the Free Software Foundation; either version 2 of the License, or
@@ -27,6 +31,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include "pmac.h"
 #include 
@@ -38,7 +43,6 @@
 
 #define chip_t pmac_t
 
-
 #if defined(CONFIG_PM) && defined(CONFIG_PMAC_PBOOK)
 static int snd_pmac_register_sleep_notifier(pmac_t *chip);
 static int snd_pmac_unregister_sleep_notifier(pmac_t *chip);
@@ -258,6 +262,16 @@
 
 
 /*
+ * stop beep (no spinlock!)
+ */
+static void snd_pmac_beep_stop(pmac_t *chip)
+{
+	snd_pmac_dma_stop(&chip->playback);
+	st_le16(&chip->extra_dma.cmds->command, DBDMA_STOP);
+	snd_pmac_pcm_set_format(chip);
+}
+
+/*
  * PCM trigger/stop
  */
 static int snd_pmac_pcm_trigger(pmac_t *chip, pmac_stream_t *rec,
@@ -672,6 +686,227 @@
 }
 
 
+/*
+ * beep stuff
+ */
+
+/*
+ * Stuff for outputting a beep.  The values range from -327 to +327
+ * so we can multiply by an amplitude in the range 0..100 to get a
+ * signed short value to put in the output buffer.
+ */
+static short beep_wform[256] = {
+	0,	40,	79,	117,	153,	187,	218,	245,
+	269,	288,	304,	316,	323,	327,	327,	324,
+	318,	310,	299,	288,	275,	262,	249,	236,
+	224,	213,	204,	196,	190,	186,	183,	182,
+	182,	183,	186,	189,	192,	196,	200,	203,
+	206,	208,	209,	209,	209,	207,	204,	201,
+	197,	193,	188,	183,	179,	174,	170,	166,
+	163,	161,	160,	159,	159,	160,	161,	162,
+	164,	166,	168,	169,	171,	171,	171,	170,
+	169,	167,	163,	159,	155,	150,	144,	139,
+	133,	128,	122,	117,	113,	110,	107,	105,
+	103,	103,	103,	103,	104,	104,	105,	105,
+	105,	103,	101,	97,	92,	86,	78,	68,
+	58,	45,	32,	18,	3,	-11,	-26,	-41,
+	-55,	-68,	-79,	-88,	-95,	-100,	-102,	-102,
+	-99,	-93,	-85,	-75,	-62,	-48,	-33,	-16,
+	0,	16,	33,	48,	62,	75,	85,	93,
+	99,	102,	102,	100,	95,	88,	79,	68,
+	55,	41,	26,	11,	-3,	-18,	-32,	-45,
+	-58,	-68,	-78,	-86,	-92,	-97,	-101,	-103,
+	-105,	-105,	-105,	-104,	-104,	-103,	-103,	-103,
+	-103,	-105,	-107,	-110,	-113,	-117,	-122,	-128,
+	-133,	-139,	-144,	-150,	-155,	-159,	-163,	-167,
+	-169,	-170,	-171,	-171,	-171,	-169,	-168,	-166,
+	-164,	-162,	-161,	-160,	-159,	-159,	-160,	-161,
+	-163,	-166,	-170,	-174,	-179,	-183,	-188,	-193,
+	-197,	-201,	-204,	-207,	-209,	-209,	-209,	-208,
+	-206,	-203,	-200,	-196,	-192,	-189,	-186,	-183,
+	-182,	-182,	-183,	-186,	-190,	-196,	-204,	-213,
+	-224,	-236,	-249,	-262,	-275,	-288,	-299,	-310,
+	-318,	-324,	-327,	-327,	-323,	-316,	-304,	-288,
+	-269,	-245,	-218,	-187,	-153,	-117,	-79,	-40,
+};
+
+#define BEEP_SRATE	22050	/* 22050 Hz sample rate */
+#define BEEP_BUFLEN	512
+#define BEEP_VOLUME	15	/* 0 - 100 */
+
+static int snd_pmac_beep_event(struct input_dev *dev, unsigned int type, unsigned int code, int value)
+{
+	pmac_t *chip;
+	pmac_stream_t *rec;
+	pmac_beep_t *beep;
+	unsigned long flags;
+	int beep_speed = 0;
+	int srate;
+	int period, ncycles, nsamples;
+	int i, j, f;
+	short *p;
+
+	chip = (pmac_t *)dev->private;
+	beep = &chip->beep;
+
+	if (type != EV_SND)
+		return -1;
+
+	switch (code) {
+	case SND_BELL:
+		if (value)
+			value = 1000;
+		break;
+	case SND_TONE:
+		break;
+	default:
+		return -1;
+	}
+
+	if (beep->buf == NULL)
+		return -1;
+
+	rec = &chip->playback;
+
+	beep_speed = snd_pmac_rate_index(chip, rec, BEEP_SRATE);
+	srate = chip->freq_table[beep_speed];
+
+	spin_lock_irqsave(&chip->reg_lock, flags);
+	if (value <= sra

Re: [PATCH 2.6] Add back beep support to snd-powermac

[Julien BLACHE]

Derrik Pates <[EMAIL PROTECTED]> wrote:

Hi,

> Julien, this patch works well for the most part (a couple of hunks
> don't apply to 2.6.7 because a bit of the code it changes was removed
> - a little hand patching was required). However, I discovered that
> when audio playback is in progress, a terminal beep attempt will cause
> audio playback to stop. (When playing in XMMS, pausing and unpausing
> makes it continue.) I moved the check for (chip->playback.running ||
> chip->capture.running) to just after the if (beep->buf == NULL) check,
> and now I can play audio and an attempted terminal beep won't stall
> out audio playback in progress, and the beep returns normally after
> playback stops. Other than that, it's nice to have a working terminal
> beep again. Thanks for the patch.

You're welcome :-)

I wonder how I managed to miss the problem you reported, it's so
obvious. Doing too many things at the same time... Thanks for catching
this one.

Fixed and updated patch against Linux 2.6.7 attached.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

diff -u linux-2.6.7/sound/ppc/Kconfig linux-2.6.7-BEEP/sound/ppc/Kconfig
--- linux-2.6.7/sound/ppc/Kconfig	2004-06-16 07:19:22.0 +0200
+++ linux-2.6.7-BEEP/sound/ppc/Kconfig	2004-06-21 19:24:43.201378672 +0200
@@ -5,7 +5,7 @@
 
 config SND_POWERMAC
 	tristate "PowerMac (AWACS, DACA, Burgundy, Tumbler, Keywest)"
-	depends on SND
+	depends on SND && INPUT
 	select SND_PCM
 
 endmenu
diff -u linux-2.6.7/sound/ppc/pmac.c linux-2.6.7-BEEP/sound/ppc/pmac.c
--- linux-2.6.7/sound/ppc/pmac.c	2004-06-16 07:20:26.0 +0200
+++ linux-2.6.7-BEEP/sound/ppc/pmac.c	2004-06-21 19:28:52.73088 +0200
@@ -4,6 +4,10 @@
  * Copyright (c) by Takashi Iwai <[EMAIL PROTECTED]>
  * code based on dmasound.c.
  *
+ * 20040609 Julien BLACHE <[EMAIL PROTECTED]>
+ *  * Added back beep support code
+ *  * Updated to the 2.6 input system, based on dmasound_awacs.c
+ *
  *   This program is free software; you can redistribute it and/or modify
  *   it under the terms of the GNU General Public License as published by
  *   the Free Software Foundation; either version 2 of the License, or
@@ -27,6 +31,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include "pmac.h"
 #include 
@@ -38,7 +43,6 @@
 
 #define chip_t pmac_t
 
-
 #if defined(CONFIG_PM) && defined(CONFIG_PMAC_PBOOK)
 static int snd_pmac_register_sleep_notifier(pmac_t *chip);
 static int snd_pmac_unregister_sleep_notifier(pmac_t *chip);
@@ -259,6 +263,16 @@
 
 
 /*
+ * stop beep (no spinlock!)
+ */
+static void snd_pmac_beep_stop(pmac_t *chip)
+{
+	snd_pmac_dma_stop(&chip->playback);
+	st_le16(&chip->extra_dma.cmds->command, DBDMA_STOP);
+	snd_pmac_pcm_set_format(chip);
+}
+
+/*
  * PCM trigger/stop
  */
 static int snd_pmac_pcm_trigger(pmac_t *chip, pmac_stream_t *rec,
@@ -673,6 +687,226 @@
 }
 
 
+/*
+ * beep stuff
+ */
+
+/*
+ * Stuff for outputting a beep.  The values range from -327 to +327
+ * so we can multiply by an amplitude in the range 0..100 to get a
+ * signed short value to put in the output buffer.
+ */
+static short beep_wform[256] = {
+	0,	40,	79,	117,	153,	187,	218,	245,
+	269,	288,	304,	316,	323,	327,	327,	324,
+	318,	310,	299,	288,	275,	262,	249,	236,
+	224,	213,	204,	196,	190,	186,	183,	182,
+	182,	183,	186,	189,	192,	196,	200,	203,
+	206,	208,	209,	209,	209,	207,	204,	201,
+	197,	193,	188,	183,	179,	174,	170,	166,
+	163,	161,	160,	159,	159,	160,	161,	162,
+	164,	166,	168,	169,	171,	171,	171,	170,
+	169,	167,	163,	159,	155,	150,	144,	139,
+	133,	128,	122,	117,	113,	110,	107,	105,
+	103,	103,	103,	103,	104,	104,	105,	105,
+	105,	103,	101,	97,	92,	86,	78,	68,
+	58,	45,	32,	18,	3,	-11,	-26,	-41,
+	-55,	-68,	-79,	-88,	-95,	-100,	-102,	-102,
+	-99,	-93,	-85,	-75,	-62,	-48,	-33,	-16,
+	0,	16,	33,	48,	62,	75,	85,	93,
+	99,	102,	102,	100,	95,	88,	79,	68,
+	55,	41,	26,	11,	-3,	-18,	-32,	-45,
+	-58,	-68,	-78,	-86,	-92,	-97,	-101,	-103,
+	-105,	-105,	-105,	-104,	-104,	-103,	-103,	-103,
+	-103,	-105,	-107,	-110,	-113,	-117,	-122,	-128,
+	-133,	-139,	-144,	-150,	-155,	-159,	-163,	-167,
+	-169,	-170,	-171,	-171,	-171,	-169,	-168,	-166,
+	-164,	-162,	-161,	-160,	-159,	-159,	-160,	-161,
+	-163,	-166,	-170,	-174,	-179,	-183,	-188,	-193,
+	-197,	-201,	-204,	-207,	-209,	-209,	-209,	-208,
+	-206,	-203,	-200,	-196,	-192,	-189,	-186,	-183,
+	-182,	-182,	-183,	-186,	-190,	-196,	-204,	-213,
+	-224,	-236,	-249,	-262,	-275,	-288,	-299,	-310,
+	-318,	-324,	-327,	-327,	-323,	-316,	-304,	-288,
+	-269,	-245,	-218,	-187,	-153,	-117,	-79,	-40,
+};
+
+#define BEEP_SRATE	22050	/* 22050 Hz sample rate */
+#define BEEP_BUFLEN	512
+#define BEEP_VOLUME	15	/* 0 - 100 */
+
+static int snd_pmac_beep_event(s

Re: 2.4 & 2.6 kernels, should sarge be 2.6 only at least for powerpc ?

[Julien BLACHE]

Vincent Lefevre <[EMAIL PROTECTED]> wrote:

> As I said in a previous mail: the sound comes from the right speaker
> only and the audio files play twice as fast as the normal speed.
> (I tried with ogg123 at least.)

Increase the buffer by a factor of 2, and it'll be ok. That's what I
did. I never got the other problem you mention, though.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: 2.4 & 2.6 kernels, should sarge be 2.6 only at least for powerpc ?

[Julien BLACHE]

Vincent Lefevre <[EMAIL PROTECTED]> wrote:

>> Increase the buffer by a factor of 2, and it'll be ok. That's what I
>> did. I never got the other problem you mention, though.
>
> Which buffer?

ALSA's buffer; see the settings of whatever app you use :) (for XMMS
it's in the preferences for the output plugin)

> Did you report the bug?

No. It works.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: RC bug fix: build needed on PPC MIPS and MIPSel

[Julien BLACHE]

Martin-Éric Racine <[EMAIL PROTECTED]> wrote:

Hi,

> One of my package (cups-pdf) has RC bugs that were just fixed by a new 
> release.  
> PowerPC MIPS and MIPSel have not attempted the build after 2 days, according 
> to:

PPC build uploaded, MIPS on its way. I do not have a mipsel machine at
hand.

HTH,

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: Upgrading the HD of an iBook?

[Julien BLACHE]

Rogério Brito <[EMAIL PROTECTED]> wrote:

Hi,

> Before actually spending the cash on it, I would like to know others'
> experiences on this. BTW, what is the biggest HD that an iBook like this
> can have installed?

I did it on my PB G4 which is now 3 years old, so I guess you can do
it too :-)

> And if I have a given HD available in both 4200 RPM and 5400 RPM models,
> which one should I choose, if I am concerned about battery life (one of my
> main concerns regarding my notebook).

The 5400 rpm model will of course be a little bit faster. I replaced
my 30 GB/5400 rpm HD by a 60 GB/7200 rpm HD, and everything is much
faster now :) (who said "bottleneck" ? :)

You should grab the datasheets of the 3 drives, and compare the
figures. In my case, the new HD consumes a bit less power than the
original one (good surprise, indeed).

> Any comments or advices are extremely appreciated.

Here it is. :) Be careful when swapping the drives, it's not that easy
to do. Study carefully your laptop before unmounting the current
drive. I don't know how the drive is attached in the iBook, but I
guess it's similar to the PB.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: Battery monitor

[Julien BLACHE]

Tony <[EMAIL PROTECTED]> wrote:

Hi,

> I am trying to find a batter monitor to use with gnome.  I have
> pbbuttonsd/powerprefs installed.  When I try to use 'Battery Charge
> Monitor 2.6.2' it comes up but always shows the battery as empty.

You can use wmbatppc as a swallowed app in the GNOME panel (if that
still exists in GNOME)

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: Sound on new Powerbook

[Julien BLACHE]

"Matthew T. Atkinson" <[EMAIL PROTECTED]> wrote:

> I am using the ALSA modules and it only produces any sound when you plug
> in external speakers.  It is on my list of things to look into after
> this initrd problem and the CPUfreq issues have been sorted.
>
> Unfortunately it seems that these new PowerBook5,4s are a bit different
> than what came before :-S.

Apple has a tradition of using new, subtly different sound chips in
every new machine. Usually all it takes to get the new chip going is a
quick look at the Darwin sources and a day or two of hacking in the
dmasound driver.

Have fun :)

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: Videoprojector with PB 15" Alu

[Julien BLACHE]

Vincent Lefevre <[EMAIL PROTECTED]> wrote:

Hi,

> On my first generation G4 PowerBook, I can use an external monitor
> (or videoprojector) only with the 2.4.18 kernel.

According to BenH, you can get the CRT to work with m3mirror again by
only initializing the first screen reported by OF at boot.

In the 2.6 tree, this is done in arch/ppc/syslib/prom_init.c, in the
2.4 tree it's done in arch/ppc/kernel/prom_init.c.

A diff between kernel 2.4.18 and kernel 2.4.20 will show the changes
so you'll get an idea of what you have to do.

I haven't tested that yet, but that's something I should do this week,
as I'll need a working CRT, and cannot boot a 2.4 kernel anymore...

I'll post a patch if it works.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: iBook 2.2: Kernel 2.6.8 and beep (PC Speaker)?

[Julien BLACHE]

Ivo Marino <[EMAIL PROTECTED]> wrote:

> I've seen there were some patches to bring beep back to live on 2.6.7
> using ALSA and snd-powermac. Wich is the status of ALSA and beep in
> 2.6.8 kernel release? Will it work by default?

No. The code is in the ALSA CVS, and has been pushed to Linus, so it
should hopefully appear in next 2.6.9-pre.

Search lkml for an ALSA update at the end of august.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: iBook 2.2: Kernel 2.6.8 and beep (PC Speaker)?

[Julien BLACHE]

ncrfgs <[EMAIL PROTECTED]> wrote:

> A first attempt to solve the "beep issue" was present in the 
> alsa-bk-2004-08-15 patch, too. I suppose the code was mainly 
> based on the patch posted in this mailing list by Julien 
> Blache.

I am not sure the code in the ALSA CVS is based on the patch I posted
here, it may have been done independently.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: iBook 2.2: Kernel 2.6.8 and beep (PC Speaker)?

[Julien BLACHE]

Sven Luther <[EMAIL PROTECTED]> wrote:

> The huge alsa patch is not a candidate for inclusion in the 2.6.8 debian
> kernels though, so it would be best if we were able to isolate only the change
> that makes the beep work. If anyone feels like isolating this, send the
> (small) patch as a bug report against kernel-source-2.6.8, please.

Use filterdiff (patchutils) to filter the changes made to sound/ppc/*,
and here's your diff.

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: Videoprojector with PB 15" Alu

[Julien BLACHE]

Julien BLACHE <[EMAIL PROTECTED]> wrote:

> According to BenH, you can get the CRT to work with m3mirror again by
> only initializing the first screen reported by OF at boot.

> I'll post a patch if it works.

So here's the oneliner that makes it work again. ISTR that it was more
complicated than that. It's the same for a 2.4 kernel, btw, but it
won't apply because the context changed (in the 2.4 kernel there is a
comment above the for ()).

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

--- prom_init.c.orig	2004-09-07 11:31:26.534522288 +0200
+++ prom_init.c	2004-09-07 11:32:20.460324320 +0200
@@ -401,7 +401,7 @@
 			break;
 	}
 
-	for (j=0; j

Re: iBook 2.2: Kernel 2.6.8 and beep (PC Speaker)?

[Julien BLACHE]

Sven Luther <[EMAIL PROTECTED]> wrote:

Hi Sven,

>> Use filterdiff (patchutils) to filter the changes made to sound/ppc/*,
>> and here's your diff.
>
> I am over busy with other stuff right now, but would you care to do this and
> send me the patch (or fill a bug report) ?

Here it is. beep.patch contains everything related to the beep
support. chips.patch contains the other changes to the files in
sound/ppc, which are bugfixes and new features for the awacs, daca,
tumbler and burgundy chips.

The changes in chips.patch are minimal, you could apply them too
without any problem.

I didn't try to build with the patches applied (lacking time), but
reading the diff there's nothing that should break.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

--- linux-2.5-plain/sound/ppc/beep.c	1970-01-01 01:00:00.0 +0100
+++ linux-sound-plain/sound/ppc/beep.c	2004-08-26 21:17:10.0 +0200
@@ -0,0 +1,262 @@
+/*
+ * Beep using pcm
+ *
+ * Copyright (c) by Takashi Iwai <[EMAIL PROTECTED]>
+ *
+ *   This program is free software; you can redistribute it and/or modify
+ *   it under the terms of the GNU General Public License as published by
+ *   the Free Software Foundation; either version 2 of the License, or
+ *   (at your option) any later version.
+ *
+ *   This program is distributed in the hope that it will be useful,
+ *   but WITHOUT ANY WARRANTY; without even the implied warranty of
+ *   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ *   GNU General Public License for more details.
+ *
+ *   You should have received a copy of the GNU General Public License
+ *   along with this program; if not, write to the Free Software
+ *   Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307 USA
+ */
+
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include "pmac.h"
+
+struct snd_pmac_beep {
+	int running;	/* boolean */
+	int volume;	/* mixer volume: 0-100 */
+	int volume_play;	/* currently playing volume */
+	int hz;
+	int nsamples;
+	short *buf;		/* allocated wave buffer */
+	unsigned long addr;	/* physical address of buffer */
+	struct input_dev dev;
+};
+
+/*
+ * stop beep if running
+ */
+void snd_pmac_beep_stop(pmac_t *chip)
+{
+	pmac_beep_t *beep = chip->beep;
+	if (beep && beep->running) {
+		beep->running = 0;
+		snd_pmac_beep_dma_stop(chip);
+	}
+}
+
+/*
+ * Stuff for outputting a beep.  The values range from -327 to +327
+ * so we can multiply by an amplitude in the range 0..100 to get a
+ * signed short value to put in the output buffer.
+ */
+static short beep_wform[256] = {
+	0,	40,	79,	117,	153,	187,	218,	245,
+	269,	288,	304,	316,	323,	327,	327,	324,
+	318,	310,	299,	288,	275,	262,	249,	236,
+	224,	213,	204,	196,	190,	186,	183,	182,
+	182,	183,	186,	189,	192,	196,	200,	203,
+	206,	208,	209,	209,	209,	207,	204,	201,
+	197,	193,	188,	183,	179,	174,	170,	166,
+	163,	161,	160,	159,	159,	160,	161,	162,
+	164,	166,	168,	169,	171,	171,	171,	170,
+	169,	167,	163,	159,	155,	150,	144,	139,
+	133,	128,	122,	117,	113,	110,	107,	105,
+	103,	103,	103,	103,	104,	104,	105,	105,
+	105,	103,	101,	97,	92,	86,	78,	68,
+	58,	45,	32,	18,	3,	-11,	-26,	-41,
+	-55,	-68,	-79,	-88,	-95,	-100,	-102,	-102,
+	-99,	-93,	-85,	-75,	-62,	-48,	-33,	-16,
+	0,	16,	33,	48,	62,	75,	85,	93,
+	99,	102,	102,	100,	95,	88,	79,	68,
+	55,	41,	26,	11,	-3,	-18,	-32,	-45,
+	-58,	-68,	-78,	-86,	-92,	-97,	-101,	-103,
+	-105,	-105,	-105,	-104,	-104,	-103,	-103,	-103,
+	-103,	-105,	-107,	-110,	-113,	-117,	-122,	-128,
+	-133,	-139,	-144,	-150,	-155,	-159,	-163,	-167,
+	-169,	-170,	-171,	-171,	-171,	-169,	-168,	-166,
+	-164,	-162,	-161,	-160,	-159,	-159,	-160,	-161,
+	-163,	-166,	-170,	-174,	-179,	-183,	-188,	-193,
+	-197,	-201,	-204,	-207,	-209,	-209,	-209,	-208,
+	-206,	-203,	-200,	-196,	-192,	-189,	-186,	-183,
+	-182,	-182,	-183,	-186,	-190,	-196,	-204,	-213,
+	-224,	-236,	-249,	-262,	-275,	-288,	-299,	-310,
+	-318,	-324,	-327,	-327,	-323,	-316,	-304,	-288,
+	-269,	-245,	-218,	-187,	-153,	-117,	-79,	-40,
+};
+
+#define BEEP_SRATE	22050	/* 22050 Hz sample rate */
+#define BEEP_BUFLEN	512
+#define BEEP_VOLUME	15	/* 0 - 100 */
+
+static int snd_pmac_beep_event(struct input_dev *dev, unsigned int type, unsigned int code, int hz)
+{
+	pmac_t *chip;
+	pmac_beep_t *beep;
+	unsigned long flags;
+	int beep_speed = 0;
+	int srate;
+	int period, ncycles, nsamples;
+	int i, j, f;
+	short *p;
+
+	if (type != EV_SND)
+		return -1;
+
+	switch (code) {
+	case SND_BELL: if (hz) hz = 1000;
+	case SND_TONE: break;
+	default: return -1;
+	}
+
+	chip = dev->private;
+	if (! chip || (beep = chip->beep) == NULL)
+		return -1;
+
+	if (! hz) {
+		spin_lock_irqsave(&chip->reg_lock, flags);
+		if (beep->running)
+			s

Re: ATI Rage128 video out didn't work

[Julien BLACHE]

Matthias Grimm <[EMAIL PROTECTED]> wrote:

Hi,

> I tried to force Xfree86 (4.3.0) to use the external video output. I set the 
> Option "Display" to "Mirror" but the videodriver (r128) told me that it will 
> ignore this option because the framebuffer knows about the right display 
> device.
>
> I don't know what to do next. I searched the internet but found only hints 
> and 
> tutorials for the Radeon cards but non for the Rage128.

First, you need to patch the kernel, this way:

--- prom_init.c.orig2004-09-07 11:31:26.534522288 +0200
+++ prom_init.c 2004-09-07 11:32:20.460324320 +0200
@@ -401,7 +401,7 @@
break;
}
 
-   for (j=0; j 
 
 Public key available on  - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: ATI Rage128 video out didn't work

[Julien BLACHE]

Dean Hamstead <[EMAIL PROTECTED]> wrote:

Hi,

> is there any reason this patch isnt in the kernel?
>
> would be nice to have it in the debian packaged kernel
> rather than having to rebuild.

This patch reverts changes made to prom_init.c around kernel 2.4.21,
which are necessary for some machines. BenH can give you more details,
as he's the one who did the changes.

This code runs early in the boot process, I'm not sure kernel
parameters are already available at that time, otherwise it'd be the
way to go. That, or a conditional based on the machine type, if it's
available at that time.

Remember that m3mirror is a gross hack that just equals to pure luck,
and the proper solution is to implement a proper dual-head support in
X and/or the framebuffer.

Unfortunately, it's not that easy to do without documentation, even if
the code would be very similar to the code of the radeon driver.

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: Cloning to an external video projector...

[Julien BLACHE]

Eugen Dedu <[EMAIL PROTECTED]> wrote:

Hi,

> I have already used my PowerBook G4 15" for videoprojection.  You need
> to patch the kernel (I have patched 2.6.8.1).  See videoprojection
> topic, reply of Julien Blache, at
> http://wiki.debian.net/index.cgi?DebianOnPowerPC.

The patch only works for machines with a Rage 128 chipset. Someone
please add that to the wiki if it's not written already...

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: ATI Rage128 video out didn't work

[Julien BLACHE]

Dean Hamstead <[EMAIL PROTECTED]> wrote:

Hi,

> has this patch been merged into the debian kernal image yet?

No, and it won't, for reasons I explained in the same thread. Check
the archives.

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: Battery status not correctly seen - how to fix?

[Julien BLACHE]

"Kevin B. McCarty" <[EMAIL PROTECTED]> wrote:

> A little more info about this:  the battery level seen just dropped from
> 99% to 0% while running on battery, causing a shutdown before I could
> plug in the power cable.  The result of "cat /proc/apm" is currently
>
> 0.5 1.1 0x00 0x01 0x03 0x08 0% -1 min

What are the reported values in /proc/pmu/* ? These are the ones you
should trust.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: Power meter.

[Julien BLACHE]

Johannes Mockenhaupt <[EMAIL PROTECTED]> wrote:

Hi,

> It's wmbatppc. This is enabled/disabled during compilation through the
> Makefile[1]. You can apt-get the source and compile it without
> osd-support. Remember to pin the package to avoid accidential upgrading
> your customized package.

I'll make that a runtime option in the next upload.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: AlBook 12"/2.4.23-pre5-ben0: bad status dma on hdc

[Julien BLACHE]

Guido Guenther <[EMAIL PROTECTED]> wrote:

> Are there linux utilities to read/set the region code of the drive?

Search for regionset, it's been ITPed a couple of days ago.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Issues with firewire hard drive

[Julien BLACHE]

Hi,

I'm trying to get a LaCie PocketDriver 60 GB to work with my PB G4
(first gen).

Everything is fine with a 2.4.20-benh kernel, but it completely fails
with any later version. It never gets past the point of logging into
the sbp2 device.

Would anyone have the tip that will make the damn thing work with a
recent kernel ?

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: Issues with firewire hard drive

[Julien BLACHE]

Soeren Sonnenburg <[EMAIL PROTECTED]> wrote:

>> Would anyone have the tip that will make the damn thing work with a
>> recent kernel ?
>
> Even with the most recent 2.6.2-rcX-benX kernel ?

I didn't test 2.6.

I need my laptop working next week, I can't break it now, so 2.6 will
have to wait (and mature) some more, sorry.

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: Issues with firewire hard drive

[Julien BLACHE]

Soeren Sonnenburg <[EMAIL PROTECTED]> wrote:

>> Would anyone have the tip that will make the damn thing work with a
>> recent kernel ?
>
> Even with the most recent 2.6.2-rcX-benX kernel ?

OK, it indeed works with 2.6.2-rc1-ben1. I finally decided to build a
2.6 kernel, now I have to set up a couple of things, that's a long
night coming... :)

Thanks,

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: 2.6.2-rc1-ben1 and XFS anyone?

[Julien BLACHE]

"J. Javier Maestro" <[EMAIL PROTECTED]> wrote:

> I was wondering if any of you managed to boot a self-compiled
> 2.6.2-rc1-ben1 with XFS support and, obviously, an XFS system (say the /
> partition).

Running fine here.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: 2.6.2-rc1-ben1 and XFS anyone? (+some questions)

[Julien BLACHE]

"J. Javier Maestro" <[EMAIL PROTECTED]> wrote:

Hi,

> Dammit, now, that IS weird...
>
> how did you turn it into XFS? Did you install from Ethan's ISO or you
> turned an EXT2/3 into XFS?

I installed the machine 2.5 years ago, with a standard Woody CD, then
built a 2.4+XFS kernel, copied the system to the new XFS partition,
then repartitioned the disk to enlarge the system partition and ran
xfs_growfs (gotta love that feature) :-)

It's been running absolutely fine since then. (and survived a couple
of kernel crashes due to my own drivers and power outages)

> I am just wondering what on earth is happening here... because it is
> very weird that a 2.4.23 kernel boots fine the XFS and the 2.6.2 breaks
> and panics...

Maybe a devfs/udev problem ? I don't use that kind of dangerous things
:P

> Can you tell me what stuff you installed, or things like that? What did
> you do to make your system run?

I did nothing special. It just works (tm)

> And finally, can you send me your kernel config so I can try and compile
> my kernel?

Config attached.

Now, I've just got a weird thing with 2.6.2-rc1-ben1, the laptop just
went down while I was typing.

I seem to recall someone reported a similar problem, but I can't
remember if a solution was found or not. If yes, could somebody
refresh my memory ?

As a last question, has anybody tried to get the vga output of a first
gen PB G4 working under 2.6 ? Forward porting Owen Stampflee's patch
didn't work (contacted him, hope something can be worked out) :/

Thanks,

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

CONFIG_MMU=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_HAVE_DEC_LOCK=y
CONFIG_PPC=y
CONFIG_PPC32=y
CONFIG_GENERIC_NVRAM=y
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_KMOD=y
CONFIG_6xx=y
CONFIG_ALTIVEC=y
CONFIG_TAU=y
CONFIG_PM=y
CONFIG_PPC_STD_MMU=y
CONFIG_PPC_MULTIPLATFORM=y
CONFIG_PPC_CHRP=y
CONFIG_PPC_PMAC=y
CONFIG_PPC_PREP=y
CONFIG_PPC_OF=y
CONFIG_PPCBUG_NVRAM=y
CONFIG_KERNEL_ELF=y
CONFIG_BINFMT_ELF=y
CONFIG_PROC_DEVICETREE=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_PCI=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCI_NAMES=y
CONFIG_HOTPLUG=y
CONFIG_PCMCIA=m
CONFIG_YENTA=m
CONFIG_CARDBUS=y
CONFIG_HIGHMEM_START=0xfe00
CONFIG_LOWMEM_SIZE=0x3000
CONFIG_KERNEL_START=0xc000
CONFIG_TASK_SIZE=0x8000
CONFIG_BOOT_LOAD=0x0080
CONFIG_BLK_DEV_LOOP=y
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_ADMA=y
CONFIG_BLK_DEV_IDE_PMAC=y
CONFIG_BLK_DEV_IDEDMA_PMAC=y
CONFIG_BLK_DEV_IDE_PMAC_BLINK=y
CONFIG_BLK_DEV_IDEDMA_PMAC_AUTO=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
CONFIG_BLK_DEV_SD=m
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
CONFIG_SCSI_QLA2XXX_CONFIG=y
CONFIG_IEEE1394=m
CONFIG_IEEE1394_OHCI1394=m
CONFIG_IEEE1394_SBP2=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_ADB_PMU=y
CONFIG_PMAC_PBOOK=y
CONFIG_PMAC_APM_EMU=y
CONFIG_PMAC_BACKLIGHT=y
CONFIG_ADB=y
CONFIG_ADB_MACIO=y
CONFIG_INPUT_ADBHID=y
CONFIG_MAC_EMUMOUSEBTN=y
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_NETLINK_DEV=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_SYN_COOKIES=y
CONFIG_IPV6=y
CONFIG_IPV6_SCTP__=y
CONFIG_NETDEVICES=y
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
CONFIG_CRC32=y
CONFIG_SUNGEM=y
CONFIG_PPP=m
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_NET_RADIO=y
CONFIG_HERMES=y
CONFIG_APPLE_AIRPORT=y
CONFIG_NET_WIRELESS=y
CONFIG_IRDA=m
CONFIG_IRLAN=m
CONFIG_IRNET=m
CONFIG_IRCOMM=m
CONFIG_IRTTY_SIR=m
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1152
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_EVDEV=y
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_INPUT_MOUSE=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_PMACZILOG=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_NVRAM=y
CONFIG_GEN_RTC=y
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=m
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_KEYWEST=y
CONFIG_FB=y
CONFIG_FB_OF=y
CONFIG_FB_ATY128=y
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_SOUND=y
CONFIG_DMASOUND_PMAC=m
CONFIG_DMASOUND=m
CONFIG_SND=y
CONFIG_SND_SEQUENCER=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFI

Re: Compilation instructions for m3mirror

[Julien BLACHE]

Toby Johnson <[EMAIL PROTECTED]> wrote:

Hi,

> The binary from penguinppc.org/~benh seems to have stopped working
> some time after the 2.4.20 kernel and before the 2.4.24 kernel.  I'm
> guessing that I need to recompile against the new kernel headers.

This won't help. It's a kernel change that broke m3mirror.

You have 2 solutions :
 - use Owen Stampflee's patch at
   <http://www.stampflee.com/kernel/>
 - replace arch/ppc/kernel/prom_init.c with the same file from the
   2.4.20 kernel.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: 2.6.2-rc1-ben1 and XFS anyone? (+some questions)

[Julien BLACHE]

"J. Javier Maestro" <[EMAIL PROTECTED]> wrote:

>   /dev/hda1 Apple partition table
>   /dev/hda2 Apple bootstrap
>   /dev/hda3 Linux swap  (1G)
>   /dev/hda4 EMPTY (for XFS, 57G)
>   /dev/hda5 Linux Native (EXT3, for sarge / )
>
> so when I grow hda4 it swallows hda5 and I end up with a nice numbered
> system? :)  Does the opposite (grow hda5 to swallow hda4) work (if you

You can only grow an XFS FS, you cannot "move" it, I mean the start of
the partition cannot move. So hda4 remains hda4 (starts at the same
place), it's only bigger.

> know, of course)? If worse comes to worse, I can always fix the
> partition numbers and mess with /etc/fstab, right?

Yes. Depends what you mean by "worse". :)

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: Dual head on G4 Powerbook 400MHz

[Julien BLACHE]

David Stanaway <[EMAIL PROTECTED]> wrote:

> I am trying to get dual head, or even just CRT only use from the Rage
> 128 M3 on my TiBook without much luck.

The good news is, the problem is known; the bad news is, nobody is
working on it.

There was a patch for the 2.4 kernel, but it doesn't work on 2.6. On
2.4, you could also replace the prom_init.c file with the one from
2.4.20 and that would allow you to use m3mirror to enable the crt
output.

Maybe it's possible to reuse prom_init.c from 2.4.20 with a 2.6
kernel, I haven't tried (yet).

The proper solution would be to add dualhead support to
aty128fb.c. (or pester BenH until he either writes the code or gives
us enough information to do it -- now that radeonfb is mostly fixed,
maybe we can get a chance ? ;)

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: Dual head on G4 Powerbook 400MHz

[Julien BLACHE]

David Stanaway <[EMAIL PROTECTED]> wrote:

Hi,

>> There was a patch for the 2.4 kernel, but it doesn't work on 2.6. On
>> 2.4, you could also replace the prom_init.c file with the one from
>> 2.4.20 and that would allow you to use m3mirror to enable the crt
>> output.
>
> I have had a look at the differences, and the only things I can see are
> some POWER4 additions, and improving the process for opening the
> displays in check_display.

The POWER4 parts are just noise in our case; what broke the mirroring
is the changes made to check_display, where each available display is
opened. (as said in private mail already)

> Would a hack workaround be to change the sorting of display nodes so
> that the CRT is opened first?

I don't think so, but I'm no expert.

> I haven't looked through the aty128fb driver yet, but what is involved
> in fixing up dualhead there?

There's no support at all currently, only a gross hack to set up a
basic mirroring between the 2 heads. BenH told me that looking at the
XFree86 radeon driver might help to get something done on the M3.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: Low battery -> power down + clock set back to 1904-01-01

[Julien BLACHE]

Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:

Hi,

> Or maybe you just wasn't fast enough flipping the battery... I suspect
> we don't power things down as efficiently than MacOS when going to sleep
> (we just don't have the HW infos for some stuffs like the thermostat/fan
> controllers and maybe a few others), thus we eat a bit more power when
> in sleep mode. Also the amount of RAM is significant. That can affect
> how long the machine survives without battery...

Vincent, are you running a 2.4 or 2.6 kernel ?

I noticed the same kind of problem with 2.4 kernels after 2.4.20. It's
impossible to swap the battery with these kernels, the machine always
crashes.

However, I can swap the battery with my current 2.6.2rc2 just
fine. Maybe there's something different in sleep code between 2.4 and
2.6 ?

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: xsane crash

[Julien BLACHE]

christophe barbe <[EMAIL PROTECTED]> wrote:

> 1:0.1.8-7 works for me with gphoto2. Could you try to rebuild xsane
> against the latest libusb-dev?

There's a new XSane in the pipe, it's just stuck in NEW at the moment,
so please wait for this new version (0.92-3) before filing a bug.

There's a new libsane too, that should be coming soon for powerpc.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: xsane crash

[Julien BLACHE]

"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:

>> There's a new XSane in the pipe, it's just stuck in NEW at the
>> moment,
>> so please wait for this new version (0.92-3) before filing a bug.
>
> Did you apply your patch (for xsane plugin in gimp-1.3+) on this
> version or is the compilation needed for using it ?

It's GIMP2.0-enabled, yes. GIMP 1.2 isn't available in Debian
anyway... :)

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 

Re: Yaboot problem on TiBook

[Julien BLACHE]

Łukasz Studziński <[EMAIL PROTECTED]> wrote:

> I was trying to upgrade kernel and Debian SID on my friend's TiBook 667
> when I faced a problem with yaboot 1.3.12. When trying to run "ybin" it
> returned the following message: 
> ybin: Unable to find OpenFirmware path for boot=/dev/hda9
> ybin: Please add ofboot= where  is the OpenFirmware path 
> to /dev/hda9 to /etc/yaboot.conf

If you use a kernel older than 2.6.3, downgrade to the previous
version of yaboot. See the changelog...

(what a nice surprise, ever heard of this thing called "backward
compatibility" ?)

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169