![]() Why is it that live CDs always work with video, but USB installs don't always?Įdit2: Did some Googling. PCLinuxOS was choosing a radeon2000 driver that wouldn't work. I know that I have an ATI card - I think a radeon 5000. If this happens to be the same problem, I need to know if I can fix it from the text prompt I get, or if I have to do a new install with a different flavor. The problem had to do with the video driver that the OS was trying to choose for me sucking like hell. Looking at the docs linked from the site made me recall having trouble with xstart when I was trying to install PCLinuxOS awhile back. ![]() I'm a linux noob, but I can follow instructions rather well. Thanks for taking a moment to read & help. Is it because I used the flavor () instead of the slitaz-4.0.iso? I get a slitaz text login prompt and can log in that way, but startx fails Where I'm at now is that I get errors along the lines of: Kernel /boot/vmlinux-2.6.37-slitaz root=/dev/sdc1 rootdelay=8 quiet Use web install with from flavor list onlineįind thread, boot to CD, "super user mode" to copy to correct location Remove laptop hard drives (per a different thread probably unnecessary)īurn Slitaz 4.0 to CD -> boot & use TazPanel installer I just installed Slitaz to a USB drive through this process: Sorry for the necro, but this thread is the one that helped me out. Install to a USB Flash Drive, as I'm sure they will see the problems in short order. I've submitted a BUG report, but so far there is no news. The install to see if that actually works. Hours and for some strange reason mine just won't boot. If you get your USB Flash Drive to boot from the Install, Please let me know as I've tried for USB, it would be the best thing, because it couldn't be overwritten by accident. If you can remove your hard drive during the install to Still connected to your IDE or SATA Cable and a wrong command can sure mess up your existing You are actually trying to boot from the USB Device, and you are in the Grub CLI.īe very careful if you use the other Grub commands because your Physical Hard Drive is likely It should be found at (hd0,0) assuming your USB Flash Drive is plugged in to a USB Port, and One other thing you can do from the Grub CLI is to double check where the stage1 file is located. Kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/sda1 quiet # Modified from root=/dev/sdb1 to root=/dev/sda1 so Grub finds the correct device # Modified from (hd1,0) to (hd0,0) so Grub finds the correct device Title SliTaz GNU/Linux (cooking) (Kernel vmlinuz-2.6.37-slitaz) So, again you will need to edit /boot/grub/menu.lst to make these modifications. With Slitaz was installed as /dev/sda1 (or /dev/sdax, etc.) or /dev/sdb1 (or /dev/sdbx, etc). Since you are bootingįrom the USB Flash Drive, it will become (hd0,x) even though it is sda or sdb and your partition Or you can edit the /boot/grub/menu.lst file and comment out thatĪfter doing that the Grub Boot menu will still need some modifications. I tracked that problem to the Splash Image (/boot/grub/) not beingĬopied to my USB Flash Drive) You can fix this problem by copying the file from the LiveCD to The first problem I found was that I got an Error of "File not Found" when trying to boot (from They try to boot from the Grub Menu, but lock up with errors. I'll relate results in a new post.I'm wondering what version of Slitaz you are trying to install to USB? I tried the following Now I am going to try a different route: I try to make a true installation of Slitaz on my usb. This could be related to the bug mentioned in I try to summarize the results of my experience:ġ) there is no difference in results using Unebootin and fat32 file system or TazUsb Installer and ext3 file system: in both cases writefs doesn't work and doesn't save current configuration to usb running writefs produce a rootfs.gz on root directory in ram and this file is not copied anyway to boot directory in usb: in order to do it, you have to manually copy file from / to /media/diskĢ) in order to save configuration automatically, you have to run writefs as root user, not as tux ordinary user: in this case rootfs.gz is created correctly in usb and also a backup copy is generated on the same drive ģ) the problem is that creating rootfs.gz apparently delete Tux user configuration: in fact, after creating it, it is impossible to login as tux (it is only possible to log in as root).
0 Comments
Leave a Reply. |