Category Archives: Arch Linux

mplayer and screen, in a fight to the death

Edit, 2011-01-01: I should probably apologize at this point, because a clean and default reinstall made this problem disappear. Apparently it was a problem with my system configuration, somewhere. Sorry for the false alarm. :oops:

It took me long enough, but I finally ran aground on that quirk between screen, mplayer and the framebuffer in Arch Linux.

I’ve had people e-mail me or leave questions here asking how to get around screen’s stranglehold on the framebuffer.

For the uninitiated, you can duplicate this … behavior … by building an Arch system, forcing it into a non-default framebuffer dimension, starting screen, then starting mplayer.

Just be prepared to cut the power on your machine, because mine locks completely each time.

Outside of screen though, mplayer seems to be working fine. It will even seek out the framebuffer on its own, without the -vo fbdev flag, and play a movie normally.

But as for fixing that lockup … ?

To be honest, I don’t know. I need to experiment a little more. Right now the only way I know to get both screen and mplayer working well together is to include Xorg.

I know what you’re thinking: You’re thinking, “What … ?” It’s nutty, but if I start screen in a terminal emulator from within X, then start mplayer from there, I can force mplayer to the tty1 on the framebuffer.

Which is so completely bizarre as to be absolutely unuseful. I’ve heard of some wacky solutions to weird problems, but that is not a solution. Heck, that’s not even an option. But what can I say: It works.

And when I think about it, it does lend itself to a few interesting permutations. … :twisted: Stay tuned. … :D

Back to Openbox

I became a little disenfranchised with my pretend Windows XP Classic desktop almost a month ago, and switched gears slightly.

Soon afterward I realized my disappointment with the desktop was rooted in IceWM, and not just in the theme I had built up around it. So I’m back to Openbox now.

And because I was feeling a little nostalgic, I put that together to mimic a desktop I was using about four years ago, also at Christmas. The machine has changed, the distro is different, but the look is similar.

I still have a little bugs to iron out, here and there. I haven’t relied singularly on Openbox for the better part of a year, and there are some shortcuts and configurations to learn.

And it has been even longer since I tinkered with conky. I know: What I have there is rather primitive, compared to what it can do.

But this will suffice for now, and should keep me fairly busy over the next few days. My real-world obligations peak today and then I should be able to coast into a nice, long, well-deserved end-of-year holiday. And I have a few things planned. :twisted:

Stay tuned. ;)

A companion for the CLI

Now this is something very very cool.

That’s CLICompanion, and probably one of the coolest tools for Xorg-plus-CLI I’ve seen in a while. At least since screen-plus-yakuake.

This is great if you have a lot of console commands, you’re tired of working with a shell history, or you’re trying new applications that need long strings of flags. Or you have a library of favorite commands, or you’re comparing configuration files, or … or … or …

You get the idea. If you like the idea of command-line life, but you prefer a full graphical desktop, this is a good starting point.

If you’re new to console commands, this will give you a two-click library to run them from, plus a gaggle of tabbed interfaces to experiment with.

It’s not purist, you’re not taking much of a stand for minimalism and it’s not going to win you any geek points from the office IT staff. Those guys and girls will always know more than you, and they won’t let you forget it. :twisted:

But it’s ridiculous fun, easy as pie to manage and doesn’t require much more effort beyond point-and-click to get started.

Get to work importing your library of favorite commands. This will probably make them a little more fun again. Or at least give you another tool in your ascension to text-only Nirvana. :D

P.S.: That’s the AUR version, which seems to hide the executable in an odd place — /usr/share/applications/clicompanion/clicompanion. Or at least it was odd for me. I believe there is an Ubuntu version; no hints on where that executable is. :)

pktstat, and a really big list

Quite by accident today I stumbled across one of the biggest lists of Linux administration tools I’ve ever found. Technically it’s in French, but I can promise that won’t be a hindrance.

It’s neatly arranged and split into groups in the form of an interactive mind map, but I’ve already exported it, converted it to plain text, stripped out the titles and spliced them with my own list in hnb.

There must be hundreds there — not all of them console tools of course, but certainly more than enough to keep me busy for a long, long time to come.

I’ve already found one I like quite well — a small network monitor called pktstat (yes, I know that link doesn’t work).

I’ve run through a dozen network monitors in the past year or so, and I keep both slurm and iftop on my machine just for times when I want to see who’s in the area.

pktstat has a slightly different arrangement but does you the favor of capturing a little information about each transfer, so you have a better clue as to what’s what.

