* Re: Gnomecard Program lost
From: Ray Olszewski @ 2003-12-05 16:11 UTC (permalink / raw)
To: linux-newbie
In-Reply-To: <200312050832.hB58Wq717871@skyinet.net>
At 04:32 PM 12/5/2003 +0800, Peter wrote:
>Hi,
>
>A weird thing happened. All of a sudden my / partition was 100% full when
>normally and as it is now again only 30 % is used. I could not find any files
>to delete so I had to reinstall RH73.
>
>In the process I lost the program gnomecard for my adresses. I can't find it
>on any of my old CDs, not in gnome.org and a google search put me back on
>gnome; tocosw was negative as well.
>
>Does anyone know where it is hidden and guide me in my apparent blindness.
In the Debian packaging system, this app is part of the package
"gnome-pim", along with gnomecal (the Calendar app). You might see if RH,
or gnome.org, packages it similarly.
-
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
* Gnomecard Program lost
From: Peter @ 2003-12-05 8:32 UTC (permalink / raw)
To: linux
Hi,
A weird thing happened. All of a sudden my / partition was 100% full when
normally and as it is now again only 30 % is used. I could not find any files
to delete so I had to reinstall RH73.
In the process I lost the program gnomecard for my adresses. I can't find it
on any of my old CDs, not in gnome.org and a google search put me back on
gnome; tocosw was negative as well.
Does anyone know where it is hidden and guide me in my apparent blindness.
Thanks & regards
--
Peter
-
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: ping messages
From: Shane Mitchell @ 2003-12-03 15:54 UTC (permalink / raw)
To: Petre Bandac; +Cc: linux-newbie
In-Reply-To: <200312030825.59905.g38@rdsbv.ro>
On Wed, 3 Dec 2003, Petre Bandac wrote:
> Date: Wed, 3 Dec 2003 08:25:59 +0200
> From: Petre Bandac <g38@rdsbv.ro>
> To: linux-newbie@vger.kernel.org
> Subject: ping messages
>
> hello
>
> I've googled around to find out EXACTLY what ping messages mean
>
> like
> icmp: time exceeded in-transit [tos 0xc0]
>
> or
>
> icmp: echo request [ttl 1]
>
> first I went to check out rfc's, but didn't find much there
>
> could you please give me any hints ?
>
> thanks,
>
> petre
>
>
This is a very good collection of links to documentation/RFC's etc..
http://www.ethereal.com/links.html
--
Shane Mitchell
so sing just like him, fuckers
it won't offend him
just me
because he's dead
-- Vedder '4/20/02'
-
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: ping messages
From: Ray Olszewski @ 2003-12-03 6:35 UTC (permalink / raw)
To: linux-newbie
In-Reply-To: <200312030825.59905.g38@rdsbv.ro>
At 08:25 AM 12/3/2003 +0200, Petre Bandac wrote:
>hello
>
>I've googled around to find out EXACTLY what ping messages mean
>
>like
>icmp: time exceeded in-transit [tos 0xc0]
>
>or
>
>icmp: echo request [ttl 1]
>
>first I went to check out rfc's, but didn't find much there
>
>could you please give me any hints ?
I've never found a decent online reference for this info. I usualy turn to
the book Internet Core Protocols (by Eric A. Hall; O'Reilly, 2000) when I
need to untangle ping responses (or most any packet internals).
Or you could try asking specific questions here ... I don't have the time
to answer a question as open-ended as "EXACTLY what ping messages mean" ...
but I can help with the occasional *specific* question.
-
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
* ping messages
From: Petre Bandac @ 2003-12-03 6:25 UTC (permalink / raw)
To: linux-newbie
hello
I've googled around to find out EXACTLY what ping messages mean
like
icmp: time exceeded in-transit [tos 0xc0]
or
icmp: echo request [ttl 1]
first I went to check out rfc's, but didn't find much there
could you please give me any hints ?
thanks,
petre
--
8:23AM up 23:18, 2 users, load averages: 0.61, 0.58, 0.47
-
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: How do I install my own service
From: Ray Olszewski @ 2003-12-03 6:07 UTC (permalink / raw)
To: linux-newbie
In-Reply-To: <1070306845.2760.4.camel@localhost.localdomain>
At 10:43 PM 12/2/2003 -0500, Ramzez wrote:
>HI friends...
>
> please, how can I install my own service (i'm using RH9.0).
>
> I make my script in /etc/rc.d/init.d ... something like this:
>-------------------------- killMyTemp -----------------------
> #!/bin/sh
> rm -rf /home/FamilyGroup/tmp/*
>--------------------------
> then I make a soft-link in /etc/rc.d/rc5.d ...
> again, something like: ln -s ../init.d/killMyTemp K99killMyTemp ...
>
> But when I turn-off my PC, this script didn't run; why?
Assuming that by "turn-off" you mean run the "shutdown" or "halt" command
... it does not run because shutdown is runlevel 6, not runlevel 5 (or at
least it is on every Linux system I've ever used ... I haven't used RH in a
very long time, though). If you look in (probably - I don't know RH's
organization) /etc/rc.d/rc6.d/, you will see the symlinks for the init
scripts that run as part of shutdown.
-
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
* How do I install my own service
From: Ramzez @ 2003-12-03 3:43 UTC (permalink / raw)
To: linux-newbie
HI friends...
please, how can I install my own service (i'm using RH9.0).
I make my script in /etc/rc.d/init.d ... something like this:
-------------------------- killMyTemp -----------------------
#!/bin/sh
rm -rf /home/FamilyGroup/tmp/*
--------------------------
then I make a soft-link in /etc/rc.d/rc5.d ...
again, something like: ln -s ../init.d/killMyTemp K99killMyTemp ...
But when I turn-off my PC, this script didn't run; why?
thanks
--
Linux User Registered #232544
ICQ : 337889406
GnuPG-key : www.keyserver.net
-------------------------------
"Software is like sex,
it's better when it's free."
[Linus Torvalds]
-
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
* irqmask doesn't work
From: Jing Xu @ 2003-11-26 21:50 UTC (permalink / raw)
To: linux-newbie
Hello,
I'm having some trouble with PCI IRQ's and I was
hoping someone here could help.
I'm running linux 2.4.20 and rtai 24.1.11. My linux
kernel module needs to use IRQ 9 10 11 for AGP graphic
card, sound card and PCI-Dio24 IO card. These irqs are
also shared by USB controllers. My module hangs when
it tries to request the above irqs used by USB
devices. I figured it would be a good idea to remove
this apparent conflict. I have scoured the web and
found that I can reserve these IRQs by specifying
pci=irqmask=0xxxxx on the kernel boot line.
I have tried to set "pci=irqmask=0xf1e8" to reserve
Irq 9 10 11 4 from my driver, and it hasn't had any
effect - those irqs are still used by usb controllers
on initialization.
How do I change these IRQ's? Is there some other
configuration file I haven't found? If anyone can
provide any insight into this, I would appreciate it
greatly. Let me know what/if any details you need - I
am by no means an expert in this area and didn't want
to post reams of irrelevant information, but if there
is something I'm missing let me know and I'll get
it...
Thanks in advance,
jing
__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
-
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
* Netlink Info required
From: Pankaj Garg @ 2003-11-24 22:57 UTC (permalink / raw)
To: linux-kernel, linux-newbie
I am writing a kernel module. The module will need to send asynchronous
messages (generated by the module) to a User Application.
I am trying to use Netlink socket for it, but can't figure out how to
use it in kernel space. Can somebody provide me with some help.
Thanks,
Pankaj
^ permalink raw reply
* Re: Printing Garbage
From: Hal MacArgle @ 2003-11-22 13:25 UTC (permalink / raw)
To: linux-newbie
In-Reply-To: <200311210238.hAL2cY201990@skyinet.net>
Greetings: Not following the thread; if the parallel port was on the
MB there could have been a simple work around. (Too late now though,
eh?)
Parallel port expansion cards are available for $10upUS.. I've had to
do that several times to "rescue" a MB.. Of course, some times it
didn't work. <grin>
Glad to see you've rediscovered the very fine Slackware 9X, IMHO.
Hal - in Terra Alta, WV - Slackware GNU/Linux 9.0 (2.4.20)
Proprietary Formats Unacceptable
On 11-21, Peter wrote:
> Hi, my own worst suspicion turned out to be true. The motherboard had failed
> which
> was a little less then 2 years old, yet old enough that this type can not be
> found any longer and therefore all the sockets of the new boards are different
> forcing me to buy as well a new processor and memories. Guess that keeps the
> industry running.
>
> The new board is P4VMM2 by ECS Elitegroup and I was unable to configure X in
> RH7.3. The first time this happened since RH5.2. I then went over to Slackware
> 9.1, got X surprisingly working there, copied XF86config over to RH and all is
> fine
> except I am $200 poorer.
>
> Thanks and regards
>
> Peter
>
> At 04:28 PM 11/17/2003 +0800, Peter wrote:
>
> >Hi,
> >
> >suddenly my printer Epson LQ 300 is only printing garbage characters. What
> >could be the reason.
> >
> >I am in RH 7.3. I went to DOS the same, only garbage printing.
> >
> >There are no error messages. Starting LPD says OK. Lprm, lpq etc function
> >normally.
> >
> >Running the printer self test performs flawlessly, meaning the printer does
> >work. I checked all the cables, can't find anything wrong.
> >
> >Any ideas, help?
-
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: Printing Garbage
From: Peter @ 2003-11-21 2:38 UTC (permalink / raw)
To: linux-newbie
In-Reply-To: <5.1.0.14.1.20031117101709.01f7afb8@celine>
Hi, my own worst suspicion turned out to be true. The motherboard had failed
which
was a little less then 2 years old, yet old enough that this type can not be
found any longer and therefore all the sockets of the new boards are different
forcing me to buy as well a new processor and memories. Guess that keeps the
industry running.
The new board is P4VMM2 by ECS Elitegroup and I was unable to configure X in
RH7.3. The first time this happened since RH5.2. I then went over to Slackware
9.1, got X surprisingly working there, copied XF86config over to RH and all is
fine
except I am $200 poorer.
Thanks and regards
Peter
At 04:28 PM 11/17/2003 +0800, Peter wrote:
>Hi,
>
>suddenly my printer Epson LQ 300 is only printing garbage characters. What
>could be the reason.
>
>I am in RH 7.3. I went to DOS the same, only garbage printing.
>
>There are no error messages. Starting LPD says OK. Lprm, lpq etc function
>normally.
>
>Running the printer self test performs flawlessly, meaning the printer does
>work. I checked all the cables, can't find anything wrong.
>
>Any ideas, help?
ray@comarre.com said:
> Were I to **guess**, it would be that you missed a bad cable. Only a
> guess, though.
-
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: problem using keyboard and mouse
From: Ray Olszewski @ 2003-11-20 18:40 UTC (permalink / raw)
To: linux-newbie
In-Reply-To: <20031120133458.67144.qmail@web60601.mail.yahoo.com>
At 05:34 AM 11/20/2003 -0800, Ravi Kumar Munnangi wrote:
> Hi,
>
> When Iam working on my computer, suddenly I face
> problems using mouse and keyboard.
> Iam not able to do scrolling using the mouse.
> Though I keep hold a key down, the character is not
> displayed repeatedly.
> I don't why this is happening suddenly.
It could be happening for any number of reasons, ranging from physical
failure of the keyboard/mouse or motherboard, through BIOS problems, or X
problems (assuming this is happening in X), or problems specific to the
application where this happens, or even user error (for example, a focus
problem).
To get help, you will have to tell us more. For example:
What version of Linux (what distro, what kernel)?
Are the keyboard and mouse PS/2 devices, or USB? (Or AT and serial, if this
is an old system?)
What version of X and what X driver (or if this is not an X problem, what
display setting it occurs in)?
What application are you running when you see the problem? Has this
SPECIFIC application worked properly with the keyboard and the mouse
before? Is "suddenly" completely out of the blue, or did you just do a
system update that may have loaded a new version of the app or apps in
question?
How are you "scrolling using the mouse"? Are you referring to a scrool
wheel or the use of scrollbars provided by the app?
Is the keypress problem happening with all (or a lot of) keys, or did you
just encounter it with 1 or 2 keys (which ones)? Do single keypresses still
work?
Is the system simply busy, so responding v-e-r-y s-l-o-w-l-y? Even though
it usually has high priority, the UI is still a process (actually, a whole
set of processes), and if the CPU is heavily loaded, it can bog down. You
might try running "top" in an xterm or over an ssh connection while this
problem is showing up, just to check for this (admittedly, long shot)
possibility.
There are so many other possibilities that I can't really frame good
questions, so I'll end with a general one: Can you think of anything
different between the situations where keyboard and mouse work the way you
expect them to and situations where they do not? For *example*, are
different uid's involved?
-
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
* problem using keyboard and mouse
From: Ravi Kumar Munnangi @ 2003-11-20 13:34 UTC (permalink / raw)
To: linux-newbie
Hi,
When Iam working on my computer, suddenly I face
problems using mouse and keyboard.
Iam not able to do scrolling using the mouse.
Though I keep hold a key down, the character is not
displayed repeatedly.
I don't why this is happening suddenly.
Kindly help me!
Thanx in advance.
RaviKumar
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
-
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: activating eth0
From: Anna G. Zapata @ 2003-11-19 21:14 UTC (permalink / raw)
To: Ray Olszewski, linux-newbie
In-Reply-To: <5.1.0.14.1.20031119121638.01f72bb0@celine>
Nevermind, it is now working again. I didn't do anything, but it seems fine now. One minute it was working, the next
it wasn't working, and now it's back up again. Sorry for the bother.
-----Original Message-----
From: linux-newbie-owner@vger.kernel.org
[mailto:linux-newbie-owner@vger.kernel.org]On Behalf Of Ray Olszewski
Sent: Wednesday, November 19, 2003 1:32 PM
To: linux-newbie@vger.kernel.org
Subject: Re: activating eth0
At 12:16 PM 11/19/2003 -0700, Anna G. Zapata wrote:
>Hello everyone,
>
>I am running RH 8.0. My network card was working just fine and then one
>day just flopped over. I have tried
>reactivating it using the GUI and using the command ifup eth0, but nothing
>seems to work. Any thoughts?
First, provide technical descriptions of the failures, not metaphorical
ones (e.g., "just flopped over" is colorful but not very informative).
Beyond that ...
What were the symptoms of the initial failure? Did it occur out of the
blue, or after a reboot, or what?
What does happen when you try to reactivate the interface? That is, what
happens when you enter (as root) the command "ifup eth0"?
What is the complete, unedited output of "ifconfig -a"? (After you do the
above attempt to reactivate, or right after a fresh boot/init, but tell us
which you are reporting.)
What kernel are you running ("uname -a")? Is it stock or one you compiled
locally?
What sort of NIC is it? What kernel module(s) does it use (or is the driver
compiled into the kernel)?
Is there any possibility of either a physical failure of the NIC or a BIOS
problem?
During the boot/init sequence, does the kernel (or the loading of the
relevant module) detect the NIC? (This info will show up in the dmesg
buffer, which RH *may* write out someplace like /var/log/dmesg .)
You may have checked some of this already, but I don't know what actual
efforts are covered by your statement that "nothing seems to work", so I
decided to be inclusive rather than risk skipping something useful because
it was too "obvious" to ask about.
-
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: activating eth0
From: Ray Olszewski @ 2003-11-19 20:31 UTC (permalink / raw)
To: linux-newbie
In-Reply-To: <HBEJLOFMLEPBMAAEFNFDGEBPCDAA.azapata@du.edu>
At 12:16 PM 11/19/2003 -0700, Anna G. Zapata wrote:
>Hello everyone,
>
>I am running RH 8.0. My network card was working just fine and then one
>day just flopped over. I have tried
>reactivating it using the GUI and using the command ifup eth0, but nothing
>seems to work. Any thoughts?
First, provide technical descriptions of the failures, not metaphorical
ones (e.g., "just flopped over" is colorful but not very informative).
Beyond that ...
What were the symptoms of the initial failure? Did it occur out of the
blue, or after a reboot, or what?
What does happen when you try to reactivate the interface? That is, what
happens when you enter (as root) the command "ifup eth0"?
What is the complete, unedited output of "ifconfig -a"? (After you do the
above attempt to reactivate, or right after a fresh boot/init, but tell us
which you are reporting.)
What kernel are you running ("uname -a")? Is it stock or one you compiled
locally?
What sort of NIC is it? What kernel module(s) does it use (or is the driver
compiled into the kernel)?
Is there any possibility of either a physical failure of the NIC or a BIOS
problem?
During the boot/init sequence, does the kernel (or the loading of the
relevant module) detect the NIC? (This info will show up in the dmesg
buffer, which RH *may* write out someplace like /var/log/dmesg .)
You may have checked some of this already, but I don't know what actual
efforts are covered by your statement that "nothing seems to work", so I
decided to be inclusive rather than risk skipping something useful because
it was too "obvious" to ask about.
-
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
* activating eth0
From: Anna G. Zapata @ 2003-11-19 19:16 UTC (permalink / raw)
To: Linux-Newbie
Hello everyone,
I am running RH 8.0. My network card was working just fine and then one day just flopped over. I have tried
reactivating it using the GUI and using the command ifup eth0, but nothing seems to work. Any thoughts?
Thank you.
Anna Zapata
UTS - Network Security
303.871.2009
-
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: Printing Garbage
From: Frank Roberts - SOTL @ 2003-11-17 21:10 UTC (permalink / raw)
To: Ray Olszewski, linux
In-Reply-To: <5.1.0.14.1.20031117101709.01f7afb8@celine>
On Monday 17 November 2003 13:27, Ray Olszewski wrote:
> At 04:28 PM 11/17/2003 +0800, Peter wrote:
> >Hi,
> >
> >suddenly my printer Epson LQ 300 is only printing garbage characters. What
> >could be the reason.
> >
> >I am in RH 7.3. I went to DOS the same, only garbage printing.
> >
> >There are no error messages. Starting LPD says OK. Lprm, lpq etc function
> >normally.
> >
> >Running the printer self test performs flawlessly, meaning the printer
> > does work. I checked all the cables, can't find anything wrong.
> >
> >Any ideas, help?
>
> Well, if the problem occurs with DOS as well as Linux, that certainly
> suggests it is not a Linux problem. There are a couple of things to do
> before you buy a new printer, though.
>
> 1. Have you power-cycled the printer? If not, do so, just in case something
> caused a transient change in the settings. Leave it off for a minute or so.
>
> 2. You say "I checked all the cables, can't find anything wrong". Checked
> *how*? Visually? That wouldn't catch a single broken wire, which would be
> enough to turn good signals into jabberwocky ... and could easily happen if
> the cable is bent sharply at either end (I've never actually seen this with
> a parallel or serial cable, but I have seen it happen to VGA cables). The
> only real way to test for a cable problem, unless you are better with a VOM
> than I am, is to substitute another cable and still see the problem (or to
> use the cable in a different setup and see no problem there ... even that
> is not a *completely* certain test, though).
>
> 3. You probably want to ask for help on a support list for the printer, not
> a Linux list. There, the question to ask is if there is some persistent
> change to the configuration that can occur accidentally ... stay in NV RAM
> or whatever.
>
> 4. Any chance that you made a BIOS change to the port (you don't way if
> this is a parallel, serial, USB, or LAN/Ethernet setup, so I can't be more
> specific than that ... though I suppose you use of DOS implies either
> parallel or serial)?
>
> Were I to **guess**, it would be that you missed a bad cable. Only a guess,
> though.
>
Hi All
First I assume competence with my response.
By that I mean that the person knows to do all the normal clean up things like
check printer cable, check plugged in, turn off printer to clear buffer,
clear files from cash et before a question like that is ask.
For mysself I have a printer HO 890 C connected to a dual boot Win XP / Md 9.1
box that at times refuses to print correct.
I have seen the same file printed under the same program in the same operating
system print and not print.
This printer may and often is connected to another dual boot Win 98 / RH 6.3
box where it always works.
There is a third box RH 7.3 form which it also always works.
At the last SLUG meeting here in Tampa I mentioned the problem because I
thought it has something to do with the fact that I had split the HD of the
offending computer into 3 sectors. The Win XP can see two: WIN XP and Common;
the Md 9.1 can see two: Common and Md 9.1. I was concerned with the partition
format being used for Common.
Oh I for got to mention the problem is independent of file format except for
plain text which always works. All other formats work and/or fail seeming at
random.
Turns out that regardless of the file format used any files brought up in Win
XP Office become corrupt. If Win XP Office is not used then there is no
problem.
I found the problem by the simple means of using a second Canon portable
printer I have.
Regards
Frank
-
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: ISDN
From: Ray Olszewski @ 2003-11-17 20:37 UTC (permalink / raw)
To: linux-newbie
In-Reply-To: <MSGID_110=3a100=2f1_3fb92872@fidonet.org>
At 07:57 PM 11/17/2003 +0000, Sean Rima wrote:
>Originally to: All
>
>Hello everybody.
>
>I asked in the Linux-ISDN list but I am a newbie to isn and I canot get
>SuSE 9.0 to see my DrayTek minivigor TA
I can't help you directly, Sean, since I use neitner ISDN nor this product.
I did look around a bit, though, and found a thread on the suse-isdn list.
Unfortunately, it is in German, so (unless you speak German) you'll need
help from someone other than me to interpret it. Good luck.
One entry point into it is ...
http://www.geocrawler.com/archives/3/289/2002/3/0/8251597/
... but you are probably better off Google'ing the topic ("DrayTek
minivigor TA linux") yourself for leads.
-
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
* ISDN
From: Sean Rima @ 2003-11-17 19:57 UTC (permalink / raw)
To: linux-newbie
Originally to: All
Hello everybody.
I asked in the Linux-ISDN list but I am a newbie to isn and I canot get SuSE 9.0 to see my DrayTek minivigor TA
Sean
-
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: Printing Garbage
From: Ray Olszewski @ 2003-11-17 18:27 UTC (permalink / raw)
To: linux
In-Reply-To: <200311170828.hAH8SP201505@skyinet.net>
At 04:28 PM 11/17/2003 +0800, Peter wrote:
>Hi,
>
>suddenly my printer Epson LQ 300 is only printing garbage characters. What
>could be the reason.
>
>I am in RH 7.3. I went to DOS the same, only garbage printing.
>
>There are no error messages. Starting LPD says OK. Lprm, lpq etc function
>normally.
>
>Running the printer self test performs flawlessly, meaning the printer does
>work. I checked all the cables, can't find anything wrong.
>
>Any ideas, help?
Well, if the problem occurs with DOS as well as Linux, that certainly
suggests it is not a Linux problem. There are a couple of things to do
before you buy a new printer, though.
1. Have you power-cycled the printer? If not, do so, just in case something
caused a transient change in the settings. Leave it off for a minute or so.
2. You say "I checked all the cables, can't find anything wrong". Checked
*how*? Visually? That wouldn't catch a single broken wire, which would be
enough to turn good signals into jabberwocky ... and could easily happen if
the cable is bent sharply at either end (I've never actually seen this with
a parallel or serial cable, but I have seen it happen to VGA cables). The
only real way to test for a cable problem, unless you are better with a VOM
than I am, is to substitute another cable and still see the problem (or to
use the cable in a different setup and see no problem there ... even that
is not a *completely* certain test, though).
3. You probably want to ask for help on a support list for the printer, not
a Linux list. There, the question to ask is if there is some persistent
change to the configuration that can occur accidentally ... stay in NV RAM
or whatever.
4. Any chance that you made a BIOS change to the port (you don't way if
this is a parallel, serial, USB, or LAN/Ethernet setup, so I can't be more
specific than that ... though I suppose you use of DOS implies either
parallel or serial)?
Were I to **guess**, it would be that you missed a bad cable. Only a guess,
though.
-
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: Printing Garbage
From: Frank Roberts - SOTL @ 2003-11-17 12:23 UTC (permalink / raw)
To: Peter, linux
In-Reply-To: <200311170828.hAH8SP201505@skyinet.net>
Try a different printer if it works correctly then buy a new printer.
Frank
On Monday 17 November 2003 03:28, Peter wrote:
> Hi,
>
> suddenly my printer Epson LQ 300 is only printing garbage characters. What
> could be the reason.
>
> I am in RH 7.3. I went to DOS the same, only garbage printing.
>
> There are no error messages. Starting LPD says OK. Lprm, lpq etc function
> normally.
>
> Running the printer self test performs flawlessly, meaning the printer does
> work. I checked all the cables, can't find anything wrong.
>
> Any ideas, help?
>
> Regards
-
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
* Printing Garbage
From: Peter @ 2003-11-17 8:28 UTC (permalink / raw)
To: linux
Hi,
suddenly my printer Epson LQ 300 is only printing garbage characters. What
could be the reason.
I am in RH 7.3. I went to DOS the same, only garbage printing.
There are no error messages. Starting LPD says OK. Lprm, lpq etc function
normally.
Running the printer self test performs flawlessly, meaning the printer does
work. I checked all the cables, can't find anything wrong.
Any ideas, help?
Regards
--
Peter
-
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: Kernel 2.6.0-test9 installation
From: Theo. Sean Schulze @ 2003-11-12 17:12 UTC (permalink / raw)
To: linux-newbie
In-Reply-To: <200311112217.32576.lindevel@gmx.net>
Dennis,
I recently had this problem come up also. The 2.6 kernel supports partitions made with other operating systems now. The way I fixed this was by going into the Partitions section of the kernel config and enabling all the different partition types. I imagine that deselecting the partition support option would also work, and then it would just go with a default for partitions built using linux. But, since I didn't try that option, and since I am now longer using the 2.6test kernels (for other reasons), I don't know for sure that this second method will work.
Try either of these courses of action and see if it does it for you. YMMV.
Cheers,
Sean
On Tue, Nov 11, 2003 at 10:17:32PM +0100, Dennis Schridde hunted and pecked out:
> Hi list.
> When I boot with Kernel 2.6.0-test9 I get the following message:
> RAMDISK: Compressed image found at block 0
> Kernel panic: VFS: Unable to mount root fs on hda2
>
> I configured, compiled (gcc 3.3.1) and installed the Kernel with modules:
> make xconfig
> make bzImage modules modules_install install
>
> It's output is:
> if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.6.0-test9; fi
> Kernel: arch/i386/boot/bzImage is ready
> sh /usr/src/linux-2.6.0-test9/arch/i386/boot/install.sh 2.6.0-test9 arch/
> i386/boot/bzImage System.map ""
> Root device: /dev/hda2 (mounted on / as reiserfs)
> Module list: reiserfs
> Kernel version: 2.6.0-test9 (i386)
> Kernel image: /boot/vmlinuz-2.6.0-test9
> Initrd image: /boot/initrd-2.6.0-test9
> Shared libs: lib/i686/libc.so.6 lib/ld-2.3.2.so
> Modules: kernel/fs/reiserfs/reiserfs.ko
> Bootsplash: SuSE (1280x1024)
> Using grub, re-install of bootloader not required.
>
> This creates following in my /boot dir:
> /boot/initrd
> /boot/initrd-2.6.0-test9
> /boot/System.map-2.6.0-test9
> /boot/vmlinuz
> /boot/vmlinuz-2.6.0-test9
>
> In my /boot/grub/menu.lst is the entry:
> title Linux-testing
> kernel (hd0,1)/boot/vmlinuz-2.6.0-test9 root=/dev/hda2 showopts
> initrd (hd0,1)/boot/initrd-2.6.0-test9
>
> My .config file is in the attachment.
>
> I'm running SuSE 9.0
>
> What is the problem?
> How can I fix it?
>
> Thanks,
> Dennis Schridde
>
>
> #
> # 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=y
> CONFIG_STANDALONE=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=y
> CONFIG_IKCONFIG_PROC=y
> # 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
>
> #
> # Loadable module support
> #
> CONFIG_MODULES=y
> # CONFIG_MODULE_UNLOAD is not set
> CONFIG_OBSOLETE_MODPARM=y
> CONFIG_MODVERSIONS=y
> CONFIG_KMOD=y
>
> #
> # Processor type and features
> #
> CONFIG_X86_PC=y
> # 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
> # CONFIG_M386 is not set
> # CONFIG_M486 is not set
> # CONFIG_M586 is not set
> # CONFIG_M586TSC is not set
> # CONFIG_M586MMX is not set
> # CONFIG_M686 is not set
> # CONFIG_MPENTIUMII is not set
> # CONFIG_MPENTIUMIII is not set
> # CONFIG_MPENTIUM4 is not set
> # CONFIG_MK6 is not set
> CONFIG_MK7=y
> # CONFIG_MK8 is not set
> # CONFIG_MELAN is not set
> # CONFIG_MCRUSOE is not set
> # CONFIG_MWINCHIPC6 is not set
> # CONFIG_MWINCHIP2 is not set
> # CONFIG_MWINCHIP3D is not set
> # CONFIG_MCYRIXIII is not set
> # CONFIG_MVIAC3_2 is not set
> # CONFIG_X86_GENERIC is not set
> CONFIG_X86_CMPXCHG=y
> CONFIG_X86_XADD=y
> CONFIG_X86_L1_CACHE_SHIFT=6
> CONFIG_RWSEM_XCHGADD_ALGORITHM=y
> CONFIG_X86_WP_WORKS_OK=y
> CONFIG_X86_INVLPG=y
> CONFIG_X86_BSWAP=y
> CONFIG_X86_POPAD_OK=y
> CONFIG_X86_GOOD_APIC=y
> CONFIG_X86_INTEL_USERCOPY=y
> CONFIG_X86_USE_PPRO_CHECKSUM=y
> CONFIG_X86_USE_3DNOW=y
> CONFIG_HPET_TIMER=y
> # CONFIG_HPET_EMULATE_RTC is not set
> # CONFIG_SMP is not set
> CONFIG_PREEMPT=y
> CONFIG_X86_UP_APIC=y
> CONFIG_X86_UP_IOAPIC=y
> CONFIG_X86_LOCAL_APIC=y
> CONFIG_X86_IO_APIC=y
> CONFIG_X86_TSC=y
> CONFIG_X86_MCE=y
> CONFIG_X86_MCE_NONFATAL=y
> # CONFIG_X86_MCE_P4THERMAL is not set
> # CONFIG_TOSHIBA is not set
> # CONFIG_I8K is not set
> CONFIG_MICROCODE=m
> CONFIG_X86_MSR=m
> CONFIG_X86_CPUID=m
> CONFIG_EDD=m
> # CONFIG_NOHIGHMEM is not set
> CONFIG_HIGHMEM4G=y
> # CONFIG_HIGHMEM64G is not set
> CONFIG_HIGHMEM=y
> # CONFIG_HIGHPTE is not set
> # CONFIG_MATH_EMULATION is not set
> CONFIG_MTRR=y
> CONFIG_HAVE_DEC_LOCK=y
>
> #
> # Power management options (ACPI, APM)
> #
> CONFIG_PM=y
> # CONFIG_SOFTWARE_SUSPEND is not set
> CONFIG_PM_DISK=y
> CONFIG_PM_DISK_PARTITION="/dev/hda3"
>
> #
> # ACPI (Advanced Configuration and Power Interface) Support
> #
> CONFIG_ACPI=y
> CONFIG_ACPI_BOOT=y
> CONFIG_ACPI_INTERPRETER=y
> CONFIG_ACPI_SLEEP=y
> CONFIG_ACPI_SLEEP_PROC_FS=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 is not set
> # CONFIG_ACPI_TOSHIBA is not set
> # CONFIG_ACPI_DEBUG is not set
> 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
>
> #
> # APM (Advanced Power Management) BIOS Support
> #
> CONFIG_APM=y
> # CONFIG_APM_IGNORE_USER_SUSPEND is not set
> CONFIG_APM_DO_ENABLE=y
> # CONFIG_APM_CPU_IDLE is not set
> CONFIG_APM_DISPLAY_BLANK=y
> # CONFIG_APM_RTC_IS_GMT is not set
> CONFIG_APM_ALLOW_INTS=y
> # CONFIG_APM_REAL_MODE_POWER_OFF is not set
>
> #
> # CPU Frequency scaling
> #
> CONFIG_CPU_FREQ=y
> CONFIG_CPU_FREQ_PROC_INTF=y
> CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
> # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
> CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
> CONFIG_CPU_FREQ_GOV_POWERSAVE=y
> CONFIG_CPU_FREQ_GOV_USERSPACE=y
> CONFIG_CPU_FREQ_24_API=y
> CONFIG_CPU_FREQ_TABLE=y
>
> #
> # CPUFreq processor drivers
> #
> # CONFIG_X86_ACPI_CPUFREQ is not set
> # CONFIG_X86_POWERNOW_K6 is not set
> # CONFIG_X86_POWERNOW_K7 is not set
> # CONFIG_X86_POWERNOW_K8 is not set
> # CONFIG_X86_GX_SUSPMOD is not set
> # CONFIG_X86_SPEEDSTEP_CENTRINO is not set
> # CONFIG_X86_SPEEDSTEP_ICH is not set
> # CONFIG_X86_SPEEDSTEP_SMI is not set
> # CONFIG_X86_P4_CLOCKMOD is not set
> # CONFIG_X86_LONGRUN is not set
> # CONFIG_X86_LONGHAUL 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_LEGACY_PROC=y
> CONFIG_PCI_NAMES=y
> # CONFIG_ISA is not set
> # CONFIG_MCA is not set
> # CONFIG_SCx200 is not set
> # CONFIG_HOTPLUG is not set
>
> #
> # Executable file formats
> #
> CONFIG_BINFMT_ELF=y
> CONFIG_BINFMT_AOUT=m
> CONFIG_BINFMT_MISC=m
>
> #
> # Device Drivers
> #
>
> #
> # Generic Driver Options
> #
>
> #
> # Memory Technology Devices (MTD)
> #
> # CONFIG_MTD is not set
>
> #
> # Parallel port support
> #
> CONFIG_PARPORT=m
> CONFIG_PARPORT_PC=m
> CONFIG_PARPORT_PC_CML1=m
> CONFIG_PARPORT_SERIAL=m
> CONFIG_PARPORT_PC_FIFO=y
> CONFIG_PARPORT_PC_SUPERIO=y
> CONFIG_PARPORT_OTHER=y
> CONFIG_PARPORT_1284=y
>
> #
> # Plug and Play support
> #
> CONFIG_PNP=y
> # CONFIG_PNP_DEBUG is not set
>
> #
> # Protocols
> #
> # CONFIG_ISAPNP is not set
> CONFIG_PNPBIOS=y
>
> #
> # Block devices
> #
> # CONFIG_BLK_DEV_FD 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=m
> CONFIG_BLK_DEV_CRYPTOLOOP=m
> CONFIG_BLK_DEV_NBD=m
> CONFIG_BLK_DEV_RAM=y
> CONFIG_BLK_DEV_RAM_SIZE=64000
> CONFIG_BLK_DEV_INITRD=y
> # CONFIG_LBD is not set
>
> #
> # 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=y
> CONFIG_BLK_DEV_IDECD=m
> # CONFIG_BLK_DEV_IDETAPE is not set
> # CONFIG_BLK_DEV_IDEFLOPPY is not set
> CONFIG_BLK_DEV_IDESCSI=m
> # CONFIG_IDE_TASK_IOCTL is not set
> # CONFIG_IDE_TASKFILE_IO is not set
>
> #
> # IDE chipset support/bugfixes
> #
> # CONFIG_BLK_DEV_CMD640 is not set
> CONFIG_BLK_DEV_IDEPNP=y
> 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_IDE_TCQ=y
> CONFIG_BLK_DEV_IDE_TCQ_DEFAULT=y
> CONFIG_BLK_DEV_IDE_TCQ_DEPTH=8
> # CONFIG_BLK_DEV_IDEDMA_FORCED is not set
> CONFIG_IDEDMA_PCI_AUTO=y
> CONFIG_IDEDMA_ONLYDISK=y
> # 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=y
> # 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 is not set
> # 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_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=m
> CONFIG_SCSI_PROC_FS=y
>
> #
> # SCSI support type (disk, tape, CD-ROM)
> #
> CONFIG_BLK_DEV_SD=m
> # CONFIG_CHR_DEV_ST is not set
> # CONFIG_CHR_DEV_OSST is not set
> # CONFIG_BLK_DEV_SR is not set
> # CONFIG_CHR_DEV_SG is not set
>
> #
> # Some SCSI devices (e.g. CD jukebox) support multiple LUNs
> #
> CONFIG_SCSI_MULTI_LUN=y
> CONFIG_SCSI_REPORT_LUNS=y
> # CONFIG_SCSI_CONSTANTS is not set
> # CONFIG_SCSI_LOGGING is not set
>
> #
> # SCSI low-level drivers
> #
> # CONFIG_BLK_DEV_3W_XXXX_RAID is not set
> # CONFIG_SCSI_ACARD is not set
> # CONFIG_SCSI_AACRAID is not set
> # CONFIG_SCSI_AIC7XXX is not set
> # CONFIG_SCSI_AIC7XXX_OLD is not set
> # CONFIG_SCSI_AIC79XX is not set
> # CONFIG_SCSI_ADVANSYS 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_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_IPS is not set
> # CONFIG_SCSI_INIA100 is not set
> CONFIG_SCSI_PPA=m
> CONFIG_SCSI_IMM=m
> # CONFIG_SCSI_IZIP_EPP16 is not set
> # CONFIG_SCSI_IZIP_SLOW_CTR is not set
> # CONFIG_SCSI_SYM53C8XX_2 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_DC395x is not set
> # CONFIG_SCSI_NSP32 is not set
> # CONFIG_SCSI_DEBUG is not set
>
> #
> # Multi-device support (RAID and LVM)
> #
> # CONFIG_MD is not set
>
> #
> # Fusion MPT device support
> #
> # CONFIG_FUSION is not set
>
> #
> # IEEE 1394 (FireWire) support (EXPERIMENTAL)
> #
> # CONFIG_IEEE1394 is not set
>
> #
> # I2O device support
> #
> CONFIG_I2O=m
> CONFIG_I2O_PCI=m
> CONFIG_I2O_BLOCK=m
> CONFIG_I2O_SCSI=m
> CONFIG_I2O_PROC=m
>
> #
> # Networking support
> #
> CONFIG_NET=y
>
> #
> # Networking options
> #
> CONFIG_PACKET=m
> CONFIG_PACKET_MMAP=y
> CONFIG_NETLINK_DEV=m
> CONFIG_UNIX=m
> CONFIG_NET_KEY=m
> CONFIG_INET=y
> CONFIG_IP_MULTICAST=y
> CONFIG_IP_ADVANCED_ROUTER=y
> CONFIG_IP_MULTIPLE_TABLES=y
> CONFIG_IP_ROUTE_FWMARK=y
> CONFIG_IP_ROUTE_NAT=y
> CONFIG_IP_ROUTE_MULTIPATH=y
> CONFIG_IP_ROUTE_TOS=y
> CONFIG_IP_ROUTE_VERBOSE=y
> CONFIG_IP_PNP=y
> CONFIG_IP_PNP_DHCP=y
> CONFIG_IP_PNP_BOOTP=y
> CONFIG_IP_PNP_RARP=y
> CONFIG_NET_IPIP=m
> CONFIG_NET_IPGRE=m
> CONFIG_NET_IPGRE_BROADCAST=y
> CONFIG_IP_MROUTE=y
> CONFIG_IP_PIMSM_V1=y
> CONFIG_IP_PIMSM_V2=y
> CONFIG_ARPD=y
> CONFIG_INET_ECN=y
> CONFIG_SYN_COOKIES=y
> CONFIG_INET_AH=m
> CONFIG_INET_ESP=m
> CONFIG_INET_IPCOMP=m
>
> #
> # IP: Virtual Server Configuration
> #
> CONFIG_IP_VS=m
> # CONFIG_IP_VS_DEBUG is not set
> CONFIG_IP_VS_TAB_BITS=12
>
> #
> # IPVS transport protocol load balancing support
> #
> CONFIG_IP_VS_PROTO_TCP=y
> CONFIG_IP_VS_PROTO_UDP=y
> CONFIG_IP_VS_PROTO_ESP=y
> CONFIG_IP_VS_PROTO_AH=y
>
> #
> # IPVS scheduler
> #
> CONFIG_IP_VS_RR=m
> CONFIG_IP_VS_WRR=m
> CONFIG_IP_VS_LC=m
> CONFIG_IP_VS_WLC=m
> CONFIG_IP_VS_LBLC=m
> CONFIG_IP_VS_LBLCR=m
> CONFIG_IP_VS_DH=m
> CONFIG_IP_VS_SH=m
> CONFIG_IP_VS_SED=m
> CONFIG_IP_VS_NQ=m
>
> #
> # IPVS application helper
> #
> CONFIG_IP_VS_FTP=m
> CONFIG_IPV6=m
> CONFIG_IPV6_PRIVACY=y
> CONFIG_INET6_AH=m
> CONFIG_INET6_ESP=m
> CONFIG_INET6_IPCOMP=m
> CONFIG_IPV6_TUNNEL=m
> # CONFIG_DECNET is not set
> # CONFIG_BRIDGE is not set
> CONFIG_NETFILTER=y
> # CONFIG_NETFILTER_DEBUG is not set
>
> #
> # IP: Netfilter Configuration
> #
> CONFIG_IP_NF_CONNTRACK=m
> CONFIG_IP_NF_FTP=m
> CONFIG_IP_NF_IRC=m
> CONFIG_IP_NF_TFTP=m
> CONFIG_IP_NF_AMANDA=m
> CONFIG_IP_NF_QUEUE=m
> CONFIG_IP_NF_IPTABLES=m
> CONFIG_IP_NF_MATCH_LIMIT=m
> CONFIG_IP_NF_MATCH_IPRANGE=m
> CONFIG_IP_NF_MATCH_MAC=m
> CONFIG_IP_NF_MATCH_PKTTYPE=m
> CONFIG_IP_NF_MATCH_MARK=m
> CONFIG_IP_NF_MATCH_MULTIPORT=m
> CONFIG_IP_NF_MATCH_TOS=m
> CONFIG_IP_NF_MATCH_RECENT=m
> CONFIG_IP_NF_MATCH_ECN=m
> CONFIG_IP_NF_MATCH_DSCP=m
> CONFIG_IP_NF_MATCH_AH_ESP=m
> CONFIG_IP_NF_MATCH_LENGTH=m
> CONFIG_IP_NF_MATCH_TTL=m
> CONFIG_IP_NF_MATCH_TCPMSS=m
> CONFIG_IP_NF_MATCH_HELPER=m
> CONFIG_IP_NF_MATCH_STATE=m
> CONFIG_IP_NF_MATCH_CONNTRACK=m
> CONFIG_IP_NF_MATCH_OWNER=m
> CONFIG_IP_NF_FILTER=m
> CONFIG_IP_NF_TARGET_REJECT=m
> CONFIG_IP_NF_NAT=m
> CONFIG_IP_NF_NAT_NEEDED=y
> CONFIG_IP_NF_TARGET_MASQUERADE=m
> CONFIG_IP_NF_TARGET_REDIRECT=m
> CONFIG_IP_NF_TARGET_NETMAP=m
> CONFIG_IP_NF_TARGET_SAME=m
> CONFIG_IP_NF_NAT_LOCAL=y
> CONFIG_IP_NF_NAT_SNMP_BASIC=m
> CONFIG_IP_NF_NAT_IRC=m
> CONFIG_IP_NF_NAT_FTP=m
> CONFIG_IP_NF_NAT_TFTP=m
> CONFIG_IP_NF_NAT_AMANDA=m
> CONFIG_IP_NF_MANGLE=m
> CONFIG_IP_NF_TARGET_TOS=m
> CONFIG_IP_NF_TARGET_ECN=m
> CONFIG_IP_NF_TARGET_DSCP=m
> CONFIG_IP_NF_TARGET_MARK=m
> CONFIG_IP_NF_TARGET_CLASSIFY=m
> CONFIG_IP_NF_TARGET_LOG=m
> CONFIG_IP_NF_TARGET_ULOG=m
> CONFIG_IP_NF_TARGET_TCPMSS=m
> CONFIG_IP_NF_ARPTABLES=m
> CONFIG_IP_NF_ARPFILTER=m
> CONFIG_IP_NF_ARP_MANGLE=m
> CONFIG_IP_NF_COMPAT_IPCHAINS=m
> CONFIG_IP_NF_COMPAT_IPFWADM=m
>
> #
> # IPv6: Netfilter Configuration
> #
> CONFIG_IP6_NF_QUEUE=m
> CONFIG_IP6_NF_IPTABLES=m
> CONFIG_IP6_NF_MATCH_LIMIT=m
> CONFIG_IP6_NF_MATCH_MAC=m
> CONFIG_IP6_NF_MATCH_RT=m
> CONFIG_IP6_NF_MATCH_OPTS=m
> CONFIG_IP6_NF_MATCH_FRAG=m
> CONFIG_IP6_NF_MATCH_HL=m
> CONFIG_IP6_NF_MATCH_MULTIPORT=m
> CONFIG_IP6_NF_MATCH_OWNER=m
> CONFIG_IP6_NF_MATCH_MARK=m
> CONFIG_IP6_NF_MATCH_IPV6HEADER=m
> CONFIG_IP6_NF_MATCH_AHESP=m
> CONFIG_IP6_NF_MATCH_LENGTH=m
> CONFIG_IP6_NF_MATCH_EUI64=m
> CONFIG_IP6_NF_FILTER=m
> CONFIG_IP6_NF_TARGET_LOG=m
> CONFIG_IP6_NF_MANGLE=m
> CONFIG_IP6_NF_TARGET_MARK=m
> CONFIG_XFRM=y
> CONFIG_XFRM_USER=m
>
> #
> # SCTP Configuration (EXPERIMENTAL)
> #
> CONFIG_IPV6_SCTP__=m
> # CONFIG_IP_SCTP is not set
> CONFIG_ATM=y
> CONFIG_ATM_CLIP=y
> CONFIG_ATM_CLIP_NO_ICMP=y
> CONFIG_ATM_LANE=m
> CONFIG_ATM_MPOA=m
> CONFIG_ATM_BR2684=m
> # CONFIG_ATM_BR2684_IPFILTER 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=y
> CONFIG_NET_SCH_CBQ=m
> CONFIG_NET_SCH_HTB=m
> CONFIG_NET_SCH_CSZ=m
> CONFIG_NET_SCH_ATM=y
> CONFIG_NET_SCH_PRIO=m
> CONFIG_NET_SCH_RED=m
> CONFIG_NET_SCH_SFQ=m
> CONFIG_NET_SCH_TEQL=m
> CONFIG_NET_SCH_TBF=m
> CONFIG_NET_SCH_GRED=m
> CONFIG_NET_SCH_DSMARK=m
> CONFIG_NET_SCH_INGRESS=m
> CONFIG_NET_QOS=y
> CONFIG_NET_ESTIMATOR=y
> CONFIG_NET_CLS=y
> CONFIG_NET_CLS_TCINDEX=m
> CONFIG_NET_CLS_ROUTE4=m
> CONFIG_NET_CLS_ROUTE=y
> CONFIG_NET_CLS_FW=m
> CONFIG_NET_CLS_U32=m
> CONFIG_NET_CLS_RSVP=m
> CONFIG_NET_CLS_RSVP6=m
> CONFIG_NET_CLS_POLICE=y
>
> #
> # Network testing
> #
> # CONFIG_NET_PKTGEN is not set
> CONFIG_NETDEVICES=y
>
> #
> # ARCnet devices
> #
> # CONFIG_ARCNET is not set
> CONFIG_DUMMY=m
> CONFIG_BONDING=m
> CONFIG_EQUALIZER=m
> CONFIG_TUN=m
> CONFIG_ETHERTAP=m
> # CONFIG_NET_SB1000 is not set
>
> #
> # Ethernet (10 or 100Mbit)
> #
> CONFIG_NET_ETHERNET=y
> CONFIG_MII=m
> # CONFIG_HAPPYMEAL is not set
> # CONFIG_SUNGEM is not set
> # CONFIG_NET_VENDOR_3COM is not set
>
> #
> # Tulip family network device support
> #
> # CONFIG_NET_TULIP is not set
> # CONFIG_HP100 is not set
> # CONFIG_NET_PCI 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=m
> CONFIG_PPP_MULTILINK=y
> CONFIG_PPP_FILTER=y
> CONFIG_PPP_ASYNC=m
> CONFIG_PPP_SYNC_TTY=m
> CONFIG_PPP_DEFLATE=m
> CONFIG_PPP_BSDCOMP=m
> CONFIG_PPPOE=m
> CONFIG_PPPOATM=m
> CONFIG_SLIP=m
> CONFIG_SLIP_COMPRESSED=y
> CONFIG_SLIP_SMART=y
> CONFIG_SLIP_MODE_SLIP6=y
>
> #
> # 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=m
>
> #
> # Wan interfaces
> #
> # CONFIG_WAN is not set
>
> #
> # ATM drivers
> #
> CONFIG_ATM_TCP=m
> # CONFIG_ATM_LANAI is not set
> # CONFIG_ATM_ENI is not set
> # CONFIG_ATM_FIRESTREAM is not set
> # CONFIG_ATM_ZATM is not set
> # CONFIG_ATM_NICSTAR is not set
> # CONFIG_ATM_IDT77252 is not set
> # CONFIG_ATM_AMBASSADOR is not set
> # CONFIG_ATM_HORIZON is not set
> # CONFIG_ATM_IA is not set
> # CONFIG_ATM_FORE200E_MAYBE is not set
> # CONFIG_ATM_HE 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
>
> #
> # 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=m
> # CONFIG_INPUT_TSDEV is not set
> CONFIG_INPUT_EVDEV=m
> # CONFIG_INPUT_EVBUG is not set
>
> #
> # Input I/O drivers
> #
> CONFIG_GAMEPORT=m
> CONFIG_SOUND_GAMEPORT=m
> # CONFIG_GAMEPORT_NS558 is not set
> # CONFIG_GAMEPORT_L4 is not set
> # CONFIG_GAMEPORT_EMU10K1 is not set
> # CONFIG_GAMEPORT_VORTEX is not set
> # CONFIG_GAMEPORT_FM801 is not set
> # CONFIG_GAMEPORT_CS461x is not set
> 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_PS2_SYNAPTICS is not set
> # CONFIG_MOUSE_SERIAL is not set
> # CONFIG_INPUT_JOYSTICK is not set
> # CONFIG_INPUT_TOUCHSCREEN is not set
> # CONFIG_INPUT_MISC is not set
>
> #
> # Character devices
> #
> CONFIG_VT=y
> CONFIG_VT_CONSOLE=y
> CONFIG_HW_CONSOLE=y
> # CONFIG_SERIAL_NONSTANDARD is not set
>
> #
> # Serial drivers
> #
> CONFIG_SERIAL_8250=m
> 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=m
> CONFIG_UNIX98_PTYS=y
> CONFIG_UNIX98_PTY_COUNT=256
> CONFIG_PRINTER=m
> CONFIG_LP_CONSOLE=y
> CONFIG_PPDEV=m
> # CONFIG_TIPAR is not set
>
> #
> # I2C support
> #
> CONFIG_I2C=m
> CONFIG_I2C_CHARDEV=m
>
> #
> # I2C Algorithms
> #
> CONFIG_I2C_ALGOBIT=m
> CONFIG_I2C_ALGOPCF=m
>
> #
> # I2C Hardware Bus support
> #
> # CONFIG_I2C_ALI1535 is not set
> # CONFIG_I2C_ALI15X3 is not set
> # CONFIG_I2C_AMD756 is not set
> # CONFIG_I2C_AMD8111 is not set
> # CONFIG_I2C_ELEKTOR is not set
> # CONFIG_I2C_I801 is not set
> # CONFIG_I2C_I810 is not set
> CONFIG_I2C_NFORCE2=m
> # CONFIG_I2C_PHILIPSPAR is not set
> # CONFIG_I2C_PIIX4 is not set
> # CONFIG_I2C_PROSAVAGE is not set
> # CONFIG_I2C_SAVAGE4 is not set
> # CONFIG_SCx200_ACB is not set
> # CONFIG_I2C_SIS5595 is not set
> # CONFIG_I2C_SIS630 is not set
> # CONFIG_I2C_SIS96X is not set
> # CONFIG_I2C_VIA is not set
> # CONFIG_I2C_VIAPRO is not set
> # CONFIG_I2C_VOODOO3 is not set
>
> #
> # I2C Hardware Sensors Chip support
> #
> CONFIG_I2C_SENSOR=m
> CONFIG_SENSORS_ADM1021=m
> CONFIG_SENSORS_EEPROM=m
> CONFIG_SENSORS_IT87=m
> CONFIG_SENSORS_LM75=m
> CONFIG_SENSORS_LM78=m
> CONFIG_SENSORS_LM85=m
> CONFIG_SENSORS_VIA686A=m
> CONFIG_SENSORS_W83781D=m
>
> #
> # Mice
> #
> # CONFIG_BUSMOUSE is not set
> # CONFIG_QIC02_TAPE is not set
>
> #
> # IPMI
> #
> CONFIG_IPMI_HANDLER=m
> CONFIG_IPMI_PANIC_EVENT=y
> CONFIG_IPMI_PANIC_STRING=y
> CONFIG_IPMI_DEVICE_INTERFACE=m
> CONFIG_IPMI_KCS=m
> CONFIG_IPMI_WATCHDOG=m
>
> #
> # Watchdog Cards
> #
> # CONFIG_WATCHDOG is not set
> # CONFIG_HW_RANDOM is not set
> CONFIG_NVRAM=m
> CONFIG_RTC=m
> # CONFIG_GEN_RTC is not set
> # 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=m
> # 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 is not set
> CONFIG_AGP_NVIDIA=m
> # CONFIG_AGP_SIS is not set
> # CONFIG_AGP_SWORKS is not set
> # CONFIG_AGP_VIA is not set
> CONFIG_DRM=y
> # CONFIG_DRM_TDFX is not set
> # CONFIG_DRM_GAMMA is not set
> # CONFIG_DRM_R128 is not set
> CONFIG_DRM_RADEON=m
> # CONFIG_DRM_MGA is not set
> # CONFIG_DRM_SIS is not set
> # CONFIG_MWAVE is not set
> # CONFIG_RAW_DRIVER is not set
> CONFIG_HANGCHECK_TIMER=m
>
> #
> # Multimedia devices
> #
> # CONFIG_VIDEO_DEV is not set
>
> #
> # Digital Video Broadcasting Devices
> #
> # CONFIG_DVB is not set
>
> #
> # Graphics support
> #
> CONFIG_FB=y
> # CONFIG_FB_CYBER2000 is not set
> # CONFIG_FB_IMSTT is not set
> # CONFIG_FB_VGA16 is not set
> CONFIG_FB_VESA=y
> CONFIG_VIDEO_SELECT=y
> # CONFIG_FB_HGA is not set
> # CONFIG_FB_RIVA is not set
> # CONFIG_FB_MATROX is not set
> CONFIG_FB_RADEON=m
> # CONFIG_FB_ATY128 is not set
> # CONFIG_FB_ATY is not set
> # CONFIG_FB_SIS is not set
> # CONFIG_FB_NEOMAGIC is not set
> # CONFIG_FB_3DFX is not set
> # CONFIG_FB_VOODOO1 is not set
> # CONFIG_FB_TRIDENT is not set
> # CONFIG_FB_VIRTUAL is not set
>
> #
> # Console display driver support
> #
> CONFIG_VGA_CONSOLE=y
> # CONFIG_MDA_CONSOLE is not set
> CONFIG_DUMMY_CONSOLE=y
> CONFIG_FRAMEBUFFER_CONSOLE=m
> CONFIG_PCI_CONSOLE=y
> # CONFIG_FONTS is not set
> CONFIG_FONT_8x8=y
> CONFIG_FONT_8x16=y
>
> #
> # Logo configuration
> #
> CONFIG_LOGO=y
> CONFIG_LOGO_LINUX_MONO=y
> CONFIG_LOGO_LINUX_VGA16=y
> CONFIG_LOGO_LINUX_CLUT224=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 is not set
> # CONFIG_SND_DEBUG is not set
>
> #
> # Generic devices
> #
> CONFIG_SND_DUMMY=m
> CONFIG_SND_VIRMIDI=m
> # CONFIG_SND_MTPAV is not set
> CONFIG_SND_SERIAL_U16550=m
> # CONFIG_SND_MPU401 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 is not set
> # 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=m
> # 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=m
> # CONFIG_USB_DEBUG is not set
>
> #
> # Miscellaneous USB options
> #
> CONFIG_USB_DEVICEFS=y
> CONFIG_USB_BANDWIDTH=y
> CONFIG_USB_DYNAMIC_MINORS=y
>
> #
> # USB Host Controller Drivers
> #
> CONFIG_USB_EHCI_HCD=m
> CONFIG_USB_OHCI_HCD=m
> CONFIG_USB_UHCI_HCD=m
>
> #
> # 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 is not set
> # CONFIG_USB_STORAGE is not set
>
> #
> # USB Human Interface Devices (HID)
> #
> # CONFIG_USB_HID is not set
>
> #
> # USB HID Boot Protocol drivers
> #
> # CONFIG_USB_KBD is not set
> # CONFIG_USB_MOUSE is not set
> # 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_TIGL is not set
> # CONFIG_USB_AUERSWALD is not set
> # CONFIG_USB_RIO500 is not set
> # CONFIG_USB_BRLVGER is not set
> # CONFIG_USB_LCD is not set
> # CONFIG_USB_SPEEDTOUCH is not set
> # CONFIG_USB_TEST is not set
> # CONFIG_USB_GADGET is not set
>
> #
> # File systems
> #
> CONFIG_EXT2_FS=m
> CONFIG_EXT2_FS_XATTR=y
> CONFIG_EXT2_FS_POSIX_ACL=y
> CONFIG_EXT2_FS_SECURITY=y
> CONFIG_EXT3_FS=m
> CONFIG_EXT3_FS_XATTR=y
> CONFIG_EXT3_FS_POSIX_ACL=y
> CONFIG_EXT3_FS_SECURITY=y
> CONFIG_JBD=m
> # CONFIG_JBD_DEBUG is not set
> CONFIG_FS_MBCACHE=m
> CONFIG_REISERFS_FS=m
> # CONFIG_REISERFS_CHECK is not set
> CONFIG_REISERFS_PROC_INFO=y
> # CONFIG_JFS_FS is not set
> CONFIG_FS_POSIX_ACL=y
> # CONFIG_XFS_FS is not set
> # CONFIG_MINIX_FS is not set
> CONFIG_ROMFS_FS=y
> # CONFIG_QUOTA is not set
> CONFIG_AUTOFS_FS=m
> CONFIG_AUTOFS4_FS=m
>
> #
> # CD-ROM/DVD Filesystems
> #
> CONFIG_ISO9660_FS=m
> CONFIG_JOLIET=y
> CONFIG_ZISOFS=y
> CONFIG_ZISOFS_FS=m
> CONFIG_UDF_FS=m
>
> #
> # DOS/FAT/NT Filesystems
> #
> CONFIG_FAT_FS=m
> CONFIG_MSDOS_FS=m
> CONFIG_VFAT_FS=m
> CONFIG_NTFS_FS=m
> CONFIG_NTFS_DEBUG=y
> CONFIG_NTFS_RW=y
>
> #
> # Pseudo filesystems
> #
> CONFIG_PROC_FS=y
> CONFIG_PROC_KCORE=y
> # CONFIG_DEVFS_FS is not set
> CONFIG_DEVPTS_FS=y
> CONFIG_DEVPTS_FS_XATTR=y
> CONFIG_DEVPTS_FS_SECURITY=y
> 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=m
> CONFIG_NFS_V3=y
> CONFIG_NFS_V4=y
> CONFIG_NFS_DIRECTIO=y
> CONFIG_NFSD=m
> CONFIG_NFSD_V3=y
> CONFIG_NFSD_V4=y
> CONFIG_NFSD_TCP=y
> CONFIG_LOCKD=m
> CONFIG_LOCKD_V4=y
> CONFIG_EXPORTFS=m
> CONFIG_SUNRPC=m
> CONFIG_SUNRPC_GSS=m
> CONFIG_RPCSEC_GSS_KRB5=m
> CONFIG_SMB_FS=m
> CONFIG_SMB_NLS_DEFAULT=y
> CONFIG_SMB_NLS_REMOTE="cp437"
> CONFIG_CIFS=m
> # 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=y
> # CONFIG_LDM_DEBUG 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
> CONFIG_SMB_NLS=y
> CONFIG_NLS=y
>
> #
> # Native Language Support
> #
> CONFIG_NLS_DEFAULT="iso8859-1"
> CONFIG_NLS_CODEPAGE_437=m
> # CONFIG_NLS_CODEPAGE_737 is not set
> # CONFIG_NLS_CODEPAGE_775 is not set
> CONFIG_NLS_CODEPAGE_850=m
> # 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=m
> # 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=m
> # CONFIG_NLS_KOI8_R is not set
> # CONFIG_NLS_KOI8_U is not set
> CONFIG_NLS_UTF8=m
>
> #
> # Profiling support
> #
> # CONFIG_PROFILING is not set
>
> #
> # Kernel hacking
> #
> # CONFIG_DEBUG_KERNEL is not set
> # CONFIG_DEBUG_SPINLOCK_SLEEP is not set
> # CONFIG_FRAME_POINTER is not set
> CONFIG_X86_EXTRA_IRQS=y
> CONFIG_X86_FIND_SMP_CONFIG=y
> CONFIG_X86_MPPARSE=y
>
> #
> # Security options
> #
> CONFIG_SECURITY=y
> CONFIG_SECURITY_NETWORK=y
> CONFIG_SECURITY_CAPABILITIES=m
> # CONFIG_SECURITY_ROOTPLUG is not set
> # CONFIG_SECURITY_SELINUX is not set
>
> #
> # Cryptographic options
> #
> CONFIG_CRYPTO=y
> CONFIG_CRYPTO_HMAC=y
> CONFIG_CRYPTO_NULL=m
> CONFIG_CRYPTO_MD4=m
> CONFIG_CRYPTO_MD5=m
> CONFIG_CRYPTO_SHA1=m
> CONFIG_CRYPTO_SHA256=m
> CONFIG_CRYPTO_SHA512=m
> CONFIG_CRYPTO_DES=m
> CONFIG_CRYPTO_BLOWFISH=m
> CONFIG_CRYPTO_TWOFISH=m
> CONFIG_CRYPTO_SERPENT=m
> CONFIG_CRYPTO_AES=m
> CONFIG_CRYPTO_CAST5=m
> CONFIG_CRYPTO_CAST6=m
> CONFIG_CRYPTO_DEFLATE=m
> # CONFIG_CRYPTO_TEST is not set
>
> #
> # Library routines
> #
> CONFIG_CRC32=m
> CONFIG_ZLIB_INFLATE=m
> CONFIG_ZLIB_DEFLATE=m
> CONFIG_X86_BIOS_REBOOT=y
> CONFIG_PC=y
--
Theo. Sean Schulze
tschulze@teamfinders.org
-
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: getting a valid display under Debian
From: James Miller @ 2003-11-12 12:54 UTC (permalink / raw)
Cc: Linux-Newbie list
In-Reply-To: <Pine.LNX.4.58.0311111846120.3176@homenet>
I found something on the web concerning directing STDERR to a file at
http://www.tldp.org/HOWTO/Bash-Prog-Intro-HOWTO-3.html . I'll post the
relevant segment here for the benefit of other newbies who may not know
what it means or how to do it, and also in hopes that it may help me
remember how. Excerpt follows:
------------------------------------------------------------
3.3 Sample: stderr 2 file
This will cause the stderr ouput of a program to be written to a file.
grep da * 2> grep-errors.txt
Here, a file called 'grep-errors.txt' will be created and it will contain
what you would see the stderr portion of the output of the 'grep da *'
command.
---------------------------------------------------------
Issuing "startx 2> xerrs.txt" at the command line seems to have worked for
me - i.e., it generated a file with some content (other things I tried,
guessing at the right text to type, generated files, but the files had no
content).
In any case, here is the content of the xerrs.txt file that resulted:
-------------------------------------------------------------------
X: warning; process set to priority -11 instead of requested priority -10
This is a pre-release version of XFree86, and is not supported in any
way. Bugs may be reported to XFree86@XFree86.Org and patches submitted
to fixes@XFree86.Org. Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs)
XFree86 Version 4.2.1.1 (Debian 4.2.1-13 20031030071229
root@newraff.debian.org) / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 18 October 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems. (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.22-rc2 i686 [ELF]
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Fri Jun 20 01:41:55 2003
(==) Using config file: "/etc/X11/XF86Config-4"
----------------------------------------------------------------
That doesn't seem particularly helpful to me, but it may hold some hidden
meaning for Ray and others trying to help out with this problem.
I also note the XFree86.0.log file in /var/log. Could that also contain
something relevant to diagnosing the problem?
Thanks, James
-
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: getting a valid display under Debian
From: James Miller @ 2003-11-12 0:50 UTC (permalink / raw)
Cc: Linux-Newbie list
In-Reply-To: <5.1.0.14.1.20031111121913.01fa3d58@celine>
On Tue, 11 Nov 2003, Ray Olszewski wrote:
> Last thought ... the X 4.x.x did, I believe, drop support for some older
> hardware. You might be getting snagged by that (with respect to the video
> card). I don't *think* this applies to S3Virge, but I'd have to check at
> xfree86.org to be certain, and you can check there as easily as I can.
>
From www.xfree86.org:
------------------------------------------------------------------
3.3.6:
Support (accelerated) for the S3 911, 924, 801, 805, 928, 864, 868, 964,
968, Trio32, Trio64, Trio64V+, Trio64UV+, Aurora64V+, Trio64V2, and
PLATO/PX is provided by the XF86_S3 server and the XF86_SVGA server with
the s3_svga driver. Support (accelerated) for the ViRGE, ViRGE/VX,
ViRGE/DX, ViRGE/GX, ViRGE/GX2, ViRGE/MX, ViRGE/MX+ is provided by the
XF86_S3V server. Support (accelerated) for the ViRGE chipsets, as well as
the Trio3D and Trio3D/2X, is provided by the XF86_SVGA server with the s3v
driver. Support (accelerated) for the Savage3D, Savage3D/MV, Savage4, and
Savage2000, is provided by the XF86_SVGA server with the s3_savage driver
on some OSes (Linux, *BSD).
4.3.0:
Support (accelerated) for the 964 (revisions 0 and 1), 968, Trio32,
Trio64, Trio64, Trio64V+, Trio64UV+, Aurora64V+, Trio64V2, and PLATO/PX is
provided by the "s3" driver (however, only models using the IBM RGB 524,
Texas Instruments 3025, or an internal TrioDAC RAMDAC chip are supported).
Support (accelerated) for the ViRGE, ViRGE/VX, ViRGE/DX, ViRGE/GX,
ViRGE/GX2, ViRGE/MX, ViRGE/MX+, Trio3D and Trio3D/2X is provided by the
"s3virge" driver. Support (accelerated) for the Savage3D, Savage3D/MV,
Savage4, Savage2000, and SuperSavage, is provided by the "savage" driver.
Support for the other S3 chipsets has not yet been ported.
Summary:
All hardware supported in 3.3.6 is also supported in 4.3.0 except for the
911, 924, 801, 805, 928, 864, and 868, and versions of the 964 and 968
that do not use the RAMDAC chips listed above. The SuperSavage chipset is
supported only in 4.3.0.
---------------------------------------------------------------------
My card is the S3 ViRGE/VX 86C988. I interpret the above to mean that my
card should be supported under the version of xfree86 that's on my system,
don't you?
Thanks, James
-
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
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox