[opensuse-factory] More bugs?
Finally managed to install 10.3a3. 1) System failed to boot. The problem of using /dev/sdxxx instead of hdX in /boot/grub/menu.lst I believe is already fixed for a4. 2) A /etc/grub.conf of setup --stage2=/boot/grub/stage2 (hd0,6) (hd0,6) isn't going to work as it doesn't install an MBR loader, so it's always a boot failure. What's needed is setup --stage2=/boot/grub/stage2 (hd0) (hd0,6) At least the latter line makes is boot, the former hangs after "booting from local disk". Raid1 (/dev/mdX) for rootfs. Or is this a result of a failure caused by 1)? 3) The "list of installed drivers" (printer pppd files) is built after the printer can be configured during installation in the hardware config step. Does this constellation make sense? 4) During installation, I changed some monitor values (number of pixels, screen diagonal, Vrefresh) and tested afterwards. Worked fine. When the system goes to runlevel 5 after installation, the xorg.conf is way off the monitor and obviously running with who knows what. The configuring during installation was obviously pointless. Has someone seen this too? 5) Module ata_piix isn't good. It takes a huge amount of time during boot, showing timeouts and lowering DMA/PIO with each step. Not really useful. Setting that module as broken in the rescue system causes piix to be loaded instead; but then no /dev/sda* are created so it's useless. Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Volker Kuhlmann <list0570@paradise.net.nz> writes:
Finally managed to install 10.3a3.
1) System failed to boot. The problem of using /dev/sdxxx instead of hdX in /boot/grub/menu.lst I believe is already fixed for a4.
2) A /etc/grub.conf of
setup --stage2=/boot/grub/stage2 (hd0,6) (hd0,6)
isn't going to work as it doesn't install an MBR loader, so it's always a boot failure. What's needed is
setup --stage2=/boot/grub/stage2 (hd0) (hd0,6)
At least the latter line makes is boot, the former hangs after "booting from local disk". Raid1 (/dev/mdX) for rootfs. Or is this a result of a failure caused by 1)?
It might be - hope this works with Alpha4, if not, please file a blocker bug!
3) The "list of installed drivers" (printer pppd files) is built after the printer can be configured during installation in the hardware config step. Does this constellation make sense?
Worth a bugreport.
4) During installation, I changed some monitor values (number of pixels, screen diagonal, Vrefresh) and tested afterwards. Worked fine. When the system goes to runlevel 5 after installation, the xorg.conf is way off the monitor and obviously running with who knows what. The configuring during installation was obviously pointless. Has someone seen this too?
Worth a bugreport.
5) Module ata_piix isn't good. It takes a huge amount of time during boot, showing timeouts and lowering DMA/PIO with each step. Not really useful. Setting that module as broken in the rescue system causes piix to be loaded instead; but then no /dev/sda* are created so it's useless.
Definitely needs a bugreport! Thanks for testing, Andreas -- Andreas Jaeger, aj@suse.de, 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
Hmmm.... That's strange considring the fact that I installed openSUSE 10.3 Alpha3 on both real hardware and VM without major issues, the only small issue being "vim-normal" package refused to install, but vim worked anyway. Again, it WORKS-FOR-ME -- -Alexey Eremenko "Technologov" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sun 29 Apr 2007 06:13:40 NZST +1200, Alexey Eremenko wrote:
Hmmm.... That's strange considring the fact that I installed openSUSE 10.3 Alpha3 on both real hardware and VM without major issues, the
Betcha you didn't install anything which was close to my config. That's why it's important for more people to test. The ata_piix module is not production quality, but looking at the name it's probably only used on PII and PIII mobos so if you have a new box you won't see the problem. The boot loader problems are kernel md raid1 for rootfs, this has last worked for me on real hardware with 10.0, can't remember vmware. Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sun 29 Apr 2007 06:10:15 NZST +1200, Andreas Jaeger wrote:
3) The "list of installed drivers" (printer pppd files) is built after the printer can be configured during installation in the hardware config step. Does this constellation make sense?
Worth a bugreport.
No problem, but perhaps more info would help. The system had no printer connected. If yast offers to configure one, it can only be for a network printer on another host. Still, should all the usual printer model descriptions (ppd files) be available here? If yes, the list of available files, which is created later when SuSEconfig runs, should already be available here, thus that part of SuSEconfig needs to be run (damn, that takes ages). If not, it would be useful for installing a printer file from another media. How is it supposed to work? Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello, On May 1 20:46 Volker Kuhlmann wrote (shortened):
3) The "list of installed drivers" (printer pppd files) is built after the printer can be configured during installation in the hardware config step. Does this constellation make sense? ... The system had no printer connected. If yast offers to configure one, it can only be for a network printer on another host.
No. YaST cannot know for sure if there is no local printer connected. A local connected printer may be switched off (in particular Epson USB printers cannot be detected when the device is switched off).
Still, should all the usual printer model descriptions (ppd files) be available here?
Yes. On a standard system it should be possible to set up a printer. In particular when you want to print directly on a network printer (i.e. when there is no CUPS print server in between) or when you want to print via SMB share or via iPrint server, you need to run the printer driver on your local machine. Perhaps I misunderstand it and you mean https://bugzilla.novell.com/show_bug.cgi?id=253257 ?
If yes, the list of available files, which is created later when SuSEconfig runs, should already be available here, thus that part of SuSEconfig needs to be run (damn, that takes ages). If not, it would be useful for installing a printer file from another media.
The YaST printer database is not created via SuSEconfig but via the YaST printer setup tool. Perhaps it only looks wrong? Perhaps the YaST printer setup tool only shows some initial stuff (e.g. its entry in the hardware config screen) and then it creates its printer database so that it only looks as if it creates its printer database too late? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
Alexey Eremenko -
Andreas Jaeger -
Johannes Meixner -
Volker Kuhlmann