Mounting a HFS+ hard drive

Mount an external hard drive with a HFS+ filesystem:

 # mount -t hfsplus -o force,rw /dev/sdb2 /mnt/tmp

Working with MIDI in Slackware

If you want to play MIDI files in Slackware you do need to install special software (synth, mixer, sequencer, etc.). There is a great page where it is explained clearly how to set up a basic environment in order to start working whit MIDI in Linux. All the software mentioned in that webpage is available for Slackware in Slackbuilds.org. Instead of copy-paste what is already clearly explained in the mentioned site, here, I highlight the differences I have observed.

Basically, the MIDI instructions are generated by reading a midi file, by a virtual instrument or by a hardware MIDI controller (as a keyboard), then the synth interprete the instructions a convert them into a sound signal. Several signals can be mixed (Jack), decoded and put in the speakers. 

1. I had by default a low latency kernel and a audio group in my Slackware box. 

2. I don't know how to modify the group limits, but I have realised that it is not strictly necessary. IT is possible to follow the procedure skipping this configuration and using the option -r when you run jackd (jackd -r ...), you will see a warning message. In my case, the performance is ok for what I want to do.

3. Considering that, at the end, you want to be able to use a MIDI sequencer (Rosegarden in this case). You will need to install the following set of software.

- Rosegarden : Sequencer

- liblo, liblrdf, dssi, lilypond : Rosegarden dependencies

- jack-audio-connection-kit, lirc, perl-xml-twig : Optional Rosegarden dependencies.

- fluidsynth : Softsynth

- fluid-soundfont : Base sound samples

- vmpk : Virtual piano keyboard. Used for testing purposes.
- qjackctl : GUI front end to configure Jack
- Qsynth : GUI front end to configure Fluidsynth.

4. Strictly, you don't need to use Jack to use MIDI, but it is recommended if you want to do more than very basic thinks. You do need Alsa and fluidsynth.

5. It is important to remark that Slackware is currently using Pulseaudio as sound engine. When Jack is running, Pulseaudio is shouted down.

Asus UX330UAK - Hardware

# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    2
Core(s) per socket:    2
Socket(s):             1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 142
Model name:            Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
Stepping:              9
CPU MHz:               719.866
CPU max MHz:           3500.0000
CPU min MHz:           400.0000
BogoMIPS:              5800.00
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              4096K
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca pu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xg

--------

# lspci 
00:00.0 Host bridge: Intel Corporation Device 5904 (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02)
00:04.0 Signal processing controller: Intel Corporation Device 1903 (rev 02)
00:14.0 USB controller: Intel Corporation Device 9d2f (rev 21)
00:14.2 Signal processing controller: Intel Corporation Device 9d31 (rev 21)
00:15.0 Signal processing controller: Intel Corporation Device 9d60 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Device 9d61 (rev 21)
00:16.0 Communication controller: Intel Corporation Device 9d3a (rev 21)
00:17.0 SATA controller: Intel Corporation Device 9d03 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
00:1c.6 PCI bridge: Intel Corporation Device 9d16 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d58 (rev 21)
00:1f.2 Memory controller: Intel Corporation Device 9d21 (rev 21)
00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
00:1f.4 SMBus: Intel Corporation Device 9d23 (rev 21)
02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

-------

# lsusb
us 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 002: ID 0bda:58d1 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

-------

# lsblk 
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 238.5G  0 disk
├─sda4   8:4    0 172.2G  0 part /home
├─sda2   8:2    0    16G  0 part [SWAP]
├─sda3   8:3    0    50G  0 part /
└─sda1   8:1    0   250M  0 part /boot/efi

-------

# free

              total        used        free      shared  buff/cache   available

Mem:       16292976     1189296    10928604      579460     4175076    13969620

Swap:      16777212           0    16777212

-------

# hdparm -i /dev/sda

/dev/sda:

 Model=SanDisk SD8SNAT256G1002, FwRev=Z2317002, SerialNo=163432426328

 Config={ }

 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=0

 BuffType=unknown, BuffSize=unknown, MaxMultSect=1, MultSect=off

 (maybe): CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=500118192

 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}

 PIO modes:  pio0 pio1 pio2 pio3 pio4 

 DMA modes:  mdma0 mdma1 mdma2 

 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 

 AdvancedPM=yes: unknown setting WriteCache=enabled

 Drive conforms to: unknown:  ATA/ATAPI-4,5,6,7

 * signifies the current active mode

