Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

2018-06-29 Thread Adam D. Barratt 
On Fri, 2018-06-29 at 11:44 +0100, Luke Kenneth Casson Leighton wrote:
[...]
> On Fri, Jun 29, 2018 at 10:35 AM, Adam D. Barratt
>  wrote:
> 
> > >  what is the reason why that package is not moving forward?
> > 
> > I assume you're referring to the dpkg upload that's in proposed-
> > updates
> > waiting for the point release in two weeks time?
> 
>  i don't know: i'm an outsider who doesn't have the information in
> short-term memory, which is why i cc'd the debian-riscv team as they
> have current facts and knowledge foremost in their minds.  which is
> why i included them.

It would have been wiser to do so *before* stating that nothing was
happening as if it were a fact.

> > I'm also getting very tired of the repeated vilification of SRM
> > over
> > this, and if there were any doubt can assure you that it is not
> > increasing at least my inclination to spend my already limited free
> > time on Debian activity.
> 
>  ah.  so what you're saying is, you could really do with some extra
> help?

I don't think that's ever been in dispute for basically any core team
in Debian.

That doesn't change the fact that the atmosphere around the change in
question has made me feel very uncomfortable and unenthused about SRM
work. (I realise that this is somewhat of a self-feeding energy
monster.)

Regards,

Adam

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

2018-06-29 Thread Adam D. Barratt 
On Fri, 2018-06-29 at 10:20 +0100, Luke Kenneth Casson Leighton wrote:
[...]
>  debian-riscv has been repeatedly asking for a single zero-impact
> line
> to be included in *one* file in *one* dpkg-related package which
> would
> allow riscv to stop being a NMU architecture and become part of
> debian/unstable (and quickly beyond), for at least six months, now.
> cc'ing the debian-riscv list because they will know the details about
> this.  it's really quite ridiculous that a single one-line change
> having absolutely no effect on any other architecture whatsover is
> not
> being actioned and is holding debian-riscv back because of that.
> 
>  what is the reason why that package is not moving forward?

I assume you're referring to the dpkg upload that's in proposed-updates 
waiting for the point release in two weeks time? Please check your
facts before ranting, particularly with such a wide cross-posting.

Also, ttbomk, the dpkg change landing in stable is not likely to
magically lead to the architecture being added to unstable - a decision
which is not the release team's to make or block. Again, please ensure
you've actually done your research.

I'm also getting very tired of the repeated vilification of SRM over
this, and if there were any doubt can assure you that it is not
increasing at least my inclination to spend my already limited free
time on Debian activity.

Regards,

Adam

Re: Porter roll call for Debian Stretch

2016-10-09 Thread Adam D. Barratt 
On Sun, 2016-10-09 at 21:12 +0300, Adrian Bunk wrote:
> [ adding debian-powerpc ]
> 
> On Sun, Oct 09, 2016 at 06:54:44PM +0200, Moritz Mühlenhoff wrote:
> > Niels Thykier  schrieb:
> > > If I am to support powerpc as a realease architecture for Stretch, I
> > > need to know that there are *active* porters behind it committed to
> > > keeping it in the working.  People who would definitely catch such
> > > issues long before the release.  People who file bugs / submit patches 
> > > etc.
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832931 is about
> > a powerpc-specific build failure of mariadb in stable. The maintainer
> > said he can't work on it, so if anyone considers himself/herself a
> > powerpc porter, this is something to look it.
> 
> Can you give a hint what exactly should be looked at?

https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.0=powerpc=10.0.27-0%2Bdeb8u1=1473621159

> The bug did not make it clear that there is any problem left at all when 
> I looked at it recently.
> 
> The last message was closing the bug.
> 
> There was a control command reopening the bug without giving any 
> rationale, but the last control command was
>   fixed 832931 10.0.27-1

For unstable, yes. The stable package is still broken.

> buildd.debian.org says that 10.0.27-0+deb8u1 was installed on jessie.[1]

That's an artefact of how builds for suites with "overlays" (i.e. pu /
tpu) are displayed. If one actually looks at the archive:

mariadb-client-10.0 | 10.0.25-0+deb8u1 | stable | powerpc
mariadb-client-10.0 | 10.0.27-0+deb8u1 | stable | amd64, arm64, armel, 
armhf, i386, mips, mipsel, ppc64el, s390x

Regards,

Adam

Re: Porter roll call for Debian Stretch

2016-09-30 Thread Adam D. Barratt 
On Fri, 2016-09-30 at 19:04 +, Niels Thykier wrote:
> As for "porter qualification"
> =
> 
> We got burned during the Jessie release, where a person answered the
> roll call for sparc and we kept sparc as a release architecture for
> Jessie.  However, we ended up with a completely broken and unbootable
> sparc kernel.

fwiw, you mean wheezy.

Regards,

Adam

Re: binNMUs: please exercise some care

2015-10-23 Thread Adam D. Barratt 

On 2015-10-23 11:56, Thorsten Glaser wrote:

On Fri, 23 Oct 2015, Emilio Pozuelo Monfort wrote:

I didn't say once per arch. I said once per package, which is worse. I 
normally

schedule binNMUs for several dozens packages. Multiply that by several


But you need to look the number up anyway? The wanna-build
--binNMU parameter gets the number to use as argument.


wanna-build does, yes, but at least the Release Team tend to use the 
"wb" wrapper tool which automatically works out the next free number on 
each architecture.


Regards,

Adam

Re: binNMUs: please exercise some care

2015-10-23 Thread Adam D. Barratt 

On 2015-10-23 13:28, Thorsten Glaser wrote:
[...]

On Fri, 23 Oct 2015, Adam D. Barratt wrote:

[...]
It's also not quite that simple, even working things out by hand - see 
#599128

for example.


Hm, I’m still under the impression that the +bN suffix to the Debian
version of the package in the archive is the authoritative source for
what binNMU version a package currently has, as that’s taking porter
uploads into account which is a requirement. If the current code
doesn’t do that I consider it a bug which must be fixed (at the same
time, or before doing this change), which makes it more tricky, yes.


