Re: linux dvb alps_tdlb7 removed
In article <[EMAIL PROTECTED]> you wrote: > With version 2.6.10 the driver for the tuner frontend from ALPS TDLB7 > was removed. > > Why do you think that this is a dead file? > While I'm happy with the work you do for dvb on Linux, and I want to > thank you for this anyway, my TV does not work anymore! :( > > I use a TechoTrend Premium card with that frontend on it. It worked > fine until 2.6.10. > Can you put it back into mainline? Is there some work to do for > reinsertion? I think the driver you now need is sp8870. It's just another name for the same file. Regards, Juri - 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 dvb alps_tdlb7 removed
In article [EMAIL PROTECTED] you wrote: With version 2.6.10 the driver for the tuner frontend from ALPS TDLB7 was removed. Why do you think that this is a dead file? While I'm happy with the work you do for dvb on Linux, and I want to thank you for this anyway, my TV does not work anymore! :( I use a TechoTrend Premium card with that frontend on it. It worked fine until 2.6.10. Can you put it back into mainline? Is there some work to do for reinsertion? I think the driver you now need is sp8870. It's just another name for the same file. Regards, Juri - 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: FAT32 superiority over ext2 :-)
In article <0106250203070J.00430@starship> you wrote: > On Monday 25 June 2001 01:49, Albert D. Cahalan wrote: >> Daniel Phillips writes: >> > On Monday 25 June 2001 00:54, Albert D. Cahalan wrote: >> >> By dumb luck (?), FAT32 is compatible with the phase-tree algorithm >> >> as seen in Tux2. This means it offers full data integrity. >> >> Yep, it whips your typical journalling filesystem. Look at what >> >> we have in the superblock (boot sector): >> >> >> >> __u32 fat32_length; /* sectors/FAT */ >> >> __u16 flags; /* bit 8: fat mirroring, low 4: active fat */ >> >> __u8 version[2];/* major, minor filesystem version */ >> >> __u32 root_cluster; /* first cluster in root directory */ >> >> __u16 info_sector; /* filesystem info sector */ >> >> >> >> All in one atomic write, one can... >> >> >> >> 1. change the active FAT >> >> 2. change the root directory >> >> 3. change the free space count >> >> >> >> That's enough to atomically move from one phase to the next. >> >> You create new directories in the free space, and make FAT >> >> changes to an inactive FAT copy. Then you write the superblock >> >> to atomically transition to the next phase. [--snip--] > When can we expect the patch? Don't! Blasphemy!!! Juri ;-) -- Juri Haberland <[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: FAT32 superiority over ext2 :-)
In article 0106250203070J.00430@starship you wrote: On Monday 25 June 2001 01:49, Albert D. Cahalan wrote: Daniel Phillips writes: On Monday 25 June 2001 00:54, Albert D. Cahalan wrote: By dumb luck (?), FAT32 is compatible with the phase-tree algorithm as seen in Tux2. This means it offers full data integrity. Yep, it whips your typical journalling filesystem. Look at what we have in the superblock (boot sector): __u32 fat32_length; /* sectors/FAT */ __u16 flags; /* bit 8: fat mirroring, low 4: active fat */ __u8 version[2];/* major, minor filesystem version */ __u32 root_cluster; /* first cluster in root directory */ __u16 info_sector; /* filesystem info sector */ All in one atomic write, one can... 1. change the active FAT 2. change the root directory 3. change the free space count That's enough to atomically move from one phase to the next. You create new directories in the free space, and make FAT changes to an inactive FAT copy. Then you write the superblock to atomically transition to the next phase. [--snip--] When can we expect the patch? Don't! Blasphemy!!! Juri ;-) -- Juri Haberland [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: 2.4.5-ac13, APM, and Dell Inspiron 8000
You wrote: > Juri Haberland wrote: >> >> Ok, I just tried that and my i8000 locked up as well. No problems with >> 2.4.5 as well. I have also another problem: >> Running with -ac13 it doesn't poweroff properly - but it did running >> 2.4.5. Sometimes it just stops where it should poweroff and locks hard, >> sometimes it blanks the display before locking up hard. > > The Dell i5000e crashes when switching between mains and battery when > the disk is active, so you might try to plug/unplug with the system > quiet. > > If this works, you'll be in a *little* better spot. > > As for hanging, you might try suspending it (i.e., close the display) > and opening it back up. This works for the i5000e; it also clears the > display that sometimes goes *nuts* when switching video modes. This > last behavior has only surfaced with the latest A06 BIOS. Hi, I didn't have all these problems when running 2.4.5 or 2.4.6-pre2. So there is something odd in Alan's tree (I assume). Juri -- Juri Haberland <[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: Need a helping hand (realproducer and radio device)
In article <[EMAIL PROTECTED]> you wrote: > Hi, > > I have an Hauppauge WinTV/Radio card and I want to be able to use it's radio > device as a source for live broadcast. > > It's RH71 distro updated with mainstream 2.4.5 . > > Radio device works fine on it's own meaning that I can tune the station and > listen to it. > > RealProducer (8.5) also works fine meaning that it encodes video inputs and Line-In > input into realmedia stream just fine. > > > The problem is that in startup realproducer mutes (IMO) or shuts down or something, >that radio > device on bt8x8 card and therefore no actual audio signal gets to Line-In resulting >in no audio > in realmedia stream. I had a similar problem long time ago. The point is that the realproducer mutes the recording source in the mixer. Try to reenable it using aumix or a similar application. Juri -- Juri Haberland <[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: 2.4.5-ac13, APM, and Dell Inspiron 8000
You wrote: > > I've been running 2.4.5 on my new Dell I8000 without too many > problems. Last night I built -ac13 (on my porch) and booted it > without incident. Later, going inside and re-connecting the AC I > notice that the thing's hung. I play around a bit and discover that > the act of plugging or unplugging the power cord will hang the box. > > This lead me to disable all power manglement in the BIOS. No joy. > > This problem does not exist using straight 2.4.5. > > Has anybody else seen this? Any debugging suggestions? Or stated > differently, has anybody with this machine arrived at a configuration > that avoids weirdness in the power management framework? Ok, I just tried that and my i8000 locked up as well. No problems with 2.4.5 as well. I have also another problem: Running with -ac13 it doesn't poweroff properly - but it did running 2.4.5. Sometimes it just stops where it should poweroff and locks hard, sometimes it blanks the display before locking up hard. Alan, what other infos do you need? Juri -- Juri Haberland <[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: 2.4.5-ac13, APM, and Dell Inspiron 8000
You wrote: I've been running 2.4.5 on my new Dell I8000 without too many problems. Last night I built -ac13 (on my porch) and booted it without incident. Later, going inside and re-connecting the AC I notice that the thing's hung. I play around a bit and discover that the act of plugging or unplugging the power cord will hang the box. This lead me to disable all power manglement in the BIOS. No joy. This problem does not exist using straight 2.4.5. Has anybody else seen this? Any debugging suggestions? Or stated differently, has anybody with this machine arrived at a configuration that avoids weirdness in the power management framework? Ok, I just tried that and my i8000 locked up as well. No problems with 2.4.5 as well. I have also another problem: Running with -ac13 it doesn't poweroff properly - but it did running 2.4.5. Sometimes it just stops where it should poweroff and locks hard, sometimes it blanks the display before locking up hard. Alan, what other infos do you need? Juri -- Juri Haberland [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: Need a helping hand (realproducer and radio device)
In article [EMAIL PROTECTED] you wrote: Hi, I have an Hauppauge WinTV/Radio card and I want to be able to use it's radio device as a source for live broadcast. It's RH71 distro updated with mainstream 2.4.5 . Radio device works fine on it's own meaning that I can tune the station and listen to it. RealProducer (8.5) also works fine meaning that it encodes video inputs and Line-In input into realmedia stream just fine. The problem is that in startup realproducer mutes (IMO) or shuts down or something, that radio device on bt8x8 card and therefore no actual audio signal gets to Line-In resulting in no audio in realmedia stream. I had a similar problem long time ago. The point is that the realproducer mutes the recording source in the mixer. Try to reenable it using aumix or a similar application. Juri -- Juri Haberland [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: 2.4.5-ac13, APM, and Dell Inspiron 8000
You wrote: Juri Haberland wrote: Ok, I just tried that and my i8000 locked up as well. No problems with 2.4.5 as well. I have also another problem: Running with -ac13 it doesn't poweroff properly - but it did running 2.4.5. Sometimes it just stops where it should poweroff and locks hard, sometimes it blanks the display before locking up hard. The Dell i5000e crashes when switching between mains and battery when the disk is active, so you might try to plug/unplug with the system quiet. If this works, you'll be in a *little* better spot. As for hanging, you might try suspending it (i.e., close the display) and opening it back up. This works for the i5000e; it also clears the display that sometimes goes *nuts* when switching video modes. This last behavior has only surfaced with the latest A06 BIOS. Hi, I didn't have all these problems when running 2.4.5 or 2.4.6-pre2. So there is something odd in Alan's tree (I assume). Juri -- Juri Haberland [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: 3c900 card and kernel 2.4.3
Juri Haberland wrote: > > Andrew Morton wrote: > > > For non-modular drivers things are less easy. If you > > want to force it to use 10baseT (if_port zero) then > > it should work OK if you cheat and use mem_start=0x400. > > So `ether=0,0,0x400'. > > > > For BNC, it should work just fine with `ether=0,0,1'. > > If it doesn't, please shout at me. Compile the > > driver with `static int vortex_debug = 7;' at line > > 183 and send me the boot logs. > > Hi Andrew, > > I tried it with 'ether=0,0,1', 3 and also 7, but to no avail. The output > of dmesg follows. Oh, and I forgot to say, that the card is actually set to autoselection in the EEPROM (I just had a look with the DOS tool). Juri - 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: 3c900 card and kernel 2.4.3
Andrew Morton wrote: > > Juri Haberland wrote: > > Do you use 10Base2 (aka cheaper net)? > > I do and after upgrading to 2.4.3 (I think) I had to force the driver to > > use the BNC connector though the card was configured (via the little config > > program supplied by 3com) to always use the BNC connector... > > This way I lost several hours to figure out why it wasn't working anymore and > > to discover that I have to build it as a module instead of having it compiled > > into the kernel because I couldn't make it work with kernel options - only > > with driver options... > > Any suggestions? > For non-modular drivers things are less easy. If you > want to force it to use 10baseT (if_port zero) then > it should work OK if you cheat and use mem_start=0x400. > So `ether=0,0,0x400'. > > For BNC, it should work just fine with `ether=0,0,1'. > If it doesn't, please shout at me. Compile the > driver with `static int vortex_debug = 7;' at line > 183 and send me the boot logs. Hi Andrew, I tried it with 'ether=0,0,1', 3 and also 7, but to no avail. The output of dmesg follows. Thanks, Juri Linux version 2.4.4-xfs ([EMAIL PROTECTED]) (gcc version 2.96 2731 (Red Hat Linux 7.1 2.96-81)) #4 Tue May 15 23:17:53 CEST 2001 [--snip--] Kernel command line: auto BOOT_IMAGE=linux ro root=305 BOOT_FILE=/boot/vmlinuz hdc=ide-scsi ether=0,0,3 [--snip--] PCI: Found IRQ 10 for device 00:0f.0 3c59x.c:LK1.1.13 27 Jan 2001 Donald Becker and others. http://www.scyld.com/network/vortex.html See Documentation/networking/vortex.txt eth0: 3Com PCI 3c900 Cyclone 10Mbps Combo at 0xc800, 00:10:5a:d6:84:df, IRQ 10 product code 5050 rev 00.4 date 11-21-98 Internal config register is 180, transceivers 0x38. 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface. MII transceiver found at address 24, status 1809. Enabling bus-master transmits and whole-frame receives. eth0: scatter/gather enabled. h/w checksums enabled [--snip--] spurious 8259A interrupt: IRQ7. eth0: Filling in the Rx ring. eth0: using NWAY device table, not 8 eth0: Initial media type Autonegotiate. vortex_up(): writing 0x180 to InternalConfig eth0: MII #24 status 1809, link partner capability , info1 0010, setting half-duplex. eth0: vortex_up() InternalConfig 0180. eth0: vortex_up() irq 10 media status 8080. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 0. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 5 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 1. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 5 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 2. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 4 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. eth0: Media selection timer tick happened, Autonegotiate. dev->watchdog_timeo=500 eth0: MII transceiver has status 1809. eth0: Media selection timer finished, Autonegotiate. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 3. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 5 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 4. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 5 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 5. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 4 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 6. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 6 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 7. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 5 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. boomerang_interrupt. status=0xe081 eth0: interrupt, status e081, latency 4 ticks. eth0: In interrupt loop, status e081. eth0: vortex_error(), status=0xe081 eth0: Updating stats. eth0: exiting interrupt, status e000. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 8. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, l
Re: 3c900 card and kernel 2.4.3
Andrew Morton wrote: Juri Haberland wrote: Do you use 10Base2 (aka cheaper net)? I do and after upgrading to 2.4.3 (I think) I had to force the driver to use the BNC connector though the card was configured (via the little config program supplied by 3com) to always use the BNC connector... This way I lost several hours to figure out why it wasn't working anymore and to discover that I have to build it as a module instead of having it compiled into the kernel because I couldn't make it work with kernel options - only with driver options... Any suggestions? For non-modular drivers things are less easy. If you want to force it to use 10baseT (if_port zero) then it should work OK if you cheat and use mem_start=0x400. So `ether=0,0,0x400'. For BNC, it should work just fine with `ether=0,0,1'. If it doesn't, please shout at me. Compile the driver with `static int vortex_debug = 7;' at line 183 and send me the boot logs. Hi Andrew, I tried it with 'ether=0,0,1', 3 and also 7, but to no avail. The output of dmesg follows. Thanks, Juri Linux version 2.4.4-xfs ([EMAIL PROTECTED]) (gcc version 2.96 2731 (Red Hat Linux 7.1 2.96-81)) #4 Tue May 15 23:17:53 CEST 2001 [--snip--] Kernel command line: auto BOOT_IMAGE=linux ro root=305 BOOT_FILE=/boot/vmlinuz hdc=ide-scsi ether=0,0,3 [--snip--] PCI: Found IRQ 10 for device 00:0f.0 3c59x.c:LK1.1.13 27 Jan 2001 Donald Becker and others. http://www.scyld.com/network/vortex.html See Documentation/networking/vortex.txt eth0: 3Com PCI 3c900 Cyclone 10Mbps Combo at 0xc800, 00:10:5a:d6:84:df, IRQ 10 product code 5050 rev 00.4 date 11-21-98 Internal config register is 180, transceivers 0x38. 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface. MII transceiver found at address 24, status 1809. Enabling bus-master transmits and whole-frame receives. eth0: scatter/gather enabled. h/w checksums enabled [--snip--] spurious 8259A interrupt: IRQ7. eth0: Filling in the Rx ring. eth0: using NWAY device table, not 8 eth0: Initial media type Autonegotiate. vortex_up(): writing 0x180 to InternalConfig eth0: MII #24 status 1809, link partner capability , info1 0010, setting half-duplex. eth0: vortex_up() InternalConfig 0180. eth0: vortex_up() irq 10 media status 8080. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 0. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 5 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 1. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 5 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 2. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 4 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. eth0: Media selection timer tick happened, Autonegotiate. dev-watchdog_timeo=500 eth0: MII transceiver has status 1809. eth0: Media selection timer finished, Autonegotiate. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 3. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 5 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 4. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 5 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 5. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 4 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 6. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 6 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 7. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 5 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status e000. boomerang_interrupt. status=0xe081 eth0: interrupt, status e081, latency 4 ticks. eth0: In interrupt loop, status e081. eth0: vortex_error(), status=0xe081 eth0: Updating stats. eth0: exiting interrupt, status e000. boomerang_start_xmit() eth0: Trying to send a packet, Tx index 8. boomerang_interrupt. status=0xe201 eth0: interrupt, status e201, latency 5 ticks. eth0: In interrupt loop, status e201. boomerang_interrupt: wake queue eth0: exiting interrupt, status
Re: 3c900 card and kernel 2.4.3
Juri Haberland wrote: Andrew Morton wrote: For non-modular drivers things are less easy. If you want to force it to use 10baseT (if_port zero) then it should work OK if you cheat and use mem_start=0x400. So `ether=0,0,0x400'. For BNC, it should work just fine with `ether=0,0,1'. If it doesn't, please shout at me. Compile the driver with `static int vortex_debug = 7;' at line 183 and send me the boot logs. Hi Andrew, I tried it with 'ether=0,0,1', 3 and also 7, but to no avail. The output of dmesg follows. Oh, and I forgot to say, that the card is actually set to autoselection in the EEPROM (I just had a look with the DOS tool). Juri - 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: 3c900 card and kernel 2.4.3
Andrew Morton wrote: > Juri Haberland wrote: >> >> Do you use 10Base2 (aka cheaper net)? >> I do and after upgrading to 2.4.3 (I think) I had to force the driver to >> use the BNC connector though the card was configured (via the little config >> program supplied by 3com) to always use the BNC connector... >> This way I lost several hours to figure out why it wasn't working anymore and >> to discover that I have to build it as a module instead of having it compiled >> into the kernel because I couldn't make it work with kernel options - only >> with driver options... >> Any suggestions? > > Yes, sorry. > > The problem with earlier kernels was that autoselection > would notice the lack of 10baseT link beat and would then > advance on to trying AUI/SQE/10base2/etc. None of these > interfaces allow the driver to know if there's anything > connected and the driver consequently gets stuck on that > interface. The net effect: if you unplug the 10baseT > the driver gets stuck and you have to reboot. > > So autoselection was turned off if the NIC was found > to have autonegotiation hardware. If you want to use > the other interfaces, you have to provide an option, > as described in Documentation/networking/vortex.txt. Actually I would expect the driver to use the default setting from the EEPROM as it did before (or at least it seemed to me like that). > For non-modular drivers things are less easy. If you > want to force it to use 10baseT (if_port zero) then > it should work OK if you cheat and use mem_start=0x400. > So `ether=0,0,0x400'. > > For BNC, it should work just fine with `ether=0,0,1'. According to vortex.txt it should be `ether=0,0,3'. I think I tried that, but will do so again this evening. > If it doesn't, please shout at me. Compile the > driver with `static int vortex_debug = 7;' at line > 183 and send me the boot logs. Thanks for answering, Juri -- Juri Haberland <[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: 3c900 card and kernel 2.4.3
[EMAIL PROTECTED] wrote: > Hi there, > > when i install kernel 2.4.3 or higher on my slackware > system the card (3c900) gets detected but doesn't do > anything, i also get the line "using NWAY 8" or something > like that (had to switch back to 2.4.2 to type e-mail) > wondered if anyone else had this problem and if there's > some way to solve it? Hi Ronnie, did you receive any answer? Do you use 10Base2 (aka cheaper net)? I do and after upgrading to 2.4.3 (I think) I had to force the driver to use the BNC connector though the card was configured (via the little config program supplied by 3com) to always use the BNC connector... This way I lost several hours to figure out why it wasn't working anymore and to discover that I have to build it as a module instead of having it compiled into the kernel because I couldn't make it work with kernel options - only with driver options... Any suggestions? Juri -- Juri Haberland <[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: 3c900 card and kernel 2.4.3
[EMAIL PROTECTED] wrote: Hi there, when i install kernel 2.4.3 or higher on my slackware system the card (3c900) gets detected but doesn't do anything, i also get the line using NWAY 8 or something like that (had to switch back to 2.4.2 to type e-mail) wondered if anyone else had this problem and if there's some way to solve it? Hi Ronnie, did you receive any answer? Do you use 10Base2 (aka cheaper net)? I do and after upgrading to 2.4.3 (I think) I had to force the driver to use the BNC connector though the card was configured (via the little config program supplied by 3com) to always use the BNC connector... This way I lost several hours to figure out why it wasn't working anymore and to discover that I have to build it as a module instead of having it compiled into the kernel because I couldn't make it work with kernel options - only with driver options... Any suggestions? Juri -- Juri Haberland [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: 3c900 card and kernel 2.4.3
Andrew Morton wrote: Juri Haberland wrote: Do you use 10Base2 (aka cheaper net)? I do and after upgrading to 2.4.3 (I think) I had to force the driver to use the BNC connector though the card was configured (via the little config program supplied by 3com) to always use the BNC connector... This way I lost several hours to figure out why it wasn't working anymore and to discover that I have to build it as a module instead of having it compiled into the kernel because I couldn't make it work with kernel options - only with driver options... Any suggestions? Yes, sorry. The problem with earlier kernels was that autoselection would notice the lack of 10baseT link beat and would then advance on to trying AUI/SQE/10base2/etc. None of these interfaces allow the driver to know if there's anything connected and the driver consequently gets stuck on that interface. The net effect: if you unplug the 10baseT the driver gets stuck and you have to reboot. So autoselection was turned off if the NIC was found to have autonegotiation hardware. If you want to use the other interfaces, you have to provide an option, as described in Documentation/networking/vortex.txt. Actually I would expect the driver to use the default setting from the EEPROM as it did before (or at least it seemed to me like that). For non-modular drivers things are less easy. If you want to force it to use 10baseT (if_port zero) then it should work OK if you cheat and use mem_start=0x400. So `ether=0,0,0x400'. For BNC, it should work just fine with `ether=0,0,1'. According to vortex.txt it should be `ether=0,0,3'. I think I tried that, but will do so again this evening. If it doesn't, please shout at me. Compile the driver with `static int vortex_debug = 7;' at line 183 and send me the boot logs. Thanks for answering, Juri -- Juri Haberland [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: Crash: XFree86 4.0.3 and Kernel 4.0.3
Trever L. Adams wrote: > I hate to report this again, I saw some reports that it was fixed with > 4.0.3 of XFree86, so I tried XF86 4.0.3 with RedHat 7.1. > > Any time it tries to turn the monitor off, it crashes. I get no oopses. > Nothing. > > Has anyone figured out why it crashes? How can I fix it besides remove > the power savings option of automatically shutting the monitor off? > BTW, I am running this box with ACPI. It crashes even more if I use > APM. I never could figure that out, but anyway. Hi Trevor, I have the same problem with almost the same combination (RH 7.0 instead of RH 7.1). Did you compile the XFree server yourself and if so, did you optimize it for i686? The reason why I'm asking is that I did that and suspected the optimazions to cause the crashes. Juri -- Juri Haberland <[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: Crash: XFree86 4.0.3 and Kernel 4.0.3
Trever L. Adams wrote: I hate to report this again, I saw some reports that it was fixed with 4.0.3 of XFree86, so I tried XF86 4.0.3 with RedHat 7.1. Any time it tries to turn the monitor off, it crashes. I get no oopses. Nothing. Has anyone figured out why it crashes? How can I fix it besides remove the power savings option of automatically shutting the monitor off? BTW, I am running this box with ACPI. It crashes even more if I use APM. I never could figure that out, but anyway. Hi Trevor, I have the same problem with almost the same combination (RH 7.0 instead of RH 7.1). Did you compile the XFree server yourself and if so, did you optimize it for i686? The reason why I'm asking is that I did that and suspected the optimazions to cause the crashes. Juri -- Juri Haberland [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: 2.4.0 statd trouble
Luc de Louw wrote: > > Hi! > > On Wed, 24 Jan 2001, Juri Haberland wrote: > > > [EMAIL PROTECTED] wrote: > > > > > > linux-2.4.0 > > > > > > I have quite a lot of these log messages: > > > > > > Upgrade your nfs-utils to version 0.2.1 > > Maybee a dumb question: how to find out the version already installed? > And I think, its maybee useful to write this as a pre-req in Documentation/Changes ? Just type 'showmount -v'. Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering & securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: hotmail not dealing with ECN
Jeremy Hansen wrote: > > Just curious if others have noticed that hotmail is unable to deal with > ECN and wondering if this is a standard that should be encouraged, as in > should I tell hotmail that perhaps they should look into supporting it, or > should I not waste my breath and echo 0 > /proc/sys/net/ipv4/tcp_ecn? Forget it. I mailed them and this is the answer: "As ECN is not a widely used internet standard, and as Cisco does not have a stable OS for their routers that accepts ECN, anyone attempting to access our site through a gateway or from a computer that uses ECN will be unable to do so." Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering & securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: 2.4.0 statd trouble
[EMAIL PROTECTED] wrote: > > linux-2.4.0 > > I have quite a lot of these log messages: > > Jan 23 18:28:52 adglinux1 rpc.statd[1532]: gethostbyname error for adglinux1.hns.com > Jan 23 18:28:52 adglinux1 rpc.statd[1532]: STAT_FAIL to adglinux1.hns.com for SM_MON >of 139.85.108.141 > Jan 23 13:28:52 adglinux1 kernel: lockd: cannot monitor 139.85.108.141 Upgrade your nfs-utils to version 0.2.1 Greetings, Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering & securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: 2.4.0 statd trouble
[EMAIL PROTECTED] wrote: linux-2.4.0 I have quite a lot of these log messages: Jan 23 18:28:52 adglinux1 rpc.statd[1532]: gethostbyname error for adglinux1.hns.com Jan 23 18:28:52 adglinux1 rpc.statd[1532]: STAT_FAIL to adglinux1.hns.com for SM_MON of 139.85.108.141 Jan 23 13:28:52 adglinux1 kernel: lockd: cannot monitor 139.85.108.141 Upgrade your nfs-utils to version 0.2.1 Greetings, Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: hotmail not dealing with ECN
Jeremy Hansen wrote: Just curious if others have noticed that hotmail is unable to deal with ECN and wondering if this is a standard that should be encouraged, as in should I tell hotmail that perhaps they should look into supporting it, or should I not waste my breath and echo 0 /proc/sys/net/ipv4/tcp_ecn? Forget it. I mailed them and this is the answer: "As ECN is not a widely used internet standard, and as Cisco does not have a stable OS for their routers that accepts ECN, anyone attempting to access our site through a gateway or from a computer that uses ECN will be unable to do so." Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: 2.4.0 statd trouble
Luc de Louw wrote: Hi! On Wed, 24 Jan 2001, Juri Haberland wrote: [EMAIL PROTECTED] wrote: linux-2.4.0 I have quite a lot of these log messages: snip Upgrade your nfs-utils to version 0.2.1 Maybee a dumb question: how to find out the version already installed? And I think, its maybee useful to write this as a pre-req in Documentation/Changes ? Just type 'showmount -v'. Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: Purging the Buffer Cache
Al Peat wrote: > > Is there any way to completely purge the buffer > cache -- not just the write requests (ala 'sync' or > 'update'), but the whole thing? Can I just call > invalidate_buffers() or destroy_buffers()? > > I know, why in the world would a person do such a > thing? Research. It'd be easier for me to write a > little program or add it to a module than wait for a > reboot each time I need a clean buffer cache. What about the ioctl BLKFLSBUF ? If you are running a SuSE distrib there is already a tool called flushb that does what you want. If not, you can download the simple tool from http://innominate.org/~juri/flushb.tar.gz Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering & securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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] fix emu10k1 init breakage in 2.2.18
"Andreas M. Kirchwitz" wrote: > > Mikael Pettersson wrote: > > > 2.2.18 broke the emu10k1 driver when compiled into the kernel. > > The problem is that 2.2.18 now implements 2.4-style module_init, > > so emu10k1 ended up being initialised twice when built non-modular, > > which rendered it dysfunctional. The fix is to remove the now > > obsolete explicit init calls. Patch below. Please apply. > > Is there also a fix available to make the bass and treble settings > work again in mixer applications (for example, Gnome mix 1.2.0)? > This is (now, was) one of the biggest advantages of this card to have > control over bass and treble settings. > > It worked for the early 2.2.18pre patches, but stopped working in > the latest ones (including final 2.2.18). Yes, put something like "EXTRA_CFLAGS += -DTONE_CONTROL" into the Makefile in drivers/sound/emu10k1/ Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering & securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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] fix emu10k1 init breakage in 2.2.18
"Andreas M. Kirchwitz" wrote: Mikael Pettersson wrote: 2.2.18 broke the emu10k1 driver when compiled into the kernel. The problem is that 2.2.18 now implements 2.4-style module_init, so emu10k1 ended up being initialised twice when built non-modular, which rendered it dysfunctional. The fix is to remove the now obsolete explicit init calls. Patch below. Please apply. Is there also a fix available to make the bass and treble settings work again in mixer applications (for example, Gnome mix 1.2.0)? This is (now, was) one of the biggest advantages of this card to have control over bass and treble settings. It worked for the early 2.2.18pre patches, but stopped working in the latest ones (including final 2.2.18). Yes, put something like "EXTRA_CFLAGS += -DTONE_CONTROL" into the Makefile in drivers/sound/emu10k1/ Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: Purging the Buffer Cache
Al Peat wrote: Is there any way to completely purge the buffer cache -- not just the write requests (ala 'sync' or 'update'), but the whole thing? Can I just call invalidate_buffers() or destroy_buffers()? I know, why in the world would a person do such a thing? Research. It'd be easier for me to write a little program or add it to a module than wait for a reboot each time I need a clean buffer cache. What about the ioctl BLKFLSBUF ? If you are running a SuSE distrib there is already a tool called flushb that does what you want. If not, you can download the simple tool from http://innominate.org/~juri/flushb.tar.gz Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: emu10k1 broken in 2.2.18
[EMAIL PROTECTED] wrote: > > All reports I've seen mention that the driver works fine if compiled as a > module. You may > want to try that. For this reason I also don't believe the problem is the > any of the emu10k1 > source files (which you diff'ed), unfortunately I haven't had much > time/means to test this > since I'm without a home PC and a SBLive. Hi Rui, this is unfortunately not true as I posted lately on emu10k1-devel. If compiled as a module /dev/dsp and /dev/audio do _no_ work, but /dev/dsp1 and /dev/audio1 do. Someone posted a little patch that makes it work again. Here it is: --- linux-2.2.18/drivers/sound/sound_core.c Sun Dec 17 11:11:46 2000 +++ linux-2.2.18-emubug/drivers/sound/sound_core.c Sun Dec 17 11:05:23 2000 @@ -436,7 +436,7 @@ cs4281_probe(); #endif #ifdef CONFIG_SOUND_EMU10K1 - init_emu10k1(); +/* init_emu10k1();*/ #endif #ifdef CONFIG_SOUND_YMFPCI ymf_probe(); Greetings, Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering & securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: emu10k1 broken in 2.2.18
[EMAIL PROTECTED] wrote: All reports I've seen mention that the driver works fine if compiled as a module. You may want to try that. For this reason I also don't believe the problem is the any of the emu10k1 source files (which you diff'ed), unfortunately I haven't had much time/means to test this since I'm without a home PC and a SBLive. Hi Rui, this is unfortunately not true as I posted lately on emu10k1-devel. If compiled as a module /dev/dsp and /dev/audio do _no_ work, but /dev/dsp1 and /dev/audio1 do. Someone posted a little patch that makes it work again. Here it is: --- linux-2.2.18/drivers/sound/sound_core.c Sun Dec 17 11:11:46 2000 +++ linux-2.2.18-emubug/drivers/sound/sound_core.c Sun Dec 17 11:05:23 2000 @@ -436,7 +436,7 @@ cs4281_probe(); #endif #ifdef CONFIG_SOUND_EMU10K1 - init_emu10k1(); +/* init_emu10k1();*/ #endif #ifdef CONFIG_SOUND_YMFPCI ymf_probe(); Greetings, Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: All INNOMINATE linux-list feeds are now killed...
Rik van Riel wrote: > > On Wed, 6 Dec 2000, Juri Haberland wrote: > > > We deeply regret this and apologize honestly, but also would > > like to resubscribe... > > Could you make it a one-way list this time? > These two-way lists always give horrible problems > and I would hate to killfile all of innominate ;) Allright, I think we have choice :-/ Sorry again... Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering & securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: All INNOMINATE linux-list feeds are now killed...
Matti Aarnio wrote: > > See attachment, these lists got removed: > > linux-alpha:[EMAIL PROTECTED] > linux-doc: [EMAIL PROTECTED] > linux-fsdevel: [EMAIL PROTECTED] > linux-kernel: [EMAIL PROTECTED] > linux-raid: [EMAIL PROTECTED] > linux-scsi: [EMAIL PROTECTED] > linux-smp: [EMAIL PROTECTED] > sparclinux: [EMAIL PROTECTED] > ultralinux: [EMAIL PROTECTED] > > Officially we don't approve bidirectional news<->list feeds, as those > are prone to this type of blunders of looping messages back to the list. We know that this is a difficult setup and we tested it thoroughly before using it, and it worked for a long time now. Unfortunately one of our admins updated the news server today without thinking of the implications :-( We deeply regret this and apologize honestly, but also would like to resubscribe... Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering & securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: All INNOMINATE linux-list feeds are now killed...
Matti Aarnio wrote: See attachment, these lists got removed: linux-alpha:[EMAIL PROTECTED] linux-doc: [EMAIL PROTECTED] linux-fsdevel: [EMAIL PROTECTED] linux-kernel: [EMAIL PROTECTED] linux-raid: [EMAIL PROTECTED] linux-scsi: [EMAIL PROTECTED] linux-smp: [EMAIL PROTECTED] sparclinux: [EMAIL PROTECTED] ultralinux: [EMAIL PROTECTED] Officially we don't approve bidirectional news-list feeds, as those are prone to this type of blunders of looping messages back to the list. We know that this is a difficult setup and we tested it thoroughly before using it, and it worked for a long time now. Unfortunately one of our admins updated the news server today without thinking of the implications :-( We deeply regret this and apologize honestly, but also would like to resubscribe... Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: All INNOMINATE linux-list feeds are now killed...
Rik van Riel wrote: On Wed, 6 Dec 2000, Juri Haberland wrote: We deeply regret this and apologize honestly, but also would like to resubscribe... Could you make it a one-way list this time? These two-way lists always give horrible problems and I would hate to killfile all of innominate ;) Allright, I think we have choice :-/ Sorry again... Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: Kernel 2.2.17, makefile bug
Gunter Königsmann wrote: > > Hello, there! > > Everything works just fine, but > > 'make bzlilo' > > compiles the kernel, and runs lilo, but it fails to copy it to > /boot/vmlinuz before that. Look in /. If you want bzlilo to copy your kernel image to boot uncomment the line #export INSTALL_PATH=/boot in /usr/src/linux/Makefile. Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering & securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: Kernel 2.2.17, makefile bug
Gunter Königsmann wrote: Hello, there! Everything works just fine, but 'make bzlilo' compiles the kernel, and runs lilo, but it fails to copy it to /boot/vmlinuz before that. Look in /. If you want bzlilo to copy your kernel image to boot uncomment the line #export INSTALL_PATH=/boot in /usr/src/linux/Makefile. Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering securitythe linux architects tel: +49-30-308806-45 fax: -77http://www.innominate.com - 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: Swapping over NFS in Linux 2.4?
Rik van Riel wrote: > > On Wed, 15 Nov 2000, Andreas Osterburg wrote: > > > Because I set up a diskless Linux-workstation, I want to swap > > over NFS. For this purpose I found only patches for "older" > > Linux-versions (2.0, 2.1, 2.2?). > > > Does anyone know wheter there are patches for 2.4 or does anyone > > know another solution for this problem? > > 1. you can swap over NBD > 2. if you point me to the swap-over-nfs patches you >have found, I can try to make them work on 2.4 ;) > > [I have some interest in making swap-over-nfs work and > most of the other VM things in 2.4 are already pretty > stable ... at the moment stability is more important > than extra performance tricks to me] There was a patch recently posted on the nfs mailing list by Tom Dyas from VAlinux. It is against 2.2.17 with the nfs patches by Trond Myklebust and Dave Higgen. The post (including the patch) can be found here: http://marc.theaimsgroup.com/?l=linux-nfs=97157102825580=2 Juri - 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: [BUG] Hard lockup using emu10k1-based sound card
Rui Sousa wrote: > > On Mon, 13 Nov 2000, Willis L. Sarka wrote: > > > I get a hard lockup when trying to play a mp3 with XMMS; > > Sound Blaster Live card. The first second loops, and I lose all > > connectivity to the machine; I can't ping it, can't to a an Alt-Sysq, > > nothing. > > Is this when you try to play something for the first time or > it just happens sometimes? > > > Details: > > > > running RedHat 7.0 > > using kernel 2.4.0-test11pre4 > > emu10k1 compiled as a module > > system is a Dell Dimension 4100 (815e based, 512mb ram, 3com 3c905c cardA) > > > > I'll try to compile in soundcore and emu10k1 into the kernel, foregoing > > any modules and see if that helps. I will also revert back to > > 2.4.0-test10 as well just to test. > > Yes, it would be good to know when the problems started. > > > If anyone needs further information, > > let me know. Well, just as a note: I'm using the same (software-) setup as above, only difference is that the emu10k1 driver is compiled into the kernel and I have no problems with xmms whatsoever. Juri - 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: [BUG] Hard lockup using emu10k1-based sound card
Rui Sousa wrote: On Mon, 13 Nov 2000, Willis L. Sarka wrote: I get a hard lockup when trying to play a mp3 with XMMS; Sound Blaster Live card. The first second loops, and I lose all connectivity to the machine; I can't ping it, can't to a an Alt-Sysq, nothing. Is this when you try to play something for the first time or it just happens sometimes? Details: running RedHat 7.0 using kernel 2.4.0-test11pre4 emu10k1 compiled as a module system is a Dell Dimension 4100 (815e based, 512mb ram, 3com 3c905c cardA) I'll try to compile in soundcore and emu10k1 into the kernel, foregoing any modules and see if that helps. I will also revert back to 2.4.0-test10 as well just to test. Yes, it would be good to know when the problems started. If anyone needs further information, let me know. Well, just as a note: I'm using the same (software-) setup as above, only difference is that the emu10k1 driver is compiled into the kernel and I have no problems with xmms whatsoever. Juri - 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: Quota fixes and a few questions
"Stephen C. Tweedie" wrote: > > Hi, > > On Thu, Oct 19, 2000 at 07:03:54PM +0200, Jan Kara wrote: > > > > > I stumbled into another problem: > > > When using ext3 with quotas the kjournald process stops responding and > > > stays in DW state when the filesystem gets under heavy load. It is easy > > > to reproduce: > > > Just extract two or three larger tar.gz files at the same time to a ext3 > > > filesystem with activated quotas... > > Which ext3 version, exactly? 0.0.2f had quota problems because ext3 > wasn't doing quota writethrough, so that inode cleaning could force > out random dirty quotas at any point. 0.0.3b should fix that. If it > doesn't, I'll try to reproduce it here. Hi Stephen, unfortunately 0.0.3b has the same problem. I tried it with a stock 2.2.17 kernel + NFS patches + ext3-0.0.3b and the quota rpm you included. Extracting two larger tar.gz files hits the deadlock reliably. Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering & security networking people phone: +49-30-308806-45 fax: -77http://innominate.de - 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: Quota fixes and a few questions
"Stephen C. Tweedie" wrote: Hi, On Thu, Oct 19, 2000 at 07:03:54PM +0200, Jan Kara wrote: I stumbled into another problem: When using ext3 with quotas the kjournald process stops responding and stays in DW state when the filesystem gets under heavy load. It is easy to reproduce: Just extract two or three larger tar.gz files at the same time to a ext3 filesystem with activated quotas... Which ext3 version, exactly? 0.0.2f had quota problems because ext3 wasn't doing quota writethrough, so that inode cleaning could force out random dirty quotas at any point. 0.0.3b should fix that. If it doesn't, I'll try to reproduce it here. Hi Stephen, unfortunately 0.0.3b has the same problem. I tried it with a stock 2.2.17 kernel + NFS patches + ext3-0.0.3b and the quota rpm you included. Extracting two larger tar.gz files hits the deadlock reliably. Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering security networking people phone: +49-30-308806-45 fax: -77http://innominate.de - 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: Quota fixes and a few questions
"Stephen C. Tweedie" wrote: > > Hi, > > On Thu, Oct 19, 2000 at 07:03:54PM +0200, Jan Kara wrote: > > > > > I stumbled into another problem: > > > When using ext3 with quotas the kjournald process stops responding and > > > stays in DW state when the filesystem gets under heavy load. It is easy > > > to reproduce: > > > Just extract two or three larger tar.gz files at the same time to a ext3 > > > filesystem with activated quotas... > > Which ext3 version, exactly? 0.0.2f had quota problems because ext3 > wasn't doing quota writethrough, so that inode cleaning could force > out random dirty quotas at any point. 0.0.3b should fix that. If it > doesn't, I'll try to reproduce it here. As I wrote in my original mail I used 0.0.2f. Is there a version called 0.0.3 yet and if so where can I find it? In ftp.uk.linux.org (which is currently not reachable as well as vger.kernel.org) I found only 0.0.2f. I must admit that I didn't look into the folders "test" and "test-dontuse". Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering & security networking people phone: +49-30-308806-45 fax: -77http://innominate.de - 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: Quota fixes and a few questions
"Stephen C. Tweedie" wrote: Hi, On Thu, Oct 19, 2000 at 07:03:54PM +0200, Jan Kara wrote: I stumbled into another problem: When using ext3 with quotas the kjournald process stops responding and stays in DW state when the filesystem gets under heavy load. It is easy to reproduce: Just extract two or three larger tar.gz files at the same time to a ext3 filesystem with activated quotas... Which ext3 version, exactly? 0.0.2f had quota problems because ext3 wasn't doing quota writethrough, so that inode cleaning could force out random dirty quotas at any point. 0.0.3b should fix that. If it doesn't, I'll try to reproduce it here. As I wrote in my original mail I used 0.0.2f. Is there a version called 0.0.3 yet and if so where can I find it? In ftp.uk.linux.org (which is currently not reachable as well as vger.kernel.org) I found only 0.0.2f. I must admit that I didn't look into the folders "test" and "test-dontuse". Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering security networking people phone: +49-30-308806-45 fax: -77http://innominate.de - 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: Quota fixes and a few questions
Juri Haberland wrote: > > "Stephen C. Tweedie" wrote: > > > > Hi Jan, > > > > On Wed, Sep 27, 2000 at 02:56:20PM +0200, Jan Kara wrote: > > > > > > So I've been thinking about fixes in quota (and also writing some parts). > > > > While we're at it, I've attached a patch which I was sent which simply > > teaches quota about ext3 as a valid fs type in fstab. It appears to > > work fine for me --- let me know if you want me to validate a new > > quotautils on ext3. > > Hi Stephen, > > actually using quotacheck with these patches on an ext3 partition > results in: > quotacheck: error while opening /dev/sda3 (which is the file system in > question) > > Just using the first to (sub-)patches works for me. Hi again, I stumbled into another problem: When using ext3 with quotas the kjournald process stops responding and stays in DW state when the filesystem gets under heavy load. It is easy to reproduce: Just extract two or three larger tar.gz files at the same time to a ext3 filesystem with activated quotas... Unfortunately there's nothing in the logs :-( Some general system infos: reproduced on two different systems, one UP, one SMP both kernel 2.2.17 + NFS-patches + ext3-0.0.2f journal size 20MBytes Any idea? Greetings, Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering & security networking people phone: +49-30-308806-45 fax: -77http://innominate.de - 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: Quota fixes and a few questions
Juri Haberland wrote: "Stephen C. Tweedie" wrote: Hi Jan, On Wed, Sep 27, 2000 at 02:56:20PM +0200, Jan Kara wrote: So I've been thinking about fixes in quota (and also writing some parts). While we're at it, I've attached a patch which I was sent which simply teaches quota about ext3 as a valid fs type in fstab. It appears to work fine for me --- let me know if you want me to validate a new quotautils on ext3. Hi Stephen, actually using quotacheck with these patches on an ext3 partition results in: quotacheck: error while opening /dev/sda3 (which is the file system in question) Just using the first to (sub-)patches works for me. Hi again, I stumbled into another problem: When using ext3 with quotas the kjournald process stops responding and stays in DW state when the filesystem gets under heavy load. It is easy to reproduce: Just extract two or three larger tar.gz files at the same time to a ext3 filesystem with activated quotas... Unfortunately there's nothing in the logs :-( Some general system infos: reproduced on two different systems, one UP, one SMP both kernel 2.2.17 + NFS-patches + ext3-0.0.2f journal size 20MBytes Any idea? Greetings, Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering security networking people phone: +49-30-308806-45 fax: -77http://innominate.de - 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: Quota fixes and a few questions
"Stephen C. Tweedie" wrote: > > Hi Jan, > > On Wed, Sep 27, 2000 at 02:56:20PM +0200, Jan Kara wrote: > > > > So I've been thinking about fixes in quota (and also writing some parts). > > While we're at it, I've attached a patch which I was sent which simply > teaches quota about ext3 as a valid fs type in fstab. It appears to > work fine for me --- let me know if you want me to validate a new > quotautils on ext3. Hi Stephen, actually using quotacheck with these patches on an ext3 partition results in: quotacheck: error while opening /dev/sda3 (which is the file system in question) Just using the first to (sub-)patches works for me. Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering & security networking people phone: +49-30-308806-45 fax: -77http://innominate.de - 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: Quota fixes and a few questions
"Stephen C. Tweedie" wrote: Hi Jan, On Wed, Sep 27, 2000 at 02:56:20PM +0200, Jan Kara wrote: So I've been thinking about fixes in quota (and also writing some parts). While we're at it, I've attached a patch which I was sent which simply teaches quota about ext3 as a valid fs type in fstab. It appears to work fine for me --- let me know if you want me to validate a new quotautils on ext3. Hi Stephen, actually using quotacheck with these patches on an ext3 partition results in: quotacheck: error while opening /dev/sda3 (which is the file system in question) Just using the first to (sub-)patches works for me. Juri -- [EMAIL PROTECTED] system engineer innominate AG clustering security networking people phone: +49-30-308806-45 fax: -77http://innominate.de - 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/
