Waldorf Live USB

vicshrike · 2012-06-19 11:16:25

Also did this;

vicshrike@crunchbang:~$ dd if=/dev/zero of=test bs=1048576 count=2048
2048+0 records in
2048+0 records out
2147483648 bytes (2.1 GB) copied, 482.103 s, 4.5 MB/s
vicshrike@crunchbang:~$ dd if=test of=/dev/null bs=1048576
2048+0 records in
2048+0 records out
2147483648 bytes (2.1 GB) copied, 161.112 s, 13.3 MB/s

saneks · 2012-06-19 18:01:56

weird, mine is about same specs, but my installed system on usb was not usable at all..maybe my writes are a lot slower? i think this is the problem.. apps writing back to disk.. so turning off swap is recommended. same stick is fine with a normal live system.

VDP76 · 2012-06-19 19:05:22

hi,
I have been trying Waldorf in a virtualbox for a bit and I like it very much, but I am not yet sure if I want to go "all-in" with a full install (unfortunately I don't have enough space on hard disk to have an installation alongside Statler hmm ) so usb-live with persistence is my next testing stage.. smile
I have been trying to do it following this guide. At the beginning I was able to see the GRUB from my pendrive but then I was getting an error about not being able to boot the kernel. The problem was with the grub.cfg hack, mine actually looks like this:

menuentry "CrunchBang Waldorf USB" {
   set uuid_grub_boot=e50bf90c-8dcb-4ab4-b593-d650db128ebc        #Enter the UUID of your boot partition (this is where grub and your kernel reside)   
   set uuid_os_root=e50bf90c-8dcb-4ab4-b593-d650db128ebc          #Enter the UUID of the partition containing the root partition of your Arch Linux installation. 
                                                                  #(Note: this may be the same as your boot partition)   
   search --no-floppy --fs-uuid $uuid_os_root --set=root          #Here we set the grub "root" variable by locating the uuid of the root partition identified above
   search --no-floppy --fs-uuid $uuid_grub_boot --set=grub_boot   #Here we set a custom variable grub_boot by locating the uuid of the boot partition identified above
   #Here's the magic. We test to see if the boot and root partitions have the same UUID. If they do we append /boot to the $grub_boot variable. For ex. (hd0,1) becomes (hd0,1)/boot. 
   if [ $uuid_grub_boot == $uuid_os_root ] ; then                 
      set grub_boot=$grub_boot/boot
   fi
   # $grub_boot now points to the correct location, so the following will properly find the kernel and initrd
   linux ($grub_boot)/usbcrunch/vmlinuz boot=live live-media-path=/usbcrunch splash gfxpayload=1024x768x32 config quiet ip=frommedia persistent noprompt keyboard-layouts=de
   initrd ($grub_boot)/usbcrunch/initrd.img
 

}

which is basically the same posted by ugh, I just changed vmlinuz1 into vmlinuz and initrd1.img into initrd.img to match the names of the file I had just copied.
With that I am now able to boot into the live system, from where I did the live-rw part apparently without getting errors, but the live system is still not persistent. hmm
Where do I take it from here?? Suggestions??

vicshrike · 2012-06-19 19:58:53

Have burned a new cd with Waldorf 32 bit, have checked that it works. Will do exactly the same thing as above to see how it works. Hope that I will have some time to do it before this weekend.

vicshrike · 2012-06-20 09:25:38

Ok, will try to get this thread on topic a little bit. Pulled the plug on my hds, like I did earlier, see post 16, installed Waldorf to usb. Now after reboot I have installed Firefox, wireless is working, have bookmarked #! forums, rebooted, and the install remembers what has been done. Will run cb welcome script etc to see what happens.

vicshrike · 2012-06-20 11:12:35

Ran the welcome script, 490 updates/upgrades, a bunch of new installs. Took some time, rebooted and for the moment all is cool

pvsage · 2012-06-20 14:16:54

^ Testing really is a moving target, innit? 490 package changes in the 2.5 months since Philip rolled that ISO...it's nucking futs. I think it was only(?) 480 last weekend when I installed Waldorf on my netbook.

Have fun!

vicshrike · 2012-06-20 19:55:02

I will, + have to read up a little bit about the suggestions on the previous page, about journaling and setting the mount options to noatime,relatime.

vicshrike · 2012-06-25 14:00:15

Have run the same test on my usb-Waldorf as I did on my usb-Statler. To compare them. Same laptop, same type of usb. No changes to the system,except normal update/upgrade.

vicshrike@crunchbangwaldorf:~$ sudo hdparm -t /dev/sda

/dev/sda:
 Timing buffered disk reads:  64 MB in  3.04 seconds =  21.06 MB/sec
vicshrike@crunchbangwaldorf:~$ dd if=/dev/zero of=test bs=1048576 count=2048
2048+0 records in
2048+0 records out
2147483648 bytes (2.1 GB) copied, 513.814 s, 4.2 MB/s
vicshrike@crunchbangwaldorf:~$ dd if=test of=/dev/null bs=1048576
2048+0 records in
2048+0 records out
2147483648 bytes (2.1 GB) copied, 120.04 s, 17.9 MB/s

ChickenPie4Tea · 2012-08-23 09:12:30

se7en11 wrote:

So I have installed walldorf on a 4gb usb stick and remove /etc/udev/rules.d/* before I use the stick on a different computer.
Till now I tested on 3 PC's and 2 notebooks and all work fine.

which guide did you follow, just in case i try it.?

silince · 2012-08-25 09:19:55

se7en11 wrote:

So I have installed walldorf on a 4gb usb stick and remove /etc/udev/rules.d/* before I use the stick on a different computer.
Till now I tested on 3 PC's and 2 notebooks and all work fine.

I've created a persistent Waldorf usb, removed the stuff in udev but I can't get it to boot on my little laptop. It hangs at INIT saying that certain processes are respawning too fast. It boots on the machine I originally used to install it however. Do I need to alter some other stuff?

No-Thing · 2012-09-29 22:19:24

se7en11 wrote:

quick (maybe stupid) question.
If I would just install to an usb drive would that install work on any other hardware OR only on the hardware of the box I did the install with? I tried to create a walldorf persistent and all the methods failed.
Installing in text mode and writing grub to the usb drive would be quite easy. BUT I would like to use the drive on many different computer and I can not find out if this is possible.
Does anybody know?
Thanks

Did you find any answer to it?
And

se7en11 wrote:

So I have installed walldorf on a 4gb usb stick and remove /etc/udev/rules.d/* before I use the stick on a different computer.
Till now I tested on 3 PC's and 2 notebooks and all work fine.

Is this something you need to do?

With love and gratitude -
No-Thing But Divine

Last edited by No-Thing (2012-09-29 22:22:18)

No-Thing · 2012-09-30 15:09:04

machinebacon wrote:

There are two guides:
http://www.betaarchive.com/forum/viewtopic.php?t=19276
http://crunchbanglinux.org/forums/topic … rsistence/
If you use dd it will make the stick have only one partition, so that won't work.

I have tried the first guide. Took out the harddrive of my older laptop - fixed a usb to usb install and it went like a dream. I then restarted after installation and the usb key got into grub and had 2 choices of CrunchBang *Yah!*
Inserted the harddrive also - and still the USB key worked beautyfull. It was a little slower on startup - but it was okey and in total CrunchBang was running fine on the laptop from the USB.
But...

Now here comes the trouble - if I insert the key into my new laptop it will only come to a point where it tells me starting Grub and giving me no Grub menu like it should. It's just sitting there doing No-Thing. sad
So... what's the game? I could try using the same guide and doing the install on the new laptop and see if it will then work on the older one after the install.
But I am thinking - does grub have some kind of number it uses to check if it's the right computer it's running on?

I used CrunchBang 10 32bit version as it is the only one that will run on both laptops.

With love and gratitude -
No-Thing But Divine

Last edited by No-Thing (2012-09-30 16:11:39)

No-Thing · 2012-09-30 17:47:46

Still using CrunchBang 10 32 bit version:

I have just tried the first guide using my new laptop - and I have the same problem :S
The new computer that I this time made the CrunchBang USB with is still having trouble regarding starting Grub.

So I took the stick and inserted it into my old laptop just for the hell of it - and wupti works without any problems beside now being alot more entries in Grub because I did not take the harddrive out of my new computer when I made the CrunchBang USB. But no worries about it, the CrunchBang USB is in the Grub selection and works.

So what the hell is going on - why won't it work on my new laptop?

*ohh, BTW sorry for being off-topic by using stable version*

With love and gratitude -
No-Thing But Divine

Last edited by No-Thing (2012-09-30 18:00:31)

xaos52 · 2012-09-30 18:28:13

Perhaps your new computer is using UEFI in stead of BIOS? Or GPT partitioning scheme? See arch linux wiki for explanantions.

No-Thing · 2012-10-02 02:44:19

Aloha dear divine reader

Well... I am trying to find an solution to this - and looking at other bootloaders. I think it would be possible to try other boot loaders to fix this issue... Not that I have any experience with bootloaders - but I need to get this thing fixed! smile
So the bootloader is Grub 2 - that I am using for my USB key.... Now I read about syslinux, and reading more on the subject on bootloaders. There has to be a bootloader out there that will do the job without failing just because something in the computer is not as it want it to be.

Anyone with good experience with bootloaders and what could be a good choice for USB boot? smile

-edit-
Heard about syslinux - mayby that will work out... Have to read more about it.
I have not found a solution for Grub 2 sad

Last edited by No-Thing (2012-10-02 03:02:34)

super.luser · 2012-10-02 05:53:30

Syslinux is good for USB drives, but then again... so is almost any boot loader that boots and... loads... things.

Are you sure the newer laptop isn't using UEFI or something? If GRUB isn't even being reached (and you have the boot order set up to reach the USB before your internal HD, of course), then that sounds like it could be an EFI booting problem. If it is EFI, you could try booting it in BIOS mode (if the mobo vendor decided to include that).

Thing is, with UEFI, your USB might not even be showing up as a bootable option. UEFI doesn't use the classic MBR way of finding boot loaders -- it does things quite differently. So if you are having UEFI troubles, you might want to try enabling BIOS (or "legacy") booting, or at least try to hit the hotkey for temporarily booting another device and see if that works instead.

Writing out a whole guide for UEFI booting is waaay beyond my current capabilities, though, I'm sorry to say. sad

iMBeCil · 2012-10-02 13:19:10

@No-Thing:

Your problem seems veeeeery similar to problem of mine few days ago, when I tried to install fresh #! on one USB stick with another (bootable) USB stick. I could boot from installation stick, but couldn't from freshly installed one.

It turns out that I forgot one important step: during #! installation, close to the end, you are asked about creating GRUB on some drive (HDD, like /dev/sda).

In my case, I had to say 'No', and then debin-install offered me to install grub on another media.

There you have to chose your new stick (something like /dev/sdb or /dev/sdc ...; at this point I cannot remember if it has to be /dev/sdb or /dev/sdbX). And that was it, at least for me.

The point is: you have to install GRUB (during installation) on USB stick, and not on HDD. And make USB stick bootable, of course.

I hope this helps. Of course, it might have to be UEFI thing ... no idea about that.

No-Thing · 2012-10-09 11:12:07

I have tried the guide below with no luck but came a little further getting into the Grub menu - but trying to start any of my now 2 systems inside grub menu will only make a blank screen appear on my new laptop and no-thing more:
http://crunchbanglinux.org/forums/topic … ce/page/2/

Both systems installed on the USB key works from my older computer - nothing works from the new HP laptop.

The first problem I ran into sounds like the problem describe on these 2 pages:
https://bugzilla.redhat.com/show_bug.cg … &id=805747
http://savannah.gnu.org/bugs/?37331

With love and gratitude -
No-Thing But Divine

Last edited by No-Thing (2012-10-09 16:23:31)

xaos52 · 2012-10-09 11:31:44

Then you should be able to see which devices grub recognizes:
at the grub menu, with your cursor over the line you want to boot, press 'e' for edit, then 'F2' for the grub shell.
at the grub prompt type 'ls' and press 'enter'
This should show you the devices that grub sees.

Last edited by xaos52 (2012-10-09 11:32:17)

kyeshi98 · 2013-03-22 16:51:12

Hi! I made a guide on how to get a persistent LiveUSB working for Waldorf, and I have tested it to work correctly with minor disturbances and bugs.
http://crunchbang.org/forums/viewtopic. … 78#p297178

CrunchBang Linux

SEARCH

#26 2012-06-19 11:16:25

Re: Waldorf Live USB

#27 2012-06-19 18:01:56

Re: Waldorf Live USB

#28 2012-06-19 19:05:22

Re: Waldorf Live USB

#29 2012-06-19 19:58:53

Re: Waldorf Live USB

#30 2012-06-20 09:25:38

Re: Waldorf Live USB

#31 2012-06-20 11:12:35

Re: Waldorf Live USB

#32 2012-06-20 14:16:54

Re: Waldorf Live USB

#33 2012-06-20 19:55:02

Re: Waldorf Live USB

#34 2012-06-25 14:00:15

Re: Waldorf Live USB

#35 2012-08-23 09:12:30

Re: Waldorf Live USB

#36 2012-08-25 09:19:55

Re: Waldorf Live USB

#37 2012-09-29 22:19:24

Re: Waldorf Live USB

#38 2012-09-30 15:09:04

Re: Waldorf Live USB

#39 2012-09-30 17:47:46

Re: Waldorf Live USB

#40 2012-09-30 18:28:13

Re: Waldorf Live USB

#41 2012-10-02 02:44:19

Re: Waldorf Live USB

#42 2012-10-02 05:53:30

Re: Waldorf Live USB

#43 2012-10-02 13:19:10

Re: Waldorf Live USB

#44 2012-10-09 11:12:07

Re: Waldorf Live USB

#45 2012-10-09 11:31:44

Re: Waldorf Live USB

#46 2013-03-22 16:51:12

Re: Waldorf Live USB

Board footer