Re: Trouble getting bcm43xx driver to work

2006-01-10 Thread Aaron
: Device lookup failed
[   59.875903] device-mapper: error adding target to table
[   59.876386] device-mapper: dm-linear: Device lookup failed
[   59.876391] device-mapper: error adding target to table
[   59.876930] device-mapper: dm-linear: Device lookup failed
[   59.876935] device-mapper: error adding target to table
[   59.877427] device-mapper: dm-linear: Device lookup failed
[   59.877431] device-mapper: error adding target to table
[   59.877964] device-mapper: dm-linear: Device lookup failed
[   59.877970] device-mapper: error adding target to table
[   59.878471] device-mapper: dm-linear: Device lookup failed
[   59.878476] device-mapper: error adding target to table
[   70.591242] hStart = 1048, hEnd = 1184, hTotal = 1344
[   70.591250] vStart = 771, vEnd = 777, vTotal = 806
[   70.591256] h_total_disp = 0x7f00a7 hsync_strt_wid = 0x910412
[   70.591260] v_total_disp = 0x2ff0325vsync_strt_wid = 0x860302
[   70.591263] pixclock = 15384
[   70.591265] freq = 6500
[   72.098455] Bluetooth: Core ver 2.8
[   72.098465] NET: Registered protocol family 31
[   72.098468] Bluetooth: HCI device and connection manager initialized
[   72.098484] Bluetooth: HCI socket layer initialized
[   72.180645] Bluetooth: L2CAP ver 2.8
[   72.180654] Bluetooth: L2CAP socket layer initialized
[   72.319271] Bluetooth: RFCOMM socket layer initialized
[   72.319304] Bluetooth: RFCOMM TTY layer initialized
[   72.319308] Bluetooth: RFCOMM ver 1.6
[   73.476291] evbug.c: Disconnected device: NULL
[   73.476306] evbug.c: Disconnected device: adb2:2.c3/input
[   73.476311] evbug.c: Disconnected device: adb7:7.1f/input
[   73.476316] evbug.c: Disconnected device: usb-0001:10:1a.0-1/input0
[   73.476321] evbug.c: Disconnected device: usb-0001:10:1a.0-1/input1
[   73.476327] evbug.c: Disconnected device: powermac/beep
[   73.476332] evbug.c: Disconnected device: usb-0001:10:1a.0-2/input0
[   75.044689] hStart = 1048, hEnd = 1184, hTotal = 1344
[   75.044696] vStart = 771, vEnd = 777, vTotal = 806
[   75.044702] h_total_disp = 0x7f00a7 hsync_strt_wid = 0x910415
[   75.044706] v_total_disp = 0x2ff0325vsync_strt_wid = 0x860302
[   75.044709] pixclock = 15384
[   75.044711] freq = 6500
[   75.581627] [drm] Initialized drm 1.0.0 20040925
[   82.346853] adt746x: setting fans speed to 64 (limit exceeded by 1 on CPU 
BOTTOMSIDE) 
[   82.346870] adt746x: Setting speed to 64 for CPU BOTTOMSIDE fan.
[  248.678814] adt746x: Stopping fans.
[  248.678830] adt746x: Setting speed to 0 for CPU BOTTOMSIDE fan.
[  687.989305] bcm43xx: PHY connected
[  688.229103] bcm43xx: Radio turned on
[  688.401262] bcm43xx: Chip initialized
[  688.402045] bcm43xx: DMA initialized
[  688.402060] bcm43xx: 80211 cores initialized
[  688.402282] bcm43xx: Keys cleared
[  875.402130] SoftMAC: Start scanning with channel: 1
[  875.402145] SoftMAC: Scanning 13 channels
[  881.957561] SoftMAC: Scanning finished
[  943.337329] SoftMAC: 
/usr/src/ieee80211softmac-20060110/ieee80211softmac_assoc.c:157:ieee80211softmac_assoc_work()
[  943.337360] SoftMAC: 
/usr/src/ieee80211softmac-20060110/ieee80211softmac_auth.c:13:ieee80211softmac_auth_req()
[  943.337373] SoftMAC: Queueing Authentication Request to 00:90:4c:7e:00:64
[  943.337384] SoftMAC: cannot associate without being authenticated, requested 
authentication
[  943.337396] SoftMAC: 
/usr/src/ieee80211softmac-20060110/ieee80211softmac_auth.c:55:ieee80211softmac_auth_queue()
[  943.345322] SoftMAC: Sent Authentication Request to 00:90:4c:7e:00:64.
[  955.341566] SoftMAC: 
/usr/src/ieee80211softmac-20060110/ieee80211softmac_auth.c:55:ieee80211softmac_auth_queue()
[  955.349457] SoftMAC: Sent Authentication Request to 00:90:4c:7e:00:64.
[  965.365516] SoftMAC: Start scanning with channel: 1
[  965.365532] SoftMAC: Scanning 13 channels
[  967.345565] SoftMAC: 
/usr/src/ieee80211softmac-20060110/ieee80211softmac_auth.c:55:ieee80211softmac_auth_queue()
[  967.353460] SoftMAC: Sent Authentication Request to 00:90:4c:7e:00:64.
[  971.921560] SoftMAC: Scanning finished
[  976.895928] NET: Registered protocol family 17
[  979.349566] SoftMAC: 
/usr/src/ieee80211softmac-20060110/ieee80211softmac_auth.c:55:ieee80211softmac_auth_queue()
[  979.357464] SoftMAC: Sent Authentication Request to 00:90:4c:7e:00:64.
[  991.353566] SoftMAC: 
/usr/src/ieee80211softmac-20060110/ieee80211softmac_auth.c:55:ieee80211softmac_auth_queue()
[  991.361448] SoftMAC: Sent Authentication Request to 00:90:4c:7e:00:64.
[  993.640891] bcm43xx: Radio turned off
[  993.640963] bcm43xx: DMA 0x0200 (RX) max used slots: 1/64
[  993.641060] bcm43xx: DMA 0x0260 (TX) max used slots: 0/512
[  993.641366] bcm43xx: DMA 0x0240 (TX) max used slots: 0/512
[  993.641670] bcm43xx: DMA 0x0220 (TX) max used slots: 2/512
[  993.641975] bcm43xx: DMA 0x0200 (TX) max used slots: 0/512
[ 1017.514718] bcm43xx: Radio turned on
[ 1017.530735] bcm43xx: Chip initialized
[ 1017.531006] bcm43xx: DMA initialized
[ 1017.531020] bcm43xx: 80211 cores initialized

