Re: Request assistance with monotone package on alpha, hppa, mipsel, powerpc, s390

[Grant Grundler]

On Mon, Sep 03, 2007 at 06:59:28PM -0700, Zack Weinberg wrote:
> I'm one of the maintainers of the Debian package of monotone; I'm also
> one of its upstream developers.  For the new 0.36-1 package presently
> in unstable, we decided to run the program's testsuite during the
> build.  This found failures on many architectures - a mixed blessing,
> since on the one hand it appears that the program has catastrophic
> bugs that need fixing, but on the other hand, now the package has been
> kicked out of testing. :-(

Zack,
I kicked this off on my testing/unstable hybrid hppa box:
dpkg-buildpackage -rfakeroot -uc -us

Source/Build tree is on:
iou.parisc-linux.org/~grundler/monotone-0.36/

hppa is a 32-bit user space and this system is running a 64-bit kernel.

Please let me know off list if you would like access to that machine
and/or ia64-linux machines.

cheers,
grant

> This message is going out to all the porter lists for which the
> monotone package presently FTBFS because of testsuite failures.  I am
> not a DD (the package is being sponsored by Ludovic Brenta) so I do
> not have access to any of the Debian porting hosts, nor do I have
> other access to any of your architectures.
> 
> I would therefore greatly appreciate assistance with these bugs.  If
> you have time to debug the thing yourself and send patches to
> [EMAIL PROTECTED], that is of course the most helpful thing
> you could do.  Failing that, the next most helpful possibility is if
> you are willing to grant me access (unprivileged only is fine) to a
> machine under your control, and install monotone's build-dependencies
> on that machine.  If you can't do that either, at the least we might
> have a chance of guessing what the problem is if you built the package
> to the point where it fails (using a method that does not destroy the
> build tree when the build fails), then tar up the tester_dir/
> directory and the "mtn" binary and send them to me.
> 
> Thanks in advance,
> zw
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


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

Re: Request assistance with monotone package on alpha, hppa, mipsel, powerpc, s390

[Lennart Sorensen]

On Mon, Sep 03, 2007 at 06:59:28PM -0700, Zack Weinberg wrote:
> I'm one of the maintainers of the Debian package of monotone; I'm also
> one of its upstream developers.  For the new 0.36-1 package presently
> in unstable, we decided to run the program's testsuite during the
> build.  This found failures on many architectures - a mixed blessing,
> since on the one hand it appears that the program has catastrophic
> bugs that need fixing, but on the other hand, now the package has been
> kicked out of testing. :-(
> 
> This message is going out to all the porter lists for which the
> monotone package presently FTBFS because of testsuite failures.  I am
> not a DD (the package is being sponsored by Ludovic Brenta) so I do
> not have access to any of the Debian porting hosts, nor do I have
> other access to any of your architectures.
> 
> I would therefore greatly appreciate assistance with these bugs.  If
> you have time to debug the thing yourself and send patches to
> [EMAIL PROTECTED], that is of course the most helpful thing
> you could do.  Failing that, the next most helpful possibility is if
> you are willing to grant me access (unprivileged only is fine) to a
> machine under your control, and install monotone's build-dependencies
> on that machine.  If you can't do that either, at the least we might
> have a chance of guessing what the problem is if you built the package
> to the point where it fails (using a method that does not destroy the
> build tree when the build fails), then tar up the tester_dir/
> directory and the "mtn" binary and send them to me.

I am currently attempting a build in my unstable chroot on my alpha.  It
might take a while.  My mipsel isn't hooked up at the moment so I can't
try that one (and it would take more than a while on it).  I don't own
any hppa, ppc or s390 at this time.  I only have m68k, mipsel, sparc,
alpha, x86 and amd64, so far, and have access to arm.  Well and a mips
(not el) but it isn't supported by linux at this time. :)

--
Len Sorensen


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

Re: ipmitool for powerpc?

[Charles Plessy]

Le Wed, Sep 05, 2007 at 08:50:35PM +0200, Hannes Schulz a écrit :
> http://packages.qa.debian.org/i/ipmitool.html says "Architecture: i386 
> amd64 ia64 powerpc".
> 
> But http://packages.debian.org/sid/ipmitool only gives downloads for i386 
> and amd64.
> 
> 
> What does one have to do to make the buildds actually build a version for 
> powerpc ?

Hi,

I am not sure, but because in previous versions powerpc was not listed
as a build arch, it may be that the buildd still ignores it:

http://buildd.debian.org/build.php?pkg=ipmitool
http://buildd.debian.org/fetch.cgi?&pkg=ipmitool&ver=1.8.1-1&arch=powerpc&stamp=1112835983&file=log

(same for ia64)

Maybe you could try to contact the buildd admins? More info here:

http://www.debian.org/doc/manuals/developers-reference/ch-pkgs.en.html#s-porter-automation


Have a nice day,

-- 
Charles Plessy
http://charles.plessy.org
Wako, Saitama, Japan


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

Re: Sleep problems with kernels >= 2.6.21 on powerpc

[Andrew Morton]

> On Wed, 05 Sep 2007 19:47:42 +0200 Stefan Richter <[EMAIL PROTECTED]> wrote:
> Andrew Morton wrote:
> >>> Trying to free already-free IRQ 40
> >>> pci_set_power_state(): 0002:20:0e.0: state=3, current state=5
> >>> firewire_ohci: pci_set_power_state failed with 
> >>> -22<3>pci_device_suspend(): pci_suspend+0x0/0x9c [firewire_ohci]() 
> >>> returns -22
> > 
> > I grepped the whole tree for firewire_ohci and came up blank.  What is it?
> 
> drivers/firewire/fw-ohci.c -> fw-ohci.o -> firewire-ohci.o ->
> firewire-ohci.ko

argh.  It's not the first time that the module system's weird
replace-dash-with-underscore thing has fooled me.

> > But yes, a failed pci_set_power_state() will hurt.  Perhaps this is
> > a result of some recently-added return-value checking fix but as I
> > cannot find the dang code I cannot tell.
> 
> The old ohci1394.c used to ignore pci_set_power_state's return value.
> In the pre 2.6.19-rc1 commit ea6104c22468239083857fa07425c312b1ecb424, I
> added a fail-on-error.  This was toned down to a printk-on-err by pre
> 2.6.19-rc4 commit 346f5c7ee7fa4ebee0e4c96415a7e59716bfa1d0.

OK.

> This was because of Benjamin Herrenschmidt's regression report:
> http://lkml.org/lkml/2006/10/24/13

It's not clear _why_ pci_set_power_state() is failing.

> A trivial post -rc1 compatible fix is coming in a minute.

neato, thanks.


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

ipmitool for powerpc?

[Hannes Schulz]

http://packages.qa.debian.org/i/ipmitool.html says "Architecture: i386 amd64 ia64 
powerpc".

But http://packages.debian.org/sid/ipmitool only gives downloads for i386 and 
amd64.


What does one have to do to make the buildds actually build a version for 
powerpc ?


--
I'm loving it

Hannes


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

Re: Sleep problems with kernels >= 2.6.21 on powerpc

[Randy Dunlap]

Stefan Richter wrote:

Randy Dunlap wrote:

On Wed, 5 Sep 2007 10:07:54 -0700 Andrew Morton wrote:
So here is the output from dmesg that suggested to me that firewire 
might be a problem:

Straightforward regression, two reporters, nothing happening.

(material for ksummit discussion, e.g.)


It's a simple thing in this incident:  I don't read all posts on LKML.
But I typically catch everything where I am in the CC list thanks to the
wonders of sieve.  Andrew, thanks for putting me in the CCs.


I understand.  I just meant the general trend, nothing specific
to this thread.

--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***


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

Re: Sleep problems with kernels >= 2.6.21 on powerpc

[Randy Dunlap]

On Wed, 5 Sep 2007 10:07:54 -0700 Andrew Morton wrote:

> > On 30 Aug 2007 22:42:46 +0200 "Tim Teulings" <[EMAIL PROTECTED]> wrote:
> > Hello!
> > 
> > > I don't have traces at hand and due to lack of time cannot reproduce it 
> > > up to tomorrow. However this hint may speed up your analysis!
> > 
> > Sorry for the delay, but my desktop PC had an urgent hard disk problem I 
> > had to fix ASASP.
> > 
> > So here is the output from dmesg that suggested to me that firewire 
> > might be a problem:
> 
> Straightforward regression, two reporters, nothing happening.

(material for ksummit discussion, e.g.)

> > > usb_endpoint usbdev2.2_ep81: PM: suspend 0->2, parent 2-1:1.0 already 2
> > > usb_device usbdev1.1: PM: suspend 0->2, parent usb1 already 2
> > > usb_endpoint usbdev1.1_ep81: PM: suspend 0->2, parent 1-0:1.0 already 2
> > > hub 1-0:1.0: PM: suspend 2->2, parent usb1 already 2
> > > usb_endpoint usbdev1.1_ep00: PM: suspend 0->2, parent usb1 already 2
> > > eth2: Airport entering sleep mode
> > > eth0: suspending, WakeOnLan disabled
> > > pci_set_power_state(): 0002:20:0e.0: state=3, current state=5
> > > firewire_ohci: pci_set_power_state failed with 
> > > -22<3>pci_device_suspend(): pci_suspend+0x0/0x9c [firewire_ohci]() 
> > > returns -22
> > > suspend_device(): pci_device_suspend+0x0/0x98() returns -22
> > > Could not suspend device 0002:20:0e.0: error -22
> > > eth0: resuming
> > > PHY ID: 4061e4, addr: 0
> > > eth2: Airport waking up
> > > eth2: New link status: Connected (0001)
> > > hda: Enabling Ultra DMA 2
> > > eth0: Link is up at 100 Mbps, full-duplex.
> > > eth0: Pause is disabled
> > > ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> > > hdb: Enabling Ultra DMA 2
> > > usb_endpoint usbdev1.1_ep00: PM: resume from 0, parent usb1 still 2
> > > usb_endpoint usbdev1.1_ep81: PM: resume from 0, parent 1-0:1.0 still 2
> > > usb_device usbdev1.1: PM: resume from 0, parent usb1 still 2
> > > Driver sleep failed
> > > Sleep rejected by devices
> > > adb: starting probe task...
> > > adb devices: [2]: 2 c4 [3]: 3 1 [7]: 7 1f
> > > ADB keyboard at 2, handler 1
> > > ADB mouse at 3, handler set to 4 (trackpad)
> > > adb: finished probe task...
> > > usb_device usbdev1.1: PM: suspend 0->2, parent usb1 already 2
> > > usb_endpoint usbdev1.1_ep81: PM: suspend 0->2, parent 1-0:1.0 already 2
> > > hub 1-0:1.0: PM: suspend 2->2, parent usb1 already 2
> > > usb_endpoint usbdev1.1_ep00: PM: suspend 0->2, parent usb1 already 2
> > > eth2: Airport entering sleep mode
> > > eth0: suspending, WakeOnLan disabled
> > > Trying to free already-free IRQ 40
> > > pci_set_power_state(): 0002:20:0e.0: state=3, current state=5
> > > firewire_ohci: pci_set_power_state failed with 
> > > -22<3>pci_device_suspend(): pci_suspend+0x0/0x9c [firewire_ohci]() 
> > > returns -22
> 
> I grepped the whole tree for firewire_ohci and came up blank.  What is it?

See drivers/firewire/Makefile

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***


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

Re: Sleep problems with kernels >= 2.6.21 on powerpc

[Andrew Morton]

> On 30 Aug 2007 22:42:46 +0200 "Tim Teulings" <[EMAIL PROTECTED]> wrote:
> Hello!
> 
> > I don't have traces at hand and due to lack of time cannot reproduce it 
> > up to tomorrow. However this hint may speed up your analysis!
> 
> Sorry for the delay, but my desktop PC had an urgent hard disk problem I 
> had to fix ASASP.
> 
> So here is the output from dmesg that suggested to me that firewire 
> might be a problem:

Straightforward regression, two reporters, nothing happening.

> > usb_endpoint usbdev2.2_ep81: PM: suspend 0->2, parent 2-1:1.0 already 2
> > usb_device usbdev1.1: PM: suspend 0->2, parent usb1 already 2
> > usb_endpoint usbdev1.1_ep81: PM: suspend 0->2, parent 1-0:1.0 already 2
> > hub 1-0:1.0: PM: suspend 2->2, parent usb1 already 2
> > usb_endpoint usbdev1.1_ep00: PM: suspend 0->2, parent usb1 already 2
> > eth2: Airport entering sleep mode
> > eth0: suspending, WakeOnLan disabled
> > pci_set_power_state(): 0002:20:0e.0: state=3, current state=5
> > firewire_ohci: pci_set_power_state failed with -22<3>pci_device_suspend(): 
> > pci_suspend+0x0/0x9c [firewire_ohci]() returns -22
> > suspend_device(): pci_device_suspend+0x0/0x98() returns -22
> > Could not suspend device 0002:20:0e.0: error -22
> > eth0: resuming
> > PHY ID: 4061e4, addr: 0
> > eth2: Airport waking up
> > eth2: New link status: Connected (0001)
> > hda: Enabling Ultra DMA 2
> > eth0: Link is up at 100 Mbps, full-duplex.
> > eth0: Pause is disabled
> > ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> > hdb: Enabling Ultra DMA 2
> > usb_endpoint usbdev1.1_ep00: PM: resume from 0, parent usb1 still 2
> > usb_endpoint usbdev1.1_ep81: PM: resume from 0, parent 1-0:1.0 still 2
> > usb_device usbdev1.1: PM: resume from 0, parent usb1 still 2
> > Driver sleep failed
> > Sleep rejected by devices
> > adb: starting probe task...
> > adb devices: [2]: 2 c4 [3]: 3 1 [7]: 7 1f
> > ADB keyboard at 2, handler 1
> > ADB mouse at 3, handler set to 4 (trackpad)
> > adb: finished probe task...
> > usb_device usbdev1.1: PM: suspend 0->2, parent usb1 already 2
> > usb_endpoint usbdev1.1_ep81: PM: suspend 0->2, parent 1-0:1.0 already 2
> > hub 1-0:1.0: PM: suspend 2->2, parent usb1 already 2
> > usb_endpoint usbdev1.1_ep00: PM: suspend 0->2, parent usb1 already 2
> > eth2: Airport entering sleep mode
> > eth0: suspending, WakeOnLan disabled
> > Trying to free already-free IRQ 40
> > pci_set_power_state(): 0002:20:0e.0: state=3, current state=5
> > firewire_ohci: pci_set_power_state failed with -22<3>pci_device_suspend(): 
> > pci_suspend+0x0/0x9c [firewire_ohci]() returns -22

I grepped the whole tree for firewire_ohci and came up blank.  What is it?

But yes, a failed pci_set_power_state() will hurt.  Perhaps this is
a result of some recently-added return-value checking fix but as I
cannot find the dang code I cannot tell.

> > suspend_device(): pci_device_suspend+0x0/0x98() returns -22
> > Could not suspend device 0002:20:0e.0: error -22
> > eth0: resuming
> > PHY ID: 4061e4, addr: 0
> > eth2: Airport waking up
> > eth2: New link status: Connected (0001)
> > hda: Enabling Ultra DMA 2
> > hdb: Enabling Ultra DMA 2
> > eth0: Link is up at 100 Mbps, full-duplex.
> > eth0: Pause is disabled
> 
> The problem wa sinitiated by closing the lid. The iBook then seems to 
> permanetly try to go to sleep (I can hear the cd-rom drive get 
> periodically initialized). So above contains more than one iteration.
> 
> The kernel is:
> > Linux kismet 2.6.22-1-powerpc #1 Sun Jul 29 13:58:06 CEST 2007 ppc GNU/Linux
> 
> The relveant debian package:
> > linux-image-2.6.22-1-powerpc_2.6.22-3_powerpc.deb
> 
> I'm running a mixture of debian testing/unstable.
> 
> The firewire and the USB connector were unused, the network connector 
> was used.
> 
> If there are questions regarding other packages, or somebody wants me to 
> test a fix (I would prever a debian package), don't hesitate - I would 
> like to get the bug fixed :-)
> 


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

Re: radeon driver updates for mac laptops

[Eugen Dedu]

Michel Dänzer wrote:

On Wed, 2007-09-05 at 16:25 +0200, Eugen Dedu wrote:

Michel Dänzer wrote:

On Wed, 2007-09-05 at 15:58 +0200, Eugen Dedu wrote:

VGA-0 disconnected (normal left inverted right x axis y axis)

If you specify

Option  "MacModel" "powerbook"

or "powerbook-duallink", the above should say DVI-0 instead of VGA-0.

However, it prints VGA-0...

Does the log file acknowledge the option being in effect as intended?

Ah...:

((II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled 
message.

WW) RADEON(0): Option "MacModel" is not used
(--) RandR disabled

I attach the whole log and xorg.conf.  Maybe I should try 
powerbook-duallink?!


The option value doesn't matter when the driver doesn't recognize the
identifier. Did you get the driver source from upstream GIT and build
it? The option isn't included in xserver-xorg-video-ati 1:6.7.192 yet.


It's from debian package...

The debian package appeared 27/08, just two days before the email, and I 
wrongly deduced that it included this option...


I prefer to wait a bit when the debian package include the option...

Many thanks and sorry for taking your time,
--
Eugen Dedu


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

Re: radeon driver updates for mac laptops

[Michel Dänzer]

On Wed, 2007-09-05 at 16:25 +0200, Eugen Dedu wrote:
> Michel Dänzer wrote:
> > On Wed, 2007-09-05 at 15:58 +0200, Eugen Dedu wrote:
> 
>  VGA-0 disconnected (normal left inverted right x axis y axis)
> >>> If you specify
> >>>
> >>>   Option  "MacModel" "powerbook"
> >>>
> >>> or "powerbook-duallink", the above should say DVI-0 instead of VGA-0.
> >> However, it prints VGA-0...
> > 
> > Does the log file acknowledge the option being in effect as intended?
> 
> Ah...:
> 
> ((II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled 
> message.
> WW) RADEON(0): Option "MacModel" is not used
> (--) RandR disabled
> 
> I attach the whole log and xorg.conf.  Maybe I should try 
> powerbook-duallink?!

The option value doesn't matter when the driver doesn't recognize the
identifier. Did you get the driver source from upstream GIT and build
it? The option isn't included in xserver-xorg-video-ati 1:6.7.192 yet.


-- 
Earthling Michel Dänzer   |  http://tungstengraphics.com
Libre software enthusiast |  Debian, X and DRI developer

Re: radeon driver updates for mac laptops

[Eugen Dedu]

Thank you for the reply.

Michel Dänzer wrote:

On Wed, 2007-09-05 at 14:40 +0200, Eugen Dedu wrote:
I own a PowerBook G4 


Titanium or aluminium? What panel size?


Aluminium.
snoopy:~$ cat /proc/cpuinfo
processor   : 0
cpu : 7447/7457, altivec supported
clock   : 612.00MHz
revision: 0.1 (pvr 8002 0101)
bogomips: 36.73
timebase: 18432000
platform: PowerMac
machine : PowerBook5,2
motherboard : PowerBook5,2 MacRISC3 Power Macintosh
detected as : 287 (PowerBook G4 15")
pmac flags  : 001b
L2 cache: 512K unified
pmac-generation : NewWorld

Sorry, how to find the panel size?  The resolution of the laptop screen
is 1280x854.

snoopy:~$ grep -i panel /var/log/Xorg.0.log
(II) RADEON(0): Existing panel PLL dividers will be used.
(WW) RADEON(0): Panel size 1280x854 is derived, this may not be correct.
If not, use PanelSize option to overwrite this setting
(EE) RADEON(0): Panel size is not correctly detected.
Please try to use PanelSize option for correct settings.
(II) RADEON(0): Panel infos found from DDC detailed: 1280x854
(II) RADEON(0): Panel infos found from DDC VESA/EDID: 1280x1024

and I do not succeed in using the 2nd monitor after 
using these steps (I am not an Xorg specialist):


1. Add Option ... in xorg.conf


... what?


Option "MacModel" "powerbook"


2. Restart computer and enter X

3. snoopy:~$ xrandr -q
Screen 0: minimum 320 x 200, current 1280 x 854, maximum 1280 x 1280
LVDS connected 1280x854+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm

1280x854   60.0*+
1280x800   60.0
1280x768   60.0
1024x768   60.0
800x60060.3
640x48059.9
VGA-0 disconnected (normal left inverted right x axis y axis)


If you specify

Option  "MacModel" "powerbook"

or "powerbook-duallink", the above should say DVI-0 instead of VGA-0.


However, it prints VGA-0...

Note: I have just upgraded xbase-clients and xutils to 1:7.3~rc1, the
test from my previous email was with xbase-clients 1:7.1.ds.3-1 and
xutils 1:7.2.ds2-2.  I redid the steps from my previous email, the same 
output is shown except that I have some information about S-video:


snoopy:~$ xrandr -q
Screen 0: minimum 320 x 200, current 1280 x 854, maximum 1280 x 1280
LVDS connected 1280x854+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm

   1280x854   60.0*+
   1280x800   60.0
   1280x768   60.0
   1024x768   60.0
   800x60060.3
   640x48059.9
VGA-0 connected (normal left inverted right x axis y axis)
   1280x1024  60.0 +   59.9
   1280x960   59.9
   1024x768   60.0
   800x60060.3
   640x48060.0
   720x40070.1
S-video disconnected 800x600+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm

  800x600 (0x55)   38.2MHz
h: width   800 start  832 end  912 total 1024 skew0 clock 
 37.4KHz
v: height  600 start  603 end  607 total  624   clock 
 59.9Hz


Thank you,
--
Eugen Dedu


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

Re: radeon driver updates for mac laptops

[Michel Dänzer]

On Wed, 2007-09-05 at 15:58 +0200, Eugen Dedu wrote:
> 
> Sorry, how to find the panel size?  

Using a ruler? ;)

> The resolution of the laptop screen is 1280x854.

Seriously though, this means it's 15".


> >> VGA-0 disconnected (normal left inverted right x axis y axis)
> > 
> > If you specify
> > 
> > Option  "MacModel" "powerbook"
> > 
> > or "powerbook-duallink", the above should say DVI-0 instead of VGA-0.
> 
> However, it prints VGA-0...

Does the log file acknowledge the option being in effect as intended?


-- 
Earthling Michel Dänzer   |  http://tungstengraphics.com
Libre software enthusiast |  Debian, X and DRI developer

Re: update unable to connect to several repositories

[Gerfried Fuchs]

* robert nuzum <[EMAIL PROTECTED]> [2007-09-05 14:52:11 CEST]:
> I'm running Lenny on an eMac and although everything seems to work well, 
> I have been unable to update for several weeks. Update stops at 
> http://ftp.egr.msu.edu/debian/dists/lenny/Release.gpg
> http://ftp.egr.msu.edu/debian/dists/lenny/main/i18n/Translation-en_US.bz2
> which fail to connect.

 I would expect that it is a specific problem with that very mirror and
not a general problem with your system.  You might want to edit your
/etc/apt/sources.list and change ftp.egr.msu.edu with some other server
from the exhaustive list on  - try
several to see which one works best for you.

 The best list for problems with mirrors is btw. debian-mirrors, there's
nothing architecture specific with a failed to connect. :)

 So long,
Rhonda


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

Re: network problem on openpower710

[Philippe Marzouk]

On Wed, Sep 05, 2007 at 02:11:01PM +0200, xavier grave wrote:
> Le mercredi 05 septembre 2007 à 12:45 +0200, Bastian Blank a écrit :
> > On Wed, Sep 05, 2007 at 12:35:43PM +0200, xavier grave wrote:
> > >   - ifconfig eth0 gives :
> > > eth0: error fetching interface information: Device not found
> > 
> > You did not show that there are no interfaces. Why? ip link?
> > ls -al /sys/class/net/?
> 
> power5:~# ls -al /sys/class/net/
> total 0
> drwxr-xr-x  5 root root 0 2007-09-05 11:58 .
> drwxr-xr-x 23 root root 0 2007-09-05 11:58 ..
> drwxr-xr-x  4 root root 0 2007-09-05 11:58 eth5
> drwxr-xr-x  4 root root 0 2007-09-05 11:58 eth6
> drwxr-xr-x  4 root root 0 2007-09-05 11:58 lo
> 
> ifconfig eth5 192.168.1.50 up
> runs perfectly...
> Now it works... Thanks !
> 
> I wonder why eth0 disappeared and eth5 and eth6 appeared ?
> Certainly because of the planar change...
> 

This is a "feature" of udev

See /etc/udev/rules.d/z25_persistent-net.rules

Philippe


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

Re: radeon driver updates for mac laptops

[Michel Dänzer]

On Wed, 2007-09-05 at 14:40 +0200, Eugen Dedu wrote:
> 
> I own a PowerBook G4 

Titanium or aluminium? What panel size?

> and I do not succeed in using the 2nd monitor after 
> using these steps (I am not an Xorg specialist):
> 
> 1. Add Option ... in xorg.conf

... what?

> 2. Restart computer and enter X
> 
> 3. snoopy:~$ xrandr -q
> Screen 0: minimum 320 x 200, current 1280 x 854, maximum 1280 x 1280
> LVDS connected 1280x854+0+0 (normal left inverted right x axis y axis) 
> 0mm x 0mm
> 1280x854   60.0*+
> 1280x800   60.0
> 1280x768   60.0
> 1024x768   60.0
> 800x60060.3
> 640x48059.9
> VGA-0 disconnected (normal left inverted right x axis y axis)

If you specify

Option  "MacModel" "powerbook"

or "powerbook-duallink", the above should say DVI-0 instead of VGA-0.


-- 
Earthling Michel Dänzer   |  http://tungstengraphics.com
Libre software enthusiast |  Debian, X and DRI developer

Re: radeon driver updates for mac laptops

[Eugen Dedu]

Hi,

I own a PowerBook G4 and I do not succeed in using the 2nd monitor after 
using these steps (I am not an Xorg specialist):


1. Add Option ... in xorg.conf

2. Restart computer and enter X

3. snoopy:~$ xrandr -q
Screen 0: minimum 320 x 200, current 1280 x 854, maximum 1280 x 1280
LVDS connected 1280x854+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm

   1280x854   60.0*+
   1280x800   60.0
   1280x768   60.0
   1024x768   60.0
   800x60060.3
   640x48059.9
VGA-0 disconnected (normal left inverted right x axis y axis)
S-video disconnected 800x600+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm


4. Connect the 2nd monitor (DVI cable)

5. [the 2nd monitor prints: "No signal" and remains completely black]

6. snoopy:~$ xrandr -q
Screen 0: minimum 320 x 200, current 1280 x 854, maximum 1280 x 1280
LVDS connected 1280x854+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm

   1280x854   60.0*+
   1280x800   60.0
   1280x768   60.0
   1024x768   60.0
   800x60060.3
   640x48059.9
VGA-0 connected (normal left inverted right x axis y axis)
   1280x1024  60.0 +   59.9
   1280x960   59.9
   1024x768   60.0
   800x60060.3
   640x48060.0
   720x40070.1
S-video disconnected 800x600+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm


7. snoopy:~$ xrandr --output LVDS --mode 1024x768

8. [the laptop screen changes resolution to 1024x768, but nothing 
happens on the 2nd monitor]


9. snoopy:~$ xrandr --output VGA-0 --mode 1024x768
xrandr: cannot find crtc for output VGA-0
snoopy:~$ xrandr -q
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 1280 x 1280
LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm

   1280x854   60.0 +
   1280x800   60.0
   1280x768   60.0
   1024x768   60.0*
   800x60060.3
   640x48059.9
VGA-0 connected (normal left inverted right x axis y axis)
   1280x1024  60.0 +   59.9
   1280x960   59.9
   1024x768   60.0
   800x60060.3
   640x48060.0
   720x40070.1
S-video connected 800x600+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm

   800x60059.9*+   60.3
snoopy:~$ xrandr --output S-video --mode 1024x768
xrandr: cannot find mode 1024x768
snoopy:~$ xrandr --output S-video --mode 800x600
xrandr: cannot find mode 800x600
snoopy:~$ xrandr --auto
snoopy:~$ xrandr --auto
snoopy:~$ xrandr -q
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1280 x 1280
LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm

   1280x854   60.0 +
   1280x800   60.0
   1280x768   60.0
   1024x768   60.0*
   800x60060.3
   640x48059.9
VGA-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
338mm x 270mm

   1280x1024  60.0*+   59.9
   1280x960   59.9
   1024x768   60.0
   800x60060.3
   640x48060.0
   720x40070.1
S-video disconnected (normal left inverted right x axis y axis)

[Nothing happens on the 2nd monitor...]

- How to put the 2nd monitor in clone mode?
- Why both VGA-0 and S-video were connected, afterwards only VGA-0?
- Why LDVS is 0mm x 0mm?



For info, here is an excerpt from Xorg.0.log:

(II) RADEON(0): EDID for output 0
(II) RADEON(0): Manufacturer: APP  Model: 9c20  Serial#: 16843009
(II) RADEON(0): Year: 2002  Week: 5
(II) RADEON(0): EDID Version: 1.3
(II) RADEON(0): Digital Display Input
(II) RADEON(0): Max H-Image Size [cm]: horiz.: 32  vert.: 22
(II) RADEON(0): Gamma: 2.20
(II) RADEON(0): No DPMS capabilities specified; RGB/Color Display
(II) RADEON(0): First detailed timing is preferred mode
(II) RADEON(0): redX: 0.600 redY: 0.350   greenX: 0.310 greenY: 0.550
(II) RADEON(0): blueX: 0.150 blueY: 0.115   whiteX: 0.320 whiteY: 0.330
(II) RADEON(0): Manufacturer's mask: 0
(II) RADEON(0): Supported additional Video Mode:
(II) RADEON(0): clock: 79.8 MHz   Image Size:  321 x 214 mm
(II) RADEON(0): h_active: 1280  h_sync: 1296  h_sync_end 1408 
h_blank_end 1536 h_bor

der: 0
(II) RADEON(0): v_active: 854  v_sync: 855  v_sync_end 858 v_blanking: 
866 v_border:

 0
(II) RADEON(0):  LTN152W3
(II) RADEON(0):  LTN152W3
(II) RADEON(0): Monitor name: Color LCD
(II) RADEON(0): EDID (in hex):
(II) RADEON(0): 00000610209c01010101
(II) RADEON(0): 050c0103802016780aa7a299594f8c26
(II) RADEON(0): 1d52540001010101010101010101
(II) RADEON(0): 0101010101012d1f51560c301070
(II) RADEON(0): 130041d6101800fe004c544e
(II) RADEON(0): 3135325733000a2000fe004c
(II) RADEON(0): 544e3135325733000a2000fc
(II) RADEON(0): 00436f6c6f72204c43440a20202b
(II) RADEON(0): EDID vendor "APP", prod id 39968
(II) RADEON(0): DDC Type: 3, Detected Monitor Type: 3
(II) RADEON(0): EDID data from the display on connector: VGA 
-

update unable to connect to several repositories

[robert nuzum]

I'm running Lenny on an eMac and although everything seems to work well, 
I have been unable to update for several weeks. Update stops at 
ttp://ftp.egr.msu.edu/debian/dists/lenny/Release.gpg

http://ftp.egr.msu.edu/debian/dists/lenny/main/i18n/Translation-en_US.bz2
which fail to connect.
Any help appreciated. I'm not particularly facile with Linux but can 
follow directions.

Bob


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

Re: network problem on openpower710

[xavier grave]

Le mercredi 05 septembre 2007 à 12:45 +0200, Bastian Blank a écrit :
> On Wed, Sep 05, 2007 at 12:35:43PM +0200, xavier grave wrote:
> > - ifconfig eth0 gives :
> > eth0: error fetching interface information: Device not found
> 
> You did not show that there are no interfaces. Why? ip link?
> ls -al /sys/class/net/?

power5:~# ls -al /sys/class/net/
total 0
drwxr-xr-x  5 root root 0 2007-09-05 11:58 .
drwxr-xr-x 23 root root 0 2007-09-05 11:58 ..
drwxr-xr-x  4 root root 0 2007-09-05 11:58 eth5
drwxr-xr-x  4 root root 0 2007-09-05 11:58 eth6
drwxr-xr-x  4 root root 0 2007-09-05 11:58 lo

ifconfig eth5 192.168.1.50 up
runs perfectly...
Now it works... Thanks !

I wonder why eth0 disappeared and eth5 and eth6 appeared ?
Certainly because of the planar change...

xavier
> Bastian
> 
> -- 
> Dammit Jim, I'm an actor, not a doctor.
> 
> 


signature.asc
Description: Ceci est une partie de message	numériquement signée

Re: network problem on openpower710

[Bastian Blank]

On Wed, Sep 05, 2007 at 12:35:43PM +0200, xavier grave wrote:
>   - ifconfig eth0 gives :
> eth0: error fetching interface information: Device not found

You did not show that there are no interfaces. Why? ip link?
ls -al /sys/class/net/?

Bastian

-- 
Dammit Jim, I'm an actor, not a doctor.


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

Re: network problem on openpower710

[xavier grave]

Le mardi 04 septembre 2007 à 06:32 +0200, Sven Luther a écrit :
> On Mon, Sep 03, 2007 at 05:34:47PM +0200, xavier grave wrote:
> > Hi,
> > 
> > I had a try with SF235_214 firmware version without much success.
> > with 2.6.22-2-powerpc64 kernel.
> > 
> > I'll try to downgrade one more time to SF230_158 just to check...
> 
> Xavier, i wonder if you could give us the exact step how you test this
> issues ?

Hi,

Ok, I'll try to explain a little better what I exactly do.
The following procedure have been tested with three king of firmware :
SF230_158, SF235_214, SF240_320
and the following debian kernels :
2.6.22-2-powerpc64, vmlinux-2.6.21-1-powerpc64, 2.6.18-4-powerpc64

This is an openpower 710 hardware.
I just boot my unstable debian distro from SCSI hard drive using yaboot.
After I can just check what is running :
- dhcp server won't start since eth0 isn't configured
- dmesg | grep e1000 gives :
e1000: :c0:01.0: e1000_probe: (PCI-X:133MHz:64-bit)
00:0d:60:de:b5:78
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: :c0:01.1: e1000_probe: (PCI-X:133MHz:64-bit)
00:0d:60:de:b5:79
e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
- ifconfig eth0 gives :
eth0: error fetching interface information: Device not found
- grep e1000 /proc/ioports gives : 
  000fe800-000fe83f : e1000
  000fec00-000fec3f : e1000
- grep e1000 /proc/iomem gives :
  400b804-400b807 : e1000
  400b80c-400b80f : e1000
  400b810-400b811 : e1000
  400b812-400b813 : e1000
- grep e1000 /proc/interrupts gives nothing

During boot I also get these messages :
Setting up networking
Configuring network interfaces...
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
eth0: ERROR while getting interface flags: No such device
eth0: ERROR while getting interface flags: No such device
Failed to bring up eth0.  
SIOCSIFADDR: No such device   
eth1: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
eth1: ERROR while getting interface flags: No such device
eth1: ERROR while getting interface flags: No such device
Failed to bring up eth1.
done.

Hope it will help... Once this machine is up it will be available for
monotone dev if this is still needed.

Cordially and friendly, xavier


signature.asc
Description: Ceci est une partie de message	numériquement signée