martouf
-
Content count
335 -
Joined
-
Last visited
Never
Posts posted by martouf
-
-
thanks for hanging in there with this ... so, what's the situation now?
Working OK in Windows, or no?
-
the info from the board manufacturer is nice, but the info from a running Linux kernel
is more helpful than specs to figure out what's going on with your system.
How's SUSE 9.1 working out for you?
What's the output from /sbin/lsmod and /sbin/lspci ?
-
it's easy enough to have rpm tell you everything you need to have on hand to successfully
install a new package. Sometimes you have to collect all of the packages first and give
rpm a whole list of rpms (say, like, "*.rpm"\) and let rpm figure out which order to install
the packages.
When you say "bombed out," what exactly do you mean?
Error message(s), please.
-
-
tell me why I can't format the following using the "tt" code?
[tt] find / -type d -name \*wine\* 2> /dev/null [/tt]
why does it appear as I typed it but without formatting?
tell me why I can't nest two simple formatting tags?
[tt][size:4] want bigger than teeny-tiny 'tt' text here [/color][/tt]
why does the above only work with the tags in reverse order?
[size:4][tt] bigger than teeny-tiny 'tt' text here [/tt][/color]
better still, why don't the formatting tags have simple modifiers?
[tt size=3] want 'tt' text but a bit bigger [/tt]
most of all: Why isn't there a link on this site to the formatting tag syntax?
-
hmm.. I'll guess one of the important files is either missing or 0 bytes.
Could be a file permissions problem..
If "rpm --verify -p name-of-torcs-rpm-file" seems to be happy with the install, then
(if the listing isn't HUGE) would you provide the
"rpm --query --list --verbose -p name-of-torcs-rpm-file" output?
-
sometimes only a go with /usr/sbin/alsaconf will produce a working set up.
-
ok.. based on your responses, the card is OK and the system is OK and the way you're working
on the problem won't create new problems.
I was interested in you having the most recent Windows drivers in order to fully test
the card in Windows (aka 'a functioning lash-up') to establish both the system and the
card are working well together.
When trying to get Windows to untangle its own self-made driver mess (which can mimic dead hardware)
you may need to not only uninstall the driver but also shut down, remove the problem card,
reboot without the card, shut down again (stoopid Windows!), install the card once again,
and finally reboot.
Ugly, but Windows does not yet have good hardware configuration management built in.
As for OEM cards: they are sometimes custom jobs almost-but-not-quite the same
as the 'consumer' version and as a result need the custom driver only available from where you
got the card (not the card designers website).
-
the three tools I'm aware of are:
mencode, transcode, and dvd::rip
Linux Journal has had some very good articles on this topic.
Read these articles all the way through, and make special note of the "resources" links
at the end of the articles:
Making Digital Movies on Linux
and
DVD Transcoding with Linux Metacomputing
pay extra attention to the 'Background', 'DVD Partitioning', and 'Test Bed Layout' sections.
-
the orinoco chipset was one of the earliest full-support successes with open source drivers
and was included with the 2.4.0 kernel.
I'd be massively surprised if it's not included in FC2.
See for yourself if there's orinoco drivers in
/lib/modules/`uname --kernel-release`/kernel/drivers/net/wireless
-
Quote:Afterwards go to /lib/modules/fglrx and run './make_install.sh'
in order to install the module into your kernel's module repository.
(see readme.txt for more details.)
What's the file 'readme.txt' in /lib/modules/fglrx got to say?Quote:kernel includes at /usr/src/linux/include not found or incomplete
file: /usr/src/linux/include/linux/version.h
Can you find the file 'version.h' in /usr/src/linux/include/linux ?
I'll guess there isn't a /usr/src/linux directory, so the kernel include directory isn't
there either. You need to install and set up the kernel sources.
Is there an instruction specifically directing you to use the '--force' rpm parameter?
If there is, that's OK, I guess, but it's dangerous and should rarely be used, if ever.
Once you've got the kernel sources installed and set up,Quote:You must go to /lib/modules/fglrx/build_mod subdir
and execute './make.sh' to build a fully customed kernel module.
Afterwards go to /lib/modules/fglrx and run './make_install.sh'
... what it says.
-
umm .. windows doesn't stop "reading in its old slot" unless the hardware is farked.
BTW, "oem" means original equipment manufacturer. Plainly spoken, it means a card supplied
by a manufacturer but without brand markings so that it can be resold or "rebadged".
In some cases, it's a special version of a card made specifically for a system vendor.
Windows could possibly develop a driver problem which looks like farked hardware,
and in that case using Device Manager
( Start -> Run -> "devmgmt.msc" ) or (Control Panel -> System -> Hardware -> Device Manager)
and "uninstalling" the card and rebooting will effect a driver reinstallation.
Does the system run OK without the card?
Are you being very careful to take all static discharge control precautions
as you work on the system's guts?
Are you using the most recent Audigy drivers for windows?
-
I think fantom is being quite intrepid and has installed linux on the same system as
what was running winXP and the Sagem ADSL modem.
DDan what you're suggesting is what I'd recommend: use the winXP box for stable connectivity
and add linux to a 'lab rat' system connected over a network to the winXP box.
-
If you're adventurous enough to be building your own tools, then you need to be comfortable
with 'make'.
The whereabouts of X is easy enough to obtain: "whereis X"
Of course, /usr/X11R6/bin/X is probably linked to
/var/X11R6/bin/X which is linked to the actual X Windows appropriate for your hardware.
Hmm.. having a look at xstroke-0.6 ... you're going to need the 'autoconf' package
and be comfortable with it, too. There isn't a Makefile, per se, in the xstroke tarball.
You're given the pieces which specify for autoconf how to put a Makefile together.
If you need more help, say so. Someone will dig deeper.
In the meantime, rest up and work on this with fresh perspective later.
-
a little more information about the MB would help.
What's the output from /sbin/lspci ? (cut and paste into reply, please)
In the meantime, do a "linux p4p800-deluxe" google search, and also have a look
-
have a look at the rpmbuild manual page ("man rpmbuild"\),
or point your browser to
/usr/share/doc/packages/rpm/RPM-HOWTO/index.html
if you need further assistance... by all means, ask!
-
to be certain it's said here and not assumed: just installing the kernel sources isn't
usually enough by itself. You need to do a little prep after installing the sources
before you're ready to build your own drivers (kernel modules).
from the documentation:
[tt]2.1.1. Installation on Linux Mandrake 9.1
-----------------------------------------
Important : Mandrake 9.1 integrates a native driver for SAGEM USB ADSL modems.
This driver is compatible ONLY with F@st800 modems using an Eagle I chipset.
If - you're using a more recent modem (based on Eagle II or higher),
- you don't know the version of the chipset used,
- you're using an ADSL over ISDN modem (SAGEM F@st 840),
----> you absolutely need to install a newer driver (version v2.0.5 or higher)
and you cannot use Mandrake 9.1 wizards to setup the ADSL connection.
In release 2.0.5, the installation script of the SAGEM F@st800-840 modem automatically
deactivates the native ADSL module of Mandrake 9.1 by renaming the file "adiusbadsl.o.gz"
into "adiusbadsl.old.o.gz".
It is recommended, unless you use Mandrake 9.1's native driver, not to activate the
"automatic connection at start-up" feature proposed by Mandrake 9.1.
2.1.2. Installation on Linux SuSE 9.0
-------------------------------------
Important : with SuSE 9.0, please go to the kernel sources directory (cd /usr/src/linux)
and type "make cloneconfig && make dep" before compiling the driver.
[/tt]
In most cases you must locate the config file used to build your kernel and copy it to
/usr/src/linux/.config and then run "make oldconfig && make dep".
"make cloneconfig && make dep" is appropriate for distros which save a copy of your
kernel config in /boot .
-
'xmms' works too, but the bottom line is you'll need copies of the windows codecs.
There is a wincodecs archive file on the 'Net and it's legal for you to use as long as
you already have a legal copy of Windows. Alternatively, you can get the list of
codec files from the wincodecs archive and copy them from your own Windows installation.
The codecs need to be installed in /usr/lib/win32
or /usr/local/lib/win32
so that 'mplayer' or 'xmms' can find them.
-
danleff - a one point kupo said the downloaded file was a "rar" file. Sound like an archive
format file to me, not an ISO image file.
If so, then YES kupo, you need to extract the ISO image file from whatever archive it is in.
You must have the ISO image to burn your disc.
kupo - "burn the disc slowly" means use something less than the fastest write speed
your disc drive permits. Disc writing software will permit you to select the disc writing
speed. Don't use the "optimal" or "fastest" setting (whatever your software calls it).
Choose 4x or even 2x instead. Higher speed increases your chance of bit errors as you write
the disc and you need a byte-for-byte exact image copy.
-
blackpage - thanks for providing a link to 'sodipodi'. Forgot about that one.
MDK 10 advertises it ships with Gimp 1.2.5 but also includes Gimp 2.0.0 (for testing, I 'spose).
If Gimp 2 (one of the extras or contrib items) isn't where you can find it on your disc,
then go on over to rpms.mandrakeclub.com and get it there.
Full CMYK support is in development, and you can always leave the color sep for Photoshop.
-
"recognizes a single processor" -
if it's system with good multiprocessor (MP) hardware and one CPU installed, then yes,
all is well.
If it's a system with ++ungood MP hardware and two CPUs installed, then
all may be well.
If it's a system with one CPU and the kernel probes and finds no MP hardware, then
all is well.
If it's a 1-CPU system and the kernel thinks it's got MP hardware, then: who knows?
There are a few more possibilities, but I think you've got the idea by now.
The first step in troubleshooting an MP system is to boot a UP kernel.
-
for those who don't have 'locate' in their distro, try:
whereis wine
or the ultimate:
find / -type d -name wine\* 2> /dev/null
translated: find all directories whose name begins with "wine", list their names,
and send all error messages like "permission denied" to the bit-bucket.
-
"boot from the floopy" - means the kernel is loaded and needs to load the initial ram disk
(initrd) filesystem before it can actually do anything useful.
without a filesystem mounted (initrd at a minimum), all the kernel can do is notice, for instance,
you've typed a key on the keyboard and basically look at you and say "yeah? what am I supposed
to do with this?"
It's important you take your own good time to read all the DIY instructions and follow them
to the letter when making your own CDs or buy CDs which have already been mastered.
-
one word: "gimp"
If by 'illustration' you mean vector graphics, have a look at 'dia'.
For a place to start getting information about available graphics software, have look
at:
http://www.portalux.com/applications/graphics/bitmap/
and
http://www.portalux.com/applications/graphics/vector/
If nothing less than Photoshop will do, then have a look at CrossOver Office
http://www.codeweavers.com/products/crossover/
and with this you can install Photoshop on your MDK system.
dial-up ISP connection without static DNS IP addy (uses DHCP) kppp issues...
in Linux Networking
Posted
I think it's a bit rude to post here and refer to a thread on a completely different
board and not provide here:
the name of the ISP
and
the contents of the problem /etc/resolv.conf file
I looked at the thread on the other board and couldn't quite make heads or tails of the
situation. I was able to see the ISP name is eskimo.com but I'm not about to sign up on the
board just to see the resolv.conf contents.
The IP addresses of the eskimo.com DNS servers are provided for you in the KPPP instructions.
You may need to configure kppp to not update resolv.conf based on the ppp negotiation with
eskimo.com and edit your own resolv.conf to get DNS resolution working for your friend.