Specifically, wanna-build doesn't expose the binNMU version information 
for suites other than unstable / experimental (actually, it might be 
that it doesn't for suites that have an overlay - either way, it affects 
{,old}stable and testing), so the only way to be certain what binNMU 
number to use is to check manually. In practice what actually happens is 
that people forget about the bug, schedule the binNMUs and then grumble 
when either dak rejects the packages or something gets confused.


Regards,

Adam

Re: binNMUs: please exercise some care

2015-10-23 Thread Adam D. Barratt 

On 2015-10-23 12:02, Thorsten Glaser wrote:

On Fri, 23 Oct 2015, Adam D. Barratt wrote:

wanna-build does, yes, but at least the Release Team tend to use the 
"wb"
wrapper tool which automatically works out the next free number on 
each

architecture.


Ah, cool – so we have only to patch this tool to automatically
use the highest number per batch on all affected architectures
(or even to use the highest number if all architectures would
be touched, but that’s probably an unreasonable amount of code
change).


Well, except you only really want to do it for libraries that are 
ma:same, as that's the only case where it actually matters and otherwise 
you're pointlessly losing versions.


It's also not quite that simple, even working things out by hand - see 
#599128 for example.



Where’s the source code to that tool?


http://anonscm.debian.org/cgit/debian-release/release-tools.git/ (in 
scripts/).


Regards,

Adam

Re: powerpc qualification for Wheezy

2012-05-23 Thread Adam D. Barratt 
On Wed, 2012-05-16 at 13:19 +0100, Adam D. Barratt wrote:
 With the sound of the ever approaching freeze ringing loudly in our ears,
 we're (somewhat belatedly) looking at finalising the list of release
 architectures for the Wheezy release.
 
 Comments on / additions and corrections to the content of
 http://release.debian.org/wheezy/arch_qualify.html would be appreciated,
 as would any other information you think is relevant to helping us
 determine powerpc's status for the release.

*gentle prod*

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1337797937.16492.11.ca...@jacala.jungle.funky-badger.org

powerpc qualification for Wheezy

2012-05-16 Thread Adam D. Barratt 
Hi,

With the sound of the ever approaching freeze ringing loudly in our ears,
we're (somewhat belatedly) looking at finalising the list of release
architectures for the Wheezy release.

Comments on / additions and corrections to the content of
http://release.debian.org/wheezy/arch_qualify.html would be appreciated,
as would any other information you think is relevant to helping us
determine powerpc's status for the release.

Regards,

Adam
pp the Release Team


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1sudcl-00058d...@kaa.jungle.funky-badger.org

Re: GCC-4.5 as the default for (at least some) architectures

2011-04-17 Thread Adam D. Barratt 
On Wed, 2011-03-02 at 02:34 +0100, Matthias Klose wrote:
 I'll make gcc-4.5 the default for (at least some) architectures within the 
 next
 two weeks before more transitions start.  GCC-4.5 is already used as the 
 default
 compiler for almost any other distribution, so there shouldn't be many 
 surprises
 on at least the common architectures.  About 50% of the build failures exposed
 by GCC-4.5 are fixed [1].  I didn't see issues on amd64 and i386, armel
 (although optimized for a different processor) and powerpc (some object files
 linked into shared libs had to be built as pic).

It looks like kfreebsd-* also made the switch and there's been a request
to switch for mips and mipsel.

Looking through the bug list for src:gcc-4.5, none of the open issues
seem to be specific to the remaining release architectures which haven't
switched yet - i.e. ia64, s390 and sparc.  Are you aware of any issues
which would preclude switching the default on those architectures?  Has
there been any discussion with the port maintainers regarding switching?

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1303068791.3489.499.ca...@hathi.jungle.funky-badger.org

Errors starting wirless driver on 17 G4 PowerBook

2006-10-21 Thread Adam D 
The output when $ sudo ifup eth1
SIOCSIFFLAGS: No such file or directory
SIOCSIFFLAGS: No such file or directory
Failed to bring up eth1.


It looks like in dmesg the bcm43xx is found when booting (using ubuntu on this 
box).  However the interface is not reconized or connected to bcm43xx.

[snip}
[   61.151418] ieee80211_crypt: registered algorithm 'NULL'
[   61.430697] ieee80211: 802.11 data/management/control stack, git-1.1.7
[   61.430706] ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL 
PROTECTED]
[   61.579889] bcm43xx driver
[   61.580614] PCI: Enabling device 0001:10:12.0 (0004 - 0006)
[   61.881835] sungem.c:v0.98 8/24/03 David S. Miller (davem@redhat.com)
[   61.947408] PHY ID: 1410cc1, addr: 0
[   61.948000] eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0d:93:35:91:44
[   61.948008] eth0: Found Marvell 88E1101 PHY

[snip]

[   61.948000] eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0d:93:35:91:44
[   61.948008] eth0: Found Marvell 88E1101 PHY

[snip]

[   64.347177] eth0: Link is up at 100 Mbps, full-duplex.
[   64.347186] eth0: Pause is disabled

[snip]


Other than that there isn't any other mention of wireless.

lsmod give this out put...

[snip]
sungem 38948  0
sungem_phy 10432  1 sungem
bcm43xx   136524  0
ieee80211softmac   33568  1 bcm43xx
ieee80211  39784  2 bcm43xx,ieee80211softmac
ieee80211_crypt 7136  1 ieee80211
[snip]




In /etc/modules I included..

bcm43xx eth1

and...

my /etc/network/interfaces has this for the interface:

iface eth1 inet static
name DS-wifi
address 192.168.1.1
netmask 255.255.255.0
gateway 192.168.1.100
wireless_mode Managed
dns-nameservers 10.1.100.1
wireless-essid xyz-abc
wireless-key xxx

All the still I can't bring up the interface.  Any extra help/eyes would be 
very helpful.  Thanks.

-Adam


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

Re: Errors starting wirless driver on 17 G4 PowerBook

