building a driver in /lib/modules/2.6.9-1.667/build/ - how? need src.rpm?
by Carlos Puchol
hi, i have a driver, called my-driver.c here, that builds cleanly
on a clean, official 2.6.9 tree:
...
MODPOST
CC drivers/char/my-driver.mod.o
LD [M] drivers/char/my-driver.ko
..
i made modifications to the Kconfig and Makefile, .config, etc. so that it
all goes well.
however, i would like to compile and run it in the stock kernel
that a given fc3 machine is running.
i gather that i have to build it in /lib/modules/2.6.9-1.667/build/
however, i am not sure _exactly_ how.
first, do i need the kernel sources in /usr/src/linux-2.6.9-1.667?
i would hope not, since i see a build/include directory, etc.
(also, i guess not, since the nvidia driver seems to have been partially
compiled dynamically).
currently i don't have the sources in the official place,
but i think i know that i can build them and make them available [*].
however, still what do i do then?
i edited Kconfig, .config and the Makefile just like i did in the official
tree, did make oldconfig, and then ... make or make modules barfs ...
[17:45:55](2)machina:build# pwd
/lib/modules/2.6.9-1.667/build
[17:47:10](2)machina:build# make modules
CHK include/linux/version.h
CHK include/asm-x86_64/offset.h
/bin/sh: arch/x86_64/kernel/asm-offsets.s: No such file or directory
UPD include/asm-x86_64/offset.h
mv: cannot stat `include/asm-x86_64/offset.h.tmp': No such file or directory
make: *** [include/asm-x86_64/offset.h] Error 1
[17:47:11](2)machina:build#
however, interestingly, i seem to compile the module just fine
like this:
[17:47:11](2)machina:build# make drivers/char/my-driver.o
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/split-include
HOSTCC scripts/basic/docproc
HOSTCC scripts/genksyms/genksyms.o
HOSTCC scripts/genksyms/lex.o
HOSTCC scripts/genksyms/parse.o
HOSTLD scripts/genksyms/genksyms
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
HOSTCC scripts/mod/file2alias.o
HOSTCC scripts/mod/modpost.o
HOSTCC scripts/mod/sumversion.o
HOSTLD scripts/mod/modpost
HOSTCC scripts/kallsyms
HOSTCC scripts/pnmtologo
HOSTCC scripts/conmakehash
CC [M] drivers/char/my-driver.o
[17:47:29](2)machina:build#
however .. i can't seem to be able to load it:
[17:49:34](2)machina:build# insmod drivers/char/my-driver.o
my-driver: error inserting 'drivers/char/my-driver.o': -1 Invalid module format
[17:50:00](2)machina:build#
[17:50:14](2)machina:build# uname -a
Linux machina 2.6.9-1.667 #1 Tue Nov 2 14:50:10 EST 2004 x86_64 x86_64 x86_64 GNU/Linux
[17:51:08](2)machina:build#
i think i am missing something simple.
one thing i have noticed, though, is that working in this directory
is really easy to _blow away_ /lib/modules/2.6.9-1.667/kernel/.
this is very alarming, so i need to be careful about building this stuff.
again, the goal is to automate compiling this module,
for _any_ FC3 machine (even if the kernel has been upgraded)
without installing a new kernel, of course.
the assumption is that the kernel running has been installed
relatively "properly" within the system, with all modules, etc.
thanks in advance,
-c
[*] i got the hint from the recent thread about the kernel sources ...
19 years, 6 months
Re: fedora-test-list Digest, Vol 9, Issue 96
by Borkowski Dariusz
> Here is my bug on the same issue:
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137579
>
> I was waiting too, until I found the fix.
>
> What do your control panel settings for sound look like ?
? I don't know. I didn't change anything there after FC3 install, so
there have to bee defaults.
> Are you rebooting to let Linux not recognize the blacklisted device ?
Of course.
> I had sound disabled when I made my change, rebooted and then enabled
> it.
After rebooting I checked volume sliders level, but there are ok.
> Can you successfully run alsamixer ?
Yes, I can. I pulled up all sliders to maximum volume in the Alsamixer.
I have one idea (will check this as I get home). To log into x as root
and try there. Maybe it'll help.
Darek Borkowski
19 years, 6 months
Bad dependencies in FC3
by Kim Lux
I reinstalled FC3 on our server machine to try to get past the init 5 x
respawning issue I had. (I suspect that x isn't installed on the server
installation and thus trying to run level 5 was a mistake on my part...)
Anyway: I installed the personal server setup and logged in. I then
used Add/Remove Packages to unselect a bunch of packages that I don't
need on the server: games, oofice, multimedia and so forth.
When I try to remove oofice, I get: Packages Not Found:
The following packages could not be found on your system.
Installation cannot continue until they are installed.
openoffice.org requ'd by openoffice.org-libs, 1.1.2-10
gnome-media requ'd by gnome-volume-manager 1.1.0-5
gthumb requ'd by ditto
libspi.so.0 libgail-gnome, 1.1.0-1
... There are about 12 packages in the list
I am going to run up2date to see if this fixes a few of them.
--
Kim Lux (Mr.) Diesel Research Inc
19 years, 6 months
FC3 disappointment: KsCD locks system; grip; CDROM in general.
by Kim Lux
Fedora Core 3 is an outstanding OS except for a few (sometimes very big)
flaws.
I've got big problems with KsCD, CDROM access in general and grip.
There were messages on the list about uDev problems with CDROMs before
the release. Why did we announce a big FC3 release when these problems
weren't fixed ? I fear that this sort of thing gives Linux in general a
big fat black eye
CDROM access: CDROM access on my computers has been iffy ever since
upgrading to FC3 (ie FC3t3, FC3rc3, FC3rc5, FC3 Final.) Clicking CDROM
in devices in KDE's File Manager used to give me mounting error
messages, but I used to be able to mount CDROMs manually. With FC3
Final, I have absolutely no CDROM access. I cannot eject a CDROM
without rebooting. Needless to say, this is a big pain. I think this
is entirely unacceptable in a final release.
KsCD: has always been a troublesome app. It will now lock my machine up
entirely if I play a CD with scratches on it. Either KsCD needs to be
fixed or it shouldn't ship with Fedora anymore. How can we keep shiping
an application that is so buggy ? I've hated KsCD since RH8 for issues
where it locks up the computer or interferes with other devices needing
access to the CDROM.
grip: is now totally incapacitated. It crashes with a segmentation
fault at start up. The first day I installed FC3, it ripped half a
dozen CDs very well. Then it hit a CD with scratches and it has gone
into some sort of loop that it can't get out of, not even with
rebooting.
While I am very happy with FC3 in general, I am very disappointed with
the fact that these large problems remained in a final version. I know
there was pressure for the team to keep up with the schedule, but was it
worth shipping a distro that is now going to cause a lot of people a lot
of headaches ?
I've got mixed feelings about the whole Fedora effort. I'm not sure
that its mandate is in sync with users. Is its focus on producing a
good, stable, usable distro for everyday use by run of the mill Linux
users or is it to push out Linux technology ASAP so that it gets
tested ?
I guess I've got the feeling that FC3 went out the door a bit early and
could have used another 2 weeks of testing and bug fixes. I'm sure that
the team adhered to the "it doesn't wreck any data" criteria, but I
think there are a few areas in FC3 that should have been polished a bit
more before it went out the door.
I've got a suggestion: I think that Fedora should continue its "bleeding
edge" mentality and that it should strive to ship 2-3 releases a year.
However, I think there should be sub releases in between releases that
do nothing but make the previous release perfect.
For example, I think the team should start working on a Fedora 3.1
release that fixes CDROM access, sound and a few other issues that seem
to remain in this release. The goal should be a near perfect release
before the team focuses on Fedora Core 4. CDROM access will need to be
fixed prior to FC4, so why not gather that and other fixes and put them
in another release ?
--
Kim Lux (Mr.) Diesel Research Inc
19 years, 6 months
ATI Radeon X 700 pro not in system-config-display
by RaXeT
Alan mentioned that the various PCI Express cards are supported in 2D
mode under FC3 Xorg.
However the particular card I have an interest in is the ATI Radeon X
700 pro, which system-config-display doesn't have a entry for.
I received word from a reliable source that perhaps this card isn't at
all supported in the latest xorg. Is there a hardware list for those
supported cards in xorg that I can look at?
Thanks in advance,
RaXeT
19 years, 6 months
Another NetworkManager question
by Amitabha Roy
I am noticing that on starting NMI, NM connects
to the best wireless signal it can associate with. (I think this is default
and expected behaviour, but can someone clarify that it is ?)
OK, rerun NMI and then connect
to a private wireless network XXX with WEP. The applet tells me that
it is connected to this network XXX with 30%signal strength. It sounds
very suspicious
so I look at iwconfig - and it actually shows association with a *different*
public network YYY that is not encrypted (which has a weak signal).
So when I restart NM and NMI, I know get to connect to the private network with
80% signal strength (its connected to XXX).
How is it possible that iwconfig and NM applet show conflicting information ?
In this case at least a 30% signal strength means that NM applet information
is actually incorrect.
I am using orinoco_cs rc2 and NM from CVS.
Also, can someone tell me where NM stores keys, ap information,
history of recorded
networks etc ? How can I reset all the information so that NM does not try
to repeat old mistakes ?
Amitabha
19 years, 6 months
Segfault with Up2date
by Jim Martin
I seem to be having a small problem getting up2date working on one of my
computers, when I run the rhn-applet it does nothing, when I run up2date
from the cli, it gives a segmentation fault and fails to run.
I have uninstalled it and re-installed it a couple of times with the
same results.
however, it is working fine on 2 other computers, and was working fine
in this one until this morning. not sure what happened, any help would
be great. thanks
Jim
19 years, 6 months
Fedora Core 3 Test Update: shadow-utils-4.0.3-42
by Adrian Havill
---------------------------------------------------------------------
Fedora Test Update Notification
FEDORA-2004-435
2004-11-16
---------------------------------------------------------------------
Product : Fedora Core 3
Name : shadow-utils
Version : 4.0.3
Release : 42
Summary : Utilities for managing accounts and shadow password files.
Description :
The shadow-utils package includes the necessary programs for
converting UNIX password files to the shadow password format, plus
programs for managing user and group accounts. The pwconv command
converts passwords to the shadow password format. The pwunconv command
unconverts shadow passwords and generates an npasswd file (a standard
UNIX password file). The pwck command checks the integrity of password
and shadow files. The lastlog command prints out the last login times
for all users. The useradd, userdel, and usermod commands are used for
managing user accounts. The groupadd, groupdel, and groupmod commands
are used for managing group accounts.
---------------------------------------------------------------------
Update Information:
Artificial limits regarding the maximum amount of users (previously 1024)
have been removed. Now limited only by memory/disk space. "add machine
script"
feature in Samba can now be used again.
---------------------------------------------------------------------
* Tue Nov 16 2004 Adrian Havill <havill(a)redhat.com> 2:4.0.3-42
- change MAXMEM static limit on group count to dynamic (#125510)
- re-allow "$" as last char for the sake of samba (#132782)
- don't strip binaries for debuginfo
---------------------------------------------------------------------
This update can be downloaded from:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/3/
d52b31c3218bcb76f9693a3f75f5a45e SRPMS/shadow-utils-4.0.3-42.src.rpm
b429012b1b09f90c7e08e59a61a47622 x86_64/shadow-utils-4.0.3-42.x86_64.rpm
1e985d22ac9cbbe37dd3bb6f0715f359
x86_64/debug/shadow-utils-debuginfo-4.0.3-42.x86_64.rpm
335c22b13a5280375634dc37a474e3bd i386/shadow-utils-4.0.3-42.i386.rpm
92146f734f0115e7e80a7dedf1f01312
i386/debug/shadow-utils-debuginfo-4.0.3-42.i386.rpm
This update can also be installed with the Update Agent; you can
launch the Update Agent with the 'up2date' command. You may
need to edit your up2date channels configuration. Within
/etc/sysconfig/rhn/sources enable the following line:
yum updates-testing
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/3...
---------------------------------------------------------------------
19 years, 6 months
access scsi tape drive under I2O??
by Eric Hoeve
I have:
Adaptec 2000S zero-channel RAID controller 32MB (BIOS 1.41 2001/07/13)
and therefore using I2O.
I did a default custom install of FC3 and was able to install everything
just fine. I have no problems with installation, but I am unable to
access my scsi tape drive (A Sony SDT-11000: Channel 1 ID 6).
I am running the following modules:
i2o_core,i2o_proc,i2o_config,i2o_block
Under /proc/i2o/iop0/206
I see:
authorized_users ddm_identity dev_name phys_dev
sensors user_info claimed dev_identity groups
priv_msgs sgl_limits users
The only interesting one seemed to be dev_identity
cat /proc/i2o/iop0/206/dev_identity
Device Class : SCSI Device
Owner TID : 0xfff
Parent TID : 0x009
Vendor info : SONY S
Product info : SDT-11000
Description : 0
Product rev. : 0200
Serial number :
Hardware:
Supermicro P4DP6/E7500/Adaptec 7899W Ultra 160
Dual Xeon 2.4
4 GB RAM
Adaptec 2000S zero-channel RAID controller 32MB (BIOS 1.41 2001/07/13)
Matrox G540 Dual Head Video Controller
Soundblaster Live 5.1
Sony SDT-11000 DDS-4 68-pin Ultra 2/LVD
I can supply more info upon request.
Thanks in advance
-Eric
--
Eric Hoeve fedora at ehoeve dot com
19 years, 6 months