Log in

No account? Create an account
Linux Community's Journal
[Most Recent Entries] [Calendar View] [Friends View]

Friday, September 17th, 2004

Time Event
problem(s) with modules in 2.6
So I just upgraded to 2.6 (Running Debian Testing, official 2.6.8-1-686 binary kernel) from 2.4.18. It's great. Nice and speedy. Took the opportunity to switch /home and /usr/local to ext3. It's all wonderful and gratifying. Except modules are totally fscked. The first time I rebooted, X wouldn't start because it failed to initialize the mouse. Okay, some quick googling, it turns out this has happened to a lot of people. I run 'MAKEDEV input' to create /dev/input/mice, 'modprobe psmouse', and add 'alias char-major-13-63 psmouse' to /etc/modprobe.d/aliases (/etc/modprobe.conf is empty). At least, I think that's all I did. It worked, anyway. Then I get to work on ALSA, which refuses to see my sound card (Creative Ensoniq, ens1371 driver). lspci shows it properly, and once I get the discover package and get the proper modules loaded, alsaconf does too. But it still doesn't work. All the alsa utils can't find it, or they say the device 'default' doesn't exist. At some point I rebooted, and X refused to start again. Same symptoms, but 'modprobe psmouse' doesn't fix it.
I've messed with the aliases file, loaded all kinds of modules, checked and rechecked everything in /dev/input/, and I can't figure it out. I really don't know anything about modules, and there doesn't seem to be a lot of information specific to the new module-init-tools and 2.6 kernels.

I'm pretty lost. Anyone had this happen and fix it? Anyone have links to some good stuff about the new module system? Or even some informative stuff about modules in general?

Current Mood: grrr, modules
Poor man's SAN?
Hey everybody

As I'm sitting here in residence, I'm contemplating what to do with my ever-expanding collection of old junky hardware (currently two P1 Compaqs and a frankenstein K6-2 333) Filesharing is something rather large on my campus (we're plugged into I2 and have the whole DC++ thing going with everyone from Princeton to Western), and I was thinking it'd be cool to farm my old boxen together somehow so I could have an 'always-up' fileshare connection. However, given the large volumes of stuff I'd want to move around, I'd need a decent sized hard drive, which unfortunately costs money. Then a thought occured to me: if I could have three (or maybe even four) PCs sitting on this farm all at once, I could just get a whole bunch of cheapy hard drives (think like 2 gig HDDs, the kind most people are likely to throw out) and pool it all together. I had thought that a SAN would be what I'd need - then I read up and realized those things are all running with dedicated servers over fibre channel. Oops.

So my question is, is there a way I can do a 'unified disk' across multiple Linux boxen using Ethernet? I know I could just NFS all these things, but then I'd have to manually split downloads across multiple discs and I'd like that to work all nice and automated. Anyone have any recommendations?
news from the SCO front
Thanks to tarian, I have had my attention directed to an item of surprising import at groklaw.net: an authoritative dismissal of SCO's claims that IBM code infringed on SCO copyrights by a world-renowned expert.

See it HERE.

Have a nice day.

(slightly cross-posted)

<< Previous Day 2004/09/17
Next Day >>
About LiveJournal.com