Prev: hostname question
Next: FYI: Kernel 2.6.33.3 is released (at kernel.org)
From: Grant on 27 Apr 2010 22:18
On Tue, 27 Apr 2010 17:21:48 -0700 (PDT), "Bru++" <thbmatrix(a)gmail.com> wrote:

....
>The problem is: the kernel which comes with Slackware 13 don't boot on
>my virtual machine.

Both kernels? huge.s boots just about anything... What error messages
were issued before the boot failed?

Grant.
--
http://bugs.id.au/
From: Glyn Millington on 28 Apr 2010 02:38
"Bru++" <thbmatrix(a)gmail.com> writes:

> Hello all!
>
> I'm having a trouble on testing Slackware 13 on a virtual machine. I
> tried all the voodoo I know using kernel parameters to fix something
> which may be wrong, but I'm unsuccessful. I have never used Slackware
> 13, and I want to test it on a VM before upgrading my 12.2 to it, so I
> want to know if Slackware 13 uses a "silent" kernel or something else,
> because it simply don't show anything on the screen after the "Booting
> the kernel" message.
>
> And it seems to be a kernel problem, because the following tests I've
> made:
> 1) I get an old 12.0 CD and booted it up;
> 2) After booting, I replaced the ramdrive root filesystem content by
> extracting 13.0 CD initrd(/isolinux/initrd.img)
> 3) I installed Slackware 13;
> 4) I tried to boot with the 13.0 default kernel, after installing lilo
> on the MBR(unsuccessful);
> 5) Booting the 12.0 CD and passing root= parameter boots my system ok;

>
> Does anybody know what can be changed on the slackware's default
> kernel config in order to put it to work on my machine? The system's
> dmesg is at http://www.bruno.inf.br/dmesg_slack12kernel.txt

If your priority here is to test Slack 13, rather than get Slack 13 to
boot in VMware, I suggest that you download VirtualBox (Slackbuilds are
available and I'll bet those for Slack 13 will work on 12.2) and try
Slack 13 in Virtualbox instead.


FWIW I have Slack 13 and a not so current Slack Current running on vb
here for tinkering purposes - no problems at all.


atb



Glyn
--
RTFM http://www.tldp.org/index.html
GAFC http://slackbook.org/ The Official Source :-)
STFW http://groups.google.com/groups?hl=en&group=alt.os.linux.slackware
JFGI http://jfgi.us/
From: Douglas Mayne on 28 Apr 2010 11:35
On Tue, 27 Apr 2010 18:35:47 -0700, Bru++ wrote:

> On 27 abr, 21:50, Jim Diamond <Jim.Diam...(a)deletethis.AcadiaU.ca> wrote:
>> On 2010-04-27 at 21:21 ADT, Bru++ <thbmat...(a)gmail.com> wrote:
>>
>> > On 27 abr, 18:25, Grant <o...(a)grrr.id.au> wrote:
>> >> On Tue, 27 Apr 2010 13:43:37 -0700 (PDT), "Bru++"
>> >> <thbmat...(a)gmail.com> wrote:
>> >> >Hello all!
>>
>> >> >I'm having a trouble on testing Slackware 13 on a virtual machine.
>> >> >I tried all the voodoo I know using kernel parameters to fix
>> >> >something which may be wrong, but I'm unsuccessful. I have never
>> >> >used Slackware 13, and I want to test it on a VM before upgrading
>> >> >my 12.2 to it,
>>
>> >> I'd like to make a suggestion for next time you reformat or upgrade
>> >> the hard drive.
>>
>> >> Make room for a second OS install primary partition.
>>
>> <snip>
>>
>> > Please, forgive me if I don't explained it well, but I'm sure you
>> > misunderstood me... I said I installed it on a virtual machine(means
>> > I created a new virtual machine only for testing Slackware 13). I
>> > haven't upgraded my system yet. I do some tests and I'm careful every
>> > time I upgrade my system, and it's what I'm doing now(I've done
>> > upgrades to all versions since Slackware 8). If you read my message
>> > again, paying attention, you'll understand my real problem.
>>
>> > The problem is: the kernel which comes with Slackware 13 don't boot
>> > on my virtual machine.
>>
>> I think he understood you but suggested an entirely different way which
>> you may find useful in the future.
>>
>> In the interim,
>> (1) which VMware?  Player?  Server (*spit*)?  Workstation?
>
> It's VMWare Server.
>
>> (2) I mostly gave up on vmware a while back and use vbox now.
>>     I have Slack 13.0 (32) running in a vbox vm with no problem at
>>     all.
>>
>> And one other question... why not boot from the S13 CD, rather than
>> confusing the issue with the Slack 12 CD (as you mentioned in your
>> first post)?
>
> Forgive me if I don't explained it better. I'll try to explain again. I
> said in a confusing way that: S13 CD don't boot on this virtual machine.
> It's because the S13's kernel seems to don't work with it. S12 kernel
> works fine, and so I needed the S12 kernel too boot up the machine, and
> S13 kernel to copy from the ramfs system.
>
> Now, I installed it and it(S13 system) works fine with S12's kernel. But
> it's ugly let my system running an old kernel, and I want to know what's
> on my virtual hardware(see the dmesg on the first message) is
> incompatible with S13, just to reconfigure the kernel and compile it
> again.
>
>
>> Cheers.
>>                                 Jim
>
> Thank you.
>
The kernel modules that you need in your initrd depend on which virtual
scsi controller you are using. I have only used the LSI controller on
VMWare. The module dependancies can be determined from the file,
modules.dep. For example, to run VMWare, I will need the module mptspi and
all of its dependancies. On the system with the 2.6.30.10 kernel, I check
the file modules.dep and see the following dependancies (paths omitted):

mptspi -> mptscsih, mptbase, scsi_transport_spi
mptscsih -> mptbase
scsi_transport_spi -> (none)

Therefore, my initrd for that controller should include the four modules
above (mptspi, mptscsih, mptbase, scsi_transport_spi). Also, I would
include the modules for the filesystems that I am using. I am using XFS,
so that means (xfs, exportfs) for me.

The key thing to remember is that virtual machines are really just like
physical machines. You debug startup problems with virtual machines in
the same way as physical machines, etc.

The biggest difference going from 12 to a later version is that the kernel
provided with the OS as released requires an initrd. See the file:
<mirror>://slackware/slackware-13.0/README.initrd
for more information.

--
Douglas Mayne
First  |  Prev  | 
Pages: 1 2
Prev: hostname question
Next: FYI: Kernel 2.6.33.3 is released (at kernel.org)