All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: Linux Performance
From: Dave Johnson @ 2004-01-26 13:48 UTC (permalink / raw)
  To: Wolfgang Denk; +Cc: linuxppc-embedded
In-Reply-To: <20040123000415.E219AC10AF@atlas.denx.de>


Caches are already enabled.

Dave..

--- Wolfgang Denk <wd@denx.de> wrote:
> In message
> <20040122204828.62134.qmail@web21405.mail.yahoo.com>
> you wrote:
> >
> > I am running MV3.1 Linux on a MPC8270 based custom
> > board. I ran LMbench2 on my board and got these
> > numbers (file attached). Also I have high
> interrupt
>
> Attachment missing.
>
> > Also these numbers dont look good either. Are
> there
> > any tricks which can be played to enhance kernel
> > performance??
>
> Turn on the caches?
>
>
> Wolfgang Denk
>
> --
> See us @ Embedded World, Nuremberg, Feb 17 - 19,
> Hall 12.0 Booth 440
> Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88
> Email: wd@denx.de
> "You know, after a woman's raised a family and so
> on,  she  wants  to
> start living her own life."   "Whose life she's
> _been_ living, then?"
>                                   - Terry Pratchett,
> _Witches Abroad_


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply

* Re: [Linux-ATM-General] Announcement: MPHY now supported in mpc860sar
From: Gilad Rom @ 2004-01-26 13:51 UTC (permalink / raw)
  To: Alex Zeffertt, linux-atm-general, linuxppc-embedded
In-Reply-To: <1075117282.1504.17.camel@zambia.cambridgebroadband.com>


This is very exciting news! (well, for me it is)

How many PHY's in parallel are we talking about here?

Thanks,
Gilad.


----- Original Message -----
From: "Alex Zeffertt" <ajz@cambridgebroadband.com>
To: <linux-atm-general@lists.sourceforge.net>;
<linuxppc-embedded@lists.linuxppc.org>
Sent: Monday, January 26, 2004 1:41 PM
Subject: [Linux-ATM-General] Announcement: MPHY now supported in mpc860sar


> Just a quick note to say that multi-phy is now supported by the
> mpc860sar ATM driver, thanks to a patch by Rodolfo Giometti.
>
> Page: http://sourceforge.net/projects/mpc860sar/
>
> Alex
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Linux-atm-general mailing list
> Linux-atm-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-atm-general
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply

* REISER4 corruptions errors
From: Paolo Correnti @ 2004-01-26 13:52 UTC (permalink / raw)
  To: Nikita Danilov; +Cc: REISER LIST
In-Reply-To: <20040123151214.56545.qmail@web21503.mail.yahoo.com>

In my last message "REISER4 strange partition size"
I wrote:

"... making intensive writing test on this
reiser4 partition (for example: writing 1 million rows
on an Oracle table in archivelog mode) on each test I
obtain a corrupted redolog file [sometimes is
recoverable, sometimes I've to rebuild the entire
DB)."

And Nikita answered:

"It is not clear how to diagnose this. What oracle
are you using? Is it available freely?"

Really I think this test is not so easy to prepare
(you have to download Oracle, install it and bla bla
...) but I think my last test is more "human".

I recomplied Kernel 2.6.0 with
CONFIG_REISER4_BADBLOCKS=y

I'm using 2.6.0 + 20031223 snapshot because 
2.6.1 + 20040119_fixed always gives me some file
corrupted and I was spending too much time re-creating
Oracle DB.

Reiser4 partition is mounted with tmgr.atom_max_age=20
option.

I noticed that if you copy a large amount of data (at
least 500 Mb) from a partition to a Reiser4 partition,
umounting Reiser4 part and using fsck.reiser4
you always obtain from 5 to 40 (and more) fixable
corruptions detected.

It seems that with 2.6.0 + 20031223 snapshot these
corruptions are not so "dangerous" to corrupt files
(I mean, also with these corruptions I'm able to work
with Oracle). Unfortunately I cannot say the same
with 2.6.1 and latest snapshot.

Any idea ?

All the best

Paolo






__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/

^ permalink raw reply

* Re: troubles programming with the sequencer
From: Clemens Ladisch @ 2004-01-26 13:52 UTC (permalink / raw)
  To: Brix; +Cc: alsa-devel
In-Reply-To: <20040123190532.1f335a80.brix82@libero.it>

Brix wrote:
> My code doesn't return any error, i just can't hear anything. If i
> do it via the RawMIDI API, it works fine (but it's, bleahh,
> horrible to use).
>
> I thought it was because i didn't assign any path/instrument to
> the midi channels,

The default instrument is 0 (grand piano).

> so i tried to set them via RawMIDI, but it still doesn't work.

You can send program change messages with the sequencer, too.

> void set_chan_instr( int chan, int instrument ) {
>   int ch = 0xC0 + chan;
>   snd_rawmidi_write(handle_out, &ch, 1);

This does not work on big-endian machines, use char for ch.

>   // now we try to set up channel 0 via RawMIDI
>   snd_rawmidi_open( NULL, &handle_out, "hw:0,1", 0)
>   // ok, let's assign instrument #4
>   set_chan_instr( 0, 4 );

If the rawmidi device is already opened, it may not be possible for
the sequencer to open it, too.  Call snd_rawmidi_close, or leave this
code out altogether.

>   // let's play! (we hope..)
>   snd_seq_event_output(seq, &ev);
>   snd_seq_drain_output(seq);
>   snd_seq_start_queue(seq, queue, NULL);
>   snd_seq_drain_output(seq);
>
>   return 0;
> }

Directly after starting the queue, the program exists, and the queue
gets destroyed.  Try snd_seq_sync_output.


