Re: The latest Microsoft FUD. This time from BillG, himself.
On Wed, 20 Jun 2001, Alan Cox wrote: > > http://www.zdnet.com/zdnn/stories/news/0,4586,5092935,00.html > > > Of course the URL that goes with that is : > http://www.microsoft.com/windows2000/interix/features.asp > > Yes., Microsoft ship GNU C (quite legally) as part of their offerings... As well as: http://www.microsoft.com/presspass/press/2000/Apr00/WinUNIXPR.asp where they announce distributing ActiveState's Perl 5.6 as part of their toolset. (Which they funded the development of...) Seems they are willing to use Open Source if it suits their purposes... [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "All power is derived from the barrel of a gnu." - Mao Tse Stallman - 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: IP_ALIAS in 2.4.x gone?
I found the problem... IP_ALIAS is no longer needed in the config. I screwed up the init script configs for it so it did not work as expected. The documentation does not reflect that the alias behaviour is on by default. I will submit a patch for the docs that reflects this so others will not get confused by that. On Wed, 20 Jun 2001, Alan Olsen wrote: > > Has the IP_ALIAS functionality been replaced by something else in the > 2.4.x kernels? > > Documentation/networking/alias.txt seems to imply that it still does, but > the string IP_ALIAS does not exist anywhere else in the entire source > tree. (Unless you count the default configs for non-i86 architectures. > > There is a "virtual server" option in the kernel that ships with Redhat, > but I assume that this is a patch for something Redhat specific. (It is > not an option in 2.4.5, unless I am missing something.) > > How is binding multiple IPs to a single ethernet card *supposed* to be > handled under 2.4.x? If the IP_ALIAS option is no longer valid, then the > alias.txt doc should be changed to reflect the new option. > > Thanks! > > [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply > Alan Olsen| to my mail, just hit the ctrl, alt and del keys. > "All power is derived from the barrel of a gnu." - Mao Tse Stallman > > - > 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/ > [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "All power is derived from the barrel of a gnu." - Mao Tse Stallman - 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/
IP_ALIAS in 2.4.x gone?
Has the IP_ALIAS functionality been replaced by something else in the 2.4.x kernels? Documentation/networking/alias.txt seems to imply that it still does, but the string IP_ALIAS does not exist anywhere else in the entire source tree. (Unless you count the default configs for non-i86 architectures. There is a "virtual server" option in the kernel that ships with Redhat, but I assume that this is a patch for something Redhat specific. (It is not an option in 2.4.5, unless I am missing something.) How is binding multiple IPs to a single ethernet card *supposed* to be handled under 2.4.x? If the IP_ALIAS option is no longer valid, then the alias.txt doc should be changed to reflect the new option. Thanks! [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "All power is derived from the barrel of a gnu." - Mao Tse Stallman - 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/
IP_ALIAS in 2.4.x gone?
Has the IP_ALIAS functionality been replaced by something else in the 2.4.x kernels? Documentation/networking/alias.txt seems to imply that it still does, but the string IP_ALIAS does not exist anywhere else in the entire source tree. (Unless you count the default configs for non-i86 architectures. There is a virtual server option in the kernel that ships with Redhat, but I assume that this is a patch for something Redhat specific. (It is not an option in 2.4.5, unless I am missing something.) How is binding multiple IPs to a single ethernet card *supposed* to be handled under 2.4.x? If the IP_ALIAS option is no longer valid, then the alias.txt doc should be changed to reflect the new option. Thanks! [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. All power is derived from the barrel of a gnu. - Mao Tse Stallman - 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: IP_ALIAS in 2.4.x gone?
I found the problem... IP_ALIAS is no longer needed in the config. I screwed up the init script configs for it so it did not work as expected. The documentation does not reflect that the alias behaviour is on by default. I will submit a patch for the docs that reflects this so others will not get confused by that. On Wed, 20 Jun 2001, Alan Olsen wrote: Has the IP_ALIAS functionality been replaced by something else in the 2.4.x kernels? Documentation/networking/alias.txt seems to imply that it still does, but the string IP_ALIAS does not exist anywhere else in the entire source tree. (Unless you count the default configs for non-i86 architectures. There is a virtual server option in the kernel that ships with Redhat, but I assume that this is a patch for something Redhat specific. (It is not an option in 2.4.5, unless I am missing something.) How is binding multiple IPs to a single ethernet card *supposed* to be handled under 2.4.x? If the IP_ALIAS option is no longer valid, then the alias.txt doc should be changed to reflect the new option. Thanks! [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. All power is derived from the barrel of a gnu. - Mao Tse Stallman - 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/ [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. All power is derived from the barrel of a gnu. - Mao Tse Stallman - 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: The latest Microsoft FUD. This time from BillG, himself.
On Wed, 20 Jun 2001, Alan Cox wrote: http://www.zdnet.com/zdnn/stories/news/0,4586,5092935,00.html Of course the URL that goes with that is : http://www.microsoft.com/windows2000/interix/features.asp Yes., Microsoft ship GNU C (quite legally) as part of their offerings... As well as: http://www.microsoft.com/presspass/press/2000/Apr00/WinUNIXPR.asp where they announce distributing ActiveState's Perl 5.6 as part of their toolset. (Which they funded the development of...) Seems they are willing to use Open Source if it suits their purposes... [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. All power is derived from the barrel of a gnu. - Mao Tse Stallman - 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: obsolete code must die
On Wed, 13 Jun 2001, Daniel wrote: I agree that some clean up is needed. (The size of the kernel is getting HUGE. Back in the old days, we didn't have kernels larger than a few hundred kbytes. That is because we had to type in the kernel source from source written on papyrus.) > So without further ado here're the features I want to get rid of: > > i386, i486 > The Pentium processor has been around since 1995. Support for these older > processors should go so we can focus on optimizations for the pentium and > better processors. You are in a part of the world that can afford them. In Third World countries, however, Pentiums are not always the norm. You are cutting off a good chunk of the world here. > math-emu > If support for i386 and i486 is going away, then so should math emulation. > Every intel processor since the 486DX has an FPU unit built in. In fact > shouldn't FPU support be a userspace responsibility anyway? How does getting rid of math-emu effect compilation on other platforms? Not just Intel out there... > ISA bus, MCA bus, EISA bus > PCI is the defacto standard. Get rid of CONFIG_BLK_DEV_ISAPNP, > CONFIG_ISAPNP, etc This I strongly disagree with. There are alot of ISA cards still in use. (I have a USR 56k voice/fax modem that still works great. How many Sound Blaster 16 cards are still being used? Lots, i would guess.) It may not be pretty, but it is still widely used. (Even in the US.) > ISA, MCA, EISA device drivers > If support for the buses is gone, there's no point in supporting devices for > these buses. I am not certain if tis is a good idea, for the reason given above. (Not certain about MCA and EISA though.) > all code marked as CONFIG_OBSOLETE > Since we're cleaning house we may as well get rid of this stuff. I don't have an argument there, except when it has not been that way long. > MFM/RLL/XT/ESDI hard drive support > Does anyone still *have* an RLL drive that works? At the very least get rid > of the old driver (eg CONFIG_BLK_DEV_HD_ONLY, CONFIG_BLK_DEV_HD_IDE, > CONFIG_BLK_DEV_XD, CONFIG_BLK_DEV_PS2) I am not certain how much this stuff is still used outside the US. The XT driver still being around does surprise me though. (Will that even *work* on modern hardware? I didn't think you could get that card to work on a 386.) > parallel/serial/game ports > More controversial to remove this, since they are *still* in pretty wide > use -- but USB and IEEE 1394 are the way to go. No ifs ands or buts. This is BAD idea. This sort of joystick was produced until reciently. They are still in use. You will piss off a bunch of gamers this way. (Yanking a gamer's joystick is never a good idea.) > a.out > Who needs it anymore. I love ELF. How much legacy code is still out there? How much will still run on 2.4? I don't see this one as a problem, but I expect that there are some special cases that will keep it alive. > I really think doing a clean up is worthwhile. Maybe while looking for stuff > to clean up we'll even be able to better comment the existing code. Any > other features people would like to get rid of? Any comments or suggestions? > I'd love to start a good discussion about this going so please send me your > 2 cents. I would like to see a clean up of the documentation. (As well as new docs written.) Getting an updated list of all the parameters that can be passed to the kernel would be a nice start. (The current list looks pretty old.) I do agree that some parts need to be cut off from the main tree. Maybe this clean-up should be a part of 2.5? 2.7? 6.6.6? [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "All power is derived from the barrel of a gnu." - Mao Tse Stallman - 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: obsolete code must die
On Wed, 13 Jun 2001, Daniel wrote: I agree that some clean up is needed. (The size of the kernel is getting HUGE. Back in the old days, we didn't have kernels larger than a few hundred kbytes. That is because we had to type in the kernel source from source written on papyrus.) So without further ado here're the features I want to get rid of: i386, i486 The Pentium processor has been around since 1995. Support for these older processors should go so we can focus on optimizations for the pentium and better processors. You are in a part of the world that can afford them. In Third World countries, however, Pentiums are not always the norm. You are cutting off a good chunk of the world here. math-emu If support for i386 and i486 is going away, then so should math emulation. Every intel processor since the 486DX has an FPU unit built in. In fact shouldn't FPU support be a userspace responsibility anyway? How does getting rid of math-emu effect compilation on other platforms? Not just Intel out there... ISA bus, MCA bus, EISA bus PCI is the defacto standard. Get rid of CONFIG_BLK_DEV_ISAPNP, CONFIG_ISAPNP, etc This I strongly disagree with. There are alot of ISA cards still in use. (I have a USR 56k voice/fax modem that still works great. How many Sound Blaster 16 cards are still being used? Lots, i would guess.) It may not be pretty, but it is still widely used. (Even in the US.) ISA, MCA, EISA device drivers If support for the buses is gone, there's no point in supporting devices for these buses. I am not certain if tis is a good idea, for the reason given above. (Not certain about MCA and EISA though.) all code marked as CONFIG_OBSOLETE Since we're cleaning house we may as well get rid of this stuff. I don't have an argument there, except when it has not been that way long. MFM/RLL/XT/ESDI hard drive support Does anyone still *have* an RLL drive that works? At the very least get rid of the old driver (eg CONFIG_BLK_DEV_HD_ONLY, CONFIG_BLK_DEV_HD_IDE, CONFIG_BLK_DEV_XD, CONFIG_BLK_DEV_PS2) I am not certain how much this stuff is still used outside the US. The XT driver still being around does surprise me though. (Will that even *work* on modern hardware? I didn't think you could get that card to work on a 386.) parallel/serial/game ports More controversial to remove this, since they are *still* in pretty wide use -- but USB and IEEE 1394 are the way to go. No ifs ands or buts. This is BAD idea. This sort of joystick was produced until reciently. They are still in use. You will piss off a bunch of gamers this way. (Yanking a gamer's joystick is never a good idea.) a.out Who needs it anymore. I love ELF. How much legacy code is still out there? How much will still run on 2.4? I don't see this one as a problem, but I expect that there are some special cases that will keep it alive. I really think doing a clean up is worthwhile. Maybe while looking for stuff to clean up we'll even be able to better comment the existing code. Any other features people would like to get rid of? Any comments or suggestions? I'd love to start a good discussion about this going so please send me your 2 cents. I would like to see a clean up of the documentation. (As well as new docs written.) Getting an updated list of all the parameters that can be passed to the kernel would be a nice start. (The current list looks pretty old.) I do agree that some parts need to be cut off from the main tree. Maybe this clean-up should be a part of 2.5? 2.7? 6.6.6? [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. All power is derived from the barrel of a gnu. - Mao Tse Stallman - 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/
es1371 compile issue in 2.4.5-ac9
Try to reproduce one problem and find another... I rebuilt from clean source and patch for 2.4.5-ac9 and neglected to add in anything using the joystick. (Which I should have done since this thing has most of the games (I mean "X test utilities") on it.) This should be pretty straightforward to fix, if it has not been already... Chokes on link. .config attached. make[1]: Leaving directory `/usr/src/linux/arch/i386/lib' ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \ --start-group \ arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \ drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/char/agp/agp.o drivers/char/drm/drm.o drivers/ide/idedriver.o drivers/scsi/scsidrv.o drivers/cdrom/driver.o drivers/sound/sounddrivers.o drivers/pci/driver.o drivers/pcmcia/pcmcia.o drivers/pnp/pnp.o drivers/video/video.o \ net/network.o \ /usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a /usr/src/linux/arch/i386/lib/lib.a \ --end-group \ -o vmlinux drivers/sound/sounddrivers.o: In function `es1371_probe': drivers/sound/sounddrivers.o(.text+0x5e5d): undefined reference to `gameport_register_port' drivers/sound/sounddrivers.o: In function `es1371_remove': drivers/sound/sounddrivers.o(.text+0x5f71): undefined reference to `gameport_unregister_port' make: *** [vmlinux] Error 1 [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." # # Automatically generated by make menuconfig: don't edit # # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set CONFIG_M586TSC=y # CONFIG_M686 is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_TSC=y CONFIG_1GB=y # CONFIG_2GB is not set # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set # CONFIG_SMP is not set # # Loadable module support # CONFIG_MODULES=y # CONFIG_MODVERSIONS is not set CONFIG_KMOD=y # # General setup # CONFIG_NET=y 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_QUIRKS=y # CONFIG_PCI_OPTIMIZE is not set CONFIG_PCI_OLD_PROC=y # CONFIG_MCA is not set # CONFIG_VISWS is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # CONFIG_BINFMT_JAVA is not set # CONFIG_PARPORT is not set # CONFIG_APM is not set # # Plug and Play support # # CONFIG_PNP is not set # # Block devices # CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_IDE=y # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_BLK_DEV_IDESCSI is not set CONFIG_BLK_DEV_CMD640=y # CONFIG_BLK_DEV_CMD640_ENHANCED is not set CONFIG_BLK_DEV_RZ1000=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_IDEDMA=y # CONFIG_BLK_DEV_OFFBOARD is not set CONFIG_IDEDMA_AUTO=y # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_TRM290 is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_VIA82C586 is not set # CONFIG_BLK_DEV_CMD646 is not set # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_IDE_CHIPSETS is not set CONFIG_BLK_DEV_LOOP=m # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_MD is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_BLK_DEV_XD is not set # CONFIG_BLK_DEV_DAC960 is not set CONFIG_PARIDE_PARPORT=y # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_DEV_HD is not set # # Networking options # CONFIG_PACKET=y CONFIG_NETLINK=y CONFIG_RTNETLINK=y # CONFIG_NETLINK_DEV is not set CONFIG_FIREWALL=y CONFIG_FILTER=y 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_IP_FIREWALL=y # CONFIG_IP_FIREWALL_NETLINK is not set # CONFIG_IP_TRANSPARENT_PROXY is not set # CONFIG_IP_MASQUERADE is not set # CONFIG_IP_ROUTER is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set CONFIG_IP_ALIAS=y # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set # CONFIG_INET_RARP is not set CONFIG_SKB_LARGE=y # CONFIG_IPV6 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_BRIDGE is not set # CONFIG_LLC is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_NET_FASTROUTE is not set # CONFIG_NET_HW_FLOWCONTROL is not set # CONFIG_CPU_IS_SLOW is
Re: SCSI is as SCSI don't...
On Tue, 5 Jun 2001, Greg KH wrote: > On Tue, Jun 05, 2001 at 11:08:04PM -0700, Alan Olsen wrote: > > The basic effect is that the kernel will not load. Something breaks hard > > in it. > > Any clue on what the last thing printed to the kernel log is? > Hardware you have? > .config for the kernel? > > Come on Alan, I know you can give better bug reports than that :) it has been a long day... Actually it did not get much past the lilo prompt. I will add more debugging options and try again after I get more sleep. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: SCSI is as SCSI don't...
On Tue, 5 Jun 2001, Greg KH wrote: On Tue, Jun 05, 2001 at 11:08:04PM -0700, Alan Olsen wrote: The basic effect is that the kernel will not load. Something breaks hard in it. Any clue on what the last thing printed to the kernel log is? Hardware you have? .config for the kernel? Come on Alan, I know you can give better bug reports than that :) it has been a long day... Actually it did not get much past the lilo prompt. I will add more debugging options and try again after I get more sleep. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. In the future, everything will have its 15 minutes of blame. - 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/
es1371 compile issue in 2.4.5-ac9
Try to reproduce one problem and find another... I rebuilt from clean source and patch for 2.4.5-ac9 and neglected to add in anything using the joystick. (Which I should have done since this thing has most of the games (I mean X test utilities) on it.) This should be pretty straightforward to fix, if it has not been already... Chokes on link. .config attached. make[1]: Leaving directory `/usr/src/linux/arch/i386/lib' ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \ --start-group \ arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \ drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/char/agp/agp.o drivers/char/drm/drm.o drivers/ide/idedriver.o drivers/scsi/scsidrv.o drivers/cdrom/driver.o drivers/sound/sounddrivers.o drivers/pci/driver.o drivers/pcmcia/pcmcia.o drivers/pnp/pnp.o drivers/video/video.o \ net/network.o \ /usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a /usr/src/linux/arch/i386/lib/lib.a \ --end-group \ -o vmlinux drivers/sound/sounddrivers.o: In function `es1371_probe': drivers/sound/sounddrivers.o(.text+0x5e5d): undefined reference to `gameport_register_port' drivers/sound/sounddrivers.o: In function `es1371_remove': drivers/sound/sounddrivers.o(.text+0x5f71): undefined reference to `gameport_unregister_port' make: *** [vmlinux] Error 1 [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. In the future, everything will have its 15 minutes of blame. # # Automatically generated by make menuconfig: don't edit # # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set CONFIG_M586TSC=y # CONFIG_M686 is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_TSC=y CONFIG_1GB=y # CONFIG_2GB is not set # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set # CONFIG_SMP is not set # # Loadable module support # CONFIG_MODULES=y # CONFIG_MODVERSIONS is not set CONFIG_KMOD=y # # General setup # CONFIG_NET=y 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_QUIRKS=y # CONFIG_PCI_OPTIMIZE is not set CONFIG_PCI_OLD_PROC=y # CONFIG_MCA is not set # CONFIG_VISWS is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # CONFIG_BINFMT_JAVA is not set # CONFIG_PARPORT is not set # CONFIG_APM is not set # # Plug and Play support # # CONFIG_PNP is not set # # Block devices # CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_IDE=y # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_BLK_DEV_IDESCSI is not set CONFIG_BLK_DEV_CMD640=y # CONFIG_BLK_DEV_CMD640_ENHANCED is not set CONFIG_BLK_DEV_RZ1000=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_IDEDMA=y # CONFIG_BLK_DEV_OFFBOARD is not set CONFIG_IDEDMA_AUTO=y # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_TRM290 is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_VIA82C586 is not set # CONFIG_BLK_DEV_CMD646 is not set # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_IDE_CHIPSETS is not set CONFIG_BLK_DEV_LOOP=m # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_MD is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_BLK_DEV_XD is not set # CONFIG_BLK_DEV_DAC960 is not set CONFIG_PARIDE_PARPORT=y # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_DEV_HD is not set # # Networking options # CONFIG_PACKET=y CONFIG_NETLINK=y CONFIG_RTNETLINK=y # CONFIG_NETLINK_DEV is not set CONFIG_FIREWALL=y CONFIG_FILTER=y 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_IP_FIREWALL=y # CONFIG_IP_FIREWALL_NETLINK is not set # CONFIG_IP_TRANSPARENT_PROXY is not set # CONFIG_IP_MASQUERADE is not set # CONFIG_IP_ROUTER is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set CONFIG_IP_ALIAS=y # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set # CONFIG_INET_RARP is not set CONFIG_SKB_LARGE=y # CONFIG_IPV6 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_BRIDGE is not set # CONFIG_LLC is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_NET_FASTROUTE is not set # CONFIG_NET_HW_FLOWCONTROL is not set # CONFIG_CPU_IS_SLOW is not set # # QoS
Re: SCSI is as SCSI don't...
Forgot to list my working environment... Redhat 7.1 patched to pretty close to the latest. (As of a week ago or so.) P-III 600 with 256 megs of ram and lots of disk, so resource starvation is not an issue. (Unless something got REALLY big in the last few patches.) On Tue, 5 Jun 2001, Alan Olsen wrote: > I am trying to get 2.4.5 and/or 2.4.5-ac9 working. Both are choking on > compile with an odd error message or four... > > In file included from /usr/src/linux-2.4.5-ac9/include/linux/raid/md.h:50, > from ll_rw_blk.c:30: > /usr/src/linux-2.4.5-ac9/include/linux/raid/md_k.h: In function > `pers_to_level':/usr/src/linux-2.4.5-ac9/include/linux/raid/md_k.h:41: > warning: control reaches end of non-void function > > I am seeing similar messages in the AIC7xxx code. > > The basic effect is that the kernel will not load. Something breaks hard > in it. > > My C is pretty rusty. (Too much IS work as of late...) Does anyone know > what this message is and why it is occuring? > > I am currently using 2.4.4-ac11 and it does not have this problem. > > My reason for upgrading is that cdrecord gave me the following error, and > I was hoping that 2.4.5 would have fixed it... > > Starting new track at sector: 0 > CDB: 2A 00 00 00 9E FF 00 00 1F 80 > cdrecord: Input/output error. write_teac_g1: scsi sendcmd: retryable error > Sense Bytes: 70 00 0B 00 00 00 00 0A 00 00 00 01 BA 00 00 00 > status: 0x2 (CHECK CONDITION) > Sense Key: 0xB Aborted Command, Segment 0 > Sense Code: 0xBA Qual 0x00 (no write data - buffer empty) Fru 0x0 > Sense flags: Blk 0 (not valid) > > cdrecord: Input/output error. write_teac_g1: scsi sendcmd: retryable error > write track data: error after 83359744 bytes > status: 0x2 (CHECK CONDITION) > Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 > WARNING: adding dummy block to close track. > CDB: 2A 00 00 00 9E FF 00 00 01 00 > Sense Bytes: 70 00 0B 00 00 00 00 0A 00 00 00 01 BA 00 00 00 > Sense Key: 0xB Aborted Command, Segment 0 > Sense Code: 0xBA Qual 0x00 (no write data - buffer empty) Fru 0x0 > Sense flags: Blk 0 (not valid) > > Ideas...? (At least it give me time to finish Linus's autobiography while > I am rebuilding things, but I am quickly running out of book. ]:> ) > > [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply > Alan Olsen| to my mail, just hit the ctrl, alt and del keys. > "In the future, everything will have its 15 minutes of blame." > > - > 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/ > [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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/
SCSI is as SCSI don't...
I am trying to get 2.4.5 and/or 2.4.5-ac9 working. Both are choking on compile with an odd error message or four... In file included from /usr/src/linux-2.4.5-ac9/include/linux/raid/md.h:50, from ll_rw_blk.c:30: /usr/src/linux-2.4.5-ac9/include/linux/raid/md_k.h: In function `pers_to_level':/usr/src/linux-2.4.5-ac9/include/linux/raid/md_k.h:41: warning: control reaches end of non-void function I am seeing similar messages in the AIC7xxx code. The basic effect is that the kernel will not load. Something breaks hard in it. My C is pretty rusty. (Too much IS work as of late...) Does anyone know what this message is and why it is occuring? I am currently using 2.4.4-ac11 and it does not have this problem. My reason for upgrading is that cdrecord gave me the following error, and I was hoping that 2.4.5 would have fixed it... Starting new track at sector: 0 CDB: 2A 00 00 00 9E FF 00 00 1F 80 cdrecord: Input/output error. write_teac_g1: scsi sendcmd: retryable error Sense Bytes: 70 00 0B 00 00 00 00 0A 00 00 00 01 BA 00 00 00 status: 0x2 (CHECK CONDITION) Sense Key: 0xB Aborted Command, Segment 0 Sense Code: 0xBA Qual 0x00 (no write data - buffer empty) Fru 0x0 Sense flags: Blk 0 (not valid) cdrecord: Input/output error. write_teac_g1: scsi sendcmd: retryable error write track data: error after 83359744 bytes status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 WARNING: adding dummy block to close track. CDB: 2A 00 00 00 9E FF 00 00 01 00 Sense Bytes: 70 00 0B 00 00 00 00 0A 00 00 00 01 BA 00 00 00 Sense Key: 0xB Aborted Command, Segment 0 Sense Code: 0xBA Qual 0x00 (no write data - buffer empty) Fru 0x0 Sense flags: Blk 0 (not valid) Ideas...? (At least it give me time to finish Linus's autobiography while I am rebuilding things, but I am quickly running out of book. ]:> ) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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/
SCSI is as SCSI don't...
I am trying to get 2.4.5 and/or 2.4.5-ac9 working. Both are choking on compile with an odd error message or four... In file included from /usr/src/linux-2.4.5-ac9/include/linux/raid/md.h:50, from ll_rw_blk.c:30: /usr/src/linux-2.4.5-ac9/include/linux/raid/md_k.h: In function `pers_to_level':/usr/src/linux-2.4.5-ac9/include/linux/raid/md_k.h:41: warning: control reaches end of non-void function I am seeing similar messages in the AIC7xxx code. The basic effect is that the kernel will not load. Something breaks hard in it. My C is pretty rusty. (Too much IS work as of late...) Does anyone know what this message is and why it is occuring? I am currently using 2.4.4-ac11 and it does not have this problem. My reason for upgrading is that cdrecord gave me the following error, and I was hoping that 2.4.5 would have fixed it... Starting new track at sector: 0 CDB: 2A 00 00 00 9E FF 00 00 1F 80 cdrecord: Input/output error. write_teac_g1: scsi sendcmd: retryable error Sense Bytes: 70 00 0B 00 00 00 00 0A 00 00 00 01 BA 00 00 00 status: 0x2 (CHECK CONDITION) Sense Key: 0xB Aborted Command, Segment 0 Sense Code: 0xBA Qual 0x00 (no write data - buffer empty) Fru 0x0 Sense flags: Blk 0 (not valid) cdrecord: Input/output error. write_teac_g1: scsi sendcmd: retryable error write track data: error after 83359744 bytes status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 WARNING: adding dummy block to close track. CDB: 2A 00 00 00 9E FF 00 00 01 00 Sense Bytes: 70 00 0B 00 00 00 00 0A 00 00 00 01 BA 00 00 00 Sense Key: 0xB Aborted Command, Segment 0 Sense Code: 0xBA Qual 0x00 (no write data - buffer empty) Fru 0x0 Sense flags: Blk 0 (not valid) Ideas...? (At least it give me time to finish Linus's autobiography while I am rebuilding things, but I am quickly running out of book. ]: ) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. In the future, everything will have its 15 minutes of blame. - 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: SCSI is as SCSI don't...
Forgot to list my working environment... Redhat 7.1 patched to pretty close to the latest. (As of a week ago or so.) P-III 600 with 256 megs of ram and lots of disk, so resource starvation is not an issue. (Unless something got REALLY big in the last few patches.) On Tue, 5 Jun 2001, Alan Olsen wrote: I am trying to get 2.4.5 and/or 2.4.5-ac9 working. Both are choking on compile with an odd error message or four... In file included from /usr/src/linux-2.4.5-ac9/include/linux/raid/md.h:50, from ll_rw_blk.c:30: /usr/src/linux-2.4.5-ac9/include/linux/raid/md_k.h: In function `pers_to_level':/usr/src/linux-2.4.5-ac9/include/linux/raid/md_k.h:41: warning: control reaches end of non-void function I am seeing similar messages in the AIC7xxx code. The basic effect is that the kernel will not load. Something breaks hard in it. My C is pretty rusty. (Too much IS work as of late...) Does anyone know what this message is and why it is occuring? I am currently using 2.4.4-ac11 and it does not have this problem. My reason for upgrading is that cdrecord gave me the following error, and I was hoping that 2.4.5 would have fixed it... Starting new track at sector: 0 CDB: 2A 00 00 00 9E FF 00 00 1F 80 cdrecord: Input/output error. write_teac_g1: scsi sendcmd: retryable error Sense Bytes: 70 00 0B 00 00 00 00 0A 00 00 00 01 BA 00 00 00 status: 0x2 (CHECK CONDITION) Sense Key: 0xB Aborted Command, Segment 0 Sense Code: 0xBA Qual 0x00 (no write data - buffer empty) Fru 0x0 Sense flags: Blk 0 (not valid) cdrecord: Input/output error. write_teac_g1: scsi sendcmd: retryable error write track data: error after 83359744 bytes status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 WARNING: adding dummy block to close track. CDB: 2A 00 00 00 9E FF 00 00 01 00 Sense Bytes: 70 00 0B 00 00 00 00 0A 00 00 00 01 BA 00 00 00 Sense Key: 0xB Aborted Command, Segment 0 Sense Code: 0xBA Qual 0x00 (no write data - buffer empty) Fru 0x0 Sense flags: Blk 0 (not valid) Ideas...? (At least it give me time to finish Linus's autobiography while I am rebuilding things, but I am quickly running out of book. ]: ) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. In the future, everything will have its 15 minutes of blame. - 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/ [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. In the future, everything will have its 15 minutes of blame. - 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: Kernel Error Message
I am getting the same message with kernel 2.2.19 on a Vaio 505VE. (Celeron 333 with 128 megs of memory.) I usually see the message when copying large quantites from the PCMCIA CD-ROM to the hard drive. On Sun, 22 Apr 2001, Andreas Neidhardt wrote: > Hello from Germany, > > I have trouble with a 2.2.18 kernel on a Gigabyte GA 5AX Rev. 5.2 > Mainboard. > I have a lot of entrys in /var/log/messages like this: > > kernel: probable hardware bug: clock timer configuration lost - probably > a VIA686a. > horst kernel: probable hardware bug: restoring chip configuration. > > The Mainboard has definitely not a VIA686a. It is a Acer M1541 and M1543 > Chipset ( Aladin V) with a Intel Pentium 200 MMX CPU. > > My Linux Computer: > > GA 5AX Rev. 5.2 > 128 MB SDRAM > Matrox Mystique PCI 2 MB Graphics Adapter > 3Com Fast EtherLink XL 3C905B-COMBO NIC > Maxtor 20 GB IDE HDD UDMA 100 > Fritz PCI ISDN Card > TEKRAM SCSI II Controller DC 390 (no SCSI Devices connected) > > cat /proc/pci => > > PCI devices found: > Bus 0, device 0, function 0: > Host bridge: Acer Labs M1541 Aladdin V (rev 4). > Slow devsel. Master Capable. Latency=32. > Non-prefetchable 32 bit memory at 0xe000 [0xe000]. > Bus 0, device 1, function 0: > PCI bridge: Acer Labs M5243 AGP (rev 4). > Slow devsel. Master Capable. Latency=32. Min Gnt=4. > Bus 0, device 7, function 0: > ISA bridge: Acer Labs M1533 Aladdin IV (rev 195). > Medium devsel. Master Capable. No bursts. > Bus 0, device 8, function 0: > VGA compatible controller: Matrox Mystique (rev 2). > Medium devsel. Fast back-to-back capable. IRQ 11. Master > Capable. Late > ncy=32. > Non-prefetchable 32 bit memory at 0xe100 [0xe100]. > Prefetchable 32 bit memory at 0xe200 [0xe208]. > Non-prefetchable 32 bit memory at 0xe300 [0xe300]. > Bus 0, device 10, function 0: > Ethernet controller: 3Com Unknown device (rev 0). > Vendor id=10b7. Device id=9058. > Medium devsel. IRQ 5. Master Capable. Latency=32. Min > Gnt=10.Max Lat=1 > 0. > I/O at 0xe000 [0xe001]. > Non-prefetchable 32 bit memory at 0xe600 [0xe600]. > Bus 0, device 11, function 0: > Non-VGA device: AMD 53C974 (rev 16). > Medium devsel. IRQ 3. Master Capable. Latency=32. Min > Gnt=4.Max Lat=40 > . > I/O at 0xe400 [0xe401]. > Bus 0, device 12, function 0: > Network controller: AVM A1 (Fritz) (rev 2). > Medium devsel. Fast back-to-back capable. IRQ 11. > Non-prefetchable 32 bit memory at 0xe6002000 [0xe6002000]. > I/O at 0xe800 [0xe801]. > Bus 0, device 15, function 0: > IDE interface: Acer Labs M5229 TXpro (rev 194). > Medium devsel. Fast back-to-back capable. Master Capable. > Latency=32. > Min Gnt=2.Max Lat=4. > I/O at 0xf000 [0xf001]. > > > > > > > > best regards > > andreas > > - > 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/ > [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Kernel Error Message
I am getting the same message with kernel 2.2.19 on a Vaio 505VE. (Celeron 333 with 128 megs of memory.) I usually see the message when copying large quantites from the PCMCIA CD-ROM to the hard drive. On Sun, 22 Apr 2001, Andreas Neidhardt wrote: Hello from Germany, I have trouble with a 2.2.18 kernel on a Gigabyte GA 5AX Rev. 5.2 Mainboard. I have a lot of entrys in /var/log/messages like this: kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a. horst kernel: probable hardware bug: restoring chip configuration. The Mainboard has definitely not a VIA686a. It is a Acer M1541 and M1543 Chipset ( Aladin V) with a Intel Pentium 200 MMX CPU. My Linux Computer: GA 5AX Rev. 5.2 128 MB SDRAM Matrox Mystique PCI 2 MB Graphics Adapter 3Com Fast EtherLink XL 3C905B-COMBO NIC Maxtor 20 GB IDE HDD UDMA 100 Fritz PCI ISDN Card TEKRAM SCSI II Controller DC 390 (no SCSI Devices connected) cat /proc/pci = PCI devices found: Bus 0, device 0, function 0: Host bridge: Acer Labs M1541 Aladdin V (rev 4). Slow devsel. Master Capable. Latency=32. Non-prefetchable 32 bit memory at 0xe000 [0xe000]. Bus 0, device 1, function 0: PCI bridge: Acer Labs M5243 AGP (rev 4). Slow devsel. Master Capable. Latency=32. Min Gnt=4. Bus 0, device 7, function 0: ISA bridge: Acer Labs M1533 Aladdin IV (rev 195). Medium devsel. Master Capable. No bursts. Bus 0, device 8, function 0: VGA compatible controller: Matrox Mystique (rev 2). Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Late ncy=32. Non-prefetchable 32 bit memory at 0xe100 [0xe100]. Prefetchable 32 bit memory at 0xe200 [0xe208]. Non-prefetchable 32 bit memory at 0xe300 [0xe300]. Bus 0, device 10, function 0: Ethernet controller: 3Com Unknown device (rev 0). Vendor id=10b7. Device id=9058. Medium devsel. IRQ 5. Master Capable. Latency=32. Min Gnt=10.Max Lat=1 0. I/O at 0xe000 [0xe001]. Non-prefetchable 32 bit memory at 0xe600 [0xe600]. Bus 0, device 11, function 0: Non-VGA device: AMD 53C974 (rev 16). Medium devsel. IRQ 3. Master Capable. Latency=32. Min Gnt=4.Max Lat=40 . I/O at 0xe400 [0xe401]. Bus 0, device 12, function 0: Network controller: AVM A1 (Fritz) (rev 2). Medium devsel. Fast back-to-back capable. IRQ 11. Non-prefetchable 32 bit memory at 0xe6002000 [0xe6002000]. I/O at 0xe800 [0xe801]. Bus 0, device 15, function 0: IDE interface: Acer Labs M5229 TXpro (rev 194). Medium devsel. Fast back-to-back capable. Master Capable. Latency=32. Min Gnt=2.Max Lat=4. I/O at 0xf000 [0xf001]. best regards andreas - 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/ [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: just a note
On Thu, 12 Apr 2001, Jan Dvorak wrote: > Hi, > > just a note: > > there are 66 Alan Coxes in net/ipv4/tcp.c in kernel 2.4.3: > > [johnydog@napalm ipv4]# cat ./tcp.c | grep "Alan Cox" -c > 66 > > do you bet that there will be 666 of them in 2.5.3/2.6.3 kernel ? > > :) I guess the devil is in the details... [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: just a note
On Thu, 12 Apr 2001, Jan Dvorak wrote: Hi, just a note: there are 66 Alan Coxes in net/ipv4/tcp.c in kernel 2.4.3: [johnydog@napalm ipv4]# cat ./tcp.c | grep "Alan Cox" -c 66 do you bet that there will be 666 of them in 2.5.3/2.6.3 kernel ? :) I guess the devil is in the details... [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: How to compile linux 0.0.0.1?
On Sat, 31 Mar 2001, Dr S.M. Huen wrote: > On Fri, 30 Mar 2001, Alan Olsen wrote: > > > Yeah, but then you have to find the buffalo and that gets hard. (Actually > > Linus used a carabou, but those are even harder to find...) > > > I thought he used GNU? :-) It was out of bullocks. ]:> [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: How to compile linux 0.0.0.1?
On Fri, 30 Mar 2001, David Relson wrote: > At 03:06 PM 3/30/01, Alan Olsen wrote: > >On Fri, 30 Mar 2001, Bruno Avila wrote: > > > > >I can't find this anywhere. What is the version of the tools to > > > compile linux kernel 0.0.0.1 (../Historic)? And where can i find them? > > > >Well, first you have to find a good source of obsidean, a couple of sharp > >rocks, and some flint... > > I have a friend who's a flintknapper. He's been doing it for decades and > does good work. I'm sure he could set you up with raw materials or with > finished products, i.e. arrowheads, knife blades, etc. Yeah, but then you have to find the buffalo and that gets hard. (Actually Linus used a carabou, but those are even harder to find...) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Matrox G400 Dualhead
On Fri, 30 Mar 2001, mythos wrote: > Does anyone know why fualhead is not working anymore? > I just get a screen with rubbish on the second head. > Also when kernel loads and and registers fb1 I lose signal > on the second head. Probably a question for the xpert list ([EMAIL PROTECTED])... What kernel version are you using? Kernel compile options? Version of XFree86? Have to looked for error messages in /var/log/XFree86.0.log? [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Matrox G400 Dualhead
On Fri, 30 Mar 2001, mythos wrote: Does anyone know why fualhead is not working anymore? I just get a screen with rubbish on the second head. Also when kernel loads and and registers fb1 I lose signal on the second head. Probably a question for the xpert list ([EMAIL PROTECTED])... What kernel version are you using? Kernel compile options? Version of XFree86? Have to looked for error messages in /var/log/XFree86.0.log? [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: How to compile linux 0.0.0.1?
On Fri, 30 Mar 2001, David Relson wrote: At 03:06 PM 3/30/01, Alan Olsen wrote: On Fri, 30 Mar 2001, Bruno Avila wrote: I can't find this anywhere. What is the version of the tools to compile linux kernel 0.0.0.1 (../Historic)? And where can i find them? Well, first you have to find a good source of obsidean, a couple of sharp rocks, and some flint... I have a friend who's a flintknapper. He's been doing it for decades and does good work. I'm sure he could set you up with raw materials or with finished products, i.e. arrowheads, knife blades, etc. Yeah, but then you have to find the buffalo and that gets hard. (Actually Linus used a carabou, but those are even harder to find...) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: How to compile linux 0.0.0.1?
On Sat, 31 Mar 2001, Dr S.M. Huen wrote: On Fri, 30 Mar 2001, Alan Olsen wrote: Yeah, but then you have to find the buffalo and that gets hard. (Actually Linus used a carabou, but those are even harder to find...) I thought he used GNU? :-) It was out of bullocks. ]: [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Where's Alan?
On Thu, 22 Mar 2001, Danny ter Haar wrote: > alterity <[EMAIL PROTECTED]> wrote: > >Haven't seen a post for sometime from the usually prolific Mr Cox. > >What's the gossip? > > Don't worry, missed him as well, but he's been posting > comments since yesterday. His personal webpage hasn't > been updated since 13th of this month though... He found out what happens when you mix Penguin bars and Penguin Mints and he has been in detox since. ];> [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Where's Alan?
On Thu, 22 Mar 2001, Danny ter Haar wrote: alterity [EMAIL PROTECTED] wrote: Haven't seen a post for sometime from the usually prolific Mr Cox. What's the gossip? Don't worry, missed him as well, but he's been posting comments since yesterday. His personal webpage hasn't been updated since 13th of this month though... He found out what happens when you mix Penguin bars and Penguin Mints and he has been in detox since. ]; [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: mysterious card
On Wed, 21 Mar 2001, Heusden, Folkert van wrote: > Hi, > > I have this mysterious 8 bit ISA card with nothing more then 2 smb-mounted > ic's > and a button. It seems to be something that should force a system memory > dump. > I think I can handle the code-writing, but since there's no documentation I > have > to find out how things are working. > Ok, the question is: does anyone know a place on the web where I can find > specifications of ISA-slots? I need to know what is supposed to be connected > to > the pins (1, 2, 6, etc.) It is supposed to do that! That sounds like the card that came with an old DOS debugger. The old 8088 PCs did not have a reset switch. This was so you could do hardware breaks when the whole system was locked up. I have one of those lying around somewhere... [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: mysterious card
On Wed, 21 Mar 2001, Heusden, Folkert van wrote: Hi, I have this mysterious 8 bit ISA card with nothing more then 2 smb-mounted ic's and a button. It seems to be something that should force a system memory dump. I think I can handle the code-writing, but since there's no documentation I have to find out how things are working. Ok, the question is: does anyone know a place on the web where I can find specifications of ISA-slots? I need to know what is supposed to be connected to the pins (1, 2, 6, etc.) It is supposed to do that! That sounds like the card that came with an old DOS debugger. The old 8088 PCs did not have a reset switch. This was so you could do hardware breaks when the whole system was locked up. I have one of those lying around somewhere... [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Alert on LAN for Linux?
Alert on LAN makes the system up from power management type sleep when there are packets to be processed. Why you would ever have sleep mode on a server is beyond me. To get wake on lan to work you will probably need the drivers from Intel. They are supposed to be freely available on their site. On Tue, 13 Mar 2001, Terje Malmedal wrote: > > Alert on LAN seems to have some useful functionality, if I understand > things correctly they have enhanced Wake-on-LAN to allow you to do > things like reset the machine, update the BIOS and such by sending > magic packets which are interpreted by the network card. Or maybe I am > reading too much into this: > > http://www.pc.ibm.com/us/desktop/alertonlan/ > > Anyway, my eepro100 cards say they are Alert on LAN capable, it would > be very useful to be able to use this reboot a Linux box remotely: > > 02:09.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 08) > > Subsystem: Intel Corporation EtherExpress PRO/100+ Management Adapter with >Alert On LAN* > Flags: bus master, medium devsel, latency 66, IRQ 11 > Memory at 4020 (32-bit, non-prefetchable) [size=4K] > I/O ports at 1400 [size=64] > Memory at 4010 (32-bit, non-prefetchable) [size=1M] > Expansion ROM at [disabled] [size=1M] > Capabilities: [dc] Power Management version 2 > > Does anybody know anything about Alert on LAN and whether it does what > I think it does? > > -- > - Terje > [EMAIL PROTECTED] > - > 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/ > [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Alert on LAN for Linux?
Alert on LAN makes the system up from power management type sleep when there are packets to be processed. Why you would ever have sleep mode on a server is beyond me. To get wake on lan to work you will probably need the drivers from Intel. They are supposed to be freely available on their site. On Tue, 13 Mar 2001, Terje Malmedal wrote: Alert on LAN seems to have some useful functionality, if I understand things correctly they have enhanced Wake-on-LAN to allow you to do things like reset the machine, update the BIOS and such by sending magic packets which are interpreted by the network card. Or maybe I am reading too much into this: http://www.pc.ibm.com/us/desktop/alertonlan/ Anyway, my eepro100 cards say they are Alert on LAN capable, it would be very useful to be able to use this reboot a Linux box remotely: 02:09.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 08) Subsystem: Intel Corporation EtherExpress PRO/100+ Management Adapter with Alert On LAN* Flags: bus master, medium devsel, latency 66, IRQ 11 Memory at 4020 (32-bit, non-prefetchable) [size=4K] I/O ports at 1400 [size=64] Memory at 4010 (32-bit, non-prefetchable) [size=1M] Expansion ROM at unassigned [disabled] [size=1M] Capabilities: [dc] Power Management version 2 Does anybody know anything about Alert on LAN and whether it does what I think it does? -- - Terje [EMAIL PROTECTED] - 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/ [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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/
OT: UCITA in Oregon
Sorry for the off-topic message, but this will be of interest to some here. There are a couple of bills being proposed in the Oregon legislature. One to stop UCITA and one to adopt it. (For those of you not familiar with UCITA, it is a nasty little provision being pushed that would make click-thru licences and all the other variants binding, as well as outlawing reverse engineering and other things.) More info on it can be found at: http://www.ieee.org/organizations/pubs/newsletters/npss/june2000/position.ht m and http://www.ieeeusa.org/forum/grassroots/ucita/ It turns out the person who has sponsored the bill to enact UCITA into law is the head of the Judiciary committee, so this could get interesting. If you are interested in testifying against UCITA contact Damon Elder at [EMAIL PROTECTED] He is the intern for Representative Phil Barnhart. Thanks! --- | Terrorists - The Boogiemen for a new Millennium. | |"The moral PGP Diffie taught Zimmermann unites all| Disclaimer: | | mankind free in one-key-steganography-privacy!" | Ignore the man | | | behind the keyboard.| | http://www.ctrl-alt-del.com/~alan/ |[EMAIL PROTECTED]| - 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: Linux stifles innovation...
On Sat, 17 Feb 2001, Dennis wrote: > At 07:01 PM 02/16/2001, Alan Olsen wrote: > >On Fri, 16 Feb 2001, Dennis wrote: > > > > > There is much truth to the concept, although Microsoft should not be ones > > > to comment on it as such. > > > >What truth? I have seen more "innovation" in the Open Source movement > >than I ever have in my 18+ years of being a professional programmer. > > You are confusing "progress" with "innovation". If there is only 1 choice, > thats not innovation. Expanding on a bad idea, or even a good one, is not > innovation. "You keep using that word. i don't think it means what you think it means." [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Linux stifles innovation...
On Sat, 17 Feb 2001, Dennis wrote: At 07:01 PM 02/16/2001, Alan Olsen wrote: On Fri, 16 Feb 2001, Dennis wrote: There is much truth to the concept, although Microsoft should not be ones to comment on it as such. What truth? I have seen more "innovation" in the Open Source movement than I ever have in my 18+ years of being a professional programmer. You are confusing "progress" with "innovation". If there is only 1 choice, thats not innovation. Expanding on a bad idea, or even a good one, is not innovation. "You keep using that word. i don't think it means what you think it means." [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Linux stifles innovation...
y do, we will just blame Microsoft". I understand your desire to make money off what you do for a living. I do object to you taring what I do as somehow damaging to the software industry as a whole. (Especially since the closed source software industry has been poaching off the open source community for years. Microsoft seeking enlightenment with WinXP is only a minor example.) I don't see how hiding how something works adds value to the process. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Linux stifles innovation...
On Thu, 15 Feb 2001, David D.W. Downey wrote: > Seriously though folks, look at who's doing this! > > They've already tried once to sue 'Linux', were told they couldn't because > Linux is a non-entity (or at least one that they can not effectively sue > due to the classification Linux holds), and now they can't use their > second favorite tactic for stifling NON-M$ product lines. > > How? They can't BUY the linux code base OR any GPL's software to the point > that they can bury it by buying and freezing the code from public use. > > We sort HAD to expect something like THIS to come. Though what DOES > concern me is how effective this current ploy may be if they get ANY sort > of backing from the government. (I doubt they will, but What If?) I expect the next thing that will happen is that they will get patents on key portions of their protocols and then start enforcing them. With the various IP laws that have been passed in the last few years in the US (and through WIPO) they will have a large brick to try and hit us with. (IMHO these laws pretty much allow large entities to buy their markets and are the biggest threat to innovation out there.) > Let's hope EFF and FSF stay on their toes for this one. M$ doesn't have to > win to really wipe our nose in stuff. They got the cash whereas we don't. > ALTHOUGH, spending money to fight an idea or concept has never proven > successful. And since the RESULTS of that idea or concept (in this case > source code) are not suable AFAIK. So we got the upper hand there. Actually I am sending copies of his rant out to all of my friends who still use Microsoft products. If that is the attitude they have towards their customers and the development community then it is time to get away while you still can. Of course, the reason I moved over all my development to Linux in the first place what that I did not have to worry about being screwed over by a "corporate strategy" or have the license terms changed on the next release or have to pay for something over and over again in the vain attempt to get something to work. With Linux I can read the source. There are no hidden interfaces. No mystical archane knowledge that you have to pay the company to learn get the job done. It is all there and it all works. (Or if it does not, then the tools exist to make it work.) I wonder what kind of law they will try to push to outlaw Open Source? If this is his idea of "The American Way" then he needs to take a basic civics course. He obviously slept through the last one. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Linux stifles innovation...
On Thu, 15 Feb 2001, David D.W. Downey wrote: Seriously though folks, look at who's doing this! They've already tried once to sue 'Linux', were told they couldn't because Linux is a non-entity (or at least one that they can not effectively sue due to the classification Linux holds), and now they can't use their second favorite tactic for stifling NON-M$ product lines. How? They can't BUY the linux code base OR any GPL's software to the point that they can bury it by buying and freezing the code from public use. We sort HAD to expect something like THIS to come. Though what DOES concern me is how effective this current ploy may be if they get ANY sort of backing from the government. (I doubt they will, but What If?) I expect the next thing that will happen is that they will get patents on key portions of their protocols and then start enforcing them. With the various IP laws that have been passed in the last few years in the US (and through WIPO) they will have a large brick to try and hit us with. (IMHO these laws pretty much allow large entities to buy their markets and are the biggest threat to innovation out there.) Let's hope EFF and FSF stay on their toes for this one. M$ doesn't have to win to really wipe our nose in stuff. They got the cash whereas we don't. ALTHOUGH, spending money to fight an idea or concept has never proven successful. And since the RESULTS of that idea or concept (in this case source code) are not suable AFAIK. So we got the upper hand there. Actually I am sending copies of his rant out to all of my friends who still use Microsoft products. If that is the attitude they have towards their customers and the development community then it is time to get away while you still can. Of course, the reason I moved over all my development to Linux in the first place what that I did not have to worry about being screwed over by a "corporate strategy" or have the license terms changed on the next release or have to pay for something over and over again in the vain attempt to get something to work. With Linux I can read the source. There are no hidden interfaces. No mystical archane knowledge that you have to pay the company to learn get the job done. It is all there and it all works. (Or if it does not, then the tools exist to make it work.) I wonder what kind of law they will try to push to outlaw Open Source? If this is his idea of "The American Way" then he needs to take a basic civics course. He obviously slept through the last one. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Slowing down CDROM drives (was: Re: ATAPI CDRW which doesn'twork)
Sorry. it was late when I answered that. (Either that or no ocffe, not certain which.) On Sun, 11 Feb 2001, Jens Axboe wrote: > On Sun, Feb 11 2001, Alan Olsen wrote: > > > It's no news that vendors only implement what they want to. New > > > cd-r/w and dvd drives are not required to implement this command, > > > so it may not work there either. > > > > Take a look at the code for cdparanoia or one of the other MP3 ripping > > programms. Slowing down the drive is a standard feature for that type of > > program. (Reduces errors when pulling audio tracks off the disc.) > > One would think that you have taken a look at the cdparanoia > source before posting something like this. Guess what it does to > control speed? Reread my message, you totally missed the point. > > -- > Jens Axboe > > [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Slowing down CDROM drives (was: Re: ATAPI CDRW which doesn'twork)
On Sun, 11 Feb 2001, Jens Axboe wrote: > On Sat, Feb 10 2001, Pavel Machek wrote: > > > ioctl(cd_fd, CDROM_SELECT_SPEED, speed); > > > > Does this actually work? I helped my friend with partly broken cdrom > > (worked only at low speeds) and it did not have much effect. It did > > not make my cdrom quiet, either, AFAI can remember. > > It's no news that vendors only implement what they want to. New > cd-r/w and dvd drives are not required to implement this command, > so it may not work there either. Take a look at the code for cdparanoia or one of the other MP3 ripping programms. Slowing down the drive is a standard feature for that type of program. (Reduces errors when pulling audio tracks off the disc.) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Slowing down CDROM drives (was: Re: ATAPI CDRW which doesn'twork)
On Sun, 11 Feb 2001, Jens Axboe wrote: On Sat, Feb 10 2001, Pavel Machek wrote: ioctl(cd_fd, CDROM_SELECT_SPEED, speed); Does this actually work? I helped my friend with partly broken cdrom (worked only at low speeds) and it did not have much effect. It did not make my cdrom quiet, either, AFAI can remember. It's no news that vendors only implement what they want to. New cd-r/w and dvd drives are not required to implement this command, so it may not work there either. Take a look at the code for cdparanoia or one of the other MP3 ripping programms. Slowing down the drive is a standard feature for that type of program. (Reduces errors when pulling audio tracks off the disc.) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: [OT] Re: 2.4.x, drm, g400 and pci_set_master
On Fri, 9 Feb 2001, David Woodhouse wrote: > [EMAIL PROTECTED] said: > > If open source people knew how it worked they might do horrible evil > > things like TV-out with the macrovision turned off. Thats basically > > the root of all this - yet again its the US movie industry > > Er... have you tried recording from the G400 TV out with matroxfb? > > Try it. You might like it. Just because something is pointless does not mean that they are not going to attempt to ram it down out throats. But I could rant on that all day... [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: [OT] Re: 2.4.x, drm, g400 and pci_set_master
On Fri, 9 Feb 2001, David Woodhouse wrote: [EMAIL PROTECTED] said: If open source people knew how it worked they might do horrible evil things like TV-out with the macrovision turned off. Thats basically the root of all this - yet again its the US movie industry Er... have you tried recording from the G400 TV out with matroxfb? Try it. You might like it. Just because something is pointless does not mean that they are not going to attempt to ram it down out throats. But I could rant on that all day... [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: [OT] Re: 2.4.x, drm, g400 and pci_set_master
On Thu, 8 Feb 2001, Petr Vandrovec wrote: > On 8 Feb 01 at 13:14, Alex Deucher wrote: > > Jeff Hartmann wrote: > > > Petr Vandrovec wrote: > > > > It does not use dynamic DMA mapping, because it doesn't do PCI DMA at > > > all. It uses AGP DMA. Actually, it shouldn't be too hard to get it to > > > work on the Alpha (just a few 32/64 bit issues probably.) Someone just > > > needs to get agpgart working on the Alpha, thats the big step. > > > > That shouldn't be too hard since many (all?) AGP alpha boards (UP1000's > > anyway) are based on the AMD 751 Northbridge? And there is already > > support for that in the kernel for x86. > > My AlphaPC 164LX does not have AGP at all - and I want to get G200/G400 PCI > working on it with dri, using 21174 features. After looking into this a little more I have found it is uglier than that. The answers I have are not very good. I assume you are wanting to use this with X. There is a rather odd driver issue involved. There are two X drivers available for the G400. One from Matrox and one in the version of X that you are using. The Matrox driver will not work under the 2.4.x kernel for DRM due to a version conflict. (It wants version 1.0 and 2.4.x uses version 2.0.) It will also not compile with 4.0.2 and above at the present time. The XFree86 version has some odd problems in Xinerama, but at least it works. (Ugly artifact borders on the second screen.) BUT... Both drivers want Matrox's HALlib. (Which is x86 binary only.) Matrox will not release the info on that interface to the chipset. (Using the standard corporate excuse whenever they don't want to do something "Intelectual Property concerns".) Good luck on getting them to make an Alpha version of the library or get them to release the underlying library interface specs. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: [OT] Re: 2.4.x, drm, g400 and pci_set_master
On Thu, 8 Feb 2001, Petr Vandrovec wrote: On 8 Feb 01 at 13:14, Alex Deucher wrote: Jeff Hartmann wrote: Petr Vandrovec wrote: It does not use dynamic DMA mapping, because it doesn't do PCI DMA at all. It uses AGP DMA. Actually, it shouldn't be too hard to get it to work on the Alpha (just a few 32/64 bit issues probably.) Someone just needs to get agpgart working on the Alpha, thats the big step. That shouldn't be too hard since many (all?) AGP alpha boards (UP1000's anyway) are based on the AMD 751 Northbridge? And there is already support for that in the kernel for x86. My AlphaPC 164LX does not have AGP at all - and I want to get G200/G400 PCI working on it with dri, using 21174 features. After looking into this a little more I have found it is uglier than that. The answers I have are not very good. I assume you are wanting to use this with X. There is a rather odd driver issue involved. There are two X drivers available for the G400. One from Matrox and one in the version of X that you are using. The Matrox driver will not work under the 2.4.x kernel for DRM due to a version conflict. (It wants version 1.0 and 2.4.x uses version 2.0.) It will also not compile with 4.0.2 and above at the present time. The XFree86 version has some odd problems in Xinerama, but at least it works. (Ugly artifact borders on the second screen.) BUT... Both drivers want Matrox's HALlib. (Which is x86 binary only.) Matrox will not release the info on that interface to the chipset. (Using the standard corporate excuse whenever they don't want to do something "Intelectual Property concerns".) Good luck on getting them to make an Alpha version of the library or get them to release the underlying library interface specs. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Matrox Marvell G400
On Mon, 5 Feb 2001, Wakko Warner wrote: > How well is this card supported for it's capture capabilities and dual head? The capture features are undocumented and unsupported (to my knowledge). As far as I have heard, the Rainbow Runner card is not supported in Linux and Matrox has no plans of doing it. As for the dual monitor... You need XFree86 4.0.1 or later. Matrox has drivers for 4.0.1. The last time I checked, they did not have anything that compiles under 4.0.2. Dual monitor mode works with xinerama as long as you are at the same resolution and color depth. (I have it working on my machine here. The Matrox driver docs tell how to make it work. It is not hard.) I have noticed some visual problems on the second screen under 4.0.2. (Ugly, but usable.) Not certain when that will get fixed. Due to Matrox using a proprietary library (HALlib), there is not alot of effort being put into making it work right. (Kind of working in the dark at this point...) This is more of a question for the xpert list on xfree86.org. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Matrox Marvell G400
On Mon, 5 Feb 2001, Wakko Warner wrote: How well is this card supported for it's capture capabilities and dual head? The capture features are undocumented and unsupported (to my knowledge). As far as I have heard, the Rainbow Runner card is not supported in Linux and Matrox has no plans of doing it. As for the dual monitor... You need XFree86 4.0.1 or later. Matrox has drivers for 4.0.1. The last time I checked, they did not have anything that compiles under 4.0.2. Dual monitor mode works with xinerama as long as you are at the same resolution and color depth. (I have it working on my machine here. The Matrox driver docs tell how to make it work. It is not hard.) I have noticed some visual problems on the second screen under 4.0.2. (Ugly, but usable.) Not certain when that will get fixed. Due to Matrox using a proprietary library (HALlib), there is not alot of effort being put into making it work right. (Kind of working in the dark at this point...) This is more of a question for the xpert list on xfree86.org. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Recommended swap for 2.4.x.
On Fri, 2 Feb 2001, Pavel Machek wrote: > Hi! > > > I am asking because I have just ordered a new drive for my Vaio (8.1 gig > > in a 8.45mm drive!) and I want to install 2.4.x on it. (I like getting > > 8.1GB in under centimeter? That's 8.1GB in compactflash slot? Standard laptop drive size except 8.45mm thick as opposed to 9.5mm thick. (Kind of bites too. If it would take a 9.5mm drive I could put in 30 gigs instead of 8.1gigs.) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Recommended swap for 2.4.x.
On Fri, 2 Feb 2001, Pavel Machek wrote: Hi! I am asking because I have just ordered a new drive for my Vaio (8.1 gig in a 8.45mm drive!) and I want to install 2.4.x on it. (I like getting 8.1GB in under centimeter? That's 8.1GB in compactflash slot? Standard laptop drive size except 8.45mm thick as opposed to 9.5mm thick. (Kind of bites too. If it would take a 9.5mm drive I could put in 30 gigs instead of 8.1gigs.) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Secure Linux
On Tue, 30 Jan 2001, Dale Amon wrote: > Has anyone else signed up on the NSA's secure Linux > discussion list? The idea of NSA backing the development > of a secure GPL'd linux is one I find intriguing. > > However I have only seen one posting. Is there anyone > "real" involved with it? That would be telling. Be seeing you! [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Secure Linux
On Tue, 30 Jan 2001, Dale Amon wrote: Has anyone else signed up on the NSA's secure Linux discussion list? The idea of NSA backing the development of a secure GPL'd linux is one I find intriguing. However I have only seen one posting. Is there anyone "real" involved with it? That would be telling. Be seeing you! [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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/
Recommended swap for 2.4.x.
What is the recommended amount of swap with the 2.4.x kernels? The standard rule is usually memory x 2. (But that is more a Solaris superstition than anything else.) Is it the same or "as much as I can get away with" or something else? I am asking because I have just ordered a new drive for my Vaio (8.1 gig in a 8.45mm drive!) and I want to install 2.4.x on it. (I like getting the swap partition done right the first time. Repartitions are a pain. Especially if you screw up.) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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/
Recommended swap for 2.4.x.
What is the recommended amount of swap with the 2.4.x kernels? The standard rule is usually memory x 2. (But that is more a Solaris superstition than anything else.) Is it the same or "as much as I can get away with" or something else? I am asking because I have just ordered a new drive for my Vaio (8.1 gig in a 8.45mm drive!) and I want to install 2.4.x on it. (I like getting the swap partition done right the first time. Repartitions are a pain. Especially if you screw up.) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: [OT?] Coding Style
On Tue, 23 Jan 2001, Helge Hafting wrote: > Stephen Satchell wrote: > > [lots of good advice deleted] > > One goal of language designers is to REMOVE the need for comments. With a > > good fourth-generation or fifth-generation language, the need for comments > > diminishes to a detailed description of the data sets and any highly > > unusual operations or transforms on the data. > > This is but a dream. You can't "design out" the need for comments by > approaching natural language. Try reading a law book and realize that > natural language too may be twisted to the extent that it needs > extensive comments. The same goes for any computer language powerful > enough to do useful work. Actually using natural language and other such constructs may INCREASE the need for comments. For more examples, see Perl. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: [OT?] Coding Style
On Tue, 23 Jan 2001, Helge Hafting wrote: Stephen Satchell wrote: [lots of good advice deleted] One goal of language designers is to REMOVE the need for comments. With a good fourth-generation or fifth-generation language, the need for comments diminishes to a detailed description of the data sets and any highly unusual operations or transforms on the data. This is but a dream. You can't "design out" the need for comments by approaching natural language. Try reading a law book and realize that natural language too may be twisted to the extent that it needs extensive comments. The same goes for any computer language powerful enough to do useful work. Actually using natural language and other such constructs may INCREASE the need for comments. For more examples, see Perl. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Total loss with 2.4.0 (release)
On Tue, 23 Jan 2001, Mike A. Harris wrote: > On Mon, 15 Jan 2001, Trever Adams wrote: > > >I had a similar experience. All I can say is windows 98 > >and ME seem to have it out for Linux drives running late > >2.3.x and 2.4.0 test and release. I had windows completely > >fry my Linux drive and I lost everything. I had some old > >backups and was able to restore at least the majority of > >older stuff. > > > >Sorry and good luck. > > I don't see how Windows 9x can be at fault in any way shape or > form, if you can boot between 2.2.x kernel and 9x no problem, but > lose your disk if you boot Win98 and then 2.3.x/2.4.x and lose > everything. Windows does not touch your Linux fs's, so if there > is a problem, it most likely is a kernel bug of some kind that > doesn't initialize something properly. I am seeing weird reporting of size problems on a VFAT partition. It has not corrupted anything, but a "df" shows the size to be a large negative number. (It worked when the drive had about 22 gigs full on the 30 gig partition, but went wonky when I deleted everything on that partition.) Drive is a Western Digital 307AA 30.7 gb drive. Kernel is 2.4.0 on a P-III 650. Partition is type "c" (Win95 FAT32 (LBA)). Partition starts at 1 and ends on 3739. 30033486 blocks. /dev/hdb130018800 -295147905179350204416 32652912 9% /export1 df version is from fileutils-4.0. (Mandrake package fileutils-4.0-13mdk, which is current.) du reports the correct amount of space used. I can read the drive, but the drive size reported is not correct. Not certain if this is a problem in 2.4.0, df, or something else. Have never seen this problem before. (And I mount vfat partitions frequently.) I have not seen any file corruption on this or the other Linux partition that stays in the drive the few and far between times I run Win 98. (Carmageddon 3 does not run under Linux yet...) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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/
Probably Off-topic Question...
This is probably a user-land and/or undocumented thing, but I am not certain where to get the correct info. Does anyone know how to get the screen brightness control to work on a Sony Vaio N505VE? There seems to be some sort of proprietary hook to get it to work that requires their install of Windows. (This is a problem as it was removed immediatly after purchacing the laptop.) I figured someone here might know, since at least one person on this list has a Vaio. (Unless Linus sold it to buy more beer. ]:> ) Pointers to a non-Windows solution would be appreciated, as it is hell on my battery life. BTW, the Yamaha sound chip in the Vaio is supported under Alsa. You might ask them what they did to get it to work, so it can be included in the stock kernel. (Or maybe it already has and I have just not been looking.) And as for code comments, they should be written in Ancient Greek with code examples taken from APL and BCPL and written using the ISO character set for Sanscrit. (To avoid complaints of swear words appearing in them by the morally clenched.) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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/
Probably Off-topic Question...
This is probably a user-land and/or undocumented thing, but I am not certain where to get the correct info. Does anyone know how to get the screen brightness control to work on a Sony Vaio N505VE? There seems to be some sort of proprietary hook to get it to work that requires their install of Windows. (This is a problem as it was removed immediatly after purchacing the laptop.) I figured someone here might know, since at least one person on this list has a Vaio. (Unless Linus sold it to buy more beer. ]: ) Pointers to a non-Windows solution would be appreciated, as it is hell on my battery life. BTW, the Yamaha sound chip in the Vaio is supported under Alsa. You might ask them what they did to get it to work, so it can be included in the stock kernel. (Or maybe it already has and I have just not been looking.) And as for code comments, they should be written in Ancient Greek with code examples taken from APL and BCPL and written using the ISO character set for Sanscrit. (To avoid complaints of swear words appearing in them by the morally clenched.) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: Total loss with 2.4.0 (release)
On Tue, 23 Jan 2001, Mike A. Harris wrote: On Mon, 15 Jan 2001, Trever Adams wrote: I had a similar experience. All I can say is windows 98 and ME seem to have it out for Linux drives running late 2.3.x and 2.4.0 test and release. I had windows completely fry my Linux drive and I lost everything. I had some old backups and was able to restore at least the majority of older stuff. Sorry and good luck. I don't see how Windows 9x can be at fault in any way shape or form, if you can boot between 2.2.x kernel and 9x no problem, but lose your disk if you boot Win98 and then 2.3.x/2.4.x and lose everything. Windows does not touch your Linux fs's, so if there is a problem, it most likely is a kernel bug of some kind that doesn't initialize something properly. I am seeing weird reporting of size problems on a VFAT partition. It has not corrupted anything, but a "df" shows the size to be a large negative number. (It worked when the drive had about 22 gigs full on the 30 gig partition, but went wonky when I deleted everything on that partition.) Drive is a Western Digital 307AA 30.7 gb drive. Kernel is 2.4.0 on a P-III 650. Partition is type "c" (Win95 FAT32 (LBA)). Partition starts at 1 and ends on 3739. 30033486 blocks. /dev/hdb130018800 -295147905179350204416 32652912 9% /export1 df version is from fileutils-4.0. (Mandrake package fileutils-4.0-13mdk, which is current.) du reports the correct amount of space used. I can read the drive, but the drive size reported is not correct. Not certain if this is a problem in 2.4.0, df, or something else. Have never seen this problem before. (And I mount vfat partitions frequently.) I have not seen any file corruption on this or the other Linux partition that stays in the drive the few and far between times I run Win 98. (Carmageddon 3 does not run under Linux yet...) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: [OT?] Coding Style
On Sun, 21 Jan 2001, Admin Mailing Lists wrote: > > And the lord spake, saying, "First shalt thou write thy holy code. Indenting > > shalt thou count to three, no more, no less. Three shalt be the spaces thou > > shalt count, and the number of the counting shalt be three. Four shalt thou > > not count, nor count thou two, excepting that thou then proceedeth to three. > > Eight is right out. Once the number three, being the third number be > > reached, shalt thou move towards indenting thy next line .. > > > > now I know why I never read the bible. I thought that was the indention rules for Python. ]:> [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: [OT?] Coding Style
On Sun, 21 Jan 2001, Admin Mailing Lists wrote: And the lord spake, saying, "First shalt thou write thy holy code. Indenting shalt thou count to three, no more, no less. Three shalt be the spaces thou shalt count, and the number of the counting shalt be three. Four shalt thou not count, nor count thou two, excepting that thou then proceedeth to three. Eight is right out. Once the number three, being the third number be reached, shalt thou move towards indenting thy next line .. now I know why I never read the bible. I thought that was the indention rules for Python. ]: [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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/
X performance on 2.4.0 v.s. 2.4.0-test12
I have seen a number of reports claiming something broken in 2.4.0 for DRI. I have tested under 2.4.0 and 2.4.0 test 12 with the exact same setup. I see a slight variation in frame rates under the release version, but so small as to be within statistical varience. Everything else seems to work in reguards to DRI and AGPGART so far. (Of course, the X server on my desk will now explode since I said that...) I have noticed that the framerate takes a hard nosedive if xinerama is turned on, but that is explained in the docs. I have not seen any "flashing" behaviour or any other reported weirdnesses. Maybe it is the sacrifices made to dark penguin gods during that last full moon. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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/
X performance on 2.4.0 v.s. 2.4.0-test12
I have seen a number of reports claiming something broken in 2.4.0 for DRI. I have tested under 2.4.0 and 2.4.0 test 12 with the exact same setup. I see a slight variation in frame rates under the release version, but so small as to be within statistical varience. Everything else seems to work in reguards to DRI and AGPGART so far. (Of course, the X server on my desk will now explode since I said that...) I have noticed that the framerate takes a hard nosedive if xinerama is turned on, but that is explained in the docs. I have not seen any "flashing" behaviour or any other reported weirdnesses. Maybe it is the sacrifices made to dark penguin gods during that last full moon. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: DRI doesn't work on 2.4.0 but does on prerelease-ac5
On Wed, 10 Jan 2001, Alan Cox wrote: > > The Mesa package in Red Hat 7 won't do DRI with recent XFree86 CVS. > > Yep. Its Mesa 3.3/DRI 1.0. XFree86 CVS is Mesa 3.4/DRI 2.0. That has several > advantages including mostly working on Matrox cards which 1.0 never did (for > me anyway) and handling things that Mesa 3.3 tried to allocate the odd gig > of ram for and then exploded. > > With the CVS stuff the 2.4 kernel should work out of the box. You need -ac for > some ALi AGP chipsets. My experiences with the Matrox G400 has been similar. With 4.0.1 and the Matrox drivers, I could get DRI to work... For a while and then the whole thing would lock tight as a drum, kernel and all. The Matrox drivers on their ftp site will not even build with XFree86 4.0.2. XFree86 4.0.2 with 2.4.0-test 12 no longer locks up on some GL games. (Heavy Gear II, Quake III, and Heretic 2 all work well.) The only exception I can find is Descent 3 which has a nasty visual smearing problem that makes it unplayable. (Not certain why. Have not pressed the issue with Loki yet.) Xinerama has an odd problem, which Keith Packard is looking into. (When he gets back from Hawaii.) Xinerama is usable, but has some ugly screen artifacts on the second screen. The other big difference between 4.0.1 under the 2.2.17 with back-ported AGP and the 4.0.2 on 2.4.0-test 12 is that I now get a contant frame rate. On the earlier version, the framerate could bounce around 25% of the total frames with the Mesa gears test. The new version I see a varience of about 2 frames or so! VERY steady. I will be testing the performance under 2.4.0 final sometime later tonight, after I am done with the project I am currently working on. (One of those "I have an idea and must test it now" kinda days. So far, the code has all worked...) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: [OT]: DRI doesn't work on 2.4.0 but does on prerelease-ac5
On Mon, 8 Jan 2001, J Sloan wrote: > This is a little OT for linux-kernel, but I'll take a swing at it > since I'm running 2.4 and Xfree 4 with a voodoo 3. > > After upgrading to Red Hat 7.0, I noticed 3D screensavers > and Quake 3 Arena were dog slow - in the end, I basically > had to make sure the mesa libs didn't get found before the > real opengl libs. > > In my case, that meant nuking mesa from my system and > letting Linux use what was left, which got me back the good > accelerated performance - you may choose a less drastic > option. I don't see any breakage from the absence of mesa. Sounds like the version you blew away was not the one built in 4.0.2. (Mesa is built along with XFree86 now, not as an add-on.) I will test with my current configuration and see if I can duplicate the slow down. I am currently using a Matrox G400 max card with 4.0.2cvs. I get about 1285 frames per second on the gears demo currently. We will see if that changes with the 2.4.0 final release version. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: [OT]: DRI doesn't work on 2.4.0 but does on prerelease-ac5
On Mon, 8 Jan 2001, J Sloan wrote: This is a little OT for linux-kernel, but I'll take a swing at it since I'm running 2.4 and Xfree 4 with a voodoo 3. After upgrading to Red Hat 7.0, I noticed 3D screensavers and Quake 3 Arena were dog slow - in the end, I basically had to make sure the mesa libs didn't get found before the real opengl libs. In my case, that meant nuking mesa from my system and letting Linux use what was left, which got me back the good accelerated performance - you may choose a less drastic option. I don't see any breakage from the absence of mesa. Sounds like the version you blew away was not the one built in 4.0.2. (Mesa is built along with XFree86 now, not as an add-on.) I will test with my current configuration and see if I can duplicate the slow down. I am currently using a Matrox G400 max card with 4.0.2cvs. I get about 1285 frames per second on the gears demo currently. We will see if that changes with the 2.4.0 final release version. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: DRI doesn't work on 2.4.0 but does on prerelease-ac5
On Wed, 10 Jan 2001, Alan Cox wrote: The Mesa package in Red Hat 7 won't do DRI with recent XFree86 CVS. Yep. Its Mesa 3.3/DRI 1.0. XFree86 CVS is Mesa 3.4/DRI 2.0. That has several advantages including mostly working on Matrox cards which 1.0 never did (for me anyway) and handling things that Mesa 3.3 tried to allocate the odd gig of ram for and then exploded. With the CVS stuff the 2.4 kernel should work out of the box. You need -ac for some ALi AGP chipsets. My experiences with the Matrox G400 has been similar. With 4.0.1 and the Matrox drivers, I could get DRI to work... For a while and then the whole thing would lock tight as a drum, kernel and all. The Matrox drivers on their ftp site will not even build with XFree86 4.0.2. XFree86 4.0.2 with 2.4.0-test 12 no longer locks up on some GL games. (Heavy Gear II, Quake III, and Heretic 2 all work well.) The only exception I can find is Descent 3 which has a nasty visual smearing problem that makes it unplayable. (Not certain why. Have not pressed the issue with Loki yet.) Xinerama has an odd problem, which Keith Packard is looking into. (When he gets back from Hawaii.) Xinerama is usable, but has some ugly screen artifacts on the second screen. The other big difference between 4.0.1 under the 2.2.17 with back-ported AGP and the 4.0.2 on 2.4.0-test 12 is that I now get a contant frame rate. On the earlier version, the framerate could bounce around 25% of the total frames with the Mesa gears test. The new version I see a varience of about 2 frames or so! VERY steady. I will be testing the performance under 2.4.0 final sometime later tonight, after I am done with the project I am currently working on. (One of those "I have an idea and must test it now" kinda days. So far, the code has all worked...) [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: DRI doesn't work on 2.4.0 but does on prerelease-ac5
On Sat, 6 Jan 2001, Michael D. Crawford wrote: > AGP, VIA support, DRM, and r128 DRM are all compiled in statically rather than > as modules. AGPGART doe *not* work if compiled statically. Compile it as a module. You will be much happier. (i.e. It might actually work.) I would also compile DRM and the r128 drivers as modules as well. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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: DRI doesn't work on 2.4.0 but does on prerelease-ac5
On Sat, 6 Jan 2001, Michael D. Crawford wrote: AGP, VIA support, DRM, and r128 DRM are all compiled in statically rather than as modules. AGPGART doe *not* work if compiled statically. Compile it as a module. You will be much happier. (i.e. It might actually work.) I would also compile DRM and the r128 drivers as modules as well. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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] 2.4.0-prerelease: preemptive kernel.
On Fri, 5 Jan 2001, Andi Kleen wrote: > On Thu, Jan 04, 2001 at 04:36:32PM -0800, ludovic fernandez wrote: > > Saying that, I definitely agree that I want/need to one day listen to > > my MP3s while building my kernel. > > ??? I can listen to MP3s just fine while building kernels, on a not very > powerful K6. I have found that sound card "hick-ups" while doing heavy work under Linux are an indication of an IRQ problem. I had that problem on my P-III 650 until I went in and rearranged cards and sorted out what was on what IRQ. (The BIOS just picked numbers, it gave you no way to determine order or slots. What IRQ you got depended on the slot and there was no real way to chenge it.) Some boards have a very poor way of chosing the assignment of IRQs. You just have to shuffle things until you get what you want. Since I did the manual reorg of the hardware, things have run MUCH smoother. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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] 2.4.0-prerelease: preemptive kernel.
On Fri, 5 Jan 2001, Andi Kleen wrote: On Thu, Jan 04, 2001 at 04:36:32PM -0800, ludovic fernandez wrote: Saying that, I definitely agree that I want/need to one day listen to my MP3s while building my kernel. ??? I can listen to MP3s just fine while building kernels, on a not very powerful K6. I have found that sound card "hick-ups" while doing heavy work under Linux are an indication of an IRQ problem. I had that problem on my P-III 650 until I went in and rearranged cards and sorted out what was on what IRQ. (The BIOS just picked numbers, it gave you no way to determine order or slots. What IRQ you got depended on the slot and there was no real way to chenge it.) Some boards have a very poor way of chosing the assignment of IRQs. You just have to shuffle things until you get what you want. Since I did the manual reorg of the hardware, things have run MUCH smoother. [EMAIL PROTECTED] | Note to AOL users: for a quick shortcut to reply Alan Olsen| to my mail, just hit the ctrl, alt and del keys. "In the future, everything will have its 15 minutes of blame." - 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/
