Puppy Linux Discussion Forum

[shelezyaka]

There should be a Saluki and the creator of the desktop

[alec78]

Hi All,

Had difficulty getting on line with luki-17.
I use an Huawei E169G in a Samsung X05 laptop.
I had made a fresh manual install on a USB memory dongle.
Booted up from the dongle and did the usual set up and shut down to make a save file.
Booted up again but this time with the E169G inserted.
Brought up pupdial and went through the usual set up, went to the Control Panel to set up the firewall, then pressed connect in pupdial. The window shut but no connection was established.
Shut down and re-booted without E169G inserted, then inserted the modem after system stabilised. Went through the same procedure as above same result.
Noticed that I was having to enter all the data into pupdial each time, i.e. wvdial.conf was not being written to.
Ran pupdial from a consul, this reported an error at lines 636 and 637 of pupdial @unexpected EOF while looking for@.
And to cut a long story short the above line shows the probable problem. The keyboard problem still lives, I had set the Keyboard to gb and somewhere along the line it has reverted to us.
I am on line now by manually editing wvdial.conf and blindly stabbing the keyboard looking for a #.
Hope all this helps somebody else.
BTW Midori is now quite nice.

Cheers

[Sage]

Wow! Birth of Venus. Classy. Now we're making real artistic progress.

[jemimah]

[jemimah]

[jemimah]

[DaveS]

[tronkel]

Better news with Frisbee. Seems to be working - and remembered over reboots.

The original problem may have been due to missing rtlwifi firmware that seemed to disappear from /lib/firmware when I downgraded to the k3.1.10 PAE kernel using the Saluki Custom Builder (due to the regression concerning compiling of the FGLRX module).

I simply copied over the rtlwifi firmware folder from the previous pup_save file that was used with the k3.2.8 version and that still seems to work with the older kernel version. If it gives any more bother, I'll post the Frisbee diagnostics tar-ball. No point in posting a diagnostics tar-ball for a functioning connection.

The only remaining bug on this system is CUPS. I removed the Chrome sfs, re-installed CUPS 1.3.11 and now have access to the CUPS browser interface. I installed the Brother DCP-7030 printer driver - which duly appeared in the CUPS interface. I can configure all the options, but it refuses to print a test page. It's an old story with CUPS - very probably a USB permissions issue. I'll look at it again tomorrow and see if I can locate the problem.

[gcmartin]

[Ray MK]

Hi J - ref:
Anyone else have this keyboard problem? I think I have a few UK users that haven't mentioned this bug. Anyone have ideas what's up?

Have not noticed any problems (either running live or with a savefile)

HTH - very best regards

[jemimah]

I have got a rudimentary graphical boot working.

If you haven't changed your kernel you can try it by using this initrd.gz (only with saluki-017).
http://smokey01.com/saluki/initrd.gz

You need to add this code to your bootloader to make it work

[KJ]

I am also having CUPS issues in both 016 and 017. CUPS IDs and seems to set up my Canon MX340 but nothing is printed. Jobs show as finished but printer stays inactive. I am running Midori as my sole browser. MX340 works correctly with Fluppy 012 but there I needed to install the canon_mx340-3.30.pet. Installing that .pet does not help. Interestingly, completed jobs have a 27 hour in the future stamp. Latest one showed in CUPS as "completed at Mon Apr 2 20:55:43 2012". Thanks KJ

[jemimah]

Here is the bootsplash I am planning to use. If anyone has any better ideas, please post.

Note that the upper half of the splash needs to be black.

[jemimah]

[Geoffrey]