On 19/05/07, Pavel Cahyna <pavel@netbsd.org> wrote:
> On Sat, May 19, 2007 at 09:16:22AM +0100, Chavdar Ivanov wrote:
> > On 19/05/07, Pavel Cahyna <pavel@netbsd.org> wrote:
> > >On Sat, May 19, 2007 at 01:56:09AM +0200, fgh salle wrote:
> > >> after install and reboot on GENERIC_LAPTOP, no problems occured and
> > >> nothing to do to boot
> > >> thanks everybody
> > >
> > >what happens if you use GENERIC instead
> >
> > I use GENERIC.MP after each upgrade (before compiling my local kernel
> > - which is GENERIC.MP with some tweaks and drm enabled), so I'd guess
> > there is no problem. The panic is only with INSTALL_LARGE.
>
> Could you try to rebuild the INSTALL_LARGE kernel with the following
> lines added:
>
> # CardBus bridge support
> cbb*            at pci? dev ? function ?
> cardslot*       at cbb?
>
> # CardBus bus support
> cardbus*        at cardslot?
> pcmcia*         at cardslot?
>
> and see if it stil panics?

It doesn't panic any more. Now I get:

...
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
Kernelized RAIDframe activated
md0: internal 5000 KB image area
atapibus0 at atabus0: 2 targets
cd0 at atapibus0 drive 0: <MATSHITADVD-RAM UJ-840S, , 1.11> cdrom removable
cd0: 32-bit data port
cd0: drive supports PIO mode 4, DMA mode 2
cd0(piixide0:0:0): using PIO mode 4, DMA mode 2 (using DMA)
ahcisata0 port 0: device present, speed: 1.5Gb/s
wd0 at atabus1 drive 0: <FUJITSU MHV2060BH>
wd0: drive supports 16-sector PIO transfers, LBA48 addressing
wd0: 57241 MB, 116301 cyl, 16 head, 63 sec, 512 bytes/sect x 117231408 sectors
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
wd0(ahcisata0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5
(Ultra/100) (using DMA)
boot device: wd0
root on md0a dumps on md0b
no file system for md0 (dev 0x1100)
cannot mount root, error = 79
root device (default md0a): wd0a
dump device (default wd0b):
file system (default generic):
root on wd0a dumps on wd0b
root file system type: ffs
init path (default /sbin/init):
init: trying /sbin/init
...

(I've selected boot from wd0 to take the dmesg; I don't know if this
is actually supposed to happen when INSTALL kernel is booted from the
hard drive).

>
> Pavel
>

Chavdar