Re: [Cooker] kernel and XFS
Because SGI's XFS project team only released patches for 2.4.21 last week. They still need to be integrated into Mandrake's kernel. Alan - Original Message - From: Gilles Mocellin [EMAIL PROTECTED] To: Mandrake Cooker [EMAIL PROTECTED] Sent: Saturday, January 18, 2003 6:39 PM Subject: [Cooker] kernel and XFS Why does the 2.4.21 kernels don't have xfs compiled in ?
Re: [Cooker] EVMS support in near futur ?
- Original Message - From: Gilles Mocellin [EMAIL PROTECTED] To: Mandrake Cooker [EMAIL PROTECTED] Sent: Saturday, November 30, 2002 6:05 PM Subject: [Cooker] EVMS support in near futur ? Is EVMS (Enterprise Volume Management System from IBM) support planned in Mandrake kernel ? Unlikely. EVMS did not make it into the 2.5 development kernel fetaure freeze, while LVM2 did. The EVMS team subsequently decided to terminate development of the EVMS kernel patches (although they would continue to support them for the 2.4 stable kernel) and to port their management tools to support LVM2. So the days of EVMS are numbered. In some respects its a shame - I thought EVMS was a better solution since it tightly integrated logical volumes and software RAID. Howver as I understand the EVMS kernel patch was *huge*, and duplicated existing functionality, so I guess Linus' descision was understandable. Alan
Re: [Cooker] supermount or alternate fs mounter ?
The problem is that AFAIK other auto mounters are user-space applications that work by periodically checking to see if a mount point is no longer used, and if so then unmounting it. Typically this check occurs at 30 second intervals (although I understand that most allow you to configure this timeout). What this means in a practical sense is that your CD (as an example) would not be unmounted until 30 seconds after you finish using it. Supermount OTOH is a kernel utility that auomatically mounts the device when you access its mount point, and unmounts as soon as you've finished using it. It basically does this by hooking into various kernel routines responsible for managing the internal file descriptor tables. The problem with supermount is that these hooks are spread over a number of places and they often have very subtle impacts on the rest of the kernel (impacts that seem to change with each new kernel version) that tends to screw things up. A significant PITA. It would help if Linus integrated supermount into the kernel, however I understand that he is not happy with the necessary patches - given the problems which Mandrake has had I don't blame him. I'm not aware of anything else that does the same sort of job as supermount, but I think someone else posted something a couple of days ago. I'll need to have a look in the list archives to refresh my memory. - Original Message - From: Eric Fernandez [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, October 29, 2002 11:28 AM Subject: Re: [Cooker] supermount or alternate fs mounter ? Robert Denier wrote: You may want to check this but I think supermount -i disable will magically change fstab to get rid of supermount options. (Remember if you mess up fstab your machine may not boot.) Clearly you now have to mount everything by hand, but considering I use a cd at most every few days, it really doesn't bother me, although thats just my case. I know that you can disable supermount. But my point was for the future updates/9.1. Mandrake distribution needs an auto-mounter, especially for newbies and people who do not want to have to mount manually. Now the question is : since there are alternatives to supermount, like autofs or AMD (the BSD automounter), why not replace the problematic supermount by another solution ? Eric
Re: [Cooker] devfsd.conf
- Original Message - From: Peter Polman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, October 01, 2002 6:38 AM Subject: Re: [Cooker] devfsd.conf On Monday 30 Sep 2002 2:04 pm, Biagio Lucini wrote: On Mon, 30 Sep 2002 [EMAIL PROTECTED] wrote: Now that 9.0 is out ... Minor spelling corrections in English version. Initialize not initialise Minimize not minimise Maximize not maximise Did you say English or American? :-) Biagio Hopefully English ... We Canadians tend to speak a little of both though! I have seen initialisation and initialization but not initialise (I know it doesn't make sense, but ...) I have never seen minimise or maximise. Are these supposed to be English or American spellings? English spellings tend to use -ise, American -ize. However the Oxford English Dictionary does allow some -ize's as an alternative.
Re: [Cooker] devfsd.conf
- Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 30, 2002 7:13 PM Subject: [Cooker] devfsd.conf Line 11 in init.d/devfsd refers to devsfsd.config shouldn't that be devfsd.conf ? Now that 9.0 is out ... Minor spelling corrections in English version. Initialize not initialise Minimize not minimise Maximize not maximise The spellings are wrong if (and only if) you are American. Otherwise they are OK.
Re: [Cooker] LM9.0: Setting up LVM
The problem with having / on an LVM volume set is that LILO can't handle it. Take this scenario as an example: mt LVM volume set spans 3 disks, that means a root file system could potentially be on any of those disks. LILO would have to analyse the LVM volume set and work it out - a lot of work for a boot loader. Bear in mind that LILO does not strictly support software RAID root partitions (although you can get around the problem for RAID-1 only). Glad you sorted your problem out anyway. - Original Message - From: Frederic Soulier [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 27, 2002 7:33 PM Subject: Re: [Cooker] LM9.0: Setting up LVM Well, I succeeded today setting Up LM9.0 with LVM. I believe the pbm was that I used Linux_extended (0x85) partition type instead of plain Extended. I have now the following setup: SWAP hda1 Primary /boot hda5 Extended Ext2 / hda6 Extended ReiserFS LVM Extended /usr ReiserFS /home ReiserFS /opt ReiserFS /var ReiserFS /tmp ReiserFS and it's all working fine. Just 2 comments: - it would be nice to have the option to have / in the LV as well - when drakdisk starts spitting out errors it's hard to make it behave again without restarting... maybe the error handling could be frendlier :) Otherwise, LM9.0 looks really good, it feels definitely faster than 8.2 I'm going to set it up on 4 boxes so I guess I'll have some more to report. Thanks Mandrake. /Fred On Fri, 2002-09-27 at 19:09, Alan Hughes wrote: I'm surpised! I installed 9.0 this morning with / as a normal ReiserFS partition, a swap partition and an LVM partition that spanned the remainder of the disk plus two other disks. I have the same set of partitions on my LVM volume (although the sizes are different - much larger disks) and had no problems. I only used the installer. However at one time I did have a problem with LVM (must have been about Beta 3 or 4) which Pixel though he had fixed. It was OK for me afterwards, but maybe I did'nt test it well enough. - Original Message - From: Frederic Soulier [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, September 26, 2002 8:32 PM Subject: [Cooker] LM9.0: Setting up LVM Hi I have been trying to setup LM9.0 using LVM with no success so far... The box is a vanilla Dell 4100 with a 20Gb HD, 256MB Ram P3 933MHz The first pbm is that / cannot be part of the LVM... (had no pbm having / part of the LVM on RH (null) and Gentoo. Scenario A -- 1) ran fdisk /dev/hda from tomsrtbt and created - a Linux extended partition (0x85) containing: swap700Mb /boot30Mb Linux native (0x82) / 250Mb Linux native (0x82) LVM remaining of space (0x8e) 2) started the LM installer 3) during the partitioning step: - changed the / type (0x82) to ReiserFS - selected the LVM Add to LVM and named it lv1 (a new tab lv1 appeared alongside hda) - selected the lv1 tab - created the following for the LVM: - /usr5500Mb ReiserFS - /home 3500Mb ReiserFS - /opt2500Mb ReiserFS - /var4200Mb ReiserFS - /tmp1200Mb ReiserFS - clicked done - Selected all partitions to be formatted incl. extra checks for bad blocks for the swap and /boot - made a prayer and clicked ok after a while I get an error that /dev/hda7 (/ in this scenario) cannot be formatted... Tried to go back and clear all the partitions to start again and I got error msgs lvremove failed (or something equivalent). Tried to backtrack evenmore until drakdisk was up shit creek. Rebooted under tomsrtbt and cleaned up all partitions then tried again using only drakdisk from a clean disk, the bloody thing would not even create the LVM (0x8e) partition... Tried again with partioning from fdisk (tomsrtbt) and using same partitioning as above with linux native type instead of ReiserFS, no more success... So basically, If someone had success setting up LVM in LM9.0 using only drakdisk or a combination of fdisk/drakdisk then I'd like to hear from you :) I cannot believe it's not working so maybe I'm not using drakdisk correctly. I've got a laptop using LVM from a RH (null) install and another box using LVM from a Gentoo install (this box has 3 HDs) and both installation worked 1st time. What is wrong with drakdisk or with me ;) Ideas, suggestions much appreciated. Thanks. /Fred
Re: [Cooker] LM9.0: Setting up LVM
I'm surpised! I installed 9.0 this morning with / as a normal ReiserFS partition, a swap partition and an LVM partition that spanned the remainder of the disk plus two other disks. I have the same set of partitions on my LVM volume (although the sizes are different - much larger disks) and had no problems. I only used the installer. However at one time I did have a problem with LVM (must have been about Beta 3 or 4) which Pixel though he had fixed. It was OK for me afterwards, but maybe I did'nt test it well enough. - Original Message - From: Frederic Soulier [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, September 26, 2002 8:32 PM Subject: [Cooker] LM9.0: Setting up LVM Hi I have been trying to setup LM9.0 using LVM with no success so far... The box is a vanilla Dell 4100 with a 20Gb HD, 256MB Ram P3 933MHz The first pbm is that / cannot be part of the LVM... (had no pbm having / part of the LVM on RH (null) and Gentoo. Scenario A -- 1) ran fdisk /dev/hda from tomsrtbt and created - a Linux extended partition (0x85) containing: swap700Mb /boot30Mb Linux native (0x82) / 250Mb Linux native (0x82) LVM remaining of space (0x8e) 2) started the LM installer 3) during the partitioning step: - changed the / type (0x82) to ReiserFS - selected the LVM Add to LVM and named it lv1 (a new tab lv1 appeared alongside hda) - selected the lv1 tab - created the following for the LVM: - /usr5500Mb ReiserFS - /home 3500Mb ReiserFS - /opt2500Mb ReiserFS - /var4200Mb ReiserFS - /tmp1200Mb ReiserFS - clicked done - Selected all partitions to be formatted incl. extra checks for bad blocks for the swap and /boot - made a prayer and clicked ok after a while I get an error that /dev/hda7 (/ in this scenario) cannot be formatted... Tried to go back and clear all the partitions to start again and I got error msgs lvremove failed (or something equivalent). Tried to backtrack evenmore until drakdisk was up shit creek. Rebooted under tomsrtbt and cleaned up all partitions then tried again using only drakdisk from a clean disk, the bloody thing would not even create the LVM (0x8e) partition... Tried again with partioning from fdisk (tomsrtbt) and using same partitioning as above with linux native type instead of ReiserFS, no more success... So basically, If someone had success setting up LVM in LM9.0 using only drakdisk or a combination of fdisk/drakdisk then I'd like to hear from you :) I cannot believe it's not working so maybe I'm not using drakdisk correctly. I've got a laptop using LVM from a RH (null) install and another box using LVM from a Gentoo install (this box has 3 HDs) and both installation worked 1st time. What is wrong with drakdisk or with me ;) Ideas, suggestions much appreciated. Thanks. /Fred
Re: [Cooker] [9.0] USB Problem
Further information, after a reboot the external hub and attached mouse was not detected at all. I had to disconnect and reconnect the mouse, at which point everything came to life. I seem to remember a similar problem being reported on RC2/RC3. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, September 26, 2002 9:20 AM Subject: [Cooker] [9.0] USB Problem Did a preliminary install of 9.0 last night (mostly to get a feel of things). Noticed that my USB mouse was not being detected on boot - its plugged into a hub, not directly into the back of my PC. When I had a look at dmesg, I spotted a line that compained that usbdevfs had invalid remount parameters (posting from work so I can't give you the precise message at the moment, I'll try to do that tonight). Solution was simple - I reset /etc/sysconfig/usb to load the USB modules early in the boot process. Mouse worked after that. However this still needs to be investigated. My machine is a dual P-III 1GHz, with the noapic argument set in the kerenl parameters (buggy BIOS). Other than that 9.0 is looking great!
Re: [Cooker] 9.0 and next
I think one positive point is that the Beta/RC cycle was much longer this time round, giving people a lot more time to find problems and report them. With 8.2 the Beta/RC cycle was very quick, so a lot of problems made it through to the final release that franckly should not have been there. Hopefully the greater care that was taken this time around should be reflected in a better quality release - watch this space for further comments. I've already seem some of the responses, can I add my voice to those saying that having multiple error reporting routes is not helpful. Personally I think the Cooker list is the best place for this sort of thing, particularly since many of the people who post here will also continue to play a role in-between releases. Continuity and continuous testing is the theme I'm trying to get at here. Another issue is feedback. If someone has gone to the trouble of reporting a bug then a simple acknowledgement can go a long way to keeping them motivated. In addition acknowledging help in the change logs would also be a good thing - I noticed Pixel doing this, but I can't remember anyone else doing so. Whether BugZilla should continue to be used I don't know - used properly it could be a powerful problem reporting and monitoring tool, but I don't think its been used properly by anyone (and that goes for the user community as well as Mandrake people). What is needed is discipline - the user community needs to be more careful reporting bugs, and Mandrake needs to use BugZilla to provide feedback w.r.t. problem status and solution. Can we get that sort of discipline? I don't know. Finally can I say that the impressions I've had of 9.0 indicate that Mandrake has done a tremendous job. As a software professional I am more than aware of the problems you can get on handling a project of that scale, the fact that you have achieved so much speaks very highly of everyone concerned. Early this year I was actually thinking of switching to another distro (due to the problems with 8.2), but you have gone a long way to renewing my confidence in Mandrake. Well done, now get some rest (and a large drink). Alan - Original Message - From: Warly [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 25, 2002 6:35 PM Subject: [Cooker] 9.0 and next 9.0 is (likely to be) finished. Thanks to you all for your precious help. During last 6 months period, and especially in the last beta period, some of you give some advice/critic/flame regarding Mandrakesoft development process. It is now the right time to debrief all this. Please comment on what you liked, disliked in the 9.0 building, testing and problem reporting process. I already collect on various mandrake IRC channels: * send a mail to the changelog disk when packages are removed with the reason * improve the cooker cooker FAQ pages, about cooker etiquette and everything when reporting a bug (http://www.mandrakelinux.com/en/cookerfaq.php3) * improved bugzilla to have a easy mail interaction system, and a more friendly interface. And to have a last known problems page. -- Warly
Re: [Cooker] RC3 Bugs (second try)
I'll give your suggestions a try, however as I said previously I'm going to wait for 9.0 to go gold. Alan - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, September 22, 2002 2:50 PM Subject: Re: [Cooker] RC3 Bugs (second try) On Sat, 21 Sep 2002, Alan Hughes wrote: I originally fiddled with the mixer settings, volume and just about everything else. Nothing worked, nada, just the big silence. Switching over to the audigy (sp?) driver (which I understand is OSS) and everything worked perfectly immediately. Assuming you use analog speakers on rear channel: Try again, use alsamixer or alsamixergui, mute the very last channel (analog output jack), increase Wave surround volume. Does it work now? Easier say: plug your speakers into front channel. Danny PS: the audigy driver is not really ment of a sblive, but will work. My box is a dual P-III running the SMP kernel, vanilla RC3 with the exception that I put the latest initscripts RPM on (USB problems as previously reported here). I plan some more fiddling, but not until after 9.0 goes gold - I've got some other things to do, including educating the wife on Linux so that she can start to teach people at work. Alan - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, September 21, 2002 1:26 PM Subject: Re: [Cooker] RC3 Bugs (second try) On Sat, 21 Sep 2002, Alan Hughes wrote: Sorted it out last night, although I use HardDrake to set the OSS driver. I think that ALSA just does not support SoundBlaster Live properly (along with I disagree, because it works fine for some other people. David may say it doesn't work but that is only because he gets artifacts on his specific systems. ALSA drivers work fine on most SBLives. But there are a few different kinds, and YMMV. Some people like ALSA better, because it supports more features and is the best maintained. I hope David will report the artifacts to alsa-devel, so they are fixed in the next version. Alan, it would be better to figure out why it was not working on your setup, because you did not really explain. If it was that you did not hear sone on your rear channel than it is a mixer configuration issue, which I hoped would be fixed, but you can always manually set your mixer correct. Danny
Re: [Cooker] RC3 Bugs (second try)
Sorted it out last night, although I use HardDrake to set the OSS driver. I think that ALSA just does not support SoundBlaster Live properly (along with some other sound cards from what I gather in some of the other messages). Other than that everything is looking OK, although I'm not using USB periphals at the moment. Alan - Original Message - From: David Walser [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 20, 2002 8:14 PM Subject: Re: [Cooker] RC3 Bugs (second try) Run draksound. I think RC3 still uses the problematic ALSA module by default, this still hasn't been fixed AFAIK. --- Alan Hughes [EMAIL PROTECTED] wrote: Yep, the new initscripts worked. Now just have to get my SOundBlaster Live working (correct module, worked in 8.2, not in RC3). __ Do you Yahoo!? New DSL Internet Access from SBC Yahoo! http://sbc.yahoo.com
Re: [Cooker] rc3 BIG bug : No USB at all
Try installing the latest initscripts package from Cooker - that appears to fix a lot of problems. - Original Message - From: Denis Bergeron [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, September 21, 2002 5:38 AM Subject: [Cooker] rc3 BIG bug : No USB at all I just install MDK9 RC3 on and ASUS k7m Athlon 650 + 512meg with inboard usb 1.1. Everything work fine turing install. I can choose the my usb mouse in the menu. I can install my usb printer. But once the computer restart, I can't use my mouse. I can't use my printer I don't have /dev/usbmouse I don't have nothing in /dev/usb/ I don't have nothing in /prod/bus/usb even if I have 1 usb joystick 1 usb mouse 1 usb printer 1 usb hub __ Lèche-vitrine ou lèche-écran ? magasinage.yahoo.ca
Re: [Cooker] VFS Inodes Busy / 9.0 BETA - Bug report / Installation
Messages also appear when using XFS or ReiserFS on an SMP system. - Original Message - From: Norman Carver [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 20, 2002 11:33 PM Subject: Re: [Cooker] VFS Inodes Busy / 9.0 BETA - Bug report / Installation I am also seeing these messages upon shutdown of RC3. They did not occur in RC2. Norm On Friday 20 September 2002 05:26 pm, you wrote: mandrakeexpert incident 32411 forwarded to cooker. when replying, please cc this email address: [EMAIL PROTECTED] quoted text below pakkie : 20/09 03:08 : Incident created Hi, I've installed MDK9rc3 (on a XFS filesystem). When I halt my system I always get the following message, which doesn't really sound healthy: VFS Inodes Busy: Self destruct in five seconds, Have a nice day -end quoted text-
Re: [Cooker] RC3 Bugs (second try)
I originally fiddled with the mixer settings, volume and just about everything else. Nothing worked, nada, just the big silence. Switching over to the audigy (sp?) driver (which I understand is OSS) and everything worked perfectly immediately. My box is a dual P-III running the SMP kernel, vanilla RC3 with the exception that I put the latest initscripts RPM on (USB problems as previously reported here). I plan some more fiddling, but not until after 9.0 goes gold - I've got some other things to do, including educating the wife on Linux so that she can start to teach people at work. Alan - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, September 21, 2002 1:26 PM Subject: Re: [Cooker] RC3 Bugs (second try) On Sat, 21 Sep 2002, Alan Hughes wrote: Sorted it out last night, although I use HardDrake to set the OSS driver. I think that ALSA just does not support SoundBlaster Live properly (along with I disagree, because it works fine for some other people. David may say it doesn't work but that is only because he gets artifacts on his specific systems. ALSA drivers work fine on most SBLives. But there are a few different kinds, and YMMV. Some people like ALSA better, because it supports more features and is the best maintained. I hope David will report the artifacts to alsa-devel, so they are fixed in the next version. Alan, it would be better to figure out why it was not working on your setup, because you did not really explain. If it was that you did not hear sone on your rear channel than it is a mixer configuration issue, which I hoped would be fixed, but you can always manually set your mixer correct. Danny
Re: [Cooker] RC3 Bugs (second try)
Thanks, I'm going to try initscripts 10 as soon as I've done a re-install. The problem with /usr is however a major headache - I never have /usr integrated with /, either at home or at work. I just hope this will be fixed for 9.0 final. For the moment I'm doing a re-install so that I can play with some of the options. The VFS message looks like the one I've seen, although I've never got a good look at it. The Have a nice day... bit sounds like a piece of kernel code however :-) Alan - Original Message - From: Götz Waschk [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 20, 2002 8:45 AM Subject: Re: [Cooker] RC3 Bugs (second try) Hi, I'd like to comment some of your problems. Am Freitag, 20. September 2002, 07:53:45 Uhr MET, schrieb [EMAIL PROTECTED]: 2. I reformatted partitions originally created for RC2. / is mounted from /dev/hda12 (ReiserFS), while /usr, /var, /tmp and /home are mounted from LVM partitions (XFS). mkfs.xfs reports that it could not find the lvdisplay command (see in ddebug.log). At the moment there are still problems with /usr on a separate partition. You could try to install again with /usr on the root partition. 3. On booting RC3 it reported an error in /etc/init.d/usb (line 1: eval not found). This is early on in the boot process, just after the host name is set, but before the LVM volumes are mounted (I think). This and your USB mouse problem relate to the fact mentioned above. The usb script requires a binary from /usr, but that partition in't mounted then. This has been fixed in initscripts 10mdk. 4. On shutting down the system I briefly saw a message in which the VFS seemed to say that some inode where still open. The system still shut down OK. Not sure what these messages meant, and they appeared and disappered so quickly I was not able to work out excatly what they said. I also had this problem, however I could identify the message: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day... That message is from fs/super.c I am not a kernel hacker, but I think some partition didn't umount successfully, maybe you could try to disable supermount and see if this helps. -- Götz Waschk master of computer science University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key -- Logout Fascism! --
Re: [Cooker] RC3 Bugs (second try)
Yep, the new initscripts worked. Now just have to get my SOundBlaster Live working (correct module, worked in 8.2, not in RC3). Alan - Original Message - From: Alan Hughes [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 20, 2002 7:32 PM Subject: Re: [Cooker] RC3 Bugs (second try) Thanks, I'm going to try initscripts 10 as soon as I've done a re-install. The problem with /usr is however a major headache - I never have /usr integrated with /, either at home or at work. I just hope this will be fixed for 9.0 final. For the moment I'm doing a re-install so that I can play with some of the options. The VFS message looks like the one I've seen, although I've never got a good look at it. The Have a nice day... bit sounds like a piece of kernel code however :-) Alan - Original Message - From: Götz Waschk [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 20, 2002 8:45 AM Subject: Re: [Cooker] RC3 Bugs (second try) Hi, I'd like to comment some of your problems. Am Freitag, 20. September 2002, 07:53:45 Uhr MET, schrieb [EMAIL PROTECTED]: 2. I reformatted partitions originally created for RC2. / is mounted from /dev/hda12 (ReiserFS), while /usr, /var, /tmp and /home are mounted from LVM partitions (XFS). mkfs.xfs reports that it could not find the lvdisplay command (see in ddebug.log). At the moment there are still problems with /usr on a separate partition. You could try to install again with /usr on the root partition. 3. On booting RC3 it reported an error in /etc/init.d/usb (line 1: eval not found). This is early on in the boot process, just after the host name is set, but before the LVM volumes are mounted (I think). This and your USB mouse problem relate to the fact mentioned above. The usb script requires a binary from /usr, but that partition in't mounted then. This has been fixed in initscripts 10mdk. 4. On shutting down the system I briefly saw a message in which the VFS seemed to say that some inode where still open. The system still shut down OK. Not sure what these messages meant, and they appeared and disappered so quickly I was not able to work out excatly what they said. I also had this problem, however I could identify the message: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day... That message is from fs/super.c I am not a kernel hacker, but I think some partition didn't umount successfully, maybe you could try to disable supermount and see if this helps. -- Götz Waschk master of computer science University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key -- Logout Fascism! --
Re: [Cooker] HPT372 raid controller not supported?
The problem with the RAID array being hosed when you create a file system has a simple explination. HPT raid controllers are normally termed WinRAID devices; they rely on specialised device drivers to provide the RAID functionality (as against true RAID controllers which use embedded software). On Linux the device drivers are provided by the ataraid and hptraid modules. The HPT RAID controllers store information on the RAID disks that describe the configuration of the RAID array. Because Highpoint designed the controllers for PCs, they assumed that Windows would be the only OS that they would have to worry about, and therefore put the RAID configuration information on disk sectors that are normally unused by MS file systems (FAT, NTFS, etc). However these sectors are typically used by Linux filesystems (ext2/3, JFS, ReiserFS, XFS), so when the file system is created on the RAID array it trashes the configuration information. Hence the complaints from the RAID BIOS. The ataraid and hptraid modules are really intended to allow you to access MS file systems on an existing RAID array, not to create your own file systems. I have a HPT-370 controller (basically the same as the 372, but only supports UDMA-100 not -133) and I've found that the best way to use it is to disable the RAID configuration (i.e. use it as a normal IDE controller) and use the Linux software raid (md) system. Its at least as fast as the ataraid/hptraid combination. Hope the above helps, even if it is long-winded. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 13, 2002 7:59 AM Subject: Re: [Cooker] HPT372 raid controller not supported? On Thursday 12 September 2002 03:33 am, Stéphane Teletchéa wrote: Due to no answer i my last message (sorry i couldn't go through the betas stages, the hardware is 4 days old), if flipped connectors (nappes IDE - please translate) 40/80, the harddrive, and finally found a pseudo-working configuration : I See the same errors if I dont use ide=nodma Before the hd in hdb was in hdg (reiserfs partitions) and produced the same errors messages, so i presume it is a not-yet supported chipset ? Actually I didnt catch if you had raid enabled or not, but the chipset seems to be supported, my bios version 2.31 reports 370/372 and the open source driver from www.highpoint-tech.com is the same for the 370 and 372. I can make partitions on the raid array during an install (ataraid.o and hptraid.o loaded) but for some reason the diskdrake writes the partition table to the drive in a way that hoses the Raid array. upon reboot HPT bios complains the raid array is broken and you have to re-create it and lose everything on the drive. After installing on a regular drive I can load ataraid and hptraid and access the partitions on the raid array, but it is choppy and slow. I can not use diskdrake. During an install the raid partitions show up as /dev/ataraid/d0p? which diskdrake likes, however when loading the modules in a running system the devices come up as /dev/ataraid/disc0/part? which diskdrake does not recognize, making a link from /dev/ataraid/disc0/part? to /dev/ataraid/d0p? lets diskdrake work. I had the /, /home, and swap on the raid0 array in 8.2 and it worked beautifully, so far the results in 9.0 are dissappointing, but at least built in support is there. Building support into the kernel and disabling the other ide stuff you dont need may take care of the sluugish response. But thrashing the raid array is a BAD thing :(
[Cooker] BUG: USB problem with EPOC D6VA motherboard, 9.0 Beta 4.
USB does not appear to work with the EPOC D6VA motherboard under Mandrake 9.0 Beta 4 using the SMP kernel. The USB chipset is detected correctly and the usb-uhci module seems to be happy with it, however devices attached to the USB port are not detected (there appears to be a timeout occuring). The usb-ohci module does not work with this chipset (unsupported). The usb module works but has the same problems. I've been testing using the USB hub built into my monitor (Iiyama VisionMaster Pro453). The hub is detected correctly on another PC under Windows-98 (my Linux machine is not dual-boot - never been contaminated by MS). Attached are output from dmesg, lspci -vv and lspcidrake -v. Note that a similar problem existed under 8.2. agpgart : VIA Technologies|VT82C691 [Apollo PRO] [BRIDGE_HOST] (vendor:1106 device:0691) unknown : VIA Technologies|VT82C598 [Apollo MVP3 AGP] [BRIDGE_PCI] (vendor:1106 device:8598) unknown : VIA Technologies|VT82C596 ISA [Apollo PRO] [BRIDGE_ISA] (vendor:1106 device:0596 subv:1106 subd:) unknown : VIA Technologies|VT82C586 IDE [Apollo] [STORAGE_IDE] (vendor:1106 device:0571) usb-uhci: VIA Technologies|VT82C586B USB [SERIAL_USB] (vendor:1106 device:3038 subv:0925 subd:1234) unknown : VIA Technologies Inc|Power Management Controller [BRIDGE_OTHER] (vendor:1106 device:3050) snd-emu10k1 : Creative Labs|SB Live! (audio) [MULTIMEDIA_AUDIO] (vendor:1102 device:0002 subv:1102 subd:8061) emu10k1-gp : Creative Labs|SB Live! (joystick) [INPUT_OTHER] (vendor:1102 device:7002 subv:1102 subd:0020) 8139too : D-Link Inc|DFE 538 TX [NETWORK_ETHERNET] (vendor:1186 device:1300) hptraid : Triones|HPT366 [STORAGE_OTHER] (vendor:1103 device:0004 subv:1103 subd:0001) Card:ATI Radeon : ATI|Radeon QD [DISPLAY_VGA] (vendor:1002 device:5144 subv:1002 subd:001a) unknown : Virtual|Hub [] (vendor: device:) 00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 8 Region 0: Memory at d800 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 2.0 Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2,x4 Command: RQ=0 SBA+ AGP+ 64bit- FW- Rate=x1 Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 9000-9fff Memory behind bridge: dc00-ddff Prefetchable memory behind bridge: d000-d7ff BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B- Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile South] (rev 23) Subsystem: VIA Technologies, Inc. VT82C596/A/B PCI to ISA Bridge Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 10) (prog-if 8a [Master SecP PriP]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 Region 4: I/O ports at a000 [size=16] Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 11) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32, cache line size 08 Interrupt: pin D routed to IRQ 19 Region 4: I/O ports at a400 [size=32] Capabilities: [80]
[Cooker] Beta 4 BUG: Problems setting up Logical Volume Manager
I've just done a test installation of Beta 4 using VMWare, configuring the system to use LVM for all but the / partition. A number of problems were found: 1. I set up the (logical) partitions in the volume group, and attempted to make the last partition smaller. I got the following error message: "Partitions sector #0 (3.9G) and #0 (1G) overlapping" No overlapping partitions appeared on the graphical display! 2. I discovered that if you create a partition, then resize it (to make it larger) the installer would allow you to resize it to the full size of the volume group regardless of the presence of any existing partitions. Not surprising vgextend complains when you try to do this. 3. I also discovered that the installer would sometimes allocate the last partition of the volume group to be 1 or 2 Mbytes too large. Attempting to create a partition in this way results in a blank error message appearing (pop-up box, no error message, just an OK button). Shrink the partition by 1 or 2 Mbytes results in it being accepted.
