![]() ![]() It's also worth noting that when I went through the steps to install the VirtualBox guest additions (including the vbox video drivers) then I could start X however that's not a good solution for me since I would need to go through those steps every time I wanted to boot from the live ISO, and it also doesn't solve the issue of seeing the same error when I boot from the USB stick on my HP Laptop. For completeness, I'm also attaching the output of lspci -k and lsmod. ![]() I have also tried adding nomodeset to the linux line - different errors in that case, but X still fails to start. Initrd (loop)/boot/rootfs4.gz (loop)/boot/rootfs3.gz (loop)/boot/rootfs2.gz (loop)/boot/rootfs1.gz Linux (loop)/boot/bzImage lang=C kmap=us rw root=/dev/null video=-32 autologin Here is my grub.cfg entry for SliTaz on the USB: set extract_path="/AIO/Files/Linux/slitaz-rolling.iso" I couldn't find much info when googling around for what that address out of range might mean, but it sounds like addresses below 0xC000 actually aren't valid for vesa bios. For comparison, when I boot directly from the SliTaz ISO image (in either virtualbox or qemu), it loads correctly with the message VESA(0): Primary V_BIOS segment is 0xC000. I get that same address error when I try to boot the USB stick from my HP laptop as well. (EE) VESA(0): V_BIOS address 0xb8480 out of range But I believe the relevant part is here: LoadModule: "int10" I'm including screenshots of the full Xorg log file for the failed launch from the USB stick - sorry, I don't have a way to copy text from the VBox terminal. ![]() ![]() In order to do a side-by-side comparison, I've tried to copy the boot parameters in case #1 from isolinux.cfg into my grub.cfg (although I'm not an expert in this area so I may have gotten it wrong) I've also set them both to use the same graphics controller (VBoxVGA). I have tried using all three of the Virtualbox graphics controllers for case #2 above and this doesn't seem to make a difference. I use Grub2 as my bootloader.ġ) I CAN start X in SliTaz from virtualbox or qemu (Mac host) when I run directly from the ISO file as the disk image (in both MBR and UEFI modes).Ģ) I CAN start X in SliTaz from qemu (Mac host) when I launch the ISO from the USB stick (in MBR mode).ģ) I CAN'T start X in SliTaz from virtualbox when I launch the ISO from the USB stick (in MBR or UEFI mode).Ĥ) I CAN start X on other Linux ISOs from the USB stick (Linux Mint, Ubuntu, and Kali)ĥ) I CAN'T start X in SliTaz on my HP laptop from the USB stick (in UEFI mode). The USB disk I've created is set up for UEFI and legacy MBR booting I've been able to successfully boot other Linux ISOs from it using both UEFI and Legacy MBR boot modes, so I know it's set up correctly. I can get to a command prompt, so between that and the error messages I'm seeing I suspect this is a video driver issue (specifically, an issue with Vesa or maybe VBE). I have tried this in both Virtualbox and on an HP Laptop without success. I'm trying to create a rescue disk with multiple Linux ISOs on it, so I'd really like to get this working. (=) Using system config directory "/usr/share/X11/ - I am able to start X on SliTaz when I boot from the disk image directly in Virtualbox, but not when I put the ISO on a USB stick and launch from Grub2. (WW) warning, (EE) error, (NI) not implemented, (?) unknown. (++) from command line, (!!) notice, (II) informational, Markers: (-) probed, (**) from config file, (=) default setting, To make sure that you have the latest version. Xorg-server 2:1.15.1-0ubuntu2.6 (For technical support please see ) Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-43-generic root=/dev/mapper/HogwartsCastle-vg-root ro Ssh'ing into the server and running startx yields this.īackground info that may help: I originally hooked up my monitor and keyboard directly to the box, but now wondering if there are some parameters that are populated with the monitor that is not there anymore? startxīuild Operating System: Linux 3.2.0-70-generic x86_64 UbuntuĬurrent Operating System: Linux HogwartsCastle 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35: x86_64 ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |