Unnamed pupplet (puppy411 kernel-2.6.27.5 Xorg-7.4 LXDE)

[wow]

I'm not sure what's wrong but I can't seem to get glxgears working. I get the message:

Code: Select all

Xlib: extension "GLX" missing on display ":0.0"
Error: couldn't get an RGB, Double-buffered visual

(EE) intel(0): [dri] I830CheckDRIAvailable failed: glx not loaded

Ok, I google it and found that it would be a problem with the xf86-video-intel driver. So I need to update xf86-video-intel, libdrm, drm kernel modules and Mesa to their latest stable versions or download everything from git (bleeding edge, unstable) make some .pets or an ISO (plus bugfixes and few goodies).
If you have the knowledge, please go ahead and install those packages from source.
I configured X with

Code: Select all

./configure --build=i686-pc-linux-gnu --prefix=/usr/X11R7 --libdir=/usr/X11R7/lib --includedir=/usr/X11R7/include --sysconfdir=/etc --localstatedir=/var

And Mesa . . . hmm . . . i can't remember at the moment.

[battleshooter]

Ok, I google it and found that it would be a problem with the xf86-video-intel driver.

So, I guess that's the final diagnosis and there's nothing to be done except compile the new packages from source.

If you have the knowledge

I've done some compiling before, but doing Xorg is way over my head. Rather intimidating I guess I'll just wait till the next ISO update or whatever comes. It's not like I'll die not being able to play Paintball I might consider having ago one day, but it'll be a steep learning curve.

@ Mark

what really makes me wonder is, that libglx.so from the original xorg gives a black screen.

Actually, I completely forgot about that. A while back I tested the official Puppy 4 with my laptop and I was given completely screwed graphics. So that would explain why the original libglx was so disastrous. Sorry I didn't bring it up, I forgot.

Battleshooter

[panzerpuppy]

I actually tried the new Ati catalyst driver 9.1.
It compiled, but the fglrx kernelmodule would not load.
dmesg and googe told be, that this is, because in the kernels .config this must be set:

Code: Select all

#
# Bus options (PCI etc.)
#
CONFIG_PCI_MSI=y

Unfortunately, this seems to make it incompatible with wows kernel.
I had to replace the modules in intrd.gz with the recompiled ones.
There are several complains about this in the phoronix forum, so I hope, they will release a version without this option.
I have not yet decided, which kernel I'll use for newyearspup final tomorrow.
If I succeed to compile a patched wine that supports pixelshaders with that catalyst driver, I would use the new kernel.
If not, this had to wait for newyearspup03 in 3 months.

I would not like, to break compatibility with wows kernel...
Wine anyway seems not to compile with the typedefs I had to add.
Mark

Do these drivers (9.1) work at all in Puppy? I run the official installer,the driver installs OK,then an aticonfig --initial -f and restart X. After that, I get a black screen and I'm forced to do a soft system reboot to get to the commandline.
Catalyst 8.11 produces the same issue. (8.12 works)

[wow]

I downloaded drm-2.4.4 from git, xf86-video-intel-2.6.1 and Mesa-7.3 (libs, glut, demos).
libdrm and xf86-video-intel configured with:

Code: Select all

./configure --build=i686-pc-linux-gnu --prefix=/usr/X11R7 --libdir=/usr/X11R7/lib --includedir=/usr/X11R7/include --localstatedir=/var --sysconfdir=/etc --disable-static --disable-maintainer-mode --enable-shared

Mesa 7.3:

Code: Select all

./configure --build=i686-pc-linux-gnu --prefix=/usr/X11R7 --libdir=/usr/X11R7/lib --includedir=/usr/X11R7/include --localstatedir=/var --sysconfdir=/etc --disable-static --disable-maintainer-mode --enable-shared --with-dri-driverdir=/usr/X11R7/lib/dri

Mesa asks for dri2proto, downloading it right now, I'll try to test this new intel driver today (I don't have the hardware to, but some friends have it) and make dotpets later.

[techtype]

@wow

It seems that Filefront no longer has this file: devx-Xorg74-gtk2144-r1.sfs which is linked on the first post.

Could you give a new link?

[MU]

techtype
you'll find it here:
http://puppyisos.org/isos/2008-07-to-12 ... .5/iso-01/

user: puppy
password: linux
Mark

[battleshooter]

I'll try to test this new intel driver today (I don't have the hardware to, but some friends have it) and make dotpets later.

Yippee! Thanks so much Wow

[techtype]

techtype
you'll find it here:
http://puppyisos.org/isos/2008-07-to-12 ... .5/iso-01/

user: puppy
password: linux
Mark

Ah, thanks Mark!

[Leon]

Unnamed pupplet (puppy411 kernel-2.6.27.5 Xorg-7.4 LXDE)
Subject description: just another puppy derivate
...
Default encoding for filenames in vfat partitions is UTF-8 (kernel module nls_utf8 by default)
...

wow,
From my experience the Unnamed-pupplet-puppy411-kernel-2.6.27.5 Xorg-7.4-LXDE is the only Puppy that properly displays sl_SI locale special characters in Rox. I noticed that sl_SI locale special characters in Rox are shown properly even if locale is set to en_US.

Would you be willing to explain what have you done to set this option to work?

We discussed this issue on Barry's blog.
Details:
http://puppylinux.com/blog/?viewDetailed=00556

[wow]

I noticed that sl_SI locale special characters in Rox are shown properly even if locale is set to en_US.
Would you be willing to explain what have you done to set this option to work?

Easy: Full install

• You have to compile your own kernel with these options in "DOS/FAT/NT Filesystems"(kernel's .config file):

  Code: Select all

  CONFIG_FAT_DEFAULT_CODEPAGE=850
  CONFIG_FAT_DEFAULT_IOCHARSET="utf8"

  Install and boot your kernel.

Hard: Full install, initrd.gz and pup_4xx.sfs edit, remaster LiveCD.

• Compile linux kernel with these options in "DOS/FAT/NT Filesystems"(kernel's .config file):

  Code: Select all

  CONFIG_FAT_DEFAULT_CODEPAGE=850
  CONFIG_FAT_DEFAULT_IOCHARSET="utf8"

  Install and boot your kernel.
  Extract contents of initrd.gz and replace every kernel module in initrd/kernel/
  Add nls_utf8.ko and nls_cp850.ko files to initrd/kernel/fs/nls/
  Replace names(nls_cp850 and nls_utf8) in initrd/init (text file)
  Instructions to edit the initrd.gz file, patch the linux kernel, make an iso with your new kernel and more help [here], [here], [and here]

[Leon]

I noticed that sl_SI locale special characters in Rox are shown properly even if locale is set to en_US.
Would you be willing to explain what have you done to set this option to work?

Easy: Full install

• You have to compile your own kernel with these options in "DOS/FAT/NT Filesystems"(kernel's .config file):

  Code: Select all

  CONFIG_FAT_DEFAULT_CODEPAGE=850
  CONFIG_FAT_DEFAULT_IOCHARSET="utf8"

  Install and boot your kernel.

Hard: Full install, initrd.gz and pup_4xx.sfs edit, remaster LiveCD.

• Compile linux kernel with these options in "DOS/FAT/NT Filesystems"(kernel's .config file):

  Code: Select all

  CONFIG_FAT_DEFAULT_CODEPAGE=850
  CONFIG_FAT_DEFAULT_IOCHARSET="utf8"

  Install and boot your kernel.
  Extract contents of initrd.gz and replace every kernel module in initrd/kernel/
  Add nls_utf8.ko and nls_cp850.ko files to initrd/kernel/fs/nls/
  Replace names(nls_cp850 and nls_utf8) in initrd/init (text file)
  Instructions to edit the initrd.gz file, patch the linux kernel, make an iso with your new kernel and more help [here], [here], [and here]

Many thanks for the instructions.

Leon

[wow]

I'll try to test this new intel driver today (I don't have the hardware to, but some friends have it) and make dotpets later.

Yippee! Thanks so much Wow

I spoken too soon... I missed something...

The kernel device modules are not shipped with libdrm releases and should only
be built from the git tree by developers and bleeding-edge testers of
non-Intel hardware. The Intel kernel modules are developed in the Linux
kernel tree.

So I have to download and compile drm-intel. Anyway, I have packaged everything else, download these files if you want [download from filefront]:

• libdrm-2.4.4git-i686.pet
  mesa-7.3-i686.pet
  drm-2.4.4-k2.6.27.5.tar.bz2
  xf86-video-intel-2.6.1-i686.pet (attached below)

Installation:
1. Switch to Xvesa (exit X and run xorgwizard)
2. Once in Xvesa, install: libdrm-2.4.4git-i686.pet; mesa-7.3-i686.pet; xf86-video-intel-2.6.1-i686.pet
3. Extract drm-2.4.4-k2.6.27.5.tar.bz2 to any folder (example: /root)
4. Exit X, go to the drm-2.4.4.-k2.6.27.5/ folder and run install.sh. Example:

Code: Select all

cd /root/drm-2.4.4.-k2.6.27.5/
./install.sh

5. Install drm-intel modules. Pending... remember? maybe tomorrow...
Screenshot: Mesa-7.3, vesa xorg video driver, software rasterizer (vesa has no hardware acceleration)

[MU]

iscraigh also will post a kernel request soon (I asked him to post it here, after he wrote a pm).

This should force us to overthink, if we should go for a new kernel, with all the new settings we need.

I would need for the new Ati catalyst driver:

Code: Select all

# 
# Bus options (PCI etc.) 
# 
CONFIG_PCI_MSI=y

If we decide to compile such a kernel, and build new isos then, we also might switch to a newer kernel release?
Or should we stay with the current one?
I was planning to try 2.6.29 in april, because it includes some new stuff for next xorg releases (dri2 I think, but I'm not certain, if it was called different).
Apart from that, I have no need of a new kernel release yet.
We also had to test, if the Ati and Nvidia drivers compile with it, especially nvidia 96 and 173.

What do you think?
Mark

[MU]

iscraigh seems to be offline, so here I quote his request, before I go asleep:
--------------------------------------------------------------------------------

Mark

I have cobbled together a puplet based on the unamed pup for the Aspire one netbook. I still have a hardware issue with the sd card slots being recognized. Using some advice from other posting on the aspire one I was able to get the left card hotplugging but found I did not have the pciehp module.

Tempestuous suggested I ask you "very nicely" to enable it in the kernel.

I suggest you ask MU nicely to enable this module in the 2.6.27 kernel configuration. It's at:
"Bus options (PCI etc.)" > "Support for PCI Hotplug"
this will then reveal an additional option above it called "PCI Express Hotplug driver"
This driver will not load automatically. The best way to load it at each bootup is by adding it to Puppy's "ADDLIST".

If this is not to much trouble I would appreciate it.

On that note assuming you are able to do this would I have to do the whole remaster again or could I mount the sfs file (is mounting an sfs rw possible) and swap in your kernel?

I am finding myself a little over my head I just made this for my kids and now people are using it so I feel I should try to keep it up.

As log as I am harrasing you one more thing

Boot speed is slower on puppy than a full ubuntu install.

I see that sickboy from the kuki linux project has a kernel just for the aspire that is supposed to be fast, could I substitute that kernel? (It can't be that easy I am sure)
Puppy seems to take forever at

loading kernel drivers to access disk drives

Any help appreciated.


Craig

[MU]

Puppy seems to take forever at Quote:
loading kernel drivers to access disk drives

I just have a rough idea:

At startup, use the option:
pdev1=sda1

If you boot from CD, type at the bootscreen:
puppy pdev1=sda1

If you boot frugal, add in the end of the line that loads the kernel:
pdev1=sda1

Instead of sda1, use the name of the drive, where your savefile is located.
This avoids, that Puppy scans ALL partitions for a savefile.

If the delay happens BEFORE this part already, we had to look closer at initrd.gz.
We must look, if that part can be optimized.
I hope I have time for this at weekend.
In "init", there is a part, that greps dmesg for loaded drivers. If I remember well, this uses a delay/timeout.
Maybe this can be enhanced.
I boot some files from an external USB-harddisk, so maybe, this is faster that on computers without USB-drives, as they write different messages to dmesg.
I could setup a testsystem, that will completely load from my internal drive (a CF card replacing a harddisk), without other drives attached.

-----------------
Simply replacing a kernel is not that simple.
The problem is, that also the modules in initrd.gz must be replaced, and some files in /etc/modules.

Mark

[iscraigh]

Mark

Got home and was just going to post, thank you for posting for me.

I have tried the pdev tricks, as well as using pizzagoods advice on editing the initrd.gz config to not force a loading in ram of the pup save file. This trick sped boot up marginally. The slowdown seems to occure before it is looking for the pup save file.

I have tried a full install as well as a frugal, both to the ssd drive.

The version of alsa in the newer kernels support the aspire one better... so I read.

Boot speed of a full install of Ubuntu is about 55 seconds
linux4one custom Ubuntu about 50 seconds
plain puppy is about 1:02
my version about 1:10
Linpus that comes with it 20 seconds
Faster from a usb stick than from the internal drive.

It would be nice to see boot times on the Aspire of 30 or 40 seconds although this may not be realistic with a generic kernel.

Thanks for the help and for the base you have given me.


Craig


Craig

[giomanh]

[lxde-pup411-i18n-r1.sfs] [18.07 MB] [more info] [more translations] native language support / langpack
I downloaded it, but i can not mount it:

mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

[wow]

Compressed with SquashFS-LZMA-3.3, official puppy releases won't mount it. You must use my puplet, or any other with SquashFS-LZMA-3.3.

[wow]

I would need for the new Ati catalyst driver:

Code: Select all

# 
# Bus options (PCI etc.) 
# 
CONFIG_PCI_MSI=y

More reasons to recompile:

• Some people use Ndiswrapper to load WinXP drivers, but with this kernel...

  Code: Select all

  *** WARNING: This kernel uses 4K stack size option
  (CONFIG_4KSTACKS); many Windows drivers will not work
  with this option enabled. Disable CONFIG_4KSTACKS
  in kernel's .config file, recompile and install kernel

  I can't compile the latest drm-intel modules (i830 compiled, loaded and untested. i915 refuses to compile) for 2.6.27.5. I ended with the whole 2.6.29rc2 source tree when downloading drm-intel

Not so bad, because I don't need/have an AMD/ATI gpu, intel gpu, nor wireless devices I designed this iso just for me and my needs, but who cares it was fun!
____________________________________________________________________

If we decide to compile such a kernel, and build new isos then, we also might switch to a newer kernel release?

My vote goes to compile another kernel and pack it in puppy-unleashed*s format. Newer kernel release? of course, as long as it can use squashfs-lzma and aufs by default.
____________________________________________________________________

I was planning to try 2.6.29 in april, because it includes some new stuff for next xorg releases (dri2 I think, but I'm not certain, if it was called different).

Please read this:

• SquashFS version 4.0 is included in Linux Kernel 2.6.29. LZMA support is not there, but since squashfs made its way to the kernel, LZMA compression algorithm will follow it sooner or later. What does it mean for this project (squashfs-lzma.org)? There is no longer any interest in developing separate patches against squashfs 4.0. If you need it, you'll most likely find it in official Kernel 2.6.30 or so. So don't worry, be happy

____________________________________________________________________

[wow]

I'm using the latest kernel (2.6.29rc4), with requested modifications to .config file (MU, iscraig, ndiswrapper) I have no problems with this new kernel even after installing the latest nVidia's beta driver. Except for SquashFS-4.0, it is not compatible with older versions!! I was unable to use Puppy2/3/4 sfs files compressed with or without lzma.


Now I'll test this:
Ubuntu linux-source-2.6.28 (2.6.28-8.21)
http://packages.ubuntu.com/jaunty/linux-source-2.6.28