portable, ThinkPad 40 & Fedora Core 2

comp.os.linux.portable - Linux OS on portable PCs.


portable >> ThinkPad 40 & Fedora Core 2

by William D. Waddington » Mon, 08 Nov 2004 02:30:32 GMT

I've added a Fedora Core 2 page to my R40 site... *yawn*.
http://www.beezmo.com/ThinkPadR40.htm

There are plenty aleady I suppose, and FC2 pretty well does its thing
out of the box - if you don't mind having your Win partition hosed.

Anyway, the reason I mention it here is that the power management
stuff didn't quite work the way I thought it should. Apmscript used
the old /proc/cpufreq interface so if the kernel was built with the
sysfs interface apmscript couldn't switch frequency governors based
on AC on-line status. Further, it only checked AC status on power
change so laptop mode and selective service shutdown appropriate
for battery power operation didn't get set if booted on battery power.

I think i have successfully re-jiggered apmscript and both apmd
scripts to do this stuff successfully. I also hacked up Carl
Thompson's CPUSpeed userspace governor to make it a little more
friendly to APM (which is how I prefer to run), added a few "features"
and maybe a little more flexibility. Basically, I changed the name
and hacked away. I don't know if I got the GPL, Copyright, and
attribution stuff correct - and I will change it immediately if
wrong. This stuff is documented in the "CPU Frequency scaling
(speedstep) and Laptop Mode" section of the page.

I'm not a programmer, and I'm not putting this stuff out there as a
solution to anything. However, if anyone is inclined to take a look
at this stuff, I would love to know if it makes any sense, especially
on non-thinkpad boxen.

Sorry for the long post, and thanks for listening.

Bill
--
William D Waddington
XXXX@XXXXX.COM
"Even bugs...are unexpected signposts on
the long road of creativity..." - Ken Burtch

Top
Similar Threads

1. Fedora Core 1 on Thinkpad T41

2. Fedora Core 1/2 on a thinkpad T23

3. Anaconda shuts down on IBMiSeries ThinkPad Fedora Core 1 install

4. driver for wireless adaptor on Thinkpad 40 - Linux Setup

5. Sound card stopped working after upgrading from Fedora Core 3 to Fedora Core 4 

I upgraded my machine from Fedora Core 3 to Fedora Core 4 and the sounds
card has stopped working.

When I start X-windows (I'm running KDE 3.4.2-0.fc3.2 Red Hat), I get an
error message "Sound server informational message: Error while
initializing the sound driver: device /dev/dsp can't be opened (No such
file or directory) The sound server will continue, using the null output
device."

And sure enough there is no /dev/dsp there.

I tried going into the KDE control center -> sound and multimedia -> sound
system.  I tried autodetect, OSS, threaded OSS, none of them worked.  All
failed with the "no such device" error above.

I tried creating a /dev/dsp with MAKEDEV as in 

[root@black ~]# /sbin/MAKEDEV -v dsp
create dsp                            c  14   3 root:root 600
create dsp1                           c  14  19 root:root 600
create dsp56k                         c  55   0 root:root 600
symlink dsp0 -> dsp
[root@black ~]# ls -l /dev/dsp
ls: /dev/dsp: No such file or directory
[root@black ~]#      

So that didn't work.

I tried updating the alsa packages using yum and while that did update the
packages, it didn't solve the problem.  I've tried rebooting, to no avail.
 I even tried using one of the older kernels, but now that's broken, too.

My /etc/modules.conf file contains:

[root@black ~]# more /etc/modules.conf
alias eth0 8139too
alias usb-controller usb-uhci
alias usb-controller1 ehci-hcd
alias ieee1394-controller ohci1394
options scanner vendor=0x04b8 product=0x011f
alias sound-slot-0 via82cxxx_audio
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :
# Note: for use under 2.6, changes must also be made to modprobe.conf!
[root@black ~]# 


lspci reports that the sound controller is still there:

[jeffs@black ~]$ /sbin/lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge
00:0f.0 RAID bus controller: Promise Technology, Inc. PDC20276 (MBFastTrak133 Lite) (rev 01)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:13.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:14.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev a2)
[jeffs@black ~]$       

Kudzu also can find it:

class: AUDIO
bus: PCI
detached: 0
driver: snd-via82xx
desc: "VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller"
vendorId: 1106
deviceId: 3059
subVendorId: 1458
subDeviceId: a002
pciType: 1
pcidom:    0
pcibus:  0
pcidev: 11
pcifn:  5


Does anybody have any bright ideas?


Many thanks


Jeff Silverman

6. Upgrade Fedora Core 3 to Fedora Core 5 Help please

7. Strange SSH halting problem between Fedora Core 2/Fedora Core 3 

Jonathan Abbey wrote:
<snip>

Hi Jon:

Something I noticed today while ssh'ing via another ssh'ed account is that
it doesn't really like multiple-forwarded X connections. 

I'll elaborate:

I ssh into my home workstation from work. This connection has been setup to
forward X connections. But then when I try to ssh from the home workstation
to another machine on my home network, I get a timeout similar to what you
describe. The solution is to do the second ssh without forwarding X, ie, by
invoking "ssh -x <server>". I don't know whether this is your problem, but
might be something to look into.

Cheers,
-- 
 ** Matt van de Werken -- Cricket, Unix, Electronics Enthusiast **
 **   Linux -- Dual Athlon MP1800+ -- Fri, 03 Dec 2004  5:01PM  **
Love tells us many things that are not so.
  -- Krainian Proverb

8. [News] Linux on 40 Cores Now More Then Reachable - Linux