@azure: I see this is your first post here at the CrunchBang forums. Welcome to the herd!
Both Statler (stable) and Waldorf (testing) should run perfectly fine on that netbook. The only concerns I have:
1. With such a small SSD, I'd actually go with a single partition rather than having a separate partition for /home.
2. Wifi may or may not be an issue. Do you know what wifi/WLAN chipset it has?
Last edited by Xazure4 (2013-01-12 19:20:34)
Sorry your previous post and account got deleted/banned; we moderators try our best not to ban real users, but we ourselves are real users and therefore human.
In my experience, CrunchBang should be quite comfortable with 1GB RAM without swap, so long as you limit yourself to fairly light usage (i.e. "typical netbook stuff") - for example, don't try transcoding complete DVDs.
Atheros wifi typically plays very well with Debian.
I was the Moderator who was human in deleting the account, it appeared to be an ad.
If you want your original login back, I can ask corenominal to restore it.
Please accept my apologies.
Apologie accetpet, thanks on that. I've stucked on "Load installer components from CD"...
sudo grub-install /dev/sda
Last edited by sytheii (2013-01-19 01:02:59)
Last edited by anon428again (2013-01-22 06:09:41)
wget -c http://crunchbang.org/download/get/crunchbang-11-20130119-amd64.iso
Last edited by dura (2013-01-21 18:31:45)
"this issue is you, your approach, or your computer".
yes, i was just thinking i could use a more systematic approach, but i wasn't anticipating this being a life long struggle.
also, you assume i didn't torrent it. i did.
Last edited by anon428again (2013-01-22 06:10:58)
sudo ls -l /dev/disk/by-id/*usb* lrwxrwxrwx 1 root root 9 Jan 21 11:25 /dev/disk/by-id/usb-SanDisk_Cruzer_Edge_1101930C9FF316DB-0:0 -> ../../sdb
Last edited by anon428again (2013-01-22 06:45:23)
on the install menu, if i select memtest or live session, it works. (whereas it crashes if i select install)
when i run live session, i will note that there are some extremely suspicous errors. suspicious because those are the errors i'm used to seeing when i boot from the hard drive - running the crunchbang that is on the hard drive. those are the errors that i would like to eradicate by re-installing crunchbang. the errors pertain to sdb write caching or something.
the eee701sd netbook has an older version of #! on it, and it has been having serious problems reading the usb drive. usually what i do is keep plugging in and unplugging the usb stick to different slots until one finally works. however, i don't think this is a hardware issue, because the bios has no problem reading from any usb drive (i can boot from usb).
The error you are getting in gparted is not the problem. It's the same one I mentioned before. I get it too, and others do. Not really sure what is the matter. It could be an issue with your computer, even though you have Waldorf installed already. I guess that probably isn't the problem. Another could be the iso itself, or some bug in corenominal's spin of it. Who knows. In the meantime though, lets go about it slightly differently. No promises, just a shot in the dark really.
Try formatting to fat32 instead of ext2. If you want to format it to ext format, then do ext4. But try fat32.
If you're getting some mounting issues, lets mount it manually. This is strange though, as Thunar is mounting it, so I don't really get what is the issue.
So let's mount it manually:
blkid -o list -c /dev/null
Will give you the uuid's of each partition. The bottom most should be your usb (sdb).
Now, make a place to mount it:
sudo mkdir /media/usbx
sudo mount mount device_node /media/usbx
Where 'device_node' is, put the uuid you get from the first command.
Then try again with dd.
There is some discussion above of the usb needing to be unmounted. So if this doesn't work, try dd with the usb unmounted. To do this you use umount (not unmount). There is lots of pages on this basic stuff if you google a bit.
Other than that, maybe it is a buggered usb or iso, or graphics or whatever. In future, it makes it easier to respond if you are very succinct with your problem.
Last edited by dura (2013-01-21 20:42:47)
^ Agree with both points pvsage, well said. In fact, I have unplugged the usb with enough data to still boot, but then have half a system installed.
As far as #! having any more or any less issues with usb devices, I say it has no more than any other OS or distro, and 99.9% of those issues will come down to user error
This thread, several more like it on the forum and the IRC channel has been filled with more successful installs with the dd method than any usb application. I would highly recommend following pvsage's advice and let the usb finish before removing it. I wait 5 minutes after the last flash of fast blink on the device.
sudo mount mount device_node /media/usbx
Last edited by anon428again (2013-01-22 06:52:23)
The "sync" is supposed to keep the feedback from appearing until after the cache has completely flushed to disc; unfortunately, this doesn't always happen. Most USB flash drives have an indicator light that blinks rapidly during data transfer and either slows or glows steadily when idle; as I mentioned above, relying on this as an indicator (as one used to rely on the disk activity light with floppy disks) also isn't 100% foolproof. Your best bet is to waid until the drive light stops blinking rapidly, than give it at least another 5 minutes after that.
I'm sorry that I can't give you anything more solid than that.
Last edited by anon428again (2013-01-22 07:06:18)
Yeah, don't trust USB sticks with lights on. I know what you mean perhaps. It's the flashy gizmo SanCruzer types.
Here's what I do:
1. sudo dd bs=4M if=/path/to/iso of=/dev/sdX, where X is the device name. No other instructions. It seems to help to have preformatted the USB to FAT 32, although I couldn't tell you why. I just get better results when I do. Then I wait 5-10 minutes after the cursor reappears but sometimes do a sudo -k because you can't be too sure.
2. If that method doesn't work, I use UNetbootin, which works for most distros but not Arch, which is based on simplicity, as it says in the Arch encyclopedia (Vol. III, page 687).
There's very little that won't work through one of those two methods on my 64-bit. However, my 32-bit from 2006/2007 is hit and miss and currently houses CrunchBang and Arch.
> while :
> do if windows sucks then mv windows /dev/null;
> apt-get install crunchbang; fi;
Last edited by OsmoHyttinen (2013-03-09 14:31:50)
Hi VastOne, thanks for your tutorial. With Unetbootin, I was stuck because it kept asking for a CDROM after a correct start from the USB stick. I copied the iso to the USB stick : ~/Downloads$ sudo dd if=crunchbang-11-20130119-amd64.iso of=/dev/sdg1 bs=4M; sync
187+1 Datensätze ein
187+1 Datensätze aus
787480576 Bytes (787 MB) kopiert, 119.041 s, 6.6 MB/s
But in spite of being activated in bios, the USB stick is not recognized. Is there an additional step to observe ? Thank Marcadam