emerge -u world broke keyboard and xpad

[daPlumber]

After an "emerge -u world" and following the directions in the Tutorial, my USB keyboard plugged into my xpad (PSO connector) and the xpad as mouse both ceased to function. Fortunately the network and ssh are fine.

OK, so what did I screw up, and how do I fix it?

Bear in mind I'm a UNIX hacker from way back, ditto for Linux, but I'm new to Gentoo as a distro. I'm also running my root on /dev/hda2 swap on /dev/hda1 (not fatx f:), I'm installed and running via the Mechinstaller, with an unmodded BIOS. I have a bunch of loopback resierfs' on E (/dev/hda50) like /var and /usr/portage, since emerge needed the space. As far as I can tel none of this is the problem, and emerge, magic, etc all work.

I'm guessing that I hosed the drivers for the keyboard and xpad somehow, but the modules seem to be loaded.

[ShALLaX]

As root:

cd /etc
rm -rf /etc/modules.autoload
wget http://gentoox.shallax.com/patch-files/modules.autoload
chmod 644 /etc/modules.autoload
reboot

[daPlumber]

OK, I think that was it.
diff on the /etc/modules.autoload:

<paste>

1c1,2
< # /etc/modules: kernel modules to load at boot time.
---
> # /etc/modules.autoload.d/kernel-2.4: kernel modules to load when system boots.
> # $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/modules.autoload.d/kernel-2.4,v 1.1 2003/03/09 09:06:23 azarah Exp $
3,30c4,9
< # This file should contain the names of kernel modules that are
< # to be loaded at boot time, one per line. Comments begin with
< # a "#", and everything on the line after them are ignored.
<
< #rtc
< #nvaudio
< usbcore
< input
< hid
< keybdev
< usb-ohci
< usbkbd
< usbmouse
< mousedev
< fat
< fatx
< i2c-core
< i2c-proc
< i2c-dev
< i2c-xbox
< extsmi
< sunrpc
< lockd
< nfs
< i810_audio
< #nvnet
< xpad
< joydev
---
> # Note that this file is for 2.4 kernels. If you need different modules
> # for a 2.5 kernel, you can create /etc/modules.autoload.d/kernel-2.5
> #
> # Add the names of modules that you'd like to load when the system
> # starts into this file, one per line. Comments begin with # and
> # are ignored. Read man modules.autoload for additional details.
31a11,12
> # For example:
> # 3c59x

</paste>

Ahem. So I guess some of those are important huh?

I'm in the middle of a magic rebuild of kde, since I didn't read that "fix" removes the packages, and that Gentoo install and compiles source. <sigh> RTFM! <smacks self on forehead>

BTW this is what my fstab looks like:

<paste>

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
#/dev/loop/0 / reiserfs defaults,errors=remount-ro 0 1
/dev/hda2 / reiserfs defaults,notail 0 1
proc /proc proc defaults 0 0
/dev/cdrom /mnt/cdrom iso9660 defaults,ro,user,noauto 0 0
/dev/hda50 /mnt/fatx/e fatx defaults 0 2
/dev/hda51 /mnt/fatx/c fatx defaults,noauto 0 2
#/dev/hda55 /mnt/fatx/f fatx defaults 0 2
#/mnt/fatx/e/swap none swap sw 0 0
/dev/hda1 none swap sw 0 0
/mnt/fatx/e/usr_portage /usr/portage reiserfs loop=/dev/loop0 0 0
/mnt/fatx/e/usr_src /usr/src reiserfs loop=/dev/loop1 0 0
/mnt/fatx/e/var /var reiserfs loop=/dev/loop2 0 0
none /dev/shm tmpfs defaults 0 0

</paste>

I'll probably get rid of the loopback reiser's on "E" as soon as I'm done messing with the config. At least "/var" loopback's are sloooowww.

I'm trying to decide if it'll be faster to just copy the files from Home 2.1's rootfs rather than waiting for KDE. I suspect so. 64MB is not a lot of space to compile in, and the box is paging like crazy.

I don't think I'm going to be doing any more "emerge -u world"'s

I could have sworn I didn't etc-update /etc/modules.autoload...
Live and learn.

Thanks for a great distro BTW. Any chance of getting Stardust to work with the MechInstaller?

[daPlumber]

Yup. /etc/modules.autoload was the problem.

Gave up on the KDE build, it was taking *WAY* too long. I dumped down Home 2.1 and installed it into my mutant filesystem collection. One quick modification to fstab and an "emerge vi" and I'm a happy camper. This old schol UNIX hacker likes his vi.

[ShALLaX]

vi sucks boooo!

[daPlumber]

Yup, and full screen editors blow goats!


Pick your poison...

See "Three Dead Trolls in a Baggie" and "Every OS Sucks":
http://artists.mp3s.com/artist_song/1241/1241156.html

[Trogdor]

vi sucks boooo!

Yeah, and what do you use? Emacs? When it comes to console editors, it is pretty limited as to your options: pico, vi, ecraps.

See my sig.

[ShALLaX]

I use nano . Great functionality, customisable syntax highlighing, spell checking, searching, replacing etc etc. Basically, anything a coder would need. Gentoox was developed with nano and nano only (ok ok.. maybe not ONLY nano, i had to use tools like sed, grep and awk )