Welcome
|
FAQ
|
Downloads
|
Wiki
Tiny Core Linux
Welcome,
Guest
. Please
login
or
register
.
Did you miss your
activation email
?
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
News:
Raspberry Pi port,
piCore-15.0
is available!
Home
Help
Login
Register
Tiny Core Linux
»
General TC
»
Tiny Core on Virtual Machines
»
Can't see the volume that I booted from on Google Compute Engine
« previous
next »
Print
Pages:
1
[
2
]
Go Down
Author
Topic: Can't see the volume that I booted from on Google Compute Engine (Read 16196 times)
Juanito
Administrator
Hero Member
Posts: 14831
Re: Can't see the volume that I booted from on Google Compute Engine
«
Reply #15 on:
October 27, 2015, 12:44:44 AM »
You need to use linux-3.16.6-patched.txz and config-3.16.6-tinycore64 from 6.x/x86/release/src/kernel
Logged
curaga
Administrator
Hero Member
Posts: 11048
Re: Can't see the volume that I booted from on Google Compute Engine
«
Reply #16 on:
October 27, 2015, 05:28:32 AM »
You don't need to compile a new kernel - just remaster the module from scsi-3.16.6-tinycore64.tcz into your initrd.
Unpack the scsi extension, copy the virtio module into place, update depmod files. The wiki has more detail on this.
Logged
The only barriers that can stop you are the ones you create yourself.
as
Newbie
Posts: 30
Re: Can't see the volume that I booted from on Google Compute Engine
«
Reply #17 on:
October 27, 2015, 08:27:24 PM »
>> just remaster the module from scsi-3.16.6-tinycore64.tcz into your initrd.
OK great this worked thanks. I can now see the hard disk on Google Compute Engine.
Currently however it only recognises the disk is I manually load the virtio_scsi module with insmod. It doesn't seem to automatically get loaded.
What is the correct way to ensure the module is loaded at boot time?
Logged
curaga
Administrator
Hero Member
Posts: 11048
Re: Can't see the volume that I booted from on Google Compute Engine
«
Reply #18 on:
October 28, 2015, 04:53:10 AM »
If you updated the depmod files, it would get loaded if a device matching it was present.
Otherwise, load it in bootsync.sh.
Logged
The only barriers that can stop you are the ones you create yourself.
Print
Pages:
1
[
2
]
Go Up
« previous
next »
Tiny Core Linux
»
General TC
»
Tiny Core on Virtual Machines
»
Can't see the volume that I booted from on Google Compute Engine