2006-10-21 Thread Adam D 
Adam D wrote:
 The output when $ sudo ifup eth1
 SIOCSIFFLAGS: No such file or directory
 SIOCSIFFLAGS: No such file or directory
 Failed to bring up eth1.
 
 
 It looks like in dmesg the bcm43xx is found when booting (using ubuntu on 
 this box).  However the interface is not reconized or connected to bcm43xx.
 
 [snip}
 [   61.151418] ieee80211_crypt: registered algorithm 'NULL'
 [   61.430697] ieee80211: 802.11 data/management/control stack, git-1.1.7
 [   61.430706] ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL 
 PROTECTED]
 [   61.579889] bcm43xx driver
 [   61.580614] PCI: Enabling device 0001:10:12.0 (0004 - 0006)
 [   61.881835] sungem.c:v0.98 8/24/03 David S. Miller (davem@redhat.com)
 [   61.947408] PHY ID: 1410cc1, addr: 0
 [   61.948000] eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0d:93:35:91:44
 [   61.948008] eth0: Found Marvell 88E1101 PHY
 
 [snip]
 
 [   61.948000] eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0d:93:35:91:44
 [   61.948008] eth0: Found Marvell 88E1101 PHY
 
 [snip]
 
 [   64.347177] eth0: Link is up at 100 Mbps, full-duplex.
 [   64.347186] eth0: Pause is disabled
 
 [snip]
 
 
 Other than that there isn't any other mention of wireless.
 
 lsmod give this out put...
 
 [snip]
 sungem 38948  0
 sungem_phy 10432  1 sungem
 bcm43xx   136524  0
 ieee80211softmac   33568  1 bcm43xx
 ieee80211  39784  2 bcm43xx,ieee80211softmac
 ieee80211_crypt 7136  1 ieee80211
 [snip]
 
 
 
 
 In /etc/modules I included..
 
 bcm43xx eth1
 
 and...
 
 my /etc/network/interfaces has this for the interface:
 
 iface eth1 inet static
 name DS-wifi
 address 192.168.1.1
 netmask 255.255.255.0
 gateway 192.168.1.100
 wireless_mode Managed
 dns-nameservers 10.1.100.1
 wireless-essid xyz-abc
   wireless-key xxx
   
 All the still I can't bring up the interface.  Any extra help/eyes would be 
 very helpful.  Thanks.
 
 -Adam

I had thought I had In /etc/modules I included.. bcm43xx eth1 but I had not.

I restarted the box and then the dmesg had changed to this.

[snip]
33.081935] NET: Registered protocol family 2
[   33.116698] IP route cache hash table entries: 131072 (order: 7, 524288 
bytes)
[   33.117676] TCP established hash table entries: 524288 (order: 9, 2097152 
bytes)
[   33.121128] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
[   33.121529] TCP: Hash tables configured (established 524288 bind 65536)
[   33.121534] TCP reno registered
[   33.121671] TCP bic registered
[   33.121683] NET: Registered protocol family 1
[   33.121696] NET: Registered protocol family 8
[   33.121699] NET: Registered protocol family 20
[snip]
 51.164732] ieee80211_crypt: registered algorithm 'NULL'
[   51.167019] ieee80211: 802.11 data/management/control stack, git-1.1.7
[   51.167025] ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL 
PROTECTED]
[   51.286790] bcm43xx driver
[   51.286944] PCI: Enabling device 0001:10:12.0 (0004 - 0006)
[   51.473109] sungem.c:v0.98 8/24/03 David S. Miller (davem@redhat.com)
[   51.540987] PHY ID: 1410cc1, addr: 0
[   51.541416] eth1: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0d:93:35:91:44
[   51.541424] eth1: Found Marvell 88E1101 PHY
[snip]
51.473109] sungem.c:v0.98 8/24/03 David S. Miller (davem@redhat.com)
[   51.540987] PHY ID: 1410cc1, addr: 0
[   51.541416] eth1: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0d:93:35:91:44
[   51.541424] eth1: Found Marvell 88E1101 PHY
[snip]
53.940763] eth0: Link is up at 100 Mbps, full-duplex.
[   53.940772] eth0: Pause is disabled
[   54.547580] NET: Registered protocol family 10
[   54.547745] lo: Disabled Privacy Extensions
[   54.547977] IPv6 over IPv4 tunneling driver
[snip]
[   64.592637] eth0: no IPv6 routers present
[   87.670670] ieee80211_crypt: registered algorithm 'WEP'
[   88.120082] bcm43xx: Error: Microcode bcm43xx_microcode5.fw not available 
or load failed.
[   88.139217] bcm43xx: Error: Microcode bcm43xx_microcode5.fw not available 
or load failed.



The kernel module is loaded ...
sungem 38948  0
sungem_phy 10432  1 sungem
bcm43xx   136524  0
ieee80211softmac   33568  1 bcm43xx
ieee80211  39784  2 bcm43xx,ieee80211softmac
ieee80211_crypt 7136  2 ieee80211_crypt_wep,ieee80211


Now with dmesg stating eth1 belonging to sungem.  
My ifconfig and route all show eth0 is up and running with the proper config.


-adam


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

Re: Errors starting wirless driver on 17 G4 PowerBook

2006-10-21 Thread Adam D 
Sebastian Muszynski wrote:
 Am Samstag, 21. Oktober 2006 23:02 schrieb Adam D:
 [   88.139217] bcm43xx: Error: Microcode bcm43xx_microcode5.fw not
 available or load failed.
 
 The trouble is that you haven't used fwcutter to extract the bcm43xx firmware 
 of your mac osx drivers... try (apt-cache search) fwcutter.
 
 Regards, 
 
 Sebastian
 


Thank you.  I googled fwcutter and found this Ubuntu page and followed its 
instructions.(https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Dapper) 
  However do I need a 2.6.17+ or can I use the bcm43xx driver on learlier 