The source code might be a little tricky to find; there’s an entry in AUR for pktstat but downloading the source code yields a 404. Luckily it’s mirrored in a dozen other places; Google can help you out here.

So, armed with both pktstat and a list of about 400 new applications to try out, I think I am ready to wade into the new decade. :shock:

Twenty-ten: The picks of the litter

Two-thousand-and-ten is almost over. I’ve done more than my share of distro-hopping this year, and not because of a fickle character, but because of a curious streak.

This year's judge and jury.

That curiosity is bent toward very low-end computers though, and it’s not enough to me to just show a pretty desktop at 150Mhz if the overall experience feels like your head is being pressed through a bowl of mashed potatoes.

To that end, some distributions stick out in my mind more than others this year, as good options for low-end machines. A few more I tried are just good options, for any kind of machine.

And some I mention because they are ingrained in my lifestyle now. Maybe I didn’t discover them this year, but in 2010, they became essential to my workflow.

So I have a few end-of-year “notes.” These are not awards so much as recommendations, since I am hardly qualified to award anybody anything. :|

The wake-up call: KolibriOS. In a world of multi-DVD distros, of thousand-dollar operating systems in a half-dozen flavors, of operating systems that require multiple processors and double-digit gigabytes of memory to use, KolibriOS hits you like a ball-peen hammer squarely in the forehead.

KolibriOS: Pocket-sized powerhouse.

It’s hard not to find something to like about a full-featured desktop replete with games, applications, hardware tools and even networking support that sits in a meager 1.44Mb of space.

And thus it’s hard not to include it in a list of things to love about 2010, considering that KolibriOS in its latest rendition is a stern lesson in software design and how to put together a truly ultralight desktop.

Granted, this is minimalism to the nth degree, lightweight to the point that you can’t conceivably pit this against any other “modern” desktop without feeling almost foolish.

But let’s be frank: Why is lightweight and conservative software such a crusade — in Linux and in other operating systems — when KolibriOS stands as such a stark counterpoint?

Why does the search for a lightweight operating system begin and end with racks and racks of desktop environments, window managers and alternative desktops, and page after page of lighter upon lighter applications, toolsets and support libraries?

Why is it such a carnival to say out loud, “I have a machine that dates back a decade, but still works great and I’d like to find modern software that will run on it”?

I’ll let you decide, but deep down I think we all know that software demands push hardware upgrades, and upgrades in turn allow for bigger, fatter software. In that way, everybody makes money.

It’s a vicious circle, but it’s hard to reach any other conclusion when I can hold up a decades-old floppy with a complete operating system on it. It’s not for lack of skill or ability or time or even desire.

KolibriOS is proof that it’s possible. Just as much as it is proof that perhaps everyone else is going about things the wrong way. Probably so they can take your money. :evil:

A chicken in every pot: Slitaz base. I’d love to say that I have a Slitaz CD perched at the ready, any time I need to jump into a live environment on any machine in the house.

But that would be a half-truth, since I don’t use the standard Slitaz ISO to do that. I stick to the base version.

Slitaz base: What it looks like inside your computer, with the lights turned off.

You won’t like it. You’ll be dropped at the command line without a stitch of help from a mouse or a pointer, and feel rather cold and naked and alone. Welcome to the underbelly of your computer.

But you’ll get there on a meager 12Mb of RAM or less, meaning that this disc can get almost anything with a working CD drive up and running and with a minimum of resources. It’s amazing.

And what you do from there is up to you. Install Slitaz, or use that hovering OS to transfer files across a USB port (or entire operating systems), or repair or recover a dying hard drive.

True, there are other distros that offer these same tools on bigger and better and more complete CDs, but the resources they will demand and the time it will take to get them moving is likewise bigger. And not necessarily better.

So for a lightweight tool that I keep coming back to, and for a full-featured console environment that will fit inside a sliver of memory, it’s tough to beat the Slitaz base version. I can think of no higher praise. :|

Knight in shining armor: Clonezilla. Clonezilla is crack for the distro hopper.

Clonezilla: So yummy, it should be illegal.

Clonezilla is going to eat your life away in small pockets, leaving you with dozens of archived systems, waiting on an external hard drive.

Clonezilla will save your life, when calamity strikes.

Clonezilla makes it too easy to backup and restore entire systems, and isn’t afraid of anything.

Clonezilla turns on a dime, needs less than the average memory available to a Pentium III to get started, and even comes in a i486 flavor, for weirdos like me.

