2.6 kernel packages available
Ben Collins
Let me know how these do. Once 2.6.2 goes final, they will be uploaded
to the archive. These are based on 2.6.2-rc3, and they do require
silo-1.4.4.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
--
To UNSUBSCRIBE, email to debian-spa...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
D Lambrou
Upgraded to silo-1.4.4 (Works fine)
2.6 image boots fine but off course no updated (2.6) modutils so a bit
of aproblem with modules.
Back to 2.4 till i upgrade libc.
2.4 works fine with new silo.
--
---------------------------------------------------------
D Lambrou
http://crazylinux.net
You can always get my public key block from
http://crazylinux.net/public.asc
Fingerprint: C7B3 A112 3704 7202 2B33 6B28 5418 78DD 774A 7BCB
Chris K. Engel
What about XFree86? Has anyone made any patches so it will run under 2.6?
On Mon, 3 Feb 2004, D Lambrou wrote:
> Using woody on SunBlade 100
> Upgraded to silo-1.4.4 (Works fine)
> 2.6 image boots fine but off course no updated (2.6) modutils so a bit
> of aproblem with modules.
> Back to 2.4 till i upgrade libc.
> 2.4 works fine with new silo.
>
>
>
Ben Collins
> And now, a minor question.
>
> What about XFree86? Has anyone made any patches so it will run under 2.6?
If you want a quick way, download the kernel source, edit
arch/sparc64/kernel/pci.c:pci_name_bus(). Edit the sprintf line to look
like this:
sprintf(name, "%02x", bus->number);
Then recompiled. Remember, this is a hack. A hack that is only needed
for PCI video cards. Soon enough XFree86 will be made to work correctly.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
Tomislav Renic
> http://www.phunnypharm.org/pub/for/sparc-folks/kernel-images-2.6/
>
> Let me know how these do. Once 2.6.2 goes final, they will be uploaded
> to the archive. These are based on 2.6.2-rc3, and they do require
> silo-1.4.4.
>
> --
> Debian - http://www.debian.org/
> Linux 1394 - http://www.linux1394.org/
> Subversion - http://subversion.tigris.org/
> WatchGuard - http://www.watchguard.com/
>
Ben,
I tried the above kernel out on my Ultra 10 and the machine boots fine.
I can ssh into it and everything seems to be running just fine. During
boot, it stops showing stuff on my framebuffer after the following line:
Console: switching to mono PROM 80x34
I'm using the Creator3D card as the console.
Also, the local keyboard (sun keyboard) doesn't work at all with this
kernel.
I've gotten 2.6.2 compiled on my own, and it boots fine. When I get to
the login, it seems that the keyboard mapping is very screwed up.
Any suggestions?
Chris K. Engel
------------------------------------
Hier liegt ein Mann ganz obnegleich;
Im Leibe dick, an Suden reich.
Wir haben ihn in das Grab gesteckt,
Weil es uns dunkt er sei verreckt.
-PDQ Bach's Epitaph.
------------------------------------
Chris K. Engel
Tomislav Renic
dpkg-reconfigure console-data worked like a charm!
Mauricio
Problem I am facing is that configure cannot find openssl,
checking for OpenSSL... no
Even though I *supposedly* have it (it is a bit hard to ssh to the
machine without it =). So, where is openssl placed in Debian? I
Solaris, it is installed in /usr/local/ssl, but that does not seem to
be the case here. =(
David Johnson
> I am trying to compile cyrus-sasl in my IPX running debian 3.
> Problem I am facing is that configure cannot find openssl,
>
> checking for OpenSSL... no
>
> Even though I *supposedly* have it (it is a bit hard to ssh to the
> machine without it =). So, where is openssl placed in Debian? I
> Solaris, it is installed in /usr/local/ssl, but that does not seem to
> be the case here. =(
You just need to install the openssl-dev package.
David.
Mauricio
>On Sunday 08 Feb 2004 8:48 pm, Mauricio wrote:
>> I am trying to compile cyrus-sasl in my IPX running debian 3.
>> Problem I am facing is that configure cannot find openssl,
>>
>> checking for OpenSSL... no
>>
>> Even though I *supposedly* have it (it is a bit hard to ssh to the
>> machine without it =). So, where is openssl placed in Debian? I
>> Solaris, it is installed in /usr/local/ssl, but that does not seem to
>> be the case here. =(
>
>You just need to install the openssl-dev package.
>
>David.
Thanks, but I seem to be having a bit of problem doing that:
katrina:/home/raub# apt-get install openssl-dev
Reading Package Lists... Done
Building Dependency Tree... Done
E: Couldn't find package openssl-dev
katrina:/home/raub#
David Johnson
>
> Thanks, but I seem to be having a bit of problem doing that:
>
Oops. Try libssl-dev.
David.
Shawn Wallbridge
is handy when you are looking for a specific package, but are not sure
what it is called.
shawn
Mauricio
>
>
>David.
That did solve the problem indeed. Thanks!
Daniel Simon
> Let me know how these do. Once 2.6.2 goes final, they will be uploaded
> to the archive. These are based on 2.6.2-rc3, and they do require
> silo-1.4.4.
Hi all,
I tried the 2.6.2 on my Ultra 10/ATI PCI graphics/Type6 us
keyboard. The current working-kernel here is 2.4.20.
At first, I had trouble getting the keyboard runnning on the console,
but dpkg-reconfigure console-data did the job.
Next, X didn't start up. I applied some sfprintf-patch in some
pci-file noted on this mailing list and recompiled the kernel based on
the configuration you provide. Reason: the mouse device in
XF86Config-4 pointed to /dev/sunmouse. This was fine with
kernel-2.4.20, but doesn't work at all with 2.6.2. Solution: I use
/dev/input/mice now.
Excerpt from XF86Config-4:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "BusMouse"
EndSection
Section "InputDevice"
Identifier "Generic Mouse"
Driver "mouse"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
EndSection
[...]
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "Generic Mouse"
EndSection
Then X did start up, but the keyboard was screwed up. The
configuration for 2.4.20 was
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "sun"
Option "XkbModel" "type5"
Option "XkbLayout" "us"
EndSection
but this does not work at all for 2.6.2. Fix: I use
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "keyboard"
Option "CoreKeyboard"
EndSection
instead. However, this does not solve the problem completely; some
keys are wrong w.r.t. 2.4.20 (eg, Meta, the function keys 'Stop',
'Open', and so on). This is quite a problem when using emacs and I'm
so used on the nice function keys by now.
On the other way around, I can not use the 2.6.2 variant of
XF86Config-4 for the 2.4.20 kernel.
Any ideas how to a) get the type6 keyboard really working and b) how
to use a single XF86Config-4 file for both kernels?
Have fun,
d.
Sheldon Mustard
> Any ideas how to a) get the type6 keyboard really working and b) how
> to use a single XF86Config-4 file for both kernels?
I know on x86 I had to make sure mousedev and psmouse were loaded in 2.6
for my X config file to work. Not sure that's any help??
later,
SJM
--
Sheldon Mustard
--