kernels such as 2.6.15?  Things look well but I can't test my connection 
because I do not know if my base station extream or the powerbook airport card 
just went bad :(.  I may have to run to the apple store to use their wireless 
network to find out if it the card or the base station.  

Until then I can't do much.  But in linux the driver did load and I can see it 
in iwconfig.

Thanks for your help

-adam


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

Re: eth0: ERROR while getting interface flags: No such device

2006-10-06 Thread Adam D 
Michael Schmitz wrote:
 On an older 2.6.11.9 kernel I can use my eth0 port but on my newer 2.6.17.11 
 kernel I have not been able to use eth0 and get this error.
 
 sungem.c:v0.98 8/24/03 David S. Miller (davem@redhat.com)
 PHY ID: 1410cc1, addr: 0
 eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0d:93:35:91:44
 eth0: Found Marvell 88E1101 PHY
 [...]
 ieee80211: 802.11 data/management/control stack, git-1.1.7
 ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED]
 ieee80211_crypt: registered algorithm 'NULL'
 ieee80211_crypt: registered algorithm 'WEP'
 ieee80211_crypt: registered algorithm 'CCMP'
 ieee80211_crypt: registered algorithm 'TKIP'
 [...]
 orinoco 0.15rc3 (David Gibson [EMAIL PROTECTED], Pavel Roskin [EMAIL 
 PROTECTED], et al)
 airport 0.15rc3 (Benjamin Herrenschmidt [EMAIL PROTECTED])
 [...]
 
 Check that your SUNGEM isn't actually eth1 now.
 
   Michael
 

Yes, it had switched.  Now the investigation goes to find out why eth0 is now 
eth1.  Apparently, I have installed a package that is conflicting with the 
order networking devices are scanned.  I used the same kernel on a fresh 
install partition and it works just fine so the only difference between the two 
are: one a new install and the other was running on my powerbook 15 TI.  

My /etc/network  looks like this:
/etc/network # l *
-rw-r--r-- 1 root root  724 2006-10-06 14:00 interfaces
-rw-r--r-- 1 root root 1.3K 2006-09-02 19:25 interfaces-old
-rw-r--r-- 1 root root 2.0K 2005-05-03 02:28 secvpn.conf

if-down.d:
total 12K
-rwxr-xr-x 1 root root 141 2006-04-10 16:02 openvpn*
-rwxr-xr-x 1 root root 803 2006-06-08 02:00 postfix*
-rwxr-xr-x 1 root root 488 2006-04-11 21:45 resolvconf*
lrwxrwxrwx 1 root root  32 2006-10-05 17:57 wpasupplicant - 
../../wpa_supplicant/ifupdown.sh*

if-post-down.d:
total 8.0K
-rwxr-xr-x 1 root root 997 2006-02-09 15:37 wireless-tools*
lrwxrwxrwx 1 root root  32 2006-10-05 17:57 wpasupplicant - 
../../wpa_supplicant/ifupdown.sh*

if-pre-up.d:
total 20K
-rwxr-xr-x 1 root root 2.3K 2006-02-09 15:37 wireless-tools*
lrwxrwxrwx 1 root root   32 2006-10-05 17:57 wpasupplicant - 
../../wpa_supplicant/ifupdown.sh*

if-up.d:
total 24K
-rwxr-xr-x 1 root root  651 2006-04-11 21:45 000resolvconf*
-rwxr-xr-x 1 root root 1.4K 2006-05-23 03:40 mountnfs*
-rwxr-xr-x 1 root root  551 2006-05-28 19:49 ntpdate*
-rwxr-xr-x 1 root root  142 2006-04-10 16:02 openvpn*
-rwxr-xr-x 1 root root 1.1K 2006-06-08 02:00 postfix*



Could any of these be conflicting with the network devices on startup?  That is 
a start.  I am amiss.  I took out a bunch of wireless packages thinking that 
may have contributed to my issue but it did not.  i also took out anything to 
do with bluetooth thinking when starting up it could be attributing to the 
missaragement of network devices and still no difference.  Now when I dmesg I 
still see bluetooth but there are not any package related to bluetooth 
installed.




Thanks for the input.

-Adam


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

eth0: ERROR while getting interface flags: No such device

2006-10-05 Thread Adam D 
I have had my 17PB in and out of Apple service this last month and a half and I 
am back installing Linux on the book.  I brought over the system from my 15 TI 
and recompiled the kernel.  


On an older 2.6.11.9 kernel I can use my eth0 port but on my newer 2.6.17.11 
kernel I have not been able to use eth0 and get this error.

# ifup eth0
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

I have the sungen complied into the kernel and also tried it as a module and 
when I load the module and bring up eth0 I get the same issues.



Here is my dmesg output:

Using PowerMac machine description
Total memory = 2048MB; using 4096kB for hash table (at cfc0)
Linux version 2.6.17.11.ppc.17pb.2 ([EMAIL PROTECTED]) (gcc version 4.0.3 
(Ubuntu 4.0.3-1ubuntu5)) #1 PREEMPT Thu Oct 5 18:13:28 EDT 2006
Found UniNorth memory controller  host bridge @ 0xf800 revision: 0xd2
Mapped at 0xfdfc
Found a Intrepid mac-io controller, rev: 0, mapped at 0xfdf4
Processor NAP mode on idle enabled.
PowerMac motherboard: PowerBook G4 17
via-pmu: Server Mode is disabled
PMU driver v2 initialized for Core99, firmware: 0c
Found UniNorth PCI host bridge at 0xf000. Firmware bus number: 0-1
Found UniNorth PCI host bridge at 0xf200. Firmware bus number: 0-1
Found UniNorth PCI host bridge at 0xf400. Firmware bus number: 0-1
nvram: Checking bank 0...
nvram: gen0=856, gen1=855
nvram: Active bank is: 0
nvram: OF partition at 0x410
nvram: XP partition at 0x1020
nvram: NR partition at 0x1120
Top of RAM: 0x8000, Total RAM: 0x8000
Memory hole size: 0MB
On node 0 totalpages: 524288
  DMA zone: 196608 pages, LIFO batch:31
  HighMem zone: 327680 pages, LIFO batch:31
Built 1 zonelists
Kernel command line: root=/dev/hda7 ro quiet splash 
mpic: Setting up MPIC  MPIC 1version 1.2 at 8004, max 4 CPUs
mpic: ISU size: 64, shift: 6, mask: 3f
mpic: Initializing for 64 sources
PID hash table entries: 4096 (order: 12, 16384 bytes)
GMT Delta read from XPRAM: 0 minutes, DST: off
time_init: decrementer frequency = 18.432000 MHz
time_init: processor frequency   = 1499.94 MHz
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
High memory: 1310720k
Memory: 2069356k/2097152k available (4408k kernel code, 1337468k reserved, 380k 
data, 220k bss, 168k init)
Calibrating delay loop... 36.73 BogoMIPS (lpj=18368)
Mount-cache hash table entries: 512
device-tree: Duplicate name in /cpus/PowerPC,[EMAIL PROTECTED], renamed to 
l2-cache#1
NET: Registered protocol family 16
KeyWest i2c @0xf8001003 irq 42 /[EMAIL PROTECTED]/[EMAIL PROTECTED]
 channel 0 bus multibus
 channel 1 bus multibus
KeyWest i2c @0x80018000 irq 26 /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL 
PROTECTED]
 channel 0 bus multibus
PMU i2c /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/pmu-i2c
 channel 1 bus multibus
 channel 2 bus multibus
PCI: Probing PCI hardware
Can't get bus-range for /[EMAIL PROTECTED]/[EMAIL PROTECTED], assuming it 
starts at 0
PCI: Cannot allocate resource region 0 of device 0001:10:18.0
PCI: Cannot allocate resource region 0 of device 0001:10:19.0
Apple USB OHCI 0001:10:18.0 disabled by firmware
Apple USB OHCI 0001:10:19.0 disabled by firmware
usbcore: registered new driver usbfs
usbcore: registered new driver hub
Bluetooth: Core ver 2.8
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 262144 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
Thermal assist unit not available
Registering PowerMac CPU frequency driver
Low: 749 Mhz, High: 1499 Mhz, Boot: 749 Mhz
audit: initializing netlink socket (disabled)
audit(1160100605.210:1): initialized
highmem bounce pool size: 64 pages
fuse init (API version 7.6)
JFS: nTxBlock = 8192, nTxLock = 65536
SGI XFS with ACLs, security attributes, realtime, no debug enabled
SGI XFS Quota Management subsystem
Initializing Cryptographic API
io scheduler noop registered
io scheduler cfq registered (default)
PCI: Enabling device :00:10.0 (0006 - 0007)
radeonfb (:00:10.0): Invalid ROM signature 303 should be 0xaa55
radeonfb: Retrieved PLL infos from Open Firmware
radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=203.00 Mhz, System=392.00 MHz
radeonfb: PLL min 12000 max 35000
radeonfb: Monitor 1 type LCD found
radeonfb: EDID probed
radeonfb: Monitor 2 type no found
radeonfb: Using Firmware dividers 0x00040080 from PPLL 0
radeonfb: Dynamic Clock Power

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

2006-08-17 Thread Adam D 

 Another question:  Has people been able to get the keyboard to light up in
 Linux for the 17 PB?


 Thanks,
 -Adam
 
 Everything on the 17 works! except the modem. you need the pbbuttons package 
 to fix the lightning.
 
 Børge
 

Ok, everything is looking good with some minor diff changes in the kernel 
source.  I  have included the .config file to show what changes I made.  
However, I don't know if this should go as a new thread or not but when I put 
the computer to sleep and wake up.. it looses all responsiveness and the only 
thing I can do is force power down the box.  I don't know if this is a kernel 
or pbbuttons issue.

Other than that.. the kernel is looking very good.  The fan does not come on 
any more and I can switch to the tty terminals and back to x without any 
problems.

-Adam
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.17.7
# Thu Aug 17 15:47:04 2006
#
# CONFIG_PPC64 is not set
CONFIG_PPC32=y
CONFIG_PPC_MERGE=y
CONFIG_MMU=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_PPC=y
CONFIG_EARLY_PRINTK=y
CONFIG_GENERIC_NVRAM=y
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_PPC_OF=y
CONFIG_PPC_UDBG_16550=y
# CONFIG_GENERIC_TBSYNC is not set
# CONFIG_DEFAULT_UIMAGE is not set

#
# Processor support
#
CONFIG_CLASSIC32=y
# CONFIG_PPC_52xx is not set
# CONFIG_PPC_82xx is not set
# CONFIG_PPC_83xx is not set
# CONFIG_PPC_85xx is not set
# CONFIG_40x is not set
# CONFIG_44x is not set
# CONFIG_8xx is not set
# CONFIG_E200 is not set
CONFIG_6xx=y
CONFIG_PPC_FPU=y
CONFIG_ALTIVEC=y
CONFIG_PPC_STD_MMU=y
CONFIG_PPC_STD_MMU_32=y
# CONFIG_SMP is not set

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION=
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
CONFIG_AUDIT=y
# CONFIG_AUDITSYSCALL is not set
# CONFIG_IKCONFIG is not set
# CONFIG_RELAY is not set
CONFIG_INITRAMFS_SOURCE=
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_SLAB=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y

#
# Block layer
#
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
# CONFIG_IOSCHED_DEADLINE is not set
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED=cfq

#
# Platform support
#
CONFIG_PPC_MULTIPLATFORM=y
# CONFIG_PPC_ISERIES is not set
# CONFIG_EMBEDDED6xx is not set
# CONFIG_APUS is not set
CONFIG_PPC_CHRP=y
CONFIG_PPC_PMAC=y
CONFIG_MPIC=y
CONFIG_PPC_RTAS=y
# CONFIG_RTAS_ERROR_LOGGING is not set
CONFIG_RTAS_PROC=y
# CONFIG_MMIO_NVRAM is not set
CONFIG_PPC_MPC106=y
# CONFIG_PPC_970_NAP is not set
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_PMAC=y
# CONFIG_PPC601_SYNC_FIX is not set
CONFIG_TAU=y
# CONFIG_TAU_INT is not set
# CONFIG_TAU_AVERAGE is not set
# CONFIG_WANT_EARLY_SERIAL is not set

#
# Kernel options
#
CONFIG_HIGHMEM=y
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_KEXEC=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_PROC_DEVICETREE=y
CONFIG_CMDLINE_BOOL=y
CONFIG_CMDLINE=console=ttyS0,9600 console=tty0
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
# CONFIG_SOFTWARE_SUSPEND is not set
CONFIG_SECCOMP=y
CONFIG_ISA_DMA_API=y

#
# Bus options
#
# CONFIG_ISA is not set
CONFIG_GENERIC_ISA_DMA=y
CONFIG_PPC_I8259=y
CONFIG_PPC_INDIRECT_PCI=y
CONFIG_PCI=y
CONFIG_PCI_DOMAINS=y

