Re: RFD: Kernel release numbering
On Wed, 2 Mar 2005, Russell Miller wrote: On Wednesday 02 March 2005 19:37, Linus Torvalds wrote: That's the whole point here, at least to me. I want to have people test things out, but it doesn't matter how many -rc kernels I'd do, it just won't happen. It's not a "real release". In contrast, making it a real release, and making it clear that it's a release in its own right, might actually get people to use it. I agree with the first part of your mail that I quoted above. Indeed, the -rc releases are not a "real release", and therefore people aren't going to test it. What you are missing is that if you use the method you have proposed. odd numberered kernels will stop being a "real release" as well to a great deal of users. The problem as stated is that people are not downloading and testing the test releases. Define people. Some won't download a thing, they will take whatever the distros feed them. Some will download and test the latest patchset frequently, especially if someone asks. Some are interested only in a particular subsystem or feature. Your solution to that problem is to make test releases look like real releases and maybe people will test them anyway. I believe the solution is slowly working its way out. Previously there were only two stark choices, either you could be stable, safe, and boring, or you could use the development series and things could break horribly. I believe having a place where things could be tried out, such as the -mm kernels, was a great idea. IMHO the 2.5 development series was long enough to be painful almost to the point of being counterproductive. I think part of the problem with development series in general is/was a lack of focus. If the announced goal of the 2.5 series had been confined to changing module loading and latency/scheduling issues at the beginning, it would have been a lot shorter, and better. I would like to see an even/odd stable/development cycle where the development cycle is limited to two or three major ideas and APIs don't change in stable cycles. New features not likely to cause breakage or new driver support could be targeted for the -mm kernels. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: VIA KT133A crash *post* 2.4.3-ac6
On Sat, 16 Jun 2001, Rachel Greenham wrote:
> Thomas Molina wrote:
>
> >So is there no correlation from particular hardware to problems reported?
> >I'm running the A7V133 with a Western Digital WD300BB UDMA 5 drive on
> >kernel 2.4.5 with no trouble.
> >
> Well, I don't know. I'd guess there'd *have* to be some correlation, but
> we're not gathering enough information to see the pattern. ie: which
> BIOS version, what exact BIOS options are set, what processor/speed,
> what memory, what exact model of hard disk... We just may not have a big
> enough sample size. Even in my case the crashes aren't predictable in
> nature - 2.4.4 passed my bonnie test the first time, making me think the
> problem was introduced in 2.4.5, and only failed later in normal usage -
> next time I tested it it failed in the first minute or so. *Most* of the
> time failures occur during the bonnie test, but at all sorts of random
> times during the test.
I'm certainly willing to provide any data it's decided is necessary to
collect to make the correlations. I'll even volunteer to be the
collection point for such data. Beyond mainboard version, bios version,
and perhaps hard drive info I'm not sure what's appropriate.
I've tried most of the tests you all have been discussing, with a couple
of exceptions. I haven't tried bonnie ( don't even know where to get it
or what it is supposed to test ). I do create a number of CDs each week
so I am copying a moderate amount of data per session; my setup may be a
bit different - I have the hard drive on the promise interface (ide2) and
cdroms on the first ide interface (ide0) so I'm probably not testing the
same ide-to-ide copy problem that others are seeing.
> as long as you're sure you do have DMA enabled that is - SuSE
> at least leaves it disabled by default, under which conditions all
> kernels are stable for me
Fairly certain. I could be misinterpreting things, though. Here is some
output I'm seeing:
[root@localhost /root]# hdparm -tT /dev/hde
/dev/hde:
Timing buffer-cache reads: 128 MB in 0.70 seconds =182.86 MB/sec
Timing buffered disk reads: 64 MB in 2.31 seconds = 27.71 MB/sec
[root@localhost /root]# hdparm /dev/hde
/dev/hde:
multcount= 0 (off)
I/O support = 0 (default 16-bit)
unmaskirq= 0 (off)
using_dma= 1 (on)
keepsettings = 0 (off)
nowerr = 0 (off)
readonly = 0 (off)
readahead= 8 (on)
geometry = 3649/255/63, sectors = 58633344, start = 0
[root@localhost /root]# hdparm -i /dev/hde
/dev/hde:
Model=WDC WD300BB-00AUA1, FwRev=18.20D18, SerialNo=WD-WMA6W1592536
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq
}
RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40
BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=58633344
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Data-corruption bug in VIA chipsets
On Sat, 14 Apr 2001, Dan Podeanu wrote: > On 13 Apr 2001, Doug McNaught wrote: > > > Alan Cox <[EMAIL PROTECTED]> writes: > > > > > > Here might be one of the resons for the trouble with VIA chipsets: > > > > > > > > http://www.theregister.co.uk/content/3/18267.html > > > > > > > > Some DMA error corrupting data, sounds like a really nasty bug. The > > > > information is minimal on that page. > > > > > > What annoys me is that we've known about the problem for _ages_. If you look > > > the 2.4 kernel has experimental workarounds for this problem. VIA never once > > > even returned an email to say 'we are looking into this'. Instead people sat > > > there flashing multiple BIOS images and seeing what made the difference. > > > > Is this problem likely to affect 2.2.X? I have a VIA-based board on > > order (Tyan Trinity) and I don't plan to run 2.4 on it anytime soon > > (it's upgrading a stock RH6.2 box). > > > > We've had HUGE problems with 2.4.x kernels and VIA based boards. We have > here 3 VIA boards with Athlon/850 and Duron/900 CPUs. The problem goes > like this: > > Compile 2.4.3 with VIA and Athlon support. > Reboot. > Ooopses (between 1 and continuously scrolling of them) occur at random > periods of time, between mounting the root filesystem and 2-3 minutes of > functionality. > Interesting. I have an ASUS A7V board I'm running an Athlon 900 on with none of the problems noted here. Are there specific hardware correlations that people have noted? It does have the 686B southbridge noted in the article as causing problems. The BIOS thing is interesting though. I work part time in a computer repair shop. With the A7V boards you never know which BIOS version will be on the board. The A7V is one of the most popular ones we have for AMD chips. We sell a ton of them, so if there are problems I'd sure like to be kept up to date. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: problem when booting 2.4.3 from a floppy disk
On Sat, 7 Apr 2001, François Dupoux wrote: > Hi, > > I have a strange bug when trying to boot a kernel-2.4.3 (official release) > from an 1.44 MB floppy disk. Just after the "Loading...", there is an > infinite loop, and this message is printed: > 0200 > AX: 0212 > BX: BC00 > CX: 5101 > DX: > 0200 > AX: 0212 > BX: BC00 > CX: 5101 > DX: > Do you have any suspect hardware in your system? The reason I ask is that I have a part time job working in a computer shop where I build and repair ix86 systems. I've seen this occasionally when I use a 2.4.X boot floppy to diagnose system problems. It hasn't been consistent and it hasn't happened often enough to correlate with anything else. I've resolved to keep formal statistics on systems which exhibit this problem so I would appreciate a cc on any followups to this. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4 kernels - "attempt to access beyond end of device"
On Thu, 1 Mar 2001, Petr Vandrovec wrote: > On 28 Feb 01 at 15:47, Michal Jaegermann wrote: > > > > I have more checks to make before I will be fully satisfied but > > > > this looks like it. > > > ... > > > > System Performance Setting [Optimal, Normal] > > > ... > > > > > > Try BIOS 1006. AFAIK 1005D changed some VIA values for 'optimal'. > > > > Is that important here? IDE drives in question were not connected to > > on-board controller but the Promise one. Results seem to indicate > > that this 'optimal' was important here anyway. > > VIA host-bridge, not VIA-IDE... It is important even if you use Promise > only - look back through archives, there must be something really wrong > with this motherboard. I'm beginning to believe it may be BIOS revision related. I haven't tried the Promise controller since I don't have an ATA-100 drive, but I don't seem to have any of the data corruption or other problems that people have mentioned. I guess I'll hold off updating the BIOS for now though. I bought the motherboard not two weeks ago, together with a Athlon 900MHz processor and it has BIOS version 1004D. I have seen problems even with Windows using the 1005D version though. My shop has been selling a LOT of this board; the problems we've seen come back seem to be specifically related to 1005D. Reflashing to 1004D has cured any problems I've seen. I've not seen any new hardware come through from the factory with 1006 though. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.1ac17 hang on mounting loopback fs
On Sat, 17 Feb 2001, Pete Toscano wrote: > reading this, I see now why mkbootdisk was locking in the D state with > the loop mounted... Would this also explain not being able to seek > forward while writing a floppy? > > I was trying to make the GRUB boot disk by writing the stage 1 and 2 > loaders to the floppy (as per the GRUB docs) with dd: > > [root@bubba grub]# dd of=/dev/fd0 if=stage1 bs=512 count=1 > 1+0 records in > 1+0 records out > [root@bubba grub]# dd of=/dev/fd0 if=stage2 bs=512 seek=1 > dd: advancing past 1 blocks in output file `/dev/fd0': Permission denied Different problem. Add conv=notrunc to the dd command to make it work. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: time in the future during make for 2.4.0
On Sun, 28 Jan 2001 [EMAIL PROTECTED] wrote: > > I had this problem when I was upgrading my kernel, and happened to do > it during the daylight savings time roll-back. Confused the heck out > of me for a while. Anyways, you can try 'touching' all your files, > and do a 'make clean' then try again. If it doesn't complain about a > long arg list, you can try 'touch `find . -type f`'. Several people emailed me with similar comments. It seems I occasionally have this habit of making myself look foolish. The explanation is this: Yesterday I put a new processor and motherboard into the system. When I set up the BIOS I put in a date one day into the future. This morning's cron job called a remote time server which corrected the date. When I compiled the kernel this morning, confusion reigned. Sorry for bothering everyone. Touching the files did fix the problem. I'll probably find a few more floating around causing problems until 0302 tomorrow morning when I'm past all the future dates. The motherboard change was instructive as was going from a K6-2 to an Athlon. Linux booted up without a problem while Windows crashed and burned. The best part was that I knew what was going to happen and I had an audience. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
time in the future during make for 2.4.0
I seem to recall a discussion on faster processors causing timing problems during a kernel make, but I'm unable to find it in the kernel archives. I've now upgraded to an Athlon 900 MHz processor and an ASUS A7V motherboard and have started seeing this. It shows up as the following messages during a make bzImage: make[3]: *** Warning: Clock skew detected. Your build may be incomplete. make[3]: *** Warning: File `/mnt/hd/local/kernel/linux.24.new/include/linux/sched.h' has modification time in the future (2001-01-28 17:41:05 > 2001-01-28 10:07:02) I would appreciate any pointers to the discussion archive or solutions. It doesn't seem to have a major problem with kernel compiles, but it appears to send compiles of lm-sensors 2.5.5 into endless loops. Each loop begins with the following: make: *** Warning: File `/usr/local/kernel/linux/include/linux/types.h' has modification time in the future (2001-01-28 17:41:05 > 2001-01-28 12:21:28) gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/usr/local/kernel/linux/include -O2 prog/detect/i2cdetect.c | \ sed -e 's@^\(.*\)\.o:@prog/detect/i2cdetect.rd prog/detect/i2cdetect.ro: Makefile '`dirname prog/detect/i2cdetect.rd`/Module.mk' @' > prog/detect/i2cdetect.rd and ends with the following before starting over again: gcc -M -MG -I. -Ikernel/include -I/usr/local/include -I/usr/local/kernel/linux/include -O2 -D__KERNEL__ -DMODULE -fomit-frame-pointer -DEXPORT_SYMTAB -DMODVERSIONS -include /usr/local/kernel/linux/include/linux/modversions.h kernel/sensors.c | \ sed -e 's@^\(.*\)\.o:@kernel/sensors.d kernel/sensors.o: Makefile '`dirname kernel/sensors.d`/Module.mk' @' > kernel/sensors.d - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
problem with dd for floppy under 2.4.0
[1.] One line summary of the problem: seek= parameter for dd under 2.4.0
gives permission denied error
[2.] Full description of the problem/report:I was creating a new
root+boot disk for 2.4.0 this evening. I issued the command:
dd if=/tmp/rootfs.gz of=/dev/fd0 bs=1k seek=335
and got the error message:
dd: /dev/fd0: Permission denied
Under 2.2.18 the copy succeeds. Under 2.4.0, specifying a non-zero seek
paramter results in an error.
[3.] Keywords (i.e., modules, networking, kernel): floppy, dd, copy
[4.] Kernel version (from /proc/version):
Linux version 2.4.0 (tmolina@wr5z) (gcc version egcs-2.91.66
19990314/Linux (egcs-1.1.2 release)) #1 Sat Jan 20 15:20:46 CST 2001
[5.] Output of Oops.. message (if applicable) N/A
[6.] A small shell script or example program which triggers the
problem (if possible) See 2. above
[7.] Environment
[7.1.] Software (add the output of the ver_linux script here)
-- Versions installed: (if some fields are empty or look
-- unusual then possibly you have very old versions)
Linux wr5z 2.4.0 #1 Sat Jan 20 15:20:46 CST 2001 i586 unknown
Kernel modules 2.4.1
Gnu C egcs-2.91.66
Gnu Make 3.78.1
Binutils 2.9.5.0.22
Linux C Library2.1.3
Dynamic linker ldd (GNU libc) 2.1.3
Procps 2.0.6
Mount 2.10f
Net-tools 1.54
Console-tools 0.3.3
Sh-utils 2.0
Modules Loaded opl3
[root@wr5z linux]# dd --version
dd (GNU fileutils) 4.0p
[7.2.] Processor information (from /proc/cpuinfo):
[root@wr5z linux]# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 5
model : 8
model name : AMD-K6(tm) 3D processor
stepping: 12
cpu MHz : 451.031
cache size : 64 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow
k6_mtrr
bogomips: 897.84
[7.3.] Module information (from /proc/modules):
opl3 11904 0 (unused)
[7.4.] Loaded driver and
hardware information (/proc/ioports,
/proc/iomem)
[root@wr5z linux]# cat /proc/ioports
-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial(auto)
0376-0376 : ide1
0388-038b : Yamaha OPL3
03bc-03be : parport0
03c0-03df : vesafb
03f6-03f6 : ide0
03f8-03ff : serial(auto)
0cf8-0cff : PCI conf1
5000-50ff : VIA Technologies, Inc. VT82C586B ACPI
d000-dfff : PCI Bus #01
d000-d0ff : ATI Technologies Inc 3D Rage Pro AGP 1X/2X
e000-e00f : VIA Technologies, Inc. Bus Master IDE
e000-e007 : ide0
e008-e00f : ide1
e800-e87f : Digital Equipment Corporation DECchip 21041 [Tulip Pass 3]
e800-e87f : eth0
ec00-ec3f : 3Com Corporation 3c900 10BaseT [Boomerang]
ec00-ec3f : eth1
[root@wr5z linux]# cat /proc/iomem
-0009fbff : System RAM
0009fc00-0009 : reserved
000a-000b : Video RAM area
000c-000c7fff : Video ROM
000f-000f : System ROM
0010-03ff : System RAM
0010-0021f62b : Kernel code
0021f62c-002939c7 : Kernel data
e000-e3ff : VIA Technologies, Inc. VT82C597 [Apollo VP3]
e400-e7ff : PCI Bus #01
e400-e4ff : ATI Technologies Inc 3D Rage Pro AGP 1X/2X
e400-e47f : vesafb
e600-e6000fff : ATI Technologies Inc 3D Rage Pro AGP 1X/2X
ea00-ea7f : Digital Equipment Corporation DECchip 21041 [Tulip
Pass 3]
ea00-ea7f : eth0
- : reserved
[7.5.] PCI information ('lspci -vvv' as root) N/A
[7.6.] SCSI information (from /proc/scsi/scsi) N/A
[7.7.] Other information that might be relevant to the problem
(please look in /proc and include all information that you
think to be relevant):
Under 2.2.18 I get the following extract from strace:
open("/tmp/rootfs.gz", O_RDONLY|O_LARGEFILE) = 0
close(1)= 0
open("/dev/fd0", O_RDWR|O_CREAT|O_LARGEFILE, 0666) = 1
ftruncate64(0x1, 0x53c00, 0, 0, 0x1)= -1 ENOSYS (Function not
implemented)
ftruncate(1, 343040)= 0
rt_sigaction(SIGINT, NULL, {SIG_DFL}, 8) = 0
Under 2.4.0 I get the following extract from strace:
open("/tmp/rootfs.gz", O_RDONLY|O_LARGEFILE) = 0
close(1)= 0
open("/dev/fd0", O_RDWR|O_CREAT|O_LARGEFILE, 0666) = 1
ftruncate64(0x1, 0x53c00, 0, 0, 0x1)= -1 EACCES (Permission denied)
write(2, "dd: ", 4) = 4
write(2, "/dev/fd0", 8) = 8
write(2, ": Permission denied", 19) = 19
write(2, "\n", 1) = 1
_exit(1)= ?
Under 2.4.0 I get the following from strace if I don't include the seek=
paramter for the copy:
open("/tmp/rootfs.gz", O_RDONLY|O_LARGEFILE) = 0
close(1)
2.2.18 compile warnings
I get a large number of warnings like the following when compiling
2.2.18:
{standard input}:338: Warning: using `%eax' instead of `%ax' due to `l'
suffix
I'm using the compiler from RedHat 6.2:
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: Announce: modutils 2.3.21 is available
On Wed, 22 Nov 2000, David Ford wrote: > > > * Remove compile warnings in xstrcat. > > > * snprintf cleanups. > > > * Set safemode when uid != euid. > > > * Strip quotes from shell responses. > > + add RedHat ism's with a --rhc (red hat compatible) -i -m (-F) > > > > RedHat kind of is the standard in the commercial world in the US. > > I don't think it's necessary or appropriate to taylor things for a particular > distribution even if it may unfortunately be 'standard' for some people. Zackerly. My system will certainly look like a RedHat system; it's based on one. However (particularly with regards to kernels and modules), I can almost guarantee it won't react like a RedHat system. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: opl3.o initialization problems in 2.4
On Tue, 14 Nov 2000, Christoph Hellwig wrote: > In article <[EMAIL PROTECTED]> you wrote: > > I continue to see apparent interaction problems between sb.o and opl3.o > > during system initialization. Several people have reported problems > > with the opl3.o module not loading or not working properly. A > > workaround was developed which results in a functional system; if sb.o > > is compiled as built-in and opl3.o is compiled modular things work. > > > My working theory is that the soundcard must be initialized and the > > driver functioning before the opl3 module can initialize its function on > > the card. Currently, the opl3 code is executed before the soundcard > > code and is unable to initialize the fm synthesizer. > > > I hate to reignite the link order war, but I would appreciate a > > clarification of the situation. > > This is strange. CONFIG_SOUND_YM3812 (the opl3 config options) > is actually _after_ CONFIG_SB in the Makefile. > > Does it work if both drivers are modular? Sorry this took so long. The short answer is no, it only works if the soundcard is built in and opl3 is modular. This seems to apply mainly to soundblaster. The long answer is that I've been trying to debug this myself, but I don't understand what I'm seeing, particularly with respect to module loadng and initialization. I wanted to present what I've found in hopes that either someone will tell me what I'm doing wrong or else this will help someone debug a problem. I have a PAS16 soundcard. It includes a Soundblaster compatible chip with it and has an OPL3 synthesizer. I have the following in /etc/lilo.conf: append="pas2=0x388,10,3,-1,0x220,5,1,-1 sb=0x220,5,1,-1 opl3=0x388" If pas2, sb, and opl3 are all built in, the kernel attempts to initialize the opl3 first. In this case io is -1 when the init_opl3 function is executed, and the fm synthesizer is not detected. I have the following in modules.conf: options opl3 io=0x388 options pas2 io=0x388 irq=10 dma=3 options sb io=0x220 irq=5 dma=1 If I build everything modular and attempt to modprobe opl3 before initializing the soundcard, io is 0x388 as it should be, but the signature it reads from the card is 0xff instead of 0x0 as it should be. If I modprobe pas2 and modprobe sb, weird things happen. I get the following on the screen: [root@wr5z /root]# modprobe sb /lib/modules/2.4.0-test11-pre4-tm7/kernel/drivers/sound/sb.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.0-test11-pre4-tm7/kernel/drivers/sound/sb.o: insmod /lib/modules/2.4.0-test11-pre4-tm7/kernel/drivers/sound/sb.o failed /lib/modules/2.4.0-test11-pre4-tm7/kernel/drivers/sound/sb.o: insmod sb failed and I get in dmesg: Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996 sb: dsp reset failed. If I now try modprobe opl3 it reads the correct signature from the card and I get the following in dmesg: YM3812 and OPL-3 driver Copyright (C) by Hannu Savolainen, Rob Hooft 1993-1996 at 0x388 but I get the following on the screen: [root@wr5z /root]# modprobe opl3 at 0x388 /lib/modules/2.4.0-test11-pre4-tm7/kernel/drivers/sound/opl3.o: init_module: Device or resource busy Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.0-test11-pre4-tm7/kernel/drivers/sound/opl3.o: insmod /lib/modules/2.4.0-test11-pre4-tm7/kernel/drivers/sound/opl3.o failed insmod opl3 failed [root@wr5z /root]# Nov 14 18:40:14 wr5z kernel: at 0x388 lsmod at this point shows: [root@wr5z sound]# lsmod Module Size Used by pas2 13392 0 (unused) sb_lib 34720 0 uart401 6512 0 [sb_lib] If I try to execute playmidi, using the synthesizer I get the following oops: ksymoops 2.3.4 on i586 2.4.0-test11-pre4-tm7. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.0-test11-pre4-tm7/ (default) -m /boot/System.map (specified) Unable to handle kernel paging request at virtual address c503a580 c01d6676 *pde = 011c2063 Oops: CPU:0 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010282 eax: ebx: ecx: 0001 edx: c503a580 esi: c0295fe0 edi: c029618c ebp: 0002 esp: c2eefec0 ds: 0018 es: 0018 ss: 0018 Process playmidi (pid: 622, stackpage=c2eef000) Stack: c0295d60 0001 0001 0001 0001 c01d846a 0001 c303de00 c0295d60 c2f9b740 c2eeff30 c01cf531 c2f083c0 c303de00 c303de00 c2f083c0 c11ae260 c02963a0 c2f083c0 Call Trace: [] [] [] [] [] [] [] Code: 8b 02 85 c0 74 0d ff 40 10 8b 06 8b 00 80 48 14 18 8b 16 55 >>EIP; c01d6676<= Trace; c01d846a Trace; c01cf531 Trace; c013555d Trace; c013470f Trace; c0134647 Trace; c013493c Trace; c010b2c3 Code;
opl3.o initialization problems in 2.4
I continue to see apparent interaction problems between sb.o and opl3.o during system initialization. Several people have reported problems with the opl3.o module not loading or not working properly. A workaround was developed which results in a functional system; if sb.o is compiled as built-in and opl3.o is compiled modular things work. My working theory is that the soundcard must be initialized and the driver functioning before the opl3 module can initialize its function on the card. Currently, the opl3 code is executed before the soundcard code and is unable to initialize the fm synthesizer. I hate to reignite the link order war, but I would appreciate a clarification of the situation. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: opl3 under 2.4.0-test10
On Sat, 11 Nov 2000, Stephen Thomas wrote: > Mark Hindley wrote: > > I am trying to setup my ALS 110 soundcard under my build of kernel > > 2.4.0-test10. > > > > I have built in isapnp support and also the sb and opl3 drivers. > > > > However, even though I pass opl3=0x388 on the Kernel command line all > > I get is an isapnp panic. > > CONFIG_SOUND_YM3812=y > > and I'm passing "opl3=0x388" to the driver. However, if I query > what synth devices the driver supports, it only reports an > AWE32-0.4.4 (RAM512k) sample device. I expect it report an FM synth > device, too. I get the same (lack of) effect if I go via the > adlib_card code, by saying "adlib=0x388". My investigations so > far have shown that when opl3_detect() first tries to get the > signature of the OPL3 device, it gets 0xff from the inb() (line > 195 of drivers/sound/opl3.c in test11pre1), while the corresponding > code in 2.2.18pre19 gets 0x00. Can you try resetting CONFIG_SOUND_YM3812 to m rather than y. I had a similar problem and that is the workaround I came up with. I haven't gone back and tried to see why it happened; maybe I need to. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
patch for pas16 configuration in 2.4
This patch allows someone to select only Pro Audio Spectrum configuration and get both PAS and SB emulation, as intended. Small changes were also made to documentation. It appears that it is too late for inclusion before 2.4 final, but is submitted now for comments. diff -urN linux.old/Documentation/Configure.help linux.new1/Documentation/Configure.help --- linux.old/Documentation/Configure.help Wed Nov 8 08:48:53 2000 +++ linux.new1/Documentation/Configure.help Wed Nov 8 10:29:26 2000 @@ -13861,6 +13861,8 @@ 16 or Logitech SoundMan 16 sound card. Answer N if you have some other card made by Media Vision or Logitech since those are not PAS16 compatible. Please read Documentation/sound/PAS16. + It is not necessary to add Sound Blaster support separately; it + is included in PAS support. If you compile the driver into the kernel, you have to add "pas2=,,, diff -urN linux.old/Documentation/sound/PAS16 linux.new1/Documentation/sound/PAS16 --- linux.old/Documentation/sound/PAS16 Sun Apr 2 17:38:53 2000 +++ linux.new1/Documentation/sound/PAS16Wed Nov 8 11:06:37 2000 @@ -1,7 +1,7 @@ Pro Audio Spectrum 16 for 2.3.99 and later = by Thomas Molina ([EMAIL PROTECTED]) -last modified 26 Mar 2000 +last modified 8 Nov 2000 Acknowledgement to Axel Boldt ([EMAIL PROTECTED]) for stuff taken from Configure.help, Riccardo Facchetti for stuff from README.OSS, and others whose names I could not find. @@ -48,14 +48,6 @@ if you want to use the SB emulation of PAS16. It's also possible to the emulation if you want to use a true SB card together with PAS16 (there is another question about this that is asked later). - "Sound Blaster support", -- Answer 'y' if you have an original SB card made by Creative Labs - or a full 100% hardware compatible clone (like Thunderboard or - SM Games). If your card was in the list of supported cards (above), - please look at the card specific instructions later in this file - before answering this question. For an unknown card you may answer - 'y' if the card claims to be SB compatible. - Enable this option also with PAS16. "Generic OPL2/OPL3 FM synthesizer support", - Answer 'y' if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4). @@ -113,27 +105,13 @@ Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio 16 or Logitech SoundMan 16 sound card. Don't answer Y if you have some other card made by Media Vision or Logitech since they are not - PAS16 compatible. + PAS16 compatible. It is not necessary to enable the separate + Sound Blaster support; it is included in the PAS driver. + If you compile the driver into the kernel, you have to add "pas2=,,, to the kernel command line. -100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support -CONFIG_SOUND_SB - Answer Y if you have an original Sound Blaster card made by Creative - Labs or a 100% hardware compatible clone (like the Thunderboard or - SM Games). For an unknown card you may answer Y if the card claims - to be Sound Blaster-compatible. The PAS16 has 8-bit Soundblaster - support, so you can answer Y here for it. - - Please read the file Documentation/sound/Soundblaster. - - If you compile the driver into the kernel and don't want to use isapnp, - you have to add "sb=,,," to the kernel command line. - - You can say M here to compile this driver as a module; the module is - called sb.o. - FM Synthesizer (YM3812/OPL-3) support CONFIG_SOUND_YM3812 Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4). @@ -167,7 +145,7 @@ CONFIG_SOUND_TRACEINIT=y CONFIG_SOUND_DMAP=y CONFIG_SOUND_PAS=y -CONFIG_SOUND_SB=y +CONFIG_SOUND_SB=n CONFIG_SOUND_YM3812=m I have also included the following append line in /etc/lilo.conf: diff -urN linux.old/drivers/sound/Makefile linux.new1/drivers/sound/Makefile --- linux.old/drivers/sound/MakefileMon Sep 25 14:32:54 2000 +++ linux.new1/drivers/sound/Makefile Wed Nov 8 09:58:56 2000 @@ -48,7 +48,7 @@ obj-$(CONFIG_SOUND_CS4232) += cs4232.o uart401.o obj-$(CONFIG_SOUND_OPL3SA2)+= opl3sa2.o ad1848.o mpu401.o obj-$(CONFIG_SOUND_MSS)+= ad1848.o -obj-$(CONFIG_SOUND_PAS)+= pas2.o sb_lib.o uart401.o +obj-$(CONFIG_SOUND_PAS)+= pas2.o sb.o sb_lib.o uart401.o obj-$(CONFIG_SOUND_SB) += sb.o sb_lib.o uart401.o obj-$(CONFIG_SOUND_WAVEFRONT) += wavefront.o obj-$(CONFIG_SOUND_MAUI) += maui.o mpu401.o - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Who will be responsible for 2.4.0 patches?
I want to make a minor change to the sound drivers Makefile for compiling pas16 as well as a modification to the documentation file. I'm told that since it is not a bugfix it needs to wait for post 2.4 final release. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
dropping untracked packets patch for 2.4 (fwd)
Linus,
Rusty Russell suggested I send the following patch to you. It redirects
to the log file those annoying dropping untracked packet messages. This
patch works agains any recent 2.4.0-test kernels.
diff -urN linux.new1/net/ipv4/netfilter/ip_nat_standalone.c
linux.new/net/ipv4/netfilter/ip_nat_standalone.c
--- linux.new1/net/ipv4/netfilter/ip_nat_standalone.c Sun Oct 22 15:19:07 2000
+++ linux/net/ipv4/netfilter/ip_nat_standalone.cSun Oct 22 13:37:44 2000
@@ -72,7 +72,7 @@
unreliable. */
if (!ct) {
if (net_ratelimit())
- printk("NAT: %u dropping untracked packet %p %u %u.%u.%u.%u ->
%u.%u.%u.%u\n",
+ printk(KERN_DEBUG "NAT: %u dropping untracked packet %p %u
+%u.%u.%u.%u -> %u.%u.%u.%u\n",
hooknum,
*pskb,
(*pskb)->nh.iph->protocol,
-- Forwarded message --
Date: Mon, 30 Oct 2000 15:50:18 +1100
From: Rusty Russell <[EMAIL PROTECTED]>
To: Thomas Molina <[EMAIL PROTECTED]>
Subject: Re: Three kernel messages
In message <[EMAIL PROTECTED]> you write
:
> I finally got tired of seeing these messages. Win98 boxes on my lan
> spew these each time they are booted and corrupt whatever virtual
> console I'm on. The following workaround sends these messages to
> /var/log/messages. Patch is against 2.4.0-test10-pre4, but should apply
> to recent kernels.
Thanks: please change to KERN_DEBUG and send to Linus...
Cheers,
Rusty.
--
Hacking time.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
oops in 2.4.0-test10-pre4 using gpm
[1.] One line summary of the problem: 2.4.0-test10-pre4 produces an oops while using gpm [2.] Full description of the problem/report: I got the enclosed oops the following way: cd to kernel source tree; ls -lR; when the listing is complete, use [SHIFT][PAGEUP] to scroll back as far as possible; use left mouse button to double click on filenames repeatedly; after highlighting some number of filenames the oops appeaars; The oops is non-fatal. gpm is killed and the stale file lock is deleted. gpm can be restarted with no apparent aftereffects. My system is RedHat 6.2 updated to account for requirements of 2.4.X. The kernel version number looks funky, but I've made only two modifications. One change is to the toplevel Makefile to add an extraversion symbol, and a change to a netfilter file to add a KERN_INFO to a printk to send the infamous "dropping untracked packet" messages to /var/log/messages instead of hitting the console. this oops happens in a text console, X was not active at the time. [3.] Keywords (i.e., modules, networking, kernel): fbcon, gpm, kernel [4.] Kernel version (from /proc/version): [tmolina@wr5z linux]$ cat /proc/version Linux version 2.4.0-test10-pre4-tm1 (tmolina@wr5z) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Sun Oct 22 13:42:39 CDT 2000 [5.] Output of Oops.. message (if applicable) with symbolic information resolved (see Documentation/oops-tracing.txt) ksymoops 2.3.4 on i586 2.4.0-test10-pre4-tm1. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.0-test10-pre4-tm1/ (default) -m /boot/System.map (specified) Oct 23 01:11:57 wr5z kernel: Unable to handle kernel paging request at virtual address c4764558 Oct 23 01:11:57 wr5z kernel: c01d61f5 Oct 23 01:11:57 wr5z kernel: *pde = Oct 23 01:11:57 wr5z kernel: Oops: 0002 Oct 23 01:11:57 wr5z kernel: CPU:0 Oct 23 01:11:57 wr5z kernel: EIP:0010:[fbcon_cfb24_putcs+425/1180] Oct 23 01:11:57 wr5z kernel: EFLAGS: 00010216 Oct 23 01:11:57 wr5z kernel: eax: c4764558 ebx: ecx: 00aa edx: aa00 Oct 23 01:11:57 wr5z kernel: esi: edi: ebp: c476455c esp: c30d1df8 Oct 23 01:11:57 wr5z kernel: ds: 0018 es: 0018 ss: 0018 Oct 23 01:11:57 wr5z kernel: Process gpm (pid: 1940, stackpage=c30d1000) Oct 23 01:11:57 wr5z kernel: Stack: c4764558 c025ba15 005f c02f5e14 0039 c3a0b600 0123 c02e2b00 Oct 23 01:11:57 wr5z kernel:00aa 00aa 00aa 0c00 000f c498c600 c4764558 c4764558 Oct 23 01:11:57 wr5z kernel:c028b081 c01d0cc7 c3a0b600 c02f5e14 c1150074 0001 00f3 Oct 23 01:11:57 wr5z kernel: Call Trace: [fb_con+1205/1824] [] [fbcon_putcs+203/232] [do_update_region+371/396] [invert_screen+375/388] [set_selection+1251/1512] [tioclinux+124/304] Oct 23 01:11:57 wr5z kernel: Code: 89 18 6a 60 68 15 ba 25 c0 55 8b 6c 24 48 83 c5 08 e8 75 10 Using defaults from ksymoops -t elf32-i386 -a i386 Code; Before first symbol <_EIP>: Code; Before first symbol 0: 89 18 mov%ebx,(%eax) Code; 0002 Before first symbol 2: 6a 60 push $0x60 Code; 0004 Before first symbol 4: 68 15 ba 25 c0push $0xc025ba15 Code; 0009 Before first symbol 9: 55push %ebp Code; 000a Before first symbol a: 8b 6c 24 48 mov0x48(%esp,1),%ebp Code; 000e Before first symbol e: 83 c5 08 add$0x8,%ebp Code; 0011 Before first symbol 11: e8 75 10 00 00call 108b <_EIP+0x108b> 108b Before first symbol [6.] A small shell script or example program which triggers the problem (if possible) see paragraph 2. [7.] Environment [7.1.] Software (add the output of the ver_linux script here) [tmolina@wr5z linux]$ sh scripts/ver_linux -- Versions installed: (if some fields are empty or look -- unusual then possibly you have very old versions) Linux wr5z 2.4.0-test10-pre4-tm1 #1 Sun Oct 22 13:42:39 CDT 2000 i586 unknown Kernel modules 2.3.19 Gnu C egcs-2.91.66 Gnu Make 3.78.1 Binutils 2.9.5.0.22 Linux C Library2.1.3 Dynamic linker ldd (GNU libc) 2.1.3 Procps 2.0.6 Mount 2.10f Net-tools 1.54 Console-tools 0.3.3 Sh-utils 2.0 Modules Loaded w83781d sensors i2c-isa opl3 [7.2.] Processor information (from /proc/cpuinfo): [tmolina@wr5z linux]$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 8 model name : AMD-K6(tm) 3D processor stepping: 12 cpu MHz : 451.32 cache size : 64 KB fdiv_bug: no hlt_bug : no sep_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid l
Re: CDROMPLAYTRKIND in 2.4.X
On Thu, 19 Oct 2000, Jens Axboe wrote: > > Admittedly I can't remember the last time I used cdp, but this seems > > like a recent problem. Are we going to look for a workaround? I've > > tried a number of player apps and they all appear to fail in the same > > way. > > > > Judging from past history I'd say the users are going to be told to bug > > the app maintainers to tell them it's broken Jim. It always comes out > > sounding a bit harsh. > > ide-scsi should probably just convert playtrkin to play_audio_10 > or play_audio_msf Assuming you are the maintainer of ide-scsi, is this the kind of change you'd be willing to accept? I got the idea this was one of those "we don't change the kernel to accomadate borken apps" deals. If your plate is full would you like me to look at it this weekend since I'm the one with the "problem"? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: test10-pre3
On Wed, 18 Oct 2000, Mike A. Harris wrote: > It's RNCD: Roman Numeral Coded Decimal. The new standard for > information interchange. A new proprietary feature of Intel > CPU's that will bring new high performance web sites to the reach > of the masses! Now you can access these special custom websites > only if you have a real Intel CPU! That is because other CPU's > from AMD, etc.. do not yet have the high technological edge of > "Roman Numeral Technology Extensions(TM)" (RMTE). And since IBM is getting into the open source movement they will issue their own version called ERNCDIC (Extended Roman Numeral Coded Decimal Interchange Code) to complement EBCDIC. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
CDROMPLAYTRKIND in 2.4.X
On Tue, 17 Oct 2000, Jens Axboe wrote: > On Tue, Oct 17 2000, Thomas Molina wrote: > > CD Recording seems to work correctly under 2.4.0-test10-pre3. I'm using > > cdrecord 1.9 with a Phillips CDD3610. However, playing back an audio cd > > using cdp gives the following error: > > > > sr0: CDROM (ioctl) reports ILLEGAL REQUEST. > > CDROMPLAYTRKIND: Operation not supported > > cd app players can't use CDROMPLAYTRKIND and expect it to always work. > It will fail on most setups with ide-scsi Admittedly I can't remember the last time I used cdp, but this seems like a recent problem. Are we going to look for a workaround? I've tried a number of player apps and they all appear to fail in the same way. Judging from past history I'd say the users are going to be told to bug the app maintainers to tell them it's broken Jim. It always comes out sounding a bit harsh. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Am I the only one with scsi-ide CDR problems?
On Mon, 16 Oct 2000, Scott Murray wrote: > On Sat, 14 Oct 2000, David Riley wrote: > > > safemode wrote: > > > > > > I'm just wondering if I'm the only person who has had problems with > > > 2.4.0-test9 recording on ide-scsi cdr's? > > > Nobody has posted anything about it and the test10-prex changefiles don't > > > mention it. cdrecord reports very weird results when scanning the scsi > > > bus whereas dmesg shows what one would expect of the ide-scsi detection. > > > anyone? > > > > Actually, I think it's on the TODO list for 2.4. That's definitely the > > sort of thing to fix. I think the exact syntax was "cdrecord produces > > shiny coasters" or something similar. > > It actually is in the "Fixed" section of the TODO list, and it did seem > to be working for me on the weekend, as I burnt a couple of disks (one at > 8x) under 2.4.0-test9 without any errors. That's with a relatively new > Matushita 8/4/32 CD-RW drive and cdrecord 1.8. CD Recording seems to work correctly under 2.4.0-test10-pre3. I'm using cdrecord 1.9 with a Phillips CDD3610. However, playing back an audio cd using cdp gives the following error: sr0: CDROM (ioctl) reports ILLEGAL REQUEST. CDROMPLAYTRKIND: Operation not supported There may have been a patch posted on the kernel list for this. As I'm having trouble accessing the archives at the moment I'm unable to test it. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: compile error in 2.4.0-test10-pre3
On Tue, 17 Oct 2000, Thomas Molina wrote: > I patched from 2.4.0-test9 to 2.4.0-test10-pre3 successfully. I then > did make mrproper, make oldconfig, make dep successfully. make bzImage > resulted in the following error: Would someone please hand me one of those brown paper bags. Note to self: Next time get some sleep before doing something stupid late at night and announcing same before everyone. I was confirming my problem about two minutes after sending that message, just before David Miller was kind enough to let me know what I was doing wrong. This was my first time doing a compile in a directory other than /usr/src/linux per Linus' suggestion. Specifically, /usr/include/asm and /usr/include/linux were stale symlinks. Pointing them to the new kernel source tree allowed the compile to proceed without incident. My hazy recollection told me Linus had said those symlinks shouldn't even be needed or should point to the "default" source tree against which glibc was compiled. I guess I was wrong. Hopefully this gets out before I get too many repeats of David's message. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
compile error in 2.4.0-test10-pre3
I patched from 2.4.0-test9 to 2.4.0-test10-pre3 successfully. I then did make mrproper, make oldconfig, make dep successfully. make bzImage resulted in the following error: [root@wr5z linux]# make bzImage gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/split-include scripts/split-include.c In file included from /usr/include/errno.h:36, from scripts/split-include.c:26: /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory make: *** [scripts/split-include] Error 1 Additional data: [root@wr5z linux]# sh scripts/ver_linux -- Versions installed: (if some fields are empty or look -- unusual then possibly you have very old versions) Linux wr5z 2.4.0-test9-pre2 #1 Sun Sep 17 21:35:55 CDT 2000 i586 unknown Kernel modules 2.3.16 Gnu C egcs-2.91.66 Gnu Make 3.78.1 Binutils 2.9.5.0.22 Linux C Library2.1.3 Dynamic linker ldd (GNU libc) 2.1.3 Procps 2.0.6 Mount 2.10f Net-tools 1.54 Console-tools 0.3.3 Sh-utils 2.0 Modules Loaded opl3 # # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_ISA=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # # 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_M686FXSR is not set CONFIG_MK6=y # CONFIG_MK7 is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_CMPXCHG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_L1_CACHE_BYTES=32 CONFIG_X86_ALIGNMENT_16=y CONFIG_X86_TSC=y CONFIG_X86_USE_PPRO_CHECKSUM=y # CONFIG_TOSHIBA is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_SMP is not set # CONFIG_X86_UP_IOAPIC is not set # # General setup # CONFIG_NET=y # CONFIG_VISWS is not set 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_NAMES=y # CONFIG_MCA is not set # CONFIG_HOTPLUG is not set # CONFIG_PCMCIA is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=m CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=m CONFIG_PM=y # CONFIG_ACPI is not set CONFIG_APM=y # CONFIG_APM_IGNORE_USER_SUSPEND is not set # CONFIG_APM_DO_ENABLE is not set # CONFIG_APM_CPU_IDLE is not set # CONFIG_APM_DISPLAY_BLANK is not set # CONFIG_APM_RTC_IS_GMT is not set # CONFIG_APM_ALLOW_INTS is not set CONFIG_APM_REAL_MODE_POWER_OFF=y # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # CONFIG_PARPORT=y CONFIG_PARPORT_PC=y # CONFIG_PARPORT_PC_FIFO is not set # CONFIG_PARPORT_PC_SUPERIO is not set # CONFIG_PARPORT_AMIGA is not set # CONFIG_PARPORT_MFC3 is not set # CONFIG_PARPORT_ATARI is not set # CONFIG_PARPORT_SUNBPP is not set # CONFIG_PARPORT_OTHER is not set CONFIG_PARPORT_1284=y # # Plug and Play configuration # # CONFIG_PNP is not set # CONFIG_ISAPNP is not set # # Block devices # CONFIG_BLK_DEV_FD=y # CONFIG_BLK_DEV_XD is not set # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_NBD is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 # CONFIG_BLK_DEV_INITRD is not set # # Multi-device support (RAID and LVM) # # CONFIG_MD is not set # CONFIG_BLK_DEV_MD is not set # CONFIG_MD_LINEAR is not set # CONFIG_MD_RAID0 is not set # CONFIG_MD_RAID1 is not set # CONFIG_MD_RAID5 is not set # CONFIG_BLK_DEV_LVM is not set # CONFIG_LVM_PROC_FS is not set # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_NETLINK=y CONFIG_RTNETLINK=y CONFIG_NETLINK_DEV=y CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_ARPD is not set # CONFIG_INET_ECN is not set CONFIG_SYN_COOKIES=y # # IP: Netfilter Configuration # CONFIG_IP_NF_CONNTRACK=y CONFIG_IP_NF_FTP=y # CONFIG_IP_NF_QUEUE is not set CONFIG_IP_NF_IPTABLES=y # CONFIG_IP_NF_MATCH_LIMIT is not set # CONFIG_IP_NF_MATCH_MAC is not set # CONFIG_IP_NF_MATCH_MARK is not set # CONFIG_IP_NF_MATCH_MULTIPORT is not set # CONFIG_IP_NF_MATCH_TOS is not set CONFIG_IP_NF_MATCH_STATE=y # CONFIG_IP_NF_MATCH_UNCLEAN
Re: ide-scsi seems to inhibit mounting CD-ROMs
On Sat, 30 Sep 2000, Timothy Little wrote: > >> When using ide-scsi to access a CDRW writer, the recording process works > >> but I am not able to mount any CD-ROM media in that drive for reading. > > > >And here it's exactly the opposite :) > > > >If anyone has a Philips CDD-36xx drive and cdrecord works, a private email > >would be gladly welcome. > > I think I went through almost every combination before getting it > right. There are about 10 different ways to get it wrong that look > plausible. It is even possible to get it wrong *after* following the > documentation, so I did. My CD-RW is a Phillips CDD-3610. I'm not sure who the person wanting input from a Phillips user was so I hope that person is reading here. I got cdrecord working by NOT compiling in ATAPI CD ROM support, and by compiling ide-scsi emulation as built-in rather than modular. I have a "regular" atapi cdrom and the above Phillips drive, both on the secondary IDE interface. the cdrom ends up at /dev/scd0 and the cdrw ends up at /dev/scd1. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: scsi emulation on 2.4.0-test8
On Fri, 29 Sep 2000, Richard Polton wrote: > Hi, > > I am using 2.4.0-test8 with scsi emulation turned on. I have one > internal atapi dvd-rom > drive and one external atapi cd-rw with a pcmcia interface. I enabled > scsi emulation and, > on the command line, set hdc=scsi and hde=scsi (where hdc is the dvd and > hde the cd-rw). Those parameters should probably be hdc-ide-scsi and hde=ide-scsi. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] for PAS16 functionality for 2.4
On Sun, 10 Sep 2000, Michael Elizabeth Chastain wrote: > I have written documentation on Rules.make and the interface between > Rules.make and Makefiles. It's here: > > ftp://ftp.shout.net/pub/users/mec/kbuild/x-Dkm-9.diff > > I would really like to see this documentation in the kernel. I've sent > it to Linus three times, and he's ignored it three times. I will try > some more after the release of 2.4.0. Thanks for a very lucid docfile. I would really urge it be included. I have just one metacomment. You have a number of sections (marked with ===) in the body of the text. Could we have those lines duplicated at the top in an "intro" section? (Sort of like This file covers the following topics...), perhaps with section designators. That would allow the reader to quickly search to the specific part he/she was interested in. I can produce a patch if you'd like. > Anyways ... I'd appreciate it if a couple of people would try this patch > so that I can submit it. > diff -u -r -N linux-2.4.0-test8/Rules.make linux/Rules.make > --- linux-2.4.0-test8/Rules.makeSun Aug 13 12:55:51 2000 > +++ linux/Rules.makeSun Sep 10 14:06:02 2000 > @@ -190,7 +190,7 @@ > # > ifdef CONFIG_MODULES > > -SYMTAB_OBJS = $(LX_OBJS) $(OX_OBJS) $(MX_OBJS) $(MIX_OBJS) > +SYMTAB_OBJS := $(sort $(LX_OBJS) $(OX_OBJS) $(MX_OBJS) $(MIX_OBJS)) > > ifdef CONFIG_MODVERSIONS > ifneq "$(strip $(SYMTAB_OBJS))" "" I tried the patch and it works for me! Thanks again. I'm also going to take a look at integrating sb functionality into pas2_card.c as Mr. Hellwig suggested, unless someone thinks that is a bad idea. That'll be later this week after I slog through integration of partial fractions (yuk). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] for PAS16 functionality for 2.4
On Sun, 10 Sep 2000, Christoph Hellwig wrote: > IMHO you should add some _more_ code to pas2_card.c so the sb stuff > is completly initialized there and sb.o (sb_card.c) is no more needed > for pas2. This means basically calling probe_sb() and attach_sb_card() > with the right parameters. Yeah. A quick inspection shows it may not be as complex as I first thought. I'll look at it after I catch up on Calculus (solids of revolution is currently kicking my butt), unless someone beats me to it. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] for PAS16 functionality for 2.4
On Sun, 10 Sep 2000, Michael Elizabeth Chastain wrote: > > Yepp. These warnings are there becuse of the way the list-style Makefiles > > work. You will see lots of them in drivers/net and drivers/scsi, too. > > Here's a patch. Let me know if it works for you; if it does, > I will submit it for 2.4.0. > > Here is some history: drivers/sound was the first of the list-style > Makefiles and has been using lists since the late 2.1.NN series. > Originally, drivers/sound/Makefile used $(sort ...) to remove duplicates. > > In 2.3.14, Linus introduced init sections. This made $(sort ...) > unusable for the construction of O_OBJS and OX_OBJS. > > Today, O_OBJS and OX_OBJS may contain duplicates, and Rules.make is > supposed to ignore the duplicates (while still preserving order). > The fact that SYMTAB_OBJS causes these warning messages is a bug. > > Anyways ... I'd appreciate it if a couple of people would try this patch > so that I can submit it. I'll try your patch and look at your documentation. I agree that the warnings are bugs. However, that was not the main point of my patch, it was a side effect. The point is that there was code in pas2_card.c to initialize the Soundblaster emulation in the PAS16. My patch merely added the sb.o module to the list of those brought in when CONFIG_SOUND_PAS was enabled in the configuration. I suppose the more basic question is: Should the Soundblaster-specific code in pas2_card.c be ripped out and leave only PAS-specific code in the PAS driver? Some might argue that would be a "cleaner" way of doing things. If the decision of my betters is that initialization should be left in PAS and the driver as separate (the current situation) then I believe my patch should stand. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] for PAS16 functionality for 2.4
On Sun, 10 Sep 2000, Christoph Hellwig wrote: > In article <[EMAIL PROTECTED]> you wrote: > > The enclosed patch corrects the Makefile and makes appropriate changes > > to various doc files. Please consider accepting this for the next > > kernel. This patch is against 2.4.0-test8. > > Aehmm. Your Makefile patch looks very strange: > > > -obj-$(CONFIG_SOUND_PAS) += pas2.o sb_lib.o uart401.o > > +obj-$(CONFIG_SOUND_PAS) += pas2.o sb.o sb_lib.o uart401.o > > Why do you remove sb.o from the object list? > The pas2 driver has no code to use the functions in sb_lib.o - > It has only some code to enable the sb emulation of the pas2 card. > Either you remove both sb.o and sb_lib.o and the pas2 sb emulation is gone, > or you leave it as is. Alternative: you can add code to use the sb_lib.o > stuff directly from the pas2 driver (this is the best solution, IMHO). I know I misunderstand things occasionally, but it looks ok to me. Isn't that just an artifact of the diff/patch thing? I simply added sb.o to the line when I edited it. That's the way I've always seen diff act. It deletes the original line and adds in an identical line with what I added in. The second line above adds in an identical line with sb.o added to the line. > > - PAS16 compatible. Please read Documentation/sound/PAS16. > > + PAS16 compatible. Do not enable both PAS16 support and Soundblaster > > + support since PAS16 support includes support for Soundblaster. > > + Please read Documentation/sound/PAS16. > > Why not - there shouldn't really be an issue with it. > It builds fine for me (and the various distributions kernel rpms). > And I doubt there is any runtime problem with that ... No there isn't a runtime problem. Linus went through a phase recently where he forced people to clean up "warnings" during the compile stage. If you answer yes to both CONFIG_SOUND_PAS and CONFIG_SOUND_SB you get "warinings" like this: /mnt/hd/src/linux-2.3.99pre/Rules.make:267: target `uart401.o' given more than once in the same rule. My change eliminates that by eliminating the need to include both. It also makes thing clearer IMHO. > > - insmod opl3 > > + modprobe opl3 > > either works well ... Modprobe seems cleaner to me. It's an opinion and it's in my docfile so I didn't see it as that big of a deal. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
[PATCH] for PAS16 functionality for 2.4
The PAS16 sound support includes code for the Soundblaster capability on the card. I found an apparent Makefile error which does not enable the Soundblaster support as anticipated. Adding SB support induces an error for uart401 being included twice at various points of the build process. The enclosed patch corrects the Makefile and makes appropriate changes to various doc files. Please consider accepting this for the next kernel. This patch is against 2.4.0-test8. Alan: would you like a patch for 2.2? If so, against which kernel? diff -urN linux/Documentation/Configure.help linux.new/Documentation/Configure.help --- linux/Documentation/Configure.help Sat Sep 9 09:44:39 2000 +++ linux.new/Documentation/Configure.help Sat Sep 9 14:06:54 2000 @@ -13699,7 +13699,9 @@ Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio 16 or Logitech SoundMan 16 sound card. Answer N if you have some other card made by Media Vision or Logitech since those are not - PAS16 compatible. Please read Documentation/sound/PAS16. + PAS16 compatible. Do not enable both PAS16 support and Soundblaster + support since PAS16 support includes support for Soundblaster. + Please read Documentation/sound/PAS16. If you compile the driver into the kernel, you have to add "pas2=,,, @@ -13710,7 +13712,8 @@ Answer Y if you have an original Sound Blaster card made by Creative Labs or a 100% hardware compatible clone (like the Thunderboard or SM Games). For an unknown card you may answer Y if the card claims - to be Sound Blaster-compatible. + to be Sound Blaster-compatible. Do not enable both Soundblaster + and PAS16 support. Please read the file Documentation/sound/Soundblaster. diff -urN linux/Documentation/sound/PAS16 linux.new/Documentation/sound/PAS16 --- linux/Documentation/sound/PAS16 Fri Apr 14 19:19:09 2000 +++ linux.new/Documentation/sound/PAS16 Sat Sep 9 14:32:15 2000 @@ -1,7 +1,7 @@ Pro Audio Spectrum 16 for 2.3.99 and later = by Thomas Molina ([EMAIL PROTECTED]) -last modified 26 Mar 2000 +last modified 9 Sep 2000 Acknowledgement to Axel Boldt ([EMAIL PROTECTED]) for stuff taken from Configure.help, Riccardo Facchetti for stuff from README.OSS, and others whose names I could not find. @@ -43,11 +43,10 @@ Pro Audio Studio 16 or Logitech SoundMan 16 (be sure that you read the above list correctly). Don't answer 'y' if you have some other card made by Media Vision or Logitech since they - are not PAS16 compatible. - NOTE! Since 3.5-beta10 you need to enable SB support (next question) - if you want to use the SB emulation of PAS16. It's also possible to - the emulation if you want to use a true SB card together with PAS16 - (there is another question about this that is asked later). + are not PAS16 compatible. PAS16 support includes support for + Soundblaster (sb.o module) so do not enable them both. + + "Sound Blaster support", - Answer 'y' if you have an original SB card made by Creative Labs or a full 100% hardware compatible clone (like Thunderboard or @@ -55,7 +54,7 @@ please look at the card specific instructions later in this file before answering this question. For an unknown card you may answer 'y' if the card claims to be SB compatible. - Enable this option also with PAS16. + Do not enable this option together with PAS16. "Generic OPL2/OPL3 FM synthesizer support", - Answer 'y' if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4). @@ -113,7 +112,10 @@ Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio 16 or Logitech SoundMan 16 sound card. Don't answer Y if you have some other card made by Media Vision or Logitech since they are not - PAS16 compatible. + PAS16 compatible. Do NOT enable both CONFIG_SOUND_PAS and + CONFIG_SOUND_SB since the PAS modules include support for + Soundblaster. + If you compile the driver into the kernel, you have to add "pas2=,,, to the kernel command line. @@ -126,13 +128,7 @@ to be Sound Blaster-compatible. The PAS16 has 8-bit Soundblaster support, so you can answer Y here for it. - Please read the file Documentation/sound/Soundblaster. - - If you compile the driver into the kernel and don't want to use isapnp, - you have to add "sb=,,," to the kernel command line. - - You can say M here to compile this driver as a module; the module is - called sb.o. + Do not enable both this option and PAS16 above FM Synthesizer (YM3812/OPL-3) support CONFIG_SOUND_YM3812 @@ -149,7 +145,7 @@ If you compile your drivers into the kernel, you MUST configure OPL3 support as a module for PAS16 support to work properly. You can the
Re: test8-pre2 fs corruption?
On Mon, 4 Sep 2000, Bartlomiej Zolnierkiewicz wrote: > > On Mon, 4 Sep 2000, Rik van Riel wrote: > > On Mon, 4 Sep 2000, Paul Jakma wrote: > > > On Sun, 3 Sep 2000, Thomas Molina wrote: > > > > > > > Odd. I started seeing mailbox corruption the day before the first post > > > > showed up here. Since it was only one list (BUGTRAQ) and I'm still at > > > > > > weird. currently my pine crashes on me when i close my bugtraq > > > folder. > > > > Ohh, so I'm not the only one having trouble reading bugtraq > > lately? ;) > > > > I'm getting that same problem on 2.4.0-test8-pre1 (+vmpatch), btw. > > > > And vanilla 2.4.0-t8-p1, ugh. Readers of BUGTRAQ probably have already seen the message indicating some of us have been seeing library problems, not fs corruption. At least those of us with problems specific to mailing lists may not have been seeing the fs corruption. A message seems to implicate multi-line X-Keywords header lines. Following is an excerpt from BUGTRAQ: On Fri, Sep 01, 2000 at 07:53:22PM +0300, Juhapekka Tolvanen wrote: > It seems, that c-client libraries by University of Washington have > some bug(s), that makes some programs that depend upon those libraries > go crazy. AFAIK affected programs include at least Pine (read "pain"), > ipop3d and IMAPD. And those programs and libraries are commonly used in > Unixes. I don't know, if any patch, fix, work-around etc. exist. X-Keywords is processed in 2 functions: mail_filter() (in imap/src/c-client/mail.c) filters out X-Keywords line and seems to handle multi-line keywords correctly unix_parse() (in imap/src/osdep/unix/unix.c) probably doesn't handle multi-line keywords Different results (different header sizes) causes pine crash. The same may apply to X-UID, X-Status and Status header (I haven't test, so I'm not sure). imap uses the same c-client library, so the same condition may cause imap crash. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: test8-pre2 fs corruption?
On Sun, 3 Sep 2000, Mohammad A. Haque wrote: > Hello > > Alot of my mailboxes have become corrupt after trying test8-pre2. I'm > back down to test7 and everything seems to be working ok so far. I was > able to forcibly corrupt a couple of mailboxes by reading unread mail > from about a week or so ago and exiting. The mailbox would then be > corrupt from allowing me to only get to messages up until last week > after manually editing the mailbox to remove the garbage in the file. Odd. I started seeing mailbox corruption the day before the first post showed up here. Since it was only one list (BUGTRAQ) and I'm still at pre7, I've ascribed it to a problem with the sender. The corruption shows up as weird characters at the end of the file. I only mention it because of the odd time-coincident nature of the error. I don't suppose there is a connection? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Raid 1/upgrade to 2.2.16
On Tue, 29 Aug 2000, Alan Cox wrote: > > I can't tell you the redhat way of doing a kernel upgrade (things like > > this are one of the resons I don't use redhat) but if you are useing the > > Mostly > rpm -Uvh kernel-foo.i386.rpm > > the full details are in the support db One small nit to pick here. As is pointed out in the support db the -Uvh parameter works for kernel-header-foo and kernel-source-foo, but you want -ivh for the kernel-foo package. Doing an upgrade of a running kernel instead of an install can get you into nasty situations that can be hard to get out of. READ THE HOWTO - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