Re: Files for BootX

2006-01-10 Thread Clive Menzies
On (09/01/06 18:11), Chris Fisichella wrote:
 I am on my sixth attempt to install Debian on a Powerbook G3 
 (Wallstreet). I am out of ideas. I have OpenFirmware  3.0, so I tried 
 the following:
 
 1. boot from floppies. four floppies, two different writing methods; I 
 think my floppy drive is too picky.
 
 2. BootX: I could have sworn I downloaded the ramdisk.img.gz file from 
 Debian, but, now I go back and cannot find it. I made it the farthest 
 with this method. I got to the point where it asks for the installation 
 CD, but, then the installer could not find the files rescue.bin and 
 powermac/drivers.tgz. I could not find these anywhere on the CD, either.
 
 3. yaboot. Did not work as the documentation said it would not.
 
 4. Quik: I could not figure out how to create a unix partition for this 
 program to use. I tried the Apple Linux Home partition, but that did 
 not work. I was skeptical that Apple would support Linux anyhow.
 
 Acutely aware of the patience of the readership, I present the 
 following questions in decreasing order of importance:
 
 a) Where do I get the ramdisk.img.gz and linux.bin files BootX is 
 looking for? The installation CD and the ftp site seem to be pushing 
 yaboot and floppies.
 Get BootX from here:

 http://penguinppc.org/historical/benh/

 It's a while since i did this but it was pretty straight forward and
 quite a few people have documented the process ... google around, you
 should find loads.

Here's one:

 http://www.ppcnux.de/modules.php?name=Contentpa=showpagepid=79

Regards

Clive

-- 
www.clivemenzies.co.uk ...
...strategies for business



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



Re: Files for BootX

2006-01-10 Thread Hans Ekbrand
On Mon, Jan 09, 2006 at 06:11:31PM -0500, Chris Fisichella wrote:
 Hi,
 
 I am on my sixth attempt to install Debian on a Powerbook G3 
 (Wallstreet). I am out of ideas. I have OpenFirmware  3.0, so I tried 
 the following:
 
 1. boot from floppies. four floppies, two different writing methods; I 
 think my floppy drive is too picky.
 
 2. BootX: I could have sworn I downloaded the ramdisk.img.gz file from 
 Debian, but, now I go back and cannot find it. I made it the farthest 
 with this method. I got to the point where it asks for the installation 
 CD, but, then the installer could not find the files rescue.bin and 
 powermac/drivers.tgz. I could not find these anywhere on the CD, either.
 
 3. yaboot. Did not work as the documentation said it would not.
 
 4. Quik: I could not figure out how to create a unix partition for this 
 program to use. I tried the Apple Linux Home partition, but that did 
 not work. I was skeptical that Apple would support Linux anyhow.

Quik can only work after you have completed the installation. It is
not useful to start an installation.

 Acutely aware of the patience of the readership, I present the 
 following questions in decreasing order of importance:
 
 a) Where do I get the ramdisk.img.gz and linux.bin files BootX is 
 looking for? The installation CD and the ftp site seem to be pushing 
 yaboot and floppies.

These filenames are not used anymore, the installation manual still
mentions them, but that is a known bug in the installation manual (bug
#344477).

The new filenames are vmlinux and initrd.gz

I you aim for an installation started with BootX and loading the rest
from an installation-CD, you should use the cdrom flavour of the
vmlinux/initrd.gz files, located at:

http://ftp.debian.org/debian/dists/sarge/main/installer-powerpc/current/images/powerpc/cdrom/

I don't know where on the installation-cd these files are located.

 b) Is BootX the way to go? I would like to have both MacOS9 and Sarge 
 on the same machine. It seems reasonable and, like I wrote previously, 
 it seemed to work the best for my setup.

Yes.

-- 
Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED]
Signature generated by Signify v1.14.  For this and more, visit 
http://www.debian.org/


signature.asc
Description: Digital signature


Re: Files for BootX

2006-01-10 Thread Hans Ekbrand
On Tue, Jan 10, 2006 at 11:29:26AM +, Clive Menzies wrote:
 On (09/01/06 18:11), Chris Fisichella wrote:

[...]

  2. BootX: I could have sworn I downloaded the ramdisk.img.gz file from 
  Debian, but, now I go back and cannot find it. I made it the farthest 
  with this method. I got to the point where it asks for the installation 
  CD, but, then the installer could not find the files rescue.bin and 
  powermac/drivers.tgz. I could not find these anywhere on the CD, either.

[...]

  a) Where do I get the ramdisk.img.gz and linux.bin files BootX is 
  looking for? The installation CD and the ftp site seem to be pushing 
  yaboot and floppies.
  Get BootX from here:
 
  http://penguinppc.org/historical/benh/

The OP already goot BootX working, se point #2 above. The OP wants to
know where to get the kernel and initrd that starts (or is) the
debian-installer.

-- 
Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED]
Q. What is that strange attachment in this mail?
A. My digital signature, see www.gnupg.org for info on how you could
   use it to ensure that this mail is from me and has not been
   altered on the way to you.


signature.asc
Description: Digital signature


Re: Trouble getting bcm43xx driver to work

2006-01-10 Thread Ruben

At Tue, 10 Jan 2006 21:51:36 +1100, Aaron wrote:
 
 Still no joy. With the last two days snapshots I get a new error using 
 iwconfig:
 [EMAIL PROTECTED]:~$ iwconfig
 lono wireless extensions.
 
 eth3  IEEE 802.11b/g  ESSID:EucalyptusMarginata  Nickname:Broadcom 
 4318
 iwconfig: symbol lookup error: iwconfig: undefined symbol: iw_sawap_ntop
 [EMAIL PROTECTED]:~$ 

I tested both the devicescape branch and the softmac branch, both with
WEP, two days ago. I didn't get any errors like this though.

 [...]
 # Check routing for local wireless network traffic is there
 [EMAIL PROTECTED]:~# netstat -r
 Kernel IP routing table
 Destination Gateway Genmask Flags   MSS Window  irtt Iface
 192.168.73.0*   255.255.255.0   U 0 0  0 eth3

I did not get dhcp to work either.  I could see on my AP that it
receives the dhcp request and it seems to hand out an IP address for
60 seconds. I assume it then waits for a confirmation from my iBook
before handing out a 'real' lease. But it doesn't seem to get that
confirmation.

I do get it working with a fixed IP address, like what you tried.  I
did add the default route to the gateway, though.  And more
importantly, I always have to wait some time before it works.  Right
after configuring the interface and adding the route, all connections
will fail. But after trying new connections for 2-3 minutes (trying to
load some websites and pinging), it suddenly works.  From then on the
connection works just fine.  I also noticed that right after adding
the default route, the command route will print out the route for
local connections and then pause a while before printing out the
default route.  I have no idea why this is or what I can do about it,
but at least I have a wireless connection now.

 # I think it may be time to but a USB wireless device until bcm43xx
 # is easier!

There's definitely still some hassle with the bcm43xx driver... but
for me it's good enough for now.

Ruben

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm


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



Re: [powerpc-floppies] Help Needed : root.img too big (1489688, should be 1474560).

2006-01-10 Thread Denis Barbier
On Mon, Jan 09, 2006 at 12:55:51AM +0100, Sven Luther wrote:
 Hi, ...
 
 I am requesting, on behalf of the powerpc oldworld floppies users, some help
 to solve the problem of too big root.img. 
 
 The file is 1489688 bytes, while the floppy size is 1474560, so it is 15128
 bytes to huge. I had a quick look at the floppy pkg-lists, but i couldn't see
 anything obvious to move around to another floppy, maybe the the socket
 modules could move to the net-drivers floppy or something, but that is about
 it, and i think socket-modules is empty right now anyway.
 
 So, it would be very nice if someone with knowledge of the floppies would take
 a look and see where we can gain those 15128 bytes, maybe removing one of the
 console maps (we have usb and at, but oldworld only have adb keymaps, not sure
 what it maps to though), and also add the bit of code Frans mentioned the x86
 floppies already have for failing if the image size is bigger than a floppy. I
 searched for it in config/i386, but failed to find anything that did something
 like this.

Hi Sven,

here is a patch against installation-locale, it saves about 35kB in the
udeb by dropping definitions for transliteration.  Since we try hard to
include all glyphs, these definitions are surely useless.

Denis


installation-locale.patch.gz
Description: Binary data


Re: Poll: debian/powerpc woody users ...

2006-01-10 Thread Eugen Paiuc

Hi,

I's very nice to see a OldWorld migrating from woody 2.2-pmac to sarge 
2.6.12-1-powerpc !

And that is done right now.
The main issue was quik. Writing the quik.conf  a la grub's menu.lst, and a

#quik -S /boot/first.b

put the new kernel in place !



regards,

Eugen Paiuc


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



Re: Trouble getting bcm43xx driver to work

2006-01-10 Thread Michael Schmitz
 connection works just fine.  I also noticed that right after adding
 the default route, the command route will print out the route for
 local connections and then pause a while before printing out the
 default route.  I have no idea why this is or what I can do about it,
 but at least I have a wireless connection now.

That's the DNS lookup timeout for your default route - use route -n or
make sure the AP IP address resolves (add it to your local DNS cache or
/etc/hosts).

Overall it seems you guys even got WEP working now? I need to try this
again ...

Michael


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



How about the new MacBook

2006-01-10 Thread Jaonary Rabarisoa

Hi all,

One more thing : MacBook pro is out :-) The specification seems to be  
great, up to 4 time faster the the powerbook, intel dual core,  
isight, ... Hmm It's exiting me
But, how about debian on it, only install the x86 version or need to  
do some little hack before ?


Regards,


Jaonary


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



Re: Poll: debian/powerpc woody users ...

2006-01-10 Thread Rich Johnson
I have a powermac 6116CD (NuBus) running stable/sarge on a 2.4.21  
kernel.


Whether ''supported'' or not, the dist-upgrade from woody went  
smoothly; though the fact that there are no NuBus cards in the  
machine may have something to do with that.



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



Re: How about the new MacBook

2006-01-10 Thread Elimar Riesebieter
On Tue, 10 Jan 2006 the mental interface of
Jaonary Rabarisoa told:

 Hi all,
 
 One more thing : MacBook pro is out :-) The specification seems to be great, 
 up 
 to 4 time faster the the powerbook, intel dual core, isight, ... Hmm It's 
 exiting me
 But, how about debian on it, only install the x86 version or need to do some 
 little hack before ?

Is it a powerbook, really? You'll get more fun with an t43(p) then.
It's inteldriven as well.

ELimar


-- 
  We all know Linux is great... it does infinite loops in 5 seconds.
-- Linus Torvalds


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



Re: How about the new MacBook

2006-01-10 Thread Gabriel Paubert
On Tue, Jan 10, 2006 at 08:41:44PM +0100, Jaonary Rabarisoa wrote:
 Hi all,
 
 One more thing : MacBook pro is out :-) The specification seems to be  
 great, up to 4 time faster the the powerbook, intel dual core,  
 isight, ... Hmm It's exiting me

It has an Intel (x86) processor so it is completely  
completely off-topic on the debian-powerpc list.

Take benchmarks with a pinch of salt (although it 
is likely much faster, mostly because of the huge 
increase in memory bandwdith, it's sad that no G4
processor ever had a faster or dual edge data bus).
For example, you'll never get the factor of 4 on RC5.

If you want to buy one, go ahead, but remember that the
only (possible) advantage over any run-of-the-mill
Intel or AMD based laptop is that it will run MacOS.

On my side I'm expecting a G4 17 any day now (it 
has shipped). This will for sure be my last Apple
laptop and I cross fingers hoping somebody will 
build PPC based laptops in the future. For me
the only reason to buy an Apple system was that 
part of my job involves developing for PPC embedded 
systems, not that it ships with MacOS, iLife or
whatever applications.

 But, how about debian on it, only install the x86
 version or need to do some little hack before ?

I don't know and I really don't care. If you really
want to discuss this, you should do it on another
mailing list.

Regards,
Gabriel


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



Re: How about the new MacBook

2006-01-10 Thread Sven Luther
On Tue, Jan 10, 2006 at 09:48:21PM +0100, Gabriel Paubert wrote:
 On my side I'm expecting a G4 17 any day now (it 
 has shipped). This will for sure be my last Apple
 laptop and I cross fingers hoping somebody will 
 build PPC based laptops in the future. For me
 the only reason to buy an Apple system was that 
 part of my job involves developing for PPC embedded 
 systems, not that it ships with MacOS, iLife or
 whatever applications.

I guess right now genesi is probably your best hope for that, altough the only
laptop on the official roadmap is the 4u2, which is a sub-laptop based on the
MPC5200 cpu.

Friendly,

Sven Luther


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



Re: How about the new MacBook

2006-01-10 Thread Jack Malmostoso
On Tue, 10 Jan 2006 21:20:22 +0100, Elimar Riesebieter wrote:

 You'll get more fun with an t43(p) then

What is it?

-- 
Best Regards, Jack
Linux User #264449
Powered by Debian GNU/Linux on AMD64


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



Re: How about the new MacBook

2006-01-10 Thread Jesse Scherer
An IBM professional-series laptop.On 10/01/06, Jack Malmostoso [EMAIL PROTECTED] wrote:
On Tue, 10 Jan 2006 21:20:22 +0100, Elimar Riesebieter wrote: You'll get more fun with an t43(p) then
What is it?--Best Regards, JackLinux User #264449Powered by Debian GNU/Linux on AMD64--To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


Re: How about the new MacBook

2006-01-10 Thread Elimar Riesebieter
On Tue, 10 Jan 2006 the mental interface of
Jack Malmostoso told:

 On Tue, 10 Jan 2006 21:20:22 +0100, Elimar Riesebieter wrote:
 
  You'll get more fun with an t43(p) then
 
 What is it?

It is a ThinkPad ;)

http://www-131.ibm.com/webapp/wcs/stores/servlet/CategoryDisplay?catalogId=-840storeId=1001langId=-1dualCurrId=73categoryId=2072541

Elimar

-- 
  Talking much about oneself can also 
   be a means to conceal oneself.
 -Friedrich Nietzsche


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



Re: [powerpc-floppies] Help Needed : root.img too big (1489688, should be 1474560).

2006-01-10 Thread Joey Hess
Denis Barbier wrote:
 here is a patch against installation-locale, it saves about 35kB in the
 udeb by dropping definitions for transliteration.  Since we try hard to
 include all glyphs, these definitions are surely useless.

That is awesome. 35k freed in all our images is a princely gift. I'm
going to apply this now.

-- 
see shy jo


signature.asc
Description: Digital signature


Re: [powerpc-floppies] Help Needed : root.img too big (1489688, should be 1474560).

2006-01-10 Thread Sven Luther
On Tue, Jan 10, 2006 at 05:27:59PM -0500, Joey Hess wrote:
 Denis Barbier wrote:
  here is a patch against installation-locale, it saves about 35kB in the
  udeb by dropping definitions for transliteration.  Since we try hard to
  include all glyphs, these definitions are surely useless.

Thanks Denis for this patch, this should solve the problem for the powerpc
root floppies, and make them installable again.

 That is awesome. 35k freed in all our images is a princely gift. I'm
 going to apply this now.

Cool, ...

BTW, i fail to build the powerpc root floppy here, i only get the following
mklibs error : 

bject: ./tmp/powerpc_floppy_root/tree/driver-tmp/usr/bin/eject
457 symbols, 406 unresolved
Traceback (most recent call last):
  File /usr/bin/mklibs, line 442, in ?
raise No library provides non-weak  + symbol
No library provides non-weak SLang_init_tty
make[3]: *** [stamps/tree-powerpc_floppy_root-stamp] Erreur 1

Anyone has any hint about this ?

Friendly,

Sven Luther




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



Re: Trouble getting bcm43xx driver to work

2006-01-10 Thread Aaron Kerr

Thanks. I will try waiting a few minutes after setting up the connection.

Your delays when running route or netstat could be a DNS lookup failure.
Try netstat -rn which will not try to translate IP addresses to names.


Ruben wrote:
 At Tue, 10 Jan 2006 21:51:36 +1100, Aaron wrote:
 
Still no joy. With the last two days snapshots I get a new error using 
iwconfig:
[EMAIL PROTECTED]:~$ iwconfig
lono wireless extensions.

eth3  IEEE 802.11b/g  ESSID:EucalyptusMarginata  Nickname:Broadcom 
4318
iwconfig: symbol lookup error: iwconfig: undefined symbol: iw_sawap_ntop
[EMAIL PROTECTED]:~$ 
 
 
 I tested both the devicescape branch and the softmac branch, both with
 WEP, two days ago. I didn't get any errors like this though.
 
 
[...]
# Check routing for local wireless network traffic is there
[EMAIL PROTECTED]:~# netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags   MSS Window  irtt Iface
192.168.73.0*   255.255.255.0   U 0 0  0 eth3
 
 
 I did not get dhcp to work either.  I could see on my AP that it
 receives the dhcp request and it seems to hand out an IP address for
 60 seconds. I assume it then waits for a confirmation from my iBook
 before handing out a 'real' lease. But it doesn't seem to get that
 confirmation.
 
 I do get it working with a fixed IP address, like what you tried.  I
 did add the default route to the gateway, though.  And more
 importantly, I always have to wait some time before it works.  Right
 after configuring the interface and adding the route, all connections
 will fail. But after trying new connections for 2-3 minutes (trying to
 load some websites and pinging), it suddenly works.  From then on the
 connection works just fine.  I also noticed that right after adding
 the default route, the command route will print out the route for
 local connections and then pause a while before printing out the
 default route.  I have no idea why this is or what I can do about it,
 but at least I have a wireless connection now.
 
 
# I think it may be time to but a USB wireless device until bcm43xx
# is easier!
 
 
 There's definitely still some hassle with the bcm43xx driver... but
 for me it's good enough for now.
 
 Ruben
 
 Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
 
 


-- 

Aaron Kerr
-
Engagement Architect
Sun Microsystems


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



Re: How about the new MacBook

2006-01-10 Thread Benjamin Herrenschmidt
On Tue, 2006-01-10 at 20:41 +0100, Jaonary Rabarisoa wrote:
 Hi all,
 
 One more thing : MacBook pro is out :-) The specification seems to be  
 great, up to 4 time faster the the powerbook, intel dual core,  

