Porteus

No need to be sorry, @fanthom. You did your best.
It's not as if things don't work at all, right?
At the moment, the hard coded /dev/sdXX option works. Well, I will live with it.

The discrepancy was maddening, that is all.

i have created 2 partitions in vbox named 'port32' and 'port64' then copied porteus on both. i have no problems with selecting from which partition i want to boot whatsoever. i was using 'from=LABEL:port32' and 'from=LABEL:port64' cheatcodes so linuxrc code is ok for sure. :( So, dashed! running: f...

fanthom wrote:everything is ok from initrd point of view. i have no clue why 'from=LABEL:qt-port' would not work.

does 'from=UUID:e8711956-5c3a-493e-b428-168c7aeb4c9f' work for you?

Very unfortunately, it does not

@fanthom,

do you need anything else from me other than that info?

@surio please also show us your /var/log/porteus-livedbg. Here it is: guest@porteus:~$ cat /var/log/porteus-livedbg # Recognized devices: /dev/sr1: LABEL="Iomega_CD" TYPE="iso9660" /dev/sda1: LABEL="System" UUID="BC98F14798F10126" TYPE="ntfs" /dev/sda2: LABEL="S3A8723D005" UUID="F6A016EAA016B0DB" T...

@brokenman, No, I haven't used UUID so far. Will try it out in a day or two and post back. @fanthom, To be clear, before I post the log, I should change the from= to point at the LABEL so it will generate the respective errors, right? Then I log back into a regular 32 bit session by replacing the la...

@all, I am just as fed up of posting these as you are of reading my grub post after grub post. SIGH! So here's my sincere sorry in advance. The last two discussions on GRUB can be found here http://forum.porteus.org/viewtopic.php?f=117&t=2394 and also here http://forum.porteus.org/viewtopic.php?f=11...

@hamza,
I'm going to redownload it, just to be sure

@fanthom,

In my case, the 2.1 ISO and the md5sums actually matched. Does that mean, I got the right one, or I got the old one?

surio.

@fanthom, I think I misread it or missed it. Either way.... ooops! Okay. I understand now, that this is the way the bootloader works ... It picks the fastest available one and in terms of access, the HDD bus is faster as well as easier to access. Therefore, it is not just the from= but the changes= ...

Hello both, Greatly appreciate your replies! @francois, No, mate. The installed version on HDD is on a EXT4 partition, so no need for a container dat file. The 2.1 that I was running from the HDD was running fresh for the first time (from a FAT32 USBdisk) @jay, I totally agree that UUID would be the...

Just wanted to add that @francois' solution is what I use, as this problem is an upstream (KDE) bug with timezone. So, this workaround fixes that. However, as jay has pointed out, Sao Paulo seems to have issues even with this workaround. Is it time for a " patch ", " within a patch "? (semi-serious?...

@fanthom, On another note: so there must be rc2 installed on a hd (and linuxrc finds it faster than 2.1 final on usb) Is this specific to our distro? Because I've used live versions of a distro to chroot to their installed versions to perform debug actions. And in those cases the HDD data from the i...

I use Openbox on crunchbang/VSIDO a lot, and consider myself somewhat familiar with it. Happy to lend a hand with minor fixes and testing for whoever wishes to take it up. The person responsible for this one is welcome to PM me, if they would like to utilise my help.

Ciao.

Hi fanthom, a) so there must be rc2 installed on a hd (and linuxrc finds it faster than 2.1 final on usb). you could avoid this by using 'from=UUID:' cheatcode. So, to confirm this, I provided from=/mnt/sdb1 from=LABEL:PENDRIVE options in the menu, on two separate occasions. So, I was able to boot i...