Nikos Chantziaras <[EMAIL PROTECTED]> writes:
> Harry Putnam wrote:
>> [...]
>> It worked just fine. But none of my attempts to bring the kernel up
>> to date have worked. All failing with a error message something like:
>> `/dev/sdb3 is not a valid device'.
>
> According to your screenshot, you don't even have an sdb. All the
> kernel sees is one hard disk: sda. If you do have an sdb, check in
> VMWare that it's actually attached to the VM.
>
> Also, are you sure the VM you downloaded is for the version of VMWare
> you're actually using? Why not create the VM yourself instead of
> downloading it?
I downloaded one thinking it would be faster after spending several
days trying to get my own built and running. I had the same boot
problem with my own rendition.
And in fact it booted up absolutely painlessly. It was only when I
started trying to build a newer kernel that the troubles began.
About sdb3. In the following dmesg output (when booting with a
working kernel-2.6.24-r8 I wondered if anyone can determine what
driver is involved there. I couldn't really tell much from it other
than the kernel sees it with no problem:
==========================================
[...]
mptbase: ioc0: Initiating bringup
ioc0: LSI53C1030 B0: Capabilities={Initiator}
scsi4 : ioc0: LSI53C1030 B0, FwRev=00000000h, Ports=1, MaxQ=128, IRQ=16
scsi 4:0:0:0: Direct-Access VMware, VMware Virtual S 1.0 PQ: 0 ANSI: 2
target4:0:0: Beginning Domain Validation
target4:0:0: Domain Validation skipping write tests
target4:0:0: Ending Domain Validation
target4:0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 127)
sd 4:0:0:0: [sdb] 44040192 512-byte hardware sectors (22549 MB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 5d 00 00 00
sd 4:0:0:0: [sdb] Cache data unavailable
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sd 4:0:0:0: [sdb] 44040192 512-byte hardware sectors (22549 MB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 5d 00 00 00
sd 4:0:0:0: [sdb] Cache data unavailable
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1 sdb3
sd 4:0:0:0: [sdb] Attached SCSI disk
sd 4:0:0:0: Attached scsi generic sg2 type 0
=============================================
