Bug#344592: rsync sometimes does unnecessary copies - fixed in latest release from upstream

[Rick Thomas]

Package: rsync
Version: 2.6.4-6
Severity: normal
Tags: patch


this bug is fixed in upstream release 2.6.5 (and presumably also in the
latest upstream release, 2.6.6) from rsync.samba.org

Quote from the changelog for 2.6.5

- Fixed a case where rsync would erroneously delete some files and then
  re-transfer them when the options --relative (-R) and --recursive
  (-r) were both enabled (along with --delete) and a source path had a
  trailing slash.

This bug makes rsync backups (using e.g. the rsnapshot program) larger
than they need to be.

-- System Information:
Debian Release: 3.1
Architecture: powerpc (ppc)
Kernel: Linux 2.6.8-powerpc
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages rsync depends on:
ii  libc6   2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libpopt01.7-5lib for parsing cmdline parameters

-- no debconf information


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

Bug#344592: rsync sometimes does unnecessary copies - fixed in latest release from upstream

[Rick Thomas]

On Dec 23, 2005, at 5:37 PM, Paul Slootman wrote:


tags 344592 = sarge
thanks

On Thu 22 Dec 2005, Rick Thomas wrote:


Package: rsync
Version: 2.6.4-6
Severity: normal
Tags: patch


I see no patches...
Perhaps you wanted to tag it as sarge, as testing and unstable have had
2.6.6 since one day after upstream released it.


Sorry... put it down to inexperience.  I thought pointing out that it 
was fixed upstream was as good as a patch.  I guess not.





this bug is fixed in upstream release 2.6.5 (and presumably also in 
the

latest upstream release, 2.6.6) from rsync.samba.org


... and from Debian etch.


Cool!  Can i just download the .deb from a random etch repository, and 
install it on an otherwise all sarge system?  As you can tell, I'm a 
little bit new to this Debian stuff, though I've been doing Linux (and 
UNIX before it) for more years than I want to count.






Quote from the changelog for 2.6.5


- Fixed a case where rsync would erroneously delete some files 
and then
  re-transfer them when the options --relative (-R) and 
--recursive
  (-r) were both enabled (along with --delete) and a source path 
had a

  trailing slash.

This bug makes rsync backups (using e.g. the rsnapshot program) larger
than they need to be.


Does rsnapshot actually use that combination of options?
Dirvish (which I use) isn't affected AFAIK.


Yes.  The reason I noticed it was because rsnapshot was doing it.  Off 
Topic:  What made you choose dirvish over rsnapshot?



I'll leave this bug as-is until a new stable version of Debian is
released; there's no way of getting a fix for something like this into 
a

point release.



OK.  It's sad that the release procedures aren't flexible enough to get 
an obvious bug fix like this slipstreamed in, but I understand the 
reasons.




Paul Slootman


Thanks! for the quick reply.

Rick



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

Bug#310529: PowerPC Netinst RC3 CD is missing kernel-image-2.4.27-powerpc

[Rick Thomas]

Package: installation-reports

> INSTALL REPORT
>
> Debian-installer-version: image>


 Index of /pub/cdimage-testing/sarge_d-i/powerpc/rc3
  Name   Last modified   Size  Description


  Parent Directory   24-Mar-2005 02:39  -
  MD5SUMS23-Mar-2005 02:35 1k
  MD5SUMS.sign   24-Mar-2005 02:45 1k
  sarge-powerpc-businesscard.iso 23-Mar-2005 02:2799M
  sarge-powerpc-netinst.iso  23-Mar-2005 02:35   194M

 Apache/1.3.31 Server at cdimage.debian.org Port 80


> uname -a: 

Not available because of bug this is reporting.


> Date: 

May 10, 2005, and a couple of times after, just to be sure.


> Method: How did you install?  What did you boot off?  If network
>   install, from where?  Proxied?

Booted installation from MacOS-9.1 with BootX.  Installed from netinst 
RC3 CD.  used vmlinux and initrd.gz from the install/powerc/2.4 folder. 
 Used DEBCONF_PRIORITY=medium.



> Machine: 

Apple PowerMac 6500/225 (OldWorld)


> Processor:

powerPC 604E


> Memory:

128 MB


> Root Device: 

SCSI


> Root Size/partition table:  Feel free to paste the full partition
>   table, with notes on which partitions are mounted where.

No longer available.  It's currently running 2.6 -- Sorry!  The 
relevant details are that it was three partitions: an HFS+ partition 
for MacOS-9.1, and a Linux root and swap.  There was no boot partition 
-- not needed since I intended to use BootX, not quik as my boot 
loader.  The root partition was ext3.



> Output of lspci and lspci -n:

(This was taken with a 2.6 kernel running on the machine)
:00:0b.0 0600: 106b:0001 (rev 03)
:00:0b.0 Host bridge: Apple Computer Inc. Bandit PowerPC host 
bridge (rev 03)

:00:10.0 ff00: 106b:0007 (rev 01)
:00:10.0 ff00: Apple Computer Inc. O'Hare I/O (rev 01)
:00:11.0 0200: 1011:0014 (rev 21)
:00:11.0 Ethernet controller: Digital Equipment Corporation DECchip 
21041 [Tulip Pass 3] (rev 21)

:00:12.0 0300: 1002:4754 (rev 41)
:00:12.0 VGA compatible controller: ATI Technologies Inc 3D Rage 
I/II 215GT [Mach64 GT] (rev 41)




>
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
>
> Initial boot worked:[o] See Note 1
> Configure network HW:   [o]
> Config network: [o]
> Detect CD:  [o]
> Load installer modules: [o]
> Detect hard drives: [o]
> Partition hard drives:  [o] manual
> Create file systems:[o]
> Mount partitions:   [o]
> Install base system:[o]
> Install boot loader:[ ] I use BootX instead of quik.
> Reboot: [E] See Note 2
>
> Comments/Problems:
>and ideas you had during the initial install.>

Note 1:
As noted above, I booted the installation kernel and initrd.gz from the 
install/powerc/2.4 folder on the RC3 netinst CD.



Note 2:
When it came time to install the kernel, the only options are
kernel-image-2.6.8-powerpc
kernel-image-2.6.8-power4
kernel-image-2.6.8-power3
kernel-image-2.4.27-apus

Notable by it's absence was anything like kernel-image-2.4.27-powerpc.

Interestingly enough, there was a kernel-image-2.4.27-powerpc available 
when I used the RC3 businesscard CD to install this same machine.


I assume this is an oversight?  I certainly hope it's not intentional 
to disallow us OldWorld Mac users from running a 2.4 kernel if we want 
to!



>
> Install logs and other status info is available in 
/var/log/debian-installer/.
> Once you have filled out this report, mail it to 
[EMAIL PROTECTED]

>

I don't think they are likely to be relevant.  But if you need them, 
just ask.


Rick




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

Bug#293506: Debian sarge RC2 NewWorld PowerMac installation report

[Rick Thomas]

Package: installation-reports
INSTALL REPORT
=
Executive Summary:
All went well until it came time after the reboot to configure the 
software packages.  After repeated failures, I tried "choose packages 
manually" (i.e. aptitude) and that went OK.

This is OK for experts, but not ready for the release to the great 
unwashed masses.

=
Debian-installer-version: 
	PowerPC (Macintosh) RC2 businesscard CD
	
uname -a: 
	Linux ribbit 2.6.8-powerpc #1 Sat Jan 8 22:01:09 CET 2005 ppc GNU/Linux

Date: 
Feb 3, 2004 5:30 PM US Eastern time
Method: How did you install?  What did you boot off?  If network 
install, from where?  Proxied?
	CD-Direct boot (hold down "option" key to get graphical boot screen - 
choose CD)

Machine: 
NewWorld PowerPC Macintosh grey deskside tower
detected as: PowerMac G4 AGP Graphics
Processor:
PPC-7400 (G4) 350 MHz
Memory:
768 MB

Root Device: 

Root Size/partition table:  Feel free to paste the full partition 
table, with notes on which partitions are mounted where.
	/dev/hda (the master IDE disk) has MacOS on it.
	/dev/hdb (the slave IDE disk) has the newly installed Debian "sarge" 
Linux on it.

ribbit:~# mac-fdisk -l
/dev/hda
#type name length   base
 ( size )  system
/dev/hda1 Apple_partition_map Apple63 @ 1   
 ( 31.5k)  Partition map
/dev/hda2  Apple_Driver43 Macintosh54 @ 64  
 ( 27.0k)  Driver 4.3
/dev/hda3  Apple_Driver43 Macintosh74 @ 118 
 ( 37.0k)  Driver 4.3
/dev/hda4Apple_Driver_ATA Macintosh54 @ 192 
 ( 27.0k)  Unknown
/dev/hda5Apple_Driver_ATA Macintosh74 @ 246 
 ( 37.0k)  Unknown
/dev/hda6  Apple_FWDriver Macintosh   200 @ 320 
 (100.0k)  Unknown
/dev/hda7  Apple_Driver_IOKit Macintosh   512 @ 520 
 (256.0k)  Unknown
/dev/hda8   Apple_Patches Patch Partition 512 @ 1032
 (256.0k)  Unknown
/dev/hda9   Apple_HFS untitled   11264000 @ 1544
 (  5.4G)  HFS
/dev/hda10  Apple_HFS untitled 2 11264000 @ 
11265544 (  5.4G)  HFS
/dev/hda11  Apple_HFS untitled 3 17631422 @ 
22529544 (  8.4G)  HFS
/dev/hda12 Apple_Free Extra22 @ 
40160966 ( 11.0k)  Free space

Block size=512, Number of Blocks=40160988
DeviceType=0x0, DeviceId=0x0
Drivers-
1: @ 64 for 23, type=0x1
2: @ 118 for 36, type=0x
3: @ 192 for 21, type=0x701
4: @ 246 for 34, type=0xf8ff
/dev/hdb
#type namelength   base
( size )  system
/dev/hdb1 Apple_partition_map Apple   63 @ 1   
( 31.5k)  Partition map
/dev/hdb2 Apple_Bootstrap boot195313 @ 64  
( 95.4M)  NewWorld bootblock
/dev/hdb3 Apple_UNIX_SVR2 root   6445313 @ 195377  
(  3.1G)  Linux native
/dev/hdb4 Apple_UNIX_SVR2 swap   1765085 @ 6640690 
(861.9M)  Linux swap

Block size=512, Number of Blocks=8405775
DeviceType=0x0, DeviceId=0x0
Drivers-
1: @ 64 for 23, type=0x1
2: @ 118 for 36, type=0x
3: @ 192 for 21, type=0x701
4: @ 246 for 34, type=0xf8ff
ribbit:~# df -m
Filesystem   1M-blocks  Used Available Use% Mounted on
/dev/hdb3 3098   379  2562  13% /
tmpfs  379 0   379   0% /dev/shm
ribbit:~#
Output of lspci and lspci -n:
ribbit:~# ( lspci -n ; lspci ) | sort
:00:0b.0 0600: 106b:0020
:00:0b.0 Host bridge: Apple Computer Inc. UniNorth AGP
:00:10.0 0300: 1002:5046
:00:10.0 VGA compatible controller: ATI Technologies Inc Rage 128 
PF/PRO AGP 4x TMDS
0001:10:0b.0 0600: 106b:001f
0001:10:0b.0 Host bridge: Apple Computer Inc. UniNorth PCI
0001:10:0d.0 0604: 1011:0026 (rev 05)
0001:10:0d.0 PCI bridge: Digital Equipment Corporation DECchip 21154 
(rev 05)
0001:11:02.0 0100: 9004:5078 (rev 03)
0001:11:02.0 SCSI storage controller: Adaptec AHA-7850 (rev 03)
0001:11:07.0 ff00: 106b:0022 (rev 02)
0001:11:07.0 ff00: Apple Computer Inc. KeyLargo Mac I/O (rev 02)
0001:11:08.0 0c03: 106b:0019
0001:11:08.0 USB Controller: Apple Computer Inc. KeyLargo USB
0001:11:09.0 0c03: 106b:0019
0001:11:09.0 USB Controller: Apple Computer Inc. KeyLargo USB
0001:11:0a.0 0c00: 104c:8019
0001:11:0a.0 FireWire (IEEE 1394): Texas Instruments TSB12LV23 
IEEE-1394 Controller
0002:21:0b.0 0600: 106b:001e
0002:21:0b.0 Host bridge: Apple Computer Inc. UniNorth Internal PCI
0002:21:0f.0 0200: 106b:0021
0002:21:0f.0 Ethernet controller: Apple Computer Inc. UniNorth GMAC 
(Sun GEM)
ribbit:~#


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked:[O] Note 1 & 2
Configure network HW:   [O] Note 4
Config network: [O] Note 5 & 6 & 

Bug#315308: (no subject) PowerMac Debian install boot floppies

[Rick Thomas]

On Jun 21, 2005, at 3:31 PM, Jacob Fugal wrote:


Package: installation-reports

Debian-installer-version: boot.img from  
http://http.us.debian.org/debian/dists/sarge/main/installer-powerpc/ 
current//images/powerpc/floppy/ on 6-21-2005

uname -a: Never got that far (Debian 3.1 Sarge)
Date: 6-21-2005, 15:25 EDT

Method: I tried installing a Power Macintosh G3 (Beige minitower) from  
a floppy. I tried copying the image boot.img from my current Debian  
box using the command "dd ..." as specified on to four different  
floppies. I tried .../floppy and .../floppy-2.4 and put the floppy in  
the system and as soon as it booted up, it spit the disk out of the  
system.
The screen showed a floppy disk with an x in it. Reinserting did  
nothing.


Jacob,

There are "freeness" problems with the boot-loader program that goes on  
the PowerMac (OldWorld) floppys.  So the working PowerMac Debian boot  
floppies are not well advertized.  They are buried away at


http://people.debian.org/~luther/d-i/images/2005-06-20/powerpc/

Give that a try.  If it doesn't work, try earlier dates than  
'2005-06-20'.


It's not a politically correct viewpoint but in my humble opinion, you  
are best off getting a MacOS {8 or 9} installation CD and using MacOS  
with the BootX extension as your Linux boot loader.  Email me off-list  
if you need instructions for doing that.


Installing from floppy can be done on a Beige G3 mini-tower.  I've got  
a couple of them running right now to prove it.  But MacOS with BootX  
is way easier!


Rick



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

Bug#315393: Problems installing Sarge on OldWorld 7300/200 Mac

[Rick Thomas]

There are "freeness" problems with the boot-loader program that goes on 
the PowerMac (OldWorld) floppies.  So the working PowerMac Debian boot 
floppies are not well advertised [*].  They are buried away at


http://people.debian.org/~luther/d-i/images/2005-06-20/powerpc/

Give that a try.  If it doesn't work, try earlier dates than 
'2005-06-20'.


It's not a politically correct viewpoint but in my humble opinion, you 
are best off getting a MacOS {8 or 9} installation CD and using MacOS 
with the BootX extension as your Linux boot loader.  Email me off-list 
if you need instructions for doing that.


I've never tried a 7300 personally, but installing from floppy can be 
done on a Beige G3 mini-tower, because I've got a couple of them 
running right now to prove it.  But MacOS with BootX is way easier!


Rick

[*] The advertised boot floppy images don't work because they don't 
contain the (non-free) miboot program.  Sigh!  Politics is *so* much 
fun!




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

Bug#315393: Problems installing Sarge on OldWorld 7300/200 Mac

[Rick Thomas]

On Jun 22, 2005, at 6:45 AM, Jan-Benedict Glaw wrote:


  * The 7300/200 seems to not be able to boot off a CD-ROM, at least I
failed to do that using
 
http://cdimage.debian.org/debian-cd/3.1_r0a/powerpc/iso-cd/debian 
-31r0a-powerpc-businesscard.iso

Maybe I just used a wrong boot command line, but the install
instructions are somewhat poor describing the actual boot process
(note: I just got these Macs and never ever touched any Mac  
before).



Booting the OldWorld PPC Macs from a CD is only possible if the CD has  
special Apple-proprietary drivers on it.  For Debian to make an install  
CD image with those drivers would be a violation of the Debian freeness  
guidelines... as well as illegal in most countries.


Bottom line: you have to use some kind of subterfuge, such as BootX or  
a floppy with miboot on it, to install Debian GNU/Linux on an OldWorld  
Mac.



Rick



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

Bug#317727: installation-reports

[Rick Thomas]

On Jul 12, 2005, at 6:45 PM, Frans Pop wrote:


On Monday 11 July 2005 02:51, Josh wrote:


Aptitude works well, but when installing a package
after download, and it leaves the ncurses built
screen, it doesn't clear the terminal, which creates
garbage looking output.


That should be solvable, but I'm afraid I don't know how. You could try
asking on the debian-sparc or debian-user mail lists.


My guess on this is that the $TERM variable is set to something that's 
*almost* right.  Maybe the number of columns/rows is wrong?  the Sun 
console firmware doesn't emulate anything standard, like a VT1xx.


Rick



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

Bug#323182: debian-installer: boot.img for sarge doesn't, on PPC

[Rick Thomas]

It's clear that, as a practical matter, Apple doesn't mind if people 
distribute the "boot block which is coming directly from Apple and has 
a couple tens of m68k assembly instructions nobody could be bothered to 
reverse-engineer", because other Linux distributions provide it and 
Apple has not sued them.  So it would seem that the only thing keeping 
it out of the Debian/PPC distribution is the Debian Freeness 
guidelines.  I respect the guidelines, and wouldn't want to go against 
them, but it seems a shame that we can't find a practical solution to 
this.



Would it be possible to have an otherwise fully functioning boot floppy 
image minus the "non-free" part?  Then someone, while disclaiming all 
connection with Debian except as an interested observer, could put the 
"non-free" part on a website somewhere with instructions for combining 
the two into a functioning boot floppy?



Rick


PS: Sven makes it sound as if reverse engineering the boot block is a 
trivial bit of work.  That's not entirely true.  It's  only trivial if 
you happen to have the necessary coding and de-coding skills and the 
necessary background in calling Apple's OF boot-rom routines.  People 
with those skills are few and far between.   And acquiring them from 
scratch for this project is definitely non-trivial.  That's why I 
didn't volunteer.  I don't have the skills and I don't have the time to 
acquire them.


Maybe we should establish a bounty for someone to reverse-engineer the 
Apple floppy boot block.  That might get somebody with the necessary 
skills to come out of the woodwork...  If ten of us put up US$100, 
would that be enough?




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

Bug#403778: installation-report: sudo password not specified

[Rick Thomas]

On Dec 21, 2006, at 1:16 PM, Tshepang Lekhonkhobe wrote:


Anyways, I didn't know that one has access to man pages during
installation. Is that because I'm a newbie myself?


So far as I know (and I've been using and administering Linux  
machines for 10 years, and UNIX machines for 20 years before that)  
the man pages aren't available during installation.


Rick


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

Bug#404876: Acknowledgement ()

[Rick Thomas]

retitle 404876 gnome-desktop: strange behavior on OldWorld PowerMac  
"beige G3"


thanks


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

Bug#404876:

[Rick Thomas]

Package: gnome-desktop

I really don't know what package to file this bug report under.  If I  
make it to "installation-reports", FJP will just say, "The installer  
did everything right, so I'm closing this report." which seems a  
little like the surgeon who said, "The operation was as success.  Too  
bad, the patient died.  But that's not my problem!"