Setting Hidpi

I did not set the DPI in Xorg. I just change in KDE the font DPI to 166 pp. This setting works fine for almost everything inside KDE but the xterm is not affected and the font looks tiny. In Window Maker everything looks small as well, but I don't know if it is possible to change that.

Another point to improve is the font size in the tty consoles, now it is very small. I know how to do it but I still have to.

Just to remember, the screen resolution is 3200 x 1800 @ 276 ppi.

Keyboard layout

My current laptop uses a German keyboard (QWERTZ), also I use to use another US-international, so I have to configure the system to use both.

I need to write in Spanish frequently. The default German layout (no death keys) works fine but it doesn't allow to write the ñ letter. The legacy version uses death keys and allows to write the lovely ñ.

Linux console:
To change the default keyboard layout, create the file:
# /etc/rc.d/rc.keymap

#!/bin/sh
# Load the keyboard map.  More maps are in /usr/share/kbd/keymaps.
if [ -x /usr/bin/loadkeys ]; then
 /usr/bin/loadkeys de-latin1.map
fi

Xorg
This settings will affect all the Xorg application, thats include KDE and Window Maker. Just create the following config file.

# /etc/X11/xorg.conf.d/90-keyboard-layout.conf

Section "InputClass"
Identifier "keyboard-all"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "XkbLayout" "de"
Option "XkbVariant" "legacy"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection

KDE
Normaly KDE will use the keymap defined by Xorg, but in the case you want to set it again in KDE, just choose the German variant German (legacy) as keyboard layout in the Input devices section of the System Settings.

There still a problem prowling around. It is the special keys, most of them works ok with the exception of the airplane mode and the increase and decrease brightness. They doesn't work, I think they are not visible in linux, but I have to check this.

Also I have to try what happens with the second keyboard, I have not tried yet.

Synaptics touchpad configuration in Xorg

I wanted to customize the configuration of the Synaptics' driver because the click buttons were swapped and I wanted to disable it while typing.

This is the Xorg configuration file I wrote:

# /etc/X11/xorg.conf.d/50-synaptics.conf

Section "InputClass"

Identifier "touchpad"

Driver "synaptics"

MatchDevicePath "/dev/input/event*"

MatchIsTouchpad "on"

 Option "TapButton1" "1"

 Option "TapButton2" "3"

 Option "TapButton3" "2"

 Option "VertEdgeScroll" "on"

 Option "VertTwoFingerScroll" "on"

 Option "HorizEdgeScroll" "on"

 Option "HorizTwoFingerScroll" "on"

 Option "EmulateTwoFingerMinZ" "40"

 Option "EmulateTwoFingerMinW" "8"

 Option "PalmDetect" "1"

 Option "PalmMinWidth" "10"

 Option "PalmMinZ" "100"

EndSection

The touchpad is not really disabled while typing. Instead, it is sensitive to recognize the palm when I touch it accidentally, avoiding to do a click.

Reference: https://wiki.archlinux.org

Sound in Slackware64 current (14.2)

UPDATE:
I installed Plasma 5.2 and now it is possible to change the output device from the System Settings > Multimedia window. Still is not a clean process but, it is cleaner than to copy and delete the asound.conf file. The procedure consisted in just to move upwards the HDMI output device in the Audio Playback option from the Audio and Video section. In my case the sub device connected to the HDMI port is the 0,7 (HDMI 2). Then, this devise also should be selected as profile in the Audio Hardware Setup tab. I tried to make a new Activity with the new configuration, but it didn't work due to the fact that all the activities share the same System Configuration, if you change something in one, it will also change in the others. Also, the configuration file snd-hda-intel.conf is not needed anymore.
---

After installing Slackware64-current (2015.12.29) I did not have sound neither in the speakers nor in the headphones. So I checked how ALSA had detected the soundcards:

$ cat /proc/asound/cards
0 [HDMI ]: HDA-Intel - HDA Intel HDMI
               HDA Intel HDMI at 0xb211c000 irq 50
1 [PCH  ]: HDA-Intel - HDA Intel PCH
               HDA Intel PCH at 0xb2118000 irq 47