Welcome to Apple's new benchmark, the JobsMark, guaranteed 100% free of
any scientific value

 But, how about debian on it, only install the x86 version or need to  
 do some little hack before ?

I suggest you ask that elsewhere

Ben.



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



Re: How about the new MacBook

2006-01-10 Thread vinai

On Wed, 11 Jan 2006, Benjamin Herrenschmidt wrote:


On Tue, 2006-01-10 at 20:41 +0100, Jaonary Rabarisoa wrote:


Hi all,

One more thing : MacBook pro is out :-) The specification seems to be
great, up to 4 time faster the the powerbook, intel dual core,


Welcome to Apple's new benchmark, the JobsMark, guaranteed 100% free of
any scientific value


But, how about debian on it, only install the x86 version or need to
do some little hack before ?


I suggest you ask that elsewhere


According to a posting from one of the darwin developer lists, the new
Intel based macs use EFI for booting.  So anything that made macs what
we KNEW as macs (i.e. Open Firmware and PowerPC CPUs) are now gone.  I
suspect that as soon as Intel can manufacture a decent 64-bit competitor
to match the Opeteron, the rest of the lines (Power Macintosh and Xserve)
will be transitioned to Intel.

So any questions on these, and future, macs will be more appropriate to
the debian x86, x86-64, and maybe even ia-64 lists (not sure if there
are any non-ia-64 EFI machines).

Let us have a moment of silence everyone ...

cheers
vinai


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



Re: [powerpc-floppies] Help Needed : root.img too big (1489688, should be 1474560).

2006-01-10 Thread Steve Langasek
On Tue, Jan 10, 2006 at 11:58:21PM +0100, Sven Luther wrote:
 On Tue, Jan 10, 2006 at 05:27:59PM -0500, Joey Hess wrote:
  Denis Barbier wrote:
   here is a patch against installation-locale, it saves about 35kB in the
   udeb by dropping definitions for transliteration.  Since we try hard to
   include all glyphs, these definitions are surely useless.

 Thanks Denis for this patch, this should solve the problem for the powerpc
 root floppies, and make them installable again.

  That is awesome. 35k freed in all our images is a princely gift. I'm
  going to apply this now.

 Cool, ...

 BTW, i fail to build the powerpc root floppy here, i only get the following
 mklibs error : 

 bject: ./tmp/powerpc_floppy_root/tree/driver-tmp/usr/bin/eject
 457 symbols, 406 unresolved
 Traceback (most recent call last):
   File /usr/bin/mklibs, line 442, in ?
 raise No library provides non-weak  + symbol
 No library provides non-weak SLang_init_tty
 make[3]: *** [stamps/tree-powerpc_floppy_root-stamp] Erreur 1

 Anyone has any hint about this ?

Are other images building?  I just fixed mklibs to cope with a change in
readelf output on alpha; if this error isn't target-specific, there may be a
similar change on powerpc that we need to cope with.  If so, the output of
readelf -s -D -W /lib/libslang.so.2 should be helpful here.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


signature.asc
Description: Digital signature


Re: xorg-6.9.0 and nautilus-2.12.2-1

2006-01-10 Thread Shreyas Ananthan
Antonio-M. Corbi Bellot [EMAIL PROTECTED] writes:


 Just upgraded my pbook with a nvidia card to xorg-6.9.0 and everything
 seems to work ok except nautilus (my version is 2.12.2-1), the desktop
 is drawn corrupted, every other application works ok.

I experience the same problem. For the time being I disabled nautilus'
ability to redraw desktop using the command...

gconftool -2 -s /apps/nautilius/preferences/show_desktop -t bool false


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



Re: Trouble getting bcm43xx driver to work

2006-01-10 Thread Shreyas Ananthan
Hi,

I tried the bcm43xx-dscape driver with a patched 2.6.15 kernel on my
iBook G4 12 and I cannot get it to work. Some relevant information...

CPU information

processor   : 0
cpu : 7447A, altivec supported
clock   : 1333MHz
revision: 0.5 (pvr 8003 0105)
bogomips: 1327.10
machine : PowerBook6,7
motherboard : PowerBook6,7 MacRISC3 Power Macintosh
detected as : 287 (iBook G4)
pmac flags  : 001b
L2 cache: 512K unified
memory  : 1024MB
pmac-generation : NewWorld


