Ubuntu 9.10 WARNING

[Leif Asbrink]

Hi All,

It seems the Linux development team is now making yet another
major change to the Linux system. The 2.6.30 kernel which we
find in Ubuntu as well as Debian squeeze has several major
problems and I would advice Linrad users to stay with older
Linux distributions for a while until the problems have been
resolved.

I am running Debiab squeeze on my laptop. I can not boot with it
so there is also a minimal Debian lenny installation on this
laptop from which I can boot Windows, lenny, squeeze and
also Fedora 64 bit.

The new Grub that comes with the 2.6.30 kernel can not co-exist
with Windows on this machine. Neither under Ubuntu nor Debian.
I tried to send info to Grub developers, but failed. Hope they
already know. (See below.)

There are many more problems with 2.6.30. The computer will
hang if I close the lid or press the power off button. As
a consequence the next boot will fail and require a disk
check.

I am using the latest software because the gcc compiler
has better error checking. Avoid it unless you really need
the support for newer hardware that it provides.

73

Leif / SM5BSZ




Date: Sat, 28 Nov 2009 01:29:28 +0100
From: Leif Asbrink <le...@sm5bsz.com>
To: pkg-gru...@lists.alioth.debian.org
Subject: Grub problems.

Hello,

After running update-from-grub-legacy I found two problems (squeeze)

1) If I reboot(CtlAltDel) before having logged in, the next boot
will fail. I have to run e2fsck and answer 'y' to correct for the
time stamp to be in the future on the partition to boot.
(Unpleasent, but not serious.)

2) I have a Windows partition also. Each time I have used Windows
Grub will fail. It says "Welcome to Grub" (or similar, two lines)
and then the computer is dead. I can then run rescue from a CD and
install Grub. That makes my Debian squeeze run until I forget that
I must always log in - or until I run Windows.

update-grub showed errors on the Windows partition. Somewhere
chkdisk was suggested. I do not think errors in Windows that
I do not care about should affect how Debian boots next time.
(In case that might be the source of the problems I see)

My (temporary) solution has been to install Ubuntu 9.10 side by side
on a small partition. That installs a working Grub from which
I can boot into Windows and Debian squeeze without errors.
This is not really a solution because after a few boots the
Grub installed by Ubuntu will also fail and require a resque
from the CD with a grub re-install.

The computer is a HP6510b laptop.

I have Debian squeeze on a stationary computer where the new
Grub works fine. There is no other operating system on the
stationary so problem 2) is not possible. Problem 1) is
NOT present.

Both computers were "standard installs" from netinstall
(lenny Oct 17 2009) The stationary was installed soon after
Oct 17 and upgraded to squeeze. The laptop was installed
today and upgraded to squeeze. Something during the boot
process in the laptop changes the clock but that particular
step in the boot sequence does not happen in the stationary
computer.

I have been using Debian for many years now. This is the first
time I have a problem (worth mentioning.)

Thanks for good work:-)

Regards

Leif


--

[Chris]

Interesting. I have Ubuntu 9.10 that was a clean install, dual-boot
with Win XP and no issues so far.

Running on a Dell X6400 Inspiron laptop I believe is the model.

It may be a fault with particular Windows releases or hardware?

> --
>
> You received this message because you are subscribed to the Google Groups "Linrad" group.
> To post to this group, send email to lin...@googlegroups.com.
> To unsubscribe from this group, send email to linrad+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/linrad?hl=en.
>
>
>



--
73 de Chris KC2RGW
-----------------------------------------------
˙dn ǝpıs ʇɥƃıɹ ɹoʇıuoɯ ɹnoʎ uɹnʇ
ǝsɐǝןd 'sıɥʇ ƃuıpɐǝɹ ǝɹɐ noʎ ɟı

[yo9gjx]

Interesting. I think possible need a new clean install. I have Debian,
Ubuntu 9.10 and Free BSD and no problems. Also Linrad work great.

> From: Leif Asbrink <l...@sm5bsz.com>
> To: pkg-grub-de...@lists.alioth.debian.org

[Lynn W7VTS]

Hello, you indicated that Linrad works great on your Ubuntu 9.10. Are
you running 32 or 64 bit? Does anyone have any thoughts on building
Linrad for 64 bit? During the build process (Ubuntu 9.10 64 bit), I
get the following error:

In file included from /usr/include/stdio.h:910,
from globdef.h:90,
from lxsys.c:23:
In function ‘sprintf’,
inlined from ‘lir_open_serport’ at lxsys.c:369:
/usr/include/bits/stdio2.h:34: error: call to __builtin___sprintf_chk
will always overflow destination buffer
make: *** [lxsys.ol] Error 1

Does anyone have any ideas on this?

Thanks!
Lynn, W7VTS

[Lynn W7VTS]

I didn't see this post during an earlier search -- fixed the problem!

==================================
The gcc compiler is changed now and then and it always becomes better.
I have not yet tried Ubuntu 9.10 myself, but obviously the latest
gcc (not yet included in Debian testing) has better error checking.

There is a serious error in Linrad. The array declared on line 22 in
lxsys.c like this:
char serport_name[]="/dev/ttyS?";
is used in line 369 like this:
sprintf(&serport_name[0],"%s","/dev/ttyUSB");
That will overwrite something else and it could be a disaster.

This variable is ONLY used if you are using (w)users_hwaredriver.c
to communicate with your transceiver.

The problem can be fixed like this:
char serport_name[12]="/dev/ttyS?";

(and a corresponding change for BSD on line 32)

73

Leif / SM5BSZ