Search Results for 'boot from iso'

[Forum Admin rokytnji]

I hope I contributed to the initial question:

You did A VERY GOOD JOB in my view. My reason for reposting. Installed 32 bit AntiX 19.2 on 32 bit XP era atom clamshell netbook.

harry@biker:~
$ cd Isos
harry@biker:~/Isos
$ ls
AntiX                      Bohdi               Multiboot
antiX-19.2.1_386-base.iso  exton_e17_debian11  MX
antiX-19.2_386-full.iso    Knoppix
harry@biker:~/Isos

Hardware Sounds like a perfect fit for Brazil.
Still dealing with family company here.

I will keep testing antiX 32 bit till when ever I am given no choice to do so any more.
Good thing I grok Puppy, almost Slitaz, and other stuff I have not tried yet.
The have not tried yet is. Because? Lack of interest.
Bohdi and Exton are for a E17 itch.
Exton does not build much on 32 bit. I am just guessing though.
Knoppix either. MX still does though.

MX 15 32 bit was what I blew away on that clamshell netbook I just posted about.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

I am sorry to say this, but I still haven’t done anything for translations. First I wanted this to work properly.
I have included both scripts inside one file. Changes:
– More help dialogs but still very little info.

– Now the program will generate a Packages.gz file that will contain ALL info about all your downloaded packages after each download.
– A new (experimental) fiture will enable you to add the repo folder to your sourcelists, so you no longer need to install with dpkg -i,
but now you can install all packages from the repo using the apt install command
(that means that synaptic will also pick your local repo packages and you can install from there).

– DOWNLOADING DEPENDENCIES: Now the script requires apt-rdepends and dpkg-dev (only for downloading packages, not for installing).
If the net is available, it will ask you if you want to install them when trying to download packages.(not working as well as expected yet).
1.1. After downloading each package+dependencies, the program will update the Packages.gz file inside the download folder.
This contains the list of all your downloaded packages so that apt can manage them.

– INSTALL FROM LOCAL REPO: Once you select the folder that contains your local repo,
Add it to the sourcefiles (button) and you will be able to install any package inside your repo folder from synaptic,
apt (commandline), etc. Also, all downloaded “programs” (done with this tool) can also be easily installed using the same program (2. Install Apps).
1.2. Please remember to 3. Remove local repo from sources when you are done installing packages.
This is recommended but shouldn’t break anything if not done (only some eror message might come up).

You can now keep ALL dowloaded packages in the same folder,
as you will be able to use this app to install the programs you want
(and not all the ones inside the folder at the same time).

Feedback, please.

Starting this thread because this netbook is slowing me down. Plus. Just letting Xecure know my bro in law will be stopping by heading back to AZ from TX and that is gonna slow me down also.

Short description of woes so far on that n270 clamshell netbook.
antix 19.2 Full iso. Fresh install. Md5sum checks out. Install was no drama except for running wifi live. Will come back to that later.
I started out with soft block in rfkill on every boot.
Took me hours before I figured out disable conman on startup in AntiX control Center.
That cured soft block.
Discovered soft block using ceni.

Next issue. For what ever reason. I fought ceni for a bit connecting.
Inxi says wlan0 rt73 driver and me checking firmware showed rt firmare was loaded also < .ko >
Finally connected.