HTH
Clemens




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

^ permalink raw reply

* [PATCH] possible fix for misbehaving hdsp
From: Thomas Charbonnel @ 2004-01-26 13:54 UTC (permalink / raw)
  To: alsa-devel, Paul Davis, Tim Blechmann

[-- Attachment #1: Type: text/plain, Size: 120 bytes --]

Hi,

Could people experiencing problems with their hdsp (namely Tim and Paul) 
try the attached patch ?

Thanks,
Thomas

[-- Attachment #2: pci_latency_timer.patch --]
[-- Type: text/plain, Size: 762 bytes --]

--- hdsp.c.old	2004-01-26 14:34:48.000000000 +0100
+++ hdsp.c	2004-01-26 14:51:18.000000000 +0100
@@ -4982,6 +4982,16 @@
 	tasklet_init(&hdsp->midi_tasklet, hdsp_midi_tasklet, (unsigned long)hdsp);
 	
 	pci_read_config_word(hdsp->pci, PCI_CLASS_REVISION, &hdsp->firmware_rev);
+	
+	/* From Martin Björnsen :
+	    "It is important that the card's latency timer register in
+	    the PCI configuration space is set to a value much larger
+	    than 0 by the computer's BIOS or the driver.
+	    The windows driver always sets this 8 bit register [...]
+	    to its maximum 255 to avoid problems with some computers."
+	*/
+	pci_write_config_byte(hdsp->pci, PCI_LATENCY_TIMER, 0xFF);
+	
 	strcpy(card->driver, "H-DSP");
 	strcpy(card->mixername, "Xilinx FPGA");
 

^ permalink raw reply

* Re: [RFC/PATCH] IMQ port to 2.6
From: Vladimir B. Savkin @ 2004-01-26 13:55 UTC (permalink / raw)
  To: jamal; +Cc: linux-kernel, netdev
In-Reply-To: <1075124312.1732.292.camel@jzny.localdomain>

On Mon, Jan 26, 2004 at 08:38:33AM -0500, jamal wrote:
> On Mon, 2004-01-26 at 04:32, Vladimir B. Savkin wrote:
> 
> > On Sun, Jan 25, 2004 at 10:09:48PM -0500, jamal wrote:
> [..]
> > > shape). I have not seen anything in favor of shaping; i could be wrong
> > > (so if you know of something or have experimented pass the data).
> > 
> > Yes, I have experimented. Shaping works much better:
> > much less packets dropped, much better donwload rates for clients.
> > 
> 
> I cant say i doubt you, but your word alone is insufficient data ;->

You can see for youself. Police users' traffic to half of the normal rate
and here them scream :) Then change policing to shaping using wrr
(or htb class for each user), and sfq on the leafs, and users are happy.

> The important point is the eventual effective throughput and fairness
> amongst the flows. Whether it is induced by an increased RTT from
> shaping or a single packet retransmit on some misbehaving flows because
> of policing is less important. i.e it is not evil for packets to
> be dropped.
> When you analyse something like this you should look at the aggregate
> throughput instead of a single client with better downloads (probably at
> the expense of another poor client download).

Well, I use wrr + sfq exactly for fairness. No such thing can be
achieved with policing only.

> 
> > I want to shape traffic that comes from upstream to clients connected
> > via PPTP.
> 
> So if i understand correctly and was to draw this: 
> you have clients on the left side coming in through ethx and that need
> to be tunneled to some pppoe/pptp before going out ethy on the right
> hand side. The right handside represents "upstream" in your terminology.
> Is this correct? I hate it when people ask me for a diagram for
> something that looks obvious;-> but bear with me and supply me with a
> diagram if i didnt understand you.

Here it is:

                    +---------+       +-ppp0- ... - client0
                    |         +-eth1-<+-ppp1- ... - client1
Internet ----- eth0-+ router  |     . . . . . . . .
                    |         +-eth2-<  . . . . . .
                    +---------+       +-pppN- ... - clientN
		    

Traffic flows from internet to clients. 
The ethX names are for example only, my setup is more complex actually,
but that complexity is not related to IMQ or traffic shaping.
Clients use PPTP or PPPoE to connect to router.
See, there's no single interface I can attach qdisc to, if I want
to put all clients into the same qdisc. 

> 
> > 
> > Here is a part of my scripts:
> > 
> > DEVICE=imq0
> > /sbin/tc qidisc add dev $DEVICE root handle 10: htb r2q 1 default 100
> > /sbin/tc class add dev $DEVICE parent 10:0 classid 10:1 est 1sec 8sec htb \
> >         rate 10Mbit burst 400k
> > /sbin/tc class add dev $DEVICE parent 10:1 classid 10:2 est 1sec 8sec htb \
> >         rate 180kbps ceil 180kbps burst 3000
> > # default class for users
> > /sbin/tc class add dev $DEVICE parent 10:2 classid 10:101 est 1sec 8sec htb \
> >         rate 20kbps burst 1k ceil 50kbps cburst 1k
> > /sbin/tc qdisc add dev $DEVICE parent 10:101 wrr \
> >         dest ip 128 1 wmode1=1 wmode2=1
> > /sbin/tc filter add dev $DEVICE protocol ip parent 10:0 \
> >         prio 100 handle 1 fw flowid 10:101
> > # more classes to follow ...
> > 
> 
> So why not have the above attached to ethy? Why does it have to be done
> at some other device?
> 
> > 
> > The limit 50kbps is artificial, so there's no bottleneck in
> > connection from upstream to this router. I cannot allocate all
> > the channel bandwidth to clients for some political reasons.
> > Then, I mark packets I want to go to this default user class with mark "1",
> > like this:
> > 
> > iptables -t mangle -A FORWARD -i $UPLINK_DEV -d $CLIENTS_NET \
> > 	-j IMQ --todev 0 # traffic from internet to clients
> > iptables -t mangle -A FORWARD -i $UPLINK_DEV -d $CLIENTS_NET \
> > 	-j MARK --set-mark 1 # default class
> 
> 
> Why do you need the redirect to IMQ?
> If you can selectively mark packets here (or at any other netfilter
> hook) you could use the fwmark classifier to attach to different
> 10:x classes on the ethy interface. I feel i am missing something.
> 
> > So, I shape traffic destined to clients, and I use "wrr" to
> > divide bandwidth fairly. I cannot attach qdisc to an egress device
> > because there's no single one, each client has its own ppp interface.
> > 
> 
> I mean the ethy interface not the ppp* interfaces. Mark the packets;
> use fwmark classifier.
> 
> > Well, I could move this shaping upstream, but what if upstream router was
> > some dumb cisco with no "wrr" qdisc? 
> 
> You dont have to.
> Give me the diagram.
> 
> cheers,
> jamal
> 
~
:wq
                                        With best regards, 
                                           Vladimir Savkin. 


