Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Setting monitor mode for airport using kernel 2.6
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC
View previous topic :: View next topic  
Author Message
Hydraulix
Guru
Guru


Joined: 12 Dec 2003
Posts: 447
Location: Baltimore, Maryland

PostPosted: Fri Mar 19, 2004 5:47 am    Post subject: Setting monitor mode for airport using kernel 2.6 Reply with quote

Ok I've searched the whole board and then googled the hell out of this problem. And I've tried everything and nothing works. All I am trying to do is enable monitor/scanning mode for my G3 500mhz iBook with the Airport card. The patches that I tried seems to not work. If anyone can help me I would be most thankful.



:)
_________________
It is the fate of operating systems to become free.
- Neal Stephenson

If only You and Dead people can read hex, how many people can read hex?
Back to top
View user's profile Send private message
gen2
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jan 2003
Posts: 82
Location: West Coast, USA

PostPosted: Sat Mar 20, 2004 5:43 pm    Post subject: Re: Setting monitor mode for airport using kernel 2.6 Reply with quote

Hydraulix wrote:
Ok I've searched the whole board and then googled the hell out of this problem. And I've tried everything and nothing works. All I am trying to do is enable monitor/scanning mode for my G3 500mhz iBook with the Airport card. The patches that I tried seems to not work. If anyone can help me I would be most thankful.
:)


Same problem here.
IIRC, there has been an odd sequence of the monitor mode patch being included and excluded from various ppc-sources kernels since 2.4.20 or so. Personally I've had a heck of a time keeping kismet working thru kernel upgrades, eventually gave up. Anyone with solid info on this would be appreciated !
Back to top
View user's profile Send private message
Hydraulix
Guru
Guru


Joined: 12 Dec 2003
Posts: 447
Location: Baltimore, Maryland

PostPosted: Sat Mar 20, 2004 6:39 pm    Post subject: Reply with quote

Glad I'm not the only one with this problem. I wonder why the monitor patches are not included with the kernel in the first place? It really would make this easier. If anyone has this working with the 2.6 kernel drop a line. :D
_________________
It is the fate of operating systems to become free.
- Neal Stephenson

If only You and Dead people can read hex, how many people can read hex?
Back to top
View user's profile Send private message
Relentless
n00b
n00b


Joined: 09 Mar 2004
Posts: 6

PostPosted: Sun Mar 21, 2004 9:43 am    Post subject: You can count me in too... Reply with quote

