Arne Chr. Jorgensen wrote: > hi, > hmm... not sure I understood. The kernel was built by "make > clone_config", > from the previous kernel source to the new. The later kernel releases > fails to > access the hardware, in this case I can only narrow it down to "sata_nv". > No Suse or Fedora will run on this for later releases.. > > ( did enter some debug option into the scsi, but without any media to > dump it > to, I haven't found a way to get those finer details documented. ) > > So, who should I contact in order to figure this out ? Have heard of > bugzilla, > and such, but I don't know how to report such things. > > > //ARNE > ( sorry to bother you with this .. but I sure would like to be able to > enable the > bcm43xx stuff I did notice ) > > Here is the results with a Fedora install iso - x86_64 : > > - the following is what I have copied manually from screen: > . > . > ata4: SATA link down (SStatus 0 SControl 300) <====Note !!! > pata_amd 0000:00:06.0: version 0.3.8 > PCI: Setting latency timer of device 0000:00:06.0 to 64 > scsi4: pata_amd > scsi5: pata_amd > ata5: PATA max UDMA/133 cmd 0x00000000000101f0 ctl 0x00000000000103f6 > bmdma 0x00000000000130c0 irq 14 > ata6: PATA max UDMA/133 cmd 0x0000000000010170 ctl 0x0000000000010376 > bmdma 0x00000000000130c8 irq 15 > ata5.00: ATAPI: MATSHITADVD-RAM UJ-851S, 1.50, max MWDMA2 > ata5.00: ATAPI: configured for MWDMA2 > ata6: port disabled. ignoring. > scsi 4:0:0:0: CD-ROM MATSHITADVD-RAM UJ-851S, 1.50 PQ: 0 ANSI: 5 > device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: > [EMAIL PROTECTED] > Reading all physical volumes. This may take a while... > No volume groups found > Volume group "VolGroup00" not found > Unable to access resume device (/dev/VolGroup00/LogVol01) > mount: could not find filesystem '/dev/root' > setuproot: moving /dev failed: No such file or directory > Setuproot: error mounting /proc: No such file or directory > Setuproot: error mounting /sys: No such file or directory > switchroot: mount failed: No such file or directory > Kernel panic - not syncing: Attempting to kill init!
Do you have _ANY_ kernel that can boot and access the hard drive? If so, please boot it and send the output of 'lsmod'. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