^ permalink raw reply

* Re: sequencer filter client
From: Clemens Ladisch @ 2004-01-26 13:57 UTC (permalink / raw)
  To: Garett Shulman; +Cc: alsa-devel
In-Reply-To: <4011916D.4040601@colorado.edu>

Garett Shulman wrote:
> Hello, I am trying to create a very simple midi filter client for the
> alsa sequencer based on aseqview-0.1.4. I have alsa 0.9.8. This code
> shows the input and the output port in aconnect when executed. And, when
> the raw_midi client is connected The callback does get called when I
> play keys on my piano. However, Its as though the message is getting
> sent back to this client and  not on to the next client.
>
> int process_event(port_t *p, int type, snd_seq_event_t *ev, int *priate_data)
> {
>     port_write_event(p, ev, 0);
> }

The event will be sent to the destination as specified in ev->dest.
For events you have just received, the destination is your own
client/port.

Call snd_seq_ev_set_source(ev, ?) to set your source port, and call
snd_seq_ev_set_subs(ev) to specify that the event is to be sent to all
ports subscribed to your port.


HTH
Clemens




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

^ permalink raw reply

* Re: udev.rules woes
From: Kay Sievers @ 2004-01-26 13:59 UTC (permalink / raw)
  To: linux-hotplug
In-Reply-To: <20040123185637.GA2431@Benine>

On Fri, Jan 23, 2004 at 08:56:37PM +0200, Guido Schimmels wrote:
> 
> To reproduce my static /dev with udev, I tried and replaced:
> 
> BUS="ide", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="cdrom",  
> NAME="%k", SYMLINK="cdrom"
> 
> with:
> 
> BUS="ide", PROGRAM="/bin/cat /proc/ide/hdc/media", RESULT="cdrom",  
> NAME="hdc", SYMLINK="cdrom"
> 
> Looks innocent enough, but triggers completely unexpected behaviour.
> It makes __all__ IDE device nodes disappear, except /dev/hdc and /dev/ 
> cdrom symlinked to it.

No, it doesn't look innocent, in any kind :) You ask for _every_ ide
device "if hdc is a cdrom" and if yes please give it the name 'hdc'.
The first rule matches every time.

Why not stick with the provided example? It just works.
If you want your own rules, you may add KERNEL= to the rule.

thanks,
Kay


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

^ permalink raw reply

* Re: [Linux-ATM-General] Announcement: MPHY now supported in mpc860sar
From: Alex Zeffertt @ 2004-01-26 13:59 UTC (permalink / raw)
  To: Gilad Rom
  Cc: linux-atm-general@lists.sourceforge.net,
	linuxppc-embedded@lists.linuxppc.org
In-Reply-To: <019201c3e413$7f45d3a0$026810ac@gilad>


It is currently only supported in SAR mode, and in that mode there is an
upper limit of 4 UTOPIA phys.  However, there's no reason that support
can't be added for MPHY in ESAR mode - in which the limit is 31 phys.  I
suspect that adding such support would be easier now that Rodolfo has
done most of the work.

Alex

PS I'm not the expert on this.  Rodolfo's sourceforge username is
"zaigor".

On Mon, 2004-01-26 at 13:51, Gilad Rom wrote:
> This is very exciting news! (well, for me it is)
>
> How many PHY's in parallel are we talking about here?
>
> Thanks,
> Gilad.
>
>
> ----- Original Message -----
> From: "Alex Zeffertt" <ajz@cambridgebroadband.com>
> To: <linux-atm-general@lists.sourceforge.net>;
> <linuxppc-embedded@lists.linuxppc.org>
> Sent: Monday, January 26, 2004 1:41 PM
> Subject: [Linux-ATM-General] Announcement: MPHY now supported in mpc860sar
>
>
> > Just a quick note to say that multi-phy is now supported by the
> > mpc860sar ATM driver, thanks to a patch by Rodolfo Giometti.
> >
> > Page: http://sourceforge.net/projects/mpc860sar/
> >
> > Alex
> >
> >
> >
> > -------------------------------------------------------
> > The SF.Net email is sponsored by EclipseCon 2004
> > Premiere Conference on Open Tools Development and Integration
> > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> > http://www.eclipsecon.org/osdn
> > _______________________________________________
> > Linux-atm-general mailing list
> > Linux-atm-general@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/linux-atm-general
> >


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply

* Re: REISER4 corruptions errors
From: Nikita Danilov @ 2004-01-26 13:59 UTC (permalink / raw)
  To: Paolo Correnti; +Cc: REISER LIST