I've been trying to get this to work for a week on my g3 ibook.....
I have all but given up
:(
_________________
Jason Remley
Back to top
View user's profile Send private message
ozonator
Guru
Guru


Joined: 11 Jun 2003
Posts: 591
Location: Ontario, Canada

PostPosted: Mon Mar 22, 2004 2:07 pm    Post subject: Reply with quote

Here's what works for me (with 2.6.x) for enabling monitor mode -- i.e., enough to run airsnort, kismet, etc.

1. Get the appropriate patch for the driver included with your kernel, from this page. With 2.6.3, that's orinoco-0.13e-patch.diff; earlier kernels may include earlier versions of the orinoco driver (2.6.2 uses 0.13d, for example), so it's worth checking: see the first line of <kernel sources>/drivers/net/wireless/orinoco.c.

2. Patch the driver:

Code:
cd <kernel sources>/drivers/net/wireless/orinoco.c
patch < /path/to/orinoco-0.13e-patch.diff


<kernel sources>, of course, is typically /usr/src/linux; '/path/to' is wherever you saved the appropriate patch in step 1 (which might not be 0.13e, so adjust accordingly).

3. If this is a fresh kernel for you, compile and install the kernel as usual (I'm assuming your config has the appropriate airport support enabled!), and reboot, loading the airport module. If you're already running an identical kernel version, re-compile and install the modules: 'make clean && make modules_install' in /usr/src/linux; then, unload and reload the airport module.

4. Check for monitor mode on the airport interface, e.g., 'iwpriv eth1' -- if all is well, there will be a line that indicates 'monitor'. Then, enjoy!

This process has worked perfectly for me for several kernel versions, starting in late 2.4.x, and newer versions of the orinoco patch include the 'channel hopping' patch described here, so it's not necessary to add that patch separately. It's also simpler (and more up-to-date with patch versions) than the process described in this thread, but that forum describes applying monitor and scanning patches; monitor is enough for me, at least for now, since it allows me to run kismet, airsnort, etc., and I don't mind doing it separately from other network activity (the difference between scanning and monitor is summarized at the beginning of the thread about enabling both).
Back to top
View user's profile Send private message
Hydraulix
Guru
Guru


Joined: 12 Dec 2003
Posts: 447
Location: Baltimore, Maryland

PostPosted: Tue Mar 30, 2004 4:23 am    Post subject: Reply with quote

Wow thanks a lot. That helped me a ton.



What patch would I use for my other system that's running 2.6.1? It's still a iBook.
_________________
It is the fate of operating systems to become free.
- Neal Stephenson

If only You and Dead people can read hex, how many people can read hex?
Back to top
View user's profile Send private message
ozonator
Guru
Guru


Joined: 11 Jun 2003
Posts: 591
Location: Ontario, Canada

PostPosted: Tue Mar 30, 2004 1:22 pm    Post subject: Reply with quote

Hydraulix wrote:
What patch would I use for my other system that's running 2.6.1? It's still a iBook.


Run this command to see what version of the patch you need:

Code:
head -1 /usr/src/linux/drivers/net/wireless/orinoco.c


I haven't got 2.6.1 sources handy for checking, but the version of the driver you have is indicated on the first line of that file (which will be displayed by that command). It will be either 0.13d (patch) or 0.13e (patch).

An update since my earlier post: I've had the chance to try the plain 0.13e patch with 2.6.4 on my iBook (compiled from development-sources, not ppc-development-sources), and so far have had no problems with either the kernel or the patched airport/orinoco driver.
Back to top
View user's profile Send private message
[aton]
n00b
n00b


Joined: 31 Mar 2004
Posts: 4
Location: old europe

PostPosted: Fri Apr 02, 2004 9:00 pm    Post subject: Reply with quote

works perfectly on my sony vaio with an acer wlan card. cu, i need to go to town :)
Back to top
View user's profile Send private message
Hydraulix
Guru
Guru


Joined: 12 Dec 2003
Posts: 447
Location: Baltimore, Maryland

PostPosted: Mon Apr 05, 2004 2:06 pm    Post subject: Reply with quote

Ok I installed kernel 2.6.4-pegasos and that patch you have in this thread. The montior function comes up BUT when I go to scan something my whole computer freezes. Not to mention Kismet can't connect to localhost. :cry:
_________________
It is the fate of operating systems to become free.
- Neal Stephenson

If only You and Dead people can read hex, how many people can read hex?
Back to top
View user's profile Send private message
ozonator
Guru
Guru


Joined: 11 Jun 2003
Posts: 591
Location: Ontario, Canada

PostPosted: Mon Apr 05, 2004 2:40 pm    Post subject: Reply with quote

Hydraulix wrote:
Ok I installed kernel 2.6.4-pegasos and that patch you have in this thread. The montior function comes up BUT when I go to scan something my whole computer freezes. Not to mention Kismet can't connect to localhost. :cry:


Did you check the kismet config, and start /etc/init.d/kismet (i.e., /etc/init.d/kismet start) before trying to run kismet? If not, that might explain the inability to connect to localhost. Don't know if that could explain a freeze, too, but it might.
Back to top
View user's profile Send private message
Hydraulix
Guru
Guru


Joined: 12 Dec 2003
Posts: 447
Location: Baltimore, Maryland

PostPosted: Mon Apr 05, 2004 4:50 pm    Post subject: Reply with quote

ozonator wrote:
Hydraulix wrote:
Ok I installed kernel 2.6.4-pegasos and that patch you have in this thread. The montior function comes up BUT when I go to scan something my whole computer freezes. Not to mention Kismet can't connect to localhost. :cry:


Did you check the kismet config, and start /etc/init.d/kismet (i.e., /etc/init.d/kismet start) before trying to run kismet? If not, that might explain the inability to connect to localhost. Don't know if that could explain a freeze, too, but it might.



I checked over everything and I believe I have it set up right. But as soon as I started the kismet server (/etc/inint.d/kismet) it happen again. My cpu maxed out at 100% and I had to reboot.

EDIT: I've upgraded to 2.6.5:)
Here's my kismet.conf





Code:
# Kismet config file
# Most of the "static" configs have been moved to here -- the command line
# config was getting way too crowded and cryptic.  We want functionality,
# not continually reading --help!

# Version of Kismet config
version=3.0.1c

# Name of server (Purely for organiational purposes)
servername=Kismet

# User to setid to (should be your normal user)
suiduser=hydraulix

# Packet sources:
# source=capture_cardtype,capture_interface,capture_name
# Card type - Specifies the type of device. It can be one of:
#     cisco         - Cisco card with Linux Kernel drivers
#     cisco_cvs     - Cisco card with CVS Linux drivers
#     cisco_bsd     - Cisco on *BSD
#     prism2        - Prism2 using wlan-ng drivers with pcap support (all
#                      current versions support pcap)
#     prism2_hostap - Prism2 using hostap drivers
#     prism2_legacy - Prism2 using wlan-ng drivers without pcap support (0.1.9)
#     prism2_bsd    - Prism2 on *BSD
#     orinoco       - Orinoco cards using Snax's patched driers
#     generic       - Generic card with no specific support.  You will have
#                      to put this into monitor mode yourself!
#     wsp100        - WSP100 embedded remote sensor. 
#     wtapfile      - Saved file of packets readable by libwiretap
#     pcapfile      - Saved file of packets readable by libpcap
#     ar5k          - ar5k 802.11a using the vt_ar5k drivers
#     drone         - Kismet remote drone
#     viha          - Mac OSX Airport drivers
# Capture interface - Specifies the network interface Kismet will watch for
#  packets to come in on.  Typically "ethX" or "wlanX".  For the WSP100 capture
#  engine, the WSP100 device sends packets via a UDP stream, so the capture
#  interface should be in the form of host:port where 'host' is the WSP100 and
#  'port' is the local UDP port that it will send data to. 
#  Kismet remote drones function similarly and the interface should be the
#  host:port of the drone.
#  CVS Cisco drivers split the interface into 2 components, ethX and wifiX.
#  They may not be the same, so for cisco_cvs the card type specifies
#  ethX:wifiX
# Capture Name      - The name Kismet uses for this capture source.  This is the
#   name used to specify what sources to enable.
#
# To enable multiple sources, specify a source line for each and then use the
# enablesources line to enable them.  For example:
# source=prism2,wlan0,prism
# source=cisco,eth0,cisco
# source=cisco_cvs,eth1:wifi0,ciscocvs

source=orinoco,eth1,orinocosource
# Other common source configs:
# source=prism2,wlan0,prism2source
# source=prism2_avs,wlan0,newprism2source
# source=orinoco,eth0,orinocosource

# Comma-separated list of sources to enable.  This is only needed if you wish
# to selectively enable multiple sources.
# For example:
# enablesources=prismsource,ciscosource

# Do we channelhop?
channelhop=true

# How many channels per second do we hop?  (1-10)
channelvelocity=5

# Do we split channels between cards on the same spectrum?  This means if
# multiple 802.11b capture sources are defined, they will be offset to cover
# the most possible spectrum at a given time.  This also controls splitting
# fine-tuned sourcechannels lines which cover multiple interfaces (see below)
splitchannels=true

# Basic channel hopping control:
# These define the channels the cards hop through for various frequency ranges
# supported by Kismet.   More finegrain control is available via the
# "sourcechannels" configuration option, but these lists are used for basic
# channel hopping.
80211bchannels=1,6,11,2,7,3,8,4,9,5,10
# Alternately, users outside of the US or with firmware which supports the
# full range of possible channels will probably want the extended channel
# list:
# 80211bchannels=1,7,13,2,8,3,14,9,4,10,5,11,6,12
80211achannels=36,40,44,48,52,56,60,64
# Depending on your card and drivers, this is a list of every 802.11a channel.
# Most won't support all of these, so you'll have to tweak it to what your
# system supports.
# 80211achannels=36,40,44,48,52,56,60,64,100,104,108,112,116,120,124,128,132,136,140,149,153,157,161,184,188,192,196,200,204,208,212,216

# Fine-tuning channel hopping control:
# The sourcechannels option can be used to set the channel hopping for
# specific interfaces, and to control what interfaces share a list of
# channels for split hopping.  This can also be used to easily lock
# one card on a single channel while hopping with other cards.
# Any card without a sourcechannel definition will use the standard hopping
# list.
# sourcechannels=sourcename[,sourcename]:ch1,ch2,ch3,...chN

# ie, for us channels on the source 'prism2source' (same as normal channel
# hopping behavior):
# sourcechannels=prism2source:1,6,11,2,7,3,8,4,9,5,10

# Given two capture sources, "prism2a" and "prism2b", we want prism2a to stay
# on channel 6 and prism2b to hop normally.  By not setting a sourcechannels
# line for prism2b, it will use the standard hopping.
# sourcechannels=prism2a:6

# To assign the same custom hop channel to multiple sources, or to split the
# same custom hop channel over two sources (if splitchannels is true), list
# them all on the same sourcechannels line:
# sourcechannels=prism2a,prism2b,prism2c:1,6,11

# Port to serve GUI data
tcpport=2501
# People allowed to connect, comma seperated IP addresses or network/mask
# blocks.  Netmasks can be expressed as dotted quad (/255.255.255.0) or as
# numbers (/24)
allowedhosts=127.0.0.1
# Maximum number of concurrent GUI's
maxclients=5

# Do we have a GPS?
gps=true
# Host:port that GPSD is running on.  This can be localhost OR remote!
gpshost=localhost:2947
# Do we lock the mode?  This overrides coordinates of lock "0", which will
# generate some bad information until you get a GPS lock, but it will
# fix problems with GPS units with broken NMEA that report lock 0
gpsmodelock=false

# Packet filtering options:
# filter_tracker - Packets filtered from the tracker are not processed or
#                  recorded in any way.
# filter_dump    - Packets filtered at the dump level are tracked, displayed,
#                  and written to the csv/xml/network/etc files, but not
#                  recorded in the packet dump
# filter_export  - Controls what packets influence the exported CSV, network,
#                  xml, gps, etc files.
# All filtering options take arguments containing the type of address and
# addresses to be filtered.  Valid address types are 'ANY', 'BSSID',
# 'SOURCE', and 'DEST'.  Filtering can be inverted by the use of '!' before
# the address.  For example,
# filter_tracker=ANY(!00:00:DE:AD:BE:EF)
# has the same effect as the previous mac_filter config file option.
# filter_tracker=...
# filter_dump=...
# filter_export=...

# Alerts to be reported and the throttling rates.
# alert=name,throttle/unit,burst
# The throttle/unit describes the number of alerts of this type that are
# sent per time unit.  Valid time units are second, minute, hour, and day.
# Burst describes the number of alerts sent before throttling takes place.
# For example:
# alert=FOO,10/min,5
# Would allow 5 alerts through before throttling is enabled, and will then
# limit the number of alerts to 10 per minute.
# A throttle rate of 0 disables throttling of the alert.
# See the README for a list of alert types.
alert=NETSTUMBLER,5/min,2
alert=WELLENREITER,5/min,2
alert=LUCENTTEST,5/min,2
alert=DEAUTHFLOOD,5/min,4
alert=BCASTDISCON,5/min,4
alert=CHANCHANGE,5/min,4
alert=AIRJACKSSID,5/min,2
alert=PROBENOJOIN,5/min,2
alert=DISASSOCTRAFFIC,5/min,2
alert=NULLPROBERESP,5/min,5

# Known WEP keys to decrypt, bssid,hexkey.  This is only for networks where
# the keys are already known, and it may impact throughput on slower hardware.
# Multiple wepkey lines may be used for multiple BSSIDs.
# wepkey=00:DE:AD:C0:DE:00,FEEDFACEDEADBEEF01020304050607080900

# Is transmission of the keys to the client allowed?  This may be a security
# risk for some.  If you disable this, you will not be able to query keys from
# a client.
allowkeytransmit=true

# How often (in seconds) do we write all our data files (0 to disable)
writeinterval=300

# Do we use sound?
# Not to be confused with GUI sound parameter, this controls wether or not the
# server itself will play sound.  Primarily for headless or automated systems.
sound=false
# Path to sound player
soundplay=/usr/bin/play
# Optional parameters to pass to the player
# soundopts=--volume=.3
# New network found
sound_new=/usr/share/kismet/wav/new_network.wav
# Network traffic sound
sound_traffic=/usr/share/kismet/wav/traffic.wav
# Network junk traffic found
sound_junktraffic=/usr/share/kismet/wav/junk_traffic.wav
# GPS lock aquired sound
# sound_gpslock=/usr/share/kismet/wav/foo.wav
# GPS lock lost sound
# sound_gpslost=/usr/share/kismet/wav/bar.wav
# Alert sound
sound_alert=/usr/share/kismet/wav/alert.wav

# Does the server have speech? (Again, not to be confused with the GUI's speech)
speech=false
# Server's path to Festival
festival=/usr/bin/festival
# How do we speak?  Valid options:
# speech    Normal speech
# nato      NATO spellings (alpha, bravo, charlie)
# spell     Spell the letters out (aye, bee, sea)
speech_type=nato
# speech_encrypted and speech_unencrypted - Speech templates
# Similar to the logtemplate option, this lets you customize the speech output.
# speech_encrypted is used for an encrypted network spoken string
# speech_unencrypted is used for an unencrypted network spoken string
#
# %b is replaced by the BSSID (MAC) of the network
# %s is replaced by the SSID (name) of the network
# %c is replaced by the CHANNEL of the network
# %r is replaced by the MAX RATE of the network
speech_encrypted=New network detected, s.s.i.d. %s, channel %c, network encrypted.
speech_unencrypted=New network detected, s.s.i.d. %s, channel %c, network open.

# Where do we get our manufacturer fingerprints from?  Assumed to be in the
# default config directory if an absolute path is not given.
ap_manuf=/etc/kismet/ap_manuf
client_manuf=/etc/kismet/client_manuf

# Use metric measurements in the output?
metric=false

# Do we write waypoints for gpsdrive to load?  Note:  This is NOT related to
# recent versions of GPSDrive's native support of Kismet.
waypoints=false
# GPSMap waypoint file.  This WILL be truncated.
waypointdata=%h/.gpsdrive/way_kismet.txt

# How many alerts do we backlog for new clients?  Only change this if you have
# a -very- low memory system and need those extra bytes, or if you have a high
# memory system and a huge number of alert conditions.
alertbacklog=50

# File types to log, comma seperated
# dump    - raw packet dump
# network - plaintext detected networks
# csv     - plaintext detected networks in CSV format
# xml     - XML formatted network and cisco log
# weak    - weak packets (in airsnort format)
# cisco   - cisco equipment CDP broadcasts
# gps     - gps coordinates
logtypes=dump,network,csv,xml,weak,cisco,gps

# Do we log "noise" packets that we can't decipher?  I tend to not, since
# they don't have anything interesting at all in them.
noiselog=false

# Do we log corrupt packets?  Corrupt packets have enough header information
# to see what they are, but someting is wrong with them that prevents us from
# completely dissecting them.  Logging these is usually not a bad idea.
corruptlog=true

# Do we log beacon packets or do we filter them out of the dumpfile
beaconlog=true

# Do we log PHY layer packets or do we filter them out of the dumpfile
phylog=true

# Do we mangle packets if we can decrypt them or if they're fuzzy-detected
mangledatalog=true

# Do we do "fuzzy" crypt detection?  (byte-based detection instead of 802.11
# frame headers)
# valid option: Comma seperated list of card types to perform fuzzy detection
#  on, or 'all'
fuzzycrypt=prism2_legacy,wtapfile

# What type of dump do we generate?
# valid option: "wiretap"
dumptype=wiretap
# Do we limit the size of dump logs?  Sometimes ethereal can't handle big ones.
# 0 = No limit
# Anything else = Max number of packets to log to a single file before closing
# and opening a new one.
dumplimit=0

# Do we write data packets to a FIFO for an external data-IDS (such as Snort)?
# See the docs before enabling this.
#fifo=/tmp/kismet_dump

# Default log title
logdefault=Kismet

# logtemplate - Filename logging template.
# This is, at first glance, really nasty and ugly, but you'll hardly ever
# have to touch it so don't complain too much.
#
# %n is replaced by the logging instance name
# %d is replaced by the current date
# %t is replaced by the starting log time
# %i is replaced by the increment log in the case of multiple logs
# %l is replaced by the log type (dump, status, crypt, etc)
# %h is replaced by the home directory
# ie, "netlogs/%n-%d-%i.dump" called with a logging name of "Pok" could expand
# to something like "netlogs/Pok-Dec-20-01-1.dump" for the first instance and
# "netlogs/Pok-Dec-20-01-2.%l" for the second logfile generated.
# %h/netlots/%n-%d-%i.dump could expand to
# /home/foo/netlogs/Pok-Dec-20-01-2.dump
#
# Other possibilities:  Sorting by directory
# logtemplate=%l/%n-%d-%i
# Would expand to, for example,
# dump/Pok-Dec-20-01-1
# crypt/Pok-Dec-20-01-1
# and so on.  The "dump", "crypt", etc, dirs must exist before kismet is run
# in this case.
logtemplate=%n-%d-%i.%l

# Where state info, etc, is stored.  You shouldnt ever need to change this.
# This is a directory.
configdir=%h/.kismet/

# cloaked SSID file.  You shouldn't ever need to change this.
ssidmap=ssid_map

# Group map file.  You shouldn't ever need to change this.
groupmap=group_map

# IP range map file.  You shouldn't ever need to change this.
ipmap=ip_map


_________________
It is the fate of operating systems to become free.
- Neal Stephenson

If only You and Dead people can read hex, how many people can read hex?
Back to top
View user's profile Send private message
ozonator
Guru
Guru


Joined: 11 Jun 2003
Posts: 591
Location: Ontario, Canada

PostPosted: Wed Apr 07, 2004 1:11 pm    Post subject: Reply with quote

Hmmm. When you try to run kismet, is the airport interface (eth1) also running otherwise? In other words, is eth1 up, with a normal network connection? It makes sense to me that kismet might be fighting with other code that's holding on to eth1 for normal networking.

Kismet works for me, but I normally make sure eth1 isn't up before I run kismet (i.e., /etc/init.d/net.eth1 stop before /etc/init.d/kismet start), and likewise I stop kismet altogether before bringing eth1 up again. Another thought: unloading and reloading the airport module before/after running kismet may also help.
Back to top
View user's profile Send private message
Hydraulix
Guru
Guru


Joined: 12 Dec 2003
Posts: 447
Location: Baltimore, Maryland

PostPosted: Fri Apr 09, 2004 2:27 pm    Post subject: Reply with quote

I'll give that a shot and post up the responce.


Thanks. :)
_________________
It is the fate of operating systems to become free.
- Neal Stephenson

If only You and Dead people can read hex, how many people can read hex?
Back to top
View user's profile Send private message
Hydraulix
Guru
Guru


Joined: 12 Dec 2003
Posts: 447
Location: Baltimore, Maryland

PostPosted: Mon Jun 07, 2004 10:13 am    Post subject: Reply with quote

Ok I'm back.

My computer still drags when I run
Code:
 iwpriv eth0 monitor 2 1



Here's my last log

Code:
Jun  6 10:57:59 [kernel] IN from bad port 64 at c022fc94
Jun  6 10:57:59 [kernel] IN from bad port 64 at c022fc94
Jun  6 10:58:02 [kernel] eth1: New link status: Connected (0001)
Jun  6 03:49:29 [kernel] device eth1 entered promiscuous mode
Jun  6 03:51:06 [kernel] device eth1 left promiscuous mode
Jun  6 14:44:07 [kernel] IN from bad port 64 at c02195bc
Jun  6 14:44:07 [kernel] IN from bad port 64 at c02195bc
Jun  6 14:44:10 [kernel] eth1: New link status: Connected (0001)
Jun  6 14:49:05 [kernel] snd_powermac: falsely claims to have parameter enable
Jun  6 14:49:06 [kernel] snd_powermac: falsely claims to have parameter enable
Jun  6 17:01:23 [kernel] IN from bad port 64 at c0243a90
Jun  6 17:01:23 [kernel] IN from bad port 64 at c0243a90
Jun  6 17:01:26 [kernel] eth1: New link status: Connected (0001)
Jun  6 23:08:48 [kernel] device eth1 entered promiscuous mode
Jun  6 23:08:48 [kernel] device eth1 left promiscuous mode
Jun  6 23:09:24 [kernel] device eth1 entered promiscuous mode
Jun  6 23:09:25 [kernel] device eth1 left promiscuous mode
Jun  6 23:11:15 [kernel] hda: Set PIO timing for mode 0, reg: 0x1090032b
Jun  6 23:11:16 [kernel] hda: Set PIO timing for mode 0, reg: 0x1090032b
Jun  7 00:06:04 [kernel] IN from bad port 64 at c022bb08
Jun  7 00:06:04 [kernel] IN from bad port 64 at c022bb08
                - Last output repeated 292 times -
Jun  7 00:06:04 [kernel] i8042.c: i8042 controller self test timeout.
Jun  7 00:06:04 [kernel] NET: Registered protocol family 2
Jun  7 00:10:58 [kernel] orinoco.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
Jun  7 00:10:58 [kernel] airport.c 0.13e (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
Jun  7 00:10:58 [kernel] Airport at physical address 80030000
Jun  7 00:10:59 [kernel] eth0: Station identity 001f:0001:0008:0046
Jun  7 00:10:59 [kernel] eth0: Looks like a Lucent/Agere firmware version 8.70
Jun  7 00:10:59 [kernel] eth0: Ad-hoc demo mode supported
Jun  7 00:10:59 [kernel] eth0: IEEE standard IBSS ad-hoc mode supported
Jun  7 00:10:59 [kernel] eth0: MAC address 00:30:65:01:48:31
Jun  7 00:10:59 [kernel] eth0: Station name "HERMES I"
Jun  7 00:10:59 [kernel] eth0: ready
Jun  7 00:11:00 [kernel] airport: card registered for interface eth0



I'll try to post some more info if I can find it. I had to hard reboot and I think I'm missing some files. :(
_________________
It is the fate of operating systems to become free.
- Neal Stephenson

If only You and Dead people can read hex, how many people can read hex?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum