Hello List
Tumbleweed : kernel-default-3.6.10-15.1.i586
__________
my system is on /dev/sdb which is 1 TB SATA HDD
- i have a /dev/sda for backups, which is 360 GB PATA HDD
..............
kernel-default-3.6.10-15.1.i586 does not allow me to mount /dev/sda
kernel 3.4.6-2.10-desktop DOES allow mounting of /dev/sda & sees /dev/sda OK
.................
- with kernel-default-3.6.10-15.1.i586 i get :
command :
_______
# mount /dev/sda4 /mnt
mount: special device /dev/sda4 does not exist
....................
[ because do not feel sufficiently 'advanced' to wrestle with bugzilla
reports,
since kernel 3.4.6-2.10 i have been hoping this trouble would be
solved and 'go away',
but, no such luck ]
best regards
Ellan
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
I am still not sure how secure grub2 is going to find its grub.cfg.
Normally its location is dynamically added to core.img. In case of
secure grub2 core.img is prebuilt and signed during package creation
(or may be signed later, not sure). So it is impossible to store
information about grub root directory there. The only place which can
be guaranteed to be auto-detected is ESP itself. But it is not where
grub2 related files are installed currently ...
Do I miss something here?
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi,
ksymoops fails to build for openSUSE Factory since quite some time.
Following https://bugzilla.novell.com/show_bug.cgi?id=793544#c2 it
doesn't make sense to offer ksymoops when the Linux kernel is built with
KALLSYMS enabled.
Therefore I'm going to drop the package and ask to get it removed from
openSUSE Factory too.
If one is willing to keep it please speak up in the next days.
Cheers,
Lars
--
Lars Müller [ˈlaː(r)z ˈmʏlɐ]
Samba Team + SUSE Labs
SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Everytime when grub2-branding-openSUSE is update, I'am getting:
( 6/32 ) Installation von: grub2-branding-openSUSE-12.3-1.16
..............................[fertig]
Zusätzliche rpm-Ausgabe:
Generating grub.cfg ...
Found theme: /boot/grub2/themes/openSUSE/theme.txt
Found linux image: /boot/vmlinuz-3.7.0-1-desktop
Found initrd image: /boot/initrd-3.7.0-1-desktop
Found linux image: /boot/vmlinuz-3.7.0-1-default
Found initrd image: /boot/initrd-3.7.0-1-default
Found linux image: /boot/vmlinuz-3.6.3-1-desktop
Found initrd image: /boot/initrd-3.6.3-1-desktop
Found linux image: /boot/vmlinuz-3.6.3-1-default
Found initrd image: /boot/initrd-3.6.3-1-default
ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8
ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8
ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8
ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8
ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8
ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8
ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8
ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8
ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8
ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8
ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8
Found Windows 7 (loader) on /dev/sda1
Found openSUSE 11.4 (x86_64) on /dev/sda6
Running fsck -f on that ext4 partition doesn't find any problem however.
But on a clone of that partition done with dd that error also shows up. Even
if it is not mounted. Very strange.
Does anyone have an idea, what might cause that problem, how to fix it and ( if
needed) to file a bug against what ?
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hello openSuSErs
- after todays update, upon adding to Data input field . . . chart
disappears.
...............
best wishes for forthcoming new year
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hello, I switched recently to OpenSUSE Tumbleweed from 12.2 and I meet
this strange problem, that is the kernel gets hard lockup whenever I
plug the AC Adapter in, after that the watchdog tried to shutdown the
locked up CPU and I have kernel panic. I tried to look around for
solution but couldn't find any, so if anyone can give me a pointer on
how to gather more information about this behaviour (so I can file a
proper bug report), or even better, a solution, I would appreciate
that. Here is a few things I noted:
- The lockup only happens with Linux 3.7.1, version 3.2 to 3.5 are
trouble-free (I haven't tested with version 3.6 yet)
- The backtraces that is shown when the lockup happens are mostly NMI
watchdog's, although sometimes there are more backtrace for other CPUs
as well (mostly related to hrtimer stuff).
- Even if I suspend the computer before plug the adapter in, the
lockup still happen right after resuming. Disabling X and using the
single user mode don't help either.
- Interestingly enough, plugging in before mounting root is fine, that
mean the culprit is loaded later, but I don't know how to find exactly
which module is causing it (no information from backtrace).
Of course, reverting back to OpenSUSE 12.2 will help, but I would like
to solve this if possible, after all I can't stay with 12.2 forever.
Thank in advance!
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
I have tried running three different kernels. I have 3.4 3.6 and 3.7 in
parallel right now. Behavior is basically the same on all three. I have
nearly googled myself into a coma.
3.4 had known intel bugs, many of which were fixed in 3.6.10, hence that
install. 3.7 (from tumbleweed) was originally being tested until I read
there were regressions regarding the intel drivers.
My screen will suddenly become unresponsive, with only the mouse being
able to move. Then shortly thereafter that will stop responding as well.
It is not possible to drop to TTY. I have to hold the power down.
After trying the different kernels, I have tried also the i915.modeset=0
and i915.modeset=1 in grub. The former seems to cause more problems than
it solves, changing from a frozen screen to a garbled one. So far the
latter is proving stable, though perhaps with slightly degraded
graphical performance.
> Hippie:/home/roger # hwinfo --gfxcard
> 09: PCI 02.0: 0300 VGA compatible controller (VGA)
> [Created at pci.319]
> Unique ID: _Znp.AyhgUXFyk41
> SysFS ID: /devices/pci0000:00/0000:00:02.0
> SysFS BusID: 0000:00:02.0
> Hardware Class: graphics card
> Model: "Intel 945 GM"
> Vendor: pci 0x8086 "Intel Corporation"
> Device: pci 0x27a2 "945 GM"
> SubVendor: pci 0x1179 "Toshiba America Info Systems"
> SubDevice: pci 0xff10
> Revision: 0x03
> Driver: "i915"
> Driver Modules: "drm"
> Memory Range: 0xf0a00000-0xf0a7ffff (rw,non-prefetchable)
> I/O Ports: 0x1800-0x1807 (rw)
> Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
> Memory Range: 0xf0b00000-0xf0b3ffff (rw,non-prefetchable)
> IRQ: 16 (3038 events)
> I/O Ports: 0x3c0-0x3df (rw)
> Module Alias: "pci:v00008086d000027A2sv00001179sd0000FF10bc03sc00i00"
> Driver Info #0:
> XFree86 v4 Server Module: intel
> Driver Info #1:
> XFree86 v4 Server Module: intel
> 3D Support: yes
> Extensions: dri
> Config Status: cfg=no, avail=yes, need=no, active=unknown
>
> 10: PCI 02.1: 0380 Display controller
> [Created at pci.319]
> Unique ID: ruGf.EeuYq4vjbr7
> SysFS ID: /devices/pci0000:00/0000:00:02.1
> SysFS BusID: 0000:00:02.1
> Hardware Class: graphics card
> Model: "Intel Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller"
> Vendor: pci 0x8086 "Intel Corporation"
> Device: pci 0x27a6 "Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller"
> SubVendor: pci 0x1179 "Toshiba America Info Systems"
> SubDevice: pci 0xff10
> Revision: 0x03
> Memory Range: 0xf0a80000-0xf0afffff (rw,non-prefetchable)
> Module Alias: "pci:v00008086d000027A6sv00001179sd0000FF10bc03sc80i00"
> Config Status: cfg=no, avail=yes, need=no, active=unknown
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org