So, ALSA configured the HDMI card as first device and it used it as default. Connecting the HDMI port to a TV the sound flew from the TV speakers. The problem was solved by switching the name of both cards in the file /etc/modprobe.d/snd-hda-intel.conf. 


# /etc/modprobe.d/snd-hda-intel.conf
options snd-hda-intel model=auto

alias char-major-116 snd
alias snd-card-0 snd-hda-intel
alias snd-card-1 snd-hda-intel

options snd-hda-intel id=PCH index=0
options snd-hda-intel id=HDMI index=1
#

After rebooting, the sound started to work properly in the speakers and headphones. Auto-mute mode worked fine as well. 

$ cat /proc/asound/cards
0 [PCH   ]: HDA-Intel - HDA Intel PCH
                HDA Intel PCH at 0xb2118000 irq 47 
1 [HDMI ]: HDA-Intel - HDA Intel HDMI
                HDA Intel HDMI at 0xb211c000 irq 50

In the other hand, connecting the HDMI port did not change the sound output. In other words, although there was video in the TV, the sound came out from the computer's speakers or headphones.  

The solution of this problem is not trivial. Some people try to solve it changing the default card every time they use a different card. Although it seem that it is possible to build a script to overwrite the setting (defined in /etc/asound.conf) i found this solution too dirty. Instead, I followed the idea of cloning the sound from one card to the another, so, always in both cards (PCH and HDMI) will sound the same audio and will be possible to just mute the computer's speakers when it will be connected to a TV.

After a couple of hours looking for a solution and a lot of try and error, I found a good reference to follow. Finally, The solution consisted in configure ALSA to create a virtual device which route the audio to both devices. Also, the configuration solves the error that occurs when multiple applications try to access to the virtual card at the same time. The configuration is made in /etc/asound.conf :

# /etc/asound.conf

pcm.PCH {
        type hw
        card 0
        device 0 }
        
ctl.PCH {
        type hw
        card 0
        device 0 }        

pcm.HDMI {
        type hw
        card 1
        device 7 }     

ctl.HDMI {
        type hw
        card 1
        device 7 }        

pcm.PCHDmixed {
   type dmix
   ipc_key 1024
   ipc_key_add_uid false
   ipc_perm 0666
   slave {
       pcm "PCH"
       period_time 0
       period_size 2048
       channels 2
    }
    bindings {
       0 0
       1 1
    }
}

pcm.HDMIDmixed {
   type dmix
   ipc_key 2048
   ipc_key_add_uid false
   ipc_perm 0666
   slave {
       pcm "HDMI"
       period_time 0
       period_size 2048
       channels 2
    }
    bindings {
       0 0
       1 1
    }
}

pcm.both {
    type route;
    slave.pcm {
        type multi;
        slaves.a.pcm "HDMIDmixed";
        slaves.b.pcm "PCHDmixed";
        slaves.a.channels 2;
        slaves.b.channels 2;
        bindings.0.slave a;
        bindings.0.channel 0;
        bindings.1.slave a;
        bindings.1.channel 1;
       
        bindings.2.slave b;
        bindings.2.channel 0;
        bindings.3.slave b;
        bindings.3.channel 1;
    }
   
    ttable.0.0 1;
    ttable.1.1 1;
   
    ttable.0.2 1; 
    ttable.1.3 1; 
}

pcm.!default {
        type  plug
        slave.pcm "both"}
        
ctl.!default {
        type  hw
        card PCH}
#

The sections pcm.PCHDmixed  and pcm.HDMIDmixed are needed to face the problem with concurrent sound from different applications. The section pcm.both defines a new PCM consisting of 4 channels, two from the PCH card and two from the HDMI card. PCM is a stereo card and, I guess, HDMI is it as well (at least the TV is it). The magic is finally done by routing the audio channels to the correct speakers (physical channels). This is done by the ttable sentence. It took me a bit long to understand the logic behind but finally I understood the syntax as follow:

ttable.speaker.channel gain

Here, the speakers are coded as: 0 = front left; 1 = front right; 2 = rear left; 3 = rear right;  4 = center; 5 = subwoofer. Meanwhile, channel is the number of the binding connected to an audio channel. Finally, gain is a factor applied to modify the loudness of the channel (0.5 -> 50%).