Output from lspci -vv

0001:10:12.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 
54g] 802.11g Wireless LAN Controller (rev 02)
Subsystem: Apple Computer Inc.: Unknown device 4318
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR-
Latency: 16
Interrupt: pin A routed to IRQ 52
Region 0: Memory at 80084000 (32-bit, non-prefetchable) [disabled] 
[size=8K]


I am using the January 10, 2006 snapshot of bcm43xx on 2.6.15 kernel
with the unofficial patch available at bcm43xx.berlios.de

Once the kernel boots up, modprobe rate_control 80211 and insmod
bcm43xx.ko works without errors. The relevant dmesg output 


80211: module license 'unspecified' taints kernel.
bcm43xx driver 0.0.1
PCI: Enabling device 0001:10:12.0 (0004 - 0006)
bcm43xx: Chip ID 0x4318, rev 0x2
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7
bcm43xx: Detected Radio:  ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
wlan0: Selected rate control algorithm 'simple'


However, the script sta_up.sh caused the kernel to crash (can someone
tell me what to dump from xmon. I am not sure what information in
there is relevant). I traced the crash to the following command in the
script sta_up.sh

ifconfig wlan0.11 up

Instead I tried

ifconfig wlan0 up and then proceeded with the remaining steps in
sta_up.sh manually and dmesg output shows...


sta0: using STA entry 0
sta0: MAC address 00:14:51:82:b1:3c
bcm43xx: PHY connected
bcm43xx: Radio turned on
bcm43xx: ASSERTION FAILED (radio_attenuation  10) at: 
/home/shreyas/src/bcm43xx-dscape-20060110/bcm43xx_phy.c:1257:bcm43xx_find_lopair()
bcm43xx: Chip initialized
bcm43xx: ASSERTION FAILED (0) at: 
/home/shreyas/src/bcm43xx-dscape-20060110/bcm43xx_main.c:2996:bcm43xx_gen_bssid()
bcm43xx: DMA initialized
bcm43xx: 80211 cores initialized
bcm43xx: Keys cleared
wlan0.11: Does not support passive scan, disabled
wlan0: no IPv6 routers present
bcm43xx: TODO: Incomplete code in bcm43xx_set_iwmode() at 
/home/shreyas/src/bcm43xx-dscape-20060110/bcm43xx_main.c:2540


However, wpa_supplicant doesn't connect and I get the following
message repeated indefinitely in dmesg

sta0: no IPv6 routers present
sta0: starting scan
sta0: scan completed
sta0: Initial auth_alg=0
sta0: authenticate with AP 00:0c:41:f3:56:eb
sta0: authenticate with AP 00:0c:41:f3:56:eb
sta0: authenticate with AP 00:0c:41:f3:56:eb
sta0: authentication with AP 00:0c:41:f3:56:eb timed out


iwconfig shows


wlan0 IEEE 802.11g  ESSID:off/any 
  Mode:Managed  Frequency:2.462 GHz 
  RTS thr:off   Fragment thr=2346 B   
 
wlan0.11  IEEE 802.11g  ESSID:off/any  Nickname:Broadcom 4318
  Mode:Managed  Frequency:2.462 GHz 
  RTS thr:off   Fragment thr=2346 B   
 
sta0  IEEE 802.11g  ESSID:off/any 
  Mode:Managed  Frequency:2.462 GHz  Access Point: 00:0C:41:F3:56:EB   
  RTS thr:off   Fragment thr=2346 B   


and ifconfig shows


sta0  Link encap:Ethernet  HWaddr 00:14:51:82:B1:3C 
  inet addr:192.168.1.5  Bcast:192.168.1.255  Mask:255.255.255.0
  inet6 addr: fe80::214:51ff:fe82:b13c/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 b)  TX bytes:576 (576.0 b)

wlan0 Link encap:Ethernet  HWaddr 00:14:51:82:B1:3C 
  inet6 addr: fe80::214:51ff:fe82:b13c/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0


I have to use WEP and I don't have any open routers or WPA routers to
test these options. The router is a Linksys WRT54G model. So my
questions are...

1. Any suggestions on how I can avoid the kernel panic when I do
ifconfig wlan0.11 up? What