In the meantime. I am spending time poking and hoping with
sudo dmesg | tail
Wlan0 looks OK there.
sudo dmesg | grep wlan0
Readouts look Kosher.
ping 8.8.8.8
`ping 1.1.1.1

in antix control center > maint > Network assistance throws out good connection but google.com does not < empty readout >

Strange. Open Dillo to a blank page. It shoulda hit the forum. I am really confused now.
Back to inxi. wlan0 shows up. Conky shows wlan0 graphs < won't if not connected >
All my other wifi antix computers . No problem. So not router.

I will come back later Xecure to this thread to give feed back on your script. wlan0 has occupied me for hours all night.
So I am giving up and hooking a land line later on after bro in law leaves my place in a few days.
So I can post better details on enabling hardware on this clam shell netbook while also giving feed back on .sh script by xecure.

Got lot’s of troubleshooting practice on the 1st 32 bit gear I located. Funny part. Making usb. No drama. Boot. Got the space bar message for undefined video mode. Easier for me wait a few seconds instead of inputting somethoing. Vesa won’t offer 1024×600 anyways in choices < I checked >

Well. That is it from me for a few days. Bro in law contacted me after I decided to do this. Sorry. Screwed up limitations of a small team.
Member has a other chore. Has to drop antiX testing. For a bit. We may be slow. But we are methodical. This post made on my IBM T430 AntiX 19 install.

Hence why the wait on what I tried with code tags.

• This topic was modified 2 years, 9 months ago by rokytnji.
• This topic was modified 2 years, 9 months ago by rokytnji.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Member PDP-8]

Hi Bob – glad to see you are making progress..

To be sure, like Brian says, this is a tool of convenience, and not a recommendation for antiX or MXlinux to change their norms of operation. As a relatively recent project, it looks like they are adding distros quite frequently. Note that my interest was solely to play with AntiX and MXlinux and a small handful of others. So as always, ymmv when it comes to 3rd party booters and support. Normally I have no need for multibooters.

Both antiX and MXlinux work beautifully from their iso’s for me in a non-multiboot situation on relatively modern hardware as is. And of course being a usb stick persistence guy, their tools are second to none! Not to mention remastering, live snapshots – the whole 9 yards. My jaw drops every time I use either one.

Re – Windows utils.. I know where you are coming from, but perhaps you may be called upon to help out some that are not as well enlightened. This case for example:

“Hey Bob – I just used my 256gb card a few times, and now Windows wants me to reformat it, but when I do, it is only a 2gb card!” Heh, the standard windows formatter is fooled.

RUFUS, however, digs DEEPER than the standard Windows formatter to find out the true capacity, and when using Rufus to format as “non bootable” instead of doing iso work, the stick is back to normal. Friend buys you a beer. 🙂

Realize that sticks and cards are only targeted towards Windows / Mac primarily, even though Linux can certainly use them, there are some tricks like the above when it comes to SD cards! (maybe especially important if you use Rasberry Pi’s, or other sbc’s with sd-cards the seemingly get corrupted.)

One oft recommended tool is from the guys who set the standard in the first place, the SD-Card Association – they provide a tool that goes beyond Windows / Mac / linux formatters since it can actually reprogram the internal chip controllers! Linux has no access to that:

https://www.sdcard.org/downloads/formatter/

Unfortunately, no direct linux support. But hey, only this tool will correct faulty controllers, in addition to just filesystems. So there’s that.

Just saying – it’s an option for those who see a use for it.

[Moderator BobC]

Ventoy is better than the others in that it’s open source, and creates a setup that allows you to load any supported .iso from a normal drive. So far I have one that comes up saying it’s unsupported. My respins of antiX come up as supported, but I haven’t tested them, yet.

I have found one system that can bring up the Ventoy boot system, but can’t actually bring up the OS’s to boot them, so it’s not flawless, but at least they seem to have a good concept.

[Moderator Brian Masinick]

I already ran a search and found each of the tools that people have wrote about here.

I’ll try a few more searches – and I can poke around in the days ahead – to see if anyone else has written any scripts that can be freely used (and visibly examined) to see how these techniques have been implemented.

However Ventoy works, it must be some kind of large file system or container that accepts input sources (and if it’s “smart”, evaluates those sources to make sure they are “supported” by the tool), then adds the next source to the list of items in the collection. If they are all ISO images or other valid computer system formats that it recognizes, it also provides some mechanisms to choose from them, so that you can either access one of them or run it live.

There is certainly more than one way to do this (and I imagine theirs is “proprietary”). If it works, that’s great. For me, without getting into either the code or the product description, I have no idea how they actually implement their solution, but it has to be something that maintains the integrity of the installable, boot-able instance.

Glad it works for you! 🙂

--
Brian Masinick

[Moderator BobC]

Brian,

Thanks for your input. The Ventoy is doing pretty well, now that I got past the install and reliability of writing issues. Admittedly I got past that by installing from Debian, but my main antiX system has a lot of additional packages which could be causing the problems, so it may not really be a problem on stock antiX.

Copying .iso files to the Ventoy could not be easier. Once I setup the mount with the right authority, I was able to copy files via mc, Spacefm, or even by directly downloading via torrent into subdirectories. They all come up on the boot list and they are lightning fast from SSD.

I am now going through each of my machines and consolidating all of my .iso files onto this drive.

The script needed:
What I need is an automatic install script for antiX. I have the feeling this already exists, somehow, somewhere, and maybe if I can find one, I can tweak it. Still need to play with persistence. That would be great to be able to use for testing sometimes.

[Moderator BobC]

Brian,

The purpose of the thread is to get a way that I can store a large number of .iso files of different distros (including primarily antiX) to be able to boot and run live or install any of them very quickly on any of my machines from a high speed, high capacity USB 3.0 SSD drive, which can hold 100 distro/versions and install antiX in under 5 minutes.

No, I don’t WANT to run Rufus, or anything else MS related unless there is something it does that I literally CANNOT do under Linux. Yes, I still have a few MS partitions I could boot if I wanted to, but I don’t want to.

I’m absolutely fed up with the arrogant MS attitude that I am operating my computer for THEIR benefit. After the last go round of buying virtual licenses for Win7 for my Core II sysytems, registering them with MS at the time, and then years later they tell me they are illegal copies, and as such after spending 2 days straight running to install them with all the updates, they then told me to buy new licenses. I was a great customer for them for years, and they made many thousands of dollars off me, but they have screwed me over one time too many. I have had it with the MS nonsense, and will NEVER pay them another penny for anything whatsoever.

My computers are here to do what ***I*** want them to, and if not I will power them down.

Back to the thread purpose… I’m trying to make it quick and easy to setup clean backups (via snapshot and live USB maker) and/or test environments from .iso files that I can load up in a flash as needed…

[Moderator Brian Masinick]

Regarding the use of Rufus or some other tool that runs either primarily or exclusively on some proprietary OS:

I NEVER use such a tool. 100% of the time, a SUPER powerful (and equally DANGEROUS tool if not used properly), the dd command is more than able to clean, reset, and install software. You can put ZEROs on a device, random sequences, or ISO images on a device, ranging from some ancient tape device, to a modern disk drive, removable USB device.

Moreover, both antiX and MX Linux each have a powerful USB tool, actually a set of tools. I recommend using them, either from the USB device itself, or from a running system (either installed on disk or removable USB). There are Format USB and Live USB Maker tools, plus the command line dd tool available. Read about them and examine them. If you have a spare USB device and an environment where you can experiment (and back up resources available), get to know all of these tools and do not be afraid to use them. Feel free to ask more questions.

I haven’t really done much with multi-boot from USB devices, but the point remains – dd is able to append information with the right choice of arguments – for instance the output redirection >> will APPEND, while > will only overwrite whatever device is specified with the of= argument.

https://www.linuxbabe.com/apps/create-multiboot-usb-linux-windows-iso has some useful information and the tools discussed do seem to be helpful.
In the long run I’d rather know the format, technique and use lower level tools myself; then I’m certain to understand it.
dd will do the job; what I do not know for certain is whether there are headers or indexing information required to identify each multiple image or if the system itself will (as expected) locate each image as long as they are appended (not overwritten) each time you add to an existing media source. My fundamental belief is that if you append them properly they should work.

• This reply was modified 2 years, 9 months ago by Brian Masinick.

--
Brian Masinick

[Member PDP-8]

Hmm. lots of variables so hard to diagnose from this distance..

Good stick right? Maybe blast it clean with gparted with a default filesystem for the whole stick and try again. (Tip – even if you don’t like Windows, the Rufus utility just by itself when using the “non bootable” filesystem option, has shown to me one of the greats in detecting true drive capacity and blasting out crud from sticks that have seen a lot of bad road…)

Sure, go ahead and use a filesystem structure of your iso’s. What I’d probably NOT do, is make a directory called ventoy on your own, just to avoid any confusion to ventoy itself. 🙂

No automount when using the ventoy install script. Covered.

After install, take a look at the stick with gparted. You’ll see one HUGE partition, that has no label, and is exFAT. The secondary partition at the end of the stick IS labeled “Ventoy”. OK.

The trick here is not to get excited about the secondary partition and try to put iso’s into the “Ventoy” partition. It’s the first one you want to slam iso’s into, and that one has no label. Thus, in a file manager, it would probably show up as generic, like /dev/sdX1 (where X is a/b/c/d whatever)

Then again, depending on distro you are building it on, it may show up in /media rather than the canonical /mnt …..

Repartitioning – one thing I did try just to prove a point, was that immediately after building the Ventoy stick, it was super easy to just let gparted reformat that huge 1st un-labeled partion from exFAT to ext3/4. FAT32 worked fine. In addition to isos, sure, use this partition for persistence too.

I suppose worst case, you could build it on the Windows gui utility, and that brought up antiX and MXlinux fine too.

I’d also maybe prove this all with a usb-stick first, rather than use your SSD just to cut out that possible variable.

Just some thoughts…

[Moderator BobC]

Not sure why it was dismounting while trying to copy .iso files to it. I created a folder /media/ventoy and added the SSD drive to my fstab.

I was able to boot and run a couple of the distros, but haven’t tried persistence yet.

[Moderator BobC]

I’m still having problems formatting and loading.

1. I’m having problems writing the .iso’s to the drive. It seems to fail and unmount. I’m not sure where to look for error messages for clues. I have tried SpaceFm, ROXFiler, and XFE. I tried the EXFAT default, XFS, Ext4 and Ext2. Right now I’m trying NTFS, but had the same problem writing to it as the others.

2. Mounting is trouble. I would like to be able to mount it the same each time. I wish I could get it to mount at the same place and would work reliably to copy the .iso files to it.

Once I get it working, I’ll do more testing booting and running from it.

So, how did you get it working? What is your setup?

[Moderator BobC]

The key I think was to turn off automount and reboot, not be running SpaceFM, and reformat to not EXFAT after it was created, BEFORE loading the .iso files.

I haven’t figured out persistence yet.

It would be cool to have each .iso in it’s own directory, and that way any associated files it would need could be there with it. But then again, I have to see. Maybe that won’t be an issue.

I am using this with a 256 gb fast SSD on a USB 3.0 mount. It’s quick enough to use for testing how to do simpler things on a USB 3.0 capable PC.

[Member PDP-8]

Ah, yes – be sure to disable drive auto-mounting or it will get confused half-way through the process as antiX mounts it half-way through the process. 🙂

I took the long way around – went into antiX control center, disabled auto-mounting of external devices / usb devices, and rebooted.

Then performed the Ventoy install to the target drive. Now it finished properly.

Returned to the antiX control-center, and re-enabled automounting since I prefer that for a desktop.

Really nice that one can reformat the primary Ventoy partition where you lay the isos on to be anything you like, not just the default exFAT. Or use commandline switches for gpt vs mbr.

I’m liking it so far..

[Moderator BobC]

It seemed to install correctly, but was very funky. It keeps mounting and dismounting the drive, and I was able to mount it manually, and copy iso files to it, but when it boots, it says there are none there. If I can get it mounted, they appear to be there, but there is something very wrong with the mounting/dismounting.

I will try again on a completely stock system.

There was no .deb, so I might think its installed right, but maybe it isn’t? I looked at trying to do an install from source and that looked impossible for me.

[Member marcelocripe]

Dear colleagues,

I will post the tests with antiX 16.3 64 bits full, I will not test the antiX 13.2 version, it does not make sense to use an older operating system than antiX 16.3, since it installs the base of Debian 8 or Debian 9, I will do the installing Debian 9.

Boot with the bootable USB stick antiX-16.3_x64-full.iso, the video did not load in graphic mode with the selection of the antiX-16.3 x64-full option (21 December 2017), after restarting the computer I selected the Safe video option Mode and the video loaded successfully and the image quality is perfect, there are no ghosts or delay in the response. The command below was applied before installing antiX 16.3:

————–

Caros colegas,

Irei postar os testes com o antiX 16.3 64 bits full, não irei testar a versão antiX 13.2, não faz sentido utilizar sistema operacional mais antigo que o antiX 16.3, haja vista que este instala a base do Debian 8 ou Debian 9, irei fazer a instalação do Debian 9.

Inicialização com o pendrive inicializável com a ISO antiX-16.3_x64-full.iso, o vídeo não carregou em modo gráfico com a seleção da opção antiX-16.3 x64-full (21 December 2017), após reiniciar o computador selecionei a opção Safe video Mode e o vídeo carregou com sucesso e a qualidade da imagem está perfeito, não há fantasmas ou atraso na resposta. O comando abaixo foi aplicado antes da instalação do antiX 16.3:

demo@antix1:~
$ inxi -Fxz
System:    Host: antix1 Kernel: 4.4.10-antix.1-amd64-smp x86_64
           bits: 64 gcc: 4.9.2
           Desktop: IceWM 1.3.8
           Distro: antiX-16.3_x64-full Berta Cáceres 21 December 2017
Machine:   Device: desktop System: Semp Toshiba Informatica Ltda product: STI v: Rev. 10/00 serial: N/A
           Mobo: Semp Toshiba model: STI 910090 v: 4.1 serial: N/A
           BIOS: Phoenix v: 6.00 PG date: 03/25/2007
CPU:       Single core Intel Celeron (-UP-) 
           arch: Netburst Prescott rev.9 cache: 256 KB
           flags: (lm nx sse sse2 sse3) bmips: 5056 speed: 2528 MHz (max)
Graphics:  Card: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro]
           bus-ID: 01:00.0
           Display Server: X.Org 1.16.4 driver: vesa
           Resolution: 1024x768@0.00hz
           OpenGL: renderer: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
           version: 3.0 Mesa 10.3.2 Direct Render: Yes
Audio:     Card VIA VT8233/A/8235/8237 AC97 Audio Controller
           driver: snd_via82xx port: cc00 bus-ID: 00:11.5
           Sound: ALSA v: k4.4.10-antix.1-amd64-smp
Network:   Card-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
           driver: 8139cp v: 1.3 port: fc00 bus-ID: 00:09.0
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
           Card-2: VIA VT6102 [Rhine-II]
           driver: via-rhine port: c800 bus-ID: 00:12.0
           IF: eth1 state: down mac: <filter>
Drives:    HDD Total Size: NA (-)
           ID-1: /dev/sda model: SAMSUNG_SP0842N size: 80.0GB
           ID-2: USB /dev/sdb model: Drive_SM_USB20 size: 2.0GB
Partition: ID-1: / size: 1.5G used: 31M (3%) fs: overlay dev: N/A
Sensors:   System Temperatures: cpu: 40.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 150 Uptime: 40 min Memory: 171.3/1938.7MB
           Init: SysVinit runlevel: 5 Gcc sys: 4.9.2
           Client: Shell (bash 4.3.301) inxi: 2.3.53

demo@antix1:~
$ inxi -G
Graphics:  Card: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro]
           Display Server: X.Org 1.16.4 driver: vesa
           Resolution: 1024x768@0.00hz
           OpenGL: renderer: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
           version: 3.0 Mesa 10.3.2

demo@antix1:~
$ lspci -v
00:00.0 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
	Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
	Flags: bus master, 66MHz, medium devsel, latency 8
	Memory at f4000000 (32-bit, prefetchable) 
	Capabilities: <access denied>
	Kernel driver in use: agpgart-via

00:00.1 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
	Flags: bus master, medium devsel, latency 0

00:00.2 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
	Flags: bus master, medium devsel, latency 0

00:00.3 Host bridge: VIA Technologies, Inc. PT890 Host Bridge
	Flags: bus master, medium devsel, latency 0

00:00.4 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
	Flags: bus master, medium devsel, latency 0

00:00.7 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
	Flags: bus master, medium devsel, latency 0

00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge (prog-if 00 [Normal decode])
	Flags: bus master, 66MHz, medium devsel, latency 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000b000-0000bfff
	Memory behind bridge: fb000000-fcffffff
	Prefetchable memory behind bridge: f0000000-f3ffffff
	Capabilities: <access denied>

00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 20)
	Subsystem: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
	Flags: bus master, medium devsel, latency 32, IRQ 11
	I/O ports at fc00 
	Memory at fdfff000 (32-bit, non-prefetchable) 
	[virtual] Expansion ROM at 7bf00000 [disabled] 
	Capabilities: <access denied>
	Kernel driver in use: 8139cp

00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) (prog-if 8f [Master SecP SecO PriP PriO])
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7211
	Flags: bus master, medium devsel, latency 32, IRQ 11
	I/O ports at f800 
	I/O ports at f400 
	I/O ports at f000 
	I/O ports at ec00 
	I/O ports at e800 
	I/O ports at e400 
	Capabilities: <access denied>
	Kernel driver in use: sata_via

00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7211
	Flags: bus master, medium devsel, latency 32, IRQ 10
	[virtual] Memory at 000001f0 (32-bit, non-prefetchable) 
	[virtual] Memory at 000003f0 (type 3, non-prefetchable)
	[virtual] Memory at 00000170 (32-bit, non-prefetchable) 
	[virtual] Memory at 00000370 (type 3, non-prefetchable)
	I/O ports at e000 
	Capabilities: <access denied>
	Kernel driver in use: pata_via

00:10.0 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7211
	Flags: bus master, medium devsel, latency 32, IRQ 10
	I/O ports at dc00 
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd

00:10.1 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7211
	Flags: bus master, medium devsel, latency 32, IRQ 10
	I/O ports at d800 
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd

00:10.2 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7211
	Flags: bus master, medium devsel, latency 32, IRQ 11
	I/O ports at d400 
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd

00:10.3 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7211
	Flags: bus master, medium devsel, latency 32, IRQ 11
	I/O ports at d000 
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd

00:10.4 USB controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20 [EHCI])
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7211
	Flags: bus master, medium devsel, latency 32, IRQ 11
	Memory at fdffe000 (32-bit, non-prefetchable) 
	Capabilities: <access denied>
	Kernel driver in use: ehci-pci

00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
	Subsystem: VIA Technologies, Inc. DFI KT600-AL / Soltek SL-B9D-FGR Motherboard
	Flags: bus master, stepping, medium devsel, latency 0
	Capabilities: <access denied>

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device b010
	Flags: medium devsel, IRQ 11
	I/O ports at cc00 
	Capabilities: <access denied>
	Kernel driver in use: snd_via82xx

00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7211
	Flags: bus master, stepping, medium devsel, latency 32, IRQ 10
	I/O ports at c800 
	Memory at fdffd000 (32-bit, non-prefetchable) 
	Capabilities: <access denied>
	Kernel driver in use: via-rhine

01:00.0 VGA compatible controller: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01) (prog-if 00 [VGA controller])
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7211
	Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 10
	Memory at f0000000 (32-bit, prefetchable) 
	Memory at fb000000 (32-bit, non-prefetchable) 
	[virtual] Expansion ROM at fc000000 [disabled] 
	Capabilities: <access denied>

demo@antix1:~
$ cat /proc/cmdline
vga=788 lang=pt_BR tz=America/Sao_Paulo quiet splash=v disable=lx nomodeset xorg=safe

*****
My observations::

The antiX 17 and antiX 16 menus are more beautiful and much more readable (easier to read) than antiX 19.2, is it possible to make the newer version look like the previous ones?

Amazing! According to Conky 103MB of RAM, antiX should stay that way, requiring as little processing and memory consumption as possible.

*****

Then I’ll post the result after installing antiX 16.3 64 bits full.

See you …

marcelocripe

————–

*****
Minhas observações:

Os menus do antiX 17 e do antiX 16 são mais bonitos e muito mais legíveis (fáceis de ler) do que do antiX 19.2, por acaso é possível deixar a versão mais nova com a aparência dos anteriores?

Que incrível! Segundo Conky 103MB de memória RAM, o antiX deveria continuar assim, exigindo o menos possível de processamento e de consumo de memória.

*****

Em seguida postarei o resultado após a instalação do antiX 16.3 64 bits full.

Até mais …

marcelocripe

• This reply was modified 2 years, 9 months ago by marcelocripe.