* Re: Alcatel speedtouch USB driver and SMP.
From: Oliver Neukum @ 2002-12-18 11:13 UTC (permalink / raw)
To: romieu, Colin Paul Adams; +Cc: linux-kernel
In-Reply-To: <20021217232010.A19613@electric-eye.fr.zoreil.com>
Am Dienstag, 17. Dezember 2002 23:20 schrieb romieu@fr.zoreil.com:
> Colin Paul Adams <colin@colina.demon.co.uk> :
> [...]
>
> > So, is anyone using it on SMP?
>
> drivers/usb/misc/speedtouch.c::udsl_atm_ioctl() calls put_user() and
> atm ioctls are issued with spinlock held (see
> net/atm/common.c::atm_ioctl()).
Correct. As far as that is concerned the ATM layer is utter crap.
Regards
Oliver
^ permalink raw reply
* EDE - 0.0.5
From: Neil Holmes @ 2002-12-18 11:04 UTC (permalink / raw)
To: Linux 8086
The Elks Distribution Edition (EDE) 0.0.5 is now ready. Though its not
uploaded yet. Its been so long since I used my ftp space that, I believe, my
password has expired !!! I have requested a new password but, in the
meantime, if anyone particularly would like a copy now then email me and I
will make interim arrangements.
Apologies for the very long delay in release. Its been difficult to spend
time working on it recently for a variety of reasons.
EDE-0.0.5 installs kernel 0.1.1. It also installs from a single floppy disk
once more. Thanks to Harry for his assistance with "rdev" in making this
possible. 0.0.5 will cater for ELKS installation on a primary hard drive
(bda1 through bda4) and can cope with dual-booting using Pascal Bellards
Bootkit. The operating systems that are recognised for co-existance, at this
stage, are DOS and Linux. I have tested for partitions containing all 3 on
one 486 laptop. My test 286 machine dual-boots ELKS and Windows 3.1 (DOS).
I have, for 0.0.5, also upgraded the version of elkscmd programs. I have
taken what was the latest download on sourceforge, namely elkscmd_20020501,
at the time I was building the release.
I have some concerns, still, for the filesystem experts. The install floppy
still boots an older kernel (0.0.82) even though it, ultimately, installs
0.1.1 to the hard drive. This is because I find that kernel more reliable
when it comes to setting up the ELKS partition. I would be very greatful of
some assistance in this area as I am still recommending the hard drive be
initialised using a DOS fdisk for the most reliable results. Apart from
anything else this means that I have to carry two kernels on the install
floppy disk taking up valuable space. Suggestions are greatfully received !
So thats 0.0.5. What next ? I am very open for suggestions as to what I
should be including next. Please email suggestions. Here are some ideas :-
- Install to a secondary hard drive (/dev/bdb1 though /dev/bdb4 - shouldn't
be too difficult)
- Introduce an option to implement elksnet
- Look for cosmetic improvements in the installation
As you can see. I am starting to fish for ideas.
Thanks to all the people who have taken the time to write to me and express
their gratitude for EDE. It makes it all worth while. Maybe it really has
helped convert a few more people to the cause ?
Anyway.
Have fun !
Neil
^ permalink raw reply
* Re: Discovery II (was Re: Support for Arctic platform (405LP based))
From: Rabeeh Khoury @ 2002-12-18 11:01 UTC (permalink / raw)
To: Mark A. Greer; +Cc: Roland Dreier, linuxppc-embedded
In-Reply-To: <3DFDCB00.7060509@mvista.com>
> Rabeeh Khoury from Marvell has done a port to it and put it in the
> linux-galileo tree. I have no hardware to test it but Rabeeh says that
> its been working fine for him for some time.
I have the DB-64360 (Development board based on MV64360 part) working
fine with the support for the development board and the gigE ethernet.
I mainly have tested this with 7455 CPUs. I also tested it with dual 7455
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply
* Re: problems with NFSv3 kernel 2.5.52 server, 2.4.20 client. (server x86 linux, clientsparclinux)
From: Trond Myklebust @ 2002-12-18 11:04 UTC (permalink / raw)
To: venom; +Cc: linux-kernel
In-Reply-To: <Pine.LNX.4.43.0212181026370.25931-100000@cibs9.sns.it>
>>>>> " " == venom <venom@sns.it> writes:
> On the server I could not find any error message, while on the
> sparclink client I found:
> Dec 17 18:08:16 storm kernel: call_verify: server accept
> status: 1 Dec 17 18:08:16 storm last message repeated 2 times
> Dec 17 18:08:16 storm kernel: RPC: garbage, exit EIO Dec 17
What mount options are you using? Is it a 'tcp' mount?
Are other clients able to access the server without the above problem?
Cheers,
Trond
^ permalink raw reply
* Re: 2.4.19, don't "hdparm -I /dev/hde" if hde is on a Asus A7V133 Promise ctrlr, or...
From: Andre Hedrick @ 2002-12-18 10:44 UTC (permalink / raw)
To: D.A.M. Revok; +Cc: Manish Lachwani, linux-kernel
In-Reply-To: <200212180538.03296.marvin@synapse.net>
Guess you two need to head over to promise and get those blood letting
NDA's signed. To figure out what is wrong with your deployment.
I have never seen this issue and I know every combination of command calls
to avoid. What you are doing is not out of spec, just how you are are
doing it is.
Cheers,
Andre Hedrick
LAD Storage Consulting Group
On Wed, 18 Dec 2002, D.A.M. Revok wrote:
> Ahem.
>
> You /may/ want to remind me, next time, that umounting all filesystems
> except root, remounting root read-only, AND raid-stop'ing all arrays
> would be a good idea before doing this ( I forgot the last one )
>
> Also, it seems that all drives de-allocate a sector every time I do this,
> and this is costing my system integrity...
>
>
> Yes, it happens on all drives on the controller, and I've 2:
> IBM 60GXP, 40GB == /dev/hde
> Quantum LM15, 15GB == /dev/hdg
>
> booting into multiuser command-line mode, no X, login as root, umount
> everything, "smartctl -a /dev/hde" ( or hdg ) gets 2 information lines,
> the second being the model# of the drive, and it never reaches the third
> line ( the newline doesn't appear ), and the drive-light comes on, and
> it's permanently hanged.
>
> I'd thought this would be implicit in the
> * "cat /proc/ide/hde/identify" gets the same results *
> comment I'd made previously, but did it out of curiosity...
>
>
> When I did it on the Quantum, the Quantum's drive-light came on ( it's in
> a "mobile-rack" ), so it seems that the drive-light actually is still
> connected to the drive at that point, though nothing useful goes on
> after...
>
>
> By the way, I seem to have hit this with the earlier 2.4.x kernels, (
> IIRC ), but had /so/ much problems with flaky config and flaky distros
> at the time, that I didn't get that info out then ( by the time I got a
> stable system, I'd forgot, sorry... )
>
>
> * Tell me which kernels you want me to try ( except ext3-broken ones ),
> and I'll do it, so you can scope where-the-break-is better, TIA *
>
> -me
>
> On Tue 17 December, 2002 7:09, you wrote:
> >Is it happening with all the drives on the controller? Is it possible
> > to immediaately gather the SMART data from the drive after bootup
> > using smartctl?
> >
> >Thanks
> >Manish
> >
> >-----Original Message-----
> From: D.A.M. Revok
> >To: linux-kernel@vger.kernel.org
> >Sent: 12/15/02 12:49 PM
> >Subject: 2.4.19, don't "hdparm -I /dev/hde" if hde is on a Asus A7V133
> >Promise ctrlr, or...
> >
> >( that's a capital-aye in the hdparm line )
> >
> >not even the Magic SysReq key will work.
> >
> >also, don't
> >
> >"cd /proc/ide/hde ; cat identify"
> >
> >... same thing
> >drive-light comes on, but have to use the power-switch to get the
> >machine
> >back, ( lost stuff again, fuck )
> >
> >
> >proc says it's pdc202xx
> >
> >Promise Ultra series driver Ver 1.20.0.7 2002-05-23
> >Adapter: Ultra100 on M/B
>
> --
> http://www.drawright.com/
> - "The New Drawing on the Right Side of the Brain" ( Betty Edwards,
> check "Theory", "Gallery", and "Exercises" )
> http://www.ldonline.org/ld_indepth/iep/seven_habits.html
> - "The 7 Habits of Highly Effective People" ( this site is same
> principles as Covey's book )
> http://www.eiconsortium.org/research/ei_theory_performance.htm
> - "Working With Emotional Intelligence" ( Goleman: this link is
> /revised/ theory, "Working. . . " is practical )
> http://www.leadershipnow.com/leadershop/1978-5.html
> - Corps Business: The 30 /Management Principles/ of the U.S. Marines (
> David Freedman )
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
^ permalink raw reply
* [parisc-linux] 2.5 serial-mux patch?
From: jsoe0708 @ 2002-12-18 10:50 UTC (permalink / raw)
To: Ryan Bradetich; +Cc: parisc-linux
Hi Ryan,
Regarding your patch:
http://lists.parisc-linux.org/pipermail/parisc-linux-cvs/2002-November/03=
1910.html
I would like to ask you some additional: is it also applicable for serial=
-mux
pci card (as Prod J3592A) or scsi-mux (as the 8 port of Central Data)?
Thanks in advance,
Joel
PS: Do you think it could be easily backport in 2.4 (if not yet done)?
*************************************************************************=
*******
Controlez mieux votre consommation Internet...surfez Tiscali Complete...h=
ttp://tiscali.complete.be
^ permalink raw reply
* Re: How do I see all my partitions?
From: axel @ 2002-12-18 10:47 UTC (permalink / raw)
To: Chris; +Cc: linux-newbie
In-Reply-To: <5.1.0.14.0.20021217222210.00b5fdd8@mail.comcast.net>
Hi Chris!
On Tue, 17 Dec 2002, Chris wrote:
> my winxp partition. How do I display all the
> partitions, Win/Dos/Linux, in one place so I can
> give mount the correct partition name?
You might already have heard of fdisk. It is a tool to partition your hard
disks and also in fact the easiest way to see what partition is of what
type and has what number/name.
To call fdisk for your primary IDE slave call "fdisk /dev/hda" and you
will get something like this:
Device Boot Start End Blocks Id System
/dev/hda1 1 9688 4882720+ 83 Linux
/dev/hda2 * 9689 48440 19531008 7 HPFS/NTFS
/dev/hda3 48441 158816 55629504 83 Linux
(For example for your second SCSI disk it would be "fdisk /dev/sdb")
Here you can see that my windows partition is /dev/hda2 is of type NTFS.
To mount it you'll need an empty directory (e.g. /windows or /mnt/win) and
the necessary file system support for you kernel (in my case NTFS).
Then "mount <device> <mount directory>". In my case this looks like:
"mount /dev/hda2 /windows"
Have fun,
Axel
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply
* Re: alsasound init script (Re: possible problems with rc6 aplay )
From: Takashi Iwai @ 2002-12-18 10:46 UTC (permalink / raw)
To: Fernando Pablo Lopez-Lezcano; +Cc: Mark Knecht, Paul Davis, Alsa-Devel
In-Reply-To: <1040153770.5622.86.camel@cmn37.Stanford.EDU>
At 17 Dec 2002 11:36:10 -0800,
Fernando Pablo Lopez-Lezcano wrote:
>
> On Tue, 2002-12-17 at 03:06, Takashi Iwai wrote:
> > At 16 Dec 2002 19:46:55 -0800,
> > Mark Knecht wrote:
> > > On Mon, 2002-12-16 at 18:51, Paul Davis wrote:
> > > > i think it would something like this:
> > > >
> > > > options snd-hdsp snd_index=0
> > > > options snd-usb-foo snd_index=1
> > > >
> > > > i'm sure that takashi or jaroslav will correct me if i got this wrong.
> > >
> > > This makes perfect sense, and it isn't what I did. (!!)
> > >
> > > The PlanetCCRMA has a Nano-HOWTO on how to install the MidiMan 2X2 by
> > > hand. It's a little USB-based MIDI interface (not a sound card) that is
> > > not recognized by alsaconf, so we do a bit of editing by hand.
> >
> > the behavior depends on the order of booting.
> > if the hotplug service is booted before the alsasound init script,
> > hotplug will start the snd-usbaudio module, which will be assigned as
> > the first empty device, i.e. device #0, unless you specify the index
> > option. and afterwards, the alsasound script is started, and it
> > results in the confliction of devices.
> >
> > setting an index option is one of the solutions.
> > in this case, the first usb-audio/midi device will be forced to be
> > assigned to #1. so, it's safe to start it beforehand.
> >
> > but, when we take a deeper look at this, we find another problem.
> > the alsasound init script checks whether the ALSA was already started
> > by checking the existence of /proc/asound directory. and, if hotplug
> > started the usb-audio/midi before alsasound, this directory would be
> > also created because the alsa core was started without help of
> > alsasound init script, too. this leads to the skip of loading of any
> > other soundcards, because alsasound will quit immediately.
> >
> > after all, a simple solution for this is to make sure that alsasound
> > starts before hotplug. then, even the index option for snd-usbaudio
> > wouldn't be necessary (in theory).
>
> I think that in RedHat hotplug is not started as a service so we cannot
> make sure that alsasound starts first (at least not easily - I have to
> check again on the startup scripts to see what is done and when).
hmm, then it's difficult to assume the order...
in most cases, hotplug is started at the fairly early stage of boot
sequences, because it supports also the fundamental devices such like
network.
> It would be better to make the alsasound script more robust (and
> independent of the startup order) and able to deal with partially loaded
> modules, so instead of just checking for the /proc/asound directory it
> would actually see what modules are already loaded and only load those
> that are not. It does not look too easy, it seems that /proc/asound does
> not provide a list of loaded modules (rather a list of cards that are
> not associated with module names).
agreed. a scenario i can imagine now is that the script just takes a
look at /proc/asound/cards and checks the numbers at the first column.
this should correspond to the card indices which have been already
loaded. then the script will try to load the modules snd-card-X but
skip the numbers listed in the above...
i'll try to rewrite as this way.
> > in the above scenario, anyway, cards_limit must be changed. and i
> > think it's a bit annoying.
> >
> > the attached patch will change the handling of cards_limit option.
> > with the patch, the alsa won't restrict the number of cards per
> > cards_limit option, but only limits the auto-probing via kmod.
> > i.e. you can load more card modules even with cards_limit=1.
>
> That sounds reasonable.
fine, does anybody see a drawback?
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
^ permalink raw reply
* [LARTC] TBF shaped machine unreachble ?
From: Paolo Poletti @ 2002-12-18 10:41 UTC (permalink / raw)
To: lartc
I've added to my RedHat 7.3 (kernel 2.4.18-3) machine on a 2Mbit line the
following command :
/sbin/tc qdisc add dev eth0 root tbf rate 256kbit latency 50ms burst 10000
After this has been added, periodically i'm not able to reach my machine from
the network. Is there any known bug ? Can i produce some kind of logging ?
Thanks !
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply
* [PATCH] ALSA & HP100 update
From: Jaroslav Kysela @ 2002-12-18 10:46 UTC (permalink / raw)
To: Linus Torvalds; +Cc: LKML
Linus, please do a
bk pull http://linux-sound.bkbits.net/linux-sound
the GNU patch is available at
ftp://ftp.alsa-project.org/pub/kernel-patches/alsa-bk-2002-12-18.patch.gz
Thank you,
Jaroslav
ALSA summary:
- added hotplug support - disconnection of running devices (USB & PCMCIA)
- added ALSA-Configuration.txt document
- control API - replace global control lock with semaphore
- driver updates
- ICE1712, USB audio, Trident, CS4281, ENS1371, ALI5451, VIA82xx, HDSP,
ALS4000, CMIPCI, CS46xx, ES1968, FM801, Intel8x0
HP100 summary:
- small HP100 driver updates by Pavel Machek
- coaxial connection detection, compilation fixes
This will update the following files:
Documentation/sound/alsa/ALSA-Configuration.txt | 1188 ++++++++++++++++++++++++
Documentation/sound/alsa/ControlNames.txt | 82 +
drivers/net/hp100.c | 99 +-
drivers/net/hp100.h | 5
include/sound/ac97_codec.h | 4
include/sound/control.h | 2
include/sound/core.h | 39
include/sound/cs46xx.h | 2
include/sound/cs46xx_dsp_spos.h | 6
include/sound/initval.h | 17
include/sound/mixer_oss.h | 1
include/sound/mpu401.h | 6
include/sound/opl3.h | 1
include/sound/pcm.h | 5
include/sound/pcm_oss.h | 1
include/sound/sb.h | 9
include/sound/trident.h | 18
include/sound/version.h | 14
sound/arm/sa11xx-uda1341.c | 2
sound/core/control.c | 176 ++-
sound/core/device.c | 40
sound/core/info.c | 8
sound/core/init.c | 355 ++++++-
sound/core/ioctl32/ioctl32.c | 1
sound/core/ioctl32/rawmidi32.c | 1
sound/core/ioctl32/seq32.c | 1
sound/core/ioctl32/timer32.c | 1
sound/core/oss/mixer_oss.c | 74 -
sound/core/oss/pcm_oss.c | 57 -
sound/core/pcm.c | 50 -
sound/core/pcm_lib.c | 12
sound/core/pcm_native.c | 8
sound/core/pcm_sgbuf.c | 52 +
sound/core/rawmidi.c | 46
sound/core/seq/Makefile | 93 -
sound/core/seq/instr/Makefile | 1
sound/core/seq/seq.c | 2
sound/core/seq/seq_device.c | 20
sound/core/seq/seq_lock.c | 2
sound/core/seq/seq_lock.h | 2
sound/core/sound.c | 10
sound/drivers/mpu401/mpu401.c | 14
sound/drivers/mpu401/mpu401_uart.c | 7
sound/drivers/mtpav.c | 78 -
sound/drivers/opl3/Makefile | 77 -
sound/drivers/opl3/opl3_lib.c | 21
sound/drivers/opl3/opl3_seq.c | 1
sound/drivers/virmidi.c | 3
sound/isa/cs423x/cs4231_lib.c | 70 -
sound/isa/cs423x/cs4236.c | 8
sound/isa/es18xx.c | 146 +-
sound/isa/sb/sb16.c | 10
sound/isa/sb/sb16_main.c | 6
sound/isa/sb/sb_mixer.c | 320 +++++-
sound/pci/Kconfig | 4
sound/pci/ac97/ac97_codec.c | 236 ++++
sound/pci/ac97/ac97_id.h | 3
sound/pci/ac97/ac97_patch.c | 14
sound/pci/ac97/ac97_patch.h | 1
sound/pci/ali5451/ali5451.c | 141 +-
sound/pci/als4000.c | 55 -
sound/pci/cmipci.c | 453 ++++++++-
sound/pci/cs4281.c | 10
sound/pci/cs46xx/cs46xx_lib.c | 297 +++---
sound/pci/cs46xx/cs46xx_lib.h | 7
sound/pci/cs46xx/dsp_spos.c | 90 +
sound/pci/cs46xx/dsp_spos.h | 26
sound/pci/cs46xx/dsp_spos_scb_lib.c | 264 ++---
sound/pci/emu10k1/emu10k1.c | 2
sound/pci/ens1370.c | 94 +
sound/pci/es1938.c | 6
sound/pci/es1968.c | 67 -
sound/pci/fm801.c | 62 -
sound/pci/ice1712/Makefile | 2
sound/pci/ice1712/ak4524.c | 58 -
sound/pci/ice1712/amp.c | 55 +
sound/pci/ice1712/amp.h | 34
sound/pci/ice1712/delta.c | 32
sound/pci/ice1712/envy24ht.h | 203 ++++
sound/pci/ice1712/ews.c | 17
sound/pci/ice1712/hoontech.c | 5
sound/pci/ice1712/hoontech.h | 8
sound/pci/ice1712/ice1712.c | 1020 ++++++++++++++++----
sound/pci/ice1712/ice1712.h | 6
sound/pci/intel8x0.c | 6
sound/pci/korg1212/korg1212.c | 4
sound/pci/rme32.c | 182 ++-
sound/pci/rme96.c | 6
sound/pci/rme9652/hammerfall_mem.c | 2
sound/pci/rme9652/hdsp.c | 62 -
sound/pci/rme9652/rme9652.c | 8
sound/pci/trident/trident.c | 10
sound/pci/trident/trident_main.c | 676 +++++++------
sound/pci/via82xx.c | 3
sound/synth/Makefile | 3
sound/usb/Kconfig | 2
sound/usb/usbaudio.c | 88 +
sound/usb/usbaudio.h | 8
sound/usb/usbmidi.c | 131 +-
sound/usb/usbmixer.c | 121 +-
sound/usb/usbmixer_maps.c | 8
sound/usb/usbquirks.h | 116 ++
102 files changed, 6111 insertions(+), 1871 deletions(-)
through these ChangeSets:
<perex@suse.cz> (02/12/18 1.885.1.5)
ALSA update
- intel8x0 - added NVidia NForce2 Audio PCI ID
- USB driver - clenaups in the disconnect routine
- added ALSA-Configuration.txt and ControlNames.txt documents
<perex@suse.cz> (02/12/17 1.885.1.4)
HP100
- fixed compilation problem when debug is active
<perex@suse.cz> (02/12/16 1.883.1.40)
ALSA update
- fixes in ALI5451 initalization
- added snd_pci_alloc_page() workaround
- FM801 - fixed PCI device identification
- USB mixer - fixed min values for some types
<perex@suse.cz> (02/12/12 1.865.2.5)
ALSA update
- fixed compilation problems for rawmidi, sb16, ac97_codec, ens1370
- ES1968 - added use_pm parameter
- USB audio
- complete callback follows 2.5
- fixed support for FU and PU controls (mixer)
- updated SB Extigy comments
<perex@suse.cz> (02/12/12 1.865.2.4)
HP100 network driver - Pavel Machek <pavel@suse.cz>
- TRUE/FALSE removal
- detection of Coaxial wire
<perex@suse.cz> (02/12/11 1.865.2.3)
ALSA update
- CS46xx
- volume bug fixes and phase reversal fix
- AC3 stuff...
- SPDIF input fix
- init.c
- used workqueue for the disconnection job
- CMIPCI
- S/PDIF output / PLL updates
- ICE1712
- fixed reversed volume for AK4524 and AK4528 codecs
- added support for Hoontech STA DSP24 Media 7.1
- USB audio
- various mixer fixes
- quirks for Edirol PCR-30/50 keyboards and Midiman hardware
<perex@suse.cz> (02/12/05 1.825.1.23)
ALSA update
- ALS4000 - improved mixer support
- ICE1712 - added ICE1724 (Envy24HT code)
- fixed Delta410 support
- usbaudio - added quirks for more Yamaha devices
<perex@suse.cz> (02/12/05 1.825.1.22)
ALSA update
- control API - replace global control lock with semaphore
- ac97 - added VT1616 support
- add code for PC98 architecture
- ENS1370/1371 - added gameport code
- HDSP - fixed oops when device is not detected
- replace __SMP__ with CONFIG_SMP
<perex@suse.cz> (02/12/04 1.825.1.21)
ALSA update
- Added hotplug support - disconnection of devices
- usbaudio
- added hotplug support
- added support for resolution to ALSA mixer
- ALI5451
- added initialization for ALi 7101
- via82xx
- added rate initialization for all AC97 streams
- RME HDSP
- fixed multiface initialization
- ICE1712
- spin-lock cleanups
<perex@suse.cz> (02/11/23 1.797.126.1)
ALSA update
- CS46xx
- SPDIF channel status implementation
- mixer name cleanups
- Trident
- added S/PDIF device for SiS 7018
- CS4281
- fixed broken loops in suspend/resume routines
- ENS1370
- fixed driver names and rights for IEC958 Playback Mask
- ICE1712
- added possibility to lock the rate (pro-pcm device)
- usbaudio
- fixed rawmidi
-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
^ permalink raw reply
* Re: 2.4.19, don't "hdparm -I /dev/hde" if hde is on a Asus A7V133 Promise ctrlr, or...
From: D.A.M. Revok @ 2002-12-18 10:38 UTC (permalink / raw)
To: Manish Lachwani; +Cc: linux-kernel
In-Reply-To: <233C89823A37714D95B1A891DE3BCE5202AB1B35@xch-a.win.zambeel.com>
Ahem.
You /may/ want to remind me, next time, that umounting all filesystems
except root, remounting root read-only, AND raid-stop'ing all arrays
would be a good idea before doing this ( I forgot the last one )
Also, it seems that all drives de-allocate a sector every time I do this,
and this is costing my system integrity...
Yes, it happens on all drives on the controller, and I've 2:
IBM 60GXP, 40GB == /dev/hde
Quantum LM15, 15GB == /dev/hdg
booting into multiuser command-line mode, no X, login as root, umount
everything, "smartctl -a /dev/hde" ( or hdg ) gets 2 information lines,
the second being the model# of the drive, and it never reaches the third
line ( the newline doesn't appear ), and the drive-light comes on, and
it's permanently hanged.
I'd thought this would be implicit in the
* "cat /proc/ide/hde/identify" gets the same results *
comment I'd made previously, but did it out of curiosity...
When I did it on the Quantum, the Quantum's drive-light came on ( it's in
a "mobile-rack" ), so it seems that the drive-light actually is still
connected to the drive at that point, though nothing useful goes on
after...
By the way, I seem to have hit this with the earlier 2.4.x kernels, (
IIRC ), but had /so/ much problems with flaky config and flaky distros
at the time, that I didn't get that info out then ( by the time I got a
stable system, I'd forgot, sorry... )
* Tell me which kernels you want me to try ( except ext3-broken ones ),
and I'll do it, so you can scope where-the-break-is better, TIA *
-me
On Tue 17 December, 2002 7:09, you wrote:
>Is it happening with all the drives on the controller? Is it possible
> to immediaately gather the SMART data from the drive after bootup
> using smartctl?
>
>Thanks
>Manish
>
>-----Original Message-----
From: D.A.M. Revok
>To: linux-kernel@vger.kernel.org
>Sent: 12/15/02 12:49 PM
>Subject: 2.4.19, don't "hdparm -I /dev/hde" if hde is on a Asus A7V133
>Promise ctrlr, or...
>
>( that's a capital-aye in the hdparm line )
>
>not even the Magic SysReq key will work.
>
>also, don't
>
>"cd /proc/ide/hde ; cat identify"
>
>... same thing
>drive-light comes on, but have to use the power-switch to get the
>machine
>back, ( lost stuff again, fuck )
>
>
>proc says it's pdc202xx
>
>Promise Ultra series driver Ver 1.20.0.7 2002-05-23
>Adapter: Ultra100 on M/B
--
http://www.drawright.com/
- "The New Drawing on the Right Side of the Brain" ( Betty Edwards,
check "Theory", "Gallery", and "Exercises" )
http://www.ldonline.org/ld_indepth/iep/seven_habits.html
- "The 7 Habits of Highly Effective People" ( this site is same
principles as Covey's book )
http://www.eiconsortium.org/research/ei_theory_performance.htm
- "Working With Emotional Intelligence" ( Goleman: this link is
/revised/ theory, "Working. . . " is practical )
http://www.leadershipnow.com/leadershop/1978-5.html
- Corps Business: The 30 /Management Principles/ of the U.S. Marines (
David Freedman )
^ permalink raw reply
* [parisc-linux] use of the parisc logo?
From: Peter Lavender @ 2002-12-18 10:16 UTC (permalink / raw)
To: parisc
Hey Everyone,
What's the go with use of the parisc logo on web pages? Can I use it?
Thanks,
Pete
^ permalink raw reply
* Re: Howto login without PAM authentication?
From: Alex Zeffertt @ 2002-12-18 10:14 UTC (permalink / raw)
To: linuxppc-embedded@lists.linuxppc.org
In-Reply-To: <F100yCBCpIP6EeaLQBs00012c26@hotmail.com>
Enrico,
I don't know about ELDK - we're using SELF - but I suspect that it uses
busybox. If so, then just build "login" as part of busybox (to do this
you must edit the busybox/Config.in file,) then add the following line
to your /etc/inittab:
ttyS0::respawn:/sbin/login
This is what we have done and we don't have any PAM libraries on our
system at all.
Alex
PS We're using a plain /etc/password file without shadowing
On Tue, 2002-12-17 at 09:14, Enrico Serretti wrote:
>
> Hi all,
> we are using ELDK environment. We would like use login authentication
> without PAM libraries. Had anybody done it ?
>
> Thanks,
> Enrico.
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply
* Re: [patch 2.5] PCI: kill pdev_enable_device()
From: Ivan Kokshaysky @ 2002-12-18 10:11 UTC (permalink / raw)
To: Dave Jones, Jeff Garzik, Linus Torvalds, linux-kernel
In-Reply-To: <20021218004226.GA3204@suse.de>
On Wed, Dec 18, 2002 at 12:42:26AM +0000, Dave Jones wrote:
> On Tue, Dec 17, 2002 at 05:31:57PM -0500, Jeff Garzik wrote:
> > Not only that, a driver _should_ be calling pci-enable-device, it's an
> > API requirement. J Random Driver should have a good reason _not_ to
> > call pci_enable_device() ...
>
> What about the xircom issue that was discussed in the last days ?
> Sounds like the solution isn't a full on pci_enable_device() as
> pcmcia 'knows better than us' at that stage aparently.
pdev_enable_device() has nothing to do with pcmcia anyway. :-)
Ivan.
^ permalink raw reply
* problems with NFSv3 kernel 2.5.52 server, 2.4.20 client. (server x86 linux, clientsparclinux)
From: venom @ 2002-12-18 9:46 UTC (permalink / raw)
To: linux-kernel
HI,
I am having some problem with NFS v3 with kernel 2.5.52 for the NFS server and
2.4.20 as NFS client..
I was doing some extended test with an x86 server (Pentium3 933 Mhz,
with 512 MB RAM,
i810 chipset), and a client sparclinux (Sparc64 II,on an Ultra 2 single CPU,
1GB RAM).
The first test I was doing was compilation of gcc, the kernel and so on on NFS
with an async export.
(Then the day after I would have started some real stress test)
Anyway the compilation seemed to go well, and I left to go home when gcc was
compiling stage 2.
When I come back this morning NFS was still mounted, bu I could not
access any NFS mounted partyition on the sparc because of I/O error (not df
was showing the the real disk occupation on those NFS partitions, just 0).
On the server I could not find any error message, while on the sparclink client
I found:
Dec 17 18:08:16 storm kernel: call_verify: server accept status: 1
Dec 17 18:08:16 storm last message repeated 2 times
Dec 17 18:08:16 storm kernel: RPC: garbage, exit EIO
Dec 17 18:08:16 storm kernel: call_verify: server accept status: 1
Dec 17 18:08:16 storm last message repeated 2 times
Dec 17 18:08:16 storm kernel: RPC: garbage, exit EIO
Dec 17 18:08:16 storm kernel: call_verify: server accept status: 1
Dec 17 18:08:16 storm last message repeated 2 times
Dec 17 18:08:16 storm kernel: RPC: garbage, exit EIO
Dec 17 18:08:16 storm kernel: call_verify: server accept status: 1
Dec 17 18:08:16 storm last message repeated 2 times
Dec 17 18:08:16 storm kernel: RPC: garbage, exit EIO
and so on.
Those are the systems:
PentiumIII 933 Mhz
i810 chipset
512MB RAM
2 ATA66 DISK
kernel 2.5.52
glibc 2.3.1
binutils 2.13.90.0.16
gcc 3.2.1
nfs and nfsd support compiled as modules
init-modules-utils 0.9.3
in nfsd support version 4 is not enabled.
nfs-utils 1.0.1
nfsd is runned with async exports
SUN UltraII
Sparc64 II 400Mhz
1GB RAM
Creator3D video card, with DRM enabled in the kernel
PROMLIB: Sun IEEE Boot Prom 3.25.0 1999/12/03 11:35
SYSIO: UPA portID 1f, at 000001fe00000000
sbus0 with clock at 25 Mhz
kernel 2.4.20 compiled with egcs-2.92.11 (gcc2 ss-980609 experimental) 64 bit.
glibc 2.3.1 (32 bit userspace)
binutils 2.13.90.0.16
gcc 3.2.1
nfs client support compiled as modules
bests
Luigi
^ permalink raw reply
* Re: mousewheel not working.
From: Anders Fugmann @ 2002-12-18 9:31 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: linux-kernel
In-Reply-To: <20021218100733.A15491@ucw.cz>
Vojtech Pavlik wrote:
> You have to set X to handle it as ExplorerPS/2.
>
Thanks - That solves it.
Regards
Anders Fugmann
^ permalink raw reply
* [PATCH] Update MAINTAINERS for modules
From: Rusty Russell @ 2002-12-18 8:58 UTC (permalink / raw)
To: torvalds; +Cc: linux-kernel, trivial
Since it looks like Linus isn't going to rip the code out...
Cheers,
Rusty.
diff -urNp --exclude TAGS -X /home/rusty/current-dontdiff --minimal linux-2.5.52/MAINTAINERS working-2.5.52-procmodules/MAINTAINERS
--- linux-2.5.52/MAINTAINERS Tue Dec 10 15:56:46 2002
+++ working-2.5.52-procmodules/MAINTAINERS Wed Dec 18 19:54:06 2002
@@ -1124,6 +1124,12 @@ W: http://www.acc.umu.se/~mcalinux/
L: linux-kernel@vger.kernel.org
S: Maintained
+MODULE SUPPORT
+P: Rusty Russell
+M: rusty@rustcorp.com.au
+L: linux-kernel@vger.kernel.org
+S: Maintained
+
MOTION EYE VAIO PICTUREBOOK CAMERA DRIVER
P: Stelian Pop
M: stelian@popies.net
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
^ permalink raw reply
* [PATCH] /proc/modules format change
From: Rusty Russell @ 2002-12-18 9:04 UTC (permalink / raw)
To: torvalds; +Cc: linux-kernel
New extensible format uses comma-separated dependencies or "-":
ipaq 6360 0 -
usbserial 22621 1 ipaq,
usbcore 53148 2 ipaq,usbserial,
Name: /proc/modules rework
Author: Rusty Russell
Status: Tested on 2.5.52
D: This changes the dependency list in /proc/modules to be one field,
D: rather than a space-separated set of dependencies, and makes sure
D: the contents are there even if CONFIG_MODULE_UNLOAD is off.
D:
D: This allows us to append fields (eg. the module address for
D: oprofile, and the module status) without breaking userspace.
D: module-init-tools already handles this format (which you can detect
D: by the presence of "-" or "," in the fourth field).
diff -urNp --exclude TAGS -X /home/rusty/current-dontdiff --minimal linux-2.5.52/kernel/module.c working-2.5.52-procmodules/kernel/module.c
--- linux-2.5.52/kernel/module.c Tue Dec 17 08:11:03 2002
+++ working-2.5.52-procmodules/kernel/module.c Wed Dec 18 19:04:59 2002
@@ -464,19 +464,29 @@ sys_delete_module(const char *name_user,
static void print_unload_info(struct seq_file *m, struct module *mod)
{
struct module_use *use;
+ int printed_something = 0;
- seq_printf(m, " %u", module_refcount(mod));
+ seq_printf(m, " %u ", module_refcount(mod));
- list_for_each_entry(use, &mod->modules_which_use_me, list)
- seq_printf(m, " %s", use->module_which_uses->name);
+ /* Always include a trailing , so userspace can differentiate
+ between this and the old multi-field proc format. */
+ list_for_each_entry(use, &mod->modules_which_use_me, list) {
+ printed_something = 1;
+ seq_printf(m, "%s,", use->module_which_uses->name);
+ }
- if (mod->unsafe)
- seq_printf(m, " [unsafe]");
+ if (mod->unsafe) {
+ printed_something = 1;
+ seq_printf(m, "[unsafe],");
+ }
- if (!mod->exit)
- seq_printf(m, " [permanent]");
+ if (!mod->exit) {
+ printed_something = 1;
+ seq_printf(m, "[permanent],");
+ }
- seq_printf(m, "\n");
+ if (!printed_something)
+ seq_printf(m, "-");
}
void __symbol_put(const char *symbol)
@@ -517,7 +527,8 @@ EXPORT_SYMBOL_GPL(symbol_put_addr);
#else /* !CONFIG_MODULE_UNLOAD */
static void print_unload_info(struct seq_file *m, struct module *mod)
{
- seq_printf(m, "\n");
+ /* We don't know the usage count, or what modules are using. */
+ seq_printf(m, " - -");
}
static inline void module_unload_free(struct module *mod)
@@ -1400,6 +1411,7 @@ static int m_show(struct seq_file *m, vo
seq_printf(m, "%s %lu",
mod->name, mod->init_size + mod->core_size);
print_unload_info(m, mod);
+ seq_printf(m, "\n");
return 0;
}
struct seq_operations modules_op = {
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
^ permalink raw reply
* Re: mousewheel not working.
From: Vojtech Pavlik @ 2002-12-18 9:07 UTC (permalink / raw)
To: Anders Fugmann; +Cc: linux-kernel
In-Reply-To: <3DFF070A.6010804@fugmann.dhs.org>
On Tue, Dec 17, 2002 at 12:14:18PM +0100, Anders Fugmann wrote:
> Hi
>
> I'm having troubles getting the mosuewheel on my logitech ps/2 mouseman+
> (model M-C48) to work, under 2.5.52. Do I need to add something special
> to the kernel boot parameters to instruct the driver that my mouse
> carries 5 buttons?
>
> dmesg:
> device class 'input': registering
> register interface 'mouse' with class 'input'
> mice: PS/2 mouse device common for all mice
> input: PS2++ Logitech Wheel Mouse on isa0060/serio1
>
> .config
>
> CONFIG_INPUT=y
> CONFIG_INPUT_MOUSE=y
> CONFIG_MOUSE_PS2=y
> # CONFIG_MOUSE_SERIAL is not set
You have to set X to handle it as ExplorerPS/2.
--
Vojtech Pavlik
SuSE Labs
^ permalink raw reply
* Re: [PATCH] S4bios for 2.5.52.
From: Ducrot Bruno @ 2002-12-18 8:59 UTC (permalink / raw)
To: Kai Germaschewski
Cc: Grover, Andrew, 'Ducrot Bruno',
linux-kernel-u79uwXL29TY76Z2rM5mHXA, Pavel Machek,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
In-Reply-To: <Pine.LNX.4.44.0212171611460.21707-100000-+ltLZMaECS1Ps8vDFOCQiqGgjKF21WCF@public.gmane.org>
On Tue, Dec 17, 2002 at 04:14:41PM -0600, Kai Germaschewski wrote:
> On Tue, 17 Dec 2002, Grover, Andrew wrote:
>
> > > From: Ducrot Bruno [mailto:poup-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org]
> > > This patch add s4bios support for 2.5.52.
>
> > > echo 4 > /proc/acpi/sleep is for swsusp;
> > > echo 4b > /proc/acpi/sleep is for s4bios.
> >
> > I still am not clear on why we would want s4bios in 2.5.x, since we have S4.
> > Like you said, S4bios is easier to implement, but since Pavel has done much
> > of the heavy lifting required for S4 proper, I don't see the need.
>
> Let me counter this, I have to admit that I didn't try the patch yet, but
> my laptop does S4 BIOS, and I'd definitely prefer that to swsusp, since
> it's much faster and also I somewhat have more faith into S4 BIOS than
> swsusp (as in: after resuming, it'll most likely either work or crash, but
> not cause any weird kinds of corruption). Since it does not need not much
> more to support it than S3, I don't see why you wouldn't want to give
> users the option?
>
In fact, I agree with Andrew. But Pavel insist and want it,
and since it is really straightforward to have it in 2.5
because Pavel have already done all the work, why not giving
him a little gift for Christmas ?
A final word: S4bios is way much _slower_ by nature than S4OS, especially
at suspend path, which is what we don't want if we have to go to S4 due
to an emergency.
Kai, if you see that S4OS is slower, it is probably a bug that have to be
fixed in swsusp.
Cheers,
--
Ducrot Bruno
http://www.poupinou.org Page profaissionelle
http://toto.tu-me-saoules.com Haume page
^ permalink raw reply
* Re: IDE-CD and VT8235 issue!!!
From: Vojtech Pavlik @ 2002-12-18 9:03 UTC (permalink / raw)
To: AnonimoVeneziano; +Cc: linux-kernel, Patrick Petermair
In-Reply-To: <3DFDDF8C.8030609@tin.it>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
On Mon, Dec 16, 2002 at 03:13:32PM +0100, AnonimoVeneziano wrote:
> Vojtech Pavlik wrote:
>
> >On Mon, Dec 16, 2002 at 02:19:56PM +0100, AnonimoVeneziano wrote:
> >
> >
> >>>>Thanks for all your effort here. It's great to see such a good
> >>>>community.
> >>>>
> >>>>
> >>>If you can, please try 2.4.20 with this patch.
> >>>
> >>>
> >>>
> >>This patch works great!! I've solved with this patch, very good work
> >>
> >>Thank you very much Pavlik!
> >>
> >>
> >
> >Can you try another patch (on top of the previous one?)? It might still
> >work, and be less intrusive ... (attached)
> >
> >
> >
> I don't know what u have changed in this patch, but this work great too. ;-)
> Thank you very much again
One more here, if you can try it (and remove the two previous ones
first).
--
Vojtech Pavlik
SuSE Labs
[-- Attachment #2: vt8235-min --]
[-- Type: text/plain, Size: 1161 bytes --]
ChangeSet@1.884, 2002-12-18 10:01:30+01:00, vojtech@suse.cz
vt82cxxx.c IDE: Never use 1 PCICLK address setup, because new devices
choke on it.
via82cxxx.c | 5 ++++-
1 files changed, 4 insertions(+), 1 deletion(-)
diff -Nru a/drivers/ide/pci/via82cxxx.c b/drivers/ide/pci/via82cxxx.c
--- a/drivers/ide/pci/via82cxxx.c Wed Dec 18 10:01:43 2002
+++ b/drivers/ide/pci/via82cxxx.c Wed Dec 18 10:01:43 2002
@@ -286,6 +286,9 @@
* @timing: IDE timing data to use
*
* via_set_speed writes timing values to the chipset registers
+ * Note: we never use the fastest ADDRESS_SETUP timing (1 PCICLK),
+ * because although it is OK with PIO4, many modern ATAPI devices
+ * choke on it.
*/
static void via_set_speed(struct pci_dev *dev, u8 dn, struct ide_timing *timing)
@@ -293,7 +296,7 @@
u8 t;
pci_read_config_byte(dev, VIA_ADDRESS_SETUP, &t);
- t = (t & ~(3 << ((3 - dn) << 1))) | ((FIT(timing->setup, 1, 4) - 1) << ((3 - dn) << 1));
+ t = (t & ~(3 << ((3 - dn) << 1))) | ((FIT(timing->setup, 2, 4) - 1) << ((3 - dn) << 1));
pci_write_config_byte(dev, VIA_ADDRESS_SETUP, t);
pci_write_config_byte(dev, VIA_8BIT_TIMING + (1 - (dn >> 1)),
^ permalink raw reply
* Re: [PATCH] S4bios for 2.5.52.
From: Ducrot Bruno @ 2002-12-18 8:59 UTC (permalink / raw)
To: Kai Germaschewski
Cc: Grover, Andrew, 'Ducrot Bruno', linux-kernel,
Pavel Machek, acpi-devel
In-Reply-To: <Pine.LNX.4.44.0212171611460.21707-100000@chaos.physics.uiowa.edu>
On Tue, Dec 17, 2002 at 04:14:41PM -0600, Kai Germaschewski wrote:
> On Tue, 17 Dec 2002, Grover, Andrew wrote:
>
> > > From: Ducrot Bruno [mailto:poup@poupinou.org]
> > > This patch add s4bios support for 2.5.52.
>
> > > echo 4 > /proc/acpi/sleep is for swsusp;
> > > echo 4b > /proc/acpi/sleep is for s4bios.
> >
> > I still am not clear on why we would want s4bios in 2.5.x, since we have S4.
> > Like you said, S4bios is easier to implement, but since Pavel has done much
> > of the heavy lifting required for S4 proper, I don't see the need.
>
> Let me counter this, I have to admit that I didn't try the patch yet, but
> my laptop does S4 BIOS, and I'd definitely prefer that to swsusp, since
> it's much faster and also I somewhat have more faith into S4 BIOS than
> swsusp (as in: after resuming, it'll most likely either work or crash, but
> not cause any weird kinds of corruption). Since it does not need not much
> more to support it than S3, I don't see why you wouldn't want to give
> users the option?
>
In fact, I agree with Andrew. But Pavel insist and want it,
and since it is really straightforward to have it in 2.5
because Pavel have already done all the work, why not giving
him a little gift for Christmas ?
A final word: S4bios is way much _slower_ by nature than S4OS, especially
at suspend path, which is what we don't want if we have to go to S4 due
to an emergency.
Kai, if you see that S4OS is slower, it is probably a bug that have to be
fixed in swsusp.
Cheers,
--
Ducrot Bruno
http://www.poupinou.org Page profaissionelle
http://toto.tu-me-saoules.com Haume page
^ permalink raw reply
* [LARTC] nano.txt
From: hare ram @ 2002-12-18 8:48 UTC (permalink / raw)
To: lartc
[-- Attachment #1: Type: text/plain, Size: 139 bytes --]
Hi
does any one have this File
seems to be this site is down
http://www.linuxvirtualserver.org/~julian/#routes-2.4
thanks
hare
[-- Attachment #2: Type: text/html, Size: 871 bytes --]
^ permalink raw reply
* Re: lk maintainers
From: Denis Vlasenko @ 2002-12-18 13:24 UTC (permalink / raw)
To: Zwane Mwaikambo; +Cc: linux-kernel
In-Reply-To: <Pine.LNX.4.50.0212180227100.8420-100000@montezuma.mastecende.com>
On 18 December 2002 05:29, Zwane Mwaikambo wrote:
> On Wed, 18 Dec 2002, Denis Vlasenko wrote:
> > > > Eric S. Raymond <esr@thyrsus.com> [5 feb 2002]
> > > > Send kernel configuration bug reports and suggestions to me.
> > > > Also I'll be more than happy to accept help enties for kernel
> > > > config options (Configure.help).
> > >
> > > Can't say i've seen this fellow in a while either.
> >
> > If 'lk maintainers' will get excessively long, I'll start pruning.
> > Do you think I should do it now?
>
> If it's supposed to be current information and to be used by bug
> reporters, then by all means, chop away ;)
It is suppsed to be accurate. That is why there are timestamps.
OTOH I should mark some entries <no longer true>, also with timestamp.
--
vda
^ permalink raw reply
* Re: Am I burning my Compaq 700EA ?
From: Vittorio Ballestra @ 2002-12-18 8:41 UTC (permalink / raw)
To: Frederic.Parrenin-uJC2I/HWIrG1lNqXp+/2b1AUjnlXr6A1
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
In-Reply-To: <1040197383.2035.6.camel-EOLtR9nHC0w7VkuvlHBOUdBf7emC4R2pl6ge6I993lI@public.gmane.org>
Alle 08:43, mercoledì 18 dicembre 2002, hai scritto:
> Hi Vittorio,
>
>
> I am not an acpi expert, but I had a similar problem with my laptop.
>
> > Second:
> > /proc/acpi/thermal_zone is there but empty. Is it Ok ? If not someone
> > knows how to fix it ? (I'm a bit worried 'bout this).
>
> For me, it was the battery and ac_adaptatot that were empty. It came
> from a buggy implementation of acpi in the Bios : my dsdt table was
> wrong. A nice gye has of the acpi-devel list looked at my
> /proc/acpi/dsdt file, and he gave me a patch to have acpi fully working.
>
Thank you for your hint. I'll try to disassemble the DSDT table and understand
it, but it will take a long time as I don't have much spare time for it...
hope in the meanwhile I'm not going to cook my compaq... or some other good
guy will give me a hand...
> For your thermal zone, try to charge your CPU and look if the fan work
> correctly. (What is your processor ? Pentium 4 ?)
>
Fan is working (running mplayer or recompiling the kernel will make it work).
Don't know how well though ...
Throttling works (manual changing the throttling state will do, don't know if
it will change automatically).
My processor is an AMD Athlon 4 1500+
> > Third:
> > acpid is not working (I've not applied the apcpid.patch, thought it was
> > integrated ...). Is this a real problem or the only side-effect is that
> > power button will not work ?
>
> If you try to start acpid, do you have an error message ?
no, but buttons are not working. I didn't want to recompile only because I've
forgotten to apply the acpid.patch that's why I asked if it was important ...
>
> Regards.
>
> Frederic
>
> > -------------------------------------------------------
> > This sf.net email is sponsored by:
> > With Great Power, Comes Great Responsibility
> > Learn to use your power at OSDN's High Performance Computing Channel
> > http://hpc.devchannel.org/
> > _______________________________________________
> > Acpi-devel mailing list
> > Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > https://lists.sourceforge.net/lists/listinfo/acpi-devel
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.