I'm picking "gnome-desktop" out of thin air, if only because I don't  
get this problem with KDE desktop manager.  Will somebody who knows,  
please redirect it to the correct place!


So here's my problem:

The computer in question is an OldWorld PowerMac Apple Macintosh,  
"Beige G3" tower.  This problem only happens on this machine.  It  
does not occur on my G4 test box.


I'd very much appreciate it if somebody else with a beige G3 would  
try it and let me know if they see the same problem.


I installed using the etch daily netinst CD from December 25th at  
04:40 UTC.


The installation process was entirely nominal (modulo the usual  
magical things I have to do to get it to load using BootX).


However, after rebooting following the install, and logging in to  
gnome, it seems to be repeatedly trying to start/re-start something  
having to do with the appearance of the desktop.  Things are very  
slow (as if a process in continually crashing and restarting) and the  
appearance of the desktop cycles thru a series of subtle but  
disturbing changes that I'll call "wiggling" for want of a better word.


Finally, after 30 seconds or a minute, I get a pop-up that says

Question
The pannel encountered a problem while loading
"OAFIID:GNOME_MixerApplet".

Do you want to delete the applet from your configuration?
[Don't delete]  [Delete]

If I click [Don't Delete] it goes back to wiggling, and about 30  
seconds later, I get the same popup.
If I click [Delete] it goes back to wiggling, but the popup doesn't  
reappear.


After a couple of minutes of wiggling, I get a popup that says

There was an error starting the GNOME Settings Daemon
	Some things such as themes, sounds, or background settings, may not  
work correctly.


The Settings Daemon restarted too many times

The last error message was:
System Exception:IDL:Bonobo/GeneralError:1.0:
Child process did not give an error message,
unknown failure occurred.

Gnome will try to restart the Settings Daemon next time you login.
[close]

When I click [close] the wiggling stops and everything is (as far as  
I can tell) normal until I log out

and try to login again.

Anybody got a clue?

Thanks!

Rick



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

Bug#404876:

[Rick Thomas]

On Dec 28, 2006, at 5:55 PM, Josselin Mouette wrote:


Le jeudi 28 décembre 2006 à 15:52 -0500, Rick Thomas a écrit :

However, after rebooting following the install, and logging in to
gnome, it seems to be repeatedly trying to start/re-start something
having to do with the appearance of the desktop.  Things are very
slow (as if a process in continually crashing and restarting) and the
appearance of the desktop cycles thru a series of subtle but
disturbing changes that I'll call "wiggling" for want of a better  
word.


Finally, after 30 seconds or a minute, I get a pop-up that says

Question
The pannel encountered a problem while loading
"OAFIID:GNOME_MixerApplet".

Do you want to delete the applet from your configuration?
[Don't delete]  [Delete]

If I click [Don't Delete] it goes back to wiggling, and about 30
seconds later, I get the same popup.
If I click [Delete] it goes back to wiggling, but the popup doesn't
reappear.

After a couple of minutes of wiggling, I get a popup that says

There was an error starting the GNOME Settings Daemon
Some things such as themes, sounds, or background settings, may not
work correctly.

The Settings Daemon restarted too many times

The last error message was:
System Exception:IDL:Bonobo/GeneralError:1.0:
Child process did not give an error message,
unknown failure occurred.

Gnome will try to restart the Settings Daemon next time you login.
[close]

When I click [close] the wiggling stops and everything is (as far as
I can tell) normal until I log out
and try to login again.


Could you try to update the liborbit2 and orbit2 packages to the
1:2.14.4-1 version in unstable, and then tell me if that bug is still
happening?


I changed "etch" to "unstable" in sources.list.  Then I did "aptitude  
update && aptitude install liborbit2 orbit2". It installed orbit2 and  
upgraded liborbit2 to version 1:2.14.4-1 and held back a whole bunch  
of stuff.  Then I logged out and back in again.  No change.  It still  
goes all wiggly on me and finally gives me the second error popup.   
(The first error popup isn't expected at this point -- I answered  
"Delete" the first time it came up a while ago and haven't seen it  
since.)


On an off chance, I rebooted the system.  Still no change.  Still all  
wiggly.




Enjoy!

Rick

Bug#404876:

[Rick Thomas]

On Dec 28, 2006, at 6:41 PM, Rick Thomas wrote:





Could you try to update the liborbit2 and orbit2 packages to the
1:2.14.4-1 version in unstable, and then tell me if that bug is still
happening?


I changed "etch" to "unstable" in sources.list.  Then I did  
"aptitude update && aptitude install liborbit2 orbit2". It  
installed orbit2 and upgraded liborbit2 to version 1:2.14.4-1 and  
held back a whole bunch of stuff.  Then I logged out and back in  
again.  No change.  It still goes all wiggly on me and finally  
gives me the second error popup.  (The first error popup isn't  
expected at this point -- I answered "Delete" the first time it  
came up a while ago and haven't seen it since.)


On an off chance, I rebooted the system.  Still no change.  Still  
all wiggly.


Interesting difference -- Now it stays wiggly forever (well -- for 5  
minutes or more).  I never actually see the error popup, and the  
wiggles never go away.


Rick



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

Bug#404876:

[Rick Thomas]

On Dec 28, 2006, at 6:58 PM, Josselin Mouette wrote:


Le jeudi 28 décembre 2006 à 18:55 -0500, Rick Thomas a écrit :

I changed "etch" to "unstable" in sources.list.  Then I did
"aptitude update && aptitude install liborbit2 orbit2". It
installed orbit2 and upgraded liborbit2 to version 1:2.14.4-1 and
held back a whole bunch of stuff.  Then I logged out and back in
again.  No change.  It still goes all wiggly on me and finally
gives me the second error popup.  (The first error popup isn't
expected at this point -- I answered "Delete" the first time it
came up a while ago and haven't seen it since.)

On an off chance, I rebooted the system.  Still no change.  Still
all wiggly.


Interesting difference -- Now it stays wiggly forever (well -- for 5
minutes or more).  I never actually see the error popup, and the
wiggles never go away.


Looks like gnome-settings-daemon is dying again and again.


Yes.  I can confirm that repeated "ps" gives different pids each time  
for gnome-settings-daemon .




Is there any relevant output in your ~/.xsession-errors file ?



it looks like this:


Xsession: X session started for rick at Thu Dec 28 18:45:08 EST 2006
SESSION_MANAGER=local/debian:/tmp/.ICE-unix/3460
Gnome-Message: gnome_execute_async_with_env_fds: returning -1
Unable to open desktop file epiphany.desktop for panel launcher


Does that help?

Rick

Bug#404876:

[Rick Thomas]

On Dec 28, 2006, at 7:07 PM, Josselin Mouette wrote:


Le jeudi 28 décembre 2006 à 18:55 -0500, Rick Thomas a écrit :

On an off chance, I rebooted the system.  Still no change.  Still
all wiggly.


Interesting difference -- Now it stays wiggly forever (well -- for 5
minutes or more).  I never actually see the error popup, and the
wiggles never go away.


Can you type "echo export OIL_CPU_FLAGS=0 >> ~/.gnomerc" and then  
try to

log out and log in again?



This did not change anything.  What was it supposed to do?




If it doesn't work, please start a fail-safe session, and in the
terminal type "gdb /usr/bin/gnome-settings-daemon", and at the gdb
prompt "run". If it crashes, type "thread apply all bt" and send me  
the

output.


typescript attached.




typescript
Description: Binary data


Hope it helps!

Rick

Bug#404876:

[Rick Thomas]

On Dec 29, 2006, at 4:42 AM, Josselin Mouette wrote:



Well, nothing really useful here, except this confirms this is a  
problem

somewhere in the GStreamer stack. Reassigning.

@debian-powerpc: as it seem to render gstreamer completely useless  
on G3
processors, I think this must be addressed before the release. If  
anyone

with powerpc knowledge has some time to find what is going wrong, that
would be very helpful.


Thanks for you help!

Is there a (set of) configuration parameter(s) I can fiddle with that  
will disable (selected parts of) gstreamer?  That might help to  
narrow the scope of the question.  As noted elsewhere, I'm an old- 
fashioned command-line kinda guy and all this multi-media stuff is  
just so much glitz as far as I'm concerned. So disabling the  
troublesome parts (or the whole thing) is acceptable to me.   
Especially if it lets me get on with other testing activities on the  
OldWorld machine.


I'm (of course) willing and anxious to help get this thing debugged.   
The machine in question is dedicated to Debian testing, so feel free  
to ask me to try anything that you think might help in diagnosing the  
problem.


Rick



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

Bug#404876: Fwd: Problems with GNOME on Beige G3

[Rick Thomas]

Begin forwarded message:


Resent-From: debian-powerpc@lists.debian.org
From: Yavor Doganov <[EMAIL PROTECTED]>
Date: December 29, 2006 1:47:46 PM EST
To: debian-powerpc@lists.debian.org
Cc: debian-user@lists.debian.org
Subject: Re: Problems with GNOME on Beige G3

Rick Thomas wrote:


The computer in question is an OldWorld PowerMac Apple Macintosh,
"Beige G3" tower.  This problem only happens on this machine.  It
does not occur on my G4 test box.


I have a Beige G3 "Gossamer", not a tower, but it's practically the
same.


I'd very much appreciate it if somebody else with a beige G3 would
try it and let me know if they see the same problem.


I noticed the same behaviour a few months ago.  As I generally run
Window Maker/GNUstep on that machine, I just ignored that as I thought
there is something broken in my configuration.  I'll try to find out
what's wrong, but that won't happen in the forthcoming weeks.

Apparently this has nothing to do with the installation CDs, as my
machine has been running Debian for ages.  One thing you could do, as
a startup, is to attach gdb to that applet and see what's crashing
it.  That might give you a clue where to investigate further.




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

Bug#404876: Output of gst-launch

[Rick Thomas]

On Dec 30, 2006, at 2:23 AM, Yavor Doganov wrote:


On Fri, Dec 29, 2006 at 02:45:14PM -0800, David Schleef wrote:

Could you run:

  rm ~/.gstreamer-0.10/registry.*.xml
  GST_DEBUG=*:3 gst-launch --gst-debug-no-color

and attach the output?


Attached is the output produced on my machine running unstable.




Interesting.  I'm not getting the mail from David Schleef, but I am  
getting the replies from Yavor Doganov.


David, would you like me to try the same things on my Beige G3 under  
Etch?


Rick


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

Bug#404876: Re:

[Rick Thomas]

On Dec 30, 2006, at 8:11 PM, Paul Mackerras wrote:


Rick Thomas writes:


However, after rebooting following the install, and logging in to
gnome, it seems to be repeatedly trying to start/re-start something
having to do with the appearance of the desktop.  Things are very
slow (as if a process in continually crashing and restarting) and the
appearance of the desktop cycles thru a series of subtle but
disturbing changes that I'll call "wiggling" for want of a better  
word.


I have seen behaviour more or less like this when the clock was set
wrongly, i.e. to 1904 or something, so check that the clock setting is
reasonable.  (I have no idea why a bogus clock setting upsets gnome so
much.)

Paul.


A good thought.  Unfortunately, the date & time are correct on this  
machine.


I just did "aptitude update && aptitude upgrade" and it installed  
newer versions of lots of gnome related stuff.  But no joy.  The  
wiggles haven't gone away.


Still hoping that somebody can help me debug this thing!

Rick



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

Bug#404876: Quick G3 Wiggly Gnome Fix

[Rick Thomas]

On Dec 31, 2006, at 12:37 PM, b9 wrote:


I've created a quick hack fix for the Wiggly Gnome Bug. This is not a
good fix as it doesn't address *why* the problem occurred or prevent
it from occurring again. However, it's good enough for me to get work
done on my G3 iMac, and I figured you might find it useful until the
bug is properly squashed.

You can compile your own libgstreamer or download the one that I  
posted:


http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404876#msg98

--Ben


I've got two machines, sitting side by side.  One is the Beige G3  
PowerMac that started all this.  The other is a G4 Powermac.  They  
are both running up-to-date Debian etch.  Both are configured for the  
GNOME desktop manager.


I did the series of magical passes described in the message b9  
pointed to on each of them.   The wigglys on the G3 are now gone.   
Hurrah!



I've done enough messing around on the G3 that I don't trust the  
config files to be meaningful, so I'm not going to send them yet.


I'll do a complete re-install from scratch on the G3 then do b9's  
magic again.  I'll send the config files from that one.


Enjoy!

Rick



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

Bug#404876: PowerMac beige G3 - test of [Re: G3 (or other non-altivec machines) testers sought]

[Rick Thomas]

On Jan 14, 2007, at 5:08 PM, Sjoerd Simons wrote:


The best hint to what the problem might be seems to indicate there is
  an issue in the libvisual altivec detection code[0]..


I installed on my "beige G3" PowerMac (OldWorld) test machine.  I  
used the latest d-i netinst CD dated 2007 Jan 21 09:10:17 UTC,  
downloaded from http://cdimage.debian.org/cdimage/daily-builds/sid_d- 
i/20070121-1/powerpc/iso-cd/


I did a default install.  When it came to running "tasksel" I chose  
the "desktop" and "standard" tasks.  It installed everything pretty  
much as expected except that it wound up in a red screen saying:


[!!] Configure gnome-applets
Installation step failed
An installation step failed.
The failing step is: Select and install software.

I continued anyway and allowed it to reboot, which went pretty much  
as expected.


After the reboot, I tried to log into Gnome.  It behaved as described  
in bug#404876 (popup telling of a problem loading  
"OAFID:GNOME_MixerApplet", and the screen went all wiggly.)


I then followed Sjoerd's instructions for testing.

0: Install gstreamer
no problem.

1: rm ~/.gstreamer-0.10/registry.*.xml
That directory didn't exist.  So there was nothing to remove.

   gst-launch-0.10 --gst-disable-registry-fork
crashed with "illegal instruction"

2b: installed the kernel from SID.
gst-launch... still gave "illegal instruction"

downloaded and installed libvisual-0.4-0_0.4.0-1.0.1_powerpc.deb  
from sjoerd's directory.
	got "ERROR: pipeline could not be constructed: empty pipeline not  
allowed."

I assume this is the "right" answer?

Then I logged out and logged back in again to Gnome.  No more  
wiggles.  So that fixes the problem, whatever it was.


Congratulations!

Rick




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

Bug#402547: debian-installer: OldWorld beige G3 Macintosh bmac network interface disabled on reboot

[Rick Thomas]

On Dec 11, 2006, at 2:08 PM, Frans Pop wrote:


On Monday 11 December 2006 09:26, Rick Thomas wrote:
After installing etch from a daily netinst CD (2006/12/10 20:42  
UTC) on
my beige G3 (OldWorld) PowerMac machine, the builtin ethernet  
interface

is disabled.

[...]

There is a strange and possibly relevant thing in syslog

Dec 11 02:34:47 debian NetworkManager: ^Ieth1: Driver
'bmac' does not support carrier detection. ^IYou must switch to it
manually.


So during the installation everything worked OK?



Except for the mentioned problem with the bmac network interface,  
everything was pretty much as expected[*].  I boot this machine with  
the BootX bootloader.  Up to now, etch has not worked with BootX.   
This is the first time it has been possible to do that since debian  
changed to >2.6.15 kernels. If we can get this bug fixed, I'll write  
up the full procedure step-by-step for the wiki.  If this can't get  
fixed (or worked around) in time for etch release, it raises the  
question of whether or not to say that OldWorld PowerMacs are fully  
supported in this release.  I'll leave that decision up to the  
release manager -- I'm just raising the question.


[*] I had to use video=ofonly to get decent video.  With sarge, I  
used to be able to use video=atyfb... but with this kernel, that gave  
a strange "almost readable" shimmery screen.  I also had to  
explicitly state "root=/dev/hde9" in the kernel parameters.  This  
again was new from sarge.  In sarge, I don't need to make that explicit.


I'll do a full installation report if you think it would be useful.

I'm also planning to do an installation from the businesscard CD.   
I'll do a full report on that if there's anything interesting.



In that case I have no idea what to do with this report, especially if
something like networkmanager is involved.
As the initial dhcp setup seems to go fine (which means that eth1 was
working at that point), I suspect that your problem is  
networkmanager's

fault, or maybe a configuration issue.

Joey: does this impact your decision to install networkmanager by  
default?


The initial DHCP during the installation went fine -- I was able to  
retrieve lots of packages over the net during the "tasksel" part of  
the installation.  It's just after rebooting into the installed  
system that the problem manifests.  I'm not completely sure, but I  
*think* from looking at the log files, that the interface comes up  
and succeeds in doing DHCP early in the boot process, then is killed  
later on, possibly by Networkmanager?


Would it be helpful to see what happens if I physically remove the  
extra ethernet card?  Or if I install using the extra card instead of  
the bmac?


Rick



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

Bug#402547: debian-installer: OldWorld beige G3 Macintosh bmac network interface disabled on reboot

[Rick Thomas]

On Dec 11, 2006, at 4:31 PM, Joey Hess wrote:


Frans Pop wrote:
Joey: does this impact your decision to install networkmanager by  
default?


It's a data point.

I'd imagine that one can get networkmanager to deal with the interface
by prodding it in the gui though.

--
see shy jo



In interesting image... (<-8)  Can you be a little more specific  
about how to go about doing this?


Thanks!

Rick


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

Bug#402547: debian-installer: OldWorld beige G3 Macintosh bmac network interface disabled on reboot

[Rick Thomas]

On Dec 11, 2006, at 5:39 PM, Joey Hess wrote:


Rick Thomas wrote:

In interesting image... (<-8)  Can you be a little more specific
about how to go about doing this?


If networkmanager is running I assume you are logged into a desktop
environment that has some kind of netowork manager applet (in the  
status

notification area in gnome for example). That applet can be used to
configure it and make it use particular interfaces.



Well, actually right now I'm logged in remotely via ssh -- the  
machine's at home and I'm at work.  Last night, after booting, from  
the console, I ran "ifdown eth1 ; ifup eth1" and it brought things  
back to normal.  So ssh-ing in is possible -- until the next reboot.


Given that (which may alter the results) "nm-tool" says:


[EMAIL PROTECTED]:~$ nm-tool

NetworkManager Tool

State: disconnected

- Device: eth0  


  NM Path:   /org/freedesktop/NetworkManager/Devices/eth0
  Type:  Wired
  Driver:8139too
  Active:no
  HW Address:00:40:05:35:EF:FF

  Capabilities:
Supported:   yes
Carrier Detect:  yes
Speed:   10 Mb/s

  Wired Settings
Hardware Link:   no


- Device: eth1  


  NM Path:   /org/freedesktop/NetworkManager/Devices/eth1
  Type:  Wired
  Driver:bmac
  Active:no
  HW Address:00:05:02:FE:55:50

  Capabilities:
Supported:   yes

  Wired Settings
Hardware Link:   yes


[EMAIL PROTECTED]:~$



When I do "man NetworkManager" I get a fairly skeletal man page that  
doesn't mention a gui.  Similarly for "man  
NetworkManagerDispatcher".  Those two, and nm-tool, are all I get out  
of "man -k NetworkManager".  Is there anything more in the way of  
documentation I can look at?


Should I be opening a bug report against networkmanager?

Thanks!


Rick



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

Bug#402547: NetworkManager: Workaround for "OldWorld beige G3 Macintosh bmac network interface disabled on reboot"

[Rick Thomas]

Package: networkmanager

See bug number 402547 (originally filed against debian-installer) for  
previous discussion.


The problem does seem to be that NetworkManager doesn't know what to  
do with the bmac interface, because it doesn't have carrier detect,  
so NetworkManager can't tell when it's up or down.


One workaround (I've tried this and it works) is to declare the  
interface to be "static" and assign it a permanent IP address,  
netmask, etc...  You can do this at install time (hit the "cancel"  
button when the installer is trying to get its address from the LAN  
DHCP server, then enter the static parameters.)  Or you can do it  
after install by adding the appropriate stanza to the /etc/network/ 
interfaces file.  There are probably more sophisticated things you  
can do that will allow you to keep using dhcp without involving (and  
confusing) networkmanager, but I haven't tried them.


This will prevent NetworkManager from messing with the interface.

See "man 5 interfaces" and /usr/share/doc/network-manager for details.

In an ideal world, the NetworkManager would recognize the bmac as  
being hardwired and not disable it, but that may be more difficult  
than it sounds.


Rick



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

Bug#402547: Further details at Bug#403112

[Rick Thomas]

Further details at  Bug#403112




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

Bug#403112: NetworkManager: Workaround for "OldWorld beige G3 Macintosh bmac network interface disabled on reboot"

[Rick Thomas]

On Dec 14, 2006, at 5:05 PM, Michael Biebl wrote:


Debian Bug Tracking System wrote:

Processing commands for [EMAIL PROTECTED]:


reassign 403112 network-manager
Bug#403112: NetworkManager: Workaround for "OldWorld beige G3  
Macintosh bmac network interface  disabled on reboot"

Warning: Unknown package 'networkmanager'
Bug reassigned from package `networkmanager' to `network-manager'.



So what exactly is the problem now, regarding network-manager?
If your driver is broken, the driver should be fixed.
If you setup a static configuration in /etc/network/interfaces,
network-manager will not touch your network settings (as it can't deal
with static configurations yet. NM 0.7.x is supposed to bring support
for that).
Could you elaborate a bit more?


I don't think it's the driver that's broken.  I believe the chip is  
incapable of a feature that NetworkManager wants.


The OldWorld PowerMac (a "Beige G3") machine (that I use for test  
installing Debian Etch) has a "bmac" 10-baseT ethernet controller on  
the motherboard, of a type that is apparently fairly common on  
OldWorld PowerMac machines, of which Apple made many varieties over  
the years.


Apparently, the bmac is not able to do some of the fancy tricks that  
more modern network interface chips are capable of, such as telling  
the software whether it is seeing a carrier or not.  This leads the  
NetworkManager to declare:


Dec 11 02:34:47 debian NetworkManager: ^Ieth1: Driver  
'bmac' does not support carrier detection. ^IYou must switch to it  
manually.
Dec 11 02:34:47 debian NetworkManager: ^Inm_device_init 
(): waiting for device's worker thread to start
Dec 11 02:34:47 debian NetworkManager: ^Inm_device_init 
(): device's worker thread started, continuing.
Dec 11 02:34:47 debian NetworkManager: ^INow managing  
wired Ethernet (802.3) device 'eth1'.
Dec 11 02:34:47 debian NetworkManager: ^IDeactivating  
device eth1.


Ooops!  This leaves the machine with no way to talk to the network  
even though I used that very same interface extensively and  
successfully when I installed the OS just a few minutes before.


A work-around is to declare the bmac interface to be active and  
static, which makes NetworkManager leave it alone.  However, if I  
read your comments correctly, as of NM 0.7.x, even that may not be  
enough.


There are lots more details (many of them probably irrelevant) in the  
referenced bug report at http://bugs.debian.org/cgi-bin/bugreport.cgi? 
bug=402547 which I submitted against the debian-installer before I  
realized where the real problem lies.



Does this help?

Thanks!

Rick



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

Bug#402547: Processed: Re: Bug#403112: NetworkManager: Workaround for "OldWorld beige G3 Macintosh bmac network interface disabled on reboot"

[Rick Thomas]

On Dec 14, 2006, at 5:05 PM, Michael Biebl wrote:


Debian Bug Tracking System wrote:

Processing commands for [EMAIL PROTECTED]:


reassign 403112 network-manager
Bug#403112: NetworkManager: Workaround for "OldWorld beige G3  
Macintosh bmac network interface  disabled on reboot"

Warning: Unknown package 'networkmanager'
Bug reassigned from package `networkmanager' to `network-manager'.



So what exactly is the problem now, regarding network-manager?
If your driver is broken, the driver should be fixed.
If you setup a static configuration in /etc/network/interfaces,
network-manager will not touch your network settings (as it can't deal
with static configurations yet. NM 0.7.x is supposed to bring support
for that).
Could you elaborate a bit more?


I don't think it's the driver that's broken.  I believe the chip is  
incapable of a feature that NetworkManager wants.


The OldWorld PowerMac (a "Beige G3") machine (that I use for test  
installing Debian Etch) has a "bmac" 10-baseT ethernet controller on  
the motherboard, of a type that is apparently fairly common on  
OldWorld PowerMac machines, of which Apple made many varieties over  
the years.


Apparently, the bmac is not able to do some of the fancy tricks that  
more modern network interface chips are capable of, such as telling  
the software whether it is seeing a carrier or not.  This leads the  
NetworkManager to declare:


Dec 11 02:34:47 debian NetworkManager: ^Ieth1: Driver  
'bmac' does not support carrier detection. ^IYou must switch to it  
manually.
Dec 11 02:34:47 debian NetworkManager: ^Inm_device_init 
(): waiting for device's worker thread to start
Dec 11 02:34:47 debian NetworkManager: ^Inm_device_init 
(): device's worker thread started, continuing.
Dec 11 02:34:47 debian NetworkManager: ^INow managing  
wired Ethernet (802.3) device 'eth1'.
Dec 11 02:34:47 debian NetworkManager: ^IDeactivating  
device eth1.


Ooops!  This leaves the machine with no way to talk to the network  
even though I used that very same interface extensively and  
successfully when I installed the OS just a few minutes before.


A work-around is to declare the bmac interface to be active and  
static, which makes NetworkManager leave it alone.  However, if I  
read your comments correctly, as of NM 0.7.x, even that may not be  
enough.


There are lots more details (many of them probably irrelevant) in the  
referenced bug report at http://bugs.debian.org/cgi-bin/bugreport.cgi? 
bug=402547 which I submitted against the debian-installer before I  
realized where the real problem lies.



Does this help?

Thanks!

Rick



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

Bug#403112: Processed: Re: Bug#403112: NetworkManager: Workaround for "OldWorld beige G3 Macintosh bmac network interface disabled on reboot"

[Rick Thomas]

On Dec 14, 2006, at 7:07 PM, Michael Biebl wrote:

Could you please send me the version of network-manager and attach  
your

/etc/network/interfaces.



Here's the interfaces file that works for me now.  It's based on what  
the installer creates when I tell it not to use DHCP during the  
initial network discovery phase of the install.



debian:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth1
iface eth1 inet static
address 192.168.1.188
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.254
# dns-* options are implemented by the resolvconf package,  
if installed

dns-nameservers 192.168.1.118 192.168.1.138 192.168.1.254
dns-search rcthomas.org rutgers.edu



Here's the interfaces file as I received it from the debian-installer.


debian:~# cat /etc/network/interfaces.ORIG
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth1
iface eth1 inet dhcp



And here's the skinny on the network-manager package.



debian:~# aptitude show network-manager
Package: network-manager
State: installed
Automatically installed: yes
Version: 0.6.4-6
Priority: optional
Section: net
Maintainer: Riccardo Setti <[EMAIL PROTECTED]>
Uncompressed Size: 623k
Depends: libc6 (>= 2.3.5-1), libdbus-1-3 (>= 0.94), libdbus- 
glib-1-2 (>= 0.71), libgcrypt11 (>= 1.2.2),
 libglib2.0-0 (>= 2.12.0), libgpg-error0 (>= 1.4), libhal1  
(>= 0.5), libiw28 (>= 28), libnl1-pre6,
 libnm-util0, iproute, iputils-arping, dhcdbd (>= 1.12-2),  
lsb-base (>= 2.0-6), wpasupplicant (>=

 0.4.8), dbus (>= 0.60), hal (>= 0.5.7.1), ifupdown, adduser
Description: network management framework daemon
NetworkManager attempts to keep an active network connection  
available at all times. It is intended only
for the desktop use-case, and is not intended for usage on servers.  
The point of NetworkManager is to make
networking configuration and setup as painless and automatic as  
possible.  If using DHCP, NetworkManager i
_intended_ to replace default routes, obtain IP addresses from a  
DHCP server, and change nameservers

whenever it sees fit.
This package provides the userspace daemons.
Homepage: http://www.gnome.org/projects/NetworkManager/

Tags: role::program



Hope it helps!

Rick

PS: This machine is dedicated to testing Debian and the debian- 
installer.  It has no other purpose.  So feel free to ask me to try  
anything (non-destructive) on it.





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

Bug#372070: Just tried it on a PPC system

[Rick Thomas]

fgfs seems to work more or less as expected on my PowerMac G4 533MHz  
with 1.5 Gbyte of RAM.


It was very slow, but I think that's likely to be the relatively  
underpowered CPU and graphics card I have.  CPU usage went up to 90%  
and stayed there.  Most of that was fgfs.


Here's some stats

[EMAIL PROTECTED]:~$ cat /proc/cpuinfo
processor   : 0
cpu : 7410, altivec supported
temperature : 35-37 C (uncalibrated)
clock   : 533.32MHz
revision: 0.3 (pvr 800c 1103)
bogomips: 66.30
timebase: 33290001
platform: PowerMac
machine : PowerMac3,4
motherboard : PowerMac3,4 MacRISC2 MacRISC Power Macintosh
detected as : 69 (PowerMac G4 Silver)
pmac flags  : 0010
L2 cache: 1024K unified
pmac-generation : NewWorld
[EMAIL PROTECTED]:~$ cat /proc/meminfo
MemTotal:  1551904 kB
MemFree:493044 kB
Buffers:118184 kB
Cached: 758028 kB
SwapCached:  0 kB
Active: 588812 kB
Inactive:   376536 kB
HighTotal:  786432 kB
HighFree:19792 kB
LowTotal:   765472 kB
LowFree:473252 kB
SwapTotal: 2148428 kB
SwapFree:  2148428 kB
Dirty: 264 kB
Writeback:   0 kB
AnonPages:   89152 kB
Mapped:  36780 kB
Slab:75824 kB
PageTables:   1904 kB
NFS_Unstable:0 kB
Bounce:  0 kB
CommitLimit:   2924380 kB
Committed_AS:   182904 kB
VmallocTotal:   186788 kB
VmallocUsed: 31016 kB
VmallocChunk:   153504 kB
[EMAIL PROTECTED]:~$

The above was on an idle system.

Here's a meminfo with fgfs running.

[EMAIL PROTECTED]:~$ cat /proc/meminfo
MemTotal:  1551904 kB
MemFree:231348 kB
Buffers:118348 kB
Cached: 758060 kB
SwapCached:  0 kB
Active: 849808 kB
Inactive:   376476 kB
HighTotal:  786432 kB
HighFree: 1316 kB
LowTotal:   765472 kB
LowFree:230032 kB
SwapTotal: 2148428 kB
SwapFree:  2148428 kB
Dirty:  88 kB
Writeback:   0 kB
AnonPages:  349892 kB
Mapped:  45360 kB
Slab:75924 kB
PageTables:   2276 kB
NFS_Unstable:0 kB
Bounce:  0 kB
CommitLimit:   2924380 kB
Committed_AS:   592172 kB
VmallocTotal:   186788 kB
VmallocUsed: 31016 kB
VmallocChunk:   153504 kB
[EMAIL PROTECTED]:~$

So it's not swapping with 1.5 Gig of RAM.  I don't find that surprising.

Rick



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

Bug#397649: install-report: NTP sync missing by default

[Rick Thomas]

On Nov 11, 2006, at 5:24 PM, Geert Stappers wrote:


Op 08-11-2006 om 20:09 schreef Olaf van der Spek:


Also, no NTP synchronization is available by default.
I really think Debian should install.
Maybe install but disable, although I'd prefer it to be enabled by  
default.


The Debian-installer installs by default the packages
with priority "standard".


Cheers
Geert Stappers
Who thinks it is stupid to install NTP by default.


Installing ntp by default (making it have priority "standard") would  
be good for the many Debian users who have always-on network access.   
But it would be a problem for the minority who have no or only  
intermittent (e.g. dial-up) network access.


An argument in favor of making it "standard" is that it would greatly  
improve the overall state of timekeeping on the internet.  This is of  
not just a "time-geek" issue.  Better time distribution has lots of  
practical advantages.


An argument in favor of leaving it optional is that requiring people  
without good network access to install in "expert" mode (to avoid  
getting ntp installed) is an imposition on a class of users who are  
individually more likely to be non-experts.


I leave it to the PTBs to figure out whether there is a compromise  
position.


Rick



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

Bug#402267: PowerPC Netinst CD "Invalid Release File"

[Rick Thomas]

Package: installation-reports

Installing from the netinst CD on a PowerMac G4, I get the following  
error:


[!!] Install the base system
Debootstrap Error
Invalid Release file: no entry for main/binary-powerpc/Packages.

This is the netinst CD from:

cdimage.debian.org:cdimage/daily-builds/sid_d-i/20061208-1/powerpc/ 
iso-cd


Trying 130.239.18.138...
-rw-r--r--1 1002 1002  143 Dec 08 10:34 MD5SUMS
-rw-r--r--1 1002 1002 73390080 Dec 08 10:32 debian- 
testing-powerpc-businesscard.iso
-rw-r--r--1 1002 1002   251055 Dec 08 10:32 debian- 
testing-powerpc-businesscard.iso.zsync
-rw-r--r--1 1002 1002 192720896 Dec 08 10:34 debian- 
testing-powerpc-netinst.iso
-rw-r--r--1 1002 1002   329558 Dec 08 10:34 debian- 
testing-powerpc-netinst.iso.zsync


cdimage.debian.org is an alias for ftp.acc.umu.se.
ftp.acc.umu.se has address 130.239.18.159
ftp.acc.umu.se has address 130.239.18.138
ftp.acc.umu.se has address 130.239.18.158




Curiously enough, if I use the Businesscard CD, I do not get this error.

Any thoughts?

Rick



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

Bug#402267: More info

[Rick Thomas]

Curiously enough, the netinst CD does appear to have the missing file...


$ ls -l dists/etch/main/binary-powerpc/
total 688
-rwxr-xr-x   1 rbthomas  rbthomas  209980 Dec  8 10:33 Packages
-rwxr-xr-x   1 rbthomas  rbthomas  131702 Dec  8 10:33 Packages.gz
-rwxr-xr-x   1 rbthomas  rbthomas  84 Dec  8 10:33 Release





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

Bug#402267: Not just powerpc -- x86 too [Re: Bug#402267: PowerPC Netinst CD "Invalid Release File"]

[Rick Thomas]

On Dec 9, 2006, at 1:01 AM, Rick Thomas wrote:


Package: installation-reports

Installing from the netinst CD on a PowerMac G4, I get the  
following error:


[!!] Install the base system
Debootstrap Error
Invalid Release file: no entry for main/binary-powerpc/Packages.

This is the netinst CD from:

cdimage.debian.org:cdimage/daily-builds/sid_d-i/20061208-1/powerpc/ 
iso-cd




Hmmm  Bug#401586  seems to indicate that this may not be limited  
to the powerpc port.  Bug#401586 is for x86.


Rick



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

Bug#402267: More info

[Rick Thomas]

On Dec 9, 2006, at 12:15 PM, Frans Pop wrote:


Hi Rick,

On Saturday 09 December 2006 07:49, Rick Thomas wrote:

Curiously enough, the netinst CD does appear to have the missing
file...


Seems to me like the message is not about the presence of the file  
itself

but rather that it is not listed _inside_ the file
/cdrom/dists/etch/Release.

Could you send us that file?



Here it is...

Presumably, the equivalent file on a "businesscard" install is coming  
from the mirror, not the CD?  So you're not interested in what's on  
the businesscard CD in that place?  Please let me know if you need  
that too.


For what it's worth, this also happened about a week ago, but I  
figured it was a transient error and didn't report it then.  I've  
been out of town for the intervening time.  But now I'm back and  
ready to pursue the issue.  Etch obviously can't release until this  
is diagnosed and fixed.





Release
Description: Binary data


Rick

Bug#402267: PowerPC Netinst CD "Invalid Release File"

[Rick Thomas]

On Dec 9, 2006, at 5:16 PM, Frans Pop wrote:


Hmmm  Bug#401586  seems to indicate that this may not be limited
to the powerpc port.  Bug#401586 is for x86.


Not sure what you see in that report that makes you say that. I  
only see

unrelated issues.


Well... the first few lines of this email...



Resent-From:  [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Subject:Bug#401586: same problem
Date:   December 9, 2006 1:41:15 PM EST
Resent-To:debian-bugs-dist@lists.debian.org
To:   [EMAIL PROTECTED]
Resent-Cc:debian-boot@lists.debian.org
Reply-To: [EMAIL PROTECTED], [EMAIL PROTECTED]

After the daily built i386 netinst CD couldn't find
main/binary-i386/Packages on the CD (it was there!!!), i sent an
installation report (#402219), and the next day (today) tried the  
daily

built i386 businesscard CD
(http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/ 
i386/iso-cd/debian-testing-i386-businesscard.iso).

The installation was successful





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

Bug#402547: debian-installer: OldWorld beige G3 Macintosh bmac network interface disabled on reboot

[Rick Thomas]

Package: debian-installer
Severity: normal


After installing etch from a daily netinst CD (2006/12/10 20:42 UTC) on my 
beige G3 (OldWorld) PowerMac machine, the 
builtin ethernet interface is disabled.  This box has two ethernet interfaces:

eth0: D-Link RTL8139
eth1: builtin "bmac" on the motherboard

eth0 is not connected to anything (for the time being).
eth1 is connected to the local ethernet.

doing
ifdown eth1
ifup eth1
restores things to normal.

There is a strange and possibly relevant thing in syslog

Dec 11 02:34:47 debian NetworkManager: ^Ieth1: Driver 'bmac' does 
not support carrier detection. ^IYou must switch to it manually. 


Here's the output of "lspci -nn"

00:00.0 Host bridge [0600]: Motorola MPC106 [Grackle] [1057:0002] (rev 40)
00:0d.0 Ethernet controller [0200]: D-Link System Inc RTL8139 Ethernet 
[1186:1300] (rev 10)
00:0e.0 SCSI storage controller [0100]: Artop Electronic Corp ATP865 
[1191:0009] (rev 06)
00:0f.0 PCI bridge [0604]: Hint Corp HB6 Universal PCI-PCI bridge 
(non-transparent mode) [3388:0021] (rev 13)
00:10.0 Unknown class [ff00]: Apple Computer Inc. Heathrow Mac I/O [106b:0010] 
(rev 01)
00:12.0 VGA compatible controller [0300]: ATI Technologies Inc 3D Rage I/II 
215GT [Mach64 GT] [1002:4754] (rev 9a)
01:08.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 41)
01:08.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 41)
01:08.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 02)
01:0b.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB12LV26 IEEE-1394 
Controller (Link) [104c:8020]



Here's the output of "grep -i -C 10 eth /var/log/syslog.0

Dec 11 02:34:35 debian syslogd 1.4.1#18: restart.
Dec 11 02:34:36 debian dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 
67 interval 6
Dec 11 02:34:36 debian dhclient: DHCPOFFER from 192.168.1.138
Dec 11 02:34:36 debian dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
Dec 11 02:34:36 debian dhclient: DHCPACK from 192.168.1.138
Dec 11 02:34:36 debian dhclient: bound to 192.168.1.188 -- renewal in 8564 
seconds.
Dec 11 02:34:36 debian kernel: klogd 1.4.1#18, log source = /proc/kmsg started.
Dec 11 02:34:36 debian kernel: Using PowerMac machine description
Dec 11 02:34:36 debian kernel: Total memory = 384MB; using 1024kB for hash 
table (at cff0)
Dec 11 02:34:36 debian kernel: Linux version 2.6.18-3-powerpc (Debian 2.6.18-7) 
([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) 
#1 Mon Dec 4 15:30:06 CET 2006
Dec 11 02:34:36 debian kernel: Found initrd at 0xc0377000:0xc0890cf4
Dec 11 02:34:36 debian kernel: Found a Heathrow mac-io controller, rev: 1, 
mapped at 0xfdf8
Dec 11 02:34:36 debian kernel: PowerMac motherboard: PowerMac G3 (Gossamer)
Dec 11 02:34:36 debian kernel: Found Grackle (MPC106) PCI host bridge at 
0x8000. Firmware bus number: 0->1
--
Dec 11 02:34:36 debian kernel: NET: Registered protocol family 1
Dec 11 02:34:36 debian kernel: NET: Registered protocol family 17
Dec 11 02:34:36 debian kernel: Freeing unused kernel memory: 180k init
Dec 11 02:34:36 debian kernel: usbcore: registered new driver usbfs
Dec 11 02:34:36 debian kernel: usbcore: registered new driver hub
Dec 11 02:34:36 debian kernel: ohci_hcd: 2005 April 22 USB 1.1 'Open' Host 
Controller (OHCI) Driver (PCI)
Dec 11 02:34:36 debian kernel: PCI: Enabling device :01:08.0 (0014 -> 0016)
Dec 11 02:34:36 debian kernel: ohci_hcd :01:08.0: OHCI Host Controller
Dec 11 02:34:36 debian kernel: ohci_hcd :01:08.0: new USB bus registered, 
assigned bus number 1
Dec 11 02:34:36 debian kernel: ohci_hcd :01:08.0: irq 18, io mem 0x81803000
Dec 11 02:34:36 debian kernel: 8139too Fast Ethernet driver 0.9.27
Dec 11 02:34:36 debian kernel: PCI: Enabling device :00:0d.0 (0004 -> 0007)
Dec 11 02:34:36 debian kernel: eth0: RealTek RTL8139 at 0x1000, 
00:40:05:35:ef:ff, IRQ 23
Dec 11 02:34:36 debian kernel: eth0:  Identified 8139 chip type 
'RTL-8100B/8139D'
Dec 11 02:34:36 debian kernel: ieee1394: Initialized config rom entry `ip1394'
Dec 11 02:34:36 debian kernel: SCSI subsystem initialized
Dec 11 02:34:36 debian kernel: eth1: BMAC at 00:05:02:fe:55:50
Dec 11 02:34:36 debian kernel: usb usb1: configuration #1 chosen from 1 choice
Dec 11 02:34:36 debian kernel: hub 1-0:1.0: USB hub found
Dec 11 02:34:36 debian kernel: hub 1-0:1.0: 3 ports detected
Dec 11 02:34:36 debian kernel: mesh: configured for synchronous 5 MB/s
Dec 11 02:34:36 debian kernel: hda: ATAPI 24X CD-ROM drive, 128kB Cache, DMA
Dec 11 02:34:36 debian kernel: Uniform CD-ROM driver Revision: 3.20
Dec 11 02:34:36 debian kernel: hdc: max request size: 128KiB
Dec 11 02:34:36 debian kernel: PCI: Enabling device :01:08.1 (0014 -> 0016)
Dec 11 02:34:36 debian kernel: ohci_hcd :01:08.1: OHCI Host Controller
Dec 11 02:34:36 debian kernel: ohci_hcd :01:08.1: new USB bus registered, 
assigned bus number 2
--
Dec 11 02:34:36 debian kernel: ieee1394: sbp2: Driver forced to seria

Bug#404876: no background screen activity in GDE or KDE @debian

[Rick Thomas]

On Jan 6, 2007, at 2:21 AM, pranay prateek wrote:


hi
I am using debian 2.6 kernel .
When i log in , the screen which i am greeted with doesnt show any  
activity in the background screen .i.e i dont get any  pop up when  
i click mouse on my background , no icons in my desktop screen and  
having a constant color .
this problem pervades through all display manager and desktop  
environments . i have tried (gdm,kdm)*(kde,xfce,gde) but all have  
the same problem .

when i login to gde it shows the following error message :

"
There was an error starting the GNOME Settings Daemon.

Some things, such as themes, sounds, or background settings may not  
work correctly.


The Settings Daemon restarted too many times.

The last error message was:

System exception: IDL:Bonobo/GeneralError:1.0 : Child process did  
not give an error message, unknown failure occurred


GNOME will still try to restart the Settings Daemon next time you  
log in.

"

Can any body suggest how this error can be rectified ?

Thanx.

PS: please include my email id in CC of the reply as i have not  
subscribed to debian-users list




--
Pranay Prateek
3rd Yr Electrical Engineering
Room No 339 ,Jamuna
IIT Madras



Pranay,

This sounds a lot like   What hardware are you using?  Is it a G3 based OldWorld  
PowerMac, by any chance?  If so, does the workaround in the bug  
report help?  If not on G3 PowerMac hardware, then it's even *more*  
interesting to know if the workaround helps!


Enjoy!

Rick



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

Bug#397649: install-report: NTP sync missing by default

[Rick Thomas]

On Nov 22, 2006, at 1:05 PM, Olaf van der Spek wrote:


reopen 397649
thanks

Could we have NTP by default?

> But it would be a problem for the minority who have no or only
> intermittent (e.g. dial-up) network access.

Why would it be a problem?


No network mean the "Network Time Protocol" won't work.

Intermittent network (e.g. dial-up) means that NTP goes for long  
periods with no connection to the external time servers.  The ntpd  
daemon is (mostly) OK with that, but some auto-dialers may see it's  
occasional polls as a reason to dial the ISP, which is probably not  
what the user expected.





> I leave it to the PTBs to figure out whether there is a compromise
> position.


PTBs?


Powers That Be  (From the US TV show "Buffy the Vampire Slayer")


Enjoy!

Rick



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

Bug#397649: install-report: NTP sync missing by default

[Rick Thomas]

On Nov 22, 2006, at 4:18 PM, Olaf van der Spek wrote:


Rick Thomas wrote:

No network mean the "Network Time Protocol" won't work.
Intermittent network (e.g. dial-up) means that NTP goes for long  
periods with no connection to the external time servers.  The ntpd  
daemon is (mostly) OK with that, but some auto-dialers may see  
it's occasional polls as a reason to dial the ISP, which is  
probably not what the user expected.


NTP could be at least installed but disabled instead of not installed.


What's the point of installing something you're not going to enable?   
It's not that much harder to type "aptitude install ntp" than it is  
to type "update-rc.d ntp defaults"



Although I'd like to have it enabled by default.

Isn't it possible to start/stop ntpd based on when the dial-up link  
is up?


Theoretically, yes.  In practice, it would be a pain to get all the  
little fiddly bits exactly right -- not something I'd want to undertake.



--
Olaf van der Spek
http://xccu.sf.net/


Rick



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

Bug#397649: install-report: NTP sync missing by default

[Rick Thomas]

On Nov 25, 2006, at 3:01 PM, Kurt Roeckx wrote:


On Sun, Nov 12, 2006 at 03:57:25PM -0500, Rick Thomas wrote:


Installing ntp by default (making it have priority "standard") would
be good for the many Debian users who have always-on network access.
But it would be a problem for the minority who have no or only
intermittent (e.g. dial-up) network access.


For ntpd to really work properly you need a static IP address.


Well... I'd say "stable" rather than "static".  If the local IP  
address changes once a week, an NTP client will have little trouble  
weathering the change.  Once an hour would be problematical.  Once a  
day is in the grey area.  Depending on the details, it may be  
desirable to restart the ntpd daemon when the IP address changes.


For an NTP *server* to be effective as a server, a very stable IP  
address is, of course, mandatory.  But most Debian users don't run  
NTP servers, and those who do know what they're doing and what is  
required to do it right.


Rick



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

Bug#398496: Installing python2.5 on etch for powerpc is broken...

[Rick Thomas]

Package: python2.5  

Installing python2.5 on etch for powerpc is broken...

Specifically:



Linking and byte-compiling packages for runtime python2.5...
pycentral: pycentral rtinstall: installed runtime python2.5 not found
pycentral rtinstall: installed runtime python2.5 not found
dpkg: error processing python2.5-minimal (--configure):



This is a newly installed etch system (installed desktop and  
printserver tasks)


Any clues?

Rick



darkstar:~# aptitude install python2.5
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Building tag database... Done
The following NEW packages will be automatically installed:
  libsqlite3-0 python2.5-minimal
The following NEW packages will be installed:
  libsqlite3-0 python2.5 python2.5-minimal
0 packages upgraded, 3 newly installed, 0 to remove and 0 not  
upgraded.
Need to get 0B/4624kB of archives. After unpacking 16.4MB will be  
used.

Do you want to continue? [Y/n/?]
Writing extended state information... Done
Selecting previously deselected package libsqlite3-0.
(Reading database ... 68871 files and directories currently  
installed.)

Unpacking libsqlite3-0 (from .../libsqlite3-0_3.3.8-1_powerpc.deb) ...
Selecting previously deselected package python2.5-minimal.
Unpacking python2.5-minimal (from .../python2.5- 
minimal_2.5-3_powerpc.deb) ...

Selecting previously deselected package python2.5.
Unpacking python2.5 (from .../python2.5_2.5-3_powerpc.deb) ...
Setting up libsqlite3-0 (3.3.8-1) ...

Setting up python2.5-minimal (2.5-3) ...
Linking and byte-compiling packages for runtime python2.5...
pycentral: pycentral rtinstall: installed runtime python2.5 not found
pycentral rtinstall: installed runtime python2.5 not found
dpkg: error processing python2.5-minimal (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of python2.5:
python2.5 depends on python2.5-minimal (= 2.5-3); however:
  Package python2.5-minimal is not configured yet.
dpkg: error processing python2.5 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
python2.5-minimal
python2.5
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up python2.5-minimal (2.5-3) ...
Linking and byte-compiling packages for runtime python2.5...
pycentral: pycentral rtinstall: installed runtime python2.5 not found
pycentral rtinstall: installed runtime python2.5 not found
dpkg: error processing python2.5-minimal (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of python2.5:
python2.5 depends on python2.5-minimal (= 2.5-3); however:
  Package python2.5-minimal is not configured yet.
dpkg: error processing python2.5 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
python2.5-minimal
python2.5
darkstar:~#







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

Bug#398496: Installing python2.5 on etch for powerpc is broken...

[Rick Thomas]

It appears to be version 0.5.9

HTH,

Rick


darkstar:~# aptitude show python-central
Package: python-central
State: installed
Automatically installed: no
Version: 0.5.9
Priority: standard
Section: python
Maintainer: Matthias Klose <[EMAIL PROTECTED]>
Uncompressed Size: 201k
Depends: python (>= 2.3)
Conflicts: debhelper (<= 5.0.37.3)
Description: register and build utility for Python packages
This package provides support for building and installing python  
modules independent of the current installed Python version.


darkstar:~#


On Nov 14, 2006, at 1:18 AM, Matthias Klose wrote:


which version of python-central is installed on the system?

Rick Thomas writes:

Package: python2.5  

Installing python2.5 on etch for powerpc is broken...

Specifically:



Linking and byte-compiling packages for runtime python2.5...
pycentral: pycentral rtinstall: installed runtime python2.5 not  
found

pycentral rtinstall: installed runtime python2.5 not found
dpkg: error processing python2.5-minimal (--configure):



This is a newly installed etch system (installed desktop and
printserver tasks)

Any clues?




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

Bug#399636: g3 imac: installation with the gtk-mini.iso

[Rick Thomas]

Holger's success emboldened me to try it on a couple of my own  
PowerMac machines.


It worked flawlessly on my G4 test machine.


[EMAIL PROTECTED]:~$ ( lspci ; lspci -n ) | sort
:00:0b.0 0600: 106b:002d
:00:0b.0 Host bridge: Apple Computer Inc. UniNorth 1.5 AGP
:00:10.0 0300: 1002:5046
:00:10.0 VGA compatible controller: ATI Technologies Inc Rage  
128 PF/PRO AGP 4x TMDS

0001:10:0b.0 0600: 106b:002e
0001:10:0b.0 Host bridge: Apple Computer Inc. UniNorth 1.5 PCI
0001:10:12.0 0101: 1095:0680 (rev 02)
0001:10:12.0 IDE interface: Silicon Image, Inc. PCI0680 Ultra  
ATA-133 Host Controller (rev 02)

0001:10:17.0 Class ff00: Apple Computer Inc. KeyLargo Mac I/O (rev 03)
0001:10:17.0 ff00: 106b:0022 (rev 03)
0001:10:18.0 0c03: 106b:0019
0001:10:18.0 USB Controller: Apple Computer Inc. KeyLargo USB
0001:10:19.0 0c03: 106b:0019
0001:10:19.0 USB Controller: Apple Computer Inc. KeyLargo USB
0002:20:0b.0 0600: 106b:002f
0002:20:0b.0 Host bridge: Apple Computer Inc. UniNorth 1.5 Internal  
PCI

0002:20:0e.0 0c00: 11c1:5811
0002:20:0e.0 FireWire (IEEE 1394): Agere Systems FW323
0002:20:0f.0 0200: 106b:0021 (rev 01)
0002:20:0f.0 Ethernet controller: Apple Computer Inc. UniNorth GMAC  
(Sun GEM) (rev 01)

[EMAIL PROTECTED]:~$



It failed, as expected (since it's got a 2.6.17 kernel) on my "beige  
G3" oldworld test machine.  I'll try again when there's a 2.6.18  
kernel available.  (The problem is in the kernel or initrd, not the g- 
i on this machine.)


I got the powerpc64 version and tried it on my dual-core G5 with the  
Nvidia graphics card.  It failed to go into graphics mode and looped  
forever spewing error messages too fast for me to get them down.   
I'll go to the wiki page and get the instructions for doing it in  
test mode.  But it will have to wait til I've had some sleep.


Specs from the MacOS-X "System Profiler" app on the video from the G5:


NVIDIA GeForce 6600LE:

  Chipset Model:GeForce 6600LE
  Type: Display
  Bus:  PCI
  Slot: SLOT-1
  VRAM (Total): 128 MB
  Vendor:   nVIDIA (0x10de)
  Device ID:0x0142
  Revision ID:  0x00a4
  ROM Revision: 2149
  Displays:
Cinema:
  Display Type: LCD
  Resolution:   1680 x 1050
  Depth:32-bit Color
  Core Image:   Supported
  Main Display: Yes
  Mirror:   Off
  Online:   Yes
  Quartz Extreme:   Supported
Display:
  Status:   No display connected



I got similar results (failing to go into graphics mode -- looping  
error messages) when I tried it on a blue&white G3 (very early  
NewWorld model).  I had to use "video=ofonly" to even get that far.   
Without it, the screen was all kinds of pretty colors, but nothing  
intelligible.


Here's the config on the blue&white:


$ ( lspci ; lspci -n ) | sort
:00:00.0 0600: 1057:0002 (rev 40)
:00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40)
:00:0d.0 0604: 1011:0026 (rev 02)
:00:0d.0 PCI bridge: Digital Equipment Corporation DECchip  
21154 (rev 02)

:01:00.0 0c00: 104c:8000 (rev 02)
:01:00.0 FireWire (IEEE 1394): Texas Instruments PCILynx/ 
PCILynx2 IEEE 1394 Link Layer Controller (rev 02)

:01:01.0 0101: 1095:0646 (rev 05)
:01:01.0 IDE interface: Silicon Image, Inc. (formerly CMD  
Technology Inc) PCI0646 (rev 05)

:01:02.0 0300: 1002:4749 (rev 5c)
:01:02.0 VGA compatible controller: ATI Technologies Inc 3D  
Rage Pro (rev 5c)

:01:03.0 0180: 1095:0680 (rev 02)
:01:03.0 Unknown mass storage controller: Silicon Image, Inc.  
(formerly CMD Technology Inc) PCI0680 Ultra ATA-133 Host Controller  
(rev 02)

:01:05.0 ff00: 106b:0017
:01:05.0 ff00: Apple Computer Inc. Paddington Mac I/O
:01:06.0 0c03: 1045:c861 (rev 10)
:01:06.0 USB Controller: OPTi Inc. 82C861 (rev 10)
$


Tomorrow I'll try this one in test mode too...


Hope this helps!

Rick






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

Bug#404876: Doesn't work on Blue&White G3 either...

[Rick Thomas]

Previously I reported that my Blue&White G3 Powermac didn't get the  
wigglies.  Apparently that was a lie.


I recently re-installed this machine and there there were!  So both  
my G3 machines (Beige OldWorld G3 and B&W NewWorld G3) have this  
problem.


Has there been any progress lately?


Rick



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

Bug#410625: G3 B/W pcilynx firewire blues

[Rick Thomas]

On Feb 12, 2007, at 7:22 PM, Benjamin Herrenschmidt wrote:


On Mon, 2007-02-12 at 15:30 -0500, Rick Thomas wrote:


Maybe I should try the whole thing again and write down the details.

Can you give me a URL for the linux ieee1394 mailing list?


https://lists.sourceforge.net/lists/listinfo/linux1394-devel

Ben.


Looking at the archives, it appears that pcilynx on PPC hardware has  
been broken horribly for a long time (at least since 2004).   
Furthermore, it looks like support for pcilynx may be dropped  
entirely from the next generation of ieee1394 drivers.


I'd suggest that pcilynx be disabled in the Debian PPC kernels, and a  
note to that effect be put in the release documents.


To what package should I send a bug report with that payload?

Rick



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

Bug#410846: [powerpc] The PCILynx firewire driver is broken on PPC machines, and should be disabled.

[Rick Thomas]

Package: release-notes

When I boot Debian (Etch or Sarge)  on my Blue&White PowerMac, with  
the old TI PCILynx firewire chip on the motherboard, the pcilynx  
driver crashes consistently.  If I blacklist pcilynx, the crash goes  
away, but I have no firewire capability.




https://lists.sourceforge.net/lists/listinfo/linux1394-devel


Looking at the archives of the Linux1394 developers mailinglist, it  
appears that pcilynx on PPC hardware has been horribly broken for a  
long time (at least since 2004).  Furthermore, it looks like support  
for pcilynx may be dropped entirely from the next generation of  
ieee1394 drivers, regardless of CPU type.


I'd like to suggest that pcilynx be disabled in the Debian PPC  
kernels, and a note to that effect be put in the release documents,  
encouraging users who need firewire to avail themselves of one of the  
cheap OHCI1394 cards.


Rick


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

Bug#410845: [powerpc] The PCILynx firewire driver is broken on PPC machines, and should be disabled.

[Rick Thomas]

Package: linux-2.6

When I boot Debian (Etch or Sarge)  on my Blue&White PowerMac, with  
the old TI PCILynx firewire chip on the motherboard, the pcilynx  
driver crashes consistently.  If I blacklist pcilynx, the crash goes  
away, but I have no firewire capability.




https://lists.sourceforge.net/lists/listinfo/linux1394-devel


Looking at the archives of the Linux1394 developers mailinglist, it  
appears that pcilynx on PPC hardware has been horribly broken for a  
long time (at least since 2004).  Furthermore, it looks like support  
for pcilynx may be dropped entirely from the next generation of  
ieee1394 drivers, regardless of CPU type.


I'd like to suggest that pcilynx be disabled in the Debian PPC  
kernels, and a note to that effect be put in the release documents,  
encouraging users who need firewire to avail themselves of one of the  
cheap OHCI1394 cards.


Rick


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

Bug#410971: interactive aptitude wants to remove hfsutils and sudo after etch installation

[Rick Thomas]

Package: installation
Severity: important


After installation on a powerpc system (PowerMac Blue&White G3) when aptitude 
is run in interactive (curses) mode, told 
to do update and finish any pending operations ("g") command, it turns out that 
the "hfsutils" and "sudo" packages are 
marked for deletion.  If aptitude is told to go ahead (a second "g" command) it 
will delete them.  This has bad effects 
on the health of the system.

*) hfsutils is used by ybin to setup the boot partition on Macs.  Without it, I 
can't use ybin to change bootstrap 
parameters.

*) sudo is needed if I choose "no root login" at installation time (which I 
usually do).  Without it I can't do system 
administration of just about any kind.

Interestingly,  non-interactive )commandline) aptitude does not seem to share 
this odd proclivity.  E.g. "aptitude 
install ntp" does not automatically delete hfsutils or sudo.

If it's important (this has been going on for a while, so it's not just a 
glitch in the current daily install CDs) this 
shows up when installing from [Debian GNU/Linux testing _Etch_ - Official 
Snapshot powerpc NETINST Binary-1 
20070214-00:13]




-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-powerpc
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


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

Bug#410971: interactive aptitude wants to remove hfsutils and sudo after etch installation

[Rick Thomas]

On Feb 14, 2007, at 8:00 PM, Frans Pop wrote:


On Thursday 15 February 2007 01:10, Joey Hess wrote:

Rick Thomas wrote:

After installation on a powerpc system (PowerMac Blue&White G3) when
aptitude is run in interactive (curses) mode, told to do update and
finish any pending operations ("g") command, it turns out that the
"hfsutils" and "sudo" packages are marked for deletion.  If aptitude
is told to go ahead (a second "g" command) it will delete them.   
This

has bad effects on the health of the system.


I have seen this occasionally in the past, especially when I used  
'apt-get

builddeps' or some such on an installed system. However, I have never
seen this after installs.

I also cannot reproduce it if I install d-i with sudo option. If I  
login
afterwards and do 'sudo aptitude' followed by 'u' and 'g', I just  
get "No

packages are scheduled to be installed, removed or upgraded.


OK, here's the exact sequence of events as near as I can remember --  
I didn't write it down.  If it's critical, I can re-do the install  
and write *everything* down.  Also, if it would be helpful, I can  
supply log files.


Start with a bog-standard Blue&White PowerMac G3 (but I've seen this  
on other PowerMac machines, so the exact hardware may not be important.)


Installed from the Netinst CD (I've seen it with Businesscard CDs  
too) at the boot prompt chose the default type of install (Non- 
expert.  Though I've seen it with an "expert" install too.)  Accepted  
all the defaults to all the questions except...


When it asked for a root password, I hit "go back" and told it I  
didn't want to allow root logins.  Then I proceeded with default  
answers from then on.  I installed a standard system at tasksel time.  
(un-checked "Desktop Environment", checked "Standard System", and  
left unchecked everything else.  But I've seen this with "Desktop  
Environment" checked as well.)


After the reboot, I logged in as normal user, did "sudo su -" to get  
to root.  I edited the sources.list file to get rid of the line that  
calls for the netinst CD.  I then did "aptitude install rsnapshot  
enscript ntp lynx-cur openssh-server lpr gpm bzip2 fbset mouseemu"  
and let it run it's course.


Then I did a bare "aptitude" and in the aptitude interactive mode I  
hit "u" and "g".  It told me it wanted to delete sudo and hfsutils.   
I told it to "install" those two instead (hit "+" for each of them)  
and gave it a "g" which installed nothing and removed nothing.


Would log files help?

Rick



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

Bug#411446: Clock not set correctly; MacOS9 not detected?

[Rick Thomas]

So the problem is that (aside from the possibility that OS9 is not  
being recognized) if the other OS is OS9, the default for hardware  
clock should be "local time", but if the other OS is OS-X, the  
default for the hardware clock should be "UTC".  Is that a correct  
assessment?


I solve it by running my OS9 in UTC.  Others are not so likely to  
appreciate that solution!


Rick



On Feb 28, 2007, at 12:14 PM, Wouter Verhelst wrote:


On Wed, Feb 28, 2007 at 05:53:16PM +0100, Frans Pop wrote:
Note that Debian people tell me that OSx systems _are supposed_ to  
run

with internal clock on UTC.


This seems correct, yes; My PowerBook happily runs both Debian and  
OS X

at this time, with clock set correctly, and with 'tail -n 1
/etc/adjtime' returning 'UTC'.




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

Bug#403112: network-manager can't cope with OldWorld G3 PowerMac with "bmac" ethernet

[Rick Thomas]

Package: network-manager
Version: 0.6.4-6
Followup-For: Bug #403112


OldWorld PowerMac beige G3 tower.  Bog-standard configuration.  No additional 
devices above those on the motherboard.  
In particular, the only ethernet interface is the "bmac" that comes standard on 
lots of OldWorld PowerMac machines.

First I installed (20070228-2 "Netinst") using the default configuration 
("Desktop" and "standard" tasks checked in 
tasksel).  The install went fine.  No difficulties with network access.  
Network info came from dhcp.

After the reboot, however, network access was not available.  Poking around in 
the log files brought up this snippit:

===
Mar  1 02:48:11 debian NetworkManager: ^Istarting... 
Mar  1 02:48:11 debian NetworkManager: ^Ieth0: Driver 'bmac' does 
not support carrier detection. ^IYou 
must switch to it manually. 
Mar  1 02:48:11 debian NetworkManager: ^Inm_device_init(): waiting 
for device's worker thread to start 
Mar  1 02:48:11 debian NetworkManager: ^Inm_device_init(): 
device's worker thread started, continuing. 
Mar  1 02:48:11 debian NetworkManager: ^INow managing wired 
Ethernet (802.3) device 'eth0'. 
Mar  1 02:48:11 debian NetworkManager: ^IDeactivating device eth0. 
===

So I did "aptitude remove network-manager-gnome" and rebooted.  After the 
reboot, the network (via the bmac) was 
available again.

Many OldWorld PowerMac machines have bmac interfaces as their only way of 
geting to the network.  If network-manager 
was smart enough to see that the machine has only one network interface, and 
not deactivate it out-of-hand (regardless 
of how braindead the interface may seem to be), then this problem would be much 
less severe.

As it is, however, this is a very serious problem.  I don't think it's a good 
idea to release Etch without solving this 
one way or another.  It renders a whole class of machines unusable.

For machines with two or more network interfaces (a bmac and one or more 
others) the workaround of not deactivating the 
only interface would not work.  But presumably, people with such machines would 
be sophisticated enough to deal with 
the problem some other way.

Rick


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-powerpc
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages network-manager depends on:
ii  adduser 3.102Add and remove users and groups
ii  dbus1.0.2-1  simple interprocess messaging syst
pn  dhcdbd (no description available)
ii  hal 0.5.8.1-6.1  Hardware Abstraction Layer
ii  ifupdown0.6.8high level tools to configure netw
pn  iproute(no description available)
pn  iputils-arping (no description available)
ii  libc6   2.3.6.ds1-11 GNU C Library: Shared libraries
ii  libdbus-1-3 1.0.2-1  simple interprocess messaging syst
ii  libdbus-glib-1-20.71-3   simple interprocess messaging syst
ii  libgcrypt11 1.2.3-2  LGPL Crypto library - runtime libr
ii  libglib2.0-02.12.4-2 The GLib library of C routines
ii  libgpg-error0   1.4-1library for common error values an
ii  libhal1 0.5.8.1-6.1  Hardware Abstraction Layer - share
pn  libiw28(no description available)
pn  libnl1-pre6(no description available)
pn  libnm-util0(no description available)
ii  lsb-base3.1-23   Linux Standard Base 3.1 init scrip
pn  wpasupplicant  (no description available)

network-manager recommends no packages.


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

Bug#413424: xserver-xorg: xserver fails to start because of resource conflict on PowerMac beige G3 (OldWorld)

[Rick Thomas]

Package: xserver-xorg
Version: 1:7.1.0-13
Severity: important

Configuration is bog-standard PowerMac beige G3 tower (OldWorld) with ATI video 
controller on the motherboard.
Details are in the attached configuration files and log files.

I've tried this with both "ati" driver and "fbdev" driver.  Both give the same 
results.



-- Package-specific info:
Contents of /var/lib/x11/X.roster:
xserver-xorg

/etc/X11/X target does not match checksum in /var/lib/x11/X.md5sum.

X server symlink status:
lrwxrwxrwx 1 root root 13 Mar  1 02:07 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1858512 Mar  1 00:23 /usr/bin/Xorg

Contents of /var/lib/x11/xorg.conf.roster:
xserver-xorg

VGA-compatible devices on PCI bus:
00:12.0 VGA compatible controller: ATI Technologies Inc 3D Rage I/II 215GT 
[Mach64 GT] (rev 9a)

/etc/X11/xorg.conf unchanged from checksum in /var/lib/x11/xorg.conf.md5sum.

Xorg X server configuration file status:
-rw-r--r-- 1 root root 3020 Mar  4 16:42 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath"/usr/share/fonts/X11/misc"
FontPath"/usr/X11R6/lib/X11/fonts/misc"
FontPath"/usr/share/fonts/X11/cyrillic"
FontPath"/usr/X11R6/lib/X11/fonts/cyrillic"
FontPath"/usr/share/fonts/X11/100dpi/:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath"/usr/share/fonts/X11/75dpi/:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath"/usr/share/fonts/X11/Type1"
FontPath"/usr/X11R6/lib/X11/fonts/Type1"
FontPath"/usr/share/fonts/X11/100dpi"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi"
FontPath"/usr/share/fonts/X11/75dpi"
FontPath"/usr/X11R6/lib/X11/fonts/75dpi"
# path to defoma fonts
FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load"bitmap"
Load"ddc"
Load"dri"
Load"extmod"
Load"freetype"
Load"glx"
Load"int10"
Load"vbe"
EndSection

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "CoreKeyboard"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "macintosh"
Option  "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
EndSection

Section "Device"
Identifier  "ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT]"
Driver  "fbdev"
BusID   "PCI:0:18:0"
Option  "UseFBDev"  "true"
EndSection

Section "Monitor"
Identifier  "EN-775e"
Option  "DPMS"
HorizSync   28-49
VertRefresh 43-72
EndSection

Section "Screen"
Identifier  "Default Screen"
Device  "ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT]"
Monitor "EN-775e"
DefaultDepth24
SubSection "Display"
Depth   1
Modes   "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   4
Modes   "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   8
Modes   "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   15
Modes   "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   16
Modes   "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   24
Modes   "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier  "Default Layout"
Screen  "Default Screen"

Bug#413814: installing Debian GNU/Linux 4.0 on a Power Macintosh G3 Server

[Rick Thomas]

Hi Alex!

Welcome to an elite minority of those of us who have got this to work!

Below are a couple of hints from my own experience in doing this.

Rick

On Mar 7, 2007, at 5:21 AM, Alex Teclo wrote:


Package: installation-reports

Boot method: BootX
Image version: Debian etch powerpc weekly build
Date: February 4th 2007

Machine: Power Macintosh G3 Server
Architecture: powerpc
Processor: PowerPC 740/750 (G3)
Memory: 256 MB
Comments/Problems:

Here's a feedback of my installation of Debian 4.0 "etch" on a  
Power Macintosh G3 MiniTower


Since it's an oldworld macintosh, it cannot boot from the Debian  
CDs. I tried booting from floppies, but it never worked, the floppy  
drive is probably dead.

So my solution was to install a legit copy of MacOS 9.2

Here's what I did:
- boot into MacOS 9.2
- launch BootX with the files vmlinux and initrd.gz
- debian-installer runs smoothly and everything goes well, except  
one thing: when debian-installer attempts to install quik as a boot  
loader, the operation fails, and the error messages states that  
"the partition is not ext2". This error messages seems odd to me.  
What partition does d-i mean ? The partition where MacOS 9.2 is,  
which is HFS ? One of the Linux partitions, which are ext3 and not  
ext2 ? Anyway, isn't ext2 the same thing as ext3 without  
journalization ?
- anyway I'm not worried at all that quik could not install,  
because I still can boot into MacOS 9.2 and then fire up BootX to  
boot into Debian GNU/Linux

- debian-installer finished up its work and reboots the machine
... and then something goes wrong: I see on the power macintosh a  
flashing "?" in a floppy. This means "I can't find any operating  
system to boot" ... ouch ! Now that's a problem.

- I tried zapping the PRAM, it did not help.
- Finally I took the "Outil Disque Dur" diskette and chose the menu  
"Fonction" and then "Mise à jour". Pardon my French, this should  
translate to "Apple Disk Tool", menu "Functions" and then "Update".  
I don't know the exact wording since I've never used MacOS 9.2 in  
any other language than French :)

... and *yes*, now I can boot into MacOS 9.2



At some point after the installer has stepped you through choosing  
language and keyboard, but before running the partitioner, you can  
choose "go back" from one of the question screens. That will get you  
to a top-level menu which has an option (near the bottom) of changing  
the priority level of the questions that the installation asks you.   
Change it to "low" or "medium".  From now on, the installer will  
return to that top level menu screen between installation steps.   It  
will also ask you more questions than it did at default priority --  
just choose the defaults if you don't know the answers.


This will give you a chance to prevent it from trying to install the  
quik bootloader (choose "proceed without installing a boot loader"  
instead.)  This will keep it from messing up the OS-9 bootstrap stuff.


When it ejects the CD and pauses one last time before rebooting,  
switch to VT2 (hit -F2) where you can start up a limited shell  
by hitting the  key.  The root partition for the installation  
is mounted on "/target".  have a look around if you like (do "ls",  
"df", "ps" and anything else non-destructive.)  Then do the following  
stuff:


mkdir /target/MacOS
# you *may* need to do "modprobe hfs" here (or "modprobe hfsplus").   
I don't recall.
# In any case, you've got the installer kernel and it's associated  
modules in the

# installer ramdisk, where you currently are, so it will work.
	mount -t hfsplus /dev/hda6 /target/MacOS  # or "-t hfs" if that's  
what it is.

chroot /target
# Now you're in "bash" inside the installed system.
# If you like, you can poke around a bit now to get a feel for the  
environment.
	cp /boot/vmlinux /MacOS/System\ Folder/Linux\ Kernels/vmlinux-new
# or whatever you like to call it
	cp /boot/initrd.img /MacOS/System\ Folder/Linux\ Kernels/initrd- 
new.img  # or whatever

exit
# now you're back into the installer environment with it's limited shell
umount /target/MacOS

Then switch back to the VT1 (-F1) console and proceed with the  
final stages of the installation.


It will reboot into MacOS-9.2 and pause at the BootX screen.  Enter  
your "root=/dev/hda9" in the parameter box and choose your new kernel  
and initrd.img files.  Then allow it to boot into Linux.  You should  
be good to go.





... but now when I boot into Debian GNU/Linux with BootX, there is  
another, more serious problem:
When I boot into Debian GNU/Linux with BootX, I can only use the  
vmlinux and initrd.gz of debian-installer. So instead of booting  
into my system, I boot into debian-installer.
Attempt to solve this problem: start a shell from debian-installer,  
and chroot to my Debian GNU/Linux system. From there, find the  
vmlinux and initrd.gz that will allow me to boot directly into  
Debian GNU/Linux (they are in /boot) an

Bug#411637: dpkg-reconfigure enscript should allow to set papersize

[Rick Thomas]

Package: enscript
Version: 1.6.4-11
Severity: wishlist
Tags: l10n


enscript currently defaults to A4 size paper regardless of locale.  It would be 
nice if there were a way (possibly via 
"dpkg-reconfigure") to set it to whatever the local standard is ("Letter" in 
the US, for example).

This is already possible for the libpaper1 package, which enscript depends on.  
Maybe enscript could consult 
/etc/papersize as configured by libpaper1 to get its paper size.


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-powerpc
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages enscript depends on:
ii  libc6   2.3.6.ds1-11 GNU C Library: Shared libraries
ii  libpaper1   1.1.21   Library for handling paper charact

enscript recommends no packages.

-- no debconf information


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

Bug#411642: should be possible to build simple /etc/printcap with dpkg-reconfigure lpr

[Rick Thomas]

Package: lpr
Version: 1:2006.11.04
Severity: wishlist

It would be nice if there were some help available (e.g. with dpkg-reconfigure) 
to build the /etc/printcap file -- at least in the simple case of a remote 
printer where the 
only information needed are the host and the printername.



-- System Information: Debian Release: 4.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-powerpc
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages lpr depends on:
ii  libc6   2.3.6.ds1-11 GNU C Library: Shared libraries
ii  netbase 4.29 Basic TCP/IP networking system

lpr recommends no packages.

-- no debconf information


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

Bug#389881: RC-ness of this bug

[Rick Thomas]

On Mar 15, 2007, at 1:12 PM, Frans Pop wrote:


On Thursday 15 March 2007 17:44, Colin Watson wrote:

Personally I also feel that all possible solutions effectively make
/etc/fstab unreadable and unmaintainable.


The approach we took in Ubuntu was to put comments above each UUID
entry in /etc/fstab documenting which traditional device name they
corresponded to at the point of installation. Of course this can get
out of date, but I don't think there's really any sensible way around
that.


My main point is not that the UUID itself is not readable, but  
rather that

the lines get way too long and, depending on your editor (settings),
either get wrapped or disappear off screen. You loose the easy  
overview

of what's in fstab.
/etc/fstab used to be fairly maintainable because the info could be  
kept
in columns fairly easily for most cases and because the info would  
mostly

fit on one line [1].

IMO with a switch to UUIDs we are going to need an fstab editor  
(console

based) that:
- does the translation to the "normal" device names on the fly (and  
thus

  does always reflect the actual situation)
- provides different 'views' of what's in fstab
- allows to select what representation for the file system should be
  used in the fstab (traditional, path, uuid, id, ...)
- allows to set mount point, type, mount options, etc.
- sorts partitions into a logical order
- maybe knows about removable devices
- has a simple interface to add new entries for e.g. USB sticks
- ...

[1] Yeah, I know this is not true for NFS volumes and if a lot of  
options

are used, but in general it was true.



If you're going to all the trouble of a smart fstab editor, why not  
simply define a more modern format (e.g. like that of dhcpd.conf) for  
the information that can accommodate line breaks and nesting.  Change  
the name to something else, don't call it fstab; if the new file  
doesn't exist the mount command (and the rest of them that currently  
read fstab) will default to /etc/fstab if present.


The biggest problem will be identifying all the places where fstab is  
currently *assumed* to be present and making them all use the new  
file.  A library is probably needed that does the deciding of which  
format to use.


Are there POSIX/LSB/etc ramifications?

just a thought,

Rick


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

Bug#415543: xorg: xserver crashes on beige G3 PowerMac

[Rick Thomas]

Package: xorg
Version: 1:7.1.0-15
Severity: important

(Note: this bugreport is about a beige G3 PowerMac tower, but the same problem 
also appears on my Blue&White G3 
PowerMac.)


Problem:
X fails to start on a beige G3 PowerMac.

I get the following error messages...  In particular, note the messages
... "INVALID IO ALLOCATION" and "found resource conflicts"

I'm also attaching /var/log/Xorg.0.log which seems to have more details.

lspci gives this:

00:00.0 Host bridge [0600]: Motorola MPC106 [Grackle] [1057:0002] (rev 40)
00:0e.0 SCSI storage controller [0100]: Artop Electronic Corp ATP865 
[1191:0009] (rev 06)
00:10.0 Unknown class [ff00]: Apple Computer Inc. Heathrow Mac I/O [106b:0010] 
(rev 01)
00:12.0 VGA compatible controller [0300]: ATI Technologies Inc 3D Rage I/II 
215GT [Mach64 GT] [1002:4754] (rev 9a)


=
[EMAIL PROTECTED]:~$ startx
xauth:  creating new authority file /home/rbthomas/.serverauth.11436


X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: UNKNOWN
Current Operating System: Linux debian 2.6.18-4-powerpc #1 Wed Feb 21 13:39:54 
CET 2007 ppc
Build Date: 07 March 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Mar 20 01:01:46 2007
(==) Using config file: "/etc/X11/xorg.conf"
(WW) INVALID IO ALLOCATION b: 0xfe001000 e: 0xfe0010ff correcting
(EE) end of block range 0xfdff < begin 0xfe00
(EE) FBDEV(0): xf86RegisterResources() found resource conflicts
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
  after 0 requests (0 known processed) with 0 events remaining.
[EMAIL PROTECTED]:~$




-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-powerpc
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages xorg depends on:
ii  gnome-terminal [x-terminal- 2.14.2-1 The GNOME 2 terminal emulator appl
ii  libgl1-mesa-dri 6.5.1-0.6A free implementation of the OpenG
ii  libgl1-mesa-glx 6.5.1-0.6A free implementation of the OpenG
ii  libglu1-mesa6.5.1-0.6The OpenGL utility library (GLU)
ii  type-handling [not+sparc]   0.2.19   dpkg architecture generation scrip
ii  xbase-clients   1:7.1.ds1-2  miscellaneous X clients
ii  xfonts-100dpi   1:1.0.0-3100 dpi fonts for X
ii  xfonts-75dpi1:1.0.0-375 dpi fonts for X
ii  xfonts-base 1:1.0.0-4standard fonts for X
ii  xfonts-scalable 1:1.0.0-6scalable fonts for X
ii  xkb-data0.9-4X Keyboard Extension (XKB) configu
ii  xserver-xorg1:7.1.0-15   the X.Org X server
ii  xterm [x-terminal-emulator] 222-1etch2   X terminal emulator
ii  xutils  1:7.1.ds.3-1 X Window System utility programs

xorg recommends no packages.

-- no debconf information


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

Bug#415543: xorg: xserver crashes on beige G3 PowerMac

[Rick Thomas]

On Mar 20, 2007, at 1:19 AM, Rick Thomas wrote:


Package: xorg
Version: 1:7.1.0-15
Severity: important

(Note: this bugreport is about a beige G3 PowerMac tower, but the  
same problem also appears on my Blue&White G3

PowerMac.)


Problem:
X fails to start on a beige G3 PowerMac.

I get the following error messages...  In particular, note the  
messages

... "INVALID IO ALLOCATION" and "found resource conflicts"

I'm also attaching /var/log/Xorg.0.log which seems to have more  
details.







Xorg.0.log
Description: Binary data

Bug#404876: G3 (or other non-altivec machines) testers sought

[Rick Thomas]

On Jan 14, 2007, at 5:08 PM, Sjoerd Simons wrote:


Hi,

  Gstreamer currently has a release critical bug that seems to be only
  reproducable on powerpc machines without altivec support and even  
then not
  always. The best hint to what the problem might be seems to  
indicate there is

  an issue in the libvisual altivec detection code[0]..


Here's an interesting counterpoint to my previous experiences with an  
OldWorld Beige G3 PowerMac...


I tried installing on a Blue&White G3 NewWorld (just barely! -- it  
was one of the very first of Apple's NewWorld PowerMacs).


It has the G3 processor (no altivec) but the wigglys don't happen!

I installed from the Jan 21, 2007 09:10:17 UTC "businesscard" CD.

I haven't tried the whole testing process that Sjoerd recommended.  I  
will do that soon.


"Curiouser and curioser!", cried Alice.

Rick



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

Bug#408818: cool

[Rick Thomas]

On Jan 28, 2007, at 9:42 PM, Phill Thorpe wrote:


On Mon, 2007-01-29 at 03:09 +0100, Frans Pop wrote:

On Monday 29 January 2007 02:41, Phill Thorpe wrote:

I dont think that you read it correctly.
This install did not detect my nic at first, it only detected my nic
when I booted with:
install interface=eth1
Which I dont believe should be necessary.


No, the "interface=eth1" option does not have _any_ effect on  
detection of

NICs, only on which one is _used_.

So, unless you can point us to a real problem with NIC detection/ 
selection
during your initial install, there is no problem as far as we can  
tell.


Cheers,
FJP


So I wonder why it detected the wrong one, when I only have one nic.

regards
 Phill.



Does looking closely at what Phill supplied for his original report  
help any?:



Output of lspci -nn and lspci -vnn:
phill:/home/phill# lspci -nn
...  ...
00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102  
[Rhine-II] [1106:3065] (rev 7c)

... 

Output of lspci -vnn:
phill:/home/phill# lspci -vnn
..
00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102  
[Rhine-II] [1106:3065] (rev 7c)

Subsystem: ASUSTeK Computer Inc. Unknown device [1043:80ed]
Flags: bus master, medium devsel, latency 64, IRQ 217
I/O ports at d800 [size=256]
Memory at febff800 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 2
...


I'm not enough of a PCI hardware guru to know if this is going to be  
recognized as a NIC.  Anybody else?


Also, I saw a bunch of PCI bridges and so on.  Is is possible that  
the NIC is on the far side of one of them and that's confusing the  
issue?  Or am I talking total nonsense?


Just a thought...

Rick



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

Bug#409218: one of three cdimage.d.o has different timezone from other two

[Rick Thomas]

Package: cdrom

One of the three machines that round-robin for the server  
"cdimage.debian.org" seems to have a different timezone (for ftp, but  
not http) from the other two.


Specifically:


$ host cdimage.debian.org
cdimage.debian.org is an alias for ftp.acc.umu.se.
ftp.acc.umu.se has address 130.239.18.138
ftp.acc.umu.se has address 130.239.18.158
ftp.acc.umu.se has address 130.239.18.159

$ host 130.239.18.158
158.18.239.130.in-addr.arpa domain name pointer laotzu.acc.umu.se.
$ host 130.239.18.159
159.18.239.130.in-addr.arpa domain name pointer chuangtzu.acc.umu.se.
$ host 130.239.18.138
138.18.239.130.in-addr.arpa domain name pointer saimei.acc.umu.se.


So when I do...

$ ( echo 'cd cdimage/daily-builds/sid_d-i/20070131-2/powerpc/iso- 
cd' ; echo 'ls' ) | ftp 130.239.18.158

-rw-r--r--1 1002 1002  242 Jan 31 22:36 HEADER.html
-rw-r--r--1 1002 1002  143 Jan 31 22:36 MD5SUMS
-rw-r--r--1 1002 1002 73443328 Jan 31 22:34 debian- 
testing-powerpc-businesscard.iso
-rw-r--r--1 1002 1002   251237 Jan 31 22:36 debian- 
testing-powerpc-businesscard.iso.zsync
-rw-r--r--1 1002 1002 246259712 Jan 31 22:36 debian- 
testing-powerpc-netinst.iso
-rw-r--r--1 1002 1002   421055 Jan 31 22:36 debian- 
testing-powerpc-netinst.iso.zsync
$ ( echo 'cd cdimage/daily-builds/sid_d-i/20070131-2/powerpc/iso- 
cd' ; echo 'ls' ) | ftp 130.239.18.159

-rw-r--r--1 1002 1002  242 Jan 31 22:36 HEADER.html
-rw-r--r--1 1002 1002  143 Jan 31 22:36 MD5SUMS
-rw-r--r--1 1002 1002 73443328 Jan 31 22:34 debian- 
testing-powerpc-businesscard.iso
-rw-r--r--1 1002 1002   251237 Jan 31 22:36 debian- 
testing-powerpc-businesscard.iso.zsync
-rw-r--r--1 1002 1002 246259712 Jan 31 22:36 debian- 
testing-powerpc-netinst.iso
-rw-r--r--1 1002 1002   421055 Jan 31 22:36 debian- 
testing-powerpc-netinst.iso.zsync
$ ( echo 'cd cdimage/daily-builds/sid_d-i/20070131-2/powerpc/iso- 
cd' ; echo 'ls' ) | ftp 130.239.18.138

-rw-r--r--1 1002 1002  242 Jan 31 23:36 HEADER.html
-rw-r--r--1 1002 1002  143 Jan 31 23:36 MD5SUMS
-rw-r--r--1 1002 1002 73443328 Jan 31 23:34 debian- 
testing-powerpc-businesscard.iso
-rw-r--r--1 1002 1002   251237 Jan 31 23:36 debian- 
testing-powerpc-businesscard.iso.zsync
-rw-r--r--1 1002 1002 246259712 Jan 31 23:36 debian- 
testing-powerpc-netinst.iso
-rw-r--r--1 1002 1002   421055 Jan 31 23:36 debian- 
testing-powerpc-netinst.iso.zsync


Interestingly, when looked at with http protocol rather than ftp  
protocol, this discrepancy does not occur.


Rick

"Curiouser and curiouser!", cried Alice.



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

Bug#383690: Latest update breaks ntp

[Rick Thomas]

Hi Daniel,

I'll see if I can reproduce the symptoms and keep a careful log.   
What logs/outputs would you like to to collect?


Rick

On Sep 1, 2006, at 10:27 PM, Daniel Burrows wrote:

  Do you have any information that would explain why it did this?   
I'll

need more data to do anything useful with this report.

   Thanks,
  Daniel




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

Bug#383690: Latest update breaks ntp

[Rick Thomas]

I'm wondering if this is similar to the problem that is described in

http://lists.debian.org/debian-user/2006/09/msg00090.html

Certainly the pattern of dependency/pre-dependency seems similar...

What happened was this:

I had installed ntpdate, ntp-simple and ntp packages at the 4.2.0a 
+stable-2sarge1 revision level.  When the "dfsg" revision of these  
packages came along, instead of updating those packages, the result  
of an "aptitude upgrade" was to delete the ntp* packages entirely.  I  
got out of the problem by re-installing the ntp* packages, which got  
me to the dfsg versions.


I plan to do a non-network install (dvd-only) of the beta3 dvd (which  
should get me to the condition I was in before the problems) then add  
a network repo to sources.list (which should attempt to update to the  
dfsg versions) and see what happens.


Rick



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

Bug#383690: Latest update breaks ntp

[Rick Thomas]

On Sep 2, 2006, at 1:35 PM, Rick Thomas wrote:

I plan to do a non-network install (dvd-only) of the beta3 dvd  
(which should get me to the condition I was in before the problems)  
then add a network repo to sources.list (which should attempt to  
update to the dfsg versions) and see what happens.



I did this.  The attached "typescript" and "/var/log/aptitude" files  
will give you all the gory details.  But here's the executive summary:


After the non-network (DVD-only) install, I added the repository at  
debian.lcs.mit.edu to my sources.list and did an "aptitude update"  
and "aptitude upgrade" to get up to the latest levels of everything  
*but* the ntp packages, so as to avoid a lot of irrelevant noise from  
updates of other packages.  Then I switched back to the DVD-only  
sources.list to install the ntp packages at level 4.2.0a 
+stable-2sarge1 from the DVD.


I switched back to the network enabled sources.list and did "aptitude  
update" and "aptitude upgrade" in an attempt to pick up the 4.2.2 
+dfsg.2-1 level of the ntp packages from the network repository.  I got:



The following packages have been kept back:
  ntp
The following packages will be upgraded:
  ntpdate psmisc
2 packages upgraded, 0 newly installed, 0 to remove and 1 not  
upgraded.

Need to get 142kB of archives. After unpacking 73.7kB will be used.
Do you want to continue? [Y/n/?]
Get:1ohttp://debian.lcs.mit.edu etch/main ntpdate 1:4.2.2+dfsg.2-1  
[59.6kB]

Get:2Whttp://debian.lcs.mit.edu etch/main psmisc 22.3-1 [82.0kB]
Fetchedo142kB]in80s0(635kB/s)
(Reading database ... 22527 files and directories currently  
installed.)
Preparing to replace ntpdate 1:4.2.0a+stable-2sarge1 (using .../ 
ntpdate_1%3a4.2.2+dfsg.2-1_powerpc.deb) ...

Unpacking replacement ntpdate ...
Preparing to replace psmisc 22.2-1 (using .../ 
psmisc_22.3-1_powerpc.deb) ...

Unpacking replacement psmisc ...
Setting up ntpdate (4.2.2+dfsg.2-1) ...
Installing new version of config file /etc/default/ntpdate ...
Installing new version of config file /etc/init.d/ntpdate ...
Installing new version of config file /etc/logcheck/ignore.d.server/ 
ntpdate ...


Setting up psmisc (22.3-1) ...


So the first question is, Why was the ntp package held back?

I did "aptitude -v show ntp ntp-server ntp-simple ntpdate" to see the  
dependency relations of those packages.  Perhaps you can make enough  
sense out of them to explain?


Then, in an effort to get it to update the ntp packages other than  
ntpdate (which was already updated), I did "aptitude dist-upgrade"  
and got:



The following packages are unused and will be REMOVED:
  libssl0.9.7 ntp
The following packages will be automatically REMOVED:
  ntp-server ntp-simple
The following packages will be REMOVED:
  ntp-server ntp-simple
0 packages upgraded, 0 newly installed, 4 to remove and 0 not  
upgraded.

Need to get 0B of archives. After unpacking 2642kB will be freed.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
(Reading database ... 22530 files and directories currently  
installed.)

Removing ntp-server ...
Stopping NTP server: ntpd.
Removing ntp ...
Removing ntp-simple ...
Removing libssl0.9.7 ...


which left me without any ntp packages at all installed (except  
ntpdate).


So the second question is, Why did it think the "ntp" package was  
unused?
And the third question is, Why didn't it install the updated "ntp"  
package?


"Curiouser and curiouser!", cried Alice.

Finally, doing "aptitude install ntp" brought in the 4.2.2+dfsg.2-1  
level from the network repository.



Hope this helps!

Rick




typescript
Description: Binary data





aptitude_log
Description: Binary data

Bug#383690: Latest update breaks ntp

[Rick Thomas]

Hi Daniel,

Here's a strange one!  I assume a bug-report is appropriate, and I'll  
make one, but I'll need your help in figuring out which package to  
report it against...


I have a machine ("darkstar") running etch, which I use for testing  
debian installer things.  I did an "aptitude update ; aptitude  
upgrade" before leaving for the 3-day weekend.  When I returned  
today, Tuesday, I tried to do the same thing, to pick up any changes  
that happened over the weekend.


The Tuesday "aptitude upgrade" told me that a whole bunch of packages  
were being kept back (as well as the usual flock that wanted to be  
upgraded; etch is testing after all).  I aborted to think about  
things.  After thinking, I allowed it to proceed and it updated what  
it could.  But it still had a bunch of packages being kept back.  I  
tried "aptitude dist-upgrade" just to see what it would propose, but  
aborted before letting it have its way, because it wanted to delete a  
bunch of stuff that looked like I wouldn't be happy if they were  
deleted.  It claimed a number of things were broken as well.


I managed to save all of this in a typescript, which is attached.   
I'll leave the machine unchanged for a while, if you want me to run  
any tests or retrieve any log files.


Any advice on where to send the bug-report will be appreciated!

Thanks!

Rick


darkstar:~# aptitude update
Get:1 http://debian.lcs.mit.edu etch Release.gpg [189B]
Get:2 http://debian.lcs.mit.edu etch Release [62.9kB]   

Get:3 http://ike.egr.msu.edu etch Release.gpg [189B]

Get:4 http://ike.egr.msu.edu etch Release [62.9kB]  

Get:5 http://security.debian.org etch/updates Release.gpg [189B]
   
Get:6 http://security.debian.org etch/updates Release [24.3kB]  
   
Get:7 http://debian.lcs.mit.edu etch/main Packages/DiffIndex [12.6kB]   
  
Get:8 http://debian.lcs.mit.edu etch/non-free Packages/DiffIndex [12.5kB]   

Ign http://security.debian.org etch/updates/main Packages/DiffIndex 

Get:9 http://ike.egr.msu.edu etch/main Packages/DiffIndex [12.6kB]  

Ign http://security.debian.org etch/updates/main Sources/DiffIndex  
   
Get:10 http://debian.lcs.mit.edu etch/contrib Packages/DiffIndex [12.5kB]   
   
Get:11 http://debian.lcs.mit.edu etch/main Sources/DiffIndex [12.5kB]   

Get:12 http://debian.lcs.mit.edu etch/non-free Sources/DiffIndex [12.5kB]   

Get:13 http://debian.lcs.mit.edu etch/contrib Sources/DiffIndex [12.5kB]

Hit http://security.debian.org etch/updates/main Packages   

Get:14 2006-09-01-1257.51.pdiff [70.4kB]

Hit http://security.debian.org etch/updates/main Sources

Get:15 http://ike.egr.msu.edu etch/non-free Packages/DiffIndex [12.5kB] 

Get:16 2006-09-01-1257.51.pdiff [1568B] 

Get:17 2006-09-01-1257.51.pdiff [1236B] 

Get:18 2006-09-01-1257.51.pdiff [15.9kB]

Get:19 2006-09-01-1257.51.pdiff [351B]  
   
Get:20 2006-09-01-1257.51.pdiff [70.4kB]
   
Get:21 2006-09-01-1257.51.pdiff [476B]  
   
Get:22 http://ike.egr.msu.edu etch/contrib Packages/DiffIndex [12.5kB]  
   
Get:23 2006-09-01-1257.51.pdiff [1568B]  
Get:24 2006-09-01-1257.51.pdiff [1236B]  
Get:25 2006-09-01-1257.51.pdiff [70.4kB]
  
Get:26 http://ike.egr.msu.edu etch/main Sources/DiffIndex [12.5kB]  

Get:27 http://ike.egr.msu.edu etch/non-free Sources/DiffIndex [12.5kB]  

Get:28 http://ike.egr.msu.edu etch/contrib Sources/DiffIndex [12.5kB]   

Get:29 2006-09-01-1257.51.pdiff [70.4kB]

Get:30 2006-09-01-1257.51.pdiff [15.9kB]

Get:31 2006-09-01-1257.51.pdiff [351B]   

Bug#389881: SCSI device renaming breaks install

[Rick Thomas]

On Sep 28, 2006, at 6:50 AM, Stephen Gran wrote:



Either use udev rules to map the RAID array to a consistent device  
name,

or use filesystem labels in fstab and menu.lst.



Which is great if you know about the problem and can deal with it in  
advance.  Just because it's listed in the errata is not an excuse for  
not fixing the problem.   Is it possible to generalize the fix that  
worked for network interfaces to also deal with disk drives?


It's definitely a case where the Debian Installer does not "just work".

Rick



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

Bug#390565: Patch for the graphical installer on PPC boxes

[Rick Thomas]

On Oct 1, 2006, at 7:34 PM, Sven Luther wrote:

I have built the images, and tested it on radeon with the 9200SE, i  
confirm
that disable-module=radeon is uncomented, and the bugs (white-on- 
white during

selection, broken font in the console) are gone this way.

I am uploading the images i built to http://people.debian.org/ 
~luther/g-i so

we others can test. I will do an announcement on debian-powerpc now.


When I tried this mini.iso on a G4/533MHz "QuickSilver" tower with  
"ATY Rage128" graphics, I saw the white-on-white problem.  So it's  
not gone away completely.


Rick



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

Bug#390565: Patch for the graphical installer on PPC boxes

[Rick Thomas]

On Oct 2, 2006, at 3:34 AM, Sven Luther wrote:


When I tried this mini.iso on a G4/533MHz "QuickSilver" tower with
"ATY Rage128" graphics, I saw the white-on-white problem.  So it's
not gone away completely.


Normal, your aty rage128 is not a radeon, and is thus using  
whatever driver is
using the aty rage128, and thus the white-on-white problem is not  
gone for

you.

Can you check which graphic driver you are using, and submit a  
modification of

attilio's patch so you also disable the aty-rage128 driver ?


Happy to do...

Can you tell me how to check which graphic driver it's using?

Rick



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

Bug#390565: Patch for the graphical installer on PPC boxes

[Rick Thomas]

On Oct 2, 2006, at 2:28 PM, Sven Luther wrote:


 I am building a new image, and uploading it, stay tuned.


I tried the new image (from http://people.debian.org/~luther/g-i/ 
powerpc/gtk-miniiso/mini.iso dated 02-Oct-2006 05:07) on my PowerMac  
3,5 with the Radeon video card.


/proc/cpuinfo=  PowerMac3,5 [69 (PowerMac G4/733MHz Silver)]
lspci=  ATI Technologies Inc Radeon RV200 QW [Radeon 7500]
/proc/fb=   0 ATI Radeon QW


When I did "DEBIAN_FRONTEND=gtk ; debian-installer",

I got dropped into the text mode installer with the error message:  
"Framebuffer not available. Disabling graphical frontend."
I tried it with all combinations of enable/disable of "linux_input"  
and "radeon", with the same results.




I also tried it on another machine with ATI Rage128 graphics card

/proc/cpuinfo=  PowerMac3,1 (PowerMac G4 AGP Graphics)
lspci=  ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS
/proc/fb=   0 ATY Rage128

I only did this one with both disables in place (unmodified /etc/ 
directfbrc file).


It also gave me the same error message about "Framebuffer not  
available" and dropped me in the text mode installer.


Is it possible that this image is broken in some fundamental way?

Hope this helps!

Rick



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

Bug#342053: [directfb-users] Bug#342053: DirectFrameBuffer crashes on PPC systems if HW accelerated drivers are used

[Rick Thomas]

On Oct 3, 2006, at 9:25 AM, Attilio Fiandrotti wrote:

fbset exists as an udeb [1]: rick, you could boot textual, pull the  
ppc version in the d-i using wget, unpack it with anna and run it.

Maybe fbset should become part of the g-i ?

Attilio

[1] http://packages.debian.org/unstable/debian-installer/fbset-udeb


I'm with you up through wget.  But I've never met anna, though I'm  
sure she's a very nice person!  (-;


Either detailed instructions on how to do unpack a udeb with anna or  
a pointer to a manual that I can read will be necessary.



Enjoy!

Rick



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

Bug#390565: Patch for the graphical installer on PPC boxes

[Rick Thomas]

On Oct 3, 2006, at 4:10 AM, Attilio Fiandrotti wrote:

Did you enter "export DEBIAN_FRONTEND=gtk" or "DEBIAN_FRONTEND=gtk"  
before running debian-installer?
In the latter case, the DEBIAN_FRONTEND variable simply may not  
have been made visible to debconf, try again with "export ..."  
before running debian-installer and let's see if this works.



My bad.  My brain knew what it had to do, but the message didn't make  
it all the way to my fingers!


In any case, the results of doing it again (right, this time) [on the  
PowerMac3,5 with Radeon] are attached.


No change, as far as I can see.

Hope it helps!

Rick



error_messages4
Description: Binary data


error_messages3
Description: Binary data


error_messages2
Description: Binary data


error_messages1
Description: Binary data


configuration
Description: Binary data

Bug#382129: Beta3 won't boot on OldWorld PowerPC Mac

[Rick Thomas]

On Aug 18, 2006, at 7:59 AM, Aurélien GÉRÔME wrote:


Hi,

On Sun, Aug 13, 2006 at 03:19:18AM -0400, Rick Thomas wrote:

Has *anybody* had any success getting the "Linux version 2.6.16-2-
powerpc (Debian 2.6.16-17)" kernel to boot an OldWorld machine with
BootX?  Or *any* kernel after 2.6.15?


I think the anwser is plainly no. :(


Perhaps the Debian PTBs should simply admit that PowerPC OldWorld  
Macintosh is an unsupported sub-arch for Debian etch?   /-8




Well, you would be better off using miBoot anyway. I think I will
produce miBoot floppies for the last Debian kernel for you to try...


One thing I've discovered:  The miboot floppy at http:// 
people.debian.org/~wouter/d-i/powerpc-miboot/daily/powerpc/floppy/  
contain the "2.6.16-2-powerpc-miboot (Debian 2.6.16-7)" kernel, which  
is the same base version (different config, presumably) as the kernel  
on the beta3 CDs.  And that kernel (the one on the miboot floppy)  
boots just fine(*) on my beige G3.  So the problem seems to be a  
configuration issue, not anything fundamental.


(*) Well... almost "just fine".  There is a small problem with the  
video parameters -- some columns of the text on the screen seem to  
flicker.  If I could figure out how to modify the kernel command line  
arguments (specifically the video options) on the floppy, I might be  
able to fix that.  Interestingly, "works just fine" only applies to  
the "boot" floppy.  The "ofonlyboot" floppy does not work -- it gets  
the same symptoms as I described in Bug#369760, and as someone else  
has described in Bug#380187.






What has changed between the Sarge kernel (which boots just fine) and
this one that would have such a catastrophic effect?


Maybe the image is too heavy, some kernel defines changed, or BootX
cannot find the sections of the image anymore? We cannot fiddle with
BootX source code to see what happens, but we will be able with miBoot
source code when it will be ready. :)


Currently, miboot (leaving aside issues of "freeness") only works for  
floppies?  Do you think there is any chance of it's working for  
booting off of CDs or hard-disks, once we can fiddle with the source  
code?




Cheers,
--
 .''`.   Aurélien GÉRÔME
: :'  :
`. `'`   Free Software Developer
  `- Unix Sys & Net Admin

Bug#383663: Latest update breaks ntp

[Rick Thomas]

Package: ntp

I just did an aptitude update/upgrade of an etch system.  It resulted  
in deleting ntp, ntp-simple, and ntp-server, leaving me without a  
function ntp daemon.


Rick

"Not the sort of behavior you ordinarily expect from a major appliance"
  - ghostbusters




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

Bug#383663: [pkg-ntp-maintainers] Bug#383663: Latest update breaks ntp

[Rick Thomas]

Thanks for your prompt reply...

The Debian bug reporting system is a bit of mystery to me.  How do I  
"complain to the aptitude developers then"?


Actually, I think it may be a problem with dependancy setting in the  
package  (maybe? -- that whole dependency business in pretty  
mysterious too...)  Is that in your purview?


Thanks,

Rick

PS: I'd be happy to RTFM.  Is there an FM I can R on any of this?

PPS:  Why is everybody in Debian so bad tempered?

On Aug 18, 2006, at 12:24 PM, Peter Eisentraut wrote:


Am Freitag, 18. August 2006 17:33 schrieb Rick Thomas:

I just did an aptitude update/upgrade of an etch system.  It resulted
in deleting ntp, ntp-simple, and ntp-server, leaving me without a
function ntp daemon.


Complain to the aptitude developers then.  ntp is certainly not  
responsible

that aptitude removes ntp.




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

Bug#382129: Beta3 won't boot on OldWorld PowerPC Mac

[Rick Thomas]

On Aug 18, 2006, at 2:31 PM, Aurélien GÉRÔME wrote:


What is PTBs? :)


Powers that be...

Bug#382129: Beta3 won't boot on OldWorld PowerPC Mac

[Rick Thomas]

On Aug 18, 2006, at 2:31 PM, Aurélien GÉRÔME wrote:





Wow!  great!  I'm really glad somebody's working on that.

Do you think it will be ready for inclusion in etch at release time?

Rick

Bug#382129: Beta3 won't boot on OldWorld PowerPC Mac

[Rick Thomas]

On Aug 18, 2006, at 2:31 PM, Aurélien GÉRÔME wrote:


Well, aside the issue of booting, the kernel runs just
fine and so does the user space... As you can look at
, I think
it is partially admitted in "Oldworld powerpc boot floppies will not
work as miboot is not included".


I think that is just referring to the fact that miboot is not (yet)  
"free" so it can't be included in an official debian distribution.   
As noted, wouter provides floppy images with a working miboot and a  
working kernel (almost -- modulo the video problems I've mentioned.)


I don't think the errata takes any notice of the fact that, quite  
independent of "freeness" considerations, there is *no* working boot  
loader for the 2.6.16 kernel on an OldWorld Mac.  I've tried both  
bootx and quik and neither of them work on my beige G3.  In it's  
current state, even if it were free, miboot would not be a workable  
solution because it only works from floppies.


Rick

Bug#383690: Latest update breaks ntp

[Rick Thomas]

Package: aptitude

I just did an aptitude update/upgrade of an etch system.  It resulted  
in deleting ntp, ntp-simple, and ntp-server, leaving me without a  
functioning ntp daemon.


Rick

"Not the sort of behavior you ordinarily expect from a major appliance"
  - ghostbusters




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

Bug#382129: Beta3 won't boot on OldWorld PowerPC Mac

[Rick Thomas]

On Aug 18, 2006, at 5:58 PM, Aurélien GÉRÔME wrote:


On Fri, Aug 18, 2006 at 02:52:24PM -0400, Rick Thomas wrote:

On Aug 18, 2006, at 2:31 PM, Aurélien GÉRÔME wrote:

What is PTBs? :)

Powers that be...


On Fri, Aug 18, 2006 at 11:44:23AM -0400, Rick Thomas wrote:

Perhaps the Debian PTBs should simply admit that PowerPC OldWorld
Macintosh is an unsupported sub-arch for Debian etch?   /-8


Okay, in that case, I strongly disagree. That would be like saying
the efforts to get it working until now are worthless. The individual
behind debian-installer has already kicked out Sven without any
concern for the PowerPC port well being.

Killing the OldWorld subarch in the PowerPC port would simply get  
Piotr

(I think) and I (surely) not caring anymore about miBoot... After
all, I know how to proceed with it the hard way, so the installation
easiness does not matter to me. It is only more fun for me for it to
become easy. :)

I sincerely hope I will succeed getting an access to the
debian-installer SVN repository to work on miboot targets and on
miboot-installer...


I have to agree that your work on miboot is the only real light I can  
see in the darkness surrounding Debian support of OldWorld  
PowerMacs.  I sincerely wish you luck in getting the resources  
(physical and political) that you need to finish the job.  If there  
is anything I can do to help with the process, please do not hesitate  
to ask.



Rick

Bug#382129: Beta3 won't boot on OldWorld PowerPC Mac

[Rick Thomas]

On Aug 18, 2006, at 6:43 PM, Sven Luther wrote:


On Sat, Aug 19, 2006 at 12:18:23AM +0200, Sven Luther wrote:

On Fri, Aug 18, 2006 at 11:58:07PM +0200, Aurélien GÉRÔME wrote:

On Fri, Aug 18, 2006 at 02:52:24PM -0400, Rick Thomas wrote:

On Aug 18, 2006, at 2:31 PM, Aurélien GÉRÔME wrote:

What is PTBs? :)

Powers that be...


On Fri, Aug 18, 2006 at 11:44:23AM -0400, Rick Thomas wrote:

Perhaps the Debian PTBs should simply admit that PowerPC OldWorld
Macintosh is an unsupported sub-arch for Debian etch?   /-8


Okay, in that case, I strongly disagree. That would be like saying
the efforts to get it working until now are worthless. The  
individual

behind debian-installer has already kicked out Sven without any
concern for the PowerPC port well being.


There is already an alternative installer planed once etch is  
released, which
will contain fixes for all those issues the d-i team left dying on  
the

road-side.


all those powerpc issues.


Thanks!  If there is anything I can do to help, please let me know.

Rick

Bug#382129: Beta3 won't boot on OldWorld PowerPC Mac

[Rick Thomas]

Well... That's interesting news.  And I'm glad you're having success  
with your system.


But, unfortunately, the bottom line for this bug report is still that  
nobody has yet succeeded in getting the 2.6.16 kernel to boot under  
BootX.


Keep in touch.  I'll be particularly interested in hearing of your  
experiences upgrading to Dapper.


Enjoy!

Rick


On Aug 20, 2006, at 3:25 AM, Harold Johnson wrote:

Oh, and since I forgot to mention it, the kernel version I  
currently (at this moment) have installed is 2.6.12-9; that's after  
simply installing Breezy.  Once I upgrade to Dapper again, I'll be  
using whatever version that is -- or I'll jump to Debian and do the  
same.  I'll try to remember to post that version number here so  
that you'll know if I got up to 2.6.16 using my method.  All I know  
for certain is that I've been able to get to Dapper using this  
installation method in the past.


Harold

On 8/19/06, Harold Johnson <[EMAIL PROTECTED]> wrote:
You have great timing; I wouldn't have had that answer for you  
earlier today, because I wasn't certain which kernel version I had  
installed.  I am writing down the entire process of setting up a  
triple-booting system, which will be running Linux, OS X, and OS  
9.  (This has been done many times before, I'm sure, but not by  
me!)  Thus far, I've installed OS 9, Ubuntu Linux, and I'm  
currently installing OS X (Panther) on the third (and final)  
partition.


I'll be adding to some online documentation, but hopefully the  
following info. will fill in some of the gaps:


-- 2 Mac OS (hfs+) partitions and one unallocated space using an OS  
9 installation disk.  The first partition will be for OS X, the  
second is for OS 9, and the free space is for Linux. 

-- After installing OS 9 and BootX, installed Ubuntu Server  
(Breezy).  This info. is probably the most helpful for you; I've  
tried on multiple occasions to install the latest flavors of Debian  
using BootX, to no avail.  The same goes with the latest Ubuntu  
versions (Dapper); only Breezy installs on my OldWorld PowerBook.   
Once I've installed Breezy, it's easy enough to upgrade to Dapper  
by simply editing the repositories (replacing all instances of  
"Breezy" with "Dapper") and then using apt-get to update the  
system.  I imagine it's possible to use this same technique to  
update to the latest version of Debian; wouldn't you think? 


Thanks for sending along your script,

Harold


On 8/19/06, Rick Thomas <[EMAIL PROTECTED]> wrote:
On Aug 19, 2006, at 6:29 PM, Harold Johnson wrote:

> In the meantime, I can continue using BootX -- not a real elegant
> solution, IMHO, but it works.

Hi Harold,

What magic did you have to use to get BootX to boot a 2.6.16 kernel
for you?

Thanks!

Rick






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

Bug#380105: Show current hour in hardware clock question

[Rick Thomas]

On Aug 25, 2006, at 10:57 AM, Christian Perrier wrote:

I am not sure, but in the graphical installer, we could add a  
clock widget
somewhere from the start, and do clock setting pretty early one  
(we probably
only need hwclock and a little menu thingy), it can even be done  
before

base-install and partman, since there are no extra dependencies.


There has been such kind of suggestion last weeks but it has been
ruled out. I guess that the rationale is mostly avoiding features that
are only available in some D-I flavours.

So, if a method to set the clock is offerred, it has to work for all
interfaces.


In some cases it's not possible (e.g. no hardware clock.)  In some  
cases it's possible but not desirable (e.g. hardware clock exists but  
is known to be wrong and porters have decided to ignore it during  
system initialization until access to an external clock is available.)


But it seems a shame to ban a useful tool just because some people  
can't or won't use it...


My two cents worth,

Rick



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

Bug#381875: loop-AES key generation requires tiresome typing

[Rick Thomas]

On Oct 10, 2006, at 3:39 PM, James Westby wrote:


I had a couple of idea while I was typing to generate keys in this
fashion. Here they are in no particular order.

1) Make a game that involves typing,


Doesn't aptitude have a minesweeper game built in?  Would that work?

Rick



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

Bug#382129: Is now a good time to revisit installer not booting on OldWorld PowerMac beige G3?

[Rick Thomas]

Is there someone out there who will work with me to get a kernel that  
boots to run debian-installer on my beige G3 PowerMac (OldWorld)  
machine?


As I reported in Bug#382129 regarding the Linux-powerpc 2.6.16 kernel  
not booting on my OldWorld test machine, I now find that the 2.6.17  
kernel in the latest daily d-i ISOs also will not boot on OldWorld.   
The console messages are essentially the same as in Bug#382129.  As  
expected, It boots OK on my G4 NewWorld test machine.


Recently, there was an email from someone who managed to configure a  
2.6.16 (I think it was) kernel that would boot on his OldWorld  
machine.  It involved making the ide disk driver resident, I think.


I'm not a kernel hacker, so I can't do that part myself.  But I've  
got hardware I can test things on, and I'd be willing to give someone  
who knows what they are doing an account on one of those machines if  
they will work with me on solving this problem.


Any takers?

If not, I think it may be time to withdraw OldWorld PowerMacs from  
the list of hardware supported by the Debian Installer.


Rick



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

Bug#382129: Is now a good time to revisit installer not booting on OldWorld PowerMac beige G3?

[Rick Thomas]

On Sep 16, 2006, at 3:05 PM, Sven Luther wrote:


On Sat, Sep 16, 2006 at 09:50:03AM +0200, Frans Pop wrote:

On Saturday 16 September 2006 09:09, Rick Thomas wrote:
Is there someone out there who will work with me to get a kernel  
that

boots to run debian-installer on my beige G3 PowerMac (OldWorld)
machine?


I'd like to see that happen.


If not, I think it may be time to withdraw OldWorld PowerMacs from
the list of hardware supported by the Debian Installer.


Note that as I understand there are also problems booting the kernel
outside the installer (i.e. just upgrading an installed system), this
does not seem to be a Debian Installer issue, but rather a powerpc  
kernel

or kernel configuration issue.


Its actually a problem with the ramdisk generators and/or  
bootloaders, not the

kernel proper.


Actually, from the symptoms I'm seeing, it may not be getting far  
enough to encounter ramdisk problems. (Not to say there are no such  
ramdisk problems, just that what I'm seeing is not diagnostic for  
them.)  I gave fairly detailed notes in the previous bug report,  
Bug#382129.  Let me know if you want more information.


If Sven is right, that leaves bootloaders.

However, I'm not completely convinced yet that it's not a kernel  
configuration problem.  My evidence for this is that the miboot  
floppy with a 2.6.16 kernel on it will boot and read it's ramdisk  
floppy.  From this I conclude that it is *possible* to build a 2.6.16  
kernel (and by inference, a 2.6.17 kernel) that will boot an OldWorld  
machine.  If so, the only question is whether such a configuration is  
acceptable as a general-purpose kernel for PowerMac machines,  
including NewWorld?


Rick




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

Bug#388159: missing lspci on a fresh install

[Rick Thomas]

Package: base

On Sep 18, 2006, at 4:57 PM, Frans Pop wrote:


On Monday 18 September 2006 21:49, Rick Thomas wrote:

On Sep 18, 2006, at 10:17 AM, De Leeuw Guy wrote:

Frans Pop a écrit :

The d-i team is not responsible for what is part of the base
system and what is not.


Then who is?  Where should I send a bug report?


What is your rationale for including it?
lspci is hardly an essential tool (although it _is_ highly useful of
course, but so are a couple of 100 other tools that are not  
included)...


Correct place to file a bug report would be the pseudo package  
"base", but

I strongly suggest you do not file a bug for this.


This has been discussed before.

Since the install-report template requests the output of lspci, I  
would think you -- of all folks -- would want it as part of the base  
system.


As things stand, it gets dragged in most of the time because the  
"Desktop" task needs it.  But if I chose to do a minimal install  
without including the Desktop task (say for example because I just  
want to test a new part of the debian installer and I don't want to  
wait for the whole Desktop task to get installed) well, lspci isn't  
there.


Another use case for including pci-utils (the parent package of  
lspci) in the base-system is for a server install, where the Desktop  
task is not likely to be wanted, but the utilities in pci-utils are  
likely to be needed.


But, as you point out, "The d-i team is not responsible for what is  
part of the base system and what is not."  So I'll just submit a bug  
report to "base" and let those who *are* responsible sort it out.

Bug#388328: boot logging fix for ntpdate in /etc/init.d

[Rick Thomas]

Package: ntpdate

I was Poking around in /var/log/syslog recently.  I noticed that  
there was no log entry for ntpdate.  Investigating a little, I found  
that /etc/init.d/ntpdate (alias /etc/rcS.d/S51ntpdate) is called  
before syslogd gets started.


This is OK... The ntpdate call has to occur pretty early in the boot  
process to avoid problems with time stepping backwards (or forwards  
by large amounts) during the rest of the initialization processes.


The net result is that you would only see the ntpdate log entry if  
you turned on bootlogd.  So I turned on bootlogd, just to make sure  
ntpdate was getting called properly.  Lo and behold!  Following a  
reboot, there was no ntpdate entry visible in /var/log/boot.


The problem is that ntpdate is getting called with a "-s" option, but  
syslogd isn't there to catch the log entries.


The attached patch fixes that.

I used "log_action_msg" instead of "log_action_begin_msg" because the  
output of ntpdate is intended to stand alone on a line by itself, not  
as part of a stream of text.


Enjoy!

Rick

== cut here =
[EMAIL PROTECTED]:~$ diff -c /etc/init.d/ntpdate /tmp/ntpdate
*** /etc/init.d/ntpdate Wed Aug  9 08:52:47 2006
--- /tmp/ntpdateTue Sep 19 17:06:08 2006
***
*** 25,32 

  case $1 in
start|force-reload)
!   log_action_begin_msg "Running ntpdate to synchronize  
clock"

!   $PROG -b -s $NTPOPTIONS $NTPSERVERS
log_action_end_msg $?
;;
restart|try-restart|reload)
--- 25,34 

  case $1 in
start|force-reload)
!   # no -s option so output will go to console (and  
bootlog if enabled) when starting up
!   # this happens before syslogd is started, so no point  
in sending it to (nonexistent) syslog

!   log_action_msg "Running ntpdate to synchronize clock"
!   $PROG -b $NTPOPTIONS $NTPSERVERS
log_action_end_msg $?
;;
restart|try-restart|reload)
== cut here =




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

Bug#388328: [pkg-ntp-maintainers] Bug#388328: boot logging fix for ntpdate in /etc/init.d

[Rick Thomas]

On Sep 21, 2006, at 1:42 PM, Peter Eisentraut wrote:


Rick Thomas wrote:

I was Poking around in /var/log/syslog recently.  I noticed that
there was no log entry for ntpdate.  Investigating a little, I found
that /etc/init.d/ntpdate (alias /etc/rcS.d/S51ntpdate) is called
before syslogd gets started.


The latest ntpdate package does not contain an init script.  Please
check with that package if you have ideas how to make the logging more
accessible.



Hmmm... what's the latest ntpdate package version?  On my local test  
etch/powerpc system I just did "aptitude install ntp ntpdate" and it  
put in ntpdate version 1:4.2.2+dfsg.2-1, which included a /etc/init.d/ 
ntpdate and a symlink /etc/rcS.d/S51ntpdate pointing to it.


What am I missing?

Thanks!

Rick




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

Bug#388328: [pkg-ntp-maintainers] Bug#388328: boot logging fix for ntpdate in /etc/init.d

[Rick Thomas]

On Sep 21, 2006, at 5:47 PM, Peter Eisentraut wrote:


Again, check the package in unstable.  That's the direction.


Thanks for the pointer.

I've looked at the ntpdate_4.2.2+dfsg.2-2 stuff now, and I have a  
couple of comments on that.


The first is just an extension of this original bug-report:

It does not make sense to use the "-s" option with ntpdate before  
syslogd has been started.  The if-up.d stuff will most commonly be  
run during system initialization.  The order of things in /etc/rcS.d  
is such that the network initialization will occur before starting  
syslogd (as it must, if syslog is redirected to another host).


But on the other hand, it does make sense to use the "-s" option if  
ntpdate is being called after syslogd is started -- as, for example,  
when bringing up a new network interface without a reboot.


So the logic in /etc/network/if-up.d/ntpdate needs to be a bit like  
the login in the old /etc/init.d/ntpdate in that it knows whether  
it's being called as part of system initialization or on-the-fly  
after initialization.



The second has to do with interaction of ntpdate with the ntp daemon:

Maybe I've missed something, but i see no code that makes sure the  
ntp daemon is stopped when running ntpdate.  My experience is that a  
running ntpd can get badly confused if you run ntpdate at the same time.


Maybe the logic is that, now that ntpd can handle it's own clock  
startup, there's no need to have the two packages installed at the  
same time?  If so, would it be desirable to have them officially  
conflict?



Enjoy!

Rick



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

Bug#388328: [pkg-ntp-maintainers] Bug#388328: boot logging fix for ntpdate in /etc/init.d

[Rick Thomas]

On Sep 21, 2006, at 9:00 PM, Peter Eisentraut wrote:


Rick Thomas wrote:

So the logic in /etc/network/if-up.d/ntpdate needs to be a bit like
the login in the old /etc/init.d/ntpdate in that it knows whether
it's being called as part of system initialization or on-the-fly
after initialization.


But that information is not available in the if-up script.


There are ways to find it out.  If you like, I'll do up and test a  
sample.






Maybe the logic is that, now that ntpd can handle it's own clock
startup, there's no need to have the two packages installed at the
same time?


Yes.


If so, would it be desirable to have them officially conflict?


No.


Forgive me my ignorance.  I'm not an expert on the details of the apt  
dependency process.  Can you educate me as to why it's not a good idea?


Thanks,

Rick



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

Bug#388328: [pkg-ntp-maintainers] Bug#388328: boot logging fix for ntpdate in /etc/init.d

[Rick Thomas]

On Sep 22, 2006, at 4:18 AM, Peter Eisentraut wrote:


Am Freitag, 22. September 2006 04:25 schrieb Rick Thomas:

But that information is not available in the if-up script.


There are ways to find it out.  If you like, I'll do up and test a
sample.


Please.


Will do.  I hope to get back to you in a couple of days(*).




If so, would it be desirable to have them officially conflict?


No.


Forgive me my ignorance.  I'm not an expert on the details of the apt
dependency process.  Can you educate me as to why it's not a good  
idea?


Well, they don't actually conflict.  They are just usually not used  
together.
In particular, considering that in sarge, they usually *are* used  
together,
it would probably upset quite a few people if we turned this around  
during

the upgrade.

If may make sense to drop the -u option from the default ntpdate  
options, so
ntpdate doesn't run when ntpd is running.  Do you want to try that  
out?

(see /etc/default/ntpdate)


Happy to.  Once again, give me a day or so to experiment.

(*) The main server for our house fried a disk this morning.  I'm  
still dealing with the details that remain after getting it back in  
working order with a new disk.  So it may take me a bit of time to  
get to do the experiments.  But I *will* do it.


I noticed that the new ntp/ntpdate packages made it into etch  
yesterday.  That will make the experiments a bit easier.  I don't  
normally run sid systems, which is why looking at the ntp* packages  
in sid didn't occur to me first think.


Enjoy!

Rick


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

Bug#342053: DirectFrameBuffer crashes on PPC systems if HW accelerated drivers are used

[Rick Thomas]

On Sep 23, 2006, at 6:13 AM, Sven Luther wrote:




Also, about the console font corruption with radeonfb, i would be
interested
in feedback of if it is a powerpc only issue, or ppc stuff ?


No idea, i on no radeon boards :(


Someone else ?


I might have a NewWorld Mac with a radeon board...  If so, it's at  
work, so checking will have to wait til Monday.  I'll let you know.





Not sure if we ever had a success with g-i on oldworld, so it is less
important, and my prep box has a sis and a matrox, but g-i is too  
big to boot
on it. I do have a spare matox millenium i could plug in the  
pegasos, and just
got a xgi volari v3xt. Will test with them. nvidia is evil and  
should be

boycotted anyway :)


If you have a kernel that will boot using BootX on an OldWorld beige  
G3 PowerMac, I can give it a try.


Is there an iso I can burn with the necessary stuff on it?  I'm not  
set up to do netbooting at this moment.


Enjoy!

Rick


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

Bug#342053: DirectFrameBuffer crashes on PPC systems if HW accelerated drivers are used

[Rick Thomas]

On Sep 24, 2006, at 5:52 AM, Sven Luther wrote:


On Sun, Sep 24, 2006 at 04:17:58AM -0400, Rick Thomas wrote:


On Sep 23, 2006, at 6:13 AM, Sven Luther wrote:




Also, about the console font corruption with radeonfb, i would be
interested
in feedback of if it is a powerpc only issue, or ppc stuff ?


No idea, i on no radeon boards :(


Someone else ?


I might have a NewWorld Mac with a radeon board...  If so, it's at
work, so checking will have to wait til Monday.  I'll let you know.


Yes, please. Do you remember the model exactly ?




OK.  I have a G4 PowerMac with

:00:10.0 VGA compatible controller: ATI Technologies Inc Radeon  
RV200 QW [Radeon 7500]



Will that be useful?

[EMAIL PROTECTED]:~$ cat /proc/cpuinfo
processor   : 0
cpu : 7450, altivec supported
clock   : 733.31MHz
revision: 0.1 (pvr 8000 0201)
bogomips: 66.30
timebase: 33217233
platform: PowerMac
machine : PowerMac3,5
motherboard : PowerMac3,5 MacRISC2 MacRISC Power Macintosh
detected as : 69 (PowerMac G4 Silver)
pmac flags  : 0010
L2 cache: 256K unified
pmac-generation : NewWorld

Enjoy!

Rick




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

Bug#342053: DirectFrameBuffer crashes on PPC systems if HW accelerated drivers are used

[Rick Thomas]

On Sep 26, 2006, at 4:04 PM, Sven Luther wrote:


On Tue, Sep 26, 2006 at 04:01:15PM -0400, Rick Thomas wrote:



OK.  I have a G4 PowerMac with

:00:10.0 VGA compatible controller: ATI Technologies Inc Radeon
RV200 QW [Radeon 7500]


Should work flawlessly with the current daily-builds.

Friendly,

Sven Luther


Hmmm

Maybe I'm not getting the current daily-build?


On Sep 24, 2006, at 5:34 AM, Frans Pop wrote:

On Sunday 24 September 2006 10:17, Rick Thomas wrote:

Is there an iso I can burn with the necessary stuff on it?  I'm not
set up to do netbooting at this moment.


There is only an iso. Look for gtk-miniiso under powerpc/powerpc64:
http://people.debian.org/~wouter/d-i/powerpc/daily/


So I went there and found


Index of /~wouter/d-i/powerpc/daily/powerpc/gtk-miniiso
NameLast modified   Size  Description

Parent Directory18-Sep-2006 22:16  -
initrd.gz   25-Sep-2006 22:34   9.7M
mini.iso25-Sep-2006 22:45  15.3M
vmlinux 25-Sep-2006 22:45   3.8M
vmlinuz-chrp.initrd 25-Sep-2006 22:56  11.1M

Apache/1.3.33 Server at people.debian.org Port 80


and from which I downloaded and burned the mini.iso

I booted from the CD and got repeating crashes when it tried to  
initialize the graphical installer


messages read in part (manually typed in -- I don't have any way to  
cut-and-paste from the crashed machine...)



  - DirectFB v0.9.25 -
...
 () *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [../../../ 
lib/fusion/reactor.c:853]

...

(*) DirectFB/Graphics: ATI Radeon 7500 (5157) 1.0 (Claudio Ciccani)
(*) DirectFB/Graphics: Acceleration disabled (by 'no-hardware')
(!) DirectFB/FBDev: No supported modes found in /etc/fb.modes and  
current mode not supported!
(!) DirectFB/FBDev: Current mode's pixelformat: rgba 8/0, 8/0, 8/0,  
0/0 (8bit)

(!) DirectFB/Core/layers: Failed to initialize layer 0!
--> Initialization error!
(!) DirectFB/Core: Could not initialize 'layers' core!
--> Initialization error!
(#) DirectFBError [gdk_display_open: DirectFBCreate]:  
Initialization error!


(debconf:1609): Gtk-Warning **: cannot open display:
(process:1641): INFO: kbd-mode: setting console mode to Unicode  
(UTF-8)

(*) DirectFB/Config: Parsing config file '/etc/directfbrc'



Is there a different mini.iso ?


Rick


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

Bug#342053: DirectFrameBuffer crashes on PPC systems if HW accelerated drivers are used

[Rick Thomas]

OK,

I booted from the CD with "install DEBIAN_FRONTEND=newt"
switched to the F2 console when the "choose language" screen came up.
The hardware info you wanted is:


~# cat /proc/cpuinfo | grep motherboard
Motherboard: PowerMac3,5 MacRISC2 MacRISC Power Macintosh

~# cat /proc/fb
0 ATI Radeon QW


Then I did:


~# echo "disable-module=linux_input" >>/etc/directfbrc
~# export DEBIAN_FRONTEND=gtk
~# debian-installer


It crashed when it tried to initialize the graphical installer

messages read in part (manually typed in -- I don't have any way to
cut-and-paste from the crashed machine...)



(process:1076): INFO kbd-mode: setting console mode to Unicode (UTF-8)

(*) DirectFB/Config: Parsing file '/etc/directfbrc'

 - DirectFB v0.9.25 -


... [ stuff snipped to save typing -- let me know if it's important - 
Rick]



(*) Direct/Modules: suppress module 'linux_input'
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 1104)
() *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [../../../  
lib/fusion/reactor.c:853]

(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmBH)
(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 1105)
(*) DirectFB/Input: IMPS/2 Mouse 1.0 (Convergence GmBH)
(*) DirectFB/Graphics: ATI Radeon 7500 (5157) 1.0 (Claudio Ciccani)
(*) DirectFB/Graphics: Acceleration disabled (by 'no-hardware')
(!) DirectFB/FBDev: No supported modes found in /etc/fb.modes and   
current mode not supported!
(!) DirectFB/FBDev: Current mode's pixelformat: rgba 8/0, 8/0,  
8/0,  0/0 (8bit)

(!) DirectFB/Core/layers: Failed to initialize layer 0!
   --> Initialization error!
(!) DirectFB/Core: Could not initialize 'layers' core!
   --> Initialization error!
(#) DirectFBError [gdk_display_open: DirectFBCreate]:  
Initialization error!


(debconf:1099): Gtk-Warning **: cannot open display:




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

Bug#342053: DirectFrameBuffer crashes on PPC systems if HW accelerated drivers are used

[Rick Thomas]

OK,

I booted from the CD with "install DEBIAN_FRONTEND=newt"
switched to the F2 console when the "choose language" screen came up.

Then I did:


~# echo "disable-module=radeon" >>/etc/directfbrc
~# echo "no-hardware" >>/etc/directfbrc
~# export DEBIAN_FRONTEND=gtk
~# debian-installer


It crashed when it tried to initialize the graphical installer

messages read in part (manually typed in -- I don't have any way to
cut-and-paste from the crashed machine...)



(process:1074): INFO kbd-mode: setting console mode to Unicode (UTF-8)

(*) DirectFB/Config: Parsing file '/etc/directfbrc'

 - DirectFB v0.9.25 -


... [ stuff snipped to save typing -- let me know if it's important - 
Rick]



(*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 1101)
(*) Direct/Thread: Running 'Linux Input' (INPUT, 1102)
() *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [../../../  
lib/fusion/reactor.c:853]


... [more stuff snipped -Rick]


(*) Direct/Modules: supress module 'radeon'
(*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (convergence  
integrated media GmBH)
(!) DirectFB/FBDev: No supported modes found in /etc/fb.modes and   
current mode not supported!
(!) DirectFB/FBDev: Current mode's pixelformat: rgba 8/0, 8/0,  
8/0,  0/0 (8bit)

(!) DirectFB/Core/layers: Failed to initialize layer 0!
   --> Initialization error!
(!) DirectFB/Core: Could not initialize 'layers' core!
   --> Initialization error!
(#) DirectFBError [gdk_display_open: DirectFBCreate]:  
Initialization error!


(debconf:1097): Gtk-Warning **: cannot open display:





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

Bug#342053: DirectFrameBuffer crashes on PPC systems if HW accelerated drivers are used

[Rick Thomas]

On Sep 27, 2006, at 7:03 PM, Rick Thomas wrote:

(!) DirectFB/FBDev: No supported modes found in /etc/fb.modes and   
current mode not supported!
(!) DirectFB/FBDev: Current mode's pixelformat: rgba 8/0, 8/0,  
8/0,  0/0 (8bit)


For what it's worth, there is no file "/etc/fb.modes" in the initrc...

Does that matter?

Enjoy!

Rick



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

Bug#342053: once more without the mouse (part 1)

[Rick Thomas]

This time without the mouse connected



~# echo "disable-module=radeon" >>/etc/directfbrc
~# echo "no-hardware" >>/etc/directfbrc
~# export DEBIAN_FRONTEND=gtk
~# debian-installer


As usual, it crashed when it tried to initialize the graphical  
installer.


Messages were substantially the same as before with minor variations  
attributable to the lack of a USB mouse.



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