Alan McKinnon <[EMAIL PROTECTED]> writes: > Something seems to have changed with 2.6.25, more so than normal for new > versions. For instance, b43 refuses point blank to work here or do > anything remotely useful like a nice driver should. b43legacy doesn't > work either. They both work with earlier versions although performance > sucks. I was hoping that this would be the version where I could dump > ndiswrapper. Maybe next time... > > Let us know how you get on with a custom config
I haven't gotten that far yet, since I decided to try adding intramfs lines to grub.conf and see if it would then work.... It didn't but then I'm not really sure what is supposed to go there where you want to boot off an initramfs. I tried these lines I found by googling at site:gentoo.org: (the part between the asterisks below) default 0 timeout 5 splashimage=(hd0,0)/grub/splash.xpm.gz title=kernel-2.6.25-r1-0x31a-1280x1024 root (hd0,0) ## ****** kernel /kernel-2.6.25-r1 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/sda3 udev ## ****** I was a little doubtful about `init=/linuxrc' since that appears to be saying it initialize from a file at /boot/linuxrc. I don't have such a file there, but all the examples I found seems to include that bit, including in this thread. At any rate it did not work and produced the same error as already posted. So, I'm thinking it probably won't do any real good to monkey around with the kernel either, if the initramfs thing isn't the problem them it seems likely to be a vista problem. However you and others have mentioned having the right drivers for the harddrive. How can I tell if I have the right drivers? And are we talking about something in the vmware settings or do you mean loading the right modules or building certain drivers into the kernel? -- [email protected] mailing list