In-Reply-To: <20040126135218.20053.qmail@web21506.mail.yahoo.com>

Paolo Correnti writes:
 > In my last message "REISER4 strange partition size"
 > I wrote:
 > 
 > "... making intensive writing test on this
 > reiser4 partition (for example: writing 1 million rows
 > on an Oracle table in archivelog mode) on each test I
 > obtain a corrupted redolog file [sometimes is
 > recoverable, sometimes I've to rebuild the entire
 > DB)."
 > 
 > And Nikita answered:
 > 
 > "It is not clear how to diagnose this. What oracle
 > are you using? Is it available freely?"
 > 
 > Really I think this test is not so easy to prepare
 > (you have to download Oracle, install it and bla bla
 > ...) but I think my last test is more "human".
 > 
 > I recomplied Kernel 2.6.0 with
 > CONFIG_REISER4_BADBLOCKS=y
 > 
 > I'm using 2.6.0 + 20031223 snapshot because 
 > 2.6.1 + 20040119_fixed always gives me some file
 > corrupted and I was spending too much time re-creating
 > Oracle DB.
 > 
 > Reiser4 partition is mounted with tmgr.atom_max_age=20
 > option.
 > 
 > I noticed that if you copy a large amount of data (at
 > least 500 Mb) from a partition to a Reiser4 partition,
 > umounting Reiser4 part and using fsck.reiser4
 > you always obtain from 5 to 40 (and more) fixable
 > corruptions detected.
 > 
 > It seems that with 2.6.0 + 20031223 snapshot these
 > corruptions are not so "dangerous" to corrupt files
 > (I mean, also with these corruptions I'm able to work
 > with Oracle). Unfortunately I cannot say the same
 > with 2.6.1 and latest snapshot.

Well, for all I know, this very well may be a bug in the fsck, rather
than corruption of the on-disk data structures. Are you experiencing any
problems when _using_ this partition (error messages in the kernel log,
crashes, deadlocks, etc.)?

 > 
 > Any idea ?
 > 
 > All the best
 > 
 > Paolo
 >

Nikita.

^ permalink raw reply

* nforce2 ethernet driver
From: cityhunter @ 2004-01-26 14:00 UTC (permalink / raw)
  To: netdev, c-d.hailfinger.kernel.2004

hello,
I found that you writed a kernel module for nvdia nforce ethenet.
your site have a lot of kernel patch for the "forcedeth.c" file that I 
can't find in my 2.6.1 kernel archive....
can you tell me where to get it?
thx
JLM

^ permalink raw reply

* Re: [Linux-ATM-General] Announcement: MPHY now supported inmpc860sar
From: Gilad Rom @ 2004-01-26 14:03 UTC (permalink / raw)
  To: Alex Zeffertt; +Cc: linux-atm-general, linuxppc-embedded
In-Reply-To: <1075125571.1504.28.camel@zambia.cambridgebroadband.com>


Okay. Thanks.

And now for my next question - Do you think the driver
should run on the 82xx family of chips? (e.g. 8260 and the likes)
these guys have 2 Utopia-II ports with support for up to 31 devices
per port. Coupled with this software, it could make for a highly
efficient DSLAM.

Gilad.

----- Original Message -----
From: "Alex Zeffertt" <ajz@cambridgebroadband.com>
To: "Gilad Rom" <gilad@romat.com>
Cc: <linux-atm-general@lists.sourceforge.net>;
<linuxppc-embedded@lists.linuxppc.org>
Sent: Monday, January 26, 2004 3:59 PM
Subject: Re: [Linux-ATM-General] Announcement: MPHY now supported
inmpc860sar


> It is currently only supported in SAR mode, and in that mode there is an
> upper limit of 4 UTOPIA phys.  However, there's no reason that support
> can't be added for MPHY in ESAR mode - in which the limit is 31 phys.  I
> suspect that adding such support would be easier now that Rodolfo has
> done most of the work.
>
> Alex
>
> PS I'm not the expert on this.  Rodolfo's sourceforge username is
> "zaigor".
>
> On Mon, 2004-01-26 at 13:51, Gilad Rom wrote:
> > This is very exciting news! (well, for me it is)
> >
> > How many PHY's in parallel are we talking about here?
> >
> > Thanks,
> > Gilad.
> >
> >
> > ----- Original Message -----
> > From: "Alex Zeffertt" <ajz@cambridgebroadband.com>
> > To: <linux-atm-general@lists.sourceforge.net>;
> > <linuxppc-embedded@lists.linuxppc.org>
> > Sent: Monday, January 26, 2004 1:41 PM
> > Subject: [Linux-ATM-General] Announcement: MPHY now supported in
mpc860sar
> >
> >
> > > Just a quick note to say that multi-phy is now supported by the
> > > mpc860sar ATM driver, thanks to a patch by Rodolfo Giometti.
> > >
> > > Page: http://sourceforge.net/projects/mpc860sar/
> > >
> > > Alex
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > The SF.Net email is sponsored by EclipseCon 2004
> > > Premiere Conference on Open Tools Development and Integration
> > > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> > > http://www.eclipsecon.org/osdn
> > > _______________________________________________
> > > Linux-atm-general mailing list
> > > Linux-atm-general@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/linux-atm-general
> > >
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply

* Re: Wrong Synaptics Touchpad detection when USB mouse present
From: Mattia Dongili @ 2004-01-26 14:09 UTC (permalink / raw)
  To: Vojtech Pavlik; +Cc: Linux Kernel Mailing List
In-Reply-To: <20040126130952.GA26596@ucw.cz>

