The antix-15.1_x64-full.iso Live installer won't let me choose a root partition...
I don't get it. I downloaded the iso, and the iso.md5 which matched what I got with
md5sum. Then I thought I'd start with a liveUSB so that I could experiment with some
persistent tweaks (Mostly installing openbox and my own ~/.config/openbox/rc.xml file
so that the keybindings I depend on will work. (I just don't do well with a mouse.)
And then I'd have a little fun learning how to save such changes...
At least that was the plan. Somebody mentioned unetbootin, when I'd asked about it in a
previous thread, So since Opensuse has unetbootin, I installed that to my Opensuse
installation and used it to make a theoretically bootable flashdrive.
But my HP Pavilion said it wasn't bootable. So I mounted it and took a peek and it looks
like it was set up for EFI with grub2 and syslinux...
But the grub2 part and/or I think the syslinux should still work with a legacy bios
set up right?
I mean it isn't that my PC can't boot from a flashdrive because I've booted a few old Puppy
Linux flash drives in it. Though to be honest, neither the Slacko 5.6, nor the
Quirky 5.7.1 booted correctly. Both said they were loading. but melted down when the
gui should have kicked in. But the Fatdog flashdrive gets all the way to a working
desktop... The antiX flashdrive got an instant response that said it wasn't bootable
and that I should insert a bootable floppy?!?
Actually my Pavilion is capable of using EFI boot methods, but I disabled that because
I already know how to work with legacy bios, and my stand alone boot partition is grub
legacy too.I also heard it was a bad idea to mix EFI and bios methods on the same
machine.
Oh well, since the liveUSB isn't booting, it's time for plan B. Which was to burn a live dvd.
Brasero said it was successful. And the live dvd does boot. But I don't like the available
window managers enough to play with it. So my plan was to use the menu to test a couple
applications and then install it to the preformatted 100 Gig partition on the Pavilion's
primary hard drive. Once it would be installed there, I'd use apt-get from a virtual console
to install the things I need to be comfortable with the GUI...
The problem is that when I start the installer, I get stuck at the select root
partition field. When I get there it says"none" but there's an arrow that should
open a list of several partitions. Including the ext3 partition sda5 with the LABEL
of"MyAntix-5"... But when I click on the arrow it doesn't list any partitions at all.
The swap partition sees the swap partition on sda4 {labeled"MySwap"}...
That's when I noticed that there was a field a little further down that was preset to
a default value of ext4. That field let me set it to ext3. But the root partition
field still won't find any of the 6 ext3 partitions on /dev/sda...
{many politically incorrect expletives deleted}
It took me 3 hours to download antix-15.1_x64-full.iso from the mirror. It occurs to
me that ANY install that get's me far enough along for me to use apt-get from a
virtual console can be modified into what I want. I don't have to start with"full".
So I gotta ask if the installer from any of the other 64 bit iso versions is any
better at seeing preexisting ext3 partitions???
Or is there a"trick" to get the one I got to see the ext3 on sda5???
11 posts
• Page 1 of 1
-
jtwdypPosts: 71
- Joined: 08 Apr 2012
#1
Last edited by jtwdyp on 26 Jun 2016, 23:07, edited 1 time in total.
-
dolphin_oraclePosts: 2,238
- Joined: 16 Dec 2007
#2
does your machine happen to have a eMMC style SSD inside? The antiX 15 installer can't see those, but the one in antiX-16 (coming this weekend) can.
a legacy boot usb should be using syslinux for the bootloader. depending on what version of syslinux was installed on your opensuse setup, its possible for unetbootin to complete but not fully install the syslinux bootloader. thank the syslinux guys for making the later versions of syslinux incompatible with earlier versions.
however, you could use the liveDVD/CD you made to use the antiX unetbootin to make a liveUSB.
a uefi boot usb should be using grub2.
a legacy boot usb should be using syslinux for the bootloader. depending on what version of syslinux was installed on your opensuse setup, its possible for unetbootin to complete but not fully install the syslinux bootloader. thank the syslinux guys for making the later versions of syslinux incompatible with earlier versions.
however, you could use the liveDVD/CD you made to use the antiX unetbootin to make a liveUSB.
a uefi boot usb should be using grub2.
-
jtwdypPosts: 71
- Joined: 08 Apr 2012
#3
Besides, it sees the drive well enough for the other field to show me the swap partition. It only seems to be the root partition selection field that refuses to populate with anything...
I don't suppose it could be ignoring the preformatted ext3 partitions because it wants ext4??? I mean has anyone actually tested installing that iso to a preformatted ext3 partition yet?
By the way, is the recommended way to turn antiX-15 into a rolling release version still just a matter of using Debian testing instead of any Debian stable repos in the sources list?
Nah, the closest thing to a solid state drive I've ever had my hands on is a couple 32 Gig flashdrives. This Pavilion came with a one terabyte sata drive that looked just like the 200 Gig one I added to it when my brother in law gave me the Pavilion's"tower" after his win7 OS self destructed...dolphin_oracle wrote:does your machine happen to have a eMMC style SSD inside? The antiX 15 installer can't see those, but the one in antiX-16 (coming this weekend) can.
Besides, it sees the drive well enough for the other field to show me the swap partition. It only seems to be the root partition selection field that refuses to populate with anything...
I don't suppose it could be ignoring the preformatted ext3 partitions because it wants ext4??? I mean has anyone actually tested installing that iso to a preformatted ext3 partition yet?
Well I'll certainly try that before I spend another 3 hours downloading a different iso version... But unless the hard drive installer on a liveUSB based on the same ISO, will populate the home partition selection field, it won't help much. Having a portable antiX liveUSB all configured to run"my way" would be a nice bonus. But my goal is a long term rolling release hard drive installation of antiX on /dev/sda5...a legacy boot usb should be using syslinux for the bootloader. depending on what version of syslinux was installed on your opensuse setup, its possible for unetbootin to complete but not fully install the syslinux bootloader. thank the syslinux guys for making the later versions of syslinux incompatible with earlier versions.
however, you could use the liveDVD/CD you made to use the antiX unetbootin to make a liveUSB.
By the way, is the recommended way to turn antiX-15 into a rolling release version still just a matter of using Debian testing instead of any Debian stable repos in the sources list?
That would actually be the SAME liveUSB, being booted by the PC's EFI OR legacy bios right?a uefi boot usb should be using grub2.
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#4
I mean has anyone actually tested installing that iso to a preformatted ext3 partition yet?
Yes - works fine with antiX-15.
Yes - works fine with antiX-15.
-
dolphin_oraclePosts: 2,238
- Joined: 16 Dec 2007
#5
there is one type of partition that the installer filters out...partitions that are too small. stupid question, are you sure you made a 100 GB partition and not a 100mb partition? you can check with gparted, on the antix liveMEDIA already.
it shouldn't matter. Mine even shows ntfs and fat32 partitions, although I admit I don't have any ext3 partitions.jtwdyp wrote:Nah, the closest thing to a solid state drive I've ever had my hands on is a couple 32 Gig flashdrives. This Pavilion came with a one terabyte sata drive that looked just like the 200 Gig one I added to it when my brother in law gave me the Pavilion's"tower" after his win7 OS self destructed...dolphin_oracle wrote:does your machine happen to have a eMMC style SSD inside? The antiX 15 installer can't see those, but the one in antiX-16 (coming this weekend) can.
Besides, it sees the drive well enough for the other field to show me the swap partition. It only seems to be the root partition selection field that refuses to populate with anything...
I don't suppose it could be ignoring the preformatted ext3 partitions because it wants ext4??? I mean has anyone actually tested installing that iso to a preformatted ext3 partition yet?
pretty much, and using the antiX testing sources instead of the stable ones.By the way, is the recommended way to turn antiX-15 into a rolling release version still just a matter of using Debian testing instead of any Debian stable repos in the sources list?
same stick.a uefi boot usb should be using grub2.
That would actually be the SAME liveUSB, being booted by the PC's EFI OR legacy bios right?
there is one type of partition that the installer filters out...partitions that are too small. stupid question, are you sure you made a 100 GB partition and not a 100mb partition? you can check with gparted, on the antix liveMEDIA already.
-
jtwdypPosts: 71
- Joined: 08 Apr 2012
#6
HOWEVER I can confirm that the liveUSB made with the unetbootin on the live-dvd not only boots, but I checked and it's installer does show me all my partitions in the root partition section field. At which point I backed out and started configuring my liveUSB. I had selected a persistent option that required me to change both root's and demo's passwd.and I added a few tools I'd miss if I had to use the liveUSB as a rescue"disk". And a few more just to make it fun to use.
That included installing openbox. Unfortunately I can't figure out how to get the liveUSB to let me actually use openbox on it. I wasn't planning on trying to get the liveUSB to boot to runnlevel 3 so that I could use startx instead of a display manager. But I can't get it listed in the liveUSB's boot menu's selectable list of window managers...
If I was booting to runlevel 3 then I could put a few things in my ~/.xinitrc, including a last instruction of:
I've only ever booted openbox that way. But I was under the impression that if I put that same exec command in a file called ~/.xsession
than it would become my"default session type" when booting with a graphical login manager. So I did that, and selected"default" as my window manager type in the boot menu... But it's still not starting openbox.
Anybody know how to get a liveUSB to start up a different window manager from any of the default boot loader selectable ones???
No there's nothing stupid about that question. But I'm very sure, I used gparted to repartition the hard drive to multi-boot 3 linux (complete with another empty ext3 in case I want to test some new distro someday.dolphin_oracle wrote:it shouldn't matter. Mine even shows ntfs and fat32 partitions, although I admit I don't have any ext3 partitions.jtwdyp wrote:I don't suppose it could be ignoring the preformatted ext3 partitions because it wants ext4??? I mean has anyone actually tested installing that iso to a preformatted ext3 partition yet?
pretty much, and using the antiX testing sources instead of the stable ones.By the way, is the recommended way to turn antiX-15 into a rolling release version still just a matter of using Debian testing instead of any Debian stable repos in the sources list?
there is one type of partition that the installer filters out...partitions that are too small. stupid question, are you sure you made a 100 GB partition and not a 100mb partition? you can check with gparted, on the antix liveMEDIA already.
HOWEVER I can confirm that the liveUSB made with the unetbootin on the live-dvd not only boots, but I checked and it's installer does show me all my partitions in the root partition section field. At which point I backed out and started configuring my liveUSB. I had selected a persistent option that required me to change both root's and demo's passwd.and I added a few tools I'd miss if I had to use the liveUSB as a rescue"disk". And a few more just to make it fun to use.
That included installing openbox. Unfortunately I can't figure out how to get the liveUSB to let me actually use openbox on it. I wasn't planning on trying to get the liveUSB to boot to runnlevel 3 so that I could use startx instead of a display manager. But I can't get it listed in the liveUSB's boot menu's selectable list of window managers...
If I was booting to runlevel 3 then I could put a few things in my ~/.xinitrc, including a last instruction of:
Code: Select all
exec openbox-session
than it would become my"default session type" when booting with a graphical login manager. So I did that, and selected"default" as my window manager type in the boot menu... But it's still not starting openbox.
Anybody know how to get a liveUSB to start up a different window manager from any of the default boot loader selectable ones???
-
dolphin_oraclePosts: 2,238
- Joined: 16 Dec 2007
#7
1. I created a liveUSB with unetbootin.
2. I selected persist_all in the boot options to get persistence set up.
3. after boot up, I installed openbox.
4. Openbox should now appear in the"Other Desktops" menu of the start menu. select that and openbox starts up.
5. antiX will remember the last desktop used and use that as the default. So as long as you select persistence again on the next boot of the liveUSB, you should get openbox. (at least I did).
2. I selected persist_all in the boot options to get persistence set up.
3. after boot up, I installed openbox.
4. Openbox should now appear in the"Other Desktops" menu of the start menu. select that and openbox starts up.
5. antiX will remember the last desktop used and use that as the default. So as long as you select persistence again on the next boot of the liveUSB, you should get openbox. (at least I did).
-
jtwdypPosts: 71
- Joined: 08 Apr 2012
#8
I say it's sudo based because it wanted demo's password until I put"targetpw" in the"Defaults" of the suduers file. Now it wants the root password, like admin functions should want...
Now my problem is that NONE of my window managers show the install icon anymore ??????
Does anybody know what command line I could type into a roxterm {presumably while running a root shell} to start up the hard drive installer???
AhHa! That's what I was missing... Since I don't generally use any Display Manager, I didn't know where to look for that. When you run startx from a virtual console after booting to runlevel 3, if you want a different Window Manager you"log out" {of the WM} which {since no DM is running} drops you back in the virtual console where your still logged in{to a command shell}. Then you do something to change which WM startx points at {in my case I use a wrapper script which copies the selected pre-edited file to ~/.xinitrc and calls startx for me. }dolphin_oracle wrote: 4. Openbox should now appear in the"Other Desktops" menu of the start menu. select that and openbox starts up.
Yes that part worked perfect... Though everytime I start openbox that way I get a pop-up {sudo based} password prompt to give wicd access...5. antiX will remember the last desktop used and use that as the default. So as long as you select persistence again on the next boot of the liveUSB, you should get openbox. (at least I did).
I say it's sudo based because it wanted demo's password until I put"targetpw" in the"Defaults" of the suduers file. Now it wants the root password, like admin functions should want...
Now my problem is that NONE of my window managers show the install icon anymore ??????
Does anybody know what command line I could type into a roxterm {presumably while running a root shell} to start up the hard drive installer???
-
dolphin_oraclePosts: 2,238
- Joined: 16 Dec 2007
#9
minstall will start the installer.
- skidoo
- Joined: 09 Feb 2012
#10
By default, antix session management suppresses (or silently handles) details such as this
and by insisting on square-pegging a round hole, you're choosing to forego one of great benefits antix provides -- easily customizeble session management.
So, after installing openbox (and obconf? and lxpanel?) ...yeah, you have your work cut out for ya.
Yep, no install icon on the desktop. Yep, no customized autostarts applied, and after you've installed additional debian packages...
...possibly unwanted extra apps autostarting each session unless you weed them out
(weed, meaning, check post-install whether installation of a given package has created ~/.config/autostart/ and populated it with a .desktop file)
along with a dozen or so other details you'll need to configure (and monitor, on an ongoing basis).
==================
You can setup for your favorite keybinds to be recognized in iceWM and/or in fluxbox and/or in JWM, so I (still) can't understand the merit in opting to roll openbox.
If doing so were a"for fun" or"simply academic" excercise, that's fine. (That's great!)... but obviously that's not the case.
wicd permission box is triggered by the freedesktops.org"xdg autostarts" built into debian.Though everytime I start openbox that way I get a pop-up {sudo based} password prompt to give wicd access...
By default, antix session management suppresses (or silently handles) details such as this
and by insisting on square-pegging a round hole, you're choosing to forego one of great benefits antix provides -- easily customizeble session management.
So, after installing openbox (and obconf? and lxpanel?) ...yeah, you have your work cut out for ya.
Yep, no install icon on the desktop. Yep, no customized autostarts applied, and after you've installed additional debian packages...
...possibly unwanted extra apps autostarting each session unless you weed them out
(weed, meaning, check post-install whether installation of a given package has created ~/.config/autostart/ and populated it with a .desktop file)
along with a dozen or so other details you'll need to configure (and monitor, on an ongoing basis).
==================
You can setup for your favorite keybinds to be recognized in iceWM and/or in fluxbox and/or in JWM, so I (still) can't understand the merit in opting to roll openbox.
If doing so were a"for fun" or"simply academic" excercise, that's fine. (That's great!)... but obviously that's not the case.
-
jtwdypPosts: 71
- Joined: 08 Apr 2012
#11
I add lxpanel because it adds a reasonable task bar. And it comes with another menu, which can be handy if I'm using a distro that won't auto-update openbox's menu. Though I seldom use the menu for anything other than logging out. I occasionally use it to figure out the command names of anything I don't have keybindings for.
But then I usually call it from the command line anyway
Once I'm booting to runlevel 3 and using startx, I've never had any problems with any installed applications starting themselves. Not on opensuse, not on mageia, and not on my old rolling release configured antix-11 which was using the debian testing repos to stay up to date until I switched to a new PC and decided I wanted antix on it.
Though I will admit I occasionally have to set Xorg back to setuid after a system update, so regular user accounts can startx.
Losing the install icon on the liveUSB wasn't convenient... But once I knew the command name, I was all set on that.
I was a bit surprised that just setting up openbox could interfere with the icons on the other WM sessions though.
But actually I AM doing so for fun. I find it fun making my computer do things the way I want. And for some reason graphical login screens always bugged me. And avoiding them is"fun".
It was a bit of a pain disabling the installed DM {aka slim} because this:
doesn't work anymore, and the new syntax, that the error message informed me of, sounded like something was changed to work with systemd. But whether that's the case or not. I wasn't going to waste time learning the new syntax of a command I most likely won't need again for years. It wasn't all that hard to manually create the"stop" symlinks. and purge any remaining start symlinks... In fact it was fun. Because I'm tired of just changing the default target symlink, for one that points at the runlevel3 target.
Anyway, what's installed is working well enough. But since it's my goal to convert this antiX-15 into a rolling release by reconfiguring the sources to use testing. I think I'd be better off doing that before I install the kitchen sink. __{{emoticon}}__
I mean I might be adding a few big packages. Or perhaps I should say packages with big dependency lists. So rather than installing everything I want, and then make apt-get reinstall the testing versions, my next task is the sources lists
After which I suspect I should use:
instead of just:
Then I can add the rest of my preferred applications...
In any case I'd like to thank you for the helpful suggestions. I did get that you don't see the point of my using openbox. But I noticed that didn't stop you from helping me do it.
THANK YOU!
Nope, I'm square pegging a square hole... It's just that ANY Display manager will try to redirect me to the round hole... Once the {expletive deleted} DM is properly disabled, I don't have any problems with session management. Xorg knows how to listen to what I want it to do. (Once I get that durned DM to stop telling it to do something else.) Incidentally I only get that wicd pop-up when I use the liveUSB's DM to start openbox. I don't get it with the antiX I just installed to the hard drive.skidoo wrote:wicd permission box is triggered by the freedesktops.org"xdg autostarts" built into debian.Though everytime I start openbox that way I get a pop-up {sudo based} password prompt to give wicd access...
By default, antix session management suppresses (or silently handles) details such as this
and by insisting on square-pegging a round hole, you're choosing to forego one of great benefits antix provides -- easily customizeble session management.
I've been using openbox this way for years now, I've never needed to fuss with obconf
So, after installing openbox (and obconf? and lxpanel?) ...yeah, you have your work cut out for ya.
Yep, no install icon on the desktop. Yep, no customized autostarts applied, and after you've installed additional debian packages...
...possibly unwanted extra apps autostarting each session unless you weed them out
(weed, meaning, check post-install whether installation of a given package has created ~/.config/autostart/ and populated it with a .desktop file)
along with a dozen or so other details you'll need to configure (and monitor, on an ongoing basis).
I add lxpanel because it adds a reasonable task bar. And it comes with another menu, which can be handy if I'm using a distro that won't auto-update openbox's menu. Though I seldom use the menu for anything other than logging out. I occasionally use it to figure out the command names of anything I don't have keybindings for.
But then I usually call it from the command line anyway
Once I'm booting to runlevel 3 and using startx, I've never had any problems with any installed applications starting themselves. Not on opensuse, not on mageia, and not on my old rolling release configured antix-11 which was using the debian testing repos to stay up to date until I switched to a new PC and decided I wanted antix on it.
Though I will admit I occasionally have to set Xorg back to setuid after a system update, so regular user accounts can startx.
Losing the install icon on the liveUSB wasn't convenient... But once I knew the command name, I was all set on that.
I was a bit surprised that just setting up openbox could interfere with the icons on the other WM sessions though.
I'd like to think so... I knew it could be done in JWM, Puppy Linux taught me that. Though I no longer remember exactly how, I just have a vague memory of finding it a pain to do. I never learned how to do that with iceWM or fluxbox. So since my goal is to get back to using my computer, instead of learning to configure unfamiliar window managers...nuff said...
==================
You can setup for your favorite keybinds to be recognized in iceWM and/or in fluxbox and/or in JWM, so I (still) can't understand the merit in opting to roll openbox.
I'm using essentially the same openbox configuration on 3 different distros on each of my computers. I occasionally fire up a different WM or even a DE for a change of pace. But I like openbox better.If doing so were a"for fun" or"simply academic" excercise, that's fine. (That's great!)... but obviously that's not the case.
But actually I AM doing so for fun. I find it fun making my computer do things the way I want. And for some reason graphical login screens always bugged me. And avoiding them is"fun".
It was a bit of a pain disabling the installed DM {aka slim} because this:
Code: Select all
update-rc.d -f slim remove
update-rc.d slim stop 20 2 3 4 5 .
doesn't work anymore, and the new syntax, that the error message informed me of, sounded like something was changed to work with systemd. But whether that's the case or not. I wasn't going to waste time learning the new syntax of a command I most likely won't need again for years. It wasn't all that hard to manually create the"stop" symlinks. and purge any remaining start symlinks... In fact it was fun. Because I'm tired of just changing the default target symlink, for one that points at the runlevel3 target.
Anyway, what's installed is working well enough. But since it's my goal to convert this antiX-15 into a rolling release by reconfiguring the sources to use testing. I think I'd be better off doing that before I install the kitchen sink. __{{emoticon}}__
I mean I might be adding a few big packages. Or perhaps I should say packages with big dependency lists. So rather than installing everything I want, and then make apt-get reinstall the testing versions, my next task is the sources lists
After which I suspect I should use:
Code: Select all
apt-get update && apt-get dist-upgrade
Code: Select all
apt-get update && apt-get upgrade
In any case I'd like to thank you for the helpful suggestions. I did get that you don't see the point of my using openbox. But I noticed that didn't stop you from helping me do it.
THANK YOU!