Hi Kirk
Thanks for giving me a pointers of how to overcome the problems I am having; I really appreciate it. Unfortunately, I may not have time to pursue the touch pad and keyboard at the moment because the HP 14 has to go back on Monday due to a defective battery. The supplier won't send me the battery to fit.
The problems that I have on the wireless network is the same on another laptop and I can look at that further. There are a few things that could be affecting my ability to connect:
1. My SSID is hidden and so when I scan I find the mac address and a string of xxs, etc. When I type in the ssid I am not certain that the string of xxs is replaced.
2. I am not sure of the procedure for using the net-setup.sh and I have followed the flow of the options.
Configure IP Address: select wlan0 - I have tried both Auto and Static
Configure Access Profile: select wlan0 - I have tried all the options here but my ssid is hidden and it may be the cause of my problems.
Activate Settings Now: select wlan0 - I have tried the options that I have set up but it fails to connect.
3. I have also tried the wpa_gui options which is in the bottom right hand corner. I am not sure whether I should have done this before the net-setup.sh. When I have done this my hidden ssid issue remains.
If I try other Puppies and your release candidates then I can connect with Dougles Network Wizard and Frisbee. For example, at the moment, I still have the HP 14 and booted a Puppy from a usb and that allowed me to connect the wifi.
I am not certain what to do next.
Regards
peterw
Fatdog64-631 for Acer C720 only.
I've never tried to connect to a hidden ssid. You might want to add ap_scan=2 to /etc/wpa_supplicant.conf :
Some folks say that their wifi driver requires that for a hidden ssid. You could also look at /etc/wpa_supplicant.conf in the other puppies and see if they have ap_scan set.
Don't use net-setup.sh and wpa_gui. Use one or the other. I would try wpa_gui first.
P.S. A hidden ssid doesn't really do much good, encryption is much better. A hidden ssid with encryption does no good at all, finding your hidden ssid is nothing compared to cracking your encryption.
Code: Select all
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=users
update_config=1
ap_scan=2
Don't use net-setup.sh and wpa_gui. Use one or the other. I would try wpa_gui first.
P.S. A hidden ssid doesn't really do much good, encryption is much better. A hidden ssid with encryption does no good at all, finding your hidden ssid is nothing compared to cracking your encryption.
Kirk,
Thank you for making FatDog64 available for the Acer C720.
This fat dog has proved to be leaner than expected.
My observations while taking it for a walk are:
WiFi network connection: Like peterw, I could not use the wpu_gui to connect to a hidden SSID. The scan for available networks did show one with a hidden SSID [mine], but I did not then manage to enter the name and PK and gain access. I had to “unhide
Thank you for making FatDog64 available for the Acer C720.
This fat dog has proved to be leaner than expected.
My observations while taking it for a walk are:
WiFi network connection: Like peterw, I could not use the wpu_gui to connect to a hidden SSID. The scan for available networks did show one with a hidden SSID [mine], but I did not then manage to enter the name and PK and gain access. I had to “unhide
- Attachments
-
- desktop2.v01.png
- system info
- (93.15 KiB) Downloaded 1138 times
-
- desktop1.v01.png
- with nothing else running
- (169.62 KiB) Downloaded 1051 times
Thanks Kirk
was looking for a reason to return to puppy after some health issues, and you have given it to me
checklist
I have access to a c720
will not have hardware issues
will not have wireless issues
thank you very much Kirk, you have made someone very happy and opened the door for a return to puppy
well done mate
was looking for a reason to return to puppy after some health issues, and you have given it to me
checklist
I have access to a c720
will not have hardware issues
will not have wireless issues
thank you very much Kirk, you have made someone very happy and opened the door for a return to puppy
well done mate
It sure does, well actually it crashes X. So you can hit ctrl-alt-backspace to exit to a terminal and then type xwin to restart the xserver. This is caused by a bug in the patched synaptics driver. Could put in the synaptics driver from the normal 631, but then the touch pad wouldn't act as well.Display Properties [in Control Panel>Desktop]: Crashes the system, have to power off and re-boot. Since this pup is intended for the C720 only, I suspect that there is no need/room for other settings.
hi rcrsn51,
I have not removed any screws and don't seem to be having any trouble.
the only difference I have noticed is having to press ctrl+l on boot up for the bios to run (do not know if removing the screw would make any difference to this),
apart from that everything seems ok.
the install instructions on this thread seemed to have worked OK for me
hope this helps
I have not removed any screws and don't seem to be having any trouble.
the only difference I have noticed is having to press ctrl+l on boot up for the bios to run (do not know if removing the screw would make any difference to this),
apart from that everything seems ok.
the install instructions on this thread seemed to have worked OK for me
hope this helps
Thanks. So you skipped this step in the Arch instructions?
If you want to make SeaBIOS default, you MUST first remove the write protect screw and then run:
Warning: I'm serious! You HAVE to remove the write-protect screw first! Otherwise the system will be corrupted and you'll need to recover it
# set_gbb_flags.sh 0×489
You don't have to do this, it just enables SeaBIOS to load by default. Like Stripe said, you can hit the ctrl-l instead at every boot. Also removing the screw voids your warranty. There a sticker over one of the screws that says so. It's not hard though, after you get all the screws off the bottom it just snaps apart. Then you move the write-protect screw to the battery enable screw, set your flags and then put everything back.Thanks. So you skipped this step in the Arch instructions?
Quote:
If you want to make SeaBIOS default, you MUST first remove the write protect screw and then run:
Warning: I'm serious! You HAVE to remove the write-protect screw first! Otherwise the system will be corrupted and you'll need to recover it
# set_gbb_flags.sh 0×489
That's a qualified yes. I did like Stripe said except I made a small ext3 partition and a ext4 partition. Some boot loaders are slow at reading ext4, so I made an ext3 partition to hold the kernel and initrd and put my savefolder on the ext4. Also used the fatdog-split-initrd.sh script to split the initrd. That way I could do away with the mem=1950m boot parameter. I said a qualified yes because I initially tried to install legacy grub, but it could not install to the mbr, so maybe so tweaking of the partition would have helped. I just used grub4dos which worked fine. I also used no swap, I think I read somewhere that swap breaks suspend/resume.When you run Gparted on the SSD, do you need to worry about partition alignment or is this handled automatically?
Thanks. I have been confused by articles like this. But I think that with a clean partition, Gparted gets it right for SSDs. You just select "Align to MB" instead of "Align to Cylinder".
I have ordered a used C720. Unfortunately, mine is costing a bit more than $99.
I have ordered a used C720. Unfortunately, mine is costing a bit more than $99.
I've saw articles like that, don't really know how much difference it makes. Probably could use a few more blocks before the first partition, don't think there was enough room for grub legacy.
The c720 is really pretty quick, the cpu is a cut-down version of a 4th generation i series. Mine is a 2Gb model, more ram would have been nice, but it's good enough. I don't use it every day, mainly when I'm traveling. Fast, light and good battery life. When we get 700 stable, I'll make another iso for this.
The c720 is really pretty quick, the cpu is a cut-down version of a 4th generation i series. Mine is a 2Gb model, more ram would have been nice, but it's good enough. I don't use it every day, mainly when I'm traveling. Fast, light and good battery life. When we get 700 stable, I'll make another iso for this.
Here is my understanding of the "SSD Partition Alignment" issue. This may be over-simplified - please feel free to comment.
Conventional hard drives read/write data in blocks of 512 bytes (1/2 K). But SSD's work in larger 4K blocks. When your computer wants to read/write a chunk of data to the SSD, it's best if the chunk fits entirely inside one of these 4K blocks. If it straddles the boundary of two blocks, the SSD has to read/write both of them. That's bad.
So when you format an SDD, you want each partition to start on a 4K boundary. That way, each data block from your computer is guaranteed to fit inside a 4K block on the SSD.
But in conventional partitioning schemes, partitions can start almost anywhere. If they start on old-style cylinder boundaries, they probably won't match up with the 4K blocks.
Here is how Gparted now works with an SSD. It collects the 4K blocks into groups of 256 (4K x 256 = 1 MB). So it sees the SSD as a string of 1MB blocks.
It reserves the first 1MB block for the MBR/partition table, even though a standard DOS MBR only needs a bit of that space. It then starts each partition on a 1 MB boundary. That ensures that each 1MB block of the partition matches up exactly with a whole number of 4K blocks on the SSD. Your SSD is optimized.
If you are using a recent version of Gparted, just select the default "Align to MB" and you are good to go.
This might be a significant issue for Puppy users who have installed SSD's but have formatted them with old versions of Gparted that have "aligned to cylinders".
Here is a test. Run "fdisk -l" and check the Start value for each partition. If it's an odd number like 63, that's bad. The partition is NOT aligned. If it's a power of two, like 2048, that's good.
Here is why 63 is bad. A 4K block on the SSD is equivalent to 8 basic 512 byte sectors. In fdisk, sectors are numbered starting at 0. If your first partition starts at sector 63, there are 63 unassigned sectors before it. But that's one less than a multiple of 4K. So the start of your partition is not aligned with the start of a 4K block.
Conventional hard drives read/write data in blocks of 512 bytes (1/2 K). But SSD's work in larger 4K blocks. When your computer wants to read/write a chunk of data to the SSD, it's best if the chunk fits entirely inside one of these 4K blocks. If it straddles the boundary of two blocks, the SSD has to read/write both of them. That's bad.
So when you format an SDD, you want each partition to start on a 4K boundary. That way, each data block from your computer is guaranteed to fit inside a 4K block on the SSD.
But in conventional partitioning schemes, partitions can start almost anywhere. If they start on old-style cylinder boundaries, they probably won't match up with the 4K blocks.
Here is how Gparted now works with an SSD. It collects the 4K blocks into groups of 256 (4K x 256 = 1 MB). So it sees the SSD as a string of 1MB blocks.
It reserves the first 1MB block for the MBR/partition table, even though a standard DOS MBR only needs a bit of that space. It then starts each partition on a 1 MB boundary. That ensures that each 1MB block of the partition matches up exactly with a whole number of 4K blocks on the SSD. Your SSD is optimized.
If you are using a recent version of Gparted, just select the default "Align to MB" and you are good to go.
This might be a significant issue for Puppy users who have installed SSD's but have formatted them with old versions of Gparted that have "aligned to cylinders".
Here is a test. Run "fdisk -l" and check the Start value for each partition. If it's an odd number like 63, that's bad. The partition is NOT aligned. If it's a power of two, like 2048, that's good.
Here is why 63 is bad. A 4K block on the SSD is equivalent to 8 basic 512 byte sectors. In fdisk, sectors are numbered starting at 0. If your first partition starts at sector 63, there are 63 unassigned sectors before it. But that's one less than a multiple of 4K. So the start of your partition is not aligned with the start of a 4K block.
Kirk,
I have been reading with interest your account of Fatdog64 on the C720, and it generated many questions!
I have a C710, and have been unable to go beyond booting ChromeOS and Ubuntu. Allegedly, ctrl-u in the developer mode will allow booting from USB, but even with an updated bios I was unsuccessful in doing so (I was using a gpt-partitioned USB stick); and there is no “legacy mode
I have been reading with interest your account of Fatdog64 on the C720, and it generated many questions!
I have a C710, and have been unable to go beyond booting ChromeOS and Ubuntu. Allegedly, ctrl-u in the developer mode will allow booting from USB, but even with an updated bios I was unsuccessful in doing so (I was using a gpt-partitioned USB stick); and there is no “legacy mode
[quote="eowens2"]Kirk,
I have been reading with interest your account of Fatdog64 on the C720, and it generated many questions!
I have a C710, and have been unable to go beyond booting ChromeOS and Ubuntu. Allegedly, ctrl-u in the developer mode will allow booting from USB, but even with an updated bios I was unsuccessful in doing so (I was using a gpt-partitioned USB stick); and there is no “legacy mode
I have been reading with interest your account of Fatdog64 on the C720, and it generated many questions!
I have a C710, and have been unable to go beyond booting ChromeOS and Ubuntu. Allegedly, ctrl-u in the developer mode will allow booting from USB, but even with an updated bios I was unsuccessful in doing so (I was using a gpt-partitioned USB stick); and there is no “legacy mode
I changed it to MBR, that might not have been necessary. It's not a normal uefi implementation, you use the SeaBIOS payload to boot, that's why I went with MBR.On the C720, you seemed to boot Fatdog64 from the USB stick in Legacy mode. Then from within Fatdog64 you repartitioned the SSD. Did you leave the SSD with the GPT partition table, or change it to MBR? You mentioned installing Grub4Dos; does that work with UEFI/GPT? On the SSD, did you make only one partition? Filesystem?
No, I made the changes to boot directly into SeaBIOS. See the first post for the Arch linux link.So on power-on, does your C720 boot to the developer screen, then ctrl-d takes you to the (single entry) Grub menu?
Sure, if you have the space and you can patch the kernel modules for those distos.Might it be possible to multiboot (Fatdog64 plus ?Ubuntu, ?Linux Mint?)
This Chromebook line seems to have a really “locked down