Re: Off-Topic (or maybe on-topic)
David Weinehall wrote: > > On Fri, Oct 27, 2000 at 04:05:50PM +0300, Petko Manolov wrote: > > David Weinehall wrote: > > > > > > You're VERY wrong here. St. Petersburg was the name before the Soviet > > > Union was formed and Russia marched into the Baltics. When the takeover > > > was made, the city was renamed Leningrad (after V.I. Lenin). When the > > > Soviet Union finally fell to pieces and the Baltics retained their freedom, > > > St. Petersburg retained its old name, which it got (if I'm not all wrong) > > > from Peter the Great. > > > > > > AFAIK Tigran is born in the Soviet Union and i thing he knows > > the history of his own country better ;-) > > Uhmmm. You known, being born in the Soviet Union (not a country in its > strictest sense), doesn't necessarily mean you know its history. And > considering that the span of the SSSR was quite enormous... > > Anyhow: > > The city was originally called Nyen and was formed by Swedes. 1703, > Peter the Great invaded the city, and 1712 the city became the capital > of Russia, named St. Petersburg. The name remained St. Petersburg until > 1914, when it was renamed Petrograd. 1918, Moscow was made the capital > of Russia, and 1924 the city got renamed again, this time to Leningrad. > > > Anyway, i am bulgarian and i also am used to call St. Petersburg > > Leningrad ;-)) > > Well, it's time for me, as a Swede, to begin calling it Nyen?! > > Oh, let's end this silly debate. I'm getting sorry I even brought it > up. Hi, but since you did, :) I will insist it is St. Petersburg :) Art. - 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/
i815e related
Hi, Our company is going to purchase some hardware to run Linux workstations. We're looking forward into getting i815e based ASUS motherboards, and I will be really glad if you could help me figure out the following hardware support questions I couldn't figure myself. I've searched the LKML archive and Intel and few other sites, but didn't find enough straightforward answers concerning the more/less complete Linux support of ASUS CUSL2-M (i815e) motherboard, (http://www.asus.com.tw/products/motherboard/pentiumpro/cusl2-m/spec.html) Here are the things: Is the 82801BA Contoller Hub (ICH2) supported (would I get ATA-100 working)? Searching through drivers/pci/pci.ids (test9-pre7), I found 82801AB (ICH0?) only. Is AD1881A (AC'97 audio) codec supported? There's also onboard 3C905C NIC ASIC, would that work with 3C905 driver? Thanks a lot, Art. - 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: i815e related
Alan Cox wrote: > > Is AD1881A (AC'97 audio) codec supported? > > Sort of - it mostly works nowdays but mic recording is unsupported still. > Its solid in 2.2.18pre so should be solid in 2.4.0test9 Ok, thanks, One more thing I'm concerned about (which is not really kernel related), does the sound processing with AC'97 interface have any impact on overall system perfomance in comparison to PCI cards sound processing? Art. - 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/
filesystem for initrd
Hi, I'm in the process of creating a custom "system partition" for out Linux servers, which is actually an initial ramdisk, coming from hd or network on boot to load necessary drivers and perform important checks before the real filesystems get mounted, and I did not find any info on what filesystems can I use for initrd, are there any restrictions? Mostly interested in cramfs, due to it's compression. Could anybody help me work this out or point to the right place for more info? Thanks a lot, Art. - 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/
pivot_root & linuxrc problem
Hi, may be thats a bug, or I'm doing something really wrong :) from Documentation/initrd.txt: "# cd /new-root # mkdir initrd # pivot_root . initrd Now, the linuxrc process may still access the old root via its executable, shared libraries, standard input/output/error, and its current root directory. All these references are dropped by the following command: # exec chroot . what-follows dev/console 2>&1 Where what-follows is a program under the new root, e.g. /sbin/init" How can I "exec /sbin/init" from "/linuxrc", whatever it is, if "linuxrc" does not get PID=1? Actually, why does NOT "linuxrc" get PID=1? A task list after booting with "root=/dev/rd/0" and "init=/linuxurc", where "linuxrc" is simply "bash", shows that: "swapper" got PID=1, next come other kernel threads with a parent PID=1, and "linuxrc" got PID=7 and a parent PID=1. "init" sees it does not have PID=1 and simply bails out, next happens this: "Note: if linuxrc or any program exec'ed from it terminates for some reason, the old change_root mechanism is invoked (see section "Obsolete root change mechanism")." I probably misunderstand something here, but could you please help? In summary: What is "swapper" and why does it get PID=1 and "linuxrc" does not? If it is supposed to be that way, how do I "exec /sbin/init" from "linuxrc" then? Also why "/linuxrc" is hardcoded in init/main.c, so telling kernel "root=/dev/rd/0 init=/sbin/whatever" does still invoke "/linuxrc"? Thanks a lot, Art. - 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: pivot_root & linuxrc problem
Mike Galbraith wrote: > > Aha.. so that's it. I've never been able to get /linuxrc to execute > automagically. I wonder why /linuxrc executes on Art's system, but > not on mine. I can call it whatever I want and it doesn't run unless > I explicitly start it with init=whatever. > > If it does execute though, that explains init complaining.. pid is > going to be whatever comes after the last thread started (would be > 8 here). It looks like you're only supposed to do setup things in > magic filename /linuxrc and not exec /sbin/init from there. > > In any case, it looks like renaming linuxrc to whatever.sh and booting > with init=/whatever.sh instead will likely make init happy. > > -Mike > > Thank you for your answers, Mike and Russell. They made me sure something weird going on with my setup. And I think a have figured the problem. I was using etherboot to boot the kernel and initrd. I should have told you that before, and I'm sorry I did not. Bootin' localy, with lilo, seems to solve the "PID problem". I guess that's more of mknbi from etherboot question than kernel-related... I have to check more in depth the etherboot documenation/sources. Art. - 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/
union mounts WAS: pivot_root & linuxrc problem
Hi, One more thing I was wondering about, is the pivot_root call the *final* implementation of the "root filesystem changer" for kernle 2.4.*? I've read about a new VFS extension, that allows multiple filesystems to be stacked at a single mount point. As I have understood it allows to *just* mount a new filesystem over the old one and unmount the old one. Is it finally going to come instead of pivot_root? The reason I'm so interested is the opportunity to freely change root, for example, from initrd to harddrive, from harddrive to nfs-mount and so on.. For now I think (am I right?) I can modify sysV init with pivot_root and chroot calls, so that before going to runlevel 1 it will pivot_root & chroot to some ramdisk for example, and for runlevel 2 to nfs-mount. Just examples. But what if I want to change the other partitions like /usr? Like if workstation does not boot, because of harddrive messup, I don't make user wait until it get fixed, but mount all partitions over nfs (identical to those on harddrive), let the user do his work, and after localdrive fixup just mount the *real* partitions over the nfs-mounted, and unmount nfs, all *transparently* to user. In my understanding thats what a new VFS extension should offer. Am I right? If so, does anybody know when it is planned to implement that if its not yet? I've seen new options for "mount" like --bind, --over, but didn't really get how they work or are they implemented at all. Would be glad if anybody could help me with this question. Thanks, Art. - 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/
gcc-2.95.3 release
Hi, gcc-2.95.3 has just been released. Could it be used for kernel compilation, or still better stick with gcc-2.91.66 for "absolute stability"? Thanks, Art. - 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/
[2.4.3-pre4] comparing eepro100 & e100
Hi, I'm setting up a new server with Intel 82559 LOM (733470-066), this is ASUS CUR-DLS. While testing the NIC performance with eepro100 driver, I was getting those famous "card reports no resources" and "too much work in interrupt". The perfomance test was actually a "ping -f -s 65507" from another host (both hosts are in 100baseTX-FD IBM switch) and some other program doing basicly the same. I played around with module parameters but had no luck. So I've had to try the Intel supplied driver *e100-1.5.5a*. ftp://download.intel.com/df-support/2250/eng/e100-1.5.5a.tar.gz And it works just rock&solid - no problems at all. - 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/
"device or resource busy" - why??
Hi, could you please help me figure out why is that happenning: After succesfull pivot_root & chroot from initrd, I *do* unmount /initrd, (no directories, no mapped files...), but I can *not* free the memory: "blockdev --flushbufs /dev/rd/0" returns "BLKFLSBUF: Device or resource busy". --- What is keeping it busy? I got really stuck with that. This is linux-2.4.3-pre6 SMP with devfs and blockdev from util-linux-2.11a and cramfs on initrd. I have the following processes running at that moment: - 1 0 /bin/bash 2 1 [keventd] 3 1 [kswapd] 4 1 [kreclaimd] 5 1 [bdflush] 6 1 [kupdated] 137 1 [mdrecoveryd] 160 1 [kreiserfsd] - And the following modules loaded: - reiserfs raid0 md sd_mod sym53c8xx scsi_mod - I thought I've checked everything I could, but with no luck. Could that be a cramfs issue? Thank you, Art. - 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/
[SoftwareRAID in 2.4.1] md_import_device() returned -22
Hi, Could anybody please help me to resolve why this error is returned? (md_import_device() returned -22) I'm trying to setup software RAID0 on Asus CUR-DLS (dual channel ULTRA2 SCSI - sym53c896). kernel is pure 2.4.1(SMP), with devfs, sym53c8xx and raid0 support linked in. raidtools are 19990824-0.90 from kernel.org. Here is /etc/raidtab: - raiddev /dev/md/0 raid-level 0 persistent-superblock 1 chunk-size 16 nr-raid-disks 2 device /dev/scsi/host0/bus0/target0/lun0/part1 raid-disk 0 device /dev/scsi/host0/bus0/target1/lun0/part1 raid-disk 1 #same bus because I have only one cable right now :) - And here is what I got with "mkraid /dev/md/0": - handling MD device /dev/md/0 analyzing super-block disk 0: /dev/scsi/host0/bus0/target0/lun0/part1, 17921008kB, raid superblock at 17920896kB disk 1: /dev/scsi/host0/bus0/target1/lun0/part1, 17921008kB, raid superblock at 17920896kB mkraid: aborted, see the syslog and /proc/mdstat for potential clues. -- And syslog says: modprobe: modprobe: Can't locate module block-major-8 kernel: md: could not lock scsi/host0/bus0/target0/lun0/part1, zero-size? Marking faulty. kernel: md: error, md_import_device() returned -22 --- Is that "modprobe" line causing problem? But I have compiled scsi driver in... Or is that a devfs issue or am I doing anything wrong? I would really be glad to get some pointers to the answer, since I can't figure that out myself. Thanks a lot, Art. - 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/
[2.4.1] "DEVFS+RAID" not working
Hi, as I've posted before in [SoftwareRAID in 2.4.1], I wasn't able to get RAID0 working with devfs enabled and mounted on /dev. The problem had gone after I passed devfs=nomount, and used old device names for configuring/starting raid: /dev/md0 instead of /dev/md/0 /dev/sda1 instead of /dev/scsi/host0/bus0/target0/lun0/part1 and so on. Why? Is that the way it is supposed to be with raid? Why can't I just use devfs naming scheme, and mount it on boot? For some reason I wouldn't want those old device files under /dev. Thanks in advance, Art. - 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: Linux support for Microsoft dynamic disks?
On Sunday 13 May 2001 03:15 pm, mirabilos wrote: > > I had (on a 2G disk) a NTFS, a FAT and some Linux partitions. It even > refused > to convert to dynamic disk. When it finally did, my Linux partitions > vanished. > You need this support to even be able to use linux on that disk... btw > . It is actiually possible to have both Linux and Windows 2000/Windows XP with dynamic disk on the same hard drive for now. The thing is you have first to install Windows XP, leaving required space for the Linux install, and convert the drive to dynamic disk. When it is sucessfully converted you can reboot from linux floppy and "resize" the last partition on the disk to the place where the free space actually begins. Now it's possible to create some partitions here to install Linux. The point is Windows still thinks there is an unpartioned space there, where you just put your Linux distro :) But thats not the option anyway, and recognising dynamic disks would be a much better solution :). Art. - 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 support for Microsoft dynamic disks?
On Sunday 13 May 2001 02:46 pm, Guest section DW wrote: > On Sat, May 12, 2001 at 08:34:45PM -0600, Jeff V. Merkey wrote: > > What is your specific question? > > Well, my specific question would be: enough information to support > mounting filesystems that live on a dynamic disk. > > Andries Understanding the layout of a dynamic disk is just a part of the problem as far as I can see it. What if I have two (three,four) dynamic disks with volumes organized into a software stripe (raid0) under Windows? There must be an implementation of MS' software raid in the linux kernel in order to access that "striped filesystem" under linux, I'm I right? Art. - 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/