Clonezilla boots from USB, boots to memory, boots to anything with a keyboard and an LCD attached, and won’t quit until you tell it to.

And what it does is free up your life to think about other things. New things. Fresh things. Knowing full well all the time that you can always go back to your old way of thinking.

Technically it’s not an operating system, so you can throw stones if you want. But if you’ve tried it, and you know it, you won’t make that big of a noise if I include it here. You’re a believer. You know you are. :twisted:

Tried and true: DSL. When I peel away the frustration and dismay, I have to admit a solemn reverence for a distro that manages so many convolutions in setting up this computer, and doing it so well, and being about a year or two out of development.

DSL, even at this late date, does things for ancient hardware that my best efforts still can’t. Maybe I’m just not well educated enough (no CS degree on my resume, pal). I am more than willing to admit my ignorance.

DSL: The ghost of Christmases past.

But the 60 seconds it takes this 5-plus-year-old distro to start, configure and announce its presence with authority are more than enough to spellbind me. Audio, video, network and peripherals, all moving at a good clip and with no sense of weariness.

It’s almost infuriating. I’ve been inside and out of the machine, probed its inner recesses and researched everything I can think of in terms of arranging and configuring. And an out-of-service, 50Mb distro beats me, with one hand tied behind its back.

Touche, sirs. For that, a small tip of the hat. I wish I could do as well, left to my own devices. :(

Service with a smile: Debian Lenny. I haven’t mentioned it much, but the Debian server I built to run at 133Mhz has convinced me to keep an otherwise superfluous computer and a network card I thought unworking. And that’s saying something.

Debian: The magical stuff that binds us all together.

Given the chance, Debian will perform back flips at the snap of a finger, and provided you don’t overwhelm a machine — of any architecture — you’re more or less assured of top-shelf performance.

Even so, combining a 13-year-old 133Mhz Pentium with only 32Mb, a RaLink-based PCMCIA network card and a gift-from-god 120Gb 5400rpm hard drive sounds like a recipe for disaster.

But like the rug that pulls the room together, Lenny makes it all work as a file server and torrent slave … with only a small bump in software for complete and perfect usability. No hiccups, no flukes, no spotty hardware performance.

And with uptimes in double-digit days, it shows no sign of stopping. You want a reason not to throw out an old machine? Ladies and gentlemen, I give you Debian Lenny.

Not for the faint of heart: Crux 2.7. Source-based distros are not for everybody. That should go without saying.

But of the ones I’ve tried, Crux — and most recently in its 2.7 version for the i586 — is by far my favorite.

Crux 2.7 i586: You too can be an Internet hero.

Linux From Scratch is educational, but becomes esoteric for me. Gentoo seems overcomplicated, when compared with Crux’s spartan arrangement. Of the others … well, I should probably look a little more before saying anything.

Suffice to say that Crux has just enough automation by default to keep it from becoming obtuse. But it also skimps on a lot of other points, which keeps you on your toes.

I mentioned the other day that I learned more about Linux from a 450Mhz K6-2 running Crux than I ever did with any more powerful machine. That’s very true.

But you could probably substitute almost any hardware for that rotten little K6-2, and still learn heaps and mounds more than what Ubuntu or other distros have to offer.

I’m no expert, and your way is always the right way. But if your goal is to figure out what makes your hardware tick, I can think of no better suggestion than Crux.

And best of all, I can guarantee with 99 percent assurance, that any speed improvement you might remember if you moved to Arch from Ubuntu, you will see again if you move from Arch to Crux. Believe you me. :shock:

Up and coming: ConnochaetOS. It’s probably not fair for me to highlight a distro so recent in my mind, because there is an observation bias that can’t be avoided.

But let’s be honest. I have a half-dozen computers I’ve used in the past year, and the majority of those predated the Pentium II. What do I really want out of life? An Arch Linux for i586s.

archlinux-i586.org dried up more than a year ago, but the DeLi Linux project morphed into the latest i586 effort built on Arch. And I am 100 percent on board with that.

ConnochaetOS: A promising future on the playing field.

Any Arch veteran who has an old machine in the house is going to wipe a tear from her eye if there’s a living, breathing version of i586 Arch out there. Time saved in compiling is the first reason.

Simple ease of use, a minimal starting point and an easy-peasy configuration system are others, and are all hallmarks of Arch proper. All three of those are gold to an antique computer enthusiast.

So while there might be a curse attached to i586 renditions of Arch Linux, I’m hoping ConnochaetOS can ride it out, in part with its history as DeLi Linux, but in part because it’s got what Arch users are used to.

My fingers are crossed for this one.

Big toys for big boys: Linux Mint Debian. What I’ve mentioned thus far all has the potential — if not the promise — of running on extremely low-end machines. Pentiums. Maybe even i486s.

But if you were born after 1992 and you think a single-core machine is sluggish, then your idea of “antique” is quite different from mine.

No matter: I have one more candidate for you, and this one should run on anything from a Pentium 4 up, and suffer no setbacks at all.

And heck, you can even strip the machine down to (a no doubt frightening) 256Mb and still get plenty of use out of it. Put in those hours at Free Geek, because your reward will no doubt perform with Linux Mint Debian.

LMDE: All of the flavor, none of the fat.

Distros like this one should put fear into the hearts of big-name projects like Ubuntu or Fedora or OpenSUSE. Why? Because all the flash (dare I say “Flash”? :lol: ), all the glitter and all the goodies are instantly available for us peons suffering with leftover machines.

How can LMD be doing things so right, and all the others be doing things so … not right? I don’t know.

But spend a week with LMD and you’ll probably never walk back to Ubuntu. And you’ll probably never walk into another computer reseller either, because the machine you use now (I feel safe in saying) is powerful enough to run it.

And Mint’s reputation for making Ubuntu even easier … ? Well, what can I say. Back in August I dropped Mint into a neighbor’s Celeron, with the hopes that it would be easier and cleaner to manage than — but just as speedy as — Arch.

And it ran without a complaint — no, really: without a stitch of attention from me — for three full months. What do you make of that? :D

P.S.: Get yourself some floppies. What is life without floppies?! :mrgreen:

(All right. You asked for it, you got it. :evil: )

My uglified ConnochaetOS beta 2 desktop

I don’t have much to report today, except to show my own rendition of ConnochaetOS‘s beta 2 IceWM environment.

I know: Zzzz. I took something admirable and made it into something terrifically boring. I apologize. It’s like dumping tomato ketchup on a lobster dinner.

But what can I say? I messed with both this one and the IceBuntu-wannabe desktop, and the XP Classic lookalike handles better at 150Mhz. An unexpected bonus. :|

I am enjoying ConnochaetOS for being one of the few distros I can find that can pull off the trifecta on the Mebius: native framebuffer resolution with the tridentfb module, a proper Xorg of any version using any driver, and the ability to connect to my network with zero configuration.

The fact that it can also run the ISA sound card if I give it the module makes it a head-and-shoulders winner over a lot of the distros I have force-fed this machine.

I am still building a lot of my own packages, just because there is still a lot of stuff that ConnochaetOS doesn’t offer in its repo, that I prefer to use on my machines.

I don’t have much to share this time though, and even if I did it would only be the same PKGBUILD that appears in the Arch Linux repos, with only the ‘i586′ identifier added to the architecture field.

But we discussed that last month. Suffice to say that a few additional keystrokes don’t delay me that much.

And the results are quite satisfying. It may be that ConnochaetOS is aimed at a slightly different market than the machines I target, but that doesn’t make it any less impressive to me.

If you have an i586 that needs an exceptionally light distro, and you’re familiar with Arch Linux’s setup and arrangement, you’ll appreciate it. Give it a spin. ;)