On Mon, Jan 26, 2004 at 02:09:52PM +0100, Vojtech Pavlik wrote:
> On Mon, Jan 26, 2004 at 01:17:49PM +0100, Mattia Dongili wrote:
> > Hi,
> > 
> > [Please Cc me as I'm not subscribed to the list]
> > 
> > I'm experiencing problems with a dual configuration of mice on my
> > laptop. The sympthoms are:
> > 
> > - if I boot with my Logitech USB mouse plugged in, the Synaptics
> >   Touchpad is not recognized as such but as "PS/2 Generic Mouse"
> > 
> > - if I boot without USB mouse plugged in or if I simply reload psmouse
> >   after the boot process, the Synaptics Touchpad is recognized correctly
> > 
> > So it has something to do with the order modules are loaded.
> 
> Load the USB modules first. It's your BIOS intervening. Or disable USB
> Mouse support or USB Legacy support in the BIOS.

Unfortunately I have no such options on my bios (Sony Vaio GR7/K -
PhoenixBIOS 4.0 Release 6.0 - R0208C0).

Anyway I solved this problem loading uhci_hcd + hid before
psmouse in /etc/modules

Thanks for your help
-- 
mattia
:wq!

^ permalink raw reply

* Re: hdsp vs 16bit vs dmix
From: Thomas Charbonnel @ 2004-01-26 14:10 UTC (permalink / raw)
  To: Jaroslav Kysela; +Cc: Takashi Iwai, Patrick Shirkey, alsa-devel
In-Reply-To: <Pine.LNX.4.58.0401261415070.2959@pnote.perex-int.cz>

Jaroslav Kysela wrote :
> On Mon, 26 Jan 2004, Thomas Charbonnel wrote:
> 
> 
>>Now if you do specify 'channels 18' in the dmix slave definition, the 
>>error is as follows :
>>aplay: set_params:827: Sample format non available
>>I have 'format S32_LE' set in the dmix slave definition, but it doesn't 
>>seem to be taken into account.
> 
> 
> It should be. Did you used 'aplay -D plug:your_dmix'?
> 
> 						Jaroslav
> 

You're right, I only used '-D my_dmix'.
Using '-D plug:my_dmix' works properly, so I guess the problem is 
solved, thanks !

For the record here's the working .asoundrc section :

pcm.hdsp_dmix {
     type dmix
     ipc_key 1024
     slave {
         pcm {
             type hw
             card 2
         }
         rate 44100
         format S32_LE
         channels 18
     }
}

Of course people will have to tweak the card and channels number to 
match their setup.

Thomas




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

^ permalink raw reply

* Re: PROBLEM: ACPI freezes 2.6.1 (acpi-20031203-2.6.1 patched) on boot
From: Sérgio Monteiro Basto @ 2004-01-26 14:11 UTC (permalink / raw)
  To: Sebastian Henschel; +Cc: acpi-devel, greve-mXXj517/zsQ
In-Reply-To: <20040122085958.GA1244-5sK/Rx+du8M@public.gmane.org>

On Thu, 2004-01-22 at 08:59, Sebastian Henschel wrote:
> hi georg...
> 
> * "Georg C. F. Greve" <greve-mXXj517/zsQ@public.gmane.org> [2004-01-21 13:27 +0100]:
> > 
> > FYI: below is my problem report about ACPI freezing my ASUS M2N on
> > boot with plain vanilla Linux 2.6.1.
> > 
> > As a possible way of solving the problem I've tried the patch
> > acpi-20031203-2.6.1.diff.bz2 with date 09-Jan-2004 (have to admit the
> > version numbering isn't clear to me) I get a different error message
> > 
> >  ACPI: IRQ9 SCI: Edge set to Level Trigger.
> > 
> > However, this still appears to be the same problem.
> 
> two things come to my mind:
> 
> - disable Local- and IO-APIC. try "noapic" as boot parameter or even
>   disable it completely in .config file.
> - upgrade your bios, i think 0206 is the latest.

or try propose patch on 
http://bugzilla.kernel.org/show_bug.cgi?id=1269

in this case Greve already try it with success on (
http://bugzilla.kernel.org/show_bug.cgi?id=1774 )

thanks 

-- 
Sérgio M B




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

^ permalink raw reply

* New linux box
From: S. Barret Dolph @ 2004-01-26 14:13 UTC (permalink / raw)
  To: linux-newbie

Well, my problems have much to do with hardware and it is time to get a new 
box. My old box ran for 6 years with Mandrake and never crashed. (X-windows 
crashed when setting up Matrox 450 though.) My question is what hardware is 
good to avoid. I only use my computer for work, no games, but I am on it at 
least 6 hours or more a day. I care mostly about stability and don't really 
care too much about speed. So more to the point are any of you aware of 
hardware that is a nightmare to install. Or a site which can help.

Cordially,
S. Barret Dolph
Taipei Taiwan
-
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: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED
From: John Stoffel @ 2004-01-26 14:12 UTC (permalink / raw)
  To: Andi Kleen
  Cc: Andrew Morton, John Stoffel, Valdis.Kletnieks, bunk, cova, eric,
	linux-kernel
In-Reply-To: <20040126060952.GC6519@colin2.muc.de>


Andi> On Sun, Jan 25, 2004 at 10:00:27PM -0800, Andrew Morton wrote:
>> "John Stoffel" <stoffel@lucent.com> wrote:
>> >
>> > Sure, the darn thing wouldn't boot, it kept Oopsing with the
>> >  test_wp_bit oops (that I just posted more details about).
>> 
>> Does this fix the test_wp_bit oops?

Andi> He apparently doesn't have an test_wp_bit oops, but just an hang
Andi> very early (after mem_init according to early printk)

Just to follow up here.  On kernels 2.6.2-rc1 and 2.6.2-rc2, it just
hangs on bootup and doesn't give any Oops output.

When I tried out 2.6.2-rc1-mm[1,2,3], it would start booting, but
oops immediately with the one I posted before, but I've re-created
here.  

I'm at work now, so I won't be able to do any tests besides remote
kernel compiles during the day.

My plan is to apply the patch from Andrew where sort_main_extable() is
moved up above mem_init() to both 2.6.2-rc2 and to 2.6.2-rc1-mm3 and
see what happens.

Here's my .config for 2.6.2-rc1-mm3:

#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
# CONFIG_CLEAN_COMPILE is not set
CONFIG_STANDALONE=y
CONFIG_BROKEN=y
CONFIG_BROKEN_ON_SMP=y

#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_IKCONFIG is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set

#
# Processor support
#

#
# Select all processors your kernel should support
#
# CONFIG_CPU_386 is not set
CONFIG_CPU_486=y
CONFIG_CPU_586=y
CONFIG_CPU_586TSC=y
CONFIG_CPU_586MMX=y
CONFIG_CPU_686=y
CONFIG_CPU_PENTIUMII=y
CONFIG_CPU_PENTIUMIII=y
# CONFIG_CPU_PENTIUMM is not set
# CONFIG_CPU_PENTIUM4 is not set
# CONFIG_CPU_K6 is not set
# CONFIG_CPU_K7 is not set
# CONFIG_CPU_K8 is not set
# CONFIG_CPU_CRUSOE is not set
# CONFIG_CPU_WINCHIPC6 is not set
# CONFIG_CPU_WINCHIP2 is not set
# CONFIG_CPU_WINCHIP3D is not set
# CONFIG_CPU_CYRIXIII is not set
# CONFIG_CPU_VIAC3_2 is not set
CONFIG_CPU_INTEL=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_F00F_BUG=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_ALIGNMENT_16=y
CONFIG_X86_BAD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
# CONFIG_X86_4G is not set
# CONFIG_X86_SWITCH_PAGETABLES is not set
# CONFIG_X86_4G_VM_LAYOUT is not set
# CONFIG_X86_UACCESS_INDIRECT is not set
# CONFIG_X86_HIGH_ENTRY is not set
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_SMP=y
CONFIG_NR_CPUS=8
# CONFIG_SCHED_SMT is not set
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_MATH_EMULATION=y
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM is not set

#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_ASUS=m
CONFIG_ACPI_TOSHIBA=m
CONFIG_ACPI_DEBUG=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_RELAXED_AML is not set
# CONFIG_X86_PM_TIMER is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_USE_VECTOR is not set
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
CONFIG_PCMCIA_PROBE=y

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y

#
# Device Drivers
#

#
# Generic Driver Options
#
# CONFIG_FW_LOADER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play support
#
CONFIG_PNP=y
CONFIG_PNP_DEBUG=y

#
# Protocols
#
CONFIG_ISAPNP=y
CONFIG_PNPBIOS=y
# CONFIG_PNPBIOS_PROC_FS is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
CONFIG_BLK_DEV_NBD=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_LBD=y

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_TASKFILE_IO is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_MAX_SD_DISKS=16
CONFIG_CHR_DEV_ST=y
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_REPORT_LUNS=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AACRAID is not set
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=32
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_BUILD_FIRMWARE is not set
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX_CONFIG=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA23XX is not set
# CONFIG_SCSI_SEAGATE is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
CONFIG_MD_RAID5=y
# CONFIG_MD_RAID6 is not set
# CONFIG_MD_MULTIPATH is not set
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_IOCTL_V4 is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
CONFIG_IEEE1394=m

#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
CONFIG_IEEE1394_OUI_DB=y

#
# Device Drivers
#

#
# Texas Instruments PCILynx requires I2C
#
CONFIG_IEEE1394_OHCI1394=m

#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
# CONFIG_IEEE1394_ETH1394 is not set
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_IEEE1394_CMP=m
# CONFIG_IEEE1394_AMDTP is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Macintosh device drivers
#

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_IPV6 is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_NETFILTER is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# Bluetooth support
#
# CONFIG_BT is not set
# CONFIG_KGDBOE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NETPOLL_RX is not set
# CONFIG_NETPOLL_TRAP is not set
# CONFIG_NET_POLL_CONTROLLER is not set

#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_SERIAL=y
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
# CONFIG_INPUT_UINPUT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
# CONFIG_ROCKETPORT is not set
CONFIG_CYCLADES=y
# CONFIG_CYZ_INTR is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_DIGI is not set
# CONFIG_ESPSERIAL is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
# CONFIG_SYNCLINK is not set
# CONFIG_SYNCLINKMP is not set
# CONFIG_N_HDLC is not set
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
# CONFIG_STALDRV is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
CONFIG_SERIAL_8250_ACPI=y
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_PRINTER=y
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set

#
# Mice
#
CONFIG_BUSMOUSE=y
# CONFIG_QIC02_TAPE is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=y
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
# CONFIG_FB is not set
# CONFIG_VIDEO_SELECT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_VERBOSE_PRINTK=y
CONFIG_SND_DEBUG=y
CONFIG_SND_DEBUG_MEMORY=y
CONFIG_SND_DEBUG_DETECT=y

#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# ISA devices
#
# CONFIG_SND_AD1816A is not set
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_ES968 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_WAVEFRONT is not set
# CONFIG_SND_ALS100 is not set
# CONFIG_SND_AZT2320 is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_DT019X is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set

#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
CONFIG_SND_ENS1371=m
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set

#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_UHCI_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
# CONFIG_USB_STORAGE_HP8200e is not set
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y

#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_XPAD is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
CONFIG_USB_SCANNER=m
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set

#
# Video4Linux support is needed for USB Multimedia device support
#

#
# USB Network adaptors
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GADGET is not set

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
# CONFIG_EXT2_FS_POSIX_ACL is not set
# CONFIG_EXT2_FS_SECURITY is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
CONFIG_DEVPTS_FS=y
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V4 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_GSS is not set
CONFIG_SMB_FS=y
# CONFIG_SMB_NLS_DEFAULT is not set
CONFIG_CIFS=y
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_NEC98_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_EFI_PARTITION is not set

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_IOVIRT=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_PAGEALLOC=y
# CONFIG_SPINLINE is not set
CONFIG_DEBUG_INFO=y
# CONFIG_LOCKMETER is not set
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_KGDB is not set
CONFIG_FRAME_POINTER=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
CONFIG_CRC32=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_PC=y

^ permalink raw reply

* Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED
From: John Stoffel @ 2004-01-26 14:14 UTC (permalink / raw)
  To: Andi Kleen
  Cc: John Stoffel, Adrian Bunk, Valdis.Kletnieks, Fabio Coatti,
	Andrew Morton, Eric, linux-kernel
In-Reply-To: <20040126050431.GB6519@colin2.muc.de>


>> On node 0 totalpages: 196606
>> DMA zone: 4096 pages, LIFO batch:1
>> Normal zone: 192510 pages, LIFO batch:16
>> HighMem zone: 0 pages, LIFO batch:1

Andi> Ok, it didn't oops. Just hung early. Probably needs some printks
Andi> to track it down.

Andi> And the problem really goes away when you disable -funit-at-a-time ?

This was from both 2.6.2-rc1 and 2.6.2-rc2, and since the later
doesn't have the -funit-at-time declaration in the Makefile, I don't
think that's the problem.

My gcc version is:

    > gcc --version
    gcc.real (GCC) 3.3.3 20040110 (prerelease) (Debian)


John

^ permalink raw reply

* Re: [Linux-ATM-General] Announcement: MPHY now supported inmpc860sar
From: Alex Zeffertt @ 2004-01-26 14:17 UTC (permalink / raw)
  To: Gilad Rom
  Cc: linux-atm-general@lists.sourceforge.net,
	linuxppc-embedded@lists.linuxppc.org
In-Reply-To: <01a701c3e415$3a49ff40$026810ac@gilad>


All I know  is that it won't run on the 8260 "as-is".  Sorry, you'll
have to RTFM.  (The chapter on ATM is only ~180 pages :-).

Alex

On Mon, 2004-01-26 at 14:03, Gilad Rom wrote:
> Okay. Thanks.
>
> And now for my next question - Do you think the driver
> should run on the 82xx family of chips? (e.g. 8260 and the likes)
> these guys have 2 Utopia-II ports with support for up to 31 devices
> per port. Coupled with this software, it could make for a highly
> efficient DSLAM.
>
> Gilad.
>
> ----- Original Message -----
> From: "Alex Zeffertt" <ajz@cambridgebroadband.com>
> To: "Gilad Rom" <gilad@romat.com>
> Cc: <linux-atm-general@lists.sourceforge.net>;
> <linuxppc-embedded@lists.linuxppc.org>
> Sent: Monday, January 26, 2004 3:59 PM
> Subject: Re: [Linux-ATM-General] Announcement: MPHY now supported
> inmpc860sar
>
>
> > It is currently only supported in SAR mode, and in that mode there is an
> > upper limit of 4 UTOPIA phys.  However, there's no reason that support
> > can't be added for MPHY in ESAR mode - in which the limit is 31 phys.  I
> > suspect that adding such support would be easier now that Rodolfo has
> > done most of the work.
> >
> > Alex
> >
> > PS I'm not the expert on this.  Rodolfo's sourceforge username is
> > "zaigor".
> >
> > On Mon, 2004-01-26 at 13:51, Gilad Rom wrote:
> > > This is very exciting news! (well, for me it is)
> > >
> > > How many PHY's in parallel are we talking about here?
> > >
> > > Thanks,
> > > Gilad.
> > >
> > >
> > > ----- Original Message -----
> > > From: "Alex Zeffertt" <ajz@cambridgebroadband.com>
> > > To: <linux-atm-general@lists.sourceforge.net>;
> > > <linuxppc-embedded@lists.linuxppc.org>
> > > Sent: Monday, January 26, 2004 1:41 PM
> > > Subject: [Linux-ATM-General] Announcement: MPHY now supported in
> mpc860sar
> > >
> > >
> > > > Just a quick note to say that multi-phy is now supported by the
> > > > mpc860sar ATM driver, thanks to a patch by Rodolfo Giometti.
> > > >
> > > > Page: http://sourceforge.net/projects/mpc860sar/
> > > >
> > > > Alex
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > The SF.Net email is sponsored by EclipseCon 2004
> > > > Premiere Conference on Open Tools Development and Integration
> > > > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> > > > http://www.eclipsecon.org/osdn
> > > > _______________________________________________
> > > > Linux-atm-general mailing list
> > > > Linux-atm-general@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/linux-atm-general
> > > >
> >
> >
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply

* Is there a grand plan for FC failover?
From: Simon Kelley @ 2004-01-26 14:18 UTC (permalink / raw)
  To: linux-scsi

I see that 2.6.x kernels now have the qla2xxx driver in the mainline, 
but without the failover code.

What is the reason for that? Is there a plan provide failover facilities 
  at a higher level which will be usable with all suitable low-level 
drivers and hardware?

I'm very much in favour of using drivers which are developed in the 
kernel mainline but I have an application which needs failover so I 
might be forced back to the qlogic-distributed code.

Cheers,

Simon.


^ permalink raw reply

* Re: New linux box
From: Peter Garrett @ 2004-01-26 14:24 UTC (permalink / raw)
  To: linux-newbie list
In-Reply-To: <200401262213.43388.wheds8@ms66.hinet.net>

You might want to look at

http://www.tldp.org/HOWTO/Hardware-HOWTO/

seems a bit outdated (2002-11-12) but it looks informative.

For Mandrake try

http://www.linux-mandrake.com/en/fhard.php3

On Tue, 2004-01-27 at 01:13, S. Barret Dolph wrote:
> Well, my problems have much to do with hardware and it is time to get a new 
> box. My old box ran for 6 years with Mandrake and never crashed. (X-windows 
> crashed when setting up Matrox 450 though.) My question is what hardware is 
> good to avoid. I only use my computer for work, no games, but I am on it at 
> least 6 hours or more a day. I care mostly about stability and don't really 
> care too much about speed. So more to the point are any of you aware of 
> hardware that is a nightmare to install. Or a site which can help.
> 
> Cordially,
> S. Barret Dolph
> Taipei Taiwan
> -
> 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

-
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: REISER4 corruptions errors
From: Paolo Correnti @ 2004-01-26 14:25 UTC (permalink / raw)
  To: Nikita Danilov; +Cc: REISER LIST
In-Reply-To: <16405.7504.491020.659611@laputa.namesys.com>


--- Nikita Danilov <Nikita@Namesys.COM> wrote:

> Well, for all I know, this very well may be a bug in
> the fsck, rather than corruption of the on-disk data
> structures. Are
> you experiencing any
> problems when _using_ this partition (error messages
> in the kernel log,
> crashes, deadlocks, etc.)?
> 

I have problems using the "20040119-fixed" partition
with 2.6.1 (after writing many MB of data, almost
always I obtain a file corrupted so that Oracle
doesn't start). With 2.6.0 and 20031223 snapshot I
have no problems using the "20031223" partition.

But in both tests I saw that fsck.reiser4 gave me
from 5 to 35 and more corruptions errors, all of type

Error: Node (210326), item (7): StatData of the file
[10001:1616662635f5445:10002] has the wrong bytes
(3625472), Should be
(3629056). Plugin (stat40).

So I was thinking (perhaps strangely ...) that this
kind of corruption was more dangerous with 2.6.1 +
20040119-fixed (I'm speaking about Oracle logfile
corrupted after 5 million rows written) than with
2.6.0 + 20030123 (which never gave me an Oracle file
corrupted, also after 10 million rows written).

I made the same test on 2 different disks so I'm
almost sure this is not an hardware problem.

Best regards

Paolo


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/

^ permalink raw reply

* fix jffs2 data errors ?
From: Armin Schindler @ 2004-01-26 14:26 UTC (permalink / raw)
  To: linux-mtd

Hi,

together with latest CVS of jffs2 (one week old), I try to use
my rootfs on a jffs2 NAND-Flash partition.

It seems to work pretty good, but when I have e.g. reset/power-down,
on the next boot/rootfs-mount I get messages like:

 jffs2_scan_dirent_node(): Name CRC failed on node at 0x001b89dc: Read 0xffffffff,
 calculated 0xc04c39e5
 Empty flash at 0x001b8a10 ends at 0x001b8c00
 Empty flash at 0x001b93f8 ends at 0x001b9400

I thought, that such errors will be fixed, but every time I mount the partition,
these errors still exist.

Is the filesystem now unfixable or am I doing something wrong?

Thanks for any hint,
Armin

^ permalink raw reply

* Re: [PATCH] fix names for MPU-401 ports
From: Takashi Iwai @ 2004-01-26 14:28 UTC (permalink / raw)
  To: Clemens Ladisch; +Cc: alsa-devel
In-Reply-To: <Pine.HPX.4.33n.0401261004380.6589-100000@studcom.urz.uni-halle.de>

At Mon, 26 Jan 2004 10:07:03 +0100 (MET),
Clemens Ladisch wrote:
> 
> 
> This moves the initialization of card->shortname before the
> component creation so that the name for the rawmidi port is
> "<shortname> MPU-401" instead of "MPU-401 (UART) x-0".

nice work!
it's now on cvs.


thanks,

Takashi


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

^ permalink raw reply

* Re: pmdisk working on ppc (WAS: Help port swsusp to ppc)
From: Guido Guenther @ 2004-01-26 14:29 UTC (permalink / raw)
  To: Benjamin Herrenschmidt
  Cc: Hugang, Patrick Mochel, Nigel Cunningham, ncunningham,
	Linux Kernel Mailing List, linuxppc-dev list
In-Reply-To: <1074912854.834.61.camel@gaston>

On Sat, Jan 24, 2004 at 01:54:15PM +1100, Benjamin Herrenschmidt wrote:
> Ok, I hammered that for a day and got pmdisk (patrick's version) suspending
> and resuming on a pismo G3 (with XFree etc.. running). Lots of rough edges
> still (via-pmu sleep need to be improved, ADB need porting to the new driver
> model to be properly suspended/resumed, a sysdev for RTC is needed too for
> time, the asm code should be fixed for G5, etc...)
Works fine on a 

processor       : 0
cpu             : 7455, altivec supported
clock           : 867MHz
revision        : 3.3 (pvr 8001 0303)
bogomips        : 863.00
machine         : PowerBook6,1
motherboard     : PowerBook6,1 MacRISC3 Power Macintosh
board revision  : 00000001
detected as     : 287 (PowerBook G4 12")
pmac flags      : 0000000b
L2 cache        : 256K unified
memory          : 256MB
pmac-generation : NewWorld

Cheers,
 -- Guido

^ permalink raw reply


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.