Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
We've fixed bug 266886 - a bug with raid setups and our developers and QA team have tested heavily all situations they could think of. I've just released a new repository with an updated perl-bootloader - and a new kernel with some minor fixes to: ftp://ftp.suse.com/pub/people/aj/10.2-bootloader-test We're going to release this the next days as official updates unless somebody finds another serious problem. Thanks for all your help with testing! Andreas P.S. Full quote as reminder ;-) Andreas Jaeger [EMAIL PROTECTED] writes: The last kernel update for openSUSE 10.2 showed a couple of bugs (see bugreport #252911) in the code that updates the bootloader configuration after a kernel update. We have tried to fix all of them and did internal testing - and fixed further bugs encountered during the internal testing. Now we're confident that we have fixed everything we tested ;-) - but would like to have the code tested in many more environments. Therefore I've created a repository that contains a new perl-Bootloader package and a new kernel. The new kernel contains as most interesting feature the re-enablement of CONFIG_USB_DEVICEFS - and also a small number of bugfixes. For me it's most interesting to have the kernel so that you can test that the bootloader rewrite works ;-) Please add the following URL as repository for testing: ftp://ftp.suse.com/pub/people/aj/10.2-bootloader-test Please install *first* the perl-bootloader patch and then *afterwards* the kernel patch. Scenarios to test: -- * openSUSE 10.2 10.3 (Alpha) installed with - /boot primary partition - /boot logical partition - / primary partition - / logical partition - persistent device links (default) - LVM proposal - EVMS proposal - fakeraid * Various architectures (i386, x86_64, ...) * Various bootloaders (GRUB, LILO, ...) * Update/install/remove kernels with rpm - Will new boot entries be created/removed? - Will new entries be inserted on top (e.g. in menu.lst)? - In case of default/smp/bigsmp kernels, will failsafe entries be created? - Is the label correct, thus Distribution -- Kernel-version-release? * Handling of default entries - New kernels should only become default if the kernel referring to the former default entry has the same flavour (e.g. 'smp' or 'xen') * System must be bootable ;) Please report everything in bugzilla and mention that you used the 10.2-bootloader-test repository. Thanks for your help, Andreas Andreas -- Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgpQVkWx548qy.pgp Description: PGP signature
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
On 4/29/07, Andreas Jaeger [EMAIL PROTECTED] wrote: We've fixed bug 266886 - a bug with raid setups and our developers and QA team have tested heavily all situations they could think of. I've just released a new repository with an updated perl-bootloader - and a new kernel with some minor fixes to: ftp://ftp.suse.com/pub/people/aj/10.2-bootloader-test We're going to release this the next days as official updates unless somebody finds another serious problem. What about the widespread criticism of the new bootloader entry naming scheme? (https://bugzilla.novell.com/show_bug.cgi?id=252911) has this been fixed? _ Benjamin Weber -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
On Monday 16 April 2007, Thomas Hertweck wrote: STDIN wrote: [...] I tried, its not there: # modprobe usbfs FATAL: Module usbfs not found. As already mentioned several times on this list: usbfs is not a self-contained kernel module. It's part of usbcore which is most likely compiled as a module. Therefore, you should get your USB_DEVICEFS with usbcore.ko if this feature had been enabled in .config at compile time (which is true for kernels to be included in 10.3 and the latest patched kernel for 10.2). All you need to do is mount the filesystem, or change /etc/fstab to do it automatically when the system starts up. Cheers, Th. Well that brings it full circle then, doesn't it Thomas? The OP posted that he DID try the new kernel (the subject of this thread) and it did NOT work for him, and others (mistakenly) suggested he modprobe it, only to be told by you that its in the kernel and he need do nothing of the sort. Its all starting to sound a little like a Monty Python skit isn't it? -- _ John Andersen pgpMWjclPxwa2.pgp Description: PGP signature
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
John Andersen wrote: [...] Well that brings it full circle then, doesn't it Thomas? The OP posted that he DID try the new kernel (the subject of this thread) and it did NOT work for him, and others (mistakenly) suggested he modprobe it, only to be told by you that its in the kernel and he need do nothing of the sort. Its all starting to sound a little like a Monty Python skit isn't it? The OP posted in [EMAIL PROTECTED] that it worked in a similar way I've described in my email - USB_DEVFS is enabled, all that had to be done is mounting the filesystem. So what's your point here? Just trying to bash other people? PS: This is a rhetorical question, so no answer required. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
STDIN wrote: [...] I tried, its not there: # modprobe usbfs FATAL: Module usbfs not found. As already mentioned several times on this list: usbfs is not a self-contained kernel module. It's part of usbcore which is most likely compiled as a module. Therefore, you should get your USB_DEVICEFS with usbcore.ko if this feature had been enabled in .config at compile time (which is true for kernels to be included in 10.3 and the latest patched kernel for 10.2). All you need to do is mount the filesystem, or change /etc/fstab to do it automatically when the system starts up. Cheers, Th. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
On Friday 13 April 2007 15:21:00 [EMAIL PROTECTED] wrote: usbfs was never removed from the kernel, it was not enable, so it was very simple to turn it on. How, please? -- Bob openSUSE 10.2 x86_64, Kernel 2.6.18.8-0.1, KDE 3.5.6 r31.4 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
On Saturday 14 April 2007 04:46, Bob Williams wrote: On Friday 13 April 2007 15:21:00 [EMAIL PROTECTED] wrote: usbfs was never removed from the kernel, it was not enable, so it was very simple to turn it on. How, please? Only by rebuilding the kernel from source. It was not run-time configurable. And If I recall correctly (but I'm not 100% sure), USBDEVFS is not available for compilation as a loadable module. -- Bob Randall Schulz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
Thomas Hertweck wrote: Randall R Schulz wrote: [...] And If I recall correctly (but I'm not 100% sure), USBDEVFS is not available for compilation as a loadable module. It is. It's not a self-contained module, but this feature is part of the usbcore.ko module. I guess what he wanted to say is that you can't just add a module but you have to replace an existing one with another. Wolfgang -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
On Sat, Apr 14, 2007 at 07:58:52AM -0700, Randall R Schulz wrote: On Saturday 14 April 2007 04:46, Bob Williams wrote: On Friday 13 April 2007 15:21:00 [EMAIL PROTECTED] wrote: usbfs was never removed from the kernel, it was not enable, so it was very simple to turn it on. How, please? Only by rebuilding the kernel from source. It was not run-time configurable. And If I recall correctly (but I'm not 100% sure), USBDEVFS is not available for compilation as a loadable module. You can also install the test kernel update we provide alongside with the new bootloader package. It has USBDEVFS enabled again. Ciao, Marcus -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
Marcus, On Saturday 14 April 2007 10:01, Marcus Meissner wrote: On Sat, Apr 14, 2007 at 07:58:52AM -0700, Randall R Schulz wrote: On Saturday 14 April 2007 04:46, Bob Williams wrote: On Friday 13 April 2007 15:21:00 [EMAIL PROTECTED] wrote: usbfs was never removed from the kernel, it was not enable, so it was very simple to turn it on. How, please? Only by rebuilding the kernel from source. It was not run-time configurable. ... You can also install the test kernel update we provide alongside with the new bootloader package. It has USBDEVFS enabled again. Is it true that a kernel update will be released through the official openSUSE update service that includes this reconfiguration? Ciao, Marcus Randall Schulz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
On Saturday 14 April 2007 10:13, Marcus Meissner wrote: ... Is it true that a kernel update will be released through the official openSUSE update service that includes this reconfiguration? Actually this kernel update that is in the testrepo will be the actual kernelupdate we will release after testing the bootloader changes has concluded. So: Yes. That's good news. Thanks. Ciao, Marcus RRS -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
Bob, Most likely you are using it for hotsyn to the PALM so I also added few tricks not related specifically to your question but that are important to hot sync with VMware. If you use the new kernel you will still need those tips to hotsync of course you will not need to enable usbfs. Using USB devices with VMWare under linux has been a pain due to the fact that VMware relies on the USB filesystem at /proc/bus/usb. SuSE 10.2 unselected the support of usbfs from the kernel so mounting by itself does not work any more. The support of usbfs is still in the kernel but you have to enable it :-( 1. Need to enable usbfs support in the kernel** Which has been disable because of security concerns. 1.1. basic requirements: kernel-source ncurses-devel (nedeed for make menuconfig) so just #yast -i ncurses-devel etc 1.2 Kernel and kernel-source should be the save version: rpm -qa | grep kernel 1.3 Change the kernel configuration #cd /usr/src/linux #make menuconfig In make menuconfig for kernel configuration GOTO: - Device Drivers//USB support/USB device filesystem and selected it! Esc/esc until ask you to save the config. Say yes. #make modules make modules_install reboot Bob this part can be done in many different way. You can clone the configuration file, change it and use one of the new vanilla kernels etc. Menuconfig is the one I use but other options are also available. This is simple and I tried in three machines and all are working very well. Do not do other changes in the kernel, make it simple. 2. Change /etc/fstab: By Default, VMWare will NOT allow the user to attach to USB devices connected to the physical workstation when the host OS is SuSE Linux 2.1 To allow access to USB devices attached to the workstation through VMWare, you need to modify the /etc/fstab file as root. /etc/fstab Locate this line: usbfs/proc/bus/usbusbfs noauto 0 0 and change it to: usbfs/proc/bus/usbusbfs autofs 0 0 2.2 After the machine has been rebooted, the USB Device attached, and VMWare started, select VM | Removable Devices | USB Device, and select the device that needs to be attached to the VMWare session. 2.3 When the usb device is the Palm like in my case Treo 700p sometimes you have another device loaded rmvisor just remove it #rmmod visor OR Mount the usb before starting VMware (instead of 2.1) # mount -t usbfs /dev/bus/usb /proc/bus/usb Continue as 2.2 and 2.3 3. Be sure the vmimage is in focus 4. Hotsync 5. May have to start with the phone out of the craddle If if does not work try to repeat the mount and rmmod command and try again.!! Ciao -=terry(Denver)=- On Sat, 2007-04-14 at 12:46 +0100, Bob Williams wrote: On Friday 13 April 2007 15:21:00 [EMAIL PROTECTED] wrote: usbfs was never removed from the kernel, it was not enable, so it was very simple to turn it on. How, please? openSUSE 10.2 x86_64, Kernel 2.6.18.8-0.1, KDE 3.5.6 r31.4 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
The last kernel update for openSUSE 10.2 showed a couple of bugs (see bugreport #252911) in the code that updates the bootloader configuration after a kernel update. We have tried to fix all of them and did internal testing - and fixed further bugs encountered during the internal testing. Now we're confident that we have fixed everything we tested ;-) - but would like to have the code tested in many more environments. Therefore I've created a repository that contains a new perl-Bootloader package and a new kernel. The new kernel contains as most interesting feature the re-enablement of CONFIG_USB_DEVICEFS - and also a small number of bugfixes. For me it's most interesting to have the kernel so that you can test that the bootloader rewrite works ;-) Please add the following URL as repository for testing: ftp://ftp.suse.com/pub/people/aj/10.2-bootloader-test Please install *first* the perl-bootloader patch and then *afterwards* the kernel patch. Scenarios to test: -- * openSUSE 10.2 10.3 (Alpha) installed with - /boot primary partition - /boot logical partition - / primary partition - / logical partition - persistent device links (default) - LVM proposal - EVMS proposal - fakeraid * Various architectures (i386, x86_64, ...) * Various bootloaders (GRUB, LILO, ...) * Update/install/remove kernels with rpm - Will new boot entries be created/removed? - Will new entries be inserted on top (e.g. in menu.lst)? - In case of default/smp/bigsmp kernels, will failsafe entries be created? - Is the label correct, thus Distribution -- Kernel-version-release? * Handling of default entries - New kernels should only become default if the kernel referring to the former default entry has the same flavour (e.g. 'smp' or 'xen') * System must be bootable ;) Please report everything in bugzilla and mention that you used the 10.2-bootloader-test repository. Thanks for your help, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgp11ks3jte4m.pgp Description: PGP signature
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
On Thursday 12 April 2007, Andreas Jaeger wrote: The new kernel contains as most interesting feature the re-enablement of CONFIG_USB_DEVICEFS - and also a small number of bugfixes. For me it's most interesting to have the kernel so that you can test that the bootloader rewrite works ;-) Why do I feel like Hansel and Gretel here -- _ John Andersen -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
John Andersen [EMAIL PROTECTED] writes: On Thursday 12 April 2007, Andreas Jaeger wrote: The new kernel contains as most interesting feature the re-enablement of CONFIG_USB_DEVICEFS - and also a small number of bugfixes. For me it's most interesting to have the kernel so that you can test that the bootloader rewrite works ;-) Why do I feel like Hansel and Gretel here What I wanted to say was: The important part for testing is perl-Bootloader. The kernel is there to allow you to test it. Besides, the kernel has some nice changes which I appreciate you testing as well - but the goal is to test the bootloader. Are you still confused? ;-) Sorry, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgpAB2yrcp5Jj.pgp Description: PGP signature
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
Alexey Eremenko [EMAIL PROTECTED] writes: CONFIG_USB_DEVICEFS This feature is really important for the Virtualization software around ! (and therefore for me) Why did it get removed from 10.2 ? I have heard of security reasons, now I don't believe this, since if it were security, it would not be re-introduced into 10.3, so more specifically - why it was removed ? Read bugzilla. It was indeed removed for security reasons and also because an alternative interface is available that has no security problems - but since it's not mounted by default, the admin can decide on his/her own whether this is a security concern or whether s/he needs it for VMware, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgpjj73ePcx84.pgp Description: PGP signature
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
On Fri, Apr 13, 2007 at 12:39:49PM +0100, Alexey Eremenko wrote: CONFIG_USB_DEVICEFS This feature is really important for the Virtualization software around ! (and therefore for me) Why did it get removed from 10.2 ? I have heard of security reasons, now I don't believe this, since if it were security, it would not be re-introduced into 10.3, so more specifically - why it was removed ? Because it is obsolete and deprecated and we thought all users were fixed already. It has now been readded for 10.2 with the above kernel update. For 10.3 we will again try to remove it. Ciao, Marcus -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test
usbfs was never removed from the kernel, it was not enable, so it was very simple to turn it on.Only I can blame opensuse for failurel to communicate this fact in the release notes . So, many user like me spend a lot of time trying to figure out why they could not sync any more under VMware. It only affected very few usb devices. Most of them worked OK. I believe the pressure to make changes should go to VMware (IMHO) -terry- -Original Message- From: Alexey Eremenko [EMAIL PROTECTED] Subj: Re: [opensuse] Call for Testing: openSUSE 10.2 Bootloader Test Date: Fri Apr 13, 2007 5:43 am Size: 489 bytes To: [EMAIL PROTECTED] CONFIG_USB_DEVICEFS This feature is really important for the Virtualization software around ! (and therefore for me) Why did it get removed from 10.2 ? I have heard of security reasons, now I don't believe this, since if it were security, it would not be re-introduced into 10.3, so more specifically - why it was removed ? -- -Alexey Eremenko Technologov -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