In between I found that ALSA stores it last parameters in the file /var/lib/alsa/asound.state (there is a link in /etc/) which is written when the computer shutdown. There is a method to temporarily remove it in this link.

I did a fast check connecting a TV and it works fine. But, I think, it still need to be tested with details.

Update: Skype reported that there is not mic available. It is needed to configure a capture channel with dmix. 

Asus UX305LA: Hardware

# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    2
Core(s) per socket:    2
Socket(s):             1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 61
Model name:            Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
Stepping:              4
CPU MHz:               799.968
CPU max MHz:           3000.0000
CPU min MHz:           500.0000
BogoMIPS:              4789.33
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              4096K

----------

# lspci 

00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)

00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)

00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)

00:04.0 Signal processing controller: Intel Corporation Broadwell-U Camarillo Device (rev 09)

00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)

00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)

00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)

00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3)

00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3)

00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)

00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)

00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)

00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP Thermal Management Controller (rev 03)

02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)

----------

# lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 004: ID 064e:9700 Suyin Corp. Asus Integrated Webcam

Bus 001 Device 003: ID 8087:0a2a Intel Corp. 

Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

----------

# lsblk 

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT

sda      8:0    0 238.5G  0 disk 

|-sda1   8:1    0   100M  0 part /boot/efi

|-sda2   8:2    0     8G  0 part [SWAP]

|-sda3   8:3    0    20G  0 part /