No joke: A full Gnome desktop on 105Mb

Careful, this might make you spit out your breakfast cereal.

That’s a fully updated installation of Linux Mint Debian, after a cold boot and with nothing else running. No special tricks or shortcuts. Clean and default.

Amazing. This puts it within striking range of Pentium III machines, in terms of memory. Or at least machines with 128 or maybe 192Mb, like this one did. I almost wish I still had that computer, just so I could try it out.

True, you can get smaller desktops with very sparse installations, in other distros as well. But this comes with all the bells and whistles, from the word go.

If you haven’t played with Mint’s version of Debian yet, you really owe it to yourself to give it at least one short attempt. And if you’ve got a Pentium III lying around with about 128Mb in it, tell me how it works. How, not if. ;)

What good is the “arch” field?

Today I exhibit my relative ignorance. After spending a lot of time with ConnochaetOS, I began to wonder: What good is the architecture field, in Arch Linux PKGBUILDs?

I mean, I’ve read this:

The arch array should contain ‘i686′ and/or ‘x86_64′ depending on which architectures it can be built on. You can also use ‘any’ for architecture independent packages.

Which might make mine an obtuse question. I really don’t use PKGBUILDs beyond the few esoteric programs I prefer, that aren’t in Arch’s Community repository.

But short of cross-compiling, and therefore needing to physically change each field each time, there’s nothing in there that isn’t defined by /etc/makepkg.conf, or by the CARCH or CFLAGS variables.

Which means, to my thinking, that it’s just a flag that stops the process, if the CARCH field doesn’t match. Isn’t that just a variable checking a variable?

Of course, this is one of those things that just shows how little I know, and so I should probably keep my mouth shut. Seems to me that, in a distro with separate packages for each architecture, making another point of declaring the architecture again is a third time and not necessarily useful.

But I don’t know everything, so feel free to teach me. But it seems like that variable, along with some other things in PKGBUILDs, could be trimmed out. Spent too much time in Crux, I guess. …

P.S.: Yes, I know about customizepkg.

More goodies for ConnochaetOS

I’ve been doing a little more work with ConnochaetOS again, this time moving more toward the same system I run in Crux, or on my day-to-day workhorse.

In other words, dropping the X-based system in favor of a framebuffer-based arrangement, and removing X altogether. :twisted:

I have the luxury of doing that with ConnochaetOS, much like I did with archlinux-i586.org, because — for reasons I don’t altogether understand — these Arch-based systems can get the framebuffer working with the tridentfb module, and a few parameters.

I’ll be darned if I can get it working on my own, with the systems I build manually. My best efforts look like … well, they don’t look like anything, and that’s the problem.

Regardless, with halfway proper framebuffer support, I can get not only a decent Terminus font working, but also fbterm with the PKGBUILDs in AUR and elsewhere. The end result is something that looks like this, and runs on about 21Mb of RAM.

Do not adjust your TV set. That screenshot looks like crap because what the framebuffer shows on the screen and what the framebuffer grabber reports are two very different things. Why? Again, for reasons I may never know.

But it’s always like that, no matter which system I use or which screen grabber. I have accepted it as fate, and moved on in life.

Ripping X out of ConnochaetOS is a little more complicated than in Arch. Arch uses groups, but ConnochaetOS either hasn’t implemented them yet, or might not.

No problem either way. A couple of simple loops will pull everything out, simply by screening for package names and prompting you to yank them. Try …

for i in `pacman -Q | grep xf86` ; do pacman -Rcsn $i ; done

to start with, and get a list of what you’ve still got with just pacman -Q. Look for libx11, pixman, xorg-fonts-alias, and some others.

I also made a point of pulling our four of the standard six tty screens (on a machine with only 32Mb, that eats a lot of memory), adding "tridentfb mode=800x600-16@60" and snd-es18xx to the rc.conf modules, backgrounding the net service (it will connect with my wireless automagically, but it takes a while), installing fbterm and fbv, and so forth and so on.

Probably most importantly, I put together PKGBUILDs for sudo and nfs-utils, because those are useful on my day-to-day systems. I know, I know, real geeks don’t use sudo, but I can rely on that for a quick shutdown at a key press.

And nfs-utils is kind of useful to me, since I have a string of three or four computers and like to trade files between them. ;)

The final product of all this offhanded geekery is this lumpy tarball. Binaries, PKGBUILDs, sourcecode and patches are all in here, for all these applications.

alsa-utils
aspell
aspell-en
axel
bs
cdf
centerim
charm
dehtml
detox
dictd
dmenu-xft
elinks
fbgrab
fbterm
fbv
figlet
giblib
giflib
heimdal
hnb
htop
iftop
imlib2
iotop
irssi
libevent
libgssglue
libid3tag
libidn
libldap
libmaa
libmad
libpcap
librpcsecgss
libsasl
libtirpc
libxinerama
lua
moc
musca
myman
ncdu
ncmatrix
nfsidmap
nfs-utils
odt2txt
renameutils
rpcbind
rxvt-unicode
screen-vs
scrot
sudo
teapot
terminus-font
tidyhtml
vitetris

(And no, I do not take requests. It’s Arch-based; you can build it yourself in less time, probably.)

Keep in mind that most of what you see there is a dependency of scrot, or musca, or nfs-utils (what a rat’s nest that is … :shock: ). The single console programs that are actually usable are generally independent and don’t need libraries and whatnot.

(I should also mention that elinks as built there doesn’t include spidermonkey.) If you want a rundown on what those programs do, take a look here.

That’s about all for now. I want to spend a little time working with a couple other distros, so I’m going to mirror this drive and try something different.

If you’ve got an old i586 lying around and want to see what trouble you can get into with it, please feel free to try out the stuff I posted. I strongly recommend dumping the binaries I gave you, and rebuilding them yourself.

That’s a backhanded reminder not to install random software posted by some stranger on the Internet. Not everything in life is sunshine and happy puppies. :)

P.S.: Yes, Mediafire is not cool, etc., etc. …

Another winner: ConnochaetOS at 150Mhz, 32Mb

I know, I’ve said this before but … I think I’m in love.

Just about the only downside to working with a source-based distro on a machine as old as … well, as old as the last century, is the fact that almost everything requires a large amount of time, a large amount of discipline and a meticulous attention to detail.

I’m not trying to flatter myself, I’m actually grieving over the effort in putting Crux — as I like it — on a 586 machine when ConnochaetOS does such a great job with almost no effort at all.

And honestly, as someone who migrated from Ubuntu to Arch to Crux, this is my ideal answer to the issue of running a lightweight system on a terrifically out-of-date machine.

I’ve wanted Arch to run on sub-Pentium IIs for years now, and I rejoice everyone puts together a i586 branch. Lowarch led the pack a while back, followed by a few independent efforts, and most recently the dearly departed archlinux-i586.org.

So yes, this may be just the latest in a long string of attempts to keep an i586-based version of Arch moving. And yes, this may be just the latest in my long string of excited attempts to keep my i586 machine moving with Arch.

But this comes off the slow dissipation of the DeLi Linux project, and might be able to carry momentum for a while. There are a lot of factors at work though. :(

Regardless, it’s still very exciting to watch a 150Mhz machine come to life and dash through the Arch startup sequence. The thrill of that might always outlast an Arch-for-i586 project.

I should mention a few caveats.

First, as best I can tell ConnochaetOS is still in its early stages. The package list is very sparse. Installing from the ISO is going to give you Fluxbox and a few options, and not much more. No vim. No emacs. Only nano. :shock:

So if you’re looking for the entire Arch Linux suite plus AUR …well, it’s not quite ready yet. Of course, with Arch, you’re only a few moments away from building whatever package you want, and stepping slowly through dependencies that way.

(Note that you’ll have to download the Arch PKGBUILD and install files from the Arch website, then edit the PKGBUILD to allow the i586 architecture to build. And even then it might need some tightening up.)

Next, I should mention that I installed to a virtual machine and copied across USB with dd, as is the case for most of the distros I test these days. I have a feeling that the ConnochaetOS ISO would boot alright, but I saw no reason to tempt fate. It’s just as easy the other way, and probably faster.

Finally, performance is very nearly what I get from Crux, with a few small concessions. I carve up rc.conf and inittab as a matter of course, and as you can see, I went through the work of building Musca and dmenu-xft, just because.

Occasionally though, I get some rough spots where ConnochaetOS seems to be dragging through something. I am accustomed to using my Crux build of Musca so I have a feel for its relative speed, and at times ConnochaetOS seems to be thinking very, very hard about something very, very important. :???:

Of course that wouldn’t be any different from any other machine that I’ve seen run both Crux and Arch though: Crux is a good step faster than Arch for me, and probably because so much of it is whittled down to nothing.

So I don’t fault ConnochaetOS for inheriting the (infinitesimally minor) shortcoming of its progenitor. Because on the whole, this is really great stuff.

It found my network card, configured it and connected to my wireless network without prodding — and without wireless-tools (which is possible with an orinoco-cs-driven card. Believe it or not). :shock:

It managed to make the transition between the emulator and the actual system without losing track of the hard drive, although I did hope for that when I picked the /dev/kernel drive assignment option at installation.

Video-wise, I did have to build my own xorg.conf file and adjust it to avoid the fbdev and trident drivers, and go with vesa. And I need to check to see if this will handle the tridentfb module, like archlinux-i586.org could.

In the sound department … I’m going to take my time, mostly because alsa-lib is in the repos, but alsa-utils isn’t. And there are a few other things I’d like to be in place before I force it to sing.

What I’ve personally built I’ll put out there on the Internet somewhere, and if you want to use it to get your own system up and running, be my guest. And I see that the ConnochaetOS team is soliciting software suggestions, within criteria.

In the mean time, I’m interested in playing with this a little more, and maybe even merging this with the carcass of archlinux-i586.org, which might have a few useful packages that ConnochaetOS, at this point, doesn’t.

Sound crazy? It might. All in the name of science, of course. :roll: