or follow amalux' advice and use (unstable) 2.0 version. neither kernel "cheatcode" configure nor installator are used ( which would result in a reboot). the system failed to start a shell within script nosystem after displaying fault messages and.Ĭ. bootdir (default: GEEXBOX) is not found and. linuxrc script shuts down your system, ifĪ. boot=UUID=643E-C29E) or Linux device names (boot=/dev/hdax or boot=/dev/sdax, where x is 1,2,3,4. Note, that argument boot accepts either UUID (e.g. and Linux is case-sensitive !īut you may use kernel "cheatcode"/argument bootdir to define your own folder. Concerning a HDD installation it is crucial to write the folder name in capital letters, because GEEXBOX is "hardcoded" in linuxrc startup script. I suppose version 2.0 has this feature, otherwise amalux would have failed, too.Ģ.
Geexbox linux download iso#
If you mount the ISO image within Linux, it's of course possible to access GEEXBOX folder. As soon as Linux leaves processor's real mode, the Grub4dos mapped virtual CDROM has gone. It is NOT possible to "chainload" Geexbox ISO image by Grub4dos in a way, that the running Linux system is able to find folder GEEXBOX within the ISO image, because it only searches real CD/DVD drives or HDDs for this necessary folder, but NOT ISO images on such devices.
Geexbox linux download code#
(linuxrc, init, nosystem see Geexbox source code ), where I found all mentioned faults/fault messages.ġ. That's right ! I had a close look at the initializing scripts of Geexbox 1.2.4. Otherwise it's an internal geexbox message/problem. Which will print the uuid of the current root device. Or just list the uuid of DEVICE (if UUID is not specified).įind -set-root uuid () 7f95820f-5e33-4e6c-8f50-0760bf06d79c Whether or not the DEVICE matches the specified UUID (if UUID is specified), If DEVICE is specified, return true or false according to Specified), or just list uuid's of all filesystems on all devices (if UUID is If DEVICE is not specified, search for filesystem with UUID in all partitionsĪnd set the partition containing the filesystem as new root (if UUID is *** New command 'uuid' to identify partitions *** Why don't you try using the actual UUID as seen by grub4dos (strangely enough it is talked about in the grub4dos documentation ) Check within your GRUB config file, which value is set for other OS on the same partition or use ls -l /dev/disk/by-uuid/ to see which uuid matches your partition. the $my_uuid value is the unique ID of your partition. Kernel / GEEXBOX/boot/vmlinuz root=/dev/ram0 rw rdinit=linuxrc boot=UUID=$my_uuid lang=en … Modify the /boot/grub/menu.lst file to add:
Geexbox linux download install#
This allows you to install GeeXboX very easily.įrom GeeXboX CD, simply copy the GEEXBOX folder into your Linux / partition (we suppose it to be /dev/sda1 here). If you already have a Linux OS installed on your system, you might just want to add a GeeXboX entry to your existing bootloader. "***ERROR can't access GeeXboX second stage system!***"Ĭan someone help getting a config to work, unless not possible? Savedefault I changed the "boot=cdrom" to "boot=hd". Kernel /geexbox/boot/vmlinuz root=/dev/ram0 rw rdinit=linuxrc boot=cdrom lang=en remote=atiusb receiver=atiusb keymap=qwerty splash=silent vga=789 video=vesafb:ywrap,mtrr hdtv quiet My secondary attempts were to extract the folder contents from the ISO, and convert the isolinux entries to grub4dos "Guess you're booting from CD-ROM" followed by something about the reason for it not loading correctly. Title Start GeeXboX for HDTV (ISO).īut as soon as the loading bar screen finishes, I got an error with this info:
My first attempts were to map the ISO through DIRECT, and MEM mapping. I originally thought I'd install it to the HD through the built in installer, until I realized the 18MB distro needed 128MB of HD space. I've been attempting to create a Grub4Dos entry that would allow me to boot the latest stable (1.2.4) version of GeeXboX.
0 kommentar(er)
