-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems when running on Linux #23
Comments
Hi, Sorry for my late reply. It's a bit confusing but the script builds a template that is aimed at running inside a Windows host and in order to be self containing it also includes the Windows binaries from the start, so you don't need to manually copy the needed files at a later stage. I hope it makes sense? Regarding the issue you are having, the script is unable to find the Release Date from the BIOS value. Just to be able to help you out better, how does your setup look like? Are you running the script on bare metal or in a VM. The "best" method is run it on bare metal Linux, this can be done by booting a computer with a Linux live CD, run the script and collect the template. Then you can use the template in your regular setup. Please get back to me and I'm sure I can figure out a way to help you =) |
Hello, |
Hi, Bare metal is good. So the reason you are getting this error, is because as noted above, that the script is unable to retrive the correct information. As the BIOS information differ between vendor it might just be something silly. If you can send me the output of: sudo dmidecode -t0 It would help me pin down the problem. Just to respond regarding live-cd runs, you can in most case install missing software even when using a live-cd. |
Hello, |
Hi, They are not listed as general dependencies as it's not that common that people run the template on a server, which seems like you do? Anyway: lscpi can be found in the Ubuntu package pciutils and smartctl in smartmontools if I remember correctly |
I've tried it on Ubuntu 16.04 and managed to get all the dependencies together, and now running the script is giving me this error: [*] Creating VirtualBox modifications ..
Handle 0x0000, DMI type 0, 24 bytes I'm not running this on a server, but on a my simple laptop. :) |
I guess that the value "'FirmwareRevision" is not populated. Do you get any output when you run: hdparm -i /dev/sda | grep -o 'FwRev=[A-Za-z0-9_+/ ."-]*' | awk -F= '{print $2}' ? |
The output is; |
Ok, so if you run: "sudo fdisk -l" and send me the output we can try to figure out what you are using instead. Btw which Linux dist are you using? |
I am using Ubuntu 16.04LTS in live CD mode. The fdisk command gives this output: Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors Disk /dev/loop0: 1.3 GiB, 1433468928 bytes, 2799744 sectors Disk /dev/mmcblk0: 3.7 GiB, 3965190144 bytes, 7744512 sectors Device Boot Start End Sectors Size Id Type |
Are you booting on a flashmemory? If /dev/mmcblk0 is your boot device, try to replace /dev/sda with /dev/mmcblk . |
I'm running from a live DVD inside a DVD-RW drive. Still, running a command |
Have you been able to find a solution? |
Hi sorry for my lack of response, I will try to catch up during next week |
Any luck? |
As you are not able to use hdparm on SD cards (apparently) , do you have better luck if you try the following command? udevadm info -a /dev/mmcblk If so, could you share the raw string for: ATTRS{model} |
Did you any chance to look into it? |
I will close this issue, but feel free to re-open it |
Hello, |
Hello, |
below is fdisk -l output Disk /dev/loop0: 2.3 MiB, 2355200 bytes, 4600 sectors Disk /dev/loop1: 42.1 MiB, 44183552 bytes, 86296 sectors Disk /dev/loop2: 87.9 MiB, 92164096 bytes, 180008 sectors Disk /dev/loop3: 13 MiB, 13619200 bytes, 26600 sectors Disk /dev/loop4: 87.9 MiB, 92119040 bytes, 179920 sectors Disk /dev/loop5: 2.3 MiB, 2433024 bytes, 4752 sectors Disk /dev/loop6: 14.5 MiB, 15208448 bytes, 29704 sectors Disk /dev/loop7: 3.7 MiB, 3887104 bytes, 7592 sectors Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors Device Boot Start End Sectors Size Id Type Disk /dev/loop8: 86.9 MiB, 91099136 bytes, 177928 sectors Disk /dev/loop9: 14.5 MiB, 15196160 bytes, 29680 sectors Disk /dev/loop10: 140.9 MiB, 147722240 bytes, 288520 sectors Disk /dev/loop11: 14.5 MiB, 15204352 bytes, 29696 sectors Disk /dev/loop12: 34.7 MiB, 36323328 bytes, 70944 sectors Disk /dev/loop13: 13 MiB, 13619200 bytes, 26600 sectors Disk /dev/loop14: 3.7 MiB, 3878912 bytes, 7576 sectors |
On Linux, the script is giving an error:
dmi_info['DmiBIOSReleaseDate'] = v['data']['Release Date']
NameError: name 'v' is not defined.
Plus, I noticed that under Linux the script is also checking for Windows dependencies...
The text was updated successfully, but these errors were encountered: