|
Bugzilla – Full Text Bug Listing |
| Summary: | install does not complete on dual opteron 24x/tyan k8sd pro | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Benj FitzPatrick <benjfitz> |
| Component: | Installation | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED WONTFIX | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | eich |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/var/log/boot.msg on failed computer
dmesg output hwinfo output lsmod output xorg.conf file xorg log file |
||
|
Description
Benj FitzPatrick
2005-11-09 18:06:27 UTC
It seems that there is some HW specific problem. Reasigning to the kernel team. could you please attach /var/log/boot.msg where its failed? Please reopen this bug if the required information can be provided. Created attachment 57392 [details]
/var/log/boot.msg on failed computer
This is from the tyan k8sd pro/dual opteron 248 machine.
I have attached the boot.msg as requested. Symbols match kernel version 2.6.13. No module symbols loaded - kernel modules not enabled. This is most likely the problem. But how comes that the symbol table mismatches the used Kernel here. Which media (exactly) do you use to boot? Please add the output of `lsmod' here. Assining this to the kernel maintainers with the request for help. re comment #6: I think old syslogd's always said "No module symbols loaded" at startup - maybe this is specific to the install system. Looking at the original comment: - install works up to the point where X is supposed to come up - user can switch to different console - reboot works So it seems this is an X11 driver issue. I'm assigning this to the X11 folks. Benj, can you please provide hwinfo output for this machine? And attach /var/log/Xorg.0.log + /etc/X11/xorg.conf as well. Thanks. > If I reboot I can't get in at all b/c I haven't been able to set up any user
> accounts.
This sounds as if the ctrl-alt-f2 trick does not work either after reboot.
Otherwise you should be able to get in as root at least.
The installation system normally falls back to ncurses yast if X cannot start up or dies for whatever reason unless yast itself crashes.
We never saw any feedback --> WONTFIX. Reopening for NEEDINFO. Benj, would you please comment? Created attachment 59041 [details]
dmesg output
Created attachment 59042 [details]
hwinfo output
Created attachment 59043 [details]
lsmod output
Created attachment 59044 [details]
xorg.conf file
Created attachment 59045 [details]
xorg log file
I have attached the requested files plus the output of dmesg just in case. Please let me know if you need any more files. > The installation system normally falls back to ncurses yast if X cannot
> start up or dies for whatever reason unless yast itself crashes.
Exactly. I don't believe this is a X11 related problem. Assigning back to Installation component.
Stefan, does 'Tyan 2880 K8S' ring a bell ?! IIRC, our machine needed a BIOS update (to 2880-203) in order to function with Linux. A BIOS update is always a good idea ;-) Otherwise, the description sounds strange, as apparently only the 246s don't work, 248 and 270 do work. Or did I get sth. wrong? Are the BIOS settings in all machines the same? Maybe some mmio problem on this machine. Ah, good though, and I should have mentioned this earlier. This happens for 3.04 and 3.05 versions of the bios with the latter being the most current, and all of them have the newest bios. As far as the computers it affects, it only happens on the single core ones (2xdual 246s and 1xdual 248), but the dual core one (dual 275s) works fine. Hi, I was wondering what the status of this one is? On my service request page it says that it is "awaiting customer." What exactly does this mean? Do you need more info from me? Thanks. Pleas boot into runlevel 3 and use "sax2 -r" for configuration. If this doesn't work attach /var/log/SaX2.log. . |