#
#

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

2006-08-16 Thread Adam D 
BXrge Holen wrote:
 On Wednesday 16 August 2006 05:31, Adam D wrote:
 Sven Luther wrote:
 On Fri, Aug 11, 2006 at 12:32:34AM +0200, Børge Holen wrote:
 On Friday 11 August 2006 00:17, Adam D wrote:
 Adam D wrote:
 BXrge Holen wrote:
 On Thursday 10 August 2006 23:53, Adam D wrote:
 OK,  I decided to just install Ubuntu on the 2nd Gen 17 powerbook
 with ext3 as the file system and it works for now instead of booting
 into xfs.

 Upon startup and starting the network interfaces and then the
 portmap the fan turns on full throttle and spins for a while. It is
 semi loud and is rather annoying.   Is there a way not to have the
 fan spin when booting into Ubunto on startup?
 Is the fan a problem? As in; a fault that make it spin, instead of
 temp.? Anyway, I believe I had some sort of unagreement with my fan
 together with kernel 2.6.8, while at it, I'm not completely sure.

 -Adam
 Guess one would say it is not a problem however when booting into OSX
 the fan does not turn on unless of something really pushing the CPU
 hard.  On Ubuntu the fan is extremely sensitive and turns on with the
 slightest thing running.
 Yes, that could be what I mentioned, I installed debian testing and a
 vanilla kernel, problem solved.
 Can you file a bug report, including a diff of your .config and the
 debian stock one, as well as the version used ?

 Friendly,

 Sven Luther
 I am sorry for taking a bit long to list what I am been doing.  I have been
 trying many different scenarios and using different Debian Install disks. 
 Every Debian install disk has graphic issues when starting into Debian.  As
 soon as the kernel boots I get funky graphic lines that wave on the screen.
  I don't get any of this when using the Ubuntu install disk at all.  I just
 downloaded the latest reversion of Debian and burned the disk. 
 http://cdimage.debian.org/debian-cd/3.1_r2/powerpc/iso-cd/  But I can't any
 choice in yaboot that will give me a proper kernel to boot from.

 Is there something I can do because this is my 2nd powerbook that is very
 temperamental in using Linux and it is very frustrating.  All my G3s (bw),
 G4s, and G4 xserv all do very well and are running as servers and
 workstations quite nicely all the time.

 Stats:

 Machine Name:PowerBook G4 17
 Machine Model:   Powerbook5.5
 CPU Type:PowerPc G4 (1,1)
 CPU Speed:   1.5 GHz
 L2 Cache (per CPU):  512KB
 Memory:  2G
 Bus Speed:   167 MHz
 Boot Rom Version:4.86f0


 It was taking me some extra time because I have been trying to install a
 Debian system and use that so I can compare my configs compiled on Debian
 instead of Ubuntu with Debian's stock kernel.

 Is there a way I can not have any graphic distortion with lines scrolling
 up on the center of the monitor.

 -Adam
 
 Kmail seems to be workin' in debian again... ok, here is my .config file for 
 the kernel. And no flickering.
 
 Børge
 
 


Borge,  thank you very much.  :)  That had helped out perfectly.  I just made a 
few changes with file systems but it worked like it should :).   Now I can get 
back to business with the box and get it configured to the liking.

Another question:  Has people been able to get the keyboard to light up in 
Linux for the 17 PB?


Thanks,
-Adam


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

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

2006-08-16 Thread Adam D 
Rick Thomas wrote:
 
 On Aug 15, 2006, at 11:31 PM, Adam D wrote:
 
 Every Debian install disk has graphic issues when starting into
 Debian.  As soon as the kernel boots I get funky graphic lines that
 wave on the screen.  I don't get any of this when using the Ubuntu
 install disk at all.
 
 Does this web page from the Linux PowerPC FAQ-O-Matic help any?
 
 http://www.jonh.net/lppcfom-serve/cache/1043.html
 


Not for what I am experiencing but that is a good reference for info I can use 
on older boxes.  Thank you.

-Adam


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

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

2006-08-15 Thread Adam D 
Sven Luther wrote:
 On Fri, Aug 11, 2006 at 12:32:34AM +0200, Børge Holen wrote:
 On Friday 11 August 2006 00:17, Adam D wrote:
 Adam D wrote:
 BXrge Holen wrote:
 On Thursday 10 August 2006 23:53, Adam D wrote:
 OK,  I decided to just install Ubuntu on the 2nd Gen 17 powerbook with
 ext3 as the file system and it works for now instead of booting into
 xfs.

 Upon startup and starting the network interfaces and then the portmap
 the fan turns on full throttle and spins for a while. It is semi loud
 and is rather annoying.   Is there a way not to have the fan spin when
 booting into Ubunto on startup?
 Is the fan a problem? As in; a fault that make it spin, instead of
 temp.? Anyway, I believe I had some sort of unagreement with my fan
 together with kernel 2.6.8, while at it, I'm not completely sure.

 -Adam
 Guess one would say it is not a problem however when booting into OSX the
 fan does not turn on unless of something really pushing the CPU hard.  On
 Ubuntu the fan is extremely sensitive and turns on with the slightest
  thing running.
 Yes, that could be what I mentioned, I installed debian testing and a 
 vanilla 
 kernel, problem solved.
 
 Can you file a bug report, including a diff of your .config and the debian
 stock one, as well as the version used ?
 
 Friendly,
 
 Sven Luther
 
 

I am sorry for taking a bit long to list what I am been doing.  I have been 
trying many different scenarios and using different Debian Install disks.  
Every Debian install disk has graphic issues when starting into Debian.  As 
soon as the kernel boots I get funky graphic lines that wave on the screen.  I 
don't get any of this when using the Ubuntu install disk at all.  I just 
downloaded the latest reversion of Debian and burned the disk.  
http://cdimage.debian.org/debian-cd/3.1_r2/powerpc/iso-cd/  But I can't any 
choice in yaboot that will give me a proper kernel to boot from.  

Is there something I can do because this is my 2nd powerbook that is very 
temperamental in using Linux and it is very frustrating.  All my G3s (bw), 
G4s, and G4 xserv all do very well and are running as servers and workstations 
quite nicely all the time.

Stats:

Machine Name:   PowerBook G4 17
Machine Model:  Powerbook5.5
CPU Type:   PowerPc G4 (1,1)
CPU Speed:  1.5 GHz
L2 Cache (per CPU): 512KB
Memory: 2G
Bus Speed:  167 MHz
Boot Rom Version:   4.86f0


It was taking me some extra time because I have been trying to install a Debian 
system and use that so I can compare my configs compiled on Debian instead of 
Ubuntu with Debian's stock kernel.

Is there a way I can not have any graphic distortion with lines scrolling up on 
the center of the monitor.

-Adam


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

17 Powerbook fan turns on when starting into Ubuntu Dapper

2006-08-10 Thread Adam D 
OK,  I decided to just install Ubuntu on the 2nd Gen 17 powerbook with ext3 as 
the file system and it works for now instead of booting into xfs.  

Upon startup and starting the network interfaces and then the portmap the fan 
turns on full throttle and spins for a while. It is semi loud and is rather 
annoying.   Is there a way not to have the fan spin when booting into Ubunto on 
startup?  

-Adam


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

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

2006-08-10 Thread Adam D 
BXrge Holen wrote:
 On Thursday 10 August 2006 23:53, Adam D wrote:
 OK,  I decided to just install Ubuntu on the 2nd Gen 17 powerbook with
 ext3 as the file system and it works for now instead of booting into xfs.

 Upon startup and starting the network interfaces and then the portmap the
 fan turns on full throttle and spins for a while. It is semi loud and is
 rather annoying.   Is there a way not to have the fan spin when booting
 into Ubunto on startup?
 
 Is the fan a problem? As in; a fault that make it spin, instead of temp.?
 Anyway, I believe I had some sort of unagreement with my fan together with 
 kernel 2.6.8, while at it, I'm not completely sure.
 
 -Adam
 

Guess one would say it is not a problem however when booting into OSX the fan 
does not turn on unless of something really pushing the CPU hard.  On Ubuntu 
the fan is extremely sensitive and turns on with the slightest  thing running.  
I can't tell if it is heat related or not.  How does one tell?  As for the 
kernel.  I have not yet been able to have a good working kernel on the 17 
powerbook yet :(.  Any kernel that does run when switching from a graphical tty 
to another tty, the display goes so wacky on me.

-Adam


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

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

2006-08-10 Thread Adam D 
Adam D wrote:
 BXrge Holen wrote:
 On Thursday 10 August 2006 23:53, Adam D wrote:
 OK,  I decided to just install Ubuntu on the 2nd Gen 17 powerbook with
 ext3 as the file system and it works for now instead of booting into xfs.

 Upon startup and starting the network interfaces and then the portmap the
 fan turns on full throttle and spins for a while. It is semi loud and is
 rather annoying.   Is there a way not to have the fan spin when booting
 into Ubunto on startup?
 Is the fan a problem? As in; a fault that make it spin, instead of temp.?
 Anyway, I believe I had some sort of unagreement with my fan together with 
 kernel 2.6.8, while at it, I'm not completely sure.

 -Adam
 
 Guess one would say it is not a problem however when booting into OSX the fan 
 does not turn on unless of something really pushing the CPU hard.  On Ubuntu 
 the fan is extremely sensitive and turns on with the slightest  thing 
 running.  I can't tell if it is heat related or not.  How does one tell?  As 
 for the kernel.  I have not yet been able to have a good working kernel on 
 the 17 powerbook yet :(.  Any kernel that does run when switching from a 
 graphical tty to another tty, the display goes so wacky on me.
 
 -Adam
 
 

I had forgotten to mention that I am using the stock kernel (2.6.15-23-powerpc) 
when I did the install.

-Adam


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

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

2006-08-10 Thread Adam D 
BXrge Holen wrote:
 On Friday 11 August 2006 00:17, Adam D wrote:
 Adam D wrote:
 BXrge Holen wrote:
 On Thursday 10 August 2006 23:53, Adam D wrote:
 OK,  I decided to just install Ubuntu on the 2nd Gen 17 powerbook with
 ext3 as the file system and it works for now instead of booting into
 xfs.

 Upon startup and starting the network interfaces and then the portmap
 the fan turns on full throttle and spins for a while. It is semi loud
 and is rather annoying.   Is there a way not to have the fan spin when
 booting into Ubunto on startup?
 Is the fan a problem? As in; a fault that make it spin, instead of
 temp.? Anyway, I believe I had some sort of unagreement with my fan
 together with kernel 2.6.8, while at it, I'm not completely sure.

 -Adam
 Guess one would say it is not a problem however when booting into OSX the
 fan does not turn on unless of something really pushing the CPU hard.  On
 Ubuntu the fan is extremely sensitive and turns on with the slightest
  thing running.
 Yes, that could be what I mentioned, I installed debian testing and a vanilla 
 kernel, problem solved.
 
  I can't tell if it is heat related or not.  How does one 
 tell?  As for the kernel.  I have not yet been able to have a good
 working kernel on the 17 powerbook yet :(.  Any kernel that does run when
 switching from a graphical tty to another tty, the display goes so wacky
 on me.
 
 
 This was fixed when I booted a new vanilla. BUT seems to happen occationaly, 
 every once a weeked... and is fixed by going back and forth one more time. 
 

Is it possible to get a copy of your kernel config and is it the latest 
(2.6.17.7)?  Every time I tried to compile a vanilla kernel it just does not 
work for me on the 17 powerbook but it works for my other G4s, G3s, and xserv.

-Adam


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

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

2006-08-10 Thread Adam D 
Charles Plessy wrote:
 Le Thu, Aug 10, 2006 at 02:53:34PM -0700, Adam D a écrit :
 Upon startup and starting the network interfaces and then the portmap
 the fan turns on full throttle and spins for a while. It is semi loud
 and is rather annoying.   Is there a way not to have the fan spin when
 booting into Ubunto on startup?  
 
 
 Dear Adam,
 
 isn't it that some fan drivers do not work when compiled as modules? At
 least it is the case on iMacs. Are you using a windfarm fan driver?
 
 Have a nice day,
 

I am not to sure.  It is the same kernel Ubuntu stock kernel from installation 
(2.6.15-23-powerpc).  I have taken the config from that kernel and made my own 
with the latests stable vanilla kernel but it did not work to well.

I am going to try to compile it again tonight.  I do think the stock kernel has 
the windfarm as a module as most of the stock kernel is compiled with modules 
all around.

-Adam


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

Re: accessing hfs journeling in 2.6.16.14 fixed?

2006-05-10 Thread Adam D 
ruben wrote:
 At Tue, 09 May 2006 14:26:04 +0200, Johannes Berg wrote:
 On Tue, 2006-05-09 at 05:18 -0700, Adam D wrote:

 I can mount HFSplus however...
 # mount -t hfsplus /dev/hda5 /mnt/x
 # touch test
 touch: cannot touch `test': Read-only file system
 If you'd bother to check the kernel messages you'd see. And earlier
 kernels didn't really support it, they just did it anyway.
 
 Ah... this confirms what I thought, nl., that only read-write to
 non-journalled HFS+ is supported/safe/whatever.  That's why I just use
 a HFS+ partition without journalling.
 
 It can still, however, be mounted read-write, while not allowing
 writes and then you get a similar message.  That happens when the file
 system was not cleanly unmounted and needs to be checked.  That can be
 done by simply booting into OSX, which will run a file system check
 during bootup.
 
 ruben
 


Ahhh.. that does explain a lot actually.  Thanks...   


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

Re: accessing hfs journeling in 2.6.16.14 fixed?

2006-05-09 Thread Adam D 
Adam D wrote:
 Bernhard Reiter wrote:
 On Sat, May 06, 2006 at 03:59:47PM -0700, Adam D wrote:
 Has anyone else not been able to access HFS journaling file
 systems?  Ever since I upgraded my kernel to 2.6.16.12 and have
 been able to access HFSX but lost any mounting of HFS journaling.
 Is this fixed in 2.6.16.14?
 I can mount /dev/hda3 (my HFSplus partition from MacOS 10) 
 with -t hfsplus without problems on 2.6.17-rc3.
 As I have build this support as a module, I have to do
  modprobe hfsplus
 before doing so.

 
 I can mount the HFSplus as well but not with journeling turned on.  Now with 
 my 2.6.13.1 kernel which I have been using since last year has been working 
 with journeling enabled and can mount all my HFSplus journeling partitions.  
 When I updated to the 2.6.16.12 kernel I can now mount HFSX which is GREAT :) 
  but I then lost all capacity to mount any of my HFSplus with journeling.  
 
 Was there a change to the kernel code?  Everything is still the same as it 
 was in my other working kernel and it was compiled directly into the kernel.
 
 -Adam
 
 

UPDATE:

I can mount HFSplus however...
# mount -t hfsplus /dev/hda5 /mnt/x
# touch test
touch: cannot touch `test': Read-only file system

This is only because it has journaling activated.. without.. I can write and 
such.  I am also getting the same issue with the most current vanilla kernel.

-Adam


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

Re: accessing hfs journeling in 2.6.16.14 fixed?

2006-05-08 Thread Adam D 
Bernhard Reiter wrote:
 On Sat, May 06, 2006 at 03:59:47PM -0700, Adam D wrote:
 Has anyone else not been able to access HFS journaling file
 systems?  Ever since I upgraded my kernel to 2.6.16.12 and have
 been able to access HFSX but lost any mounting of HFS journaling.
 Is this fixed in 2.6.16.14?
 
 I can mount /dev/hda3 (my HFSplus partition from MacOS 10) 
 with -t hfsplus without problems on 2.6.17-rc3.
 As I have build this support as a module, I have to do
   modprobe hfsplus
 before doing so.
 

I can mount the HFSplus as well but not with journeling turned on.  Now with my 
2.6.13.1 kernel which I have been using since last year has been working with 
journeling enabled and can mount all my HFSplus journeling partitions.  When I 
updated to the 2.6.16.12 kernel I can now mount HFSX which is GREAT :)  but I 
then lost all capacity to mount any of my HFSplus with journeling.  

Was there a change to the kernel code?  Everything is still the same as it was 
in my other working kernel and it was compiled directly into the kernel.

-Adam


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

accessing hfs journeling in 2.6.16.14 fixed?

2006-05-06 Thread Adam D 
Has anyone else not been able to access HFS journaling file systems?  Ever 
since I upgraded my kernel to 2.6.16.12 and have been able to access HFSX but 
lost any mounting of HFS journaling.  Is this fixed in 2.6.16.14?

-Adam


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

Re: Solid lockup on latest benh 2.6 kernel + PB 12

2004-02-19 Thread Adam D 




On Tue, 2004-02-17 at 05:22, Benjamin Herrenschmidt wrote:

On Tue, 2004-02-17 at 12:36, David Pye wrote:
 Hi,
 
 I've got an Albook G4 12 powerbook (NVidia GFX) and I have been experiencing 
 a number of hard crashes since installing the latest benh rsync'd kernel and 
 Debian Sid (same result as a two day old benh rsync'd one). (compiled 
 gcc-3.3)
 
 The crash APPEARS to be related to the framebuffer -there's no oops etc, just 
 a complete lockup.

What happens if you boot with video=ofonly or video=rivafb:noaccel ?

Ben.




I am having the same problems my self and been working on this for the last week know and my 2.6 benh kernel always stop on boot process when it gets to the ps/2 mouse... never going on further. I tried using 


video=ofonly
video=rivafb:noaccel
and
video=aty128fb:noaccel



each of these just gives me a blank screen. I can't even look at any loged messages because nothing gets to the point in the boot process to log to syslog.

I also found when compiling the kernel changing

SERIO_I8042 to N
SERIO_SERPORT to N

I can boot all the way.. BUT then I can not use a mouse 

Now when i boot into a 2.6.3 kernel.org kernel.. i can boot all the way but the FB is all mest up. When having GDM start up in the boot process I only get one of my X sessions.. I have 2 X sessions started.. one on tty6 and the other on tty7 and the one on tty6 is the only usable session. I also can not use any of my tty1-5 terminals. This happens with any 2.6 kernel I use... I know.. the FB is dif in 2.6 but for some reason I can't fix this.