I had tried a 1st installation with the unetbootin version available in the ubuntu repos. it failed when trying to install grub, just like many among us.
I then downloaded the last unetbootin version from sourceforge : yeeeees it worked. precisions : except for unetbootin, every other conditions were the same....
... now I need to switch to azerty.
Last edited by dok (2010-07-09 21:30:18)
ok. azerty is fine.
But the first strange thing that happened to me is that the sources list was almost empty. There only was the line refering to the "cd-rom". I had to add by myself the other repos. Is it normal ?
I used Unetbootin 372 in Windows Vista to make my USB stick. Statler i486 Openbox. Chose default in the UNetbootin boot menu.
Installed on ASUS Eee 701.
Did not manage to install in LVM encrypted mode ("failed to create swap partition on none" or something in this vein, said the partition editor)
I did fallback on default standard full disk partitioning.
I didn't get my username added to the sudoers file.
The repos weren't updated during cb-welcome.
All the rest looks fine so far.
Any updates on getting an Unetbootin install of Statler A2 to work? I'm sorta stuck w/o access to blank cd-r's at the moment
Finally got Alpha 2 with UNetbootin and everything on LVM
That was more paint full than what i thought....
I did experience with different way of installing and all of them have something missing.
My first problem was that grub couldn't start the root.
I looked on another thread which says something about adding the dm_mod in the initramfs-tools file, it didn't work for me.
The problem was that the lvm2 package was not install
so i choose the default install and chroot in to it but squeeze repository werent in the sources.list so added them
but after a reboot i notice that none of the crunchbang theme were install ( maybe i had to add some other repository for that)
so i decided to go for the text install but it wouldnt bring my nic.
I installed the lvm2 package with dpkg and rebooted and my system and everything was working.
note: now that i have a fully working system i see that i might have been successful on the first case adding the statler repository.
Thank you for this great distribution,
Used Ubuntu Unetbootin version 408-1ubuntu0.10.04.1
Perfectly worked as live session, as well as to install it on my laptop (I chose the Openbox AMD64 flavour)
Version 471-1 of unetbootin on Statler 10 A 2 lots of success, prolly too much. I need a new hobby. Ive made USB's of all flavors of crunchbang, Mint, sidux, ubuntu's, zenwalk, and a few others with 100% smooth as silk success, on my 3200 compaq desktop, and my 1400 compaq laptop, both considered low end I spose.
Off Like A Prom Dress...
I aborted default install option because it couldn't detect my internet . Text install went smoooooth.
I made an USB boot stick with unetbootin from statler alpha 1 repos and it failed to install on my Acer Aspire One (arch : i 686). I tried a second time with unetbootin from Ubuntu's 10.4 repos (arch : amd64) and this time text install worked fine.
I first tried using the Fedora Live USB creator, but it complained about the ISO not containing a live system or words to that effect, so I used the unetbootin in Fedora 13, 0-8.485. My user was not a sudoer, so the startup script failed. After I fixed that, the script again failed because I had no repositories in sources.list. I stole somebody's repo list from another thread and all has worked fine since. Loving it, by the way. It's very snappy on the eee pc 900 I installed it on. The only problem now is the 2-finger multitouch for right-click does not work. Edit- yes it does.
Last edited by rotwang888 (2010-08-02 14:34:25)
I used version 471, which gave a working live session with alpha2, but couldn't get past the CD-based media issue. It kept asking where the cd rom was.
I used a second tutorial in the wiki which used windows image burn (i believe) to write the iso, and that worked perfectly.
Worth noting (?) that unetbootin allowed me to open up my usb drive, and view the folders, even add more folders.
With windows image burn, the flash drive became an un-readable ~680mb drive which windows wanted to format before I opened it in windows.
My install worked pretty well, used unetbootin version 471. I had the keyboard problem and I don't seem to be in the sudoers file, but that one is probably my fault rather than the installers.
# deb cdrom:[Debian GNU/Linux 6 _Squeeze_ - Official Snapshot i386 LIVE/INSTALL Binary 20100624-21:50]/ squeeze main deb cdrom:[Debian GNU/Linux 6 _Squeeze_ - Official Snapshot i386 LIVE/INSTALL Binary 20100624-21:50]/ squeeze main # Line commented out by installer because it failed to verify: # deb http://security.debian.org/ squeeze/updates main # Line commented out by installer because it failed to verify: # deb-src http://security.debian.org/ squeeze/updates main
Last edited by hhig (2010-08-19 20:06:53)
## CrunchBang Linux 10.xx aka Statler ## Compatible with Debian Squeeze, but use at your own risk. deb http://packages.crunchbanglinux.org/statler/ statler main ## Official Debian Repositories: deb http://ftp.de.debian.org/debian/ squeeze main contrib non-free # deb-src http://ftp.de.debian.org/debian/ squeeze main contrib non-free deb http://security.debian.org/ squeeze/updates main
I'd reckon that's it. BTW personally it seems the German repositories are the fastest even living on the other side of the world from them.
Thanks for the quick reply. I gave the German servers a try and you're right, think I'll stick with them for now.
I have tried latest unetbootin, lili and the pendrive linux app and I have tried hp format tool. All those on a kingston datatraveler 1gb, a kingston dt-ii 4gb and a toshiba 4gb usb sticks. Nothing works on my gigabyte GA-8I865GME-775-RH (last revision) '_'
I've been able to boot many other distros, slitaz, puppy, ubuntu, antix, pclinuxos, pelicanHPC, pure:dyne... crunchbang 10 (and archbang) are refusing every attempt.
They boot fine on my ibm x40 though. Any suggestions? It's driving me crazy >_<
I'm downloading 9.04 to test but I want to try 10. I had a look on it on the laptop and it looks brilliant. I even shrunk my 7 partition to prepare for instalation (yes, I like it that much ^_^)
Last edited by acrocosm (2010-09-06 09:35:59)
I deleted and recreated the partition then used unetbootin. It installed fine apart from not finding the onboard lan card and automounting of windows partitions (I'm not sure if that's standard functionality)
Edit: oh I had LAN disabled in bios that's why it didn't pick it up. Nice, I was used in windows that ignores such settings ¬_¬
Last edited by acrocosm (2010-09-10 09:22:06)
I used unetbootin 471. made the boot disk on my toshiba nb 205 runing xubuntu 10.04. install went fine however, when it tired to download software sources and update neither seemed to happen, it just skipped em. Also my user name wasn't capable of sudo. I resolved these problems. on the other hand I can't set my resolution to 1024x768 all I get is 1024x600. cant get my external usb drives to mount. tried editing fstab and couldn't find one. maybe Im stupid. In any case Im burning a #! cd right now and hoping usb cd drives don't have this problem. Ive been using this system for little over 20 hours...I must say that once all the kinks are ironed out I will be a happy guy, smokes xubuntu in speed
I don't know whether this will help anyone or whether it has already been said but I was getting a "No common Cd-ROM drive was detected" when I was attempting to install via. both Unetbootin & Win32diskimager, after it automatically searched for the device required it couldn't find anything
I went to the shell during installation and did a "list-devices usb-partition" and found the path to my USB stick, I went back to the step and manually entered the path after declining its offer to find it automatically. Took me a little while to understand what was going on but I figured once I got this installed & working that it may benefit someone who encounters a similar error & like me isn't as familiar as others.
I had no problems, using Unetbootin 4.85 in ArchLinux, beyond the installer attempting to connect to the internet and failing. Everything else works, however.