Bug 113609

PLease show me 'hwinfo --netcard'

Created attachment 47946 [details]
How to debug system initialisation

Created attachment 47947 [details]
the script

Please check the pci events.

Hi,

hwinfo --netcard:
----------------------------------------------------------------------------
07: PCI 11012.0: 0280 Network controller
  [Created at pci.277]
  UDI: /org/freedesktop/Hal/devices/pci_14e4_4320
  Unique ID: 8FIi.j5xvbQ0_wg1
  SysFS ID: /devices/pci0001:10/0001:10:12.0
  SysFS BusID: 0001:10:12.0
  Hardware Class: network
  Model: "Apple BCM4306 802.11b/g Wireless LAN Controller"
  Vendor: pci 0x14e4 "Broadcom"
  Device: pci 0x4320 "BCM4306 802.11b/g Wireless LAN Controller"
  SubVendor: pci 0x106b "Apple Computer Inc."
  SubDevice: pci 0x004e 
  Revision: 0x03
  PROM id: pci@f2000000/pci80211@12
  Memory Range: 0xa0006000-0xa0007fff (rw,non-prefetchable,disabled)
  IRQ: 52 (no events)
  Module Alias: "pci:v000014E4d00004320sv0000106Bsd0000004Ebc02sc80i00"
  Config Status: cfg=no, avail=yes, need=no, active=unknown

19: PCI 2240f.0: 0200 Ethernet controller
  [Created at pci.277]
  UDI: /org/freedesktop/Hal/devices/pci_106b_32
  Unique ID: pjnY.GbVqbtzqQZ5
  SysFS ID: /devices/pci0002:24/0002:24:0f.0
  SysFS BusID: 0002:24:0f.0
  Hardware Class: network
  Model: "Apple UniNorth 2 GMAC (Sun GEM)"
  Vendor: pci 0x106b "Apple Computer Inc."
  Device: pci 0x0032 "UniNorth 2 GMAC (Sun GEM)"
  Revision: 0xff
  Memory Range: 0xf5200000-0xf53fffff (rw,non-prefetchable)
  Memory Range: 0xf5100000-0xf51fffff (ro,prefetchable)
  IRQ: 41 (no events)
  Module Alias: "pci:v0000106Bd00000032sv00000000sd00000000bc02sc00i00"
  Driver Info #0:
    Driver Status: sungem is not active
    Driver Activation Cmd: "modprobe sungem"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
------------------------------------------------------------------------------

Excerpt from command show_event_log:

# ./show_event_log
event 0 not found

Please tell me if something in README.Logging is hard to understand. I will
improve it.

You have to call show_event_log this way
  show_event_log 1 100 pci
This checks all events from 1 until 100 and shows all ebents of type pci. Very
probably all pci events will be in this range. If you are unsure you can also
call it:
  show_event_log 1 last pci
But this will take some time.

Was it an update or fresh installation?

Please show me also
  cd /etc/sysconfig/hardware; grep . hwcfg*

Created attachment 48107 [details]
show_events_log output

Output from show_event_log 1 last pci

Hi again,

Yes indeed, i am sorry i totally omitted the show_event_log part in the README .....

It is a fresh installation, clean wiped my osX, so that makes SUSE ppc dominant
OS on this powerbook G4.

./show_events_pci 1 100 pci
'event 1 not found', and thus it continues till it loops to 100.

./show_events_pci 1 last pci
Look at attachement above.

grep line excerpt:

hwcfg-bus-pci-0002:24:0f.0:MODULE='sungem'
hwcfg-bus-pci-0002:24:0f.0:MODULE_OPTIONS=''
hwcfg-bus-pci-0002:24:0f.0:STARTMODE='auto'
hwcfg-static-1:# YaST configured sound card snd-card-0
hwcfg-static-1:# 5lYh.ITz6G5CcwPB:Integrated Sound (awacs)
hwcfg-static-1:MODULE='snd-powermac'
hwcfg-static-1:STARTMODE='auto'
hwcfg-static-printer:STARTMODE='auto'
hwcfg-static-printer:MODULE='lp'

The config looks ok.

Please try if
   hwup devpath-/devices/pci0002:24/0002:24:0f.0
loads the driver.

It seems you did not manage to get syslog started early enough (before
boot.udev). Please show me:
   grep -- -Start: /etc/init.d/{earlysyslog,boot.udev}
   ls /etc/init.d/boot.d/S0*

Do you use seperate partitons for /var, /tmp or /usr (or any other)?

Hi,

I've noticed that this bug isn't very common as i've seen another ppc box with
sungem network card working in perfect order.

I've used a pretty 'standard' custom partition scheme, namely: /, boot and swap

hwup devpath-/devices/pci0002:24/0002:24:0f.0 loads driver sucessfully.

grep -- -Start: /etc/init.d/{earlysyslog,boot.udev} outputs this:
/etc/init.d/earlysyslog:# Required-Start:
/etc/init.d/earlysyslog:# Default-Start:  5
/etc/init.d/boot.udev:# Required-Start: boot.rootfsck
/etc/init.d/boot.udev:# Default-Start:    B 2 3 5

ls /etc/init.d/boot.d/S0* outputs:
/etc/init.d/boot.d/S01boot.proc
/etc/init.d/boot.d/S02boot.shm
/etc/init.d/boot.d/S03boot.rootfsck
/etc/init.d/boot.d/S04boot.ibmsis
/etc/init.d/boot.d/S04boot.udev
/etc/init.d/boot.d/S05boot.coldplug
/etc/init.d/boot.d/S06boot.device-mapper
/etc/init.d/boot.d/S06boot.md
/etc/init.d/boot.d/S07boot.localfs
/etc/init.d/boot.d/S08boot.cleanup
/etc/init.d/boot.d/S08boot.clock
/etc/init.d/boot.d/S08boot.klog
/etc/init.d/boot.d/S08boot.loadmodules
/etc/init.d/boot.d/S08boot.scpm
/etc/init.d/boot.d/S09boot.crypto

> grep -- -Start: /etc/init.d/{earlysyslog,boot.udev} outputs this:
> /etc/init.d/earlysyslog:# Required-Start:

Add 'boot.rootfsck' here

> /etc/init.d/earlysyslog:# Default-Start:  5
> /etc/init.d/boot.udev:# Required-Start: boot.rootfsck

Add 'earlysyslog' here

> /etc/init.d/boot.udev:# Default-Start:    B 2 3 5

Then call 'insserv -d earlysyslog'. After that you should see a link
  /etc/init.d/boot.d/S04earlysyslog
and boot.udev and boot.coldplug and so on got higher numbers.

> ls /etc/init.d/boot.d/S0* outputs:
> /etc/init.d/boot.d/S01boot.proc
> /etc/init.d/boot.d/S02boot.shm
> /etc/init.d/boot.d/S03boot.rootfsck
> /etc/init.d/boot.d/S04boot.ibmsis

Here we need earlysyslog.

> /etc/init.d/boot.d/S04boot.udev
> /etc/init.d/boot.d/S05boot.coldplug

Then please once again, move your syslog file, reboot, use show_event_log ...

No further info to debug --> invalid

BTW: There are no other reports about such a problem.