`-sda4   8:4    0 210.4G  0 part /home

----------

# free

              total        used        free      shared  buff/cache   available

Mem:        8059700      482956     6882264      234844      694480     7278928

Swap:       8388604           0     8388604

----------

# hdparm -i /dev/sda 

/dev/sda:

 Model=Micron_M600_MTFDDAV256MBF, FwRev=MA01, SerialNo=15130F491CAF

 Config={ Fixed DTR>10Mbs }

 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=0

 BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off

 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=500118192

 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}

 PIO modes:  pio0 pio3 pio4 

 DMA modes:  mdma0 mdma1 mdma2 

 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 

 AdvancedPM=yes: unknown setting WriteCache=enabled

 Drive conforms to: unknown:  ATA/ATAPI-3,4,5,6,7

 * signifies the current active mode

Slackware 13.1+ i810

I have installed Slackware 13.1 six month ago and since that I have a problem with video. Sometimes while I'm working the screen keeps freezing, I can move the mouse and see how the pointer moves, but always the screen shows the same image. In the console I have found the following error:

(EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: Input/output error.

I have tried a pair of times solve the problem, but never successfully. Now I'm going again, taking care of documenting everything.

My graphic card is: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

I used to use the i810 driver from Intel, but now this driver is deprecated and replaced by Intel graphic driver that support more cards from Intel.

The configuration:

• Kernel: 2.6.33.4-smp
• Xorg server: 1.7.7
• xf86-video-intel: 2.11.0

I have found these error in Xorg.0.log :

(II) LoadModule: "fbdev"
(WW) Warning, couldn't open module fbdev
(II) UnloadModule: "fbdev"
(EE) Failed to load module "fbdev" (module does not exist, 0)

I have used xorgsetup to create a xorg.conf file, after that I have not seen the error again. But glxgears goes very slow yet, and possibly the video will fail again.

WD My Passport for Mac on Slackware and formatted in NTFS

Ok, yes, this problem was a little weird, but some reasons I have bought an external USB HD for Mac and I want to use it with my Slackware 13.1 machine.
So step by step the problems I had to use it was:

1. When I plug the disk on my PC appears two devices in /dev :
1. /dev/sdb1 : hfsplus filesystem; this is the disk I want use.
2. /dev/sr1 : udf filesystem; this is other small disk, about 600MB, that I don't care by now.
2. The HD that was formatted for Mac (/dev/sdb1), it use HFS+ filesystem. I want use the disk on Linux and Windows so I need a NTFS filesystem disk. I have used fdisk to change the filesystem of sdb1 to NTFS and then I have formatted it with mkfs.ntfs -f -L Disk_label /dev/sdb1
3. When I have mounted sdb1 I had no access to the data stored in the disk, but if I did it on windows it works fine, so the problem was the way that is was mounted. I had installed NTFS-3g and the problem was solved with:
   mount -t ntfs-3g /dev/sdb1 /media/hd
   By this way, now I have complete access to the disk, but I have to mount it manually and as root.
4. On /etc/fstab I had the row:
   /dev/sdb1 /media/memory0 auto noauto,user,exec,rw 0 0
   When the disk was mounted it is did it using the native NTFS filesystem instead of NTFS-3g. I have changed it by:
   /dev/sdb1 /media/memory0 ntfs-3g defaults 0 0
   With it I can mount the drive with mount /dev/sdb1 but just as root. I suppose that with this change I could have problems with volumes with other filesystems (FAT32 for example) linked to the same device (/dev/sdb1). But this is another problem that don't care by now.

Nothing that I have searched and tried have helped.

1. I have created the file /etc/filesystems like a copy of /proc/filesystem but changing the line ntfs by ntfs-3g, but doesn't work.
2. From the FAQ of NTFS-3g I have found something that should have help me but it didn't. http://www.tuxera.com/community/ntfs-3g-faq/#unprivileged
3. Another page referring to the FAQ but with more information. http://pxnh.wordpress.com/ (at the end of the page).
4. I have changed the group of ntfs-3g to plugdev but doesn't work.

So much time I have gave it to that little problem, so I'm thinking in changing the HDD filesystem to EXT3 or 4.
Finally I have formatted the HDD with EXT4 supposing that it would resolve the problem. But when I have mounted the HDD, I didn't have access to write in it. I have deleted from /etc/fstab the line that define /dev/sdb1 and after mounting the drive for first time, as root, I have changed the owner and permissions to my user and 760. Now the drive is mounted automatically in KDE using HAL. A dirty solution but is ok by now.

The error that appears when I pugged a USB HDD was solved adding my user to the groups users and plugdev and restarting the computer:
# usermod -aG users my_user
# usermod -aG plugdev my_user

Slackware 12 + i810

Tenía problemas en X, no podía ver videos ni DVD, el openarena colgaba al PC, etc, además al iniciar X salen alguno errores. Buscando en la Internet leí que eso sucede porque el driver de mi tarjeta de video el i810 no estaba presente pues al momento de instalar el SO se instala una versión nueva que se llama intel y que el driver i810 en realidad es un link hacia intel. Para solucionar el problema bajé el paquete original del driver i810 y lo reinstalé.

El paquete está aquí : http://packages.slackware.it/package.php?q=current/xf86-video-i810-1.7.4-i486-2

Comando de instalación : # upgradepkg --reinstall xf86-video-i810-1.7.4-i486-1.tgz

Referencia : slacky.eu

Synaptics Touchpad + USB mouse

La compilación del driver Synaptics no dió especial problema, sin embargo X no partía pues decía que no encontraba un touchpad Syptics instalado. La solución pasó por editar el archivo /etc/rc.d/rc.modules-2.6.21.5-smp en la sección "PS/2 mouse support" se eliminó la opción "proto=imps" que trae por omición Slackware. Con ello todo funcionó bien. En la configuración de xorg se agregó un mouse USB, uso un MS IntelliMouse Optical 1.1, funciona pero no he probado si se pueden usar los 5 botones, por lo menos los tres tradicionales y la rueda funcionan bien.

El xorg.conf además considera la configuración para el monitor LCD y la salida de Svideo, al iniciar X veo que esto da algunos errores pero se ejecuta de todas maneras. No he probado la salida de Svideo, esto lo solucionaré más adelante. También veo que puede haber un problema con el teclado pues sale un error, pero esto no se nota al momento de usarlo. En resumen, esta configuración funciona, sucio pero funciona.

Slackbuid : synaptics.SlackBuild

xorg.conf : xorg.conf

El Hardware

La máquina destino a la que se refiere este sitio es un Laptop HP Pavilion dv1117la. El resultado de un lspci se agrega al final del post.

Todos los archivos de configuración y los slackbuilds que he usado están en:
http://alumnos.elo.utfsm.cl/~fperona/Linux/slackware/12.0/


Resultado de lspci:
00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 03)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:06.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)
02:09.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
02:09.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller
02:09.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller
02:09.4 Generic system peripheral [0805]: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller