Wary/Racy 5.3RC2 (5.2.91)
ATI Radeon HD6000 video card. Built-in driver is no go
Running Racy 5.2.90RC with ATI Radeon HD6050
The radeon driver included with this Puppy does not seem to work with the 3.0.17 kernel
I tried to compile the proprietary driver from the AMD web page. This compile fails with a DKMS error. The DKMS version that I installed was a DEB from Debian testing. I have a kernel source pet for k3.0.17 PAE installed - maybe this is a problem as well -it's the nearest kernel source version I could find. The DEVX used is the one for Racy 5.2.90
How can I set up the correct build environment for this driver?
I have got video to run using the VESA driver.
_________________
The radeon driver included with this Puppy does not seem to work with the 3.0.17 kernel
I tried to compile the proprietary driver from the AMD web page. This compile fails with a DKMS error. The DKMS version that I installed was a DEB from Debian testing. I have a kernel source pet for k3.0.17 PAE installed - maybe this is a problem as well -it's the nearest kernel source version I could find. The DEVX used is the one for Racy 5.2.90
How can I set up the correct build environment for this driver?
I have got video to run using the VESA driver.
_________________
Life is too short to spend it in front of a computer
Re: ATI Radeon HD6000 video card. Built-in driver is no go
I was able to compile the amd-driver-installer-12-2-x86.x86_64.run fortronkel wrote: I tried to compile the proprietary driver from the AMD web page. This compile fails with a DKMS error. The DKMS version that I installed was a DEB from Debian testing. I have a kernel source pet for k3.0.17 PAE installed - maybe this is a problem as well -it's the nearest kernel source version I could find. The DEVX used is the one for Racy 5.2.90
my hd4200.
I opened the terminal and ran "sh
amd-driver-installer-12-2-x86.x86_64.run", when it finished compiling
I did the "aticonfig --initial" command and then exited the terminal
and rebooted.
direct rendering: Yes
server glx vendor string: ATI
server glx version string: 1.4
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: ATI Mobility Radeon HD 4200 Series
OpenGL version string: 3.3.11554 Compatibility Profile Context
- Attachments
-
- sfsload.jpg
- (17.49 KiB) Downloaded 1004 times
Thanks Billtoo - the link to the kernel source is here:
http://bkhome.org/sources/kernel-3.0.17/
Compiled without error this time.
"report-video" command still shows VESA as the driver though. Other people have also found this to be the case as well. Uhu I see why - the xorg.conf that got updated by the "aticonfig --initial" command now has two device sections in it - one of which shows the vesa driver.
This looks like a bug in the proprietary driver then?
http://bkhome.org/sources/kernel-3.0.17/
Compiled without error this time.
"report-video" command still shows VESA as the driver though. Other people have also found this to be the case as well. Uhu I see why - the xorg.conf that got updated by the "aticonfig --initial" command now has two device sections in it - one of which shows the vesa driver.
This looks like a bug in the proprietary driver then?
Video appears to work though.Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]
#Option "ModeSetClearScreen" # [<bool>]
#Option "NoDDC" # [<bool>]
Identifier "Card1"
Driver "vesa"
BusID "PCI:2:0:0"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:2:0:0"
EndSection
Life is too short to spend it in front of a computer
Yes, report video info is wrong, hardware acceleration is working though because google earth and other programs (games ) that need it work fine.tronkel wrote:Thanks Billtoo - the link to the kernel source is here:
http://bkhome.org/sources/kernel-3.0.17/
Compiled without error this time.
"report-video" command still shows VESA as the driver though. Other people have also found this to be the case as well. Uhu I see why - the xorg.conf that got updated by the "aticonfig --initial" command now has two device sections in it - one of which shows the vesa driver.
This looks like a bug in the proprietary driver then?
Video appears to work though.Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]
#Option "ModeSetClearScreen" # [<bool>]
#Option "NoDDC" # [<bool>]
Identifier "Card1"
Driver "vesa"
BusID "PCI:2:0:0"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:2:0:0"
EndSection
EDIT: I should say some games work, nexuiz works, others like openarena that would work in earlier releases of wary don't for some reason.
-
- Posts: 106
- Joined: Fri 22 Dec 2006, 08:30
- Location: Rome, Italy
Wary 5.2.90 as Virtualbox guest
I installed Wary 5.2.90 under Virtualbox 4.1.10. I choose Wary instead of Racy because the emulated hardware in Virtualbox is nothing to write home about, and the lower resource usage of Wary doesn't hurt either.
Only problem I had was xorgwizard crashing to a black screen trying to start X (which is required if you want to install the Virtualbox Guest Additions which enable a number of useful features, such as mouse integration, shared clipboard, shared folders, 3D acceleration support, window resize and so on).
Selecting Vesa does work by the way, but you have to disable mouse integration from the vm dropdown menu and you don't have access to the above goodies.
However I restarted the virtual machine with puppy pfix=nox and found out that xorgwizard had left behing a xorg conf in a usable state - I only had to edit it and set the monitor resolution @ 1024*768*24, and this time xwin put me in a regular X (non-Vesa) environment.
Next step was to compile the Guest Additions, so I downloaded the kernel sources sfs and the devx sfs (btw, I didn't have to run anything to connect the network, it worked right out of the box). I made the boot manager mount the sfs, told the VM to load the Guest Additions iso image that comes with the Virtualbox install, then I gave these commands from a terminal:
Everything worked perfect, no errors or weird messages. I only had to reboot Puppy as directed by the install and figure out how to launch the services that virtualbox requires (they are in the VBoxClient-all script, so either you arrange for VBoxClient-all to be launched at X startup, or look into it and make the services it launches start from where services are supposed to start in first place).
Bottom line, this is the first Puppy I see in years that runs under Virtualbox with all the Guest Addition features enabled and working, and it is pretty fast as well.
Hopefully the detection issue in xorgwizard is fixable, or else we could just start in Vesa, download a proper xorg.conf and restart X...
Anyway, thanks for another awesome Puppy
Only problem I had was xorgwizard crashing to a black screen trying to start X (which is required if you want to install the Virtualbox Guest Additions which enable a number of useful features, such as mouse integration, shared clipboard, shared folders, 3D acceleration support, window resize and so on).
Selecting Vesa does work by the way, but you have to disable mouse integration from the vm dropdown menu and you don't have access to the above goodies.
However I restarted the virtual machine with puppy pfix=nox and found out that xorgwizard had left behing a xorg conf in a usable state - I only had to edit it and set the monitor resolution @ 1024*768*24, and this time xwin put me in a regular X (non-Vesa) environment.
Next step was to compile the Guest Additions, so I downloaded the kernel sources sfs and the devx sfs (btw, I didn't have to run anything to connect the network, it worked right out of the box). I made the boot manager mount the sfs, told the VM to load the Guest Additions iso image that comes with the Virtualbox install, then I gave these commands from a terminal:
Code: Select all
make -C /usr/src/linux oldconfig prepare scripts
mkdir /var/run/vboxadd
adduser -S -G daemon -u 999 -h /var/run/vboxadd vboxadd
mount /dev/cdrom /mnt/cdrom
/mnt/cdrom/VBoxLinuxAdditions.run
umount /mnt/cdrom
sync
Bottom line, this is the first Puppy I see in years that runs under Virtualbox with all the Guest Addition features enabled and working, and it is pretty fast as well.
Hopefully the detection issue in xorgwizard is fixable, or else we could just start in Vesa, download a proper xorg.conf and restart X...
Anyway, thanks for another awesome Puppy
langpack_es
Latest Spanish langpack available here (2.4 MB):
http://www.datafilehost.com/download-e3e63da7.html
Added:
hunspell-es
P-series (Pmusic, Pburn etc.) locales
Work in progress, yet with lots of translations
http://www.datafilehost.com/download-e3e63da7.html
Added:
hunspell-es
P-series (Pmusic, Pburn etc.) locales
Work in progress, yet with lots of translations
Re: Wary/Racy 5.3RC (5.2.90)
Hi BilltooBilltoo wrote:EDIT: I installed the Broadcom-STA wl pet and then loaded the module, it's working fine, it sees the wireless as eth0 but it is working.
Thanks again.
Glad it worked - although you shouldn't have needed to "load the module" - did you reboot after installing the pet?? It should have been automatic.
Is the connection persistent after a reboot?
Cheers
peebee
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Wary/Racy 5.3RC (5.2.90)
# msginit
alsaconf.pot:208: missing `msgstr' section
msginit: found 1 fatal error
#
Thus "bad news" when trying to translate
fixed by:
alsaconf.pot:208: missing `msgstr' section
msginit: found 1 fatal error
#
Thus "bad news" when trying to translate
fixed by:
Code: Select all
#: alsaconf:1228
#msgid ""
alsaconf.pot
I have created alsaconf.pot manually as it cannot be regenerated by xgettext. I have never used momanager to translate it (I used poedit only). It's good you've found this bug.
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Wary/Racy 5.3RC (5.2.90)
I have translated alsaconf now (geany and msgfmt)
2 changes in script, see image.
DIALOG='dialog' #has correct yesno
and
#export LANG=C
-------------------------
edited 20120322
These test have been made from virtual console.
Launched from menu and alsawizard GUI
we need to change last line of /usr/sbin/alsawizard from
to
2 changes in script, see image.
DIALOG='dialog' #has correct yesno
and
#export LANG=C
-------------------------
edited 20120322
These test have been made from virtual console.
Launched from menu and alsawizard GUI
we need to change last line of /usr/sbin/alsawizard from
Code: Select all
rxvt -geometry 60x3 -bg orange -e /usr/sbin/alsaconf
Code: Select all
#rxvt -geometry 60x3 -bg orange -e /usr/sbin/alsaconf
urxvt -bg orange -e /usr/sbin/alsaconf
- Attachments
-
- alsaconf_dialog.png
- (20.36 KiB) Downloaded 800 times
Last edited by L18L on Thu 22 Mar 2012, 20:08, edited 1 time in total.
Re: Wary/Racy 5.3RC (5.2.90)
I forget if I rebooted, probably not.peebee wrote: Glad it worked - although you shouldn't have needed to "load the module" - did you reboot after installing the pet?? It should have been automatic.
Is the connection persistent after a reboot?
Cheers
peebee
It is persistent after a reboot, it's working well.
The screenshot shows the b43 module that I chose, guess it was a happy accident
- Attachments
-
- b43.jpg
- (31.5 KiB) Downloaded 875 times
Re: Wary/Racy 5.3RC (5.2.90)
HmmmmBilltoo wrote:The screenshot shows the b43 module that I chose, guess it was a happy accident
Now we have a mystery......
If the B43 driver was being used the device name would be wlan0 not eth0 which is what the wl driver creates..
Can you do an lsmod in a console - I think you'll see wl listed but b43 shouldn't be there.......
If they're both there not sure what you've done - but you should only have 1 not both!!
Cheers
Peebee
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Re: Wary/Racy 5.3RC (5.2.90)
Here's the lsmod output.peebee wrote: Hmmmm
Now we have a mystery......
If the B43 driver was being used the device name would be wlan0 not eth0 which is what the wl driver creates..
Can you do an lsmod in a console - I think you'll see wl listed but b43 shouldn't be there.......
If they're both there not sure what you've done - but you should only have 1 not both!!
Cheers
Peebee
Last edited by Billtoo on Wed 21 Mar 2012, 21:32, edited 1 time in total.
I'm using icewm but I switched back to jwm to try poweroff and reboottronkel wrote:It appears that the power-off and reboot menu options in JWM don't work. Maybe it's a kernel issue. Anyone else got this problem?
This Racy is fast - the fastest Linux distro on four legs!
menu options and both worked on my full install.
Re: Wary/Racy 5.3RC (5.2.90)
Hi BilltooBilltoo wrote:Here's the lsmod output.
That's OK - no sign of B43 - just wl and michael-mic which is what I'd expect for the wl driver - I think your selection of the b43 module must just have triggered a modprobe or the equivalent steps for a reboot - or enough anyway to trigger wl into working - as you say a red herring.
I guess as eth0 has been created you mustn't have an ethernet socket on your machine - otherwise that would be eth0 and the wifi would be eth1. If you are missing an eth0 that should be there then that's another facet to investigate....
Cheers
peebee
Last edited by peebee on Wed 21 Mar 2012, 19:18, edited 1 time in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Re: Wary/Racy 5.3RC (5.2.90)
There is an ethernet socket on the netbook, I think I'll start from scratch when I get more time and see how it goes. I'll install your pet and reboot this timepeebee wrote:
I guess as eth0 has been created you mustn't have an ethernet socket on your machine - otherwise that would be eth0 and the wifi would be eth1. If you are missing an eth0 that should be there then that's another facet to investigate....
Cheers
peebee
Just installed Racy 5.2.90 and it seems to be working very well.
I have come across one problem however.
I use a boot floppy with grub4dos to boot all my puppies.
However I failed to create a boot floppy using Racy.
Here is the log file:
/usr/sbin/grub4dosconfig
version 1.7.2
Tue Mar 20 16:53:25 UTC 2012
BINSTALLER=bootlace.com
sda(MBR)_40.0GB_ATA_ST340014A_
fd0_(FLOPPY_DISK)
sda2/racy5.2.90frugal/puppy_racy_5.2.90.sfs|puppy_racy_5.2.90
sda2/puppy528/lupu_528.sfs|lupu_528
sda2/slacko5.3frugal/puppy_slacko_5.3.sfs|puppy_slacko_5.3
sda2/slacko5.3frugal/puppy_slacko_5.3.sfs|puppy_slacko_5.3
mkfs.msdos 3.0.11 (24 Dec 2010)
Wrigting... /mnt/fd0/menu.lst
Installing bootloader on floppy...
bootlace.com --floppy --chs /dev/fd0
Error: Cannot open file for read/write access.
BOOTLACE writes GRLDR BOOT RECORD to MBR or to the boot area of a file system.
Usage: bootlace.com [OPTIONS] DEVICE_OR_FILE
Options: --read-only, --floppy[=N], --boot-prevmbr-first, --boot-prevmbr-last,
--no-backup-mbr, --force-backup-mbr, --mbr-enable-floppy, --mbr-disable-floppy,
--mbr-enable-osbr, --mbr-disable-osbr, --duce, --time-out=T, --hot-key=K,
--preferred-drive=D, --preferred-partition=P, --sectors-per-track=S, --heads=H,
--start-sector=B, --total-sectors=C, --install-partition=I, --lba, --chs,
--fat12, --fat16, --fat32, --vfat, --ntfs, --ext2, --serial-number=SN,
--restore-mbr, --mbr-no-bpb, --chs-no-tune
DEVICE_OR_FILE: Filename of the device or image. For DOS, a BIOS drive number
(in hex 0xHH or decimal DDD format)can be used to access the drive.
Failed to install bootlace.com.
My work around was to create a boot floppy in Lucid 5.2.8 using the same floppy that failed in Racy.
I'm sure this is only of minority interest but I said I'd report it anyway.
irishrm
I have come across one problem however.
I use a boot floppy with grub4dos to boot all my puppies.
However I failed to create a boot floppy using Racy.
Here is the log file:
/usr/sbin/grub4dosconfig
version 1.7.2
Tue Mar 20 16:53:25 UTC 2012
BINSTALLER=bootlace.com
sda(MBR)_40.0GB_ATA_ST340014A_
fd0_(FLOPPY_DISK)
sda2/racy5.2.90frugal/puppy_racy_5.2.90.sfs|puppy_racy_5.2.90
sda2/puppy528/lupu_528.sfs|lupu_528
sda2/slacko5.3frugal/puppy_slacko_5.3.sfs|puppy_slacko_5.3
sda2/slacko5.3frugal/puppy_slacko_5.3.sfs|puppy_slacko_5.3
mkfs.msdos 3.0.11 (24 Dec 2010)
Wrigting... /mnt/fd0/menu.lst
Installing bootloader on floppy...
bootlace.com --floppy --chs /dev/fd0
Error: Cannot open file for read/write access.
BOOTLACE writes GRLDR BOOT RECORD to MBR or to the boot area of a file system.
Usage: bootlace.com [OPTIONS] DEVICE_OR_FILE
Options: --read-only, --floppy[=N], --boot-prevmbr-first, --boot-prevmbr-last,
--no-backup-mbr, --force-backup-mbr, --mbr-enable-floppy, --mbr-disable-floppy,
--mbr-enable-osbr, --mbr-disable-osbr, --duce, --time-out=T, --hot-key=K,
--preferred-drive=D, --preferred-partition=P, --sectors-per-track=S, --heads=H,
--start-sector=B, --total-sectors=C, --install-partition=I, --lba, --chs,
--fat12, --fat16, --fat32, --vfat, --ntfs, --ext2, --serial-number=SN,
--restore-mbr, --mbr-no-bpb, --chs-no-tune
DEVICE_OR_FILE: Filename of the device or image. For DOS, a BIOS drive number
(in hex 0xHH or decimal DDD format)can be used to access the drive.
Failed to install bootlace.com.
My work around was to create a boot floppy in Lucid 5.2.8 using the same floppy that failed in Racy.
I'm sure this is only of minority interest but I said I'd report it anyway.
irishrm
5.2.90
Racy-5.2.90
Noticed that this new version has slipped back to default of Seamonkey 2.5 from previous Racy version where it was 2.6 and was just wondering what the reason or advantage is? 2.5 seems to work well although the buzz seems to be towards 2.7 ??
>>>---Indian------>
Noticed that this new version has slipped back to default of Seamonkey 2.5 from previous Racy version where it was 2.6 and was just wondering what the reason or advantage is? 2.5 seems to work well although the buzz seems to be towards 2.7 ??
>>>---Indian------>
Cloud Computing For Every Puppy (a .pet)
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
talking about open wifi here. and both the desktop icon and the bottom tray icon.
cant see that "disconnect from network" or "disconnect from ethernet/wireless networks" followed by "reconnect to network" or "auto connect to wireless networks" is having the desired effect. disconnects ok but need to use the network wizard to reconnect.
cant see that "disconnect from network" or "disconnect from ethernet/wireless networks" followed by "reconnect to network" or "auto connect to wireless networks" is having the desired effect. disconnects ok but need to use the network wizard to reconnect.