Puppy 2.17alpha available
- esmourguit
- Posts: 1410
- Joined: Fri 17 Nov 2006, 14:45
- Location: Entre l'ile aux oiseaux.et l'ile de sainte Lucie
Bonjour à tous,
Me to. I am in France, GMT+1 and it seven instead of 8.
I have changed in GMT+2 to have the good one, but my screen became black. I had to press space to come back on the desktop but gxine (playing James Brown) was became mute. I had to go to Puppy Volume Mixer to make changes.
Cordialement.
Me to. I am in France, GMT+1 and it seven instead of 8.
I have changed in GMT+2 to have the good one, but my screen became black. I had to press space to come back on the desktop but gxine (playing James Brown) was became mute. I had to go to Puppy Volume Mixer to make changes.
Cordialement.
[url=http://moulinier.net/][color=blue][b]Toutou Linux[/b][/color][/url] - [url=http://toutoulinux.free.fr/pet.php][color=blue][b]Paquets français[/b][/color][/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
I'm now working on country and keyboard-layout setup...
Lobster, you reported the time was out by one hour.
Check /etc/localtime -- it should be a link to /usr/share/zoneinfo/London
-- right?
If that's right, what else could be wrong... what about the hardware clock on your PC? That is supposed to be set to the local time. This will read the hardware clock:
# hwclock -r
...does that agree with the time in the taskbar?
In London, you are on GMT+0, but are you on daylight saving?
If you are not, try relinking :
# ln -sf /usr/share/zoneinfo/GMT-0 /etc/localtime
#hwclock --localtime --hctosys
...because maybe /usr/share/zoneinfo/London is wrong.
Lobster, you reported the time was out by one hour.
Check /etc/localtime -- it should be a link to /usr/share/zoneinfo/London
-- right?
If that's right, what else could be wrong... what about the hardware clock on your PC? That is supposed to be set to the local time. This will read the hardware clock:
# hwclock -r
...does that agree with the time in the taskbar?
In London, you are on GMT+0, but are you on daylight saving?
If you are not, try relinking :
# ln -sf /usr/share/zoneinfo/GMT-0 /etc/localtime
#hwclock --localtime --hctosys
...because maybe /usr/share/zoneinfo/London is wrong.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Are you on Paris time?esmourguit wrote:Bonjour à tous,
Me to. I am in France, GMT+1 and it seven instead of 8.
I have changed in GMT+2 to have the good one, but my screen became black. I had to press space to come back on the desktop but gxine (playing James Brown) was became mute. I had to go to Puppy Volume Mixer to make changes.
Cordialement.
How did you change the GMT+1 to GMT+2? ...I mean, what did you change?
That was me. But just putting the raw kernel source doesn't work. Tried compiling a driver, it complained "ERROR: Kernel configuration is invalid." so I ran make oldconfig && make prepare on the kernel source and tried again. This time most of it built, but then it couldn't find /usr/src/linux-2.6.21.5/Module.symvers becuase that hasn't been built. Guess I can build the kernel.Um, who did that for us last time?
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
kirk, okay, thanks for doing that last time. It looks like we will need a sfs with some basic extra stuff in it, like that Module.symvers and System.map. Perhaps what you have done as quoted above, is enough and I just have to send those files. Attached:kirk wrote:That was me. But just putting the raw kernel source doesn't work. Tried compiling a driver, it complained "ERROR: Kernel configuration is invalid." so I ran make oldconfig && make prepare on the kernel source and tried again. This time most of it built, but then it couldn't find /usr/src/linux-2.6.21.5/Module.symvers becuase that hasn't been built. Guess I can build the kernel.Um, who did that for us last time?
I rebuilt the 217 kernel and using the /usr/src/ from the 2.16 devx file as a template, made a new kernel source sfs file. Tested it out by building some wifi drivers. I'll upload it somewhere. It's 52MB.
I'm assuming mksquashfs uses lzma by default now? But you know what assuming does.
PS: The rtl8180 driver source I had mentioned elsewhere, builds with the new kernel, but doesn't work. I'll see if there are any updates for it in the past week or so.
PS2:
My clock is an hour slow. But we have daylight savings time. I'm in Florida, eastern time zone.
# hwclock -r
Sat Jul 14 00:12:41 2007 0.000000 seconds
#
Task bar clock is 11:13pm jul 13.
/etc/localtime is linked to /usr/share/zoneinfo/Eastern.
Clock is correct when 2.16 or Windows is booted.
I'm assuming mksquashfs uses lzma by default now? But you know what assuming does.
PS: The rtl8180 driver source I had mentioned elsewhere, builds with the new kernel, but doesn't work. I'll see if there are any updates for it in the past week or so.
PS2:
My clock is an hour slow. But we have daylight savings time. I'm in Florida, eastern time zone.
# hwclock -r
Sat Jul 14 00:12:41 2007 0.000000 seconds
#
Task bar clock is 11:13pm jul 13.
/etc/localtime is linked to /usr/share/zoneinfo/Eastern.
Clock is correct when 2.16 or Windows is booted.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
kirk,
instead of the rtl8180-sa2400 driver, what about trying the proprietary Realtek wifi drivers -
RTL8185/8187/8187B
http://www.realtek.com.tw/downloads/dow ... Down=false
RTL8180L
http://www.realtek.com.tw/downloads/dow ... Down=false
instead of the rtl8180-sa2400 driver, what about trying the proprietary Realtek wifi drivers -
RTL8185/8187/8187B
http://www.realtek.com.tw/downloads/dow ... Down=false
RTL8180L
http://www.realtek.com.tw/downloads/dow ... Down=false
I've never got them to build. It's a part binary driver made for kernel 2.6.5. The one I had hoped would work for 2.6.21.5 was from here:what about trying the proprietary Realtek wifi drivers -
http://rtl-wifi.sourceforge.net/wiki/Main_Page
This one builds fine on both 2.16 and 2.17. But when I load the modules it complains about bad symbols and the card doesn't work. They have a forum, I'll do some searching. I uploaded the 217 kernel source sfs file to puppyisos.org and sent Mark a PM.
It's 1:15am time to sleep.
- esmourguit
- Posts: 1410
- Joined: Fri 17 Nov 2006, 14:45
- Location: Entre l'ile aux oiseaux.et l'ile de sainte Lucie
Yes i am in Paris time (GMT +1). Using timezone-set i changed in GMT +2 (Athenes time to have the good time).BarryK wrote:Are you on Paris time?esmourguit wrote:Bonjour à tous,
Me to. I am in France, GMT+1 and it seven instead of 8.
I have changed in GMT+2 to have the good one, but my screen became black. I had to press space to come back on the desktop but gxine (playing James Brown) was became mute. I had to go to Puppy Volume Mixer to make changes.
Cordialement.
How did you change the GMT+1 to GMT+2? ...I mean, what did you change?
[url=http://moulinier.net/][color=blue][b]Toutou Linux[/b][/color][/url] - [url=http://toutoulinux.free.fr/pet.php][color=blue][b]Paquets français[/b][/color][/url]
Barry, on the time zones you have USA eastern, central and pacific, but there is no USA-mountain zone.
You do have USA-Arizona, which is a state in the mountain time zone. However it is the only state in the mountain zone that does NOT observe daylight savings time. It turns out the time you have for Arizona is now valid in Wyoming, that is, what you have for Arizona IS the same as mountain zone daylight savings time. So it's valid everywhere but Arizona.
Just to make it interesting, the Navajo Nation in NE Arizona DOES observe daylight savings time. But I'm guessing there aren't too many Navajos using Puppy, so maybe it's not important.
hwclock -r yields the same time as I see displayed on the task bar (I'm using USA-Arizona).
Is your new time setup supposed to automatically switch between daylight savings time and standard time? Probably not, that would be awfully complex...
In 2.16.1 right-clicking or left-clicking on the taskbar clock launches the ical calendar. I haven't rebooted to check what it does in 2.17 but it might be a good idea for a right-click to go to a routine to set the time...
You do have USA-Arizona, which is a state in the mountain time zone. However it is the only state in the mountain zone that does NOT observe daylight savings time. It turns out the time you have for Arizona is now valid in Wyoming, that is, what you have for Arizona IS the same as mountain zone daylight savings time. So it's valid everywhere but Arizona.
Just to make it interesting, the Navajo Nation in NE Arizona DOES observe daylight savings time. But I'm guessing there aren't too many Navajos using Puppy, so maybe it's not important.
hwclock -r yields the same time as I see displayed on the task bar (I'm using USA-Arizona).
Is your new time setup supposed to automatically switch between daylight savings time and standard time? Probably not, that would be awfully complex...
In 2.16.1 right-clicking or left-clicking on the taskbar clock launches the ical calendar. I haven't rebooted to check what it does in 2.17 but it might be a good idea for a right-click to go to a routine to set the time...
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
sorry lost all track of time
From reading your blog and replies here, the situation seems to have resulted in new code . . .
I can confirm that it is not hardware (I am in Linux Tmxxine puplet on the same machine and the time is OK)
Do you still want me to follow your test instructions or await the next beta?
From reading your blog and replies here, the situation seems to have resulted in new code . . .
I can confirm that it is not hardware (I am in Linux Tmxxine puplet on the same machine and the time is OK)
Do you still want me to follow your test instructions or await the next beta?
Last edited by Lobster on Sun 15 Jul 2007, 04:17, edited 1 time in total.
I posted this message also at:BarryK wrote:I'm now working on country and keyboard-layout setup...
Lobster, you reported the time was out by one hour.
http://www.puppylinux.com/news/comments ... 714-103103
At first boot I choosed country option:
73 SLOVENIA
After that this error message is displayed:
cannot open file sl.map
...
Pausing for 60 seconds...
After created a new pup_save.2fs file the same error message is displayed at each boot.
If I choose Xorg then the keyboard layout is properly configured in "InputDevice" section of my xorg.conf file to:
Option "XkbLayout" "si"
I use frugal install on FAT32 with Grub4dos.
My menu.lst file:
title Puppy-p2.17a-idehd-pfix-ram-bp217a
rootnoverify (hd0,4)
kernel /bp217a/vmlinuz root=/dev/ram0 PMEDIA=idehd psubdir=bp217a pfix=ram
initrd /bp217a/initrd.gz
boot
It is interesting that there is no error message about missing sl.map file when I upgraded to Puppy 2.17a from my old Puppy 2.16 pup_save.2fs file.
The only problem when using the old pup_save.2fs file is that at every boot the timezone is set to GMT+8.
The timezone for Slovenia is GMT+1.
This is not a problem when using a pup_save.2fs file created by Puppy 2.17a.
The kernel source sfs file for 2.17 can be found here:
http://puppyisos.org/files/sfs/Puppy-2.17/
Put this in the same place as your pup_save file and have fun compiling drivers!
http://puppyisos.org/files/sfs/Puppy-2.17/
Put this in the same place as your pup_save file and have fun compiling drivers!
WakePup2 tune-up is finished. Assuming no one finds any bugs or has any additions they want in the custom boot options.
http://www.murga-linux.com/puppy/viewto ... 924#122924
http://www.murga-linux.com/puppy/viewto ... 924#122924
Dear Group,
Apologies for my previous post. The problem was a bad burn all a long. The CD-RW originally had 2.16.1 on it, 2.17alpha wouldn't work but I was able to write 2.16.1 back onto the CD and it worked. So I concluded that the CD player worked, the CD was OK but something else was wrong. Today I did a complete "slow" erase of the CD and burnt 2.17alpha to it. Puppy booted as it always has. The only hypothesis I can come up with is the 2.17 ISO is smaller so when I did a fast erase some of 2.16.1 was still there. In the past I've mainly done fast erases and the subsequent ISOs are generally larger.
Anyhow, brief test results regarding modems.
Compaq Presario Compaq C310TU with Agere modem - not detected
Sony Vaio PCG-FR720 with Conexant-Ambit modem - not detected
If anyone wants any additional information please feel free to ask.
Regards,
mmm
Apologies for my previous post. The problem was a bad burn all a long. The CD-RW originally had 2.16.1 on it, 2.17alpha wouldn't work but I was able to write 2.16.1 back onto the CD and it worked. So I concluded that the CD player worked, the CD was OK but something else was wrong. Today I did a complete "slow" erase of the CD and burnt 2.17alpha to it. Puppy booted as it always has. The only hypothesis I can come up with is the 2.17 ISO is smaller so when I did a fast erase some of 2.16.1 was still there. In the past I've mainly done fast erases and the subsequent ISOs are generally larger.
Anyhow, brief test results regarding modems.
Compaq Presario Compaq C310TU with Agere modem - not detected
Sony Vaio PCG-FR720 with Conexant-Ambit modem - not detected
If anyone wants any additional information please feel free to ask.
Regards,
mmm