On Thu, 2003-09-04 at 02:22, H.J.Bathoorn wrote: > On Wednesday 03 September 2003 10:11, James Sparenberg wrote: > > One thing to note is that they mention a point about removing // on line > > 128 to correct a compile error. (just in case) > > > > James > > Noted that...haven't made a home brewed yet. > FWIW I loaded the Suse module directly using "insmod -f ~ rtl8180_24x.o" (as > it's actually compiled for a different kernel version it wont load without > '-f' option) but then it loads with a few comments about -f option and > tainted modules:o) > > /var/log/syslog gives the following output of the occasion which doesn't look > too bad by itself. > > ............... > Sep 4 10:34:05 localhost kernel: > Sep 4 10:34:05 localhost kernel: > Sep 4 10:34:05 localhost kernel: ******** RTL8180 Wireless Lan Driver Version > 1.1 <2003-05-22> loaded******** > Sep 4 10:34:05 localhost kernel: PCI: Setting latency timer of device 01:00.0 > to 64 > Sep 4 10:34:05 localhost kernel: RTL8180: 01:00.0: region #0 IS a PIO > resource! > Sep 4 10:34:05 localhost kernel: RTL8180: > request_region(0x00004000,0x00000100) ! > Sep 4 10:34:05 localhost kernel: RTL8180: STA is NOT acting as AP! > Sep 4 10:34:05 localhost kernel: RTL8180: LITTLE_ENDIAN memory access > Sep 4 10:34:05 localhost kernel: RTL8180: station mode eeprom info > Sep 4 10:34:05 localhost kernel: RTL8180: EEpromAddressSize = 8! > Sep 4 10:34:05 localhost kernel: RTL8180: eepromID = 0x8129 > Sep 4 10:34:05 localhost kernel: RTL8180: EEPROMVersion = 0x0102 > Sep 4 10:34:05 localhost kernel: RTL8180: Tx Power Level, channel 0 = 0xa0 > Sep 4 10:34:05 localhost kernel: RTL8180: Tx Power Level, channel 1 = 0xb0 > Sep 4 10:34:05 localhost kernel: RTL8180: Tx Power Level, channel 2 = 0xb0 > Sep 4 10:34:05 localhost kernel: RTL8180: Tx Power Level, channel 3 = 0xc0 > Sep 4 10:34:05 localhost kernel: RTL8180: Tx Power Level, channel 4 = 0xc0 > Sep 4 10:34:05 localhost kernel: RTL8180: Tx Power Level, channel 5 = 0xd0 > Sep 4 10:34:05 localhost kernel: RTL8180: Tx Power Level, channel 6 = 0xd0 > Sep 4 10:34:05 localhost kernel: RTL8180: Tx Power Level, channel 7 = 0xc0 > Sep 4 10:34:05 localhost kernel: RTL8180: Tx Power Level, channel 8 = 0xc0 > Sep 4 10:34:05 localhost kernel: RTL8180: Tx Power Level, channel 9 = 0xc0 > Sep 4 10:34:05 localhost kernel: RTL8180: Tx Power Level, channel 10 = 0xb0 > Sep 4 10:34:05 localhost kernel: RTL8180: Tx Power Level, channel 11 = 0xb0 > Sep 4 10:34:05 localhost kernel: RTL8180: Tx Power Level, channel 12 = 0xa0 > Sep 4 10:34:05 localhost kernel: RTL8180: Tx Power Level, channel 13 = 0xa0 > Sep 4 10:34:05 localhost kernel: RTL8180: ChannelPlan = 0x0002 > Sep 4 10:34:05 localhost kernel: RTL8180: RFChipID = 0x0003 > Sep 4 10:34:05 localhost kernel: RTL8180: EEPROMVersion > 0x0101 > Sep 4 10:34:05 localhost kernel: RTL8180: AntennaDiversity = TRUE > Sep 4 10:34:05 localhost kernel: RTL8180: CSThreshold = 0x000b > Sep 4 10:34:05 localhost kernel: RTL8180: DigitalPhy = FALSE > Sep 4 10:34:05 localhost kernel: RTL8180: DefaultAntennaB = FALSE > Sep 4 10:34:05 localhost kernel: RTL8180: CSMethod = RCR_EnCS1 > Sep 4 10:34:05 localhost kernel: RTL8180: wlan driver loaded. ioaddr=0x4000, > irq=9, MAC_addr=0:50:fc:d0:55:3e > Sep 4 10:34:05 localhost /etc/hotplug/net.agent: register event not handled > ............... > Alas the last line is followed by a kernel panic and lock-up of the machine > forcing a hard reboot. > Any clues why? It all looks pretty OK to me. > > There was quite a bit of screen output during the lock-up.....any idea if this > is saved somewhere? I can't seem to find anything even vaguely related, like > core dumps.
If the card was inserted when you loaded the module this could be the explination. It would do that on mine until I stumbled (yes stumbled) upon a set of lines in my /etc/pcmcia/config file that actually were correct for my card. IF however it did this and the card isn't inserted. Then it's time to roll your own on the module. James >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
